Re: [mpls-linux-general] activate label
Status: Beta
Brought to you by:
jleu
|
From: sanjeev r. <san...@li...> - 2005-01-26 06:34:26
|
Thank you for ur response James, Things are fine now... Im going ahead.. However, I would like to clarify one thing----- Is MPLS Linux 1.172 kernel = patch supports Linux QoS? Thanks in advance... With best regards, Sanjeev R ----- Original Message ----- From: "James R. Leu" <jl...@mi...> To: "sanjeev ravindran" <san...@li...> Subject: Re: [mpls-linux-general] activate label Date: Sun, 23 Jan 2005 09:21:02 -0600 >=20 > On Sun, Jan 23, 2005 at 03:39:47PM +0800, sanjeev ravindran wrote: > > Thanks a lot for ur detailed explination James, > > > > Things are much clearer now... However, I have one more doubt=20 > > regarding the same condition in a transit router.. > > In a transit router, suppose if I bind an incoming label with an=20 > > outgoing label, traffic is activated right? In this scenario, if=20 > > I want to inactivate the traffic flow, still want to maintain the=20 > > incoming-outgoing label binding, is there any way? This=20 > > requirement will arise if i want to have multiple=20 > > icoming-outgoing label bindings but still only one is active...=20 > > Im not very sure if this is required by RSVP-TE.. Im slowly=20 > > getting hold of it... >=20 > You are correct that traffic _could_ flow on that LSP, but for that to ha= ppen > the ingress LER would have to have mapped map traffic on to it, which tak= es > us back to the previous email :-) So in general the Ingress LER is the > only one that has to worry about 'activating' a LSP. >=20 >=20 > > > > With best regards, > > Sanjeev R. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > From: "James R. Leu" <jl...@mi...> > > To: "sanjeev ravindran" <san...@li...> > > Subject: Re: [mpls-linux-general] activate label > > Date: Fri, 21 Jan 2005 08:26:30 -0600 > > > > > > On Fri, Jan 21, 2005 at 04:26:33PM +0800, sanjeev ravindran wrote: > > > > Thank you so much for ur response James, > > > > As you explained, RSVPTE can have back up LSPs. And currently=20 > > all > > the backup LSPs also will be installed in the forwarding=20 > > plane. > > But in my perspective, this doesnt serve the actual=20 > > purpose.. A > > back up LSP needs to be enabled only when the=20 > > primary LSP fails.. > > In this scenario, there needs to be some=20 > > mechanism where we can > > bind a label and activate it later=20 > > for LSPs. Im not sure if this > > is a valid point... This is=20 > > what I feel... > > > > One this to remember is that installing the LSP into the forwarding= plan > > > and mapping traffic to it are two different steps. For example I can > > > create 2 LSPs, but only map traffic to one of them. So for all inten= ts and > > > purposes the 2nd LSP is not used for anything. Only when I maps traf= fic to > > > it will it be used. > > > > MPLS Linux provides 3 mechanisms for mapping traffic to a LSP: > > > -spec_nh system which allow IPv4 or IPv6 routes to be mapped to a LSP > > > -MPLS tunnel interface represents a LSP as a logical interface. > > > The interface can be configured to appear as a PtP interface connec= ted > > > to the egress LER > > > -spec_nh system can be used in combination with iptables (netfilter) = to > > > map and/or mark specific traffic that will traverse a LSP. > > > > Here is an example of how you could use a MPLS tunnel interface to > > > facilitate a primary/backup situation. > > > > An ingress LER uses RSVP-TE to signal 2 LSPs which terminate on the= same > > > egress LER, but take two seperate paths through the network. These L= SPs > > > will be used for for a primary/backup senerio. The ingress LER uses a > > > MPLS tunnel interface to map traffic to the primary LSP. It configur= ed > > > the MPLS tunnel interface to look like a PtP connection to the egress= LER. > > > At this point traffic destined to the egress LER used the primary LSP. > > > No traffic will traverse the backup LSP. > > > > If/when the primary LSP breaks, RSVP-TE will receive a path-tear fo= r the > > > primary LSP. At that time it will trigger the ingress LER to modify = the > > > MPLS tunnel interface and detattach the primary LSP from the MPLS tun= nel > > > interface and attach the backup LSP to the MPLS tunnel interface (the > > > process of modifing a MPLS tunnel interface to move from one LSP to a= nother > > > takes just one system call). At that point traffic destined to the e= gress > > > LER uses the backup LSP. No traffic will attempt to traverse=20 > > the primary LSP. > > > > Let me know if this will suit your needs or if you still require mo= re > > > functionality. > > > > > With best regards, > > > > Sanjeev R > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > From: "James R. Leu" <jl...@mi...> > > > > To: "sanjeev ravindran" <san...@li...> > > > > Subject: Re: [mpls-linux-general] activate label > > > > Date: Thu, 20 Jan 2005 23:14:38 -0600 > > > > > > > > > > On Thu, Jan 20, 2005 at 06:34:12PM +0800, sanjeev ravindran wro= te: > > > > > > Thank you for ur response James, > > > > > > > > > > > > Ur explanation cleared my doubts regarding the activation=20 > > of > > > > labels.. However, i would like to know if the LSP will=20 > > be > > > > activated [I mean to say traffic will be forwared]=20 > > when label > > > > binding[installation in to the forwarding=20 > > plane] is done at the > > > > switch level. > > > > > > Or is there any way i can bind the label at the switch=20 > > level > > but > > still keep it inactive? and i can activate it=20 > > to forward > > traffic > > at a later time? > > > > > > MPLS linux does not currently implement admin status on=20 > > each > > MPLS segment. > > > > > Up till now, I've not seen a need to. I'd be open to implementing= it, > > > > > provided there is a valid application for it. > > > > > > > Thanks in advance... > > > > > > With best regards, > > > > > > Sanjeev R > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "James R. Leu" <jl...@mi...> > > > > > > To: rameshv <ram...@wi...> > > > > > > Subject: Re: [mpls-linux-general] activate label > > > > > > Date: Wed, 19 Jan 2005 09:08:50 -0600 > > > > > > > > > > > > > > On Wed, Jan 19, 2005 at 04:20:50PM +0530, rameshv wrote: > > > > > > > > hi, > > > > > > > > > > > > > > > > what is meant by activating label, active connection,=20 > > > > backup connection ? > > > > > > > > I believe you are referring to the difference between=20 > > allocating and > > > > > > > activating. Allocation is done in the signaling layer. Typi= cally > > > > > > > activation of a label means to install it into the > >=20 > > forwarding plane. For > > > > > > > example RSVP-TE could signal a backup LSP, meaning=20 > > allocate > > and distribute > > > > > > > labels for the LSP, but it would only install the=20 > > labels > > into > > the forwarding > > > > > > > plane (activate) when the primary LSP fails. > > > > > > > > (note that the above is a contrived example, all=20 > > deployed > > implementations > > > > > > > of RSVP-TE that signal backup LSPs install them into >=20 > > > forwarding plane prior > > > > > > > to the failure of the primary LSP) > > > > > > > > > any help is appreciated > > > > > > > > > > > > > > > > regards > > > > > > > > ramesh > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > > The SF.Net email is sponsored by: Beat the post-holiday blu= es > > > > > > > > Get a FREE limited edition SourceForge.net t-shirt=20 > > from ThinkGeek. > > > > > > > > It's fun and FREE -- well,=20 > > almost....http://www.thinkgeek.com/sfshirt > > > > > > > > _______________________________________________ > > > > > > > > mpls-linux-general mailing list > > > > > > > > mpl...@li... > > > > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-gen= eral > > > > > > > > -- > > > > > > > James R. Leu > > > > > > > jl...@mi... > > > > > > > > > ------------------------------------------------------- > > > > > > > The SF.Net email is sponsored by: Beat the post-holiday blues > > > > > > > Get a FREE limited edition SourceForge.net t-shirt from Think= Geek. > > > > > > > It's fun and FREE -- well,=20 > > almost....http://www.thinkgeek.com/sfshirt > > > > > > > _______________________________________________ > > > > > > > mpls-linux-general mailing list > > > > > > > mpl...@li... > > > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-gener= al > > > > > > > > > > > > -- ______________________________________________ > > > > > > Check out the latest SMS services @=20 > > http://www.linuxmail.org > > This > > allows you to send and=20 > > receive SMS through your mailbox. > > > > > > > > > > > > > > > > > > Powered by Outblaze > > > > > > -- > > > > > James R. Leu > > > > > jl...@mi... > > > > > > > ------------------------------------------------------- > > > > > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Rep= orting > > > > > Tool for open source databases. Create drag-&-drop reports. Save = time > > > > > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF,= etc. > > > > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > > > > > _______________________________________________ > > > > > mpls-linux-general mailing list > > > > > mpl...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > > > > > > -- ______________________________________________ > > > > Check out the latest SMS services @ http://www.linuxmail.org=20 > > This > > allows you to send and receive SMS through your mailbox. > > > > > > > > > > > > Powered by Outblaze > > > > -- > > > James R. Leu > > > jl...@mi... > > > > -- ______________________________________________ > > Check out the latest SMS services @ http://www.linuxmail.org This=20 > > allows you to send and receive SMS through your mailbox. > > > > > > Powered by Outblaze >=20 > -- > James R. Leu > jl...@mi... --=20 ______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org=20 This allows you to send and receive SMS through your mailbox. Powered by Outblaze |