Configure SNMP v1/v2c Proxy Server
Network Requirements
- Device is the SNMP Agent device and the route with the NMS server is reachable.
- NMS monitors and manages Device via SNMP v1 or SNMP v2c; when Device fails, it actively reports to NMS.
Network Topology
![Networking of configuring SNMP v1/v2c proxy server](/storage/images/Document/Maipu/monitoring/config-snmp-v1-proxy-server.jpg)
Figure 8-3 Networking of configuring SNMP v1/v2c proxy server
Configuration Steps
Step 1: Configure VLAN and add the port to the corresponding VLAN. (Omitted)
Step 2: Configure the IP address of the interface. (Omitted)
Step 3: Enable the SNMP proxy on Device and configure the SNMP community name.
#Configure Device.
Enable the SNMP proxy; configure the node view name as default, read-only community name as public and read-write community name as public.
Device#configure terminal
Device(config)#snmp-server start
Device(config)#snmp-server view default 1.3.6.1 include
Device(config)#snmp-server community public view default ro
Device(config)#snmp-server community public view default rw
|
Step 4: Configure Device to send the Trap packets to the network work station (NMS) actively and use the community name public.
#Configure Device.
Device(config)#snmp-server enable traps
Device(config)#snmp-server host 129.255.140.1 traps community public version 2
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
The SNMP version specified in the snmp-server host command should be consistent with the SNMP version running on NMS.
Step 5: Configure NMS.
#On the NMS using SNMP v1/v2c, we need to set “read-only community name” and “read- write community name”. Besides, we also need to set “timeout” and “re-try times”. The user queries and configures the device via the NMS.
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
When using the read-only community name, the user can only query the device via NMS.
- When using the read-write community name, the user can query and configure the device via NMS.
Step 6: Check the result.
#NMS can query and configure some parameters of Device via the MIB node. NMS can receive various Trap information from Device, such as interface up, down of Device, the route change caused by the network oscillation. Device generates the corresponding Trap information and sends to NMS.