Skip to main content

Configuring SNMP traps for the vCenter Server



Steps to configure the vCenter Server to generate SNMP traps:

A.In the Home page of vSphere Client
B.Select vCenter Server Settings 
C.Select SNMP configuration
D.Enable one of the SNMP receivers
E. Provide the details for : 

  • Receiver URL : Provide the host name of the Management Server (target SNMP server / monitoring tool) which will be connected to the VMware vCenter Server.(VMware vCenter Server sends the SNMP traps to this Management Server)
  • Configure port 162 as the SNMP port.
  • Community String: Provide community string (default string is "public") SNMP versions v1/v2/v3 are supported


 That is all that is needed for the configuration.  Now you need to configure alarm for generating SNMP traps in the vCenter server. When ever there is a change in the environment ( host state change, VM state change ,etc) the trigger will be generated and send an alert to the monitoring server. 

Configure the Alarms

After you have setup the external SNMP server, vCenter Server can now ready to send SNMP traps to it. There are  alarms in vCenter Server that are configured to send traps by default. So your SNMP server should receive alarms as soon as you have the SNMP setup.

Steps: 


  • Add an alarm to monitor the changes related to VM state and vCenter Server status, and then adding the appropriate action (ie, send a notification trap).
  • In the Home page of the VMware vSphere Client, select Hosts and Clusters and right-click on the VMware vCenter Server, data-center or an individual virtual machine to set the alarm. You can set the alarm at an individual virtual machine level, at the data center level, or at the entire VMware vCenter Server level. It is recommended to set it at the VMware vCenter Server level.
  • In the General tab, provide alarm details with alarm type set for monitoring the virtual machines. Enter the details as listed in the following table:
  • Alarm Name :Provide the name of the alarm.
  • Description :Provide additional information about the alarm.
  • Alarm Type :Select Virtual Machines in the Monitor drop-down list.
  • Select Monitor for specific events occurring on this object, for example, VM powered On option. Ensure that Enable this alarm check box is selected.
  • In the Triggers tab, add the required triggers to monitor the states of the virtual machine. For example, VM created, VM migrated, VM powered on, VM powered off, VM suspended, and so on.





Provide information on when to send the notification trap.

 In the Actions tab of the Alarm Settings panel, click Add to add a new action. In the Action drop-down list, select Send a notification trap option. 

 That's it. You now will be able to see the alerts in the monitoring tool dashboard. 

 Cheers ! 

Labels:

Popular posts from this blog

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N...
Read more

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this...
Read more

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely av...
Read more