I'm working with LLDP for the first time and currently unable to get a 7945 ip phone to register with a Cisco 3560-E series switch. So far, I've enabled LLDP globally on the switch, turned on transmit/receive, and initialized "lldp med-tlv-select inventory-management" on the interface the phone is connected to. I also have LLDP for the phone configured at the device level in UCCM (ver 7.1). There is no network-policy configured at this point.
When I run a show lldp neighbor, I'm only seeing the connected IDF switch, no media endpoint device(s). Right now, only one IP phone is plugged into this switch.
--> show lldp interface output:
Tx state: IDLE
Rx state: WAIT FOR FRAME
Is configuring an lldp based network policy required and if so, do I need to apply it to the vlan or the interface?
Note: By default Cisco switches do not send out what Cisco term as LLDP-MED
LLDPDU which includes the Network Policy TLV until an LLDP-MED packet is
received by the switch port. The Network Policy TLV is used to advertise to any
attached device what VLAN to use for sending traffic. Once the Cisco switch port
receives a LLDP-MED packet from the attached device, the switch will then send only
LLDP-MED LLDPDU going forward.
The part that I'm not fully understanding is whether or not the phone will send out an LLDP-MED LLDPDU packet by default on it's own or do I need a Network-Policy applied to the interface to initialize this feature?
3) Apply the network-policy to the switchport interface(s)
lldp med-tlv-select network-policy
Note: This will remove any pre-existing voice vlan from the interface(s).
At this point, the LLDP-MED packets should start flowing between the IP phone and switch. However, in my case this didn't happen. I had to remove the network-policy that I had just applied to the interface and re-apply the voice vlan. For some reason (at least in my setup), the LLDP process did not trigger with the applying of the network-policy. It would only work after I applied the network-policy to the interface, removed the network-policy from the interface, then re-applied the voice vlan to the interface. I have a TAC case open regarding this at the moment and will post my findings if applicable.
Hope this helps any other newbies who may have experienced anything similar to this.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...