Re: [mpls-linux-devel] MPLS-Linux-1.955 FC5

[James R. L. <jl...@mi...>]

Please include the output of:

   sho ip route

from vtysh and:

   ip route show

from the command line.

On Thu, Mar 08, 2007 at 12:20:43PM +0100, Sienes Rodr?guez Gonzalo wrote:
> Hi James!
>=20
> I've just installed FC5 and all the MPLS-Linux-1.955 RPMs for this OS:
>=20
> [root@PE1 ~]# rpm -qa | grep mpls | sort
> ebtables-2.0.8-0.6.rc2.fc5.mpls.1.955
> glibc-kernheaders-3.0-5.2.fc5.mpls.1.955
> iproute-2.6.16-1.fc5.mpls.1.955
> iptables-1.3.5-1.2.fc5.mpls.1.955
> kernel-devel-2.6.18-1.2257.fc5.mpls.1.955
> kernel-smp-2.6.18-1.2257.fc5.mpls.1.955
> kernel-smp-devel-2.6.18-1.2257.fc5.mpls.1.955
> quagga-0.99.6-01.fc5.mpls.1.955
>=20
> [root@PE1 ~]# lsmod | grep mpls
> mpls4                  10240  0
>=20
> I try a simple environment with 2 LSRs:
> 	   =20
> 		   eth0	  eth1             eth1   eth0
> 	12.0.0.1-------PE1---------------------PE2-------172.29.17.60
> 			  .1  10.0.0.0/24    .2
>=20
> This is the configuration I made on PE1 by vtysh:
>=20
> PE1# sh run
> Building configuration...
>=20
> Current configuration:
> !
> hostname PE1
> !
> password root
> enable password root
> !
> interface eth0
>  ipv6 nd suppress-ra
> !
> interface eth1
>  ipv6 nd suppress-ra
>  mpls ip
>  mpls labelspace 0
> !
> interface lo
> !
> interface sit0
>  ipv6 nd suppress-ra
> !
> mpls ldp
>  egress connected
> !
> ip forwarding
> !
> line vty
> !
>=20
> And the outputs of the commands relative to LDP:
>=20
> PE1# sh ldp
> LSR-ID: 12.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
> PE1# sh ldp data
>   10.0.0.0/24  local binding:   label: gen 10002
>   10.0.0.0/24  remote binding:  no outlabel lsr: 10.0.0.2:0
>   172.29.16.0/22  remote binding:  no outlabel lsr: 10.0.0.2:0
> PE1# sh ldp dis
>=20
> Local LSR Identifier: 12.0.0.1
>=20
> Interface Discovery Sources:
>         eth1: xmit/recv
>             LDP Id: 10.0.0.2:0
>=20
> Targeted Discovery Sources:
>         No configured peers
>=20
> PE1# sh ldp fec
> FEC: 1 10.0.0.0/24
>         1 0.0.0.0 1
> FEC: 4 172.29.16.0/22
>=20
> PE1# sh ldp neigh
> Peer LDP Ident: 10.0.0.2:0; Local LDP Ident: 12.0.0.1:0
>         TCP connection: 10.0.0.1.34306 - 10.0.0.2.36479
>         State: OPERATIONAL; Msgs sent/recv: 63/191; UNSOLICITED
>         Up time: 00:14:38
>         LDP discovery sources:
>           eth1
>         Addresses bound to peer:
>           172.29.17.60  10.0.0.2
>=20
> PE1# sh ldp ses
> 4  10.0.0.2 45  OPERATIONAL
>         172.29.17.60
>         10.0.0.2
>=20
> PE1# sh mpls har
> MPLS-Linux: 1.955 netlink control
>=20
> [root@PE1 ~]# mpls nhlfe
> [root@PE1 ~]# mpls ilm
> ILM entry label gen 10002 labelspace 0 proto ipv4
>         pop peek  (0 bytes, 0 pkts)
>=20
> What I want to do is to send labelled packets while they are crossing 10.=
0.0.0/24. The problem is that LDP doesn't associate the labels that are dis=
covered to the routes.
>=20
> Where could I look at?
>=20
> Thanks,
>=20
> Gonzalo.
>=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...