|C H A P T E R 3|
Identifying and Configuring Components
This chapter introduces the tools that let you administer the server and explains how the diagnostic tools fit together.
Topics in this chapter include:
The Sun Fire X4500 server and its accompanying software contain tools and features that help you:
For detailed instructions on diagnosing the server, refer to the Sun Fire X4500 Server Diagnostics Guide (819-4363) and the Sun Fire X4500 Server Service Manual (819-4359).
Some Solaris commands display data that you can use when assessing the condition of a Sun Fire X4500 server. This section discusses superuser commands that assist in troubleshooting problems with the Sun Fire X4500 server. These commands include:
This section describes the information these commands give you. For additional information about these commands, see the command man pages.
The prtconf command displays the Solaris device tree. This tree includes all the devices probed by the firmware, as well as additional devices, like individual disks, that only the operating environment software can detect. The output of prtconf also includes the total amount of system memory.
The prtconf command’s -p option produces output similar to the show-devs command. The show-devs command lists only those devices compiled by the system firmware.
The prtdiag command displays a table of diagnostic information that summarizes the status of system components.
# prtdiag System Configuration: Sun Microsystems Sun Fire X4500 BIOS Configuration: American Megatrends Inc. 080010 06/15/2006 BMC Configuration: IPMI 2.0 (KCS: Keyboard Controller Style) ==== Processor Sockets ==================================== Version Location Tag -------------------------------- -------------------------- Dual Core AMD Opteron(tm) Processor 285 H0 Dual Core AMD Opteron(tm) Processor 285 H1 ==== Memory Device Sockets ================================ Type Status Set Device Locator Bank Locator ------- ------ --- ------------------- -------------------- DDR in use 0 H0_DIMM0 BANK0 DDR in use 0 H0_DIMM1 BANK1 DDR in use 0 H0_DIMM2 BANK2 DDR in use 0 H0_DIMM3 BANK3 DDR in use 0 H1_DIMM0 BANK4 DDR in use 0 H1_DIMM1 BANK5 DDR in use 0 H1_DIMM2 BANK6 DDR in use 0 H1_DIMM3 BANK7 ==== On-Board Devices ===================================== Marvell serial-ATA #1 Marvell serial-ATA #2 Marvell serial-ATA #3 Marvell serial-ATA #4 Marvell serial-ATA #5 Marvell serial-ATA #6 Intel 82546EB #1 Intel 82546EB #2 Intel 82551QM ==== Upgradeable Slots ==================================== ID Status Type Description --- --------- ---------------- ---------------------------- 0 in use PCI-X PCIX0 1 available PCI-X PCIX1
The psrinfo command displays the date and time each CPU came online. With the verbose (-v) option, the command displays additional information about the CPUs, including their clock speed. The following is sample output from the psrinfo command with the -v option.
# psrinfo -v Status of virtual processor 0 as of: 08/03/2006 17:49:11 on-line since 08/02/2006 16:28:42. The i386 processor operates at 2593 MHz, and has an i387 compatible floating point processor. Status of virtual processor 1 as of: 08/03/2006 17:49:11 on-line since 08/02/2006 16:28:49. The i386 processor operates at 2593 MHz, and has an i387 compatible floating point processor. Status of virtual processor 2 as of: 08/03/2006 17:49:11 on-line since 08/02/2006 16:28:51. The i386 processor operates at 2593 MHz, and has an i387 compatible floating point processor. Status of virtual processor 3 as of: 08/03/2006 17:49:11 on-line since 08/02/2006 16:28:53. The i386 processor operates at 2593 MHz, and has an i387 compatible floating point processor.
The showrev command displays revision information for the current hardware and software. Code example 3-4 shows sample output of the showrev command.
The cfgadm command is used to take a component offline. The benefit of using the cfgadm command is that you can add, remove, or replace components while the system is running. An added benefit is that the cfgadm command guides you through the steps needed to add, remove, or replace system components.
The cfgadm command resides in the /usr/sbin directory. (See the cfgadm(1M) man page for more information.)
Features of the cfgadm command include the following:
You can use the cfgadm(1M) command to display device type, configuration, and condition status information about drives.
The following command displays a list of SATA drives.
The section Component Configuration Information gives more information about how to use the cfgadm command.
This section describes component configuration and state information for the Sun Fire X4500 Server.
This section includes:
The cfgadm command displays information about attachment points.
An attachment point is a collective term for a component or device, the slot that holds it, and any components on it. Slots are sometimes called receptacles.
An attachment point consists of the following:
There are two types of attachment point names:
An attachment point defines two unique elements, which are distinct from the hardware resources that exist beyond the attachment point. The two elements of an attachment point are a receptacle and an occupant. Physical insertion or removal of hardware resources occurs at attachment points and results in a receptacle gaining or losing an occupant. Configuration administration supports the physical insertion and removal operations as well as other configuration For more information about Ap_Ids, refer to cfgadm(1M).
The cfgadm command provides all resources and dynamic reconfiguration operations in terms of a common set of states (such as configured and unconfigured) and operations (such as connect, configure, unconfigure, and so on). For more information about these common states and operations, see the cfgadm(1M)
To obtain a list of all available logical attachment points, use the following commands in the domain.
1. Log on as a superuser.
2. Type cfgadm -l to display information about server attachment points.
In this example, c0 and c1 represent two SCSI controllers.
Attachment points contain state and condition information. An attachment point can be in one of five conditions: unknown, ok, failing, failed, or unusable. An attachment point can enter the system in any condition depending upon results of power-on tests and non-volatile record keeping.
You can use the cfgadm command to change attachment points.
For information about states, see the sections that follow. For more information about attachment points, see the cfgadm(1M) man page.
This section describes the states and conditions of drive slots, components, and attachment points.
The cfgadm(1M) command can display nine types of states and conditions. For more information, see Component States.
When a drive slot does not hold a drive, its state is empty. When the slot does contain a drive, the state of the drive is either disconnected or connected.
The drive in the slot is disconnected from the system bus. A drive can be in the disconnected state without being powered off. However, a drive must be powered off and in the disconnected state before you remove it from the slot. A newly inserted drive is in the disconnected state.
A drive in the connected state is either configured or unconfigured. A drive that is disconnected is always unconfigured.
A drive can be in one of three conditions: unknown, ok, or failed. Its slot might be designated as unusable.
A disk drive cannot be individually connected or disconnected. Thus, all such components are in the connected state.
The connected component is either configured or unconfigured.