Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40

Sandvine Policy Traffic Switch
Software Installation and Upgrade

Guide, Release 7.40
05-00245-D08
2016-11-26
Notices
The most current version of this document is available on the Sandvine Customer Support website at https://support.sandvine.com.
This document and the products described within are subject to copyright. Under copyright laws, neither this document nor the
product may be reproduced, translated, or reduced to any electronic medium or machine readable or other form without prior
written authorization from Sandvine.
Copyright 2016, Sandvine Incorporated ULC. All rights reserved. Sandvine™ is a trademark of Sandvine Incorporated ULC. All
other product names mentioned herein are trademarks of their respective owners.
Sandvine is committed to ensuring the accuracy of our documentation and to continuous improvement. If you encounter errors
or omissions in this user guide, or have comments, questions, or ideas, we welcome your feedback. Please send your comments
to Sandvine via email at https://support.sandvine.com.
Contacting Sandvine
To view the latest Sandvine documentation or to contact Sandvine Customer Support, register for an account at
https://support.sandvine.com.
See http://www.sandvine.com/about_us/contact.asp for a list of Sandvine Sales and Support offices.
2 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Related Documentation
Related documentation is available from Sandvine’s Customer Support web site. All documents are in PDF format and can be
opened and read or printed using Adobe® Acrobat® Reader®. You can obtain a free copy of this software from the Adobe® web
site.
Document Part Number

Getting Started with Sandvine 05-00011
PTS Administration Guide 05-00192
PTS Alarms Reference Guide 05-00262
PTS CLI Reference Guide 05-00263
PTS Hardware Installation Guide 05-00185
PTS Software Installation and Upgrade Guide 05-00245
PTS SandScript Guide 05-00217
PTS Virtual Platform User Guide 05-00269
Sandvine API User Guide 05-00330
Subscriber Mapping User Guide 05-00209
Network Protection User Guide 05-00301
Web Content Intelligence User Guide 05-00325
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 3
05-00245-D08
4 | Sandvine | TOC
Contents
1 Before You Begin..........................................................................................................................................................6
1.1 Read This First......................................................................................................................................................7
1.2 CLI Changes.........................................................................................................................................................7
1.3 Special Circumstances..........................................................................................................................................8
1.4 Downloading Upgrade Files..................................................................................................................................8
1.4.1 Install svupdate and/or Download Files..........................................................................................................8
1.4.2 For Elements without Internet Access............................................................................................................9
2 Downgrade Instructions..............................................................................................................................................12
2.1 Downgrade Notes................................................................................................................................................13
2.1.1 Downgrade Compatibility for PTS Hardware................................................................................................13
2.1.2 Downgrading Elements that Use the Second Management Port.................................................................13
2.1.3 Downgrade Compatibility for SPB Scaling Connections..............................................................................14
3 Upgrade from 6.00 or later.........................................................................................................................................16
3.1 Pre-requisites......................................................................................................................................................17
3.2 Pre-Installation....................................................................................................................................................17
3.2.1 Verifying System Installed with 6.00 or Later...............................................................................................17
3.2.2 Preparing for Installation..............................................................................................................................18
3.3 Installation...........................................................................................................................................................19
4 Upgrading from Releases Earlier than 6.00...............................................................................................................20
4.1 CLI Changes.......................................................................................................................................................21
4.2 Pre-Installation....................................................................................................................................................21
4.2.1 Verifying Pre-6.00 Systems..........................................................................................................................21
4.3 Installation...........................................................................................................................................................22
4.3.1 Installation Pre-requisites.............................................................................................................................23
4.3.2 Bypassing Traffic - Bypass Chassis.............................................................................................................23
4.3.3 Bypassing Traffic - Bypass Card or Blade....................................................................................................23
4.3.4 Disabling Cluster Ports.................................................................................................................................24
4.3.5 Upgrade and Downgrade Notes for Sandvine CLI ......................................................................................24
4.3.6 Re-enabling Cluster Ports............................................................................................................................25
4.3.7 Reapplying Traffic.........................................................................................................................................25
5 Post-installation..........................................................................................................................................................26
5.1 Post-installation...................................................................................................................................................27
5.1.1 Validating the Installation..............................................................................................................................27
5.1.2 Configuring the SPB Version........................................................................................................................27
5.1.3 Verifying the PTS..........................................................................................................................................27
6 Using the svupdate Command to Upgrade, downgrade or Install the Packages.......................................................30
05-00245-D08
Sandvine | TOC | 5
6.1 About the svupdate Command............................................................................................................................31

6.2 Updating svupdate..............................................................................................................................................31
6.3 Using the svupdate Menu....................................................................................................................................31
6.4 Downloading Packages.......................................................................................................................................31
6.5 Running Pre-Checks...........................................................................................................................................31
6.6 Performing an svupdate......................................................................................................................................32
6.6.1 For Elements with Internet Access...............................................................................................................32
6.6.2 For Elements without Internet Access (FreeBSD only)................................................................................32
6.7 Resuming Installation after a Reboot..................................................................................................................33
6.8 svupdate Commands..........................................................................................................................................33
6.8.1 Command Options.......................................................................................................................................33
6.8.2 Examples......................................................................................................................................................34
05-00245-D08
Before You Begin
1
Before You Begin
• "Read This First" on page 7
• "CLI Changes" on page 7
• "Special Circumstances" on page 8
• "Downloading Upgrade Files" on page 8
05-00245-D08
Before You Begin
Read This First
1.1 Read This First

