SNMP Configuration and Troubleshooting
THIS DOCUMENT PROVIDES INFORMATION WITH RESPECT TO SNMP CONFIGURATION ON VEGA AND TO PERFORM SNMP TROUBLESHOOTING
VEGA act as SNMP Agent as it collects the management information database from the device locally and makes it available to the SNMP manager, when it is queried for. It stores and retrieves management information as defined in the MIB.Â
Also signals an event to the manager in form of traps when required.
Configuration
SNMP configuration VEGA can easily be achieved from VEGA GUI.
All SNMP relates configuration is present within VEGA GUI > Expert Config > Logging > SNMP as shown below:
SNMP configuration on VEGA can mainly be divided in to three different parts:
General SNMP Configuration
SNMP Manager Configuration
SNMP Communities Configuration
General SNMP Configuration
As the name suggest there are the general SNMP configuration that is must to be configured in order to use SNMP.
There are mainly four General SNMP Configuration:
LAN Profile
LAN Profile as present within SNMP configuration section is configured in order to tell vega which lan profile need to be used in order to establish connection between VEGA (SNMP Agent) and SNMP ManagerPassword
This mainly configures the device password i.e. required for authentication in case of SNMPv3Contact
This mainly configures the location of the device i.e. VEGA.Location
This mainly configures the location of the device i.e. VEGA
General SNMP Configuration is shown as given below:
VEGA GUI > Expert Config > Logging > SNMP > SNMP Configuration
SNMP Managers Configuration
As the name suggest this configuration is mainly with respect to SNMP Manager that needs to be configured for VEGA
There are mainly four SNMP Manager Configuration:
IP
This mainly configures the ip of the SNMP Manager. It is configured to restrict SNMP services only to this IP address.Subnet
This mainly configures the mask to identify significant part of manager’s IP address to check.Community
This mainly configures the community name that is used by SNMPv3/SNMPv2c/SNMPv1.Support snmpV3
This mainly enable/disable support for SNMPv3 on VEGA.
Â
Important Note
VEGA SNMPv3 will only work if authentication and privacy is not enable.
SNMP Managers Configuration is shown as given below:
VEGA GUI > Expert Config > Logging > SNMP > SNMP Managers
NOTE
There can be more than one SNMP Managers that can be configured on VEGA. We can configure at max 10 SNMP managers.
SNMP Communities Configuration
As the name suggest this mainly configures the communities as used by different SNMP version i.e. SNMPv1/SNMPv2c/SNMPv3.
SNMPv1 and SNMPv2 use communities to establish trust between managers and agents. Most agents support three community names, one each for read-only, read-write and trap.Â
These three community strings control different types of activities.
The read-only community applies to get requests.
The read-write community string applies to set requests.
The trap community string applies to receipt of traps.Â
SNMPv3 also uses community strings, but allows for secure authentication and communication between SNMP manager and agent
There are mainly four SNMP Communities Configuration:
Name
This mainly configures the community name that is used by SNMP ManagerGet
This mainly configured the get command/read permission for that community i.e. if this configuration is set then SNMP Manager using its respective community is allowed to get response for SNMP Get/read command.Set
This mainly configured the set command/write permission for that community i.e. if this configuration is set then SNMP Manager using its respective community is allowed to get response for SNMP Set/write command.Traps
This mainly configured the traps/indication permission for that community i.e. if this configuration is set then SNMP Agent i.e. VEGA is allowed to send traps/indication to its respective SNMP manager.
SNMP Communities Configuration is shown as given below:
VEGA GUI > Expert Config > Logging > SNMP > SNMP Communities
Â