JUNIPER-PFE-MIB

Integer32 (0..2147483647)

The PFE slot number for this set of global PFE notification statistics.

Counter32

Count of notifications reported by the routing chip.

Counter32

Count of notifications that are dropped due to the fact that the they have been in the system for too long and hence not valid anymore.

Counter32

Count of notifications dropped due to the fact that they have an invalid notification result format. This counter is valid for Internet Processor-I and Internet Processor-II only.

Counter32

Count of notifications dropped due to the fact that they have an illegal notification type.

Counter32

Count of sample notifications reported by the routing chip.

Counter32

Count of notifications dropped that are larger than the supported DMA size.

Counter32

Count of options/TTL-expired notifications that need to be sent to service interfaces as transit packets. This counter is valid for Internet Processor-I and Internet Processor-II only.

Counter32

Count of options/TTL-expired packet notifications that could not be sent as transit packets because the output interface could not be determined. This counter is valid for Internet Processor-I and Internet Processor-II only.

Counter32

Count of IP options packets that are sent out to a Services PIC.

Counter32

Count of IP options packets that are sent out to the Routing Engine.

Counter32

Count of notifications that were re-injected by the services PIC after it had processed the associated packets. These notifications now need to be forwarded out to their actual destination. This counter is valid for Internet Processor-I and Internet Processor-II only.

Counter32

Count of TTL-expired transit packets.

Counter32

Count of sample notifications that are dropped as they refer to discarded packets in PFE.

Counter32

Count of notifications ignored because of PFE software throttling.

Counter32

Count of notifications where we could not allocate memory for DMA.

Counter32

Count of notifications where the DMA of associated packets failed for miscellaneous reasons. Valid for T-series Internet Processor only.

Counter32

Count of notifications for which the packet DMA completed. Valid for T-series Internet Processor only.

Counter32

Count of notifications that could not be resolved to a known next hop destination. Valid for T-series Internet Processor only.

Counter32

Count of notifications for the packets parsed/processed by access-security.

INTEGER1 = illegal2 = unclassified3 = option4 = nextHop5 = discard6 = sample7 = redirect8 = dontFragment9 = cfdf10 = poison11 = unknown12 = specialMemPkt13 = autoConfig14 = reject15 = vxlanEndpoint · Integer32

This identifies the PFE notification type for this row's stats. Below is a description of each notification type: 1. illegal Packets with invalid notification type. 2. unclassified Packets that did not have a key lookup performed on them. 3. option Packets which have L3 options present. 4. nextHop Packets that are destined to the host. 5. discard Used when a discarded packet is sent to the route processor. 6. sample Unused. 7. redirect This is used when a packet is being sent out on the interface it came in on. 8. dontFragment This is used that a packet needs to be fragmented but the DF (don't fragment) bit is set. 9. cfdf When an MTU exceeded indication is triggered by the CF chip and the packet has DF (don't fragment) set. 10. poison Packets that resolved to a poisoned next hop index. 11. unknown Packets of unknown notification type. 12. specialMemPkt Packets with special memory pkt type notification used in diagnostics. 13. autoconfig Packets with autoconfig PFE notification type used for dynamic VLANs. 14. reject Packets of reject PFE notification type. 15. vxlanEndpoint Packets identified as VXLAN decapsulation endpoint (vs transit) for optimized OAM processing.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..64) · OCTET STRING · hint 255a

The description of the Pfe Notification type for this entry.

Counter32

Count of successful parsing of notifications.

Counter32

Count of notifications whose associated packets were DMA'ed into route processor memory.

Counter32

Count of failures in parsing the notifications.

Counter32

Count of notifications where the notification type in the message does not match any of the valid types.

Integer32 (0..2147483647)

The FPC slot number for this set of PFE notification

Integer32 (0..2147483647)

The pfe slot number for this set of errors

Counter64 (0..18446744073709551615)

The parity error count

Counter64 (0..18446744073709551615)

The ECC error count

Unsigned32 (0..100) · percent

The percent PFE ukern memory free within ukern heap.

Unsigned32 (0..3)

ASIC instance number or pfe complex instance number.

JnxPfeMemoryTypeEnum1 = nh2 = fw3 = encapPFE memory type, nh (1), fw (2), encap (3) · Integer32

PFE ASIC memory type, nh = 1, fw = 2, encap = 3.

Unsigned32 (0..100) · percent

Percentage ASIC memory free for a specific memory type. For Trio based linecards Encap memory is not available.Hence no value is returned