You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*** This is a system generated ticket, please do not reply. Please contact support for any assistance. ***
IBM Cloud engineers are conducting a technology refresh project aimed at increasing the cloud host stability and reliability. Customers who are receiving this maintenance ticket have Virtual Server Instances (VSIs) or NetScaler VPX on cloud hosts which are scheduled to be emptied and updated. The identified VSIs/NetScaler VPXs need to be migrated to different cloud hosts in order for IBM Cloud engineers to conduct the maintenance.
Reservations for all affected VSIs/NetScaler VPXs have been made on new cloud hosts. Customers are asked to self-migrate their VSIs.
NetScaler VPX Customers:
For NetScaler VPX customers, the migration date must be coordinated with Cloud Support for their NetScaler VPX before the scheduled date above. Any VSIs not self-migrated or NetScaler VPXs not migrated will be automatically migrated beginning at the time above. All migrations are disruptive regardless of their types like self-migration or auto-migration.
Please make sure to contact support and coordinate your preferred date for NetScaler VPX migration before the scheduled date above. Support will migrate your NetScaler VPX.
Issue #2 - XenTools must be updated to the latest version in order for your device to be migrated during the above maintenance without going offline.
RISKS:
For both issues, IBM support engineers have observed BSOD failures, boot issues, networking failures, and failures during various boot stages during a migration.
NEXT STEPS:
Issue #1 - Disable auto updates for the XenTools package in Windows Update and perform a manual update of XenTools using the following instructions. https://www.ibm.com/support/pages/node/6462327
Issue #2 - Once XenTools is updated to the latest version, migrations to a new platform will no longer be blocked, and can proceed as described above.
The text was updated successfully, but these errors were encountered: