Switching

We have juniper switches in a virtual chassis and are looking to monitor the power supplies via snmp.  We're using Manager to monitor and while I can get CPU, memory, temp, etc I'm struggling with the power supply monitoring.  Any help would be appreciated.

Hi ctvader,

The OID for EX Power supplies starts at .1.3.6.1.4.1.2636.3.1.13.1.6.2:

dfex@EX4200-VC-Core> show snmp mib walk .1.3.6.1.4.1.2636.3.1.13.1.6.2 
jnxOperatingState.2.1.1.0 = 2
jnxOperatingState.2.1.2.0 = 2
jnxOperatingState.2.2.1.0 = 2
jnxOperatingState.2.2.2.0 = 2
jnxOperatingState.2.3.1.0 = 2
jnxOperatingState.2.3.2.0 = 2

This is the output from a three switch virtual chassis - the number in bold is the node (1 for node0, 2 for node1, 3 for node2 etc) and the underlined number is the power supply (1 for primary, 2 for secondary).  So if you just wanted to look at state of node2's (the 3rd node) secondary power supply for example, just add .3.2 to the end:

dfex@EX4200-VC-Core> show snmp mib walk .1.3.6.1.4.1.2636.3.1.13.1.6.2.3.2
jnxOperatingState.2.3.2.0 = 2 

The actual value of Operating State can be from 1-6:

1- Unknown 

2- Up and running

3- Ready to run, not running yet

4- Held in reset, not ready yet

5- Running at Full Speed (valid for fans only)

6- Down or off (for power supply) 

7- Running as a standby (Backup)

Hope this helps

dfex,

Thank you for your help and that helps out so much.  However, when I run the snmp walk for the OID, I see something slightly different.  Any ideas why I dont see all the switches (we have 10 EX4200s in a VC).  Thanks.

support@Core> show snmp mib walk .1.3.6.1.4.1.2636.3.1.13.1.6     
jnxOperatingState.1.1.0.0 = 2
jnxOperatingState.2.1.1.0 = 2
jnxOperatingState.2.1.2.0 = 2
jnxOperatingState.4.1.1.1 = 2
jnxOperatingState.4.1.1.2 = 2
jnxOperatingState.4.1.1.3 = 2
jnxOperatingState.7.1.0.0 = 2
jnxOperatingState.8.1.1.0 = 2
jnxOperatingState.8.1.2.0 = 2
jnxOperatingState.9.1.0.0 = 2
jnxOperatingState.9.2.0.0 = 7

Sorry for digging this thread out but maybe this might be of interest as the last question was not answered yet...

I also noticed that with the operatingtable mib there might be some VC members PSUs missing.

As a workaround instead of the operating state table the FRU table / FRU state mibs can be used:

jnxFruState OBJECT-TYPE
	SYNTAX		INTEGER {
		unknown(1),
		empty(2),
		present(3),
		ready(4),
		announceOnline(5),
		online(6),
		anounceOffline(7),
		offline(8),
		diagnostic(9),
		standby(10)
	}

Other than the operating state table this tables values seem to be more reliable even though I had some devices where all PSU slots were labeled 2 for empty while the device was actively using PSUs in these slots.

However 1.3.6.1.4.1.2636.3.1.15.1.8.2 worked good for me (use 5.2 instead of the 8.2 at the end to display a description for the FRU).