mpls-linux-general — Mailing list for general discussion about MPLS for Linux

RE: [mpls-linux-general] MPLS/Linux talking to Cisco MPLS

[<e7...@ti...>]

Hi 
Can you help me?
See the file i've attached
Thanks
>-- Messaggio Originale --
>Reply-To: <be...@ie...>
>From: "Ben Cornish" <be...@ie...>
>To: <mpl...@li...>
>Subject: [mpls-linux-general] MPLS/Linux talking to Cisco MPLS
>Date: Thu, 19 Jun 2003 13:49:48 +1000
>
>
>
>Currently I run a large scale Cisco Based MPLS based network supporting
>multiple VPN's. We use 7206 VXR routers for the LSR/LER's
>
>We use MP-BGP and tag-switching to communicate between each LSR as this
>seems to be the only way to make it work large scale wise.
>
>On the LER we use VRF's with Route Distinguisher's to adjoin each
>interface to its corresponding VPN. This works quite affectively for us.=

>
>However we wish to use a linux box of some king and run monitoring
>software to ping each end point of the VPN of multiple VPN's on a
>regular basis.
>
>To do this I believe I have to use MPLS/Zebra/LDP-portable and the
>linux-vrf project. This will allow me to ping a remote address on each
>VPN regularly.
>
>However upon looking at this further, it seems that our cisco MPLS setup=

>now uses TDP instead of LDP, is there any support for TDP ? in the
>current mpls project ?
>
>Has anyone out there successfully interfaced a Cisco based MPLS based
>network to linux-mpls project and been able to run pings across each and=

>any of the VPN's ? or use a linux box as a LER.
>
>Any help would be very greatfull.
>
>Thanks in advance.
>
>Regards,
>Ben Cornish
>Dip.IT, RHCE
>Technical Op's Manager - iExec.com.au
>Ph 1300 659 222 - Fax  7 3871 1844
>Mobile 0417 617 204 - Direct 07 3234 9302
>Icq# 32533751
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: INetU
>Attention Web Developers & Consultants: Become An INetU Hosting Partner.=

>Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!=

>INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
>_______________________________________________
>mpls-linux-general mailing list
>mpl...@li...
>https://lists.sourceforge.net/lists/listinfo/mpls-linux-general


__________________________________________________________________
Il Numero di Accesso ad Internet sta cambiando!
Modifica subito il tuo numero di accesso con Tiscali: il nuovo 
numero e' 7023456789 oppure vai alla pagina
http://assistenza.tiscali.it/connessione/mail.html
e scarica il file di configurazione automatica.

Re: [mpls-linux-general] Unique index for in_labels

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

I knew I should have been keeping up with the LSR MIB draft.

On Thu, Jun 19, 2003 at 10:32:14AM +0200, Stefan Winter wrote:
> Hello,
> 
> according to the new draft for MPLS-LSR-STD-MIB, InSegment Labels require a 
> unique index that is not a composite of label and labelspace anymore. 
> Instead, a single index is used.
> Now, when I look into /proc/net/mpls_in, I can see a hexadecimal index in the 
> first row for InSegments that would fulfill these needs. Problem is, that 
> when adding the new InSegment, I cannot retrieve that index (as I can when 
> creating new OutSegments).
> In OutSegments, I get the index from mol_req.mol_label.u.ml_key.
> But in InSegments, mil_req.mil_label.u.ml_key would only return the _label_, 
> which is not a unique identifier. Is there any way to read the unique index 
> from somewhere within mil_req after a successful add?

No, but it will not be hard to add.  The index for the in label is a bit
field made up of the bits from the labespace, label value, and label type.
If you look at the 'mpls_key' structure in linux/net/mpls/mpls_utils.c
you will see a union, with all of the label types and a field called 'mark'.
After the different bits have been placed in thier respective pieces of the
union, you can access the entire bit field via 'mark'.  In fact this is how
the in label index is generated.  All that needs to happen is that this
index should be copied back to mpls_lable.u.ml_key.

I will work on a patch.

> 
> Greetings,
> 
> Stefan Winter
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] (no subject)

[a a <dre...@ho...>]

Hi!

I have checked the output from the commands you recommended me, and found 
some strange stuff...

#show ldp database
192.168.0.0/24  local binding:   label: gen 10000
192.168.0.0/24  remote binding: no outlabel lsr: 192.168.0.101:0

I have the following hardware setup:

    snowcrash-mpls                         pennywise-mpls
    192.168.0.101                          192.168.0.100
         |                                                |
         | eth0                                        | eth0
         +-----------------------------------------------+
                     192.168.0.0/24

How do I get the mplsd to assign an outgoing label to the other machine?
I have included my conf-files and all output from the show ... stuff.

