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, kernel extension) whenever a serious error occurs. css.snap gathers dump and trace files into a snapshot compressed package. For more information, see css.snap package.
The AIX commands errpt and errpt -a are redirected into the dump file errpt.out, by the css.snap script. The file is gathered with the 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.
/usr/lpp/ssp/css/css_dump -rdumps the adapter device driver trace buffer to stdout.
When this command is run automatically from the css.snap script, the information is redirected into the file css_dump.out. 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 the device css0 and adapter error interrupts.
/usr/lpp/ssp/css/tbXdumpX is automatically replaced in the css.snap script with 3, 3mx, or 3pci according to the adapter type: TB3, TB3MX, or TB3PCI respectively.
When this command is run automatically from the css.snap script, the information is redirected into the file css_dump.out, which 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 adapter memory and state and is 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
The command:
/usr/lpp/ssp/css/fs_dump -r
dumps the fault-service kernel extension trace buffer to stdout.
When the command is run from the css.snap script, the output is redirected to the fs_dump.out file. 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 fault service kernel extension.
The file cssadm.debug is in the /var/adm/SPlogs/css directory. The file contains trace information of the actions of the cssadm 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 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 cssadm.stderr is in the /var/adm/SPlogs/css directory. The file contains any unexpected error messages received by the cssadm daemon, while performing commands external to the daemon. 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 cssadm.stdout is in the /var/adm/SPlogs/css directory. The file contains any unexpected informational messages received by the cssadm daemon while performing commands external to the daemon. In general, this file should remain empty. 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 switch adapter's Programmable Option Selection (POS) registers and TBIC registers in addition to the adapter clock status.
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. 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 read_regs command reads all registers on the local SP switch adapter and adds information about the kernel extension and the clock source that are used by the adapter. The exact output differs for the TB3, TB3MX, or TB3PCI switch adapters.
You can check the TBIC_STATUS register from this information. Another way to check this register is by issuing the command:
/usr/lpp/ssp/css/diags/read_tbic -s
which is described in the relevant switch diagnostic section.
The file router.log is in the /var/adm/SPlogs/css directory. 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 /var/adm/SPlogs/CSS_test.log, which is then gathered into the snapshot compressed package. This file is present only if the CSS_test command was run on the node.
When running in Restricted Root Access (RRA) 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.
These commands dump the switch kernel extension internal information when dealing with IP.
/usr/lpp/ssp/css/vdidlX -v -d /usr/lpp/ssp/css/vdidlX -v -i /usr/lpp/ssp/css/vdidlX -v -sX is automatically replaced in the css.snap script with 3, 3mx, or 3pci, according to the adapter type: TB3, TB3MX, or TB3PCI respectively,
The exact output differs for the TB3, TB3MX, or TB3PCI switch adapters. All information is dumped to stdout. When this command is run automatically from the css.snap script, the information is redirected into the file vdidl.out. 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:
print network and switch current status information to stdout. The css.snap script dumps the command output to the file spdata.out and packages the file together with other snapshot files. 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. The css.snap script dumps the command output to the file netstat.out and packages the file together with the other snapshot files. 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 /adm/SPlogs/css directory of each node that runs the adapter diagnostics and the TBIC test within this test (TBIC test within adapter diagnostics). The TBIC, which is a chip on the switch adapter, is scanned into this file and saved as part of the snapshot, when running 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 Switch adapter diagnostics.