Sun Microsystems SunLink SNA 9.1 PU2.1, Configuration Manual

Page: 213 / 298

Troubleshooting 12-35
12
12.3.5 The Sun PU2.1 SNA Server Configuration Does Not Start
Automatically
If the SunGMAN process is installed correctly and starts, but does not initialize
the configured systems and servers at start time, the manager network may
have 50% or fewer of the configured managers active. SunGMAN will wait
until at least 50% are active before activating the configuration. For more
information, refer to Section 1.10, “Manager Network,” on page 1-19.
If the systems or PU2.1 servers are listed in the resource window of the
SunGMI but are not active, they may be configured with an initial status of
Inactive. Change the initial status to Active and save the configuration. This
will restart the system/server and bring it to an operational state.
12.3.6 A System Fails
If a system in the SunGMI is displayed in red and is marked as "Failed", check
the event messages logged in the Events window of the SunGMI. The problem
may be one of the following:
•
The TCP host on which the system is running is unreachable.
•
The suncpd process on the remote system is not running.
•
The sunSMAN process cannot locate the TCP service names it needs.
•
The sunSMAN process is already running, but it was not started by the
SunGMAN process.
12.3.7 A PU2.1 Server Fails
The problem may be one of the following:
•
The TCP host that the Sun PU2.1 SNA Server is running on is unreachable.
•
The suncpd process on the remote system is not running.
•
A PU2.1 server process (sunPU21) is already running, but either it was not
started by the SunGMAN process or it shares the same sunOP service name.
•
The server configuration file is not valid. Check the errors logged in the
Events window of the SunGMI.