Cisco Element Manager System Installation and Configuration Guide, 3.1 - Upgrading Cisco EMF [Cisco Element Manager System]

Table Of Contents

Upgrading Cisco EMF

Upgrading only Cisco EMF

Upgrading Cisco EMF and Updated Element Managers

Upgrading Cisco EMF

If you wish to upgrade an installed Cisco EMF, you can perform an upgrade installation. During an upgrade, you will have to upgrade versions of Cisco EMF and versions of Element Managers. All Client workstations must be upgraded at the same time as the Server.

Caution For full details of Element Managers and the appropriate upgrade scenario and procedure to be used refer to the associated Element Manager documentation.

There can be various upgrade scenarios. This chapter describes two examples:

•the scenario where only the version of Cisco EMF is upgraded, refer to Upgrading only Cisco EMF

•the scenario where both Cisco EMF and one or more Element Manager need to be upgraded. The objective is that no databases or information is lost during the upgrade. This section explains how this should be done. Refer to Upgrading Cisco EMF and Updated Element Managers.

Note Check the type of upgrade required for each Element Manager before starting any upgrade installation. This information should be provided in the Release Notes.

Upgrading only Cisco EMF

The example given below assumes the following scenario:

•multiple Element Managers are deployed on Cisco EMF v3.0.x, and the system is operational

•the Element Managers have been rebuilt, tested and released on Cisco EMF v3.1

•no changes have been made to the metamodel, services, clear correlation rules, or history criteria, refer to the Element Manager documentation

Upgrade the Cisco EMF v3.0.x system to Cisco EMF v3.1 as follows:

Step 1 Login to the machine where Cisco EMF is installed as the superuser. (su)

Step 2 Change directory to the Cisco EMF bin directory, type:

cd <CEMF_ROOT>/bin

Step 3 Backup all databases. Note that it is necessary to have sufficient disk space for the backups. Refer to Chapter 11, "Cisco EMF Database Backup and Restore Procedures" for complete details.

Step 4 To display a list of all Cisco EMF packages, type:

./cemf install -show

This will list the version of Cisco EMF and the package type and all Element Managers and their package types.

Step 5 Deinstall the Element Managers. For each Element Manager, run:

./cemf install -remove

then choose the option you require from the menu.

Step 6 Stop Cisco EMF, type:

./cemf stop

Step 7 Remove the current Cisco EMF installation and any Cisco EMF installed patches, type:

./cemf install -remove

then choose the option you require from the menu.

Caution The order in which components are removed is important. You must deinstall the patches first, in reverse order starting with the latest patch. For example, if patches 3, 4 and 5 are installed, you must deinstall patch 5, then patch 4, then patch 3, then Cisco EMF itself.

Step 8 The selected Cisco EMF and its Element Manager installations have been removed, you can now install Cisco EMF v3.1. Refer to the details in Installing Cisco EMF.

Caution All the chosen paths in the new V3.1 installation must be exactly the same as those in the previous installation, for example database location, transaction log location, <CEMF_ROOT> location etc.

Step 9 Change directory to the Cisco EMF bin directory, type:

cd <CEMF_ROOT>/bin

Step 10 Start Cisco EMF, type

./cemf start

Cisco EMF processes start.

Step 11 Now install the v3.1 Element Managers. For each Element Manager, type:

./cemf install <path>

where <path> is the location of the Element Manager packages. Then choose the option you require from the menu.

Step 12 The final stage is to restore the data. To do this, Cisco EMF must not be running. type:

./cemf stop

Step 13 The databases can now be restored, type:

./cemf restore -u

Note The restore -u option restores the databases and inhibits the restoration of configuration files. Refer to Chapter 11, "Cisco EMF Database Backup and Restore Procedures" for complete details.

Step 14 Cisco EMF and the Element Managers can now be started, type

./cemf start forupgrade

Step 15 The backups created at Step 3 should only be removed after the upgraded Cisco EMF and Element Manager installation has been fully tested and verified.

Upgrading Cisco EMF and Updated Element Managers

The example given below assume the following scenario:

•multiple Element Managers are deployed on Cisco EMF v3.0.x, and the system is operational

•the Element Managers have been rebuilt, tested and released on Cisco EMF v3.1. One, or more, of the Element Managers have been modified.

•changes have been made to the metamodel, services, clear correlation rules, or history criteria, refer to the Element Manager documentaiton

Upgrade the Cisco EMF v3.0.x system to Cisco EMF v3.1 as follows:

Step 1 Login to the machine where Cisco EMF is installed as the superuser. (su)

Step 2 Change directory to the Cisco EMF bin directory, type:

cd <CEMF_ROOT>/bin

Step 3 Backup all databases. Note that it is necessary to have sufficient disk space for the backups. Refer to Chapter 11, "Cisco EMF Database Backup and Restore Procedures" for complete details. This is a precautionary measure, in case there are problems with the subsequent upgrade. If the upgrade is sucessful, this backup will not be required.

Step 4 To display a list of all Cisco EMF packages, type:

./cemf install -show

