solstice enterprise manager troubleshooting guide · 1-1 introduction to troubleshooting 1 1.1...

2550 Garcia AvenueMountain View, CA 94043U.S.A.

Solstice Enterprise ManagerTroubleshooting Guide

A Sun Microsystems, Inc. Business

PleaseRecycle

Copyright 1996 Sun Microsystems, Inc., 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. All rights reserved.

This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution anddecompilation. No part of this product or document may be reproduced in any form by any means without prior writtenauthorization of Sun and its licensors, if any.

Portions of this product may be derived from the UNIX® system, licensed from Novell, Inc., and from the Berkeley 4.3 BSDsystem, licensed from the University of California. UNIX is a registered trademark in the United States and other countries and isexclusively licensed by X/Open Company Ltd. Third-party software, including font technology in this product, is protected bycopyright and licensed from Sun’s suppliers.

RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227-14(g)(2)(6/87) and FAR 52.227-19(6/87), or DFAR 252.227-7015(b)(6/95) and DFAR 227.7202-1(a).The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications.

Sun, Sun Microsystems, the Sun logo, and Solaris, SunSoft, Solstice, Solstice Enterprise Manager, Site/SunNet/DomainManager, SunNet Manager, SunOS, OpenWindows, DeskSet, ONC, SNM, and NFS are trademarks or registered trademarks ofSun Microsystems, Inc. in the United States and other countries. All SPARC trademarks are used under license and aretrademarks or registered trademarks of SPARC International, Inc. in the United States and other countries. Products bearingSPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. UNIX is a registered trademark in theUnited States and other countries, exclusively licensed through X/Open Company, Ltd. OPEN LOOK is a registered trademarkof Novell, Inc. PostScript and Display PostScript are trademarks of Adobe Systems, Inc.

The OPEN LOOK® and Sun™ Graphical User Interfaces were developed by Sun Microsystems, Inc. for its users and licensees.Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical userinterfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, whichlicense also covers Sun’s licensees who implement OPEN LOOK GUI’s and otherwise comply with Sun’s written licenseagreements.

X Window System is a trademark of X Consortium, Inc.

THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR APARTICULAR PURPOSE, OR NON-INFRINGEMENT.

iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

1. Introduction to Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.2 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.3 Commonly-Asked Questions . . . . . . . . . . . . . . . . . . . . . . . 1-2

1.4 Troubleshooting Processes and Procedures . . . . . . . . . . . 1-2

1.5 Specific Troubleshooting Information . . . . . . . . . . . . . . . . 1-3

2. Installation and Startup Problems . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.2 Installation Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.3 EM Software Does not Start . . . . . . . . . . . . . . . . . . . . . . . . 2-3

3. Core Applications Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.2 General Application Problems . . . . . . . . . . . . . . . . . . . . . . 3-2

3.3 Discover Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

iv Solstice Enterprise Manager Troubleshooting Guide

3.4 Alarm Manager Problems . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

3.5 MIS Communication Problems. . . . . . . . . . . . . . . . . . . . . . 3-7

4. Network Administration Problems . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.2 Tools for Evaluating Your Network . . . . . . . . . . . . . . . . . . 4-1

4.3 Evaluating Network Failures . . . . . . . . . . . . . . . . . . . . . . . 4-2

5. Application Development Problems . . . . . . . . . . . . . . . . . . . . 5-1

5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.2 EM API Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.3 GDMO Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

6. Network Protocol Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.2 Working with CMIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.3 Working with SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

A. Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

v

Tables

Table 1-1 Common Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Table 1-2 Insect Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Table 2-1 Installation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Table 2-2 Startup Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Table 3-1 General Application Problems . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Table 3-2 Discover Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Table 3-3 Alarm Manager Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Table 3-4 MIS Communication Problems . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Table 4-1 Network Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Table 5-1 PMI Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Table 5-2 GDMO Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Table 6-1 CMIP Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Table 6-2 SNMP Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Table A-1 Application Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Table A-2 PMI (Portable Management Interface) Error Messages . . . . . . A-15

vi Solstice Enterprise Manager Troubleshooting Guide

vii

Preface

The Solstice Enterprise Manager Troubleshooting Guide provides information onhow to resolve situations you might encounter with Solstice EM software.Some of this information is purely “troubleshooting,” whereas some of itprovides a quick view into performing common EM tasks. For troubleshootinginformation, this book provides symptom-resolution charts that identify whatthe problem is, its likely cause(s), and how to resolve the problem.

For information on how to use the Solstice EM products for networkadministration or application development, see the Solstice Enterprise ManagerAdministration Guide or Solstice Enterprise Manager Application DevelopmentGuide, respectively.

Who Should Use This BookAnyone who works with Solstice Enterprise Manager might need to use thisbook.

viii Solstice Enterprise Manager Troubleshooting Guide

Before You Read This BookBecause this book is oriented primarily toward resolving EM problems, it doesnot contain detailed procedures for performing common EM tasks. If you arenew to Solstice EM or are trying to perform a regular task, see the books listedin Related Books.

How This Book Is OrganizedChapter 1, “Introduction to Troubleshooting,” is an overview of troubleshootingconcepts and procedures.

Chapter 2, “Installation and Startup Problems,” identifies known problems withinstalling, configuring, and starting up Solstice EM software. For eachidentified problem, this chapter includes a description of a problem along witha step-by-step procedure for solving it.

Chapter 3, “Core Applications Problems,” explains how to solve known problemswith specific EM applications. For each identified problem, this chapterincludes a description of a problem along with a step-by-step procedure forsolving it.

Chapter 4, “Network Administration Problems,” describes how to solve knownproblems involved with network administration tasks through Solstice EM. Foreach identified problem, this chapter includes a description of a problem alongwith a step-by-step procedure for solving it.

Chapter 5, “Application Development Problems,” explains how to solve problemsassociated with developing applications that use the Solstice EM APIs. Foreach identified problem, this chapter includes a description of a problem alongwith a step-by-step procedure for solving it.

Chapter 6, “Network Protocol Problems,” describes problems associated withusing EM with different network protocols, including CMIP and RPC. For eachidentified problem, this chapter includes a description of a problem along witha step-by-step procedure for solving it.

Appendix A, “Error Messages,” identifies Solstice EM error messages andexplains how to respond to each one.

Preface ix

Related BooksThe following EM documents are referenced throughout this manual asappropriate for each specified problem:

• Solstice Enterprise Manager Installation Guide

• Solstice Enterprise Manager Administration Guide

• Solstice Enterprise Manager Application Development Guide

• Solstice Enterprise Manager API Syntax Manual

• Solstice Enterprise Manager Reference Manual

What Typographic Changes MeanThe following table describes the typographic changes used in this book.

Table P-1 Typographic Conventions

Typeface orSymbol Meaning Example

AaBbCc123 The names of commands,files, and directories;on-screen computer output

Edit your .login file.Use ls -a to list all files.host_name% You have mail.

AaBbCc123 What you type, contrastedwith on-screen computeroutput; new words or terms,or words to be emphasized

host_name% suThese are called class options.You must be root to do this.

<AaBbCc123> Command-line placeholder:replace with a real name orvalue

To delete a file, type rm <filename>.

AaBbCc123 Book titles Read Chapter 6 in User’s Guide.

x Solstice Enterprise Manager Troubleshooting Guide

Shell Prompts in Command ExamplesThe following table shows the default system prompt and superuser promptfor the C shell, Bourne shell, and Korn shell.

Table P-2 Shell Prompts

Shell Prompt

C shell prompt host_name%

C shell superuser prompt host_name#

Bourne shell and Korn shellprompt

$

Bourne shell and Korn shellsuperuser prompt

#

1-1

Introduction to Troubleshooting 1

1.1 IntroductionThis chapter introduces problem-solving procedures and definitions. Laterchapters in this book provide detailed problem-solution tables for knownSolstice EM situations.

It includes the following information:

• Definitions

• Commonly-Asked Questions

• Troubleshooting Processes and Procedures

• Specific Troubleshooting Information

1.2 DefinitionsBefore you can effectively use this book to solve Solstice EM problems, youshould confirm that the following terms are used as you would expect.

TroubleshootingA defined approach to solving problems that occur with the Solstice EMsoftware. This term does not typically refer to finding information aboutcommon tasks, although you might prefer that it did.

1-2 Solstice Enterprise Manager Troubleshooting Guide

1

$EM_HOME$EM_HOME is an environment variable that translates to the location whereEnterprise Manager software is installed. $EM_HOME defaults to/opt/SUNWconn/em .

1.3 Commonly-Asked QuestionsBecause Solstice EM is a complex product, users often ask a number ofquestions. The following table lists common questions and tells you where togo to find the answers. A more complete Frequently-Asked Questions list isavailable in the Solstice Enterprise Manager online Help.

1.4 Troubleshooting Processes and ProceduresMany people have their own approach to solving problems. If you do not, or ifyou are interested in seeing a specific approach detailed, this section providesone approach to problem solving. This approach provides guidelines and is notintended as a checklist.

1. Determine whether the problem is a Solstice EM problem, anothersoftware package problem, or a hardware problem.

2. Identify the specific area of Solstice EM that is affected.

3. Create a detailed problem statement, including specific key indicators ofthe problem, reproducibility, etc.

Table 1-1 Common Questions

To answer this question... Refer to...

How do I install EM? Solstice Enterprise ManagerInstallation Guide

How do I start up EM? Solstice Enterprise ManagerInstallation Guide

How do I manage networks with Solstice EM? Solstice Enterprise ManagerAdministration Guide

How do I develop applications that use theSolstice EM platform?

Solstice Enterprise ManagerApplication Development Guide

Introduction to Troubleshooting 1-3

1

4. Verify that you are using Solstice EM correctly, as described in theSolstice EM documentation.

5. Refer to the appropriate chapter in this book for information on thespecific problem area and follow the specified procedure.

6. If you continue to experience the problem, contact EM Customer Support.

1.5 Specific Troubleshooting InformationThe remaining chapters in this book provide detailed information aboutsolving specific EM problems. In all cases, the problems are presented in aneasy-to-follow format, similar to the following example.

Table 1-2 Insect Problems

If you see this... ▼ Do this... Refer to...

Ants are in your dishwasher. 1. Spray the existing ants with some lethal antspray.

2. Spray around the outside foundation of yourhouse with the same spray or a sprayspecifically designed to keep ants out for adesignated number of months.

3. You may also want to purchase some kind oftimed-release ant dust or posts to place aroundthe outside of your foundation.

Any available bookson ant control.


1

Crickets are in your house!Some people think crickets arejust fine and make pretty songs;others consider them to be fineonly when they are not in thehouse.

1. Depending on how long the crickets have beenin your house, you may be able to solve theproblem by just closing the garage door mostof the time or sealing the large gaps betweenthe door and the foundation.

2. If that does not work, spray the existingcrickets with some lethal cricket spray.

3. Spray around the outside foundation of yourhouse with the same spray or a sprayspecifically designed to keep crickets out for adesignated number of months.

4. You may also want to purchase some kind oftimed-release dust or posts to place around theoutside of your foundation.

Any available bookson insect control.

Table 1-2 Insect Problems


2-1

Installation and Startup Problems 2

2.1 IntroductionThis chapter provides information on resolving installation, configuration, andstartup problems. It contains the following information:

• Installation Failures

• EM Software Does not Start

2.2 Installation FailuresEM installation might fail for several reasons, as shown in Table 2-1:

Table 2-1 Installation Problems


You did not verify hardware orsoftware before installingSolstice EM.

1. Check the operating system on which youinstalled the software.

2. Check whether or not you installed all filesinto the correct directories.

3. Check your hardware.

For the final word onhardware and softwarerequirements for aspecific EM release, seethe Solstice EnterpriseManager InstallationGuide and the ReleaseNotes.


2

A hardware failure occurredwhile you were installing EM.

1. Check the hardware and fix the hardwareproblem, if needed.

2. Remove existing EM software from the system(to prevent corruption).

3. Reinstall EM software.

Hardwaredocumentation andSolstice EnterpriseManager InstallationGuide

Some error occurred duringinstallation that corrupted theEM software.

1. Typically, not all the EM software will becorrupted, only a specific package.

2. To check which packages are corrupted, usethe pkgchk utility. pkgchk verifies file sizeand checks certain attributes to ensure filescopy correctly from the installing location.

3. Remove existing EM software for thecorrupted package.

4. Reinstall EM software for the corruptedpackage.

Solstice EnterpriseManager InstallationGuide

The following message showedup during installation, afterSUNWemcpa was installed:mpa_error: Cannot bootemApplicationInstance

The CMIP MPA tries to connect to an EM MISwhen it is installed. If the MIS is not started, theMPA prints this error.

1. Restart the MIS after the packages have beeninstalled, then install SUNWemcpa. Thisensures that the MPA is connected to the MIS.

2. CMIP MPA can be run on systems that do nothave the MIS installed. For this to work, youneed to have set an environment variableEM_MIS_DEFAULT_HOST to the system onwhich the MIS is running before you installSUNWemcpa.

CMIP chapter inSolstice EnterpriseManager AdministrationGuide

During MIS initialization, thefollowing kinds of errors occur:

Storing ping_upcondition failed!

Adding ping_upcondition failed!

Some of the GDMO/ASN.1 files are part of theSNM Compatibility package and are needed fornetwork management templates such asdevice_reachable and pingUpOrDown.You need to install the SNM Compatibilitypackage (SUNWembc) on your system. Use thefollowing command:

# pkgadd -d SUNWembc


Table 2-1 Installation Problems


Installation and Startup Problems 2-3

2

2.3 EM Software Does not StartEM might not start for any of the reasons listed in Table 2-2.

Table 2-2 Startup Problems


You do not know how to startEM.

1. To start the Application Launcher, type em

2. If you receive a “command unknown”message, cd to the following directory or setthe $EM_HOME environment variable to thisdirectory:

/opt/SUNWconn/EM/bin

3. Then, type em.

4. The Application Launcher should start.

5. After the Application Launcher is started, clickone of the icons shown to launch the specificapplication.


You do not know how to startspecific EM applications fromthe command line.

To start the most commonly-used applicationsfrom the command line, use these commands:

Access Manager—host% em_accessmgrAlarm Manager—host% em_alarmmgrDiscover—host% em_discoverLog Manager—host% em_logmgrLog Viewer—host% em_logviewMIS Manager—host% em_mismgrObject Editor Browser—host% em_obedRequest Designer—host% em_reqeditViewer—host% em_viewer

Command LineSummary chapter inSolstice EnterpriseManager ReferenceManual

When trying to restart the MISusing em_services, you see anerror that says:

Can’t register withthe event dispatcher:Cannot register as anevent rendezvous:

Kill the existing inetd process and restart theMIS.

1. Find the existing inetd process using thefollowing command:

# ps -ef | grep inetd

2. Kill the inetd process. For example:

# kill -HUP 111

3. Restart the MIS, using the following command:# em_services

No references.


2

Port number mismatch errorduring em_services -r .

The error message you see indicates the specificdaemon that is experiencing the problem (forexample, em_snmp-trap ). This indicates that adaemon is trying to start up using a specific port,but some other daemon already has that port inuse.

1. Use the ps command to look for anotherprocess that might have that port locked up(for example, perhaps a partially completedem_services command).

2. Kill the old process and try em_servicesagain.

No references.

