VPLS Setup Problem

Unanswered Question
Feb 26th, 2008
User Badges:

Hi, I am trialling VPLS with BGP autodiscovery, using the configs supplied at http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_vpls_auto_bgp.html



Using these templates, I am still unable to pass traffic between the endpoints.

Here is some show command output:

PE1_7604#sh mpls l2transport vc 24 det

Local interface: VFI VPLS-1 VFI up

MPLS VC type is VFI, interworking type is Ethernet

Destination address:, VC ID: 24, VC status: up

Output interface: none, imposed label stack {17}

Preferred path: not configured

Default path: active

Next hop: Invalid ADDR

Create time: 00:55:10, last status change time: 00:00:29

Signaling protocol: LDP, peer up

Targeted Hello: Id) ->

MPLS VC labels: local 19, remote 17

AGI: type 1, len 8, 000A 4773 0000 0018

Local AII: type 1, len 4, 0A00 0101 (

Remote AII: type 1, len 4, 0A00 0201 (

Group ID: local n/a, remote n/a

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

PE1_7604#sh mpls forwarding-table

Local Outgoing Prefix Bytes Label Outgoing Next Hop

Label Label or VC or Tunnel Id Switched interface

17 Pop Label 0 Gi2/48

18 No Label l2ckt(25) 0 none point2point

19 No Label l2ckt(24) 0 none point2point

As you can see, my outgoing interface is "None" and my next hop is "Invalid ADDR". I suspect this is the problem, but can't fix it.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
blakeovich Thu, 03/13/2008 - 17:10
User Badges:

The uplink is not a port channel.

TAC have responded by saying that VPLS is only supported on the OSM-type interfaces?

We planed on using the uplink ports on our Sup720-3BXLs.

Harold Ritter Tue, 03/25/2008 - 06:50
User Badges:
  • Cisco Employee,


VPLS does indeed require that the core facing interface is either part of a SIP, ES or OSM card.



This Discussion