We are still using version 4 of nworks. We now want to move to version 5.
I want to use more then one vic and balance them.
But how about the syslogconfiguration. Can is use dns roundrobin to specify an name for both the vic's and use that in my syslog.conf?
Thanks in advance.
-
- Novice
- Posts: 5
- Liked: never
- Joined: Jun 17, 2009 8:02 am
- Full Name: Rob Mokkink
- Contact:
-
- Expert
- Posts: 181
- Liked: 13 times
- Joined: Jan 13, 2010 6:08 pm
- Full Name: Brian Pavnick
- Contact:
Re: syslog config + balance VIC
Hi there!
You will actually want to forward syslogs to each of the collectors in your environment. So within the syslog.conf you will want to have multiple entries for your multiple collectors. OR.... you can look at all of the available syslog forwarder tools out there (ex: Kiwi Syslog Server, etc.).
The reason why you need to forward SYSLOG events to all collectors is because of our high availability offered in 5.0. SCOM will only receive SYSLOG events from the collector actively monitoring the ESX Host that generated the SYSLOG event. Should that ESX Host move over to a collector (due to collector failure, or being moved manually by a MC Administrator) that does not receive SYSLOGs, you will not see any SYSLOGs generated within SCOM. By forwarding SYSLOG events to all collectors you can ensure that regardless the collector SYSLOG events will make it to SCOM.
Hope this helps! Please let us know if you have any additional questions!
-Brian
You will actually want to forward syslogs to each of the collectors in your environment. So within the syslog.conf you will want to have multiple entries for your multiple collectors. OR.... you can look at all of the available syslog forwarder tools out there (ex: Kiwi Syslog Server, etc.).
The reason why you need to forward SYSLOG events to all collectors is because of our high availability offered in 5.0. SCOM will only receive SYSLOG events from the collector actively monitoring the ESX Host that generated the SYSLOG event. Should that ESX Host move over to a collector (due to collector failure, or being moved manually by a MC Administrator) that does not receive SYSLOGs, you will not see any SYSLOGs generated within SCOM. By forwarding SYSLOG events to all collectors you can ensure that regardless the collector SYSLOG events will make it to SCOM.
Hope this helps! Please let us know if you have any additional questions!
-Brian
Brian Pavnick | Cireson| Solutions Architect
- Follow me on Twitter @ vbpav
- Reach me on e-mail @ brian.pavnick@cireson.com
- Follow me on Twitter @ vbpav
- Reach me on e-mail @ brian.pavnick@cireson.com
-
- Novice
- Posts: 5
- Liked: never
- Joined: Jun 17, 2009 8:02 am
- Full Name: Rob Mokkink
- Contact:
Re: syslog config + balance VIC
Hi Brian,
Thanks for your quick response.
I will update my kickstart script and syslogconfigurator (which i already have in place) and add both syslog servers to the syslog.conf
Thanks for your quick response.
I will update my kickstart script and syslogconfigurator (which i already have in place) and add both syslog servers to the syslog.conf
Who is online
Users browsing this forum: No registered users and 1 guest