Table-based classification per port for bridged packets

For bridged packets, although the DSCP classification is based on the DSCP policy attached to the port, the enable-table-classification command must also be set in the IES or VPRN interface context as well as the respective RVPLS SAP context for table-based classification to work correctly (as shown in the Example). If enable-table-classification is not set on the respective RVPLS SAP then only profile will be taken from the port policy for that SAP. In this case, classification (in accordance with TCAM-based classification) and meters will be taken from the SAP ingress policy.

The following syntax enables table-based classification on an Ethernet port and specifies the DSCP classification policy in the port>ethernet>access>ingress command.

configure>port> 
        ethernet> 
            [no] enable-table-classification 
        exit 
        
    configure>port>ethernet>access>ingress> 
        [no] dscp-classification policy-id 
        [no] untagged-fc fc
    exit

Example

Example:

configure>port 1/1/1 
        ethernet
            enable-table-classification 
        exit 
    
    configure>port> 1/1/1
        ethernet>access>ingress> 
            dscp-classification 101 
            untagged-fc ef
        exit 
    exit 
    
    configure> service> ies> interface>
        vpls "rvpls-example-svc"
            ingress
                enable-table-classification 
            exit
        exit
    exit