PRVT-SWITCH-MIB

All MIBs › PRVT-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.

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 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.

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.

What Can Be Monitored

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

Imported Objects

From IF-MIB

ifAdminStatus	OBJECT-TYPE
ifIndex	OBJECT-TYPE
ifOperStatus	OBJECT-TYPE

From PRIV-VENDORDEF-MIB

privateVendorOID

MODULE-IDENTITY

From SNMPv2-CONF

NOTIFICATION-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using reportsHardwareTemperature OID:

Select a BATM/Telco Systems carrier Ethernet switch as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type reportsHardwareTemperature into the Find box to locate it in the OID tree, then select it and click OK. It reports the switch's internal hardware temperature, in degrees Celsius. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the temperature exceeds 65°C, a common early-warning level before thermal issues affect switch reliability. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ac500	1.3.6.1.4.1.738.1.5.100.1.1.1050
ac505	1.3.6.1.4.1.738.1.5.100.1.1.1050.1
ac512	1.3.6.1.4.1.738.1.5.100.1.1.1050.2
ac524	1.3.6.1.4.1.738.1.5.100.1.1.1050.3
acs25L4282	1.3.6.1.4.1.738.1.5.500
acs25L4282t5	1.3.6.1.4.1.738.1.5.502
aHUB1_A	1.3.6.1.4.1.738.1.5.100.1.1.18
alcatel_7250	1.3.6.1.4.1.738.1.5.100.1.1.16.1
alcatel_7250_ES	1.3.6.1.4.1.738.1.5.100.1.1.19.1
alcatel_7250_ESA	1.3.6.1.4.1.738.1.5.100.1.1.19.2
as9205	1.3.6.1.4.1.738.1.5.100.1.1.7.1
as9205_F	1.3.6.1.4.1.738.1.5.100.1.1.9.1
as9215	1.3.6.1.4.1.738.1.5.100.1.1.27.1
as9220	1.3.6.1.4.1.738.1.5.100.1.1.19.10
bI_Ethernet	1.3.6.1.4.1.738.1.5.100.1.1.18.1
bridge	1.3.6.1.4.1.738.1.2
bsw	1.3.6.1.4.1.738.1.5.1
classic	1.3.6.1.4.1.738.1.5.100.1.1.14.2
commands	1.3.6.1.4.1.738.1.5.100.5
compact	1.3.6.1.4.1.738.1.5.100.1.1.14.1
config	1.3.6.1.4.1.738.1.5.100.2
configL2	1.3.6.1.4.1.738.1.5.100.2.2
INT configL2IfaceAdminCrossOver	1.3.6.1.4.1.738.1.5.100.2.2.2.1.23	INTEGER	read-write	The 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 configL2IfaceBackpressure	1.3.6.1.4.1.738.1.5.100.2.2.2.1.9	INTEGER	read-write	The desired back-pressure mode for the interface. If the selected control is not available on the interface, a value of illegal (99) is returned.
I32 configL2IfaceBroadcastBurstSize	1.3.6.1.4.1.738.1.5.100.2.2.2.1.19	Integer32	read-write	Burst size broadcast traffic. Must be a number between 12Kbps and 1Mbps, specified in Kbps.
I32 configL2IfaceBroadcastRateLimit	1.3.6.1.4.1.738.1.5.100.2.2.2.1.16	Integer32	read-write	Rate limit broadcast traffic. Must be a number between 64Kbps and 1Gbps, specified in Kbps.
I32 configL2IfaceDefaultVID	1.3.6.1.4.1.738.1.5.100.2.2.2.1.11	Integer32	read-write	This object sets the default VLAN ID according to 802.1Q.
INT configL2IfaceDuplexModeSet	1.3.6.1.4.1.738.1.5.100.2.2.2.1.14	INTEGER	read-write	The 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 configL2IfaceDuplexSpeedSet	1.3.6.1.4.1.738.1.5.100.2.2.2.1.7	INTEGER	read-write	The 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 configL2IfaceEnable	1.3.6.1.4.1.738.1.5.100.2.2.2.1.5	INTEGER	read-write	Enables (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'.
configL2IfaceEntry	1.3.6.1.4.1.738.1.5.100.2.2.2.1		not-accessible	An index of interfaces.
INT configL2IfaceFlow	1.3.6.1.4.1.738.1.5.100.2.2.2.1.8	INTEGER	read-write	The 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.
I32 configL2IfaceMtu	1.3.6.1.4.1.738.1.5.100.2.2.2.1.22	Integer32	read-write	The Maximum Transmission Unit (in octets) of the interface.
I32 configL2IfaceMulticastBurstSize	1.3.6.1.4.1.738.1.5.100.2.2.2.1.20	Integer32	read-write	Burst size multicast traffic. Must be a number between 12Kbps and 1Mbps, specified in Kbps.
I32 configL2IfaceMulticastRateLimit	1.3.6.1.4.1.738.1.5.100.2.2.2.1.17	Integer32	read-write	Rate limit multicast traffic. Must be a number between 64Kbps and 1Gbps, specified in Kbps.
STR configL2IfaceName	1.3.6.1.4.1.738.1.5.100.2.2.2.1.4	DisplayString	read-write	The textual name of this interface, e.g., 'John'.
I32 configL2IfacePort	1.3.6.1.4.1.738.1.5.100.2.2.2.1.3	Integer32	read-only	An index that uniquely identifies a port within the slot in the Interface Table.
INT configL2IfaceRemoteFaultDetect	1.3.6.1.4.1.738.1.5.100.2.2.2.1.24	INTEGER	read-write	Controls 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.
INT configL2IfaceResetCounters	1.3.6.1.4.1.738.1.5.100.2.2.2.1.10	INTEGER	read-write	This object enables resetting the statistics counters selected for this port.
I32 configL2IfaceSlot	1.3.6.1.4.1.738.1.5.100.2.2.2.1.2	Integer32	read-only	An index that uniquely identifies a slot within the unit in the Interface Table.
I32 configL2IfaceSnifferIfIndex	1.3.6.1.4.1.738.1.5.100.2.2.2.1.12	Integer32	read-write	This object connects this port to a sniffer port indexed by the specified ifIndex. Setting this value to 0 disconnects this port from the sniffer.
INT configL2IfaceSpeedSet	1.3.6.1.4.1.738.1.5.100.2.2.2.1.15	INTEGER	read-write	The 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.
INT configL2IfaceSTPEnable	1.3.6.1.4.1.738.1.5.100.2.2.2.1.6	INTEGER	read-write	Enables (1) and disables (2) Spanning Tree operation for this interface.
configL2IfaceTable	1.3.6.1.4.1.738.1.5.100.2.2.2		not-accessible	A list of Interfaces and their properties
I32 configL2IfaceUnit	1.3.6.1.4.1.738.1.5.100.2.2.2.1.1	Integer32	read-only	An index that uniquely identifies a unit in the Interface Table.
I32 configL2IfaceUnknownBurstSize	1.3.6.1.4.1.738.1.5.100.2.2.2.1.21	Integer32	read-write	Burst size unknown traffic. Must be a number between 12Kbps and 1Mbps, specified in Kbps. For detail information see documentation.
I32 configL2IfaceUnknownRateLimit	1.3.6.1.4.1.738.1.5.100.2.2.2.1.18	Integer32	read-write	Rate limit unknown traffic. Must be a number between 64Kbps and 1Gbps, specified in Kbps. For detail information see documentation.
INT configL2SpanOnOff	1.3.6.1.4.1.738.1.5.100.2.2.1	INTEGER	read-write	Enables/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.
T/F configL2TopologyChangeDetection	1.3.6.1.4.1.738.1.5.100.2.2.2.1.13	TruthValue	read-write	This object controls the STP topology change detection for this interface.
NTF cpuTemperatureExceeded	1.3.6.1.4.1.738.1.5.100.0.1			The cpuTemperatuteExceeded trap indicates that the sending agent senses that the internal temperature has passed the program threshold.
dm9225	1.3.6.1.4.1.738.1.5.100.1.1.17.1.1
dm9225_E	1.3.6.1.4.1.738.1.5.100.1.1.17.2.1
dm9234	1.3.6.1.4.1.738.1.5.100.1.1.17.10.1
NTF doorStatusChange	1.3.6.1.4.1.738.1.5.100.0.8			The doorStatusChange trap indicates that the sending agent senses a change in the status of the door.
edgeGate201	1.3.6.1.4.1.738.1.5.100.1.1.1031
edgeGate231	1.3.6.1.4.1.738.1.5.100.1.1.1010
edgeGate232	1.3.6.1.4.1.738.1.5.100.1.1.1041
edgeGate281	1.3.6.1.4.1.738.1.5.100.1.1.1000
edgeGate281SYS	1.3.6.1.4.1.738.1.5.100.1.1.1001
edgeGate282	1.3.6.1.4.1.738.1.5.100.1.1.1020
edgeGate282S	1.3.6.1.4.1.738.1.5.100.1.1.1021
edgeGate482S	1.3.6.1.4.1.738.1.5.100.1.1.1022
edgeGate483D	1.3.6.1.4.1.738.1.5.100.1.1.1024
edgeGate483S	1.3.6.1.4.1.738.1.5.100.1.1.1023
edgeLinkT4	1.3.6.1.4.1.738.1.5.15
edgeLinkT5	1.3.6.1.4.1.738.1.5.17
NTF fanStatusChange	1.3.6.1.4.1.738.1.5.100.0.3			The fanStatusChange trap indicates that the sending agent senses a change in the status of one of the fans.
fI_Ethernet	1.3.6.1.4.1.738.1.5.100.1.1.18.2
ipSwitch	1.3.6.1.4.1.738.1.6
NTF portRedundantLinkChange	1.3.6.1.4.1.738.1.5.100.0.5			The 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 portSecurityViolation	1.3.6.1.4.1.738.1.5.100.0.4			The 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 powerSupplyStatusChange	1.3.6.1.4.1.738.1.5.100.0.2			The powerSupplyStatusChange trap indicates that the sending agent senses a change in the status of one of the power supplies.
prvt_mgmt	1.3.6.1.4.1.738.2
prvt_products	1.3.6.1.4.1.738.1
NTF prvtLogNotifyFull	1.3.6.1.4.1.738.1.5.100.0.7			Log buffer is almost full.
prvtSwitchConformance	1.3.6.1.4.1.738.1.5.100.6
prvtSwitchMib	1.3.6.1.4.1.738.1.5.100			The switch MIB module for managing switch parameters
prvtSwitchMIBGroups	1.3.6.1.4.1.738.1.5.100.6.2
prvtSwitchNotificationGroup	1.3.6.1.4.1.738.1.5.100.6.2.3			Private Notification Group.
prvtSwitchNotifications	1.3.6.1.4.1.738.1.5.100.0
reports	1.3.6.1.4.1.738.1.5.100.3
reportsHardware	1.3.6.1.4.1.738.1.5.100.3.2
INT reportsHardwareDoorStatus	1.3.6.1.4.1.738.1.5.100.3.2.7	INTEGER	read-only	Status of door 0 - Door not installed 1 - Door open 2 - Door closed
OCT reportsHardwareFanStatus	1.3.6.1.4.1.738.1.5.100.3.2.2	OCTET STRING	read-only	Each OCTET holds the status of 1 fan 0 - Fan stopped 1 - Fan failed 2 - Fan OK
OCT reportsHardwarePSStatus	1.3.6.1.4.1.738.1.5.100.3.2.1	OCTET STRING	read-only	Each 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 reportsHardwarePSVoltage	1.3.6.1.4.1.738.1.5.100.3.2.4	OCTET STRING	read-only	Each 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 reportsHardwareTemperatureEx	1.3.6.1.4.1.738.1.5.100.3.2.3	INTEGER	read-only	The internal temperature of the unit in degrees Celsius.
INT reportsHardwareTemperatureHighLimit	1.3.6.1.4.1.738.1.5.100.3.2.6	INTEGER	read-write	Displays the highest allowed Celsius (Centigrade) or Fahrenheit temperature at the unit CPU area. When this limit is reached an SNMP notification is sent.
INT reportsHardwareTemperatureScale	1.3.6.1.4.1.738.1.5.100.3.2.5	INTEGER	read-write	Displays 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.
reportsIfJack	1.3.6.1.4.1.738.1.5.100.3.3
reportsIfJackEntry	1.3.6.1.4.1.738.1.5.100.3.3.2.1		not-accessible	An entry in the table, containing information about a particular jack.
I32 reportsIfJackIndex	1.3.6.1.4.1.738.1.5.100.3.3.2.1.1	Integer32	not-accessible	This variable uniquely identifies the jack described by this entry from among other jacks attached to the same MAU.
reportsIfJackTable	1.3.6.1.4.1.738.1.5.100.3.3.2		not-accessible	Information about the external jacks attached to MAUs attached to an interface.
MOD reportsIfJackType	1.3.6.1.4.1.738.1.5.100.3.3.2.1.2	ModuleHwType	read-only	The jack connector type, as it appears on the outer side of the system.
reportsL2	1.3.6.1.4.1.738.1.5.100.3.1
I32 reportsL2IfaceActiveJackIndex	1.3.6.1.4.1.738.1.5.100.3.1.1.1.42	Integer32	read-only	The current active jack index.
I32 reportsL2IfaceBridgeIndex	1.3.6.1.4.1.738.1.5.100.3.1.1.1.4	Integer32	read-only	This is the bridge index of this port.
INT reportsL2IfaceDuplexSpeedGet	1.3.6.1.4.1.738.1.5.100.3.1.1.1.7	INTEGER	read-only	The 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.
reportsL2IfaceEntry	1.3.6.1.4.1.738.1.5.100.3.1.1.1		not-accessible	An index of interfaces.
INT reportsL2IfaceFlow	1.3.6.1.4.1.738.1.5.100.3.1.1.1.40	INTEGER	read-only	The flow control for the interface.
MOD reportsL2IfaceHWType	1.3.6.1.4.1.738.1.5.100.3.1.1.1.41	ModuleHwType	read-only	The HW type of the interface.
C32 reportsL2IfaceIfInDiscards	1.3.6.1.4.1.738.1.5.100.3.1.1.1.15	Counter32	read-only	The 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 reportsL2IfaceIfInErrors	1.3.6.1.4.1.738.1.5.100.3.1.1.1.16	Counter32	read-only	The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
C32 reportsL2IfaceIfInNUcastPkts	1.3.6.1.4.1.738.1.5.100.3.1.1.1.14	Counter32	read-only	The number of non-unicast (i.e., subnetwork- broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.
C32 reportsL2IfaceIfInOctets	1.3.6.1.4.1.738.1.5.100.3.1.1.1.12	Counter32	read-only	The total number of octets received on the interface, including framing characters.
C32 reportsL2IfaceIfInUcastPkts	1.3.6.1.4.1.738.1.5.100.3.1.1.1.13	Counter32	read-only	The number of subnetwork-unicast packets delivered to a higher-layer protocol.
C32 reportsL2IfaceIfInUnknownProtos	1.3.6.1.4.1.738.1.5.100.3.1.1.1.17	Counter32	read-only	The number of packets received via the interface that were discarded because of an unknown or unsupported protocol.
C32 reportsL2IfaceIfOutDiscards	1.3.6.1.4.1.738.1.5.100.3.1.1.1.21	Counter32	read-only	The 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 reportsL2IfaceIfOutErrors	1.3.6.1.4.1.738.1.5.100.3.1.1.1.22	Counter32	read-only	The number of outbound packets that could not be transmitted because of errors.
C32 reportsL2IfaceIfOutNUcastPkts	1.3.6.1.4.1.738.1.5.100.3.1.1.1.20	Counter32	read-only	The 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 reportsL2IfaceIfOutOctets	1.3.6.1.4.1.738.1.5.100.3.1.1.1.18	Counter32	read-only	The total number of octets transmitted out of the interface, including framing characters.
C32 reportsL2IfaceIfOutUcastPkts	1.3.6.1.4.1.738.1.5.100.3.1.1.1.19	Counter32	read-only	The 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.
INT reportsL2IfaceLink	1.3.6.1.4.1.738.1.5.100.3.1.1.1.6	INTEGER	read-only	The state of Link Detect on the interface.
I32 reportsL2IfacePort	1.3.6.1.4.1.738.1.5.100.3.1.1.1.3	Integer32	read-only	An index that uniquely identifies a port within the slot in the Interface Table.
C32 reportsL2IfaceRXOctetsNoErr	1.3.6.1.4.1.738.1.5.100.3.1.1.1.10	Counter32	read-only	The number of octets received on the interface. This number does not include octets with errors.
C32 reportsL2IfaceRXPacketsNoErr	1.3.6.1.4.1.738.1.5.100.3.1.1.1.11	Counter32	read-only	The number of packets received on the interface. This number does not include packets with errors.
I32 reportsL2IfaceSlot	1.3.6.1.4.1.738.1.5.100.3.1.1.1.2	Integer32	read-only	An index that uniquely identifies a slot within the unit in the Interface Table.
C32 reportsL2IfaceStatsBroadcastPkts	1.3.6.1.4.1.738.1.5.100.3.1.1.1.26	Counter32	read-only	The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.
C32 reportsL2IfaceStatsCollisions	1.3.6.1.4.1.738.1.5.100.3.1.1.1.33	Counter32	read-only	The 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 reportsL2IfaceStatsCRCAlignErrors	1.3.6.1.4.1.738.1.5.100.3.1.1.1.28	Counter32	read-only	The 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 reportsL2IfaceStatsDropEvents	1.3.6.1.4.1.738.1.5.100.3.1.1.1.23	Counter32	read-only	The 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 reportsL2IfaceStatsFragments	1.3.6.1.4.1.738.1.5.100.3.1.1.1.31	Counter32	read-only	The 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 reportsL2IfaceStatsJabbers	1.3.6.1.4.1.738.1.5.100.3.1.1.1.32	Counter32	read-only	The 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 reportsL2IfaceStatsMulticastPkts	1.3.6.1.4.1.738.1.5.100.3.1.1.1.27	Counter32	read-only	The 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 reportsL2IfaceStatsOctets	1.3.6.1.4.1.738.1.5.100.3.1.1.1.24	Counter32	read-only	The 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 reportsL2IfaceStatsOversizePkts	1.3.6.1.4.1.738.1.5.100.3.1.1.1.30	Counter32	read-only	The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.
C32 reportsL2IfaceStatsPkts	1.3.6.1.4.1.738.1.5.100.3.1.1.1.25	Counter32	read-only	The total number of packets (including bad packets, broadcast packets, and multicast packets) received.
C32 reportsL2IfaceStatsPkts1024to1518Octets	1.3.6.1.4.1.738.1.5.100.3.1.1.1.39	Counter32	read-only	The 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).
C32 reportsL2IfaceStatsPkts128to255Octets	1.3.6.1.4.1.738.1.5.100.3.1.1.1.36	Counter32	read-only	The 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 reportsL2IfaceStatsPkts256to511Octets	1.3.6.1.4.1.738.1.5.100.3.1.1.1.37	Counter32	read-only	The 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 reportsL2IfaceStatsPkts512to1023Octets	1.3.6.1.4.1.738.1.5.100.3.1.1.1.38	Counter32	read-only	The 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 reportsL2IfaceStatsPkts64Octets	1.3.6.1.4.1.738.1.5.100.3.1.1.1.34	Counter32	read-only	The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).
C32 reportsL2IfaceStatsPkts65to127Octets	1.3.6.1.4.1.738.1.5.100.3.1.1.1.35	Counter32	read-only	The 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 reportsL2IfaceStatsUndersizePkts	1.3.6.1.4.1.738.1.5.100.3.1.1.1.29	Counter32	read-only	The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.
reportsL2IfaceTable	1.3.6.1.4.1.738.1.5.100.3.1.1		not-accessible	A list of Interfaces and their properties
C32 reportsL2IfaceTXOctetsNoErr	1.3.6.1.4.1.738.1.5.100.3.1.1.1.8	Counter32	read-only	The number of octets transmitted from the interface. This number does not include octets with errors.
C32 reportsL2IfaceTXPacketsNoErr	1.3.6.1.4.1.738.1.5.100.3.1.1.1.9	Counter32	read-only	The number of packets transmitted from the interface. This number does not include packets with errors.
INT reportsL2IfaceType	1.3.6.1.4.1.738.1.5.100.3.1.1.1.5	INTEGER	read-only	The type of interface, repeated here from the definitions in RFC1213 as a matter of convenience.
I32 reportsL2IfaceUnit	1.3.6.1.4.1.738.1.5.100.3.1.1.1.1	Integer32	read-only	An index that uniquely identifies a unit in the Interface Table.
router	1.3.6.1.4.1.738.1.4
rptr	1.3.6.1.4.1.738.1.1
switch	1.3.6.1.4.1.738.1.5
sys	1.3.6.1.4.1.738.1.5.100.1
STR sysAssemblyNumber	1.3.6.1.4.1.738.1.5.100.1.3.3	DisplayString	read-only	Specifies the equipment assembly number
STR sysCLEI	1.3.6.1.4.1.738.1.5.100.1.3.5	DisplayString	read-only	Specifies the common language equipment identification
STR sysHwRevision	1.3.6.1.4.1.738.1.5.100.1.3.6	DisplayString	read-only	Specifies the HW revision
sysIntf	1.3.6.1.4.1.738.1.5.100.1.2
sysIntfEntry	1.3.6.1.4.1.738.1.5.100.1.2.1.1		not-accessible	sysIntfEntry
MOD sysIntfModule	1.3.6.1.4.1.738.1.5.100.1.2.1.1.4	ModuleHwType	read-only	This indicates interface module type
NTF sysIntfModuleChange	1.3.6.1.4.1.738.1.5.100.0.6			The System Interface Module change notification indicates that the physical status of a module in the unit has changed.
sysIntfTable	1.3.6.1.4.1.738.1.5.100.1.2.1		not-accessible	This table contains the interfaces module type.
INT sysIntfUnitExist	1.3.6.1.4.1.738.1.5.100.1.2.1.1.3	INTEGER	read-only	This indicates interface module type
sysManufacturing	1.3.6.1.4.1.738.1.5.100.1.3
STR sysManufacturingDate	1.3.6.1.4.1.738.1.5.100.1.3.7	DisplayString	read-only	Specifies the manufacturing date
STR sysPartNumber	1.3.6.1.4.1.738.1.5.100.1.3.4	DisplayString	read-only	Specifies the equipment part number
sysProductsOids	1.3.6.1.4.1.738.1.5.100.1.1
STR sysSerialNumber	1.3.6.1.4.1.738.1.5.100.1.3.1	DisplayString	read-only	This is the device's serial number, which is entered during the manufacturing process.
I32 sysSlotNo	1.3.6.1.4.1.738.1.5.100.1.2.1.1.2	Integer32	read-only	This indicates a single instance of a slot
UNI sysStackNo	1.3.6.1.4.1.738.1.5.100.1.2.1.1.1	UnitIndex	read-only	This object identifies the switch
sysSwitchingHW	1.3.6.1.4.1.738.1.5.100.1.4
STR sysSwitchModel	1.3.6.1.4.1.738.1.5.100.1.3.2	DisplayString	read-only	Specifies the equipment model
SER sysSwitchSeries	1.3.6.1.4.1.738.1.5.100.1.4.1	Series	read-only	This object displays the switch series.
t4Router	1.3.6.1.4.1.738.1.5.100.1.1.1
t5c	1.3.6.1.4.1.738.1.5.100.1.1.100
t5c_24FRouter	1.3.6.1.4.1.738.1.5.100.1.1.9
t5c_24GRouter	1.3.6.1.4.1.738.1.5.100.1.1.10
t5c_24GTRouter	1.3.6.1.4.1.738.1.5.100.1.1.11
t5c_24MRouter	1.3.6.1.4.1.738.1.5.100.1.1.8
t5c_24TRouter	1.3.6.1.4.1.738.1.5.100.1.1.7
t5c_48TRouter	1.3.6.1.4.1.738.1.5.100.1.1.5
t5c_XG	1.3.6.1.4.1.738.1.5.100.1.1.27
t5cgt	1.3.6.1.4.1.738.1.5.100.1.1.222
t5g	1.3.6.1.4.1.738.1.5.100.1.1.333
t5ProRouter	1.3.6.1.4.1.738.1.5.100.1.1.3
t5RNRouter	1.3.6.1.4.1.738.1.5.100.1.1.6
t5Router	1.3.6.1.4.1.738.1.5.100.1.1.2
t6pro_cpm	1.3.6.1.4.1.738.1.5.100.1.1.14
t6pro_lc_20G	1.3.6.1.4.1.738.1.5.100.1.1.13
t6Router	1.3.6.1.4.1.738.1.5.100.1.1.4
test	1.3.6.1.4.1.738.1.5.100.4
titan	1.3.6.1.4.1.738.1.5.5
titanPro	1.3.6.1.4.1.738.1.5.20
titant5	1.3.6.1.4.1.738.1.5.7
tMarc	1.3.6.1.4.1.738.1.5.100.1.1.17
tMarc_250	1.3.6.1.4.1.738.1.5.100.1.1.17.1
tMarc_254	1.3.6.1.4.1.738.1.5.100.1.1.17.2
tMarc_254h	1.3.6.1.4.1.738.1.5.100.1.1.17.3
tMarc_280	1.3.6.1.4.1.738.1.5.100.1.1.17.20
tMarc_340	1.3.6.1.4.1.738.1.5.100.1.1.17.10
tMarc_340_E	1.3.6.1.4.1.738.1.5.100.1.1.20.1
tMarc_340_EW	1.3.6.1.4.1.738.1.5.100.1.1.21.1
tMarc_340_F	1.3.6.1.4.1.738.1.5.100.1.1.24.1
tMarc_340WD	1.3.6.1.4.1.738.1.5.100.1.1.23.1
tMarc_340WD_B	1.3.6.1.4.1.738.1.5.100.1.1.22.1
tMarc_380	1.3.6.1.4.1.738.1.5.100.1.1.17.11
tMarc_380_E	1.3.6.1.4.1.738.1.5.100.1.1.20.2
tMarc_380_EW	1.3.6.1.4.1.738.1.5.100.1.1.21.2
tMarc_E	1.3.6.1.4.1.738.1.5.100.1.1.20
tMarc_EW	1.3.6.1.4.1.738.1.5.100.1.1.21
tMarc_F	1.3.6.1.4.1.738.1.5.100.1.1.24
tMarc_WD	1.3.6.1.4.1.738.1.5.100.1.1.23
tMarc_WDB	1.3.6.1.4.1.738.1.5.100.1.1.22
tMetro	1.3.6.1.4.1.738.1.5.100.1.1.16
tMetro_200S	1.3.6.1.4.1.738.1.5.100.1.1.19.11
tMetro_ES	1.3.6.1.4.1.738.1.5.100.1.1.19
tMetro_ESA	1.3.6.1.4.1.738.1.5.100.1.1.19.3
tpf	1.3.6.1.4.1.738.1.5.3
tps	1.3.6.1.4.1.738.1.5.2
trclam	1.3.6.1.4.1.738.1.3
v24s	1.3.6.1.4.1.738.1.5.100.1.1.444
vol0215	1.3.6.1.4.1.738.1.5.999
vol4000	1.3.6.1.4.1.738.1.5.998
vol5000	1.3.6.1.4.1.738.1.5.996

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