Re: Adding DASD to a 520

[DrFranken <midrange@xxxxxxxxxxxx>]

Even simple stuff that should be NO ISSUE can cause problems 'just 
because'. Case in point a customer had an Ethernet card in a model 300 
years ago. Their network wasn't ready for it yet so I told them they 
could connect the cable at any time. They did, and the system went down 
flat. So how do you explain an Ethernet cable taking down the system? 
Well I couldn't but some time later we moved that system and discovered 
the cables connecting the two cabinets had something wrong in them. When 
the cover was removed to add the Ethernet the slightest bump of those 
interconnect cables clobbered the system. Nothing at all to do with 
connecting the network cable besides the proximity.  Another case just 
this year where a 16 way 570 (six racks wide) went 'carbonite' when an 
IBM CE, doing exactly what he was supposed to do, moved a cable ever so 
slightly and that was the end of that.

Point being that even if you do in fact know exactly what needs to be 
done with drives or cards you also must have 'awareness' of the rest of 
the server, and what's around it in the racks.

  Larry "DrFranken" Bolhuis
  www.frankeni.com
  www.iDevCloud.com

On 7/8/2010 8:08 AM, rob@xxxxxxxxx wrote:
> Should have seen the interesting spark when I tried to plug in an ASCII
> workstation controller on to the wrong card a decade or so ago.  Pin outs
> looked alike.  I didn't fess up to IBM for quite some time as to what
> could have possibly made that card stop working.
>
> So even the "easiest" stuff could have interesting results.
>
>
> Rob Berendt
>