Cisco Media Gateway Control Node Manager User's Guide, 2.1 - Planning and Installation [Cisco Media Gateway Controller Node Manager]

Table Of Contents

Planning and Installation

Installation Overview

Who Should Install Cisco MNM?

Planning and Installation Checklist

Task 1: Gathering Installation Software and Required Information

Installation Software

Required Information

Task 2: Determining Your Hardware Requirements

Hardware Requirements

Disk Drives and Database Storage

Task 3: Ensuring That Network Devices Have the Correct Software

Task 4: Ensuring That the Sun Solaris 8 Operating System Is Installed

Task 5: Planning and Executing Hard Drive Partitioning

Partitioning Guidelines for a Standalone System

Partitioning Guidelines for a Test Lab

Partitioning Guidelines for a Distributed Configuration

Partitioning Guidelines for the Management Server

Procedure to Create Raw Partitions on the Management Server

Task 6: Obtaining a Cisco EMF License

Task 7: Making System Modifications

Setting Up IP and Remote User Access Information

Check and If Needed Configure DNS

Checking for DNS

Verifying DNS Configuration

Task 8: Installing the Cisco MGC Host Provisioning Tool

Task 9: Installing Cisco EMF 3.2 and Any Necessary Patches

(All Configurations) Installing the Full Cisco EMF Software

(Distributed Configuration) Installing the Cisco EMF Client Software on a Presentation Server

Installing Cisco EMF Patches

Starting Cisco EMF

Task 10: Configuring Raw File Systems in ObjectStore

Task 11: Installing and Verifying Cisco MNM 2.1

Installing Cisco MNM

Verifying the Installation of Cisco MNM

Verifying Element Managers

Verifying the Installation of CiscoView 5.1

Starting Cisco MNM

Task 12: Upgrading CiscoView 5.1 If Needed

Task 13: Setting up the X Terminal Workstations for Remote Access

Creating an XDMCP Connection

Creating a Workstation Connection

Fixing the Insufficient Colors Problem

Task 14: Configuring Network Devices to Forward Alarms

Upgrading from Cisco MNM Version 1.5

Backing Up Your Databases

Uninstalling the Cisco MNM Software

Verifying Uninstallation of Cisco MNM

Uninstalling Cisco EMF

Troubleshooting Common Installation Problems

Planning and Installation

This chapter describes how to plan and execute your installation of the Cisco Media Gateway Controller Node Manager Version 2.1 (Cisco MNM). The chapter contains the following topics:

•Installation Overview

•Planning and Installation Checklist

•Upgrading from Cisco MNM Version 1.5

•Uninstalling the Cisco MNM Software

•Uninstalling Cisco EMF

•Troubleshooting Common Installation Problems

Installation Overview

Successful network management using Cisco MNM begins with a well-planned and carefully executed installation. Network element management involves many interdependent factors, including:

•The correct hardware for your environment

•The correct software release and patch levels on the managed devices

•The correct installation of Cisco Element Manager Framework, the foundation software for Cisco MNM

To organize the installation process, use the Planning and Installation Checklist to plan and carry out your installation. Begin by reading it over to understand the major tasks in a successful installation, and check off each task as completed.

Who Should Install Cisco MNM?

Installing Cisco MNM involves tasks such as setting up hard drives and checking and modifying system files, which are best performed by an experienced system administrator with good knowledge of UNIX and Solaris.

Planning and Installation Checklist

Procedures for completing each task are described in the sections that follow.

Note If you are upgrading from 1.5: Review the Release Notes, go on to the "Upgrading from Cisco MNM Version 1.5" section.

___

Before you begin: Read the Release Notes, which supplement and, if different, take precedence over information here.

___

Task 1: Gather installation software and required information.

___

Task 2: Determine hardware requirements for your environment.

___

Task 3: Ensure that network devices have the correct software.

___

Task 4: Ensure that the Sun Solaris operating system is installed on your workstation.

___

Task 5: Partition the hard drives.

___

Task 6: Obtain a Cisco EMF license.

___

Task 7: Check system prerequisites. (DNS)

___

Task 8: Install the Cisco MGC Host provisioning tool(Voice Services Provisioning Tool(VSPT), recommended, or CMM).

___

Task 9: Install Cisco EMF 3.2 and any necessary patches.

___

Task 10: If you plan to use raw file systems, configure raw file systems in ObjectStore.

___

Task 11: Install and verifying Cisco MNM 2.1 and any necessary patches.

___

Task 12: Upgrade CiscoView 5.1 if needed.

___

Task 13: Set up the X terminal workstations for remote access.

___

Task 14: Configure network devices for management. This task, required before Cisco MNM can collect alarm information from network devices, is covered in the next chapter, "Configuring Network Devices for Management."

Note After installing Cisco MNM 2.1, you should synchronize the time configured for the Cisco MGC, Cisco MNM, and the Billing and Measurement Server (BAMS). To ensure that Cisco MNM records are correct, these components should all be configured to Greenwich Mean Time (GMT). Refer to the Cisco Media Gateway Controller Software Release 9 Software Installation Guide and the Billing and Measurement Server User's Guide for your BAMS server for information about setting the time for these components.

Task 1: Gathering Installation Software and Required Information

This section describes the software and information you should have on hand before you begin installation.

Installation Software

Cisco MNM and Cisco MGC Host Provisioning Software

Your order of Cisco MNM includes three product CDs:

•Cisco Element Management Framework (Cisco EMF) 3.2 on the first CD. The software includes ObjectStore 5.1 Service Pack 2, which provides database management. Go to http://www.cisco.com/pcgi-bin/tablebuild.pl/cemf for the Release Notes and the latest Cisco EMF 3.2 software patch.

•Cisco MNM 2.1x on the second CD, including:

–The Cisco MNM element managers that work with Cisco EMF

–Cisco Media Gateway Controller Manager (CMM) for provisioning the Cisco MGC

–CiscoView 5.1, installed automatically when Cisco MNM is installed (management interface for the Cisco SLT)

•CiscoWorks, on the third CD

Note When Cisco MNM is installed in the client-server mode, CiscoWorks must be installed on the client.

–Netscape, for displaying Help for browser-based management

Go to http://www.cisco.com/pcgi-bin/tablebuild.pl/mgc-nm for the Cisco MNM Release Notes and the latest patch, if any.

Either CMM or the VSPT is required for voice provisioning, depending on the network configuration. Either must be installed before Cisco MNM. CMM is provided on the Cisco MNM CD. Download VSPT from the Web at http://www.cisco.com/pcgi-bin/tablebuild.pl/vspt. The appropriate version of VSPT depends on your Cisco MGC version. Refer to the latest Cisco MNM Release Notes for your version.

