Re: [mpls-linux-general] LDP config... confused!
Status: Beta
                
                Brought to you by:
                
                    jleu
                    
                
            | 
      
      
      From: James R. L. <jl...@mi...> - 2002-10-18 18:15:39
      
     | 
| Make sure you clean out all interface address and routes before starting zebra/ospfd. Zebra treats interface that it provisioned and interfaces learned from the kernel differntly. I do not understand all of the ramification of this yet, but I work around it by configuring everything via zebra. On Tue, Oct 15, 2002 at 06:20:16PM +0100, Sameer Gharat wrote: > Hi James, > > nope... I have only ospfd running as the routing > protocol. the funny thing is that mplsd does create > the outlabels sometimes while sometimes it doesn't! > ... I haven't been able to pin-point the conditions > that exist when the out-labels are getting created. > Maybe I'll go through the trace output and see if I > can figure out something. > But as far as existing route entry is concerned, I > believe it would have been created by ospfd. Is that > right? > > thanks and regards, > Sameer > > --- "James R. Leu" <jl...@mi...> wrote: > Do > you have some other routing protocol running? > > LDP out labels only get > > installed for FECs that match an existing route > > entry. > > > > On Mon, Oct 14, 2002 at 04:01:00PM +0100, Sameer > > Gharat wrote: > > > Hello James and all, > > > > > > I included a dummy interface with a /32 address > > and > > > tried the procedure over again. It worked!! ... > > though > > > only partially, as it created incoming labels on > > both > > > the hosts that I was working on. But it did not > > create > > > any outgoing labels. > > > > > > Any reason, why this should happen? > > > > > > thanks in advance! > > > > > > cheers, > > > Sameer > > > > > > --- "James R. Leu" <jl...@mi...> wrote: > > > The > > > default behavior for zebra-ldp is to only > > > > distribute labels for > > > > the LSR-ID (this can be changed, but only > > > > programitically). The LSR-ID > > > > must be attached to a directly connected > > interface > > > > and must show up as > > > > a /32 in the routing table (this is probably a > > > > little too strict, I need to > > > > tweak these rules). So the easiest way is to > > use a > > > > 'dummy' interface. > > > > Compile your kernel with support for it, then > > assign > > > > a /32 to it through zebra. > > > > Configure OSPF to run passive on the dummy > > > > interface. You should then see > > > > that LDP distruibutes labels for the /32s. > > > > > > > > Jim > > > > > > > > > > > > ________________________________________________________________________ > > > Missed your favourite TV serial last night? Try > > the new, Yahoo! TV. > > > visit http://in.tv.yahoo.com > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > mpls-linux-general mailing list > > > mpl...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > > -- > > James R. Leu > > ________________________________________________________________________ > Missed your favourite TV serial last night? Try the new, Yahoo! TV. > visit http://in.tv.yahoo.com > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu |