ServerNet Nomadic Disk User’s Guide Abstract This guide explains remote mirroring and fiber-optic switching of 45xx disk drives connected to Compaq NonStop™ Himalaya S-series servers, describes how to perform planned and unplanned switchovers, and includes a command reference for both the switch command interface (SWCI) and the Nomadic Disk Manager. Product Version N.A. Supported Releases This publication supports the G06.
Document History Part Number Product Version Published 425485-001 N.A. December 2001 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice. Please check with your authorized representative to make sure you have the most recent information.
ServerNet Nomadic Disk User’s Guide Index Examples Figures Tables What’s New in This Guide vii Guide Information vii New and Changed Information About This Guide vii ix What’s in This Guide ix Where to Get More Information Your Comments Invited Notation Conventions x x xi 1.
3. Installing and Configuring the Nomadic Disk Manager Contents 3. Installing and Configuring the Nomadic Disk Manager Nomadic Disk Manager Files 3-2 Installing the Nomadic Disk Manager 3-3 Configuring the Nomadic Disk Manager Nomadic Disk Configuration File 3-5 3-5 Nomadic Disk Manager Configuration Statements 3-9 4.
6. Switch Command Interface (SWCI) Contents 6.
A. Part Numbers Contents HISTORY Command 7-11 LISTDEV Command 7-12 7-13 LISTOPENS Command OUT Command 7-14 RESET Command 7-15 SEGMENTS Command SQL Command 7-17 STATUS Command TAKE Command TMF Command UP Command 7-16 7-17 7-19 7-21 7-21 VOLUMES Command 7-22 A. Part Numbers B.
Tables Contents Tables Table 3-1. Files in the Nomadic Disk Manager Subvolume 3-2 Table 6-1. Summary of SWCI Commands 6-8 Table A-1.
Contents ServerNet Nomadic Disk User’s Guide—425485-001 vi
What’s New in This Guide Guide Information ServerNet Nomadic Disk User’s Guide Abstract This guide explains remote mirroring and fiber-optic switching of 45xx disk drives connected to Compaq NonStop™ Himalaya S-series servers, describes how to perform planned and unplanned switchovers, and includes a command reference for both the switch command interface (SWCI) and the Nomadic Disk Manager. Product Version N.A. Supported Releases This publication supports the G06.
What’s New in This Guide New and Changed Information ServerNet Nomadic Disk User’s Guide—425485-001 viii
About This Guide This guide describes how to perform a switchover using the Nomadic Disk subsystem. It is intended for system managers and operational personnel. What’s in This Guide Section Title Description 1 ServerNet Nomadic Disk Overview Explains nomadic disk concepts such as remote mirroring and fiber-optic switching. Describes database product considerations when switching.
Where to Get More Information About This Guide Where to Get More Information Topic Manual System configuration SCF Reference Manual for G-Series Releases Configuring disk drives SCF Reference Manual for the Storage Subsystem Managing disk drives SCF Reference Manual for the Storage Subsystem Installing Compaq NonStop™ Himalaya S-series systems Himalaya S-Series Hardware Installation Guide Installing the ServerNet Nomadic Disk Subsystem ServerNet Nomadic Disk Subsystem Installation and Service G
Notation Conventions About This Guide Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual.
Notation Conventions About This Guide LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]...
Notation Conventions About This Guide Line Spacing If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]...
Notation Conventions About This Guide A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list might be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
1 ServerNet Nomadic Disk Overview Remote Disk Drive Mirroring 1-2 Physically Switching the Disk Drives 1-2 Data Paths and Disk Drive Ownership Before a Switchover Data Paths and Disk Drive Ownership After a Switchover Logically Switching a Database Supported Database Products 1-5 1-5 Unsupported Database Products 1-5 ServerNet Nomadic Disk User’s Guide— 425485-001 1 -1 1-3 1-4
ServerNet Nomadic Disk Overview Remote Disk Drive Mirroring The ServerNet Nomadic Disk subsystem is a combination of hardware and software that allows you to mirror 45xx disk modules at remote nodes and switch the ownership of the disk drives in those modules from one node to another.
Data Paths and Disk Drive Ownership Before a Switchover ServerNet Nomadic Disk Overview Data Paths and Disk Drive Ownership Before a Switchover Figure 1-1 illustrates the active data paths before a switchover. • • The thick solid lines designate active data paths, which are between the primary node \PRI and the primary disk drives and mirror disk drives. The primary disk drives are located with and owned by the primary node.
Data Paths and Disk Drive Ownership After a Switchover ServerNet Nomadic Disk Overview Data Paths and Disk Drive Ownership After a Switchover To manage outages, both the primary disk drives and remotely located mirror disk drives can be switched to the backup node. When a outage brings down the primary node, the ownership of the disk drives can be switched to \BCK. After a switchover, the active data paths are as shown in Figure 1-2.
ServerNet Nomadic Disk Overview Logically Switching a Database Logically Switching a Database While a physical switch changes the connection of a device from one node to another node, a logical switch allows the backup node to access a database after a physical switch occurs. Logical switching fixes naming inconsistencies that arise when a database is moved to a node with a different node name and node number. Supported Database Products Enscribe contains features that support logical switching.
ServerNet Nomadic Disk Overview Unsupported Database Products ServerNet Nomadic Disk User’s Guide— 425485-001 1 -6
2 Nomadic Disk Hardware and Software Hardware and Software Restrictions Nomadic Disk Software 2-2 2-2 Nomadic Disk Manager 2-2 Switch Command Interface (SWCI) 2-2 Nomadic Disk Hardware 2-3 Required Hardware for All Configurations 2-3 Required Hardware for Remote Mirroring 2-3 Required Hardware for Fiber-Optic Switching 2-4 ServerNet Nomadic Disk User’s Guide—425485-001 2 -1
Nomadic Disk Hardware and Software Hardware and Software Restrictions Hardware and Software Restrictions The following are not supported by the ServerNet Nomadic Disk subsystem: • • • NonStop Himalaya S7000 servers Disk drives other than 45xx disk drives. Only 45xx disk drives can be Nomadic volumes. $SYSTEM or any other internal disk drive is not supported. The following on a Nomadic volume: ° NonStop Transaction Manager/MP (TM/MP) or any software that depends on it, such as Compaq NonStop SQL/MP.
Nomadic Disk Hardware Nomadic Disk Hardware and Software Nomadic Disk Hardware The hardware needed in your Nomadic Disk configuration depends on whether you have remote mirroring or fiber-optic switching, and the distances between the 6760 ServerNet device adapter (ServerNet/DA) and the disk modules.
Nomadic Disk Hardware and Software Required Hardware for Fiber-Optic Switching Remote mirroring up to 40 kilometer also requires: Hardware Component Function For Troubleshooting Information, refer to: SEM Increases the maximum connection distance of a Gigabit Ethernet bit stream up to 40 kilometers Contact professional services SMF cables Connects SEMs to each other Contact professional services Multimode fiber-optic (MMF) cables Connects an MSEB MMF PIC to a SEM Contact professional services
Required Hardware for Fiber-Optic Switching Nomadic Disk Hardware and Software Figure 2-1.
Nomadic Disk Hardware and Software Required Hardware for Fiber-Optic Switching ServerNet Nomadic Disk User’s Guide—425485-001 2 -6
3 Installing and Configuring the Nomadic Disk Manager Nomadic Disk Manager Files 3-2 Installing the Nomadic Disk Manager 3-3 Configuring the Nomadic Disk Manager Nomadic Disk Configuration File 3-5 3-5 Nomadic Disk Manager Configuration Statements 3-9 ServerNet Nomadic Disk User’s Guide—425485-001 3 -1
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Manager Files Nomadic Disk Manager Files Table 3-1 describes the files in the Nomadic Disk Manager subvolume. Table 3-1. Files in the Nomadic Disk Manager Subvolume File Description AAREADME A text file describing the contents of the subvolume. CREATOR A command file used to create a TACL segment file. This file uses the NOMADSRC file to create the NOMADSEG file.
Installing and Configuring the Nomadic Disk Manager Installing the Nomadic Disk Manager Installing the Nomadic Disk Manager Caution. The Nomadic Disk Manager subvolume must be on a volume that is not Nomadic. This version of Nomadic Disk Manager is supported only on Compaq NonStop™ Himalaya S-series servers. On both the primary node and backup node, install the independent product, Nomadic Disk Manager: 1.
Installing and Configuring the Nomadic Disk Manager Installing the Nomadic Disk Manager Example 3-1. Sample TACLCSTM File Included With the Nomadic Disk Manager ?TACL MACRO #set #informat tacl [#if not [#variableinfo /existence/ :nomad] |then| #def :nomad directory shared $SYSTEM.NOMADIC.NOMADSEG ]== end if #push ulist #set ulist [#uselist] [#if not [#charfind ulist 1 :utils.1:dp.1] |then| #set #uselist [#uselist] :utils:dp ] == end if [#if not [#charfind ulist 1 :nomad.
Installing and Configuring the Nomadic Disk Manager Configuring the Nomadic Disk Manager Configuring the Nomadic Disk Manager Each of the two nodes involved in a ServerNet Nomadic Disk implementation has its own configuration. Furthermore, certain management duties must be performed when the Nomadic volumes are not owned. Nomadic Disk Configuration File A Nomadic Disk configuration file is interpreted each time you start the Nomadic Disk Manager. The Manager operates on the objects defined in that file.
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Configuration File Configuration File Examples The following are example NDCONFIG files for a basic configuration for each of the two nodes participating in a ServerNet Nomadic Disk configuration. For detailed descriptions of all configuration statements, see Nomadic Disk Manager Configuration Statements on page 3-9.
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Configuration File Configuration File Example for \TELE File \TELE.$SYSTEM.NOMADIC.NDCONFIG ! ! ! PATH SWITCH SLOT OWNERSHIP ! NAME NAME NUMBER POSITION SET PATH P $SM01.#A 1 STRAIGHT SET PATH B $SM01.#A 2 STRAIGHT SET PATH M $SM02.#A 1 CROSSED SET PATH MB $SM02.
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Configuration File Configuration File Example for \OMS1 File \OMS1.$SYSTEM.NOMADIC.NDCONFIG ! ! PATH SWITCH SLOT ! NAME NAME NUMBER SET PATH P $SM01.#A 1 SET PATH B $SM01.#A 2 SET PATH M $SM02.#A 1 SET PATH MB $SM02.
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Manager Configuration Statements Nomadic Disk Manager Configuration Statements Statement Purpose ADD DEFINE Configures an alias for a character string. 3-10 ADD SEGMENT Add the definition of a segment to the configuration. 3-11 PROCESS Control where the specified utility executes, and at what priority. 3-12 SET PATH Modify the segment template, in preparation for a subsequent ADD SEGMENT statement.
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Manager Configuration Statements ADD DEFINE Statement Use the ADD DEFINE statement to configure an alias for a character string. Whenever the DEFINE name is encountered in a command, the DEFINE is evaluated at that time, before the command is executed. ADD DEFINE user-define-name character-string user-define-name is any name that is meaningful to the user that does not conflict with an existing Manager command.
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Manager Configuration Statements ADD SEGMENT Statement The ADD SEGMENT statement adds the definition of a segment to the configuration. ADD SEGMENT seg , { DATA | SPARE } seg specifies the name of a segment you want to add to the configuration file. You can use any valid TACL variable name. DATA specifies that the segment has Nomadic Disk data and is not a SPARE segment. SPARE Do not use this parameter.
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Manager Configuration Statements PROCESS Statement The Nomadic Disk Manager executes and communicates with several utilities. Use the PROCESS statement to control where a specified utility executes and at what priority. Each utility can have its own PROCESS statement, though none is required.
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Manager Configuration Statements Examples The following example specifies that the FUP utility should run in processor 3 with a priority of 151: PROCESS FUP CPU 3, PRI 151 Special Note on Parallel Processing Because FUP and SWCI perform processing sequentially, each of these utilities needs only a single process statement.
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Manager Configuration Statements SET PATH Statement The SET PATH statement modifies the segment template to be used by a subsequent ADD SEGMENT statement. A segment, as defined by the Nomadic Disk Manager, is a pair of 45xx modules. Each 45xx module has two paths to it, so a segment has four paths. Use the SET PATH statement to: • • Associate a switch card with one of the four paths to a segment.
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Manager Configuration Statements SET VOL Statement The SET VOL statement modifies the segment template to be used by a subsequent ADD SEGMENT statement. The SET VOL statement adds a disk volume to a segment. Each segment definition can have from one to eight SET VOL statements. SET VOL { $name } { $ldev [ ( $alt-name ) ] } name specifies the name of a disk volume. This device must exist. Caution. Do not use the $ldev parameter.
Installing and Configuring the Nomadic Disk Manager Nomadic Disk Manager Configuration Statements ServerNet Nomadic Disk User’s Guide—425485-001 3- 16
4 Switch Modules Switch Controller Card 4-3 Front Panel of a Switch Controller Card 4-3 SCC Key Switch 4-4 SCC Temperature Sensors 4-4 SCC LEDs 4-5 Alarm Port 4-6 Switch Card 4-7 Faceplate of a Switch Card 4-7 Switch Card Toggle Switches 4-8 Switch Card LEDs 4-9 ServerNet Nomadic Disk User’s Guide—425485-001 4 -1
Switch Modules Switch modules to control ownership of the disk modules and data paths. To control switch modules, you can either: • • Physically toggle a switch on a switch card Use software such as the ServerNet Nomadic Disk switch command interface (SWCI) or Nomadic Disk Manager The following figure shows the faceplate of a switch module.
Switch Modules Switch Controller Card Switch Controller Card A switch controller card (SCC), installed in slot 0 of a switch module, connects to two nodes.
Switch Modules SCC Key Switch SCC Key Switch The key switch on the SCC allows you to access switch cards either locally or remotely by turning the key switch from LOCAL (L) to REMOTE (R). • When the key switch is in the LOCAL position: • • You can change the position of the switches by manually moving the toggle switch on the switch cards. You can check the status of the switch module using SWCI status commands.
Switch Modules SCC LEDs SCC LEDs Caution. Do not attempt to replace the switch module, attempting to do so could damage the equipment. For repair and replacement, contact professional services. The ServerNet Nomadic Disk Subsystem Installation and Service Guide is available to professional services in the TIM Hardware Service and Maintenance Collection. The front panel of the SCC contains the following LEDs..
Switch Modules Alarm Port Alarm Port If an optional external alarm is connected to the external alarm port and the alarm relays are energized, the alarm is activated under the following conditions: • • • • • SWCI sends a command to activate the alarm. Sensor 1 or Sensor 2 temperature is out of range. Voltage for the power supply is out of range. The switch module fails the power-on self-test (POST). Certain environmental faults occur. For these faults, refer to Environmental Alert Messages on page 6-50.
Switch Modules Switch Card Switch Card Switch cards, which occupy slots 1 through 8 of a switch module, control the path of fiber-optic signals between the 45xx disk modules and one of two nodes. A switch card has two positions: straight and crossed. A switch module connects to two nodes; either node can control the disk modules depending on the position as indicated by the switch cards. Each switch card connects to two ServerNet/DAs and to a 45xx disk module.
Switch Modules Switch Card Toggle Switches Switch Card Toggle Switches When the key switch on the SCC is turned to the LOCAL position, you change the paths that fiber-optic signals take through the switch card by moving the toggle switch on the faceplate of the switch card. The toggle switch does not indicate whether the switch is straight or crossed, to determine that, refer to Switch Card LEDs on page 4-9. Straight Position Crossed position J1 J1 J2 J2 J3 J3 J4 J4 VST201.vsd VST 202.
Switch Modules Switch Card LEDs Switch Card LEDs The state of the switch is indicated by the switch card LEDs. : Location Color When Lit, Indicates Action Left Green The switch is in the straight position. J1 connects to J2, and J3 connects to J4. No action is required. Right Green The switch is in the crossed position. J1 connects to J4, and J3 connects to J2. No action is required.
Switch Modules Switch Card LEDs ServerNet Nomadic Disk User’s Guide—425485-001 4- 10
5 Switchovers Preparing for a Switchover Switchover Examples Assumptions 5-2 5-3 5-3 Moving the Fiber Optic Switches to the Opposite Position 5-4 Planned Switchovers 5-5 On Primary node \PRI 5-5 On Backup Node \BCK 5-6 Unplanned Switchovers 5-7 5-7 From the Primary Node \PRI From the Backup Node \BCK Switchback 5-7 5-8 On the Backup Node \BCK 5-8 On the Primary Node \PRI 5-9 ServerNet Nomadic Disk User’s Guide— 425485-001 5 -1
Switchovers Preparing for a Switchover After a switchover, operations continue on the backup node following a planned or unplanned outage of the primary node: • • A switchover is planned when the primary node is halted to perform significant maintenance tasks or software upgrades. A switchover is unplanned when a primary node fails. Preparing for a Switchover • Review Logically Switching a Database on page 1-5 and Section 7, Nomadic Disk Manager Interface.
Switchovers Switchover Examples Switchover Examples The examples in this section show the sequence of events and commands used to perform a switchover. For more information about the commands used in these examples: • • For detailed information about the Nomadic Disk Manager commands, see Section 7, Nomadic Disk Manager Interface. For information about the switch command interface (SWCI), see Section 6, Switch Command Interface (SWCI).
Switchovers Moving the Fiber Optic Switches to the Opposite Position Example 5-2. NDCONFIG on \BCK SET SET SET SET SET SET SET SET SET SET SET SET PATH P $ MOD1.#A 1 CROSSED PATH B $ MOD1.#A 2 CROSSED PATH M $TRM1.#A 1 STRAIGHT PATH MB $ TRM1.
Switchovers Planned Switchovers Planned Switchovers You perform a planned switchover to continue operations on the backup node when the primary node must be halted to perform significant maintenance tasks or software upgrades, minimizing down time for the users of the primary node. The following is an example of a planned switchover from primary node to backup node. On Primary node \PRI 1. Stop all running applications. 2.
Switchovers On Backup Node \BCK On Backup Node \BCK 1. If you are not using the Nomadic Disk Manager: a. Change the fiber-optic switches at the backup node to the opposite position as described in Moving the Fiber Optic Switches to the Opposite Position on page 5-4. b. Use the SWCI STATUS command to verify that switch modules are in the correct position. SWCI $SWITCH1.#PRI> STATUS c. Use the SCF START DISK command to start the nomadic volumes that were switched from the primary node.
Switchovers Unplanned Switchovers Unplanned Switchovers When a primary node fails, you perform an unplanned switchover to continue operations on the backup node. You must planned for the possibility of an unplanned switchover before a primary node failure occurs. For an example of how the switch modules support the disk drives after switchover, see Remote Mirroring After a Switchover on page 1-4. Example of an Unplanned Switchover From Primary Node to Backup Node The primary node \PRI loses all power.
Switchovers Switchback Switchback On the Backup Node \BCK 1. Stop all applications that access data on Nomadic volumes. 2. Change the switches. • If you are not using the Nomadic Disk Manager a. Use SCF to stop the Nomadic volumes: -> STOP DISK $nomadicvol b. Change the fiber-optic switches at \BCK to the opposite position as described in Moving the Fiber Optic Switches to the Opposite Position on page 5-4. • If you are using the Nomadic Disk Manager. a.
Switchovers On the Primary Node \PRI On the Primary Node \PRI 1. Change the switches. • If not using the Nomadic Disk Manager: a. Use the SWCI STATUS command to verify that switch modules are in the correct position. SWCI $SWITCH1.#PRI> STATUS b. Use the SCF START DISK command to start the nomadic volumes that were switched from the primary node. -> START DISK $nomadicvol, $nomadicvol • If using the Nomadic Disk Manager: a.
Switchovers On the Primary Node \PRI ServerNet Nomadic Disk User’s Guide— 425485-001 5- 10
6 Switch Command Interface (SWCI) Testing the ATP6100 Configuration for SWCI 6-2 Configuring the ATP6100 Line for SWCI Communications 6-5 Switch Module Device Name Starting SWCI Stopping SWCI 6-3 6-6 6-7 SWCI Commands 6-8 ALARM Command 6-9 EXIT Command 6-10 HELP Command 6-10 LOCK Command 6-11 LOG Command 6-12 OBEY Command 6-13 SELFTEST Command STATUS Commands 6-14 6-15 SWITCH Command 6-23 UNLOCK Command 6-25 SWCI Messages 6-26 Application Initialization Error Messages 6-26 Command Inpu
Switch Command Interface (SWCI) Testing the ATP6100 Configuration for SWCI Testing the ATP6100 Configuration for SWCI Use this procedure to test whether the ATP6100 line is configured correctly and the SWAN concentrators are communicating with each switch module. 1. On one switch module, set the key switch on the switch controller card (SCC) to the REMOTE (R) position. Refer to SCC Key Switch on page 4-4 for more information. 2. At a TACL prompt, start SWCI. For example: > SWCI $SWITCH1.#PRI 3.
Switch Command Interface (SWCI) Configuring the ATP6100 Line for SWCI Communications Configuring the ATP6100 Line for SWCI Communications The SWAN concentrator uses an asynchronous ATP6100 line to provide communication between SWCI running on the primary and backup nodes and a switch module . If the ATP6100 line is not already configured, perform the following steps at both the primary node and backup node. 1.
Switch Command Interface (SWCI) Configuring the ATP6100 Line for SWCI Communications For SWCI to work correctly, when you add the profile, you must change the following modifiers to the required values. .
Switch Command Interface (SWCI) Switch Module Device Name 4. Start the device Starting the DEVICE object starts both an ATP6100 line-handler process (WAN I/O process) and an ATP6100 line. The cable between the switch module and the SWAN concentrator must be connected before you can start the device. In this example the WAN IOP is named $ZZWAN.#SWITCH1, and the ATP6100 line is named $SWITCH1. This example starts the line-handler process and line at the primary node. ->START DEVICE $ZZWAN.
Switch Command Interface (SWCI) Starting SWCI Starting SWCI 1. Before starting SWCI, review these considerations: • • You must be a super-group user (255, n) to run SWCI. When you start SWCI, SWCI checks for the device specified in the RUN command. If that device exists, SWCI checks the device type and subtype, which must be type 6 (terminal type), subtype 0 (asynchronous serial device). • • If the device type and subtype are incorrect, SWCI returns an error message.
Switch Command Interface (SWCI) • Stopping SWCI To start SWCI from a NonStop Himalaya S-series server other than the one connected to the switch module, at a TACL prompt, type: 1>RUN $SYSTEM.SYSTEM.SWCI \node.$SwitchModuleDevice where: \node is the name of the remote node that switch module is connected to. $switchmoduledevice is the device name of the switch module. Stopping SWCI To stop SWCI , use the SWCI EXIT command. For example: SWCI $NDSWA.
Switch Command Interface (SWCI) SWCI Commands SWCI Commands SWCI executes each command as it is entered and displays results in the TACL window from which SWCI was started (or to an alternate terminal or file if specified in the TACL RUN command). SWCI continues to execute commands until it encounters either an EXIT command or (if input is from a file) an end-of-file condition .
Switch Command Interface (SWCI) ALARM Command ALARM Command If an optional external alarm is connected to the external alarm port of the SCC and the alarm relays are energized, the alarm command activates the alarm for three seconds. You can activate the alarm to help identify the SCC to which the remote control software is connected to, which can be useful when multiple switch modules are installed.
Switch Command Interface (SWCI) EXIT Command EXIT Command Use the EXIT command to stop SWCI. . EXIT Example SWCI $NDSWA.#TERM> EXIT HELP Command Online help is available for all SWCI commands through the HELP command. HELP [ ALL | command ] ALL returns a list of all SWCI commands. command returns information about the specified command. Example The following command gives specific help on the STATUS command, including a description of the command, command usage, and command syntax. SWCI $NDSWA.
Switch Command Interface (SWCI) LOCK Command LOCK Command The LOCK command changes the specified switch card to the locked state. LOCK SC n SC n specifies the slot number of the switch card to be locked. n is an integer from 1 through 8 Considerations • • • • • The key switch on the SCC must be in the REMOTE position for this command to succeed. If the command is successful, SWCI returns a message stating that the specified switch card is now locked.
Switch Command Interface (SWCI) LOG Command LOG Command The LOG command starts and stops logging of any input and output that is sent or received by the user terminal. LOG { TO [[$volume.]subvolume.] logfile | STOP } TO [[$volume.]subvolume.]logfile specifies the file where SWCI is to write any input or output that is sent or received by the user terminal. • • • If the specified file already exists, SWCI appends information to the end of the file. If the specified file does not exist, SWCI creates it.
Switch Command Interface (SWCI) OBEY Command OBEY Command The OBEY command instructs SWCI to execute commands contained in a command file that you specify. A command file is an EDIT file (file code 101) that contains commands (in this case, SWCI commands). When you use the OBEY command, SWCI echoes each command to the terminal as it is executed, along with any output generated by the command. After sequentially executing all commands in the file, SWCI prompts for the next command. OBEY [[$volume.
Switch Command Interface (SWCI) SELFTEST Command SELFTEST Command The SELFTEST command causes the SCC to perform its power-on self-test (POST) diagnostics. SELFTEST Considerations • • • • When the SELFTEST command is issued, all switch cards go to the locked state. The key switch on the SCC must be in the REMOTE position, or the POST fails. You cannot use SELFTEST with the key switch in the LOCAL position. If the POST is successful, SWCI returns the message “SCC self-diagnostics passed.
Switch Command Interface (SWCI) STATUS Commands STATUS Commands The STATUS command returns current operating and configuration information about switch module, switch module environment, switch card, and SCC.
Switch Command Interface (SWCI) STATUS Commands Example: Information Returned by the STATUS Command Switch Controller Card Information: Part Number ------------114120 A00-00 Track ID -------AAAAAA Date of Manufacture ------------------04/13/1995 12:00:00 Firmware -------000001 PON -------PONOK Switch Card Information: SC --1 2 3 4 5 6 7 8 Part Number ------------114117 A00-00 114117 A00-00 EMPTY EMPTY EMPTY EMPTY 114117 A00-00 114117 A00-00 SCM Environment: Track ID -------AAAAAB AAAAAC Date of M
Switch Command Interface (SWCI) The switch control module (SCM) environmental information STATUS Commands Position Current switch card position (STRAIGHT or CROSSED). See SWITCH Command on page 6-23 for definitions of straight and crossed. Lock The switch card lock/unlock status (LOCKED or UNLOCKED). See SWITCH Command on page 6-23 for definitions of locked and unlocked.
Switch Command Interface (SWCI) STATUS Commands Displaying Switch Module Environmental Information The STATUS ENV command displays environmental information about the switch module. This includes information about the power supply voltage, temperature readings inside the module, and the position of the key switch on the SCC. STATUS ENV [ , env-attr ] env-attr specifies one of these environmental attributes: POWER Displays only switch module power supply voltage.
Switch Command Interface (SWCI) • STATUS Commands To request only power supply voltage information about the switch module: SWCI $NDSWA.#TERM>STATUS ENV, POWER SCM Environment: • Power -----5.70 V To request only temperature information about the switch module: SWCI $NDSWA.#TERM>STATUS ENV, TEMP SCM Environment: • Temp 1 -----35.7 C Temp 2 ------35.9 C To request only the position of the key switch on the SCC in the switch module: SWCI $NDSWA.
Switch Command Interface (SWCI) STATUS Commands Examples • To retrieve status information about all switch cards in the switch module: SWCI $NDSWA.
Switch Command Interface (SWCI) STATUS Commands Displaying SCC Status Information The STATUS SCC command displays status information about the SCC. The command can return complete information or information about a specified attribute. Complete information about the SCC includes: • • • • • Part number Track ID Date of manufacture Firmware revision Status of the most recent power-on self-test STATUS SCC [ , scc-attr ] scc-attr specifies one of these SCC attributes: PARTNO Displays the part number.
Switch Command Interface (SWCI) STATUS Commands Examples • To retrieve all status information about the SCC: SWCI $NDSWA.#TERM>STATUS SCC Switch Controller Card Information: Part Number ------------114117 A00-00 • Track ID -------AAAAAA Date of Manufacture ------------------04/13/95 12:00:00 Firmware -------000001 PON -------PONOK To request the status of the most recent power-on self-test for the SCC: SWCI $NDSWA.
Switch Command Interface (SWCI) SWITCH Command SWITCH Command The SWITCH command changes the switch position of the specified switch card. A switch card can be in either the STRAIGHT position or the CROSSED position. SWITCH SC n [ ,STRAIGHT | ,CROSSED ] SC n specifies the switch card by its slot number, which is an integer from 1 through 8. The key switch on the SCC must be in the REMOTE position for this command to succeed.
Switch Command Interface (SWCI) • SWITCH Command To make sure that the switch card in slot 4 is in the straight position: SWCI $NDSWA.#TERM>UNLOCK SC 4 SWCI $NDSWA.#TERM>SWITCH SC 4, STRAIGHT SWCI $NDSWA.#TERM>LOCK SC 4 SC 4 is unlocked SC 4 is set to straight SC 4 is locked The switch card in slot 4 could have been either crossed or straight before this command was issued. Specifying STRAIGHT ensures that the switch is set to the straight position after this command. Figure 6-1.
Switch Command Interface (SWCI) UNLOCK Command UNLOCK Command The UNLOCK command instructs the specified switch card to change to the unlocked state. UNLOCK SC n n Is an integer in the range of 1 through 8 that identifies the slot number of the switch card to be unlocked. Considerations • • • The key switch on the SCC must be in the REMOTE position for this command to succeed. You must specify a valid slot number.
Switch Command Interface (SWCI) SWCI Messages SWCI Messages This subsection documents all error messages output by SWCI: Error Message Type Page Application initialization error messages 6-26 Command input/parsing error messages 6-29 Command execution error messages 6-33 Switch protocol error messages 6-38 Run-time fatal error messages 6-49 When errors occur, SWCI reports the incident to the user and executes the next user command.
Switch Command Interface (SWCI) Application Initialization Error Messages Guardian error err-num on access to switch comm port. Cause. An attempt to obtain information for the specified switch module device failed. err-num is the Guardian file-system error number that occurred. Effect. SWCI stops. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for recovery from the file-system error. Then, restart SWCI. Guardian error err-num on open of switch comm port. Cause.
Switch Command Interface (SWCI) Application Initialization Error Messages Startup message not found Cause. SWCI could not successfully access its startup message to obtain file input/output parameters. Effect. SWCI stops. Recovery. Restart SWCI. Switch comm port switch-comm-port-name: invalid device subtype. Cause. The switch module device specified for SWCI is a terminal device (device type 6), but not an asynchronous serial port (subtype 0). Effect. SWCI stops. Recovery.
Switch Command Interface (SWCI) Command Input/Parsing Error Messages Command Input/Parsing Error Messages These messages indicate incorrectly specified SWCI commands or errors obtaining new SWCI commands. If a command parsing error is detected, the corresponding error message is displayed with a caret (^) character indicating the point in the SWCI command at which the error was detected.
Switch Command Interface (SWCI) Command Input/Parsing Error Messages ***COMMAND ERROR*** PARTNO, TRACKID, DATE, FWREV, LOCK, or POSITION expected Cause. A STATUS command contained an invalid scc-attr value. Effect. The command is not executed. SWCI waits for the next command. Recovery. Retry the STATUS command with the correct syntax. ***COMMAND ERROR*** PARTNO, TRACKID, DATE, FWREV, or PONTEST expected Cause. A STATUS SCC command contained an invalid scc-attr value. Effect. The command is not executed.
Switch Command Interface (SWCI) Command Input/Parsing Error Messages ***COMMAND ERROR*** Slot number (1-8) expected Cause. A LOCK, UNLOCK, or SWITCH command did not include a valid slot number at the appropriate point in the command. Effect. The command is not executed. SWCI waits for the next command. Recovery. Retry the command with the correct syntax. ***COMMAND ERROR*** Slot number (1-8) or * expected Cause. A STATUS SC command contained an invalid slot-number value. Effect.
Switch Command Interface (SWCI) Command Input/Parsing Error Messages ***COMMAND ERROR*** Unrecognized command Cause. The specified input command is not in the SWCI command set. Effect. The command is not executed. SWCI waits for the next command. Recovery. Enter another command or retry the command with correct syntax. ***ERROR*** Close of obey file unsuccessful. Cause.
Switch Command Interface (SWCI) Command Execution Error Messages Command Execution Error Messages These error messages indicate errors during the execution of correctly specified SWCI commands: ***ERROR*** Command failed because SC slot-number is currently LOCKED. Cause. A SWITCH command failed because the switch card in slot slot-number is currently locked Effect. The command is not executed. SWCI waits for the next command. Recovery. Unlock the switch card, then retry the SWITCH command.
Switch Command Interface (SWCI) Command Execution Error Messages ***ERROR*** Guardian error err-num on access to obey file file-name. Cause. An an error occurred during an attempt to read the command file. err-num is the Guardian file-system error number that occurred. Effect. The command file is not executed. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for recovery from the file-system error. ***ERROR*** Guardian error err-num on read of switch comm port. Cause.
Switch Command Interface (SWCI) Command Execution Error Messages ***ERROR*** Log file file-name could not be opened. Cause. An error occurred during an attempt to open a LOG TO command log file file-name. A one-line textual description of the type of error encountered follows. Effect. The command is not executed. SWCI waits for the next command. Recovery. Retry the command with the correct syntax. ***ERROR*** Log file file-name is already active. Cause.
Switch Command Interface (SWCI) Command Execution Error Messages ***ERROR*** Obey file file-name is not an edit file. Cause. The command file file-name is not an EDIT (code 101) file. Effect. The command is not executed. SWCI waits for the next command. Recovery. Retry the command with an EDIT file. ***ERROR*** Obey file file-name was not opened successfully. Cause. An error occurred during an attempt to open the command file file-name.
Switch Command Interface (SWCI) Command Execution Error Messages ***ERROR*** SC slot-number did not LOCK successfully. Cause. A LOCK SC command failed because the switch card in slot slot-number did not correctly transition to a locked state. Effect. The command is not executed. SWCI waits for the next command. Recovery. Retry the command. ***ERROR*** SC slot-number did not UNLOCK successfully. Cause.
Switch Command Interface (SWCI) Switch Protocol Error Messages Switch Protocol Error Messages These error messages indicate errors in communication between SWCI and the attached switch module. A poor serial connection between the server and the switch module or an incompatibility between SWCI and the SCC firmware can be the source of these errors. ***PROTOCOL ERROR*** SCC response message: length too short. Cause.
Switch Command Interface (SWCI) Switch Protocol Error Messages ***PROTOCOL ERROR*** SCC response message: incorrect length. Cause. The message length field in a response message received from the SCC did not match the number of response message characters read from the SCC by SWCI. Effect. SWCI does not work properly. Recovery. Do the following: 1. Check the configuration of the switch module device and reconfigure if necessary. 2. Check the version of SWCI installed. 3.
Switch Command Interface (SWCI) Switch Protocol Error Messages Cause. The slot number field in a response message received from the SCC did not contain a valid slot number. Effect. SWCI does not work properly. Recovery. Do the following: 1. Check the configuration of the switch module device and reconfigure if necessary. 2. Check the version of SWCI installed. 3. Power the switch module device off then back on again. ***PROTOCOL ERROR*** SCC response message: invalid response type field. Cause.
Switch Command Interface (SWCI) Switch Protocol Error Messages ***PROTOCOL ERROR*** SCC response message: invalid result field. Cause. The result field in a response message received from the SCC did not contain a valid value. Effect. SWCI does not work properly. Recovery. Do the following: 1. Check the configuration of the switch module device and reconfigure if necessary. 2. Check the version of SWCI installed. 3. Power the switch module device off then back on again.
Switch Command Interface (SWCI) Switch Protocol Error Messages ***PROTOCOL ERROR*** Bad part number/revision field in SCC/SC FIR string. Cause. The part number/revision field of an SCC or the switch card FIR string read from the switch module is not present or is incorrectly specified. Effect. SWCI does not work properly. Recovery. Do the following: 1. Check the configuration of the switch module device and reconfigure if necessary. 2. Check the version of SWCI installed. 3.
Switch Command Interface (SWCI) Switch Protocol Error Messages ***PROTOCOL ERROR*** Bad tracking code field in SCC/SC FIR string. Cause. The FRU tracking code field of an SCC or the switch card FIR string read from the switch module is not present or is incorrectly specified. Effect. SWCI does not work properly. Recovery. Do the following: 1. Check the configuration of the switch module device and reconfigure if necessary. 2. Check the version of SWCI installed. 3.
Switch Command Interface (SWCI) Switch Protocol Error Messages ***PROTOCOL ERROR*** Bad manufacture date field in SCC/SC FIR string. Cause. The manufacture date/time field of an SCC or the switch card FIR string read from the switch module is not present or is incorrectly specified. Effect. SWCI does not work properly. Recovery. Do the following: 1. Check the configuration of the switch module device and reconfigure if necessary. 2. Check the version of SWCI installed. 3.
Switch Command Interface (SWCI) Switch Protocol Error Messages ***PROTOCOL ERROR*** Bad firmware revision field in SCC/SC FIR string.” Cause. The firmware revision field of an SCC FIR or the switch card FIR string read from the switch module is not present or is incorrectly specified. Effect. SWCI does not work properly. Recovery. Do the following: 1. Check the configuration of the switch module device and reconfigure if necessary. 2. Check the version of SWCI installed. 3.
Switch Command Interface (SWCI) Switch Protocol Error Messages ***PROTOCOL ERROR*** SCC response message: unexpected response type. Cause. The response message type received from the SCC for a switch command is not valid for the type of switch command sent. The type may be any of the following: ALARM FIR MUTEALARM REMOTE TEMP2 CROSSED LOCAL PONERROR STRAIGHT UNLOCK EMPTY LOCK PONOK TEMP1 VOLTS Effect. SWCI does not work properly. Recovery. Do the following: 1.
Switch Command Interface (SWCI) Switch Protocol Error Messages ***PROTOCOL ERROR*** SCC response message: invalid voltage data. Cause. The response message received from the SCC in response to a switch module voltage query does not contain valid voltage data. Effect. SWCI does not work properly. Recovery. Do the following: 1. Check the configuration of the switch module device and reconfigure if necessary. 2. Check the version of SWCI installed. 3. Power the switch module device off then back on again.
Switch Command Interface (SWCI) Switch Protocol Error Messages ***PROTOCOL ERROR*** SCC-detected checksum error on command message. Cause. The SCC detected a checksum error on a command message sent by SWCI. Effect. SWCI does not work properly. Recovery. Do the following: 1. Check the configuration of the switch module device and reconfigure if necessary. 2. Check the version of SWCI installed. 3. Power the switch module device off then back on again.
Switch Command Interface (SWCI) Fatal Application Error Messages ***PROTOCOL ERROR*** SCC-detected self-diagnostic error. Cause. The SCC unexpectedly executed self diagnostics during command execution, and that self-diagnostics failed. A reset or PON condition might have occurred on the switch module. Effect. SWCI does not work properly. Recovery. Do the following: 1. Check the configuration of the switch module device and reconfigure if necessary. 2. Check the version of SWCI installed. 3.
Switch Command Interface (SWCI) Environmental Alert Messages Environmental Alert Messages In addition to the normal output messages sent by SWCI , an environmental alert can appear after any switch module status or action command.
7 Nomadic Disk Manager Interface Starting the Nomadic Disk Manager 7-2 Nomadic Disk Manager Commands 7-3 Summary of Nomadic Disk Manager Commands 7-3 ASSUME Command 7-5 DOWN Command 7-6 EXIT Command 7-7 GIVE Command 7-8 HELP Command 7-10 HISTORY Command 7-11 LISTDEV Command 7-12 LISTOPENS Command 7-14 OUT Command RESET Command 7-15 SEGMENTS Command STATUS Command TAKE Command UP Command 7-16 7-17 SQL Command TMF Command 7-13 7-17 7-19 7-21 7-21 VOLUMES Command 7-22 ServerNet Nom
Nomadic Disk Manager Interface Starting the Nomadic Disk Manager Starting the Nomadic Disk Manager For information on installation and configuration, see Section 3, Installing and Configuring the Nomadic Disk Manager. The Nomadic Disk Manager is accessed by entering the NOMADIC command. NOMADIC [ / [ IN infile ] [ , OUT outfile ] / ] [ command-string ] IN infile specifies the infile or process name for the Nomadic Disk Manager.
Nomadic Disk Manager Interface • Nomadic Disk Manager Commands Once you start the Nomadic Disk Manager, only valid Nomadic Disk Manager commands are accepted until you exit the Manager, either inadvertently or by entering EXIT or pressing Ctl-Y. Nomadic Disk Manager Commands The ServerNet Nomadic Disk Manager has its own set of commands.
Nomadic Disk Manager Interface Summary of Nomadic Disk Manager Commands Command Description Page TAKE Changes the status of a segment to OWNED 7-19 TMF Do not use this command UP Performs an SCF START DISK command on a set of objects 7-21 VOLUMES Lists the volume names associated with a segment 7-22 ServerNet Nomadic Disk User’s Guide—425485-001 7 -4 NA
Nomadic Disk Manager Interface ASSUME Command ASSUME Command Use the ASSUME command to set a default segment name. Several Nomadic Disk Manager commands have an optional SEGMENT parameter. If you omit the SEGMENT parameter in those commands, the default segment, set by the ASSUME command, is used. ASSUME [ SEGMENT segname ] segname specifies the name of the intended current segment. segname is any valid segment name. If SEGMENT segname is not specified, the current default segment name is displayed.
Nomadic Disk Manager Interface DOWN Command DOWN Command The DOWN command performs an SCF STOP DISK command on a set of objects. DOWN { VOLUMES | PATHS { -P|-B|-M|-MB|PRIMARY|MIRROR } } [ , SEGMENT { segname | * } ] VOLUMES specifies to stop all volumes in either the specified segment, or all segments. PATHS specifies that the command affects only the selected path for each volume in either the specified segments, or all segments.
Nomadic Disk Manager Interface EXIT Command EXIT Command Use the EXIT command to exit the Nomadic Disk Manager and return to the TACL process.
Nomadic Disk Manager Interface GIVE Command GIVE Command Use the GIVE command to change the status of a segment to NOT OWNED. The prior status of the segment can be anything, that is, it need not be OWNED. GIVE [ SEGMENT segname | DATA ] [ , LOCALTMF ] [ , START ] [ , ONLY ] SEGMENT segname specifies which segments to give away. If a data segment is specified, all data segments are given away. If segname is not specified, the GIVE command operates on the current segment.
Nomadic Disk Manager Interface • • • GIVE Command In a ServerNet Nomadic Disk environment, all data segments must be owned by the same node. Therefore, whenever a data segment is given away, all data segments are given away unless explicit instructions indicate otherwise. The GIVE command implicitly performs a DOWN VOLUMES command. Before a segment can be given away, all volumes on that segment must be stopped. Then, all paths for that segment are switched to the NOT OWNED state.
Nomadic Disk Manager Interface HELP Command HELP Command Help information for any Nomadic Disk Manager command is available through the HELP command. HELP [command-name ] ALL Returns a list of all Nomadic Disk Manager commands. command-name is any valid Nomadic Disk Manager command.
Nomadic Disk Manager Interface HISTORY Command HISTORY Command The Nomadic Disk Manager HISTORY command is identical to the TACL HISTORY command. In fact, the TACL HISTORY command is invoked. See the TACL Reference Manual for a description of the TACL HISTORY command. HISTORY [ number ] number is an integer specifying a previous command line.
Nomadic Disk Manager Interface LISTDEV Command LISTDEV Command Use the LISTDEV command to perform an SCF STATUS DISK command on a set of objects. LISTDEV [ , SEGMENT { segname | * } ] SEGMENT { segname | * } specifies which segments are affected by the LISTDEV command. You can specify the volumes in only a particular segment (segname) or all volumes in all segments (*). If you do not include the SEGMENT parameter, the volumes in the current segment are affected.
Nomadic Disk Manager Interface LISTOPENS Command LISTOPENS Command Use the LISTOPENS command to perform a FUP LISTOPENS command on each volume in one or more segments. LISTOPENS [ , SEGMENT { segname | * } ] SEGMENT { segname | * } indicates which segments are affected by the LISTOPENS command. You can specify the volumes in a specific segment (segname) or all volumes in all segments (*). If you do not include the SEGMENT parameter, the volumes in the current segment are affected.
Nomadic Disk Manager Interface OUT Command OUT Command Use the OUT command to temporarily change the outfile of the Nomadic Disk Manager. OUT [ outfile ] outfile is the name of any valid output file. If you enter an OUT command without specifying outfile, the output file reverts to the Manager’s original output file. If the output file is changed, all output, including error messages, is written only to the specified outfile. Examples ND> OUT $S.#NDMGR ND> OUT $DATA.EDIT.
Nomadic Disk Manager Interface RESET Command RESET Command Use the RESET command to perform an SCF RESET DISK command on a set of objects. The RESET command places objects that are in a HARDDOWN state into a DOWN state. RESET { VOLUMES|PATHS { -P|-B|-M|-MB|PRIMARY|MIRROR|ALL } } [ , SEGMENT { segname | * } ] VOLUMES specifies to reset all volumes in the specified segments.
Nomadic Disk Manager Interface SEGMENTS Command SEGMENTS Command The SEGMENTS command lists all the defined segment names, and the segment type (data) of each segment.
Nomadic Disk Manager Interface SQL Command SQL Command Do not use the SQL command. STATUS Command Use the STATUS command to list the current ownership status of a segment or segments. The status of a segment is an indication of its current ownership, rather than an indication of the accessibility of its member volumes. STATUS [ , SEGMENT { segname | * } ] SEGMENT { segname | * } indicates which segments are affected by the STATUS command.
Nomadic Disk Manager Interface Examples >ND STATUS SEGMENT ONE >ND STATUS SEGMENT * >ND STATUS ServerNet Nomadic Disk User’s Guide—425485-001 7- 18 STATUS Command
Nomadic Disk Manager Interface TAKE Command TAKE Command Use the TAKE command to change the status of a segment to OWNED. The prior status of the segment can be anything; that is, it need not be NOT OWNED. TAKE [ SEGMENT segname | DATA ] [ [ [ [ [ [ [ , , , , , , , ADDSQLVOL ADDVOLS LOCALTMF NOFIXUP NOSTART ONLY UPPATH { -P|-B|-M|-MB|PRIMARY|MIRROR } ] ] ] ]... ] ] ] SEGMENT segname species which segments are to be taken.
Nomadic Disk Manager Interface TAKE Command UPPATH { -P | -B | -M | -MB | PRIMARY | MIRROR } specifies that an UP PATHS command be issued instead of the UP VOLUMES command. Refer to UP Command on page 7-21. Immediately after ownership is taken, all the Nomadic volumes are in a DOWN state. The TAKE command normally automatically issues the UP VOLUMES command. UPPATH is used only in special circumstances or emergencies.
Nomadic Disk Manager Interface TMF Command TMF Command Do not use the TMF command. UP Command Use the UP command to perform an SCF START DISK command on a set of objects. UP { VOLUMES | PATHS { -P|-B|-M|-MB|PRIMARY|MIRROR } } [ , SEGMENT { segname | * } ] VOLUMES specifies to start all volumes in either the specified segment, or all segments. PATHS specifies that the command affects only the selected path for each volume in either the specified segments, or all segments.
Nomadic Disk Manager Interface VOLUMES Command VOLUMES Command Use the VOLUMES command to list the volume names associated with a segment. VOLUMES [ , SEGMENT { segname | * } ] SEGMENT { segname | * } indicates which segments are affected by the LISTOPENS command. You can specify the volumes in a specific segment (segname) or all volumes in all segments (*). If you do not include the SEGMENT parameter, the volumes in the current segment are affected.
A Part Numbers For a complete list of all part numbers, refer to the ServerNet Nomadic Disk Installation and Service Guide. Table A-1.
Part Numbers ServerNet Nomadic Disk User’s Guide —425485-001 A- 2
B Operational Considerations for Remote Mirroring Powering On and Off a Remote I/O Enclosure B-2 Powering On a System With a Remote I/O Enclosure B-2 Powering Off a System With a Remote I/O Enclosure B-3 ServerNet Nomadic Disk User’s Guide —425485-001 B- 1
Operational Considerations for Remote Mirroring Powering On and Off a Remote I/O Enclosure Powering On and Off a Remote I/O Enclosure Managing a remote I/O enclosure and remote external disk drives is similar to managing any I/O enclosure or disk drives, but power-on cables cannot be used. This affects the power on and power off procedures. Powering On a System With a Remote I/O Enclosure 1. At the remote site: a. Locate the power-on push button above the handle on the remote I/O enclosure. b.
Operational Considerations for Remote Mirroring Powering Off a System With a Remote I/O Enclosure Powering Off a System With a Remote I/O Enclosure 1. Stop and power off the system as described in the Himalaya S-Series Operations Guide. 2. Power off the remote I/O enclosure. 3. Power off the remote external disk drives.
Operational Considerations for Remote Mirroring Powering Off a System With a Remote I/O Enclosure ServerNet Nomadic Disk User’s Guide —425485-001 B- 4
Index A Alarm conditions 4-6 ALARM, SWCI command 6-9 ASSUME command 7-5 Asynchronous line parameters 6-3, 6-4 ATP6100 parameters 6-3, 6-4 C Combining remote mirroring and switching 1-2 Commands SWCI 6-8 Configuration after switchover 1-4 asynchronous line 6-3, 6-4 before switchover 1-3 file examples 3-6 SWAN concentrator 6-3, 6-4 Configuration statements ADD DEFINE 3-10 ADD SEGMENT 3-11 PROCESS 3-12 SET PATH 3-14 SET VOL 3-15 summary 3-9 D DOWN command 7-6 E ENSCRIBE files, and switching databases 1-5 Er
Index F PONTEST expected 6-30 POSITION expected 6-30 POWER expected 6-30 SC slot is EMPTY 6-33 SC slot is LOCKED 6-33 SCC detected checksum error 6-48 protocol error 6-48 protocol revision error 6-48 self-diagnostic error 6-49 SCC response message frame error 6-38 incorrect length 6-39 invalid checksum 6-41 invalid comm port ID 6-39 invalid environment alert field 6-40 invalid length field 6-38 invalid response type field 6-40 invalid response type/result 6-47 invalid result field 6-41 invalid slot number
Index L L O LISTDEV command 7-12 LISTOPENS command 7-13 LOCK SC command 6-11 LOG command, SWCI 6-12 Logical switching 1-2 OBEY command, SWCI 6-13 OUT command 7-14 M Mirroring remote 1-2 remote, benefits 1-2 N Nomadic Disk configurations after switchover 1-4 before switchover 1-3 Nomadic Disk Manager files 3-2 Nomadic Disk Manager commands ASSUME 7-5 DOWN 7-6 EXIT 7-7 GIVE 7-8 HELP 7-10 HISTORY 7-11 LISTDEV 7-12 LISTOPENS 7-13 OUT 7-14 RESET 7-15 SEGMENTS 7-16 SQL 7-17 STATUS 7-17 TAKE 7-19 TMF 7-21 U
Index T configuring 6-3, 6-4 SWCI command prompt 6-7 error messages 6-26 starting and stopping a SWCI process 6-6 syntax conventions xi SWCI commands ALARM 6-9 HELP 6-9 LOCK SC 6-11 LOG 6-12 OBEY 6-13 power-on self-test 6-14 STATUS 6-15 STATUS ENV 6-18 STATUS SC 6-19 STATUS SCC 6-21 SWITCH SC 6-23 UNLOCK SC 6-25 Switch card description 4-7/4-9 slot assignments 4-7 Switch controller card description 4-3 Switch controller software 4-4 Switch module alarm port 4-6 description 4-7/?? LEDs 4-5 sensors 4-4 swit
