Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX 11i Version 1.5 Reference Volume 2, Section 1M: System Administration Commands > v

vxnotify(1M)

» 

Technical documentation

» Feedback
Content starts here

 » Table of Contents

 » Index

NAME

vxnotify — display Volume Manager configuration events

SYNOPSIS

vxnotify [-cdfims] [-g diskgroup] [-n number ] [-t timeout] [-w wait-time]

DESCRIPTION

The vxnotify utility displays events related to disk and configuration changes, as managed by the Volume Manager configuration daemon, vxconfigd. If vxnotify is running on a system where the Volume Manager cluster feature is active, it displays events related to changes in the cluster state of the system on which it is running. vxnotify displays requested event types until killed by a signal, until a given number of events have been received, or until a given number of seconds have passed.

CONFIGURATION EVENTS

Each event is displayed as a single-line output record on the standard output.

connected

A connection was established with vxconfigd. This event type is displayed immediately after successful startup and initialization of vxnotify. A connected event is also displayed if the connection to vxconfigd is lost, and then regained. A connected event displayed after a reconnection indicates that some events may have been lost.

disconnected

The connection to vxconfigd was lost. This normally results from vxconfigd being stopped (such as by vxdctl stop) or killed by a signal. In response to a disconnection, vxnotify displays a disconnected event and then waits until a reconnection succeeds. A connected event is then displayed.

A disconnected event is also printed if vxconfigd is not accessible at the time vxnotify is started. In this case, the disconnected event precedes the first connected event.

more events

Due to internal buffer overruns or other problems, some events may have been lost.

waiting ...

If the -w option is specified, a waiting event is displayed after a defined period with no other events. Shell scripts can use waiting messages to collect groups of nearly simultaneous, or at least related, events. This can make shell scripts more efficient. This can also provide some scripts with better input because sets of detach events, in particular, often occur in groups that scripts can relate together. This is particularly important given that a typical shell script will block until vxnotify produces output, thus requiring output to indicate the end of a possible sequence of related events.

import dg groupname dgid groupid

The disk group named groupname was imported. The disk group ID of the imported disk group is groupid.

deport dg groupname dgid groupid

The named disk group was deported.

disable dg groupname dgid groupid

The named disk group was disabled. A disabled disk group cannot be changed, and its records cannot be printed with vxprint. However, some volumes in a disabled disk group may still be usable, although it is unlikely that the volumes will be usable after a system reboot. A disk group will be disabled as a result of excessive failures. A disk group will be disabled if the last disk in the disk group fails, or if errors occur when writing to all configuration and log copies in the disk group.

change dg groupname dgid groupid

A change was made to the configuration for the named disk group. The transaction ID for the update was groupid.

detach subdisk subdisk plex plex volume volume dg groupname dgid groupid

The named subdisk, in the named disk group, was detached as a result of an I/O failure detected during normal volume I/O, or disabled as a result of a detected disk failure. Failures of a subdisk in a RAID-5 volume or a log subdisk within a mirrored volume result in a subdisk detach; other subdisk failures generally result in the subdisk's plex being detached.

detach plex plex volume volume dg groupname dgid groupid

The named plex, in the named disk group, was detached as a result of an I/O failure detected during normal volume I/O, or disabled as a result of a detected total disk failure.

detach volume volume dg groupname dgid groupid

The named volume, in the named disk group, was detached as a result of an I/O failure detected during normal volume I/O, or as a result of a detected total disk failure. Usually, only plexes or subdisks are detached as a result of volume I/O failure. However, if a volume would become entirely unusable by detaching a plex or subdisk, then the volume may be detached.

detach disk accessname dm medianame dg groupname dgid groupid

The named disk, with device access name accessname and disk media name medianame was disconnected from the named disk group as a result of an apparent total disk failure. Total disk failures are checked for automatically when plexes or subdisks are detached by kernel failures, or explicitly by the vxdisk check operation (see vxdisk(1M)).

log-detach volume volume dg groupname dgid groupid

All log copies for the volume (either log plexes for a RAID-5 volume or log subdisks for a regular mirrored volume) have become unusable, either as a result of I/O failures or as a result of a detected total disk failure.

change disk accessname dm medianame dg groupname dgid groupid

The disk header changed for the disk with a device access name of accessname. The disk group name and ID of the disk are groupname and groupid, respectively. The displayed groupname and groupid strings will be ``-'' or blank if the disk is not currently in an imported disk group.

