Extreme Networks EPICenter 4.1, Руководство по установке программного обеспечения

Страница: 531 / 546

Cisco Internetworking Operating System (IOS) 11.2 Features
EPICenter Software Installation and User Guide 531
Cisco Internetworking Operating System (IOS) 11.2
Features
EPICenter Policy Issues and Limitations
• The EPICenter policy server does not issue rules with duplicated traffic description. If the user
creates a rule through the ExtremeWare CLI that contains the same traffic description as an
EPICenter policy rule, the EPICenter policy rule is not configured to that device until the user
removes the manually created rule.
• If the user deletes an EPICenter policy rule through the ExtremeWare CLI, the rule is added back by
the policy server during the next EPICenter policy configuration.
• The EPICenter policy server can only detect rules that contain “duplicated” traffic descriptions
(traffic flows). When duplicates occur, only one of the duplicated rules will be used. The rule to be
used is based on the precedence of the policies.
• The policy server does not detect IP rules that “overlap” in the general case. Two rules may overlap
when their traffic classifications describe the same set of traffic even if the traffic descriptions are not
identical. The user must decide which rule to use when a general “overlap” occurs by setting the
policy precedence appropriately. When a packet matches multiple overlapping rules, the rule for the
policy with the highest precedence is used.
• EPICenter policy precedence is implemented by assigning precedence numbers to IP access-lists that
are configured to the devices. These precedence numbers may be different on different devices
depending on how many policies are active on a given device. The actual IP access-list precedence
number is not as important because it is the relative ordering between the precedence numbers from
the access-list that matters.
• For ExtremeWare 5.x-6.1.x, the EPICenter policy server does not attempt to enforce the IP policy
precedence because the policy server cannot set precedence numbers via SNMP. On these versions of
ExtremeWare, the rule precedence is controlled by the device, based on “most specific match wins.”
It is highly recommended that users upgrade to ExtremeWare 6.2 to take full advantages of the
EPICenter policy server features.
• A “Deny” ACL rule is displayed as an ACL using the “blackhole” QoS profile.
• The EPICenter Policy server does not modify IP and source port rules created via the CLI.
Cisco IOS 11.2+ Features
Supported
in
EPICenter
Notes
IP QoS
IP Access Group Yes Supported using QoS profile “blackhole”
Priority Queuing Yes Supported using QoS profile priority field. Only supports four
priorities rather than eight as in Extreme.
Custom Queuing Yes Supported using QoS profile minimum bandwidth. Minimum
bandwidth setting is simulated.
Extended IP Access-List Yes EPICenter can use access-list 100 through 199.