ACL Filter Policy Overview
476 Router Configuration Guide
For IES/VPRN, the outgoing R-VPLS interface can be in any VPRN service. The
outgoing interface and VPRN service for BGP EVPN control plane resolution
must again be configured as part of ESI PBR entry configuration. The
functionality is supported in filter policies deployed on ingress IES/VPRN
interfaces and in filter policies deployed on ingress and egress for ESM
subscribers. Only unicast traffic is subject to ESI PBR, any other traffic matching
a filter entry with L3 ESI action will be subject to action forward.
The functionality requires chassis mode D. When deployed in unsupported
direction, traffic matching a filter policy ESI PBR/PBF entry will be subject to
action forward.
→ 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/IPv6 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.
→ 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/IPv6 filter policies only, deployed
on L3 interfaces. If configured next-hop is not reachable, traffic is dropped and
“ICMP destination unreachable” message is sent. For IPv6, requires minimum
Chassis mode C.
- 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.
→ 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 and IPv6 filter policies deployed on L3
interfaces only. See Redirect Policies in this chapter for more 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). This action requires incoming interfaces to be on
FP2 line cards or newer. It is supported for ingress IPv4/IPv6 filter policies
deployed on L3 interfaces. The action can be combined with the next-hop action
specifying direct/indirect IP/IPv6 next hop. Packets are dropped if they cannot
be routed in the configured routing instance.
→ sap — forwards the incoming traffic onto the specified VPLS SAP. Supported
for ingress IPv4/IPv6 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.
To Next Page
Loading...
