PRVT-SWITCH-MIB

MIB Reference — IPNetwork Monitor

All MIBsPRVT-SWITCH-MIB

Organization: BATM Advanced Communication

Last Updated: 2009-06-22

Category: VLAN Management

Description:

Handles global configuration, port parameters, and device capabilities for BATM Advanced Communication carrier Ethernet switches.

Imported Objects

From IF-MIB

ifAdminStatusOBJECT-TYPE
ifIndexOBJECT-TYPE
ifOperStatusOBJECT-TYPE

From PRIV-VENDORDEF-MIB

privateVendorOIDMODULE-IDENTITY

From SNMPv2-CONF

NOTIFICATION-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION
TruthValue

What Is PRVT-SWITCH-MIB?

PRVT-SWITCH-MIB is a proprietary BATM Advanced Communication MIB providing core system and chassis management for their carrier Ethernet switch platform, covering global switch parameters, per-slot/interface inventory, and device identification. It exposes hardware inventory fields such as system serial number, switch model, assembly and part numbers, and CLEI code, alongside a system interface table (sysIntfTable) describing stack/slot/unit/module presence. This MIB is fundamentally about hardware inventory and slot-level status monitoring: administrators use it to confirm which physical modules are installed in each stack/slot position (sysStackNo, sysSlotNo, sysIntfUnitExist) and to verify the exact hardware model and serial number for asset management or support purposes. It underpins other BATM proprietary MIBs on the same platform (such as PRVT-SERV-MIB, PRVT-ELMI-MIB, and PRVT-L2TUNNELING-MIB) which reference the interfaces and switch identity this module defines. It is deployed on BATM carrier Ethernet switches used by service providers for Metro/Carrier Ethernet access and aggregation, and every hardware inventory object described above sits under the PRVT-SWITCH-MIB OID subtree, making it straightforward to locate in a MIB browser during an asset audit.

IPNetwork Monitor allows you to monitor SNMP objects defined in PRVT-SWITCH-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.

What Can Be Monitored

  • slot/module presence
  • switch model and serial number
  • assembly/part number identification
  • stack and slot topology
  • CLEI code

Supported Devices

  • BATM Advanced Communications (Telco Systems) T-Series carrier Ethernet switches, e.g. TM-3348 10G Service Demarcation Device

Monitoring Examples

An operator would poll sysIntfTable to enumerate every sysIntfEntry, checking sysIntfUnitExist and sysIntfModule to confirm expected line cards are physically present in each sysStackNo/sysSlotNo position across a stacked chassis. sysSerialNumber, sysSwitchModel, and sysCLEI together let an inventory system record exact hardware identity for compliance or RMA purposes. A slot reporting sysIntfUnitExist as false when a module was expected to be installed would indicate a hardware seating or backplane issue.

