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: 4523 Source: ClusSvc

Source
Level
Description
Majority Node Set resource has failed a status check for file share"\\abcdef\clustername". The error code was "53". Please ensure that the file share is configured properly and that the cluster service account has write permission on the file share.
Comments
 
In my case, the event description mentioned Error code 53. This event could be fixed very simply via command line and Cluster command. The root cause is that arbitrator of cluster clx is not configured properly in my case it was due to decommissioning of 3rd ( arbitrator server) and the cluster configuration was not changed to the new server.

(CLX are using arbitrators like 3rd nodes - but it is simply share on 3rd server in 3rd, separate datacenter).

You can use these commands to fix the problem:
- cluster res / priv
- cluster res MNS (could be another resource name ) / priv resource name=server name where is share/directory prepared

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 www.eventid.net.

Read more...

 

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.

Read more...