Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring Ethernet Services Path Selection Through Non-ERPS Nodes

    Use this procedure to configure Ethernet services path selection through non-ERPS nodes when PSM auto-provisions NNIs.

    When using the Auto-Provision NNIs feature, PSM can be configured to use a more restrictive or a more liberal set of selection criteria for selecting internal NNIs.

    1. Edit the /var/local/ems9001/conf/override-common.properties file.

      Note: The /var/local/ems9001/conf/override-common.properties file contains many settings that affect the behaviour of the PSM server. Only those attributes explicitly described in this guide should be changed. Changing any other attributes may have unintended consequences, and must only be performed under the guidance of Juniper Networks Support.

    2. Set the ethernetServices.autoRouting.nonErpsSegments.singlePath attribute as follows:
      • To force PSM to select a single linear path through non-ERPS nodes, set the value to true. Make this selection only if there is a single path through non-ERPS nodes to the endpoint.
      • To let PSM make a more liberal NNI selection through non-ERPS nodes, set the value to false. This may cause PSM to select more NNIs than is necessary. This is the default setting.

      For example, to force the selection of a single linear path:

      ethernetServices.autoRouting.nonErpsSegments.singlePath=true
    3. Save and close the file.
    4. Track changes to the /var/local/ems9001/conf/override-common.properties file with Git by committing this update to the Git repository.

      For example:

      [user ~]# cd /var/local/ems9001/conf
      [user conf]# git commit -m "Configured single path selection for non-ERPS nodes.  By user@example.org."  override-common.properties
      

      This update can now be seen in the Git log. For more information on Git, see Using Git to Track override-common.properties.

    5. Changes made to the override-common.properties file do not take effect until the PSM server is restarted. To restart the server, enter the following command:
      psm-restart

      The restart command successfully completes when the 'Ems-' processes all change to the running state. Type <ctrl> c to exit the Linux watch command window.

    Modified: 2017-11-07