SNMP and MIBS8-24 Express5800/ftServer: System Administrator’s Guide for the Linux Operating SystemThe instances of interest are the following:These are the instances to check for when pulling cables. State changes includeDUPLEX, SIMPLEX, BROKEN, and of course, various counters such as frames andcollisions. (See ‘‘OpState:State Definitions’’ on page 8-158 for state changeidentification.)3. Run snmpwalk on the ftcEtherState OID before and after pulling each cable:# snmpwalk -v 1 -c private -t 40 localhost ftcEtherStateSRA-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 afterdiff comparison. For example, in your work area, run snmpwalk for the entireSRA-ftLinux-MIB file and dump that data to a file. Pull the cable, then run snmpwalkagain and dump it to another file.Finally, run diff on the two files to see all Express5800/ftServer objects that havechanged because of the fault insertion. You may want to put these commands into ashell script for easier testing.SNMP and MIBSThe SRA-ftLinux-MIB file maps ftServer device definitions for management byNet-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 bemanaged.InstanceInstance Name(I/O element / Slot) DeviceftcEtherInstanceName.3 10/5 eth080010ftcEtherInstanceName.4 10/5 eth080011ftcEtherInstanceName.5 11/5 eth000010ftcEtherInstanceName.6 11/5 eth000011
