APC UPS Data Center & Enterprise Solutions Forum
Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-28 03:10 AM . Last Modified: 2024-02-14 10:31 PM
I have 4 NetworkAir FM units in a datacenter that I'm monitoring via ethernet/SNMP.
I can get the supply/return temp and humidity no problem... those values show up under the snmp tree:
.iso.org.dod.internet.private.enterprises.apc.products.hardware.airConditioners.airFM.airFMStatus....
There seems to be different parts of the MIB for system and per-unit. I can get those temps/humidities on either subtree,
which makes sense.
But now I'm trying to get the per-unit stats (as defined in the powernet MIB) for filter/coil DP and suction/discharge pressure.
This info is available via the web/telnet interface but it's seemingly not available in SNMP -- when I walk the MIB there's
just no values for those parameters. It really looks like nobody at APC bothered to implement it for those of us using SNMP.
Running firmware 6.24.0, and the ethernet card rev is 3.0.2 (there don't seem to be any updates for the ethernet card for
NetworkAIR FM despite updates being available for the same card for other APC products such as symmetra).
If I can't get at this stuff via SNMP I'm going to have to screen-scrape the telnet or web itnterface, which is just dumb,
since APC obviously had the foresight to put it in the MIB definition in the first place....
Any ideas?
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: 2021-06-28 03:10 AM . Last Modified: 2024-02-14 10:31 PM
We finally got a chance to apply the upgrade... works great now, thanks!
-Will
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: 2021-06-28 03:10 AM . Last Modified: 2024-02-14 10:31 PM
Will,
I'm awaiting a reply from our Infrastruxure Cooling team since we do not have an FM setup in our lab for me to browse to myself. I'll post back as soon as they reply.
Thanks for being patient.
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: 2021-06-28 03:10 AM . Last Modified: 2024-02-14 10:31 PM
Hi Will,
If you use 1.3.6.1.4.1.318.1.1.13, and brows to the subtrees on that, there should be information available via SNMP.
I'm not sure how far off the ball I am with this, and if it's not what you're looking for, you may want to contact Cooling Support and see if they can input a request for a rev of FW that has that information or even find out from FW engineers if that's possible.
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: 2021-06-28 03:10 AM . Last Modified: 2024-02-14 10:31 PM
From our cooling team as I asked them to update for suction/discharge, etc.:
Found them for the FM:
.1.3.6.1.4.1.318.1.1.13.1.5.2.2.1.9
The difference in pressure on either side of the air filters. A high differential pressure indicates a clogged filter. Measured in hundredths of inches water column. A value of -2147483648 indicates that this OID does not apply to this device due to its configuration.
.1.3.6.1.4.1.318.1.1.13.1.5.2.2.1.11
The difference in pressure on either side of the cooling/dehumidification coils. Measured in hundredths of inches water column. A value of -2147483648 indicates that this OID does not apply to this device due to its configuration.
And here are the Suction and Discharge variables:
.1.3.6.1.4.1.318.1.1.13.1.5.4.2.1.7
The refrigerant pressure measured at the discharge outlet of the compressor. Measured in pounds per
square inch. A value of -2147483648 indicates that this OID does not apply to this device due to its configuration.
.1.3.6.1.4.1.318.1.1.13.1.5.4.2.1.5
The refrigerant pressure measured at the suction inlet of the compressor. Measured in pounds per
square inch. A value of -2147483648 indicates that this OID does not apply to this device due to its configuration.
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: 2021-06-28 03:10 AM . Last Modified: 2024-02-14 10:31 PM
Hey KMP,
Those are the exact OIDs I was trying to get after reading the MIB.
I simply get a 'no such variable' response on them.
I can walk like so from a linux box:
%snmpwalk -On -v1 -mall -c(mycommunity) (myhost) 1.3.6.1.4.1.318.1.1.13
.1.3.6.1.4.1.318.1.1.13.1.1.1.0 = STRING: "crac1"
.1.3.6.1.4.1.318.1.1.13.1.1.2.0 = INTEGER: 1
.1.3.6.1.4.1.318.1.1.13.1.1.3.1.1.1 = INTEGER: 1
.1.3.6.1.4.1.318.1.1.13.1.1.3.1.2.1 = STRING: "FM35-50*301419"
.1.3.6.1.4.1.318.1.1.13.1.1.3.1.3.1 = STRING: "03/21/2005"
.1.3.6.1.4.1.318.1.1.13.1.1.3.1.4.1 = STRING: "XK0511002392"
.1.3.6.1.4.1.318.1.1.13.1.1.3.1.5.1 = STRING: "6.24.0"
.1.3.6.1.4.1.318.1.1.13.1.1.3.1.6.1 = STRING: "00"
.1.3.6.1.4.1.318.1.1.13.1.2.1.0 = INTEGER: statusOn(1)
.1.3.6.1.4.1.318.1.1.13.1.2.2.0 = INTEGER: 298
.1.3.6.1.4.1.318.1.1.13.1.2.3.0 = INTEGER: 857
.1.3.6.1.4.1.318.1.1.13.1.2.4.0 = INTEGER: 306
.1.3.6.1.4.1.318.1.1.13.1.2.5.0 = INTEGER: 298
.1.3.6.1.4.1.318.1.1.13.1.2.6.0 = INTEGER: 857
.1.3.6.1.4.1.318.1.1.13.1.2.7.0 = INTEGER: 306
.1.3.6.1.4.1.318.1.1.13.1.2.8.0 = INTEGER: 0
.1.3.6.1.4.1.318.1.1.13.1.2.9.0 = INTEGER: 320
.1.3.6.1.4.1.318.1.1.13.1.2.10.0 = INTEGER: 0
.1.3.6.1.4.1.318.1.1.13.1.2.11.0 = INTEGER: 320
.1.3.6.1.4.1.318.1.1.13.1.2.12.0 = INTEGER: 0
.1.3.6.1.4.1.318.1.1.13.1.2.13.0 = INTEGER: 0
.1.3.6.1.4.1.318.1.1.13.1.2.14.0 = INTEGER: 320
.1.3.6.1.4.1.318.1.1.13.1.2.15.0 = INTEGER: enabledYes(1)
.1.3.6.1.4.1.318.1.1.13.1.2.16.0 = INTEGER: enabledYes(1)
.1.3.6.1.4.1.318.1.1.13.1.2.17.0 = INTEGER: enabledYes(1)
.1.3.6.1.4.1.318.1.1.13.1.2.18.0 = INTEGER: enabledYes(1)
.1.3.6.1.4.1.318.1.1.13.1.2.19.0 = INTEGER: 1
.1.3.6.1.4.1.318.1.1.13.1.2.20.1.1.1 = INTEGER: 1
.1.3.6.1.4.1.318.1.1.13.1.2.20.1.2.1 = INTEGER: 50
.1.3.6.1.4.1.318.1.1.13.1.2.20.1.3.1 = INTEGER: 145
.1.3.6.1.4.1.318.1.1.13.1.2.20.1.4.1 = INTEGER: 581
.1.3.6.1.4.1.318.1.1.13.1.2.20.1.5.1 = INTEGER: 822
.1.3.6.1.4.1.318.1.1.13.1.2.20.1.6.1 = INTEGER: 298
.1.3.6.1.4.1.318.1.1.13.1.2.20.1.7.1 = INTEGER: 857
.1.3.6.1.4.1.318.1.1.13.1.2.20.1.8.1 = INTEGER: 306
.1.3.6.1.4.1.318.1.1.13.1.3.1.0 = INTEGER: statusLoadShare(3)
.1.3.6.1.4.1.318.1.1.13.1.3.2.0 = INTEGER: 27792
.1.3.6.1.4.1.318.1.1.13.1.3.3.0 = INTEGER: roleBackup(2)
Notice there's nothing under
1.3.6.1.4.1.318.1.1.13.1.5 ...
where all the per-unit good stuff I need is!
If I try a single get of OIDs under that part of the tree, I get:
%snmpget -On -v1 -mall -c(mycommunity) (myhost) .1.3.6.1.4.1.318.1.1.13.1.5.2.2.1.11
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.318.1.1.13.1.5.2.2.1.11
And just to prove that the snmpget command works on the other part of the snmp tree (the part shown in the walk above):
%snmpget -On -v1 -mall -c(mycommunity) (myhost) .1.3.6.1.4.1.318.1.1.13.1.2.4.0
.1.3.6.1.4.1.318.1.1.13.1.2.4.0 = INTEGER: 306
Can you follow up or let me know who to contact to keep digging?
Thanks!
-Will
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: 2021-06-28 03:10 AM . Last Modified: 2024-02-14 10:31 PM
Will,
I'm back on it with the cooling team, trying to figure out why it doesn't return that ENTIRE subtree. Maybe if Voidstar is around (not sure of WHAT FW you handle, but maybe some insight?) he can assist. If not, I'm trying to figure out who within APC we can contact above tech support to get a resolution for you.
Thanks for being patient.
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: 2021-06-28 03:10 AM . Last Modified: 2024-02-14 10:31 PM
We finally got a chance to apply the upgrade... works great now, thanks!
-Will
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.