EcoStruxure IT forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-04 04:29 PM . Last Modified: 2024-04-05 12:13 AM
Dear Mates,
Hope you all are doing well, I am connecting the Netbotz Sensor Pod 150 Qty:11 with Netbotz 550, but there is a problem, i,e
few of the Sensor pods were existing and others were new , now after cascading, Sensor POD Identification was not in proper sequence, Rack Monitor 550 - 150 IDs were in below sequence
NB550 - ID 6 - ID 11 - ID 5 - ID 2 - ID 10 - ID 9 - ID 4 - ID 12 - ID 3 - ID 7 - ID 8
Please guide that how it can be sorted out without changing the device placement.
Please note that, I had installed the system as per installation manual and put terminator into last sensor POD out-Link, and then powerup the system.
(CID:130094806)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-04 04:29 PM . Last Modified: 2024-04-05 12:12 AM
Hi Mian,
The 150 uses ID #1 by default. If the device sees another pod in the chain has that ID, it gives it #2 and so on. Subsequently that pod will always have ID #2 until it is added to a chain where #2 (or whichever it was last given) is taken and it will get the next available ID. If it's been attached to a chain, it will retain that ID. There is currently no way to manually alter these IDs. It is a suggested enhancement that's already in the system and I will add this post to that enhancement request however I do not know that it is going to be addressed and if so, when it may be. Sorry.
Steve
(CID:130094821)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-04 04:29 PM . Last Modified: 2024-04-05 12:12 AM
Hi Mian,
The 150 uses ID #1 by default. If the device sees another pod in the chain has that ID, it gives it #2 and so on. Subsequently that pod will always have ID #2 until it is added to a chain where #2 (or whichever it was last given) is taken and it will get the next available ID. If it's been attached to a chain, it will retain that ID. There is currently no way to manually alter these IDs. It is a suggested enhancement that's already in the system and I will add this post to that enhancement request however I do not know that it is going to be addressed and if so, when it may be. Sorry.
Steve
(CID:130094821)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-04 04:29 PM . Last Modified: 2024-04-05 12:12 AM
Hi Steven Marchetti,
Thanks for your prompt response, its OK if there is not solution to this problem,
but i have a question here, suppose I reset my Netbotz Rack monitor 550, will this affect any sensor pod Identification # or not?
&
Is there any way to hard reset my Netbotz sensor pod 150 ?
(CID:130094836)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-04 04:29 PM . Last Modified: 2024-04-05 12:12 AM
Sorry Mian but no. Resetting the NetBotz parent device will not reset the IDs shown on the sensor pod 150s. As I tried to infer, it is in the memory of the pod and only changes when there is a conflict with another pod with the same number and it should increment by 1 (or until it reaches a non-conflict number) . If resetting the appliance was an option, I would have suggested that.
Steve
(CID:130094838)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-07-04 04:30 PM . Last Modified: 2023-10-22 02:34 AM
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.