I am having an issue getting a VPLS up using an ME3600x with 15.3(2) and BGP signalling. @yelfathi and @packettalk have pointed me down the correct route but not sure how to resolve it.

I have 2 ME3600 switches using RSVP as PE and 2 MX80 routers as P.

The P routers show the LSP's as transit LSP correctly and my TE tunnels are up. On both switches I get the following:-

SW1.THN-LON#show mpls L2transport vc 501 detail
Local interface: VFI FLVPLS001 vfi up
Interworking type is Ethernet
Destination address:, VC ID: 501, VC status: down
Last error: MPLS dataplane reported a fault to the nexthop
Output interface: none, imposed label stack {}
Preferred path: not configured
Default path: no route
No adjacency
Create time: 00:19:42, last status change time: 00:19:42
Last label FSM state change time: 00:19:42
Signaling protocol: BGP
Status TLV support (local/remote)   : Not Applicable
  LDP route watch                   : Not Applicable
  Label/status state machine        : activating, LruRruD
  Last local dataplane   status rcvd: DOWN(pw-tx-fault)
  Last BFD dataplane     status rcvd: Not Applicable
  Last BFD peer monitor  status rcvd: Not Applicable
  Last local AC  circuit status rcvd: No fault
  Last local AC  circuit status sent: DOWN(pw-rx-fault)
  Last local PW i/f circ status rcvd: No fault
  Last local LDP TLV     status sent: Not Applicable
  Last remote LDP TLV    status rcvd: Not Applicable
  Last remote LDP ADJ    status rcvd: Not Applicable
MPLS VC labels: local 27, remote 16
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Control Word: Off
SSM segment/switch IDs: 0/10075 (used), PWID: 12
VC statistics:
transit packet totals: receive 0, send 0
transit byte totals:   receive 0, send 0
transit packet drops:  receive 0, seq error 0, send 0

SW1.THN-LON#show mpls for detail
Local      Outgoing   Prefix           Bytes Label   Outgoing   Next Hop  
Label      Label      or Tunnel Id     Switched      interface            
None       304720   0             Tu0        point2point
MAC/Encaps=14/18, MRU=9000, Label Stack{304720}, via Te0/2
A8D0E55DEB3D88F077938CDB8847 4A650000

The pseudo wires are up but still the VC is down.

When doing the following command it comms back saying no FEC mapping.

SW1.THN-LON#ping mpls ipv4 
Sending 5, 100-byte MPLS Echos to Target FEC Stack TLV descriptor, 
 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,
'l' - Label switched with FEC change, 'd' - see DDMAP for return code,
'X' - unknown return code, 'x' - return code 0

Type escape sequence to abort.
Success rate is 0 percent (0/5)
Total Time Elapsed 48 ms

Config for the switch re relevant parts as follows:-

interface Tunnel0
 description sw1.thn-lon-to-sw1.sco-edi
 ip unnumbered Loopback0
 tunnel mode mpls traffic-eng
 tunnel destination
 tunnel mpls traffic-eng autoroute announce
 tunnel mpls traffic-eng priority 1 1
 tunnel mpls traffic-eng path-option 1 dynamic

mpls traffic-eng tunnels
l2vpn vfi context FLVPLS001 
 vpn id 501
 autodiscovery bgp signaling bgp 
  ve id 1
  rd 56595:501
  route-target export 56595:501
  route-target import 56595:501

bridge-domain 501 
 member GigabitEthernet0/1 service-instance 2

interface GigabitEthernet0/1
 description customer xxx
 switchport trunk allowed vlan none
 switchport mode trunk
 mtu 1600
 speed 100
 duplex full
 service instance 1 ethernet
  description Cust: xxx
  encapsulation dot1q 400
  rewrite ingress tag pop 1 symmetric
 service instance 2 ethernet
  description Oil and Gas VPLS
  encapsulation dot1q 501
  rewrite ingress tag pop 1 symmetric

interface Vlan501
 no ip address
 member vfi FLVPLS001

Any help/commands etc greatly appreciated

router bgp 56595  
 bgp log-neighbor-changes  
 bgp graceful-restart restart-time 120  
 bgp graceful-restart stalepath-time 360  
 bgp graceful-restart  
 neighbor remote-as 56595  
 neighbor update-source Loopback0  
 address-family l2vpn vpls  
  neighbor activate  
  neighbor send-community extended  
  neighbor suppress-signaling-protocol ldp  

I have added ospf config for completeness.

router ospf 1
 redistribute connected subnets
 redistribute static subnets
 network area
 mpls traffic-eng router-id Loopback0
 mpls traffic-eng area

some events from debug atom events

*Jun  8 05:31:57.748: AToM[, 501]: Evt dataplane reactivateS, in activating
*Jun  8 05:31:57.748: AToM[, 501]: . Activate dataplane
*Jun  8 05:31:57.748: AToM[, 501]: . Need to setup the dataplane
*Jun  8 05:31:57.748: AToM[, 501]: . Setup dataplane, PWID 21
*Jun  8 05:31:57.748: AToM[, 501]: .. Provision SSM with PWID 21, VC ID 501, Block ID 3
*Jun  8 05:31:57.748: AToM[, 501]: .. Set imp flags: ra
*Jun  8 05:31:57.748: AToM[, 501]: ..              : nsf
*Jun  8 05:31:57.748: AToM[, 501]: .. No signal context found, defaulting to single segment PW
*Jun  8 05:31:57.748: AToM[, 501]: .. Provision SSM with 7540/20332 (sw/seg)
*Jun  8 05:31:57.748: AToM[, 501]: Receive SSM dataplane unavailable notification
*Jun  8 05:31:57.748: AToM[, 501]: Evt dataplane downS, in activating
*Jun  8 05:31:57.748: AToM[, 501]: . Dataplane unavailable
*Jun  8 05:31:57.748: AToM[, 501]: . Set last error: MPLS dataplane reported a fault to the nexthop
*Jun  8 05:31:57.748: AToM[, 501]: . Notify dataplane down
*Jun  8 05:31:57.748: AToM[, 501]: Deactivating data plane
*Jun  8 05:31:57.748: AToM[, 501]: Notify dataplane down
*Jun  8 05:31:57.748: AToM[, 501]: Unprovision and deallocate SSM segment
*Jun  8 05:31:57.748: AToM[, 501]: Added vc to 60 sec retry queue
*Jun  8 05:31:57.748: AToM[, 501]: Event provision retry already in retry queue

