| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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.
...
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.
...
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
...
| Note |
|---|
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:
...
| Info |
|---|
NOTE There can be more than one SNMP Communities that can be configured on VEGA but each Manager configured will be subjected to only single community. We can configure at max 10 SNMP Communities. |