IBM Support

Power HMC V10R3 View: Configuring HMC for Use on a Private and Open Network

How To


Summary

This document provides steps to configure the Hardware Management Console (HMC) for use on a dual network. This process assumes that the HMC being used has two Ethernet adapters installed.

Objective

Configure network interfaces on the HMC/vHMC

Environment

7063-CR1 V10R3M1050
7063-CR2 V10R3M1050
vHMC on x86 V10R3M1050
vHMC on Power V10R3M1050

Steps

 The following document provides steps to configure the Hardware Management Console (HMC) for use with the recommended private/open network. The recommended configuration is to configure eth0 for remote HMC access, call home, and dual HMC and/or HMC/partition communications and configure eth1 as a private network for management of the server(s). This is a change from prior recommendations, and pertains to Power HMC's. This document applies to HMC Version 10 R3 M1050 only.
****If you have a 7063-CR2, first review this link for better understanding of using eth0, and plan accordingly. 
image-20240201165619-1
 Select HMC Management => Network Settings.
 image-20240201162022-1

A . Select the Identification tab.

1. The console name should be the host name of the HMC as configured in the DNS.
2. The domain name should be must be filled in ( xxxxxx.com or xxxxxx.org).
3. Make a note of the domain name because it is required later on the Name Services tab.
 B. Click on the LAN Adapters tab:
image-20240201162541-2
 Eth0 should be used for the Open LAN. Eth1 should be used for the Private LAN. This is a change from prior releases, and considered best practice.
Selecting Ethernet eth0 and clicking on Details provides the following options.
image-20240201163341-4
Notes:
1.
eth0 specifies the open network and has access to the location's intranet. Access to the Internet using the location's intranet is allowed and actually preferred for future use of service related functions. Private should not be selected here.
2. DHCP server may not be selected here (open network).
3. The HMC can obtain an address using DHCP (automatically) or use a static TCP/IP address (preferred). Specify the correct subnet for static TCP/IP address.
4. For media speed, autodetection should be selected except for the case when the network switch adapter is connected to, is set to FORCE FULL DUPLEX. Then set full duplex.
 
Repeat for eth1. Below is the details panel for eth1: 
image-20240201162847-3
Notes:
1. Selecting Private makes this the eBMC/FSP's local network.
2. Enable DHCP to make the HMC a source for TCP/IP addresses on the Private network.
3. Select the address range. If two HMCs manage the same server, each HMC must use a unique DHCP Server Address range. Do not select an address range that is used on or overlaps an address range used on the open (intranet) network..
4. Specifying a TCP/IP address should automatically get filled in with the base address of the DHCP range filled in above in the DHCP frame of this window. 192.168.128.1 is one below the 192.168.128.2 which is the beginning of the DHCP range. Different ranges may use a different base address, however, the TCP/IP address is filled in automatically for a private LAN when DHCP is selected above.
5. For media speed, use autodetection exclusively except for the case when the user's switch is set to FORCE FULL DUPLEX. Then set full duplex.
 

Click on Firewall to view and/or customize firewall settings for the selected interface. Example for eth0, might be, 
 
image-20240201163738-5
Notes:

1. In the Firewall tab, select additional services from the top list box. Typically only Secure Shell and Secure Remote Web Access needs to be added.

2. Click the Allow Incoming button to allow access from any IP address.
** You can also verify the Remote Control options are enabled by checking the boxes. Go HMC Management screen - Example
image-20240229140857-1


Once the firewall options have been set for eth0, check the Domain Name Services settings by clicking on the Name Services tab in the Change Network Settings:
 image-20240201164311-7
Notes:
1. A DNS server is optional but recommend. (This will be needed for call home to work after Nov. 2024)
2. Include the Network Identification domain name into the Domain Suffix Search Order.
Once all of the DNS server entries and domains have been added, click on the Routing tab from the Change Network Settings: 
image-20240917122800-2
Notes:
1. A Net type route that matches the private network may automatically show up in the routing information. The default gateway should be the open networks default gateway.
2. The gateway device should be eth0. 
3. If no open network is being used, the default gateway need not be filled in.
Click OK, OK to save the changes.

The HMC may prompt to generate a new self-signed certificate that includes the new network information. Click yes to generated the new certificate. The HMC will restart.
 

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"7063CR2","label":"Hardware Management Console (7063-CR2)"},"ARM Category":[{"code":"a8m0z000000GnS5AAK","label":"HMC"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}]}]

Document Information

Modified date:
12 February 2025

UID

ibm17114249

Page Feedback