6920 Service Manual

Sun Microsystems, Inc.www.sun.com

Submit comments about this document at: http://www.sun.com/hwdocs/feedback

Sun Confidential: Internal Only

Sun StorEdge™ 6920 SystemTechnician’s Reference Guide

Part No. 817-6499-10May 2004, Revision 01

PleaseRecycle


Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.

Sun StorEdge is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.

Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any.

Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.

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.

Sun, Sun Microsystems, the Sun logo, AnswerBook2, docs.sun.com, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and in other countries.

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and in other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.

U.S. Government Rights—Commercial use. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, Californie 95054, Etats-Unis. Tous droits réservés.

Sun StorEdge sont des marques déposées ou enregistrées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.

Sun Microsystems, Inc. a les droits de propriété intellectuels relatants à la technologie qui est décrit dans ce document. En particulier, et sans la limitation, ces droits de propriété intellectuels peuvent inclure un ou plus des brevets américains énumérés à http://www.sun.com/patents et un ou les brevets plus supplémentaires ou les applications de brevet en attente dans les Etats-Unis et dans les autres pays.

Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a.

Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.

Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.

Sun, Sun Microsystems, le logo Sun, AnswerBook2, docs.sun.com, et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays.

Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.

L’interface d’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique. Sun détient une license non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licence couvrant également les licenciées de Sun qui mettent en place l’interface d ’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun.

LA DOCUMENTATION EST FOURNIE "EN L’ÉTAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE UTILISATION PARTICULIERE OU A L’ABSENCE DE CONTREFAÇON.

Contents

1. Introduction 1

Features 1

Hardware Overview 3

Storage Array Configurations 6

Internal and External Networks 7

Software Overview 8

User Interfaces 8

Resident Software 9

Required Host Software 9

Solaris Host Software 9

Host Software for Other Operating Systems 10

Additional Supported Software 11

Supported Third-Party Software 11

Solaris Driver Stack 12

Predictive Failure Analysis (PFA) Capabilities 12

2. Troubleshooting Tools 13

About the Storage Automated Diagnostic Environment 13

▼ To Log In to the System 14

▼ To Display the Event Log for a Specific Device 15

Contents iii


Using Solution Extract 16

▼ To Run a Solution Extract From the GUI 16

Running Solution Extract from the CLI 19

About Diagnostic Tests 20

Tests Available From the Storage Service Processor 20

Tests Available From Data Hosts 20

▼ To Access the Diagnostic Tests 21

Running Diagnostic Tests 22

▼ To Test From Topology 22

▼ To View a Test’s Man Page From the GUI 24

▼ To Test from List 25

Log Files on the Sun StorEdge 6920 System 27

About SAN Tools 28

3. Basic Troubleshooting Procedures 31

Required Patches and Packages 32

▼ To Check the SAN Foundation Kit Version 32

Data Host Patches 32

▼ To Download the Patches 33

▼ To Install the Patches 34

Maintenance Precautions 34

Reserving the Cabinet for Maintenance 34

Isolating the Problem 35

Troubleshooting the Storage Service Processor 37

Troubleshooting Best Practices 38

Asking Troubleshooting Questions 38

Troubleshooting SAN Connections 39

External Troubleshooting Software 39

Gathering Information 40

iv Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


Asking Troubleshooting Questions 40

Debugging Individual Components via Serial Connections 41

Bootup Events 41

SVD_PATH_FAILOVER Messages 41

boot -r Side Effects 41

4. Troubleshooting Network Components 43

Troubleshooting the 3COM Ethernet Hub 43

Troubleshooting the NetGear Router 44

LED Status 45

▼ To Access the Router 46

Connecting to the Network Terminal Concentrator (NTC) 49

▼ To Connect to the Storage Service Processor From the NTC 49

Common Problems 50

Useful Commands 51

show server Command 52

show ip all Command 53

show port Command 54

5. Troubleshooting Host Devices 55

Host Support 55

Using the Host Event Advisor 56

▼ To Access the Event Advisor for a Host 56

Actionable Events on the Host 58

6. Troubleshooting the Data Services Platform 65

Before You Begin 66

About DSP Chassis LEDs 66

Chassis Status 69

Fan Status 69

Contents v


Power Supply Status 70

About DSP Card LEDs 70

Management Information Card (MIC) Status 70

Switch Fabric Card (SFC) Status 73

Storage Resource Card (SRC) Status 75

SIO Card Status 77

Responding to a DSP Boot-Up Failure 78

Using the Event Advisor for DSP Events 79

▼ To Access the DSP Events 80

7. Troubleshooting Sun StorEdge 6020 Arrays 93

About Sun StorEdge 6020 Arrays 93

Supported Configurations 94

Default Configuration Settings 94

User Interfaces 94

Array Features 95

RAID-Striped Data With Standby Hot Spare 95

LUN Mapping 95

LUN Masking 95

About Expansion Units 96

About Multipathing 96

Manually Halting the I/O 96

▼ To Quiesce the I/O 96

▼ To Unconfigure the Controller/Device Path 97

▼ To Return the Controller/Device Path to Production 97

▼ To View Dynamic Multipathing (DMP) Properties 97

▼ To Return the DMP-Enabled Paths to Production 100

About Array LEDs 100

Array Unit LEDs 101

vi Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


Disk Drive LEDs 102

Power and Cooling Unit LEDs 104

Interconnect Card LEDs 105

Controller Card LEDs 106

Determining FRU Failures 109

Using the Event Advisor fro Array Events 109

▼ To Access Array Events 110

8. About the Storage Service Processor 125

About the Storage Service Processor 125

Storage Service Processor Security 126

Storage Service Processor Accessory Tray 126

Configuration Possibilities 127

9. Replacing the DSP and DSP FRUs 129

Before You Begin 129

Removing and Replacing the Management Interface Card 130

Removing and Replacing the Switch Fabric Card 133

Removing and Replacing the Storage I/O Card 135

Removing and Replacing the Storage Resource Card 137

Removing and Replacing GBICs 141

Removing and Replacing the Power Supply 142

Removing and Replacing the Fan Assembly 144

Installing Additional Storage I/O and Storage Resource Cards 145

Removing and Replacing the DSP Chassis and Midplane 149

▼ To Remove the DSP Chassis 149

Moving the FRUs to the New DSP Chassis 152

▼ To Move the Cards 152

▼ To Move the Power Supplies 153

Contents vii


▼ To Move the Fan Tray Assembly 153

▼ To Move the Chassis Side Rails 154

▼ To Install the New Chassis 154

▼ To Recable the Chassis 154

▼ To Update the Chassis License and Verify the Configuration 155

▼ To Generate a New Inventory 156

10. Replacing Array FRUs 157


Removing and Replacing an Entire Array 158

▼ To Remove the Array Chassis 158

Moving the FRUs to the New Array Chassis 163

▼ To Move the Disk Drives 163

▼ To Move the Interconnect Cards 165

▼ To Move the Controller Card 166

▼ To Move the Power and Cooling Units 168

▼ To Move the Tray Side Rails 170

Installing the New Array Chassis 170

Configuring the Array 173

Installing and Configuring Additional 2X2 Storage Arrays 174

▼ To Add a Storage Array 174

▼ To Configure a New Array 176

Removing and Replacing an Array Disk Drive 177

Removing and Replacing an Array Controller Card 181

Removing and Replacing an Array Loop Card 184

Removing and Replacing an Array Power and Cooling Unit 186

Removing and Replacing the Battery in the Array Power and Cooling Unit 190

Adding Array Capacity 192

Removing Array Capacity 194

viii Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


11. Servicing the Storage Service Processor and USB Flash Disk 197


Removing and Replacing the Storage Service Processor 198

Reloading the Storage Service Processor Image 200

Replacing the USB Flash Disk 201

12. Servicing the Storage Service Processor Accessory Tray 203


Overview of the Storage Service Processor Accessory Tray 204

Overview of the Storage Service Processor Accessory Tray Cables 206

Removing and Replacing the Storage Service Processor Accessory Tray 209

Configuring the NTC 210

Configuring the Router and Firewall 212

13. Servicing the Storage Service Processor Panel 217


Removing and Replacing the Service Panel 218

Removing and Replacing the USB Relay Panel 221

14. Replacing Cabinet Field-Replaceable Units 223


Adding an Expansion Cabinet 224

Connecting the Fibre Channel Cables 224

Connecting the Ethernet Cables 226

Connecting Light-Out Power Management Cables 228

Cabling the Remaining Fibre Channel Connections to the Data Service Platform 231

Identifying a Name for Each New Array 235

Connecting the AC Power Cables 235

Configuring the Arrays in an Expansion Cabinet 237

Contents ix


Removing and Replacing the Rear AC Power Cable 238

Removing and Replacing the Front AC Power Cable 240

Removing and Replacing the Front Power Sequencer 240

Removing and Replacing the Rear Power Sequencer 245

Removing and Replacing the Ethernet Hub in the Main Cabinet 247

Removing and Replacing the Ethernet Hub in an Expansion Cabinet 248

Removing and Replacing the Ethernet Hub Bracket in an Expansion Cabinet 249

Removing and Replacing the Key Switch 250

Removing and Replacing the Front Door 252

▼ To Remove the Front Door: 252

▼ To Replace the Front Door: 252

Removing and Replacing the Back Door 253

▼ To Remove the Back Door: 253

▼ To Replace the Back Door: 253

Removing and Replacing the Side Panel 253

▼ To Remove the Side Panel 253

▼ To Replace the Side Panel 254

15. Extra Options 255


About Lights-Out Power Management 256

Performing a Partial System Shutdown 257

Powering Off the System Partially 257

Performing a Full System Shutdown 259

Restoring Power to the System 262

Restoring Power to the System After a Partial System Shutdown 262

Restoring Power to the System After a Full System Shutdown 263

Troubleshooting Tips 264

Common problems: 265

x Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


Adding and Removing Lights-Out Power Management 265

▼ To Prepare the System for Remote Power 265

▼ To Enable the SW Support for Lights Out Operation 269

▼ To Remove Remote Lights-out Management 271

▼ To Disable the Software Support for Lights Out Operation 272

Adding and Removing an External Modem 274

▼ To Add an External Modem 274

▼ To Remove an External Modem 276

Using the Special Service Cable for Diagnostics (Base Cabinet) 276

Using the Special Service Cable for Diagnostics (Expansion Cabinet) 278

A. Connecting SAN and DAS Hosts and Allocating Ports 281

About Connecting Hosts 281

Connecting Hosts to a SAN 282

Connecting DAS Hosts 284

Selecting Ports for Additional Host Connections 284

Selecting Ports for Additional Storage Connections 286

B. Unconfiguring and Restoring the Service Processor Configuration 289

Unconfiguring the Service Processor 289

Restoring the Service Processor Configuration 294

C. Solution Extract from the Command Line 299

Running Solution Extract from the CLI 299

Viewing the Contents of the Extract File 300

▼ To View Array-Specific Information 301

▼ To View DSP-Specific Information 302

▼ To View Storage Automated Diagnostic Environment-Specific Information 303

▼ To View Service Processor-Specific Information 303

Contents xi


Running Solution Extract from Storage Automated Diagnostic Environment 303

D. Storage Profiles 305

Glossary 309

Index 1

xii Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


Figures

FIGURE 1-1 Sun StorEdge 6920 System Base Cabinet – Front and Back Views 3

FIGURE 1-2 Array Configuration Options 6

FIGURE 2-1 Sun Web Console Login Page 14

FIGURE 2-2 Sun Web Console Page 15

FIGURE 2-3 Solution Extract Page 17

FIGURE 2-4 Test From List Page 21

FIGURE 2-5 Test From Topology Page 23

FIGURE 2-6 Accessing a Test’s Man Page 24

FIGURE 2-7 Sample Test Man Page 25

FIGURE 2-8 Test From List Page 26

FIGURE 5-1 Host Event Advisor 57

FIGURE 6-1 Front View of the Data Services Platform 67

FIGURE 6-2 Back View of the Data Services Platform 68

FIGURE 6-3 Management Information Card 70

FIGURE 6-4 Switch Fabric Card 74

FIGURE 6-5 Storage Resource Card 76

FIGURE 6-6 Storage Input/Output Card 78

FIGURE 6-7 Event Advisor Showing DSP Events 80

FIGURE 7-1 Array Unit SIS LEDs 101

FIGURE 7-2 Disk Drive LEDs 102

Figures xiii


FIGURE 7-3 Power and Cooling Unit LEDs 104

FIGURE 7-4 Interconnect Card LEDs 105

FIGURE 7-5 Controller Card SIS LEDs 107

FIGURE 7-6 Controller Card Communication Channel LEDs 107

FIGURE 7-7 Event Advisor Showing Array Events 110

FIGURE 9-1 Releasing a MIC From the DSP 131

FIGURE 9-2 Releasing the SFC From the DSP 134

FIGURE 9-3 Releasing a SIO Card From the DSP 136

FIGURE 9-4 Releasing an SRC From the DSP 139

FIGURE 9-5 Removing a GBIC 141

FIGURE 9-6 Installing the New Power Supply 143

FIGURE 9-7 Loosening and Removing the Fan Tray Assembly 145

FIGURE 9-8 Installing the SIO Card in the DSP 146

FIGURE 9-9 Installing the SRC 148

FIGURE 10-1 Removing the Chassis Tray Screws 161

FIGURE 10-2 Removing the Four Front Screws That Secure the Tray to the Cabinet 162

FIGURE 10-3 Disk Drive Removal 163

FIGURE 10-4 Disk Drive Numbering 164

FIGURE 10-5 Location of Screws on Interconnect Cards 165

FIGURE 10-6 Removing the Interconnect Card 166

FIGURE 10-7 Controller Card Location 167

FIGURE 10-8 Removing the Controller Card 167

FIGURE 10-9 Location of Power and Cooling Units 168

FIGURE 10-10 Removing the Power and Cooling Unit 169

FIGURE 10-11 Aligning the Tray and Cabinet Rails to Insert the New Tray 170

FIGURE 10-12 Inserting the New Tray and Securing it to the Cabinet With the Four Screws 171

FIGURE 10-13 Securing the Tray Rails to the Back of the Cabinet With the Four Screws 172

FIGURE 10-14 Interconnect Card Cable Locations. 175

FIGURE 10-15 Disk Drive Location. 178

FIGURE 10-16 Disk Drive Latch Release 179

xiv Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


FIGURE 10-17 Controller Card Location 181

FIGURE 10-18 Removing the Controller Card 182

FIGURE 10-19 Interconnect Card Locations 184

FIGURE 10-20 Removing the Interconnect Card 185

FIGURE 10-21 Power and Cooling Unit Locations 187

FIGURE 10-22 Removing the Power and Cooling Unit 188

FIGURE 10-23 Removing the Battery Unit 189

FIGURE 12-1 Storage Service Processor Accessory Tray Connections 206

FIGURE 12-2 Internal Layout of the Storage Service Processor Accessory Tray 208

FIGURE 13-1 View of the Back of the Service Panel 219

FIGURE 14-1 Connecting EXP1 A FC1 and EXP1 A FC2 of the Base Cabinet to EXP A and EXP B of the First Expansion Cabinet 225

FIGURE 14-2 Connecting EXP2 B FC1 and EXP2 B FC2 of the Base Cabinet to EXP A and EXP B of the second expansion cabinet. 226

FIGURE 14-3 Ethernet Cable Connections for Adding the First Expansion Cabinet to the Base Cabinet 227

FIGURE 14-4 Ethernet Cable Connections for Adding the First and Second Expansion Cabinets to the Base Cabinet 228

FIGURE 14-5 Lights-Out Power Management Cable Connections Between the First Expansion Cabinet and the Base Cabinet 229

FIGURE 14-6 Lights-Out Power Management Cable Connections Between the First Expansion Cabinet and the Second Expansion Cabinet 230

FIGURE 14-7 Example of Base Cabinet and One Expansion Cabinet with Four 2x4s 232

FIGURE 14-8 SIO Card Ports Connections for Example Configuration of Base Cabinet and One Expansion Cabinet with four 2X4s 233

FIGURE 14-9 Example of Base Cabinet and One Expansion Cabinet with Nine 2x2s 234

FIGURE 14-10 SIO Card Ports Connections for Example Configuration of Base Cabinet and One Expansion Cabinet with Nine 2X2s 235

FIGURE 14-11 Connecting the AC Power Cable 236

FIGURE 14-12 Removing the Power Cable From the Power Sequencer 239

FIGURE 14-13 Disconnecting the Key Switch Interface Cable Between the Front and Rear Power Sequencers 242

FIGURE 14-14 Disconnecting and Removing the Power Sequencer from the Cabinet Frame 243

FIGURE 14-15 Ethernet Hub and Bracket Assembly in an Expansion Cabinet 248

Figures xv


FIGURE 14-16 Key Switch Cable Connector Location Between the Front and Rear Power Sequencers 250

FIGURE 14-17 Removing and Replacing the Key Switch From the Key Switch Panel 251

FIGURE 14-18 Side Panel Removal 254

FIGURE 15-1 General Settings Page: System Partial Shutdown Button 258

FIGURE 15-2 General Settings Page: Confirm Partial Shutdown 258

FIGURE 15-3 General Settings Page: System Shutdown Button 260

FIGURE 15-4 General Settings Page: Confirm Full Shutdown 261

FIGURE 15-5 AC Power Sequencer Control Panel: Power Off 261

FIGURE 15-6 General Settings Page: System Power Up Button 262

FIGURE 15-7 View of the Back of the Master Service Panel 266

FIGURE 15-8 Lights-Out Power Management Cable Connections Between the Base Cabinet and the First Expansion Cabinet 267

FIGURE 15-9 Lights-Out Power Management Cable Connections Between the First Expansion Cabinet and the Second Expansion Cabinet 268

FIGURE 15-10 Disconnecting the RJ-45 Cable From the DB-9/RJ-45 Adaptor 274

FIGURE 15-11 Connecting the RJ-45 Cable to the AUX Port on the Service Processor Panel 275

FIGURE 15-12 Connecting the RJ-45 Cable to the 6020 Array 277

FIGURE 15-13 Connecting Hosts to a SAN 283

FIGURE 15-14 Connecting Hosts Directly 284

xvi Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


Tables

TABLE 1-1 System Hardware Components 5

TABLE 1-2 Storage Array Configuration Options 6

TABLE 1-3 Internal and External LANs 7

TABLE 1-4 Resident (Pre-installed) System Software 9

TABLE 1-5 Solaris Driver Stack 12

TABLE 2-1 Components of Sun StorEdge 6920 Systems 18

TABLE 2-2 Log Files on the Sun StorEdge 6920 System 27

TABLE 2-3 Miscellaneous SAN Tools and Scripts 28

TABLE 3-1 Data Host Patches 33

TABLE 3-2 Storage Service Processor Troubleshooting Questions 38

TABLE 3-3 Host-Side Troubleshooting Questions 40

TABLE 4-1 Router LEDs 45

TABLE 5-1 Actionable Host Events 58

TABLE 6-1 LED Status Examples 66

TABLE 6-2 Chassis LEDs 69

TABLE 6-3 Fan Assembly LEDs 69

TABLE 6-4 Power Supply LEDs 70

TABLE 6-5 MIC Ready, Power, Redund and Attention LEDs 71

TABLE 6-6 MIC Act 1 LED 72

TABLE 6-7 MIC Act 2 LED 73

Tables xvii


TABLE 6-8 MIC Link LED 73

TABLE 6-9 SFC Ready, Power, Redund, and Attention LEDs 74

TABLE 6-10 SRC Ready, Power, Sync and Attention LEDs 76

TABLE 6-11 SIO Card Link LED 78

TABLE 6-12 SIO Card Act LED 78

TABLE 6-13 Storage Automated Diagnostic Environment Service Advisor for the Data Service Processor 81

TABLE 7-1 Array Unit SIS LEDs 101

TABLE 7-2 Disk Drive LEDs 103

TABLE 7-3 Power and Cooling Unit LEDs 104

TABLE 7-4 Interconnect Card SIS LEDs 106

TABLE 7-5 Interconnect Card Channel Status LEDs 106

TABLE 7-6 Controller Card SIS LEDs 108

TABLE 7-7 FC-AL Channel-Status LEDs 108

TABLE 7-8 Ethernet Channel-Status LEDs 109

TABLE 7-9 Actionable Array Events 111

TABLE 12-1 Sun StorEdge Remote Response Program Service Panel Cabling 206

TABLE 12-2 Factory Settings 209

TABLE 14-1 Expansion Cabinet Ethernet Ports 227

TABLE 14-2 Light-Out Power Management Cabling from Base to First Expansion Cabinet 229

TABLE 14-3 Light-Out Power Management Cabling from the First to the Second Expansion Cabinet 230

xviii Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


Preface

The Sun StorEdge 6920 Technician’s Reference Guide is a combination maintenance and troubleshooting guide for the Sun StorEdgeTM 6920 system. It provides information about troubleshooting and maintaining the various components of the Sun StorEdge 6920 system. For detailed configuration information, refer to the online help system.

The document is for internal use only by Sun field service and technical service personnel, who have been fully trained on all the components in the configuration.

Before You Read This BookIn order to fully use the information in this document, you should be trained and certified by Sun to install and service Sun StorEdge products, and you should be familiar and experienced with:

■ The 6020/6120 storage sub-systems■ The Solaris™ Operating System (Solaris OS)■ Multipathing and failover■ Storage virtualization■ Storage area networks (SANs)■ Using command-line interfaces (CLIs)■ Using web-browser interfaces

xix


How This Book Is OrganizedThis book contains the following chapters:

Chapter 1 introduces the Sun StorEdge 6920 system.

Chapter 2 presents information about tools used to troubleshoot, including the Storage Automated Diagnostic Environment (diagnostic tests, Solution Extract, and topology), and commands from the command-line interface (CLI).

Chapter 3 offers general troubleshooting guidelines. Sections for information gathering, troubleshooting questions, and problem isolation are presented for both Storage Service Processor and hosts.

Chapter 4 discusses network components including the 3COM Ethernet hub, the NetGear Router, and the Network Terminal Concentrator (NTC). Information associated with the 3COM Ethernet hubs is limited in this guide, however, because 3COM does not allow duplication of its information.

Chapter 5 provides information about host device troubleshooting.

Chapter 6 provides how to troubleshoot the Data Services Platform (DSP).

Chapter 7 describes how to troubleshoot Sun StorEdge 6020 arrays.

Chapter 8 provides detailed information for troubleshooting the Storage Service Processor.

Chapter 9 describes how to replace the entire DSP and how to replace individual DSP FRUs.

Chapter 10 provides procedures for removing and replacing an entire array, and for removing and replacing array FRUs.

Chapter 11 describes how to remove and replace the Storage Service Processor and the USB flash disk.

Chapter 12 describes how to replace the Storage Service Processor accessory tray.

Chapter 13 describes how to replace the service panel and the USB relay panel.

Chapter 14 provides information about adding and removing a second cabinet, and about replacing the components within the cabinet.

Chapter 15 describes how to add and remove lights-out power management, how to add and remove an external modem, and how to use the dangling cable for array enclosure diagnostics.

xx Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


Appendix A describes making SAN and DAS host connections and describes how to allocate ports.

Appendix B describes how to unconfigure and restore the Service Processor configuration.

Appendix C describes how to run a solution extract via the CLI or via Storage Automated Diagnostics Environment, and shows the command-line output of the various components in a solution extract file.

Appendix D provides tables describing attributes and best applications for each RAID level, attributes and applications for typical factory storage profiles, attributes and applications for custom storage profiles for corner cases, and guidelines for creating storage profile

Shell Prompts

Shell Prompt

C shell machine-name%

C shell superuser machine-name#

Bourne shell and Korn shell $

Bourne shell and Korn shell superuser #

Preface xxi


Typographic Conventions

Typeface *

* The settings on your browser might differ from these settings.

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

Read Chapter 6 in the User’s Guide.These are called class options.You must be superuser to do this.

Command-line variable; replace with a real name or value

To delete a file, type rm filename.

xxii Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


Related DocumentationThe following table lists the documentation for the Sun StorEdge 6920 system and related products.

Product Title Part Number

Late-breaking news • Sun StorEdge 6920 System 1.0 Release Notes 817-5229

Sun StorEdge 6920 series information

• Sun StorEdge 6920 System Host Installation Software Guide• Sun StorEdge 6920 System Getting Started Guide• Sun StorEdge 6920 System Site Preparation Guide

817-5831817-5227817-5224

Sun StorEdge 6120 and 6020 array

• Sun StorEdge 6120 Array Start Here

• Sun StorEdge 6120 Array Release Notes• Sun StorEdge 6120 Array Site Preparation Guide• Sun StorEdge 6120 Array Installation Guide• Sun StorEdge 6020 and 6120 Arrays System Manual

817-0198

817-0201817-0960817-0199817-0200

Sun StorEdge Expansion Cabinet

• Sun StorEdge Expansion Cabinet Installation and Service Manual

805-3067

