English dropdown-ico

Sun Microsystems 3.2 manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Sun Microsystems 3.2, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Sun Microsystems 3.2 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Sun Microsystems 3.2. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Sun Microsystems 3.2 should contain:
- informations concerning technical data of Sun Microsystems 3.2
- name of the manufacturer and a year of construction of the Sun Microsystems 3.2 item
- rules of operation, control and maintenance of the Sun Microsystems 3.2 item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Sun Microsystems 3.2 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Sun Microsystems 3.2, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Sun Microsystems service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Sun Microsystems 3.2.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Sun Microsystems 3.2 item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    Sun Microsystems, Inc. www .sun.com Submit comments about this document at: http://www.sun.com/hwdocs/feedback Sun StorEdge ™ A v ailability Suite 3.2 Softw are T roub leshooting Guide P ar t No . 817-3752-10 December 2003, Revision 51[...]

  • Page 2

    Please Recycle Copyright© 2003 Sun Microsystems, Inc., 4150 Network Cir cle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual pr operty rights relating to technology embodied in this pr oduct. In particular , and without limitation, these intellectual property rights may include one or mor e of the[...]

  • Page 3

    iii Contents Preface v 1. Point-in-T ime Copy Software T roubleshooting T ips 1 Troubleshooting Checklist 1 Checking Log Files 2 Improving Performance 2 Safeguarding the VTOC Information 3 2. Remote Mirror Software T roubleshooting T ips 5 Troubleshooting Checklist 6 Troubleshooting Log Files and Services 6 Checking Log Files 7 Checking the /etc/ns[...]

  • Page 4

    iv Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 Correcting Common User Errors 13 Enabled Software on Only One Host 13 V olumes Ar e Inaccessible 13 W rong V olume Set Name Specif ied 14 Accommodating Memory Requirements 16 3. Error Messages 19[...]

  • Page 5

    v Pr eface Sun StorEdge A vailability Suite 3.2 Software T r oubleshooting Guide helps users solve common problems that might arise when using the Sun StorEdge™ A vailability Suite 3.2 software. Befor e Y ou Read This Book T o use the information in this document, you must have thorough knowledge of the topics discussed in these books: ■ Sun St[...]

  • Page 6

    vi Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 How This Book Is Or ganized 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 mirr or software. Chapter 3 provides an alphabe[...]

  • Page 7

    Preface vii Shell Pr ompts T ypographic Conventions Shell Prompt C shell machine-name % C shell superuser machine-name # Bourne shell and Korn shell $ Bourne shell and Korn shell superuser # T ypeface 1 1 The settings on your browser might differ from these settings. Meaning Examples AaBbCc123 The names of commands, files, and directories; on-scr e[...]

  • Page 8

    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 A vailability Suite 3.2 Software Release Notes 817-2782 Sun Cluster 3.0 and Sun StorEdge Software Release Note Supplement[...]

  • Page 9

    Preface ix Accessing Sun Documentation Y ou can view , print, or purchase a broad selection of Sun documentation, including localized versions, at: http://www.sun.com/documentation Contacting Sun T echnical Support If you have technical questions about this product that are not answered in this document, go to: http://www.sun.com/service/contacting[...]

  • Page 10

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

  • Page 11

    1 CHAPTER 1 Point-in-T ime Copy Softwar e T roubleshooting T ips 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: ■ “T roubleshooting Checklist” on page 1 ■ “Checking Log Files” on page 2 ■ “Improving Performance” on[...]

  • Page 12

    2 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 Checking Log Files Y ou 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 me[...]

  • Page 13

    Chapter 1 P oint-in-Time Copy Software T roubleshooting Tips 3 Safeguar ding the VTOC Information Caution – When creating shadow volume sets, do not cr eate 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) tha[...]

  • Page 14

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

  • Page 15

    5 CHAPTER 2 Remote Mirr or Software T roubleshooting T ips This section describes how to avoid or troubleshoot any pr oblems might occur when using the remote mirr or software. The following topics are described. ■ “T roubleshooting Checklist” on page 6 ■ “T roubleshooting Log Files and Services” on page 6 ■ “Checking the Integrity [...]

  • Page 16

    6 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 T roubleshooting Checklist This table shows the troubleshooting checklist and related sections. T roubleshooting Log Files and Services The remote mirr or software is client-server software that is bidir ectional. The primary and secondary hosts each act as a cli[...]

  • Page 17

    Chapter 2 Remote Mirror Software T roub leshooting Tips 7 Checking Log Files Check the following files to tr oubleshoot 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 mirr or software [...]

  • Page 18

    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 conf igured corr ectly , you might encounter these problems: ■ If the hosts: entry is incorrect, volume sets not r esume after a reboot. ■ If the services: entry is incorrect, t[...]

  • Page 19

    Chapter 2 Remote Mirror Software T roub leshooting 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 [...]

  • Page 20

    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 I[...]

  • Page 21

    Chapter 2 Remote Mirror Software T roub leshooting Tips 11 T esting with ifconfig Use the ifconfig command to make sure that the network interface is configur ed and running correctly . This example output shows all the interfaces that are configur ed and running: T esting with ping Use the ping command to verify that the network interfaces can com[...]

  • Page 22

    12 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 In the first example, the command is issued fr om the primary host nws822 to the secondary host nws350 . The network interface is hme0 and the port used by the rdc service is reported. In the second example, the link is A TM so the atmsnoop utility is appr opria[...]

  • Page 23

    Chapter 2 Remote Mirror Software T roub leshooting Tips 13 Corr ecting Common User Errors This section describes user errors encountered often when using the softwar e. ■ “Enabled Software on Only One Host” on page 13 ■ “V olumes Are Inaccessible” on page 13 ■ “W r ong V olume Set Name Specified” on page 14 Enabled Softwar e on On[...]

  • Page 24

    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 enabled or a disk or volume is inaccessible: W rong V olume Set Name Specified When you first enable a set, the remote mirr [...]

  • Page 25

    Chapter 2 Remote Mirror Software T roub leshooting Tips 15 For example, this command updates the volume on the secondary host calamari from the primary host volume: T o correctly display the volume set name, use the sndradm -p command on the primary host. See “T o Find the V olume Set Name” on page 16 . Using the dsstat Command Incorrectly An a[...]

  • Page 26

    16 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 ▼ T o Find the V olume 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 run befor e the A vailability Suite’s start[...]

  • Page 27

    Chapter 2 Remote Mirror Software T roub leshooting Tips 17 The order of write operations must be maintained within a group. Ther efore, these out of order r equests must be stored in memory on the secondary host until the missing request comes in and completes. The secondary host can store up to the har d-coded limit of 64 requests per gr oup. Exce[...]

  • Page 28

    18 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003[...]

  • Page 29

    19 CHAPTER 3 Err or Messages Error messages during the installation pr ocess are described in the Sun StorEdge A vailability Suite 3.2 Software Installation Guide. Solaris err or messages related to the Sun StorEdge A vailability Suite software are described in .... T ABLE 3-1 lists Sun StorEdge A vailability Suite 3.2 error messages in alphabetica[...]

  • Page 30

    20 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 Abort failed PITC iiadm could not abort a copy or update operation on a set. Possible errors: EFAULT : The kernel module tried to read out-of- bounds. File a bug against iiadm. ENOMEM : The kernel module ran out of memory . DSW_EEMPTY : No set was specif ied. DS[...]

  • Page 31

    Chapter 3 Error Messages 21 Bitmap reconfig failed %s:%s Kernel A request to reconf igure the bitmap on the local host has failed. This can happen for two reasons: • The old bitmap cannot be read fr om to obtain needed information. • The new bitmap cannot be reserved because the volume is not accessible or is already in use. V erify that the ne[...]

  • Page 32

    22 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 cannot find SNDR set <shost>:<svol> in config RM Remote mirror set cannot be found in the conf iguration database. The set is not configur ed. Check the entry for errors. Cannot reconfig %s:%s to %s:%s, Must be in logging mode Kernel An operation has[...]

  • Page 33

    Chapter 3 Error Messages 23 Cannot enable %s:%s ==> %s:%s, secondary in use in another set Kernel A set being enabled or resumed has a secondary volume that is already in use as a secondary volume for another remote mirr or set. A volume cannot be enabled as a secondary volume if it is already in use as a secondary volume by another remote mirro[...]

  • Page 34

    24 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 Copy failed PITC A copy or update operation could not be initiated. Possible errors: EFAULT : The kernel module tried to read out-of- bounds. File a bug against iiadm. ENOMEM : The kernel module ran out of memory . DSW_EEMPTY : No set was specif ied on the comma[...]

  • Page 35

    Chapter 3 Error Messages 25 Create overflow failed PITC An overflow volume couldn’t be initialized. Possible errors: EFAULT : The kernel module tried to read out-of- bounds. File a bug against iiadm. ENOMEM : The kernel module ran out of memory . DSW_EEMPTY : No overflow volume was specif ied. DSW_EINUSE : The volume that was specified is alr ead[...]

  • Page 36

    26 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 Disable pending on diskq %s, try again later Kernel A request to disable the disk queue is already in progr ess. V erify that the previous request has completed successfully . If it has, this r equest is no longer valid. If it has not, wait for it to complete un[...]

  • Page 37

    Chapter 3 Error Messages 27 disk queue volume <vol> must not match any primary SNDR volume or bitmap RM The disk queue volume specified for the reconf iguration operation is already in use by the remote mirr or software as a data volume or bitmap volume. don't understand shadow type PITC The iiadm -e command expected dep or ind . DSWIOC_[...]

  • Page 38

    28 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 Enable failed PITC Could not enable volume. Possible errors: EFAULT : The kernel module tried to read out-of- bounds. File a bug against iiadm. ENOMEM : The kernel module ran out of memory . DSW_ESHUTDOWN : The kernel module is in the process of shutting down th[...]

  • Page 39

    Chapter 3 Error Messages 29 Failed to detach overflow volume PITC iiadm had a problem detaching the overflow volume from a set. Possible err ors: EFAULT : The kernel module tried to read out-of- bounds. File a bug against iiadm. ENOMEM : The kernel module ran out of memory . DSW_EEMPTY : No set was specif ied to detach from. DSW_ENOTFOUND : The set[...]

  • Page 40

    30 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 hostname tag exceeds CFG_MAX_BUF PITC Because CFG_MAX_BUF is 1k, this message is not expected to be reported. Import failed PITC Could not import shadow volume. Possible errors: EFAULT : The kernel module tried to read out-of- bounds. File a bug against iiadm EN[...]

  • Page 41

    Chapter 3 Error Messages 31 Join failed PITC Could not join shadow volume back to the set. Possible errors: EFAULT : The kernel module tried to read out-of- bounds. File a bug against iiadm. ENOMEM : The kernel module ran out of memory . DSW_EEMPTY : A volume was missing on the command line. DSW_ENOTFOUND : The set could not be found in the kernel.[...]

  • Page 42

    32 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 Memory allocation failure PITC iiadm ran out of memory . Must be super-user to execute Kernel The user issued a remote mirror command but does not have superuser privileges. All r emote mirror commands requir e superuser privileges. must specify full set details[...]

  • Page 43

    Chapter 3 Error Messages 33 Overflow list access failure PITC iiadm could not get a list of overflow volumes fr om the kernel. Possible errors: EF AUL T : The kernel module tried to read out-of- bound. File a bug against iiadm. ENOMEM: The kernel module ran out of memory . Overflow volume is already in an InstantImage group PITC During an attach op[...]

  • Page 44

    34 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 Reverse sync needed, cannot sync %s:%s ==> %s:%s Kernel The user requested a forward sync operation for a remote mirr or set which needs a reverse sync. This occurs when a previous r everse sync does not complete successfully or because the primary volume was[...]

  • Page 45

    Chapter 3 Error Messages 35 Shadow group %s is suspended PITC The user attempted to perform a copy or update operation on a group with one or more suspended sets. The %s parameter identifies the f irst set found in the group that is suspended. Shadow group suspended PITC The user attempted to perform a copy or update operation on a suspended set. S[...]

  • Page 46

    36 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 SNDR set does not have a disk queue RM Set does not have a disk queue attached when attempting either a queue r emove operation or a queue replace operation. SNDR: The volume ’<vol2>’ has been configured previously as ’<vol1>’. Re-enter comma[...]

  • Page 47

    Chapter 3 Error Messages 37 The volume %s is already in use Kernel The data volume in the remote mirror set is alr eady in use as a bitmap volume or a disk queue volume. Use a differ ent data volume. Too many volumes given for update PITC iiadm ran out of memory . Unable to access bitmap PITC During an enable operation, iiadm tried to validate the [...]

  • Page 48

    38 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 unable to determine hostname: <host> RM Could not determine the host name of the system. unable to determine IP addresses for either host <phost> or host <shost> RM The IP address for either the primary host or the secondary host could not be d[...]

  • Page 49

    Chapter 3 Error Messages 39 unable to obtain unique set id for <shost>:<svol> RM Lookup of the set ID in the configuration database for this set has failed. Unable to open bitmap file <vol> RM The volume specified for the bitmap could not be opened. The volume might not exist or is already in use by another program. Unable to open[...]

  • Page 50

    40 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 Update failed PITC One or more volumes in a group copy or update command failed. Possible errors: EFAULT : The kernel module tried to read out-of- bounds. File a bug against iiadm. ENOMEM : The kernel module ran out of memory . EINVAL : User is performing a shad[...]

  • Page 51

    Chapter 3 Error Messages 41 Volumes are not in same disk group PITC iiadm detected that the master , shadow , and bitmap volumes are not all in the same cluster device group, as requir ed by the point-in-time copy software. volume "<vol>" is not part of a disk group, please specify resource ctag RM The volume <vol> is not bein[...]

  • Page 52

    42 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003 Related Error Messages The Solaris configuration administration utility , cfgadm, reports an err or when it is used on systems where the Sun StorEdge A vailability Suite software is installed. The error occurs because a pr ocess does not suspend properly so that[...]