jnxPfeNotifyTypeTable

jnxPfeNotifyTypeTable contains information about type-specific Packet Forwarding Engine notifications for each Packet Forwarding Engine slot. Packet Forwarding Engine notification types are listed in Table 110.

Table 110: Packet Forwarding Engine Notification Types

Index

Item

Description

1

Illegal

Packets with an invalid notification type.

2

Unclassified

Packets that did not have a key lookup performed on them.

3

Option

Packets that include L3 options.

4

Next Hop

Packets that are destined to the host.

5

Discard

Discarded packets sent to the route processor.

6

Sample

Unused.

7

Redirect

Packets sent back to the interfaces from which they arrived.

8

Do Not Fragment

Packets that need to be fragmented, but have a don’t fragment (DF) value set.

9

CFDF

Packets that have a DF value set and a maximum transmission unit (MTU) exceeded indicator is triggered.

10

Poison

Packets that have a poisoned next-hop index.

For information about jnxPfeNotifyTypeEntry, see the following section:

jnxPfeNotifyTypeEntry

jnxPfeNotifyTypeEntry contains information about type-specific Packet Forwarding Engine notifications, and has the objects listed in Table 111.

Table 111: jnxPfeNotifyTypeEntry

Object

Object Identifier

Description

jnxPfeNotifyTypeId

jnxPfeNotifyTypeEntry 1

Identifies the Packet Forwarding Engine notification type. See Table 110 for a list of notification types.

jnxPfeNotifyTypeDescr

jnxPfeNotifyTypeEntry 2

A description of the Packet Forwarding Engine notification type.

jnxPfeNotifyTypeParsed

jnxPfeNotifyTypeEntry 3

The number of notifications that are parsed successfully.

jnxPfeNotifyTypeInput

jnxPfeNotifyTypeEntry 4

The number of notifications whose associated packets are stored in router processor memory using direct memory access.

jnxPfeNotifyTypeFailed

jnxPfeNotifyTypeEntry 5

The number of notifications that are not parsed successfully.

jnxPfeNotifyTypeIgnored

jnxPfeNotifyTypeEntry 6

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

Related Topics