Sun Microsystems 3.2 Manuel utilisateur

Sun Microsystems, Inc.

www.sun.com

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

Sun StorEdge

™

Availability Suite 3.2 Software

Troubleshooting Guide

Part No. 817-3752-10

December 2003, Revision 51

Please

Recycle

Sun Microsystems,Inc.hasintellectualproperty rights relatingtotechnologyembodiedinthisproduct. In particular, and without limitation,

these intellectual propertyrightsmayincludeoneormore of the U.S.patentslistedathttp://www.sun.com/patents and one or more

additional patents or pending patent applications in the U.S.andinothercountries.

This document and the producttowhichitpertainsare distributedunderlicensesrestrictingtheiruse,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-partysoftware,including font technology,is copyrighted and licensed fromSun suppliers.

Parts of the product may be derived fromBerkeley BSD systems, licensed from the University of California. UNIX is a registeredtrademark 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, Sun StorEdge, and Solaris aretrademarks or registeredtrademarks of Sun

Microsystems,Inc. in the U.S. and in other countries.

All SPARCtrademarks areused under license and are trademarks or registeredtrademarks of SPARC International, Inc. in the U.S. and in other

countries. Productsbearing SPARCtrademarks are based upon an architecturedeveloped by Sun Microsystems, Inc.

The Adobe® logo is a registeredtrademark of Adobe Systems,Incorporated.

U.S. Government Rights—Commercial use. Government users aresubject to the Sun Microsystems, Inc. standard license agreementand

applicable provisionsof the FAR and its supplements.

Productscoveredby and information contained in this service manual are controlled by U.S. Export Controllaws and may be subject to the

export or import laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, 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 WARRANTY OF MERCHANTABILITY,FITNESS FOR APARTICULAR PURPOSEOR NON-INFRINGEMENT,

ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Sun Microsystems, Inc. a les droitsde 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émentairesou 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 restreignentl’utilisation, la copie, la distribution, et la

décompilation. Aucune partie de ce produit ou document ne peut êtrereproduitesous 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 relativeaux 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 marquesde fabrique ou des marques

déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autrespays.

Toutesles marquesSPARC sont utilisées sous licence et sont des marques de fabrique ou des marquesdéposées de SPARCInternational, Inc.

aux Etats-Unis et dans d’autres pays. Les produitsprotant les marques SPARCsont basés sur une architecturedéveloppée par Sun

Microsystems,Inc.

Ce produitest soumis à la législation américaine en matièrede contrôle des exportations et peut êtresoumis à 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, directementou 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èrenon exhaustive, la liste de personnes qui font objet d’un ordrede ne pas participer, d’une façon directe

ou indirecte,aux exportations des produitsou 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ﬁquementdésignés sont rigoureusementinterdites.

LA DOCUMENTATION EST FOURNIE "EN L’ÉTAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES

OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEEPAR 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.

iii

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

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

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

v

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

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

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 information:

■ Software documentation that you received with your system

■ Solaris™ operating environment documentation, which is at

http://docs.sun.com

Preface vii

Shell Prompts

Typographic Conventions

Shell Prompt

C shell machine-name%

C shell superuser machine-name#

Bourne shell and Korn shell $

Bourne shell and Korn shell superuser #

Typeface

1

1 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.

Replace command-line variables

with real names or values.

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.

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

Related Documentation

Application Title Part Number

Man pages sndradm

iiadm

dsstat

kstat

svadm

N/A

Latest release

information

Sun StorEdge Availability Suite 3.2 Software Release

Notes

817-2782

Sun Cluster 3.0 and Sun StorEdge Software Release

Note Supplement

816-5128

Installation and user Sun StorEdge Availability Suite 3.2 Software

Installation Guide

817-2783

SunATM 3.0 Installation and User’s Guide

SunATM 4.0 Installation and User’s Guide

805-0331

805-6552

Sun Gigabit Ethernet FC-AL/P Combination Adapter

Installation Guide

806-2385

