RE: Twinax?

I can't speak for Rob's setup but we use the 2 Ethernet ports on the back of 
the i5.  One goes to the local HMC and the other goes to the network where it's 
routed to the remote HMC.

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 Marc Rauzier
Sent: Wednesday, March 29, 2006 8:52 AM
To: Midrange Systems Technical Discussion
Subject: RE: Twinax?

Le mer. 29 mars 2006 16:22:14,  écrivait:

> And the two hmc's,
> one at one site and one at the other, and either one can control 
> either i5 is not just theory.  We do it in practice.
> 

Rob,

we have a problem with this setup.

Do you use one ethernet port of the servers to connect to the first HMC, and 
the other ethernet port of the servers to connect to the second HMC ?

Or, do you use only one ethernet port of the servers to connect to both the 
HMCs ?

We were in the second situation until V4R5 release of the HMC and after an 
upgrade to V5R1M1, it does not work anymore. Note that the first HMC is DHCP 
server for the private network in our settings.

--
Cordialement/Best regards
Marc Rauzier

Opinions I stated here are my own.

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