LLDP trasport over Pseudowire ASR9K

[Atahar Khan]

We are trying to transport LLDP over PW and CE devices can not see the LLDP neighbors one CE. Can anyone confirm ASR9K transport LLDP over PW as I did not find LLDP specific information on CCO and its not working ??

www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k_r4-1/interfaces/configuration/guide/hc41asr9kbook/hc41ethi.html

We could only see STP neighbor with this setup but not LLDP

Topology :

CE(LLDP Enabled) ------- ASR903 (PW End A)---------MPLS-------------ASR9K( PW End B)----- CE( LLDP Enabled)

IF we move the link from ASR9K to ASR903 , LLDP & STP neighbors can be seen on CE.

ASR9K Configuration :

RP/0/RSP0/CPU0:ASR9K#sh running-config int gig 0/5/1/1

Tue Mar 24 00:56:23.707 IST

interface GigabitEthernet0/5/1/1

mtu 9216

speed 1000

load-interval 30

!

RP/0/RSP0/CPU0:ASR9K#sh running-config int gig 0/5/1/1.100

Tue Mar 24 00:56:31.582 IST

interface GigabitEthernet0/5/1/1.4002 l2transport

encapsulation dot1q 100

rewrite ingress tag pop 1 symmetric

l2protocol cpsv tunnel

!

l2vpn
 logging
  pseudowire
 !
 xconnect group ABC_xconnect
  p2p ABC
   interface gig 0/5/1/1.100
   neighbor ipv4 192.168.54.11 pw-id 1001

ASR903 Configuration

S2BLRACPTNXXXACR007#sh run  int gig 0/3/4

Building configuration...

Current configuration : 342 bytes

!

interface GigabitEthernet0/3/4

mtu 9202

no ip address

negotiation auto

no keepalive

service instance 1 ethernet

  encapsulation default

  l2protocol tunnel stp lldp

  xconnect 192.168.53.65 1001 encapsulation mpls

!

end

[tcalvin2006]

Were you ever able to get it to work over the ASR9000?

Can anyone from Cisco provide any insight. 

This is starting to become a very common request from customers and haven't been able to get it it to work either. 

[Atahar Khan]

Yes, We made it work after tweaking the configuration. Please refer attached PDF for config example.

[xthuijs]

hi atahar, tcalvin,

few comments, the command: l2protocol cpsv tunnel is not necessary for the asr9k, it was implemented for some backward catalyst compatibility but is no longer needed.

by default the a9k is transparent on l2 if the service is not configured locally, otherwise the packets are intercepted such as stp, cdp etc.

what seems a bit problematic in this config example above is the encap dot1q 100 on one end and the other end uses an encap default, that might make some vlans mis matched.

regards

xander