Thread: [mpls-linux-general] can anyone help me ? (urgent!!!)
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-general
|
From: venda - y. <vy...@eu...> - 2002-04-19 12:58:06
|
Hi all,
We are a new user of mpls-linux. We want to implement mpls in our laboratory with 6 computer. We have run mpls-linux-1.0 in red hat 7.2 and kernel 2.4.7 by following the instruction that included in mpls-linux-1.0/readme. Base on the instruction first we get kernel 2.4.7 then untar this kernel. After uncompressing mpls-linux-1.0 , we patch linux-mpls.diff into the kernel and compile the kernel. We have done that steps successfully (we knew it by running !'dmesg | grep MPLS!( and we get the mpls version). The next step is enterting the directory /mpls-linux-1.0/utils then run !'make all!(, then edit the content of /etc/profile by adding :
export MPLSHOME=/usr/src/mpls-linux-1.0
export PATH=$PATH:$MPLSHOME/scripts:$MPLSHOME/utils
then run !(make mplsadm!(.
The topology that we use is like this :
Host A ----- LER A ------ LSR ------ LER B ----- Host B
Eth0 eth0 eth1 eth2 eth0 eth0 eth1 eth0
The ip number that we use :
Host A 3 eth0 : 192.167.1.1
LER A 3 eth0 : 192.167.1.2
eth1 : 192.167.2.2
LSR 3 eth2 : 192.167.2.3
eth0 : 192.167.3.3
LER B 3 eth0 : 192.167.3.4
eth1 : 192.167.4.4
Host B 3 eth0 : 192.167.4.5
Host A and host B -3 without MPLS
LER A :
root# mplsadm -v !VL eth0:0
root# mplsadm !Vv !VL eth1:0
root# mplsadm !Vv -A !VB !VO gen:1234:eth1:ipv4:192.167.2.3 !Vf 192.167.4.5/32
root# mplsadm !Vv !VA !VI gen:4563:0
mpls_in: 40474c00 0/0/0 gen 4563 0 POP PEEK
mpls_out: 40134803 0/0/0 PUSH (gen 1234) SET (eth1, 192.167.2.3)
LSR:
root# mplsadm -v !VL eth0:0
root# mplsadm !Vv !VL eth1:0
root# mplsadm !Vv !VA !VI gen:1234:0 !VO gen:2341:eth0:ipv4:192.167.3.4 !VB
root# mplsadm !Vv !VA !VI gen:3456:0 !VO gen:4563:eth2:ipv4:192.167.2.2 !VB
mpls_in : 40134800 0/0/0 gen 1234 0 POP FW (40249402)
40360000 0/0/0 gen 3456 0 POP FW (40474c04)
mpls_out: 40249402 0/0/0 PUSH (gen 2341) SET (eth0, 192.167.3.4)
40474c04 0/0/0 PUSH (gen 4563) SET (eth2, 192.167.2.2)
LER A :
root# mplsadm -v !VL eth0:0
root# mplsadm !Vv !VL eth1:0
root# mplsadm !Vv -A !VB !VO gen:3456:eth0:ipv4:192.167.3.3 !Vf 192.167.1.1/32
root# mplsadm !Vv !VA !VI gen:2341:0
mpls_in: 40249400 0/0/0 gen 2341 0 POP PEEK
mpls_out: 40360002 0/0/0 PUSH (gen 3456) SET (eth0, 192.167.3.3)
but when we ping host A from host B and also the opposite (host B from host A) we get the same output with the ordinary tcp/ip (ping host A from host B by using linux without mpls). We mean, if we use mpls to ping host A from host B it need b 1.485 ms and it is the same time that we need to ping host A from host B without mpls.
So we want to ask is there any mistake with all the things that we!&ve done ? because it looks like that our mpls is not running well. and what should we do with ldp-portable ? (we have download it, but we don't know how to use it to support mpls)
So can someone tell us how to fix it ? and how we will know that the mpls have run properly ? we waiting for your suggestion , thank you.
venda, andy, amiek.
Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com
|
|
From: venda - y. <vy...@eu...> - 2002-04-19 13:02:30
|
Hi all,
We are a new user of mpls-linux. We want to implement mpls in our laboratory with 6 computer. We have run mpls-linux-1.0 in red hat 7.2 and kernel 2.4.7 by following the instruction that included in mpls-linux-1.0/readme. Base on the instruction first we get kernel 2.4.7 then untar this kernel. After uncompressing mpls-linux-1.0 , we patch linux-mpls.diff into the kernel and compile the kernel. We have done that steps successfully (we knew it by running !'dmesg | grep MPLS!( and we get the mpls version). The next step is enterting the directory /mpls-linux-1.0/utils then run !'make all!(, then edit the content of /etc/profile by adding :
export MPLSHOME=/usr/src/mpls-linux-1.0
export PATH=$PATH:$MPLSHOME/scripts:$MPLSHOME/utils
then run !(make mplsadm!(.
The topology that we use is like this :
Host A ----- LER A ------ LSR ------ LER B ----- Host B
Eth0 eth0 eth1 eth2 eth0 eth0 eth1 eth0
The ip number that we use :
Host A 3 eth0 : 192.167.1.1
LER A 3 eth0 : 192.167.1.2
eth1 : 192.167.2.2
LSR 3 eth2 : 192.167.2.3
eth0 : 192.167.3.3
LER B 3 eth0 : 192.167.3.4
eth1 : 192.167.4.4
Host B 3 eth0 : 192.167.4.5
Host A and host B -3 without MPLS
LER A :
root# mplsadm -v !VL eth0:0
root# mplsadm !Vv !VL eth1:0
root# mplsadm !Vv -A !VB !VO gen:1234:eth1:ipv4:192.167.2.3 !Vf 192.167.4.5/32
root# mplsadm !Vv !VA !VI gen:4563:0
mpls_in: 40474c00 0/0/0 gen 4563 0 POP PEEK
mpls_out: 40134803 0/0/0 PUSH (gen 1234) SET (eth1, 192.167.2.3)
LSR:
root# mplsadm -v !VL eth0:0
root# mplsadm !Vv !VL eth1:0
root# mplsadm !Vv !VA !VI gen:1234:0 !VO gen:2341:eth0:ipv4:192.167.3.4 !VB
root# mplsadm !Vv !VA !VI gen:3456:0 !VO gen:4563:eth2:ipv4:192.167.2.2 !VB
mpls_in : 40134800 0/0/0 gen 1234 0 POP FW (40249402)
40360000 0/0/0 gen 3456 0 POP FW (40474c04)
mpls_out: 40249402 0/0/0 PUSH (gen 2341) SET (eth0, 192.167.3.4)
40474c04 0/0/0 PUSH (gen 4563) SET (eth2, 192.167.2.2)
LER A :
root# mplsadm -v !VL eth0:0
root# mplsadm !Vv !VL eth1:0
root# mplsadm !Vv -A !VB !VO gen:3456:eth0:ipv4:192.167.3.3 !Vf 192.167.1.1/32
root# mplsadm !Vv !VA !VI gen:2341:0
mpls_in: 40249400 0/0/0 gen 2341 0 POP PEEK
mpls_out: 40360002 0/0/0 PUSH (gen 3456) SET (eth0, 192.167.3.3)
but when we ping host A from host B and also the opposite (host B from host A) we get the same output with the ordinary tcp/ip (ping host A from host B by using linux without mpls). We mean, if we use mpls to ping host A from host B it need b 1.485 ms and it is the same time that we need to ping host A from host B without mpls.
So we want to ask is there any mistake with all the things that we!&ve done ? because it looks like that our mpls is not running well. and what should we do with ldp-portable ? (we have download it, but we don't know how to use it to support mpls)
So can someone tell us how to fix it ? and how we will know that the mpls have run properly ? we waiting for your suggestion , thank you.
venda, andy, amiek.
Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com
|
|
From: James R. L. <jl...@mi...> - 2002-04-23 14:34:56
|
On Fri, Apr 19, 2002 at 07:57:45PM +0700, venda - yuniarti wrote: > Hi all,=20 > We are a new user of mpls-linux. We want to implement mpls in our labora= tory with 6 computer. We have run mpls-linux-1.0 in red hat 7.2 and kernel = 2.4.7 by following the instruction that included in mpls-linux-1.0/readme. = Base on the instruction first we get kernel 2.4.7 then untar this kernel. A= fter uncompressing mpls-linux-1.0 , we patch linux-mpls.diff into the kerne= l and compile the kernel. We have done that steps successfully (we knew it = by running !'dmesg | grep MPLS!( and we get the mpls version). The next ste= p is enterting the directory /mpls-linux-1.0/utils then run !'make all!(, t= hen edit the content of /etc/profile by adding : > export MPLSHOME=3D/usr/src/mpls-linux-1.0 > export PATH=3D$PATH:$MPLSHOME/scripts:$MPLSHOME/utils > then run !(make mplsadm!(.=20 > The topology that we use is like this : >=20 > Host A ----- LER A ------ LSR ------ LER B ----- Host B > Eth0 eth0 eth1 eth2 eth0 eth0 eth1 eth0 >=20 > The ip number that we use : > Host A =043 eth0 : 192.167.1.1 > LER A =043 eth0 : 192.167.1.2 > eth1 : 192.167.2.2 > LSR =043 eth2 : 192.167.2.3 > eth0 : 192.167.3.3 > LER B =043 eth0 : 192.167.3.4 > eth1 : 192.167.4.4 > Host B =043 eth0 : 192.167.4.5 >=20 > Host A and host B -=043 without MPLS=20 >=20 > LER A : > root# mplsadm -v !VL eth0:0 > root# mplsadm !Vv !VL eth1:0 > root# mplsadm !Vv -A !VB !VO gen:1234:eth1:ipv4:192.167.2.3 !Vf 192.167.= 4.5/32 > root# mplsadm !Vv !VA !VI gen:4563:0 > mpls_in: 40474c00 0/0/0 gen 4563 0 POP PEEK > mpls_out: 40134803 0/0/0 PUSH (gen 1234) SET (eth1, 192.167.2.3) >=20 > LSR: > root# mplsadm -v !VL eth0:0 > root# mplsadm !Vv !VL eth1:0 > root# mplsadm !Vv !VA !VI gen:1234:0 !VO gen:2341:eth0:ipv4:192.167.3.4 != VB > root# mplsadm !Vv !VA !VI gen:3456:0 !VO gen:4563:eth2:ipv4:192.167.2.2 != VB > mpls_in : 40134800 0/0/0 gen 1234 0 POP FW (40249402) > 40360000 0/0/0 gen 3456 0 POP FW (40474c04) > mpls_out: 40249402 0/0/0 PUSH (gen 2341) SET (eth0, 192.167.3.4) > 40474c04 0/0/0 PUSH (gen 4563) SET (eth2, 192.167.2.2) >=20 > LER A : > root# mplsadm -v !VL eth0:0 > root# mplsadm !Vv !VL eth1:0 > root# mplsadm !Vv -A !VB !VO gen:3456:eth0:ipv4:192.167.3.3 !Vf 192.167.= 1.1/32 > root# mplsadm !Vv !VA !VI gen:2341:0 > mpls_in: 40249400 0/0/0 gen 2341 0 POP PEEK > mpls_out: 40360002 0/0/0 PUSH (gen 3456) SET (eth0, 192.167.3.3) >=20 > but when we ping host A from host B and also the opposite (host B from ho= st A) we get the same output with the ordinary tcp/ip (ping host A from hos= t B by using linux without mpls). We mean, if we use mpls to ping host A fr= om host B it need =04b 1.485 ms and it is the same time that we need to pin= g host A from host B without mpls.=20 > So we want to ask is there any mistake with all the things that we!&ve do= ne ? because it looks like that our mpls is not running well. and what shou= ld we do with ldp-portable ? (we have download it, but we don't know how to= use it to support mpls) > So can someone tell us how to fix it ? and how we will know that the mpls= have run properly ? we waiting for your suggestion , thank you. > venda, andy, amiek. You won;t necessarily see a change in your ping times. You shoud go to LSR A or B and do a tcpdump (or ethereal) on on of those interface to what is happening. In addition turn on mpls kernel debugging (mplsadm -d) and look at your console output (also in /var/log/messages) Jim >=20 >=20 >=20 > Join 18 million Eudora users by signing up for a free Eudora Web-Mail acc= ount at http://www.eudoramail.com >=20 > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X