VVR event notification


		< Previous \| TOC \| Index \| Next >

VVR event notification

VVR provides the vrnotify utility to notify administrators of VVR specific events, such as SRL full, resynchronization complete, etc. You can receive notification for a VVR event on the Primary or Secondary node, or both the nodes in an RDS.

The vrnotify command enables you to write a script that receives VVR event notification and notifies administrators of these events through email, pager, etc. See the examples in this section to see how event notifications can also be used to keep history of various events.

If you do not specify the local_rvgname in the vrnotify command, event notification is started for all the RDSs on the local host. If any of the RDSs have RVGs in a shared disk group, vrnotify provides notification about events on the logowner for those RVGs. Use the -g option to receive event notifications for RVGs in a specific disk group.

The vrnotify command displays the VVR events until you explicitly terminate or kill the command.

To receive event notifications on the Primary or Secondary, enter the following command:

# vrnotify -g diskgroup local_rvgname....

The argument local_rvgname... is a space-separated list of the names of the RVGs on the local host in the specified disk group.

The vrnotify command displays each event on a new line in the following format:

host_name:event_type:RDS_name:event message

For an RVG in a shared disk group, host_name is the logowner, and the displayed event information reflects activity on the logowner host.

The vrnotify command displays the following types of events:

Event Type	Event Message
`resync_started`	Resync started on Primary RVG
`resync_stopped`	Resync stopped on Primary RVG
`resync_paused`	Resync paused on Primary RVG
`lat_throttle_on`	Latency throttling started
`lat_throttle_off`	Latency throttling stopped
`lat_throttle_override`	Latency throttling overridden
`lat_throttle_fail`	Latency throttling caused I/O failures
`srlprot_throttle_on`	SRL overflow protection throttling started
`srlprot_throttle_off`	SRL overflow protection throttling stopped
`srlprot_override`	SRL overflow protection overridden
`srlprot_fail`	SRL overflow protection caused I/O failures
`srl_overflow`	Replication stopped due to SRL overflow
`srlprot_dcm_on`	Started using DCM for SRL protection
`srlprot_dcm_off`	Stopped using DCM
`rlk_connect`	RLINK connected to remote
`rlk_disconnect`	RLINK disconnected from remote
`srl_log_warn`	SRL percentage full has changed by 10%
`repmode_sync`	Replicating in synchronous mode
`repmode_async`	Replicating in asynchronous mode
`repibc_freeze`	Replication on Secondary frozen due to IBC
`repibc_unfreeze`	Replication on Secondary unfrozen after IBC
`rvg_pritosec`	RVG role changed from Primary to Secondary
`rvg_sectopri`	RVG role changed from Secondary to Primary
`rvg_pritoactsec`	RVG role changed from Primary to acting Secondary
`rvg_actsectopri`	RVG role changed from acting Secondary to Primary
`rlk_paused`	Secondary RLINK paused because of a configuration error
`ibcmsg_discarded`	IBC was discarded due to timeout on the Secondary.

Example:

The following example script shows how to use the vrnotify utility to receive event notifications for the hr_rvg RDS in the hrdg disk group and send email to the alias vvradmin if the event srl_warning occurs.

#!/bin/sh

IFS=:

vrnotify -g hrdg hr_rvg | while read host event rvg msg

case $event in

srl_log_warn)

(echo "This message is sent by VVR notify mechanism"

echo "$msg for RVG $rvg on host $host"

) | mailx -s "VVR SRL Log Warning" vvradmin;;

esac

done


^ Return to Top	< Previous \| TOC \| Index \| Next >