SSR Legacy Software Installation Overview

Introduction

This guide focuses on legacy software installations - those prior to version 6.3.0. The installation process changes significantly with version 6.3.0.

Welcome to Session Smart Routing - the first software-based routing solution designed to be both session-oriented and service-centric through the application of Secure Vector Routing. The purpose of this guide is to provide an overview and installation walkthrough for the SSR Router and Conductor products into a Linux operating system environment. This product suite is collectively known as SSR Software.

Before You Begin

Before you begin the installation and configuration of an SSR Networking Plaform, you must:

• Be familiar with Linux fundamentals, basic network addressing, and IP networking terminology.
• Be a system administrator to perform the installation and configuration.
• Have an entry in /etc/sudoers allowing you to execute Linux shell commands as root (via sudo). Failure to do so may result in the loss of remote management connectivity to the router.

note

The examples listed in this guide generally prefer running commands as a non-root user, except as noted, and prepend commands that must be run as a superuser with sudo. The SSH Root login is not permitted.

Installation Process

• Pre-Installation Process:
  • Download the ISOs
  • Create Bootable Media
• Legacy Installation
  • Perform the Interactive ISO installation
  • Install a Conductor
  • Create the Router configuration with the Conductor or Import a Configuration
  • Install the Router using the OTP ISO or Install the Router using the Interactive Installation

A Mist-redirect ZTP process for Conductor-managed deployments is supported on Juniper branded hardware devices - the SSR1x0/1x00. See Onboard an SSR Device to a Conductor for details about this process.

Image-based Installation

SSR Version 6.3.0 provides support for image-based installs for both Conductor- and Mist-managed deployments. Earlier installations (6.0.x - 6.2.x) using the image-based install only support Mist-managed deployments.

An image-based ISO installation process is available for users who manage their network using the Mist Cloud. This installation and upgrade process is available for SSR version 6.0.x - 6.2.x, and is only available for Mist-managed deployments. See Image-Based Installation for information and the ISO installation process.

important

The Image-Based Installation process supports Mist WAN Assurance; the Mist-managed WAN Assurance offering. Do not use the image-based installation for versions 6.0.x - 6.2.x in a conductor-managed WAN Telemetry deployment.

For customers with legacy conductor-managed deployments, the package-based installation continues to be used for upgrades and new installations.

Upgrades

Please refer to Upgrade Considerations before upgrading. Additional prerequisites include configuring a user with super user (sudo) privileges. The SSH Root login is not permitted. If the existing version allows SSH Root login, it will be disabled during the upgrade. When a system is installed using the OTP ISO, a "t128" user is configured with sudo privileges.

For full details and instructions refer to Upgrading the SSR Networking Platform.

Version Dependencies

SSR-6.3.5 Software and Version Compatibility

Beginning with SSR-6.3.5, conductor-managed routers running SSR-6.3.5 must be managed by conductors running SSR-6.3.5 or higher software. Internal updates to the software prevent successful management from a lower patch version on the conductor when 6.3.5 is installed on the router. For example:

• Conductor: SSR-6.3.5 / Router: SSR-6.3.5 Compatible
• Conductor: SSR-6.3.5+ / Router: SSR-6.3.5 Compatible
• Conductor: SSR-6.3.5 / Router: SSR-6.2.6 Compatible
• Conductor: SSR-6.3.4 / Router: SSR-6.3.5 Not Compatible
• Conductor: SSR-6.2.9 / Router: SSR-6.3.5 Not Compatible

General Dependency Information

The conductor major.minor.patch version must be greater than or equal to the router version. All versions currently under support can be run on a router and managed by the conductor, provided that the conductor version is greater. Versions of software not under support may work, but are not guaranteed to do so.

Examples:

• Conductor running version 6.0.10, managing Routers running version 6.0.5: Supported.
• Conductor running version 5.6.7, managing Routers running version 5.6.17: Not supported.
• Conductor running version 6.2.5, managing Routers running version 5.6.17: Supported.
• Conductor running version 5.6.8, managing Routers running version 6.1.3; Not supported.