[edtrumbull]

I would like to have my hmc tell all its clients to refresh their dhcp leases, especially since it thinks that one system has two different addresses, the one it assigned and the default. I KNOW that the system doesn't have two hmc connections -- I just looked. Besides, I'm missing a system or two.

So, is there a way for the dhcp server on the HMC to tell all clients "drop your lease and re-lease --NOW"?

[FASherman]

From what I have been able to find, no. The thinking by IBM is that the HMC network is (or should be) a closed secure network.

They do recognize that the two IP scenario can occur, and they give steps on how to remove stale info:

To identify manually assigned IP addresses when the HMC is configured as a DHCP server, do the following

1. Create a list of all of the configured HMC IP connections. On the HMC command line, type the following command:lssysconn -r all This command displays the following information for service processors and Bulk Power Cards (BPCs) on the private network for which the HMC has configured IP connection:element type, MTMS, IP address(es), connection state
2. Make a note of all IP addresses that are displayed. You will need these addresses later.
3. Display a list of the DHCP IP addresses that have been assigned. To do this, type the following HMC command:lshmc -n -F clients The client= keyword in the output of this command lists all IP addresses that have been assigned by the HMC’s DHCP server.
4. Make a note of all IP addresses that are listed in the output.
5. Make a note of other servers that are managed by this HMC that use static IP addresses.
6. Compare the lssysconn and lshmc lists. If an IP address is displayed in the output for both the lshmc -n -F clients and lssysconn -r all commands, the IP address was assigned by the HMC DHCP server and the connection is being managed by the HMC DHCP server.
7. Remove from the list any address that is displayed in the output of the lshmc -n -F clients command but not displayed in the output of the lssysconn -r all command, and is not in the list of servers that use static IP addresses.

Note: If an IP address is displayed in the lshmc -n output and not in the lssysconn -r all output, that IP address was assigned by the HMC DHCP server. However, it is not a current connection on the HMC. The DHCP server keeps a history of all IP address assignments in the event that the connection is re-established. The DHCP server might also have assigned an IP address if an unknown device on the private network requested a DHCP IP address from the HMC.

[edtrumbull]

Thanks. I'll take a look at that and see if it solves the problem.

[edtrumbull]

What works is to disconnect the HMC clients and reconnect them one at a time.
It's recommended that you give them at least a minute between disconnect and reconnect. That, apparently, is long enough for them to flush their leases and get new ones.

Then, you wait - as patiently as possible - a few minutes (5? less than 10, I think), and voila, your client will reconnect itself to the HMC. Reenter the password, if you've changed it, and off you go.

[FASherman]

Typical IBM.