Note If you are managing nodes with Cisco MGC hosts running different software versions, you can install both VSPT versions. Cisco MNM launches the correct version for the currently selected host.

X Terminal Software

To access Cisco MNM from a remote workstation, you should have Reflection 7.2 or above installed. See the "Task 13: Setting up the X Terminal Workstations for Remote Access" section for information about X terminal access.

Solaris 8 Operating System

The machines that will run Cisco MNM should have the Sun Solaris 8 operating system with Common Desktop Environment (CDE) 1.3 installed.

Note Please check that Solaris 8 is installed on your Sun hardware. Sun hardware is typically shipped with Solaris 2.7.

Note For optimum database handling where you are collecting large quantities of data, a volume manager is recommended. Sun Solaris 8 Server version includes one (DiskSuite).

Required Information

This chart lists information helpful to have before you begin installation. Complete the chart and have it available as you work through the installation tasks.

Information

Where To Find It

Value

Superuser (su) password and privileges

Your UNIX system administrator

Host name and host ID of the machine where Cisco EMF will be installed (in a distributed configuration, the Management server)

On the machine, enter hostname at the command prompt. The host name displays.

At the command prompt, enter hostid. The host ID displays. This is a hexadecimal string that identifies the system, not the IP address.

Hostname:

Host ID:

Host IP address of that machine

At the command prompt, enter host.

If there are multiple interfaces, select the IP address of the interface where traps will be forwarded (as specified when you configure devices for network management; see Chapter 3).

Product Authorization Key for Cisco EMF, to be used in Task 6

On the Cisco EMF product CD sleeve.

DNS Domain of the machine where Cisco EMF will be installed (in a distributed configuration, the Management server)

Your UNIX system administrator

Disk descriptions of disks with raw partitions, in the form c0t0d0s0

Make note of disk names when you are complete "Procedure to Create Raw Partitions on the Management Server" section.

Disk:

Disk:

Disk:

Disk:

Task 2: Determining Your Hardware Requirements

The hardware you need and the way you install Cisco MNM depend on the size of the network you are managing and the amount of data you collect. This section is designed to help you determine your hardware requirements and software configuration.

Cisco EMF and Cisco MNM each comprise server and client software:

•The server software handles network management, including management of the databases that contain network information and store alarm and performance data. The server software also handles the GUI applications with which users interact when CMNM is installed on a standalone server.

•The client software handles the GUI applications with which users interact.

The Cisco EMF and Cisco MNM software runs on a separate machine or on machines other than the Cisco MGC host. In a small network, such as a lab, server and client software might reside on a single machine (a standalone configuration). In larger networks, the software is installed on two (or more) machines, in this distributed configuration:

•One machine, known as the Management server, contains the server software (including the ObjectStore database management software included with Cisco EMF) and client software

•One machine, known as the Presentation server, contains the client software only. In some large networks, more than one Presentation server may be required.

In either configuration, users typically access Cisco MNM from X terminal workstations that run the Client software through a Telnet session. In the distributed configuration, the X terminal workstations connect directly to the Presentation server to run the Client software.

The two configurations are shown in Figure 2-1.

Figure 2-1 Standalone and Distributed Configurations

Note The management server is sometimes called the Database server. The presentation server is sometimes called the client, GUI, or Application server. To avoid confusion, this document uses Management server and Presentation server consistently, and these terms describe the machines in a distributed configuration, not the software that resides on them.

Note Cisco MNM supports ten simultaneous X terminal users, depending on your processing resources, network size, and the version of Cisco EMF you are running.

Hardware Requirements

The Cisco MGC hardware requirements for various network sizes are described in Table 2-1. In addition, except in a very small network, each operator requires an X terminal workstation.

Table 2-1 Hardware Requirements for Cisco MNM Host Machine(s)—Cisco MGC

Network Element

Small Network

1-3 Operators

1-5 Nodes

1 trap / sec

Medium Network

4-6 Operators

6-10 Nodes

2 traps / sec

Large Network

7-10 Operators 11-20 Nodes

4 traps / sec

Number of machines

1 machine

2 machines

2 machines

Configuration

Standalone

Distributed

Distributed

Presentation server

Management server

Presentation server

Management server

RAM (GB)

2

2

2

2

4

Swap (GB)

2

1

2

1

2

Disk drives (9 GB minimum)

4

1

4

1

8

CPU (MHz)

2 x 440

2 x 440

2 x 440

4 x 440

2 x 440

Note Disk drive requirements are based on the number of drives. The CEMF host machine requires at least the number of drives indicated in Table 2-1.

Note These are recommendations to aid you in planning. The total amount of disk space required depends on many factors, such as the amount of alarm and performance data collected.

Disk Drives and Database Storage

In a medium to large network, using multiple disk drives to store the databases helps alleviate I/O bottlenecks and improves software performance. If you are using multiple disk drives for database storage, or you expect to generate large database files, use raw partitions, as described in the "Partitioning Guidelines for a Distributed Configuration" section. If you are using cooked file partitions, installing more than one drive for database storage does not yield any performance improvements because the databases cannot span multiple partitions.

Task 3: Ensuring That Network Devices Have the Correct Software

Cisco MNM interacts with other software running on the various components of the Cisco MGC node. A potential cause of network management problems, such as failure to discover a device during deployment, is a mismatch between the software on the device and the version or patch compatible with Cisco MNM. The software requirements for these components are described in Table 2-2.

Caution Upgrades are released frequently. To be sure that you have any necessary software patch, check the Web site for the latest bulletins and upgrades.

Table 2-2 Required Software Versions for Cisco MGC Node Devices

External Software

Version

Where To Check for Upgrades

Cisco MGC host software

7.4.11¹ (managed by CMNM 1.5) and 9.x (managed by CMNM 2.1)

For upgrades to the PGW2200:

http://www.cisco.com/pcgi-bin/Support/PSP/psp_view.pl?p=Hardware:SC2200

For installation documentation and release notes:

Version 7:

http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/

Version 7 and 9:

http://wwwin.cisco.com/CustAdv/InfoSys/StrategicServices/VoIP/PBAPP/Display_Sec.pl?page_id=3684

Cisco SLT IOS SS7 image

12.0.7 XR or above

For upgrades:

http://www.cisco.com/pcgi-bin/Support/PSP/psp_view.pl?p=Hardware:2600&s=Software_Installation#Software_Features_%26_Versions

For installation documentation and release notes:

http://www.cisco.com/univercd/cc/td/doc/product/access/sc/slt/index.htm

