vxesd - Dynamic Multi-Pathing (DMP) event source daemon
The event source daemon (vxesd) registers with various sources of device-related events on the system. When vxesd receives notification of these events, it takes the appropriate actions. The vxesd also obtains information about the Fibre Channel and iSCSI SAN configuration for DMP.
The vxesd registers to the following event sources:
By default, VxVM starts vxesd at boot time. To stop the vxesd daemon, use the vxddladm utility:
o Device attach and detach events, provided by the operating system (OS) On Linux, vxesd registers with the UDEV framework and keeps DMP up_to_date with device arrival and detaches. When vxesd receives a notification that a device is removed from the system, vxesd notifies DMP about the change. 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. 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.*vxddladm stop eventsourceTo start the vxesd daemon, use the vxddladm utility:vxddladm start eventsource [logfile=logfilename]
The vxesd daemon is started with the current values of dmp_monitor_fabric tunable. When this tunable is changed, the vxesd daemon is restarted with the changed value.
vxconfigd(1m), vxddladm(1m), vxdmpadm(1m), Storage Foundation Administrators Guide