SQL errors when trying to startup EM daemon for workingwith Oracle databases.

The error message indicates an invalid driverdesignator.

1. Check the log2rdb.cfg file and the Oracletsnames.ora file for the right connectionstring. A correct connection string forSQL*NET V1 looks like: t:hostname:SID .For SQL*NET V2, the connection string isdefined in /var/opt/oracle/tsnames.orausing a LISP-like format.

2. Make sure the DATABASE name defined in thelog2rdb.cfg file is defined in thetsnames.ora file.

No references.




2

You have no idea what is wrong,but EM does not start up. Someof the possible indicators are:• The MIS is not started.• EM software has not been

installed correctly.• EM software is corrupted.• You have not set up your

environment correctly orcompletely.

1. Verify the MIS is running by typing thefollowing command:

host_name% ps -eaf | grep mis

2. If you do not see a display similar to thefollowing, then restart the MIS.

root 1508 1 80 09:15:52 pts/5 0:21em_mis

3. To restart the MIS, log in as root to the machineon which the MIS is running, and type thefollowing command:

host_name# $EM_HOME/em_services

4. If the MIS is running, but you see an errormessage like the following, you need to setappropriate environment variables:

em_host: can’t open display,exiting...

Use the SETENV command to set display toyour workstation. For example, if yourworkstation is called “my_host” and you havejust opened a window on “other_host,” fromsome_other_host, type the followingcommand:

other_host% setenv DISPLAY my_host





2

(continued from previous page) 5. If the MIS is running, but you see errormessages like the following, you need toprovide access to your host from the MISserver:

Xlib: connection to “doctest:0.0”refused by server

Xlib: Client is not authorized toconnect to Server

Error: Can’t open display:doctest:0.0

Use the xhost command to authorize accessto your workstation. For example, if yourworkstation is called “my_host” and you aretrying to run EM from “other_host,” type thefollowing command from a window attachedto your workstation:

my_host% xhost other_host

6. Try to start the Application Launcher again.

7. If the Application Launcher still fails to start, itis likely that your EM software has beencorrupted (perhaps due to a disk problem).Reinstall EM software.


When you click on one of thecore applications in theApplication Launcher window,the application does not start(For information on errormessages, see Appendix A,“Error Messages”).

1. Log in as root to the machine on which the MISis supposed to be running.

2. Start the MIS by typing the followingcommand:

host_name# $EM_HOME/em_services

3. After you have verified that the MIS isrunning, try to access the core applicationsagain.

4. If the MIS is running and this is a newinstallation of EM, look at the installationsection for more information.





2

Specific EM Application doesnot start with the expectedproperties

Most of the EM applications have configurableproperties. When you change these properties,you must save them for them to be in effect thenext time you start the applications.

1. Reconfigure the properties to be as you want.

2. Save the properties.

For information onconfiguring a specificapplication, see thesection for thatapplication in theSolstice EnterpriseManager ReferenceManual.




2

3-1

Core Applications Problems 3

3.1 IntroductionThis chapter provides information on resolving problems with specific SolsticeEM applications. It contains the following information:

• General Application Problems

• Discover Problems

• Alarm Manager Problems

• MIS Communication Problems


3

3.2 General Application ProblemsYou might need help with any of the following general application situations,described in Table 3-1:

Table 3-1 General Application Problems


An application has buttons thatare “grayed out,” or certainapplication functionality isrestricted.

1. It is likely that the user does not have fullaccess to the application or the features of theapplication. Bring up Access Manager andcheck the user’s privileges using View UserPrivileges.

2. To fix this problem, you need to add the userto the appropriate group or change theprivileges for the group to which the usercurrently belongs.

Access Managerchapter in the SolsticeEnterprise ManagerReference Manual.

EM application icon is not“grayed out” when it should be.

1. Non-EM applications are never grayed out. Ifthe application is an EM application, checkwhether the “Yes” toggle in the ApplicationProperties window is selected.

2. Verify that the EM Application Name is thesame as the name the application uses toconnect to the MIS.Note: This might not always be the same as thename of the executable.

Access Managerchapter in the SolsticeEnterprise ManagerReference Manual.

Core Applications Problems 3-3

3

You need to add an applicationto the Application Launcher.

1. To add an application to the ApplicationLauncher, you need to know the name of theapplication (for example, Browser) and itsexecutable (for example, em_browser ).

2. If you want the application to show up as anicon in the Application Launcher’s mainwindow, you need to create an icon to putthere.

3. To add the application to the ApplicationLauncher, select the Application Propertiesoption from the File menu.

4. Fill in the Icon Name, Path to Executable, andPath to Icon fields.

5. If the application is an EM application or auser-developed application that uses EM’saccess control features, click the Yes buttonnext to EM Application and fill in the EMApplication Name.Note: The EM Application Name is the namethe application uses to connect to the MIS. Thismight not always be the same as the name ofthe executable.

6. Click Add to add the application’s icon to theApplication Launcher’s main window.

Application Launcherchapter in the SolsticeEnterprise ManagerReference Manual.

When you start an applicationfrom the Application Launcher,the Launcher does not wait forthe application to start.

1. Change em_panel.response to 1 in theem_panel.cf file.

Solstice EnterpriseManager ReferenceManual.

The Application Launcherincludes applications you do notuse.

1. Select the Configure Applications option fromthe Application Launcher’s Options pull-downmenu.

2. Select the specific application you want toremove from the Applications list.

3. Click Delete.

Application Launcherchapter in the SolsticeEnterprise ManagerReference Manual.




3

3.3 Discover ProblemsYou might need help with any of the Discover situations described in Table 3-2.

Tools that are listed on the Toolspull-down menu do not runwhen selected.

1. Verify that you have the correct executableshown in the Configure Tools for the tool youwant to run.

2. Find out if this tool runs from some otheraccess point (for example, directly from theApplication Launcher or from the commandline).


Table 3-2 Discover Problems


Discover does not start. If you are not root and you install EM in a non-default directory, Discover will not start. This isbecause Discover runs as a setuid process andthe LD_LIBRARY_PATH variable is not inherited.Try the following solutions:

3. Always run Discover as root.

4. Create $EM_HOME/lib and put a link tolibpmi.so .

Discover chapter in theSolstice EnterpriseManager ReferenceManual.




3

Messages in the Monitorwindow indicate that there areno containers to monitor.

1. Check to see if you have run a discovery yet. Ifnot, do so, then run the Monitor again.

2. If you have run a discovery, verify that the MISis running by typing the following command:


3. If the MIS is not running, restart it. To restartthe MIS, login as root to the machine onwhich the MIS is running and type thefollowing command:

host_name# $EM_HOME/bin/em_services

4. If the MIS is running and this is a newinstallation of EM, look at the installationproblems section for more solutions.

5. After you have verified that the MIS isrunning, try to start the Monitor again.


When you run a discoveryfunction, managed objects thatyou know exist are notdiscovered. This can manifestitself by a known object notbeing visible in the Viewer.

1. Verify whether or not the object is visibleoutside of EM. For example, can you “ping”the object?

2. If you know the object exists, try runningDiscover from the command line as follows:

host_name% em_discover -device<device_to_discover>

3. This form of discovery finds the objectregardless of the subnetwork on which it lives.


You ran a flat discovery andspecified a name (for example,“Routers”) and then ran ahierarchical discovery (forexample, under Internet), andthe result was that thehierarchical discovery addednodes under the resulting viewof the flat discovery.

You cannot run a flat discovery, which corruptsthe network topology tree, and then run ahierachical discovery and get correct results. Whatyou probably intended to do was to collect theinformation into a single view (for example,collect all the routers into a view). To achieve this,do the following:

1. Run a regular discovery.

2. Use the Viewer Tools --> Find tool to collect allthe information you want into a single view.





