SNMP protocol version

SNMP agents support three SNMP protocol versions: SNMPv1, SNMPv2c, and SNMPv3.

∙SNMPv1 uses community names for authentication. A community name performs a similar role as a password to regulate access from the NMS to the agent. If the community name provided by the NMS is different from the community name set on the agent, the SNMP connection cannot be established and the NMS fails to access the agent.

∙SNMPv2c uses community names for authentication. SNMPv2c is compatible with SNMPv1, but it provides more operation modes, supports more data types, and provides various error codes for troubleshooting.

∙SNMPv3 offers authentication based on the User-based Security Model (USM), which allows network administrators to set authentication and privacy functions. The authentication function is used to authenticate the validity of the sending end of the authentication packets, preventing access of unauthorized users. The privacy function is used to encrypt packets between the NMS and agents, preventing the packets from being intercepted. USM ensures more secure communication between NMSs and agents by providing authentication and privacy functions.

Successful interaction between an NMS and the agents requires consistency of SNMP versions configured on them.

SNMP configuration

Configuration task list

As configurations for SNMPv3 differ substantially from those for SNMPv1 and SNMPv2c, their configuration tasks are introduced separately as follows.

Configuring SNMPv1 or SNMPv2c

Perform the tasks in 1 to configure SNMPv1 or SNMPv2c:

1.SNMPv1 or SNMPv2c configuration task list

Task

Remarks

 

Required

Enabling SNMP

The SNMP agent function is disabled by default.

IMPORTANT:

 

 

If SNMP is disabled, all SNMP-related configurations are removed.

 

Optional

Configuring an SNMP

After creating SNMP views, you can specify an SNMP view for an

SNMP community to limit the MIB objects that can be accessed by the

 

 

SNMP community.

 

 

Configuring an SNMP

Required

 

 

116