Choose Policies→Routing→Statement from the NFM-P main menu. The Routing Policy - Statements form opens.

Click Create or choose a policy and click Properties. The Routing Policy - Statement, Global Policy form opens.

Configure the required parameters on the General tab.

Note: Do not create a new routing policy statement with the following terms as the Policy Statement Name: N/A, n/a, or @. Creating a routing policy statement with @ in the Policy Statement Name results in Template Inconsistent/Configuration Mismatch alarms, which do not clear after a synchronization with the global policy. Also, updating the policy statement name using node CLI as N/A is not valid.

If you set the Default Action parameter to Accept, Next Entry, Next Policy, or Reject/Drop, the Default Action tab is selectable. Go to Step 4.

If you set the Default Action parameter to None, go to Step 6.

Configure a default action for the routing policy statement. Click on the Default Action tab and perform the following on the General tab:

1. Configure the parameters, policy variables, and global variables on the General sub-tab, as required.

   Note:

   If you want to specify a policy variable for an action item on this tab, select the policy statement entry that defines the required policy variable.

   If you want to specify a policy variable for an action item on this tab, then you cannot configure a corresponding parameter Value for the same item. They are mutually exclusive.

   If you want to specify a global variable for an action item on this tab, select the global variable entry that defines the required global variable. Global variables are configured in To configure global variables.

2. Click on the Path sub-tab and configure the BGP AS path parameters and variables, as required.

   Note:

   A BGP AS Path Name must be selected if the BGP AS Path Action is set to Add or Replace.

   You cannot specify both a BGP AS Prepend Number and a BGP AS Prepend Policy Variable. They are mutually exclusive.

   If you are specifying a BGP AS Prepend Policy Variable, this is done by selecting the policy statement entry that defines the required variable.

   If you want to specify a global variable for an action item on this tab, select the global variable entry that defines the required global variable. Global variables are configured in To configure global variables.

Configure the default community actions for the routing policy statement.

1. Click on the Default Community Actions tab and click on the Add, Remove, or Replace sub-tabs as required to perform the specific action that you want to configure.

2. Click Select to add, remove, or replace a Community Name Action. Review the usage notes provided below the Community Name Action field and implement, as required.

Note: You can specify mid-string expansions such as "peer-@asname@" or "comm-@peeras@-add" for example, for the Community Name Action field. However, there is no validation on the parameterized mid-strings entered for communities.

Configure policy statement entries for the routing policy statement.

Note: Routing policy entries are compared against incoming packets. Entries are compared in the numerical sequence of the Entry IDs, from lowest to highest. When a match is found, the action specified using the Action parameter occurs. If no action is specified, the action specified using the Default Action parameter occurs. If no default action is specified, the default action for the protocol or the route configuration occurs. For this reason, Nokia recommends that you sequence the routing policy entries to ensure the first entry is the most explicit and the last entry is the least explicit.

Nokia recommends staggering the numerical Entry ID values (for example, using 10, 20, 30… instead of 1, 2, 3…), to allow insertion of additional entries without renumbering the entire set. The NFM-P supports renumbering existing entries on supporting NEs.

1. Click on the Policy Statement Entries tab.

2. To renumber an entry on an existing policy statement, choose the entry in the list and click Renumber ID. Repeat for each additional entry that requires renumbering.

   When the routing policy statement is redistributed to NEs that support entry renumbering, the new Entry ID values are used.

3. Click Create, or choose a policy in the list and click Properties. The Policy Statement Entry, Site form opens.

4. Configure the required parameters on the General tab.

   Select a policy variable for the SRv6 Sid Prefix Address parameter, configure the SRv6 Sid Prefix Length parameter, and select a global variable for the Policy/Global Variable parameter.

   You can choose to enable or disable either or both the To Criteria and From Criteria here, whether they are configured or not.

   If you set the Action parameter to Accept, Next Entry, or Next Policy, the Action tab is selectable. Go to Step 7 .

   If you set the Action parameter to None or Reject/Drop, go to Step 8 .

Click on the Action tab to configure actions for the policy statement entry.

1. Configure the parameters and select policy variables on the General sub-tab, as required.

   Notes:

   You must configure the SR Maintenance Policy parameter in order to select the policy variables in the SRv6 Return Path BFD and SR Return Path BFD Label panels.

   If you want to specify a policy variable for a subordinate policy action item on this tab, this is done by selecting the policy statement entry that defines the required variable. Such a policy statement entry is typically part of another existing (higher level) routing policy statement.

2. Click on the Path sub-tab and configure the BGP AS path parameters, as required.

   Note:

   A BGP AS Path Name must be selected if the BGP AS Path Action is set to Add or Replace.

   You cannot specify both a BGP AS Prepend Number and a BGP AS Prepend Policy Variable. They are mutually exclusive.

   If you are specifying a BGP AS Prepend Policy Variable, this is done by selecting the policy statement entry that defines the required variable. Such a policy statement entry is typically part of another existing (higher level) routing policy statement.

