The following default-fc assignment rules apply for SAPs configured in Layer 3 services, including RVPLS services:
Bridged IP packets processed in an RVPLS context that do not match any of the explicitly configured DSCP classification entries in the access port DSCP classification policy are assigned the default-dscp-fc configured in the policy. The profile assigned on ingress is in accordance with the user configuration (for example, default-dscp-fc "be" profile out).
Bridged, tagged non-IP Layer 2 Ethernet packets, which are processed in an RVPLS context and that do not match any of the explicitly configured dot1p classification entries in the access port dot1p classification policy, are assigned the default-dot1p-fc configured in the policy. The profile assigned on ingress is in accordance with the user configuration (for example, default-dot1p-fc "be" profile out).Bridged, untagged non-IP Layer 2 Ethernet packets, which are processed in an RVPLS context, will not match any of the explicitly configured dot1p classification entries in the access port dot1p classification policy. They are assigned access port untagged-fc profile.
Routed IP packets processed in an RVPLS context that do not match any of the explicitly configured DSCP classification entries in the DSCP classification policy associated with the interface using the routed-override-qos-policy command are assigned the default-dscp-fc configured in the policy. The profile assigned on ingress is in accordance with user configuration in the DSCP classification policy.
IP packets processed in an IES or VPRN service context that do not match any of the explicitly configured DSCP classification entries in the DSCP classification policy associated with SAP ingress policy are assigned the default-dscp-fc configured in the DSCP classification policy. The profile assigned on ingress is in accordance with user configuration in the DSCP classification policy.