Cisco Element Management System Installation and Configuration Guide, 3.2 Service Pack 7
Before You Start Your Installation
Downloads: This chapterpdf (PDF - 393.0KB) | Feedback

Before You Start Your Installation

Table Of Contents

Before You Start Your Installation

Installation Workflow

Installation Checklist

Mounting a Remote CD-ROM Drive

cemf install Command

Types of Deployment

Server and Client Deployments

Cisco EMF Server

Cisco EMF Client

Cisco EMF Presentation Server

Licensing

Cisco EMF Licenses

Acquiring a Permanent License

Updating an Evaluation License

Upgrading a License Key Without Stopping Cisco EMF

Configuring Your System

Guidelines for Disk Layout

Hard Drive Partitioning

Suggested Layout for File System Partitions for a Small to Medium Deployment

Database Setup Example for a Large Deployment

Configuring an X-Client

Configuring Your System for Cold Standby


Before You Start Your Installation


There are some general items you should take into consideration when preparing for installing an Element Manager System (EMS) .

The installation workflow and checklist provide a quick reference to be used prior to starting installation and uninstallation of new software and new EMS packages on a Cisco EMF Server and a Cisco EMF Client. Refer to the other sections in this Guide for full details.

You must have a license to install and use the EMS.

You need to configure your system correctly before you start a Cisco EMF installation. This chapter also describes how to optimize your system after the EMS is installed and includes examples, best practices and tips.

This chapter comprises the following details:

Installation Workflow

Installation Checklist

Mounting a Remote CD-ROM Drive

cemf install Command

Types of Deployment

Server and Client Deployments

Cisco EMF Server

Cisco EMF Client

Licensing

Cisco EMF Licenses

Acquiring a Permanent License

Updating an Evaluation License

Upgrading a License Key Without Stopping Cisco EMF

Configuring Your System

Guidelines for Disk Layout

Database Setup Example for a Large Deployment

Configuring an X-Client

Configuring Your System for Cold Standby

Installation Workflow

Installing Cisco EMF requires the following:

1. Check that you have everything you need before you start the installation. (See Installation Checklist.)

2. If your system does not have its own CD-ROM drive, you can mount the installation CD on a remote system. (See Mounting a Remote CD-ROM Drive.)

3. Configure your system before you start the installation. (See Configuring Your System.)

4. Installation—Install the Cisco EMF software according to the instructions in one of the following sections:

Installing a Cisco Element Manager Server, page 2-1

Installing a Remote Client, page 2-9

Installing Service Pack 7, page 2-11

Installing Integration Packages, page 2-12

5. Begin working with Cisco EMF. (See Administering Cisco EMF Workstations.)

6. Other chapters in this guide describe the system administration tasks. (See Organization and Use, page -xviii.)

Installation Checklist

Before you start the installation you must have the required hardware and software. You need to:

1. Check for latest information in the Release Notes on Cisco.com, http://www.cisco.com/en/US/products/sw/netmgtsw/ps829/prod_release_notes_list.html.

2. Determine whether your network requires a small deployment on a single workstation, or a larger deployment in a multi-site Client/Server configuration.

3. Determine the installation type (Server, or Client, or Patch). (See Types of Deployment.)

4. Determine whether you intend to run RME co resident with the Cisco Element Manager Server. (See Installing Integration Packages, page 2-12.)

5. Check the minimum hardware requirements.

a. The size of a large or standard installation depends on the technology being managed. A basic Cisco Element Manager Server installation requires 2GB of free disk space in a file system (for example /opt) and an appropriate amount of free disk space for database files.

b. The Cisco-Sun hardware reference configurations for Cisco Element Managers are detailed in http://www.sun.com/oem/cisco/ Do not order hardware until you have referred to this.

c. The Cisco CNS Configuration Engine you require:
Cisco CNS 2100 Series Intelligence Engine v1.2.2 or v1.2.3 or v1.3.

6. Partition hard drives on the workstation (See Hard Drive Partitioning.)

