|
HMC. One HMC can easily be configured to control all 3 i5s. If you're in to redundancy/fault tolerance, you can put an HMC in each data center and configure each to control all 3 i5s. In that scenario, you'd not only have centralized control (using either HMC) but redundancy as well in case something happened to one HMC or to the link between data centers. Also, a big nod towards the HMCs is that if you do decide to LPAR later on, you've already got the management station(s) to handle it. BTW, you do not have to order IBM'$ KVM solution if you get a rack mount HMC. Any KVM (and KVM switch for that matter) should work fine so you can feel free to add it to the KVM switch you may be using with your Windows boxes. The only downside I've noticed on the HMC is that it seems to want to be rebooted every once in a while, like every few months. If you don't, when you do eventually reboot it will run a full disk scan (CHKDSK equivalent) that can take a while. I noticed this once when I powered down our rack to move it to a new data center (in the same building). When I brought it back up it said it had been more than 180 days since *something* and ran the CHKDSK equivalent as part of the boot process, keeping me from powering up the i5 for a few extra minutes. 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 ChadB@xxxxxxxxxxxxxxxxxxxx Sent: Monday, May 15, 2006 9:03 AM To: midrange-l@xxxxxxxxxxxx Subject: HMC or LAN Console For a non-LPAR shop running 3 different 520s in 2 different locations (2 at one site and 1 at the other), would you choose an HMC or a LAN Console setup? Reliability, security, and managability are the main concerns rather than a difference in cost. -- 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.