ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzatl_5.4.0.1/rzatltrouble.htm

135 lines
8.8 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2005" />
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="task" />
<meta name="DC.Title" content="Troubleshoot the CIM server" />
<meta name="abstract" content="Use this information to troubleshoot the CIM server." />
<meta name="description" content="Use this information to troubleshoot the CIM server." />
<meta name="DC.Relation" scheme="URI" content="rzatlkickoff.htm" />
<meta name="DC.Relation" scheme="URI" content="http://www.openssl.org/docs" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzatltrouble" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Troubleshoot the CIM server</title>
</head>
<body id="rzatltrouble"><a name="rzatltrouble"><!-- --></a>
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Troubleshoot the CIM server</h1>
<div><p>Use this information to troubleshoot the CIM server.</p>
<div class="section">Use this information if the CIM server does not start or if the CIM
server starts, but does not run as expected.</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzatlkickoff.htm" title="The Common Information Model (CIM) is a standard developed by a consortium of major hardware and software vendors (including IBM) called the Distributed Management Task Force (DMTF) as part of the Web Based Enterprise Management (WBEM) initiative.">Common Information Model</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="http://www.openssl.org/docs" target="_blank">OpenSSL documentation</a></div>
</div>
</div><div class="nested1" xml:lang="en-us" id="thecimserverdoesnotstart"><a name="thecimserverdoesnotstart"><!-- --></a><h2 class="topictitle2">The CIM server does not start</h2>
<div><div class="section">Do the following steps if the CIM server does not start. <div class="note"><span class="notetitle">Note:</span> <img src="./delta.gif" alt="Start of change" />If
this is the first time the CIMOM server is being started after install of
Pegasus V2.5, it takes a while for the server to start. During that time,
the repository is being upgraded and the user data from the previous repository
is being migrated.<img src="./deltaend.gif" alt="End of change" /></div>
<dl><dt class="dlterm">Ensure that the CIM server is configured correctly.</dt>
<dd>See <a href="rzatlconfigparms.htm">Set the required configuration parameters</a> to configure your CIM server.</dd>
<dt class="dlterm">Verify whether you need to change your Kerberos configuration or change
the CIM server to use basic authentication.</dt>
<dd>If you receive the following message, there is an error with your authentication.
You need to fix your authentication or use another form of authentication,
such as basic authentication.<pre>CPDDF82: (Message appears in CIM server, QYCMCIMOM, joblog)
PGS02000: The CIM server authentication handler for Kerberos
failed to initialize properly. The CIM server is not started.</pre>
<div class="note"><span class="notetitle">Note:</span> <img src="./delta.gif" alt="Start of change" />You should not use basic authentication unless
you are using HTTPS or unless you have a highly secure environment, where
passing clear text passwords is not an issue. To use the cimconfig command
to change your CIM configuration settings, QSHELL (Option 30) must be installed.<img src="./deltaend.gif" alt="End of change" /></div>
</dd>
<dd class="ddexpand">To change the authorization to basic, type the following command at a
command line.<pre>qsh
cd / QIBM/UserData/OS400/CIM
cimconfig -shttpAuthType=Basic -p</pre>
</dd>
<dt class="dlterm"><img src="./delta.gif" alt="Start of change" />Ensure that the correct options are installed on your system.<img src="./deltaend.gif" alt="End of change" /></dt>
<dd>If you receive the CPDDF80 with reason code 07 indicating the required
option 39 is not installed, install Option 39 (ICU). </dd>
<dd class="ddexpand">You might need to install LPO 5733-SC1 (OpenSSL) if the server starts
with SSL disabled and the server job log contains a message saying that OpenSSL
is required. In this case the server is configured to use SSL, but OpenSSL
is not installed. You can install OpenSSL or configure the server to not use
SSL. The default configuration of the server is to enable SSL on both the
wbem-https and wbem-exp-https ports.<p>In addition, if LPO 5733-SC1 had an
installation error, you will also receive the message in the server job log,
and the server will start with SSL disabled. You can use the CHKPRDOPT command
to check the error status of the LPO in this case.</p>
<p>OpenSSL requires
that PASE (option 33 of the Base OS) is installed. After the server starts,
if PASE is not installed, and the server has SSL enabled, then OpenSSL sends
a CPFB9C1 escape message to the server job log, and the server ends.</p>
</dd>
</dl>
</div>
</div>
</div>
<div class="nested1" xml:lang="en-us" id="thecimserverrunsdoesnotbehaveasexpected"><a name="thecimserverrunsdoesnotbehaveasexpected"><!-- --></a><h2 class="topictitle2">The CIM server does not behave as expected</h2>
<div><div class="section">If you are having trouble with the CIM server, see the following
instructions:<dl><dt class="dlterm">Check to see if the CIM server is running by typing <span class="cmdname">WRKJOB QYCMCIMOM</span> at
a command line.</dt>
<dd>If there is not an active job, start the CIM server by typing <span class="cmdname">STRTCPSVR
*CIMOM</span> at a command line.</dd>
<dt class="dlterm">Check to see if the CIMOM repository is corrupted.</dt>
<dd>Verify whether the repository directory and configuration files exist
in the <span class="filepath">QIBM/UserData/OS400/CIM</span> directory of the integrated
file system. If any of these files are missing, restore all the repository
directories and files from your backup. You must use a backup of those files
from the Pegasus V2.5 backup, not from a V5R3 system that did not have the
Pegasus V2.5 PTFs installed.</dd>
<dd class="ddexpand">If a backup to restore from does not exist, follow the instructions in <a href="rzatlrestore.htm">Restore corrupted files</a>.</dd>
<dt class="dlterm">Verify if you are attempting to process a request when the provider is
not registered or enabled.</dt>
<dd>To verify if you are attempting to process a request when the provider
is not registered or enabled, do the following steps:<ol><li>Type <span class="parmname">cimprovider -l -s</span> to list the name and status
of the registered provider modules.</li>
<li>Type <span class="parmname">cimprovider -l-m</span> <var class="varname">module name</var> to
see the individual providers in that module.</li>
</ol>
</dd>
<dt class="dlterm">Check the job log file.</dt>
<dd>To check the job log file, do the following steps: <ol><li>Type <span class="cmdname">WRKACTJOB</span> at a command line.</li>
<li>Look in the QSYSWRK subsystem to find the QYCMCIMOM job.</li>
<li>Select 5 (work with), then 10 (Display job log, if active, on job queue,
or pending).</li>
<li>If the QYCMCIMOM job is not running, type <span class="cmdname">WRKJOB QYCMCIMOM</span>.</li>
<li>Select the most recent job by typing 1 (Select) next to it.</li>
<li>If status is OUTQ, type 4 (Work with spooled files), and then type 5 (Display)
next to the QPJOBLOG file.</li>
</ol>
</dd>
<dt class="dlterm">Check whether CIM client request failures result in SSL certificate-related
messages.</dt>
<dd>Make sure the remote CIM server certificate is added to the trust store
file on the client system. Make sure that the clients certificate and private
key are being used by the client application and that the client certificate
is trusted by the server.</dd>
</dl>
</div>
</div>
</div>
<img src="./deltaend.gif" alt="End of change" /></body>
</html>