Re: [mpls-linux-devel] QUAGGA 99.6 + LDP-Portable
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
Re: [mpls-linux-devel] QUAGGA 99.6 + LDP-Portable
|
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 >> > > |
