All MIBs › TN-LLDP-MIB › tnLldpConfigCdpAware
tnLldpConfigCdpAware
Module: TN-LLDP-MIB
OID (symbolic): TN-LLDP-MIB::tnLldpConfigCdpAware
OID (numeric): 1.3.6.1.4.1.868.2.5.151.1.2.2.1.4
Node type: OBJECT-TYPE
Type: TruthValue
Access: read-write
Description: Enables/disables CDP awareness for the interface.
CDP is Cisco's equivalent to LLDP.
The CDP operation is restricted to decoding incoming CDP frames (The switch doesn't transmit CDP frames). CDP frames are only decoded if LLDP on the port is enabled.
Only CDP TLVs that can be mapped to a corresponding field in the LLDP neighbors' table are decoded. All other TLVs are discarded (Unrecognized CDP TLVs and discarded CDP frames are not shown in the LLDP statistics.).
CDP TLVs are mapped onto LLDP neighbors' table as shown below.
CDP TLV 'Device ID' is mapped to the LLDP 'Chassis ID' field.
CDP TLV 'Address' is mapped to the LLDP 'Management Address' field. The CDP address TLV can contain multiple addresses, but only the first address is shown in the LLDP neighbors table.
CDP TLV 'Port ID' is mapped to the LLDP 'Port ID' field.
CDP TLV 'Version and Platform' is mapped to the LLDP 'System Description' field.
Both the CDP and LLDP support 'system capabilities', but the CDP capabilities cover capabilities that are not part of the LLDP. These capabilities are shown as 'others' in the LLDP neighbors' table.
If all ports have CDP awareness disabled the switch forwards CDP frames received from neighbor devices. If at least one port has CDP awareness enabled all CDP frames are terminated by the switch.
Note: When CDP awareness on a port is disabled the CDP information isn't removed immediately, but gets removed when the hold time is exceeded.
What is tnLldpConfigCdpAware?
Enables or disables CDP awareness on the interface so the switch can decode incoming Cisco Discovery Protocol frames (it never transmits CDP itself) and map recognized CDP fields - Device ID, Address, Port ID, and Version/Platform - into the corresponding columns of the LLDP neighbors table. It only applies while LLDP is enabled on the port, and turning it off does not immediately clear already-learned CDP-derived entries until their hold time expires.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.868.2.5.151.1.2.2.1.4 snmpwalk -v2c -c public <target> TN-LLDP-MIB::tnLldpConfigCdpAware
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.868.2.5.151.1.2.2.1.4.1 snmpget -v2c -c public <target> TN-LLDP-MIB::tnLldpConfigCdpAware.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.868.2.5.151.1.2.2.1.4.1 s <value>
Start monitoring Transition Networks media converters/switches (LLDP neighbor-discovery/timer config status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TN-LLDP-MIB::tnLldpConfigCdpAware OID value, configure state conditions and alerts, and monitor any Transition Networks media converters/switches (LLDP neighbor-discovery/timer config status) from a single console.
OID Breakdown
Upper-level ancestors (9 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.868 | transition | TRANSITION-SMI |
| 1.3.6.1.4.1.868.2 | products | TRANSITION-SMI |
| 1.3.6.1.4.1.868.2.5 | tnProducts | TRANSITION-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.868.2.5.151 | tnLldpMib | TN-LLDP-MIB |
| 1.3.6.1.4.1.868.2.5.151.1 | tnLldpMibObjects | TN-LLDP-MIB |
| 1.3.6.1.4.1.868.2.5.151.1.2 | tnLldpConfig | TN-LLDP-MIB |
| 1.3.6.1.4.1.868.2.5.151.1.2.2 | tnLldpConfigTable | TN-LLDP-MIB |
| 1.3.6.1.4.1.868.2.5.151.1.2.2.1 | tnLldpConfigEntry | TN-LLDP-MIB |
| 1.3.6.1.4.1.868.2.5.151.1.2.2.1.4 | tnLldpConfigCdpAware | TN-LLDP-MIB |