Sun Microsystems 3.2 manual Using the dsstat Command Incorrectly

Page 25

For example, this command updates the volume on the secondary host calamari from the primary host volume:

#sndradm -un calamari:/dev/vx/rdsk/rootdg/tony1

To correctly display the volume set name, use the sndradm -pcommand on the primary host. See “To Find the Volume Set Name” on page 16.

Using the dsstat Command Incorrectly

An administrator might use the dsstat(1M) command instead of sndradm -pto find the volume set name. The output of both commands only appears to be similar

# dsstat -m sndr

 

 

 

 

 

 

 

Name

t

s

pct

role

kps

tps

svt

sk/rootdg/tony1

P

L

0.00

net

0

0

0

sk/rootdg/bmap1

 

 

 

bmp

0

0

0

 

 

 

 

 

 

 

 

Issuing the sndradm -pCommand on the Secondary Host Incorrectly

An administrator might use the sndradm -pcommand to find the volume set name correctly but issue the command from the secondary host incorrectly. Depending on which host you issue the command from, the output differs. For example, when issued from the primary host, the command shows the correct volume set name of calamari:/dev/vx/rdsk/rootdg/tony1:

# sndradm -p

 

/dev/vx/rdsk/rootdg/tony1

-> calamari:/dev/vx/rdsk/rootdg/tony1

When issued from the secondary host, the command shows the incorrect volume set name. The name ariell:/dev/vx/rdsk/rootdg/tony0 is the name of the primary host and its volume set.

#sndradm -p

/dev/vx/rdsk/rootdg/tony0 <- ariell:/dev/vx/rdsk/rootdg/tony0

Chapter 2 Remote Mirror Software Troubleshooting Tips 15

Page 24 Page 26
Image 25
Page 24 Page 26
Contents Sun Microsystems, Inc Please Recycle Contents Error Messages Before You Read This Book PrefaceHow This Book Is Organized Using Unix CommandsTypographic Conventions Shell PromptsShell Shell superuserRelated Documentation Contacting Sun Technical Support Accessing Sun DocumentationSun Welcomes Your Comments Page Check for installation errors Troubleshooting ChecklistReboot Check the log file contentsImproving Performance Checking Log FilesSafeguarding the Vtoc Information Page Remote Mirror Software Troubleshooting Tips Check the integrity of the link Check for common errors Troubleshooting Log Files and ServicesChecking Log Files Checking That the rdc Service Is Running If the /dev/rdc Link Is Not Created Checking the Integrity of the Link Testing with ifconfig Nws822# snoop -d hme0 port rdc Enabled Software on Only One Host Correcting Common User ErrorsWrong Volume Set Name Specified Using the dsstat Command Incorrectly Accommodating Memory Requirements To Find the Volume Set NameRemote Mirror Software Troubleshooting Tips Page Line. This happens when the copy parameters option Iiadm was expecting a number to be on the commandIs used but the arguments for units and delay are Contains the volumes does not match the cluster tagSpecified set. Possible errors Overflow volume could not be attached toDsweempty No overflow volume was specified Dsweinuse The overflow volume is already beingMirror set is already configured to be used by Volume requested as a bitmap for the remoteVolume requested as a remote mirror bitmap Volume is already configured to be a volume used byDatabase. The set is not configured. Check the entry for Remote mirror set cannot be found in the configurationErrors Primary volume has a file system mounted on itVolume that is already in use as a secondary volume Kernel Set being enabled or resumed has a secondaryFor another remote mirror set. a volume cannot be Enabled as a secondary volume if it is already in use asPossible errors Copy or update operation could not be initiatedDsweempty No set was specified on the command Dsweoffline One or more volumes in the set isDsweinuse The volume that was specified is already An overflow volume couldn’t be initialized. PossibleVolume Dswersrvfail The kernel was unable to accessUnsuccessfully before attempting to disable the disk Kernel Request to disable the disk queue is alreadyIiadm command must be issued on the other Where the iiadm command was issuedReconfiguration operation is already in use by Disk queue volume specified forRemote mirror software as a data volume or bitmap Iiadm -ecommand expected dep or indNew sets can be enabled Could not enable volume. Possible errorsDsweempty One of the volumes names master Dsweinuse One of the volumes master, shadowFrom a set. Possible errors Iiadm had a problem detaching the overflow volumeDsweodependency The overflow volume is still Going from logging mode to replicating modeSets can be enabled Could not import shadow volume. Possible errorsDsweempty One of the volume names is blank. File a Dsweinuse One of the volumes is already in use byDsweempty a volume was missing on the command Could not join shadow volume back to the set. PossibleTrying to join the volume is not in the exported state Dsweinvalbmp The bitmap volume is not bigSet specified for the command cannot be found User attempted to enable a set using the shostsvolCurrent configuration. Check the set to ensure that It matches one of the configured sets. Use sndradmKernel. Possible errors Iiadm could not get a list of overflow volumes fromVolume the user specified to attach to a compact Master, shadow, or bitmap volumeSize of the secondary volume. Verify that Disk queue replace command can also be used toSecondary volume is not in an error state and can be AccessedVolume specified as the shadow volume is already User attempted to perform a copy or updateUse as an attached overflow volume Use as a shadow for a different master volumeVolume was already enabled, but with a different User attempted to enable a set in whichVolume in the remote mirror set Dswenotfound Could not find specified volumeBitmap device, but could not get access to it During an enable operation, iiadm tried to validateMaster device, but could not get access to it During a reset operation, iiadm was unable to findSunCluster could not find the specified disk service Be determined. Verify the settingsCould not find remote mirror group in configuration Could not find remote mirror set in configurationVolume specified for the bitmap could not be Lookup of the set ID in the configuration database forOpened. The volume might not exist or is already Iiadm attempted to access the configuration fileCommand failed. Possible errors One or more volumes in a group copy or updateSame as Update failed meaning but for a specific During a reset, iiadm tried to updateVolume vol is not being managed by Volumes are not all in the same cluster device groupIiadm detected that the master, shadow, and bitmap As required by the point-in-time copy softwareRelated Error Messages

