Unisphere for VMAX: eMgmt:  unable to delete performance alert

           

   Article Number:     503436                                   Article Version: 4     Article Type:    Break Fix 
   

 


Product:

 

Unisphere for VMAX,Unisphere for VMAX 8.3

 

Issue:

 

 

Screenshot of Alert   

SMAS.log on MGMT-0 (Server-1, not present in Server-0):2017-08-18 19:37:10,100 WARN  [em.bp.ALERTS] (EJB default - 5) AlertCacheManager.findAlertsByKeys:Failed to resolve AlertKey='{e120220b-2c46-43a8-878b-706c479xxxx (Channel='PERFORMANCE', ID=--S0)}.'.2017-08-18 19:37:10,100 WARN  [em.bp.ALERTS] (EJB default - 5) AlertCacheManager.findAlertsByKeys:Failed to resolve AlertKey='{85bf5ef9-47d3-403c-99cc-900a0e7xxxxx (Channel='PERFORMANCE', ID=--S0)}.'.2017-08-18 19:37:10,100 WARN  [em.bp.ALERTS] (EJB default - 5) AlertCacheManager.findAlertsByKeys:Failed to resolve AlertKey='{72045346-0cfc-4b50-85e2-d91190daxxxx (Channel='PERFORMANCE', ID=--S0)}.'. SMAS.log on MGMT-1 (Server-1, not present in Server-0):2017-08-18 19:37:10,099 WARN  [em.bp.ALERTS] (EJB default - 5) AlertCacheManager.findAlertsByKeys:Failed to resolve AlertKey='{2ace4545-4a59-42d6-8e4c-363aba6xxxxx (Channel='PERFORMANCE', ID=--S0)}.'.2017-08-18 19:37:10,100 WARN  [em.bp.ALERTS] (EJB default - 5) AlertCacheManager.findAlertsByKeys:Failed to resolve AlertKey='{e120220b-2c46-43a8-878b-706c479cxxxxx (Channel='PERFORMANCE', ID=--S0)}.'.2017-08-18 19:37:10,100 WARN  [em.bp.ALERTS] (EJB default - 5) AlertCacheManager.findAlertsByKeys:Failed to resolve AlertKey='{85bf5ef9-47d3-403c-99cc-900a0e7xxxx (Channel='PERFORMANCE', ID=--S0)}.'.                   
                                                             

 

 

Cause:

 

 

Its a nasty bug that can occur whenever there is a change in the set of VMAXs that U4V is managing (discover new VMAX, symmavoid a VMAX, etc).                                                             

 

 

Resolution:

 

 

This has been resolved in Unisphere for VMAX 9.0.0.