Re: [mpls-linux-general] LSP ????

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

Without even reading your email I can tell you you need to
use the 'mpls xc' command on your LSRs.  I guess I need to post an example
that uses this.

Answers to your other questions.

mpls nhlfe add key 0		tell the kernel to allocate a NHLFE and
				a key for that NHLFE (think of 'key' in
				terms of a index).  The resulting key
				is displayed on standard out.  This
				key is the only way to refer to this
				newly created NHLFE.

mpls nhlfe change key 0x2 ...	change something about the NHLFE with
				the key of 0x2

mpls xc add ilm_label gen 100 ilm_labelspace 0 nhlfe_key 0x4
				cross connect traffic that arrives on
				ILM gen:100:0 to the NHLFE with the
				key 0x4

ip route add ... spec_nh 0x8847 0x3
				Add a route that has a special nexthop.
				0x8847 indicates its is a MPLS special
				nexthop.  0x3 indicates that the NHLFE
				with a key 0x3 is used as part of the
				special nexthop.

BTW please do not spam the mailing list with multiple versions
of the same question.  I will get around to answering you when I have
time, sending the question multiple times will not speed up the process.
			=09

On Wed, Sep 07, 2005 at 01:22:23AM +0800, taufico jose wrote:
> my MPLS test bed
>=20
>=20
>  A              B             C              D            E
> =3D=3D1.1---1.2=3D=3D2.1---2.2=3D=3D4.2---4.1=3D=3D5.1---5.2=3D=3D
>                3.1----------------------------3.2
>=20
>=20
> linux pc=3D A,B,C,D, and E
>=20
> note: B and D consists 3 NICs
>        : A,C and E consists 2 NICs
>        : "---" cable
>        : "=3D=3D" linuc pc
>=20
> Hello...I already try the example from (how to set up LSP) through this w=
eb page http://mpls-linux.sourceforge.net/simple.php . Thus the set up was =
successful  between A and B (please refer to my test bed above). I also tri=
ed to set up LSP between  B and A ..and it also was succesful.
>  =20
> My questions are:
>  =20
>  =20
>   1) I got confius when I want to set up LSP between A and C, also betwee=
n B and D and so forth. How the set up will be? How to set up the ip route =
between them ?
>  =20
> 2) This test-bed intended to transmit MPLS packet from A to E using "ping=
" command. The packet has two choices, either go through (A)1.1 --1.2--2.1-=
-2.2--4.2--4.1--5.1--5.2(E) or (A)1.1--1.2--3.1--3.2--5.1--5.2(E). For exam=
ple, output packet from A (gen 16) will go to B to C to D and finally E, wh=
ile ouput packet from A (gen 20) will go to B  to D and finally E. How this=
 network design can be achieved ?
> =20
> =20
> 3) Before the LSP has been set up between A and B, I had set up the kerne=
l routing table at each computer to enable computer A to ping each NIC. Do =
I have to change anything in "kernel routing table" in order to create Labe=
l routing table ?
>  =20
> 4) From your example given :
>  =20
> uml1
> ----
> [root@uml1 root]# cat /sys/mpls/version
>  1.946
> [root@uml1 root]# mpls nhlfe add key 0
> Key: 0x00000002
>  [root@uml1 root]# mpls nhlfe change key 0x2 instructions push gen 10000 =
nexthop eth1 ipv4 11.0.1.2
>  [root@uml1 root]# ip route add 11.0.1.2/32 via 11.0.1.2 spec_nh 0x8847 0=
x2
> [root@uml1 root]# mpls nhlfe show
> NHLFE entry key 0x00000002 mtu 1496 propagate_ttl
>          push gen 10000 set eth1 ipv4 11.0.1.2  (0 bytes, 0 pkts, 0 dropp=
ed)
> [root@uml1 root]# ip route show
> 11.0.1.2 via 11.0.1.2 dev eth1 spec_nh 0x8847 0x2  192.168.2.0/24 dev eth=
0  scope link
> 11.0.1.0/24 dev eth1  proto kernel  scope link  src 11.0.1.1
> 127.0.0.0/8 dev lo  scope link
> [root@uml1 root]#
>=20
>  =20
> 3i) What is the meaning of=20
>  =20
>     "add key 0"
>     "key 0x2"
>     "spec_nh 0x8847 0x2"
>  =20
> >From your example, I know the packet is labeled with 10000 and uml2 is s=
et up to receive only MPLS packet with label 1000.
>  =20
> Can somebody help me..my project is nearly success...
>=20
>=20
>=20
> Send instant messages to your online friends http://asia.messenger.yahoo.=
com=20
--=20
James R. Leu
jl...@mi...