Workaround: To avoid this issue, only the publisher should be selected for the first stage of the cluster upgrade process. Scenario: This issue occurs if subscribers are selected for upgrade at the same time as the publisher upgrade. Symptom: On the Cluster Update page, the notification sometimes stays at the reboot and migration stage even after the publisher upgrade is successfully completed. Workaround: Use the password from the previous partition when logging in to bootstrap the second partition.Ĭluster Upgrade and Update Table 2: Cluster Upgrade and Update Known Issues in 6.8.0 When the system reboots after the install-image command and the user tries to log in to initiate the bootstrapping process, the default password is not accepted. Scenario: This issue is seen after the user installs the new 6.8.0 image on a ClearPass hardware appliance, logs in to the appadmin CLI and executes the install-image command. Symptom: On a ClearPass hardware appliance, when the user tries logging in to initiate the bootstrapping process for a new partition, The default password is not accepted after the system install-image command is executed. For a list of known issues identified in previous releases, see Known Issues Identified in Previous Releases.ĭo not update to 6.7.10 or upgrade to 6.8.0 if you think your hardware appliance is affected by the issue described in the Aruba Support Advisory ARUBA‑SA‑-20190802_PL元02, “Failure to Boot after Upgrade/Update to 6.7.10 or 6.8.0,” and in CP‑34406 and CP‑34776 below. The following known issues were identified in the ClearPass 6.8.0 release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |