Sun Microsystems 3.2 - Manuals

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

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

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 releaseinformation Sun StorEdge Availability Suite 3.2 Software ReleaseNotes 817-2782 Sun Cluster 3.0 and ...

Preface ix Accessing Sun Documentation You can view, print, or purchase a broad selection of Sun documentation, includinglocalized versions, at: http://www.sun.com/documentation Contacting Sun Technical Support If you have technical questions about this product that are not answered in thisdocument,...

1 C H A P T E R 1 Point-in-Time Copy SoftwareTroubleshooting Tips This chapter describes how to avoid or troubleshoot problems that might occurwhen using the point-in-time copy software. The chapter includes the following topics: ■ “Troubleshooting Checklist” on page 1 ■ “Checking Log Files” on page...

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 twosystem log files: ■ /var/opt/SUNWesm/ds.log The /var/opt/SUNWesm/ds.log file contains timestamped messages about the poi...

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

5 C H A P T E R 2 Remote Mirror SoftwareTroubleshooting Tips This section describes how to avoid or troubleshoot any problems might occur whenusing the remote mirror software. The following topics are described. ■ “Troubleshooting Checklist” on page 6 ■ “Troubleshooting Log Files and Services” on pa...

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

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

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/n...

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

Chapter 2 Remote Mirror Software Troubleshooting Tips 11 Testing with ifconfig Use the ifconfig command to make sure that the network interface is configured and running correctly. This example output shows all the interfaces that areconfigured and running: Testing with ping Use the ping command to ...

Chapter 2 Remote Mirror Software Troubleshooting Tips 13 Correcting Common User Errors This section describes user errors encountered often when using the software. ■ “Enabled Software on Only One Host” on page 13 ■ “Volumes Are Inaccessible” on page 13 ■ “Wrong Volume Set Name Specified” on page 14...

14 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 This example shows the newfs -N command completing successfully: This example shows a typical error caused when the secondary host is not enabledor a disk or volume is inaccessible: Wrong Volume Set Name Specified ...

Chapter 2 Remote Mirror Software Troubleshooting Tips 15 For example, this command updates the volume on the secondary host calamari from the primary host volume: To correctly display the volume set name, use the sndradm -p command on the primary host. See “To Find the Volume Set Name” on page 16 . ...

16 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 ▼ To Find the Volume Set Name 1. If you are unsure of the volume set name, type the following command from the primary host: Running Startup Script Out of Order The scripts to configure the network interface must r...

19 C H A P T E R 3 Error Messages Error messages during the installation process are described in the Sun StorEdgeAvailability Suite 3.2 Software Installation Guide. Solaris error messages related to theSun StorEdge Availability Suite software are described in .... TABLE 3-1 lists Sun StorEdge Avail...

42 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 Related Error Messages The Solaris configuration administration utility, cfgadm, reports an error when it isused on systems where the Sun StorEdge Availability Suite software is installed. Theerror occurs because a...