Sun Cluster 3.1 - 3.2 With Sun StorEdge 3510 or 3511 FC RAID Array Manual for Solaris OS

Preface

The Sun Cluster 3.1 - 3.2 With Sun StorEdge 3510 or 3511 FC RAID Array Manual for Solaris OS provides procedures specific to Sun StorEdgeTM 3510 and 3511 FC RAID storage arrays placed in a SunTM Cluster environment.

Use this manual with any version of Sun Cluster 3.1 or 3.2 software on SPARC® based clusters and with any supported version of Sun Cluster 3.1 or 3.2 on x86 based clusters. Unless otherwise noted, procedures are the same for all Sun Cluster 3.1 or 3.2 versions. See the Revision History for a list of changes to this manual.

See the Sun Cluster 3.0-3.1 Release Notes Supplement for current information on bugs or restrictions.


Note –

This Sun Cluster release supports systems that use the SPARC and x86 families of processor architectures: UltraSPARC, SPARC64, and AMD64. In this document, the label x86 refers to systems that use the AMD64 family of processor architectures. The information in this document pertains to both platforms unless otherwise specified in a special chapter, section, note, bulleted item, figure, table, or example.


Who Should Use This Book

This book is for Sun representatives who are performing the initial installation of a Sun Cluster configuration and for system administrators who are responsible for maintaining the system.

This document is intended for experienced system administrators with extensive knowledge of Sun software and hardware. Do not use this document as a planning or a pre-sales guide. You should have already determined your system requirements and purchased the appropriate equipment and software before reading this document.

How This Book Is Organized

Chapter 1, Installing and Maintaining Sun StorEdge 3510 and 3511 Fibre Channel RAID Arrays discusses how to install, configure, and maintain the RAID version of the StorEdge 3510 and 3511 storage arrays.

Revision History

The following table lists the information that has been revised or added since the initial release of this documentation. The table also lists the revision date for these changes.

Table P–1 Sun Cluster 3.1 - 3.2 With Sun StorEdge 3510 or 3511 FC RAID Array Manual for Solaris OS

Revision Date 

New Information 

March 2008 

Replaced outdated information about SunSolve with information about Sun Connection Update Manager.

January 2009 

Updated table in Preface in to include different versions of Sun Cluster documentation. 

Related Documentation

The following books provide conceptual information or procedures to administer hardware and applications. If you plan to use this documentation in a hardcopy format, ensure that you have these books available for your reference.

The following Sun Cluster books support the Sun Cluster 3.1 and 3.2 releases. If you are maintaining a different version of Sun Cluster software, refer to the appropriate documentation. All Sun Cluster documentation is available at http://docs.sun.com. Documentation that is not available at http://docs.sun.com is listed with the appropriate URL.

Table P–2 Hardware Documentation

Title 

Part Number 

Sun StorEdge 3000 Family Installation, Operation, and Service Manual, Sun StorEdge 3510 FC Array

816-7300 

Sun StorEdge 3000 Family RAID Firmware 4.1x User’s Guide

817–3711 

Sun StorEdge 3000 Family Best Practices Manual

816–7325 

Sun StorEdge 3510 FC Array Release Notes

816-7301 

Sun StorEdge 3511 FC Array with SATA Release Notes

817–6597 

Sun StorEdge 3000 Family FRU Installation Guide

816-7326 

Sun StorEdge 3000 Family Rack Installation Guide for 2U Arrays

817-3629 

Table P–3 Sun Cluster Documentation

Documentation 

Solaris Cluster 3.2

Sun Cluster 3.1

Using UNIX Commands

This document contains information about commands that are used to install, configure, or upgrade a Sun Cluster configuration. This document might not contain complete information about basic UNIX® commands and procedures such as shutting down the system, booting the system, and configuring devices.

See one or more of the following sources for this information:

Getting Help

If you have problems installing or using Sun Cluster, contact your service provider and provide the following information.

Use the following commands to gather information about your system for your service provider.

Command 

Function 

prtconf -v

Displays the size of the system memory and reports information about peripheral devices 

psrinfo -v

Displays information about processors 

showrev -p

Reports which patches are installed 

prtdiag -v

Displays system diagnostic information 

/usr/cluster/bin/clnode show-rev/usr/cluster/bin/scinstall -pv

Displays Sun Cluster release and package version information 

Also have available the contents of the /var/adm/messages file.

Documentation, Support, and Training

The Sun web site provides information about the following additional resources:

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. To share your comments, go to http://docs.sun.com and click Feedback.

Typographic Conventions

The following table describes the typographic conventions that are used in this book.

Table P–4 Typographic Conventions

Typeface 

Meaning 

Example 

AaBbCc123

The names of commands, files, and directories, and onscreen computer output 

Edit your .login file.

Use ls -a to list all files.

machine_name% you have mail.

AaBbCc123

What you type, contrasted with onscreen computer output 

machine_name% su

Password:

aabbcc123

Placeholder: replace with a real name or value 

The command to remove a file is rm filename.

AaBbCc123

Book titles, new terms, and terms to be emphasized 

Read Chapter 6 in the User's Guide.

A cache is a copy that is stored locally.

Do not save the file.

Note: Some emphasized items appear bold online.

Shell Prompts in Command Examples

The following table shows the default UNIX system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell.

Table P–5 Shell Prompts

Shell 

Prompt 

C shell 

machine_name%

C shell for superuser 

machine_name#

Bourne shell and Korn shell 

$

Bourne shell and Korn shell for superuser 

#