Policy Framework Configuration Guide - Juniper Networks

Chapter 5: Extended Match Conditions Configuration
In Junos OS Release 9.2 and later, you can also use AS-dot notation when defining a
4-byte AS number for the target and origin extended communities. Specify two integers
joined by a period: 16-bit high-order value in decimal.16-bit low-order value in decimal. For
example, the 4-byte AS number represented in plain-number format as 65546 is
represented in AS-dot notation as 1.10.
For more information about configuring AS numbers, see the Junos OS Routing Protocols
Configuration Guide.
Examples: Defining BGP Extended Communities
Configure a target community with an administrative field of 10458 and an assigned
number of 20:
[edit policy-options]
community test-a members [ target:10458:20 ];
Configure a target community with an administrative field of 10.1.1.1 and an assigned
number of 20:
[edit policy-options]
community test-a members [ target:10.1.1.1:20 ];
Configure an origin community with an administrative field of 10.1.1.1 and an assigned
number of 20:
[edit policy-options]
community test-a members [ origin:10.1.1.1:20 ];
Configure a target community with a 4-byte AS number in the administrative field of
100000 and an assigned number of 130:
[edit policy-options]
community test-b members [ target:100000L:130 ];
Related
Documentation
• Configuring AS Numbers for BGP in the Using 4-Byte Autonomous System Numbers in
BGP Networks Technology Overview
• Configuring 4-Byte AS Numbers and BGP Extended Community Attributes in the Using
4-Byte Autonomous System Numbers in BGP Networks Technology Overview
Inverting Community Matches
To invert the results of the community expression matching, include the invert-match
statement:
invert-match;
You can include this statement at the following hierarchy levels:
• [edit policy-options community name]
• [edit logical-systems logical-system-name policy-options community name]
Copyright © 2010, Juniper Networks, Inc.
109