2    Using the Server Platform Manager

This chapter describes the different tasks you can accomplish using the Server Platform Manager (SPM). Section 2.1 provides a brief overview of the program, after which, the following topics are discussed:

2.1    Overview

The Server Platform Manager is a graphical client-server application. The server runs on the AMS machine and the client is a Web-based graphical user interface that provides local and remote management of platforms and consoles.

Each console represents a name for a port on a platform or a subpartition that can be connected via the cmfd. Consoles are logged and monitored for events on all platform management ports and all partition ports.

Each platform has one console, the console associated with the platform management port or the terminal-server port, which is always port 23.

A partition that can run an operating system can have a console. On ES47, ES80, and GS1280 platforms, the port number associated with a console is always assigned by the firmware; on GS80, GS160, and GS320 platforms, the port is assigned through the terminal-server configuration.

You can monitor the status of platforms and systems using the SPM's left frame and monitor bar. Use the left frame to monitor the hardware status of each platform and the operation status of each partition using the SPM's color-coded status icons.

Use the monitor bar, located under the menu bar, to see the status of any platforms that are running in a warning, critical, or unknown state; the number of platforms with that status; and the user name of the person currently logged in. You can also view and manage the platforms' partitions and the consoles associated with those partitions.

To manage a platform or system, you can launch a Telnet session to a platform's management port or a system's console. You can also access platform and system management applications.

The SPM's online help provides step-by-step information about tasks you can perform with the SPM. To view the SPM online help, select Help in the menu bar and then select Contents.

2.2    Logging On and Working with Users

The following sections describe how access and log onto the SPM, add users, and assign privileges to users.

2.2.1    Using the SPM Locally

You can run the SPM locally on an AMS machine either in a Web browser or as a Java application. We recommend running SPM locally on the AMS as a Java application.

To run the SPM locally on an AMS machine using a Web browser:

  1. Set the environment variable for the Java 2 plug-in in the ksh environment:

    On Tru64 UNIX: 

    # NPX_PLUGIN_PATH=/usr/opt/java131/jre/plugin/alpha/ns4
# export NPX_PLUGIN_PATH

    On Linux: 

    # ln -s /usr/java/jre1.3.08/plugin/i386/libjavaplugin_obj.so /usr/lib/mozilla/plugins
 
 

  2. Point your browser to the following URL (where localhost is the host name of the AMS machine): 

    http://localhost:8080/spm

To run the SPM locally on an AMS machine as a Java application: 

# /usr/bin/spm

2.2.2    Accessing the SPM Remotely

To connect to the SPM, enter the following URL in a Web browser, specifying the host name of the AMS machine you want to connect to: 

http://AMS_hostname:8080/spm

2.2.3    Security Certificate

The first time you access Version 3.0 of the SPM program or the AMU as a standalone program, you must respond the Java Plug-in Security Certificate (Figure 2-1) that is displayed prior to loading the SPM program.

Figure 2-1:  Security Warning

The action you take with the security window determines whether you can access the program and whether you will see the certificate again:

Pressing the View Certificate button opens a new window with information about the certificate.

All applets included in the AMS application are digitally signed by HP with a VeriSign certificate. The signing gives applets permission to access resources and enable copy and paste operations on client machines.

2.2.4    Logging On

You must be root on the AMS machine to log into the SPM for the first time. The AMS root user automatically has SPM administrator privileges. Authorization roles can be assigned only to accounts in the amsuser group. Figure 2-2 shows the SPM login dialog box.

Figure 2-2:  Login Dialog Box

2.2.5    Assigning Privileges

The AMS root user has administrator privileges to all SPM functions by default. All other amsuser group accounts have limited guest access until the SPM administrator assigns them different privileges.

An administrator can assign or modify privileges to an amsuser group account from the Configuration menu by choosing Security -> Assign User Access... (Figure 2-3), selecting the role in the combo box, and selecting Modify.

The SPM access roles are stored in the SPM's server database until the administrator removes them.

Figure 2-3:  Assign User Access Dialog Box

Table 2-1 displays a list of SPM functions and the privileges allowed for each.

Table 2-1:  SPM Privileges

  Administrator Operator Guest
