My guess is either you haven't had enough patience or you have a problem with the boot process somewhere.
ANS is basically an Apple badged IBM RS/6000 server. I know from using my own RS/6000 (and techfury90 will concur here I'm sure) that they take a long time (mine takes upwards of 5 minutes just to get to the initial boot screen) to perform the Power On Self Test sequence, because they do a thorough and exhaustive test at startup. As servers they were not designed to be power-cycled regularly, so any power-cycles were usually for upgrades or maintenance which both required comprehensive diagnostic on startup to establish if the messing around had worked or if it had damaged or disturbed anything.
Secondly it could be that somewhere the boot sequence or POST are failing. On true RS/6000s they display a 4-digit code on the LCD screen for every single stage of the POST and boot, so if it fails or stalls you can see what it's fallen over on. I do not know if the ANS had this feature, so I can't actually say to look for it, but it' an idea at least.
ANS is basically an Apple badged IBM RS/6000 server. I know from using my own RS/6000 (and techfury90 will concur here I'm sure) that they take a long time (mine takes upwards of 5 minutes just to get to the initial boot screen) to perform the Power On Self Test sequence, because they do a thorough and exhaustive test at startup. As servers they were not designed to be power-cycled regularly, so any power-cycles were usually for upgrades or maintenance which both required comprehensive diagnostic on startup to establish if the messing around had worked or if it had damaged or disturbed anything.
Secondly it could be that somewhere the boot sequence or POST are failing. On true RS/6000s they display a 4-digit code on the LCD screen for every single stage of the POST and boot, so if it fails or stalls you can see what it's fallen over on. I do not know if the ANS had this feature, so I can't actually say to look for it, but it' an idea at least.