Home > Troubleshooting > Network Adapter disconnects fail to alert in OpsMgr 2007

Network Adapter disconnects fail to alert in OpsMgr 2007

This came up in the forums and Jonathan Almquist gave a great answer.

“There is a problem we’re currently investigating in the Data Source in the Network Adapater Connection Health monitor. This monitor type uses an event log detection before pass-thru to a script diagnostic. The event log provider is not configured correctly, in that we will never detect the events and allow the script to process the diagnostics. The reason why this monitor works when you perform a recalculation from Health Explorer is because we don’t use the Data Source in recalculations. We pass-thru directly to the script in this case. The script works fine, and will detect health of the adapater. Keep in mind that there are additional parameters the script takes to diagnose certain adapter “disconnect” conditions.

The logic of the script is as follows:

Select * from Win32_NetworkAdapter

If ((MediaDisconnectionFlag = true) And (oWmiObj.NetConnectionStatus = 7)) or
((DisconnectionFlag = true) And (oWmiObj.NetConnectionStatus = 0)) or
((HardwareFlag = true) And (oWmiObj.NetConnectionStatus = 6))

Then set state and generate alert.”

Advertisements
Categories: Troubleshooting
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: