Filter Configuration Command Reference
580 Router Configuration Guide
router
Syntax router router-instance
router service-name service-name
no router
Context config>filter>redirect-policy
Description This command enhances VRF support in redirect policies. When a router instance is specified, the
configured destination tests are run in the specified router instance, and the PBR action is executed in
the specified router instance. If no destination is active or if the hardware does not support PBR action
“next-hop router”, action forward will be executed (i.e. routing will be performed in the context of the
incoming interface routing instance).
The no form of the command preserves backward-compatibility. Tests always run in the “Base”
routing instance context, and the PBR action executes in the routing context of the ingress interface
that the filter using this redirect policy is deployed on.
Default no router
Parameters router-instance — Specifies a router instance in the form of router-name or service-id.
Values router-name — Base
service-id — an existing Layer 3 service [1 to 2147483647]
service-name — Specifies the name of a configured Layer 3 service.
shutdown
Syntax [no] shutdown
Context config>filter>redirect-policy
config>filter>redirect-policy>destination
Description Administratively enables/disabled (AdminUp/AdminDown) an entity. Downing an entity does not
change, reset or remove any configuration settings or statistics. Many objects must be shutdown before
they may be deleted.
The shutdown command administratively downs an entity. Administratively downing an entity
changes the operational state of the entity to down.
Unlike other commands and parameters where the default state will not be indicated in the
configuration file, shutdown and no shutdown are always indicated in system generated
configuration files.
The no form of the command puts an entity into the administratively enabled state.
Default no shutdown
To Next Page
Loading...