3.2 specifications

Sun Microsystems 3.2, often referred to as SunOS 3.2, was a notable release of the Sun operating system that emerged during the rapidly evolving landscape of computer technology in the early 1980s. This operating platform was designed specifically for Sun Workstations, utilizing the robust hardware architecture developed by Sun Microsystems. The introduction of SunOS 3.2 marked a significant step forward in the development of UNIX-like operating systems optimized for entrepreneurship and scientific applications.

One of the main features of SunOS 3.2 was its adherence to the Berkeley Software Distribution (BSD) model, which allowed for advanced networking capabilities, enhanced performance, and efficient resource management. BSD's influence provided SunOS 3.2 with TCP/IP networking protocols, allowing users to connect to other devices seamlessly and manage network resources easily. This feature was crucial during a time when networking was becoming increasingly vital for organizations.

The system's support for virtual memory was another innovative characteristic. SunOS 3.2 utilized demand paging, which allowed programs to use more memory than was physically installed on their machines, significantly improving multitasking and overall system responsiveness. This capability was particularly advantageous for enterprises that relied on large-scale computations and data analysis.

SunOS 3.2 also introduced support for the Sun Window System, which meant users could utilize graphical user interfaces for interacting with applications, moving away from purely text-based command interfaces. This transition paved the way for more intuitive user experiences in the realm of computing, making powerful UNIX capabilities more accessible.

The inclusion of software utilities such as the C shell (csh) and a variety of development tools further strengthened SunOS 3.2’s position as a suitable platform for developers. The system provided robust development environments for programming in languages like C and assembly, catering to custom application requirements across different industries.

Lastly, security features were integrated into SunOS 3.2 to safeguard sensitive data and enhance system integrity. Permission settings and user authentication mechanisms were refined, allowing organizations to securely manage their computing resources.

In summary, SunOS 3.2 represented a landmark evolution in operating systems, showcasing a blend of advanced networking, memory management, graphical user interface, development tools, and security—elements that defined a generation of computing within the high-performance ecosystem of Sun Microsystems.
Top Page Image Contents