F10-BPSTATS-MIB

All MIBs › F10-BPSTATS-MIB

Organization: Dell Inc

Last Updated: 2013-09-18

Category: Network Monitoring (RMON), Technology: Traffic Monitoring, Vendor: Dell/DNOS

Description: Dell Force10 MIB for backplane statistics, reporting data plane traffic counters across chassis backplane interfaces.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is F10-BPSTATS-MIB?

This Dell Force10 (Dell Networking OS) MIB covers backplane statistics for chassis-based switches, reporting traffic counters for the internal backplane (BP) ports that interconnect line cards and route engines inside a modular chassis. Per its module description it covers BP port traffic statistics, BP link-bundle monitoring, and queue/buffer utilization on BP ports. It is squarely a performance-counter MIB used to monitor internal hardware fabric health — packet/byte counts, queue depth, and buffer utilization on the backplane links that carry all inter-line-card traffic within the chassis. No sample objects were available in this batch, but as a Dell Networking OS proprietary MIB it is expected to build on standard SNMPv2 conventions without direct dependence on other IETF MIBs. It is used in large modular Dell Force10 chassis switches (e.g., E-Series) where visibility into internal backplane congestion or buffer exhaustion is critical for diagnosing performance problems not visible from front-panel interface counters alone. Engineers can download the F10-BPSTATS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in F10-BPSTATS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Dell Force10 modular chassis switch (E-Series and similar)

Monitoring Examples

Sample object names were not available for this MIB, so a concrete polling example cannot be grounded in real names; based on the module description, an admin would be expected to poll per-BP-port traffic counters and queue/buffer utilization tables to detect backplane congestion or an unbalanced link bundle inside the chassis fabric.

What Can Be Monitored

backplane port traffic statistics
backplane link bundle status
backplane queue statistics
backplane buffer utilization

Imported Objects

From FORCE10-SMI

f10Mgmt

OBJECT-IDENTITY

From SNMPv2-SMI

Counter32
Counter64
Gauge32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

TimeStamp

OIDs

OID symbolic	OID numeric	Type	Access	Description
C32 bpBufferStatsCurrentUsagePerPort	1.3.6.1.4.1.6027.3.24.2.1.4.1.4	Counter32	read-only	Current buffer usage per bp port.
C32 bpBufferStatsDefaultPacketBuffAlloc	1.3.6.1.4.1.6027.3.24.2.1.4.1.5	Counter32	read-only	Default packet buffer allocated.
bpBufferStatsEntry	1.3.6.1.4.1.6027.3.24.2.1.4.1		not-accessible	Per bp port buffer stats
C32 bpBufferStatsMaxLimitPerPort	1.3.6.1.4.1.6027.3.24.2.1.4.1.6	Counter32	read-only	Max buffer limit per bp port.
INT bpBufferStatsPortIndex	1.3.6.1.4.1.6027.3.24.2.1.4.1.3	INTEGER	not-accessible	BP port number. Maximum ports shall support by Trident2 BCM npu is 128. This address space includes FE ports also, which are invalid ports as far as BP is concern. For Z9000 leaf BCM units, 34 to 41 are the valid BP port numbers and for spine BCM units, 1 to 16 are the valid BP ports
INT bpBufferStatsPortPipe	1.3.6.1.4.1.6027.3.24.2.1.4.1.2	INTEGER	not-accessible	bpPortPipe denotes the BCM unit in the stack unit(card Type) Each BCM unit shall contain 1-128 local ports, which includes BP as well as front end ports
INT bpBufferStatsStackUnitIndex	1.3.6.1.4.1.6027.3.24.2.1.4.1.1	INTEGER	not-accessible	Stack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units
bpBufferStatsTable	1.3.6.1.4.1.6027.3.24.2.1.4		not-accessible	The back plane stats per port table contains the packet buffer usage per bp port per NPU unit.
INT bpCosStatsCOSNumber	1.3.6.1.4.1.6027.3.24.2.1.5.1.4	INTEGER	not-accessible	COS queue number, There shall 10 unicast and 5 multicast queues per port in Trident2
C32 bpCosStatsCurrentUsage	1.3.6.1.4.1.6027.3.24.2.1.5.1.5	Counter32	read-only	Current buffer usage per COS per bp port.
C32 bpCosStatsDefaultPacketBuffAlloc	1.3.6.1.4.1.6027.3.24.2.1.5.1.6	Counter32	read-only	Default packet buffer allocated per COS queue
bpCosStatsEntry	1.3.6.1.4.1.6027.3.24.2.1.5.1		not-accessible	Per bp port buffer stats and per COS buffer stats.
C64 bpCosStatsHOLDDrops	1.3.6.1.4.1.6027.3.24.2.1.5.1.8	Counter64	read-only	HOLD Drops Per Queue.
C32 bpCosStatsMaxLimit	1.3.6.1.4.1.6027.3.24.2.1.5.1.7	Counter32	read-only	Max buffer utilization limit per bp port.
INT bpCosStatsPortIndex	1.3.6.1.4.1.6027.3.24.2.1.5.1.3	INTEGER	not-accessible	BP port number. Maximum ports shall support by Trident2 BCM npu is 128. This address space includes FE ports also, which are invalid ports as far as BP is concern. For Z9000 leaf BCM units, 34 to 41 are the valid BP port numbers and for spine BCM units, 1 to 16 are the valid BP ports
INT bpCosStatsPortPipe	1.3.6.1.4.1.6027.3.24.2.1.5.1.2	INTEGER	not-accessible	bpPortPipe denotes the BCM unit in the stack unit(card Type) Each BCM unit shall contain 1-128 local ports, which includes BP as well as front end ports
INT bpCosStatsStackUnitIndex	1.3.6.1.4.1.6027.3.24.2.1.5.1.1	INTEGER	not-accessible	Stack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units
bpCosStatsTable	1.3.6.1.4.1.6027.3.24.2.1.5		not-accessible	The back plane statistics per COS table gives packet buffer statistics per COS per bp port.
C64 bpDropsEgMacDrops	1.3.6.1.4.1.6027.3.24.2.1.1.1.10	Counter64	read-only	No of packets dropped on Egress MAC
C64 bpDropsEgTxAgedCounter	1.3.6.1.4.1.6027.3.24.2.1.1.1.11	Counter64	read-only	No of Aged packets dropped on Egress
C64 bpDropsEgTxErrCounter	1.3.6.1.4.1.6027.3.24.2.1.1.1.12	Counter64	read-only	No of Error packets dropped on Egress
C64 bpDropsEgTxErrPktCounter	1.3.6.1.4.1.6027.3.24.2.1.1.1.14	Counter64	read-only	No of total packets dropped in Egress
C64 bpDropsEgTxMACUnderflow	1.3.6.1.4.1.6027.3.24.2.1.1.1.13	Counter64	read-only	No of MAC underflow packets dropped on Egress
bpDropsEntry	1.3.6.1.4.1.6027.3.24.2.1.1.1		not-accessible	Each drops entry is being indexed by StackUnit(card Type) BCM unit ID and local Port Id
C64 bpDropsInDrops	1.3.6.1.4.1.6027.3.24.2.1.1.1.4	Counter64	read-only	The No of Ingress packet Drops
C64 bpDropsInMacDrops	1.3.6.1.4.1.6027.3.24.2.1.1.1.8	Counter64	read-only	No of packets dropped on Ingress MAC
C64 bpDropsInMTUExceeds	1.3.6.1.4.1.6027.3.24.2.1.1.1.7	Counter64	read-only	No of packets dropped on Ingress because of MTUExceeds
C64 bpDropsInUnKnownHgHdr	1.3.6.1.4.1.6027.3.24.2.1.1.1.5	Counter64	read-only	The No of Unknown hiGig header Ingress packet Drops
C64 bpDropsInUnKnownHgOpcode	1.3.6.1.4.1.6027.3.24.2.1.1.1.6	Counter64	read-only	The No of Unknown hiGig Opcode Ingress packet Drops
C64 bpDropsMMUHOLDrops	1.3.6.1.4.1.6027.3.24.2.1.1.1.9	Counter64	read-only	No of packets dropped in MMU because of MMU HOL Drops
INT bpDropsPortIndex	1.3.6.1.4.1.6027.3.24.2.1.1.1.3	INTEGER	not-accessible	BP port number. Maximum ports shall support by Trident2 BCM npu is 128. This address space includes FE ports also, which are invalid ports as far as BP is concern. For Z9000 leaf BCM units, 34 to 41 are the valid BP port numbers and for spine BCM units, 1 to 16 are the valid BP ports
INT bpDropsPortPipe	1.3.6.1.4.1.6027.3.24.2.1.1.1.2	INTEGER	not-accessible	bpPortPipe denotes the BCM unit in the stack unit(card Type) Each BCM unit shall contain 1-128 local ports, which includes BP as well as front end ports
INT bpDropsStackUnitIndex	1.3.6.1.4.1.6027.3.24.2.1.1.1.1	INTEGER	not-accessible	Stack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units
bpDropsTable	1.3.6.1.4.1.6027.3.24.2.1.1		not-accessible	The back plane drops table contains the list of various drops per BP higig port per BCM unit in a stack unit(card type).
bpIfStatsEntry	1.3.6.1.4.1.6027.3.24.2.1.2.1		not-accessible	Each Stats entry is being indexed by StackUnit(card Type) BCM unit ID and local Port Id
C64 bpIfStatsIn128To255BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.6	Counter64	read-only	The total number of frames (including bad frames) received that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets).
C64 bpIfStatsIn256To511BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.7	Counter64	read-only	The total number of frames (including bad frames) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets).
C64 bpIfStatsIn512To1023BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.8	Counter64	read-only	The total number of frames (including bad frames) received that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets).
C64 bpIfStatsIn64BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.4	Counter64	read-only	The total number of frames (including bad frames) received that were 64 octets in length (excluding framing bits but including FCS octets).
C64 bpIfStatsIn65To127BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.5	Counter64	read-only	The total number of frames (including bad frames) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets).
I32 bpIfStatsInCentRate	1.3.6.1.4.1.6027.3.24.2.1.2.1.27	Integer32	read-only	This is the percentage of maximum line rate at which data is receiving on the Interface. For Z9000 - BP hiGig line rate is 42G. This is an integer value which can go from 0% to 100%.
C64 bpIfStatsInCRC	1.3.6.1.4.1.6027.3.24.2.1.2.1.13	Counter64	read-only	The total number of frames received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had a bad CRC.
C64 bpIfStatsInGiants	1.3.6.1.4.1.6027.3.24.2.1.2.1.12	Counter64	read-only	The total number of frames received that were longer than 1518 (1522 Bytes in case of VLAN Tag) octets (excluding framing bits, but including FCS octets) and were otherwise well formed. This counter is not incremented for too long frames.
C64 bpIfStatsInOver1023BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.9	Counter64	read-only	The total number of frames received that were longer than 1023 (1025 Bytes in case of VLAN Tag) octets (excluding framing bits, but including FCS octets) and were otherwise well formed. This counter is not incremented for too long frames.
C64 bpIfStatsInOverruns	1.3.6.1.4.1.6027.3.24.2.1.2.1.14	Counter64	read-only	The total number of frames has been chosen to be dropped by detecting the buffer issue
C64 bpIfStatsInRunts	1.3.6.1.4.1.6027.3.24.2.1.2.1.11	Counter64	read-only	The total number of frames received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.
C64 bpIfStatsInThrottles	1.3.6.1.4.1.6027.3.24.2.1.2.1.10	Counter64	read-only	This counter is incremented when a valid frame with a length or type field value equal to 0x8808 (Control Frame) is received.
TIM bpIfStatsLastChange	1.3.6.1.4.1.6027.3.24.2.1.2.1.29	TimeStamp	read-only	The value of sysUpTime, on which all the counters are updated recently
TIM bpIfStatsLastDiscontinuityTime	1.3.6.1.4.1.6027.3.24.2.1.2.1.26	TimeStamp	read-only	The value of sysUpTime on the most recent occasion at which this interface's counters suffered a discontinuity via a reset. If no such discontinuities have occurred since the last reinitialization of the local management subsystem, then this object contains a zero value.
C64 bpIfStatsOut128To255BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.21	Counter64	read-only	The total of valid frame with the block size of range between 128 and 255 bytes are transmitted
C64 bpIfStatsOut256To511BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.22	Counter64	read-only	The total of valid frame with the block size of range between 256 and 511 bytes are transmitted
C64 bpIfStatsOut512To1023BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.23	Counter64	read-only	The total of valid frame with the block size of range between 512 and 1023 bytes are transmitted
C64 bpIfStatsOut64BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.19	Counter64	read-only	The total number of valid frames with the block of 64 byte size is transmitted
C64 bpIfStatsOut65To127BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.20	Counter64	read-only	The total of valid frame with the block size of range between 65 and 127 bytes are transmitted.
I32 bpIfStatsOutCentRate	1.3.6.1.4.1.6027.3.24.2.1.2.1.28	Integer32	read-only	This is the percentage of maximum line rate at which data is sending on the Interface. For Z9000 - BP hiGig line rate is 42G. This is an integer value which can go from 0% to 100%.
C64 bpIfStatsOutCollisions	1.3.6.1.4.1.6027.3.24.2.1.2.1.17	Counter64	read-only	A count of the frames that due to excessive or late collisions are not transmitted successfully.
C64 bpIfStatsOutOver1023BytePkts	1.3.6.1.4.1.6027.3.24.2.1.2.1.24	Counter64	read-only	The total of valid frame with the block size of greater than 1023 bytes are transmitted.
C64 bpIfStatsOutThrottles	1.3.6.1.4.1.6027.3.24.2.1.2.1.25	Counter64	read-only	This counter is incremented when a valid frame with a length or type field value equal to 0x8808 (Control Frame) is sent.
C64 bpIfStatsOutUnderruns	1.3.6.1.4.1.6027.3.24.2.1.2.1.15	Counter64	read-only	The total number of frames dropped because of buffer underrun.
C64 bpIfStatsOutUnicasts	1.3.6.1.4.1.6027.3.24.2.1.2.1.16	Counter64	read-only	The total number of Unicast frames are transmitted out of the interface
C64 bpIfStatsOutWredDrops	1.3.6.1.4.1.6027.3.24.2.1.2.1.18	Counter64	read-only	The total number of frames are dropped by using WRED policy due to excessive traffic.
INT bpIfStatsPortIndex	1.3.6.1.4.1.6027.3.24.2.1.2.1.3	INTEGER	not-accessible	BP port number. Maximum ports shall support by Trident2 BCM npu is 128. This address space includes FE ports also, which are invalid ports as far as BP is concern. For Z9000 leaf BCM units, 34 to 41 are the valid BP port numbers and for spine BCM units, 1 to 16 are the valid BP ports
INT bpIfStatsPortPipe	1.3.6.1.4.1.6027.3.24.2.1.2.1.2	INTEGER	not-accessible	bpPortPipe denotes the BCM unit in the stack unit(card Type) Each BCM unit shall contain 1-128 local ports, which includes BP as well as front end ports
INT bpIfStatsStackUnitIndex	1.3.6.1.4.1.6027.3.24.2.1.2.1.1	INTEGER	not-accessible	Stack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units
bpIfStatsTable	1.3.6.1.4.1.6027.3.24.2.1.2		not-accessible	The back plane counter statistics table contains the list of various counters per BP higig port per BCM unit in a stack unit(card type).
bpLinkBundleAlarmVariable	1.3.6.1.4.1.6027.3.24.3.2
NTF bpLinkBundleImbalance	1.3.6.1.4.1.6027.3.24.3.1.1			Trap generated when traffic imbalance observed in BP Link Bundles
NTF bpLinkBundleImbalanceClear	1.3.6.1.4.1.6027.3.24.3.1.2			Trap generated when traffic imbalance is no longer observed on Bp Link bundles
INT bpLinkBundleLocalId	1.3.6.1.4.1.6027.3.24.3.2.4	INTEGER	accessible-for-notify	The local linkBundle Id which is overloaded
bpLinkBundleNotifications	1.3.6.1.4.1.6027.3.24.3.1
INT bpLinkBundleNpuUnit	1.3.6.1.4.1.6027.3.24.3.2.3	INTEGER	accessible-for-notify	The npuUnitId(BCM unit Id) on which Link Bundle is overloaded
bpLinkBundleObjects	1.3.6.1.4.1.6027.3.24.1.1
INT bpLinkBundleRateInterval	1.3.6.1.4.1.6027.3.24.1.1.1	INTEGER	read-write	The rate interval for polling the Bp link bundle Monitoring.
INT bpLinkBundleSlot	1.3.6.1.4.1.6027.3.24.3.2.2	INTEGER	accessible-for-notify	The SlotId on which Link Bundle is overloaded
INT bpLinkBundleTriggerThreshold	1.3.6.1.4.1.6027.3.24.1.1.2	INTEGER	read-write	The traffic distribution trigger threshold for Bp link bundle Monitoring.In percentage of total bandwidth of the link Bundle
INT bpLinkBundleType	1.3.6.1.4.1.6027.3.24.3.2.1	INTEGER	accessible-for-notify	Indicates Type of Back plane HiGig link bundle
C32 bpPacketBufferCurrentAvailBuffer	1.3.6.1.4.1.6027.3.24.2.1.3.1.4	Counter32	read-only	Current available buffer in this NPU unit.
bpPacketBufferEntry	1.3.6.1.4.1.6027.3.24.2.1.3.1		not-accessible	Packet buffer details per NPU unit.
C32 bpPacketBufferPacketBufferAlloc	1.3.6.1.4.1.6027.3.24.2.1.3.1.5	Counter32	read-only	Static or Dynamic allocation.
INT bpPacketBufferPortPipe	1.3.6.1.4.1.6027.3.24.2.1.3.1.2	INTEGER	not-accessible	bpPortPipe denotes the BCM unit in the stack unit(card Type) Each BCM unit shall contain 1-128 local ports, which includes BP as well as front end ports
INT bpPacketBufferStackUnitIndex	1.3.6.1.4.1.6027.3.24.2.1.3.1.1	INTEGER	not-accessible	Stack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units
bpPacketBufferTable	1.3.6.1.4.1.6027.3.24.2.1.3		not-accessible	The packet buffer table contains the modular packet buffers details per stack unit and the mode of allocation.
C32 bpPacketBufferTotalPacketBuffer	1.3.6.1.4.1.6027.3.24.2.1.3.1.3	Counter32	read-only	Total packet buffer in this NPU unit.
bpStatsObjects	1.3.6.1.4.1.6027.3.24.2.1
f10BpStatsAlarms	1.3.6.1.4.1.6027.3.24.3
f10BpStatsLinkBundleObjects	1.3.6.1.4.1.6027.3.24.1
f10BpStatsMib	1.3.6.1.4.1.6027.3.24			Dell Networking OS Back plane statistics mib. This is MIB shall use for all back plane statistics related activities. This includes the BP ports traffic statistics. BP link bundle monitoring based on BP port statistics. Queue statistics and buffer utilization on BP ports etc ..
f10BpStatsObjects	1.3.6.1.4.1.6027.3.24.2

RFC description

A Force10 Networks (now Dell) proprietary MIB for monitoring and reporting backup and protection statistics on Force10 switching and routing equipment, part of the FTOS management infrastructure.

Start monitoring Dell Force10 modular chassis switch (backplane port statistics) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download F10-BPSTATS-MIB

What Is F10-BPSTATS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description