5    Using the Platform Console Manager

Following a brief overview of the Platform Console Manager (PCM) and the main PCM window in Section 5.1 and Section 5.2, the following topics are discussed:

• Adding platforms and consoles to the PCM (Section 5.3).

• Modifying the properties of platforms and consoles managed by PCM (Section 5.4)

• Removing platforms and consoles from the list of managed items (Section 5.5)

• Stopping and restarting the cmfd daemon from the PCM (Section 5.6)

• Viewing and modifying the number of days that the cmfd daemon logs console output before archiving the log file (Section 5.7)

• Working with events (Section 5.8)

• Connecting to the ES47/ES80/GS1280 and GS80/GS160/GS320 platform management port (Section 5.9)

• Managing consoles Connecting to a system's console (Section 5.10)

5.1    Overview

The Platform Console Manager (PCM) is a character-cell application that provides access to the consoles of subpartitions and systems configured in the PCM.

You can use the PCM to connect to the platform's management port, connect to consoles, view the status of each console, and view the console's log files. You can also monitor the latest console output from the managed systems in a continuously updated, timestamped list located in the main PCM window (Figure 5-1).

Figure 5-1:  Main PCM Window

The Console Management Facility (CMF) daemon cmfd provides the PCM access to the consoles and logs console output; it logs all console sessions by default. See cmfd(8) for more information.

5.1.1    Starting, Navigating, and Exiting the PCM

You must be root or a member of the amsuser group on the AMS machine to use the PCM.

To start the PCM:

1. Unset your display:

   # unset DISPLAY
   

2. Start the PCM:

   # /usr/bin/pcm
   

Press [Ctrl/g] for keyboard navigation help.

Select Exit from the main PCM window or press [Ctrl/c] to exit PCM.

5.1.2    Customizing the Telnet Escape Sequence

The default Telnet escape sequence is [Ctrl/x]. You can customize the escape sequence of Telnet sessions you launch from the PCM. You can ensure that you choose a unique escape sequence that does not conflict with escape sequences of other applications.

When using the Bourne and Korn shells, configure the Telnet escape sequence and add the following line to the .profile. file:

AMS_SESSION_ESC=^G; export AMS_SESSION_ESC

In this example, the Telnet escape sequence is changed to ^G.

When using the C shell, add the following line to the .login file:

setenv AMS_SESSION_ESC ^G

In this example, the Telnet escape sequence is changed to ^G.

The PCM displays the configured escape sequence in the top of the Telnet window.

5.2    The Main PCM Window

The Main window is launched when you start up PCM. It has three principal sections: a systems view and selection area, buttons to perform various actions, and console message area.

For a guide to navigating the character cell environment, see Appendix G.

5.2.1    System View and Selection Area

The system view and selection area displays information you specified when you added a platform or console (see Section 5.3). This information includes the console's name, the name of the platform on which the console is running, the model number of the platform, and a description of the system. Also included is a status column, which displays one of the following:

• Open — cmfd has a connection to the console.

• In use (RO) — All the users connected to the console are in Read-Only mode.

• In use (SH) — At least one user is connected in Shared mode. Other users may be connected in Shared or Read-Only modes.

  In this mode, users with shared connections can all make changes that affect the work of other shared-connection users.

• In Use (EX) — One user is connected in Exclusive mode. Other users may be connected in Read-Only mode. A connection as Shared is not possible.

• Inaccessible — The platform or network is down.

• Refused — The port is in use, external to cmfd.

• Disabled — The console is disabled.

• Unknown — An internal error has occurred. Often, this status occurs because the cmfd daemon is not running.

Select any column heading to sort by that field. For instance, to sort the systems by platform, select the Platform column heading, and the managed systems will be sorted alphabetically by platform.

5.2.2    Buttons

When you select the Connect..., Console..., Tools..., Events..., or Configure... buttons in the Main window, you open a new window in which you can perform various actions. Selecting OK in any of those windows returns you to the Main window. A description of the button actions follows.

Connect...

Selecting Connect... lets you choose the type of connection you want to make to the selected system:

• Read-only mode

  Allows you to see console output, but not to send input to it.

• Shared mode (the default)

  Allows you to see console output and send input to it. The input and output of connections is shown in all open console windows.

