If you want to differentiate priorities of different services in a VPN, set the DiffServ mode to uniform. You can also set the DiffServ mode to pipe or short pipe, but you need to specify the DiffServ domain in which the mode applies.
If you want to differentiate priorities of services in different VPNs but not priorities of services in a VPN, set the DiffServ mode to pipe or short pipe and specify EXP values in private labels.
If you do not want to change priorities carried in original packets, you are advised to set the DiffServ mode to pipe or short pipe. In uniform and pipe modes, the egress node determines the per-hop behavior (PHB) based on the EXP priorities of packets. In short pipe mode, the egress node determines the PHB based on DSCP priorities of packets.
The system view is displayed.
The VPN instance view is displayed.
The DiffServ mode supported by the MPLS L3VPN is set.
By default, the DiffServ mode supported by the MPLS L3VPN is uniform.
If the mpls-qos ingress trust upstream none or mpls-qos egress trust upstream none command is configured, the device on the private network does not perform EXP priority mapping even if you run the diffserv-mode command.
When the DiffServ mode is set to uniform on the ingress node, the ingress node performs priority mapping in the DiffServ domain specified by the domain parameter in this command. If the domain parameter is not specified, the ingress node performs priority mapping in the DiffServ domain specified by the mpls-qos ingress trust upstream { ds-name | default } command.
In a non-PHP scenario, the egress node performs priority mapping in the DiffServ domain specified by the mpls-qos egress trust upstream { ds-name | default } command. In a PHP scenario, the egress node performs priority mapping in the DiffServ domain specified by the domain parameter in this command. If the domain parameter is not specified, the egress node performs priority mapping in the DiffServ domain specified by the mpls-qos egress trust upstream { ds-name | default } command.
This command must be configured before the instance takes effect; otherwise, you must reset BGP connections to make the configuration take effect.