Filter profiles are sets of rules that determine whether to accept or discard packets transiting on either a switch or wireless radio interface.
Use the Manage Filter Profiles page to create new wired Filter profiles and manage existing Filter profiles.
This topic describes:
From the Manage Filter Profiles page, you can:
Note: You cannot delete profiles that are in use—that is, profiles assigned to objects or used by other profiles. To see the current assignments for a profile, select the profile and click Details.
Table 117 describes the information provided about wired Filter profiles on the Manage Filter Profiles page. This page lists all Filter profiles defined for your network, regardless of the scope you selected in the network view.
Table 117: Manage Wired Filter Profile Fields
Field | Description |
---|---|
Profile Name | Name given to the profile when the profile was created. |
Family Type | The device family on which the profile was created: Switching (EX), Campus Switching ELS, or Data Center Switching Non-ELS. |
Description | Description of the profile entered when the profile was created. Tip: To display the entire description, you might need to resize the Description column by clicking the column border in the heading and dragging it. |
Creation Time | Date and time when the profile was created. |
Last Updated Time | Date and time when the profile was last modified. |
User Name | The username of the user who created or modified the profile. |
Note: All columns might not be displayed. To show or hide fields in the table, click the down arrow on the field header, select Columns, and select or clear the check box adjacent to the field that you want to show or hide.
To create a wired Filter profile, you must provide a filter name and configure at least one term. A term is a collection of one or more match conditions, and actions that the system takes when match conditions are met. A term must have at least one match condition.
To create a wired Filter profile:
Note: Do not select Dashboard View, Datacenter View, or Topology View.
Network Director opens the Device Family Chooser window.
The Create Filter Profile wizard for the selected device family is displayed.
The system saves the Filter profile and displays the Manage Filter Profiles page. Your new or modified Filter profile is listed in the table of Filter profiles.
A Filter profile must have at least one term in it. Each term has one filtering function. For example, if a term is evaluating the source of packets, then that term cannot also evaluate the protocols used by the packets. Some switch models do accommodate multiple terms in one filter. When you have more than one term in a filter, the ordering of the terms is important. The system evaluates multiple filter terms as follows:
To configure a Filter profile for EX Series switches:
The Create Term window opens, displaying a section for each type of term you can create, Source and Destination Parameters, Protocols, DSCP Settings, TCP Settings, and ICMP Settings. The Action section applies to all of those types.
Note: The order of the terms within a Filter profile configuration is important. Packets are tested against each term in the order in which terms are listed.
Table 118: Create Term Fields for EX Switching
Task | Description |
---|---|
Source and Destination
Parameters You can specify match conditions for either packets’ origin (source) or packets’ destination, or both. You are indicating the location of the filtering here—either specifying that packets that originate at a specific place (source) will be filtered or packets destined for a specific location (destination) will be filtered. You can have multiple sources and destinations for one filter term. | |
Add Source Parameters and Destination Parameters | ProcedureTo add source and destination parameters to the named filter term:
|
Protocols and
EtherTypes For either INET family, you can apply a filter term based on protocols being used by packets. For the Ethernet-switching family, you can apply a filter term based on either the protocols being used by packets or on the EtherTypes being used by packets. EtherType indicates a protocol that is encapsulated in the payload of an Ethernet Frame. Expand the Protocols section to see the configuration. | |
Add a Protocol Match Condition | ProcedureTo add a protocol match condition to the named filter term:
|
Add an EtherType Match Condition | ProcedureTo add an EtherType match condition to the named filter Ethernet-switching family term:
|
DSCP Settings Expand this section to see the DSCP term settings. DiffServ is a simple mechanism for classifying and managing network traffic and providing quality-of-service (QoS) on IP networks. DiffServ can, for example, be used to apply low-latency to critical network traffic such as voice or streaming media while providing simple best-effort service to non-critical services such as Web traffic. Here, you can apply a filter term based on the Differentiated Services code point (DSCP) which is a field in IPv4 and IPv6 headers. Note: With IPv6 packets, the DS field and ECN field replace the IPv4 TOS field. | |
Add a DSCP Match Condition | ProcedureTo add a DSCP match condition to the named filter term: Note: A DSCP IP match condition and a precedence match condition cannot be both specified for the same term.
|
Add a Precedence match condition | You can apply an IP precedence match condition to the named term. With IP precedence, a device prioritizes traffic by class first. Then it differentiates and prioritizes same-class traffic. Note: The two match conditions IP Precedence and DSCP cannot be simultaneously applied to a term. ProcedureTo apply an IP precedence value match condition to the named term:
|
TCP Settings Expand this section to see the TCP term settings. The Transmission Control Protocol (TCP) is the most common core protocol of the Internet protocol suite (IP). TCP provides reliable, ordered, error-checked delivery of a stream of octets between programs running on computers connected to the Internet or an intranet. You can use the TCP initial flag for a match condition. | |
Enable TCP Initial flag match condition | Select to use the TCP initial flag for a match condition. The TCP flags option becomes unavailable as a result. |
Enable other TCP flag match conditions | If you are not using the TCP initial flag for a match condition, select one of the TCP flags from the list—RST, ACK, SYN, Urgent, Push, FIN, None. These flags have the following meaning:
|
ICMP Settings Expand the ICMP Settings section to select an ICMP code value for the filter item’s match condition. The Internet Control Message Protocol (ICMP) is one of the core IP protocols used by operating systems of networked computers to send error messages. ICMP can also be used to relay query messages. | |
Add an ICMP Code match condition | ProcedureTo apply an ICMP code match condition to the named term:
Note: ICMP code specifies more specific information than ICMP type. Because the value’s meaning depends upon the associated ICMP type, you must specify an ICMP type along with an ICMP code. The keywords are grouped by the ICMP type with which they are associated. |
Add an ICMP Type match condition | Note: ICMP type specifies the ICMP packet type field. Typically, you specify this match condition in conjunction with the protocol match condition to determine which protocol is being used on the port. ICMP code specifies more specific information than ICMP type. Because the value’s meaning depends upon the associated ICMP type, you must specify an ICMP type along with the ICMP code. The keywords are grouped by the ICMP type with which they are associated. ProcedureTo apply an ICMP type match condition to the named term:
|
Action Select the action that the system performs on an IP packet if all match conditions that you specified above are met. Possible actions are Discard and Accept. The default action is to discard a packet that matches the filter term’s conditions. | |
Action | Select either Discard or Accept to indicate what the filter term does with a packet when a match is made. Note: The remaining fields in this section are enabled only if you select Accept as the action. |
Counter Name | When Accept is the action, specify a counter name. |
Loss Priority | When Accept is the action, specify the packet loss priority, Low, High, or None. Note: Forwarding class and loss priority must be specified together for the same term. |
Policer | When you create a Filter profile, you can specify a policer action for any term or terms within the filter. Policing, or rate limiting, enables you to limit the amount of traffic that passes into or out of an interface. All traffic that matches a term that contains a policer action goes through the policer that the term references. You have two options with a policer. You can specify that an existing policer be used for the packet that matches the match condition. Or, you can create a new policer for the packet that matches the match condition. To select a policer from an existing list of policers, click Select. The Select Policer page appears. Select the policer that you want to use for the term and click OK. The system displays the selected policer in the Policer field in the Create Term page. |
To create a new policer: Procedure
| |
Forwarding Class | When Accept is the action, specify the forwarding class (or output queue) that is to be used for the packet that matches the match condition. You can create a new forwarding class or select from a list of available forwarding classes. To select a forwarding class from an existing list of classes, click Select. The Select Forwarding Class page appears. Select the forwarding class that you want to use for the packet and click OK. The system displays the selected forwarding class in the Forwarding Class field in the Create Term page. |
ProcedureTo create a new forwarding class:
|
Click OK to save the term and return to the Create Filter Profile page.
A Filter profile must have at least one term in it. Each term has one filtering function. For example, if a term is evaluating the source of packets, then that term cannot also evaluate the protocols used by the packets. Some switch models accommodate multiple terms in one filter. When you have more than one term in a filter, the ordering of the terms is important. The system evaluates multiple filter terms as follows:
To configure a Filter profile for Campus switching ELS:
The Create Term window opens.
Note: The order of the terms within a Filter profile configuration is important. Packets are tested against each term in the order in which the terms are listed.
Table 119: Create Term Fields for Campus Switching ELS
Field | Description |
---|---|
Source and Destination
Parameters You can specify match conditions based on the packets’ origin (source) or the packets’ destination, or both. You are indicating the location of the filtering here—either specifying that packets that originate at a specific place (source) will be filtered or packets destined for a specific location (destination) will be filtered. You can have multiple sources and destinations for one filter. | |
Source Parameters and Destination Parameters | ProcedureTo add source and destination parameters to the named filter term:
|
Protocols and
EtherTypes Depending on the Filter Family you selected, you can sometimes apply a filter term based on either protocols being used by packets or on EtherTypes being used by packets. Recognized protocols are listed where applicable. Recognized EtherTypes, which indicate the protocol that is encapsulated in the payload of an Ethernet Frame, are also listed where applicable. | |
Protocols | ProcedureTo add a protocol match condition to the named filter term:
|
EtherTypes | ProcedureTo add an EtherTypes match condition to the named filter term:
|
DSCP Settings Expand the DSCP section to see the DSCP match settings. DiffServ is a simple mechanism for classifying and managing network traffic and providing quality-of-service (QoS) on IP networks. DiffServ can, for example, be used to apply low-latency to critical network traffic such as voice or streaming media while providing simple best-effort service to non-critical services such as Web traffic. Here, you can apply a filter term based on the Differentiated Services code point (DSCP) which is a field in IPv4 and IPv6 headers. Note: With IPv6 packets, the DS field and ECN field replace the IPv4 TOS field. | |
DSCP | ProcedureTo add a DSCP match condition to the named filter term: Note: A DSCP IP match condition and a precedence match condition cannot be both specified for the same term.
|
Precedence for DSCP | You can apply an IP precedence match condition to the named term. With IP precedence, a device prioritizes traffic by class first. Then it differentiates and prioritizes same-class traffic. The match conditions IP Precedence and DSCP cannot be simultaneously applied to a term. ProcedureTo apply an IP precedence value match condition to the named term:
|
TCP Settings Expand this section to access the TCP settings. The Transmission Control Protocol (TCP) is the most common core protocol of the Internet protocol suite (IP). TCP provides reliable, ordered, error-checked delivery of a stream of octets between programs running on computers connected to the Internet or an intranet. You can use the TCP initial flag for a match condition. | |
Enable TCP Initial | Select to use the TCP initial flag for an Ethernet, INET, or INET6 match condition. Tip: If you use the TCP initial flag for filtering, you cannot use any other TCP flag. |
TCP Flags | If you are not using the TCP initial flag for a match condition, you can select one of the TCP flags from the list for a match condition—RST, ACK, SYN, Urgent, Push, FIN, or None. These flags have the following meaning:
|
ICMP Settings You can select the ICMP code value for the filter item’s match condition—expand this section to access the ICMP settings. The Internet Control Message Protocol (ICMP) is one of the core IP protocols used by operating systems of networked computers to send error messages. ICMP can also be used to relay query messages. | |
ICMP Code | ProcedureTo apply an ICMP code match condition to the named term:
Note: An ICMP code specifies more specific information than an ICMP type. Because the value’s meaning depends upon the associated ICMP type, you must specify and ICMP type along with ICMP code. The keywords are grouped by the ICMP type with which they are associated. |
ICMP Type | Note: ICMP type specifies the ICMP packet type field. Typically, you specify this match condition in conjunction with the protocol match condition to determine which protocol is being used on the port. ICMP code specifies more specific information than ICMP type. Because the value’s meaning depends upon the associated ICMP type, you must specify ICMP type along with ICMP code. The keywords are grouped by the ICMP type with which they are associated. ProcedureTo apply an ICMP type match condition to the named term:
|
Action Select the action that the system performs on an IP packet if all match conditions that you specified above are met. Possible actions are Discard and Accept. The default action is to discard packet that matches the filter term conditions. | |
Action | Select either Discard or Accept to indicate what the filter term does with a packet when a match is made. Note: All other fields in this section are enabled only if you select Accept as the action. |
Counter Name | When the action selected is accept, specify the maximum packet count for this filter, term, or policer. |
Loss Priority | When the action selected is accept, specify the packet loss priority, Low, High, Medium-low, Medium-high, or None. Note: Forwarding class and loss priority must be specified together for the same term. |
Policer | When you create a Filter profile with the action accept, you can specify a policer action for any term or terms within the filter. Policing, or rate limiting, enables you to limit the amount of traffic that passes into or out of an interface. All traffic that matches a term that contains a policer action goes through the policer that the term references. You have two options with a policer. You can specify that an existing policer be used for the packet that matches the match condition. Or, you can create a new policer for the packet that matches the match condition. |
To select an existing policer: Procedure
| |
To create a new policer: Procedure
| |
Forwarding Class | Specify the forwarding class (or output queue) that is to be used for the packet that matches the match condition. You can either select from a list of available forwarding classes or create a new forwarding class. To select a forwarding class from an existing list of classes, click Select. The Select Forwarding Class page appears. Select the forwarding class that you want to use for the packet and click OK. The system displays the selected forwarding class in the Forwarding Class field in the Create Term page. |
ProcedureTo create a new forwarding class:
|
The new filter is added to the Manage Filter Profile list.
A Filter profile must have at least one term in it. Each term has one filtering function. For example, if a term is evaluating the source of packets, then that term cannot also evaluate the protocols used by the packets. Some switch models accommodate multiple terms in one filter. When you have more than one term in a filter, the ordering of the terms is important. The system evaluates multiple filter terms as follows:
To configure a Filter profile:
The Create Term window opens.
Note: The order of the terms within a Filter profile configuration is important. Packets are tested against each term in the order in which the terms are listed.
Table 120: Create Term Fields for Data Center Switching Non-ELS
Field | Description |
---|---|
Source and Destination
Parameters You can specify match conditions for either the packets’ origin (source) or the packets’ destination, or both. You are indicating the location of the filtering here—either specifying that packets that originate at a specific place (source) will be filtered or packets destined for a specific location (destination) will be filtered. You can have multiple sources and destinations for one filter. | |
Source Parameters and Destination Parameters | ProcedureTo add source and destination parameters to the named filter term:
|
Protocols and
EtherTypes You can apply a filter term that is based on either the protocols being used by packets or on the EtherTypes being used by packets. Protocols such as AH, DSTOPTS, EGP, ESP, FRAGMENT, GRE, HOP-BY-HOP, ICMP, ICMP6, IPIP, IPv6, no-text-header, OSPF, PIM, ROUTING, RSVP, SCTP, TCP, UDP, and VRRP are recognized. EtherType indicates the protocol that is encapsulated in the payload of an Ethernet Frame. | |
Protocols | ProcedureTo add a protocol match condition to the named filter term:
|
EtherTypes | ProcedureTo add an EtherTypes match condition to the named filter term:
|
DSCP Settings DiffServ is a simple mechanism for classifying and managing network traffic and providing quality-of-service (QoS) on IP networks. DiffServ can, for example, be used to apply low-latency to critical network traffic such as voice or streaming media while providing simple best-effort service to non-critical services such as Web traffic. Here, you can apply a filter term based on the Differentiated Services code point (DSCP) which is a field in IPv4 and IPv6 headers. Note: With IPv6 packets, the DS field and ECN field replace the IPv4 TOS field. | |
DSCP | ProcedureTo add a DSCP match condition to the named filter term: Note: A DSCP IP match condition and a precedence match condition cannot be both specified for the same term.
|
Precedence | You can apply an IP precedence match condition to the named term. With IP precedence, a device prioritizes traffic by class first. Then it differentiates and prioritizes same-class traffic. Note: The match conditions IP Precedence and DSCP cannot be simultaneously applied to a term. ProcedureTo apply an IP precedence value match condition to the named term:
|
TCP Settings The Transmission Control Protocol (TCP) is the most common core protocol of the Internet protocol suite (IP). TCP provides reliable, ordered, error-checked delivery of a stream of octets between programs running on computers connected to the Internet or an intranet. You can use the TCP initial flag for a match condition. | |
Enable TCP Initial | Select to use the TCP initial flag for a match condition. |
TCP Flags | If you are not using the TCP initial flag for a match condition, select one of the TCP flags from the list—RST, ACK, SYN, Urgent, Push, Fin, None. These flags have the following meaning:
|
ICMP Settings You can select the ICMP code value for the filter item’s match condition. The Internet Control Message Protocol (ICMP) is one of the core IP protocols used by operating systems of networked computers to send error messages. ICMP can also be used to relay query messages. | |
ICMP Code | ProcedureTo apply an ICMP code match condition to the named term:
Note: ICMP code specifies more specific information than ICMP type. Because the value’s meaning depends upon the associated ICMP type, you must specify ICMP type along with ICMP code. The keywords are grouped by the ICMP type with which they are associated. |
ICMP Type | Note: ICMP type specifies the ICMP packet type field. Typically, you specify this match condition in conjunction with the protocol match condition to determine which protocol is being used on the port. ICMP code specifies more specific information than ICMP type. Because the value’s meaning depends upon the associated ICMP type, you must specify an ICMP type along with the ICMP code. The keywords are grouped by the ICMP type with which they are associated. ProcedureTo apply an ICMP type match condition to the named term:
|
QFabric Settings These settings apply only when the profile is applied to a QFabric device. | |
Enable-from-fabric | Select to create a match condition that matches packets coming from the fabric. |
Enable-to-fabric | Select to create a match condition that matches packets going to the fabric. |
except | Select to create a match condition that matches all packets that are not going to the fabric. |
Action Select the action that the system performs on an IP packet if all match conditions that you specified above are met. Possible actions are Discard and Accept. The default action is to discard packet that match the filter term’s conditions. | |
Action | Select either Discard or Accept to indicate what the filter term does with a packet when a match is made. Note: All other fields in this section are enabled only if you select Accept as the action. |
Counter Name | Specify the maximum packet count for this filter, term, or policer. |
Loss Priority | Specify the packet loss priority, low, high, or none. Note: Forwarding class and loss priority must be specified together for the same term. |
Policer | When you create a Filter profile, you can specify a policer action for any term or terms within the filter. Policing, or rate limiting, enables you to limit the amount of traffic that passes into or out of an interface. All traffic that matches a term that contains a policer action goes through the policer that the term references. You have two options with a policer. You can specify that an existing policer be used for the packet that matches the match condition. Or, you can create a new policer for the packet that matches the match condition. To select a policer from an existing list of policers, click Select. The Select Policer page appears. Select the policer that you want to use for the term and click OK. The system displays the selected policer in the Policer field in the Create Term page. To create a new policer: Procedure
|
Forwarding Class | Specify the forwarding class (or output queue) that is to be used for the packet that matches the match condition. You can create a new forwarding class or select from a list of available forwarding classes. To select a forwarding class from an existing list of classes, click Select. The Select Forwarding Class page appears. Select the forwarding class that you want to use for the packet and click OK. The system displays the selected forwarding class in the Forwarding Class field in the Create Term page. |
ProcedureTo create a new forwarding class:
|
Click OK to save the term and return to the Create Filter Profile page.
A Filter profile must have at least one term in it. Each term has one filtering function. For example, if a term is evaluating the source of packets, then that term cannot also evaluate the protocols used by the packets. Some switch models accommodate multiple terms in one filter. When you have more than one term in a filter, the ordering of the terms is important. The system evaluates multiple filter terms as follows:
To configure a Filter profile for Data Center switching ELS:
The Create Term window opens.
Note: The order of the terms within a Filter profile configuration is important. Packets are tested against each term in the order in which the terms are listed.
Table 121: Create Term Fields for Data Center Switching ELS
Field | Description |
---|---|
Source and Destination
Parameters You can specify match conditions based on the packets’ origin (source) or the packets’ destination, or both. You are indicating the location of the filtering here—either specifying that packets that originate at a specific place (source) will be filtered or packets destined for a specific location (destination) will be filtered. You can have multiple sources and destinations for one filter. | |
Source Parameters and Destination Parameters | ProcedureTo add source and destination parameters to the named filter term:
|
Protocols and
EtherTypes Depending on the Filter Family you selected, you can sometimes apply a filter term based on either protocols being used by packets or on EtherTypes being used by packets. Recognized protocols are listed where applicable. Recognized EtherTypes, which indicate the protocol that is encapsulated in the payload of an Ethernet Frame, are also listed where applicable. | |
Protocols | ProcedureTo add a protocol match condition to the named filter term:
|
EtherTypes | ProcedureTo add an EtherTypes match condition to the named filter term:
|
DSCP Settings Expand the DSCP section to see the DSCP match settings. DiffServ is a simple mechanism for classifying and managing network traffic and providing quality-of-service (QoS) on IP networks. DiffServ can, for example, be used to apply low-latency to critical network traffic such as voice or streaming media while providing simple best-effort service to non-critical services such as Web traffic. Here, you can apply a filter term based on the Differentiated Services code point (DSCP) which is a field in IPv4 and IPv6 headers. Note: With IPv6 packets, the DS field and ECN field replace the IPv4 TOS field. | |
DSCP | ProcedureTo add a DSCP match condition to the named filter term: Note: A DSCP IP match condition and a precedence match condition cannot be both specified for the same term.
|
Precedence for DSCP | You can apply an IP precedence match condition to the named term. With IP precedence, a device prioritizes traffic by class first. Then it differentiates and prioritizes same-class traffic. The match conditions IP Precedence and DSCP cannot be simultaneously applied to a term. ProcedureTo apply an IP precedence value match condition to the named term:
|
TCP Settings Expand this section to access the TCP settings. The Transmission Control Protocol (TCP) is the most common core protocol of the Internet protocol suite (IP). TCP provides reliable, ordered, error-checked delivery of a stream of octets between programs running on computers connected to the Internet or an intranet. You can use the TCP initial flag for a match condition. | |
Enable TCP Initial | Select to use the TCP initial flag for an Ethernet, INET, or INET6 match condition. Tip: If you use the TCP initial flag for filtering, you cannot use any other TCP flag. |
TCP Flags | If you are not using the TCP initial flag for a match condition, you can select one of the TCP flags from the list for a match condition—RST, ACK, SYN, Urgent, Push, FIN, or None. These flags have the following meaning:
|
ICMP Settings You can select the ICMP code value for the filter item’s match condition—expand this section to access the ICMP settings. The Internet Control Message Protocol (ICMP) is one of the core IP protocols used by operating systems of networked computers to send error messages. ICMP can also be used to relay query messages. | |
ICMP Code | ProcedureTo apply an ICMP code match condition to the named term:
Note: An ICMP code specifies more specific information than an ICMP type. Because the value’s meaning depends upon the associated ICMP type, you must specify and ICMP type along with ICMP code. The keywords are grouped by the ICMP type with which they are associated. |
ICMP Type | Note: ICMP type specifies the ICMP packet type field. Typically, you specify this match condition in conjunction with the protocol match condition to determine which protocol is being used on the port. ICMP code specifies more specific information than ICMP type. Because the value’s meaning depends upon the associated ICMP type, you must specify ICMP type along with ICMP code. The keywords are grouped by the ICMP type with which they are associated. ProcedureTo apply an ICMP type match condition to the named term:
|
Action Select the action that the system performs on an IP packet if all match conditions that you specified above are met. Possible actions are Discard and Accept. The default action is to discard packet that matches the filter term conditions. | |
Action | Select either Discard or Accept to indicate what the filter term does with a packet when a match is made. Note: All other fields in this section are enabled only if you select Accept as the action. |
Counter Name | When the action selected is accept, specify the maximum packet count for this filter, term, or policer. |
Loss Priority | When the action selected is accept, specify the packet loss priority, Low, High, Medium-low, Medium-high, or None. Note: Forwarding class and loss priority must be specified together for the same term. |
Policer | When you create a Filter profile with the action accept, you can specify a policer action for any term or terms within the filter. Policing, or rate limiting, enables you to limit the amount of traffic that passes into or out of an interface. All traffic that matches a term that contains a policer action goes through the policer that the term references. You have two options with a policer. You can specify that an existing policer be used for the packet that matches the match condition. Or, you can create a new policer for the packet that matches the match condition. |
To select an existing policer: Procedure
| |
To create a new policer: Procedure
| |
Forwarding Class | Specify the forwarding class (or output queue) that is to be used for the packet that matches the match condition. You can either select from a list of available forwarding classes or create a new forwarding class. To select a forwarding class from an existing list of classes, click Select. The Select Forwarding Class page appears. Select the forwarding class that you want to use for the packet and click OK. The system displays the selected forwarding class in the Forwarding Class field in the Create Term page. |
ProcedureTo create a new forwarding class:
|
The new filter is added to the Manage Filter Profile list.
After you create a Filter profile, you can do one of the following: