SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual March 2005 83-00003261, Revision C
Copyright Copyright 2001-2005 Dot Hill Systems Corp. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, translated, transcribed, or transmitted, in any form or by any means – manual, electric, electronic, electromechanical, chemical, optical, or otherwise – without prior explicit written permission of Dot Hill Systems Corp., 6305 El Camino Real, P.O. Box 9000, Carlsbad, CA., 92009-1606.
Contents Preface 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Product and Architecture Overview 1.1 Comparison of FC, SATA, and SATA SE Arrays 1.1.1 1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 . . . . . . . . . . . . . . . . . . . . . . . . 1–2 Fibre Channel and SATA Array Architectures . . . . . . . . . . . . . . . . . . 1–3 1.1.1.1 SANnet II 200 FC Array Features . . . . . . . .
1.5 Fibre Channel Architecture 1.5.1 1.6 2. Site Planning Host Bus Adapters 1.5.1.2 Active-to-Active Redundant Controller 1.5.1.3 Host Redundant Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–14 . . . . . . . . . . . . . . .1–15 . . . . . . . . . . . . . . . . . . . . . . . . . .1–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 Connecting the Chassis to DC Power Outlets 4.5 Cabling to Expansion Units 4.6 Setting Loop IDs on Expansion Units 4.7 Powering Up and Checking LEDs 4.8 Reviewing Channels, Ports, and SFPs 4.8.1 4.8.2 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.3 7. 6.2.1 Drive LED Status 6.2.2 Correcting SES or PLD Firmware Version Conflicts Back-Panel LEDs 7.2 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–5 6.3.2 I/O Expansion Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–8 6.3.3 Power Supply and Fan Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . .6–9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A. B. 8.5 Recovering From Fatal Drive Failure 8.6 Using the Reset Push Button 8.7 Troubleshooting Flowcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–11 8.7.1 Power Supply and Fan Module 8.7.2 Drive LEDs 8.7.3 Front-Panel LEDs 8.7.4 I/O Controller Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F. G. H. I. viii E.2 Using the tip Command for Local Access to the Array . . . . . . . . . . . . . . . . E–2 E.3 Determining the WWN in the Solaris Operating System . . . . . . . . . . . . . . . . E–3 Configuring a Microsoft Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F–1 F.1 Setting Up the Serial Port Connection F.2 Accessing the Firmware Application From a Microsoft Windows Server F.
I.3 Attaching the Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–4 I.4 Logical Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–4 I.5 Definitions of Common Terms I.6 Creating a Physical Volume I.7 Creating a Volume Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–6 I.8 Creating a Logical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
Figures FIGURE 1-1 SANnet II 200 FC, SATA, and SATA SE Array Front View . . . . . . . . . . . . . . . . . 1–2 FIGURE 4-1 Front Bezel and Front Bezel Locks of an Array FIGURE 4-2 Sequence of Steps to Change Front Bezel Locks So Keys Cannot Be Removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3 FIGURE 4-3 Hardware Connections on the Back of a Dual-Controller SANnet II 200 FC Array . . . . . . . . . . . . . . . . . . . . . . . . . .
FIGURE 4-20 SANnet II 200 SATA Array Default Single-Controller SFP Placement FIGURE 4-21 SANnet II 200 FC JBOD/Expansion Unit Default SFP Placement FIGURE 4-22 SANnet II 200 SATA Expansion Unit Default SFP Placement FIGURE 4-23 Typical SFP Connector Used to Connect Cables to Chassis SFP Ports FIGURE 5-1 A Point-to-Point Configuration with a Dual-Controller SANnet II 200 FC Array and Two Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FIGURE B-3 SANnet II 200 FC JBOD Array Attached to Two HBA Ports . . . . . . . . . . . . . . . . B–8 FIGURE B-4 JBOD or Expansion Unit Troubleshooting Flowchart, 1 of 2 . . . . . . . . . . . . . . . B–15 FIGURE B-5 JBOD or Expansion Unit Troubleshooting Flowchart, 2 of 2 . . . . . . . . . . . . . . .
xiv SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
Tables TABLE 1-1 Comparison of SANnet II 200 FC, SATA, and SATA SE Array Features . . . . . . . . 1–5 TABLE 1-2 SANnet II 200 FC, SATA, and SATA SE Array Configuration Options TABLE 2-1 Environmental Specifications TABLE 2-2 Power Specifications TABLE 2-3 Physical Specifications TABLE 2-4 Site Preparation Worksheet TABLE 2-5 Host and Fabric Switch Connectivity Summarized TABLE 3-1 Contents of SANnet II 200 Array Packages TABLE 4-1 DC Cable Wiring for Cable 35-00000148 . . . . . . . . . .
TABLE 6-6 Power Supply LEDs TABLE 7-1 Battery Status Indicators TABLE 8-1 Cooling Element Sensors for FC, SATA, and SATA SE Arrays TABLE 8-2 Temperature Sensors for FC, SATA, and SATA SE Arrays TABLE 8-3 Voltage Sensors for FC Arrays TABLE 8-4 Voltage Sensors for SATA and SATA SE Arrays TABLE 8-5 Power Supply Sensors for FC, SATA, and SATA SE Arrays TABLE 8-6 Silencing Alarms TABLE A-1 SANnet II 200 FC, SATA, and SATA SE Array Physical Specifications TABLE A-2 SANnet II 200 FC, SATA, and
Preface This manual provides instructions for installing, initially configuring, and operating the SANnet II 200 Fibre Channel (FC), SANnet II 200 SATA, and the SANnet II 200 SATA Special Edition (SE) arrays; hereafter referred to as FC, SATA, and SATA SE arrays for ease of reading. This guide is written for experienced system administrators who are familiar with Dot Hill hardware and software products.
Appendix E provides instructions on configuring a Sun™ server. Appendix F provides instructions on configuring a Windows 2000 or Windows 2000 Advanced server. Appendix G provides instructions on configuring a Linux server. Appendix H provides instructions on configuring a IBM AIX server. Appendix I provides instructions on configuring an HP-UX server. Typographic Conventions Typeface1 Meaning Examples AaBbCc123 The names of commands, files, and directories; on-screen computer output Edit your.
Technical Support For late-breaking Release Notes and all manuals for this product, go to the SANnet II SCSI array section, or the SANnet II 200 FC array section, depending on which array you have, at: http://www.dothill.
Dot Hill Welcomes Your Comments Dot Hill is interested in improving its documentation and welcomes your comments and suggestions. You can email your comments to: support@dothill.com Include the part number (83-00003261) of your document in the subject line of your email.
CH A P T E R 1 Product and Architecture Overview This manual describes the SANnet II 200 FC, SATA, and SATA Special Edition (SE) arrays. The FC, SATA, and SATA SE arrays are rack-mountable, Network Equipment Building System (NEBS) Level 3-compliant, Fibre Channel mass storage subsystems. NEBS Level 3 is the highest level of NEBS criteria used to assure maximum operability of networking equipment in mission-critical environments such as telecommunications central offices. SANnet II 200 FC Array.
1.1 Comparison of FC, SATA, and SATA SE Arrays Figure 1-1 SANnet II 200 FC, SATA, and SATA SE Array Front View The SANnet II 200 FC array is a next-generation Fibre Channel storage system designed to provide direct attached storage (DAS) to entry-level, mid-range, and enterprise servers, or to serve as the disk storage within a storage area network (SAN). This solution features powerful performance and reliability, availability, and serviceability (RAS) features using modern FC technology.
1.1.1 Fibre Channel and SATA Array Architectures The FC, SATA, and SATA SE share many architectural elements. This section discusses those elements, making note of the few ways in which the architecture is implemented differently in the two arrays. The SANnet II 200 FC array, SATA array, and SATA SE array RAID controllers have six FC channels. RAID controller channels 0, 1, 4, and 5 are normally designated for connection to hosts or Fibre Channel switches.
1.1.1.2 SANnet II 200 SATA and SATA SE Array Features On the SANnet II 200 SATA and SATA SE arrays, RAID controller channels 0 and 1 are dedicated host channels. Channels 4 and 5 are host channels by default but can be configured as drive channels. RAID controller channels 2 and 3 are dedicated drive channels that connect to expansion units.
Note – Although the products are very similar in appearance and setup, the configurations have very important differences. While the FC array can be used for all applications, the SATA and SATA SE arrays cannot. Inappropriate use of the SATA arrays in applications for which the FC array was designed might result in loss of data and/or loss of data access.
Table 1-1 Comparison of SANnet II 200 FC, SATA, and SATA SE Array Features (Continued) SANnet II 200 FC Array SANnet II 200 SATA Array SANnet II 200 SATA SE Array Maximum Number of Disks per Configuration 192 (1 RAID array + 15 expansion units) 192 (1 RAID array + 15 expansion units) 12 Maximum Number of Logical Drives 32 logical drives 32 logical drives 32 logical drives Direct hostattached JBOD Support One JBOD per server Not supported Not supported (1 RAID array) Caution – In FC and SATA
Table 1-2 shows the configuration options for SANnet II 200 FC, SATA, and SATA SE arrays. Table 1-2 SANnet II 200 FC, SATA, and SATA SE Array Configuration Options Internal RAID controllers 1 or 2 2-Gbit/sec Fibre Channel disks (SANnet II 200 FC array)1 1.5-Gbit/sec serial ATA disks (SANnet II 200 SATA array) Up to 12 per array or per expansion unit, with a minimum of 4 plus 1 spare FC expansion units2 Up to 8 for a SANnet II 200 FC array.
in a JBOD array. For example, “SANnet II 200 D1000” identifies a JBOD array with SES firmware version 1000 and “SANnet II 200F A1000” identifies a SANnet II 200 FC RAID array with firmware version 1000. For a list of supported racks and cabinets, refer to the SANnet II Family Rack Installation Guide for 2U Arrays.
Specific Integrated Circuit (ASIC) controller chips handle the interconnection between the controller bus, DRAM memory, and Peripheral Component Interconnect (PCI) internal buses. They also handle the interface between the on-board 2-Mbyte flash memory, 32-Kbyte nonvolatile random access memory (NVRAM), RS-232 port chip, and 10/100 BASE-T Ethernet chip. The RAID I/O controller module is a multifunction board.
Caution – You can mix disk drive capacity in the same chassis, but not spindle speed (RPM). For instance, you can use 36-Gbyte and 73-Gbyte drives with no performance problems if both are 10K RPM drives. Violating this configuration guideline leads to poor performance. In the event of a single disk drive failure, with the exception of RAID 0, the system continues to service all I/O requests.
1.2.5 Power and Fan Modules Note – The SATA arrays can only be ordered in an AC configuration. However, DC power supplies can be ordered in an x-option kit, and the SATA arrays can be reconfigured using the DC power supplies. For details, refer to the SANnet II Family FRU Installation Guide. Each array contains two redundant power and fan modules. Each module contains a 420-watt power supply and two radial 52-cubic-feet-per-minute (CFM) fans.
1.4.1 FC Protocols Two common protocols are used to connect Fibre Channel (FC) nodes together: ■ Point-to-point—The point-to-point protocol is straightforward, doing little more than establishing a permanent communication link between two ports. ■ Arbitrated loop—The arbitrated loop protocol creates a simple network featuring distributed (arbitrated) management between two or more ports, using a circular (loop) data path. Arbitrated loops can support more nodes than point-to-point connections can.
A fabric switch functions as a routing engine, which actively directs data transfers from source to destination and arbitrates every connection. Bandwidth per node via a fabric switch remains constant when more nodes are added, and a node on a switch port uses a data path with speed up to 100 Mbps to send or receive data. 1.4.4 Data Availability Data availability is one of the major requirements for today’s mission-critical applications.
1.5 Fibre Channel Architecture Each RAID array has six Fibre Channels with the following defaults: ■ Channels 0, 1, 4, and 5 are host channels connected to servers. Any SANnet II 200 FC array host channels can be reassigned as drive channels to connect to expansion units. SANnet II 200 SATA array channels 3 and 4 can also be reassigned as drive channels.
1.5.1.2 Active-to-Active Redundant Controller In active-to-active redundant controller mode, the primary loop serves the I/O traffic directed to the primary controller, and its pair loop serves the I/O traffic to the secondary controller. The host-side management software directs I/O traffic to the pair loop if one of the redundant loops fails. Since each fibre interface supports only a single loop ID, two HBAs are necessary for active-to-active redundant controller operation.
1-16 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
CH A P T E R 2 Site Planning This chapter outlines the site planning requirements and basic safety requirements for the installation and use of the FC arrays, SATA arrays, and SATA Special Edition (SE) arrays. Complete a preinstallation worksheet and prepare the site for installation according to the worksheet details and the specified site planning requirements. Review the details of this chapter before installing an array.
The customer is responsible for meeting all government codes and regulations concerning facilities. The customer is also responsible for compliance with the following requirements: ■ Meeting all local, national, and international codes covered in Appendix A. The subjects covered include fire and safety, building, and electrical codes. ■ Documenting and informing Dot Hill, Inc. of any deviations from Appendix A. 2.
2.3 Environmental Requirements Table 2-1 Environmental Specifications Operating Nonoperating Altitude To 9000 feet (3000 meters) To 36,000 feet (12,000 meters) Humidity 10% to 90% RH at 80° F (27° C) max wet bulb (noncondensing) 93% RH, 100° F (38° C) max wet bulb temperature (noncondensing) 41° F (5° C) to 104° F (40° C) 41° F (5° C) to 95° F (35° C) –40° F (–40° C) to +149° F (+65° C) –40° F (–40° C) to +149° F (+65° C) Temperature Standalone Rack 2.3.
Table 2-2 Power Specifications 2.5 AC power Voltage and frequency 90 to 264 VAC, 47 to 63 Hz Input current 5A max Power supply output voltage +5 VDC and +12 VDC DC power –48 VDC (–36 VDC to –72 VDC) Physical Specifications Use the physical specifications in Table 2-3 to plan the location of your array. Table 2-3 Physical Specifications 2.6 Category Description Dimensions 2U 3.45 inches (8.76 cm.) height 21 inches (53.34 cm.) chassis depth 17.5 inches (44.6 cm.) width 19 inches (48.26 cm.
■ ■ ■ 2.6.2 Route interface cables away from motors and other sources of magnetic or radio frequency interference. Stay within the cable length limitations. Provide two separate power sources for the array. These power sources must be independent of each other, and each must be controlled by a separate circuit breaker at the power distribution point. Tabletop Placement SANnet II 200 FC, SATA, and SATA SE arrays can be positioned on a desk or a table.
Note – SANnet II family arrays require at least CAT-5 Ethernet cable. See the following preinstallation worksheet for additional preparation details. 2.8 Preinstallation Worksheets Before ordering an FC, SATA, or SATA SE array, complete the preinstallation worksheets on the following pages and then prepare the site for installation according to the site planning requirements.
Table 2-4 Site Preparation Worksheet Rackmounting Customers must ensure that the appropriate service outlets are available for installation. Requirements vary. • Will the array be rackmounted? Yes / No • Is the rack supplied by Dot Hill, Inc.
Table 2-5 Host and Fabric Switch Connectivity Summarized Host or Fabric Switch Connectivity - Host or Fabric Switch #1 Host or fabric switch name: _____________________________________ Host or fabric switch make/model: ________________________________ HBA connector types: _____________________________ Cable distance from the array to the hosts: ___________ Operating system: ________________________________ Patches installed: ________________________________ IP addresses: • Network ____________________ • Ho
CH A P T E R 3 Unpacking Your Array This chapter describes the procedure for unpacking your FC, SATA, or SATA SE array package. The following topics are covered in this chapter: ■ “Opening Your Package” on page 3-1 ■ “Checking the Package Contents” on page 3-2 ■ “Field-Replaceable Units” on page 3-3 ■ “Customer-Provided Cables” on page 3-3 ■ “Mounting Your Array in a Rack or Cabinet” on page 3-3 3.1 Opening Your Package Follow these guidelines for unpacking the equipment.
6. Check the list of “Customer-Provided Cables” on page 3-3. These are required to complete your installation. Note – You must purchase or provide fiber-optic cables for connecting FC, SATA, and SATA SE arrays to host servers. 3.2 Checking the Package Contents Inspect the array package for standard items as well as purchased options before you begin installation. If any parts are missing or damaged, contact your sales representative immediately. 3.2.
3.3 Field-Replaceable Units Check that you received all field-replaceable units (FRUs) ordered with your array. For additional FRUs, consult your sales representative.
3-4 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
CH A P T E R 4 Connecting Your Array This chapter describes procedures for cabling a FC, SATA, or SATA SE array and for connecting an array to power and to network devices.
Before you connect the array to the network, position the array in the rack, cabinet, or other location where it will be used. Caution – When positioning the array, do not block the air vents at the front or back of the unit. Follow all safety precautions specified in the SANnet II Family Safety, Regulatory, and Compliance Manual. Caution – When you power off an array, wait five seconds before you power it back on. If you power the array off and on too quickly, unexpected results can occur.
4. Lift the pawl off the threaded part of the lock body, as shown in the second panel of Figure 4-2. Figure 4-2 Sequence of Steps to Change Front Bezel Locks So Keys Cannot Be Removed 5. Set the pawl aside, face up, so that you can remember its orientation when you replace it. 6. Use the key to turn the lock 180 degrees, as shown in the third panel of Figure 4-2. 7. Replace the pawl in the same orientation as before, as shown in the fourth panel of Figure 4-2. 8.
9. Replace the bezel. Note – To convert your bezel locks so that the keys can be removed, repeat this procedure. 4.2 RAID Array Connections Management is in-band through fibre host connections and out-of-band through the serial port and Ethernet port on the back of each controller. 4.2.1 SANnet II 200 FC Array Connections Figure 4-3 identifies the hardware connections on the back of a dual-controller SANnet II 200 FC array.
Servers and consoles FC devices Management console FC expansion units/FC arrays FC device connections application/data servers and consoles Figure 4-3 Hardware Connections on the Back of a Dual-Controller SANnet II 200 FC Array 4.2.2 SANnet II 200 SATA Array Connections Figure 4-4 identifies the hardware connections on the back of a dual-controller SANnet II 200 SATA array.
Servers and consoles FC devices Management console FC expansion units/FC arrays FC device connections application/data servers and consoles Figure 4-4 Hardware Connections on the Back of a Dual-Controller SANnet II 200 SATA Array 4-6 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
4.2.3 SANnet II 200 SATA SE Array Connections Figure 4-5 identifies the hardware connections on the back of a dual-controller SANnet II 200 SATA SE array. Servers and consoles Management console FC device connections application/data servers and consoles Figure 4-5 Hardware Connections on the Back of a Dual-Controller SANnet II 200 SATA SE Array 4.3 Connecting the Chassis to AC Power Outlets When you connect the AC power cords, install the two provided cord locks at the same time.
1. Use a Phillips screwdriver to remove the screw and cylindrical standoff from one of the two provided cord locks. Set them aside for reassembly later. 2. Slide the cord lock over the AC power connector. 3. Hold the cylindrical standoff between the two screw holes on the flanges of the cord lock. 4. Insert the screw into the first screw hole, through the standoff, and then into the threaded screw hole on the other flange. 5.
2 1 3 4 Figure 4-6 Installing a Cord Lock 4.4 Connecting the Chassis to DC Power Outlets Note – The SANnet II 200 SATA array can only be ordered in an AC configuration. However, DC power supplies can be ordered in an x-option kit, and a SANnet II 200 SATA array can be reconfigured using the DC power supplies. Refer to the SANnet II Family FRU Installation Guide for a procedure for removing and replacing power supplies. Two DC power cords are packaged with each DC array.
Table 4-1 DC Cable Wiring for Cable 35-00000148 Pin Number Voltage Color A3 Return Red A2 GND (Chassis Ground) Green/Yellow A1 –48 VDC Black Table 4-2 DC Cable Wiring for Cable 35-00000156 Pin Number Voltage Color A3 L+ Red A2 GND (Chassis Ground) Green/Yellow A1 L– White 2. Connect a DC power cable to the first power supply and to a power outlet. Note – Use only the DC power cables provided with the array.
4.5 Cabling to Expansion Units The instructions in this section apply to the SANnet II 200 FC and the SANnet II 200 SATA arrays only. The SANnet II 200 SATA SE array does not support expansion units. Caution – When connecting expansion units to a RAID array, always connect channel 2 of the RAID array to the A channel of the expansion units, and connect channel 3 of the RAID array to the B channel of the expansion units. Otherwise, unexpected behavior might occur.
RAID array Expansion unit 1 Expansion unit 2 Loop A (top drive ports) Loop B (bottom drive ports) Cable to drive Cable to host Figure 4-7 SANnet II 200 FC Array Attached to Two Hosts and Two Expansion Units 4-12 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
H/D/RCC RAID array H/D/RCC Expansion unit 1 Loop A (left-side drive ports) Expansion unit 2 Cable to drive Loop B (right-side drive ports) Cable to host Figure 4-8 SANnet II 200 SATA Array Attached to Two Hosts and Two Expansion Units 4.6 Setting Loop IDs on Expansion Units When an expansion unit is attached to a RAID array, unique, hard-assigned loop IDs are assigned to each expansion unit drive. A loop ID is the decimal version of an arbitrated loop physical address (AL_PA).
Plastic “ear” cap covering loop ID switch Bezel locks Figure 4-9 Front Bezel and Front Bezel Locks of an Array 1. Use the provided key to unlock both bezel locks. 2. Grasp the front bezel cover on both sides and pull it forward and then down. 3. Remove the plastic cap from the left ear of the array. a. Squeeze both sides of the cap at the top and the bottom. b. Turn the cap toward the center of the array until it disengages and pull it free.
Ensure that the loop IDs of expansion units do not duplicate the loop IDs of other connected expansion units or RAID arrays. The ID switch offers eight ID ranges. Each range contains 16 IDs (the last four IDs in each range are ignored). These ranges are shown in Table 4-3.
8. Lift the bezel into position and press it onto the front of the chassis until it is flush with the front. 9. Use the key to lock both bezel locks. 4.7 Powering Up and Checking LEDs Perform the initial check of the array according to the following procedure. 1. Connect two AC or DC power cables to the power and fan modules on the back of the array. 2. Power on the array by turning on each power switch.
labeled FC0, FC1, FC4, and FC5 to indicate channels 0, 1, 4, and 5. Default configurations do not include an SFP connector in every SFP port. To add or change SFP connectors, see to “Changing Your SFP Configuration” on page 4-24. The channels and associated ports for the SANnet II 200 FC, SATA, and SATA SE arrays are summarized in Table 4-5.
Note – The SANnet II 200 SATA SE array configuration does not include drive ports. 4.8.1.1 SANnet II 200 FC Array Drive Ports Configured for redundancy, each controller in a dual-controller RAID array has two adjacent dedicated drive channels on one loop to load balance I/O operations (see Figure 4-12). Each drive channel has two SFP ports that can be connected to expansion units. Drive channels 2 and 3 access all the disk drives and are interconnected to loadbalance I/O operations.
Two drive ports on channel 2 Two drive ports on channel 3 An upper port and a lower port are on each drive channel. Figure 4-13 Dedicated Drive Channels 2 and 3 (on Both Controllers) in a Dual-Controller SANnet II 200 SATA Array 4.8.2 Host Port Connectivity in a Dual-Controller Array Host channels connect to host computers either directly or through storage switches or other devices. In a default dual-controller RAID configuration, each controller has four host channels, channels 0, 1, 4, and 5.
Host channel 0 Host channel 4 Host channel 1 Host channel 5 An upper port and a lower port are on each host channel. Figure 4-14 Host Channels on a Dual-Controller SANnet II 200 FC Array 4.8.2.
Host channel 0 Host channel 4 Host channel 1 Host channel 5 An upper port and a lower port are on each host channel. Figure 4-15 Host Channels on a Dual-Controller SANnet II 200 SATA Array The following figure shows the host channels for a SANnet II 200 SATA SE array. Host channel 0 Host channel 4 Host channel 1 Host channel 5 An upper port and a lower port are on each host channel. Figure 4-16 Host Channels on a Dual-Controller SATA SE Array 4.8.
To review various configuration options, see the discussions following “Summary of Array Configuration” on page 5-1. Refer also to the configuration options presented in the SANnet II 200 FC and SATA Array Best Practices Manual. In dual-controller arrays, SFPs are initially plugged into one of each pair of host and drive ports. The default port connections are: ■ The upper I/O controller module has SFPs in the FC0, FC2, and FC4 ports.
No SFPs are plugged into the drive channels. This configuration is appropriate for connecting to up to four hosts or fibre switches, with no connection to expansion units (see Figure 4-19 and Figure 4-20).
Default SFP Placement Figure 4-21 SANnet II 200 FC JBOD/Expansion Unit Default SFP Placement In a default SANnet II 200 SATA expansion unit, SFPs are initially plugged into the left-most Loop A port in the upper I/O expansion module and in the left-most Loop B port in the lower I/O expansion module (Figure 4-22). Default SFP Placement Figure 4-22 SANnet II 200 SATA Expansion Unit Default SFP Placement 4.8.
Figure 4-23 Typical SFP Connector Used to Connect Cables to Chassis SFP Ports 4.9 Establishing Communications With An Array Before you can configure an array, you must establish one or more communication links between at least one host and an array. You can use any combination of the array’s RS-232 COM (serial) port, the Ethernet port, and the in-band data connection between the host and the array.
■ ■ ■ Use the show network-parameters CLI command. Refer to the SANscape CLI User's Guide for more information. If the RAID controller is not on a network connected to an active DHCP server, an IP address of 0.0.0.0 is displayed. Refer to the SANscape CLI User's Guide for more information. Use the Change Network Settings window in SANscape. Refer to the “Updating the Configuration” chapter in the SANscape User’s Guide for more information. Enable the controller firmware to send event messages using SNMP.
4.11 Manually Setting a Static IP Address You can manually set an array’s IP address using the controller’s firmware by typing values for the IP address, the subnet mask, and IP address of the gateway. If your network uses a Reverse Address Resolution Protocol (RARP) server or a Dynamic Host Configuration Protocol (DHCP) server to automatically configure IP information for devices on the network, you can specify the appropriate protocol instead of typing the information manually.
8. Choose Yes to reset the controller. The controller takes a few minutes to format a small storage sector on each physical drive before logical drives can be successfully initialized. 4.12 Setting Up Out-of-Band Management Over Ethernet The controller Ethernet port offers interactive out-of-band management through the following interfaces: ■ The SANscape application. Refer to the SANscape User’s Guide for details. ■ The SANscape Command-Line Interface (CLI).
# telnet IP-address Note – Alternatively, you can use the Solaris operating system tip command or a terminal emulation program to access the firmware application program. See “Configuring a Host COM Port to Connect to a RAID Array” on page 4-26 for more information. 4. Press Ctrl-L to refresh the screen and view the Main Menu. Note – If you reset the controller during a telnet session, you are disconnected from the RAID array. Use the telnet command to login to the array again.
Carefully consider the following limitations of special high-capacity configurations. Using multiple SANnet II 200 FC arrays connected to the same SAN normally provides significantly better performance than one high-capacity configuration. ■ Maximize the size of each logical drive (up to 1908 Gbyte) before creating another logical drive in order to allow for maximum storage capacity. ■ SANnet II 200 FC arrays can be connected to SANnet II 200 FC expansion units.
6. Verify the SES/PLD (programmable logic device) version of the expansion unit and the RAID array. To review the version information, using the SANscape CLI, type show ses. Or, using SANscape, open the View Enclosure window. 7. If the SES/PLD version is not the same for the RAID array and the expansion unit, download the latest SES/PLD firmware from the Dot Hill web site: http://www.dothill.com. a. Choose Support →Downloads. b. Click Firmware Downloads. c. Enter the required information, and click Submit.
Note – The connection of a FC, SATA, or SATA SE array to Fibre Channel HBAs that use different speeds (1 Gbit and 2 Gbit) on the same channel is not supported. You can, however, mix 1-Gbit and 2-Gbit Fibre Channel HBAs on different channels. This limitation is due to the design of SANnet II 200 Fibre Channel array port bypass circuitry and the inability of Fibre Channel to support auto-negotiation in a multi-drop loop configuration.
4.17 Powering Off the Array You might need to power off the array (both power supplies) if you relocate the array or perform certain maintenance procedures with associated servers. Always shut down the array’s controller before powering off the array. Caution – If controllers are not shut down from the firmware application or the SANscape CLI before an array is powered off, data that is written to cache and that has not been completely written to the disks will be lost.
4-34 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
CH A P T E R 5 Configuration Overview This chapter highlights the tools and the important limitations and guidelines which must be understood prior to configuring your array.
3. Set up an IP address for the controller. See “Establishing Communications With An Array” on page 4-25. Note – For detailed information in performing steps 4–14, refer to the SANnet II Family RAID Firmware User’s Guide for optimization mode guidelines. 4. Check the status of the available physical drives. 5. Determine whether sequential or random optimization is more appropriate for your applications and configure your array accordingly. 6.
Note – Each operating system has a method for recognizing storage devices and LUNs and might require the use of specific commands or the modification of specific files. Be sure to check the information for your operating system to ensure that you have performed the necessary procedures.
Caution – If you keep the default loop mode and connect to a fabric switch, the array automatically shifts to public loop mode. As a result, communication between the array and the switched fabric runs in half duplex (send or receive) instead of providing the full duplex (send and receive) performance of point-to-point mode. ■ ■ ■ Check the host IDs on all the channels to ensure that there is only one ID per channel (on the primary controller or on the secondary controller) for point-to-point mode.
attaching the cables for a LUN-mapped channel pair, make sure that the first channel is connected to the upper port and the second channel is connected to the lower port of the second channel. For example, to provide redundancy, map half of the LUNs across Channel 0 (PID 40) and Channel 4 (PID 42), and then map the other half of your LUNs across Channel 1 (SID 41) and Channel 5 (SID 43). ■ ■ Point-to-point mode allows a maximum of 128 LUNs per array.
Note – Multipathing for FC, SATA, and SATA SE arrays is provided by SANpath software. Remember these important rules: ■ A single logical drive can be mapped to only one controller, either the primary controller or the secondary controller. ■ In a point-to-point configuration, only one host ID per channel is allowed. The host ID can be assigned to the primary controller and be a PID, or it can be assigned to the secondary controller and be a SID.
Server 0 Server 1 Switch 0 Switch 1 PID 40 0 PID 43 1 N/A 4 N/A 5 N/A 0 N/A 1 SID 45 4 SID 46 5 Map LG0 to PIDs 40 and 43 N Map LG1 to SIDs 45 and 46 : Host port on channel number N PID 40 / PID43 : SID 45 / SID46 : N/A : : Host IDs on primary controller Host IDs on secondary controller Not applicable (no ID on that controller) Port bypass circuit Figure 5-1 A Point-to-Point Configuration with a Dual-Controller SANnet II 200 FC Array and Two Switches Chapter 5 Configuration Overview
Server 0 Server 1 Switch 0 Switch 1 PID 40 A PID 43 C N/A N/A A N/A C SID 45 Map LG0 to PIDs 40 and 43 N N/A H G SID 46 H G Map LG1 to SIDs 45 and 46 : Host port on channel number N PID 40 / PID43 : SID 45 / SID46 : N/A : : Host IDs on primary controller Host IDs on secondary controller Not applicable (no ID on that controller) Port bypass circuit Figure 5-2 A Point-to-Point Configuration With a Dual-Controller SANnet II 200 SATA Array and Two Switches Note – These illustrations show t
Table 5-1 Example Point-to-Point Configuration With Two Logical Drives in a DualController Array Logical Drive LUN IDs Channel Number Primary ID Number Secondary ID Number Map 32 partitions of LG 0 to CH 0 LG 0 0-31 0 40 N/A Duplicate-map 32 partitions of LG 0 to CH 1 LG 0 0-31 1 41 N/A Map 32 partitions of LG 1 to CH 4 LG 1 0-31 4 N/A 50 Duplicate-map 32 partitions of LG 1 to CH 5 LG 1 0-31 5 N/A 51 Task Perform the following steps to set up a typical point-to-point SAN config
7. Map logical drive 0 to channels 0 and 1 of the primary controller. Map LUN numbers 0 through 31 to the single ID on each host channel. 8. Map logical drive 1 to channels 4 and 5 of the secondary controller. Map LUN numbers 0 through 31 to the single ID on each host channel. Since each set of LUNs is assigned to two channels for redundancy, the total working maximum number of LUNs is 64 LUNs.
Server 1 Server 3 Server 2 Server 4 Figure 5-3 A DAS Configuration With Four Servers, a Dual-Controller SANnet II 200 FC Array, and Two Expansion Units Chapter 5 Configuration Overview 5-11
Server 4 Server 3 Server 1 Server 2 H/D/RCC H/D/RCC Figure 5-4 A DAS Configuration With Four Servers, a Dual-Controller SANnet II 200 SATA Array, and Two Expansion Units Establishing complete redundancy and maintaining high availability requires the use of multipathing software such as SANpath software. To configure for multipathing: 1. Establish two connections between each server and the array. 2. Install and enable multipathing software on the server. 3.
DAS configurations are typically implemented using a fabric loop (FL_port) mode. A loop configuration example is described in “A Sample DAS Loop Configuration” on page 5-10. FL_port connections between a FC, SATA, or SATA SE arrays and multiple servers allow up to 1024 LUNs to be presented to servers. For guidelines on how to create 1024 LUNs, refer to the SANnet II Family RAID Firmware User’s Guide. Perform the following steps to set up a DAS loop configuration as shown in Figure 5-3 and Figure 5-4. 1.
11. Connect the first server to port FC 0 of the upper controller and port FC5 of the lower controller. 12. Connect the second server to port FC 4 of the upper controller and port FC1 of the lower controller. 13. Connect the third server to port FC 5 of the upper controller and port FC0 of the lower controller. 14. Connect the fourth server to port FC 1 of the upper controller and port FC4 of the lower controller. 15. Install and enable multipathing software on each connected server. 5.1.
■ ■ ■ ■ Do not combine SANnet II 200 FC drives and SANnet II 200 SATA drives on the same Fibre Channel loop. Use them only on separate loops. Do not connect SANnet II 200 SATA expansion units to SANnet II 200 FC arrays in single-controller configurations. Make sure at least one additional logical drive is available before adding a SANnet II 200 SATA expansion unit. It is preferable to make sure a minimum of one available logical drive per SANnet II 200 SATA expansion unit is available.
5-16 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
CH A P T E R 6 Checking LEDs This chapter describes the front and back-panel LEDs, which display the operating status of all drives and modules.
6.2 Front-Panel LEDs The drive LEDs are located between the rows of drives on the front-panel, as shown in Figure 6-1. The system operation LEDs are located on the right ear of the chassis and shown in Figure 6-2. Drive LED 0 LED 1 LED 2 • Power Drive LED 3 LED 4 LED 5 • Fan • Temp • Event • Reset • Reset push button Disk 0 Disk 3 Disk 6 Disk 9 Disk 1 Disk 4 Disk 7 Disk 10 Disk 2 Disk 5 Disk 8 Disk 11 Figure 6-1 Front-Panel LEDs Figure 6-2 shows the chassis ear LEDs and reset push button.
Table 6-2 lists the front-panel LEDs and describes LED activity. Table 6-2 Front-Panel LEDs LED LED Color Description Drive Solid green Good: Drive power-up and spin-up OK. Blinking green Good: Indicates drive activity. Solid amber Failed: Drive failure. Power (Light bulb icon) Monitors the DC output voltage within tolerance specification. Overcurrent protection shutting down any voltage output is also displayed. Voltage thresholds: +5 VDC +/–.25 VDC +12 VDC +/–.
Note – To test that the LEDs work, using a paper clip, press and hold the Reset button for 5 seconds. All the LEDs should change from green to amber when you perform this test. Any LED that fails to light indicates a problem with the LED. When you release the Reset button, the LEDs return to their initial state. 6.2.1 Drive LED Status The drive LED color changes based on array events.
A similar situation occurs when you add an expansion unit or JBOD and there is a mismatch between the SES or PLD firmware of the RAID array and that of the expansion unit, or between two expansion units. See “Upgrading SES and PLD Firmware” on page 7-8 for information about upgrading SES and PLD firmware. 6.3 Back-Panel LEDs The back-panel LED colors indicate the conditions described in the following figures and tables.
I/O activity Cache Ethernet active Ethernet link Battery H/D/RCC RAID controller status SFP link status SFP speed Figure 6-4 SANnet II 200 SATA Array I/O Controller Module and Battery Module LEDs Note – Although an amber light on the back panel often indicates a faulty component, a steady amber light on the Ethernet link LED indicates normal Ethernet activity. See Table 6-4 for more information.
The I/O controller module LEDs and their color definitions are shown in Table 6-4.
Note – Ethernet link LEDs on SANnet II 200 FC, SATA, and SATA SE arrays differ from the Ethernet link LEDs found on SANnet II 200 SCSI arrays and SANnet II 220 SCSI arrays. On SANnet II 200 FC, SATA, and SATA SE arrays, a connected port’s Ethernet link LED glows solid amber only on the active controller, because the Ethernet port on an FC array is considered active only if its controller is active. On an inactive controller, a port’s Ethernet link LED is off whether the port is connected or not.
The I/O expansion module LEDs and their color definitions are shown in Table 6-5.
LED Figure 6-8 AC Power Supply and Fan Module The following figure shows the DC power supply and fan module.
CH A P T E R 7 Maintaining Your Array This chapter covers the following maintenance and troubleshooting topics: ■ “Using Software to Monitor and Manage the Array” on page 7-1 ■ “Out-of-Band Connections” on page 7-2 ■ “In-Band Connections” on page 7-2 ■ “Other Supported Software” on page 7-2 ■ “Enabling VERITAS DMP” on page 7-3 ■ “The VERITAS Volume Manager ASL” on page 7-4 ■ “Battery Operation” on page 7-4 ■ “Viewing Event Logs on the Screen” on page 7-5 ■ “Upgrading Firmware” on page 7-7 ■ “Installing Fir
■ ■ SANscape Alert provides event monitoring and notification. Refer to the SANscape Alert User’s Guide for information. SANscape Command-Line Interface (CLI) provides script-based management. Refer to the SANscape CLI User’s Guide for SANscape CLI information. For details on how to install SANscape, SANscape Alert, or SANscape CLI software, refer to the SANscape Software Installation Guide.
setting up a configuration with redundant pathing. Multipathing software makes multiple paths between the server and the storage system and provides full services on each path for path failover. Refer to the appendix for your host and to the SANnet II 200 FC, SATA, and SATA SE Array Release Notes for information about which versions of SANpath software are supported on your platform. Refer to these release notes for information about additional supported or provided software. 7.1.
7.1.5 The VERITAS Volume Manager ASL VERITAS has provided an Array Software Library (ASL) that must be installed on the same host system as the Volume Manager 3.2 or 3.5 software to enable the software to recognize a FC or SATA array. 7.2 Battery Operation The battery LED (on the far right side of the I/O controller module) is amber if the battery is bad or missing. The LED blinks green if the battery is charging and is solid green when the battery is fully charged. 7.2.
Your lithium ion battery should be changed every two years if the unit is continuously operated at 77° F (25° C). If the unit is continuously operated at 95° F (35° C) or higher, the battery should be changed every year. The shelf life of your battery is three years. Note – The RAID controller has a temperature sensor which shuts off battery charging when the temperature reaches 129° F (54° C).
1. From the Main Menu, choose view and edit Event logs to view the event logs. A log of recent events is displayed. Note – The controller can store up to 1000 event log entries. The event log records configuration and operational events as well as error messages and alarm events. 2. Use your arrow keys to move up and down through the list. 3. To clear events from the log after you have read them, use your arrow keys to move down to the last event you want to clear and press Return.
7.4 Upgrading Firmware Caution – Be particularly careful about downloading and installing PLD firmware. If the wrong firmware is installed, or the firmware is installed on the wrong device, your controller might be rendered inoperable. Always be sure to upgrade your SES firmware first before trying to determine if you need a PLD upgrade. 7.4.1 Installing Firmware Upgrades It is important that you run a version of firmware that is supported by your array.
A controller that replaces a failed unit in a dual-controller system often has a newer release of the firmware installed than the firmware in the controller it replaced. To maintain compatibility, the surviving primary controller automatically updates the firmware running on the replacement secondary controller to the firmware version of the primary controller. Note – When you upgrade your controller firmware in the Solaris operating system, the format(1M) command still shows the earlier revision level.
7.5.1 Removing the Front Bezel and Ear Caps 1. Use the provided key to unlock both bezel locks. 2. Grasp the front bezel cover on both sides and pull it forward and then down. Note – For many operations, including replacing disk drives, it is not necessary to further detach the bezel, because dropping it down moves it sufficiently out of the way. 3. Press the right bezel arm (hinge) toward the left side to release it from the chassis hole. The left hinge also disengages. 4.
7-10 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
CH A P T E R 8 Troubleshooting Your Array This chapter covers the following maintenance and troubleshooting topics: ■ “Sensor Locations” on page 8-1 ■ “Silencing Audible Alarms” on page 8-5 ■ “RAID LUNs Not Visible to the Host” on page 8-7 ■ “Controller Failover” on page 8-7 ■ “Recovering From Fatal Drive Failure” on page 8-8 ■ “Using the Reset Push Button” on page 8-10 ■ “Troubleshooting Flowcharts” on page 8-11 ■ “Power Supply and Fan Module” on page 8-11 ■ “Drive LEDs” on page 8-13 ■ “Front-Panel LEDs”
8.1.1 Cooling Element Sensors There are two fans in each power supply module. The normal range for fan speed is 4000 to 6000 RPM. Cooling element failure occurs when a fan’s speed drops below 4000 RPM.
8.1.2 Temperature Sensors Extreme high and low temperatures can cause significant damage if they go unnoticed. There are twelve temperature sensors at key points in the enclosure.
8.1.3 Voltage Sensors Voltage sensors make sure that the array’s voltage is within normal ranges. The voltage components differ for the SANnet II 200 FC, SATA, and SATA SE arrays. The following tables describe each voltage sensor. Table 8-3 Voltage Sensors for FC Arrays Element ID Description Location Alarm Condition 0 Voltage Sensor 0 Left Power Supply (5V) < 4.00V or > 6.00V 1 Voltage Sensor 1 Left Power Supply (12V) < 11.00V or > 13.00V 2 Voltage Sensor 2 Right Power Supply (5V) < 4.
Table 8-4 Voltage Sensors for SATA and SATA SE Arrays (Continued) Element ID Description Location Alarm Condition 4 Voltage Sensor 4 Upper I/O Module (1.8V) < 1.71V or > 1.89V 5 Voltage Sensor 5 Upper I/O Module (2.5V) < 2.25V or > 2.75V 6 Voltage Sensor 6 Upper I/O Module (3.3V) < 3.00V or > 3.60V 7 Voltage Sensor 7 Upper I/O Module (1.812V)1 < 1.71V or > 1.89V 8 Voltage Sensor 8 Upper I/O Module (Midplane 5V) < 4.00V or > 6.
Note – It is important to know the cause of the error condition because how you silence the alarm depends on the cause of the alarm. To silence the alarm, perform the following steps: 1. Check the error messages, event logs, and LED activity to determine the cause of the alarm.
2. Depending on whether the cause of the alarm is a failed component or a controller event and which application you are using, silence the alarm as specified in the following table. Table 8-6 Silencing Alarms Cause of Alarm To Silence Alarm Failed Component Alarms Use a paper clip to push the Reset button on the right ear of the array. Controller Event Alarms Using the controller firmware: From the Main Menu, choose system Functions →Mute beeper.
■ The surviving controller sends event messages announcing the controller failure of the other controller. A “Redundant Controller Failure Detected” alert message is displayed and written to the event log. If one controller in the redundant controller configuration fails, the surviving controller takes over for the failed controller until it is replaced.
If a double drive failure has occurred, it might be possible to recover by performing the following steps: 1. Discontinue all I/O activity immediately. 2. To cancel the beeping alarm, from the controller firmware’s Main Menu, choose system Functions →Mute beeper. See “Silencing Audible Alarms” on page 8-5 for more information about silencing audible alarms. 3. Physically check that all the drives are firmly seated in the array and that none have been partially or completely removed. 4.
■ If the status is still “FATAL FAIL,” you might have lost all data on the logical drive, and it might be necessary to re-create the logical drive. Proceed with the following procedures: a. Replace the failed drive. Refer to the SANnet II Family FRU Installation Guide for more information. b. Delete the logical drive. Refer to the SANnet II Family RAID Firmware User’s Guide for more information. c. Create a new logical drive. Refer to the SANnet II Family RAID Firmware User’s Guide for more information.
8.7 Troubleshooting Flowcharts This section provides troubleshooting flowcharts to illustrate common troubleshooting methods. The flowcharts included in this section are: ■ “Power Supply and Fan Module” on page 8-11 ■ “Drive LEDs” on page 8-13 ■ “Front-Panel LEDs” on page 8-16 ■ “I/O Controller Module” on page 8-21 For the JBOD and expansion unit flowchart, see “Troubleshooting SANnet II 200 FC JBOD Arrays” on page B-12. For overview information about LEDs, see Chapter 6.
1A Power supply or fan problem Notes A fan can continue to spin normally even when a power supply has failed. Prior to replacing a chassis, try the following: --Reseat the FRU that is not operating correctly. --Swap the questionable FRU with a known-good FRU from the same array. Front panel power LED amber? Yes Check power supply LEDs. Replace chassis. End No Both green? Is the LED ribbon cable on the right ear loose? Yes Yes Secure the ribbon cable.
1B Power supply or fan problem Power supply module LED amber? Yes Is the power cord connected? No Plug it in. Resolved? Yes Yes End Yes End No Is the power supply module completely seated and the power switch turned on? No Reseat the module and turn on the switch. Resolved? Yes No No Is the fan spinning? No Try a known good power supply module in that slot. Resolved? Yes End No Yes Replace chassis.
For overview information about drive LEDs and how they work, see “Front-Panel LEDs” on page 6-2. You can check physical drive parameters using the firmware application. From the firmware Main Menu, choose view and edit scsi drives. For more information about the firmware application, refer to the SANnet II Family RAID Firmware User’s Guide. Caution – When you rotate or replace drives, make sure that: - All I/O is stopped.
2A Drive LEDs problem (FC) Is only one drive LED amber? Yes Check View and Edit SCSI drives menu. Is drive displayed? No All drive LEDs amber? No Power off. Move drive to new slot. Power on. Check drive to see if it is displayed. Yes Rotate drive into another slot. Yes Yes Replace chassis. No Does drive show bad? Refer to FRU Installation Guide for instructions. No Does problem follow drive? Yes No No Replace drive.
2B Drive LEDs problem (FC) Remove the right end cap. All front panel LEDs flashing amber? Yes Check that the Reset button is not jammed. LEDs stop flashing? Check that LED ribbon cable in right ear is not loose. Refer to FRU Installation Guide for instructions Replace chassis. No Replace the end cap. Yes No Are all the LEDs off during operation? End Yes Is the power switch on? Yes Is the power connected? Yes Is the power cord well seated? No No No Turn it on. Connect it. Seat it.
3A Front panel LEDs problem (FC) Adjust end cap to ensure reset button is not depressed. All front panel LEDs flashing amber? Remove the right end cap. Yes Check that the Reset button is not jammed. Check that LED ribbon cable in right ear is not loose. Replace the end cap. No Yes LEDs stop flashing? No Refer to FRU Installation Guide for instructions Replace chassis.
3B Front panel LEDs problem (FC) Front panel power LED amber? Yes No Front panel fan Yes LED amber? Yes Are both power switches on? Yes Is the power connected? Yes Are the power cords well seated? No No No Turn them on. Connect them. Seat them. Is either power/cooling FRU LED amber? Yes Replace FRU. Yes Is either power/cooling FRU LED amber? No Is the LED ribbon cable on the right ear loose? Yes Replace FRU.
3C Front panel LEDs problem (FC) Is Temp LED amber? Yes Is Fan LED amber also? Check temperature in Event Log messages. No Go to 3D. No Yes Yes Follow procedure for "Fan LED amber?" on 9B. Is the ambient temp. within environmental limits? Check that LED ribbon cable in right ear is not loose. No No Is event LED amber? No Yes Resolved? Resolved? Yes Yes End End No Replace chassis. Check for any amber LEDs in back panel.
Notes 55 degrees Celsius equals 131 degrees Fahrenheit. 3D Front panel LEDs problem (FC) Prior to replacing a chassis, try the following: --Reseat the FRU that is not operating correctly. --Swap the questionable FRU with a known-good FRU from the same array. Verify the air conditioning is working properly. Fix if needed. Temp LED Resolved? No Ensure adequate ventilation. Resolved? Yes End Yes End Yes End No Check that LED ribbon cable in right ear is not loose.
8.7.4 I/O Controller Module The following flowchart provides troubleshooting procedures for the I/O controller module. 4A I/O controller module problem (FC) SFP Link LED amber? Yes Replace SFP with known good SFP. Try a known good HBA. Replace the cable. No No No RAID controller 2 status amber? Yes Replace I/O controller module. No Resolved? Resolved? Resolved? Yes Yes Yes End End End Power off. Check event messages in firmware or software messages. Replace I/O controller module.
8-22 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
APPENDIX A SANnet II 200 FC, SATA, and SATA SE Array Specifications This appendix provides the specifications for the SANnet II 200 FC, SATA, and SATA SE arrays. The topics covered are: ■ “Physical Specifications” on page A-1 ■ “SANnet II 200 FC, SATA, and SATA SE Array Highlights” on page A-2 ■ “Agency Approvals and Standards” on page A-4 A.1 Physical Specifications Table A-1 SANnet II 200 FC, SATA, and SATA SE Array Physical Specifications Description Desktop Rackmount Height 3.64 in. / 9.
Table A-1 SANnet II 200 FC, SATA, and SATA SE Array Physical Specifications (Continued) Description Desktop Rackmount Weight (fully loaded FC expansion unit) 56.6 lb / 25.7 kg with 36-GB drives 53.9 lb / 24.4 kg with 73-GB drives 54.9 lb / 24.9 kg with 146-GB drives 60.6 lb / 27.5 kg with 36-GB drives 57.9 lb / 26.3 kg with 73-GB drives 58.9 lb / 26.7 kg with 146-GB drives Weight (fully loaded SATA array) 59 lb / 26.8 kg with 250-GB drives 61.6 lb / 27.9 kg with 400-GB drives 63 lb / 28.
Table A-2 SANnet II 200 FC, SATA, and SATA SE Array Highlights (Continued) Feature Description Density • • • • • • Up to 1752 GB in a RAID array (with 146-GB drives) Up to 4800 GB in a RAID array (with 400-GB drives) 21 in. (53.
A.2.3 Firmware LUN Filtering (RAID-Based Mapping) LUN filtering is a method used for separating and controlling access to data from the RAID controller. One major benefit of Fibre Channel is the capability to share a common storage pool with multiple servers or workstations. However, allocation becomes an issue when every server in a network can access the data in a logical drive. LUN filtering provides a means for controlling data access if data is not allowed for every server.
Table A-3 SANnet II 200 FC, SATA, and SATA SE Array Product Safety & Electromagnetic Standards (Continued) Product Safety Standard Australia Part of World-wide CB Scheme Argentina Resolution 92-98 (S-Mark) Germany GS mark (ergonomics) (Rheinland) Russia Part of World-wide CB Scheme (GOST-R mark) Russia Hygienic Mark (ergonomics) Electromagnetic Compatibility Standard Country U.S.
A-6 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
APPENDIX B Using a Standalone JBOD Array (SANnet II 200 FC Array Only) A single SANnet II 200 FC JBOD array can be connected directly to certain Solaris operating system hosts. This appendix describes the use of SANnet II 200 FC JBOD arrays. Note – SANnet II 200 SATA and SATA SE configurations do not support the use of JBOD arrays.
B.2 Supported Operating Systems (JBOD Arrays) The SANnet II 200 FC JBOD array can be used with currently released versions of the Solaris 8, Solaris 9, and Solaris 10 operating systems. B.3 Supported Host Platforms and Connection Methods (JBOD Arrays) Table B-1 lists the Sun systems that are supported by the JBOD array. The table also shows the connection methods supported for each of the supported Sun systems. Supported HBAs include (X)6767A 2-Gbit PCI Single FC HBA and (X)6768A 2-Gbit PCI Dual FC HBA.
■ ■ ■ SANscape software supports FC JBOD arrays. However, since FC JBOD arrays do not have a RAID controller to manage the disks, this software support is necessarily limited. Monitoring functionality that does not require a RAID controller works the same way it does for RAID arrays. See “Using SANnet II Family Software Monitoring and Management Tools with JBOD Arrays” on page B-3 for more specific information.
B.5.1.1 Enabling JBOD Support To monitor peripheral device conditions and events on a SANnet II 200 FC JBOD array from SANscape, you first need to enable JBOD support. See “Enabling SANnet II 200 FC JBOD Array Support” on page B-10 for the procedure for enabling JBOD support. B.5.2 SANscape Alert SANscape Alert supports standalone JBOD arrays. However, triggered event notification is limited to environmental failures and hard drive failures. B.5.3 SANscape CLI The SANscape CLI supports JBOD arrays.
Press to change the ID number Figure B-1 ID Switch By default, the ID switch on all SANnet II 200 FC JBOD arrays is set to 1 so the range of IDs is automatically 16 to 31. You can leave the ID switch set to 1, or set it for whichever range of IDs you prefer. The ID switch offers eight ID ranges. Each set contains 16 IDs. The last 4 IDs in each range are ignored. These ranges are shown in Table B-2. Table B-2 ID Switch Settings for SANnet II 200 FC JBOD Arrays B.6.
Caution – The loop ID should only be changed while the JBOD array is powered off or not in use. After changing the loop ID, a power cycle is required to make the ID switch change take effect. Failure to cycle the power following an ID switch change can lead to unexpected results. 4. Reattach the plastic ear cap and the bezel on the front of the chassis. B.7 Connecting SANnet II 200 FC JBOD Arrays You can connect a SANnet II 200 FC JBOD array directly to a host server.
Host computer JBOD array Figure B-2 SANnet II 200 FC JBOD Array Attached to a Single HBA Port In this example, if the loop ID switch is set to 0, the format command shows 12 drives on this loop, ranging from c1t0d0 to c1t11d0.
Figure B-3 shows an example of a SANnet II 200 FC JBOD array with 12 drives, connected to a host computer over two loops to two FC ports. In this example, both ports are on dual-port HBAs. Host computer JBOD array Figure B-3 SANnet II 200 FC JBOD Array Attached to Two HBA Ports When you connect your SANnet II 200 FC JBOD array to a host over two loops, the format command shows 24 drives, 12 on each loop, because the host sees a device entry for each path.
Table B-4 Example of 24 Drives Shown on a 12-Disk SANnet II 200 FC JBOD Array Connected to a Host Over Two FC Loops Drive Identifier (First Loop) Drive Identifier (Second Loop) c1t0d0 c2t0d0 c1t1d0 c2t1d0 c1t2d0 c2t2d0 c1t3d0 c2t3d0 c1t4d0 c2t40d0 c1t5d0 c2t5d0 c1t6d0 c2t6d0 c1t7d0 c2t7d0 c1t8d0 c2t8d0 c1t9d0 c2t9d0 c1t10d0 c2t10d0 c1t11d0 c2t11d0 Caution – Be careful not to mount the same drive twice if you are not using multipathing software. B.7.
1. Connect a fiber-optic cable to an HBA. 2. Set your loop IDs using the ID switch on the JBOD array. Caution – The loop ID should only be changed while the JBOD array is powered off or not in use. After changing the loop ID, a power cycle is required to make the ID switch change take effect. Failure to cycle the power following an ID switch change can lead to unexpected results. 3.
4. Click OK. The JBOD array is displayed in the main window. In a single-bus configuration, both ports of the JBOD array are connected to one HBA on the server, as shown in the following example:. In a split-bus configuration, each port is connected to its own HBA, as shown in the following example: B.
B.10 Resizing LUNs Greater Than 1 Tbyte When a LUN is created larger than 1 Tbyte, the Solaris operating system identifies the LUN as an EFI drive. If the LUN is later rebuilt to less than 1 Tbyte, it retains the EFI label. If you want the LUN to revert back to SMI labeling, the format -e | label command is required. To relabel a LUN to less than 1 Tbyte, perform these steps: Note – In this example, the LUN being relabeled is c1t2d3. 1. Type the format command in a terminal window:.
B.11.1 Troubleshooting Configuration Issues Follow this sequence of general steps to isolate software and configuration issues. 1. Look for storage-related messages in /var/adm/messages and identify any suspect SANnet II 200 FC JBOD arrays and fibre loops. 2. Check your SANscape console for alerts or messages. 3. Check revisions of software package, patches, and hardware. 4. Verify correct device file paths. B.11.
■ ■ SANscape CLI event log For expansion units, the RAID firmware event log For more information about replacing the chassis, I/O module, or controller, refer to the SANnet II Family FRU Installation Guide. Caution – When you rotate or replace drives, make sure that: - All I/O is stopped. - The Periodic Drive Check Time setting in the firmware application is set to disabled (this is the default setting). This prevents automatic drive rebuild, which is not recommended for live systems or troubleshooting.
5A JBOD or expansion unit problem (FC) Drive light amber? Yes Replace drive with knowngood drive. Resolved? No Switch drive with known drive from another slot. Is the drive light green in new slot? Replace drive again. No Yes Yes No End Is the drive light green in the original slot? I/O expansion module LED amber Yes Check event messages in firmware or software. Yes End Go to 11B No Replace chassis. End No SFP link status amber? 2 Yes Check for proper cabling.
5B JBOD or expansion unit problem (FC) Has a controller failure occurred? Yes Replace I/O expansion module. Resolved? No Possible midplane failure. Replace chassis. Yes No End Has a data error occurred? Yes Correct data error. End End No Switch controller with know good controller. Resolved? Yes End No Replace chassis. Notes Prior to replacing a chassis, try the following: --Reseat the FRU that is not operating correctly.
APPENDIX C Failed Component Alarm Codes This appendix describes failed component alarm codes. Failed component alarm codes use Morse code dot and dash characters. The dot “.” is a short tone sounding for one unit of time. The dash “-” is a long tone sounding for three units of time. Alarms, also referred to as beep codes, are presented in a sequence, starting with the critical component failure alarm, which alerts you to a component problem or failure or a firmware mismatch.
See “Front-Panel LEDs” on page 6-2 for more information about the SES/PLD firmware mismatch mentioned in Table C-1. Caution – Be particularly careful to observe and rectify a temperature failure alarm. If you detect this alarm, shut down the controller and the server as well if it is actively performing I/O operations to the affected array. Otherwise, system damage and data loss can occur.
APPENDIX D Cable Pinouts This appendix identifies the pinouts for each connector used in the SANnet II 200 FC, SATA, and SATA SE arrays. Topics covered are: ■ “RJ-45 Connector” on page D-1 ■ D.1 “DB9 COM Port” on page D-2 RJ-45 Connector Figure D-1 Ethernet RJ-45 Socket 10/100BASE-T Table D-1 Ethernet RJ-45 Pin Description Pin No.
Table D-1 Ethernet RJ-45 Pin Description (Continued) D.2 Pin No. Description Color 6 RX – Green 7 Not connected White with brown 8 Not connected Brown DB9 COM Port The COM port is a female DB9 connector that requires a male DB9 null modem cable. Figure D-2 RS-232 DB9 (EIA/TIA 574) View of the Male End Table D-2 Pin Names D-2 Pin No.
APPENDIX E Configuring a Sun Server Running the Solaris Operating System This appendix provides access information and LUN setup information needed when you connect a FC or SATA array to a server running the Solaris operating system. For a list of supported adapters, refer to the SANnet II 200 FC, SATA, and SATA SE Array Release Notes.
COM port COM port Figure E-1 RAID Array COM Port Connected Locally to the Serial Port of a Workstation 2. Power up the array. It can take two or three minutes for both controllers to be initialized before communication is possible over the connection. 3. Set the serial port parameters on the workstation. See “Configuring a Host COM Port to Connect to a RAID Array” on page 4-26 for the parameters to use. E.
E.3 Determining the WWN in the Solaris Operating System Perform the following steps to determine the world wide name (WWN) of a newly installed HBA device. 1. Reboot the computer. 2. Type the following the command: # luxadm probe 3. Scroll down the listing to see the Fibre Channel devices and the related WWNs. Figure E-2 Worldwide Name Information Displayed by the luxadm command.
E-4 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
APPENDIX F Configuring a Microsoft Windows Server This appendix provides platform-specific host installation and configuration information to use when you connect a FC, SATA, or SATA SE array to a host running the Windows 2000 Server, Windows 2000 Advanced Server, Windows 2003 Server, or Windows 2003 Advanced Server operating system. For convenience, these platforms will be referred to collectively in this document as “Windows Windows Server.
Note – A DB9-to-DB25 serial cable adapter is included in your package contents for connecting the serial cable to a DB25 serial port on your host if you do not have a DB9 serial port. 2. Power up the array. 3. On the server, choose Start → Programs → Accessories → Communications → HyperTerminal. 4. Type a name and choose an icon for the connection. 5. In the Connect To window, select the COM port from the Connect using: drop-down menu for that array. 6. Click OK. 7.
■ ■ 1 stop bit No parity 8. To save the connection and its settings, choose File → Save. The connection file name is connection-name where connection-name is the name you gave this HyperTerminal connection in Step 4. 9. To make a connection shortcut on your desktop: a. Choose Start → Find → For Files or Folders. b. Enter connection-name and click the Search Now button. c. Highlight and right-click on the file name in the Search Results window. d. Choose Create Shortcut and click Yes.
F.2 Accessing the Firmware Application From a Microsoft Windows Server To access the array from a Microsoft Windows Server through a serial port, use the HyperTerminal connection you configured in “Setting Up the Serial Port Connection” on page F-1 or install a VT100 terminal emulation program and use the parameters described there. To access the array through an Ethernet connection, follow the procedures in “Setting Up Out-of-Band Management Over Ethernet” on page 4-28.
c. Select the Disk Management folder. d. If a Write Signature and Upgrade Disk Wizard is displayed, click Cancel. A “Connecting to Logical Disk Manager Server” status message is displayed. 4. Select your new device when it is displayed. 5. Right-click in the Unallocated partition of your device to display a pop-up menu. 6. Choose Create Partition from the pop-up menu. The Create Partition wizard is displayed. 7. Select Primary partition and click Next.
8. Specify the amount of disk space to use or accept the default value, and click Next. 9. Assign a drive letter, if desired, and click Next. 10. Select Format this partition with the following settings. a. Specify NTFS as the “File system to use.” b. Make sure the Perform a Quick Format checkbox is selected.
c. Click Next. A confirmation dialog box displays the settings you have specified. 11. Click Finish. The new partition is formatted and the formatted partition is identified as NTFS in the Computer Management window. 12. Repeat Step 5 through Step 11 for any other new partitions and devices you want to format.
F.4 Determining the Worldwide Name for Microsoft Windows Servers Before you can create host filters, you need to know the worldwide name (WWN) for the FC HBA that connects your host to your FC array. 1. Boot a specific host system and note the BIOS version and HBA card models connected to your host. 2. Access the HBA card’s BIOS with the appropriate command (alt-q or control-a are commonly used). If the host has multiple HBA cards, select the card that is connected to the storage. 3.
APPENDIX G Configuring a Linux Server This appendix provides access information and LUN setup information needed when you connect a FC, SATA, or SATA SE array to a server running the Linux operating system. For a list of supported adapters, refer to the SANnet II 200 FC, SATA, and SATA SE Array Release Notes.
1. Use a null modem cable to communicate via the serial port of the array. Connect the serial null modem cable to the array and to ttyS0 (COM1), ttyS1 (COM2), ttyS2 (COM3), or ttyS3 (COM4). Note – A DB9-to-DB25 serial cable adapter is included in your package contents for connecting the serial cable to a DB25 serial port on your host if you do not have a DB9 serial port. 2. Power on the array. 3.
d. If E is not correct, press the letter E and the cursor goes to line E. Backspace and change the line to: 38400 8N1 After you edit the line, press Return and the cursor goes back to the line Change which Settings? e. Set F to no. When pressing F, toggle from yes to no. f. Set G to no. When pressing G, toggle from yes to no. g. Press the Escape key to return to the configuration screen. h. In the configuration menu, use the arrow keys to highlight Save setup as dfl and press Return.
G.3 Checking the Adapter BIOS When booting the server, watch for the HBA card BIOS message line to be displayed. Then press the proper sequence of keys to get into the HBA BIOS ( for FC Qlogic HBAs). The keystrokes are listed on the screen when the adapter is initializing. If your HBA has multiple interfaces on it, they will all show up in the main screen of the BIOS software. You must make the same changes on every interface unless one of the interfaces is going to be bootable.
12. Press Escape until a screen is displayed that says “Configuration setting modified.” Highlight Save changes and press Return. 13. Return to the Fast!UTIL Options. Highlight Scan Fibre Devices and press Return. This menu option scans all 126 channels to see if there are any devices attached; the devices are displayed after the scan. If there are no devices attached, it takes some time to scan. If there are devices attached, the scan usually finds them right away. 14.
1. To list all devices and their paths, start a terminal session and type: fdisk -l Record the device names and paths that you plan to use. 2. Type: fdisk /dev/sd(x) x= a,b,c,... A banner is displayed for the specified array device. The last statement displays a prompt. 3. Type m to display the menu. 4. On the displayed menu, select “n” for the command action and press Return. Two choices are displayed: e extended p primary partition (1-4) Note – Only four primary partitions are allowed per array.
2. Take the device that you ran fdisk on and run the following command to create an ext3 file system: mkfs -t ext3 /dev/sdb(x) where x is the partition on which you are creating a file system. Replace x with 1 because there is only one partition. G.7 Creating a Mount Point and Mounting the File System Manually 1. Go to the directory where you want to create a directory that will be the mount point. Then type the following command: mkdir name where name is the name of the new directory. 2.
3. Save the file. 4. To verify that fstab was set up correctly, type: mount -a If the mount point and the fstab file are correctly set up, no errors are displayed. 5. To verify that the file system is mounted and list all mounted file systems, type: df -k 6. To unmount the file system, type: umount /filesystem-name G.9 Determining the Worldwide Name for Linux Hosts Before you can create host filters, you need to know the worldwide name (WWN) for the FC HBA that connects your host to your FC array. 1.
APPENDIX H Configuring an IBM Server Running the AIX Operating System This appendix provides platform-specific host installation and configuration information to use when you connect an FC or SATA array to an IBM server running the AIX operating system. The SANnet II 200 FC, SATA, and SATA SE arrays support versions 4.3.3 and 5.1L of the IBM AIX operating system in dual-path configurations using SANpath failover drivers for IBM AIX.
If you are planning to access your array over an IP network or through a terminal server and only want to connect through a serial port for the initial configuration of the array, it is not necessary to configure a serial port connection from your IBM host. For convenience, installers frequently perform the initial array configuration using a serial port on a portable computer.
COM port COM port Figure H-1 RAID Array COM Port Connected Locally to the Serial Port of a Host System 2. Power on the array. 3. After the array is powered up, power on the IBM server and log in as root, or become superuser if you are currently logged in as a user. 4. Start the Kermit program and set the parameters as shown. Use the device-specific name for the serial port you are using. In the example, the serial port being configured is /dev/tty0p1. # kermit Executing /usr/share/lib/kermit/ckermit.
H.3 Identifying the Device on Which You Will Create a Logical Volume 1. Display all the defined disk devices on your system. # lsdev -Cc disk A list of defined disk devices is displayed along with information about those devices. 2. Identify the name of the device on which you want to create a logical volume, for example, hdisk7. 3. Verify that the disk you’ve identified is the one you want. # lscfg -v -l device-name Detailed information about the device you specified is displayed. 4.
2. Choose System Storage Management (Physical and Logical Storage) from the System Management menu. 3. Choose Logical Volume Manager from the System Storage Management menu. The Logical Volume Manager menu is displayed on the Logical Volume Manager screen. You will be using menu options from this menu to create a volume group and then a logical volume within this volume group.
7. Choose Activate a Volume Group from the Volume Groups menu. 8. Next to VOLUME GROUP name, type the name you gave the volume group. When the volume group is activated, a status screen displays “Command: OK.” H.6 Creating a Logical Volume 1. Return to the Logical Volume Manager screen. 2. Choose Logical Volumes from the Logical Volume Manager menu to display the Logical Volumes screen. 3. Choose Add a Logical Volume from the Logical Volumes menu to display the Add a Logical Volume screen. 4.
7. Move the cursor to highlight the name of the volume group you created in “Creating a Volume Group” on page H-5. The Add a Standard Journaled File System screen is displayed. 8. Specify the size of the file system you want to create by typing the number of blocks you want next to SIZE of file system (in 512-byte blocks). 9. Next to MOUNT POINT, type the directory name (and path, if desired) on which you want to mount the new file system. Note – If the mount point directory does not exist, it is created.
3. Display the attributes of the new file system. # H.10 df -k mount-point Determining the Worldwide Name for IBM Servers Running AIX Before you can create host filters, you need to know the worldwide name (WWN) for the FC HBA that connects your host to your FC array. For supported IBM HBAs, perform these steps: 1. Determine the device name by typing the command: # lscfg | grep fc 2. Type the following command: # lscfg -vl device-name Output similar to the following is displayed.
APPENDIX I Configuring an HP Server Running the HP-UX Operating System This appendix provides platform-specific host installation and configuration information to use when you connect a FC or SATA array to an HP server running the HP-UX operating system. The FC, SATA, and SATA SE arrays support the HP-UX operating system Level 11.0 and Level 11.i in dual-path configurations using multipath failover drivers for the HPUX operating system.
If you are planning to access your array over an IP network or through a terminal server and only want to connect through a serial port for the initial configuration of the array, it is not necessary to configure a serial port connection from your HP host. For convenience, installers frequently perform the initial array configuration using a serial port on a portable computer.
COM port COM port FIGURE I-1 RAID Array COM Port Connected Locally to the Serial Port of a Host System 2. Power on the array. 3. After the array is powered up, power on the HP server and log in as root, or become superuser if you are logged in as a user. 4. Start the Kermit program and set the parameters as shown. Use the device-specific name for the serial port you are using. In the example, the serial port being configured is /dev/tty0p1. # kermit Executing /usr/share/lib/kermit/ckermit.ini for UNIX..
I.3 Attaching the Disk Array The simplest way to configure a disk array is to use System Administration Manager (SAM), HP-UX’s system administration tool. If SAM is not installed on your system, or if you prefer to use the command-line interface, the following procedures guide you through the task. For more information, consult the HP document, Configuring HP-UX for Peripherals: 1. Use the ioscan command to determine what addresses are available on the HBA to which you will be attaching the array. 2.
As with many system administration tasks, you can use SAM to create and maintain logical volumes. However, some functions can only be performed with HP-UX commands. The procedures in this appendix are performed using the command-line interface rather than SAM. I.5 Definitions of Common Terms Volume groups are HP-UX’s method for dividing and allocating disk storage capacity. Volume groups can be used to subdivide a large partition of storage into smaller units of usable space called logical volumes.
3. Initialize each partition as an LVM disk with the pvcreate command. For example, type: # pvcreate /dev/rdsk/c12t6d2 Caution – This process results in the loss of any data that resides on the partition. I.7 Creating a Volume Group The volume group contains the physical resources that you can use to create usable storage resources for your applications. 1.
VG Write Access VG Status read/write available Max LV 255 Cur LV 0 Open LV 0 Max PV 16 Cur PV 1 Act PV 1 Max PE per PV VGDA PE 2167 2 Size (Mbytes) 4 Total PE 2167 Alloc PE 0 Free PE Total 2167 PVG 0 In the output of vgdisplay, the Total PE field displays the number of physical extents in the volume group.
Both character and block device files for the new logical volume are created in the volume group directory: # ls /dev/vg02 group lvol1 rlvol1 Applications should use these names to access the logical volumes. Unless you specify otherwise, HP-UX creates names in the form shown in the example. To specify custom names for logical volumes refer to vgcreate(1M). I.9 Creating an HP-UX File System The following command creates a file system on the logical volume created in the previous steps. # I.
2. To include the file system created in the example, add the following line to the file /etc/fstab: /dev/vg0mynewvg/lvol1 /usr/local/myfs vxfs delaylog 0 2 Refer to the entry for fstab(4) for details about creating /etc/fstab entries. 3. To check to see if fstab was set up correctly, type: # mount -a If the mount point and the fstab file are correctly set up, no errors are displayed. 4. To verify that the file system is mounted and list all mounted file systems, type: # bdf 5.
2. Type: # fcmsutil/device-name/ Output similar to the following is displayed: The Node worldwide name shown is the WWN you use when configuring the RAID controller.
Index A address IP 4–25 agent Agent Options Management window B–10 alarms failed component description C–1 silencing 8–6 amber blinking on Event LED 6–4 arbitrated loop physical address A–3 array connecting 4–1 mounting 3–3 B battery 7–4 date code 7–4 description 1–10 shelf life 7–4 when to change 7–4 battery operation 7–4 baud rate 4–26 beep codes muting 8–6 bus adapter connecting to 4–31 C cable pinouts pinouts cable D–1 cables customer-provided 3–3 standard package 3–3 cabling cables supplied 3–2 Ethe
Solaris E–1 Windows F–1 Windows 2000 server or Windows 2000 Advanced server F–1 connecting an expansion unit B–6 chassis to an AC power outlet 4–7 chassis to DC power outlets 4–9 fibre channel array 4–1 ports to hosts 4–31 SFPs to SFP Ports 4–24 SFPs to SFP ports B–9 connection in-band 7–2 controller failover 8–7 failure 8–8 customer obligations 2–1 customer-provided cables 3–3 cabling to B–6 F DB9 COM port D–2 DHCP 4–25, 4–27 DHCP client 4–25 disks not visible 8–7 drive description 1–9 drive channels 4–
host channels 4–16 data transfer speed SANnet II 200 FC Array 4–19 SANnet II 200 SATA Array 4–20 limitations 4–20 host configuration Linux G–1 Solaris E–1 Solaris operating system E–1 Windows F–1 Windows 2000 F–1 host connections 4–31 host LUNs not visible 8–7 host port SANnet II 200 FC Array 4–19 humidity 2–3 limitations host channels 4–20 load balancing A–4 loop id setting on expansion units 4–13, B–4 LUN filtering A–4 LUN mask A–4 LUNs resizing B–12 M map layout 2–4 logical drive A–4 Mounting Your FC A
powering up an array 4–16 Powering Up and Checking LEDs 4–16 power-off procedure 4–33 power-on sequence 4–32 preinstallation worksheet 2–6 Product and Architecture Overview 1–1 protocols Fibre Channel 1–12 R rack-mounting an array cabinet-mounting an array 3–3 RARP 4–27 Rear-Panel LEDs 6–5 Recovering From Fatal Drive Failure 8–8 redundant controller explained 8–8 redundant loops A–4 release notes 1–15 requirements environmental 2–3 Reset button 8–7 reset button pressing 8–10 silencing failed component alar
W Windows accessing firmware from F–4 determining worldwide name F–8 recognizing new devices and LUNs F–4 worksheet preinstallation 2–6 worldwide name determining on Solaris OE E–3 Index 5
6 SANnet II 200 FC, SATA, and SATA SE Array Installation, Operation, and Service Manual • March 2005
