Information About L2VPN Over Port-Channel
The Cisco cBR-8 supports L2VPN, where the Ethernet frames from the cable modem are cross connected to a specific VLAN interface. The VLAN ID to be inserted is specified. With the L2VPN over port-channel feature, you can now support port-channel uplink interface as well as the 10 Gb uplink interface.
For the Transparent LAN Service (TLS) L2VPN, the dot1q maps contain the cable modem MAC address, the VLAN ID, and the outbound interface. Traffic received from a specific cable modem is tagged with a VLAN ID and is sent out from the uplink interface.
For the Data-over-Cable Service Interface Specifications (DOCSIS) L2VPN, cable modem (CM) configuration file holds the L2VPN encodings for both, the CM and the service flow. At the CMTS level you have to specify the default port-channel Network Side Interface (NSI). L2VPN encodings are passed by the CM to the CMTS during registration. The CMTS installs DOCSIS service flow VLAN mapping based on the information passed to it during the registration. For upstream traffic, the CMTS sends the dot1q VLAN tagged traffic out from the uplink interface. On downstream, the CMTS receives the dot1q tagged traffic from the aggregator. The CMTS replaces the VLAN header with a DOCSIS header to the corresponding service flow.
Benefits of L2VPN Over Port-Channel
By using the dot1q L2VPN, you can utilize the port-channel interface feature instead of a single 10 Gb port.
Restrictions for L2VPN Over Port-Channel
The CMTS dot1q L2VPN is designed to support traffic from customer premises equipment to the network or verse vice. For CMTS L2VPN NSI port, port-channel interface does not support VLAN redundancy.