Identifying and Configuring Components
|
This chapter introduces the tools that let you administer the Sun Fire X4540 server and explains how the tools work together.
Topics in this chapter include:
For detailed instructions on diagnosing the server, refer to the Sun Fire X4540 Server Diagnostics Guide (819-4363) and the Sun Fire X4540 Server Service Manual (819-4359).
The Sun Fire X4540 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
Solaris System Commands
This section describes Solaris superuser commands that you can use to assess Sun Fire X4540 server condition and troubleshoot server problems. The related commands include:
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 10-1 prtconf Command Output
$ /usr/sbin/prtconf -p
System Configuration: Sun Microsystems i86pc
Memory size: 32768 Megabytes
System Peripherals (PROM Nodes):
Node ’i86pc’
Node ’ramdisk’
Node ’isa’
Node ’pci’
Node ’pci10de,cb84’
Node ’pci10de,cb84’
|
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 summarizes system component status in table format.
CODE EXAMPLE 10-2 prtdiag Command Output
$ /usr/sbin/prtdiag
System Configuration: Sun Microsystems Sun Fire X4540
BIOS Configuration: American Megatrends Inc. 080014 04/04/2008
BMC Configuration: IPMI 2.0 (KCS: Keyboard Controller Style)
==== Processor Sockets ====================================
Version Location Tag
-------------------------------- --------------------------
Quad-Core AMD Opteron(tm) Processor 2356 CPU 1
Quad-Core AMD Opteron(tm) Processor 2356 CPU 2
==== Memory Device Sockets ================================
Type Status Set Device Locator Bank Locator
------- ------ --- ------------------- --------------------
DDR2 in use 0 DIMM0 BANK0
DDR2 in use 0 DIMM1 BANK1
...
DDR2 in use 0 DIMM15 BANK15
==== On-Board Devices =====================================
Gigabit Ethernet #0
Gigabit Ethernet #1
Gigabit Ethernet #2
Gigabit Ethernet #3
AST2000 VGA
LSI SCSI 1068-e #0
LSI SCSI 1068-e #1
LSI SCSI 1068-e #2
LSI SCSI 1068-e #3
LSI SCSI 1068-e #4
LSI SCSI 1068-e #5
==== Upgradeable Slots ====================================
ID Status Type Description
--- --------- ---------------- ----------------------------
1 available PCI Express PCIExp SLOT0
2 available PCI Express PCIExp SLOT1
3 available PCI Express PCIExp SLOT2
|
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 10-3 psrinfo -v Command Output
$ /usr/sbin/psrinfo -v
Status of virtual processor 0 as of: 06/25/2008 17:54:39
on-line since 06/25/2008 11:34:12.
The i386 processor operates at 2300 MHz,
and has an i387 compatible floating point processor.
Status of virtual processor 1 as of: 06/25/2008 17:54:39
on-line since 06/25/2008 11:34:16.
The i386 processor operates at 2300 MHz,
and has an i387 compatible floating point processor.
Status of virtual processor 2 as of: 06/25/2008 17:54:39
on-line since 06/25/2008 11:34:18.
The i386 processor operates at 2300 MHz,
and has an i387 compatible floating point processor.
Status of virtual processor 3 as of: 06/25/2008 17:54:39
on-line since 06/25/2008 11:34:20.
The i386 processor operates at 2300 MHz,
and has an i387 compatible floating point processor.
Status of virtual processor 4 as of: 06/25/2008 17:54:39
on-line since 06/25/2008 11:34:22.
The i386 processor operates at 2300 MHz,
and has an i387 compatible floating point processor.
Status of virtual processor 5 as of: 06/25/2008 17:54:39
on-line since 06/25/2008 11:34:24.
The i386 processor operates at 2300 MHz,
and has an i387 compatible floating point processor.
Status of virtual processor 6 as of: 06/25/2008 17:54:39
on-line since 06/25/2008 11:34:26.
The i386 processor operates at 2300 MHz,
and has an i387 compatible floating point processor.
Status of virtual processor 7 as of: 06/25/2008 17:54:39
on-line since 06/25/2008 11:34:28.
The i386 processor operates at 2300 MHz,
and has an i387 compatible floating point processor.
|
showrev Command
The showrev command displays revision information for hardware and software. Code example 3-4 shows sample output of the showrev command.
CODE EXAMPLE 10-4 showrev Command Output
$ showrev
Hostname: abc-123
Hostid: dbc23b9
Release: 5.10
Kernel architecture: i86pc
Application architecture: i386
Hardware provider:
Domain:
Kernel version: SunOS 5.10 Generic_127128-11
|
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
CODE EXAMPLE 10-5 cfgadm Command Output
$ /usr/sbin/cfgadm
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c1 scsi-bus connected configured unknown
c2 scsi-bus connected configured unknown
c3 scsi-bus connected configured unknown
c4 scsi-bus connected configured unknown
c5 scsi-bus connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb0/3 unknown empty unconfigured ok
usb0/4 unknown empty unconfigured ok
usb0/5 usb-device connected configured ok
usb0/6 unknown empty unconfigured ok
usb0/7 unknown empty unconfigured ok
usb0/8 unknown empty unconfigured ok
usb0/9 unknown empty unconfigured ok
usb0/10 unknown empty unconfigured ok
usb1/1 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok
usb1/3 unknown empty unconfigured ok
usb1/4 unknown empty unconfigured ok
usb1/5 unknown empty unconfigured ok
usb1/6 usb-hub connected configured ok
usb1/6.1 unknown empty unconfigured ok
usb1/6.2 unknown empty unconfigured ok
usb1/6.3 unknown empty unconfigured ok
usb1/6.4 unknown empty unconfigured ok
usb1/7 unknown empty unconfigured ok
usb1/8 unknown empty unconfigured ok
usb1/9 unknown empty unconfigured ok
usb1/10 unknown empty unconfigured ok
|
You can use the cfgadm -al (1M) command to display device type, configuration, and condition status information about drives.
Type the cfgadm -al | grep disk command to display a list of SATA drives.
CODE EXAMPLE 10-6 cfgadm Command Output with grep (c0-c2)
|
Device
Type
Receptacle
Occupant
Condition
cfgadm -al | grep disk
c0::dsk/c0t0d0 disk connected configured unknown
c0::dsk/c0t1d0 disk connected configured unknown
c0::dsk/c0t2d0 disk connected configured unknown
c0::dsk/c0t3d0 disk connected configured unknown
c0::dsk/c0t4d0 disk connected configured unknown
c0::dsk/c0t5d0 disk connected configured unknown
c0::dsk/c0t6d0 disk connected configured unknown
c0::dsk/c0t7d0 disk connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c1::dsk/c1t3d0 disk connected configured unknown
c1::dsk/c1t4d0 disk connected configured unknown
c1::dsk/c1t5d0 disk connected configured unknown
c1::dsk/c1t6d0 disk connected configured unknown
c1::dsk/c1t7d0 disk connected configured unknown
c2::dsk/c2t0d0 disk connected configured unknown
c2::dsk/c2t1d0 disk connected configured unknown
c2::dsk/c2t2d0 disk connected configured unknown
c2::dsk/c2t3d0 disk connected configured unknown
c2::dsk/c2t4d0 disk connected configured unknown
c2::dsk/c2t5d0 disk connected configured unknown
c2::dsk/c2t6d0 disk connected configured unknown
c2::dsk/c2t7d0 disk connected configured unknown
(next Page)
|
CODE EXAMPLE 10-7 cfgadm Command Output with grep (c3-c5)
|
Device
Type
Receptacle
Occupant
Condition
(Continued)
c3::dsk/c3t0d0 disk connected configured unknown
c3::dsk/c3t1d0 disk connected configured unknown
c3::dsk/c3t2d0 disk connected configured unknown
c3::dsk/c3t3d0 disk connected configured unknown
c3::dsk/c3t4d0 disk connected configured unknown
c3::dsk/c3t5d0 disk connected configured unknown
c3::dsk/c3t6d0 disk connected configured unknown
c3::dsk/c3t7d0 disk connected configured unknown
c4::dsk/c4t0d0 disk connected configured unknown
c4::dsk/c4t1d0 disk connected configured unknown
c4::dsk/c4t2d0 disk connected configured unknown
c4::dsk/c4t3d0 disk connected configured unknown
c4::dsk/c4t4d0 disk connected configured unknown
c4::dsk/c4t5d0 disk connected configured unknown
c4::dsk/c4t6d0 disk connected configured unknown
c4::dsk/c4t7d0 disk connected configured unknown
c5::dsk/c5t0d0 disk connected configured unknown
c5::dsk/c5t1d0 disk connected configured unknown
c5::dsk/c5t2d0 disk connected configured unknown
c5::dsk/c5t3d0 disk connected configured unknown
c5::dsk/c5t4d0 disk connected configured unknown
c5::dsk/c5t5d0 disk connected configured unknown
c5::dsk/c5t6d0 disk connected configured unknown
c5::dsk/c5t7d0 disk connected configured unknown
|
See Component Configuration Information for more information about how to use the cfgadm command.
Component Configuration Information
This section describes component configuration and state information for the Sun Fire X4540 Server.
This section includes:
Attachment Points Overview
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. The cfgadm command displays information about attachment points.
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 configurations. 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, refer to 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. Display information about attachment points on the system.
CODE EXAMPLE 10-8 cfgadm Command Display of Attachment Points
# cfgadm -al
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, refer to 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 10-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 10-2 Configured 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. A drive slot might be designated as unusable.
TABLE 10-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 10-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.