Extreme Networks Policy Manager (EPM) Supervisor Edition - User Guide
Extreme Networks Policy Manager (EPM) Supervisor Edition - User Guide
Preface........................................................................................................................................... 7
Introduction ...............................................................................................................................7
Conventions................................................................................................................................7
Related Publications ...................................................................................................................8
Index ............................................................................................................................................ 79
Extreme
Extreme Networks
Networks PolicyPolicy Manager
Manager (EPM)(EPM) 1.2 User
1.2 User GuideGuide 5 5
Table of Contents
This preface introduces this user guide, describes guide conventions, and lists other useful publications.
Introduction
This guide provides the required information to use the Extreme Networks Policy Manager (EPM) -
Supervisor Edition software. It is intended for use by network administrators who are responsible for
monitoring and managing Local Area Networks and assumes a basic working knowledge of:
● Local Area Networks (LANs)
● Ethernet concepts
● Ethernet switching and bridging concepts
● Routing concepts
● Access Control Lists (ACLs)
● CLEAR-Flow
NOTE
If the information in a Release Note differs from the information in this User Guide, the Release Note takes
precedence.
Conventions
Table 1 and Table 2 list conventions that are used throughout this guide.
Related Publications
Other manuals that you will find useful are:
For documentation on Extreme Networks® products, and for general information about Extreme
Networks, see the Extreme Networks home page:
http://www.extremenetworks.com
Customers with a support contract can access the Technical Support pages at:
http://www.extremenetworks.com/services/eSupport.asp
The technical support pages provide the latest information on Extreme Networks software products,
including the latest Release Notes, information on known problems, downloadable updates or
patches as appropriate, and other useful information and resources.
Introduction
This chapter describes the following sections:
● Description of the Extreme Networks Policy Manager on page 9
● About This Manual on page 10
● Editions of the EPM on page 10
ACLs are used to perform packet filtering and forwarding decisions on traffic traversing the switch.
Each packet arriving on an ingress port and/or VLAN is compared to the access list applied to that
interface and is either permitted or denied. ACLs are typically applied to traffic that crosses Layer 3
router boundaries, but is possible to use access lists within a Layer 2 virtual LAN (VLAN).
CLEAR-Flow is an extension to ACLs that implements security, monitoring, and anomaly detection in
Extreme XOS software. ACL policy rules are created to count packets of interest. CLEAR-Flow rules are
added to the policy to monitor the ACL counter statistics for situations of interest in the individual
network. Such situations can include: the cumulative value of a counter; the change to a counter over a
sampling interval; the ratio of two counters; or even the ratio of the changes of two counters over an
interval. For example, monitoring the ratio between TCP SYN and TCP packets might show an
abnormally large ratio which may indicate a SYN attack.
The counters used in CLEAR-Flow are either defined by the user in an ACL entry, or can be a
predefined counter. Refer to a list and description of these counters in Appendix A on page 63.
If the rule conditions are met, the CLEAR-Flow actions configured in the rule are executed. The switch
can respond by modifying an ACL that will block, prioritize, or mirror the traffic, executing a set of CLI
commands, or sending a report using a SNMP trap or EMS log message.
For additional information about ACLs or CLEAR-Flow refer to the ExtremeXOS Concepts Guide.
Switch Requirements
The following apply to the switch used with the EPM.
● The EPM can be run on the following Extreme Networks switches:
■ BlackDiamond® 8800 series
■ Summit® family of switches (Summit X150, X250e, X450, X450a and X450e series)
■ BlackDiamond 10808
■ BlackDiamond 12800 series
NOTE
Although the BlackDiamond 8800 and Summit switches listed above support the EPM, they do not support
CLEAR-Flow rules. Therefore, when the EPM is used with these switches, CLEAR-Flow rules and their raw rule
text are displayed but the rules themselves are disabled
EPM Installation
The EPM is installed from a network download and utilizes a user interface installation Wizard. Use the
following procedure:
1 Download the EPM program files from Extreme Networks’ Software Downloads web page.
2 On Windows, double click the installation bundle executable icon.
On Linux, run the installation script (.sh file) from an xterm window.
The Setup Wizard window is launched as shown below.
NOTE
Installation on Linux uses the Installation Wizard with similar panels and properties.
and is followed by
The Wizard then extracts and installs the files, and displays
e Notification of the file installation,
f The following Information window, and
Introduction
This chapter provides a brief description of the different ways to view policies and rules in the Extreme
Networks Policy Manager (EPM).
The EPM functions in two modes—local and switch. In local mode, the user can work independently
within an offline set of files to create, modify and verify policies and rules. The local files can also be
used as a backup system for files running on a switch. When working locally, certain elements of the
application are hidden and can be seen only when connected to a switch. In switch mode, the user can
utilize all the functions of the EPM.
Each policy is viewed and edited individually and only one policy can be open at a time. If one policy
is open in the program and the user attempts to open or create another, the EPM prompts with a save
command before closing the currently open policy.
NOTE
Only one instance of the EPM can be executed on the desktop at a time.
The first time the EPM program is launched, the following message is displayed
.
2 After reading, Close the box. The following IP Address Notice is displayed. This notice is displayed
every time the EPM is opened until an IP address has been set.
3 Click OK. The EPM then notifies the user if it has found a TFTP server. Without one, the EPM can
open and save local policies only.
a If it finds a TFTP server, the following notice is displayed.
Refer to “Configuring the EPM for use on a Switch” on page 18 to set the policy staging directory.
b If it does not find a TFTP server, the following notice is displayed.
NOTE
A notice regarding TFTP server availability is also displayed in the Status Panel under the Alerts tab. (Refer to
“Status Panel” on page 23.)
● The EPM has found a TFTP server. Check that the TFTP server is running on client and is listening
on port 69.
● The user running the EPM has read/write/create permission to the TFTP server’s root directory.
● The file staging directory is pointing towards the TFTP server’s root directory. To set the directory:
a Choose Tools > Properties > Set file staging directory from the menu. A file Open box is
displayed.
b Point to the TFTP server’s root directory as shown below.
c Click Open. The box closes and the file staging directory is set.
● The local IP address is set. To set the address:
a Choose Tools > Properties > Set Local IP Address from the menu. A Local IP Selection box
opens.
b From the dropdown menu, select an available IP address and click OK. The IP address is set.
NOTE
If the network configuration is changed, the local IP address must be reset.
● If applicable, set the public side address of NAT. If not applicable, leave blank. To set the address:
a Choose Tools > Properties > Set NAT IP address from the menu. An Input dialog box is
displayed.
b Enter the address and click OK.
NOTE
Network Address Translation (NAT) is a method used by networking equipment such as routers to share an IP
address.
● The file search directory is pointing towards the policy files as shown below. This is the default.
Choose Tools > Properties > Set file search directory to check the file name in the file Open box.
Some window elements are common to both the Rule Editor and the Rule Navigator windows. The
following screen identifies those common elements.
These include:
Menu Bar
The Menu Bar consists of six standard menus—File, View, Policy, Rules, Tools and Help. Table 5
describes the elements of these menus.
In the Rule Editing and Viewing Panel and the Rule Navigator window, another menu is displayed
when you right-click any rule in the list. For details about the functions of this menu, refer to the
chapter, “Modifying Policies and Rules” on page 43.
Toolbar
The Toolbar contains icons for the most common menu operations and are shown in Table 6.
Status Panel
The Status Panel displays data from different log files—Alert, Actions, Log, Policy Information and
Rule Activity. A log is selected by clicking its panel tab. These logs are described below with examples
of the screens.
● The Alerts tab displays the alerts log messages. Alerts are warnings or notices about an
action or error that may or may not have inhibited EPM functions.
● The Actions tab displays the actions log messages. All user actions are recorded for audit
purposes. (The replay of actions is planned for a future release.)
● The Log tab displays common log messages. The common log contains any trace or error
messages that inhibit or cause failure of EPM functions.
For each of these three logs (Alerts, Actions and Log), there is a “Clear” button that removes the entries
currently appearing on the screen. These entries are then stored in the program’s log files
(\Program Files\epm_supervisor\log). To set the maximum number of status capture lines for a log,
choose Tools > Properties > Message Capture > Set Capture Size from the menu.
● The Policy Information tab is displayed when a policy is opened and shows
Information and Notes about that currently open policy. Information shows basic data including
when and by whom the policy was created and last modified as well as the number and type of
rules. Notes might include the purpose of the policy or other user defined identifiers. This is a read/
write text box.
● The Rule Activity tab displays activity data for a policy running on a switch. The EPM
updates the data every 15 to 30 seconds. This log is shown only when the EPM is connected to a
switch.
For the Rule Activity log, there is a Refresh button that manually updates any modified activity.
Status Bar
The Status Bar displays the current activity of the EPM. When it is not executing a function it reads
“Idle.” Otherwise, it shows an explanation of the function that is running. For example:
● When opening a file locally, the status bar reads “Operation 'OpenLocal' is in progress. (The
operation should complete within '30' seconds.)” or
● When exiting the EPM, the status bar reads “Operation 'FlushLogsAndExit' is in progress (The
operation should complete within '30' seconds.)”
Tree Structure Panel Rule Editing and Viewing Panel Rule Properties Panel
● Clicking the up, down and side “arrow points” adjacent to the Tree Structure, and Status panels
● Clicking the X in the upper right corner of the Rule Properties and Status panels
● From the Menu Bar, selecting and deselecting the boxes from the View > Status Panel, Rule
Properties Panel, and Tool Bar submenus
When a panel is hidden using these methods, the remaining panels expand to fill the window.
Within this panel, the rules can be organized and displayed in three different ways. Use the three tabs
that are located below the panel to organize and display the rules according to the following:
Rules by class Displays the rules by their class.(Refer to “Class” in the next table.)
Rules by action Displays the rules by each action included in the rule.
• For ACL rules, the actions are: Permit, Deny, Count, CVID, Link Aggregation Hash,
Qos, SCOS, STAG Ethertype, SVID, Traffic Queue, and Uplink Port.
• For CF rules the actions are: Permit, Deny, Qos, Mirror, Cli, Snmp, and Syslog.
Rules by reference Displays the rules showing the connection between an specific ACL rule and a CLEAR-
Flow rule. An ACL rule that is shown in blue text is one that does not have a
corresponding CLEAR-Flow reference or vice versa.
Information in this panel is displayed using a standard tree structure that allows subcomponents to be
hidden or shown by clicking the "key" icon.
NOTE
Right-click actions are not supported in the tree structure panel.
# A number that shows the position of each rule in the policy. If the rules are reordered, the
position numbers for the rules change accordingly.
Rank The rank number is used to indicate the order in which the rules are stored in the policy file.
They are stored in descending order. The user can set the order by positioning the rules
manually or rely on the EPM’s algorithm to establish an efficient order based on the
specificity of the rule.
The algorithm is available when creating a rule or later by using the menu command Policy >
Recalculate rule ranks. The menu command is used when creating new rules and for
recalculating rank when rules have been added or deleted from the policy.
Type The type of rule—ACL or CLEAR-Flow.
Class The class is a friendly name label that the user defines to customizes the rules according to
individual needs and categories. When a class is not named, the default is “Generic.”
Name Name of the rule. Clicking on the plus sign expands each rule to display its raw rule text.
TCNT Trigger Count. TCNT is shown when the policy opened on a switch is activated by the Activity
Manager. It represents the number of times the ACL or CLEAR-Flow rule has been evaluated
and triggered or fired. The TCNT is updated only when a policy is opened on a switch and
when the Refresh button above the Rule Activity tab display on the Status Panel is pressed.
For policies opened locally, nothing is displayed under the TCNT column.
Status Status displays whether a policy that was saved with the EPM has been modified without the
EPM. When the policy has not been so modified, there is no entry in the column. When the
policy has been so modified the status column entry is “Rule modified externally.”
Another feature of this panel is a dropdown menu that is displayed when you right-click any rule in the
list. The menu displays functions that are used primarily to edit and modify policies and rules. For
details about this menu, refer to the chapter, “Modifying Policies and Rules” on page 43.
Rule Parameters Tab. Clicking the Rule Parameters tab displays the following information:
● When an ACL is selected from either the Tree Structure or the Rule Editing and Viewing Panel, the
rule parameters displayed are:
Match Conditions The match conditions contained in the rule—the “if” statement. A list
of available match conditions is included in Appendix A on page 69.
Actions The action taken when the packet matches the match conditions—the
“then” “permit or deny” statement. If the packet matches all the
match conditions and if there is no action specified in the “then”
statement, “permit” is used by default.
Action Modifiers Additional modifiers to the actions, such as “count”, cvid, link-
aggregation-hash, traffic queue, or redirect.
Match Conditions The conditions that will trigger the rule and how often to evaluate the
rule.
Actions (True Condition) The list of actions to take when the rule is triggered—the “then”
clause.
Actions (False Condition) The list of actions to take after the rule is triggered and when the
match conditions later become false—the else clause.
Icons are connected to each of the three boxes and are used to edit the parameters. They are:
Delete Selection
Add
Rule Information Tab. Clicking the Rule Information tab displays the following information:
General A summary of the basic information about the rule including: Name; Type; Policy
Version; Action information, and so forth.
Access Details showing when and by whom the rule was created and, if applicable,
modified. In the Supervisor edition, the “by whom” is always the supervisor.
Notes A read/write text box into which notes such as the purpose of the rule can be
added. To add notes, click inside the text box and begin typing. The Apply Notes
button is enabled. Click the button when the entry in complete. To delete notes,
highlight the text to be removed then strike the keyboard’s Delete or Backspace
key. The Apply Notes button is enabled. Click the button.
The screen below shows the Rule Navigator Window and the elements unique to this window. Those
elements include:
● Access Control List Rules (ACL) and ACL Rule Detail
● CLEAR-Flow Rules (CF) and CF Rule Detail
The Access Control List (ACL) Rules panel displays the names of the ACL rules that are included in
the policy that is open. ACL Rule Detail displays the raw rule text for the ACL rule that is selected.
The CLEAR-Flow (CF) Rules panel displays the names of the CF rules that are included in the policy
that is open. CF Rule Detail displays the raw rule text for the CF rule that is selected.
Above both the Access Control List Rules panel and the CLEAR-Flow Rules panel are the following two
icons.
Between the Access Control List rules panel and the CLEAR-Flow Rules panel are two icon arrows
which toggle filters on and off.
A toggle button that when clicked filters the CLEAR-Flow rules to show only those that are
referenced by the selected ACL rule. In the CF Rule Detail panel, the reference is highlighted in
yellow. Click the button a second time to toggle the filter off and again show all CLEAR-Flow
rules.
A toggle button that when clicked filters the ACL rules to show only those that are referenced by
the selected CLEAR-Flow rule. In the ACL Rule Detail panel, the reference is highlighted in
yellow. Click the button a second time to toggle the filter off and again show ACL rules.
When the EPM cannot find the required metadata to determine the policy file version, a Policy
Version Notice box is displayed that requests more information.
a Click OK. A Policy Version Selection box is displayed.
b From the Versions: panel, select an appropriate version based on information in the Description
panel and click OK. The Operation Progress box is displayed followed by a Validation Notice.
3 Enter the following information, completing all four fields. Leaving a field blank does not result in
default behavior.
a The IP Address of the switch to which you want to connect
b The Virtual Router on which the SSH server traffic is routed
c The Admin Login ID
d The associated Admin Password
Then click OK. An Operation Progress box is displayed showing that the connection to and from
the switch is being checked.
NOTE
The EPM remembers the Remote Switch Dialog settings after they have been entered and the connection is
successful.
4 When there is a problem with the connection, the following box is displayed.
Check the suggested reasons and make the necessary adjustments. For additional information, refer
to “Configuring the EPM for use on a Switch” on page 18.
When there is no problem with the connection, a Policy Selection box opens as shown below.
5 From the dropdown menu, choose the desired policy name and click OK. The Operation Progress
box is displayed and is followed by a Load Notice box stating that the policy was successfully
loaded.
6 Click OK. In the Tree Structure Panel, the IP address of the switch is displayed following the policy
name.
NOTE
The Operation Progress box appears when policies are being loaded from or saved to a switch, indicating that the
switch connection is being checked.
Some EPM functions are active only when the program is connected to a switch and are either not
displayed or not enabled in the local mode. These include the following:
● The Status Panel’s Rule Activity tab is displayed only when connected to a switch.
● The Rule Editing and Viewing Panel’s TCNT entries do not show unless connected to a switch.
Policy Parsing
The EPM can be set to respond in one of two ways when an attempt is made to open an invalid policy.
1 From the menu, choose Tools > Properties > Policy Parsing > Ignore Unknown Keywords. The box
is checked by default.
When the box is checked, the EPM attempts to load the policy. When such a policy is encountered, a
Parse Notice box is displayed as shown below.
2 Click OK and the rule display in the rule viewing panels resembles the following:
When the box is unchecked, the EPM responds with an invalid message and does not attempt to load
the policy.
Search by Name
To search for a rule in the Rule Editing and Viewing Panel by name or partial name, use the following
procedure:
1 In the text box located in the Toolbar, type all or part of the desired rule name, for instance: “ACK.”
2 Click the Find Rule icon . The first rule in the Rule Editing and Viewing Panel that matches the
entered criteria, is then highlighted. In this example, the rule is “ACL_SMURF_ATTACK.”
3 Click the Find Next icon to continue the search. In the example, the next rule is ACL-ACK.
4 Continue as needed until the Find Notice box reading "Search reached end of policy" is displayed.
NOTE
When a rule is found and highlighted in the Rule Editing and Viewing Panel, it is also highlighted in the other rule
listings in both the Rule Editor window and the Rule Navigator window.
Search by Parameter
To search for one or more rules that have specified elements, use the following procedure:
1 From the menu choose Policy > Search or click the Search Policy icon . A Search Policy dialog
box opens as shown below.
2 Click the boxes to indicate Search acl rules and/or Search CLEAR-Flow rules.
3 Click either the Match all of the following or the Match any of the following radio button.
4 Click the More command button. A row of three fields is displayed as shown:
5 From the first (Rule Name) and second (Contains) dropdown menus, select the features on which to
search and in the text field, type specific values. For example: In the first box select “Match condition
args” and in the second box “Contains”. In the text field, type “count.” Then click the Search button.
The rules matching the search criteria are displayed in the bottom left box.
6 Click on any of the listed rules to see the raw rule text and the requested value highlighted in the
bottom right box.
7 To further refine the search, click the More button again to add another criteria row then specify the
search criteria. In this example, select “Rule Name” and “Starts with” and in the text field, type “U”
and click Search. The list of rules is reduced as seen below. Note that in the script, both “count” and
“U” are highlighted.
NOTE
The search function is not case-sensitive, but the highlighting function is.
CAUTION
The Delete command button removes a rule from the policy completely, not only in this action.
10 If desired, mark any rules using the “Mark” buttons. When the Search Policy window is closed,
these marks are displayed in the main windows.
11 To remove the search results, click the Clear command button.
Introduction
The Extreme Networks Policy Manager (EPM) is used by first creating a policy and then populating it
with ACL and CLEAR-Flow rules.
Policies and Rules can be created locally, tested and verified, and then pushed to a switch.
This chapter describes the following sections:
● Creating a New Policy on page 37
● Creating a New Rule for a Policy on page 37
● Saving a Policy on page 39
● Validating and Checking a Policy on page 40
● Importing and Exporting Rules into a Policy on page 41
1 From the Menu, choose Policy > New Policy or File > New or click the icon. The Policy Version
Selection box opens.
2 From the Versions: panel, select either 02.00.00 or 03.00.00 and click OK. A new_policy.pol (localfile)
is displayed in the Tree Structure panel.
NOTE
The version 3 policy supports access control list (ACL) and CLEAR-Flow (CF) rules.
The version 2 policy supports access control list (ACL) rules only
3 Add one or more rules to the policy as described in the following sections.
NOTE
Rules must be added to a new policy before the policy can be saved.
1 From the Menu, choose Rules > New Rule or click the icon. The Rule Wizard opens.
2 In the Rule Wizard box, make the following entries:
a In the Rule Name text box, type a name.
b From the Class Name dropdown menu, choose an existing class or type a new class name.
NOTE
If the new rule is being added to an existing policy, the dropdown menu contains selections of those class names
that are currently in the policy. If it is being added to a new policy, there are no selections and a name must be
added. Choose a name that will group all related rules.
c Click the appropriate radio button to designate an ACL or CLEAR-Flow rule. (This button is
displayed only when adding rules to a 03.00.00 version policy.)
d For additional information on rule types and class names, click the Help button. The same
information can be found in Appendix A of this manual under “Type Selection Panel” on page 68.
e Click Next
3 From the Available list box, select one or more "match conditions" and use the "Arrow" icon to move
each of them to the Selected list box.
For addition information on “match conditions”, click the Help button. The same information can be
found in Appendix A of this manual under “Match Condition Selection Panel” on page 69.
4 Click Next. A dialog box opens for the first "match condition."
5 In the text box, enter arguments for the particular “match condition.'”Note that clicking the enabled
icons under the text box provides synonyms and other variable suggestions depending on which
"match condition" was selected. The Description box also displays information consistent with the
selection.
6 Click Next. If applicable, a dialog box opens for the next "match condition." Continue the process
until arguments have been selected for each "match condition."
7 From the Available list box, select the desired true or "then" action (permit or deny) and move it to
the Selected list box.
NOTE
“Permit” is the default, so if no action is specified in a rule entry, the packet is forwarded.
8 Click Next.
9 From the Available list box, select none or one or more "action modifiers" and move them to the
Selected list box.
For addition information on “action modifiers”, click the Help button. The same information can be
found in Appendix A of this manual under “Action Modifier Selection Panel” on page 70.
10 Click Next. If action modifiers were selected, a dialog box opens.
11 From the Available list box, select the desired "arguments" for the first action modifier that was
selected in Step 9, and move them to the Selected list box. Then click Next to continue the process
for each action modifier.
12 Click Next. The text of the new rule is displayed.
13 Under the text box, check or uncheck the box Use algorithm to insert rule in optimized location.
● When checked (the default), the rule is ranked using an algorithm that calculates its best position
in the policy based on the specifics of the ACL rules. Specific rules trigger before general rules.
● When unchecked, the rule is inserted according to its position. The user can determine the
position or the rule is added to the end of the list.
14 Click Finish. The new rule is added to the policy and displayed in all of the rule viewing panels.
Use the following procedure to add a new rule in a given position in the listing. For example, add a
new # 005 after # 004.
1 In the Rule Editing and Viewing Panel, right-click anywhere in the # 004 row. A menu is displayed.
2 Choose Insert new rule (after). The Rule Wizard opens.
3 Follow Step 2 through Step 14 above.
Saving a Policy
Policies can be saved to a local file or to a switch.
1 From the Menu Bar, choose File > Save As > Local. The Save box opens.
2 In the File Name: field, type a new policy name ending in “.pol” and click Save. A Validation
Notice box is displayed that confirms the Policy rules were successfully saved and the new policy
name in displayed in the Tree Structure Panel, followed by "(localfile)."
To save to a switch:
1 From the Menu Bar, choose File > Save As > Switch. The Remote Switch Dialog box opens as
shown below.
2 Enter the required information (described on page 31) and click OK. A Policy Entry box opens as
shown below.
c Select an existing policy name from the dropdown menu. The name is then displayed in the text
field. Use this when replacing an existing policy with an updated one. The EPM displays a
warning when it is overriding an existing policy.
d To save the name you have chosen to display in the Name text field, click OK.
NOTE
The “Launch activity manager after save” box above refers to the Policy Activity Manager dialog box which is
described on page 50.
When the policy is being saved on a switch that supports CLEAR-Flow, a Validation Notice
confirming the save is displayed.
When the policy is being saved on a switch that does not support CLEAR-Flow (see “Switch
Requirements” on page 11), a CLEAR-Flow Support Notice is displayed as shown below. Click Yes
to continue the save process. CLEAR-Flow rules are displayed in the rule viewing panels but are not
supported on the switch.
The saved policy name is displayed in the Tree Structure Panel followed by the IP address of the switch.
NOTE
A policy name must be an alpha-numeric string between 1 and 32 characters in length ending in ‘.pol.’
1 From the Menu choose Policy > Validate & Check or click the icon. An Operation Progress box
is displayed, followed by either a Validation Notice if the policy has passed validation or a Policy
Validation Exception if it has not. When you are working on a switch, this function indicates that it
validates the policy and checks it on the switch.
2 When the Policy Validation Exception box is shown, click Show Details. An Exception Detail box
opens explaining why the policy did not pass validation. Possible reasons include:
■ The Policy contains no rules.
■ Parse Exception ( Last Rule Line = 1, Last Rule = n/a, Last Metadata Line = 0 ) : Unable to
parse policy because policy selection is invalid.
■ Any of the errors you would encounter running the check policy command line directly on
the switch.
Use the import function when rules are to be added from one policy to the rules in the current policy.
Use the export function when selected rules in the current policy are to replace the rules in another
existing policy or when a new policy is to be created and populated with selected rules in the current
policy.
Importing Rules
Rules imported from another policy (source) into the currently open policy (target) are merged or added
to the rules already in the existing policy.
When the rule is unique and valid, the EPM proceeds to import the rule.
When the EPM finds a problem importing a specific rule such as finding one that is common to both
policies, it prompts the user as shown in the above figure and suggests appropriate action.
4 Click the Use custom prefix for inserted rules box to add a prefix to the imported rules. Dup_ is the
default prefix but another can be used.
When the rule is of a different policy version, the EPM prompts the user as follows:
6 Click OK. The Rule Mark Notice is displayed stating that Updated and inserted rules will be
marked. (Refer to “Marking Rules” on page 44.)
7 Click OK. The new rule is displayed in all the rule viewing panels in rank order.
8 Save the policy.
Exporting Rules
Rules are exported from the currently open policy (the source) in two ways. They can be exported into
an existing policy or into a new policy that is created as part of the export process.
1 "Mark" one or more or all rules that are to be exported. (Refer to “Marking Rules” on page 44.) A
mark icon appears next to the rule name.
NOTE
Rules must be marked to be exported.
2 From the Menu Bar, choose File > Export To... > Policy File. The Save box opens.
3 Select the target policy and click Save. The Confirm Export box opens as shown below.
1 "Mark" one or more or all rules that are to be exported. (Refer to “Marking Rules” on page 44.) A
mark icon appears next to the rule name.
2 From the Menu Bar, choose File > Export To... > Policy File. The Save box opens.
3 In the File Name: field, type a new policy name ending in “.pol” and click Save. A Validation
Notice box is displayed that confirms the Policy rules were successfully exported and the new policy
is opened with all of the rules displayed.
4 Open the new policy again to see the final new policy displaying only the marked rules.
Introduction
The Extreme Networks Policy Manager (EPM) provides the capability to easily edit and modify existing
policies and rules. This chapter describes the following sections:
● Marking Rules on page 44
● Adding and Deleting Rules in a Policy on page 44
● Modifying Rules on page 45
■ Renaming a Rule
■ Reclassifying a Rule
■ Changing Rule Parameters
● Managing Global and Policy Variables on page 48
● Organizing Rules on page 49
● Deleting Policies on page 49
● Managing Policy Activity on page 50
■ Activating and Deactivating a Policy
■ Disabling a Rule
Most editing and modifying functions are accomplished using the menu that is displayed by right-
clicking a rule row in either the Rule Editing and Viewing Panel or the Rule Navigator Panel. The
complete menu is shown below:
Marking Rules
The rules in the currently open policy can be marked either for reference purposes or to select specific
rules for export. When a rule is marked, an icon is displayed in front of the rule name both in the
Rule Editing and Viewing Panel and in the Rule Navigator window. Rules can be marked using either
of the two following methods:
● In either the Rule Editing and Viewing Panel or the Rule Navigator window, right-click the desired
rule and from the resulting menu, choose Mark for only the selected rule or Mark All for all of the
rules in the policy.
● In the Rule Navigator window, click to select the desired rule and then click the Mark Selected Rule
icon .
Marked rules can be unmarked by following the same two procedures and choosing Unmark or
Unmark All from the right-click menu or in the Rule Navigator window, clicking the Clear All Marks
icon .
Adding Rules
Rules can be added to an existing policy in the following ways:
● Create a new rule as described in “Creating a New Rule for a Policy” on page 37. The new rule can
be positioned in a specific location in the rule list by right-clicking an adjacent rule and from the
dropdown menu, choosing either Insert new rule (before) or Insert new rule (after). If the position
is not selected, the rule is positioned according to its rank as determined by the algorithm.
● Import or export rules as described in “Importing and Exporting Rules into a Policy” on page 41.
● Copy a rule from one policy to another using the following procedure:
a In either the Rule Editing and Viewing Panel or the Rule Navigator window, right-click the
desired rule and from the resulting menu, choose Copy.
b Open the target policy and right-click an existing rule, then choose one of the Paste functions. The
copied rule is inserted and marked “Copy of...”
Deleting Rules
Rules can be deleted from either the Rule Editing and Viewing Panel listing in the Rule Editor window
or from the Access Control List Rules (ACL) or CLEAR-Flow Rules (CF) panel listing in the Rule
Navigator window.
1 From either list, right-click the rule that is to be deleted. The rule is highlighted and a menu is
displayed.
1 From either list, mark the rules that are to be deleted using the procedures on page 44.
2 Right-click one of the marked rules and choose Cut all marked. All marked rules are deleted.
NOTE
A policy must contain at least one rule. If the user attempts to delete all rules or the last rule from a policy, the
changes will not be saved.
NOTE
The EPM does not support “undo.”
Modifying Rules
The following changes can be made to an existing rule
Renaming a Rule
To change the name of a rule, use the following procedure:
1 In the Rule Editing and Viewing Panel or the Rule Navigator window, right-click a rule and from the
menu displayed, choose Rename. The following dialog box is displayed.
2 Enter a new name and click OK. The new name is displayed in the rule viewing panels.
Reclassifying a Rule
To change the class of a rule, use the following procedure:
1 Right-click a rule and from the menu displayed, choose Reclassify. A submenu displays available
classes from which to choose or offers the choice to <create a new class>.
2 When <create a new class> is chosen, the following Class Entry Dialog box is displayed.
3 Enter a new class name and click OK. The new class is added to the rule viewing panels and the
rule classification is changed.
To assist in the selection of arguments for count, clicking the icon as shown above, displays a list of
“rule packet counters.”
NOTE
The Enter arguments box provides different lists and reference options depending on which “match condition” or
“action” has been selected,
c Modify the parameters as needed and then click Save and Close. The parameter is changed.
Deleting parameters from a rule.
a To delete a parameter, select a parameter in either the Match Conditions, Actions, or Action
Modifiers text box. The Delete selected icon is enabled.
b Click the Delete selected icon. A Confirm Delete box is displayed, an example of which is
shown below:
NOTE
The submenu command, Refresh, is enabled only when the policy being changed is currently activated on a switch.
2 To add a variable, click the Add button. To edit a variable, select the variable that is to be edited and
click the Edit button. The following Global or Policy Variable Editing box is displayed.
3 When Add is selected, the Name and Value fields are blank. Enter the information and from the
Type dropdown menu, choose a type.
When Edit is selected, The Name and Value fields display the current settings. Make the desired
changes in the fields and in the Type dropdown menu.
4 Click Save. The new entries or modifications are displayed in the Policy or Global Manager
Variable box.
5 Make any additional additions or edits, then click Close.
Organizing Rules
Rules can be organized to function within a policy in two ways. As discussed earlier in the rule creation
process (on page 38), the user can either determine the order in which the rules are to be read or call the
EPM algorithm that assigns an efficient order based on the specificity of the rules. The existing rule
order can then be changed in the following ways.
● Reassign rule ranks using the EPM algorithm by choosing Policy > Recalculate rule ranks from the
menu. Use this command when rules have been added or deleted from an existing policy or when
the original ranks were determined without using the algorithm.
● Rearrange the rules according to rank. by choosing Policy > Reorder rules by rank. When this
command is chosen, the following box is displayed allowing the user to maintain the existing
ranking or change it.
● Return all rules to their original order by choosing Policy > Reorder rules by initial position. When
this command is chosen, a Rule Location Notice box is displayed stating that "Any new rules added
since the policy was loaded will appear at the top of the rule list in all views."
Deleting Policies
Policies are deleted from the policy folder in the program files rather than through the EPM application.
1 From the menu, choose Policy > Activity.... A Policy Activity Manager dialog box is displayed as
shown below.
2 To activate the policy on a port, click the Activate Port command button. The following Policy
Activity - Activate Port(s) dialog box opens.
3 From the Available list of ports, select a port and using the arrow command button transfer it to the
Selected text box. Select additional ports as needed. Click the Ingress or Egress radio buttons and
then Save and Close. The box closes and in the Active Ports panel, the port number, ingress or
egress and the Policy name are displayed.
4 Continue the process, selecting additional ports (egress or ingress) and VLANs as desired. All are
displayed in the Policy Activity Manager dialog box.
5 When all desired ports and VLANs have been selected, click the now enabled Commit command
button and when the process is completed, Close the box. Under the Rule Activity tab, the port and
VLAN commitments are shown.
To view all the policies that are currently committed to the ports or VLANs, use the following
procedure.
1 Choose Policy > Activity... to open the Policy Activity Manager dialog box.
2 Click the Show All command button to view the following dialog box. The Show All button is a
toggle button that, when selected, shows the VLANs and ports that are activated for policies other
than the policy that is currently loaded in the EPM. All VLANs and ports that are active for the
current policy are shown in black, and all other active VLANs and ports are shown in red.
The Active Vlans field displays the name of each active VLAN, the direction (egress or ingress), and
the name of the policy activated on that VLAN.
The Active Ports field displays the number of each active port, the direction, and the name of the
policy activated on that port.
3 To return to the current policy only, click the Show All button again.
1 Choose Policy > Activity... to open the Policy Activity Manager dialog box. The commitments for
the current policy are shown.
2 The deactivate command buttons show the available options. Click the desired option (Deactivate
Ingress, Deactivate Egress, Deactivate Selected, or Deactivate All) then click the Commit command
button. The policies are deactivated.
Disabling a Rule
Rules are normally enabled with the policy. However, one or more individual rules within a policy can
be disabled by using the following procedure:
1 In the Rule Editing and Viewing Panel or the Rule Navigator Window, right-click the rule to be
disabled and from the resulting menu, choose Disable. The rule appears in red.
2 To re-enable the rule, repeat the process in Step 1, selecting Enable from the menu.
NOTE
Each of the following two examples consists of a series of connected procedures. Each procedure begins in the state
where the previous one ended. If a procedure is used out of the order that is displayed here, the results may be
affected.
Example 1—Example_TCP_Threshold.pol
This TCP_Threshold example is a simple policy demonstrating the ability to show CLEAR-Flow rules
that detect TCP traffic that exceeds a minimum threshold.
Save to a Switch
1 Before saving a policy to a switch, make certain that the configuration steps, as described on page 11
and on page 18 have been taken.
2 From the menu, choose File > Save As > Switch.
3 In the Remote Switch Dialog box, enter the required information. (For more detail, see "To Save to a
Switch on page 39.")
4 When the Policy Entry dialog box opens, it prompts with the policy name that was used locally.
That name is accepted here by clicking OK. (For other options, see “Saving a Policy” on page 39.)
This box includes an option to open the Activity Manager dialog after the policy is saved. In this
case, it was not selected.
(This example is being run on a switch that does not support CLEAR-Flow. Therefore, a CLEAR-
Flow Support Notice box opens with a reminder of that limitation and the question of whether to
proceed. Yes is selected.)
1 From the menu, choose Policy > Activity.... The Policy Activity Manager dialog box opens.
2 Click the Activate Port command button. The Policy Activity - Activate Port(s) dialog box opens as
shown below.
3 Transfer port 16 from the Available list to the Selected box using the arrow command buttons. Click
the Ingress radio button and then Save and Close. Port 16 is now displayed in the Active Ports field
as shown below.
4 See the notation in red stating that "Recent changes have not been committed to the switch
configuration!" Click the Commit command button. A Commit Confirmation box opens.
5 Click Yes. The now disabled Commit command button indicates that the changes have been
committed to the switch.
6 See the change also in the Status Panel. It shows that the policy is activated on Port 16 and the
direction is ingress.
7 Click the Show All command button. As shown below, the current policy is shown in black, and all
other ports and/or VLANs with activated policies are shown in red.
8 Click the Show All command button again to show only the currently edited policy.
9 Close the dialog box.
5 Replace "100" with "200" then click Save and Close. The change is displayed in the "Match
Conditions" text panel and in the raw rule text of the other rule viewing panels.
6 From the menu, choose Policy > Refresh. The following Refresh Confirmation box is displayed.
7 Click Yes. An Operation Progress box is displayed followed by a Validation Notice stating that the
"Policy has been refreshed."
NOTE
The submenu command, Refresh, is enabled only when the policy being changed is currently activated on a switch.
Example 2—Example_TCP_UDP_Balance.pol
This example uses two ACL rules and one CLEAR-Flow rule to track the ratio of TCP to UCP packets.
5 Click the Rules by class tab to see the relationship between the two classes and the three rules.
In this example, the user is looking for a ACL rule with a "COUNTER" action to be referenced with a
CLEAR-Flow rule. To find it, use the following procedure:
1 From the tool bar, click the "Search Policy" icon . The Search Policy dialog box opens.
2 Deselect the Search CLEAR-Flow rules check box and click the More command button. A search
criteria row of three fields is displayed.
3 From the Rule Name dropdown menu, choose Action modifier args; leave the Contains list as is,
and type "COUNTER" in the text field. Then click Search. Two rules matching the criteria
(ACL_UDP and ACL_TCP) are displayed in the lower left text box.
4 Click one of the rules. The raw rule text is displayed in the right box with COUNTER highlighted. It
is also displayed in the other rule viewing panels.
5 When there are many hits, use another criterion to refine the search, in this case, to specify the UDF
protocol. Click More and a new search criteria row is displayed.
6 From the Rule Name menu, choose Match condition args; leave the Contains list as is, and type
UDP in the text field. Then click Search. The following screen is displayed showing both criteria
highlighted.
NOTE
The search function is not case-sensitive, but the highlighting function is.
7 Close the Search Policy box. (The search procedure is not saved.)
1 Right-click the now selected rule and choose Copy from the resulting menu. Close the current (or
source) policy and open the policy into which the rule is to be copied (target). Right-click an existing
rule and choose the desired Paste command from the menu.
NOTE
The Copy/Paste function can be used only with an already populated policy.
When one or more rules that were found are to be the beginning of a new policy, the export function
simplifies the process. Use the following procedure.
1 In this example, mark the rule either from the Search Policy box, before closing, or from the right-
click menu. From the menu, choose File > Export To... > Policy File. In the Save box that opens, type
a new file name (in this case ExportTest.pol) and click Save. When the export is successful, a
Validation Notice is displayed confirming the export. Click OK. From the menu, choose File > Open
> Local and select ExportTest.pol to see the new policy with the rule, ACL_UDP. Additional rules
can be added either by creating new ones, using copy/paste from other policies, importing and/or
exporting.
2 When the new policy is complete, it can be validated. From the menu, choose Policy > Validate &
Check. The EPM checks the policy and validates it or returns notice of problems.
3 Save the new policy to a switch when it is complete.
4 Exit the EPM.
Introduction
This appendix includes Help messages and other reference material that appear in the Extreme
Networks Policy Manager (EPM). These are cross-referenced in this manual from the procedure to
which they apply.
For additional description of this material, refer to the ExtremeXOS Concepts Guide and the ExtremeXOS
Command Reference Guide.
Included are:
sys_IcmplnErrors counterreference
sys_IcmplnDestUnreachs counterreference
sys_IcmplnTimeExcds counterreference
sys_IcmplnParmProbs counterreference
sys_IcmplnSrcQuenchs counterreference
sys_IcmplnRedirects counterreference
sys_IcmplnEchos counterreference
sys_IcmplnEchoReps counterreference
sys_IcmplnTimestamps counterreference
sys_IcmplnTimestampReps counterreference
sys_IcmplnAddrMasks counterreference
sys_IcmplnAddrMaskReps counterreference
sys_IcmpOutMsgs counterreference
sys_IcmpOutErrors counterreference
sys_IcmpOutDestUnreachs counterreference
sys_IcmpOutTimeExcds counterreference
sys_IcmpOutParmProbs counterreference
sys_IcmpOutSrcQuenchs counterreference
sys_IcmpOutRedirects counterreference
sys_IcmpOutEchos counterreference
sys_IcmpOutEchoReps counterreference
sys_IcmpOutTimestamps counterreference
sys_IcmpOutTimestampReps counterreference
sys_IcmpOutAddrMasks counterreference
sys_IcmpOutAddrMaskReps counterreference
sys_IcmplnProtoUnreachs counterreference
sys_IcmplnBadLen counterreference
sys_IcmplnBadCode counterreference
sys_IcmplnTooShort counterreference
SYS_IcmpOutProtoUnreachs counterreference
sys_IcmpOutRouterAdv counterreference
sys_IgmplnQueries counterreference
sys_IgmplnReports counterreference
sys_IgmplnLeaves counterreference
sys_IgmplnErrors counterreference
sys_IgmpOutQueries counterreference
sys_IgmpOutReports counterreference
sys_IgmpOutLeaves counterreference
ethernet-type: Ethernet packet type. In place of the numeric value, you can specify one of the following text
synonyms (the field values are also listed): ETHER-P-IP (0x0800), ETHER-P-8021Q (0x8100),
ETHER-P-IPV6 (0x86DD).
ethernet-source-address Ethernet source MAC address.
ethernet-destination-address Ethernet destination MAC address and mask. The mask is optional, and is in the same format as
the MAC address. Only those bits of the MAC address whose corresponding bit in the mask is
set to 1 will be used as match criteria. So, the example above will match 00:01:02:03:xx:xx. If
the mask is not supplied then it will be assumed to be ff:ff:ff:ff:ff:ff. In other words, all bits of
the MAC address will be used for matching.
source-address: IP source address and mask. Egress ACLs do not support IPv6 addresses, only IPv4 addresses.
Use either all IPv4 or all IPv6 addresses in an ACL.
destination-address: IP destination address and mask. Egress ACLs do not support IPv6 addresses, only IPv4
addresses. Use either all IPv4 or all IPv6 addresses in an ACL.
protocol: IP protocol field. In place of the numeric value, you can specify one of the following text
synonyms (the field values are also listed): egp(8), esp(5), gre(47), icmp(1), igmp(2), ipip(4),
ipv6(41), ospf(89), pim(102), rsvp(46), tcp(6), or udp(17).
fragments: BlackDiamond 10K and BlackDiamond 12804 only. Specifies IP fragmented packet. FO > 0
(FO = Fragment Offset in IP header).
first-fragments: Non-IP fragmented packet or first fragmented packet. FO==0.
source-port: TCP or UDP source port. In place of the numeric value, you can specify one of the text
synonyms. Normally, you specify this match in conjunction with the protocol match to
determine which protocol is being used on the port. In place of the numeric value, you can
specify one of the following text synonyms (the field values are also listed): afs(1483),
bgp(179), biff(512), bootpc(68), bootps(67), cmd(514), cvspserver(2401), DHCP(67),
domain(53), eklogin(2105), ekshell(2106), exec(512), finger(79), ftp(21), ftp-data(20), http(80),
https(443), ident(113), imap(143), kerberos-sec(88), klogin(543), kpasswd(761), krb-prop(754),
krbupdate(760), kshell(544), idap(389), login(513), mobileip-agent(434), mobileip-mn(435),
msdp(639), netbios-dgm(138), netbiosns( 137), netbios-ssn(139), nfsd(2049), nntp(119),
ntalk(518), ntp(123), pop3(110), pptp(1723), printer(515), radacct(1813), radius(1812), rip(520),
rkinit(2108), smtp(25), snmp(161), snmptrap(162), snpp(444), socks(1080), ssh(22),
sunrpc(111), syslog(514), tacacs-ds(65), talk(517), telnet(23), tftp(69), timed(525), who(513),
xdmcp(177), zephyr-clt(2103), or zephyr-hm(2104).
destination-port: TCP or UDP destination port. Normally, you specify this match in conjunction with the protocol
match to determine which protocol is being used on the port. In place of the numeric value, you
can specify one of the following text synonyms (the field values are also listed): afs(1483),
bgp(179), biff(512), bootpc(68), bootps(67), cmd(514), cvspserver(2401), DHCP(67),
domain(53), eklogin(2105), ekshell(2106), exec(512), finger(79), ftp(21), ftp-data(20), http(80),
https(443), ident(113), imap(143), kerberos-sec(88), klogin(543), kpasswd(761), krb-prop(754),
krbupdate(760), kshell(544), idap(389), login(513), mobileip-agent(434), mobileip-mn(435),
msdp(639), netbios-dgm(138), netbiosns( 137), netbios-ssn(139), nfsd(2049), nntp(119),
ntalk(518), ntp(123), pop3(110), pptp(1723), printer(515), radacct(1813), radius(1812), rip(520),
rkinit(2108), smtp(25), snmp(161), snmptrap(162), snpp(444), socks(1080), ssh(22),
sunrpc(111), syslog(514), tacacs-ds(65), talk(517), telnet(23), tftp(69), timed(525), who(513),
xdmcp(177), zephyr-clt(2103), or zephyr-hm(2104).
tcp-flags: TCP flags. Normally, you specify this match in conjunction with the protocol match statement.
In place of the numeric value, you can specify one of the following text synonyms (the field
values are also listed): ACK(0x10), FIN(0x01), PUSH(0x08), RST(0x04), SYN(0x02),
URG(0x20), SYN_ACK(0x12).
igmp-msg-type: IGMP message type. Possible values and text synonyms: v1- report(0x12), v2-report(0x16), v3-
report(0x22), V2-leave (0x17), or query(0x11).
icmp-type: ICMP type field. Normally, you specify this match in conjunction with the protocol match
statement. In place of the numeric value, you can specify one of the following text synonyms
(the field values are also listed): echo-reply(0), echorequest( 8), info-reply(16), info-request(15),
mask-request(17), mask-reply(18), parameter-problem(12), redirect(5), routeradvertisement( 9),
router-solicit(10), source-quench(4), timeexceeded( 11), timestamp(13), timestamp-reply(14), or
unreachable(3).
icmp-code: ICMP code field. This value or keyword provides more specific information than the icmp-type.
Because the value's meaning depends upon the associated icmp-type, you must specify the
icmp-type along with the icmp-code. In place of the numeric value, you can specify one of the
following text synonyms (the field values also listed); the keywords are grouped by the ICMP
type with which they are associated: Parameter-problem: ip-header-bad(0), required-option-
missing(1) Redirect: redirect-for-host (1), redirect-for-network (2), redirect-for-tosand- host (3),
redirect-for-tos-and-net (2) Time-exceeded: ttl-eq-zero-during-reassembly(1), ttl-eq-zero-during-
transit(0) Unreachable: communication-prohibited-by-filtering(13), destination-hostprohibited(
10), destination-host-unknown(7), destinationnetwork- prohibited(9), destination-network-
unknown(6), fragmentation-needed(4), host-precedence-violation(14), hostunreachable( 1), host-
unreachable-for-TOS(12), networkunreachable( 0), network-unreachable-for-TOS(11),
portunreachable( 3), precedence-cutoff-in-effect(15), protocolunreachable( 2), source-host-
isolated(8), source-route-failed(5)
ip-tos: IP TOS field. In place of the numeric value, you can specify one of the following text synonyms
(the field values are also listed): minimize-delay 16 (0x10), maximize-reliability 4(0x04),
minimize-cost2 (0x02), and normal-service 0(0x00).
dscp Differentiated Service Code Point. The DiffServ protocol uses the type of service (TOS) byte in
the IP header, and the most significant six bits of this type form the DSCP. In place of the
numeric value, you can specify one of the following text synonyms (the field values are also
listed): The Expedited Forwarding RFC defines one code point: ef(46) The Assured Forwarding
RFC defines 4 classes, with 3 drop precedences in each class, for a total of 12 code points:
af11(10), af12(12), af13(14), af21(18), af22(20), af23(22), af31(26), af32(28),af33(30), af41(34),
af42(36), af43(38).
count:
Increments the counter named in the action modifier (ingress only). A number of packet statistics are
gathered by the XOS kernel. To allow you to use these statistics in CLEAR-Flow expressions, these
kernel counters are now available for use with CLEAR-Flow. Most of the counter names are based
directly on well known names from common kernel structures and MIBs. The names are modified from
their familiar form by prepending the characters sys_ to the counter names.
Available Counters:
sys_IpInReceives - The total number of input IP packets received from interfaces, including those
received in error.
sys_IpInHdrErrors - The number of input IP packets discarded due to errors in their IP headers,
including bad checksums, version number mismatch, other format errors, timeto- live exceeded, errors
discovered in processing their IP options, etc.
sys_IpInAddrErrors - The number of input IP packets discarded because the IP address in their IP
header's destination field was not a valid address to be received at this entity. This count includes
invalid addresses (for example, 0.0.0.0) and addresses of unsupported Classes (for example, Class E).
sys_IpForwDatagrams - The number of input IP packets for which this entity was not their final IP
destination, as a result of which an attempt was made to find a route to forward them to that final
destination.
sys_IpInDiscards - The number of input IP packets for which no problems were encountered to prevent
their continued processing, but which were discarded (for example, for lack of buffer space). Note that
this counter does not include any IP packets discarded while awaiting re-assembly.
sys_IpOutRequests - The total number of IP packets which local IP user-protocols (including ICMP)
supplied to IP in requests for transmission. Note that this counter does not include any IP packets
counted in ipForwDatagrams.
sys_IpOutDiscards - The number of output IP packets for which no problem was encountered to
prevent their transmission to their destination, but which were discarded (for example, for lack of buffer
space). Note that this counter would include IP packets counted in ipForwDatagrams if any such
packets met this (discretionary) discard criterion.
sys_IpOutNoRoutes - The number of IP packets discarded because no route could be found to transmit
them to their destination. Note that this counter includes any packets counted in ipForwDatagrams
which meet this `no-route' criterion.
sys_IpReasmTimeout - The maximum number of seconds which received fragments are held while
they are awaiting reassembly at this entity.
sys_IpReasmFails - The number of failures detected by the IP re-assembly algorithm (for whatever
reason: timed out, errors, etc.). Note that this is not necessarily a count of discarded IP fragments since
some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by
combining them as they are received.
sys_IpFragOKs - The number of IP packets that have been successfully fragmented at this entity.
sys_IpFragFails - The number of IP packets that have been discarded because they needed to be
fragmented at this entity but could not be, for example, because their Don't Fragment flag was set.
sys_IpFragCreates - The number of IP packet fragments that have been generated as a result of
fragmentation at this entity.
sys_IcmpInMsgs - The total number of ICMP messages which the entity received. Note that this
counter includes all those counted by icmpInErrors.
sys_IcmpInErrors - The number of ICMP messages which the entity received but determined as having
ICMP-specific errors (bad ICMP checksums, bad length, etc.).
sys_IcmpOutMsgs - The total number of ICMP messages which this entity attempted to send. Note that
this counter includes all those counted by icmpOutErrors.
sys_IcmpOutErrors - The number of ICMP messages which this entity did not send due to problems
discovered within ICMP such as a lack of buffers. This value should not include errors discovered
outside the ICMP layer such as the inability of IP to route the resultant datagram. In some
implementations there may be no types of error which contribute to this counter's value.
sys_IcmpInBadCode - The number of incoming ICMP packets with a bad code field value.
sys_IgmpInQueries - The number of Host Membership Query messages that have been received on this
interface.
sys_IgmpInReports - The number of Host Membership Report messages that have been received on
this interface for this group address.
sys_IgmpInLeaves - The number of incoming IGMP leave requests. sys_IgmpInErrors - The number of
incoming IGMP errors.
sys_IgmpOutQueries - The number of Host Membership Query messages that have been sent on this
interface
sys_IgmpOutReports - The number of Host Membership Report messages that have been sent on this
interface for this group address.
cvid:
Modifies the C-VID value. In the field, the value must be a positive integer number.
link-aggregation-hash:
Controls which link is used by matching VMAN traffic (egress only). In the field, the value must be a
positive integer number.
qosprofile:
Forwards the packet to the specified QoS profile (ingress only). The profile name must be one of the
default profiles. Values of “QP1” to “QP8” are allowed.
scos:
Modifies the S-COS value. In the field, the value must be a positive integer number.
stag-ethertype:
Modifies the VMAN Ethertype value, also called the S-Tag value. In the field, the value must be a
positive integer number.
svid:
Modifies the S-VID value. In the field, the value must be a positive integer number.
traffic-queue:
Places the traffic on the specified traffic-queue (Black Diamond 12804R only)
uplinkport:
Modifies the uplink port. In the first field, enter “tagged” or “untagged” or leave it empty for all traffic.
In the second field, enter a single number or a list separated by commas.
redirect:
Used to redirect packets (BlackDiamond 10K and BlackDiamond 12804 Only). Packets are forwarded to
the IPv4 address specified, without modifying the IP header. The IPv4 address must be in the IP ARP
cache, otherwise the packet is forwarded normally. Only fast path traffic can be redirected. This
capability can be used to implement Policy Based Routing. You may want to create a static ARP entry
for the redirection IP address, so that there will always be a cache entry.
mirror:
Sends a copy of the packet to the monitor (mirror) port (ingress only).
mirror-cpu:
replace-dscp:
Replace the packets DSCP field with the value from the associated QoS profile.
replace-dot1p:
Replace the packets 802.1p field with the value from the associated QoS profile.
log:
log-raw:
meter:
The meter keyword allows you to associate a meter with an ACL. The meter must be created outside of
the EPM using the command line.
permit Changes the existing ACL to permit. All packets that match the conditional
statements of the specified ACL are allowed to pass to their destinations.
deny Changes the existing ACL to deny. All packets that match the conditional
statements of the specified ACL are dropped.
qosprofile Modifies an existing ACL to set the QoS profile for traffic that matches that
rule.
mirror This action modifies an existing ACL rule to mirror traffic that matches that
rule, or to stop mirroring that traffic. The mirroring port must be enabled when
mirroring on an ACL rule is turned on. This could be configured earlier, or use
the CLI action to execute CLI commands to configure mirroring at the same
time.
cli This action executes a CLI command. There is no authentication or checking
the validity of each command. If a command fails, the CLI will log a message
in the EMS log. The message (FieldOne) must be placed in quotes.
snmptrap This action sends an SNMP trap message to the trap server, with a
configurable ID and message string, when the rule is triggered. The message is
sent periodically with interval <period> seconds. If <period> is 0, or if this
optional parameter is not present, the message is sent only once when the rule
is triggered. The interval must be a multiple of the rule sampling/evaluation
interval, or the value will be rounded down to a multiple of the rule sampling/
evaluation interval. The message (FieldTwo) must be placed in quotes.
syslog This action sends log messages to the ExtremeXOS EMS sever. The possible
values for message level are: DEBU, INFO, NOTI, WARN, ERRO, and CRIT.
The message is sent periodically with interval <period> seconds. If <period> is
0, or if this optional parameter is not present, the message is sent only once
when the rule is triggered. The interval must be a multiple of the rule
sampling/evaluation interval, or the value will be rounded down to a multiple of
the rule sampling/evaluation interval. The messages are logged on both MSMs,
so if the backup log is sent to the primary MSM, then the primary MSM will
have duplicate log messages. The message (FieldOne) must be placed in
quotes.
global-rule The global-rule statement is optional and affects how the counters are treated.
An ACL that defines counters can be applied to more than one interface. In
the original release of CLEAR-Flow, however, any counters used in an
expression were only evaluated for that particular interface that the CLEAR-
Flow rule was applied to. Beginning with the ExtremeXOS 11.2 release, you
can specify the global-rule statement so that counters are evaluated for all the
applied interfaces. For example, if a policy that defines a counter is applied to
port 1:1 and 2:1, a CLEAR-Flow rule that used the global-rule statement would
sum up the counts from both ports. Without the global-rule statement, the
CLEAR-Flow rule would only look at the counts received on one port at a time.
count A CLEAR-Flow count expression compares a counter with the threshold value.
Beginning in ExtremeXOS release 11.4, the value of <countThreshold> and
<hysteresis> can be specified as floating point numbers. The count
statement specifies how to compare a counter with its threshold. The
<counterName> is the name of an ACL counter referred to by an ACL rule
entry and the <countThreshold> is the value compared with the counter.
The REL_OPER is selected from the relational operators for greater than,
greater than or equal to, less than, or less than or equal to (>, >=, <, <=). The
hysteresis <hysteresis> statement is optional, and sets a hysteresis value
for the threshold. After the count statement is true, the value of the threshold
is adjusted so that a change smaller than the hysteresis value will not cause
the statement to become false. For statements using the REL_OPER > or >=,
the hysteresis value is subtracted from the threshold; for < or <=, the
hysteresis value is added to the threshold.
delta A CLEAR-Flow delta expression computes the difference from one sample to
the next of a counter value. This difference is compared with the threshold
value. Beginning in ExtremeXOS release 11.4, the value of
<countThreshold> and <hysteresis> can be specified as floating point
numbers. The delta expression specifies how to compare the difference in a
counter value from one sample to the next with its threshold. The
<counterName> is the name of an ACL counter referred to by an ACL rule
entry and the <countThreshold> is the value compared with the difference
in the counter from one sample to the next. The REL_OPER is selected from
the relational operators for greater than, greater than or equal to, less than, or
less than or equal to (>, >=, <, <=).
ratio A CLEAR-Flow ratio expression compares the ratio of two counter values with
the threshold value. Beginning in ExtremeXOS release 11.4, the value of
<countThreshold> and <hysteresis> can be specified as floating point
numbers, and the ratio is computed as a floating point number. The ratio
statement specifies how to compare the ratio of two counters with its
threshold. The value of <counterNameA> is divided by the value of
<counterNameB>, to compute the ratio. That ratio is compared with the
<countThreshold>. The REL_OPER is selected from the relational operators
for greater than, greater than or equal to, less than, or less than or equal to (>,
>=, <, <=). The min-value statement is optional, and sets a minimum value for
the counters. If either counter is less than the minimum value, the expression
evaluates to false. If not specified, the minimum value is 1.
delta-ratio A CLEAR-Flow delta-ratio expression is a combination of the delta and ratio
expressions. The CLEAR-Flow agent computes the difference from one sample
to the next for each of the two counters. The ratio of the differences is then
compared to the threshold value. Beginning in ExtremeXOS release 11.4, the
value of <countThreshold> and <hysteresis> can be specified as
floating point numbers, and the delta-ratio is computed as a floating point
number. The delta-ratio statement specifies how to compare the ratio of
the counter differences with its threshold. The difference of the sample values
of <counterNameA> is divided by the difference of the sample values of
<counterNameB>, to compute the ratio that is compared with the
<countThreshold>. The REL_OPER is selected from the relational operators
for greater than, greater than or equal to, less than, or less than or equal to (>,
>=, <, <=).
rule-true-count A CLEAR-Flow rule-true-count expression compares how many times a CLEAR-
Flow rule is true with a threshold value. One use is to combine multiple rules
together into a complex rule. The rule-true-count statement specifies how
to compare how many times a CLEAR-Flow rule is true with the expression
threshold. The <ruleName> is the name of the CLEAR-Flow rule to monitor
and the <countThreshold> is the value compared with the number of times
the rule is true. The REL_OPER is selected from the relational operators for
greater than, greater than or equal to, less than, or less than or equal to (>,
>=, <, <=).
Introduction
This appendix includes suggestions for dealing with problems that may occur when running the
Extreme Networks Policy Manager (EPM). They are categorized as follows:
Connectivity Problems
When there is failure opening or saving policy file on a switch, check the following:
● Check the network connection to the switch by pinging the switch
● Check that the local IP address is correct.
● Check that the NAT address is set if the client is on the outside of a NAT.
● Check that the TFTP server is running on the client and listing on port 69.
● Check that the file staging directory is set to the TFTP server’s root directory.
● Check that the user running the EPM has read/write permission to the TFTP server’s root directory.
● Check the client firewalls
● Check that the SSH image is loaded and that it has been enabled.
● Check the user name and password. They are case-sensitive.
● Check the default routes on the switch and client.
● Verify that the client has at least 1 GB of memory. The EPM requires up to 512 MB of available
memory but functions better with 1 GB.
● Terminate any other applications that may be consuming memory and restart the EPM. Verify that it
executes correctly.
● Verify that the CPU is not “swamped” with other intensive processing tasks. Reduce the other tasks
and restart the EPM. Verify that the EPM executes correctly.
● Verify that the user specified version 3 when opening an external policy file. If not, reopen the policy
with the correct version.
● Verify that the policy file looks like a reasonable Extreme policy file.
SSH Problems
When the EPM has connection problems, use the following procedure.
To terminate and restart SSH process during a software upgrade on the switch
Symbols E
#, definition, 27 editing
rule parameters, 46
A rules, 43
EPM
Access Control List (ACL) Rules panel, 29 desktop, 20
Access Control Lists see ACLs launching, 15
ACLs, 9 modes, 15
Action Modifier Selection Panel opening, 15
reference list, 70 eSupport Website link, 20
Actions tab, 24 exporting rules, 42
activate a policy Extreme Networks Policy Manager see EPM
example, 55
procedure, 50 G
activated policy, changing, 47
adding, 44 global variables, 48
global and policy variables, 48 adding, 47
rule parameters, 46 deleting, 47
rules, 44 modifying, 47
Alerts tab, 23
arrow icons, 30 H
C hardware requirements, 11
changing I
activated policy, 47
rule parameters, 46 icons
class, definition, 27 arrows (vertical), 30
CLEAR-Flow (CF) notice, 7
description, 9 toolbar, 23
Rules panel, 29 importing rules, 41
conventions installation procedure, 13
text, 8
creating L
new policies, 37
launching the EPM, 15
new rule, 37
local mode
opening a policy, 30
D saving a policy, 39
deactivate Log tab, 24
policies, 51
deleting M
policies, 49
marking rules, 44
rule parameters, 47
Match Condition Selection Panel
rules, 44
reference list, 69
disable rules, 52
menu bar, 21
N type, 27
Rule Editor Window, 26
name, definition, 27 Rule Editing and Viewing Panel, 27
NAT IP address, setting, 18 Rule Properties Panel, 28
Tree Structure Panel, 27
O Rule Information tab, 28
Rule Navigator Window, 29
opening a policy, 30 Access Control List (ACL) Rules panel, 29
opening the EPM, 15 CLEAR-Flow (CF) Rules panel, 29
organizing rules, 49 rule parameters
adding, 46
P changing, 46
deleting, 47
parsing, 32
editing, 46
policies
Rule Parameters tab, 28
activate, 50
Rule Properties Panel, 28
creating, 37
Rule Information tab, 28
deactivate, 51
Rule Parameters tab, 28
deleting, 49
rule rank
invalid, 32
definition, 27
parsing, 32
recalculate, 49
validating, 40
reorder by, 49
Policy Information tab, 24
rules, 44
Policy Validation Exception box, 40
creating, 37
policy variables, 48
deleting, 44
policy, opening
disable, 52
locally, 30
importing and exporting, 41
switch, 31
marking, 44
Predefined CLEAR-Flow System Counters
organizing, 49
reference list, 63
reclassifying, 45
renaming, 45
R searching, 33
rank see rule rank
reclassifying a rule, 45 S
refresh
saving a policy, 39
description, 21, 47
searching for rules in a policy, 33
example, 58
set file search directory, 19
related publications, 8
set file staging directory, 18
Release Notes, 7
software requirements, 11
renaming a rule, 45
SSH (Secure Shell) module, 12
requirements
Status Bar, 25
hardware, 11
Status Panel
software, 11
Actions tab, 24
SSH, 12
Alerts tab, 23
switch, 11
description, 23
TFTP server, 12
Log tab, 24
Rule Activity tab, 25
Policy Information tab, 24
Rule Editing and Viewing Panel, 27
Rule Activity tab, 25
#, 27
status, definition, 27
class, 27
switch mode
name, 27
opening a policy, 31
rank, 27
saving a policy, 39
status, 27
switch requirements, 11
TCNT, 27
T
TCNT, definition, 27
text conventions, 7
TFTP server, 12
toolbar icons, 23
Tree Structure Panel, 27
Trigger Count see TCNT
Trivial File Transfer Protocol see TFTP
troubleshooting, 77
Type Selection Panel
reference, 68
type, definition, 27
V
validate a policy, 40
variables
global, 48
policy, 48