EoMPLS Xconnect between 2811XM and 7606 with RSP720

Unanswered Question

We have an urgent need to quickly deploy an MPLS capable router to carry l2 traffic. We use mpls xconnects throughout our network. I am having difficulty establishing an xconnect between a 2811XM ISR and a 7606. OSPF and BGP are up, MPLS establishes, but cannot get the tunnel to come up. Any ideas? Is 2811 even capable of MPLS xconnects?

Thanks in advance,

Scott.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3.5 (2 ratings)
Loading.

Thanks for the quick response, I have included the show ver, and the command you asked for. Please let me know if there is anything esle that might help. Thanks.

Cisco IOS Software, 2800 Software (C2800NM-ADVIPSERVICESK9-M), Version 12.4(24)T, REL

EASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2009 by Cisco Systems, Inc.

Compiled Wed 25-Feb-09 17:55 by prod_rel_team

ROM: System Bootstrap, Version 12.4(1r) [hqluong 1r], RELEASE SOFTWARE (fc1)

ERIN-ppt2801s1 uptime is 9 hours, 6 minutes

System returned to ROM by power-on

System image file is "flash:c2800nm-advipservicesk9-mz.124-24.T.bin"

2811 mpls vc detail:

Local interface: Fa0/1.1601 up, line protocol up, Eth VLAN 1601 up

Destination address: 1.0.16.1, VC ID: 1601, VC status: down

Output interface: none, imposed label stack {}

Preferred path: not configured

Default path: no route

No adjacency

Create time: 06:52:06, last status change time: 06:52:02

Signaling protocol: LDP, peer 1.0.16.1:0 up

MPLS VC labels: local 83, remote 188

Group ID: local 0, remote 0

MTU: local 1500, remote 1500

Remote interface description: g1/47.1602 ERIN COT2

Sequencing: receive disabled, send disabled

VC statistics:

packet totals: receive 0, send 0

byte totals: receive 0, send 0

packet drops: receive 0, seq error 0, send 0

7606 mpls vc detail:

Local interface: Gi1/47.1601 up, line protocol up, Eth VLAN 1601 up

Destination address: 1.0.16.70, VC ID: 1601, VC status: down

Output interface: none, imposed label stack {}

Preferred path: not configured

Default path: no route

No adjacency

Create time: 07:32:23, last status change time: 06:52:55

Signaling protocol: LDP, peer 1.0.16.70:0 up

Targeted Hello: 1.0.16.1(LDP Id) -> 1.0.16.70

Status TLV support (local/remote) : enabled/not supported

Label/status state machine : activating, LruRruD

Last local dataplane status rcvd: DOWN(PW-tx-fault)

Last local SSS circuit status rcvd: no fault

Last local SSS circuit status sent: DOWN(PW-rx-fault)

Last local LDP TLV status sent: DOWN(PW-tx-fault)

Last remote LDP TLV status rcvd: not sent

MPLS VC labels: local 188, remote 83

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, seq error 0, send 0

Giuseppe Larosa Sat, 06/20/2009 - 03:46

Hello Scott,

I've noticed

>> Preferred path: not configured

Default path: no route

No adjacency

Are the two LDP router-ids advertised in the IGP ?

This happens on both sides.

You need to be able to perform an extended ping with SA = local router-id DA= remote LDP router-id in order to have the VC to comes up.

You actually need specific routes for these ip addresses that have typically /32 mask.

Check also that there are the MPLS paths on both directions with

sh mpls forwarding remote-LDP-router-id because the VC label is carried in a label stack in inner position.

Hope to help

Giuseppe

Harold Ritter Sat, 06/20/2009 - 05:29

Scott,

I think the issue comes from the fact that you configured the xconnect statement under the SVI interface on the 2811. Can you try to use a dot1q subinterface just as you do on the 7600.

Also, as suggested by Giuseppe, make sure that the neighbor id used on the xconnect is equal to the LDP router ID and that it is advertised as a /32 in the IGP.

Regards

I actually configured the interface as a dot1q on the 2811. The neighbor ID's for all our MPLS nodes use /32 loopback IP's, they are showing as the LDP id also. I hopefully should have some more time to look at this later, I will try to gather some more info to post.

Thanks for all the help, its flustering when you cant figure out why something that is suppose to work, wont.

sounmukh Tue, 03/22/2011 - 23:56

Just curious. I am facing the same issue. Was the PW over a Tunnel interface?

If I shut down the Tunnel, the PW comes up. Something to do with MPLS Forwarding as extended Ping doesnt go through.

BALA_3800X#show mpls l2transport vc detail

Local interface: Vl110 up, line protocol up, Eth VLAN 110 up

  Interworking type is Ethernet

  Destination address: 3.3.3.3, VC ID: 110, VC status: down

    Output interface: none, imposed label stack {}

    Preferred path: not configured 

    Default path: no route

    No adjacency

  Create time: 00:20:38, last status change time: 00:00:50

  Signaling protocol: LDP, peer 3.3.3.3:0 up

    Targeted Hello: 100.100.100.100(LDP Id) -> 3.3.3.3

    Status TLV support (local/remote)   : enabled/not supported

      Label/status state machine        : activating, LruRruD

      Last local dataplane   status rcvd: DOWN(PW-tx-fault)

      Last local SSS circuit status rcvd: no fault

      Last local SSS circuit status sent: DOWN(PW-rx-fault)

      Last local  LDP TLV    status sent: DOWN(PW-tx-fault)

      Last remote LDP TLV    status rcvd: not sent

    MPLS VC labels: local 16, remote 28

    Group ID: local 0, remote 0

    MTU: local 1500, remote 1500

    Remote interface description:

  Sequencing: receive disabled, send disabled

  VC statistics:

    packet totals: receive 3, send 0

    byte totals:   receive 275, send 0

    packet drops:  receive 0, send 0

Actions

This Discussion