Upgrading to Cisco Prime Network 3.8

Transcription

1 CHAPTER 12 Upgrading to Cisco Prime Network 3.8 The following topics provide information about upgrading from a Cisco Active Network Abstraction 3.7.x release to Cisco Prime Network 3.8. This chapter includes: Overview of Upgrading to Cisco Prime Network 3.8, page 12-1 Before You Begin, page 12-6 Upgrading From Cisco ANA 3.6.x to Cisco ANA 3.7, page 12-9 Upgrading from Cisco ANA 3.7.x to Cisco Prime Network 3.8, page 12-9 Rolling Back from Cisco Prime Network 3.8, page Postupgrade Tasks, page Integration Activities, page Table 12-1 Variables Used in This Chapter Before 3.8 After 3.8 <Product name> ana prime network <username> ana user network user <user permissions> ana user: anagroup network user: network group <upgrade directory> ANA_upgrade Prime_Network_upgrade Overview of Upgrading to Cisco Prime Network 3.8 Cisco Prime Network 3.8 includes an automatic upgrade procedure that installs Cisco Prime Network 3.8 on top of the existing Cisco Active Network Abstraction (Cisco ANA) 3.7.x installation. The upgrade procedure backs up the existing user directory and then adds any new Cisco Prime Network 3.8 libraries, files, and code to your existing Cisco ANA 3.7.x installation. Any changes to the database are made automatically as part of the upgrade. Customizations and user-defined information remain intact and available in Cisco Prime Network 3.8 after upgrading. The amount of time required to upgrade Cisco Prime Network depends on your deployment size and system performance. During this time, the system will be down. Contact your Cisco account representative for an estimated upgrade duration. 12-1

2 Overview of Upgrading to Cisco Prime Network 3.8 Chapter 12 Upgrading to Cisco Prime Network 3.8 Note Cisco Prime Network will use your tar executable to back up the Cisco Prime Network files. If your tar version does not support the -E flag, the Cisco Prime Network upgrade will fail before changing the Cisco Prime Network files or database. Verify that your the tar executable supports the -E flag. The tar executable must be in the root user path environment variable, and not under the ANA home directory. Table 12-2 shows the components affected by the Cisco Prime Network upgrade, and whether those components are upgraded automatically or manually. Table 12-2 Components Affected by the Cisco Prime Network Upgrade Component VNE AVMs Support for third-party VNEs Database: schema changes Database: data preservation Description Avm*.xml files with managed element definitions Upgraded Automatically? Yes Comments All existing VNE avm*.xml files are available after upgrading. Before upgrading, contact your Cisco account representative for sizing and AVM planning changes. Support for non-cisco VNEs No Before upgrading, contact your Cisco account representative to identify which third-party VNE drivers your upgrade requires, and to have these third-party VNE drivers re-enabled. If you enabled third-party VNEs in Cisco ANA 3.7.x, those VNEs remain available after upgrading to Cisco Prime Network 3.8. Add, change, or remove Cisco ANA tables to meet the Cisco Prime Network 3.8 schema definition Migrate the old data representation to the Cisco Prime Network 3.8 representation, where applicable Yes Yes All tickets and events are available after upgrading. If you are upgrading from Cisco ANA 3.6.x, see the section Managing 3.6.x Events in the Cisco Active Network Abstraction 3.7 Installation Guide to understand the event migration. All other data (such as maps, users, and so on) is preserved and migrated. 12-2

3 Chapter 12 Upgrading to Cisco Prime Network 3.8 Overview of Upgrading to Cisco Prime Network 3.8 Table 12-2 Components Affected by the Cisco Prime Network Upgrade (continued) Upgraded Component Description Automatically? Comments Database: general No Before upgrading, manually apply the Cisco Prime Network 3.8 database configurations and recommendations. See Chapter 4, Creating and Configuring an Oracle Database. The Cisco Prime Network upgrade procedure does not support a change in the database deployment scenario. In other words, you cannot upgrade from a colocated database on the gateway server to a remote database, or from a customer-provided database to an embedded database. Licenses Yes All users, scopes, and licenses are maintained. Northbound API: IMO and BQL Northbound API: trap forwarding and SNMP Customizations: Soft properties Changes to information model objects (IMOs) Out-of-box support for the SNMP trap forwarding mechanism Soft properties remain backward compatible and are available in Cisco Prime Network 3.8 after upgrading. No Yes Note Yes If Cisco ANA 3.7.x was operating without a valid license, you must obtain and install a license for Cisco Prime Network 3.8 within 120 days of the upgrade. See the Cisco Prime Network 3.8 Administrator Guide for information on licensing. Some of the Cisco ANA 3.7.x IMOs were changed to support new inventory and management features. See the Cisco Prime Network 3.8 Release Notes for details. The Cisco-EPM-NOTIFICATION-MIB structure includes a running index in the object identifier (OID) suffix, instead of a constant number as in previous releases. The cenalarmtype content has also changed in Cisco Prime Network 3.8. For details, see Using Event Notification Service in the Cisco Prime Network 3.8 Integration Developer Guide. If you are upgrading from Cisco ANA 3.6.x and you deployed the Cisco ANA2Netcool (AVM80) solution to integrate with CIC or IBM Tivoli (Netcool), contact your Cisco account representative for support. 12-3

