Setting up AIX or Linux to use an HMC to connect to service and support

Learn how to create a service connection to send service information from AIX® or Linux logical partitions and servers using an HMC.

Perform or verify Tasks 1 through 16 to set up connectivity for an AIX or Linux logical partitions or servers using an HMC.

Task 1. Before you begin

This procedure contains the complete list of tasks needed to set up connectivity to service and support. Some of these tasks might already have been completed (during initial server setup, for example). If so, you can use this procedure to verify that the tasks were completed correctly.

In this document, an Internet connection is defined as access to the Internet from a logical partition, server, or HMC by direct or indirect access. Indirect means that you are behind a Network Address Translation (NAT) firewall. Direct means that you have a globally routable address without an intervening firewall, which would block the ports that are needed for communication to service and support.

Task 2. Decide on your connectivity method

Choose the method that best describes your situation.

If you have an HMC and have multiple logical partitions:

For the HMC, use one of the following methods:
- Direct Internet including VPN or a Secure Sockets Layer (SSL) connection
- Shared direct Internet
- Shared dial-up connection
Note: If you have multiple HMCs on the same subnet, or HMCs that manage common systems, only one HMC needs to connect to service and support. This allows connectivity to be concentrated through one HMC which simplifies firewall rules.
For AIX or Linux logical partitions, hardware errors will be reported through the HMC, using the connection method provided for the HMC.

Task 3. Prerequisites

For direct Internet connections, contact the network administrator to verify the following:
- For HMC environments, if you plan on using VPN for transport, ensure that the following ports are open for communication:
  - Protocol UDP ports 500 and 4500 with the following IP addresses: Boulder: 207.25.252.196 and Rochester: 129.42.160.16
  - ESP (protocol 50) with the following IP addresses: Boulder: 207.25.252.196 and Rochester: 129.42.160.16
- For HMC environments, if you plan on using Secure Sockets Layer for transport and a firewall is in place between the HMC and the Internet, it must allow outgoing TCP/IP connections on port 443 from the HMC to each of the following IP addresses:
  - 129.42.160.48 and 207.25.252.200 (all regions)
  - 129.42.160.49 and 207.25.252.204 (North or South America)
  - 129.42.160.50 and 207.25.252.205 (all other regions)
    Note: You need to specify only the IP addresses necessary to set up access that is appropriate for your region.
- If multiple logical partitions are sharing an Internet connection, you will need the IP addresses or host names created for TCP/IP and for virtual Ethernet.
For a dial-up (modem) connection, determine necessary configuration settings, including:
- Local area code
- Predial information, such as dialing 9 to dial outside the network
- Use of commas if delayed dialing is needed
- Any special telephone line conditions such as pulse (rotary) dialing or no dialtone.
Ensure that TCP/IP is set up and configured correctly. If not, contact the network administrator and consult your operating system documentation.

Task 4. Ensure that your physical networking is set up correctly

The underlying framework of your service environment is networking. The following networking connections are required for you to be able to take advantage of electronic services such as reporting hardware problems and other server information and downloading updates:

Between the service processor and the HMC
Between the HMC and the server (AIX and Linux)
Between your site and service and support

Verify the physical connection between the service processor and the HMC.
The service processor is part of your platform hardware and monitors hardware attributes and conditions on your server. The service processor is controlled by server firmware and does not require an operating system to perform its tasks. The connection to the service processor is recommended for all servers, whether or not you have logical partitions. This connection is represented in the following illustration:

Figure 1. This diagram shows the Ethernet connection between your HMC and the service processor on your server.
Verify the physical connection between the HMC and the server (AIX and Linux).
This connection allows your server to communicate with your HMC.
How you set up this connection depends on your configuration:
- If your server is in its manufacturing default configuration, you will make this connection when you set up your server.
- If your server has multiple logical partitions, you must ensure that your HMC can communicate with each logical partition and that the logical partitions can communicate with each other. You will set up these connections as you create your logical partitions.
You can use either of the following methods:
Note: Both of the following networking methods require basic TCP/IP configuration on your logical partitions. For instructions on how to configure TCP/IP, see your operating system documentation.
- Have an Ethernet adapter for one logical partition, most likely your service partition, and then use virtual Ethernet to enable the logical partitions to communicate with each other and with the HMC. This option is the preferred option because it requires that you have only one physical adapter in the system. The following illustration shows this configuration:
  Figure 2. This diagram shows the Virtual Ethernet connection between your logical partitions and the physical Ethernet connection between your service partition and the HMC.
- Have a LAN adapter for each logical partition then have a physical connection between each logical partition and the HMC. This option requires that you have a router and a physical LAN adapter for each logical partition. The following illustration shows this configuration:
  Figure 3. This diagram shows physical Ethernet connections between your logical partitions and your HMC through a router.