Thanks in advance,
Andreas

>From: "James R. Leu" <jl...@mi...>
>Reply-To: jl...@mi...
>To: a a <dre...@ho...>
>CC: mpl...@li...
>Subject: Re: [mpls-linux-general] (no subject)
>Date: Tue, 17 Jun 2003 10:54:11 -0500
>
>On Tue, Jun 17, 2003 at 01:44:24PM +0200, a a wrote:
> > Hi again!
> >
> > How do I use the labels given by the zebra-ldp? I have investigated some
> > pkts with tethereal and found that the pkts are not mpls pkts...
> > Do I have to use mplsadm in order to use the lsp:s?
>
>Check the output from the 'ldp' related show commands.  From the mplsd
>command line:
>
>      show ldp discovery
>      show ldp neighbor
>      show ldp database
>
>Also look at the MPLS show commands:
>
>      show mpls forwarding
>      show mpls ftn
>
>Also, check the:
>
>     show ip route
>
>output from the zebra command line.
>
>If everything is running correctly mplsd will create the MPLS forwarding
>entites in the kernel for you and bind the LSPs to route entries.
>
> >
> > Sincerly,
> > Drew
> >
> > _________________________________________________________________
> > Hitta rätt på nätet med MSN Sök http://search.msn.se/
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: INetU
> > Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
>--
>James R. Leu
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: INetU
>Attention Web Developers & Consultants: Become An INetU Hosting Partner.
>Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
>INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
>_______________________________________________
>mpls-linux-general mailing list
>mpl...@li...
>https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

_________________________________________________________________
Hitta rätt på nätet med MSN Sök http://search.msn.se/

[mpls-linux-general] Unique index for in_labels

[Stefan W. <ma...@st...>]

Hello,

according to the new draft for MPLS-LSR-STD-MIB, InSegment Labels require a 
unique index that is not a composite of label and labelspace anymore. 
Instead, a single index is used.
Now, when I look into /proc/net/mpls_in, I can see a hexadecimal index in the 
first row for InSegments that would fulfill these needs. Problem is, that 
when adding the new InSegment, I cannot retrieve that index (as I can when 
creating new OutSegments).
In OutSegments, I get the index from mol_req.mol_label.u.ml_key.
But in InSegments, mil_req.mil_label.u.ml_key would only return the _label_, 
which is not a unique identifier. Is there any way to read the unique index 
from somewhere within mil_req after a successful add?

Greetings,

Stefan Winter

[mpls-linux-general] MPLS/Linux talking to Cisco MPLS

[Ben C. <be...@ie...>]

Currently I run a large scale Cisco Based MPLS based network supporting
multiple VPN's. We use 7206 VXR routers for the LSR/LER's

We use MP-BGP and tag-switching to communicate between each LSR as this
seems to be the only way to make it work large scale wise.

On the LER we use VRF's with Route Distinguisher's to adjoin each
interface to its corresponding VPN. This works quite affectively for us.

However we wish to use a linux box of some king and run monitoring
software to ping each end point of the VPN of multiple VPN's on a
regular basis.

To do this I believe I have to use MPLS/Zebra/LDP-portable and the
linux-vrf project. This will allow me to ping a remote address on each
VPN regularly.

However upon looking at this further, it seems that our cisco MPLS setup
now uses TDP instead of LDP, is there any support for TDP ? in the
current mpls project ?

Has anyone out there successfully interfaced a Cisco based MPLS based
network to linux-mpls project and been able to run pings across each and
any of the VPN's ? or use a linux box as a LER.

Any help would be very greatfull.

Thanks in advance.

Regards,
Ben Cornish
Dip.IT, RHCE
Technical Op's Manager - iExec.com.au
Ph 1300 659 222 - Fax  7 3871 1844
Mobile 0417 617 204 - Direct 07 3234 9302
Icq# 32533751

Re: [mpls-linux-general] Initial CVS check-ins

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

Since Dec of 2000 I have converted to using Perforce's P4 as my revision
control system.

Take a look at the 'Access to my development repository' section on:

    http://mpls-linux.sourceforge.net/

