F10-BPSTATS-MIB Table View

Table-centric layout grouping table, row, and column objects.

Tables
5
Rows
5
Columns
62

bpDropsTable

table
.1.3.6.1.4.1.6027.3.24.2.1.1 · 1 row entry · 14 columns
Uses the force10 variant from /opt/observium/mibs/force10.
Command help
Walk bpDropsTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'F10-BPSTATS-MIB' -M '/opt/observium/mibs/force10:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'F10-BPSTATS-MIB::bpDropsTable'
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 row .1.3.6.1.4.1.6027.3.24.2.1.1.1
Each drops entry is being indexed by StackUnit(card Type)
BCM unit ID and local Port Id
Column Syntax OID
Stack unit(Card Type Id) number where this port present
Each card shall contain more than one BCM units
Integer32
Constraints:
range: 1-12
.1.3.6.1.4.1.6027.3.24.2.1.1.1.1
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
Integer32
Constraints:
range: 1-6
.1.3.6.1.4.1.6027.3.24.2.1.1.1.2
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 po…
Integer32
Constraints:
range: 1-128
.1.3.6.1.4.1.6027.3.24.2.1.1.1.3
The No of Ingress packet Drops
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.1.1.4
The No of Unknown hiGig header Ingress packet Drops
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.1.1.5
The No of Unknown hiGig Opcode Ingress packet Drops
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.1.1.6
No of packets dropped on Ingress because of
MTUExceeds
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.1.1.7
No of packets dropped on Ingress MAC
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.1.1.8
No of packets dropped in MMU because of
MMU HOL Drops
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.1.1.9
No of packets dropped on Egress MAC
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.1.1.10
No of Aged packets dropped on Egress
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.1.1.11
No of Error packets dropped on Egress
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.1.1.12
No of MAC underflow packets dropped on Egress
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.1.1.13
No of total packets dropped in Egress
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.1.1.14
.1.3.6.1.4.1.6027.3.24.2.1.2 · 1 row entry · 29 columns
Uses the force10 variant from /opt/observium/mibs/force10.
Command help
Walk bpIfStatsTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'F10-BPSTATS-MIB' -M '/opt/observium/mibs/force10:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'F10-BPSTATS-MIB::bpIfStatsTable'
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 row .1.3.6.1.4.1.6027.3.24.2.1.2.1
Each Stats entry is being indexed by StackUnit(card Type)
BCM unit ID and local Port Id
Column Syntax OID
Stack unit(Card Type Id) number where this port present
Each card shall contain more than one BCM units
Integer32
Constraints:
range: 1-12
.1.3.6.1.4.1.6027.3.24.2.1.2.1.1
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
Integer32
Constraints:
range: 1-6
.1.3.6.1.4.1.6027.3.24.2.1.2.1.2
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 por…
Integer32
Constraints:
range: 1-128
.1.3.6.1.4.1.6027.3.24.2.1.2.1.3
The total number of frames (including bad
frames) received that were 64 octets in length
(excluding framing bits but including FCS octets).
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.4
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).
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.5
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).
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.6
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).
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.7
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).
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.8
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
f…
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.9
This counter is incremented when a valid
frame with a length or type field value equal
to 0x8808 (Control Frame) is received.
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.10
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.
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.11
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 f…
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.12
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.
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.13
The total number of frames has been chosen to be
dropped by detecting the buffer issue
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.14
The total number of frames dropped because
of buffer underrun.
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.15
The total number of Unicast frames are transmitted
out of the interface
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.16
A count of the frames that due to excessive
or late collisions are not transmitted successfully.
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.17
The total number of frames are dropped by using
WRED policy due to excessive traffic.
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.18
The total number of valid frames with the
block of 64 byte size is transmitted
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.19
The total of valid frame with the block size of
range between 65 and 127 bytes are transmitted.
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.20
The total of valid frame with the block size of
range between 128 and 255 bytes are transmitted
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.21
The total of valid frame with the block size of
range between 256 and 511 bytes are transmitted
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.22
The total of valid frame with the block size of
range between 512 and 1023 bytes are transmitted
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.23
The total of valid frame with the block size of
greater than 1023 bytes are transmitted.
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.24
This counter is incremented when a valid
frame with a length or type field value equal
to 0x8808 (Control Frame) is sent.
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.2.1.25
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 managemen…
SNMPv2-TCTimeStamp
Based On: SNMPv2-SMITimeTicks
Description:
The value of the sysUpTime object at which a specific
occurrence happened. The specific occurrence must be

defined in the description of any object defined using this
type.

If sysUpTime is reset t…
.1.3.6.1.4.1.6027.3.24.2.1.2.1.26
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%.
Integer32
Constraints:
range: 0-100
.1.3.6.1.4.1.6027.3.24.2.1.2.1.27
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%.
Integer32
Constraints:
range: 0-100
.1.3.6.1.4.1.6027.3.24.2.1.2.1.28
The value of sysUpTime, on which all the counters are
updated recently
SNMPv2-TCTimeStamp
Based On: SNMPv2-SMITimeTicks
Description:
The value of the sysUpTime object at which a specific
occurrence happened. The specific occurrence must be