7. Check that you have all the necessary software:

a. Locate the Cisco EMF v3.2 SP4 CD#1 and CD#2.

b. If you are installing Resource Manager Essentials, locate the CiscoWorks Common Services 2.2CD and the RME CD. You will need:
CiscoWorks for Solaris and Resource Manager Essentials 3.5 for Solaris
or
CiscoWorks for Windows and Resource Manager Essentials 3.5 for Windows.

c. X client software—Reflection X v8.0.2 and Exceed v6.1 are supported for use with Cisco EMF.


Note OpenWindows is not supported on Cisco EMF.


8. Obtain Root, or superuser (su) password and privileges from your UNIX system administrator.

By default Cisco EMF is installed with one default user account for the system administrator. The default username is admin and default password admin.


Caution Cisco recommends that for security purposes you change the administrator password upon installation. Also, for other users, Cisco strongly recommends that you set up individual user accounts through the Access Manager. (See Chapter 10, "Access Control")

9. Have a valid license key file available on the system (See Licensing). If you do not have one you may still continue the installation, but you will not be able to start the Cisco EMF Server.

To get a Temporary License (for evaluation) or a Permanent License, you need:

a. Product Authorization Key (PAK) number provided on the Cisco EMF product CD sleeve.

b. 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.

c. 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.

10. Will you use the FlexLM daemon installed with Cisco EMF , or an existing FlexLM daemon already running on the system or another machine on the network?

11. Determine the hostname of the machine where you are installing the default Cisco EMF Server.

12. 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.

13. Determine the hostnames of the machines where you are installing other Cisco EMF Servers.

14. Know the IP address of the default Cisco EMF Server.

15. Know the IP addresses of other Cisco EMF Servers.

16. There is no requirement for Domain Name System (DNS) to be configured.


Note Cisco EMF installs correctly if a workstation does not use DNS.


17. Determine the directory where the Cisco EMF software will be installed, (recommended path is /opt/cemf).

18. Cisco EMF databases should be stored on a separate disk from the Cisco EMF Server. Determine where these databases will be stored.

Determine if the databases are to be installed in a RAW File System (RAWFS) partition.

If the database is in RAWFS the backup location can be UNIX File System (UFS) or RAWFS.


Note If you have a large deployment, the databases should be placed in a raw partition. This gives the benefit of improved Cisco EMF performance and also allows databases to grow larger than 2GB in size. When installing Cisco EMF you will be prompted if you wish to use a raw partition. See RAW File System (RAWFS), page 2-7.


19. Determine where the backups will be stored. (See Database Setup Example for a Large Deployment.)

You need more disk space available for the database backup than the expected database partition size.

20. Remove any versions of ObjectStore. (See Configuring an ObjectStore Installation for Cisco EMF, page 2-5.)

Mounting a Remote CD-ROM Drive

The installation program and installation software are found on the Cisco EMF System v3.2 CD#1 and CD#2.

To install software onto a system that does not have its own CD-ROM drive, mount the CD on the remote system and 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 CD into the CD-ROM drive on the remote host.

Step 2 On the remote host, log in as superuser (su).

Step 3 On the remote host, export the CD-ROM device as follows:

a. Check the Volume Manager is running, enter:

/usr/bin/ps -ef | grep vold

If the Volume Manager is running, you see a message similar to:
root 591 1 0 Feb 26 ? 0 :01 /usr/sbin/vold

b. If the Volume Manager is not running, start the Volume Manager, enter:
/etc/rc2.d/S92volmgt start

c. When they are not already running, start the NFS related daemons. At the command line prompt, enter:

/usr/lib/nfs/nfsd 8
/usr/lib/nfs/mountd

d. Share the mount point from the remote host. At the command line prompt, enter:

share -F nfs -o ro /cdrom/cdrom0

e. Verify that this host has made the CD-ROM drive accessible. At the command line prompt, enter:

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, enter:

mkdir /mnt/CEMFmnt