Cisco LAN Switch code

5.4(4)

For upgrades:

http://www.cisco.com/public/sw-center/sw-lan.shtml

BAMS

2.8 and 3.0

For installation documentation and release notes:

http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/bams2/

¹Although Version 7.4.10(B) can be used with Cisco MNM, it is not a supported release.

Task 4: Ensuring That the Sun Solaris 8 Operating System Is Installed

Cisco MNM machines should have the Sun Solaris 8 operating system with CDE 1.3 installed. The operating system installation script is provided by the hardware manufacturer.

If the Sun Solaris 8 operating system is not already installed, install it according to instructions provided by the manufacturer.

When the Solaris operating system is installed, go to Task 5: Planning and Executing Hard Drive Partitioning.

Note Please check that Solaris 8 is installed on your Sun hardware. Sun hardware is typically shipped with Solaris 2.7.

Note Newer model equipment might require the drivers provided in the most recent patches. If your Ethernet interfaces do not come up as Active, you may have an older patch. Check the Sun web site for the most recent patch.

Task 5: Planning and Executing Hard Drive Partitioning

This section provides:

•Guidelines for planning and partitioning hard drives in a standalone system (for a small network) or a distributed configuration (for a larger network)

•Instructions for creating raw partitions

By default, the Cisco EMF software is installed with the ObjectStore database configured for standard UNIX cooked partitions (partitions with readable directory structures). However, we recommend using raw partitions (partitions without a readable directory structure) for the database drives f or larger networks because it offers these advantages over cooked partitions:

•The capability of having databases over 2 GB in size

•The ability to store database files across multiple drives

Use the following guidelines to plan the disk layout for your site, and then see "Procedure to Create Raw Partitions on the Management Server" section for the step-by-step drive partitioning procedure.

Partitioning Guidelines for a Standalone System

In a small network using a standalone configuration, the Cisco EMF/Cisco MNM server typically contains four 9 GB hard drives:

•Drive 1 and 2 contain necessary Cisco EMF/Cisco MNM directories and swap space.

•Drive 3 and 4 contain the database, using raw partitions.

Use the same file system layout as shown in "Partitioning Guidelines for the Management Server" section.

Partitioning Guidelines for a Test Lab

If a Cisco MNM implementation is used exclusively for testing Cisco MNM, you may implement a smaller system with only three drives:

•Drive 1 and 2 contain necessary Cisco EMF/Cisco MNM directories and swap space.

•Drive 3 contains the database and uses cooked partitions.

Partition drives according to the specifications in Table 2-3.

Table 2-3 File System Layout for Small Test Lab

Drive

Partition

Directory

Size

1

0

/root

512 MB

1

/swap

2.0 GB

3

/var

1.0 GB

4

/usr

4.0 GB

5

/home

Remainder

2

0

/swap

2.0 GB

1

/opt

Remainder

3

0

/opt/CSCOcemf/db

2.0 GB

Partitioning Guidelines for a Distributed Configuration

Partitioning Guidelines for the Management Server

In a medium to large network, a Cisco MNM Management server typically contains four or more 9 GB hard drives:

•Drive 1 and 2 contain necessary Cisco EMF/Cisco MNM directories and swap space.

•Drive 3 and each additional drive are configured with raw partitions for database storage.

Using a raw file system for database drives optimizes ObjectStore database performance. With raw partitions, ObjectStore does not have to go through the Solaris operating system to access the partition for data storage and retrieval.

Note With raw partitions, when the first database drive is full, ObjectStore begins to write data to the next drive, but it does not perform load balancing across drives. If you anticipate collecting extensive measurements and alarms on a large network, you might want the improved database handling provided by load balancing. Use a volume manager utility, such as Volume Manager (included with Sun Solaris 8 Server version) to set up all the database drives as a single volume.

Figure 2-2 shows the recommended file system layout for the standalone or Management server in a distributed configuration. Partition drives according to the specifications in Table 2-4. For instructions on how to create raw partitions, see the "Procedure to Create Raw Partitions on the Management Server" section.

Figure 2-2 Recommended File System Layout for Standalone or Management Server

Caution All hard drives used in the raw file system should be of the same manufacturer and model.

Table 2-4 Recommended File System Layout for Management Server

Drive

Partition

Directory

Size

1

0

/root

512 MB

1

/swap

2.0 GB

3

/var

1.0 GB

4

/usr

4.0 GB

5

/home

Remainder

2¹

0

/swap

2.0 GB

1

/opt

Remainder

Partitioning of additional drives with raw partitions (required if using multiple database drives)

3

0

none

All

4

0

none

All

Each additional drive

0

none

All

¹Do not modify partition 2 (also called the backup or overlap partition). This partition identifies the amount of space on the entire drive.

Note Because cooked partitions are the ObjectStore default, after installation you must configure raw file systems in ObjectStore. See the "Task 10: Configuring Raw File Systems in ObjectStore" section.

Procedure to Create Raw Partitions on the Management Server

These instructions assume that you have installed the operating system and the system is bootable.

Note Be prepared to write down in the chart, in the "Required Information" section, the drive label names identified during this procedure. This information is needed in Task 10: Configuring Raw File Systems in ObjectStore.

Use the following steps to create a raw partition.

Step 1 Log in as superuser (su).

Step 2 At the system prompt, type format and press Enter. The AVAILABLE DISK SELECTIONS list appears, showing disks on the system, for example:
AVAILABLE DISK SELECTIONS:
0 c0t0d0
...
Where 0 is the disk number and c0t0d0 is the disk label. The line after the list of available disks displays the prompt:
Specify disk (enter its number):
Step 3 In the chart in the "Required Information" section, write down the label of the disk you are about to partition, followed by s0. This is the complete disk description including the partition or "slice" number, represented by s0. For example:
c0t0d0s0
Step 4 Enter the number of the disk you are partitioning, such as 3, and press Enter. The FORMAT MENU appears followed by the prompt:
format>
Step 5 Enter ver, and press Enter, to show the current partitions. On a new drive, you see a display similar to this:
Part      Tag    Flag     Cylinders         Size            Blocks
  0 unassigned    wm       0                0         (0/0/0)            0
  1 unassigned    wm       0                0         (0/0/0)            0
  2     backup    wm       0 - Last cyl     Total     (First block/0/0) Total blocks
                                            disk
  3 unassigned    wm       0        						        0         (0/0/0)            0
  4 unassigned    wm       0                0         (0/0/0)            0
  5 unassigned    wm       0                0         (0/0/0)            0
  6 unassigned    wm       0                0         (0/0/0)            0
  7 unassigned    wm       0                0         (0/0/0)            0
Step 6 Enter par, and press Enter. The PARTITION MENU appears listing the partitions that you can configure.

Step 7 Enter 0, and press Enter. This prompt appears:
Enter partition id tag [unassigned]:
Step 8 To make this a raw partition, leave the id tag blank, choosing the default "unassigne,d" and press Enter. This prompt appears:
Enter partition permission flags[wm]:
Step 9 Press Enter to choose the default flag (wm). This prompt appears:
Enter new starting cyl[0]:
Step 10 Press Enter to choose the default (0, the beginning of the drive) as the starting cylinder, . This prompt appears:
Enter partition size:
Step 11 Enter the partition size based on the space you are allocating to the database, typically the entire drive. For example, enter 8.5gb, and press Enter.

You have completed the partitioning, and the partition prompt appears:
partition>
Step 12 Enter q, and press Enter to quit the PARTITION MENU. The format prompt appears:
format>
Step 13 Commit your changes:

Enter label, and press Enter. This prompt appears:
Ready to label disk, continue?
Step 14 Enter Yes, and press Enter. The format prompt appears:
format>
Step 15 Verify the partitioning:

Enter ver, and press Enter. You should now see a display similar to this:
Part      Tag    Flag     Cylinders         Size            Blocks
  0 unassigned    wm       0 - Last cyl     Total     (First block/0/0) Total blocks
                                            disk
  1 unassigned    wm       0                0         (0/0/0)            0
  2     backup    wm       0 - Last cyl     Total     (First block/0/0) Total blocks
                                            disk
  3 unassigned    wm       0                0         (0/0/0)            0
  4 unassigned    wm       0                0         (0/0/0)            0
  5 unassigned    wm       0                0         (0/0/0)            0
  6 unassigned    wm       0                0         (0/0/0)            0
  7 unassigned    wm       0                0         (0/0/0)            0
Step 16 Enter q, and press Enter, to quit the format menu. The system prompt appears.

The raw partition for the selected drive is complete. Follow the same steps to partition the remaining database drives.

Note Since this is a raw, not cooked, partition, you do not run the newfs utility.

Task 6: Obtaining a Cisco EMF License

You need a valid license key file available on the system to start Cisco EMF. In a distributed configuration, the license key is required on the Management server.

Use the following steps to obtain a Cisco EMF license:

Step 1 If you are a registered Cisco Connection Online (CCO) user, go to the Cisco Software Registration site:

http://cco.cisco.com/kobayashi/sw-center/sw-registration.shtml

If you are not a registered CCO user, go to the Cisco Software Registration site
:
http://cco.cisco.com/public/sw-center/sw-registration.shtml

Step 2 Click Cisco Element Manager Framework.

Step 3 In the Contact Information section, fill all required fields (denoted by an asterisk).

Note Because the permanent license key is returned to you by e-mail as an attached file, you must provide your correct e-mail address.

Step 4 In the Version number field, select version 3.2.

Step 5 If it was not automatically filled in for you when you completed the Contact Information, enter the Product Authorization Key (PAK) number which is on your product CD.

Step 6 Specify the host name of the server where Cisco EMF is to be installed.

Obtain the host name by entering hostname at the command line prompt.

Step 7 Specify the host ID of the server where Cisco EMF is to be installed.

Obtain the host ID by entering hostid at the command line prompt.

Step 8 Provide answers to the questions at the end of the form, and click Enter Form.

To update a Cisco EMF 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) see the Cisco EMF Installation and Administration Guide at:

/en/US/docs/net_mgmt/element_manager_system/3.2/installation/guide/license.html#xtocid183871

Task 7: Making System Modifications

Two kinds of system modifications are necessary after you have installed the Solaris operating system and set up disk drives:

•Setting up IP and remote user access information

•Checking and, if needed, configuring DNS

Setting Up IP and Remote User Access Information

After you have installed Solaris and added all hard drives, you will need to edit some files on the Management server that contain data for IP networking and remote user access.

Table 2-5 IP Networking and Remote User Access Files

File

Modification

/etc/defaultrouter

Add the host name and IP address of the default gateway router that provides network access between remote users, network devices, and the standalone system or the Management server.

/etc/default/login

Add a # symbol at the front of the line that says CONSOLE = /dev/console to comment out the line. If you do not comment out this line, users will not be able to login to the machine remotely.

/etc/default/login

Add the login accounts for all users that will be accessing the server by Telnet.

/etc/hosts

Add the Presentation server's host information.

Note If the Cisco EMF server uses Domain Name System (DNS), also see "Task 8: Installing the Cisco MGC Host Provisioning Tool" section.

Check and If Needed Configure DNS

If the server where you are installing Cisco EMF/Cisco MNM uses Domain Name System (DNS), you must configure the host name known to the DNS server before installing Cisco EMF. This section describes how to determine the DNS status of the server and, if needed, configure the host name.

We recommend that you install Cisco MNM in an environment that uses DNS.

Note Perform this task before installing Cisco EMF. If you change how DNS is configured after Cisco EMF is installed, you must uninstall and reinstall Cisco EMF.

In a distributed configuration using DNS, the host name of the Presentation server must also be configured on the Management server.

Checking for DNS

In a distributed configuration, perform this check on the Management server only. Use the following steps to check for DNS:

Step 1 Log in as superuser (su), and change to the /etc directory.

Step 2 Look for the file resolv.conf. If the file exists, go to "Verifying DNS Configuration" below. If the file does not exist, go on to the next step.

Step 3 Verify that the hosts entry in the file /etc/nsswitch.conf looks exactly like the following line:

hosts: files

Note If the hosts: line in /etc/nsswitch.conf has anything else configured, Cisco EMF does not install properly.

Step 4 If the machine does not use DNS, go to the next task. Cisco EMF and Cisco MNM will install properly.

Verifying DNS Configuration

If you determine that the system uses DNS, follow these steps to verify that the Management server is configured on the DNS server:

Step 1 Verify that a valid DNS server and domain name are defined in /etc/resolv.conf.

Step 2 To verify that the Management server is configured on the DNS server, enter the following command:
nslookup hostname
Where hostname is the server's host name.

If the command fails, add the host name to the DNS server before installing Cisco EMF. Contact your system administrator to do this.

Step 3 In a distributed configuration, also verify that the host name of the Presentation server is configured.

Task 8: Installing the Cisco MGC Host Provisioning Tool

There are two different Cisco MGC provisioning tools, depending on what network architecture you are running. If you are running the Cisco SS7 PRI Gateway Solution or the Cisco Tandem Offload Solution, install the VSPT. For all other architectures, install Cisco MM.

