Résumé du contenu de la page N° 1
™
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
Résumé du contenu de la page N° 2
Copyright© 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in this product. 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
Résumé du contenu de la page N° 3
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 therdc Service Is Running 8 If the/dev/rdc Link Is Not Created 9 Checking the Integrity of the Link 10 Testing with ifconfig 11
Résumé du contenu de la page N° 4
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
Résumé du contenu de la page N° 5
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 Administr
Résumé du contenu de la page N° 6
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 sy
Résumé du contenu de la page N° 7
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 1 Typeface Meaning Examples AaBbCc123 The names of commands, files, Edit your.login file. and directories; on-screen Use ls -a to list all files. computer output % You have mail. AaBbCc123 What you type, when contrasted % su with on-screen computer output Password: AaBbCc123 Book titles, new words or terms, Read Chapter 6 i
Résumé du contenu de la page N° 8
Related Documentation Application Title Part Number Man pages sndradm N/A iiadm dsstat kstat svadm Latest release Sun StorEdge Availability Suite 3.2 Software Release 817-2782 information Notes Sun Cluster 3.0 and Sun StorEdge Software Release 816-5128 Note Supplement Installation and user Sun StorEdge Availability Suite 3.2 Software 817-2783 Installation Guide SunATM 3.0 Installation and User’s Guide 805-0331 SunATM 4.0 Installation and User’s Guide 805-6552 Sun Gigabit Ethernet FC-AL/P Combina
Résumé du contenu de la page N° 9
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: h
Résumé du contenu de la page N° 10
x Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003
Résumé du contenu de la page N° 11
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 Troubleshootin
Résumé du contenu de la page N° 12
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 /var/adm/messages The /var/adm/messages file contains timestamped messages about the p
Résumé du contenu de la page N° 13
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 Avail
Résumé du contenu de la page N° 14
4 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003
Résumé du contenu de la page N° 15
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
Résumé du contenu de la page N° 16
Troubleshooting Checklist This table shows the troubleshooting checklist and related sections. 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 “Checking That therdc Service Is Running” reboot. 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
Résumé du contenu de la page N° 17
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: Aug 20 19:13:55 scm: scmadm cache enable succeeded Aug 20 19:13:55 ii: iiboot resume cluster tag 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 firs
Résumé du contenu de la page N° 18
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 fil
Résumé du contenu de la page N° 19
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: rpcinfo: RPC: Program not registered 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: # netstat -a|grep rdc *.rdc *.* 0 0 65535 0 LISTEN
Résumé du contenu de la page N° 20
The /etc/name_to_major file is missing an entry for the /dev/rdc pseudo-link. This example shows a valid entry (the number followingrdc can be any number): # grep rdc /etc/name_to_major rdc 239 The /usr/kernel/drv/rdc.conf file is incomplete. This example shows a valid entry: # grep pseudo /usr/kernel/drv/rdc.conf name="rdc" parent="pseudo"; 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 installatio
