[pkosch]

We are new to HMC and partitioning and are having a problem getting started. We set up the hardware with the HMC as a DHCP server then powered up the managed server. Unfortunately we had the cabling incorrect between the managed server and the hmc box. Realizing the mistake we powered down everything, changed the cabling and started again. The problem is that the HMC server does not see the managed server. The managed server now has an IP address of 192.168.2.147 on E0. It is a 9910 server. How do I get rid of that IP address so I can get this working?

[dthacker]

I think you need to power down the managed unit and do the infamous "pinhole reset" while connected to the HMC. Make sure all your LPARS, including VIO are shut off. You don't mention what your managed server is. I have a p570.

HTH

Dave

[pkosch]

Not sure what the pinhole reset is. The server is a P510.

[pkosch]

We found the pinhole. Did the reset and have the same ip address and no communication from the managed server and the HMC.

[KingofAIX]

you may need to do this:

shutdown the 510
reset the FSP dipswitch (it's tiny, and towards the back of the system board (just flip both dips (1 for each HMC port) and it'll be reset to defaults)

restart the host. you can shell out on the HMC (rt click in the background field, and select terminal/rshterm) and run lshmc -n

the clients= shows the IP addresses of all hosts that have recieved a DHCP address from your HMC. if this is empty, then you:

1. have configured the wrong interface for DHCP.
2. incorrectly cabled the HMC/FSP connection
3. something else


if you reset the dips, you can attach a notebook via any cat5 cable (the FSP handles xover and straight cables (slick huh?)) and set your IP address to something in the default network (192.168.2.147 FSP port1, 192.168.3.147FSP port2)

you can then attach with ASMI http to the default ip address (use your browser to connect to 192.168.2.147)

and figure out what address the fsp is at/reset the fsp

you do need to spend some time and verify that the interface on the HMC is indeed doling out DHCP, if not, see 1, 2,3

[ross.mather]

You can usually fix problems like this (not 100% sure for a p510) but hang a PC on the Sevice card with an IP setup that can access 192.168.2.147. Then you can reset the Service Card via the ASMI to use DHCP. To use ASMI point a web browser to https://192.168.2.147.

If the machine has a second Service Card port then it is IP address 192.168.3.147.

[gvoden]

I am having a similar issue with a p510... the guys who setup our first p510s didnt use DHCP for whatever reason, so we use static IPs... that's fine, however my problem is that we build our servers via the serial port and not HMC, so when u hook it up to HMC it finds it but cannot open a Terminal window.... how do i reset the server to be able to get the Terminal window through HMC ...?

[ross.mather]

Ahh when you install it via the Serail Line you are using the full machine just like a POwer4 machine. If you hang it on an HMC then it will probably disable the serial ports and expect you to define an LPAR.

This is a guess, but if you define an LPAR with all system resources you should be able to point it at the relevant disks to get it to boot. BE CAREFUL I haven't tried this so no guarantees....

[gvoden]

You have a point, I saw the servers that were working properly through HMC had 2 partitions, one disabled ( with the serial number of the server as a name ) and another one that had the actual server hostname... I was able to connect to that one using Open Terminal Window...
We don't really split the systems into many LPARs, hardly anyone knows much about them since we're primarily a Solaris shop (90%)... so these new AIX p5's are freaking us out heheh..

[gvoden]

I tried creating a new LPAR using all system resources and it actually worked. I checked the "open a terminal window" checkbox at the end of the whole process and actually got a terminal window popping up... another thing came up - I could see all the output of the system booting up but I don't get a login prompt after the AIX Banner scrolls up... any suggestions on that?
If you delete an LPAR does it have any effect on the underlying OS?