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

CLI-based Configuration Guide - Network Management and Monitoring

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the basic concepts, configuration procedures, and configuration examples in different application scenarios of the network management feature supported by the device.
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 using the same community name manage one device, perform this configuration based on the site requirements.

Scenario

Steps

All NMSs using this community name access the ViewDefault view.

No action required

Only the specified NMSs using this community name access the ViewDefault view.

1, 3

All NMSs using this community name access the specified objects on the managed device.

1, 2, 3

Only the specified NMSs using this community name access the specified objects on the managed devices.

1, 2, 3

The NMS can connect to only the specified physical interfaces on the managed device.

1, 4

NOTE:

The ViewDefault view are the 1.3.6.1 view and 1.2.840.10006.300.43 view.

When an ACL is used to control the NMS access rights, the constraints are as follows:
  • 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 an 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. Run snmp-agent mib-view view-name { exclude | include } subtree-name [ mask mask ]

    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.

    If both the included and excluded parameters are configured for MIB objects that have an inclusion relationship, whether to include or exclude the lowest MIB object will be determined by the parameter configured for the lowest MIB object. For example, the snmpV2, snmpModules, and snmpUsmMIB objects are from top down in the MIB table. If the excluded parameter is configured for snmpUsmMIB objects and included is configured for snmpV2, snmpUsmMIB objects will still be excluded.

  3. Configure NMS filtering based on community name.
    1. (Optional) Configure the basic ACL.

      Before configuring the access control rights, you must create a basic ACL. For the creation procedure, see "ACL Configuration" in the Huawei AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600 Series Enterprise Routers Configuration Guide-Security.

    2. Run the snmp-agent community { read | write } community-name [ mib-view view-name | acl acl-number ] * command to specify the NMS's access right.

      By default, the created community name allows the NMS to access the ViewDefault view.

      • To grant only the read permission to low-level administrators, specify the parameter read. To grant the read and write permissions to high-level administrators, specify the parameter write.

      • If the NMSs using this community name can access the ViewDefault view, the parameter mib-view view-name is not required.

      • If all NMSs using this community name manage specified objects on the managed devices, the acl acl-number parameter is not required.

      • If some NMSs using this community name manage specified objects on the managed devices, the acl and mib-view parameters must be configured.

      NOTE:

      If both community name and ACL are configured, the NMS checks the community name and then the ACL before accessing the device.

  4. Run snmp-agent permit interface { interface-type interface-number } &<1-5>

    Physical interfaces on the device to which the NMS can connect are specified.

    By default, the NMS can connect to all the physical interfaces on the device.

Follow-up Procedure

After the access right is configured, especially after the IP address of the NMS is specified, if the IP address changes (for example, the NMS changes its location, or IP addresses are reallocated due to network adjustment), you need to change the IP address of the NMS in the ACL. Otherwise, the NMS cannot access the device.

Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100069336

Views: 30398

Downloads: 177

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