SNMP Features Supported by the Device
This section compares SNMP versions in terms of their support for features and usage scenarios to provide a reference for your SNMP version selection during network deployment.
The device supports SNMPv1, SNMPv2c, and SNMPv3. Table 1-1 lists the features supported by SNMP, and Table 1-2 shows the support of different SNMP versions for the features. Table 1-3 describes the usage scenarios of SNMP versions, which helps you choose a proper version for the communication between an NMS and managed devices based on the network operation conditions.
When multiple NMSs using different SNMP versions manage the same device in a network SNMPv1, SNMPv2c, and SNMPv3 are configured on the device for its communication with all the NMSs.
Feature |
Description |
|---|---|
Access control |
This function is used to restrict a user's device administration rights. It gives specific users the rights to manage specified objects on devices and therefore provides fine management. |
Authentication and privacy |
The authentication and privacy packets are transmitted between the NMS and managed devices. This prevents data packets from being intercepted or modified, improving data sending security. |
Error code |
Error codes help the administrator to identify and rectify faults. It is easy for the administrator to manage the device if the error codes are more with variety. |
Trap |
Traps are sent from managed devices to the NMS. Traps help administrator to know device faults. The managed devices do not require the acknowledgement from the NMS after sending traps. |
Inform |
Informs are sent from managed devices to the NMS. The managed devices require the acknowledgement from the NMS after sending informs. If a managed device does not receive an acknowledgement after sending an inform. |
GetBulk |
GetBulk allows an administrator to perform Get-Next operations in batches. In a large network, GetBulk reduces the workload of administrator and improves management efficiency. |
After the restart, the NMS can receive the informs that are sent during the restart.
Feature |
SNMPv1 |
SNMPv2c |
SNMPv3 |
|---|---|---|---|
Access control |
Access control based on the community name and MIB view |
Access control based on the community name and MIB view |
Access control based on the user, user group, and MIB view |
Authentication and privacy |
Authentication based on the community name |
Authentication based on the community name |
Supported authentication and privacy modes are as follows: Authentication mode:
Encryption
mode:
|
Error code |
6 error codes supported |
16 error codes supported |
16 error codes supported |
Trap |
Supported |
Supported |
Supported |
Inform |
Not supported |
Supported |
Not supported |
GetBulk |
Not supported |
Supported |
Supported |
Version |
Usage Scenario |
|---|---|
SNMPv1 |
This version is applicable to small-scale networks whose networking is simple and security requirements are low or whose security and stability are good, such as campus networks and small enterprise networks. |
SNMPv2c |
This version is applicable to medium and large-scale networks whose security requirements are not strict or whose security is good (for example, VPNs) but whose services are so busy that traffic congestion may occur. Use inform to ensure the messages sent from managed devices are received by the NMS. |
SNMPv3 |
This version is applicable to networks of various scales, especially the networks that have strict requirements on security and can be managed only by authorized administrators. For example, data between the NMS and managed device needs to be transmitted over a public network. |
If you plan to build a network, choose an SNMP version based on your usage scenario. If you plan to expand or upgrade an existing network, choose an SNMP version to match the SNMP version running on the NMS to ensure the communication between managed devices and the NMS.