What kind of setup is this? A cluster or have you somehow connected two non-clustered nodes to the same storage?
---------- Post updated 2010-04-03 at 12:01 AM ---------- Previous update was 2010-04-02 at 11:58 PM ----------
Also can you post the output of:
Code:
vxdg -o alldgs list
Hello,
Thanks for reply.
This is a single machine (v440) connected via scsi cable to only ESM on storedge D2. Other scsi port is terminated using LVD/SE terminator. No cluster software on the v440 as well as no such intention.
Code:
vxdg -o alldgs list
VxVM vxdg ERROR V-5-1-776 Option alldgs not recognized, recognized options are:
failfast - set the failfast timeout for the disk (msec)
verify - verifies that the specified disk group task can be performed
without violating any storage-specific guidelines,
but does not perform the task
override - performs the disk group task and ignores any
storage-specific guidelines
remove - removes the objects involved in a move/split/join from
thisdiskgroup
complete - perform recovery by retrying original operation
clean - clear any move/split/join-related internal flags
expand - select additional objects that reside on same disks
dgtype - select dg type (private, shared, san)
clearreserve - clear reservations before import
groupreserve - import with group reserve
listreserve - show group reserve information with list command
ejectkey - eject host membership
dgid - need to use dgid for the dg to be initialized
selectcp - Select cp on this disk
site - Site based import
noreonline - Don't reonline disks
coordinator - dg disks reserved as coordinator disks
site - disk group site name
tag - disk group tag name[=value]
source - disk group tag source
useclonedev - import clone disks
updateid - update ids when importing clone disks
addmirror - Add mirror on the new site
rmmirror - Remove mirror on the site being removed
overridessb - Override SSB on reattaching a disk/site
alldisks - Reattach a site only if all disks are online
autotagging - Autotaging for newly added disks
Hi,
Can anybody provide me Pointers to Practice tests or any Material to prepare for Brainbench certification in Unix Shell Scripting? Also how good is this Certification for UNIX programmers. Is it worth it? I'm planning to take this certification in 2 weeks. Kindly let me know all the pros... (0 Replies)
Dear Gurus,
I have encountered a C question, which I thought of sharing with you.
This question was asked by one of my technical training staff...Though my training was over I'm still thinking of a solution for this..
Write a C program to do a small task(lets say just simply printing a "Hello... (34 Replies)
Hi Gurus,
To the Brain Teaser, if I add another condition, say the executable should not be altered, how the program should be altered? (no perl please, purely C). I forgot to mention this condition my staff had mentioned. ( forgot then and got now :D )
The program executed the first time... (4 Replies)
Hello!
I am working on an application which reads environmental instruments which have serial ports. The application requires a serial port to be present to talk to the device (i.e. /dev/ttyS0 ). In some instances the environmental devices will be 100's of yards away from the computer, so a... (5 Replies)
A global group of scientists are spending the next ten years and a billion dollars to try and develop a computer simulation of the brain:
https://www.humanbrainproject.eu/
I always found it fascinating that the brain can understand itself. This almost sounds like in a few years the computer... (0 Replies)
Discussion started by: figaro
0 Replies
LEARN ABOUT HPUX
vxsited
vxsited(1M)vxsited(1M)NAME
vxsited - site monitoring daemon
SYNOPSIS
/etc/vx/bin/vxsited [mail_address...]
DESCRIPTION
The vxsited daemon monitors Veritas Volume Manager (VxVM) for disks being attached, and reattaches a detached site if the disks that belong
to that site become accessible.
vxsited analyzes the output of the vxnotify command, and waits for a failed disk to attach. When a disk is attached, vxsited attempts to
online the disk, and tries to reattach the failed site. If a site is successfully reattached, vxsited starts recovery using vxrecover, and
sends mail to root (by default) or to other specified users.
Mail Notification
By default, vxsited sends mail to root with information about the disk status of any attempts to reattach the site. To send mail to other
users, add the user login name to the line that starts vxsited in the startup script, /etc/init.d/vxvm-recover, and reboot the system. For
example, if the line appears as:
nohup vxsited root &
and you want mail also to be sent to user1 and user2, change the line to read:
nohup vxsited root user1 user2 &
Alternatively, kill the vxsite process, and restart it from the command line with the required mail addresses as arguments.
The mail notification has a format that is similar to the following:
Subject : Volume Manager site reattach on host hostname
Reattached site sitename in disk-group diskgroup
Reattachment Procedure
If a disk from a detached site becomes accessible again, vxsited checks whether the relocation daemon, vxrelocd, is running. If vxrelocd
is running, vxsited attempts to reattach the site. The relocation daemon can then try to relocate the failed subdisks using space on the
available disks in the disk group. If the failed objects are successfully relocated, vxrelocd changes the state of the site to RECOVER,
and starts the recovery of volumes at the site. When all the plexes at a site have been recovered, the plexes are put into the ACTIVE
state, and the state of the site is set to ACTIVE.
If vxrelocd is not running, vxsited only reattaches a site when all the disks from that site become accessible. After successfully reat-
taching a site, vxsited changes the site state to ACTIVE, and initiates recovery using vxrecover. When all the plexes from a site have been
recovered, the plexes are put into the ACTIVE state, and the state of the site is set to ACTIVE.
vxsited does not attempt to reattach a site that has been explicitly detached by an administrator. The state OFFLINE is set for sites that
have been detached by using the following command:
vxdg -g dg_name detachsite sitename
Disabling vxsited
If you do not want a site to be recovered automatically, kill the vxsited daemon, and prevent it from restarting. To kill the daemon, run
the following command from the command line, and locate the process table entry for vxsited:
ps -ef
Execute the command:
kill -9 PID
Substitute the process ID of the vxsited process for PID. To prevent vxsited from being restarted, comment out the line that starts
vxsited in the startup script /sbin/init.d/vxvm-recover.
FILES
/sbin/init.d/vxvm-recover The startup file for vxsited.
SEE ALSO kill(1), mailx(1), ps(1), vxdg(1M), vxrelocd(1M), vxintro(1M), vxnotify(1M), vxrecover(1M)VxVM 5.0.31.1 24 Mar 2008 vxsited(1M)
04-02-2010