3. Click on the Community Actions tab to configure a community action for the policy statement entry.

4. Click on the Add, Remove, or Replace sub-tabs as required to perform the specific action that you want to configure.

5. Click Select to add, remove, or replace a Community Name Action. Review the usage notes provided below the Community Name Action field and implement as required.

   Note:

   You can specify mid-string expansions such as "peer-@asname@" or "comm-@peeras@-add" for example, for the Community Name Action field. However, there is no validation on the parameterized mid-strings entered for communities.

Configure the From criteria for the policy statement entry.

1. Click on the From Criteria tab, select a route distinguisher policy, and configure the parameters on the General sub-tab, as required.

   Note:

   If you are performing this procedure to create a subordinate (lower level) routing policy that needs to specify an AS Path Name, AS Path Group Name, or Community List Name as a policy variable (defined in a higher level routing policy), then these policy variables are selected at this step.

   If you are performing this procedure to create a main (higher level) routing policy that contains policy variables that will be called by a subordinate routing policy, then that subordinate routing policy name must be specified at this step using the Policy Statement Name parameter. The policy variables for this higher level routing policy are defined in Step 10 .

   You cannot add policies that have nested sub-policies.

   Configuring a Community List Name in this step, either by selection or as a policy variable, is mutually exclusive with creating a Community List Expression in Step 9 .

2. Click on the Prefix Lists sub-tab to assign a prefix list to the policy statement entry.

   The Prefix Lists sub-tab displays if you did not assign a prefix list on the Prefix List Override sub-tab.

3. Configure the Prefix List Members as required.

   Note:

   You can specify mid-string expansions such as "prefixA-@prefixB@" or "prefixA-@prefixB@-add" for example, in the Prefix List field. However, there is no validation on the parameterized mid-strings entered for prefix lists.

4. Click on the Prefix List Override sub-tab.

   The Prefix List Override sub-tab displays if you did not assign a prefix list on the Prefix Lists sub-tab.

5. Select the prefix list and configure the required parameter.

   Depending on the option that you selected for the Type parameter, additional parameters may display.

Create a community expression list for the policy statement entry.

1. Click on the Community Expression tab and click Create. The Community Expression, Site form opens.

2. Select or enter a Community Name.

3. Click the Add button to add an entry into the Community List Expression field. The following conditions apply to this parameter:

   • The entire Community List Expression is limited to 900 characters. Use Boolean operators (AND, OR, and NOT) to form expressions, and use parentheses to form more complex expressions. For example:

     [comlist1] AND ([comlist3] OR [comlist4])

   • If you make an error in the construction of the string, use the Clear All button to start again, or place your cursor in the field and manually edit the text.

4. Save your changes and close the form.

Create a policy variable for the policy statement entry.

This step is required if you are creating a main (higher level) routing policy that will be called by a subordinate (lower level) routing policy. A policy variable in this context may be an integer, an IPv4/IPv6 address, or a string (that is, a pointer to another routing policy type). If you want to select the Type as a String, then you must create the other routing policy type (for example, Prefix List or Community policy) before you start this step. You can create up to ten policy variables for each policy statement entry.

1. Click on the Policy Variables tab and click Create. The Policy Variable, Site form opens.

2. Configure the Name parameter for the policy variable. The name must begin and end with an “@” sign; for example: @variable-name_1@.

3. Configure the Type and Value parameters. If you configure Type as String, then click Select to choose and assign a routing policy to the policy variable.

4. Click OK. The Policy Variable, Site form reappears.

5. Click OK to save your changes and close the form.

Note: You can configure global policy variables (for supporting NEs) that you can assign to multiple routing policy statements to improve configuration efficiency; see To configure global variables.

Configure the To criteria for the policy statement entry.

1. Click on the To Criteria tab and configure the parameters on the General tab, as required.

2. Click on the Prefix Lists sub-tab and configure the Prefix List Members as required.

Configure a conditional expression for the policy statement entry.

1. Click on the Conditional Expression tab and click Create. The Conditional Expression, Site form opens.

2. Specify a conditional expression for the Route Exists String parameter, or click on the Select button to select an existing prefix list policy.

3. Save your changes and close the form.

To create an additional policy statement entry, go to Step 6 otherwise go to Step 14 .

Save your changes and close the form. See To release and distribute a policy to release and distribute the policy to NEs.

Note: A routing policy is discovered as local edit only. To synchronize a routing policy with all NEs, you must change the distribution mode of the routing policy to sync with global. To configure the distribution mode, see To release and distribute a policy .

See To view policy variable usage in a routing policy statement to view policy variable usage in a distributed routing policy statement.

End of steps