All MIBs › TN-SAP-MIB › tnReceivedTCN
tnReceivedTCN
Module: TN-SAP-MIB
OID (symbolic): TN-SAP-MIB::tnReceivedTCN
OID (numeric): 1.3.6.1.4.1.7483.6.1.3.4.5.0.6
Node type: NOTIFICATION-TYPE
Description:
The tnReceivedTCN notification is generated when a SAP has received TCN from another bridge. This bridge will either have its configured BPDU with the topology change flag set if it is a root bridge, or it will pass TCN to its root bridge. Eventually the address aging timer for the forwarding database will be made shorter for a short period of time. No recovery is needed.
Examples
Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):
snmptrap -v2c -c public <manager> '' TN-SAP-MIB::tnReceivedTCN snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.7483.6.1.3.4.5.0.6
Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):
snmptrapd -f -Lo -c /dev/null authCommunity log public
Example snmptrapd log entry:
zoo11-linux.zoo [UDP: [192.168.30.111]:55347->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (167519795) 19 days, 9:19:57.95 SNMPv2-MIB::snmpTrapOID.0 = OID: TN-SAP-MIB::tnReceivedTCN
OID Breakdown
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | BIANCA-BRICK-PPP-MIB |
| 1.3.6 | dod | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1 | internet | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4 | private | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.4.1 | enterprises | ANIROOT-MIB |
| 1.3.6.1.4.1.7483 | tropic | TROPIC-GLOBAL-REG |
| 1.3.6.1.4.1.7483.6 | tnProducts | TROPIC-GLOBAL-REG |
| 1.3.6.1.4.1.7483.6.1 | tnSRMIB | TROPIC-GLOBAL-REG |
| 1.3.6.1.4.1.7483.6.1.3 | tnSRNotifyPrefix | TROPIC-GLOBAL-REG |
| 1.3.6.1.4.1.7483.6.1.3.4 | tnServNotifications | TN-SERV-MIB |
| 1.3.6.1.4.1.7483.6.1.3.4.5 | tnTstpTrapsPrefix | TN-SERV-MIB |
| 1.3.6.1.4.1.7483.6.1.3.4.5.0 | tnTstpTraps | TN-SERV-MIB |
| 1.3.6.1.4.1.7483.6.1.3.4.5.0.6 | tnReceivedTCN | TN-SAP-MIB |