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:
- Isolate problems when there is a failure of a field-replaceable component
- Monitor the status of a functioning system
- Exercise the system to disclose an intermittent or incipient problem
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).
Solaris System Commands
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.
prtconf Command
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.
CODE EXAMPLE 3-1 prtconf Command Output
# prtconf -p
System Configuration: Sun Microsystems i86pc
Memory size: 8096 Megabytes
System Peripherals (PROM Nodes):
|
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.
prtdiag Command
The prtdiag command displays a table of diagnostic information that summarizes the status of system components.
CODE EXAMPLE 3-2 prtdiag Command Output
# 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
|
psrinfo Command
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.
CODE EXAMPLE 3-3 psrinfo -v Command Output
# 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.
|
showrev Command
The showrev command displays revision information for the current hardware and software. Code example 3-4 shows sample output of the showrev command.
CODE EXAMPLE 3-4 showrev Command Output
# showrev
Hostname: abc-123
Hostid: cc0ac37f
Release: 5.10
Kernel architecture: i86pc
Application architecture: i386
Hardware provider: Sun_Microsystems
Domain: Sun.COM
Kernel version: SunOS 5.10 Generic_11122-15
|
cfgadm 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:
- Displaying system component status
- Testing system components
- Changing component configurations
- Displaying configuration help messages
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.
CODE EXAMPLE 3-5 System SATA Disk Drive Status Display
|
Device
|
Type
|
Receptacle
|
Occupant
|
Condition
|
sata0/0::dsk/c0t0d0
|
disk
|
connected
|
configured
|
ok
|
sata0/1::dsk/c0t1d0
|
disk
|
connected
|
configured
|
ok
|
sata0/2::dsk/c0t2d0
|
disk
|
connected
|
configured
|
ok
|
sata0/3::dsk/c0t3d0
|
disk
|
connected
|
configured
|
ok
|
sata0/4::dsk/c0t4d0
|
disk
|
connected
|
configured
|
ok
|
sata0/5::dsk/c0t5d0
|
disk
|
connected
|
configured
|
ok
|
sata0/6::dsk/c0t6d0
|
disk
|
connected
|
configured
|
ok
|
sata0/7::dsk/c0t7d0
|
disk
|
connected
|
configured
|
ok
|
sata1/0::dsk/c1t0d0
|
disk
|
connected
|
configured
|
ok
|
sata1/1::dsk/c1t1d0
|
disk
|
connected
|
configured
|
ok
|
sata1/2::dsk/c1t2d0
|
disk
|
connected
|
configured
|
ok
|
sata1/3::dsk/c1t3d0
|
disk
|
connected
|
configured
|
ok
|
sata1/4::dsk/c1t4d0
|
disk
|
connected
|
configured
|
ok
|
sata1/5::dsk/c1t5d0
|
disk
|
connected
|
configured
|
ok
|
sata1/6::dsk/c1t6d0
|
disk
|
connected
|
configured
|
ok
|
sata1/7::dsk/c1t7d0
|
disk
|
connected
|
configured
|
ok
|
sata2/0::dsk/c4t0d0
|
disk
|
connected
|
configured
|
ok
|
sata2/1::dsk/c4t1d0
|
disk
|
connected
|
configured
|
ok
|
sata2/2::dsk/c4t2d0
|
disk
|
connected
|
configured
|
ok
|
sata2/3::dsk/c4t3d0
|
disk
|
connected
|
configured
|
ok
|
sata2/4::dsk/c4t4d0
|
disk
|
connected
|
configured
|
ok
|
sata2/5::dsk/c4t5d0
|
disk
|
connected
|
configured
|
ok
|
sata2/6::dsk/c4t6d0
|
disk
|
connected
|
configured
|
ok
|
sata2/7::dsk/c4t7d0
|
disk
|
connected
|
configured
|
ok
|
sata3/0::dsk/c5t0d0
|
disk
|
connected
|
configured
|
ok
|
sata3/1::dsk/c5t1d0
|
disk
|
connected
|
configured
|
ok
|
sata3/2::dsk/c5t2d0
|
disk
|
connected
|
configured
|
ok
|
sata3/3::dsk/c5t3d0
|
disk
|
connected
|
configured
|
ok
|
sata3/4::dsk/c5t4d0
|
disk
|
connected
|
configured
|
ok
|
sata3/5::dsk/c5t5d0
|
disk
|
connected
|
configured
|
ok
|
sata3/6::dsk/c5t6d0
|
disk
|
connected
|
configured
|
ok
|
sata3/7::dsk/c5t7d0
|
disk
|
connected
|
configured
|
ok
|
sata4/0::dsk/c6t0d0
|
disk
|
connected
|
configured
|
ok
|
sata4/1::dsk/c6t1d0
|
disk
|
connected
|
configured
|
ok
|
sata4/2::dsk/c6t2d0
|
disk
|
connected
|
configured
|
ok
|
sata4/3::dsk/c6t3d0
|
disk
|
connected
|
configured
|
ok
|
sata4/4::dsk/c6t4d0
|
disk
|
connected
|
configured
|
ok
|
sata4/5::dsk/c6t5d0
|
disk
|
connected
|
configured
|
ok
|
sata4/6::dsk/c6t6d0
|
disk
|
connected
|
configured
|
ok
|
sata4/7::dsk/c6t7d0
|
disk
|
connected
|
configured
|
ok
|
sata5/0::dsk/c7t0d0
|
disk
|
connected
|
configured
|
ok
|
sata5/1::dsk/c7t1d0
|
disk
|
connected
|
configured
|
ok
|
sata5/2::dsk/c7t2d0
|
disk
|
connected
|
configured
|
ok
|
sata5/3::dsk/c7t3d0
|
disk
|
connected
|
configured
|
ok
|
sata5/4::dsk/c7t4d0
|
disk
|
connected
|
configured
|
ok
|
sata5/5::dsk/c7t5d0
|
disk
|
connected
|
configured
|
ok
|
sata5/6::dsk/c7t6d0
|
disk
|
connected
|
configured
|
ok
|
sata5/7::dsk/c7t7d0
|
disk
|
connected
|
configured
|
ok
|
The section Component Configuration Information gives more information about how to use the cfgadm command.
Component Configuration Information
This section describes component configuration and state information for the Sun Fire X4500 Server.
This section includes:
Attachment Points Overview
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:
- An occupant, which represents a hardware component that can be configured into the system. The term occupant refers to the combination of a component and its attached devices, including any external storage devices connected by interface cables.
- A receptacle, which is the location that accepts the occupant.
There are two types of attachment point names:
- Physical attachment point - The software driver and the location of the slot.
- Logical attachment point - An abbreviated name created by the system to see the physical attachment point.
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).
Determining Attachment Points
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)
man page.
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.
CODE EXAMPLE 3-6 cfgadm Command Display of Attachment Point
# cfgadm -l
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c1 scsi-bus connected configured unknown
|
In this example, c0 and c1 represent two SCSI controllers.
Changing to Attachment Points
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.
- To change the state of an attachment point, use these specific cfgadm options:
- configure
- unconfigure
- connect
- disconnect
- To change the availability of an attachment point’s associations, use these specific cfgadm options:
For information about states, see the sections that follow. For more information about attachment points, see the cfgadm(1M) man page.
States and Conditions
This section describes the states and conditions of drive slots, components, and attachment points.
- State is the operational status of either a hard disk drive slot or its occupant.
- Condition is the operational status of an attachment point.
The cfgadm(1M) command can display nine types of states and conditions. For more information, see Component States.
Drive and Drive Slot 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.
TABLE 3-1 Drive and Drive Slot States
|
State
|
Description
|
|
empty
|
The slot does not hold a drive.
|
|
disconnected
|
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.
|
|
connected
|
The drive in the slot is powered on and connected to the system bus. You can view the components on a drive only after it is in the connected state.
|
A drive in the connected state is either configured or unconfigured. A drive that is disconnected is always unconfigured.
TABLE 3-2 Conrfigured and Unconfigured Drives
|
Name
|
Description
|
|
configured
|
The drive is available for use by the Solaris software.
|
|
unconfigured
|
The drive is not available for use by the Solaris software.
|
Drive Conditions
A drive can be in one of three conditions: unknown, ok, or failed. Its slot might be designated as unusable.
TABLE 3-3 Drive and Drive Slot Conditions
|
Name
|
Description
|
|
unknown
|
The drive has not been tested.
|
|
ok
|
The drive is operational.
|
|
failed
|
The drive failed testing.
|
|
unusable
|
The drive slot is unusable.
|
Component States
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.
TABLE 3-4 Connected Components: Configured or Unconfigured
|
Name
|
Description
|
|
configured
|
The component is available for use by the Solaris OS.
|
|
unconfigured
|
The component is not available for use by the Solaris OS.
|
| Sun Fire X4500/X4540 Servers Administration Guide
|
819-6562-17
|
   
|
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.