F10-BPSTATS-MIB: View SNMP OID List / Download MIB

VENDOR: FORCE10 NETWORKS


 Home MIB: F10-BPSTATS-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC, FORCE10-SMI

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 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 ..
       f10BpStatsLinkBundleObjects 1.3.6.1.4.1.6027.3.24.1
           bpLinkBundleObjects 1.3.6.1.4.1.6027.3.24.1.1
               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.
               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
       f10BpStatsObjects 1.3.6.1.4.1.6027.3.24.2
           bpStatsObjects 1.3.6.1.4.1.6027.3.24.2.1
               bpDropsTable 1.3.6.1.4.1.6027.3.24.2.1.1 no-access
The back plane drops table contains the list of various drops per BP higig port per BCM unit in a stack unit(card type).
                   bpDropsEntry 1.3.6.1.4.1.6027.3.24.2.1.1.1 no-access
Each drops entry is being indexed by StackUnit(card Type) BCM unit ID and local Port Id
                       bpDropsStackUnitIndex 1.3.6.1.4.1.6027.3.24.2.1.1.1.1 integer no-access
Stack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units
                       bpDropsPortPipe 1.3.6.1.4.1.6027.3.24.2.1.1.1.2 integer no-access
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
                       bpDropsPortIndex 1.3.6.1.4.1.6027.3.24.2.1.1.1.3 integer no-access
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
                       bpDropsInDrops 1.3.6.1.4.1.6027.3.24.2.1.1.1.4 counter64 read-only
The No of Ingress packet Drops
                       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
                       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
                       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
                       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
                       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
                       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
                       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
                       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
                       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
                       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
               bpIfStatsTable 1.3.6.1.4.1.6027.3.24.2.1.2 no-access
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).
                   bpIfStatsEntry 1.3.6.1.4.1.6027.3.24.2.1.2.1 no-access
Each Stats entry is being indexed by StackUnit(card Type) BCM unit ID and local Port Id
                       bpIfStatsStackUnitIndex 1.3.6.1.4.1.6027.3.24.2.1.2.1.1 integer no-access
Stack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units
                       bpIfStatsPortPipe 1.3.6.1.4.1.6027.3.24.2.1.2.1.2 integer no-access
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
                       bpIfStatsPortIndex 1.3.6.1.4.1.6027.3.24.2.1.2.1.3 integer no-access
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
                       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).
                       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).
                       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).
                       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).
                       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).
                       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.
                       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.
                       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.
                       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.
                       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.
                       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
                       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.
                       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
                       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.
                       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.
                       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
                       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.
                       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
                       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
                       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
                       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.
                       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.
                       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.
                       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%.
                       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%.
                       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
               bpPacketBufferTable 1.3.6.1.4.1.6027.3.24.2.1.3 no-access
The packet buffer table contains the modular packet buffers details per stack unit and the mode of allocation.
                   bpPacketBufferEntry 1.3.6.1.4.1.6027.3.24.2.1.3.1 no-access
Packet buffer details per NPU unit.
                       bpPacketBufferStackUnitIndex 1.3.6.1.4.1.6027.3.24.2.1.3.1.1 integer no-access
Stack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units
                       bpPacketBufferPortPipe 1.3.6.1.4.1.6027.3.24.2.1.3.1.2 integer no-access
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
                       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.
                       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.
                       bpPacketBufferPacketBufferAlloc 1.3.6.1.4.1.6027.3.24.2.1.3.1.5 counter32 read-only
Static or Dynamic allocation.
               bpBufferStatsTable 1.3.6.1.4.1.6027.3.24.2.1.4 no-access
The back plane stats per port table contains the packet buffer usage per bp port per NPU unit.
                   bpBufferStatsEntry 1.3.6.1.4.1.6027.3.24.2.1.4.1 no-access
Per bp port buffer stats
                       bpBufferStatsStackUnitIndex 1.3.6.1.4.1.6027.3.24.2.1.4.1.1 integer no-access
Stack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units
                       bpBufferStatsPortPipe 1.3.6.1.4.1.6027.3.24.2.1.4.1.2 integer no-access
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
                       bpBufferStatsPortIndex 1.3.6.1.4.1.6027.3.24.2.1.4.1.3 integer no-access
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
                       bpBufferStatsCurrentUsagePerPort 1.3.6.1.4.1.6027.3.24.2.1.4.1.4 counter32 read-only
Current buffer usage per bp port.
                       bpBufferStatsDefaultPacketBuffAlloc 1.3.6.1.4.1.6027.3.24.2.1.4.1.5 counter32 read-only
Default packet buffer allocated.
                       bpBufferStatsMaxLimitPerPort 1.3.6.1.4.1.6027.3.24.2.1.4.1.6 counter32 read-only
Max buffer limit per bp port.
               bpCosStatsTable 1.3.6.1.4.1.6027.3.24.2.1.5 no-access
The back plane statistics per COS table gives packet buffer statistics per COS per bp port.
                   bpCosStatsEntry 1.3.6.1.4.1.6027.3.24.2.1.5.1 no-access
Per bp port buffer stats and per COS buffer stats.
                       bpCosStatsStackUnitIndex 1.3.6.1.4.1.6027.3.24.2.1.5.1.1 integer no-access
Stack unit(Card Type Id) number where this port present Each card shall contain more than one BCM units
                       bpCosStatsPortPipe 1.3.6.1.4.1.6027.3.24.2.1.5.1.2 integer no-access
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
                       bpCosStatsPortIndex 1.3.6.1.4.1.6027.3.24.2.1.5.1.3 integer no-access
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
                       bpCosStatsCOSNumber 1.3.6.1.4.1.6027.3.24.2.1.5.1.4 integer no-access
COS queue number, There shall 10 unicast and 5 multicast queues per port in Trident2
                       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.
                       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
                       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.
                       bpCosStatsHOLDDrops 1.3.6.1.4.1.6027.3.24.2.1.5.1.8 counter64 read-only
HOLD Drops Per Queue.
       f10BpStatsAlarms 1.3.6.1.4.1.6027.3.24.3
           bpLinkBundleNotifications 1.3.6.1.4.1.6027.3.24.3.1
               bpLinkBundleImbalance 1.3.6.1.4.1.6027.3.24.3.1.1
Trap generated when traffic imbalance observed in BP Link Bundles
               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
           bpLinkBundleAlarmVariable 1.3.6.1.4.1.6027.3.24.3.2
               bpLinkBundleType 1.3.6.1.4.1.6027.3.24.3.2.1 integer no-access
Indicates Type of Back plane HiGig link bundle Enumeration: 'unknown': 1, 'bpHgBundle': 2.
               bpLinkBundleSlot 1.3.6.1.4.1.6027.3.24.3.2.2 integer no-access
The SlotId on which Link Bundle is overloaded
               bpLinkBundleNpuUnit 1.3.6.1.4.1.6027.3.24.3.2.3 integer no-access
The npuUnitId(BCM unit Id) on which Link Bundle is overloaded
               bpLinkBundleLocalId 1.3.6.1.4.1.6027.3.24.3.2.4 integer no-access
The local linkBundle Id which is overloaded