HP-UX SNAplus2 Diagnostics Guide

Resolving Common Problems
Basic Checks
Chapter 234
The SNA daemons may fail to start if there is an error in the
configuration, such as a reference to a missing configuration record.
Other errors can occur if SNAplus2 has not been installed correctly. For
example:
• There may be no domain configuration file (sna_domn.cfg)
• There may be no kernel SNA drivers present because the kernel has
not been relinked and the system restarted since installing the
software
• SNAplus2 was not installed successfully
Refer to the HP-UX SNAplus2 Installation Guide for more information.
Check That the Local SNA Node Is Active
The local SNA node must be activated before SNAplus2 can become
fully-functional. To check whether the node is active, use the snapadmin
status_node command. Refer to the HP-UX SNAplus2 Administration
Guide for more information about this command.
This command can report the following:
• The node is active.
• The node is inactive.
The Local SNA Node Is Active
If the snapadmin status_node command reports that the node is active
then the node has been activated successfully.
The Local SNA Node Is Inactive
If the snapadmin status_node command reports that the node is
inactive then you must activate the node using either the Motif
administration program or the command-line administration program.
Refer to HP-UX SNAplus2 Administration Guide for information about
starting the node.
If the node fails to start then check the error log file. The error log file
might indicate that there is an error in the configuration file. In this case
use the Motif administration program or the command-line
administration program to correct the error.
For more information about configuring the node, refer to HP-UX