Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Upgrade Instructions

This section includes instructions to upgrade to Junos Space Network Management Platform Release 16.1R2. Read these instructions before you begin the upgrade process.

In Junos Space Platform Release 16.1R2, CentOS 6.8 is used as the underlying OS. A direct upgrade of the OS from CentOS 5.9 to CentOS 6.8 is not recommended; therefore, a direct upgrade from Junos Space Platform Release 15.2R2 to Junos Space Platform Release 16.1R2 by using the Junos Space Platform UI is not supported. You must follow a multistep procedure that involves backing up data from the nodes in the Junos Space Platform setup, installing Junos Space Platform Release 16.1R2 on the nodes, and restoring backed-up data to the nodes to complete the upgrade from Junos Space Platform Release 15.2R2 to Junos Space Platform Release 16.1R2.

Caution: Ensure that all data on the node is backed up to a remote server before you install the Junos Space Platform Release 16.1R2 software image as part of the upgrade procedure from Junos Space Platform Release 15.2R2 to Junos Space Platform Release 16.1R2. Existing data on the node is deleted when you install Junos Space Platform Release 16.1R2.

To upgrade from Junos Space Platform Release 15.2R2 to Junos Space Platform Release 16.1R2, you must follow the procedure outlined in Upgrading to Junos Space Network Management Platform Release 16.1R1.

Note: The procedure described for the upgrade from Junos Space Platform Release 15.2R2 to Junos Space Platform Release 16.1R1 in Upgrading to Junos Space Network Management Platform Release 16.1R1 is also applicable for the upgrade from Junos Space Platform Release 15.2R2 to Junos Space Platform Release 16.1R2.

Caution: During the Junos Space Network Management Platform upgrade process, do not modify the filename of the software image that you download from the Juniper Networks support site. If you modify the filename, the upgrade fails.

Instructions for Validating the Junos Space Network Management Platform OVA Image

From Junos Space Network Management Platform Release 14.1R1 onward, the Junos Space Platform open virtual appliance (OVA) image is securely signed.

Note:

  • Validating the OVA image is optional; you can install or upgrade Junos Space Network Management Platform without validating the OVA image.
  • Before you validate the OVA image, ensure that the PC on which you are performing the validation has the following utilities available: tar, openssl, and ovftool (VMWare Open Virtualization Format [OVF] Tool). You can download VMWare OVF Tool from the following location: https://my.vmware.com/web/vmware/details? productId=353&downloadGroup=OVFTOOL351 .

To validate the Junos Space Network Management Platform OVA image:

  1. Download the Junos Space Platform OVA image and the Juniper Networks Root CA certificate chain file (JuniperRootRSACA.pem) from the Junos Space Network Management Platform - Download Software page at https://www.juniper.net/support/downloads/space.html .

    Note: You need to download the Juniper Networks Root CA certificate chain file only once; you can use the same file to validate OVA images for future releases of Junos Space Network Management Platform.

  2. (Optional) If you downloaded the OVA image and the Root CA certificate chain file to a PC running Windows, copy the two files to a temporary directory on a PC running Linux or Unix. You can also copy the OVA image and the Root CA certificate chain file to a temporary directory (/var/tmp or /tmp) on a Junos Space node.

    Note: Ensure that the OVA image file and the Juniper Networks Root CA certificate chain file are not modified during the validation procedure. You can do this by providing write access to these files only to the user performing the validation procedure. This is especially important if you use a generally accessible temporary directory, such as /tmp or /var/tmp, because such directories can be accessed by several users.

  3. Navigate to the directory containing the OVA image.
  4. Unpack the OVA image by executing the following command:

    tar xf ova-filename

    Where ova-filename is the filename of the downloaded OVA image.

  5. Verify that the unpacked OVA image contains a certificate chain file (junos-space-certchain.pem) and a signature file (.cert extension).
  6. Validate the signature in the unpacked OVF file (extension .ovf) by executing the following command:

    ovftool ovf-filename

    Where ovf-filename is the filename of the unpacked OVF file.

  7. Validate the signing certificate with the Juniper Networks Root CA certificate chain file by executing the following command:

    openssl verify -CAfile JuniperRootRSACA.pem -untrusted Certificate-Chain-File Signature-file

    Where JuniperRootRSACA.pem is the Juniper Networks Root CA certificate chain file, Certificate-Chain-File is the filename of the unpacked certificate chain file (extension .pem), and Signature-file is the filename of the unpacked signature file (extension .cert).

    If the validation is successful, a message indicating that the validation is successful is displayed.

    A sample of the validation procedure is as follows:

    -bash-4.1$ ls
    JuniperRootRSACA.pem space-16.1R1.3.ova
    -bash-4.1$ mkdir tmp
    -bash-4.1$ cd tmp
    -bash-4.1$ tar xf ../space-16.1R1.3.ova
    -bash-4.1$ ls
    junos-space-certchain.pem space-16.1R1.3.cert
    space-16.1R1.3-disk1.vmdk.gz space-16.1R1.3.mf
    space-16.1R1.3.ovf
    -bash-4.1$ ovftool space-16.1R1.3.ovf
    OVF version:   1.0
    VirtualApp:    false
    Name:          viso-space-16.1R1.3
    
    Download Size:  1.76 GB
    
    Deployment Sizes:
      Flat disks:   250.00 GB
      Sparse disks: 4.68 GB
    
    Networks:
      Name:        VM Network
      Description: The VM Network network
    
    Virtual Machines:
      Name:               viso-space-16.1R1.3
      Operating System:   rhel5_64guest
      Virtual Hardware:
        Families:         vmx-04 
        Number of CPUs:   4
        Cores per socket: 1
        Memory:           8.00 GB
    
        Disks:
          Index:          0
          Instance ID:    7
          Capacity:       250.00 GB
          Disk Types:     SCSI-lsilogic 
    
        NICs:
          Adapter Type:   E1000
          Connection:     VM Network
    
          Adapter Type:   E1000
          Connection:     VM Network
    
          Adapter Type:   E1000
          Connection:     VM Network
    
          Adapter Type:   E1000
          Connection:     VM Network
    
    -bash-4.1$ openssl verify -CAfile JuniperRootRSACA.pem -untrusted junos-space-certchain.pem space-16.1R1.3.cert
    space-16.1R1.3.cert: OK
    -bash-4.1$
    
  8. (Optional) If the validation is not successful, perform the following tasks:
    1. Determine whether the contents of the OVA image are modified. If the contents are modified, download the OVA image from the Junos Space Network Management Platform - Download Software page.
    2. Determine whether the Juniper Networks Root CA certificate chain file is corrupted or modified. If it is corrupted or modified, download the Root CA certificate chain file from the Junos Space Network Management Platform - Download Software page.
    3. Retry the preceding validation steps by using one or both of the new files.