•For information on installing and upgrading VSPT, refer to the Cisco VSPT web site:

http://www.cisco.com/pcgi-bin/tablebuild.pl/vspt

•For information on installing and upgrading Cisco MM, which is included on the Cisco MNM product CD, refer to the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide:

http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/swinst/index.htm

Task 9: Installing Cisco EMF 3.2 and Any Necessary Patches

This section describes how to install and start Cisco EMF 3.2. You must install and start Cisco EMF 3.2 before installing Cisco MNM.

(All Configurations) Installing the Full Cisco EMF Software

Use this procedure to install Cisco EMF on a standalone system or on the Management server in a distributed configuration.

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

Step 2 Insert the Cisco EMF product CD into the CD-ROM device.

Step 3 At the command line prompt, type:

cd /cdrom/cdrom0

Step 4 To invoke the Cisco EMF installation script at the command line prompt, type:

./cemfinstall

A menu listing the Cisco EMF installation options appears.

Step 5 Choose Server to install the full version of Cisco EMF (both the Server and Client software).

You are asked where the installation should be placed. The default location is /opt/cemf.

Step 6 If the default location is acceptable, press Enter.

If the default is not acceptable

a. Enter n.

b. Enter a directory path.

c. Press Enter to verify your choice or to repeat the sequence.

You are prompted to enter the directory to be used for backups and restores. The default directory /opt/Backup is displayed.

Step 7 For the backup directory, specify a separate disk to gain better performance from Cisco EMF. For example, specify:

disk /opt/Backup

Step 8 If the machine has more than one host name, a menu is displayed. Do one of the following:

•Select the correct host name, then press Enter.

•If the correct host name is not listed in the menu, press Enter, type in the desired host name, then press Enter.

The server host name and server IP Address are displayed.

Step 9 If the setup is correct, press Enter.

If the setup is not correct, type n, then press Enter when you wish to change these values. You normally only change these values if your system has multiple network card interfaces from which to choose.

Note If you enter an incorrect host name or IP address, the Error : IP Address <IP Address> entered for <server name> Server system is invalid message is displayed.

When you have specified the valid host name and IP address, the installation process checks your system for a valid version of ObjectStore.

Step 10 Type y, and press Enter.

You are asked if you wish to store the databases in a raw partition.

Step 11 Type y, and press Enter. For more configuration information, refer to UNIX File System, RAW File System (RAWFS) or Adding Partitions to Increase ObjectStore Available Space.

You are asked where to place the database files.

Step 12 Type in the relevant path, the disk name noted during raw partitioning, and press Enter.

You are prompted to confirm the location of the directory where the ObjectStore transaction log file will be placed.

Step 13 Type n, and press Enter. You are asked to specify the directory where the transaction log file is to be placed.

Step 14 Type in the path to the directory, and press Enter. The directory you specified is displayed. If it is correct, press Enter. If the directory is not correct type n, press Enter, and correct the relevant information.

Note To optimize performance, the log file should be placed on a separate drive.

When the ObjectStore options are configured, you are asked for the DNS domain of your system.

Step 15 To accept the default, type y, and press Enter. To change the default, type n, press Enter, specify the relevant DNS domain, and press Enter.

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.

Step 16 To use the FlexLM daemon provided with Cisco EMF, type y, and press Enter. You are asked if you have a valid license file.

Press Enter, if you have a valid license file available on your network. You are then asked to type in the full name, including the path, of the license file.

Step 17 To use an existing FlexLM daemon running on your system, type n, and press Enter.

You are asked to Enter the location of the license file. Type in the location, then press Enter. Your choice is displayed and you are asked to confirm that the location is correct.

Step 18 Type y, then press Enter to proceed or type n, then press Enter to correct the path.

The installation process starts. This process takes several minutes. The system displays a message message that the Cisco EMF Server Package installation completed satisfactorily.

Once the installation is complete, cd out of the directory /cdrom/cdrom0, and type eject.

Remove the Cisco EMF product CD from the CD-ROM drive.

If a valid license file was supplied, you can now start the Cisco EMF Server, as described in "Starting Cisco EMF" section.

(Distributed Configuration) Installing the Cisco EMF Client Software on a Presentation Server

Use this procedure to install the Cisco EMF Client software in a distributed configuration. You do not need a license on this machine.

Step 1 Log in as superuser (su) on the Presentation server.

Step 2 Insert the Cisco EMF product CD into the CD-ROM drive.

Step 3 Change to the CD-ROM drive and enter:
host# cd /cdrom/cdrom0
Step 4 To start the Cisco EMF installation script, enter:
host# ./cemfinstall
Step 5 Select option 2 to install the client software.

The default location for installing the Cisco EMF Client software is /opt/cemf.

Step 6 If the default location is acceptable, press Enter.

If the default is not acceptable:

a. Enter n.

b. Enter a directory path.

c. Press Enter to verify your choice or to repeat the sequence.

Step 7 Enter and verify the host name of the Management server (where the full Cisco EMF software is installed).

Step 8 If the server host name and server IP address are correct, press Enter. To change the values, enter n.

Tip Change these values if your system has multiple network card interfaces.

Step 9 When the installation is complete, leave the /cdrom/cdrom0 directory, and enter eject.

Step 10 Remove the Cisco EMF product CD from the CD-ROM drive.

Installing Cisco EMF Patches

Refer to the Cisco MNM Release Notes for the patch version and download location required. To install the patch as described in the following steps:

Step 1 Go to the following URL:

http://www.cisco.com/pcgi-bin/tablebuild.pl/cemf

Step 2 Download the appropriate Cisco EMF patch to a directory on your hard drive.

Step 3 Follow the patch installation instructions in the Cisco EMF Installation and Administration Guide at the following web site:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cemf/3_2/install/index.htm

Starting Cisco EMF

Start the Cisco EMF as described in the following procedure:

Step 1 Log in to the system where you installed Cisco EMF, and type su - root to become the root user.

Step 2 Change to the CEMF bin directory by entering:

cd <CEMF_ROOT>/bin

Where <CEMF_ROOT> is the directory where Cisco EMF is installed.

Step 3 If the Cisco EMF background processes are not already running, enter:

./cemf start

Step 4 Wait 10 to 15 minutes for the Cisco EMF startup processes to complete.

Task 10: Configuring Raw File Systems in ObjectStore

Perform this task after installing Cisco EMF but before installing Cisco MNM.

Note the following:

•You must have previously partitioned the hard drives as described in the "Task 5: Planning and Executing Hard Drive Partitioning" section.