Sun Gigabit Ethernet/S 2.0 Adapter Installation and

User’s Guide

Sun Gigabit Ethernet/P 2.0 Adapter Installation and

User’s Guide

805-2784

805-2785

Sun Enterprise 10000 InterDomain Networks User

Guide

806-4131

System administration Sun StorEdge Availability Suite 3.2 Remote Mirror

Software Administration and Operations Guide

817-2784

Sun StorEdge Availability Suite 3.2 Point-In-Time

Copy Software Administration and Operations Guide

817-2781

Cluster Sun Cluster 3.0 and Sun StorEdge Software

Integration Guide

816-5127

Configuration Sun Enterprise 10000 InterDomain Network

Configuration Guide

806-5230

Preface ix

Accessing Sun Documentation

You can view, print, or purchase a broad selection of Sun documentation, including

localized versions, at:

http://www.sun.com/documentation

Contacting Sun Technical Support

If you have technical questions about this product that are not answered in this

document, go to:

http://www.sun.com/service/contacting

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and

suggestions. You can submit your comments by going to:

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

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

Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide, part number 817-

3752-10

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

1

CHAPTER

1

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 troubleshooting checklist and related sections.

TABLE 1-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.

Sun StorEdge Availability Suite 3.2 Software

Installation Guide

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

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

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:

■ /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:

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.

Mar 05 15:56:16 scm: scmadm cache enable succeeded

Mar 05 15:56:16 ii: iiboot resume cluster tag <none>

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

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

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 the 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

0.

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

5

CHAPTER

2

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-in-

time copy software volumes.

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

Troubleshooting Checklist

This table shows the troubleshooting checklist and related sections.

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.

TABLE 2-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.

“Checking That the rdc Service Is Running”

on page 8

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

page 9

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

Installation Guide

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

5. Check that the /etc/nsswitch.conf

file is configured correctly.

“Checking the /etc/nsswitch.conf File”

on page 8

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

page 10

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

page 13

Chapter 2 Remote Mirror Software Troubleshooting Tips 7

Checking Log Files

Check the following files to troubleshoot problems:

■ /var/opt/SUNWesm/ds.log

The /var/opt/SUNWesm/ds.log file contains timestamped messages about the

software. For example:

■ /var/adm/messages

Make sure that the rdc service is active when the remote mirror software starts or

you see the following error messages:

Aug 20 19:13:55 scm: scmadm cache enable succeeded

Aug 20 19:13:55 ii: iiboot resume cluster tag <none>

Aug 20 19:13:58 sndr: sndrboot -r first.atm /dev/vx/rdsk/rootdg/vol5

/dev/vx/rdsk/

rootdg/bm6 second.atm /dev/vx/rdsk/rootdg/vol7 /dev/vx/rdsk/rootdg/bm7

Successful

Aug 20 19:13:58 sndr: sndrboot -r first.atm /dev/vx/rdsk/rootdg/vol4

/dev/vx/rdsk/

rootdg/bm4 second.atm /dev/vx/rdsk/rootdg/vol4 /dev/vx/rdsk/rootdg/vol4

Successful

Aug 20 19:13:58 sndr: sndrboot -r first.atm /dev/vx/rdsk/rootdg/vol2

/dev/vx/rdsk/

rootdg/bm2 second.atm /dev/vx/rdsk/rootdg/vol2 /dev/vx/rdsk/rootdg/bm2

Successful

Aug 20 19:13:58 sndr: sndrboot -r first.atm /dev/vx/rdsk/rootdg/vol3

/dev/vx/rdsk/

rootdg/bm3 second.atm /dev/vx/rdsk/rootdg/vol3 /dev/vx/rdsk/rootdg/bm3

Successful

Completing SNDR startup: sndrd Aug 16 08:37:16 sndrd[291]: Cannot get address

for transport tcp6 host \1 service rdc

Aug 16 08:37:16 sndrd[291]: Cannot establish RDC service over /dev/tcp6:

