Scenario: Linux without an HMC

If you are running the Linux^® operating system, learn about the most common service scenario for Linux.

Situation

If you are responsible for maintaining servers at your company, one of your roles might be to establish the connections within your network and to the service and support organization so that your servers can access service and support resources.

Objectives

In this scenario, you want to ensure that your company's server can receive support from the service organization when requested by your company's network administrator. The objectives of this scenario are as follows:

To configure Electronic Service Agent™ on the server that has a modem connection to service and support
Note: Alternatively, you can use an Internet connection instead of the modem to connect to service and support.
To configure Electronic Service Agent on the other client servers to communicate with the server that has the modem

Note: If you are using the Integrated Virtualization Manager to manage your server, check Service Focal Point for the Integrated Virtualization Manager to see if you need to contact service and support.

Details

The following figure illustrates the flow of service information and problems through the service connection to service and support.

Figure 1. A figure of three Linux servers and their connection through a modem to service and support.

A figure of three Linux servers and their connection through a modem to service and support.

The figure illustrates the following points relevant to this scenario.

The Electronic Service Agent gateway server and Connection Manager are set up on the server with a modem that connects to service and support.
The Electronic Service Agent clients are set up on the other servers.
Service information and problems flow from each client and gateway server to service and support using the modem on the server, as follows:
- Linux servers (Electronic Service Agent clients) > Linux server (Electronic Service Agent gateway server) > Service and support

Prerequisites and assumptions

Successful implementation of this scenario requires that all necessary hardware planning and setup tasks are complete.

Configuration steps

You must complete the following tasks:

Ensure that all prerequisites are met for your connection method. Refer to Task 3. Prerequisites.
Ensure that your physical networking is set up correctly. Refer to Task 4. Ensure that your physical networking is set up correctly.
Obtain or verify your IBM^® ID. See Task 5. Obtain or verify an ID.
Install the operating system on your servers. For details, see the Installing operating systems topic.
Configure your TCP/IP network. For instructions, refer to the operating system documentation.
Activate TCP/IP on your server. TCP/IP starts automatically, as long as the network adapter is recognized and can communicate with the network when the AIX^® operating system is started.
Obtain Electronic Service Agent™, and configure it on the gateway server and the client servers by performing these tasks:
1. Obtain and configure Electronic Service Agent for AIX. See Task 9. Obtain and configure Electronic Service Agent for AIX or Linux.
2. Use the Service Agent (SA) Basic User Interface. See Task 10. Use the Service Agent (SA) Basic User Interface.
3. Register the IBM ID with Electronic Service Agent for AIX. See Task 11. Register the ID with Electronic Service Agent for AIX or Linux.
Configure the service processor for connectivity. See Task 12. Configure the service processor.
Verify that the connection to service and support is set up correctly and that information is being transmitted correctly. See Task 13. Test the connection to service and support.
View information that was shared. See Task 14. View the server information that was reported.