On Wed, Jun 18, 2003 at 03:56:12PM -0400, Mr. James W. Laferriere wrote:
> 	Hello James ,  The only module I can access mpls-linux .  What has
> 	happened to the others ?  I keep getting either of the two below .
> 		Tia ,  JimL
> 
> cvs -z3 -d:pserver:ano...@cv...:/cvsroot/mpls-linux co iproute2
> cvs server: cannot find module `iproute2' - ignored
> cvs [checkout aborted]: cannot expand modules
> 
> cvs -z3 -d:pserver:ano...@cv...:/cvsroot/mpls-linux co zebra
> cvs [checkout aborted]: end of file from server (consult above messages if any)
> 
> On Fri, 1 Dec 2000, James R. Leu wrote:
> > I have checked in the inital dump of all of my code base into CVS.
> > If you want to keep up with all of the changes in between releases, I suggest
> > you introduce your self to Sourceforges CVS system.
> > Goto:
> > http://sourceforge.net/projects/mpls-linux/
> > Follow the lin the bottom about the CVS Repository.  It will
> > provide you with info how to use it.
> 
> > Here are the "modules" I have created:
> >
> > iproute2		-version of the standard iproute tools which is being
> > 			 adapted to configure MPLS forwarding
> > ldp-portable		-the ldp-portable package
> > linux			-a full linux kernel with the MPLS patch applied
> > mpls-linux		-the mpls-linux package
> > zebra			-version of zerbra routing package which is being
> > 			 modified to include LDP
> >
> > NOTES:
> > -ldp-portable right now has changes that have note been test yet :-)
> > -linux and iproute2 have changes which have not yet been tested
> > -zebra is un-modified (directly from the zebra tar file)
> > Have fun :-)
> > Jim
> -- 
>        +------------------------------------------------------------------+
>        | James   W.   Laferriere | System    Techniques | Give me VMS     |
>        | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
>        | ba...@ba... | Coudersport PA 16915 |   only  on  AXP |
>        +------------------------------------------------------------------+

-- 
James R. Leu

Re: [mpls-linux-general] Initial CVS check-ins

[Mr. J. W. L. <ba...@ba...>]

	Hello James ,  The only module I can access mpls-linux .  What has
	happened to the others ?  I keep getting either of the two below .
		Tia ,  JimL

cvs -z3 -d:pserver:ano...@cv...:/cvsroot/mpls-linux co iproute2
cvs server: cannot find module `iproute2' - ignored
cvs [checkout aborted]: cannot expand modules

cvs -z3 -d:pserver:ano...@cv...:/cvsroot/mpls-linux co zebra
cvs [checkout aborted]: end of file from server (consult above messages if any)

On Fri, 1 Dec 2000, James R. Leu wrote:
> I have checked in the inital dump of all of my code base into CVS.
> If you want to keep up with all of the changes in between releases, I suggest
> you introduce your self to Sourceforges CVS system.
> Goto:
> http://sourceforge.net/projects/mpls-linux/
> Follow the lin the bottom about the CVS Repository.  It will
> provide you with info how to use it.

> Here are the "modules" I have created:
>
> iproute2		-version of the standard iproute tools which is being
> 			 adapted to configure MPLS forwarding
> ldp-portable		-the ldp-portable package
> linux			-a full linux kernel with the MPLS patch applied
> mpls-linux		-the mpls-linux package
> zebra			-version of zerbra routing package which is being
> 			 modified to include LDP
>
> NOTES:
> -ldp-portable right now has changes that have note been test yet :-)
> -linux and iproute2 have changes which have not yet been tested
> -zebra is un-modified (directly from the zebra tar file)
> Have fun :-)
> Jim
-- 
       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
       | ba...@ba... | Coudersport PA 16915 |   only  on  AXP |
       +------------------------------------------------------------------+

Re: [mpls-linux-general] Re: MPLS forwarding /IP forwarding

[Mr. J. W. L. <ba...@ba...>]

	Hello yuxiao ,  5K routes is not even close to being large .  The
	present internet routinfg table is 130K+ routes .
	Mr. Robert Olsson sent a URL to a tool he created that should
	create ~ 123954 routes .  I beleive that the table inside was
	taken from a live internet router .  See ftp url below .
		Hth ,  JimL

On Tue, 17 Jun 2003, Robert Olsson wrote:
> Date: Tue, 17 Jun 2003 19:29:25 +0200
> From: Robert Olsson <Rob...@da...>
> To: David S. Miller <da...@re...>
> Cc: Rob...@da..., si...@ne..., ra...@is...,
>      ha...@sh..., xe...@fo..., fw...@de...,
>      ne...@os..., lin...@vg...
> Subject: Re: Route cache performance tests
> David S. Miller writes:
>>  >     Internet-routing and made a script so it can be used for
>>  >     experiments. I can make it available.

>  > Please do, I'd like to play with such a list locally.

> ftp://robur.slu.se/pub/Linux/net-development/inet_routes/

> Just configure the script and run...
> And Simon can you do a run with this routing table too? And even fibstat
> output could be interesting to compare.
> Cheers.
> 						--ro

