[c-nsp] MPLS load-balancing on ME-3800X

[Tassos Chatzithomaoglou]

To correct my first email, i'm looking for ether-channel load-balancing of MPLS traffic.

The page at 
http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/12.2_52_ey/configuration/guide/swethchl.html#wp1116754 
doesn't have any reference to usage of labels.

--
Tassos


Tassos Chatzithomaoglou wrote on 5/3/2012 12:12:
> Looking for MPLS load-balancing on ME-3800X, the page 
> http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/12.2_52_ey/configuration/guide/swmpls.html 
> includes just the following note:
>
> ================================================================================
> /For information about load balancing, see this URL:
>
> http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SR/configuration/guide/pfc3mpls.html#wp1347055 
> /
> ================================================================================
>
> which leads to the following:
>
> ================================================================================
> /Basic MPLS Load Balancing
> The maximum number of load balancing paths is 8. The PFC forwards MPLS labeled packets 
> without explicit configuration. If the packet has three labels or less and the 
> underlying packet is IPv4, then the PFC uses the source and destination IPv4 address. If 
> the underlying packet is not IPv4 or more than three labels are present, the PFC parses 
> down as deep as the fifth or lowest label and uses it for hashing.
>
> MPLS Layer 2 VPN Load Balancing
> Load balancing is based on the VC label in the MPLS core if the first nibble of the MAC 
> address in the customer Ethernet frame is not 4.
> Note Load balancing is not supported at the ingress PE for Layer 2 VPNs. Load balancing 
> is done based on the VC label and it is pre-selected.
>
> MPLS Layer 3 VPN Load Balancing
> MPLS Layer 3 VPN load balancing is similar to basic MPLS load balancing. /
> ================================================================================
>
> Is this the way ME-3800X also works?
>