CISCO-ENTITY-PFE-MIB

Monitored by Observium
        The Packet Forwarding Engine technology are Cisco developed 
Network Processors, which accelerates certain features in 
order to provide better network performance.
        
An agent uses this MIB to monitor the performance history 
on any active PFE pipeline listed in the ENTITY-MIB (RFC 2737)
entPhysicalTable. This monitoring is via measurement periods
of actual, 1-minute, 5-minutes and 15-minutes.
        
For the 1-minute and 5-minute measurement periods, perfor-
mance statistics are calculated and displayed based on pre-
vious 1 minute and 5 minute respectively.
        
For the 15-minute period, the performance statistics are
accumulated in fifteen minute intervals.  At any one time, 
an agent maintains one current (incomplete) interval and up 
to 96 completed intervals (24 hours worth).  Fewer than 96 
intervals of data will be available if the agent has been 
restarted within the last 24 hours. In addition, there is a 
rolling 24-hour total of each performance statistic.
        
There is no requirement for an agent to ensure fixed rela-
tionship between the start of a fifteen minute interval and 
any wall clock; however some agents may align the fifteen 
minute intervals with quarter hours.
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Processors
Explore Observium network monitoring
Source file
CISCO-ENTITY-PFE-MIB
Last revised
Identity
ciscoEntityPfeMib
Base OID
1.3.6.1.4.1.9.9.265
Imported Objects
CISCO-SMI ciscoMgmt
ENTITY-MIB entPhysicalIndex PhysicalIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Gauge32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DisplayString TEXTUAL-CONVENTION (no object page) TimeStamp
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-ENTITY-PFE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-ENTITY-PFE-MIB::ciscoEntityPfeMib'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-ENTITY-PFE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-ENTITY-PFE-MIB::ciscoEntityPfeMib'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (47)
1 directly used by Observium
.1.3.6.1.4.1.9.9.265
.1.3.6.1.4.1.9.9.265.0
.1.3.6.1.4.1.9.9.265.1
.1.3.6.1.4.1.9.9.265.1.1
.1.3.6.1.4.1.9.9.265.1.1.1
.1.3.6.1.4.1.9.9.265.1.1.1.1
secondsUnsigned32
.1.3.6.1.4.1.9.9.265.1.1.1.1.1
Unsigned32
.1.3.6.1.4.1.9.9.265.1.1.1.1.2
.1.3.6.1.4.1.9.9.265.1.1.1.1.3
.1.3.6.1.4.1.9.9.265.1.1.1.1.4
.1.3.6.1.4.1.9.9.265.1.1.1.1.5
.1.3.6.1.4.1.9.9.265.1.1.1.1.6
.1.3.6.1.4.1.9.9.265.1.1.1.1.7
.1.3.6.1.4.1.9.9.265.1.1.1.1.8
.1.3.6.1.4.1.9.9.265.1.1.2
.1.3.6.1.4.1.9.9.265.1.1.2.1
.1.3.6.1.4.1.9.9.265.1.1.2.1.1
.1.3.6.1.4.1.9.9.265.1.1.2.1.2
.1.3.6.1.4.1.9.9.265.1.1.2.1.3
.1.3.6.1.4.1.9.9.265.1.1.2.1.4
.1.3.6.1.4.1.9.9.265.1.1.2.1.5
.1.3.6.1.4.1.9.9.265.1.1.2.1.6
.1.3.6.1.4.1.9.9.265.1.1.3
.1.3.6.1.4.1.9.9.265.1.1.3.1
Unsigned32
.1.3.6.1.4.1.9.9.265.1.1.3.1.1
.1.3.6.1.4.1.9.9.265.1.1.3.1.2
.1.3.6.1.4.1.9.9.265.1.1.3.1.3
.1.3.6.1.4.1.9.9.265.1.1.4
.1.3.6.1.4.1.9.9.265.1.1.4.1
.1.3.6.1.4.1.9.9.265.1.1.4.1.1
.1.3.6.1.4.1.9.9.265.1.1.4.1.2
.1.3.6.1.4.1.9.9.265.1.2
.1.3.6.1.4.1.9.9.265.1.2.1
Unsigned32
.1.3.6.1.4.1.9.9.265.1.2.2
Unsigned32
.1.3.6.1.4.1.9.9.265.1.2.3
.1.3.6.1.4.1.9.9.265.1.2.4
.1.3.6.1.4.1.9.9.265.1.2.4.1
Unsigned32
.1.3.6.1.4.1.9.9.265.1.2.4.1.1
.1.3.6.1.4.1.9.9.265.1.2.4.1.2
.1.3.6.1.4.1.9.9.265.1.2.4.1.3
.1.3.6.1.4.1.9.9.265.1.2.4.1.4
.1.3.6.1.4.1.9.9.265.1.2.4.1.5
.1.3.6.1.4.1.9.9.265.1.2.4.1.6
.1.3.6.1.4.1.9.9.265.1.2.4.1.7
.1.3.6.1.4.1.9.9.265.2
.1.3.6.1.4.1.9.9.265.2.1
.1.3.6.1.4.1.9.9.265.2.2
Dependencies (8) 5 direct · 3 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (9)
Unsigned32 range: 0..100
Unsigned32 range: 0..100
Enumeration
none(1)
log(2)
notify(3)
logAndNotify(4)
Enumeration
thldUtilizationEvent(1)
thldEfficiencyEvent(2)
thld1MinUtilizationEvent(3)
thld1MinEfficiencyEvent(4)
thld5MinUtilizationEvent(5)
thld5MinEfficiencyEvent(6)
restartEvent(7)
Unsigned32 range: 0..100
Unsigned32 range: 0..100
Unsigned32 range: 0..100
Unsigned32 range: 0..100
Unsigned32 range: 0..100
Conformance Groups (6)
The collection of objects which are used to manage the per-
formance history of the PFE pipeline.
.1.3.6.1.4.1.9.9.265.2.2.1
The collection of objects which are used to maintain the PFE
processor's performance history over a 24 hour of operation.
.1.3.6.1.4.1.9.9.265.2.2.2
The collection of objects which are used to maintain the PFE
processor's performance history over a 24 hour of operation.
.1.3.6.1.4.1.9.9.265.2.2.3
The collection of objects which are used to manage the
threshold configuration for the PFE pipeline performance.
.1.3.6.1.4.1.9.9.265.2.2.4
The collection of objects which are used to manage the
threshold configuration for the PFE pipeline performance.
.1.3.6.1.4.1.9.9.265.2.2.5
The collection of objects which are used to generate a
threshold event for the PFE pipeline performance.
.1.3.6.1.4.1.9.9.265.2.2.6
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.265.2.1.1
An Entity-MIB implementation can implement this module to
provide PFE pipeline performance history.
Required groups
mandatory cePfeMIBPerformanceGroup
mandatory cePfeMIBCurrentGroup
mandatory cePfeMIBHistGroup
mandatory cePfeMIBHistEventGroup
optional cePfeMIBIntervalGroup This group is optional.
optional cePfeMIBTotalGroup This group is optional.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.9.9.265.0.1
This notification is generated when a threshold event has
occurred and the cePfeHistNotifiesEnable is set to
'notify (3)' or 'logAndNotify(4)'.

After generating this notification, another such notifica-
tion will not be sent out until the sample value has fallen
below the threshold value.
.1.3.6.1.4.1.9.9.265.0.2
This notification is generated when a restart event has
occurred and the cePfeHistNotifiesEnable is set to
'notifyp (3)' or 'logAndNotify(4)'.