Upgrading from Prior Releases of Junos Space Network Management Platform

You can upgrade to Junos Space Network Management Platform Release 16.1R2 from the following earlier releases:

To upgrade to Junos Space Platform Release 16.1R2 from releases earlier than Junos Space Platform Release 15.2R2, you must first upgrade to Junos Space Platform Release 15.2R2.

Upgrade Notes

  • During the upgrade process, do not manually reboot the nodes if the Junos Space user interface does not come up for an extended period of time. Contact the Juniper Networks Support team for help in resolving this issue.
  • Before the upgrade, ensure that the latest backups are available in a location other than the Junos Space server. For more information about backups, see Backing Up the Junos Space Network Management Platform Database.
  • When you upgrade from Junos Space Platform Release 15.2R2 to Junos Space Platform Release 16.1R2, if you have dedicated database nodes or Fault Monitoring and Performance Monitoring (FMPM) nodes configured for the Junos Space Platform setup that you are upgrading, after the upgrade and data restoration on the first node of the Junos Space fabric is complete, you must add the dedicated database nodes and FMPM nodes to the fabric by using the Junos Space Platform UI. For detailed information about upgrading to the Junos Space Platform Release 16.1R2, see Upgrading to Junos Space Network Management Platform Release 16.1R1.
  • If you have disaster recovery configured for the Junos Space Platform Release 15.2R2 setup that you are upgrading, you must upgrade both the active and standby sites to Junos Space Platform Release 16.1R2, by following the procedure outlined in Upgrading to Junos Space Network Management Platform Release 16.1R1, and then reconfigure disaster recovery. For information about configuring disaster recovery, see Configuring the Disaster Recovery Process Between an Active and a Standby Site.
  • After you upgrade the Junos Space Platform Release 15.2R2 setup to Junos Space Platform Release 16.1R2, all previously installed applications, except Junos Space Service Now Releases 15.1R3, 15.1R4, and 16.1R1, are disabled. You must upgrade the applications to releases that are compatible with Junos Space Platform Release 16.1R2, by using the Junos Space Platform UI.

    Service Now Release 16.1R1, that is installed on the setup before the upgrade, is enabled and ready to use after the upgrade. If Service Now Release 15.1R3 or 15.1R4 is installed on the setup before the upgrade, during the data backup procedure, you are prompted to specify whether you want to retain the specific Service Now release after the upgrade. If you choose to retain the Service Now release, it is enabled for use after the upgrade is completed.

    If you are taking a backup of Service Now Release 16.2R1 installed on Junos Space Platform Release 15.2R2, follow the procedure, Taking Back Up of Service Now Release 16.2R1 Data Before Upgrading Junos Space Platform to Release 16.1R1, provided in the Service Now Release 16.2R1 release notes.

  • After you upgrade Junos Space from release 15.2 or 16.1R1 to 16.1R2, during the system log registration of a device that is discovered or connects to Junos Space, a new pattern, "(requested 'commit synchronize' operation)", is added to the system log patterns on the device. When you issue a commit synchronize command, Junos Space Release 16.1R2 automatically resynchronizes only those devices that have the "(requested 'commit synchronize' operation)" pattern added to the system log patterns.

Modified: 2017-06-14