Jump to content
Robert Hornibrook

A script/plugin for iscsi disconnects, failed raid controller, bad sectors

Recommended Posts

I monitor for basic windows iscsi login failures and disk errors in all servers. The only boxes where I've actually seen disk errors occuring have been in Azure and ESX and the event monitors have picked them up when there really were errors.

iscsi drives missing

table: drives

field to check: missing

result: 1

additional condition: model like '%iSCSI%'

(we add iSCSI to the names of all iSCSI partitions on each machine)

I'll have to look up the others when I have battery....

 

Share this post


Link to post
Share on other sites

I monitor for basic windows iscsi login failures and disk errors in all servers. The only boxes where I've actually seen disk errors occuring have been in Azure and ESX and the event monitors have picked them up when there really were errors.

Monitor for iscsi drives missing

table: drives

field to check: missing

result: 1

additional condition: model like '%iSCSI%'

(we add iSCSI to the names of all iSCSI partitions on each machine)

 

Monitor for disk Errors:

Table to check: eventlogs

Field to Check: EventID

Check condition: Equals

Result: 153

Additional Condition: eventlogs.source='disk'

 

 

Share this post


Link to post
Share on other sites
On 11/19/2018 at 11:56 PM, Robert Hornibrook said:

So where in Connectwise would I have to write this script? What if your volumes aren't named Iscsi? 

 

You could either work this into an remote monitor or an internal monitor. your call. Those monitors you could setup through groups and searches.
It's based on eventlogs that are being generated.

I tink we setup an search that finds machines with the iscsi initiator installed and the service as automatic/running. And deploy eventlog remote monitor.

Share this post


Link to post
Share on other sites
4 hours ago, Wupsje said:

You could either work this into an remote monitor or an internal monitor. your call. Those monitors you could setup through groups and searches.
It's based on eventlogs that are being generated.

I tink we setup an search that finds machines with the iscsi initiator installed and the service as automatic/running. And deploy eventlog remote monitor.

Do you have an example of a remote monitor that picks up iscsi disconnect and sends an e-mail upon failure?

 

Share this post


Link to post
Share on other sites
On 12/13/2018 at 5:10 PM, Robert Hornibrook said:

Do you have an example of a remote monitor that picks up iscsi disconnect and sends an e-mail upon failure?

 

I looked but apparently we deleted this one.
You can easily set it up yourself. you can either search and find the eventlog on the agent that it happened on. Right click it and select Create Event Monitor.
Or you could create a monitor with the event id (39) and source iScsiPrt

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×