Table 3-2. Setup output files (continued)

File

Location

Description

Directory

 

 

 

 

css.snap.log

All nodes

Log files created by the switch

/var/adm/SPlogs/css

 

 

support code

 

 

 

 

 

Table 3-3. Tuning output files

 

 

 

 

 

 

 

File

Location

Description

Directory

 

 

 

 

daemon.stdout

All nodes

Keeps a detailed account of the

/var/adm/SPlogs/css

 

 

tuning process initiated by the Estart

 

 

 

command. It includes data from

 

 

 

every tuning operation since the

 

 

 

current daemon on the primary node

 

 

 

was initiated.

 

 

 

 

 

topology.data

Primary

A record of the primary node, how

/var/adm/SPlogs/css

 

 

many nodes were initialized, and the

 

 

 

links between them.

 

 

 

 

 

daemon.stderr

All nodes

A record of which nodes were not

/var/adm/SPlogs/css

 

 

initialized.

 

 

 

 

 

out.top

Primary

Reports errors from the last tuning

/var/adm/SPlogs/css0/p0

 

 

procedure. It begins as a copy of the

 

 

 

topology file and errors are

 

 

 

indicated to the right of each entry.

 

 

 

 

 

out.top.old

Primary

A copy of out.top from the previous

/var/adm/SPlogs/css0/p0

 

 

run.

 

 

 

 

 

router.log

Primary

The router log file generated by the

/var/adm/SPlogs/css0/p0

 

 

route table generator after

 

 

 

initialization.

 

 

 

 

 

router.log.old

Primary

A copy of router.log from a previous

/var/adm/SPlogs/css0/p0

 

 

run.

 

 

 

 

 

Using the css.snap script

The css.snap script is located in the /usr/lpp/ssp/css directory. When the script runs, it collects log, trace, and dump files created by SP Switch2 support code (device driver, worm, fault-service daemon, and diagnostics) into a single compressed package.

Attention: css.snap uses a number of undocumented utilities to collect information. Some of these can be destructive when used on a running system. After using css.snap to collect diagnostic information, it's best to run /usr/lpp/ssp/css/rc.switch in order to reset and reload the switch adapter and eliminate residual effects of these utilities. This procedure should be used only under the direction of the IBM Support Center.

When working with a two-plane SP Switch2 system, add the adapter name to the command, as follows: dsh -a /usr/lpp/ssp/css/rc.switch-a<adapter_name>

The css.snap script is called whenever a serious error is detected by the switch support code. You can direct the system to create a snapshot by loging into the desired node and manually issuing the command: /usr/lpp/ssp/css/css.snap with any of the optional flags: [-c -n] [-s] [-a cssX (where X=0 or 1)] [-p p0] where:

v-cFlushes the adapter cache and prints the result. This is the default.

Chapter 3. Service procedures 3-3

Page 61
Image 61
IBM RS/6000 SP manual Using the css.snap script

RS/6000 SP specifications

The IBM RS/6000 SP (Scalable Power) is a high-performance computing system that was developed in the early 1990s and has since become a significant player in the realm of supercomputing and enterprise solutions. Designed primarily for scientific, engineering, and complex data analysis tasks, the RS/6000 SP provides powerful processing capabilities, enhanced scalability, and features to support demanding applications.

One of the key characteristics of the RS/6000 SP is its modular architecture, which allows for the addition of multiple nodes. Each node is based on IBM's Power architecture, leveraging the RISC (Reduced Instruction Set Computing) design to achieve high throughput and efficiency. The system can support configurations ranging from a few nodes to hundreds, enabling organizations to scale their computational power as needed based on workload requirements.

The RS/6000 SP employs advanced interconnect technologies, most notably the SP Switch, which ensures high-speed communication between nodes. This interconnect allows for seamless data transfer, ensuring that the system can handle large datasets and complex computations without bottlenecks. The SP's ability to deliver concurrent processing capabilities makes it ideal for parallel computing tasks, including simulations, modeling, and large-scale computations.

In terms of software, the RS/6000 SP was equipped with AIX, IBM's version of the UNIX operating system, which provides a stable and secure environment for enterprise applications. Furthermore, the system supports a vast array of programming languages and tools, including Fortran, C, and C++, along with libraries and frameworks designed for high-performance computing. This compatibility allows developers to optimize their applications to fully utilize the underlying hardware.

Another notable feature of the RS/6000 SP is its extensive support for various workloads, including database management, multi-user applications, and graphical processing. The system was equipped with high-performance graphics capabilities, making it suitable for tasks that require intensive visualization, such as computer-aided design (CAD) and scientific visualization.

Overall, the IBM RS/6000 SP has solidified its role in the high-performance computing landscape, combining advanced technologies, robust scalability, and flexibility to meet the unique demands of research and enterprise environments. Its legacy continues to influence modern computing architectures, embodying IBM’s commitment to innovation and performance in the pursuit of complex problem-solving capabilities.