Supported Upgrade Paths
You can upgrade directly from any of the following versions:
•
5.0r2
•
5.0r1
•
4.1r4
Beginning with IDP OS Release 5.0, IDP Series does not support bridge, proxy-arp, or
router mode. Before upgrading to IDP OS 5.1, you must redeploy the IDP Series device in
transparent or sniffer mode.
NOTE:
The upgrade paths assume your current IDP Series device has been
in use and the device had been added to NSM. You might encounter
unexpected behavior during the upgrade if you are upgrading from a newly
reimaged, undeployed IDP OS 4.2 or 4.1 device (such as a 2009 factory image
of the IDP OS). In these cases, we recommend you add the IDP device to NSM
and import the device configuration into NSM prior to performing the upgrade.
Doing so will avoid the file permissions issue described in KB 15071.
Table 2 on page 5 describes the changes to files and directories you will notice when
you upgrade.
Table 2: Changes to Files and Directories
Files and Directories
Upgrade Path
No changes to attend to before upgrade.
From 5.0r2
Before you upgrade, take note of the following changes and recommended actions:
•
IDP 5.1r1 stores packet logs in numbered subdirectories of
/usr/idp/device/var/pktlogs/
. To implement
this change, your existing
/usr/idp/device/var/pktlogs/
directory will be overwritten. If you have
been using the option to maintain packet data locally and send to NSM on demand, copy any packet
logs you want saved from
/usr/idp/device/var/pktlogs/
to a remote location before you upgrade.
Previously collected packet capture logs will not be available to NSM. This action is not required if
you have been using the option to always include packet data when NSM sends the event log.
•
Your custom settings in the
/usr/idp/device/bin/user_funcs
file are preserved when you upgrade.
No action is required.
From 5.0r1
5
Copyright © 2011, Juniper Networks, Inc.
Supported Upgrade Paths