Expand and collapse tree yes yes yes
View discovered servers and their status yes yes yes
View event details (toolbar and tree) yes yes yes
Customize the display of the right frame yes yes yes
View help (all menus yes yes yes
Set refresh period yes yes  
Add platform yes    
Modify platform yes    
Remove platform yes    
Configure console yes yes  
Assign access roles yes    
Launch AMU, Event Viewer, Insight Management Agents yes yes  
Launch APW yes    
Telnet to console yes    
Telnet to MBM yes    
Turn on or off console output logging yes    
View console log files yes yes  
View properties (all tree notes) yes yes  
Show/disconnect users yes yes  
Add standalone console yes yes  
Map console ports yes yes  
Broadcast to connected users yes yes  
Enable console yes yes  
Show AMS sessions yes yes  

2.3    The Main SPM Window

The main SPM window displays the platforms and consoles connected to the SPM and lets you interact with them. Figure 2-4 shows the main SPM window, which is described in the following sections.

Figure 2-4:  Main SPM Window

2.3.1    The Monitor Bar

The monitor bar (Figure 2-5), gives you an easy way to see the status of any platforms that are running in a warning, critical, or unknown state; the number of platforms with that status; and the user name of the person currently logged in to the SPM using the monitor bar. You can separate the monitor bar from the main SPM window to save desktop space.

Figure 2-5:  The Monitor Bar

The monitor bar uses the following icons:

The number to the right of this icon indicates how many platforms are running without errors.

The number to the right of this icon indicates how many platforms have warning errors. These are not critical yet, but you may want to investigate them further.

The number to the right of this icon indicates how many platforms have critical errors calling for your immediate attention.

2.3.2    The Left Frame

The left frame (Figure 2-6) displays a tree structure in which you can view and interact with the platforms and consoles managed by the AMS.

Figure 2-6:  The Left Frame

The left frame uses the following icons:

The platform is running without errors.

The platform has one or more warning errors. These are not critical yet, but you may want to investigate them further. For example, this icon displays when the SPM times out during platform discovery.

The platform has critical errors calling for your immediate attention.

The hard partition is powered on.

The hard partition is powered off.

The operating system, SRM console, or XSROM is running on the subpartition.

Nothing is running on the subpartition.

The component is in an unknown state. The SPM could be in the process of discovering this component.

You can perform actions on the components in the left frame. Different actions are available for different components. Select a component and then select the Actions menu to display the list of actions you can perform on that component. You can also press the right mouse button on a component to display a pop-up Actions menu.

See Section 2.5, Section 2.6, Section 2.8, and the online help for information about each of the menu items.

2.3.3    The Top Right Frame

The top right frame displays information about disk utilization for the AMS server, icons of the platforms or consoles, the default hard partitions, detailed information about the default subpartitions, and the status of a selected subpartition. Selecting a component in the left frame displays the component, groups of components, or detailed information in the SPM top right frame.

You can display either the platforms connected to the AMS, the subpartitions configured on a platform, the consoles configured on a subpartition, or the console's status. For example, selecting Platforms in the left frame displays all of the platforms connected to the AMS in the top right frame.

When a branch of the tree in the left frame contains branches below it, you can view icons in the right frame or you can view details about that branch. You choose the view you want by using the View menu.

For example, Figure 2-7 displays the icon view for the AMS Platform Consoles; Figure 2-8 displays the details view.

Figure 2-7:  The Top Right Frame (Icon View)

Figure 2-8:  The Top Right Frame (Details View)

If the branch in the left frame contains no branches below it, the right frame displays details about that branch. In this case, clicking on the View menu items has no affect on the display. Figure 2-9 shows the right frame display of a specific AMS platform console.

Figure 2-9:  The Top Right Frame (Specific Console View)

When you display a platform and default hard partition in the top right frame, you can right-click on its icon to display its Actions menu.

You can customize the console status view by dragging the column headings in the order you want.

2.3.4    Hardware Warnings and Errors Frame

The bottom right frame displays detailed information about the warnings and errors found for all platforms. The following is a summary of the hardware errors that will be displayed if they occur:

ES47, ES80, and GS1280 Platforms

GS80, GS160, and GS320 Platforms

2.3.5    Customizing the Main SPM Window

You can move the shaded bars on the SPM to customize the layout. For example, you can click and drag the shaded bars between frames to make the frames larger or smaller. You can also move the monitor bar within the application window or drag it outside of the application window to create a separate monitor bar.

You can customize the right frame display to display detailed properties for each selected tree node.

You can sort the columns of the hardware errors table and all the tables when in the Details view, or move them to a different position.

Note

Window customizations are not persistent between different browser sessions.

See the SPM online help for more information.

2.4    Adding and Modifying a Platform

You can add a platform to the SPM by selecting Add Platform... from the Platforms context menu or from the Actions menu when you select Platforms. The process is the same for the ES47/ES80/GS1280 and GS80/GS160/GS320 platforms, with some differences in the information you provide to the Add Platform dialog box.

The same dialog boxes are displayed when you modify and existing platform. You modify a platform by selecting Modify... from the specified platform's context menu or from Actions menu when you highlight the specified platform.

2.4.1    Adding or Modifying an ES47, ES80, and GS1280

Figure 2-10 shows the Add Platform dialog box for ES47, ES80, and GS1280 platforms. A description of the fields follows.

Figure 2-10:  Add Platform Dialog Box (ES47, ES80, and GS1280)

To add a platform or modify an existing one, you need the following information:

The platform appears in the left frame after you add it to the SPM. The SPM automatically obtains the platform's configuration information. If a platform's configuration is not returned, the SPM cannot access the platform at the specified address.

You can also modify a platform that is managed by the SPM by selecting Modify... from the Actions menu.

After the subpartition icons are displayed, you should configure each subpartition. Configuring the subpartition allows you to connect to its OS/SRM console port. See Section 2.6.1 for more information.

2.4.2    Adding or Modifying a GS80, GS160, and GS320

Figure 2-11 shows the Add Platform dialog box for GS80, GS160, and GS320 platforms. A description of the fields follows.

Figure 2-11:  Add Platform Dialog Box (GS80, GS160, and GS320)

To add a platform or modify an existing one, you need the following information:

The platform appears in the left frame after you add it to the SPM. The SPM automatically obtains the platform's configuration information. If a platform's configuration is not returned, the SPM cannot access the platform at the specified address.

You can also modify a platform that is managed by the SPM by selecting Modify... from the Actions menu.

After the subpartition icons are displayed, you should configure each subpartition. Configuring the subpartition allows you to connect to its OS/SRM console port. See Section 2.6.1 for more information.

2.5    Managing Platforms

You can manage platforms with the SPM by:

Selecting a platform's context menu or clicking on the Actions menu when a specific platform is highlighted displays a menu with the following items:

2.5.1    Connecting to the Platform's Management Port

You can establish a connection to a platform's management LAN directly from the SPM by connecting to the platform's management port.

2.5.1.1    ES47, ES80, and GS1280 Platforms

The management LAN connects to the platform's management software, which is controlled by the backplane manager (MBM). You can view the status and error logs of the platform and manage the MBM using the command-line interface when you connect to the management port.

You access the management port through a Network Address Translator (NAT) box, which provides the platform with a unique IP address for the AMS and the hard partitions configured on the platform with a single point of access to the AMS.

The prompt of the management port is MBM>. See the CLI Reference manual on the Server Management CD-ROM.

For a list of commands you can perform at the MBM> prompt, enter help.

The MBM console output is logged to a file named PlatformName_MBM.log in the /usr/opt/ams/logs/cmfd.dated directory. By default, cmfd archives the console logs every seven days. You can change the archive schedule by selecting the Console Logfile Archiving Period ... item from the Consoles context menu.

2.5.1.2    GS80, GS160, and GS320 Platforms

In GS80, GS160, and GS320 platforms, the interface to the firmware is the System Control Manager (SCM). SCM commands allow an administrator to perform tasks such as check detailed hardware status, view error registers, partition the platform, and power partitions on and off. To issue SCM control commands to the firmware you must connect to the Master SCM console.

The Master SCM is the console associated with the lowest port number of the configured terminal server's port range. The SCM runs in two modes, SCM mode and console mode:

In SPM, you can determine which partition console is the Master SCM by displaying the Properties dialog box of a GS80, GS160, and GS320 platform.

To access the Master SCM, invoke the Telnet application from the partition associated with the SCM port.

For a list of the available SCM commands type help at the SCM prompt. See the AlphaServer GS80/160/320 Firmware Reference Manual for additional information.

2.5.2    Partitions

The SPM's left frame displays each platform's hard partitions and subpartitions. One hard partition and one subpartition within that hard partition are configured by default on ES47, ES80, and GS1280 platforms.

Hard partitions physically divide computing resources into separate logical systems; in this case the resources are CPUs and their associated memory. You can consider the platform as a whole as one hard partition. Each partition is capable of running an operating system with its own set of applications.

A subpartition is configured on the hard partition by default to enable you to load and run an operating system on the platform.

You can create new partitions using the AlphaServer Partition Wizard (see Chapter 4) and the AlphaServer Management Utility (see Section 3.12) on how to partition a platform.

2.5.3    Accessing the AMU

You can access the AlphaServer Management Utility (AMU), a Web-based application with which you can monitor and manage ES47, ES80, and GS1280 platforms from the SPM. The AMU does not recognize GS80, GS160, and GS320 platforms.

With AMU you can:

The AMU window is divided into two frames. The left frame displays a tree view of the platform's processor units by cabinet location. The right frame displays a graphical representation of the physical layout of the selected platform or the selected component of the platform.

For example, you can display a graphical representation of the platform's cabinets by clicking on Hardware in the left frame. You can move your mouse over the right frame to display information about each cabinet; for example, the number of processors, the system box it is running on, and the status.

See Chapter 3 and the AMU's online help for more information.

2.5.4    Accessing the APW

The AlphaServer Partitioning Wizard (APW) provides an easy-to-use graphical interface for adding or removing partitions from a selected platform.

You can access the APW by selecting a platform and selecting APW from the drop-down menu or the Actions item of the main menu. You can use the APW to partition ES47/ES80/GS1280 and GS80/GS160/GS320 platforms.

For information about using the APW, see Chapter 4.

2.5.5    Viewing a Platform's Properties

You can view the properties of a selected platform or console using the Properties... item from the selected platform or console's context menu or from the Actions Menu.

2.5.5.1    ES47, ES80, and GS1280 Platform Properties

Figure 2-12 shows the Properties dialog box for a ES47, ES80, and GS1280 platform. A description of the fields in that box follows.

Figure 2-12:  Platform Properties Dialog Box (ES47, ES80, and GS1280)

2.5.5.2    GS80, GS160, and GS320 Platform Properties

Figure 2-13 shows the Properties dialog box for a GS80, GS160, and GS320 platform. A description of the fields in that box follows.

Figure 2-13:  Platform Properties Dialog Box (GS80, GS160, and GS320)

2.5.6    Removing a Platform

You can remove a platform and its associated consoles by selecting Remove from the selected platform's context menu or from the Actions item of the menu bar. You will be asked to confirm the removal (Figure 2-14) before the platform is removed.

Figure 2-14:  Remove Platform Confirmation Dialog Box

2.6    Managing Partitions

ES47/ES80/GS1280 and GS80/GS160/GS320 platforms can be configured into one or more hard partitions that can contain one or more subpartitions. By default, ES47, ES80, and GS1280 platforms are configured with a default hard partition that contains a default subpartition. The subpartition allows an operating system to run on the platform. You can load an operating system onto a subpartition at its SRM prompt. See the SRM Console Reference on the Server Management CD-ROM for more details.

Use the SPM to do the following:

2.6.1    Configuring a Subpartition

You configure a subpartition to be managed by SPM using the Configure dialog box (Figure 2-15). Configuring a subpartition allows you to connect to the subpartition's console.

Figure 2-15:  Configure Subpartition Dialog Box

To configure the console, you must enter the following information:

2.6.2    Accessing the HP Insight Management Agents

You can use the SPM to access the HP Insight Management Agents running on the Tru64 UNIX or OpenVMS operating system of a selected subpartition.

Note

To access the Insight Management Agents, the subpartition must be running the operating system.

You cannot access the Insight Management Agents from a subpartition running a Linux environment.

Figure 2-16:  Insight Management Agents

Figure 2-16 shows the Insight Management Agents Device Home Page.

The Insight Management Agents allow you to look across a heterogeneous computing services environment and access information through a Web browser about any entity connected to the network. The Insight Management Agents can be run on partitions running Tru64 UNIX or on OpenVMS servers. You can view your hardware configuration and monitor the state of the system.

Using the Insight Management Agents for Tru64 UNIX, you can view your AlphaServer hardware configuration and monitor the state of the system. You can access the Tru64 UNIX System Management Home Page, SysMan Menu, SysMan Station, and the Sys_Check Configuration reports from any browser.

See http://h30097.www3.hp.com/cma for documentation of Insight Management Agents for Tru64 UNIX and http://h71000.www7.hp.com/openvms/products/mgmt_agents/ for documentation of Insight Management Agents for OpenVMS.

2.6.3    Enabling and Disabling Events Generated from Console Output

You can enable or disable events generated from console output from the Console Logging submenu of the selected subpartition's Actions menu.

By default, events are generated for each platform management console and OS console connection defined. Messages that are normally echoed to the consoles are parsed; if a match between the output and any entry in the specified event definition file is found an event with the indicated priority is generated.

Be aware, however, that event generation for a given port is disabled when a user is connected to that port.

2.6.4    Using the Event Viewer

You can view events that have been generated either from operating system console output or from AMS components in the Event Viewer. In the main SPM window, open the Event Viewer from the Actions menu of a platform or the AMS.

Note that the Event Viewer does not dynamically display new events. However, you can use the Refresh button to update the display. Figure 2-17 shows the SPM's View Events dialog box displaying events from platform2.

Figure 2-17:  View Events Dialog Box

You must choose to log console output and monitor events from the Console Logging option in a subpartition's Actions menu in order to view its events in the Event Viewer.

The Event Viewer is part of the Event Manager (EVM) system. EVM is a comprehensive event management system that, in addition to providing traditional event handling facilities, unifies events from many channels, such as a log file, to provide a systemwide source of information.

An EVM event is a package of information that can be passed among programs and stored in files. You can receive events from either the AMS components or from the operating system running on a subpartition. See the EVM chapters in the Tru64 UNIX System Administration guide and Programmer's Guide for more information.

Examples of events you can receive from the AMS components are:

Examples of events you can receive from the operating system are:

You can view events generated by AMS components by selecting the AMS icon with the right mouse button in the SPM's left frame and selecting View Events.

You can view events that match the ams.* event template by selecting the platform icon with the right mouse button in the SPM's left frame and selecting View Events.

2.6.5    Viewing ES47, ES80, and GS1280 Subpartition Properties

You can view the properties of ES47, ES80, and GS1280 subpartitions configured on the SPM.

Figure 2-18:  Subpartition Properties Dialog Box

Figure 2-18 shows the SPM's Subpartition Properties dialog box. A description of the fields in this box follows:

2.7    Adding a Standalone Console

SPM lets you add standalone consoles (also called generic consoles) to the Consoles tree. By doing this, you can access non-AMS consoles through the SPM.

To do this, select the Add Standalone Console ... menu item from the Standalone Console's context menu or from the Actions menu when the Standalone Consoles listing is highlighted. This displays the Add Standalone Console dialog box, in which you provide a name for the console, its IP address and port number, a description, and an event definition file to be identified with this console.

After you have created a standalone console, its context menu is the same as that for AMS platform consoles (see Section 2.8), with the addition of the following items:

2.8    Working with Consoles

MBM, master SCM, and SRM/OS consoles are available from their platform and partition and from the Consoles tree node. Standalone consoles are available only from the Consoles tree. From a console's menu you can perform the following tasks:

2.8.1    Telnet Access to Consoles

You can connect to a management or SRM/OS port or subpartition's port using Telnet in one of the following access modes:

To create a Telnet session to a ES47, ES80, and GS1280 backplane manager, select the Telnet to MBM item from the Action menu or context menu of a selected platform or console MBM. To create a Telnet session to a console, select the Telnet to Console item from the Action menu or context menu of the selected platform.

To create a Telnet session to a GS80, GS160, and GS320 terminal server, select the Telnet to Terminal Server ... item from the Action menu or context menu of a selected platform.

To create a Telnet session to a console, select the Telnet to Console item from the Action menu or context menu of the selected console.

2.8.2    Identifying, Contacting, and Disconnecting Other Users

The SPM allows you to identify the users connected to the console, broadcast messages to them, and disconnect them from the console.

2.8.2.1    Displaying and Users

You can see which users are connected to AMS-managed consoles and disconnect them from those consoles.

The user names, IP addresses, and connection modes of the connected users are displayed. This feature gives you the means to resolve problems you may have accessing a console that is managed by the AMS.

The user names of users who are connected using a different console manager cannot be displayed.

2.8.2.2    Broadcasting a Message

You can send a message to the users connected to a specific console or all consoles managed by AMS.

Figure 2-19:  Broadcast to All Users Dialog Box

Users who are connected using a different console manager will not receive the broadcast messages.

2.8.3    Console Logging

You can turn console logging on or off by selecting Console Logging from the context menu of the selected subpartition or console listing or from the Action menu. From this menu, you can chose one of the following items:

You can view a console's log by selecting View Console Log... from the context menu of the selected subpartition or console or from the Action menu.

2.8.4    Enabling and Disabling a Console

When a console is enabled, console connections using another console manager cannot be established. To allow another console manager to access a console, you should disable the console.

The cmfd establishes connections to all enabled consoles; all consoles are enabled by default.

If you need to disable the cmfd connection in order to connect to a console using another console manager, you can do so by selecting Enable Console item from the console's drop-down menu. A checkmark in front of the Enable Console item indicates that the console is enabled. You can also see if a console is enabled by viewing its properties, in which an enabled console has a value of True.

2.8.5    Port Mapping

The SPM's port mapping feature lets you configure a console or platform management port to be accessible by other console managers via cmfd.

You access this feature from the context menu of the Consoles tree item or from the Actions menu when Consoles is highlighted. Selecting the Map Console Ports for External Access item opens a window (Figure 2-20), which lists the identified consoles, their IP Addresses, and their port numbers.

In this dialog box you can specify a port number to be mapped to the actual port. For example, if you map port 323 to port 1501, a user on a remote machine could access the console at port 323 by issuing a command like the following: 

telnet ams.hostname.customer 1501

After entering a user name and password at the prompts, the user will be connected to console corresponding to port 323.

The dialog box also lets you enable or disable security. By enabling security, you require authentication for the clients that connect to this port.

Figure 2-20:  Port Mapping Dialog Box

2.8.6    Viewing a Console's Properties

You bring up the Console Properties window of a selected console by selecting the Properties... item from the console's context menu or from the Actions Menu. You can also click on the console to view its properties in the right frame.

The properties that are displayed vary according to the type of console you select. For example, the properties for a standalone console include the console's IP address and the properties for a console for a GS80, GS160, and GS320 platform may include the property for a Master SCM. Figure 2-21 shows a console for a ES47, ES80, and GS1280 platform.

Figure 2-21:  Console Properties Box

The following list describes the console properties you may see.

2.8.7    Creating and Modifying an Event Definition File

You can create a new event definition file from scratch or by using an existing event definition file as a template. You can also modify an existing file.

You access this feature from the context menu of the Consoles tree item or from the Actions menu when Consoles is highlighted. Selecting the Create/Modify Event Definition File ... item opens the Create/Modify Event Definition File window.

Figure 2-22:  Create/Modify Event Definition File Dialog Box

When you first open the window, the File to Open field has an entry for a new file. A drop-down menu lets you select one of the existing event definition files. You can, for example, select the default.event file, change its patterns and do one of the following:

The text field contains three columns, Patterns, Priority, and Case Sensitive. To add or modify text in each field, click on the field, delete the existing text, and type the new text. In the Case Sensitive column, put a 1 (one) if you want the pattern to be case sensitive, or 0 (zero) if you do not want the pattern to be case sensitive.

The buttons in Row operations fields do the following:

2.8.8    Setting the Archive Period for Log Files

By default, SPM logs console output for seven days and then archives the file. Using the Console Logfile Archive Period menu item, you can specify the number of days before log files are archived.

You access this feature from the context menu of the Consoles tree item or from the Actions menu when Consoles is highlighted. Selecting Console Logfile Archive Period ... brings up the Set Logfile Archive Period dialog box (Figure 2-23).

Figure 2-23:  Set Log File Archive Period Dialog Box

You view current console log files by selecting View Console Logs ... from the context menu of a selected platform in the Platforms tree. After a file is archived, you can view them from within a terminal window in the /usr/opt/ams/logs directory.