The connection-profile-vlan SAPs (CP SAPs) allow the association of a range of customer VIDs to a specific SAP. CP SAPs can be used to build Layer 2 services that are fully compatible with MEF 10.3 Bundling Service Attributes and RFC 7432 EVPN VLAN Bundle Service interfaces.
The config>connection-profile-vlan>vlan-range command defines the range of customer VIDs to be matched when the connection-profile-vlan is associated with a dot1q or QinQ SAP.
The following example shows the command usage in dot1q and QinQ SAPs:
A:PE# configure connection-profile-vlan 1 create
vlan-range 5 to 100
vlan-range 150 to 300
vlan-range 350
exit
The following is an example configuration output:
A:PE>config>service>vpls# info
----------------------------------------------
<snip>
sap 1/1/1:cp-1 create
no shutdown
exit
sap 1/1/2:100.cp-1 create
no shutdown
exit
sap 1/1/3:cp-1.* create
no shutdown
exit
<snip>
For VLAN manipulation, the CP SAP behavior is equivalent to the default SAP’s (when the ingress VID falls into the range configured in the CP), where the range of VIDs included is not service-delimiting and therefore, the VIDs are not pushed/popped. The main differences between the CP SAPs and the default SAPs are:
A default SAP consumes less resources; a default SAP consumes one SAP instance, whereas a CP SAP consumes SAP instances equal to the number of VLANs in the range. To check the number of SAP instances used by the system, run the following CLI commands:
See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Basic System Configuration Guide for a complete description of the tools dump resource-usage command.
*A:Dut# tools dump resource-usage system =============================================================================== Resource Usage Information for System =============================================================================== Total Allocated Free ------------------------------------------------------------------------------- <snip> SAP Entries | 262143 8 262135 =============================================================================== *A:Dut# tools dump resource-usage card 1 fp 1 =============================================================================== Resource Usage Information for Card Slot #1 FP #1 =============================================================================== Total Allocated Free ------------------------------------------------------------------------------- <snip> SAP Instances | 63999 254 63745 <snip> ===============================================================================Unlike the default SAP, a CP SAP cannot coexist with a vlan SAP that is in the same range. For example, 1/1/1:* and 1/1/1:100 can coexist; in contrast, 2/1/1:cp-1 (cp-1 = vlan 1 to 200) and 2/1/1:100 cannot coexist.
Figure: VLAN tag handling shows customer VID processing by SAPs with service-delimiting VIDs, and by CP SAPs. In this example, SAP 1/1/1:cp-1 does not strip off or push VID 10, whereas SAP 1/1/1:100 and SAP 1/1/1:200 do strip off and push the corresponding VID.
A connection-profile-vlan allows the configuration of VLAN ranges with the following characteristics:
A vlan-range can be defined as a single VID (for example, vlan-range 101), or two VIDs delimiting the beginning and the end of the range (for example, vlan-range 105 to 107).
Discontinuous ranges are allowed.
Overlapping ranges are not allowed within the same connection-profile-vlan configuration. Overlapping VLAN ranges can exist across different connection profiles if they are not applied to the same port (in the case of dot1q ports), or the same port and service-delimiting tag (in the case of QinQ ports). For example:
1/1/1:x.cp-1 and 1/1/1:y.cp-2 can coexist on the same port, where cp-1 includes VIDs [10-20] and cp-2 includes VIDs [15-25]
if x=y, then the overlapping is not possible in the above case
A connection-profile-vlan must have at least one range (with a single or multiple VIDs) before it can be associated with a SAP.
A connection-profile-vlan cannot contain an explicitly defined SAP within any of the ranges when the explicit SAP is configured on the same port.
The configured VLAN ranges cannot contain VIDs 0 or 4095.
The connection-profile-vlan SAPs are supported in Layer 2 services only. No IES or VPRN services can contain CP SAPs.
CP SAPs are supported on access or hybrid ports but are not on network interfaces.
CP SAPs are supported in (non-PBB) Epipe and VPLS services.
CP SAPs support SAP based QoS policies. VID type MAC criteria can be used on CP SAPs to apply specific QoS on a VLAN within the connection-profile-vlan.
The legacy OAM commands (mac-ping, mac-trace, mac-purge, and mac-populate) are not supported for CP SAPs.