Thread: [mpls-linux-general] trouble setting up LSPs
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-general
|
From: Wayne W. S. <ww...@ho...> - 2002-09-10 03:04:55
|
Hi, Just downloaded, installed and compiled the latest version into the kernel. I am trying to setup two LSPs, one going from A to C and the other going from C back to A in the following simple network, but could not get ping to work from A to C nor from C to A. 10.0.0.10 (eth0) 10.0.1.20 (eth1) A---------------------B---------------------C 10.0.0.20 (eth0) 10.0.1.30 (eth1) The commands issued are as follows, and I have checked /proc/net/mpls* and it seems all the entries are recorded correctly. On A: ===== mplsadm2 -vAO 0 -o push:gen:16:set:eth0:ipv4:10.0.1.30 # returns <key1> ip2 route add 10.0.1.30/32 via 10.0.0.20 lsp <key1> mplsadm2 -vAI gen:20:0 mplsadm2 -vL eth0:0 On B: ===== # for LSP from A to C mplsadm2 -vAI gen:16:0 mplsadm2 -vAO 0 -o push:gen:16:set:eth1:ipv4:10.0.1.30 # returns <key2> mplsadm2 -vI gen:16:0 -o <key2> -B mplsadm2 -vL eth1:0 # for LSP from C to A mplsadm2 -vAI gen:20:0 mplsadm2 -vAO 0 -o push:gen:20:set:eth0:ipv4:10.0.0.10 # returns <key3> mplsadm2 -vI gen:20:0 -o <key3> -B mplsadm2 -vL eth0:0 On C: ===== mplsadm2 -vAI gen:16:0 mplsadm2 -vAO 0 -o push:gen:20:set:eth1:ipv4:10.0.0.10 # returns <key4> ip2 route add 10.0.0.10/32 via 10.0.1.20 lsp <key4> mplsadm2 -vL eth1:0 I have doubled-checked the commands and I believe they are accurate and complete. Any ideas on what could be wrong and suggestions on what to do? Thanks, -Wayne |
|
From: James R. L. <jl...@mi...> - 2002-09-10 14:37:57
|
Suggested changes inline:
>
> 10.0.0.10 (eth0) 10.0.1.20 (eth1)
> A---------------------B---------------------C
> 10.0.0.20 (eth0) 10.0.1.30 (eth1)
>
> On A:
> =====
> mplsadm2 -vAO 0 -o push:gen:16:set:eth0:ipv4:10.0.1.30 # returns <key1>
^^^^^^^^^
10.0.0.20?
> ip2 route add 10.0.1.30/32 via 10.0.0.20 lsp <key1>
> mplsadm2 -vAI gen:20:0
> mplsadm2 -vL eth0:0
>
> On B:
> =====
> # for LSP from A to C
> mplsadm2 -vAI gen:16:0
> mplsadm2 -vAO 0 -o push:gen:16:set:eth1:ipv4:10.0.1.30 # returns <key2>
> mplsadm2 -vI gen:16:0 -o <key2> -B
> mplsadm2 -vL eth1:0
>
> # for LSP from C to A
> mplsadm2 -vAI gen:20:0
> mplsadm2 -vAO 0 -o push:gen:20:set:eth0:ipv4:10.0.0.10 # returns <key3>
> mplsadm2 -vI gen:20:0 -o <key3> -B
> mplsadm2 -vL eth0:0
>
> On C:
> =====
> mplsadm2 -vAI gen:16:0
> mplsadm2 -vAO 0 -o push:gen:20:set:eth1:ipv4:10.0.0.10 # returns <key4>
^^^^^^^^^
10.0.1.20?
> ip2 route add 10.0.0.10/32 via 10.0.1.20 lsp <key4>
> mplsadm2 -vL eth1:0
Check my suggested changes. If it still doesn't work, send the contents
of /proc/net/mpls_*
Jim
--
James R. Leu
|
|
From: Wayne W. S. <ww...@ho...> - 2002-09-10 16:02:06
|
Hi James, I have made the changes you suggested but I am still unable to ping C from A. The content of /proc/net/mpls* on each machine are as follows. Any ideas whats wrong? On A: ===== [root@csgradpc03 net]# more mpls_* :::::::::::::: mpls_in :::::::::::::: 0x40005000 0/0/0 gen 20 0 1 POP PEEK :::::::::::::: mpls_labelspace :::::::::::::: eth0 0 14 :::::::::::::: mpls_out :::::::::::::: 0x00000005 55/4620/0 3 PUSH(gen 16) SET(eth0,10.0.0.20) :::::::::::::: mpls_tunnel :::::::::::::: [root@csgradpc03 net]# ip2 route 10.0.1.30 via 10.0.0.20 dev eth0 lsp 0x5 10.0.0.0/24 dev eth0 scope link 10.0.1.0/24 dev eth2 scope link 129.97.78.0/24 dev eth1 scope link 10.1.0.0/24 dev eth3 scope link 127.0.0.0/8 dev lo scope link default dev eth1 scope link On B: ===== [root@node02 net]# more mpls_* :::::::::::::: mpls_in :::::::::::::: 0x40004000 55/4840/0 gen 16 0 56 POP PEEK 0x40005000 0/0/0 gen 20 0 1 POP PEEK :::::::::::::: mpls_labelspace :::::::::::::: eth0 0 9 eth1 0 8 :::::::::::::: mpls_out :::::::::::::: 0x00000002 0/0/0 1 PUSH(gen 16) SET(eth1,10.0.1.30) 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth0,10.0.0.10) :::::::::::::: mpls_tunnel :::::::::::::: [root@node02 net]# ip2 route 10.0.0.0/24 dev eth0 scope link 10.0.1.0/24 dev eth1 scope link 10.1.0.0/24 dev eth2 scope link 127.0.0.0/8 dev lo scope link default via 10.0.0.1 dev eth0 On C: ===== [root@node03 net]# more mpls_* :::::::::::::: mpls_in :::::::::::::: 0x40004000 0/0/0 gen 16 0 1 POP PEEK :::::::::::::: mpls_labelspace :::::::::::::: eth1 0 9 :::::::::::::: mpls_out :::::::::::::: 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth1,10.0.1.20) :::::::::::::: mpls_tunnel :::::::::::::: [root@node03 net]# ip2 route 10.0.0.10 via 10.0.1.20 dev eth1 lsp 0x3 10.0.0.0/24 dev eth0 scope link 10.0.1.0/24 dev eth1 scope link 10.1.0.0/24 dev eth2 scope link 127.0.0.0/8 dev lo scope link default via 10.0.0.1 dev eth0 On Tue, 10 Sep 2002, James R. Leu wrote: > Suggested changes inline: > > > > > 10.0.0.10 (eth0) 10.0.1.20 (eth1) > > A---------------------B---------------------C > > 10.0.0.20 (eth0) 10.0.1.30 (eth1) > > > > On A: > > ===== > > mplsadm2 -vAO 0 -o push:gen:16:set:eth0:ipv4:10.0.1.30 # returns <key1> > ^^^^^^^^^ > 10.0.0.20? > > > ip2 route add 10.0.1.30/32 via 10.0.0.20 lsp <key1> > > mplsadm2 -vAI gen:20:0 > > mplsadm2 -vL eth0:0 > > > > On B: > > ===== > > # for LSP from A to C > > mplsadm2 -vAI gen:16:0 > > mplsadm2 -vAO 0 -o push:gen:16:set:eth1:ipv4:10.0.1.30 # returns <key2> > > mplsadm2 -vI gen:16:0 -o <key2> -B > > mplsadm2 -vL eth1:0 > > > > # for LSP from C to A > > mplsadm2 -vAI gen:20:0 > > mplsadm2 -vAO 0 -o push:gen:20:set:eth0:ipv4:10.0.0.10 # returns <key3> > > mplsadm2 -vI gen:20:0 -o <key3> -B > > mplsadm2 -vL eth0:0 > > > > On C: > > ===== > > mplsadm2 -vAI gen:16:0 > > mplsadm2 -vAO 0 -o push:gen:20:set:eth1:ipv4:10.0.0.10 # returns <key4> > ^^^^^^^^^ > 10.0.1.20? > > > ip2 route add 10.0.0.10/32 via 10.0.1.20 lsp <key4> > > mplsadm2 -vL eth1:0 > > Check my suggested changes. If it still doesn't work, send the contents > of /proc/net/mpls_* > > Jim > -- > James R. Leu > |
|
From: Gilles N. <gno...@ee...> - 2002-09-10 16:16:16
|
You need to type these commands: On A: route add -host 10.0.1.30 gw 10.0.0.20 On C: route add - host 10.0.0.10 gw 10.0.1.20 Normally it should work. Regards. On Tue, 10 Sep 2002, Wayne W. Szeto wrote: > Hi James, > > I have made the changes you suggested but I am still unable to ping C from > A. The content of /proc/net/mpls* on each machine are as follows. Any > ideas whats wrong? > > On A: > ===== > [root@csgradpc03 net]# more mpls_* > :::::::::::::: > mpls_in > :::::::::::::: > 0x40005000 0/0/0 gen 20 0 1 POP PEEK > :::::::::::::: > mpls_labelspace > :::::::::::::: > eth0 0 14 > :::::::::::::: > mpls_out > :::::::::::::: > 0x00000005 55/4620/0 3 PUSH(gen 16) SET(eth0,10.0.0.20) > :::::::::::::: > mpls_tunnel > :::::::::::::: > [root@csgradpc03 net]# ip2 route > 10.0.1.30 via 10.0.0.20 dev eth0 lsp 0x5 > 10.0.0.0/24 dev eth0 scope link > 10.0.1.0/24 dev eth2 scope link > 129.97.78.0/24 dev eth1 scope link > 10.1.0.0/24 dev eth3 scope link > 127.0.0.0/8 dev lo scope link > default dev eth1 scope link > > On B: > ===== > [root@node02 net]# more mpls_* > :::::::::::::: > mpls_in > :::::::::::::: > 0x40004000 55/4840/0 gen 16 0 56 POP PEEK > 0x40005000 0/0/0 gen 20 0 1 POP PEEK > :::::::::::::: > mpls_labelspace > :::::::::::::: > eth0 0 9 > eth1 0 8 > :::::::::::::: > mpls_out > :::::::::::::: > 0x00000002 0/0/0 1 PUSH(gen 16) SET(eth1,10.0.1.30) > 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth0,10.0.0.10) > :::::::::::::: > mpls_tunnel > :::::::::::::: > [root@node02 net]# ip2 route > 10.0.0.0/24 dev eth0 scope link > 10.0.1.0/24 dev eth1 scope link > 10.1.0.0/24 dev eth2 scope link > 127.0.0.0/8 dev lo scope link > default via 10.0.0.1 dev eth0 > > On C: > ===== > [root@node03 net]# more mpls_* > :::::::::::::: > mpls_in > :::::::::::::: > 0x40004000 0/0/0 gen 16 0 1 POP PEEK > :::::::::::::: > mpls_labelspace > :::::::::::::: > eth1 0 9 > :::::::::::::: > mpls_out > :::::::::::::: > 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth1,10.0.1.20) > :::::::::::::: > mpls_tunnel > :::::::::::::: > [root@node03 net]# ip2 route > 10.0.0.10 via 10.0.1.20 dev eth1 lsp 0x3 > 10.0.0.0/24 dev eth0 scope link > 10.0.1.0/24 dev eth1 scope link > 10.1.0.0/24 dev eth2 scope link > 127.0.0.0/8 dev lo scope link > default via 10.0.0.1 dev eth0 > > > > > On Tue, 10 Sep 2002, James R. Leu wrote: > > > Suggested changes inline: > > > > > > > > 10.0.0.10 (eth0) 10.0.1.20 (eth1) > > > A---------------------B---------------------C > > > 10.0.0.20 (eth0) 10.0.1.30 (eth1) > > > > > > On A: > > > ===== > > > mplsadm2 -vAO 0 -o push:gen:16:set:eth0:ipv4:10.0.1.30 # returns <key1> > > ^^^^^^^^^ > > 10.0.0.20? > > > > > ip2 route add 10.0.1.30/32 via 10.0.0.20 lsp <key1> > > > mplsadm2 -vAI gen:20:0 > > > mplsadm2 -vL eth0:0 > > > > > > On B: > > > ===== > > > # for LSP from A to C > > > mplsadm2 -vAI gen:16:0 > > > mplsadm2 -vAO 0 -o push:gen:16:set:eth1:ipv4:10.0.1.30 # returns <key2> > > > mplsadm2 -vI gen:16:0 -o <key2> -B > > > mplsadm2 -vL eth1:0 > > > > > > # for LSP from C to A > > > mplsadm2 -vAI gen:20:0 > > > mplsadm2 -vAO 0 -o push:gen:20:set:eth0:ipv4:10.0.0.10 # returns <key3> > > > mplsadm2 -vI gen:20:0 -o <key3> -B > > > mplsadm2 -vL eth0:0 > > > > > > On C: > > > ===== > > > mplsadm2 -vAI gen:16:0 > > > mplsadm2 -vAO 0 -o push:gen:20:set:eth1:ipv4:10.0.0.10 # returns <key4> > > ^^^^^^^^^ > > 10.0.1.20? > > > > > ip2 route add 10.0.0.10/32 via 10.0.1.20 lsp <key4> > > > mplsadm2 -vL eth1:0 > > > > Check my suggested changes. If it still doesn't work, send the contents > > of /proc/net/mpls_* > > > > Jim > > -- > > James R. Leu > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > |
|
From: James R. L. <jl...@mi...> - 2002-09-10 16:25:40
|
See comments inline:
> mpls_out
> ::::::::::::::
> 0x00000005 55/4620/0 3 PUSH(gen 16) SET(eth0,10.0.0.20)
^^^^^^^
means traffic was sent on this outlabel
> 10.0.1.30 via 10.0.0.20 dev eth0 lsp 0x5
^^^
looks right
> mpls_in
> ::::::::::::::
> 0x40004000 55/4840/0 gen 16 0 56 POP PEEK
^^^^^^^ ^^^^
means we recv traffic No no, you want this to say FWD ...
mplsadm2 -I gen:16:0 -O 0x2 -B
will XC gen:16:0 to outlabel with index 0x2
Start with that fix.
Jim
> 0x40005000 0/0/0 gen 20 0 1 POP PEEK
> ::::::::::::::
> mpls_labelspace
> ::::::::::::::
> eth0 0 9
> eth1 0 8
> ::::::::::::::
> mpls_out
> ::::::::::::::
> 0x00000002 0/0/0 1 PUSH(gen 16) SET(eth1,10.0.1.30)
> 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth0,10.0.0.10)
> ::::::::::::::
> mpls_tunnel
> ::::::::::::::
> [root@node02 net]# ip2 route
> 10.0.0.0/24 dev eth0 scope link
> 10.0.1.0/24 dev eth1 scope link
> 10.1.0.0/24 dev eth2 scope link
> 127.0.0.0/8 dev lo scope link
> default via 10.0.0.1 dev eth0
>
> On C:
> =====
> [root@node03 net]# more mpls_*
> ::::::::::::::
> mpls_in
> ::::::::::::::
> 0x40004000 0/0/0 gen 16 0 1 POP PEEK
> ::::::::::::::
> mpls_labelspace
> ::::::::::::::
> eth1 0 9
> ::::::::::::::
> mpls_out
> ::::::::::::::
> 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth1,10.0.1.20)
> ::::::::::::::
> mpls_tunnel
> ::::::::::::::
> [root@node03 net]# ip2 route
> 10.0.0.10 via 10.0.1.20 dev eth1 lsp 0x3
> 10.0.0.0/24 dev eth0 scope link
> 10.0.1.0/24 dev eth1 scope link
> 10.1.0.0/24 dev eth2 scope link
> 127.0.0.0/8 dev lo scope link
> default via 10.0.0.1 dev eth0
>
>
>
>
> On Tue, 10 Sep 2002, James R. Leu wrote:
>
> > Suggested changes inline:
> >
> > >
> > > 10.0.0.10 (eth0) 10.0.1.20 (eth1)
> > > A---------------------B---------------------C
> > > 10.0.0.20 (eth0) 10.0.1.30 (eth1)
> > >
> > > On A:
> > > =====
> > > mplsadm2 -vAO 0 -o push:gen:16:set:eth0:ipv4:10.0.1.30 # returns <key1>
> > ^^^^^^^^^
> > 10.0.0.20?
> >
> > > ip2 route add 10.0.1.30/32 via 10.0.0.20 lsp <key1>
> > > mplsadm2 -vAI gen:20:0
> > > mplsadm2 -vL eth0:0
> > >
> > > On B:
> > > =====
> > > # for LSP from A to C
> > > mplsadm2 -vAI gen:16:0
> > > mplsadm2 -vAO 0 -o push:gen:16:set:eth1:ipv4:10.0.1.30 # returns <key2>
> > > mplsadm2 -vI gen:16:0 -o <key2> -B
> > > mplsadm2 -vL eth1:0
> > >
> > > # for LSP from C to A
> > > mplsadm2 -vAI gen:20:0
> > > mplsadm2 -vAO 0 -o push:gen:20:set:eth0:ipv4:10.0.0.10 # returns <key3>
> > > mplsadm2 -vI gen:20:0 -o <key3> -B
> > > mplsadm2 -vL eth0:0
> > >
> > > On C:
> > > =====
> > > mplsadm2 -vAI gen:16:0
> > > mplsadm2 -vAO 0 -o push:gen:20:set:eth1:ipv4:10.0.0.10 # returns <key4>
> > ^^^^^^^^^
> > 10.0.1.20?
> >
> > > ip2 route add 10.0.0.10/32 via 10.0.1.20 lsp <key4>
> > > mplsadm2 -vL eth1:0
> >
> > Check my suggested changes. If it still doesn't work, send the contents
> > of /proc/net/mpls_*
> >
> > Jim
> > --
> > James R. Leu
> >
--
James R. Leu
|
|
From: Wayne W. S. <ww...@ho...> - 2002-09-11 16:55:30
|
Ok that fixes the ping problem, thank you. Now I am able to ping C from A and vice versa. However I notice that I can not ftp files > 1Mb along the estalished LSP (from A to C or C to A). Of course ftp works fine between A and B, and B and C. Any ideas on whats wrong? On Tue, 10 Sep 2002, James R. Leu wrote: > See comments inline: > > > > mpls_out > > :::::::::::::: > > 0x00000005 55/4620/0 3 PUSH(gen 16) SET(eth0,10.0.0.20) > ^^^^^^^ > means traffic was sent on this outlabel > > > 10.0.1.30 via 10.0.0.20 dev eth0 lsp 0x5 > ^^^ > looks right > > > mpls_in > > :::::::::::::: > > 0x40004000 55/4840/0 gen 16 0 56 POP PEEK > ^^^^^^^ ^^^^ > means we recv traffic No no, you want this to say FWD ... > > mplsadm2 -I gen:16:0 -O 0x2 -B > > will XC gen:16:0 to outlabel with index 0x2 > > Start with that fix. > > Jim > > > > 0x40005000 0/0/0 gen 20 0 1 POP PEEK > > :::::::::::::: > > mpls_labelspace > > :::::::::::::: > > eth0 0 9 > > eth1 0 8 > > :::::::::::::: > > mpls_out > > :::::::::::::: > > 0x00000002 0/0/0 1 PUSH(gen 16) SET(eth1,10.0.1.30) > > 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth0,10.0.0.10) > > :::::::::::::: > > mpls_tunnel > > :::::::::::::: > > [root@node02 net]# ip2 route > > 10.0.0.0/24 dev eth0 scope link > > 10.0.1.0/24 dev eth1 scope link > > 10.1.0.0/24 dev eth2 scope link > > 127.0.0.0/8 dev lo scope link > > default via 10.0.0.1 dev eth0 > > > > On C: > > ===== > > [root@node03 net]# more mpls_* > > :::::::::::::: > > mpls_in > > :::::::::::::: > > 0x40004000 0/0/0 gen 16 0 1 POP PEEK > > :::::::::::::: > > mpls_labelspace > > :::::::::::::: > > eth1 0 9 > > :::::::::::::: > > mpls_out > > :::::::::::::: > > 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth1,10.0.1.20) > > :::::::::::::: > > mpls_tunnel > > :::::::::::::: > > [root@node03 net]# ip2 route > > 10.0.0.10 via 10.0.1.20 dev eth1 lsp 0x3 > > 10.0.0.0/24 dev eth0 scope link > > 10.0.1.0/24 dev eth1 scope link > > 10.1.0.0/24 dev eth2 scope link > > 127.0.0.0/8 dev lo scope link > > default via 10.0.0.1 dev eth0 > > > > > > > > > > On Tue, 10 Sep 2002, James R. Leu wrote: > > > > > Suggested changes inline: > > > > > > > > > > > 10.0.0.10 (eth0) 10.0.1.20 (eth1) > > > > A---------------------B---------------------C > > > > 10.0.0.20 (eth0) 10.0.1.30 (eth1) > > > > > > > > On A: > > > > ===== > > > > mplsadm2 -vAO 0 -o push:gen:16:set:eth0:ipv4:10.0.1.30 # returns <key1> > > > ^^^^^^^^^ > > > 10.0.0.20? > > > > > > > ip2 route add 10.0.1.30/32 via 10.0.0.20 lsp <key1> > > > > mplsadm2 -vAI gen:20:0 > > > > mplsadm2 -vL eth0:0 > > > > > > > > On B: > > > > ===== > > > > # for LSP from A to C > > > > mplsadm2 -vAI gen:16:0 > > > > mplsadm2 -vAO 0 -o push:gen:16:set:eth1:ipv4:10.0.1.30 # returns <key2> > > > > mplsadm2 -vI gen:16:0 -o <key2> -B > > > > mplsadm2 -vL eth1:0 > > > > > > > > # for LSP from C to A > > > > mplsadm2 -vAI gen:20:0 > > > > mplsadm2 -vAO 0 -o push:gen:20:set:eth0:ipv4:10.0.0.10 # returns <key3> > > > > mplsadm2 -vI gen:20:0 -o <key3> -B > > > > mplsadm2 -vL eth0:0 > > > > > > > > On C: > > > > ===== > > > > mplsadm2 -vAI gen:16:0 > > > > mplsadm2 -vAO 0 -o push:gen:20:set:eth1:ipv4:10.0.0.10 # returns <key4> > > > ^^^^^^^^^ > > > 10.0.1.20? > > > > > > > ip2 route add 10.0.0.10/32 via 10.0.1.20 lsp <key4> > > > > mplsadm2 -vL eth1:0 > > > > > > Check my suggested changes. If it still doesn't work, send the contents > > > of /proc/net/mpls_* > > > > > > Jim > > > -- > > > James R. Leu > > > > > -- > James R. Leu > |
|
From: James R. L. <jl...@mi...> - 2002-09-11 21:10:29
|
You probably answered this for me already but what version are you using? I thought I had this fixed. Jim On Wed, Sep 11, 2002 at 12:55:17PM -0400, Wayne W. Szeto wrote: > > Ok that fixes the ping problem, thank you. Now I am able to ping C from A > and vice versa. However I notice that I can not ftp files > 1Mb along > the estalished LSP (from A to C or C to A). Of course ftp works fine > between A and B, and B and C. Any ideas on whats wrong? > > > > On Tue, 10 Sep 2002, James R. Leu wrote: > > > See comments inline: > > > > > > > mpls_out > > > :::::::::::::: > > > 0x00000005 55/4620/0 3 PUSH(gen 16) SET(eth0,10.0.0.20) > > ^^^^^^^ > > means traffic was sent on this outlabel > > > > > 10.0.1.30 via 10.0.0.20 dev eth0 lsp 0x5 > > ^^^ > > looks right > > > > > mpls_in > > > :::::::::::::: > > > 0x40004000 55/4840/0 gen 16 0 56 POP PEEK > > ^^^^^^^ ^^^^ > > means we recv traffic No no, you want this to say FWD ... > > > > mplsadm2 -I gen:16:0 -O 0x2 -B > > > > will XC gen:16:0 to outlabel with index 0x2 > > > > Start with that fix. > > > > Jim > > > > > > > 0x40005000 0/0/0 gen 20 0 1 POP PEEK > > > :::::::::::::: > > > mpls_labelspace > > > :::::::::::::: > > > eth0 0 9 > > > eth1 0 8 > > > :::::::::::::: > > > mpls_out > > > :::::::::::::: > > > 0x00000002 0/0/0 1 PUSH(gen 16) SET(eth1,10.0.1.30) > > > 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth0,10.0.0.10) > > > :::::::::::::: > > > mpls_tunnel > > > :::::::::::::: > > > [root@node02 net]# ip2 route > > > 10.0.0.0/24 dev eth0 scope link > > > 10.0.1.0/24 dev eth1 scope link > > > 10.1.0.0/24 dev eth2 scope link > > > 127.0.0.0/8 dev lo scope link > > > default via 10.0.0.1 dev eth0 > > > > > > On C: > > > ===== > > > [root@node03 net]# more mpls_* > > > :::::::::::::: > > > mpls_in > > > :::::::::::::: > > > 0x40004000 0/0/0 gen 16 0 1 POP PEEK > > > :::::::::::::: > > > mpls_labelspace > > > :::::::::::::: > > > eth1 0 9 > > > :::::::::::::: > > > mpls_out > > > :::::::::::::: > > > 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth1,10.0.1.20) > > > :::::::::::::: > > > mpls_tunnel > > > :::::::::::::: > > > [root@node03 net]# ip2 route > > > 10.0.0.10 via 10.0.1.20 dev eth1 lsp 0x3 > > > 10.0.0.0/24 dev eth0 scope link > > > 10.0.1.0/24 dev eth1 scope link > > > 10.1.0.0/24 dev eth2 scope link > > > 127.0.0.0/8 dev lo scope link > > > default via 10.0.0.1 dev eth0 > > > > > > > > > > > > > > > On Tue, 10 Sep 2002, James R. Leu wrote: > > > > > > > Suggested changes inline: > > > > > > > > > > > > > > 10.0.0.10 (eth0) 10.0.1.20 (eth1) > > > > > A---------------------B---------------------C > > > > > 10.0.0.20 (eth0) 10.0.1.30 (eth1) > > > > > > > > > > On A: > > > > > ===== > > > > > mplsadm2 -vAO 0 -o push:gen:16:set:eth0:ipv4:10.0.1.30 # returns <key1> > > > > ^^^^^^^^^ > > > > 10.0.0.20? > > > > > > > > > ip2 route add 10.0.1.30/32 via 10.0.0.20 lsp <key1> > > > > > mplsadm2 -vAI gen:20:0 > > > > > mplsadm2 -vL eth0:0 > > > > > > > > > > On B: > > > > > ===== > > > > > # for LSP from A to C > > > > > mplsadm2 -vAI gen:16:0 > > > > > mplsadm2 -vAO 0 -o push:gen:16:set:eth1:ipv4:10.0.1.30 # returns <key2> > > > > > mplsadm2 -vI gen:16:0 -o <key2> -B > > > > > mplsadm2 -vL eth1:0 > > > > > > > > > > # for LSP from C to A > > > > > mplsadm2 -vAI gen:20:0 > > > > > mplsadm2 -vAO 0 -o push:gen:20:set:eth0:ipv4:10.0.0.10 # returns <key3> > > > > > mplsadm2 -vI gen:20:0 -o <key3> -B > > > > > mplsadm2 -vL eth0:0 > > > > > > > > > > On C: > > > > > ===== > > > > > mplsadm2 -vAI gen:16:0 > > > > > mplsadm2 -vAO 0 -o push:gen:20:set:eth1:ipv4:10.0.0.10 # returns <key4> > > > > ^^^^^^^^^ > > > > 10.0.1.20? > > > > > > > > > ip2 route add 10.0.0.10/32 via 10.0.1.20 lsp <key4> > > > > > mplsadm2 -vL eth1:0 > > > > > > > > Check my suggested changes. If it still doesn't work, send the contents > > > > of /proc/net/mpls_* > > > > > > > > Jim > > > > -- > > > > James R. Leu > > > > > > > > -- > > James R. Leu > > -- James R. Leu |
|
From: Wayne W. S. <ww...@ho...> - 2002-09-11 22:09:45
|
I am using v1.17. I downloaded it from sourceforge 2 days ago. On Wed, 11 Sep 2002, James R. Leu wrote: > You probably answered this for me already but what version are you using? > I thought I had this fixed. > > Jim > > On Wed, Sep 11, 2002 at 12:55:17PM -0400, Wayne W. Szeto wrote: > > > > Ok that fixes the ping problem, thank you. Now I am able to ping C from A > > and vice versa. However I notice that I can not ftp files > 1Mb along > > the estalished LSP (from A to C or C to A). Of course ftp works fine > > between A and B, and B and C. Any ideas on whats wrong? > > > > > > > > On Tue, 10 Sep 2002, James R. Leu wrote: > > > > > See comments inline: > > > > > > > > > > mpls_out > > > > :::::::::::::: > > > > 0x00000005 55/4620/0 3 PUSH(gen 16) SET(eth0,10.0.0.20) > > > ^^^^^^^ > > > means traffic was sent on this outlabel > > > > > > > 10.0.1.30 via 10.0.0.20 dev eth0 lsp 0x5 > > > ^^^ > > > looks right > > > > > > > mpls_in > > > > :::::::::::::: > > > > 0x40004000 55/4840/0 gen 16 0 56 POP PEEK > > > ^^^^^^^ ^^^^ > > > means we recv traffic No no, you want this to say FWD ... > > > > > > mplsadm2 -I gen:16:0 -O 0x2 -B > > > > > > will XC gen:16:0 to outlabel with index 0x2 > > > > > > Start with that fix. > > > > > > Jim > > > > > > > > > > 0x40005000 0/0/0 gen 20 0 1 POP PEEK > > > > :::::::::::::: > > > > mpls_labelspace > > > > :::::::::::::: > > > > eth0 0 9 > > > > eth1 0 8 > > > > :::::::::::::: > > > > mpls_out > > > > :::::::::::::: > > > > 0x00000002 0/0/0 1 PUSH(gen 16) SET(eth1,10.0.1.30) > > > > 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth0,10.0.0.10) > > > > :::::::::::::: > > > > mpls_tunnel > > > > :::::::::::::: > > > > [root@node02 net]# ip2 route > > > > 10.0.0.0/24 dev eth0 scope link > > > > 10.0.1.0/24 dev eth1 scope link > > > > 10.1.0.0/24 dev eth2 scope link > > > > 127.0.0.0/8 dev lo scope link > > > > default via 10.0.0.1 dev eth0 > > > > > > > > On C: > > > > ===== > > > > [root@node03 net]# more mpls_* > > > > :::::::::::::: > > > > mpls_in > > > > :::::::::::::: > > > > 0x40004000 0/0/0 gen 16 0 1 POP PEEK > > > > :::::::::::::: > > > > mpls_labelspace > > > > :::::::::::::: > > > > eth1 0 9 > > > > :::::::::::::: > > > > mpls_out > > > > :::::::::::::: > > > > 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth1,10.0.1.20) > > > > :::::::::::::: > > > > mpls_tunnel > > > > :::::::::::::: > > > > [root@node03 net]# ip2 route > > > > 10.0.0.10 via 10.0.1.20 dev eth1 lsp 0x3 > > > > 10.0.0.0/24 dev eth0 scope link > > > > 10.0.1.0/24 dev eth1 scope link > > > > 10.1.0.0/24 dev eth2 scope link > > > > 127.0.0.0/8 dev lo scope link > > > > default via 10.0.0.1 dev eth0 > > > > > > > > > > > > > > > > > > > > On Tue, 10 Sep 2002, James R. Leu wrote: > > > > > > > > > Suggested changes inline: > > > > > > > > > > > > > > > > > 10.0.0.10 (eth0) 10.0.1.20 (eth1) > > > > > > A---------------------B---------------------C > > > > > > 10.0.0.20 (eth0) 10.0.1.30 (eth1) > > > > > > > > > > > > On A: > > > > > > ===== > > > > > > mplsadm2 -vAO 0 -o push:gen:16:set:eth0:ipv4:10.0.1.30 # returns <key1> > > > > > ^^^^^^^^^ > > > > > 10.0.0.20? > > > > > > > > > > > ip2 route add 10.0.1.30/32 via 10.0.0.20 lsp <key1> > > > > > > mplsadm2 -vAI gen:20:0 > > > > > > mplsadm2 -vL eth0:0 > > > > > > > > > > > > On B: > > > > > > ===== > > > > > > # for LSP from A to C > > > > > > mplsadm2 -vAI gen:16:0 > > > > > > mplsadm2 -vAO 0 -o push:gen:16:set:eth1:ipv4:10.0.1.30 # returns <key2> > > > > > > mplsadm2 -vI gen:16:0 -o <key2> -B > > > > > > mplsadm2 -vL eth1:0 > > > > > > > > > > > > # for LSP from C to A > > > > > > mplsadm2 -vAI gen:20:0 > > > > > > mplsadm2 -vAO 0 -o push:gen:20:set:eth0:ipv4:10.0.0.10 # returns <key3> > > > > > > mplsadm2 -vI gen:20:0 -o <key3> -B > > > > > > mplsadm2 -vL eth0:0 > > > > > > > > > > > > On C: > > > > > > ===== > > > > > > mplsadm2 -vAI gen:16:0 > > > > > > mplsadm2 -vAO 0 -o push:gen:20:set:eth1:ipv4:10.0.0.10 # returns <key4> > > > > > ^^^^^^^^^ > > > > > 10.0.1.20? > > > > > > > > > > > ip2 route add 10.0.0.10/32 via 10.0.1.20 lsp <key4> > > > > > > mplsadm2 -vL eth1:0 > > > > > > > > > > Check my suggested changes. If it still doesn't work, send the contents > > > > > of /proc/net/mpls_* > > > > > > > > > > Jim > > > > > -- > > > > > James R. Leu > > > > > > > > > > > -- > > > James R. Leu > > > > > -- > James R. Leu > > > ------------------------------------------------------- > In remembrance > www.osdn.com/911/ > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > |
|
From: James R. L. <jl...@mi...> - 2002-09-11 22:50:00
|
OK. So the bug must still exist. What are the symptoms you see? Are there any kernel opps? My guess is that mpls-linux is dropping the frames because it thinks they are too big (>MTU). So you should see the drop counter increasing on an outlabel somewhere in the network. (in /proc/net/mpls_out their is a trio of numbers for each entry in the form 0/0/0, drops is the last number) Jim On Wed, Sep 11, 2002 at 06:09:33PM -0400, Wayne W. Szeto wrote: > I am using v1.17. I downloaded it from sourceforge 2 days ago. > > > On Wed, 11 Sep 2002, James R. Leu wrote: > > > You probably answered this for me already but what version are you using? > > I thought I had this fixed. > > > > Jim > > > > On Wed, Sep 11, 2002 at 12:55:17PM -0400, Wayne W. Szeto wrote: > > > > > > Ok that fixes the ping problem, thank you. Now I am able to ping C from A > > > and vice versa. However I notice that I can not ftp files > 1Mb along > > > the estalished LSP (from A to C or C to A). Of course ftp works fine > > > between A and B, and B and C. Any ideas on whats wrong? > > > > > > > > > > > > On Tue, 10 Sep 2002, James R. Leu wrote: > > > > > > > See comments inline: > > > > > > > > > > > > > mpls_out > > > > > :::::::::::::: > > > > > 0x00000005 55/4620/0 3 PUSH(gen 16) SET(eth0,10.0.0.20) > > > > ^^^^^^^ > > > > means traffic was sent on this outlabel > > > > > > > > > 10.0.1.30 via 10.0.0.20 dev eth0 lsp 0x5 > > > > ^^^ > > > > looks right > > > > > > > > > mpls_in > > > > > :::::::::::::: > > > > > 0x40004000 55/4840/0 gen 16 0 56 POP PEEK > > > > ^^^^^^^ ^^^^ > > > > means we recv traffic No no, you want this to say FWD ... > > > > > > > > mplsadm2 -I gen:16:0 -O 0x2 -B > > > > > > > > will XC gen:16:0 to outlabel with index 0x2 > > > > > > > > Start with that fix. > > > > > > > > Jim > > > > > > > > > > > > > 0x40005000 0/0/0 gen 20 0 1 POP PEEK > > > > > :::::::::::::: > > > > > mpls_labelspace > > > > > :::::::::::::: > > > > > eth0 0 9 > > > > > eth1 0 8 > > > > > :::::::::::::: > > > > > mpls_out > > > > > :::::::::::::: > > > > > 0x00000002 0/0/0 1 PUSH(gen 16) SET(eth1,10.0.1.30) > > > > > 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth0,10.0.0.10) > > > > > :::::::::::::: > > > > > mpls_tunnel > > > > > :::::::::::::: > > > > > [root@node02 net]# ip2 route > > > > > 10.0.0.0/24 dev eth0 scope link > > > > > 10.0.1.0/24 dev eth1 scope link > > > > > 10.1.0.0/24 dev eth2 scope link > > > > > 127.0.0.0/8 dev lo scope link > > > > > default via 10.0.0.1 dev eth0 > > > > > > > > > > On C: > > > > > ===== > > > > > [root@node03 net]# more mpls_* > > > > > :::::::::::::: > > > > > mpls_in > > > > > :::::::::::::: > > > > > 0x40004000 0/0/0 gen 16 0 1 POP PEEK > > > > > :::::::::::::: > > > > > mpls_labelspace > > > > > :::::::::::::: > > > > > eth1 0 9 > > > > > :::::::::::::: > > > > > mpls_out > > > > > :::::::::::::: > > > > > 0x00000003 0/0/0 1 PUSH(gen 20) SET(eth1,10.0.1.20) > > > > > :::::::::::::: > > > > > mpls_tunnel > > > > > :::::::::::::: > > > > > [root@node03 net]# ip2 route > > > > > 10.0.0.10 via 10.0.1.20 dev eth1 lsp 0x3 > > > > > 10.0.0.0/24 dev eth0 scope link > > > > > 10.0.1.0/24 dev eth1 scope link > > > > > 10.1.0.0/24 dev eth2 scope link > > > > > 127.0.0.0/8 dev lo scope link > > > > > default via 10.0.0.1 dev eth0 > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, 10 Sep 2002, James R. Leu wrote: > > > > > > > > > > > Suggested changes inline: > > > > > > > > > > > > > > > > > > > > 10.0.0.10 (eth0) 10.0.1.20 (eth1) > > > > > > > A---------------------B---------------------C > > > > > > > 10.0.0.20 (eth0) 10.0.1.30 (eth1) > > > > > > > > > > > > > > On A: > > > > > > > ===== > > > > > > > mplsadm2 -vAO 0 -o push:gen:16:set:eth0:ipv4:10.0.1.30 # returns <key1> > > > > > > ^^^^^^^^^ > > > > > > 10.0.0.20? > > > > > > > > > > > > > ip2 route add 10.0.1.30/32 via 10.0.0.20 lsp <key1> > > > > > > > mplsadm2 -vAI gen:20:0 > > > > > > > mplsadm2 -vL eth0:0 > > > > > > > > > > > > > > On B: > > > > > > > ===== > > > > > > > # for LSP from A to C > > > > > > > mplsadm2 -vAI gen:16:0 > > > > > > > mplsadm2 -vAO 0 -o push:gen:16:set:eth1:ipv4:10.0.1.30 # returns <key2> > > > > > > > mplsadm2 -vI gen:16:0 -o <key2> -B > > > > > > > mplsadm2 -vL eth1:0 > > > > > > > > > > > > > > # for LSP from C to A > > > > > > > mplsadm2 -vAI gen:20:0 > > > > > > > mplsadm2 -vAO 0 -o push:gen:20:set:eth0:ipv4:10.0.0.10 # returns <key3> > > > > > > > mplsadm2 -vI gen:20:0 -o <key3> -B > > > > > > > mplsadm2 -vL eth0:0 > > > > > > > > > > > > > > On C: > > > > > > > ===== > > > > > > > mplsadm2 -vAI gen:16:0 > > > > > > > mplsadm2 -vAO 0 -o push:gen:20:set:eth1:ipv4:10.0.0.10 # returns <key4> > > > > > > ^^^^^^^^^ > > > > > > 10.0.1.20? > > > > > > > > > > > > > ip2 route add 10.0.0.10/32 via 10.0.1.20 lsp <key4> > > > > > > > mplsadm2 -vL eth1:0 > > > > > > > > > > > > Check my suggested changes. If it still doesn't work, send the contents > > > > > > of /proc/net/mpls_* > > > > > > > > > > > > Jim > > > > > > -- > > > > > > James R. Leu > > > > > > > > > > > > > > -- > > > > James R. Leu > > > > > > > > -- > > James R. Leu > > > > > > ------------------------------------------------------- > > In remembrance > > www.osdn.com/911/ > > _______________________________________________ > > mpls-linux-general mailing list > > mpl...@li... > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > -- James R. Leu |
|
From: Wayne W. S. <ww...@ho...> - 2002-09-12 00:44:32
|
I checked the drop counter on the outlabels on all the machines and they are all zero. The following are from /proc/net/mpls* on each machine: On A: ===== [wwszeto@csgradpc03 net]$ more mpls_* :::::::::::::: mpls_in :::::::::::::: 0x40005000 7533/10804580/0 gen 20 0 7534 POP PEEK :::::::::::::: mpls_labelspace :::::::::::::: eth0 0 12 :::::::::::::: mpls_out :::::::::::::: 0x00000006 4126/219279/0 1 PUSH(gen 16) SET(eth0,10.0.0.20) :::::::::::::: mpls_tunnel :::::::::::::: [wwszeto@csgradpc03 net]$ ip2 route 10.0.1.30 via 10.0.0.20 dev eth0 lsp 0x6 10.0.0.0/24 dev eth0 scope link 10.0.1.0/24 dev eth2 scope link 129.97.78.0/24 dev eth1 scope link 10.1.0.0/24 dev eth3 scope link 127.0.0.0/8 dev lo scope link default dev eth1 scope link On B: ===== [root@node02 net]# more mpls* :::::::::::::: mpls_in :::::::::::::: 0x40004000 4126/235805/0 gen 16 0 1 POP FWD(0x00000002) 0x40005000 7533/10804580/0 gen 20 0 1 POP FWD(0x00000003) :::::::::::::: mpls_labelspace :::::::::::::: eth0 0 9 eth1 0 8 :::::::::::::: mpls_out :::::::::::::: 0x00000002 4126/219301/0 2 PUSH(gen 16) SET(eth1,10.0.1.30) 0x00000003 7533/10774448/0 2 PUSH(gen 20) SET(eth0,10.0.0.10) :::::::::::::: mpls_tunnel :::::::::::::: [root@node02 net]# ip2 route 10.0.0.0/24 dev eth0 scope link 10.0.1.0/24 dev eth1 scope link 10.1.0.0/24 dev eth2 scope link 127.0.0.0/8 dev lo scope link default via 10.0.0.1 dev eth0 On C: ===== [root@node03 net]# more mpls* :::::::::::::: mpls_in :::::::::::::: 0x40004000 4126/265835/0 gen 16 0 4127 POP PEEK :::::::::::::: mpls_labelspace :::::::::::::: eth1 0 9 :::::::::::::: mpls_out :::::::::::::: 0x00000003 7575/10783790/0 1 PUSH(gen 20) SET(eth1,10.0.1.20) :::::::::::::: mpls_tunnel :::::::::::::: [root@node03 net]# ip2 route 10.0.0.10 via 10.0.1.20 dev eth1 lsp 0x3 10.0.0.0/24 dev eth0 scope link 10.0.1.0/24 dev eth1 scope link 10.1.0.0/24 dev eth2 scope link 127.0.0.0/8 dev lo scope link default via 10.0.0.1 dev eth0 On Wed, 11 Sep 2002, James R. Leu wrote: > OK. So the bug must still exist. What are the symptoms you see? > Are there any kernel opps? My guess is that mpls-linux is dropping > the frames because it thinks they are too big (>MTU). So you should > see the drop counter increasing on an outlabel somewhere in the network. > (in /proc/net/mpls_out their is a trio of numbers for each entry in the > form 0/0/0, drops is the last number) > > Jim > |
|
From: James R. L. <jl...@mi...> - 2002-09-12 01:07:53
|
Hmmm. Ok lets look at /proc/net/rt_cache find the entries that match the source and dest of the ftp session. I'll need the info from both ends. Also try running the transfer with mpls kernel debugging turned on 'mplsadm2 -d' Jim On Wed, Sep 11, 2002 at 08:44:21PM -0400, Wayne W. Szeto wrote: > > I checked the drop counter on the outlabels on all the machines and they > are all zero. The following are from /proc/net/mpls* on each machine: > > > On A: > ===== > [wwszeto@csgradpc03 net]$ more mpls_* > :::::::::::::: > mpls_in > :::::::::::::: > 0x40005000 7533/10804580/0 gen 20 0 7534 POP PEEK > :::::::::::::: > mpls_labelspace > :::::::::::::: > eth0 0 12 > :::::::::::::: > mpls_out > :::::::::::::: > 0x00000006 4126/219279/0 1 PUSH(gen 16) SET(eth0,10.0.0.20) > :::::::::::::: > mpls_tunnel > :::::::::::::: > [wwszeto@csgradpc03 net]$ ip2 route > 10.0.1.30 via 10.0.0.20 dev eth0 lsp 0x6 > 10.0.0.0/24 dev eth0 scope link > 10.0.1.0/24 dev eth2 scope link > 129.97.78.0/24 dev eth1 scope link > 10.1.0.0/24 dev eth3 scope link > 127.0.0.0/8 dev lo scope link > default dev eth1 scope link > > On B: > ===== > [root@node02 net]# more mpls* > :::::::::::::: > mpls_in > :::::::::::::: > 0x40004000 4126/235805/0 gen 16 0 1 POP FWD(0x00000002) > 0x40005000 7533/10804580/0 gen 20 0 1 POP FWD(0x00000003) > :::::::::::::: > mpls_labelspace > :::::::::::::: > eth0 0 9 > eth1 0 8 > :::::::::::::: > mpls_out > :::::::::::::: > 0x00000002 4126/219301/0 2 PUSH(gen 16) SET(eth1,10.0.1.30) > 0x00000003 7533/10774448/0 2 PUSH(gen 20) SET(eth0,10.0.0.10) > :::::::::::::: > mpls_tunnel > :::::::::::::: > [root@node02 net]# ip2 route > 10.0.0.0/24 dev eth0 scope link > 10.0.1.0/24 dev eth1 scope link > 10.1.0.0/24 dev eth2 scope link > 127.0.0.0/8 dev lo scope link > default via 10.0.0.1 dev eth0 > > On C: > ===== > [root@node03 net]# more mpls* > :::::::::::::: > mpls_in > :::::::::::::: > 0x40004000 4126/265835/0 gen 16 0 4127 POP PEEK > :::::::::::::: > mpls_labelspace > :::::::::::::: > eth1 0 9 > :::::::::::::: > mpls_out > :::::::::::::: > 0x00000003 7575/10783790/0 1 PUSH(gen 20) SET(eth1,10.0.1.20) > :::::::::::::: > mpls_tunnel > :::::::::::::: > [root@node03 net]# ip2 route > 10.0.0.10 via 10.0.1.20 dev eth1 lsp 0x3 > 10.0.0.0/24 dev eth0 scope link > 10.0.1.0/24 dev eth1 scope link > 10.1.0.0/24 dev eth2 scope link > 127.0.0.0/8 dev lo scope link > default via 10.0.0.1 dev eth0 > > > On Wed, 11 Sep 2002, James R. Leu wrote: > > > OK. So the bug must still exist. What are the symptoms you see? > > Are there any kernel opps? My guess is that mpls-linux is dropping > > the frames because it thinks they are too big (>MTU). So you should > > see the drop counter increasing on an outlabel somewhere in the network. > > (in /proc/net/mpls_out their is a trio of numbers for each entry in the > > form 0/0/0, drops is the last number) > > > > Jim > > -- 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