EcoStruxure IT forum
A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.
Posted: 2020-07-05 01:47 PM
This question was originally posted on DCIM Support by guanyc on 2018-11-06
Recently, we received a customer notification that a Netbotz 250 communication was lost, but in the same local network, there is an SNMP ups that is working.
Using network capture analysis, I found that Netbotz was able to receive DCE requests, but the response was sent to a different path.
Specifically,
DCE's SNMP request is sent to Netbotz via (three-layer switch) 3c:e5:a6:14:36:XX
, but the response message is sent to the 00:11:18:09:21:XX device (not the default gateway),
by MAC address, I found that the device IP is 121.1.X.188 (the default gateway is 129),
And I saw that it had a lot of routing broadcasts, and when the device was disconnected from the network, the communication with DCE was restored.
Netbotz uses a static IP, and should not change the send flow because of routing announcements? So, what causes Netbotz's data to go incorrectly? Thank you
Network Management Card AOS v6.4.6
NETBOTZ 250 APP v6.4.6
(CID:134694444)
Posted: 2020-07-05 01:47 PM
This comment was originally posted on DCIM Support by spezialist on 2018-11-08
Dear guanyc,
Thanks for the detailed explanation of the problem, I appreciate it.
Since NetBotz-250 devices are devices of a new generation, to begin with, I highly recommend that you first upgrade your firmware to the latest version v.6.5.6.
See for example and NetBotz Firmware v6.5.6 (NBRK0250/NBACS125/NBACS1356).
Try this and please report the result.
With respect.
(CID:134695218)
Posted: 2020-07-05 01:47 PM
This comment was originally posted on DCIM Support by spezialist on 2018-11-25
Dear guanyc,
Please, tell us if you could solve this problem or not?
With respect.
(CID:137103342)
Posted: 2020-07-05 01:47 PM
This comment was originally posted on DCIM Support by guanyc on 2018-12-03
HI @spezialist
I have upgraded to 6.5.6.
But the problem has not been solved.
Is there any other solution?
Thank you
(CID:137106544)
Posted: 2020-07-05 01:47 PM
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.