Install Electronic Service Agent version 3.3

Linux on Power Systems™ uses Electronic Service Agent™ version 3.3.

You must complete all relevant steps in Setting up AIX or Linux to connect to service and support before completing this procedure.

Perform or verify steps 1 through 5 to set up Electronic Service Agent version 3.3.

Step 1. Obtain and configure Electronic Service Agent version 3.3

If you are using the Linux operating system, you need to obtain and configure Electronic Service Agent version 3.3.

Obtain Electronic Service Agent.
Install the selected code and any prerequisites that you obtained in the previous step.
To configure Electronic Service Agent for Linux, review the following information.
In this example, you configure 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 connection instead of the modem to connect to service and support.

Figure 1. Two Service Agent clients attached to one Service Agent gateway that is attached to a modem
From the Linux command prompt, type the following command to configure and start the 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 prompt, type the following command to configure and start the gateway server:
```
/usr/svcagent/bin/sagatewayconfig
```
The Service Agent gateway server acts as the central management server for all the clients (monitored servers or logical partitions). It contains the central database and starts communication to service and support.

Step 2. Use the Service Agent basic user interface

The 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 to complete 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.

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

CallController: Verify that URL2CM is the default https://localhost:1198. Or ensure that the address is correct for the unsecured SACM, including the host name and port.

ConnectionManager: Ensure that True is selected for Use Modem as a Connection Method to IBM to enable the dialer. This value indicates that you want to use a modem to connect to service and support.

Dialer: Specify details about the modem and the service and support connection parameters.

Machines: Add two service agent client servers.

Enroll: Register the servers with service and support. This action starts a call to service and support to enroll the servers in the service and support database. To complete the process, service and support sends the gateway database a key for each enrolled host. Your common IBM® ID also is associated with the newly enrolled host.

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 guide.

Step 3. Register the ID with Electronic Service Agent

You must have an IBM ID so that you can view information that has been reported to IBM through the Electronic Service Agent application.

From the basic user interface, click Enroll.
Complete the required fields on the right side of the interface. Required fields are indicated with an exclamation point.

Step 4. Test the connection to service and support

You can test the connection to service and support from the Electronic Service Agent application

To test the connection for Linux (if you set up Electronic Service Agent on the server or logical partition), follow these steps:

Ensure that the Electronic Service Agent Connection Manager is active if it is located on a machine other than the Electronic Service Agent server.
Start the Advanced User Interface.
At a Linux command prompt, type one of these commands depending on whether you want the user interface or ASCII:
```
/usr/svcagent/bin/saui
```
or
```
/usr/svcagent/bin/sauiascii
```
Open the Manual Tools folder.
Click Connection.
Monitor the call log for the following entry: TEST Connection (Success: 1, Fail: 0).

Step 5. View the server information that was reported

You can use the Internet to view details of the system that you have enabled, and see the data collected by the Electronic Service Agent. To use the advanced features and to receive the full benefits of Electronic Service Agent, you must enter an IBM registration ID (IBM ID). The first IBM ID entered has 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 IBM 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 is available 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