Sun Netra™ CP3260 Blade Server User’s Guide Sun Microsystems, Inc. www.sun.com Part No. 820-0457-11 April 2009, Revision 01 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. This distribution may include materials developed by third parties. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.
Contents Preface 1. xiii Introduction 1.1 Overview 1.2 Features 1.3 System Configurations 1.4 Advanced Rear Transition Modules 1.5 Hot-Swap Support 1.6 System Requirements and Options 1.7 1–1 1–2 1–8 1–11 1–14 1–14 1.6.1 Hardware Requirements and Options 1.6.2 Software Requirements 1–15 Part Number, Serial Number, and Revision Number Identification 1–16 Hardware Installation 2–1 2.1 Equipment and Operator Safety 2.2 Materials and Tools Required 2–3 2.
2.4 Installation Procedure Summary 2.5 Configuring On-Board Hardware 2.5.1 3. 4. iv 2–4 2–5 Adding or Replacing FB-DIMM Memory Modules 2.5.1.1 To Remove FB-DIMM Memory Modules 2.5.1.2 To Install FB-DIMM Memory Modules 2.5.2 Adding or Replacing Compact Flash Card 2.5.3 Adding or Replacing TOD Clock Battery 2–10 2–11 2–13 2–14 2.6 Installing an Advanced Rear Transition Module (Optional) 2.7 Installing the Netra CP3260 Blade Server 2.8 Connecting External I/O Cables 2.
4.3 OpenBoot Firmware 4.3.1 Getting to the ok Prompt 4.3.2 Auto-Boot Options 4.3.3 OpenBoot Commands 4.3.4 4–6 4–6 probe-scsi and probe-scsi-all Commands 4.3.3.2 probe-ide Command 4–8 4.3.3.3 show-devs Command 4–8 4.3.3.4 Using watch-net and watch-net-all Commands to Check the Network 4–11 OpenBoot Configuration Variables Error Handling Summary 4.5 Automatic System Recovery 4–16 Enabling and Disabling Automatic System Recovery 4.5.1.1 To Enable Automatic System Recovery 4.5.1.
5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 UltraSPARC T2 Processor 5–4 5.2.1.1 Electronic Fuse 5–7 5.2.1.2 Cores 5.2.1.3 L2 Cache 5.2.1.4 Memory Controller 5.2.1.5 I/O Interface Memory Subsystem 5–8 5–9 Memory Capacity 5.2.2.2 Memory Speed I/O Subsystem 5–9 5–9 5–9 5.2.3.1 PCI Express Switch 5.2.3.2 Base Interface 5.2.3.3 Fabric Interface 5.2.3.4 Common ARTM Other ARTM Interfaces 5–10 5–10 5–10 5–10 5–11 5.2.4.1 Serial Ports 5.2.4.
5.2.8.4 ATCA Hot-Swap Latch 5.2.8.5 LEDs 5.2.8.6 Power Control 5.2.8.7 System Monitor (ADM1026) and Thresholds 5.2.8.8 FRUID PROMs 5–15 5.2.10 ATCA Power Module (−48V to 12V) 5.2.11 TOD Clock Battery Form Factor A.2 Layout A.3 Front Panel 5–17 5–18 5–18 A–1 A–1 A–1 A–3 A.3.1 Visual Indicators A.3.2 Ports A–3 A–3 Connectors and Pinout A.4.1 5–15 5–17 I/O Subsystem Resets A.1 A.4 5–15 5.2.9 A. Physical Characteristics 5–14 A–3 Front Panel Connectors A–3 A.4.1.
B.3 Solaris OS Graceful Shutdown Commands B.
Figures FIGURE 1-1 Netra CP3260 Blade Server Front Panel 1–4 FIGURE 1-2 Netra CP3260 Blade Server (Top View) 1–5 FIGURE 1-3 Netra CP3260 Blade Server in an ATCA Shelf Enclosure FIGURE 1-4 Netra CP3260 Blade Server, Midplane, and Netra CP32x0 ARTM FIGURE 1-5 Netra CP3260 Blade Server Barcode Labeling FIGURE 2-1 FB-DIMM Memory Locations FIGURE 2-2 Removing an FB-DIMM Memory Module FIGURE 2-3 Installing a FB-DIMM Memory Module FIGURE 2-4 Compact Flash Card Location FIGURE 2-5 TOD Battery
FIGURE A-5 Power Distribution Connector (Zone 1) P10 FIGURE A-6 Zone 2 Connectors FIGURE A-7 Zone 3 Signal Connectors FIGURE A-8 Zone 3 Power Connector FIGURE A-9 TOD Battery Location x A–9 A–10 A–12 A–14 Netra CP3260 Blade Server User’s Guide • April 2009 A–7
Tables TABLE 1-1 Netra CP3260 Blade Server Feature Summary 1–2 TABLE 1-2 I/O Configurations TABLE 2-1 Ethernet Device Names TABLE 3-1 Local Network Information TABLE 4-1 Ways of Accessing the ok Prompt 4–5 TABLE 4-2 OpenBoot Configuration Variables 4–12 TABLE 4-3 Network Device Aliases TABLE 4-4 PICL Frutree Entries and Description for the Netra CP3260 Board TABLE 5-1 Voltage Sensor Thresholds TABLE 5-2 CPU Temperature Alarms TABLE A-1 Ethernet Port Connector Pin Assignments TABLE
TABLE B-1 Get Version Command Data Bytes TABLE B-2 Get RTM Status Command Data Bytes TABLE 1 Solaris OS Graceful Shutdown Parameters in /etc/fsmd.
Preface The Sun Netra CP3260 Blade Server User’s Guide provides information about features, installation, configuration, functional hardware components, and physical properties of this blade server. The Sun Netra CP3260 Blade Server User’s Guide is written for system integration engineers, field applications and service engineers, and others involved in the integration of these blade servers into systems. How This Document Is Organized Chapter 1 provides an overview of the Sun Netra™ CP3260 blade server.
Using UNIX Commands This document might not contain information on basic UNIX® commands and procedures such as shutting down the system, booting the system, and configuring devices. Refer to the following for this information: ■ Software documentation that you received with your system ■ Solaris™ Operating System documentation, which is at: http://docs.sun.
Typographic Conventions Typeface Meaning Examples AaBbCc123 The names of commands, files, and directories; on-screen computer output Edit your.login file. Use 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.
Application Title Part Number Format Location Installation and Configuration Sun Netra CP32x0 SAS Storage Advanced Rear Transition Module, Dual HD User’s Guide 820-3147 PDF, HTML Online http://docs.sun.com/app/docs/prod/cp32x0.sas#hic Installation and Configuration Sun Netra™ CP32x0 Quad GbE, Dual Fibre Channel, Advanced Rear Transition Module, User’s Guide 820-3148 PDF, HTML Online http://docs.sun.com/app/docs/prod/cp32x0.
or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources. Sun Welcomes Your Comments Sun is interested in improving its documentation and welcomes your comments and suggestions. You can submit your comments by going to: http://www.sun.
xviii Sun Netra CP3260 Blade Server User’s Guide • April 2009
1-C HR APTE CHAPTER Introduction This chapter contains the following sections: 1.1 ■ Section 1.1, “Overview” on page 1-1 ■ Section 1.2, “Features” on page 1-2 ■ Section 1.3, “System Configurations” on page 1-8 ■ Section 1.5, “Hot-Swap Support” on page 1-14 ■ Section 1.6, “System Requirements and Options” on page 1-14 ■ Section 1.
■ Elimination of PCI connectivity between the blade servers in the system and reallocation of connectivity to serial interconnects, eliminating single points of failure ■ Mandatory use of Intelligent Platform Management Interface (IPMI) management interfaces ■ Flexible user I/O ■ Power and thermal management guidelines enforced by the management infrastructure ■ Separation of control and data traffic by supporting the Base (PICMG 3.0) and Fabric (PICMG 3.
TABLE 1-1 Netra CP3260 Blade Server Feature Summary Feature Description PICMG compliance • • • • • • Node board support Functions as a CPU node board with the Solaris operating system and software packages Operating system Solaris 10 8/07 OS and subsequent compatible versions with supported Netra patches Internal I/O (connections to ATCA midplane) • Dual 10/100/1000BASE-T Ethernet for Base interfaces • 10-Gb XAUI or 1-Gb SERDES Ethernet interfaces as Fabric interfaces • Dual IPMI channel connects
FIGURE 1-1 1-4 Netra CP3260 Blade Server Front Panel Netra CP3260 Blade Server User’s Guide • April 2009
FIGURE 1-2 Netra CP3260 Blade Server (Top View) Chapter 1 Introduction 1-5
⑤ ④ ③ ② ① ⑦ 1-6 Netra CP3260 Blade Server User’s Guide • April 2009
Figure Legend 1 Top latch 2 Out of Service LED (yellow) 3 Ethernet management port (RJ-45) 4 OK LED (green) 5 Dual USB Ports (USB 2.
Figure Legend 1.3 5 Compact Flash connector 6 UltraSPARC T2 processor (under heat sink) 7 FB-DIMMs System Configurations Netra CP3260 blade servers can be installed in an ATCA shelf (or chassis), as shown in FIGURE 1-3. The blade servers can be deployed in various electrical configurations to suit each end-user requirement.
FIGURE 1-3 Netra CP3260 Blade Server in an ATCA Shelf Enclosure Chapter 1 Introduction 1-9
① ② ③ ④ Ethernet ⑤ ⑥ ⑦ Diskless client that boots through network from a remote server 1-10 Netra CP3260 Blade Server User’s Guide • April 2009
Figure Legend 1.4 1 Remote server 2 Sun Netra CP32X0 Advanced RTM (installed from rear) 3 Serial connection 4 Console terminal 5 Ethernet connection (RJ-45) 6 Sun Netra CP3260 blade server (installed from front) 7 Netra CT 900 server ATCA shelf Advanced Rear Transition Modules An optional Sun Netra CP32X0 Advanced Rear Transition Module (ARTM) can be installed into the rear of the ATCA enclosure, opposite the Netra CP3260 blade server (FIGURE 1-3).
FIGURE 1-4 Netra CP3260 Blade Server, Midplane, and Netra CP32x0 ARTM ① ② ③ 1-12 Netra CP3260 Blade Server User’s Guide • April 2009
Figure Legend 1 Sun Netra CP3260 blade server 2 Sun Netra CP32X0 ARTM 3 ATCA chassis midplane Note – When a Netra CP32x0 ARTM is used with the Netra CP3260 blade server, shielded cables are required for serial I/O ports. Unshielded cables can be used on Ethernet ports to satisfy EMI compliance standards. The shields for all shielded cables must be terminated on both ends. The customer can order a Netra CP32x0 ARTM, build a custom card, or buy from an independent hardware vendor (IHV).
1.5 Hot-Swap Support There are three hot-swap models described in the PICMG ATCA specification: basic hot-swap, full hot-swap, and high-availability (HA) hot-swap. Refer to the PICMG ATCA Specification, which provides a detailed description of this subject. The Netra CP3260 blade server supports basic hot-swap. The hot-swap process uses hardware connection control to disconnect and connect the hardware in an orderly sequence. 1.
■ Serial terminal or terminal emulation for console output. ■ Cables for terminal and network connections. ■ Optional AMC disks and PCI-E cards. The following are ATCA and other minimum requirements met by the Netra CP3260 blade server. 1.6.
1.7.1 Part Number, Serial Number, and Revision Number Identification The Netra CP3260 blade server part number, serial number, and revision can be found on labels located on the card (FIGURE 1-5).
FIGURE 1-5 Netra CP3260 Blade Server Barcode Labeling Note – You might find the labels shown in FIGURE 1-5 on other locations on your blade server. Your particular blade server configuration might also appear different than the illustration.
1-18 Netra CP3260 Blade Server User’s Guide • April 2009
2-C HR APTE CHAPTER Hardware Installation This chapter describes the hardware installation procedures for the Netra CP3260 blade server, and contains the following sections: 2.1 ■ Section 2.1, “Equipment and Operator Safety” on page 2-1 ■ Section 2.2, “Materials and Tools Required” on page 2-3 ■ Section 2.3, “Preparing for the Installation” on page 2-3 ■ Section 2.4, “Installation Procedure Summary” on page 2-4 ■ Section 2.5, “Configuring On-Board Hardware” on page 2-5 ■ Section 2.
The installer must be familiar with commonly accepted procedures for integrating electronic systems and with the general practice of Sun systems integration and administration. Although parts of these systems are designed for hot-swap operation, other components must not be subjected to such stresses. Work with power connected to a chassis only when necessary, and follow these installation procedures to avoid equipment damage.
2.2 Materials and Tools Required This section provides information on the materials and tools required to perform installation. The minimum tools required to perform installation are: ■ Phillips screwdrivers, No. 1, No. 2 (optional) ■ Antistatic wrist strap ■ Terminal console See Section 1.6.1, “Hardware Requirements and Options” on page 1-14 for information on hardware requirements. 2.3 Preparing for the Installation Prepare for installation by reading and performing the following steps: 1.
2.4 ■ Facility power loading specifications can support the rack or enclosure requirements. ■ Your enclosure specifications support the cooling airflow requirements. The Netra CP3260 blade server fits a standard ATCA shelf or chassis. If your installation requirements are different, contact your field application engineer. Installation Procedure Summary The procedure in this section summarizes the Netra CP3260 blade server installation at a high level. Be sure to read the details in Section 2.
2.5 Configuring On-Board Hardware This section provides the procedures for adding or replacing the on-board hardware components such as memory modules, a Compact Flash card, and the time-of day (TOD) battery. Read and perform the procedures, as necessary, before installing the Netra CP3260 blade server into the chassis. 2.5.1 Adding or Replacing FB-DIMM Memory Modules The Netra CP3260 blade server supports a total of 8 FB-DIMMs and a maximum memory capacity of 16 Gbytes (using eight 2-Gbyte DIMMs).
FIGURE 2-1 2-6 FB-DIMM Memory Locations Netra CP3260 Blade Server User’s Guide • April 2009
Chapter 2 Hardware Installation 2-7
2-8 Netra CP3260 Blade Server User’s Guide • April 2009 ① ②③ ④ ⑤ ⑥ ⑦ ⑧
Figure Legend 1 FB0B 2 FB0A 3 FB1B 4 FB1A DIMM Pair 0 5 FB2A 6 FB2B DIMM Pair 1 7 FB3A 8 FB3B DIMM Pair 2 DIMM Pair 3 Chapter 2 Hardware Installation 2-9
2.5.1.1 To Remove FB-DIMM Memory Modules You might need to remove a FB-DIMM module from the Netra CP3260 blade server if you are returning the FB-DIMM module or the blade server for service, or if you are replacing a module with another FB-DIMM module. Note – Safely store the original factory-shipped FB-DIMM and related FB-DIMM packaging. You might wish to store any removed FB-DIMM in the new FB-DIMM packaging, or use the packaging for service.
FIGURE 2-2 Removing an FB-DIMM Memory Module 6. If you are replacing the module you removed with a new FB-DIMM, install it as described in Section 2.5.1.2, “To Install FB-DIMM Memory Modules” on page 2-11. 2.5.1.2 To Install FB-DIMM Memory Modules The following procedure provides a general guide for installing additional memory. However, for directions on the installation process of the memory FB-DIMMs on the Netra CP3260 blade server, refer to the documentation that shipped with the memory module.
1. Locate the FB-DIMM connectors on the Netra CP3260 blade server. Select the connectors where you will install the memory module (FIGURE 2-1). If you need to replace an existing memory module with a new module, see Section 2.5.1.1, “To Remove FB-DIMM Memory Modules” on page 2-10 for instructions on removing the FB-DIMM module. 2. Remove the FB-DIMM from its protective packaging, holding the module only by the edges. 3.
4. Press the top edge of the FB-DIMM toward the blade server until the retainer clips click into place (see ➋ in FIGURE 2-3). The small retainer clips on each side of the FB-DIMM slot click into place in the notches on the sides of the FB-DIMM. 2.5.2 Adding or Replacing Compact Flash Card You can install an optional Sun Compact Flash card on the Netra CP3260 blade server. The Compact Flash card is not hot-swappable and there is no access to the card once the blade server is installed in an ATCA chassis.
FIGURE 2-4 Compact Flash Card Location ① Figure Legend 1 2.5.3 Compact Flash connector Adding or Replacing TOD Clock Battery FIGURE 2-5 shows the location of the TOD clock battery and holder. The optional TOD battery must be type CR1632, with a minimum of 4ma abnormal charging current rating (for example; a Renata CR1632).
Caution – Risk of explosion if the battery is replaced by an incorrect type. Dispose of batteries properly in accordance with manufacturer’s instructions and local regulations. To install the battery, perform the following steps: 1. Remove the FB-DIMM closest to the front panel. To do this, see Section 2.5.1.1, “To Remove FB-DIMM Memory Modules” on page 2-10. 2. (Optional) Remove the old battery if necessary. 3. Slide the new battery into the holder with the side labeled “+ “ facing up. 4.
FIGURE 2-5 2-16 TOD Battery Location Netra CP3260 Blade Server User’s Guide • April 2009
① ② ③ Chapter 2 Hardware Installation 2-17
Figure Legend 2.6 1 TOD battery location 2 Remove this FB-DIMM for access to battery 3 TOD clock battery location with FB-DIMM removed Installing an Advanced Rear Transition Module (Optional) For rear I/O access, a compatible RTM must be used with the Netra CP3260 blade server. Note – If you are using a Netra CP32x0 ARTM, refer to the appropriate Netra CP32x0 ARTM User’s Guide for specific installation instructions. In general, install the RTM from the rear of the server.
FIGURE 2-6 Installing a Netra CP32X0 ARTM ② ① ③ Figure Legend 1 Netra CP3260 blade server 2 Netra CP32X0 ARTM 3 ATCA chassis midplane Chapter 2 Hardware Installation 2-19
2.7 Installing the Netra CP3260 Blade Server Caution – The Netra CT 900 server fan tray upgrade kit (594-4953) must be installed in the chassis before the Netra CP3260 blade server is installed. This fan tray upgrade is required to provide adequate cooling and to prevent the system from overheating or shutting down due to an over-temperature condition that can occur with the older fan trays.
FIGURE 2-7 Installing Blade Server Into Chassis Slot 6. Push the blade server slightly into the midplane connectors, and then close the latches to seat the blade server in the connectors (FIGURE 2-8). 7. When the lower latch is closed, the blue Hot-Swap LED blinks while the blade server is initializing. The blue LED turns off and the green OK LED lights when the blade server is ready. 8. Tighten the locking screws to ensure the blade server is secured into the shelf (FIGURE 2-8).
FIGURE 2-8 2.8 Netra CP3260 Blade Server Latches and Locking Screws Connecting External I/O Cables External I/O cables are connected to the Netra CP3260 blade server, or to the Netra CP32x0 ARTM when a rear transition module is used.
Note – Shielded cables are required for serial I/O ports. Unshielded cables can be used on Ethernet ports to satisfy EMI compliance standards. The shields for all shielded cables must be terminated on both ends. Information on connecting each of these cables follows: ■ For Ethernet connections, category 5e or better network cable is required. One end of the Ethernet cable is connected to a suitable 10/100/1000BASE-T switch and the other end to one of the Ethernet ports on the Netra CP3260 blade server.
2.9 Hot-Swapping the Netra CP3260 Blade Server The Netra CP3260 blade server supports hot-swapping at the blade server level. Note – Before hot-swapping the blade server, the system administrator should gracefully shutdown the applications and operating system, and deactivate the blade server. After the blade server is replaced, the system administrator should activate the new blade server.
FIGURE 2-9 Hot-Swap Latch and Hot-Swap LED Chapter 2 Hardware Installation 2-25
2-26 Netra CP3260 Blade Server User’s Guide • April 2009
3-C HR APTE CHAPTER Software Installation This chapter contains the following sections: 3.1 ■ Section 3.1, “Operating Systems and Patches” on page 3-1 ■ Section 3.2, “Configuring Payload OS NIU Driver for Multiplexing to Zones 2 and 3” on page 3-2 ■ Section 3.3, “Installing as a Diskless Clients” on page 3-4 ■ Section 3.4, “Firmware Updates” on page 3-8 ■ Section 3.5, “Configuring for 1-GbE or 10-GbE Switches” on page 3-8 ■ Section 3.
Depending the blade server’s hardware configuration, the Sun Netra CP3260 blade server can be used as a diskless client with the Solaris OS installed on a boot server (see Section 3.3, “Installing as a Diskless Clients” on page 3-4. The OS can also be downloaded to a boot device like the Netra CP32x0 SAS Storage ARTM, Dual HD, or an optional Compact Flash. 3.
CODE EXAMPLE 3-3 Zone 2 and Zone 3 Connectivity: First NIU Port (nxge0) to Zone 2 (at 10Gbps Speed) and the Second NIU Port (nxge1) to Zone3 name = "SUNW,niusl" parent = "/niu@80" unit-address = "0" phy-type = "xgsd"; name = "SUNW,niusl" parent = "/niu@80" unit-address = "1" phy-type = "xgf"; CODE EXAMPLE 3-4 Zone 2 and Zone 3 Connectivity: First NIU Port (nxge0) to Zone 3 (at 10Gbps Speed) and the Second NIU Port (nxge1) to Zone2 name = "SUNW,niusl" parent = "/niu@80" unit-address = "0" phy-type = "xg
3.3 Installing as a Diskless Clients The following procedures describe how to create a boot server for diskless clients and how to add new diskless clients to the patched boot server. For additional instructions on installing diskless clients, refer to the appropriate Solaris Documentation Collection at the Sun Documentation web site at: http://docs.sun.com/app/docs/prod/solaris You must have a superuser password on your diskless server to perform the tasks in the following sections. 3.3.
■ locale is the locale that you want to use ■ \ (backslash) is a line-continuation character indicating that the command is continued on the next line. Refer to the smosservice(1M) man page for more information and options. For example: # ./smosservice add -u root -p root_password -- -x mediapath=/export/install \ -x platform=sparc.sun4v.
4. Change directories to the /usr/sadm/bin directory. # cd /usr/sadm/bin 5. Set up the diskless clients. For each diskless client, type the following command as superuser: # ./smdiskless add -- -i ip_address -e ethernet_address -n host_name \ -x os=sparc.sun4v.
■ time_zone = US/Pacific ■ locale = en_US ■ name_service = NIS ■ name_server = nameserver_host ■ \ (backslash) is a line continuation character indicating that the command is continued on the next line. You must type your superuser password again after typing this command. The installation process should take roughly 5 minutes per client and about 15-30 minutes for the operating environment service to install; however, no progress is displayed on screen while the process is running.
TABLE 3-1 Local Network Information Information Needed Your Information Gateway router IP address NFS server names and IP addresses Web server URL * Local IP addresses are not needed if they are assigned by a network DHCP server. You might need the MAC (Ethernet) addresses of the local hosts to make nameserver database entries. The MAC address can be seen in the console output while booting to the ok prompt. It can also be derived from the host ID seen on the barcode label (see Section 1.7.
The NIU (Network Interface Unit) driver configuration file, nxge.conf, might need to be modified to employ the proper port configurations. The nxge.conf file is located in the /platform/sun4v/kernel/drv directory. The following examples show the proper entries for each switch configuration. These entries are additional to any other configuration parameters set in the nxge.conf file. Example 1: If Sun Netra CP3240 10-GbE switches are used in Slot 7 and Slot 8, the nxge.
SunVTS software is used to validate a system during development, production, inspection, troubleshooting, periodic maintenance, and system or subsystem stressing. SunVTS software can be tailored to run on machines ranging from desktops to servers with modifiable test instances and processor affinity features. You can perform high-level system testing by using the appropriate version of SunVTS software.
4-C HR APTE CHAPTER Firmware and Blade Server Management This chapter contains the following sections: ■ Section 4.1, “System Firmware” on page 4-2 ■ Section 4.2, “Power-On Self-Test Diagnostics” on page 4-3 ■ Section 4.3, “OpenBoot Firmware” on page 4-4 ■ Section 4.4, “Error Handling Summary” on page 4-15 ■ Section 4.5, “Automatic System Recovery” on page 4-16 ■ Section 4.6, “Network Device Aliases” on page 4-18 ■ Section 4.7, “Retrieving Device Information” on page 4-19 ■ Section 4.
4.1 System Firmware The Netra CP3260 blade server contains a modular firmware architecture that gives you latitude in controlling boot initialization. You can customize the initialization, test the firmware, and even enable the installation of a custom operating system. This platform also employs the Intelligent Platform Management Controller (IPMC)—described in Section 5.2.
4.2 Power-On Self-Test Diagnostics Power-on self-test (POST) is a firmware program that helps determine whether a portion of the system has failed. POST verifies the core functionality of the system, including the CPU modules, motherboard, memory, and some on-board I/O devices. The software then generates messages that can be useful in determining the nature of a hardware failure. POST can run even if the system is unable to boot.
4.2.2 POST Diagnostic and Error Message Format POST diagnostic and error messages are displayed on a console.
4.3.1 ■ When the operating system crashes, the system reverts to OpenBoot firmware control. ■ During the boot process, when there is a serious hardware problem that prevents the operating system from running, the system reverts to OpenBoot firmware control. ■ When a serious hardware problem develops while the system is running, the operating system transitions smoothly to run level 0.
4.3.2 Auto-Boot Options The system firmware stores a configuration variable called auto-boot?, which controls whether the firmware will automatically boot the operating system after each reset. The default setting for Sun platforms is true. Normally, if a system fails power-on diagnostics, auto-boot? is ignored and the system does not boot unless an operator boots the system manually. An automatic boot is generally not acceptable for booting a system in a degraded state.
4.3.3.1 probe-scsi and probe-scsi-all Commands The probe-scsi and probe-scsi-all commands diagnose problems with the SCSI devices. Caution – If you used the halt command or the Stop-A key sequence to reach the ok prompt, issuing the probe-scsi or probe-scsi-all command can hang the system. The probe-scsi command communicates with all SCSI devices connected to on-board SCSI controllers. The probe-scsi-all command also accesses devices connected to any host adapters installed in PCI slots.
4.3.3.2 probe-ide Command The probe-ide command communicates with all Integrated Drive Electronics (IDE) devices connected to the IDE bus. This is the internal system bus for media devices such as the DVD drive. Caution – If you used the halt command or the Stop-A key sequence to reach the ok prompt, issuing the probe-ide command can hang the system. The following shows sample output from the probe-ide command.
CODE EXAMPLE 4-3 show-devs Command Output /cpu@37 /cpu@36 /cpu@35 /cpu@34 /cpu@33 /cpu@32 /cpu@31 /cpu@30 /cpu@2f /cpu@2e /cpu@2d /cpu@2c /cpu@2b /cpu@2a /cpu@29 /cpu@28 /cpu@27 /cpu@26 /cpu@25 /cpu@24 /cpu@23 /cpu@22 /cpu@21 /cpu@20 /cpu@1f /cpu@1e /cpu@1d /cpu@1c /cpu@1b /cpu@1a /cpu@19 /cpu@18 /cpu@17 /cpu@16 /cpu@15 /cpu@14 /cpu@13 /cpu@12 /cpu@11 /cpu@10 /cpu@f /cpu@e /cpu@d /cpu@c /cpu@b /cpu@a /cpu@9 Chapter 4 Firmware and Blade Server Management 4-9
CODE EXAMPLE 4-3 show-devs Command Output /cpu@8 /cpu@7 /cpu@6 /cpu@5 /cpu@4 /cpu@3 /cpu@2 /cpu@1 /cpu@0 /virtual-devices@100 /virtual-memory /memory@m0,8000000 /aliases /options /openprom /chosen /packages /ebus@c0/serial@0,ca0000 /pci@0/pci@0 /pci@0/pci@0/pci@a /pci@0/pci@0/pci@9 /pci@0/pci@0/pci@8 /pci@0/pci@0/pci@2 /pci@0/pci@0/pci@1 /pci@0/pci@0/pci@a/pci@0 /pci@0/pci@0/pci@a/pci@0/usb@4,2 /pci@0/pci@0/pci@a/pci@0/usb@4,1 /pci@0/pci@0/pci@a/pci@0/usb@4 /pci@0/pci@0/pci@a/pci@0/usb@4,2/storage@2 /pci@
CODE EXAMPLE 4-3 show-devs Command Output /virtual-devices@100/channel-devices@200 /virtual-devices@100/channel-devices@200/virtual-channel-client@1 /virtual-devices@100/channel-devices@200/virtual-channel@0 /virtual-devices@100/channel-devices@200/virtual-channel-client@2 /virtual-devices@100/channel-devices@200/virtual-channel@3 /openprom/client-services /packages/obp-tftp /packages/kbd-translator /packages/SUNW,asr /packages/dropins /packages/terminal-emulator /packages/disk-label /packages/deblocker /
/pci@0/pci@0/pci@1/network@0 1000 Mbps full duplex Link up Looking for Ethernet Packets. ’.’ is a Good Packet. ’X’ is a Bad Packet. Type any key to stop. ..... {0} ok 4.3.4 OpenBoot Configuration Variables The OpenBoot configuration variables are stored in the OBP flash PROM and determine how and when OpenBoot tests are performed. This section explains how to access and modify OpenBoot configuration variables. For a list of important OpenBoot configuration variables, see TABLE 4-2.
TABLE 4-2 OpenBoot Configuration Variables Variable Possible Values Default Value Description error-reset-recovery boot, none, sync boot Specifies recovery action after an error reset. Default is boot. • none – No recovery action. • boot – System attempts to boot. • sync – Firmware attempts to execute a Solaris sync callback routine. fcode-debug? true, false false If true, include name fields for plug-in device FCodes. input-device keyboard, virtual-console Power-on input device.
OpenBoot Configuration Variables TABLE 4-2 Variable Possible Values Default Value Description security-password variable-name none Firmware security password if security-mode is not none (never displayed). Do not set this directly. ttya-mode 9600,8,n,1,- 9600,8,n,1,- Serial management port (baud rate, bits, parity, stop, handshake). The serial management port only works at the default values. use-nvramrc? true, false false If true, execute commands in NVRAMRC during server startup.
boot-device use-nvramrc? error-reset-recovery {0} ok ■ disk net false boot disk net false boot To set or change the value of an OpenBoot configuration variable, use the setenv command: {0} ok setenv error-reset-recovery none error-reset-recovery = none ■ 4.4 To set OpenBoot configuration variables that accept multiple keywords, separate keywords with a space.
4.5 ■ Any CPU failed ■ All logical memory banks failed ■ Flash RAM cyclical redundancy check (CRC) failure ■ Critical field-replaceable unit (FRU) PROM configuration data failure ■ Critical application-specific integrated circuit (ASIC) failure Automatic System Recovery Automatic system recovery (ASR) consists of self-test features and an autoconfiguration capability to detect failed hardware components and unconfigure them.
4.5.1 Enabling and Disabling Automatic System Recovery The automatic system recovery (ASR) feature is not activated until you enable it. Enabling ASR requires changing configuration variables in OpenBoot. 4.5.1.1 To Enable Automatic System Recovery 1. At the ok prompt, type: ok setenv auto-boot true ok setenv auto-boot-on-error? true 2.
After you disable the automatic system recovery (ASR) feature, it is not activated again until you re-enable it. 4.6 Network Device Aliases A device alias is a shorthand representation of a device path. The Solaris OS provides some predefined device aliases for the network devices so that you do not need to type the full device path name. TABLE 4-3 lists the network device aliases, the default Solaris OS device names, and associated ports for the Netra CP3260 blade server.
4.7 Retrieving Device Information You can use the Solaris platform information and control library (PICL) framework for obtaining the state and condition of the Netra CP3260 blade server. The PICL framework provides information about the system configuration that it maintains in the PICL tree. Within this PICL tree is a subtree named frutree, which represents the hierarchy of system field-replaceable units (FRUs) with respect to a root node in the tree called chassis.
CODE EXAMPLE 4-4 cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu 4-20 prtpicl Command Output virtual-channel-client (obp-device, 6f0000011d) n2cp (obp-device, 6f00000127) ncp (obp-device, 6f00000134) random-number-generator (obp-device, 6f00000141) flashprom (flashprom, 6f0000014d) console (serial, 6f00000154) rtc (obp-device, 6f00000161) (cpu, 6f00000169) (cpu, 6f00000177) (cpu, 6f00000185) (c
CODE EXAMPLE 4-4 prtpicl Command Output cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu pci (cpu, 6f00000399) (cpu, 6f000003a7) (cpu, 6f000003b5) (cpu, 6f000003c3) (cpu, 6f000003d1) (cpu, 6f000003df) (cpu, 6f000003ed) (cpu, 6f000003fb) (cpu, 6f00000409) (cpu, 6f00000417) (cpu, 6f00000425) (cpu, 6f00000433) (cpu, 6f00000441) (cpu, 6f0000044f) (cpu, 6f0000045d) (cpu, 6f0000046b) (cpu, 6f00000479) (cpu, 6f00000487) (cpu, 6f00000495) (cpu, 6f000004a3) (cpu, 6f0
CODE EXAMPLE 4-4 prtpicl Command Output network (network, 6f00000804) network (network, 6f00000814) os-io (console, 6f00000824) pseudo (devctl, 6f00000843) zconsnex (devctl, 6f0000084c) obp (picl, 6f0000001f) packages (packages, 6f00000034) SUNW,builtin-drivers (SUNW,builtin-drivers, 6f0000003a) deblocker (deblocker, 6f00000040) disk-label (disk-label, 6f00000047) terminal-emulator (terminal-emulator, 6f0000004d) dropins (dropins, 6f00000054) SUNW,asr (SUNW,asr, 6f0000005b) kbd-translator (kbd-translator,
CODE EXAMPLE 4-4 prtpicl Command Output L2_BANK7 (other, 6f00000cda) BR0 (other, 6f00000ce0) CH0 (other, 6f00000ce6) D0 (module, 6f00000cec) R0 (unknown, 6f00000cf7) R1 (unknown, 6f00000cfc) SEEPROM (other, 6f00000d01) PRSNT (presence-indicator, 6f00000d07) T_AMB (temperature-sensor, 6f00000d0f) CH1 (other, 6f00000d1f) D0 (module, 6f00000d25) R0 (unknown, 6f00000d30) R1 (unknown, 6f00000d35) SEEPROM (other, 6f00000d3a) PRSNT (presence-indicator, 6f00000d40) T_AMB (temperature-sensor, 6f00000d48) BR1 (other
CODE EXAMPLE 4-4 prtpicl Command Output CH0 (other, 6f00000e4e) D0 (module, 6f00000e54) R0 (unknown, 6f00000e5f) R1 (unknown, 6f00000e64) SEEPROM (other, 6f00000e69) PRSNT (presence-indicator, 6f00000e6f) T_AMB (temperature-sensor, 6f00000e77) CH1 (other, 6f00000e87) D0 (module, 6f00000e8d) R0 (unknown, 6f00000e98) R1 (unknown, 6f00000e9d) SEEPROM (other, 6f00000ea2) PRSNT (presence-indicator, 6f00000ea8) T_AMB (temperature-sensor, 6f00000eb0) CORE0 (other, 6f00000ec0) SPU (other, 6f00000ec6) FPU (other, 6
CODE EXAMPLE 4-4 prtpicl Command Output IMMU (other, 6f00000f86) DMMU (other, 6f00000f8c) CORE5 (other, 6f00000f92) SPU (other, 6f00000f98) FPU (other, 6f00000f9e) ICACHE (other, 6f00000fa4) DCACHE (other, 6f00000faa) IMMU (other, 6f00000fb0) DMMU (other, 6f00000fb6) CORE6 (other, 6f00000fbc) SPU (other, 6f00000fc2) FPU (other, 6f00000fc8) ICACHE (other, 6f00000fce) DCACHE (other, 6f00000fd4) IMMU (other, 6f00000fda) DMMU (other, 6f00000fe0) CORE7 (other, 6f00000fe6) SPU (other, 6f00000fec) FPU (other, 6f0
CODE EXAMPLE 4-4 prtpicl Command Output P24 (other, 6f000010a0) P25 (other, 6f000010a6) P26 (other, 6f000010ac) P27 (other, 6f000010b2) P28 (other, 6f000010b8) P29 (other, 6f000010be) P30 (other, 6f000010c4) P31 (other, 6f000010ca) P32 (other, 6f000010d0) P33 (other, 6f000010d6) P34 (other, 6f000010dc) P35 (other, 6f000010e2) P36 (other, 6f000010e8) P37 (other, 6f000010ee) P38 (other, 6f000010f4) P39 (other, 6f000010fa) P40 (other, 6f00001100) P41 (other, 6f00001106) P42 (other, 6f0000110c) P43 (other, 6f0
4.8 Multiplexing to Zones 2 and 3 A multiplexer (MUX) controller and ShMM configuration is available for use on Netra CP3260 blade servers to multiplex 10GbE network interface unit (NIU) ports to Zone 2 (backplane) and/or to Zone 3 (ARTM).
Be aware of the following possible issues when multiplexing zones: 4-28 ■ MUX and payload driver configuration could go out of sync, requiring a system administrator to make sure they are set to the same configuration. ■ Midplane FRUID record could be corrupted when updating with the MUX configuration. ■ Third-party shelf management software might block updates to the midplane FRUID.
CHAPTER 5 Hardware Functional Descriptions This chapter contains the following sections: 5.1 ■ Section 5.1, “Hardware Architecture” on page 5-1 ■ Section 5.2, “Hardware Modules” on page 5-4 Hardware Architecture The Netra CP3260 blade server is an ATCA node board based on the UltraSPARC T2 processor.
Netra CP3260 Blade Server Block Diagram DOC MD4832 PORT 1 X4 Console PORT 10 X4 FRONT/REAR SERIAL CONSOLE PORT 8 Midplane Zone 2 10/100/1000 MGMNT FRONT PANEL ETHERNET PCI-EXP ETHERNET USB 2,3 1 Base ETHERNET 0 XAUI XAUI_RTM SMM15 FLASH_SEL OBP/HV SP NVRAM SUNFRUID SCC_MAC I2C Selector Debug I2C H8 Serial Netconsole I2C (Netconsole) Serial Payload Dual GBE ETHERNET (Mgmnt) 1 10/100 BASE-T I2C Devices XFMR Fabric I2C Devices Dual GBE XAUI_RTM 0 TI TUSB6250 USB-IDE CF Flash
There are four on-chip memory controllers that interface directly to FB-DIMM memory and include eight FB-DIMM slots (one per channel, or two per memory controller). In addition, there are an on-chip PCI-Express I/O interface and two 10-Gb Ethernet ports. The UltraSPARC T2 processor is a highly integrated processor that implements the 64-bit SPARC V9 architecture. 5.1.2 I/O All I/O is provided via the UltraSPARC T2 PCI-Express interface. A PLX switch provides the PCI-E interfaces.
5.1.6 ARTM Support ARTM support is routed to the ARTM through the Zone 3 connectors. Typical ARTM support includes: ■ One RS-232 serial console port ■ One 10/100/100BASE-T Ethernet management port Because Netra CP32x0 Advanced RTMs (ARTM) provide additional functionality, the following interfaces are also routed to the ARTM. ■ A x8 PCI-E interface ■ Dual 10/100/1000 SERDES Ethernet channels (from Intel NIC) Power for the ARTMs is provided through the Zone 3 RTM power connector. 5.
FIGURE 5-2 UltraSPARC T2 Multicore Processor Block Diagram Chapter 5 Hardware Functional Descriptions 5-5
5-6 Netra CP3260 Blade Server User’s Guide • April 2009
1.2 GHz UltraSPARC T2 667 MHz 64 SPARC core SPARC core L2 Bank 1 L2 Bank 1 14 L2 Bank 0 TCU 10 Gb MAC 10 Gb MAC 14 MCU2 14 10 14 10 64 128 L2 Bank 1 CCU 10 64 L2 Bank 0 SPARC core 14 10 64 L2 Bank 1 SPARC core MCU1 64 128 SPARC core 10 10 L2 Bank 0 Cache Crossbar (CCX) 14 64 128 SPARC core MCU0 64 SPARC core SPARC core 10 L2 Bank 0 128 Fully buffered DIMMs (FBD) 4.0 GHz MCU3 14 10 64 14 Efuse SIU NIU Optional dual channel mode PCI-E SSI ROM I/F 5.2.1.
5.2.1.2 Cores The UltraSPARC T2 processor provides 8 physical SPARC processor cores and each physical core is capable of supporting 8 threads for a total of 64 threads. 5.2.1.3 L2 Cache The UltraSPARC T2 provides a total of 4 Mbytes of L2 cache banked 8 ways. 5.2.1.4 Memory Controller The UltraSPARC T2 supports 4 FB-DIMM memory controllers, each controller capable of supporting 2 FB-DIMM memory channels.
The XAUI interface is the Fabric interface to the ATCA midplane. The XAUI interface is routed to the Zone 2 connector on the midplane (see Section A.4, “Connectors and Pinout” on page A-3 for details on board connector pinout assignments. 5.2.2 Memory Subsystem The heart of the Memory subsystem is the FB-DIMM memory. Data from the FB-DIMM memory controller is brought out on a high-speed serial bus that connects to a single memory DIMM per channel.
5.2.3.1 PCI Express Switch The Netra CP3260 uses the PLX PCI switch that encompasses a 32-lane PCI Express switch with six configurable ports (x1, x2, x4, x8, x16). 5.2.3.2 Base Interface The Netra CP3260 provides dual redundant 10/100/1000BASE-T Ethernet links to connect to the midplane Base interface channels. A x4 lane port from the PCI Express switch connects to a dual gigabit controller. 5.2.3.
5.2.4 Other ARTM Interfaces In addition to the AMC-type interface to the ARTM, additional interfaces are routed to the ARTM to provide for rear access to the Netra CP3260 I/O. 5.2.4.1 Serial Ports The console port from the PPC is routed to the ARTM for rear access. When a serial device is connected into the ARTM’s serial port, the console data is output to that port.
Note – A serial port is also provided on the Netra CP32x0 ARTM. You can use either the serial port on the front panel or the serial port on Netra CP32x0 ARTM, but only one of the ports should be used at one time. 5.2.5.3 Dual USB Ports Dual USB ports are 2.0 compliant and routed from the USB hub to the front panel. 5.2.6 Compact Flash Socket The Netra CP3260 blade server provides a Type I/II compact flash socket for removal media.
■ H8 interface providing IPMC support. ■ MPC interface. ■ SSI Interface (UltraSPARC T2). ■ BUS Interface and Arbiter (Round Robin). ■ Bus Clock Control ■ Power sequence control of DC/DCs on board. ■ Interrupts. ■ Data Channel/Fast Mailbox Control. The FPGA configuration is performed after an FPGA reset when the configuration is downloaded from the PROM. 5.2.
5.2.8.1 ■ Environmental monitoring ■ Access to all environmental I2C devices ■ Access to all I2C devices when MPC is reset Intelligent Platform Management Bus The BMR-H8S provides dual buffered Intelligent Platform Management Bus (IPMB) interfaces to the IPMB-0 bus on the PICMG 3.0 midplane. The I2C channels on the H8S are connected the IPMB-A and IPMB-B through the I2C buffers.
5.2.8.5 LEDs The Netra CP3260 blade server supports three LEDs compliant with ATCA specification: ■ Green LED – Healthy status ■ Amber LED – Fault condition ■ Blue LED – Indicates that blade server is safe for removal when on and hot swapping in progress when blinking. The LEDs are controlled by H8. 5.2.8.6 Power Control The BMR-H8S is able to control (enable/disable) power rails to the payload. 5.2.8.
TABLE 5-1 Voltage Sensor Thresholds ADM1026 Generated Critical Warning (approx. 7%) H8 Initiated Shutdown (approx. 10%) Sensor Number Sensor Name Voltage Lower Upper Lower Upper 7 12.0V 12V 11.16V 12.84V 11V 13.2V 8 5.0V 5V 4.8V 5.2V 4.78V 5.23V 9 3.3V 3.3V 3.07V 3.53V 3V 3.6V 10 3.3V STBY 3.3V 3.07V 3.53V 2.97V 3.63V 11 3V VBAT/STBY 3V 2.79V No UC no shutdown no shutdown 12 1.0V 1V 0.93V 1.07V 0.9V 1.1V 13 1.1V CPU 1.1V 1.02V 1.18V 0.99V 1.
The H8 temperature alarm equivalents are: Minor Alarm = Upper Non Critical (UNC) Major Alarm = Upper Critical (UC) Critical Alarm = Upper Non Recoverable (UNR) Emergency H8 Shutdown (EMR) = UNR Caution – These voltage and temperature thresholds should not be changed under normal operating conditions. 5.2.8.8 FRUID PROMs There are two FRUID PROMs on the Sun Netra CP3260 and both are 64-Kbyte SEEPROMs. One contains Sun FRU information and the other contains IPMI FRU information.
A reset mask register is provided in the FPGA to allow the masking of resets to individual I/O components. For example, a PEX_RESET_L reset from the UltraSPARC T2 processor resets only those I/O subcomponents not masked by the reset mask register. 5.2.10 ATCA Power Module (−48V to 12V) The Netra CP3260 blade server uses the Artesyn ATCA power module solution. The Artesyn power module provides an integrated ATCA power solution that meets PICMG 3.
APPENDIX A Physical Characteristics Specifications for the Netra CP3260 blade server are provided in the following sections: A.1 ■ Section A.1, “Form Factor” on page A-1 ■ Section A.2, “Layout” on page A-1 ■ Section A.3, “Front Panel” on page A-3 ■ Section A.4, “Connectors and Pinout” on page A-3 Form Factor The Netra CP3260 blade server is a standard 8U form factor, a single-slot-wide. It complies with the blade server mechanical dimensions required by the PICMG 3.0 R1.0 Specification: A.
FIGURE A-1 Netra CP3260 Blade Server Layout ④ ⑧ ① ⑦ ② ③ ⑥ ⑤ Figure Legend A-2 1 Ethernet port connector (RJ-45) 5 Zone 1 power connector 2 Dual USB port connector (USB 2.
A.3 Front Panel The single-slot-wide, 8U front panel was designed to meet PICMG 3.0 R 1.0 and other specifications. A.3.1 Visual Indicators The Netra CP3260 blade server has the following indicators on the front panel: ■ Green LED – Board’s healthy status or user programmable (ACTIVE). ■ Amber LED – Board’s fault condition (FAULT). ■ Blue LED – Indicates safe removal (hot-swap activity). The front panel’s Ethernet ports do not have LED indicators. A.3.
A.4.1.1 Ethernet Port The Ethernet connector is a RJ-45 connector. The controller autonegotiates to either 10BASE-T, 100BASE-T, or 1000BASE-T. The Ethernet connector pin numbering is shown in FIGURE A-2. FIGURE A-2 Ethernet RJ-45 Connector ... < > 12345678 Link LED (green) Activity LED (yellow) TABLE A-1 shows the Ethernet connector pin assignments. TABLE A-1 A.4.1.
FIGURE A-3 Dual USB Connector 1 2 3 4 3 4 B 1 2 A For USB connector signals, see TABLE A-2. TABLE A-2 A.4.1.3 USB Connector Pin Assignments Pin Signal Description Pin Signal Description A1 +5 V (fused) B1 +5 V (fused) A2 USB2− B2 USB3− A3 USB2+ B3 USB3+ A4 Ground B4 Ground Serial Port FIGURE A-4 contains the connector pin assignments for the front panel serial port.
FIGURE A-4 Front Panel Serial Port Diagram I0I0I 12345678 TABLE A-3 shows the serial port connector pin assignments. TABLE A-3 A.4.2 Serial Port RJ-45 Connector Pinouts Pin Signal Name Function Pin Signal Name Function 1 RTS Request To Send 5 GND Ground 2 DTR Data Terminal Ready 6 RXD Receive Data 3 TXD Transmit Data 7 DSR Data Set Ready 4 GND Ground 8 CTS Clear To Send Compact Flash Connector The Compact Flash connector is a type I/II connector. A.4.
FIGURE A-5 shows the pin assignments. FIGURE A-5 Power Distribution Connector (Zone 1) P10 TABLE A-4 lists the power connector pin assignments.
TABLE A-4 Power Distribution Connector Pin Assignments (Continued) Pin Number Name A.4.
FIGURE A-6 Zone 2 Connectors J20 J23 TABLE A-5 gives the Zone 2 J23 connector pin assignments.
TABLE A-6 Row A Zone 2 J20 Connector Pin Assignments (Continued) B C D E F G H 4 N/C N/C N/C N/C N/C N/C N/C N/C 5 N/C N/C N/C N/C N/C N/C N/C N/C 6 N/C N/C N/C N/C N/C N/C N/C N/C 7 N/C N/C N/C N/C N/C N/C N/C N/C 8 N/C N/C N/C N/C N/C N/C N/C N/C 9 N/C N/C N/C N/C N/C N/C N/C N/C 10 N/C N/C N/C N/C N/C N/C N/C N/C For information about multiplexing to Zone 2 or Zone 3, see Section 4.8, “Multiplexing to Zones 2 and 3” on page 4-27. A.
TABLE A-7 gives the Zone 3 J31 connector signals and pin assignments.
TABLE A-9 gives the Zone 3 J33 connector signals and pin assignments.
TABLE A-10 Zone 3 Power Connector Pin Assignments R o w Pin 1 Pin 2 Pin 3 Pin 4 Pin 5 Pin 6 A Logic_GND Logic_GND Logic_GND Shelf_GND Shelf_GND Shelf_GND B Logic_GND Logic_GND Logic_GND +3.3V_STBY_RTM +3.3V_STBY_RTM +3.
FIGURE A-9 TOD Battery Location ① ② Figure Legend A-14 1 TOD battery location 2 TOD clock battery location with FB-DIMM removed Netra CP3260 Blade Server User’s Guide • April 2009
APPENDIX B Sun OEM IPMI Commands This appendix contains the following sections: ■ Section B.1, “Get Version Command” on page B-2 ■ Section B.2, “Get RTM Status Command” on page B-3 ■ Section B.3, “Solaris OS Graceful Shutdown Commands” on page B-4 ■ Section B.4, “Send Sensor State Command” on page B-5 The commands described in this appendix are specific to Netra CP3260 blade server designed by Sun Microsystems.
B.1 Get Version Command Get Version returns the IPM controller (IPMC) firmware version and Standby CPLD version. Bytes 8, 9, and A are reserved for future use.
Example (Terminal Mode): [B8 00 80 00 00 2A] <-------Request [BC 00 80 00 00 00 2A 02 02 00 00 00 00] <----Response ■ The IPMC version is read as: lower nibble of REV1 . high nibble of REV2 . low nibble of REV2 In the preceding example, the IPMC version is 2.0.0. ■ The CPLD version is read as: -> lower nibble of CPLD version byte In the example, the CPLD version is 2. B.
Example (Terminal Mode): [B8 00 88 00 00 2A] <------Request [BC 00 88 00 00 00 2A 01] <------Response B.3 Solaris OS Graceful Shutdown Commands Users can change the graceful shutdown time out of Solaris OS with an IPMI command executed from ShMM or a user application. Note that this setting is not persistent; the Solaris FSM will overwrite it after every Solaris OS boot. SUNWctfsm is the Solaris FSM for ATCA graceful shutdown and reboot.
Note – As of the R3U2 release, Netra CP3260 sysfw 7.2.1 has graceful shutdown support. Note – To use the graceful shutdown effectively, users must determine a component’s shutdown time “cost,” which depends on hardware, software, and configuration. For example, the default 120 seconds could be too short for a Sun Netra CP3260 blade server with a heavy I/O configuration. Conversely, it could be too long for a Sun Netra CP3220 blade server.
TABLE B-3 Type B-6 Send Sensor State Command Data Bytes (Continued) Byte Data Field Byte4 Sensor type byte Indicates event class or type of sensor that generates the event message. (Refer to IPMI specification for sensor type codes.) Byte5 Sensor # (optional); Write to 0 Unique number representing the sensor within the management controller that generates the event message.
TABLE B-3 Send Sensor State Command Data Bytes (Continued) Type Response data Byte Data Field Byte12 Reserved for future use.
B-8 Netra CP3260 Blade Server User’s Guide • April 2009
Index Advanced Rear Transition Module (ARTM), 1-11 Advanced Telecommunications Computing Architecture (ATCA), 1-1 ARTM, 1-11, 2-18, 5-4, 5-10 installing, 2-19 ATCA (AdvancedTCA), 1-1 ATCA midplane, 2-20 auto-boot (OpenBoot variable), 4-6 automatic system recovery (ASR) disabling, 4-17 enabling, 4-17 obtaining recovery information, 4-28 replacing, 2-13 compliance NEBS, 1-3 PICMG specifications, 1-3 configurations Ethernet, 1-13 I/O, 1-13 Netra switches, 3-9 SAS, 1-13 connectors pinouts, A-3 to A-13 console
fabric interface, 5-1 management port, 5-4, 5-11 RJ-45, A-4 SERDES, 5-1 F fabric interface, 5-1, 5-3, 5-9, 5-10 fan tray upgrade kit, 1-14 FB-DIMMs, 2-5, 5-8 description, 2-5 installing, 2-11 location, 2-6 removing, 2-10 requirements, 2-5 features, 1-2 CPU, 1-2 hot-swap, 1-3 IPMI system management, 1-3 memory, 1-2 operating system, 1-3 power requirements, 1-2 Field-Programmable Gate Array (FPGA), 5-12 firmware updates, 3-8 flash update, 1-3 form factor, A-1 front panel, A-3, A-5 I/O, 1-3, 5-11 FRUID PROMs,
M MAC address, 3-8 label, 1-16 management port Ethernet, 5-11 manual system reset, 4-5 memory, 1-2, 5-8 FB-DIMMs, 2-5, 5-9 N netfunction (NetFn), B-1 Netra CP32X0 ARTM, 1-8, 1-11, 1-13, 1-14, 2-20 network boot, 1-8 network device aliases, 4-18 Power PC, 5-3 power-on self-test (POST), 4-2 preparation installation, 2-3 probe-ide (OpenBoot command), 4-8 probe-scsi (OpenBoot command), 4-7 probe-scsi-all (OpenBoot command), 4-7 processor block diagram, 5-5 cores, 5-2, 5-4 speed, 5-4 UltraSPARC T2, 5-2, 5-4 R
Solaris commands init, 4-5 shutdown, 4-5 SPARC, 5-2 subsystems, 5-1 CPU and memory, 5-1 I/O, 5-1 IPMI, 5-1 power, 5-1 service processor, 5-1 Sun Download Center (SDLC), 3-1 Sun OEM IPMI commands Get RTM Status, B-3 Sun Services, 1-15 SunVTS software, 3-9 support, 1-15 switch configuration Netra CP3140 1-GbE, 3-8 Netra CP3240 10-GbE, 3-8 system flash PROM, 4-2 system monitor, 5-15 World Wide Name (probe-scsi), 4-7 X XAUI, 5-1, 5-8, 5-9 XAUI ports, 5-8 T temperature monitoring, 5-16 TOD clock battery, 5-18
