Alcatel-Lucent 6850-48 ネットワークガイド
Configuring QoS
Policy Applications
OmniSwitch AOS Release 6 Network Configuration Guide
September 2009
page 40-59
To create a policy rule to prioritize the traffic from Network 1, first create a condition for the traffic that
you want to prioritize. In this example, the condition is called ip_traffic. Then create an action to priori-
tize the traffic as highest priority. In this example, the action is called high. Combine the condition and the
action into a policy rule called rule1.
you want to prioritize. In this example, the condition is called ip_traffic. Then create an action to priori-
tize the traffic as highest priority. In this example, the action is called high. Combine the condition and the
action into a policy rule called rule1.
-> policy condition ip_traffic source ip 10.10.4.0 mask 255.255.255.0
-> policy action high priority 7
-> policy rule rule1 condition ip_traffic action high
The rule is not active on the switch until the qos apply command is entered on the command line. When
the rule is activated, any flows coming into the switch from 10.10.4.0 will be given the highest priority.
the rule is activated, any flows coming into the switch from 10.10.4.0 will be given the highest priority.
Bandwidth Shaping Example
In this example, a specific flow from a source IP address is sent to a queue that will support its maximum
bandwidth requirement.
bandwidth requirement.
First, create a condition for the traffic. In this example, the condition is called ip_traffic2. A policy action
(flowShape) is then created to enforce a maximum bandwidth requirement for the flow.
(flowShape) is then created to enforce a maximum bandwidth requirement for the flow.
-> policy condition ip_traffic2 source ip 10.10.5.3
-> policy action flowShape maximum bandwidth 1k
-> policy rule rule2 condition traffic2 action flowShape
Note that the bandwidth may be specified in abbreviated units, in this case, 1k.
The rule is not active on the switch until the qos apply command is entered. When the rule is activated,
any flows coming into the switch from source IP address 10.10.5.3 will be queued with no more than 1k of
bandwidth.
any flows coming into the switch from source IP address 10.10.5.3 will be queued with no more than 1k of
bandwidth.
Redirection Policies
A redirection policy sends traffic that matches the policy to a specific port or link aggregate instead of the
originally intended destination. This type of policy may use any condition; the policy action determines
which port or link aggregate to which the traffic is sent.
originally intended destination. This type of policy may use any condition; the policy action determines
which port or link aggregate to which the traffic is sent.
The following policy action commands are used for port and link aggregate redirection:
Note the following regarding the use and configuration of redirection policies:
• Redirection policies apply to both bridged and routed traffic.
• When redirecting routed traffic from VLAN A to VLAN B, the redirect port or link aggregate ID must
belong to VLAN B (tagged or default VLAN).
• Routed packets (from VLAN A to VLAN B) are not modified after they are redirected; the source and
MAC address remain the same. In addition, if the redirect port or link aggregate ID is tagged, the redi-
rected packets will have a tag from the ingress VLAN A.
rected packets will have a tag from the ingress VLAN A.
• If a route exists for the redirected flow, then redirected packets are the final post-routing packets.
• If a route does not exist for the redirected flow, the flow is not redirected to the specified port or link
aggregate ID and is “blackholed”. As soon as a route is available, the flow is then redirected as speci-
fied in the policy.
fied in the policy.