The "fjsnap" command is a system information tool of the Solaris, and it comes with the FJSVsnap Expanded Support Function Package. This tool enables you to collect information for troubleshooting if a failure occurs in the PRIMECLUSTER system.
The procedure for executing the fjsnap command is described below.
Log in with system administrator authority.
Execute the "fjsnap" command.
/opt/FJSVsnap/bin/fjsnap -h output
or
/opt/FJSVsnap/bin/fjsnap -a output
If -a is specified, the amount of data becomes large because all detailed information is collected. If -h is specified, only cluster control information is collected.
Specify a special file name or an output file name (ex: /dev/rmt/0) to output information. The specified name is the file to which collected information is output when the "fjsnap" command is executed.
When executing the fjsnap command while some nodes which constitute a cluster has been stopped, the following message may be output to the switchlog and the /var/adm/messages file. However, no corrective action is required.
(BM, 8) Failed sending message <message> to object <object> on host <host>.
(WRP, 11) Message send failed, queue id <queueid>, process <process>, <name>, to host <node>.
See
For details on the "fjsnap" command, see the "README" file, which is the README file included in the "FJSVsnap" package.
Information
Execution timings for the fjsnap command
For problems that occur during operation, for example, if an error message is output, execute the "fjsnap" command immediately after the problem occurs.
If the "fjsnap" command cannot be executed because the system hangs, collect a system dump. Then start the system in single user mode, and execute the "fjsnap" command.
To collect the system dump, input the abort key sequence (for example, Break signal) to forcibly stop the node to OBP mode, and then execute "sync." For detailed instructions on forcibly stopping the node to OBP mode, see the "System Administration Guide" of the Solaris.
After an error occurs, if a node restarts automatically (the node could not be started in single-user mode) or if the node is mistakenly started in multi-user mode, execute the "fjsnap" command.
If investigation information cannot be collected because the "fjsnap" command results in an error or the "fjsnap" command does not return, then collect a system dump.
