Numéro d’article: 494137

printer Imprimer mail E-mail

ViPR Controller: Reoccurring pending "Actionable Events" after upgrade to 3.5

Résumé: ViPR Controller: Reoccurring pending "Actionable Events" after upgrade to 3.5, Disable the Discovery of the Linux Host.

Produit principal: ViPR Controller Controller 3.5

Produit: ViPR Controller plus…

Dernière publication: 20 mars 2020

Type d’article: Break Fix

État publié: En ligne

Version: 5

ViPR Controller: Reoccurring pending "Actionable Events" after upgrade to 3.5

Contenu de l’article

Problème


Pending Actionable Events keeps on reoccurring after upgrading to ViPR Controller 3.5:

User-added image

 

 

Cause
Manually created cluster of discoverable Linux hosts generate Actionable event to remove the host from manual cluster after every discovery cycle. 
 
Résolution

 If we 'Disable the Discovery of the Linux host' and the actionable events will not get generated during every discovery cycle.

Edit the Hosts that the actionable events gets triggered on and Uncheck the "Discoverable" option and then Save.
After that the Automatically discovered information from the host regarding IP Interfaces and Initiators would be disabled for this host(s).

The impact of disabling the discovery for these hosts would be just that if initiators (HBAs) are replaced for the host, then we will not be generating Actionable Events. In case of HBAs replacement for these hosts, then we can enable the discovery for these hosts and approve only the HBA replacement Actionable Events.

Notes

Problème


Pending Actionable Events keeps on reoccurring after upgrading to ViPR Controller 3.5:

User-added image

 

 

Cause
Manually created cluster of discoverable Linux hosts generate Actionable event to remove the host from manual cluster after every discovery cycle. 
 
Résolution

 If we 'Disable the Discovery of the Linux host' and the actionable events will not get generated during every discovery cycle.

Edit the Hosts that the actionable events gets triggered on and Uncheck the "Discoverable" option and then Save.
After that the Automatically discovered information from the host regarding IP Interfaces and Initiators would be disabled for this host(s).

The impact of disabling the discovery for these hosts would be just that if initiators (HBAs) are replaced for the host, then we will not be generating Actionable Events. In case of HBAs replacement for these hosts, then we can enable the discovery for these hosts and approve only the HBA replacement Actionable Events.

Notes

Article Attachments

Pièces jointes

Pièces jointes

Propriétés de l’article

Première publication

jeu. janv. 05 2017 12:56:39 GMT

Première publication

jeu. janv. 05 2017 12:56:39 GMT

Noter cet article

Précis
Utile
Facile à comprendre
Avez-vous trouvé cet article utile ?
0/3000 characters