• Exclusive mode

  Allows you to take complete control of the console, preventing other users to connect using share or exclusive modes. Read-only connections are allowed.

Figure 5-2:  Connect Dialog Box

If the selected system is on an ES47, ES80, and GS1280 series platform and its status is REFUSED, a force connection dialog box will appear. Force connection allows you to disconnect the external user connected to the port. To disconnect the external user select Yes, otherwise, select No to terminate the connection attempt.

Figure 5-3:  Force Connection Dialog Box

Select the type of connection you want and then press OK.

If an error occurs, for example, you request a shared connection when a user is connected in exclusive mode, a new window displays the error.

Console...

Selecting Console... lets you do one of the following:

• View the console log (the default action).

• View/Disconnect Users

  Selecting this option (see Figure 5-24) brings up a window that lists the users, their IP addresses, and their connection mode. This window is refreshed every 30 seconds.

  The Disconnect All option disconnects all the users connected to the console. Once the users are disconnected, the window is refreshed to show any connected user. Selecting OK closes this window and returns you to the main window.

• Send a message to users on the console. The message is limited to 160 characters.

  Selecting this option brings up a new window in which you can send a message to users. Selecting OK in that window brings up a window that displays a success message or an error message (for example, a message that exceeds the 160 character limit). Selecting OK returns you to the Send Message window, where selecting OK returns you to the Main window. The Send Message window is also available from the Tools... menu.

• Disconnect users from the console.

  Selecting this window brings up a new window in which you can disconnect all or specific users from the console. This includes users who are connected in Exclusive mode.

Tools...

Selecting Tools... lets you do one of the following:

• Restart/Stop cmfd (see Section 5.6.1 for more details).

• View/Modify log archiving interval

  Selecting this option lets you specify the number of days before log files are archived. By default, the cmfd daemon logs console output for seven days and then archives the file.

• Send a message to all consoles.

  This option acts the same as the Send Message option in the Console... menu.

• Map a console to a port on the local host.

  Selecting this option brings up a window that lists all the configured consoles and the port on the local host that are mapped to them. To assign or modify a port on the local host to a console, select the console in the list and press Modify button. This brings up a new window in which you can assign a port on the local host to that console and also specify whether authentication is required for the clients that connect to this port. You select OK to complete the process.

Figure 5-5:  Modify Mapped Port Dialog Box

Events...

Selecting Events... lets you do the following:

• View events.

• Create a new event file.

• Modify an existing event file.

• Delete an event file.

See Section 5.8 for more details.

Configure...

Selecting Configure... lets you do the following:

• Add a platform or console (see Section 5.3).

• Modify a selected item (see Section 5.4).

• Delete a selected item from the list of managed systems (see Section 5.5).

5.2.3    Console Output

In the bottom of the Main window, you can view a consolidated log file for all managed systems. The time stamp uses the format yy/mm/dd_hh:mm:ss (Year/Month/Day_Hours:Minutes:Seconds). Select any column heading (Time, System, or Message) to sort by that field.

The PCM displays the console log files that were generated during the past seven days. To view older log files, you must view them in the /usr/opt/ams/logs directory within a terminal window.

5.3    Adding a Platform or Console

The steps for adding a platform or a console to the PCM are similar. The main difference is in the data you supply to the Add Platform and Add Console dialog boxes.

5.3.1    Adding a Platform

To manage a platform from the PCM, you add it to the PCM's list of managed systems. When you add a platform, the changes are dynamically updated in the PCM's main window. Once you add a platform, you can connect to the management port of the platform and view the console's log.

To add a platform to the PCM:

1. Select Configure....

2. Select Add Platform.

3. Select OK. The Add Platform: Specify Type dialog box is displayed (Figure 5-6).

   Figure 5-6:  Add Platform: Specify Type Window

   

4. Choose your platform type, either ES47, ES80, and GS1280 or GS80, GS160, and GS320. The next dialog box you see depends on the platform you chose.

5.3.1.1    Add an ES47, ES80, and GS1280 Platform

Figure 5-7 shows the dialog box for adding an ES47, ES80, or GS1280 platform. A description of the fields in that dialog box follows.