degraded volume volume dg groupname dgid groupid

The RAID-5 volume has become degraded due to the loss of one subdisk in the raid5 plex of the volume. Accesses to some parts of the volume may be slower than to other parts depending on the location of the failed subdisk and the subsequent I/O patterns.

enabled path pathname belonging to dmpnode dmpnodename

The path pathname is now available for I/O. It is a path to the disk/LUN represented by the DMP metanode dmpnodename.

disabled path pathname belonging to dmpnode dmpnodename

The path pathname is no longer available for I/O. It is a path to the disk/LUN represented by the DMP metanode dmpnodename.

enabled dmpnode dmpnodename

The DMP metanode dmpnodename is enabled. At least one of the paths to the disk/LUN represented by this DMP metanode is now available for I/O.

disabled dmpnode dmpnodename

The DMP metanode dmpnodename is disabled. The disk/LUN represented by the DMP metanode is not available for I/O.

enabled controller controllername belonging to disk array da_serial_no

The host controller controllername connected to the disk array with the disk array serial number da_serial_no is enabled. As a result DMP allows I/Os to all paths connected to this host controller.

disabled controller controllername belonging to disk array da_serial_no

The host controller controllername connected to the disk array with disk array serial number da_serial_no is disabled for I/O. As a result DMP will not allow I/Os to any of the paths that are connected to this host controller.

removed disk array da_serial_no

The disk array with serial number da_serial_no is disconnected from the host.

added disk array da_serial_no

The disk array with serial number da_serial_no is connected to the host.

joined cluster clustername as slave node nodeid

This system has joined the cluster named clustername as a slave node. Its node ID is nodeid. Available only if the Volume Manager cluster feature is enabled.

joined cluster clustername as master node nodeid

This system has joined the cluster named clustername as a master node. Its node ID is nodeid. If the system was already in the cluster as a slave, it has now become the master node. Available only if the Volume Manager cluster feature is enabled.

left cluster

This system has left the cluster of which it was previously a member. Available only if the Volume Manager cluster feature is enabled.

OPTIONS

-c

Display disk group change events.

-d

Display disk change events.

-g diskgroup

Restrict displayed events to those in the indicated disk group. The disk group can be specified either as a disk group name or a disk group ID.

-f

Display plex, volume, and disk detach events.

-i

Display disk group import, deport, and disable events.

-m

Display multipath events.

-n number

Display the indicated number of vxconfigd events, then exit. Events that are not generated by vxconfigd (that is, connect, disconnect, and waiting events) do not count towards the number of counted events and will not cause an exit to occur.

-s

Display cluster change events. If the -i option is also specified, the imports and deports of shared disk groups will be displayed when a cluster change takes place. Available only if the Volume Manager cluster feature is enabled.

-t timeout

Display events for up to timeout seconds, then exit. The -n and -t options can be combined to specify a maximum number of events and a maximum timeout to wait before exiting.

-w wait_time

Display waiting events after wait_time seconds with no other events.

If none of the -c, -d, -f, -i, or -s options are specified, then default to printing all event types. If a disk group is specified with -g, display only disk group-related events.

EXAMPLES

The following example shell script sends mail to root for all detected plex, volume, and disk detaches:

checkdetach() { d=`vxprint -AQdF '%name %nodarec' | awk '$2=="on" {print " " $1}'` p=`vxprint -AQpe 'pl_kdetach || pl_nodarec' -F ' %name'` v=`vxprint -AQvF ' %name' -e \\ "((any aslist.pl_kdetach==true) || (any aslist.pl_nodarec)) && !(any aslist.pl_stale==false)"` if [ ! -z "$d" ] || [ ! -z "$p" ] || [ ! -z "$v" ] then ( cat <<EOF Failures have been detected by the VERITAS Volume Manager: EOF [ -z "$d" ] || echo "\\\\ failed disks:\\\\ $d" [ -z "$p" ] || echo "\\\\ failed plexes:\\\\ $p" [ -z "$v" ] || echo "\\\\ failed volumes:\\\\ $v" ) | mailx -s "Volume Manager failures" root fi } vxnotify -f -w 30 | while read code more do case $code in waiting) checkdetach;; esac done

EXIT CODES

The vxnotify utility exits with a non-zero status if an error is encountered while communicating with vxconfigd.

See vxintro(1M) for a list of standard exit codes.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1983-2001 Hewlett-Packard Development Company, L.P.