User guide

8-10 EXTREMEWARE ENTERPRISE MANAGER INSTALLATION AND USER GUIDE
USING THE POLICY SYSTEM
CISCO PORT MAPPINGS
When ExtremeWare Enterprise Manager pushes a policy to a Cisco device, the device
automatically maps well-known TCP and UDP port numbers to names (for example,
TCP port 80 to the name “HTTP”). When Enterprise Manager reads the rules from a
Cisco device, it must re-map the name back to a port number. ExtremeWare Enterprise
Manager uses a properties file to associate the well-known port names and port
numbers. The file,
ciscoipports.properties, is found in the extreme directory under
the top-level installation directory
(
<eem-install-dir>/extreme/ciscoipports.properties). If you encounter
port-to-name mappings that are not included in this file, you can edit the file with a
standard text editor. See Appendix E, “ExtremeWare Enterprise Manager Properties
Files,” for a listing of this file as it shipped with ExtremeWare Enterprise Manager
release 2.0.
L
IMITATIONS ON CISCO DEVICE SUPPORT
There are certain policies that cannot be fully implemented on Cisco devices to make
them function exactly like Extreme devices.
Maximum bandwidth parameter in a QoS profile. The maximum bandwidth parameter is
not used when ExtremeWare Enterprise Manager pushes policies to Cisco devices.
QoS rule precedence. When two policies specify overlapping traffic streams that are
each associated with different profiles, and neither stream is a proper subset of the
other, (for example, one is source IP: 10.203.1.1, destination IP: 10.203.1.2 and the other
is HTTP traffic) then the resolution of which policy gets higher precedence is as follows:
For Extreme switches, there is a set of rules to determine the precedence. See the
ExtremeWare Software User Guide, V 4.0, Chapter 8, “Quality of Service (QoS)” for details.
Precedence Profile
Highest Blackhole
• QP4
• QP3
• QP2
Lowest QP1