Diagnostics • Storage Automated Diagnostic Environment 2.2 User’s Guide—Device Edition (for Sun StorEdge 6120 Arrays

817-0822

Sun StorEdge network FC switch-8 and switch-16 switches

• Sun StorEdge SAN Foundation Software 4.4 Installation Guide• Sun StorEdge SAN Foundation Software 4.4 Configuration

Guide• Sun StorEdge SAN Foundation Software 4.4 Release Notes• Sun StorEdge SAN Foundation Software 4.4 Guide to

Documentation

817-3671817-3672

817-3673817-3670

3COM Ethernet hubs • SuperStack 3 Baseline Hub 12-Port TP User Guide• SuperStack 3 Baseline Hub 24-Port TP User Guide

3C16440A3C16441A

SANbox-8/16 Segmented Loop FC Switch

• SANbox-8/16 Segmented Loop Fibre Channel Switch Management User’s Manual

• SANbox-8 Segmented Loop Fibre Channel Switch Installer’s/User’s Manual

• SANbox-16 Segmented Loop Fibre Channel Switch Installer’s/User’s Manual

875-3060

875-1881

875-3059

Preface xxiii


Accessing Sun DocumentationYou can view, print, or purchase a broad selection of Sun documentation, including localized versions, at:

http://www.sun.com/documentation

For Sun StorEdge 6920 system documentation, go to:

http://www.sun.com/products-n-solutions/hardware/docs/Network_Storage_solutions/Midrange/6920/index.html

Sun Welcomes Your CommentsSun is interested in improving its documentation and welcomes your comments and suggestions. You can submit your comments by going to:

http://www.sun.com/hwdocs/feedback

Please include the title and part number of this document with your feedback:

Sun StorEdge 6920 System Technician’s Reference Guide, part number 817-6499-10.

xxiv Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


CHAPTER 1

Introduction

This chapter introduces the Sun StorEgde 6920 system. It contains the following sections:

■ “Features” on page 1

■ “Hardware Overview” on page 3

■ “Software Overview” on page 8

■ “Solaris Driver Stack” on page 12

■ “Predictive Failure Analysis (PFA) Capabilities” on page 12

FeaturesThe Sun StorEdge 6920 system provides the following features:

■ Support for 36-Gbyte, 73-Gbyte, or 146-Gbyte bidirectional, dual-ported Fibre Channel-Arbitrated Loop (FC-AL) disk drives

■ Support for the Sun StorEdge Remote Response service, which provides phone-home remote monitoring and support

■ An embedded Storage Service Processor that provides the following:

■ A platform for firmware and software system upgrades■ Continuous monitoring of components in the Sun StorEdge 6920 system, once

the Sun StorEdge Remote Response service is enabled■ Diagnostic tools to troubleshoot problems

■ Maximum of 8 Sun StorEdge 6020 arrays in the base Sun StorEdge Expansion Cabinet

■ Maximum of 20 Sun StorEdge 6020 arrays using the base cabinet and an additional expansion cabinet.

1


■ Maximum of 32 Sun StorEdge 6020 arrays using the base cabinet and two additional expansion cabinets.

■ Depending on the number of drives available, preconfiguration of each Sun StorEdge 6020 array as one RAID-5 virtual disk (7 to 13 drives) or two RAID-5 virtual disks (14 drives).

■ Remote power cycle and reboot so you can securely power on and power off the entire system

■ Logical unit number (LUN) security access for the storage consolidation models

■ Hot swapping of most field-replaceable units (FRUs)

■ Cluster and simultaneous independent host attachment support

2 Sun StorEdge 6920 System Technician’s Reference Guide • May 2004


Hardware OverviewThe Sun StorEdge 6920 system has a modular architecture with integrated system-wide manageability. The system base cabinet contains all of the hardware components for the system.

FIGURE 1-1 Sun StorEdge 6920 System Base Cabinet – Front and Back Views

From the front of the system’s base cabinet, you can view the LEDs for the Storage Service Processor, Data Services Platform (DSP), and storage arrays.

Data Services Platform (DSP)

Storage arrays

Storage Service Processor (SSP)

SP LANOUTSERVICE

PROCESSORPANEL

SP LANIN

USERLAN AUX

SERVICESERIAL

SERVICECONSOLE PHONE

PWR SEQUENCER

OUT FRONT

OUT REAR

EXPFC1

AFC2

EXP ENET 1

I/O EXP ENET 2

ANPORT 1

B

2 3 4 5 6 7 8

EXPFC1

BFC2

I/OC

NPORT 1

D

2 3 4 5 6 7 8

Service panel

Storage arrays

Power sequencer

Storage array LEDs

Management interfacecards (MICs)

I/O panels

Service Processor panel

Chapter 1 Introduction 3


From the back of the base cabinet, you can access the service panel for cabling the hosts, storage area network (SAN), and local area network (LAN) to the Sun StorEdge 6920 system. You can also access storage arrays and the Data Services Platform’s field replaceable units (FRUs) such as power and cooling units, array controllers, and storage resource cards.

The system can comprise a base cabinet alone, or it can include an expansion cabinet.

For more information about configuration options and instructions on how to expand the system by adding disks, trays, cabinets, storage arrays, Fibre Channel (FC) ports, and external FC switches, see the online help.

TABLE 1-1 describes the Sun StorEdge 6920 system hardware components.



For more information about hardware components, go to the online help system. Click the Search tab and type hardware.

TABLE 1-1 System Hardware Components

Component Description

Service panel The service panel simplifies the cabling to the system. It provides the following:

• Modem connection

• LAN connections for management

• Serial ports

• I/O connections for data hosts

• Power connections for expansion rack management

• Ethernet and FC connections for expansion racks

• AUX port to connect to the DSP management interface card (MIC) card, which provides management interface failover

You connect cables to these accessible panel connections rather than to individual components of the system.

Storage Service Processor The Storage Service Processor is a management host residing in the system’s base cabinet. The management software arrives pre-installed on the Storage Service Processor. The Storage Service Processor is cabled to the service panel, allowing for easy serial and local area network (LAN) connections. You do not connect directly to the Storage Service Processor.

Storage Service Processor accessory tray

The Storage Service Processor accessory tray provides a number of functions for the system, including:

• Network terminal concentrator (NTC)

• Router with a firewall

• Modem to connect to the Sun StorEdge Remote Response service

Data Services Platform (DSP) The DSP provides virtualization services for the storage devices in the system. It also provides FC switching so that the system does not require additional switches.

Storage arrays The storage arrays make up the physical storage of the Sun StorEdge 6920 system. The individual disk trays in an array can contain from seven to fourteen disk drives each.

Ethernet hub The Ethernet hub manages internal network traffic on the Sun StorEdge 6920 system.



Storage Array ConfigurationsThe storage array design is modular, with a variety of possible configurations (FIGURE 1-2). Each configuration option includes two controllers (also referred to as a controller pair) to provide redundancy and failover capabilities. Each storage array also has redundant Fibre Channel (FC) data paths and two power supplies with an integral battery backup system. In the event of a total power failure, each array has sufficient power from the batteries to shut down in an orderly fashion.

The system is available in three supported storage array configurations:

TABLE 1-2 Storage Array Configuration Options

Option Trays x ControllersNumber of Disk Drives

Minimum Capacity

Maximum Capacity

1 2 x 2 14 to 28 504 gigabytes 4 terabytes

2 2 x 4 28 to 56 1 terabyte 8 terabytes

3 2 x 6 42 to 84 1.5 terabytes 12 terabytes

FIGURE 1-2 Array Configuration Options

2x4 Configuration: Two Controllers and Four Storage Trays

2x2 Configuration: Two Controllers and Two Storage Trays

2x6 Configuration: Two Controllers and Six Storage Trays

Ethernet Ethernet2 GB FC

2 GB FC

2 GB FC

2 GB FC

2 GB FC

2 GB FCEthernet

EthernetEthernetEthernet



The configuration of the system is based on requirements for throughput, amount of storage, and economy. For example, if throughput is more important than economy, you might want to use the option 1 storage array configuration. In contrast, if the amount of available storage is more important than throughput, you might want to use the option 2 or 3 storage array configuration.

A controller tray contains disk drives and built-in RAID management hardware. An expansion tray contains disk drives only and is managed by a controller tray.

FC I/O connections on the service panel connect to the controller of each array in the base cabinet. This cabling is attached at the factory before the cabinet is shipped.

For more information about array configuration, see the online help.

Internal and External NetworksThe Sun StorEdge 6920 system incorporates three separate networks: The Storage Service Processor LAN, the internal component LAN, and the site (customer) LAN (TABLE 1-3).

TABLE 1-3 Internal and External LANs

Network Description

Storage Service Processor LAN The Storage Service Processor LAN is used by the Sun StorEdge Remote Response system to remotely monitor the Sun StorEdge 6920 system. When multiple Sun StorEdge 6920 systems (up to eight at the same site) are installed, the systems can share a single telephone line.

Internal Component LAN The Storage Service Processor communicates with components that make up the system over this LAN. This network is not accessible from outside the system and is isolated from the data path.

Site (customer) LAN This LAN connects to the customer’s internal Ethernet LAN. This network enables access to the system from the user’s management host. The management host is used to configure, control, and monitor the system through a web browser or a thin-scripting client. A firewall is included in the router of the Storage Service Processor accessory tray between the user LAN and the Storage Service Processor LAN.



Software OverviewThis section describes the following software used in the system:

■ “User Interfaces” on page 8

■ “Resident Software” on page 9

■ “Required Host Software” on page 9

User InterfacesYou can access the system software using the two main interfaces to the system:

■ A browser-based graphical user interface (GUI)

■ A command-line interface (CLI), available through a thin-scripting client for remote management

Note – See the Sun StorEdge 6920 System Release Notes for a list of supported browsers.

In addition to providing the same control and monitoring capability as the web browser, the thin-scripting client is also scriptable. If you want to configure storage from a remote management host, you can install the thin-scripting client on an external server and then use the sscs commands to access the system.

For more information about the thin-scripting client, see the Sun StorEdge 6920 System Host Installation Guide and the sscs(1M) man page.



Resident SoftwareTABLE 1-4 describes the software that is pre-installed on the Sun StorEdge 6920 system.

Required Host SoftwareIn addition to the software that is pre-installed on the system, there is additional software that must be installed on hosts for the system either to function properly or to gain additional functionality. This software is summarized in the following sections.

Solaris Host Software

The Host Installation CD that ships with the system includes a variety of Solaris host-based software for managing the Sun StorEdge 6920 system. You specify the functionality you require, and the CD installs the necessary software.

TABLE 1-4 Resident (Pre-installed) System Software

Software Description

System and storage management software

Provides configuration services through a centralized management tool.

System monitoring and diagnostic software

Provides a diagnostic monitoring tool for the system. It can be configured to monitor on a 24-hour basis, collecting information that enhances the reliability, availability, and serviceability (RAS) of the Sun StorEdge 6920 system.

Revision maintenance software

Provides a tool for upgrading firmware revisions of all components resident in the system. It also keeps track of these firmware levels and whether components are using the latest firmware revisions.

Sun StorEdge Remote Response software

Connects to the Sun Service Center, allowing trained personnel to remotely monitor, troubleshoot, diagnose, and service the system. If the Sun Service Center organization determines that there is a problem, Sun will recommend and perform maintenance on the system.

Sun StorEdge Storage Pool Manager software

Enables virtualization and pooling of storage assets across applications. Up to 2 terabytes of capacity is provided with the system. Additional right to use (RTU) licensing is required for use of larger capacities.

Sun StorEdge Data Snapshot software

Allows for the creation of point-in-time snapshot copies of a volume. The snapshot copies can be read/write-mounted by applications to secondary storage and used for backup, application testing, or data mining without the need to take the primary storage offline. The right to use (RTU) license is issued per system and is based on the capacity of primary storage that will be snapped.



The software on the Host Installation CD includes:

■ Sun StorEdge SAN Foundation software – Incorporates drivers and utilities that enable Solaris data hosts to connect to, monitor, and transfer data in a SAN.

To enable multipathing functionality, each Solaris data host must have Sun StorEdge Traffic Manager software installed before it can reliably communicate with the system’s storage. You may also choose to purchase VERITAS software, as described in “Additional Supported Software” on page 11, to enable Dynamic Multipathing (DMP).

■ Storage Automated Diagnostic Environment software, Device Edition – Resides on a data host or management console to monitor devices in the SAN.

■ Sun StorEdge Remote Configuration CLI – Enables Solaris hosts to remotely configure storage for the Sun StorEdge 6920 system.

Host Software for Other Operating Systems

Additional host software enables data hosts that run operating systems other than Solaris to communicate with the Sun StorEdge 6920 system. For details about the supported operating systems and versions, see the Sun StorEdge 6920 System Release Notes.

This software consists of the following:

■ Sun StorEdge Traffic Manager Software – Is required for hosts to make use of the Sun StorEdge 6920 system’s storage. The Traffic Manager software incorporates kernel drivers and utilities that enable data hosts to connect to, monitor, and transfer data in a SAN. The Traffic Manager software is available for Microsoft Windows 2000, Microsoft Windows 2003, Red Hat Linux, HP-UX, and IBM AIX operating environments.

■ Sun StorEdge Remote Configuration CLI – Enables hosts to remotely configure storage for the Sun StorEdge 6920 system. The remote CLI software is available for Microsoft Windows 2000, Microsoft Windows 2003, Red Hat Linux, HP-UX, and IBM AIX operating environments.

You can download host software for non-Solaris operating systems from Sun’s Download Center at:

http://wwws.sun.com/software/download/sys_admin.html

Go to the Download Center, select the Sun StorEdge 6920 system related software link, and follow the instructions to register and download the host software.



Additional Supported Software

The following host-based software is supported by the Sun StorEdge 6920 system:

■ Sun StorEdge Enterprise Storage Manager – SAN management software that helps you manage SAN environments, including the Sun StorEdge 6920 system, other Sun StorEdge storage systems, arrays, and heterogeneous hosts.

■ Sun StorEdge Availability Suite – Software that provides for remote mirroring and point-in-time copies of data.

■ Sun StorEdge Enterprise Backup Software – Software that provides backup, recovery, and other services for a variety of operating environments.

■ Solstice DiskSuite (for the Solaris 8 Operating System) – Software that manages data and disk drives.

■ Solaris Volume Manager (embedded in the Solaris 9 Operating System) – Software that lets you manage large numbers of disks and the data on those disks.

■ Sun StorEdge Performance Suite with Sun StorEdge QFS – Software that provides scalability, high performance, and reliable data integrity for applications managing large number of files, many large files or large file systems in a distributed network environment.

■ Sun StorEdge Utilization Suite with Sun StorEdge SAM-FS – Archive management software that automatically copies files from online disk to archive media.

■ Sun Cluster software – Software that extends the Solaris Operating System into a cluster operating environment, providing support for high availability, failover, and scalable services.

■ Sun StorEdge Diagnostic Expert – Software provides remote monitoring and diagnostics for Sun storage devices.

Supported Third-Party Software

The Sun StorEdge 6920 system is compatible with the following third-party applications:

■ VERITAS NetBackup Server

■ VERITAS NetBackup Enterprise Server

■ VERITAS Volume Manager with Dynamic Multipathing (DMP) for Solaris

■ VERITAS File System (VxFS) for Solaris

■ VERITAS Volume Replicator for Solaris

■ Legato NetWorker

■ You can purchase any of this software and install it on hosts connected to the Sun StorEdge 6920 system. For a list of supported releases and versions, see the Sun StorEdge 6920 System Release Notes.



Solaris Driver StackTABLE 1-5 shows the driver stack for host bus adapters (HBAs), Fibre Channel (FC) ports, the disk driver, the FC protocol, and the Sun FC transport library.

Predictive Failure Analysis (PFA) CapabilitiesHealth and monitoring functions for the Sun StorEdge 6920 systems are provided by Storage Automated Diagnostic Environment software. This software provides the following predictive failure analysis (PFA) capabilities:

■ FC links – FC links are monitored at all end points through the Fibre Channel Extended Link Service (FCELS) link counters. When link errors surpass the specified threshold values, an alert is sent. The alert message advises Sun personnel to replace components that are experiencing high transient fault levels before a hard fault occurs.

■ Enclosure status – Enclosed devices such as arrays cause alerts to be sent if temperature thresholds are exceeded. This enables Sun personnel to address the problems before a device or enclosure fails.

■ Single point of failure (SPOF) notification – Notification of path failures and failovers enables Sun to repair the primary path in a timely fashion. This notification reduces the time of exposure to single points of failure and helps to preserve data availability during the repair process.

TABLE 1-5 Solaris Driver Stack

Component Description

qlc ISP 2300 Family Fibre Channel (FC) HBA driver

fp Sun FC port driver

ssd Disk driver for FC-AL disks and Sparc Storage Array (SSA) disks

fcp FC protocol driver

fctl Sun FC transport library



CHAPTER 2

Troubleshooting Tools

This chapter provides an overview of the tools and resources available for troubleshooting problems that occur on the Sun StorEdge 6920 system. It contains the following sections:

■ “About the Storage Automated Diagnostic Environment” on page 13

■ “About Diagnostic Tests” on page 20

■ “Log Files on the Sun StorEdge 6920 System” on page 27

■ “About SAN Tools” on page 28

About the Storage Automated Diagnostic EnvironmentThe Storage Automated Diagnostic Environment is the main fault management tool of the Sun StorEdge 6920 system. It provides around-the-clock system monitoring and notification, as well as diagnostic tools for the various subcomponents of arrays.

You can also use the Storage Automated Diagnostic Environment for maintenance tasks such as reserving a cabinet for maintenance, checking the status of the various field-replaceable units (FRUs), and generating new inventories.

This section describes common tasks you perform using the Storage Automated Diagnostic Environment, including logging into the system, reserving the cabinet, and displaying the event log for a device.

13


▼ To Log In to the System1. Open a supported browser.

Tip – For information about supported web browsers, see the Sun StorEdge 6920 System Release Notes.

2. Enter the IP address of the system in this format: https://IPaddress:6789

This IPaddress is the IP address of the site LAN interface.

The system displays the Sun Web Console login page (FIGURE 2-1).

FIGURE 2-1 Sun Web Console Login Page

3. Enter the user name and password.

■ To log in as system administrator to configure system-wide setting, use enter the following for the login and password:

admin!admin

■ To log in as storage administrator to configure and manage storage on the system, use enter the following for the login and password:

storage!storage

■ To log in as a guest user without read/write permissions, use enter the following for the login and password:

guest!guest



Note – The admin and storage accounts are exclusive. If a second user logs on to an account already in use, the session of the first user terminates.

4. Click on Storage Automated Diagnostic Environment.

5. Click the Log In button.

The system displays the Sun Web Console page (FIGURE 2-2).

6. Select Storage Automated Diagnostic Environment

▼ To Display the Event Log for a Specific DeviceAt times, you may want to look at the events related to a specific device. For example, if LEDs on the Data Services Platform light in such a way that indicate some type of hardware failure, you should first look at the events for Data Service Platform before replacing any FRUs.

1. From any Storage Automated Diagnostic Environment page, click Monitor > Device

FIGURE 2-2 Sun Web Console Page

Chapter 2 Troubleshooting Tools 15


2. Click the name of the device listed in the device column for which you want to display the event log.

3. Select Event Log from the Page list.

The Event Log Report is displayed. It contains the following information:

■ Date and time the event occurred■ Host name■ Severity icon■ Additional information about the event

4. To access the Event Advisor for an event, click the event in the Event column.

The Event Advisor page displays detailed information about the event and, if the event requires action, provides a probable cause and recommended action.

Note – The Event Log report is for informational purposes only. No user input is accepted.

Using Solution ExtractSolution Extract is a Storage Automated Diagnostic Environment utility that is similar in functionality to the Explorer (SUNWexplo) or T3Extractor utility used for Sun StorEdge 6020 arrays. Its purpose is to gather the data used to verify configuration and error conditions.

The Solution Extract command creates a tar file that contains a snapshot of the Sun StorEdge 6920 configuration. The file includes events, logfiles, configuration logs, and commands.

▼ To Run a Solution Extract From the GUI

1. From any Storage Automated Diagnostic Environment page, click Monitor > Utilities.

The Solution Extract page is displayed (FIGURE 2-3).



FIGURE 2-3 Solution Extract Page

2. If the Sun StorEdge 6020 arrays in the cabinet have a password, enter it.

3. Click Start Extract.

The system starts collecting the data.

Depending on the system configuration, it can take up to an hour to complete the file extract.

4. Click the appropriate link to download the extract output you want to view.

The resulting tar file is downloaded to the system where you are running the web browser.

5. Untar the file.



.

A directory containing the various files is created. The output, shown in TABLE 2-1, provides information about the components that make up a Sun StorEdge 6920 system. Each component directory contains information that can help you detect and isolate problems.

# cd /path-to-download-directory

# lsextract_6920.8335ba6c_2004-03-31_130055.tar

# tar xvf extract_tar cf extract_6920.8335ba6c_2004-03-31_130055.tar

# ls -lFtotal 544drwxr-xr-x 9 root root 626 Apr 8 13:35 6920.8335ba6c/-rw------- 1 rarneson swat 266240 Apr 8 13:42 extract_6920.8335ba6c_2004-03-31_130055.tar

# cd 6920.8335ba6c

# lsArrays/ PatchPro/ Sp/ Switches/ DSP/ Rack/ Storade/ Ves/extract_log.txt

TABLE 2-1 Components of Sun StorEdge 6920 Systems

Directory Description

Arrays Contains information about the storage arrays in the system.

PatchPro Contains information pertaining to the operation of PatchPro.

Rack, Sp Contain information about the configuration of the Storage Service Processor

Switches Not applicable for Sun StorEdge 6920 system.

DSP Contains information about the Data Services Platform.

Storade Contains information about alerts and monitoring

Ves Not applicable for Sun StorEdge 6920 system.



Running Solution Extract from the CLI

You can also run Solution Extract from the command-line interface (CLI) on the Storage Service Processor, as shown in the following example.

The resulting tar file is located in the following directory:

/var/opt/SUNWstade/DATA/Download/Solution

Note – For sample command-line output from the modules that are available on the Storage Service Processor, see Appendix C.

[sp5]# /opt/SUNWstade/sysbin/se_extract

Usage: se_extract -r -t <array_password> -d [1|2] -s [status] -p [print] -b [background] -d : debug level -t : array password, all the same -s : status of extract run -p : print extract log -x : return the tar file immediately to stdout with http header. -r : run -b : background

[sp5]# /opt/SUNWstade/sysbin/se_extract -d 2 -r -bOK sysbin/se_extract started.



About Diagnostic TestsThis section describes the available diagnostic tests for the Sun StorEdge 6920 system and its related SAN components. Some of these tests area available from the Storage Service Processor; others are run from data hosts in the system.

Tests Available From the Storage Service ProcessorThe following tests are available from the Storage Automated Diagnostic Environment software on the Storage Service Processor.

■ Sun StorEdge 6920 Array Echo Test (6020loop) – The 6020loop(1M) test tests the functions of the Sun StorEdge 6020 array controller. Each controller has three SIMs (chips) that run the Fibre Channel (FC) loops inside and outside the array.

■ Sun StorEdge 6920 Array Volverify Test (6020volverify) – The 6020volverify(1M) test enables array administrators to execute manual parity checks on existing volumes.

Note – Check data parity using the 6020volverify(1M) test before performing tape backup overwrite cycles, approximately once every 30 days.

Tests Available From Data HostsTests available from outside the Storage Service Processor are initiated from a Solaris host running Storage Automated Diagnostic Environment software that has been configured to monitor the data path. Components in this data path include the following:

■ Host bus adapters (HBAs)

■ FC switches

■ LUNs presented to the Solaris Operating System from the Sun StorEdge 6920 system

■ Any Sun StorEdge 6920 system expansion cabinet



The tests are:

■ Sun StorEdge Peripheral Component Interconnect (PCI) Dual FC Host Adapter Board Test (qlctest) – The qlctest(1M) tests the functions of the Sun StorEdge 1-Gbyte and 2-Gbyte PCI and cPCI FC network adapter boards. This diagnostic test is not scalable and is only for Qlogic adapters branded by Sun.

■ Sun StorEdge 2Gbyte cPCI Dual Fibre Channel Network JNI FC Host Adapter Board Test (jnitest) – The jnitest(1M) tests the functions of the Sun StorEdge 2-Gbyte PCI cPCI Dual FC network adapter Java Native Interface (JNI) boards. This test applies only to JNI adapters branded by Sun.

■ FC Link Test (linktest) – The linktest(1M) test verifies the functionality of passive FC components in a storage area network (SAN) or direct attached storage (DAS) environment. linktest isolates failing FRUs for devices that have external loopback tests.

Note – linktest is available only from the Storage Automated Diagnostic Environment Test from Topology view. It is not available from the CLI or from the Storage Automated Diagnostic Environment Test from List view.

■ Sun StorEdge 6920 System Test (se2test) – The se2test(1M) test aids the validation and fault isolation for the Sun StorEdge 6920 system components.

■ Sun StorEdge 6920 System Configuration Test (se_configcheck) – The se_configcheck(1M) test checks the status of the Sun StorEdge 6920 system configuration. There are no options for the se_configcheck test.

▼ To Access the Diagnostic Tests

● From any Storage Automated Diagnostic Environment page, click Diagnose.

The Test From List page is displayed.

FIGURE 2-4 Test From List Page



Running Diagnostic TestsWith two exceptions, you can run Storage Automated Diagnostic Environment diagnostic tests using either Test from List or Test from Topology. The exceptions are these:

■ If you want to use the Link Test, you must run the test using Test From Topology. You cannot invoke the Link Test functionality using Test from List.

■ If you want to test HBAs that are not connected to any device, you must use the Test from List option.

Note – The monitoring status of devices and links appears both in the Test from Topology view and in the Test from List menu.

The Test from List view shows the devices and their associated tests. This list also includes warnings and errors reported by the monitoring agents. In addition, Test from List displays all available host and HBA tests, not just the connected ports, as the Test from Topology view displays.

Using Test from List, you can do the following:

■ Sort by host, device type, test type, and device status ■ Select options for a specific device, select multiple devices, or select all devices■ Specify the number of passes each test will run

▼ To Test From Topology

The Storage Automated Diagnostic Environment’s implementation of diagnostic tests verifies the operation of all the user-selected components. Using the Topology view, you can select specific subtests and test options.

1. On the Diagnostic Tests page, click Test From Topology.

The Test From Topology page is displayed (FIGURE 2-5).



FIGURE 2-5 Test From Topology Page

2. Double-click the device you want to test.

A new window displays the test options for this device.

3. Select the test you want to run on the device.

4. Change the values in fields with pull down menus, and enter an email address in the Send Results to Email field.

5. Click Go.

After the test has completed its run, an email message containing the results is sent to the email recipient.

Note – For instructions on setting up the email recipients, see the online help.



▼ To View a Test’s Man Page From the GUI

● Click the Man Page link in the device’s test window (FIGURE 2-6).

FIGURE 2-6 Accessing a Test’s Man Page

Click here to access the test’s man page



The test’s man page is displayed (FIGURE 2-7).

FIGURE 2-7 Sample Test Man Page

▼ To Test from List

The Storage Automated Diagnostic Environment’s implementation of diagnostic tests verifies the operation of all the user-selected components. Tests are selected from a list of physical devices.

1. On the Diagnostic Tests page, click Test From List.

The Test From List page is displayed (FIGURE 2-8).



FIGURE 2-8 Test From List Page

2. Select the diagnostic test that you want to run.

3. From the Host list, select the host on which you want to run the test.

4. From the Filter list, select the devices on which you want to run the test.

5. Click GO.

A list that matches your specified criteria is displayed.

6. In the Run Test column, click the name of the test you want to run.

A list of parameters related to the test is displayed.

7. Specify the necessary information, then click Start Test.

After the test has completed its run, an email message containing the results is sent to the email recipient.

Note – For instructions on setting up the email recipients, see the online help.



Log Files on the Sun StorEdge 6920 SystemTABLE 2-2 lists the location of various log files available on the Sun StorEdge 6920 system. These log files are on the Storage Service Processor

TABLE 2-2 Log Files on the Sun StorEdge 6920 System

Log File Path Description

/var/opt/SUNWstade/DATA/rasagent.conf File containing information such as site location, hosts, devices, and local notifications that were entered into the Storage Automated Diagnostic Environment GUI. The file remains on the system between upgrades so that previously entered configuration information is not lost.

/var/opt/SUNWstade/log Storage Automated Diagnostic Environment message logs.

/var/adm/messages General Solaris host messages.

/var/adm/messages.array Mirrored system logs from storage arrays.

/var/tmp/se6000configure.log Console output of the setup procedure.

/var/tmp/se6000watchdog.log Console output of the configuration software watchdog software.

/var/tmp/wbemconfig.log Output of the configuration software operations.



About SAN ToolsThe Product Technical Support (PTS) -Americas Network Storage Team has useful tools on its web site that can assist in SAN troubleshooting. Be advised, however, that these tools are not supported and have not been tested in production environments.

Access the tools at http://pts-americas.west/nws/products/Switch/tools.html

TABLE 2-3 Miscellaneous SAN Tools and Scripts

SAN Tool Description

dumpmaps

luxadm Dump Mapperksh script to extract luxadm -e dump_map from all connected HBAs. Also prints out the controller number, qlc instance, and HBA device path for the path dumping the map.

hbamap

Sun StorEdge SAN Foundation software-HBA Mapper

ksh script to map out the following HBA data for Sun StorEdge SAN Foundation software cards:• Controller number• qlc instance• Port Worldwide name (WWN)• ISP chip set

• FCode• Connection status (from luxadm -e port)• Device path• Fabric address• cfgadm output

lunmap

Sun StorEdge Traffic Manager and VxVM LUN Mapper

ksh script to map MPxIO devices to VxVM enclosure names:• VxVM enclosure name• MPxIO device name• Device WWN• LUN number• Number of primary and secondary paths• Path state (ONLINE/OFFLINE/STANDBY)• Controller, qlc instance, and device pathlunmap can also check for path problems.



sfkcheck

SAN Foundation Kit (SFK) and SAN Revision Checker

ksh script to check revision levels of Sun StorEdge SAN Foundation software packages and patches.

Note: sfkcheck uses an internal /net path to find the latest patch revisions. To run this on an external customer system, use the -l option, which checks for patches but does not provide the latest revision levels.

TABLE 2-3 Miscellaneous SAN Tools and Scripts (Continued)

SAN Tool Description





CHAPTER 3

Basic Troubleshooting Procedures

This chapter offers general troubleshooting guidelines. Sections for information gathering, troubleshooting questions, and problem isolation are presented for both Storage Service Processor and hosts. It contains the following sections:

■ “Required Patches and Packages” on page 32

■ “Data Host Patches” on page 32

■ “Maintenance Precautions” on page 34

■ “Reserving the Cabinet for Maintenance” on page 34

■ “Isolating the Problem” on page 35

■ “Troubleshooting the Storage Service Processor” on page 37

■ “Troubleshooting SAN Connections” on page 39

■ “Debugging Individual Components via Serial Connections” on page 41

■ “Bootup Events” on page 41

31


Required Patches and PackagesBefore you begin any troubleshooting procedures, make sure that the following packages and patches are installed on the Sun StorEdge 6920 system management host or any data host connected to the system:

■ Sun StorEdge 6920 Host Installation software (also available on the product CD)

■ VERITAS Array Support Library, required only for VERITAS Volume Manager support with the array

■ SAN Foundation Kit version is 4.4 or higher

Note – Patches must be installed in the same location as the package.

▼ To Check the SAN Foundation Kit Version

Make sure the SAN Foundation Kit version is 4.4 or higher.

● Type the following command:

Data Host PatchesTABLE 3-1 lists the minimum level patches necessary for the array. These patches must be installed on the data host.

# modinfo | egrep ’(SunFC|mpxio|scsi_vhci)’

64 12fd9bb 1196b 149 1 fp (SunFC Port v6.2.6-2-1.28)65 130edb6 7018 - 1 fctl (SunFC Transport v6.2.6-2-1.20)67 1345b2a 4a062 153 1 qlc (SunFC Qlogic FCA v6.2.6-2-1.29)108 13d5add 10c3d 150 1 fcp (SunFC FCP v6.2.6-2-1.44)109 13e615e 515c - 1 mpxio (MDI Library v6.2.6-1-1.10)110 13eafb0 85b8 189 1 scsi_vhci (SCSI vHCI Driver v6.2.6-1-1.19)175 78207eb6 74d7 154 1 fcip (SunFC FCIP v6.2.6-2-1.16)



Caution – Always check the most recent release notes for the latest minimum patch set requirements, as the patch revisions are subject to change.

▼ To Download the Patches1. Go to the SunSolveSM web site: http://www.sunsolve.sun.com

TABLE 3-1 Data Host Patches

Platform Patch Number Patch Description

Solaris 9 operating system, first release or later

Refer to:http://www.sun.com/storage/san

Sun StorEdge SAN Foundation 4.4 software: For patch and product information, refer to the Sun StorEdge SAN Foundation 4.4 Installation Guide at:http://www.sun.com/storage/san

112392-05 or later VERITAS VxVM 3.5 general patch1

VERITAS VxVM patches must be installed in the order listed.

Solaris 8 operating system, Update 4 or later

Refer to:http://www.sun.com/storage/san

Sun StorEdge SAN Foundation 4.4 software:For patch and product information, refer to the Sun StorEdge SAN Foundation 4.4 Installation Guide at:http://www.sun.com/storage/san.

112392-06 or later VERITAS VxVM 3.5 general patch1

VERITAS VxVM 3.5 supplemental general patch1

VERITAS VxVM patches must be installed in the order listed.

Microsoft Windows 2000 Server and Advanced Server

Available from Microsoft Microsoft Windows 2000 Service Pack, SP 3Sun StorEdge Traffic Manager 3.0 Win2K

IBM AIX 4.3.3 Available from IBM ML 10Sun StorEdge Traffic Manager 3.0 AIX

IBM AIX 5.1 32- and 64-bit Available from IBM ML 03Sun StorEdge Traffic Manager 3.0 AIX

HP-UX 11.00 and 11.i Available from Hewlett Packard

Patch set from September, 2002

Red Hat Linux 7.2 (single path support only)

Available from Red Hat Version 2.4.7-10

1Required only for systems running VERITAS Volume Manager with the array.

Chapter 3 Basic Troubleshooting Procedures 33


2. Download the patches listed in TABLE 3-1.

You can access these patches by navigating the links Patch Pro>Network Storage Products.

▼ To Install the Patches1. Use the patchadd(1M) command to install the patches listed in TABLE 3-1.

2. Refer to the patch README files for more patch information.

Maintenance PrecautionsBefore you perform any maintenance procedures on the Sun StorEdge 6920 system, take note of and follow these steps to prevent damaging any field-replaceable unit (FRU) during the removal and replacement process:

■ Remove all plastic, vinyl, and foam material from the work area.

■ Before handling any FRU, discharge any static electricity by touching a grounded surface.

■ Wear an antistatic wrist strip at all times when handling any FRU.

■ Do not remove a FRU from its antistatic protective bag until you are ready to install it.

■ After removing a FRU from the cabinet, immediately place it in an antistatic bag or antistatic packaging.

■ Handle any card FRU only by its edges, and avoid touching the components or circuitry.

■ Do not slide a FRU over any surface.

■ Limit body movement (which builds up static electricity) during the removal and replacement of a FRU.

Reserving the Cabinet for MaintenanceEach time you perform maintenance on the Sun StorEdge 6920 system, you should reserve the cabinet. You must be logged in to the Storage Automated Diagnostic Environment as admin to access this feature.



1. From any Storage Automated Diagnostic Environment page, click Service > Service Advisor.

2. Enter a description of the service action you want to perform (for example, replacing the SRC).

3. From the Reserve Cabinet For: list, select the amount of time you estimate this service action will take.

4. Click Reserve Cabinet(s).

When they log in, other users are alerted that this service action is in progress.

5. Close the pop-up window.

6. When you have finished the maintenance task, click Reserve/Release and then Release cabinet(s).

Isolating the Problem1. Determine the source of the error by checking one or more of the following

messages or files:

■ Storage Automated Diagnostic Environment alerts or email messages

■ /var/adm/messages

■ The Sun StorEdge 6020 array syslog file

2. Determine the extent of the problem by using one or more of the following methods:

■ Review the Storage Automated Diagnostic Environment topology.

■ Check the cfgadm -al output on the data host.

■ Check the luxadm(1M) output on the data host.

■ Review the multipathing status using the Sun StorEdge Traffic Manager (MPxIO) software or vxdmp(1M) command.

3. Check the status of a Sun StorEdge 6020 array by using one or more of the following methods:

■ Review the Storage Automated Diagnostic Environment device monitoring reports to determine the current health of the array.

■ Review the luxadm(1M) display output on the data host LUNs.

■ Review the LED status on the Sun StorEdge 6020 array.

■ Review the Storage Automated Diagnostic Environment’s Solution Extract output.



4. Check the status of the host by using the following tools:

■ Review /var/adm/messages.

■ Review the error logs of specific applications.

■ Review format output.

■ Review the Explorer data collection utility (SUNWexplo) output, which is located on the Storage Service Processor.

5. Quiesce the I/O along the path to be tested by using one of the following methods:

■ For systems using VERITAS Dynamic Multipathing (DMP), disable vxdmpadm(1M).

■ For systems using the Sun StorEdge Traffic Manager (MPxIO) software, unconfigure the Fabric device.



■ Follow the procedure described in “Manually Halting the I/O” on page 96.

■ Halt the application.

6. Test and isolate FRUs by using the following tools:

■ Storage Automated Diagnostic Environment diagnostic tests (this might require a loopback cable for isolation)

■ Sun StorEdge 6020 array tests; these include:

■ 6120test(1M)

■ 6120ofdg(1M)

■ 6020volverify(1M)

Note – These tests isolate the problem to a FRU that must be replaced. Follow the instructions later in this document for proper FRU replacement procedures.

7. Verify the fix by reviewing the following:

■ Any new messages generated by the Storage Automated Diagnostic Environment

■ The Storage Automated Diagnostic Environment topology

■ The following data host output:

■ luxadm(1M)

■ cfgadm -al

■ /var/adm/messages

8. Return the path to service with one of the following methods:

■ Use the multipathing software

■ Restart the application

Troubleshooting the Storage Service Processor The Storage Automated Diagnostic Environment detects messages, alerts, and errors while running on the Storage Service Processor.

This section lists the high-level steps you can take to isolate and troubleshoot problems in the Sun StorEdge 6920 system using the Storage Automated Diagnostic Environment. It offers a methodical approach, and lists the tools and resources available at each step.



Note – A single problem can cause various errors throughout the storage area network (SAN). Always isolate a fault to the lowest level affected.

Troubleshooting Best PracticesTroubleshooting best practices include the following:

■ Before you begin troubleshooting, collect the following information:

■ A clear and concise problem description

■ Specific symptoms and behavior that the customer is experiencing

■ Use the Fault Signature Analysis feature of the Storage Automated Diagnostic Environment to focus your troubleshooting efforts.

■ Locate available logs and diagnostic LEDs for the Sun StorEdge 6920 system.

■ Isolate the failure, symptom, or unexpected behavior to the component FRU.

■ Employ log error messages to aid in FRU isolation.

■ Identify failed hardware components using LEDs and messages.

■ Identify faulty cabling using LEDs and messages.

If you need to further isolate the problem, refer to the following sections.

Asking Troubleshooting QuestionsTABLE 3-2 provides questions and links to related information to help you find the source of the problem.

TABLE 3-2 Storage Service Processor Troubleshooting Questions

Problem Action

Is the Storage Service Processor available? See “About the Storage Service Processor” on page 125

Is the Storage Automated Diagnostic Environment generating events?

See “About the Storage Automated Diagnostic Environment” on page 13

Is a Storage Automated Diagnostic Environment topology snapshot displaying the problem?

See “About the Storage Automated Diagnostic Environment” on page 13



Troubleshooting SAN ConnectionsThis section describes how to troubleshoot storage area network (SAN) connections to a Sun StorEdge 6920 array from a data host, without using the Storage Automated Diagnostic Environment. The messages and errors that the data host detects are usually logged in the /var/adm/messages file.

External Troubleshooting SoftwareExternal software installed on a Solaris host is required to monitor and manage the FC switches. The external software includes the following:

■ SUNWsmgr package for Sun switch configuration

■ SUNWstade package for monitoring and diagnostics. SUNWstade is the standalone device edition of the Storage Automated Diagnostic Environment.

Note – See the information that was packaged with the operating system for operating systems other than Solaris.

What is the state of the array? Is the array in-band or out-of-band?

See “Troubleshooting Sun StorEdge 6020 Arrays” on page 93

How is the device accessed? See “About Multipathing” on page 96

Is the virtual disk shared between multiple hosts? • If yes, are all hosts affected the same way? • If yes, check for the common components (for

example, switch ports, array status, and virtual disk status).

• If no, isolate to the specific host.

See “Troubleshooting Host Devices” on page 55

TABLE 3-2 Storage Service Processor Troubleshooting Questions (Continued)

Problem Action



Gathering InformationCollect the following information before you take further steps to isolate the problem.

■ Patch and package information

■ cfgadm output

■ format output

■ luxadm output

■ Pertinent /var/adm/message errors

■ Switch information from /etc/opt/SUNWexplo/saninput.txt

See TABLE 3-3 for specific troubleshooting questions. If you need more detail to isolate the problem, refer to the following sections.

Asking Troubleshooting QuestionsTABLE 3-3 provides questions and links to related information to help you find the source of the problem.

TABLE 3-3 Host-Side Troubleshooting Questions

Problem Action

Is the system fully patched? Check the revision level using the Storage Automated Diagnostic Environment (Manage functionality).

Are there error messages? Check the /var/adm/messages file.

If the devices are Fabric-connect, are they configured in cfgadm?

Use the cfgadm -al command.

Are the LUNs in their primary multipath states? Gather Sun StorEdge Traffic Manager or vsdmp information.Check - luxadm display /dev/rdsk/lun (for Traffic Manager.)

Are the HBAs online? Use the luxadm -e port command.

Are the devices seen from the HBA? Use the luxadm -e dump_map device command.

Are the devices seen in format? Use the - format command.

Are there any CRC or Invalid Tx word errors on the HBA path?

Use the - luxadm -e rdls device command.



Debugging Individual Components via Serial ConnectionsYou can use serial connections on the Service Panel as field hook-up to proprietary device debug ports (for example, a Sun StorEdge 6020 array serial port). To do so, qualified service personnel should remove a serial connection from either port 3 or port 4 of the network terminal concentrator (NTC) in order to connect to the target device.

When you are finished, make sure to replace the serial connection to port 3 or 4 of the NTC.

Bootup EventsBefore you begin troubleshooting or maintaining the Sun StorEdge 6920, please read this section. It provides information about the following:

■ SVD_PATH_FAILOVER Messages■ boot -r Side Effects

SVD_PATH_FAILOVER MessagesDuring bootup, when the loop is split, drives 1, 2, 4, 5, 7, 8, 10, 11, 13, and 14 put SVD_PATH_FAILOVER warning messages in the syslog file. Although one might expect these messages to indicate a failover and a faulty FRU, they do not. You can check FRUs by issuing the commands fru stat and port listmap.

boot -r Side EffectsThe boot -r command is used to clear out the volume configuration on the Sun StorEdge 6020 array. If you run the boot -r command, it changes the mp_support parameter in the SYSTEM area of the T4 array such that the mp_support parameter value is changed from mpxio to none.

You must manually change the mp_support parameter value back to mpxio; as follows:



1. First, run sys list to check the system parameter, for example:

2. Manually change the mp_support parameter to mpxio by entering the following command:

3. Check the result by again running sys list.

array11:/:<1>sys listcontroller : 2.5blocksize : 32kcache : automirror : automp_support : none <------this is the changed parameternaca : offrd_ahead : onrecon_rate : medsys memsize : 256 MBytescache memsize : 1024 MBytesfc_topology : autofc_speed : 2Gbdisk_scrubber : onondg : befit

array11:/:<1> sys mp_support mpxio

array11:/:<1>sys listcontroller : 2.5blocksize : 32kcache : automirror : automp_support : mpxio <------The parameter shows the correct valuenaca : offrd_ahead : onrecon_rate : medsys memsize : 256 MBytescache memsize : 1024 MBytesfc_topology : autofc_speed : 2Gbdisk_scrubber : onondg : befit



CHAPTER 4

Troubleshooting Network Components

This chapter discusses network components including the 3COM Ethernet hub, the NetGear Router, and the Network Terminal Concentrator (NTC). All components described in this section are part of the Storage Service Processor accessory tray. Note that information associated with the 3COM Ethernet hubs is limited in this guide because 3COM does not allow duplication of its information.

This chapter contains the following sections:

■ “Troubleshooting the 3COM Ethernet Hub” on page 43

■ “Troubleshooting the NetGear Router” on page 44

■ “Connecting to the Network Terminal Concentrator (NTC)” on page 49

Troubleshooting the 3COM Ethernet HubThe internal Ethernet hub provides access to the 192.168.0.x LAN for the dmfe1 interface of the Storage Service Processor, the Sun StorEdge 6020 arrays, and the Data Services Processor. No configuration should be necessary.

Ask these questions if you have an internal Ethernet problem:

■ Are all of the LEDs green?

■ Are all connected ports LEDs green?

■ How many components are affected by the problem?

■ Can you use the ping command to ping other components on the internal network, for example, the DSP or arrays?

43


■ Does ifconfig -a show dmfe1 plumbed?

For example:

■ Does netstat -r show appropriate routes?

For example:

■ Does moving a cable to an empty port fix the problem?

■ Does performing a power-on and power-off procedure fix the problem?

If addressing these questions does not correct the Ethernet problem, replace the entire Storage Service Processor accessory tray as described in “Servicing the Storage Service Processor Accessory Tray” on page 203.

Troubleshooting the NetGear RouterThe NetGear router controls the external access to the Sun StorEdge 6920 system. It is used to control the firewall rules that allow access by way of certain ports to the Storage Service Processor.

The router is automatically configured during the setup phase of the system installation process, and the results are logged to /var/tmp/se6000configure.log on the Storage Service Processor.

Note – The power and test LEDs on the Storage Service Processor accessory tray are the LEDs for the router.

dmfe1: flags=1000843<UP, BROADCAST, RUNNING, MULTICAST, IPv4> mtu 1500index3 inet 192.168.0.2 netmask ffffff00 broadcast 192.168.0.255

Routing Table: IPv4 Destination Gateway Flags Ref Use Interface-------------------- -------------------- ----- ----- ------ -----192.168.0.0 loghost U 1 145 dmfe1rfc1918-10-0-0-0.10. in-addr.arpa sp0 U 1 58 dmfe0224.0.0.0 sp0 U 1 0 dmfe0default sp0-firewall UG 1 38localhost localhost UH 5 22150 lo0



LED StatusTABLE 4-1 describes the LEDs on the NetGear router.

TABLE 4-1 Router LEDs

Label Activity Description

PWR

(Power)

On

Off

Power is supplied to the router.

Power is not supplied to the router.

TEST OnOff

Blinking

The system is not ready or has failed to start up.The system is ready and running.

The system is initializing.

USER LAN (WAN)LNKACT

OnBlinking

The port has detected a link with an attached device.Data is being transmitted or received.

SP PORTS (LAN)LNK/ACT

100

OnBlinkingOn

Off

The port has detected a link with an attached device.Data is being transmitted or received.The port is operating at 100 Mbps.

The port is operating at 10 Mbps.

Chapter 4 Troubleshooting Network Components 45


The configuration settings are listed in /opt/SUNWsespfw/repository. The following listing shows a typical configuration.

The listed services are the only services that are allowed through the firewall.

Note – The ftp, telnet, ssh, and rlogin commands are not enabled through the firewall.

▼ To Access the Router1. To obtain the current status of the router, open a Telnet session to the router from

the Storage Service Processor.

The IP address of the router is spx-firewall, where x is the system identifier of the Sun StorEdge 6920 system. In this example, the system ID is sp5.

LanSubnetMask:255.255.255.0WanIPAddr:172.20.67.25patchpro_port:8080dns:enabledUniqueID:0030ab1b2236esm:enabledpatchpro:enabledntp:enabledLanDNSSrv:0.0.0.0snmp:enabledWanGateway:172.20.67.248cim_http:enabledsvc_http:enabledsm_https:enabledsvc_https:enabledWanSubnetMask:255.255.255.0ssh:disabledesm_port:8443sm_http:disabledLanDHCPSrv:disabledFirewallLogin:adminVersion:1.17WanAddrType:staticFirewallPwd:sun1LanIPAddr:10.0.0.52



Note – The password for the router is sun1.

2. Type 24. System Maintenance.

The System Maintenance menu is displayed.

[sp5]# telnet sp5-firewall

Trying 10.0.0.52...Connected to sp5-firewall.Escape character is ’^]’.

Password: ****

vRP114 Main MenuGetting Started Advanced Management

1. General Setup 21. Filter Set Configuration2. WAN Setup3. LAN Setup 23. System Password4. Internet Access Setup 24. System Maintenance

Advanced Applications11. Remote Node Setup12. Static Routing Setup15. SUA Server Setup

99. Exit

Enter Menu Selection Number:

Menu 24 - System Maintenance

1. System Status2. System Information and Console Port Speed3. Log and Trace4. Diagnostic5. Backup Configuration6. Restore Configuration7. Upload Firmware8. Command Interpreter Mode9. Call Control10. Time and Date Setting11. Remote Management Setup

Enter Menu Selection Number:



3. Choose Option 1. System Status, which gives the best overview of the current status of the router.

The remaining options primarily address various configuration settings and tests that do not pertain to a router installed in a Sun StorEdge 6920 system.

Caution – Do not manually change any settings on the router.

4. Check the number of collisions (Cols).

5. Check the IP addresses of the WAN and LAN ports.

The WAN port should be an IP address on the customer’s network. The LAN port should be one of the fixed IPs in the 10.0.0.X network.

The actual address depends on the system ID. You can find the defaults in the /etc/hosts file on the Storage Service Processor.

Menu 24.1 - System Maintenance - Status 11:52:00 Thu. May. 03, 2004

Port Status TxPkts RxPkts Cols Tx B/s Rx B/s Up Time WAN 10M/Half 43406 519745 0 0 362 45:39:26 LAN 100M/Full 34768 107796 0 291 128 45:39:26

Port Ethernet Address IP Address IP Mask DHCP WAN 00:30:ab:1b:22:36 172.20.67.25 255.255.255.0 None LAN 00:30:ab:1b:22:35 10.0.0.52 255.255.255.0 None

System up Time: 45:39:32

