Virtual Console FCD-CFxx Informations techniques Page 52

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 920
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 51
2.1.20.6 RDU8508 : "CMC<slot number>: cannot failover since the other CMC is non-
functional."
When event is generated, message will have the following substitutions:
<slot number> = ""
2.1.20.7 RDU8509 : "CMC<slot number>: cannot failover, chassis is in non-redundant state"
When event is generated, message will have the following substitutions:
<slot number> = ""
2.1.20.8 RDU8510 : "CMC<slot number>: cannot failover, CMC firmware versions are
different"
When event is generated, message will have the following substitutions:
<slot number> = ""
2.1.20.9 RDU8511 : "Unable to failover, CMC<slot number> in unknown state."
When event is generated, message will have the following substitutions:
<slot number> = ""
2.1.20.10 RDU8512 : "CMC<slot number>: firmware versions are different [<local fw version>
<factory revision> : <remote version> <factory revision>]"
When event is generated, message will have the following substitutions:
<slot number> = ""
2.1.20.11 RDU8513 : "CMC<slot number>: firmware versions are same <fw version> <factory
revision>"
When event is generated, message will have the following substitutions:
<slot number> = ""
2.1.20.12 RDU8514 : "CMC<slot number>: cannot failover, firmware update is in progress."
When event is generated, message will have the following substitutions:
<slot number> = ""
2.1.20.13 RDU8515 : "CMC<slot number>: failover was initiated by internal health monitoring
process."
When event is generated, message will have the following substitutions:
<slot number> = ""
2.1.20.14 RDU8516 : "CMC<slot number>: failover initiated by RACADM interface."
When event is generated, message will have the following substitutions:
52
Vue de la page 51
1 2 ... 47 48 49 50 51 52 53 54 55 56 57 ... 919 920

Commentaires sur ces manuels

Pas de commentaire