4 Overview of Upgrading to Cisco Prime Network 3.8 Chapter 12 Upgrading to Cisco Prime Network 3.8 Table 12-2 Components Affected by the Cisco Prime Network Upgrade (continued) Component Customizations: Command Builder Built-in Command Builder scripts Customizations: workflows Customizations: Drools rules Customizations: business objects Customizations: crontabs Customizations: external launch Customizations: Message of the Day Description User-defined commands Yes User-defined Command Builder scripts are available after upgrading to Cisco Prime Network 3.8. Cisco Prime Network built-in activation scripts Yes The upgrade procedure updates the built-in changes and removes scripts that are no longer part of the product. See Command Builder Scripts, page to understand which commands require installation after the upgrade. Yes The workflow templates are backward compatible and are available after the upgrade is complete. Yes The Post.drl rule is available after upgrading. The alarm model introduced in Cisco ANA 3.7 requires manual migration of Drools rules. The pre.drl rules are not supported in Cisco ANA 3.7.x. Contact your Cisco account representative for recommendations. See also Drools Rules Migration, page The Drools plugin is disabled by default. To enable the Drools plugin manually, see the Cisco Prime Network 3.7 Customization User Guide. Yes Review IMO changes to verify that the OID associated with the business object did not change. Cisco Prime Network crontabs are configured as part of the installation Upgraded Automatically? Yes Comments If you have user-defined cron jobs, place them in network-home/local/cron/crontab.user.list. The upgrade will automatically add the user-defined cron jobs. User-defined cron jobs that are not placed in this directory will be removed. External launch configuration Yes Review IMO changes to verify that the OID associated with the launch command did not change. Message of the Day configuration No The upgrade process overrides the customized Message of the Day and restores the default message. After upgrading to Cisco Prime Network 3.8, use Cisco Prime Network Manage to re-enter your customized Message of the Day content. 12-4

5 Chapter 12 Upgrading to Cisco Prime Network 3.8 Overview of Upgrading to Cisco Prime Network 3.8 Table 12-2 Components Affected by the Cisco Prime Network Upgrade (continued) Upgraded Component Description Automatically? Comments Registry Yes New Cisco Prime Network 3.8 registry files are available automatically after the upgrade. Customizable registry files, including avm+.xml and site*, are available and upgraded automatically. Review any customized registry configurations in site.xml and avm*.xml to understand whether they are relevant to Cisco Prime Network 3.8. Contact your Cisco account representative, if necessary. network-user_admin user Security: SSH and SSL keys Cisco Prime Network persistency files User with database administrator permissions who can run maintenance tasks such as gathering statistics on the other Cisco Prime Network database schemas. Cisco Prime Network SSL keystore and truststore keys, SSH keys, and registry encryption keys Inventory, events, and link persistency data Yes Yes Yes Except for VNE and event persistency files, other Cisco ANA 3.7.x persistency files are available after the upgrade. VNE and event persistency files are not preserved. GUI client No If you are upgrading from Cisco ANA 3.6.x, you must install the Cisco ANA 3.7.x client. After upgrading or rolling back to an earlier release, delete the client cache from: $ANA_Client_Installation_dir/cache/gateway- IP-address. Cisco ANA NetworkVision New name Yes Cisco ANA NetworkVision becomes Cisco Prime Network Vision. Cisco ANA Manage New name Yes Cisco ANA Manage becomes Cisco Prime Network Administration. Cisco ANA Event Manager Network Service Activation (NSA) New name Yes Cisco ANA Events Manager becomes Cisco Prime Network Events. No Cisco ANA NSA becomes Cisco Prime Network Activation. It is installed or upgraded automatically. 12-5

6 Before You Begin Chapter 12 Upgrading to Cisco Prime Network 3.8 Table 12-2 Components Affected by the Cisco Prime Network Upgrade (continued) Component Configuration and Image Management High availability (HA) configuration Description Change and Configuration Management provides tools that allow you to manage the software and device configuration changes that are made to devices in your network Cisco Prime Network upgrades for either the Veritas gateway HA or the Red Hat Cluster Suite/Oracle Active Data Guard gateway HA. Upgraded Automatically? Yes Comments Configuration and Image Management is changed to Change and Configuration Management. It is installed or upgraded automatically as part of the upgrade. For details, see Installing the Cisco Prime Network Gateway, page 7-4. No For Veritas gateway HA, review guidelines in Upgrading to Cisco Prime Network 3.8 in a Veritas Gateway HA Environment, page RHCS/ADG gateway HA is upgraded using the upgrade procedure in this chapter. However, you must move the ana and Oracle services to maintenance mode before you run the upgrade, then move them back to normal mode after it. Before You Begin Note Prior to the upgrade of Cisco Prime Network, or the upgrade of a VNE driver, make sure to delete the Drivers content from $ANAHOME/main/drivers on all of the ANA units. Do not delete any content from the ANA Gateway directory. To delete the Drivers content, remove all jar files, under ~/Main/drivers by running the following command as ana-user: rm -rf *.jar Before upgrading to Cisco Prime Network 3.8, complete the following steps: Step 1 Step 2 Step 3 Step 4 See Hardware and Software Requirements, page 1-1 before you carry out any of the procedures in this chapter. Free up all the designated ports. For a list of ports that must be available, see Cisco Prime Network Server, HTTP, TCP, and UDP Ports, page Understand the upgrade process and identify areas in your configuration that might require customization or special integration. See the following guides for reference: Cisco Prime Network 3.8 Integration Developer Guide Cisco Prime Network 3.8 Customization User Guide Back up your data. 12-6