Figure 5-7:  Add an ES47, ES80, and GS1280 Platform Window

1. Enter the name of the platform to be managed.

2. Select the model from the dropdown list.

3. Enter the IP address of the Nat box to which the system's console is connected.

4. Provide a description of the platform.

5. Select a Layout Template File by typing one in the field or by selecting one from the Select a Layout Template window (Figure 5-8) that you bring up by selecting the Browse... button.

   Figure 5-8:  Layout Template Selection Window

   

6. Enable or disable Console access.

   If you disable console access, the logging of console output and generation of events from the console output will also be disabled.

7. Enable or disable Log console output.

   If you disable the logging of console output, the generation of events from the console output will also be disabled.

8. Enable or disable Generate events from the console output.

9. Enter a name for an event definition file or select the Browse... button to bring up a selection of names to choose from in the Select an event definition file window (Figure 5-9).

   Figure 5-9:  Select an Event Definition File Window

   

10. Select OK.

The PCM's main window is displayed and the new platform is now included in the list of managed systems. The MBM console output of the new platform is included in the consolidated console log displayed in the PCM's main window.

If the change does not register in the PCM's display within a few minutes, there may be a problem with the cmfd daemon. Restart the cmfd daemon from the PCM Tools menu. See Section 5.6.1 for more information.

5.3.1.2    GS80, GS160, and GS320 Platforms

Figure 5-10 shows the dialog box for adding an GS80, GS160, or GS320 platform. A description of the fields in that dialog box follows.

Figure 5-10:  Add a GS80, GS160, and GS320 Platform

1. Enter the name of the platform to be managed.

2. Select the model from the dropdown list.

3. Enter the IP address of the terminal server.

4. Provide a description of the platform.

5. Specify a port range by entering a minimum port number and a maximum port number.

6. Enable or disable Console access.

   If you disable console access, users will be unable to Telnet to the terminal server.

7. Select OK.

The PCM's main window is displayed and the new platform is now included in the list of managed platforms.

If the change does not register in the PCM's display within a few minutes, there may be a problem with the cmfd daemon. Restart the cmfd daemon from the PCM Tools menu. See Section 5.6.1 for more information.

5.3.2    Adding a Console

To manage a console from the PCM, you add it to the PCM's list of managed systems. You can add a console that is on an AlphaServer Management Station (AMS) platform or add a standalone console. Each console represents a name for a port on a subpartition to which you can connect via cmfd, which logs the console's output and scans the output for events.

To add a console to the PCM:

1. Select Configure....

2. In the Configure dialog box, select Add Console.

3. Select OK. The Specify Type dialog box is displayed.

4. Select the type of console you want to add — an AMS platform console or a standalone console.

5. Select OK and continue with the procedure for adding the AMS platform console or a standalone console, as applicable.

5.3.2.1    Adding an AMS Platform Console

Figure 5-11 shows the dialog box for adding a platform console. The steps that follow describe the fields in that dialog box.

Figure 5-11:  Add a Console Dialog Box

1. Enter the name of the platform or browse from the list of available platforms.

2. Enter a name for the console.

3. Enter the port number for the console.

4. Enter the operating system (OS) type that will run on the console or browse from the list of supported OS types.

5. Enable or disable the following options. By default, these options are enabled:

   1. Enable console access.

      If you disable console access, you will not be able to connect to the console. The logging of console output and generation of events from the console output will also be disabled.

   2. Log console output.

      If you disable the logging of console output, the generation of events from the console output will also be disabled.

   3. Generate events from the console output.

6. Enter a name for an event definition file or browse from a selection of names.

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

8. Select OK

The PCM's main window is displayed and the new console is now included in the list of managed systems.

If the change does not register in the PCM's display within a few minutes, there may be a problem with the cmfd daemon. Restart the cmfd daemon from the PCM Tools menu. See Section 5.6.1 for more information.

5.3.2.2    Adding a Standalone Console

Figure 5-12 shows the dialog box for adding a standalone console. The steps that follow describe the fields in that dialog box.

Figure 5-12:  Add a Standalone Console Dialog Box

1. Enter a name for the console.

2. Enter the IP Address for the terminal server (or other device) to which the console is connected.

