Sun Enterprise[TM] 10000: Troubleshooting Netcon Logging and netcon

Asset ID:	1-75-1321262.1
Update Date:	2011-05-25
Keywords:

Solution Type Troubleshooting Sure

Solution 1321262.1 : Sun Enterprise[TM] 10000: Troubleshooting Netcon Logging and netcon_server

Applies to:

Sun Enterprise 10000 Server - Version: Not Applicable to Not Applicable - Release: N/A to N/A
Information in this document applies to any platform.

Purpose

This document provides troubleshooting assistance for both netcon logging and netcon_server on the SSP.

Last Review Date

May 11, 2011

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

What is netcon logging? How do I enable it?

Netcon logging is a console log for E10000 domains. Logging console information is crucial in the event the system in unable to log information via normal methods. Also, there are some messages that are only output to the console (a panic stack trace for example).

SSP 3.1.1 and higher Netcon logging is integrated into SSP 3.1.1 and beyond. To enable logging on for SSP 3.1.1 and higher, edit the /etc/syslog.conf file and uncomment the local1.debug line and restart the SSP.

# Uncomment to enable SSP netcon session logging:
local1.debug           /var/opt/SUNWssp/.ssp_private/machine_server_fifo

The output for each domain's console is stored in $SSPVAR/adm/<domain_name>/netcon.

SSP 3.0 and 3.1 For SSP 3.0 and 3.1, there is a script that can be installed to collect console logs.

Store S99netcon_logger in /etc/rc2.d/S99netcon_logger.
Store netcon_loggerd in /opt/SUNWssp/bin/netcon_loggerd. Ensure execute permissions for user ssp are set.

The output for each domain's console is stored in $SSPVAR/adm/<domain_name>/netcon.log. If the netcon process which is recording the log dies or is killed, netcon_loggerd will restart it, unless an exclusive netcon session is used. To restart recording after an exclusive session has been used, send a kill -HUP to netcon_loggerd.

It is also recommended to configure archiving of the netcon logs.

Store newnetconlog in /opt/SUNWssp/bin/newnetconlog.
Modify the MAX variable to specify the number of archived logs to be maintained.
Add the following line to root's crontab:

            5 4 * * 6 /opt/SUNWssp/bin/newnetconlog >/dev/null 2>&1 # archives netcon.log

netcon_server fails at startup

Symptom:

netcon_server fails at startup with

syslog: VerExec: ERR: VerExecApp.cc, 261: netcon_server error:

Resolution:

Check that the OS version in the domain_config file is correct.

/var/opt/SUNWssp/.ssp_private/domain_config

The domain's OS version can be corrected via the domain_rename command
run on the Main SSP.

domain_rename -d domainname -o 5.#

where 5.# equals the SunOS version - for example, 5.5.1, 5.6, 5.7, 5.8, and so on

Attachments

This solution has no attachment