• To identify the installation directory for the Cisco EMF software, use the command /bin/pkgparam cemfm BASEDIR.

• All raw partitions must be exactly the same size (in megabytes). ObjectStore does not use partitions of different sizes.

•Have on hand t he raw partition names (for example, /dev/rdsk/c0t1d0s3) you wrote down during hard disk partitioning.

•Have on hand the host name of the machine whose drives you are partitioning (for example, cemfserver).

Caution Adding, modifying, or deleting raw file systems resets the ObjectStore database and destroys any existing data.

Use the following procedure to configure raw file systems in ObjectStore:

Step 1 Type su - root to become the root user.

Step 2 Stop the current Cisco EMF processes (/etc/init.d/cemf stop).

Step 3 Shut down ObjectStore (for example, /etc/rc2.d/S80ostore4 stop).

Step 4 Shut down the AV License Manager (for example, /etc/rc2.d/S98avlm stop).

Step 5 Start a Cisco EMF shell (for example, /etc/rc2.d/S99cemf shell).

Step 6 Change to the Cisco EMF installation directory (for example, /opt/cemf).

Step 7 Change to the ./ODI/OS5.1/ostore/etc directory (under /opt/$INSTALL_DIR).

Step 8 Edit the host name server parameter file (for example, cemfserver_server_parameters) and make the following modifications:

