You really need to connect to HMC2, as HMC1 already has a new address, which
you don't necessarily know. If you go to option 30 off the front panel, you
will know what the HMC1 address is. You can set the HMC ETH0 to have be in
the same range and then get a connection.
Pete
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lukas Beeler
Sent: Thursday, February 12, 2009 3:57 PM
To: Midrange Systems Technical Discussion
Subject: Re: I/O Battery cache replacement problems
On Thu, Feb 12, 2009 at 21:26, Thomas Garvey <tgarvey@xxxxxxxxxx> wrote:
Yep. However, the HMC was not talking to the iSeries. It only saw an IP
address of 10.0.0.254 and the Status for that was No Connection. So, the
HMC could not be used.
10.0.0.0/24 is one of the default subnets for a private subnet for
HMC/FSP communication.
This is why you probably didn't know it.
In a default configuration, the FSP receives it's IP Address from the
HMC through DHCP. If you power on the FSP before the HMC, the FSP may
fail to get a DHCP lease from the HMC, most likely leading to the
problem you described.
Plug your laptop into the HMC port on your i, use the fallback default
IP (192.168.2.147, if i remember correctly), log onto the ASMI and
change the FSPs IP Adress.
Alternatively, power down your i, unplug the power, replug the power,
and then the FSP should get a valid lease from the HMC.
midrange.com