b. Mount the remote directory. At the command line prompt, enter:

mount -r <remote-host> : /cdrom/cdrom0 /mnt/CEMFmnt

where <remote-host> is replaced by the hostname of the remote device.

The contents of the Cisco EMF v3.2 SP4 CD are now visible under the /mnt/CEMFmnt mount point.


cemf install Command


Note The cemf install command is called cemfinstall on the CD-ROM.


With Cisco EMF and Patch 1 or later patches installed, the <CEMF_ROOT>/bin/cemf command is used to perform many administrative operations on Cisco EMF.

<CEMF_ROOT> is the directory in which Cisco EMF is installed.


Note You must be logged in as the superuser (su) to use the installation program.


The cemf install command parameters detailed in Table 1-1 are used when the EMS is installed and uninstalled. You need not enter the entire parameter, you can just specify the first letter of the parameter's name. For example, cemf install -h and cemf install -help can both be used to display help information.


Note Other cemf install command parameters are available in Cisco EMF v3.0. They are not documented here, but if you prefer they can still be used. These options are superseded by the commands detailed in Table 1-1.


Table 1-1 cemf install Command Parameters 

Parameter
Description

show

Shows the installed packages.

remove [forupgrade] [skipportcheck | skipallchecks]

Displays a menu from which you choose a package to remove. forupgrade specifies that a new version of the EMS will be installed later. skipportcheck and skipallchecks are used if you have problems during EMS installation or uninstallation.

help

Displays help.

-choice <choice>

Choose the <choice> menu option. For example, cemf install -c 3 chooses the third menu option.

-echoonly

Does not run (only echoes) commands.

-yestoall

Answer Yes to all cemf install script questions

-o <option>

Allows you to customize cemf install by prepending the <option> argument to any Cisco EMF commands invoked by cemf install. The <option> is therefore specific to the type of installation or uninstallation being performed.


Types of Deployment

This section explains the types of deployments and contains the following information:

Server and Client Deployments

Cisco EMF Server

Cisco EMF Client

Server and Client Deployments

The EMS can be deployed with a server and clients to use the power of multiple machines. Four types of deployment are available:

Server—see Figure 1-1

Server and Clients—see Figure 1-2. A client can be local or remote. A local client is one that is running on the server itself. A remote client is running on a separate workstation.

Client—see Figure 1-3. A client connected to multiple servers, this is known as client session switching, and allows a user to be able to access multiple servers at remote sites through a single client machine.

Presentation Server—see Figure 1-4. Cisco EMF can also be accessed through running the user interface on either the server or a remote client machine and displaying back to a different machine using the X protocol. A common configuration for this display machine is a PC running X emulation software, see "Configuring an X-Client" section.


Note Reflection X v8.0.2 and Exceed v6.1 are supported for use with Cisco EMF.


In an Element Manager System with Resource Manager Essentials (RME), RME can be installed on a Solaris workstation or on a Windows NT PC. The Solaris version can be installed on the same workstation as the EMS, this is a co-resident installation.


Note Currently, an RME co-resident installation is supported only for small and medium scale deployments, that is upto 200 chassis, and with RME installed on a separate disk. See Guidelines for Disk Layout.


Figure 1-1 Server Deployment

Figure 1-2 Server/Client Deployment

Figure 1-3 Client and Multiple Server Deployment

Figure 1-4 Server/Presentation Server/X Client Deployment

Cisco EMF Server

Every EMS deployment must have a Cisco EMF server installed. Processes on the server keep track of the current state of the network model, user access, events etc. The ObjectStore database system will be installed on this machine.


Note The server includes all client application graphical user interfaces (GUIs).


If you have an EMS co-resident with RME, the co-resident installation is on the Cisco EMF server.

The Cisco-Sun hardware reference configurations for Cisco Element Managers are detailed in http://www.sun.com/oem/cisco/.

Cisco EMF Client

An EMS deployment may have the client installation on separate workstations, which are used to run applications to access objects on the server, see Figure 1-2 or a single client connected to multiple servers, see Figure 1-3.


