Microsoft

Configure SNMP on the vCenter Server Appliance 6.5

vCenter Server Appliance includes an Simple Network Management Protocol agent that can send trap notifications and receive GET, GETBULK, and GETNEXT requests. You can use the appliance shell API commands to enable and configure the Simple Network Management Protocol agent in vCenter Server appliance. You need to configure the agent differently depending on whether you want to use Simple Network Management Protocol v1/v2c or v3. Here we are discussing about configuring SNMP v1 agaent on VCSA 6.5.
In vSphere 6.0, SNMP v3 informs are not supported. The vCenter Server Appliance supports only notifications such as v1 and v2c traps, as well as v3 traps with all security levels.

To get the current Simple Network Management Protocol configuration of vCenter Server appliance 6.5,  Loging to the vCenter Server appliance using SSH and execute the below command


snmp.get

You will get the current configuration of Simple Network Management Protocol settings on VCSA 6.5. As of now, 
Nothing is configured and Simple Network Management Protocol is also not enabled.

Before enabling Simple Network Management Protocol on VCSA 6.5, We need to configure the Simple Network Management Protocol communities on the vCenter Server appliance 6.5. To Set the community for VCSA, Execute the below command


snmp.set --communities 

Example :  snmp.set --communities Management-server

We need to configure VCSA to send Simple Network Management Protocol trap data. To configure this, Execute the below command Trap server IP information. I have 2 Simple Network Management Protocol trap servers  (172.20.10.253 & 172.20.10.50). Simple Network Management Protocol uses the default UDP port 161 for general Simple Network Management Protocol messages and UDP port 162 for Simple Network Management Protocol trap messages.


snmp-set --targets server1-ip@162/communitystring,server2-ip@162/communitystring

Example:

snmp.set --targets 172.20.10.253@162/management-server,172.20.10.50@162/management-server


There are four levels of logging to choose from:  debug|info|warning|error  (“debug” has the highest level of verbosity, and “error” has the lowest). I will be configuring my logging level as “warning”. To set the logging level, Execute the below command


snmp.set --loglevel warning

Once the configuration is completed, We need to enable the Simple Network Management Protocol on the vCenter Server appliance using the below command


snmp.enable

Once you have configured and enabled the settings, Validate the configuration information using the below command
snmp.get

Once all the configuration is completed, You can send the test trap using the below command


snmp.test

You will see the “Sucess:True” if the Simple Network Management Protocol is configured correctly.

 
Rajesh Radhakrishnan

Share
Published by
Rajesh Radhakrishnan

Recent Posts

NAKIVO Backup & Replication v10.8 Released With New Features

Nakivo has released its new Backup and Replication solution Nakivo v10.8, which includes support for…

2 years ago

Oracle Cloud VMware Solution and Features

Oracle Cloud VMware Solution (OCVS) provides a customer-managed, native VMware-based cloud environment hosted in Oracle…

2 years ago

Vinchin Backup and Recovery Review

Vinchin is a professional provider of data protection solutions for enterprises. It provides a series…

2 years ago

VMware Cloud Disaster Recovery (VCDR) Solution Deployment And Configuration Part 2

In my previous blog post, I have explained about VMware Cloud Disaster Recovery (VCDR) Onboarding and…

2 years ago

How to Deploy vRNI Cloud With VMC on AWS

vRealize Network Insight helps you build an optimized, highly available, and secure network infrastructure across…

2 years ago

This SysAdmin Day, WIN with Hornetsecurity!

Can you believe it's here again? SysAdmin Day is back, and with it comes endless gratitude…

2 years ago