Thread: Re: [mpls-linux-devel] QUAGGA 99.6 + LDP-Portable
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-devel
|
From: <gsr...@al...> - 2007-01-12 16:38:00
|
Hi James, thanks for your answer.
[root@PE2 ~]# rpm -qa | grep mpls | sort
glibc-kernheaders-3.0-5.2_mpls0.1162999872
iproute-2.6.11-1_mpls_90.1162552079
iptables-1.3.0-2_mpls_1.950d
kernel-2.6.15-1.1831_FC4mpls_1.950
kernel-devel-2.6.15-1.1831_FC4mpls_1.950
quagga-0.99.6-2007010801_mpls_0.1168246002
quagga-contrib-0.99.6-2007010801_mpls_0.1168246002
quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002
quagga-devel-0.99.6-2007010801_mpls_0.1168246002
I tried what you told me in this scenario:=20
12.0.0.1 .1 10.0.0.0/24 .2 11.0.0.1
--------------PE1---------------------PE2--------------
eth1 | eth0 eth1 | eth0
| |
dummy0 (17.1) dummy0 (15.1)=09
These are all the configuration parameters I type in by vtysh (on PE2):
!
hostname PE2
!
service integrated-vtysh-config
!
debug zebra events
debug zebra kernel
!
password root
!
interface dummy0
ip address 15.0.0.1/32
ipv6 nd suppress-ra
!
interface eth0
ip address 11.0.0.1/32
ipv6 nd suppress-ra
!
interface eth1
ip address 10.0.0.2/32
ipv6 nd suppress-ra
mpls ip
mpls labelspace 0
!
interface lo
!
interface sit0
ipv6 nd suppress-ra
!
mpls ldp
egress connected
!
router ospf
passive-interface dummy
network 10.0.0.0/24 area 0.0.0.0
network 11.0.0.0/24 area 0.0.0.0
network 15.0.0.0/24 area 0.0.0.0
!
ip forwarding
!
line vty
!
And these are the outputs related to mpls and ldp:
PE2# sh mpls for
Insegments:
Lbl Spc Label Owner
0 10004 ldp
0 10005 ldp
0 10006 ldp
0 10007 ldp
Total 4
Outsegments:
Interface Label Next Hop Owner
eth1 10003 10.0.0.1 ldp
Total 1
Cross Connects:
Total 0
PE2# sh mpls for
Insegments:
Lbl Spc Label Owner
0 10004 ldp
0 10005 ldp
0 10006 ldp
0 10007 ldp
Total 4
Outsegments:
Interface Label Next Hop Owner
eth1 10003 10.0.0.1 ldp
Total 1
Cross Connects:
Total 0
PE2# sh ip route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
I - ISIS, B - BGP, > - selected route, * - FIB route
K>* 0.0.0.0/0 via 172.29.16.1, eth0
O 10.0.0.0/24 [110/10] is directly connected, eth1, 00:18:30
C>* 10.0.0.0/24 is directly connected, eth1
C>* 10.0.0.2/32 is directly connected, eth1
O 11.0.0.1/32 [110/10] is directly connected, eth0, 00:18:20
C>* 11.0.0.1/32 is directly connected, eth0
O>* 12.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:12:07
C>* 127.0.0.0/8 is directly connected, lo
K>* 169.254.0.0/16 is directly connected, eth1
C>* 172.29.16.0/22 is directly connected, eth0
PE2# sh ldp
LSR-ID: 11.0.0.1 Admin State: ENABLED
Transport Address: 0.0.0.0
Control Mode: ORDERED Repair Mode: GLOBAL
Propogate Release: TRUE Label Merge: TRUE
Retention Mode: LIBERAL Loop Detection Mode: NONE
TTL-less-domain: FALSE
Local TCP Port: 646 Local UDP Port: 646
Keep-alive Time: 45 Keep-alive Interval: 15
Hello Time: 15 Hello Interval: 5
PE2# sh ldp add
Addr: 1 ac1d113c
0
0
1
Addr: 2 0b000001
0
0
1
Addr: 3 0a000002
0
0
2
Addr: 4 ac1d1001
0
1
0
Addr: 5 0a000001
2
7
0
Addr: 8 0c000001
2
0
0
Addr: 9 0d000001
2
0
161461200
PE2# sh ldp neig
Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 11.0.0.1:0
TCP connection: 10.0.0.2.33193 - 10.0.0.1.646
State: OPERATIONAL; Msgs sent/recv: 17/43; UNSOLICITED
Up time: 00:02:04
LDP discovery sources:
eth1
Addresses bound to peer:
10.0.0.1 12.0.0.1
PE2# sh ldp disc
Local LSR Identifier: 11.0.0.1
Interface Discovery Sources:
eth1: xmit/recv
LDP Id: 12.0.0.1:0
Targeted Discovery Sources:
No configured peers
PE2# sh ldp fec
FEC: 1 0.0.0.0/0
1 172.29.16.1 0
FEC: 2 169.254.0.0/16
2 0.0.0.0 0
FEC: 3 10.0.0.0/24
3 0.0.0.0 1
FEC: 4 10.0.0.2/32
4 0.0.0.0 1
FEC: 5 11.0.0.1/32
5 0.0.0.0 1
FEC: 6 172.29.16.0/22
6 0.0.0.0 1
FEC: 9 10.0.0.1/32
FEC: 10 12.0.0.1/32
PE2# sh ldp ses
2 1.0.0.0 45 OPERATIONAL
10.0.0.1
12.0.0.1
13.0.0.1
The problem persists. I'm not able to send labeled ICMP packets between =
ldp peers, any idea?
[root@PE2 ~]# mpls ilm
ILM entry label gen 10007 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
ILM entry label gen 10006 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
ILM entry label gen 10005 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
ILM entry label gen 10004 labelspace 0 proto ipv4
pop peek (0 bytes, 0 pkts)
[root@PE2 ~]# mpls nhlfe
NHLFE entry key 0x00000003 mtu 1496 propagate_ttl
push gen 10003 set eth1 ipv4 10.0.0.1 (0 bytes, 0 pkts)
Thanks for your time and effort,
Gonzalo.
|
|
From: James R. L. <jl...@mi...> - 2007-01-16 02:02:43
|
I've added tommy <ema...@fr...> to the CC list because he is seeing =
the
same issues as you are Gonzalo.
So it looks like configuring the interfaces via vtysh had no affect. The
last thing that differs between your setup and mine is the kernel.
I assume your using fedora. Are you using fedora 4? If so I will
try building an up-to-date FC4 kernel with the latest patches.
(tommy what kernel and distribution are you using?)
In the meantime. Lets dig into the zebra/kernel communication a little bit.
Here is the debugging I have configured:
log file /var/log/monkey2
debug zebra kernel
In addition lets try a very controlled test and see is that yields a
difference result:
- Add the above config to your LERs
- Remove all MPLS/LDP commands from the config
- Save the configs
- Stop the OSPF/LDP/zebra daemons
- Clean out all MPLS entities with the 'mpls' utility
- Restart the OSPF/LDP/zebra daemons
- Wait for OSPF to converge
- Add the MPLS/LDP config
Once LDP establishes, send me the result of the show commands, and the
relevant output from the log file you configure. (preferably different log
files for each node)
Hopefully this will help me figure out where the problem is occurring.
On Fri, Jan 12, 2007 at 05:35:03PM +0100, Sienes Rodr?guez Gonzalo wrote:
> Hi James, thanks for your answer.
>=20
> [root@PE2 ~]# rpm -qa | grep mpls | sort
> glibc-kernheaders-3.0-5.2_mpls0.1162999872
> iproute-2.6.11-1_mpls_90.1162552079
> iptables-1.3.0-2_mpls_1.950d
> kernel-2.6.15-1.1831_FC4mpls_1.950
> kernel-devel-2.6.15-1.1831_FC4mpls_1.950
> quagga-0.99.6-2007010801_mpls_0.1168246002
> quagga-contrib-0.99.6-2007010801_mpls_0.1168246002
> quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002
> quagga-devel-0.99.6-2007010801_mpls_0.1168246002
>=20
> I tried what you told me in this scenario:=20
>=20
> 12.0.0.1 .1 10.0.0.0/24 .2 11.0.0.1
> --------------PE1---------------------PE2--------------
> eth1 | eth0 eth1 | eth0
> | |
> dummy0 (17.1) dummy0 (15.1)=09
>=20
>=20
> These are all the configuration parameters I type in by vtysh (on PE2):
>=20
> !
> hostname PE2
> !
> service integrated-vtysh-config
> !
> debug zebra events
> debug zebra kernel
> !
> password root
> !
> interface dummy0
> ip address 15.0.0.1/32
> ipv6 nd suppress-ra
> !
> interface eth0
> ip address 11.0.0.1/32
> ipv6 nd suppress-ra
> !
> interface eth1
> ip address 10.0.0.2/32
> ipv6 nd suppress-ra
> mpls ip
> mpls labelspace 0
> !
> interface lo
> !
> interface sit0
> ipv6 nd suppress-ra
> !
> mpls ldp
> egress connected
> !
> router ospf
> passive-interface dummy
> network 10.0.0.0/24 area 0.0.0.0
> network 11.0.0.0/24 area 0.0.0.0
> network 15.0.0.0/24 area 0.0.0.0
> !
> ip forwarding
> !
> line vty
> !
>=20
> And these are the outputs related to mpls and ldp:
>=20
> PE2# sh mpls for
> Insegments:
> Lbl Spc Label Owner
> 0 10004 ldp
> 0 10005 ldp
> 0 10006 ldp
> 0 10007 ldp
> Total 4
>=20
> Outsegments:
> Interface Label Next Hop Owner
> eth1 10003 10.0.0.1 ldp
> Total 1
>=20
> Cross Connects:
>=20
> Total 0
>=20
> PE2# sh mpls for
> Insegments:
> Lbl Spc Label Owner
> 0 10004 ldp
> 0 10005 ldp
> 0 10006 ldp
> 0 10007 ldp
> Total 4
>=20
> Outsegments:
> Interface Label Next Hop Owner
> eth1 10003 10.0.0.1 ldp
> Total 1
>=20
> Cross Connects:
>=20
> Total 0
>=20
> PE2# sh ip route
> Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
> I - ISIS, B - BGP, > - selected route, * - FIB route
>=20
> K>* 0.0.0.0/0 via 172.29.16.1, eth0
> O 10.0.0.0/24 [110/10] is directly connected, eth1, 00:18:30
> C>* 10.0.0.0/24 is directly connected, eth1
> C>* 10.0.0.2/32 is directly connected, eth1
> O 11.0.0.1/32 [110/10] is directly connected, eth0, 00:18:20
> C>* 11.0.0.1/32 is directly connected, eth0
> O>* 12.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:12:07
> C>* 127.0.0.0/8 is directly connected, lo
> K>* 169.254.0.0/16 is directly connected, eth1
> C>* 172.29.16.0/22 is directly connected, eth0
>=20
> PE2# sh ldp
> LSR-ID: 11.0.0.1 Admin State: ENABLED
> Transport Address: 0.0.0.0
> Control Mode: ORDERED Repair Mode: GLOBAL
> Propogate Release: TRUE Label Merge: TRUE
> Retention Mode: LIBERAL Loop Detection Mode: NONE
> TTL-less-domain: FALSE
> Local TCP Port: 646 Local UDP Port: 646
> Keep-alive Time: 45 Keep-alive Interval: 15
> Hello Time: 15 Hello Interval: 5
>=20
> PE2# sh ldp add
> Addr: 1 ac1d113c
> 0
> 0
> 1
> Addr: 2 0b000001
> 0
> 0
> 1
> Addr: 3 0a000002
> 0
> 0
> 2
> Addr: 4 ac1d1001
> 0
> 1
> 0
> Addr: 5 0a000001
> 2
> 7
> 0
> Addr: 8 0c000001
> 2
> 0
> 0
> Addr: 9 0d000001
> 2
> 0
> 161461200
>=20
> PE2# sh ldp neig
> Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 11.0.0.1:0
> TCP connection: 10.0.0.2.33193 - 10.0.0.1.646
> State: OPERATIONAL; Msgs sent/recv: 17/43; UNSOLICITED
> Up time: 00:02:04
> LDP discovery sources:
> eth1
> Addresses bound to peer:
> 10.0.0.1 12.0.0.1
>=20
> PE2# sh ldp disc
>=20
> Local LSR Identifier: 11.0.0.1
>=20
> Interface Discovery Sources:
> eth1: xmit/recv
> LDP Id: 12.0.0.1:0
>=20
> Targeted Discovery Sources:
> No configured peers
>=20
> PE2# sh ldp fec
> FEC: 1 0.0.0.0/0
> 1 172.29.16.1 0
> FEC: 2 169.254.0.0/16
> 2 0.0.0.0 0
> FEC: 3 10.0.0.0/24
> 3 0.0.0.0 1
> FEC: 4 10.0.0.2/32
> 4 0.0.0.0 1
> FEC: 5 11.0.0.1/32
> 5 0.0.0.0 1
> FEC: 6 172.29.16.0/22
> 6 0.0.0.0 1
> FEC: 9 10.0.0.1/32
> FEC: 10 12.0.0.1/32
>=20
> PE2# sh ldp ses
> 2 1.0.0.0 45 OPERATIONAL
> 10.0.0.1
> 12.0.0.1
> 13.0.0.1
>=20
> The problem persists. I'm not able to send labeled ICMP packets between l=
dp peers, any idea?
>=20
> [root@PE2 ~]# mpls ilm
> ILM entry label gen 10007 labelspace 0 proto ipv4
> pop peek (0 bytes, 0 pkts)
> ILM entry label gen 10006 labelspace 0 proto ipv4
> pop peek (0 bytes, 0 pkts)
> ILM entry label gen 10005 labelspace 0 proto ipv4
> pop peek (0 bytes, 0 pkts)
> ILM entry label gen 10004 labelspace 0 proto ipv4
> pop peek (0 bytes, 0 pkts)
>=20
> [root@PE2 ~]# mpls nhlfe
> NHLFE entry key 0x00000003 mtu 1496 propagate_ttl
> push gen 10003 set eth1 ipv4 10.0.0.1 (0 bytes, 0 pkts)
>=20
> Thanks for your time and effort,
>=20
> Gonzalo.
>=20
>=20
>=20
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
--=20
James R. Leu
jl...@mi...
|
|
From: tommy <ema...@fr...> - 2007-01-16 20:32:44
|
I am using FC 4 with the 2.6.15.1 kernel from sourceforge. When I find some time I will see if I can setup the same config and try what you adviced. Regards, tommy James R. Leu wrote: > I've added tommy <ema...@fr...> to the CC list because he is seeing the > same issues as you are Gonzalo. > > So it looks like configuring the interfaces via vtysh had no affect. The > last thing that differs between your setup and mine is the kernel. > I assume your using fedora. Are you using fedora 4? If so I will > try building an up-to-date FC4 kernel with the latest patches. > (tommy what kernel and distribution are you using?) > > In the meantime. Lets dig into the zebra/kernel communication a little bit. > > Here is the debugging I have configured: > > log file /var/log/monkey2 > debug zebra kernel > > In addition lets try a very controlled test and see is that yields a > difference result: > > - Add the above config to your LERs > - Remove all MPLS/LDP commands from the config > - Save the configs > - Stop the OSPF/LDP/zebra daemons > - Clean out all MPLS entities with the 'mpls' utility > - Restart the OSPF/LDP/zebra daemons > - Wait for OSPF to converge > - Add the MPLS/LDP config > > Once LDP establishes, send me the result of the show commands, and the > relevant output from the log file you configure. (preferably different log > files for each node) > > Hopefully this will help me figure out where the problem is occurring. > > On Fri, Jan 12, 2007 at 05:35:03PM +0100, Sienes Rodr?guez Gonzalo wrote: > >> Hi James, thanks for your answer. >> >> [root@PE2 ~]# rpm -qa | grep mpls | sort >> glibc-kernheaders-3.0-5.2_mpls0.1162999872 >> iproute-2.6.11-1_mpls_90.1162552079 >> iptables-1.3.0-2_mpls_1.950d >> kernel-2.6.15-1.1831_FC4mpls_1.950 >> kernel-devel-2.6.15-1.1831_FC4mpls_1.950 >> quagga-0.99.6-2007010801_mpls_0.1168246002 >> quagga-contrib-0.99.6-2007010801_mpls_0.1168246002 >> quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002 >> quagga-devel-0.99.6-2007010801_mpls_0.1168246002 >> >> I tried what you told me in this scenario: >> >> 12.0.0.1 .1 10.0.0.0/24 .2 11.0.0.1 >> --------------PE1---------------------PE2-------------- >> eth1 | eth0 eth1 | eth0 >> | | >> dummy0 (17.1) dummy0 (15.1) >> >> >> These are all the configuration parameters I type in by vtysh (on PE2): >> >> ! >> hostname PE2 >> ! >> service integrated-vtysh-config >> ! >> debug zebra events >> debug zebra kernel >> ! >> password root >> ! >> interface dummy0 >> ip address 15.0.0.1/32 >> ipv6 nd suppress-ra >> ! >> interface eth0 >> ip address 11.0.0.1/32 >> ipv6 nd suppress-ra >> ! >> interface eth1 >> ip address 10.0.0.2/32 >> ipv6 nd suppress-ra >> mpls ip >> mpls labelspace 0 >> ! >> interface lo >> ! >> interface sit0 >> ipv6 nd suppress-ra >> ! >> mpls ldp >> egress connected >> ! >> router ospf >> passive-interface dummy >> network 10.0.0.0/24 area 0.0.0.0 >> network 11.0.0.0/24 area 0.0.0.0 >> network 15.0.0.0/24 area 0.0.0.0 >> ! >> ip forwarding >> ! >> line vty >> ! >> >> And these are the outputs related to mpls and ldp: >> >> PE2# sh mpls for >> Insegments: >> Lbl Spc Label Owner >> 0 10004 ldp >> 0 10005 ldp >> 0 10006 ldp >> 0 10007 ldp >> Total 4 >> >> Outsegments: >> Interface Label Next Hop Owner >> eth1 10003 10.0.0.1 ldp >> Total 1 >> >> Cross Connects: >> >> Total 0 >> >> PE2# sh mpls for >> Insegments: >> Lbl Spc Label Owner >> 0 10004 ldp >> 0 10005 ldp >> 0 10006 ldp >> 0 10007 ldp >> Total 4 >> >> Outsegments: >> Interface Label Next Hop Owner >> eth1 10003 10.0.0.1 ldp >> Total 1 >> >> Cross Connects: >> >> Total 0 >> >> PE2# sh ip route >> Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, >> I - ISIS, B - BGP, > - selected route, * - FIB route >> >> K>* 0.0.0.0/0 via 172.29.16.1, eth0 >> O 10.0.0.0/24 [110/10] is directly connected, eth1, 00:18:30 >> C>* 10.0.0.0/24 is directly connected, eth1 >> C>* 10.0.0.2/32 is directly connected, eth1 >> O 11.0.0.1/32 [110/10] is directly connected, eth0, 00:18:20 >> C>* 11.0.0.1/32 is directly connected, eth0 >> O>* 12.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:12:07 >> C>* 127.0.0.0/8 is directly connected, lo >> K>* 169.254.0.0/16 is directly connected, eth1 >> C>* 172.29.16.0/22 is directly connected, eth0 >> >> PE2# sh ldp >> LSR-ID: 11.0.0.1 Admin State: ENABLED >> Transport Address: 0.0.0.0 >> Control Mode: ORDERED Repair Mode: GLOBAL >> Propogate Release: TRUE Label Merge: TRUE >> Retention Mode: LIBERAL Loop Detection Mode: NONE >> TTL-less-domain: FALSE >> Local TCP Port: 646 Local UDP Port: 646 >> Keep-alive Time: 45 Keep-alive Interval: 15 >> Hello Time: 15 Hello Interval: 5 >> >> PE2# sh ldp add >> Addr: 1 ac1d113c >> 0 >> 0 >> 1 >> Addr: 2 0b000001 >> 0 >> 0 >> 1 >> Addr: 3 0a000002 >> 0 >> 0 >> 2 >> Addr: 4 ac1d1001 >> 0 >> 1 >> 0 >> Addr: 5 0a000001 >> 2 >> 7 >> 0 >> Addr: 8 0c000001 >> 2 >> 0 >> 0 >> Addr: 9 0d000001 >> 2 >> 0 >> 161461200 >> >> PE2# sh ldp neig >> Peer LDP Ident: 12.0.0.1:0; Local LDP Ident: 11.0.0.1:0 >> TCP connection: 10.0.0.2.33193 - 10.0.0.1.646 >> State: OPERATIONAL; Msgs sent/recv: 17/43; UNSOLICITED >> Up time: 00:02:04 >> LDP discovery sources: >> eth1 >> Addresses bound to peer: >> 10.0.0.1 12.0.0.1 >> >> PE2# sh ldp disc >> >> Local LSR Identifier: 11.0.0.1 >> >> Interface Discovery Sources: >> eth1: xmit/recv >> LDP Id: 12.0.0.1:0 >> >> Targeted Discovery Sources: >> No configured peers >> >> PE2# sh ldp fec >> FEC: 1 0.0.0.0/0 >> 1 172.29.16.1 0 >> FEC: 2 169.254.0.0/16 >> 2 0.0.0.0 0 >> FEC: 3 10.0.0.0/24 >> 3 0.0.0.0 1 >> FEC: 4 10.0.0.2/32 >> 4 0.0.0.0 1 >> FEC: 5 11.0.0.1/32 >> 5 0.0.0.0 1 >> FEC: 6 172.29.16.0/22 >> 6 0.0.0.0 1 >> FEC: 9 10.0.0.1/32 >> FEC: 10 12.0.0.1/32 >> >> PE2# sh ldp ses >> 2 1.0.0.0 45 OPERATIONAL >> 10.0.0.1 >> 12.0.0.1 >> 13.0.0.1 >> >> The problem persists. I'm not able to send labeled ICMP packets between ldp peers, any idea? >> >> [root@PE2 ~]# mpls ilm >> ILM entry label gen 10007 labelspace 0 proto ipv4 >> pop peek (0 bytes, 0 pkts) >> ILM entry label gen 10006 labelspace 0 proto ipv4 >> pop peek (0 bytes, 0 pkts) >> ILM entry label gen 10005 labelspace 0 proto ipv4 >> pop peek (0 bytes, 0 pkts) >> ILM entry label gen 10004 labelspace 0 proto ipv4 >> pop peek (0 bytes, 0 pkts) >> >> [root@PE2 ~]# mpls nhlfe >> NHLFE entry key 0x00000003 mtu 1496 propagate_ttl >> push gen 10003 set eth1 ipv4 10.0.0.1 (0 bytes, 0 pkts) >> >> Thanks for your time and effort, >> >> Gonzalo. >> >> >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys - and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> mpls-linux-devel mailing list >> mpl...@li... >> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel >> > > |
|
From: <gsr...@al...> - 2007-03-02 10:05:31
|
Hi James:
As you could see the enviroment is the same as yours:
[root@PE3 mpls-linux-1.955-FC4]# md5sum =
quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm2187b703d908784b2c03d836086fc607 =
quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm
[root@PE3 mpls-linux-1.955-FC4]# rpm -qa | grep quagga
quagga-0.99.6-01.fc4.mpls.1.955
[root@PE3 mpls-linux-1.955-FC4]# more /etc/fedora-release
Fedora Core release 4 (Stentz)
[root@PE3 mpls-linux-1.955-FC4]# zebra -d
[root@PE3 mpls-linux-1.955-FC4]# ospfd -d
[root@PE3 mpls-linux-1.955-FC4]# ldpd -d
[root@PE3 mpls-linux-1.955-FC4]# vtysh
Hello, this is Quagga (version 0.99.6).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
PE3# con t
PE3(config)# mpls ldp
PE3(config-ldp)# exit
PE3(config)# int eth1
PE3(config-if)# mpls ip
PE3(config-if-ldp)# end
PE3# sh ldp disc
Local LSR Identifier: 10.0.0.2
Interface Discovery Sources:
eth1: xmit
Targeted Discovery Sources:
No configured peers
PE3# con t
PE3(config)# int eth1
PE3(config-if)# mpls labelsp 0
Labelspace: 0
PE3(config-if)# end
The problem is that I'm not able to create an LDP session between to =
LSRs, while I'm trying to configure the second of them I always get an =
I/O error, then the ldpd daemon is closed.
I'm going to try it in FC5, with last RPMs from Source Forge.
Thanks for your time,
Gonzalo.
-----Mensaje original-----
De: James R. Leu [mailto:jl...@mi...]
Enviado el: jue 01/03/2007 4:24
Para: Sienes Rodr=EDguez Gonzalo
CC: mpl...@li...
Asunto: Re: [mpls-linux-devel] New MPLS-Linux code
=20
On Wed, Feb 28, 2007 at 10:56:10AM +0100, Sienes Rodr?guez Gonzalo =
wrote:
> Hi again:
>=20
> I have configured a simple scenario. And the result, is that I'm able =
to create mpls segments from vtysh. In the sender I type: ip route =
12.0.0.1 gen 222 nexthop eth1 10.0.0.1, and in the receiver: mpls static =
0 -> label-map gen 222 pop. With ping from sender to 12.1 I can see that =
the ICMP packets are labelled. Also I can see the new mpls segment =
created by mpls nhlfe show and mpls ilm show.
> So the problem must be at configuring LDP, as I told you in the =
"running config" doesn't appear mpls ip (at the required interface) or =
the general command mpls ldp.
I built a FC4 chroot environment and installed the quagga-mpls FC4 rpms
inside of it and launched zebra/ldpd/ospfd. Using vtysh I can able to
configure:
-bash-3.00# md5sum quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm=20
2187b703d908784b2c03d836086fc607 =
quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm
-bash-3.00# rpm -qa | grep quagga
quagga-0.99.6-01.fc4.mpls.1.955
-bash-3.00# more /etc/fedora-release=20
Fedora Core release 4 (Stentz)
-bash-3.00# vtysh
Hello, this is Quagga (version 0.99.6).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
koko# conf t
koko(config)# mpls ldp=20
koko(config-ldp)# exit
koko(config-ldp)# exit
koko(config-if)# mpls ip
koko(config-if-ldp)# end
koko# sho ldp discovery=20
Local LSR Identifier: 192.168.1.16
Interface Discovery Sources:
eth0: xmit
Targeted Discovery Sources:
No configured peers
koko#=20
Please verify which version of the RPM you have installed, which=20
vtysh your running and include the commands your using for starting
the processes.
Here is what I did to get it up and running after installing the RPM:
echo "hostname "`hostname -s` > /etc/quagga/zebra.conf
echo "hostname "`hostname -s` > /etc/quagga/ospfd.conf
echo "hostname "`hostname -s` > /etc/quagga/ldpd.conf
chown quagga.quagga /etc/quagga/zebra.conf /etc/quagga/ospfd.conf =
/etc/quagga/ldpd.conf
service zebra start
service ospfd start
service ldpd start
vtysh
> Thanks,
> Gonzalo
>=20
>=20
> -----Mensaje original-----
> De: James R. Leu [mailto:jl...@mi...]
> Enviado el: lun 26/02/2007 15:08
> Para: Sienes Rodr?guez Gonzalo
> CC: mpl...@li...
> Asunto: Re: [mpls-linux-devel] New MPLS-Linux code
> =20
> On Mon, Feb 26, 2007 at 11:32:15AM +0100, Sienes Rodr?guez Gonzalo =
wrote:
> > Hi James!
> >=20
> > I've installed the revised RPMs for FC4. I got kernel panic after =
rebooting the system that I solved by typing "enforcing=3D0" at =
grub.conf. I have some problems with the wheel of the mouse or the USB =
ports but in general it works right. I'm able to create MPLS static =
configurations. In this version the "mpls" module has disappeared so I =
only load "mpls4". I launch zebra, ospfd and ldpd but I make the whole =
configuration by vtysh. OSPF works well but I can't put most of the ldpd =
commands, in fact, the only one that appears with "show running-config" =
is "mpls labelspace 0" in the corresponding interface, Neither "mpls =
ldp" nor "mpls ip". Are these problems solved in FC5? If that's it I =
would like to work with FC5.
>=20
> Can you manually create MPLS segments with the 'mpls' command?
> I'll look into the issue with no ldp command in vtysh.
>=20
> > Thanks,
> >=20
> > Gonzalo.
> >=20
> > I updated the FC4 kernel RPMs. Can you please try them?
> >=20
> > On Mon, Feb 19, 2007 at 11:47:24AM +0100, Sienes Rodr?guez Gonzalo =
wrote:
> > > Hi James:
> > >=20
> > > I'm trying to install your new software for FC4 but I have some =
problems.
> > > When I try to install the kernel-2.6.18 from Source Forge for FC4 =
it makes me install lots of RPMs, most of them can be installed by "yum =
update" but I can't find the libraries libc.so.6(GLIBC_2.4) and =
libpcap.so.0.9.3 anywhere for FC4. I search for them and people talks =
about 64 architecture and I'm working with Intel(R) Pentium(R) D CPU =
3.00GHz. Could you provide them to me? Witch OS are you using? Should I =
install FC5? =20
> > >=20
> > > Thanks in advance.
> > >=20
> > > P.D.: These are the outputs I get.
> > >=20
> > > [root@PE3 mpls-linux-1.955]# rpm -ivh =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686.rpm
> > > error: Failed dependencies:
> > > mkinitrd >=3D 4.2.21-1 is needed by =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686
> > > isdn4k-utils < 3.2-32 conflicts with =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686
> > > kudzu < 1.2.5 conflicts with =
kernel-2.6.18-1.2257.fc4.mpls.1.955.i686
> > >=20
> > > [root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm
> > > error: Failed dependencies:
> > > libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386
> > >=20
> > > [root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm
> > > error: Failed dependencies:
> > > libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386
> > > libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386
> > >=20
> >=20
> >=20
> >=20
> > --=20
> > James R. Leu
> > jl...@mi...
> >=20
> >=20
> >=20
>=20
>=20
>=20
> --=20
> James R. Leu
> jl...@mi...
>=20
>=20
> =
-------------------------------------------------------------------------=
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =
share your
> opinions on IT & business topics through brief surveys-and earn cash
> =
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel
--=20
James R. Leu
jl...@mi...
|
|
From: James R. L. <jl...@mi...> - 2007-03-02 14:50:03
|
I usually see this behavior if I've forgotten to load the mpls4 module. Did you do a 'modprobe mpls4' before starting ldpd? On Fri, Mar 02, 2007 at 11:03:38AM +0100, Sienes Rodr?guez Gonzalo wrote: > Hi James: >=20 > As you could see the enviroment is the same as yours: >=20 > [root@PE3 mpls-linux-1.955-FC4]# md5sum quagga-0.99.6-01.fc4.mpls.1.955.i= 386.rpm2187b703d908784b2c03d836086fc607 quagga-0.99.6-01.fc4.mpls.1.955.i3= 86.rpm > [root@PE3 mpls-linux-1.955-FC4]# rpm -qa | grep quagga > quagga-0.99.6-01.fc4.mpls.1.955 > [root@PE3 mpls-linux-1.955-FC4]# more /etc/fedora-release > Fedora Core release 4 (Stentz) > [root@PE3 mpls-linux-1.955-FC4]# zebra -d > [root@PE3 mpls-linux-1.955-FC4]# ospfd -d > [root@PE3 mpls-linux-1.955-FC4]# ldpd -d > [root@PE3 mpls-linux-1.955-FC4]# vtysh >=20 > Hello, this is Quagga (version 0.99.6). > Copyright 1996-2005 Kunihiro Ishiguro, et al. >=20 > PE3# con t > PE3(config)# mpls ldp > PE3(config-ldp)# exit > PE3(config)# int eth1 > PE3(config-if)# mpls ip > PE3(config-if-ldp)# end >=20 > PE3# sh ldp disc >=20 > Local LSR Identifier: 10.0.0.2 >=20 > Interface Discovery Sources: > eth1: xmit >=20 > Targeted Discovery Sources: > No configured peers >=20 > PE3# con t > PE3(config)# int eth1 > PE3(config-if)# mpls labelsp 0 > Labelspace: 0 > PE3(config-if)# end >=20 > The problem is that I'm not able to create an LDP session between to LSRs= , while I'm trying to configure the second of them I always get an I/O erro= r, then the ldpd daemon is closed. >=20 > I'm going to try it in FC5, with last RPMs from Source Forge. >=20 > Thanks for your time, > Gonzalo. >=20 > -----Mensaje original----- > De: James R. Leu [mailto:jl...@mi...] > Enviado el: jue 01/03/2007 4:24 > Para: Sienes Rodr?guez Gonzalo > CC: mpl...@li... > Asunto: Re: [mpls-linux-devel] New MPLS-Linux code > =20 > On Wed, Feb 28, 2007 at 10:56:10AM +0100, Sienes Rodr?guez Gonzalo wrote: > > Hi again: > >=20 > > I have configured a simple scenario. And the result, is that I'm able t= o create mpls segments from vtysh. In the sender I type: ip route 12.0.0.1 = gen 222 nexthop eth1 10.0.0.1, and in the receiver: mpls static 0 -> label-= map gen 222 pop. With ping from sender to 12.1 I can see that the ICMP pack= ets are labelled. Also I can see the new mpls segment created by mpls nhlfe= show and mpls ilm show. > > So the problem must be at configuring LDP, as I told you in the "runnin= g config" doesn't appear mpls ip (at the required interface) or the general= command mpls ldp. >=20 > I built a FC4 chroot environment and installed the quagga-mpls FC4 rpms > inside of it and launched zebra/ldpd/ospfd. Using vtysh I can able to > configure: >=20 > -bash-3.00# md5sum quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm=20 > 2187b703d908784b2c03d836086fc607 quagga-0.99.6-01.fc4.mpls.1.955.i386.rpm > -bash-3.00# rpm -qa | grep quagga > quagga-0.99.6-01.fc4.mpls.1.955 > -bash-3.00# more /etc/fedora-release=20 > Fedora Core release 4 (Stentz) > -bash-3.00# vtysh >=20 > Hello, this is Quagga (version 0.99.6). > Copyright 1996-2005 Kunihiro Ishiguro, et al. >=20 > koko# conf t > koko(config)# mpls ldp=20 > koko(config-ldp)# exit > koko(config-ldp)# exit > koko(config-if)# mpls ip > koko(config-if-ldp)# end > koko# sho ldp discovery=20 >=20 > Local LSR Identifier: 192.168.1.16 >=20 > Interface Discovery Sources: > eth0: xmit >=20 > Targeted Discovery Sources: > No configured peers >=20 > koko#=20 >=20 > Please verify which version of the RPM you have installed, which=20 > vtysh your running and include the commands your using for starting > the processes. >=20 > Here is what I did to get it up and running after installing the RPM: >=20 > echo "hostname "`hostname -s` > /etc/quagga/zebra.conf > echo "hostname "`hostname -s` > /etc/quagga/ospfd.conf > echo "hostname "`hostname -s` > /etc/quagga/ldpd.conf > chown quagga.quagga /etc/quagga/zebra.conf /etc/quagga/ospfd.conf /etc/qu= agga/ldpd.conf > service zebra start > service ospfd start > service ldpd start > vtysh >=20 > > Thanks, > > Gonzalo > >=20 > >=20 > > -----Mensaje original----- > > De: James R. Leu [mailto:jl...@mi...] > > Enviado el: lun 26/02/2007 15:08 > > Para: Sienes Rodr?guez Gonzalo > > CC: mpl...@li... > > Asunto: Re: [mpls-linux-devel] New MPLS-Linux code > > =20 > > On Mon, Feb 26, 2007 at 11:32:15AM +0100, Sienes Rodr?guez Gonzalo wrot= e: > > > Hi James! > > >=20 > > > I've installed the revised RPMs for FC4. I got kernel panic after reb= ooting the system that I solved by typing "enforcing=3D0" at grub.conf. I h= ave some problems with the wheel of the mouse or the USB ports but in gener= al it works right. I'm able to create MPLS static configurations. In this v= ersion the "mpls" module has disappeared so I only load "mpls4". I launch z= ebra, ospfd and ldpd but I make the whole configuration by vtysh. OSPF work= s well but I can't put most of the ldpd commands, in fact, the only one tha= t appears with "show running-config" is "mpls labelspace 0" in the correspo= nding interface, Neither "mpls ldp" nor "mpls ip". Are these problems solve= d in FC5? If that's it I would like to work with FC5. > >=20 > > Can you manually create MPLS segments with the 'mpls' command? > > I'll look into the issue with no ldp command in vtysh. > >=20 > > > Thanks, > > >=20 > > > Gonzalo. > > >=20 > > > I updated the FC4 kernel RPMs. Can you please try them? > > >=20 > > > On Mon, Feb 19, 2007 at 11:47:24AM +0100, Sienes Rodr?guez Gonzalo wr= ote: > > > > Hi James: > > > >=20 > > > > I'm trying to install your new software for FC4 but I have some pro= blems. > > > > When I try to install the kernel-2.6.18 from Source Forge for FC4 i= t makes me install lots of RPMs, most of them can be installed by "yum upda= te" but I can't find the libraries libc.so.6(GLIBC_2.4) and libpcap.so.0.9.= 3 anywhere for FC4. I search for them and people talks about 64 architectur= e and I'm working with Intel(R) Pentium(R) D CPU 3.00GHz. Could you provide= them to me? Witch OS are you using? Should I install FC5? =20 > > > >=20 > > > > Thanks in advance. > > > >=20 > > > > P.D.: These are the outputs I get. > > > >=20 > > > > [root@PE3 mpls-linux-1.955]# rpm -ivh kernel-2.6.18-1.2257.fc4.mpls= .1.955.i686.rpm > > > > error: Failed dependencies: > > > > mkinitrd >=3D 4.2.21-1 is needed by kernel-2.6.18-1.2257.fc= 4.mpls.1.955.i686 > > > > isdn4k-utils < 3.2-32 conflicts with kernel-2.6.18-1.2257.f= c4.mpls.1.955.i686 > > > > kudzu < 1.2.5 conflicts with kernel-2.6.18-1.2257.fc4.mpls.= 1.955.i686 > > > >=20 > > > > [root@PE3 Requeridos]# rpm -ivh mkinitrd-4.2.21-1.i386.rpm > > > > error: Failed dependencies: > > > > libc.so.6(GLIBC_2.4) is needed by mkinitrd-4.2.21-1.i386 > > > >=20 > > > > [root@PE3 Requeridos]# rpm -ivh isdn4k-utils-3.2-32.i386.rpm > > > > error: Failed dependencies: > > > > libc.so.6(GLIBC_2.4) is needed by isdn4k-utils-3.2-32.i386 > > > > libpcap.so.0.9.3 is needed by isdn4k-utils-3.2-32.i386 > > > >=20 > > >=20 > > >=20 > > >=20 > > > --=20 > > > James R. Leu > > > jl...@mi... > > >=20 > > >=20 > > >=20 > >=20 > >=20 > >=20 > > --=20 > > James R. Leu > > jl...@mi... > >=20 > >=20 > > -----------------------------------------------------------------------= -- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share= your > > opinions on IT & business topics through brief surveys-and earn cash > > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEVDEV > > _______________________________________________ > > mpls-linux-devel mailing list > > mpl...@li... > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel >=20 > --=20 > James R. Leu > jl...@mi... >=20 >=20 > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share y= our > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > mpls-linux-devel mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel --=20 James R. Leu jl...@mi... |
×
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