Note Client session switching is an option available when starting a user session on a client or a server. See Starting a User Session, page 5-6.


A client installation contains only those parts of Cisco EMF necessary for a user session. This user session communicates back to the server when required to retrieve management information. The GUI runs on the client machine, which frees system resources on the server machine to process network information.

The 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.


Note The server installation process also installs all of the files required to establish a client to server session on a single machine. Therefore, you can install the entire Cisco EMF including both server and client functionality, on the same machine by installing just the server system. (See Figure 1-1.) Thereafter, you can install the client systems on additional machines as required. (See Figure 1-2.)


Cisco EMF Presentation Server

A Cisco EMF presentation server is a workstation with a Cisco EMF client software installation used solely for the purpose of hosting remote X clients. The workstation is generally of a higher specification than a standard client workstation. The presentation server is used to host multiple remote Cisco EMF user sessions, either from PCs running X servers, or from other Solaris boxes which do not have the Cisco EMF client software installed. This is the most cost effective means of achieving large numbers of end users.

The presentation server user session communicates back to the Cisco EMF server when required to retrieve management information. The X based traffic is processed by the presentation server.

This type of deployment differs from the deployment where the remote user session is supported directly on the Cisco EMF server. In that case fewer users are possible as the server needs to process all the X-based traffic as well as the Cisco EMF traffic. Client software on the presentation server means you need not mount files across a network. Network traffic occurs only when the client requires more data from the server. The Cisco EMF GUI runs on the client machine, which frees system resources on the server machine. This means that a higher number of remote clients can be supported. On a heavily loaded Cisco EMF server, Cisco recommends 10 users per presentation server. So five presentation servers will be required for a 50 user deployment (30 active, 20 inactive). For a lightly loaded server, the presentation server can support up to 20 users.

Licensing

This chapter describes the licensing required for an EMS.

This section contains the following information:

Cisco EMF Licenses

Acquiring a Permanent License

Updating an Evaluation License

Upgrading a License Key Without Stopping Cisco EMF

Cisco EMF Licenses

Installations of Cisco EMF are subject to license control. The EMS requires a Cisco EMF license to run.

When you initially receive the EMS, an evaluation license is provided with Cisco EMF. Upon installing Cisco EMF from the 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 Cisco EMF.

Cisco EMF uses the FlexLM license manager, which is on the Cisco EMF CD-ROM. If you need to integrate with an existing FlexLM license manager, refer to the procedures documented in the FLEXlm End User Manual. This manual is available at <CEMF_ROOT>/flexlm/htmlman/user.


Note During the evaluation period, every time the Cisco Element Manager Server is started, a message is displayed indicating the time remaining before the evaluation key is due to expire. If the EMS is running when the evaluation license runs out, all processes stop. Cisco EMF will not restart when the evaluation license has expired.

If Cisco EMF is running and its processes stop, you can view the details of any licensing problem, enter more <LOGSDIR>/sysmgr.log, where <LOGSDIR> is the directory chosen at install time. During installation you can choose to place the log files into a non-standard location, the default location is <CEMF_ROOT>/logs.


When you start to use the permanent license on the same hardware after using an evaluation license all existing configuration and databases are preserved.


Note You need a valid license key available on the system to start the Cisco EMF Server. If you do not have one you may still continue the installation, but you will not be able to start the Server.


If you have problems with licensing, see Licensing, page 18-25 in the Troubleshooting chapter.

Acquiring a Permanent License

To acquire the required permanent license key file, you must do the following:


Step 1 Navigate to the Cisco Software Registration site:

http://cco.cisco.com/pcgi-bin/Software/FormManager/formgenerator.pl

Step 2 Click 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.


Note As the permanent license key is returned to you by email as an attached file, it is imperative that you provide your correct email address.


a. Select the version of Cisco EMF you are licensing in the Version number field.

b. 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 CD sleeve.

c. Specify the hostname of the server where Cisco EMF is installed.

