IBM2210-MIB
Detailed view of the defined objects, syntax rules, and hierarchical paths.
Imported Objects
Objects
41 total| Object Name |
|---|
proteon OBJECT IDENTIFIER .1.3.6.1.4.1.1 |
RFC1213-MIB Unknown .1.3.6.1.4.1.1 |
proXfaceGenericTableA table of information about each interface. SEQUENCE OF ProXfaceGenericEntry .1.3.6.1.4.1.1.2 |
proXfaceGenericEntryAn entry containing objects to describe the
interface. ProXfaceGenericEntry .1.3.6.1.4.1.1.2.1 |
proXfaceGenericTypeThe type of the interface, according to the internal
net identifier.ro Enumeration .1.3.6.1.4.1.1.2.1.1 |
proXfaceGenericCSRThe Command and Status Register address for the
interface.ro INTEGER .1.3.6.1.4.1.1.2.1.2 |
proXfaceGenericIntVecThe multi-bus interrupt vector for the interface.ro INTEGER .1.3.6.1.4.1.1.2.1.3 |
proXfaceGenericMaintIntThe number of seconds before the next interface
maintenance.ro INTEGER .1.3.6.1.4.1.1.2.1.4 |
proXfaceGenericMaintLimThe number of maintenance check failures permitted
before a self test is run.ro INTEGER .1.3.6.1.4.1.1.2.1.5 |
proXfaceGenericNextTestThe number of seconds before the next self test.ro INTEGER .1.3.6.1.4.1.1.2.1.6 |
proXfaceGenericNextMaintThe number of seconds between maintenance checks.ro INTEGER .1.3.6.1.4.1.1.2.1.7 |
proXfaceGenericMaintCntThe number of failed maintenance checks since the
last successful maintenance check.ro Counter .1.3.6.1.4.1.1.2.1.8 |
proXfaceGenericMaintFailsThe total number of maintenance failures on this
interface.ro Counter .1.3.6.1.4.1.1.2.1.9 |
proXfaceGenericTestPassesThe total number of self test successes on this
interface.ro Counter .1.3.6.1.4.1.1.2.1.10 |
proXfaceGenericTestFailsThe total number of self test failures on this
interface.ro Counter .1.3.6.1.4.1.1.2.1.11 |
proXfaceGenericModuleIdThe module identifier of this interface, this
object is relevant only to the CNX and DNX
platforms. It uniquely identifies the interface
card-type.
It will always be '0' for the IBM2210 platform.ro INTEGER .1.3.6.1.4.1.1.2.1.12 |
proto OBJECT IDENTIFIER .1.3.6.1.4.1.1.3 |
general OBJECT IDENTIFIER .1.3.6.1.4.1.1.3.1 |
proip OBJECT IDENTIFIER .1.3.6.1.4.1.1.3.2 |
defgw OBJECT IDENTIFIER .1.3.6.1.4.1.1.3.2.1 |
proProtoIpDefGwAddressThe Internet address of the default gateway for the
router.ro IpAddress .1.3.6.1.4.1.1.3.2.1.1 |
proProtoIpDefGwCostThe cost of the default gateway for the router.ro INTEGER .1.3.6.1.4.1.1.3.2.1.2 |
proProtoIpDefGwAgeThe age of the default gateway for the router.ro INTEGER .1.3.6.1.4.1.1.3.2.1.3 |
pDot3ChipSets OBJECT IDENTIFIER .1.3.6.1.4.1.1.5 |
pDot3ChipMC68EN360 OBJECT IDENTIFIER .1.3.6.1.4.1.1.5.1 |
ibm OBJECT IDENTIFIER .1.3.6.1.4.1.2 |
ibmProd OBJECT IDENTIFIER .1.3.6.1.4.1.2.6 |
ibm2210 OBJECT IDENTIFIER .1.3.6.1.4.1.2.6.72 |
ibmElsTrapV1An ELS trap event.
Note that this trap is being deprecated and will not be
supported in all future releases.
The objects proELSTrapVar1 through proElsTrapVar9 are
conditionally included in this trap to carry variable
data fields from the ELS message. These objects are not
carried as object IDs as defined, but in fact are data
objects. Their syntax will change depending on the
data they cary for a particular trap instance. TRAP-TYPE .1.3.6.1.4.1.2.6.72.0.1 |
ibmElsTrapV2When the routing subsystem ELS component is configured to
generate SNMP traps, the following trap is generated.
It contains a single varBind containing a text string in one
of the two following formats.
If ELS timestamping is enabled:
hr:min:sec subsys_name.event_num: message_text
For example - 09:32:56 IP.008: no rte 9.7.1.8 -> 9.7.4.3 dsc
If ELS timestamping is disabled:
subsys_name.event_num: message_text
For example - IP.008: no rte 9.7.1.8 -> 9.7.4.3 dsc TRAP-TYPE .1.3.6.1.4.1.2.6.72.0.2 |
ibm2210admin OBJECT IDENTIFIER .1.3.6.1.4.1.2.6.72.1 |
ibm2210system OBJECT IDENTIFIER .1.3.6.1.4.1.2.6.72.2 |
ibm2210hardware OBJECT IDENTIFIER .1.3.6.1.4.1.2.6.72.3 |
ibm2210hardwareinfo OBJECT IDENTIFIER .1.3.6.1.4.1.2.6.72.3.1 |
ibmServiceGenericTableA table of information about each service port. SEQUENCE OF IbmServiceGenericEntry .1.3.6.1.4.1.2.6.72.3.1.1 |
ibmServiceGenericEntryAn entry containing objects to describe the
service port. IbmServiceGenericEntry .1.3.6.1.4.1.2.6.72.3.1.1.1 |
ibmServiceGenericPortThe number of service port. On 12x and 1Sx/1Ux models,
only one service port exists and is designated #1. On
x4x models, the lower paort is designated #1, the upper
port is #2.ro INTEGER .1.3.6.1.4.1.2.6.72.3.1.1.1.1 |
ibmServiceGenericBaurdrateThe baudrate of service port.ro INTEGER .1.3.6.1.4.1.2.6.72.3.1.1.1.2 |
ibmServiceGenericTypeThe card type of service port. On 12x, 1Sx and 1Ux
models, the second row will always indeicate nocard(3).ro Enumeration .1.3.6.1.4.1.2.6.72.3.1.1.1.3 |
ibm2210routing OBJECT IDENTIFIER .1.3.6.1.4.1.2.6.72.4 |
ibm2210switching OBJECT IDENTIFIER .1.3.6.1.4.1.2.6.72.5 |
More MIBs from Proteon
Browse all ProteonMIBs →SNMP MIB module
The LANCOM-1711-PLUS-MIB provides the management information base definitions required for SNMP-based monitoring and configuration of the LANCOM 1711 PLUS router, enabling the retrieval of device-specific operational metrics such as interface statistics, system health indicators, and routing table states.
The LANCOM-1722-MIB module enables SNMP-based monitoring and management of the LANCOM 1722 VoIP gateway, specifically exposing Annex B-defined metrics for voice session states, call quality parameters, and telephony interface statistics.
The LANCOM-1721-MIB module provides SNMP management capabilities for the LANCOM 1721 VPN router, specifically exposing metrics defined in Annex B to monitor VPN tunnel states, security associations, and interface statistics. This module enables network administrators to track connection status, throughput counters, and error conditions for the device's integrated VPN functionality.
The LANCOM-1711-MIB module enables monitoring and management of VPN tunnel states, cryptographic session statistics, and interface parameters specifically for LANCOM 1711+ series routers. It provides access to counters for IPsec and PPTP tunnel establishment failures, throughput metrics, and device health indicators required for maintaining secure WAN connectivity on this hardware platform.
The LCOS-SX-MIB module provides SNMP management definitions for Brocade (now Broadcom) LCOS SX switches, enabling the monitoring of Layer 2 Ethernet switch metrics including port status, traffic counters, error statistics, and spanning tree states.