Re: Virtual HMC connection

[Pete Helgren <pete@xxxxxxxxxx>]

So the vHMC was a bit of a challenge.  First, getting the ova imported 
into vSphere was interesting (ESXI 5.1 [old]) but it runs fine.  The 
networking options did throw me though.  When I installed the wrong 
version initially, I chose "Open" but then the IP address of the FSP in 
the documentation kind of threw me (no DHCP server on the vLAN).  So, 
when I finally installed the correct vHMC version I chose "private" but 
then had to fire up a DHCP server to assign the address to the FSP.  The 
DHCP server triggered alerts on our network that there was a rogue DHCP 
server so, after successfully connecting to the FSP I then set static 
private addresses and turned off the DHCP server.  All is well. It's 
private in the logical sense, on a different network address block that 
my IBM i resources, but it's all plugged into the same switch.  There is 
nothing but my old BCS and my new P9 on that vLAN so it isn't a big 
issue for me.

It would be nice to have some discussion about the pros and cons and the 
implementation challenges of private vs open in the documentation.  But 
there was just enough info for me to get it working....

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
Twitter - Sys_i_Geek  IBM_i_Geek

On 6/7/2019 8:53 AM, DrFranken wrote:
> It's not just security it's reliability. 99.99% of the time there is 
> no issue.  Switches are up. Network is happy. Life is good. And then 
> there is the time when murphy hits a home run and your DC goes dark. 
> Now you gotta get things a goin again and, well crap. The network boys 
> are staring at a big switch with a bigger problem. Your HMC is up, 
> your POWER System is sitting with a blinking green but the two ain't 
> talkin. For the price of an Ethernet cable. *sigh*.
>
> And you think this don't happen??? HA!  I have been standing next to 
> these two clowns. Them: "How?? This is a $250,000 Cisco switch with 
> redundant EVERYTHING!" Me: "Not any more." (The DC manager nearly 
> exploded with laughter.)
>
> And you say: But if the network is down users can't get on either. 
> True that, but often you might have hours of work to do to get the 
> database and applications happy again. Getting that started is on the 
> critical path.
>
> And it's security too of course. The entire world knows that the only 
> users for ASMI are admin and general. So if that thing is open they 
> can bang away at those two users until they get in. Or more likely 
> lock them. However, ff they do get in well the keys to the making of 
> the mayhem are in their hands.
>
> So cable the way you'd like as it's your systems.
>
> Me: Private network every time.
>
> For Pete he's not in that situation and open network for this is not 
> an issue.
>
>         - Larry "DrFranken" Bolhuis
>
> www.Frankeni.com
> www.iDevCloud.com - Personal Development IBM i timeshare service.
> www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
>
> On 6/5/2019 11:25 AM, Rob Berendt wrote:
> > I use an open network to connect my HMC to my Power systems.  Some 
> > prefer the hardwire method under the belief that it's ok for your 
> > payroll, drawings, etc to be on your network but heaven forbid your 
> > systems management access port be on your corporate network.
> > https://www.ibm.com/support/knowledgecenter/en/POWER9/p9hai/p9hai_prephmc.htm 
> >
> >
> > Rob Berendt