RP/0/RSP0/CPU0:router(config-l2vpn-bg-bd-vfi-ad-sig)# load-balancing flow-label both static
Enables load-balancing on ECMPs. Also, enables the imposition and disposition of flow labels for the pseudowire.
Step 14 Use the commit or end command.
commit - Saves the configuration changes and remains within the configuration session.
end - Prompts user to take one of these actions:
• Yes - Saves configuration changes and exits the configuration session.
• No - Exits the configuration session without committing the configuration changes.
• Cancel - Remains in the configuration mode, without committing the configuration changes.
Configuring Pseudowire Headend
The Pseudowire Headend (PWHE) is created by configuring the pw-ether main interface, pw-ether subinterface,
or pw-iw interface. The available PWHE types are pw-ether main interfaces, subinterfaces, and pw-iw
interfaces. Unless specified otherwise, the term interface is applicable for pw-ether main interfaces,
subinterfaces, and pw-iw interfaces.
The PWHE-Ethernet subinterfaces and interworking interfaces are supported from Release 5.1.1 onwards.
Note
For the PWHE to be functional, the crossconnect has to be configured completely. Configuring other Layer
3 (L3) parameters, such as VRF and IP addresses, are optional for the PWHE to be functional. However, the
L3 features are required for the Layer 3 services to be operational; that is, for PW L3 termination.
PWHE supports both IPv4 and IPv6 addresses.
This section describes these topics:
PWHE Configuration Restrictions
These configuration restrictions are applicable for PWHE:
1. The generic interface list members should be the superset of the ECMP path list to the A-PE.
2. Only eight generic interface lists are supported per A-PE neighbor address.
3. Eight Layer 3 links per generic interface list are supported.
4. Only PW-Ether interfaces can be configured as PWHE L2 or L3 subinterfaces.
5. Cross-connects that contain PW-Ether main interfaces can be configured as either VC-type 5 or VC-type
4. By default, the cross-connects are configured as VC-type 5; else by using the command—pw-class
transport-mode ethernet. To configure the cross-connects as VC-type 4, use the p2p neighbor tag-impose
vlan id and the pw-class transport-mode vlan commands.
6. Cross-connects that contain PW-Ether main interfaces that have L3 PW-Ether subinterfaces associated
with them, are supported with only VC-type 5.
7. Cross-connects that contain PW-IW interfaces are only supported with IPv4 and VC-type 11. PW-IW
interfaces are the L3 virtual interfaces used for IP interworking. To configure the cross-connect as
VC-type 11, use the interworking ipv4 command.
L2VPN and Ethernet Services Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 6.3.x
292
Implementing Multipoint Layer 2 Services
Configuring Pseudowire Headend
To Next Page
Loading...
Need help?
General
