Hello,
Does anyone try and succeed to get SNMP traps from ESX server to MOM?
thanks
We don't use SNMP. We forward syslog messages to our MOM server. Works great.
You can always use the Nworks management pack for ESX server.
From what I've gathered it's the better option for MOM management.
They also have a beta for MOM 2007 available.
http://www.nworks.com/downloads/vmware/VMware%20SPI%20Datasheet.pdf
\- Anders
Maybe, but IMO it's quite expensive. What they told me is about 1000US-$ per monitored host CPU.
actually it's now licensed by ESX Host, not Host-cpu...about $1000 US per host (includes 1 year support+upgrades). New licensing model.
And our beta for OpsMgr 2007 is just out, supports VI3 with Topology views, metrics and events grabbed from the VC2 SDK
Check it out!
We created a script that is executed via a trigger and creates an event in the virtual center servers event log and bingo MOM reads and alerts!!
We like to monitor our ESX 3.0.1 servers using MOM 2005, is there a direct management pack for free available from VMware instead of using third party one like nworks. I am sorry i am not against nworks but just want to know if there is anything available from VMware?
Bister, could you let us know how you setup syslogs to forward, this sounds interesting and I would like to know how to set it up?
Thanks
Zippy,
That sounds slick! Would you be interested in sharing?
Thanks!
What about: EXC Software, we use it in conjunction with MOM
Sending Alerts to the Event log is fairly simple.
Create a vbs file and put it on your VC server, say in C:\
alert.vbs
' Takes alerts from VirtualCenter and puts them in the EventLog
Const LogName = "Application"
EventID = WScript.Arguments.Item(0)
Source = WScript.Arguments.Item(1)
Description = WScript.Arguments.Item(2)
Set WshShell=WScript.CreateObject("WScript.Shell")
strCommand="eventcreate /T Warning /ID "& EventID & " /L "&LogName&" /SO "& _
Chr(34) & Source& Chr(34)& " /D " & Chr(34) & Description & Chr(34)
WshShell.Run strCommand
All this script does is take 3 parameters, and creates a Warning event to the Application Event Log, the parameters are.
1. Event id, number between 1 and 1000.
2. Event Title
3. Event Description
You can pass parameters to the script from VirtualCenter, I picked \{alarmName} \{newStatus} and \{eventDescription} as the most appropriate.
There are other parameters that can be passed to the script, but the above seems to work well.
Other parameters:
\{eventDescription}
\{targetName}
\{alarmName}
\{triggeringSummary}
\{declaringSummary}
\{oldStatus}
\{newStatus}
\{target}
To configure: In VirtualCenter select an Alert, i.e. ESX Host Connection Status; Select Actions, and add an action of Run Script, and enter the following script command to run:
cscript c:\alert.vbs 700 "\{alarmName} \{newStatus}" "\{eventDescription}"[/b]
This will then call the vb script and log events in the event log, it seems to work for all alerts. The only thing I suggest changing is the event ID for each alert.
John