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 12800 and 12800E V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, LLDP, NQA, Service Diagnosis, Mirroring, Packet Capture, sFlow, and NETCONF.
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).
(Optional) Restricting Management Rights of the NMS

(Optional) Restricting Management Rights of the NMS

Context

When multiple NMSs in the same SNMPv3 user group manage one device, perform this configuration according to the scenario.

Scenario

Steps

The NMSs access the ViewDefault view.

No action required

1, 2, 8 (NMS filtering based on SNMP agent)

1, 3, 5, 8 (NMS filtering based on user group)

1, 6, 7, 8 (NMS filtering based on user)

1, 3, 5, 6, 7, 8 (NMS filtering based on user group and user)

1, 2, 3, 5, 8 (NMS filtering based on SNMP agent and user group)

1, 2, 6, 7, 8 (NMS filtering based on SNMP agent and user)

1, 2, 3, 5, 6, 7, 8 (NMS filtering based on SNMP agent, user group, and user)

The NMSs access the specified objects on the managed device.

1, 4, 5, 8

1, 2, 4, 5, 8 (NMS filtering based on SNMP agent)

1, 3, 4, 5, 8 (NMS filtering based on user group)

1, 4, 5, 6, 7, 8 (NMS filtering based on user)

1, 3, 4, 5, 6, 7, 8 (NMS filtering based on user group and user)

1, 2, 3, 4, 5, 8 (NMS filtering based on SNMP agent and user group)

1, 2, 4, 5, 6, 7, 8 (NMS filtering based on SNMP agent and user)

1, 2, 3, 4, 5, 6, 7, 8 (NMS filtering based on SNMP agent, user group, and user)

The following describes how an ACL is used to control the access rights of NMSs:
  • When the ACL rule is permit, the NMS with the source IP address specified in this rule can access the local device.

  • When the ACL rule is deny, the NMS with the source IP address specified in this rule cannot access the local device.

  • If a packet does not match any ACL rule, the NMS that sends the packet cannot access the local device.

  • When no ACL rule is configured, all NMSs can access the local device.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Configure NMS filtering based on SNMP agent.
    1. Configure the basic ACL.

      Before configuring the access control rights, you must create a basic ACL. For instructions on how to create an ACL, see "ACL Configuration" in the CloudEngine 12800 and 12800E Series Switches Configuration Guide-Security.

    2. Run the snmp-agent acl { acl-number | acl-name } command to configure an ACL for SNMP.

      By default, access control is unavailable for SNMP.

  3. Configure a basic ACL for an SNMP user group to allow only the NMS matching the ACL to access the managed device.

    For instructions on how to create an ACL, see "ACL Configuration" in the CloudEngine 12800 and 12800E Series Switches Configuration Guide-Security.

  4. Run snmp-agent mib-view { excluded | included } view-name oid-tree

    A MIB view is created, and manageable MIB objects are specified.

    By default, an NMS has right to access the objects in the ViewDefault view.

    The excluded and included parameters are applicable to the following scenarios:

    • excluded: If a few MIB objects on the device or some objects in the current MIB view do not or no longer need to be managed by the NMS, specify excluded in the command to exclude these MIB objects.

    • included: If a few MIB objects on the device or some objects in the current MIB view need to be managed by the NMS, specify included in the command to include these MIB objects.

    You can run this command multiple times. If it is run multiple times and the values of view-name and oid-tree are the same each time, the new configuration overwrites the original configuration. In contrast, if the values of view-name and oid-tree are different, the new and original configurations both take effect.

    If both the included and excluded parameters are configured for MIB objects that have an inclusion relationship, whether the lowest MIB object is included or excluded depends on the parameter configured for it. For example, the snmpV2, snmpModules, and snmpUsmMIB objects have a top-down inclusion relationship in the MIB tree. If the excluded parameter is configured for snmpUsmMIB objects and included is configured for snmpV2, snmpUsmMIB objects will still be excluded.

  5. Run snmp-agent group v3 group-name { authentication | privacy | noauthentication } [ read-view read-view | write-view write-view | notify-view notify-view ] * [ acl { acl-number | acl-name } ]

    The write-read right is configured for a user group.

    By default, the read-only view of an SNMP user group is the ViewDefault view, and the names of the read-write view and inform view are not specified.

    To configure the NMS to receive traps or informs specified by notify-view, you must first configure a target host for receiving traps.

  6. Configure a basic ACL for an SNMP user to allow only the NMS matching the ACL to access the managed device.

    For instructions on how to create an ACL, see "ACL Configuration" in the CloudEngine 12800 and 12800E Series Switches Configuration Guide-Security.

  7. Run snmp-agent usm-user v3 user-name [ group group-name | acl { acl-number | acl-name } ] *

    Authentication and encryption are configured for SNMPv3 users in the specified user group.

    • To allow all NMSs using the same SNMPv3 user name to access the agent, do not specify the acl parameter.

    • To allow only the specified NMSs using this user name to access the agent, configure the acl parameter.

  8. Run commit

    The configuration is committed.

Follow-up Procedure

If the NMS allowed to access the managed device changed its IP address for some reasons, for example, there is a location change or IP address reallocation, change the IP address in the ACL rule accordingly; otherwise, the NMS cannot access the managed device.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075344

Views: 28496

Downloads: 29

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