7 Chapter 12 Upgrading to Cisco Prime Network 3.8 Before You Begin Step 5 Step 6 Step 7 Step 8 Manually back up the database and any specific files that are not part of ANA, yet reside in your Cisco Prime Network system; for example, user-defined crontab jobs. A database backup is required in case you decide to roll back to Cisco ANA or rerun the upgrade. For internal database backup procedures, see the Cisco Prime Network 3.8 Administrator Guide. For non-embedded database backup, see the appropriate Oracle documentation. Verify that you have unzip version 5.5 or higher. Verify that gateways and units with Red Hat installed have rsync version x86_64. For gateways and units with older rsync versions, upgrade rsync by using the attached RPM and entering the following command as the root user: rpm -Uhv rsync x86_64.rpm Verify that the database is up and Oracle and the Oracle listener are running. Reconfigure your database according to the instructions in Chapter 4, Creating and Configuring an Oracle Database. Note Cisco Prime Network 3.8 requires the Oracle JVM and partitioning options. For the database storage sizing guidelines, contact your Cisco account representative to obtain the Cisco Prime Network Capacity Planning Guide. Verify that the database has at least 8 GB of RAM available, which is the minimum requirement. Step 9 Step 10 Step 11 Step 12 Step 13 If you are upgrading from Cisco ANA3.6.x, contact your Cisco account representative to maintain support for third-party VNEs. See Maintaining Support for Third-Party VNEs, page If you installed SBC, IPoDWDM, or legacy scripts in an earlier Cisco ANA release, uninstall the scripts manually before upgrading to Cisco Prime Network 3.8. If you are upgrading from Cisco ANA and have the RHCS/ADG Local HA installed, place the ana and oracle_db services in maintenance mode: clusvcadm -Z ana clusvcadm -Z oracle_db If your ANA network contains Linux servers, Port 161 must be redirected to Port To do this, as the root user, enter: iptables -t nat -D PREROUTING -p udp --dport 161 -j REDIRECT --to-port 1161 service iptables save If you are upgrading from Cisco ANA 3.7.x to Cisco Prime Network 3.8, you must create the BOS user manually: a. Log in as the root user. b. Enter the following command: echo "bos:x:1310:1310:bos Admin:$ANAHOME/Main/bosconfig/bos_shell_scripts:$ANAHOME/Main/bosconfig/bos_shell_scri pts/run.csh" >> /etc/passwd Note $ANAHOME is the environment variable for the Cisco Prime Network home directory. 12-7

8 Before You Begin Chapter 12 Upgrading to Cisco Prime Network 3.8 c. Enter: echo "bos:qhn.ui6wm.io2:::::::" >> /etc/shadow pwconv Step 14 If you have a new installation of Cisco ANA installed, continue with Step 15. If you upgraded to from an earlier version, or if you have an earlier version installed, complete the following steps to enable the ana-user_admin user to run maintenance tasks such as gathering statistics on the other ANA database schemas: a. As the Oracle UNIX user, use SQL*Plus to log into user sys as sysdba. b. Enter one of the following commands: If the ana-user_admin user does not exist, enter: SQL> grant execute on dbms_lock to system with grant option; If the ana-user_admin user already exists, enter: SQL> grant execute on dbms_lock to network-user_admin with grant option; Step 15 c. Verify your database contains the temporary TEMP tablespace which is required by the new admin database user. If this tablespace doesn't exist, you have two options: Create this TEMP tablespace. Manually add the new admin database user as described in Creating Cisco Prime Network 3.8 Database Schemas Manually, page While the ANA is up and running, enter the following commands as the ana-user to verify that the databasepath and databaseuser entries are set in the avm66.xml file: cat $ANAHOME/Main/registry/ConfigurationFiles/ /avm66.xml grep databaseuser cat $ANAHOME/Main/registry/ConfigurationFiles/ /avm66.xml grep databasepath If the first query returns empty output, enter the following commands to set the databaseuser in avm66.xml: cd ~/Main./runRegTool.sh -gs localhost set avm66/services/workflow/engine/databaseuser ""./runregtool.sh -gs localhost get workflowavm/services/workflow/engine/databaseuser./runregtool.sh -gs localhost set avm66/services/workflow/engine/databaseuser result-from-previous-command If the second query returns empty output, enter the following commands to set the databasepath in avm66.xml: cd ~/Main./runRegTool.sh -gs localhost set avm66/services/workflow/engine/databasepath ""./runregtool.sh -gs localhost get workflowavm/services/workflow/engine/databasepath./runregtool.sh -gs localhost set avm66/services/workflow/engine/databasepath result-from-previous-command Step 16 Each new release expands its technology coverage and support, which might affect your VNE size and distribution to AVMs. Contact your Cisco account representative to obtain the Capacity Planning Guide, which provides detailed guidelines as you review your deployment sizing and your VNE-to-AVM assignments. 12-8

9 Chapter 12 Upgrading to Cisco Prime Network 3.8 Upgrading From Cisco ANA 3.6.x to Cisco ANA 3.7 Upgrading From Cisco ANA 3.6.x to Cisco ANA 3.7 If you currently have Cisco ANA 3.7, 3.7.1, or installed, go to Upgrading from Cisco ANA 3.7.x to Cisco Prime Network 3.8, page If you have Cisco ANA 3.6.x installed, you must upgrade to at least Cisco ANA 3.7 before you upgrade to Cisco Prime Network 3.8. The Cisco Prime Network 3.8 Disk 2: Upgrade Install DVD includes the complete procedure to upgrade from Cisco ANA 3.6.x to Cisco ANA 3.8. Caution Do not apply any service patches during any phase of the upgrade to Cisco Prime Network 3.8. To complete the Cisco ANA 3.6.x prerequisites: Step 1 Step 2 Step 3 Step 4 Complete one of the following: If you are currently running Cisco ANA or earlier, see Chapter 10, section Upgrading to Cisco ANA in the Cisco Active Network Abstraction Installation Guide. If you are currently running Cisco ANA 3.6.7, see Chapter 10, section Upgrading to Cisco ANA 3.7 in the Cisco Active Network Abstraction Installation Guide. Complete the procedures provided in these chapters on the gateway and on all units. After the upgrade to Cisco ANA 3.7 completes successfully, reset the ANA user password in order to connect to the UNIX workstation. (If you already reset the ANA user password during the 3.7 migration, you do not need to repeat this step.) If your environment contains a standby unit, complete the following steps: a. Remove the standby unit from the gateway. b. Uninstall the existing version from the standby unit. c. After the upgrade is complete, install the unit with Cisco ANA 3.7. (Install the final version on the standby unit and connect it to the gateway at the end of the upgrade process.) d. Attach the unit to the gateway as a standby unit after the gateway and other units have been upgraded. For information on configuring standby units, see the Cisco Active Network Abstraction 3.7 Administrator Guide. After completing the Cisco ANA 3.6.x to Cisco ANA 3.7 upgrades, do not restart the system or apply any postmigration steps. Continue directly to Upgrading from Cisco ANA 3.7.x to Cisco Prime Network 3.8, page Upgrading from Cisco ANA 3.7.x to Cisco Prime Network 3.8 Complete the following steps on the gateway to upgrade from one of the following Cisco ANA versions to Cisco Prime Network 3.8: Cisco ANA 3.7 to Cisco Prime Network 3.8 Cisco ANA to Cisco Prime Network 3.8 Cisco ANA to Cisco Prime Network 3.8 Cisco ANA to Cisco Prime Network

10 Upgrading from Cisco ANA 3.7.x to Cisco Prime Network 3.8 Chapter 12 Upgrading to Cisco Prime Network 3.8 Caution Do not apply any service patches during any phase of the upgrade to Cisco Prime Network 3.8. Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Before starting the upgrade, verify that you have the following installation DVDs: Disk 1: New Install Disk 2: Upgrade Install If you are upgrading an RHCS/ADG gateway HA configuration, verify that the ana and oracle_db services were placed in maintenance mode. If not, enter the following commands: clusvcadm -Z ana clusvcadm -Z oracle_db Close all database sessions (such as TOAD, SQL, and so on). Verify that the gateway and units are powered up and connected, that is, you can open an SSH session between gateway and all units. Verify that Oracle and the Oracle listener are running. Stop all VNEs, if they are running. Back up your database. A database backup is required in case you decide to roll back to an earlier version or rerun the upgrade. Insert Disk 2: Upgrade Install into the DVD drive. Open a Telnet or SSH session to the gateway and log in as the ana-user. Switch to the DVD Upgrade directory: cd /cdrom/cdrom0/upgrade Copy the ANA_upgrade directory to any directory except the home directory and subdirectories. The directory where you copy the ANA_upgrade directory must have ana-user:ana-group permission. Caution Step 12 Step 13 Step 14 Step 15 Step 16 Step 17 Do not copy the ANA_upgrade directory to the the home directory or subdirectories. If you are upgrading from Cisco ANA 3.7, the upgrade script requires a database system password to create the new network-user_admin or XMP database schema on top of Cisco ANA 3.7. To create the database schema manually, see Creating Cisco Prime Network 3.8 Database Schemas Manually, page Remove Disk 2 Install Upgrade and install Disk 1 New Install. (This DVD contains the ivne-drivers.tar.) Create a temporary directory and copy the ivne-drivers.tar into it. The directory must have ana-user:ana-group permission. If you are upgrading from Cisco ANA or Cisco ANA 3.7.3, extract the contents of the ivne-driver.tar into this directory. If you are upgrading from 3.7 or 3.7.1, continue with Step 16. As the ana user, enter the following command to change to the ANA_upgrade directory: cd ANA_upgrade; As the ana user, enter one of the following commands to start the upgrade: In a non-veritas gateway HA configuration, enter: perl./upgrade.pl -i 12-10

11 Chapter 12 Upgrading to Cisco Prime Network 3.8 Upgrading from Cisco ANA 3.7.x to Cisco Prime Network 3.8 In a Veritas gateway HA configuration, enter the following commands. Primary server: perl./upgrade.pl -i -ha Secondary server: perl./upgrade.pl -i -ha_redundant The script uses the following flags: Table 12-3 Upgrade Flags -p Indicates a patch upgrade. -i Indicates a major version upgrade. -nobackup Skips the home directory backup (for rollback purposes). Note If the -nobackup flag is used, the upgrade procedure does not back up the existing user directory. -ha or -ha_redundant Upgrades an HA setup. For details, see Upgrading to Cisco Prime Network 3.8 in a Veritas Gateway HA Environment, page The flags have the following usage: perl upgrade.pl state [-nobackup, -ha -ha_redundant] Step 18 where: state Enter -i for a major version upgrade. Enter -p for patch upgrade. -nobackup Use this option to skip the default backup. -ha -ha_redundant Use this option to upgrade an HA setup. The following output is generated: ana37@csi-bvc [/export/home/ana_upgrade]% perl./upgrade.pl -i + Preparing for Prime Network Upgrade - Writing log to /export/home/ana37/main/upgrade log Step 19 Verify you meet all the requirements provided in Before You Begin, page Before continuing, please make sure that all the upgrade prerequisites have been met. Prerequisites are listed in: Step 20 When asked whether you completed a recent database backup, enter Y or N, as appropriate: Do you have an updated backup of the database? (Y,N) [default Y] If you enter N, the upgrade process will stop and will ask you to backup the database. If you enter Y, the following output appears: - Checking connectivity to the database [OK] - Checking connectivity to the units [OK] - Verifying free space under /export/home/ana37 [OK] - Reading version information [OK] - Stopping Prime Network on gateway & units - Stopping Prime Network processes on gateway & units 12-11