3. Enter the port number for the console.

4. Enable or disable the following options. By default, these options are enabled:

   1. Enable console access.

      If you disable console access, you will not be able to connect to the console. The logging of console output and generation of events from the console output will also be disabled.

   2. Log console output.

      If you disable the logging of console output, the generation of events from the console output will also be disabled.

   3. Generate events from the console output.

5. Enter a name for an event definition file or browse from a selection of names.

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

7. Select OK

The PCM's main window is displayed and the new console is now included in the list of managed systems.

If the change does not register in the PCM's display within a few minutes, there may be a problem with the cmfd daemon. Restart the cmfd daemon from the PCM Tools menu. See Section 5.6.1 for more information.

5.4    Modifying Platform and Console Properties

When you modify a platform or console (either an AMS platform console or a standalone console), the cmfd daemon restarts automatically and the changes are dynamically updated in the PCM's main window.

The modification process is the same for platforms and consoles and the dialog boxes are similar to those for adding platforms and consoles.

To modify a platform or console configured in the PCM:

1. Select the platform or console you want to modify.

2. Select Configure....

3. Select Modify the selected item.

4. Select OK.

   The Modify Platform or Modify Console dialog box is displayed. This dialog box displays the same information you entered when you created the platform or console. For example, the Modify an ES47, ES80, and GS1280 Platform dialog box in Figure 5-13 contains the same information that was entered in Figure 5-7.

   Figure 5-13:  Modify a Platform Dialog Box

   

5. Modify the data you want (all fields must remain filled). See Section 5.3.1 and Section 5.3.2 for descriptions of the data fields you can modify.

6. Select OK.

The PCM applies the new properties to the system and the PCM's main window is displayed.

If the change does not register in the PCM's display within a few minutes, there may be a problem with the cmfd daemon. Restart the cmfd daemon from the PCM Tools menu. See Section 5.6.1 for more information.

5.5    Removing a Platform or Console

When you remove a platform or console, the cmfd daemon restarts automatically and the changes are dynamically updated in the PCM's main window.

To remove a platform or console from the PCM:

1. Select the platform or console you want to delete.

2. Select Configure....

3. Select Delete the selected item.

4. Select OK.

   A dialog box with the properties of the platform and console is displayed.

5. Select OK to remove the selected platform or console.

The PCM's main window is displayed, with the removed platform or console no longer included in the list of managed systems.

If the change does not register in the PCM's display within a few minutes, there may be a problem with the cmfd daemon. Restart the cmfd daemon from the PCM Tools menu. See Section 5.6.1 for more information.

5.6    Restarting and Stopping the cmfd

You can restart and stop the cmfd directly from the PCM, as described in the following sections.

5.6.1    Restarting the cmfd

Sometimes a console's status is Unknown or the console is unresponsive. You may be able to correct this problem by restarting the cmfd daemon.

Restarting the cmfd closes all connections to all consoles. Any unsaved work being done on a console will be lost when that console closes. You should ensure that no one is connected to the consoles before stopping the cmfd.

Figure 5-14:  Restarting the cmfd

Figure 5-14 shows the PCM Tools menu with the Restart the Console Management Facility daemon (cmfd) option displayed.

To restart the cmfd:

1. Select Tools...

2. Select Restart/Stop the Console Management Facility daemon (cmfd).

3. Select OK.

   This opens the Restart/Stop CMFD dialog box.

4. Select Restart the Console Management Facility Daemon (cmfd).

5. Select OK.

   This opens a confirmation dialog box.

6. Select OK.

   The cmfd restarts and the PCM's main window is displayed.

5.6.2    Stopping the cmfd

Stopping the cmfd closes all connections to and stops the logging of all consoles. Any unsaved work being done on a console will be lost when that console closes. You should ensure that no one is connected to the consoles before stopping the cmfd.

To stop the cmfd:

1. Select Tools...

2. Select Reset/Stop the Console Management Facility daemon (cmfd).

3. Select OK.

   This opens the Restart/Stop CMFD dialog box.

4. Select Stop the Console Management Facility Daemon (cmfd).

5. Select OK.

   This opens a confirmation dialog box.

