|
Completed my first Online Import job this past week/end. Did one 8400 and another 4400 to two 7200s. Thought I'd pass along an important lesson learned....
I got an error message when tried migrating my first Windows cluster that stated "Host Set Creation Failed."
I submitted insplore logs to software support and this is what they found:
Time : 2013-09-21 13:43:54.72 CDT
Node : 1
Seq : 196972
Class : Notification
Severity : Minor
Type : CLI command error
Component: sw_cli
Message : {3paradm super all {{0 8}} -1 192.168.8.5 13216} {Command: createhostset Host_set_TESTDW_LUN10_Pr_Log R07_U27_DL580 R07_U31_DL580 R07_U35_DL580 Error: Name Host_set_TESTDW_LUN10_Pr_Log is too long, should be less than 28 characters} {}
A little decipher:
TESTDW_LUN10_Pr_Log is a vdisk
R07_U27_DL580 R07_U31_DL580 R07_U35_DL580 are host names
What happens is that the Online Import Wizard knows this is a cluster (through the explicit / implicit method used in migration) and tries to a create Host Set on 3par, but it uses the names of vdisks to name the Host Set. I simply tried to rename just that particular vdisk, and the Wizard still failed. Weird. So, I renamed all the vdisks to make them 18 characters or less (factoring in the 9 character prefix 'Host_set_')
Just wanted to share...
|