12 Upgrading from Cisco ANA 3.7.x to Cisco Prime Network 3.8 Chapter 12 Upgrading to Cisco Prime Network 3.8 Step 21 At the prompt for a directory to back up your current home directory, specify a directory with at least 500 MB of free space. Verify that the backup directory is available for the network-user: - Please enter the destination location for the backup tar file that has at least Kb of free space: directory-name - Backing up current installation to: directory-name_time-stamp.tar.gz [OK] The prompt for OS root user is dispalyed only for the HA setup (Veritas/Red Hat) - Enter the password for the OS root user: Note The following printout includes all upgrade steps from 3.7 to Upgrading to Updating ANA directories & files - Updating Golden Source directories - Updating 3rd party jars - Removing patches - Updating ANA client components - Updating ANA plugins [OK] - Running the ANA upgrade procedures - Executing com/cisco/nm/ana/dev/upgrade/v371/vpls/drop_vpls.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v371/vpls/vpls.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v371/vlan/carriere.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v371/evc/evc.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v371/pseudowire/pw.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v371/vpn/vpn.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v371/fault/fault.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v371/update_reportdata.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v371/update_workflow_task_result_attributes.sql.. - Executing CarrierEDeleteReconcile.. - Executing TFSMigrationHook.. - Executing Tftp83UpdateHookForBsm.. - Executing Reports84UpdateHook.. - Executing GWSwitchPowerHook.. - Executing UnitSwitch512MHeap.. - Executing DM77UpdateHookForBsm.. - Executing ExtractAndInstallXmpNccmMigrationHook.. a. At the prompt to install the optional Configuration and Image Management component, enter the necessary details, as appropriate: - ANA is bundled with Configuration and Image Management runtime. You can install the XMP platform and these components now, or later as a stand-alone operation. In case you want to install it now, you might be asked to provide some missing information - Would you like to install Configuration and Image Management now? (yes/no) yes Tip If you enter no at the preceding prompt, Configuration and Image Management will not be installed as part of the upgrade. After the upgrade is complete, you can install Configuration and Image Management separately using the setup_xmp_nccm.cmd command. Entering no at the preceding prompt and installing Configuration and Image Management separately speeds up the upgrade. - ANA upgrade can create the necessary database user for configuration and image management, or it can use any pre-defined user. Do you want ANA to create the user (recommended) (yes/no) [Default: yes] yes 12-12

13 Chapter 12 Upgrading to Cisco Prime Network 3.8 Upgrading from Cisco ANA 3.7.x to Cisco Prime Network Please enter DB Admin User name: [Default: system] username - Please enter DB Admin password: password - Enter the path location for the Configuration and Image Management DB data files: location-name Going to install the Configuration and Image Management components. This may take some time, please wait... - Executing UnInstallScriptsHook.. - Executing UpdateOidArrays.. - Executing LicenseEvaluationSystemResetHook.. - Executing RemoveAvmPersistency.. - Executing com/cisco/nm/ana/dev/upgrade/v371/update_ssh_config_hook.pl.. - Executing UpgradeJDKHook.. + Upgrading to Updating ANA directories & files - Updating Golden Source directories - Updating 3rd party jars - Removing patches - Updating ANA client components - Updating ANA plugins [OK] - Running the ANA upgrade procedures - Executing AddNewKeyAvm99Hook.. - Executing com/cisco/nm/ana/dev/upgrade/v372/fault/fault.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v372/vlan/carriere.sql.. - Executing AddAnaUserAdmin.. b. Enter the database user information: + ANA setup can create the ana37_admin database user, or it can use any pre-defined user. This user is used for gathering statistics about the system. if you chose to let ANA create the user it will use the ana37 scheme password as the ana37_admin password. Do you want ANA to create the user (recommended) (yes/no) [Default: yes] yes - Enter Oracle's admin username: [Default: system] username - Enter Oracle's admin password: password - Enter the location of the ana37_admin data files: location-name Note If you manually created the admin database users, choose no. c. The upgrade procedure continues the hooks to update your existing Cisco ANA installation: - Executing com/cisco/nm/ana/dev/upgrade/v372/fault/fault_ep.sql.. - Executing LicenseFunctionalTierNasSetterHook.. - Executing IdentifiedUnmanagedSubnetsHook.. - Executing PartitioningRegistryHook.. - Executing RemoveDriversHook.. d. The upgrade procedure removes the existing VNE drivers and replaces them with the contents of the ivne-drivers.tar file. At the prompt, point to the directory you created in Step 14: - Please specify the folder that contains ivne-drivers.tar : folder-name - Executing MixModeJdkLinks.. - Executing com/cisco/nm/ana/dev/upgrade/v372/fix_post_login.pl.. - Executing UpdateTopologyServiceHook.. - Executing UpdateAvm99ControlledHook.. - Executing CopyHADirHook.. - Executing UpdateUnitPm.. - Executing DM77UpdateHookForBsm.. - Executing ExtractAndInstallXmpNccmMigration372Hook.. e. If Configuration and Image Management was previously installed, it is upgraded automatically to and user data is preserved: 12-13

14 Upgrading from Cisco ANA 3.7.x to Cisco Prime Network 3.8 Chapter 12 Upgrading to Cisco Prime Network ANA is bundled with Configuration and Image Management runtime. It will be upgraded now to version if it is present. Upgrading Configuration and Image Management components if they are present. This may take some time, please wait... + Updating persistency - Executing com/cisco/nm/ana/dev/upgrade/v372/update_report.sql.. - Executing RemoveReportsJarsHook.. - Executing RemoveWebrootFilesHook.. - Executing RemoveOldFiles.. - Executing com/cisco/nm/ana/dev/upgrade/v372/pseudowire/pw.sql.. - Executing UpgradeJDKHook Executing com/cisco/nm/ana/dev/upgrade/v372/fault/remove_event_persistency.pl.. - Executing com/cisco/nm/ana/dev/upgrade/v372/update_se_and_pwedge.sql.. - Executing RemoveRegistryFilesHook.. - Executing UpdateWorkflowServiceHook.. - Executing UpdateUnitFiles.. - Executing EmptyHook.. - Running deploy.cmd files [OK] + Upgrading to Updating ANA directories & files - Updating Golden Source directories - Updating 3rd party jars - Removing patches - Updating ANA client components - Updating ANA plugins [OK] - Running the ANA upgrade procedures - Executing UpdateXmpNccmPersistency373Hook.. + Updating persistency - Executing ExtractAndInstallXmpNccmMigration373Hook.. - ANA is bundled with Configuration and Image Management runtime. It will be upgraded now to version if it is present. Upgrading Configuration and Image Management components if they are present. This may take some time, please wait... + Updating persistency - Executing UpdateCeServiceHook.. - Executing com/cisco/nm/ana/dev/upgrade/v373/appscore/appscore.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v373/plugin.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v373/fault/fault.sql.. - Executing MigrateTicketHistoryHook.. f. During the upgrade, values for the new CreationTime, RootEventTime, and Description ticket properties are automatically set for all active (non-archived) tickets. For archived tickets, this is optional. If you want to upgrade the archived tickets with the new CreationTime, RootEventTime, and Description ticket properties, enter Y at the next prompt, and the new ticket properties will be set for archived tickets. (Updating the archive tickets might take up to ten minutes for every 30,000 tickets.) - Would you like to upgrade all the Archived Tickets in the system? This might take some time, depending on the number of Archived Tickets. Consult your Cisco representative for more details (Y/N) [Default: N] Upgrade will not run on the Archived Tickets in the system - Executing com/cisco/nm/ana/dev/upgrade/v373/statsproc/admin_sql.sql.. - Executing EmptyHook.. - Running deploy.cmd files [OK] + Upgrading to Updating Prime Network directories & files - Updating Golden Source directories - Updating 3rd party jars - Removing patches - Updating Prime Network client components - Updating Prime Network plugins [OK] - Running the Prime Network upgrade procedures - Executing UpdatePerlDriversHook

