Re: Can't reach HMC console remotely -- MIDRANGE-L

2 HMCs, 2 iSeries, 2 data cneters. One HMC & iSeries in each data center.
Each HMC is direct-cabled to the local iSeries' FSP. Each HMC is also
cabled to the LAN/WAN. By doing this each HMC can see/control both iSeries
and we have full remote admin capability both to each HMC and from each HMC
to the iSeries.

It's been forever since they were installed but I seem to recall the DHCP
only applying to the Ethernet port that was direct-cabled to the iSeries.
It's never been an issue for us.

On Wed, Mar 18, 2009 at 10:52 AM, <William.Epperson@xxxxxxxxxxxxxxxxxxxxxxxx

wrote:

We have 3 HMC's here. One is at another building across town and two are
in this data center. One HMC is dedicated to our iSeries machines and the
other HMC is dedicated to the pSeries machines. The two pSeries HMC's
share a routed private vlan and can see everything, both for redundancy
sake.
All of the HMC's have a private lan for the HMC to system connection and
the other port is connected to our internal network so that we can do the
web
based HMC management thing.

I think you may want to just purchase a small switch and plug all of your
HMC connections into that private little switch and let the servers talk to
the HMC to their hearts content. That way, you get your DHCP connectivity
and your network guy stops flipping out.

Good luck,
Bill Epperson Jr.
Systems Communications Analyst
Memorial Health System
(719) 365-8831

rob@xxxxxxxxx

Sent by: midrange-l-bounces@xxxxxxxxxxxx
To

Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>

cc
03/18/2009 09:46

Subject
Re:
Can't reach HMC console remotely
Please respond to
Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>

That's one possible configuration. We only have one cable coming out of
our hmc and we can ping it, and our FSP from our network.

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

From:
Kirk Goins <kgoins@xxxxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
03/18/2009 11:33 AM
Subject:
Re: Can't reach HMC console remotely
Sent by:
midrange-l-bounces@xxxxxxxxxxxx

Thomas Garvey wrote:

Can't say when I'll get to this. I'm also a little suspicious of our
network configuration. The network guy keeps telling me that the HMC
Console can NOT be allowed to be a DHCP server, but the IBM docs tell me

it

must be. I'm trying to figure out how to tell the boss there's another

HMC

upgrade but I can't guarantee that will allow me remote access either.

If YOU find an answer before hearing from ME, I'd appreciate a heads up

as

well.

Thanks.

Thomas Garvey

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Debora Wagner
Sent: Monday, March 16, 2009 1:32 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Can't reach HMC console remotely

Hello Thomas,

I seem to be in the same boat as you. I recently upgraded the HMC to
v6r1.3 myself and cannot connect to the HMC over VPN. Its too slow and

just

times out. At least, that is what I think. I can connect to the console

work

station, but again, it is soooooooo slow. Worse than dial up.

I'd like to hear if you find a solution. And upgrading to version 7

right

now is not an option.

Thank you,

Debbie Wagner
iSeries Administrator/IS Department

Rittal Corporation
1 Rittal Place
Urbana, Ohio 43078
<mailto:dwagner@xxxxxxxxxxxxxxx>
Website: www.rittal-corp.com <http://www.rittal-corp.com/>

Friedhelm Loh Group

This email contains confidential information. You are not authorized to

copy

the contents without the consent of the sender.***

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

Sorry I'm a little late on this thread and if I repeat things already
said... If this is the ONLY HMC and it's in the same rack as the
system... then it shouldn't be a problem. The connection between the HMC
and the system should be just 1 cable from the HMC (eth0) to the HMC1
port on the system. That is the entire network where the DHCP server
will be used. The System FSP will get its IP address via DHCP from the
HMC. No other machines shuld even be able to see the DHCP server. There
will be a second cable from the HMC (eth1) to your corporate network
where you will most likely have assigned a Static IP that is correct for
that network.

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

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