This section provides information about migrating from earlier SRC software releases to SRC Release 4.12.0.
Starting with SRC Release 4.2.0, an action configured for a policy rule no longer requires a name to identify the action. Old configurations with a name are accepted.
You cannot have multiple instances of the same action configured for one rule.
Migrating VTAs Running on Solaris to SRC VTA Running on the C Series Controller
If you have Solaris-based VTAs running and want to migrate to the SRC 4.12 VTA, which runs on the C Series Controller, contact Juniper Networks Professional Services.
The basic procedure to migrate from Solaris-based VTAs to a VTA running on SRC 4.12 C Series Controllers is:
- Copy your VTA configuration data into the Juniper Networks database (if necessary).
- Execute a shell script to copy the VTA configuration to a new version compatible with the SRC VTA. This script is specific to your environment. Please contact Juniper Networks Professional Services for assistance.
- Configure and start the SRC VTA.
- Shut down the Solaris VTA.
- Modify the SAE EJB plug-ins to send their events to the SRC VTA.
To run both Solaris-based VTAs and SRC-based VTAs, the Solaris-based VTAs must be running a minimum of SRC Release 4.1 software.
With the inclusion of the VTA in the SRC software package that runs on the C Series Controller and acts as VMs, there is no longer a separate application library package. If you wish to continue running your VTA on a Solaris host, use the SRC 4.1 Application Library package. The SRC 4.1 VTA is compatible with SRC 4.10.
Migrating the C Series Controller to Software Release 4.12.0
You cannot upgrade the C Series Controller software to Release 4.12.0 from a release earlier than 4.8.0 by using the request system upgrade url url command, because a different operating system (CentOS 6.5) is being used from SRC 4.8.0. You must reimage the controller by using the USB storage device. For more information about using the USB storage device to reimage the controller, see Recovering or Installing System Software on a C Series Controller by Using the USB Storage Device Supplied by Juniper Networks.
The basic procedure to migrate the C Series Controller from release earlier than 4.8.0 to Release 4.12.0 is:
- Back up the configuration to the USB storage device or
to a remote server by using the save and file copy commands.
We recommend that you back up the configuration to the remote server.
- Create an installation medium by using the read/write USB storage device.
- Boot the controller from the USB storage device and install the software.
- Load the backup configuration by using the load command.
You can load backup configuration from the XML, text, or LDAP LDIF file. Before loading backup configuration from XML or text file, you must perform the following steps in the backup configuration to avoid errors:
For all router drivers, set the minimum thread pool size to 100.
For all SRC components, set the maximum file size to 2,000,000.
Define network device type and SAE connection.
Delete logrotate configurations.
Delete the external interface configurations.
Configure the new SAE heap percentage options (java-min-heap-size-percentage, java-heap-size-percentage, java-min-new-size-percentage, and java-new-size-percentage) based on the values set to the existing heap options (java-min-heap-size, java-heap-size, java-min-new-size, and java-new-size).
Delete the JPS component and configurations related to JPS.
If the redirect server is set to SSLv2 for HTTPS, change it to a supported protocol (SSLv23, SSLv3, TLSv1, TLSv1.1, or TLSv1.2).