On Wed, 18 Jun 2003, yuxiao jia wrote:
> Hi James
> Since the limitation of hardware, I don't have many PC and 1000M fast
> ethernet card, But I still want emulate the large network
> I try emulate the large IP routing table in core LSR . the entries of my IP
> routing table is 5000. I expected to see the latency with IP increase, but
> MPLS no change,,
> Unfortuanly expermient show still no diffserence with or withour large IP
> table.
> is there some way to emulte the large MPLS network?
> thanks
> yuxiao

-- 
       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
       | ba...@ba... | Coudersport PA 16915 |   only  on  AXP |
       +------------------------------------------------------------------+

Re: [mpls-linux-general] diffserv in mpls

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

On Wed, Jun 18, 2003 at 07:50:51PM +0530, ashutosh wrote:
> hi,
> i want to implement diffserv in mpls.In the mpls 1.172 version diffserv is 
> implemented but I am not able to understand where it is implemented.Also what 
> is the use of the functions mpls_in_op_set_tc, mpls_in_op_set_exp, 
> mpls_in_op_set_ds,etc.?what for are these functions used?And how do i 
> implement diffserv in mpls?
> ashutosh

At what level are you trying to implement this?  Are you trying to setup
static LSPs (E or L?) which have the correct PHB based on DSCP?  Are you
looking to do this via a signaling protocol?

The forwarding plane implementation contains everything you need to
setup static LSPs that have the correct PHB based on DSCP.  If you
are looking to do this via a signaling protocol, check out:

    http://dsmpls.atlantis.rug.ac.be/

> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] Re: MPLS forwarding /IP forwarding

[yuxiao j. <yx...@si...>]

Hi James

Since the limitation of hardware, I don't have many PC and 1000M fast
ethernet card, But I still want emulate the large network

I try emulate the large IP routing table in core LSR . the entries of my IP
routing table is 5000. I expected to see the latency with IP increase, but
MPLS no change,,

Unfortuanly expermient show still no diffserence with or withour large IP
table.

is there some way to emulte the large MPLS network?

thanks

yuxiao


----- Original Message -----
From: "James R. Leu" <jl...@mi...>
To: "yuxiao jia" <yx...@si...>
Cc: <mpl...@li...>
Sent: Tuesday, June 17, 2003 7:22 PM
Subject: Re: [mpls-linux-general] Re: MPLS forwarding /IP forwarding


