Thread: [mpls-linux-general] mpls FC3 hierarchy question
Status: Beta
Brought to you by:
jleu
|
From: diva p. <div...@pl...> - 2006-01-25 00:41:04
|
Hi James,sorry i want to ask some ques
I had installed FD3 in my computers and have compiled
mpls-linux successfully.
I have used : 1.linux-2.6.9.tar
2.mpls-linux-1.946a.tar
3.iproute-2.6.9-3mpls1_946.i386.rpm
4.quagga-0.97.3-1.FC3mpls1_946a.i386.rpm
I have the following simple topology
ip(11.0.4.1) --- LER1 (11.0.1.1) --- (11.0.1.2) LSR1
(11.0.2.1)
--- (11.0.2.2) LSR2 (11.0.3.1) --- (11.0.3.2) LER2 ---
ip(11.0.5.1)
or in MPLS network label topology:
101
100 201 200
LER1------LSR1------LSR2------LER2
Between LER1 and LSR1 use label 100
Between LER2 and LSR2 use label 200
Between LER1 and LER2 use label 101 and 201
assumtion we send with eth0 and receive with eth1
I want ip(11.0.4.1) with/to ip(11.0.5.1) can communicate
I have used the example hierarchy in
http://mpls-linux.sf.net command,but i have confused
because in the http://mpls-linux.sf.net only use two
computers.
I have configured with the following command:
Setup LSP between Ingress LER1 and LSR1:
[root@LER1]#mpls nhlfe add key 0
(key 2)
[root@LER1]#mpls nhlfe change key 0x2 instructions push
gen 100 nexthop eth0 11.0.1.2
[root@LER1]#ip route add 11.0.5.1
[root@LSR1]#mpls labelspace add dev eth1 labelspace 0
[root@LSR1]#mpls ilm add label gen 100 labelspace 0
Setup LSP between Engress LSR2 and LER2:
[root@LSR2]#mpls nhlfe add key 0
(key 2)
[root@LSR2]#mpls nhlfe change key 0x2 instructions push
gen 200 nexthop eth0 11.0.3.2
[root@LER2]#mpls labelspace add dev eth1 labelspace 0
[root@LER2]#mpls ilm add label gen 200 labelspace 0
Setup LSP between LSR1 and LSR2 (label 101):
[root@LSR1]#mpls nhlfe add key 0
(key 2)
[root@LSR1]#mpls nhlfe change key 0x2 instructions push
gen 101 nexthop eth0 11.0.2.2
[root@LSR2]#mpls labelspace add dev eth1 labelspace 0
[root@LSR2]#mpls ilm add label gen 101 labelspace 0
Setup another LSP between LSR1 and LSR2 (201 label):
[root@LSR1]#mpls nhlfe key 0
(key 3)
[root@LSR1]#mpls nhlfe change key 0x3 instructions push
gen 101 nexthop eth0 11.0.2.2
[root@LSR2]#mpls ilm add label gen 201 labelspace 0
Forwarding traffic for the 201 LSP to ride on the 101 LSP:
[root@LSR1]#mpls nhlfe change key 0x3 instrutions push gen
201 forward 0x2
[root@LSR2]#mpls ilm add label gen 101 labelspace 0
Some question that i want to ask:
1.Please check, is my command true and how the solution?
2.How to tie the LSPs together
3.How to configure via tunnel interface
4.How to use quagga,i cannot get the command (config t)
sorry i have much ques,THANKS VERY MUCH BEFORE with your
attention
========================================================================================
Speedy Gift 4 You. Pasang Speedy gratis Flexi Trendy dan berhadiah undian :
3 Notebook, 7 Handycam, 9 Digital Camera, dan 25 Modem ADSL. Maaf hanya untuk Januari 2006.
Info : 147 (Khusus Jawa Timur)
========================================================================================
Dapatkan hosting tercepat dengan bandwidth tak terbatas. Hanya di http://www.hostingkilat.com
========================================================================================
|
|
From: James R. L. <jl...@mi...> - 2006-01-25 13:57:54
|
Any reason why you didn't use the FC3 kernel RPM or SRPM I provide?
Just curious.
As for your question, your missing the 'xc' or cross connects. I have post=
ed
more documentation for 1.950 at sourceforge. The examples I've posted for
1.950 will not work _exactly_ for 1.946, but the 'xc' command has not
changed from 1.946 to 1.950 so I think it will be usful to see how it is
used.
http://sourceforge.net/docman/?group_id=3D15443
On Wed, Jan 25, 2006 at 07:40:47AM +0700, diva permata wrote:
>=20
> Hi James,sorry i want to ask some ques
> I had installed FD3 in my computers and have compiled=20
> mpls-linux successfully.
>=20
> I have used : 1.linux-2.6.9.tar
> 2.mpls-linux-1.946a.tar
> 3.iproute-2.6.9-3mpls1_946.i386.rpm
> 4.quagga-0.97.3-1.FC3mpls1_946a.i386.rpm
>=20
> I have the following simple topology
>=20
> ip(11.0.4.1) --- LER1 (11.0.1.1) --- (11.0.1.2) LSR1=20
> (11.0.2.1)
> --- (11.0.2.2) LSR2 (11.0.3.1) --- (11.0.3.2) LER2 ---=20
> ip(11.0.5.1)
>=20
> or in MPLS network label topology:
> 101
> 100 201 200
> LER1------LSR1------LSR2------LER2
>=20
> Between LER1 and LSR1 use label 100
> Between LER2 and LSR2 use label 200
> Between LER1 and LER2 use label 101 and 201
> assumtion we send with eth0 and receive with eth1
> I want ip(11.0.4.1) with/to ip(11.0.5.1) can communicate
>=20
> I have used the example hierarchy in=20
> http://mpls-linux.sf.net command,but i have confused=20
> because in the http://mpls-linux.sf.net only use two=20
> computers.
>=20
> I have configured with the following command:
>=20
> Setup LSP between Ingress LER1 and LSR1:
> [root@LER1]#mpls nhlfe add key 0
> (key 2)
> [root@LER1]#mpls nhlfe change key 0x2 instructions push=20
> gen 100 nexthop eth0 11.0.1.2
> [root@LER1]#ip route add 11.0.5.1
>=20
> [root@LSR1]#mpls labelspace add dev eth1 labelspace 0
> [root@LSR1]#mpls ilm add label gen 100 labelspace 0
>=20
> Setup LSP between Engress LSR2 and LER2:
> [root@LSR2]#mpls nhlfe add key 0
> (key 2)
> [root@LSR2]#mpls nhlfe change key 0x2 instructions push=20
> gen 200 nexthop eth0 11.0.3.2
>=20
> [root@LER2]#mpls labelspace add dev eth1 labelspace 0
> [root@LER2]#mpls ilm add label gen 200 labelspace 0
>=20
> Setup LSP between LSR1 and LSR2 (label 101):
> [root@LSR1]#mpls nhlfe add key 0
> (key 2)
> [root@LSR1]#mpls nhlfe change key 0x2 instructions push=20
> gen 101 nexthop eth0 11.0.2.2
>=20
> [root@LSR2]#mpls labelspace add dev eth1 labelspace 0
> [root@LSR2]#mpls ilm add label gen 101 labelspace 0
>=20
> Setup another LSP between LSR1 and LSR2 (201 label):
> [root@LSR1]#mpls nhlfe key 0
> (key 3)
> [root@LSR1]#mpls nhlfe change key 0x3 instructions push=20
> gen 101 nexthop eth0 11.0.2.2
>=20
> [root@LSR2]#mpls ilm add label gen 201 labelspace 0
>=20
> Forwarding traffic for the 201 LSP to ride on the 101 LSP:
> [root@LSR1]#mpls nhlfe change key 0x3 instrutions push gen=20
> 201 forward 0x2
>=20
> [root@LSR2]#mpls ilm add label gen 101 labelspace 0
>=20
> Some question that i want to ask:
> 1.Please check, is my command true and how the solution?
> 2.How to tie the LSPs together
> 3.How to configure via tunnel interface
> 4.How to use quagga,i cannot get the command (config t)
>=20
> sorry i have much ques,THANKS VERY MUCH BEFORE with your=20
> attention
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Speedy Gift 4 You. Pasang Speedy gratis Flexi Trendy dan berhadiah undian=
:=20
> 3 Notebook, 7 Handycam, 9 Digital Camera, dan 25 Modem ADSL. Maaf hanya=
=20
> untuk Januari 2006. Info : 147 (Khusus Jawa Timur)
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Dapatkan hosting tercepat dengan bandwidth tak terbatas. Hanya di=20
> http://www.hostingkilat.com
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
--=20
James R. Leu
jl...@mi...
|