15 Chapter 12 Upgrading to Cisco Prime Network 3.8 Upgrading from Cisco ANA 3.7.x to Cisco Prime Network Executing com/cisco/nm/ana/dev/upgrade/v380/fault/fault.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v380/fault/fault_ep.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v380/evc/ethernetservicegroup.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v380/tptunnel/mplstptunnel.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v380/clock/networkclockservice.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v380/pseudowire/alter_pseudowire.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v380/discovery/discovery.sql.. - Executing SignJarsHook.. - Running deploy.cmd files [OK] Step 22 Step 23 Enter the directory containing the upgrade files - Please specify the root directory which contains the installation/upgrade so that the system can access the necessary folder(s). /auto/cd2/cdimages/ana3.8_il_sol/daily/ana3.8_il_sol_latest_good/image/ - Executing com/cisco/nm/ana/dev/upgrade/v380/upgrade_embedded.pl.. - Executing UpdateAvm11ENSHook.. - Executing UpdateAVM100MemoryHook.. - Executing com/cisco/nm/ana/dev/upgrade/v380/update_report.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v380/vlan/carriere.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v380/update_dm_properties_hook.pl.. - Executing SuiteInteg.. The installer asks if Cisco Prime Network is installed as part of the Cisco Prime IP-NGN Suite: + Is Prime Network being installed as part of the Prime IP-NGN Suite? (yes,no) [default no] If you answer yes, additional questions are displayed: - Enter the Cisco Prime Central database server IP address: - Enter the Cisco Prime Central database SID: - Enter the Cisco Prime Central database username: - Enter the Cisco Prime Central database password: - Enter the Cisco Prime Central database port: Provide the Cisco Prime Central database server IP address, SID, username, password and port. After providing this information, Cisco Prime Network will be launched in suite mode. See the Cisco Prime Central 1.0 Quick Start Guide for more information. After you respond to the Cisco Prime IP-NGN Suite question, the following output is displayed: - Executing BlockingOldClients.. - Executing com/cisco/nm/ana/dev/upgrade/v380/remove_old_ana_scripts.pl.. - Executing com/cisco/nm/ana/dev/upgrade/v380/embedded_update_db_accounts_and_profiles.pl.. - Executing AddAnaAdminAndXmpUserDefaults.. - Executing RemoveOldBirtRedundantJars.. - Executing com/cisco/nm/ana/dev/upgrade/v380/appscore/searchworkflow.sql.. - Executing UpdateWorkflowMemorySizeHook.. - Executing UpdateWorkflowAVMStatusHook.. - Executing WorkflowSearchMigrationHook.. log4j:warn No appenders could be found for logger (dralasoft.workflow). log4j:warn Please initialize the log4j system properly. log4j:warn See for more info. - Executing FixHaProtocolEntriesHook.. - Executing AddAvm82ToAvm Executing com/cisco/nm/ana/dev/upgrade/v380/cre_unit_seq.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v380/cre_em_seq.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v380/ipv6_related_upgrade.pl.. - Executing UpdateRsyncOnRemoteUnits.. - Executing UpdatCshrcFiles.. - Executing CreateUnitIDsHive.. - Executing RemoveAvmPersistency.. - Executing RemoveTopologyPersistency

16 Upgrading from Cisco ANA 3.7.x to Cisco Prime Network 3.8 Chapter 12 Upgrading to Cisco Prime Network Executing AVM35DefaultHook.. - Executing ExtractAndInstallXmpNccmMigration38Hook.. Step 24 If Cisco ANA Configuration and Image Management was installed previously, it is upgraded to Cisco Prime Network Change and Configuration Management. If it was not installed previously, Cisco Prime Network Change and Configuration Management is installed. - Prime Network is bundled with Change and Configuration Management runtime. It will be upgraded now to version 3.8 if an earlier version is installed. Otherwise, a fresh copy of version 3.8 will be installed. Upgrading Change and Configuration Management if it is present. This will take some time, please wait... + Updating persistency - Executing UpdateEventCollectorEntriesHook.. - Executing AddAvm76ToAvm Executing AddAutoAssignInAvm11Avm Executing com/cisco/nm/ana/dev/upgrade/v380/jobscheduler/job.sql.. - Executing com/cisco/nm/ana/dev/upgrade/v380/install_nsa_hook.pl.. - Executing RemoveBakFilesHook.. Cisco Prime Network upgrade process creates the backup files. To remove these.bak files, enter yes in the following prompt. - Would you like to remove.bak files under /export/home/network-user? (yes/no) yes Note While performing an upgrade installation, only the job data of Configuration and Image Management is not preserved; all the other application and user data are preserved for Change and Configuration Management. Step 25 If you installed the Cisco ANA Red Hat Cluster Suite gateway high availability, the upgrade will ask you to enter the following physical IP addresses: The IP address of the server you are logged into, If local redundancy was configured, the IP address of the other local cluster node, and If geographical redundancy was configured, the IP address of the remote geographical redundant node. - Executing RHHARegistryHook.. - Please specify the physical host ip for this server : Please specify the physical ip for the other node in the RH cluster : Please specify the physical ip for DR remote server : After entering the IP addresses, the upgrade continues: - Executing RHHAValidateReplicationHook.. - Executing RHHACorrectSwitchHook.. - Executing AddSecondaryHost.. - Executing EmptyHook.. - Running deploy.cmd files [OK] - Copying WAR file to XMP directory [OK] + Running post upgrade tasks - Updating crontab on the gateway [OK] - Updating crontab on the units - Updating login, aliases and ctl files on the units - Starting Prime Network.. [OK] 12-16

