Troubleshooting
Problem
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.
Resolving The Problem
The following document provides steps to configure the Hardware Management Console (HMC) for use with the recommended private/open network. This process assumes that the HMC being used has two or more Ethernet adapters installed. The recommended configuration is to configure eth0 as a private network for management of the server(s) and configure eth1 for remote HMC access, call home, and dual HMC and/or HMC/partition communications. This document applies to HMC Version 7 and later.
Select HMC Management => Change Network Settings.
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:
Eth0 should be used for the private LAN. Eth1 should be used for the public LAN. Selecting Ethernet eth0 and clicking on Details provides the following options.
Notes:
| 1. | Selecting Private makes this the 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. | Do not check partition communication. |
| 6. | 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. |
Repeat for eth1. Below is the details panel for eth1:
Notes:
| 1. | eth1 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 may 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. 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. |
Click on Firewall to view and/or customize firewall settings for the selected interface.
Notes:
1. In the Firewall tab, select additional services from the top list box. Typically only Secure Shell needs to be added.
2. Click the Allow Incoming button to allow access from any IP address.
Once the firewall options have been set for eth1, check the Domain Name Services settings by clicking on the Name Services tab in the Change Network Settings:
Notes:
| 1. | DNS must be enabled. An address for the DNS server (in the above example, 9.10...) must be added to the DNS search order. If no DNS server entry exists, type the TCP/IP address of the HMC as a DNS to ensure that it has an entry. |
| 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:
Notes:
| 1. | A Net type route that matches the private network should automatically show up in the routing information. The default gateway should be the open networks default gateway. |
| 2. | The gateway device should be eth1. |
| 3. | If no open network is being used, the default gateway need not be filled in. |
| 4. | Do not enable 'routed'. |
Depending on what release of HMC, code changes made in any of the above-described processes (DNS, Firewall settings, and so on) will not take effect until the HMC is restarted.
Historical Number
575739979
Was this topic helpful?
Document Information
Modified date:
22 September 2021
UID
nas8N1011960