Configuring the Enhanced Forwarding Function for IPv6 Control Packets Generated by the Device
Context
QoS policies take effect only for data packets. In certain cases, IPv6 control packets need to be managed. For example, bandwidth limitation is required for the IPv6 control packets generated by Telnet applications. The enhanced forwarding function can meet the requirement. You can configure this function to apply QoS policies to the IPv6 control packets generated by the device. Currently, the enhanced forwarding function is valid only for the IPv6 control packets generated by the device.
Procedure
- Run system-view
The system view is displayed.
- Run ipv6 soft-forward enhance enable
The enhanced forwarding function for IPv6 control packets generated by the device is enabled.
By default, the enhanced forwarding function is enabled for IPv6 control packets generated by the device.
- (Optional) Set the priority for IPv6 control packets.
Set the 802.1p priority.
Run set priority dot1p priority-value
The 802.1p priority is set for the control packets.
Set the DSCP priority.
Run set priority protocol-type-ipv6 protocol-type dscp dscp-value
The DSCP priority of IPv6 control packets generated by the device is configured based on the protocol type.
Run set priority acl6 acl6-number dscp dscp-value
The DSCP priority of IPv6 control packets generated by the device is configured based on the ACL rule.
You can configure the DSCP priority of BGP4+, IPv6 DNS, ICMPv6, IPv6 SNMP, IPv6 SSH, IPv6 Telnet control packets based on the protocol type. To configure the DSCP priority of other types of control packets, configure advanced ACL6 rules based on the protocol type (see Configuring an Advanced ACL6), and configure the DSCP priority of control packets based on the ACL rule.If you specify the DSCP priority of IPv6 control packets based on both the protocol type and ACL rule, the protocol type configuration takes effect preferentially.
- (Optional) Run one or more of the following commands to configure packets to support QoS policies:
Run undo control-packet-ipv6 { bgp4plus | dns6 | ftp | icmpv6 | snmp | ssh | telnet | udp } * output car bypass or undo control-packet-ipv6 all output car bypass
IPv6 control packets generated by the device are configured to support traffic policing function.
By default, IPv6 control packets generated by the device do not support traffic policing function.
Run undo control-packet-ipv6 { bgp4plus | dns6 | ftp | icmpv6 | snmp | ssh | telnet | udp } * output queue bypass or undo control-packet-ipv6 all output queue bypass
IPv6 control packets generated by the device are configured to support QoS queue functions (such as traffic shaping, congestion management, and congestion avoidance).
By default, IPv6 control packets generated by the device do not support QoS queue functions.
Run undo control-packet-ipv6 { bgp4plus | dns6 | ftp | icmpv6 | snmp | ssh | telnet | udp } * output filter bypass or undo control-packet-ipv6 all output filter bypass
The device is configured to discard generated IPv6 control packets when the traffic policy and ACL-based simplified traffic policy contain the deny action.
By default, the device does not discard generated IPv6 control packets when the traffic policy and ACL-based simplified traffic policy contain the deny action.
After this step is performed, the device discards IPv6 control packets.
Follow-up Procedures
After the enhanced forwarding function is configured for IPv6 control packets, you can only make QoS policies take effect for the control packets. To implement differentiated services for control packets, configure QoS policies. For details, see NetEngine AR Configuration Guide - QoS.