How to interconnect S series switches with an NMS using SNMP

3

S series switches can be managed by an NMS.
When an NMS is used to manage S series switches, the following conditions must be met:
1. The switches and NMS are reachable to each other.
2. SNMP functions are configured on the switches.
3. The SNMP versions used on the switches are selected on the NMS. When SNMPv1 and SNMPv2c are used, only community names need to be configured. When SNMPv3 is used, the user group, user name, authentication mode, authentication password, encryption mode, and encryption password must be configured.

Other related questions:
How can I configure an S series switch running SNMP to send traps to an NMS
You can run the snmp-agent target-host trap command to configure an S series switch (except the S1700) running SNMP to send traps to a specified NMS. Example: 1. SNMPv1 [HUAWEI] snmp-agent target-host trap address udp-domain 10.1.1.1 params securityname huawei123 v1 2. SNMPv2c [HUAWEI] snmp-agent target-host trap address udp-domain 10.1.1.1 params securityname huawei123 v2c 3. SNMPv3 [HUAWEI] snmp-agent target-host trap address udp-domain 10.1.1.1 params securityname huawei123 v3 Note: For SNMPv3, securityname in the command must be configured as the user name on the NMS and switch running SNMP. The NMS can receive traps from a switch running SNMP only after passing the securityname verification (including authentication and encryption modes). For SNMPv1 and SNMPv2c, the NMS can receive traps from all switches running SNMP without verifying the securityname parameter. securityname is used to distinguish multiple switches running SNMP that send traps.

How can I obtain switch configurations through an NMS when the IP address of the NMS is on a VPN
Solution When an NMS manages a switch through a VPN, switch management information needs to be sent to the NMS through a VPN instance. You can run the set net-manager vpn-instance command to configure the default VPN instance for the NMS to manage the switch so that the switch can use this VPN instance to communicate with the NMS. Precautions - Before running this command, ensure that a VPN instance has been created successfully on the switch. - After this command is configured, commands that you have configured for file transfers over FTP, TFTP, or SFTP only take effect in the default VPN instance. - If the switch has been configured as a log host, the NMS can receive logs from the switch through the default VPN instance.

SNMP configuration on S series switch
S series switches (except S1700 switches) support three SNMP versions: SNMPv1, SNMPv2c, and SNMPv3. SNMPv1 and SNMPv2c use community names for authentication, resulting in low security, whereas SNMPv3 uses authentication and encryption technologies to enhance security. The following uses SNMPv2c configuration as an example: [HUAWEI] snmp-agent //Enable SNMP. [HUAWEI] snmp-agent sys-info version v2c //Set the SNMP version to SNMPv2c. [HUAWEI] snmp-agent community write adminnms01 //Set the SNMP write community name. For common SNMP configuration information, see "Common SNMP Operations" in S1720&S2700&S3700&S5700&S6700&S7700&S9700 Series Switches Common Operation Guide. For typical SNMP configuration examples, see "Typical SNMP Configuration" in "Typical Network Management and Monitoring Configuration" of S1720&S2700&S3700&S5700&S6700&S7700&S9700 Typical Configuration Examples. Common configuration and typical configuration examples for S9300 and S12700 series switches are the same as those for Sx700 series switches. The Sx700 series switches are used as an example here.

S series switch SNMP OID
A Management Information Base (MIB) is a database that stores the variables (information that can be queried and set by the agent) on managed devices A MIB defines the attributes of managed devices, including name, status, access permission, and data type. MIB stores information using a tree structure. The leaf nodes of the tree are managed objects (MOs). An MO is identified by the set of nodes along the path from the root to the leaf node. Such a path is called object identifier (OID). An OID consists of positive integers and zero, and it is used to uniquely identify an MO in the MIB. For example, an SNMP object can be identified as { iso(1).org(3).dod(6).internet(1).snmpV2(6) }, which can be simplified to 1.3.6.1.6. The identifier is called an OID.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top