Before you begin upgrading the PTS you should:
1. If you do not have a support account, refer to Obtaining a Support Account on page 9
2. Document your current installation, including:
• PTS hardware version.
• PTS software version.
• Other Sandvine products installed on the PTS.
• PTS cluster topology.
• SPB software version.
• SDE software version.
• PTS firmware.
• Confirm that the PTS does or does not have access to the Sandvine Support Site.
See the documentation for your currently installed software version for details on how to obtain this information.
3. Document the system's current performance using one of these procedures:
• See Verifying System Installed with 6.00 or Later on page 17 for platforms running PTS 6.00 or higher.
• See Verifying Pre-6.00 Systems on page 21 for platforms running earlier releases.
4. Follow these upgrade notes with respect to Control Center Synchronization.
Note:
• Before upgrade, ensure that the PTS element is in-sync with the Control Center, to avoid loss of any configuration
during the upgrade. See the Synchronization States section in the Control Center User Guide, for additional
information.
• When the upgrading of the PTS element to 7.00.01 version is complete, the Control Center will report that the PTS
configuration is out-of-sync. You must accept the configuration on the element; otherwise, the Control Center may
apply outdated configuration on the PTS element.
5. Read the release notes for the release you are upgrading to. Review these items:
• Compatibility matrix.
• New behaviors.
• Caveats and limitations.
6. Schedule a maintenance window for the upgrade.
7. Check if your system has one of the special circumstances, see Special Circumstances on page 8.
8. Choose an upgrade path:
• See Upgrade from 6.00 or later on page 16 if you are upgrading from 6.00 or later.
• Otherwise, see Upgrading from Releases Earlier than 6.00 on page 20.
1.2 CLI Changes

As of the PTS 6.00.00 software release, configuration changes are accomplished using the CLI in configuration mode. Sandvine
recommends using the CLI to configure the system. However, if you are upgrading from a release earlier than 6.00.00, you need
to make some configuration changes before you can upgrade to the current release.
05-00245-D08
Before You Begin
Special Circumstances
1.3 Special Circumstances

Note the upgrade processes for these special circumstances:
Virtual Switch Cluster

When migrating PTS elements in a virtual switch cluster, sandvine recommends that you upgrade the cluster as a whole, during
a maintenance window. Alternatively, you should break the cluster into smaller sub-clusters and the sub-clusters migrated as
maintenance windows become available.
1.4 Downloading Upgrade Files

Use svupdate to install or upgrade packages on PTS or SPB for FreeBSD only.
Download the svupdate files using one of these methods:
• See Install svupdate and/or Download Files on page 8 if the elements are connected to the internet.
• See For Elements without Internet Access if the elements do not have an internet connection.
1.4.1 Install svupdate and/or Download Files

Before beginning the installation, ensure to use the updated svupdate utility (PTS FreeBSD and SPB FreeBSD only). For
elements with internet access, svupdate will upgrade itself to the latest version before running. See For Elements without
Internet Access on page 9 if the element you are upgrading does not have access to the internet. Use these steps for elements
with internet access:
1. Enter: svupdate at the command line.
2. Enter your Sandvine Customer Support username and password when prompted.
Your username is your email address. If you have a user account made prior to 2013, you may need to replace the "@"
with a "." For example, user@mycompany.com becomes user.mycompany.com.
3. Press q to quit, if you are not prompted to upgrade. Otherwise press y.
4. Select the latest release.
5. Select PTS from the product family listing.
Select Product Family

---------------------
1. PTS (installed)
6. Select the latest release that you want to upgrade from the release menu.
7. Confirm the release version selected by choosing install.
Select Action
-------------
1. Select PTS 7.20 for install
05-00245-D08
Before You Begin
Downloading Upgrade Files
1.4.2 For Elements without Internet Access

In order to upgrade an element without internet access, you need to download the install files (tarball) from the Sandvine FTP
server from a device with internet access, and then perform the upgrade.
Tarball is a standard file format (for example tar, pax, cpio, zip, jar, and ar) which contains install files in a compressed form. To
perform upgrade using tarball ensure that an online machine and an offline element are on the same network.
See... To...
Obtaining a Support Account on page 9 Obtain Sandvine Customer Support account.
Downloading Files from the Sandvine FTP server on page 9 Download the release tarball.
1.4.2.1 Obtaining a Support Account

A Sandvine Customer Support Account gives you access to software releases, product documentation, and other support.
1. Go to https://support.sandvine.com.
2. Enter your email address in the New User? dialog, and then click Submit Query.
You will receive an email acknowledgment shortly after confirming your account activation. In some cases, account activation
can take as long as two business days.
1.4.2.2 Downloading Files from the Sandvine FTP server

Download a tarball and/or md5sum file using this procedure to upgrade Sandvine elements that are offline.
Note:
You must have an active Sandvine Customer Support Account. See Obtaining a Support Account on page 9.
1. Log in to the Sandvine Customer Support website at https://support.sandvine.com.
2. To access the release link for the first time:

