Traffic Policies; Policy Based Services; Service Bundles - Extreme Networks IP Service Manager User Manual

Infrastructure client for ism provision

Table of Contents

Service Library

Traffic Policies

A traffic policy is similar to an access list in ExtremeWare. You can specify IP, TCP, and

UDP traffic policies to specify the handling of various kinds of traffic. Just like an access

list, you specify source, destination, and precedence for the traffic policies. Unlike access

lists, there is no "deny" or "permit" parameter for traffic policies. The deny/permit

functionality is implemented when you create policy based services. A traffic policy that

is part of a policy based service configured to "block" traffic is equivalent to an access

list set to "deny". A traffic policy that is part of a policy based service configured to

either "no rate limiting" or "use rate limiting" is equivalent to an access list set to

"permit" (the rate limiting may cause the traffic to be dropped because of congestion,

but that is different from an outright "deny").

A policy based service consists of at least one traffic policy and a specification of the

behavior for the service. A policy based service only applies to the ingress traffic of a

subscriber. The ingress behavior can be set to "blocked", "no rate limiting", or "use rate

limiting". If the "use rate limiting" parameter is set, there must be a loopback

port/VLAN defined for the subscriber that the policy based service is eventually

applied to. Those policy based services set to "use rate limiting" will set one of the QoS

profiles (Qp2 through Qp8) on the subscriber loopback VLAN. You cannot manually

assign which service uses which profile.

Policy based services are not used directly by subscribers, but are part of service

bundles. A single policy based service can belong to more than one service bundle.

A service bundle can be thought of as the default behavior for a subscriber's ingress

and egress traffic, modified by any policy based services added to the service bundle.

This service bundle will be associated with a subscriber (created in Service Activation

view), to control the traffic on that subscriber's port. If there are no policy based

services added to the service bundle, the service bundle sets the behavior for all of the

traffic for a subscriber.

4-2

IP Service Manager User Guide

Table of Contents