Re: [mpls-linux-devel] QUAGGA 99.6 + LDP-Portable

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Looking closer at your configs and comparing to mine, there are two
differences I notice.  First, I configure all of my routing/MPLS
interface IP addresses via vtysh. (ie the system does not configure them
via /etc/sysconfig/network-scripts/ifcfg-*)  Second, I always use
a dummy0 interface to establish my router-id/lsr-id

Here is the important parts of my config:

interface dummy0
 ip address 192.168.3.2/32
 ipv6 nd suppress-ra
!
interface eth0
 ipv6 nd suppress-ra
!
interface eth1
 ip address 192.168.2.2/30
 ipv6 nd suppress-ra
 mpls ip
 mpls labelspace 0
!
interface eth2
 ip address 192.168.4.2/29
 ipv6 nd suppress-ra
 mpls ip
 mpls labelspace 0
!
mpls ldp
 egress connected
!
router ospf
 passive-interface dummy0
 network 192.168.2.0/30 area 0.0.0.0
 network 192.168.3.2/32 area 0.0.0.0
 network 192.168.4.0/29 area 0.0.0.0

You'll notice that eth0 does not have an IP in the config.
This is the only interface I configure via the system.  This
is so that if zebra is not running I can still login to the
box.  But all other routing/MPLS/LDP interfaces are configured
via vtysh.

Give my suggestions a try and see if either fix things for you.
Please let me know the results!

On Mon, Jan 08, 2007 at 12:51:10PM +0100, Sienes Rodr?guez Gonzalo wrote:
> Hi James:
>=20
> You'll have to forgive me, I had some important business to finish before=
 christmas.
>=20
> I've downloaded the latest quagga-mpls and ldp-portable from your P4 repo=
sitory and
>=20
> test it in a simple scenario with two PCs.
>=20
> =20
>=20
> 13.0.0.1 .1 10.0.0.0/24 .2 11.0.0.1
>=20
> --------------PE1---------------------PE2--------------
>=20
> eth1 eth0 eth1 eth0
>=20
> And these are the versions of the RPMs related to MPLS and QUAGGA and the=
 modules I load:
