HP Netserver AA Solution Administrator’s Guide HP Part Number 5971-3014 Printed in April 2001
NOTICE The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents Preface Chapter 1 — Introduction Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Endurance Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Endurance Server Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Endurance Server Hardware Configuration . . . . . . . . . . . . . . . . . . . . 1-8 Endurance Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Connection States . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20 Keyboard/Pointer States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21 Other Endurance Component States . . . . . . . . . . . . . . . . . . . . . . . 2-21 Monitoring the Endurance Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 Endurance Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security Features for Remote Use of Endurance Manager . . . . . . . . . . . 4-25 Chapter 5 — Commands Issuing Endurance Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Verifying Endurance Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 CE1 or CE2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 CE_O/S Shutdown . . . . . . . . . . . . . . . . . . .
Chapter 7 — Tools and Utilities MIC BIOS Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Using the MIC BIOS Setup Utility . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 MTCFLASH Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7 Running MTCFLASH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8 MTCEINFO Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12 Running MTCEINFO . . . . . . . . . . .
Replacing an IOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18 Removing an IOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18 Preparing a New IOP for Installation . . . . . . . . . . . . . . . . . . . . . . 9-19 Installing a New IOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20 Replacing a CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22 Updating MIC BIOS, FPGA, and Microcode. . . . . . . . . . . . . . . .
Tables 1-1 1-2 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 3-1 3-2 4-1 4-2 4-3 4-4 4-5 4-6 4-7 4-8 4-9 4-10 4-11 4-12 5-1 5-2 Tables Endurance Server Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . Endurance Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi-Boot Options for IOPs. . . . . . . . . . . . . . . . . . . . . . . . . . Server States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CE Operating System States . . . . . . . . . .
5-3 5-4 5-5 5-6 5-7 5-8 5-9 5-10 5-11 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 5-27 5-28 5-29 5-30 5-31 5-32 5-33 5-34 6-1 6-2 7-1 7-2 7-3 7-4 7-5 8-1 9-1 9-2 A-1 A-2 x CE1 or CE2 Commands . . . . . . . . . . . . . . . . . . CE Parameters . . . . . . . . . . . . . . . . . . . . . . . ESI Data Paths . . . . . . . . . . . . . . . . . . . . . . . IOP1 and IOP2 Commands . . . . . . . . . . . . . . . . . IOPn.DatagramService Commands. . . . . . . . . . . . .
A-3 A-4 Tables Firmware LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Fiber LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 1-1 1-2 2-1 2-2 2-3 2-4 4-1 4-2 4-3 4-4 4-5 4-6 4-7 6-1 6-2 7-1 7-2 7-3 7-4 7-5 A-1 B-1 B-2 Figures Endurance Server . . . . . . . . . . . . . . . . . . . . . . Endurance Server Physical versus Logical View . . . . . . Interconnect Paths in the Endurance Server . . . . . . . . . The Virtual Network . . . . . . . . . . . . . . . . . . . . Overview of IOP Boot Process . . . . . . . . . . . . . . . Overview of CE Boot Process . . . . . . . . . . . . . . . . Endurance Manager Main Window . . . . . .
Preface This guide describes how to install the HP Netserver AA Solution Enduranceâ server, the Assured AvailabilityΤΜ solution from Hewlett-Packard Company. Audience This guide is written for experienced network administrators and technical personnel responsible for installing, configuring, administering, and managing network server hardware and software, including Microsoftâ Windowsâ.
• Endurance Upgrade/Downgrade Procedures that describes the procedure for downgrading an operational Endurance server. This information is available online using the HP Netserver AA Solution Endurance CD. For Release 4.0, there is no upgrade procedure. All the documentation is available online using the HP Netserver AA Solution Endurance CDROM that was shipped with your HP Netserver AA Solution kit.
For Customer Support Refer to the Warranty & Support for Your HP NetServer booklet supplied with your NetServer for information relating to warranty or customer support.
xviii HP Netserver AA Solution Administrator’s Guide
Introduction 1 This chapter describes the Endurance server, the server with ComputeThru TM technology that enables the server to continue computing even when system components fail. This chapter provides a conceptual overview of the Endurance server, introduces Endurance terminology, and describes the components of an Endurance server. This chapter contains the following sections: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Endurance Components . . . . . . . . . . . . . . .
Introduction The HP Netserver AA Solution Endurance server is a fault tolerant Microsoft Windows server that provides Constant Computing TM, mirrored data storage, and uninterrupted network access. The Endurance server uses the Microsoft Windows operating system and Marathon’s patented technology to offer a fault tolerant server that runs Windows-compatible applications.
Table 1-1 Endurance Server Benefits Benefit Description Redundant, fault tolerant processing and I/O subsystem The Endurance server uses redundant hardware and Endurance software to ensure that your server remains operational even in the event of a failed processor, a memory failure, an I/O failure (even those associated with I/O controllers), a disk drive failure, or a failed Ethernet adapter.
Table 1-1 Endurance Server Benefits (Continued) Benefit Description Automatic reconfiguration When a fault condition occurs, or after that fault is corrected and the failed component is returned to service, the Endurance server automatically reconfigures and, if needed, synchronizes the components affected by the fault. This can include CPU processing, including CPU memory; the server’s operating system and associated applications; and any system data, including data stored on mirrored devices.
Endurance Components Figure 1-1 shows the Endurance components. Table 1-2 describes each component in detail. The Endurance server hardware requirements are described in Chapter 2 in the HP Netserver AA Solution Installation Guide. Other Endurance terms and industry-standard terms are described in the Glossary.
Table 1-2 Endurance Components Endurance Server Contains . . . Component Description CE Each CE (Compute Element) is a Pentium class system that includes a motherboard, video adapter, a MIC (Marathon Interface Card), and two processors. The processors on the CE provide the compute processing for the Endurance server. 2 ESI The Endurance System Interconnect (ESI) is a conceptual term used to describe the fiber paths that connect the IOPs to the CEs.
Endurance Server Overview The Endurance server operates as a standard Windows server while offering a complete fault tolerant operating environment. Because of this, the Endurance server supports any off-theshelf and custom applications that are compatible with Windows without requiring any scripts or API support. To achieve full redundancy and fault tolerance, the Endurance server integrates four industrystandard Pentium-based systems with Marathon’s hardware and software.
Endurance Server Hardware Configuration With four systems integrated into a single Windows fault tolerant server, as shown in Figure 1-1, the Endurance server provides complete hardware redundancy. Because the Endurance server uses redundant hardware, its hardware availability far surpasses that of a standard Windows server. Using redundant hardware also allows online service and replacement of Endurance hardware.
Endurance Software Endurance software integrates and synchronizes processing across four industry-standard Pentium class systems. All components are capable of multiprocessing, forming a logical, fully redundant, fault tolerant server. This results in the Windows operating system, all applications, and the local area network logically perceiving the integrated systems in the Endurance server as a standard Windows server.
Endurance software also includes the following: • Automatic disk mirroring. This ensures that data on mirrored SCSI disks are automatically maintained, and that data on mirrored disks are accurate and current. • Redundant network connectivity. The Endurance server uses redundant network connections (up to four on each IOP). The Endurance software detects any physical network adapter or connectivity failures.
Endurance Overview 2 This chapter provides an overview of the Endurance server, including the boot process and state information. This chapter assumes that you are familiar with the Endurance terminology described in the Introduction and the Glossary. This chapter includes the following sections: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Virtual Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Redirected Video and the CE Desktop Application . . . . . . . .
Overview The Endurance server is a fully redundant, fault tolerant server that provides continuous computing and redundant I/O devices for your Windows server and its applications. You can monitor and manage your Endurance server using Endurance Manager, a GUI-based Endurance management application. Using Endurance Manager, you can: • View the status of an Endurance server and its components. This includes the CEs, IOPs, MICs, interconnects, and all redirected devices.
• Each IOP requires a licensed copy of the Windows operating system that should be accessed only to perform maintenance procedures. In addition to the concepts described in Chapter 1, the Endurance fault tolerant technology coordinates all I/O requests and responses between the CEs and IOPs using the ESIs and the IL, as shown in Figure 2-1. • • In the Endurance server, the ESIs (Endurance System Interconnects) provide the interconnect paths for all Endurance server I/O requests and responses.
Virtual Network In addition to the networking described above, the Endurance server includes a virtual network that provides LAN-style connectivity between the CE’s operating system and each IOP’s operating system. This connectivity is independent of any public (redirected) or private (IOP) network adapters. Within this virtual network, the IOPs and CE appear as three interconnected nodes, as shown in Figure 2-2.
Network transports are bound to VNR and VNP just as they would be bound to any standard Network Interface Card. Ethernet addresses for all virtual adapters are automatically assigned and are based on the Endurance Ethernet Vendor ID. For information on the installation of the virtual network, see software installation procedures in Chapter 3 of the HP Netserver AA Solution Installation Guide.
Redirected Video and the CE Desktop Application In the Endurance server, CE video output is redirected to the IOPs. To accomplish this video redirection, the Endurance server uses several kernel mode drivers and the CE Desktop application, which is similar to industry-standard remote control applications. The CE Desktop application is a standard Windows GUI application.
Endurance Boot Process When the IOPs and CEs in an Endurance server are powered on, they automatically start a boot process that results in loading both the Windows operating system and the Endurance software. When powered on, the IOPs pass power-on self test (POST) and load the Windows operating system and the Endurance software. The IOP boot process must complete for the CEs to begin their boot process.
After the IOPs complete their boot process, the CEs boot: one CE loads the Windows operating system; then the other CE is synchronized so that both CEs perform all CPU and memory functions in a synchronized manner. This ensures that in the event of a CPU or memory failure, the Endurance server’s operating system provides continuous computing without any loss of context. After the CE boot process completes, the Endurance server is available for use.
CEx CEy Powered on and completes POST Powered on and completes POST CE issues boot request. CE issues boot request. IOP services boot request. IOP servicing boot redirects its keyboard to the CE. CE loads Windows and Endurance software. CE has active control of all redirected devices. If IOPs are both present and their disks are not current, a mirror copy starts. CEs synchronize and start executing in lock step.
Endurance Characteristics During the CE Boot Process During the CE boot process, you can use Endurance Manager to view the state transitions of the Endurance server components. Until the CE boot completes, the only redirected keyboard is the one attached to the IOP that is serving the boot request. During CE boot, if you must access the CE (for example, to select a multi-boot option): • Use the keyboard on the IOP that is servicing the boot request.
IOP Multi-Boot Options During the IOP boot process, the IOP multi-boot options for the Windows operating system are displayed on the boot loader menu. These options allow you to choose the system root that you want to use. Note: Do not boot your IOP in any mode other than Operational Endurance I/O Processor Mode without explicit instructions from your service provider or without following the information described in the Endurance documentation.
Endurance Component States The Endurance server components can report any of the following states, depending on their status: • Server States • CE Operating System States • CE States • IOP States • Interconnect States • MIC Port State Display Lights • Mirrored Disk States • Network Connection States • Keyboard/Pointer States • Other Endurance Component States Note: 2-12 You can use the Endurance Manager to view the current state of any component in the Endurance server.
Server States The server states are: Table 2-2 Server States State Description Offline Indicates that none of the IOPs or CEs in the Endurance server are active. Online Indicates that one IOP or CE is ready, but none are active. Active Indicates that at least one CE and IOP is active. CE Operating System States The CE operating system states are: Table 2-3 CE Operating System States State Description Offline Indicates that the Windows operating system is neither running nor booting on either CE.
CE States The CE states are: Table 2-4 CE States State Description Offline Indicates that the CE is not available for use in the server. The CE is typically in this state when it is powered down or if it cannot communicate with an IOP because the ESI between the CE and IOP is not usable. Ready Indicates that the CE is powered up and has established communications with an IOP. After this state, the CE transitions to either Booting or Sync-Slave (where CE synchronization is performed).
IOP States The IOP states are: Table 2-5 IOP States State Description Offline Indicates that the IOP is not available for use in the server. The IOP is typically in this state if it is powered down or if it cannot communicate with other IOPs because the Interconnects between the IOP and the Endurance server are not usable. Ready Indicates that the IOP is ready to become an active member of the server configuration. The IOP remains in this state until it joins with another IOP, or until it boots the CE.
Interconnect States There are two types of Interconnects: an IL (IOP link) that connects one IOP to the other IOP, and an ESI (Endurance System Interconnect) that connects an IOP to a CE. The IL cables provide a path for communicating system states and status information. This path also provides the mirror copy data path. The Interconnect states are: Table 2-6 Interconnect States State Description Offline Indicates that the Interconnect is not in use by the server but is available for use.
MIC Port State Display Lights Each IOP collects and displays the status of its local MIC ports along with the status of the CE MIC ports connected through the fiber. CE status is relayed to the IOP with the assistance of MIC firmware; therefore, the CE port status is only available after the CE MIC BIOS has set its ports to a software-enabled state. The following table explains the MIC port state lights displayed on the MIC’s graphical display in the Endurance Manager window.
Mirrored Disk States The mirrored disk states are: Table 2-8 Mirrored Disk States State Description Online Indicates that a disk is available for use or is currently in use by the CE operating system. As a mirror copy begins, a mirror copy target transitions from offline to online and remains online when the mirror copy completes successfully.
Table 2-8 Mirrored Disk States (Continued) State Description Faulted Indicates a disk failed a read or write request after repeated retries. The disk is not available for use by the CE operating system. You can use Endurance Manager to re-enable a disk that has experienced unrecovered failures and return it to service. You do not need to reboot the IOP to bring the disk back online. An ensuing mirror copy to the disk may correct bad spots present on the failed disk.
Network Connection States The network connection states are: Table 2-9 Network Connection States State Description Online Indicates that the Ethernet adapter and its associated network connection is active in the Endurance server configuration. The Endurance Manager Administration Window (Chapter 4) uses color to indicate whether the adapter is either primary or standby. • Primary indicates that the adapter is responsible for all transmits and receives.
Keyboard/Pointer States The keyboard and pointer states are: Table 2-10 Keyboard/Pointer States State Description Online Both the keyboard and pointer are available to the Endurance server. Faulted The keyboard or pointer is not available to the entire Endurance server configuration. In some cases (for example, failed keyboard or pointer), the input device is not available to either the IOP or CE.
Monitoring the Endurance Server Because the Endurance server is fault tolerant, when a fault occurs (for example, a failed disk), the Endurance server continues operating. However, even though it is operating, it may be vulnerable. This means that any failure to the faulted component’s redundant counterpart affects the availability of the Endurance server. Because of this, you need to monitor the status of the components in your Endurance server and correct any faults.
Endurance Messages When it is operational, Endurance software continuously monitors the Endurance server. It reports status and error messages by logging most Endurance messages in the Windows event log. Endurance software displays some messages as they occur, either directly on the Windows blue screens during the text phase of boot or when a CE is being deconfigured; in pop-up windows; and for messages that pertain to the monitoring of the server, in a window on the Endurance Manager GUI.
Table 2-13 Event Log Icons and Message Severity Levels Severity Level Informational Description Informational messages are the least severe and do not require action. Examples of informational messages include: Warning • Reporting benign state changes • Reporting commands as they are issued • Reporting completion status of user-initiated processes Warning messages may require attention. A continued series of warning messages merits review to see if corrective action is required.
Redirected Video and the CE Desktop Application 3 This chapter describes redirected video and the CE Desktop application, a Windows application that runs on the Endurance server IOPs and displays the CE video output on the IOPs. This chapter assumes that you are familiar with the Endurance terminology described in Chapter 1 and the Glossary. This chapter includes the following sections: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 CE Video During Boot . . . . . . . . . . . .
Overview In the Endurance server, CE video output is redirected for display on the IOPs. To accomplish this redirection, the Endurance server uses several kernel mode drivers and the CE Desktop application, whose user interface is similar to industry-standard remote control applications. The CE Desktop application is a standard Windows GUI application. It runs on the IOPs and displays CE video output in a window on the IOPs. To display CE video, you must run the CE Desktop application.
CE Video During Boot The CE Desktop application displays output from the CE that occurs after the CE passes POST and the text phase of the Windows boot process.
Redirected Video Components This section describes the redirected video components used in the Endurance server. The kernel mode components of redirected video include software that runs on the IOP and on the CE. Software Running on the IOPs • MtcVidP.sys — the Video Provider • MtcVideo.exe — the CE Desktop application The Video Provider on each IOP communicates with the Video Redirector. It receives information from the Video Redirector that is used for displaying the CE video on both IOPs.
CE Video Drivers When the Video Redirector and Display Driver are loaded, they disable the CE video adapter. You cannot disable the Endurance video drivers or substitute other drivers. CE and IOP Video Modes In the IOPs, you should use video cards that support resolutions of at least 1024 X 768 and also support more than 256 colors. The CE color palette is always set to 256 colors. You should run the IOPs at least one setting above 256 colors.
Video Recommendations The following sections provide recommendations for the most efficient use of system resources. Some Remote Control Applications Not Supported on the CE The Endurance server does not support the use of remote control applications on the CEs that replace the Endurance video drivers with their own drivers. The Endurance video drivers are required for CE synchronization.
Using the CE Desktop Application This section describes how to launch and use the CE Desktop application. Before you launch the CE Desktop application, set the color palette for the IOPs to a minimum of one setting above 256 colors. To set the number of colors: 1. From the Task Bar, select Start Settings Control Panel Display. 2. Select the Settings tab. 3. In the Color Palette box, select the number of colors from the list box.
Running the CE Desktop Application The first time that you access the application, it runs in a window. After that, you can run the CE Desktop application either in a window or in full-screen mode.
When the application is running in full-screen mode and you want to run the application in a window: 1. Change the input focus to the IOP. See Changing Input Focus on page 3-9. 2. Click the CE Desktop icon on the title bar. 3. Uncheck the Full Screen Mode option. If the CE is running at a lower resolution than the IOP, then the entire CE desktop can be resized so that it is visible without scroll bars.
Setting Video Resolution and Refresh Frequency The CE desktop default resolution is 640 x 480 pixels. You can change this setting using the Display application in the Control Panel window. If necessary, change the resolution in the Desktop Area on the Settings page. The lower you set the resolution, the less system resources Endurance redirected video uses.
Endurance Manager 4 This chapter describes the Endurance Manager, the Endurance server management application. This chapter assumes that you are familiar with the Endurance terminology described in Chapter 1 and the Glossary. This chapter includes the following sections: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Starting the Endurance Manager . . . . . . . . . . . . . . . . . . 4-3 Endurance Manager Window . . . . . . . . . . . . . . . . . . . .
Overview The Endurance Manager is a complete management tool for your Endurance server. Endurance Manager is a standard Windows application that enables you to: • View the status of any Endurance server and its components. This includes the Endurance server, and Endurance CEs, IOPs, interconnects, keyboards, pointers, redirected devices, and Ethernet connections. • Issue commands to manage the Endurance server and its components, including enabling and disabling server components.
Starting the Endurance Manager You can run Endurance Manager on a CE, an IOP, or a remote workstation. Use the Windows Start menu to start the Endurance Manager. Select Start Programs Marathon Endurance Endurance Manager. You can also create a desktop shortcut icon to the Endurance Manager or place an Endurance Manager shortcut in your startup group.
Endurance Manager Window When you start the application, the Endurance Manager main window opens and displays the current status of your Endurance server. A typical Endurance Manager view of a fully operational Endurance server is shown in Figure 4-1 and is described in Table 4-1. Your display includes the name of the product running on the server shown in the Server window. In the following example, an Endurance 6200 server is being monitored.
Table 4-1 Endurance Manager Main Window Contents Window Item Description Title Bar Displays the type of system and product. Menu Bar Contains Endurance Manager menu options described in Menu Options (page 4-20). Administration Window Displays a graphical representation of the Endurance server that you can use to administer your Endurance server (page 4-7). All hardware devices and connections are displayed, as is the video icon that launches the CE Desktop application.
Table 4-1 Endurance Manager Main Window Contents (Continued) Window Item Description Last Mirror Copy Status Window Displays information about the mirror copy status for your Endurance server (page 4-14).
Administration Window The Administration window is located in the Endurance Manager main window (Figure 4-1). It provides a graphical representation of the Endurance server. You can use this Endurance Manager feature to: • View current status information about your Endurance server and its components. • Access commands for a specific Endurance server component. • Determine which IOP is providing Endurance server status information to the Endurance Manager.
An example of the Administration window and how it displays Endurance server state and status information is shown in Figure 4-2 and described in Table 4-2. The colors displayed in the Administration window indicate component status using the colors described in Table 4-3.
Table 4-2 Administration Window Contents Component Description CE1 and CE2 Indicates the status of a CE. MIC LEDs Indicates the status of the MIC associated with the LEDs. ESI Indicator Indicates the status of the ESIs (Endurance System Interconnects) that collectively report the status of connections to the various components. IOP1 and IOP2 Indicates the status of an IOP. IL Indicator Indicates the status of the IL (IOP Link).
Table 4-2 Administration Window Contents (Continued) Component Description Redirected Devices Indicates the status of the redirected devices that are defined in the Endurance server configuration (Chapter 6). The redirected device types are described below. The icon for a redirected device type is displayed only if one or more devices of that type are redirected. For example, the serial port icon is displayed only if a serial port is redirected.
Table 4-3 Endurance Manager Color Interpretation Color Component Indicates...
Device Status Window The Device Status window displays the current status of the components in the Endurance server. The Device Status window is shown in Figure 4-3 and described in Table 4-4. To control how this window displays, use the Endurance Manager options described in Table 4-5.
Table 4-4 Device Status Windows Contents Field Description Component Identifies the name of the component. To the left of the component name, a box indicates the component’s status using the colors described on page 4-11. Status Indicates the component’s state. For component state information, refer to Chapter 2. Table 4-5 Endurance Manager Options Affecting the Device Status Window Option Description View Configures whether the Device Status window is displayed.
Last Mirror Copy Status Window The Last Mirror Copy Status window displays mirror copy status information for the Endurance server. The Last Mirror Copy Status window is shown in Figure 4-4, and is described in Table 4-6. To control how this window displays, use the Endurance Manager options described in Table 4-7. Because this window displays the last mirror copy status as seen by a particular IOP, it is possible for the IOPs to return last mirror copy status reports that appear somewhat different.
Table 4-6 Last Mirror Copy Status Window Contents (Continued) Option Description Pending Mirror copy is waiting to start. Note: A mirror copy target disk is offline while a mirror copy is pending. It transitions to online as the mirror copy begins. IOP1 Started Mirror copy is in progress. Unable A disk was located, but it cannot participate in a mirror copy. For example, it may be faulted or it may have been explicitly disabled. Unknown State of the disk cannot be determined.
Display and Control Window The Display and Control window displays the commands, options, and parameters that enable you to manage and display information about your Endurance server. Note: For Endurance server command information, refer to Chapter 5. You can access the Display and Control window by: • Choosing Tools Display and Control from the Endurance Manager menu bar. By default, this enables you to manage all components of the Endurance server.
Table 4-8 Display and Control Window Options Option Description Command Description When a command is selected, this area displays a brief description of the command. Filters Applies a filter to Target. The filter is applied when the checkbox for a command is not displayed. The filters shown are: • Devices -- affects whether keyboard, SCSI disk, Ethernet, and tape commands are displayed in Target. • Elements -- affects whether CE, IOP, and ESI commands are displayed in Target.
Options Window The Options window configures the Endurance Manager monitoring parameters. The Options window is shown Figure 4-6, and is described in Table 4-9.
Table 4-9 Options Window Parameters Parameter Description Time in seconds to automatically poll for the system status Specifies the interval to poll and update Endurance server state and status information. The default is 5 seconds. If this field is blank or 0, Endurance Manager does not perform an automatic update. Time in seconds to automatically re-execute Show commands Specifies the interval to update any open Show command windows. The default is 3 seconds.
Menu Options The Endurance Manager window contains the following menu options: • File Menu • View Menu • Tools Menu • Help Menu File Menu The File menu contains the Exit option. Use this option to exit Endurance Manager.
View Menu The View menu contains the options described in Table 4-10. Table 4-10 View Menu Options Option Description Device Status Determines whether device status is displayed. If a checkmark is displayed by this option, the Device Status window is displayed. Mirror Copy Status Determines whether mirror copy status is displayed. If a checkmark is displayed by this option, the Mirror Copy Status window is displayed.
Tools Menu The Tools menu displays the options described in Table 4-11. Table 4-11 Tools Menu Options Option Description Display and Control Opens the Display and Control Window. This dialog box enables you to execute commands to monitor and manage your Endurance server. The Display and Control window is described on page 4-16. Endurance Configuration Utility Starts the Endurance Configuration Utility. Refer to Chapter 6 or the Endurance Configuration Utility’s online help for information.
Help Menu The Help menu displays the options described in Table 4-12. Table 4-12 Help Menu Options Option Description Contents Displays the contents page for the Endurance online help. About Endurance Manager Displays version and copyright information for your Endurance Manager software.
Using Endurance Manager on a Remote Workstation You can use Endurance Manager on a remote workstation to monitor and administer your Endurance server. To do so, connect Endurance Manager on a remote workstation to the Endurance server using either a local area network or a modem. For installation instructions, refer to Chapter 3 of the HP Netserver AA Solution Installation Guide.
Security Features for Remote Use of Endurance Manager Security features within Endurance Manager provide • Protection against Endurance software installation from an unprivileged account. Endurance Setup requires Administrator privileges. If a user account without Administrator privileges attempts to install the Endurance software, the following error message is displayed, and the operation fails. Insufficient privilege for attempted operation. Endurance Setup requires ADMIN privilege.
Commands 5 This chapter describes Endurance server commands. It assumes that you are familiar with Endurance terminology described in Chapter 1 and the Glossary. This chapter documents the Endurance server commands in alphabetical order in the following sections: Issuing Endurance Commands . . . . . . . . . . . . . . . . . . . 5-3 Verifying Endurance Commands . . . . . . . . . . . . . . . . . . 5-4 Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 CE1 or CE2 Commands CE_O/S Shutdown .
Management Show Computer Information Server Shutdown Commands Tuple Commands 5-2 . . . . . . . . . . . . 5-78 . . . . . . . . . . . . . . . . . . . 5-79 . . . . . . . . . . . . . . . . . . . . . . . . .
Issuing Endurance Commands You can issue the Endurance commands using either: • Endurance Manager – the command syntax for this method is documented in the Command section of each command. • MTCCONS (the Endurance Manager Console) – the command syntax for this method is documented in the Console Syntax section of each command. Refer to page 7-16 for MTCCONS information, including a description of the MTCCONS parameters.
Verifying Endurance Commands After issuing an Endurance command, you can verify that it executed successfully by completing one of the following. • Use the Endurance Manager to make sure that the status of the Endurance server component matches the state that you expected. • Use the Endurance Manager to issue an IOPn.Monitor Show Configuration command (5-69) from either IOP to make sure that the component reflects the appropriate state.
Command Summary Table 5-2 lists all Endurance commands in alphabetical order.
Table 5-2 Endurance Commands (Continued) Command Page IOPn.Diskx Reset Endurance Sector 5-32 IOPn.Diskx Reset Mirror Copy 5-33 IOPn.Dsl Show Configuration 5-34 IOPn.Ethernetx Disable Operation 5-35 IOPn.Ethernetx Enable Operation 5-36 IOPn.Ethernetx Reset Port Counters 5-36 IOPn.Ethernetx Show Port Counters 5-37 IOPn.Ethernetx Show Port Information 5-39 IOPn.EthernetProvider Reset Provider Counters 5-41 IOPn.EthernetProvider Show Parameter Values 5-41 IOPn.
Table 5-2 Endurance Commands (Continued) Command Page IOPn.InputProvider Show Counters 5-54 IOPn.InputProvider Show Hotkey 5-55 IOPn.InputProvider Show Hotkey Value 5-55 IOPn.InputProvider Show Input Device States 5-56 IOPn.InputProvider Show LED Flashing 5-58 IOPn.LinkDriver Reset Port Counters 5-59 IOPn.LinkDriver Show Parameter Values 5-59 IOPn.LinkDriver Show Port Counters 5-61 IOPn.LinkDriver Show Port Information 5-63 IOPn.Monitor Disable Auto Start 5-65 IOPn.
Table 5-2 Endurance Commands (Continued) Command Page Tuple Enable Operation 5-83 Tuple Shutdown Operation 5-84 5-8 HP Netserver AA Solution Administrator’s Guide
CE1 or CE2 Commands The CE1 or CE2 commands perform operations on the CE. Table 5-3 lists the CE1 or CE2 commands.
CE Disable Auto Boot This command disables Auto Boot for a specific CE. Auto Boot allows the CE to automatically boot the CE’s Windows operating system after a reboot or power cycle. If you disable Auto Boot, the operating system cannot be booted on this CE until you issue a CE Enable Auto Boot command. If you are setting this option to prevent a CE from joining the Endurance server configuration, make sure that you disable both Auto Boot and Auto Synch (page 5-11) on that CE.
CE Disable Auto Synch This command disables Auto Synch for a specific CE. Auto Synch allows the second CE to automatically attempt to synchronize with the running CE. If you disable Auto Synch, you cannot synchronize that CE into the Endurance server until you issue a CE Enable Auto Synch command. If you are setting this option to prevent a CE from joining the Endurance server configuration, make sure that you disable both Auto Boot (page 5-10) and Auto Synch on that CE.
CE Disable Operation This command disables (removes) the specified CE from the active Endurance server configuration. For the CE to rejoin the Endurance server, you must enable it using the CE Enable Operation command. Warning: This command does not perform a normal Windows operating system shutdown. As a result, you can lose any data in the Windows disk cache that has not been written to disk. Therefore, if only one CE is in operation, use a Windows Shutdown command instead.
CE Enable Auto Boot This command enables Auto Boot for a specific CE. Auto Boot allows the CE to automatically boot the CE’s Windows operating system after a reboot or power cycle. By default, Auto Boot is true (enabled).
CE Enable Operation This command enables a faulted or disabled CE, allowing it to join the active Endurance server. Command CEn Enable Operation From IOPx Console Syntax MTCCONS CEn Enable Operation From IOPx Variables n – the ID number of the CE (1 or 2) x – the ID number of the IOP (1 or 2) To verify that CEn has been enabled, either: Results See Also • Issue an IOPx Show Configuration command from either IOP to make sure that the CE and any associated components (such as CEn.
Results Check the Windows Event Viewer for a message that indicates that the CE has been shut down, disabled, or removed from service. See Also CE Disable Auto Boot CE Disable Auto Synch CE Disable Operation CE Enable Operation CE Show Auto Boot This command shows the state of the Auto Boot parameter for a specific CE. Auto Boot allows the CE to automatically boot the CE’s Windows operating system after a reboot or power cycle. By default, Auto Boot is true (enabled).
CE Show Auto Synch This command shows the state of the Auto Synch parameter for a specific CE. Auto Synch allows the CE to automatically synchronize with the other CE after a reboot. If you disable Auto Synch, you cannot synchronize that CE until you issue a CE Enable Auto Synch command. By default, Auto Synch is true (enabled).
Table 5-4 CE Parameters Value Meaning Auto Boot Displays the state of the Auto Boot parameter as either: true (enabled) or false (disabled). Auto Synch Displays the state of the Auto Synch parameter as either: true (enabled) or false (disabled).
CE_O/S Shutdown This command performs a shutdown on the CE operating system. Command CE_O/S Shutdown Operation From IOPx Console Syntax MTCCONS CE_O/S Shutdown Operation From IOPx Variables x – the ID number of the IOP (1 or 2) Results The monitor on the specified IOP issues a request to the CE Endurance System Management service to shut down the operating system. The CE Endurance System Management service initiates the system shutdown.
ESI Enable Operation This command enables a faulted ESI (Endurance System Interconnect). Command ESIn Enable Operation From IOPx Console Syntax MTCCONS ESIn Enable Operation From IOPx Variables n – the ESI’s ID number: Table 5-5 ESI Data Paths ESI ID Number Data Path Between . . . 11 IOP1 and CE1 12 IOP1 and CE2 21 IOP2 and CE1 22 IOP2 and CE2 x – the ID number of the IOP (1 or 2) Results Check the Windows Event Viewer on the CE for the following message: IOPx.
IL12 Enable Operation This command enables the IL (IOP Link) when it is faulted. Command IL12 Enable Operation From IOPx Console Syntax MTCCONS IL12 Enable Operation From IOPx Variables x – the ID number of the IOP (1 or 2) Results Check any of the following: • the Endurance Manager Main Window • the Endurance Manager Device Status Windows • the Windows Event Viewer on the CE for the message: IOPx.MtcMon status: ILn has been enabled by operator request.
IOP1 and IOP2 Commands The IOP1 and IOP2 commands perform operations on the IOPs. Table 5-6 lists the IOP1 and IOP2 commands. Table 5-6 IOP1 and IOP2 Commands Command Page IOP Disable Operation 5-21 IOP Enable Operation 5-22 IOP Shutdown Operation 5-23 IOP Disable Operation This command disables (removes) the specified IOP from the active Endurance server configuration. You can use this command to start a maintenance procedure described in Chapter 9.
Results See Also To verify that IOPn has been disabled, either: • Check the Windows Event Viewer for a message that indicates that IOP has been shut down, disabled, or removed from service. • Issue an IOP Show Configuration command on the CE. Then verify that IOPn is disabled and any associated components (such as IOPn.MIC) are offline. IOP Enable Operation IOP Shutdown Operation IOPn.Monitor Show Configuration IOP Enable Operation This command enables the specified IOP that was disabled or faulted.
IOP Shutdown Operation This command removes the specified IOP from the Endurance configuration, shuts down the IOP, and automatically reboots it. When it reboots, the IOP rejoins the Endurance server configuration. If you do not want the IOP to rejoin, power it off or use the IOP Disable command.
IOPn.DatagramService Commands The IOPn.DatagramService commands control and return statistics for adapters that are bound to the Endurance Datagram Service (DGS). Adapters are bound to DGS during Endurance software installation. Table 5-7 lists the IOPn.DatagramService commands. Table 5-7 IOPn.DatagramService Commands Command Page IOPn.DatagramService Reset Port Counters 5-24 IOPn.DatagramService Show Parameter Values 5-24 IOPn.DatagramService Show Port Counters 5-25 IOPn.
Results Table 5-8 DatagramService Parameter Values Value Meaning Number of Bound Adapters Number of adapters bound to the Datagram service (MtcDgs) Number of Open Adapters Number of adapters opened by the Datagram service (MtcDgs) Maximum Transmit Retries Maximum number of retransmits on reset errors NDIS Packet Pool Size for Send Size of NDIS_PACKET pools for sends NDIS Packet Pool Size for Receive Size of NDIS_PACKET pools for receives IOPn.
Results Table 5-9 DatagramService Port Counters Value Meaning Network Binding Name CurrentControlSet\Service\MtcDgs\Linkage Bind value Datagrams Transmitted Number of datagrams transmitted Datagrams Retransmitted Number of datagrams retransmitted Datagrams Received Number of datagrams received Invalid Ethernet Packets Received Number of invalid Ethernet packets received NDIS Packets Unavailable for Send Number of times NDIS_PACKET for send could not be allocated NDIS Buffers Unavailable for S
IOPn.DatagramService Show Port Information This command returns port information about devices that are bound to the Endurance Datagram Service (DGS) on the specified IOP. Command IOPn.DatagramService Show Port Information Console Syntax MTCCONS IOPn.DatagramService Show Port Information Variables n – the ID number of the IOP (1 or 2) Results Table 5-10 DatagramService Port Information Value Meaning Vendor Description The manufacturer data reported directly from the card.
IOPn.Diskx Commands The IOPn.Diskx commands operate on mirrored SCSI disks and apply to mirror copying, mirror disk availability, and bad block remapping operations. Table 5-11 lists the IOPn.Diskx commands. Table 5-11 IOPn.Diskx Commands Command Page IOPn.Diskx Disable Bad Block Remap 5-28 IOPn.Diskx Disable Mirrored Disk 5-29 IOPn.Diskx Enable Bad Block Remap 5-30 IOPn.Diskx Enable Mirrored Disk 5-31 IOPn.Diskx Reset Endurance Sector 5-32 IOPn.Diskx Reset Mirror Copy 5-33 IOPn.
Results If bad block remapping is turned on, but later you determine that automatic bad block remapping is not desirable, invoke this command to stop the SCSI software from automatically remapping bad blocks for a device. It is possible that bad block remapping might cause file system information loss to occur, depending on whether the sector in which the bad block was encountered is in use by your file system.
IOPn.Diskx Enable Bad Block Remap Warning: Read all instructions in this section before using this command. Bad block remapping can be used to replace disk sectors containing bad spots with undamaged sectors during a mirror copy. It is possible that bad block remapping might cause file system information loss to occur, depending on whether the sector in which the bad block was encountered is in use by your file system.
IOPn.Diskx Enable Mirrored Disk Warning: Using this command may cause a mirror set copy. Read all instructions in this section before using this command. This command attempts to enable a mirrored SCSI disk, indicated by Diskx, that is disabled or faulted. The disk is enabled without having to reboot the IOP under most circumstances. A disk is faulted when it cannot respond to a read or write request. The disk’s failure to respond to a read or write request may be transient or permanent.
IOPn.Diskx Reset Endurance Sector Warning: Using this command may cause a mirror set copy. Read all instructions in this section before continuing. This command is used to: • Reset an Endurance sector on an improperly created replacement disk • Correct problems with the data in the Endurance sector on a mirrored disk If a disk’s state is offline for no apparent reason, and it is not the target of a mirror set copy, check the event log for messages indicating invalid data on the Endurance sector.
IOPn.Diskx Reset Mirror Copy This command attempts to restart a mirror copy for a device, indicated by Diskx. This command usually is issued to restart a mirror copy that has failed because the mirror copy source disk encountered bad blocks. Typically you would enable bad block remapping immediately prior to this call. This command can also be used if you want to restart a failed mirror copy without first enabling bad block remapping.
IOPn.Dsl Show Configuration This command shows device state information for the local and remote IOP. The remote IOP information is valid only when the CE’s operating system is running and both IOPs are active. Command IOPn.Dsl Show Configuration Console Syntax MTCCONS IOPn.Dsl Show Configuration Variables n – the ID number of the IOP (1 or 2) Results See Also 5-34 The device states that are displayed in the main window of the Endurance Manager.
IOPn.Ethernetx Commands The IOPn.Ethernetx commands perform operations on Ethernet adapters. step Table 5-12 lists the IOPn.Ethernetx commands. Table 5-12 IOPn.Ethernetx Commands Command Page IOPn.Ethernetx Disable Operation 5-35 IOPn.Ethernetx Enable Operation 5-36 IOPn.Ethernetx Reset Port Counters 5-36 IOPn.Ethernetx Show Port Counters 5-37 IOPn.Ethernetx Show Port Information 5-39 IOPn.Ethernetx Disable Operation This command disables an Ethernet adapter.
IOPn.Ethernetx Enable Operation This command enables an Ethernet adapter that was disabled. Note: For information on enabling a faulted Ethernet adapter, refer to Chapter 9. Command IOPn.Ethernetx Enable Operation Console Syntax MTCCONS IOPn.ETHERNETx Enable Operation Variables n – the ID number of the IOP (1 or 2) x – the ID number of the Ethernet adapter Results Check the Windows Event Viewer on the CE for the following message: IOPn.
IOPn.Ethernetx Show Port Counters This command displays the Ethernet Provider counters for the specified Ethernet adapter. Command IOPn.Ethernet Show Port Counters Console Syntax MTCCONS IOPn.
Table 5-13 Ethernet Port Counters (Continued) Value Meaning Unsolicited Packets Unavailable Number of times a packet descriptor could not be allocated. Packet descriptors are used to forward Ethernet packets received by the IOPs to the CEs. This does not indicate that incoming Ethernet packets were dropped. The Ethernet Provider buffers some of the network packets until the unsolicited request buffer becomes available. See also the IOPn.EthernetProvider Show Provider Counters command.
IOPn.Ethernetx Show Port Information This command displays port information for the specified Ethernet adapter on IOPn. Command IOPn.Ethernetx Show Port Information Console Syntax MTCCONS IOPn.
Table 5-14 Ethernet Show Port Information Value Meaning Vendor Description The manufacturer data reported directly from the card. Typically, this is the vendor name and model number. Ethernet descriptions are stored in the Windows Registry under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ NetworkCards\X\Description Network Binding Name Name of Ethernet device bound to the Ethernet Provider.
IOPn.EthernetProvider Commands The IOPn.EthernetProvider commands display statistics or reset counters for the Ethernet Provider. Table 5-15 lists the IOPn.EthernetProvider commands. Table 5-15 IOPn.EthernetProvider Commands Command Page IOPn.EthernetProvider Reset Provider Counters 5-41 IOPn.EthernetProvider Show Parameter Values 5-41 IOPn.EthernetProvider Show Provider Counters 5-43 IOPn.EthernetProvider Reset Provider Counters This command resets all counters maintained by the Ethernet Provider.
Results Table 5-16 Ethernet Provider Parameter Values Value Meaning Redirector NDIS Receive Pool Size Redirector NDIS_PACKET and NDIS_BUFFER pool size for receive processing NDIS Packet Pool Size for Send Size of NDIS_PACKET pools for sends NDIS Packet Pool Size for Receive Size of NDIS_PACKET pools for receives NDIS Buffer Pool Size Size of NDIS_BUFFER pool for sends and receives IOP Join Response Interval IOP Join Response Interval in milliseconds Redirector NDIS Receive Pool Size Redirector
Table 5-16 Ethernet Provider Parameter Values (Continued) Value Meaning Transmit Failure Tolerance Number of transmit failures to allow before failing over to the standby adapter Network Watch Factor Interval at which network status counters are checked Network Status Expiration Number of milliseconds for which statistics are considered accurate NDIS Request Timeout Maximum time in milliseconds to wait for a pending NdisRequest or NdisReset to complete Response Buffer Pool Size Maximum size of th
Table 5-17 Ethernet Provider Counters Value Meaning Response Buffers Allocated Number of buffers allocated to receive unsolicited responses. These buffers may be in use or stored on a free queue and are used for Ethernet packets that have been received from the network.
IOPn.EventProvider Commands The IOPn.EventProvider commands configure or display information related to the Event Provider. Table 5-18 lists the IOPn.EventProvider commands. Table 5-18 IOPn.EventProvider Commands Command Page IOPn.EventProvider Remove Events 5-45 IOPn.EventProvider Set Checkpoint 5-45 IOPn.EventProvider Show Dropped Event Statistics 5-46 IOPn.EventProvider Remove Events Warning: Use this command only at the request of your service provider.
IOPn.EventProvider Show Dropped Event Statistics This command displays statistics about events that could not be logged. These statistics are used for diagnostic purposes. Command IOPn.EventProvider Show Dropped Event Statistics Console Syntax MTCCONS IOPn.
IOPn.InputProvider Commands The IOPn.InputProvider commands configure and display the current settings for the Endurance server keyboard and pointer. Table 5-20 lists the IOPn.InputProvider commands. Table 5-20 IOPn.InputProvider Commands Command Page IOPn.InputProvider Disable Automatic Switchover 5-48 IOPn.InputProvider Disable Hotkey 5-48 IOPn.InputProvider Disable LED Flashing 5-49 IOPn.InputProvider Enable Automatic Switchover 5-49 IOPn.InputProvider Enable Hotkey 5-50 IOPn.
IOPn.InputProvider Disable Automatic Switchover This command prevents input devices from automatically switching over from the IOPs to the CEs during CE boot, as described in Endurance Boot Process in Chapter 2. After issuing this command, if you want input devices to switch to the CE (during CE boot), you must manually switch over the input devices, using either the hotkey, the IOPn.InputProvider Set Input Devices IOP command, or the IOPn.InputProvider Set Input Devices CE command.
IOPn.InputProvider Disable LED Flashing This command disables the Scroll Lock LED from flashing the input device status. By default, LED flashing is enabled, and the Scroll Lock LED flashes whenever the input devices are logically connected to the local IOP. Command IOPn.InputProvider Disable LED Flashing Console Syntax MTCCONS IOPn.InputProvider Disable LED Flashing Variables n – the ID number of the IOP (1 or 2) See Also IOPn.InputProvider Enable LED Flashing IOPn.
IOPn.InputProvider Enable Hotkey This command enables hotkeys so that they can be used to toggle input devices between the local IOP and the CEs. By default, using hotkeys is enabled. Command IOPn.InputProvider Enable Hotkey Console Syntax MTCCONS IOPn.InputProvider Enable Hotkey Variables n – the ID number of the IOP (1 or 2) See Also IOPn.InputProvider Disable Hotkey IOPn.InputProvider Show Hotkey IOPn.
Variables n – the ID number of the IOP (1 or 2) x – the timeout value that you want to set. The timeout range is 0 to 300 seconds. If the timeout is 0, arbitration is disabled (default), and input is accepted from both IOPs. See Also IOPn.InputProvider Show Arbitration Timeout IOPn.InputProvider Set Hotkey Value This command defines the hotkey sequence that toggles input devices between the IOP and the CEs. By default, F12 is the hotkey sequence. Command IOPn.
IOPn.InputProvider Set Input Active This command forces the arbitration timeout to expire and switches the active input devices to the specified IOP. For this command to be valid, arbitration timeout must be enabled. (Refer to the IOPn.InputProvider Set Arbitration Timeout command.) Command IOPn.InputProvider Set Input Active Console Syntax MTCCONS IOPn.InputProvider Set Input Active Variables n – the ID number of the IOP (1 or 2) See Also IOPn.InputProvider Set Arbitration Timeout IOPn.
IOPn.InputProvider Show Arbitration Timeout This command displays the input arbitration setting for the Endurance server. When arbitration is enabled, it allows input to be processed from only one tuple at a time (effectively blocking input from the other tuple). At the end of each arbitration interval, input control is available to switch to the first IOP where mouse movement or keyboard activity is detected. The arbitration timeout is displayed as number of seconds. Command IOPn.
See Also IOPn.InputProvider Disable Automatic Switchover IOPn.InputProvider Enable Automatic Switchover IOPn.InputProvider Show Counters This command shows all of the statistics and error counters that are maintained by the Input Provider. Command IOPn.InputProvider Show Counters Console Syntax MTCCONS IOPn.
Table 5-21 InputProvider Counters (Continued) Value Meaning CE mouse input dropped Number of times mouse input was discarded by the CE Max mouse input processed Maximum number of mouse input packets processed at one time IOPn.InputProvider Show Hotkey This command shows the state of hotkey as either true (enabled) or false (disabled). By default, show hotkey is true. Command IOPn.InputProvider Show Hotkey Console Syntax MTCCONS IOPn.
Results See Also IOPn.InputProvider Set Hotkey Value IOPn.InputProvider Show Hotkey IOPn.InputProvider Show Input Device States This command shows the logical location and the states of the input devices and the hotkey value. It also shows the states of user-configurable Input Provider parameters. Command IOPn.InputProvider Show Input Device States Console Syntax MTCCONS IOPn.
Table 5-22 InputProvider Input Device States Value Meaning Input directed to IOP1 When true, input is directed to IOP1. When false, input is directed to CEs. Input directed to IOP2 When true, input is directed to IOP2. When false, input is directed to CEs. CE input devices IOP(s) that are eligible to send input to the CEs. Input device merging When true, input device merging is enabled. LED Flashing When true, the scroll lock LED flashes whenever input devices are directed to the IOP.
IOPn.InputProvider Show LED Flashing This command shows whether LED flashing is true (enabled) or false (disabled). By default, Show LED Flashing is true. When set to true, the Scroll Lock LED flashes when the input devices are logically connected to the local IOP. Command IOPn.InputProvider Show LED Flashing Console Syntax MTCCONS IOPn.InputProvider Show LED Flashing Variables n – the ID number of the IOP (1 or 2) Results See Also IOPn.InputProvider Disable LED Flashing IOPn.
IOPn.LinkDriver Commands The IOPn.LinkDriver commands control and return statistics the Endurance IOP Link (IL). Table 5-23 lists the IOPn.LinkDriver commands. Table 5-23 IOPn.LinkDriver Commands Command Page IOPn.LinkDriver Reset Port Counters 5-59 IOPn.LinkDriver Show Parameter Values 5-59 IOPn.LinkDriver Show Port Counters 5-61 IOPn.LinkDriver Show Port Information 5-63 IOPn.LinkDriver Reset Port Counters This command resets the IL port counter statistics to zero on the specified IOP.
Results Table 5-24 IOP LinkDriver Show Parameter Values Value Meaning Heartbeat Interval Interval in seconds at which heartbeat PDUs are transmitted Circuit Timeout Number of seconds in which a heartbeat or other PDU must be received Maximum Transmit Retries Maximum number of times a Data PDU will be retransmitted Transmit Timeout Number of seconds in which a Data PDU must be acknowledged (ACKed) Send Window Size The maximum send window size for Data PDUs.
IOPn.LinkDriver Show Port Counters This command returns statistics for the IOP Link on the specified IOP. Command IOPn.LinkDriver Show Port Counters Console Syntax MTCCONS IOPn.
Table 5-25 IOP LinkDriver Port Counters (Continued) Value Meaning Receives Out of Sequence Number of Data PDUs received out of sequence. The sequence number received did not agree with the sequence number that was expected.
IOPn.LinkDriver Show Port Information This command returns port information for the IOP Link (IL) on the specified IOP. Command IOPn.LinkDriverShow Port Information Console Syntax MTCCONS IOPn.LinkDriver Show Port Information Variables n – the ID number of the IOP (1 or 2) Results Table 5-26 IOP LinkDriver Show Port Information Value Meaning Vendor Description The manufacturer data reported directly from the card. Typically, this is the vendor name and model number.
Table 5-26 IOP LinkDriver Show Port Information (Continued) Value Meaning Virtual Circuit State Virtual circuit state in hexidecimal Outstanding Data PDUs The number of unacknowledged data PDUs Next Sequence Number Next data PDU sequence number 5-64 HP Netserver AA Solution Administrator’s Guide
IOPn.Monitor Commands The IOPn.Monitor commands perform operations on the monitor. Table 5-27 lists the IOPn.Monitor commands. Table 5-27 IOPn.Monitor Commands Command Page IOPn.Monitor Disable Auto Start 5-65 IOPn.Monitor Enable Auto Start 5-66 IOPn.Monitor Set Initialization Interval 5-66 IOPn.Monitor Show Auto Start 5-67 IOPn.Monitor Show Client Status 5-68 IOPn.Monitor Show Configuration 5-69 IOPn.Monitor Show Initialization Interval 5-70 IOPn.
IOPn.Monitor Enable Auto Start Warning: Changing the setting of Auto Start from its default (disabled) on any IOP invalidates data protection features of the Endurance server. This command enables Auto Start for an IOP. When an IOP reboots, Auto Start allows the specified IOP to automatically join the Endurance server configuration (after the time specified by the initialization interval has elapsed), regardless of whether the other IOP is available. Auto Start is also affected by the IOPn.
Results If the timer expires, check the Windows Event Viewer on the CE for a message that indicates that the IOP is unavailable for initialization. See Also IOPn.Monitor Disable Auto Start IOPn.Monitor Enable Auto Start IOPn.Monitor Show Auto Start IOPn.Monitor Show Initialization Interval IOPn.Monitor Show Parameters IOPn.Monitor Show Auto Start This command displays the Auto Start setting for the specified IOP.
IOPn.Monitor Show Client Status This command displays the status of the clients listed in the ClientList Registry parameter on the specified IOP. If no clients are specified in the client list, the following error message displays: An invalid parameter was provided by the caller. Command IOPn.Monitor Show Client Status Console Syntax MTCCONS IOPn.
IOPn.Monitor Show Configuration This command displays Endurance server components and the parameters that describe the components and their states on the specified IOP. Command IOPn.Monitor Show Configuration Console Syntax MTCCONS IOPn.
IOPn.Monitor Show Initialization Interval This command displays the initialization interval for the specified IOP. The initialization interval is the time period in seconds that the IOP waits to initialize with the other IOP before either or both of the following occur: • Responding to the CE if Auto Start is true (enabled). • An event is generated if the other IOP does not become available and if Auto Start is false (disabled).
Results Table 5-30 MIC Interconnect Status Values Commands Value Meaning Unknown/ Unavailable IOPn cannot determine the status of the specified IOP or CE. Uninitialized The specified IOP or CE has not yet been initialized. Good The specified IOP or CE is working correctly. Failed The specified IOP or CE has failed. Lost Power The specified IOP or CE has lost power. Reset The specified IOP or CE is being reset.
IOPn.Monitor Show Parameters This command displays parameters for IOPn. Command IOPn.Monitor Show Parameters Console Syntax MTCCONS IOPn.Monitor Show Parameters Variables n – the ID number of the IOP (1 or 2) Results Table 5-31 Monitor Parameter Values Value Meaning IOP Initialization in Progress When true, indicates that the IOP is initializing with the other IOP. See IOP States on page 2-15. IOP Joining in Progress When true, indicates that the IOP is joining the active Endurance server.
Table 5-31 Monitor Parameter Values (Continued) Value Meaning CE O/S Shutdown in Progress When true, indicates that the shutdown of the CE operating system is pending. CE Crash Dump in Progress When true, indicates that the CE operating system is in the progress of generating a crash dump. IOP Shutdown in Progress When true, indicates that the shutdown of the IOP operating system is pending. Auto Start Displays the Auto Start value. By default, this is false.
IOPn.ScsiProvider Commands The IOPn.ScsiProvider commands display information about the SCSI Provider. Table 5-32 lists the IOPn.ScsiProvider commands. Table 5-32 IOPn.ScsiProvider Commands Command Page IOPn.ScsiProvider Set Mirror Copy Bias 5-74 IOPn.ScsiProvider Show Bad Block Status 5-75 IOPn.ScsiProvider Show Mirror Copy Bias 5-76 IOPn.ScsiProvider Show Mirror Status 5-77 IOPn.
IOPn.ScsiProvider Show Bad Block Status This command displays the bad block status of all the mirrored disks in the Endurance server, indicating whether the mirrored disks have bad block remapping enabled or disabled. Command IOPn.ScsiProvider Show Bad Block Status Console Syntax MTCCONS IOPn.ScsiProvider Show Bad Block Status Variables n – the ID number of the IOP (1 or 2) Results See Also IOPn.Diskx Disable Bad Block Remap IOPn.
IOPn.ScsiProvider Show Mirror Copy Bias This command shows the setting of the mirror copy bias. Mirror copy bias is set using the IOPn.ScsiProvider Set Mirror Copy Bias command. By default, the mirror copy bias is two. Command IOPn.ScsiProvider Show Mirror Copy Bias Console Syntax MTCCONS IOPn.ScsiProvider Show Mirror Copy Bias x Variables n – the ID number of the IOP (1 or 2) Results See Also 5-76 IOPn.
IOPn.ScsiProvider Show Mirror Status This command displays the mirror status of all the mirrored disks in the Endurance server. The status information includes whether disks are current and whether a mirror copy is pending. Command IOPn.ScsiProvider Show Mirror Status Console Syntax MTCCONS IOPn.
Management Show Computer Information This command shows information about the target system from the Endurance management interface.
Server Shutdown Commands The server shutdown commands shut down the server by first shutting down the CE’s operating system, and then shutting down the operating system on the IOPs. Table 5-33 lists the server shutdown commands.
Server Shutdown Operation This command shuts down the CE’s operating system and then shuts down the operating system on each available IOP. Note: This command is the preferred method for shutting down the Endurance server. Command Server Shutdown Operation From IOPx Console Syntax MTCCONS Server Shutdown Operation From IOPx Variables x – the ID number of the IOP (1 or 2) Results The monitor on the specified IOP initiates a shutdown of the Endurance server.
Server Shutdown Without IOP Reboot This command is used primarily when upgrading or downgrading the Endurance server from one Endurance release to another, or whenever you shut down the server and do not want it to restart immediately. This command shuts down the CE’s operating system and then shuts down the operating system on each available IOP.
Tuple Commands The tuple commands perform operations on a tuple of the Endurance server. Table 5-34 lists the tuple commands. Table 5-34 Tuple Commands Command Page Tuple Disable Operation 5-82 Tuple Enable Operation 5-83 Tuple Shutdown Operation 5-84 Tuple Disable Operation This command disables (removes) the specified tuple from the active Endurance server configuration. When this command is issued, both the CE and IOP in the specified tuple are disabled.
See Also CE Disable Operation CE Enable Operation IOP Disable Operation IOP Enable Operation Tuple Enable Operation Tuple Shutdown Operation Tuple Enable Operation This command enables any faulted or disabled tuple component (IOP and/or CE). After the tuple component is enabled, it can rejoin the Endurance server.
Tuple Shutdown Operation This command removes IOPn and CEn from the Endurance server configuration. If necessary, the CE operating system is shut down, and the IOP operating system is shut down. Both the CE and the IOP attempt to rejoin the Endurance server configuration when they become available. To permanently remove the tuple from the configuration, use the Tuple Disable Operation command.
Configuration Utility 6 This chapter describes the Endurance Configuration Utility. This chapter assumes that you are familiar with the Endurance terminology described in Chapter 1 and the Glossary. This chapter includes the following sections: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Starting the Endurance Configuration Utility Using the Endurance Configuration Utility Configuration Utility . . . . . . . . . . . 6-5 . . . . . . . . . . . .
Introduction The Endurance Configuration Utility enables you to define the Endurance server’s hardware configuration and to store that configuration information in the appropriate locations of the Windows Registry. You can run the Endurance Configuration Utility from an IOP booted in Operational Endurance I/O Processor Mode or Offline Endurance I/O Processor Mode. You cannot run this utility from a CE or a remote workstation.
You can use the icons and buttons in this window to add, remove (delete), and display devices in your configuration. The icons in this window are described in Table 6-1; the buttons are described in Table 6-2. For more detailed information about Endurance Configuration Utility windows and dialog boxes, refer to the utility’s online help. Warning: The configuration information must be identical on both IOPs.
Table 6-2 Endurance Configuration Utility Button Information Button Description Add Adds a new device Remove Removes an existing device. Properties Displays or modify properties for an existing device. Open Current Opens the current configuration in the Registry. Open File Opens a previously saved configuration file. Save As Saves the currently displayed configuration to a file. Commit Stores the current configuration in the Registry, overwriting any existing configuration information.
Starting the Endurance Configuration Utility The Endurance Configuration Utility is distributed on the Endurance CD. When you install Endurance software on an IOP, the Endurance Configuration Utility is installed in the Marathon Endurance program folder. You can start the Endurance Configuration Utility using Endurance Manager or the Windows Start menu. To start the Endurance Configuration Utility: • Using the Windows Start menu, select Start Programs Endurance Endurance Configuration Utility.
Using the Endurance Configuration Utility Using this window, you can: • Add Devices • Display Device Properties • Remove Devices • Commit Configuration Changes Warning: The configuration information must be identical on both IOPs, except for Ethernet addresses. If you add or remove any devices from your configuration, you must make the change on each IOP. Add Devices To add a hardware device: Step Action Notes 1 Click on the icon for the device you want to add.
When you add a SCSI device: Step Action 1 Select the type of device from the list. 2 The device types are: • Non-mirrored on IOP1 • Non-mirrored on IOP2 • Mirrored Select the SCSI device from the list, and/or enter the SCSI address. To specify a SCSI device address for a device that is not currently shown in the list: Use this option only for a device that is not currently present in the system but will be physically added after the IOP is shut down.
Figure 6-2 Sample Endurance Configuration 6-8 HP Netserver AA Solution Administrator’s Guide
Display Device Properties To display or modify the properties of an existing device: Step Action Notes 1 Click on the device. For example, it might be CE.Disk0. 2 Click Properties. The Properties dialog box displays the information for the device. You can modify the properties of an existing device from the Properties dialog box. Refer to the online help for specific device property information.
Remove Devices To remove an existing device: Step Action Notes 1 Click on the device that you want to remove. For example, it might be CE.CDROM1. 2 Click Remove If you are removing a device so that you can redefine its properties, after you complete this step, select Commit, and then add the device again following the instructions in Add Devices on page 6-6. 3 Complete your configuration changes following the steps in Commit Configuration Changes on page 6-13.
Change CE Ethernet Adapters Properties If you need to change information for a CE Ethernet adapter (because you initially entered incorrect information or because you replaced an adapter): Note: This procedure is not required except for a new MAC address, in which case, you must remove the adapter and add it back in. Step Action 1 Select and Remove (delete) the Ethernet adapter that is currently defined. 2 Click Commit.
Recommitting the Change to a Driver for a Redirected Ethernet Adapter On an IOP, after you update the third-party Ethernet driver for a redirected Ethernet adapter, and before you restart Windows, use the Endurance Configuration Utility to recommit the configuration. The Endurance Configuration Utility writes the NetworkAddress Registry value under the Services key for the Ethernet adapter. To recommit the configuration: Step Action Notes 1 Open the Endurance Configuration Utility.
Commit Configuration Changes After you finish making the configuration changes, commit your changes by saving an identical configuration file on both IOPs, except for the Ethernet addresses. Warning: The configuration information must be identical on both IOPs, except the Ethernet addresses. If you add or remove any hardware devices from your configuration, you must make the same change on each IOP.
Step Action 3 If your Endurance server is operational: Notes a. Schedule an appropriate time to remove your Endurance server from service, and reboot the IOPs. b. Issue an Endurance Manager Server Shutdown command. 4 6-14 Reboot each IOP for the new configuration to take effect. The configuration information must be identical on both IOPs, except for the Ethernet addresses, for the Endurance server to operate properly.
Tools and Utilities 7 This chapter describes the Endurance command-based tools that are distributed on the Endurance CD. This chapter assumes that you are familiar with Endurance terminology described in Chapter 1 and the Glossary. This chapter includes the following sections: MIC BIOS Utility . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 MTCFLASH Tool . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7 MTCEINFO Tool . . . . . . . . . . . . . . . . . . . . . . . . . .
MIC BIOS Utility The Endurance server includes a MIC BIOS utility. Once set up, this utility provides automatic MIC adapter initialization, and boot and synchronization of the Windows operating system on the CEs. After it is configured to do so, the MIC BIOS utility also performs extensive diagnostic tests of the MIC. The MIC BIOS utility causes initialization, system boot, and synchronization errors to be displayed on the CE console.
Using the MIC BIOS Setup Utility If your system does not have a monitor attached to the CE, prior to running the MIC BIOS utility to perform tests, you must either attach a monitor to the CE or use a video/keyboard/mouse switch if you installed one. Before using the MIC BIOS utility for testing, you must choose and properly configure all elements you will be examining and testing. You also use the MIC BIOS Setup utility to configure the MIC.
In this screen, press Enter to continue with the MIC Setup screen, shown in Figure 7-2. Figure 7-2 MIC Setup Screen In the MIC Setup screen, make selections about the parameters described in Table 7-1. When the screen displays, the first field is highlighted. To select another field, press the up or down arrows until you highlight the field of choice. To select or change an item, press Enter to cycle among the possible values. You can make one selection per MIC identity setting.
Table 7-1 MIC BIOS Setup Window Parameters (Continued) Parameter Description MIC Connectivity Test Identifies the type of test to run: Connectivity Test Duration • Int-Loop — Internal loopback. Uses the MIC’s internal loopback capability to verify MIC operation in the local system. • Ext-Loop — External loopback. Similar to the internal loopback capability, but requires a fiber connection between the two ports. Consequently, it also verifies the fiber segments and external connectors.
Once the above parameters are chosen and the MIC identity setting is saved, the server displays the MIC Setup Confirmation screen, shown in Figure 7-3. Then the server reboots with the new settings in effect. Figure 7-3 MIC Setup Confirmation Screen The MIC BIOS utility tests the parameters you have chosen and displays messages, warnings, and errors on the local monitor. If a test encounters a fatal error, the BIOS pauses so that you can view the message.
MTCFLASH Tool The MTCFLASH Tool is an MS-DOS application that allows you to upgrade the Endurance MIC firmware, including MIC FPGA code, extended BIOS, and microcode.
Running MTCFLASH Before you run MTCFLASH, note that: • In an Endurance server, all MICs (CE and IOP) must use the same MIC firmware revisions. • After running MTCFLASH, you must reboot the computer that you are updating, either by using the reset button or by powering the machine off and then on again. Warning: Before removing power to any computer, observe all necessary precautions to maintain Endurance server availability.
Table 7-2 Creating the MTC Diskette for Running MTCFlash (Continued) If running MTCFLASH . . . Create the MTC Diskette . . . Notes When installing an Endurance server software upgrade Using the Endurance CD that was shipped as part of your Endurance server upgrade or an Endurance hotfix diskette if one is applicable to this release.
MTCFLASH Syntax and Switch and Option Values To run MTCFLASH, boot the server to DOS and type MTCFLASH switch options at the DOS command prompt (not in a command window under Windows). The MTCFLASH switches and options are listed and described in Table 7-3. The first section of the table lists the switches, and the second section of the table lists the options. Table 7-3 MTCFLASH Tool Switches and Options Switch and Option Variables Description -l Lists the MIC ROM image version information.
Upgrading MIC Firmware with MTCFLASH To upgrade the MIC firmware on each IOP and each CE: Step Action Notes 1 Insert the MTC diskette into the computer’s local floppy drive. You should consider the Endurance hotfixes installed at your site. If you have hotfixes installed, make sure that the version of MTCFLASH coincides with your hotfix level. If you have a hotfix that supersedes what is contained on the MTC diskette you created, use the hotfix diskette to flash the MICs.
MTCEINFO Tool The MTCEINFO tool is a command line application that displays Ethernet adapter information. You can run this tool from any computer to view information about its Ethernet adapters. You may need to access this information to: • Verify that the adapter is operating properly. • Verify that the adapter is receiving network traffic. • Verify the network addresses for all adapters installed in an IOP.
A sample of MTCEINFO summary output follows: MtcEinfo Version 4.0.6-W2.EA Copyright (c) Marathon Technologies Corporation, 1996, 1997-2001.
A partial sample of detailed MTCEINFO output follows: >mtceinfo {906D34F1-763F-4945-AA11-8D590468D5CE} MtcEinfo Version 4.0.6-W2.EA Copyright (c) Marathon Technologies Corporation, 1996, 1997-2001. Vendor Description = HP 10/100TX PCI Ethernet Driver Vendor Id = 0x00831000 (length = 4) Vendor Driver Version = 4.2 (0x00040002) NDIS version in use by NIC driver = 5.
Making an MTC Diskette Some Endurance tools require an MTC diskette. You can create this diskette at any computer that contains a floppy drive and CD-ROM drive. To create an MTC diskette: Step Action Notes 1 From any computer, insert an MS-DOS bootable diskette in the floppy drive. 2 Insert the Endurance CD into the CD-ROM drive. 3 Copy contents of the \MTCUTILS directory onto the diskette. You can use Windows Explorer or an equivalent file management tool.
MTCCONS (Endurance Manager Console Commands) You can execute Endurance server commands from an MS-DOS window. The primary reason for using MTCCONS (Endurance Manager console commands) is to execute scripts for system validation (test) or system management. When using MTCCONS, enter the command syntax and any required parameters. Note: We recommend that you set your current directory to the Endurance area in Program Files before using MTCCONS commands.
Table 7-4 MTCCONS Parameters (Continued) Parameter Description interval Integer from 0 to n flag True = on; False = off When issuing console commands, note the following: • An example of a command line is MTCCONS • The MTCCONS syntax is not case sensitive. • You can use abbreviated syntax by entering the minimum characters that make the command unique. For example, for the IOP Disable Command, you can type either: IOP1.MTCMON SHOW CONFIGURATION.
Table 7-5 Summary of MTCCONS Commands MTCCONS Command Page MTCCONS CEn Disable Auto Boot From IOPx 5-10 MTCCONS CEn Disable Auto Synch From IOPx 5-11 MTCCONS CEn Enable Operation From IOPx 5-12 MTCCONS CEn Enable Auto Boot From IOPx 5-13 MTCCONS CEn Enable Auto Synch From IOPx 5-13 MTCCONS CE_O/S Shutdown Operation From IOPx 5-18 MTCCONS ESIn Enable Operation From IOPx 5-19 MTCCONS IL12 Enable Operation From IOPx 5-20 MTCCONS IOPn Disable Operation From IOPx -disable_safeguard 5-12 MTCCO
Table 7-5 Summary of MTCCONS Commands (Continued) MTCCONS Command Page MTCCONS IOPn.Event Set Checkpoint 5-45 MTCCONS IOPn.Event Show Dropped Event Statistics 5-46 MTCCONS IOPn.InputProvider Disable Automatic Switchover 5-48 MTCCONS IOPn.InputProvider Disable Hotkey 5-48 MTCCONS IOPn.InputProvider Disable LED Flashing 5-49 MTCCONS IOPn.InputProvider Enable Automatic Switchover 5-49 MTCCONS IOPn.InputProvider Enable Hotkey 5-50 MTCCONS IOPn.
Table 7-5 Summary of MTCCONS Commands (Continued) MTCCONS Command Page MTCCONS IOPn.Monitor Show Parameters 5-72 MTCCONS IOPn.ScsiProvider Set Mirror Copy Bias 5-74 MTCCONS IOPn.ScsiProvider Show Bad Block Status 5-75 MTCCONS IOPn.ScsiProvider Show Mirror Copy Bias x 5-76 MTCCONS IOPn.
Endurance Performance Monitor Although Endurance has multiprocessing on the CEs, the standard Windows Performance Monitor allows you to view only one Endurance CE processor (Processor 0). However, the Endurance server also includes the Endurance Performance Monitor, a plug-in for the standard Windows Performance Monitor that enables it to display the activity of the second CE processor. The Endurance Performance Monitor is implemented in English only.
Step Action Notes 3 Select the % Processor 1 Time counter. The % Processor 1 Time counter is updated once every .75 seconds. For accurate readings, in the Chart Options dialog box, do not set the Update Time Interval value to less than 1 second. 4 Select the standard Processor object, % Processor Time counter, Instance 0. Use this selection to monitor the CE Processor 0.
Installation Verification Procedure (IVP) The Installation Verification Procedure runs automatically each time an IOP boots. It evaluates the server’s Ethernet bindings and reports its findings to the event log on the local IOP. You can also run the installation verification procedure manually whenever you want to reevaluate the Ethernet bindings. To run the procedure, open an MS-DOS command window and type mtcivp. The results are written to the event log on the IOP from which you run the procedure.
Managing Faults 8 This chapter describes the general methods of diagnosing faults and provides an overview of the troubleshooting process. This chapter contains the following sections: Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Diagnosing Faults . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 Isolating Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Correcting Faults . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault Management Because the Endurance server is fault tolerant, when a fault occurs (for example, a failed network adapter), the server continues operating. Even though it is still operational, any failure to the faulted component’s redundant counterpart can affect the availability of the server. To return the Endurance server to a fully fault tolerant state, you may need to complete some fault management procedures. Fault management involves several steps. The actions taken depend on the type of fault.
Diagnosing Faults You can use any of the methods in Table 8-1 to diagnose a fault. Table 8-1 Diagnosing Faults Method Description Refer to . . . Endurance Manager Use the Administration Window and Device Status Window to determine if a component, including the MIC, is active or online. Chapter 4 for Endurance Manager information MIC status lights Displays the power and connection status for the MICs in your Endurance server.
Isolating Faults If you have local access to the Endurance server, check the following in the order that they are listed: Step Action Notes 1 Check the upper and lower status lights on the handles of each of the four MICs in your server. If both sets of lights are solid green, the MICs are working properly and communicating correctly. If any of the lights are orange, red, or off, there may be a problem with the MIC. Refer to Appendix A for a description of the MIC status lights.
If you only have access to an Endurance server using Remote Endurance Manager, check the following: Step Action 1 Using the Endurance Manager Administration Window and the Device Status Window, note any components that are not active, online, or standby. 2 Check the Windows Event Viewers to which you have access. Look for Endurance messages that begin with or Notes . Reference those events (in the HP Netserver AA Solution Messages online manual) for information and corrective action.
Endurance Server Maintenance 9 This chapter contains the maintenance procedures for the Endurance server. Use this chapter only if referred here by an Action section in a message (in HP Netserver AA Solution Messages). Warning: When performing maintenance on your Endurance server, carefully follow the instructions in each procedure. Otherwise, you could unintentionally remove your Endurance server from operation or cause damage to its components.
Replacing a MIC . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16 Replacing an IOP Replacing a CE . . . . . . . . . . . . . . . . . . . . . . . . . 9-18 . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22 Updating MIC BIOS, FPGA, and Microcode . . . . . . . . . . . 9-22 Replacing a Failed Ethernet Adapter . . . . . . . . . . . . . . . 9-23 Updating an Ethernet Driver . . . . . . . . . . . . . . . . . . . 9-25 Adding a Windows Service Pack . . . . . . . . . . . . . . . . . .
Rebooting an IOP Before you reboot an IOP, consider the following points which may affect your decision to reboot the IOP at that time. • • When an IOP is removed from service (powered off, disabled, faulted or booted in any mode other than Operational Endurance I/O Processor Mode): - Any non-mirrored devices that physically reside on that IOP are not available to the Endurance server.
To reboot an IOP: Step Action Notes 1 Follow the instructions in the procedure Rebooting the Endurance Server on page 9-9. Do this only if you are willing to remove the Endurance server from service. If you do not want to remove the Endurance server from service, continue with the next step. 2 Use Endurance Manager to ensure the following: If possible, perform any necessary backups for non-mirrored devices on the IOP that you want to reboot.
Shutting Down an IOP Before you shut down an IOP, consider the following points. You may decide to shut down the IOP at another time. • • When an IOP is removed from service (powered off, disabled, faulted or booted in any mode other than Operational Endurance I/O Processor Mode): - Any non-mirrored devices that physically reside on that IOP are not available to the Endurance server.
To shut down an IOP: Step Action Notes 1 Follow the instructions in the procedure Shutting Down the Endurance Server on page 9-9. Do this only if you are willing to remove the Endurance server from service. If you do not want to remove the Endurance server from service, continue with the next step. 2 Use Endurance Manager to ensure the following: If possible, perform any necessary backups for non-mirrored devices on the IOP that you want to shut down.
Shutting Down a Tuple Before you shut down a tuple IOP, consider the fact that when a tuple is shut down, both the CE and IOP are removed from service. As a result, any non-mirrored devices that physically reside on that IOP are not available to the Endurance server. For this reason, you may decide to shut down the tuple at another time. To shut down a tuple: Step Action Notes 1 Follow the instructions in the procedure Shutting Down the Endurance Server on page 9-9.
Shutting Down a CE To shut down a CE: Step Action Notes 1 Make sure that the other CE is active. If the other CE is not active, shutting down the only active CE removes the Endurance server from service. 2 From Endurance Manager issue the CEx Disable Operation command. 3 Power off the CE if desired. A disabled element will not attempt to rejoin the server.
Rebooting the Endurance Server Before you reboot the Endurance server, consider the fact that completing this procedure removes your server from service. Make sure that you schedule an appropriate time and that you have completed any necessary backups before starting this procedure. To reboot the Endurance server, from Endurance Manager issue the Server Shutdown command.
Replacing an Interconnect Fiber Cable To replace an interconnect fiber cable: Step Action 1 Obtain a replacement interconnect fiber cable from your service provider. 2 Using Table 9-1 as a guideline, identify the fiber cable to be replaced. Table 9-1 Interconnect Fiber Cable Chart 9-10 Fiber cable between...
Replacing an Interconnect Fiber Cable on an Online System Use the following procedure to replace an interconnect fiber cable on an online system. Caution: Before proceeding, make sure you are properly grounded using, for instance, a wrist strap with an attached alligator clip that is connected to an appropriate ground. Step Action 1 Make sure a component at one end of the fiber to be replaced is offline or disabled. 2 Disconnect the existing fiber from the Endurance system.
Replace an Interconnect Fiber Cable on an Offline System Use the following procedure to replace an interconnect fiber cable on an offline system. Caution: Before proceeding, make sure you are properly grounded using, for instance, a wrist strap with an attached alligator clip that is connected to an appropriate ground. Step Action Notes 1 Shut down and power off the Endurance system. See Shutting Down the Endurance Server on page 9-9. 2 Disconnect the existing fiber from the Endurance system.
Replacing the IL Fiber or Cable The IL provides a direct Ethernet connection between the IOPs. Caution: Before proceeding, make sure you are properly grounded using, for instance, a wrist strap with an attached alligator clip that is connected to an appropriate ground. To replace an IL fiber or cable: Step Action Notes 1 Obtain a replacement IL cable. Obtain the appropriate fiber or cable that meets the specifications for your Ethernet adapter.
Replacing an IOPx.Ethernet Fiber or Cable The IOPx.Ethernet fiber or cable connects the IOP to the public Ethernet. Caution: Before proceeding, make sure you are properly grounded using, for instance, a wrist strap with an attached alligator clip that is connected to an appropriate ground. To replace an IOPx.Ethernet fiber or cable: Step Action Notes 1 Obtain a replacement Ethernet cable from your service provider that meets the specifications for your network.
Step Action Notes 6 Make sure that any components affected by this procedure are active or online. Reenable any faulted or disabled components (page 9-31). Use Endurance Manager for this step. 7 Confirm that the new Ethernet cable operates properly: Use Endurance Manager for these steps. • Establish a network connection to validate that the connection is operating properly. For example, use Windows Explorer to connect to a network node.
Replacing a MIC To replace a MIC, complete the following procedures: • Removing a MIC • Installing a Replacement MIC Removing a MIC Caution: Before proceeding, make sure you are properly grounded using, for instance, a wrist strap with an attached alligator clip that is connected to an appropriate ground. To remove a MIC: Step Action 1 Obtain a replacement MIC from your service provider. 2 Remove from service the Endurance element in which the MIC is installed.
Installing a Replacement MIC Caution: Before proceeding, make sure you are properly grounded using, for instance, a wrist strap with an attached alligator clip that is connected to an appropriate ground. To install a replacement MIC: Step Action 1 Carefully remove the replacement MIC from its anti-static packaging. 2 Install the replacement MIC into the correct slot. 3 Replace the cover. 4 Attach the MIC fiber connections by clipping them into the cable receptacles. 5 Power up the system.
Replacing an IOP To replace an IOP, complete the following procedures: • Removing an IOP • Preparing a New IOP for Installation • Installing a New IOP Removing an IOP Caution: Before proceeding, make sure you are properly grounded using, for instance, a wrist strap with an attached alligator clip that is connected to an appropriate ground. To remove an IOP from the Endurance server configuration: Step Action Notes 1 Shut down the IOP that you want to replace. page 9-5.
Preparing a New IOP for Installation After removing the IOP from the Endurance server configuration, prepare the replacement IOP for installation: Step Action 1 Install any hardware for your IOP using the procedures in Chapter 2 of the HP Netserver AA Solution Installation Guide. 2 Decide which, if any, disks will be transferred to the new IOP. Notes When you install those disks, make sure that their new configuration is identical to the configuration that was used in the IOP that you are replacing.
Installing a New IOP Caution: Before proceeding, make sure you are properly grounded using, for instance, a wrist strap with an attached alligator clip that is connected to an appropriate ground. After preparing the new IOP, finish installing the new IOP: Note: For detailed instructions, refer to the HP Netserver AA Solution Installation Guide. Step Action 1 If required, fasten the rackmount brackets and install the IOP in the rack. 2 Attach the following cables to the IOP: • The power cord.
Step Action Notes 6 Reboot the new IOP into Operational Endurance I/O Processor Mode. The public Ethernets may require additional considerations. Refer to the procedures on page 9-24 for information. 7 Use Endurance Manager to ensure that: • Any components affected by this procedure are active or online. Reenable any faulted or disabled components (page 9-31). • The IOP joins the server. • The IL transitions to active. • The IOPx.
Replacing a CE Caution: Before proceeding, make sure you are properly grounded using, for instance, a wrist strap with an attached alligator clip that is connected to an appropriate ground To replace a CE: Step Action 1 Shut down the CE as described on page 9-8. 2 Power off the CE. 3 Detach and label the following cables from the CE: • The power cord. • The MIC fiber cables by squeezing the connectors to unclip them and detaching them. • The video cable.
Replacing a Failed Ethernet Adapter To replace a failed Ethernet adapter, complete the following procedures: • Installing the Replacement Adapter • Configuring the Replacement Adapter Installing the Replacement Adapter Caution: Before proceeding, make sure you are properly grounded using, for instance, a wrist strap with an attached alligator clip that is connected to an appropriate ground. To replace a failed Ethernet adapter: Step Action Notes 1 Obtain a replacement Ethernet adapter.
Configuring the Replacement Adapter To configure a replacement adapter: Step Action Notes 1 From My Network Places on the desktop, select Properties to verify that the network bindings are properly configured. • Verify and correct the adapter bindings to match those in the other IOP. Refer to Chapter 3 in the HP Netserver AA Solution Installation Guide for information about how to configure bindings. • Correct the MAC addresses to the new addresses, and then commit the Endurance configuration.
Updating an Ethernet Driver On an IOP, after you update the third-party Ethernet driver for a redirected Ethernet adapter and before you restart Windows, you must recommit the configuration, using the Endurance Configuration Utility. The Endurance Configuration Utility rewrites the Network Address parameter for the Ethernet adapters in the Registry. To accomplish this: Step Action Notes 1 Open the Endurance Configuration Utility. Be sure this is on the IOP where you updated the driver.
Adding a Windows Service Pack For the CE Operating System To add a Windows Service Pack to the CE operating system: Step Action 1 Schedule an appropriate time to reboot the CE operating system. 2 Install Windows Service Pack software. 3 When prompted, reboot Windows. Notes For an IOP Determine in advance if you want to install the Service Pack on both IOPs simultaneously. If so, on both IOPs, perform step 1 and step 2 in the following table, and then reboot the entire server.
Replacing a Failed Mirrored Disk Warning: If the failed disk is the source of a mirror copy, do not implement this procedure until completing all precautions to save data from this disk. Often disks can be replaced within a RAID subsystem with no need for special Endurance considerations at all. Refer to your vendor’s RAID documentation and ignore this procedure.
Step Action 3 If the failed disk is a component of a hardware RAID array (with redundancy), follow the RAID controller vendor’s documentation. If the vendor supports replacing devices with power on (hot swap bays), there are no further steps to perform in this procedure. Notes You can perform a local rebuild using RAID controller features, and there is nothing further to do. (In some systems, I/O performance may be degraded during the rebuild.
Step Action Notes 4 If the failed disk is not installed in a hot swap bay, shut down the IOP. If the failed disk is in IOP1, verify that IOP2 (the other IOP) is capable of sustaining the server, including the CE operating system and connections to the redirected networks. (Refer to step 2 in this procedure). If the failed disk is installed in a hot swap bay, you can attempt the repair while the IOP remains online. To do so, skip to step 5.
Step Action 5 Initialize the Endurance sector on the replacement disk: 6 • From the application task bar, select Start Programs Marathon Endurance Endurance Manager. • From the Endurance Manager, issue the command • Substitute for n the number of the IOP in which the replacement disk was installed. IOPn.Diskx Reset Endurance Sector. • Substitute for x the number of the CE disk of the mirror set in which it was a member. For example: IOP2.
Reenabling Faulted Components After completing a maintenance procedure, you may need to enable a component that was previously disabled, faulted, or offline. If necessary, reenable any faulted or disabled components using Endurance Manager commands, as follows: Table 9-2 Endurance Manager Commands to Reenable Components Faulted Component Enable Using...
MIC Specifications and LEDs A This appendix describes the specifications and LEDs of the Marathon Interface Card (MIC), V4.0. This appendix includes the following section: Marathon Interface Card (MIC) Specifications . . . . . . . . . . A-2 MIC LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Marathon Interface Card (MIC) Specifications Refer to Endurance Release Notes Release 4.0 for information about the correct versions of the MIC to use in your server. The MIC specifications in this section apply to the MIC shipped in the standard Endurance kit. The specifications include: • MIC Specifications • MIC Fiber Cable Specifications The MIC is a high-speed interconnect path for communication between the CEs and the IOPs.
MIC LEDs Each MIC has LEDs which indicate the status of the firmware and of the local and remote fiber connections. Figure A-1 is a representation of the MIC LEDs. Remote connection fiber status Firm ware status Local connection fiber status Figure A-1 MIC LEDs Table A-3 describes the firmware LED. Table A-3 Firmware LED State Indicates Off No power, or MIC is not working. Rapid Red Flash (5-10 seconds) Rate of 1/10th second MIC is running the self-test which occurs after reset.
Table A-4 describes the fiber LEDs. Table A-4 Fiber LEDs State Indicates No light No power, or no fiber signal is detected. Green The MIC hardware is transmitting and receiving fiber status through the fiber connector. Red The fiber connection has been lost for an unknown reason. Orange The fiber connection is lost due to a power failure or a reset of the other MIC.
Endurance Boot Flow Charts B This appendix shows the Endurance server boot flow charts referenced in Chapter 2. The IOP and CE flow charts detail the boot process for the Endurance server. The flow charts assume a normal system with all Endurance server components powered on and installed and configured properly. The flow charts also assume that the Endurance server is booting using the default system configuration.
IOPx IOPy IOPx is powered on and starts the boot process. IOPy is powered on and starts the boot process. IOP passes POST. IOP passes POST. IOP tests MIC BIOS and calls MIC BIOS. IOP tests MIC BIOS and calls MIC BIOS. MIC BIOS calls system BIOS. MIC BIOS calls system BIOS. System BIOS starts to load Windows*. System BIOS starts to load Windows*. Endurance software is loaded. Endurance software is loaded. IOP verifies tuple ID. IOP verifies tuple ID. IOP transitions from Offline to Ready.
CEy CEx CEx is powered on and starts the boot process. CEy is powered on and starts the boot process. CE passes POST. CE passes POST. CE tests MIC BIOS and calls MIC BIOS. CE tests MIC BIOS and calls MIC BIOS. CE initializes interconnect paths to IOP(s). CE initializes interconnect paths to IOP(s). CE issues boot request. CE issues boot request. IOP services boot request. IOP servicing boot redirects its keyboard to the CE. CE loads Windows and initializes Endurance drivers and services.
Glossary boot disk. A SCSI disk that contains the Windows operating system. For the Endurance server, the boot disk for the CE is a member of a mirrored disk set that physically resides on the IOPs. The boot disk for an IOP is non-mirrored and local to that IOP. booting. A process for a system that includes passing POST and loading a system’s Windows operating system. CE Desktop application.
DSL. Device Synchronization Layer. The DSL controls and participates in device I/O request processing on the IOPs. enable. Manually add a component to the active Endurance server configuration. Components are enabled using an Endurance Manager or a MTCCONS command. Endurance Manager. A user-level server management application for the Endurance server. This Endurance application provides both a Windows-based graphical user interface (GUI) and a command prompt interface. Endurance sector.
IOP link. See IL. lock step. A mode in which two CEs simultaneously execute the same copy of the Windows operating system and any Windows applications. logical disk. A CE disk that is composed of one disk from each IOP. For example: A logical mirror set identified by the name “Disk0” is composed of two physical disks: one residing on IOP1 and the other residing on IOP2. Marathon Interface Card. See MIC. MIC. Marathon Interface Card.
POST. Power-On Self Test. A test that each system passes as part of its initial boot process. The content of POST is specific to the system’s manufacturer and model. shutdown. A system process that refers to shutting down either one of (or a combination of) the IOPs’ and CE’s copies of the Windows operating system. provider. Endurance IOP-based software driver that provides access to a specific service.
virtual network. LAN-style connectivity between the CE and each IOP. This connectivity is independent of any public (redirected) or private (IOP) network adapters. vulnerable. The state of an Endurance server when one or more components has failed but the system is still operational and available to end users. The system is vulnerable to complete failure if certain additional components fail.
Index Symbols % field 4-6, 4-19 A Accessing Endurance Manager commands 5-3 Action field 4-17 Active 2-21 Active CE state 2-14 Active interconnect state 2-16 Active IOP state 2-15 Active server state 2-13 Arbitration timeout set 5-50 show 5-53 Auto boot disable 5-10 enable 5-13 show 5-15 Auto scrolling 3-8 Auto start disable 5-65 enable 5-66 show 5-67 Auto synch disable 5-11 enable 5-13 show 5-16 Automatic switchover disable 5-48 enable 5-49 show 5-53 B Bad block disable remap 5-28 enable remap 5-30 Bad b
CE Desktop application 3-8 CE tray icon 3-9 input focus 3-9 refresh frequency 3-10 running in a window 3-8 running in Full-Screen Mode 3-8 video resolution 3-8, 3-10 CE Disable Operation command 5-12 CE Enable Operation command 5-14 CE O/S command shutdown 5-18 CE O/S shutdown command 5-18 CE operating system shutting down 9-8 CE operating system states 2-13 CE Remove from Configuration command 5-14 CE states active 2-14 booting 2-14 disabled 2-14 faulted 2-14 offline 2-14 ready 2-14 sync-master 2-14 sync-s
D E DatagramService commands 5-24 Device Synchronization Layer Glossary-2 Devices non-mirrored Glossary-3 Diagnosing faults 8-3 Disable Glossary-1 Disable commands auto start 5-65 automatic switchover 5-48 bad block remap 5-28 CE 5-12 CE auto boot 5-10 CE auto synch 5-11 Ethernet 5-35 hotkey 5-48 IOP 5-21 LED flashing 5-49 mirrored disk 5-29 tuple operation 5-82 Disable_safeguard option 5-12, 5-14, 5-23, 7-16 Disabled 2-21, Glossary-1 Disabled CE state 2-14 Disabled IOP state 2-15 Disabled mirrored disk s
ESI description 1-6, 2-3 ESI command enable operation 5-80 ESI Enable Operation command 5-19 Ethernet multiple connections 1-3 network connection description 1-6 Ethernet adapters configuring 6-11 replacing 9-23–9-26 Ethernet cable replacing 9-14 Ethernet commands disable 5-35 enable 5-36 reset port counters 5-36 show port counters 5-37 show port information 5-39 EthernetProvider commands reset provider counters 5-41 show parameter values 5-41 show provider counters 5-43 Event commands remove events 5-45 s
IL Enable Operation command 5-20 In a window CE Desktop application 3-8 Informational events description 2-24 Initialization interval set 5-66 show 5-70 Initialized IOP state 2-15 Initializing IOP state 2-15 Initializing network connection state 2-20 Input active set 5-52 set CE 5-52 set IOP 5-52 Input devices Glossary-2 show states 5-56 Input focus, CE Desktop application 3-9 Installing replacement IOP 9-18, 9-20 replacement MIC 9-16, 9-17 Interconnect 2-16 Interconnect fiber cable replacing 9-10 Interconn
IOPn.Ethernetx commands 5-35–5-40 IOPn.EventProvider Commands Remove Events 5-45 IOPn.EventProvider commands 5-45–5-47 remove events 5-45 set checkpoint 5-45 show dropped event statistics 5-46 IOPn.EventProvider Remove Events command 5-45 IOPn.
MIC 9-16 replacing CE 9-22 Ethernet adapters 9-23–9-26 failed mirrored disk 9-27 IL cable 9-13 interconnect fiber cable 9-10 IOP 9-18 IOPx.Ethernet cable 9-14 shutting down CE 9-8 CE operating system 9-8 IOP 9-5 server 9-9 tuple 9-7 updating MIC BIOS, FPGA and Microcode 9-22 Making an MTC diskette 7-15 Management commands show computer information 5-78 Marathon Interface Card. see MIC Marathon software.
Online keyboard/pointer state 2-21 Online mirrored disk state 2-18 Online network connection state 2-20 Online server state 2-13 Operating System commands shutdown 5-18 Operation field 4-17 Operational Endurance I/O Processor Mode 2-11 Operator override field 4-17 Options dialog description 4-18 P Parameter field 4-17 Parameter values show 5-41 Parameters show 5-16 PCI Reset MIC port state 2-17 Pointer Glossary-3 Port counters DatagramService reset 5-24 show values 5-25 Ethernet reset 5-36 show 5-37 LinkDr
Resetting Endurance sector 5-32 Resetting mirror copy 5-33 Revision information others 5-74 Revision levels software 4-21 S Save On Exit field 4-19 SCSI disks replacing failed mirrored disk 9-27 Serial port states 2-21 Server boot process 2-7 CE boot process 2-9 component states 2-12 description 1-2 IOP boot process 2-7 logical view 1-7 physical view 1-7 shutting down 9-9 Server command shutdown 5-80 Server name 4-5 Server software 1-9 Server states 2-13 active 2-13 offline 2-13 online 2-13 Service pack ad
Specifications Endurance hardware A-2 SplitSite 1-3, 1-8 State descriptions 2-12 States CD-ROM 2-21 CE 2-14 CE operating system 2-13 floppy disk drive 2-21 interconnect 2-16 IOP 2-15 keyboard/pointer 2-21 mirrored disk 2-18 network connection 2-20 other components 2-21 serial port 2-21 server 2-13 tape drive 2-21 Status field 4-6, 4-19 Status lights Endurance Manager 4-9 Synchronize Glossary-4 Sync-Master CE state 2-14 Sync-Slave CE state 2-14 System administration 2-1–2-24 using the CE 2-22 System states d