17 Chapter 12 Upgrading to Cisco Prime Network 3.8 Upgrading from Cisco ANA 3.7.x to Cisco Prime Network Upgrade completed, check logs for further information. The upgrade logs are available at /export/home/network-user/main/upgrade log. You need to re-login as the Prime Network user for environment changes to take place. g. The independent VNE (IVNE) drivers menu appears. If you do not want to update the IVNEs now, enter q. If you want to update them, choose 3, then choose the directory into which you extracted the contents of the ivne-driver.tar in Step 14. Note Cisco ANA or Cisco ANA with Device Package 8.0 or later: After upgrading to Cisco Prime Network 3.8, you must install Prime Network 3.8 Device Package 1.0 from Cisco.com in order to have the same level of device support that you had in your earlier installation. This is because Prime Network 3.8 includes all of the support that is provided up to Cisco ANA 3.7.2/3.7.3 Device Package 7.0. You can update the drivers later following the procedures provided in Cisco Prime Network 3.8 Administrator Guide. Note The other IVNE options do not apply to upgrades.????????????????????????????????????????????????????????????????????????????????? Cisco Prime Network Independent VNE Driver Installer??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????1?Install independent VNE drivers from Device Package tar file (recommended).??2?install independent VNE driver jar file from a web repository.??3?install independent VNE driver jar file from a local folder??4?rollback to a previous independent VNE driver installation.??5?list the existing drivers and their versions.??q?quit.????????????????????????????????????????????????????????????????????????????????? Make a selection and press Enter. Step 26 After the upgrade is complete, Cisco Prime Network starts automatically. Log in as the network-user for the environment changes to take effect. Tip Step 27 You do not need to upgrade the standby unit separately; standby units are upgraded automatically. A standby unit completes its upgrade when it is started by the gateway, which occurs when a nonstandby unit switches to the standby unit. If any of the preceding steps fail, the following error message is shown: Failed to execute hook-type for hook-name. See log for further details. - Hook hook-name terminated with failure - Please choose one of the following: 1. Abort the upgrade process 2. Re-run the hook In the error message, hook-type is the type of procedure that was executed; hook-name is the specific procedure that failed. Check the upgrade log(/network-home/main/upgrade-timestamp.log) to identify the reason for the failure

18 Rolling Back from Cisco Prime Network 3.8 Chapter 12 Upgrading to Cisco Prime Network 3.8 If you can identify the problem and fix it manually, do so; then, choose option 2 to rerun the hook. The upgrade procedure continues from the procedure that failed. If you cannot fix the problem, choose option 1 to cancel the upgrade. After canceling the upgrade, Cisco Prime Network cannot be started. Contact your Cisco account representative to fix the problem; then, rerun the upgrade. The upgrade procedure continues from the procedure that failed. Note If you decide not to rerun the upgrade, you must roll back to your base Cisco Prime Network environment, including rolling back the database. See Rolling Back from Cisco Prime Network 3.8, page Step 28 If you upgraded an RHCS/ADG Local HA configuration, take the ana and oracle_db services out of maintenance mode: clusvcadm -U ana clusvcadm -U oracle_db Rolling Back from Cisco Prime Network 3.8 Rollback is available if you encounter problems during the upgrade, or if you need to roll back to an earlier version after the upgrade completes. Complete the following sections to roll back to 3.7.x: Rolling Back from Cisco Prime Network 3.8 to Cisco ANA 3.7.x, page Note If you are rolling back a gateway and one or more units connected to the gateway, roll back the units first, then the gateway. The rollback will remove redundant units from the registry and the GoldenSource. Rolling Back from Cisco Prime Network 3.8 to Cisco ANA 3.7.x Step 1 Step 2 Step 3 Step 4 Verify that the Cisco Prime Network application is not running. Verify that the gateway and units are powered up and connected. That is, you can open an SSH session between the gateway and all units. If your environment contains standby/nat units, use Cisco Prime Network Administration to remove the standby/nat units from the gateway. Restore the backed-up database and start the database services and the listener. The database table structure changed during the upgrade. In order for the system to function correctly after a rollback, the old table structure must be recovered through a database backup. To restore an external database, contact your database administrator. Do the following to restore an embedded database: a. Log into the gateway as network user. b. Change to the directory NETWORKHOME/Main/scripts/embedded_db: # cd $ANAHOME/Main/scripts/embedded_db c. Execute the restoration script: # emdbctl --restore 12-18

