CISCO-TS-STACK-MIB :: ciscoTsStackSwitchSPANMonitoredTrCRFs

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-TS-STACK-MIBciscoTsStackSwitchSPANMonitoredTrCRFs

ciscoTsStackSwitchSPANMonitoredTrCRFs

Module: CISCO-TS-STACK-MIB

OID (symbolic): CISCO-TS-STACK-MIB::ciscoTsStackSwitchSPANMonitoredTrCRFs

OID (numeric): 1.3.6.1.4.1.9.5.32.2.1.1.29

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-write

Description: Token Ring Concentrator Facilities (TrCRFs) for which traffic on the port specified by ciscoTsStackSwitchSPANMonitoredPort should be monitored. Individual TrCRFs can be selected for monitoring only on trunk ports.

Each octet within the value of this object specifies a set of eight TrCRFs, with the first octet specifying TrCRFs 1 through 8, the second octet specifying TrCRFs 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered TrCRF, and the least significant bit represents the highest numbered TrCRF. Thus, each TrCRF of the stack is represented by a single bit within the value of this object. If that bit has a value of '1' then that TrCRF is included in the set of TrCRFs for which traffic should be monitored ; the TrCRF is not included if its bit has a value of '0'. The default is all zeros.

Get requests for this object will return all zeros if ciscoTsStackSwitchSPANMonitoredPort specifies a non-trunk port. Set requests for this object will be rejected with a 'badValue' error if ciscoTsStackSwitchSPANMonitoredPort specifies a non-trunk port.

What is ciscoTsStackSwitchSPANMonitoredTrCRFs?

This read-write OCTET STRING (128 bytes) selects which specific TrCRFs' traffic gets mirrored to the SPAN monitored port, but the description notes this per-TrCRF filtering only works on trunk ports, you can't selectively monitor individual TrCRFs on a non-trunk port. An admin troubleshooting a problem isolated to one VLAN-like TrCRF within a trunk would set only that TrCRF's bit here rather than mirroring the trunk's entire mixed traffic to the analyzer. This gives more granular visibility than ciscoTsStackSwitchSPANMonitoredPort alone provides on a trunk carrying many TrCRFs.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.5.32.2.1.1.29
snmpwalk -v2c -c public <target> CISCO-TS-STACK-MIB::ciscoTsStackSwitchSPANMonitoredTrCRFs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.5.32.2.1.1.29.1
snmpget -v2c -c public <target> CISCO-TS-STACK-MIB::ciscoTsStackSwitchSPANMonitoredTrCRFs.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.9.5.32.2.1.1.29.1 s <value>

Start monitoring Cisco stackable terminal server (async port aggregation, legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-TS-STACK-MIB::ciscoTsStackSwitchSPANMonitoredTrCRFs OID value, configure state conditions and alerts, and monitor any Cisco stackable terminal server (async port aggregation, legacy) from a single console.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.5workgroupCISCO-ES-STACK-MIB
1.3.6.1.4.1.9.5.32tsStackCISCO-STACK-MIB
Numeric OIDNameModule
1.3.6.1.4.1.9.5.32.2ciscoTsStackCISCO-TS-STACK-MIB
1.3.6.1.4.1.9.5.32.2.1ciscoTsStackTableCISCO-TS-STACK-MIB
1.3.6.1.4.1.9.5.32.2.1.1ciscoTsStackEntryCISCO-TS-STACK-MIB
1.3.6.1.4.1.9.5.32.2.1.1.29ciscoTsStackSwitchSPANMonitoredTrCRFsCISCO-TS-STACK-MIB