Basic Epicenter Policy Definition; Policy Types - Extreme Networks EPICenter Guide Manual

Concepts and solutions guide
Hide thumbs Also See for EPICenter Guide:
Table of Contents

Advertisement

Policy Manager Overview
definition. Resources must be set up through the Grouping Manager or Inventory Manager before you
can use them in a policy definition. You should be thoroughly familiar with the Grouping applet before
you begin to define policies using the Policy Manager.

Basic EPICenter Policy Definition

A QoS policy in the EPICenter Policy Manager is composed of the following components:
A Name and Description that you supply when you create the policy. The Description is optional.
The Policy Type, which translates to the implementation type (Access-based Security QoS, IP QoS,
Source Port QoS, or VLAN QoS). The implementation type determines the type of traffic grouping
the switch will look for in implementing the policy. This in turn determines what type of endpoints
are allowed in your traffic definition, and how some of the other elements, such as traffic direction,
are handled.
A definition of the Access List (for Security policies) or Policy Traffic (for IP policies) to be affected
by the policy. You define the policy traffic by specifying the endpoints the switch should use to
identify the traffic of interest. The EPICenter Policy Manager lets you define the endpoints using a
high-level set of resources described below (see
details).
The Access Domain or Scope of the policy—the set of network devices on which to apply the policy.
The EPICenter Policy Manager converts the high-level policy definition you create into a set of low-
level ACL and QoS rules that it will configure on the devices within the scope or domain of the
policy. To do this, the Policy Manager takes the following steps:
a Converts the endpoint components and the specified traffic direction into traffic patterns.
b Uses the policy domain or scope to determine the device(s) and ports on which the QoS rules
should be implemented.
c Determines the QoS profiles to associate with the traffic flows for each device in the scope.
d Resolves any QoS rule conflicts using precedence relationships.
e Configures the QoS rules on the network switches either automatically (if Auto Configuration is
enabled) or when you initiate the configuration using one of the directed configuration
operations.

Policy Types

The EPICenter Policy Manager supports four types of policies: Access-based Security QoS policies, IP
QoS (Access List) policies, Source Physical Port QoS policies, and VLAN QoS policies. These policies
assign QoS profiles to traffic flows that are identified based on dynamically determined destination
port, IP-based endpoint addressing information, physical port of origin, or VLAN origin. This release of
the EPICenter Policy Manager does not support policies for traffic based on MAC address destination
information or on explicit class of service (802.1P and DiffServ) information.
ExtremeWare versions 5.0 or later support IP, VLAN and source port types. Only ExtremeWare 7.0
supports Security policies. ExtremeWare versions prior to 5.0 support only VLAN-based QoS. Thus,
although the Policy Manager supports IP, Access-based Security, and Source Port policies, non-i-series
devices will not be able to use those policies unless they are running ExtremeWare version 5.0. The
Policy Manager will not attempt to configure policies on devices that cannot support them.
162
"Policy Named Components" on page 170
EPICenter Concepts and Solutions Guide
for more

Advertisement

Table of Contents
loading

This manual is also suitable for:

Epicenter 6.0

Table of Contents