installation guide for cisco media gateway manager 5.0 ... · 2.1.2 updating the system parameters...

Cisco Media Gateway Manager 5.0 Installation Guide

Corporate HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 526-4100

Text Part Number: OL-5460-01

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco Media Gateway Manager 5.0 Installation GuideCopyright © 1998-2005 Cisco Systems, Inc. All rights reserved.

CCSP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0501R)

OL-5460-01

C O N T E N T S

Preface vii

Audience vii

Conventions viii

Installation Overview viii

Obtaining Documentation ix

Cisco.com ix

Ordering Documentation ix

Documentation Feedback ix

Obtaining Technical Assistance x

Cisco Technical Support Website x

Submitting a Service Request x

Definitions of Service Request Severity xi

Obtaining Additional Publications and Information xi

C H A P T E R 1 System Requirements 1-1

1.1 Cisco MGM Server Requirements 1-1

1.1.1 Server Specifications 1-2

1.1.2 Disk Space Specifications 1-3

1.1.3 Partition Specifications 1-4

1.2 Cisco MGM Client Requirements 1-5

1.3 Oracle Licensing for Cisco MGM 1-6

1.3.1 Oracle Enterprise Edition 1-8

1.3.1.1 Cisco MGM with Oracle EE (Example A) 1-8

1.3.1.2 Cisco MGM with Oracle EE (Example B) 1-8

1.3.2 Cisco MGM High Availability Option 1-8

1.4 Installation Prerequisites 1-9

1.4.1 Overview of Sudo Commands 1-9

1.4.2 Explanation of the mgms-start Command 1-10

1.4.3 Explanation of the mgms-stop Command 1-11

C H A P T E R 2 Installing the Cisco MGM Server and Oracle9i 2-1

2.1 Installing Cisco MGM 5.0 and Oracle9i on the Same Workstation 2-1

2.1.1 Installing Oracle9i 2-1

2.1.1.1 Setting the Environment for Installation 2-2

iiiCisco Media Gateway Manager 5.0 Installation Guide

Contents

2.1.1.2 Installing the Oracle9i Software with the .rsp Response File Provided by Cisco 2-4

2.1.1.3 Downloading the 9.2.0.6 Patch for Oracle9i 2-6

2.1.1.4 Installing the 9.2.0.6 Patch for Oracle9i 2-7

2.1.1.5 Downloading Oracle Patch 4067938 2-8

2.1.1.6 Downloading the Oracle Patch Installer 2-8

2.1.1.7 Installing Oracle Patch 4067938 2-9

2.1.2 Updating the System Parameters 2-9

2.1.3 Installing the Cisco MGM Server and Database 2-11

2.2 Setting Up Sudo 2-13

C H A P T E R 3 Installing Cisco MGM GateWay/CORBA 5.0 3-1

3.1 Installing Cisco MGM GateWay/CORBA 5.0 3-1

3.2 Changing the Default Cisco MGM GateWay/CORBA 5.0 Port 3-3

3.2.1 Configuring the Port Number for Cisco MGM GateWay/CORBA 5.0 3-3

3.2.2 Configuring the Port Number for the Cisco MGM Notification Server 3-3

C H A P T E R 4 Installing the Cisco MGM 5.0 Client 4-1

4.1 Installing the Cisco MGM Client on Microsoft Windows 4-1

4.1.1 Installing the Cisco MGM Client 4-1

4.1.2 Specifying the Default Browser to Display the Online Help 4-2

4.1.2.1 Special Considerations when Proxy Server Is Enabled 4-2

4.2 Starting the Cisco MGM Client in Microsoft Windows 4-3

4.3 Installing the Cisco MGM Client on Sun Solaris 4-4

4.3.1 Installing the Cisco MGM Client 4-4

4.3.2 Requirements to Display the Online Help 4-5

4.3.2.1 Special Considerations when Proxy Server Is Enabled 4-5

4.4 Starting the Cisco MGM Client in Sun Solaris 4-5

C H A P T E R 5 Uninstalling Cisco MGM, and the Oracle Database 5-1

5.1 Uninstalling the Cisco MGM Server 5-1

5.2 Uninstalling the Cisco MGM Client on Microsoft Windows 5-3

5.3 Uninstalling the Cisco MGM Client on Sun Solaris 5-4

5.4 Uninstalling the Oracle Software 5-4

5.5 Deleting the EMS Information From the Oracle Database 5-5

A P P E N D I X A Installation Error Messages A-1

A.1 Cisco MGM Client Installation Error Messages A-1

A.2 Cisco MGM Server Installation Error Messages A-2

ivCisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01

Contents

A P P E N D I X B Mounting and Unmounting CDs on Sun Solaris B-1

B.1 Mounting a Local CD-ROM Drive B-1

B.2 Mounting a Remote CD-ROM Drive B-2

B.3 Unmounting a Local CD-ROM Drive B-4

B.4 Unmounting a Remote CD-ROM Drive B-4

A P P E N D I X C Cisco Info Center Product Integration Policy Packs C-1

C.1 Update Distribution Files C-2

C.1.1 CIC36xPatch002MGM50.tar Readme File C-2

IN D E X

vCisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01

Contents

viCisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01

Preface

This guide explains how to install Cisco Media Gateway Manager (Cisco MGM) 5.0.

Cisco Media Gateway Manager (MGM) is the element management system (EMS) for the Cisco MGX 8880 Media Gateway and Cisco MGX 8850 for voice solutions based on VoIP technologies. Cisco MGM supports fault, configuration, performance, and security management functional areas. Cisco MGM also serves as a foundation for integration into a larger overall operations support system (OSS) environment by providing northbound gateway interfaces to higher layer management systems.

Note The Cisco MGM release notes are available on the product CD and online at http://www.cisco.com/en/US/products/sw/netmgtsw/ps1920/prod_release_notes_list.html.

Cisco MGM CORBA GateWay is an architectural component of Cisco MGM that provides northbound EMS-to-network management system (NMS) interface mediation. Cisco MGM CORBA GateWay enables service providers to integrate Cisco MGM with their existing Operations Support Systems (OSSs) by using standardized open interfaces.

AudienceThe primary audience for this guide includes network operations personnel and system administrators who are responsible for the Cisco MGX8880 Media Gateway and Cisco MGX8850 network management. This guide assumes the reader is familiar with the following products and topics:

• Cisco MGX8880 Media Gateway

• Cisco MGX8850

• Basic internetworking terminology and concepts

• Network topology and protocols

• Microsoft Windows 2000 Professional, XP, and NT 4.0

• Sun Microsystems Solaris administration

• Oracle database administration

viiCisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01

http://www.cisco.com/en/US/products/sw/netmgtsw/ps1920/prod_release_notes_list.html

Preface Conventions

ConventionsThis document uses the conventions listed in Table 1.

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the publication.

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Tip Means the following information will help you solve a problem.

Installation OverviewThis section describes the typical installation workflow for Cisco MGM.

1. Check your system requirements before attempting to install Cisco MGM 5.0. See Chapter 1, “System Requirements” for further information.

2. For a new server installation, see Chapter 2, “Installing the Cisco MGM Server and Oracle9i” for further information.

3. To install Cisco MGM GateWay/CORBA 5.0, see Chapter 3, “Installing Cisco MGM GateWay/CORBA 5.0” for further information. The Cisco MGM GateWay/CORBA option is a CORBA-based interface that provides higher-layer management systems with information for all Cisco MGM-supported NEs. You can install Cisco MGM GateWay/CORBA when you install the Cisco MGMserver or you can install Cisco MGM GateWay/CORBA separately after the server installation.

Note You must purchase a separate license for Cisco MGM GateWay/CORBA 5.0. The Cisco MGM 5.0 license does not include a license for Cisco MGM GateWay/CORBA 5.0.

Table 1 Document Conventions

Item Convention

Commands and keywords boldface font

Variables for which you supply values italic font

Displayed session and system information screen font

Information you enter boldface screen font

Variables you enter italic_screen font

Menu items and button names boldface font

Selecting a menu item Option > Network Preferences

viiiCisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01

Preface Obtaining Documentation

4. To install the Cisco MGM 5.0 client, see Chapter 4, “Installing the Cisco MGM 5.0 Client” for further information.

Obtaining DocumentationCisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.comYou can access the most current Cisco documentation at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:


You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering DocumentationYou can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

• Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).

Documentation FeedbackYou can send comments about technical documentation to [email protected].

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco SystemsAttn: Customer Document Ordering170 West Tasman DriveSan Jose, CA 95134-9883

We appreciate your comments.

ixCisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01

http://www.cisco.com/univercd/home/home.htm


http://www.cisco.com/public/countries_languages.shtml

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

http://www.cisco.com/en/US/partner/ordering/index.shtml

Preface Obtaining Technical Assistance

Obtaining Technical AssistanceFor all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support WebsiteThe Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do

Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.

Submitting a Service RequestUsing the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)EMEA: +32 2 704 55 55USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

xCisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01

http://www.cisco.com/techsupport

http://tools.cisco.com/RPF/register/register.do

http://www.cisco.com/techsupport/servicerequest


Preface Obtaining Additional Publications and Information

Definitions of Service Request SeverityTo ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is “down,” or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and InformationInformation about Cisco products, technologies, and network solutions is available from various online and printed sources.

• Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

• The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

• Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

• Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

• iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

xiCisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01


http://www.cisco.com/go/marketplace/

http://cisco.com/univercd/cc/td/doc/pcat/

http://www.ciscopress.com

http://www.cisco.com/packet


Preface Obtaining Additional Publications and Information

• Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

• World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html

xiiCisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01


http://www.cisco.com/ipj

http://www.cisco.com/en/US/learning/index.html

Cisco Media GOL-5460-01

C H A P T E R 1
System Requirements
This chapter describes what is required to install Cisco MGM. It contains the following sections:

• 1.1 Cisco MGM Server Requirements

• 1.2 Cisco MGM Client Requirements

• 1.3 Oracle Licensing for Cisco MGM

• 1.4 Installation Prerequisites

Note Although Cisco makes every attempt to ensure the availability of third-party hardware and software platforms specified for Cisco MGM, Cisco reserves the right to change or modify system requirements due to third-party vendor product availability or changes that are beyond Cisco’s control.

1.1 Cisco MGM Server RequirementsThe Cisco MGM server runs on Sun Solaris 8, hardware release 02/02 (or later), on a Sun SPARC-based server.

Performance depends on the size of the network and the usage pattern of management tasks. Typical server installations include a Sun Fire V240 server (for small networks), or a Sun Fire V480 server (for medium networks), configured as shown in Table 1-1 (if the Cisco MGM server and Oracle9i run on the same server).

Note Cisco MGM is capable of using a nonlocal database. For information about this configuration, contact your Cisco account representative.

Caution During the Solaris 8 installation, you are prompted to select software to install. (The default is End User System Support—769 MB.) It is recommended that you select Entire Distribution plus OEM support—1491 MB.

Caution Configure your file systems to allow large files. By default, no single file can be larger than 2 GB. This can be problematic for large database installations of the Cisco MGM server.

1-1ateway Manager 5.0 Installation Guide

Chapter 1 System Requirements1.1 Cisco MGM Server Requirements

To install the Cisco MGM server, Cisco recommends that you have:

• Sun Solaris patches Generic_117350-06 or later, available on SunSolve Online at http://sunsolve.sun.com.

Note These Solaris patches might be superseded by more recent patches. Visit Sun’s website for the most up-to-date patch information.

Note While installing Solaris patches, you might receive a message saying “This patch is obsoleted by patch number, which has already been applied to this system.” This message indicates that an updated version of the patch is already installed, and no action is required.