• Put a comment character (#) at the beginning of the Log File line. (This places the transaction log in the raw partition.)

• Add an entry for each raw partition that ObjectStore uses.

• Each line must begin with PartitionX: (where X is a number starting with zero and incrementing by one). Do not forget the colon character.

• Each line must have the word PARTITION as its second element.

• Each line must have the raw partition listed as its last element. (Do not forget to use the rdsk partition identifier.)

An example cemfserver_server_parameters file is shown here:

unix-shell#> cd /opt/cemf/ODI/OS5.1/ostore/etc
unix-shell#> cat cemfserver_server_parameters

#Log File: /opt/transact.log

Partition0: PARTITION /dev/rdsk/c2t9d0s0

Partition1: PARTITION /dev/rdsk/c2t10d0s0

Partition2: PARTITION /dev/rdsk/c2t12d0s0

Partition3: PARTITION /dev/rdsk/c2t13d0s0

unix-shell#>

Step 9 Change to the Cisco EMF_INSTALL/ODI/OS5.1/ostore/lib directory (for example, opt/cemf/ODI/OS5.1/ostore/lib).

Step 10 Run the command ./osserver -i to reinitialize ObjectStore. Answer yes when prompted to reinitialize the database.

Step 11 Run the command /etc/init.d/cemf reset to reset the Cisco EMF database. Answer yes when prompted.

Step 12 Run the command /etc/init.d/cemf start to start the ObjectStore and Cisco EMF processes.

Task 11: Installing and Verifying Cisco MNM 2.1

Follow these instructions to install Cisco MNM and verify the installation. If you are upgrading from Version 1.5, see the "Upgrading from Cisco MNM Version 1.5" section.

Identify any necessary patches by checking the location given in the "Installation Software" section.

Note You must install the Cisco MNM software as root.

Follow the procedure below to install Cisco MNM on a standalone system or on both machines (Management server and Presentation server) in a distributed configuration. The Cisco MNM installation process automatically detects if the Cisco EMF complete software is installed, or only the Cisco EMF Client, and then installs the correct Cisco MNM component.

Note The Cisco MNM software is shipped with the Element Managers in Table 2-6. Cisco MNM has not been tested with any other Element Managers. If you install additional Element Managers, they are not supported by Cisco MNM.

Installing Cisco MNM

Step 1 Make sure tat Cisco EMF is running.

Step 2 Type cd <CEMF_ROOT>/bin, and enter the following command to veryify that Cisco EMF is running:

>./cemf query

Step 3 Locate the Cisco MNM installation media.

Step 4 Type su - root to become the root user.

Step 5 Verify that the Volume Management daemon is running:

a. Type the command ps -ef | grep vold.

•If it is running, you see the following output:

root 363 1 0 May 23 ? 0:01 /usr/sbin/vold

•If the Volume Management daemon is not running, start the daemon using the following command:

/etc/init.d/volmgt start

b. Verify that the Volume Management daemon is running with the command provided above. If it is still not running, contact your system administrator.

Step 6 Place the Cisco MNM installation media into the CD-ROM drive.

Step 7 Type cd /cdrom/cscocmnm.

Step 8 Type ./installCSCOcmnm.

Note If the Cisco MNM Element Managers are already installed, you see an error message informing you that and the installation exits. Use the upgrade option as described in the "Upgrading from Cisco MNM Version 1.5" section.

Verifying the Installation of Cisco MNM

Verify that Cisco MNM software is installed properly before starting Cisco MNM.

Verifying Element Managers

Step 1 Verify that the Cisco MNM Package is installed using the following command:

pkginfo CSCOcmnm

The following message should appear:

application CSCOcmnm Cisco MGC-Node Manager

Step 2 Verify that the Cisco MNM Element Managers have been installed. Run the following script to display the installed Cisco MNM Element Managers and compare this with the list in the table below.

Cisco EMF Basedir/bin/cmnmversion -verbose
CSCOcmnm Tool Versions
                      Patch Build  Build
         Name Version Level  Num   Type
    ------------------------------------
     CSCOcmnm   2.1    00   102300 REL   
     CSCOcmcv   5.1    00   092600       
    CSCOcemfm   3.2 Patch: 170004-08
    ------------------------------------
CSCOcmnm Element Manager Versions
                      Patch Build  Build
         Name Version Level  Num   Type
    ------------------------------------
      hostEMm   2.1    00   022101 REL   
       mgcEMm   2.1    00   022101 REL   
------------------------------------
Note Specific information displayed from running this script varies according to the CMNM release and patch you are using.

Table 2-6 Element Managers

mgcEM

Common Element Manager for Cisco MGC node devices

hostEM

Element Manager for Cisco MGC host signaling, trunking, and dial plan components

Verifying the Installation of CiscoView 5.1

Note CiscoView is designed to work with CiscoWorks 2000. When installing CiscoView packages outside this environment, certain functions are not supported. The following CiscoView buttons do not work in the Cisco MNM environment:

- Telnet
- CCO connection
- Preferences
- About
- Help

When running xdsu, the following exception is generated and can be ignored:

ERROR: exception occurred while examining Integration Utility configuration: com.cisco.nm.nmim.nmic.IntgUtilCheckConfig

Use the following procedure to verify the installation of CiscoView 5.1:

Step 1 Verify that the CiscoView Application has been installed with the following command:

pkginfo CSCOcmcv

•If the package is installed, you see the following:

application CSCOcmcv CiscoView 5.1 for Cisco MGC-Node Manager

•If the package is not installed, you see the following:

ERROR: information for "CSCOcmcv" was not found

Step 2 Verify that the CiscoView Packages have been installed. CiscoView is shipped with the packages in Table 2-7.

Table 2-7 CiscoView Packages List

CiscoView Packages

Version

Base

1.0

Cat2900 XL

1.1

Cat5000

1.2

Cat5500

1.2

Cat8500

2.0

Rtr2600

2.0

StackMaker

1.0

SwitchAddlets

1.3

Step 3 Run either of the following commands to determine if the CiscoView packages listed in Table 2-7 are installed:

Cisco EMF Directory/ciscoview5.1/bin/dsu -query -all

The dsu application displays to STDOUT the installed CiscoView packages.

Cisco EMF Directory/ciscoview5.1/bin/xdsu

The xdsu application displays a GUI that lists the installed CiscoView packages.

Starting Cisco MNM

Step 1 Have Cisco EMF running.

Step 2 Log in with your user ID.

Step 3 Change to the Cisco EMF directory. For example:

cd /opt/cemf/bin

Note An X-server must be running, and the DISPLAY environment variable must be properly configured. Use one of the following commands, depending on which shell you are using, to set the x-display variable.

In "csh" or "tcsh": setenv DISPLAY <hostname>:0
In "sh" or "ksh": DISPLAY=<hostname>:0;export $DISPLAY

Step 4 Enter:

./cemf session

Step 5 When prompted, enter your login name and password:

Note The default Cisco MNM login and password are admin. Use the login and password configured for your system.

See "Getting Started with Cisco MNM," for help getting started using Cisco MNM.

Task 12: Upgrading CiscoView 5.1 If Needed

CiscoView 5.1 is installed with Cisco MNM. You should check for upgrades and, if there is one, install it.

Step 1 Check the CiscoView web site for the latest supported version of the package:

http://www.cisco.com/public/library/netmanage/cview/

Step 2 If there is an upgrade, go on to Step 3. Otherwise, go on to Task 13.

Step 3 Download the latest CiscoView packages and place in a temporary directory; for example, /scratch/cvUpgrade.

Step 4 Make sure that the package files are readable by the root user. If not, the packages do not appear in the CiscoView upgrade tool.

Step 5 Type su - root to become the root user.

Step 6 Change the directory to /scratch/cvUpgrade.

Step 7 To run the CiscoView upgrade tool, type:

Cisco EMF Directory/ciscoview5.1/bin/xdsu

Step 8 Click Install. Ignore the following exception:

ERROR: exception occurred while examining Integration Utility configuration: com.cisco.nm.nmim.nmic.IntgUtilCheckConfig

Step 9 Type in the exact location of the CiscoView packages in the Directory box, and press Enter or click Browse, navigate to your CiscoView packages' temporary directory, and click Select.

Step 10 Select the CiscoView packages that you want to upgrade, click Install, and click the appropriate confirmation button.

Task 13: Setting up the X Terminal Workstations for Remote Access

You can access Cisco MNM remotely from a workstation or PC. Cisco MNM has been tested with the Reflection 7.20 X server software package.

Creating an XDMCP Connection

For Reflection software to display Cisco MNM correctly, Reflection software must be run in XDMCP mode. For host name, use the name of the Presentation server (in a distributed configuration) or of the standalone system.

Step 1 Start Reflection.

Step 2 From the Connection menu, select New XDMCP Connection.

Step 3 From the Method pull-down menu, select Broadcast or Direct, and continue with one of the following set of steps:

For Broadcast method:

a. Click Connect.

b. Select the appropriate XDMCP computer. If you do not know which computer to select, contact your system administrator.

For Direct method:

a. In the Host Name field, enter the host name of an XDMCP computer.

b. Click Connect.

An X terminal window opens on the host machine. Start Cisco MNM in the usual manner, as described in the "Starting Cisco MNM" section.

Note If the Cisco EMF Launchpad displays but appears to be inactive, check for a message box behind the Launchpad reporting that there are insufficient colors available for Cisco EMF Manager. You can safely ignore the message (and close the message box), or remedy the problem as described in the next section.

Creating a Workstation Connection

Use the following procedure to connect to Cisco MNM from a remote UNIX workstation:

Step 1 Open anX-terminal window.

Step 2 Use Telnet to connect to the Cisco MNM host.

Step 3 Enter the following command to change to the Cisco MNM directory:

#cd /opt/cemf/bin

Step 4 Enter the following command to launch Cisco MNM:

#./cemf session

Fixing the Insufficient Colors Problem

To fix the "... insufficient colors available for Cisco EMF Manager" problem, obtain a copy of the Sun Solaris file rgb.txt, download it to your Winxx workstation, and configure Reflection to use the UNIX rgb.txt file as opposed to the Reflection default rgb.txt file. Use the following steps to perform this procedure:

Step 1 Change directory to your Reflection user directory using the following command:

cd Reflection Directory/user

Step 2 Back up your original rgb.txt file using the following command:

cp rgb.txt rgb.txt.orig

Step 3 Copy the UNIX file, /usr/openwin/lib/X11/rgb.txt, from your Sun Solaris workstation to your Winxx Reflection directory. You can use either FTP or RCP. If you are unable to use FTP or RCP to copy the rgb.txt file, contact your system administrator.

To use FTP, type the following commands:

ftp your_workstation

cd /usr/lib/X11

get rgb.txt rgb_unix.txt

Step 4 Configure Reflection:

a. Bring up Reflection X Manager.

b. From the Settings menu, select Color.

c. Look for the RGB Color File frame, and change the setting from Reflection Directory\user\rgb.txt to Reflection Directory\user\rgb_unix.txt.

Step 5 Stop and restart Reflection.

Note Just resetting the Reflection Xserver does not work; you must stop and restart Reflection.

Task 14: Configuring Network Devices to Forward Alarms

A final task in readying Cisco MNM for network management is to configure the devices in the network so that they send alarm information to Cisco MNM. For details, see "Configuring Network Devices for Management."

Note Migration from Cisco MNM Release 1.5 to Cisco MNM Release 2.1, or later, is not supported. Performance and alarm data cannot be migrated to Cisco MNM Release 2.1. The only recommended alternative is to create a seed file, which can be used for manual discovery.

Upgrading from Cisco MNM Version 1.5

If you are using Cisco MNM Version 1.5, the installation upgrade option installs Cisco MNM Version 2.1 and leaves your data intact (for example, network data and user access settings). You do not need to uninstall Cisco MNM Version 1.5 before upgrading. Both Cisco MNM 1.5 and 2.1 use Cisco EMF 3.2.

Note Although the upgrade option preserves your data, we recommend that you perform a backup before upgrading, as described in the "Uninstalling the Cisco MNM Software" section.

Perform the following steps to upgrade from Cisco MNM version 1.5:

Step 1 Check the"Planning and Installation Checklist" section to identify any other tasks needed for the upgrade.

Step 2 Have Cisco EMF and Cisco MNM running. Change to the <cemf_root>/bin directory and enter ./cemf query.

Step 3 Locate the Cisco MNM installation media.

Step 4 Type su - root to become the root user.

Step 5 Verify that the Volume Management daemon is running:

a. Type the command ps -ef | grep vold.

•If it is running, you see the following output:

root 363 1 0 May 23 ? 0:01 /usr/sbin/vold

•If the Volume Management daemon is not running, start the daemon using the following command:

/etc/init.d/volmgt start

b. Verify that the Volume Management daemon is running with the command provided above. If it is still not running, contact your system administrator.

Step 6 Place the Cisco MNM installation media into the CD-ROM drive.

Step 7 Type cd /cdrom/cscocmnm.

Step 8 Back up your database (see the "Uninstalling the Cisco MNM Software" section).

Step 9 Remove the MGX objects in the MGX-8260-View in Cisco MNM Mapviewer (see the "Modifying or Deleting Deployed Objects" section).

Step 10 Close Cisco MNM.

Step 11 Install CEMF 3.2 Patch 1.

Step 12 Type ./installCSCOcmnm -upgrade

Step 13 Open Cisco MNM and rediscover all BAMS objects using the Map Viewer BAMS-View.

Step 14 During installation, you receive the following prompts:

•Have you backed up your databases? Enter Y if you have.

•Logfile location - to accept the default, enter Y.

•Logfile name - to accept the default, enter Y.

Step 15 When the installation is complete, verify it according to the instructions in the "Verifying the Installation of Cisco MNM" section.

Note During the upgrade process, you may see error messages caused by Cisco EMF trying to create controllers that already exist. These messages may safely be ignored.

Note The Cisco MNM 1.5 Element Managers are installed; if present, they are upgraded.

Backing Up Your Databases

Be sure to back up your databases before upgrading from Cisco MNM 1.5 to 2.x. For more details, see the Cisco EMF Installation and Administration Guide.

Uninstalling the Cisco MNM Software

To uninstall the Cisco MNM software, type the following command:

<CEMF_ROOT>/uninstall/uninstallCSCOcmnm

Verifying Uninstallation of Cisco MNM

After uninstalling Cisco MNM, you should verify the uninstallation. Use the following procedure to verify that the Cisco MNM package is not installed:

Step 1 Type pkginfo CSCOcmnm.

The following message should appear:

ERROR: information for "CSCOcmnm" was not found

Step 2 Type pkginfo | grep EM to verify that no Cisco MNM Element Managers are installed.

Step 3 Type pkginfo CSCOcmcv to verify that CiscoView is not installed.

The following message should appear:

ERROR: information for "CSCOcmcv" was not found

Cisco MNM is uninstalled.

Uninstalling Cisco EMF

You must uninstall Cisco MNM before uninstalling Cisco EMF. When Cisco EMF is deinstalled, all Cisco EMF processes are automatically stopped. If ObjectStore was installed as part of the Cisco EMF installation, it is removed during uninstallation. If ObjectStore was installed as a separate package before the Cisco EMF installation, ObjectStore still remains installed after Cisco EMF is deinstalled.

Use the following procedure to uninstall Cisco EMF:

Step 1 As a superuser (su), log in to the machine where Cisco EMF is installed.

Step 2 Ensure that Cisco MNM has been deinstalled.

Step 3 At the command line prompt, enter the following command to change to the Cisco EMF bin directory:

cd /opt/<CEMF_ROOT>/bin

Step 4 At the command line prompt, enter:

./cemfinstall -remove

Step 5 Choose an option from the menu.

For more details, see the Cisco Element Management Framework Installation and Administration Guide at: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cemf/3_2/install/index.htm.

Troubleshooting Common Installation Problems

Carefully following the Planning and Installation Checklist, will avoid most installation pitfalls. If a problem does occur, check this section for troubleshooting guidelines.

Related Topics

"Troubleshooting Cisco MNM"

"Problems During Element Manager Installation or Deinstallation" in the Cisco Element Management Framework Installation and Administration Guide.

Table 2-8 Troubleshooting Installation Problems

Problem

Suggested Steps

You get the message, "Cannot connect to session" when you try to start a Cisco MNM session.

Make sure Cisco EMF is running.

•If Cisco EMF is not running, start it; then retry starting Cisco MNM.

•If Cisco EMF is running, check to see if the IP address or host name of the Cisco MNM server has changed since Cisco MNM was installed. If so, follow the steps described for the next problem.

You get the message, "System IP address does not match databased address" when you try to start Cisco EMF.

This may be caused by a change in the IP address or host name of the Cisco MNM server after Cisco MNM was installed. To correct the problem:

1. Stop Cisco EMF:

/opt/cemf/bin/cemf stop

2. If needed, update the IP address in Cisco EMF:

/opt/cemf/bin/cemf updateIP -m

You are prompted for the new IP address. Enter the new IP address.

3. If needed, update the host name in Cisco EMF:

/opt/cemf/bin/cemf updateName -m

You are prompted for the new host name. Enter the new name.

4. Restart Cisco EMF.

/opt/cemf/bin/cemf start

Note If the Management server address or name has changed in a distributed configuration, make the necessary changes on both the Management server and the Presentation server. If the Presentation server address or name has changed, make the changes on the Presentation server only.

Password problems

Reset the password.

License challenges

Verify that:

•The license file (a file with the extension.lic) is present in the /opt/CSCOcemf/license directory.

•The license has not expired. If it has, get a new license at http://cco.cisco.com/kobayashi/sw-center/sw-registration.shtml. For instructions, see Task 6: Obtaining a Cisco EMF License.

•The license is a multi-user license.

•The license file was not issued for a different machine. The license is machine-specific; you cannot move a license file from one machine to another but must get a new license for your current machine.

Uninstallation problem

Make sure you are uninstalling in the correct sequence. Before uninstalling Cisco EMF, you must uninstall Cisco MNM. Before uninstalling Cisco MNM, make sure that Cisco EMF is running.