Thread: [mpls-linux-general] Problems with LDP
Status: Beta
Brought to you by:
jleu
From: Alexander S. <sa...@cc...> - 2002-05-02 15:46:33
|
Hi I use mpls-linux-1.0 and ldp-portable-0.060 I have two hosts connected to the same subnetwork which make use of LDP. = After I issue > add global ... > add interface ... commands the exchange of labels occur (I can see it with network = analyzer) but one of the hosts do not ALWAYS build LSP properly. So, = from host A to host B all packets come with labels, but in the opposite = direction they come without them. ldp_linux on the host A outputs FEC: .... and on the host B it outputs index: .... Explicit > add route ... command on host B helps but sometimes ldp_linux crashes. By the way, what do the following messages mean which I use to see in = ldp_linux output ?=20 PRT: ldp_state_recv_init: cannot find adj PRT: Gratuitous search !! Another problem is the following. Suppose I have only one network = interface (eth0). If I issue the following command > add interface eth4 the ldp_linux will report an error but somehow add this interface (it is = possible to check it with show interfaces). If I issue then > del interface appropriate_number the ldp_linux will crash Quite often the whole system crashes when I exit from ldp_linux.=20 Sincerely, Sayenko Alex |
From: priya S. <mpl...@ya...> - 2004-03-23 18:19:10
|
haii I have this problem with lsp setup. I have a simple network setup as shown below. ---- LSR1 ---- | | Host1 --- LER1 LER2--- Host2 | | ---- LSR2 ---- I have a IP to FEC binding in LER2 and the routing table and mpls_out contents are as below (which is fine and as expected) root@localhost LER2]# ip route sh 10.0.4.0/24 dev eth1 scope link 10.0.1.0/24 via 10.0.3.1 dev eth2 lsp 0x3 proto zebra metric 20 equalize 10.0.3.0/24 dev eth2 scope link 10.0.12.0/24 dev eth0 scope link 127.0.0.0/8 dev lo scope link [root@localhost LER2]# cat /proc/net/mpls_out 0x00000003 68500/5753838/0 2 PUSH(gen 10002) SET(eth2,10.0.3.1) 0x00000004 447/36612/0 1 PUSH(gen 10005) SET(eth2,10.0.3.1) 0x00000008 15/738/0 1 PUSH(gen 10020) SET(eth2,10.0.3.1) BUT, I donot have a similar IP--FEC binding at LER1. The ip route show and the cat /proc/net/mpls_out commands show the following output (which packets take which LSPs-- 0x1a or 0x1b in mpls_out below) [root@localhost LER1]# ip route sh 10.0.4.0/24 via 10.0.2.2 dev eth2 proto zebra metric 20 equalize 10.0.1.0/24 dev eth1 scope link 10.0.2.0/24 dev eth2 scope link 10.0.3.0/24 via 10.0.1.2 dev eth1 proto zebra metric 20 equalize 10.0.12.0/24 via 10.0.1.2 dev eth1 proto zebra metric 30 equalize 10.0.11.0/24 dev eth0 scope link 127.0.0.0/8 dev lo scope link [root@localhost LER1]# cat /proc/net/mpls_out 0x0000001a 2845/238980/0 2 PUSH(gen 10109) SET(eth1,10.0.1.2) 0x0000001b 0/0/0 1 PUSH(gen 10111) SET(eth1,10.0.1.2) What could be the problem? The FEC binding at LER2 was automatic but not at the LER1. I just enabled the interfaces for LER1, LSR1 , LSR2, LER2 on the mpls network using "mpls ldp". Also please let me know if there is any documentation that could explain as to how the ldp for mpls-linux sets up labels for all the networks in the LSRs and LERs. Thanks in advance Praveen Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. |
From: James R. L. <jl...@mi...> - 2004-03-23 18:54:31
|
There are a couple of problems with your setup: -ECMP - the LDP RFC say that ECMP is not specified, and is up to each implementation as to how to deal with it, my implementation chooses not to deal with it and thus will not work right in the presence of ECMP -there are many bug in the version of ldp-portable you are using. I have a lot of fixes in my development tree, but I have not released them yet. On Tue, Mar 23, 2004 at 10:19:03AM -0800, priya Srinivasan wrote: > haii > > I have this problem with lsp setup. I have a > simple network setup as shown below. > > ---- LSR1 ---- > | | > Host1 --- LER1 LER2--- Host2 > | | > ---- LSR2 ---- > > I have a IP to FEC binding in LER2 and the routing > table and mpls_out contents are as below (which is > fine and as expected) > > root@localhost LER2]# ip route sh > 10.0.4.0/24 dev eth1 scope link > 10.0.1.0/24 via 10.0.3.1 dev eth2 lsp 0x3 proto zebra > metric 20 equalize > 10.0.3.0/24 dev eth2 scope link > 10.0.12.0/24 dev eth0 scope link > 127.0.0.0/8 dev lo scope link > > [root@localhost LER2]# cat /proc/net/mpls_out > 0x00000003 68500/5753838/0 2 PUSH(gen 10002) > SET(eth2,10.0.3.1) > 0x00000004 447/36612/0 1 PUSH(gen 10005) > SET(eth2,10.0.3.1) > 0x00000008 15/738/0 1 PUSH(gen 10020) > SET(eth2,10.0.3.1) > > BUT, I donot have a similar IP--FEC binding at LER1. > The ip route show and the cat /proc/net/mpls_out > commands show the following output (which packets take > which LSPs-- 0x1a or 0x1b in mpls_out below) > > [root@localhost LER1]# ip route sh > 10.0.4.0/24 via 10.0.2.2 dev eth2 proto zebra metric > 20 equalize > 10.0.1.0/24 dev eth1 scope link > 10.0.2.0/24 dev eth2 scope link > 10.0.3.0/24 via 10.0.1.2 dev eth1 proto zebra metric > 20 equalize > 10.0.12.0/24 via 10.0.1.2 dev eth1 proto zebra > metric 30 equalize > 10.0.11.0/24 dev eth0 scope link > 127.0.0.0/8 dev lo scope link > > [root@localhost LER1]# cat /proc/net/mpls_out > 0x0000001a 2845/238980/0 2 PUSH(gen 10109) > SET(eth1,10.0.1.2) > 0x0000001b 0/0/0 1 PUSH(gen 10111) SET(eth1,10.0.1.2) > > > What could be the problem? The FEC binding at LER2 was > automatic but not at the LER1. I just enabled the > interfaces for LER1, LSR1 , LSR2, LER2 on the mpls > network using "mpls ldp". > Also please let me know if there is any > documentation that could explain as to how the ldp for > mpls-linux sets up labels for all the networks in the > LSRs and LERs. > Thanks in advance > Praveen > > > > Do you Yahoo!? > Yahoo! Finance Tax Center - File online. File on time. -- James R. Leu jl...@mi... |
From: James R. L. <jl...@mi...> - 2002-05-15 02:59:29
|
Hello On Thu, May 02, 2002 at 06:48:59PM +0300, Alexander Sayenko wrote: > Hi > > I use mpls-linux-1.0 and ldp-portable-0.060 > > I have two hosts connected to the same subnetwork which make use of LDP. After I issue > > add global ... > > add interface ... > commands the exchange of labels occur (I can see it with network analyzer) but one of the hosts do not ALWAYS build LSP properly. So, from host A to host B all packets come with labels, but in the opposite direction they come without them. > There is a know issue with un-even label distribution. I'm working on this problem. Jim > ldp_linux on the host A outputs > FEC: .... > and on the host B it outputs > index: .... > > Explicit > > add route ... > command on host B helps but sometimes ldp_linux crashes. > > By the way, what do the following messages mean which I use to see in ldp_linux output ? > > PRT: ldp_state_recv_init: cannot find adj > PRT: Gratuitous search !! > > Another problem is the following. Suppose I have only one network interface (eth0). If I issue the following command > > add interface eth4 > the ldp_linux will report an error but somehow add this interface (it is possible to check it with show interfaces). If I issue then > > del interface appropriate_number > the ldp_linux will crash > > Quite often the whole system crashes when I exit from ldp_linux. > > Sincerely, > Sayenko Alex -- James R. Leu |