• Sun Microsystems Java Runtime Environment (JRE) (installed automatically for both server and GateWay/CORBA 5.0 but not for the Cisco MGM client).

• Sun Microsystems JRE Standard Edition version 1.4.2.

• Oracle9i software plus the 9.2.0.6 patch.

• Oracle Patch 4067938

• Oracle9i licenses for Sun Solaris.

Note Oracle licenses can be purchased by the server processor or by the named user. For more information on Oracle9i named users, see the Cisco Media Gateway Manager 5.0 User Guide.

• Available swap space (see Table 1-4 for swap space requirements).

• CD-ROM drive.

1.1.1 Server SpecificationsTable 1-1 shows sample configurations when the Cisco MGM server and Oracle9i database are installed on the same workstation. The Cisco MGM server can run on any platform that supports Sun Solaris 8. The following sample configurations are provided as general guidelines for configuring your Cisco MGM server. It is not mandatory that the Cisco MGM server run on the following platforms.

Table 1-1 Sample Configurations for Installing the Cisco MGM Server and Oracle9i on the Same Workstation

Network Size Oracle Database CPUs RAM

Max No. of MGX-MGWs with PM

Max No. of MGX-MGWs without PM

Max No. of Client

Disk Space with PM

Disk Space without PM

Small Enterprise Edition 2 (1.2GHz) 4 GB 5 10 30 130 GB 42 GB

Medium Enterprise Edition 4 (1.2GHz) 4 GB 25 50 50 214 GB 68 GB

Large Enterprise Edition 8 (1.2GHz) 16 GB 50 100 100 434 GB 103 GB

1-2Cisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01

http://sunsolve.sun.com

http://sunsolve.sun.com


Note The installation procedure assumes that you are performing the installation directly from the workstation. X-terminal sessions and Reflection-X are supported for the Cisco MGM server installation. Exceed is not supported for remote installation of Cisco MGM 5.0 or Oracle 9i.

Table 1-1 displays the resulting maximum number of MGX-MGWs with fully populated VXSM cards the server manages for each sample configuration.

The following list details the server configuration parameters and particularly the effect of changes in each parameter on the maximum number of NEs the server can manage:

• Network Size—If the network size is increased from the size detailed in Table 1-1, more resources are reserved for the higher number of NEs to be managed. For example, if the server listed in the small configuration is reset for medium, and the rest of the configuration parameters are kept constant, the server can manage fewer NEs.

• Oracle Database Type—Standard Edition is only allowed in the small configuration. In the small configuration, performance is identical whether Standard Edition or Enterprise Edition is used.

• CPUs—If the number of CPUs is reset to a higher number than the suggested number detailed in Table 1-1 (for example, 4 CPUs rather than the suggested 2), the server can manage a higher number of NEs. If the number of CPUs is reset to less than the suggested number detailed in Table 1-1, the server can manage a lower number of NEs.

• CPU Speed—If the CPU speed is reset higher than the suggested speed detailed in Table 1-1, the server can manage a higher number of NEs. If the CPU speed is lower than the suggested speed detailed in Table 1-1, the server can manage a lower number of NEs.

• RAM—If the size of RAM is reset higher than the suggested size detailed in Table 1-1, the server can manage a higher number of NEs. If the size of RAM is reset lower than the suggested amount detailed in Table 1-1, the server can manage a lower number of NEs.

• Disk Space with PM Collection—This configuration parameter is described in the following sections: 1.1.2 Disk Space Specifications and 1.1.3 Partition Specifications.

• Disk Space without PM Collection—This configuration parameter is described in the following sections: 1.1.2 Disk Space Specifications and 1.1.3 Partition Specifications.

Note The disk space values listed in Table 1-1 are for new installations of Cisco MGM 5.0 only.

1.1.2 Disk Space SpecificationsTable 1-2 shows disk space requirements based on network size and PM collection status when you are installing the Cisco MGM server and Oracle9i database on the same workstation.

Table 1-2 Disk Space Requirements for Installing the Cisco MGM Server and Oracle9i on the

Same Workstation

Network Size No. of NEs Disk Space with PM Collection Disk Space Without PM Collection

Small 30 130 GB 42 GB

Medium 50 214 GB 68 GB

Large 100 434 GB 103 GB


OL-5460-01



Table 1-3 shows disk space requirements based on network size and PM collection status when you are installing the Cisco MGM server and Oracle9i database on separate workstations.


1.1.3 Partition SpecificationsTable 1-4 shows partition specifications for installing the Cisco MGM server and Oracle9i on the same server.

Note The partition sizes listed in Table 1-4 are for new installations of Cisco MGM 5.0 only. See Table 1-4 for information about disk directories.

Table 1-3 Disk Space Requirements for Installing Cisco MGM Server and Oracle9i on Separate

Workstations

Cisco MGM Server

Network Size No. of NEs Disk Space

Small 30 12 GB

Medium 50 18 GB

Large 100 54 GB

Oracle9i Database Server

Network Size No. of NEs Disk Space with PM Collection Disk Space Without PM Collection

Small 30 99 GB 38 GB

Medium 50 208 GB 62 GB

Large 100 398 GB 94 GB

Table 1-4 Partition Sizing for Installing the Cisco MGM Server and Oracle9i on the Same Server

Network Size No. of NEs root swap oraclesw9i db01 db02 db031

1. If PM collection is not enabled, the /db03 directory requires 5 GB for a small network, 8 GB for a medium network, and 14 GB for a large network.

db042


db053

3. The /db05 directory is required only if you want to install the Cisco MGM database in ARCHIVELOG mode.

Total with PM Collection

Total Without PM Collection

Small 30 4 GB 6 GB 5 GB 5 GB 6 GB 40 GB 30 GB 8 GB 130 GB 42 GB

Medium 50 4 GB 12 GB 5 GB 8 GB 16 GB 90 GB 70 GB 10 GB 214 GB 68 GB

Large 100 4 GB 48 GB 5 GB 10 GB 26 GB 190 GB 140 GB 12 GB 434 GB 130 GB


OL-5460-01

Chapter 1 System Requirements1.2 Cisco MGM Client Requirements

Note The partition sizes listed in Table 1-5, Part 1 and Table 1-5, Part 2 are for new installations of Cisco MGM R5.0 only. See Table 1-4 for information about disk directories.

1.2 Cisco MGM Client RequirementsTo install the Cisco MGM client, Cisco recommends that you have a Sun Solaris workstation or Microsoft Windows PC configured as shown in Table 1-6.

Table 1-5, Part 1 Partition Sizing for Installing the Cisco MGM Server and Oracle9i on Separate Workstations

Cisco MGM Server

Network Size

No. of NEs root swap oraclesw9i db01 db02 db03 db04 db05 Total

Small 30 4 GB 6 GB 4 GB — — — — — 12 GB

Medium 50 4 GB 12 GB 4 GB — — — — — 18 GB

Large 100 4 GB 48 GB 4 GB — — — — — 54 GB

Table 1-5, Part 2 Partition Sizing for Installing the Cisco MGM Server and Oracle9i on Separate Workstations

Oracle9i Database Server

Network Size

No. of NEs root swap oraclesw9i db01 db02 db031


db042


db053

3. The /db05 directory is required only if you want to install the Cisco MGM database in ARCHIVELOG mode.

Total with PM Collection

Total Without PM Collection

Small 30 2 GB 4 GB 5 GB 5 GB 6 GB 40 GB 30 GB 8 GB 99 GB 38 GB

Medium 50 4 GB 6 GB 5 GB 8 GB 16 GB 90 GB 70 GB 10 GB 208 GB 62 GB

Large 100 4 GB 12 GB 5 GB 10 GB 26 GB 190 GB 140 GB 12 GB 398 GB 94 GB

Table 1-6 Minimum Requirements for the Cisco MGM Client

Platform1Network Size RAM2 CPUs

CPU Speed

Free Disk Space3 Other

Sun Ultra 5 workstation4

Small 512 MB 1 333 MHz 401 MB • Sun Solaris 8 with Common Desktop Environment (CDE), with graphics support for 16-bit color or higher

• Netscape Navigator 4.79, or equivalent

Medium 512 MB

Large 512 MB


OL-5460-01

Chapter 1 System Requirements1.3 Oracle Licensing for Cisco MGM

1.3 Oracle Licensing for Cisco MGMThis section explains how to calculate the total number of Oracle Named User Plus licenses required for your Cisco MGM 5.0 server and client installations.

• 1.3.1 Oracle Enterprise Edition

• 1.3.2 Cisco MGM High Availability Option

Note See the Oracle website for further details on Oracle licensing definitions and requirements.

Oracle’s technology products, including the Oracle database required for use with Cisco MGM, are licensed using one of two possible metrics. Which metric to use normally depends on which will result in a lower price for the database. If for some reason the number of database users cannot be counted, the Processor metric must be used. However, in the case of a Cisco MGM environment, database users normally can be counted:

• Processor: This metric is defined as the number of processors on the server on which the Oracle database is installed and/or running. This option must be used in environments in which software users cannot easily be identified or counted (not normally the case in a Cisco MGM environment).

• Named User Plus: This metric is used in environments in which users can be identified and counted. Named User Plus includes both human-operated and automated devices. All human-operated and automated devices that access the program must be licensed. A Named User Plus license may access the program on any instances on which it is deployed, provided that the minimum license requirement on each server is met.

In the context of a Cisco MGM environment, human-operated device means any device operated by a user who has direct or indirect access to Cisco MGM. Direct access is gained through a user account on Cisco MGM that allows access to Cisco MGM through the client GUI. Indirect access is possible

Pentium III or Pentium 4 class PC

Small 512 MB 1 450 MHz 401 MB • Windows 2000 Professional with Service Pack 3, Windows NT 4.0 with Service Pack 4 or higher, or Windows XP Professional, each with graphics support for 16-bit color or higher

• Microsoft Internet Explorer 5.5, Netscape 4.76 or higher, with JavaScript enabled

Medium 512 MB

Large 512 MB

1. X-terminal sessions are not supported.

2. Cisco recommends setting the client virtual memory to two times the size of the physical memory (two times the amount of RAM).

3. Disk space requirements are for Cisco MGM client software only.

4. It is not mandatory that the Cisco MGM client run on a Sun Ultra 5 workstation. You can run the Cisco MGM client on other comparable Sun workstations.

Note For a multiclient operation, the Cisco MGM clients must be installed on workstations separate from the Cisco MGM server. For a single-client operation, the Cisco MGM client and server can be installed on the same workstation or on separate workstations. Do not install the client on the server in a production environment as performance will be a issue.

Table 1-6 Minimum Requirements for the Cisco MGM Client (continued)

Platform1Network Size RAM2 CPUs

CPU Speed

Free Disk Space3 Other


OL-5460-01


through a user account on a higher-layer Operations Support System (OSS), which in turn communicates with Cisco MGM through either Cisco MGM GateWay/CORBA or SNMP enhanced by a robust trap mechanism (RTM). RTM provides a reliable mechanism to handle and deliver the SNMP traps to network managers. It detects missing traps and retrieves the lost traps by using a sequence number for each trap. Automated users include the network elements (NEs) managed by Cisco MGM and the Cisco MGM server itself.

Figure 1-1 shows an example Cisco MGM environment to illustrate identifying the human and automated database users that need to be counted.

Figure 1-1 Example Cisco MGM Environment

In the example shown in Figure 1-1 there are two independent Cisco MGM servers and Oracle database instances. There are four NEs, one of which is managed by both Cisco MGM servers. There is one direct Cisco MGM user represented and one indirect user represented. So in this example the total number of Oracle named users is as follows:

• Cisco MGM servers: 2*

• NEs: 4**

• Cisco MGM Users: 1**

• Higher-layer OSS Users: 1

