Sun BladeTM T6320 Server Module Service Manual Sun Microsystems, Inc. www.sun.com Part No. 820-2386-12 June 2009, Revision A Submit comments about this document at: http://www.sun.
Copyright © 2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S.
Contents Preface 1. ix Sun Blade T6320 Server Module Product Description 1.1 Component Overview 1.1.1 1.2 2. 1–1 1–1 Multicore Processor Information 1–9 Support for RAID Storage Configurations 1–10 1.2.1 Sun Blade RAID 5 Expansion Module 1.2.2 Sun Blade RAID 0/1 G2 Expansion Module 1.3 Finding the Serial Number 1.4 Additional Service Related Information 1–11 1–11 1–11 Sun Blade T6320 Server Module Diagnostics 1–14 2–1 2.1 Sun Blade T6320 Server Module Diagnostics Overview 2.
2.3.2 2–16 2.4 Using ILOM for Diagnosis and Repair Verification 2.5 Using the ILOM Web Interface For Diagnostics 2.6 2.7 iv Ethernet Port LEDs 2–16 2–18 2.5.1 Changing POST Settings With the ILOM Web Interface 2.5.2 Changing POST Settings With the ILOM CLI 2.5.3 Displaying System Faults 2–19 2–21 2–21 2.5.3.1 Viewing Fault Status Using the ILOM Web Interface 22 2.5.3.2 Viewing Fault Status Using the ILOM CLI 2– 2–23 2.5.4 Displaying the Environmental Status with the ILOM CLI 2.
2.7.1 2.8 2.9 2.11 2.7.1.2 Using the fmdump Command 2.7.3 Clearing the PSH Fault From the ILOM Logs 2–45 2–46 Collecting Information From Solaris OS Files and Commands 2.8.1 Checking the Message Buffer 2.8.2 Viewing the System Message Log Files 2–47 2–47 2–48 Managing Components With Automatic System Recovery Commands 48 2– Displaying System Components With the show /SYS Command 2–50 Exercising the System With SunVTS 2–51 2.10.1 Checking SunVTS Software Installation 2.10.
4.2 4.3 4.1.1 Safety Symbols 4.1.2 Electrostatic Discharge Safety 4.5 Using an Antistatic Wrist Strap 4.1.2.2 Using an Antistatic Mat Common Procedures for Parts Replacement 4.7 4.8 vi 4–2 4–3 4–3 4.2.1 Required Tools 4.2.2 Shutting Down the System 4.2.3 Using the ILOM Web Interface to Shut Down the Server Module 4–4 4.2.4 Using the ILOM CLI to Shut Down the Server Module 4–3 Removing and Replacing DIMMs 4–3 4–5 4–10 4.3.1 Removing the DIMMs 4–10 4.3.
4.8.1 Replacing the Cover 4.8.2 Reinstalling the Server Module in the Chassis A. Specifications A.1 A.2 4–28 A–1 Physical Specifications A.1.1 4–28 A–1 System Environmental Specifications Motherboard Block Diagram A–2 A–3 B. Creating a Bootable Array With the Sun Blade RAID 5 Expansion Module B.1 About Creating a Bootable Array on a SPARC System B.2 Creating a Bootable Array Task Map B.3 Modifying the Miniroot Directory On the Install Server B.
D.7 Checking Device Configuration D.
Preface The Sun BladeTM T6320 Server Module Service Manual provides information to aid in diagnosing hardware problems and describes how to replace components. This manual also describes how to add components such as hard drives and memory. This manual is written for technicians, service personnel, and system administrators who service and repair computer systems. The person qualified to use this manual: ■ Can open a system chassis, and can identify and replace internal components.
Typographic Conventions Typeface* Meaning Examples AaBbCc123 The names of commands, files, and directories; on-screen computer output Edit your.login file. Type ls -a to list all files. % You have mail. AaBbCc123 What you type, when contrasted with on-screen computer output % su Password: AaBbCc123 Book titles, new words or terms, words to be emphasized. Replace command-line variables with real names or values. Read Chapter 6 in the User’s Guide. These are called class options.
Document Title Description Sun Blade T6320 Server Module Product Notes, 820-2383 Important late-breaking information about the server module and related software. Sun Blade T6320 Server Module Installation Guide, 820-2384 Basic information about installing, powering on and installing software. If you purchased hard drives with preinstalled software you can also find information here: http://www.sun.com/software/preinstall Sun Integrated Lights Out Manager 2.
Third-Party Web Sites Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources.
CHAPTER 1 Sun Blade T6320 Server Module Product Description This chapter provides an overview of the features of the Sun Blade module. (A server module is also known as a “blade.”) TM T6320 server The following topics are covered: 1.1 ■ Section 1.1, “Component Overview” on page 1-1 ■ Section 1.2, “Support for RAID Storage Configurations” on page 1-10 ■ Section 1.3, “Finding the Serial Number” on page 1-11 ■ Section 1.
FIGURE 1-1 Sun Blade T6320 Server Module With Chassis TABLE 1-1 lists the Sun Blade T6320 server module features. TABLE 1-2 lists some of chassis input-output features.
FIGURE 1-2 Front View Front and Rear Panels White - Locator LED (press to reset the LED) Rear View Power connector Blue - Ready to Remove LED Amber - Service Action Required LED Signal connector Green - OK LED Power button NMI (non-maskable interrupt, for service use only) Universal Connector Port (UCP) Green - Drive OK LED Amber - Drive Service Action Required LED Blue - Drive Ready to Remove LED Note – For information about connecting to the server module refer to the Sun Blade T6320 Server Module
FIGURE 1-3 Cable Dongle Connectors Four connector dongle cable (UCP-4) RJ-45 (Do not use this connector with the Sun Blade T6320 Server Module) DB-9 serial, male (TTYA) USB 2.0 (two connectors) Three connector dongle cable (UCP-3) RJ-45 serial USB 2.0 (two connectors) VGA 15-pin, female Insert the connector straight into the server module.
Caution – Insert the connector straight into the server module. The cable dongle is for temporary connections only. The cable dongle has not been evaluated for electromagnetic compatibility (EMC). The cable dongle or server module connectors could be damaged by closing rack doors or other impacts. Remove the cable dongle during normal system operation. Note – If you are using the older 4-cable dongle (UCP-4), do not use the RJ-45 connector with the Sun Blade T6320 server module.
TABLE 1-1 Sun Blade T6320 Server Module Features (Continued) Feature Description Universal Connector Port One universal connector port (UCP) in the front panel. A universal cable is included with the chassis and can be purchased separately (FIGURE 1-3). The following connections are supported: • USB 2.0* • VGA video • Serial (FIGURE 1-3).
For more information about chassis features and controls, refer to the service manual for your blade chassis at: http://docs.sun.com/app/docs/prod/blade.
TABLE 1-3 Sun Blade T6320 Server Module FRU List (Continued) FRU Description FRU Name* Replacement Instructions FB-DIMMs 1 Gbyte, 2 Gbyte, 4 Gbyte SYS/MB/CMPx/B Rx/CHx/Dx Section 4.3.1, “Removing the DIMMs” on page 4-10 Hard drive SFF SAS, or SATA 2.5-inch hard drive in NEMO bracket HDD0,1,2,3 Section 3.2.2, “Removing a Hard Drive” on page 3-2 Server Module Enclosure with CPU, motherboard SYS/MB New server module * The FRU name is used in system messages.
FIGURE 1-5 PCI Express and Ethernet Connections on a Sun Blade 6000 Modular System BL = blade (server module) NEM1 NEM0 1.1.1 Multicore Processor Information The UltraSPARC® T2 multicore processor is the basis of the Sun Blade T6320 server module. The processor has four, six, or eight UltraSPARC cores. Each core equates to a 64-bit execution pipeline capable of running eight threads.
8-core processor handles up to 64 active threads concurrently. For more information about the UltraSPARC® T2 multicore processor, go to: http://www.sun.com/processors/UltraSPARC-T2/features.xml http://www.sun.com/servers/wp.jsp?tab=1 1.
1.2.1 Sun Blade RAID 5 Expansion Module The Sun Blade RAID 5 Expansion Module supports RAID levels 0, 1, 1E, 10, 5, or 6 with global or dedicated hot spares. When a Sun Blade RAID 5 Expansion Module is installed, SAS drives can be installed in disk slots 0 through 3. You can configure these disks as RAID 0, 1, 5, or 10. For information on creating a bootable array, see Appendix B. For information on installing the OS on a bootable array, see Appendix C. 1.2.
FIGURE 1-6 Serial Number and MAC Address Location MAC address Serial number You can type the ILOM show /SYS command or the ALOM CMT showplatform command to obtain the chassis serial number. Both examples are shown below.
-> show /SYS /SYS Targets: SERVICE LOCATE ACT OK2RM SP MB MIDPLANE HDD0 HDD1 HDD2 HDD3 NEM0 NEM1 FM0... .... .... ...
sc> showplatform SUNW, Sun Blade T6320 Server Module Blade Serial Number: 1005LCB-07385N005L Chassis Serial Number: 1005LCB-0709YM007M Slot Number: 5 Domain Status ------ -----S0 Running sc> 1.4 Additional Service Related Information Documentation for the Sun Blade T6320 server module, and related hardware and software is listed in “Accessing Sun Documentation” on page x. The following resources are also available. 1-14 ■ SunSolvesm Online – Provides a collection of support resources.
CHAPTER 2 Sun Blade T6320 Server Module Diagnostics This chapter describes the diagnostics that are available for monitoring and troubleshooting the Sun Blade T6320 server module. This chapter is intended for technicians, service personnel, and system administrators who service and repair computer systems. The following topics are covered: ■ Section 2.1, “Sun Blade T6320 Server Module Diagnostics Overview” on page 2-2 ■ Section 2.2, “Memory Configuration and Fault Handling” on page 2-7 ■ Section 2.
2.1 Sun Blade T6320 Server Module Diagnostics Overview There are a variety of diagnostic tools, commands, and indicators you can use to monitor and troubleshoot a Sun Blade T6320 server module. ■ LEDs – Provide a quick visual notification of the status of the server module and some of the FRUs. ■ ILOM firmware – This system firmware runs on the service processor.
The diagnostic flowchart in FIGURE 2-1 and TABLE 2-1 describes an approach for using the server module diagnostics to identify a faulty field-replaceable unit (FRU). The diagnostics you use, and the order in which you use them, depend on the nature of the problem you are troubleshooting, so you might perform some actions and not others.
FIGURE 2-1 Diagnostic Flowchart 1. Are the Power OK LEDs off? Faulty hardware suspected Yes Numbers in this flow chart correspond to the Action numbers in Table 2-1. Check the power source and connections. No 2. Are any faults reported by the ILOM show /SP/faultmgt command? Are any Service LEDs 0n? Yes The ILOM show/SP/ faultmgt command displays a fault No Identify faulty FRU from the fault message and replace the FRU. Yes 3. Do the Solaris logs indicate a faulty FRU? 6.
TABLE 2-1 Action No. Diagnostic Flowchart Actions Diagnostic Action For more information, see these sections Resulting Action 1. Check the OK LED. The OK LED is located on the front of the Sun Blade Section 2.3, “Interpreting T6320 server module. System LEDs” on page 2-12 If the LED is not lit, check that the blade is properly connected and the chassis has power. 2. Type the ILOM show /SP/faultmgmt command to check for faults.
TABLE 2-1 Action No. 7. Diagnostic Flowchart Actions (Continued) Diagnostic Action Resulting Action Determine if the fault was detected by PSH. If the fault message displays the following text, the fault was detected by the Solaris Predictive SelfHealing software: Host detected fault If the fault is a PSH detected fault, identify the faulty FRU from the fault message and replace the faulty FRU. After the FRU is replaced, perform the procedure to clear PSH detected faults.
2.2 Memory Configuration and Fault Handling New dual rank fully-buffered (FB) DIMMs replace the single rank FB-DIMMs. The Sun Blade T6320 server module has 16 connectors (slots) that hold Sun approved, industry standard FB-DIMMs in the following capacities: ■ 1 Gbyte (maximum of 16 Gbytes) ■ 2 Gbyte (maximum of 32 Gbytes) ■ 4 Gbyte (maximum of 64 Gbytes) ■ 8 Gbyte (maximum of 128 Gbytes) The Sun Blade T6320 server module performs best if all 16 connectors are populated with 16 identical FB-DIMMs.
When Replacing Faulty FB-DIMMs Within each branch, ensure that the replacement FB-DIMM has the same part number as the FB-DIMM you are removing. If you are unable to obtain an FB-DIMM with the same part number, you might need to replace all FB-DIMMs in the branch to ensure that they all have the same part number. The following table lists the supported FB-DIMMs and part numbers.
FIGURE 2-3 FB-DIMM Installation Rules Eight DIMMs installed Four DIMMs installed BR1/CH1/D0 BR1/CH0/D0 BR0/CH1/D0 BR0/CH0/D0 BR2/CH0/D0 BR2/CH1/D0 BR3/CH0/D0 BR3/CH1/D0 BR1/CH1/D1 BR1/CH0/D1 BR0/CH1/D1 BR0/CH0/D1 BR2/CH0/D1 BR2/CH1/D1 BR3/CH0/D1 BR3/CH1/D1 Sixteen DIMMs installed Chapter 2 Sun Blade T6320 Server Module Diagnostics 2-9
FIGURE 2-4 DIMM Locate Button and DIMM LEDs You can also use TABLE 2-2 to identify the DIMMs you want to remove.
TABLE 2-2 Branch Name FB-DIMM Configuration and Installation (Continued) Channel Name Channel 1 FRU Name Motherboard FB-DIMM Connector FB-DIMM Installation Order* FB-DIMM Pair\ /SYS/MB/CMP0/BR3/CH0/D1 J2501 3 H /SYS/MB/CMP0/BR3/CH1/D0 J2601 2 G /SYS/MB/CMP0/BR3/CH1/D1 J2701 3 H * Upgrade path: DIMMs should be added with each group populated in the order shown. \ Fault replacement path: Each pair is addressed as a unit, and each pair must be identical. 2.2.1.
associated with the fault. Once you have identified which DIMMs to replace, see Chapter 4 for DIMM removal and replacement instructions. You must perform the instructions in that chapter to clear the faults and enable the replaced DIMMs. 2.3 Interpreting System LEDs The Sun Blade T6320 server module has LEDs on the front panel and the hard drives. The behavior of LEDs on your server module conforms to the American National Standards Institute (ANSI) Status Indicator Standard (SIS).
FIGURE 2-5 Front Panel and Hard Drive LEDs Front View White - Locator LED (press to reset the LED) Blue - Ready to Remove LED Amber - Service Action Required LED Green - OK LED Power button NMI (non-maskable interrupt for service use only) Universal Connector Port (UCP) Green - Drive OK LED Amber - Drive Service Action Required LED Blue - Drive Ready to Remove LED . TABLE 2-3 LED Behavior and Meaning LED Behavior Meaning Off The condition represented by the color is not true.
TABLE 2-4 LED Behaviors With Assigned Meanings Color Behavior Definition White Off Steady state Fast blink 4 Hz repeating sequence, equal intervals On and Off. This indicator helps you to locate a particular enclosure, board, or subsystem (for example, the Locator LED). The LED is activated using one of the following methods: • Type the ILOM command: set /SYS/LOCATE value=on • Press the button to toggle the indicator on or off.
TABLE 2-4 Color LED Behaviors With Assigned Meanings (Continued) Behavior Definition Description, Actions, and ILOM Commands Standby blink Repeating sequence The system is running at a minimum level and is ready to be consisting of a brief quickly revived to full function (for example, the System Activity (0.1 sec.) on flash LED). followed by a long off period (2.9 sec.
2.3.2 Ethernet Port LEDs For information about Ethernet LEDs see the service manual for your modular system chassis or ethernet device at: http://docs.sun.com/app/docs/prod/blade.6000mod 2.4 Using ILOM for Diagnosis and Repair Verification The Sun Integrated Lights Out Manager (ILOM) is contained on firmware on the service processor in the Sun Blade T6320 server module. ILOM enables you to remotely manage and administer your server module. Note – ILOM also contains an ALOM-CMT compatibility shell.
FIGURE 2-6 ILOM Fault Management Service Required LED FRU LEDs ILOM FRUID PROMs Event Logs Alerts In ILOM you can view the ILOM logs to see alerts. FIGURE 2-7 is a sample of the ILOM web interface. Using the CLI you can type the show /SP/logs/event/list/ command. FIGURE 2-7 Sample Event Log in ILOM Web Interface ILOM can detect when a fault is no longer present and clears the fault in several ways: ■ Fault recovery – The system automatically detects that the fault condition is no longer present.
Many environmental faults can automatically recover. For example, a temperature that is exceeding a threshold might return to normal limits, when you connect a fan. The recovery of environmental faults is automatically detected. Recovery events are reported using one of two forms: ■ fru at location is OK. ■ sensor at location is within normal range. There are three thresholds for an environmental fault: ■ Warning: ILOM issues a command to burst the fan speed.
1. Connect to the ILOM web interface by typing the IP address for the Sun Blade T6320 server module service processor in a web browser. If you do not know the IP address for the server module, you can obtain the service processor IP address from the following: ■ ILOM CLI: ->show /SP/network ■ ALOM-CMT compatibility shell: sc> showsc ■ Chassis CMM ILOM: ->show /CH/BLx/SP/network (Where BLx is the number of the blade server module in the chassis.) 2.
1. Select the Remote Control tab and the Diagnostics tab (FIGURE 2-9). 2. Set the verbosity level, trigger, and other settings as needed. TABLE 2-6 shows how different settings produce POST output. FIGURE 2-9 Setting POST Diagnostics Levels With the ILOM Web Based Interface 3. To set the diagnostics mode, select the Remote Control tab and the Keyswitch tab.
2.5.2 Changing POST Settings With the ILOM CLI 1. Type the show command to see the current POST settings: -> show /HOST/diag /HOST/diag Targets Properties: level = max mode = normal trigger = power-on-reset error-reset verbosity = normal Commands: cd set show 2. Change the POST settings with the set /HOST/diag command.
Use the web interface or type the show /SP/faultmgmt command for the following reasons: 2.5.3.1 ■ To see if any faults have been passed to, or detected by the ILOM firmware. ■ To obtain the fault message ID (SUNW-MSG-ID) for PSH detected faults. ■ To verify that the replacement of a FRU has cleared the fault and not generated any additional faults.
FIGURE 2-11 Faulted Component ID Window Alternatively, in the ILOM web interface, you can identify the fault status of a component on the Component Management page. FIGURE 2-12 2.5.3.2 Component Management Page - Fault Status Viewing Fault Status Using the ILOM CLI In the ILOM CLI, you can view the fault status of component(s) by using the show command.
->show /SP/faultmgmt 2.5.4 Displaying the Environmental Status with the ILOM CLI The ILOM show command displays a snapshot of the server module environmental status. This command displays system temperatures, hard drive status, power supply and fan status, front panel LED status, voltage, and current sensors. The output uses a format similar to the Solaris OS command prtdiag (1M). At the -> prompt, type the show command. The output differs according to your system model and configuration.
2.5.5 Displaying the Environmental Status and Sensor Readings with the ILOM Web Interface 1. Open a web browser and type the IP address of the server module service processor in the browser. 2. Select the top System Monitoring tab and the lower Sensor Readings tab (FIGURE 2-13). 3. Double click on the sensor reading that you want to check (FIGURE 2-13).
FIGURE 2-14 2.5.6 Sensor Reading Window for an FB-DIMM in Channel 1 Displaying FRU Information ILOM can display static FRU information such as the FRU manufacturer, serial number and some FRU status information (FIGURE 2-15). Note – To view dynamic FRU information you must type the ALOM CMT showfru command. The dynamic FRU information provides more details about FRUs. 2.5.6.1 Using the ILOM Web Interface to Display FRU Information 1. Select the System Information and Components tabs. 2.
FIGURE 2-15 2.5.6.2 Static FRU Information in the ILOM Web Interface Using the CLI to Display FRU Information The show /SYS/MB command displays static information about the FRUs in the server module. Use this command to see information about an individual FRU, or for all the FRUs.
● At the -> prompt, type the show command. In the following example, the show command displays information about the motherboard (MB). -> show /SYS/MB /SYS/MB Targets: FEM0 REM0 SEEPROM SCC_NVRAM NET SASHBA USB0 USB1 T_AMB CMP0 V_VMEML V_VMEMR V_+3V3_STBY V_VCORE V_+3V3_MAIN V_VDDIO V_+12V0_MAIN VCORE_POK VMEML_POK VMEMR_POK Properties: type = Motherboard fru_name = MB fru_description = 4C,1.
sc> showfru /SYS/SP (container) SEGMENT: ST /Status_CurrentR /Status_CurrentR/UNIX_Timestamp32: Thu Feb 17 07:25:57 2000 /Status_CurrentR/status: 0x00 (OK) SEGMENT: TH ... ... ... ...
/SunSPD/status /SunSPD/Initiator /SunSPD/Message: /SunSPD/powerupdate: /SunSPD/Poweron_minutes: /SYS/MB/CMP0/BR1/CH0/D0 (container) ... ... ... sc> 2.6 0x00 (OK) N/A No message Thu Feb 17 07:01:16 2000 1487 Running POST Use POST to test and verify server module hardware. Power-on self-test (POST) is a group of PROM-based tests that run when the server module is powered on or reset. POST checks the basic integrity of the critical hardware components in the server module (CPU, memory, and I/O buses).
TABLE 2-6 lists the DIAG variables used to configure POST and FIGURE 2-16 shows how the variables work together. TABLE 2-6 Parameters Used For POST Configuration Parameter Values Description setkeyswitch* normal The system can power on and run POST (based on the other parameter settings). For details see FIGURE 2-16. This parameter overrides all other commands. diag The system runs POST based on predetermined settings. stby The system cannot power on.
FIGURE 2-16 2-32 Flowchart of ILOM Variables for POST Configuration Sun Blade T6320 Server Module Service Manual • June 2009
TABLE 2-7 shows typical combinations of ILOM variables and associated POST modes.
FIGURE 2-17 Setting POST Parameters With the ILOM Web Interface 5. Select the Remote Power Control Tab. 6. Select a power control setting and Select Save (FIGURE 2-18).
FIGURE 2-18 Changing Power Settings with the ILOM Web Interface When you power cycle the server module, POST runs and displays output to the service processor console window: {0} ok Chassis | critical: Host has been powered off Chassis | major: Host has been powered on 2007-11-07 18:22:19.511 0:0:0> 2007-11-07 18:22:19.560 0:0:0>Sun Blade T6320 Server Module POST 4.27.4 2007/10/02 19:09 /export/delivery/delivery/4.27/4.27.4/post4.27.x/Niagara/glendale/integrated (root) 2007-11-07 18:22:19.
2007-11-07 2007-11-07 2007-11-07 2007-11-07 2007-11-07 18:22:20.421 18:22:20.533 18:22:20.629 18:22:20.714 18:22:20.843 0:0:0>VBSC selecting Normal mode, MAX Testing. 0:0:0>VBSC setting verbosity level 3 0:0:0> Niagara2, Version 2.1 0:0:0> Serial Number: 0f880060.768660a8 0:0:0>Basic Memory Tests..... 7. Read the POST output to determine if you need to perform service actions. See Section 2.6.3, “Interpreting POST Messages” on page 2-38. 2.6.2.2 Using the CLI to Change POST Parameters 1.
3. Power cycle the server module to run POST. There are several ways to initiate a reset. The following example uses the ILOM reset command. -> reset /SYS Are you sure you want to reset /SYS (y/n)? y Performing hard reset on /SYS -> 4. Read the POST output to determine if you need to perform service actions. See Section 2.6.3, “Interpreting POST Messages” on page 2-38. 2.6.3 Interpreting POST Messages When POST is finished running and no faults were detected, the system will boot.
2. Type the show /SPfaultmgmt command to obtain additional fault information. The fault is captured by ILOM, where the fault is logged. The Service Action Required LED is lit, and the faulty component is disabled. For example: ok #. -> -> show /SP/faultmgmt /SP/faultmgmt Targets: 0 (/SYS/MB/CMP0/BR2/CH1/D1) Properties: Commands: cd show In this example, /SYS/MB/CMP0/BR2/CH1/D1 is disabled. The system can boot using memory that was not disabled until the faulty component is replaced.
2.6.4.1 Clearing Faults With the Web Interface This procedure describes how to enable components after a POST fault has been generated. The POST fault log is not actually cleared. 1. Select the tabs: System Information and Components tabs (FIGURE 2-19). 2. Select the radio button for the component that you must clear. 3. In the Actions menu, select: Enable Component.
2.6.4.2 Clearing Faults With the ILOM CLI 1. At the ILOM prompt, type the show /SP/faultmgmt command to identify POST detected faults. POST detected faults are distinguished from other faults by the text: deemed faulty and disabled, and no UUID number is reported. For example: -> show /SP/faultmgmt ■ If no fault is reported, you do not need to do anything else. Do not perform the subsequent steps. ■ If a fault is detected, continue with Step 2. 2.
4. At the ILOM prompt, type the show /SP/faultmgmt command to verify that no faults are reported. -> show /SP/faultmgmt Last POST run: THU MAR 09 16:52:44 2006 POST status: Passed all devices No failures found in System 2.6.4.3 Clearing Faults Manually with ILOM The ILOM set /SYS/clear_fault_action=enabled command allows you to manually clear certain types of faults without replacing a FRU. It also allows you to clear a fault if ILOM was unable to automatically detect the FRU replacement. 2.6.4.
The Predictive Self-Healing technology covers the following Sun Blade T6320 server module components: ■ UltraSPARC® T2 multicore processor (CPU) ■ Memory ■ I/O bus The PSH console message provides the following information: ■ Type ■ Severity ■ Description ■ Automated response ■ Impact ■ Suggested action for system administrator If the Solaris PSH facility has detected a faulty component, type the fmdump command to identify the fault.
2. Use the output of this command to clear the fault as shown in Section 2.7.2, “Clearing PSH Detected Faults” on page 2-45. If fmadm faulty does not identify a faulty component or if you need more detailed information, type the fmdump command. 2.7.1.2 Using the fmdump Command The fmdump command displays the list of faults detected by the Solaris PSH facility. Use this command for the following reasons: ■ To see if any faults have been detected by the Solaris PSH facility.
a. In a browser, go to the Predictive Self-Healing Knowledge Article web site: http://www.sun.com/msg b. Type the message ID in the SUNW-MSG-ID field, and press Lookup. In this example, the message ID SUN4U-8000-6H returns the following information for corrective action: CPU errors exceeded acceptable levels Type Fault Severity Major Description The number of errors associated with this CPU has exceeded acceptable levels.
1. After replacing a faulty FRU, boot the system. 2. Type fmadm faulty: # fmdadm faulty STATE RESOURCE /UUID faulted cpu:///cpuid=8/serial=FAC006AE4515C47 8856153f-6f9b-47c6-909a-b05180f53c07 3. Clear the fault from all persistent fault records. In some cases, even though the fault is cleared, some persistent fault information remains and results in erroneous fault messages at boot time.
1. After replacing a faulty FRU, at the ILOM prompt, type the ILOM -> show faults command to identify PSH detected faults. PSH detected faults are distinguished from other faults by the text: Host detected fault. For example: -> show /SP/faultmgmt ■ If no fault is reported, you do not need to do anything else. ■ If the fault is reported, continue with Step 2. 2.
2. Type the syslogd command. # syslogd The syslogd command displays the most recent messages generated by the system. 2.8.2 Viewing the System Message Log Files The error logging daemon, syslogd, automatically records various system warnings, errors, and faults in message files. These messages can alert you to system problems such as a device that is about to fail. The /var/adm directory contains several message files. The most recent messages are in the /var/adm/messages file.
The database that contains the list of disabled components is called the ASR blacklist (asr-db). In most cases, POST automatically disables a component when it is faulty. After the cause of the fault is repaired (FRU replacement, loose connector reseated, and so on), you must remove the component from the ASR blacklist. The ASR commands (TABLE 2-8) enable you to view and manually add or remove components from the ASR blacklist. These commands are run from the ILOM -> prompt.
2.9.1 Displaying System Components With the show /SYS Command To see examples of ILOM web interface and CLI commands that show component status, see Section 2.5.4, “Displaying the Environmental Status with the ILOM CLI” on page 2-24. The show command displays the system components (asrkeys) and reports their status. 1. At the -> prompt, type the show command. An example with no disabled components.
2.10 Exercising the System With SunVTS Sometimes a system exhibits a problem that cannot be isolated definitively to a particular hardware or software component. In such cases, it might be useful to run a diagnostic tool that stresses the system by continuously running a comprehensive battery of tests. Sun provides the SunVTS software for this purpose. 2.10.
The SunVTS 6.4PS1 software, and subsequent compatible versions, are supported on the Sun Blade T6320 server module. SunVTS installation instructions are described in the Sun VTS 6.4 User’s Guide, 8201669. 2.10.2 Exercising the System Using SunVTS Software Before you begin, the Solaris OS must be running. You should verify that SunVTS validation test software is installed on your system. See Section 2.10.1, “Checking SunVTS Software Installation” on page 2-51.
3. Remotely log in to the server as superuser. Type a command such as rlogin or telnet. 4. Start SunVTS software. # /opt/SUNWvts/bin/sunvts -display display-system:0 As SunVTS starts, it prompts you to choose between using CLI, BI, or tty interfaces. A representative SunVTS BI is displayed below (FIGURE 2-20).
5. (Optional) Select the test category you want to run. Certain tests are enabled by default, and you can choose to accept these. Alternatively, you can enable or disable test categories by clicking the checkbox next to the test name or test category name. Tests are enabled when checked, and disabled when not checked. TABLE 2-10 lists tests that are especially useful to run on this server.
2.11 ■ VTS Kernel Error – Error messages pertaining to SunVTS software itself. Look here if SunVTS software appears to be acting strangely, especially when it starts up. ■ Solaris OS Messages (/var/adm/messages) – A file containing messages generated by the operating system and various applications. ■ Log Files (/var/sunvts/logs) – A directory containing the log files.
6. Close the server module, install it in the modular system chassis, and boot the server module. Refer to the Sun Blade T6320 Server Module Installation Guide for instructions.
2-56 Sun Blade T6320 Server Module Service Manual • June 2009
CHAPTER 3 Replacing Hot-Swappable and HotPluggable Components This chapter describes how to remove and replace the hot-swappable and hotpluggable field-replaceable units (FRUs) in the Sun Blade T6320 server module. The following topics are covered: 3.1 ■ Section 3.1, “Hot-Pluggable Hard Drives” on page 3-1 ■ Section 3.2, “Hot-Plugging a Hard Drive” on page 3-1 ■ Section 3.
3.2.1 Rules for Hot-Plugging To safely remove a hard drive, you must: ■ Prevent any applications from accessing the hard drive. ■ Remove the logical software links. Hard drives cannot be hot-plugged if: ■ The hard drive provides the operating system, and the operating system is not mirrored on another drive. ■ The hard drive cannot be logically isolated from the online operations of the server module.
FIGURE 3-1 Hard Drive Locations and LEDs Amber LED Service Action Required Green LED Drive OK HDD2 Blue LED Drive Ready to Remove HDD3 HDD0 HDD1 4. Push the latch release button (FIGURE 3-2). Caution – The latch is not an ejector. The latch can be damaged if you bend it too much. Handle the hard drive carefully: the hard drive printed circuit board is not covered. 5. Grasp the latch and pull the drive out of the drive slot.
FIGURE 3-2 3.2.3 Hard Drive Locations, Release Button, and Latch HDD2 HDD3 HDD0 HDD1 Replacing a Hard Drive or Installing a New Hard Drive The hard drive is physically addressed to the slot in which it is installed. Note – If you removed a hard drive, ensure that you install the replacement drive in the same slot. 1. If necessary, remove the hard drive filler panel. 2. Slide the drive into the bay until it is fully seated (FIGURE 3-2.).
3. Close the latch to lock the drive in place. 4. Perform administrative tasks to reconfigure the hard drive. The procedures that you perform at this point depend on how your data is configured. You might need to partition the drive, create file systems, load data from backups, or have data updated from a RAID configuration. 3.3 ■ You can use the Solaris command cfgadm -al to list all disks in the device tree, including 'unconfigured' disks.
3-6 Sun Blade T6320 Server Module Service Manual • June 2009
CHAPTER 4 Replacing Cold-Swappable Components This chapter describes how to remove and replace field-replaceable units (FRUs) that must be cold-swapped. The following topics are covered: 4.1 ■ Section 4.1, “Safety Information” on page 4-1 ■ Section 4.2, “Common Procedures for Parts Replacement” on page 4-3 ■ Section 4.3, “Removing and Replacing DIMMs” on page 4-10 ■ Section 4.4, “Removing and Replacing the Service Processor” on page 4-15 ■ Section 4.
4.1.1 ■ Follow all Sun standard cautions, warnings, and instructions marked on the equipment and described in Important Safety Information for Sun Hardware Systems, 816-7190. ■ Ensure that the voltage and frequency of your power source match the voltage and frequency inscribed on the equipment s electrical rating label. ■ Follow the electrostatic discharge safety practices as described in this section.
on the chassis. Do this after you disconnect the power cords from the server module. Following this practice equalizes the electrical potentials between you and the server module. 4.1.2.2 Using an Antistatic Mat Place ESD-sensitive components such as the motherboard, memory, and other PCB cards on an antistatic mat. 4.2 Common Procedures for Parts Replacement Before you can remove and replace internal components, you must perform the procedures in this section. 4.2.
1. Log in as superuser or equivalent. TABLE 4-1 ILOM Web Interface Tabs Poweroff Command Equivalents ILOM CLI Remote Control, -> stop /sys Remote Power Control, -> stop -script /sys Select Action ALOM-CMT Compatibility Shell sc> poweroff -y Server Module Power Button Use a paper clip to press the power button for a graceful shutdown. Depending on the nature of the problem, you might want to view the system status, the log files, or run diagnostics before you shut down the system.
FIGURE 4-1 4.2.4 Powering Off the Server Module with the ILOM Web Interface Using the ILOM CLI to Shut Down the Server Module 1. Switch from the system (host) console to the ILOM -> prompt by typing the #. (Hash-Period) key sequence.
2. At the ILOM -> prompt, type the set /SYS/PS0 prepare_to_remove_action=true command and type y to confirm. ILOM CLI, ILOM web interface, and ALOM-CMT command equivalents are shown in TABLE 4-1. -> set /SYS/ prepare_to_remove_action=true Are you sure you want to stop /SYS (y/n)? y Stopping /SYS The blue blade ok2 remove LED is illuminated. The top white LED is the Locator LED.
FIGURE 4-2 Disconnecting the Cable Dongle Four connector dongle cable (UCP-4) RJ-45 (Do not use this connector with the Sun Blade T6320 Server Module) DB-9 serial, male (TTYA) USB 2.0 (two connectors) VGA 15-pin, female Three connector dongle cable (UCP-3) RJ-45 serial USB 2.
Caution – The cable dongle is for temporary connections only. The cable dongle has not been evaluated for electromagnetic compatibility (EMC). The cable dongle or server module connectors could be damaged by rack doors or other impacts. Remove the cable dongle during normal system operation. Note – If you are using the older 4-cable dongle (UCP-4), do not use the RJ-45 connector with the Sun Blade T6320 server module. Use the DB-9 connector for serial connections. 4. Open the ejector levers (FIGURE 4-3).
Caution – Hold the server module firmly so that you do not drop it. The server module weighs approximately 16 pounds (7.3 kg). Caution – Do not stack server modules higher than five units tall. They might fall and cause damage or injury. FIGURE 4-4 Stack Five Server Modules or Fewer 6. Set the server module on an antistatic mat. 7. Attach an antistatic wrist strap. When servicing or removing server module components, attach an antistatic strap to your wrist and then to a metal area on the chassis.
FIGURE 4-5 Antistatic Mat and Wrist Strap 8. While pressing the top cover release button, slide the cover toward the rear of the server module about an inch (2.5 mm). 9. Lift the cover off the chassis. 4.3 Removing and Replacing DIMMs This section describes how to remove and replace DIMMs. 4.3.1 Removing the DIMMs LEDs indicate if a DIMM requires replacement. ■ If the system is still powered on and installed in the chassis, see Section 2.
1. Perform the procedures described in Section 4.2, “Common Procedures for Parts Replacement” on page 4-3. 2. Locate the DIMMs that you want to replace (FIGURE 4-7). The server module has a DIMM locate button on the motherboard. Press the DIMM locate button to illuminate the LEDs of the bad DIMMs. FIGURE 4-6 DIMM Locate Button and DIMM LEDs You can also use FIGURE 4-7 and TABLE 4-2 to identify the DIMMs that you want to remove.
FIGURE 4-7 DIMM Installation Rules Eight DIMMs installed Four DIMMs installed BR1/CH1/D0 BR1/CH0/D0 BR0/CH1/D0 BR0/CH0/D0 BR2/CH0/D0 BR2/CH1/D0 BR3/CH0/D0 BR3/CH1/D0 BR1/CH1/D1 BR1/CH0/D1 BR0/CH1/D1 BR0/CH0/D1 BR2/CH0/D1 BR2/CH1/D1 BR3/CH0/D1 BR3/CH1/D1 Sixteen DIMMs installed TABLE 4-2 FB-DIMM Configuration Branch Name Channel Name FRU Name Motherboard FB-DIMM Connector Branch 0 Channel 0 /SYS/MB/CMP0/BR0/CH0/D0 J1001 1 A /SYS/MB/CMP0/BR0/CH0/D1 J1101 3 B 4-12 Sun Blade T6320 S
TABLE 4-2 Branch Name Branch 1 FB-DIMM Configuration Channel Name FRU Name Motherboard FB-DIMM Connector Channel 1 /SYS/MB/CMP0/BR0/CH1/D0 J1201 2 A /SYS/MB/CMP0/BR0/CH1/D1 J1301 3 B /SYS/MB/CMP0/BR1/CH0/D0 J1401 1 C /SYS/MB/CMP0/BR1/CH0/D1 J1501 3 D /SYS/MB/CMP0/BR1/CH1/D0 J1601 2 C /SYS/MB/CMP0/BR1/CH1/D1 J1701 3 D /SYS/MB/CMP0/BR2/CH0/D0 J2001 1 E /SYS/MB/CMP0/BR2/CH0/D1 J2101 3 F /SYS/MB/CMP0/BR2/CH1/D0 J2201 2 E /SYS/MB/CMP0/BR2/CH1/D1 J2301 3 F /SYS/MB/C
FIGURE 4-8 Removing DIMMs 5. Grasp the top corners of the faulty DIMM and remove it from the system. 6. Place DIMMs on an antistatic mat. 4.3.2 Replacing the DIMMs See Section 2.2.1, “FB-DIMM Configuration Guidelines” on page 2-7 for complete memory configuration and installation rules. Caution – The DIMM rules must be followed. The server module might not operate correctly if the DIMM rules are not followed. Always use DIMMs that have been qualified by Sun. 1.
4.3.2.1 Verifying DIMM Installation Clear the previous faults and enable the DIMMs. See Section 2.6.4, “Clearing POST Detected Faults” on page 2-39. 4.4 Removing and Replacing the Service Processor The service processor controls the host power and monitors host system events (power and environmental). The service processor holds a battery and a socketed EEPROM for storing the system configuration, all Ethernet MAC addresses, and the host ID. Caution – Handle the components carefully to avoid damage. 4.
FIGURE 4-9 Removing the Service Processor 3. Grasp the top corners of the service processor and pull it out of the bracket. 4. Place the service processor card on an antistatic mat. 5. Remove the system configuration PROM (NVRAM) (FIGURE 4-10) from the service processor card and place the PROM on an antistatic mat. The service processor contains the persistent storage for the system host ID and Ethernet MAC addresses.
FIGURE 4-10 4.4.2 Removing the System Configuration PROM (NVRAM) Replacing the Service Processor 1. Remove the replacement service processor from the package and place it on an antistatic mat. 2. Install the system configuration PROM (NVRAM) that you removed from the faulty service processor. The PROM is keyed to ensure proper orientation. 3. Insert the service processor edge into the bracket and carefully align the service processor so that each of its contacts is centered on a socket pin. 4.
5. Perform the procedures described in Section 4.8, “Finishing Component Replacement” on page 4-28. 4.5 Removing and Replacing the Battery on the Service Processor Caution – Handle the components carefully to avoid damage. 1. Perform the procedures described in Section 4.2, “Common Procedures for Parts Replacement” on page 4-3. 2. To remove the service processor from the chassis, pull back the plastic tab and lift the handle (Section 4.4, “Removing and Replacing the Service Processor” on page 4-15). 3.
FIGURE 4-11 4.5.1 Removing the Battery From the Service Processor Replacing the Battery on the Service Processor 1. Remove the replacement battery from the package. 2. Press the new battery into the service processor (FIGURE 4-11) with the positive side (+) facing upward (away from the card). 3. Place the edge of the service processor in between the tabs on the plastic bracket and carefully align the connectors. 4. Press between the handle edges until the service processor is seated in the connector. 5.
6. Before you poweron the host system, type the ILOM set /SP/clock datetime command to set the day and time. For details about this command, refer to the Sun Integrated Lights out Manager 2.0 User’s Guide, 820-1188. ->set /SP/clock datetime=10 Set ‘datetime’ to ‘102421532007.30’ -> show /SP/clock Targets Properties: datetime = Wed Oct 24, 21:53:38 2007 usentpserver = disabled ... 4.
1. Place your fingers under the RAID expansion module (REM), with each finger close top the connector (FIGURE 4-12). 2. Lift the card free from the connector. 3. Lift the REM free from the gray plastic standoff. FIGURE 4-12 4.6.1 Removing the RAID Expansion Module Installing the RAID 5 Expansion Module 1. Place the card under the tabs of the gray plastic standoff (FIGURE 4-13). 2.
FIGURE 4-13 Replacing the RAID 5 Expansion Module Verifying the RAID 5 Expansion Module Installation Note – Check all SAS cables to ensure that they are securely attached and are not damaged or pinched anywhere along the length of cable. 1. Power-up the computer and storage systems. a. Ensure that all hard disk drives are securely installed. b. Connect all power cords securely and plug them into the proper power sources. c.
2. Enter the Open Boot Prompt (OBP) and use the show-disks command to list the current devices. In the following example, the HBA is the first device that is listed. {0} ok show-disks a) /pci@500/pci@0/pci@9/scsi@0/disk b) /pci@500/pci@0/pci@2/pci@0/usb@0,2/storage@5/disk c) /pci@500/pci@0/pci@2/pci@0/usb@0,2/storage@1/disk Note – Device paths might vary from this example, depending on which SPARC system you are using and into which PCI-E slot the card is plugged. 3.
4. To display additional configuration information, list the device properties by using the .properties command. {0} ok .properties firmware-version assigned-addresses compatible model reg version wide device_type name fcode-rom-offset interrupts cache-line-size class-code subsystem-id subsystem-vendor-id 15825 82e70010 00000000 50000000 00000000 00200000 82e70030 00000000 50200000 00000000 00080000 pciex9005,285.108e.7aac.9 pciex9005,285.108e.7aac pciex9005,285.
4.6.3 Creating a Bootable Array With the RAID 5 Expansion Module If you are installing an operating system onto a bootable array, see Appendix B. 4.6.4 Additional Information For more information, refer to the following documents at: http://docs.sun.
FIGURE 4-14 4.7.1 Removing the RAID Expansion Module Replacing the RAID 0/1 Expansion Module 1. Place the card under the tabs of the gray plastic standoff (FIGURE 4-15). 2. Press on the rubber button on the top of the card until the connector engages with the connector on the motherboard (FIGURE 4-15).
FIGURE 4-15 4.7.2 Replacing the RAID 0/1 Expansion Module Verifying the RAID 0/1 Expansion Module Installation Refer to the Sun Blade G2 RAID 0/1 Expansion Module Installation Guide (820-5448) for details. Note – Check all SAS cables to ensure that they are securely attached and are not damaged or pinched anywhere along the length of cable.
4.8 Finishing Component Replacement 4.8.1 Replacing the Cover 1. Place the cover on the chassis. Set the cover down so that it hangs over the rear of the server module by about an inch (2.5 mm). 2. Slide the cover forward until it latches into place (FIGURE 4-16). FIGURE 4-16 4.8.2 Replacing the Cover Reinstalling the Server Module in the Chassis Caution – Hold the server module firmly so that you do not drop it. The server module weighs approximately 17 pounds (7.7 kg). 1.
■ The server module powers on with 3.3v standby power. ■ The ILOM software boots. You can either press the Power button to fully power on the server module, type the ILOM command start /SYS, command, or use the ALOM-CMT poweron command.
4-30 Sun Blade T6320 Server Module Service Manual • June 2009
APPENDIX A Specifications This appendix discusses the various specifications of the Sun Blade T6320 server module. Topics covered are: ■ Section A.1, “Physical Specifications” on page A-1 ■ Section A.2, “Motherboard Block Diagram” on page A-3 If you need specifications for the modular system chassis, see the chassis documentation. A.1 Physical Specifications TABLE A-1 Exterior Dimensions Depth Width Height Weight 19.56 in. 496.82mm 12.88 in. 327.15 mm 1.75 in. 44.5 mm 17.
FIGURE A-1 Server Module Dimensions 1.75 in. 44.5 mm 19.56 in. 496.82 mm 12.88 in. 327.15 mm A.1.1 System Environmental Specifications Operating Temperature and Altitude ■ Max Temperature at sea level: 35˚ C ■ Max Temperature at 10,000ft: 29˚ C ■ Maximum altitude: 10,000 ft. Non-Operating Temperature and Altitude A-2 ■ Temperature: -40˚ C to 60˚ C ■ Maximum altitude: 40,000 ft.
A.
A-4 Sun Blade T6320 Server Module Service Manual • June 2009
APPENDIX B Creating a Bootable Array With the Sun Blade RAID 5 Expansion Module As an installation option, you can choose to create a bootable array (bootable logical drive) and then install the Solaris operating system and the HBA driver onto that array (logical drive). This chapter describes how to set the Sun Blade T6320 to be the boot controller, and how to create a bootable array on a SPARC system. Note – This appendix assumes that you are experienced with Solaris network installs.
B.1 About Creating a Bootable Array on a SPARC System These instructions describe how to use the Sun Blade RAID 5 Expansion Module to create boot disks for a SPARC system that will run the Solaris 10 OS with a network install server. Instructions for creating a bootable array with just the Live CD and no install server are also included. Creating a bootable array using an install server is suggested for larger sites.
5. Obtain the following packages from the Live CD or from http://support.intel.com/support/go/sunraid.htm,and copy them into a working directory on the install server: ■ SUNWaac ■ StorMan ■ SUNWgccruntime Note – When you copy these packages to a working directory, ensure that you use the recursive copy command (cp -r). The packages are structured in a directory/file system format, so you need to copy the entire contents. 6.
■ StorMan - The Sun StorageTek SAS RAID Internal HBA utilities package, which contains the command-line interface and Sun StorageTek RAID Manager GUI. For information about obtaining these packages, see “Creating a Bootable Array Task Map” on page 2. ▼ To Modify the Miniroot Directory The examples in this procedure use install_dir_path to refer to the location where the network install image is located.
Note – In the following example, the -R flag is directing the pkgadd command to use an alternate root so that the packages will be installed correctly onto the miniroot image. When you substitute your own directory path for install_dir_path, be sure to begin with a / to provide an absolute path name. Also note that -d. (dash d dot) syntax before the package names. # pkgadd -R install_dir_path/Solaris_10/Tools/Boot -d. SUNWaac # pkgadd -R install_dir_path/Solaris_10/Tools/Boot -d.
The cp command places the package on a network-mounted directory that will be available to the install client. However, the command does not install the package. Installing the package is a manual step that you will perform after the installation of other Solaris software. B.5 Building a Logical Drive On Which to Install the Solaris OS Before you can install the Solaris OS, you need to build the logical drive (array) on which to install it.
3. At the system prompt, access the command-line interface (CLI), and use the ./arcconf GETCONFIG command to print a list of the complete configuration of card 1 on the system. In the following example, note that the CLI is located in the /opt/StorMan directory, and the name of the CLI is aarconf. All commands must start with ./ unless you have altered the path to include /opt/StorMan in it. # cd /opt/StorMan # .
■ Bringing the drive online These tasks are covered in the Solaris OS administration documentation. For additional drive verification, use SunVTS. Refer to the SunVTS and Solaris documentation at http://docs.sun.com for details. ▼ To Create a Logical Drive Without a Network Install Server Note – This procedure is supported on Sun Blade T6320 Server Modules released after July 2009. For Sun Blade T6320 Server Modules released before July 2009, an external CDROM device with a USB connection is required. 1.
Note – Ignore any “failing to write to log files” messages that might be displayed after running the command. The command will run successfully and will provide a list of physical disks, card status, and logical disks. The list might be long if you have many physical disks. 7. Create a logical drive on the REM, using RAID 5 and all space on disks 0,2 0,3 and 0,4. Run the CREATE command as shown in the following example. # .
● To delete a logical drive on the REM, use the DELETE card-number LOGICALDRIVE drive-number command. In this example, x is the number of the logical drive that you want to delete. # ./arcconf DELETE 1 LOGICALDRIVE x ▼ To Label the Newly Created Logical Drive Before the Solaris OS can install software onto the newly created logical drive, you must label the drive. 1. Use the ./arcconf GETCONFIG card-number LD command to display the logical drives on the REM. # ./arcconf GETCONFIG 1 LD 2.
# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 /pci@780/pci@0/pci@9/scsi@0/sd@0,0 1. c0t1d0 /pci@780/pci@0/pci@9/scsi@0/sd@1,0 2. c2t0d0 /pci@7c0/pci@0/pci@8/scsi@0/sd@0,0 3. c2t1d0 /pci@7c0/pci@0/pci@8/scsi@0/sd@1,0 Specify disk (enter its number): 2 4.
B.6.1 Additional Information For more information, refer to the following documents at: http://docs.sun.com/app/docs/coll/dsk-cntrl ■ Uniform Command-Line Interface User’s Guide, 820-2145 ■ Sun StorageTek RAID Manager Software User’s Guide, 820-1177 ■ Sun StorageTek RAID Manager Software Release Notes, 820-2755 ■ Sun StorageTek SAS RAID HBA Installation Guide Eight-Port, Internal HBA http://docs.sun.
APPENDIX C Installing the Solaris OS and the RAID 5 Expansion Module Driver If you chose to create a bootable array as part of your installation (see Appendix B), you can install the Solaris operating system (OS) and the REM driver on that bootable array. This appendix explains how to install the Solaris OS onto a bootable array (logical drive) and then install the REM driver on the array (logical drive). Note – This appendix assumes you are experienced with Solaris network installs. Topics include: C.
Note – For up-to-date Sun StorageTek SAS RAID HBA support, go to http://support.intel.com/support/go/sunraid.htm. C.2 Installing the RAID 5 Expansion Module Driver With the Solaris OS This section contains the following subsection: ■ “To Install the RAID 5 Expansion Module Driver With the Solaris OS” on page 2 ▼ To Install the RAID 5 Expansion Module Driver With the Solaris OS 1.
■ The logical drive onto which you need to place the driver package is mounted on /a. /a is the standard Solaris mount point for the disk on which the OS is being installed. 4. If the product install directory and the logical drive are not mounted, manually mount them. Note – With this example, you must substitute the correct host names, directory paths, and device paths in your environment.
C.3 Next Steps You can optionally install and use the Sun StorageTek RAID Manager GUI to create arrays on the disk enclosure. See the Sun StorageTek RAID Manager User’s Guide at: http://docs.sun.com/app/docs/prod/stortek.raid.hba C.3.1 Additional Information For more information, refer to the following documents at: http://docs.sun.
APPENDIX D XVR-50 Graphics Accelerator This appendix discusses the XVR-50 Graphics Accelerator Topics covered are: D.1 ■ Section D.1, “Features” on page D-1 ■ Section D.2, “Video Formats” on page D-2 ■ Section D.3, “Sun OpenGL for Solaris Software” on page D-3 ■ Section D.4, “Man Pages” on page D-3 ■ Section D.5, “Optional Video Output” on page D-4 ■ Section D.6, “Default Color Depth” on page D-4 ■ Section D.7, “Checking Device Configuration” on page D-5 ■ Section D.
D.2 Video Formats TABLE D-1 lists the monitor video formats supported by the XVR-50 graphics accelerator. ● To get a list of available screen resolutions for your display device, type: host% fbconfig -res \? If you have selected a resolution where support for this resolution cannot be verified, fbconfig displays the following output: SUNWpfb_config: Cannot verify that selected resolution is a supported video resolution for this monitor TABLE D-1 lists video formats supported by the HD15 port.
Note – The XVR-50 graphics accelerator video composite sync is an XOR composite sync. Note – Not all resolutions are supported by all monitors. Using resolutions that are not supported by the monitor may damage the monitor. Please refer to your monitor manuals for supported resolutions. The default resolution is dictated either by EDID information from the connected monitor or by the console resolution that is set (see TABLE D-1).
Type the fbconfig -help option to display the attributes and parameters information of the man page. host% fbconfig -dev pfb0 -help ● To access the fbconfig man page, type: host% man fbconfig ● To access the XVR-50 graphics accelerator man page, type: host% man SUNWpfb_config D.5 Optional Video Output The default system uses a resolution suggested by the monitor as long as the monitor is connected to power and connected to the XVR-50 video port.
To set 8 or 24 as the default color depth, type /usr/sbin/svccfg. /usr/sbin/svccfg -s x11-server setprop options/default_depth=8 /usr/sbin/svccfg -s x11-server setprop options/default_depth=24 The default color depth is 24. 2. Log out and then log back in for the change to take effect. D.7 Checking Device Configuration Type fbconfig to check the X window system (-propt) and XVR-50 graphics accelerator (-prconf) device configuration values.
fbconfig -prconf option displays the current XVR-50 graphics accelerator device configuration (see below for an example). If certain values differ from those displayed in -propt, it is because those values have been configured since the X window system started.
Index A advanced ECC technology, 2-11 Advanced Lights Out Management (ALOM) CMT and POST, 2-32 antistatic mat, 4-3 antistatic wrist strap, 4-2 architecture designation, 1-6 ASR blacklist, 2-49 asrkeys, 2-50 asrkeys, 2-49 Automatic System Recovery (ASR), 2-48 B battery, service processor FRU name, 1-7 replacing, 4-18 blacklist, ASR, 2-49 button Locator, 4-6 Power, 2-15 C cfgadm command, 3-2, 3-5 chassis illustration, 1-2 reinstalling server, 4-28 chipkill, 2-11 clear_fault command, 2-47 clear_fault_action
DIMMs, 1-8 example POST error output, 2-38 installation rules, 2-8 interleaving, 2-8 replacing, 4-14 troubleshooting, 2-11 disabled component, 2-50 disabling components with ILOM, 2-49 disk configuration RAID, 1-10 striping, 1-10 disk drives see hard drives displaying FRU status, 2-27 dmesg command, 2-48 Drive Ready to Remove LED, 2-14 dynamic FRU and ALOM, 2-27 E EEPROM, system configuration, 4-16 electrostatic discharge (ESD) prevention, 4-2 enablecomponent command, 2-41, 2-49 enabling components with IL
L latch release button, hard drive, 3-3 LEDs descriptions, 2-12, 2-14 Ethernet port (chassis), 2-16 OK, 2-5 system, interpreting, 2-12 locating the server for maintenance, 4-6 locating the server module, 2-14 Locator LED, 4-6 log files, viewing, 2-48 M MAC address label, 1-11 man pages, D-3 fbconfig, D-3 SUNWpfb_config, D-3, D-4 memory configuration, 2-7 fault handling, 2-7 overview, 1-5 message ID, 2-42, 2-44 messages file, 2-47 mirrored disk, 1-10 MSG-ID, online, 1-14, 2-43 N NVRAM, system controller PR
reset /SYS command, 2-38 reset button, 2-15 resolutions, D-2 S safety information, 4-1 safety symbols, 4-2 screen resolutions, D-2 serial number finding, 1-11 server module, 1-11 server module locating, 2-14 serial number, 1-11 specifications, A-1 Service Action Required LED, 2-14, 2-16, 2-41 service information resources, 1-14 service mode, 2-31 service processor battery, 4-18 description, 1-7 service processor and ILOM, 2-2 service resources, 1-14 set /HOST/diag command and POST, 2-21 set /SP/clock datet
actions, 2-5 DIMMs, 2-11 U UltraSPARC T1 processor and PSH, 2-43 universal connector port features, 1-6 Universal Unique Identifier (UUID), 2-42, 2-44 V video formats, HD15, D-2 video, Sun XVR-50, D-1 voltage and current sensor status, displaying, 2-24 W web interface and ILOM, 2-18 Index-5
Index-6 Sun Blade T6320 Server Module Service Manual • June 2009
