Thread: [mpls-linux-general] LDP config... confused!
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-general
|
From: <sam...@ya...> - 2002-10-07 12:50:28
|
Hello James and everybody,
I've managed to set up static LSPs successfully and
have now moved over to setting up of dynamic LSPs
using ldp-portable-0.2.
For this, I'm working with a simple setup of two
hosts. Host A ==> 10.3.9.87 and Host B ==> 10.3.9.92.
I have setup and configured zebra, ospfd and mplsd on
both these machines. My config files are:
--------------zebra.conf--------------------
!
hostname zebra
password root
enable password root
!
interface eth0
ip address 10.3.9.92/0
!
log file zebra.log
--------------ospfd.conf--------------------
!
hostname ospfd
password root
enable password root
!
router ospf
network 10.3.0.0/20 area 0
!
log stdout
--------------mplsd.conf--------------------
!
hostname mplsd
password root
enable password root
!
interface eth0
mpls ldp
!
router zebra
mpls ldp
!
log file ./mplsd.log
!
line vty
!
Having done this, when I check up the command "show
ldp neighbor" after telnetting to mplsd, I can see
that it has recognized the other machine as the
neighbor and is exchanging HELLO messages.
But when, I try to run the command "show ldp
database", all I get is "no label info has been
exchanged".
I am guessing that this means that the LSPs haven't
been set up since no label info was exchanged.
Is there something wrong in my config files? ...
alternatively could you direct me as to how to ensure
that the label info is exchanged between the two
hosts.
Any help would be greatly appreciated.
Thanking in advance!
Cheers,
Sameer
________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
visit http://in.tv.yahoo.com
|
|
From: James R. L. <jl...@mi...> - 2002-10-07 13:11:30
|
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 On Mon, Oct 07, 2002 at 01:50:15PM +0100, Sameer Gharat wrote: > Hello James and everybody, > > I've managed to set up static LSPs successfully and > have now moved over to setting up of dynamic LSPs > using ldp-portable-0.2. > > For this, I'm working with a simple setup of two > hosts. Host A ==> 10.3.9.87 and Host B ==> 10.3.9.92. > I have setup and configured zebra, ospfd and mplsd on > both these machines. My config files are: > --------------zebra.conf-------------------- > ! > hostname zebra > password root > enable password root > ! > interface eth0 > ip address 10.3.9.92/0 > ! > log file zebra.log > > --------------ospfd.conf-------------------- > ! > hostname ospfd > password root > enable password root > ! > router ospf > network 10.3.0.0/20 area 0 > ! > log stdout > > --------------mplsd.conf-------------------- > ! > hostname mplsd > password root > enable password root > ! > interface eth0 > mpls ldp > ! > router zebra > mpls ldp > ! > log file ./mplsd.log > ! > line vty > ! > > Having done this, when I check up the command "show > ldp neighbor" after telnetting to mplsd, I can see > that it has recognized the other machine as the > neighbor and is exchanging HELLO messages. > But when, I try to run the command "show ldp > database", all I get is "no label info has been > exchanged". > > I am guessing that this means that the LSPs haven't > been set up since no label info was exchanged. > > Is there something wrong in my config files? ... > alternatively could you direct me as to how to ensure > that the label info is exchanged between the two > hosts. > > Any help would be greatly appreciated. > > Thanking in advance! > > Cheers, > Sameer > > ________________________________________________________________________ > 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 |
|
From: <sam...@ya...> - 2002-10-14 15:01:19
|
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
|
|
From: James R. L. <jl...@mi...> - 2002-10-14 19:49:11
|
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 |
|
From: <sam...@ya...> - 2002-10-15 17:20:25
|
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 |
|
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 |
|
From: <sam...@ya...> - 2002-10-19 08:57:18
|
Hello James,
Yup!... I did clean out all the interface addresses
and routes and made a clean start.
And after a bit of struggle, I managed to get it to
work!! ... though it did take time for me to realize
the significance of "backbone area" in ospfd. Once
that issue was ironed out, LDP started working like a
dream and exchanged labels and created dynamic LSPs
perfectly!
Thanks a ton for all the help you provided from time
to time as I hit some raodblocks along the way!!
Thanks a lot!
cheers,
Sameer
--- "James R. Leu" <jl...@mi...> wrote: >
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:
________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
visit http://in.tv.yahoo.com
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X