Name: SE6320 Routing: IP RAS F/W Version: V3.26(CD.0) | 8/17/2001

Press Command:

COMMANDS: 1-Drop WAN 9-Reset Counters ESC-Exit



Connecting to the Network Terminal Concentrator (NTC)The serial network terminal concentrator (NTC) is used for remote serviceability support.

▼ To Connect to the Storage Service Processor From the NTC

1. Log in to the NTC:

2. Connect to the Storage Service Processor by connecting to a local port:

Login: rsspassword: sun1rss

ntc0: connect local port_2Local protocol emulation 1.0 - Local Switch: <^[>.

Sun StorEdge 6920 Storage Service Processor

WARNING: This is a restricted access server. If you do not have explicit permission to access this server, please disconnect immediately. Unauthorized access to this system is an actionable offense and will be prosecuted to the fullest extent of the law.

sp3 console login:



To break out of a serial connection and return to the ntc0: prompt, use the CTRL- [ or CTRL-] key sequence.

To return to the session, type resume. To close the session, type to return to the session, disconnect session # or disconnect all.

Common ProblemsThese problems pertain to connecting to the NTC:

■ Problem 1 – If you cannot access Port 2 using the command connect_local port_2

Solution – At the ntc0 console, issue the following command:

Also, you can issue the show session command to see if there is already a connection to local port_2. If there is, you can kill the session or log out of the port.

[sp3]# <=== CTRL- [ key sequence

ntc0:ntc0: resume

%Info: Session 1 with PORT_2 resumed.

[sp3]#

ntc0: suPassword: sun1rssntc0: logout port 2ntc0:



■ Problem 2 – If you cannot connect to Port 1

Solution 1 – If you have access to the SP, log into the NTC via Telnet and issue the following command:

Solution 2 – Repower the Storage Service Processor accessory tray.

There may be a connectivity issue from the server to the Sun Storage 6920 rack. Verify these things:

■ Cable configuration from the server to the Sun StorEdge 6920 rack is correct.

■ The connection is at 9600, 8, none, 1 with no flow control.

Useful CommandsThe following commands might be helpful when you are displaying information from the NTC:

■ show server

■ show ip all

■ show ports

ntc0: suPassword: sun1rssntc0: logout port 1ntc0:



show server CommandThe show server command displays the current server from which commands will operate.

ntc0: show serverSCS400 Version B2.0/202(021016) Name: sp3-ntcHardware Addr: 00-80-a3-56-36-8e Uptime: 0:41:04 Daytime: Thu May 29 23:12:09

Cur High Max Cur High Max Active Ports: 1 2 5 Active Users: 1 1 5Queue Entries: 0 2 40 Local Services: 0 0 ---

Memory Usage (%): 7 100 Allocated Pkts: 2551Free Bytes: 2286608 2461108 Freed Pkts: 1746Memory Fragments: 24 Largest Packet: 2268668NVRAM Memory: 5124 5882 Allocation Failures: 0

Queue Limit: 40 Password Limit: 3Inactive Timer: 30min Retrans Limit: 15 Session Limit: 4 Network Buffering: 4096 Time to Shutdown: N/A Prompt: ntc0:

Characteristics: Rlogin Lock AltPrompt Incoming Logins: Telnet Rlogin (Passwords Required)



show ip all CommandThe show ip all command displays the IP address of the hardware components, such as the Ethernet hub and router.

ntc0: show ip all SCS400 Version B2.0/202(021016) Name: sp3-ntcHardware Addr: 00-80-a3-56-36-8e Uptime: 0:41:16 Daytime: Thu May 29 23:12:21

Global Parameters: Routing

Name: Ethernet Type: Ethernet Netstate: Running Device/RefCount: ps0:/003IP Address: 10.0.0.33 Remote Address: (undefined)Netmask: 255.255.255.0 Network: 10.0.0.0TimeToLive Cost: 1 Largest Packet (MTU): 1500Pool Range Start: (undefined) Pool Range End: (undefined)Pool Status: Invalid Pool Addresses In Use 0

Listen to RIP packets: Enabled Send RIP packets: EnabledRip Update Time (seconds): 30 Rip Metric: 1Default Interface: Disabled Trusted Routers: DisabledProxy Arp: Enabled

Packets In: 370 Packets Out: 219Packet Errors: 0 Uptime: 41:16Last Packet In: 0:04 Last Packet Out: 0:07Last Routed Packet In: (Never) Last Routed Packet Out: (Never)

Destination Next Router Metric Source Timer Interface10.0.0.0 10.0.0.33 1 Local ------ Ethernet %Info: No trusted routers



show port CommandThe show ports command displays information related to ports.

ntc0: show ports

Port 1 : Username: rss Physical Port 1 (Local Mode)

Char Size/Stop Bits: 8/1 Input Speed: 9600 Flow Ctrl: Xon/Xoff Output Speed: 9600 Parity: None Modem Control: Disabled

Access: Local Local Switch: ^[ Backward: None Port Name: Port_1 Break Ctrl: Local Session Limit: 4 Forward: None Terminal Type: Soft() Idle Log Max Size: 0KB Alternate Break key: None Autostart char(s): --/-- Datasend char(s): --/-- Save chars (AS/DS): none/none Timer: (none)

Preferred Services: (Telnet)

Characteristics: Authenticate Inactive Limit Loss Notify PPP Telnet Pad Verify PPP Detect



CHAPTER 5

Troubleshooting Host Devices

This chapter describes how to troubleshoot components associated with a Sun StorEdge 6920 system host.


■ “Host Support” on page 55

■ “Using the Host Event Advisor” on page 56

Host SupportThe Sun StorEdge 6920 system supports the following operating systems:

■ Solaris 8, Solaris 9, and later releases

■ Sun Cluster 3.1

■ Microsoft Windows NT Enterprise Edition 4.0, Service Pack 6

■ Microsoft Windows 2000 Server and Windows 2000 Advanced Server, Service Pack 2

■ Hewlett-Packard HP-UX 11.i

■ IBM AIX 4.3.3, AIX 5.1 32-bit, and AIX 5.1 64-bit

■ Red Hat Linux 7.2

Each Sun StorEdge 6920 high-availability (HA) configuration supports up to 128 initiators. This enables the Sun StorEdge 6920 system, consisting of a maximum of 16 Sun StorEdge 6020 arrays, to allow up to 128 hosts with fibre channel (FC) storage area network (SAN) zoning.

The Sun StorEdge 6920 system provides native fabric (F port) host connectivity.

55


Using the Host Event AdvisorThe Storage Automated Diagnostic Environment Event Advisor enables you to sort host events by component, category, or event type. The Event Advisor describes the severity of an event, and tells whether and what action is require. Refer to the online help for more information.

▼ To Access the Event Advisor for a Host1. From any Storage Automated Diagnostic Environment page, click Service > Event

Advisor.

2. Select Host from the Category menu, and click GO.

FIGURE 5-1 shows the Host Service Advisor, from which you can select related criteria for the event you are troubleshooting.



FIGURE 5-1 Host Event Advisor

Chapter 5 Troubleshooting Host Devices 57


Actionable Events on the HostTABLE 5-1 lists actionable host events displayed by the Event Advisor, and indicates information on each event’s severity, cause, and recommended action.

TABLE 5-1 Actionable Host Events

Component Event Type Severity Information Recommended Action

array_errorarray_warningdisk.log

host.LogEvent Warning The Storage Automated Diagnostic Environment agent monitoring the array log file reports on the following:• Errors and Warnings

(“E” and “W”) found in the log file

• Notice and Information (“N” and “I”) lines about disk errors

• Notices about the battery

• Notices about the power and cooling unit (PCU) hold time

Note: This event is generated as a host event because it applies to an array that the Storage Automated Diagnostic Environment is not monitoring.

1. Use the Storage Automated Diagnostic Environment log-viewing function to check messages that were generated before and after this message.

2. Check volume integrity associated with the disk in question.

3. Replace the disk.4. Monitor the disk.

disk_capacity AlarmEvent Warning The system detected that /var/opt/SUNWstade is at or above 98% capacity

• Remove unused files and directories to free up space.

• Use a larger disk for /var/opt/SUNWstade

driver.link_down host.LogEvent Warning The Link Down message could indicate:• A Fibre Channel cable

has been removed. • There is trouble with a

Fibre Channel loop.

1. Check to see if a Fibre Channel cable has been removed.

2. Check for Fibre Channel errors.



driver.MPXIO_offline

host.LogEvent Warning The MPxIO multipathing software has noted that the path to a storage device has gone offline.

• Check the Topology view to see what devices are affected.

• Check all cables and connections.

• Check for other alerts that might indicate an underlying problem.

• Check the output of cfgadm -al and luxadm -e port, which might uncover other fabric problems.

driver.QLC_loop_offline

host.LogEvent Warning The Found Loop OFFLINE message could indicate:• A Fibre Channel cable

has been removed.• There is trouble with a

Fibre Channel loop.• The qlctest was run.

• Check whether a Fibre Channel cable has been removed.

• Check for Fibre Channel errors.

• Check to see if the qlctest(1M) was running at the time of failure.

driver.sf_offalert host.LogEvent Error The host system’s message log has recorded an error resulting from a problem with the Fibre Channel.

• Check the Storage Automated Diagnostic Environment for information about the host and the specifics about the host bus adapter HBA.

• Check the Topology view for devices attached to the HBA.

• Run a linktest diagnostic between the devices found in the topology.

• Replace the component that most likely caused this error message (GBIC, HBA, controller, or cable).

TABLE 5-1 Actionable Host Events (Continued)




driver.SSD_alert

host.LogEvent Error The Storage Automated Diagnostic Environment software scrubs the system log file for patterns that match known failure signatures. These warnings could indicate a faulty link.

The Storage Automated Diagnostic Environment software found enough WARNING messages in the system log file that it called out an Serial SCSI Driver (SSD) device and exceeded the threshold setting.

• Check the Storage Automated Diagnostic Environment for other error events for any of the devices being monitored.

• Check with the system administrator to determine activity on the SSD device.

• Run linktest to isolate a possible faulty GBIC, cable, or other faulty component.

driver.SSD_warn

host.LogEvent Warning The Storage Automated Diagnostic Environment software scrubs the system log file for patterns that match known failure signatures. These warnings could indicate a faulty link.

The Storage Automated Diagnostic Environment software found enough WARNING messages in the system log file that called out an SSD device and exceeded the threshold setting.

• Check for other error events for any of the devices being monitored.

• Check with the system administrator for activity on the SSD device.

• Run linktest to isolate a possible faulty GBIC, cable, or other faulty component.





hba AlarmEvent- Error A change occurred in the output of luxadm -e port.

1. Use luxadm -e port to confirm the HBA status and verify that all the paths are working.

2. Check the Storage Automated Diagnostic Environment for event information about the host and specifics about the HBA.

3. Check the topology for any devices that are attached to the HBA.

4. Run a linktest diagnostic between the devices found in the topology.

5. Replace the component most likely to have caused this event (the GBIC, HBA, controller, or cable).

hba AlarmEvent+ Warning The command luxadm -e port returned a change in the status of an HBA port previously recorded by the Storage Automated Diagnostic Environment.

Verify with the onsite system administrator that this was the expected result of any previous action, and that the port is now working properly.

lun.T300 AlarmEvent+AlarmEvent-

Error The Storage Automated Diagnostic Environment software found a change in the port status of one of the paths of this device.

The software executes luxadm display [WWN] on the host in search of output anomalies. The software then attempts to find the enclosure to which this path corresponds by reviewing its database of arrays and virtualization engines.

• Check the LED indicators on the ports to ensure proper light indications.

• Check the FRU status on this device for possible HA configuration controller failover.

• Replace the component at the point of origin for the light source.

• Replace the controller in the array.

• Replace the GBIC in the virtualization engine.





power.battery host.LogEvent Error This event is generated for battery messages found in the array log file that are not specific to any other type of battery event.This could indicate:• The battery warranty

period has expired.• The battery’s ability to

hold a charge has diminished to a point where it can no longer be recharged.

• The last refresh cycle failed to change the status of the battery.

• Check the Storage Automated Diagnostic Environment for the current state and status of the power control units in the array.

• Replace the suspect battery or the entire PCU in the array.





power.battery.refresh

host.LogEvent Warning The Sun StorEdge 6020 array has a BATD process that executes according to /etc/schd.conf file on the array. The process monitors the battery portion of the PCU.This event likely indicates that a refresh message was posted to the log file indicating that the batteries are recharging.f

• Monitor the cycle and ensure that it completed properly.

• Check the Storage Automated Diagnostic Environment for the current state and status of the PCUs in the array.

• Check the Storage Automated Diagnostic Environment for warranty dates and battery usage calculations.

• Replace the battery as described in “Removing and Replacing the Battery in the Array Power and Cooling Unit” on page 190.

power.battery.replace

host.LogEvent Warning A message was found in the message log indicating a battery status that warrants notification.This could indicate:

• The battery warranty period is about to expire.

• The battery hold time is low or the battery can no longer hold a charge.

• Check the Storage Automated Diagnostic Environment for the status of the PCU batteries for this array.

• Open a Tenet session to the array and run refresh -s to verify the battery state.

• Replace the battery as described in “Removing and Replacing the Battery in the Array Power and Cooling Unit” on page 190.







CHAPTER 6

Troubleshooting the Data Services Platform

This chapter provides information on troubleshooting the Data Services Platform (DSP) including recognizing DSP LED status indicators, and diagnosing problems according to those LEDs. This chapter includes the following sections:

■ “Before You Begin” on page 66

■ “About DSP Chassis LEDs” on page 66

■ “About DSP Card LEDs” on page 70

■ “Responding to a DSP Boot-Up Failure” on page 78

■ “Using the Event Advisor for DSP Events” on page 79

65


Before You BeginThe LED status tables in this chapter describe LEDs in three different states: off, on, and blinking, and presents what each status indicates. The LED status tables also suggest how to resolve problems by providing a bulleted number in the “See” column that can be referenced in the troubleshooting sections that follow each table. TABLE 6-1 provides an example of an LED status table.

About DSP Chassis LEDsThe DSP has three sets of LEDs to show the status of the chassis, the fans, and the power supplies. The chassis and fan LEDs are on the front of the DSP (FIGURE 6-1).

TABLE 6-1 LED Status Examples

LED Status Indication and Action (If Applicable)

LED is not lit (off).

LED is lit (on).

LED is blinking (on and off).



FIGURE 6-1 Front View of the Data Services Platform

The power LED is located on the back of the DSP.

AttentionPowerFan

Fan

Chassis LEDsPowerAttention

Chapter 6 Troubleshooting the Data Services Platform 67


FIGURE 6-2 Back View of the Data Services Platform

The following tables describe each of the LEDS on the DSP and the actions you may need to take.

Power LED

DC OK DC OK



Chassis Status

Fan Status

TABLE 6-2 Chassis LEDs


No power is applied.Check that power cables are connected securely.

Power is applied and the chassis is operating normally.

No action required.

Chassis requires attention.sThe chassis or one of the cards has a failure.

TABLE 6-3 Fan Assembly LEDs


No power is applied.• Check that power cables are connected securely.• Check that the fan assembly is seated properly.• Check whether one of the fans or the assembly is

defective.

Power is applied and the chassis is operating normally.No action required.

One or both fans have failed.Check that each fan can operate.

GreenPower Attention

Yellow


Yellow


Yellow


Yellow


Yellow


Yellow



Power Supply Status

About DSP Card LEDsThis section describes the LEDs for the cards that are installed in the DSP system chassis:

■ Management Information Card

■ Switch Fabric Card (SFC)

■ Storage Resource Card (SRC)

■ Storage Input/Output (SIO) Card

Management Information Card (MIC) StatusEach system has two management interface cards (MICs) (FIGURE 6-3), that you access from the back of the cabinet. The MIC is not in the data path.

Each MIC has seven LEDs: the Ready, Attention, Power, and Redundancy LEDs are on the left side of the card, and the Act1, Act 2 and Link LEDs are on the right side.

FIGURE 6-3 Management Information Card

TABLE 6-4 Power Supply LEDs


GreenDC OK

No power is applied, or the module has failed.• Check that power cables are connected securely.• Check that the power module is functioning.

GreenDC OK

Power is applied and DC output is normal.No action required.



TABLE 6-5 MIC Ready, Power, Redund and Attention LEDs


Normal operation.Card is acting as master.No action required.

No power is applied.Check that: • Power cables are connected securely.

• The MIC is seated properly.• The MIC is not defective.

Hardware failure.

Check that the MIC: • Is seated properly.• Is in the proper slot: 5 or 6.• Has a valid image.• Is not defective.

Hardware or software failureCheck that the MIC is: • Seated properly.• Not defective.

Hardware or software failureCheck that the MIC is: • Seated properly.• Not defective.

GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow



Hardware or software failure.Check that the MIC is: • Seated properly.• In proper slot: Slot 1.

Card is booting.No action required.

Normal operation but redundancy is active. Card is operating as the alternate master.No action required.

TABLE 6-6 MIC Act 1 LED


GreenAct 1

No activity on the link.No action required.

GreenAct 1

Activity on the link.No action required.

TABLE 6-5 MIC Ready, Power, Redund and Attention LEDs (Continued)


GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow



Switch Fabric Card (SFC) StatusThe Switch Fabric Card (SFC) (FIGURE 6-4) has four LEDs: Ready, Power, Redund, and Attention. You access the SFC from the front of the cabinet. The SFC is in the data path.

TABLE 6-7 MIC Act 2 LED


GreenAct 2

No P CMCIA card is installed.No action required.

GreenAct 2

A P CMCIA card is inserted in the slot.No action required.

TABLE 6-8 MIC Link LED


GreenLink

No connection.Check that:

• All connections are undamaged and secure.• Cable type is correct (straight-through).• Devices at both ends of the link are powered on.

GreenLink

Connection is functioning.

No action required.



FIGURE 6-4 Switch Fabric Card

TABLE 6-9 SFC Ready, Power, Redund, and Attention LEDs


Normal operation.No action required.

No power is applied.Check that: • Power cables are connected securely.• The SFC is seated properly.• The SFC is not defective.

Hardware failure.Check that the card is: • Seated properly.• Not defective.

Hardware or software failure.Check the event log. See “To Display the Event Log for a Specific Device” on page 15.Check that the card is:

• Seated properly.• Not defective.



GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow



Storage Resource Card (SRC) StatusThe Storage Resource Card (SRC) (FIGURE 6-5) has four LEDs: Ready, Power, Sync, and Attention. You access the SRC from the front of the cabinet. The SRC is in the data path.

Hardware or software failure.Check the event log. See “To Display the Event Log for a Specific Device” on page 15.


Normal operation but redundancy is active. Card is operating as the alternate master.No action required.

TABLE 6-9 SFC Ready, Power, Redund, and Attention LEDs (Continued)


GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow

GreenReady

Redund

Power

YellowAttention

Green

Yellow



FIGURE 6-5 Storage Resource Card

TABLE 6-10 SRC Ready, Power, Sync and Attention LEDs


Normal operation.No action required.

No power is applied.Check that the card is: • Seated properly.• Not defective.

Hardware failure.Check that the card is:



• Seated properly.

• Not defective

GreenPower

Attention

Ready

YellowSync

Green

Red

GreenPower

Attention

Ready

YellowSync

Green

Red

GreenPower

Attention

Ready

YellowSync

Green

Red

GreenPower

Attention

Ready

YellowSync

Green

Red



SIO Card StatusThe storage I/O (SIO) card (FIGURE 6-6) contains two LEDs for each gigabit interface converter (GBIC): Link and Act. You access the SIO card from the back of the cabinet. The SIO card is in the data path.


• Seated properly.• Not defective

Hardware or software failure.Check the event log. See “To Display the Event Log for a Specific Device” on page 15.


TABLE 6-10 SRC Ready, Power, Sync and Attention LEDs (Continued)


GreenPower

Attention

Ready

YellowSync

Green

Red

GreenPower

Attention

Ready

YellowSync

Green

Red

GreenPower

Attention

Ready

YellowSync

Green

Red



FIGURE 6-6 Storage Input/Output Card

Responding to a DSP Boot-Up FailureIf the Data Services Platform does not boot after a shutdown, the failure could have several causes, both hardware and software. Check the messages reported on the console and in the event log to diagnose the problem. If your site has enabled the Sun Service Remote Response feature, the problem is reported automatically.

TABLE 6-11 SIO Card Link LED


GreenLink

No connection.Check that:• All connections are undamaged and secure.• Cable type is correct (straight-through).• Devices at both ends of the link are powered on.

GreenLink

Connection.No action required.

TABLE 6-12 SIO Card Act LED


YellowAct

No activity on the link.

YellowAct

Activity on the link.



Using the Event Advisor for DSP EventsThe Storage Automated Diagnostic Environment Event Advisor enables you to sort DSP-related events by component, category, or event type. The Event Advisor describes an event and its severity and tells you what, if any, action should be taken. Refer to online help for more information.



▼ To Access the DSP Events1. From any Storage Automated Diagnostic Environment page, click Service > Event

Advisor.

2. Select dsp (Sun DSP) from the Category menu, and click Find Events.

FIGURE 6-7 shows the DSP Event Advisor, from which you can select related criteria for the event you are troubleshooting.

FIGURE 6-7 Event Advisor Showing DSP Events



TABLE 6-13 lists actionable events for the Sun StorEdge 6020 array.

TABLE 6-13 Storage Automated Diagnostic Environment Service Advisor for the Data Service Processor

Component Event Type Severity InformationRecommendedAction

aggregate ConnectivityLostEvent

Error This message indicates that connectivity was lost between the DSP and an array, both of which are specified in the message description.This event is generated when device ports go offline and other events are confirming it.

Check the Storage Automated Diagnostic Environment for the current status of the device, as well as for any additional events that might have occurred

aggregate DeviceLostEvent Err/Critical

The DSP is no longer available, confirmed by subevents.

chassis.fan AlarmEvent Warning This event indicates any one of several possible negative state changes to the fan assembly. The event description indicates the component number.Probable causes include:

• Defective fan• Lack of power to the

fan

• Check the Storage Automated Diagnostic Environment for the current status of the device, as well as for any additional events that might have occurred.

• Check the fan assembly LEDs as described in “Fan Status” on page 69.

• If necessary, replace the fan assembly.



chassis.power AlarmEvent Warning This event indicates a negative state change to a power supply (indicated in the message description) in the DSP.


• Check the power supply LEDs as described in “Power Supply Status” on page 70.

• If necessary, replace the power supply.

device_error LogEvent Warning A message in the DSP log file is classified as an error.

Check the Storage Automated Diagnostic Environment for the current status of the device, as well as for any additional events that might have occurred.

fcserverInstance StateChangeEvent

Error This message indicates that the specified fcserver instance on the DSP has gone offline. Probable causes Include:• Maintenance• Reconfiguration

1. Verify whether maintenance or a deliberate reconfiguration occurred.

2. If not, check the Storage Automated Diagnostic Environment for the current status of the device, as well as for any additional events that might have occurred.





ib DeviceLostEvent Err/Critical

This event indicates lost communication (InBand([Host-Name])) with [DSP-Name] ([IP-Address]).

This event is established using luxadm. Monitoring may not be activated for a particular DSP.

1. Run the luxadm command (luxadm probe, luxadm display).

2. Verify cables, GBICs, power, and connections along the data path.3. Check the SAN topology to identify the failing segment of the data path.

interface.loopcard.cable

LoopCable|Disconnect

Error This event indicates that a Loop Interconnect Cable is disconnected or has failed. The message specifies the device and the port.

Examine the message and reconnect the cable.

log_alert LogEvent Error This event indicates that there is a message in the DSP log file classified as an Alert.

Check the Storage Automated Diagnostic Environment for the current status of the device, as well as any additional events that might have occurred.

log_critical LogEvent Error This event indicates that there is a message in the DSP log file classified as Critical.


log_error LogEvent Error A message in the DSP log file is classified as an error.






MIC ComponentRe-moveEvent

Error This message indicates that the MIC specified in the event description was removed or had a failure. Probable causes include:• Maintenance• Reconfiguration

1. Verify whether removal or reconfiguration was deliberate.


3. Replace the MIC if necessary, as described in “Replacing the DSP and DSP FRUs” on page 129.

MIC StateChangeEvent

Error This message indicates that the MIC in the specified DSP has gone offline.


• Check the LEDs on MIC as described in “Management Information Card (MIC) Status” on page 70.

• If necessary, replace the MIC





oob CommunicationLostEvent

Err/Critical

This out-of-band error means that the DSP failed to answer to ping or failed to return valid status.Probable causes include:• Very slow network• Ethernet connection

to this DSP is lost

• Check power on the DSP.

• Check Ethernet connectivity to the affected DSP.

• Verify that the PC card on the active MIC is inserted properly.

• Increase the http and/or ping timeout in Utilities > System > Timeouts. The default timeouts are 10 seconds for a ping and 60 seconds for HTTP (tokens).

port StateChangeEvent

Error This message indicates that a port on the DSP has logged out of the fabric and gone offline. The message description specifies the port.


power StateChangeEvent

Warning This event indicates a negative change in the power supply in the DSP. The message description indicates which power supply is experiencing a problem.


• Check the power supply LEDs as described in “Power Supply Status” on page 70.

• If necessary, replace the power supply.





SFC ComponentRe-moveEvent

Error This message indicates that the SFC specified in the event description was removed or had a failure. Probable causes include:• Maintenance• Reconfiguration



3. Replace the SFC if necessary, as described in “Replacing the DSP and DSP FRUs” on page 129.

SFC StateChangeEvent

Error This message indicates that the SFC in the specified DSP has gone offline.


• Check the LEDs on the SFC as described in “Switch Fabric Card (SFC) Status” on page 73.

• If necessary, replace the SFC.





SIO ComponentRe-moveEvent

Error This message indicates that the SIO Card specified in the event description was removed or had a failure.Probable causes include:• Maintenance• Reconfiguration



3. Replace the SIO if necessary, as described in “Replacing the DSP and DSP FRUs” on page 129.

SIO StateChangeEvent

Error This message indicates that the SIO card in the specified DSP has gone offline.


• Check the LEDs on the SIO card as described in “SIO Card Status” on page 77.

• If necessary, replace the SIO card.





SRC ComponentRemoveEvent

Error This message indicates that the SRC specified in the event description was removed or had a failure. Probable causes include:• Maintenance• Reconfiguration



3. Replace the SRC if necessary, as described in “Replacing the DSP and DSP FRUs” on page 129.

SRC StateChangeEvent

Error This message indicates that the SRC in the specified DSP has gone offline.


• Check the LEDs on ten SRC as described in “Storage Resource Card (SRC) Status” on page 75.

• If necessary, replace the SRC.





ConnectivityLossEvent

Error This message indicates that connectivity was lost between two devices. The message description indicates both devices and ports.

Examine the message and reconnect the cable, if a physical disconnection has occurred. Otherwise, check the Storage Automated Diagnostic Environment for the current status of the device, as well as for any additional events that might have occurred.





LinkEvent_CRC Warning This event indicates an increase in the Cyclic Redundancy Check (CRC) counter between two components on the Fibre Channel. The threshold is 10/24 hr.Probable causes include:• GBICs• Fibre Channel cables • Device optical

connections


• Replace the GBICs associated with the link to the device specified in the event description.

• Reroute or replace the cables associated with the device as necessary.

LinkEvent_ITW Warning This event indicates an increase in the Invalid Transmitting Word (ITW) counter detected between two components on the Fibre Channel. The Threshold is 10/1 hr. Probable causes include:• GBIC• Fibre channel cables • Device optical

connections








LinkEvent_SIG Warning This event indicates an increase in the Signal Loss (SIG) counter detected between two components on the Fibre Channel. The Threshold is 10/1hr. TProbable causes include:• GBICs• Fibre Channel cables• Device optical

connections










CHAPTER 7

Troubleshooting Sun StorEdge 6020 Arrays

This chapter describes how to troubleshoot Sun StorEdge 6020 arrays. It contains the following sections:

■ “About Sun StorEdge 6020 Arrays” on page 93

■ “About Expansion Units” on page 96

■ “About Multipathing” on page 96

■ “About Array LEDs” on page 100

■ “Using the Event Advisor fro Array Events” on page 109

About Sun StorEdge 6020 ArraysThe Sun StorEdge 6020 array is a high-performance, modular, scalable storage device. Depending on the number of drives available, factory-configured Sun StorEdge 6920 system arrays are preconfigured as one RAID 5 virtual disk (7 to 13 drives) or two RAID-5 virtual disks (14 drives).

Caution – Perform storage pool and volume configuration tasks from the Storage Service Processor using the graphical user interface (GUI). Changing array settings through serial or Ethernet access directly on the array could cause problems at the configuration service level.

93


Supported ConfigurationsThe naming convention used in the configuration is (number of controller trays x number of total trays). A 2x2 configuration consists of two controllers and two trays. A 2x4 configuration consists of two controllers and four trays.

High-availability (HA) configurations are dual-controller arrays with expansion capability to provide additional capacity. They are as follows:

■ Array with two controllers and two disk trays (2x2)

■ Array with two controllers and four disk trays (2x4‘)

Default Configuration SettingsEach new array is delivered with default settings for system, boot, volume, and port management parameters. During installation the default configuration and some or all of these settings may be changed.

User InterfacesYou can configure the array using three different interfaces:

■ Array telnet command-line interface (CLI)

■ Graphical user interface (GUI)

■ Configuration Service CLI

The GUI and the Configuration Service CLI reside on an external host. This host can be any host configured to communicate with the system through a Telnet session.



Array FeaturesThe features described in this section are available on a Sun StorEdge 6920 system after the volume-slicing feature has been enabled.

RAID-Striped Data With Standby Hot Spare

The Sun StorEdge 6920 system includes Sun StorEdge 6020 array units preconfigured with one or two RAID-5 virtual disks. The customer does not have to create RAID virtual disks but, if desired can change the configuration to RAID-1 or RAID-0.

■ RAID 5 – In a RAID-5 configuration, data and parity information are striped across the drives in segments. Because of this parity, if a single drive fails, data can be recovered from the remaining drives. Two drive failures cause all data to be lost. A RAID-5 virtual disk has the data capacity of all the drives in the logical unit, less one. For example, a five-drive RAID-5 volume with 73-Gbyte drives has a capacity of (5 – 1) x 73 = 292 Gbytes.

■ RAID 1 – Each data block in a RAID-1 virtual disk is mirrored on two physical drives. If one of the mirrored pair fails, the data from the other drive is used. Because the data is mirrored in a RAID-1 configuration, the volume has only half the capacity of the assigned drives. For example, if you create a four-drive RAID- 1 virtual disk with 36-Gbyte drives, the resulting data capacity is 4 x 36 / 2 = 72 Gbytes.

LUN Mapping

LUN mapping enables customers to create up to 64 virtual drives from physical LUNs on a Sun StorEdge 6920 HA configuration, as required.

LUN Masking

The Sun StorEdge 6920 system provides support for LUN masking, a key feature in large storage systems. Each host bus adapter (HBA) port has a manufacturer-assigned a worldwide name (WWN), used for identification purposes. WWNs are assigned individually or in groups to specific LUNs. LUN masking is the antithesis of LUN mapping, meaning when you exclude a LUN from being mapped to an HBA, you have masked the LUN from being seen by that HBA.

Sun StorEdge 6020 arrays support a maximum of 64 LUNs per HA configuration and support HBA groups. Sun StorEdge 6020 arrays can be used to set LUN access control properties for a group of host HBAs. All settings are done via the Sun StorEdge 6920 management interfaces.

Chapter 7 Troubleshooting Sun StorEdge 6020 Arrays 95


About Expansion UnitsThe controller-less Sun StorEdge 6020 array’s hardware components include the following:

■ Power sequencer■ AC power cable■ Key switch■ Fan tray

About MultipathingThe Sun StorEdge 6920 has multipathing features as follows:

■ Array side failover – whereby, for example, if a controller fails, the raidsets (virtual disks) that belong to that controller fail over to the surviving controller.

■ Host side failover – whereby, for example, if the I/O fails down one path, I/O continues down the other path.

Manually Halting the I/OAs an alternative to using the Sun StorEdge Traffic Manager (MPxIO) software, you can manually halt the I/O using one of two methods:

■ Quiesce the I/O

■ Unconfigure the controller/device path

These methods are explained in the following sections.

▼ To Quiesce the I/O

1. Determine the path you want to disable.

2. Type the following command:

# cfgadm -c unconfigure device



▼ To Unconfigure the Controller/Device Path

● Type the following command:

▼ To Return the Controller/Device Path to Production


2. Verify that I/O has resumed on all paths.

▼ To View Dynamic Multipathing (DMP) PropertiesDynamic Multipathing (DMP) is a VERITAS Volume Manager feature that provides an alternate pathing mechanism for rerouting data in the event of a controller failover.

# cfgadm -al

Ap_Id Type Receptacle Occupant Condition

c0 scsi-bus connected configured unknownc0::dsk/c0t0d0 disk connected configured unknownc0::dsk/c0t1d0 disk connected configured unknownc1 scsi-bus connected configured unknownc1::dsk/c1t6d0 CD-ROM connected configured unknownc2 fc-fabric connected configured unknownc2::210100e08b23fa25 unknown connected unconfigured unknownc2::2b000060220041f4 disk connected configured unknownc3 fc-fabric connected configured unknownc3::210100e08b230926 unknown connected unconfigured unknownc3::2b000060220041f9 disk connected configured unknownc4 fc-private connected unconfigured unknownc5 fc connected unconfigured unknown

# cfgadm -c configure c2::2b000060220041f4




# vxdisk list Disk_1

Device: Disk_1devicetag: Disk_1type: slicedhostid: diag.xxxxx.xxx.COMdisk: name=t3dg02 id=1010283311.1163.diag.xxxxx.xxx.comgroup: name=t3dg id=1010283312.1166.diag.xxxxx.xxx.comflags: online ready private autoconfig nohotuse autoimport importedpubpaths: block=/dev/vx/dmp/Disk_1s4 char=/dev/vx/rdmp/Disk_1s4privpaths: block=/dev/vx/dmp/Disk_1s3 char=/dev/vx/rdmp/Disk_1s3version: 2.2iosize: min=512 (bytes) max=2048 (blocks)public: slice=4 offset=0 len=209698816private: slice=3 offset=1 len=4095update: time=1010434311 seqno=0.6headers: 0 248configs: count=1 len=3004logs: count=1 len=455Defined regions: config priv 000017-000247[000231]: copy=01 offset=000000 enabled config priv 000249-003021[002773]: copy=01 offset=000231 enabled log priv 003022-003476[000455]: copy=01 offset=000000 enabledMultipathing information:

numpaths: 2c20t2B000060220041F4d0s2 state=enabledc23t2B000060220041F9d0s2 state=enabled

# vxdmpadm listctlr all

CTLR-NAME ENCLR-TYPE STATE ENCLR-NAME=====================================================c0 OTHER_DISKS ENABLED OTHER_DISKSc2 SENA ENABLED SENA0c3 SENA ENABLED SENA0c20 Disk ENABLED Diskc23 Disk ENABLED Disk



The vxdisk output includes two physical paths to the LUN:

■ c20t2B000060220041F4d0s2

■ c23t2B000060220041F9d0s2

Both of these paths are currently enabled with DMP.

4. Use the luxadm(1M) command to display further information about the underlying LUN.

# /usr/sbin/luxadm display /dev/rdsk/c20t2B000060220041F4d0s2

DEVICE PROPERTIES for disk: /dev/rdsk/c20t2B000060220041F4d0s2 Status(Port A): O.K. Vendor: SUN Product ID: SESS01 WWN(Node): 2a000060220041f4 WWN(Port A): 2b000060220041f4 Revision: 080C Serial Num: Unsupported Unformatted capacity: 102400.000 MBytes Write Cache: Enabled Read Cache: Enabled Minimum prefetch: 0x0 Maximum prefetch: 0x0 Device Type: Disk device Path(s):/dev/rdsk/c20t2B000060220041F4d0s2/devices/pci@a,2000/pci@2/SUNW,qlc@4/fp@0,0 ssd@w2b000060220041f4,0:c,raw

# luxadm display /dev/rdsk/c23t2B000060220041F9d0s2

DEVICE PROPERTIES for disk: /dev/rdsk/c23t2B000060220041F9d0s2 Status(Port A): O.K. Vendor: SUN Product ID: SESS01 WWN(Node): 2a000060220041f9 WWN(Port A): 2b000060220041f9 Revision: 080C Serial Num: Unsupported Unformatted capacity: 102400.000 MBytes Write Cache: Enabled Read Cache: Enabled Minimum prefetch: 0x0 Maximum prefetch: 0x0 Device Type: Disk device Path(s): /dev/rdsk/c23t2B000060220041F9d0s2 /devices/pci@e,2000/pci@2/SUNW,qlc@4/fp@0,0/ssd@w2b000060220041f9,0:c,raw



▼ To Return the DMP-Enabled Paths to Production1. Type the following command:

2. Verify that the path has been re-enabled by typing the following command:

About Array LEDsThe array incorporates a number of Service Indicator Standard (SIS) light-emitting diodes (LEDs) that are used to assist in determining the status of the array as well as in repairing it. The array unit and each array FRU have SIS LEDs, which have the following general meanings:

■ Green – indicates that the unit or FRU is operating properly.

■ Yellow or Amber – indicates that the unit or FRU requires service.

■ Blue – means that it is safe to remove the unit or FRU and to replace it.

■ White – indicates the location of the array unit.

A white, or locator, LED is implemented on the front and back of the array. No other FRU within the array has a white LED. The white LED is used to lead you to the correct array in need of service. LEDs on FRUs within the array indicate the FRU that requires service and the FRU’s current status. This section contains information about the LEDs for the array and each array FRU. This section also includes illustrations of the LED locations and tables of LED descriptions for all types of LED indicators.

# vxdmpadm enable ctlr=cn

# vxdmpadm listctlr all



Array Unit LEDsThe array contains SIS LEDs that are visible from the front and back of the array unit (FIGURE 7-1).

FIGURE 7-1 Array Unit SIS LEDs

TABLE 7-1 lists the possible conditions of the LEDs and describes each state.

TABLE 7-1 Array Unit SIS LEDs

White Amber Green Indication

Off Off Off Array is not powered (no AC power).

Off n/a On No locator action is active to this tray.

On n/a On A locator action is underway for this tray.

Front view

Back view

White

Amber

Green



Disk Drive LEDsEach disk drive has three SIS LEDs, viewable from the front of the array only(FIGURE 7-2).

FIGURE 7-2 Disk Drive LEDs

n/a Off On Array is powered on to standby or to full power, and no service action is required.

n/a On On A service action is required for an included FRU, and the array is powered on to standby or to full power.

Fast blink* Fast blink On Array is performing a power-on test or tray LED check.

* Fast blink is measured as four blinks per second.

TABLE 7-1 Array Unit SIS LEDs (Continued)

White Amber Green Indication

BlueAmber

Green




Caution – During a data reconstruction on the disk drive, the blue SIS LED will light, indicating a “ready to replace” state for the drive. Do not remove the drive at this time; this is a false LED signal.

TABLE 7-2 Disk Drive LEDs

Blue Amber Green Indication

Off Off Off Drive is not mated or is not powered on.

On Off Off Drive is OK to remove; drive is not ready; software is deconfigured; drive is mated and is powered on.

Off Off Slow blink*

* Slow blink is measured as one second on and one second off. Fast blink is measured as four blinks per second.

Drive is not ready; drive is powered on and is either spinning up or down, or is waiting for the spin-up command.

Off Off On Drive is ready and is spun-up.

Off Off Mainly on, flashing off at a visible frequency

Drive is ready with SCSI activity.

Off On On Drive service action is required; drive is ready; drive is not OK to remove.

Off On Slow blink Drive service action is required; drive is not ready; drive is not OK to remove.

On On Off Drive is OK to remove; drive service action is required; drive is not ready; software is deconfigured.

On Off Slow blink Drive is OK to remove; drive not ready; software is deconfigured; drive is powered on and is either spinning up or down, or is waiting for the spin-up command.

Fast blink Fast blink n/a Array power-on test, drive insertion test, or array LED check is in progress.



Power and Cooling Unit LEDsEach power and cooling unit (PCU) has three SIS LEDs, viewable from the back of the array (FIGURE 7-3).

FIGURE 7-3 Power and Cooling Unit LEDs


TABLE 7-3 Power and Cooling Unit LEDs


Off Off Off PCU is not mated; there is no AC power, or this is the normal state for PCU in standby.

Off Off On PCU is ready; all voltages are at rated value.

Off Off Fast blink* PCU is ready, battery power is available, and all DC voltages are within tolerance.

Off On On PCU service action is required; the PCU is ready.

Off On Off PCU service action is required; the PCU is not ready.

BlueAmber

Green

Power switch



Interconnect Card LEDsEach interconnect card has three SIS LEDs and two channel-status LEDs viewable from the back of the array (FIGURE 7-4).

FIGURE 7-4 Interconnect Card LEDs

On On Off PCU is OK to remove; PCU service action is required; PCU is not ready; PCU software is deconfigured.

On Off Off PCU is OK to remove; PCU is software deconfigured; no service action is required.

Fast blink Fast blink Fast blink Array power-on test, PCU insertion test, or array LED test is in progress.


TABLE 7-3 Power and Cooling Unit LEDs (Continued)


BlueAmber

Green

Channel-status LED

Channel-status LED



TABLE 7-4 lists the possible conditions of the SIS LEDs and describes each state.

TABLE 7-5 lists the possible conditions and states for the interconnect card channel status LEDs.

Controller Card LEDsEach controller card has three SIS LEDs, an Fibre Channel Arbitrated Loop (FC-AL) channel-status LED, and an Ethernet channel-status LED viewable from the back of the array (FIGURE 7-5 and FIGURE 7-6).

TABLE 7-4 Interconnect Card SIS LEDs


Off Off Off Interconnect card is not mated or there is no standby power.

Off Off On Interconnect card is Ready; standby power is OK.

Off On On Interconnect card service action is required; interconnect card is ready.

Off On Off Interconnect card service action is required; interconnect card is not ready.

On Off Off Interconnect card is OK to remove; interconnect card is not ready; software is deconfigured.

On On Off Interconnect card is OK to remove; interconnect card service action is required; interconnect card is not ready; interconnect card software is deconfigured.

Fast blink*


Fast blink Fast blink Array power-on test, interconnect card insertion test, or array LED check is in progress.

TABLE 7-5 Interconnect Card Channel Status LEDs

Amber Green Indication

Off On Interconnect cable is present; interconnect card is OK.

Off Off Interconnect cable is missing or the port has been shut down.

On Off Interconnect cable is present; no signal is detected.



FIGURE 7-5 Controller Card SIS LEDs

FIGURE 7-6 Controller Card Communication Channel LEDs

BlueAmber

Green

FC-AL channel-status LED

Ethernet channel LED states VAL

ACT

100 bps

10 bps

Ethernet transfer rate

Ethernet channel status Valid (VAL) and Active (ACT)



TABLE 7-6 lists the possible conditions of the controller card SIS LEDs and describes each state.

TABLE 7-7 lists the possible conditions of the FC-AL channel-status LED and describes each state.

TABLE 7-6 Controller Card SIS LEDs


Off Off Off Controller not is mated, or is not powered, or is not booted.

Off Off On Controller is ready.

Off On On Controller service action is required; controller is ready.

Off On Off Controller service action is required; controller is not ready.

On On Off Controller is OK to remove; controller service action is required; controller is not ready; controller software is deconfigured.

On Off Off Controller is OK to remove; controller is not ready; software is deconfigured.

Fast blink*


Fast blink n/a Array power-on test, controller insertion test, or array LED check is in progress.

TABLE 7-7 FC-AL Channel-Status LEDs

Green Amber Indication

Off Off Port is disabled.

Off On Port is enabled; no signal is detected or there is a laser fault

On Off Port is enabled; signal is detected.

Blink Off Port is enabled; signal is detected; port is transferring information.



TABLE 7-8 lists the possible conditions of the Ethernet channel-status LEDs and describes each state.

Determining FRU FailuresFRU failures are reported by an alarm or message notification from the tool that is used to monitor the array, such as the Storage Automated Diagnostic Environment. The failed FRU displays a blinking amber LED. FRU failures can also be found in the syslog output of the array activity.

Before replacing a FRU on the basis of an LED indicator, verify the FRU’s failure by using a diagnostic tool such as the Storage Automated Diagnostic Environment or the array CLI commands.

Using the Event Advisor fro Array EventsThe Storage Automated Diagnostic Environment Event Advisor enables you to sort Sun StorEdge 6020 array events by component, category, or event type. The Event Advisor describes an event and its severity and tells what, if any, action should be taken. Refer to online help for more information.

TABLE 7-8 Ethernet Channel-Status LEDs

LED Green Function

VAL/ACT Off Link invalid.

On Link valid.

Blink Link valid and active.

100 bps or 10 bps On 100 Mbps communication speed

Off 10 Mbps communication speed



▼ To Access Array Events1. From any Storage Automated Diagnostic Environment page, click Service > Event

Advisor.

2. Select 6020 (Sun6020 array), from the Category menu, and click Find Events.

FIGURE 7-7 shows the Event Advisor, from which you can select related criteria for the event you are troubleshooting.

FIGURE 7-7 Event Advisor Showing Array Events



TABLE 7-9 lists actionable events for the Sun StorEdge 6020 arrays.

TABLE 7-9 Actionable Array Events


6020ofdg DiagnosticTest- Error The results of ofdg testing on a Sun StorEdge 6020 array resulted in a failed status. ofdg is an offline diagnostic utility. The failed state is a result of a health check failure.

• 1. Check Test Manager for details about why the test failed.

• 2. Review the syslog file from the unit from where ofdg was run. The complete ofdg results are written to the unit’s syslog facility.

6020volverify DiagnosticTest- Error The test 6020volverify ([Host-Name]) on [Array-Name] ([IP-Address]) failed.

The 6020volverify command compares the constructed parity with the stored parity. This implementation assumes that the integrity of the data drives is correct. The fix option will update the parity drive only.

Check Test Manager for details about why the test failed.

aggregate DeviceLostEvent System is Down

Device 6020b0 is no longer available, confirmed by subevents.



array_errorarray_warning

LogEvent Warning The Sun StorEdge 6020 array message log /var/adm/messages.6020 reports the following:• Warnings and errors

found in the Sun StorEdge 6020 array log file.

• Notice and information lines about Sun StorEdge 6020 array disks.

• Notices about the battery.

• Notices about the PCU hold time.

The probable cause is that the Storage Automated Diagnostic Environment detected the above pattern in the array log file.

• Use the Storage Automated Diagnostic Environment log- viewing mechanism to check messages generated before and after this message.

• Check the volume integrity associated with the disk in question.

• Replace this disk.

cacheMode AlarmEvent Warning The Storage Automated Diagnostic Environment has detected that the array’s caching mode has been disabled.The probable cause is a FRU failure affecting the cache, which causes the array to stop caching data.

• Check the Storage Automated Diagnostic Environment for events and alerts associated with the Array-Name detailed in the actual event.

• Replace the FRU if necessary.

TABLE 7-9 Actionable Array Events (Continued)




controller StateChangeEvent-

Error The Sun StorEdge 6020 controller is disabled.

1. Use Telnet to connect to the affected controller.2. Verify the controller state with fru stat and sys stat.3. Re-enable the controller if possible (using enable u).4. Run logger -dmprstlog from a serial port session on the affected controller.Note: The output from logger will only go to the syslog facility. Review syslog on the master controller to determine the cause of the failure.5. Replace the controller as indicated by the non-volatile random access memory (NVRAM) failure code.

controller ComponentRemoveEvent

Error The Sun StorEdge 6020 array has reported that a controller has been removed from the chassis.

Replace the controller within 30 minutes of power shutdown.

controller.port LogEvent Error The Sun StorEdge 6020 array has detected an internal loop failure and has logged it.

Check the Storage Automated Diagnostic Environment for additional events related to the device called out in the log file.





device_path AlarmEvent Error A LUN presented to the host is no longer available to the Solaris Operating System. The Storage Automated Diagnostic Environment generates this event when a device is no longer listed on the luxadm probe list.

1. Check the Storage Automated Diagnostic Environment for events relating to the device in the message.

2. Check the Storage Automated Diagnostic Environment Topology view for link errors associated with the device connections.

3. Check the Storage Automated Diagnostic Environment for events associated with the components connected to the device in the topology message.

disk StateChangeEvent-

Error The Sun StorEdge 6020 array has reported that a disk has failed.

Drive Status Messages:0 Drive mounted

2 Drive present3 Drive is spun up4 Drive is disabled5 Drive has been replaced7 Invalid system area on drive9 Drive not present

D Drive disabled; drive is being reconstructedS Drive substituted

1. Use Telnet to connect to the affected Sun StorEdge 6020 array.

2. Verify the disk state with vol stat, fru stat, and fru list commands.





disk LogEvent Error The Storage Automated Diagnostic Environment has detected a possible problem in the Sun StorEdge 6020 array message log.

The Storage Automated Diagnostic Environment looks for all command error messages as an indication of possible disk failure.

1. Use the Storage Automated Diagnostic Environment log- viewing mechanism to check messages generated before and after this message.

2. Replace the disk.

disk ComponentRemoveEvent

Error The Sun StorEdge 6020 array has reported that a disk has been removed from the chassis.

The probable cause is that a system administrator has changed the monitoring status of the device called out in the event message.

1. Verify with the administrator that this is an expected action.

2. Check the Storage Automated Diagnostic Environment for the current status of the device, as well as for any additional events that might have occurred.






disk.log LogEvent Warning The Storage Automated Diagnostic Environment agent monitoring the array log file reports on the following:• Errors and warnings

(depicted by “E:” and “W:”) found in the log file.

• Notice and information (depicted by “N:” and “I:”) lines about disks.

• Notices about the battery.

• Notices about the PCU hold time.

The probable cause is that the Storage Automated Diagnostic Environment detected the above pattern in the array log file.

1. Use the Storage Automated Diagnostic Environment GUI log viewing functions to check messages before and after this message.

2. Check volume integrity associated with the disk in question.

3. Replace the disk.4. Monitor the disk.

disk.pathstat AlarmEvent- Error The Storage Automated Diagnostic Environment, while monitoring the tokens that are equivalent to the .disk pathstat uXdNN command. found that the state of the disk pathstat changed.

The probable cause is that a disk drive has experienced a failover of one of its loops.

1. Check the Storage Automated Diagnostic Environment for events relating to the array called out in the message.

2. Check the Storage Automated Diagnostic Environment for status of the disk drive called out in the message.3. Replace the disk.





disk.port AlarmEvent- Error The array has reported that one port of a dual-ported disk has failed.Drive Status Messages:0 Drive mounted2 Drive present3 Drive is spun up4 Drive is disabled5 Drive has been replaced7 Invalid system area on drive9 Drive not presentD Drive disabled; drive is being reconstructedS Drive substituted

1. Check the status of the array.2. Use Telnet to connect to the array and verify the disk state with fru stat, fru list, and vol commands.3. Replace the disk, if necessary.

disk.senseKey LogEvent Warning PFA Sense Key information reported from a disk, indicates a problem with the disk.

1. Use the Storage Automated Diagnostic Environment log- viewing mechanism to check messages generated before and after this message.


disk.temperature AlarmEvent- Info While monitoring the temperature of the disks in the enclosure,.the Storage Automated Diagnostic Environment detected a discrepancy in the token information about the disk temperature returned by the array.

Check the Storage Automated Diagnostic Environment for additional information pertaining to the disk called out in the event.

driver.SSD_WARN LogEvent Warning The MPxIO support may be set differently between the Sun StorEdge 6020 array and the host.

Check MPxIO settings.





enclosure QuiesceEndEvent

Info Monitoring has been temporarily stopped.The probable cause is that an administrator has changed the monitoring status of the device called out in the event message.

Verify with the administrator that this is an expected action. Additional events might have occurred.

ib Comm_LostEvent

Down Communication has been lost (InBand([Host-Name])) with [Array-Name] ([IP-Address]).

This event is established using luxadm. Monitoring may not be activated for a particular Sun StorEdge 6020 array.

1. Verify luxadm through the command line (luxadm probe, luxadm display).2. Verify cables, GBICs, power, and connections along data path.

3. Check SAN topology GUI to identify failing segment of the data path.4. Verify correct FC switch configuration, if applicable.

interface.loopcard StateChangeEvent-

Error The Sun StorEdge 6020 array has indicated that the loopcard is no longer in an optimal state.

1. Use Telnet to connect to the affected Sun StorEdge 6020 array.2. Verify the loopcard state with fru stat.

3. Verify matching firmware with other loopcards.4. Re-enable the loopcard if possible (enable u(encid)|[1|2]).5. Replace the loopcard if necessary.

interface.loopcard ComponentRemoveEvent

Error The Sun StorEdge 6020 array has reported that a loopcard has been removed from the chassis.

Replace the loopcard within 30 minutes of shutdown.





interface.loopcard.cable

AlarmEvent- Error The Sun StorEdge 6020 array reported that an interface loopcard cable has failed.

1. Use Telnet to connect to the affected Sun StorEdge 6020 array.2. Verify the loopcard state with fru stat.3. Verify matching firmware with other loopcards.4. Re-enable the loopcard, if possible (enable u(encid) [1|2]).5. Replace the loopcard if necessary.6. Verify the connections of the interconnect cables.

log AlarmEvent Warning This event includes all important errors found.

Check the messages file for appropriate action.

oob Comm_LostEvent

System is Down

This is an out-of-band error indicating that the Sun StorEdge 6020 array failed to answer to ping or failed to return its tokens.

This problem can also be caused by a very slow network, or by a lost Ethernet connection to this array.

1. Check power on the array.2. Check Ethernet connectivity to the array.3. Verify that the array is booted correctly.4. Verify correct TCP/IP settings on the array.5. Increase the http and/or ping timeout in Utilities > System > Timeouts. The default timeouts are 10 seconds for a ping and 60 seconds for HTTP (tokens).

power ComponentRemoveEvent

Error The Sun StorEdge 6020 array has reported that a Power Cooling Unit (PCU) has been removed from the chassis.

Replace the PCU within 30 minutes of shutdown.





power StateChangeEvent-

Error The Sun StorEdge 6020 array has reported that a power cooling unit (PCU) has been disabled.Probable causes include:• Internal or external

power loss• Turning off of the

power switch• PCU failures• Battery failures

1. Check the power supply and cables.

2. Check with the onsite system administrator for expected occurrence.

3. Replace the PCU.

4. Replace the battery.

power LogEvent Error Two warnings were found in log file /var/adm/messages.6020, indicating a problem with the Sun StorEdge 6020 array.

Refresh the battery.

power.battery AlarmEvent- Error The state of the batteries in the Sun StorEdge 6020 array is not optimal.

1. Use Telnet to connect to the affected array.2. Run refresh -s to verify the battery state.3. Replace the battery, if necessary.

power.battery.refresh

LogEvent Warning A refresh message was posted to the log file indicating that the batteries are recharging.

Replace the battery.

power.fan AlarmEvent- Error The state of a fan on the Sun StorEdge 6020 array is not optimal.The probable cause is a problem with the power cooling unit (PCU) called out in the event.

1. Use Telnet to connect to the affected array.2. Verify the fan state with fru stat.3. Replace the power cooling unit, if necessary.





power.output AlarmEvent- Error The state of the power in the Sun StorEdge 6020 array power cooling unit (PCU) is not optimal.Probable causes include:• Voltage level on the

power supply and battery have moved out of acceptable thresholds.

• The internal PCU temperature has exceeded acceptable thresholds.

• A PCU fan has failed.

1. Use Telnet to connect to the affected array.2. Verify the PCU state with fru stat.3. Replace the PCU if necessary.

power.replacebattery

LogEvent Warning A message was posted to the log file indicating that the battery warranty period is about to expire, that the battery hold time might be low, or that the battery can no longer hold a charge.

1. Check the Storage Automated Diagnostic Environment for the status of the PCU batteries for this array.2. Use Telnet to connect to the array and run refresh -s to verify the state of the battery.

3. Replace the battery, if necessary.

power_sequencer se2.AlarmEvent- Error The state of the power sequencer on the Sun StorEdge 6020 array changed from On to Off.The power sequencer controls the PDUs in the cabinet.

Contact the onsite system administrator to verify that this is an expected occurrence.

power.temp AlarmEvent- Error The state of the temperature in the Sun StorEdge 6020 array PCU is either too high or is unknown.

1. Use Telnet to connect to the affected array.2. Verify the PCU state with fru stat.3. Replace the PCU if necessary.





system_reboot AlarmEvent Warning This event indicates that the system has rebooted.Probable causes include:• The Sun StorEdge

6020 array experienced a power hit or rebooted.

• A system administrator executed the date command in error.

1. Verify with the system administrator that if a reboot did occur, it was intentional and successful.

2. Use the Storage Automated Diagnostic Environment log viewer to check the device’s mirrored syslog for the date command.

3. Check the Storage Automated Diagnostic Environment for the current status of other monitored devices with similar events.

4. Check the cabinet’s power source to ensure solid connections.





temp_threshold LogEvent Error A message was found in the /var/adm/messages.6020 log file indicating the temperature setting that was exceeded.Probable causes include:• The PCU fans are not

functioning.• Physical placement

of the unit is impeding heat dissipation.

• The component is faulty.

1. Check the physical environment to ensure proper air flow around the array.

2. Check the Storage Automated Diagnostic Environment for the status of the PCU fans for this array.

3. Check the Storage Automated Diagnostic Environment status and compare to the temperature of other components in the unit.

time_diff AlarmEvent Warning The time the Sun StorEdge 6020 array is different from the time set on the host.

Fix the date/time on the Sun StorEdge 6020 array using the date command. Date and time should be the same here as on the monitoring host.





volume StateChangeEvent-

Error The Sun StorEdge 6020 array has reported that a LUN has changed state.

Drive Status Messages:0 Drive mounted

2 Drive present3 Drive is spun up4 Drive is disabled5 Drive has been replaced7 Invalid system area on drive9 Drive not present

D Drive disabled; drive is being reconstructedS Drive substituted

1. Use Telnet to connect to the affected Sun StorEdge 6020 array.2. Check the status of LUNs using vol mode or vol stat from Sun StorEdge 6020 array.3. Check the disk status with fru stat and vol stat.





CHAPTER 8

About the Storage Service Processor

This chapter describes how to troubleshoot the Storage Service Processor component of a Sun StorEdge 6920 system.


■ “About the Storage Service Processor” on page 125

■ “Storage Service Processor Security” on page 126

■ “Storage Service Processor Accessory Tray” on page 126

■ “Configuration Possibilities” on page 127

About the Storage Service ProcessorThe Storage Service Processor supports health monitoring and fault mitigation independent of the customer’s server. The Storage Service Processor comes with a 16-Mbyte, hot-swappable universal serial bus (USB) flash disk. The USB flash disk provides a place to store and easily retrieve files about the Sun StorEdge 6920 system configuration. The data can easily be restored in the event of a hardware failure.

Every Storage Service Processor is configured with the same hardware and software components to ensure ease of replacement. All Storage Service Processors support Sun StorEdge Remote Response.

The customer management connection is a dedicated Ethernet cable that connects to the Storage Service Processor. Each Storage Service Processor serves as the master for collecting data from its Sun StorEdge 6920 system. This connection is also referred to as the site LAN. If more than one Sun StorEdge 6920 system is connected to the customer management connection, alert traffic is passed across the LAN.

125


Storage Service Processor SecuritySecurity for the Storage Service Processor is provided by:

■ The aggregation of Storage Service Processors■ The security module■ The secure socket layer (SSL)

The SSL is located between the site LAN connection and a Storage Service Processor using the Storage Automated Diagnostic Environment software.

The Sun StorEdge Remote Response service provides remote monitoring and diagnostics serviceability. Through the use of security software installed on the Storage Service Processor, Sun uses the secure shell (ssh(1)) command for the connection between the dial-up line and the Storage Service Processor, which adds encryption and authentication.

Note – For security purposes, inbound telnet(1) and ftp(1) connections to the Storage Service Processor have been disabled.

Storage Service Processor Accessory Tray The Storage Service Processor accessory tray, mounted directly below the Storage Service Processor, is a sheet metal tray that contains the following:

■ Serial network terminal concentrator (NTC) used for remote serviceability support

■ Ethernet router (firewall) used to provide additional security to Sun from the site LAN

■ Personal Computer Memory Card International Association (PCMCIA)-compatible modem

■ AC power supply used by all components in the tray

■ USB relay is connected to the Storage Service Processor and provides the lights-out power management

The Storage Service Processor accessory tray is a field-replaceable unit.



Configuration PossibilitiesThere are several configuration options for the Sun StorEdge 6920 system:

■ Standalone with no remote service – A standalone Sun StorEdge 6920 system can be configured with no remote service. With this configuration, the Storage Service Processor must be configured as a master service processor.

■ Remote service to a single unit – Remote service to a single unit is accomplished when Sun StorEdge 6920 alerts are sent to remote hosts for notification through the site LAN.

Note – For security reasons, inbound telnet(1) and ftp(1) connections to the Storage Service Processor have been disabled.

■ Remote service to multiple units – Remote service to multiple units is accomplished by aggregating information on multiple Storage Service Processors and the transmission of that information to a single host through a single site LAN. The Storage Automated Diagnostic Environment remotely services the multiple units for which alert information has been aggregated.

Chapter 8 About the Storage Service Processor 127




CHAPTER 9

Replacing the DSP and DSP FRUs

This chapter describes how to replace the entire DSP and how to replace individual DSP FRUs. It includes the following sections:


■ “Removing and Replacing the Management Interface Card” on page 130

■ “Removing and Replacing the Switch Fabric Card” on page 133

■ “Removing and Replacing the Storage I/O Card” on page 135

■ “Removing and Replacing the Storage Resource Card” on page 137

■ “Removing and Replacing GBICs” on page 141

■ “Removing and Replacing the Power Supply” on page 142

■ “Removing and Replacing the Fan Assembly” on page 144

■ “Installing Additional Storage I/O and Storage Resource Cards” on page 145

■ “Removing and Replacing the DSP Chassis and Midplane” on page 149

Before You BeginBefore performing any of the procedures in this chapter, be sure to do the following:

■ Reserve the cabinet as described in “Reserving the Cabinet for Maintenance” on page 34

■ Follow the safety precautions described in “Maintenance Precautions” on page 34

129


Removing and Replacing the Management Interface CardFollow these steps to remove and replace a management interface card (MIC).

1. Select the MIC that you are replacing.

2. Check the LEDs on the MIC to determine whether the card is in a faulted state.

If it is not in any of the following states, it is faulted.

■ If the Ready LED is blinking green and the Power LED is solid green, the card is booting.

■ If the Ready LED is solid green and the Power LED is solid green, the card is in normal operation.

■ If the link (10/100 Ethernet) LED is on green, the link is connected.

■ If the Act 1 LED is green, the MICPC card is inserted.

3. Verify that the MIC is ready to remove by clicking on dsp00 - MIC.Front3 in the online version of these instructions.

The Show Chassis state should be Fault or Powered Off.

4. Remove the Ethernet and serial port cables.

5. Loosen the one captive screws from each side of the MIC faceplate.

You may need a Phillips screw driver to loosen the screw.



6. Pull the lock and ejector handles outward completely to release the card from the mid-plane chassis (FIGURE 9-1).

FIGURE 9-1 Releasing a MIC From the DSP

7. Slide the card out of its slot until it is completely removed from the chassis.

To maintain proper cooling, do not leave the card slot empty for an extended length of time.

8. Remove the PCMIC from the MIC.

You will install it in the new MIC.

9. Place the removed MIC in an antistatic bag.

Chapter 9 Replacing the DSP and DSP FRUs 131


10. Making sure that the lock and ejector handles are completely open, slide the new card into the slot until it connects with the chassis mid-plane.

Use the alignment pins located on the edge of the card to align it with the guide holes in the chassis.

11. Push in the lock and ejector handles to secure the MIC in place.

12. Ensure that the card face is flush with the adjoining cards in the chassis.

If it is not flush, remove and reseat the card.

13. Secure the card by tightening the captive screws on the card faceplate.

The Power LED and Ready LED should now be green.

14. Insert the PCMIC into slot one (lower slot) in the new MIC.

The Act LED to the left of the ejector button should now be green.

15. Insert the Ethernet and serial port cables.

16. Close the service panel and tighten the three captive fasteners.

17. Clear the MIC failover flag by clicking Clear Failover Flag in the online version of these instructions.

a. From Select Device options, select the corresponding DSP link.

b. From the Select Command list, select the redund -c command.

c. Click Run Command.

A message indicates when the flag is cleared.

18. Verify that the MIC is Normal by clicking on dsp00 - MIC.Front3 in the online version of these instructions.

The Show Chassis state should be Normal or Standing By.

19. Create new inventory:

a. Click Service > Sun Solution Series.

b. At the bottom of the Inventory Maintenance page, click Generate New Inventory.

c. Click Save New Inventory.



20. Check the revision level of the new card to confirm compatibility by clicking array00 - u1ctr in the online version of these instructions.

a. Select the Update Revisions link from the Revision Maintenance Menu.

b. Click Create New Patch Report at the bottom of the page.

c. Select and apply any patches as required.

Removing and Replacing the Switch Fabric CardFollow these steps to remove and replace the switch fabric card (SFC).

1. Select the card you want to replace.

2. Check the LEDs to determine whether the card is in a faulted state; if it is not in any of the following states, it is faulted.



3. Verify that the SFC is ready to remove by clicking on dsp00 - SFC.Front3 in the online version of these instructions.


4. Loosen the one captive screw from the left side of the SFC faceplate.





FIGURE 9-2 Releasing the SFC From the DSP



7. Place the removed SFC in an antistatic bag.



9. Push in the lock and ejector handles to secure the SFC in place.





11. Secure the card by tightening the captive screw on the card faceplate.


The card may take up to 10 minutes to become ready for the system.

12. Verify that the SFC is Normal by clicking on dsp00 - SFC.Front3 in the online version of these instructions.

The Show Chassis state should be Normal or Standing By.



b. At the bottom of Inventory Maintenance page, click Generate New Inventory.






Removing and Replacing the Storage I/O CardFollow these steps to remove and replace the storage I/O (SIO) card.

Note – The SIO card and storage resource card (SRC) must be replaced as a pair. After replacing the SIO card, you must replace the corresponding SRC.


2. At the back of the cabinet, unscrew the three captive fasteners on the right side of the service panel and then open the panel.

3. Check the LEDs to determine whether the card is in an active state:

■ If the Link LED is solid green, the link is connected. If it is not lit or is blinking, there is no activity on the link.



■ If the Act LED is solid amber or blinking amber, there is activity on the link. If it is not lit, there is no activity on the link.

4. Stop all host activity to the SIO card.

5. Verify that the SIO card is ready to remove by clicking on dsp00 - SIO.Front3 in the online version of these instructions.


6. From the back of the cabinet, remove all of the fiberoptic cables from the SIO card.

Make sure to label all cables and their port locations.

7. Loosen the two captive screws, one on each side of the SIO card faceplate.



FIGURE 9-3 Releasing a SIO Card From the DSP





10. Remove the GBICs from the SIO card; if you need help, refer to “Removing and Replacing GBICs” on page 141.

11. Place the removed SIO card in an antistatic bag.



13. Push in the lock and ejector handles to secure the SIO in place.




16. Insert the GBICs into the correct ports of the new SIO card; if you need help, refer “Removing and Replacing GBICs” on page 141.

17. Insert the fibre cables into the correct port.

The SIO card boots only after the corresponding SRC has been replaced. The Link LED will be green for all connected ports.

18. Replace the corresponding SRC as described in the next section, “Removing and Replacing the Storage Resource Card” on page 137.

Removing and Replacing the Storage Resource CardFollow these steps to remove and replace the storage resource card (SRC).

Note – The SIO card and SRC must be replaced as a pair. You must replace the SIO card before replacing the corresponding SRC.




2. Check the LEDs to determine whether the card is in a faulted state; if it is not in either of the following states, it is faulted.



3. Verify that the SRC is ready to remove by clicking on dsp00 - SRC.Front3 in the online version of these instructions.

4. Loosen the one captive screw from the left side of the SRC faceplate.


If Then

The Show Chassis state is Fault or Powered Off, or if the SRC is faulted, but the SIO card is not faulted.

First replace the SIO card, then continue on to step 4 in this procedure to replace the SRC.

You’ve received an alert from Event Advisor telling you to check the SRC, but neither the SRC nor the SIO card is in the Fault or Powered Off state.

Call your Sun Service provider to assist with this service action.




FIGURE 9-4 Releasing an SRC From the DSP



7. Place the removed SRC in an antistatic bag.



9. Push in the lock and ejector handles to secure the SRC in place.





The card may take up to 10 minutes to become ready for the system. The corresponding SIO card boots with the SRC. The link LEDs on the SIO card should be on for all connected ports.



12. Verify that both the SIO card and the SRC are Normal by clicking on dsp00 - SRC.Front3 in the online version of these instructions.

The Show Chassis state should be Normal.



b. At the bottom of Inventory Maintenance page, click Generate New Inventory.






15. Using a host-based utility, verify that the StorEdge 6920 volumes are available to the host.



Removing and Replacing GBICsFollow these steps to remove and replace the GBICs.

1. From the back of the cabinet, unscrew the three captive fasteners on the right side of the service panel and swing the panel open.

2. Label the fiberoptic cable and its port location, then disconnect the fiberoptic cable from the GBIC.

3. Remove the GBIC as follows (FIGURE 9-5):

a. Note the GBIC’s orientation.

b. Hold the GBIC and squeeze the latches together on both sides.

c. While squeezing the latches, pull the GBIC to remove it from the SIO card, (FIGURE 9-5).

If you have difficulty removing the GBIC, try gently rocking it side-to-side as you pull.

The spring-loaded door of the SIO card will close the port opening when the GBIC is removed.

FIGURE 9-5 Removing a GBIC



4. Insert the new GBIC into the port of the SIO card using the correct orientation.

The GBIC clicks and latches when inserted correctly.

5. Insert the fiberoptic cable into the port.

The Link LED should now be green.


Removing and Replacing the Power SupplyFollow these steps to remove and replace a power supply.

1. At the back of the cabinet, unscrew the three captive fasteners on the right side of the service panel and swing the panel open.

2. Check the power supply LED (Green DC OK - On or Off) to determine whether it is still receiving power.

3. Verify that the power supply is ready for removal by clicking on Verify power supply in the online version of these instructions.

■ The Show Chassis state should be Failed/Absent.

Note – If the power supply is not Failed/Absent, call your Sun Service provider to assist with this service action.

4. Remove the power cable from the failed power supply.

Note – The power cable must be removed before the handle can be lowered.

5. Loosen the two captive screws located on the front of the power supply.

You may need a Phillips screw driver to loosen the screws.

6. Pull the power supply latch handle down to disengage it from the chassis.

7. Slide the power supply out of its slot until it is completely removed from the chassis.

8. Insert the new power supply until the latch handle touches the chassis.



9. Push the latch handle up to engage and lock the latch handle (FIGURE 9-6).

FIGURE 9-6 Installing the New Power Supply

10. Secure the power supply by fastening the two captive screws.

11. Insert the power cord into the power supply connector.

The DC OK LED will now be green.


13. Verify that the power supply is Ready/Normal by clicking on Verify power supply in the online version of these instructions.

The Show Chassis state should be On.



Removing and Replacing the Fan AssemblyFollow these instructions to remove and replace the fan assembly.

1. At the front of the cabinet, check the fan tray assembly LEDS to determine whether the fan is in a failed state.

2. Verify that the fan tray assembly is ready to remove by clicking on Verify fan tray assembly in the online version of these instructions.

The Show Chassis state should be Failed.

3. Using a small Phillips screwdriver, loosen the captive screw holding the fan tray assembly in place.

4. Remove the fans assembly as follows (FIGURE 9-7):

a. Hold the handle on the front of the fan tray assembly and pull it partially out of the chassis.

b. Verify that both fans have stopped rotating, and remove the assembly completely from the chassis.

Caution – The fans continue to rotate; be careful not to place your fingers into the fan tray assembly.

If Then

The fan power LED (green) is On and the fan attention LED (amber) is Off.

The fan has power and is operating normally.

The fan power LED (green) is On and the fan attention LED (amber) is On

There is a failure of one or both fan units.

If the fan power LED (green) is Off and the fan attention LED (amber) is Off.

Either no power is applied to the unit, or power has failed.



FIGURE 9-7 Loosening and Removing the Fan Tray Assembly

Do not leave the removed fan tray assembly out of the chassis for an extended period of time.

5. Insert the new fan tray assembly until it connects with the mid-plane chassis.

6. Secure the fan tray assembly by tightening the captive screw.

The Fan Power LED indicator should now be green.

7. Verify that the fan tray state is On by clicking on Verify fan tray assembly in the online version of these instructions.

The Show Chassis state should be On.

Installing Additional Storage I/O and Storage Resource CardsWhen you add SIO card/SRC pairs to the DSP, you must first install the SIO card and then install the corresponding SRC. Follow these instructions to install the SIO card and then the SRC.



1. Verify that the DSP is in a known good state by clicking on Verify DSP FRUs in the online version of these instructions.

The Show Chassis state should show the FRUs as ON, Normal or Standing By.

2. At the back of the cabinet, locate the SIO filler card slots (1 and 2) and loosen the captive screws, one on each side of the faceplate.

3. Pull the lock and ejector handles outward completely to release the filler card from the mid-plane chassis.

4. Slide the filler card out of its slot until it is completely removed from the chassis.


5. Making sure that the lock and ejector handles are completely open, slide the new SIO card into the slot until it connects with the chassis mid-plane, (FIGURE 9-8).


FIGURE 9-8 Installing the SIO Card in the DSP



6. Push in the lock and ejector handles to secure the SIO card.

The card faceplate should be flush with the adjoining cards in the chassis. If it is not, remove and reseat the card.


8. Insert the GBICs into the correct ports of the new SIO card.

For instructions, refer to “Removing and Replacing GBICs” on page 141 and note note the following port information:

■ Port locations go from right (1) to left (8).

■ Ports 1 through 4 are assigned to host connections, and ports 5 through 8 are assigned to storage connections.

■ Storage ports 8, 7, 6, and 5 are populated in that order: on cards in slots 3 and 4. If there are more than 8 controller pairs (14 maximum) then ports 4, 3, 2, and 1 are populated in that order: on the cards in slots 1 and 2, and ports 4 and 3 are populated on cards 3 and 4.

■ Storage connections are assigned to card slot locations 1 and 3, and alternate storage connections are assigned to card slot connections 2 and 4.

9. Insert the fiberoptic cables into the GBICs.

10. Loosen the SRC filler card's one captive screw from the left side of the faceplate, (FIGURE 9-4).


11. Pull the lock and ejector handles outward completely to release the filler card from the mid-plane chassis.

12. Slide the filler card out of its slot until it is completely removed from the chassis.


13. Making sure that the lock and ejector handles are completely open, slide the new SRC into the slot until it connects with the chassis mid-plane, (FIGURE 9-9).

Use the alignment pins located on the edge of the card to align the card with the guide holes in the chassis.



FIGURE 9-9 Installing the SRC

14. Push in the lock and ejector handles to secure the SRC in place.

The card face should be flush with the adjoining cards in the chassis. If it is not, remove and reseat the card.


The card may take up to 10 minutes to become ready for the system.

The Power LED and Ready LED should now be green for both SRC and SIO cards.

16. From the back, verify that the SIO card Link LEDs are green for all active ports on both cards.

17. Verify that both the SIO card and the SRC are Normal by clicking on dsp00 - SRC.Front3 in the online version of these instructions.

The Show Chassis state should be Normal.



Removing and Replacing the DSP Chassis and Midplane

Note – This procedure requires two people; the DSP can weigh up to 100 pounds when fully populated.

Replacing the DSP requires several separate procedures. Obtain the ID of the new chassis, then follow the instructions in each of these sections:

■ “To Remove the DSP Chassis” on page 149

■ “Moving the FRUs to the New DSP Chassis” on page 152

■ “To Install the New Chassis” on page 154

■ “To Recable the Chassis” on page 154

■ “To Update the Chassis License and Verify the Configuration” on page 155

■ “To Generate a New Inventory” on page 156

Note – To access the instructions for this procedure in the Storage Automated Diagnostic Environment, you must supply the password: arrayservice.

▼ To Remove the DSP Chassis1. Stop I/O to the subsystems from all hosts.

2. Establish a serial connection to the NTC by entering the following:

3. At the NTC prompt, execute the following command; and press Return

tip -9600 /dev/ttya or /dev/ttyblogin: rsspassword: sun1rss

ntc0: connect local port_3Local protocol emulation 1.0 - Local Switch: <^[>



4. Log in to the DSP:

5. At the DSP prompt, execute the following commands to verify the state of the DSP, and make sure to note all of the configuration information.

6. To prevent possible corruption of the PCMIC cards, execute the following command from the DSP prompt to remove the PCMIC card from the master MIC.

7. At the back of the cabinet, unscrew the three captive fasteners on the right side of the service panel and open the panel.

8. Depress the ejection button to the left of the PCMIC card to activate the card release.

The PCMIC card is located in the right side of the MIC.The ACT LED will be unlit on the unmounted card.

9. Slide the card out of its slot until it is completely removed from the MIC.

Mark the PCMIC card to identify from which MIC slot it was removed.

10. To remove the PCMIC card from the slave MIC, execute CTRL+[ key sequence at the DSP prompt:

11. From the ntc0: prompt, execute the following command:

Username: rootPassword: sun1

dsp00# show chassisdsp00# show disksdsp00# show volumesdsp00# show fc-servers

dsp00# pumount a:

Drive ‘A’: successfully unmountedOK to remove PC card from socket.

dsp00# ^[

ntc0: disconnect all



12. From the ntc0: prompt, execute the following commands:

13. Press Enter to connect to the MIC SLV-!> prompt.

14. At the MIC SLV-!> prompt, execute the following commands:

15. At the MIC SLV-!> prompt, execute the following commands:

16. Depress the ejection button to the left of the PCMIC card to activate the card release.

The ACT LED will be unlit on the unmounted card.

17. Slide the card out of its slot until it is completely removed from the MIC.

Mark the PCMIC card to identify from which slot it was removed.

18. Return to the DSP by executing the following commands:

19. Press Enter.

20. From the back of the cabinet, remove the power cords from both of the power supplies.

21. Remove the following cables, and make sure that they are all labeled:

■ Ethernet cables from the MICs

■ Console cables from the MICs

■ Fibre cables from the SIO cards

ntc0: connect local port_4ntc0: ^d

MIC SLV-!> .MIC SLV-!> m

MIC SLV-!> pumount a

Drive ‘A’ successfully unmountedOK to remove PC Card from socket.

MIC SLV-!> ^[ ntc0: disconnect allntc0: Connect local port_3

Local protocol emulation 1.0 - Local Switch <\B>



22. Remove the four screws (two per rail) that hold the DSP rails to the cabinet frame.

23. From the front of the cabinet, remove the four trim strips on both sides of the DSP.

24. Remove the filler panel below the DSP to provide proper access for removing the DSP.

25. Remove the eight screws (four per side) holding the DSP chassis to the cabinet frame.

26. Use two people to slide the DSP chassis out of the cabinet.

Caution – Use care. The chassis is heavy.

After the chassis has been removed, you must move the FRUs to the new chassis.

Moving the FRUs to the New DSP ChassisThis section describes how to move each FRU to the new DSP chassis. You must move:

■ All cards (MIC, SIO, SFC, and SRC) and blank cards

■ Power supplies

■ Fan tray assembly

■ Chassis side rails

▼ To Move the Cards

You remove all cards and blank cards in the same fashion.

1. From the back of the old chassis, loosen the card's captive screws, one on each side of the faceplate.


2. Pull the lock and ejector handles outward completely to release the card from the mid-plane chassis.


4. Making sure that the lock and ejector handles are completely open, slide the card into the slot in the new chassis until it connects with the chassis mid-plane.

Use the alignment pins located on the edge of the card to align the card with the guide holes in the chassis.



5. Push in the lock and ejector handles to secure the card in place.

The card faceplate should be flush with the adjoining cards in the chassis. If it is not, remove and reseat the card.


7. For MICs only, insert the corresponding removed PCMIC card into slot one (lower slot) until it is completely inserted.

If the PCMIC does not fit correctly, do not force it into the slot. Instead, remove and reinsert it.

The adjacent ejection button will set itself in an outward position when the PCMIC is properly inserted.

▼ To Move the Power Supplies

1. From the back of the old chassis, loosen the two captive screws located on the front of the power supply.

You may need a Phillips screw driver to loosen the screws.

2. Pull the power supply latch handle down to disengage the power supply from the chassis.

3. Slide the power supply out until it is completely removed from the chassis.

4. Insert the power supply into the new chassis until the latch handle touches the chassis.

5. Push the latch handle up to engage and lock the latch handle.

6. Secure the power supply by tightening the captive screws on the front of the power supply.

▼ To Move the Fan Tray Assembly

1. Using a small Phillips screw driver, loosen the captive screw holding the fan tray assembly in place in the old chassis.

2. Hold the handle on the front of the fan tray assembly, and pull the assembly partially out of its slot.

3. Verify that both fans have stopped rotating, then remove the assembly completely.

Caution – If the fans are still rotating, be careful not to place your fingers into the fan tray assembly.



4. Insert the fan tray assembly into the new enclosure until it connects with the mid-plane chassis.

5. Secure the fan tray assembly by tightening the captive screw.

▼ To Move the Chassis Side Rails

1. Remove the 24 screws (12 per side rail) the hold the two side rails to the old chassis.

2. Using the 24 screws, attach the two side rails to the new chassis.

▼ To Install the New Chassis1. Using two people, align the chassis rails with the rails inside the cabinet and slide

the chassis into the front of the cabinet.

2. Replace the eight screws that secure the front of the DSP chassis to the cabinet frame.

3. Replace the filler panel below the DSP.

4. Replace the four trim strips on both sides of the DSP.

5. At the back of the cabinet, replace the four rail screws to secure the chassis to the cabinet frame.

▼ To Recable the Chassis1. Replace the following cables:

a. Insert the Ethernet cables into the MICs.

b. Insert the console cables into the MICs.

c. Insert the fiberoptic cables into the SIO cards.

d. Replace all wire ties.

2. Insert the power cables in the power supplies to return power to the DSP.

The DSP may take up to 10 minutes to reboot.




▼ To Update the Chassis License and Verify the Configuration

1. Re-establish a serial connection to the NTC by entering the following:

2. At the NTC prompt, execute the following command, and press Return:

3. Log in to the DSP:

4. Update the new chassis license as follows:

5. Exit config mode and retrun to the dsp00# prompt by entering the following:

6. At the DSP prompt, execute the following commands to verify the state and configuration of the DSP:

tip -9600 /dev/ttya or /dev/ttyblogin: rsspassword: sun1rss

ntc0: connect local port_3Local protocol emulation 1.0 - Local Switch: <^[>

Username: rootPassword: sun1

dsp00# configdsp00(config)# license-CHASSIS< chassis ID>For example:dsp00(config)# license-CHASSIS 0246ab-d3c36a-f5n501-06f883-8362y4-6947

dsp00(config)# end

dsp00# show chassisdsp00# show disksdsp00# show volumesdsp00# show fc-servers



▼ To Generate a New Inventory1. At the bottom of the Inventory Maintenance page, click Generate New Inventory.

2. After the new inventory has been generated, click Save New Inventory at the bottom of the page.



CHAPTER 10

Replacing Array FRUs

This chapter provides procedures for removing and replacing and entire array, and for removing and replacing array FRUs. It includes the following sections:


■ “Removing and Replacing an Entire Array” on page 158

■ “Installing and Configuring Additional 2X2 Storage Arrays” on page 174

■ “Removing and Replacing an Array Disk Drive” on page 177

■ “Removing and Replacing an Array Controller Card” on page 181

■ “Removing and Replacing an Array Loop Card” on page 184

■ “Removing and Replacing an Array Power and Cooling Unit” on page 186

■ “Removing and Replacing the Battery in the Array Power and Cooling Unit” on page 190

■ “Adding Array Capacity” on page 192

■ “Removing Array Capacity” on page 194




157


Removing and Replacing an Entire ArrayReplacing an Array requires several separate procedures; follow the instructions in each of these sections:

■ “To Remove the Array Chassis” on page 158

■ “Moving the FRUs to the New Array Chassis” on page 163

■ “Installing the New Array Chassis” on page 170

■ “Configuring the Array” on page 173

Note – Removing and replacing the tray chassis from the cabinet requires two people as the chassis can weigh up to 90 Lbs when it is fully populated.


▼ To Remove the Array Chassis1. Make sure the customer has taken steps to back up and secure the data that is on

the tray you are replacing, including deleting data from the array itself.

2. Stop I/O to the array from all hosts.

3. Establish a serial connections to the NTC as follows:

tip -9600/dev/ttya or dev/ttyblogin: rssPassword: sun1rss



4. At the ntc0: prompt, enter the following command and login into the service processor.

5. At the sp0 console login port, login as follows:

6. From the SP prompt, Telnet to the array you are going to move, for example:

7. At the login prompt, login as shown:

8. At the array prompt, execute the following commands to verify the state of the array and make sure to note all of the FRU and configuration information.

ntc0: connect local port_2Local protocol emulation 1.0 - Local Switch <^[>

Press Return

The following message appears:

This system is for the use of authorized users only. Individuals using this computer system without authority, or in excess of their authority, are subject to having all of their activities on this system monitored and recorded by system personnel. In the course of monitoring individuals improperly using this system, or in the course of system maintenance, the activities of authorized users may also be monitored. Anyone using this system expressly consents to such monitoring and is advised that if such monitoring reveals possible evidence of criminal activity, system personnel may provide the evidence of such monitoring to law enforcement officials.

sp0 console login: rootPassword: !root

sp0# telnet array00

Login: rootPassword: sun1

array00:/:<1>fru statarray00:/:<2>vol listarray00:/:<3>vol stat

Chapter 10 Replacing Array FRUs 159


9. At the array prompt, issue the following command to shutdown the array.

10. Enter y.

The shutdown only spins down the disk drives and powers off the controller cards.

11. From the back of the cabinet, on the tray chassis you are removing, press the power switches on the power and cooling units to the Off (-) position.

12. For the any other trays that are a part of the array chassis you are removing, press the power switches on the power and cooling units to the Off (-) position.

13. Disconnect the power cables from each power and cooling unit in the tray chassis you are replacing.

14. Disconnect the power cables from each power and cooling unit in the other trays that are part of the array you are replacing.

15. Disconnect and remove the two loop/interconnect card cables, making note of their locations.

16. Disconnect the Ethernet cable if the tray has a controller card installed.

17. Remove the Ethernet and fiberoptic cables from the cable clips on the power and cooling units.

array00:/:<1>shutdown

Shut down the system, are you sure? [N]:



18. Remove the four screws that secure the tray chassis side rails to the cabinet frame (FIGURE 10-1.)

FIGURE 10-1 Removing the Chassis Tray Screws

19. From the front of the cabinet, remove the trim strips from each side of the tray enclosure.



20. Remove the four screws that attach the tray enclosure to the cabinet frame (FIGURE 10-2).

FIGURE 10-2 Removing the Four Front Screws That Secure the Tray to the Cabinet

21. Using two service engineers, slowly push the tray enclosure from the back of the cabinet.

The second person must be present to guide the tray enclosure from the front.



Moving the FRUs to the New Array ChassisYou need to move the following FRUs:

■ Disk Drive, see “To Move the Disk Drives” on page 163

■ Interconnect Cards, see “To Move the Interconnect Cards” on page 165

■ Controller Card (if necessary), see “To Move the Controller Card” on page 166

■ Power and Cooling Units, see “To Move the Power and Cooling Units” on page 168

■ Tray Side Rails, see “To Move the Tray Side Rails” on page 170

▼ To Move the Disk Drives

1. For each disk drive, push down on the disk drive latch release to open the drive latch handle (FIGURE 10-3).

FIGURE 10-3 Disk Drive Removal

2. Use the latch handle to pull the disk drive straight out of the enclosure.



3. As you remove each disk drive, immediately label it with its slot location in the tray so that you can replace it in the correct slot.

Disk drives are numbered from 1 to 14, starting from the left side of the tray (FIGURE 10-4).

FIGURE 10-4 Disk Drive Numbering

Note – If you install disks drives into the wrong slots, the data can be lost.

4. Install the disk drives into the new enclosure:

a. Gently insert each disk drive onto the middle of the rails and push it in until it is seated in the midplane connector.

b. Push in on the drive handle to firmly secure the drive.

The handle clicks into place when the drive is fully inserted.



▼ To Move the Interconnect Cards

1. Loosen the Phillips retaining screw to unlock the latch handle (FIGURE 10-5).

FIGURE 10-5 Location of Screws on Interconnect Cards

2. Pull the latch handle to release the interconnect card from the connector and remove it from the array (FIGURE 10-6).

Caution – The latch handle on the interconnect card is operated by a gear at the base of the card. To avoid injury, keep your fingers away from this gear when removing the card and opening or closing the latch handle.

Phillips Retaining Screw



FIGURE 10-6 Removing the Interconnect Card

3. Insert the interconnect card all the way into the new chassis.

4. Lock the new interconnect card in place by pushing in on the latch handle.

5. Tighten the retaining screw.

▼ To Move the Controller Card

1. Loosen the Phillips retaining screws to unlock the latch handles (FIGURE 10-7).

When you are facing the back of the tray, the controller card is located in the middle of the tray.



FIGURE 10-7 Controller Card Location

2. Pull the latch handles to release the controller card from the connector and remove it from the array (FIGURE 10-8).

FIGURE 10-8 Removing the Controller Card

Controller Card



3. Insert the controller card all the way into the new enclosure.

4. Lock the new controller card in place by pushing in on the latch handles.

5. Tighten the retaining screws.

▼ To Move the Power and Cooling Units

1. Loosen the Phillips retainer screw to unlock the power and cooling unit latch handle.

Note that when facing the back of the tray, Power and Cooling unit number one is located on the left and Power and Cooling unit two is located on the right (FIGURE 10-9).

FIGURE 10-9 Location of Power and Cooling Units

1 2



2. Pull up on the latch handle to release the Power and Cooling unit from its connector, then pull the unit straight out of the tray (FIGURE 10-10).

FIGURE 10-10 Removing the Power and Cooling Unit

3. Insert the Power and Cooling unit into the new enclosure until the latch handle touches the chassis.

Push the latch handle down to lock the Power and Cooling unit into place.

4. Tighten the retaining screw.



▼ To Move the Tray Side Rails

1. Remove the eight screws that hold the two side rails to the enclosure.

2. Use the eight screws to attach the two side rails to the new enclosure.

Installing the New Array ChassisInstall the new array chassis as follows;

3. From the front of the cabinet, align the tray rails with the rails inside the cabinet and push the tray into the cabinet (FIGURE 10-11).

FIGURE 10-11 Aligning the Tray and Cabinet Rails to Insert the New Tray



4. Install the four screws that secure the tray to the front of the cabinet frame (FIGURE 10-12).

FIGURE 10-12 Inserting the New Tray and Securing it to the Cabinet With the Four Screws

5. Attach the trim strips to the cabinet frame.



6. Insert the four screws that secure the tray to the side rails in to the back of the cabinet (FIGURE 10-13).

FIGURE 10-13 Securing the Tray Rails to the Back of the Cabinet With the Four Screws

7. Insert the two interconnect card cables into their proper locations.

8. Insert the Ethernet cable in the controller card if one is present.

9. Insert the fiberoptic cable in the controller card if one is present.

10. Make sure the Power switches are in the Off (-) position, then insert the Power and Cooling unit cables for all trays in the new array.

Turn on the power switches for the Power and Cooling units for all trays in the array.



11. Follow the steps in “To Configure a New Array” on page 176 to configure this new array.

Configuring the ArrayFollow these instruction for configured the newly-replaced array.

1. Establish a serial connections to the NTC as follows:



4. From the SP prompt, Telnet to the array you are going to move, for example:



Press Return




sp0# telnet array00



5. At the login prompt, login as shown:

6. At the array prompt, execute the following commands to verify the state of the array and make sure to note all of the FRU and configuration information.





Installing and Configuring Additional 2X2 Storage ArraysFollow the steps in these procedures to add and configure an additional 2X2 storage array:

■ “To Add a Storage Array” on page 174

■ “To Configure a New Array” on page 176

▼ To Add a Storage Array

Note – This procedure assumes two service engineers are available to lift the tray.

1. Remove the tray from the shipping container.

2. Attach the side rails to the tray using the eight screws.

Login: rootPassword: sun1

array00:/:<1>fru statarray00:/:<2>vol listarray00:/:<3>vol stat



3. From the front of the cabinet, remove the appropriate number of filler panels to accommodate the new tray.

4. Align the tray rails with the rails inside the cabinet and push the tray into the cabinet (FIGURE 10-11).

5. Install the four screws that secure the tray to the front of the cabinet frame (FIGURE 10-12).

6. Attach the trim strips to the cabinet frame.

7. Insert the four screws that secure the tray to the side rails in the back of the cabinet (FIGURE 10-13).

8. Using the right side connector of the loop card on the bottom tray and the left side connector of the loop card on the upper tray, connect the two loop card interconnect cables between the two trays. (FIGURE 10-14).

FIGURE 10-14 Interconnect Card Cable Locations.

9. Route the Ethernet cable through the keepers.

10. Insert the Ethernet cable in the controller card.

11. Insert the fiber optic cables in the controller card

12. Follow the instruction in the next section for configure the array.



▼ To Configure a New Array 1. Log into the Storage Automated Diagnostic Environment as Storage or Admin.

Note – You must log into the Storage Automated Diagnostic Environment as either Storage or Admin to configure the arrays.

2. Click Service > Sun Solutions Series, then click Ethers.

The system displays the Update Ethers page, which lists the names and corresponding IP addresses of all standard and optional components that can comprise the StorEdge 6920 system.

3. Enter the MAC address of the array in the appropriate MAC address field on the Update ethers page.

MAC addresses are located on a sticker on the back panel of each array.

4. Click update ethers.

When you click update ethers, the systems run a script that associates the MAC address of the array with the corresponding IP address to identify the array to the system. The system also updates the /etc/ethers file.

5. Make sure the power switch is on the Off position, and insert the power and cooling unit cables for both trays.

Note – The power switch must be in the Off position before you attach the power and cooling unit cables.

6. Power cycle the new array:

To power cycle an individual array, toggle both power switches on the back panel of the array to the off position. After approximately 30 seconds have passed, toggle both power switches to the on position to turn the power to the array back on.

Note – Allow 3 to 5 minutes for the array to complete the boot cycle.

7. Reboot the array once again to reset the array configuration information:

a. Click on Reset array configuration information in the online version of these instructions.

b. Select the name of the new array from the drop down box (for example, array01).



c. In the password box, either enter the last known password, or leave the box empty if the array does not have a password.

d. Monitor the boot process from the pop-up screen until the Boot Operation Status reports Done and that the array is available.

This takes 3 to 5 minutes.





9. Check the revision level of the new card to confirm compatibility by clicking Verify Revision Maintenance in the online version of these instructions.




10. Verify the status of the new trays by clicking on Verify Trays in the online version of this procedure.

The FRU Stat Status-State should now be Ready-Enabled for all FRUs.

11. Create a new Topology Snapshot for the new array by clicking Create New Topology Snapshot in the online version of these instructions, then selecting Create Topology from the left side of the page.

12. Verify that the new array has been added to the topology by clicking View the New Topology Snapshot link in the online version of these instructions.

Removing and Replacing an Array Disk DriveFollow these steps to remove and replace and array disk drive.

1. If you have already selected the disk drive you want to replace, go to step 2 or return to the previous screen to select another disk drive.

If you need help locating the correct tray, activate the blinking white locator LED by selecting Set tray locator in the online version of these instructions.



2. If you need help locating the correct try, activate the blinking white locator LED by clicking on Set tray locator in the online version of these instructions.

3. Locate the disk drive with the blue LED on, indicating a ready to remove state.

If the blue LED is not on, proceed to step 4 regardless. Note that disk drives are numbered from 1 to 14, starting from the left side of the tray (FIGURE 10-15).

FIGURE 10-15 Disk Drive Location.

4. Verify that the disk drive is ready to remove by clicking on array00 - u1d1 in the online version of these instructions.

■ The FRU Stat, Status -State should be either fault-Disabled or Fault-Substituted.

■ The Vol Stat should be Substituted.

■ The Proc List should show no volume reconstruction activity.

Note – If the disk drive is not Disabled or Substituted, call your Sun Service provider to assist with this service action.



5. If the disk drive is ready for removal, push down on the latch release to open the drive latch handle (FIGURE 10-16).

FIGURE 10-16 Disk Drive Latch Release

6. Use the latch handle to slowly pull out the disk drive about one inch.

7. Wait 30 seconds (giving the disk drive time to spin down), the pull the drive out completely.

8. Push in the latch handle on the removed disk drive to protect it from damage.

9. Wait approximately one minute after the drive has been removed before inserting a new replacement drive.

This allows the system time to determine that the failed drive has been removed and for internal drive states to be updated.

10. Push the latch release to open the handle on the disk drive to be installed.

11. Insert the new disk drive gently on the middle of the rails and push it in until it is seated with the mid-plane connector.

12. Push in on the drive handle to firmly secure the drive.


13. After the drive is fully inserted, the green LED blinks for approximately 1-2 minutes before staying on solid to indicate a ready state.



14. Verify that the disk drive is ready-enabled by clicking array00 - u1d1 in the online version of these instructions.

■ The FRU Stat- Status should be Ready-Enabled.

■ The Vol Stat should be Mounted.

■ The Proc List volume reconstruction activity MUST be complete before starting the next step.





16. Turn the tray LED Off by clicking Clear Tray Locator in the online version of these instructions.



Removing and Replacing an Array Controller Card

1. If you have already selected the correct controller card, go to step 3, or if you have not, go to step 2.

2. If you need help locating the correct tray, activate the blinking white locator LED by clicking on Set tray locator in the online version of these instructions.

3. The controller card is located in the middle of the tray when facing the back of the tray (FIGURE 10-17).

FIGURE 10-17 Controller Card Location

4. Locate the controller card that needs to be replaced with the blue LED on, indicating a ready to remove state.

If the blue LED is not on, proceed to step 6 regardless.

5. Verify that the controller card is ready to remove by clicking on array00 - u1ctr in the online version of these instructions.

The FRU Stat Status-State should be either Offline-Disabled, or Ready-Disabled.

Note – If the controller card is not Offline-Disabled, or Ready-Disabled, call your Sun Service provider to assist with this service action.

6. If the controller card is Offline-Disabled, or Ready-Disabled, remove the Ethernet cable from the connector.

7. Remove the fiber optic cable from the connector.

Controller Card



8. Loosen the Phillips screw to unlock the latch handle.

9. Pull the latch handles to release the controller card from the connector and remove it from the tray (FIGURE 10-18).

FIGURE 10-18 Removing the Controller Card

10. Place the removed controller card in an antistatic bag.

11. Insert the new controller card all the way in the chassis.

12. Push in the latch handles to secure the controller card with the connector, then tighten the retaining screw.

13. Insert the fiber optic cable into the connector, and the Ethernet cable into the Ethernet connector.

14. Allow enough time for the controller to boot (3 - 5 minutes), then check the controller LEDs to determine when the controller is operational.

The controller is operational when the green LED is on.



Note – During a controller boot process, if the Power-On-Self-Test detects a fatal problem with the controller, the system prevents the controller from going online. If this happens, the amber LED, which normally indicates a controller failure, does not light.

15. Verify that the controller card is ready-enabled by clicking array00 - u1ctr in the online version of these instructions.

The FRU Stat Status-State should now be Ready-Enabled.









18. Turn the tray LED Off by clicking on Clear Tray Locator in the online version of these instructions.



Removing and Replacing an Array Loop Card

1. If you have already selected the correct interconnect card, go to the next step or return to the previous screen to select another interconnect card.

2. If you need help locating the correct tray, activate the blinking white locator LED by clicking on Set Tray Locator in the online version of these instructions.

3. Locate the interconnect card with the blue LED on, indicating a ready to remove state.

If the blue LED is not on, go to step 4 regardless.

Interconnect card number one is located on the left and interconnect card number two is located on the right when facing the back of the tray (FIGURE 10-19).

FIGURE 10-19 Interconnect Card Locations

4. Verify that the interconnect card is ready to remove by clicking array00 - u1l1 in the online version of these instructions.

The FRU Stat Status-State should be either Offline-Disabled, or Fault-Disabled, or Ready-Disabled.

Note – If the interconnect card is not Offline-Disabled, or Fault-Disabled, or Ready-Disabled, call your Sun Service provider to assist with this service action.

Interconnect card number one (1) is located on the left and interconnect card number two (2) is located on the right.

1 2



5. If the interconnect card is ready for removal, remove the interconnect cable from the failed interconnect card.

Note whether the removed cable is from either the left or the right interconnect card receptacle.

6. Loosen the Phillips retaining screw to unlock the latch handle.

Caution – The latch handle on the interconnect card is operated by a gear at the base of the card. To avoid injury, keep your fingers away from this gear when removing the card and opening or closing the latch handle.

7. Pull the latch handles to release the interconnect card from the connector and remove it from the tray (FIGURE 10-20).

FIGURE 10-20 Removing the Interconnect Card

8. Place the removed interconnect card in an antistatic bag.

9. Insert the new interconnect card all the way in to the chassis.

10. Lock the new interconnect card in place by pushing in on the latch handle, then tighten the retaining screw.

11. Reconnect the interconnect cable to the interconnect card.

12. Verify that it has initialized properly by checking the green LEDs on the interconnect card.



13. Verify that the interconnect card is ready-enabled by clicking on array00 - u1l1 in the online version of these instructions.

The FRU Stat Status-State should now be Ready-Enabled.





15. Check the revision level of the new card to confirm compatibility by clicking array00 - u1l1 in the online version of these instructions.





Removing and Replacing an Array Power and Cooling Unit

1. If the correct power and cooling unit has been selected proceed to step 3; otherwise, return to the previous screen to select another power and cooling unit battery.

2. If needed, to help locate the correct tray, activate the blinking white locator LED by clicking on Set Tray Locator in the online version of this procedure.

3. Locate the power and cooling unit with the blue LED on, indicating a ready to remove state. If the blue LED is not ON, still proceed to step 5 (FIGURE 10-21).

When facing the back of the tray, power and cooling unit number one is located on the left and power and cooling number two is located on the right.



FIGURE 10-21 Power and Cooling Unit Locations

4. Verify the power and cooling unit is ready to remove by click on array00 u1pcu1 in the online version of these instructions.

The FRU Stat Status-State should be Fault-Enabled or Fault-Disabled.

5. Confirm that the FRU Stat Status-State for the redundant power and cooling unit in the same tray is Ready_Enabled.

Note – If the power and cooling unit is not Fault-Enabled or Fault-Disabled and the redundant power and cooling unit Ready-Enabled, call your Sun Service provider to assist with this service action.

6. If the power and cooling unit is ready for removal, shut off the power and cooling unit by pressing the power switch to Off.

7. Disconnect the power cable from the power and cooling unit.

8. Remove the power cable from the cable clip on the power and cooling unit.

9. Loosen the Phillips retainer screw to unlock the power and cooling unit latch handle.

10. Pull up on the latch handle to release the power and cooling unit from its connector.

11. Pull the power and cooling unit straight out of the tray (FIGURE 10-22).

Note – Use care not to unplug any other cables when removing the power and cooling unit.

Power and Cooling Units



FIGURE 10-22 Removing the Power and Cooling Unit

12. Turn the power and cooling unit over and place it on a flat surface so that the bottom is facing up.

13. Remove the four screws that secure the UPS battery in the power and cooling unit.



14. Lift the battery up and pull it out at an angle to disconnect it (FIGURE 10-23).

FIGURE 10-23 Removing the Battery Unit

15. Slide the battery in the new power and cooling unit at a slight angle, matching the male connector on the battery with the female connector on the power and cooling unit.

16. Secure the four screws that hold the battery in place.

17. Insert the new power and cooling unit in the tray until the latch handle touches the chassis.

18. Push the latch handle down and secure the Phillips retainer screw to lock the latch handle.

When the power and cooling unit receives AC power, the LEDs will flash.

19. Make sure the power switch is in the Off position (-) before connecting the power cord.



20. Insert the power cord into the power and cooling unit connector, then press the power switch to the On position.

21. Insert the power cable into the cable clip.

22. Verify that the power and cooling unit green LED is On and that power is present.

23. Verify that the power and cooling unit is ready-enabled by clicking array00 - u1pcu1 in the online version of these instructions.

The FRU Stat Status-State should now be Ready_Enabled. The FRU Stat Output should be Normal and the Battery should be Charge, or Normal.





25. Turn the tray LED Off by clicking on Clear tray locator in the online version of these instructions.

Removing and Replacing the Battery in the Array Power and Cooling Unit

1. If you already have selected the correct power and cooling unit/battery, proceed to step 3; otherwise, return to the previous screen to select another power and cooling unit / battery.

2. If you need help locating the correct tray, activate the blinking white locator LED by clicking on Set Tray Locator in the online version of this procedure.

3. Locate the power and cooling unit/battery that needs to be replaced (FIGURE 10-21).

4. Verify that the power and cooling unit that contains the failed battery is ready to be removed by clicking on array00 - u1pcu1 in the online version of these instructions.

The FRU Stat Output should be Fault and Battery should be Failed.

5. Confirm that the FRU Stat Status-State for the redundant power and cooling unit in the same tray is Ready-Enabled.

■ If the FRU Stat Output is not Fault and the Battery Failed, call your Sun Service provider to assist with this service action.



■ If the FRU Stat Output is Fault and the Battery is Failed, the power and cooling unit is ready for removal; go to the next step.

6. Power off the power unit by pressing the power switch to Off.

7. Disconnect the power cable from power and cooling unit.

8. Remove the power cable from the cable clip on the power and cooling unit.

9. Loosen the retainer screw to unlock the power and cooling unit latch handle.

10. Pull up on the latch handle to release the power and cooling unit from its connector, then pull the unit straight out of the tray (FIGURE 10-22).

Note – Use care not to unplug any other cables when removing the power and cooling unit.

11. Turn the power and cooling unit over and place it on a flat surface so that the bottom is facing up.

12. Remove the four Phillips screws that secure the UPS battery in the power and cooling unit.

13. Lift the battery up and pull it out at an angle to disconnect it (FIGURE 10-23).

Note – Dispose of the old battery properly.

14. Slide the new battery in at a slight angle, matching the male connector on the battery with the female connector on the power and cooling unit.

15. Secure the four screws that hold the battery in place.

16. Insert the power and cooling unit in the tray until the latch handle touches the chassis.

17. Push the latch handle down and secure the Phillips retainer screw to lock the latch handle.

When the power and cooling unit receives AC power, the LEDs will flash.

18. Make sure the power switch is in the Off position (-) before connecting the power cord.

19. Insert the power cord into the power and cooling unit connector, then press the power switch to the On position.

20. Insert the power cable into the cable clip.

21. Verify that the power and cooling unit green LED is On and that power is present.



22. Verify that the power and cooling unit is ready-enabled by clicking array00 - u1pcu1 in the online version of these instructions.

The FRU Stat Status-State should now be Ready-Enabled. The FRU Stat Output should be Normal and the Battery should be Charge or Normal.






Adding Array CapacityFollow these steps to add array capacity.

1. You should have selected the first available disk drive slot identified as Dummy Disabled. If it wasn't, return to the previous screen and select the correct drive slot.

2. Verify that the disk drive is Dummy Disabled by clicking on array00 - u1d7 in the online version of these instructions.

The FRU Stat, Status-State should be: Dummy Disabled.

3. If needed, to help locate the correct tray, activate the blinking white locator LED by clicking on Set Tray Locator online version of these instructions.

4. Locate the blank drive spacer that needs to be removed (FIGURE 10-15).

Disk drives are numbered from 1 to 14, starting on the left side of the tray.

5. Push down on the latch release to open the latch handle (FIGURE 10-16).

6. Use the latch handle to pull out the blank drive spacer.

7. Remove the blank drive spacer from the array.

8. Push in the latch handle on the removed blank drive spacer to protect it from damage.

9. Push the latch release to open the handle on the disk drive to be installed.



10. Insert the new disk drive gently on the middle of the rails and push it in until it is seated with the mid-plane connector.

11. Push in on the drive handle to firmly secure the drive.


After the drive is fully inserted, the green LED blinks for approximately 1-2 minutes before staying on solid to indicate a ready state.

12. Repeat Step 1 through Step 11 for each drive that will be added to the tray.

13. Verify that the newly installed disk drives are Ready-Enabled by clicking on array00 - u1d7 in the online version of these instructions.

The FRU Stat, Status-State should be: Ready-Enabled.





15. Select and apply any patches as required.

16. After the Generate New Inventory has completed, confirm that the new disk drives have been added from the Current Inventory table, then click Save New Inventory at the bottom of the screen.




Removing Array CapacityFollow these steps to remove array capacity.

1. Make sure that the disk drive that has been selected is the correct disk drive and ready for removal, then verify that:

a. The customer has backed up the data.

b. The drive is not allocated to any jobs.

2. Verify that the disk drive is not mounted by clicking on array00 - u1d1 in the online version of these instructions.

The disk drive should no longer be listed under the Vol Stat.

3. If you need help locating the correct tray, activate the blinking white locator LED by clicking on Set Tray Locator in the online version of these instructions.

4. Locate the drive that needs to be removed (FIGURE 10-15).

Disk drives are numbered from 1 to 14, starting on the left side of the tray.

5. Push down on the latch release to open the latch handle (FIGURE 10-16).

6. Use the latch handle to pull out the disk drive and remove it from the array.

7. Push in the latch handle on the removed disk drive to protect it from damage, then place it in an antistatic bag.

8. Push the latch release to open the handle on the blank disk drive spacer to be installed.

9. Insert the blank disk drive spacer gently on the middle of the rails and push it in until it is seated with the mid-plane connector.

10. Push in on the blank disk drive spacer handle to firmly secure the blank drive.

The handle clicks into place when the blank drive is fully inserted.

11. Repeat Step 1 through Step 10 for each drive that will be removed.

12. Verify the state of the remaining disk drives in that tray by clicking array00 - u1d1 in the online version of these instructions.

■ The FRU Stat, Status-State should be Ready-Enabled.

■ The Vol Stat should be Mounted.

■ Any drives that have been removed should be Dummy Disabled.







14. Turn the tray LED Off by clicking Clear Tray Locator in the online version of these instructions.





CHAPTER 11

Servicing the Storage Service Processor and USB Flash Disk

This chapter describes how to remove and replace the service processor panel and the USB relay panel. It includes the following sections:


■ “Removing and Replacing the Storage Service Processor” on page 198

■ “Reloading the Storage Service Processor Image” on page 200

■ “Replacing the USB Flash Disk” on page 201



Note – Follow the safety precautions described in “Maintenance Precautions” on page 34

197


Removing and Replacing the Storage Service ProcessorYou must have a service processor recovery CD to complete this procedure.


1. If possible, verify the host name of the service processor being replaced.

2. Establish a serial connections to the NYC as follows:


4. If you did not receive the previous message, go to Step 7.



Press Return






6. Upon successful login, run the fbr command with the -b (backup) option to ensure the flash disk contains the latest system-specific information from the service processor, as follows:

A message confirms a successful completions: Backup Command Successful, or Restore Command Successful.

7. Issue a shutdown to the service processor as follows:

8. From the back of the cabinet, open the service panel by loosening the three captive fasteners on the right side of the service processor an I/O panel and open the panel.

9. Power off the service processor.

It could take up to five minutes to complete the power off and shut down.

10. Disconnect the power cable.

11. Disconnect all cables from the service processor, making sure to label each cable indicating its location.

12. Remove the USB flash disk.

13. From the front of the cabinet, remove the trim strips holding the service processor to the cabinet.

14. Remove the service processor by sliding it out the front of the cabinet.

15. Remove the 12 screws (6 on each side) that hold the service processor to the mounting brackets.

16. Attach the mounting brackets to the new service processor.

17. Insert the new service processor by sliding it back into the front of the cabinet.

18. Replace the two screws with the trim strips to secure the service processor to cabinet.


# /opt/SUNWsefbru/bin/fbr -b

sp0# shutdown -y

Chapter 11 Servicing the Storage Service Processor and USB Flash Disk 199


19. Reconnect all cables.

20. Insert the power cable.

21. Power on the service processor.

22. Close the service panel and tighten the three captive screws.

23. Wait for the boot process to complete and the service processor login prompt to appear, then follow the instructions for reloading the Storage Service Processor image in the next section.

Reloading the Storage Service Processor Image

1. Insert the recovery CD into the service processor CD-ROM drive tray and close the tray.

2. Establish a telnet connection to the service processor by entering:

3. Type the following from the lom prompt.

4. Type the following from the ok prompt.

5. Type y of the following:

login: #.

lom> break.

ok> boot cdrom - install

The system displays the following:

This CD restores your Sun StorEdge 6920 Service Processor back to the factory defaults it shipped with. All current state will be wiped clean.Are you sure you want to do this [y/n]?



The Service Processor reboots, then the system prompts you as follows:

6. Insert the USB flash device, then press y to begin the local configuration restore process.

The storage service processor reboots when the process is finished.

7. Log out of the service processor.

8. Disconnect from the service processor console connection using the CTRL+] sequence.

9. Log out of the NTC:

10. Disconnect from the tip session:

11. Remove the CD from the CD-ROM drive when the restore process is finished.

Replacing the USB Flash Disk1. From the back of the cabinet, loosen the three captive fasteners on the right side

of the Service Panel and open the panel.

2. Locate the USB flash drive, and remove it from the back of the service processor.

3. Insert the new USB flash drive.

4. Restore the configuration information to the new USB flash drive by running the back-up flash drive command as follows:

To restore local information the USB flash disk must be connected.

Connect the USB devices, then press y to continue. [y/?]

sp0# logout

ntc0: logout

ntc0: ~.

Chapter 11 Servicing the Storage Service Processor and USB Flash Disk 201


a. From the Select Command pull-down box, select the /opt/SUNWsefbru/bin/fbr -b command.

b. Select Run Command.

You should see a successful completion message such as: Backup Command Successful, or Restore Command Successful.




CHAPTER 12

Servicing the Storage Service Processor Accessory Tray

This chapter describes how to replace the Storage Service Processor accessory tray, and contains the following sections:


■ “Overview of the Storage Service Processor Accessory Tray” on page 204

■ “Overview of the Storage Service Processor Accessory Tray Cables” on page 206

■ “Removing and Replacing the Storage Service Processor Accessory Tray” on page 209

■ “Configuring the NTC” on page 210

■ “Configuring the Router and Firewall” on page 212




203


Overview of the Storage Service Processor Accessory TrayThe Storage Service Processor accessory tray is mounted in the Sun StorEdge 6920 system directly below the Storage Service Processor. The Storage Service Processor accessory tray contains the following pieces:

■ Serial Network Terminal Concentrator (NTC) – Used for remote serviceability support. The NTC provides secure access for inbound and outbound connections, LAN-to-LAN, the console server, and ISP connections. The NTC supports Point-to-Point protocol (PPP), Serial Line Internet Protocol (SLIP/CSLIP), SecurID, Radius, Kerberos, UNIX, NetWare, and local user’s database for authentication on inbound and outbound connections. Additional protection is provided through the routing capabilities. TCP/IP, IPX, and AppleTalk protocols can be routed, in addition to supporting Network Address Translation (NAT).

■ Ethernet router/firewall – Used to provide additional security to Sun from the site LAN. Because the Storage Service Processor could be connected to the customer’s management LAN, there is a security risk to the Storage Service Processor and its software components. This security issue is heightened with the presence of Sun StorEdge Remote Response, which would extend the risk into the Sun Remote Support Center. Using a hardware firewall enables Sun to establish the type of traffic allowed to pass through to the Storage Service Processor from the customer’s management LAN.

■ The 4-port Ethernet hub – Provides connectivity to support additional external Storage Service Processors connected to any given Storage Service Processor, thus forming a miniature daisy-chained LAN. The WAN port can be used to connect the master Storage Service Processor to your management LAN or provide a local port for service actions. Combining this hardware firewall with a 4-port Ethernet hub eliminates both problems.

■ Personal Computer Memory Card International Association (PCMCIA) compatible modem – Is the default connection point for the Sun StorEdge Remote Response solutions center support personnel. If the location of the system is not within one of the supported countries, an external serial port is available to connect an external modem qualified for that country locally.

■ A single AC power supply – Used by all components in the tray.

The Storage Service Processor in the Sun StorEdge 6920 system contains Storage Automated Diagnostic Environment software that identifies devices, logs events, and alerts Sun engineers by email and pager if the data falls outside of pre-defined tolerances.



The Storage Service Processor communicates on two networks. The internal component LAN (IP address 192.168.0.2) and the SP LAN (IP address 10.0.0.2). The SP LAN is used to aggregate the Sun StorEdge Remote Response access to a modem.

Most of this information can be obtained by running the ifconfig(1M) command on the Storage Service Processor. The interface information that is not the lo0 FRU is the information required.

The following example output from ifconfig shows the Storage Service Processor IP address (10.0.0.10), the netmask being used (ff000000), and the broadcast being used (10.0.0.255).

Note – The internal component LAN is a private network for the Storage Service Processor only.

The Storage Service Processor LAN is on dmfe0 and the internal component LAN is on dmfe1 of the Storage Service Processor. For example, use the following commands to view the network interface parameters:

# ifconfig dmfe0dmfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 10.0.0.10 netmask ff000000 broadcast 10.0.0.255# ifconfig dmfe1

dmfe1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3 inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255

Chapter 12 Servicing the Storage Service Processor Accessory Tray 205


Overview of the Storage Service Processor Accessory Tray CablesThis section describes the cables and connections involved when removing and replacing the Storage Service Processor accessory tray.

FIGURE 12-1 shows the connections on the Storage Service Processor accessory tray.

FIGURE 12-1 Storage Service Processor Accessory Tray Connections

TABLE 12-1 lists the external cables used to connect the Storage Service Processor accessory tray to the Storage Service Processor and the Storage Processor Access Panel.

TABLE 12-1 Sun StorEdge Remote Response Program Service Panel Cabling

Cable Type Description

1 RJ45M/RJ45M Cat-5 (1-1/8-8) Connects the Service Processor Access Panel Serial Console Port to the Storage Service Processor accessory tray Serial Console Port

2 RJ45M/RJ45M Cat-5 (1-1/8-8) Connects Storage Service Processor SP TTY-A port to the Storage Service Processor Accessory tray SP ttya port

3 RJ45M/RJ45M Cat-5 (1-1/8-8) Connects Service Processor access panel service serial port to the Storage Service Processor accessory tray Service Serial port

4 RJ45M/RJ45M Cat-5 (1-1/8-8) Connects Service Processor access panel AUX port to the Storage Service Processor accessory tray Aux port

5 RJ45M/RJ45M Cat-5 (1-1/8-8) Connects Service Processor access panel user LAN port to the Storage Service Processor accessory tray user LAN

6 RJ45M/RJ45M Cat-5 (1-1/8-8) Connects the Storage Service Processor DFME-0 Ethernet port to the Storage Service Processor accessory tray SP dfme0 port

SERIALCONSOLE

SPttya

SPdfme0

1

SP LANIN

SP LANOUT NTC ENET PHONE

SERVICESERIAL

USERLANAUX

2 3LAN 4WAN

PWR

TEST

1 2 3 4 5 6 7 8 9 10



FIGURE 12-2 shows the cables inside the Storage Service Processor accessory tray.

7 RJ45M/RJ45M Cat-5 (1-1/8-8) Connects the Service Processor access panel SP-LAN In port to the Storage Service Processor accessory tray SP LAN In port

8 RJ45M/RJ45M Cat-5 (1-1/8-8) Connects the Service Processor access panel SP-LAN Out port to the Storage Service Processor accessory tray SP LAN Out port

9 RJ45M/RJ45M Cat-5 (1-1/8-8) Connects the Storage Service Processor accessory tray NTC Enet port to the Storage Service Processor accessory tray SP-LAN Enet port

10 RJ11M/RJ11M Standard four-conductor phone cord. Connects Service Processor access panel phone port to the Storage Service Processor accessory tray phone port

TABLE 12-1 Sun StorEdge Remote Response Program Service Panel Cabling (Continued)

Cable Type Description



FIGURE 12-2 Internal Layout of the Storage Service Processor Accessory Tray

Router

Power Supply

Modem

Network Terminal Concentrator



Removing and Replacing the Storage Service Processor Accessory TrayThe replacement Storage Service Processor accessory tray has the Network Terminal Concentrator (NTC) and the Router/Firewall configured to Sun’s factory settings. The factory settings are shown in.

However, the Storage Service Processor is already configured with a host name that is dependent on the system ID (0 to 7) of the Sun StorEdge 6920 system. For example, the host name of the Storage Service Processor with system ID 3 is “sp3.” The IP address for that system is 10.0.0.40.


To remove and replace the Storage Service Processor accessory tray:

1. Open the back door of the system.

2. From the back of the cabinet, unscrew the three captive fasteners on the right side of the service panel and open the panel.

3. Disconnect the power cable from the Storage Service Processor accessory tray.

There is no On/Off switch on the Storage Service Processor accessory tray.

4. Make sure all cables are labeled and moving from right to left, disconnect all cables.

See TABLE 12-1 to identify the names of all cables.

5. Remove the two screws that hold the back of the Storage Service Processor accessory tray in place.

Note – The screw that holds the left rail in place is hidden behind a bundle of cables. Open the front door of the system.

TABLE 12-2 Factory Settings

Variable NTC Firewall

Host name new_ntc new_firewall

IP address 10.0.0.243 10.0.0.242



6. Cut the wire tie holding the power cable to the right rail.

7. From the front of the cabinet, remove as many of the filler panels as necessary to remove the Storage Service Processor accessory tray.

8. Remove the two screws that secure the front of Storage Service Processor accessory tray to the cabinet.

9. Remove the Storage Service Processor accessory tray by sliding it out the front of the cabinet.

10. Remove the six screws (three on each side) that hold the Storage Service Processor accessory tray to the mounting brackets.

11. Attach the mounting brackets to the new Storage Service Processor accessory tray using the six screws.

12. Slide the Storage Service Processor accessory tray into the cabinet.

13. Replace the two screws that secure the front of Storage Service Processor accessory tray to the cabinet.

14. Replace any filler panels that were removed while removing the Storage Service Processor accessory tray.

15. From the back of the cabinet, replace the two screws that secure the mounting rails.

Use care when moving cables out of the way.

16. Replace the cut wire tie to hold the power cable tot he right rail.

17. Moving from left to right, replace all non-power cables.

See TABLE 12-1 to identify the location of all cables.

18. Connect the power cable back into the Storage Service Processor accessory tray.


20. Close the back door of the system.

Configuring the NTC The NTC will fail the boot process because it must load firmware from the Storage Service Processor configured as new_sp. At this stage the Storage Service Processor will have a host name associated with the system ID of the configured Sun StorEdge 6920 system.



The NTC tries five times to boot before giving up. After the five tries, the NTC displays a login prompt. Follow the procedures below to re-configure the NTC.

1. Establish a serial connection to the NTC.

2. Issue the following commands to configure the NTC to the correct values.

Reference the /etc/hosts file to identify the ten Net addresses for your specific sp. As an example for sp0:

■ 10.0.0.2 - sp0-firewall

■ 10.0.0.3 - sp0-ntc

■ 10.0.0.10 - sp0

NTC boots with the following output:

tip -9600 /dev/ttya or dev/ttyb

login: rsspassword: sun1rss

ntc0: set priv Password: sun1rssntc0: set server ipaddress 10.0.0.3 ntc0: define server software "scs400.sys"ntc0: source "10.0.0.10:config.sys"

%Info: Port speed changed to 57600.

ntc0: init reload



3. The NTC reboots with the following output.

4. You must enter Return when the NTC appears to hang.

Continue with the configuration instructions in the following section.

Configuring the Router and Firewall Follow these steps to configure the router and firewall.

Lantronix SCS400 Initialization

Rom Version V1.2 (Dec 31, 2001)Ethernet Address: 00-00-a0-06-00-10 Internet Address 10.0.0.3

Current Diagnostics report: NVR Config: Normal Ram Size: 4096 KB Flash Version: B2.0/202(021016) ARM ASIC Version: 7 FPGA Version: 3 Errors: None

...

Load Completed - Booting to Address 0x20188%Error: Duplicate IP address - not added.%Error: Duplicate IP address - not added.%Error: Duplicate IP address - not added.%Error: Duplicate IP address - not added.%Error: Duplicate IP address - not added.%Error: Duplicate IP address - not added.%Error: Duplicate IP address - not added.%Error: Duplicate IP address - not added.



1. Connect to the Storage Service Processor through the NTC.

2. Log in to the Storage Service Processor as root. The default password is !root.

3. Identify the system ID.

4. Save the current repository file which contains information about the firewall.

The following fours files are listed: downgrade, get version, restore and upgrade.

5. Execute the file run command on the restore file.

login: rssPassword: sun1rss

Lantronix SCS400 Version B2.0/202(021016)

Type HELP at the ’ntc0: ’ prompt for assistance.

ntc0: connect local port_2Local protocol emulation 1.0 - Local Switch: <^[>.

Sun StorEdge 6920 Service Processor

WARNING: This is a restricted access server. If you do not haveexplicit permission to access this server, please disconnectimmediately. Unauthorized access to this system is an actionableoffense and will be prosecuted to the fullest extent of the law.


sp0# more /etc/nodenamesp0

sp0# cd /opt/SUNWsespfw/binsp)# ls

sp0# ./restore



The following output appears.

Note – The restore and reboot of the service processor accessory tray may take several minutes to complete.

Step 1 : Backing up Firewall Repository file...Step 2 : Downloading Firewall ROM file...Step 3 : Check for Firewall to come back online, up to 5 minutes...Feb 10 14:13:51 sp6 dmfe: NOTICE: dmfe0 PHY 1 link down10.0.0.242 is aliveStep 4 : Changing Firewall Settings, takes several minutes...DEBUG(196): Starting firewall configuration...DEBUG(196): Locking blocker file fw_access_block...DEBUG(196): Reading Repository...DEBUG(196): Repository ‘/opt/SUNWsespfw/repository’ does not exist;DEBUG(196): creating new repository information...DEBUG(196): Starting firewall configuration...DEBUG(196): Pinging new_firewall via ICMPDEBUG(196): new_firewall is aliveDEBUG(196): Unique ID: '0030ab1ef9c8'DEBUG(196): Pinging new_firewall via ICMPDEBUG(196): new_firewall is aliveDEBUG(196): Modifying WAN connection...DEBUG(196): Getting WAN address typeDEBUG(196): Getting WAN address typeDEBUG(196): Modifying port forwarding address...DEBUG(196): Modifying LAN connection...DEBUG(196): LAN IP settings updated - committing changesnew_firewall (10.0.0.242) deletedDEBUG(196): Sleeping 90 seconds for firewallDEBUG(196): Modifying DHCP server...DEBUG(196): Configuring DHCP server state to disabledDEBUG(196): Desired DHCP server configuration matches current configDEBUG(196): Unlocked blocker fileDEBUG(196): Calling RNID configuration agentDEBUG(196): Firewall configuration complete.DEBUG(196): Configuration changed: saving imageDEBUG(196): Saving configuration for firewall at 10.0.0.2DEBUG(196): Good completionStep 5 : Verifying Firewall Port Settings, may take several minutes...

##### restore_SPAT.ksh completed successfully ######



6. Verify the firewall has been restored correctly.

7. Log out of the service processor.

8. Disconnect from the service processor console connection using the CTRL+] sequence.

9. Logout of the NTC.

10. Disconnect from the tip session.

sp0# ping sp0-firewall

sp0-firewall is alive

sp0# logout

ntc0: logout

ntc0: ~.





CHAPTER 13

Servicing the Storage Service Processor Panel

This chapter describes how to replace the service processor panel and the USB relay panel. It contains the following sections:


■ “Removing and Replacing the Service Panel” on page 218

■ “Removing and Replacing the USB Relay Panel” on page 221




217


Removing and Replacing the Service PanelIf the Sun StorEdge 6920 subsystem is configured for remote power management, you must turn the key switch from Standby to On before following this procedure.


1. Halt all I/O to the 6920 subsystem.

2. Open the back door of the subsystem.

3. Label and remove all cables from the outside of the service panel.

4. Unscrew the three captive fasteners on the right side of the service panel and swing the panel open.

5. Proceed as follows:

■ If the 6920 subsystem is configured for remote power management, make sure to turn the key switch from Standby to On and go to the next step.

■ If the subsystem is not configured for remote power management, go to step 8.

6. Remove the Rear Sequencer J14 and the Front Sequencer J14 connections.

See FIGURE 13-1 for the location of the J14 connections.



FIGURE 13-1 View of the Back of the Service Panel

7. Disconnect the USB cable from the left side of the USB Relay panel.

8. From the inside of the panel, verify that the cables are labeled and note their location.

9. Remove all cables from the inside of the panel.

10. Close the service panel.

11. Remove the remaining six screws that hold the left side of the service panel to the side of the cabinet.

12. Make a note of the RU locations for all screws and the captive fasteners that hold the service panel in place.

Note – You must replace the service panel in the same location for the cables to be routed properly.

Chapter 13 Servicing the Storage Service Processor Panel 219


13. Lift the panel away from the cabinet, making sure that the panel does not get caught in any of the cables.

14. Disassemble as many of the three sections of the panel as is necessary to replace the defective section.

If the top or center section is defective, you must disassemble the entire panel. You may also need to disassemble the top section, which has the USB relay assembly attached to it.

15. Place the new panel in the exact location from which the old panel was removed.

16. Insert and tighten the six screws on the left side to hold the panel in place on the cabinet.

17. If you removed them, reconnect the Rear Sequencer J14 and the Front Sequencer J14 connections.

18. If you removed it, reconnect the USB relay cable.

19. Reconnect the cables to the inside of the new panel, using care to connect the cables in the same location.

20. Replace any cable ties and wraps to properly route and secure the cables.

21. Close the panel and tighten the three captive fasteners.

22. Replace all of the cables that were removed from the outside of the panel, making sure to connect the cables in the same location.

23. Turn the key switch from On to Standby.

24. Close the back door of the cabinet.

25. Restart I/O to the system.



Removing and Replacing the USB Relay PanelIf the Sun StorEdge 6920 system is configured for remote power management, you must turn the key switch from Standby to On before following this procedure.


1. Open the back door of the subsystem.

2. From the back of the cabinet, loosen the three captive fasteners on the right side of the Service Panel and open the panel.

3. Remove the Rear Sequencer J14 and the Front Sequencer J14 connections.

See the FIGURE 13-1 for the location of the J14 connections.

4. Disconnect the USB cable from the left side of the USB Relay panel.

5. Unscrew the four screws holding the USB Relay Panel in place.

Note – The four screws that hold the panel in place are not captive fasteners.

6. Remove the USB Relay panel.

7. Attach the new USB Relay Panel using the four screws.

Note – Use care when moving the cables out of the way of the bottom screws.

8. Reconnect the Rear Sequencer J14 and the Front Sequencer J14 connections.

9. Reconnect the USB relay cable.

10. Close the Service Panel and tighten the three captive fasteners.

11. Close the back door.

12. Turn the key switch from On to Standby.

Chapter 13 Servicing the Storage Service Processor Panel 221




CHAPTER 14

Replacing Cabinet Field-Replaceable Units

This chapter provides information about adding and removing a second cabinet, and about replacing the components within the cabinet. It includes the following sections:


■ “Adding an Expansion Cabinet” on page 224

■ “Removing and Replacing the Rear AC Power Cable” on page 238

■ “Removing and Replacing the Rear AC Power Cable” on page 238

■ “Removing and Replacing the Front AC Power Cable” on page 240

■ “Removing and Replacing the Front Power Sequencer” on page 240

■ “Removing and Replacing the Rear Power Sequencer” on page 245

■ “Removing and Replacing the Ethernet Hub in the Main Cabinet” on page 247

■ “Removing and Replacing the Ethernet Hub in an Expansion Cabinet” on page 248

■ “Removing and Replacing the Ethernet Hub Bracket in an Expansion Cabinet” on page 249

■ “Removing and Replacing the Key Switch” on page 250

■ “Removing and Replacing the Front Door” on page 252

■ “Removing and Replacing the Back Door” on page 253

■ “Removing and Replacing the Side Panel” on page 253

223





Adding an Expansion CabinetTo connect one or two expansion cabinets, perform the steps in the following sections:

■ “Connecting the Fibre Channel Cables” on page 224

■ “Connecting the Ethernet Cables” on page 226

■ “Connecting Light-Out Power Management Cables” on page 228

■ “Cabling the Remaining Fibre Channel Connections to the Data Service Platform” on page 231

■ “Identifying a Name for Each New Array” on page 235

■ “Configuring the Arrays in an Expansion Cabinet” on page 237

Connecting the Fibre Channel CablesConnect Fibre Channel cables as follows:

1. Use two MTP cables (537-1060-01) to connect the data path FC connections between the base cabinet and the first expansions cabinet as follows (refer to FIGURE 14-1):

a. Use the first cable to connect the EXP A port of the expansion cabinet patch panel to the EXP1 A FC1 port of the base cabinet’s first I/O panel

b. Use the second cable to connect the EXP B port of the expansion cabinet patch panel to the EXP1 A FC2 port of the base cabinet’s first I/O panel



Note – The FC1 connections are the data path FC connections to the master SE6920 controllers. The FC2 connections are the data path FC connections to the alternate master SE6920 controllers.

FIGURE 14-1 Connecting EXP1 A FC1 and EXP1 A FC2 of the Base Cabinet to EXP A and EXP B of the First Expansion Cabinet

1. If you are connecting a second expansion cabinet, use two MTP cables (537-1060-01) to connect the data path FC connections between the base cabinet and the second expansions cabinet as follows (refer to FIGURE 14-2):

a. Use the first cable to connect the EXP A port of the expansion cabinet patch panel to the EXP2 B FC1 port of the base cabinet’s second I/O panel

b. Use the second cable to connect the EXP B port of the expansion cabinet patch panel to the EXP2 B FC2 port of the base cabinet’s second I/O panel

Chapter 14 Replacing Cabinet Field-Replaceable Units 225


FIGURE 14-2 Connecting EXP2 B FC1 and EXP2 B FC2 of the Base Cabinet to EXP A and EXP B of the second expansion cabinet.

Connecting the Ethernet CablesConnect the Ethernet cables as follows:



1. Use the two Ethernet cables to connect the control path Ethernet connections between the base cabinet and the first and second expansion cabinets as shown in TABLE 14-1, and FIGURE 14-3:

FIGURE 14-3 Ethernet Cable Connections for Adding the First Expansion Cabinet to the Base Cabinet

TABLE 14-1 Expansion Cabinet Ethernet Ports

Base Cabinet l Ethernet Port

Expansion Cabinet #

Expansion CabinetEthernet Port Cable

EXP ENET 1 1 ENET 530-3138-01

EXP ENET 2 2 ENET 530-3138-01



FIGURE 14-4 Ethernet Cable Connections for Adding the First and Second Expansion Cabinets to the Base Cabinet

Connecting Light-Out Power Management CablesConnect Lights-Out Power Management cables as follows:

1. Use the two DB-9 Male-to-Female serial cables (530-3210-01) to connect the base cabinet to the first expansion cabinet (see TABLE 14-2, and FIGURE 14-5).

a. Use the first serial cable to connect the Power Sequencer Out Front port of the base cabinet’s service panel to the Power Sequencer In Front port of expansion cabinet patch panel.



b. Use the second serial cable to connect Power Sequencer Out Rear port of the base cabinet’s service panel to the Power Sequencer In Rear port of the expansion cabinet.

FIGURE 14-5 Lights-Out Power Management Cable Connections Between the First Expansion Cabinet and the Base Cabinet

2. To cable Lights-Out power Management for a second expansion cabinet, use the two DB-9 Male-to-Female serial cables (530-3210-01) to connect the first expansion cabinet to the second expansion cabinet (see TABLE 14-3, and fig).

a. Use the first serial cable to connect the Power Sequencer Out Front port of the first expansion cabinet patch panel to the Power Sequencer In Front port of the second expansion cabinet patch panel.

TABLE 14-2 Light-Out Power Management Cabling from Base to First Expansion Cabinet

Base Cabinet PortExpansion CabinetEthernet Port Cable

Power Sequencer Out Front Power Sequencer In Front 530-3210-01

Power Sequencer Out Rear Power Sequencer In Rear 530-3210-01



b. Use the second serial cable to connect the Power Sequencer Out Rear port of the first expansion cabinet patch panel to the Power Sequencer In Rear port of the second expansion cabinet patch panel.

FIGURE 14-6 Lights-Out Power Management Cable Connections Between the First Expansion Cabinet and the Second Expansion Cabinet

TABLE 14-3 Light-Out Power Management Cabling from the First to the Second Expansion Cabinet

First Expansion Cabinet PortSecond Expansion CabinetPort Cable

Power Sequencer Out Front Power Sequencer In Front 530-3210-01

Power Sequencer Out Rear Power Sequencer In Rear 530-3210-01



Cabling the Remaining Fibre Channel Connections to the Data Service PlatformFollow these steps to connect the remaining data path Fibre Channel connections to the Data Services Platform in the base cabinet.

1. Count the number of arrays in the new expansion cabinet.

The expansion cabinet can have from one to six arrays (2 to 12 trays).

Note – The following steps assume there is n (some number between 1 and 6) arrays in the expansion cabinet.

■ For the first expansion cabinet, which is connected to the EXP1 A FC1 port on the patch panel interior, you must use the first n SC (storage) connections from the MTP to the SC cable inside the base cabinet.

The SC connections use cable 537-1061-01 and are labeled: 1A/1B, 2A/2B, 3A/3B, 4A/4B, 5A/5B, 6A/6B.

The other end of these cables are connected to the master SE6020 controllers in the SE6020 arrays in the expansion cabinet through the inter-cabinet MTP cable.

■ For the second expansion cabinet, which is connected to the EXP2 B FC1 port on the patch panel interior, you must use the first n SC (storage) connections from the MTP to the SC cable inside the base cabinet

The SC connections use cable 537-1061-01 and are labeled: 1A/1B, 2A/2B, 3A/3B, 4A/4B, 5A/5B, 6A/6B

2. Determine what ports are unused as follows:

■ If this configuration has two SIO and SRCs, determine what ports are unused from the SIO cards in slots 3 and 4.

These are the ports to be used for SC connections using cable 537-1061-01.

■ If this configuration has four SIO and SRCs, determine what ports are unused from the SIO cards in slots 3 and 4 first. If all ports are populated, then go to the SIO cards in slots 1 and 2 for the first unused ports.

These are the ports to be used for SC connections using cable 537-1061-01.

Note also:

■ Ports 1 though 4 are assigned to host connections and ports 5 through 8 are assigned to storage connections.

■ Port locations go from right (1) to left (8).

■ The odd number SIO cards are for the A and C NPORT host connections and the even number SIO cards are for the B and D NPORT host connections.



■ Storage ports are populated in the following order: 8, 7, 6, 5 on cards in slot 3 and 4. If there are more than 8 controller pairs (14 maximum), then ports are populated in the following order: 4, 3, 2, 1 on cards in slots 1 and 2, and then ports 4 and 3 on cards in slots 3 and 4.

■ Master controller (storage) connections are assigned to card slot locations 1 and 3; alternate controller (storage) connections are assigned to card slot locations 2 and 4.

3. Connect the n SC connections to the first n unused ports found.

See FIGURE 14-7 and FIGURE 14-8 which show a configuration of a base cabinet and one expansion cabinet with four 2x4s and the associated SIO card port connections.

FIGURE 14-7 Example of Base Cabinet and One Expansion Cabinet with Four 2x4s



FIGURE 14-8 SIO Card Ports Connections for Example Configuration of Base Cabinet and One Expansion Cabinet with four 2X4s

See FIGURE 14-9 and FIGURE 14-10 which show a configuration of a base cabinet and the first expansion cabinet with nine 2x2s, and the associated SIO card port connections.



FIGURE 14-9 Example of Base Cabinet and One Expansion Cabinet with Nine 2x2s



FIGURE 14-10 SIO Card Ports Connections for Example Configuration of Base Cabinet and One Expansion Cabinet with Nine 2X2s

4. Repeat steps 2 for the EXP1 A FC2 MTP to SC cable in the base cabinet.

5. Repeat steps 2 for the EXP2 B FC2 MTP to SC cable in the base cabinet.

6. Connect the n SC connections selected to the first n unused ports as per the SIO card connections notes in step 3.

Identifying a Name for Each New ArrayIdentify a name for each new array as follows:

■ For arrays in the first expansion cabinet, select from these names: array10, array 11, array 12, array 13, array 14, array 15

■ For arrays in the second expansion cabinet, select from these names: array20, array 21, array 22, array 23, array 24, array 25

Connecting the AC Power Cables Connect the AC power cables as follows:



1. From the front of the cabinet, remove the four screws holding the key switch panel in place.

2. Verify that the power sequencer circuit breaker is up in the Off position.

3. Pull the AC power cable through the cable hole.

4. Connect the AC power cable to the connector on the power sequencer and engage the latch to secure it to the connector (FIGURE 14-11).

FIGURE 14-11 Connecting the AC Power Cable

5. Connect the AC power cable to the grounded outlet.

6. Verify that all of the tray power and cooling unit switches are in the Off position.

7. Verify that the Local/Remote switch on the power sequencer is in the Remote position and that the key switch is in the On position.



8. Push the power sequencer circuit breaker down to the On position.

The Power Available and two Switched Outlet LEDs should be green.The tray LEDs will flash and half of the power and cooling unit fans will come on and the loop cards will boot.

9. Hold the key switch panel to the cabinet frame and tighten with four screws.

Configuring the Arrays in an Expansion Cabinet After you add an expansion cabinet to the Sun StorEdge 6920 system, configure the arrays using the Sun StorEdge Storage Automated Diagnostic Environment.

To configure the arrays in an expansion cabinet:

1. If not already logged in, log into the system and access the Storage Automated Diagnostic Environment.

The system displays the Current Alarms page.

Note – You must log into the Storage Automated Diagnostic Environment as either Storage or Admin to configure the arrays.

2. Click Service > Sun Solution Series > Ethers.

The system displays the Update Ethers page, which lists the names and corresponding IP addresses of all standard and optional components that can comprise the StorEdge 6920 system.

3. Enter the MAC address of each array in the expansion cabinet in the appropriate MAC address field on the Update Ethers page.

MAC addresses are located on a sticker on the back panel of each array.

For the first expansion cabinet, the MAC addresses for the arrays correspond to IP addresses 192.168.0.50 through 192.168.0.55.

For a second expansion cabinet, enter the MAC addresses for the arrays correspond to IP addresses 192.168.0.60 through 192.168.0.65.

4. Click Update Ethers.

The systems run a script that associates the MAC address of the array with the corresponding IP address to identify the array to the system. The system also updates the /etc/ethers file.

5. Make sure the power switches are in the Off position, then insert the power and cooling unit cables for the new trays.

6. Turn on the power switches for the power and cooling units for all new trays.



Allow three to five minutes for the array to complete the boot cycle.





8. Check the revision level of the new card to confirm compatibility by clicking Verify Revision Maintenance in the online version of these instructions.



c. Select and apply an patches as required.

9. Verify the status of the new trays by clicking on Verify Trays in the online version of this procedure.

The FRU Stat Status-State should now be Ready-Enabled for all FRUs.

10. Create a new Topology Snapshot for the new array by clicking Create New Topology Snapshot in the online version of these instructions, then select Create Topology from the left side of the page.

11. Verify that the new cabinets have been added to the topology by clicking View the New Topology Snapshot link in the online version of these instructions.

Removing and Replacing the Rear AC Power CableFollow these steps to replace the rear AC power cable.

1. Lift the rear power sequencer circuit breaker up to the Off position.

2. Disconnect the AC power cable from the grounded outlet.

3. Disconnect the AC power cable from the connector on the power sequencer, by pushing down on the latch to release the connector and push the cable down through the cable hole (FIGURE 14-12).



FIGURE 14-12 Removing the Power Cable From the Power Sequencer

4. Pull the new AC power cable through the cable hole.

5. Connect the new AC power cable to the connector on the power sequencer and engage the latch to secure it to the connector.


7. Push the rear power sequencer circuit breaker down to the On position.

The Power Available and the two Switched Outlet green LEDs should now be On.

The Amber service LED on the front of the array tray(s) should now be off and the Amber PCU(s) LEDs should also be off.



Removing and Replacing the Front AC Power CableFollow these steps to replace the front AC power cable.

1. Remove the four screws holding the key switch panel in place to provide access to the power sequencer circuit breaker.

2. Lift the front power sequencer circuit breaker up to the Off position.


Disconnect the AC power cable from the connector on the power sequencer, by pushing down on the latch to release the connector and push the cable down through the cable hole (FIGURE 14-12).

4. Pull the new AC power cable through the cable hole.

5. Connect the new AC power cable to the connector on the power sequencer and engage the latch to secure it to the connector.


7. Push the front power sequencer circuit breaker down to the On position.

The Power Available and the two Switched Outlet green LEDs should now be On.

The Amber Service LED on the front of the array tray(s) should now be Off and the Amber PCU(s) LEDs should also be Off.

8. Hold the key switch panel to the cabinet frame and tighten the four screws.

Removing and Replacing the Front Power Sequencer

Caution – This is a disruptive procedure; you must schedule maintenance time with the customer if the Local/Remote switches are in the Remote position on the front and rear power sequencers. Do not attempt this procedure when the Local/Remote switches are in the Remote position; the cabinet will lose power.



If the Local/Remote switches are in the Local position, then you can change the power sequencer non-disruptively. Note that once you turn the circuit breaker Off, you wont be able to view this procedure online Storage Automated Diagnostic Environment because there will be no power to the Service Processor.

1. Remove the four screws holding the key switch panel in place to provide access to the power sequencer circuit breaker.



4. Disconnect the AC power cable from the connector on the power sequencer by pushing down on the latch to release the connector, then pushing it down through the cable hole to allow the power sequencer to slide out (FIGURE 14-12).

5. Disconnect the grounding strap from the power sequencer.



6. From the back of the cabinet, disconnect the key switch cable from the system interface cable; it is located at the back of the front power sequencer (FIGURE 14-13).

FIGURE 14-13 Disconnecting the Key Switch Interface Cable Between the Front and Rear Power Sequencers

7. From the front, remove the key switch panel and cable from the cabinet.

Use care when pulling the key switch cable from under the power sequencer.

8. Remove the power sequencer cables J15 and J14 from the front of the power sequencer and push both cables down through the cable hole.

9. Remove the four screws holding the power sequencer rails to the cabinet frame (FIGURE 14-14).



FIGURE 14-14 Disconnecting and Removing the Power Sequencer from the Cabinet Frame

10. Slide the power sequencer out far enough to see and easily disconnect the following cables:

■ The system interface cable from the connector (J3 or J4) at the back of the power sequencer.

Use a small blade/flat tip screw driver.

■ Cables J1 (bottom) and J2 (top) on the far left and J5 through J12 on the right.

Odd numbered cables J5, J7, J9 and J11 go from left to right on the bottom row of connectors of the sequencer.

Even numbered cables J6, J8, J10 and J12 go from left to right on the top row of connectors of the sequencer.

11. Slide the power sequencer completely out of the cabinet.

12. Remove the eight screws holding the rails to the removed power sequence (FIGURE 14-14).

13. Attach the rails to the new power sequence with the eight screws.



14. Slide the new power sequencer partially into the cabinet leaving enough room to easily connect the cables as follows:

■ Connect the system interface cable to the connector (J3 or J4) at the back of the power sequencer.

A small blade/flat tip screw driver is required.

■ Connect cables J1 (bottom) and J2 (top) on the far left and J5 through J12 on the right.

Odd numbered cables J5, J7, J9 and J11 go from left to right on the bottom row of connectors of the sequencer.

Even numbered cables J6, J8, J10 and J12 go from left to right on the top row of connectors of the sequencer.

15. Carefully slide the power sequencer all the way in, being careful not to pinch any cables.

16. Insert and tighten the four screws holding the power sequencer rails to the cabinet frame.

17. Insert and tighten the power sequencer cables J15 and J14 to the front of the power sequencer.


19. Make sure the power sequencer circuit breaker is in the Off (up) position, then connect the AC power cable to the connector on the power sequencer and engage the latch to secure it to the connector.

20. From the front, place the key switch panel up near the cabinet frame and slide the key switch cable under the power sequencer.

21. From the back of the cabinet, connect the key switch cable to the system interface cable at the back of the front power sequencer.

22. Connect the grounding strap to the power sequencer.


24. Push the front power sequencer circuit breaker down to the On position.

The Power Available and the two Switched Outlet LEDs should now be green.





Removing and Replacing the Rear Power Sequencer

Caution – This is a disruptive procedure; you must schedule maintenance time with the customer is the Local/Remote switches are in the Remote position on the front and rear power sequencers. Do not attempt this procedure when the Local/Remote switches are in the Remote position; the cabinet will lose power.

If the Local/Remote switches are in the Local position, then you can change the power sequencer non-disruptively. Note that once you turn the circuit breaker Off, you wont be able to see this procedure n Storage Automated Diagnostic Environment because there will be no power to the Service Processor.



3. Disconnect the AC power cable from the connector on the power sequencer by pushing down on the latch to release the connector and push the cable down through the cable hole (FIGURE 14-12).

4. Disconnect the grounding strap from the power sequencer.

5. Remove the four screws holding the rear cable restraint panel to the frame.

6. Remove the power sequencer cables J15 and J14 from the front of the power sequencer.

7. Remove the four screws holding the power sequencer rails to the frame (FIGURE 14-14).

8. Slide the power sequencer out far enough to see and easily disconnect the following cables:

■ The system interface cable from the connector (J3 or J4) at the back of the power sequencer.


■ Cables J1 (bottom) and J2 (top) on the far left and J5 through J12 on the right.

The odd numbered cables J5, J7, J9 and J11 go from left to the right on the bottom row of connectors of the sequencer.

The even numbered cables J6, J8, J10 and J12 go from left to right on the top row of connectors of the sequencer.



9. Slide the power sequencer completely out of the cabinet.

10. Remove the eight screws holding the rails to the removed power sequence (FIGURE 14-14).

11. Attach the rails to the new power sequence with the eight screws.

12. Slide the new power sequencer partially into the cabinet leaving enough room to easily connect the cables as follows:

■ Connect the system interface cable to the connector (J3 or J4) at the back of the power sequencer.


■ Connect cables J1 (bottom) and J2 (top) on the far left and J5 through J12 on the right.

The odd numbered cables J5, J7, J9 and J11 go from left to the right on the bottom row of connectors of the sequencer.

The even numbered cables J6, J8, J10 and J12 go from left to right on the top row of connectors of the sequencer.

13. Carefully slide the power sequencer all the way in, being careful not to pinch any cables.

14. Insert and tighten the four screws holding the power sequencer rails to the cabinet frame.

15. Insert and tighten the power sequencer cables J15 and J14 to the front of the power sequencer.


17. Make sure the power sequencer circuit breaker is in the Off (up) position, then connect the AC power cable to the connector on the power sequencer and engage the latch to secure the connector.

18. Place the rear cable restraint panel on the frame and insert and tighten the four screws.

19. Connect the grounding strap to the power sequencer.


21. Push the rear power sequencer circuit breaker down to the On position.

The Power Available and the two Switched Outlet LEDs should now be green.




Removing and Replacing the Ethernet Hub in the Main Cabinet

1. Remove the necessary number of trim panels to gain access to the Ethernet hub.

2. Disconnect the power cable from the Ethernet hub.

3. Remove the two screws holding the Ethernet Hub to the cabinet mounting rails.

4. From the back of the cabinet, unscrew the three captive fasteners on the right side of the service panel and swing the panel open.

5. Verify that all Ethernet cables are labeled, then disconnect the cables.

6. Remove the two screws holding the back of the Ethernet hub to the cabinet mounting rails.

Use a short phillips screw driver to remove the screw from the left side.

7. From the front of the cabinet, slide Ethernet hub out to remove it from the cabinet.

8. Remove the four screws (two per side) holding the Ethernet hub to the mounting rails and the three small screws holding the Ethernet hub to the center bracket.

9. Attach the mounting rails and center bracket to the new Ethernet hub with the seven screws.

10. From the front of the cabinet, slide the Ethernet hub into the cabinet until it stops.

11. Insert and tighten the two screws that attach the front of the Ethernet hub mounting brackets to the cabinet rails.

12. Insert the power cable to power on the Ethernet hub.

13. From the back of the cabinet, insert and tighten the two screws that attach the back of the Ethernet hub mounting brackets to the cabinet rails.

14. Verify that the Power LED is green.

15. Reconnect all of the Ethernet cables.


17. Replace the trim panels in the front of the cabinet.



Removing and Replacing the Ethernet Hub in an Expansion Cabinet

1. From the back, unscrew the two captive fasteners on the right side of the Ethernet hub mounting bracket.

2. Open the Ethernet hub mounting bracket to gain complete access to the cables.


4. Verify that all Ethernet cables are labeled, then disconnect them.

5. Unscrew the four screws (two on the left and two on the right) that secure the Ethernet hub to the mounting bracket and remove it from the mounting bracket (FIGURE 14-15).

Hold on to the Ethernet hub when removing the screws so it does not fall.

FIGURE 14-15 Ethernet Hub and Bracket Assembly in an Expansion Cabinet

6. Place the new Ethernet hub in the mounting bracket and secure it with the four screws (two on the left and two on the right).






10. Close the Ethernet hub mounting bracket and tighten the two captive fasteners.

Removing and Replacing the Ethernet Hub Bracket in an Expansion Cabinet

1. From the back of the cabinet, unscrew the two captive fasteners on the right side of the Ethernet hub mounting bracket.

2. Open the Ethernet hub mounting bracket to gain complete access to the cables.


4. Verify that all Ethernet cables are labeled then disconnect all of the Ethernet cables.

5. Unscrew the four screws (two on the left and two on the right) that secure the Ethernet hub to the mounting bracket and remove it from the mounting bracket (FIGURE 14-15).

Hold on to the Ethernet hub when removing the screws so it does not fall.

6. To ensure proper placement of the new mounting, note the location of where the mounting bracket is mounted to the cabinet, the remove the defective hub mounting bracket.

7. Install the new hub mounting bracket to the cabinet frame.

8. Place the Ethernet hub in the new mounting bracket and secure it with the four screws (two on the left and two on the right).




12. Close the Ethernet hub mounting bracket and tighten the two captive fasteners.



Removing and Replacing the Key Switch1. From the front of the cabinet, remove the four screws holding the key switch

panel to the cabinet frame.

2. Carefully pull the key switch panel off and locate the key switch wiring cable that runs under the front power sequencer.

3. From the back of the cabinet, locate the key switch wiring cable between the front and rear power sequencers (FIGURE 14-16).

FIGURE 14-16 Key Switch Cable Connector Location Between the Front and Rear Power Sequencers

4. From the back of the cabinet, disconnect the key switch cable from the system interface cable between the front and rear power sequencers.



5. From the front, pull the key switch panel and cable from the cabinet.

Use care when pulling the key switch cable from under the power sequencer.

6. From the back of the key switch panel, use a pair of needle noose pliers to slide off the metal clip that holds the key switch to the key switch panel (FIGURE 14-17).

FIGURE 14-17 Removing and Replacing the Key Switch From the Key Switch Panel

7. Pull the key switch out of the key switch panel.

8. Insert the new key switch in the panel opening.

9. Slide the metal clip onto the notch of the key switch body to hold it in place.

10. From the front, place the key switch panel up near the cabinet frame and slide the key switch cable under the power sequencer.

11. From the back of the cabinet, connect the key switch cable to the system interface cable at the back of the front power sequencer.




Removing and Replacing the Front Door This section describes removing and replacing the front door of the cabinet.

▼ To Remove the Front Door:1. Open the front door.

2. Reach inside the door and push down on the lever attached to the spring of the top hinge pin.

This causes the hinge pin to retract into the door.

3. Tilt the door out from the top mounting bracket and lift up slightly to remove the door.

▼ To Replace the Front Door:1. To replace the door, tilt the door and insert the bottom hinge pin with the outside

hole of the bottom left mounting bracket.

2. Reach inside the door and push down on the lever attached to the spring of the top hinge pin.

3. Align the top hinge pin with the outside hole of the top left mounting bracket.

4. Release the lever.

The hinge pin extends into the mounting bracket and the door is now ready to be closed and locked.



Removing and Replacing the Back DoorThis section describes removing and replacing the back door of the cabinet.

▼ To Remove the Back Door:1. Open the back door completely so it will clear the rack frame.

2. Lift the door until the door hinge pins are completely removed from the frame hinge brackets, then lift it away from the unit.

▼ To Replace the Back Door: 1. Position the back door so it completely clears the rack frame.

2. Align the top and bottom hinge pins above the frame hinge brackets and lower the door in place.

The door is now ready to be closed and locked.

Removing and Replacing the Side PanelThis section describes removing and replacing the side panel of the cabinet.

▼ To Remove the Side Panel● For each panel you are removing, use an Allen wrench to loosen the four 1/4-inch

shoulder screws that fasten the side panel to the cabinet frame, then remove the side panel from the frame (FIGURE 14-18).

Use caution to not allow the side panel to fall after the last allen screw is removed.



FIGURE 14-18 Side Panel Removal

▼ To Replace the Side Panel1. Align the side panel screw holes to the cabinet frame screw holes.

2. Use an Allen wrench to tighten the four 1/4-inch shoulder screws to fasten the side panel to the cabinet frame.



CHAPTER 15

Extra Options

This chapter describes how to add and remove lights-out power management, how to add and remove an external modem, and how to use the dangling cable for array enclosure diagnostics. It includes the following sections:


■ “About Lights-Out Power Management” on page 256

■ “Performing a Partial System Shutdown” on page 257

■ “Performing a Full System Shutdown” on page 259

■ “Restoring Power to the System” on page 262

■ “Adding and Removing Lights-Out Power Management” on page 265

■ “Adding and Removing an External Modem” on page 274

■ “Using the Special Service Cable for Diagnostics (Base Cabinet)” on page 276

■ “Using the Special Service Cable for Diagnostics (Expansion Cabinet)” on page 278




255


About Lights-Out Power ManagementThe default power management mode of operation for Sun StorEdge 6920 systems shipped by the factory is Local. The default states of the system is as follows:

■ Power Sequencers are set to Remote

■ Circuit breakers are Off

■ Key Switch is Off

■ Service Processor is connected to the USB relay via a USB cable

When Lights-Out Power Management is enabled, the USB relay controls when the system is at partial or full power. For the relay to be able control the two power sequencers, their toggle buttons must be set to Remote (not Local or Off). Also, for the relay to be included in the circuit, the key switch on the bottom front panel must be set to I (not set to 0).

■ Serial cables between the USB relay and the power sequencers are connected at the power sequencer end, but are not connected to the USB relay (on back side of the path panel)

■ Power sequencer serial cable between the base cabinet the expansion cabinet patch panel is not connected.

■ power sequencer serial cable between the first expansion cabinet the second expansion cabinet patch panel is not connected.

With Lights-Out Power Management enabled, you are able to switch the Power Distribution Units (PDUs) in the cabinets on or off either locally or remotely. Once enabled, the Service Processor detects the presence of the relay board and enables two additional functions in the Control Management Software: Lights-Out Power Up and Lights-Out Power Down. These modes are used to logically shutdown the storage devices n the rack and then instruct the PDUs to disconnect the power from those components. Note that in these two modes, the Service Processor and Service Processor accessory tray remain powered on and active to provide control over the power relay board. You should not use this mode to remotely shutdown the power when moving the cabinets to a different locations; instead, use the complete power down.

For instructions on how to enable Lights-Out Power Management, see “Adding and Removing Lights-Out Power Management” on page 265.



Performing a Partial System ShutdownBefore you power off the system, you must halt any I/O between host systems and the Sun StorEdge 6920 system.

Depending on the data host’s operating system, you might need to:

■ Exit the operating system

■ Take the host system off line

Refer to the host operating system documentation for specific instructions.

Caution – Failure to stop I/O between host system(s) and the expansion cabinet can result in the loss of data.

Powering Off the System PartiallyWhen you partially power off the system, the system components in the base cabinet and expansion cabinet (if applicable) are in the following state:

■ The Storage Service Processor remains powered on (base cabinet only). The system is now under lights-out management control.

■ The Storage Service Processor accessory tray remains powered on (base cabinet only).

■ All arrays are powered off completely. If the system includes an expansion cabinet, the arrays in the expansion cabinet are powered off.

■ The Data Services Platform (DSP) is powered off.

■ On all power sequencers, only the Power Available LED is illuminated.

Follow these steps to partially power off the Sun StorEdge 6920 system:

1. Connect to the configuration management software with a web browser by entering:

where ipaddress is the IP address of the Storage Service Processor or external host where the software is installed.

The Sun Web Console login page is displayed.

https://ipaddress:6789/

Chapter 15 Extra Options 257


2. Log in as a system administrator:

User name: admin password: !admin

3. Click SE6920 Configuration Service.

The General Settings page is displayed.

4. Click the System Partial Shutdown button.

FIGURE 15-1 General Settings Page: System Partial Shutdown Button

5. Click OK to confirm the partial shutdown.

FIGURE 15-2 General Settings Page: Confirm Partial Shutdown



The system is now partially shut down. Refer to “Powering Off the System Partially” on page 257 for the state of each system component.

Performing a Full System ShutdownWhen you perform a full system shutdown, you must go to the location of the system to manually restore power.

Before you power off the system, you must halt any I/O between host systems and the Sun StorEdge 6920 system.

Caution – Failure to stop I/O between host system(s) and the system can result in the loss of data.

When you completely power off the system, the system components in the base cabinet and expansion cabinet (if applicable) are in the following state:

■ The Storage Service Processor is shut down.

■ The Storage Service Processor accessory tray remains powered on.

■ The array drives have spun down.

■ The array controller cards are powered off.

■ The array trays have the green LED illuminated, indicating that the tray has power.

■ The loop cards have the green LED illuminated, indicating that the loop cards have power.

■ The power and cooling unit (PCU) fans are on.

■ The PCUs, in the back of the arrays, have the blue LEDs illuminated meaning it is safe to remove them.

■ All power sequencers have all three green LEDs illuminated meaning power is present.

To completely power off the system, use the following steps:










4. Click the System Shutdown button.

FIGURE 15-3 General Settings Page: System Shutdown Button



5. Click OK to confirm the full system shutdown.

FIGURE 15-4 General Settings Page: Confirm Full Shutdown

6. At the bottom front and bottom back of the base cabinet, press the AC power sequencer circuit breakers to Off.

FIGURE 15-5 AC Power Sequencer Control Panel: Power Off

7. At the bottom front and bottom back of the expansion cabinet (if applicable), press the AC power sequencer circuit breakers to Off.

The system is now completely shut down. Refer to “Performing a Full System Shutdown” on page 259 for the state of each system component.

AC power sequencercircuit breaker

Power Off

Local/Remote switchin Remote position



Restoring Power to the SystemThis section provides procedures for restoring the system after you remotely power off the system. It includes the following sections:

■ “Restoring Power to the System After a Partial System Shutdown” on page 262

■ “Restoring Power to the System After a Full System Shutdown” on page 263

Restoring Power to the System After a Partial System ShutdownIf the system has been powered off using the remote partial shutdown procedure, you must use the following procedure to restore power to the system.







FIGURE 15-6 General Settings Page: System Power Up Button




4. Click the System Power Up button to power on the Sun StorEdge 6920 system.

This selection activates the power sequencers in the base cabinet and any expansion cabinet and causes the storage components to power on. The Switched Outlets LEDs are illuminated.

The system is now ready for operation.

Restoring Power to the System After a Full System ShutdownIf the system has been powered off using the full shutdown procedure, you must go to the system location to restore power.

1. Open the front door and back door if they are not already open.

2. Remove the front trim panel from the base cabinet and set it aside if you have not already done so.

3. Verify that the key switches, located at the bottom front of the base cabinet and any expansion cabinet, are in the Standby position.

4. At the bottom front and bottom back of the base cabinet and any expansion cabinet, press the AC power sequencer circuit breakers to Off.

5. Verify that the AC power cables of the base cabinet and any expansion cabinet are connected to the correct AC outlets.

6. At the bottom front and bottom back of the base cabinet and any expansion cabinet, verify that the Local/Off/Remote switch is in the Remote position.

7. If an expansion cabinet is connected to the base cabinet, press the AC power sequencer circuit breakers to the On position.

Wait until the expansion cabinet completes its power up sequence and all array component LEDs are in the green steady state.

8. At the bottom front and bottom back of the base cabinet, press the AC power sequencer circuit breakers to the On position.

The three power status indicators on the front panel show the status of the front power sequencer. The main AC power light emitting-diode (LED) is illuminated when power is applied to the expansion cabinet. The LED for sequencer stage 1 is illuminated next, followed by the LED for sequencer stage 2.

Note – The front panel power sequencer bottom LED is illuminated only when the AC power sequencer circuit breakers for the front power supply are on.



Note – To check the status of the rear power sequencer, open the back door of the expansion cabinet and look for the three green LEDs.

9. Wait approximately 1 minute after the AC power sequencer circuit breakers are pressed on, and then, at the back of the system, locate the power switch for the Storage Service Processor and press the switch off, then on.

All components of the system power on in an optimal state.

10. Verify that all the components have only green LEDs illuminated.

If LEDs are illuminated other than green ones, or if no LEDs are illuminated, see “Troubleshooting Tips” on page 264 to troubleshoot any component that is not powered on.

11. Replace the front trim panel and close the front and back doors.

The system is now powered up and operational.

Troubleshooting TipsUse this list as a guide for isolating common problems.

■ Verify that all power and data cables are properly installed and in the right locations.

■ Verify that all FC connections, cable adapters, and Gigabit Interface Converters (GBICs) are installed and secure.

■ Verify that the power to the system is turned on.

■ Check the AC power sequencer control panel:

■ If the switched outlet LEDs are not illuminated, check the position of the key switch.

■ If one switched outlet LED is illuminated but the other is not, check the status of the power sequencer for the LED that is not illuminated.

■ If any FRU has an amber LED, a service action is required. Go to the Storage Automated Diagnostic Environment Event Advisor for information.

■ If some FRUs have power and others do not, check the power-on switch on the FRUs that do not have power.



Common problems:1. The user interface shows the Partial Power Down button as grayed-out.

Possible Causes:

■ Lights-Out Power Management may not be enabled. Log into the sp_console as setup. If option 4 reads: Enable Remote Power Management, then select and enable it. If option 4 reads: Disable Remote Power Management, then Light-Out Power Management is enabled.

■ Serial cable between the power sequencers and the USB relay may not be connected; check them.

2. The system is configured for Lights-Out Power Management, but selecting Partial Power or Full Power does nothing, or controls only one cabinet.

Possible Cause: The relays may not be connected tot he USB port on the USB, or the DB-9 cables on the patch panel may not be connected to the following patch panels. Double check the connections.

Adding and Removing Lights-Out Power ManagementFollow the instructions in these sections for adding and removing Lights-Out Power Management:

■ “To Prepare the System for Remote Power” on page 265

■ “To Enable the SW Support for Lights Out Operation” on page 269

■ “To Remove Remote Lights-out Management” on page 271

■ “To Disable the Software Support for Lights Out Operation” on page 272

▼ To Prepare the System for Remote Power 1. Verify that the key switches located at the bottom front of the base system and any

expansion cabinet are in the Standby position.

Keys for this switch are packed in the kit that was shipped with your system and any expansion cabinet. If the key switch is not in the Standby position, insert the key and turn the key switch to Standby.

2. From the back of the base cabinet, unscrew the three captive fasteners on the right side of the service panel and swing the panel open.



3. Locate the two DB-9 to DB-9 cables that are bundled close to the USB relay panel on the back of the service panel.

4. Connect the cable labeled Front Seq J14 in to the front SEQ J14 connection and the cable labeled Rear Seq J14 in to the Rear SEQ J14 connection on the back of the master service panel.

The other ends of these cables are already connected to the front and back power sequencers. They enable the Storage Service Processor to recognize that the system is capable of a remote power-on and power-off sequence.

The following figure shows the back of the Base Cabinet master service panel and the location of the FRONT SEQ J14 and REAR SEQ J14 connections.

FIGURE 15-7 View of the Back of the Master Service Panel

5. Verify that the cable connecting USB port 1 of the service processor to the USB relay card is installed.

The LED on the USB relay card should be green.




7. If an expansion cabinet is to be connected, use the two 393.7-inch (10- meter) DB-9 to DB-9 expansion cabinet cables to connect the power sequencer out-jacks on the front of the base cabinet service panel to the power sequencer in-jacks on the front of the expansion cabinet service panel for both the front and rear power sequencers (FIGURE 15-8).

The cables are in the kit that was shipped with the system.

This connection allows the expansion cabinet to power on or power off when the base cabinet is powered on or powered off.

FIGURE 15-8 Lights-Out Power Management Cable Connections Between the Base Cabinet and the First Expansion Cabinet

8. If a second expansion cabinet is to be connected, use the two 10 meter DB-9 to DB-9 expansion cabinet cables to connect the power sequencer out-jacks on the front of the first expansion cabinet service panel to the power sequencer in-jacks on the front of the second expansion cabinet service panel for both the front and rear power sequencers (FIGURE 15-9).

The cables are in the kit that was shipped with the system.



FIGURE 15-9 Lights-Out Power Management Cable Connections Between the First Expansion Cabinet and the Second Expansion Cabinet

9. From all cabinets, loosen the four screws on the front Key Switch trim panel and remove the panel.

10. At the bottom front left and bottom back left of all cabinets, press the Power Sequencers Local/Off/Remote switch to Remote.

11. Reattach the trim panel(s) to the cabinet frame(s) using the four screws you removed for each trim panel.



▼ To Enable the SW Support for Lights Out Operation

1. Establish a serial connection to the NTC as follows:

2. At the ntc0: prompt, connect to the service storage processor console port. For example:

3. Log in to the Storage Service Processor console, as follows:

tip -9600 /dev/ttya or dev/ttyb# login: rssPassword: sun1rss

ntc0:connect local port_2 Local protocol emulation 1.0 - Local Switch:< >.

Press Return




This account automatically runs a configuration script that will prompt you for information to properly set up the Sun StorEdge 6920 system

4. Select operation number four (4).

The following output appears:

5. Select Y.

Configuration is complete. You should now be at the sp console login.

6. Disconnect from the service processor console login using the CTRL+[ sequence.


new_sp console login: setup Password: !setupLast login: Tue Mar 16 15:35:32 on console Mar 16 15:47:11 new_sp login:ROOT LOGIN /dev/console Tue Mar 16 15:47:12 PST 2004*************************************** StorEdge 6920 Initial Configuration Utility ***************************************Select the operation you wish to perform: 1. Initial configuration 2. Restore previously defined configuration 3. Unconfigure 4. Enable SW Support for Lights Out Operation Your Choice:

*************************************** StorEdge 6x20 Lights Out Operation***************************************Performing this operations will enable the Remote Power feature of you StorEdge 6x20. Before enabling this feature, ensure that your system hardware is configured properly for Remote Power as described in “Preparing the Storage System for Remote Power” in the “Sun StorEdge 6x20 Series 1.0 Storage System Installation Guide.” If the hardware is not configured properly prior to performing this operation, failure alerts will be generated and the Remote Power feature will not be available. Are you sure you wish to perform this operation? (Y/N)

ntc0:logout%Info: Connection with PORT_2 closed.Exiting the Lantronix SCS400




If you want, use the Management software to verify the Lights Out operation functionality.

▼ To Remove Remote Lights-out Management1. Verify that the key switches located at the bottom front of the base system and any

expansion cabinet are in the Standby position.

Keys for this switch are packed in the kit that was shipped with your system and any expansion cabinet. If the key switch is not in the Standby position, insert the key and turn the key switch to Standby.

2. From the back of the base cabinet, unscrew the three captive fasteners on the right side of the service panel and open the panel.

3. Locate the two DB-9 to DB-9 cables that are connected to the USB relay panel on the back of the master service panel.

4. Disconnect the cable labeled Front Seq J14 from the FRONT SEQ J14 connection and the cable labeled Rear Seq J14 from the REAR SEQ J14 connection on the back of the master service panel (FIGURE 15-7).

5. Carefully route the ends of the cables so they do not interfere with the panel, other cables or connections.

The other ends of these cables can remain connected to the front and rear power sequencers.


7. If an expansion cabinet is attached, disconnect the two 393.7-inch (10- meter) DB-9 to DB-9 expansion cabinet cables that connect the power sequencer out-jacks on the front of the master service panel to the power sequencer in-jacks on the front of the expansion cabinet service panel for both the front and rear power sequencers (see FIGURE 15-8).

8. If a second cabinet is attached, disconnect the two 10 meter DB-9 to DB-9 expansion cabinet cables connected between the power sequencer out-jacks on the front of the first expansion cabinet to the power sequencer in-jacks on the front of the second expansion cabinet service panel for both the front and rear power sequencers (FIGURE 15-9).

9. From all cabinets, loosen the four screws on the front Key Switch trim panel and remove the panel.

10. At the bottom front left and bottom back left of all cabinets, press the Power Sequencers Local/Off/Remote switch to Local.



11. Reattach the trim panel(s) to the cabinet frame(s) using the four screws you removed for each trim panel.

▼ To Disable the Software Support for Lights Out Operation

1. Establish a serial connection to the NTC as follows:

2. At the ntc0: prompt, connect to the service storage processor console port. For example:


tip -9600 /dev/ttya or dev/ttyb# login: rssPassword: sun1rss

ntc0:connect local port_2 Local protocol emulation 1.0 - Local Switch:< >.

Press Return




This account automatically runs a configuration script that will prompt you for information to properly set up the Sun StorEdge 6920 system

4. Select operation number one (1) or three (3).

5. Follow the menus and update according to your specific configuration.

■ Operation 1, Initial Configuration is documented in the Sun StorEdge 6920 System Getting Started Guide.

■ Operation 3, Unconfigure is documented in “Unconfiguring and Restoring the Service Processor Configuration” on page 289.

6. Disconnect from the service processor console login using the CTRL+[ sequence.



new_sp console login: setup Password: !setupLast login: Tue Mar 16 15:35:32 on console Mar 16 15:47:11 new_sp login:ROOT LOGIN /dev/console Tue Mar 16 15:47:12 PST 2004*************************************** StorEdge 6920 Initial Configuration Utility ***************************************Select the operation you wish to perform: 1. Initial configuration 2. Restore previously defined configuration 3. Unconfigure 4. Enable SW Support for Lights Out Operation Your Choice:

ntc0:logout%Info: Connection with PORT_2 closed.Exiting the Lantronix SCS400



Adding and Removing an External ModemThis section describes adding and removing and external modem. The procedure details the installation of a customer supplied modem instead of the internal modem of the Sun StorEdge 6920.

▼ To Add an External Modem1. Disconnect the RJ-45 cable (530-3205-01) from the DB-9/RJ-45 Adaptor (530-3205-

01) on the MIC (in slot 6) serial port.

The other end of this cable should remain connected to the AUX port of the Storage Service Processor accessory tray.

FIGURE 15-10 Disconnecting the RJ-45 Cable From the DB-9/RJ-45 Adaptor

2. Unplug the cable that is currently plugged into the AUX port on the inside of the service processor panel.



3. Connect the end of RJ-45 cable (530-3205-01) you disconnected in Step 1 to the AUX port on the inside of the service processor panel.

FIGURE 15-11 Connecting the RJ-45 Cable to the AUX Port on the Service Processor Panel

4. Connect the external modem to the AUX port of the service processor panel.

Note – The NTC port 4 (AUX) is configured for a baud rate of 19200. In order to communicate, you must change the baud rate of the AUX port to match the baud rate of the external modem. Complete the rest of the steps in these instructions to change the baud rate.

5. Determine the baud rate of the external modem, then establish a serial connection to the NTC:

6. Set the baud rate from the ntc0: prompt:


ntc0: set port_4 speed 9600



7. When the service action is complete, log out of the NTC:

8. Disconnect from the tip session:

▼ To Remove an External Modem1. Disconnect the external modem from the AUX port of the patch panel.

2. Disconnect the RJ-45 cable (530-3205-01) from the AUX port on the interior face of the service processor panel (FIGURE 15-11).

3. Reinsert the cable that you unplugged when you installed the modem into the AUX port.

4. Connect the RJ-45 cable (530-3205-01) to the DB-9/RJ-45 Adaptor (530-3205-01) on the MIC (in slot 6) serial port (FIGURE 15-10).

Using the Special Service Cable for Diagnostics (Base Cabinet)Use the special service cable for temporary diagnosis of service issues on 6020s on the Base Cabinet only through the 6020 serial port:


1. Disconnect the RJ-45 cable (530-2990-01) from the DB-9/RJ-45 Adaptor (530-3205-01) on the MIC (in slot 5) serial port.

The other end of this cable should remain connected to the Service Serial port of the Storage Service Processor accessory tray.

ntc0: logout

ntc0: ~.



2. Connect the end of RJ-45 cable (530-2990-01) you just disconnected to the serial port of the 6020 that requires diagnosis (FIGURE 15-12).

The serial port on the 6020 is the right-most RJ-45 receptacle on the 6020 controller. The other end of this cable should remain connected to the Service Serial port of the Storage service Processor accessory try.

FIGURE 15-12 Connecting the RJ-45 Cable to the 6020 Array

3. Change the baud rate to 9600 to facilitate access to the 6020 array:

a. Establish a serial connections to the NTC.

b. Set the baud rate from the ntc0: prompt.





c. When the service action is complete, log out of the NTC.

d. Disconnect from the tip session.

4. Reconnect the original Storage Service Processor accessory Tray-to-DSP connections in the Base cabinet when diagnosis is complete.

Using the Special Service Cable for Diagnostics (Expansion Cabinet)Use the special service cable for temporary diagnosis of service issues on 6020s on the Master Cabinet only through the 6020 serial port.


1. Disconnect the RJ-45 cable (530-2990-01) from the DB-9/RJ-45 Adaptor (530-3205-01) from the service serial port of the Storage Service Processor accessory tray.

The other end of this cable should remain connected to the MIC (in slot 5) port.

2. Connect the RJ-45 cable (530-3138-01) to the serial port of the 6020 in the Expansion rack that requires diagnosis.

The serial port on the 6020 is the right-most RJ-45 receptacle on the 6020 controller.

The 530-3138-01 cable allows a 10 meter cable run length between the Master and Expansion cabinets. It is stored in the Expansion Cabinet.

3. Connect the other end of this cable (530-3138-01) to the Service Serial port of the Storage service Processor accessory tray in the Base cabinet.

4. Change the baud rate to 9600 to facilitate access to the 6020 array:

ntc0: logout

ntc0: ~.



a. Establish a serial connections to the NTC.

b. Set the baud rate from the ntc0: prompt.

c. When the service action is complete, log out of the NTC.

d. Disconnect from the tip session.

5. Reconnect the original Storage Service Processor accessory try-to-DSP connections in the Base cabinet when diagnosis is complete.



ntc0: logout

ntc0: ~.





APPENDIX A

Connecting SAN and DAS Hosts and Allocating Ports

This appendix describes making SAN and DAS host connections and describes how to allocate ports. It contains the following sections:

■ “About Connecting Hosts” on page 281

■ “Connecting Hosts to a SAN” on page 282

■ “Connecting DAS Hosts” on page 284

■ “Selecting Ports for Additional Host Connections” on page 284

■ “Selecting Ports for Additional Storage Connections” on page 286

About Connecting HostsThe method you use to connect data hosts depends on how the customer plans to use the system. The Sun StorEdge 6920 system supports both storage area network (SAN) and direct attached storage (DAS) configurations for host-side server connections.

Redundant Fibre Channel (FC) ports located on the two I/O panels of the service panel are reserved for data host connections. A system can be configured for 16 FC or 32 FC ports. A 16 FC port configuration includes two storage resource card (SRC) sets, each consisting of two SRC processor cards and two storage I/O (SIO) cards. Additional FC ports can be added to the system by installing additional SRC sets.

With a 16 FC port configuration, use the four leftmost ports (ports 1 through 4) of the lower I/O panel to connect data hosts. The four rightmost ports (ports 5 through 8) are connected to arrays in the system.

281


Ports connections are typically evenly allocated between data hosts and arrays. However, you can allocate additional ports for either host or array connections, depending on the needs at your site. If you need additional ports for array connections, refer to “Selecting Ports for Additional Storage Connections” on page 286 for guidelines. If you need additional ports for host connections, refer to “Selecting Ports for Additional Host Connections” on page 284 for guidelines.

Note – If you allocate more than half of the available ports for SAN or DAS hosts, an additional 1-meter LC-to-SC cable for each HBA port is required to physically connect the DSP to the service panel.

Connecting Hosts to a SANFIGURE 15-13 shows a sample configuration of data hosts connected to external SAN FC switches from redundant ports 1 through 4 of the lower I/O panel.



FIGURE 15-13 Connecting Hosts to a SAN

For more information about the allocation of I/O ports for SAN and DAS hosts, go to online help. Click the Search tab and type FC ports.

LAN

SP LANOUTSERVICE

PROCESSORPANEL

SP LANIN

USERLAN AUX

SERVICESERIAL


PWR SEQUENCER

OUT FRONT

OUT REAR

EXP 1FC1

AFC2

EXP ENET 1

I/O EXP ENET 2

ANPORT 1

B

2 3 4 5 6 7 8

EXP 2FC1

BFC2

I/O CNPORT 1

D

2 3 4 5 6 7 8

Fibre Channel Switches

Data Host Servers

Management Console

Appendix A Connecting SAN and DAS Hosts and Allocating Ports 283


Connecting DAS HostsThe Sun StorEdge 6920 system supports direct attached storage (DAS), allowing data hosts to connect directly to storage. FIGURE 15-14 shows an example of data hosts connected directly to the Sun StorEdge 6920 system.

FIGURE 15-14 Connecting Hosts Directly

Selecting Ports for Additional Host ConnectionsPorts in the columns marked 1, 2, 3, and 4 are specifically for host connections. (see FIGURE A-1). If you need to allocate more ports for host attachment, select ports as follows:

■ Take additional ports from right to left and top to bottom.

LAN

SP LANOUTSERVICE

PROCESSORPANEL

SP LANIN

USERLAN AUX

SERVICESERIAL


PWR SEQUENCER

OUT FRONT

OUT REAR

EXP 1FC1

AFC2

EXP ENET 1

I/O EXP ENET 2

ANPORT 1

B

2 3 4 5 6 7 8

EXP 2FC1

BFC2

I/O CNPORT 1

D

2 3 4 5 6 7 8

Management Console

Data Host Servers



That is, once you have used all ports in columns 1 through 4, use the topmost available port in column 5 and work your way down that column. If necessary, go to column 6 and use ports from top to bottom, and so on.

■ You cannot use ports in column 8 for host connections.

FIGURE A-1 Selecting Additional Ports for Host Connections

Ports for Host Connections

Two Additional Host (HBA Port) Connections in Column 5

123678 45



Selecting Ports for Additional Storage ConnectionsPorts in the columns marked 8, 7, 6, and 5 are specifically for storage connections. (see FIGURE A-2). If you need to allocate more ports for storage attachment, you need to connect ports as follows:

■ Take additional ports from left to right and top to bottom.

That is, once you have used all ports in columns 8 through 5, use the topmost available port in column 4 and work your way down that column. If necessary, go to column 3 and use ports from top to bottom, and so on.

■ You cannot use ports in column 1 for storage connections.



FIGURE A-2 Selecting Additional Storage Connection Ports

Ports for Storage Connections

Two Additional Storage Connections in Column 4

123678 45





APPENDIX B

Unconfiguring and Restoring the Service Processor Configuration

This appendix describes how to unconfigure and restore the Service Processor configuration. It contains the following sections:

■ “Unconfiguring the Service Processor” on page 289

■ “Restoring the Service Processor Configuration” on page 294

At times, you may need to either unconfigure or restore the configuration using the Initial Configuration Utility. For instance,

■ When replacing the spay tray, if the restore command fails, you need to unconfigure, then restore the configuration.

■ If the Storage Service Processor has a hard disk crash, or something similar, you need to restore the configuration.

■ If you need to bring the Service Processor back to a default shipping configuration, you need to unconfigure it.

Unconfiguring the Service ProcessorFollow these steps to unconfigure the Service Processor.

Note – If the Service Processor is connected to a group of Service Processors on an SP-LAN, disconnect the Service Processor from the group before performing the Unconfigure operation.

289


1. Log in to the Sun StorEdge 6920 system internal Network Terminal Concentrator (NTC), as follows:

2. At the ntc0: prompt, connect to the service storage processor console port, as follows:


# login: rssPassword: sun1rss


Type HELP at the ntc0: prompt for assistance ntc0:If a mistake is entered during this procedure, type resume at the ntc0 prompt.

ntc0:connect local port_2

Local protocol emulation 1.0 - Local Switch:< >.

Sun StorEdge 6920 Service Processor WARNING: This is a restricted access server: If you do not have explicit permission to access this server, please disconnect immediately. Unauthorized access to this system is an actionable offense and will be prosecuted to the fullest extent of the law.

new_sp console login:

new_sp console login: setup Password: !setup

Last login: Tue Mar 16 15:35:32 on console Mar 16 15:47:11 new_sp login:ROOT LOGIN /dev/console Tue Mar 16 15:47:12 PST 2004*************************************** StorEdge 6920 Initial Configuration Utility ***************************************Select the operation you wish to perform: 1. Initial configuration 2. Restore previously defined configuration 3. Unconfigure 4. Enable SW Support for Lights Out Operation Your Choice:



4. Select operation number three (3).

The following output appears.

5. Enter y.

The following output appears as the Service processor is unconfigured.

************************************************ Setting StorEdge 6x20 to Unconfigured State ************************************************Performing this operation will reset you network configuration to manufacturing defaults.Are you sure you wish to perform this operation? (Y/N) y

Appendix B Unconfiguring and Restoring the Service Processor Configuration 291


******************************************* Performing StorEdge 6x20 Configuration *******************************************Running step 1 of 12...Updating time zone...Updating system date and time...

New date and time: Sat Jan 1 00:00:00 GMT 2000syslog service starting.WBEM Service StoppingWBEM Service StartingShutting down Sun(TM) Web Console Version 2.0.2...Starting Sun(TM) Web Console Version 2.0.2...See /var/log/webconsole/console_debug_log for server logging informationSuccessfully Completed.

Running step 2 of 12...Updating SP network settings ...Successfully Completed.

Running step 3 of 12...Setting hostname and host files...Successfully Completed.

Running step 4 of 12...Updating firewall configuration...NOTE: Successful execution of this operation takes several minutes!Please be patient...Return Code (0) : Successful completion

Running step 5 of 12...Updating default route...Successfully Completed.

Running step 6 of 12...Updating file resolv.conf...Successfully Completed.

Running step 7 of 12...Restarting sendmail...Successfully Completed.

Running step 8 of 12...Restarting se6000...Requesting WBEM And Tomcat Services To Be RestartedPlease Wait...Jan 1 00:01:58 sp0 dmfe: NOTICE: dmfe0: PHY 1 link downWBEM And Tomcat Services Have Been RestartedSuccessfully Completed.



Running step 9 of 12...Updating DSP configuration...Sending output to nohup.out

Running step 10 of 12...Updating Rasagent configuration...Sending output to nohup.out

Running step 11 of 12...Updating Crontab...

Running step 12 of 12...Updating NTC configuration...NOTE: Successful execution of this operation takes several minutes! Please Wait....Return Code (0) : Successful completionNOTE: The NTC Configuration was successful. The NTC will be reinitialized in less than two minutes. Please press "Enter" when prompted in order to proceed with configuration, then log off. Disconnect from the NTC, and wait approximately two minutes before reconnecting. If the following network verification is successful, you may begin other configuration tasks.

Successfully Completed.

************************************************************************** **** Attention: This product supports remote monitoring capability. **** Please consult the installation guide or contact **** your Sun service representative for more information **** ***********************************************************************Press enter to continue....



6. Press Enter.

The Service Processor unconfigure is complete.

Restoring the Service Processor ConfigurationWhen you restore the service processor configuration, you are restoring it to: Follow these steps to unconfigure the Service Processor.

1. Log in to the Sun StorEdge 6920 system internal Network Terminal Concentrator (NTC), as follows:

|-----------------------------------------------------------------|| This system is for the use of authorized users only. || Individuals using this computer system without authority, or in || excess of their authority, are subject to having all of their || activities on this system monitored and recorded by system || personnel. || || In the course of monitoring individuals improperly using this || system, or in the course of system maintenance, the activities || of authorized users may also be monitored. ||| Anyone using this system expressly consents to such monitoring || and is advised that if such monitoring reveals possible || evidence of criminal activity, system personnel may provide the || evidence of such monitoring to law enforcement officials. ||-----------------------------------------------------------------|

new_sp console login: root

# login: rssPassword: sun1rss


Type HELP at the ntc0: prompt for assistance ntc0:If a mistake is entered during this procedure, type resume at the ntc0 prompt.



2. At the ntc0: prompt, connect to the service storage processor console port, as follows:


ntc0:connect local port_2

Local protocol emulation 1.0 - Local Switch:< >.

Sun StorEdge 6920 Service Processor WARNING: This is a restricted access server: If you do not have explicit permission to access this server, please disconnect immediately. Unauthorized access to this system is an actionable offense and will be prosecuted to the fullest extent of the law.

new_sp console login:

new_sp console login: setup Password: !setup

Last login: Tue Mar 16 15:35:32 on console Mar 16 15:47:11 new_sp login:ROOT LOGIN /dev/console Tue Mar 16 15:47:12 PST 2004*************************************** StorEdge 6920 Initial Configuration Utility ***************************************Select the operation you wish to perform: 1. Initial configuration 2. Restore previously defined configuration 3. Unconfigure 4. Enable SW Support for Lights Out Operation Your Choice:2



4. Select option number two (2).

The following output appears:

5. Press Enter.

Output continues as follows:

****************************************** Restoring StorEdge 6x20 Configuration ******************************************Performing this operation will restore your prior configurationand then test the validity of your StorEdge 6x20 network settings.Are you sure you wish to perform this operation? (Y/N) yRestoring StorEdge 6x20 Configuration.Please wait...Running step 1 of 1...Restore Command SuccessfulRestoring StorEdge 6x20 Configuration was SuccessfulUpdating Rasagent configuration...Sending output to nohup.out

Press enter to continue....

Configuration restored from flash - rebootingApr 26 15:36:50 sp1 reboot: rebooted by setupApr 26 15:36:50 sp1 syslogd: going down on signal 15|-----------------------------------------------------------------|| This system is for the use of authorized users only. || Individuals using this computer system without authority, or in || excess of their authority, are subject to having all of their || activities on this system monitored and recorded by system || personnel. || || In the course of monitoring individuals improperly using this || system, or in the course of system maintenance, the activities || of authorized users may also be monitored. || || Anyone using this system expressly consents to such monitoring || and is advised that if such monitoring reveals possible || evidence of criminal activity, system personnel may provide the || evidence of such monitoring to law enforcement officials. ||-----------------------------------------------------------------|

sp1 console login: Apr 26 15:36:51 rpcbind: rpcbind terminating on signal.syncing file systems... done



rebooting...ResLOM event: +146d+0h38m4s host resetting ...Sun Fire V100 (UltraSPARC-IIe 548MHz), No KeyboardOpenBoot 4.0, 512 MB memory installed, Serial #53852780.Ethernet address 0:3:ba:35:ba:6c, Host ID: 8335ba6c.

Executing last command: boot Boot device: disk File and args:SunOS Release 5.9 Version Generic 64-bitCopyright 1983-2002 Sun Microsystems, Inc. All rights reserved.Use is subject to license terms.configuring IPv4 interfaces: dmfe0 dmfe1.Hostname: sp1The system is coming up. Please wait.starting rpc services: rpcbind done.Setting netmask of dmfe0 to 255.255.255.0Setting default IPv4 interface for multicast: add net 224.0/4: gateway sp1syslog service starting.Starting Sun(TM) Web Console Version 2.0.2...See /var/log/webconsole/console_debug_log for server logging information/opt/SUNWstade/apache/bin/apachectl startssl: apache startedhttpd starting.volume management starting.SLPD StartingWBEM Service StartingWaiting For WBEM Service To Establish CommunicationsSetting SLP IP Address 10.8.87.189Sending output to nohup.outStarting 6020 RNID configuration agentStarting DSP RNID configuration agentThe system is ready.

|-----------------------------------------------------------------|| This system is for the use of authorized users only. || Individuals using this computer system without authority, or in || excess of their authority, are subject to having all of their || activities on this system monitored and recorded by system || personnel. || || In the course of monitoring individuals improperly using this || system, or in the course of system maintenance, the activities || of authorized users may also be monitored. ||



Anyone using this system expressly consents to such monitoring || and is advised that if such monitoring reveals possible || evidence of criminal activity, system personnel may provide the || evidence of such monitoring to law enforcement officials. ||-----------------------------------------------------------------|

sp1 console login:



APPENDIX C

Solution Extract from the Command Line

This appendix describes how to run the extractor from the command line, or from the Storage Automated Diagnostics Environment. It also explains how to view the contents of the solution extract file. It contains the following sections:

■ “Running Solution Extract from the CLI” on page 299

■ “Running Solution Extract from Storage Automated Diagnostic Environment” on page 303

Running Solution Extract from the CLIFollow these steps to run solution extract from the command line:

1. Change to the following directory:

[sp1]# /opt/SUNWstade/sysbin

2. Run the following command:

[sp1]# ./se_extract -r -d 2 -b

This creates a directory called Solution in the following location: /opt/SUNWstade/DATA/Download. Within this directory, the following files are created:■ extract_6920.8335ba6c_2004-04-27_110338.tar■ Extract_log.txt■ Extract.tar■ log_6920.8335ba6c_2004-04-27_110338.txt

299


Note – Note: The date and MAC address will correlate to your specific Service Processor.

Viewing the Contents of the Extract FileTo view the contents, you must un-tar the extract_6920.8335ba6c_2004-04-27_110338.tar file and then view the contents of the subdirectories for each component.

The following subdirectories are created as a result of un-packing the extract_6920.8335ba6c_2004-04-27_110338.tar file:

[sp1]# cd extract_6920.8335ba6c_2004-04-27_110338 [sp1]# lsArrays PatchPro StoradeDSP Rack Switchesextract_log.txt Sp Ves



▼ To View Array-Specific Information● View the list of array commands that are captured as a result of the extract:

[sp1]# cd Arrays[sp1]# lsarray00 array01[sp1]# cd array00[sp1]# lscommands files[sp1]# cd files[sp1]# lscmdlog properties syslogcmdlog.OLD properties.backup syslog.OLD[sp1]# cd ../commands[sp1]# lsarp__a id_read_u2date id_read_u2b1_devtree_1 id_read_u2b2_devtree_2 id_read_u2c1_disk_glist_u1d1_14 id_read_u2l1_disk_glist_u2d1_14 id_read_u2l2_disk_harderr_u1d1_14 id_read_u2pcu1_disk_harderr_u2d1_14 id_read_u2pcu2_disk_linkstat_u1d1_14_path_0 logger__dmprstlogdisk_linkstat_u1d1_14_path_1 _loop_stat_disk_linkstat_u2d1_14_path_0 ls__l_disk_linkstat_u2d1_14_path_1 ls__l_etc

Appendix C Solution Extract from the Command Line 301


▼ To View DSP-Specific Information● View the list of DSP commands that are captured as a result of the extract:

_disk_pathstat_u1d1_14 ls__l_web_disk_pathstat_u2d1_14 lun_map_list_disk_plist_u1d1_14 lun_perm_list_disk_plist_u2d1_14 lun_wwn_list_disk_softerr_u1d1_14 netstat__airs_disk_softerr_u2d1_14 ntp_disk_tmon_list_u1d1_14 ntp_stats_disk_tmon_list_u2d1_14 ntp__vdisk_version_u1d1_14 port_listdisk_version_u2d1_14 port_listmapdu__a proc_listdu__s refresh__s_ep_info route__rfru_list savecore_listfru_myuid setfru_stat _setfru_statistic sys_fc_speedfru_stat_sys sys_fc_topologyhwwn_list sys_listhwwn_listgrp _sys_listid_read_u1 sys_statid_read_u1b1 tzsetid_read_u1b2 verid_read_u1c1 vol_listid_read_u1l1 vol_modeid_read_u1l2 volslice_listid_read_u1pcu1 vol_statid_read_u1pcu2

[sp1]# cd DSP[sp1]# lsdsp00[sp1]# cd dsp00[sp1]# ls

PCRASH.TXT show_support STARTUP.LOG



▼ To View Storage Automated Diagnostic Environment-Specific Information

● View the list of Storage Automated Diagnostic Environment commands that are captured as a result of the extract:

▼ To View Service Processor-Specific Information● View the list of Service Processor commands that are captured as a result of the

extract:

Running Solution Extract from Storage Automated Diagnostic EnvironmentFollow these steps to run solution extract from Storage Automated Diagnostic Environment:

1. Log in to Storage Automated Diagnostic Environment.

2. Select Monitor > Utilities > Solution Extract.

3. If you have an array password, enter it; if not, go to the next step.

[sp1]# cd Storade[sp1]# lsEvents.log ras_admin_device_list ras_admin_topo_MASTERMODEL_6920 ras_admin_email_list ras_admin_topo_sp1OLD_REPORTS ras_admin_provider_list rasagent.conf

pkginfo_SUNWstade ras_admin_site_info showrev_SUNWstade

[sp1]# cd Sp [sp1]# ls_k messages pkginfo_l service sysconfiginetd.conf netinfo ps_ef showrev_p

Appendix C Solution Extract from the Command Line 303


4. Click Start Extract.

This creates a file that can be downloaded and unpacked. Once you download and

unpack the file, you can view all files as described in “Viewing the Contents of the Extract File” on page 300.



APPENDIX D

Storage Profiles

This appendix provides several tables which describe:

■ Attributes and best applications for each RAID level (TABLE D-1).

■ Attributes and applications for typical factory storage profiles (TABLE D-2).

■ Attributes and applications for custom storage profiles for corner cases (TABLE D-3).

■ Guidelines for creating storage profiles (TABLE D-4).

TABLE D-1 RAID Level Descriptions

RAIDLevel

DataProtection

DataLayout

ReadPerformance

WritePerformance

Best for ApplicationWorkload Characteristic:

RAID 0 None Striped across all HDDs

Read from all HDDS simultaneously

No Penalty Sequential, Reads or Writes

RAID 1 Mirroring Entire file on one HDD; file may span HDDs

Read from either HDD in pair

2X Write Penalty

HA Random, Heavy Writes

RAID 1+0 Mirroring Striped across adjacent HDDs

Read file blocks from 2 adjacent HDDs

2X Write Penalty

HA Random or Sequential, Heavy Writes

RAID 5 Parity Striped across all HDDs

Read from all HDDS simultaneously

4X Write Penalty

HA Random or Sequential, Reads

305


TABLE D-2 Factory Storage Profiles for Most Cases

ProfileName

Read/WriteRatio

RAIDLevel

StripeDepth

Segm.Size

StripeSize

ReadAhead

Min.HDD rpm Application Example(s)

Default Varies 5 Variable 64K 1MB ON 10K -------------

Sequential Varies 5 Variable 64K N/A(concatenated)

ON 10K Read: DSS, Edge Servers, financial services, home directories.Write: Point-of-service, process control

HPC Varies 5 Variable 64K N/A(concatenated)

ON 10K Digital simulation (oil & gas exploration, fluid dynamics, weather mapping); real-time data stream ingest/processing, video production operations

NFS-

Striping

Varies 5 Variable 64K 2MB ON 10K File sharing

Random 5 70/30 -35/65

5 Variable 64K 2MB ON 15K Mail spool, metadata, OLTP database

Random 1 70/30 -35/65

5 Variable 64K 2MB ON 15K Mail spool, metadata, OLTP database

Oracle DSS 80/20 5 Variable 64K 2MB ON 10K DSS (Data Warehouse or Data Mart)

Sybase

DSS

80/20 5 Variable 64K 2MB ON 10K DSS (Data Warehouse or Data Mart)

Oracle

OLTP

70/30 5 Variable 64K 1MB ON 15K Financials, SAP, Online order taking

Sybase OLTP

70/30 5 Variable 64K 1MB ON 15K Financials, SAP, Online order taking

Mail

Spooling

35/65 1+0 Variable 64K 2MB ON 10K Exchange, Netscape



* Turn off only if no other storage profile requiring Read Ahead On is on the same controller pair.

NFS-Mirroring

Varies 1+0 Variable 64K 2MB ON 10K File sharing

Oracle

OLTP HA

70/30 1+0 Variable 32K 1MB ON 15K Financials, SAP, Online order taking

Sybase

OLTP HA

70/30 1+0 Variable 32K 1MB ON 15K Financials, SAP, Online order taking

TABLE D-3 Custom Storage Profiles for Corner Cases

ProfileName

Work-loadType

BlockSize

Read/WriteRatio

RAIDLevel

StripeDepth

Segm.Size

StripeSize

ReadAhead

Min.HDD rpm

Application Example(s)

Sequential Heavy Read

Large 80/20 5 or 1+0

7 orless

64K or more

N/A(concatenated)

ON 10K Decision Support

Sequential Heavy Write

Large 20/80 1+0 7 orless

64K or more

N/A(concatenated)

ON 10K Database Load/Update

Random Heavy Read

Large 80/20 5 or 1+0

7 orless

64K 2MB or more ON 10K HPC

Random Heavy Write

Large 20/80 1+0 7 orless

64K 2MB or more ON 10K HPC

Random Heavy Read

Small 80/20 5 or 1+0

14 ormore

32K or less

1MB or less OFF* 15K OLTP

Random Heavy Write

Small 20/80 1+0 14 ormore

32K or less

1MB or less OFF* 15K OLTP

TABLE D-2 Factory Storage Profiles for Most Cases (Continued)

ProfileName

Read/WriteRatio

RAIDLevel

StripeDepth

Segm.Size

StripeSize

ReadAhead

Min.HDD rpm Application Example(s)

Appendix D Storage Profiles 307


TABLE D-4 General Guideline/Hints for Creating Storage Profiles

ProfileType

Controller Segm. Size

Segment Size Start

Read Ahead Setting

Recommended DSP Stripe Size

DSPPartitioning, Striping and Performance Impacts

MixedRand/Seq

Greater than app. I/O size

64K (Increase from here)

ON 4MB Moderate (avoid partitioning if possible). Random I/Os do not adversely impact performance due to partitioning; sequential I/Os do as hosts I/Os use different partitions (causing disk sector seeks).

Sequential As large as possible

64K (Increase from here)

ON 4MB Minimal. Stripe as much as possible to minimize sector seeks across the HDDs and leverage as many HDD spindles as possible. Do not use more than one virtual disk for more than one virtual volume.

Random > or = to app. I/O size

64K (Increase or decrease)

ON: Large BlockOFF: Small Block

1MB Maximum. Stripe across all virtual HDDs in storage pool. Ensures I/O workload is spread evenly across as many HDDs as possible.



Glossary

A

agent

A Sun StorEdge Automated Diagnostic Environment program that runs on a management host, monitoring its storage elements and diagnosing any problems.

alarm

A warning of an existing or approaching alert. See also event.

alert

A subtype of an event that requires user intervention. The term actionable event often describes an alert. See also event.

array

A disk subsystem, made up of multiple disk drives, that functions as a single large, fast, reliable device. Arrays are designed to provide high performance, high availability, and increased storage capacity. In Sun StorEdge 6320 and 6920 systems, a high-availability (HA) array configuration has multiple storage trays of disk drives.

B

base cabinet

The system’s main cabinet, which contains a Data Services Platform (DSP), trays, a Storage Service Processor, a service panel, power distribution units (PDUs), a USB flash disk, and an Ethernet hub. The base cabinet can be connected to one or two expansion cabinets.

block

The amount of data sent or received by the host per I/O operation; the size of a data unit.

309


C

CLI

Command-line interface. In Sun StorEdge 6920 systems, the command-line interface is available when you install the thin-script client on a management host.

concatenated volume

One of the logical devices that can be constructed through concatenation so that storage capacity is not limited to the actual physical size of an individual disk. You concatenate multiple disks to form a volume. You use a concatenated volume to store a large file or file system that spans more than one disk.

concatenation

A storage allocation method in which sequential blocks on a disk are linked together as a logical device. This method combines the storage potential of several physical devices. See also striping.

controller tray

A tray with an installed RAID controller. A controller tray is the smallest possible storage array configuration.

controller unit

The card that manages RAID functions and failover characteristics for an array, tray, or group of trays.

control path

The route used for communication of system management information, usually an out-of-band connection.

customer LAN

See site LAN.

D

DAS

See direct access storage (DAS).

data host

Any host that uses the system for storage. A data host can be connected directly to the system or can be connected to an external switch that supports multiple data hosts.

data path

The route taken by a data packet between a data host and the storage device.

310 Storage Automated Diagnostic Environment 2.3 Online H elp • November, 2003


Data Services Platform (DSP)

A dedicated computing system for consolidating and virtualizing storage so that all storage in the system can be managed like a single disk.

dedicated hot spare

A disk that serves as the hot spare for one and only one virtual disk in an array or tray.

direct access storage (DAS)

A storage architecture in which the systems that store data are connected physically to storage elements.

disk

A physical component that stores data. See also virtual disk.

domain

See storage domain.

DSP

See Data Services Platform (DSP).

E

event

A notification of something that happened on a device. There are many types of events, and each type describes a separate occurrence. See also alarm and alert.

expansion cabinet

A cabinet connected to a base cabinet to increase storage capacity. A power management cable connects the service panels on both cabinets, and the Fibre Channel/Ethernet cable connects the I/O panels on both cabinets.

expansion tray

A tray that does not have a RAID controller, used to expand the capacity of an array. This type of tray must be attached to a controller tray to function.

extent

A set of contiguous blocks with consecutive logical addresses on a physical or virtual disk.

Glossary 311


F

failover and recovery

The loss of a data path and the automatic change to an alternate path.

fault coverage

The percentage of faults detected against all possible faults or against all faults of a given type.

FC

See Fibre Channel (FC).

Fibre Channel (FC)

A gigabit serial data-transfer protocol, deployed across a wide range of storage hardware and commonly used for storage area network (SAN) configurations.

Fibre Channel switch

A networking device that can send packets directly to a port associated with a given network address. In the Sun StorEdge 6920 system, FC ports are connected to a data host’s initiators.

field-replaceable unit (FRU)

An assembly component that is designed to be replaced on site, without having to be returned to the manufacturer.

flash card

See USB flash card.

flash disk

See USB flash disk.

FRU

See field-replaceable unit (FRU).

G

GUI

Graphical user interface. In this product, the GUI is based on a web browser.

Back to top



H

HBA

See host bus adapter (HBA).

host bus adapter (HBA)

A controller board that sits between the system’s I/O expansion bus and the Fibre Channel components and that manages low-level data transfers. See also initiator.

host port

A port on the Data Services Platform that connects to a data host. See also storage port.

hot spare

The drive used by a controller to replace a failed disk; a reserve disk that can be made available to all virtual disks within an array.

I

in-band traffic

System management traffic that uses the data path between a host and a storage device. See also out-of-band traffic.

initiator

On a Fibre Channel network, a host that requests transactions with storage elements. Each connection represents a separate initiator, so if a host is connected to the system through two HBAs, the system identifies two different initiators.

I/O panel

See service panel.

IOPS

I/O processors that specialize in interrupt handling, buffering, and data transfer.

L

LAN

Local area network.

logical unit (LUN)

The identifier for a volume as it is recognized by a particular host. The same volume can be represented by a different LUN to a different host.

Glossary 313


LUN

See logical unit (LUN).

LUN mapping

Assigning volume permissions to an initiator.

LUN masking

Filtering the initiators that have access to a particular volume.

M

MAC address

See media access control (MAC) address.

management host

A host with an out-of-band network connection to the system that is used to manage the system. A management host can have monitoring software installed, such as a remote CLI package, Sun StorEdge Enterprise Storage Manager or Sun Storage Automated Diagnostic Environment (Device Edition), or a third-party monitoring program such as Tivoli. A management host can also be used to run management software on another machine through a network connection.

management interface card (MIC)

The card on which the management software resides. Each Data Services Platform has two MICs, which operate in a master/alternate master mode.

master / alternate master

A design for reliability that uses redundant configuration. Array configurations and the management interface cards (MICs) have master/alternate master configurations: each array configuration has two controller trays but only one IP address and name, and the MICs share one IP address and name. In each case, the master component uses the IP address and name. If the master fails, the alternate master assumes the IP address and name and takes over the master’s functions.

media access control (MAC) address

The physical address identifying an Ethernet controller board. The MAC address, also called an Ethernet address, is set at the factory and must be mapped to the IP address of the device.



MIC

See management interface card (MIC).

multipathing

A design for redundancy that provides at least two physical paths to a target.

N

network domain

A LAN that is used for a special purpose such as internal communication. Each storage system can be part of up to three LANs; that is, it can be configured in one of three types of network domains.

NSCC

Network Storage Command Center.

O

out-of-band traffic

System management traffic outside of the primary data path, such as traffic that uses an Ethernet network. See also in-band traffic.

P

PDU

See power distribution unit (PDU).

pool

See storage pool.

power distribution unit (PDU)

The assembly that provides power management for the system. The redundant design uses two PDUs in each system so that the system’s data path continues to function if one of the PDUs fails.

profile

See storage profile.

provisioning

The assignment of applications that use storage to logical storage elements instead of physical elements. The storage administrator can use storage efficiently by assigning resources where needed and when needed.

Glossary 315


R

RAID

Redundant array of independent disks. A configuration in which several drives are combined into a single virtual drive to improve performance and reliability. Also called a RAID set or a RAID group.

RAS

Reliability, availability, and serviceability.

remote monitoring

Monitoring of the functions and performance of a hardware system from a location other than where the hardware resides.

remote support

Direct or indirect troubleshooting, diagnosis, and servicing of hardware from a location other than where the hardware resides.

S

SAN

See storage area network (SAN).

service panel

A single interface used for input and output connections for both control path functions and data path functions. The service panel provides ports for host connections and connections for up to two expansion cabinets.

SES device

SCSI Enclosure Services device. A device that senses and monitors physical conditions within an enclosure and that enables access to the status reporting and configuration features of the enclosure, such as indicator LEDs.

SFC

See switch fabric card (SFC).

SIO card

See storage I/O (SIO) card.

site LAN

The local area network at your site. When the system is connected to your LAN, the system can be managed through a browser from any host on the LAN.



snapshot

A copy of a volume’s data at a specific point in time.

SRC

See storage resource card (SRC).

storage area network (SAN)

An architecture in which the storage elements are connected to each other and to a server that is the access point for all systems that use the SAN to store data.

storage domain

A logical domain with its own storage and its own management environment. When the Data Services Platform is powered on, the DEFAULT storage domain is configured automatically.

storage I/O (SIO) card

A board that provides the physical Fibre Channel ports. This card is always paired with a storage resource card (SRC). See also storage resource card (SRC) set.

storage pool

A collection of disks, virtual disks, or storage extents with a common configuration, availability, and performance that can be divided into volumes.

storage port

A port on the Data Services Platform that connects to the storage system. See also host port.

storage profile

A set of storage pool attributes that optimize the storage pool for a particular access pattern and level of data protection. You assign a profile to a pool to define the attributes of the pool.

storage resource card (SRC)

A board that provides the service processors. An SRC is always paired with an SIO card. See also storage resource card (SRC) set.

storage resource card (SRC) set

Two cards that together provide the Fibre Channel interface: the storage resource card (SRC) and the storage I/O (SIO) card. Two to four SRC sets can be installed to provide the ports for connecting data hosts to the system.

Glossary 317


Storage Service Processor

A device integrated into storage systems to provide unified management access to system components, as well as local and remote management and maintenance. The Storage Service Processor also supports automatic upgrades of patches, firmware, and software.

storage tray

An enclosure containing disks. A tray with a RAID controller is called a controller tray; a tray without a controller is called an expansion tray.

stripe size

The total amount of data in a stripe, representing the block size multiplied by the number of disks in the stripe. See also striping.

striping

A storage allocation method in which data is stored over a series of disks or virtual disks. Because multiple disk controllers can access data simultaneously, striping improves performance. See also concatenation.

Sun StorEdge Remote Response Service (SSRR)

A remote support solution that consists of SRS Net Connect, customizable Sun storage self-management, and around-the-clock system monitoring by Sun.

switch fabric card (SFC)

A board that provides the central switching function for the storage data path.

T

target

The recipient of initiator commands, usually a volume.

thin-scripting client

A client that runs the system’s command-line interface on any host in the network. The client communicates with the system’s Storage Service Processor through a secure out-of-band interface, HTTPS. The client must be installed on a host that has network access to the system. The available clients are for the Solaris, Microsoft Windows 2000 and Windows 2003, Linux, HP-UX, and IBM AIX operating environments.

tray

See storage tray.



U

USB flash card

The resident card on which the Data Services Platform’s configuration information is stored.

USB flash disk

The resident disk on which the Storage Service Processor’s configuration information is stored. You can move the disk into a new Storage Service Processor if the current one must be replaced.

V

virtual disk

A collection of disks or extents that acts as one disk. The device that mounts the virtual disk handles the virtual disk as one disk.

virtualization

A design strategy in which storage services are combined with management functions to handle the complexity of storage administration. Instead of administrators configuring a data host to use a specific storage element, a system that uses virtualization allows administrators to assign data hosts’ storage to a storage pool, which coordinates and allocates the storage among available storage elements.

volume

A fixed amount of storage, not limited by the physical device. A disk can have more than one volume, and a volume can span more than one disk. Applications that use volumes do not need to be aware of physical storage locations, because the management software maps the virtual address to the physical address.

W

WWN

Worldwide name.

Glossary 319




Index

NUMERICS6120loop test 20

6120ofdg test 111

6120volverify test 20, 111

AAC power cable, replacing 240

accessing eventsdata services platform 80

storage arrays 110

aggregate event 111

application testing, volume snapshots and 9archive management software 11

array capacity, adding 192

array controller card, replacing 181

array error event 112

array FRUs, replacing 157

array loop card, replacing 184

array system level LEDs 101

arrays 93

arrays. See storage arrays

AUX port, on service panel 5

Bbackup software 11

backups, volume snapshots and 9base cabinet 3battery backup 6boot -r command side effects 41

Ccabinets 4

See also base cabinet, expansion cabinet

cables, for power management 228

cacheMode alarm 112

cfgadm -al command 40

chassis LEDs 69

command-line interface (CLI) 8commands. See individual commands

common problems, power management 265

configtest test 21

configuration software 9configuring

new storage array 176

storage arrays in an expansion cabinet 237

controller card LEDs 107

controller error 113

1


controller trays 6compared with expansion trays 7

controller/device pathreturning to production 97

unconfiguring 97

creatingsolution snapshot 16

storage profiles 308

customer LAN. See site LAN

DDAS. See direct attached storage

data host patches 32

data host softwarerequired 9for Solaris systems 9supported 11

for systems other than Solaris 10

data hostscabling for 4connected directly 284

connected through a SAN 282

connecting 281

ports for 5software for. See data host software

data management software 11

data mining, volume snapshots and 9data paths, redundant 6Data Services Platform (DSP)

boot-up failure on 78

described 5front view 67

location of 3rear view 67

replacing 149

troubleshooting 65

data traffic, software for monitoring 10

device monitoring, software for 10

device path error 114

diagnostic and monitoring software 9diagnostic tests

accessing 21

available from the Storage Service Processor 20

outside the Storage Service Processor 20

running from list 25

running from topology 22

view man page 24

direct attached storage (DAS), data hosts for 281, 284

disk driveLEDs 102

replacing 177

disk error 114

disk log warning 116

disk pathstat error 116

disk port error 117

disk senseKey warning 117

DMP-enabled paths, returning to production 100

driver warning 117

DSP. See Data Services Platform

dynamic multipathing 10, 11

dynamic multipathing (DMP) 97

Eerror discovery 35

ESD precautions 34

Ethernet hubdescribed 5

Ethernet hub, replacing 247

Ethernet ports 5Event Advisor

accessing 110

array information in 109

DSP information in 80



Event Advisor, accessing 56

expansion cabinetadding 224

expansion trays, compared with controller trays 7external modem

adding 274

removing 276

Ffailover capabilities 6fan assembly, replacing 144

fan LEDs 69

FC portsconnecting data hosts to 281

guidelines for allocating 282

on service panel 5, 7Fibre Channel (FC) switching 5field replaceable units

isolating 37

testing 37

field replaceable units. See also individual FRUsfield-replaceable units (FRUs)

accessing 4file management software 11

firewalllocation of 5

firmware, software for upgrading 9format command 40

front AC power cablereplacing 240

front door, replacing 252

front power sequencers, replacing 240

FRU failures, determining 109

FRUs. See field-replaceable units

full remote shutdown 259

GGBICs, replacing 137, 141

graphical user interface (GUI) 8GUI. See graphical user interface

Hhardware. See system hardware

hbamap tool 28

host devicesevents 58

support 55

troubleshooting 55

array error and warning 58

disk capacity warning 58

driver link down warning 58

driver offline warning 59

LUN error 61

MPxIO offline 59

power battery error 62

SSD alert error 60

host events, HBA error 61

host installation CD 9host software. See data host software

HP-UX operating system, supported software for 10

II/O

manually halting 96

quiescing 96

I/O panelslocation of 3

IBM AIX operating system, supported software for 10

installationsadditional storage arrays 174

storage I/O and storage resource card pairs 145

Index 3


Sun StorEdge Traffic Manager 36

VERITAS VxDMP 36

interface loopcard error 118

internal component LAN 7

Jjnitest test 21

Kkey switch, replacing 250

LLAN connections, in service panel 5LEDs

array system level 101

chassis 69

controller card 106, 107

disk drive 102

fan 69

interconnect card 105

location of 3management interface cards 70

NetGear router 45

power and cooling unit 104

power supply 70

storage I/O (SIO) cards 77

storage resource cards (SRCs) 75

lights-out managementabout 256

adding 265

powering off the system with 257, 259

removing 271

restoring the system and 262

linktest test 21

local area networks (LANs)

cabling for 4types of 7

log warning 119

lost communication in-band 118

lost communication out-of-band 119

LUN mapping 95

LUN masking 95

luxadm command 40

luxadm -e dump_map command 40

luxadm -e port command 40

luxadm(1M) command, used to display information 99

Mmanagement console 284

management interface cards (MICs)LEDs 70

location of 3port for 5replacing 130

management software 9Microsoft Windows operating environments

supported software for 10

mirroring, software for 11

modem ports, in service panel 5monitoring and diagnostic software 9MPxIO, tool to map devices 28

multipathing 10, 96

NNetGear router

LEDs 45

network terminal concentratorconnecting to 49

opening serial connection to 49



troubleshooting 49

network terminal concentrator (NTC) 5network traffic, internal 5networks, types of 7

Ppartial remote shutdown 257

restoring the system after 262

patch revisionschecking 29

PFAFC links 12

power and cooling unit battery, replacing 190

power and cooling unit, replacing 186

power battery error 120

power connections 5power error 119

power fan error 120

power sequencer error 121

power sequencerslocation of 3replacing

front 240

rear 245

power suppliesbattery backup 6redundant 6

power supplyLEDs 70

replacing 142

power temperature error 121

power-on sequenceafter full remote power-off 259, 263

after partial remote power-off 262

predictive failure analysis (PFA) 12

Qqlctest test 21

RRAID configurations 95

RAID level descriptions 305

RAID management hardware 7rear AC power cable, replacing 238

rear door, replacing 253

rear power sequencer, replacing 245

recovery software 11

Red Hat Linux operating system, supported software for 10

remote configuration, software for 10

remote management, command-line interface for 8, 10

remote mirroring, software for 11

remote monitoringsoftware for 9, 11

remote power management. See lights-out management

remote power-off sequencefull shutdown in 259

partial shutdown 257

restoring the system after 262

remote serviceto multiple units 127

to a single unit 127

remote service options 127

removal proceduresexternal modem 276

lights-out management 271

replacement proceduresarray controller card 181

array FRUs 157

array loop card 184

Index 5


Data Services Platform chassis and midplane 149

Ethernet hub bracket in expansion cabinet 249

Ethernet hub, main cabinet 247

fan assembly 144

front AC power cable 240

front door 252

front power sequencer 240

GBICs 137, 141

key switch 250

management interface card 130

power and cooling unit 186

power and cooling unit battery 190

power supply 142

rear AC power cable 238

rear door 253

rear power sequencer 245

service panel 218

Service Processor 198

side panel 253

storage array chassis 158

storage array disk drive 177

storage I/O cards 135

storage resource cards 137

switch fabric card 133

USB flash disk 201

USB relay panel 221

required patchesdowloading 32

downloading 33

installing 34

SSAN Foundation kit version, checking 32

SAN management software 11

SANs. See storage area networks

serial connection, network terminal concentrator 49

serial ports, in service panel 5service panel

in base cabinet 3described 5location of 4

service panel, replacing 218

Service Processorreplacing 198

unconfiguring 294

Service Processor panel 3service, remote to multiple units 126

Show IP command 53

Show Port command 54

Show Server command 52

side panel, replacing 253

SIO cards. See storage I/O (SIO) cards

site LAN 7snapshots. See volume snapshotssoftware. See data host software, system software

Solaris driver stack 12

Solaris Operating System, software for extending 11

Solaris Volume Manager software 11

Solstice DiskSuite software 11

solution extractfrom the CLI 19

via Storage Automated Diagnostic Environment 16

viewingarray information 301

contents of file 300

DSP information 302Storage Automated Diagnostics

Environment information 303

Storage Service Processor information 303

solution snapshot 16

SP LAN connection 205

special service cable diagnostics



base cabinet 276

expansion cabinet 278

SRCs. See storage resource cards (SRCs)

sscs commands 8SSP. See Storage Service ProcessorSSRR. See Sun StorEdge Remote Response servicestorage area networks (SANs)

cabling for 4storage area networks (SANs), data hosts in 281

storage array configurationscapacity of 6

storage arraysconfigurations of. See storage array

configurationsconfiguring 176

controller card LEDS 106

described 5description 93

disk drive LEDS 102

features 95

interconnect card LEDS 105

location of 3location of LEDs for 3maximum allowed in expansion cabinet 1power and cooling unit LEDS 104

replacing 158

reviewing LED status 35

status checking 35

supported configurations 94

syslog file 35

troubleshooting 93

unit LEDS 101

Storage Automated Diagnostic Environment application 10, 15

storage I/O (SIO) cardsLEDs 77

replacing 135

storage poolssoftware for managing 9

storage profiles

creating 308

custom 307

factory supplied 305

guidelines for creating 308

RAID level descriptions 305

storage resource cards (SRCs)LEDs 75

replacing 137

storage resource cards (SRCs), accessing 4Storage Service Processor

configuration possibilities 126

described 5description 125

location of 3security 126

troubleshooting 37

unconfiguring 289

Storage Service Processor accessory traycable overview 206

cables used to connect 206

described 5description 126, 204

Storage Service Processor LAN 7storage trays

in array configurations 6Sun Cluster software 11

Sun StorEdge Availability Suite software 11

Sun StorEdge Diagnostic Expert software 11

Sun StorEdge Enterprise Backup software 11

Sun StorEdge Enterprise Storage Manager software 11

Sun StorEdge Performance Suite with Sun StorEdge QFS software 11

Sun StorEdge Remote Configuration CLI 10

Sun StorEdge Remote Response service 5described 9Storage Service Processor LAN and 7

Index 7


Sun StorEdge Remote Response service capabilities 1

Sun StorEdge SAN Foundation software 10

Sun StorEdge Snapshot software 9Sun StorEdge Storage Pool Manager software 9Sun StorEdge Traffic Manager

alternatives to using 96

installations 36

troubleshooting workarounds 96

Sun StorEdge Traffic Manager software 10

Sun StorEdge Utilization Suite with Sun StorEdge SAM-FS software 11

Sun Web Console page 15

supported third-party software 11

SVD_PATH_FAILOVER warning messages 41

switch fabric cards (SFCs)replacing 133

system architecture 3system cabinets 4

See also base cabinet, expansion cabinet

system defaults 256

system hardwarecomponents of 5overview of 3

system monitoring, remote. See remote monitoring

system reboot warning 122

system router, location of 5system software

overview of 8pre-installed 9upgrading 9

Ttemperature threshold error 123

testsfor Sun StorEdge T3+ arrays 37

from list 25

from topology 22

tests. See individual tests

thin-scripting client 8third-party software 11

time difference warning 123

tools, unsupported 28

topology, navigation of window 22

trays. See controller trays, expansion trays, storage trays

Uunconfiguring the Service Processor 294

unit LEDs, storage array 101

USB flash disk, replacing 201

USB relay panel, replacing 221

VVERITAS DMP

installations 36

VERITAS software 11

virtualization services 5virtualization software 9volume error 124

volume management software 11

volume snapshotssoftware for creating 9



Documents

6920 Service Manual