Sun Microsystems StorEdge Availability Suite 3.2 User Manual

Sun StorEdge

™

Availability Suite 3.2 Software

Troubleshooting Guide

Sun Microsystems, Inc. www.sun.com

Part No. 817-3752-10 December 2003, Revision 51

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

Copyright© 2003 Sun Microsystems,Inc.,4150NetworkCircle,SantaClara,California95054,U.S.A.Allrightsreserved. Sun Microsystems,Inc.hasintellectualpropertyrightsrelatingtotechnologyembodiedinthisproduct.Inparticular,andwithoutlimitation,

these intellectual propertyrightsmayincludeoneormoreoftheU.S.patentslistedathttp://www.sun.com/patentsandoneormore additional patents or pending patent applications in the U.S.andinothercountries.

This document and the producttowhichitpertainsaredistributedunderlicensesrestrictingtheiruse,copying,distribution,and decompilation. No part of the productorofthisdocumentmaybereproducedinanyformbyanymeanswithoutpriorwrittenauthorizationof Sun and its licensors, if any.

Third-partysoftware,includingfonttechnology,iscopyrightedandlicensedfromSunsuppliers. Parts of the productmaybederivedfromBerkeleyBSDsystems,licensedfromtheUniversityofCalifornia.UNIXisaregistered trademark in

the U.S. and in other countries, exclusively licensedthroughX/OpenCompany,Ltd. Sun, Sun Microsystems,theSunlogo,AnswerBook2,docs.sun.com,SunStorEdge,andSolarisaretrademarksorregisteredtrademarksofSun

Microsystems,Inc.intheU.S.andinothercountries. All SPARC trademarks are used under license and aretrademarksorregisteredtrademarksofSPARCInternational,Inc.intheU.S.andinother

countries. ProductsbearingSPARC trademarks are based upon anarchitecturedevelopedbySunMicrosystems,Inc. The Adobe® logo is a registeredtrademarkofAdobeSystems,Incorporated. U.S. Government Rights—Commercialuse.GovernmentusersaresubjecttotheSunMicrosystems,Inc.standardlicenseagreement and

applicable provisionsoftheFAR and its supplements. ProductscoveredbyandinformationcontainedinthisservicemanualarecontrolledbyU.S.ExportControl laws and may be subject to the

export or import laws in other countries. Nuclear,missile,chemicalbiologicalweaponsornuclearmaritimeendusesorendusers,whether director indirect, are strictly prohibited. Export or reexportto countries subject to U.S. embargo or to entities identiﬁed on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals list is strictly prohibited.

DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTYOF 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© 2003 Sun Microsystems,Inc., 4150 Network Circle, Santa Clara, Californie 95054, Etats-Unis. Tousdroits réservés. 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 droitsde propriété intellectuels peuvent inclure un ou plus des brevets américains énumérés à http://www.sun.com/patentset un ou les brevets plus supplémentaires ou les applications de brevet en attente dans les Etats-Unis et dans les autres pays.

Ce produitou 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 ena.

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, Sun StorEdge, 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 SPARCsont utilisées sous licence et sont des marquesde fabrique ou des marques déposées de SPARCInternational, Inc. aux Etats-Unis et dans d’autres pays. Les produits protant les marques SPARCsont basés sur une architecturedéveloppée par Sun Microsystems,Inc.

Ce produitest soumis à la législation américaine en matière de contrôle des exportations et peut être soumis à la règlementation en vigueur dans d’autrespays dans le domaine des exportations et importations. Les utilisations, ou utilisateurs ﬁnaux, pour des armes nucléaires, des missiles, des armes biologiques et chimiques ou du nucléaire maritime, directement ou indirectement, sont strictement interdites. Les exportations ou réexportations vers les pays sous embargo américain, ou vers des entités ﬁgurant sur les listes d’exclusion d’exportation américaines, y compris, mais de manière non exhaustive, la liste de personnes qui font objet d’un ordrede ne pas participer,d’une façon directe ou indirecte,aux exportations des produits ou des services qui sont régis par la législation américaine sur le contrôle des exportations et la liste de ressortissants spéciﬁquement désignés sont rigoureusement interdites.

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

Please

Recycle

Contents

Preface v

1. Point-in-Time Copy Software Troubleshooting Tips 1

Troubleshooting Checklist 1 Checking Log Files 2 Improving Performance 2 Safeguarding the VTOC Information 3

2. Remote Mirror Software Troubleshooting Tips 5

Troubleshooting Checklist 6 Troubleshooting Log Files and Services 6

Checking Log Files 7 Checking the /etc/nsswitch.conf File 8 Checking That the rdc Service Is Running 8 If the /dev/rdc Link Is Not Created 9

Checking the Integrity of the Link 10

Testing with ifconfig 11 Testing with ping 11 Testing with snoop and atmsnoop 11

iii

Correcting Common User Errors 13

Enabled Software on Only One Host 13 Volumes Are Inaccessible 13 Wrong Volume Set Name Specified 14

Accommodating Memory Requirements 16

3. Error Messages 19

iv Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003

Preface

Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide helps users solve common problems that might arise when using the Sun StorEdge™ Availability Suite 3.2 software.

Before You Read This Book

To use the information in this document, you must have thorough knowledge of the topics discussed in these books:

■ Sun StorEdge Availability Suite 3.2 Point-in-Time Copy Software Administration and

Operations Guide

■ Sun StorEdge Availability Suite 3.2 Remote Mirror Software Administration and

Operations Guide

How This Book Is Organized

This book includes the following chapters:

Chapter 1 helps to solve problems associated with the point-in-time copy software. Chapter 2 helps to solve problems associated with the remote mirror software. Chapter 3 provides an alphabetical list of error messages from all sources associated

with the Sun StorEdge Availability Suite software.

Using UNIX Commands

This document might not contain information on basic UNIX®commands and procedures such as shutting down the system, booting the system, and configuring devices. See the following for this i nformation:

■ Software documentation that you received with your system

■ Solaris™ operating environment documentation, which is at

http://docs.sun.com

vi Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003

Shell Prompts

Shell Prompt

C shell machine-name% C shell superuser machine-name# Bourne shell and Korn shell $ Bourne shell and Korn shell superuser #

Typographic Conventions

Typeface

AaBbCc123 The names of commands, files,

AaBbCc123

AaBbCc123 Book titles, new words or terms,

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

Meaning Examples

and directories; on-screen computer output

What you type, when contrasted with on-screen computer output

words to be emphasized. Replace command-line variables with real names or values.

Edit your.login file. Use ls -a to list all files.

% You have mail. % su

Password:

Read Chapter 6 in the User’s Guide. These are called class options. You must be superuser to do this. To delete a file, type rm filename.

Preface vii

Point-in-Time Copy Software Troubleshooting Tips

This chapter describes how to avoid or troubleshoot problems that might occur when using the point-in-time copy software.

The chapter includes the following topics:

■ “Troubleshooting Checklist” on page 1

■ “Checking Log Files” on page 2

■ “Improving Performance” on page 2

■ “Safeguarding the VTOC Information” on page 3

Troubleshooting Checklist

This table shows the t roubleshooting checklist and related sections.

TABLE1-1 Troubleshooting Checklist

Step For Instructions

1. Check for installation errors. Sun StorEdge Availability Suite 3.2 Software Installation Guide

2. Check that /dev/ii is created after

reboot.

3. Check the log file contents. “Checking Log Files” on page 2

Sun StorEdge Availability Suite 3.2 Software Installation Guide

Checking Log Files

You can check the status of the point-in-time copy software by examining two system log files:

■ /var/opt/SUNWesm/ds.log

The /var/opt/SUNWesm/ds.log file contains timestamped messages about the point-in-time copy software, including error messages and informational messages. For example:

Mar 05 15:56:16 scm: scmadm cache enable succeeded Mar 05 15:56:16 ii: iiboot resume cluster tag <none>

■ /var/adm/messages

The /var/adm/messages file contains timestamped messages about the point-in-time copy software, including general system error and informational messages. For example:

Mar 5 16:21:24 doubleplay pseudo: [ID 129642 kern.info] pseudo-device: ii0 Mar 5 16:21:24 doubleplay genunix: [ID 936769 kern.info] ii0 is /pseudo/ii@0

Improving Performance

If the Sun StorEdge Availability Suite software is used with a filesystem, tuning the number of SV threads might produce better performance.

When a filesystem flushes its cache, it generates many parallel write operations. The SV’s default setting of 32 threads could produce a bottleneck. You can increase the number of SV threads. The maximum number of threads allowed is 1024.

Note – Each thread consumes 32k of memory.