This will list the version of Cisco EMF and the package type and all Element Managers and their package types.

Step 5 Deinstall the Element Managers for upgrade. For each Element Manager, type:

./cemf install -remove -o -upgrade

then choose the option you require from the menu.

Step 6 Backup the databases. Type:

./cemf backup -l <backup path B>

Ensure that the backup path you specify here is different from the path specified in Step 3.

Note These are the backups that will be restored later.

Step 7 Stop Cisco EMF, type:

./cemf stop

Step 8 Remove the current Cisco EMF installation and Cisco EMF patches, type:

./cemf install -remove

then choose the option you require from the menu.

Caution The order in which components are removed is important. You must deinstall the patches first, in reverse order starting with the latest patch. For example, if patches 3, 4 and 5 are installed, you must deinstall patch 5, then patch 4, then patch 3, then Cisco EMF itself.

Step 9 Cisco EMF v3.0.x and its Element Managers are now removed, and the Cisco EMF v3.1 system can be installed. Insert the Cisco EMF product CD into the CD-ROM device.

Step 10 Change directory into the cdrom area. At the command line prompt, type:

cd /cdrom/cdrom0

Step 11 Install Cisco EMF v3.1, type:

./cemfinstall

from the Cisco EMF v3.1 CD-ROM.

Caution All the chosen paths in the new V3.1 installation must be exactly the same as those in the previous installation, for example database location, transaction log location, <CEMF_ROOT> location etc.

Step 12 Change directory to the Cisco EMF bin directory, type:

cd <CEMF_ROOT>/bin

Step 13 Start Cisco EMF, type

./cemf start

Cisco EMF processes start and Cisco EMF is initialized.

Step 14 Stop Cisco EMF, type:

./cemf stop

Step 15 Restore the databases backed up in Step 6. The databases can now be restored, type:

./cemf restore -t <dateofbackup> -l <backup path B>

The <dateofbackup> value is the date the backups in Step 6 were created.

Step 16 Start Cisco EMF v3.1, type:

./cemf start forupgrade

Step 17 Now install the v3.1 Element Managers. For each Element Manager, type:

./cemf install <path>

where <path> is the path of the Element Manager, then choose the option you require from the menu.

Step 18 The backups created at Step 3 and Step 6 should only be removed after the upgraded Cisco EMF and Element Manager installation has been fully tested and verified.

	Cisco Element Manager System Installation and Configuration Guide, 3.1
	Upgrading Cisco EMF
