SEO

#1 (**permalink**) 01-05-2008, 11:33 AM

On Apr 9, 3:41 pm, "UncleSteve" <steve.stam...@foremost.com> wrote:
> In one environment I have two 570s each with their own HMC connected
> via ethernet cable. I'm adding some new systems to this environment
> and want to put all the systems and HMCs into their own VLAN so any
> HMC can talk with any system. Anyone know of any bumps in the road?
>
> My only concern is the DHCP service on the HMCs. Are each smart
> enough not to issue an address that already exists?

The proper target configuration in this case is to have two VLAN's -
one
will connect the first HMC to the HMC1 ports on the managed systems
(primary HMC), the other will connect the second HMC to the HMC2 ports
on the managed systems (backup HMC). The IP address ranges used
by the HMC's should be different; this is not an absolute requirement
since the VLAN's are physically separated, but will prevent confusion.

In order for this transition to happen without any service
interruption, the
HMC1 ports of your existing systems need to be in the same IP address
range, but have different IP addresses. The same applies to the HMC2
ports. If your HMC's currently use the same IP address range, chances
are that the managed systems are assigned the same IP addresses.
You can verify this with the 'lssysconn -r all' command on the HMC.

If the above requirement is not satisfied, at least one of the
existing
systems will need to re-acquire its IP address via DHCP. Unfortunately
this means down time, i.e. physically unplugging the power from the
system.

Regards,
Dmitri

#2 (**permalink**) 01-05-2008, 11:33 AM

Dmitri Pasyutin wrote:
>
> If the above requirement is not satisfied, at least one of the
> existing
> systems will need to re-acquire its IP address via DHCP. Unfortunately
> this means down time, i.e. physically unplugging the power from the
> system.

I think that with 570 firmware (SF225_096_096?) from the last year or so, a
power off isn't necessary. IIRC, there's a "network scan" function on the HMC
(don't have one in front of me at the moment, so I can't confirm). You might
need to know the HMC connection password (to the service processor), which can
be reset via ASMI if you don't know it.

--
steve stackwick
sstackwick@jasi.com
---------------------------------------------------------------------------
The social dynamics of the net are a direct consequence of the fact that
nobody has yet developed a Remote Strangulation Protocol. -- Larry Wall

#3 (**permalink**) 01-05-2008, 11:34 AM

On Apr 9, 9:48 pm, Stackwick <Stephen.Stackw...@jhuapl.edu> wrote:
> I think that with 570 firmware (SF225_096_096?) from the last year or so, a
> power off isn't necessary. IIRC, there's a "network scan" function on the HMC
> (don't have one in front of me at the moment, so I can't confirm). You might
> need to know the HMC connection password (to the service processor), which can
> be reset via ASMI if you don't know it.

Haven't seen this in the firmware history, but you are right according
to this
article:

http://www-1.ibm.com/support/docview...72210059d1 c5

It is an iSeries support article, but I suppose it should work for
pSeries also.
Apparently, a power off was needed before firmware 230. Now it is
sufficient
to disconnect the FSP network port for 2 minutes in order to force it
to
acquire a new IP address.

To complement my first reply, there is also this article which talks
about
redundant HMC confgurations:

http://www-03.ibm.com/support/techdo...Index/TD102463

Regards,
Dmitri

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: Moving HMCs to VLAN