Statically Configuring an FSP IP Address on POWER7 for Stable HMC Connectivity

This article describes how to assign a static IP address to the Flexible Service Processor (FSP) on an IBM POWER7 system when experiencing flapping connections from the Hardware Management Console (HMC). The recommended approach configures the static address on the second FSP port (usually labeled “HMC2”) while leaving the primary port (usually silkscreened as “HMC1”) on its existing dynamic/DHCP configuration. This method provides a stable secondary path and minimizes the risk of losing management access during the change.

POWER7 systems include two FSP Ethernet ports labeled HMC1 and HMC2. We will configure the static IP on the second port so that we can keep the primary port (HMC1) set to dynamic. This approach allows the existing HMC connection to remain functional on HMC1 while the new static configuration is tested on HMC2. It also provides a clear fallback path if any issues arise with the static settings.

Here's what you'll need before you begin.

• Administrative access to the HMC (hscroot or equivalent role).
• A target static IP address, subnet mask, and default gateway that does not conflict with the existing private network.
• ASMI login credentials (default is frequently admin / admin and I do NOT recommend changing them)
• Physical or network access to the FSP ports as needed and switchport/VLAN access for your laptop if you choose or are forced to use that method.
• Current FSP IP addresses and HMC private network settings documented before beginning. So, check the HMC settings no matter what the connection state is. It's the authority on it's DHCP segment.

Use this method when the current HMC connection remains stable enough to complete the session.

1. Log in to the HMC web interface.
2. Navigate to the managed POWER server system.
3. Launch the Advanced System Management Interface (ASMI) for the system.
4. Log in to ASMI.
5. Expand Network Services then select Network Configuration.
6. Choose the second interface (HMC2 or eth1).
7. Enable the option Configure this interface?.
8. Change Type of IP address to Static.
9. Enter the desired static IP address, Subnet mask, Default gateway, hostname, and domain information.
10. Review all values carefully.
11. Save the configuration.
12. Verify that the new static IP is active on HMC2 and test connection stability from the HMC (see lssyconn command example below and ping is also helpful).

Use this method when direct HMC access to the ASMI menu on your POWER server is unreliable or doesn't work. Connect a laptop to the private network segment used by the HMC and FSP ports.

On the HMC, run the following command as hscroot:

lssysconn -r all

This command displays managed systems and their FSP connection details. Typical output includes columns showing the system identifier, connection State (such as Connected), and the current IP Address assigned to the FSP. Use the output to confirm which IP addresses are currently in use and verify the systems visible to the HMC. Unfortunately, you may need to guess at the correct subnet mask: /24 usually works.

To view private network configuration details through the GUI:

1. Go to HMC Management → HMC Configuration → Customize Network Settings
2. Select the LAN adapter configured as Private.
3. Click Details.
4. Note whether the DHCP server is enabled and record the configured address range.
5. Note the HMC's own IP address on the private interface.

Common private network ranges on POWER7 HMCs include 192.168.2.0/24 and 10.0.255.0/24. The HMC typically uses the first address in the DHCP pool. Yes, you might need to randomly stomp on an IP with your laptop for a sec. Hopefully you choose a last octet in your IP way down past the number of servers you manage. Ie.. if you manage 30 servers and your private HMC backend subnet is 192.168.2.0/24 then maybe choose 192.168.2.75 as your laptop's temp IP address.

1. Assign the laptop a static IP address within the same subnet as the HMC private network (example: if the HMC private IP is 192.168.2.30/24, use 192.168.2.50/24).
2. Connect the laptop to the same VLAN/switch as FSP HMC2 is on (and it might also be the same VLAN as HMC1, no biggie). It's the private network segment the second HMC network interface is configured on. Your HMC manages this network segment's DHCP server thereon also.
3. Determine the current IP address of the connected FSP port (use Method 3 or common defaults such as 192.168.3.147 for HMC2).
4. Open a browser and navigate to

   https://<FSP-IP>

5. Log in to ASMI.
6. Follow the Network Services → Network Configuration steps from Method 1, selecting only the second port (HMC2 / eth1).
7. Set Type of IP address to Static and enter the target values.
8. Save the changes.
9. Update the HMC connection information if necessary so it recognizes the new static address on HMC2.

Use the operator panel when network access to ASMI is unavailable. This method primarily helps gather current IP information so that Method 2 can be used.

- Locate the operator panel on the front of the POWER7 system. - Enter Manual mode:

1. Use the arrow buttons to display function 02.
2. Press Enter.
3. Change the mode indicator from N (Normal) to M (Manual).
4. Press Enter to confirm.

- View FSP IP addresses using function 30:

1. Enter 30 and press Enter.
2. Use sub-functions to view addresses:
   • 3000 displays the HMC1 (eth0) IP address.
   • 3001 displays the HMC2 (eth1) IP address.
3. Record the addresses shown.

- Return the panel to Normal mode if desired by setting function 02 back to N. - It is possible to use the operator panel to set the FSP address as well. It's very frustrating and difficult.

1. Confirm the new static IP address using operator panel function 30 or the HMC command

   lssysconn -r all

2. Verify in the HMC that the managed system shows as Connected using the static address on HMC2.
3. Test long-term stability by monitoring the connection and, when safe, temporarily isolating the primary HMC1 connection.
4. Update any system documentation and cabling diagrams with the new static IP and port assignments.
5. Label ports and cables clearly for future reference.

This configuration establishes a stable, DHCP-independent connection on the secondary FSP port while preserving the original primary path. If flapping persists after these changes, examine physical cabling, switch port statistics, DHCP lease behavior on the HMC private network, or FSP firmware levels.