The sv_threads value is in the /usr/drv/conf/sv.conf file. Because the file is read when a module loads, changes to the sv_threads value do not take effect until you reboot the system.

2 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003

Safeguarding the VTOC Information

Caution – When creating shadow volume sets, do not create shadow or bitmap

volumes using partitions that include cylinder 0. Data loss might occur.

The Solaris system administrator must be knowledgable about the virtual table of contents (VTOC) that is created on raw devices by the Solaris operating system. The creation and updating of a physical disk’s VTOC is a standard function of the Solaris operating system. Software applications like t he Sun StorEdge Availability Suite, the growth of storage virtualization, and the appearance of SAN-based controllers have made it easy for an uninformed Solaris system administrator to allow a VTOC to be altered inadvertently. Altering the VTOC increases the possibility of data loss.

Remember these points about the VTOC:

■ A VTOC is a software-generated virtual table of contents based on the geometry

of a device and written to the first cylinder of that device by the Solaris format(1M) utility.

■ Various software components such as dd(1M), backup utilities, point-in-time copy

software, and remote mirror software can copy the VTOC of one volume to another volume if that volume includes cylinder 0 in its mapping.

■ If the VTOC of the source and destination volumes are not identical, some type of

data loss might occur. This data loss might not be detected initially, but can be detected later when other utilities are used, like fsck(1M), or when the system is rebooted.

When first configuring and validating volume replication, save copies of all affected devices’ VTOCs using the prtvtoc(1M) utility. The fmthard(1M) utility can be used to restore them later, if necessary.

■ When using volume managers like SVM and VxVM, copying between individual

volumes created under these volume managers is safe. VTOC issues are avoided because the VTOC is excluded from volumes created by these volume managers.

■ When formatting individual partitions on a raw device, for all partitions except

the backup partition, make sure the partitions do not map cylinder 0, which contains the VTOC. When using raw partitions as volumes, you are the volume manager and you need to exclude the VTOC from partitions that you configure.

■ When formatting the backup partition of a raw device, make sure that the

physical geometries of the source and destination devices are identical. (Partition 2, by default, maps all cylinders under the backup partition.) If identical device sizing is not possible, make sure that the source backup partition is smaller than the destination partition and that the destination partition does not map cylinder

Chapter 1 Point-in-Time Copy Software Troubleshooting Tips 3

4 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003

CHAPTER

Remote Mirror Software Troubleshooting Tips

This section describes how to avoid or troubleshoot any problems might occur when using the remote mirror software. The following topics are described.

■ “Troubleshooting Checklist” on page 6

■ “Troubleshooting Log Files and Services” on page 6

■ “Checking the Integrity of the Link” on page 10

■ “Correcting Common User Errors” on page 13

Note – The Sun StorEdge Availability Suite 3.2 Remote Mirror Software Administration

and Operations Guide describes the dsstat and scmadm commands. These

commands are useful for displaying information about remote mirror and point-intime copy software volumes.

Troubleshooting Checklist

This table shows the t roubleshooting checklist and related sections.

TABLE2-1 Troubleshooting Checklist

Step For Instructions

1. Check for installation errors. Sun StorEdge Availability Suite 3.2 Software Installation Guide

2. Check that /dev/rdc is created after

reboot.

3. Check that the sndrd daemon is running. Sun StorEdge Availability Suite 3.2 Software

4. Check the log file contents. “Checking Log Files” on page 7

5. Check that the /etc/nsswitch.conf

file is configured correctly.

6. Check the integrity of the link. “Checking the Integrity of the Link” on

7. Check for common errors. “Correcting Common User Errors” on

“Checking That the rdc Service Is Running” on page 8

“If the /dev/rdc Link Is Not Created” on page 9

Installation Guide

“Checking the /etc/nsswitch.conf File” on page 8

page 10

page 13

Troubleshooting Log Files and Services

The remote mirror software is client-server software that is bidirectional. The primary and secondary hosts each act as a client and server in the protocol.

6 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003

+ 36 hidden pages

Sun Microsystems StorEdge Availability Suite 3.2 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Preface

Point-in-Time Copy Software Troubleshooting Tips

Troubleshooting Checklist

Checking Log Files

Improving Performance

Safeguarding the VTOC Information

Remote Mirror Software Troubleshooting Tips

Troubleshooting Checklist

Troubleshooting Log Files and Services