Re: HMC Question, Private LAN netmask

[DrFranken <midrange@xxxxxxxxxxxx>]

Rob,

   I guess you would put me in that 'Paranoid' group. Likely this comes 
from the early days of HMC where mistakes bit back hard. In addition 
since that connection is to an absolutely positively critical piece of 
my infrastructure I simply am not interested in that communications 
being disrupted. Keeping it on a private network reduces the chances 
that will happen. Having said that I have no issue with a properly built 
VLAN (or physical lan if you prefer) that contains all my FSPs and HMCs 
and I have customers who have extended that VLAN to other facilities for 
more HMCs and FSPs. This provides HMC redundancy between facilities and 
gives me the flexibility to add more FSPs by simply allocating ports in 
the switch. As for being able to get to ASMI from anywhere in the 
network without going first to the HMC, not gonna happen in my networks.

 - Larry "DrFranken" Bolhuis


On 12/16/2010 11:46 AM, rob@xxxxxxxxx wrote:
> I know that some feel that the connection between the HMC and the FSP
> should be on some private network.  I've never been that paranoid.  I put
> all my FSP's on the same subnet (while they are in the same building) that
> the HMC's (and some other equipment) are on.
>
> I can ping the FSP's and HMC's from any PC in our intranet.
>
> Doing this makes it easier to share HMC's between racks.  And, finally,
> we're planning on moving our backup rack offsite.  We'll have one hmc in
> one city and one in another and want to be able to control either rack
> from either HMC.
>
> Rob Berendt