Got it

MIB node set failure

Created: Apr 20, 2021 11:21:03Latest reply: Jan 26, 2022 12:30:46 564 3 0 0 0
  HiCoins as reward: 0 (problem unresolved)

Hello,

During the weekly backup of config on the eSight, we find the error of 'MIB node set failure' for some of the switch S5700-28P-PWR-LI-ACs in the network. Although the weekly backup is successful, the error is still found in the diagnostic. Please have a look below for reference. 

Please help to resolve this issue.

 

Apr 18 2021 01:01:21+08:00 S57-C1 %SNMP/4/SNMP_MIB_SET(s)[6]:MIB node set.(UserName=%^%#TNm7-IB#bJ7=nW'Vu4]:]C:-RE"j|OMGYDNil,B1"oM_V(kVM=.iK!V4i.b~n2#T=0Ll-F0BEx(eFyq<%^%#,SourceIP=10.1.1.3, Version=v2c, RequestId=524825139, hwCfgOperateType.87591=6,hwCfgOperateProtocol.87591=3,hwCfgOperateFileName.87591=[63.6f.6e.66.69.67.66.69.6c.65.2f.53.35.37.30.30.2d.32.38.50.2d.50.57.52.2d.4c.49.2d.41.43.2f.31.30.2e.33.2e.31.2e.32.35.30.2f.32.30.32.30.30.35.31.31.30.31.30.31.32.31.53.2e.7a.69.70(hex)], hwCfgOperateServerAddress.87591=10.1.1.3,hwCfgOperateUserName.87591=[61.64.6d.69.6e (hex)],hwCfgOperateUserPassword.87591=******, hwCfgOperateServerPort.87591=31922,hwCfgOperateRowStatus.87591=4, VPN= )

Apr 18 2021 01:01:20+08:00 S57-C1%SNMP/4/SNMP_MIB_SET_FAILED(s)[7]:MIB node set failure.(UserName=%^%#TNm7-IB#bJ7=nW'Vu4]:]C:-RE"j|OMGYDNil,B1"oM_V(kVM=.iK!V4i.b~n2#T=0Ll-F0BEx(eFyq<%^%#,SourceIP=10.1.1.3, Version=v2c, RequestId=524825124, ErrorStatus=12,ErrorIndex=3, hwCfgOperateType.57748=6, hwCfgOperateProtocol.57748=3,hwCfgOperateFileName.57748=[63.6f.6e.66.69.67.66.69.6c.65.2f.53.35.37.30.30.2d.32.38.50.2d.50.57.52.2d.4c.49.2d.41.43.2f.31.30.2e.33.2e.31.2e.32.35.30.2f.32.30.32.30.30.35.31.31.30.31.30.31.32.30.53.2e.63.66.67(hex)], hwCfgOperateServerAddress.57748=10.1.1.3,hwCfgOperateUserName.57748=[61.64.6d.69.6e (hex)],hwCfgOperateUserPassword.57748=******, hwCfgOperateServerPort.57748=31922,hwCfgOperateRowStatus.57748=4, VPN= )

Apr 18 2021 01:01:20+08:00 S57-C1 %SNMP/4/SNMP_MIB_SET(s)[8]:MIB node set.(UserName=%^%#TNm7-IB#bJ7=nW'Vu4]:]C:-RE"j|OMGYDNil,B1"oM_V(kVM=.iK!V4i.b~n2#T=0Ll-F0BEx(eFyq<%^%#,SourceIP=10.1.1.3, Version=v2c, RequestId=524825124, hwCfgOperateType.57748=6,hwCfgOperateProtocol.57748=3, hwCfgOperateFileName.57748=[63.6f.6e.66.69.67.66.69.6c.65.2f.53.35.37.30.30.2d.32.38.50.2d.50.57.52.2d.4c.49.2d.41.43.2f.31.30.2e.33.2e.31.2e.32.35.30.2f.32.30.32.30.30.35.31.31.30.31.30.31.32.30.53.2e.63.66.67(hex)], hwCfgOperateServerAddress.57748=10.1.1.3,hwCfgOperateUserName.57748=[61.64.6d.69.6e (hex)],hwCfgOperateUserPassword.57748=******, hwCfgOperateServerPort.57748=31922,hwCfgOperateRowStatus.57748=4, VPN= )

Apr 18 2021 01:01:20+08:00 S57-C1 %SNMP/4/SNMP_MIB_SET_FAILED(s)[40]:MIB node set failure..(UserName=%^%#TNm7-IB#bJ7=nW'Vu4]:]C:-RE"j|OMGYDNil,B1"oM_V(kVM=.iK!V4i.b~n2#T=0Ll-F0BEx(eFyq<%^%#,SourceIP=10.11.1.3, Version=v2c, RequestId=1313701076, ErrorStatus=13,ErrorIndex=8, hwCfgOperateType.4721=3, hwCfgOperateProtocol.4721=3,hwCfgOperateFileName.4721=[63.6f.6e.66.69.67.66.69.6c.65.2f.53.35.37.30.30.2d.32.38.50.2d.50.57.52.2d.4c.49.2d.41.43.2f.31.30.2e.33.2e.31.2e.32.35.30.2f.32.30.32.30.30.35.30.34.30.30.30.31.30.32.52.2e.63.66.67(hex)], 

Featured Answers

Recommended answer

Popeye_Wang
Admin Created Apr 20, 2021 11:28:03

Hi,

From the logs, we can see there are two types of error for the MIB node failure. All the error occurred when the NMS Server backup device configuration file.

1. ErrorStatus=12, ErrorIndex=3

When the NMS Server backup the device file, the NMS server will deliver a task to the device and the device will use the MIB node to backup the file then send it to NMS Server. But due to frequent backup operation on NMS Server causing the device to exist the same task, appear this issue.

Apr 18 2021 01:01:20+08:00 S57-C1%SNMP/4/SNMP_MIB_SET_FAILED(s)[7]:MIB node set failure.(UserName=%^%#TNm7-IB#bJ7=nW'Vu4]:]C:-RE"j|OMGYDNil,B1"oM_V(kVM=.iK!V4i.b~n2#T=0Ll-F0BEx(eFyq<%^%#,SourceIP=10.1.1.3, Version=v2c, RequestId=524825124, ErrorStatus=12,ErrorIndex=3,

 

2. ErrorStatus=13, ErrorIndex=8

This means the CFG module of the device is busy, also due to frequent backup operation on NMS Servercausing device don’t finish the previous backup task and new task come from NMSServer, so appear this failure(device only can do one backup at the same time).

Apr 18 2021 01:01:20+08:00 S57-C1 %SNMP/4/SNMP_MIB_SET_FAILED(s)[40]:MIB node set failure..(UserName=%^%#TNm7-IB#bJ7=nW'Vu4]:]C:-RE"j|OMGYDNil,B1"oM_V(kVM=.iK!V4i.b~n2#T=0Ll-F0BEx(eFyq<%^%#,SourceIP=10.11.1.3, Version=v2c, RequestId=1313701076, ErrorStatus=13,ErrorIndex=8,


Therefore, please changes the server backup settings. Backups can be performed once a day at most. Typically, we set up a one-week backup.

And if there are several NMS Server, you need to set different backup times periodically.


View more
  • x
  • convention:

All Answers

Hi,

From the logs, we can see there are two types of error for the MIB node failure. All the error occurred when the NMS Server backup device configuration file.

1. ErrorStatus=12, ErrorIndex=3

When the NMS Server backup the device file, the NMS server will deliver a task to the device and the device will use the MIB node to backup the file then send it to NMS Server. But due to frequent backup operation on NMS Server causing the device to exist the same task, appear this issue.

Apr 18 2021 01:01:20+08:00 S57-C1%SNMP/4/SNMP_MIB_SET_FAILED(s)[7]:MIB node set failure.(UserName=%^%#TNm7-IB#bJ7=nW'Vu4]:]C:-RE"j|OMGYDNil,B1"oM_V(kVM=.iK!V4i.b~n2#T=0Ll-F0BEx(eFyq<%^%#,SourceIP=10.1.1.3, Version=v2c, RequestId=524825124, ErrorStatus=12,ErrorIndex=3,

 

2. ErrorStatus=13, ErrorIndex=8

This means the CFG module of the device is busy, also due to frequent backup operation on NMS Servercausing device don’t finish the previous backup task and new task come from NMSServer, so appear this failure(device only can do one backup at the same time).

Apr 18 2021 01:01:20+08:00 S57-C1 %SNMP/4/SNMP_MIB_SET_FAILED(s)[40]:MIB node set failure..(UserName=%^%#TNm7-IB#bJ7=nW'Vu4]:]C:-RE"j|OMGYDNil,B1"oM_V(kVM=.iK!V4i.b~n2#T=0Ll-F0BEx(eFyq<%^%#,SourceIP=10.11.1.3, Version=v2c, RequestId=1313701076, ErrorStatus=13,ErrorIndex=8,


Therefore, please changes the server backup settings. Backups can be performed once a day at most. Typically, we set up a one-week backup.

And if there are several NMS Server, you need to set different backup times periodically.


View more
  • x
  • convention:

I have problem:
Jan 26 2022 15:20:22+03:00 USG6555E_FW2_HQ %SNMP/4/SNMP_MIB_SET_FAILED(s)[57]:MIB node set failure.
View more
  • x
  • convention:

Hi, friend!
Please wait a moment. The engineer will reply later.
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 " User Agreement."

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.