×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

L2VPN + VLANS not passing traffic

Unanswered Question
Apr 9th, 2014
User Badges:

Hello Everyone.

I am working on getting L2VPN between two CE routers, which essentially need to have the equivalent of an 802.1q trunk between them. I have created a diagram to help illustrate my point. Right now I can not ping between the CE routers.

Here is the configuration:

CE ROUTER 1

interface GigabitEthernet0/1/1
mtu 9216
no ip address
speed 1000
no negotiation auto
cdp enable
service instance 1 ethernet
  encapsulation dot1q 72
  bridge-domain 72
!
interface BDI72
ip address 10.12.0.2 255.255.254.0
standby 0 ip 10.12.0.1
encapsulation dot1Q 72

PE ROUTER 1

interface GigabitEthernet0/1/0/3
mtu 9216
l2transport
  l2protocol cpsv tunnel

l2vpn
xconnect-group SITE-TO-SITE
  p2p POINT-TO-POINT
   interface GigabitEthernet0/1/0/3
    neighbor 10.208.255.5 pw-id 8

Configuration is mirrored across the 2nd PE & CE routers

Digram:

http://i.imgur.com/wvQLAD3.png

What am I missing?

 

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Rivalino Tamaela Fri, 04/11/2014 - 07:23
User Badges:
  • Cisco Employee,

Have you checked if PW or AC is up? You can see from following command:

- show l2vpn xconnect neighbor 10.208.255.5 pw-id 8 detail

 

thanks,

rivalino

Evan Roggenkamp Fri, 04/11/2014 - 08:25
User Badges:

Hello Rivalino and thank you for taking a look.

 

Below is the output. As you can see, I have modified my attachment circuit a bit in the process of troubleshooting, but the problem remains the same regardless of configuring the interface as I have above, or using vlan subinterfaces as shown here.

 

Group SITE-TO-SITE, XC POINT-TO-POINT, state is up; Interworking none<br />&nbsp; AC: GigabitEthernet0/1/0/24.72, state is up<br />&nbsp; &nbsp; Type VLAN; Num Ranges: 1<br />&nbsp; &nbsp; VLAN ranges: [72, 72]<br />&nbsp; &nbsp; MTU 9086; XC ID 0x440077; interworking none<br />&nbsp; &nbsp; Statistics:<br />&nbsp; &nbsp; &nbsp; packets: received 20831, sent 0<br />&nbsp; &nbsp; &nbsp; bytes: received 1372386, sent 0<br />&nbsp; &nbsp; &nbsp; drops: illegal VLAN 0, illegal length 0<br />&nbsp; PW: neighbor 10.208.255.5, PW ID 8, state is up ( established )<br />&nbsp; &nbsp; PW class VLAN-TEST, XC ID 0xc000006f<br />&nbsp; &nbsp; Encapsulation MPLS, protocol LDP<br />&nbsp; &nbsp; Source address 10.80.255.1<br />&nbsp; &nbsp; PW type Ethernet, control word disabled, interworking none<br />&nbsp; &nbsp; PW backup disable delay 0 sec<br />&nbsp; &nbsp; Sequencing not set&nbsp; &nbsp; PW Status TLV in use<br />&nbsp; &nbsp; &nbsp; MPLS &nbsp; &nbsp; &nbsp; &nbsp; Local &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Remote &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br />&nbsp; &nbsp; &nbsp; ------------ ------------------------------ -----------------------------<br />&nbsp; &nbsp; &nbsp; Label &nbsp; &nbsp; &nbsp; &nbsp;289941 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 16011 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<br />&nbsp; &nbsp; &nbsp; Group ID &nbsp; &nbsp; 0x20006c0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0x2000300 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<br />&nbsp; &nbsp; &nbsp; Interface &nbsp; &nbsp;GigabitEthernet0/1/0/24.72 &nbsp; &nbsp; GigabitEthernet0/1/0/3.72 &nbsp; &nbsp;&nbsp;<br />&nbsp; &nbsp; &nbsp; MTU &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;9086 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 9086 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br />&nbsp; &nbsp; &nbsp; Control word disabled &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; disabled &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br />&nbsp; &nbsp; &nbsp; PW type &nbsp; &nbsp; &nbsp;Ethernet &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Ethernet &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br />&nbsp; &nbsp; &nbsp; VCCV CV type 0x2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0x2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(LSP ping verification) &nbsp; &nbsp; &nbsp; &nbsp;(LSP ping verification) &nbsp; &nbsp; &nbsp;&nbsp;<br />&nbsp; &nbsp; &nbsp; VCCV CC type 0x6 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0x6 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(router alert label) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (router alert label) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(TTL expiry) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (TTL expiry) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br />&nbsp; &nbsp; &nbsp; ------------ ------------------------------ -----------------------------<br />&nbsp; &nbsp; Incoming Status (PW Status TLV):<br />&nbsp; &nbsp; &nbsp; Status code: 0x0 (Up) in Notification message<br />&nbsp; &nbsp; Outgoing Status (PW Status TLV):<br />&nbsp; &nbsp; &nbsp; Status code: 0x0 (Up) in Notification message<br />&nbsp; &nbsp; MIB cpwVcIndex: 3221225583<br />&nbsp; &nbsp; Create time: 10/04/2014 21:57:03 (11:58:02 ago)<br />&nbsp; &nbsp; Last time status changed: 10/04/2014 21:57:03 (11:58:02 ago)<br />&nbsp; &nbsp; Statistics:<br />&nbsp; &nbsp; &nbsp; packets: received 0, sent 20831<br />&nbsp; &nbsp; &nbsp; bytes: received 0, sent 1372386

 

