|
o
|
Device attach and detach events, provided by the operating system (OS)
|
|
On Solaris, vxesd registers with the Reconfiguration Coordination
Manager (RCM) and the sysevent framework to integrate seamlessly with
the Dynamic Reconfiguration (DR) cfgadm utility so that vxesd
receives notifications before a device is removed from the system and when
a new device is attached to the system.
|
|
When vxesd receives a notification that a device is
being removed, vxesd checks whether the device is in use by
Veritas Volume Manager (VxVM) or DMP. If the device is in use, vxesd
notifies RCM about it to prevent removal of the device. If VxVM or DMP
is not using the device, vxesd notifies DMP that the device is
being removed from the system.
|
|
When vxesd receives a notification about a new device arrival,
vxesd triggers a VxVM device discovery with vxconfigd,
so that the device becomes available for use by DMP and VxVM.
Use the dmp_monitor_osevent tunable parameter to turn on or off the vxesd functionality to monitor OS events.
|
o
|
Fabric events from Fibre Channel SAN
|
|
vxesd uses the SNIA HBA API library to obtain information
about the Fibre Channel SAN and to register for event notifications from
SAN that reach the HBA. On receiving a SAN disruption notification,
vxesd notifies DMP about a likely failure in the affected
part of the SAN.
|
|
Use the dmp_monitor_fabric tunable parameter to turn on or
off the vxesd functionality to monitor fabric events.
|
o
|
Events from the DMP driver.
|
|
vxesd also registers for notifications from the DMP
driver. On receiving these notifications, it logs these
events with the exact time stamps in a circular log file. The
log files are located at /var/adm/vx/dmpevents.log.*
|
|
By default, VxVM starts