> You will be hard pressed to notice latency variation in such a small
> network, no matter what protocol you use.  Try measuring throughput
> instead.  Also, as I said in my previous e-mail, as soon as you introduce
> a LER (ingress or egress) into your throughput test, you will see a
> decrease in performance compared to IP only.  For you to see the benifits
> or MPLS forwarding (with respect to throughput measured on the LSR).  You
> will have to have many LERs connected to your LSR(s).
>
> For example:
>
> iL = ingress LER
>
>              100Mbps                 1000Mbps
>
>        iL1-----.
>                 \
>        iL2-----. \     ------------            -----------
>        .        \ `---|            |          |           |
>        .         `----|   LSR 1    |----------|  LSR 2    |
>        .         .----|            |          |           |
>        .        / .---|            |          |           |
>        iL(N-1)-. /     ------------            -----------
>                 /
>        iL(N)---`
>
> In this case if each ingress LER generated 100Mbps of labeled traffic
> you should see N*100 Mbps of traffic on the core link (where N is < 10).
> Typically IP forwarding on Linux will top out at about 600Mbp (depending
> on the packet size).
>
> On Tue, Jun 17, 2003 at 05:09:40PM -0400, yuxiao jia wrote:
> > hello James
> >
> > I measure per node delay in MPLS network (and corresponding IP network).
> > Toplolgy:  Ingress- Core---Egress
> >
> > The way I did is use external PC with two interafce connect to router ,
> > running tcpdump for capure IP forwarding, runing ethereal/tethereal to
> > caputer MPLS packet.
> >
> > ------router -------
> >     |               |
> >       analyser
> >
> > based on same packet ID, I calculate the differenc between incoming
timstamp
> > and outgoing timestamp. I believe the per node delay what I got is =
> > forarding +queusing delay+ transimiiton delay
> >
> >
> >
> > ----- Original Message -----
> > From: "James R. Leu" <jl...@mi...>
> > To: "yuxiao jia" <yx...@si...>
> > Sent: Tuesday, June 17, 2003 6:43 PM
> > Subject: Re: MPLS forwarding /IP forwarding
> >
> >
> > > The MPLS forwarding mechanism in mpls-linux is _not_ based on IP
> > forwarding.
> > > I believe Pim was refering to ingress and egress LER functionallity.
> > > In those cases it is expect that the forwarding will be slower then
> > > just straight IP because both IP and MPLS lookups need to occur (this
> > > case, but it hasn't).
> >
> > what does you meane "can be optimized in the egress LER  case"?
> >
> >
> > > As far as LSR forwarding being not being faster then IP, I would have
to
> > > look at your methodology for testing.  Are you measuring only latency?
> > > Or total throughput?  It has been a while since I've done any sort of
> > > erformance comparison, put last time performace testing was done, LSR
> > > forwarding was able to achive more throughput them IP forwarding.
> > I measure latency, how to measure total throuhput? can y give me some
ideas
> >
> > > In addition, the existance of mpls-linux is _not_ to provide a faster
> > > means of forwarding packets, it is meant to be a tool for people to
learn
> > > about MPLS.  To that end, if you really want to understand MPLS
> > > forwarding, look at the code.
> > >
> > > On Tue, Jun 17, 2003 at 04:35:03PM -0400, yuxiao jia wrote:
> > > > Hello Jame
> > >
> > > James not Jame.
> > >
> > > >
> > > > I am working the Linux testbed based on "RSVP-TE for MPLS diffserv"
> > > >
> > > > I want compare MPLS forwarding and normal IP forwarding perfomace.
The
> > topology is
> > > >
> > > >
> > > > -----Ingress -----Core ----10M -----Egress----  (other part is 100M)
> > > >
> > > > I measure the each router per node delay by using extrenal anlyaer.
the
> > result show
> > > >
> > > > on Ingress, since MPLS stack over head, the delay of MPLS > IP
> > > > on Core,  delay of MPLS almost = delay of IP ( I expected the MPLS
> > should fast then IP, since label swictc)
> > > > on Egress, delay of MPLS a liitle big , almost same =IP..
> > > >
> > > > I try figure out why on Core mpls forwarding not fast, I email Pim,
he
> > said under linux , MPLS forwarding is based on IP forwarding (since time
> > cosuming and error prone if withou IP forwarding)
> > > >
> > > > This is why I want ask you question
> > > >
> > > > 1) why in your mpls implemntaio, based on IP forawrding, does it do
IP
> > table look up?
> > > > 2) How much involved in IP forwarding when implement MPLS
forwarding.?
> > > > 3) if I emulete a lager IP routing table, can i get mpls fast than
IP?
> > > >
> > > > thanks
> > > >
> > > > yuxiao
> > > >
> > > >
> > >
> > > --
> > > James R. Leu
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: INetU
> > Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
> --
> James R. Leu
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

Re: [mpls-linux-general] diffserv in mpls

[yuxiao j. <yx...@si...>]

Hi

Check this web site
http://dsmpls.atlantis.rug.ac.be/


----- Original Message -----
From: "ashutosh" <ash...@co...>
To: <mpl...@li...>
Sent: Wednesday, June 18, 2003 10:20 AM
Subject: [mpls-linux-general] diffserv in mpls


> hi,
> i want to implement diffserv in mpls.In the mpls 1.172 version diffserv is
> implemented but I am not able to understand where it is implemented.Also
what
> is the use of the functions mpls_in_op_set_tc, mpls_in_op_set_exp,
> mpls_in_op_set_ds,etc.?what for are these functions used?And how do i
> implement diffserv in mpls?
> ashutosh
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

[mpls-linux-general] diffserv in mpls

[ashutosh <ash...@co...>]

hi,
i want to implement diffserv in mpls.In the mpls 1.172 version diffserv i=
s=20
implemented but I am not able to understand where it is implemented.Also =
what=20
is the use of the functions mpls_in_op_set_tc, mpls_in_op_set_exp,=20
mpls_in_op_set_ds,etc.?what for are these functions used?And how do i=20
implement diffserv in mpls?
ashutosh

Re: [mpls-linux-general] Re: MPLS forwarding /IP forwarding

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

You will be hard pressed to notice latency variation in such a small
network, no matter what protocol you use.  Try measuring throughput
instead.  Also, as I said in my previous e-mail, as soon as you introduce
a LER (ingress or egress) into your throughput test, you will see a
decrease in performance compared to IP only.  For you to see the benifits
or MPLS forwarding (with respect to throughput measured on the LSR).  You
will have to have many LERs connected to your LSR(s).

For example:

iL = ingress LER

             100Mbps                 1000Mbps

       iL1-----.
                \
       iL2-----. \     ------------            -----------
       .        \ `---|            |          |           |
       .         `----|   LSR 1    |----------|  LSR 2    |
       .         .----|            |          |           |
       .        / .---|            |          |           |
       iL(N-1)-. /     ------------            -----------
                /
       iL(N)---`

In this case if each ingress LER generated 100Mbps of labeled traffic
you should see N*100 Mbps of traffic on the core link (where N is < 10).
Typically IP forwarding on Linux will top out at about 600Mbp (depending
on the packet size).

