NetBotz 250 SNMP OID dropped and sensor limitation

[DCIM_Support]

Hello,

I have a NB250 Main Module with no sensors connected.

I have 7 expansion modules each with 6 T&H sensors (total of 42 sensors).

When using SNMPOID to retrieve the data: if I only retrieve up 36 sensors, it works perfectly.

When I tried to retrieve 42 sensors, only 22 of the sensors are return. The remaining 20 are lost.

Can you please let me know if you have seen this issues.

Below are my system info:

Application Module Name: nb250

Version: v6.4.4

Date: Jun 13 2016

APC OS (AOS) Name: aos

Version: v6.4.4

Date: Jun 13 2016

APC Boot Monitor Name: bootmon

Version: v1.0.8

Date: Apr 8 2014

(CID:145850895)

[DCIM_Support]

Hi Quang,

I’ve not heard of this issue before. I can check to see what my engineers may have set up when I’m back in the office Monday as I don’t have anything available that is as loaded as your system. 

Just to be sure, you do have some of the sensor pods powered by an AP9505I power supply correct? Also you’ve verified that the sensors are all showing in the web interface, correct? 

Have you tried upgrading the device firmware?

What specific OID are you using?

Have you tried polling the OID with specific instances instead of all at once?

Have you tried with another SNMP utility to ensure it is not something with your polling software?  

Thanks,

Steve. 

(CID:145850916)

[DCIM_Support]

Hi. I will check with IT to see if they have the AP9505i added. I can poll up to 36 OID in any order. Once I go beyond that, it dropped down to to 22.

I will have IT update the firmware to see if that will solve it. I will keep you updated.

Thanks.

(CID:145851293)

[DCIM_Support]

Thanks Quang. 

What OID were you using?

(CID:145851296)

[DCIM_Support]

OID:

1.3.6.1.4.1.318.1.1.10.4.2.3.1.5.0.1

all the way up

1.3.6.1.4.1.318.1.1.10.4.2.3.1.5.7.1

(CID:145851399)

[DCIM_Support]

I reallized that Netbotz 200 can handle up to 12 expansion module. Is there anything I can do on Netbotz 250 to increase the expansion module? It doesn't make sense a later version limit the expansion module down to only 6. Thanks.

(CID:145851757)

[DCIM_Support]

Hi Quang,

I had to go back to the documentation and I'sorry but I guess I missed this in my initial answer. According to the manual:

https://www.apc.com/salestools/JLER-AK9JP3/JLER-AK9JP3_R5_EN.pdf

The 250 only supports 6 sensor pods. This is why when you add a 7th, you don't get the values. There is nothing you can do with the 250 to make it accept more pods. You'd have to go with a different appliance such as the 570 which can support up to 12 pods:
https://sxwhelpcenter.ecostruxureit.com/download/attachments/96044657/990-3291J.pdf?version=1&modifi...

or you need a second NBRK0250.

Thanks,

Steve.

(CID:145851762)

[DCIM_Support]

Thank you very much Steve for looking into the issue. I see what we need to do on our end. Thanks.

(CID:145851872)

[DCIM_Support]

Okay. So playing with this for over a month now and I have figured out the root cause of this. Below are what I found out.

This happen across both netbotz 200 and netbotz 250. Here is the setup:

Netbotz 250 with 6 expansion module, total T/H sensors is 42 (same with Netbotz 200), loaded with latest firmware.

Using a snmp (such as snmpget), i can ping up to a total of 37 oid addresses at once, when I ping any more than that, the netbotz cease operation and doesn't return any information.

For example, this OID below get the sensors name on main module (0) and sensor (1) - last two digit

.1.3.6.1.4.1.318.1.1.10.4.2.3.1.3.0.1

You can use snmpget to load as much of these oid in as needed as long at it is under 37, anymore and the netbotz cease to return any data.

Can your software team please look at this and see if you can come up with a firmware fix?

Please contact me and I will be happy provide any information your team might need.

Thanks

(CID:147200944)

[DCIM_Support]

Hi Quang,

I can't do much for the 200. If it has an issue like this, it will likely never get fixed as it has been end of life for a few years now. No new firmware is likely to be created except in potential extreme cases such as a potential vulnerability.

On the 250, can you please share the output of the walk?

If for instance the walk fails at:

.1.3.6.1.4.1.318.1.1.10.4.2.3.1.3.6.1  (.6.1 being the instance) and you feel it should go to 6.6 or some similar number, can you poll the instance individually,

.1.3.6.1.4.1.318.1.1.10.4.2.3.1.3.6.6

do you get the value that you expect?

I'm assuming also that similar to your initial comment, this is happening with multiple OIDs, correct?

Steve

(CID:147201191)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.