mpls-linux-general

[mpls-linux-general] MPLS-Linux

[Sunil K. <sun...@ho...>]

Hi,

I want to creat a Manual/Static Tunnel with following topology;


  LER A--------------------LSR------------------LER B
  172.16.10.2   172.16.10.1  172.17.10.1     172.17.10.2
                        ETH1   ETH2


- LER A & B are simulated Routers so we can't configure any mplsadm
  command on those.
- I have configured LSR as under ;


mplsadm -A -O gen:1024:eth1:ipv4:172.16.10.2

mplsadm -A -T mpls0

ifconfig mpls0 172.17.10.2 netmask 255.255.0.0

mplsadm -B -O gen:1024:eth1 -T mpls0

route add -net 172.17.0.0/16 mpls0

- Is there anything I did wrong in above configuration ? please advise the 
correct command script, if the above is not correct.

- How can I verify the Tunnel ID and the traffic going through it on
  MPLS Linux Router ? please clarify.



Thanks
Sunil




_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

[mpls-linux-general] MPLS-Linux

[Saeed A. <she...@ho...>]

Hi James,

I have been seeing the communication between you and Sunil,I have a small 
doubt i.e Can we do multiple labels swapping in the same packet ? without 
using any LDP/RSVP(I believe Yes, we can),please correct me if I am wrong.


Let's suppose we are sending MPLS labels 31,32 and 33 in packet 1 and want 
to get those labels swapped with 41,42 & 43 labels to be received at the 
destination.Then how can we configure it on MPLS-Linux ?

Hope you will guide me through this.

Thanks
Saeed






_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Re: [mpls-linux-general] MPLS-Linux

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

On Fri, Jun 22, 2001 at 04:59:54AM +0500, Saeed Akhter wrote:
> Hi James,
> 
> I have been seeing the communication between you and Sunil,I have a small 
> doubt i.e Can we do multiple labels swapping in the same packet ? without 
> using any LDP/RSVP(I believe Yes, we can),please correct me if I am wrong.
> 
> 
> Let's suppose we are sending MPLS labels 31,32 and 33 in packet 1 and want 
> to get those labels swapped with 41,42 & 43 labels to be received at the 
> destination.Then how can we configure it on MPLS-Linux ?
> 

Do you mean swapping a label stack of more then one label?
Yes this can be done, but why would you want to?  The most common
use of a label stack is for hiearchtical LSPs.  In this case only
the top label is swappedi,pushed or popped at each hop.

Take a look at:

mpls-linux/docs/README.label-intructions
mpls-linux/docs/README.hierarchy

-- 
James R. Leu

[mpls-linux-general] MPLS-Linux

[Saeed A. <she...@ho...>]

Hi Everybody,

Can anybody just verify (or correct my configuration,if I am wrong)for 
following scenerio;(LER A and LER B are simulated Routers)


LER A-----------------LSR 1-----------LSR 2---------LER B
192.168.100.3       eth1   eth2    eth0   eth1       192.168.200.3


LSR 1 eth1...192.168.100.1
LSR 1 eth2...192.168.101.1

LSR 2 eth0...192.168.101.2
LSR 2 eth1...192.168.200.1

I configured LSR 1 as under;

mplsadm -v -L eth1:0
mplsadm -v -L eth2:0

mplsadm -A -B -I gen:16:0 -O gen:26:eth2:ipv4:192.168.101.2 -f 
192.168.200.3/32

(I believe above command will swap the label 16 with 26 and will send-out 
the label 26 to 192.168.200.3 through LSR 2)

I configured LSR 2 as under;

mplsadm -v -L eth0:0
mplsadm -v -L eth1:0

mplsadm -A -B -I gen:26:0 -O gen:27:eth1:ipv4:192.168.200.3

(This command should swap label 26 with 27 and will send-out to LER B 
through LSR 2).

Please correct me if I am wrong anywhere.

Thanks
Saeed





















_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

[mpls-linux-general] Re: MPLS-Linux

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

On Sat, Jun 23, 2001 at 04:12:33AM +0500, Saeed Akhter wrote:
> Hi Everybody,
> 
> Can anybody just verify (or correct my configuration,if I am wrong)for 
> following scenerio;(LER A and LER B are simulated Routers)
> 
> 
> LER A-----------------LSR 1-----------LSR 2---------LER B
> 192.168.100.3       eth1   eth2    eth0   eth1       192.168.200.3
> 
> 
> LSR 1 eth1...192.168.100.1
> LSR 1 eth2...192.168.101.1
> 
> LSR 2 eth0...192.168.101.2
> LSR 2 eth1...192.168.200.1
> 
> I configured LSR 1 as under;
> 
> mplsadm -v -L eth1:0
> mplsadm -v -L eth2:0
> 
> mplsadm -A -B -I gen:16:0 -O gen:26:eth2:ipv4:192.168.101.2 -f 
> 192.168.200.3/32

In this senerio you do not need the -f option.  In fact mplsadm may do the
wrong thing right now

The above command line should do the following (although as I said above,
mplsadm may have a bug which prevents all of these from happening):

-create in label gen:16:0
-create out label gen:26:eth2:ipv4:192.168.101.2
-bind the in label to the out label
-bind the fec (192.168.200.3/32 to the out label)

> (I believe above command will swap the label 16 with 26 and will send-out 
> the label 26 to 192.168.200.3 through LSR 2)
> 
> I configured LSR 2 as under;
> 
> mplsadm -v -L eth0:0
> mplsadm -v -L eth1:0
> 
> mplsadm -A -B -I gen:26:0 -O gen:27:eth1:ipv4:192.168.200.3

This command line looks right.

Couple of things to note:

-This only establishes an LSP for traffic from LER A to LER B.  Traffic
 from LER B to LER A will try to go via normal routing (unless you setup
 another LSP)
-Label spaces are only required on the incoming interfaces (not on the
 interface specified in the out label) It doesn't break anything to specify
 a label space on the outgoing interferface, it is just unnecessary.

Make sure to double check you work by looking at the files /proc/net/mpls_*
to make sure the kernel has done what you told it to.

Jim
-- 
James R. Leu