Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE). Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.
This article addresses how users can create an NSRP cluster in Juniper Networks NSM.
To create an NSRP cluster:
Note: Refer to KB12459 for additional tips/gotchas on adding a cluster to NSM.
Go to Device Manager > FW/VPN Devices, click the "+". Select Cluster.

Fill out the New Cluster form. For the example, the cluster is called NS-50 Cluster.

Click OK.
Right-click the newly created cluster, and choose Edit.

Go to Network > Interface. Configure the physical ethernet interface for ethernet1 and ethernet3.
For ethernet1, right-click ethernet1 and choose Edit. In this example, the ethernet1 interface IP address is 50.50.50.1/24.

Click OK.
For ethernet3, right-click ethernet3 and choose Edit. In this example, the ethernet3 interface IP address is 10.100.31.135/24.

Enable SCS or Telnet so that NSM can talk to the cluster. Click OK.
Click OK to accept the interface parameters.
Select NS-50 Cluster, and click "+" to add the Cluster Member.

In the example, the first cluster member is labeled NS-50A.

Enter the manage-ip for the physical device. This is the IP address that NSM will use for management communication with the device. In the example, the manage-ip for NS-50A will be 10.100.13.93. Enter the admin username and password.

Click Next.
NSM will now verify authenticity with the device if using SSH (recommended).

Click Next.
NSM will attempt to discover the device. When successful, the following information will be displayed:

Click Finish.
Repeat steps 12 through 18 for the other cluster member device.
Import the configuration to the Cluster. From the Devices menu, select Configuration > Update Device config. Select NS-50 Cluster:

Click OK.
NSM will import the configuration from each individual device to the cluster members. When finished, the following will display:

2020-10-18: Tagged article for EOL/EOE.
2020-03-30: Article reviewed for accuracy, and found to be relevant and valid