This chapter describes the following topics:
The following log files provide useful information on SGIconsole operations:
| SGIconsole Log | Description |
| /var/log/vacm.log | Resides on the SGIconsole system and contains a log of VACM activity. |
| /var/adm/SYSLOG | Resides on every IRIX server and contains a log of messages written to the system console. |
| /var/log/messages | Resides on every SGI Altix 3000 Linux server and contains a log of messages written to the system console. |
| /var/lib/sysadm/salog | The Console Manager GUI log which contains all backend command and parameters executed by the console manager GUI. |
| /var/www/html/SGIconsole_logs | SGIconsole logs directory |
| /proc/dgrp/config and /proc/dgrp/nodeinfo | Use these files to determine the status of your EL-16 device. |
[root@linux1 /tmp]# cat els00.log
09/19/01 09:03:16: EtherLite daemon running
09/19/01 09:03:16: Vendor ID: DigiIntl, Firmware Version: V7.6
Model Name: EL-16, IP Address: 192.12.1.20
09/19/01 09:03:16: Unit Online |
If the SGIconsole machine is rebooted or the SGI console Reset node task is run, console logging is disabled on all nodes. To start logging whenever /etc/init.d/sgiconsole is run, update the contents of the /etc/sgiconsole.conf file.
The /etc/sgiconsole.conf configuration file specifies startup-time actions that are performed when SGIconsole is started. Currentl, only the log action is supported.
You can start logging on either the system or controller console (or both, if the node supports it, particularly the MSC- and L2-type nodes) by adding entries to the /etc/sgiconsole.conf file similar to the following:
# This file contains configuration directives for SGIconsole, # to be applied on startup. # # Currently recognised directives: # nogroupdbfix - do not try to fix the groups database: nogroupdbfix # # log - enable logging on a specified node: ##log SYSTEM <nodename> ##log CONTROLLER <nodename> # log SYSTEM blue log SYSTEM green log CONTROLLER blue |
When the SGIconsole software is restarted, this configuration file allows the nodes blue and green to have their console logging restarted, automatically (as a new console log session).
 | Note: Console logs are activated as if the Switch State of Console Logging task has been applied to each node in turn. Thus, for nodes with controllers that only allow one console type to be logged at a time (MMSC and L1 controllers), the console type actually logged will be the the type of the last entry specified for the node in the configuration file. |
Each Console Manager task has the following flow of execution when a GUI task is executed, such as connecting to a node or getting a console port:
GUI task ---> privcmd CLI ---> VACM (nexxus) ---> VACM plugins ---> EL-16 driver (if present)
Key:
privcmd = privileged command
CLI = command line interface
VACM = cluster manager software
nexxus = Console Manager backend software (Console Manager daemon)
VACM plugins = SGI software plugins to support various SGI servers.