[Sajid Ikram]

Hello ALL,

I am new to this technical forum. We are managing two p5 servers using separate HMCs. Each management host have two logical partitions. In order to achieve improve availablity, we want to network both management hosts and HMCs. After this we can easily manage both management servers using any HMC. If anyone guy have performed this activity successfully, please provide me tips.

Thanks in advance.

Regards,
Sajid Ikram

[ross.mather]

You have two choices:
1. Put each HMC on a different VLAN and manage the machines via different HMC ports on the service cards

2. Put everything on one VLAN and let one HMC be your DHCP server

Which one you choose is up to you.

[john.samons]

HI Sajid,

This should be quite easy.

Which model of HMC do you have and how many available network ports on the HMC do you have?

Is your HMC connected to the public network?

How far apart is the equipment from each other?

Best Regards,
John Samons

[Sajid Ikram]

HMC1 Model : 7310-CR3 IBM x336 having two ports,
(One port for web-based system manager remote client,other for management host)
HMC2 Model : 7310-CR4 IBM x336 having two ports
(One port for web-based system manager remote client,other for management host)

Current each HMC is directy connected (i.e. point-to-point using cross cable) to respective p5 server. Both pair are physically apart, but our network team provide cabling through switch. Our network team will create a differenct VLAN for communication between management hosts and HMCs. Is it necessary to create different VLAN for each HMC port in managed server. Also I am not interested in setting up DHCP setup. I just want to use static IPs.
Regards,
Sajid Ikram

[ross.mather]

Use DHCp - its better for you when someone adds a server later. I STRONGLY urge you to use DHCP!

Sounds like you want a single VLAN where all the Servers and both HMCs are connected to the VLAN.

[john.samons]

Ok, obviously you still want WebSM access, so leave the HMC's on the public network, however take the port being used for the managed systems and connect it to, lets say, a 8 port switch. Calling it swA for this example.

Then do the same with the other HMC, however it requires it's own 8 port switch (swB)

Are you referring to non-DHCP for the HMC WebSM? Your WebSM port will still be static, however you can setup your private network to be DHCP.

If this is ok, then select a DHCP address range on the ether card on the HMC for the private network. The address range should be different on BOTH HMC's, as they will function as DHCP servers on the private network.

When this is done, reboot HMC's and connect the each p5 server to both switches. i.e.both HMC1 ports to swA and both HMC2 ports to swB


Now sometimes the p5 server will not be seen on the HMC as the service processor doesn't release the IP and select a new one via DHCP. Depends on your firmware levels It actually acquires an address during service processor boot time.

During your maintenance slot, you can shutdown both p5's, remove power. Replace power and then boot them. They should be now visible from both.


IF you really want to have the private network static as well, you can do it. But you should do this only if your network environment REALLY REALLY requires it. It's more complex...

Setup your HMC's to use two different subnets on the private network, then. you should log onto ASMI and change the IP address of HMC1 & HMC2 ports, again onto the two different subnets.

Hope this helps...

Best Regards,
John Samons

[Sajid Ikram]

We can not run DHCP in our environment. Our network team has approved for a single VLAN. For the time being, this project is delayed. I will contact you guys then.

Thanks all guys for your responses.

Regards,
Sajid Ikram