Well, occasionally, devices don’t like me. Like today, on a C7000 G2 blade enclosure’s OA:
OA-68...> connect server 3 Connecting to bay 3 ... Connection terminated by server. OA-68...> connect server 3 Connecting to bay 3 ... Connection terminated by server.
Mortimer, there’s no fun anymore …
Google showed some other poor soul did have it’s experience with those thingies – why not give it a try? This blade enclosure isn’t yet productive, after all …
Yeah, right, fun ahead:
OA-68...> reset bay 3 WARNING: Resetting the server trips its E-Fuse. This causes all power to be momentarily removed from the server. This command should only be used when physical access to the server is unavailable, and the server must be removed and reinserted. Any disk operations on direct attached storage devices will be affected. I/O will be interrupted on any direct attached I/O devices. Entering anything other than 'YES' will result in the command not executing. YES Successfully reset the E-Fuse for device bay 3. OA-68...> connect server 3 Request is valid only for SERVER blades. OA-68...> connect server 3 Request is valid only for SERVER blades. OA-68...> connect server 3 Invalid MP IP Address: 0.0.0.0 Operation failed.
During this, I witnessed the blade in question to vanish from the OA’s web interface view and resurface. But this did not cure the connecivity issue:
OA-68..> connect server 3 Connecting to bay 3 ... Connection terminated by server.
Fsck. I really refuse to give in and use the damned web frontend, which would, after some tweaking, work, so: Any hints on why this bloody excuse for technology refuses to obey my commands are greatly appreciated …
(Needless to say: I worked with exactly this kind of technology already successfully in Asia; why it now fails on me in Europe I do not understand, yet …)