All MIBs › TMU-MIB › fibTmuMatchStationInfo
fibTmuMatchStationInfo
Module: TMU-MIB
OID (symbolic): TMU-MIB::fibTmuMatchStationInfo
OID (numeric): 1.3.6.1.4.1.22.60.3.20.1.5
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: Information on the attached station: If BIT0 is set (value = 0x01) then this is definitely a 'sniffer' port (i.e. a station which is sending 'trace tool present' messages is located on this port). If BIT1 is set (value = 0x02) then its location is doubtful (System has been unable to resolve the location of this station). If BIT2 is set (value = 0x04) then station is not attached to one of the tmu's ports but rather to the trunk. If bit3 is set (value = 0x08) then station is one of the tmu's chips. If BIT4 is set (value = 0x10) then this is a station attached to the tmu (and not on the trunk). See remark in fibTmuMatchListValid above
What is fibTmuMatchStationInfo?
This is a bit-mapped status field describing the attached station: bit0 set means it's definitely a 'sniffer' port (a station sending 'trace tool present' messages); bit1 set means its location is doubtful (the system couldn't fully resolve it); bit2 set means the station is attached to the trunk rather than one of the Tmu's own ports; bit3 (and further bits per the source) flag it as one of the Tmu's own chipsets. Admins decode these bits to understand the nature of a matched station beyond just its address. For example, the sniffer-port bit being set would tell an admin a network analyzer is currently attached at that position on the ring.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.22.60.3.20.1.5 snmpwalk -v2c -c public <target> TMU-MIB::fibTmuMatchStationInfo
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.22.60.3.20.1.5.1 snmpget -v2c -c public <target> TMU-MIB::fibTmuMatchStationInfo.1
Start monitoring Legacy networking equipment, enterprise OID 22 fibronics (firmware inventory/fault-handling status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TMU-MIB::fibTmuMatchStationInfo OID value, configure state conditions and alerts, and monitor any Legacy networking equipment, enterprise OID 22 fibronics (firmware inventory/fault-handling status) from a single console.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.22 | spartacus | CMU-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.22.60 | tmu | TMU-MIB |
| 1.3.6.1.4.1.22.60.3 | tmuMatch | TMU-MIB |
| 1.3.6.1.4.1.22.60.3.20 | fibTmuMatchTable | TMU-MIB |
| 1.3.6.1.4.1.22.60.3.20.1 | fibTmuMatchEntry | TMU-MIB |
| 1.3.6.1.4.1.22.60.3.20.1.5 | fibTmuMatchStationInfo | TMU-MIB |