Unix Revolution

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

Recently I had a huge debacle involving a USS7110, which happens to be a Sun x4240 with ZFS, moderately over-glorified ;-) As a result of the disaster I was essentially pulling the mirror disk from my alternate system (uss02) and putting it into my primary system (uss01) to get that system running again. Simple enough... I guess. The problem I ran into, and this will be specific to the USS only, is that the drives in the array are either identified as "system" or "data" (which you can see from the BUI). During my drive swapping, I had pulled the "data" spare, and mirrored the "system" OS disk to it. Somehow it left the data disk-type stamp on it. The drive mirrored fine and all, but when I would go to create a new zpool, the OS drive would appear to be a valid disk to put the data on. I obviously didn't go through with that step, but I can't imagine what would happen if I had. Chances are you will never be in the position ...