This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Configure Rollback
The Configuration Rollback feature allows the Change Management system to detect and recover from the following software/configuration errors by reverting to the previously active software/configuration:
- After a software upgrade, virtual Path is dead and the service gets disabled if the software crash happens.
- After making the configuration changes, virtual Path is dead without any software crash.
- If the configuration for the MCN appliance itself causes a network problem on the MCN site, it does not detect the outage and does not roll itself back. However, all the other clients in the network roll themselves back as they were unable to connect to the MCN.
The configuration rollback feature is enabled by default, to disable this feature clear Revert on Error option in the Activation tab of the Change Management wizard.
If a system configuration error occurs on a client while activating the staged package from an MCN the client reverts to the previous software configuration and an error message appears as shown in the following screenshot.
The client generates a critical severity event for the SOFTWARE_UPDATE object if an appliance crash is detected, or generates a critical severity event for the CONFIG_UPDATE object if a network outage is detected.
If Revert on Error is enabled, the client appliances monitor itself for about 30 minutes. If the software crashes within 30 minutes, or if the network is down (unable to establish a Virtual Path to the MCN) for 30 minutes, then a rollback is triggered.
On the MCN, an error message appears as shown in the following screenshot. As the clients rejoin the network, it reports the type of error encountered. A summary count of the number of errors is displayed in the error message.
In the Change Management window of the MCN, you can see the state of the site appliances indicating if that site had encountered a Software Error, or a Configuration Error.
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.