You can obtain the server's hostname by typing the hostname command at the server's command line prompt.


Caution The server hostname must not include a period ( .). The only occurrence where a period is allowed in a server hostname is when it precedes a file extension name, for example .lic

d. Specify the host ID (a hexadecimal string that identifies the system, not the IP address) of the server where Cisco EMF is installed.

You can obtain the server's host ID by typing the hostid command at the server's command line prompt.


Note If you make a mistake entering any information you can change details in a specific field. To clear the details from all fields, click Clear Form.


Step 4 Please also provide answers to the questions at the end of the form, then click Submit Form.

The License Request form is submitted. The permanent license key file is returned to you as an email attachment.

Step 5 See "Updating an Evaluation License" for instructions on how to replace an evaluation license with the permanent license.


Updating an Evaluation License

To update the evaluation license currently in use, for example if you wish to extend an evaluation license, or convert an evaluation system to a proper installation with a permanent license, or license additional Cisco EMF products, do the following:


Step 1 Upon receiving the new license key file <license>.lic by email, you must place the <license>.lic file in the <CEMF_ROOT>/config/licenses directory, where <CEMF_ROOT> is the EM installation directory on the server.


Caution The server hostname must not include a period ( .). The only time a period is allowed in a server hostname is when it precedes the file extension name, .lic. The license filename must be in the form <filename>.lic. If there is no filename extension ( .lic) or multiple extensions then this can cause problems. See Licensing, page 18-25 for more license troubleshooting information.

Caution You must remove expired license keys from the <CEMF _ROOT>/config/licenses directory before you install and read the new license.

Tip If the license key file you plan to replace has not expired, you may want to copy the file to a temporary location so that it is available in the event that there are problems with the new file.


Step 2 On the Cisco Element Manager Server, run the cemf license script to install and read the permanent license key file, enter:

host# cd <CEMF_ROOT>/bin
host# ./cemf license -file <CEMF_ROOT>/config/licenses/<license>.lic

When you start to use the permanent license, after having used an 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.


Note License keys can be updated at any time and all existing databases will be preserved.



Note Evaluation License keys are available for evaluation periods of 30, 60 or 90 days. These evaluation license keys are valid for 30, 60 or 90 days from the date the software is installed. Therefore if an evaluation license key is extended the extended period is always referenced to the software installation date. For example, if a 30 day license key is used for software installed on June 20th the software will run until July 19th. If the evaluation period is extended using a 60 day key, then the new license key will expire on August 17th (60 days after the software was installed).



Upgrading a License Key Without Stopping Cisco EMF

To update a license key, proceed as follows:


Step 1 Ensure that your new key is valid in terms of machine details and expiry dates. If the key is not valid then the following procedure will close down Cisco EMF.

Step 2 Copy the new key into <CEMF_ROOT>/config/licenses.

Step 3 Remove the old license key from this directory. This is critically important, especially if a DEMO license is being upgraded to a full license.

Step 4 Enter <CEMF_ROOT>/flexlm/lmreread -c <CEMF_ROOT>/config/licenses. This will reread the license keys in the specified directory and use the new key from now on. Cisco EMF will continue running as normal assuming the new key is valid.


Configuring Your System

This section explains how to configure your system before you start an EMS installation. It also describes how to optimize your system after the EMS is installed.

This section contains the following information:

Guidelines for Disk Layout

Hard Drive Partitioning

Database Setup Example for a Large Deployment

Configuring an X-Client

Configuring Your System for Cold Standby

Guidelines for Disk Layout

Each of the following components should be installed on a separate disk:

Disk Drive
Components

Disk 1

Cisco EMF and Solaris Operating System

Disk 2

Solaris Swap

Disk 3

Cisco EMF databases

Disk 4

ObjectStore Transaction Log

Disk 5

RME, if you are planning a co-resident installation



Note Using multiple disk drives to store the databases helps avoid I/O bottlenecks and substantially aids in the performance of the software.


