Got it

The MIB OID cannot be read

Created: Dec 30, 2019 10:37:50Latest reply: Dec 30, 2019 10:38:06 249 1 0 0 0
  Rewarded HiCoins: 0 (problem resolved)

Hello, everyone.

After the S5700S-52P-LI is upgraded from V200R003 to V200R007, the MIB object 1.3.6.1.2.1.17.7.1.4.3.1.1 cannot be read.

In V200R007, the following information is obtained by snmpwalk

1.3.6.1.2.1.17.7.1.4.3.1

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2369 = ""

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2370 = ""

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2371 = ""

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2372 = ""

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2373 = ""

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2374 = ""

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2375 = ""

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2376 = ""

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2377 = ""

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2378 = ""

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2379 = ""

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.2380 = "":

In V200R003, the obtained MIB information is as follows:

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.1 = STRING: "VLAN 0001"

SNMPv2-SMI::mib-2.17.7.1.4.3.1.1.300 = STRING: "VLAN 0300"

SNMPv2-SMI::mib-2.17.7.1.4.3.1.2.1 = Hex-STRING: 7E E7 FB C0 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00

SNMPv2-SMI::mib-2.17.7.1.4.3.1.2.300 = Hex-STRING: 01 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00

SNMPv2-SMI::mib-2.17.7.1.4.3.1.3.1 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00

Please tell me the cause of the problem. Thank you!


  • x
  • convention:

Featured Answers
DDSN
Admin Created Dec 30, 2019 10:38:06

Hi, Qazik.
In earlier versions, the value of dot1qVlanStaticName does not comply with the RFC definition. In the target version, the value of dot1qVlanStaticName is changed to the VLAN name. In this case, use the VLAN name to configure the description. The object can be read normally. Thank you.
View more
  • x
  • convention:

All Answers
DDSN
DDSN Admin Created Dec 30, 2019 10:38:06

Hi, Qazik.
In earlier versions, the value of dot1qVlanStaticName does not comply with the RFC definition. In the target version, the value of dot1qVlanStaticName is changed to the VLAN name. In this case, use the VLAN name to configure the description. The object can be read normally. Thank you.
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.