Output of bgp

SW1.THN-LON#show bgp l2vpn vpls all
BGP table version is 17, local router ID is
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, 
          r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter, 
          x best-external, a additional-path, c RIB-compressed, 
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found

 Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 56595:501
 *>  56595:501:VEID-1:Blk-1/136
                                     32768 ?
 *>i 56595:501:VEID-2:Blk-1/136
                       0    100      0 ?

after some help from @ytti we have narrowed it to a bug within the me3600 regarding BGP signalling.

We changed signalling to be LDP and it worked fine. Will post an update once resolved with Cisco.

  • nvm, I missed the fact that the LSPs are up
    – user661
    Jun 7, 2013 at 19:17
  • sorry. not sure how to sort the formatting
    – NetDonkey
    Jun 7, 2013 at 21:24
  • bgp config now added to OP
    – NetDonkey
    Jun 7, 2013 at 21:36
  • 1
    stackexchange seems not perfect for this type of problem. But it seems like ME3600 thinks there is problem in your IGP label (i.e. RSVP tunnels). Maybe 'sh ip cef detail' would help (follow the label hop-by-hop and post output for both direction). Also maybe try to reduce problem domain, by trying IGP labels on 'LDP' first (keep VPLS in BGP). Another thing you could try, is to configure L3 MPLS VPN on loopbacks of the ME3600, to see if there also is a problem. I'd like to look at the BGP NLRI as well, although they probably are fine as you have VPN labels.
    – ytti
    Jun 8, 2013 at 8:38
  • Hi Ytti. There are 2 intermediate MX80's. Will have a look at those too.
    – NetDonkey
    Jun 8, 2013 at 10:11

3 Answers 3


Revising answer/consolidating comments and taking another stab (disclaimer: my MPLS/VPLS experience is not on the Cisco platform). Trying to infer how your topology looks:


You said you were running OSPF between all of these. Have you double checked that you have a full mesh of LSP's between your devices? (this is a requirement for vanilla VPLS). Have you configured mpls traffic-eng area x and mpls traffic-eng router-id Loopback0 within router ospf on the ME3600's?

I'm assuming that Tunnel0 is actually representative of an LSP (I know the term "Pseudowire" has been thrown around in this question, but to me Pseudowire = L2VPN/EoMPLS/VLL). LSP's are only unidirectional, so it's possible that because of a lack of a full mesh of LSP's, the ME3600's can see the other's loopbacks in the routing table, the P routers may be interfering with the RSVP signaling/dropping things on the floor.

  • Will give that a bash. as its me3600 to me3600 i dont think it will make a diff as its more for interop to other non cisco devices
    – NetDonkey
    Jun 7, 2013 at 21:47
  • Tried and doesnt make a diff. VC still down
    – NetDonkey
    Jun 7, 2013 at 21:50
  • It is. Do i need l2vpn vpls sessions with those also?
    – NetDonkey
    Jun 7, 2013 at 21:55
  • Fair point :-D Do i need l2vpn vpls AF bgp sessions to the MX80's? I thought they wouldnt as they would only be switching labels?
    – NetDonkey
    Jun 7, 2013 at 22:00
  • Ospf between them all. PW's are up and CFO is up. Just no VC :-(
    – NetDonkey
    Jun 7, 2013 at 22:52

Seems a forwarding-plane problem somewhere on the way down to the egress switch. What's the ouput of: ping mpls ipv4 verbose?

  • Hi Marco,SW1.THN-LON#ping mpls ipv4 verbose Type escape sequence to abort. F size 100, reply addr, return code 4 F size 100, reply addr, return code 4 F size 100, reply addr, return code 4 F size 100, reply addr, return code 4 F size 100, reply addr, return code 4 Success rate is 0 percent (0/5) Total Time Elapsed 52 ms
    – NetDonkey
    Jun 7, 2013 at 19:55
  • Apologies. They all came back with F meaning no FEC mapping
    – NetDonkey
    Jun 7, 2013 at 20:02
  • I would check the MPLS forwarding table at the router. Something is broken there Is that your MX80? Jun 8, 2013 at 7:50
  • Hi Marco, that is an mx80
    – NetDonkey
    Jun 8, 2013 at 10:02
  • If anyone fancies a teamviewer session to have a look, I will pay them in beers :)
    – NetDonkey
    Jun 8, 2013 at 10:28

Found a post on c-nsp that suggests that an MTU mismatch (either global or on the interface) could be responsible: http://www.gossamer-threads.com/lists/cisco/nsp/98769#98769 Another thing worth checking is that both PE routers have each other's loopback addresses in their routing tables (as /32).

  • Hi Aziraphale Each switch can see the others loopback via the TE tunnel. MTU is fine. Access ports have 1600. Uplinks have 9000.
    – NetDonkey
    Jun 7, 2013 at 20:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.