Loading...
Loading...
Some iAppLX package files on primary blade do not exist on secondary blades.
When a failover occurs to a blade with an incomplete iAppLX package, parts of the iAppLX GUI may not work.
After installing an iAppLX package on a multi-blade chassis the package files are synced to other blades. This process is not instantaneous and may take several minutes. During this time if the same iAppLX package is upgraded, not all of the files will be synced across blades, and an incomplete iAppLX package will exist on secondary blades.
To trigger a resync of files from primary to secondary blades run the following command: bigstart restart csyncd
The system now syncs files from primary to secondary blades in this scenario.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.