cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1351
Views
5
Helpful
3
Replies

VPLS on on CAT6506-E - xconnect up but no traffic

davek
Level 1
Level 1

I have two CAT6506-Es, and want to extend Vlan 624 over MPLS from one to the other:

router1:

l2 vfi VPLS manual 
 vpn id 624
 neighbor 10.0.0.3 encapsulation mpls

interface Vlan624
 ip address 100.64.1.1 255.255.255.0
 xconnect vfi VPLS

 

router 2:

l2 vfi VPLS manual 
 vpn id 624
 neighbor 10.0.0.4 encapsulation mpls

interface Vlan624
 ip address 100.64.1.2 255.255.255.0
 xconnect vfi VPLS


xconnect is up and we are getting the lables across:

router1:

#sh xconnect all
Legend:    XC ST=Xconnect State  S1=Segment1 State  S2=Segment2 State
  UP=Up       DN=Down            AD=Admin Down      IA=Inactive
  SB=Standby  HS=Hot Standby     RV=Recovering      NH=No Hardware

XC ST  Segment 1                         S1 Segment 2                         S2
------+---------------------------------+--+---------------------------------+--
UP     vfi  VPLS             UP mpls 10.0.0.3:624               UP
UP     ac   Vl624:624(Eth VLAN)          UP vfi  VPLS             UP

#sh mpls l2transport vc detail 
Local interface: VFI VPLS VFI up
  Interworking type is Ethernet
  Destination address: 10.0.0.3, VC ID: 624, VC status: up
    Output interface: none, imposed label stack {}
    Preferred path: not configured  
    Default path: active
    No adjacency
  Load Balance: none
  Flow Label: Disabled
  Create time: 00:57:15, last status change time: 00:00:04
  Signaling protocol: LDP, peer 10.0.0.3:0 up
    Targeted Hello: 10.0.0.4(LDP Id) -> 10.0.0.3, LDP is UP
    Status TLV support (local/remote)   : enabled/not supported
      LDP route watch                   : enabled
      Label/status state machine        : established, LruRru
      Last local dataplane   status rcvd: No fault
      Last local SSS circuit status rcvd: No fault
      Last local SSS circuit status sent: No fault
      Last local  LDP TLV    status sent: No fault
      Last remote LDP TLV    status rcvd: Not sent
      Last remote LDP ADJ    status rcvd: No fault
    MPLS VC labels: local 206, remote 97 
    Group ID: local 0, remote 0
    MTU: local 1500, remote 1500
    Remote interface description: 
  Sequencing: receive disabled, send disabled
  Control Word: On (configured: autosense)
  VC statistics:
    transit packet totals: receive 0, send 0
    transit byte totals:   receive 0, send 0
    transit packet drops:  receive 0, send 0

#sh mpls forwarding-table labels 206
Local      Outgoing   Prefix           Bytes Label   Outgoing   Next Hop    
Label      Label      or Tunnel Id     Switched      interface              
206        No Label   l2ckt(624)       0             none       point2point 

 

router 2:

#sh xconnect all
Legend:    XC ST=Xconnect State  S1=Segment1 State  S2=Segment2 State
  UP=Up       DN=Down            AD=Admin Down      IA=Inactive
  SB=Standby  HS=Hot Standby     RV=Recovering      NH=No Hardware

XC ST  Segment 1                         S1 Segment 2                         S2
------+---------------------------------+--+---------------------------------+--
UP     vfi  VPLS             UP mpls 10.0.0.4:624               UP
UP     ac   Vl624:624(Eth VLAN)          UP vfi  VPLS             UP


#sh mpls l2transport vc detail 
Local interface: VFI VPLS VFI up
  Interworking type is Ethernet
  Destination address: 10.0.0.4, VC ID: 624, VC status: up
    Output interface: none, imposed label stack {}
    Preferred path: not configured  
    Default path: active
    No adjacency
  Load Balance: none
  Flow Label: Disabled
  Create time: 01:00:47, last status change time: 00:00:00
  Signaling protocol: LDP, peer 10.0.0.4:0 up
    Targeted Hello: 10.0.0.3(LDP Id) -> 10.0.0.4, LDP is UP
    Status TLV support (local/remote)   : enabled/not supported
      LDP route watch                   : enabled
      Label/status state machine        : established, LruRru
      Last local dataplane   status rcvd: No fault
      Last local SSS circuit status rcvd: No fault
      Last local SSS circuit status sent: No fault
      Last local  LDP TLV    status sent: No fault
      Last remote LDP TLV    status rcvd: Not sent
      Last remote LDP ADJ    status rcvd: No fault
    MPLS VC labels: local 97, remote 206 
    Group ID: local 0, remote 0
    MTU: local 1500, remote 1500
    Remote interface description: 
  Sequencing: receive disabled, send disabled
  Control Word: On (configured: autosense)
  VC statistics:
    transit packet totals: receive 0, send 0
    transit byte totals:   receive 0, send 0
    transit packet drops:  receive 0, send 0

