Re: Can't reach HMC console remotely

[Kirk Goins <kgoins@xxxxxxxxxxx>]

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.