Alcatel 9000 Betriebsanweisung PDF herunterladen (Seite 559)

100

101

Configuring QoS Policy Applications

OmniSwitch 6800/6850/9000 Network Configuration Guide June 2006 page 26-53

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.

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.

-> 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.

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.

The following policy action commands are used for port and link aggregate redirection:

policy action redirect port

policy action redirect linkagg

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.

• 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.

• In most cases, a redirected flow will not trigger an update to the routing and ARP tables. If necessary,

create a static route for the flow or assign the redirect port or link aggregate ID to the ingress VLAN

(VLAN A) to send packets to the redirect port until a route is available.

• When redirecting bridged traffic on VLAN A, the redirect port or link aggregate ID must belong to

VLAN A (tagged or default VLAN).

In the following example, flows destined for UDP port 80 is redirected to switch port 3/2:

-> policy condition L4PORTCOND destination udp port 80

-> policy action REDIRECTPORT redirect port 3/2

-> policy rule L4PORTRULE condition L4PORTCOND action REDIRECTPORT

1 2 ... 554 555 556 557 558 559 560 561 562 563 564 ... 701 702

Kommentare zu diesen Handbüchern

Keine Kommentare

Alcatel 9000 Betriebsanweisung Seite 559

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Software Alcatel 9000