The following considerations apply to SAP configurations:
Ensure that egress SAP counters are enabled before associating accounting records that count egress forwarded packets.
Before modifying the counter, disable the account log generation and run the no collect-stats command.
Egress SAP statistics are not available on any of the SAPs of a port, on which a dot1q SAP and dot1q default SAP configuration are present at the same time. This limitation also applies for egress ACLs. That is, egress ACLs are not supported on either dot1q SAPs or dot1q default SAPs when both these SAPs are configured on a port simultaneously.
Egress SAP statistics cannot be configured for use simultaneously on all the configured SAPs. The number of SAPs that can use this feature simultaneously is less than the maximum number of SAPs supported by the node.
Service MTU is not supported on the 7210 SAS-D.
QinQ access SAPs of type Q1.0 are supported only for IES and R-VPLS services. They are not supported for Layer 2 services.
The following table lists the SAPs allowed with different values for the svc-sap-type on 7210 SAS-D and 7210 SAS-Dxp.
svc-sap-type |
Access SAPs |
Access-uplink SAPs |
---|---|---|
null-star |
null SAP, Dot1q default SAP Q.* SAP, 0.* SAP default QinQ SAP (*.* SAP) |
Q.* SAP, 0.* SAP default QinQ SAP (*.* SAP) |
dot1q-preserve |
Dot1q SAP (Dot1q VLAN tag not stripped on ingress), Q1.Q2 SAP (Q2 tag VLAN must match the Dot1q SAP VLAN ID) |
Q1.Q2 SAP (Q2 tag VLAN ID must match the Dot1q SAP VLAN ID) |
any |
null SAP, Dot1q SAP, Dot1q explicit null SAP Q1.Q2 SAP, Q.* SAP, 0.* SAP |
Q1.Q2 SAP, Q.* SAP, 0.* SAP |
dot1q-range |
Dot1q SAP (Dot1q VLAN tag not stripped on ingress), Q1.* SAP |
Q1.* SAP |
A dot1q default SAP cannot be configured when the svc-sap-type is set to any.
When svc-sap-type is set to any for a null SAP, the system processes and forwards only packets with no VLAN tag (that is, untagged). All other packets with one or more VLAN tags (even those with priority tag only) are not processed and are dropped. Users can use the service with the svc-sap-type set to null-star, to process and forward packets with one or more tags (including priority tag) on a null SAP.
The default QinQ SAP processes only tagged packets received on a QinQ port. All tagged packets that do not match the specific SAP tags configured on the same port are processed by this SAP. The default QinQ SAP cannot process untagged packets, even if 0.* SAP is not configured for use on that port.
The default QinQ SAPs are available for use with 0.* SAPs configured on the same port or in the same service. It is available for use with another default QinQ SAP configured in the same service (on a different port).
In a VPLS service, the default QinQ SAP is available for use with any other SAP type configured in a service configured with the svc-sap-type parameter set to null-star.
SAPs using connection profiles (to specify dot1q VLAN ranges) can be configured in a service only when the svc-sap-type is set to dot1q-range.
When a service is configured to use svc-sap-type dot1q-range, the outermost V-LAN tag of the packets is not stripped when the packet is received on access port ingress. See Epipe for information about processing behavior for this type of service.
Service MTU is not supported on 7210 SAS-D.
The following counters are available on 7210 SAS-D and 7210 SAS-Dxp devices:
ingress and egress counters per SAP
ingress policer counters per SAP
egress queue counters per access port
ingress and egress counters per access-uplink port
The number of counters available to count total received packets or octets on an access-uplink SAP (in a VPLS, VLL or IES service) ingress is limited; therefore a count of received packets or octets cannot be obtained for all the SAPs simultaneously. By default, these counts are not available.
The config service epipe sap statistics ingress command is available to associate a counter with the SAP and obtain the counts.
The number of counters available to count total forwarded packets or octets on an access SAP egress and access-uplink SAP egress is limited and therefore a count of received packets or octets cannot be obtained for all the SAPs simultaneously. By default, these counts are not available.
The config service epipe sap statistics ingress forwarded-count command is available to associate a counter with the SAP and obtain the counts.