Juniper POLICY MANAGEMENT - CONFIGURATION GUIDE V11.1.X Configuration Manual page 163

substituted for parameters A, B, and C when you use the policy-parameter
command. Because of this policy attachment and the policy-parameter
command, the following aggregation nodes are created: (slot 5, ingress, EPG1,
1), (slot 5, ingress, EPG2, 1). The system creates a rate-limit instance for each
aggregation node: ER1-instance-1 and ER2-instance-1, respectively.
ER1-instance-1 is referenced in parent-group instances (EPG1, parameter A) and
(EPG1, parameter B). ER2-instance-1 is referenced in the parent group instance
(EPG2, parameter C).
Attach POL to atm5/0.2 as input policy.
4.
host1(config)#interface atm 5/0.2
host1(config-interface)#ip policy-parameter hierarchical A 1
host1(config-interface)#ip policy-parameter hierarchical B 2
host1(config-interface)#ip policy-parameter hierarchical C 2
host1(config-interface)#ip policy input POL statistics enabled
host1(config-interface)#exit
Policy list POL contains three parameter names that must be substituted with
actual values. This attachment consumes two internal rate-limit instances: one
for R1 and one for R2. This attachment also consumes one parent group instance
for IPG1, one parent-group instance for (EPG1, parameter A) tuple, one for (EPG1,
parameter B) tuple, and one for (EPG2, parameter C) tuple as in Step 3. When
you use the policy-parameter command, parameter A is substituted with value
1 and parameters B and C are substituted with value 2. Because of this policy
attachment and the policy-parameter commands, the following aggregation
nodes are identified: (slot 5, ingress, EPG1, 1), (slot 5, ingress, EPG1, 2), (slot 5,
ingress, EPG2, 2). The (slot 5, ingress, EPG1, 1) node was already created in Step
3 and was named ER1-instance-1. The other two aggregation nodes are now
created and named ER1-instance-2 and ER2-instance-2, respectively.
ER1-instance-1 is referenced by parent-group instance (EPG1, parameter A),
ER1-instance-2 is referenced by parent group instance (EPG1, parameter B), and
ER2-instance-2 is referenced by the parent group instance (EPG2, parameter C).
Attach POL to atm5/0.3 as input policy.
5.
host1(config)#interface atm 5/0.3
host1(config-interface)#ip policy-parameter hierarchical A 2
host1(config-interface)#ip policy-parameter hierarchical B 1
host1(config-interface)#ip policy-parameter hierarchical C 2
host1(config-interface)#ip policy input POL statistics enabled
host1(config-interface)#exit
Policy list POL contains three parameter names that need to be substituted with
actual values. This attachment consumes two internal rate-limit instances: one
for R1 and one for R2. This attachment also consumes one parent group instance
for IPG1, one parent-group instance for (EPG1, parameter A) tuple, one for (EPG1,
parameter B) tuple, and one for (EPG2, parameter C) tuple. When you use the
policy-parameter command, parameters A and C are substituted with value 2
and parameter B is substituted with value 1. Because of this policy attachment
and use of the policy-parameter commands, the following aggregation nodes
are identified; (slot 5, ingress, EPG1, 2), (slot 5, ingress, EPG1, 1), (slot 5, ingress,
EPG2, 2). All three aggregation nodes were created in earlier steps and were
named ER1-instance-2, ER1-instance-1, and ER2-instance-2, respectively.
ER1-instance-2 is referenced by parent-group instances (EPG1, parameter A),
Chapter 7: Creating Hierarchical Policies for Interface Groups
Example: Configuring Hierarchical Policies
137