No index entries found.
Download This Guide
Migration
This section provides information about migrating from earlier SRC software releases to SRC Release 4.7.0.
Policy Changes
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.
 | Note: 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.7 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.7 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.
| Note: With the inclusion of the VTA in the SRC software package that runs on the C-Series Controller, 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.7. |
Reference: TIC 17708 / PR 906376