#sh mpls forwarding-table labels 97
Local      Outgoing   Prefix           Bytes Label   Outgoing   Next Hop    
Label      Label      or Tunnel Id     Switched      interface              
97         No Label   l2ckt(624)         0      none       point2point

 

And pseudowire pinging fine:

router1:

#ping mpls pseudowire 10.0.0.3 624
Sending 5, 100-byte MPLS Echos to 10.0.0.3,
     timeout is 2 seconds, send interval is 0 msec:

Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
  'L' - labeled output interface, 'B' - unlabeled output interface,
  'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,
  'M' - malformed request, 'm' - unsupported tlvs, 'N' - no label entry,
  'P' - no rx intf label prot, 'p' - premature termination of LSP,
  'R' - transit router, 'I' - unknown upstream index,
  'X' - unknown return code, 'x' - return code 0

Type escape sequence to abort.
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms

 

But I am unable to get packets across:

router1:

#ping 100.64.1.2 source 100.64.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 100.64.1.2, timeout is 2 seconds:

Packet sent with a source address of 100.64.1.1 

.....

Success rate is 0 percent (0/5)

#sh arp | i 100.64.1.2                     
Internet  100.64.1.2              0   Incomplete      ARPA

Also - there is a bunch of dynamically learned MAC addresses in vlan 624 on router 1 - I do not see these in the mac address table of router 2.

What is concerning here is the 

imposed label stack {}

there is no P router in-between these two routers, so the label get's popped for the neighbour:

#sh mpls forwarding-table 10.0.0.3    
Local      Outgoing   Prefix           Bytes Label   Outgoing   Next Hop    
Label      Label      or Tunnel Id     Switched      interface              
33         Pop Label  10.0.0.3/32    0             Vl113      172.16.0.117

 

 but I expected to see at least the VC ID label to be imposed...


Running 12.2(33)SXI5 on both. Am I missing something?

 

 

3 Replies 3

bhnegi
Cisco Employee
Cisco Employee

Hi Dave,

 

Can you please upload the output of "show module" from 6500-E?

Also please go through link below.

http://www.cisco.com/c/en/us/products/collateral/data-center-virtualization/data-center-interconnect/white_paper_c11_493718.html#wp9000250

 

Best Regards,

Bheem

Thank you for the info  and prompt response Bheem

I don't have a SUP2T, nor do I have SIPs or ES+:

 

#sh module 
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
  1   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     <snip>
  5    2  Supervisor Engine 720 (Active)         WS-SUP720-3B       <snip>

Mod MAC addresses                       Hw    Fw           Sw           Status
--- ---------------------------------- ------ ------------ ------------ -------
  1  <snip>                             2.5   12.2(14r)S5  12.2(33)SXI5 Ok
  5  <snip>                             5.2   8.4(2)       12.2(33)SXI5 Ok

Mod  Sub-Module                  Model              Serial       Hw     Status 
---- --------------------------- ------------------ ----------- ------- -------
  1  Centralized Forwarding Card WS-F6700-CFC       <snip>       2.1    Ok
  5  Policy Feature Card 3       WS-F6K-PFC3B       <snip>       2.3    Ok
  5  MSFC3 Daughterboard         WS-SUP720          <snip>       2.5    Ok

Mod  Online Diag Status 
---- -------------------
  1  Pass
  5  Minor Error

 

So I guess that means hardware incompatibility.

Are there any suggestions to achieve extending the vlan by some means (other than dot1Q) that this hardware would support? GRE perhaps?

bhnegi
Cisco Employee
Cisco Employee

Yes, vpls is supported when we have core facing line cards as SIP or ES+. You can use port/vlan based xconnect to extend the vlans and it doesn't require those WAN cards.

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/pfc3mpls.html#wp1109041
 

Best Regards,

Bheem