About once a week or so i get the alert shown below:
--------------
You have received this email alert because an event has occurred on your VNXe system of which you need to be aware and take action to correct. Thealert is:
Storage associated with storage resource xxxxxxxx is unavailable and requires a Storage Integrity Check
To learn more about this alert, open Unisphere and click Monitor > System Alerts and then click on the alert. You may also want togo to the System Health page (Monitor > System Health) to further investigate the situation.
------------
The weird thing about it is that about five minutes later I get another alert that the same resource is now operating normally. This always seems to happen after hours so i can never get in and check it before it clears itself. Everything under "System Health" is fine by the time i get in to check it. This alerts happens randomly for different storage resources and always clears itself up within about 5 mins.
Anyone else seeing anything like this? What do i check to see whats causing this alarm to go off and then clearing itself?
Just an update on this. I did open a ticket and was told to upgrade to a the latest version of code to resolve this. This was a known issue in older code as mentioned aboe. Since upgrading to latest code the problem has not popped back up yet.
I am not sure if you are still experiencing this alert sequence. If yes I recommend you contact EMC Technical Support via Live Chat from the VNXe Product Page or locally via Unisphere. EMC Technical Support can have this issue investigated for you.
We know there was a issue with older VNXe code, hence I would recommend to upgrade to the latest code available ie 2.1.3 and monitor it for sometime to find if you still receive these alerts.
Note : If you are in 2.0.3 or older code you need to first upgrade it to 2.1.0 and than proceed with upgrading it to 2.1.3
Further to Shivanand's guidance, we hae checked this with VNXe Engineering. Guidence from VNXe Engineering is that the forthcoming MR2 release, due sometime in March, should address concerns around this area.
In addition, if we could obtain the logs to confirm that the issue seen on this VNXe system is covered under the changes for MR2 that would be very helpful. Easiest way to provide logs are through VNXe Technical Support via Live Chat.
fishermc-woffor
61 Posts
1009
0
Posted February 6th, 2012 09:00
Just an update on this. I did open a ticket and was told to upgrade to a the latest version of code to resolve this. This was a known issue in older code as mentioned aboe. Since upgrading to latest code the problem has not popped back up yet.