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 ?

 

[Breslau]

if i recall correctly, you have to enable remote management of the p5 HMC while logged into the local HMC console. have you done anything like that?

 

[nogg123]

yes, it is enabled - i can get into it from a pc on the same lan, but not on another network,
i can ping it on the same lan, but not from another

that's why i think it's routing problem, but it is setup same as hmc next to it.

 

[Breslau]

did you try to 'traceroute' from the other LAN to this new HMC?

what sits between the two networks?

which LAN is the private one, with or without the HMC's?

 

[nogg123]

no, i haven't tracerouted, the other hmc, several aix boxes, several sun boxes and a hp netserver route just fine.

a 5308

there isn't a 'private' one - the p5 hmc defines it's own 'private' one, doesn't it?!

 

[Gloups]

did you check your netmask to be sure you're in the same net ?

 

[nogg123]

yes! its exactly the same as the hmc p4 next to it!
i can wsm in from the netserver on the same lan!

 

[Breslau]

the p5 hmc defines it's own 'private' one, doesn't it?!"

yes it does. you can set up a physical network for this, or use VLANS on you network. however, this is a seperate interface than what you use for remote HMC/node management. the private LAN is for HMC to managed host traffic.

assuming seperate physical networks, you'd need a LAN line run into your HMC, it should have 2 rj45 (ethernet) ports in it.

 

[nogg123]

i have tried to change the 1st ethernet address and when rebooted, it can't talk to the frame any more, as i suspected
i suspect it is a netmask clash between eth0 and eth1 as above, but i can't change the range of vpn addresses assigned, or the 'private' one without losing the frame.
i suspect the hmc will have to be re-installed choosing a different ip address at the beginning.....

 

[Breslau]

are you able to run a second LAN line to the eth1 port?

that way, you could use different address ranges for the two interfaces.

 

[nogg123]

yes, i have a 2nd lan into the eth1, thats how i already connect from a pc on the same lan ok
what i can't do is route out of this 2nd lan
i have a range of 192.168.2.* on eth1 which is allocated by the network dept and i can't change
and 192.168.0.* on eth0 which was alocated during install (i believe) and if i change this then the gui won't connect to show lpars etc.

WHAT I AM after is a procedure for re-installing the hmc cec connection using a different ip range on eth0 (IMHO)

 

[DukeSSD]

The eth0 lan should only be used for HMC to managed system communication. You don't want any other systems on this private lan.

Can the p4 HMC ping the p5 HMC and vice versa, on the 192.168.2 network?

 

[nogg123]

yes both hmc can ping each other and any other machine on 192.168.2

i have no other systems on eth0
it says it is private, but i think the netmask overlaps with eth1

 

[MoreFeo]

In the IP settings, there is a tick you must activate that says "Enable routed", I think in the last tab. If you don't have this option activated you can manage from the same LAN but not from outside it.

 

[nogg123]

i have already tried ticked and unticked - makes no difference.

 

[MoreFeo]

Usually problems with hmc remote connecting are: firewall, enabling routed and ports.
Hmc uses port 9090, but I think it also uses 3000 and 3001 while trying to connect. See if this ports are open.

 

[mrn]

Do you have a route to allow trafic between subnets?

Try adding a route on your PC

route ADD <destination IP> <Gateway_IP>

Mike

"Whenever I dwell for any length of time on my own shortcomings, they gradually begin to seem mild, harmless, rather engaging little things, not at all like the staring defects in other people's characters."

 

[nogg123]

my pc can route to the other hmc next to it and next address from it, so there isn't a route issue at my end - its at the new hmc end

the ports must be open as i can websm from the same lan

WHAT I AM after is a procedure for re-installing the hmc cec connection using a different ip range on eth0 (IMHO)

 

[DukeSSD]

have you loaded the i/p5 websm software on your local machine?
websm only works on systems up to the level of the system you loaded websm from.
reload your websm software on your local PC from the i5 HMC (it will support lower level HMCs still)
point your PC browser at the i5 HMC:

http://'i5

HMC hostname or ip address'/remote_client.html

 

[DukeSSD]

http://www-128.ibm.com/developerworks/eserver/library/es-websm/

might help.
go for the install shield, the java version reloads all of the websm code each time and takes ages to come ready.
don't forget you need to reload the websm client each time you try to connect to a newer level of HMC code than the one you downloaded the client from.
if your network is blindingly fast you could use the java version and then when you upgrade an HMC code level your PC will autamatically load the new websm client but I've never used a network fast enough to make the java client worth while.