[c-nsp] PWHE vs BVI on Bridge Domain - l2vpn ios xr

[Luis Anzola]

Hi Aaron,

Take a look on the PWHE and BVI interface capabilities in terms of feature set (qos, sec, routing, etc) and you will probably find the answer to your question, e.g. QoS is not supported on BVI interfaces.

QoS on PWHE Interfaces:
 IPv4 and IPv6 address-families are supported.
Policy maps on both ingress and egress PW-HE. Both ingress and egress support policing, marking, and queuing within hardware limitations.
Policies at the port for the transit traffic can be applied simultaneously with policies for PWHE interfaces.
Policy is replicated on all PWHE members. This means the rate specified in the PWHE policy-map is limited to the lowest rate of all the pin down members. For example, if the PW-HE interface has both 1G and 10G pin down members, the rate is limited to 1G. if the 10G member has a shaper of 900 mbps, the rate of the PWHE interface policy is limited to 900 mbps.
Port shaping policy on the member interface will impact the PWHE traffic passing through that port.
Best regards, 

Luis

Sent from my iPhone

On Jun 6, 2013, at 5:36 PM, "Aaron" <aaron1 at gvtc.com> wrote:

> From a previous post, I got curious about PWHE since I didn't know what it
> was.
> 
> 
> 
> I looked at someone's config and read a little about it on cisco.com.
> 
> 
> 
> It seems that what I'm reading about PWHE and what I saw in a previous
> config of a previous post, I've used a construct of l2vpn, bridge group,
> bridge domain, neighbors for pw's, and bvi for L3 to accomplish a similar
> function as what someone else used with xconnect groups, p2p xconnects,
> interfacelists, and PW interface for L3
> 
> 
> 
> Why would I use one method over the other?
> 
> 
> 
> Aaron
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/