Cisco Element Manager System Installation and Configuration Guide, 3.1 About This Guide Installation Checklist Cisco EMF Configuration Options License Requirements ObjectStore Installation Options Administering Cisco EMF Workstations Upgrading Cisco EMF Installing and Deinstalling Element Managers Deinstalling Cisco EMF Installing and Deinstalling a Patch Cisco EMF Database Backup and Restore Procedures Access Control Auto Discovery Performance Data Storage Creating a New Thresholding Regime Using the Command Line Interface Northbound Event Interface Troubleshooting	Download this chapter Upgrading Cisco EMF Feedback Table Of Contents Upgrading Cisco EMF Upgrading only Cisco EMF Upgrading Cisco EMF and Updated Element Managers Upgrading Cisco EMF If you wish to upgrade an installed Cisco EMF, you can perform an upgrade installation. During an upgrade, you will have to upgrade versions of Cisco EMF and versions of Element Managers. All Client workstations must be upgraded at the same time as the Server. Caution For full details of Element Managers and the appropriate upgrade scenario and procedure to be used refer to the associated Element Manager documentation. There can be various upgrade scenarios. This chapter describes two examples: •the scenario where only the version of Cisco EMF is upgraded, refer to Upgrading only Cisco EMF •the scenario where both Cisco EMF and one or more Element Manager need to be upgraded. The objective is that no databases or information is lost during the upgrade. This section explains how this should be done. Refer to Upgrading Cisco EMF and Updated Element Managers. Note Check the type of upgrade required for each Element Manager before starting any upgrade installation. This information should be provided in the Release Notes. Upgrading only Cisco EMF The example given below assumes the following scenario: •multiple Element Managers are deployed on Cisco EMF v3.0.x, and the system is operational •the Element Managers have been rebuilt, tested and released on Cisco EMF v3.1 •no changes have been made to the metamodel, services, clear correlation rules, or history criteria, refer to the Element Manager documentation Upgrade the Cisco EMF v3.0.x system to Cisco EMF v3.1 as follows: Step 1 Login to the machine where Cisco EMF is installed as the superuser. (su) Step 2 Change directory to the Cisco EMF bin directory, type: cd <CEMF_ROOT>/bin Step 3 Backup all databases. Note that it is necessary to have sufficient disk space for the backups. Refer to Chapter 11, "Cisco EMF Database Backup and Restore Procedures" for complete details. Step 4 To display a list of all Cisco EMF packages, type: ./cemf install -show This will list the version of Cisco EMF and the package type and all Element Managers and their package types. Step 5 Deinstall the Element Managers. For each Element Manager, run: ./cemf install -remove then choose the option you require from the menu. Step 6 Stop Cisco EMF, type: ./cemf stop Step 7 Remove the current Cisco EMF installation and any Cisco EMF installed patches, type: ./cemf install -remove then choose the option you require from the menu. Caution The order in which components are removed is important. You must deinstall the patches first, in reverse order starting with the latest patch. For example, if patches 3, 4 and 5 are installed, you must deinstall patch 5, then patch 4, then patch 3, then Cisco EMF itself. Step 8 The selected Cisco EMF and its Element Manager installations have been removed, you can now install Cisco EMF v3.1. Refer to the details in Installing Cisco EMF. Caution All the chosen paths in the new V3.1 installation must be exactly the same as those in the previous installation, for example database location, transaction log location, <CEMF_ROOT> location etc. Step 9 Change directory to the Cisco EMF bin directory, type: cd <CEMF_ROOT>/bin Step 10 Start Cisco EMF, type ./cemf start Cisco EMF processes start. Step 11 Now install the v3.1 Element Managers. For each Element Manager, type: ./cemf install <path> where <path> is the location of the Element Manager packages. Then choose the option you require from the menu. Step 12 The final stage is to restore the data. To do this, Cisco EMF must not be running. type: ./cemf stop Step 13 The databases can now be restored, type: ./cemf restore -u Note The restore -u option restores the databases and inhibits the restoration of configuration files. Refer to Chapter 11, "Cisco EMF Database Backup and Restore Procedures" for complete details. Step 14 Cisco EMF and the Element Managers can now be started, type ./cemf start forupgrade Step 15 The backups created at Step 3 should only be removed after the upgraded Cisco EMF and Element Manager installation has been fully tested and verified. Upgrading Cisco EMF and Updated Element Managers The example given below assume the following scenario: •multiple Element Managers are deployed on Cisco EMF v3.0.x, and the system is operational •the Element Managers have been rebuilt, tested and released on Cisco EMF v3.1. One, or more, of the Element Managers have been modified. •changes have been made to the metamodel, services, clear correlation rules, or history criteria, refer to the Element Manager documentaiton Upgrade the Cisco EMF v3.0.x system to Cisco EMF v3.1 as follows: Step 1 Login to the machine where Cisco EMF is installed as the superuser. (su) Step 2 Change directory to the Cisco EMF bin directory, type: cd <CEMF_ROOT>/bin Step 3 Backup all databases. Note that it is necessary to have sufficient disk space for the backups. Refer to Chapter 11, "Cisco EMF Database Backup and Restore Procedures" for complete details. This is a precautionary measure, in case there are problems with the subsequent upgrade. If the upgrade is sucessful, this backup will not be required. Step 4 To display a list of all Cisco EMF packages, type: ./cemf install -show This will list the version of Cisco EMF and the package type and all Element Managers and their package types. Step 5 Deinstall the Element Managers for upgrade. For each Element Manager, type: ./cemf install -remove -o -upgrade then choose the option you require from the menu. Step 6 Backup the databases. Type: ./cemf backup -l <backup path B> Ensure that the backup path you specify here is different from the path specified in Step 3. Note These are the backups that will be restored later. Step 7 Stop Cisco EMF, type: ./cemf stop Step 8 Remove the current Cisco EMF installation and Cisco EMF patches, type: ./cemf install -remove then choose the option you require from the menu. Caution The order in which components are removed is important. You must deinstall the patches first, in reverse order starting with the latest patch. For example, if patches 3, 4 and 5 are installed, you must deinstall patch 5, then patch 4, then patch 3, then Cisco EMF itself. Step 9 Cisco EMF v3.0.x and its Element Managers are now removed, and the Cisco EMF v3.1 system can be installed. Insert the Cisco EMF product CD into the CD-ROM device. Step 10 Change directory into the cdrom area. At the command line prompt, type: cd /cdrom/cdrom0 Step 11 Install Cisco EMF v3.1, type: ./cemfinstall from the Cisco EMF v3.1 CD-ROM. Caution All the chosen paths in the new V3.1 installation must be exactly the same as those in the previous installation, for example database location, transaction log location, <CEMF_ROOT> location etc. Step 12 Change directory to the Cisco EMF bin directory, type: cd <CEMF_ROOT>/bin Step 13 Start Cisco EMF, type ./cemf start Cisco EMF processes start and Cisco EMF is initialized. Step 14 Stop Cisco EMF, type: ./cemf stop Step 15 Restore the databases backed up in Step 6. The databases can now be restored, type: ./cemf restore -t <dateofbackup> -l <backup path B> The <dateofbackup> value is the date the backups in Step 6 were created. Step 16 Start Cisco EMF v3.1, type: ./cemf start forupgrade Step 17 Now install the v3.1 Element Managers. For each Element Manager, type: ./cemf install <path> where <path> is the path of the Element Manager, then choose the option you require from the menu. Step 18 The backups created at Step 3 and Step 6 should only be removed after the upgraded Cisco EMF and Element Manager installation has been fully tested and verified.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks