The dump files are created either along with the css.snap script, which automatically invokes the associated utility commands, or manually at the user's request. The css.snap script is issued by the user or by the switch support code (device driver, fault service daemon, HAL) whenever a serious error occurs. css.snap gathers dump and trace files into a snapshot compressed package. For more information, see Information to collect before contacting the IBM Support Center.
The AIX commands errpt and errpt -a are redirected into the file errpt.out on the port level, by the css.snap script. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is gathered with other dump and trace files into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
The command:
/usr/lpp/ssp/css/cadd_dump [-0 | -1] -r
dumps the adapter device driver css0 or css1 message buffer to stdout.
When this command is run automatically from the css.snap script, the information is redirected into the file cadd_dump.out on the port level. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
The command dumps status and error information for events such as ioctl calls to a specific port on a specific adapter.
The command:
/usr/lpp/ssp/css/ifcl_dump -a -l -f
dumps the adapter device driver IP message buffer of css0 to stdout.
When this command is run automatically from the css.snap script, the information is redirected into the file ifcl_dump.out on the adapter level. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
The file contains records of errors which occurred in the components running on the node which experienced the error. These components are notified when switch-related error log entries are made, and report the summary data to Event Management for transmission to the control workstation. This file is on the adapter level of each node. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
This file contains error information for the css.summlog daemon, which gathers summary log information and writes it to the summary log file. For information on the summary log file, see Summary log for SP Switch, SP Switch2, and switch adapter errors. summlog.out is a text file on the node level. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
The command:
/usr/lpp/ssp/css/col_dump [-0 | -1] -r
dumps the microcode trace buffer of css0 or css1 to stdout.
When the command is run from the css.snap script, the output is redirected to the col_dump.out file on the adapter level. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
The command dumps status and error information for events such as user-space system calls to the Hardware Abstraction Layer (HAL).
The command dumps adapter memory and state, and may be destructive, meaning that the adapter cannot be in use while issuing this command. Furthermore, after running the command the adapter should be restarted. Restarting the adapter is done by running the rc.switch script on the affected node:
/usr/lpp/ssp/css/rc.switch -l [css0 | css1]
The file contains trace information of the actions of the cssadm2 daemon. This file contains entries for each event received and handled, as well as how the events were handled and the results. This file is on the node level. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
The file contains any unexpected eror messages received by the cssadm2 daemon, while performing commands external to the daemon. This file is on the node level. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
The file contains any unexpected informational messages received by the cssadm2 daemon while performing commands external to the daemon. In general, this file should remain empty. This file is on the node level. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
The command:
/usr/lpp/ssp/css/read_regs
dumps the SP Switch2 adapter's Trail Blazer Interface Chip (TBIC3), MIC, and NBA registers.
All information is dumped to stdout. When this command is run automatically from the css.snap script, the information is redirected into the file regs.out on the adapter level. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
You can check the TBIC_STATUS register from this information.
The file router.log is in the adapter level directory on each node. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is used to record error and warning messages issued by the route table generator (RTG). It contains the RTG version and date, the date and time that the file was created, the node on which the file was created, information about the system topology and the routing algorithm type, and any messages generated during route generation. This file is created during service route generation on the primary node, and during processor route generation on all nodes.
If the file is found at the start of route generation, it is copied to router.log.old. If the file contains any messages at the end of route generation, the file is copied to router_failed.log1. Up to two failed router logs, router_failed.log1 and router_failed.log2 are maintained at any time.
This file is then gathered into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
The command:
/usr/lpp/ssp/bin/CSS_test
produces a log file CSS_test.log at the node level directory, which is then gathered into the snapshot compressed package. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is present only if the CSS_test command was run on the node.
If your system is running in restricted root access mode, CSS_test must be run from the control workstation. For more information, see Verify software installation, and the CSS_test entry of PSSP: Command and Technical Reference.
The commands:
/bin/odmget -q "attribute=adapter_status" PdAt /bin/odmget -q "attribute=adapter_status" CuAt
dump the SP Switch2 adapter's configuration status as it was saved in the ODM, to stdout.
When this command is run automatically from the css.snap script, the information is redirected into the file odm.out on the adapter level. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. For more information on the snapshot, see Information to collect before contacting the IBM Support Center.
The commands:
prints network and switch current status information to stdout.
When these commands are run automatically from the css.snap script, the information is redirected into the file spdata.out on the port level. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. See Information to collect before contacting the IBM Support Center. The splstdata command is described in PSSP: Command and Technical Reference.
The AIX commands:
print network related data to stdout.
When these commands are run automatically from the css.snap script, the information is redirected into the file netstat.out on the adapter level. For the full path name, see SP Switch2 log and temporary file hierarchy. This file is then gathered into the snapshot compressed package. See Information to collect before contacting the IBM Support Center. The netstat command is described in AIX 5L Version 5.1 Command and Technical Reference.
These files are in the adapter level of each node that runs the adapter diagnostics and the TBIC test within this test (TBIC test within adapter diagnostics). For the full path name, see SP Switch2 log and temporary file hierarchy. The TBIC, which is a chip on the SP Switch2 adapter, is scanned into this file and saved as part of the snapshot by the css.snap script. The scan_save.log is a previous TBIC scan. This TBIC scan procedure is destructive and therefore taken only when the css.snap runs after a permanent failure. No other switch communication is available, and the switch adapter is reset after the scan is taken. See SP Switch2 adapter diagnostics
The DeviceDB.dump file is in the port level directory of each node. For the full path name, see SP Switch2 log and temporary file hierarchy. This file contains the latest dump of the device data base from the fault service daemon. This dump is taken as part of the snapshot by the css.snap script.