6. Select OK.

   The cmfd daemon stops and the PCM's main window is displayed.

   The status for all managed consoles changes to Inaccessible.

5.7    Setting Log Archiving Interval

The cmfd daemon logs console output for specified number of days and then archives the file. You can view the specified archiving interval (which by default is seven days) or modify it as follows:

Figure 5-15:  Set Log Archive Interval Dialog Box

1. Select Tools...

2. Select View/Modify Log Archiving Interval

3. Select OK.

4. Enter the log archiving interval (in days).

5. Select OK.

The new archiving interval is established and the PCM main window is displayed.

5.8    Working with Events

AMS provides event definition files for each supported platform type and its associated console. The files are located in the events directory, /usr/opt/ams/events. You can use these files as provided, modify them, or create new files. The following sections describe the actions you can take when you select the Events... option from the Main window.

By default, events are generated for each MBM and OS console connection defined. Messages that are normally echoed to the MBM or OS console 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.

5.8.1    The Create Events Definition File Window

Selecting the Create Events File option from the Events window brings up a Create Events Definition File window (Figure 5-16). From this window you can add a new event, modify or delete an event, and import event patterns from existing files.

Figure 5-16:  Create Events Definition File Window

Create a File

To create a new file, do the following:

1. Type in a name. An event definition file name can contain only alphanumeric characters, in addition to the hyphen (-), underscore (_), and period (.). The use of the .event file extension is a common convention, but is not necessary. You cannot specify an existing event name.

2. Select Add... or Import... to bring up a new window:

   • The Add... dialog box (Figure 5-18) lets you specify patterns, priorities, and whether you want the pattern to be searched in a case-sensitive manner.

   • The Import... dialog box lets you replicate the patterns, priorities, and case-sensitivity specified in an existing event definition file.

Add Patterns

To add a pattern:

1. In the Add... dialog box (Figure 5-18), type in the pattern you want to monitor and a priority from 100 to 700. You can change the default case sensitivity by pressing the Return Key while positioned in that field. Notice that the Modify... and Delete menus are inactive during this action. When you are satisfied, select OK.

2. To add additional patterns, reselect Add... and repeat the steps.

Import Patterns

When you import patterns from an existing event definition file, the Pattern list box of the Create an Event Definition File window must be empty.

In the Import... dialog box:

1. Select an existing event definition file.

   A new window will open that lists existing event definition files (Figure 5-17).

   Figure 5-17:  Import an Event Pattern

   

2. Highlight an event definition file and press Return to see its pattern list.

3. When you determine which file's pattern list you want to import, highlight that event definition file and select OK. You will be returned to the Create an Event Definition File window, where the new patterns will be listed.

   From this point you can add additional patterns and can modify or delete existing patterns.

4. When you are finished, select OK in the Create an Event Definition File window to return to the Main window.

You cannot create an empty event definition file.

Modify or Delete Patterns

After you have named your new event definition file and added at least one pattern, you can modify or delete any patterns listed.

1. Select the pattern you want to modify or delete and select the Modify... or Delete... option.

   • Selecting Modify... opens a window in which you can change the existing pattern. After making changes, select OK. You can continue to add patterns.

   • Selecting Delete... removes the pattern from the pattern list. If the list is empty, the Import... option becomes available.

2. Select OK in the Create an Event Definition File window to return to the Main window.

5.8.2    Modifying or Deleting an Existing Event Definition File

You can modify or delete any existing file from the Event Definition File window.

Selecting Modify... or Delete... opens a window that lists the existing event definition files. Highlight the file you want to modify or delete.

• If you selected the Modify... option, the file you highlight opens in a window that allows you to modify the properties. The window you see and the steps you take are similar to those when you create a new event definition file.

• If you selected the Delete... option, the file you highlight is deleted from the events directory. You can not delete an event definition file that is being used by a console.

5.8.3    Generating Events from Console Error Messages

Use the Create Event Definition File: Add dialog box (Figure 5-18) to generate Event Manager events from console error messages.

To generate events from console error messages, first choose a type of console error message you want to generate into an event. For example, you may want to be notified when a system crash has occurred.

Figure 5-18:  Events: Add Dialog Box

