RE: when a ups doesn't help

Jim,

I try to make sure that equipment with redundant power supplies have
each power supply connect to a separate power strip.

This would have saved you, assuming your i5 has redundant power
supplies.

We have only a single large UPS for the entire computer room, so a
problem with it would bring down everything.  It'd be nice to take the
redundancy all the way and have two large UPS.  Then you could have each
power supply plugged into a separate power strip and each power strip
plugged into a separate UPS.  Heck take it a step further and have two
separate generators for each UPS ;-)

HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
> Sent: Wednesday, February 22, 2006 9:50 AM
> To: MIDRANGE-L@xxxxxxxxxxxx
> Subject: when a ups doesn't help
> 
> Had a customer plug a monitor power cord into same rack power strip
> that i5 was plugged into. This is a regular professional rack 
> with built in power
> strips. The whole rack, with i5, is covered by a large ups. 
> Power strip "blinked" (some 
> kind of electrical short) and next thing we know, i5 is 
> IPLing. The system value
> is set to re-ipl when power restored, so it did. Came up 
> fine, but management 
> asking how to avoid this. 
> Is it common to use a large ups for multiple equipment,
> or do most shops with comm, wintel servers, and i5 isolate 
> the i5 on a separate ups? 
> (and that ups would have to be within power cord distance from server)
> jim franz
> -- 
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>