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 

Upgrading Connectivity Services Director

You can upgrade Connectivity Services Director from Release 1.0R2 to Connectivity Services Director Release 2.0R1.

Before you begin:

  • Junos Space Platform Release 15.2R2 must be running before you begin to install Connectivity Services Director Release 2.0.
  • Connectivity Services Director is supported on a JA2500 Junos Space Appliance or a Junos Space Virtual Appliance that meets the hardware requirements specified in the Junos Space documentation. The Junos Space Appliance that suits your requirement depends on the number of devices you plan to manage by using the network management application.
  • You cannot install Network Director or Edge Services Director on the same system as Connectivity Services Director. Uninstall Network Director or Edge Services Director before you install Connectivity Services Director on your system.
  • When you back up the database of a Junos Space Appliance by using the Junos Space Network Application Platform database backup and restore facility, all the data maintained by the Junos Space Platform and installed Junos Space applications on the appliance is backed up. If your appliance contains a Junos Space application, such as Service Now, that you do not want to use in your network after upgrading to a different version of Junos Space Platform, you must ensure that you uninstall such applications before you perform a backup. This condition occurs because all the backed up data is restored when you use the restore utility to reapply the data after an upgrade operation. As a result, if your device was previously installed with a Junos Space application that you have not reinstalled after upgrading Junos Space Platform, restoring the backed up data causes undefined behavior because the backup in such a scenario also contains data of applications that you have not reinstalled.

Before you start the upgrade, ensure that you have:

  • Disabled monitoring for all categories in the Monitoring tab of the Preferences page. For more details, see Disabling Data Collection for Monitors.
  • Taken a back up your database using the Junos Space backup feature. For more details, see Backing Up and Restoring the Database Overview.
  • Junos Space Release 15.2R2 is running on your appliance. If your appliance is running an unsupported release of Junos Space, you must upgrade Junos Space before installing Connectivity Services Director. For step-by-step instructions on upgrading Junos Space, see Upgrading Junos Space.
  • Downloaded the Connectivity Services Director Release 2.0R1 software image to the hard disk or to an SCP server. The Connectivity Services Director software images are located at https://www.juniper.net/support/downloads/space.html .

If Connectivity Services Director Release 1.0R2.6 is installed on Junos Space Platform 15.1R1 and you try to upgrade to Junos Space Platform Release 15.2R2, the upgrade fails. This issue occurs because of a conflict between two RPM files.

Workaround:

  1. Before upgrading Junos Space Platform, do the following:

    Note: If your Junos Space setup contains more than one node, you must perform these steps for all nodes in the fabric.

    1. Connect to the Junos Space VIP node (by using SSH) and log in (as the admin user) to access the Junos Space CLI.

      The Junos Space Settings Menu appears.

    2. Type 6 (if the node is a hardware appliance) or 7 (if the node is a virtual appliance) to open a debug (command) prompt.

      You are prompted to enter your password.

    3. Type the password for the admin user and press Enter.

      You are taken to the shell.

    4. Run the rpm -qa|grep jmp-csd command to determine the Connectivity Services Director RPM to uninstall. A sample output is as follows:
      [root@host ~]# rpm -qa|grep jmp-csd
          jmp-csd-1.0-367423
    5. Run the rpm -e --nodeps rpm-name command to uninstall the RPM, where rpm-name is the name of the RPM obtained in the preceding step.
    6. Run the rpm -qa|grep jmp-csd command to confirm that the RPM was uninstalled successfully. The command produces no output if the RPM was uninstalled successfully.
    7. Exit the shell and log out of the Junos Space VIP node.
  2. Upgrade Junos Space Platform from Release 15.1R1 to Release 15.2R2.
  3. After Junos Space Platform is upgraded successfully, reinstall the Connectivity Services Director RPM that you previously uninstalled:

    Note: If your Junos Space setup contains more than one node, you must perform these steps for all nodes in the fabric.

    1. Log in to the Junos Space CLI on the VIP node and access the shell.
    2. Run the /usr/bin/extract_image.sh -i /var/cache/jboss/jmp/Connectivity-Services-Director.1.0R2.6/Connectivity-Services-Director.1.0R2.6.img -s /etc/pki/jmp-softwareManager/certs/JunosSpaceSoftwareCA_v1.pem -t /etc/pki/jmp-softwareManager/certs/JunosSpaceTrusted_CAs.pem -d /home/admin/ command to extract the Connectivity Services Director RPM that you previous uninstalled from the Connectivity Services Director software image.

      The RPM is extracted to the /home/admin/Connectivity-Services-Director.1.0R2.6 directory.

    3. Run the rpm -ivh --force jmp-csd-1.0-367423.x86_64.rpm command to install the Connectivity Services Director RPM. A sample output follows.
      [root@space-0050569e39b6 ~]# rpm -ivh --force jmp-csd-1.0-367423.x86_64.rpm
            Preparing...                ########################################### [100%]
              1:jmp-csd                ########################################### [100%]
           File exists so just check for the strings     modprobe ip_conntrack_ftp present
           modprobe ip_conntrack_tftp present
           File exists so just check for the strings
           string present - so just replace the value
    4. Exit the shell and log out of the Junos Space VIP node.
  4. Reboot Junos Space Platform to finish the upgrade.

