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

Configuration Guide - Network Management and Monitoring

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, NETCONF, OpenFlow, LLDP, NQA, Mirroring, Packet Capture, Packet Trace, Path and Connectivity Detection Configuration, NetStream, sFlow, and iPCA.
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 Basic SNMPv1 Functions

Configuring Basic SNMPv1 Functions

Context

For the configuration of basic SNMP functions, steps 1, 4, 6, 7 and 13 are mandatory. After the configuration is complete, basic SNMP communication can be established between the NMS and managed device.

NOTE:

The community name and port number on the network management side must be the same as those on the device side and the SNMP version used on the NMS must be enabled on the device; otherwise, the NMS cannot connect to the device. If only a write community name is configured on the device, the NMS uses this write community name as the read and write community names.

Procedure

  1. Run system-view

    The system view is displayed.

  2. (Optional) Run snmp-agent

    The SNMP agent is enabled.

    By default, the SNMP agent is disabled. Executing the snmp-agent command can enable the SNMP agent, even if no parameter is specified in the command.

  3. (Optional) Run snmp-agent udp-port port-num

    The port number of the SNMP agent is changed.

    The default port number of the SNMP agent is 161.

    This command enhances device security. After the number of the port on SNMP agent connecting to the NMS is changed, ensure that the port number on the NMS is the same as the changed port number; otherwise, the SNMP agent cannot connect to the NMS.

  4. Run snmp-agent sys-info version v1

    The SNMP version is set to SNMPv1.

    By default, the device supports SNMPv3. After you set the SNMP version to SNMPv1, the device supports both SNMPv1 and SNMPv3, and can be managed by NMSs running SNMPv1 and SNMPv3.

  5. (Optional) Run snmp-agent password min-length min-length

    The minimum length of SNMP password is set.

    By default, the minimum length of SNMP password is 8.

    After this command is run, the lengths of created SNMP community names cannot be shorter than the set value.

  6. Run snmp-agent community { read | write } { community-name | cipher community-name } [ alias alias-name ]

    The community name is set.

    By default, no community name exists in the system. The community name will be saved in encrypted format in the configuration file. To facilitate identification of community names, set the alias names for the communities. The alias names are stored in plain text in the configuration file.

    By default, the device checks complexity of community names. If the check fails, the community name cannot be configured. To ensure the security of SNMP community names, you are advised to refrain from using the snmp-agent community complexity-check disable command to disable community name complexity check.

    The device has the following requirements for community name complexity:

    • The minimum length of a community name is eight characters by default.

    • A community name includes at least two kinds of characters, which can be uppercase letters, lowercase letters, digits, and special characters (excluding question marks and spaces). When double quotation marks are used around the string, spaces are allowed in the string.

    To change the access right of the NMS, see Restricting Management Rights of the NMS. Ensure that the community name of the NMS is the same as that set on the agent; otherwise, the NMS cannot access the agent.

  7. Choose one of the following commands according to your network requirements to configure a destination IP address of the traps and error codes sent from the device.

    NOTE:

    Before configuring a device to send traps, confirm that the information center has been enabled. The information center can be enabled by running the info-center enable command.

    • To configure a destination IPv4 address for the traps and error codes sent from the device.

      Run snmp-agent target-host [ host-name host-name ] trap address udp-domain ip-address [ udp-port port-number | source interface-type interface-number | { vpn-instance vpn-instance-name | public-net } ] * params securityname { security-name | cipher security-name } [ v1 | private-netmanager | ext-vb | notify-filter-profile profile-name | heart-beat enable ] *

    • To configure a destination IPv6 address for the traps and error codes sent from the device.

      Run snmp-agent target-host [ host-name host-name ] trap ipv6 address udp-domain ipv6-address [ udp-port port-number | [ vpn-instance vpn-instance-name | public-net ] ] * params securityname { security-name | cipher security-name } [ v1 | private-netmanager | ext-vb | notify-filter-profile profile-name ] *

    Note the following before running the command:
    • The default destination UDP port number is 162. To ensure secure communication between the NMS and managed devices, run the udp-port command to change the UDP port number to a lesser-known port number.

    • The securityname parameter indicates the devices that send traps. The NMS identifies these devices according to this parameter.

  8. (Optional) Configure the switch to listen on the source interface or source IPv6 address of SNMP request packets sent from the NMS.

    • On an IPv4 network, run the snmp-agent protocol source-interface interface-type interface-number command to configure the interface used to receive SNMP packets from and send SNMP packets to the NMS.

      By default, the interface used to receive SNMP packets from and send SNMP packets to the NMS is not configured.

      After SNMP is bound to the source interface, SNMP listens only this interface, through which the NMS communicates with the device. If the source interface or its IP address is deleted, SNMP will stop receiving IP packets, and therefore communication between the NMS and devices will interrupt. After the source interface's IP address is changed, the NMS can communicate with devices only through the new IP address.

    • On an IPv6 network, run the snmp-agent protocol ipv6 source-ip ipv6-address command to configure the device to listen on the IPv6 addresses of SNMP request packets from the NMS.

      By default, no source IPv6 address is configured. A switch can use any reachable IPv6 address in communication with other devices.

  9. (Optional) Run snmp-agent protocol [ ipv6 ] { vpn-instance vpn-instance-name | public-net }

    A switch is configured to receive and respond to the SNMP request packets from VPN or public network.

    By default, a switch receives and responds to the SNMP request packets from the global VPN instances and public network.

  10. (Optional) Run snmp-agent protocol server [ ipv4 | ipv6 ] disable

    The SNMP IPv4 or IPv6 listening port is disabled.

    By default, the SNMP IPv4 or IPv6 listening port is disabled.

    After you disable the SNMP IPv4 or IPv6 listening port using this command, SNMP no longer processes SNMP packets. Exercise caution when running this command.

  11. (Optional) Run snmp-agent protocol get-bulk timeout time

    The delay after which the device returns information in response to the get-bulk operation of the NMS is set.

    By default, the device returns information 2s after the NMS performs a get-bulk operation.

    The default delay 2s is recommended. If you need to change the value, ensure that the value must be smaller than the timeout interval set on the NMS.

  12. (Optional) Run snmp-agent sys-info { contact contact | location location }

    The device administrator's contact information or location is configured.

    By default, the device administrator's contact information is "R&D Beijing, Huawei Technologies Co.,Ltd." and location is "Beijing China."

    This step is required for the NMS administrator to view contact information and locations of the device administrator when the NMS manages many devices. This helps the NMS administrator to contact the device administrator for fault location and rectification.

  13. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 33907

Downloads: 123

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