3

3.4 Alarm Manager ProblemsYou might need help with any of the Alarm Manager situations, described inTable 3-3.

You tried to use the ARP TableOnly method for a discovery ona subnet other than the one youare on and it defaults back toSerial Ping method.

The ARP Table Only method can be used only onthe local subnet, so you cannot do what you triedto do.


Table 3-3 Alarm Manager Problems


When you click theAcknowledge or Clear button,the alarm status does notchange.

Verify that you have privileges to acknowledgeand clear alarms. If not, contact your networkadministrator.

Access Manager andAlarm Managerchapters in the SolsticeEnterprise ManagerReference Manual.

The Alarm Manager seems to betaking a long time to start up.

If you have a large number of alarms in youralarm log, sometimes Alarm Manager takesawhile to start.

Alarm Manager chapterin the Solstice EnterpriseManager ReferenceManual.




3

3.5 MIS Communication ProblemsYou might need help with any of the MIS situations described in Table 3-4.

Table 3-4 MIS Communication Problems


You are unable to viewinformation on a remote MIS.

It can be difficult to determine whether a remoteMIS is down or the network connection to theremote MIS is broken. The symptoms are similar.

Any standard networkadministration book.

You cannot get your MIS tocommunicate with an MIS onanother machine or system.

To some extent, the solution depends on what youneed to do with the additional MIS. For example,if you only want to view event information onanother MIS, you can access the second MISdirectly from the Log Viewer’s Propertieswindow.If, on the other hand, you want to forward eventsto another MIS, you have to use the MIS Managerto define the EFD (Event ForwardingDiscriminator) to enable this capability.

MIS-to-MISCommunicationchapter in the SolsticeEnterprise ManagerReference Manual.


3

4-1

Network Administration Problems 4

4.1 IntroductionThis chapter provides information on resolving network administrationproblems with Solstice EM. It provides the following information:

• Tools for Evaluating Your Network

• Evaluating Network Failures

For detailed information on how to use EM to perform network administrationtasks, see the Solstice Enterprise Manager Administration Guide.

4.2 Tools for Evaluating Your NetworkMost of the Solstice EM core applications provide tools for monitoring networkstatus and responding to network events. In particular, the followingapplications provide specific information:

• Viewer—Provides a visual display of the managed objects in your network.

• Discover—Allows you to find out what objects are visible in your networkand to monitor communications among those objects.

• Log Manager—Allows you to keep a record of events that occur on yournetwork.

• Alarm Manager—Allows you to respond to events that occur on yournetwork.


4

• Request Designer—Allows you to identify events to respond to and defaultvalues for responding to those events.

For more information about using these EM applications, see the SolsticeEnterprise Manager Reference Manual.

4.3 Evaluating Network FailuresYou might experience any of the network problems listed in Table 4-1.

Table 4-1 Network Problems


The physical configuration ofyour network does not agreewith what Solstice EM displaysin the Viewer.

1. To populate the MIS automatically, use theDiscover application. Discover finds hosts,routers, networks, links, and SNMP devices tobe managed. When Discover finds one of theseelements, it creates a record in the MIS for thatelement.

2. In some instances, recent changes to theconfiguration might not be visible in theViewer yet. Try shutting down and restartingthe Viewer.

3. In other cases, the MIS database can becomecorrupted. In this case, manually remove theobjects that appear to be incorrect and run anew discovery or use the following commandto discover a specific device:

host% $EM_HOME/bin/discover -device<device_name>

Discover and Viewerchapters in SolsticeEnterprise ManagerReference Manual.

When you run a discovery onyour network, EM findsnothing.

1. Your network might be down. Check thehardware and fix the hardware problem, ifneeded.

2. Verify that Discover is functioning correctly.


You have configured yournetwork to report particularevents; however, when theevents occur, EM does not showthem.

1. Event forwarding discriminators (EFDs) arenot defined correctly.


5-1

Application Development Problems 5

5.1 IntroductionThis chapter provides information on resolving problems with Solstice EMfrom a development perspective. For detailed information on working withEM from an application development perspective, see Solstice EnterpriseManager Application Development Guide.

This chapter contains the following information:

• EM API Problems

• GDMO Problems

5.2 EM API ProblemsYou might experience any of the problems shown in Table 5-1 whendeveloping code that uses the EM platform.

Table 5-1 PMI Problems


You compile your applicationwith included PMI calls, butwhen you run the application,you do not see any errormessages and it does not dowhat you expected.

You forgot to call the appropriate error handlingroutines in your application.

Solstice EnterpriseManager API SyntaxManual for informationon Error Class.


5

If you use Rogue Wave classes(for example, Tool.h++ ), youmight see error messages duringcompilation that appear toblame the Rogue Wave classfiles. The errors will be similarto the following:

“/opt/SUNWspro/SC4.0.1/include/CC/rw/regexp.h,” line74: Error: “}” expected

