Configuring WS EventingThe WS Eventing protocol is used for a client service (subscriber) to register interest (subscription) with a server (event source) forreceiving messages containing the server events (notifications or event messages). Clients interested in receiving the WS Eventingmessages can subscribe with iDRAC and receive Lifecycle Controller job related events.The steps required to configure WS Eventing feature to receive WS Eventing messages for changes related to Lifecycle Controllerjobs are described in the Web service Eventing Support for iDRAC 1.30.30 specification document. In addition to this specification,see the DSP0226 (DMTF WS Management Specification), Section 10 Notifications (Eventing) document for the completeinformation on the WS Eventing protocol. The Lifecycle Controller related jobs are described in the DCIM Job Control Profiledocument.Configuring Redfish EventingThe Redfish eventing protocol is used for a client service (subscriber) to register interest (subscription) with a server (eventsource) for receiving messages containing the Redfish events (notifications or event messages). Clients interested in receiving theRedfish eventing messages can subscribe with iDRAC and receive Lifecycle Controller job related events.Monitoring chassis eventsOn the PowerEdge FX2/FX2s chassis, you can enable the Chassis Management and Monitoring setting in iDRAC to performchassis management and monitoring tasks such as monitoring chassis components, configuring alerts, using iDRAC RACADM topass CMC RACADM commands, and updating the chassis management firmware. This setting allows you to manage the servers inthe chassis even if the CMC is not on the network. You can set the value to Disabled to forward the chassis events. By default, thissetting is set as Enabled.NOTE: For this setting to take effect, you must ensure that in CMC, the Chassis Management at Server setting must beset to Monitor or Manage and Monitor.When the Chassis Management and Monitoring option is set to Enabled, iDRAC generates and logs chassis events. The eventsgenerated are integrated into the iDRAC event subsystem and alerts are generated similar to the rest of the events.CMC also forwards the events generated to iDRAC. In case the iDRAC on the server is not functional, CMC queues the first 16events and logs the rest in the CMC log. These 16 events are sent to iDRAC as soon as Chassis monitoring is set to enabled.In instances where iDRAC detects that a required CMC functionality is absent, a warning message is displayed informing you thatcertain features may not be functional without a CMC firmware upgrade.Monitoring chassis events using the iDRAC web interfaceTo monitor chassis events using the iDRAC web interface, perform the following steps:NOTE: This section appears only for PowerEdge FX2/FX2s chassis and if Chassis Management at Server mode is set toMonitor or Manage and Monitor in CMC.1. On the CMC interface, click Chassis Overview → Setup → General.2. From the Chassis Management at Server Mode drop-down menu, select Manage and Monitor, and click Apply.3. Launch the iDRAC web interface, click Overview → iDRAC Settings → CMC.4. Under the Chassis Management at Server section, ensure that Capability from iDRAC drop-down box is set to Enabled.Monitoring chassis events using RACADMThis setting is applicable only for PowerEdge FX2/FX2s servers and if Chassis Management at Server mode is set to Monitor orManage and Monitor in CMC.160
