SNMP and MIBS
8-24
Express5800/
ftServer
: System Administrator’s Guide for the Linux Operating System
The instances of interest are the following:
These are the instances to check for when pulling cables. State changes include
DUPLEX
,
SIMPLEX
,
BROKEN
, and of course, various counters such as frames and
collisions. (See
‘‘OpState:State Definitions’’ on page 8-158
for state change
identification.)
3. Run
snmpwalk
on the
ftcEtherState
OID before and after pulling each cable:
#
snmpwalk -v 1 -c private -t 40 localhost ftcEtherState
SRA-ftLinux-MIB::ftcEtherState.1 = INTEGER: triplex(22)
SRA-ftLinux-MIB::ftcEtherState.2 = INTEGER: device-ready(13)
SRA-ftLinux-MIB::ftcEtherState.3 = INTEGER: simplex(20)
SRA-ftLinux-MIB::ftcEtherState.4 = INTEGER: device-ready(13)
SRA-ftLinux-MIB::ftcEtherState.5 = INTEGER: simplex(20)
SRA-ftLinux-MIB::ftcEtherState.6 = INTEGER: device-ready(13)
In practice, you will actually redirect your
snmpwalk
output to files for before and after
diff
comparison. For example, in your work area, run
snmpwalk
for the entire
SRA-ftLinux-MIB file and dump that data to a file. Pull the cable, then run
snmpwalk
again and dump it to another file.
Finally, run
diff
on the two files to see all Express5800/
ftServer
objects that have
changed because of the fault insertion. You may want to put these commands into a
shell script for easier testing.
SNMP and MIBS
The SRA-ftLinux-MIB file maps ftServer device definitions for management by
Net-SNMP and ftlSNMP. These device definitions map to addressable devices in the
/proc
virtual file system. ftlSNMP can retrieve operation state data on these devices.
The contents of SRA-ftLinux-MIB provide useful remarks about objects that can be
managed.
Instance
Instance Name
(I/O element / Slot)
Device
ftcEtherInstanceName.3
10/5
eth080010
ftcEtherInstanceName.4
10/5
eth080011
ftcEtherInstanceName.5
11/5
eth000010
ftcEtherInstanceName.6
11/5
eth000011