A prescribed order is always required for the upgrade of Connectivity Services Director. Use the following table to determine the order required for your upgrade:

Type of Upgrade or Installation

Required Order of Installation

Upgrade from Connectivity Services Director Release 1.0R1 or 1.0R2 to Release 2.0

Before you start the upgrade, ensure that you have:

  • Disabled monitoring for all categories in the Monitoring tab of the Preferences page. For more details, see Disabling Data Collection for Monitors.
  • Taken a back up your database using the Junos Space backup feature. For more details, see Backing Up and Restoring the Database Overview.
  • Junos Space Release 15.2R2 running on your appliance. If your appliance is running an unsupported release of Junos Space, you must upgrade Junos Space before installing Connectivity Services Director.
  • Downloaded the Connectivity Services Director Release 2.0 software image to the hard disk or to an SCP server. The Connectivity Services Director software images are located at https://www.juniper.net/support/downloads/space.html .
  1. Ensure that Junos Space Network Management Platform Release 15.2R2 is running.
  2. Install Connectivity Services Director Release 2.0R1.
  3. Restart the JBoss server for the monitoring and fault features to work properly in standalone and cluster setups:

    To restart the JBoss server in a standalone setup:

    1. Stop the watchdog, domain controller, and JBoss services on the standalone node.

      service jmp-watchdog stop

      service jboss-dc stop

      service jboss stop

    2. Start the watchdog service.

      service jmp-watchdog start

      Note: Starting the watchdog service restarts the JBoss and domain controller services as well.

      It takes approximately 20 minutes for the JBoss server to come up after the restart.

    To restart the JBoss server in a cluster setup:

    1. Stop the services on the secondary node.

      service jmp-watchdog stop

      service jboss stop

    2. Stop the services on the master node (You can find the VIP hosted node Space > Fabric).

      service jmp-watchdog stop

      service jboss-dc stop

      service jboss stop

    3. Start the services on the master node.

      service jmp-watchdog start

    4. Start the service on the secondary node.

      service jmp-watchdog start

      It takes approximately 20 minutes for the JBoss server to come up after the restart.

Upgrade from Network Activate Release 14.3R1, Transport Activate 14.3R1, OAM Insight 14.3R1 and Sync Design 14.3R1 to Connectivity Services Director Release 2.0

Note: You cannot directly upgrade to Connectivity Services Director Release 2.0 from the applications in Services Activation Director Release 14.3R1 or 14.3R2, such as Network Activate, NetworkAppsApi, Transport Activate, OAM Insight, QoS Design, and Sync Design. You must first upgrade from Services Activation Director Release 14.3R1 or 14.3R2 to Connectivity Services Director Release 1.0R2, and then upgrade to Connectivity Services Director Release 2.0.