Then enter a regular expression in the PCM Events dialog box that matches the error message you want and the priority you want to assign to the event. For example, to generate system crash error messages into events, enter crash and enter a priority of 700. Any console error message that contains the string crash is generated into an event with a priority of 700.

After you configure the PCM to generate events, you can view the events that match your filter by opening the Event Viewer from the PCM's Events dialog box. See evm(5) and the Event Viewer's online help for more information.

You also can use EVM to notify you when interesting events occur. EVM can display notifications on screen, in e-mail messages, or in pager messages. See Appendix E and the EVM chapters in the Tru64 UNIX System Administration guide and Programmer's Guide for more information.

To generate events:

1. Select Events in the PCM's main window.

2. Select the Specify Search Patterns checkbox in the Events dialog box.

3. Select Add.

   The Events: Add dialog box displays.

4. Enter a search pattern using regular expressions. The PCM will search the console error logs for this pattern and, if found, generate an EVM event for that error.

   For example, enter the regular expression crash. The PCM will generate events for error messages containing the string crash.

   See grep(1) for more information.

5. Enter the priority of the event you want to generate.

   You can use the priority levels to select the events EVM will notify you of or to sort the display in the Event Viewer.

   By default, EVM notifies you of events with a high priority level of 500 to 700. The high priority levels range from critical to alert to emergency. See Table 5-1 for more information.

6. Select OK.

   The PCM's Events dialog box displays. The regular expression and the priority you entered are displayed in the list of events in the PCM Events dialog box.

7. Select OK to return to the PCM main window.

Table 5-1:  EVM Event Priorities

5.8.4    Viewing Events

Use the PCM to launch the Event Viewer to display Event Manager (EVM) events generated from console error messages.

Figure 5-19:  View Events Dialog Box

Figure 5-19 shows the summary of events received from the platform harsh.

To view events generated from console error messages:

1. Select Events in the PCM's main window.

2. Ensure that View Events is selected.

3. Select OK.

The EVM Event Viewer launches.

EVM can notify a user via e-mail or a pager about events it receives. EVM sends e-mail messages of events with a priority of 700 or higher to the root user of the AMS, by default. You can configure EVM to let you specify a priority and the name of a user you want notified.

See Appendix D for information about using Event Manager and Appendix E for information about how to send selected events via e-mail.

5.9    Connecting to a Platform's Management Port

You can establish a connection to the management LAN of ES47, ES80, and GS1280 platforms directly from the PCM by connecting to the platform's management port.

Figure 5-20:  Connecting to the Platform's Management Port

Figure 5-20 shows the prompt of the platform's management port displayed after you connect to it from the PCM.

The management LAN connects to the platform's management software, which is controlled by the backplane manager (MBM) of ES47, ES80, and GS1280 platforms . You can view the status and error logs of the platform and manage the MBM when you connect to the management port.

For ES47, ES80, and GS1280 platforms, you access the MBM through a Network Address Translator (NAT) box. A NAT box 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. It allows you to assign to the hard partitions one set of IP addresses for internal traffic and a second set for external traffic.

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

To connect to a platform's management port:

1. Select the platform or console MBM to which you want to connect.

2. Select Console...

3. Select Connect to the platform's management port.

4. The Telnet session starts.

To exit the Telnet session and return to the PCM's main window:

1. Press [Ctrl/x], which exits from the console's prompt.

   See Section 5.1.2 for information on customizing the Telnet escape sequence.

2. Press [Return] to return to the PCM.

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

5.10    Managing Consoles

You can manage the consoles of systems created on a platform by using the PCM to:

• Connect to the console (Section 5.10.1)

• Determine a console's status (Section 5.10.2)

• Monitor a console's output (Section 5.10.3)

• Disconnect users from the console (Section 5.10.5)

• View console log files (Section 5.10.6)

5.10.1    Connecting to a Console

You can connect to the console of a managed system in the main PCM window.

The Telnet session connects through the cmfd daemon to a specific system's console. The cmfd logs each Telnet session.

Note

There can be only one connection to a console open at a time. If a connection to a console is already established by another user, you will not be able to connect to the console.

You can clear a console from the PCM, but you should do this with caution and only as a last resort. Clearing the console closes the Telnet connection to it and closes any applications that may be running by a user, which could result in the loss of unsaved data.