Something to note is we have other pseudowires of this nature functioning, but none facing an EVC-based interface as in this example, simply IOS 802.1q trunks - and they work well. 

Rivalino Tamaela Fri, 04/11/2014 - 08:55
User Badges:
  • Cisco Employee,

On AC counter we can see that it detects incoming packets from CE:

AC: GigabitEthernet0/1/0/24.72, state is up
    Type VLAN; Num Ranges: 1
    VLAN ranges: [72, 72]
    MTU 9086; XC ID 0x440077; interworking none
    Statistics:
      packets: received 20831, sent 0
      bytes: received 1372386, sent 0

 

On PW statistics, we can see that those packets were forwarded to remote PE:

 Statistics:
      packets: received 0, sent 20831
      bytes: received 0, sent 1372386

 

However, we do not see received packets from remote PE to this PE:

 Statistics:
      packets: received 0, sent 20831   <-- received counter is zero
      bytes: received 0, sent 1372386 

 

The next troubleshooting step is to take a look remote PE and doing the same command. Check the statistics for AC and PW. If AC's statistics in zero, so troubleshoot the link between PE and CE.

 

thanks,

rivalino

Evan Roggenkamp Fri, 04/11/2014 - 10:28
User Badges:

 

Ah, yes. These are the statistics from the remote end:

Group SITE-TO-SITE, XC POINT-TO-POINT, state is up; Interworking none<br />&nbsp; AC: GigabitEthernet0/1/0/3.72, state is up<br />&nbsp; &nbsp; Type VLAN; Num Ranges: 1<br />&nbsp; &nbsp; VLAN ranges: [72, 72]<br />&nbsp; &nbsp; MTU 9086; XC ID 0x88001c; interworking none<br />&nbsp; &nbsp; Statistics:<br />&nbsp; &nbsp; &nbsp; packets: received 0, sent 26091<br />&nbsp; &nbsp; &nbsp; bytes: received 0, sent 2013691

Pseudowire:

&nbsp; &nbsp; Statistics:&nbsp; &nbsp; &nbsp; packets: received 26091, sent 0<br />&nbsp; &nbsp; &nbsp; bytes: received 2013691, sent 0

 

I cleared the counters on both ends of this circuit and did a few pings

CE FACING PE

GigabitEthernet1/3/0 is up, line protocol is up&nbsp;<br />&nbsp; Hardware is SPA-2X1GE-V2, address is 88f0.774a.8170 (bia 88f0.774a.8170)<br />&nbsp; Description: *** L2 LINK FACING PE FOR PSEUDOWIRE ***<br />&nbsp; MTU 9100 bytes, BW 1000000 Kbit/sec, DLY 10 usec,&nbsp;<br />&nbsp; &nbsp; &nbsp;reliability 255/255, txload 1/255, rxload 1/255<br />&nbsp; Encapsulation ARPA, loopback not set<br />&nbsp; Keepalive not supported&nbsp;<br />&nbsp; Full Duplex, 1000Mbps, link type is force-up, media type is LX<br />&nbsp; output flow-control is on, input flow-control is on<br />&nbsp; ARP type: ARPA, ARP Timeout 04:00:00<br />&nbsp; Last input 00:00:25, output 00:00:08, output hang never<br />&nbsp; Last clearing of &quot;show interface&quot; counters 00:16:35<br />&nbsp; Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0<br />&nbsp; Queueing strategy: fifo<br />&nbsp; Output queue: 0/40 (size/max)<br />&nbsp; 5 minute input rate 0 bits/sec, 0 packets/sec<br />&nbsp; 5 minute output rate 0 bits/sec, 0 packets/sec<br />&nbsp; &nbsp; &nbsp;450 packets input, 39525 bytes, 0 no buffer<br />&nbsp; &nbsp; &nbsp;Received 21 broadcasts (0 IP multicasts)<br />&nbsp; &nbsp; &nbsp;0 runts, 0 giants, 0 throttles&nbsp;<br />&nbsp; &nbsp; &nbsp;0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored<br />&nbsp; &nbsp; &nbsp;0 watchdog, 429 multicast, 0 pause input<br />&nbsp; &nbsp; &nbsp;23 packets output, 8987 bytes, 0 underruns<br />&nbsp; &nbsp; &nbsp;0 output errors, 0 collisions, 0 interface resets<br />&nbsp; &nbsp; &nbsp;0 unknown protocol drops<br />&nbsp; &nbsp; &nbsp;0 babbles, 0 late collision, 0 deferred<br />&nbsp; &nbsp; &nbsp;0 lost carrier, 0 no carrier, 0 pause output<br />&nbsp; &nbsp; &nbsp;0 output buffer failures, 0 output buffers swapped out