a. Click Update Portal User Settings.
b. Enter the password in the FTP Password dialog.
c. Enter the same password into the Verify FTP Password dialog. It can take up-to 10 minutes to activate your password.
3. Click Document/Release.
4. Enter your user name and FTP password into the Authentication Required dialog.
The file directory opens.
5. Select the Product directory.
6. Select the model and software version of the files you require.
7. Select a tarball and md5sum file to download them.
1.4.2.3 Using Tarballs

Once the tarball is downloaded to an online machine, you need to transfer it to the offline element you want to upgrade.
05-00245-D08
Before You Begin
Perform these steps to transfer a tarball from an online machine to an offline element:
1. Copy the tarball to /d2/tmp on an offline element.
• Run the scp command on an online machine to copy the tarball onto an offline element.
Note:
The scp command runs a remote file copy program that copies files between hosts on a network.
• Run the fetch command on an offline element to transfer files from the online machine.
2. Run the cd /d2/tmp command to navigate to the /d2/tmp location.
3. Verify that the file has transferred to the offline element and exists in /d2/tmp.
4. Run the md5sum -c <mmd5sum file> command. Compare the md5sum of the tar file and the md5sum file (PTS and SPB
only) to verify the file downloaded successfully.
If the md5sum does not match, re-download the tarball from the Sandvine Customer Support website.
5. Check the available free space. If the /tmp utilization is less than 50%, then continue with step 8; otherwise, run the
svptsd.sh stop command to stop PTSD.
Note:
Running the svptsd.sh stop command stops the traffic.
6. Run the show system services CLI command to confirm if the PTSD is online. Wait or repeat this step until PTSD
becomes online.
7. Install the tarball.

a. For PTS 6.15 or higher, you can install the tarball using svupdate 7.15 or higher by running the command svupdate
--release-image=<file>, where the software release contained in the specified <file> is installed. However,
do not use this command with any of the commands listed in the above procedure.
b. For older versions, run tar –xvf <tarball> to unpack the tarball to the current working /d2/tmp directory, then
run svupdate –U /d2/tmp.
8. Follow the steps on screen.

You are prompted to do an svupdate. Repeat the svupdate command you used in step 8.
05-00245-D08
Before You Begin
05-00245-D08
Downgrade Instructions
2
• "Downgrade Notes" on page 13
05-00245-D08
Downgrade Notes
2.1 Downgrade Notes

Use these notes to prepare for a downgrade.
2.1.1 Downgrade Compatibility for PTS Hardware

Run the show system information CLI command to identify your hardware model. You can, when required, downgrade
PTS hardware to a version no earlier than these releases:
PTS Hardware Earliest Supported Software Release

BLD 22006 6.10
PTS 22600-B 6.20, 6.15.01
PTS 22600-C 6.30
BLD 24080 6.20
PTS 24700-D 6.20
PTS 24700-E 6.30
BLD 32042 7.00.01
BLD 32080 7.10.00
PTS 32400-A 7.00.01
PTS 32400-B 7.20
PTS 32100-B 7.30.04
PTS 32000-C 7.40.00
2.1.2 Downgrading Elements that Use the Second Management Port

If the second management port was used exclusively, downgrading can cause the PTS to lose SSH connectivity.
In PTS 6.10 and above, you can use both management ports for SSH connectivity on the PTS 22000, PTS 24000, and PTS
32000. If the first management port (mgmt1) is disabled (or operationally down), management connections are still possible over
the second port (mgmt2) which continues to operate. In this case, it is necessary to re-establish the functionality of mgmt1 before
downgrading to PTS 6.00 and earlier in order to maintain management connectivity.
Run the show interface management CLI command to check the status of the management interfaces, on an element that
has PTS 6.10 or higher installed.
PTS> show interface management
AGGREGATE MANAGEMENT INTERFACE
==============================
Port Redundancy IpAddress AdminStatus OperStatus PrimaryPort

------------ ---------- ------------- ----------- ---------- -----------
[management] [failback] 10.10.10.1 [up] [degraded] mgmt2
Port SecondaryPort MTU

------------ ------------- -----
[management] mgmt1 1,500
05-00245-D08
Downgrade Notes
MEMBER INTERFACES
=================
Port AdminStatus OperStatus

----- ----------- ----------
mgmt1 [up] [down]
mgmt2 [up] [up]
Alternately, run the show alarms CLI command and look for an alarm such as:
43 Network interface down: Control mgmt1
2.1.3 Downgrade Compatibility for SPB Scaling Connections

