Filter Policies
Router Configuration Guide 529
Context config>filter>ip-filter
config>filter>ipv6-filter
Description This command embeds a previously defined IPv4 or IPv6 embedded filter policy or Hybrid OpenFlow
switch instance into this exclusive, template or system filter policy at the specified offset value. Rules
derived from BGP flowspec can also be embedded into template filter policies only.
The embed-filter open-flow ofs-name form of this command enables OpenFlow (OF) in GRT either
by embedding the specified OpenFlow switch (OFS) instance with switch-defined-cookie disabled,
or by embedding rules with sros-cookie:type “grt-cookie”, value 0 from the specified OFS instance
with switch-defined-cookie enabled. The embedding filter can only be deployed in GRT context or
be unassigned.
The embed-filter open-flow ofs-name system form of this command enables OF in system filters by
embedding rules with sros-cookie:type “system-cookie”, value 0 from the specified OFS instance with
switch-defined-cookie enabled. The embedding filter can only be of scope system.
The embed-filter open-flow ofs-name service {service-id | service-name} form of this command
enables OF in VPRN/VPLS filters by embedding rules with sros-cookie:type “service-cookie”, value
service-id from the specified OFS instance with switch-defined-cookie enabled – per service rules.
The embedding filter can only be deployed in the specified VPRN/VPLS service. A single VPLS
service can only support OF rules per SAP or per service.
The embed-filter open-flow ofs-name sap sap-id form of this command enables OF in VPLS SAP
filters by embedding rules with sros-cookie:type “service-cookie”, value service-id and flow match
conditions specifying the sap-id from the specified OFS instance with switch-defined-cookie enabled
– per SAP OF rules. The embedding filter must be of type exclusive and can only be deployed on the
specified SAP in the context of the specified VPLS service. A single VPLS service can only support
OF rules per SAP or per service.
The no embed-filter open-flow ofs-name form of this command removes the OF embedding for the
GRT context.
The embed-filter flowspec form of this command enables the embedding of rules derived from BGP
flowspec routes into the filter policy that is being configured. The optional router parameter specifies
the routing instance source of the BGP flowspec routes; if the parameter is not specifies, the routing
instance is derived automatically from the context in which the filter policy is applied. Flowspec rules
associated with one routing instance cannot be embedded in a filter applied to an interface of a different
routing instance. Also, once flowspec rules associated with one routing instance are embedded into a
filter, that filter policy cannot be applied to an interface of a different routing instance.
The no embed-filter flowspec form of this command removes the flowspec filter embedding from this
filter policy.
The embed-filter vsd vsd-filter-id command refers to the VSD filter ID encoded _tmnx_vsd_filter-id.
The filter is created dynamically and managed exclusively via the Python script, so rules can be
inserted and removed in the proper VSD filters. The command is supported with IP and IPv6 filters.
For more information on VSD filter provisioning, automation, and the Python script, refer to the Layer
2 Services and EVPN User Guide.
To Next Page
Loading...
