Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) - Manual (Page 486)

458 Multi-Service IronWare Routing Configuration Guide
53-1003033-02
Limiting the number of hops an IPv6 packet can traverse
Limiting the number of hops an IPv6 packet can traverse
By default, the maximum number of hops an IPv6 packet can traverse is 64. You can change this
value to between 1 – 255 hops. For example, to change the maximum number of hops to 70, enter
the following command.
Brocade(config)# ipv6 hop-limit 70
Syntax: [no] ipv6 hop-limit number
The number of hops can be from 1 – 255.
QoS for IPv6 traffic
Configuring QoS for IPv6 traffic is generally the same as it is for IPv4 traffic. The QoS policies you
configure on the device apply to both incoming IPv6 and IPv4 traffic. ACLs can be used to perform
QoS for IPv6 traffic for the following values:
• dscp
• fragments
• priority-force
• priority-mapping
• source routing
• drop-precedence
• drop-precedence force
To enable QoS for IPv6 traffic, enter the following commands.
Brocade(config)# port-priority
Brocade(config)# write memory
Brocade(config)# end
Brocade# reload
Syntax: [no] port-priority
NOTE
You must save the configuration and reload the software to place the change into effect. This applies
whether you are enabling QoS for IPv6 or IPv4 traffic.
The port-priority command globally enables QoS for IPv6 traffic on all interfaces. On Brocade
devices, when QoS is enabled with the port-priority command, the device inserts a value in the
internal header based on a combination of the following information:
• 802.1p priority
• Interface priority (if configured)
• VLAN priority (if configured)
• The DSCP field in the Type of Service (ToS) header