xconnect problem

Unanswered Question
May 16th, 2007

we are having PE-PE xconnect.There sessions are established last five weeks.But now there session is brraken up.And now we are not able to start new xconnect session between pe-pe.Can anyone provide the solution.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
shivlu jain Sun, 05/20/2007 - 06:04

i am forwarding my configuration of both PE'S.

IST PE:-

interface FastEthernet0.801

description #### CE MPLS INTERFACE ####

encapsulation dot1Q 801

no snmp trap link-status

no cdp enable

xconnect x.x.x.x 801 encapsulation l2tpv3 pw-class shivlu

end

Second PE:-

interface GigabitEthernet0/2.801

description #### VARANASI MPLS INT ####

encapsulation dot1Q 801

no cdp enable

xconnect x.x.x.x 801 encapsulation l2tpv3 pw-class shiv

end

now when i run the command at pe2 i got the output like the given

VARANASI_PGCIL#sh l2tun session

%No active L2F tunnels

L2TP Session Information Total tunnels 2 sessions 3

LocID RemID TunID Username, Intf/ State Last Chg Uniq ID

Vcid, Circuit

3610 12208 30621 246, Fa0.246:246 est 01:02:36 2

3849 0 49847 890, Fa0.890:890 wt-tnl 00:00:01 129

3851 0 49847 801, Fa0.801:801 wt-tnl 00:00:00 58

my tunnels are always in the wt-tnl state.But this session is already established for 3 weeks not it got down and not able to up again.It is happening the same way with the clients.For the solution i have to migrate the clinet to another router where is worls fine.

The remote id is always 0 at one end.As i think that my core 7200 series router is not able to generate the tunnels and not assigning the local id number.

My hardware details are given below:-

7200 here i am getting problem

2811

Harold Ritter Sun, 05/20/2007 - 08:04

It looks like the l2tpv3 packets might not be getting from one PE to the other.

Is it possible to run a "debug xconnect"

Regards,

swaroop.potdar Wed, 05/16/2007 - 12:09

Sincerly you should open a TAC case at your earliest. Since its in prodcution and a working config has stopped working.

In the meanwhile when you open the case, also check whether your end to end LSP is upon, using MPLS ping/trace.

HTH-Cheers,

Swaroop

Actions

This Discussion