Configuration Notes
288 7705 SAR OS Router Configuration Guide
Configuration Notes
The following information describes the conditions for filter policy implementation.
• Creating a filter policy is optional.
• Using a filter policy is optional.
• A filter policy must be created before it can be applied to a service.
• When a filter policy is configured, it must be defined as having either an exclusive
scope (for use with one interface), or a template scope (meaning that the filter can be
applied to multiple interfaces). VLAN filter policies always have a template scope.
• A specific filter must be explicitly associated with a specific interface in order for
packets to be matched.
• Each filter policy must consist of at least one filter entry. Each entry represents a
collection of filter match criteria. When packets enter an ingress port or SAP or SDP,
or exit an egress SAP, the packets are compared to the criteria specified within the
entry or entries.
• When you configure a large (complex) filter, it may take a few seconds to load the
filter policy configuration.
•The action keyword must be entered for the entry to be active. Any filter entry
without the action keyword is considered incomplete and will be inactive.
See the following sections for specific notes on:
• IP Filters
• IPv6 Filters
• MAC Filters
• VLAN Filters
• Filter Logs
IP Filters
• Define filter entry packet matching criteria — if a filter policy is created with an entry
and entry action specified but the packet matching criteria is not defined, then all
packets processed through this filter policy entry will pass and take the action
specified. There are no default parameters defined for matching criteria.
• Action — an action keyword must be specified for the entry to be active. Any filter
entry without an action keyword specified is considered incomplete and will be
inactive.
To Next Page
Loading...