On Tue, Jun 17, 2003 at 05:09:40PM -0400, yuxiao jia wrote:
> hello James
> 
> I measure per node delay in MPLS network (and corresponding IP network).
> Toplolgy:  Ingress- Core---Egress
> 
> The way I did is use external PC with two interafce connect to router ,
> running tcpdump for capure IP forwarding, runing ethereal/tethereal to
> caputer MPLS packet.
> 
> ------router -------
>     |               |
>       analyser
> 
> based on same packet ID, I calculate the differenc between incoming timstamp
> and outgoing timestamp. I believe the per node delay what I got is =
> forarding +queusing delay+ transimiiton delay
> 
> 
> 
> ----- Original Message -----
> From: "James R. Leu" <jl...@mi...>
> To: "yuxiao jia" <yx...@si...>
> Sent: Tuesday, June 17, 2003 6:43 PM
> Subject: Re: MPLS forwarding /IP forwarding
> 
> 
> > The MPLS forwarding mechanism in mpls-linux is _not_ based on IP
> forwarding.
> > I believe Pim was refering to ingress and egress LER functionallity.
> > In those cases it is expect that the forwarding will be slower then
> > just straight IP because both IP and MPLS lookups need to occur (this
> > case, but it hasn't).
> 
> what does you meane "can be optimized in the egress LER  case"?
> 
> 
> > As far as LSR forwarding being not being faster then IP, I would have to
> > look at your methodology for testing.  Are you measuring only latency?
> > Or total throughput?  It has been a while since I've done any sort of
> > erformance comparison, put last time performace testing was done, LSR
> > forwarding was able to achive more throughput them IP forwarding.
> I measure latency, how to measure total throuhput? can y give me some ideas
> 
> > In addition, the existance of mpls-linux is _not_ to provide a faster
> > means of forwarding packets, it is meant to be a tool for people to learn
> > about MPLS.  To that end, if you really want to understand MPLS
> > forwarding, look at the code.
> >
> > On Tue, Jun 17, 2003 at 04:35:03PM -0400, yuxiao jia wrote:
> > > Hello Jame
> >
> > James not Jame.
> >
> > >
> > > I am working the Linux testbed based on "RSVP-TE for MPLS diffserv"
> > >
> > > I want compare MPLS forwarding and normal IP forwarding perfomace. The
> topology is
> > >
> > >
> > > -----Ingress -----Core ----10M -----Egress----  (other part is 100M)
> > >
> > > I measure the each router per node delay by using extrenal anlyaer. the
> result show
> > >
> > > on Ingress, since MPLS stack over head, the delay of MPLS > IP
> > > on Core,  delay of MPLS almost = delay of IP ( I expected the MPLS
> should fast then IP, since label swictc)
> > > on Egress, delay of MPLS a liitle big , almost same =IP..
> > >
> > > I try figure out why on Core mpls forwarding not fast, I email Pim, he
> said under linux , MPLS forwarding is based on IP forwarding (since time
> cosuming and error prone if withou IP forwarding)
> > >
> > > This is why I want ask you question
> > >
> > > 1) why in your mpls implemntaio, based on IP forawrding, does it do IP
> table look up?
> > > 2) How much involved in IP forwarding when implement MPLS forwarding.?
> > > 3) if I emulete a lager IP routing table, can i get mpls fast than IP?
> > >
> > > thanks
> > >
> > > yuxiao
> > >
> > >
> >
> > --
> > James R. Leu
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] Re: MPLS forwarding /IP forwarding

[yuxiao j. <yx...@si...>]

hello James

I measure per node delay in MPLS network (and corresponding IP network).
Toplolgy:  Ingress- Core---Egress

The way I did is use external PC with two interafce connect to router ,
running tcpdump for capure IP forwarding, runing ethereal/tethereal to
caputer MPLS packet.

------router -------
    |               |
      analyser

based on same packet ID, I calculate the differenc between incoming timstamp
and outgoing timestamp. I believe the per node delay what I got is =
forarding +queusing delay+ transimiiton delay



----- Original Message -----
From: "James R. Leu" <jl...@mi...>
To: "yuxiao jia" <yx...@si...>
Sent: Tuesday, June 17, 2003 6:43 PM
Subject: Re: MPLS forwarding /IP forwarding


> The MPLS forwarding mechanism in mpls-linux is _not_ based on IP
forwarding.
> I believe Pim was refering to ingress and egress LER functionallity.
> In those cases it is expect that the forwarding will be slower then
> just straight IP because both IP and MPLS lookups need to occur (this
> case, but it hasn't).

what does you meane "can be optimized in the egress LER  case"?


> As far as LSR forwarding being not being faster then IP, I would have to
> look at your methodology for testing.  Are you measuring only latency?
> Or total throughput?  It has been a while since I've done any sort of
> erformance comparison, put last time performace testing was done, LSR
> forwarding was able to achive more throughput them IP forwarding.
I measure latency, how to measure total throuhput? can y give me some ideas

> In addition, the existance of mpls-linux is _not_ to provide a faster
> means of forwarding packets, it is meant to be a tool for people to learn
> about MPLS.  To that end, if you really want to understand MPLS
> forwarding, look at the code.
>
> On Tue, Jun 17, 2003 at 04:35:03PM -0400, yuxiao jia wrote:
> > Hello Jame
>
> James not Jame.
>
> >
> > I am working the Linux testbed based on "RSVP-TE for MPLS diffserv"
> >
> > I want compare MPLS forwarding and normal IP forwarding perfomace. The
topology is
> >
> >
> > -----Ingress -----Core ----10M -----Egress----  (other part is 100M)
> >
> > I measure the each router per node delay by using extrenal anlyaer. the
result show
> >
> > on Ingress, since MPLS stack over head, the delay of MPLS > IP
> > on Core,  delay of MPLS almost = delay of IP ( I expected the MPLS
should fast then IP, since label swictc)
> > on Egress, delay of MPLS a liitle big , almost same =IP..
> >
> > I try figure out why on Core mpls forwarding not fast, I email Pim, he
said under linux , MPLS forwarding is based on IP forwarding (since time
cosuming and error prone if withou IP forwarding)
> >
> > This is why I want ask you question
> >
> > 1) why in your mpls implemntaio, based on IP forawrding, does it do IP
table look up?
> > 2) How much involved in IP forwarding when implement MPLS forwarding.?
> > 3) if I emulete a lager IP routing table, can i get mpls fast than IP?
> >
> > thanks
> >
> > yuxiao
> >
> >
>
> --
> James R. Leu

[mpls-linux-general] MPLS forwarding/IP forwarding

[yuxiao j. <yx...@si...>]

Hello Jame

I am working the Linux testbed based on "RSVP-TE for MPLS diffserv" =
project

I want compare MPLS forwarding and normal IP forwarding perfomace. The =
topology is


-----Ingress -----Core ----10M -----Egress----  (other part is 100M)

I measure the each router per node delay by using external anlyaer =
(tcpdump/tethereal). the result show

on Ingress, since MPLS stack over head, the delay of MPLS > IP
on Core,  delay of MPLS almost =3D delay of IP ( I expected the MPLS =
should fast then IP, since label swictc)
on Egress, delay of MPLS a liitle big , almost same =3DIP..

I try figure out why on Core mpls forwarding not fast, I email Pim, he =
said under linux , MPLS forwarding is based on IP forwarding (since time =
cosuming and error prone if without IP forwarding)

This is why I want ask you question

1) why in your mpls implemntaio, based on IP forawrding, does it do IP =
table look up?
2) How much involved in IP forwarding when implement MPLS forwarding.?
3) if I emulete a lager IP routing table, can i get mpls fast than IP?

thanks

yuxiao

Re: [mpls-linux-general] (no subject)

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

On Tue, Jun 17, 2003 at 01:44:24PM +0200, a a wrote:
> Hi again!
>=20
> How do I use the labels given by the zebra-ldp? I have investigated som=
e=20
> pkts with tethereal and found that the pkts are not mpls pkts...
> Do I have to use mplsadm in order to use the lsp:s?

Check the output from the 'ldp' related show commands.  From the mplsd
command line:

     show ldp discovery
     show ldp neighbor
     show ldp database

Also look at the MPLS show commands:

     show mpls forwarding
     show mpls ftn

Also, check the:

    show ip route

output from the zebra command line.

If everything is running correctly mplsd will create the MPLS forwarding
entites in the kernel for you and bind the LSPs to route entries.

>=20
> Sincerly,
> Drew
>=20
> _________________________________________________________________
> Hitta r=E4tt p=E5 n=E4tet med MSN S=F6k http://search.msn.se/
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission=
!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

--=20
James R. Leu

[mpls-linux-general] (no subject)

[a a <dre...@ho...>]

Hi again!

How do I use the labels given by the zebra-ldp? I have investigated some 
pkts with tethereal and found that the pkts are not mpls pkts...
Do I have to use mplsadm in order to use the lsp:s?

Sincerly,
Drew

_________________________________________________________________
Hitta rätt på nätet med MSN Sök http://search.msn.se/

Re: [mpls-linux-general] about mpls-linux 1.172

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

On Thu, Jun 12, 2003 at 11:22:09AM +0800, ste...@so... wrote:
> Hi jleu:
>   I read the souce code about the mpls-linux 1.172,and find the code is something confused.
>   eg:mpls_add_out_label(out) function is to add a new NHLFE, according souce in this function, the input parameter out is useless,anything I input use mplsadmin -O option is not workable.

What is the exact command line you are using?  Check out the example
I just posted to the http://mpls-linux.sf.net web page.

>   I get the CVS reposity's lastest new source, it's sound reasonable.
>   I was confused the relation about 1.172 release and current cvs code.

Read the section "Access to my development repository" over at:
http://mpls-linux.sf.net

> 
> thx
> 
> stevens yin  
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by: eBay
> Great deals on office technology -- on eBay now! Click here:
> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] about mpls-linux 1.172

[<ste...@so...>]

Hi jleu:
  I read the souce code about the mpls-linux 1.172,and find the code is something confused.
  eg:mpls_add_out_label(out) function is to add a new NHLFE, according souce in this function, the input parameter out is useless,anything I input use mplsadmin -O option is not workable.
  I get the CVS reposity's lastest new source, it's sound reasonable.
  I was confused the relation about 1.172 release and current cvs code.

thx

stevens yin  

[mpls-linux-general] strange ethernet header...

[a a <dre...@ho...>]

Hi!

As I start to dig into mpls I have found some strange stuff... I have set up 
a couple of MPLS machines and observes the traffic between these. As I start 
to look at the ethernet-frame I see that there is some strange 
protocol-values.

The strange stuff that I find are the following:
0x2020 and 0x6920

Can anyone tell me what kind of pkt these are? I have been trying to find an 
rfc where the ethernet-frame-protocols are descussed, but haven't found 
anything. :(

Thanks!
Drew

_________________________________________________________________
Hitta rätt på nätet med MSN Sök http://search.msn.se/

Re: [mpls-linux-general] Layer 2 virtual circuit

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

Take a look at my 'perforce' development tree (see http://mpls-linux.sf.net/
for more info).  You can check out l2cc-kernel and get the lastest
incarnation of this work.  It is lacking a userland utility (I was in
the midst of writing it, then got distracted by my day job, and have never
had a chance to get back to it).  It should be pretty trivial to add
the required functionalty to the l2ccadm utiliy in l2cc-linux.

On Thu, Jun 05, 2003 at 11:44:04AM -0700, Chen Allan wrote:
> Hi James Leu,
>  
>    I read from the mailing archive that you mentioned about
> a patch for the layer 2 virtual circuit forwarding plane. I'm 
> interested in the patch even if the ldp signalling part is not ready yet.
> Could you give some pointers?
> Thanks a lot!
>  
> Allan 
> 
> 
> ---------------------------------
> Do you Yahoo!?
> Free online calendar with sync to Outlook(TM).
-- 
James R. Leu

[mpls-linux-general] Layer 2 virtual circuit

[Chen A. <all...@ya...>]

Hi James Leu,
 
   I read from the mailing archive that you mentioned about
a patch for the layer 2 virtual circuit forwarding plane. I'm 
interested in the patch even if the ldp signalling part is not ready yet.
Could you give some pointers?
Thanks a lot!
 
Allan 


---------------------------------
Do you Yahoo!?
Free online calendar with sync to Outlook(TM).

Re: [mpls-linux-general] about zebra ldp patch

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

On Wed, Jun 04, 2003 at 06:10:52PM +0800, stevens yin wrote:
> I get the source code by cvs, find the LDP source code is not use any zebra 
> api.
> and in cvs had some attic directory look like about zebra.

The ldp-portable code is designed to be portable.  It relies on a 'porting
layer'.  The zebra-ldp porting layer interacts with zebra.  You will find
this in the diff file zebra-ldp.diff.  Read README.zebra-ldp for more
information.

> how can i get a zebra-ldp patch ? only the diff file.
> what about the status of zebra and ldp relations?

To get the most recent version get the code from my 'perforce' tree (not CVS).
Take a look at http://mpls-linux.sf.net/ for more info.

> 
> stevens yin
> 
> _________________________________________________________________
> Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
> http://join.msn.com/?page=features/featuredemail
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] about zebra ldp patch

[stevens y. <ste...@ms...>]

I get the source code by cvs, find the LDP source code is not use any zebra 
api.
and in cvs had some attic directory look like about zebra.

how can i get a zebra-ldp patch ? only the diff file.
what about the status of zebra and ldp relations?


stevens yin

_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail

[mpls-linux-general] L2CC

[Chen A. <all...@ya...>]

Hi James Leu,
 
   I read in one of the emails you sent to the mailing group that there's a patch
for the forwarding plane supporting L2CC. Is it available for download? 
Thanks a lot.
 
Allan


---------------------------------
Do you Yahoo!?
Free online calendar with sync to Outlook(TM).