Verify the physical connection from your site to service and support.
This connection enables you to report hardware problems and other server information to service and support. It also enables you to install updates. This connection is represented in the following illustration:
Figure 4. This diagram shows the connection between service and support and a company that has a server and an HMC.

Task 5. Obtain or verify an IBM ID

You will need an IBM® ID to register IBM Electronic Service Agent™ on the HMC and for Electronic Service Agent on your operating system or systems. You also will need this ID to view information that has been reported to IBM through Electronic Service Agent.

Go to the My IBM Profile Web site.
Verify that you are registered.
- If you are registered, Welcome back will be displayed on the Web site. Or, you can select Sign in and see if your e-mail address is recognized.
- If you are not registered, select Register and fill out the registration form. Create an IBM ID for each of the people you want to have access to the information that Electronic Service Agent reports to IBM. You must associate these accounts with a server, usually your central server. (You can add other servers later.) The people for whom you create IDs must have system administrator authority on all registered servers.
Record your IBM ID (the e-mail address that you registered).
You will need the ID during Task 6. Verify the HMC service settings.

Task 6. Verify the HMC service settings

To verify that the HMC service settings are set up correctly, use the Guided Setup wizard.

Note: If you have not set up your server, do that now. For details, refer to Initial server setup.

Access the Guided Setup wizard using the HMC interface:
1. In the navigation area, select the HMC that you want to work with.
2. Click Information Center and Setup Wizard.
3. In the contents pane, click Launch the Guided Setup Wizard. The Guided Setup wizard steps you through the tasks that are required to set up your HMC, including the tasks that are required to set up your service environment.
Click Next to skip the tasks that are not specific to setting up service, including:
- Setting the date and time
- Changing passwords for the hscroot and root user IDs
- Creating user IDs and passwords for new users and setting their authorities
- Specifying network settings
Ensure that the following service tasks are completed correctly:
1. Customer contact information for service-related activities, including:
  - Company name
  - Administrator name
  - E-mail address
  - Telephone numbers
  - Information regarding the location of the HMC
2. Configuration of connectivity for service-related activities.
  - Internet VPN
    Note: When configuring the HMC's network settings for connecting using direct or indirect Internet, the HMC must be configured with a default gateway to access the Internet. Select HMC Management > Change Network Settings. Ensure that the Default Gateway Information field has a Gateway address listed and a selection is made in the Gateway device field (for example, any).
  - Internet: Currently, the SSL option must be configured manually:
    1. Select Service Management > Manage Outbound Connectivity
    2. ClickConfigure....
    3. Select the Internet tab.
  - Dial-up connection from the local HMC
  - Connecting through other systems or logical partitions
3. Configuration of the network settings.
  - For direct or indirect Internet:
    - HMC host name
    - Domain name
    - Description of HMC
  - For a dial-up modem connection:
    - Dial prefix, if applicable
    - Modem configuration, including:
      - Dial type
      - Dial prefix, if applicable
    - Telephone number
4. Authorize two users for Electronic Service Agent by entering the ID (the e-mail address that you registered with the My Profile Web site at https://www.ibm.com/account/profile.
  Note: You will be able to authorize more users later.
5. Add e-mail addresses for those you want to be notified when problem events occur.
To test the connection from the HMC, open Service Management > Manage Outbound Connectivity.
Select the tab for the type of outbound connectivity that you chose for your HMC (Local Modem, Internet, Internet VPN, or Pass-Through Systems). For more information about these settings, see Choosing your connection method.
Click Test.
Choose from the following options:
- If the test is successful, continue with the next Task.
- If the test fails, continue with the next step.
Ensure that your country or region is listed. Select Service Management > Manage Customer Information. Ensure that your country or region is selected from the list.
Choose from the following options:
- If you have a dial-up connection, perform the following:
  - Check the telephone line going into the HMC and the wall socket.
  - Check to make sure that you have the telephone number configured correctly, including predial information, such as dialing 9 to dial outside the network.
- If you have an Internet VPN connection, perform the following:
  - Ensure that the appropriate firewall rules have been added, if necessary.
  - Check that you have a default gateway set up on the HMC. Select HMC Management > Change Network Settings. Ensure that the Default Gateway Information field has a Gateway address listed and a selection is made in the Gateway device field (for example, any).

Task 7. Set up and configure your logical partitions

For details, refer to Partitioning the server.

Task 8. Install the operating systems on your server or logical partitions

For details, refer to Installing operating systems.

Task 9. Configure your TCP/IP network

For instructions, refer to the operating system documentation.

Task 10. Activate TCP/IP on your server or logical partitions

TCP/IP starts automatically, as long as the network adapter is recognized and can communicate with the network when the AIX or Linux operating system is started.

Task 11. Obtain and configure Electronic Service Agent for AIX or Linux

If you have an HMC, you do not need to obtain and configure Electronic Service Agent for AIX or Linux. The AIX and Linux inventory and hardware-problem information (or report, perhaps) are sent through the HMC. However, you might want to set up Electronic Service Agent on AIX or Linux to contact the software service organization.

Choose from the following options:
- If you have an HMC and do not want to obtain and configure Electronic Service Agent, continue with Task 14. Configure the service processor.
- If you want to obtain and configure Electronic Service Agent for AIX or Linux, continue with the next step.
Obtain Electronic Service Agent.
1. Go to the Electronic Service Agent Web site.
2. Follow the on-screen prompts to locate the instructions to obtain Electronic Service Agent.
Choose from the following options:
- To configure Electronic Service Agent AIX, continue with the next step.
- To configure Electronic Service Agent for Linux, go to step 9.
To configure Electronic Service Agent for AIX, review the following information:
In this example, you will configure the following:
- Electronic Service Agent on the server that has a modem for dial-up connection to service and support
  Note: Alternatively, you can use an Internet or Secure Sockets Layer (SSL) connection instead of the modem to connect to service and support.
- Electronic Service Agent on the other clients to communicate with the server that has the modem
Figure 5. This diagram shows three servers and their connection through a modem to service and support.
Note: For complex network environments involving HTTP proxies, SOCKS proxies, or DMZs, refer to the Electronic Service Agent for IBM pSeries® and IBM RS/6000® User's Guide.
From the System Management Interface Tool (SMIT), configure and start Service Agent Connection Manager (SACM). The SACM is responsible for establishing connectivity to service and support. It enables the gateway server and clients to use a single, secure connection.
Note: For more details on SMIT, see the System Management Interface Tool SMIT Redbook.
1. Verify that the host name for the SACM is correct. In this example, the SACM is located on the server or logical partition with the modem. Therefore, the SACM is configured to the host name of the server or logical partition with the modem.
2. Verify the default port 1198. In most cases, the default port is appropriate. You can change the port later, if necessary. This port is necessary for communication between the gateway server and the SACM.
Configure and start the Electronic Service Agent gateway server. This is the server or logical partition that acts as the central management server for all of the clients (monitored servers or logical partitions). The Service Agent gateway server contains the central database, and it initiates communication to service and support. The Service Agent gateway communicates to service and support through the SACM.
1. Verify that the host name is correct. In this example, the SACM and SA gateway server are located on the same server. It is the server or logical partition with the modem. The SA gateway server is the server or logical partition with the modem. Therefore, the SA gateway is configured to the host name of the server or logical partition with the modem.
2. Verify that the machine type, model, and serial number are correct.
Configure and start the Electronic Service Agent client. This is the monitored server or logical partition for which system information is collected and reported to service and support.
1. Verify that the host names for the SA clients and for the SA gateway are correct.
2. Verify that the machine type, model, and serial number are correct.
Continue with Task 12. Use the Service Agent (SA) Basic User Interface.
To configure Electronic Service Agent for Linux, review the following information.
In this example, you will configure the following:
- Electronic Service Agent on the server that has a modem for dial-up connection to service and support
  Note: Alternatively, you can use an Internet or Secure Sockets Layer (SSL) connection instead of the modem to connect to service and support.
- Electronic Service Agent on the other clients to communicate with the server that has the modem
Figure 6. This diagram shows three servers and their connection through a modem to service and support.
From the Linux command line, type the following command to configure and start Service Agent Connection Manager (SACM):
```
startsrc -s sacm
```
The SACM application enables the gateway server and client servers to use a single, secure connection to reach service and support.
From the Linux command line, type the following command to configure and start the Electronic Service Agent gateway server:
```
/usr/svcagent/bin/sagatewayconfig
```
The Service Agent gateway server acts as the central management server for all of the clients (monitored servers or logical partitions). It contains the central database and initiates communication to service and support.
Continue with Task 12. Use the Service Agent (SA) Basic User Interface.

Task 12. Use the Service Agent (SA) Basic User Interface

You will need to install Electronic Service Agent on AIX or Linux to access the SA Basic User Interface. For details, refer to the Electronic Service Agent Web site and search for the appropriate Electronic Service Agent user's guide.

Get familiar with the SA Basic User Interface. The SA Basic User Interface provides a list of properties and the associated fields that you need to complete to configure Electronic Service Agent.
Specify information for the required property fields. Click each property on the left side of the interface, and complete the required fields on the right side of the interface. Required fields are indicated with an exclamation point.
Depending on how you complete the fields, the interface guides you through the appropriate properties. For example, if you specify that you want to use a modem in the Connection Manager property fields, the interface automatically displays the dialer property fields, so that you can complete the information about your modem.

For this example, where you have multiple servers or logical partitions running AIX or Linux and you use a modem for outbound connectivity, you need to complete specific information for the following properties:
ConnectionManager

Clear False for Connect to SDR using Dialer to enable the dialer. This indicates that you want to use a modem to connect to service and support.

Dialer

Specify details about your modem and service and support connection parameters.

Machines

Add two SA client servers.

Enroll

Register the servers with service and support. This initiates a call to service and support to enroll the servers in service and support's database. To complete the process, service and support sends you a key.

Call log

Check the status of the call to service and support. You can see whether the call to service and support is successful.

To learn about advanced features that go beyond the scope of this example, go to the Electronic Service Agent Web site and search for the appropriate Electronic Service Agent user's guide.

Task 13. Register the ID with Electronic Service Agent for AIX or Linux

From the Service Agent Basic User Interface, click Enroll.
Complete the required fields on the right side of the interface. Required fields are indicated with an exclamation point.
Continue with Task 14. Configure the service processor.

Task 14. Configure the service processor

You might use this type of service connection if your server is not available, because the service processor does not require an operating system to perform its tasks.

To set up your service processor to connect to service and support, you need to attach a modem to the system port on your server. In addition, you need to use the Advanced System Management Interface (ASMI) menus to perform several configuration steps.

On the ASMI Welcome pane, specify your user ID and password, and click Log In.
Note: To perform these tasks, you must have an authority level of either Administrator or Service provider.
In the navigation area, expand System Service Aids.
To configure the service processor system port, follow these steps:
1. Select Serial Port Setup.
2. Modify the appropriate fields in the S1 (used with the call-home feature) and S2 (used with the call-in feature) sections.
3. Click Save settings to save the setting changes.
To configure the modem, follow these steps:
1. Select Modem Configuration.
2. Modify the appropriate fields in the S1 and S2 sections.
3. Click Save settings.
To configure the call-home and call-in policy, follow these steps:
1. Select Call-in/Call-home.
2. Enter the desired text into the specified fields.
3. Click Save settings to save changes.
To test the call-home policy, follow these steps:
1. Select Call-Home Test.
2. Click Initiate call-home test. A test of the call-home system is performed as specified by the current port and modem selections.
Continue with Task 15. Test the connection to service and support.

Task 15. Test the connection to service and support

If you use an HMC to connect to service and support, follow these steps to test the connection for the HMC:
1. On the HMC, open Service Management > Create Serviceable Event.
2. Select Test problem reporting.
3. Select Request Service. A message is displayed when the service request is sent.
To test the connection for AIX (if you set up Electronic Service Agent on the server or logical partition), follow these steps:
1. From the System Management Interface Tool (SMIT) on your Electronic Service Agent server, activate the Electronic Service Agent.
2. Ensure that the Electronic Service Agent Connection Manager is active if it is located on a machine other than the Electronic Service Agent server.
3. From SMIT, start the Service Agent Advanced User Interface.
4. To use a modem, follow the instructions to configure the dialer on the Connection Manager screen. The default is to connect to service and support using an existing Internet connection.
5. Open the Manual Tools folder.
6. Select Connect.
7. Monitor the CallLog for the following entry: TEST Connection (Success: 1, Fail: 0).
To test the connection for Linux (if you set up Electronic Service Agent on the server or logical partition), follow these steps:
1. On your Electronic Service Agent server, activate the Electronic Service Agent.
2. At a Linux command line, type the following:
```
startsrc -g svcagent
```
3. Ensure that the Electronic Service Agent Connection Manager is active if it is located on a machine other than the Electronic Service Agent server.
4. At a Linux command line, type the following:
```
startsrc -s sacm
```
5. Start the Service Agent Advanced User Interface.
6. At a Linux command line, type the following:
```
/usr/svcagent/bin/sauiascii
```
7. If you want to use a modem, follow the instructions to configure the dialer on the Connection Manager screen. The default is to connect to service and support using an existing Internet connection.
8. Open the Manual Tools folder.
9. Click Connection.
10. Monitor the CallLog for the following entry: TEST Connection (Success: 1, Fail: 0).

Task 16. View the server information that was reported

You can use the Internet to view details of the system you have enabled, and see the data collected by Electronic Service Agent. To use the advanced features and receive the full benefits of Electronic Service Agent, you must enter an IBM Registration ID (IBM ID). The first IBM ID entered will have Administrator authority and is able to authorize additional users on the Web site. The second IBM ID is available as a backup for the Administrator.

Go to the Electronic Service Agent Web site.
Click Sign in (in the upper-right corner).
Type the IBM ID and password.
Choose the following options from the navigation bar:
- To view your server information, click My systems.
- To search technical support using your server information to improve the search results, click Premium Search.
  Note: In some cases, the Premium Search feature is available only while your server is under warranty or afterward through a service contract.
- To view information related to your servers and interests, click My messages.
Enter the requested information.

Send feedback | Rate this page

Last updated: Wed, March 28, 2012