|
The reasonable approach: 1. Multiple UPSes for redundancy, not to break out iSeries vs. rest-of-world. 2. Redundant PDUs in the racks, each fed off a different UPS and each on it's own circuit. 3. Redundant PSUs in the servers. Higher-cost options: 4. Generator(s) to backup one or all of the UPSes. 5. Each UPS/generator fed from a different power grid. If a UPS or PDU goes belly-up, the equipment in the rack should not go down. Don't forget to provide backup HVAC power. Or, if not, configure everything to auto-powerdown when they go to UPS power. There are some devices, like KVMs, that typically don't have the option of redundant power. For those, if needed just swing the power cord to the surviving PDU or live without. Of course it's good to test the UPSes once in a while. Ditto the generators if you've got them. We do 1-4 as a minimum in our production data centers; 1-3 for DR. John A. Jones, CISSP Americas Information Security Officer Jones Lang LaSalle, Inc. V: +1-630-455-2787 F: +1-312-601-1782 john.jones@xxxxxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Haase, Justin C. Sent: Wednesday, February 22, 2006 9:10 AM To: Midrange Systems Technical Discussion Subject: RE: when a ups doesn't help In my experience, bigger shops = bigger UPSes. Economies of scale. Keep your System i5 on separate circuits from things being switched on and off and you won't have the problem which occurred today. (Monitors, laser printers, etc...) -- Justin C. Haase - iSeries System Engineer IBM Certified Systems Expert - eServer i5 Kingland Systems Corporation -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Piotrowski Sent: Wednesday, February 22, 2006 9:04 AM To: Midrange Systems Technical Discussion Subject: RE: when a ups doesn't help Hi Jim, That has always been common practice around our shops. The AS/400 has it's own UPS and the remaining Wintel servers all operate under their own UPS grid. We're by no means a big shop (2 AS/400s, 8 Wintel servers), but I would have to guess the bigger shops might operate in the same fashion. Brian. -----Original Message----- From: Jim Franz [mailto:franz400@xxxxxxxxxxxx] 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. -- 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. CONFIDENTIALITY NOTICE: This e-mail communication, including attachments, is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential, and may be legally privileged. If you are not the intended recipient or believe you received this communication in error, please reply to the sender indicating that fact and delete the copy you received. In addition, retention, dissemination, distribution, copying, or otherwise use of the information contained in this communication is strictly prohibited. Thank you. -- 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. This email is for the use of the intended recipient(s) only. If you have received this email in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this email without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. The information contained in this communication may be confidential and may be subject to the attorney-client privilege. If you are the intended recipient and you do not wish to receive similar electronic messages from us in future then please respond to the sender to this effect.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.