Chapter 43: BSoD L2VPN
STANDARD Revision 1.0 C4® CMTS Release 8.3 User Guide
© 2016 ARRIS Enterprises LLC. All Rights Reserved. 1087
BSoD L2VPN Configuration via CLI
This feature is meant to serve the needs of operators who want to use CMs for L2VPN tunneling, but for whatever reason
cannot use the CM configuration file to create the L2VPN. This would be the case, for example, if the MSO’s back office
provisioning system does not support the TLVs needed for L2VPN configuration. For such cases, this feature provides a set
of CLI commands and MIBs simulate the L2VPN TLVs needed to add these CMs to the tunnel.
When an L2VPN modem registers with a CM config file, the provisioned data includes a VPNID, Q-tag values (single or
double), and ESAFE MAC addresses. Since the L2VPN configuration information is not provided by the registration file, the
information needs to be provisioned for each CM requiring the service. The format and function of these fields is similar to
the information defined by the TLVs used in the CM configuration files of the regular L2VPN feature.
The l2vpnid <vpnid> parameter serves the same function as the VPNID TLV. It is used to logically group the display of
multiple L2VPNs. The value of this parameter is displayed by the CLI show commands.
The Q-tags (single or dual) are the values used to encapsulate packets within a L2VPN.
The ESAFE MAC addresses are used to specify which devices behind the CM should not be included in the tunnel.
When a modem is configured for L2VPN via CLI, all of its upstream service flows are associated with the tunnel. All
upstream traffic received on these service flows will be encapsulated with the configured Q-tag or dual Q-tags and sent out
the primary interface. The only exception to this is data for which the CM itself is the source. Any traffic received by the
CMTS that has the source MAC (SMAC) of the CM is not encapsulated even if it is part of a service flow associated with a
L2VPN. This behavior matches that of modems that are added to L2VPNs by means of their config files.
Note: Configuring a CM with L2VPNs via a config file and simultaneously configuring it for use in a L2VPN via the CLI
command is not permitted and may prevent the CM from registering.
Table 134. CLI Commands for Configuring CMs for Use with L2VPN Tunnels
configure l2vpn forwarding cm-mac <mac>
l2vpnid <vpnid> single-qtag <vlanid>
Create a CadL2vpnProvisionedCmEntry for a CM to
single-qtag--cadL2vpn. The
ProvisionedCmInnerVlanId is set to 0.
Associate any data to/from the specified modem
with the VPNID <vpnid>. This data will be
encapsulated with the single-qtag <vlanid>.
To Next Page
Loading...