Print | Rate this content

CSTM WILL NOT RUN ON MPE/ix 6.5

CSTM WILL NOT RUN ON MPE/ix 6.5

DocId:
DFQKBCA00000344
Updated:
10/4/01 11:41:00 AM

PROBLEM

When running CSTM it hangs and never gets to a CSTM prompt.
Other symptoms include CSTM running intermittently or various functions within
CSTM will not operate.

CONFIGURATION

HP3000 MPE/ix 6.5

RESOLUTION

1. PATCH REQUIREMENTS:

The system must be on the current Powerpatch and ODI patch.
As of March 2001 these are Powerpatch 2 and ODILXG0.
ODILXG0 must be installed after the Powerpatch.
The Powerpatch has network fixes needed for CSTM to work correctly.
Without the current patches, the functionality of CSTM will be
undependable.

NOTE: CSTM may still run without the above mentioned patches.
Continue with this document to complete CSTM problem resolution and
install the patches at the earliest time available.

2. STOPPING AND STARTING CSTM DAEMONS:

CSTM relies on a Diagnostic Monitor Daemon (DIAGMOND) that is started at
boot time. When CSTM will not run this daemon may be hung. Also,
DIAGMOND must be stopped before the network is shutdown, else DIAGMOND
will hang. It is recommended to stop and start the daemons as a first
step of troubleshooting. Also, it may be necessary to stop and start the
daemons as changes are made during the troubleshooting process. Other
daemons used are DIAGLOGD and MEMLOGD.

NOTE: Before installing any ODI patch, the daemons must be stopped.

2a. To stop the daemons, log-on as MANAGER.SYS and issue the following
command file:

:STMSHUT.DIAG.SYS

Diagmond has now been shutdown.

If the following error occurs:
"diagmond did not shutdown within 1 minute"
proceed to step 2.b

To start the daemons, make sure the Network is running (see step 3)
and issue command file:

:STMSTART.DIAG.SYS.

Diagmond has been started.

Please wait a few minutes for diagmond to complete initialization.

NOTE: STMSTART is installed with ODILXG0. Use the following process
to start the daemons if ODILXG0 is not installed.

Log-on as MANAGER.SYS. Issue the CSTM command. Error information
will be displayed then CSTM will hang. Issue a Cntrl- Y. More error
information will be displayed then a CSTM prompt will appear.

Type SSU (stmstartup) from the CSTM prompt.
Type EXIT
NOTE: Wait 5-10 minutes to allow CSTM to complete initialization.

2b. The following process is used to "kill" a hung diagmond daemon using
the Posix shell commands. The commands used are grep to see the
process and kill to stop them. Log-on as MANAGER.SYS and type the
following commands.

: XEQ SH.HPBIN.SYS
$ ps -ef | grep diag

0 65588 1 0 Jan 01 1:11 /usr/sbin/stm/uut/bin/sys/diagmond
0 589888 65588 0 Jan 01 0:01 /usr/sbin/stm/uut/bin/sys/diaglogd

$ kill -9 65588
$ ps -ef | grep diag
$
$ exit

This will stop both diagmond and diaglogd daemons. If CSTM still
does not run after stopping and starting the daemons, continue with
step 3.

3. NETWORK CONFIGURATION:

The internal network interface (NI) LOOP must be configured and running.
This is automatically done when an external network interface is
configured. Configuration is done in NMMGR.
To confirm LOOP is running, type:

:NETCONTROL STATUS;NET=LOOP.

Look for the line that states "PROTOCOL STARTED"
To start LOOP, type:

:NETCONTROL START;NET=LOOP.

3a. CSTM must resolve two names to IP addresses. The first is the
LOCALHOST name, the second is the NS name configured on the HP3000.
The LOCALHOST resolves to 127.0.0.1 and the NS name resolves to the
HP3000's IP address.

Name resolution occurs using either the HOSTS.NET.SYS file or
RESLVCNF.NET.SYS file. For customers using a DNS (Domain Name
Server) the RESLVCNF.NET.SYS file is used and should contain the name
search criteria and the IP address(es) of the name server(s).
To see a sample of this file, type PRINT RSLVSAMP.NET.SYS. If there
is no RESLVCNF.NET.SYS file, then the HOSTS.NET.SYS file is used.
This file should contain the LOCALHOST LOOPBACK IP address and the
local HP3000's node name and IP address.
Example:

127.0.0.1 localhost loopback
192.1.1.1 highland highland.scotland.world.com

If unsure about these files or CSTM continues to hang with error
"Waiting to obtain host information from local host", consult with a
network engineer.

3b. Maximum TCP connections in NMMGR should be set to 4096 or greater. If
current configuration is less than 4096 it will not prevent CSTM from
running however, downloading firmware to a FWSCSI card uses 1300+
TCP connections.

How to change the Max Number of TCP connections in NMMGR:

Log-on as MANAGER.SYS.
Type NMMGR.
In NMMGR press F1 "Open Config"
Press F2 "NS"
Press F2 "Unguided Config"
Press F1 "Go to Net Xport"
Press F2 "Go to GPROT"
Press F2 "Go to TCP"
Tab to column "Maximum Number of Connections"
and change the value to 4096.
Press F6 "Save Data".
Exit NMMGR.
Reboot the system with START NORECOVERY to save the changes.

4. OTHER DEPENDANCIES:

Check for the following Shared Library files which are restored from FOS
tape when the system is updated. Issue a LISTFILE command for each file
to verify they exist.

/lib/libm.sl
/usr/dt/lib/libdthelp.sl
/usr/dt/lib/libnew.sl
/usr/lib/libIO.sl
/usr/lib/libmcats.sl
/usr/lib/libmcurs.sl
/usr/lib/libsocket.sl
/lib/libsvipc.sl
/lib/libc.sl
XL.PUB.SYS


Issue command PRINT SERVICES.NET.SYS and verify the following line is
included in the file:

Diagmond 1508/tcp # Support Tools Manager (STM/IX)


KEYWORDS

<category1>HARDWARE, <category2>Servers, <category3>K-Class

Original KMine CA DFQKBCA00000344

Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!
Document title: CSTM WILL NOT RUN ON MPE/ix 6.5
Document ID: emr_na-c00959003-2
How helpful was this document?
How can we improve this document?
Note: Only English language comments can be accepted at this time.
Please wait while we process your request.