AP4421 no response to OID output Load

[BillP]

Hi,

We use ATS AP4421 firmware v4.1.9 and the OID library Powernet 4.2.6. When i try to poll the device with output Load OID (ex: 1.3.6.1.4.1.318.1.1.8.5.4.3.1.10 or  1.3.6.1.4.1.318.1.1.8.5.4.3.1.7), it return a NULL value. I did my test with the snmp tester EXE of paessler.

So i'm not able to monitor the ATS load. if someone could help me it could be great. 

[BillP]

The OIDs you should be using are: atsOutputPower (1.3.6.1.4.1.318.1.1.8.5.4.3.1.13) or atsOutputPercentPower (1.3.6.1.4.1.318.1.1.8.5.4.3.1.16). 

Also, I think v4.1.9 firmware version may be the ATS controller rev. I'd check for the AOS/APP version you have which should be 6.X.X and is the revision of the Network Management Card in the ATS. Please provide this if the OIDs above still don't work.

Depending on your SNMP tool, you may need to specify an SNMP OID instance at the end of the OID if you are doing a GET. A walk command may not require that. I am not familiar with the tool you're using so I am not sure exactly what is needed. Alternatively, you can try walking atsOutputPhaseTable (1.3.6.1.4.1.318.1.1.8.5.4.3) where the OIDs for output are located to see if they come back.

[BillP]

Thanks for your help.

Snmp tester is a tool to debug snmp for PRTG monitoring.

I tried with a walk command and your OID worked. If I submit a complete OID it don't work but with walk it's ok.

I would like to upgrade the firmware. I'm not familiar with APC product do you know if there is power supply reboot during a firmware upgrade ?

[BillP]

You're welcome.

On 9/26/2018 11:22 AM, damien said:

I tried with a walk command and your OID worked. If I submit a complete OID it don't work but with walk it's ok.

This is probably because you need to add the instance, like .0 or something to the end of the OID. I say that because the walk works.

On 9/26/2018 11:22 AM, damien said:

I would like to upgrade the firmware. I'm not familiar with APC product do you know if there is power supply reboot during a firmware upgrade ?

On this model, you can upgrade the firmware and only the embedded Network Management Card restarts, the ATS itself or power output is not disturbed. (Older generation models had a pre-requisite process to upgrading.) 

[BillP]

I provide you that I tried.

With walk command (1.3.6.1.4.1.318.1.1.8.5.4.3.1.16): 26/09/2018 17:32:12 (29 ms) : 1.3.6.1.4.1.318.1.1.8.5.4.3.1.16.1.1.1 = "26" [ASN_INTEGER]

With OID, without instance (1.3.6.1.4.1.318.1.1.8.5.4.3.1.16): 26/09/2018 17:33:45 (45 ms) : Value: NULL2

With OID, with instance (1.3.6.1.4.1.318.1.1.8.5.4.3.1.16.1.1.1):26/09/2018 17:35:00 (740 ms) : Value: NULL2

[BillP]

Hmm, try sending/specifying .0 and does that work? That is what I see most people doing.

[BillP]

I've upgrade the device to the 6.5.1 version.

After i tried with the following OID: 1.3.6.1.4.1.318.1.1.8.5.4.3.1.16.0 

And the result is not better: 27/09/2018 10:26:28 (28 ms) : Value: NULL2 

[BillP]

Hmm, yes then I am not sure which syntax it wants unfortunately. The walk function still works though, right?

P.S. we will be having a 6.6.4 firmware upgrade coming out in a few weeks for this product, just FYI.

[BillP]

26/09/2018 17:32:12 (29 ms) : 1.3.6.1.4.1.318.1.1.8.5.4.3.1.16.1.1.1 = "26" [ASN_INTEGER]

with the walk command I can see the ID instance (in orange), but even if I submit the complete OID it doesn't work. 

[BillP]

Maybe you have to add .0 to that?

Like 1.3.6.1.4.1.318.1.1.8.5.4.3.1.16.1.1.1.0 ?

I typically use GUI based MIB browser/polling tools so I am not used to having to specify the instance and the most common way to do it.

[BillP]

What do you usally use ? May be it's a PRTG issue. I could try with another tool.

I tried with the .1.1.1.0 and it didn't worked better.

[BillP]

I use a mix between tools like MG-Soft, GetIf, and iReasoning. You usually just highlight the OID and press get or walk and the result comes back. i do find myself using "walk" more often if I had to say.

I have dabbled with Net-SNMP as well (CLI type tool) but usually adding .0 on whatever the OID with in my experience is what is needed for the syntax. I haven't used that too often enough though and of course only on certain OIDs, not really this.

[Anonymous user · Accepted solution]

Hi there. I have the same problem with ATS AP4421 firmware v4.1.9 with same OIDs. Have you solved your problem?

Why snmpwalk can read these OID, but snmpget can't?