Filter Policy Actions - Alcatel-Lucent 7450 Configuration Manual

Filter Policy Actions

The following lists actions supported by ACL filter policies
•
•
•
7450 ESS Router Configuration Guide
drop — This action allows operator to deny traffic to ingress/egress the system
forward — This action allows operator to permit traffic to ingress/egress the system and
be subject to regular processing
forward "Policy-based Routing/Forwarding (PBR/PBF) action"— PBR/PBF actions
allows operator to permit ingress traffic but change the regular routing/forwarding packet
would be a subject to. The PBR/PBF is applicable to unicast traffic only. The following
PBR/PBF actions are supported (See CLI section for command details):
→ router — changes the routing instance a packet is routed in from the upcoming
interface's instance to the routing instance specified in the PBR action (supports both
GRT and VPRN redirect). Requires incoming interfaces to be on FP2 line cards or
newer. Supported for ingress IPv4 filter policies deployed on L3 interfaces. Can be
combined with next-hop action specifying direct/indirect IP/IPv6 next hop. Packets
are dropped if they cannot be routed in the configured routing instance.
→ next-hop — changes the IP destination address used in routing from the address in the
packet to the address configure in this PBR action. The operator can configure
whether the next-hop IP address must be direct (local subnet only) or indirect (any IP).
Supported for ingress IPv4 filter policies only, deployed on L3 interfaces. If
configured next-hop is not reachable, traffic is dropped and "ICMP destination
unreachable" message is sent.
→ lsp — forwards the incoming traffic onto the specified LSP. Supports RSVP-TE LSPs
(type static or dynamic only) or MPLS-TP LSPs. Supported for ingress IPv4 filter
policies only deployed on IES SAPs or network interfaces. If the configured LSP is
down, traffic matches the entry and action forward is executed.
→ interface — forwards the incoming traffic onto the specified IPv4 interface.
Supported for ingress IPv4 filter policies in global routing table instance. If the
configured interface is down or not of the supported type, traffic is dropped.
→ sap — forwards the incoming traffic onto the specified VPLS SAP. Supported for
ingress IPv4 and MAC filter policies deployed in VPLS service. The SAP traffic is to
egress on must be in the same VPLS service as the incoming interface. If the
configured SAP is down, traffic is dropped.
→ sdp — forwards the incoming traffic onto the specified VPLS SDP. Supported for
ingress IPv4 and MAC filter policies deployed in VPLS service. The SDP traffic is to
egress on must be in the same VPLS service as the incoming interface. If the
configured SDP is down, traffic is dropped.
Filter Policies
Page 443