F10-BPSTATS-MIB
AI MIB Summary
The F10-BPSTATS-MIB module monitors Dell Networking OS backplane hardware by tracking per-port traffic counters, link bundle status, queue depths, and buffer utilization. This data enables precise analysis of internal switching fabric performance and congestion on Dell F10 series switches.
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 ..
Main OID:
f10BpStatsMib.1.3.6.1.4.1.6027.3.24
88
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
88 total| Object Name |
|---|
f10BpStatsMibDell 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 .. MODULE-IDENTITY .1.3.6.1.4.1.6027.3.24 |
f10BpStatsLinkBundleObjects OBJECT IDENTIFIER .1.3.6.1.4.1.6027.3.24.1 |
bpLinkBundleObjects OBJECT IDENTIFIER .1.3.6.1.4.1.6027.3.24.1.1 |
bpLinkBundleRateIntervalThe rate interval for polling the Bp link bundle Monitoring.rw INTEGER .1.3.6.1.4.1.6027.3.24.1.1.1 |
bpLinkBundleTriggerThresholdThe traffic distribution trigger threshold for Bp link bundle Monitoring.In percentage of total bandwidth of the link Bundlerw INTEGER .1.3.6.1.4.1.6027.3.24.1.1.2 |
f10BpStatsObjects OBJECT IDENTIFIER .1.3.6.1.4.1.6027.3.24.2 |
bpStatsObjects OBJECT IDENTIFIER .1.3.6.1.4.1.6027.3.24.2.1 |
bpDropsTableThe back plane drops table contains the list of various drops per BP higig port per BCM unit in a stack unit(card type). SEQUENCE OF BpDropsEntry .1.3.6.1.4.1.6027.3.24.2.1.1 |
bpDropsEntryEach drops entry is being indexed by StackUnit(card Type) BCM unit ID and local Port Id BpDropsEntry .1.3.6.1.4.1.6027.3.24.2.1.1.1 |
bpDropsStackUnitIndexStack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units INTEGER .1.3.6.1.4.1.6027.3.24.2.1.1.1.1 |
bpDropsPortPipebpPortPipe 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 INTEGER .1.3.6.1.4.1.6027.3.24.2.1.1.1.2 |
bpDropsPortIndexBP 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 INTEGER .1.3.6.1.4.1.6027.3.24.2.1.1.1.3 |
bpDropsInDropsThe No of Ingress packet Dropsro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.1.1.4 |
bpDropsInUnKnownHgHdrThe No of Unknown hiGig header Ingress packet Dropsro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.1.1.5 |
bpDropsInUnKnownHgOpcodeThe No of Unknown hiGig Opcode Ingress packet Dropsro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.1.1.6 |
bpDropsInMTUExceedsNo of packets dropped on Ingress because of MTUExceedsro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.1.1.7 |
bpDropsInMacDropsNo of packets dropped on Ingress MACro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.1.1.8 |
bpDropsMMUHOLDropsNo of packets dropped in MMU because of MMU HOL Dropsro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.1.1.9 |
bpDropsEgMacDropsNo of packets dropped on Egress MACro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.1.1.10 |
bpDropsEgTxAgedCounterNo of Aged packets dropped on Egressro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.1.1.11 |
bpDropsEgTxErrCounterNo of Error packets dropped on Egressro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.1.1.12 |
bpDropsEgTxMACUnderflowNo of MAC underflow packets dropped on Egressro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.1.1.13 |
bpDropsEgTxErrPktCounterNo of total packets dropped in Egressro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.1.1.14 |
bpIfStatsTableThe back plane counter statistics table contains the list of various counters per BP higig port per BCM unit in a stack unit(card type). SEQUENCE OF BpIfStatsEntry .1.3.6.1.4.1.6027.3.24.2.1.2 |
bpIfStatsEntryEach Stats entry is being indexed by StackUnit(card Type) BCM unit ID and local Port Id BpIfStatsEntry .1.3.6.1.4.1.6027.3.24.2.1.2.1 |
bpIfStatsStackUnitIndexStack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units INTEGER .1.3.6.1.4.1.6027.3.24.2.1.2.1.1 |
bpIfStatsPortPipebpPortPipe 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 INTEGER .1.3.6.1.4.1.6027.3.24.2.1.2.1.2 |
bpIfStatsPortIndexBP 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 INTEGER .1.3.6.1.4.1.6027.3.24.2.1.2.1.3 |
bpIfStatsIn64BytePktsThe total number of frames (including bad frames) received that were 64 octets in length (excluding framing bits but including FCS octets).ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.4 |
bpIfStatsIn65To127BytePktsThe 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).ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.5 |
bpIfStatsIn128To255BytePktsThe 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).ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.6 |
bpIfStatsIn256To511BytePktsThe 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).ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.7 |
bpIfStatsIn512To1023BytePktsThe 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).ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.8 |
bpIfStatsInOver1023BytePktsThe 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.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.9 |
bpIfStatsInThrottlesThis counter is incremented when a valid frame with a length or type field value equal to 0x8808 (Control Frame) is received.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.10 |
bpIfStatsInRuntsThe total number of frames received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.11 |
bpIfStatsInGiantsThe 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.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.12 |
bpIfStatsInCRCThe 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.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.13 |
bpIfStatsInOverrunsThe total number of frames has been chosen to be dropped by detecting the buffer issuero Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.14 |
bpIfStatsOutUnderrunsThe total number of frames dropped because of buffer underrun.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.15 |
bpIfStatsOutUnicastsThe total number of Unicast frames are transmitted out of the interfacero Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.16 |
bpIfStatsOutCollisionsA count of the frames that due to excessive or late collisions are not transmitted successfully.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.17 |
bpIfStatsOutWredDropsThe total number of frames are dropped by using WRED policy due to excessive traffic.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.18 |
bpIfStatsOut64BytePktsThe total number of valid frames with the block of 64 byte size is transmittedro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.19 |
bpIfStatsOut65To127BytePktsThe total of valid frame with the block size of range between 65 and 127 bytes are transmitted.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.20 |
bpIfStatsOut128To255BytePktsThe total of valid frame with the block size of range between 128 and 255 bytes are transmittedro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.21 |
bpIfStatsOut256To511BytePktsThe total of valid frame with the block size of range between 256 and 511 bytes are transmittedro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.22 |
bpIfStatsOut512To1023BytePktsThe total of valid frame with the block size of range between 512 and 1023 bytes are transmittedro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.23 |
bpIfStatsOutOver1023BytePktsThe total of valid frame with the block size of greater than 1023 bytes are transmitted.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.24 |
bpIfStatsOutThrottlesThis counter is incremented when a valid frame with a length or type field value equal to 0x8808 (Control Frame) is sent.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.2.1.25 |
bpIfStatsLastDiscontinuityTimeThe 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.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.6027.3.24.2.1.2.1.26 |
bpIfStatsInCentRateThis 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%.ro Integer32 .1.3.6.1.4.1.6027.3.24.2.1.2.1.27 |
bpIfStatsOutCentRateThis 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%.ro Integer32 .1.3.6.1.4.1.6027.3.24.2.1.2.1.28 |
bpIfStatsLastChangeThe value of sysUpTime, on which all the counters are updated recentlyro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.6027.3.24.2.1.2.1.29 |
bpPacketBufferTableThe packet buffer table contains the modular packet buffers details per stack unit and the mode of allocation. SEQUENCE OF BpPacketBufferEntry .1.3.6.1.4.1.6027.3.24.2.1.3 |
bpPacketBufferEntryPacket buffer details per NPU unit. BpPacketBufferEntry .1.3.6.1.4.1.6027.3.24.2.1.3.1 |
bpPacketBufferStackUnitIndexStack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units INTEGER .1.3.6.1.4.1.6027.3.24.2.1.3.1.1 |
bpPacketBufferPortPipebpPortPipe 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 INTEGER .1.3.6.1.4.1.6027.3.24.2.1.3.1.2 |
bpPacketBufferTotalPacketBufferTotal packet buffer in this NPU unit.ro Counter32 .1.3.6.1.4.1.6027.3.24.2.1.3.1.3 |
bpPacketBufferCurrentAvailBufferCurrent available buffer in this NPU unit.ro Counter32 .1.3.6.1.4.1.6027.3.24.2.1.3.1.4 |
bpPacketBufferPacketBufferAllocStatic or Dynamic allocation.ro Counter32 .1.3.6.1.4.1.6027.3.24.2.1.3.1.5 |
bpBufferStatsTableThe back plane stats per port table contains the packet buffer usage per bp port per NPU unit. SEQUENCE OF BpBufferStatsEntry .1.3.6.1.4.1.6027.3.24.2.1.4 |
bpBufferStatsEntryPer bp port buffer stats BpBufferStatsEntry .1.3.6.1.4.1.6027.3.24.2.1.4.1 |
bpBufferStatsStackUnitIndexStack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units INTEGER .1.3.6.1.4.1.6027.3.24.2.1.4.1.1 |
bpBufferStatsPortPipebpPortPipe 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 INTEGER .1.3.6.1.4.1.6027.3.24.2.1.4.1.2 |
bpBufferStatsPortIndexBP 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 INTEGER .1.3.6.1.4.1.6027.3.24.2.1.4.1.3 |
bpBufferStatsCurrentUsagePerPortCurrent buffer usage per bp port.ro Counter32 .1.3.6.1.4.1.6027.3.24.2.1.4.1.4 |
bpBufferStatsDefaultPacketBuffAllocDefault packet buffer allocated.ro Counter32 .1.3.6.1.4.1.6027.3.24.2.1.4.1.5 |
bpBufferStatsMaxLimitPerPortMax buffer limit per bp port.ro Counter32 .1.3.6.1.4.1.6027.3.24.2.1.4.1.6 |
bpCosStatsTableThe back plane statistics per COS table gives packet buffer statistics per COS per bp port. SEQUENCE OF BpCosStatsEntry .1.3.6.1.4.1.6027.3.24.2.1.5 |
bpCosStatsEntryPer bp port buffer stats and per COS buffer stats. BpCosStatsEntry .1.3.6.1.4.1.6027.3.24.2.1.5.1 |
bpCosStatsStackUnitIndexStack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units INTEGER .1.3.6.1.4.1.6027.3.24.2.1.5.1.1 |
bpCosStatsPortPipebpPortPipe 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 INTEGER .1.3.6.1.4.1.6027.3.24.2.1.5.1.2 |
bpCosStatsPortIndexBP 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 INTEGER .1.3.6.1.4.1.6027.3.24.2.1.5.1.3 |
bpCosStatsCOSNumberCOS queue number, There shall 10 unicast and 5 multicast queues per port in Trident2 INTEGER .1.3.6.1.4.1.6027.3.24.2.1.5.1.4 |
bpCosStatsCurrentUsageCurrent buffer usage per COS per bp port.ro Counter32 .1.3.6.1.4.1.6027.3.24.2.1.5.1.5 |
bpCosStatsDefaultPacketBuffAllocDefault packet buffer allocated per COS queuero Counter32 .1.3.6.1.4.1.6027.3.24.2.1.5.1.6 |
bpCosStatsMaxLimitMax buffer utilization limit per bp port.ro Counter32 .1.3.6.1.4.1.6027.3.24.2.1.5.1.7 |
bpCosStatsHOLDDropsHOLD Drops Per Queue.ro Counter64 .1.3.6.1.4.1.6027.3.24.2.1.5.1.8 |
f10BpStatsAlarms OBJECT IDENTIFIER .1.3.6.1.4.1.6027.3.24.3 |
bpLinkBundleNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.6027.3.24.3.1 |
bpLinkBundleImbalanceTrap generated when traffic imbalance observed in BP Link Bundles NOTIFICATION-TYPE .1.3.6.1.4.1.6027.3.24.3.1.1 |
bpLinkBundleImbalanceClearTrap generated when traffic imbalance is no longer observed on Bp Link bundles NOTIFICATION-TYPE .1.3.6.1.4.1.6027.3.24.3.1.2 |
bpLinkBundleAlarmVariable OBJECT IDENTIFIER .1.3.6.1.4.1.6027.3.24.3.2 |
bpLinkBundleTypeIndicates Type of Back plane HiGig link bundlero Enumeration .1.3.6.1.4.1.6027.3.24.3.2.1 |
bpLinkBundleSlotThe SlotId on which Link Bundle is overloadedro INTEGER .1.3.6.1.4.1.6027.3.24.3.2.2 |
bpLinkBundleNpuUnitThe npuUnitId(BCM unit Id) on which Link Bundle is overloadedro INTEGER .1.3.6.1.4.1.6027.3.24.3.2.3 |
bpLinkBundleLocalIdThe local linkBundle Id which is overloadedro INTEGER .1.3.6.1.4.1.6027.3.24.3.2.4 |