Filter Policy Statistics - Alcatel-Lucent 7450 Configuration Manual

Filter Policy Basics
•
•
In addition to the above actions, operator can select a default-action for a filter policy. Default
action is executed on packets subjected to an active filter when none of the filter's active entries
matches the packet. By default, filter policies have default action set to drop but operator can
select a default action to be forward instead.

Filter Policy Statistics

Filter policies support per-entry, packet match debug statistics. The cumulative matched packet
counters are available per ingress and per egress direction. Every packet arriving on an interface/
service/subscriber using a filter policy increments ingress or egress (as applicable) matched packet
count for a filter entry the packet matches (if any) on the line card the packet ingresses/egresses.
For each policy, the counters for all entries are collected from all line cards, summed up and made
available to an operator.
Starting with SROS Release 11.0 R4, filter policies applied on access interfaces are downloaded
only when active and only to line cards that have interfaces associated with those filter policies. If
a filter policy is not downloaded to any line card, the statistics show 0 (zero). If a filter policy is
Page 444
→ redirect-policy — implements PBR next-hop or PBR next-hop router action with
ability to select and prioritize multiple redirect targets and monitor the specified
redirect targets so PBR action can be changed if the selected destination goes down.
Supported for ingress IPv4 filter policies deployed on L3 interfaces only. See
Policies in this chapter for more details
forward "isa action" — ISA processing actions allow operator to permit ingress traffic
and send it for ISA processing as per specified isa action. The following isa actions are
supported (see CLI section for command details):
→ nat — forwards matching traffic for NAT. Supported for IPv4 filter policies for L3
services in GRT or VPRN. If ISAs performing NAT are down, traffic is dropped. (see
CLI for options)
→ reassemble — forwards matching packets to the reassembly function. Supported for
IPv4 ingress filter policies only. If ISAs performing reassemble are down, traffic is
dropped.
→ gtp-local-breakout — forwards matching traffic to NAT instead of being GTP
tunneled to the mobile operator's PGW or GGSN. The action applies to GTP-
subscriber-hosts. If filter is deployed on other entities, action forward is applied.
Supported for IPv4 ingress filter policies only. If ISAs performing NAT are down,
traffic is dropped.
http-redirect — implements HTTP redirect captive portal. HTTP GET is forwarded to
CPM card for captive portal processing by router. See HTTP-redirect (Captive Portal)
section for further details.
7450 ESS Router Configuration Guide
Redirect