|
|
The Cisco Element Management Framework (Cisco EMF) installation instructions detail how to install and de-install a Cisco EMF Server and a Cisco EMF Client. System requirements for the different installations are also specified.
Cisco EMF can be deployed with a server and clients to utilize the power of multiple machines. A typical deployment is shown in Figure 1-1.
Two types of deployment are available:
Every Cisco EMF deployment must have a Cisco EMF Server installed. Processes on the Cisco EMF Server keep track of the current state of the network model, user access, events etc. The Object Store database system should be installed on this machine.
A Cisco EMF deployment may have the Client installation on separate workstations, which are used to run Cisco EMF applications to access objects on the Server. A Client installation contains only those parts of the Cisco EMF system necessary for a Cisco EMF user session. This user session communicates back to the Cisco EMF Server, when required, to retrieve management information. The Cisco EMF GUI runs on the Cisco EMF client machine, which frees system resources on the Cisco EMF server machine to process network information.
The Cisco EMF Client installation process installs the Client software on the local machine, therefore, you need not mount files across a network. Network traffic occurs only when the Client requires more data from the Server.
Cisco EMF can be deployed in a number of different configurations, from a single hardware system to a multi-site management system, using Sun Solaris/SPARC hardware with Solaris Release 2.6.
A basic Cisco EMF Server installation requires at least 300MB of free file system disk space (for example, in /opt) and an appropriate amount of free disk space for database files (refer to Table 1-1).
| Resource | Cisco EMF (large installation) | Cisco EMF (small installation) | Cisco EMF Client |
|---|---|---|---|
Hardware | Sun Enterprise 450 | Sun Ultra 60 workstation | Sun Ultra 5 workstation |
Operating System | Solaris 2.6 | Solaris 2.6 | Solaris 2.6 |
Memory | 1GB RAM | 1GB RAM | 256MB RAM |
Disk Space | Six 9GB 10,000 RPM disks | Two 9GB internal disks 9GB 10,000 RPM external disk | 9GB disk |
Processor | Four x 250MHz | Two x 360MHz | 333MHz |
Swap Space | 2GB | 2GB | 2GB |
Monitor | 17" color | 17" color | 17" color |
Graphics Card | 24 bit | 24 bit | 24 bit |
Installations of Cisco EMF are subject to license control. Cisco EMF uses the FlexLM license manager, which is on the Cisco EMF product CD-ROM. If you need to integrate with an existing FlexLM license manager, refer to the procedures documented in the FLEXlm End User Manual located at ../../../../../../../../home/home.htm
The Cisco EMF Server requires a Cisco EMF license to run.
When you initially receive the Cisco EMF product, an evaluation license is provided. Upon installing the Cisco EMF product from the product CD, the evaluation license is automatically installed. The evaluation license allows you to evaluate the product for a period of thirty days. During this thirty day evaluation period, it is recommended you request a permanent license for the Cisco EMF product.
To acquire the required permanent license key file, you must do the following:
Step 1 If you are a registered Cisco Connection Online (CCO) user, navigate to the Cisco Software Registration site: http://cco.cisco.com/kobayashi/sw-center/sw-registration.shtml
If you are not a registered Cisco Connection Online user, navigate to the Cisco Software Registration site: http://cco.cisco.com/public/sw-center/sw-registration.shtml
Step 2 Click on the Cisco Element Management Framework link.
A License Request form is displayed.
Step 3 Fill in all required fields (denoted by an asterisk) in the Contact Information section of the License request form.
Step 4 Select the version of the Cisco EMF product you are licensing in the Version number field.
Step 5 If it was not automatically filled in for you when you filled in the Contact Information, specify the Product Authorization Key (PAK) number.
The PAK is provided on the Cisco EMF product CD sleeve.
Step 6 Specify the hostname of the server where the Cisco EMF product is installed.
You can obtain the server's hostname by typing the hostname command at the server's command line prompt.
Step 7 Specify the host ID (a hexadecimal string that identifies the system, not the IP address) of the server where the Cisco EMF product is installed.
You can obtain the server's host ID by typing the hostid command at the server's command line prompt.
Step 8 Please also provide answers to the questions at the end of the form, then click on the
Enter Form button.
The License Request form is submitted. The Cisco EMF permanent license key file is returned to you as an email attachment.
Step 9 Go to the "Updating a Cisco EMF License" section for instructions on how to replace a evaluation license with the permanent license.
To install software onto a system that does not have its own CD-ROM drive, mount the CD on the remote system, then export the device to make it accessible over the network. Both of these operations are done on the remote system with the CD-ROM drive. You must then mount the remote CD on the local system where the installation is to take place.
Step 1 Insert the Cisco EMF product CD into the CD-ROM drive on the remote host.
Step 2 On the remote host, login as superuser (su).
Step 3 On the remote host, export the CD-ROM device as follows:
(a) When they are not already running, start the NFS related daemons. At the command line prompt, type:
host# /usr/lib/nfs/nfsd 8
host# /usr/lib/nfs/mountd
(b) Share the mount point from the remote host. At the command line prompt, type:
host# share -F nfs -o ro /cdrom/cdrom0
(c) Verify that this host has made the CD-ROM drive accessible. At the command line prompt, type:
host# share
The output displayed should include the /cdrom mount point.
Step 4 On the local host, on which the installation is to take place, mount the remote CD-ROM.
(a) When it does not already exist, create a mount point. At the command line prompt, type:
host# mkdir /mnt/CEMFmnt
(b) Mount the remote directory. At the command line prompt, type:
host# mount -r <remote-host> : /cdrom/cdrom0 /mnt/CEMFmnt
where <remote-host> is replaced by the hostname of the remote device.
The contents of the CD are now visible under the /mnt/CEMFmnt mount point.
Before you install Cisco EMF you must:
1. Determine whether your network requires a small deployment on a single workstation, or a larger deployment in a multi-site, client/server configuration.
2. Determine the installation type (Server, Client, or Patch).
3. Determine the hostname of the machine where you are installing the Cisco EMF Server.
4. Determine the directory and/or path where the Cisco EMF software will be installed (recommended path is /opt/cemf).
5. Remove any old versions of ObjectStore. Cisco EMF requires V5.1. If this already exists, you must know where it is installed.
6. Obtain root, or superuser (su) password and privileges from your UNIX system administrator.
7. Locate the Cisco EMF product CD.
8. If the system on which you are installing the Cisco EMF Server software has multiple network cards, determine which network card/hostname/IP address pair will be used.
9. Determine if the Cisco EMF databases will be stored on a separate disk from the Cisco EMF Server, and if so, where.
Cisco EMF uses the cemfinstall program to install and deinstall Cisco EMF. Table 1-2 describes the cemfinstall parameters. You need not type the entire parameter, you can just specify the first letter of the parameter's name. For example, cemfinstall -h and cemfinstall -help can both be used to display help information.
| Parameter | Description |
|---|---|
| When no parameters are specified, the installation menu is displayed. |
-choice <choice> | Select the <choice> menu option. For example, cemfinstall -c 3 selects the third menu option. |
-dir [<directory>] | Display the location of the packages. |
-echoonly | Does not run (only echoes) the commands. |
-help | Displays help information. |
-remove | Removes an existing installation. |
-show | Shows all packages installed by the cemfinstall program. |
-yestoall | Answer Yes to all cemfinstall script questions. |
To install Cisco EMF, proceed as follows:
Step 1 Login as superuser (su) onto the workstation where Cisco EMF is to be installed.
Step 2 Insert the Cisco EMF product CD into the CD ROM device.
Step 3 Change directory into the cdrom area. At the command line prompt, type:
host# cd /cdrom/cdrom0
Step 4 Invoke the Cisco EMF installation script. At the command line prompt, type:
host# ./cemfinstall
ERROR: You must be root to run this Script error message is displayed. Login as superuser (su), then run the cemfinstall script again.
A menu listing the Cisco EMF installation options is displayed.
Step 5 Select the desired installation option, then press Enter.
Type Q to quit the installation process, then press Enter.
**Already Installed** message is displayed beside the option and the option to install that package is removed.
The following steps are only relevant when you select a Cisco EMF Server installation.
Step 1 After selecting the Server installation option, you are asked where the installation should be placed. The default location is /opt/cemf.
Step 2 If the default location is acceptable, press Enter.
Step 3 If a machine has more than one hostname, the hostname menu is displayed. Select the correct hostname, then press Enter. If the correct hostname is not listed in the menu, press Enter, type the desired hostname, then press Enter.
Step 4 When you have specified the directory, the Server hostname and IP address are displayed. When this setup is correct, press Enter. Otherwise, type n, then press Enter when you wish to change these values. You normally only change these values when your system has multiple network card interfaces from which to choose.
Step 5 When you have specified the relevant hostname and IP address, the installation process checks your system for a valid version of Object Store. You now proceed with the ObjectStore installation and configuration (refer to the "ObjectStore Installation Options" section for full details.)
Step 6 When the ObjectStore options are configured, you are asked for the DNS domain of your system. To accept the default, type y, then press Enter. To change the default, type n, press Enter, specify the relevant DNS domain, then press Enter.
Step 7 You are now informed about Licensing options. The recommended option is to run the FlexLM daemon, which is provided with Cisco EMF. Your other option is to use an existing FlexLM daemon you already have running on your system.
Step 8 To use the FlexLM daemon provided with Cisco EMF, type y, then press Enter. You are asked if you have a valid license file.
Step 9 Press Enter if you have a valid license file available on your network. Note, this is always true when you are installing Cisco EMF for the first time as an evaluation license comes with the product. You are asked to type in the full name, including the path, of the license file.
Step 10 To use an existing FlexLM daemon running on your system, type n, then press Enter.
Step 11 You are asked to enter the location of the license file. For example, the evaluation license file DEMO30.lic can be found on the Cisco EMF product CD at /cdrom/cdrom0. Type in the location, then press Enter. Your choice is displayed and you are asked to confirm that the location is correct. Type y, then press Enter to proceed, or type n, then press Enter to correct the path.
Step 12 The installation process starts. This process takes several minutes. A message informing you the Cisco EMF Server Package installation completed satisfactorily is displayed.
Step 13 Once the installation is complete, type eject.
The Cisco EMF product CD is ejected from the CD-ROM drive.
Step 14 Remove the Cisco EMF product CD from the CD ROM drive.
Step 15 If a valid license file was supplied, you can now start the Cisco EMF Server as described in the "Starting Cisco EMF on a Server or Client" section.
The following steps are only relevant when you select a Cisco EMF Client installation.
Step 1 After selecting the Client installation option, you are asked where the Cisco EMF Client software should be placed. The default location provided is /opt/cemf.
Step 2 If the default installation location is acceptable, press Enter.
Step 3 When the installation directory is set, you are asked to specify the hostname of the system where the Cisco EMF Server is installed.
Step 4 Press Enter to accept the supplied default, or type in the relevant hostname, then press Enter.
Step 5 You are asked to confirm that the hostname is correct. Press Enter to accept the displayed hostname. Otherwise, type n, then press Enter if you wish to change the displayed hostname.
Step 6 The Server hostname and corresponding IP address are displayed. If they are correct, press Enter. Otherwise, type n, then press Enter if you want to change these values.
Step 7 The installation process now starts. This process takes several minutes. A message telling you the Cisco EMF Client Package installation completed satisfactorily is displayed.
Step 8 Once the installation is complete, cd out of the /cdrom/cdrom0 directory, then type eject.
Step 9 Remove the Cisco EMF product CD from the CD ROM drive.
Step 10 The Cisco EMF Client can now be started as described in the "Starting Cisco EMF on a Server or Client" section.
This section describes ObjectStore related installation options.
Step 1 During the Cisco EMF installation process, you are asked if ObjectStore needs to be installed. Type y, then press Enter.
Step 2 You are asked if you want to store the databases in an ObjectStore file partition.
Step 3 Type n, then press Enter to accept the default. If you wish to configure ObjectStore differently, contact Cisco Customer Support. Type y, then press Enter.
Step 4 You are asked where to place the database files. Press Enter to use the default /opt/cemf/db or type in the relevant path, then press Enter.
Step 5 You are asked to confirm the location of the directory where the ObjectStore transaction log file will be placed. Press Enter to accept the default directory.
You return to the Cisco EMF installation process (refer to the "Installing Cisco EMF" section.
Step 1 You are asked if ObjectStore should be installed. Type n, then press Enter.
Step 2 You are asked to specify where ObjectStore is currently installed. Type in the path to the directory that contains your Object Store Installation, then press Enter (for example, the path should specify down to the /opt/ODI/OS5.1 level).
Step 3 The directory you specified is displayed and you are asked to confirm if it is correct. Press Enter if it is correct.
The system checks the specified directory for an installation of ObjectStore. A message is displayed informing you if a valid or invalid version of Object Store has been discovered.
Step 4 When a valid version is found, you are asked to confirm the location of the directory where the ObjectStore database files are to be placed. Press Enter to accept the default directory.
Step 5 You are asked to confirm the location of the directory where the ObjectStore transaction log file is to be placed. Press Enter to accept the default directory.
You return to the Cisco EMF installation process (refer to the "Installing Cisco EMF" section.)
A message is displayed informing you if a valid or invalid version of Object Store has been discovered.
If a valid version is found, you are asked if you want to store the databases in an ObjectStore file partition. If an invalid version of ObjectStore is discovered, the installation process is aborted and you are asked to remove the invalid version of ObjectStore.
Step 1 Type n, then press Enter to accept the default. If you wish to configure ObjectStore differently, contact Cisco Customer Support. Type y, then press Enter.
Step 2 You are asked where the database files are to be placed. Press Enter to use the default /opt/cemf/db directory, or type in the relevant path, then press Enter.
Step 3 Press Enter to accept the default directory.
You return to the Cisco EMF installation process (refer to the "Installing Cisco EMF" section.)
All Cisco EMF processes are automatically stopped and deinstalled when the deinstallation script is run. If you are deinstalling versions of Element Managers or Cisco EMF systems installed on versions of Cisco EMF prior to Version 3.0, you must use the cemfinstall and cemfload scripts, as detailed in the "Deinstalling Cisco EMF and Element Manager Packages Installed Prior to Version 3.0" section.
Step 1 As superuser (su), login to the machine where Cisco EMF is installed.
Step 2 Ensure that any installed Element Managers have been removed. To remove any Element Managers, refer to the "Removing an Element Manager" section.
Step 3 Deinstall Cisco EMF. From the command line prompt, type:
host# <CEMF_ROOT>/bin/cemfinstall -remove
Step 4 From the displayed list, select the package you want to deinstall.
You are notified that the deinstallation is about to take place.
If you proceed with the deinstallation, the screen scrolls through the software being deleted and the following message is displayed:
Removal of <package> was successful.
The following steps assume Cisco EMF has already been installed and that Cisco EMF is already running. For convenience, all examples assume Cisco EMF has been installed in the /opt/cemf directory.
The cemfinstall installation script is provided with the Cisco EMF platform to install and remove Element Managers. The script is found on the Cisco EMF product CD or in the <CEMF_ROOT>/bin directory. You can obtain help for cemfinstall by typing <CEMF_ROOT>/bin/cemfinstall -help, where <CEMF_ROOT> is the directory Cisco EMF is installed.
To start an installation of an Element Manager, proceed as follows:
Step 1 As superuser (su), login to the machine where Cisco EMF is installed.
Step 2 Insert the Element Manager product CD.
Step 3 Change to the directory where you want the Element Manager installed.
Step 4 Run the install script ./cemfinstall
ERROR: You must be root to run this Script error message is displayed. Login as superuser (su), then run the cemfinstall script again.
Step 5 A menu listing the installation options is displayed. Select the Element Manager installation you desire, then press Enter.
To quit the installation process, type Q, then press Enter.
**Already Installed** is displayed beside the option and the option to install that package is removed.
ERROR: CEMF is not running error message is displayed. Start Cisco EMF, then run the cemfinstall script again.
Step 6 The script starts installing the Element Manager. You are asked if you are sure you want to install the package. Press Enter to confirm and to continue to install the package.
Information is displayed detailing the progress of the installation. Once the installation is finished, you are informed that the installation was successful.
To start the deinstallation of an Element Manager, proceed as follows:
Step 1 As superuser (su), login to the machine where Cisco EMF is installed.
Step 2 Change directory to the <CEMF_ROOT>/bin directory. From the command line prompt, type:
host# cd <CEMF_ROOT>/bin
where <CEMF_ROOT> is the directory Cisco EMF is installed.
Step 3 Display a list of all of the Cisco EMF packages, type:
host# ./cemfinstall -show
Step 4 Run the deinstall script ./cemfinstall -remove. From the displayed list, select the package you want deinstalled, then press Enter.
To quit the installation process, type Q, then press Enter.
Step 5 The script starts removing the selected Element Manager. You are asked if you are sure you want to remove the package. Press Enter to confirm and to continue to remove the package.
Information is displayed detailing the progress of the deinstallation. Once the deinstallation is finished, you are informed that the deinstallation was successful.
To start the deinstallation of an Element Manager, proceed as follows:
Step 1 As superuser (su), log onto the machine where Cisco EMF is installed.
Step 2 Change directory to the Cisco EMF bin directory. From the command line prompt, type:
host# cd <CEMF_ROOT>/bin
where <CEMF_ROOT> is the directory Cisco EMF is installed.
Step 3 Find the name of the Element Manager package you wish to remove. From the command line prompt, type:
host# pkginfo
Step 4 A list of the packages on the current system are displayed in the format:
PackageType PackageName PackageDescription
Step 5 Run the cemfload script with the removal option. From the command line prompt, type:
host# ./cemfload -remove <PackageName>
where <PackageName> is the name of the package you wish to remove (for example, ./cemfload -remove myEM).
If you are not logged in as superuser, the following error message is displayed:
ERROR: You must be root to run this Script.
Step 6 Login as superuser, then run the cemfload script again.
If Cisco EMF is not running, the following error message is displayed:
ERROR: CEMF is not running.
Step 7 Start Cisco EMF, then run the cemfload script again.
Step 8 The script starts removing the desired Element Manager. You are asked to confirm the removal of the package. Press Enter to confirm and to continue to deinstall the package.
Step 9 If you made a mistake with the package name, type n, then press Enter. The deinstallation process stops and you can restart it at a later time.
Information is displayed detailing the deinstallation progress. Once the deinstallation is finished, the following message is displayed:
## Program Finished
This section describes how to administer Cisco EMF workstations.
The Cisco EMF software on a Server or Client workstation is automatically started during system boot-up. To start this software at other times:
Step 1 Login as superuser (su).
Step 2 From the command line prompt, type:
host# <CEMF_ROOT>/bin/cemf start
where <CEMF_ROOT> is the directory Cisco EMF is installed.
The Cisco EMF processes start.
The Cisco EMF software on a Server or Client is stopped during system shut down. To stop this software at other times:
Step 1 Quit any running Cisco EMF Launchpad sessions.
Step 2 Login as superuser (su).
Step 3 From the command line prompt, type:
host# <CEMF_ROOT>/bin/cemf stop
where <CEMF_ROOT> is the directory Cisco EMF is installed.
The Cisco EMF processes stop.
To check the status of Cisco EMF, type:
host% <CEMF_ROOT>/bin/cemf query
where <CEMF_ROOT> is the directory Cisco EMF is installed. When Cisco EMF is active, the system responds with a list of running processes. When Cisco EMF is inactive, the system displays the Cisco EMF system not running message.
To log on to Cisco EMF and start the Client application, type:
host% <CEMF_ROOT>/bin/cemf session
where <CEMF_ROOT> is the directory Cisco EMF is installed.
To update the Cisco EMF evaluation license currently in use do the following:
Step 1 Upon receiving the Cisco EMF permanent license key file (CEMF3license.lic) by email, you must place the CEMF3license.lic file in the <CEMF_ROOT>/config/license directory, where <CEMF_ROOT> is the Cisco EMF installation directory on the server.
Step 2 On the Cisco EMF server workstation, invoke the licenseCEMF script to install and read the Cisco EMF permanent license key file by typing:
host# cd <CEMF_ROOT>/bin/cemf
host# ./licenseCEMF -file <CEMF_ROOT>/config/license CEMF3license.lic
When you start to use the permanent license, after having used a evaluation license, all existing configuration and databases are preserved.
The new license key is automatically configured properly for this system (if it happened to be an evaluation key) and is read in so that it is immediately in effect. Therefore, you are able to extend a running system, that is, you need not wait until the evaluation period has expired before updating/extending the license.
Backups must be located at the same level as the Cisco EMF installation directory but not within it (for example, if the <CEMF_ROOT> directory is /opt/cemf, then the backup must be done to the /opt/cemfBackup directory). This method precludes you from losing a backup on deinstallation as the backups are located outside the Cisco EMF installation directory.
Cisco EMF is capable of representing large networks, and, as a result, databases become very large. Care must be taken to ensure that enough disk space is available. It is recommended that backups are stored on separate disks.
Backups should be done under the following circumstances:
1. Before a new Element Manager is installed. It is possible that the Element Manager may corrupt the existing configuration.
2. Before installing a patch to already installed Cisco EMF or Element Manager packages.
3. Before installing an upgrade to already installed Cisco EMF or Element Manager packages.
4. Before deinstalling an Element Manager (this is optional).
5. On a daily basis.
It is recommended that:
The Cisco EMF backup facility only backs up the Cisco EMF databases, plus any additional files that need to be kept synchronized with these databases. It does not back up the entire Cisco EMF installation. This is left as a task for the system administrator.
The <CEMF_ROOT>/bin/cemf backup command has the following format:
backup [-l <backup_dir>] [-t] [-h]
| Parameter | Description |
|---|---|
-l <backup_dir> | Specifies the directory in which the backup output is written. The default location is: /opt/cemfBackup. |
-t | Specifies that old backups should be archived to tape. The default is not to archive to tape. |
-h | Prints out the backup command usage message. |
Cisco EMF database backups can be performed manually by typing
<CEMF_ROOT>/bin/cemf backup, where <CEMF_ROOT> is the directory Cisco EMF is installed. This backup operation can be automated by setting up a cron job to perform the backups on a regular basis (for example, if a backup must be made every day at 3:00 a.m., the following line should be added to the cron job:
0 3 * * * <CEMF_ROOT>/bin/cemf backup
It is recommended that daily back ups are made. As well as backing up databases, all configuration files are backed up. The configuration files to be backed up are specified in the <CEMF_ROOT>/config/data/filesToBackup file.
Complete database back ups are carried out on a weekly basis (Sunday to Saturday) in a date stamped directory under <CEMF_ROOT>/../cemfBackup. The date stamp format is <mm>-<dd>-<yyyy> and represents the Sunday at the start of the week in which the first back up was taken (for example, 04-19-1998). A new directory is created each Sunday and a full back up is taken (all other days are incremental backups.)
No more than two backup directories are present on the machine at any time. You can choose to have the oldest backups either deleted from the system entirely or backed up to a tape device. The default backup does not go to tape. If you want to backup to tape, you have two options:
1. specify the -t option with the backup command each time it is invoked.
2. Permanently change the default device (refer to Step 4).
By default, the oldest backups (those over two weeks old) are deleted, however, they can be tarred to a tape as follows:
Step 1 Using a text editor, open the <CEMF_ROOT>/config/scripts/backup script file.
Step 2 Locate the following line:
archiveToTape=0
Step 3 Replace it with:
archiveToTape=1
Step 4 By default, the /dev/rmt/0 tape device is used. If this must be changed, in the <CEMF_ROOT>/config/scripts/backup script file, locate the following line:
tapeDevice= /dev/rmt/0
Step 5 Replace it with appropriate device. For example:
tapeDevice= /dev/rmt/i
By default, the backup utility handles databases that have a collective storage requirement of twenty Gigabytes. This limit may be changed by modifying the BackupVolumes configuration variable in the <CEMF_ROOT>/config/init/dbRestore.ini file. By default, this variable is set to 10. A volume is equal to the maximum file size which is two Gigabytes. If the collective total is greater than two Gigabytes, it is split into volumes as shown in the following example:
backupRecord - The incremental record file day0.1- Backup image file for day 0 (Sunday) day0.2- Backup image file for day 0 (Sunday) day0.3- Backup image file for day 0 (Sunday) day0.4- Backup image file for day 0 (Sunday) day0.5- Backup image file for day 0 (Sunday) day0.config- Tarfile of config files for day 0 day1.1- Backup image file for day 1 (Monday) day1.2- Backup image file for day 1 (Monday) day1.3- Backup image file for day 1 (Monday) day1.4- Backup image file for day 1 (Monday) day1.5- Backup image file for day 1 (Monday) day1.config- Tarfile of config files for day 1
Cisco EMF should be stopped prior to configuring and restoring databases. Ensure the backup being restored is consistent with the existing packages. If a new package was installed since the selected backup was made, the system may be left in an inconsistent state when the restoration proceeds. In these situations, you may want to do one of the following:
1. Deinstall the packages installed since the selected backup was made. Note, you will lose all of the data associated with these packages.
2. If a backup was made after the current packages were installed, use this backup and then do a restore.
The <CEMF_ROOT>/bin/cemf restore command has the following format:
restore -t <mm-dd-yyyy> [-d <db1> [<db2>...] [-l <backup_dir>] [-x <tape_drive>][-h]
| Parameter | Description |
|---|---|
-t <mm-dd-yyyy> | Specifies when the backup was made. |
-d <db1> | Specifies the database(s) to be restored. |
-l <backup_dir> | Specifies the directory in which the backup is located. The default location is: <CEMF_ROOT>/../cemfBackup. |
-x <tape_drive> | Specifies the tape device on which the backups located. The default is /dev/rmt/0. |
-h | Prints out the restore command usage message. |
In previous Cisco EMF releases, multiple database restoration groups were specified in the <CEMF_ROOT>/config/data/dbGroups file. In this release, dbGroups is now a directory and each file added to this directory specifies a database restore group. Each file contains a list of whitespace (space, tab, or newline) separated databases to specify a restore group. When an Element Manager is installed, a dbGroups file should be placed in this directory. This file should contain all database groupings specific to that Element Manager.
If one database in a group is restored, all databases in that group are restored. In addition, any cross-database pointers are detected, and any databases they point to are also restored. This is done to ensure the databases remain synchronized.
To restore a database, type <CEMF_ROOT>/bin/cemf restore -t <mm-dd-yyyy> where <CEMF_ROOT> is the directory Cisco EMF is installed and <mm-dd-yyyy> is the date the backup was created. For example,
host% <CEMF_ROOT>/bin/cemf restore -t 11-19-1999
restores all databases using the backup created on 19 November 1999. If the back up cannot be found on the system, the required tape should be used to continue the restore.
Posted: Mon Jan 10 09:02:00 PST 2000
Copyright 2000©Cisco Systems Inc.