Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.dcom.lans.ethernet
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion MPLS
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Stephen  
View profile  
 More options Apr 4 2012, 4:55 pm
Newsgroups: comp.dcom.lans.ethernet, comp.protocols.tcp-ip
From: Stephen <stephen_h...@xyzworld.com>
Date: Wed, 04 Apr 2012 21:55:43 +0100
Local: Wed, Apr 4 2012 4:55 pm
Subject: Re: MPLS
Print | View thread | Show original | Report this message | Find messages by this author
On Mon, 2 Apr 2012 10:31:21 -0400, "Mark"

<mark_cruzNOTFORS...@hotmail.com> wrote:
>Hello Stephen,

>thanks for your comments.

>"Stephen" <stephen_h...@xyzworld.com> wrote in message
>news:n5ben7dtdqi1bjmomj6v1j3spkvjfts2o8@4ax.com...
>> You need a way to get routes into the router (just like you would with
>> IP) - the common way is to use routing protocols since MPLS networks
>> normally are large scale.

>[skip]

>> The issue is whether the routing protocol and actual router
>> implementation you are using knows what to do to load balance traffic
>> across those paths.
>> This at least involves recognising multiple equal paths, putting more
>> than 1 into a forwarding table at the same time, and splitting the
>> traffic load across the paths.

>The one thing I'm trying to understand now is about relation between FTN,
>ILM and NHLFE -- reading rfc3031 it appears that on LSR  ILM can map an
>incoming label to a *set* of NHLFEs, that means we can have multiple
>nexthops per label.

>But can we have multiple labels per FTN entry?

never had to try, but yes.

A lot of the clever tuning in MPLS implementations is about splitting
traffic across multiple paths to a destination.

have a look at
http://www.cisco.com/en/US/tech/tk436/tk428/technologies_q_and_a_item...
https://supportforums.cisco.com/thread/344837

not much in there about the details of how it works though......

>So we have such relations:

>FTN <-> NHLFE  for un-labeled packets
>ILM <-> NHLFE  for labeled packets

>Does it make sense?

>Thanks.

>Mark

--
Regards

stephen_h...@xyzworld.com - replace xyz with ntl


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google