Upgrading from 6.1.17 - 7.1.0
The following steps describe upgrading from Redcell versions 6.1.17 to 7.1.0. Notice that these are suggested steps that may not comprehensively cover your particular system needs; modify these steps to accommodate your system’s setup. See Manual Migration for an abbreviated list of what appears below.
Best practice is to perform these steps in a lab, then modify them to suit your system’s needs, before upgrading a production system.
1. Make any changes to the hardware needed to accommodate your system. See Hardware, Operating Systems and Ports Used for suggestions.
2. On your 6.1.17 installation, before upgrading:
a. Export the following custom objects to files on disk:
–All custom Service Templates
–All custom Adaptive CLI Scripts
b. Create and run a report listing any custom Adaptive CLI scripts installed currently that have associated Negate Command Adaptive CLIs. Include the name of the Negate Command Adaptive CLIs as a column of the report to list the existing Adaptive CLIs.
c. Note or take screen shots of the following that must be manually recreated after upgrading:
–Existing User Records and Associated User Group Membership
–Existing Permissions for each User Group
–Any configured, enabled Scheduled Items
–Any Group Operations
–Groups of Adaptive CLIs (for batch execution)
–File Backup Actions
–Redcell Change Management Actions
3. Do a full backup of your database. (See MySQL Backup / Restore or refer to your database’s backup instructions)
4. Optional: Back up the host to which you are installing.
5. Optional (but recommended): stop all running Redcell Synergy processes.
6. Perform the 7.1.0 Upgrade Installation (see Installation for more about this). You must run the loaddb -s command line as part of this installation.
7. You may need to look through the portal properties to see the web server is on the correct address. It defaults to the application server’s IP address, which would be incorrect if web server is not on that machine. Correct
8. Manually recreate the following in 7.1.0 using its Web Portal:
a. Recreate previous User Groups named exactly the same as they were in 6.1.17.
As long as you use the same name for new User Groups (Roles) created in the upgrade as existed in 6.1.17, the previously assigned functional permissions associated with each Group are automatically linked in the upgrade. No need to reassign the functional permissions for each group.
b. Recreate previous Users with proper assigned User Group Membership (Roles) and Passwords in the Web Portal.
To validate this, test, log in with each of the configured User Logins to ensure they have the previously assigned permissions.
After upgrading, Users may not initially appear associated to their roles, but you can work around this apparent failure by clicking Update Associations. This is in the Roles portion of the Control Panel. Click Actions > Assign Members, then click the Update Associations button on the following screen. Alternatively, you can go to the Server Administration portion of the Control Panel and click Execute to Reindex all search indexes.
c. Recreate File Backup actions against defined group(s) of target devices.
d. Regroup and test ACLI Actions that were previously grouped together as a Task Groups in Redcell 6.1.17.
The task group feature was not supported in Redcell 6.1.17, but RC 7.1 lets you group execution of tasks in sequence.
e. Recreate Scheduled Items, taking into account any new actions configured for items above.
f. Review previously Scheduled Items that appear in the upgraded installation. Recreate any missing Scheduled items to ensure proper visibility and execution of the associated scheduled Redcell activity.
9. Review / augment and retest Adaptive CLIs that had negate commands previously tied to them (both positive and negative/error use cases). Ensure these require no negate scripts.
Negate scripts are typically not used/needed for Juniper JUNOS devices because of the JunOS's transaction control and semantics.
10. Test any custom Adaptive CLI Scripts migrated from RC 6.1.17 on your updated installation.
11. Test particular applications like Service Center's functionality for any previously implemented services. For example:
a. Test service provisioning functions (Create, Modify, Deploy, Undeploy, Delete, Service Discovery, Spoof Deploy) using pre-existing service templates.
b. Test previously created Generic CLI Service templates for CLI configuration.
c. Spot check testing of Service Discovery for MPLS VPN services.
d. Test the Approval Workflow (User/Group Assignments) to these were set up properly in the upgrade process.
12. Create a Production Upgrade Plan to follow once Lab upgrade testing is successfully completed.
When upgrading from an earlier version 6 Redcell in a Windows environment, you may have to handle a port issue. In early version 6 Redcell Synergy, the default application server port was 80; later the default was changed to 8089. During web portal installation by itself, the installer asks for the application server port. This screen defaults to 8089. The installing user must verify that their original application server installation is running on port 8089; and if not enter the appropriate port number your previous installation uses.
You can also change this after installing by updating the portal-ext.properties file with a text editor.