[j-nsp] FPC CPU

[Alexandre Snarskii]

On Mon, Sep 24, 2012 at 02:41:46PM +0400, Nick Kritsky wrote:
> Dear j-nsp,
> 
> Apologies, if this is a trivial FAQ - but I cannot find the
> information anywhere.
> For M, MX, EX series there is an OID for monitoring FPC CPU.
> Question - what is this CPU for? What are we measuring here?

Short answer: it depends. 

Longer answer: if you using jnxOperatingCPU (.1.3.6.1.4.1.2636.3.1.13.1.8)
for CPU monitoring, you may use corresponding jnxOperatingDescr OID
(.1.3.6.1.4.1.2636.3.1.13.1.5) to determine which one CPU you're 
monitoring.

For example, closest MX reports following operating entries: 

snar at fri:~>snmpbulkwalk -v2c <some MX960> .1.3.6.1.4.1.2636.3.1.13.1.5
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.1.1.0.0 = STRING: "midplane"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.2.1.0.0 = STRING: "PEM 0"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.2.2.0.0 = STRING: "PEM 1"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.2.3.0.0 = STRING: "PEM 2"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.2.4.0.0 = STRING: "PEM 3"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.4.1.0.0 = STRING: "Top Fan Tray"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.4.1.1.0 = STRING: "Top Tray Fan 1"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.4.1.2.0 = STRING: "Top Tray Fan 2"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.4.1.3.0 = STRING: "Top Tray Fan 3"
[...]
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.7.10.0.0 = STRING: "FPC: MPC 3D 16x 10GE @ 9/*/*"
[...]
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.9.1.0.0 = STRING: "Routing Engine 0"
SNMPv2-SMI::enterprises.2636.3.1.13.1.5.9.2.0.0 = STRING: "Routing Engine 1"
[...]

So monitoring of Routing Engines CPU should be set up using following OIDs: 

.1.3.6.1.4.1.2636.3.1.13.1.8.9.1.0.0 (RE0)
.1.3.6.1.4.1.2636.3.1.13.1.8.9.2.0.0 (RE1)

and for FPC9 .1.3.6.1.4.1.2636.3.1.13.1.8.7.10.0.0 should be used.

> Is it raw throughput stats of an ASIC, or CPU time that is used for
> some FPC-level tasks by some utility processor (BFD? LACP? STP?
> J-Flow?).
> What happens when this value reaches 100% (card freeze, drops, LACP link loss)?

The same answer: it depends [on CPU you're monitoring]. 

> Appreciate your help.
> 
> Thanks
> Nick
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

-- 
In theory, there is no difference between theory and practice. 
But, in practice, there is.