How do I create an SR policy?
Purpose
SR policies can be manually created, or automatically generated. If, for example, the creation of a new LSP (with an Explicit Route Strategy of 'Standard BSID Preferred') causes the maximum stack depth (MSD) to be exceeded due to the number of strict hops through the network, NSP checks if an existing SR policy can be reused. If the existing policies are not sufficient, NSP will automatically generate a new SR policy using a backwards-recursive algorithm. SR Policies are preferred at domain boundaries.
This procedure is used to manually create an SR policy.
Note: Before creating an SR policy, the BGP of all eligible nodes must be configured to support sr-policy-ipv4 in family.
Note: Before creating an SR policy, open the sros-vm.conf file and ensure that it reads as follows:
sros-vms {
vms =[
{
rom=true
}
]
}
SR policies are imported into path simulation when importing a network from a file, or if 'Network and LSPs' is selected when importing a live network.
Note: Impacted SR policies are not included in the results of simulations or worst case failure scenarios.
Steps
1 |
Navigate to either the Path Control, SR Policies view or the Path Simulation, SR Policies view. A list of existing SR policies is displayed. | ||||||||||||||||||
2 |
Click on the button. The Create SR policy form opens. | ||||||||||||||||||
3 |
Configure the Policy parameters, as required:
| ||||||||||||||||||
4 |
Configure the Candidate Path parameters, as required:
Note: If not manually specified, binding SIDs will only be generated if the label stack depth of the computed TE path exceeds the maximum stack depth requested or configured. Note: The following REST API can be used to enable binding SID generation, and to configure binding SID and color range: PATCH /sdn/api/v4/nsp/configuration/sr-policy-config Where NSP_cluster is the IP address of the NSP cluster. If the Binding SID parameter is manually configured with a value of -1, the binding SID will inherit configuration from the above REST API. For more information, see the Network Developer Portal. Note: When updating an SR policy, if a candidate path that is administratively 'Up' is modified - but remains administratively 'Up' - no changes to that candidate path will be processed. | ||||||||||||||||||
5 |
Perform one of the following:
| ||||||||||||||||||
6 |
Perform one of the following:
Go to Step 10. | ||||||||||||||||||
7 |
Click + SEGMENT LIST and configure the parameters:
| ||||||||||||||||||
8 |
Click + SID and provide a unique identifier. Repeat as required. | ||||||||||||||||||
9 |
Repeat Step 7 as required to create additional segment lists. | ||||||||||||||||||
10 |
Repeat Step 4 as required to create additional candidate paths. | ||||||||||||||||||
11 |
Click CREATE. The SR policy is created. End of steps |
© 2024 Nokia. Nokia Confidential Information
Use subject to agreed restrictions on disclosure and use.