Re: [mpls-linux-general] trouble setting up LSPs
Status: Beta
Brought to you by:
jleu
|
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 |