SCOM 2007 R2 sending Failure Notifications for all decommissioned devices.
Step in troubleshoot the issue
1) monitor for trigger the alert: 192.168.1.5 Printer which is not the built-in monitor and is a custom monitor
2) Check whether you has hard code the device IP
192.168.1.52 for monitor (192.168.1.5 Printer)
3) Remove the monitor entity
192.168.1.52 from the monitor
Roger
July 12th, 2012 10:45am
I've inherited a SCOM 2007 environment 6 months ago and have had issues regarding the removal of decommissioned devices from SCOM. When I remove a network device by right clicking and deleting the device all seems to be well, however once every 6 weeks
or so I receive email notifications stating that the devices I have removed are unavailable.(as seen below) Whenever I search for the devices or try to set an override for the devices, I cannot find them in the Operations Manager. My SCOM environment is not
clustered and I can't seem to find an answer as to why this is happening. I believe this is a simple Ping Monitor, but cannot locate the deleted items to disable their notifications. Any assistance would be greatly appreciated in pointing me in the direction
to disable these phantom device failure notifications. At this time I have 8 deleted items throwing these notifications.
Failure Notification
Monitor Status
Last Test
Thu, 12 Jul 2012 03:54:23
Last Status
Server timed out
Up / Down Time
0:00 min / 26:55 min
Alert
2 of 3
Concurrent Failures
6
Type and Addressing
Monitor Name
192.168.1.5 Printer
Monitor Type
PING
Base Address
192.168.1.52
Port
Timing and Alert Parameters
Test Frequency
300 seconds
Test Frequency (alert state)
300 seconds
Maximum Test Duration
300 seconds
Notify Every X Failures
3
Send a Maximum of X Alerts
3
Comments
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2012 8:20am
I think I may have just fixed my own problem by running the SQL Monitoring Cleanup Script found in this link from Kevin Holman.
http://blogs.technet.com/b/kevinholman/archive/2009/12/21/tuning-tip-do-you-have-monitors-constantly-flip-flopping.aspx
I won't know officially until 4-6 weeks from now, but the script did reset my retention days to the correct time. Before running the script it was set to 340, after running the script it was reset to 7 which is correct.
Thanks,
MD
July 14th, 2012 8:50am
Step in troubleshoot the issue
1) monitor for trigger the alert: 192.168.1.5 Printer which is not the built-in monitor and is a custom monitor
2) Check whether you has hard code the device IP
192.168.1.52 for monitor (192.168.1.5 Printer)
3) Remove the monitor entity
192.168.1.52 from the monitor
Roger
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2012 10:02am
Hi,
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios.
In addition, wed love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.
Thanks,Yog Li
TechNet Community Support
July 25th, 2012 10:59pm