RE: Second HMC

["Jones, John (US)" <John.Jones@xxxxxxxxxx>]

Do the words "winging it" and "hmc" really belong in the same paragraph?

Sorry I can't help, but I am interested in how it turns out.  We should
be walking down that same path in June when we replace our DR 830 with a
570.  I want the HMC on each 570 to be able to control both systems.

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: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] 
Sent: Friday, April 08, 2005 1:54 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Second HMC

I have an HMC controlling both a 520, and a 570.

I have a second HMC that I want to attach.

Currently all of this equipment is in the one machine room.  Future
plans are to move the 520 and one of the HMC's offsite.

Any gotcha's I need to be aware of when hooking up a second HMC?  I was
planning on just stepping through the wizard and winging it.  Along with
my network guy to hook up the hmc to the lan and to hook up the
secondary port on the 520 and the 570 to the lan also.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
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 the future then please respond to the sender to this effect.