Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 118 Source: elxstor

The description for Event ID ( 118 ) in Source ( elxstor ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\RaidPort0.
This issue could occur in case of issue with SAN. In this case you have to restart related SAN port. afterthat also cluster node. After this action will be issue fixed.
Connect to the SAN switches, identify the right port for cluster node which indicates this issue with event IDs 1209 or 118 (maybe both) and perform a port reset. If this will doesn't help, power down both cluster nodes. Next start-up 1st cluster node and the the 2nd cluster node. After this action, the Microsoft Windows Cluster Service will be again up and running fine on both nodes. At the end, don't forget to divide the cluster resources as per your policies.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.