19 Chapter 12 Upgrading to Cisco Prime Network 3.8 Rolling Back from Cisco Prime Network 3.8 Note After you restore the database, Cisco Prime Network tries to reboot. The reboot does not succeed, and an error appears in the gateway log that AVMs with a heap size of 6 GB cannot be configured. You can ignore this message and continue with the next step. Step 5 Step 6 As the network-user, go to the directory where the ANA_upgrade directory was copied during the Cisco Prime Network 3.8 upgrade procedure and enter the following command to change to the ANA_upgrade directory: cd ANA_upgrade As the Cisco Prime Network user, enter the following command on the Cisco Prime Network gateway only: perl rollback.pl Caution Do not deploy the rollback.pl script in the Cisco Prime Network home directory. If you do this, an error message appears that the script should not run from this location. Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 At the Have you rolled back the database? enter yes if you have rolled back the database, as described in Step 4. If you have not rolled back the database, do not continue. Complete the database rollback first, then start this procedure again. At the Have you reinstalled the units? enter yes if you have reinstalled any units connected to the gateway. If not, do not continue. Reinstall the units, then begin the procedure again. At the prompt Are you sure you want to roll back the current Prime Network installation, enter yes: - Writing log to /export/home/ana-upgrade/ana_upgrade/rollback-number.log - Are you sure you want to rollback the current Prime Network installation? (yes,no) [default yes] yes - Stopping Prime Network on GW & units At the prompt Please enter the full path to the backup archive file, enter the location of the backup archive directory. The rollback.pl script does not delete the backup archive. - Please enter the full path to the backup archive file: /export/home/ana-upgrade/anabkup/primenetworkbackup_number.tar.gz The scripts reverts the gateway back to its earlier version: - Stopping Prime Network on gateway - Removing content of /export/home/network-user [OK] - Extracting backup archive under /export/home/network-user [OK] - Removing Standby Units [OK] - Starting Prime Network on gateway + Rollback completed successfully. Please remember to do the following: - Manually roll back database changes because ANA does not roll back these changes. - Reinstall the units (see the ANA Installation Guide for instructions) - Re-login as the ANA user for environment changes take place check logs for further information. - Rollback logs can be found at <logfile> Configure all units using the command ana-conf. Use ANA Manage to reconnect the standby and NAT units

20 Postupgrade Tasks Chapter 12 Upgrading to Cisco Prime Network 3.8 Step 14 Step 15 After the rollback to your original Cisco Active Network 3.7.x environment is complete, reconfigure your user-defined crontabs. Use the anactl start command to start the units. Postupgrade Tasks After the upgrade to Cisco Prime Network 3.8 is complete, you must perform the postupgrade tasks described in this section. Updating the Database Host in the Registry If you are using network address translation (NAT) with the Cisco Prime Network Vision client, update the database host in the Prime Network registry to contain the hostname instead of the IP address. Complete the following mandatory steps after the upgrade to Cisco Prime Network 3.8 is complete and the system is up and running. Note If you already use a hostname instead of an IP address, you do not have to repeat this procedure. Step 1 Step 2 Before changing the hostname, verify that the Windows client workstations have the correct Domain Name System (DNS) mapping. From ~/Main, enter the following commands:./runregtool.sh -gs set site/persistency/nodes/main/host database-server-hostname./runregtool.sh -gs set site/persistency/nodes/ep/host database-server-hostname Step 3 Enter the following command to restart the Cisco Prime Network system: anactl restart Updating the Customized Message of the Day Content The upgrade process overrides the customized Message of the Day and restores the default message. After upgrading to Cisco Prime Network 3.8, use Cisco Prime Network Administration to re-enter your customized Message of the Day content. Updating the Port Watchdog Scripts After upgrading to Cisco Prime Network 3.8, you must copy the port watchdog scripts to /var/adm/cisco/network/scripts. To do this, enter the following commands as the root user: mkdir p /var/adm/cisco/network/scripts cp network-home/main/scripts/port_watchdog.pl /var/adm/cisco/network/scripts cp network-home/main/scripts/keep_alive_port_watchdog.pl /var/adm/cisco/network/scripts chmod -R 700 /var/adm/cisco/network/scripts 12-20

21 Chapter 12 Upgrading to Cisco Prime Network 3.8 Postupgrade Tasks chown -R network-user:network /var/adm/cisco/network/scripts Note network-home is the Cisco Prime Network installation directory. network-user is the UNIX user account for the Cisco Prime Network application, created when Cisco Prime Network is installed. Recreating Business Objects If you are upgrading from Cisco Prime Network 3.6.x and you had business objects assigned to link elements, complete the following steps after the upgrade script finishes running: Step 1 Open the ~/Main/BOTableLinkOIDs.log.* file and verify the presence of business objects that were attached to links. Step 2 Retain the BOTableLinkOIDs.log.* file. When the system is up after the Cisco Prime Network 3.8 upgrade, use the Cisco Prime Network client GUI or BQL commands to recreate the business objects that appear in the log file. Note The OID in the BOTableLinkOIDs.log is in the old format, which does not have the LinkType property. If you are using the Cisco Prime Network client GUI, you must identify the corresponding link manually. If you are using BQL commands, you must convert the old OID format to the new format, instead of using the OIDs in the BOTableLinkOIDs.log file. Managing Events If you are upgrading from Cisco ANA or 3.7, event and fault data is available when the upgrade is complete. If you are upgrading from Cisco Prime Network 3.6.x, see the section Managing 3.6.x Events in the Cisco Active Network Abstraction 3.7 Installation Guide to understand the event migration. Postmigration event management in Cisco Prime Network 3.8 is the same as in Cisco ANA and 3.7. Event types (identifiers) changed from 3.7 to 3.7.1, but did not change from to 3.8. To understand the event types changes from 3.7 to 3.7.1, see the section Managing Events in the Cisco Active Network Abstraction Installation Guide. Maintaining Support for Third-Party VNEs In Cisco Prime Network 3.8, third-party VNE drivers are disabled by default. Third-party VNE support includes devices from: Alcatel ECI Hi-Focus 12-21