AlphaServer GS80/160/320 System Management Console User's Guide Order Number: EK–GSCON–UG. A01 This manual provides information about using version 4.0 of the system management console for Compaq AlphaServer GS80/160/320 systems. This manual is for managers and operators of those systems.
First Printing, March 2002 © 2002 Compaq Computer Corporation. Compaq, the Compaq logo, Compaq Insight Manager, AlphaServer, StorageWorks, and TruCluster Registered in U.S. Patent and Trademark Office. OpenVMS, Tru64, and Carbon Copy are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. Acrobat is a trademark of Adobe Systems Incorporated. ConsoleWorks is a trademark of TECSys Development Incorporated. Java is a trademark of Sun Microsystems, Inc.
Japanese Notice Canadian Notice This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Avis Canadien Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. European Union Notice Products with the CE Marking comply with both the EMC Directive (89/336/EEC) and the Low Voltage Directive (73/23/EEC) issued by the Commission of the European Community.
Contents Preface ..................................................................................................................... xiii Chapter 1 1.1 1.2 1.3 1.4 1.5 1.6 System Management Console Overview ............................................... 1-2 Logging on to the SMC.......................................................................... 1-4 Using the SMC Locally ......................................................................... 1-6 Using the SMC Remotely ..........................
3.3.4 3.3.5 3.3.6 3.3.7 3.3.8 3.4 3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.4.6 3.5 3.5.1 3.5.2 3.5.3 3.5.4 3.5.5 3.5.6 3.6 3.6.1 3.6.2 3.6.3 Renaming a Console...................................................................... 3-36 Giving a Console an Alias ............................................................. 3-38 Adding a Console Group ............................................................... 3-40 Deleting a Console Group .............................................................
4.5.5 4.6 Advanced Soft Partitioning........................................................... 4-38 Managing CAPM Files ........................................................................ 4-40 Chapter 5 5.1 5.1.1 5.1.2 5.1.3 5.2 Setting Up the GCU.............................................................................. 5-2 Establish Access Control................................................................. 5-2 Create an Account for Each Galaxy Instance .................................
B.5 Contents of the MAIL.PL File...............................................................B-9 Appendix C SMC Hard Disk Appendix D ConsoleWorks Licenses Index Figures 1–1 1–2 1–3 1–4 1–5 2–1 2–2 2–3 2–4 2–5 2–6 2–7 2–8 2–9 2–10 2–11 2–12 2–13 2–14 3–1 3–2 3–3 3–4 3–5 3–6 3–7 3–8 3–9 viii System Management Console ............................................................... 1-2 Windows NT Security Window .............................................................
3–10 3–11 3–12 3–13 3–14 3–15 3–16 3–17 3–18 3–19 3–20 3–21 3–22 3–23 3–24 3–25 3–26 3–27 3–28 3–29 3–30 3–31 3–32 3–33 3–34 3–35 3–36 3–37 3–38 3–39 3–40 3–41 3–42 3–43 3–44 3–45 3–46 3–47 3–48 3–49 3–50 console_name Configuration Screen.................................................... 3-19 KEA! Connection Window................................................................... 3-20 Show Consoles Screen ......................................................................... 3-24 Security Warning ...
3–51 3–52 3–53 3–54 3–55 4–1 4–2 4–3 4–4 4–5 4–6 4–7 4–8 4–9 4–10 4–11 4–12 4–13 4–14 4–15 4–16 4–17 4–18 4–19 4–20 4–21 4–22 4–23 4–24 4–25 4–26 4–27 4–28 4–29 4–30 4–31 4–32 5–1 5–2 5–3 x profile_name Screen ............................................................................ 3-77 console_name Logfiles Screen ............................................................. 3-78 Log File Screen....................................................................................
5–4 6–1 6–2 6–3 6–4 6–5 6–6 6–7 6–8 6–9 6–10 6–11 6–12 6–13 6–14 6–15 eXcursion Icon....................................................................................... 5-8 Browser Window ................................................................................. 6-10 Ports Configuration Dialog Box .......................................................... 6-11 Configuration Dialog Box....................................................................
Preface Intended Audience This manual is for managers and operators of Compaq AlphaServer GS80/160/320 systems. Document Structure This manual uses a structured documentation design. Topics are organized into small sections, usually consisting of two facing pages. Most topics begin with an abstract that provides an overview of the section, followed by an illustration or example. The facing page contains descriptions, procedures, and syntax definitions.
• Appendix B, Compaq-Supplied Configuration Files for ConsoleWorks, contains in-depth information about the ConsoleWorks configuration files. • Appendix C, SMC Hard Disk, lists recommendations for use of the disk partitions and shows the directory structure. • Appendix D, ConsoleWorks Licenses, contains information about licensing requirements.
Information on the Internet Visit Compaq’s AlphaServer site at www.compaq.com/alphaserver/ site_index.html for more information about AlphaServer GS80/160/320 systems. See ftp.digital.com/pub/Digital/Alpha/firmware/interim/smc/smc.html for more information about the system management console.
Chapter 1 Getting Started with the System Management Console The system management console manages one or more GS80/160/320 systems. This manual is for V4.0 of the system management console.
1.1 System Management Console Overview The system management console makes it possible to operate one or more systems, some or all of which have multiple partitions, with a single console device.
With the system management console (SMC), one or more GS80/160/320 systems, each with a single or multiple console lines, can be managed from a single device. The SMC consists of a Compaq Deskpro PC, one or more DECserver 90M terminal servers, a network hub (if more than one GS80/160/320 system is managed by the SMC), and associated hardware and software. Figure 1–1 shows a typical setup. The eight-port terminal server can connect to a maximum of eight partitions.
1.2 Logging on to the SMC When logging on the first time, give the administrator account a password. Other accounts can be set up on the SMC system.
When the SMC system arrives, the administrator account has no password. You can give that account a password by following these instructions. 1. Press Ctrl+Alt+Del. The Windows NT Security window displays (Figure 1– 2). 2. Click Change Password… The Change Password dialog box displays (Figure 1–3). 3. Enter the old password (in this case, the leave the field blank) and the new one, and enter the new password again to confirm it. (The passwords display as asterisks.) Click OK.
1.3 Using the SMC Locally Icons on the SMC desktop are used to run applications locally. Figure 1–4 SMC Desktop The SMC desktop has several icons that enable you to run applications and view documentation online. Table 1–1 shows the icons and describes the result of double-clicking each.
Table 1–1 SMC Desktop Icons Icon Function Runs ConsoleWorks, the console management application used by the SMC. See Chapter 3 for a quick reference and the ConsoleWorks Administrator and User Guide for more in-depth information. NOTE: Since ConsoleWorks runs in the Internet Explorer browser, the first time you start it, the Internet Explorer Setup Wizard runs. You will need to supply connection information, including proxies if applicable.
1.4 Using the SMC Remotely The SMC Web page is used to run applications remotely.
To display the SMC Web page from a system that is networked to the SMC system, open a Web browser and enter the address http://name.domain:2301/smc/smc.htm, where name.domain is the fully qualified address or the IP address of the SMC system on the corporate network; press Enter. The supported browsers are Internet Explorer V5.0 or later and Netscape V4.7 or later.2 Browsers must have Java and JavaScript enabled.
1.5 Naming Convention An SMC system can support multiple GS80/160/320 systems. Each system has a maximum of eight consoles. The names given to systems and consoles, along with IP numbers, are shown here.
Table 1–3 System Names and IP Host Numbers System Name IP Host System Name IP Host ASGS1 90.0.0.1 ASGS17 90.0.0.33 ASGS2 90.0.0.3 ASGS18 90.0.0.35 ASGS3 90.0.0.5 ASGS19 90.0.0.37 ASGS4 90.0.0.7 ASGS20 90.0.0.39 ASGS5 90.0.0.9 ASGS21 90.0.0.41 ASGS6 90.0.0.11 ASGS22 90.0.0.43 ASGS7 90.0.0.13 ASGS23 90.0.0.45 ASGS8 90.0.0.15 ASGS24 90.0.0.47 ASGS9 90.0.0.17 ASGS25 90.0.0.49 ASGS10 90.0.0.19 ASGS26 90.0.0.51 ASGS11 90.0.0.21 ASGS27 90.0.0.53 ASGS12 90.0.0.
1.6 Keep in Mind Keep these points in mind when you use the system management console. • An SMC may be used with one or more GS80/160/320 systems only. The license does not permit it to be connected to other equipment. • The GS80/160/320 SCM and SRM may not have associated passwords. • The SCM escape sequence must be the default, scm. • The SMC system requires a static IP address. • In order for CAPM to run, ConsoleWorks services must be running.
Chapter 2 SMC Utilities The SMC expunge utility enables you to delete ConsoleWorks events and reduce the size of the default.config file outside of ConsoleWorks. Two other utilities back up and restore the SMC configuration.
2.1 Configuring Your Browser to Run SMC Utilities Set your browser to accept cookies, at least per-session. Figure 2–1 Internet Explorer Security Settings Internet Explorer 1. From the Tools menu select Internet Options… The Internet Options window opens. 2. Select the Security tab.
3. Click the Custom Level… button. The Security Settings window opens (Figure 2–1). 4. Scroll to Cookies and select Enable under Allow per-session cookies. 5. Click OK in the Security Settings window and the Internet Options window. Netscape Navigator 1. From the Edit menu select Preferences… The Preferences window opens. 2. Select Advanced. The Advanced options display (Figure 2–2). 3. Select Accept all cookies. Click OK.
2.2 Logging on to the SMC Utilities Page From the SMC Web page select SMC Utilities. Log on using your NT username and password.
Click the SMC Utilities icon on the SMC Web page. The SMC Utilities login page displays (Figure 2–4). Log in using the Windows NT username and password of a valid account on the SMC system.
Figure 2–5 SMC Utilities in Use 2-6 System Management Console User's Guide
If the SMC Utilities Page is already in use, the message shown in Figure 2–5 displays. You can wait for the current session to be logged off or to time out, or you can close all Internet Explorer windows, restart the Compaq SMC HMMO Server service (refer to Section 6.5), restart Internet Explorer, and select the SMC Utilities link. When the login is successful, the utility selection page displays (Figure 2–6). Select the utility you want to run, or log out from this page.
2.3 Expunging Events From the SMC Utilities selection Unacknowledged Events link.
Events can be expunged from within ConsoleWorks (see Section 3.4.6), but if too many unacknowledged events are allowed to build up, ConsoleWorks takes an excessive amount of time to start. If that happens, use this utility to expunge events. 1. Click the Expunge Unacknowledged Events link on the selection page (Figure 2–6). The expunge confirmation displays (Figure 2–7). 2. Click OK to continue. The progress of the utility displays (Figure 2–8). It is finished when the line Stop Expunge Process prints. 3.
2.4 Backing up the Configuration From the SMC Utilities selection page select Configuration Backup. Figure 2–9 Backup Confirmation Figure 2–10 Backup Progress The backup utility enables you to save the user settings of the SMC software. 1. Click the Configuration Backup link on the selection page (Figure 2–6). The backup confirmation displays (Figure 2–9).
2. Click OK to continue. The progress of the utility displays (Figure 2–10). It is finished when the line Stop Backup Process prints. 3. To see what has been backed up, click the link View backup details. The display is similar to Figure 2–11. Note that the entries under the lines Backup Carbon Copy Access and Backup KEA! indicate that no files are available to be copied. This is normal if a utility has not been used. Use the browser’s Back button to return to the previous page. 4.
2.5 Restoring the Configuration From the SMC Utilities selection page select Configuration Restore. Figure 2–12 Restore Confirmation Figure 2–13 Restore Progress The restore utility restores the configuration that was backed up in Section 2.4. The utility requires that configuration information be in d:\smcbackup. 1. If the folder d:\smcbackup is on a removable disk, copy it to the D drive.
2. Click the Configuration Restore link on the selection page (Figure 2–6). The restore confirmation displays (Figure 2–12). 3. Click OK to continue. The progress of the utility displays (Figure 2–13). It is finished when the line Stop Restore Process prints. 4. To see what has been restored, click the link View restore details. The display is similar to Figure 2–14. Note that the entries under the line Backup KEA! indicate that no files are available to be copied.
Chapter 3 ConsoleWorks ConsoleWorks is a Web-based application that enables communication with, and monitors and logs output from, the GS80/160/320 consoles. This chapter provides a quick reference for the procedures most commonly performed on a GS80/160/320 system management console (SMC). For more information about ConsoleWorks, see the ConsoleWorks Administration/User Guide. (You can open this manual from the SMC Documentation desktop folder on the SMC system or from the link on the SMC Web page.
3.1 Overview ConsoleWorks is a Web-based application that monitors console output and provides console management functions. Compaq provides a script that customizes ConsoleWorks for the system management console and GS80/160/320 environment. Figure 3–1 ConsoleWorks Application and Script C:\Cwks\import_pcm SCM.port 3 1 2 To Mail Server Console Works Event Detection SMTP Mail Notification GS80/160/320 5 Action Generation Perl Serial Ports Console Lines RUN "Prog"/Fixed Parameters Mail.
ConsoleWorks monitors console output for events, which are text strings in a console’s SCM or SRM output. Each event is part of one or more scans, or collection of events. A scan, in turn, is associated with one or more consoles. Compaq has customized the ConsoleWorks application used in the SMC to monitor for particular events and to send mail to user-specified recipients when those events occur.
3.1.1 Starting ConsoleWorks Start ConsoleWorks from the desktop icon or from the SMC Web page.
You can run ConsoleWorks from the SMC system or from a workstation networked to the SMC system. • To run ConsoleWorks from the SMC system, double-click the ConsoleWorks desktop icon: • To run ConsoleWorks from a workstation networked to the SMC system, click the icon on the SMC Web page (Figure 3–3). To display the SMC Web page, enter this in the browser Address box: http://name.domain:2301/smc/smc.htm, where name.
3.1.2 ConsoleWorks Screen The ConsoleWorks screen is divided into three sections: left navigation panel, main data panel, and lower navigation panel.
Figure 3–4 shows the screen that opens after you log in to ConsoleWorks. The three parts of the screen are described below. Left navigation panel – This panel lists menu links, and each menu link lists selection links: • Menu links (Operations, Reports, Change, Manage, Admin, Download, and Help). Clicking any of these links causes the display of a list of related selection links. • Selection links. This list changes depending on which menu link is chosen.
3.2 Communicating with a GS80/160/320 Console There are three methods for communicating with consoles. Table 3–1 Communication Methods Method Steps ConsoleWorks Telnet Listener utility In a Command Prompt (MS-DOS) window type: configure_telnet_listener m n telnet host_name port_number ConsoleWorks terminal emulator window Click the icon next to the console name on the Show Consoles screen. KEA! or other terminal emulator Follow the ConsoleWorks setup instructions in Section 3.2.
One of the primary functions of ConsoleWorks on the SMC is to enable communication with consoles on a GS80/160/320 system. You can communicate with a GS80/160/320 console via ConsoleWorks in three ways: • ConsoleWorks Telnet Listener utility • ConsoleWorks terminal emulator window • KEA! or other terminal emulator program The sections that follow give instructions for setting up and using each of these methods.
3.2.1 Using the ConsoleWorks Telnet Listener Utility In a Command Prompt window configure the telnet listener and start a telnet session.
1. Open a Command Prompt window by double-clicking the MSDOS Command desktop icon. 2. In the Command Prompt window enter the following (shown here in bold); press the Enter key at the end of each line: C:\> cd c:\cwks\bin C:\CWKS\Bin> configure_telnet_listener m n where m is the system number (1 to 32) of the GS80/160/320 system, and n is the number of consoles (1 to 8) you want to enable. Entering a number that is less than the number of consoles in the system enables the first n consoles.
Table 3–2 Telnet Listener Port Numbers Console Number System Number 1 2 3 4 5 6 7 8 1 5181 5182 5183 5184 5185 5186 5187 5188 2 5191 5192 5193 5194 5195 5196 5197 5198 3 5201 5202 5203 5204 5205 5206 5207 5208 4 5211 5212 5213 5214 5215 5216 5217 5218 5 5221 5222 5223 5224 5225 5226 5227 5228 6 5231 5232 5233 5234 5235 5236 5237 5238 7 5241 5242 5243 5244 5245 5246 5247 5248 8 5251 5252 5253 5254 5255 5256 5257 5258 9 5261 52
Table 3–2 Telnet Listener Port Numbers (Continued) Console Number System Number 1 2 3 4 5 6 7 8 24 5411 5412 5413 5414 5415 5416 5417 5418 25 5421 5422 5423 5424 5425 5426 5427 5428 26 5431 5432 5433 5434 5435 5436 5437 5438 27 5441 5442 5443 5444 5445 5446 5447 5448 28 5451 5452 5453 5454 5455 5456 5457 5458 29 5461 5462 5463 5464 5465 5466 5467 5468 30 5471 5472 5473 5474 5475 5476 5477 5478 31 5481 5482 5483 5484 5485 5486 548
3.2.2 Using a ConsoleWorks Terminal Emulator Window Click the icon next to the console name in the Show Consoles screen, or click the Connect link at the top of the console_name Configuration screen.
ConsoleWorks has a built-in terminal emulator function.
Table 3–3 ConsoleWorks Console Icons Icon 3-16 Name Meaning Connect The console has a read and write connection. Monitor The console is read only. Active connect The console has a read and write connection, and another user is connected to it. (The icon is shaded green.) Locked The console has been locked by another user. Sick dude The console has lost its connection. Information An information URL, defined in the console configuration screen, is associated with the console.
You can copy text from a ConsoleWorks terminal emulator window and paste it into another application. That this feature exists is not apparent, however, since the window has no Copy command. Do the following to copy and paste from a ConsoleWorks terminal emulator window: 1. Open the window you want to paste the text into, and click to place the cursor at the point where the text will be pasted. 2. In the ConsoleWorks terminal emulator window, click and drag over the text to be copied (Figure 3–8).
3.2.3 Using KEA! with ConsoleWorks Select Change|Connect Settings in the left navigation panel. Then select the option button labeled Use Java Telnet Proxy. Select Operations|Consoles in the left navigation panel, then select the console from the list. Use the desktop icon to open KEA! and create a new session.
A terminal emulator can be used with ConsoleWorks. Directions for using KEA! are given here because it is distributed with the SMC software, but another terminal emulator program may be used. 1. In the left navigation panel of ConsoleWorks select Change. From the selection links select Connect Settings. The Console Connection Settings screen opens (Figure 3–9). Select the Use Java Telnet Proxy option button. The change takes effect immediately. 2. In the left navigation panel select Operations.
Figure 3–11 KEA! Connection Window 3-20 System Management Console User's Guide
4. Double-click the KEA! desktop icon to open KEA!. In the connection wizard do the following: a. Select Serial. Click Next. b. Select Telnet. Click Next. c. Enter the host name or IP address (not the IP host number) of the GS80/160/320 system and the telnet port number of the console (Figure 3–11). See Table 3–4 for the telnet port number, which is at the intersection of the IP host and IP port numbers that you noted in step 3. Click Next. d. Select a terminal type. Click Next. e.
Table 3–4 Telnet Ports IP Port IP Host 2001 2002 2003 2004 2005 2006 2007 2008 90.0.0.1 5181 5182 5183 5184 5185 5186 5187 5188 90.0.0.3 5191 5192 5193 5194 5195 5196 5197 5198 90.0.0.5 5201 5202 5203 5204 5205 5206 5207 5208 90.0.0.7 5211 5212 5213 5214 5215 5216 5217 5218 90.0.0.9 5221 5222 5223 5224 5225 5226 5227 5228 90.0.0.11 5231 5232 5233 5234 5235 5236 5237 5238 90.0.0.13 5241 5242 5243 5244 5245 5246 5247 5248 90.0.0.
Table 3–4 Telnet Ports (Continued) IP Port IP Host 2001 2002 2003 2004 2005 2006 2007 2008 90.0.0.47 5411 5412 5413 5414 5415 5416 5417 5418 90.0.0.49 5421 5422 5423 5424 5425 5426 5427 5428 90.0.0.51 5431 5432 5433 5434 5435 5436 5437 5438 90.0.0.53 5441 5442 5443 5444 5445 5446 5447 5448 90.0.0.55 5451 5452 5453 5454 5455 5456 5457 5458 90.0.0.57 5461 5462 5463 5464 5465 5466 5467 5468 90.0.0.
3.3 Managing Consoles ConsoleWorks provides access to each console line in a GS80/160/320 system.
ConsoleWorks is used to manage the console lines in a GS80/160/320 system. To find information about a console line, start by clicking Operations, and then the Consoles link in the left navigation panel of any ConsoleWorks screen. This opens the Show Consoles screen (Figure 3–12). From there you can view a console line’s activity or its configuration, delete a console (Section 3.3.2) or add one (Section 3.3.3). NOTE: When you open a console, a security warning displays.
3.3.1 Loading Certificate Authority The Java applet used in ConsoleWorks warns of a potential security violation on the SMC PC. By loading the certificate authority, which is on the C drive with the application, you agree that content from TECSys Development, Inc. can be trusted.
When you open a console, a security warning displays (Figure 3–13). To prevent repeated display of this warning, load the TDI security certificate. 1. In the left navigation panel of any ConsoleWorks screen, select Download. 2. From the selection links at the bottom of the left navigation panel, select TDI Certificate. The File Download dialog box opens (Figure 3–14). 3. Select the option button labeled Open this file from its current location and click OK.
Figure 3–15 TDI Certificate 3-28 System Management Console User's Guide
4. The certificate displays (Figure 3–15). Click Install Certificate…. 5. The Certificate Manager Import Wizard opens. Follow the instructions in the wizard and accept the defaults. At the end click Finish. 6. The Root Certificate Store window opens (Figure 3–16). Click Yes. 7. The certificate displays again. Click OK.
3.3.2 Deleting a Console Select Operations|Consoles in the left navigation panel, then Delete Console at the top of the screen. Privileges required: Admin – R W C; Console – none Figure 3–17 Delete Console Screen NOTE: Be sure you want to delete the console, since you cannot undo this operation. If you accidentally delete a console, use the Add Console function (Section 3.3.3) to reconfigure it.
When a physical console line (between a standard I/O module and the terminal server) is removed, do the following to remove it from the software configuration: 1. Remove the console from the system group (see Section 3.3.8). 2. In the left navigation panel select Operations. From the selection links select Consoles. The Show Consoles screen opens. 3. At the top of the Show Consoles screen select Delete Console. The Delete Console screen opens (Figure 3–17). 4.
3.3.3 Adding a Console Select Operations|Consoles in the left navigation panel, then Add Console at the top of the screen. The type is telnet.
1. In the left navigation panel select Operations. From the selection links select Consoles. The Show Consoles screen opens. NOTE: The maximum number of consoles that can exist on an SMC is set by the ConsoleWorks license. If the Show Consoles screen lists the maximum number of consoles (not including the ConsoleWorks internal console, CONWRKS), do not attempt to add another. Instead, you must delete a console before adding one or add a license for more consoles. (See Appendix D for license information.) 2.
Figure 3–20 3-34 console_name Configuration Screen System Management Console User's Guide
5. Click the Add Console button. The console_name Configuration screen opens (Figure 3–20). 6. If you want ConsoleWorks to automatically delete events, enter a number from 1 to 999 in the AutoPurge Events block. The number corresponds to the number of days before events are purged. Enter 0 to prevent ConsoleWorks from deleting events. 7. Enter the profile access information at the bottom of the main data panel. Click the Update button. 8. At the top of the screen select Connect.
3.3.4 Renaming a Console ConsoleWorks does not allow direct renaming of a console. To change a name, delete the console and add a new one with the preferred name.
The SMC is configured with the number of consoles chosen at installation. Since ConsoleWorks does not allow direct renaming of a console, to change a name, you must delete the console and add a new one with the name you choose. NOTE: If the Show Consoles screen lists the maximum number of consoles permitted by the ConsoleWorks license (not including the ConsoleWorks internal console, CONWRKS), be sure to delete the console before adding a new one. 1. Determine the console’s properties. a.
3.3.5 Giving a Console an Alias Enter the alias in the Alias block on the console_name Configuration screen and click the Update Console button.
An easier way to give a console a different name than renaming it (Section 3.3.4) is to give it an alias. The alias displays in ConsoleWorks and CAPM wherever the console’s name would be used. To give a console an alias, enter it in the Alias block on the console_name Configuration screen (Figure 3–22) and click the Update Console button.
3.3.6 Adding a Console Group Select Manage|Groups from the left navigation panel, then Add Group from the top of the screen. All consoles in a system must be in the same group before the system can be partitioned. Privileges required: Admin – R W; Console – none Figure 3–23 Add Group Screen All consoles in a system are configured into a group when the system is installed. Each system's consoles constitute one group. The user can create other groups so that consoles are in a meaningful organization.
2. At the top of the Show Groups screen select Add Group. The Add Group screen opens (Figure 3–23). 3. Enter a name in the Group Name box. The name is limited to 31 characters. 4. Optionally, enter a description. 5. Click the Add Group button. The Group group_name screen opens (Figure 3–24). 6. Add a console to the group by selecting the checkbox next to the console's name. Remove a console by toggling the console's checkbox. 7.
3.3.7 Deleting a Console Group Select Manage|Groups from the left navigation panel, then Delete Group from the top of the screen.
1. In the left navigation panel select Manage. From the selection links select Groups. The Show Groups screen opens. 2. At the top of the screen select Delete Group. The Delete Group screen opens (Figure 3–25). 3. In the pulldown list select the group to delete. Click the Delete Group button. 4. An acknowledge box opens. Click OK to confirm that the group should be deleted.
3.3.8 Removing a Console from or Adding One to an Existing Group Select Manage|Groups from the left navigation panel, then the link for the group.
Removing a Console from a Group 1. In the left navigation panel select Manage. From the selection links select Groups. The Show Groups screen opens. 2. Select the link for the group. The Group group_name screen opens (Figure 3–26). 3. In the Included Consoles list, click the checkbox for the console to clear the box. (In Figure 3–26, ASGS1_CONSOLE7 is being removed.) Click the Update Group button. Adding a Console to an Existing Group 1. Create the console if it does not exist. See Section 3.3.3. 2.
3.4 Managing Events and Actions An event is a text string in the input or output of a console’s SCM, SRM, or operating system instance for which ConsoleWorks monitors. Based on the event, ConsoleWorks can trigger an action. Each event is associated with one or more scans, or collection of events. A scan, in turn, is associated with one or more consoles.
An event is a text string in the input or output of a serial port for which ConsoleWorks tests. The string can be to or from the SCM, SRM, or operating system. A number of events are supplied by ConsoleWorks and by Compaq; the user can create others (Section 3.4.3). Compaq supplies a number of events that are specific to the GS80/160/320 system (Section 3.4.1). An event can trigger an action.
3.4.1 Importing and Using Compaq-Supplied Events The Compaq-supplied events and script send mail to a designated individual if any of seven conditions occurs in the GS80/160/320 system. Some configuration is required to enable these actions.
To use the Compaq-supplied events, do the following: 1. The ConsoleWorks script (c:\cwks\default\actions\event\mail.pl) should have been been modified at installation to include the name of your mail server. If it was not, or if you want to change it, do so now by opening the file Mail.pl in Notepad and following the instructions under the heading “WARNING!!!”. 2. Follow the instructions in Section 3.4.2 to enable MAIL.BAT on all consoles for each of the seven events that begins with the string “GS–”.
Figure 3–29 Services Dialog Box 3-50 System Management Console User's Guide
This is the second procedure for importing Compaq-supplied events. 1. Stop the ConsoleWorks services: a. Open the Control Panel. From the Start button select Settings|Control Panel. b. In the Control Panel double-click the Services icon. The Services dialog box opens (Figure 3–29). c. Click to highlight the ConsoleWorks LMF Server service and click the Stop button. This also stops the ConsoleWorks Server service. 2. Open a Command Prompt window by double-clicking the MSDOS Command desktop icon. 3.
3.4.2 Enabling an Action Each event can have a number of associated actions.
1. In the left navigation panel select Manage. From the selection links select Events. The Show Events screen opens. 2. Select the event link from the list. The Event event_name screen opens (Figure 3–30). 3. Select the Automatic Actions link (above the Pattern box). The Event event_name Actions screen opens (Figure 3–31). 4. Enable or disable event throttling. If throttling is enabled, the event triggers the action once, but does not activate it again until the event is acknowledged.
Figure 3–32 Mail from ConsoleWorks 3-54 System Management Console User's Guide
6. Click the checkbox(es) of the action or actions that you want to have triggered by the event. Four items are listed; they represent the four files in the folder C:\Cwks\Actions\Event. Three of them represent valid actions: • AUTOCANCEL.BAT – Acknowledge an event immediately after it occurs and, optionally, purge it. • BROADCAST.BAT – Broadcast a message to the indicated contact. • MAIL.BAT – Send mail to the indicated contact. The fourth item, MAIL.PL, is used by MAIL.BAT.
3.4.3 Adding an Event Select Manage|Events in the left navigation panel, then Add Event at the top of the screen.
1. In the left navigation panel select Manage. From the selection links select Events. The Show Event screen opens. 2. At the top of the Show Event screen select Add Event. The Add Event screen opens (Figure 3–33). 3. Enter the information for the event: a. Event – Name of the event, limited to 61 characters. The name specified in this field is used in the list on the Show Event screen. b. Description – Description of the event, maximum 127 characters. c.
3.4.4 Adding a Scan Select Manage|Scans in the left navigation panel, then Add Scan at the top of the screen. Privileges required: Admin – R W C; Console – none Figure 3–34 Add Scan Screen 1. In the left navigation panel select Manage. From the selection links select Scans. The Show Scans screen opens. 2. At the top of the Show Scan screen select Add Scan. The Add Scan screen opens (Figure 3–34).
3. Enter the information for the scan: a. Scan – Name of the scan, limited to 30 characters. b. Description – Description of the event, maximum 126 characters. 4. Click the Add Scan button. The Scan scan_name screen opens. 5. At the top of the screen select Events. A list of events displays; all are shown as excluded. 6. In the Excluded Events column select the events to include in this scan. Click the Update Scan button.
3.4.5 Acknowledging and Purging Events Click Events Detail. Select individual events or the Select All link. Click Acknowledge Selected Events, then Purge Acknowledged Events.
1. Display the events. You can display the events for one console only or for all consoles. • One console: From the left navigation panel select Operations. From the selection links select Consoles. The Show Consoles screen opens. Select the console for which you want to acknowledge events from the list. The console_name Configuration screen opens. At the top of the screen select the Events link. The console_name Events screen opens. • All consoles: From the lower navigation panel select Events Detail.
3.4.6 Expunging Events Expunging acknowledges and deletes all events of a specified priority and lower from a console. Select Admin|Expunge. Select the console or consoles from which events are to be deleted and click Expunge Events.
Expunging acknowledges and deletes all events of a specified priority and lower from a console in one operation. 1. In the left navigation panel select Admin. From the selection links select Expunge. The Expunge Events screen opens (Figure 3–37). 2. In the box labeled Priorities equal to or lower than, select the highest priority of events to delete. 3. Click the checkbox of each console for which events will be deleted. 4. Click the Expunge Events button. 5.
3.5 Managing Users The SMC system administrator determines the consoles to which a user has access and the level of that access. The level of access is controlled by a profile; each user is associated with one or more profiles.
Users gain access to consoles through profiles. A profile specifies the privileges granted to any user who is listed in its Users Granted table. Each user has access to one or more profiles but can use only one profile at a time. Profiles specify two types of privileges: Console and Admin (administrative). Console and Admin privileges are independent. Console privileges are for managing consoles. These privileges identify the level of interaction a user can have with a console and are hierarchical.
3.5.1 Adding a User Select Manage|Users in the left panel, then Add User at the screen top. Privileges required: Admin – R W C; Console – none Figure 3–40 Add User Screen 1. In the left navigation panel select Manage. From the selection links select Users. The Show Users screen opens. 2. At the top of the Show Users screen select Add User. The Add User screen opens (Figure 3–40). 3. Enter the information for the user: a. Username – Must be unique.
b. Description – For information only; not used elsewhere in ConsoleWorks. c. Password – Must be at least six characters long. d. Verify – Enter the password again. Verify must match Password. 4. Click the Add User button. The user_name screen opens (Figure 3–41). 5. Enter the user contact information and select the profile for this user. NOTE: If you select more than one profile, the user is logged in with the one that has the least administrative privilege.
3.5.2 Communicating with Another User To send a message, select Operations|Send Message in the left navigation panel. To read messages, click the mailbox icon in the bottom panel. Privileges required: Admin – none; Console – none Figure 3–42 Send a User Message Screen Sending a Message 1. In the left navigation panel select Operations. From the selection links select Send Message. The Send a User Message screen opens (Figure 3–42). 2. Select the recipient from the Select User dropdown menu.
3. Enter the message in the Message text box. The maximum length is 255 characters. 4. Enter the timeout period in the Expires text box and select the units in the dropdown menu to the right of the text box. The default is 1 hour, the minimum 1 minute, and the maximum 9999 days. The message is deleted if the recipient does not read it before the timeout period expires. Reading Messages Message status is indicated by the icon in the lower left corner of the lower navigation panel.
3.5.3 Changing a User Password Select Change|Password in the left navigation panel. Privileges required: Admin – R W C (none for user’s own) ; Console – none Figure 3–44 Change Password Screen 1. In the left navigation panel select Change. From the selection links select Password. The Change Password screen opens (Figure 3–44). 2. From the Change Password dropdown list select the user whose password is to change.
3. Enter the information for the password: a. Password – The new password; six characters or longer. b. Verify – Retype the new password. 4. Click the Change Password button. The Password Change screen (Figure 3– 45) opens, confirming the change. NOTE: If the password is changed for an account in use, that user’s session ends, and the user must log in with the new password. Administrative privileges Read, Write, and Control are required to change another user’s password.
3.5.4 Resetting the console_manager Password Stop the ConsoleWorks services, run C:\ Cwks\bin\consoleworks_ reset_ password.exe, and restart the services.
If you forget the password for the console_manager account, you will not be able to perform administrative tasks such as purging or expunging events, creating new users, or adding or deleting consoles. Follow this procedure to reset the password. 1. Stop the ConsoleWorks services: a. From the Start button select Settings|Control Panel. The Control Panel box opens. b. Double-click the Services icon. The Services box opens (Figure 3–46). c. Scroll down to ConsoleWorks LMF Server.
3.5.5 Adding a Profile Select Manage|Profiles in the left navigation panel, then Add Profile at the top of the screen.
1. In the left navigation panel select Manage. From the selection links select Profiles. The Show Profiles screen opens. 2. At the top of the Show Profiles screen select Add Profile. The Add Profile screen opens (Figure 3–48). 3. Enter the information for the profile: a. Profile Name – Can be no longer than 30 characters. b. Description – Maximum 62 characters. 4. Click the Add Profile button. The profile_name screen opens (Figure 3–49). 5. Select privileges for users who have this profile. 6.
3.5.6 Modifying a Profile Select Manage|Profiles in the left navigation panel.
1. In the left navigation panel select Manage. From the selection links select Profiles. The Show Profiles screen opens (Figure 3–50). 2. Select the profile to modify from the list. The profile_name screen opens (Figure 3–51). 3. Make the changes to the profile. Click the Update Profile button.
3.6 Managing ConsoleWorks Log Files ConsoleWorks creates log files for each console. These logs are text files that can be viewed or deleted through ConsoleWorks or by accessing them in the directory.
ConsoleWorks creates a new log file for each console every day at midnight. These log files are on the SMC hard drive in the directory D:\cwks\log. The naming convention is console_name.LOG_yyyy_mm_dd. A console log shows all activity on the console for the specified day. The log for CONWRKS shows activity and events from all consoles on the specified day. Log files can quickly fill the disk if they are not managed. For that reason, it is a good idea to archive or delete these files often.
3.6.1 Viewing a Log File Select Operations|Consoles in the left navigation panel. Then select the console from the list. At the top of the screen select the Logs link and the log to view from the list.
1. From the left navigation panel select Operations. From the selection links select Consoles. The Show Consoles screen opens. 2. Select the console from the list. The console_name Configuration screen opens. 3. At the top of the screen select Logs. The console_name Logfiles screen opens (Figure 3–52). 4. Select the log file from the list. The file displays (Figure 3–53).
3.6.2 Deleting Log Files Select Operations|Consoles in the left navigation panel. Then select the console from the list. At the top of the screen select the Logs link.
1. From the left navigation panel select Operations. From the selection links select Consoles. The Show Consoles screen opens. 2. Select the console from the list. The console_name Configuration screen opens. 3. At the top of the screen select Logs. The console_name Logfiles screen opens (Figure 3–54). 4. Click the checkboxes of the log files to delete and click the Delete button.
3.6.3 Mailing a Log File Start Outlook Express, then include the log file as an attachment.
1. Double-click the Outlook Express icon on the SMC desktop. The Outlook Express Window opens. 2. From the Compose menu select New Message. The New Message window opens (Figure 3–55). 3. Enter recipients' names or addresses and the subject. The title bar text changes to the subject. 4. To include the log file as an attachment, from the Insert menu select File Attachment… or click the button with the paperclip icon. Select Browse… and switch to the D drive, cwks\log folder (D:\cwks\log) for a list of files.
Chapter 4 Compaq AlphaServer Partition Manager The Compaq AlphaServer Partition Manager (CAPM) simplifies creation of partitions.
4.1 Starting CAPM Start CAPM from the SMC desktop icon or from the SMC Web page.
You can run CAPM directly from the desktop icon on the SMC or from the SMC Web page. • To run CAPM from the SMC system, double-click the CAPM desktop icon: • To run CAPM from a workstation networked to the SMC system, click the icon on the SMC Web page (Figure 4–1). To display the SMC Web page on a system running Windows, enter this in the browser Address box: http://name.domain:2301/smc/smc.htm, where name.
Figure 4–2 Error Selecting System 4-4 System Management Console User's Guide
Before You Begin The following conditions must be observed when running CAPM: • An instance of CAPM can partition only one system. To partition more than one system, you must start additional instances. • CAPM partitions consist only of consoles that are assigned to ConsoleWorks groups. Before running CAPM the first time, or if any changes are made to the hardware, run the Console Group Validator utility (see Chapter 11 of the System Management Console Installation Guide).
4.2 Overview of CAPM CAPM enables the user to partition a GS80/160/320 system without using console commands. Figure 4–3 Login Box Compaq AlphaServer Partition Manager (CAPM) is a graphical application 1 that simplifies the creation and management of partitions on a GS80/160/320 system. CAPM runs on the SMC and, through a wizard-like series of screens, enables you to work with partitions without having to know anything about the console commands involved.
After the username and password are validated, CAPM displays a window requesting the user to select the system to partition (Figure 4–4). CAPM then connects to the selected GS80/160/320 system and discovers its configuration. (If conflicting connections or locks exist in ConsoleWorks to this system, CAPM displays an error dialog showing the conflicts.
4.3 Partition Maps The partition map provides partitioning information about the GS80/160/320 system.
Figure 4–5 shows the Current Partition Map screen with the Partition Map option button selected. This selection provides partition information about the GS80/160/320 system in the form of a table. (See page 4-10 for the screen with the System Information button selected.) The parts of the display are described here. Partition – A number from 1 to the number of quad building blocks (QBB) in the system (maximum 8).
Figure 4–6 System Information Figure 4–6 shows the Current Partition Map screen with the System Information option button selected. This selection provides QBB information about the GS80/160/320 system. QBB – The hard QBB number. There is one line in the partition map for each QBB.
OS Status – Running if an operating system is running in this partition; Not Running if the SRM firmware is running; Powered Off if the partition is powered off; Faulted if there is a fault. CPUs – The number of CPUs found by CAPM in the QBB during the discovery process. This includes failed and powered-off CPUs. Mem (MB) – The amount of memory (in megabytes) found by CAPM in the QBB during the discovery process. I/O? – Yes if CAPM detects a PCI box attached to the QBB; otherwise No.
4.4 Working With Hard Partitions Hard partitions do not share resources. CAPM can create, add, and delete hard partitions and modify, save, validate, and commit partition maps.
After you select a system, the first screen that displays is the Current Partition Map (Figure 4–8), which shows hard partition information. Section 4.3 describes the information that is displayed in a partition map. The GS80/160/320 system can have two types of partitions, hard and soft. In this section we look at hard partitions; Section 4.5 discusses soft partitions. Hard partitions do not share any CPU, memory, or I/O resources. In other words, the boundaries of these partitions are hard.
4.4.
1. From the Current Partition Map screen (Figure 4–8), click Next. The Work with Partition Maps screen displays (Figure 4–9). 2. Select the option button labeled Create a new partition map. 3. Enter a number in the box labeled Number of partitions. Click Next. If the GS80/160/320 system does not have sufficient resources to create the number of partitions specified, a message displays indicating that the system has insufficient resources.
Figure 4–10 Create or Modify a Partition Map 4-16 System Management Console User's Guide
4. The Create or Modify a Partition Map screen displays (Figure 4–10). This screen includes a suggested partition map created by CAPM based on the number of partitions you selected in the Work with Partition Maps screen. As much as possible, CAPM balances the system resources (existing and potential CPU and memory modules) among the partitions. Optionally, you can name the partition map by typing the name in the block labeled Partition Map. This is not the same as saving the map to a file. (See Section 4.4.
4.4.2 Adding a Hard Partition Figure 4–11 Add or Modify Hard Partition Screen 1. From the Current Partition Map screen (Figure 4–8) click Next. The Work with Partition Maps screen displays (Figure 4–9). 2. Select the option button labeled Modify the current partition map. The Create or Modify Partition Map screen displays (Figure 4–10). 3. Click Add. The Add or Modify Hard Partition screen displays (Figure 4–11). The number of the hard partition is shown in the title bar. 4.
6. Repeat steps 3 through 5 to add other partitions. As QBBs are added, the message below the Total block indicates if the hardware requirements of a partition have been met. Each partition must have at least one CPU, 64 Mbytes of memory, and an I/O riser module that is connected to a master PCI box with a standard I/O module. The partition shown in Figure 4–11 does not yet have a connection to a PCI box with a standard I/O module. In Figure 4–12 this is resolved by adding QBB 7 to the partition.
4.4.3 Deleting a Hard Partition Figure 4–13 Create or Modify a Partition Map Screen 1. From the Current Partition Map screen (Figure 4–8) click Next. The Work with Partition Maps screen displays (Figure 4–9). 2. Select the option button labeled Modify the current partition map. The Create or Modify a Partition Map screen displays (Figure 4–13). 3. Click to highlight the partition to be deleted, and click the Delete button.
4. A confirmation message displays (Figure 4–14). Click Yes to delete the partition or No to keep the partition. When a hard partition is deleted, all of its resources are returned to Unassigned, indicating that the hardware is not part of any partition.
4.4.4 Modifying a Partition Map Figure 4–15 Work with Partition Maps Screen 1. From the Current Partition Map screen (Figure 4–8) click Next. The Work with Partition Maps screen displays (Figure 4–15). 2. Select the option button labeled Modify the current partition map. Click Next. The Create or Modify a Partition Map screen displays (Figure 4–13).
3. Click to highlight the partition2 to be modified, and click the Modify button. The Add or Modify Hard Partition screen displays (Figure 4–16). 4. Do one of the following: • Select a QBB in the block labeled Available system resources to add it to the partition specified in the title bar; click Add, or • Select a QBB in the block labeled Resources assigned to this partition to remove it from the partition; click Remove. The partition information for the QBB changes to Unassigned. 5.
4.4.5 Saving, Validating, and Committing a Partition Map Figure 4–17 Saving a Partition Map Figure 4–18 Validating a Partition Map Saving a Partition Map 1. In the Create or Modify a Partition Map screen click the Save As… button. An information box displays (Figure 4–17). 2. Supply a file name and, optionally, change the location to which the file is saved. Click Save. A message confirms that the file was saved successfully.
The default file extension is .PMF (partition management file). The default (and recommended) location is c:\smc\capm\maps. When CAPM is launched from the SMC Web page, c:\smc\capm\maps is the only location available for saving or loading a partition management file. Validating a Partition Map To have CAPM evaluate a partition map and determine if it is valid, in the Create or Modify a Partition Map screen click the Validate button.
4.4.
1. In the Current Partition Map screen click Next. The Work with Partition Maps screen displays (Figure 4–20). 2. Select the option button labeled Load and modify an existing partition map. Enter the file name of a partition map that has been saved to a file (see Section 4.4.5) in the Partition Map box, or click the Browse button to find the file. The default file extension is .PMF.
4.5 Working With Soft Partitions Soft partitions can share memory, and CPUs can be moved among them. CAPM can create soft partitions by two methods.
Soft partitions are implemented within the boundaries of a hard partition. A portion of memory can be defined so it is shared among all the soft partitions in the hard partition. In addition, CPUs can be reassigned to other soft partitions. Because of this sharing of resources, the boundaries of these partitions are considered soft.
4.5.
1. In the Add or Modify Hard Partition screen (Figure 4–21), select the option button labeled Basic soft partitioning and click the Soft Partitions… button. 2. An informational message displays (Figure 4–22), indicating which QBB has the console for the hard partition. This QBB must be assigned to the first soft partition. Click OK. 3.
4.5.
1. In the Basic Soft Partition screen (Figure 4–23), click the Add… button. The Add or Modify Soft Partition screen displays (Figure 4–24). If this is the first soft partition in the hard partition, the QBB that contains the hard partition's console is listed in the block labeled Resources assigned to this partition. This QBB must be in the first soft partition; CAPM will not allow you to remove it. 2.
4.5.
1. In the Basic Soft Partition screen (Figure 4–25), click to select the partition you want to modify and click the Modify… button. The Add or Modify Soft Partition screen displays (Figure 4–26). 2. Do one of the following in the Add or Modify Soft Partition screen: • Add another QBB to this soft partition by clicking on a QBB in the box labeled Hard partition resources and clicking the Add button. Continue doing this until you have added all the QBBs that belong in this soft partition.
4.5.
1. In the Basic Soft Partition screen (Figure 4–27), click to select the partition you want to delete and click the Delete… button. 2. A message displays, asking for confirmation of the action (Figure 4–28). Click the appropriate button. 3. The Basic Soft Partition screen updates if you chose to delete the partition. (See Figure 4–29.) Click OK.
4.5.5 Advanced Soft Partitioning Figure 4–30 Advanced Soft Partition Screen CAUTION: Advanced Soft Partitioning is intended for users who are familiar with AlphaServer SRM environment variables. CAPM does not validate any information entered in these screens. Advanced Soft Partitioning gives the user more precise control than the Basic Soft Partition process. It requires knowledge of AlphaServer SRM environment variables. 1.
For descriptions of the AlphaServer SRM environment variables used to create soft partitions, and examples of using them, see the manual AlphaServer GS80/160/320 Getting Started with Paritions.
4.6 Managing CAPM Files CAPM creates log files and partition map files.
The CAPM log file contains a record of the transaction information and any errors that occur as the application runs. An excerpt from a CAPM log file is shown in Figure 4–32. The file is saved to the folder D:\capm\logs. CAPM creates a new log file for every session. A session starts when the user presses OK on the login window and ends when the user quits CAPM. The naming convention for log files is capmlog-yyyy.mm.dd-s.
Chapter 5 Graphical Configuration Utility The Graphical Configuration Utility (GCU) is an OpenVMS Galaxy utility for creating and maintaining partitions.
5.1 Setting Up the GCU Define information for the Galaxy instances in the eXcursion Control Panel. 5.1.
1. From the Start menu select Programs|eXcursion V7|eXcursion Control Panel. The eXcursion Control Panel window opens with the Info tab displayed. 2. Select the Access tab (Figure 5–1). 3. In the Access tab select the Enable Access Control checkbox, enter the Node Name, and click the Add button. Click Apply.
5.1.
1. In the eXcursion Control Panel window select the Accounts tab (Figure 5–2). 2. Enter the Account Alias, Host name, Username, and Password. Click the Add button. 3. Repeat step 2 for each instance.
5.1.
1. In the eXcursion Control Panel window select the Applications tab (Figure 5–3). 2. Enter an alias in the Application Alias box. 3. In the Command box enter $mcr gcu. 4. Select an Account Alias from the dropdown list. 5. Click the Add button. 6. Repeat steps 2 through 5 for each instance. 7. When an application has been defined for each instance, click OK.
5.2 Using the GCU From the eXcursion icon select Applications and the Galaxy instance.
1. Right-click on the eXcursion icon in the task bar. 2. Select Applications and the name of the Galaxy instance. The Graphical Configuration Utility window displays. See the OpenVMS Alpha Galaxy Guide for information on managing Galaxy partitions. This manual is available in HTML and PDF formats on the Web. Go to the URL http://www.openvms.compaq.com:8000/ and click the link OpenVMS Operating System. Scroll down the list to OpenVMS Alpha Galaxy Guide.
Chapter 6 Troubleshooting This chapter contains troubleshooting tips for the system management console hardware and software.
6.1 Troubleshooting Chart Table 6–1 lists a number of potential symptoms along with their possible causes and suggested solutions. Table 6–1 Troubleshooting Chart Symptom Possible Cause Suggested Solution File default.config has become too large. Run the Expunge utility. (Section 2.3) Terminal server is not powered. Connect the terminal server to the power source (see Section A.4 or B.4 of the System Management Console Installation Guide). Terminal server software has not been configured.
Table 6–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution Communications (continued) No prompt in a terminal window. Position identifier dial is set incorrectly. Set the position identifier dial on the terminal server to management agent (see Section A.3 or B.3 of the Installation Guide). The SMC system and the terminal server are connected by the wrong cable. Change the cable to a BN24Q. Terminal server is hung.
Table 6–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution Communications (continued) Text is garbled when UNIX is booting. Partition’s baud rate was set to 9600 by UNIX; terminal server’s or SMC’s baud rate is not 9600. Set terminal server’s or SMC’s baud rate to 9600 (Sections 6.2 and 6.3). ConsoleWorks has unused consoles. Delete consoles that will never be used (Section 3.3.2). A large number of events has accrued. Acknowledge and purge (Section 3.4.
Table 6–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution ConsoleWorks (continued) The SMC system has hung. (The pointer does not move when the mouse moves, or windows cannot be selected.) Reboot the SMC system. ConsoleWorks services are not running. Start ConsoleWorks services (Section 6.5). Default.config file might be corrupted. Stop the ConsoleWorks services (Section 6.5); rename the file c:\Cwks\Default\Config\ default.config; restart the ConsoleWorks services.
Table 6–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution A newly added GS80/160/320 system is not recognized by CAPM. The console group has not been validated. Run the Console Group Validator utility (see Chapter 11 of the Installation Guide). CAPM does not start. ConsoleWorks services are not running. Start ConsoleWorks services (Section 6.5). CAPM service is not running. Start the CAPM service in the same way as the ConsoleWorks services (Section 6.5).
Table 6–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution The consoles in the system are not part of a group. Create a group consisting of the consoles in the system (see Section 3.3.6). The Console Group Validator utility has not been run. Run CG Validator (see Chapter 11 of the Installation Guide). CAPM (continued) CAPM no longer recognizes a system. Console Group Validator Utility CG Validator does not show a system. The consoles in the system are not part of a group.
Table 6–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution HMMO service is not running on the SMC system. Start the service in the same way as the ConsoleWorks services (Section 6.5). The service name is Compaq SMC HMMO Server. You must have the Java 2 Runtime Environment, Standard Edition running on the system on which you are working. Go to the URL http://java.sun.com/j2se/1.3/jre to download it. The Java 2 plug-in for Tru64 UNIX can be found at http://www.compaq.com/java.
Table 6–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution Restart after Power Fail The SMC system does not automatically restart after a power failure. The system has not been configured to restart automatically. Depending on the model, change a switch setting or a BIOS setting (Section 6.6). Tru64 UNIX misinterprets the Enter key. Set up a hot key in the ConsoleWorks terminal emulator window (Section 6.8).
6.2 Changing Baud Rates: System with Multiple Console Lines Change the terminal server port’s baud rate to match the GS80/160/320 partition’s rate and establish communication. Then change the partition baud rate to 9600, and finally change the terminal server rate to 9600. 6.2.
1. Open Access Server Manager (ASM). From the Start menu select Programs|Access Server Manager|Access Server Manager. A Browser window displays (Figure 6–1). 2. In the Browser window select the item with IP address 90.0.0.1. Click Open. The Access Server window displays. 3. Select the Configuration tab. In the box, select Ports. Click the Configure… button. The Ports Configuration dialog box displays (Figure 6–2).
Figure 6–3 Configuration Dialog Box 6-12 System Management Console User's Guide
4. Select the port for which you will change the baud rate and click the Configure… button. The Configuration dialog box displays (Figure 6–3). 5. Click the Properties button. The Connection Service Configuration dialog box displays (Figure 6–4). 6. Change the port speed in this box, and check that the other settings are correct for your environment. Click OK.
6.2.
1. In the left navigation panel of a ConsoleWorks window, select Consoles. The Show Consoles screen displays. 2. Find the name of the console that is attached to the port you worked with in Section 6.2.1. Click the icon to the left of the name. A terminal emulator window for the console displays. 3. In the terminal emulator window press Enter. If the SCM or SRM console prompt displays, the baud rate of the terminal server port matches that of the GS80/160/320 partition.
6.3 Changing Baud Rates: System with Single Console Line Change the baud rate of the system’s COM1 port to match the GS80/160/320 system and establish communication. Then change the system rate to 9600, and finally change the COM1 rate to 9600. 6.3.
1. From the Start button select Settings|Control Panel. 2. In the control panel, double click the Ports icon. The Ports dialog box displays (Figure 6–6). 3. Select COM1 and click the Settings… button. The Settings for COM1 dialog box displays (Figure 6–7). 4. Change the baud rate, and check that the other settings are correct for your environment. Click OK.
6.3.
1. In the left navigation panel of a ConsoleWorks window, select Consoles. The Show Consoles screen displays (Figure 6–8). 2. Click the icon to the left of the ASGS1_CONSOLE1 link. A terminal emulator window for the console displays. 3. In the terminal emulator window press Enter. If an SRM console prompt displays, the baud rates match, and you can set the GS80/160/320 baud rate (step 4). If a prompt does not display, return to Section 6.3.1 and set the COM1 speed to a different setting. 4.
6.4 Changing the Internet Explorer Proxy Setting From the Internet Explorer Tools menu select Internet Options. Select the Connections tab and LAN Settings.
1. Ask the network administrator if settings are configured automatically or if proxy server information must be entered. 2. From the Tools menu select Internet Options… The Internet Options dialog box displays. 3. Select the Connections tab. Near the bottom click the LAN Settings… button. The Local Area Network (LAN) Settings dialog box displays. 4.
6.5 Starting the ConsoleWorks Services Open the Control Panel and double-click the Services icon. Select the ConsoleWorks services and click Start.
1. Open the Control Panel. From the Start button select Settings|Control Panel. 2. In the Control Panel double-click the Services icon. The Services dialog box displays (Figure 6–11). 3. Check the Status and Startup columns for the two ConsoleWorks services. If one or both do not look like the illustration, do the following: a. To change the status: Select a service and click Start. Repeat with the other service. b. To change the startup type: Select a service and click Startup….
6.6 Configuring the SMC System to Restart After a Power Failure The SMC system should power up and boot following a power failure. If it does not, corrective action is necessary. The action to take depends on the system model.
Location of Model Type Information The instructions below differ according to model. You can determine the model of the SMC system by looking at the label on the top or side of the minitower or desktop box. Models DPENM and DPEND 1. Shut down the SMC system and disconnect the power cord. 2. Remove the cover from the SMC box. 3. Locate the switchpack on the motherboard. Figure 6–13 and the label inside the SMC cover show the location of the switchpack. 4. Set switch 6 to On (Figure 6–13). 5.
6.7 Setting the Path Variable Open the Control Panel and double-click the System icon. In the Environment tab select Path and add the path to the Java Runtime Environment in the Value box.
1. From the Start menu, select Settings | Control Panel. Double-click the System icon. The System Properties dialog box displays. 2. Select the Environment tab (Figure 6–14). 3. In the System Variables block, highlight the Path variable. The name and value of the variable display near the bottom of the dialog box, in the Variable and Value boxes, respectively. 4. Move the cursor to the end of the Value box. (Do not delete anything in the box.
6.8 Setting a Hot Key in the ConsoleWorks Terminal Emulator Window In the terminal emulator window select Hot Keys from the Options menu.
A GS80/160/320 system connected to an SMC without a terminal server can have problems with menu-driven applications displayed in the ConsoleWorks terminal emulator window. (This is the window that displays when you click the Connect link in the ConsoleWorks console_name Configuration screen or when you click the icon to the left of the console name in the Show Consoles screen.) Examples of this problem are that input appears invalid during a Tru64 UNIX install or when running 'setup' in Tru64 UNIX.
Appendix A Using the SMC Software CD Instructions for using the AlphaServer GS80/160/320 Console Management Software CD (AG–RRNCA–BE) can be found in the document AlphaServer GS80/160/320 System Management Console Installation and Release Notes (AA–RRNEA–TE). The printed version of the installation and release notes is packaged with the CD. A PDF version can be found at the top level of the CD.
Table A–1 SMC V4.0 Software Software Version Access Server Loader 1.1 Acesss Server Manager 2.3 Acrobat Reader 4.05c Carbon Copy Access Edition 5.5 WinVNC 3.3.3 Compaq Management Agents 4.37 REV H Compaq AlphaServer Partition Manager (CAPM) 2.0 ConsoleWorks 1.5WNT eXcursion 7.2.177 Internet Explorer 5.5 JRE 1.3.0_01 KEA! 5.1 Perl 5.60.613 Windows NT 4.0 (Service Pack 6) WinZip 7.0 (SR-1) World Wire 2.
Appendix B Compaq-Supplied Configuration Files for ConsoleWorks This appendix describes components that enable ConsoleWorks to operate on the system management console of a GS80/160/320 system. B.1 SCM.PORT The file SCM.PORT contains the event and scan definitions in a format compatible with Polycenter Console Manager (PCM). This file is imported to ConsoleWorks to supply definitions of scans and events. The name of the scan is GS_SCM_SCAN.
All events listed in Table B–1 have a priority of 50 and a severity of critical. Note that event GS_PCI_PBM_SYSEVENT can be triggered by any of three subevents. These are defined and recognized in the Perl script, as described in Section B.2. B.1.1 Loading SCM.PORT is imported with the import_pcm utility. To do this, open a Command Prompt window, change the directory to C:\Cwks, and type the command import_pcm c:\cwks\port\scm.port. The PC will need to be restarted after this is done. B.1.
which contains the trigger text and a defined number of displayed lines before and after this text, to determine if this event is one of which a user needs to be notified. These subevents are: ~E~ FAN. FAIL - POWEROFF IN 30 SECONDS ~E~ LM80. TEMP FAIL ~E~ PS. POK DEASSERTED MAIL.PL then formats a mail addressee, subject, and message body from this information, and contacts (through a TCP/IP socket, port 25) an SMTP (Simple Mail Transport Protocol) server and sends this mail message.
B.2.2 Contents The content of the MAIL.PL file is included in Section B.5. B.3 Verification and Testing The following procedures can be used to ensure that the setup was performed properly and that alerts from the GS80/160/320 system do in fact notify the designated persons. Three methods are provided to be used as appropriate. Method 1 – Complete End-to-End Verification This method uses the console line echo to drive the events as they would normally be encountered.
EVENTMOD and click it. When the event details are displayed, select the link Automatic Actions. Click the Update Event button at the top of the screen. This sequence fires off the mail message. It is not necessary to be connected to any consoles. B.4 Contents of the SCM.
NAME: GS_QBB_OVERTEMP_FAILURE INFO: Overtemp failure from a PSM TEXT: ~E~ QBB%/PSM%% SysEvent: QBB_OVERTEMP_FAILURE*Reg0:*Reg1:* CLASS: SCM SUB_SYSTEM: CSB REGULAR_EXPRESSION: Y START: 0 COUNT: 1 PRIORITY: CRITICAL END: DELETE_EVENT: NAME: GS_HS_OVERTEMP END: ADD_EVENT: NAME: GS_HS_OVERTEMP INFO: Overtemp failure from an HPM TEXT: ~E~ HSW%/HPM%% SysEvent: HS_OVERTEMP*Reg0:*Reg1:* CLASS: SCM SUB_SYSTEM: CSB REGULAR_EXPRESSION: Y START: 0 COUNT: 3 PRIORITY: CRITICAL END: DELETE_EVENT: NAME: GS_PWR_FAIL END: A
INFO: Clock failure from an HPM TEXT: ~E~ HSW%/HPM%% SysEvent: SYSCLK_FAIL*Reg0:* Reg1:* CLASS: SCM SUB_SYSTEM: CSB REGULAR_EXPRESSION: Y START: 0 COUNT: 3 PRIORITY: CRITICAL END: DELETE_EVENT: NAME: GS_PCI_PBM_SYSEVENT END: ADD_EVENT: NAME: GS_PCI_PBM_SYSEVENT INFO: PCI/PBM SysEvent TEXT: ~E~ PCI%/PBM%% SysEvent CLASS: SCM SUB_SYSTEM: CSB REGULAR_EXPRESSION: Y START: 0 COUNT: 3 PRIORITY: CRITICAL END: DELTE SCAN: NAME: GS_SCM_SCAN END: ADD_SCAN: NAME: GS_SCM_SCAN INFO: SCM ASCII messages EVENT: GS_AIR_MOVE
B.5 Contents of the MAIL.PL File #!/usr/local/bin/perl # #-----------------------------------------------------------#+ # File Identification: MAIL.PL # Version Number: V2.0 # Date: 16-Oct-2001 # Used By: ConsoleWorks # Copyright: 2001 Compaq Computer Corporation ##-----------------------------------------------------------#+ # WARNING !!! # =========================== # This file MUST be modified before it can be used.
# Revision History: # V1.0 - Nov 2000. First Release. # V2.0 - Oct 2001. Fix smtp incompatibility. # # Additional Information: # To check for updated versions of this file, check the # web-site below: # www.compaq.com ##-----------------------------------------------------------#+ # NOTES: # 1. This is written using a simple style of the PERL # programming language. # # 2. In PERL, a single character match is the period (".").
# # above, so its commented. $remote = "my.email.server.name.net"; $port = 25; $iaddr = inet_aton($remote) || die "no host: \"$remote\"\n"; $paddr = sockaddr_in($port, $iaddr); $proto = getprotobyname('tcp'); select(SOCK); $| = 1; # Force flush after every write or print socket(SOCK, PF_INET, SOCK_STREAM, $proto) || die "socket: $!"; connect(SOCK, $paddr) || die "connect: ". @SOCK .
#+ # Parse PCI/BPM SysEvents # The 3 line entries look something like this, with the last # line changing # ~E~ PCI3/PBM13 SysEvent # ~E~ PBM13 Error: # ~E~ FAN1 FAIL - POWEROFF IN 30 SECONDS #if ( $ARGV[1] eq /GS_PCI_PBM_SYSEVENT/ ) { open (SC, $ARGV[3]) || die "Can not open event context file - $ARGV[3] $!"; while () { if (/^CONTEXT_BEGIN:/) {last}; } while () { if ($_ eq /^CONTEXT_END:/) {last}; if ($_ =~ /^~E~/) { if ($_ =~ /^~E~ PCI.\/PBM.. SysEvent/) {next;} if ($_ =~ /^~E~ PBM..
Appendix C SMC Hard Disk The hard disk in the SMC is partitioned at the factory. It is recommended that the partitions be used as shown in Table C–1.
Appendix D ConsoleWorks Licenses The ConsoleWorks license for the first GS80/160/320 system (eight console lines) is included with the SMC. Each additional GS80/160/320 system connected to the SMC requires a ConsoleWorks license for the number of console lines planned for the system. The part numbers for these licenses are shown in Table D–1. The licenses listed in Table D–1 are subject to the following restrictions: • A single license may not be used to connect consoles of multiple systems.
Index A Actions (ConsoleWorks) enabling, 3-52 Adding console line, 3-32 Alias (ConsoleWorks), 3-38 B Baud rate, 6-3, 6-4, 6-10, 6-16 COM1, 6-16 GS80/160/320, 6-15, 6-19 terminal server, 6-10 C CAPM, 4-1–4-41 client cannot connect to server, 6-6 discovery phase, 4-7 does not recognize a system, 6-7 does not run, 6-6 does not start, 6-6 files, managing, 4-40 hard partitions, 4-12–4-27 JVM.
adding, 3-32 adding to an existing group, 3-45 configuring, 3-32 deleting, 3-30 giving an alias, 3-38 managing, 3-24–3-45 removing from a group, 3-45 renaming, 3-36 viewing activity, 3-8–3-23, 3-25 viewing configuration, 3-25 displaying terminal emulator window, 6-15 does not start, 6-5 events, B-1 acknowledging, 3-60 adding, 3-56 AlphaServer specific, 3-48 Compaq-supplied, 3-48 defined, 3-56 deleting, 3-60 expunging, 3-62 managing, 3-46–3-63 modifying, 3-56 files, managing, 3-78–3-85 left navigation panel,
AlphaServer specific, 3-48 Compaq-supplied, 3-48 defined, 3-56 deleting, 3-60 expunging, 3-62 managing, 3-46–3-63 modifying, 3-56 eXcursion, 5-2 F Files (CAPM), managing, 4-40 Files (ConsoleWorks), managing, 3-78–3-85 G Graphical Configuration Utility (GCU), 5-1–5-9 H Hard partition adding, 4-18 creating, 4-14 defined, 4-13 deleting, 4-20 grouping consoles for, 3-40 loading partition map, 4-26 modifying partition map, 4-22 Hardware requirements for partitions, 4-19, 4-29 I Icons, 1-7 Internet Explorer c
modifying, 4-34 Partition map, 4-8 loading, 4-26 modifying, 4-22 Partitions, SMC hard disk, C-1 Password CAPM, 4-6 ConsoleWorks changing user password, 3-70 default for first login, 3-5 Path variable, 6-26 Ports COM1, 6-16 terminal server, 6-11 Position identifier dial, terminal server, 6-3 Profile (ConsoleWorks) adding, 3-74 defined, 3-74 modifying, 3-76 Proxy, Internet Explorer, 6-20 Q QBB, defined, 4-9 R Removing console line, 3-30 Restoring the SMC disk, A-1 Restrictions, 1-12 S Scan (ConsoleWorks) a
not communicating with SMC system, 6-2 ports, 6-11 position identifier dial, 6-3 Testing ConsoleWorks setup, B-4 Troubleshooting, 6-1–6-29 U UNIX, text unreadable when booting, 6-4 User (ConsoleWorks) adding, 3-66 communicating with another, 3-68 managing, 3-64–3-77 Index-5
