This article provides information about the support that is provided to obtain the temperature and CPU utilization/buffer utilization/Memory from the EX8200-VC backup RE via the jnxOperatingEntry SNMP object.

Customers might claim that the value is always displayed as 0 , when they use SNMP to obtain the temperature/CPU/Buffer/Memory from the EX8200-VC backup RE:

root@EX8200-VC> show snmp mib walk jnxOperatingDescr 
...snip...
jnxOperatingDescr.7.4.0.0 = LCC0 FPC: EX8200-2XS-40P @ 3/*/*
jnxOperatingDescr.7.5.0.0 = LCC0 FPC: EX8200-48PL @ 4/*/*
jnxOperatingDescr.7.6.0.0 = LCC0 FPC: EX8200-8XS-ES @ 5/*/*
jnxOperatingDescr.7.7.0.0 = LCC0 FPC: EX8200-48F @ 6/*/*
jnxOperatingDescr.9.1.0.0 = SCC Routing Engine 0  < Primary RE
jnxOperatingDescr.9.2.0.0 = SCC Routing Engine 1  < Backup RE
jnxOperatingDescr.9.3.0.0 = LCC0 Routing Engine 0
...snip...

{master:8}
root@EX8200-VC> show snmp mib get jnxOperatingTemp.9.2.0.0 
jnxOperatingTemp.9.2.0.0 = 0 < Always shows 0

{master:8}
root@EX8200-VC> show snmp mib get jnxOperatingCPU.9.2.0.0 
jnxOperatingCPU.9.2.0.0 = 0  < Always shows 0

{master:8}
root@EX8200-VC> show snmp mib get jnxOperatingBuffer.9.2.0.0
jnxOperatingBuffer.9.2.0.0 = 0 < Always shows 0
                      
{master:8}
root@EX8200-VC> show snmp mib get jnxOperatingMemory.9.2.0.0 
jnxOperatingMemory.9.2.0.0 = 0 < Always shows 0; it should be 4096

{master:8}
root@EX8200-VC> show snmp mib get jnxOperatingMemory.9.1.0.0 
jnxOperatingMemory.9.1.0.0 = 4096

With the current design, the OIDs for the backup RE in the EX8200-VC system are not supported. The following information indicates the support extended by Junos for EX devices:
 

• For the jnxOperatingTemp SNMP object, the feature for the backup RE in the EX8200-VC system will be supported from Junos 12.2R1.
• For CPU/Buffer/Memory, the feature for the backup RE in the EX8200-VC system will be supported from Junos 12.3R1.

2021-04-06: Updated the article terminology to align with Juniper's Inclusion & Diversity initiatives