Beruflich Dokumente
Kultur Dokumente
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.
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
4 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Sandvine | TOC | 5
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 5
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
6 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Before You Begin
Read This First
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.
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 7
05-00245-D08
Before You Begin
Special Circumstances
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.
6. Select the latest release that you want to upgrade from the release menu.
Select Action
-------------
1. Select PTS 7.20 for install
8 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Before You Begin
Downloading Upgrade Files
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.
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.
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.
6. Select the model and software version of the files you require.
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 9
05-00245-D08
Before You Begin
Downloading Upgrade Files
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.
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.
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.
10 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Before You Begin
Downloading Upgrade Files
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 11
05-00245-D08
Downgrade Instructions
2
Downgrade Instructions
• "Downgrade Notes" on page 13
12 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Downgrade Instructions
Downgrade Notes
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 13
05-00245-D08
Downgrade Instructions
Downgrade Notes
MEMBER INTERFACES
=================
Alternately, run the show alarms CLI command and look for an alarm such as:
43 Network interface down: Control mgmt1
14 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Downgrade Instructions
Downgrade Notes
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 15
05-00245-D08
Upgrade from 6.00 or later
3
Upgrade from 6.00 or later
• "Pre-requisites" on page 17
• "Pre-Installation" on page 17
• "Installation" on page 19
16 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Upgrade from 6.00 or later
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.
2. Collect and save the information retrieved using these CLI commands:
The model number of the device you are upgrading. show system information
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.
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 17
05-00245-D08
Upgrade from 6.00 or later
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.
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.
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.
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.
18 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Upgrade from 6.00 or later
Installation
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.
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.
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 19
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
20 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Upgrading from Releases Earlier than 6.00
CLI Changes
4.2 Pre-Installation
These sections outline tasks to perform on the element being upgraded prior to installation.
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:
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
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.
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 21
05-00245-D08
Upgrading from Releases Earlier than 6.00
Installation
5. Verify that the PTS is connected to an SPB using the appropriate CLI command.
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.
22 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Upgrading from Releases Earlier than 6.00
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.
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.
cd /usr/local/sandvine/etc/certs
mv service.crt service.crt.bk
/usr/local/sandvine/scripts/ssl_certificate.sh
svcli
PTS> restart service ptsd
PTS> restart service policy-engine-service
PTS> restart service service-discovery
2. Perform an svreload.
3. Note the changes you made so you can re-enable the functionality during the post-install process.
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 23
05-00245-D08
Upgrading from Releases Earlier than 6.00
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
3. Perform an svreload.
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.
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>
3. Perform an svreload.
4. Note down the changes you made so you can re-enable the functionality during the post-installation process.
24 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Upgrading from Releases Earlier than 6.00
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 (#).
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.
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.
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 25
05-00245-D08
Post-installation
5
Post-installation
• "Post-installation" on page 27
26 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
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.
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.
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.
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 27
05-00245-D08
Post-installation
Post-installation
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.
28 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Post-installation
Post-installation
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 29
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.
30 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Using the svupdate Command to Upgrade, downgrade or Install the Packages
About the svupdate Command
When the menu appears, follow the on-screen prompts to complete the download, installation, or upgrade process.
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 31
05-00245-D08
Using the svupdate Command to Upgrade, downgrade or Install the Packages
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.
4. Run the svupdate --release-image <release-tar-ball> command on the Sandvine element to install the package.
32 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Using the svupdate Command to Upgrade, downgrade or Install the Packages
Resuming Installation after a Reboot
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>
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.
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.
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 33
05-00245-D08
Using the svupdate Command to Upgrade, downgrade or Install the Packages
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:
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.
34 Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40
05-00245-D08
Using the svupdate Command to Upgrade, downgrade or Install the Packages
svupdate Commands
Sandvine Policy Traffic Switch Software Installation and Upgrade Guide, Release 7.40 35
05-00245-D08