Juniper STRM 2008.2R2 - UPGRADING TO STRM 2008.2R2 REV 2 Troubleshooting

Download Troubleshooting of Juniper STRM 2008.2R2 - UPGRADING TO STRM 2008.2R2 REV 2 Other for Free or View it Online on All-Guides.com.

Juniper STRM 2008.2R2 - UPGRADING TO STRM 2008.2R2 REV 2 Troubleshooting - Page 1
1
Juniper STRM 2008.2R2 - UPGRADING TO STRM 2008.2R2 REV 2 Troubleshooting - Page 2
2
Juniper STRM 2008.2R2 - UPGRADING TO STRM 2008.2R2 REV 2 Troubleshooting - Page 3
3
Juniper STRM 2008.2R2 - UPGRADING TO STRM 2008.2R2 REV 2 Troubleshooting - Page 4
4
Juniper STRM 2008.2R2 - UPGRADING TO STRM 2008.2R2 REV 2 Troubleshooting - Page 5
5
Before You Begin 1
JUNIPER NETWORKS STRM
U
PGRADING TO STRM 2008.2R2
RELEASE 2008.2R2
OCTOBER 2008--REVISION 2
This document provides information for upgrading to STRM 2008.2 including:
Before You Begin
Upgrading to STRM 2008.2r2
Troubleshooting Your Upgrade
Clearing the Cache
You must upgrade the systems in your deployment in the following order:
Console
Caution: The upgrade process must be complete on your STRM Console and you
must be able to access the STRM user interface on your system hosting the
Console before you upgrade any other systems in your deployment.
Remote Event Processors
Remote Event Collectors
Classification Engines
Flow Processors
Flow Collectors
Before You Begin Before you upgrade to STRM 2008.2, note the following:
To upgrade to STRM 2008.2r2, you must be running STRM 2008.2r1. If you are
not running STRM 2008.2r1, contact Juniper Networks Customer Support for
assistance with your upgrade.
Make sure you log out of STRM and any instance of the STRM Administration
Console.
Make sure all browsers are closed during the upgrade process.
Make sure you upgrade all systems in your deployment hosting VIS
components. If you do not upgrade these systems, error messages may appear
in the log files until the affected systems are upgraded.
Custom configuration to the crontab is not maintained after the upgrade. The
default crontab configuration is applied by the upgrade process. We
recommend that you backup your crontab configuration prior to the upgrade
using the
crontab –l > /tmp/crontab_backup command. However, after
the upgrade, do not replace the default crontab configuration with the backup