hmc remote access

[nogg123]

i have a p4 hmc which I can access remotely with wsm etc. just fine.
I have aquired access to p5 hmc on a i570 which was previously for as400 but will now run aix as well, but i wasn't around during it's setup.
i can wsm into it on the same lan, but cannot remotely, so i suspect a routing problem but it is on the same lan as the p4 one and has the same default gateway.!?

does a private lan affect an open lan?
the private lan is 192.168.0.1/b
and the open lan is 192.168.2.6/c

I notice a lot more firewall in the p5 hmc setup could this be preventing access ?

 

[wsw3]

Hi,

What type of connection exists between the HMC and the 570? direct? VLAN? Hub?

Are there multiple frames being managed by the HMC?
Is the HMC configured as a private DHCP server on eth0?

If the 570 is the only frame connected to the p5 HMC and the HMC is a private DHCP server, you can change the address range to whatever you like on eth0 (under network settings), reboot the hmc (to activate the change), and then run mksysconn -o auto from a command line on the HMC. This will dynamically instruct the 570 to acquire a new address from the HMC. You will need to clean up any old addresses which were previously distributed by the HMC using rmsysconn.

In order to accomplish this, you may need to know the HMC access password to the FSP because the frame may fail authentication after you change the address range. As long as you have it (set it previously), this will work with no problems.

The main thing to consider is the connection method between the HMC and the frame(s). If you control it (via a private hub switch, direct connection, etc..), then you can change it at will. Otherwise, you may need to involve your network folks.


HTH

 

[DukeSSD]

If the p/i series system has firmware older than SF235 the above may not work without powering off the system, I mean powering off, a reboot will not do.
It was only from SF235 that the managed systems would reapply, via dhcp from the service processor (fsp - flexible service processor) for a new IP address without a complete FSP powerdown and reboot!

 

[wsw3]

I've got p570s at much older levels than SF235 on which I performed these steps successfully.

It will work unless the frames in question are 575, 590, or 595s. Those frames require power cycles because they contain internal hubs.

 

[nogg123]

thanks for all your help

i seem to have fixed it now.
i shutdown powered off the hmc
shutdown the cecs
pulled the power to cecs & hms
pulled the ethernet from hmc to cec

powered on hmc
changed ip on hmc and rebooted
connected power & ip to cecs
can now use .2.2 address and partions are visible
it still has 192.168.0.2 in display but appears to work ok