PE FACING CE:

GigabitEthernet0/1/0/3 is up, line protocol is up&nbsp;<br />&nbsp; Interface state transitions: 17<br />&nbsp; Hardware is GigabitEthernet, address is 6c9c.ed0a.3f09 (bia 6c9c.ed0a.3f09)<br />&nbsp; Description: Uplink to CE ROUTER FOR PSEUDOWIRE<br />&nbsp; Internet address is Unknown<br />&nbsp; MTU 9100 bytes, BW 1000000 Kbit (Max: 1000000 Kbit)<br />&nbsp; &nbsp; &nbsp;reliability 255/255, txload 0/255, rxload 0/255<br />&nbsp; Encapsulation ARPA,<br />&nbsp; Full-duplex, 1000Mb/s, LXFDX, link type is force-up<br />&nbsp; output flow control is off, input flow control is off<br />&nbsp; loopback not set,<br />&nbsp; Last input 00:00:30, output 00:00:00<br />&nbsp; Last clearing of &quot;show interface&quot; counters 00:14:04<br />&nbsp; 5 minute input rate 0 bits/sec, 0 packets/sec<br />&nbsp; 5 minute output rate 0 bits/sec, 0 packets/sec<br />&nbsp; &nbsp; &nbsp;19 packets input, 7367 bytes, 0 total input drops<br />&nbsp; &nbsp; &nbsp;19 drops for unrecognized upper-level protocol<br />&nbsp; &nbsp; &nbsp;Received 0 broadcast packets, 19 multicast packets<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0 runts, 0 giants, 0 throttles, 0 parity<br />&nbsp; &nbsp; &nbsp;0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort<br />&nbsp; &nbsp; &nbsp;377 packets output, 33266 bytes, 0 total output drops<br />&nbsp; &nbsp; &nbsp;Output 14 broadcast packets, 363 multicast packets<br />&nbsp; &nbsp; &nbsp;0 output errors, 0 underruns, 0 applique, 0 resets<br />&nbsp; &nbsp; &nbsp;0 output buffer failures, 0 output buffers swapped out<br />&nbsp; &nbsp; &nbsp;2 carrier transitions

I wonder what could be causing the problem here? Bad SFP???

 

Rivalino Tamaela Fri, 04/11/2014 - 11:33
User Badges:
  • Cisco Employee,

We need to troubleshoot further on PE-CE link. Does number of packets sent by CE matches with number of packets received by PE? Or, you can try to configure subinterface on PE into layer 3 subinterface (removing from PE), and then ping from directly connected CE to that ip address.

 

thanks,

Rivalino

Evan Roggenkamp Sun, 04/13/2014 - 12:02
User Badges:

Rivalino I do thank you for your assistance. You have helped me narrow it down, and you are correct. I have done as you say, and the link in question is not passing traffic. Why this is still eludes me, as the configurations are the same, and the links are up! Do you have any theories?

I've attached the configuration comparison.

 

EDIT:

 

Today I removed the EVC and the sub-interface from the CE to PE configuration that was giving trouble and just added ipv4 address there.

It pings fine! So something is wrong with the L3 sub-interface or the EVC configuration? Since it is the same on the other side, what could it be?? Is this a bug?

Strange messages in my logs as well. Attached as they do not fit on the page.

Rivalino Tamaela Mon, 04/14/2014 - 09:43
User Badges:
  • Cisco Employee,

When you change the config to L3 and it worked fine, this rules out hardware issue including the SFP. Then we need to take a look at the software in ASR1k. Unfortunately, I do not have expertise in CE's platform (i guess the image is IOS-XE). You might try to upgrade the image in CE router to latest release and see if this solve the problem.

Actions

This Discussion