...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Panel | ||
|---|---|---|
| ||
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.
...
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:
...