Troubleshooting
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. This document applies to HMC Version 6 and earlier.
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 and configure eth1 for remote HMC access, call home, and dual HMC and/or HMC/partition communications. This document applies to HMC Version 6 and earlier.
Review the network settings for the HMC by clicking on the following in the Navigation Area (left window): HMC Management => HMC Configuration. Then click on Customize Network Settings from the options listed in the right frame of the Web-Based System Manager (WebSM).
Notes:
| 1. | The console name must not be localhost. |
| 2. | The domain name must be filled in with xxxxxx.com .org where xxxxxx is the name of the public network. If there is no public network, you should make up a name. This must be filled in. |
| 3. | Make a note of the domain name because it is required later on the Name Services tab. |
Eth0 should be used for the private LAN, eth1 should be used for the public LAN. Select Ethernet eth0 and clicking on Details provides the following options.
Notes:
| 1. | Select Private. |
| 2. | Enable DHCP to make the HMC a source for TCP/IP addresses on the Private network. |
| 3. | Specify 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.0.1 is one below the 192.168.0.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. |
| 4. | Do not check partition communication. |
| 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. |
Repeat for eth1. Below is the details panel for eth1:
Notes:
| 1. | Specify open network for 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. It does conform to name services standards and, therefore, attempts to register its name to the DNS specified upon receiving an address. Specify the correct subnet for the static TCP/IP address. |
| 4. | Verify that there is not a subnet range violation between the DHCP range of the private network and the static TCP/IP range or dynamic TCP/IP range, if specified, of the open network. Otherwise, specific addresses are not available. |
| 5. | For media speed, autodetection should be selected except for the case when the network switch the 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, services in the bottom list box are those currently selected to be available from the HMC. Select additional services from the top list box and click on the add button to add desired services. Select WebSM if remote access to WebSM is from the private network, Secure Shell (SSH), Web access, and Secure web access. |
| 2. | Open ports using the Allow Incoming button rather than by TCP/IP address. |
Once the firewall options have been set for eth01, check the Domain Name Services settings by clicking on the Name Services tab in Customize Network Settings.
Notes:
| 1. | DNS should be enabled. An address for the DNS server (in the above example, 9.10...) must be added to the DNS search order. |
| 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 Customize 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. |
Changes to the lan adapter settings, DNS, and default gateway do not take effect until the HMC is restarted. Firewall changes do not require a restart.
Historical Number
349221119
Was this topic helpful?
Document Information
Modified date:
22 September 2021
UID
nas8N1015949