OIDs
OID symbolicOID numericTypeAccessDescription
prvt_products1.3.6.1.4.1.738.1
rptr1.3.6.1.4.1.738.1.1
bridge1.3.6.1.4.1.738.1.2
trclam1.3.6.1.4.1.738.1.3
router1.3.6.1.4.1.738.1.4
switch1.3.6.1.4.1.738.1.5
bsw1.3.6.1.4.1.738.1.5.1
tps1.3.6.1.4.1.738.1.5.2
tpf1.3.6.1.4.1.738.1.5.3
titan1.3.6.1.4.1.738.1.5.5
titant51.3.6.1.4.1.738.1.5.7
edgeLinkT41.3.6.1.4.1.738.1.5.15
edgeLinkT51.3.6.1.4.1.738.1.5.17
titanPro1.3.6.1.4.1.738.1.5.20
prvtSwitchMib1.3.6.1.4.1.738.1.5.100The switch MIB module for managing switch parameters
prvtSwitchNotifications1.3.6.1.4.1.738.1.5.100.0
NTF cpuTemperatureExceeded1.3.6.1.4.1.738.1.5.100.0.1The cpuTemperatuteExceeded trap indicates that the sending agent senses that the internal temperature has passed the program threshold.
NTF powerSupplyStatusChange1.3.6.1.4.1.738.1.5.100.0.2The powerSupplyStatusChange trap indicates that the sending agent senses a change in the status of one of the power supplies.
NTF fanStatusChange1.3.6.1.4.1.738.1.5.100.0.3The fanStatusChange trap indicates that the sending agent senses a change in the status of one of the fans.
NTF portSecurityViolation1.3.6.1.4.1.738.1.5.100.0.4The port security violation notification indicates that a port security violation has been detected, e.g more MAC adresses have been learned on that port than the number allowed.
NTF portRedundantLinkChange1.3.6.1.4.1.738.1.5.100.0.5The port redundant link change notification indicates that the physical state of a redundant (i.e. blocked or discarding) link has changed from link-up to link down or vice versa.
NTF sysIntfModuleChange1.3.6.1.4.1.738.1.5.100.0.6The System Interface Module change notification indicates that the physical status of a module in the unit has changed.
NTF prvtLogNotifyFull1.3.6.1.4.1.738.1.5.100.0.7Log buffer is almost full.
NTF doorStatusChange1.3.6.1.4.1.738.1.5.100.0.8The doorStatusChange trap indicates that the sending agent senses a change in the status of the door.
sys1.3.6.1.4.1.738.1.5.100.1
sysProductsOids1.3.6.1.4.1.738.1.5.100.1.1
t4Router1.3.6.1.4.1.738.1.5.100.1.1.1
t5Router1.3.6.1.4.1.738.1.5.100.1.1.2
t5ProRouter1.3.6.1.4.1.738.1.5.100.1.1.3
t6Router1.3.6.1.4.1.738.1.5.100.1.1.4
t5c_48TRouter1.3.6.1.4.1.738.1.5.100.1.1.5
t5RNRouter1.3.6.1.4.1.738.1.5.100.1.1.6
t5c_24TRouter1.3.6.1.4.1.738.1.5.100.1.1.7
as92051.3.6.1.4.1.738.1.5.100.1.1.7.1
t5c_24MRouter1.3.6.1.4.1.738.1.5.100.1.1.8
t5c_24FRouter1.3.6.1.4.1.738.1.5.100.1.1.9
as9205_F1.3.6.1.4.1.738.1.5.100.1.1.9.1
t5c_24GRouter1.3.6.1.4.1.738.1.5.100.1.1.10
t5c_24GTRouter1.3.6.1.4.1.738.1.5.100.1.1.11
t6pro_lc_20G1.3.6.1.4.1.738.1.5.100.1.1.13
t6pro_cpm1.3.6.1.4.1.738.1.5.100.1.1.14
compact1.3.6.1.4.1.738.1.5.100.1.1.14.1
classic1.3.6.1.4.1.738.1.5.100.1.1.14.2
tMetro1.3.6.1.4.1.738.1.5.100.1.1.16
alcatel_72501.3.6.1.4.1.738.1.5.100.1.1.16.1
tMarc1.3.6.1.4.1.738.1.5.100.1.1.17
tMarc_2501.3.6.1.4.1.738.1.5.100.1.1.17.1
dm92251.3.6.1.4.1.738.1.5.100.1.1.17.1.1
tMarc_2541.3.6.1.4.1.738.1.5.100.1.1.17.2
dm9225_E1.3.6.1.4.1.738.1.5.100.1.1.17.2.1
tMarc_254h1.3.6.1.4.1.738.1.5.100.1.1.17.3
tMarc_3401.3.6.1.4.1.738.1.5.100.1.1.17.10
dm92341.3.6.1.4.1.738.1.5.100.1.1.17.10.1
tMarc_3801.3.6.1.4.1.738.1.5.100.1.1.17.11
tMarc_2801.3.6.1.4.1.738.1.5.100.1.1.17.20
aHUB1_A1.3.6.1.4.1.738.1.5.100.1.1.18
bI_Ethernet1.3.6.1.4.1.738.1.5.100.1.1.18.1
fI_Ethernet1.3.6.1.4.1.738.1.5.100.1.1.18.2
tMetro_ES1.3.6.1.4.1.738.1.5.100.1.1.19
alcatel_7250_ES1.3.6.1.4.1.738.1.5.100.1.1.19.1
alcatel_7250_ESA1.3.6.1.4.1.738.1.5.100.1.1.19.2
tMetro_ESA1.3.6.1.4.1.738.1.5.100.1.1.19.3
as92201.3.6.1.4.1.738.1.5.100.1.1.19.10
tMetro_200S1.3.6.1.4.1.738.1.5.100.1.1.19.11
tMarc_E1.3.6.1.4.1.738.1.5.100.1.1.20
tMarc_340_E1.3.6.1.4.1.738.1.5.100.1.1.20.1
tMarc_380_E1.3.6.1.4.1.738.1.5.100.1.1.20.2
tMarc_EW1.3.6.1.4.1.738.1.5.100.1.1.21
tMarc_340_EW1.3.6.1.4.1.738.1.5.100.1.1.21.1
tMarc_380_EW1.3.6.1.4.1.738.1.5.100.1.1.21.2
tMarc_WDB1.3.6.1.4.1.738.1.5.100.1.1.22
tMarc_340WD_B1.3.6.1.4.1.738.1.5.100.1.1.22.1
tMarc_WD1.3.6.1.4.1.738.1.5.100.1.1.23
tMarc_340WD1.3.6.1.4.1.738.1.5.100.1.1.23.1
tMarc_F1.3.6.1.4.1.738.1.5.100.1.1.24
tMarc_340_F1.3.6.1.4.1.738.1.5.100.1.1.24.1
t5c_XG1.3.6.1.4.1.738.1.5.100.1.1.27
as92151.3.6.1.4.1.738.1.5.100.1.1.27.1
t5c1.3.6.1.4.1.738.1.5.100.1.1.100
t5cgt1.3.6.1.4.1.738.1.5.100.1.1.222
t5g1.3.6.1.4.1.738.1.5.100.1.1.333
v24s1.3.6.1.4.1.738.1.5.100.1.1.444
edgeGate2811.3.6.1.4.1.738.1.5.100.1.1.1000
edgeGate281SYS1.3.6.1.4.1.738.1.5.100.1.1.1001
edgeGate2311.3.6.1.4.1.738.1.5.100.1.1.1010
edgeGate2821.3.6.1.4.1.738.1.5.100.1.1.1020
edgeGate282S1.3.6.1.4.1.738.1.5.100.1.1.1021
edgeGate482S1.3.6.1.4.1.738.1.5.100.1.1.1022
edgeGate483S1.3.6.1.4.1.738.1.5.100.1.1.1023
edgeGate483D1.3.6.1.4.1.738.1.5.100.1.1.1024
edgeGate2011.3.6.1.4.1.738.1.5.100.1.1.1031
edgeGate2321.3.6.1.4.1.738.1.5.100.1.1.1041
ac5001.3.6.1.4.1.738.1.5.100.1.1.1050
ac5051.3.6.1.4.1.738.1.5.100.1.1.1050.1
ac5121.3.6.1.4.1.738.1.5.100.1.1.1050.2
ac5241.3.6.1.4.1.738.1.5.100.1.1.1050.3
sysIntf1.3.6.1.4.1.738.1.5.100.1.2
sysIntfTable1.3.6.1.4.1.738.1.5.100.1.2.1not-accessibleThis table contains the interfaces module type.
sysIntfEntry1.3.6.1.4.1.738.1.5.100.1.2.1.1not-accessiblesysIntfEntry
UNI sysStackNo1.3.6.1.4.1.738.1.5.100.1.2.1.1.1UnitIndexread-onlyThis object identifies the switch
I32 sysSlotNo1.3.6.1.4.1.738.1.5.100.1.2.1.1.2Integer32read-onlyThis indicates a single instance of a slot
INT sysIntfUnitExist1.3.6.1.4.1.738.1.5.100.1.2.1.1.3INTEGERread-onlyThis indicates interface module type
MOD sysIntfModule1.3.6.1.4.1.738.1.5.100.1.2.1.1.4ModuleHwTyperead-onlyThis indicates interface module type
sysManufacturing1.3.6.1.4.1.738.1.5.100.1.3
STR sysSerialNumber1.3.6.1.4.1.738.1.5.100.1.3.1DisplayStringread-onlyThis is the device's serial number, which is entered during the manufacturing process.
STR sysSwitchModel1.3.6.1.4.1.738.1.5.100.1.3.2DisplayStringread-onlySpecifies the equipment model
STR sysAssemblyNumber1.3.6.1.4.1.738.1.5.100.1.3.3DisplayStringread-onlySpecifies the equipment assembly number
STR sysPartNumber1.3.6.1.4.1.738.1.5.100.1.3.4DisplayStringread-onlySpecifies the equipment part number
STR sysCLEI1.3.6.1.4.1.738.1.5.100.1.3.5DisplayStringread-onlySpecifies the common language equipment identification
STR sysHwRevision1.3.6.1.4.1.738.1.5.100.1.3.6DisplayStringread-onlySpecifies the HW revision
STR sysManufacturingDate1.3.6.1.4.1.738.1.5.100.1.3.7DisplayStringread-onlySpecifies the manufacturing date
sysSwitchingHW1.3.6.1.4.1.738.1.5.100.1.4
SER sysSwitchSeries1.3.6.1.4.1.738.1.5.100.1.4.1Seriesread-onlyThis object displays the switch series.
config1.3.6.1.4.1.738.1.5.100.2
configL21.3.6.1.4.1.738.1.5.100.2.2
INT configL2SpanOnOff1.3.6.1.4.1.738.1.5.100.2.2.1INTEGERread-writeEnables/disables Spanning Tree. When Spanning Tree is disabled, the switch's ports are placed in forwarding mode, regardless of the current Spanning Tree state. When re-enabled, the normal state transitions take place.
configL2IfaceTable1.3.6.1.4.1.738.1.5.100.2.2.2not-accessibleA list of Interfaces and their properties
configL2IfaceEntry1.3.6.1.4.1.738.1.5.100.2.2.2.1not-accessibleAn index of interfaces.
I32 configL2IfaceUnit1.3.6.1.4.1.738.1.5.100.2.2.2.1.1Integer32read-onlyAn index that uniquely identifies a unit in the Interface Table.
I32 configL2IfaceSlot1.3.6.1.4.1.738.1.5.100.2.2.2.1.2Integer32read-onlyAn index that uniquely identifies a slot within the unit in the Interface Table.
I32 configL2IfacePort1.3.6.1.4.1.738.1.5.100.2.2.2.1.3Integer32read-onlyAn index that uniquely identifies a port within the slot in the Interface Table.
STR configL2IfaceName1.3.6.1.4.1.738.1.5.100.2.2.2.1.4DisplayStringread-writeThe textual name of this interface, e.g., 'John'.
INT configL2IfaceEnable1.3.6.1.4.1.738.1.5.100.2.2.2.1.5INTEGERread-writeEnables (1)or disables (2) control for the interface. For this product, this is the ONLY way to enable or disable the interface. 'ifAdminStatus' in RFC1213 and 'dot1dStpPortEnable' in RFC1493 are both implemented as 'read-only'.
INT configL2IfaceSTPEnable1.3.6.1.4.1.738.1.5.100.2.2.2.1.6INTEGERread-writeEnables (1) and disables (2) Spanning Tree operation for this interface.
INT configL2IfaceDuplexSpeedSet1.3.6.1.4.1.738.1.5.100.2.2.2.1.7INTEGERread-writeThe desired speed and duplex mode for the interface. If the selected control is not available for the interface, a value of illegal (99) is returned. If the port type does NOT support the default of autonegotiate (1), then the application will initialize the port to a valid value (e.g., 1000full (6)). Note that not all controls are available for all interfaces. For example, only full-1000 (6) is available for Gigabit Ethernet interfaces. As this object was marked as obsolete the following two configurable parameters of an interface should be used: configL2IfaceDuplexModeSet, configL2IfaceSpeedSet
INT configL2IfaceFlow1.3.6.1.4.1.738.1.5.100.2.2.2.1.8INTEGERread-writeThe desired flow mode for the interface. If the selected control is not available on the interface, a value of illegal (99) is returned. If the port type does NOT support the default value of autonegotiate (1), then the application will initialize the port to a valid value (e.g., 1000full (6)).Note that not all controls are available for all interfaces. For example, only full-1000 (6) is available for Gigabit Ethernet interfaces.
INT configL2IfaceBackpressure1.3.6.1.4.1.738.1.5.100.2.2.2.1.9INTEGERread-writeThe desired back-pressure mode for the interface. If the selected control is not available on the interface, a value of illegal (99) is returned.
INT configL2IfaceResetCounters1.3.6.1.4.1.738.1.5.100.2.2.2.1.10INTEGERread-writeThis object enables resetting the statistics counters selected for this port.
I32 configL2IfaceDefaultVID1.3.6.1.4.1.738.1.5.100.2.2.2.1.11Integer32read-writeThis object sets the default VLAN ID according to 802.1Q.
I32 configL2IfaceSnifferIfIndex1.3.6.1.4.1.738.1.5.100.2.2.2.1.12Integer32read-writeThis object connects this port to a sniffer port indexed by the specified ifIndex. Setting this value to 0 disconnects this port from the sniffer.
T/F configL2TopologyChangeDetection1.3.6.1.4.1.738.1.5.100.2.2.2.1.13TruthValueread-writeThis object controls the STP topology change detection for this interface.
INT configL2IfaceDuplexModeSet1.3.6.1.4.1.738.1.5.100.2.2.2.1.14INTEGERread-writeThe duplex mode for the interface. If the port type does NOT support the default of autonegotiate (1), then the application will initialize the port to a valid value (e.g., full (2)).
INT configL2IfaceSpeedSet1.3.6.1.4.1.738.1.5.100.2.2.2.1.15INTEGERread-writeThe desired speed and duplex mode for the interface. If the selected control is not available for the interface, a value of illegal (99) is returned. If the port type does NOT support the default of autonegotiate (1), then the application will initialize the port to a valid value (e.g., 1000 (3)). Note that not all controls are available for all interfaces. For example, only 1000 (4) is available for Gigabit Ethernet interfaces.
I32 configL2IfaceBroadcastRateLimit1.3.6.1.4.1.738.1.5.100.2.2.2.1.16Integer32read-writeRate limit broadcast traffic. Must be a number between 64Kbps and 1Gbps, specified in Kbps.
I32 configL2IfaceMulticastRateLimit1.3.6.1.4.1.738.1.5.100.2.2.2.1.17Integer32read-writeRate limit multicast traffic. Must be a number between 64Kbps and 1Gbps, specified in Kbps.
I32 configL2IfaceUnknownRateLimit1.3.6.1.4.1.738.1.5.100.2.2.2.1.18Integer32read-writeRate limit unknown traffic. Must be a number between 64Kbps and 1Gbps, specified in Kbps. For detail information see documentation.
I32 configL2IfaceBroadcastBurstSize1.3.6.1.4.1.738.1.5.100.2.2.2.1.19Integer32read-writeBurst size broadcast traffic. Must be a number between 12Kbps and 1Mbps, specified in Kbps.
I32 configL2IfaceMulticastBurstSize1.3.6.1.4.1.738.1.5.100.2.2.2.1.20Integer32read-writeBurst size multicast traffic. Must be a number between 12Kbps and 1Mbps, specified in Kbps.
I32 configL2IfaceUnknownBurstSize1.3.6.1.4.1.738.1.5.100.2.2.2.1.21Integer32read-writeBurst size unknown traffic. Must be a number between 12Kbps and 1Mbps, specified in Kbps. For detail information see documentation.
I32 configL2IfaceMtu1.3.6.1.4.1.738.1.5.100.2.2.2.1.22Integer32read-writeThe Maximum Transmission Unit (in octets) of the interface.
INT configL2IfaceAdminCrossOver1.3.6.1.4.1.738.1.5.100.2.2.2.1.23INTEGERread-writeThe administrative MDI/MDI-X cable connection status of ports, as specified in IEEE 803.2. The mdi-x mode (crossover) is configured (3), the interface works in MDI-X mode. The mdi mode (2) defines port to work in standard MDI mode. The auto (1) defines automatic crossover detection, and any type of MDI/MDI-X cabling can be used on the port. Note: This attribute can be configured only on interfaces that support that option.
INT configL2IfaceRemoteFaultDetect1.3.6.1.4.1.738.1.5.100.2.2.2.1.24INTEGERread-writeControls the remote fault detection on interfaces, connected to 100Base Fiber pair. Once enabled (1), the switch will indicate link-down event on the interface, once remote peer detects link down. Note: Relevant only on 100Base Fiber interfaces.
reports1.3.6.1.4.1.738.1.5.100.3
reportsL21.3.6.1.4.1.738.1.5.100.3.1
reportsL2IfaceTable1.3.6.1.4.1.738.1.5.100.3.1.1not-accessibleA list of Interfaces and their properties
reportsL2IfaceEntry1.3.6.1.4.1.738.1.5.100.3.1.1.1not-accessibleAn index of interfaces.
I32 reportsL2IfaceUnit1.3.6.1.4.1.738.1.5.100.3.1.1.1.1Integer32read-onlyAn index that uniquely identifies a unit in the Interface Table.
I32 reportsL2IfaceSlot1.3.6.1.4.1.738.1.5.100.3.1.1.1.2Integer32read-onlyAn index that uniquely identifies a slot within the unit in the Interface Table.
I32 reportsL2IfacePort1.3.6.1.4.1.738.1.5.100.3.1.1.1.3Integer32read-onlyAn index that uniquely identifies a port within the slot in the Interface Table.
I32 reportsL2IfaceBridgeIndex1.3.6.1.4.1.738.1.5.100.3.1.1.1.4Integer32read-onlyThis is the bridge index of this port.
INT reportsL2IfaceType1.3.6.1.4.1.738.1.5.100.3.1.1.1.5INTEGERread-onlyThe type of interface, repeated here from the definitions in RFC1213 as a matter of convenience.
INT reportsL2IfaceLink1.3.6.1.4.1.738.1.5.100.3.1.1.1.6INTEGERread-onlyThe state of Link Detect on the interface.
INT reportsL2IfaceDuplexSpeedGet1.3.6.1.4.1.738.1.5.100.3.1.1.1.7INTEGERread-onlyThe actual speed and duplex for the interface. If the interface is not configured to one of the acceptable values, a value of illegal (99) is returned.
C32 reportsL2IfaceTXOctetsNoErr1.3.6.1.4.1.738.1.5.100.3.1.1.1.8Counter32read-onlyThe number of octets transmitted from the interface. This number does not include octets with errors.
C32 reportsL2IfaceTXPacketsNoErr1.3.6.1.4.1.738.1.5.100.3.1.1.1.9Counter32read-onlyThe number of packets transmitted from the interface. This number does not include packets with errors.
C32 reportsL2IfaceRXOctetsNoErr1.3.6.1.4.1.738.1.5.100.3.1.1.1.10Counter32read-onlyThe number of octets received on the interface. This number does not include octets with errors.
C32 reportsL2IfaceRXPacketsNoErr1.3.6.1.4.1.738.1.5.100.3.1.1.1.11Counter32read-onlyThe number of packets received on the interface. This number does not include packets with errors.
C32 reportsL2IfaceIfInOctets1.3.6.1.4.1.738.1.5.100.3.1.1.1.12Counter32read-onlyThe total number of octets received on the interface, including framing characters.
C32 reportsL2IfaceIfInUcastPkts1.3.6.1.4.1.738.1.5.100.3.1.1.1.13Counter32read-onlyThe number of subnetwork-unicast packets delivered to a higher-layer protocol.
C32 reportsL2IfaceIfInNUcastPkts1.3.6.1.4.1.738.1.5.100.3.1.1.1.14Counter32read-onlyThe number of non-unicast (i.e., subnetwork- broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.
C32 reportsL2IfaceIfInDiscards1.3.6.1.4.1.738.1.5.100.3.1.1.1.15Counter32read-onlyThe number of inbound packets that were chosen to be discarded even if no errors that prevent their deliverability to a higher-layer protocol had been detected. One possible reason for discarding such a packet could be to free buffer space.
C32 reportsL2IfaceIfInErrors1.3.6.1.4.1.738.1.5.100.3.1.1.1.16Counter32read-onlyThe number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
C32 reportsL2IfaceIfInUnknownProtos1.3.6.1.4.1.738.1.5.100.3.1.1.1.17Counter32read-onlyThe number of packets received via the interface that were discarded because of an unknown or unsupported protocol.
C32 reportsL2IfaceIfOutOctets1.3.6.1.4.1.738.1.5.100.3.1.1.1.18Counter32read-onlyThe total number of octets transmitted out of the interface, including framing characters.
C32 reportsL2IfaceIfOutUcastPkts1.3.6.1.4.1.738.1.5.100.3.1.1.1.19Counter32read-onlyThe total number of packets that higher-level protocols requested to be transmitted to a subnetwork-unicast address, including those that were discarded or not sent.
C32 reportsL2IfaceIfOutNUcastPkts1.3.6.1.4.1.738.1.5.100.3.1.1.1.20Counter32read-onlyThe total number of packets that higher-level protocols requested to be transmitted to a non- unicast (i.e., a subnetwork-broadcast or subnetwork-multicast) address, including those that were discarded or not sent.
C32 reportsL2IfaceIfOutDiscards1.3.6.1.4.1.738.1.5.100.3.1.1.1.21Counter32read-onlyThe number of outbound packets that were chosen to be discarded even if no errors that prevented their transmission had been detected. One possible reason for discarding such a packet could be to free up buffer space.
C32 reportsL2IfaceIfOutErrors1.3.6.1.4.1.738.1.5.100.3.1.1.1.22Counter32read-onlyThe number of outbound packets that could not be transmitted because of errors.
C32 reportsL2IfaceStatsDropEvents1.3.6.1.4.1.738.1.5.100.3.1.1.1.23Counter32read-onlyThe total number of events in which packets were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected.
C32 reportsL2IfaceStatsOctets1.3.6.1.4.1.738.1.5.100.3.1.1.1.24Counter32read-onlyThe total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets). This object can be used as a reasonable estimate of Ethernet utilization. If greater precision is desired, the etherStatsPkts and etherStatsOctets objects should be sampled before and after a common interval. The differences in the sampled values are Pkts and Octets, respectively, and the number of seconds in the interval is Interval. These values are used to calculate the Utilization as follows: Pkts * (9.6 + 6.4) + (Octets * .8) Utilization = ------------------------------------- Interval * 10,000 The result of this equation is the Ethernet segment utilization which is the percent utilization of the ethernet segment on a 0 to 100 percent scale.
C32 reportsL2IfaceStatsPkts1.3.6.1.4.1.738.1.5.100.3.1.1.1.25Counter32read-onlyThe total number of packets (including bad packets, broadcast packets, and multicast packets) received.
C32 reportsL2IfaceStatsBroadcastPkts1.3.6.1.4.1.738.1.5.100.3.1.1.1.26Counter32read-onlyThe total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.
C32 reportsL2IfaceStatsMulticastPkts1.3.6.1.4.1.738.1.5.100.3.1.1.1.27Counter32read-onlyThe total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address.
C32 reportsL2IfaceStatsCRCAlignErrors1.3.6.1.4.1.738.1.5.100.3.1.1.1.28Counter32read-onlyThe total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
C32 reportsL2IfaceStatsUndersizePkts1.3.6.1.4.1.738.1.5.100.3.1.1.1.29Counter32read-onlyThe total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.
C32 reportsL2IfaceStatsOversizePkts1.3.6.1.4.1.738.1.5.100.3.1.1.1.30Counter32read-onlyThe total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.
C32 reportsL2IfaceStatsFragments1.3.6.1.4.1.738.1.5.100.3.1.1.1.31Counter32read-onlyThe total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Note that it is entirely normal for etherStatsFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits.
C32 reportsL2IfaceStatsJabbers1.3.6.1.4.1.738.1.5.100.3.1.1.1.32Counter32read-onlyThe total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Note that this definition of jabber is different from the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition in which any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms.
C32 reportsL2IfaceStatsCollisions1.3.6.1.4.1.738.1.5.100.3.1.1.1.33Counter32read-onlyThe best estimate of the total number of collisions on this Ethernet segment. The value returned will depend on the RMON probe's location. Sections 8.2.1.3 (10BASE-5) and 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision in the receive mode if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. Probe location plays a much smaller role when considering 10BASE-T. Section 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions. Note also that an RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coaxial segments to which the repeater is connected.
C32 reportsL2IfaceStatsPkts64Octets1.3.6.1.4.1.738.1.5.100.3.1.1.1.34Counter32read-onlyThe total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).
C32 reportsL2IfaceStatsPkts65to127Octets1.3.6.1.4.1.738.1.5.100.3.1.1.1.35Counter32read-onlyThe total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets).
C32 reportsL2IfaceStatsPkts128to255Octets1.3.6.1.4.1.738.1.5.100.3.1.1.1.36Counter32read-onlyThe total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets).
C32 reportsL2IfaceStatsPkts256to511Octets1.3.6.1.4.1.738.1.5.100.3.1.1.1.37Counter32read-onlyThe total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets).
C32 reportsL2IfaceStatsPkts512to1023Octets1.3.6.1.4.1.738.1.5.100.3.1.1.1.38Counter32read-onlyThe total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets).
C32 reportsL2IfaceStatsPkts1024to1518Octets1.3.6.1.4.1.738.1.5.100.3.1.1.1.39Counter32read-onlyThe total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets).
INT reportsL2IfaceFlow1.3.6.1.4.1.738.1.5.100.3.1.1.1.40INTEGERread-onlyThe flow control for the interface.
MOD reportsL2IfaceHWType1.3.6.1.4.1.738.1.5.100.3.1.1.1.41ModuleHwTyperead-onlyThe HW type of the interface.
I32 reportsL2IfaceActiveJackIndex1.3.6.1.4.1.738.1.5.100.3.1.1.1.42Integer32read-onlyThe current active jack index.
reportsHardware1.3.6.1.4.1.738.1.5.100.3.2
OCT reportsHardwarePSStatus1.3.6.1.4.1.738.1.5.100.3.2.1OCTET STRINGread-onlyEach OCTET holds the status of 1 power supply or if supported, a status of its corresponding power supply fan. Every octet can show one of the following states: 0 - power supply not installed; 1 - power supply is installed but does not function correctly; 2 - power supply is installed and working OK; There are devices, which can also show status of the Fan, attached to the power supply. All devices which support the Power Supply fan, will display their status in series of octet pairs. The fan status octet will be displayed right after the supply status octet.
OCT reportsHardwareFanStatus1.3.6.1.4.1.738.1.5.100.3.2.2OCTET STRINGread-onlyEach OCTET holds the status of 1 fan 0 - Fan stopped 1 - Fan failed 2 - Fan OK
INT reportsHardwareTemperature1.3.6.1.4.1.738.1.5.100.3.2.3INTEGERread-onlyThe internal temperature of the unit in degrees Celsius.
OCT reportsHardwarePSVoltage1.3.6.1.4.1.738.1.5.100.3.2.4OCTET STRINGread-onlyEach OCTET holds the voltage of a corresponding power supply. Every octet can show one of the following states: 0 - power supply not installed or voltage information is not supported; 1-C - power supply in V, hexadecimal;
INT reportsHardwareTemperatureScale1.3.6.1.4.1.738.1.5.100.3.2.5INTEGERread-writeDisplays the scale used - Celsius (Centigrade) or Fahrenheit when measuring CPU temperature. The value of this object determines the type of scale used for the values of reportsHardwareTemperature and reportsHardwareTemperatureHighLimit objects.
INT reportsHardwareTemperatureHighLimit1.3.6.1.4.1.738.1.5.100.3.2.6INTEGERread-writeDisplays the highest allowed Celsius (Centigrade) or Fahrenheit temperature at the unit CPU area. When this limit is reached an SNMP notification is sent.
INT reportsHardwareDoorStatus1.3.6.1.4.1.738.1.5.100.3.2.7INTEGERread-onlyStatus of door 0 - Door not installed 1 - Door open 2 - Door closed
reportsIfJack1.3.6.1.4.1.738.1.5.100.3.3
reportsIfJackTable1.3.6.1.4.1.738.1.5.100.3.3.2not-accessibleInformation about the external jacks attached to MAUs attached to an interface.
reportsIfJackEntry1.3.6.1.4.1.738.1.5.100.3.3.2.1not-accessibleAn entry in the table, containing information about a particular jack.
I32 reportsIfJackIndex1.3.6.1.4.1.738.1.5.100.3.3.2.1.1Integer32not-accessibleThis variable uniquely identifies the jack described by this entry from among other jacks attached to the same MAU.
MOD reportsIfJackType1.3.6.1.4.1.738.1.5.100.3.3.2.1.2ModuleHwTyperead-onlyThe jack connector type, as it appears on the outer side of the system.
test1.3.6.1.4.1.738.1.5.100.4
commands1.3.6.1.4.1.738.1.5.100.5
prvtSwitchConformance1.3.6.1.4.1.738.1.5.100.6
prvtSwitchMIBGroups1.3.6.1.4.1.738.1.5.100.6.2
prvtSwitchNotificationGroup1.3.6.1.4.1.738.1.5.100.6.2.3Private Notification Group.
acs25L42821.3.6.1.4.1.738.1.5.500
acs25L4282t51.3.6.1.4.1.738.1.5.502
vol50001.3.6.1.4.1.738.1.5.996
vol40001.3.6.1.4.1.738.1.5.998
vol02151.3.6.1.4.1.738.1.5.999
ipSwitch1.3.6.1.4.1.738.1.6
prvt_mgmt1.3.6.1.4.1.738.2

FAQ

How can I confirm which hardware module is installed in a specific slot of a BATM carrier Ethernet switch?
PRVT-SWITCH-MIB's system interface table reports stack number, slot number, and unit/module presence (sysStackNo, sysSlotNo, sysIntfUnitExist), so an operator can poll exactly which physical modules occupy which slots without opening the chassis, useful when planning a card swap or verifying a shipment.

How do I look up the exact model and serial number of a BATM switch for an asset audit?
The MIB exposes hardware inventory fields including system serial number, switch model, assembly/part numbers, and CLEI code. Polling these lets an asset-management process confirm the identity of a deployed switch remotely rather than relying on a physical label check.

RFC description

Manages BATM Advanced Communication carrier Ethernet switch global configuration, port parameters, and device capabilities.

Start monitoring BATM/Telco Systems carrier Ethernet switches 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 PRVT-SWITCH-MIB