transport setup problem.

Aug 16 08:37:16 sndrd[291]: Cannot get address for transport tcp host \1 service

rdc

Aug 16 08:37:16 sndrd[291]: All transports have been closed with errors.

Exiting.

Aug 16 08:37:16 sndrd[291]: SNDR Fatal server error

sndrsyncd done

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

Checking the /etc/nsswitch.conf File

If entries in the /etc/nsswitch.conf are not configured correctly, you might

encounter these problems:

■ If the hosts: entry is incorrect, volume sets not resume after a reboot.

■ If the services: entry is incorrect, the rdc service might not activate and no

data is replicated.

Note – The services port number must be the same between all interconnected

remote mirror host systems.

When the hosts: and services: entries are included in the

/etc/nsswitch.conf file, ensure that files is placed before nis, nisplus,

ldap, dns, or any other service the machine is using. For example, for systems using

the NIS naming service, the file must include:

If you need to edit the /etc/nsswitch.conf(4) file, use a text editor.

● After editing the file, shut down and restart your machine.

Checking That the rdc Service Is Running

When the remote mirror software loads, it adds an entry into the /etc/services

file for the rdc service. Search for an entry that looks like this:

Use the rpcinfo and netstat commands to check the service:

■ rpcinfo

hosts: files nis

services: files nis

# /etc/shutdown -y -g 0 -i 6

# grep rdc /etc/services

rdc 121/tcp # SNDR server daemon

# rpcinfo -T tcp hostname 100143

program 100143 version 6 ready and waiting

Chapter 2 Remote Mirror Software Troubleshooting Tips 9

where:

■ -T tcp specifies the transport that the service uses.

■ hostname is the name of the machine where the service is running.

If the service is not running, this message is displayed:

If you see this message, it is possible that the /etc/nsswitch.conf services:

entry is incorrectly configured. See “Checking the /etc/nsswitch.conf File” on

page 8.

■ netstat

This messages shows that the service is running:

If the /dev/rdc Link Is Not Created

Note – Although other applications make entries in the files described in this

section, you can edit the files to correct these problems. Always make a backup copy

of a file before editing it.

The /dev/rdc pseudo-link might not be created for the following reasons:

■ The /etc/devlink.tab file is missing an entry for the /dev/rdc pseudo-link.

This example shows a valid entry:

rpcinfo: RPC: Program not registered

# netstat -a|grep rdc

*.rdc *.* 0 0 65535 0 LISTEN

*.rdc *.* 0 0

65535 0 LISTEN

# grep rdc /etc/devlink.tab

type=ddi_pseudo;name=rdc \D

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

■ The /etc/name_to_major file is missing an entry for the /dev/rdc

pseudo-link. This example shows a valid entry (the number following rdc can be

any number):

■ The /usr/kernel/drv/rdc.conf file is incomplete. This example shows a

valid entry:

Checking the Integrity of the Link

After you determine that the rdc service is ready, check the integrity of the TCP/IP

link. As part of the installation process, you entered the primary and secondary host

names and IP addresses of the machines where the software is installed in the

/etc/hosts file. Make sure this file contains the same information on the primary

and secondary hosts because the software is bidirectional. The software uses these

hosts to transfer data.

Simple tests to check link integrity include the following:

■ Use the telnet or rlogin commands to connect to the hosts.

■ Use the ifconfig command to check your network interfaces.

■ Use the ping command to make sure packets are being transmitted.

■ Use the snoop or atmsnoop commands to make sure the software is copying

data.

Note – The dsstat command displays volume information The sndradm -H

command displays link I/O statistics.

# grep rdc /etc/name_to_major

rdc 239

# grep pseudo /usr/kernel/drv/rdc.conf

name="rdc" parent="pseudo";

La page charge ...

Sun Microsystems 3.2 Manuel utilisateur

Ce manuel convient également à

Sun Microsystems 3.2 Manuel utilisateur

dans d''autres langues

Documents connexes

Autres documents