There is a new option in  clmgr  to handle this change: clmgr modify event PREPOSTFAILS=true The pre and post event commands run in the foreground, although the notify service always  runs in the background. To access the cluster events SMIT pane, run  smitty sysmirror , and then click  Custom  Cluster Configuration  Events  Cluster Events  Change/Show Cluster Events , as  shown in Example 2-11. Example 2-11 Cluster Events SMIT pane Change/Show Cluster Events Type or select values in entry fields. Press Enter AFTER making all desired changes. [Entry Fields] Event Name  network_down Description Script run when a network has failed. * Event Command  [/usr/es/sbin/cluster/events/network_down] Notify Command  [] Pre-event Command  []  + Post-event Command  []  + Fail event if pre or post event fails?  No  + F1=Help F2=Refresh  F3=Cancel F4=List F5=Reset F6=Command  F7=Edit F8=Image F9=Shell F10=Exit  Enter=Do  As shown in Example 2-11, you can now specify the pre and post commands directly  because there is no need to separately create custom events. Thus, PowerHA V7.2.3 no  longer supports a recovery method and count. Cluster verification also checks that the pre,  post, and notify event commands exist and are executable. Example 2-12 shows a successful pre-event command processing. <LAT>|2019-01-21T19:06:43|8296\|EVENT START: admin_op clrm_start_request 8296 0|</LAT> <LAT>|2019-01-21T19:06:46|8296\|EVENT COMPLETED: admin_op clrm_start_request 8296 0 0|</LAT> <LAT>|EVENT_PREAMBLE_START|TE_JOIN_NODE_DEP|2019-01-21T19:06:48|8297|</LAT> <LAT>|NODE_UP_COMPLETE|</LAT> <LAT>|EVENT_PREAMBLE_END|</LAT> <LAT>|2019-01-21T19:06:50|8297\|EVENT START: node_up node1|</LAT> <LAT>|2019-01-21T19:06:50|8297\|NOTIFY COMMAND: /usr/local/scripts/node_up_notify node1|</LAT> <LAT>|2019-01-21T19:06:50|8297\|PRE EVENT COMMAND: /usr/local/scripts/node_up_pre node1|</LAT> <LAT>|2019-01-21T19:06:50|8297\|EVENT COMPLETED: /usr/local/scripts/node_up_pre node1 0|</LAT> <LAT>|2019-01-21T19:06:51|8297\|POST EVENT COMMAND: /usr/local/scripts/node_up_post node1|</LAT> <LAT>|2019-01-21T19:06:51|8297\|EVENT COMPLETED: /usr/local/scripts/node_up_post node1 0|</LAT> <LAT>|2019-01-21T19:06:51|8297\|NOTIFY COMMAND: /usr/local/scripts/node_up_notify node1|</LAT> <LAT>|2019-01-21T19:06:51|8297\|EVENT COMPLETED: node_up node1 0|</LAT> Chapter 2. New features  39 Example 2-12 Output of a pre-event command processing