Re: Spec for New V7R1 Development Machine/Remotely Racked -- MIDRANGE-L

Rob, are you always using the shared (route) or do you ever use the
dedicated route?? I seldom use the shared key route myself.

On Wed, Feb 16, 2011 at 1:46 PM, <rob@xxxxxxxxx> wrote:

Bryan,

You've yet to address my repeated concern. The OP is not going to be able
to physically touch his HMC. It will be stored in an offsite location.
Yes, the remote web rocks in 7.1. Yes, the ability to take over a shared
console session is good. However, if you IPL the entire rack (like for a
firmware upgrade, massive power failure, hardware upgrade) then all shared
sessions drop. Or, like the OP, you will be creating new lpars in the
future and those will need a new console session. And it really sucks to
be in the middle of an OS install or a RCLSTG, or a full system save, and
have the comm drop and kill your session. If, however, you started the
shared session first (by using the KVM) then if the comm drops using the
traditional shared session you can get right back in.

I did some on the side work for a company. They just had a single lpar
with Lan Console. But when they got it up and running it was all going to
an offsite hardened location ran by a third party. A room that other
people use. Building with armed guards and customers are just not
allowed to enter the building. The fact that it is your computer is
irrelevant. Situations like this may call for drastic measures. Like, do
you get a power strip with remote capability so that you can physically
power off and on a device?

I have an HMC controlling 3 racks: 9117, 9408, 8203. Each rack has
multiple lpars. 10 total of i and 2 of linux between all three racks. If
I drop all lpars on the 9117, and then IPL the 9117 to put on a firmware
upgrade, I've lost my console sessions to each lpar. When I start a new
shared session remotely my big clue is that I have to enter the shared
console session password twice. That reminds me that I better hope and
pray that my comm doesn't drop, or I'd be better off driving the four
miles and starting the shared console session there before beginning the
long running job.

Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: "Burns, Bryan" <Bryan_Burns@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 02/16/2011 12:58 PM
Subject: RE: Spec for New V7R1 Development Machine/Remotely Racked
Sent by: midrange-l-bounces@xxxxxxxxxxxx

I disagree. What if the KVM fails? What if your keyboard (say it's a
Dell) doesn't play well with the KVM - HMC interface? I've been there.
It sucked using an expensive Avocent KVM with Dell flat screen and
keyboard.

Get the IBM console and put it under 24/7 maintenance. It's the front
end to your system!

Y'all are so IBMCentric I'm surprised you're recommending something
other than IBM.

B Burns

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Wednesday, February 16, 2011 6:42 AM
To: Midrange Systems Technical Discussion
Subject: Re: Spec for New V7R1 Development Machine/Remotely Racked

You don't need the monitor/keyboard that lists for about $3k. Use your
own KVM keyboard/mouse/monitor for it.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC

On 2/15/2011 9:44 PM, Richard Schoen wrote:

OK, I just saw the first pass at the config.

Is an HMC console with monitor really $9K ?

Yikes !!

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence Email:richard@xxxxxxxxxxxxxxx Web
Site:http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
----------------------------------------------------------------------

message: 1

--
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.