defined in the description of any object defined using this
type.

If sysUpTime is reset t…
.1.3.6.1.4.1.6027.3.24.2.1.2.1.29
.1.3.6.1.4.1.6027.3.24.2.1.3 · 1 row entry · 5 columns
Uses the force10 variant from /opt/observium/mibs/force10.
Command help
Walk bpPacketBufferTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'F10-BPSTATS-MIB' -M '/opt/observium/mibs/force10:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'F10-BPSTATS-MIB::bpPacketBufferTable'
The packet buffer table contains the modular packet buffers details
per stack unit and the mode of allocation.
bpPacketBufferEntry row .1.3.6.1.4.1.6027.3.24.2.1.3.1
Packet buffer details per NPU unit.
Column Syntax OID
Stack unit(Card Type Id) number where this port present
Each card shall contain more than one BCM units
Integer32
Constraints:
range: 1-12
.1.3.6.1.4.1.6027.3.24.2.1.3.1.1
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
Integer32
Constraints:
range: 1-6
.1.3.6.1.4.1.6027.3.24.2.1.3.1.2
Total packet buffer in this NPU unit.
SNMPv2-SMICounter32
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.6027.3.24.2.1.3.1.3
Current available buffer in this NPU unit.
SNMPv2-SMICounter32
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.6027.3.24.2.1.3.1.4
Static or Dynamic allocation.
SNMPv2-SMICounter32
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.6027.3.24.2.1.3.1.5
.1.3.6.1.4.1.6027.3.24.2.1.4 · 1 row entry · 6 columns
Uses the force10 variant from /opt/observium/mibs/force10.
Command help
Walk bpBufferStatsTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'F10-BPSTATS-MIB' -M '/opt/observium/mibs/force10:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'F10-BPSTATS-MIB::bpBufferStatsTable'
The back plane stats per port table  contains
the packet buffer usage per bp port per NPU unit.
bpBufferStatsEntry row .1.3.6.1.4.1.6027.3.24.2.1.4.1
Per bp port buffer stats
Column Syntax OID
Stack unit(Card Type Id) number where this port present
Each card shall contain more than one BCM units
Integer32
Constraints:
range: 1-12
.1.3.6.1.4.1.6027.3.24.2.1.4.1.1
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
Integer32
Constraints:
range: 1-6
.1.3.6.1.4.1.6027.3.24.2.1.4.1.2
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 por…
Integer32
Constraints:
range: 1-128
.1.3.6.1.4.1.6027.3.24.2.1.4.1.3
Current buffer usage per bp port.
SNMPv2-SMICounter32
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.6027.3.24.2.1.4.1.4
Default packet buffer allocated.
SNMPv2-SMICounter32
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.6027.3.24.2.1.4.1.5
Max buffer limit per bp port.
SNMPv2-SMICounter32
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.6027.3.24.2.1.4.1.6
.1.3.6.1.4.1.6027.3.24.2.1.5 · 1 row entry · 8 columns
Uses the force10 variant from /opt/observium/mibs/force10.
Command help
Walk bpCosStatsTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'F10-BPSTATS-MIB' -M '/opt/observium/mibs/force10:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'F10-BPSTATS-MIB::bpCosStatsTable'
The back plane statistics per COS table gives
packet buffer statistics per COS per bp port.
bpCosStatsEntry row .1.3.6.1.4.1.6027.3.24.2.1.5.1
Per bp port buffer stats and per COS buffer stats.
Column Syntax OID
Stack unit(Card Type Id) number where this port present
Each card shall contain more than one BCM units
Integer32
Constraints:
range: 1-12
.1.3.6.1.4.1.6027.3.24.2.1.5.1.1
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
Integer32
Constraints:
range: 1-6
.1.3.6.1.4.1.6027.3.24.2.1.5.1.2
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 por…
Integer32
Constraints:
range: 1-128
.1.3.6.1.4.1.6027.3.24.2.1.5.1.3
COS queue number, There shall 10 unicast and 5 multicast
queues per port in Trident2
Integer32
Constraints:
range: 1-15
.1.3.6.1.4.1.6027.3.24.2.1.5.1.4
Current buffer usage per COS per bp port.
SNMPv2-SMICounter32
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.6027.3.24.2.1.5.1.5
Default packet buffer allocated per COS queue
SNMPv2-SMICounter32
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.6027.3.24.2.1.5.1.6
Max buffer utilization limit per bp port.
SNMPv2-SMICounter32
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.6027.3.24.2.1.5.1.7
HOLD Drops Per Queue.
SNMPv2-SMICounter64
Type Constraints:
range: 0..18446744073709551615
.1.3.6.1.4.1.6027.3.24.2.1.5.1.8