Hard Drive Partitioning

By default, the Cisco EMF software is installed with standard UNIX File System (UFS) partitions (partitions with readable directory structures.) However, RAW File System (RAWFS) partitions (partitions without readable directory structures) offer the following advantages over UNIX File System partitions:

The capability to span multiple hard disks

The option of having databases over 2GB in size

You must install using RAWFS if your EMS is likely to have databases greater than 2GB.


Note Cisco EMF uses ObjectStore for its databases. ObjectStore is installed with Cisco EMF.


Suggested Layout for File System Partitions for a Small to Medium Deployment

Configuring an ObjectStore Installation for Cisco EMF, page 2-5 details how the ObjectStore installation should be configured for Cisco EMF and suggests performance enhancements for file system partitions.

Table 1-2 gives the mount point and size for creating file system partitions for a small to medium deployment, that is upto 200 chassis.


Note You may want to setup the name of each mount point to include the disk number, for example disk1/var or disk3/opt/cemf/db.


Table 1-2 Mount Point and Sze for File System Partitions for Small to Medium Deployments

Disk
Components
Mount Point
Size

Disk 1 (9GB)

Cisco EMF and Solaris Operating System

/(root)

512MB

   

<swap>

2GB

   

/var

1GB

   

/usr

4GB

   

/home

Remainder

Disk 2(9GB)

Solaris Swap1

<swap>

2GB

   

/opt

Remainder

Disk 3 (9GB)

Cisco EMF databases

/opt/cemf/db

Total

Disk 4 (9GB)

ObjectStore Transaction Log

The transaction log should be placed on UFS to improve performance.

/opt/trx

Total

Disk 5

RME, if you are planning a co-resident installation. Refer to the RME documentation for recommended disk size.

/opt/RME

Total

1 It is recommended that you have the same size Swap space as RAM.



Note Currently, an RME co-resident installation is supported only for small and medium scale deployments, that is upto 200 chassis, and with RME installed on a separate disk.


Database Setup Example for a Large Deployment

This section and Table 1-3 give an example database layout for a large deployment, that is more than 200 chassis, and with RME installed on a separate disk.

The two spare partitions should be changed to be RAID 0+1 to give maximum performance at a cost of disk space.

To get backup to work correctly with the spare partitions, links will need to be added to the databases from the default DB directory.

Table 1-3 Example Database Layout for a Large Deployment

Mount
Size
File System
Mount Option
Purpose

/opt

4 Gbytes

UFS

default

Contains the Cisco EMF installation in the default location (/opt/cemf).

/opt/trx

3 Gbytes

UFS

 

Contains ObjectStore transaction log file (/opt/trx/transact.log)

/opt/cemf/db

30 Gbytes
(4x9Gb disks or larger)

UFS - RAID5

 

Contains the Cisco EMF ObjectStore databases.

/opt/Backup

50 Gbytes

UFS - RAID5

default

Backup location/work area.


Configuring an X-Client

An X-client can be used to access the EMS deployment running on a UNIX host but displaying back onto a PC using X emulation software.

Cisco EMF has been tested to be compatible with the Reflection X Version 8.0.2 for Windows NT emulation package and Exceed v6.1.

The Reflection X package has been tested on a PC with the following recommended specification:

PII 500Mhz

16Mb video card, running 1024x768, 24-bit color resolution, 85Mhz refresh rate

128Mb system memory

100Mb network card

10GB Hard Drive (not requirement)

SoundBlaster 16 compatible audio card

Windows 2000 operating system


Note When running the EMS on a laptop using Reflection X, occasionally the dimensions of the display area of the laptop is smaller than the default dimensions of the displayed dialog.
You can use the mouse to resize the dialog, and then scroll the application to access all features or you can increase the laptop resolution to the maximum value.
On some laptops this will increase the base display size of the laptop meaning that the display itself scrolls left and right, and up and down to accommodate the new resolution.


To setup the Reflection X software, choose Settings > Windows Manager:


