AlphaServer GS80/160/320 System Management Console Installation and User's Guide Order Number: EK–GSCON–IN. D01 This manual provides installation and configuration instructions for the system management console, as well as information about using the system management console for managing consoles in Compaq AlphaServer GS80/160/320 systems. This manual is for service providers, managers, and operators of Compaq AlphaServer GS80/160/320 systems.
Revised, February 2001 © 2001 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 .......................................................................................................................xv Part 1 Overview of the System Management Console Chapter 1 1.1 1.2 Overview System Management Console Overview ............................................... 1-2 How to Use This Manual....................................................................... 1-4 Part 2 Installing the System Management Console Chapter 2 2.1 2.2 Installation Kit.........................
4.2 4.3 4.4 Cable the SMC to the GS80/160/320..................................................... 4-4 Cable the SMC to the Corporate Network ............................................ 4-6 Check the COM1 Settings..................................................................... 4-8 Chapter 5 5.1 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.3 5.4 5.5 5.6 5.6.1 5.6.2 5.6.3 5.7 5.7.1 5.7.2 5.7.3 5.8 Set the SMC System Time, Date, and Time Zone.................................
.3 7.4 Using the SMC Remotely ...................................................................... 7-6 Keep in Mind......................................................................................... 7-8 Chapter 8 8.1 8.2 8.3 8.4 8.4.1 8.4.2 8.4.3 8.4.4 8.5 8.5.1 8.5.2 8.5.3 8.5.4 8.5.5 8.5.6 8.6 8.6.1 8.6.2 8.6.3 8.6.4 8.6.5 8.7 8.7.1 8.7.2 8.7.3 8.8 8.9 Starting ConsoleWorks ......................................................................... 8-2 Overview of ConsoleWorks...................
9.4.4 9.4.5 9.4.6 9.5 9.5.1 9.5.2 9.5.3 9.5.4 9.5.5 9.6 Modifying a Partition Map............................................................ 9-18 Saving, Validating, and Committing a Partition Map.................. 9-20 Loading a Saved Partition Map .................................................... 9-22 Working With Soft Partitions ............................................................. 9-24 Basic Soft Partitioning..................................................................
Appendix A Using the SMC Software CD Appendix B Installing a Terminal Server in a GS160/320 System B.1 B.2 B.3 B.4 B.5 B.6 B.6.1 B.6.2 B.6.3 Remove the Existing Connection from the SMC System to the GS160/320 .............................................................................................B-2 Attach the Mounting Brackets..............................................................B-4 Install the Terminal Server in the GS160/320 Power Cabinet .............
Appendix E SMC Hard Disk Index Examples 5–1 9–1 Modifying the ConsoleWorks Script (MAIL.PL) ................................. 5-14 Excerpt from a CAPM Log File ........................................................... 9-36 Figures 1–1 3–1 3–2 3–3 3–4 3–5 3–6 3–7 3–8 4–1 4–2 4–3 4–4 4–5 4–6 4–7 5–1 5–2 5–3 5–4 5–5 5–6 5–7 5–8 5–9 5–10 5–11 x System Management Console ............................................................... 1-2 GS80/160/320 Keyswitch.............................................
5–12 5–13 5–14 5–15 5–16 5–17 5–18 5–19 5–20 5–21 5–22 5–23 5–24 5–25 5–26 6–1 6–2 6–3 6–4 6–5 7–1 7–2 7–3 7–4 8–1 8–2 8–3 8–4 8–5 8–6 8–7 8–8 8–9 8–10 8–11 8–12 8–13 8–14 8–15 8–16 8–17 ConsoleWorks Delete Console Screen ................................................. 5-18 Delete Console Verification Message .................................................. 5-19 Access Server Loader Window ............................................................ 5-20 Access Server Loader Confirm Dialog Box.........
8–18 8–19 8–20 8–21 8–22 8–23 8–24 8–25 8–26 8–27 8–28 8–29 8–30 8–31 8–32 8–33 8–34 8–35 8–36 8–37 8–38 8–39 8–40 8–41 8–42 8–43 8–44 9–1 9–2 9–3 9–4 9–5 9–6 9–7 9–8 9–9 9–10 9–11 9–12 9–13 9–14 xii Event event_name Actions Screen...................................................... 8-29 Mail from ConsoleWorks..................................................................... 8-30 Add Scan Screen..................................................................................
9–15 9–16 9–17 9–18 9–19 9–20 9–21 9–22 9–23 9–24 9–25 9–26 9–27 10–1 10–2 10–3 10–4 11–1 11–2 11–3 11–4 11–5 11–6 11–7 11–8 11–9 11–10 11–11 11–12 11–13 11–14 B–1 B–2 B–3 B–4 B–5 B–6 B–7 B–8 B–9 B–10 Validating a Partition Map ................................................................. 9-20 Committing a Partition Map............................................................... 9-21 Work with Partition Maps Screen.......................................................
B–11 C–1 C–2 C–3 C–4 C–5 C–6 C–7 C–8 C–9 C–10 E–1 Terminal Server Cable ........................................................................B-15 COM1 Port ............................................................................................C-2 PCI Box Rear – Local Port Connection .................................................C-3 Mounting Brackets................................................................................C-4 Position Identifier Dial.........................................
Preface Intended Audience This manual is for service providers, 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.
• Chapter 8, ConsoleWorks, contains information about using the application to manage the GS80/160/320 consoles. • Chapter 9, Compaq AlphaServer Partition Manager, contains directions for using this application to partition the GS80/160/320 system. • Chapter 10, Graphical Configuration Utility, has information about setting up and using the utility. • Chapter 11, Troubleshooting, contains suggestions for basic troubleshooting.
Table 1 AlphaServer GS80/160/320 Documentation (Continued) Order Number AG–RLVJA–BE QA–6GAAB–G8 Title AlphaServer GS80/160/320 User Information CD (translations) AlphaServer GS80/160/320 Service Documentation Kit EK–GS320–SV AlphaServer GS80/160/320 Service Manual EK–GS320–RM AlphaServer GS80/160/320 Firmware Reference Manual AG–RKSZ*–BE AlphaServer GS80/160/320 Service Information CD EK–GSCON–IN AlphaServer GS80/160/320 System Management Console Installation and User’s Guide EK–GS320–UP AlphaSer
Part 1 Overview of the System Management Console
Chapter 1 Overview The system management console is the console device for AlphaServer GS80/160/320 systems. It consists of a Compaq Deskpro PC, a DECserver 90M terminal server, and associated hardware and software.
1.1 System Management Console Overview The system management console makes it possible to operate a system that has multiple partitions with a single console device.
With the system management console (SMC), an AlphaServer GS80/160/320 system with multiple console lines can be managed from a single device. The system management console consists of a DECserver 90M terminal server, a Compaq Deskpro PC, and associated hardware and software. Figure 1–1 shows a typical system. The eight-port terminal server can connect to a maximum of eight partitions. The console for each partition can be displayed in a terminal window under ConsoleWorks.
1.2 How to Use This Manual The chapters and appendixes in this manual provide instructions for installing and using the system management console and for restoring the SMC disk. Installing the system management console – In Part 2 of this manual, Chapters 3 through 6 provide procedures for cabling and configuring the system management console. • System with multiple consoles – If the system is partitioned, follow the procedures in Chapters 3, 5 (except Section 5.7), and 6.
Part 2 Installing the System Management Console
Chapter 2 Before You Begin This chapter contains information you need before starting the installation.
2.1 Installation Kit The system management console consists of the SMC PC kit and the terminal server kit. Typically the terminal server kit is installed at the factory. Table 2–1 SMC PC Kit Part Number Description 3X–DS8BA–xx BOM for SMC PC kit; contains these items: See note Compaq Deskpro PC (minitower or desktop box) including keyboard, mouse, and Windows NT 4.0 CD 3R–A1605–xx Power cord and adapter for modem 3R–A1611–AA Worldwide V.
The order number for the SMC PC kit is 3X–DS8BA–xx. It contains the components listed in Table 2–1. (The monitor is separately ordered; it is not part of the SMC PC kit.) The components of the SMC PC kit are installed at the site. When the SMC is ordered with the GS80/160/320 system, the terminal server and cables are installed in the GS160/320 power cabinet or the GS80 cabinet at the factory. When the SMC is not ordered with the GS80/160/320 system, the terminal server kit is installed at the site.
2.2 Installation Sequence Before installing the terminal server, check that the keyswitch and all AC input box breakers on the GS80/160/320 system are turned to Off. The following is the recommended sequence of installation for the GS80/160/320 system and the system management console: 1. Set up the GS80/160/320 hardware. See the AlphaServer GS80 Installation Guide or the AlphaServer GS160/320 Installation Guide. 2.
Chapter 3 Connecting the SMC in a System with Multiple Serial Console Lines A system with multiple console lines is a GS80/160/320 system that has more than one standard I/O (SIO) module. The SIO module is in a PCI box connected to a quad building block, and on it is the SRM console firmware, which provides a command-line interface for operator control of the system or a partition.
3.1 Set Up the SMC Follow the instructions enclosed with the SMC system and monitor to set them up, then start the system. With the GS80/160/320 keyswitch turned off, turn on the AC input box breakers. Make cable connections. Log on to the SMC system.
1. Set up the Compaq Deskpro computer and monitor according to the accompanying instructions. 2. Start the SMC system. As the system software loads, enter information when requested: user name, company name, product ID, and system name. See the AlphaServer GS80/160/320 System Management Console Installation and Release Notes for instructions. 3.
3.2 Cable the Terminal Server to the SMC Connect the management channel connector on the terminal server to network adapter 2 on the SMC system. Figure 3–3 Terminal Server Management Channel Connector 1 PK-1769-00 1. Connect one end of the BN24Q–07 cable (17–04308–05) to the management channel connector on the terminal server ( in Figure 3–3). 2. Connect the other end of the cable to network adapter 2 on the SMC system (Figure 3–4).
Figure 3–4 Network Adapter 2 Minitower Model DPENCM Minitower Model DPENM Desktop Box Model DPENL Desktop Box Model DPEND PK-1723-00 NOTE: The model type is on a label on the top or side of the SMC box.
3.3 Cable the Terminal Server to the GS80/160/320 For PCI boxes in an expander cabinet, make the cable connection to the terminal server. Then record the connections in the table provided and dress the cables. 3.3.1 Make the Cable Connection Cable the local port of the PCI box to the appropriate port on the terminal server with a BN25G cable.
For information about partitioning the system, see AlphaServer GS80/160/320 Getting Started with Partitions.
3.3.2 Record the Connections Record the connections made for this installation in Table 3–2.
3.3.3 Dress the Cables Form a service loop and tie wrap the BN25G cable to the rail. Figure 3–7 Terminal Server Cable 2 3 1 2 3 4 5 6 7 8 1 PK-1753-00 1. At the PCI box end, tie wrap the BN25G cable (17–03212–05) to the CSB junction cable (17–04936–xx) to form a service loop ( in Figure 3–7). 2. Tie wrap the BN25G cable down the rail of the expander cabinet ( ). 3. At the bottom of the rail, coil the BN25G cable and place the extra length in the rail ( ).
3.4 Cable the SMC to the Corporate Network Connect to the corporate network from network adapter 1 on the SMC system. Figure 3–8 Network Adapter 1 Minitower Model DPENCM Desktop Box Model DPENL Minitower Model DPENM Desktop Box Model DPEND PK-1727-00 NOTE: The model type is on a label on the top or side of the SMC box.
Connect a network cable to network adapter 1 on the SMC system, as shown in Figure 3–8. (This cable is not included in the SMC installation kit.) The network adapters are numbered from left to right on the minitower and from bottom to top on the desktop.
Chapter 4 Connecting the SMC in a System with One Serial Console Line A system with a single console line is a GS80/160/320 system that has only one standard I/O (SIO) module. The SIO module is in a PCI box connected to a quad building block, and on it is the SRM console firmware, which provides a command-line interface for operator control of the system.
4.1 Set Up the SMC Follow the instructions enclosed with the SMC system and monitor to set them up, then start the system. With the GS80/160/320 keyswitch turned off, turn on the AC input box breakers. Make cable connections. Log on to the SMC system.
1. Set up the Compaq Deskpro computer and monitor according to the accompanying instructions. 2. Start the SMC system. As the system software loads, enter information when requested: user name, company name, product ID, and system name. See the AlphaServer GS80/160/320 System Management Console Installation and Release Notes for instructions. 3.
4.2 Cable the SMC to the GS80/160/320 Connect the COM1 port of the SMC system to the local port of the GS80/160/320. Figure 4–3 COM1 Port Minitower Model DPENCM Desktop Box Model DPENL COM1 (A) COM1 (A) Minitower Model DPENM Desktop Box Model DPEND COM1 (A) COM1 (A) PK-1735-00 NOTE: The model type is on a label on the top or side of the SMC box.
Install H8585–AA connectors (12–36054–01) on the COM1 (or A) port of the SMC system (Figure 4–3) and the local port of the standard I/O module in the GS80/160/320 system primary PCI box ( in Figure 4–4). Connect these ports with a BN24Q cable (17–04308–05).
4.3 Cable the SMC to the Corporate Network Connect to the corporate network from the network adapter on the SMC system. Figure 4–5 Network Adapter 1 Minitower Model DPENCM Desktop Box Model DPENL Minitower Model DPENM Desktop Box Model DPEND PK-1727-00 NOTE: The model type is on a label on the top or side of the SMC box.
Connect a network cable to network adapter 1 on the SMC system, as shown in Figure 4–5. (This cable is not included in the SMC installation kit.) The network adapters are numbered from left to right on the minitower and from bottom to top on the desktop.
4.4 Check the COM1 Settings Check that the baud rate for the COM1 port is 9600. Change it if it is set to any other speed. Check the other COM1 settings.
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 4–6). 3. Select COM1 and click the Settings… button. The Settings for COM1 dialog box displays (Figure 4–7). 4. If the baud rate displayed is not 9600, change it to 9600. Set the Data Bits to 8, Parity to None, Stop Bits to 1, and Flow Control to XON/XOFF. If these settings are not compatible with your environment, change them to settings that are.
Chapter 5 Configuring the SMC Software The software to be configured depends on the number of consoles in the system.
5.1 Set the SMC System Time, Date, and Time Zone Use the Date/Time icon in the Control Panel to set the time, date, and time zone.
1. From the Start button select Settings|Control Panel. The Control Panel window displays. 2. In the Control Panel double-click the Date/Time icon. The Date/Time Properties dialog box displays. 3. In the Date & Time tab, set the date and time (Figure 5–1). 4. Select the Time Zone tab (Figure 5–2). 5. From the drop-down menu select the time zone for this installation. Click OK.
5.2 Configure the Network Connections Verify the computer name and the protocol for the private LAN. Specify the IP address. Finally, set up the adapter for the corporate network. 5.2.
1. Open the Windows Control Panel: From the Start menu select Settings|Control Panel. 2. Double-click the Network icon. The Network dialog box displays with the Identification tab selected. 3. Click the Change… button. The Identification Changes dialog box displays (Figure 5–3). Check that the box labeled Computer Name correctly identifies the SMC system as a management station on the corporate network. (In the example shown in Figure 5–3, that name is MySMC.) If it does not, enter the correct name.
5.2.
1. In the Network dialog box, select the Protocols tab (Figure 5–4). If the protocol shown is TCP/IP, skip the rest of this page and go on to Section 5.2.3. 2. If the protocol shown is not TCP/IP, highlight the protocol and click the Remove button. A message box displays; click Yes. 3. In the Network dialog box, click the Add… button. The Select Network Protocol dialog box displays (Figure 5–5). Highlight TCP/IP Protocol. Click OK.
5.2.3 Configure Network Adapter 1 Figure 5–6 Microsoft TCP/IP Properties NOTE: The IP address values in the illustration are an example only. Obtain the correct values for this installation from the network administrator.
Enter the static IP address, subnet mask, and gateway. Ask the network administrator for this information. The SMC requires a static IP address; it cannot have a dynamic address (that is, an address assigned by a DHCP server). 1. In the Adapter box of the Microsoft TCP/IP Properties dialog box (Figure 5– 6), select adapter 1. 2. Select the option button labeled Specify an IP address. Enter the IP address, subnet mask, and gateway. Click OK. NOTE: The network card shown in Figure 5–6 is an example only.
5.2.
1. In the Network dialog box, select the Protocols tab. Click the Properties button. 2. The Microsoft TCP/IP Properties dialog box displays (Figure 5–7). Select adapter 2. 3. Select the option button labeled Specify an IP address. Enter the following information: IP address: Subnet mask: 90.0.0.100 255.255.255.0 Leave the Default Gateway blank. Click OK. NOTE: The network card shown in Figure 5–7 is an example only. Another type of network card might be used.
5.2.5 Bind the Protocol Figure 5–8 Bindings Tab in the Network Dialog Box 1. In the Network dialog box, select the Bindings tab. A box with a progress bar displays. 2. When the progress bar indicates that the operation is finished, click Close. 3. Restart the SMC system.
5.2.6 Verify the Network Setup Figure 5–9 Verifying the Network Setup 1. Open a Command window: From the Start menu select Programs| Command Prompt. 2. At the prompt type ping 90.0.0.100. The response should look similar to the first command in Figure 5–9. 3. At the prompt type ping name, where name is the fully qualified computer name displayed in Section 5.2.1. The response should look similar to the second command in Figure 5–9.
5.3 Enter the Mail Server Name in the ConsoleWorks Script Modify the file MAIL.PL to include the name of the mail server. This file is in the folder C:\Cwks\Actions\Event. Example 5–1 Modifying the ConsoleWorks Script (MAIL.PL) #!/usr/local/bin/perl # Note: This is written in a very simple version of Perl for # non-experts) # In perl, a single character match is the period ".", # contrasting with "%" in ConsoleWorks. # Multi is "*" in both cases.
Modify the file MAIL.PL to include the name of the mail server. This file is in the folder C:\Cwks\Actions\Event. 1. Open MAIL.PL in Notepad or another text editor. 2. Find the line ‘$remote = “my.email.server.name.net”;’ ( in Example 5–1. The example shows an excerpt from the file; for a full listing of MAIL.PL, see Appendix D.) 3. Obtain the name of the mail server from the network administrator. Replace everything between the double quotes with the server name. 4. Save the file and close the editor.
5.4 Configure Outlook Express Obtain mail server information from the network administrator before configuring. Figure 5–10 Internet Accounts Dialog Box 1. Double-click the Outlook Express icon on the desktop. If this is the first time Outlook Express is opened, a box displays asking where messages should be stored. Select a folder and click OK. The Outlook Express window displays. 2. From the Tools menu select Accounts. The Internet Accounts dialog box displays (Figure 5–10). 3.
b. The type of server for incoming mail. Outlook Express recognizes POP3 and IMAP. c. The names of the incoming and outgoing mail servers. 5. When Outlook Express sends or receives mail, by default it removes the messages from the server. To leave a copy of messages on the server, do the following: a. From the Tools menu select Accounts. In the Internet Accounts window right-click on the account name and select Properties from the pop-up menu. The account_name Properties dialog box displays (Figure 5–11).
5.5 Delete Unused Consoles in ConsoleWorks Start and log on to ConsoleWorks. Select Consoles and Delete Console.
The default configuration for ConsoleWorks is eight consoles. If the GS80/160/320 system has fewer than eight consoles (that is, fewer than eight PCI boxes with standard I/O modules that are connected to the terminal server), delete the extras in ConsoleWorks. NOTE: Unused consoles generate a great number of events, causing the log files and the file DEFAULT.CONFIG to grow to an unmanageable size and slow down the system. Deleting unused consoles is strongly recommended. 1.
5.6 Configure the Terminal Server: Access Server Loader Access Server Loader configures the IP address and subnet mask of the terminal server. 5.6.
1. Start Access Server Loader: From the Start menu select Programs|Access Server Loader|Access Server Loader. The Access Server Loader window displays (Figure 5–14). 2. Click Setup. The Confirm dialog box displays (Figure 5–15). Click Yes.
5.6.
1. The Access Server Loader Configuration dialog box displays (Figure 5–16). On the Clients tab, enter the following information: Host Name: computer name (Section 5.2.1) Hardware Addr: from the label on the terminal server ( IP Addr: 90.0.0.1 Subnet Mask: 255.255.255.0 in Figure 5–17) NOTE: The IP address you enter in the Access Server Loader Configuration dialog box is the IP address for the terminal server, not for the host. 2. Click OK. The Access Server Loader window displays.
5.6.
1. Keeping the GS80/160/320 keyswitch in the Off position, turn on the breakers on the AC input boxes. NOTE: Turning on the breakers applies power to the terminal server. These instructions assume that the terminal server has not been powered on until now. If it was on when you reached this point, power cycle the terminal server now. 2. Check the Access Server Loader window (Figure 5–18) for the following: a.
5.7 Configure the Terminal Server: Access Server Manager Access Server Manager configures the terminal server for access by the SMC system. 5.7.
1. Start Access Server Manager. From the Start menu select Programs| Access Server Manager|Access Server Manager. The Access Server Manager window displays. 2. From the File menu select New. The New Access Server dialog box displays (Figure 5–20). The default Login Password is access and the default Privileged Password is system. Click OK. 3. The Access Server dialog box displays (Figure 5–21).
5.7.
1. In the Access Server dialog box, select the Utilities tab (Figure 5–22). Select Test Connection. Click the Do It Now… button. The message “Access Server connection test successful” displays. Click OK. 2. Select Connect to Telnet Console. Click the Do It Now… button. The Telnet window displays (Figure 5–23). 3. At the Local> prompt type show server. A snapshot of the server displays. This confirms the connection. 4. Close the Telnet window.
5.7.
1. From the Utilities tab of the Access Server dialog box (Figure 5–22), select Run Command File. 2. Click the Do It Now… button. The Select a Command File dialog box displays (Figure 5–24). 3. Select the file GS_CON.cmds. Click Open. The Run Command File dialog box displays (Figure 5–25). Click OK. The command file runs. 4. Close the Access Server dialog box and return to Access Server Manager. 5. Close Access Server Manager.
5.8 Replace the ConsoleWorks Configuration File The default configuration file put in place by the SMC installation process is for multiple-console systems. If this system has only one console, replace the configuration file.
1. In Windows Explorer go to the folder C:\Cwks\Config (Figure 5–26). 2. Copy the file SERIAL_COM1_DEFAULT.CONFIG: a. Click on the file to highlight it. b. From the Edit menu select Copy. 3. From the Edit menu select Paste. A file named Copy of SERIAL_COM1_DEFAULT.CONFIG is pasted into the folder. 4. Delete the file DEFAULT.CONFIG. 5. Rename the file Copy of SERIAL_COM1_DEFAULT.CONFIG to DEFAULT.CONFIG: a. Click on the file to highlight it. b. From the File menu select Rename. c.
Chapter 6 Configuring the SMC for Remote Use Sections in this chapter are: • Set Up the Modem • Configure the Remote Access Software NOTE: When you have finished setting up the modem and configuring the remote access software, restart the SMC system and set the keyswitch on the GS80/160/320 to On.
6.1 Set Up the Modem Follow the manufacturer’s instructions for cabling the modem. Figure 6–1 COM2 Port Minitower Model DPENCM Desktop Box Model DPENL COM2 (B) COM2 (B) Minitower Model DPENM Desktop Box Model DPEND COM2 (B) COM2 (B) PK-1735A-00 NOTE: The model type is on a label on the top or side of the SMC box. 1. Cable the modem, following the manufacturer’s instructions. Connect the RS-232C cable from the SMC installation kit to COM2 on the SMC system (Figure 6–1; COM2 might be marked B).
2. Open the Control Panel: From the Start menu select Settings|Control Panel. 3. Double-click the Modems icon. The Install New Modem dialog box displays. Click Next. The operating system detects the modem and tests it. 4. The Install New Modem dialog box displays, with the words Standard Modem in the box. Click the Change… button. Click the Have Disk… button. Insert the disk that came with the modem in the appropriate drive. 5. In the dialog box click the Browse button, and select the drive and file.
6.2 Configure the Remote Access Software Configure both remote access applications, Carbon Copy Access Edition and WinVNC. 6.2.
1. Start Carbon Copy Access Edition: From the Start menu select Programs|Carbon Copy Access Edition|Carbon Copy. 2. From the Options menu select Communications. The Communication Properties dialog box displays (Figure 6–3). NOTE: Check with the customer before setting up the Wait for Call feature. 3. In the tab labeled Wait for Call, select the modem and the corporate network in the box labeled Select the connection types. In the Options block, select Wait for Call on Startup. Click OK. 4.
6.2.2 WinVNC Figure 6–5 Default Local System Properties Dialog Box 1. Display the WinVNC settings: from the Start menu select Programs| VNC|Administrative Tools|Show Default Settings. The Default Local System Properties dialog box displays (Figure 6–5). 2. Enter a password and select the checkboxes shown in Figure 6–5.
Part 3 Using the System Management Console
Chapter 7 Getting Started with the System Management Console Sections in this chapter are: • Logging on to the SMC • Using the SMC Locally • Using the SMC Remotely • Keep in Mind Getting Started with the System Management Console 7-1
7.1 Logging on to the SMC Logon is automatic if the administrator account has no password. For manual logon, a different account can be used, or the administrator account can be given a password. Figure 7–1 Windows NT Security Window The SMC system is configured to log on to the administrator account automatically when it powers up. If you leave the administrator account with the default configuration (that is, without a password), you can log on to another account by following these instructions. 1.
If the administrator account is reconfigured to use a password, the Log On dialog box always displays when the PC powers up. You can give that account a password by following these instructions. 1. Press Ctrl+Alt+Del. The Windows NT Security window displays (Figure 7– 1). 2. Click Change Password… The Change Password dialog box displays (Figure 7–2). 3. Enter the old password and the new one, and enter the new password again to confirm it. (The passwords display as asterisks.) Click OK.
7.2 Using the SMC Locally Icons on the SMC desktop are used to run applications locally. Figure 7–3 SMC Desktop The SMC desktop has several icons that enable you to run applications and view documentation online. Table 7–1 shows the icons and describes the result of double-clicking each.
Table 7–1 SMC Desktop Icons Icon Function Runs ConsoleWorks, the console management application used by the SMC. See Chapter 8 for a quick reference and the ConsoleWorks Administration/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.
7.3 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 and running Windows, 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.1 Browsers must have Java and JavaScript enabled.
7.4 Keep in Mind Keep these points in mind when you use the system management console. • An SMC may be used with only one GS80/160/320 system. Do not attach it to multiple systems or 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 requires a static IP address. • In the SMC Web page, use the IP address or the fully qualified system name for the SMC system. Do not use localhost.
Chapter 8 ConsoleWorks ConsoleWorks is a Web-based application that 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 desktop icon on the SMC system or from the link on the SMC Web page.
8.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 8–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.
8.2 Overview of ConsoleWorks 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 8–2 ConsoleWorks Application and Script C:\Cwks\import_pcm SCM.
ConsoleWorks monitors console output for events, 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.
8.3 ConsoleWorks Screen The ConsoleWorks screen is divided into three sections: left navigation panel, main data panel, and lower navigation panel.
Figure 8–4 shows the first screen that displays after you log in to ConsoleWorks. The three parts of the screen are described below. Left navigation panel – This panel is divided into three segments (from top to bottom): • Function links (Consoles, Groups, Send Message, and Logout). Clicking any of these results in either the display of new information in the main data panel or the display of a new popup window. • Menu links (Admin, Manage, Change, Reports, Download, and Help).
8.4 Managing Consoles ConsoleWorks provides access to each console line in a GS80/160/320 system directly from the SMC.
ConsoleWorks is used to manage the console lines in a GS80/160/320 system. To find information about a console line, start by clicking the Consoles link in the left navigation panel of any ConsoleWorks screen to display the Show Consoles screen (Figure 8–5). From there you can view a console line’s activity or its configuration, delete a console (Section 8.4.2) or add one (Section 8.4.3). NOTE: When you open a console, a security warning displays. By loading the certificate authority (Section 8.4.
8.4.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 8–6). 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 displays (Figure 8–7). 3. Select the option button labeled Open this file from its current location and click OK.
Figure 8–8 TDI Certificate 8-12 SMC Installation and User’s Guide
4. The certificate displays (Figure 8–8). Click Install Certificate…. 5. The Certificate Manager Import Wizard displays. Follow the instructions in the wizard and accept the defaults. At the end click Finish. 6. The Root Certificate Store window displays (Figure 8–9). Click Yes. 7. The certificate displays again. Click OK.
8.4.2 Deleting a Console Select Consoles in the left navigation panel, then Delete Console at the top of the 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 8.4.3) to reconfigure it. 1. In the left navigation panel select Consoles. The Show Consoles screen displays. 2. At the top of the Show Consoles screen select Delete Console. The Delete Console screen displays (Figure 8–10). 3. From the Delete dropdown menu select the console to be deleted. 4.
8.4.3 Adding a Console Select Consoles in the left navigation panel, then Add Console at the top of the screen. The type is Telnet. Do not attempt to add a console if eight consoles already exist.
1. In the left navigation panel select Consoles. The Show Consoles screen displays. NOTE: The maximum number of consoles supported by this version of ConsoleWorks is eight. If the Show Consoles screen lists eight consoles (not including the ConsoleWorks internal console, CONWRKS), do not attempt to add a ninth. Instead, you must delete a console before adding another. 2. At the top of the Show Consoles screen select Add Console. The Add Console screen displays. 3. From the Type dropdown menu select Telnet.
Figure 8–13 8-18 console_name Configuration Screen SMC Installation and User’s Guide
5. Click the Add Console button. The console_name Configuration screen displays (Figure 8–13). 6. Enter the profile access information at the bottom of the main data panel. Click the Update button. 7. At the top of the screen select Connect. A window displays showing console line activity. Press Enter to validate the connection. The connection is working if the SCM, SRM, or operating system prompt displays.
8.4.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 eight default consoles, CONSOLE_1 through CONSOLE_8, which have the attributes needed by this system. 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 eight consoles (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.
8.5 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 8.5.1). Compaq supplies a number of events that are specific to the GS80/160/320 system (Section 8.5.2). An event can trigger an action.
8.5.1 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 displays. 2. At the top of the Show Event screen select Add Event. The Add Event screen displays (Figure 8–16). 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.
8.5.2 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.
The Compaq-supplied events warn of a number of AlphaServer conditions that require attention (Table 8–1). These events must be brought into ConsoleWorks before they can be used. Unless ConsoleWorks is re-installed, this procedure is done only once. To import the Compaq-supplied events into ConsoleWorks, do the following: 1. Open a Command window: From the Start button, select Programs| Command Prompt. 2.
8.5.3 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 displays. 2. Select the event link from the list. The Event event_name screen displays (Figure 8–17). 3. Select the Automatic Actions link (above the Pattern box). The Event event_name Actions screen displays (Figure 8–18). 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 8–19 Mail from ConsoleWorks 8-30 SMC Installation and 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.
8.5.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 8–20 Add Scan Screen 1. In the left navigation panel select Manage. From the selection links select Scans. The Show Scans screen displays. 2. At the top of the Show Scan screen select Add Scan. The Add Scan screen displays (Figure 8–20).
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 displays. 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.
8.5.5 Acknowledging and Purging Events Click Events Detail. Select individual events or the Select All link. Click Acknowledge Selected Events, then Purge Acknowledged Events. Privileges required: Acknowledge: Admin – none; Console – R A Delete: Admin – none; Console – R A W C Figure 8–22 ConsoleWorks Events Detail Screen 1. Display the events. You can display the events for one console only or for all consoles. • 8-34 One console: From the left navigation panel select Consoles.
• All consoles: From the lower navigation panel select Events Detail. The ConsoleWorks Events Detail screen displays (Figure 8–22). 2. Select the event or events to acknowledge. • Individual events: Each occurrence of an event is listed on a line. Click in the checkbox on that line to select the event. • All events on the page: Click the link Select All. This selects all events on the page. Click this link on other pages to select all events. 3. Optionally, enter a comment in the Comment box. 4.
8.5.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. Privileges required: Admin – R W C; Console – none Figure 8–24 Expunge Events Screen 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.
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. Wait for the message indicating the number of events that have been expunged (Figure 8–25). 6. Close the ConsoleWorks application. 7. Stop the ConsoleWorks services: From the Start menu select Settings| Control Panel. Double-click the Services icon.
8.6 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.
8.6.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 8–27 Add User Screen 1. In the left navigation panel select Manage. From the selection links select Users. The Show Users screen displays. 2. At the top of the Show Users screen select Add User. The Add User screen displays (Figure 8–27). 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 displays (Figure 8–28). 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.
8.6.2 Communicating with Another User To send a message, select 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 8–29 Send a User Message Screen Sending a Message 1. In the left navigation panel select Send Message. The Send a User Message screen displays (Figure 8–29). 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.
8.6.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 8–31 Change Password Screen 1. In the left navigation panel select Change. From the selection links select Password. The Change Password screen displays (Figure 8–31). 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 8– 32) displays, 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.
8.6.4 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 displays. 2. At the top of the Show Profiles screen select Add Profile. The Add Profile screen displays (Figure 8–33). 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 displays (Figure 8– 34). 5. Select privileges for users who have this profile. 6.
8.6.5 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 displays (Figure 8–35). 2. Select the profile to modify from the list. The profile_name screen displays (Figure 8–36). 3. Make the changes to the profile. Click the Update Profile button.
8.7 Managing ConsoleWorks Log Files ConsoleWorks creates log files for each console (CONSOLE_1 through CONSOLE_8 and CONWRKS). 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 (CONSOLE_1 through CONSOLE_8 and CONWRKS) 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. The logs for CONSOLE_1 through CONSOLE_8 show all activity on the console. The log for CONWRKS shows activity and events from all consoles. Log files can quickly fill the disk if they are not managed.
8.7.1 Viewing a Log File Select 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 Consoles. The Show Consoles screen displays. 2. Select the console from the list. The console_name Configuration screen displays. 3. At the top of the screen select Logs. The console_name Logfiles screen displays (Figure 8–37). 4. Select the log file from the list. The file displays (Figure 8–38).
8.7.2 Deleting Log Files Select Consoles in the left navigation panel. Then select the console from the list.
1. From the left navigation panel select Consoles. The Show Consoles screen displays. 2. Select the console from the list. The console_name Configuration screen displays. 3. At the top of the screen select Logs. The console_name Logfiles screen displays (Figure 8–39). 4. Click the checkboxes of the log files to delete and click the Delete button.
8.7.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 displays. 2. From the Compose menu select New Message. The New Message window displays (Figure 8–40). 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 folder (D:\CWKS) for a list of files. 5.
8.8 Saving the Configuration Once you have established the ConsoleWorks configuration, save it to a Zip or floppy disk, D drive, or a network drive so you can easily restore it if ConsoleWorks must be reinstalled. Shut down ConsoleWorks before saving the configuration.
You can save the configuration to a Zip disk or floppy disk, or to the D drive on the SMC or a network drive. Saving the Configuration 1. If ConsoleWorks is running, shut it down. 2. From the Start menu select Programs|Windows NT Explorer. 3. In the Exploring window select C:\Cwks\Config (Figure 8–41). 4. From the Edit menu select Copy. 5. If you are saving the configuration to a Zip disk or a floppy disk, insert the disk in the drive. 6.
8.9 Using KEA! with ConsoleWorks Select Change|Connect Settings in the left navigation panel. Then select the option button labeled Use Java Telnet Proxy. Select 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.
1. Select Change in the left navigation panel. From the selection links select Connect Settings. The Console Connection Settings screen displays (Figure 8–42). Select the Use Java Telnet Proxy option button. The change takes effect immediately. 2. In the left navigation panel select Consoles. The Show Consoles screen displays. Select the console to which you want to connect KEA!. The console_name Configuration screen displays. 3. At the top of the screen select Connect.
Figure 8–44 KEA! Connection Window 8-62 SMC Installation and User’s Guide
Chapter 9 Compaq AlphaServer Partition Manager The Compaq AlphaServer Partition Manager (CAPM) simplifies creation of partitions.
9.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 9–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.
9.2 Overview of CAPM CAPM enables the user to partition a GS80/160/320 system without using console commands.
Compaq AlphaServer Partition Manager (CAPM) is a graphical application that simplifies the creation and management of partitions1 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. These can be hard partitions and, if OpenVMS Galaxy is the operating system in a hard partition, soft partitions. CAPM uses ConsoleWorks usernames and passwords.
9.3 Partition Maps The partition map provides partitioning information about the GS80/160/320 system. Figure 9–3 Sample Partition Map NOTE: Partition numbering in CAPM differs from partition numbering shown in the output of console commands.
Figure 9–3 shows the Current Partition Map screen. The partition map provides information about the GS80/160/320 system in the form of a table. 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) or Unassigned. Any QBB that has not explicitly been assigned to a partition is part of the Unassigned partition.
9.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.
When you start CAPM, the first screen that displays (after the login box) is the Current Partition Map (Figure 9–4), which shows hard partition information. Section 9.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 9.5 discusses soft partitions. Hard partitions do not share any CPU, memory, or I/O resources.
9.4.
1. From the Current Partition Map screen (Figure 9–4), click Next. The Work with Partition Maps screen displays (Figure 9–5). 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 9–6 Create/Modify a Partition Map 9-12 SMC Installation and User's Guide
4. The Create/Modify a Partition Map screen displays (Figure 9–6). 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 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 9.4.5.
9.4.2 Adding a Hard Partition Figure 9–7 Add/Modify Hard Partition Screen 1. From the Current Partition Map screen (Figure 9–4) click Next. The Work with Partition Maps screen displays (Figure 9–5). 2. Select the option button labeled Modify the current partition map. The Create/Modify Partition Map screen displays (Figure 9–6). 3. Click Add. The Add/Modify Hard Partition screen displays (Figure 9–7). The number of the hard partition is shown in the title bar. 4.
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 9–7 does not yet have a connection to a PCI box with a standard I/O module. In Figure 9–8 this is resolved by adding QBB 7 to the partition. The message below the Total block now indicates that the hardware requirements for a partition have been met.
9.4.3 Deleting a Hard Partition Figure 9–9 Create/Modify a Partition Map Screen 1. From the Current Partition Map screen (Figure 9–4) click Next. The Work with Partition Maps screen displays (Figure 9–5). 2. Select the option button labeled Modify the current partition map. The Create/Modify a Partition Map screen displays (Figure 9–9). 3. Click to highlight the partition to be deleted, and click the Delete button.
4. A confirmation message displays (Figure 9–10). 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, as shown in Figure 9–11.
9.4.4 Modifying a Partition Map Figure 9–12 Work with Partition Maps Screen 1. From the Current Partition Map screen (Figure 9–4) click Next. The Work with Partition Maps screen displays (Figure 9–12). 2. Select the option button labeled Modify the current partition map. Click Next. The Create/Modify a Partition Map screen displays (Figure 9–9). 3. Click to highlight the partition to be modified, and click the Modify button. The Add/Modify Hard Partition screen displays (Figure 9–13).
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. 5. Specify the operating system for the partition in the OS type dropdown list, and, optionally, supply a name for the partition in the name block. Click OK. The Create/Modify a Partition Map screen returns. 6.
9.4.5 Saving, Validating, and Committing a Partition Map Figure 9–14 Saving a Partition Map Figure 9–15 Validating a Partition Map Saving a Partition Map 1. In the Create/Modify a Partition Map screen click the Save As… button. An information box displays (Figure 9–14). 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).
Validating a Partition Map To have CAPM evaluate a partition map and determine if it is valid, in the Create/Modify a Partition Map screen click the Validate button. A message confirms that the partition map is valid (Figure 9–15) or indicates that it is not valid. Committing a Partition Map To commit the partition map to the GS80/160/320 system, in the Create/Modify a Partition Map screen click the Commit button. If the map has not been saved to a file, a message displays asking you to do so.
9.4.
1. In the Current Partition Map screen click Next. The Work with Partition Maps screen displays (Figure 9–17). 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 9.4.5) in the Partition Map box, or click the Browse button to find the file. The default file extension is .PMF.
9.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.
9.5.
1. In the Add/Modify Hard Partition screen (Figure 9–18), select the option button labeled Basic soft partitioning and click the Soft Partitions… button. 2. An informational message displays (Figure 9–19), indicating which QBB has the console for the hard partition. This QBB must be assigned to the first soft partition. Click OK. 3.
9.5.
1. In the Basic Soft Partition screen (Figure 9–20), click the Add… button. The Add/Modify Soft Partition screen displays (Figure 9–21). 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.
9.5.
1. In the Basic Soft Partition screen (Figure 9–22), click to select the partition you want to modify and click the Modify… button. The Add/Modify Soft Partition screen displays (Figure 9–23). 2. Do one of the following in the Add/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.
9.5.
1. In the Basic Soft Partition screen (Figure 9–24), 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 9–25). Click the appropriate button. 3. The Basic Soft Partition screen updates if you chose to delete the partition. (See Figure 9–26.) Click OK.
9.5.
CAUTION: The Advanced Soft Partition screen is intended for users who are familiar with AlphaServer SRM environment variables. CAPM does not validate any information entered in this screen. Advanced Soft Partitioning gives the user more precise control than the Basic Soft Partition process. It requires knowledge of AlphaServer SRM environment variables. 1.
9.6 Managing CAPM Files CAPM creates log files and partition map files. Example 9–1 Excerpt from a CAPM Log File [Tue Dec 05 12:01:03 EST 2000, pmu.ccm.CwkCCM, 0, Info] Successful login by console_manager [Tue Dec 05 12:01:04 EST 2000, pmu.PMUServerImpl, 3, Trace] Discovery beginning [Tue Dec 05 12:01:04 EST 2000, pmu.PMUServerImpl, 6, Trace] Discovering console WF2 [Tue Dec 05 12:01:05 EST 2000, pmu.ccm.CwkCCM, 0, Info] Opened connection on WF2 [Tue Dec 05 12:01:05 EST 2000, pmu.
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 Example 9–1. The file is saved to the folder C:\SMC\CAPM\LOGS. Every time CAPM runs, information is appended to the current log file. This file, always named CAPMLOG.TXT, is used until its size reaches 1 MB. It is then renamed CAPMLOG.BAK, and a new CAPMLOG.TXT log is started. NOTE: When a new CAPMLOG.TXT file is created, the existing CAPMLOG.
Chapter 10 Graphical Configuration Utility The Graphical Configuration Utility (GCU) is an OpenVMS Galaxy utility for creating and maintaining partitions.
10.1 Setting Up the GCU Define information for the Galaxy instances in the eXcursion Control Panel. 10.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 10–1). 3. In the Access tab select the Enable Access Control checkbox, enter the Node Name, and click the Add button. Click Apply.
10.1.
1. In the eXcursion Control Panel window select the Accounts tab (Figure 10– 2). 2. Enter the Account Alias, Host name, Username, and Password. Click the Add button. 3. Repeat step 2 for each instance.
10.1.
1. In the eXcursion Control Panel window select the Applications tab (Figure 10–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 drop-down 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.
10.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 URL http://www.openvms.compaq.com:8000/ and click the link OpenVMS Operating System. Scroll down the list to OpenVMS Alpha Galaxy Guide.
Part 4 Troubleshooting
Chapter 11 Troubleshooting This chapter contains troubleshooting tips for the system management console hardware and software.
11.1 Troubleshooting Chart Table 11–1 lists a number of potential symptoms along with their possible causes and suggested solutions. Table 11–1 Troubleshooting Chart Symptom Possible Cause Suggested Solution DEFAULT.CONFIG has become too large. Delete C:\Cwks\Config\ DEFAULT.CONFIG. Copy 8_CONSOLE_DEFAULT.CONFIG (systems with multiple console lines) or SERIAL_COM1_ DEFAULT.CONFIG (one console line) in the same folder. Rename it DEFAULT.CONFIG. Change attributes from read only to read/write.
Table 11–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution Communications (continued) No prompt in a terminal window. Text is garbled when UNIX is booting. The SMC system and the terminal server are connected by the wrong cable. Change the cable to a BN24Q. Terminal server is hung. Reload the terminal server using Access Server Manager (Section 5.7). Console line is not associated with a partition. No action required. Baud rate mismatch. Change the baud rate (Sections 11.
Table 11–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution ConsoleWorks has unused consoles. Delete consoles that will never be used (Section 8.4.2). A large number of events has accrued. Acknowledge (Section 8.5.5) or expunge (Section 8.5.6) events. DEFAULT.CONFIG has become too large. Delete the file and copy 8_CONSOLE_DEFAULT.CONFIG (systems with a terminal server) or SERIAL_COM1_ DEFAULT.CONFIG (no terminal server) to DEFAULT.CONFIG.
Table 11–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution ConsoleWorks (continued) A security warning displays whenever a console is opened. Certificate authority has not been loaded. Load the certificate authority (Section 8.4.1). ConsoleWorks services are not running. Start ConsoleWorks services (Section 11.5). CAPM service is not running. Start the CAPM service in the same way as the ConsoleWorks services (Section 11.5). The service name is Compaq CAPM Server.
Table 11–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution The ConsoleWorks application is open. Exit ConsoleWorks (but leave the ConsoleWorks services running). HMMO service is not running on the SMC system. Start the service in the same way as the ConsoleWorks services (Section 11.5). The service name is Compaq SMC HMMO Server. The correct version of JRE is not installed on the system trying to access the Web page.
Table 11–1 Troubleshooting (Continued) Symptom Possible Cause Suggested Solution SMC Web Page (continued) Clicking a link to either of the user guides does not display the manual. You are using Netscape V6.0 with Windows 98. This combination is unsupported; use a previous version of Netscape or use Internet Explorer. Acrobat Reader is not the correct version. Upgrade to Acrobat Reader V4.05c or later. Restart after Power Fail The SMC system does not automatically restart after a power failure.
11.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. 11.2.
1. Open Access Server Manager (ASM). From the Start menu select Programs|Access Server Manager|Access Server Manager. A Browser window displays (Figure 11–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 11–2).
Figure 11–3 Configuration Dialog Box 11-10 SMC Installation and 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 11–3). 5. Click the Properties button. The Connection Service Configuration dialog box displays (Figure 11–4). 6. Change the port speed in this box, and check that the other settings are correct for your environment. Click OK.
11.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 11.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.
11.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. 11.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 11–6). 3. Select COM1 and click the Settings… button. The Settings for COM1 dialog box displays (Figure 11–7). 4. Change the baud rate, and check that the other settings are correct for your environment. Click OK.
11.3.
1. In the left navigation panel of a ConsoleWorks window, select Consoles. The Show Consoles screen displays (Figure 11–8). 2. Click the icon to the left of the CONSOLE_1 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 11.3.1 and set the COM1 speed to a different setting. 4.
11.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.
11.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 11–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….
11.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 11–13 and the label inside the SMC cover show the location of the switchpack. 4. Set switch 6 to on (Figure 11–13). 5.
11.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 11–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 Name and Value boxes, respectively. 4. Move the cursor to the end of the Value box. (Do not delete anything in the box.
Appendix A Using the SMC Software CD Instructions for using the AlphaServer GS80/160/320 Console Management Software CD (AG–RMDRB–BE) can be found in the document AlphaServer GS80/160/320 System Management Console Installation and Release Notes (AV–RMDQB–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.
In addition, shortcuts are placed on the desktop for the following: • ConsoleWorks for AlphaServer • Compaq AlphaServer Partition Manager • KEA! • ConsoleWorks Administration/User Guide (PDF format) • AlphaServer GS80/160/320 System Management Console Installation and User’s Guide (a PDF version of this manual) A-2 SMC Installation and User’s Guide
Appendix B Installing a Terminal Server in a GS160/320 System When a GS160/320 system is reconfigured from a single-console-line to a multiple-console-line system, the system management console must be upgraded. This appendix contains instructions for installing the hardware for that upgrade.
B.1 Remove the Existing Connection from the SMC System to the GS160/320 Remove the cable between the SMC system and the GS160/320. Figure B–1 COM1 Port Minitower Model DPENCM Desktop Box Model DPENL COM1 (A) COM1 (A) Minitower Model DPENM Desktop Box Model DPEND COM1 (A) COM1 (A) PK-1735-00 NOTE: The model type is on a label on the top or side of the SMC box.
1. Remove the BN24Q cable (17–04308–05) from the H8585–AA connectors (12–36054–01) on the COM1 port of the SMC system (Figure B–1) and the local port of the GS160/320 ( in Figure B–2). NOTE: The COM1 port might be labeled A. 2. Remove the H8585–AA connector from the COM1 port.
B.2 Attach the Mounting Brackets Position the top rear holes over the alignment pins. Fasten the brackets with the M5 screws.
1. Position the holes in the bracket (indicated by in Figure B–3) over the alignment pins ( ) on the terminal server tray. The front end of the bracket should be 2 inches (5 cm) from the front of the terminal server. (The front is the face that has the port connectors.) 2. Fasten the bracket to the terminal server with the M5 screws ( ). 3. Repeat with the bracket on the other side.
B.3 Install the Terminal Server in the GS160/320 Power Cabinet Set the position identifier dial to management agent and install the terminal server in the power cabinet.
1. Set the position identifier dial at the rear of the terminal server to management agent (the position after 14; Figure B–4). 2. Attach the power cord to the rear of the terminal server power supply. Do not plug the other end into the power source yet. 3. From the rear of the GS160/320 power cabinet, install the U-type fasteners in holes 14 and 16 from the bottom on both side rails, above the AC input boxes (Figure B–5). 4. Install the terminal server in the power cabinet.
B.4 Connect the Terminal Server to the Power Source Connect the power cord to J19 of the bottom AC input box.
Plug the power cord of the terminal server into J19 of AC input box 1 (the bottom AC input box) in the GS160/320 power cabinet. If the GS160/320 system is powered up, the terminal server powers up when it is plugged in.
B.5 Cable the Terminal Server to the SMC System Connect the management channel connector on the terminal server to network adapter 2 on the SMC system. Figure B–7 Terminal Server Management Channel Connector 1 PK-1769-00 1. Connect one end of the BN24Q–07 cable (17–04308–05) to the management channel connector on the terminal server ( in Figure B–7). 2. Connect the other end of the cable to network adapter 2 on the SMC system (Figure B–8).
Figure B–8 Network Adapter 2 Minitower Model DPENCM Minitower Model DPENM Desktop Box Model DPENL Desktop Box Model DPEND PK-1723-00 NOTE: The model type is on a label on the top or side of the SMC box.
B.6 Cable the Terminal Server to the GS160/320 For each console, connect a terminal server port to the local port of the PCI box. B.6.1 Make the Cable Connection Figure B–9 PCI Box Rear — Local Port Location 1 PK-1724-00 Make the connection for each console: 1. Attach an H8585–AA connector (12–36054–01) to the local port of the PCI box ( in Figure B–9). 2.
Table B–1 Terminal Server Cabling QBB Number Terminal Server Port GS160 GS320 1 0 0 2 1 1 3 2 2 4 3 3 5 — 4 6 — 5 7 — 6 8 — 7 Figure B–10 Terminal Server Ports 2 PK-1770A-00 Installing a Terminal Server in a GS160/320 System B-13
B.6.2 Record the Connections Record the connections made for this installation in Table B–2.
B.6.3 Dress the Cable Figure B–11 Terminal Server Cable 2 3 1 2 3 4 5 6 7 8 1 PK-1753-00 1. At the PCI box end, tie wrap the 17–03212–cable to the CSB junction cable (17–04936–xx) to form a service loop ( in Figure B–11). 2. Tie wrap the 17–03212–05 cable down the rail of the cabinet ( ). 3. At the bottom of the rail, coil the cable and place the extra length in the rail ( ).
Appendix C Installing a Terminal Server in a GS80 System When a GS80 system is reconfigured from a single-console-line to a multipleconsole-line system, the system management console must be upgraded. This appendix contains instructions for installing the hardware for that upgrade.
C.1 Remove the Existing Connection from the SMC System to the GS80 Remove the cable between the SMC system and the GS80. Figure C–1 COM1 Port Minitower Model DPENCM Desktop Box Model DPENL COM1 (A) COM1 (A) Minitower Model DPENM Desktop Box Model DPEND COM1 (A) COM1 (A) PK-1735-00 NOTE: The model type is on a label on the top or side of the SMC box.
1. Remove the BN24Q cable (17–04308–05) from the H8585–AA connectors (12–36054–01) on the COM1 port of the SMC system (Figure C–1) and the local port of the GS80 ( in Figure C–2). NOTE: The COM1 port might be labeled A. 2. Remove the H8585–AA connector from the COM1 port of the SMC.
C.2 Attach the Mounting Brackets Position the top rear holes over the alignment pins. Fasten the brackets with the M5 screws.
1. Position the holes in the bracket (indicated by in Figure C–3) over the alignment pins ( ) on the terminal server tray. The front end of the bracket should be 2 inches (5 cm) from the front of the terminal server. (The front is the face that has the port connectors.) 2. Fasten the bracket to the terminal server with the M5 screws ( ). 3. Repeat with the bracket on the other side.
C.3 Install the Terminal Server in the GS80 Rack Set the position identifier dial to management agent and install the terminal server in the power cabinet.
1. Set the position identifier dial at the rear of the terminal server to management agent (the position after 14; Figure C–4). 2. Attach the power cord to the rear of the terminal server power supply. Do not plug the other end into the power source yet. 3. At the front of the GS80 rack, install the U-type fasteners in holes 1 and 3 at the bottom of both side rails (Figure C–5). 4. Install the terminal server in the rack.
C.4 Connect the Terminal Server to the Power Source Connect the power cord to J5A or J1 of the bottom AC input box.
Plug the power cord of the terminal server into AC input box 1 (the bottom AC input box) in the GS80 rack: • North America systems (–CA variant), use outlet J4A. • Europe and Japan systems (–CB and –CC variants), use outlet J1. Figure C–6 shows the location of these outlets. If the GS80 system is powered up, the terminal server powers up when it is plugged in.
C.5 Cable the Terminal Server to the SMC System Connect the management channel connector on the terminal server to network adapter 2 on the SMC system. Figure C–7 Terminal Server Management Channel Connector 1 PK-1769-00 1. Connect one end of the BN24Q–07 cable (17–04308–05) to the management channel connector on the terminal server ( in Figure C–7). 2. Connect the other end of the cable to network adapter 2 on the SMC sytem (Figure C–8).
Figure C–8 Network Adapter 2 Minitower Model DPENCM Minitower Model DPENM Desktop Box Model DPENL Desktop Box Model DPEND PK-1723-00 NOTE: The model type is on a label on the top or side of the SMC box.
C.6 Cable the Terminal Server to the GS80 For each console, connect a terminal server port to the local port of the PCI box. C.6.1 Make the Cable Connection Figure C–9 PCI Box Rear — Local Port Location 1 PK-1724-00 Make the connection for each console: 1. Attach an H8585–AA connector (12–36054–01) to the local port of the PCI box ( in Figure C–9). 2.
Table C–1 Terminal Server Cabling Terminal Server Port QBB Number 1 0 2 1 3 — 4 — 5 — 6 — 7 — 8 — Figure C–10 Terminal Server Ports 1 PK-1770-00 Installing a Terminal Server in a GS80 System C-13
C.6.2 Record the Connections Record the connections made for this installation in Table C–2.
Appendix D 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. D.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 D–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 D.2. D.1.1 Loading SCM.PORT is imported with the import_pcm utility. To do this, open a Comand 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. D.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.
Verify that you can connect to the console and receive a prompt. The prompt can be from the SCM, SRM, or operating system. If you do not see a prompt, configure the console as appropriate. Refer to Section D.4 for the contents of the SCM.PORT file. For any event, look for the string located at the TEXT: label. These patterns can also be seen in the pattern field of the discrete event screen. You can trigger an event by typing the pattern string on the console.
D.4 Contents of the SCM.
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: ADD_EVENT: NAME: GS_PWR_FAIL INFO: Vital power failure from an HPM TEXT: ~E~ HSW%/HPM%% SysEvent: PWR_FAIL*Reg0:*Reg1:* CLASS: SCM SUB_SYSTEM: CSB REGULAR_EXPRESSION: Y START: 0 COUNT: 3 P
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_MOVER_FAILURE EVENT: GS_VITAL_POWER_FAILURE EVENT: GS_QBB_OVERTEMP_FAILURE EVENT: GS_HS_OVERTEMP EVENT: GS_PWR_FAIL EVENT: GS_SYSCLK_FAIL EVENT: GS_PCI_PBM_SYSEVENT END: Compaq-S
D.5 Contents of the MAIL.PL File #!/usr/local/bin/perl # Note: This is written in a very simple version of Perl for non-experts) # In perl, a single character match is the period ".", contrasting with "%" # in ConsoleWorks. Multi is "*" in both cases. # Also for WinNT, you can not start a perl file directly, # though you can in a command window # Therefore create a single line script MAIL.BAT like this # C:\Perl\Bin\Perl C:\Cwks\Actions\Event\mail.
# print SOCK "DATA\n"; print SOCK "From: $fm\n"; print SOCK "Subject: $subj\n"; print SOCK "To: $to\n"; print SOCK "\n"; print SOCK @msg; print SOCK "\n.\n"; sleep(2); print SOCK "QUIT\n"; sleep(2); close (SOCK) || die "close: $!"; #Note the error...
} } close(SC); } #+ # The other events are just mail...
Appendix E 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 E–1. Table E–1 Use of Disk Partitions Partition Recommended Use C Operating system and applications D User setups (unique scripts, other inputs) and log files The directory structure of the C partition is shown in Figure E–1.
Figure E–1 C Partition E-2 SMC Installation and User's Guide
Index A Access Server Loader, 5-20 creating the database, 5-22 verifying the connection, 5-24 Access Server Manager, 5-26 Telnet window, 5-29 Actions (ConsoleWorks) enabling, 8-28 Administrator account, 3-3, 4-3 AlphaServer hardware, 2-4 B Baud rate, 11-3, 11-8, 11-14 COM1, 4-8, 11-14 GS80/160/320, 11-13, 11-17 terminal server, 11-8 BN24Q cable, 4-5, B-3, B-10, C-3, C-10 BN25G cable, 3-6, 3-9, B-10, C-10 C Cables BN24Q, 4-5, B-3, B-10, C-3, C-10 BN25G, 3-6, 3-9, B-10, C-10 RS-232C, 6-2 Cables, dressing,
renaming, 8-20 viewing activity, 8-9 viewing configuration, 8-9 ConsoleWorks, 1-3, 8-1–8-62, D-1–D-10 access time, 11-4 actions enabling, 8-28 certificate authority, 8-10–8-13 configuration restoring, 8-59 saving, 8-59 configuring for single console, 5-32 console adding, 8-16 configuring, 8-16 deleting, 8-14 renaming, 8-20 viewing activity, 8-9 viewing configuration, 8-9 displaying terminal emulator window, 11-13 does not start, 11-4 events, D-1 acknowledging, 8-34 adding, 8-24 AlphaServer specific, 8-26 Co
deleting, 8-34 expunging, 8-36 managing, 8-22–8-37 modifying, 8-24 eXcursion, 10-2 changing proxy setting, 11-18 IP address, 5-10, 7-8 IP host, 11-3 K Files (CAPM), managing, 9-36 Files (ConsoleWorks), managing, 8-50– 8-57 KEA!, using with ConsoleWorks, 8-60 Keyswitch, 2-4, 3-3, 4-3 Kits SMC, 2-2 terminal server, 2-3 G L Graphical Configuration Utility (GCU), 10-1–10-9 GS80/160/320 hardware, 2-4 keyswitch, 3-2, 4-2 local port, 3-6, 4-5 Local port, PCI box, 3-6, 4-5, B-12, C-3, C-12 Log file (Console
OpenVMS Galaxy, 10-1 Outlook Express, 5-16 Overview, 1-2 ConsoleWorks, 8-4 P Partition hard adding, 9-14 committing partition map, 9-20 creating, 9-10 defined, 9-9 deleting, 9-16 loading partition map, 9-22 modifying partition map, 9-18 saving partition map, 9-20 validating partition map, 9-20 soft adding, 9-28 advanced, 9-34 basic, 9-26 defined, 9-25 deleting, 9-32 modifying, 9-30 Partition map, 9-6 committing, 9-20 loading, 9-22 modifying, 9-18 saving, 9-20 validating, 9-20 Partitions, SMC hard disk, E-1
not communicating with terminal server, 11-2 restart after power fail, 11-7 restart after power failure, 11-22 restoring disk, A-1 restrictions, 7-8 running applications remotely, 7-6 setting up the box and monitor, 3-2, 4-2 setting up the modem, 6-2 software, 3-3, 4-3 SMC Web page, 7-6, 7-8, 8-2, 9-2 cannot display user guides, 11-7 displaying, 7-7 does not display, 11-6 running CAPM from, 9-3 running ConsoleWorks from, 8-3, 9-3 Windows NT service, 11-6 Soft partition adding, 9-28 advanced, 9-34 basic, 9-2