This section provides the configurations required when the PTS is downgraded from any higher version (for example: 7.00.01)
to the PTS 7.00 version, which supports connection to a single SPB only.
Note these points during the downgrade process of a PTS is configured to connect with multiple SPB domains in a higher PTS
version to a lower release version (less than equal to PTS 7.00 version):
• All the previously configured connections to the SPB domain(s) should be removed, and
• The PTS should be configured to connect to only one SPB. This is because the PTS connections to multiple SPB domains
are not supported on release versions lower than 7.00.01.
Perform these steps to remove the previously configured SPB connections:
1. As an administrative user, run the configure command to enter the PTS CLI configuration mode.
2. Run the reset config service spb servers CLI command to reset the SPB server connections.
3. Run the reset config service spb domain CLI command to reset the SPB domain connections.
The PTS connections to the SPB servers/domains configured for the higher version (example: 7.00.01) are removed, and
you can configure a single SPB connection for the lower PTS release version (for example: 7.00).
To configure the PTS connections to a single SPB, to downgrade to the lower PTS version:
4. Run the set config service spb servers “SPB IP/URI” CLI command, where the SPB IP/URI is the single SPB
which should be connected after PTS is downgraded to the version lower than 7.00.01.
5. Run the commit CLI command to commit the configuration changes.
05-00245-D08
Downgrade Notes
05-00245-D08
Upgrade from 6.00 or later
3
• "Pre-requisites" on page 17
• "Pre-Installation" on page 17
• "Installation" on page 19
05-00245-D08
Pre-requisites
3.1 Pre-requisites
To use these upgrade steps, the PTS element must have this software installed:
• svupdate version 7.15 or later for PTS machines with internet access. For PTS machines without internet access, use the
pre-installed svupdate version.
• PTS 6.00 or later
If these pre-requisites are not met, follow the installation instructions in Upgrading from Releases Earlier than 6.00 on page 20.
3.2 Pre-Installation
These sections outline tasks to perform on the element being upgraded prior to installation.
3.2.1 Verifying System Installed with 6.00 or Later

Verify that the system is working correctly. Sandvine recommends that you save all verification output into a separate file for post
install verification. You should resolve any alarms or problems should before proceeding with the installation.
1. Review the caveats section of the PTS Release Notes for any known issues that may impact your deployment.
2. Collect and save the information retrieved using these CLI commands:
For this information: Run this CLI command:
The model number of the device you are upgrading. show system information
All currently installed software. show system version detail
The alarm history. show alarms history limit 1000
The current traffic levels. show interface rate
The current system resource utilization. show system resources
3. This is an optional step. Run the svtechsupport command to gather an svtechsupport report. Since this report can take
20 minutes or more to run, you and should consider running it during your maintenance window. However, it can provide
valuable information if there is a problem during installation.
4. Run the command: tail -1000 /var/log/svlog command to check for svlog errors, especially around the previous
reload or reboot.
5. Run the show service spb connections CLI command to verify that the PTS is connected to an SPB (for PTS 7.00
or above).
6. Run the show system resources 2 command to ensure that the Free column is 400M or higher for each row.
05-00245-D08
Pre-Installation
7. Run the show system resources 7 CLI command to verify that there is at least 2GB of disk space available on the /d2
partition.
8. Run the show system resources 6 CLI command to verify that there is at least 200MB of disk space available on the
root partition.
9. Review the deprecated protocols list in the latest Loadable Traffic Identification Package release notes and remove them
from your SandScript file.
10. Check if your SSH connection to the PTS is routed through the data plane. If so, you may lose connectivity to the PTS during
the upgrade. Use one of these steps to avoid this:
• Use the console port to connect to the PTS and perform the upgrade.
• Use the bypass instructions below to maintain traffic during the upgrade.
3.2.2 Preparing for Installation

Prepare the system for install by enabling bypass mode and disabling cluster ports.
3.2.2.1 Bypassing Traffic

If your PTS is connected to a bypass chassis, card or blade, then you can bypass traffic by using these steps.
1. Run the configure CLI command, as an administrative user, from the configuration mode.
2. Put the PTS into the bypass mode using one of these options:
• If your PTS is connected to a bypass chassis, run: set config interface bypass external admin-status
bypass
• If your PTS is equipped with a bypass card or bypass blade, run show interface bypass . For every bypass port
with the AdminStatus “software”, run: set config interface bypass <interface> admin-status bypass.
Where <interface> is the index number to bypass.
The show interface bypass command provides output containing an Index column. The value in the Index column is
what is required for the set config interface bypass <interface> admin-status bypass command.
3. Run the commit CLI command to commit the change.
4. Run the show alarms CLI command to check for any new alarms.
5. Note down the changes you made so you can re-enable the functionality during the post-install process.
3.2.2.2 Disabling Cluster Ports

To disable cluster ports:
1. Run the configure CLI command, as an administrative user, from the configuration mode.
2. Run the show interface configuration CLI command to determine which ports are configured as cluster ports.
3. Run the set config interface <interface> enabled false CLI command, to disable for every port that has
AdminStatus up and Function cluster. Where <interface> is the port to disable.
05-00245-D08
Installation
4. Run the commit CLI command to commit the change.
5. Note the changes you made so you can re-enable the functionality during the post-install process.
3.3 Installation
To install the release:
1. Run one of these commands:
• Run svupdate, on elements with internet access,and then enter your Sandvine Customer Support username and
password.
• Run svupdate --release-image=<file>, on elements without internet access, where the software release contained
in the specified<file> is installed.
Note:
If svupdate --release-image=<file> is used to install the PTS 7.35 or the PTS 7.40, without internet access,
then run svupdate --release-file=<release.xml> --release-image=<file> to downgrade the
element to an older software release. The <release.xml> refers to the latest release.xml file available at
ftp://ftp.support.sandvine.com.
2. Press y if prompted to upgrade svupdate.
3. Select PTS on the Family menu.
4. Select the appropriate model of PTS from the Product list.
5. Select the latest release of the software on the Select list.
6. Select 1. Install images on the Operation menu.
7. Monitor the svupdate output for any errors.
8. Once the upgrade completes check the Validate Install Summary section, in the svupdate output for any errors. The PTS
automatically reboots when the upgrade is successful.
Note:
It can take up to 10 minutes for a PTS to fully reboot and for all services to come back online.
9. Verify the system, see Post-installation on page 27.
05-00245-D08
Upgrading from Releases Earlier than 6.00
4
Upgrading from Releases Earlier
than 6.00
• "CLI Changes" on page 21
• "Pre-Installation" on page 21
• "Installation" on page 22
05-00245-D08
CLI Changes
4.1 CLI Changes

