No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight V300R010C00SPC200, 300, and 500 Operation Guide 09

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring the SNMP Protocol on Devices

Configuring the SNMP Protocol on Devices

The SNMP protocol is used to add devices to eSight. SNMP parameters on devices must be the same as those on eSight.

  • The alarm management of eSight does not support SNMPv1. To manage device alarms using eSight, you must use SNMPv2c or SNMPv3.
  • SNMPv1 and SNMPv2c are not secure, and may have security risks. You are advised to use the more secure SNMPv3.

The following uses Huawei S5720-52X-PWR-SI-AC V200R011C10 as an example to describe the configuration. For other device models, see the configuration manual.

NOTE:

The commands may differ depending on the device model. When configuring a command, you are advised to enter a question mark (?). The associated command is displayed automatically. The following is an example.

[Device] snmp-agent usm-user v3 snmpv3user ?
  • SNMPv3
    <Device> system-view
    [Device] snmp-agent sys-info version v3
    [Device] snmp-agent mib-view included  View_ALL iso    //View_ALL indicates the name of the MIB view. To ensure that eSight can properly manage devices (for example, discover device links through the LLDP protocol), the MIB view must contain the iso node.
    [Device] snmp-agent group v3 snmpv3group privacy write-view View_ALL notify-view View_ALL   //snmpv3group indicates the configured user group. Set the name of the write view and notification view to View_ALL. By default, the write view has the read permission and you do not need to set read-view. The notification view is used to restrict the MIB node that sends alarms to eSight.
    [Device] snmp-agent usm-user v3 snmpv3user group snmpv3group   //snmpv3user indicates the configured user name, which is the same as the eSight security name. The security level of a user cannot be lower than that of the user group to which the user belongs. Otherwise, the communication fails. For example, if the security level of user group snmpv3group is set to privacy, the security level of user snmpv3user must be authentication and encryption.
    [Device] snmp-agent usm-user v3 snmpv3user authentication-mode sha   //Set the authentication protocol and password of the user, which are the same as those of eSight.
    [Device] snmp-agent usm-user v3 snmpv3user privacy-mode aes128   //Set the encryption protocol and password of the user, which must be the same as those of eSight.
    [Device] snmp-agent trap enable    
    Warning: All switches of SNMP trap/notification will be open. Continue? [Y/N]:Y
    [Device] snmp-agent target-host trap address udp-domain 10.10.10.10 source GigabitEthernet 0/0/1 udp-port 162 params securityname snmpv3user v3 privacy private-netmanager ext-vb  //10.10.10.10 is the IP address of the eSight server. (If the southbound and northbound network isolation solution is used, this IP address is the southbound IP address of eSight.) GigabitEthernet 0/0/1 is the port for reporting device traps. 162 is port number of the trap message. (You are advised not to change the port number. To change the port number, seek for technical support.) securityname is the configured user name. private-netmanager specifies Huawei NMS as the destination host for receiving trap messages. This parameter needs to be configured when Huawei NMS is used. Alarms sent to the NMS can carry more information, including the alarm type, alarm sending sequence, and alarm sending time. ext-vb specifies the alarm sent to the destination host to carry extended binding variables. If alarm nodes defined by the public MIB are extended for Huawei data communication devices, the ext-vb parameter can specify whether the alarm sent to the NMS carries the extended binding variables. If the Huawei NMS tool is used, it is recommended that the ext-vb parameter be used so that the alarm can carry more information. If a third-party NMS tool is used, it is recommended that ext-vb not be used to ensure that the third-party NMS tool can normally receive alarms sent by Huawei data communication devices.
    [Device] snmp-agent packet max-size 12000   //Set the maximum size of an SNMP packet that can be received and sent by the device to 12000 bytes. By default, the maximum size of an SNMP packet is 12000 bytes. Since this parameter may be modified, you need to reset this parameter.
    [Device] snmp-agent local-engineid engineid    //(Optional) Set the engine ID of the local SNMP entity. If the local engine ID is changed, existing SNMPv3 users will be deleted. After engineID is modified, you need to click the update or device information synchronization on the eSight page to manually trigger the alarm. Otherwise, the alarm is not reported.
    [Device] quit
    <Device> save
  • SNMPv2c
    <Device> system-view
    [Device] snmp-agent sys-info version v2c
    [Device] snmp-agent mib-view included View_ALL iso   //View_ALL indicates the name of the MIB view. To ensure that eSight can properly manage devices (for example, discover device links through the LLDP protocol), the MIB view must contain the iso node.
    [Device] snmp-agent community read cipher Public_123 mib-view View_ALL   //Public_123 is the specified read community. The value must be the same as Read community on eSight. 
    [Device] snmp-agent community write cipher Private_123 mib-view View_ALL   //Private_123 is the specified write community. The value must be the same as Write community on eSight.
    [Device] snmp-agent trap enable  
    Warning: All switches of SNMP trap/notification will be open. Continue? [Y/N]:Y
    [Device] snmp-agent target-host trap address udp-domain 10.10.10.10 source GigabitEthernet 0/0/1 udp-port 162 params securityname Public_123 v2c private-netmanager ext-vb  //10.10.10.10 is the IP address of the eSight server. GigabitEthernet 0/0/1 is the port for reporting device traps. 162 is port number of the trap message. (You are advised not to change the port number. To change the port number, seek for technical support.) securityname is the configured read community. private-netmanager specifies Huawei NMS as the destination host for receiving trap messages. This parameter needs to be configured when Huawei NMS is used. Alarms sent to the NMS can carry more information, including the alarm type, alarm sending sequence, and alarm sending time. ext-vb specifies the alarm sent to the destination host to carry extended binding variables. If alarm nodes defined by the public MIB are extended for Huawei data communication devices, the ext-vb parameter can specify whether the alarm sent to the NMS carries the extended binding variables. If the Huawei NMS tool is used, it is recommended that the ext-vb parameter be used so that the alarm can carry more information. If a third-party NMS tool is used, it is recommended that ext-vb not be used to ensure that the third-party NMS tool can normally receive alarms sent by Huawei data communication devices.
    [Device] snmp-agent packet max-size 12000   //Set the maximum size of an SNMP packet that can be received and sent by the device to 12000 bytes. By default, the maximum size of an SNMP packet is 12000 bytes. Since this parameter may be modified, you need to reset this parameter.
    [Device] quit
    <Device> save
  • SNMPv1
    <Device> system-view
    [Device] snmp-agent sys-info version v1
    [Device] snmp-agent mib-view included View_ALL iso   //View_ALL indicates the name of the MIB view. To ensure that eSight can properly manage devices (for example, discover device links through the LLDP protocol), the MIB view must contain the iso node.
    [Device] snmp-agent community read cipher Public_123 mib-view View_ALL   //Public_123 is the specified read community. The value must be the same as Read community on eSight. 
    [Device] snmp-agent community write cipher Private_123 mib-view View_ALL   //Private_123 is the specified write community. The value must be the same as Write community on eSight.
    [Device] snmp-agent trap enable
    Warning: All switches of SNMP trap/notification will be open. Continue? [Y/N]:Y
    [Device] snmp-agent target-host trap address udp-domain 10.10.10.10 source GigabitEthernet 0/0/1 udp-port 162 params securityname Public_123 v1 private-netmanager ext-vb  //10.10.10.10 is the IP address of the eSight server. GigabitEthernet 0/0/1 is the port for reporting device traps. 162 is port number of the trap message. (You are advised not to change the port number. To change the port number, seek for technical support.) securityname is the configured read community. private-netmanager specifies Huawei NMS as the destination host for receiving trap messages. This parameter needs to be configured when Huawei NMS is used. Alarms sent to the NMS can carry more information, including the alarm type, alarm sending sequence, and alarm sending time. ext-vb specifies the alarm sent to the destination host to carry extended binding variables. If alarm nodes defined by the public MIB are extended for Huawei data communication devices, the ext-vb parameter can specify whether the alarm sent to the NMS carries the extended binding variables. If the Huawei NMS tool is used, it is recommended that the ext-vb parameter be used so that the alarm can carry more information. If a third-party NMS tool is used, it is recommended that ext-vb not be used to ensure that the third-party NMS tool can normally receive alarms sent by Huawei data communication devices.
    [Device] snmp-agent packet max-size 12000   //Set the maximum size of an SNMP packet that can be received and sent by the SNMP Agent to 12000 bytes. By default, the maximum size of an SNMP packet is 12000 bytes. Since this parameter may be modified, you need to reset this parameter.
    [Device] quit
    <Device> save
Translation
Download
Updated: 2019-09-12

Document ID: EDOC1100044378

Views: 72660

Downloads: 378

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next