Switch management
User manual 58185_TREE M4/6-TX PN IP20_hdb_en_10
55/103
Integrated MIB engine
Managing MIBs
The switch has an integrated MIB engine. The engine manages the following
MIBs, whose relevant parts were implemented.
MIB-II (RFC 1213)
System Group
Contains basic information about the device
(e.g., description, uptime, etc.)
Interface Group
Contains generic information about each interface/port
(e.g., speed, transferred packets, etc.)
EtherLike MIB (RFC 1643)
Dot3StatsTable Group
Contains Ethernet-specific information about errors at each port
(e.g., collisions, CRC errors, carrier sense errors, etc.)
MAU-MIB (RFC 4836)
Q-BRIDGE-MIB (RFC 2674)
P-BRIDGE-MIB (RFC 2674)
BRIDGE-MIB (RFC 1493)
IF-MIB (RFC 2863)
SNMPv2-MIB (RFC 3418)
DISMAN-EVENT-MIB (RFC 2981)
LLDP-MIB
RMON (RFC 1757)
Statistics Group
Contains Ethernet-specific statistics for each port
(e.g., transferred packets, multicast packets, drop events, etc.)
Event Group
can be used to define events (send trap and/or log local) that can be
triggered by other RMON groups
Alarm Group
(not supported in Version 1.0.0)
Example:
We can use a request for the time at which the system was started as an ex-
ample.
This value is saved in the variable
sysUpTime
. The variable
sysUpTime
can
be found in the system group of the MIB-II. The resulting object identifier (OID)
is shown in Tab. 10-2: "Object Identifier (OID)":
Tab. 10-2: Object Identifier (OID)
Rules
Distinguishing between levels:
In order to distinguish between the various levels of the MIB tree, the indi-
vidual numbers are separated using decimal points.
Designating instances:
A zero is added to designate an object as an instance rather than a spec-
ification.
Based on these rules,
the OID for the variable sysUpTime in our example would be:
1.3.6.1.2.1.1.3.0
.
ISO
ORG
DOD
Internet MGMT
MIB-II
System
sysUpTime
1
3
6
1
2
1
1
3
