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

Troubleshooting Guide

CloudEngine 16800, 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches

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).
Why Does an SNMP MIB Operation Performed by the NMS Not Take Effect on a Device?

Why Does an SNMP MIB Operation Performed by the NMS Not Take Effect on a Device?

Assume that the NMS has set up an SNMP connection with a device and then operates on an SNMP MIB object. If the operation does not take effect on the device, the SNMP MIB object is not included in the MIB objects that the NMS can access. To check the MIB objects that the NMS can access, perform the following steps:

  1. Check the SNMP configuration on the device.

    <HUAWEI> display current-configuration configuration snmp-agent
    #
    snmp-agent
    snmp-agent local-engineid 800007DB03200BC7391301
    snmp-agent community write cipher %^%#M(VE75y$]*r&h\Q2ZE96~,\#PThr[Y_5;}9zfoHSUDHF(vI^u-e"xp8F/Q65xGE\2#W%hU^,d`(V,Du#%^%# mib-view allextisis acl 2001
      //Configure the rights that the SNMPv1 or SNMPv2c community name has on a MIB view.
    #
    snmp-agent sys-info version all
    snmp-agent group v3 admin privacy write-view allextisis acl 2001  //Configure the rights that the SNMPv3 user group has on a MIB view.
    #
    snmp-agent mib-view excluded allextisis isisMIB  //Create a MIB view, and specify the MIB objects that the NMS can monitor and manage.
    snmp-agent usm-user v3 nms2-admin
    snmp-agent usm-user v3 nms2-admin group admin
    snmp-agent usm-user v3 nms2-admin authentication-mode sha cipher %^%#p$(+$9#z/CbPuu,=4N9I9l0=BRSi{FZyfl"nFInU%^%#
    snmp-agent usm-user v3 nms2-admin privacy-mode aes128 cipher %^%#%UhCY<o`oH(.eq=/}G;'z}cT>@9Nw=)Z;J(iHA7-%^%#

    If no MIB view is specified in the SNMP community name configuration, the MIB objects that the NMS can access are restricted within the ViewDefault view. If no read-only MIB view is specified using the read-view parameter in the SNMP user group configuration, the MIB objects that the NMS can access (with read-only access granted) are restricted within the ViewDefault view. If no read-write MIB view is specified using the write-view parameter in the SNMP user group configuration, the NMS cannot write data into the device through the MIB.

    The ViewDefault view includes sub-objects except snmpVacmMIB, snmpUsmMIB, and snmpCommunityMIB under the internet object.

    For details about the SNMP access rights of the NMS, see How Can I Restrict SNMP Access Rights of NMSs?.

  2. Check whether the MIB object operated by the NMS is included in the MIB objects that the NMS can access. If not, reconfigure the MIB view. If so, contact technical support personnel.

Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 616549

Downloads: 2965

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next