Endurance FTvirtual Server Administrator’s Guide Marathon Technologies Corporation Fault and Disaster Tolerant™ Solutions for Windows Environments Release 6.1.
NOTICE Marathon Technologies Corporation reserves the right to make improvements to this guide and the product it describes at any time and without further notice. COPYRIGHT Marathon Technologies Corporation. 1996-2005. All rights reserved. This guide is copyrighted, and all rights are reserved. No part of this guide or the products it describes may be reproduced by any means or in any form, without prior consent in writing from Marathon Technologies Corporation. Printed in the U.S.A. U.S.
Contents Preface Chapter 1 — Starting, Shutting Down, and Restarting Endurance FTvirtual Server Methods for Performing Management Tasks . . . . . . . . . . . . . . . . . . . . . . 1-2 Starting A Endurance Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Shutting Down the Endurance Configuration. . . . . . . . . . . . . . . . . . . . . . 1-4 Starting the FTvirtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Shutting Down the Endurance FTvirtual Server . . . .
Configuring Storage Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11 Updating Device Settings When Adding Disks. . . . . . . . . . . . . . . . . . 3-11 Updating Device Settings When Removing Disks . . . . . . . . . . . . . . . . 3-13 Updating Device Settings When Replacing Devices . . . . . . . . . . . . . . . 3-14 Updating Device Settings When Adding CD-ROMs, Medium Changers, and Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Endurance Component States . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 Mirror Copy Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31 Component Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . 4-32 Managing CoServer Link Communications . . . . . . . . . . . . . . . . . . . . . 4-33 Optimizing CoServer Link Communications . . . . . . . . . . . . . . . . . . . 4-33 Examining CoServer Link Properties and Status . . . . . . . . . . . . . . . . .
Diagnosing Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Isolating Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Correcting Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Chapter 6 — Endurance Tools MTCCONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Installation Verification Procedure (IVP) . . . . . . . . . . . . . . . . . . . . . . . .
Tables 2-1 2-2 3-1 3-2 3-3 3-4 4-1 4-2 4-3 4-4 4-5 4-6 4-7 4-8 4-9 4-10 4-11 4-12 4-13 4-14 4-15 4-16 4-17 4-18 4-19 4-20 4-21 4-22 4-23 5-1 6-1 FTvirtual Server Video Recommendations . . . . . . Video Mode Options . . . . . . . . . . . . . . . . . . Endurance Device Redirector Icons . . . . . . . . . . Endurance Device Redirector Toolbar Icons . . . . . Endurance Device Redirector Menus . . . . . . . . . Endurance Device Redirector Button Information. . . Connect to Host Settings Descriptions . . . . . .
A-1 A-2 A-3 A-4 A-5 A-6 A-7 A-8 viii Endurance VFT MIB and Extension Agent Files. . . . . . . Subtree Nodes within the Endurance MIB . . . . . . . . . . Endurance Vft MIBv1 Sub-tree Nodes . . . . . . . . . . . Trap Name Severity Levels Indicating State Information . . System Information Variables At the Beginning of All Traps System Information Variables At the End of All Traps . . . Device Trap Names and Child Numbers . . . . . . . . . . . Optional Device Specific Variables . . . . . . . . . . . . . . .
Figures 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 4-1 4-2 4-3 4-4 4-5 4-6 4-7 4-8 4-9 4-10 4-11 4-12 4-13 4-14 4-15 A-1 A-2 A-3 A-4 Endurance Device Redirector Main Window . . . . . . . Device Redirector Connections Dialog Box . . . . . . . Add Disks Screen . . . . . . . . . . . . . . . . . . . . . Replace Disks Screen . . . . . . . . . . . . . . . . . . . Virtual Disks in the Device Redirector . . . . . . . . . . Redirect Virtual Disks Screen . . . . . . . . . . . . . . .
x Endurance FTvirtual Server Administrator’s Guide
Preface This manual describes how to manage and administer the Endurance FTvirtual Server. Audience This manual is written for experienced technical personnel responsible for installing, configuring, administering, and managing network server hardware and software, including Microsoft Windows. This manual assumes that you are familiar with the Endurance terminology.
Endurance Manuals The Endurance manuals include: • Endurance FTvirtual Server Administrator’s Guide (Admin.pdf), which describes how to manage and administer the Endurance FTvirtual Server and use its related Endurance tools and utilities; and provides complete documentation of the Endurance SNMP software and MIB files. • Endurance FTvirtual Server Commands (Commands.pdf), which lists and describes the Endurance FTvirtual Server commands used with the MTCCONS utility within scripts you write.
Conventions The following conventions are used in the Endurance documentation set: Convention Description Italics, Courier font Indicates a variable that you replace in a path name or command Bold, Courier font Indicates actions or commands that you must type. For example, type A:\ETX Courier font Represents examples of screen text. For example, scsiid = 0, 1. Bold Is used to: Italics • Emphasize important information. • Indicate menu, pathname, or button selections.
For Technical Support For technical support, contact your certified Endurance FTvirtual Server support provider. You can also consult the Marathon Support web site at http://support.marathontechologies.com for additional documentation and information. Login to the Support web site using your license key number. Additional Information on the Support Web Site Visit the Support web site at http://support.marathontechnologies.
Starting, Shutting Down, and Restarting Endurance FTvirtual Server 1 This chapter describes the procedures you use to start up, shut down, and restart the Endurance Configuration and FTvirtual Server. This chapter assumes that you are familiar with the Endurance terminology described in the Glossary. This chapter includes the following sections: Methods for Performing Management Tasks . . . . . . . . . . . . 1-2 Starting A Endurance Configuration . . . . . . . . . . . . . . . .
Methods for Performing Management Tasks When you are logged in locally to a CoServer or the FTvirtual Server, either directly or through a Microsoft terminal services client, Endurance software provides the following methods from which you can perform management tasks: • Windows Start Menu • Taskbar Icon Menu • Endurance Manager Windows Start Menu To use the Windows Start Menu, navigate to the Programs menu and select Marathon Endurance and select the appropriate menu item to accomplish the desired ta
Starting A Endurance Configuration Starting a Endurance Configuration involves powering on and booting both CoServers. Although you can boot the CoServers in any order, you must boot both CoServers in Online Endurance CoServer Mode, the default boot mode, in order to start fault tolerant operations. Once the CoServers are fully booted and joined, the FTvirtual Server starts automatically and initializes as a fault tolerant operating environment.
Shutting Down the Endurance Configuration Shutting down the Endurance Configuration typically shuts down the FTvirtual Server and both CoServers, consequently shutting down all applications and removing them from service. A Disabled CoServer is not shut down as part of the Endurance Configuration Shutdown commands. You may choose to: • Have both CoServers power off (if possible) or not reboot after shutdown. • After shutdown, have both CoServers reboot and then automatically restart the FTvirtual Server.
To shut down the Endurance Configuration when logged in to a CoServer or the FTvirtual Server Desktop: Step Action 1 Select a keyboard and monitor that are connected physically to a CoServer that is in the state Good. 2 Login to the CoServer. 3 Shut down the Endurance Configuration. Notes From the Taskbar icon on your desktop, right click and select Manage Configuration Shutdown. (Select Restart if you want the configuration to restart automatically after shutdown is complete.
To shut down the Endurance Configuration when operating on a remote client PC: Step Action Notes 1 Use the Endurance Manager to connect to the FTvirtual Server. On a remote client PC, launch the Endurance Manager by selecting from the Programs menu Marathon Endurance Manager. 2 Shut down the Endurance Configuration. From the Endurance Manager running on your desktop, connect to the FTvirtual Server, and on the Manage menu, select Endurance Configuration Shutdown.
Starting the FTvirtual Server You can begin the start process for the FTvirtual Server on either CoServer. You can use either the Windows Start menu, the Taskbar icon, or the Endurance Manager to restart the FTvirtual Server.
When the FTvirtual Server does not start automatically, you can start it manually using either of the following methods. To start the FTvirtual Server when logged in to either CoServer: Step Action 1 Select a keyboard and monitor that are connected physically to a CoServer that is Good. 2 Start the FTvirtual Server. Notes You can start the FTvirtual Server in several ways: • From the Taskbar icon on your desktop, right click and select Manage FTvirtual Server Start.
Shutting Down the Endurance FTvirtual Server Shutting down the FTvirtual Server shuts down only the FTvirtual Server. Both CoServers remain active after the operation completes. When you shut down the FTvirtual Server, you may do so without having it reboot, or you can shut it down and have it restart automatically. Whichever shutdown process you choose, applications running in the fault tolerant environment are terminated. The following examples describe shutting down the FTvirtual Server without reboot.
To shut down the FTvirtual Server when logged in to either CoServer or the FTvirtual Server Desktop: Step Action 1 Select a keyboard and monitor that are connected physically to a CoServer that is Good. 2 Login to the CoServer. 3 Shut down the FTvirtual Server. Notes From the Taskbar icon on your desktop, right click and select Manage FTvirtual Server Shutdown. (Select Restart if you want the FTvirtual Server to restart automatically after shutdown is complete.
To shut down the FTvirtual Server when operating on a remote client PC: Step Action Notes 1 Use the Endurance Manager to connect to the FTvirtual Server. On a remote client PC, launch the Endurance Manager by selecting from the Programs menu Marathon Endurance Manager. 2 Shut down the FTvirtual Server. From the Endurance Manager running on your desktop, on the Manage menu, select FTvirtual Server Shutdown.
1-12 Endurance FTvirtual Server Administrator’s Guide
FTvirtual Server Desktop 2 This chapter describes the FTvirtual Server Desktop, which is accessible from the CoServer. This chapter assumes that you are familiar with the Endurance terminology described in the Glossary. This chapter includes the following sections: FTvirtual Server Desktop . . . . . . . . . . . . . . . . . . . . . . 2-2 Video Considerations . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Using the FTvirtual Server Desktop . . . . . . . . . . . . . . . .
FTvirtual Server Desktop The FTvirtual Server Desktop, a Windows application similar to industry-standard remote control applications, displays FTvirtual Server video output on the CoServer. To launch the FTvirtual Server Desktop: • From the Taskbar, right click on the Taskbar icon and select Launch FTvirtual Server Desktop. • From the Windows Programs menu, select Marathon Endurance Desktop to launch the application.
Video Considerations For Remote Control Applications in the FTvirtual Server: • • The Endurance Video Display Driver (MtcVidD) and Video Miniport Driver (MtcVidR) redirect the FTvirtual Server output to the FTvirtual Server Desktop. Therefore, Endurance video drivers are required. - Do not substitute other video on the FTvirtual Server. - Do not disable the Endurance video drivers.
Table 2-1 FTvirtual Server Video Recommendations (Continued) About . . . Recommendations Running graphic-intensive applications on the FTvirtual Server Connect to the FTvirtual Server from a remote client or from a CoServer using the Windows Remote Desktop Connection or a terminal server client. Visual effects On both the FTvirtual Server and the CoServer, you can reduce video overhead by turning off all visual effects.
Using the FTvirtual Server Desktop Before you launch the FTvirtual Server Desktop, set the color palette for the CoServers to a minimum of one setting above 256 colors. Choose a value such as Medium (16 bit). To set the number of colors: 1. From the Control Panel select Display. 2. Select the Settings tab. 3. In the Color quality box, select the number of colors from the list box. FTvirtual Server Desktop Modes The first time that you run the FTvirtual Server Desktop, it runs in a window.
To run the FTvirtual Server Desktop in full screen mode: 1. Double click the FTvirtual Server Desktop icon on the title bar. 2. Check Full Screen Mode. Full-screen mode is available only when the FTvirtual Server and CoServer are running at the same video resolution. To determine the video resolution in which the FTvirtual Server and CoServer are running: 1. On the CoServer and FTvirtual Server, select Display from the Control Panel. 2. Select the Settings tab. 3.
Changing Input Focus When input focus is directed to the FTvirtual Server, the mouse is restricted to the FTvirtual Server Desktop. To shift the input focus to the CoServer, perform one of the following actions: • Press the default hot key sequence Ctrl/Shift/F12, the sequence you assigned if you selected a different sequence, or the sequence which your system administrator may have set for the server.
FTvirtual Server and CoServer Display Settings In the CoServers, you should use video cards that support: • Resolutions of at least 1024 x 768. The display resolution of the FTvirtual Server Desktop need not match that of the CoServer. You can also run the CoServers at different video resolutions. • More than 256 colors. The FTvirtual Server Desktop color palette is always set to 256 colors. You should run the CoServers above 256 colors.
Setting Video Resolution and Refresh Frequency After the FTvirtual Server installation completes, the FTvirtual Server Desktop’s default screen resolution is 800 x 600 pixels for Windows 2003 and 640 x 480 pixels for other versions of Windows. You can change this setting using the Settings tab of the Display application in the Windows Control Panel. Lower resolutions use fewer system resources.
2-10 Endurance FTvirtual Server Administrator’s Guide
Endurance Device Redirector 3 This chapter describes the Endurance Device Redirector. This chapter assumes that you are familiar with the Endurance terminology described in the Glossary. This chapter includes the following sections: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Starting the Endurance Device Redirector . . . . . . . . . . . . . 3-3 Configuring Storage Devices . . . . . . . . . . . . . . . . . . . .3-11 Managing Virtual Disks . . . . . . . . . . . . . . . . . .
Introduction The Endurance Device Redirector is the utility you use to define the redirected devices accessible to the FTvirtual Server environment. Using a graphical user interface, you define the redirected devices and their mapping to physical devices located on the CoServers. You can run the Endurance Device Redirector from a CoServer booted in either Online Endurance CoServer Mode or Offline Endurance CoServer Mode, from the FTvirtual Server, or from any remote host.
Starting the Endurance Device Redirector When you install Endurance software on a CoServer, the FTvirtual Server, and remote clients, the Endurance Device Redirector is installed in the Endurance program folder. You start the Endurance Device Redirector: • From the Windows Programs menu, select Marathon Endurance Device Redirector. • From the Taskbar, by right-clicking on the icon and selecting Launch Device Redirector.
If you are running the Endurance Device Redirector remotely, the default login screen shown in Figure 3-2 displays. Figure 3-2 Device Redirector Connections Dialog Box On this screen, the Local Endurance System check box is grayed out, and you must type the names of the CoServers. You can use the familiar Windows browsing capability to locate the CoServers.
disks are grouped under Disk Drives, and Ethernet adapters are grouped under Networks. The right pane is the workspace where you indicate device settings and where information about devices is displayed. You make changes to the redirected device configuration using the FTvirtual Server branch. Select the type of device you want to configure in the tree view in the left-hand panel. Then, use the menus to provide their device settings.
Table 3-1 Endurance Device Redirector Icons (Continued) Networks Each network connection provides a communication path between the Endurance FTvirtual Server and a local area network. Ethernet devices are paired with one network interface card installed in each CoServer. Together, they are seen by the FTvirtual Server as a single device. Tape Drives All tape drives are non-mirrored SCSI tape drives. Device Setting Conflicts Some devices have settings that are not consistent or correct.
Table 3-2 Endurance Device Redirector Toolbar Icons (Continued) Add a device Add a new redirected device and then update device settings. Remove a device Remove an existing redirected device and then update device settings. Toolbar Icons Use this tool to... Replace a disk Replace a physical SCSI device and then update device settings. Delete the device settings Delete all device settings for devices at and below the selected level.
Table 3-3 describes the menus. Table 3-3 Endurance Device Redirector Menus Menus Description File Menu Open File. . . Opens a previously saved device settings file. Save File Saves the currently displayed device settings to the opened file. Save File As... Saves the currently displayed device settings to the file name you provide. Read Device Settings Opens the file containing the current device settings in the running system.
Table 3-3 Endurance Device Redirector Menus (Continued) Dismount Dismounts a virtual disk from the CoServer. The virtual disk remains available to be mounted again. Properties Displays information for the selected device. View Menu Configuration View Displays a view of the entire Endurance Configuration, showing a tree view of the CoServer devices and FTvirtual Server devices.
Table 3-3 Endurance Device Redirector Menus (Continued) Dismount Dismounts a virtual disk from the CoServer. The virtual disk remains available to be mounted again. Properties Displays information for the selected device. Collapse Hides the devices in the selected branch. Expand Displays the devices in the selected branch. Collapse All Hides all the devices in the Endurance Configuration. Expand All Displays all the devices in the Endurance Configuration.
Configuring Storage Devices Use the Endurance Device Redirector to update device settings when you add, remove, and reconfigure disks and storage devices. Updating Device Settings When Adding Disks Follow the procedures described in the next table to update device settings when you add disks. Figure 3-3 shows the screen used to do so.
Table 3-4 describes the buttons available when using the Add or Replace wizard, or in the case of the Edit button, when you want to change properties. Table 3-4 Endurance Device Redirector Button Information Button Description Edit Allows changes you can modify to properties in the right pane. OK Accepts the information on the current screen. Cancel Cancels any changes you have made to the device settings since the last time the device settings were saved.
Step Action Notes 5 Optionally, enter a description for the device. The description is displayed in the comments field on the disk properties page. 6 Click OK. If the information displayed on this screen is not correct, click Cancel, and add the disk again with the correct information for its device settings. 7 Select File Write Device Settings to save the settings. Updating Device Settings When Removing Disks You can remove any redirected disk from the list of redirected devices.
Updating Device Settings When Replacing Devices You also can use the Endurance Device Redirector to update device settings when you replace disks, CD-ROMs, medium changers, or tape drives due to the following circumstances: • You can replace a mirrored disk member if it is disabled or failed. • You can replace a non-mirrored disk if it is failed. • You can replace any missing device.
To update device settings when you replace an existing disk, CD-ROM, medium changer, or tape drive: Step Action Notes 1 Click on the physical device that you want to replace. • For example, the disk might be CoServer1[3:0:1:0]. • For a mirrored device, use Endurance Manager to ensure the device is failed, disabled, or unknown. • For a non-mirrored device, ensure the device is failed or unknown. • Alternatively, remove the logical device and add the desired device back into the configuration.
Updating Device Settings When Adding CD-ROMs, Medium Changers, and Tape Drives To update device settings when you add a CD-ROM, medium changer, or tape drive: Step Action 1 Click on the appropriate icon for either CDROM, Medium Changer, or Tape Drives. 2 Choose Actions Add or right-click CDROM, Medium Changers, or Tape Drives 3 Notes Add. Select a device on one of the CoServers.
Updating Device Settings When Removing CD-ROMs, Medium Changers, and Tape Drives To update device settings when you remove an existing CD-ROM, medium changer, or tape drive: Step Action 1 Click on the redirected CD-ROM, medium changer, or tape drive in the FTvirtual Server that you want to remove. 2 Choose Actions Remove or right-click, then choose Remove. Notes A verification message is displayed. Click Yes to indicate that you are sure you want to remove the device.
Managing Virtual Disks A virtual disk is created from a file that is specifically formatted to allow it to be mounted as if it were a physical disk. The virtual disk file resides on a CoServer. You may create as many virtual disks as required. For a virtual disk, you can: • Manage it using the Windows Disk Management utility. • Create, format, and delete partitions. • Redirect it to the FTvirtual Server using the Device Redirector functions you use to redirect a physical disk.
Creating a Virtual Disk You create a virtual disk by specifying its size and location. The Device Redirector creates a file which becomes a virtual disk that you can redirect to the FTvirtual Server. To create a virtual disk: Step Action 1 Under CoServer Devices CoServern Disk Drives, then select Actions Create, or right-click Disk Drives then select Create. 2 Specify the size of the virtual disk in megabytes. 3 Specify the name and location of the file that will become the virtual disk.
Mounting a Virtual Disk Virtual disk files can be mounted as disks, making them available to the CoServer for use as a redirected disk. To mount a virtual disk: Step Action 1 Under CoServer Devices CoServern Disk Drives, then select Actions Mount or Notes right-click on the disk drives then select Mount. 2 When you are prompted for the name of an existing file, specify the name of the file or use the Browse button to locate the file; and then click OK.
Redirecting a Virtual Disk You redirect a virtual disk to the FTvirtual Server in the same way that you redirect a physical disk. Typically, a virtual disk is configured together with a virtual disk on the remote CoServer to form a mirror set, but you can also pair a virtual disk with a physical disk to create a mirror set or redirect a single non-mirrored disk. Follow the procedures described in the next table to redirect virtual disks.
To redirected a virtual disk: Step Action Notes 1 Select FTvirtual Server Devices Disk Drives and then select Actions Add or right click on Disk Drives, and select Add. 2 Select a virtual disk for both or either members of the FTvirtual Server Disk Drive. 3 Select File 4 Exit the Device Redirector and reboot the Endurance Configuration at a convenient time. 3-22 See Figure 3-6. You can modify the FTvirtual Server Address and enter a description of the FTvirtual Disk.
Dismounting a Virtual Disk When you dismount a virtual disk, it is removed from the list of CoServer disks, but the virtual disk file is not deleted. You can remount the virtual disk later (see Mounting a Virtual Disk on page 3-20). You cannot dismount a virtual disk that is currently redirected to the FTvirtual Server. You must first replace the virtual disk in the FTvirtual Server disk or remove the FTvirtual Server disk itself.
Deleting a Virtual Disk When you delete a virtual disk, it is dismounted from the CoServer and the file that contained the virtual disk is deleted. You cannot delete a virtual disk that is currently redirected to the FTvirtual Server. You must first replace the virtual disk in the FTvirtual Server disk or remove the FTvirtual Server disk itself. See Replacing a Virtual Disk on page 3-25 or Updating Device Settings When Removing Disks on page 3-13 to perform either of these tasks.
Replacing a Virtual Disk Follow the procedures described in the next table to replace virtual disks. You replace a virtual disk in the same way that you replace a physical disk. Figure 3-7 shows the screen used to update settings when you replace a virtual disks.
To replace a virtual disk: Step Action 1 Ensure that a replacement disk is available as either a virtual or physical disk. Notes If necessary, create a replacement virtual disk (see Creating a Virtual Disk on page 3-19). This disk is then available for redirection as an FTvirtual Server disk. 2 If the virtual disk is not in a Failed or Disabled state, use the Endurance Manager to set it to Disabled.
Moving a Virtual Disk You can move a virtual disk file from one location to another. To relocate a virtual disk file: Step Action 1 Ensure that the Endurance Configuration state is Good. 2 Reboot the CoServer on which the virtual disk resides into Endurance Offline Mode. 3 Dismount the virtual disk as described in the section Dismounting a Virtual Disk on page 3-23. 4 Using Windows Explorer, move the virtual disk file to the desired location, or rename it.
Copying a Virtual Disk You can make a copy of a virtual disk file. To copy a virtual disk file: Step Action 1 Ensure that the Endurance Configuration state is Good. 2 Reboot the CoServer on which the virtual disk resides into Endurance Offline Mode. 3 Dismount the virtual disk as described in the section Dismounting a Virtual Disk on page 3-23. 4 Notes Select Offline Endurance CoServer when Windows boots. Using Windows Explorer, make a copy of the virtual disk file.
Configuring Ethernet Adapters The Endurance FTvirtual Server can support multiple Ethernet connections, or connections to multiple networks to provide network redundancy. Ethernet adapters are configured in pairs. One adapter actively transmits and receives data on the network, and the other adapter remains in a standby state. If the active adapter loses connectivity, network operations automatically fail over to the standby adapter.
Step Action Notes 5 Windows 2003: Select Update Network Connections adapter names. Instructs the Network Setup Wizard to change the friendly name of the adapter to that shown in the Role list. Windows 2003: Select the Update Network and Dial-up Connections adapter name. 6 Click Apply on the Apply Settings dialog. 7 Click Exit. Network bindings and addresses are modified to reflect the new designation for the adapter. If you are running on CoServer 1, repeat steps 2-7 on CoServer 2.
Figure 3-8 Adding Redirected Adapter Screen Step Action Notes 11 Select an adapter from CoServer1 and an adapter from CoServer2 and click OK. Then select File Write Device Settings. Click OK to the Device Settings Saved confirmation dialog. The Device Redirector configures the new network adapter and saves the new settings. 12 Exit the Device Redirector. 13 Right-click on the Endurance taskbar icon and select Manage Endurance Configuration Restart.
Step Action 14 Run the Endurance FTvirtual Server Desktop and log onto the FTvirtual Server using an account with administrator privileges. 15 Windows 2003: Select Start Control Panel Add Hardware. Notes You must add the new network adapter to Windows on the FTvirtual Server. Windows 2000: Select Start Settings Control Panel Add/Remove Hardware. 16 Windows 2003: Click Next at the Welcome to the Add Hardware Wizard. Windows 2000: Click Next at the Welcome to the Add/Remove Hardware Wizard.
Step Action Notes 21 In the Manufacturer column, select Marathon, and in the Network Adapter column, select Endurance Ethernet Redirector (MtcEthR) and click Next. Specifies that the network adapter is an Endurance Ethernet Redirector. 22 Windows 2003: Click Next at the The wizard is ready to install your hardware dialog. The Endurance Ethernet Redirector is installed and functional. Windows 2000: Click Next at the Start Hardware Installation dialog. 23 Click Finish.
Step Action Notes 5 Select each redirected adapter and click Unassign. All adapters must be reassigned when removing an adapter. 6 The Network Setup Wizard prompts you to reassign the unassigned adapters. Starting with Redirected0 select each adapter that you wish to reconfigure and click Next until the Apply Settings dialog is displayed. Figure 3-9 shows an example in a system with two redirected adapters.
7 Windows 2003: Select the Update Network Connections adapter names box. Instructs the Network Setup Wizard to change the friendly name of the adapters to those shown in the Role list. Windows 2000: Select the Update Network and Dial-up Connections adapter names box. 8 Click Apply. 9 Answer No when prompted to run the Device Redirector to autoconfigure the redirected adapters. 10 Click Exit on the Settings Applied dialog. If you are running on CoServer 1, repeat steps 2-10 on CoServer 2.
15 Right click on Networks under FTvirual Server Devices and select Add as shown in Figure 38. Displays a dialog in the right-hand pane that is used to reconfigure the redirected network adapter. 16 For each redirected adapter that you wish to reconfigure, select an adapter from CoServer 1 and an adapter from CoServer 2 and click OK. You cannot leave gaps in the redirected adapter numbers. You must reassign each adapter numbered above the one you just removed. 17 Select File Write Device Settings.
Figure 3-10 Network Adapters Uninstall Screen 22 Click OK in response to the Confirm Device Removal dialog. 23 Click No in response to the question Do you want to restart Windows? and exit the Windows Computer Management utility. 24 Right click on the Endurance taskbar icon and select Manage Endurance Configuration Restart. Click on OK in response to the Confirm Endurance Management Operation dialog. Endurance Device Redirector Windows removes the network adapter from the system.
Displaying and Editing Device Properties Follow the procedures described in the next table to display and edit device properties. Figure 3-11 shows an example of the screen on which you would display and edit disk properties. Click on the Edit button at the bottom of the screen to access the screen where you edit the properties. Figure 3-11 Sample Device Properties Screen To display and then edit the properties of an existing device: Step Action 1 Click on the physical device.
Step Action Notes 3 To edit device information: The Edit Properties page is displayed with the field(s) that you can change. a. Click the Edit button. b. Make the changes you want. 4 Click OK.
Resolving Conflicts Sometimes when major hardware or software errors occur, the device settings of the two CoServers may be mismatched. In such scenarios, a Conflicts branch is displayed on the Endurance system tree, with a yellow question mark icon. The devices with errors or inconsistencies are overlaid with the error icon, and the error is described at the top of the page, as shown in Figure 3-12.
Correct errors displayed in the Conflicts branch as follows: Step Action Notes 1 Click on the device that is in error. The Properties page for that device is displayed. The error is described at the top of the page. 2 Remove the device, and add it again. Follow the procedures for removing and adding the type of device in error. When the device settings are corrected, the Conflicts branch of the Endurance Configuration no longer displays. 3 Select File the settings.
3-42 Endurance FTvirtual Server Administrator’s Guide
Endurance Manager 4 This chapter describes the Endurance Manager. This chapter assumes that you are familiar with the Endurance terminology described in the Glossary. This chapter includes the following sections: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Starting the Endurance Manager . . . . . . . . . . . . . . . . . . 4-3 Using the Endurance Manager . . . . . . . . . . . . . . . . . . . 4-8 Monitoring the Endurance Configuration . . . . . . . . . . . . .
Overview The Endurance Manager is a complete management tool for your Endurance Configuration. The Endurance Manager is a standard Windows application that enables you to: • View the status of any Endurance Configuration component, including the FTvirtual Server, Virtual Servers, CoServers, adapters, keyboards, pointers, redirected devices, and network connections. • Manage the Endurance Configuration components. • Access statistics about the Endurance Configuration components.
Starting the Endurance Manager You can run the Endurance Manager on a remote workstation as well as locally on the Endurance Configuration you are monitoring. Use the Windows Start menu to start the Endurance Manager. From the Windows Programs menu, select Marathon Endurance Manager. You can also place a Endurance Manager shortcut in your startup group. You can also start the Endurance Manager by: • Right-clicking on the Endurance Taskbar icon and selecting Launch Endurance Manager.
The first time you launch the Endurance Manager, if your local host is a CoServer or FTvirtual Server in a Endurance Configuration, you will be connected to the last host automatically. If the local host is not in a Endurance Configuration, the Connect to Host dialog is displayed, and you can specify a host in a Endurance Configuration to monitor. Subsequent launches of the Endurance Manager connect you automatically to the last host to which you were successfully connected.
Main Window When you start the application, the Endurance Manager main window opens and displays the current status of your Endurance Configuration. A typical view of a fully operational Endurance Configuration is shown in Figure 4-2 and is described in Table 4-2. Your display includes the name of the Endurance Configuration shown in the main window.
You can also use the CoServer view to display the Endurance Configuration. Menu bar Title bar Tool bar FTvirtual Server Name Virtual Server on CoServer1 Virtual Server on CoServer2 CoServer Link CoServer Name Physical peripheral devices Name of the computer monitoring the Endurance Configuration Figure 4-3 Main Window CoServer View To switch your view of the Endurance Configuration, select View CoServer View or FTvirtual Server View, depending on the view you want.
Table 4-2 describes the settings in the main window.For definitions of Endurance terms, refer to the Glossary. Table 4-2 Main Window Contents Window Item Description Title Bar Displays the product name and the name of the Endurance FTvirtual Server or CoServer to which the Endurance Manager is connected. Menu Bar Contains Endurance Manager menu options, including File, View, Manage, and Help. These menu options are fully described in Menus (page 50).
Using the Endurance Manager The Endurance Manager uses the familiar Windows environment and navigation. You monitor the Endurance Configuration in windows, using menus, standard left and right mouse clicks, and tool-tip text. When you first launch the Endurance Manager, the main window displays the Endurance Configuration – either in the CoServer view or the FTvirtual Server view. Refer to Main Window starting on page 5 for a complete definition and description of the Endurance Configuration views.
Also you can work with components from the Component Status window. Right-click on the component, and pop-up menus appear with the available options for the component. Figure 4-6 Pop-up Menus on the Component Status Window See Setting Defaults for the Endurance Manager on page 4-10 and Component Status Window on page 4-13 for information about the Component Status Window.
Setting Defaults for the Endurance Manager The Endurance Manager has certain default characteristics as well as a number of options you can set. These settings determine how the Endurance Configuration is displayed, either as a CoServer view or as a FTvirtual Server view, whether the component and mirror status pages appear when you start the Endurance Manager, how tool-tip text is presented, and how often polling of data and counters occurs. To configure these options, select File Options.
Table 4-3 describes the settings in the Options window. Table 4-3 Options Window Settings Setting Description Show CoServer View Causes the CoServer view of the Endurance Configuration to be the default display in the main window. This view is a graphical representation of the entire Endurance Configuration from the perspective of the two CoServers.
Monitoring the Endurance Configuration With the Endurance Manager menus you can view the status and attributes of the Endurance Configuration and its components, gather statistics, and set timing and other device performance options. Viewing Status You can view the status of the Endurance Configuration, the status and properties of the Endurance Configuration components, and the status of the mirror copy operations. To view the states of the components: Select View Component Status....
Component Status Window The Component Status window displays the current state of all components in the Endurance Configuration, in either a CoServer or FTvirtual Server view, depending on whether the main window is showing the CoServer or FTvirtual Server view when you selected Component Status. Icons overlay the component icon indicating its state. The Endurance Component States sections describe the states of the Endurance Configuration and its components.
Table 4-4 describes the menus in the Component Status window. Table 4-4 Component Status Window Menu Description File Contains the option to close this window. View Contains the options to switch from the current view to the other view; the current view is grayed out. For example, if your current view is of the FTvirtual Server, you can select CoServer View to switch to that view.
State Icons and Colors The Endurance Configuration displays icons and/or colors to indicate the component states described in Table 4-5.
Figure 4-10 shows an example of a CoServer View main window with icons indicating states. Figure 4-10 CoServer View Showing Status Icons In this example, the Virtual Server on CoServer 1 and CoServer 1 have icons indicating the Offline, Degraded, and Disabled states.
Endurance Configuration States The Endurance Configuration can report the states described in Table 4-6. Table 4-6 Endurance Configuration States State Description Degraded • One of the Virtual Servers is not usable. • The Virtual Servers are usable, but one or more redirected devices is not usable or is not operating redundantly. In this state, application operations continue, but the Endurance Configuration is not fault tolerant, since it is not operating redundantly.
FTvirtual Server States The FTvirtual Server can report the states described in Table 4-7. Table 4-7 FTvirtual Server States State Description Degraded One Virtual Server is usable, and the other Virtual Server is not because it is Failed, Disabled, Offline, or it is otherwise not currently providing service to the FTvirtual Server. Degraded/ Unsynchable The FTvirtual Server cannot be synchronized because of a platform or software restriction. Failed The FTvirtual Server is unusable.
Virtual Server States The Virtual Servers can report the states described in Table 4-8. Table 4-8 Virtual Server States State Description Disabled A Virtual Server has been manually disabled. It is not providing service for the FTvirtual Server. When one Virtual Server is Disabled, the FTvirtual Server is not fault tolerant because it is not operating redundantly. If both Virtual Servers are Disabled, the FTvirtual Server is Failed.
CoServer States The CoServer can report the states described in Table 4-9: Table 4-9 CoServer States State Description Degraded A CoServer is not fully usable because of one of the following: Disabled • One or more of the redirected physical devices attached to the CoServer is not functional. • The CoServer’s Virtual Server is not running the FTvirtual Server. The CoServer has been manually disabled.
Table 4-9 CoServer States (Continued) State Description Transitioning/Joining The CoServer is not usable. The CoServers are in the process of becoming redundant. Transitioning/ Validating The CoServer is not usable. A physical path from one CoServer to the other CoServer is established and is verifying hardware and software requirements. Unknown The CoServer is not part of the Endurance Configuration and is not communicating with the other CoServer.
CoServer Link Adapter States The CoServer Link adapter connects the two CoServers to each other. The link adapter provides a path for communicating system states and status information between the CoServers. This path also provides the mirror copy data path. You can only view CoServer Link Adapter states when you are in the CoServer View. If you are in the FTvirtual Server View, open the Component Status window to view the CoServer Link Adapter states.
CoServer Logical Link States The CoServer Logical Link is a manageable entity representing the physical link adapters between the two CoServers and the virtual connections established between them. The CoServer Logical Link states are used for system management. The CoServer Logical Link can report the states described in Table 4-10: Table 4-11 CoServer Link Adapter States State Description Degraded One link adapter is usable. Two are required for fault tolerant operations.
Disk States You can see the disk states in both the CoServer and FTvirtual Server Views. You can also go to the Component Status window in either view to obtain details about all disks. A FTvirtual Server disk (for example, Disk0) may be mirrored or non-mirrored. A mirrored FTvirtual Server disk is a redundant device which consists of a pair of CoServer physical disks (for example, CoServer1.Disk0 and CoServer2.Disk0).
Table 4-12 Disk States (Continued) State Failed FTvirtual Server Disk Description Both physical disks are not usable because they are: • • Failed, Disabled, Offline, or Unknown while the FTvirtual Server was active. or Failed while the FTvirtual Server was shut down. CoServer Disk Description The physical disk has experienced a failure. It is no longer usable and requires repair. For non-mirrored disks: The physical disk has experienced a failure. It is no longer usable and requires repair.
Table 4-12 Disk States (Continued) State Offline/Missing FTvirtual Server Disk Description CoServer Disk Description The physical disk has not been found. This could be because it is physically disconnected, powered off, not properly configured, or otherwise not functional. For non-mirrored disks: The physical disk has not been found. This could be because it is physically disconnected, powered off, not properly configured, or otherwise not functional.
Ethernet Adapter States A FTvirtual Server Ethernet adapter (for example, Ethernet0) consists of a pair of CoServer Ethernet adapters that form redundant network paths to the FTvirtual Server (for example, CoServer1.Ethernet0 and CoServer2.Ethernet0). The Ethernet adapter can report the states described in Table 4-13: Table 4-13 Ethernet Adapter States State Degraded FTvirtual Server Ethernet Adapter Description One of the physical adapters is usable while the other one is not.
Table 4-13 Ethernet Adapter States State Offline FTvirtual Server Ethernet Adapter Description CoServer Ethernet Adapter Description Both physical adapters are not usable because they are Disabled, Offline, or Unknown while the FTvirtual Server was shut down. The adapter is not available for use. This could be because the CoServer to which it is attached is in a Failed, Disabled, or Offline state or because the adapter is not properly configured.
Input Devices States The FTvirtual Server input devices consist of a set of physical CoServer keyboard and mouse devices from each CoServer (for example CoServer1.Keyboard1 and CoServer2.Keyboard1, CoServer1.Pointer1 and CoServer2.Pointer1). The FTvirtual Server keyboard and mouse devices can report the states described in Table 4-14: Table 4-14 Input Devices States State FTvirtual Server Description CoServer Description Degraded One of the input devices is usable, but the other one is not.
CD-ROM, Medium Changers, and Tape Drives States FTvirtual Server CD-ROMs (for example, Cdrom0), medium changers (for example, MediumChanger0), and tape drives (for example, Tape0) are non-redundant devices which consists of a single CoServer physical device (for example, CoServer1.Cdrom0, CoServer1.MediumChanger0, CoServer1.Tape0).
Mirror Copy Status Window The Mirror Copy Status window displays mirror copy status information for the Endurance Configuration. Figure 4-11 shows the Mirror Copy Status window. Figure 4-11 Mirror Copy Status Window To control if this window is displayed when you start the Endurance Manager, use the Endurance Manager options, described in Options Window on page 4-10. Any active CoServer (one that is neither Offline, Failed, nor Disabled) provides complete current mirror copy status reports.
Component Properties Window To view the properties of a particular component, select the View menu and then select Properties.... The Component Properties window displays with Endurance Configuration highlighted and its relevant property information in the content pane. The Component Properties window contains the familiar Windows tree view in the left-hand pane, where you can expand and contract the tree branches to select a component.
Managing CoServer Link Communications Endurance uses default assumptions and policies regarding CoServer Link configuration, bandwidth, and latencies in order to optimize load balancing of synchronization and mirroring traffic. In most configurations, Endurance will automatically detect and correctly set default settings to optimize the CoServer Links. However, in certain configurations it may not be possible to automatically detect network configuration topology or characteristics.
CoServer Link Configuration When two CoServer Links are specified during installation, using the network setup wizard, the CoServer link configuration settings are enabled. The options for the link configuration settings are Dual Path (the default), and Dual Path With Shared Network. Choose Dual Path when the two CoServer Link paths are independent of each other in terms of their available bandwidth.
Knowing the base speed of each path allows Endurance to properly schedule message traffic. These settings are used separately from the Shared Bandwidth setting. In some cases it may be necessary to manually specify both a Shared Bandwidth setting as well as specific speeds for each CoServer Link. Dynamic Latency Measurement Endurance periodically measures transmission latency across the CoServer Link paths in order to determine the best route for its most latency-sensitive messages.
Managing SplitSite Operations Enabling SplitSite Operations SplitSite operations are enabled by default when you enter an appropriate Endurance SplitSite license key during the Endurance installation or upgrade process. When SplitSite is enabled, Endurance will enforce CoServer joining and fault handling policies specific to SplitSite and require the presence of a quorum server to enable fault tolerant operations. This behavior can be disabled using the Endurance Manager Splitsite Components Property page.
Identifying The Preferred CoServer For Surviving Failures Under some failure scenarios, Endurance software must make a decision about which CoServer to remove from the configuration to preserve application operations. A number of factors regarding the health of the CoServers as well as mirror copy status and direction are considered when the decision is made. However, in some circumstances, both CoServers may be considered as equal candidates for removal.
Configuring Quorum Services In complex SplitSite configurations consisting of multiple Quorum Services, CoServers jointly elect one accessible Quorum Service at any one time. The currently elected Quorum Service is the only one that a CoServer pair can use to resolve communication failures. The selection of the elected Quorum Service is, by default, arbitrary, but an election cannot occur without the participation of both CoServers.
displayed with a warning icon. These names may be selected as the preferred or alternate choice or you can directly enter a host name or IP address for the Quorum Service you would like to use. If the Quorum Service you are using resides on a host in an outside subnet, you must enter the IP address of the host.
The list displayed includes all known Quorum Services, including those that are permanently ineligible and those that are temporarily ineligible. A permanently ineligible Quorum Service includes any Quorum Service running at an incompatible revision level, or running on the local Endurance Configuration configuration (i.e., running on CoServer1, CoServer2, or the FTvirtual Server). An error icon ( ) indicates that a Quorum Service is permanently ineligible.
restored. In the event that a CoServer is blocking boot, and you know for certain that the remote CoServer and the Quorum Service are completely removed from service (due to a site disaster, for instance or forced shutdown), you can manually force the boot of a Virtual Server on the operational CoServer. To do this, start the Endurance Manager and select the View Properties....
Link. After using this option and when restoring the remote CoServer to service, you must follow the set of steps outlined below. Failure to follow these steps may result in split-brain operation and possible data corruption. 1. Identify the currently elected Quorum Service by inspecting the SplitSite property page. 2. Stop the elected Quorum Service using the Windows Services control panel on the server hosting the Quorum Service or disconnect the Quorum Server from the network entirely. 3.
Managing the Components Using the Manage menu options, you can perform various tasks on the Endurance Configuration components. Alternatively, you can use the context-sensitive pop-up menus accessed by right-clicking on components viewed from the Main Window or Component Status page to complete tasks. For information about working with Endurance Manager menus, see Using the Endurance Manager on page 4-8. The following sections describe the options you can select for the components.
FTvirtual Server Options Table 4-17 describes the options for the FTvirtual Server. Table 4-17 FTvirtual Server Options Option Description Notes Restart Shuts down the FTvirtual Server and then restarts it. The FTvirtual Server reboots, as defined by the Virtual Server Automatic Start setting. Resynchronize Resynchronizes the non-functioning Virtual Server with the running Virtual Server. Shutdown Shuts down the FTvirtual Server. Start Starts the FTvirtual Server after a reboot or power cycle.
CoServer1 and CoServer2 Options Table 4-18 describes the options for the CoServer. Table 4-18 CoServer Options Option Description Notes CoServer Disable Removes the specified CoServer from the active Endurance Configuration. Enable Enables the specified CoServer that was Disabled or Failed. Shutdown Removes the specified CoServer from the Endurance Configuration and shuts down the CoServer.
Table 4-18 CoServer Options (Continued) Option Description Notes Datagram Counters Displays a dialog box where you control and display statistics for adapters that are bound to the Endurance Datagram Service. Events Log Checkpoint Event Places a checkpoint event in the event log. Use this option to insert a checkpoint in the system event log for diagnostic purposes. Remove Events Removes any events from pending queues. Use this option for diagnostic purposes or maintenance only.
Disk Options To work with disks, select either mirrored or non-mirrored disks, and then select a particular disk. Table 4-20 describes the options for the disks. Table 4-20 Disk Options Option Description Notes Mirrored Disks Diskn The mirror set name Restart Mirror Copy Restarts a failed mirror copy for a disk. MIrror Copy Status. . . Raises the Mirror Copy Status window for the selected disk. CoServern.Diskn Disable Disables an individual mirrored disk that is Good or Offline.
Networks Options Table 4-21 describes the options for the Ethernet adapters. Table 4-21 Network Options Option Description Notes Disable Disables the Ethernet adapter. Disabling the Ethernet adapter causes failover to the Ethernet adapter on the other CoServer. Enable Enables the disabled Ethernet adapter. Counters... Displays the Counters window for the Ethernet adapter where you can export data, reset and update the error counters and statistics. Ethernetn CoServern.
Input Devices Options Table 4-22 describes the options for the input devices. Table 4-22 Input Device Options Option Description Notes Expire Arbitration Forces the arbitration timeout to expire and switches the active input devices to the specified CoServer. For this option to be valid, arbitration timeout must be enabled. CoServern Set Input to FTvirtual Server Redirects input from the input devices on the selected CoServer to the FTvirtual Server.
Menus The main window contains the File, View, Manage, and Help menu options. File Menu The File menu contains the options shown in Figure 4-12. This menu enables you to control certain Endurance Configuration functions. For information about the File menu options, see Connecting to the Host on page 4-3 and Setting Defaults for the Endurance Manager on page 4-10 Figure 4-12 File Menu View Menu The View menu contains the options shown in Figure 4-13.
Manage Menu The Manage menu displays the options shown in Figure 4-14. For information about the Manage menu, see Manage Menu on page 4-51. Figure 4-14 Manage Menu Help Menu Figure 4-15 shows the Help menu, which enables you to access online help and certain Endurance Configuration information.
Table 4-23 describes the Help menu options. Table 4-23 Help Menu Options Option Description About... Displays the Help About box, indicating the version number, patent numbers, and copyright information. Contents... Displays the contents page for the Endurance online help. Revisions... Displays the Component Properties window with Revisions highlighted in the left-hand pane and component revision information in the right-hand pane.
Using the Endurance Manager on a Remote Workstation You can use the Endurance Manager on a remote workstation to monitor and administer your Endurance Configuration. To do so, connect the Endurance Manager on a remote workstation to the Endurance Configuration using a LAN, a RAS connection, or a virtual private network over the Internet.
Installing and Uninstalling the Remote Endurance Manager Prerequisites for a workstation on which you want to install the Endurance Manager: • Windows 2003, Windows 2000 or Windows XP and any Microsoft requirements for running these operating systems. To install the Endurance Manager on a remote workstation: • Browse the Endurance CD to locate and then launch setup.exe. • When the installation program runs, select Remote Management and follow the prompts to complete the installation.
Endurance Configuration. Once this is accomplished, you can use all capabilities of the Endurance Manager. Without administrative privilege, you can monitor but not manage the Endurance Configuration remotely.
4-56 Endurance FTvirtual Server Administrator’s Guide
Troubleshooting 5 This chapter describes the general methods of diagnosing, monitoring, and managing faults. It also provides an overview of the troubleshooting process. This chapter assumes that you are familiar with the Endurance terminology described in the Glossary. This chapter contains the following sections: Monitoring and Managing Faults Diagnosing Faults . . . . . . . . . . . . . . . . . 5-2 . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Isolating Faults . . . . . . . . . . . . . . . .
Monitoring and Managing Faults Because the Endurance Configuration is fault tolerant, when a fault occurs (for example, a failed network adapter), the Endurance FTvirtual Server continues operating. Even though the Configuration is still operational, any failure to a faulted component’s redundant counterpart affects the server’s availability. To return the Endurance Configuration to a fully fault tolerant state, you need to complete some repair procedures. Repairs involve several steps.
To reconfigure the Endurance System Management Service port number of any component in your Endurance FTvirtual Server, in the Registry for that component, change the value for the parameter: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MtcMgmtSrv\Parame ters\ORBPortNumber After you have modified and saved the Registry, you must restart the Endurance System Management Service.
Diagnosing Faults You can use any of the methods in Table 5-1 to receive notifications and diagnose faults. Table 5-1 Diagnosing Faults Method Description Refer to . . . Endurance Manager Use the main window to determine the current status of any Endurance component. Chapter 4 Third-party management frameworks Utilities that can be used to monitor system components and status.
Isolating Faults If you have local access to the Endurance Configuration, check the following in the order that they are listed: Step Action Notes 1 Using the main window in the Endurance Manager, note any components that are not Good, or Transitioning. 2 Because the two CoServers may have slightly different error messages, depending on the state of the Endurance Configuration, check the Windows Event Viewer for Endurance messages beginning with Coservers.
Correcting Faults After isolating the fault, you can correct the condition by: • Following instructions in the Action section of a message. • Completing a maintenance procedure specific to the device or scenario diagnosed. For information about these procedures refer to Endurance’s support site.
Endurance Tools 6 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 the Glossary. This chapter includes the following sections: MTCCONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Installation Verification Procedure (IVP) . . . . . . . . . . . . . 6-4 MTCEINFO Utility . . . . . . . . . . . . . . . . . . . . . . . . .
MTCCONS You can execute Endurance commands from an MS-DOS window. The primary purpose for using MTCCONS (Endurance Management console commands) is to execute scripts for system validation (test) or routine 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 6-1 MTCCONS Parameters (Continued) Parameter Description -width Screen buffer width 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 Show CS1.SCP Computer Names • The MTCCONS syntax is not case sensitive. • You can use abbreviated syntax by entering the minimum characters that make the command unique.
Installation Verification Procedure (IVP) The Installation Verification Procedure runs automatically each time a CoServer boots. It evaluates the Endurance Configuration’s Ethernet bindings and reports its findings to the event log on the local CoServer. You can also run the installation verification procedure whenever you want to re-evaluate the Ethernet bindings. From the Windows Start menu, select Programs Marathon Endurance Networking Run Diagnostics.
MTCEINFO Utility The MTCEINFO utility is a command line application that displays Ethernet adapter information. You can run this utility from any CoServer 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 a CoServer.
6-6 Endurance FTvirtual Server Administrator’s Guide
Endurance VFT MIB and SNMP Implementation A This chapter describes the Endurance FTvirtual Server (VFT) SNMP MIB and the implementation of SNMP, which enables you to view management data and receive notification of state changes from the SNMP trap mechanism. You can use SNMP in conjunction with thirdparty products to obtain a complete view of the state of your virtual server’s health and its performance.
Overview of the Endurance VFT SNMP MIB and Extension Agent This section provides an overview of the Endurance VFT implementation of SNMP, including the Endurance VFT MIB, and the Endurance VFT SNMP extension agent. Refer to Microsoft documentation for detailed information and references materials about MIBs and SNMP concepts.
The following files are associated with the SNMP MIB browser and the extension agent. These files ensure that you always have access to the correct MIB files for the DLL files you have installed: Table A-1 Endurance VFT MIB and Extension Agent Files File Description MtcSnmp.dll Endurance VFT SNMP extension agent Mtcmsgs.dll Endurance VFT message file MarathonEnduranceVftInt.MIB An SMIv1 file that contains definitions of all manageable objects and SNMP traps.
MIB Naming Tree Figure A-1 depicts the MIB naming tree, showing the specific position of the Marathon Technologies domain in the standard MIB naming tree. All information related to Marathon Technologies and its products appears in the marathonTechnologies (3390) entry in the MIB naming tree.
iso.org.dod.internet.private.enterprises.marathonTechnologies (1.3.6.1.4.1.3390) • marathonTechnologiesIdentity (1) •mtcProducts (1000) • mtcRegistrations (10) • mtcExperimental (200) • mtcCommon (100) • • mtcExperimentalProducts (1000) Figure A-2 Marathon Sub-tree of the MIB Naming Tree Table A-2 describes the nodes within the Marathon sub-tree of the MIB.
Table A-2 Subtree Nodes within the Marathon MIB (Continued) Name Child Number mtcExperimentalProducts 1000 Description An intermediate node under mtcExperimental in which experimental products are registered prior to moving them to the mtcProducts sub-tree later. Note: The child number of this node matches that of mtcProducts. Endurance VFT MIB Sub-tree The MIB for Marathon’s Endurance FTvirtual Server product is located in the module MarathonEnduranceVftInt.MIB.
Table A-3 describes the subnodes defined under the Endurance Vft MIBv1 node of the MIB tree. Table A-3 Endurance Vft MIBv1 Sub-tree Nodes Name Child Number Description mtcEnduranceVftMIBv1Objects 1 Contains all manageable objects for the Endurance FTvirtual Server product mtcEnduranceVftMIBv1Traps 2 Contains all traps (notification events) for the Endurance FTvirtual Server product. Manageable Objects The MIB sub-tree contains the objects associated with the Endurance FTvirtual Server product.
The MIB sub-tree that contains the Endurance FTvirtual Server manageable objects is shown in Figure A-4. mtcEnduranceVftMIBv1.
SNMP Traps The Endurance FTvirtual Server SNMP extension agent monitors the state of the entire FTvirtual Server and generates SNMP traps (notification events) when changes occur in the states of the FTvirtual Server or the server components. Changes are noted for the Endurance FTvirtual Server components listed previously in the section Manageable Objects.
SNMP traps report three system information variables that are present at the beginning of each trap. Table A-5 lists and describes these system information variables. Table A-5 System Information Variables At the Beginning of All Traps Variable Name Variable Type Variable Description mtcEnVftConfigurationAgentSystemName Octet string The host name of the system on which the Endurance SNMP extension agent is running.
Table A-6 System Information Variables At the End of All Traps (Continued) Variable Name Variable Type Variable Description mtcEnVftDeviceNamePreviousSeverity Enumerated Integer The severity level of the device state prior to the last state transition mtcEnVftDeviceNameLastStateChangeReason Enumerated Integer The reason for the last device state transition mtcEnVftDeviceNameLastStateChangeTime Octet string The date and time of the last device state transition.
Table A-7 Device Trap Names and Child Numbers (Continued) Device Name Trap Names Associated with the Device Trap Severity Child Number NonMirroredDisk • mtcEnVftTrapNonMirroredDiskError • Critical • 1021 • mtcEnVftTrapNonMirroredDisk Unknown • Unknown • 1022 • mtcEnVftTrapNonMirroredDisk Warning • Major • 1023 • mtcEnVftTrapNonMirroredDisk Informational • Minor • 1024 • mtcEnVftTrapNonMirroredDiskGood • Informational • 1025 LogicalCD LogicalTape LogicalNetwork LogicalKe
Table A-7 Device Trap Names and Child Numbers (Continued) Device Name Trap Names Associated with the Device Trap Severity Child Number LogicalPointer • mtcEnVftTrapLogicalPointerError • Critical • 1071 • mtcEnVftTrapLogicalPointer Unknown • Unknown • 1072 • mtcEnVftTrapLogicalPointerWarning • Major • 1073 • mtcEnVftTrapLogicalPointer Informational • Minor • 1074 • mtcEnVftTrapLogicalPointerGood • Informational • 1075 • mtcEnVftTrapLogicalMedium ChangerError • Critical
Table A-7 Device Trap Names and Child Numbers (Continued) Device Name Trap Names Associated with the Device Trap Severity Child Number CoServer1Disk • mtcEnVftTrapCoServer1DiskError • Critical • 4011 • mtcEnVftTrapCoServer1Disk Unknown • Unknown • 4012 • mtcEnVftTrapCoServer1Disk Warning • Major • 4013 • mtcEnVftTrapCoServer1Disk Informational • Minor • 4014 • mtcEnVftTrapCoServer1DiskGood • Informational • 4015 • mtcEnVftTrapCoServer1CDError • Critical • 4021 • mtc
Table A-7 Device Trap Names and Child Numbers (Continued) Device Name Trap Names Associated with the Device Trap Severity Child Number CoServer1Keyboard • mtcEnVftTrapCoServer1Keyboard Error • Critical • 4051 • mtcEnVftTrapCoServer1Keyboard Unknown • Unknown • 4052 • mtcEnVftTrapCoServer1Keyboard Warning • Major • 4053 • mtcEnVftTrapCoServer1Keyboard Informational • Minor • 4054 • mtcEnVftTrapCoServer1Keyboard Good • Informational • 4055 • mtcEnVftTrapCoServer1PointerErro
Table A-7 Device Trap Names and Child Numbers (Continued) Device Name Trap Names Associated with the Device Trap Severity Child Number CoServer2 • mtcEnVftTrapCoServer2Error • Critical • 5001 • mtcEnVftTrapCoServer2Unknown • Unknown • 5002 • mtcEnVftTrapCoServer2Warning • Major • 5003 • mtcEnVftTrapCoServer2 Informational • Minor • 5004 • mtcEnVftTrapCoServer2Good • Informational • 5005 • mtcEnVftTrapCoServer2DiskError • Critical • 5011 • mtcEnVftTrapCoServer2Disk U
Table A-7 Device Trap Names and Child Numbers (Continued) Device Name Trap Names Associated with the Device Trap Severity Child Number CoServer2NIC • mtcEnVftTrapCoServer2Keyboard Error • Critical • 5041 • mtcEnVftTrapCoServer2Keyboard Unknown • Unknown • 5042 • mtcEnVftTrapCoServer2Keyboard Warning • Major • 5043 • mtcEnVftTrapCoServer2Keyboard Informational • Minor • 5044 • mtcEnVftTrapCoServer2Keyboard Good • Informational • 5045 • mtcEnVftTrapCoServer2PointerError •
Table A-7 Device Trap Names and Child Numbers (Continued) Device Name Trap Names Associated with the Device Trap Severity Child Number CoServer2Link Adapter • mtcEnVftTrapCoServer2LinkAdapter Error • Critical • 5081 • mtcEnVftTrapCoServer2LinkAdapter Unknown • Unknown • 5082 • mtcEnVftTrapCoServer2LinkAdapter Warning • Major • 5083 • mtcEnVftTrapCoServer2LinkAdapter Informational • Minor • 5084 • mtcEnVftTrapCoServer2LinkAdapter Good • Informational • 5085 • mtcEnVftTrapC
Table A-8 Optional Device Specific Variables (Continued) Device Name Optional Variable Name Variable Type Variable Description LogicalCD • mtcEnVftLogicalCDDisk Name • Octet String • The name of the FTvirtual Server CDROM drive • mtcEnVftLogicalCDDisk LogScsiIds • Octet String • The FTvirtual Server CDROM drive SCSI ID • mtcEnVftLogicalTapeDisk Name • Octet String • The name of the FTvirtual Server tape drive • mtcEnVftLogicalTapeDisk LogScsiIds • Octet String • The FTvirtual Ser
Table A-8 Optional Device Specific Variables (Continued) Device Name Optional Variable Name Variable Type Variable Description CoServer1CD • mtcEnVftCoServer1CD Name • Octet String • The name of the CDROM drive • mtcEnVftCoServer1CD CoServerId • Integer • ID of the CoServer on which the physical CDROM drive resides • mtcEnVftCoServer1CD PhyScsiIds • Octet string • The physical CDROM drive SCSI ID • mtcEnVftCoServer1Tape Name • Octet String • The name of the tape drive • mtcEnVf
Table A-8 Optional Device Specific Variables (Continued) Device Name Optional Variable Name Variable Type Variable Description CoServer1Link Adapter • mtcEnVftCoServer1Link AdapterName • Octet string • The name of the link adapter.
Table A-8 Optional Device Specific Variables (Continued) Device Name Optional Variable Name Variable Type Variable Description CoServer2 Pointer • mtcEnVftCoServer2 PointerName • Octet string • The name of the pointer device • mtcEnVftCoServer2 PointerCoServerId • Integer • ID of the CoServer on which the pointer device resides • mtcEnVftCoServer2 MediumChangerName • Octet string • The name of the medium changer • mtcEnVftCoServer2 MediumChangerCo ServerId • Integer • ID of the C
Configuring SNMP to Send Traps to Remote Management Systems At any time after the SNMP files are installed, you can configure SNMP to send traps to additional remote management systems, which can be running Windows or any other operating system that supports the SNMP protocol. To enable the receipt of the traps, you must also configure the remote management systems. If the remote client is a Windows server, it must be running the Windows SNMP Trap Service.
Step Action Note 6 On each Windows Remote Management System: You can also adjust the settings so that the startup of the Trap Service is automatic, manual, or disabled. Refer to Microsoft’s SNMP documentation for information about each of these options. A-24 • Select Services, then double click on SNMP Trap Service. • In the SNMP Trap Service Properties (Local Computer) dialog box, click Start in the Service Status area to start the SNMP Trap Service.
Glossary boot disk. A SCSI disk that contains the Windows operating system. For the Endurance FTvirtual Server , the boot disk for the FTvirtual Server is a member of a mirrored disk set that physically resides on the CoServers. The boot disk for a CoServer is non-mirrored and local to that CoServer. booting. A system process that includes passing POST and loading the system’s Windows operating system. callout.
Disabled. A state indicating that a Endurance component is configured as, or has been, manually disabled. In this state, a component is not operating as part of the Endurance Configuration. For specific information on this state as it applies to particular components, refer to the Endurance FTvirtual Server Administrator’s Guide. enable. Enables a previously disabled or failed device for use in the Endurance Configuration.
field replaceable unit. See FRU. FTvirtual Server. The fault-tolerant operating system environment that runs in lockstep on and is synchronized between two CoServers. The FTvirtual Server is where you install and run applications and also where the majority of the interaction with the Endurance FTvirtual Server occurs. When running on a single CoServer, the FTvirtual Server is degraded but remains available. FTvirtual Server boot disk.
mirroring. A process for creating and maintaining a set of identical disk images on separate physical SCSI disks. See mirror set. non-identical disks. SCSI disks configured as a mirror set. The disks may be different sizes, and may also have different model numbers, or be from different manufacturers. non-mirrored device. A device in a Endurance Configuration that does not have a redundant counterpart, such as a tape drive or a CD-ROM.
Redirected disk. A FTvirtual Server redirected disk that is composed of one disk from each CoServer. For example, a redirected mirror set identified by the name “Disk0” is composed of two physical disks: one residing on CoServer1 and the other residing on CoServer2. redirection. Identifies when a system uses a device that is not directly controlled by that system. For example, access to the Ethernet and SCSI devices is redirected by Endurance software from the FTvirtual Server to the CoServer. redirector.
Unknown. The Endurance software cannot determine the state of the component. This can be caused by the loss of communication when a remote CoServer is shut down. UPS. Uninterruptable Power Supply. A batteryoperated device that provides a limited supply of electrical power in the event of a power failure. valid disk. A disk in a mirror set whose contents are correct and up to date. Typically, a mirror set has two valid disks. It is also possible for there to be no valid disks in a mirror set.
