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: 2022-06-14 08:40 AM
Hello all. My company is evaluating Netbotz 750 along with a pair of 155 sensors. We have in-house automation that polls unique SNMP OID's of various APC devices and power infra to gather metrics. We would like to run this against the 155 sensors.
On the Netbotz, each unique sensor is assigned a unique ID e.g.
NetBotz50-MIB::tempSensorIndex.1015030 = Counter32: 1015030
NetBotz50-MIB::tempSensorIndex.1023022 = Counter32: 1023022
NetBotz50-MIB::tempSensorLabel.1015030 = STRING: probe02
NetBotz50-MIB::tempSensorLabel.1023022 = STRING: probe01
How are the tempSensorLabel values assigned? Are they based on enclosure port, or randomly generated? If we manage multiple Netbotz appliances, will the sensor label connected to port 1 always have value 1023022 and the sensor label for sensor on port 2 be 1015030, or will they be different? Thanks all!
Posted: 2022-06-14 08:57 AM
Hi @nwicka ,
For all intents and purposes, the instances associated with each sensor or pod is dynamic and pretty much randomly generated. If you have 2 different 750s, it's a good bet that each sensor on 750 #1 will have a different instance associated with it than the sensors on 750 #2. It was made this way because of the dynamic nature of the NetBotz appliances.
The polling system will need to be manually configured for each 750, pod, and sensor.
One thing you can look at to identify the different sensors is the sensor label. I strongly recommend you label each sensor uniquely on each 750. Maybe provide it's location or rack or something of the sort. The reason for this is that the instances you're seeing will be the same for all that sensor's values. From your own notes, you can see:
NetBotz50-MIB::tempSensorIndex.1015030 = Counter32: 1015030
NetBotz50-MIB::tempSensorIndex.1023022 = Counter32: 1023022
NetBotz50-MIB::tempSensorLabel.1015030 = STRING: probe02
Those 2 responses are for the same sensor and there are a number of other values that will also be associated with that sensor in this way. This is the same way the older version 3 and 3 NetBotz appliances used to work. The NetBotz 250 is a totally different animal all together though and has specific OIDs for each sensor.
Thanks,
Steve
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.