Configuring Inbound Route Filters for IPv4 OSPFv2
|
|
Note - These commands are available starting from R81.10.05. |
|
|
Important - In a Cluster, you must configure all the Cluster Members in the same way. |
OSPF inbound route filters only apply to OSPF ASE routes.
Intra-area and inter-area OSPF routes are always installed.
The default behavior is to accept all OSPF ASE routes.
|
|
|
Parameter |
Description |
|---|---|
|
|
Configures the IPv4 OSPFv2 Import Policy (for the specified OSPF instance). |
|
|
Accepts all IPv4 routes that match this filter, except those route that are explicitly restricted by a more specific rule. Accepting routes is the default behavior, unless the "restrict" option is configured. |
rank {<0-255> | default}
|
Assigns a rank to all incoming routes that match this filter, except those that match a more specific rule with a different rank configured. Range: 0-255, or default Default: The protocol rank configured for " |
|
|
Rejects all IPv4 routes that match this filter, except those that match a more specific filter that is set to "accept". |
|
|
Configures import policy for a specific network. Range: Dotted-quad ([0-255].[0-255].[0-255].[0-255]) / [0-32] Default: None |
|
|
Accepts this route. |
|
|
There are different mechanisms, by which routes can be matched against the configured subnet. A match type must be configured following the subnet. Accepts any route with prefix equal to the specified network, whose mask length falls within a particular range. |
|
|
There are different mechanisms, by which routes can be matched against the configured subnet. A match type must be configured following the subnet. Rejects all routes that match this policy rule, except those that match a more specific filter that is set to "accept". |
|
|
There are different mechanisms, by which routes can be matched against the configured subnet. A match type must be configured following the subnet. Accepts only routes with prefix and mask length exactly equal to the specified network. |
|
|
There are different mechanisms, by which routes can be matched against the configured subnet. A match type must be configured following the subnet. Rejects all routes that match this policy rule, except those that match a more specific filter that is set to "accept". |
|
|
There are different mechanisms, by which routes can be matched against the configured subnet. A match type must be configured following the subnet. Accepts any route equal to or contained within the specified network. |
|
|
There are different mechanisms, by which routes can be matched against the configured subnet. A match type must be configured following the subnet. Rejects all routes that match this policy rule, except those that match a more specific filter that is set to "accept". |
|
|
Removes this address filter from this import policy. |
|
|
Assigns a rank to all incoming routes that match this filter, except those that match a more specific rule with a different rank configured. Range: 0-255, or default Default: The protocol rank configured for " |
|
|
There are different mechanisms, by which routes can be matched against the configured subnet. A match type must be configured following the subnet. Matches routes contained within the specified network, but only more specific (for example, with a greater mask length). |
|
|
There are different mechanisms, by which routes can be matched against the configured subnet. A match type must be configured following the subnet. Rejects all routes that match this policy rule, except those that match a more specific filter that is set to "accept". |
Only accept subnets of 192.168.0.0/16, but do not accept the exact route itself.
|
|