Step 1 Enable the following options:

Window Mode > Microsoft Windows desktop

Default local window manager > Microsoft Windows

Options > Allow remote window manager

Show icons for managed clients

Step 2 Disable the following option on the Keyboard Settings dialog:

Backspace key sends delete


Configuring Your System for Cold Standby

Network availability is an important function of a network management system where downed structures bring critical functions to a standstill, costing time and money. The Cisco EMF guidelines for network availability recommend a cold standby system where the network has a spare machine on which you would restore your last backup and which is then used as the management server, if there are problems with the primary server. This then gives the opportunity for full troubleshooting procedures to be accomplished on the faulty server.


Note When discussing a cold standby system, the two servers may be referred to as the primary server and the secondary server, or the active server and the passive server. These terms may be used interchangeably.


Figure 1-5 shows a typical cold standby scenario.

In a cold standby system, the primary Cisco EMF server runs as normal. Backups are regularly taken from this server and should a problem arise on the primary, the data is restored on the standby server, which assumes management. Failure detection on the primary server must be performed by the system administrator. The frequency of the backup is variable. More frequent backups will ensure less data loss, but this must be balanced against the interruption to service which occurs when a backup is performed; if backups are performed too frequently then system performance will be degraded.

For full details of the backup and restore procedure, see Chapter 8, "Cisco EMF Database Backup and Restore".

Figure 1-5 Cisco EMF Cold Standby

To setup a cold standby system, proceed as follows:


Step 1 Install and configure the primary server which is managing the network. This primary server has an EMS installation with all up-to-date patches.

Step 2 Install and configure the cold standby server. This server must have the identical specification as the primary server installation. This includes the EMS installation as well as the Solaris patches. The cold standby server must have the same IP address as the primary server. This is required, otherwise all the trap destinations will have to be re-configured. The cold standby server should be connected to the same network as the primary server, but should be administratively shut down. There may be access to the cold standby server on another interface.


Note If the EMS installation is co-resident with the CNS Notification Engine (C-NOTE), ensure that the cold standby server is configured for co-residency. See Configuring Co-Residency with CNS Notification Engine (C-NOTE), page 6-4.


Step 3 If any co-resident software files will need to be backed up, add these files to the filesToBackup file, located in the <CEMF_ROOT>/config/data directory. This will ensure these additional files will be saved and restored as part of the backup/restore process. See Backing Up a C-NOTE/Element Manager Co-resident Installation, page 10-7.

Step 4 The system administrator initiates a daily backup process on the primary server. The backup operation can be automated by setting up a cron job to perform backups on a regular basis. See Performing Automatic or Scheduled Backups, page 8-5.

Step 5 The network operator monitors the network for any failures on the primary server. If the decision is taken to initiate the cold standby server, bring up the secondary server and restore the latest backup from the primary server.

When restoring from a backup from the primary server, it is vitally important that the system on which the restore is being performed is identical to, or compatible with, that from which the backup was taken. In particular:

1. The major version of Cisco EMF for the secondary system being restored to must be the same or greater than the primary system the backup was taken on.

2. The Cisco EMF patch level for the secondary system being restored to should be the same or greater than the primary system the backup was taken on.

3. The same element manager packages, with compatible versions, should be present, as in the original backup. If new packages have been added since that backup was taken, they should be de-installed (remember that you will lose the data associated with these packages).

4. There must be sufficient disk space to accommodate the restored databases.

5. To successfully restore a particular backup, the restore process must have the initial, full backup, plus all incremental backups.

6. The cold standby server must have the same IP address as the primary server.

Step 6 The restore process ensures that databases will be updated with the current configuration.

If Cisco EMF or its databases on which the backup was performed have been installed in a different location to your Cisco EMF on which the restore was performed, some configuration information should be updated. This is performed automatically by the restore script.

Step 7 You can now point the clients at a cold standby server without having to uninstall the client. See Changing Default Server, page 5-11.

Step 8 You should now initiate a network re-synchronization.