Use the following CLI syntax to configure the policy association under the PCC:
classic CLI
configure router pcep
pcc
pce-associations
[no] policy association-name
association-id association-id
no association-id
association-source ip-address
no association-source
MD-CLI
configure router pcep
pcc
pce-associations
policy [assoc-name] string
association-id number
association-source ip-address
This association is always operator-configured [draft-ietf-pce-association-policy], that is, the value of the Association ID has a global meaning for this Association Type within a specific domain, independent of the source address in the ASSOCIATION object. For example, a PCC node can associate a policy Association ID with an SR-TE LSP included in the PCRpt message by including the PCC source address in the ASSOCIATION object, but the PCE looks up a path profile ID solely based on the Association ID value for PCC nodes in that domain. If another PCC node in the same domain signals another LSP with the same policy Association ID, the PCE also looks up the same path profile.