2    Configuring the AlphaServer Management Station

Follow the procedures outlined in this chapter to configure the AlphaServer Management Station (AMS) and the platforms you will manage.

2.1    Starting the Console Management Facility Daemon and the Tomcat Web Server

The Console Management Facility (CMF) daemon, cmfd, allows you to connect to consoles configured on the platforms. It monitors and logs the output of any console connections.

The Tomcat Web server allows you to run the Server Platform Manager (SPM) in a Web browser.

1. Start cmfd:

   For Tru64 UNIX:

   # /sbin/init.d/cmfd start
   

   For Linux:

   # /etc/init.d/cmfd start
   

   The cmfd starts automatically during subsequent reboots of the AMS.

2. Start the Tomcat Web server:

   For Tru64 UNIX:

   # /sbin/init.d/amstomcat start
   

   For Linux:

   # /etc/init.d/amstomcat start
   

   The Tomcat Web server starts automatically during subsequent reboots of the AMS.

2.2    Adding Users to the amsuser Group

The amsuser group is created on the AMS machine when you install the AMS software. Members of the amsuser group, along with root, are allowed to run the PCM. You can add users to the amsuser group to give users access to the PCM.

To add users to the amsuser group, edit the /etc/group file located on the AMS machine.

2.3    Securing Access to the Platforms

You can secure access to a platform managed by the AMS by:

• Using the AMS machine as a bridge between the platform's management LAN and your corporate network

• Configuring remote access to consoles

See Section 1.2.1 for more information.

2.3.1    Using the AMS as a Bridge

You can secure access to the platforms by installing two network interface cards (NIC) in the AMS machine. This allows the AMS machine to connect to the platform's built-in local area network (LAN) through a Network Address Translator (NAT) box or similar device, and to the corporate network. This configuration restricts access to the platforms because you must have an account on the AMS machine to use its components.

We recommend that you secure access to the platforms in this way because:

• There is no login process to the MBM; therefore, it is not secure.

• Securing access to the platforms also controls conflicting access to the MBM console and subpartition console ports. Only one connection can be made to a console port at a time. The CMF daemon cmfd, a component of the AMS, manages and logs console connections. See cmfd(8) for more information.

2.3.2    Configuring Access to Consoles

To access system consoles and the management port of a platform remotely, you must use the AMS. By default, you cannot Telnet directly to the consoles or management port when not using a component of the AMS.

You can access the AMS machine remotely by using Telnet to connect to the AMS or accessing the Server Platform Manager (SPM) in a Web browser.

To allow Telnet connections to consoles and the management port by turning AMS security off:

1. Log into the AMS as root.

2. Enter the following command:

   # /usr/opt/amsmgr -security false
   

2.4    Configuring the Platforms to Be Managed

Before managing platforms with the AMS, you must configure them in either the Server Platform Manager (SPM) or the Platform Console Manager (PCM).

Use the SPM if you want to manage the platforms locally on the AMS machine machine or remotely using a Web browser. The SPM is a client-server application. The server runs on the AMS machine and the client is a Web-based graphical user interface. You can also run the SPM as a Java application. See Section 2.4.1 for more information.

Use the PCM if you want to manage the platforms remotely over a low-bandtwidth connection.. The PCM is a character cell application, which makes it ideal for use on a low bandwidth connection to the AMS machine. See Section 2.4.2 for more information.

2.4.1    Using the SPM to Configure the Platforms to be Managed

Use the Server Platform Manager (SPM) to configure platforms that you will manage.

A major component of the AMS is the Server Platform Manager (SPM) application, through which you can manage and monitor platforms, connect to the platform's management port, establish connections to the consoles of systems running on the platform, and view platform and system console logs. To perform these actions, you first must configure the platform and the platform's default subpartition.

Using your preferred Web browser, specify the host name of the AMS machince in the following URL to connect remotely to the SPM:

http://AMS_hostname:8080/spm

You can also run the SPM as a Java application locally on the AMS machine by entering the following command:

# /usr/opt/ams/bin/spm

To configure platforms to be managed by the SPM:

1. From the main window of the SPM, select Login from the File menu and log in as root, using the same root password as that of the AMS.

2. Select the icon of a platform that is connected to the SPM.

3. Select Add Platform... from the Actions menu.

4. Enter the name, model, NAT box IP address, description, and layout template (the layout template will be used by the Platform Manager to display a graphical representation of the platform).

5. Select OK to add the platform to the SPM.

6. Wait approximately 30 seconds while the SPM discovers the platform.

To configure the platform's default subpartition:

1. Select the icon of the default subpartition in the SPM left frame.

2. Press the right mouse button. A pop-up Actions menu displays.

3. Select Configure....

4. Enter the subpartition's hostname, the type of operating system that will run on the subpartition, and an optional description.

5. Select OK.

You can now connect to the platform's management port. See Chapter 3 for more information about the SPM.

2.4.2    Using the Platform Console Manager to Configure Platforms to Be Managed

You can use the Platform Console Manager (PCM) to configure systems that you will manage with the AMS. Because the PCM runs in character cell mode, it is ideal for remote use over low bandwidth connections.

A system is a subdivision, partition, or subpartition of a platform and runs an operating system.

Note

You can run the PCM only on the AMS. To run the PCM remotely, you must Telnet to the AMS machine. See Chapter 6 for more information.

To start the PCM:

1. Unset your display:

   # unset DISPLAY
   

2. Start the PCM:

   # /usr/bin/pcm
   

To add a system, or default subpartition, to be managed by the PCM:

1. Select Configure... from the PCM main window.

2. Select Add a system to be managed.

3. Select OK. The Add a system to be managed dialog box displays.

4. Enter the name of the system (partition running an operating system) to be managed.

   We recommend that you give the system the same name as that of the operating system running on it.

5. Enter the name of the platform on which the system is configured.

6. Enter the model of the platform.

7. Select the console connection type.

   Select NAT since system consoles on ES47/ES80/GS1280 platforms are accessed through a NAT box.

8. Enter the IP address of the NAT box to which the system's console is connected.

9. Enter the port number of the NAT box to which the system's console is connected.

10. Enter the management port number of the NAT box. The default is port 23.

11. Choose whether or not to log console output.

12. If you chose to log console output, then you can choose to monitor console output. Choosing to monitor console output enables the PCM to display real time output received from the consoles of all configured systems. It also enables you to generate events from console error messages. See Chapter 6 for more information.

13. Enter a description (for example, production system).

14. Select OK.