Chapter 4


System Configuration Control

4.1 DEVICE STATUS

System configuration control manages the device status for the devices (central subsystem units and peripheral devices).

The central subsystem units of SX-4 include CPU(CPxx), MMU(MMxx), XMU(MSXx), IOP(PCIxx), HIPPI channel(CHxx), CHE(PCIxx), SCSI channel / FDDI channel (PCxxx) and AOC(AOxx).

The central subsystem units of SX-5 include CPU(CPxx), MMU(MMxx), IOP(PCIxxx), HIPPI channel / FCP channel / SCSI channel / FDDI channel / Ethernet channel (PCxxx), and AOC(AOxx).

The peripheral devices include devices under IOX (Input/Output Multiplexer), HIPPI devices (e.g., RAID) and directly-connected SCSI/FCP devices. For details on these devices, refer to the System Administrator's Guide.

There are three types of device status managed by the system configuration control: normal connection status (online), abnormal connection status (unavailable), and off status (offline). The three device status types are shown in Figure 4-1.

Figure 4-1  Device Status

Figure 4-1 Device Status

Legend

  1. Permanent failure of device or command entry
  2. Command entry
  3. Command entry
  4. Command entry
  5. Command entry
  6. Command entry

Home


4.2 DISCONNECTING A DEVICE AS A RESULT OF FAILURE

A device may be disconnected as a result of a failure. This occurs when the central subsystem error handling or the driver of a peripheral device detects a failure in hardware. In this case, the device enters the abnormal connection status (unavailable).

In this status, input/output by each peripheral device driver cannot be performed.

4.3 DEVICE CONNECTION AND DISCONNECTION BY COMMAND

A command can be used to connect and disconnect devices other than the CPU and MMU.

By using a command, a device can be placed in the normal connection status (online), abnormal connection status (unavailable), or off status (offline).

Use the devconf(1M) command for central subsystem units. For peripheral devices, use the ioconf(1M) command. For details on the commands, refer to the System Administrator's Reference Manual.

4.4 HARDWARE FAILURE LOG

A failure log is recorded when a hardware failure occurs.

There are two types of failure logs: the SVP log recorded by hardware (firmware) and the error log recorded by software. This section, however, does not explain the SVP log. The error log recorded by software is stored in the error log file (/usr/adm/errfile).

Hardware failures in the devices under the Input/Output Multiplexer (IOX) are recorded by the IOX.

Table 4-1 lists the timing and priority of error log collection.

Table 4-1 Error Log Collection Timing

Error Log Collection TimingPriority
Start log1
IOP/HIPPI failure log3
Device failure log
Software retry failed after I/O abnormal termination
I/O termination timeout detected
4
Connection by system configuration control failed
Software retry succeeded after I/O abnormal termination
Report of successful hardware retry
5
Debug information (trace information collected by each device driver)6

Home


4.4.1 Editing Error Log

A banner (4-digit hexadecimal number) is assigned to each error log information to identify the error log content. Table 4-2 lists banners and corresponding devices (information).

Table 4-2 Error Log Banners

BannerDevice (Information)
1xxx
1001
1010
CPU central subsystem unit and XMU
XMU
IXS
4xxx
4010
4011
4012
4020
4060
4061
4062
4063
4070
4071
4072
4090
Log information from device driver
Disk array (AD)
IPI
HIPPI tape unit (HMT)
Third-party driver
SCSI channel
FDDI channel
FCP channel
Ethernet channel
Directly-connected SCSI disk unit
Directly-connected SCSI tape unit
Directly-connected SCSI media changer unit
HIPPI
7000 Debug information
8xxx
8000
System configuration control
System configuration control
0001 Start log

Home


4.4.2 Error Log Output Information

Output images and information for the error logs output by the errpt command are listed next. Refer to the SUPER-UX System Administrator's Reference Manual for details.

Home


Home


Home


Home


Home


Home


Home


See the SUPER-UX Programmer's Reference Manual for more information on the error log edit commands.

Home

Contents Previous Chapter Next Chapter Index