If you are running a version of Network Activate, Transport Activate, OAM Insight, or Sync Design earlier than 14.3R1, you must first upgrade to 14.3R1 or later before you can upgrade to Connectivity Services Director 1.0R2.

  1. Back up the Junos Space Network Management Platform database.
  2. Upgrade Junos Space Platform to Release 15.1R1.
  3. Install Connectivity Services Director 1.0R2.
  4. Uninstall other applications (such as Junos Space QoS Design or Junos Space Transport Activate) as needed before you uninstall Network Activate.
  5. Uninstall Network Activate and NetworkAppsApi.
  6. Restart the JBoss server.

    Note: QoS Design cannot be installed on the same system as Connectivity Services Director. After the uninstallation of the legacy applications, such as Network Activate 14.3R1, Transport Activate 14.3R1, Sync Design 14.3R1, or OAM Insight 14.3R1, wait until the applications are removed from the Applications page of the Junos Space Platform application. After all the applications are uninstalled, restart the JBoss server. Connectivity Services Director does not work correctly if the JBoss server is not rebooted.

  7. Upgrade Junos Space Network Management Platform to Release 15.2R2.
  8. Upgrade Connectivity Services Director to Release 2.0R1.
  9. Restart the JBoss server

To upgrade Connectivity Services Director from the Administration > Applications display of Junos Space:

  1. Select Connectivity Services Director from the list of installed applications and click Upgrade Application from the Actions menu.
  2. In the Upgrade Application page, click either Upload via HTTP or Upload via SCP and navigate to the location where you stored the Connectivity Services Director image.

    To upload Connectivity Services Director by using HTTP:

    1. Click Upload via HTTP to open the dialog box.
    2. Navigate to the local location where the Connectivity Services Director image is stored.
    3. Select the image file and click Open to load the path.
    4. Click Upload to load the image file into Junos Space.

    To upload Connectivity Services Director by using SCP:

    1. Click Upload via SCP to open the Upload dialog box.
    2. Enter the Secure Copy credentials to upload the Connectivity Services Director image from a remote server to Junos Space.
      • Enter the username.
      • Enter the password and reenter the password in the Confirm Password field.
      • Enter the host IP address.
      • Enter the local path name of the Connectivity Services Director application file.
    3. Click Upload to load the image file into Junos Space.
  3. Click OK to skip viewing the job results.
  4. Select Connectivity Services Director and click Upgrade.

    You can check the Job Status page to see the progress of the upgrade job. Once the upgrade completes, Connectivity Services Director appears on the Applications inventory page. The new or upgraded application also appears in the Application Chooser (at the upper-left corner).

  5. After you upgrade Connectivity Services Director, you must restart the JBoss server for the monitoring and fault features to work properly in standalone and cluster setups:

    To restart the JBoss server in a standalone setup:

    1. Stop the watchdog, domain controller, and JBoss services on the standalone node.

      service jmp-watchdog stop

      service jboss-dc stop

      service jboss stop

    2. Start the watchdog service.

      service jmp-watchdog start

      Note: Starting the watchdog service restarts the JBoss and domain controller services as well.

      It takes approximately 20 minutes for the JBoss server to come up after the restart.

    To restart the JBoss server in a cluster setup:

    1. Stop the services on the secondary node.

      service jmp-watchdog stop

      service jboss stop

    2. Stop the services on the master node (You can find the VIP hosted node Space > Fabric).

      service jmp-watchdog stop

      service jboss-dc stop

      service jboss stop

    3. Start the services on the master node.

      service jmp-watchdog start

    4. Start the service on the secondary node.

      service jmp-watchdog start

      It takes approximately 20 minutes for the JBoss server to come up after the restart.

  6. Download the DMI schemas for devices that require a later schema, and upload the schema to the Junos Space.
  7. To work on Connectivity Services Director, select Connectivity Services Director from the Applications list in the upper left corner above the Tasks tree.

    Connectivity Services Director starts in the browser window. The default view is the Dashboard View. Use the View selector on the top banner to navigate to the other views—Location View, Device View, Topology View, Custom Group View, or the Service View.

  8. Bookmark this page in your browser for future use.

    You can use the bookmarked URL to log in to Connectivity Services Director without logging in to Junos Space first.

Modified: 2016-07-14