This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Chiming in as I would like an option to mute this alarm condition for the hosts related to the full system flash copy process.
After some thinking, may be an option per host "Suspend alerts for this hosts (or this host connection)" are sufficient.
I agree that filtering or monitoring by host is a better approach. Some examples in common configurations are: Recovery hosts for SGC - in the Cybervault solution, SGC should be cloned, mounted and verified frequently - these will be alternately online/offline. Flash copy hosts where a flashcopy is mounted and backed up - again frequently online/offline. A slightly different case is Alternate WWPNs for Power Live Partition Mobility - these are an alternate set of NPIV addresses that are used when a partition is moved from one Power hardware platform to another - these always appear offline - which shows as an error in the GUI and can hide real connectivity issues. Defining them as part of the normal host always has half down and shows degraded all the time. Defining them as separate hosts shows Offline most of the time. Currently there is no good solution that does not indicate an false positive error.
I agree with the suggestion Host Attibut "Do not monitor this host"
We also have a number of customers who are experiencing the problems associated with this message. If these messages are ignored for the reasons already mentioned, there is a risk that messages worth processing will be overlooked and not processed.
I agree with the suggestion Host Attibut "Do not monitor this host".
Maybe even "Do not monitor status of this host" would be better.
I have also a situation at customer, but the solution on top is dangerous. It hit all hosts and some alerts are important!
But I think to have an option to just have a button that says 'Do not monitor this host' in the dmp. will be a much better way. It is much more sensible and give the customer the chance to decide witch host. May there is a host, there will be for testing or recovery and will be often planed rebooted or offline. You can reduce regular alerts where you know what will happen and can focus on important alerts there are not planed.