>=20
> [root@PE2]# rpm -qa | grep mpls | sort
>=20
> glibc-kernheaders-3.0-5.2_mpls0.1162999872
>=20
> iproute-2.6.11-1_mpls_90.1162552079
>=20
> iptables-1.3.0-2_mpls_1.950d
>=20
> kernel-2.6.15-1.1831_FC4mpls_1.950
>=20
> kernel-devel-2.6.15-1.1831_FC4mpls_1.950
>=20
> quagga-0.99.6-2007010801_mpls_0.1168246002
>=20
> quagga-contrib-0.99.6-2007010801_mpls_0.1168246002
>=20
> quagga-debuginfo-0.99.6-2007010801_mpls_0.1168246002
>=20
> quagga-devel-0.99.6-2007010801_mpls_0.1168246002
>=20
> [root@PE2]# lsmod | grep mpls
>=20
> mpls4 5953 0
>=20
> mpls 78209 2 mpls4
>=20
> Now I show you the configuration and output of some commands in PE2 (anal=
ogue in PE1):
>=20
> PE2# sh run
>=20
> Building configuration...
>=20
> Current configuration:
>=20
> !
>=20
> hostname PE2
>=20
> !
>=20
> service integrated-vtysh-config
>=20
> !
>=20
> debug zebra events
>=20
> debug zebra kernel
>=20
> !
>=20
> password root
>=20
> !
>=20
> interface eth0
>=20
> description 11.0.0.1 netmask 255.255.255.0 broadcast 11.0.0.255
>=20
> ipv6 nd suppress-ra
>=20
> !
>=20
> interface eth1
>=20
> description 10.0.0.2 netmask 255.255.255.0 broadcast 10.0.0.255
>=20
> ipv6 nd suppress-ra
>=20
> mpls ip
>=20
> mpls labelspace 0
>=20
> !
>=20
> !
>=20
> mpls ldp
>=20
> egress connected
>=20
> !
>=20
> router ospf
>=20
> network 10.0.0.0/24 area 0.0.0.0
>=20
> network 11.0.0.0/24 area 0.0.0.0
>=20
> network 15.0.0.0/24 area 0.0.0.0
>=20
> !
>=20
> ip forwarding
>=20
> !
>=20
> line vty
>=20
> !
>=20
> PE2# sh ldp
>=20
> LSR-ID: 10.0.0.2 Admin State: ENABLED
>=20
> Transport Address: 0.0.0.0
>=20
> Control Mode: ORDERED Repair Mode: GLOBAL
>=20
> Propogate Release: TRUE Label Merge: TRUE
>=20
> Retention Mode: LIBERAL Loop Detection Mode: NONE
>=20
> TTL-less-domain: FALSE
>=20
> Local TCP Port: 646 Local UDP Port: 646
>=20
> Keep-alive Time: 45 Keep-alive Interval: 15
>=20
> Hello Time: 15 Hello Interval: 5
>=20
> PE2# sh ldp dis
>=20
> Local LSR Identifier: 10.0.0.2
>=20
> Interface Discovery Sources:
>=20
> eth1: xmit/recv
>=20
> LDP Id: 13.0.0.1:0
>=20
> Targeted Discovery Sources:
>=20
> No configured peers
>=20
> PE2# sh ldp fec
>=20
> FEC: 1 169.254.0.0/16
>=20
> 1 0.0.0.0 0
>=20
> FEC: 2 10.0.0.0/24
>=20
> 2 0.0.0.0 1
>=20
> PE2# sh ldp dat
>=20
> 10.0.0.0/24 local binding: label: gen 10001
>=20
> 10.0.0.0/24 remote binding: label: gen 10001 lsr: 13.0.0.1:0 ingress
>=20
> PE2# sh mpls for
>=20
> Insegments:
>=20
> Lbl Spc Label Owner
>=20
> 0 10001 ldp
>=20
> Total 1
>=20
> Outsegments:
>=20
> Interface Label Next Hop Owner
>=20
> eth1 10001 10.0.0.1 ldp
>=20
> Total 1
>=20
> Cross Connects:
>=20
> Total 0
>=20
> PE2# sh ip route
>=20
> Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
>=20
> I - ISIS, B - BGP, > - selected route, * - FIB route
>=20
> O 10.0.0.0/24 [110/10] is directly connected, eth1, 00:06:05
>=20
> C>* 10.0.0.0/24 is directly connected, eth1
>=20
> O 11.0.0.0/24 [110/10] is directly connected, eth0, 00:06:05
>=20
> C>* 11.0.0.0/24 is directly connected, eth0
>=20
> O>* 13.0.0.0/24 [110/20] via 10.0.0.1, eth1, 00:05:12
>=20
> C>* 127.0.0.0/8 is directly connected, lo
>=20
> K>* 169.254.0.0/16 is directly connected, eth1
>=20
> PE2# sh ldp ses
>=20
> 2 1.0.0.0 45 OPERATIONAL
>=20
> 10.0.0.1
>=20
> 13.0.0.1
>=20
> PE2# sh ldp dis
>=20
> Local LSR Identifier: 10.0.0.2
>=20
> Interface Discovery Sources:
>=20
> eth1: xmit/recv
>=20
> LDP Id: 13.0.0.1:0
>=20
> Targeted Discovery Sources:
>=20
> No configured peers
>=20
> PE2# sh ldp neig
>=20
> Peer LDP Ident: 13.0.0.1:0; Local LDP Ident: 10.0.0.2:0
>=20
> TCP connection: 10.0.0.2.39560 - 10.0.0.1.646
>=20
> State: OPERATIONAL; Msgs sent/recv: 26/78; UNSOLICITED
>=20
> Up time: 00:05:18
>=20
> LDP discovery sources:
>=20
> eth1
>=20
> Addresses bound to peer:
>=20
> 10.0.0.1 13.0.0.1
>=20
> PE2# sh mpls hard
>=20
> MPLS-Linux: 1.950 netlink control
>=20
> PE2# sh mpls ver
>=20
> Version 1.950
>=20
> [root@PE2]# mpls ilm
>=20
> ILM entry label gen 10001 labelspace 0 proto ipv4
>=20
> pop peek (0 bytes, 0 pkts)
>=20
> [root@PE2]# mpls nhlfe
>=20
> NHLFE entry key 0x00000003 mtu 1496 propagate_ttl
>=20
> push gen 10001 set eth1 ipv4 10.0.0.1 (0 bytes, 0 pkts)
>=20
> [root@PE2]# ip route
>=20
> 10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.2
>=20
> 11.0.0.0/24 dev eth0 proto kernel scope link src 11.0.0.1
>=20
> 13.0.0.0/24 via 10.0.0.1 dev eth1 proto zebra metric 20
>=20
> The result is that, althaugh the NHLFE and ILM tables add a new entry for=
 10.0.0.0/24 subnet,=20
>=20
> I'm not able to send labeled packets from one host to another because IP =
table doesn't change=20
>=20
> to route the packets via mpls.
>=20
> I think we're very close to solve it, but I need your help.
>=20
> Thanks in advange,
>=20
> Gonzalo
>=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...