Route policy options

Context

config>router>policy-options

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a route policy AS path regular expression statement to use in route policy entries.

The no form of this command deletes the AS path regular expression statement.

Parameters

name

Specifies the AS path regular expression name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

regular-expression

Specifies the AS path regular expression (any string or null).

Values

Any string up to 256 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

null — Specifies the AS path expressed as an empty regular expression string.

Context

config>router>policy-options

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a route policy community list to use in route policy entries.

The no form of this command deletes the community list or the provided community ID.

Default

no community

Parameters

name

Specifies the community list name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

comm-id

Specifies the community ID. Up to 15 community ID strings can be specified, to a maximum of 72 characters.

Values

72 chars max
2byte-asnumber:comm-val | reg-ex | ext-comm | well-known-comm
ext-comm	type:{ip-address:comm-val | reg-ex1&reg-ex2 | ip-address&reg-ex2 | 2byte-asnumber:ext-comm-val |4byte-asnumber:comm-val}
2byte-asnumber	0 to 65535
comm-val	0 to 65535
reg-ex	72 chars max
type	target, origin
ip-address	a.b.c.d
ext-comm-val	0 to 4294967295
4byte-asnumber	0 to 4294967295
reg-ex1	63 chars max
reg-ex2	63 chars max
well-known-comm	null, no-export, no-export-subconfed, no-advertise

A community ID can be specified in different forms:

• as-num:comm.-value — Specifies the as-num is the Autonomous System (AS) number.

  Values:

  as-num:	1 to 65535
  comm-value:	0 to 65535

• type {target | origin}:as-num:comm.-value — Keywords target or origin denote the community as an extended community of type route target or route origin respectively. The as-num and comm.-value allow the same values as described previously for regular community values.

• reg-ex1 reg-ex2 — Specifies a regular expression string. Allowed values are any string up to 63 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

• well-known-comm — Keywords are the following: null, no-export, no-export-subconfed, no-advertise

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode

Description

Commands in this context configure route policies.

In the access-uplink operating mode, route policies are used for IGMP group membership report filtering.

The no form of this command deletes the route policy configuration.

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command triggers route policy reevaluation.

By default, when a change is made to a policy in the config>router>policy>options context and then committed, the change is effective immediately. There may be circumstances when the changes should or must be delayed; for example, if a policy change is implemented that would effect every BGP peer on a 7210 SAS router, the consequences could be dramatic. It is more effective to control changes on a peer-by-peer basis.

When this command is enabled, a specific peer is established, and you want the peer to remain up, in order for a change to a route policy to take effect, a clear command with the soft or soft-inbound option must be used. When a triggered-policy is enabled, any routine policy change or policy assignment change within the protocol does not take effect until the protocol is reset or a clear command is issued to reevaluate route policies; for example, clear router bgp neighbor x.x.x.x soft. This keeps the peer up and the change made to a route policy is applied only to that peer or group of peers.