As of the PTS 6.00.00 software release, configuration changes are accomplished using the CLI in configuration mode. Sandvine
recommends using the CLI to configure the system. However, if you are upgrading from a release earlier than 6.00.00, you need
to make some configuration changes before you can upgrade to the current release.
4.2 Pre-Installation
These sections outline tasks to perform on the element being upgraded prior to installation.
4.2.1 Verifying Pre-6.00 Systems

Use these preliminary steps to verify that the system is working correctly. Sandvine recommends that you save all verification
output into a separate file for post install verification. Any alarms or problems should be resolved before proceeding with the
installation.
1. Review the caveats section of this document for any known issues that may impact your deployment.
2. This is an optional step. Run the svtechsupport CLI command to gather an svtechsupport report. This report can take
20 minutes or more to run and you should consider running it during your maintenance window. However, it can provide
valuable information if there is a problem during installation.
3. Collect and save the information retrieved using these CLI commands:
For this information: Run this CLI command:

The model number of the device you are upgrading show system information
Note:
On older systems, you can run the cat /etc/model CLI
command to identify the model number.
All currently installed software show system version detail
Note:
On older systems, use the show version detail CLI
command.
The alarm history show alarms history limit 1000
The current traffic levels show interface rate
The current system resource utilization show system resources
4. Run the tail -1000 /var/log/svlog CLI command to check for svlog errors, especially around the previous reload
or reboot.
Errors on the last reload may appear during the upgrade.
05-00245-D08
Installation
5. Verify that the PTS is connected to an SPB using the appropriate CLI command.
Run the CLI Command... With Release...

show spb connections 5.60 and above
show service spb connections 6.00 and above
6. Verify that CPU usage (check for free memory) is less than 65% using one of these options:
• If upgrading from 6.00, run the command: show system resources 66
• If upgrading from 5.60 or below, run the command: show system cpu 1
7. Run the df -h /d2 CLI command to verify that there is at least 2 GB of disk space available on the /d2 partition.
8. Run the ssh module-1 top | grep Free CLI command to verify that there is sufficient free memory available. The
PTS requires at least 400M of free memory.
9. Run the df -h / CLI command to verify that there is at least 200MB of disk space available on the root partition.
10. Run the wc –l /usr/local/sandvine/etc/subnets.txt CLI command to verify that your subnets.txt file is less
than 50,000 lines long.
11. Review the deprecated protocols list in the latest Loadable Traffic Identification Package release notes and remove them
from your SandScript file.
12. Check if your SSH connection to the PTS is routed through the data plane. If so, you may lose connectivity to the PTS during
the upgrade. Use one of these steps to avoid this:
• Use the console port to connect to the PTS and perform the upgrade.
• Use the bypass instructions below to maintain traffic during the upgrade.
4.3 Installation
To install the release:
1. Run one of these commands:
• On elements with internet access, run: svupdate
• On elements without internet access, see: Using Tarballs on page 9.
2. Press y if prompted to upgrade svupdate.
3. Select PTS on the Family menu.
4. Select the appropriate model of PTS from the Product list.
5. Select the latest release of the software on the Select list.
6. Select 1. Install images on the Operation menu.
05-00245-D08
Installation
7. If upgrading from 5.6 or earlier, press y to proceed with the upgrade to the operating system architecture.
The system reboots automatically.
8. Monitor the svupdate output for any errors.
9. Once the upgrade completes check the Validate Install Summary section of the svupdate output, for any errors. Run the
PTS> shutdown CLI command, if prompted to reboot the PTS.
Note:
It can take up to 10 minutes for a PTS to fully reboot and for all services to come back online.
10. Verify the system, see Post-installation on page 27.
4.3.1 Installation Pre-requisites

Before you install and configure the Virtual PTS, install the RHEL operating system that the PTS server uses, and complete the
procedures listed in this section.
When upgrading to PTS 7.40 or above, the REST API require these additional configurations to update the SSL certificate:
• Run these shell commands to update the SSL certificate:
cd /usr/local/sandvine/etc/certs
mv service.crt service.crt.bk
/usr/local/sandvine/scripts/ssl_certificate.sh
• Run these CLI commands after updating the SSL certificate:
svcli
PTS> restart service ptsd
PTS> restart service policy-engine-service
PTS> restart service service-discovery
4.3.2 Bypassing Traffic - Bypass Chassis

To bypass traffic on a PTS that is connected to a bypass chassis:
1. In the rc.conf file (/usr/local/sandvine/etc/) add these lines:
SetExtBypassAdminStatus bypass
2. Perform an svreload.
3. Note the changes you made so you can re-enable the functionality during the post-install process.
4.3.3 Bypassing Traffic - Bypass Card or Blade

