Route policy options

as-path

Syntax

as-path name expression regular-expression

no as-path name

Context

config>router>policy-options

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a route policy autonomous system (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. Allowed values are 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. A value of null specifies the AS path expressed as an empty regular expression string.

community

Syntax

community name members comm-id [comm-id...(up to 15 max)]

no community name [members comm-id]

Context

config>router>policy-options

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates 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. Note that up to 15 community ID strings can be specified up to a total maximum of 72 characters.

Values

72 chars maximum

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..65535

comm-val

0..65535

reg-ex

72 chars maximum

type

target, origin

ip-address

a.b.c.d

ext-comm-val

0..4294967295

4byte-asnumber

0..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 — The as-num is the autonomous system number (ASN)

    Values:

    as-num:

    1 to 65535

    comm-value:

    0 to 65535

  • type {target | origin} as-num:comm.-value — The 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 values allow the same preceding values for regular community values.

  • reg-ex1 reg-ex2 — These values are 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, and so on), the entire string must be enclosed within double quotes.

  • well-known-comm — Keywords null, no-export, no-export-subconfed, no-advertise.

policy-options

Syntax

[no] policy-options

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure route policies. Route policies are applied to the routing protocol used for IGMP group membership report filtering.

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

triggered-policy

Syntax

[no] triggered-policy

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command triggers route policy re-evaluation.

By default, when a change is made to a policy in the config router policy options context and 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 affect 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.

If the triggered-policy 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. That is, when a triggered-policy is enabled, any routine policy change or policy assignment change within the protocol will not take effect until the protocol is reset or a clear command is issued to re-evaluate 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.