feature restore failed. Look at the specific feature log file under
/usr/local/ibrix/setup/
logs/
for more detailed information.
To retry the copy of configuration, use the command appropriate for your server:
◦
A dedicated management console:
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade -f
◦
A file serving node:
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade –s
◦
An agile node (a file serving node hosting the agile management console):
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade –f –s
•
If the install of the new image succeeds, but the configuration restore fails and you need to
revert the server to the previous install, execute
boot_info –r
and then reboot the machine.
This step causes the server to boot from the old version (the alternate partition).
•
If the public network interface is down and inaccessible for any node, power cycle that node.
Manual upgrade
Check the following:
•
If the restore script fails, check
/usr/local/ibrix/setup/logs/restore.log
for
details.
•
If configuration restore fails, look at
/usr/local/ibrix/autocfg/logs/appliance.log
to determine which feature restore failed. Look at the specific feature log file under
/usr/
local/ibrix/setup/logs/
for more detailed information.
To retry the copy of configuration, use the command appropriate for your server:
◦
A dedicated management console:
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade -f
◦
A file serving node:
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade –s
◦
An agile node (a file serving node hosting the agile management console):
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade –f –s
Troubleshooting upgrade issues
77