• Total Named User Plus: 8 = 2 + 4 + 1 + 1

*Because of the self monitor feature of Cisco MGM, a Cisco MGM server itself is considered an automated user of the database and is therefore counted.

**A Named User Plus license entitles the user to access Oracle on any instances where it is deployed. So if a user has access to multiple Cisco MGM servers, only a single license is needed per user. Also, if an NE is managed by multiple Cisco MGM servers, only a single license is needed per NE.

NUP NUP

NUPNUP

NUP

NUPNUPNUPNUP

Higher LayerOSS

GateWay/CORBA

Cisco MGM +Oracle Database

(Instance 1)

Cisco MGM +Oracle Database(Instance 2)

Cisco MGM-Managed NEs

Oracle Named User Plus License

Cisco MGM GUI User with accounts on both MGM 1 and 2

Higher LayerOSS User

1134

40


OL-5460-01


This example explains how to count the named users, but, of course, the number of named users required is the larger of either 1) the actual count or 2) the required minimum. The required minimum will vary depending on the edition of the Oracle database (for example, enterprise).

1.3.1 Oracle Enterprise EditionDue to the scalability features included, Oracle Database Enterprise Edition (EE) is required for Cisco MGM servers managing medium- to large (more than 200 NEs) Cisco MGM installations.

1.3.1.1 Cisco MGM with Oracle EE (Example A)

A service provider has 800 NEs and a data center with 10 Cisco MGM client workstations. 100 employees in the data center are authorized to use the Cisco MGM client. Some of the employees in the data center share the same Cisco MGM account (username/password). Cisco MGM is running on a Sun V880 with 8 processors and 32 GB RAM.

• Named User Plus: 1) Minimum = 8 processors x 25 users/processor = 200 or 2) Count = 800 licenses for NEs + 100 licenses for data center personnel + 1 Cisco MGM server = 901

Result: 901 Named User Plus licenses are required

• Processor: 8 Processor licenses

1.3.1.2 Cisco MGM with Oracle EE (Example B)

The same service provider customer as in “1.3.1.1 Cisco MGM with Oracle EE (Example A)” decides to enable Cisco MGM GateWay/CORBA and connect to a higher-layer OSS that handles inventory management. There are 20 employees in the data center authorized to access the inventory system; 5 of them are also Cisco MGM users (that is, they are a subset of the 100 Cisco MGM users identified in “1.3.1.1 Cisco MGM with Oracle EE (Example A)”). In this case, the total number of human users is:

95 Cisco MGM-only users + 15 inventory system-only users + 5 Cisco MGM/inventory system users or 115 human named users.

As a result of adding the OSS and related users, the total number of named users required has increased from 901 to 916.

1.3.2 Cisco MGM High Availability OptionIn the Cisco MGM High Availability (HA) architecture, the server nodes are configured in fail-over cluster. In this configuration, the first node acts as a primary node. If the primary node fails, another node in the cluster acts as the primary node. In this type of environment, Oracle permits licensed Oracle Database customers to run the Database on an unlicensed spare computer for up to a total of ten separate days in any given calendar year. Any other use requires the environment to be fully licensed. Additionally, the same metric must be used when licensing the databases in a fail-over environment.


OL-5460-01

Chapter 1 System Requirements1.4 Installation Prerequisites

1.4 Installation PrerequisitesBefore installing the Cisco MGM server and the Oracle9i database on your Sun Solaris 8 server, verify the following:

• You have the correct Solaris patches installed. (See 1.1 Cisco MGM Server Requirements.)

• You have the correct version of Oracle9i—Enterprise Edition, for Sun Solaris.

• You meet all of the system requirements described in this chapter.

• The ping command is included in your Path environment variable.

• Decide whether or not you want to install the Cisco MGM database in ARCHIVELOG mode. If you plan to perform hot database backups, ARCHIVELOG mode is required.

• Verify that your /mgm_backup directory (the disk directory for the backed-up database and configuration files) is at least as big as the total sum of your database data files. If the /mgm_backup directory is not large enough to accommodate all of your database data files, the backup will not proceed.

• Decide which nonroot users you want to be able to run Cisco MGM UNIX commands. (See the 1.4.1 Overview of Sudo Commands.)

1.4.1 Overview of Sudo CommandsSudo software (freeware) version 1.6.6 is bundled with the Cisco MGM 5.0 software. The sudo software enables nonroot UNIX users to run the following UNIX commands:

• mgms-start

• mgms-abort

• mgms-stop

• mgms-stop-service

• showmgm

• prune_auditlog.sh

• prune_errlog.sh

• prune_audittrail.sh

• prune_fm.sh

• prune_pm.sh

• prune_ne.sh

• prune_server_monitor.sh

• prune_admin_job_table.sh

During the Cisco MGM server installation, the setup program prompts you to specify the name of the UNIX group to which you want to assign administrator privileges. By default, this group is set to the root group. If you specify a group other than root, the setup program verifies that the UNIX group exists on the system and adds entries to the /etc/sudoers file. Entries in this file reflect the commands that the specified UNIX group can run by using the sudo command.


OL-5460-01


The following entries in the /etc/sudoers file reflect the commands that can be run as nonroot:

%MGM_UNIX_group hostname=(root) NOPASSWD: \/opt/CiscoMGMServer/bin/mgms-start, \/opt/CiscoMGMServer/bin/mgms-abort, \/opt/CiscoMGMServer/bin/mgms-stop, \/opt/CiscoMGMServer/bin/mgms-stop-service, \/opt/CiscoMGMServer/bin/showmgm,\/opt/CiscoMGMServer/bin/prune_auditlog.sh, \/opt/CiscoMGMServer/bin/prune_errlog.sh, \/opt/CiscoMGMServer/bin/prune_audittrail.sh, \/opt/CiscoMGMServer/bin/prune_fm.sh, \/opt/CiscoMGMServer/bin/prune_pm.sh, \/opt/CiscoMGMServer/bin/prune_ne.sh, \/opt/CiscoMGMServer/bin/prune_server_monitor.sh, \/opt/CiscoMGMServer/bin/prune_admin_job_table.sh

1.4.2 Explanation of the mgms-start CommandA complete set of administrative command scripts is added to the application during installation. One command automatically starts the Cisco MGM server processes every time the server is started. The server processes can also be started or stopped manually as necessary; the scripts are located in the /opt/CiscoMediaGatewayManagerServer/bin directory.

The mgms-start command sets the appropriate environment variables and starts the Cisco MGM server. The amount of time it takes for the Cisco MGM server to start varies based on the number of NEs in the configuration and the size of the database. Use mgms-start only when the Cisco MGM server has stopped.

To start the Cisco MGM server:

Step 1 Log into the Cisco MGM server workstation as the root user.

Step 2 On the command line, enter the following command:

mgms-start

Note The mgms-start command can take from 0 to 5 minutes to start after the command has finished execution. This is because NE services and gateway services (if enabled) are still initializing for all the NEs that are deployed. Wait 5 minutes after entering the mgms-start command; then, enter the showmgm command. The NE service corresponding to all the deployed NEs should have started.


OL-5460-01


1.4.3 Explanation of the mgms-stop CommandThe mgms-stop command stops the Cisco MGM server. The stop procedure shuts down the server and cleans all memory and connections. The overall process takes less than five minutes.

To stop the Cisco MGM server:

Step 1 Log into the Cisco MGM server workstation as the root user.

Step 2 On the command line, enter the following command:

mgms-stop


OL-5460-01



OL-5460-01


C H A P T E R 2
Installing the Cisco MGM Server and Oracle9i
This chapter describes the installation process for Cisco MGM 5.0 and Oracle9i. It contains the following sections:

• 2.1 Installing Cisco MGM 5.0 and Oracle9i on the Same Workstation, page 2-1

• 2.2 Setting Up Sudo, page 2-13

Note For an explanation of error messages that you might encounter during the server installation, see Appendix A, “Installation Error Messages.”

Note If you need instructions to mount or unmount CDs, see Appendix B, “Mounting and Unmounting CDs on Sun Solaris.”

2.1 Installing Cisco MGM 5.0 and Oracle9i on the Same Workstation

This section describes how to install the Cisco MGM server and Oracle9i on the same Sun Solaris 8 server:

• 2.1.1 Installing Oracle9i

• 2.1.2 Updating the System Parameters

• 2.1.3 Installing the Cisco MGM Server and Database

Note The C shell is assumed for all UNIX commands entered during the server installation.

2.1.1 Installing Oracle9iThis section provides supporting information to assist you with the Oracle9i installation. You need to install the following components in this order:

1. Oracle 9.2

2. 9.2.0.6 Patch for Oracle9i


Chapter 2 Installing the Cisco MGM Server and Oracle9i2.1 Installing Cisco MGM 5.0 and Oracle9i on the Same Workstation

3. Oracle Patch 4067938

Use this information with Oracle’s documentation:

• 2.1.1.1 Setting the Environment for Installation

• 2.1.1.2 Installing the Oracle9i Software with the .rsp Response File Provided by Cisco

• 2.1.1.3 Downloading the 9.2.0.6 Patch for Oracle9i

• 2.1.1.4 Installing the 9.2.0.6 Patch for Oracle9i

• 2.1.1.5 Downloading Oracle Patch 4067938

• 2.1.1.6 Downloading the Oracle Patch Installer

• 2.1.1.7 Installing Oracle Patch 4067938

2.1.1.1 Setting the Environment for Installation

To set the environment for installation, log in as the root user and complete the following steps:

Step 1 Verify that the disk directories shown in Table 2-1 exist.

Step 2 (Optional) If you want to use your existing partitions, enter the following commands from the / directory:

ln -s /partition_name_1 /db01ln -s /partition_name_2 /db02ln -s /partition_name_3 /db03ln -s /partition_name_4 /db04ln -s /partition_name_5 /db05ln -s /partition_name_6 /mgm_backupln -s /partition_name_7 /oraclesw9i

Table 2-1 Disk Directories

Directory Contents

/db01 For the system tablespace used by Oracle

/db02 For the basedata tablespace, the alarmdata tablespace, and the eventdata tablespace used by Cisco MGM

/db03 For the PM metadata tablespace used by Cisco MGM

/db04 For the INDEX tablespace used by Cisco MGM

/db051

1. If you want to install the Cisco MGM database in ARCHIVELOG mode, the /db05 directory is required. ARCHIVELOG mode is required for hot database backups.

For the archived logs

/mgm_backup2

2. The /mgm_backup directory can be a symbolic link to a storage device. Note that performance degrades if you map all of your symbolic links to the same partition and you do not have disk striping.

For the backed-up database and configuration files

/oraclesw9i For the Oracle software

/tftpboot For the TFTP directory

Note Disk partitioning is not required for /tftpboot, but the directory is required.


OL-5460-01


Step 3 If you do not have a TFTP directory, complete the following substeps to create one:

a. Enter the following commands:

mkdir /tftpbootchmod 777 /tftpboot

b. Verify that the TFTP entry in the /etc/inetd.conf file is not commented.

The following example represents a typical TFTP entry in the /etc/inetd.conf file. In this example, the TFTP directory is /tftpboot:

tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot

c. If the TFTP entry is commented, remove the pound sign (#) at the beginning of the line to uncomment it.

Step 4 Enter the following command to create a UNIX group for database administrators:

groupadd -g 3303 dba

Step 5 Enter the following command to create a UNIX account to own the Oracle software:

useradd -g dba -m -s /bin/csh -d /oraclesw9i oracle

Step 6 Enter the following command to change the Oracle user password:

passwd oracle

Enter the new password; then, reenter the password to confirm it.

Step 7 Insert the Cisco MGM 5.0 Server installation CD and enter the following command:

cd /cdrom/cdrom0/disk1/mgms

Step 8 Enter the following command to list the files in the cdrom/cdrom0/disk1/mgms directory:

ls -laR

Note If a list of files is returned, it indicates that you can access the CD-ROM successfully. If no files are visible, or if an error message is returned, refer to Appendix B, “Mounting and Unmounting CDs on Sun Solaris” for mounting the CD-ROM.

Step 9 Enter the following command to copy the default profile to the Oracle home directory:

cp /cdrom/cdrom0/disk1/mgms/cfg/{small | medium | large end}/.cshrc /oraclesw9i/.cshrc

For example, to copy the default profile for a small network, enter:

cp /cdrom/cdrom0/disk1/mgms/cfg/small/.cshrc /oraclesw9i/.cshrc

Step 10 Enter the following command to determine what type of applications you can run on your operating system (OS):

isainfo -v

The output indicates you can run 32-bit applications.

If the output reads “32-bit sparcv9 kernel modules,” you can run only 32-bit applications.

Note Cisco recommends being able to run 32-bit applications.


OL-5460-01


Step 11 Complete the following options:

• Enter the following command to copy the svrcustom.rsp response file to the local disk:

cp /cdrom/cdrom0/disk1/mgms/svrcustom.rsp /oraclesw9icp /cdrom/cdrom0/disk1/mgms1/mgms/patchset.rsp /oraclesw9icp /cdrom/cdrom0/disk1/mgms1/mgms/oui.rsp /oraclesw9i

• Enter the following command to copy the svrcustom_std.rsp response file to the local disk:

cp /cdrom/cdrom0/disk1/mgms/svrcustom_std.rsp /oraclesw9icp /cdrom/cdrom0/disk1/mgms1/mgms/patchset.rsp /oraclesw9icp /cdrom/cdrom0/disk1/mgms1/mgms/oui.rsp /oraclesw9i

Step 12 Enter the following command to copy the patchset.rsp response file to the /oraclesw9i directory:

cp /cdrom/cdrom0/disk1/mgms/patchset.rsp /oraclesw9i

Step 13 Enter the following commands to change ownership of the Oracle software directories:

/usr/bin/chown -R oracle:dba /oraclesw9i/usr/bin/chown -R oracle:dba /db01/usr/bin/chown -R oracle:dba /db02/usr/bin/chown -R oracle:dba /db03/usr/bin/chown -R oracle:dba /db04/usr/bin/chown -R oracle:dba /db05/usr/bin/chown -R oracle:dba /mgm_backup

Step 14 Enter the following commands to eject the Cisco MGM 5.0 Server installation CD:

cd /eject cdrom

Step 15 Enter the following commands to create a temporary staging area:

cd /mkdir tempchmod 777 /temp

Step 16 If you are using an xterm window or a remote host, enter the following command to enable the xterm connection from the clients:

/usr/openwin/bin/xhost +

2.1.1.2 Installing the Oracle9i Software with the .rsp Response File Provided by Cisco

To install the Oracle9i software with the response file provided by Cisco:

Step 1 Enter the following command to log in as the Oracle user:

su - oracle

Tip To verify the username, enter the id command.

Step 2 Insert disk one of the Oracle9i installation CDs in the CD-ROM drive.

Step 3 Enter the following command to set the display on your terminal:

setenv DISPLAY hostname:0.0


OL-5460-01


Step 4 Enter the following command to verify that the display is set correctly:

echo $DISPLAY

In the output, you should see:

<hostname_or_IP_address>:0.0

Step 5 Complete the following options:

• Enter the following command to start the Oracle Installer:

./cdrom/cdrom0/orcl9201_1/runInstaller -responseFile /oraclesw9i/svrcustom.rsp &

• Enter the following command to start the Oracle Installer:

./cdrom/cdrom0/orcl9201_1/runInstaller -responseFile /oraclesw9i/svrcustom.rsp &

Step 6 At the Inventory Location screen, click OK.

Step 7 The Oracle Universal Installer screen appears and prompts you to run the /tmp/orainstRoot.sh script. Log into another terminal window as the root user and enter the following command:

cd /tmp/

Note The Installer does not prompt you to run the /tmp/orainstRoot.sh script if you have a previous version of Oracle installed on your workstation or if the /var/opt/oracle/oratab file already exists on your workstation.

Step 8 Enter the following command to run the orainstRoot.sh script:

./orainstRoot.sh

Step 9 Return to the Oracle Universal Installer screen and click Continue.

Note The Oracle Universal Installer process might take up to five minutes.

Step 10 The Disk Location dialog box prompts you for disk two of the Oracle9i installation CDs. Return to the terminal window where you ran the ./runInstaller command and press Return on your keyboard to bring up the command prompt.

Step 11 Enter the following commands at the command prompt:

eject cdrom

Step 12 Remove disk one and insert disk two of the Oracle9i installation CDs.

Step 13 Minimize the terminal window.

Step 14 Return to the Disk Location dialog box and change the path to read:

/cdrom/cdrom0/orcl9201_2

Click OK.

Step 15 The Disk Location dialog box prompts you for disk three of the Oracle9i installation CDs. Return to the terminal window where you ran the ./runInstaller command and press Return on your keyboard to bring up the command prompt.

Step 16 Enter the following command at the command prompt:

eject cdrom


OL-5460-01


Step 17 Remove disk two and insert disk three of the Oracle9i installation CDs.

Step 18 Minimize the terminal window.

Step 19 Return to the Disk Location dialog box and change the path to read:

/cdrom/cdrom0/orcl9201_3

Click OK.

Step 20 You are prompted to run /oraclesw9i/product/9.2/root.sh from another window. Log into another terminal window as the root user and enter the following command:

cd /oraclesw9i/product/9.2

Step 21 Enter the following command to run the root.sh script:

./root.sh

Step 22 At the prompt for the local bin directory, enter the following path in the root.sh script:

/oraclesw9i/product/9.2/local/bin

Note The local bin directory needs to be created before running root.sh script.

Step 23 Return to the Oracle Universal Installer screen and click Next.

Step 24 Enter the following commands to eject the CD:

eject cdrom

2.1.1.3 Downloading the 9.2.0.6 Patch for Oracle9i

Note If you already have the 9.2.0.6 patch for Oracle9i installed, you can skip this section.

Verify that the /oraclesw9i directory has enough disk space to download the patch.

To download the 9.2.0.6 patch for Oracle9i:

Step 1 Go to http://metalink.oracle.com and click Login to MetaLink. Enter your Oracle metalink username and password.

Step 2 Click Patches.

Step 3 Click Simple Search.

Step 4 In the Search by Patch Number(s) field, enter 3948480.

Step 5 In the Platform or Language field, choose the Solaris Operating System (SPARC 32-bit) option.

Step 6 Click Go.

Step 7 Click Download. For 32-bit Oracle, download p3948480_9206_SOLARIS.zip.


OL-5460-01


Step 8 As the root user, save the patch to the /oraclesw9i directory and enter the following command to unzip the .zip file:

cd /oraclesw9iunzip p3948480_9204_SOLARIS.zipunzip <patch_zip_filename>

2.1.1.4 Installing the 9.2.0.6 Patch for Oracle9i

To install the 9.2.0.6 patch for Oracle9i:

Step 1 Insert disk one of the Oracle9i installation CDs in the CD-ROM drive.

Step 2 Enter the following command to log into the database workstation as the Oracle user:

su - oracle

Step 3 Enter the following command to install the 9.2.0.6 rdbms server patch:

Note If the Disk Location screen pops up, click Cancel.

cd /oraclesw9i/Disk1./runInstaller -silent -responseFile /oraclesw9i/patchset.rsp

Step 4 At the prompt to run the root.sh script, log into another terminal window as the root user and enter the following commands:

cd /oraclesw9i/product/9.2./root.sh

Step 5 After the script finishes running, return to the prompt popup window and click OK.

Step 6 Click Next.

Step 7 Enter the following commands to eject the CD:

cd /eject cdrom

Step 8 Enter the following set of commands to remove the 9.2.0.6 patch installation files:

rm -rf Disk1 rm -rf p3948480_9206_SOLARIS.zip rm -rf README.html


OL-5460-01


2.1.1.5 Downloading Oracle Patch 4067938

Note If you already have Oracle patch 4067938 installed, you can skip this section.

To download the Oracle patch:





Step 5 In the Platform or Language field, choose the Solaris Operating System (SPARC 32-bit) option.

Step 6 Click Go.

Step 7 Click Download.

Step 8 Save the patch to the location of your choice.

2.1.1.6 Downloading the Oracle Patch Installer

Oracle patch 4067938 requires the Oracle patch installer. To download the Oracle patch installer:





Step 5 In the Platform or Language field, choose Solaris Operating System (SPARC 32-bit).

Step 6 Click Go.


Step 8 In the list of patches returned, click the first patch, which has the latest release number.

Step 9 In the Patch 2617419 window, go to the Platform or Language field and choose Generic Platform (the default).


Step 11 Save the patch to the location of your choice.


OL-5460-01

http://metalink.oracle.com

http://metalink.oracle.com


2.1.1.7 Installing Oracle Patch 4067938

To install Oracle patch 4067938:

Step 1 Log into the database workstation as the Oracle user and enter the following commands:

cd /oraclesw9imkdir oracle_patch

Step 2 Locate the saved patch (4067938) and copy it to the /oraclesw9i/oracle_patch directory.

Step 3 Enter the following sets of commands to unzip the patch file:

unzip p4067938_9206_SOLARIS.zip

Step 4 Enter the following commands to shut down the Oracle listener and all Oracle processes, if they are running:

sqlplus /nologconnect /as sysdbashutdown immediateexitlsnrctl stop

Step 5 Enter the following commands to apply the Oracle security patch:

cd /oraclesw9i/oracle_patch/4067938setenv PATH $ORACLE_HOME/OPatch:$(PATH)/oraclesw9i/oracle_patch/OPatch/opatch apply

2.1.2 Updating the System ParametersTo update the system parameters, log in as the root user and complete the following steps:

Step 1 If you are using an xterm window or a remote host, enter the following command to set the DISPLAY variable:

setenv DISPLAY <hostname_or_IP_address>:0.0


echo $DISPLAY



Step 3 Insert the Cisco MGM 5.0 Server installation CD and enter the following commands:

cd /cdrom/cdrom0/disk1/mgms./mgmsetup.sh


OL-5460-01


The setup program searches for Sun Microsystems JRE version 1.4.2 on your workstation.

Note If JRE is not installed, the setup program starts the Java installation program. Follow the prompts to install JRE. Enter yes at the following binary license code agreement prompt:

Do you agree to the above license terms? [yes or no]

Then, continue updating the system parameters.

Note If the required Solaris patches are missing, including patch 117000-03 or later, you must install them manually. Click Cancel; then, click Quit. Download the patches from SunSolve Online at http://sunsolve.sun.com. After you install the patches, continue updating the system parameters.

Wait for up to 60 seconds while the following message appears:

Installing Cisco Media Gateway Manager server...

Step 4 Click Next at the Introduction screen.

Step 5 At the License Agreement screen, read the license agreement and click the I accept the terms of the license agreement radio button. Click Next.

Step 6 At the Select Products screen, check the Install Cisco Media Gateway Manager Server check box; then, click Next.

Caution Do not check the other check boxes on the Select Products screen.

Note When you choose Install Cisco Media Gateway Manager Server, the High Availability Installation option becomes available. This option applies only to high availability (HA) installations. Do not choose it. To install HA, refer to the High Availability Installation Guide for Cisco Media Gateway Manager 5.0.

Note The license for Cisco MGM GateWay/CORBA is sold separately. If you are using this feature in a production environment, you must purchase the license. You can install Cisco MGM GateWay/CORBA when you install the Cisco MGM server; however, this section assumes that you are installing the two products separately. For more information, see Chapter 3, “Installing Cisco MGM GateWay/CORBA 5.0.”

Step 7 At the Cisco MGM Group Information screen, enter the name of the UNIX group to which you want to assign administrator privileges. Click Next.

Note For information about this feature, see the “1.4.1 Overview of Sudo Commands” section on page 1-9.



OL-5460-01


Step 9 At the Main Options screen, check only the Check system settings check box; then, click Next.

Caution Do not check the other check boxes on the Main Options screen. You will check the other options during the next phase of the installation.

Step 10 At the Select Network Configuration screen, specify the size of your network; then, click Next.

Step 11 At the Update System Parameters screen, check the following check boxes:

• Optimize Cisco MGM database parameters

• Optimize Cisco MGM server parameters

Step 12 Click Next.

Step 13 At the warning screen, click Exit and reboot the system.

2.1.3 Installing the Cisco MGM Server and DatabaseTo install the Cisco MGM server and database, log in as the root user and complete the following steps:

Step 1 If you are using an xterm window or a remote host, enter the following command to set the DISPLAY variable:



echo $DISPLAY





The Cisco MGM server installation begins. Wait for up to 60 seconds while the following message appears:




Step 6 At the Select Products screen, check the Install Cisco Media Gateway Manager Server check box. Click Next.

Step 7 At the Cisco MGM Group Information screen, confirm the name of the UNIX group to which you want to assign administrator privileges. Click Next.


OL-5460-01


Step 8 At the Main Options screen, complete the following substeps:

a. Check the Create Cisco MGM database check box and specify the Oracle source identifier (SID). The default is Cisco MGM5_0.

b. Check the Install Cisco MGM server check box.

Note Uncheck the Check system settings check box. The system settings were checked previously in the “2.1.2 Updating the System Parameters” section on page 2-9.

Caution Do not check the other check boxes on the Main Options screen.

c. Click Next.

Step 9 At the Server IP Address screen, specify an IP address for the Cisco MGM server; then, click Next.

Step 10 At the Select Network Configuration screen, specify the size of your network; then, click Next.

Step 11 At the Database Information screen, specify the IP address of the database workstation and specify whether or not you want to install the database in ARCHIVELOG mode. Click Next.

Step 12 At the Cisco MGM Database Installation Directories screen, the setup program verifies that the directories exist as recommended in Table 2-1, “Disk Directories.” Click Next.

Step 13 At the Destination Folder screen, specify where you want to install the Cisco MGM server. The default directory is /opt/CiscoMGMServer. You can click Change to choose a different destination. After you specify your destination, click Next.

Note If the destination directory that you specified is a new directory, you receive the message “Specified directory does not exist, create it?” Click Yes.

Caution Cisco MGM creates a symbolic link from /opt/CiscoTransportManagerServer to /opt/CiscoMGMServer or the user-selected server directory. Do not delete this symbolic link.

Caution Cisco MGM checks for the /opt directory or a symbolic link to it. If Cisco MGM cannot find the /opt directory or a symbolic link, Cisco MGM creates a symbolic link automatically. Therefore, do not delete any instances of /opt from your Cisco MGM file structure.

Step 14 The Pre-Installation Summary screen shows the items that will be installed. Click Install.

Step 15 The Install Complete screen summarizes the results of the installation. Click Done.


OL-5460-01

Chapter 2 Installing the Cisco MGM Server and Oracle9i2.2 Setting Up Sudo

Step 16 Reboot the system. The Cisco MGM server starts automatically after rebooting.

Note Enter the showmgm command after the server reboots, to verify that the Cisco MGM server is running. The showmgm command displays the Cisco MGM server version running as 5.0. In the output, you will see the text “MGMServer,” “SnmpTrapService,” and “SMService,” as shown in the following example.# showmgm

MGM Processes for Cisco Media Gateway Manager Server

Version : 5.0

Build Label : 5.0.0.103

Build Date : Fri Jun 18 12:51:27 PDT 2004

------------------------------------------------------------------------------

USER PID %CPU %MEM S START TIME PROCESS

------------------------------------------------------------------------------

root 550 0.0 0.211632 S 02:22:39 0:00 MGMServer

root 561 0.0 0.42093614856 ? S 02:22:40 0:01 MGMServer

root 710 0.6 2.520950498648 ? S 02:23:48 7:22 SnmpTrapService

root 669 0.1 2.421231293456 ? S 02:23:17 0:50 SMService

root 967 0.9 1.512795259424 ? S 02:31:09 11:39 MGX8880 NEService-19

root 981 0.2 1.212009647008 ? S 02:31:09 2:15 MGX8880 PMService-20

------------------------------------------------------------------------------

This indicates that the Cisco MGM server is running. You should also see NE specific processes depending on your network. In the case of a fresh installation, you would see the NE specific processes only if the NEs are added in the Cisco MGM server.

2.2 Setting Up SudoAs described in the “1.4.1 Overview of Sudo Commands” section on page 1-9, the Cisco MGM server installation includes installation of the UNIX sudo command. This command allows nonroot users who belong to the UNIX group specified during installation to run certain Cisco MGM administrative commands. For security reasons, the installed sudo command setuid is disabled by default. You must enable setuid on the sudo command in order for it to work. To enable setuid:

Step 1 Log into the Cisco MGM server as the root user.

Step 2 Enter the following command:

chmod 4111 /opt/CiscoMGMServer/admin/sudo/sudo

Step 3 Verify that users have /opt/CiscoMGMServer/admin/sudo in their path environment, so that they can execute sudo without having to specify the full path.

Note Sudo is often available in the standard UNIX environment established by the Cisco MGM server system administrator. If so, it is not necessary to use the sudo bundled with Cisco MGM or follow this procedure to enable it. Instead, you can use the sudo established by the system administrator.


OL-5460-01

Chapter 2 Installing the Cisco MGM Server and Oracle9i2.2 Setting Up Sudo


OL-5460-01


C H A P T E R 3
Installing Cisco MGM GateWay/CORBA 5.0
The Cisco MGM GateWay/CORBA 5.0 option is a CORBA-based interface that provides higher-layer management systems with information for all Cisco MGM-supported NEs.

Note The license for Cisco MGM GateWay/CORBA 5.0 is sold separately. If you are using this feature in a production environment, you must purchase the license.

You can install Cisco MGM GateWay/CORBA 5.0 when you install the Cisco MGM server, or you can install Cisco MGM GateWay/CORBA 5.0 separately. This chapter describes how to install Cisco MGM GateWay/CORBA 5.0 as a separate option after installing the Cisco MGM 5.0 server.

Tip For more information about CORBA support, refer to the Cisco Media Gateway Manager 5.0 GateWay/CORBA User Guide and Programmer Manual.

This chapter contains the following sections:

• 3.1 Installing Cisco MGM GateWay/CORBA 5.0

• 3.2 Changing the Default Cisco MGM GateWay/CORBA 5.0 Port

3.1 Installing Cisco MGM GateWay/CORBA 5.0

Note You must install Cisco MGM GateWay/CORBA 5.0 on the same workstation as the Cisco MGM server. During the Cisco MGM GateWay/CORBA 5.0 installation, you do not need to shut down the Cisco MGM server.

Note The Cisco MGM database must be up and running before installing Cisco MGM GateWay/CORBA 5.0.

Log into the Cisco MGM server workstation as the root user and complete the following steps in C shell:

Step 1 If you are using an xterm window or a remote host, enter the following command to enable the xterm connection from the clients:

/usr/openwin/bin/xhost +


Chapter 3 Installing Cisco MGM GateWay/CORBA 5.03.1 Installing Cisco MGM GateWay/CORBA 5.0

Step 2 After the xterm connection is established, enter the following command to set the DISPLAY variable:



echo $DISPLAY





The setup program searches for Sun Microsystems JRE version 1.4.2 on your workstation.

Note If JRE is not installed, the setup program starts the Java installation program. Follow the prompts to install JRE. Enter yes at the following binary license code agreement prompt:Do you agree to the above license terms? [yes or no]

Then, continue installing Cisco MGM GateWay/CORBA 5.0.

Note If the required Solaris patches are missing, including patch 117000-03 or later you must install them manually. Click Cancel; then, click Quit. Download the patches from SunSolve Online at http://sunsolve.sun.com. After you install the patches, continue installing Cisco MGM GateWay/CORBA 5.0.

The installation begins. Wait for up to 60 seconds while the following message appears:




Step 7 At the Select Products screen, check the Install Cisco Media GatewayManager CORBA GateWay check box; then, click Next.

Step 8 At the Server IP Address screen, specify an IP address for the server setup; then, click Next.

Step 9 The Pre-Installation Summary screen shows the items that will be installed. Click Install.

Step 10 The Install Complete screen summarizes the results of the installation. Click Done.

Step 11 Enter the following commands to eject the Cisco MGM 5.0 server installation CD:

cd /eject cdrom

Note When Cisco MGM GateWay/CORBA 5.0 is installed, you must enable the service from the Control Panel. See the Cisco Media Gateway Manager 5.0 User Guide for more information.


OL-5460-01

Chapter 3 Installing Cisco MGM GateWay/CORBA 5.03.2 Changing the Default Cisco MGM GateWay/CORBA 5.0 Port

3.2 Changing the Default Cisco MGM GateWay/CORBA 5.0 PortBy default, Cisco MGM GateWay/CORBA 5.0 objects use the port assigned by the object request broker (ORB). The following sections describe how to change the default listener port.

3.2.1 Configuring the Port Number for Cisco MGM GateWay/CORBA 5.0To configure the port number for Cisco MGM GateWay/CORBA 5.0, add the following command line parameter to the last line of the /opt/CiscoMGMServer/cfg/corbagw.properties file:

corbagw.session.listen.port=port_number

3.2.2 Configuring the Port Number for the Cisco MGM Notification Server

Note Make sure that the Cisco MGM GateWay/CORBA service is not running when performing the procedure below.

To configure the port number for the Cisco MGM notification server:

Step 1 Log into the UNIX workstation as the root user and enter the following command:

mgms-start

Step 2 Open a UNIX prompt and enter the following commands in csh:

setenv CLASSPATH /opt/CiscoMGMServer/bin/vbjorb.jarcd /opt/CiscoMGMServer/openfusion/bin./manager &

Step 3 In the left side of the window, choose Domains > OpenFusion > localhost > NotificationService.

Step 4 In the property sheet on the right side of the window, click the CORBA tab.

Step 5 In the Server Port field, enter a value for the notification server listener port. The port value must be greater than 1500.

Step 6 Click the Save Configuration icon to save the changes.

Step 7 Choose File > Exit; then, click OK.


OL-5460-01

Chapter 3 Installing Cisco MGM GateWay/CORBA 5.03.2 Changing the Default Cisco MGM GateWay/CORBA 5.0 Port


OL-5460-01


C H A P T E R 4
Installing the Cisco MGM 5.0 Client
This chapter describes how to install and start the Cisco MGM client on Microsoft Windows or Sun Solaris.

This chapter contains the following sections:

• 4.1 Installing the Cisco MGM Client on Microsoft Windows

• 4.2 Starting the Cisco MGM Client in Microsoft Windows

• 4.3 Installing the Cisco MGM Client on Sun Solaris

• 4.4 Starting the Cisco MGM Client in Sun Solaris

Note For an explanation of error messages that you might encounter during the Cisco MGM client installation, see Appendix A, “Installation Error Messages.”

4.1 Installing the Cisco MGM Client on Microsoft WindowsThis section describes how to install the Cisco MGM client on your Windows 2000, NT 4.0, or XP workstation.

Note To install the Cisco MGM client on Windows, you must have administrator privileges on the local workstation and all running instances of any client software must be shut down before performing the installation.

4.1.1 Installing the Cisco MGM ClientTo install the Cisco MGM client:

Step 1 Insert the Cisco MGM 5.0 client installation CD and navigate to mgmc\win32\setup.exe. Double-click setup.exe. The Introduction window appears.

Step 2 Click Next. The Destination Folder window appears.


Chapter 4 Installing the Cisco MGM 5.0 Client4.1 Installing the Cisco MGM Client on Microsoft Windows

Step 3 At the Destination Folder window, complete the following substeps:

a. Specify where you want to install the Cisco MGM client. The default destination folder is C:\Cisco\MGMClient5_0. You can click Change to choose a different destination.

b. Specify whether you want to create a Cisco MGM desktop icon, a Cisco MGM shortcut in the Start menu, or both. If you choose the Start menu shortcut option, specify the destination folder for the shortcut. The default shortcut folder is Programs\Cisco Media Gateway Manager.

Step 4 Click Next. The Pre-Installation Summary window appears. The Pre-Installation Summary window shows the items that will be installed and the space that is required.

Step 5 Click Install. The installation begins.

Step 6 The Install Complete window summarizes the results of the installation. Click Done.

Step 7 Eject the Cisco MGM 5.0 client installation CD.

4.1.2 Specifying the Default Browser to Display the Online HelpIn Microsoft Windows, Cisco MGM uses the default browser to display the online help. If you want to use a specific browser to launch the Cisco MGM online help, make that the default browser for your workstation.

Note During testing, Cisco uses Internet Explorer and Netscape to display the online help; other browsers have not been tested.

The online help requires Adobe Acrobat Reader. Acrobat Reader is not required in your PATH environment variable, but the PDF file type must be associated with Acrobat Reader.

4.1.2.1 Special Considerations when Proxy Server Is Enabled

If you are using a proxy-server enabled web browser, complete one of the following options, depending on your browser type.

For Internet Explorer, complete the following steps:

Step 1 Choose Tools > Internet Options.

Step 2 Click the Connections tab.

Step 3 Click the LAN Settings button.

Step 4 Complete one of the following options:

• Uncheck the Use a proxy server for your LAN check box.

• If the “Use a proxy server for your LAN” check box must remain checked, click Advanced. Enter your server IP address in the Do not use proxy server addresses beginning with field. Separate each address with a semicolon.

Step 5 Click OK.


OL-5460-01

Chapter 4 Installing the Cisco MGM 5.0 Client4.2 Starting the Cisco MGM Client in Microsoft Windows

For Netscape, complete the following steps:

Step 1 Choose Edit > Preferences.

Step 2 Expand Advanced and choose Proxies.


• If you do not want to use a proxy, click Direct connection to the Internet.

• If you do not have a proxy location (URL), click Manual proxy configuration. In the No Proxy for field, enter the domains that you do not want to use a proxy for. Use a comma to separate domains.

Step 4 Click OK.

4.2 Starting the Cisco MGM Client in Microsoft Windows To start the Cisco MGM client:

Step 1 Depending on the option you chose during installation, double-click the Cisco MGM desktop icon or choose the Cisco MGM Start menu shortcut to start the client.

Note It is not necessary to restart the workstation.

Step 2 The first time you log in, use the default username and password:

• Username: SysAdmin

• Password: MGM123!

Note The username and password are case sensitive.

Step 3 Enter the Cisco MGM server host name or IP address and click OK.

Note Do not enter a host name unless Domain Name System (DNS) is enabled in your network.

Step 4 For security reasons, you are prompted to change the password after you log in for the first time. Click Yes. The password must:

• Contain at least 6, but not more than 12 characters.

• Contain at least two alphabetic characters (A-Z, a-z).

• Contain at least one numeric character (0-9).

• Contain at least one special character (. ; : % & ! + #).

• Not contain the username or any circular shift of the username. An uppercase letter and its corresponding lowercase letter are considered equivalent. For example, if the username is Arthur, the password cannot contain the string arthur, rthura, thurar, hurart, urarth, or rarthu.

Change the password; then, click OK.


OL-5460-01

Chapter 4 Installing the Cisco MGM 5.0 Client4.3 Installing the Cisco MGM Client on Sun Solaris

Step 5 Click OK in the login advisory dialog box.

Note The default SysAdmin user has limited privileges. Create new Cisco MGM users with Superuser privileges to have access to all Cisco MGM operations. Refer to the Cisco Media Gateway Manager 5.0 User Guide for information about user profiles and creating Cisco MGM users.

4.3 Installing the Cisco MGM Client on Sun SolarisThis section describes how to install the Cisco MGM client on your Sun Solaris 8 workstation.

4.3.1 Installing the Cisco MGM ClientTo install the Cisco MGM client:

Step 1 Log in as the root user and insert the Cisco MGM 5.0 client installation CD.

Step 2 From a terminal window, enter the following commands:

cd /cdrom/cdrom0/disk2/mgmc/solaris./mgmcsetup.sh

The Cisco MGM client installation begins. Wait for up to 60 seconds while the following message appears:

Installing Cisco Media Gateway Manager client...

Step 3 Click Next at the Introduction window.

Step 4 At the Destination Folder window, complete the following substeps:

a. Specify where you want to install the Cisco MGM client. The default destination folder is /opt/CiscoMGMClient. You can click Change to choose a different destination.

b. Click Next.

Note If the destination directory that you specified is a new directory, you receive the message “Specified directory does not exist, create it?” Click Yes.

Step 5 At the Cisco MGM Group Information window, enter the name of the UNIX group to which you want to assign administrator privileges. The default is the group name of the root user. You can uncheck the “Ignore user-entered group name” check box and enter the group name of your choice. After you specify the Cisco MGM group name, click Next.

Note The group name should exist on the UNIX workstation. The users that belong to the group should have the umask 002 command configured.

Step 6 The Pre-Installation Summary window shows the items that will be installed and the space that is required. Click Install.


OL-5460-01

Chapter 4 Installing the Cisco MGM 5.0 Client4.4 Starting the Cisco MGM Client in Sun Solaris

Step 7 The Install Complete window summarizes the results of the installation. Click Done.

Step 8 Enter the following commands to eject the Cisco MGM 5.0 client installation CD:

cd /eject cdrom

4.3.2 Requirements to Display the Online HelpIn Sun Solaris, Cisco MGM invokes the netscape command to display the online help. By default, the directory where your Netscape executable is installed must be in your PATH environment variable.

Note If you are using Netscape 4.76 on a Solaris workstation, the online help does not open if Netscape is not already open. Therefore, open the Netscape browser before opening the Cisco MGM online help. This problem does not apply if you are using Netscape 4.79 and later.

The online help requires Adobe Acrobat Reader in your PATH environment variable.

Tip If you cannot launch the online help, open a command prompt from another window and enter the xhost + command. Also, verify that the DISPLAY variable is set correctly.

4.3.2.1 Special Considerations when Proxy Server Is Enabled

If you are using a proxy-server enabled Netscape browser, complete the following steps:

Step 1 Choose Edit > Preferences.

Step 2 Expand Advanced and choose Proxies.


• If you do not want to use a proxy, click Direct connection to the Internet.

• If you do not have a proxy location (URL), click Manual proxy configuration. In the No Proxy for field, enter the domains that you do not want to use a proxy for. Use a comma to separate domains.

Step 4 Click OK.

4.4 Starting the Cisco MGM Client in Sun SolarisTo start the Cisco MGM client:

Step 1 At the console, enter the following command to change the directory:

cd /opt/CiscoMGMClient


OL-5460-01

Chapter 4 Installing the Cisco MGM 5.0 Client4.4 Starting the Cisco MGM Client in Sun Solaris

Step 2 Enter the following command:

./mgmc-start

Caution In the Bourne shell, if you enter ./mgmc-start to start the client and then execute Ctrl-C in the xterm window where the client was launched, the Cisco MGM client will terminate.

Note The installation program creates a soft link on /usr/bin for mgmc-start. If the soft link is missing, enter install_directory/mgmc-start at the console.

The following message appears:

Starting Cisco Media Gateway Manager client. Please wait.

Wait 10 to 20 seconds for the Cisco MGM client application to start.

Step 3 The first time you log in, enter the default username and password:

• Username: SysAdmin

• Password: MGM123!

Note The username and password are case sensitive.

Step 4 Enter the Cisco MGM server host name or IP address and click OK.

Note Do not enter a host name unless DNS is enabled in your network.

Step 5 For security reasons, you are prompted to change the password after you log in for the first time. Click Yes. The new password must:

• Contain at least 6, but not more than 12 characters.

• Contain at least two alphabetic characters (A-Z, a-z).

• Contain at least one numeric character (0-9).

• Contain at least one special character (. ; : % & ! + #).

• Not contain the username or any circular shift of the username. An uppercase letter and its corresponding lowercase letter are considered equivalent. For example, if the username is Arthur, the password cannot contain the string arthur, rthura, thurar, hurart, urarth, or rarthu.

Change the password; then, click OK.

Step 6 Click OK in the login advisory dialog box.

Note The default SysAdmin user has limited privileges. Create new Cisco MGM users with Superuser privileges to have access to all Cisco MGM operations. Refer to the Cisco Media Gateway Manager 5.0 User Guide for information about user profiles and creating Cisco MGM users.


OL-5460-01


C H A P T E R 5
Uninstalling Cisco MGM, and the Oracle Database
This chapter describes how to uninstall the Cisco MGM 5.0 server, the Cisco MGM 5.0 client, and Oracle and the database. It contains the following sections:

• 5.1 Uninstalling the Cisco MGM Server

• 5.2 Uninstalling the Cisco MGM Client on Microsoft Windows

• 5.3 Uninstalling the Cisco MGM Client on Sun Solaris

• 5.4 Uninstalling the Oracle Software

• 5.5 Deleting the EMS Information From the Oracle Database

5.1 Uninstalling the Cisco MGM Server

Note Before uninstalling the Cisco MGM server, use the mgms-stop command to shut down the server.

Note Uninstalling the Cisco MGM server automatically uninstalls the WebServer (if WebServer was installed). WebServer cannot be uninstalled on its own.

To uninstall the Cisco MGM server:

Step 1 Enter the following command to set the display on your terminal:



echo $DISPLAY



Step 3 Log into the Cisco MGM server as the root user and enter the following command to change the directory to the uninstall directory:

cd /opt/CiscoMGMServer/UninstallerData


Chapter 5 Uninstalling Cisco MGM, and the Oracle Database5.1 Uninstalling the Cisco MGM Server

Step 4 Enter the following command to run the uninstall script:

./IAUninstaller.sh

Wait for up to 60 seconds while the following message appears:

Uninstalling Cisco Media Gateway Manager server...

Step 5 At the Uninstall Cisco Media Gateway Manager screen, click Uninstall.

Note If you are prompted to stop the Cisco MGM server, click OK.

Step 6 At the Uninstall Complete screen, click Quit.

Step 7 The following message is displayed:

Remove directories/files not removed by installer under /opt/CiscoMGMServer. Continue ? [y]

Click y to proceed.

Following files and directories will be removed. Press Ctrl C to exit/opt/CiscoMGMServer/opt/CiscoMGMServer/cfg/opt/CiscoMGMServer/cfg/CTMKeystore/opt/CiscoMGMServer/cfg/CTMKeys.pem/opt/CiscoMGMServer/cfg/CTMPubKey.pem/opt/CiscoMGMServer/cfg/corbagw.properties.default/opt/CiscoMGMServer/cfg/NMAlarmServer.ior/opt/CiscoMGMServer/cfg/NMInventoryServer.ior/opt/CiscoMGMServer/cfg/NMServerDisconnect.ior/opt/CiscoMGMServer/cfg/Topod.ior/opt/CiscoMGMServer/bin/opt/CiscoMGMServer/bin/ctm41_411.sh/opt/CiscoMGMServer/bin/sqlnet.log/opt/CiscoMGMServer/admin/opt/CiscoMGMServer/admin/sudo/opt/CiscoMGMServer/admin/sudo/sudo/opt/CiscoMGMServer/log/opt/CiscoMGMServer/log/SMService.log.lck/opt/CiscoMGMServer/log/SMService_initialization.log.lck/opt/CiscoMGMServer/log/SnmpTrapService.log.lck/opt/CiscoMGMServer/log/SnmpTrapService_initialization.log.lck/opt/CiscoMGMServer/log/MGX8880NEService-19.log.lck/opt/CiscoMGMServer/log/MGX8880NEService-19_initialization.log.lck/opt/CiscoMGMServer/log/MGX8880PMService-20.log.lck/opt/CiscoMGMServer/log/MGX8880PMService-20_initialization.log.lck/opt/CiscoMGMServer/jms/opt/CiscoMGMServer/jms/server/opt/CiscoMGMServer/jms/server/default/opt/CiscoMGMServer/jms/server/default/log/opt/CiscoMGMServer/jms/server/default/log/boot.log/opt/CiscoMGMServer/jms/server/default/log/server.log/opt/CiscoMGMServer/jms/server/default/log/server.log.bak/opt/CiscoMGMServer/jms/server/default/log/server.log.2004-10-12/opt/CiscoMGMServer/jms/server/default/tmp/opt/CiscoMGMServer/jms/server/default/tmp/deploy/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/conf/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/conf/jboss-service.xml/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/conf/jboss-service.xml/1.jboss-service.xml


OL-5460-01

Chapter 5 Uninstalling Cisco MGM, and the Oracle Database5.2 Uninstalling the Cisco MGM Client on Microsoft Windows

/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jpl-pattern.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jpl-pattern.jar/2.jpl-pattern.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jts.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jts.jar/3.jts.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/process-plugin.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/process-plugin.jar/4.process-plugin.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jbossmq.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jbossmq.jar/5.jbossmq.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jmxtools.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jmxtools.jar/6.jmxtools.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jboss-j2ee.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jboss-j2ee.jar/7.jboss-j2ee.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jnet.jar/opt/CiscoMGMServer/jms/server/default/tmp/deploy/server/default/lib/jnet.jar/8.jnet.jar

Press any key to remove

The Uninstallation is complete.

5.2 Uninstalling the Cisco MGM Client on Microsoft WindowsTo uninstall the Cisco MGM client:

Step 1 On the workstation where the client will be uninstalled, close any Cisco MGM client sessions that are currently open.

Step 2 Use the Windows Add/Remove Programs tool to uninstall the Cisco MGM client.

a. Choose Start > Settings > Control Panel > Add/Remove Programs.

b. In the Add/Remove Programs dialog box, select Cisco Media Gateway Manager Release x.x and click Change/Remove.

c. At the Uninstall Cisco Media Gateway Manager screen, click Uninstall.

Note If you are prompted to close any Cisco MGM client sessions that are currently open, click OK.

Note You may see messages during the Uninstall process, for example Unable to remove c:\CiscoMediaGatewayManager\debug. The Cisco MGM uninstall process has identified that these are files created or updated by the user during installation or while using Cisco MGM, and checks to see if these files should be removed. If you need the data, retain the files. If the data is not required, remove these files.

d. At the Uninstall Complete screen, click Quit.

e. In the Add/Remove Programs dialog box, click Close.


OL-5460-01

Chapter 5 Uninstalling Cisco MGM, and the Oracle Database5.3 Uninstalling the Cisco MGM Client on Sun Solaris

Step 3 Delete the directory where the Cisco MGM client was installed. The default installation directory is C:\Cisco\MGMClient5_0.

5.3 Uninstalling the Cisco MGM Client on Sun Solaris

Note If any reports or exports of Cisco MGM data have been stored under the client directory and need to be saved, move the reports to a different directory before uninstalling the Cisco MGM client.

To uninstall the Cisco MGM client:

Step 1 On the workstation where the client will be uninstalled, close any Cisco MGM client sessions that are currently open.

Step 2 Log in as the root user or become the root user on the workstation where the client will be uninstalled.

Step 3 Enter the following command to change to the /opt/CiscoMGMClient/UninstallerData directory:

cd /opt/CiscoMGMClient/UninstallerData

Step 4 Enter the following command to remove the /opt/CiscoMGMClient directory:

./IAuninstaller.sh

Step 5 Enter the following command to remove the symbolic link to mgmc-start:

rm /usr/bin/mgmc-start

Caution In the Bourne shell, if you enter mgmc-start to start the client and then execute Ctrl-C in the xterm window where the client was launched, the Cisco MGM client will terminate.

5.4 Uninstalling the Oracle SoftwareTo uninstall the Oracle9i software:

Caution If you remove the Oracle9i software, you cannot use Cisco MGM 5.0. Be sure that you want to remove the Oracle9i software before completing the following steps.

Step 1 Log into the Oracle database workstation as the root user and enter the following command:

rm -rf /oraclesw9i/product/9.2


OL-5460-01

Chapter 5 Uninstalling Cisco MGM, and the Oracle Database5.5 Deleting the EMS Information From the Oracle Database

Step 2 Log into the Cisco MGM server workstation as the root user and enter the same command:

rm -rf /oraclesw9i/product/9.2

5.5 Deleting the EMS Information From the Oracle DatabaseTo delete the EMS information from the Oracle database:

Step 1 Log in as the root user on the server where the Oracle database is installed.

Step 2 Enter the following commands:

cd /opt/CiscoMGMServer/bin./delete_old_db.sh <ORACLE_SID>


OL-5460-01

Chapter 5 Uninstalling Cisco MGM, and the Oracle Database5.5 Deleting the EMS Information From the Oracle Database


OL-5460-01


A P P E N D I X A
Installation Error Messages
This appendix details the error messages that may occur when installing Cisco MGM. It contains the following sections:

• A.1 Cisco MGM Client Installation Error Messages

• A.2 Cisco MGM Server Installation Error Messages

A.1 Cisco MGM Client Installation Error MessagesTable A-1 lists the error messages that you might encounter during the Cisco MGM client installation and recommends solutions.

Table A-1 Client Installation Error Messages

Error Message Recommended Action

EID-1: Enter the destination directory. Specify the destination location.

EID-2: Physical memory on your machine is less than 256 MB; Cisco Media Gateway Manager might not perform as expected.

Upgrade the system RAM to 256 MB or install the software on another workstation.

EID-3: Please select either desktop menu or Shortcut menu or both to proceed.

Specify whether you want to create a Cisco MGM desktop icon, a Cisco MGM shortcut in the Start menu, or both.

EID-24: Not enough space in the selected disk drive. Please choose a different disk drive.

Choose a disk drive that has enough space.

EID-26: Error occurred while extracting the files. Please check disk space and reinstall.

Verify that the system has enough disk space; then, reinstall the Cisco MGM client.

Warning: The installation will write over an existing installation. Press “Previous” if you want to change the install folder.

Click Previous and select a new installation location.

A-1ateway Manager 5.0 Installation Guide

Appendix A Installation Error MessagesA.2 Cisco MGM Server Installation Error Messages

A.2 Cisco MGM Server Installation Error MessagesTable A-2 lists the error messages that you might encounter during the Cisco MGM server installation and recommends solutions.

Table A-2 Server Installation Error Messages


EID-26: Enter a directory for the Cisco MGM Index tablespace.

Enter the directory name.

EID-27: Enter a directory for the Cisco MGM Data1 tablespace.


EID-28: Enter a directory for the Cisco MGM Data2 tablespace.


EID-29: Enter the database administrator name. Enter the database administrator name.

EID-30: Enter the database administrator password. Enter the database administrator password.

EID-31: Enter the database file size in MB. Enter the database file size.

EID-32: Enter a valid number for the database file size.

Enter the database file size.

EID-33: Enter the data file path. Enter the data file path.

EID-35: The installation directory is not specified.

Specify the installation directory.

EID-36: I/O exception occurred while writing to the USER.DAT file.

Check file permissions and disk space.

EID-38: Error occurred while removing the USER.DAT file.

Check file permissions.

EID-43: Select at least one option to proceed. Select at least one option.

EID-44: IP address and username must be specified. Enter the IP address and username.

EID-45: Username and password are mandatory. Enter the username and password.

EID-46: IP address or host name is mandatory. Enter the IP address or host name.

EID-47: The installation directory must be specified.

Enter the installation directory.

EID-48: The IP address must be specified. Enter the IP address.

EID-49: Host name and password must be specified. Enter the host name and password.

EID-50: Host name could not be located. Specify the correct name or IP address.

Enter the host name or IP address.

EID-51: Both host names and the password must be specified.

Enter the host name(s) and password.

EID-52: Source host name could not be located. Specify the correct name or IP address.

Enter the source host name or IP address.

EID-53: Destination host name could not be located. Specify the correct name or IP address.

Enter the destination host name or IP address.

EID-54: The host name translates to multiple IP addresses. Specify one physical IP address.

Enter the IP address.

A-2Cisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01


EID-100: Invalid SID. The SID is null or contains spaces. Enter an SID that is not null and does not contain spaces.

Enter a valid SID.

EID-101: The Cisco MGM GateWay/CORBA installation failed. The Cisco MGM database might be down or not installed. Start the Cisco MGM database or install it. Then, retry the Cisco MGM GateWay/CORBA installation.

1. Start or install the Cisco MGM database.

2. When the server and database machines are installed on separate workstations (and before you install GateWay/CORBA on the server machine), you must manually update the oratab file on the server for the Oracle SID of the remote database server. The oratab file is located in the /var/opt/oracle/ directory.

3. Retry the Cisco MGM GateWay/CORBA installation.

Table A-2 Server Installation Error Messages (continued)



OL-5460-01



OL-5460-01


A P P E N D I X B
Mounting and Unmounting CDs on Sun Solaris
This appendix describes how to mount and unmount CD-ROMs on a Solaris system. It includes general information only. For more detailed instructions, consult your Sun documentation. It contains the following sections:

• B.1 Mounting a Local CD-ROM Drive

• B.2 Mounting a Remote CD-ROM Drive

• B.3 Unmounting a Local CD-ROM Drive

• B.4 Unmounting a Remote CD-ROM Drive

B.1 Mounting a Local CD-ROM DriveTo mount a local CD-ROM drive, insert the CD-ROM into the drive and complete the following steps:

Step 1 Become the superuser by entering the su command and the root password at the command prompt, or log in as the root user. The command prompt changes to the pound sign (#).

Step 2 If the /cdrom directory does not already exist, enter the following command to create it:

mkdir /cdrom

Step 3 Mount the CD-ROM drive.

Note The vold process manages the CD-ROM device and performs the mounting. The CD-ROM might automatically mount onto the /cdrom/cdrom0 directory.

If you are running File Manager, a separate File Manager window displays the contents of the CD-ROM. From the File Manager, double-click the setup.sh file. The Action: Run dialog box appears. Click OK to continue the installation.

Step 4 If the /cdrom/cdrom0 directory is empty because the CD-ROM was not mounted, or if the File Manager does not open a window displaying the contents of the CD-ROM, enter the following command to verify that the vold daemon is running:

ps -ef | grep vold | grep -v grep

Step 5 If vold is running, the system displays the process identification number of vold. If the system does not display anything, enter the following command to restart the daemon:

/usr/sbin/vold &

B-1ateway Manager 5.0 Installation Guide

Appendix B Mounting and Unmounting CDs on Sun SolarisB.2 Mounting a Remote CD-ROM Drive

Step 6 If the vold daemon is running but did not mount the CD-ROM, stop the vold daemon and then restart it. To stop the vold process, you must know the process identification number. If you do not know the process identification number, enter the following command to obtain the process ID:


Step 7 Enter the following command to stop the vold process:

kill -15 process_ID_number

Step 8 Enter the following command to restart the vold process:

/usr/sbin/vold &

Step 9 If you have problems using the vold daemon, enter the following command to mount the CD-ROM:

mount -F hsfs -r ro /dev/dsk/cxtyd0sz /cdrom/cdrom0

where x is the CD-ROM drive controller number, y is the CD-ROM drive Small Computer System Interface (SCSI) ID number, and z is the slice of the partition on which the CD-ROM is located.

B.2 Mounting a Remote CD-ROM DriveInsert the CD-ROM into the CD-ROM drive of the remote workstation and perform Steps 1 through 12 only on the remote workstation. Then, perform Steps 13 through 16 on the workstation where you want to install the application.

Step 1 Log in as the root user. The command prompt changes to the pound sign (#).

Step 2 If the /cdrom directory does not already exist, enter the following command to create it:

mkdir /cdrom

Step 3 Mount the CD-ROM drive.

Note The vold daemon process manages the CD-ROM device and performs the mounting. The CD-ROM might automatically mount onto the /cdrom/cdrom0 directory.

If you are running File Manager, a separate File Manager window displays the contents of the CD-ROM. From the File Manager, double-click the setup.sh file. The Action: Run dialog box appears. Click OK to continue the installation.

Step 4 If the /cdrom/cdrom0 directory is empty because the CD-ROM was not mounted, or if the File Manager does not open a window displaying the contents of the CD-ROM, enter the following command to verify that the vold daemon is running:


Step 5 If vold is running, the system displays /usr/sbin/vold. If the system does not display anything, enter the following command to restart the daemon:

/usr/sbin/vold &

B-2Cisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01

Appendix B Mounting and Unmounting CDs on Sun SolarisB.2 Mounting a Remote CD-ROM Drive

Step 6 If the vold daemon is running but did not mount the CD-ROM, stop the vold daemon and then restart it. To stop the vold process, you must know the process identification number. If you do not know the process identification number, enter the following command to obtain the process ID:


Step 7 Enter the following command to stop the vold process:

kill -15 process_ID_number

Step 8 Enter the following command to restart the vold process:

/usr/sbin/vold &

Step 9 If you have problems using the vold daemon, enter the following command to mount the CD-ROM:

mount -F hsfs -r ro /dev/dsk/cxtyd0sz /cdrom/cdrom0

where x is the CD-ROM drive controller number, y is the CD-ROM drive SCSI ID number, and z is the slice of the partition on which the CD-ROM is located.

Step 10 Use a text editor to create an /etc/dfs/dfstab file, if one does not already exist.

Step 11 Add the following line to the /etc/dfs/dfstab file:

share -F nfs -o ro /cdrom/cdrom0

Step 12 Enter the following command to verify that your remote workstation is enabled as a Network File System (NFS) server:

ps -ef | grep nfs | grep -v grep

The output of this command shows whether or not the /usr/lib/nfs/nfsd and /usr/lib/nfs/mountd daemons are running. If they are not running, enter the following command to enable your workstation as an NFS server:

/etc/init.d/nfs.server start

If your workstation is enabled as an NFS server, enter one of the following commands:

share

or

shareall

Step 13 Go to the workstation where you want to install the application.

Step 14 Log in as superuser by entering the command su and the root password, or log in as the root user.

Step 15 Enter the following command to create a /cdrom directory, if one does not already exist:

mkdir -p /cdrom/directory_name

Step 16 Enter the following command to mount the CD-ROM drive:

/usr/sbin/mount -r remote_workstation_name:/cdrom/cdrom0 /cdrom/directory_name


OL-5460-01

Appendix B Mounting and Unmounting CDs on Sun SolarisB.3 Unmounting a Local CD-ROM Drive

B.3 Unmounting a Local CD-ROM DriveTo unmount a local CD-ROM drive:

Step 1 As the root user, enter the following commands:

cdumount /cdrom/cdrom0 eject

Step 2 Remove the CD-ROM and store it in a safe place.

B.4 Unmounting a Remote CD-ROM DriveTo unmount a remote CD-ROM drive:

Step 1 As the root user, enter the following command on the local workstation:

umount /cdrom/directory_name

Step 2 As the root user, enter the following command on the remote workstation:

umount /cdrom/cdrom0

Step 3 Remove the CD-ROM and store it in a safe place.


OL-5460-01


A P P E N D I X C
Cisco Info Center Product Integration Policy Packs
Cisco MGM includes a Cisco Info Center Product Integration Policy Pack. A policy pack is a software package that can be installed to update the event processing provided by the Cisco Info Center application. Policy packs are provided as necessary when Cisco Info Center processing rules or tools for Cisco MGM events are changed.

The Cisco Info Center Product Integration Policy Pack for Cisco MGM includes a tar file that can be installed using the Cisco Info Center update utility (nco_update). The Product Integration Policy Pack is provided in on the Cisco MGM CD-ROM, in a tar file that the update utility can process.

The update utility is a tool that is used to install new rules, enhancements, and new lookups necessary for CIC to function with Cisco MGM.

Install the Cisco Info Center updates for Cisco MGM on the host that is running the Cisco Info Center RTTrapd Info Mediator.

Note To update the Cisco Info Center installation, Cisco Info Center release 3.6.1 must already be installed in your Cisco MGM environment.

For detailed information on how to install Cisco Info Center in the Cisco MGM environment, please refer to the Cisco Info Center Installation and Configuration Guide, 3.6.1. at the following URL:

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

For information on using Cisco Info Center, refer to the Cisco Info Center User Guide, 3.6.1 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/info_ctr/3_6_1/user/index.htm

For additional information on Cisco Info Center documentation, refer to the Documentation Guide for Cisco Info Center, 3.6.1, which is provided in the Cisco Info Center product box and at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/info_ctr/3_6_1/docguide/docguide.htm

C-1ateway Manager 5.0 Installation Guide

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

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/info_ctr/3_6_1/user/index.htm


Appendix C Cisco Info Center Product Integration Policy PacksC.1 Update Distribution Files

C.1 Update Distribution FilesThe Cisco MGM CD-ROM contains the following files in the cdromAgent/cic sub-directory:

• CIC3.6x-IIU003-MGM5.0.README

• CIC3.6x-IIU003-MGM50.tar

C.1.1 CIC36xPatch002MGM50.tar Readme FileMGM support for CIC-------------------Patch Name:----------CIC36xPatch001BTS44.tar

Supported Configurations:------------------------1. CIC 3.6 + Webtop 1.22. CIC 3.6.1 + Webtop 1.2

Installation:-------------1. The environment variable OMNIHOME must be set to the CIC installed directory ( Example: export OMNIHOME="/opt/Omnibus" )2. InfoServer must be running to update the CIC with the new tool "Launch MGM Client"3. Desktop component must have been installed to insert new MGM filters and views4. Webtop sever must be running to update the Webtop configuration with MGM filters and views5. The patch must be installed using $OMNIHOME/bin/cic_update utility

MGM Info Mediator configuration:-------------------------------1. After the patch installation, nco_config has to be run to configure MGM Info Mediator to receive traps from MGM server

Uninstall:---------1. The environment variable OMNIHOME must be set to the CIC installed directory ( Example: export OMNIHOME="/opt/Omnibus" )2. InfoServer must be running to delete the tool "Launch MGM Client"3. Webtop sever must be running to delete the MGM filters and views from the Webtop configuration4. The patch can be uninstalled, using $OMNIHOME/bin/cic_update utility by giving input as the uninstall tar ball created during the patch installation5. Run nco_config, if the MGM Info Mediator was configured

License:--------1. MGM Info Mediator uses the licenses of rttrapd Info Mediator

C-2Cisco Media Gateway Manager 5.0 Installation Guide

OL-5460-01


Cisco Media GateOL-5460-01

I N D E X

A

audience for this document vii

C

cautions

regarding

configuring your system for large files 1-1

deleting /opt from Cisco MGM file structure 2-12

Solaris 8 installation 1-1

significance of viii

CDs

mounting

local CD-ROM B-1

remote CD-ROM B-2

unmounting

local CD-ROM B-4

remote CD-ROM B-4

changing the default CORBA port 3-3

CORBA. See GateWay/CORBA

D

disk directories (table) 2-2

document conventions (table) viii

E

environment, setting, same workstation 2-2 to 2-4

G

GateWay/CORBA

changing the default CORBA port 3-3

configuring the port number for the notification server 3-3

installing 3-1

I

installation and upgrade workflow viii

installing GateWay/CORBA only 3-1 to 3-2

installing the Cisco MGM 5.0 client 4-1

Solaris

install client 4-4 to 4-5

requirements to display online help 4-5

starting the client 4-5

Windows

install client 4-1 to 4-2

specify the default browser 4-2


installing the Cisco MGM 5.0 server and Oracle9i 2-1

installing the Cisco MGM 5.0 database 2-11 to 2-13

installing the Cisco MGM 5.0 server 2-11 to 2-13

same workstation

installation 2-1 to 2-13

installing Oracle9i 2-1 to 2-4

installing the Cisco MGM 5.0 database 2-11 to 2-13

updating the system parameters 2-9 to 2-11

installing the Cisco MGM 5.0 server and Oracle9i 2-1 to 2-7

installing the Cisco MGM client

Solaris


IN-1way Manager 5.0 Installation Guide

Index

P

partition sizing for the Cisco MGM server and Oracle9i (table)

same workstation 1-4

separate workstations 1-5

Pentium III or Pentium 4 workstation, system requirements 1-6

R

requirements for the Cisco MGM client (table) 1-5

response file from Cisco, using to installing Oracle9i 2-4 to 2-6

S

starting

Cisco MGM server 1-10 to 1-11

stopping

Cisco MGM server 1-11

sudo, setting up 2-13

sudo commands, overview 1-9 to 1-10

Sun Ultra 5 workstation, system requirements 1-5

system requirements

Cisco MGM client 1-5, 1-6

Pentium III or Pentium 4 PC 1-6

Sun Ultra 5 workstation 1-5

Cisco MGM server 1-4 to 1-5

caution regarding configuring your system for large files 1-1

caution regarding Solaris 8 installation 1-1

partition sizing, with Oracle9i on a separate workstation 1-5

partition sizing, with Oracle9i on the same workstation 1-4

description 1-1 to 1-10

prerequisites 1-9 to 1-10

correct version of Oracle9i 1-9

IN-2Cisco Media Gateway Manager 5.0 Installation Guide

T

tables

Cisco MGM client installation error messages A-1

Cisco MGM server installation error messages A-2

disk directories 2-2

disk space for Cisco MGM server and Oracle9i



document conventions viii

partition sizing for the Cisco MGM server and Oracle9i



requirements for the Cisco MGM client 1-5

sample configuration for Cisco MGM server and Oracle9i, same workstation 1-2

typographical conventions viii

U

uninstalling

Cisco MGM 5-1

Cisco MGM client

on Solaris 5-4

Cisco MGM server 5-1

W

workstation requirements

Pentium III or Pentium 4 1-6

Sun Ultra 5 1-5

OL-5460-01

installation guide for cisco media gateway manager 5.0 ... · 2.1.2 updating the system parameters...

Documents