HP-UX SNAplus2 Diagnostics Guide

Using Logging and Tracing
Controlling Logging Using Command-Line Administration Program
Chapter 3 71
----------------------- 13:55:16 EDT 15 May 1997 -----------------------
CFG_DAEM Message 4097 - 132, Subcode: 1 - 1
Log category: PROBLEM Cause Type: External
System: sna18
Process ID: 17908 (snapcfgdae)
The initially active port could not be started when starting the node.
Port name = SDLCP0
Cause: The config daemon could not start the port while loading the node’s
configuration. The node will be started, but the port will not be started.
Action: Check for other logs which indicate why the port failed to start.
Check that the DLC has been started.
Verbose logging messages contain the following information:
Timestamp
The time and date the message was generated. If you
are using central logging, the timestamp for each
message is taken from the system clock on the
computer where the message was generated. If the
system clocks on different computers are not
synchronized (because of clock inaccuracies or time
zone differences), the messages in the central log file
may appear out of sequence because they are added to
the file in order of arrival at the central logger and not
in order of their timestamps.
If your system includes Windows clients and you are
using central logging, ensure that the TZ environment
variable on the Windows client is set to indicate the
correct time zone. If this variable is not set, timestamps
for logs from the Windows client may be incorrect.
Refer to your Windows documentation for more
information about the setting of TZ.
Component
The SNAplus2 component (such as local node, link
driver, or APPC library) that logged the message.
Message number
An identifier for the message. This identifier consists of
two numbers.