[rbak-nsp] MPLS issue in SE800
Umar Ahmed
Umar.Ahmed at vanco.co.uk
Fri Sep 22 12:40:57 EDT 2006
ok folks a quick update to say it was fixed by running a
process restart rib
process restart lm
This restarts the rib and lable-mapper in the box - worked like a charm.
Seemed that the SE-800 was stuck in flux on the label distribution.
_____
From: redback-nsp-bounces at puck.nether.net
[mailto:redback-nsp-bounces at puck.nether.net] On Behalf Of Umar Ahmed
Sent: 21 September 2006 10:02
To: Sridhar; redback-nsp at puck.nether.net
Cc: Umar Ahmed
Subject: Re: [rbak-nsp] MPLS issue in SE800
Hello Sridhar,
The SeOs version on London is SEOS-2.6.3.2-Release and Paris is
SEOS-2.6.5.3-Release. One of my colleaguges has raised a case with TAC to
see if they can help :)
Umar.
-----Original Message-----
From: manisridhar at gmail.com [mailto:manisridhar at gmail.com
<mailto:manisridhar at gmail.com> ] On Behalf Of Sridhar
Sent: 20 September 2006 15:20
To: redback-nsp at puck.nether.net
Cc: Umar.Ahmed at vanco.co.uk
Subject: Re: [rbak-nsp] MPLS issue in SE800
hi Umar,
what versions of SEOS are you running on the two boxes?
besides the ping of rsvp lsp LONDON-PARIS which fails, is there some other
problem that you see?
thanks
sridhar
On 9/20/06, Umar Ahmed <Umar.Ahmed at vanco.co.uk> wrote:
>
>
> Hello all,
>
> I have the following setup in terms of LSP's:
>
> London - Paris
>
> Paris - London
>
> Very basic so that I can pass traffic across my 2547 network. There
> are other LSP's that are setup in the same way ingress/egress of Paris
> and London which work fine.
>
> The problem is that I can ping from Paris to London whereby London to
> Paris does not want to know (see pings below):
>
> [local]#ping mpls rsvp PARIS-LONDON
> Sending 5 100-byte MPLS echos to PARIS-LONDON, source x.x.x.3,
> timeout is 1 second, send interval is 0 msec:
> !!!!!
>
> [local]#ping mpls rsvp LONDON-PARIS
> Sending 5 100-byte MPLS echos to LONDON-PARIS, source x.x.x.2,
> timeout is 1 second, send interval is 0 msec:
> .....
>
> I have triple checked the config which is in line with other LSP's
> that work, however this is stumping me.
>
> The IGP is fine - OSPF can see the loopbacks, and MBGP is looking
> good. The VPN config is fine with the RT and RD looking good.
>
> This is the viewpoint from London for the LSP's ingress and egress
>
>
> --- RSVP LSP London-Paris (ID: 3) ---
>
> Ingress : x.x.x.2 Endpoint : x.x.x.3
> Origin : Ingress LSP State : Up
> Extended Tunnel ID : x.x.x.2 LSP ID : 0
> Trafffic-Eng : default State Transitions : 1
> Downstream Nhop : x.x.x.3 Downstream Intf : x.x.x.29
> Downstream Nbr : x.x.x.30 Downstream Label : 3
> Setup Priority : 0 Holding Priority : 0
> Last Downstream Tx : 18 Last Downstream Rx : 11
> Next Timer in (sec) : 6 Lifetime (sec) : 157
> Time to Die (sec) : 145 B/W (Bytes/sec) : 0
> LSP cct : 255/3:1023:63/0/1/1
> IGP Shortcut : Disabled
> Use Explicit Route : No Record Route : Yes
> Recorded Route (hops: 1):
> x.x.x.3/32
>
>
>
> --- RSVP LSP Paris-London (ID: 3) ---
>
> Ingress : x.x.x.3 Endpoint : x.x.x.2
> Origin : Egress LSP State : Up
> Extended Tunnel ID : x.x.x.3 LSP ID : 0
> Trafffic-Eng : None State Transitions : 0
> Setup Priority : 0 Holding Priority : 0
> Last Upstream Tx : 6 Last Upstream Rx : 8
> Upstream Intf : x.x.x.29 Upstream Nhop : x.x.x.30
> Upstream Nbr : x.x.x.30 Upstream Label : 3
> Next Timer in (sec) : 31 Lifetime (sec) : 157
> Time to Die (sec) : 148 B/W (Bytes/sec) : 0
> LSP cct : Cct invalid
>
>
>
> Paris Point of View:
>
> --- RSVP LSP London-Paris (ID: 3) ---
>
> Ingress : x.x.x.2 Endpoint : x.x.x.3
> Origin : Egress LSP State : Up
> Extended Tunnel ID : x.x.x.2 LSP ID : 0
> Trafffic-Eng : None State Transitions : 1
> Setup Priority : 0 Holding Priority : 0
> Last Upstream Tx : 7 Last Upstream Rx : 21
> Upstream Intf : x.x.x.30 Upstream Nhop : x.x.x.29
> Upstream Intf Name : mplstolonix :
> Upstream Nbr : x.x.x.29 Upstream Label : 3
> Next Timer in (sec) : 36 Lifetime (sec) : 157
> Time to Die (sec) : 135 B/W (Bytes/sec) : 0
> LSP cct : Cct invalid
>
>
>
> --- RSVP LSP Paris-London (ID: 3) ---
>
> Ingress : x.x.x.3 Endpoint : x.x.x.2
> Origin : Ingress LSP State : Up
> Extended Tunnel ID : x.x.x.3 LSP ID : 0
> Trafffic-Eng : default State Transitions : 9
> Downstream Nhop : x.x.x.2 Downstream Intf : x.x.x.30
> Downstream Intf Name: mplstolonix :
> Downstream Nbr : x.x.x.29 Downstream Label : 3
> Setup Priority : 0 Holding Priority : 0
> Last Downstream Tx : 7 Last Downstream Rx : 39
> Next Timer in (sec) : 14 Lifetime (sec) : 157
> Time to Die (sec) : 118 B/W (Bytes/sec) : 0
> LSP cct : 255/3:1023:63/0/1/1
> IGP Shortcut : Disabled
> Session Attr : Local-Protect May-Reroute Record-Label
>
> Path Error messages :
> Time: 02:27:18, Node Address: x.x.x.158, Code: No Sender Info for Resv,
> Flags: 0x0, Value: 0x0
> Time: 02:27:43, Node Address: x.x.x.29, Code: No Sender Info for Resv,
> Flags: 0x0, Value: 0x0, Repeat cnt: 2
> Time: 02:29:01, Node Address: x.x.x.158, Code: No Sender Info for Resv,
> Flags: 0x0, Value: 0x0
>
> Use Explicit Route : No Record Route : Yes
> Recorded Route (hops: 1):
> x.x.x.29/32
>
> There seems to be limited commands for troubleshooting the LSP so if
> anyone knows what else to try - please let me know. I see some path
> error messages but dont know how to decipher them - any ideas ????
>
>
> Kind regards,
>
>
>
> Umar Ahmed
>
>
>
> IST Changes Manager
>
>
>
> Vanco UK Limited, a Vanco plc Group Company
>
> John Busch House, 277 London Road, Isleworth, TW7 5AX, UK
>
> T +44 (0) 20 8636 1700
>
> F +44 (0) 20 8636 1701
>
> W <http://www.vanco.co.uk <http://www.vanco.co.uk> >
>
> DDI +44 (0) 20 8636 2957
>
> M +44 (0) 7818 242 138
>
> E umar.ahmed at vanco.co.uk
>
>
>
> **********************************************************************
> Any opinions expressed in the email are those of the individual and
> not necessarily the company. This email and any files transmitted with
> it are confidential and solely for the use of the intended recipient.
> If you are not the intended recipient or the person responsible for
> delivering it to the intended recipient, be advised that you have
> received this email in error and that any dissemination, distribution,
> copying or use is strictly prohibited.
>
> If you have received this email in error, or if you are concerned
> with the content of this email please e-mail to:
> e-security.support at vanco.info
>
> The contents of an attachment to this e-mail may contain software
> viruses which could damage your own computer system. While the sender
> has taken every reasonable precaution to minimise this risk, we cannot
> accept liability for any damage which you sustain as a result of software
viruses.
> You should carry out your own virus checks before opening any
> attachments to this e-mail.
> **********************************************************************
>
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
<https://puck.nether.net/mailman/listinfo/redback-nsp>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/redback-nsp/attachments/20060922/8f4e271c/attachment-0001.html
More information about the redback-nsp
mailing list