Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Putting a Device in RMA State and Reactivating Its Replacement

 

Sometimes, because of hardware failure, a device managed by Junos Space Network Management Platform needs to be returned to the vendor for repair or replacement. In such cases, Junos Space Network Management Platform can keep on record the configuration of the defective device until you can obtain an equivalent replacement device from the vendor. You create this record by putting the defective device in Return Materials Authorization (RMA) state before removing it. In this way, you prevent the configuration from being deleted from the Junos Space Network Management Platform database when the device is removed.

Before connecting the replacement device, you must configure it with such basic information as the name, IP address, SSH fingerprint, and login credentials.

After the replacement device has been reconnected within your network, you perform the Reactivate from RMA task to cause Junos Space Network Management Platform to read its settings, deploy the preserved configuration onto it, and bring it back under management. Because the two devices are perceived as equivalent, this operation is considered reactivation, even if the replacement device is new.

Do not delete or physically disconnect the defective device before performing the Put in RMA State task.

Warning

Remove any provisioning services associated with a device before putting it in RMA state.

Putting a Device in RMA State

If you want to return a device to the vendor under RMA, but you do not want to delete its configuration from the Junos Space Network Management Platform database, put the device in RMA state.

To have Junos Space Network Management Platform keep on record the configuration of a defective device so that you can later deploy that configuration to the defective device’s replacement:

  1. On the Junos Space Network Management Platform user interface, select Devices > Device Management.

    The Device Management page is displayed.

  2. Select the defective device and select Device Operations > Put in RMA State from the Actions menu.

    The RMA Device window appears.

  3. Click Confirm to put the selected device in RMA state.

Reactivating a Replacement Device

Before you begin, you must perform basic configuration on the replacement device, such as the name, IP address, SSH fingerprint, and login credentials. TheIP address must match that of the original device when it was put in RMA state.

From Junos Space Network Management Platform Release 18.2 onward, you can reactivate multiple replacement devices at the same time. The maximum number of devices that can be reactivated simultaneously is 100.

To reactivate the replacement device:

  1. Connect the replacement device to your network in the same way as the defective device was connected.
  2. On the Junos Space Network Management Platform user interface, select Devices > Device Management.

    The Device Management page is displayed.

  3. Select the items that formerly represented the defective devices. (It in fact now represents the replacement device, without the need for you to make any changes to it.)
  4. Select Device Operations > Reactivate from RMA from the Actions menu.

    The Reactivate Device from RMA page is displayed listing the selected items representing the replacement devices. The device name and IP address of the device is displayed for each item on this list.

    By default, the New fingerprint column will be empty for every device. User can manually enter the new device fingerprint or leave it empty.

  5. Enter the new fingerprint manually or import fingerprints in the form of a CSV file.

    To import SSH fingerprint using a CSV files:

    • Click Browse and select the CSV file to be uploaded from your local file system.
    • Click Upload to upload the selected CSV file.

      Once the file is uploaded, the details of the devices to be reactivated - device name, IP address of the device, and new SSH fingerprint is displayed in the grid.

    • (Optional) To download a sample CSV file, click the Sample CSV link.

      A sample CSV file listing the name, IP address, and new SSH fingerprint of the devices to be reactivated.

  6. (Optional) If there is no SSH fingerprint displayed for an device or if you want to associate a new SSH fingerprint with the reactivated device, a fingerprint conflict occurs.

    To auto-resolve SSH fingerprint conflicts, select the Auto-resolve fingerprint conflict if new fingerprint is not provided check box. If you choose select this check box, the fingerprint conflict resolution settings saved in the Device section of Modify Application Settings page (Administration > Applications) is overridden for device reactivation from RMA.

  7. To push the existing device configuration from Junos Space:

    • (Optional) Select the Push existing device configuration from Junos Space check box to push the configuration saved in Junos Space to the reactivated device.Note

      If you choose to push existing device configuration from Junos Space, scripts that were staged on the replaced device is restaged to the reactivated devices.

      If you choose not to push existing device configuration from Junos Space, all the scripts associated with the device is removed.

    • To use commit -confirmed for the reactivated devices, select the Use commit -confirmed check box.
    • To use temporary credentials to push device configuration from Junos Space, select the Use temporary device credentials to push configuration check box.

      Enter the temporary username and password to push the configuration.

      Note

      The temporary username and password will be used only to push the existing configuration from Junos Space on to the reactivated devices.

  8. Click Confirm to activate the replacement devices.

    The Reactivate Devices from RMA Job page appears displaying the job Id for the reactivation job. To view details of the job, click on the job ID.

    The replacement devices are displayed with the defective devices’ configuration in the Device Management page. As activation proceeds, intermediate states such as Reactivating are displayed under Managed Status. The replacement devices are active and under management when Connection Status reports that the device is up, and Managed Status reports In Sync.

    If Junos Space Platform detects an SSH fingerprint mismatch between that on the device and the fingerprint stored in the Junos Space Platform database, the connection is dropped. The connection status is displayed as Down and the authentication status is displayed as Fingerprint Conflict on the Device Management page.

Release History Table
Release
Description
From Junos Space Network Management Platform Release 18.2 onward, you can reactivate multiple replacement devices at the same time. The maximum number of devices that can be reactivated simultaneously is 100.