[j-nsp] Details of show ted output

[Harry Reynolds]

Assuming this is a non production network you might try clearing the OSPF
data base with a clear ospf database purge (not really that disruptive, but
better to be safe). Also, you might display the opaque LSAs, which support
TE extensions, to see if any routers are not correctly generating the type
10 LSAs.

I sometimes fine that disabling cspf with a no-cspf and then building a
convention RSVP LSP, perhaps using ERO constraints, is a good way to spot
general MPLS issues, like missing RSVP on family MPLS on the correct logical
unit. The benefit here is that you test baseline MPLS while eliminating
complexity of TED and CSPF.

Regards





> -----Original Message-----
> From: Bala S Venkata [mailto:balavenkata at netscape.net] 
> Sent: Thursday, July 29, 2004 8:54 AM
> To: harry at juniper.net
> Cc: jeremy at skwire.net; juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Details of show ted output
> 
> Harry-
> 
> I see that on both ends of the link the interface shows up 
> under mpls, rsvp and OSPF (my IGP) families. OSPF also has TE 
> specified. I did the following on one of the link endpoints:
> 
> ------------------------------------------------
> user at host# show protocols ospf
> traffic-engineering;
> area 0.0.0.0 {
>     interface fxp0.0 {
>         disable;
>     }
>     interface all;
> }
> 
> [edit]
> user at host# show protocols mpls
> interface so-0/1/0.0;
> interface so-0/3/0.0;
> interface so-1/2/0.0;
> interface at-0/1/0.0;
> 
> [edit]
> user at host# show protocols rsvp
> interface all;
> interface so-0/1/0.0;
> interface so-0/3/0.0;
> interface so-1/2/0.0;
> interface at-0/1/0.0;
> ------------------------------------------------
> 
> Is something missing here ?
> 
> 
> >Check to see that both ends of the link support the MPLS 
> family, RSVP, 
> >and TE extensions to the IGP. Usually when I see an 
> asymmetric number 
> >of in links vs. out links, it is one of the above causes.
> >
> >HTHs
> >
> > 
> >
> >  
> >
> >>-----Original Message-----
> >>From: juniper-nsp-bounces at puck.nether.net
> >>[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Bala S 
> >>Venkata
> >>Sent: Thursday, July 29, 2004 7:51 AM
> >>To: jeremy at skwire.net
> >>Cc: juniper-nsp at puck.nether.net
> >>Subject: Re: [j-nsp] Details of show ted output
> >>
> >>Thanks for that Jeremy. I read the docs too but I was unclear as to 
> >>why would a link used by a node pointing to "this node"
> >>be unidirectional. THat is the part for which I was looking for an 
> >>answer. Lmk if you have more ideas.
> >>
> >>
> >>TIA
> >>
> >>jeremy at skwire.net wrote:
> >>
> >>    
> >>
> >>>Bala,
> >>>
> >>>The LnkIn shows how many nodes point towards this node, and LnkOut 
> >>>shows how many nodes this node points toward.  Here is the 
> doc that 
> >>>points this out:
> >>>
> >>>http://www.juniper.net/techpubs/software/junos/junos62/swcmdr
> >>>      
> >>>
> >>ef62/html/
> >>    
> >>
> >>>mpls-monitor13.html
> >>>
> >>>J.
> >>>
> >>>On Wed, 28 Jul 2004 15:41:46 -0700
> >>>Bala S Venkata <balavenkata at netscape.net> wrote:
> >>>
> >>>BSV> HI,
> >>>BSV> 
> >>>BSV> In the output of "show ted database" what does LnkIn 
> and LnkOut 
> >>>BSV> really mean ? In the following sample, you can see 
> the LnkIn is
> >>>BSV> 3 and LnkOut is 1. I am trying to understand what it means 
> >>>BSV> (especially why it shows a mismatch).
> >>>BSV> 
> >>>BSV> ------------------------------
> >>>BSV> user at host# run show ted database 192.168.0.102 TED 
> database: 0 
> >>>BSV> ISIS nodes 6 INET nodes
> >>>BSV> ID                            Type Age(s) LnkIn 
> LnkOut Protocol
> >>>BSV> 192.168.0.102                 Rtr   59244     3      1 
> >>>      
> >>>
> >>OSPF(0.0.0.0)
> >>    
> >>
> >>>BSV> .....
> >>>BSV> ------------------------------
> >>>BSV> 
> >>>BSV> 
> >>>BSV> Thanks !
> >>>BSV> 
> >>>BSV> /bala
> >>>BSV> 
> >>>
>