Home/Catalog/BATM-SWITCH-MIB

BATM-SWITCH-MIB

AI MIB Summary

BATM-SWITCH-MIB provides SNMP management access to internal Telco Systems BATM switch parameters, enabling monitoring of ATM virtual circuit states, port statistics, and switching fabric performance metrics.

The switch MIB module for managing BATM/Telco Systems internal switch parameters
Main OID:
batmSwitchMib.1.3.6.1.4.1.2697.1.5.100
192
Objects
Active
Status
6
Dependencies

Imported Objects

Objects

192 total
Object Name
batm-products
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1
SNMPv2-TC
NOTIFICATION-TYPE
.1.3.6.1.4.1.2697.1
rptr
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.1
bridge
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.2
trclam
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.3
router
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.4
switch
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5
bsw
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.1
tps
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.2
tpf
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.3
titan
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.5
titant5
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.7
edgeLinkT4
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.15
edgeLinkT5
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.17
titanPro
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.20
batmSwitchMibThe switch MIB module for managing BATM/Telco Systems internal switch parameters
MODULE-IDENTITY
.1.3.6.1.4.1.2697.1.5.100
batmSwitchNotifications
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.0
cpuTemperatureExceededThe cpuTemperatuteExceeded trap indicates that the sending agent senses that the internal temperature has passed the program threshold.
NOTIFICATION-TYPE
.1.3.6.1.4.1.2697.1.5.100.0.1
powerSupplyStatusChangeThe powerSupplyStatusChange trap indicates that the sending agent senses a change in the status of one of the power supplies.
NOTIFICATION-TYPE
.1.3.6.1.4.1.2697.1.5.100.0.2
fanStatusChangeThe fanStatusChange trap indicates that the sending agent senses a change in the status of one of the fans.
NOTIFICATION-TYPE
.1.3.6.1.4.1.2697.1.5.100.0.3
portSecurityViolationThe port security violation notification indicates that a port security violation has been detected, e.g more MAC adresses have been learned on that p ort than the number allowed.
NOTIFICATION-TYPE
.1.3.6.1.4.1.2697.1.5.100.0.4
portRedundantLinkChangeThe 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.2697.1.5.100.0.5
sysIntfModuleChangeThe System Interface Module change notification indicates that the physical status of a module in the unit has changed.
NOTIFICATION-TYPE
.1.3.6.1.4.1.2697.1.5.100.0.6
batmLogNotifyFullLog buffer is almost full.
NOTIFICATION-TYPE
.1.3.6.1.4.1.2697.1.5.100.0.7
sys
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1
sysProductsOids
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1
t4Router
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1
t5Router
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.2
t5ProRouter
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.3
t6Router
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.4
t5c-48TRouter
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.5
t5RNRouter
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.6
t5c-24TRouter
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.7
as9205
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.7.1
t5c-24MRouter
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.8
t5c-24FRouter
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.9
as9205-F
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.9.1
t5c-24GRouter
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.10
t5c-24GTRouter
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.11
t6pro-lc-20G
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.13
t6pro-cpm
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.14
compact
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.14.1
classic
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.14.2
tMetro
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.16
alcatel-7250
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.16.1
tMarc
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.17
tMarc-250
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.17.1
dm9225
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.17.1.1
tMarc-254
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.17.2
dm9225-E
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.17.2.1
tMarc-340
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.17.10
dm9234
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.17.10.1
tMarc-380
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.17.11
aHUB1-A
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.18
bI-Ethernet
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.18.1
fI-Ethernet
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.18.2
tMetro-ES
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.19
alcatel-7250-ES
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.19.1
alcatel-7250-ESA
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.19.2
as9220
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.19.10
t5c-XG
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.27
as9215
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.27.1
t5c
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.100
t5cgt
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.222
t5g
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.333
v24s
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.444
edgeGate281
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1000
edgeGate281SYS
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1001
edgeGate231
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1010
edgeGate282
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1020
edgeGate282S
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1021
edgeGate482S
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1022
edgeGate483S
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1023
edgeGate201
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1031
edgeGate232
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1041
ac500
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1050
ac505
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1050.1
ac512
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1050.2
ac524
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.1.1050.3
sysIntf
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.2
sysIntfTableThis table contains the interfaces module type.
SEQUENCE OF SysIntfEntry
.1.3.6.1.4.1.2697.1.5.100.1.2.1
sysIntfEntry
SysIntfEntry
.1.3.6.1.4.1.2697.1.5.100.1.2.1.1
sysStackNoThis object identifies the switchro
UnitIndex
.1.3.6.1.4.1.2697.1.5.100.1.2.1.1.1
sysSlotNoThis indicates a single instance of a slotro
INTEGER
.1.3.6.1.4.1.2697.1.5.100.1.2.1.1.2
sysIntfUnitExistThis indicates interface module typero
Enumeration
.1.3.6.1.4.1.2697.1.5.100.1.2.1.1.3
sysIntfModuleThis indicates interface module typero
ModuleHwType
.1.3.6.1.4.1.2697.1.5.100.1.2.1.1.4
sysManufacturing
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.3
sysSerialNumberThis is the device's serial number, which is entered during the manufacturing process. This object is supported starting from BiNOS version 5.0.0.8.2 and boot version 3.7.1. Boot versions prior to 3.7.1 return string 'not supported'.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.2697.1.5.100.1.3.1
sysSwitchModelSpecifies the equipment modelro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.2697.1.5.100.1.3.2
sysAssemblyNumberSpecifies the equipment assembly numberro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.2697.1.5.100.1.3.3
sysPartNumberSpecifies the equipment part numberro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.2697.1.5.100.1.3.4
sysCLEISpecifies the common language equipment identificationro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.2697.1.5.100.1.3.5
sysHwRevisionSpecifies the HW revisionro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.2697.1.5.100.1.3.6
sysManufacturingDateSpecifies the manufacturing datero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.2697.1.5.100.1.3.7
sysSwitchingHW
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.1.4
sysSwitchSeriesThis object displays the switch series.ro
Series
.1.3.6.1.4.1.2697.1.5.100.1.4.1
config
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.2
configL2
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.2.2
configL2SpanOnOffEnables/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.rw
Enumeration
.1.3.6.1.4.1.2697.1.5.100.2.2.1
configL2IfaceTableA list of Interfaces and their properties
SEQUENCE OF ConfigL2IfaceEntry
.1.3.6.1.4.1.2697.1.5.100.2.2.2
configL2IfaceEntryAn index of interfaces.
ConfigL2IfaceEntry
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1
configL2IfaceUnitAn index that uniquely identifies a unit in the Interface Table.ro
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.1
configL2IfaceSlotAn index that uniquely identifies a slot within the unit in the Interface Table.ro
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.2
configL2IfacePortAn index that uniquely identifies a port within the slot in the Interface Table.ro
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.3
configL2IfaceNameThe textual name of this interface, e.g., 'John'.rw
DisplayString
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.4
configL2IfaceEnableEnables (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'.rw
Enumeration
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.5
configL2IfaceSTPEnableEnables (1) and disables (2) Spanning Tree operation for this interface.rw
Enumeration
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.6
configL2IfaceDuplexSpeedSetThe 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.rw
Enumeration
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.7
configL2IfaceFlowThe 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.rw
Enumeration
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.8
configL2IfaceBackpressureThe desired back-pressure mode for the interface. If the selected control is not available on the interface, a value of illegal (99) is returned.rw
Enumeration
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.9
configL2IfaceResetCountersThis object enables resetting the statistics counters selected for this port.rw
Enumeration
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.10
configL2IfaceDefaultVIDThis object sets the default VLAN ID according to 802.1Q.rw
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.11
configL2IfaceSnifferIfIndexThis object connects this port to a sniffer port indexed by the specified ifIndex. Setting this value to 0 disconnects this port from the sniffer.rw
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.12
configL2TopologyChangeDetectionThis object controls the STP topology change detection for this interface.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.13
configL2IfaceDuplexModeSetThe 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)).rw
Enumeration
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.14
configL2IfaceSpeedSetThe 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.rw
Enumeration
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.15
configL2IfaceBroadcastRateLimitRate limit broadcast traffic. Must be a number between 64Kbps and 1Gbps, specified in Kbps.rw
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.16
configL2IfaceMulticastRateLimitRate limit multicast traffic. Must be a number between 64Kbps and 1Gbps, specified in Kbps.rw
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.17
configL2IfaceUnknownRateLimitRate limit unknown traffic. Must be a number between 64Kbps and 1Gbps, specified in Kbps. For detail information see documentation.rw
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.18
configL2IfaceBroadcastBurstSizeBurst size broadcast traffic. Must be a number between 12Kbps and 1Mbps, specified in Kbps.rw
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.19
configL2IfaceMulticastBurstSizeBurst size multicast traffic. Must be a number between 12Kbps and 1Mbps, specified in Kbps.rw
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.20
configL2IfaceUnknownBurstSizeBurst size unknown traffic. Must be a number between 12Kbps and 1Mbps, specified in Kbps. For detail information see documentation.rw
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.21
configL2IfaceMtuThe Maximum Transmission Unit (in octets) of the interface.rw
INTEGER
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.22
configL2IfaceAdminCrossOverThe 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.rw
Enumeration
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.23
configL2IfaceRemoteFaultDetectControls 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.rw
Enumeration
.1.3.6.1.4.1.2697.1.5.100.2.2.2.1.24
reports
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.3
reportsL2
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.3.1
reportsL2IfaceTableA list of Interfaces and their properties
SEQUENCE OF ReportsL2IfaceEntry
.1.3.6.1.4.1.2697.1.5.100.3.1.1
reportsL2IfaceEntryAn index of interfaces.
ReportsL2IfaceEntry
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1
reportsL2IfaceUnitAn index that uniquely identifies a unit in the Interface Table.ro
INTEGER
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.1
reportsL2IfaceSlotAn index that uniquely identifies a slot within the unit in the Interface Table.ro
INTEGER
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.2
reportsL2IfacePortAn index that uniquely identifies a port within the slot in the Interface Table.ro
INTEGER
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.3
reportsL2IfaceBridgeIndexThis is the bridge index of this port.ro
INTEGER
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.4
reportsL2IfaceTypeThe type of interface, repeated here from the definitions in RFC1213 as a matter of convenience.ro
Enumeration
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.5
reportsL2IfaceDuplexSpeedGetThe 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.ro
Enumeration
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.7
reportsL2IfaceTXOctetsNoErrThe number of octets transmitted from the interface. This number does not include octets with errors.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.8
reportsL2IfaceTXPacketsNoErrThe number of packets transmitted from the interface. This number does not include packets with errors.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.9
reportsL2IfaceRXOctetsNoErrThe number of octets received on the interface. This number does not include octets with errors.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.10
reportsL2IfaceRXPacketsNoErrThe number of packets received on the interface. This number does not include packets with errors.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.11
reportsL2IfaceIfInOctetsThe total number of octets received on the interface, including framing characters.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.12
reportsL2IfaceIfInUcastPktsThe number of subnetwork-unicast packets delivered to a higher-layer protocol.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.13
reportsL2IfaceIfInNUcastPktsThe number of non-unicast (i.e., subnetwork- broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.14
reportsL2IfaceIfInDiscardsThe 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.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.15
reportsL2IfaceIfInErrorsThe number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.16
reportsL2IfaceIfInUnknownProtosThe number of packets received via the interface that were discarded because of an unknown or unsupported protocol.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.17
reportsL2IfaceIfOutOctetsThe total number of octets transmitted out of the interface, including framing characters.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.18
reportsL2IfaceIfOutUcastPktsThe 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.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.19
reportsL2IfaceIfOutNUcastPktsThe 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.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.20
reportsL2IfaceIfOutDiscardsThe 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.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.21
reportsL2IfaceIfOutErrorsThe number of outbound packets that could not be transmitted because of errors.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.22
reportsL2IfaceStatsDropEventsThe 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.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.23
reportsL2IfaceStatsOctetsThe 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.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.24
reportsL2IfaceStatsPktsThe total number of packets (including bad packets, broadcast packets, and multicast packets) received.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.25
reportsL2IfaceStatsBroadcastPktsThe total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.26
reportsL2IfaceStatsMulticastPktsThe 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.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.27
reportsL2IfaceStatsCRCAlignErrorsThe 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).ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.28
reportsL2IfaceStatsUndersizePktsThe total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.29
reportsL2IfaceStatsOversizePktsThe total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.30
reportsL2IfaceStatsFragmentsThe 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.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.31
reportsL2IfaceStatsJabbersThe 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.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.32
reportsL2IfaceStatsCollisionsThe 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.ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.33
reportsL2IfaceStatsPkts64OctetsThe total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.34
reportsL2IfaceStatsPkts65to127OctetsThe 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).ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.35
reportsL2IfaceStatsPkts128to255OctetsThe 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).ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.36
reportsL2IfaceStatsPkts256to511OctetsThe 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).ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.37
reportsL2IfaceStatsPkts512to1023OctetsThe 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).ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.38
reportsL2IfaceStatsPkts1024to1518OctetsThe 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).ro
Counter32
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.39
reportsL2IfaceFlowThe flow control for the interface.ro
Enumeration
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.40
reportsL2IfaceHWTypeThe HW type of the interface.ro
ModuleHwType
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.41
reportsL2IfaceActiveJackIndexThe current active jack index.ro
INTEGER
.1.3.6.1.4.1.2697.1.5.100.3.1.1.1.42
reportsHardware
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.3.2
reportsHardwarePSStatusEach 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.ro
OCTET STRING
.1.3.6.1.4.1.2697.1.5.100.3.2.1
reportsHardwareFanStatusEach OCTET holds the status of 1 fan 1 - Fan failed 2 - Fan OKro
OCTET STRING
.1.3.6.1.4.1.2697.1.5.100.3.2.2
reportsHardwareTemperatureThe internal temperature of the unit in degrees Celsius.ro
INTEGER
.1.3.6.1.4.1.2697.1.5.100.3.2.3
reportsHardwarePSVoltageEach 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;ro
OCTET STRING
.1.3.6.1.4.1.2697.1.5.100.3.2.4
reportsIfJack
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.3.3
reportsIfJackTableInformation about the external jacks attached to MAUs attached to an interface.
SEQUENCE OF ReportsIfJackEntry
.1.3.6.1.4.1.2697.1.5.100.3.3.2
reportsIfJackEntryAn entry in the table, containing information about a particular jack.
ReportsIfJackEntry
.1.3.6.1.4.1.2697.1.5.100.3.3.2.1
reportsIfJackIndexThis variable uniquely identifies the jack described by this entry from among other jacks attached to the same MAU.
Integer32
.1.3.6.1.4.1.2697.1.5.100.3.3.2.1.1
reportsIfJackTypeThe jack connector type, as it appears on the outer side of the system.ro
ModuleHwType
.1.3.6.1.4.1.2697.1.5.100.3.3.2.1.2
test
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.4
commands
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.5
batmSwitchConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.6
batmSwitchMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.100.6.2
acs25L4282
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.500
acs25L4282t5
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.502
vol5000
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.996
vol4000
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.998
vol0215
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.5.999
ipSwitch
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.1.6
batm-mgmt
OBJECT IDENTIFIER
.1.3.6.1.4.1.2697.2
BATM-SWITCH-MIB - SNMP MIB Reference | MIBs Explorer