The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Re: Linux implementation of MPLS
Right Padmini. And thats what I said. You donot need to worry about labelspaces for static LSP setting. Each label is unique and it would work fine. I myself have set labelspace to 0 for all my work and everythign is working fine. But, plz donot take me for granted or authority. Try and See. I am saying what seems to be working for me. And correct me too if i am too missing a point !!!. I too am still a learner :) cheers, sudeep On Fri, 17 Sep 2004, M.V. Padmini wrote: > Hi sudeep, > > Well, we are talking of a static routing scenario here. When we alreadly > know the LSR, where where is the need to use the label space info? (well > pardon me since i have still not read the doc. completely!). Since the > labels on the LSRs are unique, there is no question of messing up. Well, > as far as the simple routing is concerned, unique label for every FEC > should work fine. May be its required in some other cases i.e. Tunnel > etc. Am not sure. The other reason could be not to run out of labels!! > > - Padmini > > >> Hi Padmini, >> We are also in the process of creating a MPLS test-bed in IITB. I >> guess >> the notion of lablespace is to identify the interface that the labels >> come from (as you have rightly said), but this concept is useful in >> processing at the hop on the basis of interfaces that it come from, >> rather than trying and identifying each and individual labels and then >> processing. Labelspaces can make some processing fast. >> >> As far as a small test-bed is considered, it doesn't make a difference >> to >> use or not to use labelspaces. >> >> I have successfully traversed ping packets using MPLS on my test-bed. >> But >> ssh and other application packets seem not to work as of now. Lets see. >> Efforts are on :) >> >> ciao, >> Sudeep >> >> >> On Fri, 17 Sep 2004, M.V. Padmini wrote: >> >>> >>> We are in the process of implementing a Test bed for MPLS using linux >>> boxes. Having gone through the mplsadm literature, they seem to be >>> using two parameters (label, labelspace) to be associated with each >>> Interface for an FEC. The labelspace is supposed to identify the >>> interface (from which it came) where the labels could be same (labels >>> coming from different interfaces). >>> >>> Is there a need to do this? If you enforce the uniqueness of the >>> label wrt to a FEC, dont u think that there is no requirement for a >>> labelspace. Am i missing something? >>> >>> Thanks in advance. >>> >>> >>>> Abhishek Mittal wrote: >>>>> 6> Fix up the MTU size >>>> >>>> After upgrading to a newer IOS on the Catalyst yesterday, I just >>>> added MPLS IP to the 12k router again --- works fine now (with 1512 >>>> as MTU on all used interfaces) ... >>>> >>>> -gg >>>> >>>> ------- >>>> The MPLS-OPS Mailing List >>>> Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml >>>> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml >>> >>> >>> ____________________________________________ >>> ERNET Project >>> Dept. of Computer Science and Engineering >>> IIT Delhi >>> New Delhi - 110 016 >>> >>> Phone: +(91)-11-2659 6009 >>> >>> >>> ------- >>> The MPLS-OPS Mailing List >>> Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml >>> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml >>> >> >> -- >> >> When a great leader's work is done, people say "we did it ourselves". >> -Tao >> >> ------- >> The MPLS-OPS Mailing List >> Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml >> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > > > ____________________________________________ > ERNET Project > Dept. of Computer Science and Engineering > IIT Delhi > New Delhi - 110 016 > > Phone: +(91)-11-2659 6009 > > > -- When a great leader's work is done, people say "we did it ourselves". -Tao ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
|
|