Policy Framework Configuration Guide - Juniper Networks

Chapter 4: Routing Policy Configuration
policy-statement policy-statement-name {
dynamic-db;
}
You can also define specific policy objects based on the configuration of these objects
in the dynamic database. To define a policy object based on the dynamic database,
include the dynamic-db statement with the following statements at the [edit
policy-options] hierarchy level:
• as-path name
• as-path-group group-name
• community community-name
• condition condition-name
• prefix-list prefix-list-name
In the standard configuration, you can also define a routing policy that references any
policy object you have configured in the standard configuration that references an object
configured in the dynamic database.
For example, in standard configuration mode, you configure a prefix list prefix-list pl2
that references a prefix list, also named prefix-list pl2, that has been configured in the
dynamic database:
[edit policy-options]
prefix-list pl2 {
dynamic-db; # Reference a prefix list configured in the dynamic database.
}
You then configure a routing policy in the standard configuration that includes prefix-list
pl2:
[edit policy-options]
policy-statement one {
term term1 {
from {
prefix-list pl2; # Include the prefix list configured in the standard configuration
# database, but which references a prefix list configured in the dynamic database.
}
then accept;
}
then reject;
}
If you need to update the configuration of prefix-list pl2, you do so in the dynamic database
configuration using the [edit dynamic] hierarchy level. This enables you to make commit
configuration changes to the prefix list more quickly than you can in the standard
configuration database.
Copyright © 2010, Juniper Networks, Inc.
67