instead of “(“.

“/opt/SUNWspro/SC4.0.1/include/CC/rw/regexp.h”,line74: Error: no directdeclarator preceding “(“.

You must include the Rogue Wave classes beforethe PMI classes. For example, if you had thefollowing series of include statements:

#include <pmi/hi.hh>#include <rw/cstring.h>#include <rw/regexp.h>#include <rw/rstream.h>

You should change the sequence to:

#include <rw/cstring.h>#include <rw/regexp.h>#include <rw/rstream.h>#include <pmi/hi.hh>

Solstice EnterpriseManager ApplicationDevelopment Guide.

When you do multiple, scopedGETs through the PMI, theresponses are buffered, whichcauses performance to degrade.When the MIS processes a GET,it sends a response to the PMI.Upon receiving the reponse, thePMI attempts to construct animage out of the response to beincluded in the Album. To do so,it needs the MDR informationfor the class. Upon checking thecache, it finds no suchinformation and sends anACTION to the MIS to get theMDR information. The MIS,however, cannot get to theACTION until all the responseshave been completed. Thus, thePMI queues the remainingresponses until the ACTION issatisfied.

To avoid making the PMI wait for the MISresponses to complete, pre-cache the informationfrom the MDR. Specifically, instead of thefollowing code:

album.set_derivation(“xxxxxx/LV(1)”);

album.derive();

Use the following code:

Image im(duNONE, <objectClass>);

im.boot;

album.set_derivation(“xxxxxx/LV(1)”);

album.derive();

For information aboutthe specific syntax ofAPI functions andclasses, see the SolsticeEnterprise Manager APISyntax Manual.



Application Development Problems 5-3

5

5.3 GDMO ProblemsWorking with GDMO is a simple yet complex task. Table 5-2 illustrates thekinds of problems you can have when working with GDMO and how to

You tried to send a synchronous,confirmed request (also called a“round-trip request”)viewerapi_send_request() in an event callback (handler).This does not work because thereponse would come to theevent queue of the sendingprocess, but the sending processwould not be able to examinethe queue because it wasalready in an event callback.Only after the callbackcompletes can the event queuebe examined. Thereforeviewerapi_send_request() would be blocked until time-out, but the request may well besent out and executedsuccessfully in the remoteprocess.

Send an asynchronous requestviewerapi_start_send_request( ) , or insimple cases, an unconfirmed requestviewerapi_send_request_unconfirmed( ) ,or if possible, do the synchronous, confirmedrequest outside the callback.

For information aboutthe specific syntax ofAPI functions andclasses, see the SolsticeEnterprise Manager APISyntax Manual.




5

respond to them.

Table 5-2 GDMO Problems


You want to add a newnotification to the platformsimilar to an existingnotification (for example, acommuncationsAlarm). Youcreate a new GDMO documentwith your notification and add amapping in every object so thatyour event will get logged as anemAlarmRecord.

Everything goes smoothly (noGDMO compilation errors), butwhen the event is sent,probableCause andspecificProblems are notlogged even though they werepresent in the event.

Your GDMO document lookslike this:

myEvent NOTIFICATION

BEHAVIOURsnmAlarmEventBehaviour;

WITH INFORMATION SYNTAXNotification-ASN1Module.AlarmInfo

AND ATTRIBUTE IDSprobableCause probableCause,

specificProblemsspecificProblems;

REGISTERED AS {em-mpa-notification 1};

myEventBehaviour

BEHAVIOUR

DEFINED AS

"This notification is used tosend my event duh";

probableCause and specificProblems aredefined in a different GDMO document and thiswas not caught during compilation. When thelogRecord is created, the log module cannot findthose attributes so it bypasses them.

1. The attributes should be defined as follows.

AND ATTRIBUTE IDS

probableCause

"Rec. X.721 | ISO/IEC 10165-2 :1992": probableCause,

specificProblems

"Rec. X.721 | ISO/IEC 10165-2 :1992":specificProblems;

For detailedinformation aboutGDMO, see ITU X.722ISO/IEC 10165-4Guidelines for theDefinition of ManagedObjects (GDMO).

6-1

Network Protocol Problems 6

6.1 IntroductionThis chapter provides information on resolving problems that occur when youwork with various protocols. It provides information about the following:

• Working with CMIP

• Working with SNMP

6.2 Working with CMIPWhen working with CMIP, you might experience the problems listed inTable 6-1.

Table 6-1 CMIP Problems


You don’t know how to start theCMIP Configuration utility.

To configure CMIP agents, use the ObjectConfiguration Tool (OCT). Type the followingcommand:

host% $EM_HOME/bin/em_oct -cmip


CMIP MPA does not start. Solstice EM’s daemons start up when you run thefollowing command:

host_name# $EM_HOME/bin/em_services

Solstice EnterpriseManager InstallationGuide.


6

You do not know how to set upcommunication from one MIS toanother.

To some extent, the solution depends on what youneed to do with the additional MIS. For example,if you only want to view event information onmultiple MISs, you can access the second MISdirectly from the Log Viewer’s Propertieswindow.If, on the other hand, you want to forward eventsto another MIS, you have to define the EFD (EventForwarding Discriminator) to enable thiscapability.


You are unable to viewinformation on a remote MIS.

Either:

1. You have not correctly configured the MIS-MIScommunication. Use the MIS Manager to dothis.

2. The remote MIS server is down.

3. The network connection between your currentMIS and the remote MIS is broken.


Table 6-1 CMIP Problems


Network Protocol Problems 6-3

6

6.3 Working with SNMPWhen working with SNMP in the EM environment, you might experience theproblems listed in Table 6-2.

Table 6-2 SNMP Problems


You attempted to delete an entryfrom an SNMP MIB eitherthrough the SNMP Browser orfrom within some user-developed code function and itdoes not work.

You need to perform some special setup steps toenable EM to delete entries from SNMP MIBs.

1. Compile the MIB to its GDMO and ASN.1 filesusing em_cmib2gdmo . If the MIB has alreadybeen compiled, ignore this step.

2. Consult the text definitions of the table entriesin the MIB and find the attribute used fordeletion of the entry and its value.

3. In the corresponding GDMO file for the entry’sname bindings, modify the following values:CREATEDELETEATTCREATEDELETEVALUELook at the following example for MIB-II.In rfc1213.mib , you have the following:

ipNetToMediaType OBJECT-TYPESYNTAX INTEGER {

other(1),invalid(2),dynamic(3),static(4)

}

Then, in rfc1213.gdmo , you might havesomething like this:

MULTIPLEINSTANCESINDEX

ipNetToMediaIfIndex,ipNetToMediaNetAddress;

CREATEDLETEATT ipNetToMediaTypeCREATEDELETEVALUE 2

ENDMULTIPLEINSTANCES

For more informationabout working withnetwork protocols, seethe Solstice EnterpriseManager AdministrationGuide.


6

A-1

Error Messages A

This appendix provides a list of Solstice Enterprise Manager error messages.For each message, it includes a description (what the message means) andresponse (what to do about it). The messages are listed in alphabetical order,based on the first standard word in the message. For example, if you see thefollowing message:

em_panel: can’t open display, exiting...

You would look for the message:

can’t open display, exiting...

A-2 Solstice Enterprise Manager Troubleshooting Guide

A

Table A-1 Application Error Messages

Message.... What it means... ▼ How to respond...

address compare failed (port number)mismatch

Upon invoking the em_snmp-trap daemon (to interact withSNMP traps), the em_snmp-trap and na.snmp-trapddaemons are in contention for aport.

1. Edit the inetd.conf file andcomment out the snmp-trapd entry.

2. Kill the inetd process, using kill -HUP.

3. Restart the em_snmp-trap daemon.

Album derive failed - Cannot accessalarm log

An internal error occurred in theAlarm Manager.

Exit and restart the Alarm Manager.

Application Launcher could not createicon - Exiting

The Application Launcher couldnot display the specified icon onyour screen. Either:• You have run out of colors.• The specified icon file does

not exist.

Exit any color-intensive applications,such as WWW browsers, graphicspackages, and word processors.

Cannot create default glyph -- exiting The Viewer could not displaygraphical data on your screen.Either:• You have run out of colors.• The specified icon file does

not exist.

Exit any color-intensive applications,such as WWW browsers, graphicspackages, and word processors.

Cannot Read from File Either:• The specified alarm log file

does not exist.• The specified file does not

have the right format for analarm log file.

• You do not have access tothe specified file.

1. Verify that the file you are trying toload is a valid alarm log file.

2. Make sure you have the right filename.

Error Messages A-3

A

Cannot retrieve topology data from theMIS. Exiting!!

Discover cannot accessinformation about the networkin the MIS.

1. Verify the MIS is running by typingthe following command:


2. If you do not see a display similar tothe following, then restart the MIS.

root 1508 1 80 09:15:52pts/5 0:21 em_mis

3. Restart the MIS.

4. Restart Discover.

Cannot Write to File Either:• You do not have write access

to this alarm log file.• You have run out of disk

space.

1. Verify the disk space available byusing the following command:

host_name% df -k

2. Check the file protection on the alarmlog file by using the followingcommand:

host_name% ls -l<alarm_log_file_name>

Can’t alloc %s Request Designer cannotallocate memory to perform thespecified function.

1. Check memory usage on yourmachine and on the MIS server.

2. Sometimes memory remainsallocated for applications that haveterminated. To correct this problem,shut down all applications on themachine and reboot the machine.

Can’t connect to MIS! 1. You tried to start an EMapplication, but the MIS isnot running.

2. You are not registered toaccess this MIS. Use theAccess Manager to addaccess for the user and/orgroup.

1. Start the MIS by typing the followingcommand

host_name#$EM_HOME/bin/em_services

2. Reconnect the Application Launcherto the MIS, if needed.

3. Start or Restart the application.




A

Can’t connect to MIS!cannot connect to server %s

Either:• The MIS is not running.• There is a network problem

between your host and theMIS server host.

1. To restart the MIS, log in as root to themachine on which the MIS is running,and type the following command:


2. If the MIS is located on a remote hostand you cannot log in to it, check thephysical network. Use ping<host_name> to find out if you cansee the remote host.

Can’t find registered oid for %.200s You are operating on an objectthat is not registered. This mightmean you have the wrong objectidentifier (OID) for the object orthe object is not a valid object.

1. Use OBED to verify the OID for theobject.

2. If you are trying to operate on a newobject, you need to register the object.

Can’t locate template Request Designer is trying toload a request template file thatdoes not exist in the MIS. Youmight have mistyped a name.

Verify the name of the request templatefile through OBED and try again.

<application_name>: can’t open display,exiting...

Your environment display is notset to your workstation. Usually,this means you just completed aremote login and forgot to setthe display from the remotelogin screen.

1. Use the SETENV command to set thedisplay to your workstation.For example, if your workstation iscalled “my_workstation_name ” andyou have just opened a window on“some_other_host ,” fromsome_other_host , type thefollowing command:

some_other_host% setenvDISPLAYmy_workstation_name:0.0

2. Try to run EM again.



Error Messages A-5

A

Can’t register with the event dispatcher:Cannot register as an event rendezvous:

Upon restarting the MIS, there isan old inetd process on thesystem.

1. Find the existing inetd process usingthe following command:

# ps -ef | grep inetd

2. Kill the inetd process. For example:

# kill -HUP 111

3. Restart the MIS, using the followingcommand:

# em_services

Condition being used between <state1>& <state2> in Template<template_name>.

You attempted to delete acondition from the RequestDesigner, but the conditioncannot be deleted because it iscurrently in use.

Nothing—you cannot delete the specifiedcondition without first deleting it fromthe template that is using it.

Could not connect to MIS on<host_name>...

Most likely the MIS is notrunning on the specified host.

Restart the MIS on the specified host.

Could not display alarms in log = %sEither the MIS connection is downor log is not available

Either:• The alarm log (as identified

by the %s information) doesnot exist.

• The MIS has disconnected.

1. Verify the alarm log exists and thatyou typed in the correct name for it.

2. Verify the MIS is running by typingthe following command:


3. If you do not see a display similar tothe following, then restart the MIS.

root 1508 1 80 09:15:52pts/5 0:21 em_mis



Couldn’t boot topology image An object that should be visiblein the Viewer cannot bedisplayed due to an internalsoftware error.

Call customer support.




A

DEBUG caution !!!: album invalid This application developmentmessage means the developerdefined the album classincorrectly or created membersof the album that do not belongthere.

Fix the album definition.

Default status option %s does not exist.Using %s instead.

A specified status option is not avalid status option. EM will usethe default option.

Either correct the status option to a validoption or let EM use the default.

Discover: fork () failed Discover could not create a newprocess to run. This usuallyoccurs due to one of thefollowing conditions:• The system-imposed limit on

the total number of processesunder execution by a singleuser would be exceeded.

• The total amount of systemmemory available istemporarily insufficient toduplicate this process.

• There is not enough swapspace.

Reboot.

Discover: pipe() failed Discover’s attempt to create aninterprocess channel failed.Usually, pipe() fails if too manyfile descriptors are currentlyopen for a process or a file tableentry could not be allocated forthe process.

Reboot.

em_dataviewer: Couldn’t Get superior(parent) object, cancelling

Data Viewer attempted to getdata on the parent object(superior object from whichproperties are inherited) for thecurrent object. The operation hasbeen terminated.

Restart the MIS.



Error Messages A-7

A

em_panel: Can’t open config file: The configuration file for theApplication Launcher or one ofits applications is locked ormissing.

1. Verify the configuration file exists.

2. Verify the configuration file has theappropriate protections set.

em_panel: couldn’t open file The executable file for theapplication is locked or missing.

1. Use the Configure Applicationsoption to verify the correct pathnamehas been provided.

2. Verify the file exists and hasprotections set appropriately.

EM_PANEL couldn’t start command: Application Launcher tried toexecute a command as specifiedin the Configure Applicationswindow and could not.

1. Verify the command is valid.

2. Check that all paths are set to enablerunning the command.

em_panel: missing argument for The configuration for anapplication is missing anargument.

1. Check the information for theapplication in the ConfigureApplications window.

2. Verify the arguments shown for theapplication in this window are validarguments for the application.

em_viewer: couldn’t start cmd Viewer tried to execute acommand as specified in theConfigure Tools window andcould not.

1. Verify the command is valid.

2. Check that all paths are set to enablerunning the command.

Error: bad display valuecouldn’t get objname()

OBED was not able to displayinformation about the specifiedobject.


Error creating grapher rpc client:Error occurred calling the rpc servermsg failed: rpc server error =>

Attempt to start Grapher fromAlarm Manager failed.

Try starting Grapher from the commandline using the following command:

$EM_HOME/bin/em_grapher

error getting album_name OBED could not accessinformation about the specifiedalbum.





A

Error importing file xxxFailed to create user yyy

This error occurs when usingthe Import function of AccessManager. It means the user istrying to import a user loginthat is not valid for the currentMIS host.

Edit the file being imported (which is anASCII file) and remove the invalid userlogin.

Error in executing %s Application Launcher could notrun the specified executable.

1. Try to run the executable outside ofthe Launcher.

2. If it runs outside of the Launcher,check the configuration information toensure you have specified the correctexecutable information.

Error in Setting up Nickname Service The nickname service uses adaemon.

Verify that the nickname daemon isrunning.

ERROR opening object:get on parent_obj failed

OBED was unable to accessinformation about an object’sparent.

Check whether OBED can access theparent object directly (rather than as theparent of the child).

Got callback, but can’t translate It’s broken! Call customer support.

Invalid CMIS filter The CMIS filter information inthe Properties window does notconform to CMIS filteringguidelines.

For details on CMIS filtering, see theCMIS Scoping and Filtering section in theEM Reference Manual.

Invalid Netmask! Information in the Netmaskfield of the Discover Propertieswindow does not match theformat of a netmask.

Make sure the netmask fits the correctformat. For example, 255.255.255.0.

Invalid Network Name/Number! The network name specified inthe Discover Properties windowis not a valid network name.

Enter the name of a valid network, forexample, LLL22-000-n.

Invalid Network Number! The network number specifiedin the Discover Propertieswindow is not a valid networknumber.

Enter the number of a valid network, forexample, LLL22-000-n.



Error Messages A-9

A

Invalid password on the MIS host The password entered is notcorrect for the given user loginon the host on which the MIS isrunning.

Type your password correctly and tryagain.

Invalid Proxy! It’s broken! Call customer support.

ld.so.1: gdmo: fatal: libpmi.so: can’t openfile: errno=2

The directory containing one ormore of the important EM filesis not part of yourLD_LIBRARY_PATHenvironment variable.

1. Look at your path to see what isdefined. To do this, type setenv fromany prompt.

2. Note the directories listed in thePATH statement.

3. You should be able to identify themissing file from the error message.Find the directory that contains thisfile.

4. Redefine your path so that it containsthe appropriate directory.

LoginClient: Can’t get user passwordsalt...

The user login entered is not avalid user login for the host onwhich the MIS is running.

1. Verify that the user login entered isvalid on the MIS host machine.

2. Verify that the user login has beenadded to the MIS through AccessManager.

LoginClient: Couldn’t receive messagefrom em_login...

The em_login daemon is notrunning.

1. Check to see if other em daemons arerunning. If they are, try restarting justthe em_login daemon. Use thefollowing command:

# $EM_HOME/em_login

2. If this does not work, restart EM usingthe following command:

# $EM_HOME/em_services

LoginClient: User name length is notbetween 1 and 8...

The user login entered is eithertoo short or too long.

Verify that the correct user login ID isbeing used and try again.




A

MIS server disconnected... The MIS disconnected while theapplication was running.

To restart the MIS, log in as root to themachine on which the MIS is running,and type the following command:


Monitor: pipe() failed Discover’s attempt to create aninterprocess channel for amonitor function failed. Usually,pipe() fails if too many filedescriptors are currently openfor a process or a file table entrycould not be allocated for theprocess.

Reboot.

Not authorized to run<application_name>!

User has not been authorized toaccess this application.

Use the Access Manager to change theuser’s authorization.

Platform Disconnected...Press OK to continue

The MIS disconnected while theAlarm Manager was running.



2. Restart the Alarm Manager.

Platform has Disconnected! The MIS disconnected whileDiscover was running.



2. Restart Discover.

Platform has Disconnected. Save currentproperties?

The MIS disconnected while LogManager was running.





Error Messages A-11

A

Print Failed. Unable to open temp file %s EM could not open a temporaryfile to use for printing. Thisusually means you have run outof disk space.

Use the following command to see if youhave any disk space available:

host% df -k

Print failed. Can’t fork. EM could not create a newprocess to run. This usuallyoccurs due to one of thefollowing conditions:• The system-imposed limit on

the total number of processesunder execution by a singleuser would be exceeded.

• The total amount of systemmemory available istemporarily insufficient toduplicate this process.

• There is not enough swapspace.

Reboot or perform other maintenance tofree up system space.

Remote MIS %s has been disconnected.All displayed alarm logs in this MIS willbe removed.Press OK to continue.

The remote MIS disconnectedwhile the Alarm Manager wasrunning.

1. The alarm information from that MISgoes away.

2. To view alarm information for theremote MIS, restart the MIS on theremote system and reload the alarmlog.

SET_DERIVATION FAILED It’s broken! Call customer support.

snm_gr: Cannot grab lockfile. snm_grmay already be running.

A user tries to start more thanone instance of the Grapherapplication. This error occurs ifthe Grapher terminatesabnormally and the userattempts to restart it.

1. Remove files from the /tmp directorythat have the following format:

snm_gr.rpcid.<user_id>

snm_gr.lock.<user_id>

Where <user_id> matches the userwho has the problem.

2. Restart the Grapher.

Some of the necessary information wasmissing,please fill in all required fields and tryagain.

You did not fill in all requiredCMIP configurationinformation.

1. Fill in all the fields.

2. Try again.




A

Storing object to MIS failed. Error = %s. EM could not write the CMIPconfiguration information intothe MIS. This means:• The MIS is down.• You do not have

authorization to write to theMIS.

• The MIS server has run outof disk space.

1. Verify that the MIS is running.

2. Verify that you are authorized toaccess the MIS.

The Name %s Is Associated WithMultiple Objects. Using Object With Id%d.

The Data Viewer has foundmultiple objects in the MIS thathave the same name. The secondpart of the message identifiesthe specific OID for which theData Viewer will display thedata.

1. If Data Viewer is displaying the objectyou wanted, you could do nothing.

2. If, however, you want to preventconfusion, rename one of the objectsto a new, unique name.

There are no selected objects todiscover!

The Discover Propertieswindow results in no objectsbeing discovered. You selectedTypes to discover, but did notselect any specific types.

Change the selection criteria to All orIndividual or select specific types todiscover.

Topology database doesn’t exist The Viewer is unable to accessthe topology database. Either:• The database file has been

removed.• The machine on which the

database file exists isunreachable.

1. Verify that the database exists.

2. Verify that the system on which youare running the Viewer is able toreach the system on which thedatabase exists.

Unknown Alarm Type %s An alarm instance is of anunknown alarm type. Thisusually means the alarm is notone of the standard alarm types.

Depending on what you want to do withthe alarm, this message might not affectyour work.

User does not belong to any group The user login has not beenassigned to a group in AccessManager.

Use Access Manager to add user login toa group in the MIS.



Error Messages A-13

A

User does not exist in Access ControlObjects

The user login is not registeredwith the EM platform.

Use Access Manager to create the userlogin in the MIS and assign the user loginto access groups.

User does not have connection privilege The user login does not belongto a group with privileges forthe application being run.

Use Access Manager to add the user tothe appropriate group or modify groupprivileges for the group to which the userbelongs.

Using default object glyph Either:• You do not have enough

colors available to use thespecified icons.

• No icon is identified for aspecific application.

1. If you have run out of colors for yourdisplay, you see some other icon inplace of the expected icons. Forexample, the Viewer might use the“host” icon in place of the “universe”icon.

2. To respond to this situation, exit fromany color-intensive applications, suchas Netscape or FrameMaker.

3. Restart the Viewer.

View Properties have changed. Savenew properties?

You modified Log Manager’sviewing properties and are nowexiting the Log Managerapplication.

1. If you want Log Manager to be able torestart with the current properties,click Yes.

2. If you do not want to save thechanged properties, click No.

Warning: <application_name>: Can'tAllocate Label Color

Either:• You do not have enough

colors available to use thespecified color.

• You specified a color thatdoes not exist.

1. Verify the label is set to an existingcolor.

2. If you have run out of colors for yourdisplay, exit from any color-intensiveapplications, such as Netscape orFrameMaker.

3. Restart the application.




A

Xlib: connection to <host_name>refused by serverXlib: Client is not authorized to connectto ServerError: Can’t open display: <host_name>

EM is not authorized to displayinformation to yourworkstation. Usually, this meansyou just completed a remotelogin and forgot to set access toyour workstation from the EMserver.

1. Use the xhost command toauthorize access to your workstation.For example, if your workstation iscalled “my_workstation_name” andyou are trying to run EM from“some_other_host,” type thefollowing command from a windowattached to your workstation:

my_workstation_name% xhostsome_other_host

2. Try to run EM again.



Error Messages A-15

A

Table A-2 PMI (Portable Management Interface) Error Messages


Could not connect to MIS on <server_name> A PMI call attempted toconnect to a remote hostthat does not have arunning MIS.

1. Change the PMI call to connect to ahost on which the MIS is running.

2. If the MIS should be running on thespecified remote host, restart the MISon the remote host.



PMI_SUCCESS A PMI call completedsuccessfully.

Nothing. This verifies the call completedsuccessfully.

This Image was constructed without settingthe <objname> parameter to duNONE

This Image wasconstructed without settingthe <objname> parameter toduNONE. The problem isthat the Image constructoris called using the SuperiorOI as the objname as in:

Image im = Image(TOPODB, TOPOCLASS);

Not only does this createthe behavior detailed above,but you must also callImage::shut_down aftercalling create_within()before create_within can beused again.

1. Try the following workaround:

Image im = Image( duNONE,<object class>);

before calling Image::create_within().

2. However, if you used the imageconstructor, the PMI starts referringwrong objects and there is nothing auser can do.


A

Index-1

Index

Symbols$EM_HOME, 1-2

Aaccess control

error, A-8, A-10Access Manager

error, A-8acknowledging alarms, 3-6ACTION request, 5-2alarm

error, A-12Alarm Manager, 4-1

access problems, 3-6error, A-2, A-3, A-5, A-7, A-8, A-10,

A-11, A-12startup time, 3-6

albumerror, A-2, A-7

album.derive, 5-2album.set_derivation, 5-2API errors, 5-1Application Launcher

error, A-2, A-7, A-8waiting to start applications, 3-3

applications

how to start, 2-3waiting to start, 3-3

Ccan’t register

error, 2-3, A-5clearing alarms, 3-6CMIP

configuration, 6-1MPA, 6-1utility, 6-1

CMISerror, A-8

collecting managed objects, 3-5color

error, A-13communicating with remote MIS, 3-7configuration, 4-2connect

error, A-3, A-4, A-5, A-14

Ddaemon

em_login, A-9daemons, 6-1Data Viewer

Index-2 Solstice Enterprise Manager Troubleshooting Guide

error, A-6, A-12defining EFDs, 6-2disconnect

error, A-10Discover, 4-1, 4-2

ARP table only, 3-6device option, 3-5error, A-3, A-4, A-6, A-8, A-9, A-10,

A-12flat discovery, 3-5hierarchical discovery, 3-5managed objects not found, 3-5no objects found, 4-2serial ping, 3-6

discover, 3-4discovery, 4-2duNONE

error, A-15

EEFDs, 4-2, 6-2EM

how to start, 2-3em_cmipconfig

error, A-11, A-12em_dmuxd

error, A-2em_log2rdb, 2-4em_login

error messages, A-9em_panel.cf, 3-3em_services, 2-4environment variables

$EM_HOME, 1-2error class, 5-1error messages, A-1 to A-15

access, A-13access control, A-8, A-10access error, A-12Access Manager, A-8address compare failed, A-2Alarm Manager, A-2, A-3, A-5, A-7,

A-8, A-10, A-11, A-12

album, A-2, A-7Application Launcher, A-2, A-7, A-8bad display value, A-7callback, A-8can’t alloc, A-3can’t allocate label color, A-13can’t connect, A-3, A-4can’t find oid, A-4can’t fork, A-11can’t locate template, A-4can’t open config, A-7can’t open display, A-4, A-14can’t open file, A-9can’t register, 2-3, A-5can’t translate, A-8cannot create glyph, A-2cannot delete condition, A-5cannot grab lockfile, A-11cannot read, A-2cannot retrieve topology, A-3cannot write, A-3client not authorized, A-14CMIS, A-8color, A-13connection refused, A-14could not connect, A-5, A-15could not create icon, A-2could not display alarms, A-5couldn’t boot topology, A-5couldn’t get superior, A-6couldn’t open file, A-7couldn’t start cmd, A-7couldn’t start command, A-7Data Viewer, A-6, A-12DEBUG caution, A-6default object glyph, A-13default status, A-6Discover, A-3, A-4, A-6, A-8, A-9,

A-10, A-12duNONE, A-15em_cmipconfig, A-11, A-12em_login, A-9error executing, A-8error importing file, A-8fork, A-6gdmo, A-9

Index-3

glyph, A-13Grapher, A-7, A-11grapher rpc client, A-7icon, A-13Image constructed without

duNONE, A-15invalid CMIS filter, A-8invalid netmask, A-8invalid network name/number, A-8invalid network number, A-8invalid password, A-9invalid proxy, A-9libpmi, A-9Log Manager, A-10, A-13LoginClient, A-9MIS, A-3, A-4, A-5, A-10MIS disconnect, A-10missing argument, A-7missing information, A-11Monitor, A-10multiple objects, A-12name, A-12nickname, A-8no selected objects, A-12not authorized, A-10OBED, A-4, A-6, A-7, A-8, A-11oid, A-12opening object, A-8pipe, A-6, A-10platform disconnected, A-10PMI, A-15PMI_SUCCESS, A-15print failed, A-11privileges, A-13remote MIS disconnect, A-11Request Designer, A-3, A-4, A-5RPC, A-7server, A-10SET_DERIVATION, A-11setting up nickname, A-8storing object failed, A-12temp file, A-11topology database, A-12unknown alarm, A-12user does not belong, A-12user does not exit, A-13

user does not have connection, A-13user name length, A-9view properties changed, A-13Viewer, A-2, A-5, A-6, A-7, A-12,

A-13xlib, A-14

errror messagesLoginClient, A-9

events, 4-2

Ffork

error, A-11

GGDMO, 5-4GET, 5-2glyph

error, A-13Grapher

error, A-7, A-11

Hhardware failure, 2-2hardware requirements, 2-1

IImage

error, A-15import

error, A-8include files, 5-2inetd

error, 2-3, A-5installation, 2-1invalid password, A-9

Llabel

error, A-13

Index-4 Solstice Enterprise Manager Troubleshooting Guide

Launcheradding applications, 3-3removing applications, 3-3starting applications, 2-6

libraryerror, A-9

lockfileerror, A-11

Log Manager, 4-1error, A-10, A-13

LoginClienterror messages, A-9

Mmessages

See error messagesMIB

deleting entries from, 6-3MIS

error, A-3, A-4, A-5, A-10MIS Manager, 6-2MIS response, 5-2MIS-to-MIS communication, 6-2Monitor

error, A-10no containers, 3-5

MPAstarting, 6-1

MPA error, 2-2

Nnetmask

error, A-8network configuration, 4-2network name

error, A-8network number

error, A-8nickname

error, A-8notifications, 5-4

OOBED

error, A-4, A-6, A-7, A-8, A-11OCT, 6-1oid

error, A-12Oracle errors, 2-4

Ppassword

error messages, A-9path

error, A-9pipe

error, A-10platform

error, A-10PMI, 5-2

error messages, A-15PMI errors, 5-1PMI_SUCCESS, A-15port number

error, A-2Port number mismatch, 2-4print

error, A-11privileges

error messages, A-13properties

startup, 2-7proxy

error, A-9

Rremote

error, A-11remote discovery, 3-6remote MIS, 3-7, 6-2request

round-trip, 5-3synchronous, confirmed, 5-3

Index-5

Request Designer, 4-2error, A-3, A-4, A-5

Rogue Wave classes, 5-2round-trip request, 5-3RPC

error, A-7rw errors, 5-2

Sserver

error, A-10setuid problem, 3-4SNMP

deleting MIB entries, 6-3SNMP daemon, 2-4software requriements, 2-1SQL errors, 2-4starting discover, 3-4startup

error, 2-3, A-5startup problems, 2-5

TTools menu, 3-4topology

error, A-5topology database

error, A-12

Uuser

error messages, A-12, A-13user name length, A-9

VViewer, 4-1, 4-2

error, A-2, A-5, A-6, A-7, A-12, A-13viewerapi_send_request(), 5-3viewing remote information, 3-7

Wwaiting, 3-3

Xxlib

error, A-14

Copyright 1996 Sun Microsystems Inc., 2550 Garcia Avenue, Mountain View, Californie 94043-1100, U.S.A. Tous droitsréservés.

Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie,la distribution, et la décompilation. Aucune partie de ce produit ou de sa documentation associée ne peut être reproduite sousaucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’ily en a.

Des parties de ce produit pourront être dérivées du système UNIX® licencié par Novell, Inc. et du système Berkeley 4.3 BSDlicencié par l’Université de Californie. UNIX est une marque enregistrée aux Etats-Unis et dans d’autres pays et licenciéeexclusivement par X/Open Company Ltd. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux policesde caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.

Sun, Sun Microsystems, le logo Sun, SunSoft, Solstice, Solstice Enterprise Manager, Site/SunNet/Domain Manager, SunNetManager, SunOS, OpenWindows, DeskSet, ONC, SNM, and NFS sont des marques déposées ou enregistrées de SunMicrosystems, Inc. aux Etats-Unis et dans d’autres pays. Toutes les marques SPARC, utilisées sous licence, sont des marquesdéposées ou enregistrées de SPARC International, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marquesSPARC sont basés sur une architecture développée par Sun Microsystems, Inc.

Les interfaces d’utilisation graphique OPEN LOOK® et Sun™ ont été développées par Sun Microsystems, Inc. pour sesutilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept desinterfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique. Sun détient une licence non exclusive deXerox sur l’interface d’utilisation graphique Xerox, cette licence couvrant aussi les licenciés de Sun qui mettent en placel’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun.

Le système X Window est un produit de X Consortium, Inc.

CETTE PUBLICATION EST FOURNIE “EN L’ETAT” SANS GARANTIE D’AUCUNE SORTE, NI EXPRESSE NI IMPLICITE,Y COMPRIS, ET SANS QUE CETTE LISTE NE SOIT LIMITATIVE, DES GARANTIES CONCERNANT LA VALEURMARCHANDE, L’APTITUDE DES PRODUITS A RÉPONDRE A UNE UTILISATION PARTICULIERE, OU LE FAIT QU’ILSNE SOIENT PAS CONTREFAISANTS DE PRODUITS DE TIERS.

solstice enterprise manager troubleshooting guide · 1-1 introduction to troubleshooting 1 1.1...

Documents