Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1467
Views
0
Helpful
7
Replies

MPLS VPLS VPN

ty.chan007
Level 1
Level 1

‎01-30-2012 08:48 PM

I am having two Cisco 6509(R01,R02) connecting back to back with MPLS LDP enabled then i try to test VPLS VPN with VLAN AC.

R01's LDP Router ID is 111.90.180.8 , R02's LDP Router ID is 111.90.180.9. I got below output:

R01#sh mpls l2transport vc

Local intf     Local circuit              Dest address    VC ID      Status   

-------------  -------------------------- --------------- ---------- ----------

VFI vpls1      VFI                        111.90.180.9    101        DOWN     

CR01-POP1#sh mpls l2transport vc detail

Local interface: VFI vpls1 VFI down

  Interworking type is Ethernet

  Destination address: 111.90.180.9, VC ID: 101, VC status: down

    Output interface: none, imposed label stack {}

    Preferred path: not configured 

    Default path: active

    No adjacency

  Create time: 00:18:50, last status change time: 00:00:05

  Signaling protocol: LDP, peer 111.90.180.9:0 up

    Targeted Hello: 111.90.180.8(LDP Id) -> 111.90.180.9

    MPLS VC labels: local 247, remote 242

    Group ID: local 0, remote 0

    MTU: local 1500, remote 1500

    Remote interface description:

  Sequencing: receive disabled, send disabled

  VC statistics:

    packet totals: receive 0, send 0

    byte totals:   receive 0, send 0

    packet drops:  receive 0, send 0

R01#

===============

R02#sh mpls l2transport vc

Local intf     Local circuit              Dest address    VC ID      Status   

-------------  -------------------------- --------------- ---------- ----------

VFI vpls1      VFI                        111.90.180.8    101        UP       

R02#sh mpls l2transport vc detail

Local interface: VFI vpls1 VFI up

  Interworking type is Ethernet

  Destination address: 111.90.180.8, VC ID: 101, 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:30:45, last status change time: 00:00:11

  Signaling protocol: LDP, peer 111.90.180.8:0 up

    Targeted Hello: 172.16.32.7(LDP Id) -> 111.90.180.8, 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 242, remote 247

    Group ID: local 0, remote 0

    MTU: local 1500, remote 1500

    Remote interface description:

  Sequencing: receive disabled, send disabled

  Control Word: On (configured: autosense)

  SSO Descriptor: 111.90.180.8/101, local label: 242

    SSM segment/switch IDs: 16642/12294 (used), PWID: 4104

  VC statistics:

    transit packet totals: receive 0, send 0

    transit byte totals:   receive 0, send 0

    transit packet drops:  receive 0, send 0

R02#

=================================

As you can see, VC 101 is up on R02 but VC101 is down on R01. If i shutdown VC101 on R01, it report down too on R02.

Am i doing something wrong?

Labels:
0 Helpful
7 Replies 7

Sergey Kozhedub
Level 1
Level 1

‎02-01-2012 03:41 AM

Hello Ty Chan,

Could this be a problem?

R01

    Targeted Hello: 111.90.180.8(LDP Id) -> 111.90.180.9

R02

    Targeted Hello: 172.16.32.7(LDP Id) -> 111.90.180.8, LDP is UP

0 Helpful

ty.chan007
Level 1
Level 1
In response to Sergey Kozhedub

‎02-01-2012 05:59 PM

Dear Sergey,

Thanks for reply.

Now LDP ID is changed to the correct one as below result:

02#sh mpls l2transport vc detail

Local interface: VFI vpls1 VFI up

  Interworking type is Ethernet

  Destination address: 111.90.180.8, VC ID: 101, 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: 1d21h, last status change time: 00:00:08

  Signaling protocol: LDP, peer 111.90.180.8:0 up

    Targeted Hello: 111.90.180.9(LDP Id) -> 111.90.180.8, 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 242, remote 232

    Group ID: local 0, remote 0

    MTU: local 1500, remote 1500

    Remote interface description:

  Sequencing: receive disabled, send disabled

  Control Word: On (configured: autosense)

  SSO Descriptor: 111.90.180.8/101, local label: 242

    SSM segment/switch IDs: 15057/12294 (used), PWID: 4104

  VC statistics:

    transit packet totals: receive 0, send 0

    transit byte totals:   receive 0, send 0

    transit packet drops:  receive 0, send 0

R02#

-------------------

R01#sh mpls l2transport vc detail

Local interface: VFI vpls1 VFI up

  Interworking type is Ethernet

  Destination address: 111.90.180.9, VC ID: 101, VC status: down

    Output interface: none, imposed label stack {}

    Preferred path: not configured 

    Default path: active

    No adjacency

  Create time: 1d21h, last status change time: 00:00:08

  Signaling protocol: LDP, peer 111.90.180.9:0 up

    Targeted Hello: 111.90.180.8(LDP Id) -> 111.90.180.9

    MPLS VC labels: local 232, remote 242

    Group ID: local 0, remote 0

    MTU: local 1500, remote 1500

    Remote interface description:

  Sequencing: receive disabled, send disabled

  VC statistics:

    packet totals: receive 0, send 0

    byte totals:   receive 0, send 0

    packet drops:  receive 0, send 0

R01#

-----------

But VC is sitll down on R01 while VC on R02 is up.

Regards, CT

0 Helpful

Sergey Kozhedub
Level 1
Level 1
In response to ty.chan007

‎02-02-2012 06:07 AM

Hi Ty Chan,

What type of Ethernet / WAN cards you're using on R1 and R2 facing to each other?

Could this be a hardware limitation?

For VPLS you have to use ES/ES+ or SIP- cards.

Sergey

0 Helpful

ty.chan007
Level 1
Level 1
In response to Sergey Kozhedub

‎02-02-2012 10:30 PM

Hi Sergey,

I am using cat6509 with

1. R02 is s3223_rp-ADVENTERPRISE_WAN-M), Version 12.2(33)SXI4, RELEASE SOFTWARE (fc3)

2. R01 is s3223_rp-ADVENTERPRISE_WAN-M), Version 12.2(33)SXI3, RELEASE SOFTWARE (fc2)

3. R01 is using WS-X6148-GE-TX 48 port 10/100/1000mb EtherModule Rev. 7.1

4. R02 is using WS-X6148A-GE-TX 48-port 10/100/1000 RJ45 EtherModule Rev. 4.1

any suggestion?

Regards, CT

0 Helpful

Sudeep Valengattil
Cisco Employee
Cisco Employee
In response to ty.chan007

‎02-02-2012 10:35 PM

Hi Ty chan,

SVI-based EoMPLS (SW-based or WAN-based EoMPLS) requires OSM/SIP/ES+ for the Core-facing interfaces. It will not work with WS-X6148-GE-TX.

Regards,

Sudeep

0 Helpful

ty.chan007
Level 1
Level 1
In response to Sudeep Valengattil

‎02-03-2012 05:19 PM

Hi Sudeep,

I using "WS-X6516A-GBIC SFM-capable 16 port 1000mb GBIC Rev. 4.7" facing core and " WS-X6148-GE-TX 48 port 10/100/1000mb EtherModule Rev. 7.2" facing to customer (CE) on both routers.

Regards, CT

0 Helpful

Kishore Chennupati
Level 7
Level 7
In response to ty.chan007

‎02-04-2012 05:56 AM

Hi ty,

If its just 2 switches why dont you just use EoMPLS? Is there a compelling reason to use VPLS.

Regards.

Kishore

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents