× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Chris,

I don't prefer your approach because it adds another device (the DHCP server) in the HMC to FSP network that must be maintained, could cause issues, and is not needed if IBM were to allow us to specify the HMC address and a netmask. Hard coding the FSP address means I have to fire up the thing with a laptop connected, go into ASMI and change the addresses. Again a step not needed if I could simply assign the FSP to HMC network in the HMC.

By that's just the way *I* think.

- Larry "DrFranken" Bolhuis

On 12/16/2010 11:25 AM, Chris Bipes wrote:
That would be nice but not necessary. Don't use the Private network but
define it as public. This turns off the DHCP service and forces you to,
1. Provide your own DHCP server or 2. Hard code the FSP and HMC IP
address.

Hard code the IP address is my preference and then I put both into a
VLAN on a switch. I can add switch ports to the VLAN as I add systems.
This also allow you to provide routing between the local HMC and a
remote HMC / iSeries. Really makes the configuration more flexible.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.