It is important to terminate the Telnet session when you are finished since the port will not be accessible while the session is in progress.

To connect to a console:

1. Move the cursor to the system to which you want to connect and press [Enter].

2. Select Connect to the console.

3. Select OK.

   The Telnet session starts. Press [Return] until you see the console prompt.

   Either the firmware prompt (>>>) displays if no operating system is installed, or the operating system's login prompt displays.

   Enter help for a list of commands at the firmware prompt.

To exit the Telnet session and return to the PCM's main window:

1. Press [Ctrl/x], which exits from the console's prompt and goes to the CMF prompt (cmf>).

   See Section 5.1.2 for information on customizing the Telnet escape sequence.

2. Press [Return] to return to the PCM.

5.10.2    Determining a Console's Status

You can determine a console's status in the List of Managed Systems located in the top of the main PCM window. For example, if a console has a status of In Use, you can find which user is connected to it and ask that user to disconnect.

Figure 5-21:  Console Status Display

Figure 5-21 shows the list of managed systems and their status.

The different status labels indicate the following:

• Open — cmfd has a connection to the console.

• In use (RO) — All the users connected to the console are in Read-Only mode.

• In use (SH) — At least one user is connected in Shared mode. Other users may be connected in Read-Only mode.

  In this mode, users with shared connections can all make changes that affect the work of other shared-connection users.

• In Use (EX) — One user is connected in Exclusive mode. Other users may be connected in Read-Only mode. A connection as Shared is not possible.

• Inaccessible — The platform or network is down.

• Refused — The port is in use, external to cmfd.

• Disabled — The console is disabled.

• Unknown — An internal error has occurred.

The list of systems is sorted by System by default. To sort by either Platform, Model, Console, or Description, select the heading by which you want to sort.

5.10.3    Monitoring a Console's Output

You can monitor a list of consolidated error messages produced by all consoles managed by the PCM. The PCM provides a real-time display of all console output received from all configured systems. It displays the output in a sortable list at the bottom of its main window. Each new line of console output is appended to the list, which scrolls automatically to keep each new line visible.

To view log files of individual systems, either sort the list by System, or view the system's log file in the /usr/opt/ams/logs directory.

Figure 5-22:  PCM Console Log

Figure 5-22 shows the latest console output from the managed systems sorted by the time each message was received.

You can customize the console log display by selecting a column heading to sort the output list. For example, to sort by system, select the System column heading.

The PCM displays the console log files that were generated during the past seven days. To view older log files, you must view them in the /usr/opt/ams/logs/cmf.dated directory within a terminal window.

5.10.4    Viewing the Consoles' Logs

Use the PCM to view console error messages generated during the past seven days.

Figure 5-23:  View a Console Log

Figure 5-23 shows the PCM Console menu with the View console log option selected.

To view older log files, you must view them in the /usr/opt/ams/logs/cmf.dated directory within a terminal window.

To view a console's log:

1. Select the system to which you want to connect in the PCM's main window.

2. Select Console...

3. Select View console logs.

4. A dialog box opens displaying the logs.

5. Press [q] to return to the main PCM window.

5.10.5    Disconnect a Users from a Console

There can be only one connection to a console open at a time. If a connection to a console is already established by another user, you will not be able to connect to the console without disconnecting that user.

Figure 5-24:  Disconnecting Users from a Console

Figure 5-24 shows the PCM Console menu with Disconnect users from console selected.

Although you can disconnect another user from the PCM, you should do so with caution and only as a last resort. Disconnecting a user closes that Telnet connection, thereby closing any applications the user may be running. This could result in the loss of unsaved data.

To disconnect a user from a console managed by the PCM:

1. Select the system whose console you want to clear.

2. Select Console...

3. Select View/Disconnect users.

4. Select OK.

   This brings up the View/Disconnect Users dialog box, which lists all connected users.

5. Select Disconnect All.

   The PCM closes all connections to the console.

6. Press [Return] to return to the main PCM window.

5.10.6    Managing Console Log Files

The PCM displays the console log files that were generated during the past seven days. To view older log files, you must view them in the /usr/opt/ams/logs/cmf.dated directory within a terminal window.