To bypass traffic on a PTS equipped with a bypass card or bypass blade:
1. Run the show interface bypass CLI command.
05-00245-D08
Installation
2. For every bypass port with the AdminStatus “software”, add this line in the rc.conf file (/usr/local/sandvine/etc/):
SetBypassAdminStatus <port> bypass
For example:
SetBypassAdminStatus 1 bypass
4. Run the show alarms CLI command to check for any new alarms.
5. Note down the changes you made so you can re-enable the functionality during the post-install process.
4.3.4 Disabling Cluster Ports

To disable cluster ports:
1. Run the show interface configuration CLI command to determine which ports are configured as cluster ports.
The svupdate command will ask you to shutdown cluster ports.
2. For every port that has AdminStatus up and Function cluster (or Role cluster on some older versions), add this
to the bottom of the rc.conf file (/usr/local/sandvine/etc/):
SetPortDisable <port>
4. Note down the changes you made so you can re-enable the functionality during the post-installation process.
4.3.5 Upgrade and Downgrade Notes for Sandvine CLI

These upgrade and downgrade instructions relate to Fairshare installed on PTS 7.35 and later releases.
• The default user accounts (sv_admin, sv_service, and sv_operator) will have the default shell CLI set to Sandvine CLI
(PTS>) from PTS 7.35 and later releases. Select the desired svupdate version for PTS 7.35 for elements without internet
access. See Updating svupdate on page 31 for detailed information.
• When using the PTS for the first time, only the default user account of sv_admin is enabled for login. The default user
accounts root, sv_service, and sv_operator will be initially disabled.
• Run the set user sv_admin default-shell <bash|cli> CLI command as an admin user to change the default shell
prompt of any user.
• Upgrade notes:
During upgrade from a lower version of PTS to the 7.35 version, when a new user is added (for example using add user
<name> group <admin|service|operator> CLI command), there is a user prompt Use CLI as the default
shell? (Y/n) to select the prompt. If you select y which is the default option, the prompt sets to Sandvine CLI prompt
(PTS>). If you select option n, the CLI prompt is set to bash prompt(#). If you do not select any option, the prompt sets to the
default Sandvine CLI prompt (PTS>).
• Downgrade notes:
During downgrade from PTS 7.35 to a lower version, when a new user is added (for example using add user <name>
group <admin|service|operator> CLI command), a message is displayed where you can select the default prompt
as Use CLI as the default shell? (y/n) . If you select n which is the default option, the prompt sets to bash prompt
05-00245-D08
Installation
(#). If you select y, the prompt sets to Sandvine CLI prompt (PTS>). If you do not select any option, the prompt sets to the
default bash prompt (#).
4.3.6 Re-enabling Cluster Ports

To re-enable the cluster ports on each PTS, once all the PTSes in the cluster are upgraded to latest release:
1. Run the configure CLI command, as administrative user, in the configuration mode.
2. For each port disabled in Disabling Cluster Ports on page 24, run: set config interface <port> enabled true.
3. Run the commit CLI command, after completing the configuration, to commit the changes. The system will automatically
reload and this can impact service.
4. Run the show service load-balancer modules CLI command, then wait until all modules have Status up before
proceeding.
5. If the output of the previous step shows all traffic going to one PTS, run the clear service load-balancer CLI
command to clear the state of the load balancer.
4.3.7 Reapplying Traffic

1. Run the configure CLI command, as an administrative user, to enter the CLI configuration mode.
2. Run one of these commands to take the PTS out of bypass configuration:
• Run the set config interface bypass external admin-status software CLI command if your PTS is
connected to a bypass chassis.
• Run the set config interface bypass <index> admin-status software CLI command, if your PTS is
equipped with a bypass card or bypass blade, for every port that was bypassed in Bypassing Traffic - Bypass Card or
Blade on page 23.
3. Run the commit command, to commit the configuration changes. Note that the system automatically reloads and this can
impact service.
05-00245-D08
Post-installation
5
Post-installation
• "Post-installation" on page 27
05-00245-D08
Post-installation
Post-installation
5.1 Post-installation
Follow these procedures to validate the install and re-enable features that were disabled during the pre-installation stage.
5.1.1 Validating the Installation

To verify the current state of the system:
1. Run the show system version CLI command to verify the software version.
2. Run the show system services CLI command to verify system services.
3. Run the show alarms CLI command to verify the current alarms.
4. This is an optional step. Gather an svtechsupport report by running the svtechsupport command. This report can take
20 minutes or more to run and you should consider running it during your maintenance window. However, it can provide
valuable information if there was a problem during installation.
5.1.2 Configuring the SPB Version

If the PTS/SDE is connected to an SPB running version 6.40.01 or earlier, run the show config service spb version CLI
command on the PTS/SDE to determine the configured SPB version.
If this does not match the actual SPB version, run the set config service spb version <version> CLI command.
Where <version> is one of 5.40, 5.51, 5.60, 6.00, or 6.20.
Note:
Since all versions are currently not available, use the closest version that is not higher than the actual SPB version.
5.1.3 Verifying the PTS

To verify the PTS:
1. Run the show alarms CLI command to verify current active alarms.
2. Run the show interface rate CLI command to verify current traffic levels.
3. Run the show interface counters data CLI command to verify there are no incrementing errors on the data interfaces.
4. If there are any errors, run clear interface counters data, then run show interface counters data again.
5. Run the show system services CLI command to verify the operation of the PTS.
6. Run the show system resources CLI command to verify that the current system resources capacity is less than 90%.
7. Run the show service spb connections CLI command to verify the connection with the SPB.
05-00245-D08
Post-installation
Post-installation
The OperStatus should indicate [connected].
8. Run the show service subscriber-management dashboard CLI command to verify communication with the SPB.
9. When traffic has run through the PTS for at least 30 minutes, run a report for the last hour.
05-00245-D08
Post-installation
Post-installation
05-00245-D08
Using the svupdate Command to Upgrade, downgrade or Install the Packages
6
Using the svupdate Command to
Upgrade, downgrade or Install the
Packages
This section provides information about upgrading software on Sandvine elements.
• "About the svupdate Command" on page 31

• "Updating svupdate" on page 31
• "Using the svupdate Menu" on page 31
• "Downloading Packages" on page 31
• "Running Pre-Checks" on page 31
• "Performing an svupdate" on page 32
• "Resuming Installation after a Reboot" on page 33
• "svupdate Commands" on page 33
05-00245-D08
About the svupdate Command
6.1 About the svupdate Command

Use svupdate to install or upgrade packages on an element (PTS and SPB running FreeBSD only). Run the svupdate command
from a bash shell (or command line) to guide you through an interactive menu system to select and install the desired software
version.
6.2 Updating svupdate

Each time you run the svupdate command, it checks whether a new version is available. If an update is available, the command
automatically upgrades to the latest version, and at the same time downloads packages for the current version.
If the element with the Loadable Traffic Identification Package you are upgrading does not have access to the Internet, manually
download the latest svupdate. Complete the procedure outlined in Installation without Internet Access.
6.3 Using the svupdate Menu

To use the svupdate command, connect to an element, and at the command prompt, run svupdate. A menu appears that:
• Displays the available software releases and installed products.
• Lets you perform actions on selected releases, such as installing or downloading the packages.
• Provides intuitive prompts to guide you.
When the menu appears, follow the on-screen prompts to complete the download, installation, or upgrade process.
6.4 Downloading Packages

The svupdate command lets you download packages before an installation or upgrade occurs. To do this, select the product,
or products, you plan to install and select the Download packages for pending changes option from the menu.
The svupdate command downloads the selected products and replaces those that are currently installed. The command also
downloads packages for the currently installed version, which ensures that after the upgrade is complete, previous packages are
still available if you need to downgrade.
Sandvine recommends that you download packages before a maintenance window to ensure that they are available during the
upgrade. If you download packages outside the maintenance window, download them during off-peak hours, as the download
may impact performance on the element.
6.5 Running Pre-Checks

The svupdate command lets you run a series of pre-checks before any installation or upgrade. These pre-checks help to
determine if any issues could occur during an upgrade, or if the element has any known issues that could affect a planned
upgrade.
05-00245-D08
Performing an svupdate
To run a pre-check, select the product(s) you plan to install, and then select the Run pre-checks for pending changes
menu option.
Note:
Sandvine recommends that you run pre-checks during off-peak hours, unless you want to run them during peak hours to
determine issues. If you run the pre-checks outside the maintenance window, there may be a performance impact on the
element.
6.6 Performing an svupdate

When you run the svupdate command, it provides information about your system, such as which packages are installed.
6.6.1 For Elements with Internet Access

To run the svupdate command on an element that has Internet access:
1. Log on to the element as an administrative user.
2. Run the svupdate command.
3. Enter your Sandvine Support user ID and password when prompted.
4. Select a product or terminate the command.
5. If you selected a product in Step 4, select from additional menus as required.
6.6.2 For Elements without Internet Access (FreeBSD only)

If you upgrade an element that does not have access to the Internet, download the files for the upgrade and ensure that you
have:
• A device with access to the Internet.
• A method of transferring a single file from the device with Internet access to the Sandvine element that does not have access.
Complete these steps to install the package:

1. Log in to the Sandvine Customer Support site at http://support.sandvine.com on the device with Internet access.
2. Download the release tarball.
3. Copy the tarball to the Sandvine element.
4. Run the svupdate --release-image <release-tar-ball> command on the Sandvine element to install the package.
05-00245-D08
Resuming Installation after a Reboot
6.7 Resuming Installation after a Reboot

Depending on the product you install, you may need to reboot the element. If a reboot is part of the installation, the svupdate
shell command provides a warning while running the pre-checks. If a reboot occurs during installation, run the update continue
shell command to resume the installation when you log in to the element.
6.8 svupdate Commands

The SSH command line provides these commands for running svupdate.
Command Description
Displays the svupdate menu. See Using the
svupdate <option>
svupdate Menu on page 31 for more information
about the menu.
Installs a release specified in the file.
svupdate --release-image=<file>
Uninstalls a release.
svupdate uninstall <release1> [<release2> ….] <option>
Lists available releases.

svupdate list <platform> <option>
Continues a previously initiated upgrade.

update continue <option>
Updates licenses.
svupdate update-licenses <option>
Each command can include various options as described in Command Options on page 33. These options provide functionalities
such as download-only, pre-check-only, and force install.
6.8.1 Command Options

The options you can include while executing the svupdate command are:
Option Description
--compare-only Only lists packages that change as a result of the specified command.
--config-file <file> Specifies an alternate configuration file to read during startup.
By default, the svupdate command reads /usr/local/sandvine/etc/svupdate.conf
file. If it does not exist, the programmed defaults are used.
--download-only Downloads the packages that the specified command needs and then exits.
--force When upgrading or downgrading a product, reinstalls all corresponding packages, even
if there is no change in their versions.
--no-backups Lets you download selected products only, without backup copies of the currently installed
versions. Do not download backup packages for the installed packages that an upgrade
or downgrade will replace.
05-00245-D08
svupdate Commands
Option Description
--password <password> Uses the specified password to authenticate when downloading Sandvine software.
--precheck-only Runs any applicable pre-upgrade check scripts. These scripts check for problems that
may arise as a result of the transaction. Use this option to detect and resolve such
problems ahead of the maintenance window when the actual upgrade takes place.
--release-file <file URL> Specifies additional release metadata files to process. The svupdate command looks
for a copy of release.xml at the root of the URL specified with the --URL option and
processes it first.
--release-image <release-tar-ball> Installs the software release contained in the specified file. You cannot use this option
with any other options.
--rollback Lets you roll back the currently-ongoing upgrade or downgrade.
You can only use this flag with the continue command; you cannot use it to undo
an upgrade or downgrade that is already completed.
--timeout=<seconds> Specifies a timeout, in seconds, for file downloads. If a download attempt does not make
any progress during the timeout period, the download will fail. The default value is 30
seconds. A timeout period of 0 seconds means that downloads will not time out.
--username <username> Uses the specified username to authenticate when downloading Sandvine software.
--URL <URL> Downloads files and packages from the specified URL. A file called release.xml must
exist at the root of this URL and contain release definitions. You can specify additional
metadata files using the --release-file option.
6.8.2 Examples
These examples illustrate how you can use various options with the svupdate command:
Run this svupdate command... To...

svupdate list List all Sandvine software releases available on the platform.
svupdate list PTS List all PTS releases available on the platform.
svupdate --release-image Install the protocols package 15.06.02 using a release image obtained from
GENERAL_Protocols_15.06.02.tar the Sandvine Customer Support site.
svupdate continue Complete an interrupted upgrade or downgrade, or continue installation after

a reboot.
svupdate --release-file=/d2/release. Complete tarball downgrade.
xml --release-image=/d2/tmp/7.20_mr9.
tar
05-00245-D08
svupdate Commands
05-00245-D08

Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40

Загружено:

Авторское право:

Доступные форматы

Sandvine Policy Traffic Switch

Software Installation and Upgrade

Document Part Number

6.1 About the svupdate Command............................................................................................................................31

1.1 Read This First

1.2 CLI Changes

1.3 Special Circumstances

Virtual Switch Cluster

1.4 Downloading Upgrade Files

1.4.1 Install svupdate and/or Download Files

3. Press q to quit, if you are not prompted to upgrade. Otherwise press y.

4. Select the latest release.

5. Select PTS from the product family listing.

Select Product Family

7. Confirm the release version selected by choosing install.

1.4.2 For Elements without Internet Access

1.4.2.1 Obtaining a Support Account

1.4.2.2 Downloading Files from the Sandvine FTP server

1. Log in to the Sandvine Customer Support website at https://support.sandvine.com.

2. To access the release link for the first time:

b. Enter the password in the FTP Password dialog.

5. Select the Product directory.

7. Select a tarball and md5sum file to download them.

1.4.2.3 Using Tarballs

2. Run the cd /d2/tmp command to navigate to the /d2/tmp location.

7. Install the tarball.

8. Follow the steps on screen.

2.1 Downgrade Notes

2.1.1 Downgrade Compatibility for PTS Hardware

PTS Hardware Earliest Supported Software Release

2.1.2 Downgrading Elements that Use the Second Management Port

Port Redundancy IpAddress AdminStatus OperStatus PrimaryPort

Port SecondaryPort MTU

Port AdminStatus OperStatus

2.1.3 Downgrade Compatibility for SPB Scaling Connections

3.2.1 Verifying System Installed with 6.00 or Later

For this information: Run this CLI command:

All currently installed software. show system version detail

The alarm history. show alarms history limit 1000

The current traffic levels. show interface rate

The current system resource utilization. show system resources

3.2.2 Preparing for Installation

3.2.2.1 Bypassing Traffic

3. Run the commit CLI command to commit the change.

3.2.2.2 Disabling Cluster Ports

4. Run the commit CLI command to commit the change.

2. Press y if prompted to upgrade svupdate.

3. Select PTS on the Family menu.

4. Select the appropriate model of PTS from the Product list.

5. Select the latest release of the software on the Select list.

6. Select 1. Install images on the Operation menu.

7. Monitor the svupdate output for any errors.

9. Verify the system, see Post-installation on page 27.

4.1 CLI Changes

4.2.1 Verifying Pre-6.00 Systems

For this information: Run this CLI command:

The current traffic levels show interface rate

The current system resource utilization show system resources

Run the CLI Command... With Release...

show service spb connections 6.00 and above

2. Press y if prompted to upgrade svupdate.

3. Select PTS on the Family menu.

4. Select the appropriate model of PTS from the Product list.