SCF Reference Manual for the Storage Subsystem Abstract This manual describes how to use the Subsystem Control Facility (SCF) to configure, control, and inquire about storage subsystem objects on HP Integrity NonStop™ NS-series servers and HP NonStop S-series servers. This manual is for anyone who configures new systems, changes or adds to existing system configurations, plans changes to systems, monitors the status of the storage subsystem, or operates a network of distributed systems.
Document History Part Number Product Version Published 529937-002 Storage Config MGR H01 and G06 July 2005 529937-003 Storage Config MGR H01 and G06 August 2005 529937-004 Storage Config MGR H01 and G06 September 2005 529937-005 Storage Config MGR H01 and G06 November 2005 529937-008 Storage Config MGR H01 and G06 June 2007
SCF Reference Manual for the Storage Subsystem Glossary Index What’s New in This Manual xiii Manual Information xiii New and Changed Information Tables xiv About This Manual xv Who Should Use This Manual xv Where to Get More Information xv Notation Conventions xv 1.
2. Storage Subsystem Objects (continued) Contents 2. Storage Subsystem Objects (continued) Object Types for the Storage Subsystem The ADAPTER Object 2-3 The DISK Object 2-4 The MON Object 2-7 The POOL Object 2-8 The PROFILE Object 2-8 The SAC Object 2-10 The SCSI Object 2-10 The SUBSYS Object 2-11 The TAPE Object 2-12 2-3 3.
. Displaying Information About Magnetic Disks (continued) Contents 5.
. Configuring Magnetic Disks (continued) Contents 6.
. Managing Magnetic Disks (continued) Contents 7.
. Disk Load Balancing (continued) Contents 8. Disk Load Balancing (continued) Topology Branch Example for G06.10 and Earlier RVUs 8-6 A Closer Look at Eight Disks 8-8 PRIMARY Command Function in G06.00 Through G06.10 8-8 PRIMARY Command Function in G05.00 and Earlier 8-11 Establishing a Disk Load Balance in RVUs Prior to G06.11 8-14 Maintaining a Disk Load Balance 8-18 9.
10. Configuring and Managing Virtual Disks (continued) Contents 10. Configuring and Managing Virtual Disks (continued) Managing a Virtual Disk 10-12 Starting a Virtual Disk 10-12 Resetting a Virtual Disk 10-13 Stopping a Virtual Disk 10-13 Swapping Processors for a Virtual Disk 10-13 11.
13. Configuring and Managing Tape Drives Contents 13.
14. Storage Subsystem Commands (continued) Contents 14.
Contents 14. Storage Subsystem Commands (continued) 14.
14. Storage Subsystem Commands (continued) Contents 14. Storage Subsystem Commands (continued) STOPOPENS Command 14-135 STOPOPENS DISK Command 14-135 SWITCH Command 14-137 SWITCH ADAPTER Command 14-137 SWITCH DISK Command 14-138 SWITCH SCSI Command 14-139 VERSION Command 14-140 VERSION SUBSYS Command 14-140 A. SCF Command Summary B. Storage Subsystem Error Messages If You Have to Contact Your Service Provider Handling File-System Error Messages B-2 Storage Subsystem Error Messages B-2 B-1 C.
Tables (continued) Contents Tables (continued) Table 12-1. Table 13-1. Table 14-1. Table 14-2.
What’s New in This Manual Manual Information SCF Reference Manual for the Storage Subsystem Abstract This manual describes how to use the Subsystem Control Facility (SCF) to configure, control, and inquire about storage subsystem objects on HP Integrity NonStop™ NS-series servers and HP NonStop S-series servers.
New and Changed Information What’s New in This Manual New and Changed Information New and Changed Information in this version The following information has been changed in this version of this manual: • Update for information for the REVIVERATE attribute in Considerations for Changing the Speed of a Revive Operation on page 7-7.
About This Manual This manual describes how to use the Subsystem Control Facility (SCF) to configure, control, and inquire about storage devices on HP Integrity NonStop NS-series and HP NonStop S-series servers.
General Syntax Notation About This Manual lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none.
Notation for Messages About This Manual Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must enter as shown. For example: "[" repetition-constant-list "]" Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted.
Change Bar Notation About This Manual [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
1 Introduction to the Storage Subsystem The storage subsystem allows you to use SCF to configure and manage storage devices online.
Introduction to the Storage Subsystem Manager Processes Manager Processes Storage Subsystem Manager ($ZZSTO) The $ZZSTO storage subsystem manager process is a generic process that uses SCF to perform persistent configuration and management. That is, when you use SCF to change the system configuration database, the changes survive a system load. After you configure storage subsystem objects online, $ZZSTO maintains this configuration information in the system configuration database ($SYSTEM.ZSYSCONF.
Configuration Overview Introduction to the Storage Subsystem • Other SMF utilities SMF uses these object types in the storage subsystem: Object Type Description Section DISK Virtual disk process Section 10, Configuring and Managing Virtual Disks MON SMF monitor process $ZSMS Section 4, Configuring and Managing the SMF Master Process POOL Storage pool process created from multiple magnetic disks Section 9, Configuring and Managing Storage Pools for Magnetic Disks Configuration Overview To Mak
Introduction to the Storage Subsystem Using OBEYFORM to Create an SCF Command File Comparing OBEYFORM to LIKE The LIKE attribute of the ADD command performs a function similar to the OBEYFORM attribute of the INFO command: • • Use the LIKE attribute to quickly add one or more similar objects to the current configuration file. Use the OBEYFORM attribute to see and change the attributes of new objects before adding them to the configuration file.
Displaying Information About the Storage Subsystem Introduction to the Storage Subsystem Displaying Information About the Storage Subsystem To display information about storage subsystem devices and processes, see: • • The SCF INFO Command on page 14-80 LISTDEV Information for the Storage Subsystem on page 1-5 LISTDEV Information for the Storage Subsystem You can use the SCF LISTDEV command to display configured information about processes that have a device type and that are known to SCF.
Fault Tolerance Introduction to the Storage Subsystem Fault Tolerance An important concept, and a possible source of confusion for users, is the three ways that the word primary can be used when configuring and managing devices. Primary Processor An IOP runs in two processors: primary and backup. The PRIMARYCPU and BACKUPCPU attributes of the ADD command are set when the device is configured. To change which processor runs the primary process, specify that processor number in a PRIMARY command.
2 Storage Subsystem Objects This section describes how storage subsystem components are organized for management through the SCF interface. Topic Page Object Names 2-1 Object Types for the Storage Subsystem 2-3 Object States and Substates 2-2 Object Names Object names are the device or process names you use to specify a particular object in an SCF command. Each object type has its own object-name format. Object Type Object-Name Format Example Object Name ADAPTER $ZZSTO.#type.GRP-g.MOD-m.
Object States and Substates Storage Subsystem Objects • • A single wild-card character Text with one or more wild-card characters The storage subsystem supports these wild-card characters: * Represents a character string of undefined length. For example, to display the object names of all disks managed by the storage subsystem: -> NAMES DISK $* ? Represents a single unknown character in a specific position.
Object Types for the Storage Subsystem Storage Subsystem Objects Object Types for the Storage Subsystem Object Type Definition Page The ADAPTER Object A ServerNet adapter, which controls communication between the system and attached devices 2-3 The DISK Object A disk volume, either magnetic or virtual 2-4 The MON Object The Storage Management Foundation (SMF) master process 2-7 The POOL Object A storage pool 2-8 The PROFILE Object A method used to preconfigure disks 2-8 The SAC Object A
Storage Subsystem Objects The DISK Object GRP-g.MOD-m.SLOT-s is the physical location (group, module, and slot) of the adapter. g cannot have a leading zero. Wild-card characters are supported. Examples $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50 $ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-55 $ZZSTO.#SNDA.SAC-1.GRP-1.MOD-1.
The DISK Object Storage Subsystem Objects Examples $DATA00-P $DATA00-M $DATA00-B $DATA00-MB $DATA03 Object States and Substates of Magnetic Disks The object state and substate of a magnetic disk provide current status information about the disk or a path to that disk. Table 2-1. Object States and Substates of Magnetic Disks (page 1 of 2) State Substate Caused By Description SERVICING -- -- The disk volume or disk path is in transition and is unavailable due to a pending service operation.
The DISK Object Storage Subsystem Objects Table 2-1. Object States and Substates of Magnetic Disks (page 2 of 2) State Substate Caused By Description INACCESSIBLE Processor halts All paths to the processor are down. PREMATURETAKEOVER Improper sequence of commands The backup disk process was asked to take over for the primary disk process before the backup disk process had enough information.
The MON Object Storage Subsystem Objects Virtual Disk Object States Table 2-2. Virtual Disk Object States SCF State Description STARTED Accessible STARTING In transition to the STARTED state STOPPED Inaccessible The MON Object The MON object represents the $ZSMS Storage Management Foundation (SMF) master process, which maintains information about storage pools and virtual disks on the system.
The POOL Object Storage Subsystem Objects The POOL Object The POOL object represents a storage pool, which is a collection of magnetic disk volumes, all on the same system. A POOL object represents a resource of spaces where data files can be placed. Virtual disk processes can create files across volumes of a storage pool. A storage pool can have up to 144 magnetic disk volumes. The number of storage pools on a system is limited only by the current size of the destination control table (DCT).
The PROFILE Object Storage Subsystem Objects The PROFILE object has this format: $ZZSTO.INTERNAL-DISK[-groupnum ] $ZZSTO is the storage subsystem manager. INTERNAL-DISK is the type of disk for which a storage subsystem profile can be configured. -groupnum is the enclosure number to which a user-configured profile applies. groupnum cannot have a leading zero. The default standard profile has no group number and can be used to preconfigure any internal disk inserted in a slot in any enclosure.
Storage Subsystem Objects The SAC Object The SAC Object The SAC object represents a ServerNet addressable controller on a storage adapter. Commands issued for a SAC are often targeted at devices connected to the SAC.
Storage Subsystem Objects The SUBSYS Object For more information, see Section 12, Configuring and Managing Open SCSI Devices. The SCSI object has this format: $SCSI-device-name [-P | -B ] $SCSI-device-name is the name of the Open SCSI process controlling the Open SCSI device. The format is a dollar sign ($) followed by a maximum of seven alphanumeric characters, the first of which must be alphabetic. -P | -B indicates a path to the primary or backup Open SCSI device. Wild-card characters are supported.
Storage Subsystem Objects The TAPE Object Wild-card characters are supported. Example $ZZSTO The TAPE Object The TAPE object represents a specific tape drive, which is a storage device for archiving data. For more information, see Section 13, Configuring and Managing Tape Drives. The TAPE object has this format: $tape-name $tape-name is the name of the tape process controlling the tape device. Wild-card characters are supported.
3 Using the Storage Subsystem Manager The storage subsystem manager ($ZZSTO) is a generic process configured in the kernel subsystem. $ZZSTO monitors and controls all storage subsystem objects. $ZZSTO has the object type of SUBSYS.
Using the Storage Subsystem Manager Displaying Current Status Information BulkIO shows whether direct bulk I/O is on or off. LabelTape shows whether labeled-tape operation is on or off. UPS shows whether the uninterruptible power supply option is on or off. Note.
4 Configuring and Managing the SMF Master Process The SMF master process manages a centrally located database of information required at startup time for all other SMF processes, and it monitors and controls all storage pools and virtual disks in the system. The SMF master process, $ZSMS, has the object type of MON.
Displaying Information Configuring and Managing the SMF Master Process Displaying Information To display information about the SMF master process: • • Displaying Configuration Information on page 4-2 Displaying Current Status Information on page 4-3 Displaying Configuration Information The INFO MON Command (page 14-83) displays configured information about the SMF master process. Example of an INFO MON Report -> INFO MON $ZSMS STORAGE - Info MON \COMM.$ZSMS *BackupCPU CatalogLocation 4 $VIRCFG.
Displaying Current Status Information Configuring and Managing the SMF Master Process CatalogLocation the location of the catalog for the SMF master process. Highpin shows whether the IOP can run at a high PIN (ON) or a low PIN (OFF). The PIN is the process identification number. Mode shows whether the SMF master process generates additional EMS messages. PrimaryCPU the processor number of the primary SMF master process. Program the object file name of the SMF master process.
Configuring and Managing the SMF Master Process Configuring the SMF Master Process Mon I/O Process Information: Library File shows the library file name of the SMF master process. Program File shows the program file name of the SMF master process.
Configuring and Managing the SMF Master Process Altering the Values of the SMF Master Process Attributes 1. Capture the existing default profile: -> INFO / OUT LOG / $ZSMS, OBEYFORM == STORAGE - Detailed Info MON in obeyform: \COMM.$ZSMS ADD MON $ZSMS , & SENDTO STORAGE , & BACKUPCPU 4 , & CATALOGLOCATION $VIRCFG.ZSMSCAT0, & HIGHPIN OFF, & MODE QUIET, & PRIMARYCPU 5 , & PROGRAM $SYSTEM.SYSTEM.OMP 2.
Configuring and Managing the SMF Master Process Deleting the SMF Master Process 4. Restart the SMF master process: -> START $ZSMS Deleting the SMF Master Process The DELETE MON Command (page 14-77) removes the SMF master process from the system configuration database. Considerations for DELETE MON Caution. Using wild-card characters can affect the MON objects of other subsystems (QIO, for example).
Configuring and Managing the SMF Master Process Managing the SMF Master Process Managing the SMF Master Process Management tasks for the SMF master process include: • • • • Starting the SMF Master Process on page 4-7 Stopping the SMF Master Process on page 4-7 Resetting the SMF Master Process on page 4-8 Swapping Processors for the SMF Master Process on page 4-8 Starting the SMF Master Process The START MON Command (page 14-110) starts the SMF master process and puts it in the STARTED state.
Configuring and Managing the SMF Master Process Resetting the SMF Master Process Resetting the SMF Master Process The RESET MON Command (page 14-105) puts the SMF master process into the STOPPED state, substate DOWN, reading for restarting. 1. Check the current status of the SMF master process: -> STATUS $ZSMS 2. If it is not in the STOPPED state, substate DOWN: -> RESET $ZSMS 3. Start the SMF master process: -> START $ZSMS 4.
5 Displaying Information About Magnetic Disks This section describes displaying information about magnetic disks. For a description of the different types of magnetic disks that the storage subsystem supports, see Types of Magnetic Disks on page 6-2. Magnetic disks share the object type of DISK with virtual disks (discussed in Section 10, Configuring and Managing Virtual Disks).
Displaying Information About Magnetic Disks Displaying Information About Installed, Nonconfigured Internal Disks Displaying Information About Installed, Nonconfigured Internal Disks When physically installing an internal SCSI disk, you should note manually the location of any disk that is not configured. If you physically install a new disk in an empty slot that is not configured for a disk, OSM or TSM displays the disk.
Displaying Information About Magnetic Disks Displaying Information About Configured Disks Displaying Information About Configured Disks Example 1: An INFO Report for a Magnetic Disk Page 5-3 Example 2: A Detailed INFO Report for a Magnetic Disk Page 5-3 To display a report about all magnetic disks on the system: -> INFO DISK $* , SUB MAGNETIC Example 1: An INFO Report for a Magnetic Disk -> INFO $AUDIT STORAGE - Info Magnetic DISK configuration \COMM.
Displaying Common Disk Information Displaying Information About Magnetic Disks Topic INFO Command Attribute Page Displaying Disk Label Information LABEL Displaying Bad Sector Information BAD 5-18 Displaying Profile Attributes LOG 5-11 5-9 Displaying Common Disk Information -> INFO $SYSTEM, DETAIL STORAGE - Detailed Information Magnetic Common Disk Configuration Information: *BackupCpu............................. *HighPin............................... *PrimaryCpu............................
Displaying Disk Configuration Information Displaying Information About Magnetic Disks Displaying Disk Configuration Information -> INFO $SYSTEM, CONFIG Disk Type Specific Information: *AuditTrailBuffer/SQLMXBuffer (MB)..... *AutoRevive............................ *AutoSelect............................ *AutoStart............................. *CBPoolLen............................. *FSTCaching............................ *FullCheckpoints....................... *HaltOnError...........................
Displaying Information About Magnetic Disks Displaying Disk Configuration Information Explanation of Fields Disk Type Specific Information AuditTrailBuffer/ SQLMXBuffer (MB) shows one of: • • The audit-trail buffer size in megabytes for a TMF audittrail volume. This value is used to improve the performance of systems using the Remote Duplicate Database Facility. The SQLMXBuffer attribute specifies the buffer size (in megabytes) for an SQL/MX session in DP2.
Displaying Information About Magnetic Disks Displaying Disk Configuration Information LKTableSpaceLen the memory (in 128-kilobyte units) to be allocated for lockrelated data structures. The memory available for these structures limits the total number of file and record locks allowed on the disk. MaxLocksPerOCB the maximum number of records that can be locked outside a transaction. MaxLocksPerTCB the maximum number of records and files a transaction can lock.
Displaying Information About Magnetic Disks Displaying Disk Configuration Information Path Information (for each path) Adapter the adapter type and physical location (group, module, slot) of the storage adapter that controls the disk. This value is retrieved from the system. Disk Device ID / Port Name For an internal disk, the SCSI address. For a model 45xx disk connected to an adapter, the slot number of the disk in the modular disk subsystem. This is the address used by the SAC to access the disk.
Displaying Information About Magnetic Disks Displaying Disk Label Information Displaying Disk Label Information -> INFO $SYSTEM, LABEL Disk Label Information $SYSTEM: Disk Label Information $SYSTEM Primary: *Volume Name.......................... $SYSTEM *Alternate Volume Name................ $SYSTEM Volume ID............................ 257 Volume Label Verifier................ D2 Volume Label Version................. 0 Operating System Last Mounted Under.. G06 (Q06) Volume Label Last Written............
Displaying Information About Magnetic Disks Displaying Disk Label Information Explanation of Fields * an attribute whose value you can change by using the ALTER DISK command. Volume Name the default disk name. To change this name, use the VOLNAME attribute of the ALTER DISK Command (page 14-30). To change the volume name and alternate volume name simultaneously, use the RENAME DISK Command (page 14-100). Alternate Volume Name the alternate volume name of the specified disk volume.
Displaying Information About Magnetic Disks Displaying Profile Attributes Displaying Profile Attributes The INFO PROFILE Command (page 14-85) displays configured information about a disk profile. Example of an INFO PROFILE Report -> INFO PROFILE $ZZSTO.#INTERNAL-DISK STORAGE - Detailed Information PROFILE \COMM.$ZZSTO.INTERNAL-DISK *AuditTrailBuffer/SQLMXBuffer (MB)..... 0 *AutoRevive............................ OFF *AutoSelect............................ n/a *AutoStart.............................
Displaying Information About Magnetic Disks Displaying Profile Attributes AutoSelect (magnetic disks only) shows whether a virtual disk process is allowed to automatically consider this physical volume when making file placement decisions. AutoStart (internal SCSI and M8xxx disks only) specifies whether the disk process is automatically started when inserted. CBPoolLen the maximum memory (in 128-KB units) that can be allocated for open-related data structures on the disk.
Displaying Information About Magnetic Disks Displaying Profile Attributes OSSCaching shows whether caching for Open System Services (OSS) files is enabled. PhysvolSelect (magnetic disks only) shows whether a virtual disk process is allowed to consider the physical volume for file placement. Pool the storage pool process with which the disk volume is associated. Program shows the object file name of the disk process.
Displaying Disk Cache Configuration Information Displaying Information About Magnetic Disks Displaying Disk Cache Configuration Information -> INFO $SYSTEM, CACHE Disk cache configuration: Cache Block Size ________________512_________1024_________2048_________4096_ *Blocks Requested: Blocks Allocated: 24 160 Bytes Allocated To Cache: 4608 22 144 21 144 21 1024 K Explanation of Fields * indicates an attribute whose value you can change by using the ALTER DISK command.
Displaying Disk Cache Statistics Displaying Information About Magnetic Disks Displaying Disk Cache Statistics The STATS DISK Command (page 14-114) displays cache statistics about a magnetic disk. -> STATS $AUDIT STORAGE - Stats DISK \ALM171.$AUDIT Current Time............. 07 Jul 2001, 13:12:25.369 Counters Reset Time...... 07 Jul 2001, 10:29:59.176 Elapsed Time............. 0 days, 02:42:26 Bytes Allocated To Cache. 5748 Writes/Control Point..... 0.
Displaying Information About Magnetic Disks Displaying Disk Cache Statistics Blocks Requested the default number of cache blocks that are requested. Blocks Allocated the number of cache blocks allocated. Blocks In Use the number of cache blocks containing a valid disk block in memory. Blocks Dirty the percentage of allocated blocks that are currently dirty (blocks in cache that have been changed but are not yet written back to disk).
Reconfiguring Cache to Resolve Performance Problems Displaying Information About Magnetic Disks Cache Write Cleans the percentage of cache writes for which the block was found unchanged in cache (not dirty). When new data is inserted into a block, the disk process does not have to perform a disk read but it must perform a disk write. This counter is also incremented when an end of file (EOF) is extended (an application appends to the end of a file).
Displaying Information About Magnetic Disks Displaying Error and Current Status Information Displaying Error and Current Status Information The STATUS DISK Command (page 14-119) displays the current status of a disk. Displaying Disk Errors 1. Run DSAP on the suspected volume. DSAP identifies unspared sectors: if an SCF INFO DISK, BAD command confirms that sectors have not been spared, see Sparing a Defective Sector on page 7-14. DSAP identifies doubly allocated file extents.
Displaying Bad Sector Information Displaying Information About Magnetic Disks This display is an example of a disk that has no bad sectors. -> INFO $SYSTEM, BAD Bad Sectors Information $SYSTEM Primary: No bad sectors found. Bad Sectors Information $SYSTEM Mirror: No bad sectors found. This display indicates that a disk that has a bad sector, as recorded in the Spare Tracks Table. -> INFO $DATA01, BAD STORAGE - Bad Sector Information Magnetic DISK \GANESAN.
Displaying Defect Log Information Displaying Information About Magnetic Disks Displaying Defect Log Information The defect log lists defective sectors that have been spared using the CONTROL DISK, SPARE command. -> INFO $DATA01, LOG Defect Log Information $DATA01 Primary: Lifetime defect log report on $DATA01-P 16 May 2001, 11:21:43.973 Physical Sector Address ----------------------- Source ------ %H0029211 Added defect map The defect log contains 1 defects of which 1 were displayed.
Examples of STATUS Reports for Magnetic Disks Displaying Information About Magnetic Disks Examples of STATUS Reports for Magnetic Disks Example 1: Displaying the Status of a Mirrored Disk Page 5-21 Example 2: Displaying the Status and State of All Paths to a Disk Page 5-21 Example 3: Displaying the Status of a Nonmirrored Disk Page 5-22 Example 1: Displaying the Status of a Mirrored Disk To display the status of $SYSTEM: -> STATUS $SYSTEM STORAGE - Status DISK \COMM.
Examples of STATUS Reports for Magnetic Disks Displaying Information About Magnetic Disks Explanation of Fields LDev the logical device number for the disk volume. This number is arbitrarily assigned to a device when you configure the device and every time the system is loaded. Path the disk path assignment. Status shows whether the disk path is the current path (ACTIVE) or not (INACTIVE). State the current SCF state of the disk path.
Displaying Information About Magnetic Disks Examples of STATUS Reports for Magnetic Disks Example 4: Displaying STATUS DISK, CONSISTENCY Information To display the consistency information about the mirrored disk volume $WENDY: -> STATUS $WENDY, CONSISTENCY This display shows that the system-configuration database, the two disk processes, and the two SIFM processes are consistent. 6-> STATUS DISK $WENDY, CONSISTENCY STORAGE - Status DISK \SYS.
Example of STATUS DISK Detailed Report for Magnetic Disks Displaying Information About Magnetic Disks Example of STATUS DISK Detailed Report for Magnetic Disks To display detailed status of $SYSTEM: -> STATUS $SYSTEM, DETAIL STORAGE - Detailed Status DISK \COMM.
Displaying Information About Magnetic Disks Example of STATUS DISK Detailed Report for Magnetic Disks State the current SCF state of the disk path. For an explanation, see Table 2-1, Object States and Substates of Magnetic Disks, on page 2-5. Substate the current SCF substate of each disk path. Primary PID Backup PID the processor number and PIN of the primary and backup disk processes. General Disk Information: Device Type the device type. Magnetic disks are always type 3.
Displaying Information About Magnetic Disks Example of STATUS DISK Detailed Report for Magnetic Disks Hardware Information: Device the path from the ServerNet addressable controller (SAC) to the disk. Values are PRIMARY and MIRROR. Location (group, module, slot) the location (group, module, slot) of the disk. Power the power supply status of the disk. Values can be: DUAL—Powered by two power supplies. SINGLE—Powered by one power supply. NONE—Does not have power.
Displaying Information About Magnetic Disks Example of STATUS DISK Detailed Report for Magnetic Disks Process Information Process information is displayed if the name of the object file for the running disk process is not the same as the name of the object file for the configured disk process. This difference indicates either that the alternate disk process was activated or that the active object file for the configured disk process was renamed.
Displaying Information About Magnetic Disks OSR State Example of STATUS DISK Detailed Report for Magnetic Disks the current state of an online software replacement (OSR) operation: Abort—The alternate disk process is being replaced by the configured disk process. Active—The alternate disk process has replaced the configured disk process and is currently running. Install—The operation to replace the disk process has begun. n/a—No state information is available.
Displaying Information About Magnetic Disks Example of STATUS DISK Detailed Report for Magnetic Disks Alternate program the object-file name of the alternate disk process stored in the SYSnn.CONFALT file. Primary executes the object-file name of the disk process currently running as the primary process. The OSR state and OSR substate fields indicate whether the configured disk process was replaced by the alternate disk process.
Displaying Information About Magnetic Disks Example of STATUS DISK Detailed Report for Magnetic Disks SCF Reference Manual for the Storage Subsystem—529937-008 5- 30
6 Configuring Magnetic Disks This section describes configuring magnetic disks. Magnetic disks share the object type of DISK with virtual disks. See Section 10, Configuring and Managing Virtual Disks. For information about disk load balancing, see Section 8, Disk Load Balancing. For a list of supported disks, see the NonStop S-Series Planning and Configuration Guide and the NonStop NS-Series Planning Guide.
Configuring Magnetic Disks Types of Magnetic Disks Types of Magnetic Disks You can configure four types of magnetic disks for NonStop servers: Type Description Internal SCSI SCSI disks that reside in slots 1 through 18 of NonStop S-series system enclosures. 45xx Fibre Channel disks that reside in slots 0 through 7 of a modular disk subsystem outside of NonStop S-series system enclosures. The disk subsystem connects to the server through a ServerNet/DA Adapter (SNDA).
Considerations for M8xxx Fibre Channel Disks Configuring Magnetic Disks Table 6-1.
Configuring Magnetic Disks Considerations for ESS Disks after the revive is complete. For information about the migratory revive operation, see the Modular I/O Installation Guide. • • • SCF requires that you specify a primary and a backup path when configuring an M8xxx disk. AUTOCONFIGURE is not recommended for M8xxx disks. Confirm that this attribute is OFF before adding M8xxx disks. New M8xxx disks that are being used for the first time must be initialized after they have been added.
Configuring Magnetic Disks System Disk Configuration System Disk Configuration When you configure the system disk, these restrictions exist: • • • • • • You cannot use SCF to configure the system disk. The system generation program configures the system disk. If the system disk is configured improperly, the system halts during system load, and you must use the system generation program to recover.
Automating Disk Configuration Configuring Magnetic Disks Automating Disk Configuration To automate the configuration of internal magnetic disks when you insert the disk into a slot (or, if the system is down, when the next system load occurs), use the ALTER SUBSYS command to set the AUTOCONFIGURE attribute (page 14-63). Automatic configuration enables the system to automatically configure an internal disk when initially detected after a system load, processor reload, or disk insertion. Note.
Configuring Magnetic Disks Enabling Automatic Disk Configuration The storage subsystem looks for a custom profile (page 6-9) for the enclosure. If no custom profile exists, the storage subsystem uses the default profile (page 5-11) to configure the disk. To make internal disk configuration plug and play, enable these attributes: -> ALTER $ZZSTO, AUTOCONFIG ON, AUTOREVIVE ON, AUTOSTART ON 3.
Configuring Internal Magnetic Disks to Start Automatically Configuring Magnetic Disks Configuring Internal Magnetic Disks to Start Automatically Note. HP does not recommend using AUTOSTART with M8xxx Fibre Channel disks.
Configuring Custom Profiles Configuring Magnetic Disks Configuring Custom Profiles You can automatically configure internal magnetic disks by using a custom or default set of attributes, called a profile. This set of attributes has the object type of PROFILE.
Configuring Magnetic Disks Altering a Profile This sequence of actions changes the default attributes for internal disks in enclosure 3: 1. Capture the existing default profile: -> INFO / OUT LOG / PROFILE $ZZSTO.#INTERNAL-DISK, OBEYFORM == STORAGE - Obeyform Information PROFILE \COMM.$ZZSTO.INTERNAL-DISK ADD PROFILE \COMM.$ZZSTO.
Configuring Magnetic Disks Deleting a Custom Profile Deleting a Custom Profile The DELETE PROFILE Command (page 14-78) removes a custom profile from the system configuration database. Considerations for DELETE PROFILE • • You cannot delete the standard profile $ZZSTO.#INTERNAL-DISK. After you delete a custom profile, autoconfiguration uses the default profile. Examples To delete the custom profile for all disks inserted into group 01: -> DELETE PROFILE $ZZSTO.
Configuring Magnetic Disks Mirrored Disk Placement Mirrored Disk Placement Mirroring Without NonStop S-Series Enclosure Interleaving For proper fault tolerance, always install the two disks of a mirrored volume on different SCSI buses: • • For internal disks in a NonStop S-series system enclosure, if you install the primary disk in an odd-numbered slot, install the mirror disk in an even-numbered slot.
Configuring Mirrored Disks Configuring Magnetic Disks Configuring Mirrored Disks The mirroring examples in this section are based on internal SCSI disks. If you are mirroring model 45xx or M8xxx disks, you also need to specify PRIMARYDEVICEID, BACKUPDEVICEID, MIRRORDEVICEID, and MBACKUPDEVICEID attributes.
Configuring Magnetic Disks Changing a Mirrored Volume Into Two Nonmirrored Disks Changing a Mirrored Volume Into Two Nonmirrored Disks This procedure converts a mirrored, internal volume into two nonmirrored disks without destroying files on either disk. 1. Review the Considerations for RENAME DISK on page 6-27. 2. Stop both halves of the mirrored volume: -> STOP $DATA01 3. Delete the mirror from the system configuration database: -> DELETE $DATA01-M 4. Restart the disk process: -> START $DATA01 5.
Configuring Magnetic Disks Remirroring Disks Online Remirroring Disks Online You can perform these tasks without stopping the entire disk volume: • • • • Change the disk configuration from an unmirrored configuration to a mirrored configuration Relocate both the mirror disk and primary disk to new slots Unmirror a disk volume Switch the roles of the two disks of a mirror disk volume Throughout the performance of these tasks, a primary disk drive is always available to applications.
Remirroring Disks Online Configuring Magnetic Disks Considerations for ALTER DISK, SWAPMIRROR, and Online Disk Remirroring • • • The SWAPMIRROR attribute causes the two disk drives of a mirrored disk volume to switch roles: ° ° • The mirror disk drive becomes the primary disk drive. To delete the paths to a primary disk drive when you perform online disk remirroring, you must first use an ALTER DISK, SWAPMIRROR command so that the primary disk drive becomes the mirror disk drive.
Configuring Magnetic Disks Remirroring Disks Online Example of Online Disk Remirroring Note. OSM automatically recognizes online remirrored disks. TSM does not. Anytime you use TSM in conjunction with online disk remirroring, observe these rules: • • Before issuing a sequence of SCF commands that implements online disk remirroring, always stop the TSM process. After you have issued the commands and before you exit SCF, make sure to restart the TSM process. For example: 1.
Configuring Magnetic Disks Adding a Magnetic Disk the primary. You must therefore use the SWAPMIRROR attribute so that the primary disk drive becomes the mirror disk drive: -> ALTER DISK $DATA1, SWAPMIRROR This command converts the original mirror disk drive into the primary, thus making it available to applications. 5. After the disk drive originally serving as the primary has become the mirror, you can issue these commands: -> STOP DISK $DATA1-M -> STOP DISK $DATA1-MB -> DELETE DISK $DATA1-M 6.
Adding a Magnetic Disk Configuring Magnetic Disks Adding a Magnetic Disk Use this procedure for internal disks if autoconfiguration is not enabled. 1. For the PRIMARYLOCATION attribute, note the group, module, and slot location where you install the disk. 2. Add the disk: -> ADD DISK $DATA02, SENDTO STORAGE, PRIMARYLOCATION (1,1,3) 3. Verify the attributes recorded in the system configuration database: -> INFO $DATA02, DETAIL 4. See Starting a Magnetic Disk on page 7-3.
Configuring Magnetic Disks Adding a Similar Disk to This System -> MIRRORPORTNAME 50060E8003501241, & -> MBACKUPPORTNAME 50060E8003501243, & -> MIRRORLUN 17 Adding a Similar Disk to This System To add another disk that is similar to an existing disk, use the LIKE attribute.
Configuring Magnetic Disks • Adding a Similar Disk to Another System Different SAC numbers for PRIMARYSAC and MIRRORSAC if the new locations use different SACs For 45xx, M8xxx, and ESS disks, PRIMARYLOCATION and MIRRORLOCATION are the storage adapter locations instead of disk locations, so the adapter location attributes do not automatically determine the SAC and DEVICEID attributes.
Configuring Magnetic Disks Altering Magnetic Disk Attribute Values Altering Magnetic Disk Attribute Values Use the ALTER DISK Command (page 14-48) to change configured attributes for magnetic disks.
Configuring Magnetic Disks Changing the Values of the Attributes for Magnetic Disks Changing the Values of the Attributes for Magnetic Disks 1. Display detailed information about the configured attributes of the disk you want to alter: -> INFO $DATA00, DETAIL Displayed fields are defined starting on page 5-3. An asterisk (*) indicates the attributes you can alter. 2. Change one or more Magnetic Disk Attributes for the ALTER DISK Command (page 14-49).
Configuring the Size of Disk Cache Configuring Magnetic Disks • • • • There can be up to eight disk processes for each volume. Each disk process in the volume disk-process group requires a minimum configuration for each cache block size. These minimums are determined by the disk process during initialization (that is, after a system-load or when a volume is brought up). The minimum values are based upon a number of factors, such as the physical memory page size and the number of disk processes.
Configuring the Size of Disk Cache Configuring Magnetic Disks 3. Save accumulated statistical data before flushing it: -> STATS / OUT STATSLOG / $DATA10 STORAGE - Stats DISK \COMM.$DATA10 Current Time............. 18 May 2001, 11:34:27.606 Counters Reset Time...... 17 Feb 2001, 12:37:32.929 Elapsed Time............. 89 days, 22:56:54 Bytes Allocated To Cache. 4608 Writes/Control Point..... 0.
Naming a Magnetic Disk Configuring Magnetic Disks Naming a Magnetic Disk All magnetic disk volumes have two names: a default volume name and an alternate volume name. Both can be assigned the same name when you label a volume (by using either the RENAME DISK or ALTER DISK, LABEL command): • • Use the RENAME DISK command when you want to retain use of all the files that reside on the disk you are renaming. Use the ALTER DISK, LABEL command when you want to erase all files on the disk. Caution.
Configuring Magnetic Disks Resolving Disk-Naming Conflicts Resolving Disk-Naming Conflicts When a disk is started, the storage subsystem verifies that the configured name of the disk matches one of the names on the disk label and, if necessary, changes the configured name. Before changing the configured name, the storage subsystem must also verify the new name is not being used by another process. The sequence of events is: 1.
Configuring Magnetic Disks • • Changing the Volume Name and Alternate Volume Name You cannot rename a disk that resides in a storage pool. If you do, the pool process and virtual disks are not informed of the name change. Therefore, before letting you rename a magnetic disk in a storage pool, the storage subsystem manager issues a warning regarding the possible effects on the storage pool process and virtual disks.
Configuring Magnetic Disks Changing Either the Volume Name or Alternate Volume Name Changing Either the Volume Name or Alternate Volume Name The VOLNAME attribute (page 14-30) and ALTNAME attribute (page 14-12) of the ALTER DISK command change the volume name and alternate volume name, respectively, of a stopped disk. When a disk is started, SCF uses the name in the system configuration database to bring up the disk.
Configuring Magnetic Disks Changing Either the Volume Name or Alternate Volume Name 4. View the new volume name: -> INFO $DATA02, LABEL The volume name in the display should be $DEF00. 5. Start the disk: -> START $DATA02 Starting the disk changes the name of the $DATA02 disk to $DEF00 in the system configuration database. 6.
Configuring Magnetic Disks Changing the Volume Name and Alternate Volume Name (Deleting Files) Changing the Volume Name and Alternate Volume Name (Deleting Files) The LABEL attribute (page 14-19) of the ALTER DISK command changes the volume name and deletes all files from the volume. Considerations for LABEL and Magnetic Disks Cautions. • • • The ALTER DISK, LABEL command erases any existing files on the volume that you are labeling.
Configuring Magnetic Disks • Changing the Volume Name and Alternate Volume Name (Deleting Files) When you use the START DISK command on a volume (or when you load the system from tape), SCF uses the default volume name to bring up the disk unless this name is being used by some other device or process. If the default volume name is in use, the storage subsystem automatically uses the alternate volume name.
Configuring Magnetic Disks Relabeling and Initializing a Magnetic Disk Relabeling and Initializing a Magnetic Disk The INITIALIZE DISK Command (page 14-88) re-creates the label and initializes magnetic disk information such as the spare-tracks table. Caution. The INITIALIZE command deletes all existing files on the volume.
Configuring Magnetic Disks Deleting a Magnetic Disk Deleting a Magnetic Disk The DELETE DISK Command (page 14-76) removes a magnetic disk from the system configuration database. Considerations for DELETE DISK and Magnetic Disks • • • • • A disk volume must be STOPPED or not running before you can delete it. You can delete a mirror half of a disk volume while the disk volume is in a STARTED state. You cannot delete only the primary half of a mirrored volume.
7 Managing Magnetic Disks This section describes managing magnetic disks. Magnetic disks share the object type of DISK with virtual disks. See Section 10, Configuring and Managing Virtual Disks). For information about disk load balancing, see Section 8, Disk Load Balancing.
Managing Magnetic Disks Managing Disks Managing Disks When managing disks, review these special considerations: • • • Managing the System Disk on page 7-2 Recovering From the Loss of a Path to a Disk on page 7-2 Troubleshooting Disks on page 7-2 Managing the System Disk You cannot stop access to the system disk because important processes have their object files and swap files on it. Therefore, you cannot stop the last path to the system disk.
Managing Magnetic Disks Starting a Magnetic Disk Starting a Magnetic Disk The START DISK Command (page 14-109) makes a stopped disk accessible to user processes. When finished, the disk is in the STARTED state. Considerations for START DISK • • • • • • New M8xxx disks that have been added and are being used for the first time must be initialized before they can be started. If you are starting a mirrored volume, see Considerations When Reviving a Mirrored Volume on page 7-4.
Managing Magnetic Disks Reviving a Mirrored Disk 4. Confirm that the disk has started: -> STATUS $DISK00 STORAGE - Status DISK \COMM.$DISK00 LDev Primary Backup Mirror 212 *STARTED STARTED *STARTED MirrorBackup STARTED Primary PID 9,262 Backup PID 8,271 5. If the START DISK command fails, see the information on troubleshooting disk drives in the Service and Support Library of the NonStop Technical Library (NTL).
Managing Magnetic Disks Starting a Mirrored Disk Starting a Mirrored Disk 1. Verify the current state of the disk volume: -> STATUS $DSMSCM-* STORAGE - Detailed Status DISK \ALM171.$DSMSCM Disk Path Information: LDev Path Status 98 98 98 98 PRIMARY BACKUP MIRROR MIRROR-BACKUP ACTIVE INACTIVE ACTIVE INACTIVE State Substate STOPPED STOPPED STOPPED STOPPED DOWN DOWN DOWN DOWN Primary PID 0,21 0,21 0,21 0,21 Backup PID 1,15 1,15 1,15 1,15 2.
Managing Magnetic Disks Starting a Mirrored Disk To preserve the older disk and copy it to the disk that has the newer time stamp, start a path to the older disk first. This action causes an update to its timestamp, making it more recent. Then you can start the rest of the volume. To monitor the progress of the revive operation, periodically issue this command: -> STATUS $DSMSCM, DETAIL STORAGE - Detailed Status DISK \ALM171.
Managing Magnetic Disks Changing the Speed of a Revive Operation Changing the Speed of a Revive Operation While a revive operation is in progress, you can use the ALTER command to change the speed of a revive operation. Considerations for Changing the Speed of a Revive Operation • • The speed of all future revive operations is also changed. During system installation, the system administrator should tailor the REVIVEPRIORITY and REVIVERATE attributes for your system.
Managing Magnetic Disks Temporarily Stopping a Revive Operation If you have enabled automatic sector reallocation, the system spares the sector and the revive operation resumes. If automatic sector reallocation is disabled, see Temporarily Stopping a Revive Operation on page 7-8. • Nonfatal checksum errors have stalled a revive operation or put it into a loop. Symptoms are: ° ° ° The revive interval in a STATUS, DETAIL display has become large. The Current Logical Sector remains unchanged.
Managing Magnetic Disks Stopping a Magnetic Disk Stopping a Magnetic Disk These two commands stop access to a magnetic disk: • • STOP DISK command—stops access in an orderly manner ABORT DISK command—stops access immediately Stopping a Disk With the STOP DISK Command The STOP DISK Command (page 14-130) stops access to a magnetic disk in an orderly manner. When finished, the disk is in the STOPPED state, substate DOWN. The disk remains configured in the system configuration database.
Managing Magnetic Disks Stopping a Magnetic Disk With the ABORT DISK Command Stopping a Magnetic Disk With the ABORT DISK Command The ABORT DISK Command (page 14-5) stops access to a magnetic disk when the disk or path to the disk either: • • Is malfunctioning but has not been brought down by the disk Must be removed from the system (but the system currently cannot be reconfigured) Considerations for ABORT DISK • • • • • • • Do not used the ABORT DISK, FORCED option on the system disk.
Managing Magnetic Disks Resetting a Magnetic Disk 3. Confirm that the disk is in the STOPPED state, substate HARDDOWN: -> STATUS $AUDIT-* STORAGE - Status DISK \COMM.
Managing Magnetic Disks Considerations for RESET DISK Considerations for RESET DISK • • The RESET command is ignored if the process is started. If the disk is in the STARTING state, substate REVIVE, the disk process is suspended in that state until either another START command restarts the revive operation or a STOP command terminates the revive operation. Resetting One Magnetic Disk 1. Check the current status of the disk: -> STATUS $DISK00-* 2.
Managing Magnetic Disks Resetting a Group of Magnetic Disks Resetting a Group of Magnetic Disks 1. Identify disks that have paths that are not running: -> STATUS DISK $*-*, SEL NOT STARTED, SUB MAGNETIC 2. Prepare all nonrunning disk paths for a subsequent START command: -> RESET DISK $* 3. To prevent a START DISK command with a wild-card disk name from failing if some disk paths do not start: -> ALLOW ALL ERRORS 4. To prevent a specified disk path from starting: -> ABORT DISK $disk{-P |-B |-M | -MB } 5.
Managing Magnetic Disks Sparing a Defective Sector Sparing a Defective Sector Sector sparing is the process of moving the data on a physically defective sector to a different sector and preventing data from using that defective sector again.
Managing Magnetic Disks Controlling Whether $ZRD9 Starts Automatically After a System Load To disable automatic sector reallocation: > STOP $ZRD9 You might want to disable $ZRD9 if you choose to manually spare a sector. Controlling Whether $ZRD9 Starts Automatically After a System Load • To ensure that $ZRD9 does not start automatically after a system load, do one of the following: ° Stop the process and reconfigure it to be started manually: -> ABORT PROCESS $ZZKRN.
Managing Magnetic Disks Sparing a Sector Manually 1. Confirm that the address reported in the error message also appears in an INFO DISK, BAD report: -> INFO $DATA00, BAD 2. Spare the sector containing the address identified in the BAD report. -> CONTROL $DATA00-M, SPARE %H795C The CONTROL command assigns an alternate sector for the data in the spared sector and makes an entry into the defect log.
Managing Magnetic Disks Correcting Doubly Allocated File Extents Correcting Doubly Allocated File Extents The REBUILDDFS attribute (page 14-71) of the CONTROL DISK command rebuilds the disk free space table. This process also gets rid of doubly allocated file extents. File extent overlaps (doubly allocated file extents) are caused by a hardware or software error.
Managing Magnetic Disks Troubleshooting Doubly Allocated File Extents Troubleshooting Doubly Allocated File Extents 1. Repeat Identifying Doubly Allocated File Extents on page 7-17 to see whether any doubly allocated file extents remain: • • If none remain, you are finished with the procedure and you can restart applications. If doubly allocated file extents remain, continue to the next step. 2.
Managing Magnetic Disks Replacing the Bootstrap Program Replacing the Bootstrap Program Note. The REPLACEBOOT attribute does not apply to Integrity NonStop NS-series servers. Instead, the bootstrap program is installed through firmware update into flash memory. The REPLACEBOOT attribute (page 14-71) of the CONTROL DISK command replaces the disk bootstrap program.
Managing Magnetic Disks Replacing the Disk Bootstrap Program on a Mirrored Volume (NonStop S-Series Servers) 4. Replace the bootstrap program on the primary disk: -> CONTROL DISK $SYSTEM, REPLACEBOOT $SYSTEM.SYSnn.SYSDISC 5. To facilitate recovery of a mirrored volume in the event of failure, SCF asks, Do you want to ABORT $SYSTEM-M? Type yes. Caution. If you type no, the REPLACEBOOT operation updates the diskboot file on both disks simultaneously.
Managing Magnetic Disks Replacing the Disk Bootstrap Program on a Nonmirrored Volume (NonStop S-Series Servers) Replacing the Disk Bootstrap Program on a Nonmirrored Volume (NonStop S-Series Servers) This procedure replaces the disk bootstrap program on an unmirrored volume of a NonStop S-series server. The REPLACEBOOT attribute does not apply to Integrity NonStop NS-series servers. Instead, the bootstrap program is installed through firmware update into flash memory. Caution.
Managing Magnetic Disks Enabling and Disabling File Opens on a Magnetic Disk Enabling and Disabling File Opens on a Magnetic Disk Preventing File Opens on a Magnetic Disk The STOPOPENS DISK Command (page 14-135) prevents applications from opening files on a specific magnetic disk. Considerations for STOPOPENS DISK Caution. Do not issue a STOPOPENS DISK command on the system disk. Issuing a STOPOPENS DISK command on the system disk makes it inaccessible to file-open attempts.
Managing Magnetic Disks Allowing File Opens on a Magnetic Disk Allowing File Opens on a Magnetic Disk The ALLOWOPENS DISK Command (page 14-46) lets applications open files on a specific magnetic disk.
Managing Magnetic Disks Swapping Processors for a Disk Swapping Processors for a Disk The PRIMARY DISK Command (page 14-92) swaps the primary and backup processors for a disk. The current primary processor becomes the backup processor, and the backup processor becomes the primary processor, but the PRIMARYCPU and BACKUPCPU values stay the same. Note. To change the primary or backup processor values for a disk, stop all the disk paths (STOP DISK command) or terminate the disk process (RESET DISK, FORCED).
Managing Magnetic Disks An Example for G06.11 and Later RVUs 1. Display the current status of the disk on which you intend to swap the processors: -> STATUS DISK $D0201-* STORAGE - Status DISK \WAGER.
Managing Magnetic Disks An Example for G06.11 and Later RVUs 3. Display the changed status: -> STATUS DISK $D0201-* STORAGE - Status DISK \WAGER.$D0201-* LDev Path Status State 104 104 104 104 PRIMARY BACKUP MIRROR MIRROR-BACKUP ACTIVE INACTIVE ACTIVE INACTIVE STARTED STARTED STARTED STARTED Substate Primary PID 3,35 3,35 3,35 3,35 Backup PID 2,107 2,107 2,107 2,107 Processor 3 now controls the primary disk process for $D0201, and processor 2 controls the backup disk process.
Managing Magnetic Disks Changing the Active Path for a Magnetic Disk Changing the Active Path for a Magnetic Disk The SWITCH DISK Command (page 14-138) designates the active path to a disk, determines whether the -P or -B path is active and, if the disk is mirrored, whether the -M or -MB path is active. You should configure the -P and -M paths to be active because they are on opposite ServerNet fabrics.
Managing Magnetic Disks Processor 2 X Y Changing the Active Path for a Magnetic Disk $D0201 $D0203 $D0205 $D0207 $D0208 $D0201’ Processor 3 $D0203’ $D0205’ $D0207’ X Y $D0208’ X Y SCSI Bus 1 SAC 1 SAC 2 SAC 1 -MB -M -MB -M -MB -M $D0201-M $D0203-M $D0205-M $D0208-P $D0201-P $D0203-P $D0205-P $D0207-P -P -B -P -B -P -B -B -P -P SCSI Bus 2 • • • • SAC 2 -B VST505.vsd The $D0201 disk process is executing in processor 2.
Managing Magnetic Disks Changing the Active Path for a Magnetic Disk 3. Display the changed status: -> STATUS $D0201-* STORAGE - Status DISK \WAGER.
Managing Magnetic Disks Changing the Active Path for a Magnetic Disk 5. Display the changed status: -> STATUS DISK $D0201-* STORAGE - Status DISK \WAGER.
8 Disk Load Balancing Disk load balancing seeks to distribute the disk work load across all fabrics and processors in the system. This subsection describes load balancing between the X and Y fabrics and pairs of processors in a NonStop S-series processor enclosure. A processor enclosure and its I/O enclosures are called a topology branch. The principles that apply to the internal disks in these examples also apply to 45xx disks in a modular disk subsystem.
Disk Load Balancing Between Processors Disk Load Balancing For example, if $OPER on the PMF CRU in slot 50 is balanced between the X and Y fabrics, the primary (-P or -B) disk OR the mirror (-M or -MB) disk has an asterisk in a detailed INFO ADAPTER display: Slot 50: 2 $OPER-MB … 1 $OPER-P STARTED 0,298 1,269 *STARTED 0,298 1,269 Correspondingly, if $OPER on the PMF CRU in slot 55 is balanced between X and Y, the primary (-P or -B) disk OR the mirror (-M or -MB) disk has an asterisk: Slot 55: 2 $OP
Guidelines for All G-Series RVUs Disk Load Balancing Guidelines for All G-Series RVUs Regardless of RVU: • • • When you change a disk path or primary processor, the change does not actually take place until the next I/O action on the disk. The active paths to any mirrored disk should be either the primary and mirror paths or the backup and mirror-backup paths. This distribution ensures fault-tolerance because the disks are accessed through separate system components.
Topology Branch Example for G06.
A Closer Look at Eight Disks Disk Load Balancing A Closer Look at Eight Disks Looking more closely at the disks in the group 02 processor cabinet, this configuration is an ideal situation for G06.
Disk Load Balancing on G06.10 and Earlier RVUs Disk Load Balancing Disk Load Balancing on G06.10 and Earlier RVUs Understanding SAC Ownership On G06.10 and earlier RVUs each SAC is owned by a processor. A mirrored volume can communicate with its processors through up to four SACs. These events can cause SAC ownership to change: • • • A hardware failure along an active data path to that SAC. A PRIMARY command on a started disk. A processor failure or halt on a primary processor.
Topology Branch Example for G06.
A Closer Look at Eight Disks Disk Load Balancing A Closer Look at Eight Disks Looking more closely at the disks in the group 03 processor cabinet, this configuration is the ideal situation for G06.10 and earlier RVUs: • • • All primary disk processes run in processor 4. All backup disk processes, represented with a prime mark (') run in processor 5. Processor 4 owns all four SACs.
PRIMARY Command Function in G06.00 Through G06.10 Disk Load Balancing 1. Before the PRIMARY command is issued, the status of $D0203 is: STORAGE - Status DISK \WAGER.$D0203-* LDev Path Status State 105 105 105 105 PRIMARY BACKUP MIRROR MIRROR-BACKUP ACTIVE INACTIVE ACTIVE INACTIVE STARTED STARTED STARTED STARTED Substate Primary PID Backup PID 2,22 2,22 2,22 2,22 3,16 3,16 3,16 3,16 In the figures that follow: • • • • SACs owned by processor 2 are shaded.
PRIMARY Command Function in G06.00 Through G06.10 Disk Load Balancing 3. Display the changed status: -> STATUS DISK $D0203-* STORAGE - Status DISK \WAGER.
PRIMARY Command Function in G05.00 and Earlier Disk Load Balancing $D0203 also changes primary processors in because: 1. The disk process executing in processor 2 attempts to access $D0203-P. The path to $D0203-P on the X fabric leads through SAC 2. Because of the PRIMARY command on the other disk, this SAC is now owned by processor 3. Because the disk process is executing in processor 2, the disk access fails. 2.
PRIMARY Command Function in G05.00 and Earlier Disk Load Balancing Processor 2 X Y $D0201 $D0203 $D0205 $D0207 $D0208 $D0201' Processor 3 $D0203' $D0205' $D0207' X Y $D0208' Y X SAC 1 SCSI Bus 1 -MB -M -MB -M $D0201-M $D0203-M $D0205-M $D0208-P $D0201-P $D0203-P $D0205-P $D0207-P -MB -M SAC 2 SAC 1 -P -B -P -B -P -B -B -P -P SAC 2 -B SCSI Bus 2 VST510.vsd 2. Move the primary disk process of another disk in the same topology branch to processor 3: -> PRIMARY $D0201, 3 3.
PRIMARY Command Function in G05.00 and Earlier Disk Load Balancing Processor 2 X Y $D0201' $D0203 $D0205 $D0207 $D0208 $D0201 $D0203' $D0205' $D0207' $D0208' Processor 3 X Y X Y SAC 1 SAC 2 SCSI Bus 1 SAC 1 -MB -M -MB -M -MB -M $D0201-M $D0203-M $D0205-M $D0208-P $D0201-P $D0203-P $D0205-P $D0207-P -P -B -P -B -P -B -B -P -P -B SCSI Bus 2 SAC 2 VST511.vsd $D0203 changes paths to access the disk in because: 1.
Establishing a Disk Load Balance in RVUs Prior to G06.11 Disk Load Balancing This process affects all disk processes that use these SACs. Note. Loss of SAC ownership is detected only when an I/O is attempted. When ownership of both SACs is lost, a read from one or both paths detects a loss of ownership. However, a read from one path whose SAC ownership was not lost would not detect the loss of ownership of the SAC on the path to the other disk. Establishing a Disk Load Balance in RVUs Prior to G06.
Establishing a Disk Load Balance in RVUs Prior to G06.11 Disk Load Balancing 7. The status shows all primary processes in processor 2: -> STATUS $D02*-* STORAGE - Status DISK \WAGER.
Establishing a Disk Load Balance in RVUs Prior to G06.11 Disk Load Balancing 9. Display the changed status: -> STATUS $D02*-* STORAGE - Status DISK \WAGER.
Establishing a Disk Load Balance in RVUs Prior to G06.11 Disk Load Balancing 11. Display the changed status: -> STATUS $D02*-* STORAGE - Status DISK \WAGER.
Maintaining a Disk Load Balance Disk Load Balancing Maintaining a Disk Load Balance • • For fabrics, verify each disk IOP is correctly balancing its load between the X and Y fabrics. See Disk Load Balancing Between Fabrics on page 8-1. For processors, once you have achieved the desired load-balancing scheme, use the STATUS command periodically to monitor that balance. If you have configured all SACs in group 02 to be owned by processor 02, type: -> STATUS ADAPTER $ZZSTO.#*.
9 Configuring and Managing Storage Pools for Magnetic Disks A storage pool is a collection of magnetic disks that are managed by the Storage Management Foundation (SMF). Each storage pool is associated with virtual disks. A storage pool has the object type of POOL.
Configuring and Managing Storage Pools for Magnetic Disks Displaying Information About Storage Pools Displaying Information About Storage Pools To display information about storage pools for magnetic disks: • • Displaying Storage Pool Configuration Information on page 9-2 Displaying Storage Pool Status Information on page 9-5 Displaying Storage Pool Configuration Information The INFO POOL Command (page 14-84) displays configured information about the storage pool.
Configuring and Managing Storage Pools for Magnetic Disks Displaying Storage Pool Configuration Information Example of a Detailed INFO POOL Report -> INFO POOL $POOL3, DETAIL STORAGE - Detailed Info POOL \COMM.$POOL3 *Audited............................... ALLOWED *BackupCPU............................. 7 CatalogLocation....................... $VIRCFG.POOL3CAT *DiskInterval.......................... 2% *DiskThreshold......................... 90% *ExtentInterval........................-1 *ExtentThreshold..
Configuring and Managing Storage Pools for Magnetic Disks Displaying Storage Pool Configuration Information ExtentThreshold shows the threshold for remaining extend allocation space at which the disk processes associated with the physical volume in the storage pool should generate an EMS warning message. HighPin the desired PIN range for the storage pool process. Magnetic Mirrored shows whether magnetic or mirrored volumes are allowed or required in the storage pool.
Configuring and Managing Storage Pools for Magnetic Disks Displaying Storage Pool Status Information Displaying Storage Pool Status Information The STATUS POOL Command (page 14-122) displays current status information about the storage pool. Example of a STATUS POOL Report To display current status information about $POOL3: -> STATUS $POOL3 STORAGE - Status POOL \COMM.
Configuring and Managing Storage Pools for Magnetic Disks Configuring a Storage Pool for Magnetic Disk Drives Configuring a Storage Pool for Magnetic Disk Drives Configuration tasks for storage pools include: • • • • • Adding a Storage Pool on page 9-6 Adding a Magnetic Disk to a Storage Pool on page 9-8 Removing a Magnetic Disk From a Storage Pool on page 9-8 Altering Storage Pool Attribute Values on page 9-9 Deleting a Storage Pool on page 9-10 Adding a Storage Pool Use the ADD POOL Command (page 14-
Configuring and Managing Storage Pools for Magnetic Disks Adding a Storage Pool Example Adding a Similar Pool Process Using the OBEYFORM Attribute To configure one or more pool processes, you can create a command file by using the OBEYFORM attribute of the INFO DISK command. You can copy this file to another system or add it to different configuration file on the current system. 1.
Configuring and Managing Storage Pools for Magnetic Disks Adding a Magnetic Disk to a Storage Pool Adding a Magnetic Disk to a Storage Pool The ALTER DISK Command (page 14-48) adds a disk to an SMF storage pool. Considerations for Adding a Magnetic Disk to a Storage Pool • • • • All the magnetic disks in a storage pool must be on the same system. Up to 144 magnetic disk volumes can be placed in a pool. A magnetic disk volume can be in only one storage pool at a given time.
Configuring and Managing Storage Pools for Magnetic Disks • Altering Storage Pool Attribute Values Avoid overriding any safety checks whenever possible. Excluding a disk from a storage pool even though a discrepancy exists could have severe consequences. For example, storage-managed files on a physical volume are still accessible after the physical volume has been excluded from a storage pool, but the catalog for the storage pool is no longer in a consistent state.
Configuring and Managing Storage Pools for Magnetic Disks Deleting a Storage Pool 4. Restart the storage pool: -> START $POOL00 Deleting a Storage Pool Use the DELETE POOL Command on page 14-77 to delete a storage pool. Considerations for DELETE POOL • • • • • • • • Before deleting a storage pool process from the system configuration database, you must delete the virtual disks associated with the pool and reconfigure the physical volumes.
Configuring and Managing Storage Pools for Magnetic Disks Deleting a Storage Pool Example 1. Identify the physical and virtual volumes associated with the pool: -> INFO $POOL5, DETAIL STORAGE - Detailed Info POOL \COMM.$POOL5 *Audited............................... ALLOWED *BackupCPU............................. 9 CatalogLocation....................... $VIRCFG.POOL5CAT *DiskInterval.......................... 2% *DiskThreshold......................... 90% *ExtentInterval........................
Configuring and Managing Storage Pools for Magnetic Disks Managing a Storage Pool Managing a Storage Pool Management tasks for storage pools include: • • • • Starting a Storage Pool on page 9-12 Stopping a Storage Pool on page 9-13 Resetting a Storage Pool on page 9-13 Swapping Processors for a Pool Process on page 9-13 Starting a Storage Pool The START POOL Command (page 14-111) puts the storage pool into the STARTED state.
Configuring and Managing Storage Pools for Magnetic Disks Stopping a Storage Pool Stopping a Storage Pool The STOP POOL Command (page 14-132), like the ABORT POOL Command, makes a storage pool inaccessible to user requests. -> STOP $POOL5 The storage pool finishes any current activity before it enters the STOPPED state. Virtual disks that use the stopped pool encounter an error.
Configuring and Managing Storage Pools for Magnetic Disks Swapping Processors for a Pool Process SCF Reference Manual for the Storage Subsystem—529937-008 9- 14
10 Configuring and Managing Virtual Disks Virtual disks share the object type of DISK with magnetic disks (discussed in Section 6, Configuring Magnetic Disks). A virtual disk is created by configuring one or more magnetic disks in a storage pool as part of Storage Management Foundation (SMF) (See page 1-2.
Configuring and Managing Virtual Disks Overview of Virtual Disks Overview of Virtual Disks To understand virtual disks: • • • How Virtual Disks Relate to Magnetic Disks on page 10-2 Functions of the Virtual Disk Process on page 10-2 Location-Independent Naming on page 10-2 How Virtual Disks Relate to Magnetic Disks A virtual disk appears to application programs to be a magnetic disk in most respects.
Configuring and Managing Virtual Disks Displaying Information With location-independent naming, the file \SYSA.$DATA00.CURRENT.OVERDUE can reside on any physical volume. With the exception of the node name, the name of the file managed by SMF is independent of its location. SMF controls the mapping of the external name to the internal name.
Configuring and Managing Virtual Disks Displaying Configuration Information for Virtual Disks Example of an INFO DISK Summary Report -> INFO $VDISK00 STORAGE - Info Virtual DISK \COMM.$VDISK00 *ANT ANT *Cache Capacity Location Size 1000000 $P1D02.ZYS00000.A0001MRG 30000 PendOps Location $P1D02.ZYS00000.A0001MRH Pool $POOL1 Explanation of Fields * indicates an attribute whose configured value you can change by using an ALTER DISK command.
Configuring and Managing Virtual Disks Displaying Configuration Information for Virtual Disks Example of an INFO DISK Detailed Report For virtual disks, the INFO DISK, DETAIL command produces a short report (compared to the report for magnetic disks). -> INFO DISK $DATA1, DETAIL STORAGE - Detailed Info Virtual DISK \COMM.$DATA1 *ANTCapacity........................... 1000000 ANTLocation........................... $P1D02.ZYS00000.A0001MRG *BackupCPU............................. 5 *CacheSize................
Displaying Current Status Information Configuring and Managing Virtual Disks Program shows the object file name of the virtual disk process. StartState shows whether the virtual disk process is enabled (STARTED state) or disabled (STOPPED state) when the system is loaded. Configuration State shows the state of the configuration for the virtual disk. For a description of possible states, see Example of a Missing Data Report on page 10-4.
Configuring and Managing Virtual Disks Configuring a Virtual Disk Virtual Disk I/O Process Information: Library File the library file name of the disk process. Program File the program file name of the disk process.
Configuring and Managing Virtual Disks Adding a Virtual Disk Example Adding a Similar Disk Using the LIKE Attribute To add another disk similar to an existing disk on the same system, you can use the LIKE attribute.
Configuring and Managing Virtual Disks Troubleshooting Problems With Adding a Virtual Disk Troubleshooting Problems With Adding a Virtual Disk 1. Use an INFO or STATUS command to detect problems when adding a virtual disk: • • The INFO command displays a process that has a configuration record but the Configuration State is “No Definition With SMF master process.” The STATUS command also displays the Configuration State “No Definition With SMF master process.” 2.
Configuring and Managing Virtual Disks Altering Virtual Disk Attribute Values Altering Virtual Disk Attribute Values The ALTER DISK Command (page 14-48) changes configured attributes for a virtual disk. Considerations for ALTER DISK and Virtual Disks • • • The process must be in the STOPPED state or not running before you can change its configuration. Changes take effect when you restart the process. All configuration changes related to SMF require that: ° ° ° TMF must be running on the system.
Configuring and Managing Virtual Disks Deleting a Virtual Disk Deleting a Virtual Disk The DELETE DISK Command (page 14-76) removes a virtual disk from the system configuration database. Considerations for DELETE DISK and Virtual Disks • • • For the DELETE DISK command to succeed: ° ° ° ° ° The process must be stopped or not running before you can delete it. ° The CATALOGLOCATION volume for the storage pool process must be started and enabled by TMF.
Configuring and Managing Virtual Disks Managing a Virtual Disk Managing a Virtual Disk Virtual disk management tasks include: • • • • Starting a Virtual Disk on page 10-12 Resetting a Virtual Disk on page 10-13 Stopping a Virtual Disk on page 10-13 Swapping Processors for a Virtual Disk on page 10-13 Starting a Virtual Disk The START DISK Command (page 14-109) puts the virtual disk process into the STARTED state.
Configuring and Managing Virtual Disks Resetting a Virtual Disk Resetting a Virtual Disk The RESET DISK Command (page 14-104) puts a virtual disk into the STOPPED state, substate DOWN, ready to be started. 1. Check the current status of the disk: -> STATUS $VDISK00 2. If the disk is in the HARDDOWN state or SERVICING state, substate SPECIAL: -> RESET $VDISK00 3. Start the disk: -> START $VDISK00 4.
Configuring and Managing Virtual Disks Swapping Processors for a Virtual Disk Examples • To execute the primary process of $VDISK00 in processor 3 (assuming it is configured to run in processor 3): -> PRIMARY $VDISK00, 3 • To make the current backup process of $VDISK00 the primary process: -> PRIMARY $VDISK00 SCF Reference Manual for the Storage Subsystem—529937-008 10 -14
11 Configuring and Managing ServerNet Storage Adapters A ServerNet storage adapter has the object type of ADAPTER. For a list of supported storage adapters, see the Storage Management Foundation User’s Guide.
Configuring and Managing ServerNet Storage Adapters • Displaying Storage Adapter Configuration Information To display detailed configuration information about the same adapter in the PMF CRU: -> INFO ADAPTER $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50, DETAIL The display is shown and explained under Example of a Detailed INFO PMF ADAPTER Report on page 11-3. • To display configuration information about the adapter in the IOMF CRU in group 11, slot 50: -> INFO ADAPTER $ZZSTO.#IOMF.GRP-11.MOD-1.
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Configuration Information Example of an INFO PMF ADAPTER Report -> INFO ADAPTER $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50 STORAGE - Info ADAPTER \COMM.$ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50 Location Access List (1,1,50) 0,1 Explanation of Fields Location is where the storage adapter is located (group, module, and slot). Access List is the numbers of the processors configured to access this storage adapter.
Configuring and Managing ServerNet Storage Adapters • Displaying Storage Adapter Configuration Information Has a tape drive on SAC 3 Explanation of Fields Access List the numbers of the processors that can access this storage adapter. Location (Group, Module, Slot) where the storage adapter is located. ServerNet Addressable Controllers: SAC the name of the SAC, determined automatically by the storage adapter hardware.
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Configuration Information Example of a Detailed INFO IOMF ADAPTER Report -> INFO ADAPTER $ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-50, DETAIL STORAGE - Detailed Info ADAPTER \COMM.$ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-50 Access List................... 0,1 Location (Group,Module,Slot).. (11,1,50) ServerNet Addressable Controllers: SAC \COMM.$ZZSTO.#IOMF.SAC-1.GRP-11.MOD-1.
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Configuration Information See Explanation of Fields on page 11-3. Example of a Detailed INFO SNDA ADAPTER Report -> INFO ADAPTER $ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-51, DETAIL STORAGE - Detailed Info ADAPTER \COMM.$ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-51 Access List................... 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 Location (Group,Module,Slot).. (11,1,51) ServerNet Addressable Controllers: SAC \COMM.$ZZSTO.#SNDA.SAC-1.GRP-11.MOD-1.
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Example of a Detailed INFO FCSA Adapter Report -> INFO ADAPTER $ZZSTO.#FCSA.GRP-11.MOD-2.SLOT-1, DETAIL STORAGE - Detailed Info ADAPTER \IO.$ZZSTO.#FCSA.GRP-11.MOD-2.SLOT-1 ServerNet Addressable Controllers: SAC \IO.$ZZSTO.#FCSA.SAC-1.GRP-11.MOD-2.
Configuring and Managing ServerNet Storage Adapters • Displaying Storage Adapter Status Information To display status of the 6760 ServerNet device adapter in group 11, slot 51: -> STATUS ADAPTER $ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-51 The display is shown and explained under Example of a STATUS SNDA ADAPTER Report on page 11-13. • To display detailed status of the same 6760 ServerNet device adapter: -> STATUS ADAPTER $ZZSTO.#SNDA.GRP-11.MOD-1.
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Example of a Detailed STATUS PMF ADAPTER Report -> STATUS ADAPTER $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50, DETAIL STORAGE - Detailed Adapter Type..... Location......... Part ID.......... Power-1.......... Revision Level... Tracking Number.. Status ADAPTER \COMM.$ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50 PMF (1,1,50) Number of SACs... 3 142184 POST Result...... PASSED ON Power-2.......... ON A03-05 Status...........
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Explanation of Fields Adapter Type the type of adapter. Possible values: PMF, PMF2, IOMF, IOMF2, SNDA, and FCSA Location the location of the adapter (group, module, slot). Number of SACs the number of SACs present in the adapter (3 SACs for a PMF CRU or IOMF CRU, up to 4 SACs for an SNDA, and 2 SACs for an FCSA). Part ID the vendor number stored in the adapter.
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Example of a STATUS IOMF ADAPTER Report -> STATUS ADAPTER $ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-50 STORAGE - Status ADAPTER \COMM.$ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-50 Location Status POST Power-1 Power-2 SACs (11,1,50) PRESENT PASSED ON ON 3 See Explanation of Fields on page 11-8.
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Example of a Detailed STATUS IOMF ADAPTER Report -> STATUS ADAPTER $ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-50, DETAIL STORAGE - Detailed Adapter Type..... Location......... Part ID.......... Power-1.......... Revision Level... Tracking Number.. Status ADAPTER \COMM.$ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-50 IOMF (11,1,50) Number of SACs... 3 129574 POST Result...... PASSED ON Power-2.......... ON A10-15 Status...........
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Example of a STATUS SNDA ADAPTER Report -> STATUS ADAPTER $ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-51 STORAGE - Status ADAPTER \COMM.$ZZSTO.#SNDA.GRP-11.MOD-1.
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Example of a Detailed STATUS SNDA ADAPTER Report -> STATUS ADAPTER $ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-51, DETAIL STORAGE - Detailed Adapter Type..... Location......... Part ID.......... Power-1.......... Revision Level... Tracking Number.. Status ADAPTER \COMM.$ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-51 SNDA (11,1,51) Number of SACs... 4 123201 POST Result...... PASSED ON Power-2.......... ON B02-04 Status...........
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Example of a STATUS FCSA ADAPTER Report -> STATUS ADAPTER $ZZSTO.#FCSA.GRP-11.MOD-2.SLOT-1 Location (11,2,1) Status PRESENT POST PASSED Power-1 ON Power-2 SACs ON 2 See Explanation of Fields on page 11-8. Example of a STATUS FCSA ADAPTER, SACS -> STATUS ADAPTER $ZZSTO.#FCSA.GRP-11.MOD-2.SLOT-1, SACS STORAGE - Detailed Adapter Type..... Flash Boot....... Flash Firmware... Location......... Part ID.......
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Connection indicates the Fibre Channel connections type. Port Id designates the controller identifier from the Fabric Switch Name Server. (For the Loop connection type, Port Id is equal to controller AL_PA.
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Example of a STATUS FCSA ADAPTER, VPROCS Report -> STATUS ADAPTER $ZZSTO.#FCSA.GRP-11.MOD-2.SLOT-1, VPROCS STORAGE - Vprocs Status ADAPTER \IO.$ZZSTO.#FCSA.GRP-11.MOD-2.SLOT-1 SAC-1 Firmware.......T0630G06^25JUN2004^20APR2004^15 SAC-2 Firmware.......T0630G06^25JUN2004^20APR2004^15 Flash Firmware.......T0630G06^25JUN2004^23APR2004^16 Flash Boot..........
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Example of a Detailed STATUS FCSA ADAPTER Report -> status adapter $ZZSTO.#FCSA.GRP-11.MOD-2.SLOT-1, DETAIL STORAGE - Detailed Adapter Type..... Flash Boot....... Flash Firmware... Location......... Part ID.......... Power-1.......... Revision Level... Tracking Number.. Status ADAPTER \IO.$ZZSTO.#FCSA.GRP-11.MOD-2.SLOT-1 FCSA T0612G06 Flash Update Active.... Done T0630G06 Flash Update Result....
Configuring and Managing ServerNet Storage Adapters Displaying Storage Adapter Status Information Port Id designates the controller identifier from the Fabric Switch Name Server. (For the Loop connection type, Port Id is equal to controller AL_PA.
Configuring and Managing ServerNet Storage Adapters Configuring a Storage Adapter Configuring a Storage Adapter Configuration tasks for storage adapters include: • • Checking the Automatic Configuration of Storage Adapters on page 11-20 Deleting an Adapter on page 11-21 Checking the Automatic Configuration of Storage Adapters When you physically install an adapter, it is automatically added to the system configuration database.
Configuring and Managing ServerNet Storage Adapters Deleting an Adapter Deleting an Adapter All ServerNet addressable controller (SAC) records associated with the adapter are deleted. Considerations for DELETE ADAPTER You must physically remove the storage adapter before deleting the adapter from the system configuration database.
Configuring and Managing ServerNet Storage Adapters Managing a Storage Adapter Managing a Storage Adapter Management tasks for storage adapters include: • • Troubleshooting Adapter Installation on page 11-22 Changing the Active Path for a Storage Adapter on page 11-23 Troubleshooting Adapter Installation If the slot that you want to install an adapter in was previously configured for another adapter, you get an EMS message (storage message 1041) and the adapter is not configured.
Configuring and Managing ServerNet Storage Adapters Changing the Active Path for a Storage Adapter Changing the Active Path for a Storage Adapter The SWITCH ADAPTER Command on page 14-137 moves all device paths from and to a SAC on an adapter. Use this command before replacing a device that contains a storage adapter and dual paths. Considerations for SWITCH ADAPTER • • • • The SWITCH ADAPTER command replaces a series of SWITCH commands for individual paths and devices in the topology branch.
Configuring and Managing ServerNet Storage Adapters • • • • Displaying Information About Connections to SACs on an FCSA Operational firmware downloaded through a REPLACE command does not remain in effect beyond the next system load. A system load reverts to the standard firmware file names in the specified SYSnn. Flash firmware replacement is permanent until the next replacement.
12 Configuring and Managing Open SCSI Devices An Open SCSI device is a device that obeys the ANSI standard protocol for the small computer system interface (SCSI) to communicate with the system through the Open SCSI I/O process. An Open SCSI device has the object type of SCSI. The SCSI object can also represent Fibre Channel devices that use the SCSI protocol to communicate with the system. These devices are called Open SCSI Fibre Channel devices.
Configuring Paths for Open SCSI Devices Configuring and Managing Open SCSI Devices Configuring Paths for Open SCSI Devices The values you specify when configuring an Open SCSI device vary depending on the type of connection and the NonStop server model. For example, the valid ranges for group, module, and slot of an Open SCSI device connected to an FCSA on an Integrity NonStop NS-series server differ from those of an Open SCSI device connected to an ServerNet/DA on a NonStop S-series server. Note.
Configuring and Managing Open SCSI Devices Displaying Information About an Open SCSI Device Displaying Information About an Open SCSI Device Displaying Configuration Information The INFO SCSI Command (page 14-86) displays configured information about an Open SCSI device. Example of an INFO SCSI Report -> INFO SCSI $S11500 STORAGE - Info SCSI configuration \COMM.$S11500 Primary Backup *SCSI ID / Port *LUN *Program Location Location (11,1,50) 0 0 $SYSTEM.SYSTEM.
Displaying Configuration Information Configuring and Managing Open SCSI Devices Examples of Detailed INFO SCSI Reports This example shows an INFO DETAIL report for an Open SCSI device connected to an IOMF CRU: -> INFO SCSI $S11500, DETAIL STORAGE - Detailed Info SCSI configuration \COMM.$S11500 I/O Process Information: *BackupCpu............................. 0 *HighPin............................... ON *PrimaryCpu............................ 1 *Program............................... $SYSTEM.SYSTEM.
Configuring and Managing Open SCSI Devices Displaying Configuration Information Explanation of Fields I/O Process Information: * indicates an attribute whose value you can change by using an ALTER SCSI command. BackupCpu the processor number of the backup IOP. HighPin shows whether the IOP can run at a high PIN (ON) or a low PIN (OFF). The PIN is the process identification number. PrimaryCpu the processor number of the primary IOP. Program the object file name of the IOP.
Displaying Status Information Configuring and Managing Open SCSI Devices SAC Name the name of the SAC on the adapter, determined by the location of the adapter in the system. SAC Number the subdevice number of the SAC on the adapter which determines which SCSI bus accesses the device. SCSI ID / Portname For Open SCSI devices, the SCSI ID that the IOP uses to access the device. For Open SCSI Fibre Channel devices, the worldwide name (WWN) that the IOP uses to access the device.
Configuring and Managing Open SCSI Devices Displaying Status Information Explanation of Fields SCSI Path Information: LDev the logical device number for the device. This number is arbitrarily assigned to a device when you configure the device and every time the system is loaded. Path the Open SCSI device path assignment. Status shows whether the device path is the current path (ACTIVE) or not (INACTIVE). State the current state of the device path.
Configuring and Managing Open SCSI Devices Configuring an Open SCSI Device Configuring an Open SCSI Device Adding an Open SCSI Device The ADD SCSI Command (page 14-38) adds an Open SCSI device to the system configuration database: 1. Physically install the device. 2. Based on the manufacturer documentation, verify the SCSI ID of the device is the same as the configured SCSIID value. 3.
Configuring and Managing Open SCSI Devices Adding an Open SCSI Fibre Channel Device 1. Capture the configuration for an existing Open SCSI device: -> INFO / OUT LOG / $S11502, OBEYFORM == STORAGE - Detailed Info SCSI in obeyform: \COMM.$S11502 ADD SCSI $S11502 , & SENDTO STORAGE , & BACKUPCPU 0 , & HIGHPIN ON , & LUN 0 , & MAXOPENS 4 , & NUMIO 8 , & PRIMARYCPU 1 , & PRIMARYLOCATION (11,1,50) , & PRIMARYSAC 5 , & PROGRAM $SYSTEM.SYSTEM.
Configuring and Managing Open SCSI Devices Deleting an Open SCSI Device Considerations for ALTER SCSI • • • The process must be in the STOPPED state or not running before you can change its configuration. Changes take effect when you restart the process. Verify the SCSI ID of the device is the same as the configured SCSIID value. Changing the Values of the Attributes for an Open SCSI Device 1. Stop the device: -> STOP $S11500 2. Verify the device is in the STOPPED state: -> STATUS $S11500 3.
Configuring and Managing Open SCSI Devices Managing an Open SCSI Device Managing an Open SCSI Device Resetting an Open SCSI Device The RESET SCSI Command (page 14-106) puts an Open SCSI device into the STOPPED state, substate DOWN, reading for restarting: 1. Check the current status of the Open SCSI device: -> STATUS $S11500 2. If it is not in the STOPPED state, substate DOWN: -> RESET $S11500 3. Start the Open SCSI device: -> START $S11500 4.
Configuring and Managing Open SCSI Devices Swapping Processors for an Open SCSI Device Considerations for SWITCH SCSI • • You can use this command only on Open SCSI devices that are configured with dual paths (by using PRIMARYLOCATION and BACKUPLOCATION attributes in the ADD SCSI command). Use the STATUS SCSI command to verify the path switch. Example 1. Switch the primary and backup paths of the device: -> SWITCH $S11500-P 2.
13 Configuring and Managing Tape Drives This section describes configuring tape drives. The tape drive processes on the system have the object type of TAPE.
Configuring Paths for Tape Devices Configuring and Managing Tape Drives Configuring Paths for Tape Devices The values you specify when configuring a tape device depend on the type of connection and the NonStop server model. For example, the valid ranges for group, module, and slot of a tape device connected to an FCSA on an Integrity NonStop NS-series server differ from those of a tape device connected to an IOMF CRU on a NonStop S-series server. Note.
Configuring and Managing Tape Drives Displaying Information Displaying Information To display information about tape drives: • • Displaying Configuration Information on page 13-3 Displaying Status Information on page 13-5 Displaying Configuration Information The INFO TAPE Command (page 14-87) displays configuration information about a tape drive. Example of an INFO TAPE Report -> INFO $DLT23 STORAGE - Info TAPE configuration \COMM.
Configuring and Managing Tape Drives Displaying Configuration Information Examples of INFO TAPE Detailed Reports This example shows an INFO DETAIL report for a tape drive connected to a PMF CRU: -> INFO TAPE $DLT23, DETAIL STORAGE - Detailed Info TAPE configuration \COMM.$DLT23 Adapter Name.......................... $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-55 *Adapter Location (Group,Module,Slot).. (1,1,55) *BackupCpu............................. 0 *Compression........................... ON *Density..................
Displaying Status Information Configuring and Managing Tape Drives Compression for cartridge tape drives, shows whether compression is configured. This setting is ignored by a 5194 tape drive because compression is always on. For other tape drives, this field is not applicable (N/A). Density the configured tape density in bpi of a 5170 tape drive. DeviceID/PortName for SCSI devices, the device ID that is configured for the device. This ID must match the SCSI ID that is physically set in the device.
Displaying Status Information Configuring and Managing Tape Drives Example of a Detailed STATUS TAPE Report -> STATUS $DLT24, DETAIL STORAGE - Detailed Status TAPE \COMM.$DLT24 Tape Process Information: LDev State Primary PID 370 STARTED 1,283 Backup PID 0,285 DeviceStatus ONLINE, BOT Tape I/O Process Information: Library File....... Program File....... $SYSTEM.SYS01.OTPPROCP Current Settings: ACL................ Checksum Mode...... *Density............ Opens.............. Short Write Mode...
Configuring and Managing Tape Drives Buffer Level Displaying Status Information the level of buffering provided by the tape process. Buffering can increase the performance of a write operation when no errors occur. Values can be: UNSUPPORTED—The buffering level is unsupported or unknown. RECORD—No buffering is performed on tape writes (every record written to the tape process is passed to the tape drive immediately).
Configuring and Managing Tape Drives Short Write Mode Displaying Status Information shows how the tape process handles write requests of less than 24 bytes. Values can be: ALLOWED, NONPADDED—Short writes are allowed (no data padding is performed). ALLOWED, PADDED—Short writes are allowed (but data is padded with zeros to a length of 24 bytes). NOT ALLOWED—Short writes are not allowed. UNSUPPORTED—Short writes are not supported for this tape drive.
Configuring and Managing Tape Drives Configuring a Tape Drive Configuring a Tape Drive Configuration tasks for tape drives include: • • • Adding a Tape Drive on page 13-9 Altering Tape Drive Attribute Values on page 13-11 Deleting a Tape Drive on page 13-12 Adding a Tape Drive The ADD TAPE Command (page 14-42) adds a tape drive to the system configuration database. Considerations for ADD TAPE • • • • • Before adding a SCSI tape drive, verify the SCSI interface is properly terminated.
Configuring and Managing Tape Drives Adding a Tape Drive Adding a Similar Tape Drive Using the OBEYFORM Attribute To configure the same or a similar tape drive, you can create a command file by using the OBEYFORM attribute of the INFO TAPE command. You can copy this file to another system or add it to different configuration file on the current system. 1. Capture the configuration for an existing tape drive: -> INFO / OUT LOG / $TAPE0, OBEYFORM == STORAGE - Detailed Info TAPE in obeyform: \COMM.
Configuring and Managing Tape Drives Altering Tape Drive Attribute Values Altering Tape Drive Attribute Values The ALTER TAPE Command (page 14-65) alters the attributes of a tape drive in the system configuration database. For a description of alterable tape attributes, see pages 14-66 through 14-68. Considerations for ALTER TAPE • • The process must be in the STOPPED state or not running before you can change its configuration. Changes take effect when you restart the process.
Configuring and Managing Tape Drives Deleting a Tape Drive Deleting a Tape Drive The DELETE TAPE Command (page 14-79) removes a tape drive from the system configuration database. Considerations for DELETE TAPE • • Stop the tape drive before deleting it. If the DELETE TAPE command does not work, try using the RESET TAPE, FORCED command and then issue the DELETE command. Example 1. Verify the tape drive is in the STOPPED state: -> STATUS $TAPE0 2.
Configuring and Managing Tape Drives Managing a Tape Drive Managing a Tape Drive Management tasks for tape drives include: • • • • Enabling or Disabling Labeled-Tape Processing on page 13-13 Resetting a Tape Drive on page 13-14 Starting a Tape Drive on page 13-14 Stopping a Tape Drive on page 13-15 For information about I/O commands for managing tape drives, see the Guardian Procedure Calls Reference Manual.
Configuring and Managing Tape Drives Resetting a Tape Drive 4. Restart all available tape drives: -> START TAPE $* Resetting a Tape Drive The RESET TAPE Command (page 14-107) puts a tape drive into the STOPPED state, substate DOWN, reading for restarting: 1. Check the current status of the tape drive: -> STATUS $S11500 2. If it is not in the STOPPED state, substate DOWN: -> RESET $TAPE0 3. Start the tape drive: -> START $TAPE0 4.
Configuring and Managing Tape Drives Stopping a Tape Drive Stopping a Tape Drive The STOP TAPE Command (page 14-133) makes a tape drive inaccessible to user requests: 1. Stop the tape drive: -> STOP $TAPE0 2.
Configuring and Managing Tape Drives SCF Reference Manual for the Storage Subsystem—529937-008 13 -16 Stopping a Tape Drive
14 Storage Subsystem Commands This section provides the syntax and description of SCF commands. Overview of Storage Subsystem Commands Table 14-1. Overview of Storage Subsystem Commands Command Page Description ABORT 14-5 Terminates the operation of an object without regard to the current state of its operation. ADD 14-8 Defines an object to the subsystem. ALLOWOPENS 14-46 Allows an object to once again accept opens; reverses the effect of the STOPOPENS command.
SCF Commands and Object Types Storage Subsystem Commands Table 14-1. Overview of Storage Subsystem Commands (continued) Command Page Description STOPOPENS 14-135 Prevents any additional opens to an object. SWITCH 14-137 Designates the active a path to a device VERSION 14-140 Displays the version level of the current subsystem. SCF Commands and Object Types Table 14-2.
Storage Subsystem Commands Commands That Behave Differently When Used in a Command File Commands That Behave Differently When Used in a Command File Some commands that display prompts for user action when used in interactive mode (at the command prompt) behave differently when used in noninteractive mode (in a command file). As a result, these commands cannot be used in a command file except where noted.
Sensitive Commands Storage Subsystem Commands Sensitive Commands Only these users can issue a sensitive command: • • • A super-group user (255,n) The owner of the subsystem A member of the group of the owner of the subsystem The owner of a subsystem is the user who started that subsystem.
ABORT Command Storage Subsystem Commands ABORT Command The ABORT command stops access to an object as quickly as possible. Supported objects are: DISK page 14-5 MON page 14-6 POOL page 14-6 ABORT is a sensitive command. ABORT DISK Command The ABORT DISK command puts a disk into the STOPPED state, substate HARDDOWN, but leaves the disk process running.
Storage Subsystem Commands ABORT MON Command SUB { ALL | MAGNETIC | VIRTUAL } specifies that the command affects only disks of the specified type. The default is ALL. ABORT DISK Examples • To immediately stop the mirror path of $DATA00: -> ABORT $DATA00-M • To immediately stop the mirror paths of $DATA00 and $DATA01, even if files are open or if all other paths to the disk are down: -> ABORT ($DATA00-M, $DATA01-M), FORCED See Stopping a Magnetic Disk With the ABORT DISK Command on page 7-10.
Storage Subsystem Commands ABORT POOL Command OUT file-spec directs all SCF output to the specified file. POOL $pool is the storage pool process. ABORT POOL Consideration Use the RESET Command on page 14-104 to prepare the process for restarting.
ADD Command Storage Subsystem Commands ADD Command The ADD command defines an object in the storage subsystem and adds the object to the system configuration database. ADD is a sensitive command. ADD DISK Command The ADD DISK command adds a magnetic or virtual disk to the system configuration. The syntax is: ADD [ / OUT file-spec / ] DISK $disk , SENDTO STORAGE [ , LIKE object ] [ , attribute-spec ]... Wild-card characters are not supported for this command.
Storage Subsystem Commands ADD DISK Command Magnetic Disk Attributes for the ADD Command These attributes are valid for the ADD DISK command.
Storage Subsystem Commands ADD DISK Command Virtual Disk Attributes for the ADD Command These virtual disk attributes are valid for the ADD DISK command. For a complete description of these attributes, see Disk Attribute Descriptions on page 14-12. [ , , [ , [ , [ , [ , , , [ , [ , [ , , ANTCAPACITY number ] ANTLOCATION { $vol | $vol.subvol.fileid } BACKUPCPU number ] CACHESIZE number ] HIGHPIN { ON | OFF } ] MODE { NOISY | QUIET } ] PENDOPSLOCATION { $vol | $vol.subvol.
Storage Subsystem Commands -> -> -> -> -> -> -> -> -> ADD DISK Command MIRRORSAC 2, & MBACKUPLOCATION (11,2,5), & MBACKUPSAC 2 & PRIMARYPORTNAME 50060E8003501213, & BACKUPPORTNAME 50060E8003501225 & PRIMARYLUN 16 & MIRRORPORTNAME 50060E8003501241, & MBACKUPPORTNAME 50060E8003501243, & MIRRORLUN 17 ADD DISK Example for Virtual Disks See the procedure and considerations for Adding a Virtual Disk on page 10-7.
Storage Subsystem Commands Disk Attribute Descriptions Disk Attribute Descriptions This list describes all the attributes that can be used to define magnetic disks, virtual disks, and disk profiles. Attributes that are not valid for certain commands, the PROFILE object, or virtual disks are indicated accordingly. ALTNAME $vol is an alternate volume name for the disk. Note. This attribute is not valid for the ADD DISK command and the PROFILE object.
Storage Subsystem Commands Disk Attribute Descriptions AUDITTRAILBUFFER number (TMF audit-trail volumes only) is the audit-trail buffer size (in megabytes) for an audit volume. This value improves the performance of systems that use the Remote Duplicate Database Facility. number is in the range 0 (no buffer specified) through 768. The default is 0. Do not use this attribute for SQL/MX volumes. If you specify too large or small a value, DP2 automatically sets the needed size.
Disk Attribute Descriptions Storage Subsystem Commands AUTOSELECT { ON | OFF } specifies whether a virtual disk process is allowed to automatically consider this physical volume when making file-placement decisions. This attribute is valid only when this physical volume is a member of a storage pool. ON Enable automatic selection (default). OFF Disable automatic selection.
Storage Subsystem Commands Disk Attribute Descriptions If you configure a disk volume for use with an FCSA connected to an ESS, you cannot specify BACKUPDEVICEID. BACKUPLOCATION ( group, module, slot ) (45xx and M8xxx disks only) is the location of the adapter that controls the backup path to the device. Note. This attribute is not valid for the PROFILE object. This attribute is optional if BACKUPSAC is given in name format but required if BACKUPSAC is given in number format.
Disk Attribute Descriptions Storage Subsystem Commands CACHE { ( block-size, num-blocks ) | ( ( block-size, num-blocks ), ( block-size, num-blocks ) ) } specifies the disk cache configuration for an in-use volume. Note. This attribute is not valid for the ADD DISK command and the PROFILE object. Disk cache configuration is the number and size of sectors read from disk and stored in the processor for use as virtual memory.
Storage Subsystem Commands Disk Attribute Descriptions unless you load the system from a saved system configuration database that contains a smaller value for this attribute. FORCED specifies that the disk attribute values be changed without any interaction with the user. SCF does not prompt for confirmation.
Storage Subsystem Commands Disk Attribute Descriptions number is one of: 1 Never halt a processor (default). No processor halts, and the primary or backup disk process that detects an unrecoverable disk-process error can go into the STOPPED state, substate DOWN. 2 Never halt the backup processor. The primary processor halts, but the backup disk process can go into the STOPPED state, substate DOWN, if it detects an unrecoverable diskprocess error. 3 Never halt the primary processor.
Storage Subsystem Commands Disk Attribute Descriptions IGNOREINCONSISTENCY specifies that a command can create an inconsistency between the system configuration database and the SMF catalogs maintained by the SMF manager process, storage pools, and virtual disks. Note. This attribute is not valid for the PROFILE object. Use this attribute only if you understand SMF architecture and know how to restore consistency between the system configuration database and the SMF catalogs.
Disk Attribute Descriptions Storage Subsystem Commands MAXLOCKSPERTCB number is the maximum records and files that a transaction can lock. number is in the range 5000 through 100000. The default is 5000. You can increase the value of this attribute while the disk is in the STARTED state. However, to decrease the value of this attribute, the disk must be in the STOPPED state.
Disk Attribute Descriptions Storage Subsystem Commands The ESS administrator must give you the WWN so that you can specify it in this attribute. Enter number as a 16 character hexadecimal number, without a leading %H. MBACKUPSAC { number | name } (mirrored 45xx and mirrored M8xxx disks only) is the SAC that controls the mirror backup path to the disk. Note. This attribute is not valid for the PROFILE object. number Is the SAC subdevice number on the adapter.
Storage Subsystem Commands Disk Attribute Descriptions ON Enables automatic configuration as half of a mirrored disk. A disk in an odd-numbered slot is assigned the next-higher slot number for its mirror; a disk in an even-numbered slot is assigned the next-lower slot number for its mirror. (Default) OFF Disables automatic mirroring. MIRRORLOCATION ( group, module, slot ) for internal disks, is the location of the mirror half of the disk volume. Note.
Storage Subsystem Commands Disk Attribute Descriptions MIRRORSAC { number | name } (mirrored 45xx and M8xxx disks only) is the SAC that controls the mirror path to the disk. Note. This attribute is not valid for the PROFILE object. number Is the SAC subdevice number on the adapter. name Is the full name of the SAC location including the SAC number. For example: SNDA.SAC-1.GRP-1.MOD-1.SLOT-53 FCSA.SAC-1.GRP-11.MOD-2.
Storage Subsystem Commands Disk Attribute Descriptions NONAUDITEDINSERT { ON | OFF } (magnetic disks) specifies whether nonaudited insert mode is enabled (ON) or disabled (OFF). ON enhances performance by buffering insertions to entry-sequenced files or relative-sequenced files that do not have the REFRESH attribute set and are open with a SYNCDEPTH greater than 0. This feature is known as nonaudited insert mode.
Disk Attribute Descriptions Storage Subsystem Commands POOL $pool (for virtual disks) is the name of the storage pool process associated with the virtual disk. Note. This attribute is required when adding virtual disks. It has no default and it cannot be used with the ALTER DISK command. The storage pool process must be in the STARTED state. In addition, the CATALOGLOCATION volume (page 14-31) of that storage pool process must be in the STARTED state and enabled in TMF.
Storage Subsystem Commands Disk Attribute Descriptions PRIMARYLOCATION ( group, module, slot ) (for internal disks) is the location of the slot where the primary disk of the mirrored volume is installed. Note. This attribute is not valid for the PROFILE object. (for 45xx, ESS, and M8xxx magnetic disks) is the location of the adapter that controls the primary path to the disk. This attribute is optional if PRIMARYSAC is given in name format but required if given in number format.
Disk Attribute Descriptions Storage Subsystem Commands number is the SAC subdevice number on the adapter. If you specify PRIMARYSAC in number format, you must also specify the PRIMARYLOCATION attribute. name is the full name of the adapter location including the SAC number. For example: PMF.SAC-1.GRP-1.MOD-1.SLOT-55 FCSA.SAC-1.GRP-11.MOD-2.SLOT-5 Use this form to override the default selection of which adapter gets the -P path and which gets the -B path. PROGRAM [[$vol.]subvol.
Disk Attribute Descriptions Storage Subsystem Commands During the process of reviving a mirrored disk volume, DP2 must perform the timeconsuming task of copying data from the STARTED half of the disk volume to the half that is in the REVIVE substate. The REVIVEPRIORITY attribute specification can lessen the impact of this task on system resources by giving the task a lower priority. For example, if REVIVEPRIORITY is 50, the revive process defers to new requests with a priority above 50.
Storage Subsystem Commands Disk Attribute Descriptions SERIALWRITES { ENABLED | DISABLED } (mirrored volumes only) specifies whether serial writes are used when updating files. ENABLED Perform serial writes if the mirror disk is available. If the primary or mirror disk is not available, and if FULLCHECKPOINTS (page 14-17) is ENABLED or FORCED, full-block checkpoints protect the validity of the data. ENABLED minimizes potential data loss caused by certain processor error conditions.
Storage Subsystem Commands Disk Attribute Descriptions TYPE { MAGNETIC | VIRTUAL } is the type of disk you are adding. The default is MAGNETIC. Note. This attribute is not valid for the ALTER DISK command and the PROFILE object. VOLNAME $vol is the default volume name for the disk. This name is used when the system first tries to start the volume. This attribute changes the volume name on the label of the disk but does not change the system configuration database. Note.
Storage Subsystem Commands ADD MON Command ADD MON Command The ADD MON command adds the $ZSMS master Storage Management Foundation (SMF) process to the system configuration database. The syntax is: ADD [ / OUT file-spec / ] MON $ZSMS , SENDTO STORAGE [ , attribute-spec ]... Wild-card characters are not supported. MON $ZSMS is the SMF master process. SENDTO STORAGE directs the command to the storage subsystem. This attribute is required unless you specified SENDTO STORAGE in a previous ASSUME command.
Storage Subsystem Commands ADD POOL Command HIGHPIN { ON | OFF } specifies whether the IOP can run at a high PIN (ON, the default) or only at a low PIN (OFF). MODE { NOISY | QUIET } specifies whether to generate additional EMS messages for debugging. NOISY Generate additional EMS messages for debugging. QUIET Generate only essential EMS messages (default). PRIMARYCPU number is the processor in which the primary IOP starts. The default is PRIMARYCPU 0. PROGRAM [[$vol.]subvol.
ADD POOL Command Storage Subsystem Commands POOL $pool is the storage pool process. SENDTO STORAGE directs the command to the storage subsystem. This attribute is required unless you specified SENDTO STORAGE in a previous ASSUME command. LIKE object identifies an existing object whose attribute values are copied to the object affected by this command. The object name must currently exist in the system configuration, and the object type must match that of the object affected by this command.
Storage Subsystem Commands ADD POOL Command BACKUPCPU number is the processor in which the backup IOP starts. The default is BACKUPCPU 1. CATALOGLOCATION $vol[.subvol ] is the location of the catalog for the storage pool process. $vol must be in the STARTED state and enabled in TMF. If CATALOGLOCATION is not specified, $vol is set to $SYSTEM. If you omit subvol, the storage pool process selects an empty subvolume and gives it the name ZSMSPnn.
ADD POOL Command Storage Subsystem Commands EXTENTTHRESHOLD number is the number of extents that, with the EXTENTINTERVAL attribute, is used by the disk process to determine when to issue an extents-left EMS message for physical volumes in the storage pool. For example, if EXTENTTHRESHOLD is 6, the disk process issues an EMS message when only six extents remain to be allocated to a file.
Storage Subsystem Commands ADD POOL Command If you specify PROGRAM as $SYSTEM.SYSTEM, the operating system first searches for the file on $SYSTEM.SYSTEM and on the current SYSnn subvolume. STARTSTATE { STARTED | STOPPED } specifies whether the IOP is available to other processes (STARTED) or unavailable (STOPPED) when the system is loaded or reloaded. The default is STARTED.
Storage Subsystem Commands ADD PROFILE Command ADD PROFILE Command The ADD PROFILE command adds a profile to the system configuration database for use in autoconfiguration of internal disks. The syntax is: ADD [ / OUT file-spec / ] PROFILE $ZZSTO.INTERNAL-DISK-groupnum , SENDTO STORAGE [ , LIKE object ] [ , attribute-spec ]... Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. PROFILE $ZZSTO.INTERNAL-DISK-groupnum is a custom profile for enclosure groupnum.
Storage Subsystem Commands [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , , , , , , , , , , , ADD SCSI Command FSTCACHING { ON | OFF | ENABLED } ] FULLCHECKPOINTS { DISABLED | ENABLED | FORCED } ] HALTONERROR number ] HIGHPIN { ON | OFF } ] LKIDLONGPOOLLEN number ] LKTABLESPACELEN number ] MAXLOCKSPEROCB number ] MAXLOCKSPERTCB number ] MIRRORING { OFF | ON } ] NAMEMASK { STANDARD | name } ] NONAUDITEDINSERT { ON | OFF } ] NUMDISKPROCESSES number ] OSSCACHING { ON | OFF } ]
Storage Subsystem Commands ADD SCSI Command SENDTO STORAGE directs the command to the storage subsystem. This attribute is required unless you specified SENDTO STORAGE in a previous ASSUME command. LIKE object identifies an existing object whose attribute values are copied to the object affected by this command. The object name must currently exist in the system configuration, and the object type must match that of the object affected by this command.
Storage Subsystem Commands ADD SCSI Command BACKUPLOCATION ( group,module,slot ) is the location of the adapter that controls the backup path to the device. This attribute has no default value. If this attribute is not specified, the device is not accessible through its backup path. BACKUPPORTNAME number is the Fibre Channel port name used by the backup path to the Open SCSI device. The number should be entered as a 16 character hexadecimal number, without a leading %H.
Storage Subsystem Commands ADD SCSI Command PRIMARYLOCATION ( group,module,slot ) is the location of the adapter that controls the primary path to the Open SCSI device. This attribute is required. PRIMARYPORTNAME number is the fiber channel port name used by the primary path to the Open SCSI device. The number should be entered as a 16 character hexadecimal number, without a leading %H. PRIMARYSAC { number | name } is the SAC that controls the primary path to the device.
ADD TAPE Command Storage Subsystem Commands TRACEBUFLEN number is the size (in kilobytes) of the memory area used for internal tracing by the Open SCSI IOP. number is in the range 32 through 65. The default is 33. TRACELEVEL number is the level of tracing used by the Open SCSI IOP. number is in the range 0 through 65,535. The default is 65,535. ADD SCSI Consideration Before using the ADD SCSI command, verify the SCSI ID of the device is the same as the configured SCSIID value.
Storage Subsystem Commands ADD TAPE Command configuration, and the object type must match that of the object affected by this command. If you specify LIKE, any attribute values that you explicitly specify override the attribute values of the LIKE object. The location, SAC, and device ID values are not copied from the LIKE object. To assign values to these attributes, you must explicitly specify them. attribute-spec is one or more ADD TAPE Attributes.
Storage Subsystem Commands ADD TAPE Command DEVICEID number is the device ID of the tape drive. This value must match either the SCSI ID of the tape drive (if SCSI-connected) or the device ID of the tape drive (if Fibre Channel connected). If the tape drive is connected to a PMF CRU, an IOMF CRU, or an SNDA, number is in the range 0 through 5. The default is 5. If the tape drive is connected to an F-SAC of an SNDA, number is 4 or 5.
Storage Subsystem Commands ADD TAPE Command RECSIZE number is the configured record size for the device (in number of words). This value is used by some utility programs when making requests to the IOP. number is in the range 1 through 57344. The default is 4096. SAC { number | name } is the SAC that controls the primary path to the device. number is the SAC subdevice number on the adapter. name is the full name of the SAC. For example: SNDA.SAC-1.GRP-1.MOD-1.SLOT-53 .
ALLOWOPENS Command Storage Subsystem Commands ALLOWOPENS Command The ALLOWOPENS command permits an object to accept opens again; reverses the effect of the STOPOPENS command. ALLOWOPENS is a sensitive command. ALLOWOPENS DISK Command The ALLOWOPENS command permits file opens on a specified magnetic disk volume. The syntax is: ALLOWOPENS [ / OUT file-spec / ] DISK $disk [ , POOL $pool ] [ , SEL state ] [ , SUB { ALL | MAGNETIC | VIRTUAL } ] [ , SUPERONLY ] Wild-card characters are supported.
Storage Subsystem Commands ALLOWOPENS DISK Command ALLOWOPENS DISK Examples See the procedure for Allowing File Opens on a Magnetic Disk on page 7-23.
ALTER Command Storage Subsystem Commands ALTER Command The ALTER command changes the configuration attributes of an object. Supported objects are: DISK page 14-48 SCSI page 14-59 MON page 14-53 SUBSYS page 14-63 POOL page 14-54 TAPE page 14-65 PROFILE page 14-58 ALTER is a sensitive command. ALTER DISK Command The ALTER DISK command changes attribute values for an existing magnetic or virtual disk on your system.
Storage Subsystem Commands • • • • ALTER DISK Command Location attributes: ° BACKUPLOCATION ° MBACKUPLOCATION ° MIRRORLOCATION ° PRIMARYLOCATION SAC attributes: ° BACKUPSAC ° MBACKUPSAC ° MIRRORSAC ° PRIMARYSAC ° MIRRORLOCATION PORTNAME attributes: ° BACKUPPPORTNAME ° MBACKUPPORTNAME ° MIRRORPORTNAME ° PRIMARYPORTNAME LUN attributes: ° MIRRORLUN ° PRIMARYLUN These virtual disk attributes are not copied from the LIKE object.
Storage Subsystem Commands [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ALTER DISK Command FORCED ] FSTCACHING { ON | OFF | ENABLED} ] FULLCHECKPOINTS { ENABLED | DISABLED | FORCED } ] HALTONERROR number ] HIGHPIN { ON | OFF } ] IGNOREINCONSISTENCY ] LABEL $vol ] LKIDLONGPOOLLEN number ] LKTABLESPACELEN number ] MAXLOCKSPEROCB number ] MAXLOCKSPERTCB number ] MBACKUPDEVICEID { n
Storage Subsystem Commands ALTER DISK Command Virtual Disk Attributes for the ALTER COMMAND These virtual disk attributes are valid for the ALTER DISK command. For a description of these attributes, see Disk Attribute Descriptions on page 14-12 [ [ [ [ [ [ [ [ , , , , , , , , ANTCAPACITY number ] BACKUPCPU number ] CACHESIZE number ] HIGHPIN { ON | OFF } ] MODE { NOISY | QUIET } ] PRIMARYCPU number ] PROGRAM [[$vol.]subvol.
Storage Subsystem Commands ALTER DISK Command ALTER DISK Examples for Virtual Disks See the procedure for Troubleshooting Problems With Adding a Virtual Disk on page 10-9.
Storage Subsystem Commands ALTER MON Command ALTER MON Command The ALTER MON command changes the configured attribute values for the SMF master process. The syntax is: ALTER [ / OUT file-spec / ] MON $ZSMS [ , attribute-spec ]... Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. MON $ZSMS is the SMF master process. attribute-spec is one or more ALTER MON Attributes.
Storage Subsystem Commands ALTER POOL Command PROGRAM [[$vol.]subvol.]fileid is the object file name of the IOP. If not specified, PROGRAM is: $SYSTEM.SYSTEM.OMP If you specify the program file name location as $SYSTEM.SYSTEM, the operating system first searches for the file there and on the current SYSnn subvolume. ALTER MON Examples See the procedure for Altering the Values of the SMF Master Process Attributes on page 4-5.
ALTER POOL Command Storage Subsystem Commands ALTER POOL Attributes [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , AUDITED { ALLOWED | DISALLOWED | REQUIRED } ] BACKUPCPU number ] DISKINTERVAL number ] DISKTHRESHOLD number ] EXTENTINTERVAL number ] EXTENTTHRESHOLD number ] HIGHPIN { ON | OFF } ] MAGNETIC { ALLOWED | DISALLOWED | REQUIRED } ] MIRRORED { ALLOWED | DISALLOWED | REQUIRED } ] MODE { NOISY | QUIET } ] PRIMARYCPU number ] PROGRAM [[$vol.]subvol.
ALTER POOL Command Storage Subsystem Commands EMS message when the physical volume becomes 75, 80, 85, 90, and 95 percent full. number is either -1 (the default, no disk-full EMS messages are issued) or in the range 1 through 100 percent. EXTENTINTERVAL number is the number of extents that, with the EXTENTTHRESHOLD attribute, is used by the disk process to determine when to issue an extents-left EMS message for physical volumes in the storage pool.
Storage Subsystem Commands ALTER POOL Command MODE { NOISY | QUIET } specifies whether to generate additional EMS messages for debugging. NOISY Generate additional EMS messages for debugging. QUIET Generate only essential EMS messages (default). PRIMARYCPU number is the processor in which the primary IOP starts. The process must be in the STOPPED state or not running for you to alter this attribute. PROGRAM [[$vol.]subvol.]fileid is the object file name of the IOP.
Storage Subsystem Commands ALTER PROFILE Command ALTER PROFILE Command The ALTER PROFILE command changes a disk configuration profile. The syntax is: ALTER [ / OUT file-spec / ] PROFILE $ZZSTO.INTERNAL-DISK[-groupnum ] [ , attribute-spec ]... Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. PROFILE $ZZSTO.INTERNAL-DISK[-groupnum ] is either the standard default profile, $ZZSTO.#INTERNAL-DISK, or a user-created custom profile for enclosure groupnum.
Storage Subsystem Commands [ [ [ [ [ , , , , , ALTER SCSI Command REVIVEPRIORITY number ] REVIVERATE number ] SERIALWRITES { DISABLED | ENABLED } ] SQLMXBUFFER number ] STARTSTATE { STARTED | STOPPED } ] ALTER PROFILE Examples See the procedure for Altering a Profile on page 6-10. • To modify the standard default profile for all internal disks in the system: -> ALTER PROFILE $ZZSTO.#INTERNAL-DISK, NAMEMASK DATA • To change a profile for all disks inserted into group 03: -> ALTER PROFILE $ZZSTO.
Storage Subsystem Commands ALTER SCSI Command ALTER SCSI Attributes [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , , , , , , BACKUPCPU number ] BACKUPLOCATION ( group, module, slot ) ] BACKUPPORTNAME number ] BACKUPSAC number | name ] HIGHPIN { ON | OFF } ] LUN number ] MAXOPENS number ] NUMIO number ] PRIMARYCPU number ] PRIMARYLOCATION ( group,module,slot ) ] PRIMARYPORTNAME number ] PRIMARYSAC number | name ] PROGRAM [[$vol.]subvol.
Storage Subsystem Commands ALTER SCSI Command HIGHPIN { ON | OFF } specifies whether the IOP can run at a high PIN (ON, the default) or only at a low PIN (OFF). LUN number is the logical unit number (LUN) of a device connected to the Open SCSI device. For devices connected to a SCSI controller number is in the range 0 through 7. For Fibre Channel devices number is in the range 0 through 32767. MAXOPENS number is the maximum concurrent opens allowed for the device. number is in the range 1 through 64.
Storage Subsystem Commands ALTER SCSI Command PROGRAM [[$vol.]subvol.]fileid is the object file name of the IOP. If not specified, PROGRAM is: $SYSTEM.SYSTEM.TDSCSI If you specify the program file name location as $SYSTEM.SYSTEM, the operating system first searches for the file there and on the current SYSnn subvolume. RECSIZE number is the configured record size for the device (in number of words). This value is used by some utility programs when making requests to the IOP.
Storage Subsystem Commands ALTER SUBSYS Command ALTER SUBSYS Command The ALTER SUBSYS command changes attributes of the storage subsystem manager. The syntax is: ALTER [ / OUT file-spec / ] SUBSYS $ZZSTO [ , attribute-spec ]... Wild card characters are not supported. OUT file-spec directs all SCF output to the specified file. SUBSYS $ZZSTO is the storage subsystem manager. attribute-spec is one or more ALTER SUBSYS Attributes.
Storage Subsystem Commands ALTER SUBSYS Command For information about using this attribute, see Configuring Internal Mirrored Magnetic Disks to Revive Automatically on page 6-13. AUTOSTART { ON | OFF } (internal and M8xxx disks only) specifies whether to automatically start the disk process when the disk is inserted. ON Enable automatic starting (default). OFF Disable automatic starting. DISK AUTOSTART ON is ignored if SUBSYS AUTOSTART is OFF.
Storage Subsystem Commands ALTER TAPE Command ALTER SUBSYS Examples • To set BULKIO on: -> ALTER $ZZSTO, BULKIO ON • To turn on labeled-tape processing: -> ALTER $ZZSTO, LABELTAPE ON • To make internal disks plug and play: -> ALTER $ZZSTO, AUTOCONFIGURE ON, AUTOSTART ON, & -> AUTOREVIVE ON See Automating Disk Configuration on page 6-6. ALTER TAPE Command The ALTER TAPE command changes the configured attribute values for a tape device attached to your system.
Storage Subsystem Commands ALTER TAPE Command ALTER TAPE Attributes [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , BACKUPCPU number ] COMPRESSION { ON | OFF } ] DENSITY { 1600 | 6250 } ] DEVICEID number ] HIGHPIN { ON | OFF } ] LOCATION (group,module,slot) ] LUN number ] MAXOPENS number ] PORTNAME number ] PRIMARYCPU number ] PROGRAM [[$vol.]subvol.
Storage Subsystem Commands ALTER TAPE Command HIGHPIN { ON | OFF } specifies whether the IOP can run at a high PIN (ON, the default) or only at a low PIN (OFF). LOCATION ( group, module, slot ) is the location of the adapter where the tape drive is connected. LUN number is the logical unit number (LUN) used by the path of the tape volume in the range 0 through 31. MAXOPENS number is the maximum number of concurrent opens allowed for the device. number is in the range 1 through 64. The default is 4.
Storage Subsystem Commands ALTER TAPE Command STARTSTATE { STARTED | STOPPED } specifies whether the IOP is available to other processes (STARTED) or unavailable (STOPPED) when the system is loaded or reloaded. The default is STARTED.
CONTROL Command Storage Subsystem Commands ALTER TAPE Example See the procedure for Altering Tape Drive Attribute Values on page 13-11. To alter the data compression attribute: -> ALTER $TAPE0, COMPRESSION ON CONTROL Command CONTROL a sensitive command.
CONTROL DISK Command Storage Subsystem Commands SEL state specifies that the command affects only devices in the specified state. SUB [ { ALL | MAGNETIC } ] specifies that the command affects only disks of the specified type. attribute-spec is one or more CONTROL DISK Attributes. CONTROL DISK Attributes [ [ [ [ [ [ [ [ , , , , , , , , CHECKSUM [ % | %H ] lsa ] POWER { ON | OFF } ] POWEROFF ] POWERON ] REBUILDDFS ] REFRESH ] REPLACEBOOT [[$vol.]subvol.
Storage Subsystem Commands CONTROL DISK Command POWEROFF powers the disk drive off. All paths to the disk drive (-P and -B or --M and -MB) must be in a STOPPED state before you can use this command option. When you use this attribute, you can specify only the -P path or the-M path. Note. You cannot turn the power off for M8xxx disks with this attribute. POWERON powers the disk drive on.
CONTROL DISK Command Storage Subsystem Commands When you initiate a REPLACEBOOT operation, SCF puts one half of the mirrored volume HARDDOWN before replacing the bootstrap file. The other half must be STARTED. If the specified bootstrap file and the processor type are incompatible, an error message is generated and the operation is not performed.
CONTROL SAC Command Storage Subsystem Commands • To spare the sector that has logical sector address %H0000795C on the mirror half of a volume: -> CONTROL $DATA01-M, SPARE %H795C CONTROL SAC Command For M8xxx FCDMs connected to an FCSA, the CONTROL SAC command is used to issue commands to disks connected to the SAC. The syntax is: CONTROL [ /OUT file-spec/ ] SAC $ZZSTO.#sac-name, DEVICEID (shelf, bay) [ , attribute-spec ] ... OUT file-spec directs all SCF output to the specified file.
Storage Subsystem Commands CONTROL SAC Command BYPASS { OFF | ON } causes the specified disk to be bypassed (ON) or not bypassed (OFF) on the loop connected to the SAC. Note. Disk paths affected by BYPASS ON must already be in the STOPPED state, with a substate of either DOWN or HARDDOWN. BYPASSBOTH { OFF | ON } causes the specified disk to be bypassed (ON) or not bypassed (OFF) on both loops. Note.
DELETE Command Storage Subsystem Commands DELETE Command The DELETE command removes objects from the system configuration database. Supported objects are: ADAPTER page 14-75 POOL page 14-77 DISK page 14-76 PROFILE page 14-78 MON page 14-77 SCSI page 14-79 DELETE is a sensitive command. DELETE ADAPTER Command The DELETE ADAPTER command removes an adapter from the system configuration database. The syntax is: DELETE [ / OUT file-spec / ] ADAPTER $ZZSTO.#type.GRP-g.MOD-m.
DELETE DISK Command Storage Subsystem Commands DELETE DISK Command The DELETE DISK command removes a magnetic or virtual disk from the system configuration database. The syntax is: DELETE [ / OUT file-spec / ] DISK $disk[-B |-M |-MB ] [ , IGNOREINCONSISTENCY ] [ , POOL $pool ] [ , SEL state ] [ , SENDTO STORAGE ] [ , SUB { ALL | MAGNETIC | VIRTUAL } Wild-card characters are not supported. OUT file-spec directs all SCF output to the specified file.
Storage Subsystem Commands DELETE MON Command DELETE DISK Example See the procedure for Deleting a Magnetic Disk on page 6-34 or the procedure for Deleting a Virtual Disk on page 10-11. To remove a volume from the system configuration database: -> DELETE $DATA01 DELETE MON Command The DELETE MON command removes the SMF master process from the system configuration database. The syntax is: DELETE [ / OUT file-spec / ] MON $ZSMS [ , SEL state ] Wild-card characters are supported.
Storage Subsystem Commands DELETE PROFILE Command POOL $pool is the storage pool process. IGNOREINCONSISTENCY specifies that a command can create an inconsistency between the system configuration database and the SMF catalogs maintained by the SMF manager process, storage pools, and virtual disks. Use this attribute only if you understand SMF architecture and know how to restore consistency between the system configuration database and the SMF catalogs.
Storage Subsystem Commands DELETE SCSI Command To delete a profile for all disks inserted into group 01: -> DELETE PROFILE $ZZSTO.#INTERNAL-DISK-1 DELETE SCSI Command The DELETE SCSI command removes an Open SCSI device from the system configuration database. The syntax is: DELETE [ / OUT file-spec / ] SCSI $SCSI-device [ , SEL state ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. SCSI $SCSI-device is the name of the Open SCSI device.
INFO Command Storage Subsystem Commands OUT file-spec directs all SCF output to the specified file. TAPE $tape is the name of the tape device. DELETE TAPE Example See the procedure for Deleting a Tape Drive on page 13-12. To delete a tape drive from the system configuration database: -> DELETE $TAPE0 INFO Command The INFO command displays system configuration information, such as the current attribute values for a specified object.
Storage Subsystem Commands INFO DISK Command INFO ADAPTER Examples • To display information about the PMF CRU adapter in group 01, slot 50: -> INFO $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50 See the display and explanation under Example of an INFO PMF ADAPTER Report on page 11-3. • To display detailed information about the PMF CRU adapter in group 01, slot 50: -> INFO $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50, DETAIL See the display and explanation under Example of a Detailed INFO PMF ADAPTER Report on page 11-3.
Storage Subsystem Commands INFO DISK Command LOG (magnetic disks only) displays information about spared sectors. OBEYFORM displays information about the object in the format used in an ADD command. POOL $pool specifies that the command is performed only on disks associated with the specified storage pool. SECTOR [ % | %H ] lsa (magnetic disks only) displays information about the disk sector at logical sector address lsa. lsa can be expressed as an octal (%), hexadecimal (%H), or decimal number.
INFO MON Command Storage Subsystem Commands See the display and explanation under Example of an INFO DISK Detailed Report on page 10-5. • To display information about disk cache configuration for $SYSTEM: -> INFO $SYSTEM, CACHE See the display and explanation under Displaying Disk Cache Configuration Information on page 5-14. • To display information about the label for $SYSTEM: -> INFO $SYSTEM, LABEL See the display and explanation under Displaying Disk Label Information on page 5-9.
INFO POOL Command Storage Subsystem Commands INFO MON Examples • To display information about the SMF master process: -> INFO $ZSMS See the display and explanation under Example of an INFO MON Report on page 4-2. • To display detailed information about the SMF master process: -> INFO $ZSMS , DETAIL See the display and explanation under Example of a Detailed INFO MON Report on page 4-2. INFO POOL Command The INFO POOL command displays configuration information about a storage pool.
Storage Subsystem Commands • INFO PROFILE Command To display detailed information about a storage pool process: -> INFO $POOL1 , DETAIL See the display and explanation under Example of a Detailed INFO POOL Report on page 9-3. INFO PROFILE Command The INFO PROFILE command displays configuration information about the specified profile. The syntax is: INFO [ / OUT file-spec / ] PROFILE $ZZSTO.#INTERNAL-DISK[-groupnum ] [ , OBEYFORM ] Wild-card characters are supported. PROFILE $ZZSTO.
Storage Subsystem Commands INFO SCSI Command INFO SCSI Command The INFO SCSI command displays configuration information about an Open SCSI device. The command syntax is: INFO [ / OUT file-spec / ] SCSI $SCSI-device [ , { DETAIL | OBEYFORM } ] [ , SEL state ] Wild-card characters are supported. SCSI $SCSI-device is the name of the Open SCSI device. DETAIL displays detailed configuration information. OBEYFORM displays information about the object in the format used in an ADD command.
Storage Subsystem Commands INFO TAPE Command SUBSYS $ZZSTO is the storage subsystem manager. INFO SUBSYS Consideration The information showed by INFO SUBSYS and STATUS SUBSYS should always be the same. If the information shown in these displays differs, contact your service provider. INFO SUBSYS Example -> INFO SUBSYS $ZZSTO See the display and explanation under Section 3, Using the Storage Subsystem Manager.
INITIALIZE Command Storage Subsystem Commands • To display detailed information about a tape drive: -> INFO $TAPE0, DETAIL See the display and explanation under Examples of INFO TAPE Detailed Reports on page 13-4. • To display information about all tape drives that are not stopped: -> INFO TAPE $*, SEL NOT STOPPED INITIALIZE Command The INITIALIZE command prepares a magnetic disk for use on the system.
NAMES Command Storage Subsystem Commands INITIALIZE DISK Examples See Swapping Processors for a Disk on page 7-24. • To initialize a disk and relabel it using the same volume name: -> INITIALIZE DISK $DATA12 • To initialize a disk and give it another name: -> INITIALIZE DISK $DATA12, LABEL $SPARE00 NAMES Command The NAMES command displays object names for a specified object type and any subordinate objects.
NAMES Command Storage Subsystem Commands For DISK objects, these subtypes are allowed (the default is ALL): ALL MAGNETIC VIRTUAL NAMES Examples • To display the object names of all objects managed by the storage subsystem manager process: -> NAMES $ZZSTO STORAGE Names SUBSYS \SWEET.$ZZSTO SUBSYS $ZZSTO ADAPTER $ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-50 $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50 $ZZSTO.#PMF.GRP-2.MOD-1.SLOT-50 $ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-51 $ZZSTO.#SNDA.GRP-11.MOD-1.
NAMES Command Storage Subsystem Commands • To display the object names of all adapters: -> NAMES $ZZSTO, SUB ADAPTER STORAGE Names SUBSYS \COMM.$ZZSTO ADAPTER $ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-50 $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50 $ZZSTO.#PMF.GRP-2.MOD-1.SLOT-50 $ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-51 $ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-53 • $ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-55 $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-55 $ZZSTO.#PMF.GRP-2.MOD-1.SLOT-55 $ZZSTO.#SNDA.GRP-11.MOD-1.
PRIMARY Command Storage Subsystem Commands PRIMARY Command The PRIMARY command swaps the primary and backup processors for a device or process. The current primary process becomes the backup process, and the current backup process becomes the primary process, but the PRIMARYCPU and BACKUPCPU values stay the same. Supported objects are: DISK page 14-92 SCSI page 14-95 MON page 14-93 SUBSYS page 14-95 POOL page 14-94 TAPE page 14-96 PRIMARY is a sensitive command.
PRIMARY MON Command Storage Subsystem Commands FORCED (magnetic disks only) for G06.10 and earlier RVUs, specifies that all disk processes using the same controller as the specified disk must switch to the specified primary processor. Beginning with G06.11, the FORCED attribute is ignored. Because SACs can be owned by more than one processor, the PRIMARY command affects only the IOP for the disk whose primary processor is being swapped. Other disk processes are unaffected.
Storage Subsystem Commands PRIMARY POOL Command MON $ZSMS is the SMF master process. cpunumber is the processor number of the processor that is to become the primary processor. This decimal integer must identify one of the two processors configured as primary and backup processors for the device. If you do not specify a processor number, the storage subsystem manager determines which processors are currently being used for the primary process and backup process and swaps those processors.
Storage Subsystem Commands PRIMARY SCSI Command PRIMARY POOL Examples See the procedure for Swapping Processors for a Pool Process on page 9-13. • To run the primary pool process in processor 3: -> PRIMARY $POOL00, 3 • To swap the primary and backup processors controlling a pool process: -> PRIMARY $POOL01 PRIMARY SCSI Command The PRIMARY SCSI command switches the primary and backup processors for the specified Open SCSI device.
PRIMARY SUBSYS Command Storage Subsystem Commands PRIMARY SUBSYS Command The PRIMARY SUBSYS command moves all storage subsystem IOPs into or away from a processor, as part of device or adapter replacement. The syntax is: PRIMARY [ / OUT file-spec / ] SUBSYS $ZZSTO , cpunumber , { AWAY | DEFAULT } OUT file-spec directs all SCF output to the specified file. SUBSYS $ZZSTO is the storage subsystem manager.
Storage Subsystem Commands PRIMARY TAPE Command the current backup process becomes the primary process, but the PRIMARYCPU and BACKUPCPU values stay the same. The syntax is: PRIMARY [ / OUT file-spec / ] TAPE $tape [ , cpunumber ] Wild-card characters are supported. TAPE $tape is the name of the tape device. cpunumber is the processor number of the processor that is to become the primary processor.
PROBE Command Storage Subsystem Commands PROBE Command The PROBE SAC command tests the Fibre Channel connection to a SAC on an FCSA. Note. The PROBE SAC command is available on H06.04 and subsequent H-series RVUs. PROBE is a sensitive command. PROBE SAC Command The PROBE SAC command sends and receives a data packet to test the Fibre Channel connection to a SAC on an FCSA. The connection can be either an arbitrated loop or a link to a Fibre Channel switch.
Storage Subsystem Commands PROBE SAC Command DATA pattern specifies a data pattern (up to 64 bytes) that can be used for diagnostic purposes. The data pattern must be entered as a hexadecimal number without a leading %H. PORTNAME wwn specifies the worldwide name of a port in the Fibre Channel link connected to the SAC. wwn must be entered as a 16-character hexadecimal number without a leading %H. Specify a PORTNAME to test the connection to a Fibre Channel switch.
Storage Subsystem Commands RENAME Command RENAME Command The RENAME command changes the name of a disk. RENAME is a sensitive command. RENAME DISK Command The RENAME command changes the default volume name and alternate volume name of a magnetic disk without destroying files on the disk. The syntax is: RENAME [ / OUT file-spec / ] DISK $disk , $new-disk Wild-card characters are not supported. OUT file-spec directs all SCF output to the specified file. DISK $disk is the name of the disk.
Storage Subsystem Commands REPLACE Command REPLACE Command The REPLACE command is used to change the object file of an executing object. REPLACE ADAPTER Command The REPLACE ADAPTER command downloads new firmware to adapters and SACs. The syntax is: REPLACE [ /OUT file-spec/ ] ADAPTER $ZZSTO.#adapter-name [ , attribute-spec ] ... OUT file-spec directs all SCF output to the specified file. ADAPTER $ZZSTO.# adapter-name is a ServerNet adapter of type PMF, IOMF, SNDA or FCSA in the format type.GRP-group.
Storage Subsystem Commands REPLACE SAC Command FIRMWARE [[$volume.]subvol.]filename specifies the name of the new operational firmware file. The file must exist and must have a file code of 510. The default volume and subvolume are equal to the current SYSnn. The adapter name must be given as $ZZSTO.#*. FLASHBOOT [[$volume.]subvol.]filename specifies the name of the new flash boot file. The file must exist and must have a file code of 510. The default volume and subvolume are equal to the current SYSnn.
Storage Subsystem Commands REPLACE SAC Command FIRMWARE [[$volume.]subvol.]filename specifies the name of the new EMU firmware file. The file must exist, and it must have file code 0. The default volume and subvolume is the current SYSnn.
RESET Command Storage Subsystem Commands RESET Command The RESET command puts an object in a state ready for starting. RESET is a sensitive command. RESET DISK Command The RESET DISK command puts a disk into the STOPPED state, substate DOWN, ready for restarting. It also can pause a disk revive operation. The syntax is: RESET [ / OUT file-spec / ] [ , FORCED ] DISK $disk[-P |-B |-M |-MB ] [ , POOL $pool ] [ , SEL state ] [ , SUB { ALL | MAGNETIC | VIRTUAL } ] Wild-card characters are supported.
RESET MON Command Storage Subsystem Commands RESET DISK Examples See these procedures: Resetting a Magnetic Disk Resetting a Virtual Disk • 7-11 10-13 To reset the mirror half of a disk: -> RESET $DATA00-M • To reset a virtual disk: -> RESET $VDISK1 RESET MON Command The RESET MON command puts the SMF master process into the STOPPED state, substate DOWN, ready for restarting. The syntax is: RESET [ / OUT file-spec / ] MON $ZSMS [ , FORCED ] [ , SEL state ] Wild-card characters are supported.
RESET POOL Command Storage Subsystem Commands RESET POOL Command The RESET POOL command puts a storage pool process into the STOPPED state, substate DOWN, ready for restarting. The syntax is: RESET [ / OUT file-spec / ] POOL $pool [ , FORCED ] [ , SEL state ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. POOL $pool is the storage pool process. FORCED terminates the IOP. SEL state specifies that the command affects only devices in the specified state.
RESET TAPE Command Storage Subsystem Commands OUT file-spec directs all SCF output to the specified file. SCSI $SCSI-device[-P |-B ] is the name of the Open SCSI IOP and, optionally, the path (primary or backup). FORCED terminates the IOP. If you use this attribute, you cannot specify a -P or B path. SEL state specifies that the command affects only devices in the specified state. RESET SCSI Consideration The RESET command is ignored if the process is started.
Storage Subsystem Commands RESET TAPE Command SEL state specifies that the command affects only devices in the specified state. RESET TAPE Consideration The RESET command is ignored if the process is started. RESET TAPE Example See the procedure for Resetting a Tape Drive on page 13-14.
START Command Storage Subsystem Commands START Command The START command initiates the operation of an object (make a stopped device accessible to user processes). Successful completion of the START command leaves the object in the STARTED state. Supported objects are: DISK page 14-109 SCSI page 14-112 MON page 14-110 TAPE page 14-112 POOL page 14-111 START is a sensitive command. START DISK Command The START DISK command makes a stopped disk accessible to user processes.
START MON Command Storage Subsystem Commands SPECIAL puts the disk into the SERVICING state, substate SPECIAL. Use this attribute to ensure that only privileged processes can access the disk. You must designate the entire primary or mirror path. SUB { ALL | MAGNETIC | VIRTUAL } specifies that the command affects only disks of the specified type. The default is ALL.
START POOL Command Storage Subsystem Commands SEL state specifies that the command affects only devices in the specified state. SPECIAL specifies that the process be started in the SERVICING state, substate SPECIAL. START MON Example See the procedure for Starting the SMF Master Process on page 4-7. To start the SMF master process $ZSMS in the SERVICING state: -> START $ZSMS, SPECIAL START POOL Command The START POOL command makes a storage pool available to the applications on the system.
START SCSI Command Storage Subsystem Commands • To start a storage pool process in the SPECIAL substate: -> START $POOL00, SPECIAL START SCSI Command The START SCSI command makes a stopped Open SCSI device or a path to an Open SCSI device accessible to user processes. The syntax is: START [ / OUT file-spec / ] SCSI $SCSI-device[-P |-B ] [ , DEBUG $terminal ] [ , SEL state ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file.
Storage Subsystem Commands START TAPE Command OUT file-spec directs all SCF output to the specified file. TAPE $tape is the name of the tape device. DEBUG $terminal specifies that the process should start in debug mode on $terminal. SEL state specifies that the command affects only devices in the specified state. START TAPE Examples See the procedure for Starting a Tape Drive on page 13-14.
Storage Subsystem Commands STATS Command STATS Command The STATS command displays cache statistics about an object and optionally resets them. STATS DISK Command The STATS command displays cache statistics about magnetic disks. The syntax is: STATS [ / OUT file-spec / ] DISK $disk [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , ALL ] CACHE ] CONTROLBLOCKS ] IO ] LOCKS ] POOL $pool ] RESET [ , FORCED ] ] SEL state ] SQLMX ] SUB { ALL | MAGNETIC | VIRTUAL } ] Wild-card characters are supported.
Storage Subsystem Commands STATS DISK Command LOCKS specifies that locks statistics be shown. POOL $pool specifies that the command is performed only on disks associated with the specified storage pool. RESET [ , FORCED ] restores statistics counters to their initial values. Only super-group users (255,nnn) can use this attribute. . FORCED specifies that the command be executed without any interaction with the user. SEL state specifies that the command affects only devices in the specified state.
STATS SAC Command Storage Subsystem Commands STATS SAC Command The STATS SAC command displays statistical information about the connections to a SAC on an FCSA. The command can display information about a port in the Fibre Channel link or the SAC itself Note. The STATS SAC command is available on H06.04 and subsequent H-series RVUs. The syntax is: STATS [ / OUT file-spec / ] SAC $ZZSTO.#sac-name [ , PORTNAME wwn ] [ , RESET [ , FORCED ] ] Wild-card characters are supported.
Storage Subsystem Commands STATS SAC Command STATS SAC Examples To obtain statistics for SAC 1 on the FCSA in slot 3, module 3 of group 111: -> STATS SAC $ZZSTO.#FCSA.SAC-1.GRP-111.MOD-3.SLOT-3 STORAGE - Stats SAC \IO.$ZZSTO.#FCSA.SAC-1.GRP-111.MOD-3.SLOT-3 Command timeouts........ 0 Device Changes......... 9 Fabric Device Changes... 0 FC Length Errors....... 0 ISP Database Changes.... 1 ISP Downloads.......... 1 ISP Fabric LID Available 126 ISP Firmware Errors.... 0 ISP Hardware Errors.....
STATUS Command Storage Subsystem Commands STATUS Command The STATUS command displays current status information about an object. Supported objects are: ADAPTER page 14-118 SAC page 14-123 DISK page 14-119 SCSI page 14-127 MON page 14-121 SUBSYS page 14-127 POOL page 14-122 TAPE page 14-128 STATUS ADAPTER Command The STATUS ADAPTER command displays current information about a ServerNet adapter. The syntax is: STATUS [ / OUT file-spec / ] ADAPTER $ZZSTO.#type.GRP-g.MOD-m.
STATUS DISK Command Storage Subsystem Commands VPROCS displays only the full VPROC strings for firmware. See Example of a STATUS FCSA ADAPTER, VPROCS Report on page 11-17. STATUS ADAPTER Examples • To display the status of the PMF CRU adapter in group 01, slot 50: -> STATUS ADAPTER $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50 See the display and explanation under Example of a STATUS PMF ADAPTER Report on page 11-8. • To display detailed status of the PMF CRU adapter in group 01, slot 50: -> STATUS ADAPTER $ZZSTO.
Storage Subsystem Commands STATUS DISK Command CONFIG causes a display of the values that the running disk process is currently using as operational parameters defined by certain disk configuration attributes. These values can differ from the values entered into the system configuration database. In the display, values that differ in this way are marked with an asterisk (*).
STATUS MON Command Storage Subsystem Commands • To display the status of all paths to all internal disks in the group 02 topology branch: -> STATUS $D02*-* The display is shown on page 8-17. • To display the consistency information about the disk volume $WENDY: -> STATUS $WENDY, CONSISTENCY See the display and explanation under Example 4: Displaying STATUS DISK, CONSISTENCY Information on page 5-23.
STATUS POOL Command Storage Subsystem Commands SEL state specifies that the command affects only devices in the specified state. STATUS MON Examples • To display the current status of the SMF master process: -> STATUS $ZSMS See the display and explanation under Example of a STATUS MON Command on page 4-3. • To display detailed status of the SMF master process: -> STATUS $ZSMS, DETAIL See the display and explanation under Example of a Detailed STATUS MON Report on page 4-3.
STATUS SAC Command Storage Subsystem Commands See the display and explanation under Example of a STATUS POOL Report on page 9-5. • To display detailed status of a storage pool process: -> STATUS $POOL00, DETAIL See the display and explanation under Example of a Detailed STATUS POOL Report on page 9-5.
Storage Subsystem Commands STATUS SAC Command EMU , DEVICEID (shelf , 0) displays a small subset of the inventory and status information from the environmental monitoring unit (EMU). shelf specifies the shelf number of the enclosure to which the command applies. The bay number must be 0. EMULIST displays the shelf worldwide names for any EMUs visible through the SAC. LOCATION displays the shelf and bay of the disk with the specified PORTNAME. LUN specifies a Logical Unit Number (LUN) in the range 0-32767.
STATUS SAC Command Storage Subsystem Commands STATUS SAC Command Examples This command shows the worldwide names for the EMUs in the FCDMs connected to SAC 2: -> STATUS SAC $ZZSTO.#FCSA.SAC-2.GRP-111.MOD-2.SLOT-1, EMULIST STORAGE - Emulist Status SAC \OSM2.$ZZSTO.#FCSA.SAC-2.GRP-111.MOD-2.SLOT-1 Shelf WWN 1 500508B3005833C7 2 500508B3006814C5 This command shows the worldwide names for all disks in enclosure 1 connected to SAC 2: -> STATUS SAC $ZZSTO.#FCSA.SAC-2.GRP-111.MOD-2.
STATUS SAC Command Storage Subsystem Commands This command displays details for the ports connected to SAC 1: -> STATUS SAC $ZZSTO.#FCSA.SAC-1.GRP-112.MOD-3.SLOT-3,& -> PORTLIST, DETAIL STORAGE - Detailed Portlist Status SAC \IO.$ZZSTO.#FCSA.SAC-1.GRP-112.MOD3.
STATUS SCSI Command Storage Subsystem Commands STATUS SCSI Command The STATUS SCSI command displays current status information about Open SCSI devices. The syntax is: STATUS [ / OUT file-spec / ] SCSI $SCSI-device[-P |-B ] [ , DETAIL ] [ , SEL state ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. SCSI $SCSI-device [-P |-B ] is the name of the Open SCSI IOP and, optionally, the path (primary or backup). DETAIL displays detailed status information.
STATUS TAPE Command Storage Subsystem Commands Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. SUBSYS $ZZSTO is the storage subsystem manager. DETAIL displays detailed status information. STATUS SUBSYS Consideration The information showed by INFO SUBSYS and STATUS SUBSYS should always be the same. Contact your service provider if the information shown in these displays differs.
Storage Subsystem Commands STATUS TAPE Command STATUS TAPE Examples • To display the status of a tape drive: -> STATUS $TAPE0 See the display and explanation under Example of a STATUS TAPE Report on page 13-5. • To display detailed status of a tape drive: -> STATUS $TAPE0, DETAIL See the display and explanation under Example of a Detailed STATUS TAPE Report on page 13-6.
STOP Command Storage Subsystem Commands STOP Command The STOP command terminates access to a storage device in a orderly manner. When the STOP command finishes, configured devices are left in the STOPPED state, substate DOWN. The devices remain in the system configuration database. Supported objects are: DISK page 14-130 SCSI page 14-133 MON page 14-131 TAPE page 14-133 POOL page 14-132 STOP is a sensitive command. STOP DISK Command The STOP DISK command terminates access to a disk.
STOP MON Command Storage Subsystem Commands SEL state specifies that the command affects only devices in the specified state. SUB { ALL | MAGNETIC | VIRTUAL } specifies that the command affects only disks of the specified type. The default is ALL. STOP DISK Examples See the procedure for Stopping a Magnetic Disk on page 7-9; and the procedure for Stopping a Virtual Disk on page 10-13.
STOP POOL Command Storage Subsystem Commands SEL state specifies that the command affects only devices in the specified state. STOP MON Example See the procedure for Stopping the SMF Master Process on page 4-7. To stop access to the SMF master process: -> STOP $ZSMS STOP POOL Command The STOP POOL command stops access to the specified storage pool. The syntax is: STOP [ / OUT file-spec / ] POOL $pool [ , FORCED ] [ , SEL state ] Wild-card characters are supported.
STOP SCSI Command Storage Subsystem Commands STOP SCSI Command The STOP SCSI command stops access to an Open SCSI device. The syntax is: STOP [ / OUT file-spec / ] [ , FORCED ] SCSI $SCSI-device[-P |-B ] [ , SEL state ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. SCSI $SCSI-device [-P |-B ] is the name of the Open SCSI IOP and, optionally, the path (primary or backup).
Storage Subsystem Commands STOP TAPE Command OUT file-spec directs all SCF output to the specified file. TAPE $tape is the name of the tape device. FORCED specifies that the command be executed without any interaction with the user, even if the command stops the last path to the device or files are open on the device. If you use this attribute, you must first stop all processes that use the disk to store object code (programs) or swap files. Otherwise, a %5113 halt could occur.
STOPOPENS Command Storage Subsystem Commands STOPOPENS Command The STOPOPENS command prevents any additional opens to an object. STOPOPENS is a sensitive command. STOPOPENS DISK Command The STOPOPENS command prevents applications from opening files on the specified magnetic or virtual disk volume. Use the ALLOWOPENS command to let applications open files on the disk again. Caution. Do not issue a STOPOPENS DISK command on the system disk.
Storage Subsystem Commands STOPOPENS DISK Command STOPOPENS DISK Examples See Preventing File Opens on a Magnetic Disk on page 7-22. You cannot issue a STOPOPENS DISK command to a virtual disk.
SWITCH Command Storage Subsystem Commands SWITCH Command The SWITCH command designates the active a path to a device. Supported objects are: ADAPTER page 14-137 DISK page 14-138 SCSI page 14-139 SWITCH is a sensitive command. SWITCH ADAPTER Command The SWITCH ADAPTER command moves all device paths from and to a SAC on an adapter, as part of adapter replacement. The syntax is: SWITCH [ / OUT file-spec / ] ADAPTER $ZZSTO.#type.GRP-g.MOD-m.
SWITCH DISK Command Storage Subsystem Commands SWITCH ADAPTER Examples • To stop all data paths to a PMF adapter before removing it: -> SWITCH ADAPTER $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-55, & -> AWAY, FORCED • To restore data paths to an adapter after inserting it: -> SWITCH ADAPTER $ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-54, DEFAULT SWITCH DISK Command The SWITCH DISK command designates the active paths to a magnetic disk, as well as the preferred SAC path for any disk accessible through dual paths.
SWITCH SCSI Command Storage Subsystem Commands • To designate the mirror path of a volume as the primary disk path: -> SWITCH $DATA00-M • To designate the backup path of a volume as the primary disk path: -> SWITCH $DATA-B • To combine both of the previous commands: -> SWITCH DISK ($DATA00-M, $DATA-B) SWITCH SCSI Command The SWITCH SCSI command designates the active path to an Open SCSI device and, in doing so, designates the preferred SAC path for the Open SCSI device.
VERSION Command Storage Subsystem Commands VERSION Command The VERSION command displays current version information about the storage subsystem manager. VERSION SUBSYS Command VERSION [ / OUT file-spec / ] SUBSYS $ZZSTO [ , DETAIL ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. SUBSYS $ZZSTO is the storage subsystem manager. DETAIL displays version information about the storage subsystem, Guardian, and SCF Kernel components of the system.
A SCF Command Summary Attribute descriptions, and examples for these storage subsystem commands appear in Section 14, Storage Subsystem Commands. ABORT [ /OUT file-spec/ ] DISK $disk [-P |-B |-M |-MB ] [ , FORCED ] [ , POOL $pool ] [ , SEL state ] [ , SUB { ALL | MAGNETIC | VIRTUAL } ] ABORT [ /OUT file-spec/ ] MON $ZSMS ABORT [ /OUT file-spec/ ] POOL $pool ADD [ /OUT file-spec/ ] DISK $disk , SENDTO STORAGE [ , LIKE object ] [ , attribute-spec ]...
SCF Command Summary ADD [ /OUT file-spec/ ] SCSI $SCSI-device , SENDTO STORAGE [ , LIKE object ] [ , attribute-spec ]... ADD [ OUT file-spec ] TAPE $tape , SENDTO STORAGE [ , LIKE object ] [ attribute-spec ]... ALLOWOPENS [ /OUT file-spec/ ] DISK $disk [ , POOL $pool ] [ , SEL state ] [ , SUB { ALL | MAGNETIC | VIRTUAL } ] [ , SUPERONLY ] ALTER [ / OUT file-spec / ] DISK $disk [ , LIKE object ] [ , attribute-spec ]... ALTER [ / OUT file-spec / ] MON $ZSMS [ , attribute-spec ]...
SCF Command Summary ALTER [ / OUT file-spec / ] SUBSYS $ZZSTO [ , attribute-spec ]... ALTER [ / OUT file-spec / ] TAPE $tape [ , LIKE object ] [ , attribute-spec ]... CONTROL [ /OUT file-spec/ ] DISK $disk[-P |-M ] [ , POOL $pool ] [ , SEL state ] [ , SUB { ALL | MAGNETIC } ] [ , attribute-spec ]... DELETE [ / OUT file-spec / ] ADAPTER $ZZSTO.#type.GRP-g.MOD-m.
SCF Command Summary DELETE [ / OUT file-spec / ] SCSI $SCSI-device [ , SEL state ] DELETE INFO [ / OUT file-spec / ] TAPE $tape [ / OUT file-spec / ] ADAPTER $ZZSTO.#type.GRP-g.MOD-m.
SCF Command Summary INFO [ / OUT file-spec / ] SUBSYS $ZZSTO INFO [ / OUT file-spec / ] TAPE $tape [ , { DETAIL | OBEYFORM } ] [ , SEL state ] INITIALIZE [ / OUT file-spec / ] DISK $disk[-P |-M ] [ , LABEL $volume ] LABEL [ / OUT file-spec / ] DISK { $ldev|$disk } , $newname [ , attribute-spec ] NAMES [ / OUT file-spec / ] [ object-spec ] [ , POOL $pool ] [ , SEL state ] PRIMARY [ / OUT file-spec / ] [ , cpunumber ] [ , SUB subobjtype ] DISK $disk [ , FORCED ] [ , POOL $pool ] [ , SEL state ]
SCF Command Summary PRIMARY [ / OUT file-spec / ] SUBSYS $ZZSTO , cpunumber , { AWAY | DEFAULT } PRIMARY [ / OUT file-spec / ] TAPE $tape [ , cpunumber ] PROBE [ / OUT file-spec / ] SAC $ZZSTO.#sac-name [ , COUNT n [ , CONTINUE ] ] [ , DATA pattern ] [ , PORTNAME wwn ] RENAME [ / OUT file-spec / ] DISK $disk , $new-disk REPLACE [ / OUT file-spec / ] ADAPTER $ZZSTO.#adapter-name [ , attribute-spec ] ... REPLACE [ / OUT file-spec / ] SAC $ZZSTO.
SCF Command Summary RESET [ / OUT file-spec / ] POOL $pool [ , FORCED ] [ , SEL state ] RESET [ / OUT file-spec / ] SCSI $SCSI-device [ , FORCED ] [ , SEL state ] RESET [ / OUT file-spec / ] TAPE $tape [ , FORCED ] [ , SEL state ] START [ / OUT file-spec / ] [ , DEBUG $terminal ] DISK $disk[-P |-B |-M |-MB ] [ , POOL $pool ] [ , NOWAIT ] [ , SEL state ] [ , SPECIAL ] [ , SUB { ALL | MAGNETIC | VIRTUAL } ] START [ / OUT file-spec / ] MON $ZSMS [ , DEBUG $terminal ] [ , SEL state ] [ , SPECIAL
SCF Command Summary STATS [ / OUT file-spec / ] DISK $disk [ , POOL $pool ] [ , SEL state ] [ , RESET [ , FORCED ] ] [ , SUB { ALL | MAGNETIC | VIRTUAL } ] STATS [ / OUT file-spec / ] SAC $ZZSTO.#sac-name [ , PORTNAME wwn ] [ , RESET [ , FORCED ] ] STATUS [ / OUT file-spec / ] ADAPTER $ZZSTO.#type.GRP-g.MOD-m.
SCF Command Summary STATUS [ / OUT file-spec / ] SUBSYS $ZZSTO STATUS [ / OUT file-spec / ] TAPE $tape STOP [ / OUT file-spec / ] [ , FORCED ] [ , DETAIL ] [ , DETAIL ] DISK $disk[-P |-B |-M |-MB ] [ , POOL $pool ] [ , SEL state ] [ , SUB { ALL | MAGNETIC | VIRTUAL } ] STOP [ / OUT file-spec / ] MON $ZSMS [ , FORCED ] [ , SEL state ] STOP [ / OUT file-spec / ] POOL $pool [ , FORCED ] [ , SEL state ] STOP [ / OUT file-spec / ] [ , FORCED ] SCSI $SCSI-device[-P |-B ] [ , SEL state ] STOP [ / O
SCF Command Summary SWITCH [ / OUT file-spec / ] ADAPTER $ZZSTO.#type.GRP-g.MOD-m.
B Storage Subsystem Error Messages This appendix describes where to get more information about error messages. For error messages associated with the storage subsystem, refer to the Operator Messages Manual. For SCF messages for all subsystems, refer to the SCF Reference Manual for G-Series RVUs. If You Have to Contact Your Service Provider If the recovery for an error message indicates to contact your service provider or the Global Customer Support Center (GCSC), supply this following log file: 1.
Storage Subsystem Error Messages Handling File-System Error Messages Handling File-System Error Messages When you encounter file-system error messages that display a number, use one of these methods to get a description of the error: • Use online help to display it. For example, to display help text associated with filesystem error 66: -> error 66 • Look up the error number in the Guardian Procedure Calls Reference Manual.
Storage Subsystem Error Messages Storage Subsystem Error Messages Cause. Response type ZSPI-VAL-ERR-AND-WARN was specified by the server but the reply buffer contained no error nor warning. Effect. SCF waits for the next command. Recovery. Informational message only; no corrective action is required. 00004 STORAGE 00004 Token conflict in requester buffer, token: tokname, object name: objname tokname is the name of the token issued with the command.
Storage Subsystem Error Messages Storage Subsystem Error Messages Effect. The command is not executed. SCF waits for the next command. Recovery. Report this problem immediately. See If You Have to Contact Your Service Provider on page B-1. 00007 STORAGE 00007 Duplicate attribute: attribute attribute is the attribute that you specified more than once in the command. Cause. You entered the same attribute twice in the command. Effect. The command is not executed. SCF waits for the next command. Recovery.
Storage Subsystem Error Messages • Storage Subsystem Error Messages The device being serviced Effect. The command is not executed. SCF waits for the next command. Recovery. 1. Verify the state of the device using the SCF STATUS command. 2. If needed, use the SCF RESET command to change the state of the device before retrying the operation. 00010 STORAGE 00010 Negative response received from Storage Subsystem Manager. Cause. The command was rejected by the storage subsystem manager process ($ZZSTO).
Storage Subsystem Error Messages Storage Subsystem Error Messages devname is the name of the device you specified in the command. state is the current state of the device you specified in the command. Cause. The device is in a state that prevents it from performing the operation requested. This error can occur when you perform online as well as offline reconfiguration. You cannot perform an online reconfiguration of a mirror drive while TSM ($ZTSM) is running. Effect. The command is not executed.
Storage Subsystem Error Messages Storage Subsystem Error Messages Effect. The command is not executed. SCF waits for the next command. Recovery. Report this problem immediately. See If You Have to Contact Your Service Provider on page B-1. 00015 STORAGE 00015 Unexpected error returned from $ZCNF, error: err-num, error detail: err-detailnum (errdesc). err-num is the error number returned from the $ZCNF process. err-detailnum is the error detail number returned from the $ZCNF process.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. Report this problem immediately. See If You Have to Contact Your Service Provider on page B-1. 00017 STORAGE 00017 Unexpected error returned from CONFIG_GETINFO_, error: err-num, error detail: err-detailnum. err-num is the error number returned from the CONFIG_GETINFO_ system procedure. err-detailnum is the error detail number returned from the CONFIG_GETINFO_ system procedure. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. The recovery action depends on the cause: 1. Use the SCF START command. If the processor is not down, the START command will restart the IOP process. 2. If the processors are down, reload the processors. For instructions about how to reload processors, see the NonStop S-Series Operations Guide. If the problem persists, contact your service provider. See If You Have to Contact Your Service Provider on page B-1.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00022 STORAGE 00022 Required attribute not specified: BACKUPCPU Cause. You did not specify the BACKUPCPU attribute with the command. Effect. The command is not executed. SCF waits for the next command. Recovery. Reissue the command with the BACKUPCPU attribute. 00023 STORAGE 00023 Required attribute not specified: LOCATION Cause. You did not specify the LOCATION attribute with the command. Effect. The command is not executed.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00026 STORAGE 00026 MIRRORLOCATION: Invalid value specified. Cause. You specified an invalid value for the MIRRORLOCATION attribute for the disk. Currently, the PRIMARYLOCATION and MIRRORLOCATION attributes must specify the same group. The MIRRORLOCATION must specify the group, module, and slot location of the mirror disk. For example: -> ALTER DISK $DATA04, MIRRORLOCATION (1,1,8) Effect. The command is not executed.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00029 STORAGE 00029 objtype devname is not present in location (grp,mod,slot) objtype is the object type of the object you specified with the command. devname is the name of the device you specified in the command. grp,mod,slot is the group, module, and slot location of the device you specified in the command. Cause. The device specified in a command is not physically present in the location. Effect. The command is not executed.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00031 STORAGE 00031 System configuration database ($SYSTEM.ZSYSCONF.CONFIG) is locked. Cause. The system configuration database is busy and therefore temporarily locked. Effect. The command is not executed. SCF waits for the next command. Recovery. Wait a short while and reissue the command. If the problem persists, contact your service provider. See If You Have to Contact Your Service Provider on page B-1.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. Add the device to the system configuration using the SCF ADD command. If the problem persists, contact your service provider. See If You Have to Contact Your Service Provider on page B-1. 00034 STORAGE 00034 command failed. Mismatch between adapter ACCESSLIST. Parameter: value. command is the command you specified. value is the value you specified in the command. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages processor is the attribute you used in the command to specify the primary processor (PRIMARYCPU) or backup processor (BACKUPCPU). Cause. You specified an invalid processor number in the command. The specified processor cannot access the adapters controlling the device. Effect. The command is not executed. SCF waits for the next command. Recovery. Reissue the command with the correct processor number.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00039 STORAGE 00039 Object is already being used. Object is the type of the device you specified in the command. Cause. The device you specified in the command is already being used. Effect. The command is not executed. SCF waits for the next command. Recovery. Reissue the command and specify the correct device. 00040 STORAGE 00040 Configuration database record not found. Cause. One or more configuration database records are missing.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00043 STORAGE 00043 Wrong path specified: object-type name. Cause. You specified a command that does not allow the specified device path. Effect. The command is not executed. SCF waits for the next command. Recovery. Correct and reissue the command. 00044 STORAGE 00044 Configuration database record already exists. Cause. The object is already configured. The indicated object might already be configured by another device. Effect.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00047 STORAGE 00047 CPUs not running. Cause. You issued a START or PRIMARY command targeting a processor or set of processors that were not running. Effect. The command is not executed. SCF waits for the next command. Recovery. Reload the processors or change the configuration and reissue the command. 00048 STORAGE 00048 Required adapter not present for location. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages Effect. The command is not executed. SCF waits for the next command. Recovery. Reissue the command using the correct storage pool attribute. 00051 STORAGE 00051 command failed. Disk does not belong to any pool command is the command you specified. Cause. you issued an ALTER command using POOL attributes for a disk that does not belong to any storage pool. Effect. The command is not executed. SCF waits for the next command. Recovery.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. Reissue the command specifying a valid location for BACKUPLOCATION. 00055 STORAGE 00055 PRIMARYLOCATION AND BACKUPLOCATION are equal. Cause. You specified the same location for PRIMARYLOCATION and BACKUPLOCATION. Effect. The command is not executed. SCF waits for the next command. Recovery. Reissue the command using unique values for PRIMARYLOCATION and BACKUPLOCATION. 00056 STORAGE 00056 SMF pool communication error. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages Effect. The command is not executed. SCF waits for the next command. Recovery. Resolve the cause of the failure and reissue the command. 00059 STORAGE 00059 Program file is not $SYSTEM.SYSTEM. Cause. You specified that the PROGRAM file of a storage object is located in a subvolume other than $SYSTEM.SYSTEM. You must verify you want to use the specified subvolume. No warning is given in noninteractive mode. Effect.
Storage Subsystem Error Messages Storage Subsystem Error Messages Cause. You requested information for a CRU, but that information was unavailable from the hardware inventory table. Effect. The command is not executed. SCF waits for the next command. Recovery. Verify the hardware is actually present and connected correctly. 00062 STORAGE 00062 Error from PROCESS_LAUNCH_, error: errnum, error detail: text. errnum is the error number returned from the PROCESS_LAUNCH_ procedure.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00064 STORAGE 00064 errnum cmd failed. No CRU info; cru-info error: cmd is the command you specified. cru-info is additional information about the CRU in the command you specified. errnum is the error associated with this failure. Cause. While trying to complete the requested command, communication with the CRU was interrupted. Effect. The command is not executed. SCF waits for the next command. Recovery.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00066 STORAGE 00066 cmd failed. POST did not succeed for sacpath. cmd is the command you specified. sacpath is the path of the ServerNet addressable controller (SAC) specified in the command. Cause. The indicated SAC did not pass the power-on self-test (POST). Effect. The command is not executed. SCF waits for the next command. Recovery. Contact your service provider. See If You Have to Contact Your Service Provider on page B-1.
Storage Subsystem Error Messages Storage Subsystem Error Messages is the path of the ServerNet addressable controller (SAC) specified in the command. Cause. The device type of the device specified in the command does not match the device type of the primary device. Effect. The command is not executed. SCF waits for the next command. Recovery. Verify the device specified in the command is the same type as the primary device. (For example, you are trying to mirror an internal disk with a 45xx disk.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00071 STORAGE 00071 Attribute attname is obsolete and will not be supported in future releases. attname is the name of the obsolete attribute you used in the command. Cause. You specified an obsolete attribute with a command. Effect. The command is not executed. SCF waits for the next command. Recovery. Avoid using the attribute. Modify command files that contain commands using this attribute. 00072 STORAGE 00072 deleted.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00074 STORAGE 00074 Operation invalid, REPLACE already committed. Cause. You issued a REPLACE command twice. Effect. The command is not executed. SCF waits for the next command. Recovery. Use the REVERT operation to back out of the committed replace. 00075 STORAGE 00075 REPLACE DISK volname failed to delete software replacement record, error err-num. volname is the disk name you specified. err-num is the file-system error that occurred.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00077 STORAGE 00077 REPLACE DISK volname software replacement record read, error: err-num. volname is the disk name you specified. err-num is the file-system error that occurred. For more information, refer to the Guardian Procedure Errors and Messages Manual. Cause. A file-system error occurred while data was being read from $SYSTEM.SYSnn.CONFALT. Effect. The command is not executed. SCF waits for the next command. Recovery.
Storage Subsystem Error Messages Storage Subsystem Error Messages Effect. The command is not executed. SCF waits for the next command. Recovery. Issue the REPLACE, ABANDON command. 00080 STORAGE 00080 A replace operation is still pending. Cause. A REPLACE, PROGRAM or REPLACE, AGAIN operation has not finished. Effect. The command is not executed. SCF waits for the next command. Recovery. 1. Wait for the operation to finish. 2. If it does not finish, reactivate it with the REPLACE, AGAIN command. 3.
Storage Subsystem Error Messages Storage Subsystem Error Messages Effect. The command fails, possibly with the replace operation half finished. Recovery. 1. Refer to the error message for the cause of the error. 2. Retry the command. 3. If the problem persists, contact your service provider. See If You Have to Contact Your Service Provider on page B-1. 00083 STORAGE 00083 Unexpected error returned from DSC_OLSR_DEVICE_, error: err-num. err-num is the file-system error that occurred.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. 1. Refer to the error message for the cause of the error. 2. Retry the command. 3. If the problem persists, contact your service provider. See If You Have to Contact Your Service Provider on page B-1. 00085 STORAGE 00085 REPLACE DISK volname Filesystem error returned from DSC_OLR_DEVICE_, error: err-num. volname is the disk name you specified. err-num is the file-system error that occurred.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00087 STORAGE 00087 DISK volname cannot have IOP object on itself. volname is the disk name you specified. Cause. You attempted to run a disk IOP from an object file that resides on the disk controlled by that IOP. Effect. The command is not executed. SCF waits for the next command. Recovery. Run the disk IOP from an object file that is not located on the disk controlled by that IOP.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00089 STORAGE 00089 expected. Non-supported adapter found where devname was devname is the device name expected by SCF. Cause. SCF found a nonsupported adapter where it expected to find a supported storage adapter. Effect. The command is not executed. SCF waits for the next command. Recovery. Recovery depends on the results you want. If you want a storage adapter configured in the slot: 1. Remove whatever is in the slot. 2.
Storage Subsystem Error Messages Storage Subsystem Error Messages 2. Verify that the object you are using for the REPLACE, PROGRAM command is compatible with the running object. 00091 STORAGE 00091 Unsupported program version. Cause. You issued a REPLACE command, and one of two problems occurred: • The program file used for this command did not contain the expected version of the procedure. • The version of the procedure did not indicate that it supported this command. Effect.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00094 STORAGE 00094 Both paths of the disk process are assigned the same fabric. Cause. When you entered the command, you assigned the same fabric to access both paths to the disk. Effect. The command is executed. This is a warning. Recovery. Reissue the command and assign a separate path to each path. 00095 STORAGE 00095 Unable to process the command due to an internal NSC error. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. Handle those exceptions individually. 00098 STORAGE W00098 Action begun successfully, but not yet finished. Monitor with STATUS. Cause. The action was initiated successfully, but it has not yet finished. Effect. The command is executed. This message is only a reminder. Recovery. Use the STATUS command to monitor the progress of the action. 00099 STORAGE E00099 The process cannot be terminated. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00102 STORAGE E00102 Requested operation failed due to a file system error. Cause. Requested operation failed due to a file system error. Effect. The command is not executed. SCF waits for the next command. Recovery. Check the returned file system error to determine what to do next. 00103 STORAGE E00103 Command rejected because there's another action pending for the specified object name. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages 00106 STORAGE E00106 The two paths to a device must be in different IOAM modules Cause. You have specified two paths to a device through FCSA adapters in the same IOAM module. This configuration is not recommended. Effect. The command is not executed. SCF waits for the next command Recovery. Specify the two paths in different IOAM modules.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. Start the FCSMON processes. If they are already running, wait 3 minutes and re-try the command. 00110 STORAGE E00110 Alternate path SAC is not connected to the same device. Cause. The alternate path (BACKUP or MBACKUP) SAC is not connected to the same device as the corresponding primary path (PRIMARY or MIRROR). Effect. The command is not executed. SCF waits for the next command. Recovery.
Storage Subsystem Error Messages Storage Subsystem Error Messages Effect. The disk revive operation is started. Recovery. Informational message only; no corrective action is required. SCF initializes a disk revive operation. 01002 STORAGE 01002 objtype devname is state. Please use RESET command. objtype is the object type of the object you specified with the command. devname is the name of the device you specified in the command. state is the current state of the device you specified in the command.
Storage Subsystem Error Messages Storage Subsystem Error Messages command is the SCF command that you issued. Cause. The command you issued is not allowed for a disk that contains active audit trail files. Effect. The command is not executed. SCF waits for the next command. Recovery. 1. Verify you issued the command for the correct disk. 2. If you issued the command for the correct disk, you must stop the Transaction Management Facility (TMF) subsystem and then reissue the command.
Storage Subsystem Error Messages Storage Subsystem Error Messages 01007 STORAGE 01007 The command will make all paths to volname inaccessible. command is the SCF command that you issued. volname is the name of the volume that you specified in the command. Cause. You issued a command that would make all paths to the disk inaccessible. This message is generated by SCF only in noninteractive mode. In interactive mode, a prompt is generated asking you to verify the command. Effect.
Storage Subsystem Error Messages Storage Subsystem Error Messages volname is the name of the volume that you specified in the command to alter cache. Cause. You issued an ALTER DISK, CACHE command in noninteractive mode. In interactive mode, you are prompted to verify the operation. Effect. The cache counters are reset. Recovery. Informational message only; no corrective action is required. 01010 STORAGE 01010 The ALTER DISK, LABEL command will DESTROY any existing files on volname.
Storage Subsystem Error Messages Storage Subsystem Error Messages 2. Remove the command from the SCF command file. 01012 STORAGE 01012 The CONTROL DISK, REPLACEBOOT operation will OVERWRITE the existing bootstrap on volname. volname is the name of the volume that you specified in the command. Cause. You issued the CONTROL DISK, REPLACEBOOT command in noninteractive mode. The CONTROL DISK, REPLACEBOOT command is available only in interactive mode.
Storage Subsystem Error Messages Storage Subsystem Error Messages Cause. You issued the CONTROL DISK, SPARE command to spare a disk sector. The disk controller has verified that the sector does not need to be spared. Effect. The disk sector is not spared. SCF waits for the next command. Recovery. 1. Verify you used the correct sector address. 2. Reissue the command with the correct address, if needed.
Storage Subsystem Error Messages Storage Subsystem Error Messages 01017 STORAGE 01017 command, processornum failed. command is the SCF command that you issued. processornum is the processor number of the processor you specified in the command. Cause. You issued a command to change processor ownership but the storage subsystem manager process detected that it did not occur, even though no error was returned from the disk process. Effect. The processor ownership is unchanged. SCF waits for the next command.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. 1. Verify you used the correct disk name. 2. Reissue the command, if necessary. 01020 STORAGE 01020 ALTER DISK volname, LABEL failed, disk is in an incorrect state. volname is the name of the volume that you specified in the command. Cause. You tried to update the label on a disk that is not in a correct state. Effect. The label operation is not performed. SCF waits for the next command. Recovery.
Storage Subsystem Error Messages Storage Subsystem Error Messages is the error number of the failure. Cause. An error occurred in an internal work file that prevented the label operation from finishing. Effect. The label operation is not performed. SCF waits for the next command. Recovery. Contact your service provider. See If You Have to Contact Your Service Provider on page B-1. 01023 STORAGE 01023 ALTER DISK volname, LABEL failed, disk error err-num.
Storage Subsystem Error Messages Storage Subsystem Error Messages 01025 STORAGE 01025 CONTROL DISK volname, REPLACEBOOT failed (invalid boot section). volname is the name of the volume that you specified in the command. Cause. An invalid section in the bootstrap file prevented the REPLACEBOOT operation from finishing. Effect. The REPLACEBOOT operation is not performed. SCF waits for the next command. Recovery. Contact your service provider to obtain a new bootstrap file and retry the command.
Storage Subsystem Error Messages Storage Subsystem Error Messages Effect. The REPLACEBOOT operation is not performed. SCF waits for the next command. Recovery. Correct the problem indicated by the error number and reissue the command. 01028 STORAGE 01028 CONTROL DISK volname, REPLACEBOOT failed (I/O error err-num on bootstrap file). volname is the name of the volume that you specified in the command. err-num is the I/O error number of the failure. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages 01030 STORAGE 01030 CONTROL DISK volname, REPLACEBOOT failed (internal error was detected). volname is the name of the volume that you specified in the command. Cause. An internal REPLACEBOOT algorithm error prevented the bootstrap replacement. Effect. The REPLACEBOOT operation is not performed. SCF waits for the next command. Recovery. Report this problem immediately. See If You Have to Contact Your Service Provider on page B-1.
Storage Subsystem Error Messages Storage Subsystem Error Messages 1. You can use the disk to load your system. 2. Contact your service provider. See If You Have to Contact Your Service Provider on page B-1. 01033 STORAGE 01033 Disk old-name changed name to new-name. Cause. An automatic disk rename took place. This can happen when a new disk is installed in a slot and the label has a name that does not match the name in the system configuration database.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. Determine the correct value for the attribute and reissue the command. 01036 STORAGE 01036 Disk pair is not consistent. The devname diskhalf not restarted. devname is the name of the device you specified in the command. Cause. The modification time stamps on the primary and mirror disks of the mirrored volume differ. A revive operation is required. Effect. The command is executed.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. You have the choice to start the disk regardless of the label discrepancy. In same cases, you have to choose whether to start the primary or mirror half of the disk. 01040 STORAGE 01040 Both slots target the same SCSI chain. Cause. Both locations for a mirrored disk volume target the same SCSI bus. Effect. The command is not executed. SCF waits for the next command. Recovery.
Storage Subsystem Error Messages Storage Subsystem Error Messages is the number of open files on the disk. Cause. You issued a STOPOPENS command for a disk with open files. Effect. The command is not executed. SCF waits for the next command. Recovery. Informational message only; no corrective action is required. 01044 STORAGE 01044 ALTER DISK $DATA00, Autoselect change failed, error errnum errnum is the error number provided by the file-system. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages 01047 STORAGE 01047 Not allowed: The disk is audited. Cause. This command, if executed, would leave the TMF product in an inconsistent state. Effect. The command is not executed. SCF waits for the next command. Recovery. Disable the disk under the TMF product and reissue the command. 01048 STORAGE 01048 Sector secnum is out of range. maxsecnum Maximum is secnum is the sector number you specified with the command.
Storage Subsystem Error Messages Storage Subsystem Error Messages 01050 STORAGE 01050 devname is currently running unmirrored. REPLACEBOOT operation cannot be performed. devname is the name of the device you specified in the command. Cause. You issued the CONTROL DISK, REPLACEBOOT command in noninteractive mode. This command is available only in interactive mode.
Storage Subsystem Error Messages Storage Subsystem Error Messages Cause. You have not used the REPLACE command from interactive mode. Effect. The command is not executed. SCF waits for the next command. Recovery. Reissue the REPLACE command from an interactive prompt. 01054 STORAGE 01054 command devname failed. Impossible, 3-cable configuration implied by other devices using the same SAC. command is the SCF command that you issued. devname is the name of the device you specified in the command. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. Either: • • Correct the value for the indicated attribute. Place the I/O process in a STOPPED state and reissue the command. 01056 STORAGE W01056 The primary and mirror paths to a device should be on different chains. Cause. You specified primary and mirror paths to a device on the same chain. This configuration is not recommended. Effect. The command is executed. This is a warning. Recovery.
Storage Subsystem Error Messages Storage Subsystem Error Messages 01059 STORAGE W01059 This action will cause the mirror-related configuration of the disk to change while the disk volume is in a started state. Cause. You requested changes to mirror-related configuration attributes of a disk volume that is in a started state. This warning message is issued to inform you of the effect of the command. Effect.
Storage Subsystem Error Messages Storage Subsystem Error Messages If you cannot resolve the problem indicated by errnum and error-detail, contact your service provider. If you determine that you can resolve the problem yourself, perform either of these two actions: 1. Reissue the command that specified the new configuration. The storage subsystem manager ($ZZSTO) then retries the configuration change.
Storage Subsystem Error Messages Storage Subsystem Error Messages tolerance. For instance, the backup disk might have lost its access to the mirror disk drive. Depending on the error condition indicated by errnum and error-detail, perform either of these two actions: • Reissue the command that specified the new configuration.
Storage Subsystem Error Messages Storage Subsystem Error Messages 01064 STORAGE E01064 Command failed. Another disk using the same adapter shares a CPU but not both adapters. Cause. Another disk using the same adapter shares a CPU but not both adapters. This configuration is not supported on G-series RVUs prior to G06.27 or on the H06.03 RVU. Effect. The command is not executed. SCF waits for the next command. Recovery. Use INFO ADAPTER, DETAIL to see other disks using the same adapter.
Storage Subsystem Error Messages Storage Subsystem Error Messages is the error number provided by the file system. Cause. There is no SMF MON definition for the device. Effect. The command is not executed. SCF waits for the next command. Recovery. Check the returned file-system error to determine what to do next. 09003 STORAGE 09003 cmd rejected, SMF error: errnum cmd is the command that you issued. errnum is the error number provided by the Storage Management Foundation (SMF). Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages Effect. The command is not executed. SCF waits for the next command. Recovery. Reissue the command and include the CATALOGLOCATION attribute. 09006 STORAGE 09006 Required attribute not specified: POOL Cause. You did not specify the POOL attribute in the command you issued. Effect. The command is not executed. SCF waits for the next command. Recovery. Reissue the command and include the POOL attribute.
Storage Subsystem Error Messages Storage Subsystem Error Messages 09010 STORAGE 09010 ABORT is not supported for this process. will be used. STOP Cause. You issued the ABORT command for a process that doesn’t accept it. Effect. The command is not executed. SCF issues the STOP command. Recovery. Informational message only; no corrective action is required. 09011 STORAGE 09011 Invalid format in location name. Cause. You issued a command with an invalid location name. Effect. The command is not executed.
Storage Subsystem Error Messages Storage Subsystem Error Messages 09014 STORAGE 09014 SMF dependency failure: Required process name is not running. name is the name of the process that is needed to complete the command. Cause. A process is not running that is needed for the command you issued. Effect. The command is not executed. SCF waits for the next command. Recovery. Start the required process and reissue the command. 09015 STORAGE 09015 SMF dependency failure: TMF is not running. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. Reissue the command to a volume that will accept the file or change the value of the PHYSVOLSELECT attribute of the disk you used in the command. 09018 STORAGE 09018 SMF dependency failure: Catalog disk volume name is not in a pool. name is the name of the catalog disk volume you used in the command you issued. Cause. The catalog disk volume that you specified in the command does not reside in a storage pool. Effect.
Storage Subsystem Error Messages Storage Subsystem Error Messages 09021 STORAGE 09021 SMF dependency failure: Invalid syntax for filename Cause. The configuration database record contains an invalid file name. Effect. The command is not executed. SCF waits for the next command. Recovery. Correct the configuration database record that contains the invalid file name and reissue the command. 09022 STORAGE 09022 SMF dependency failure: Can’t read configuration record for name. name is the name of the device.
Storage Subsystem Error Messages Storage Subsystem Error Messages is the name of the process. Cause. You issued a command specifying a monitor or storage pool attribute for an object of the wrong type. Effect. The command is not executed. SCF waits for the next command. Recovery. Determine the correct object and reissue the command. 09025 STORAGE 09025 Can't delete pool because virtual disks are associated with it. Cause.
Storage Subsystem Error Messages Storage Subsystem Error Messages 09027 STORAGE 09027 Can't put disk in pool because disk label doesn't match disk name. Cause. You attempted to add a disk to a storage pool whose disk name in the configuration database does not match the name on the label. Effect. The command is not executed. SCF waits for the next command. Recovery. Start the disk with or without the SPECIAL attribute.
Storage Subsystem Error Messages Storage Subsystem Error Messages Recovery. Change the command so that the device and attribute match. For example, if POOL is specified, the name must be the name of a storage pool. If you specify the LIKE attribute, both object names must be of the same type. 09030 STORAGE 09030 This disk is already associated with another pool. Cause. You issued a command to associate a physical volume with a storage pool, but the volume is already associated with another storage pool.
Storage Subsystem Error Messages Storage Subsystem Error Messages 09033 STORAGE 09033 Required attribute not specified attribute. attribute is the name of an attribute. Cause. You issued a command without specifying a required attribute. Effect. The command is not executed. SCF waits for the next command. Recovery. Make the request again, using the required attribute. 09034 STORAGE 09034 devname cannot be configured on a sacname which is on an adaptername.
Storage Subsystem Error Messages Storage Subsystem Error Messages 09035 STORAGE 09035 Can’t delete pool because a disk profile refers to the pool. Cause. You attempted to delete a storage pool that is referenced by a disk profile. Effect. The command is not executed. SCF waits for the next command. Recovery. 1. Issue the INFO, PROFILE command to determine which disk profiles refer to the storage pool. 2. Delete the disk profile that refers to the pool. 3. Retry the command.
C Converting D-Series PUP and COUP Commands to SCF Commands This appendix compares PUP and COUP commands to their SCF equivalents.
Converting D-Series PUP and COUP Commands to SCF Commands PUP Commands and Equivalent SCF Commands PUP Commands and Equivalent SCF Commands PUP Command SCF Command Comments ALLOWOPENS ALLOWOPENS DISK Permits files to be opened on a magnetic disk. It reverses the effect of the STOPOPENS command. CHECKSUM CONTROL DISK, CHECKSUM Reads and rewrites disk sectors in order to correct checksum values. CONSOLE -- Not applicable to the storage subsystem.
Converting D-Series PUP and COUP Commands to SCF Commands PUP Commands and Equivalent SCF Commands PUP Command SCF Command Comments (continued) ISOLATE ALTER DISK, PHYSVOLSELECT ON The virtual disk process is allowed to put files on the volume only when the request contains the physical volume name. FORMAT INITIALIZE DISK Erases existing files, labels the disk, and starts it. LABEL ALTER DISK, LABEL Erases existing files and writes a volume label on a new or previously labeled volume.
Converting D-Series PUP and COUP Commands to SCF Commands PUP Commands and Equivalent SCF Commands PUP Command SCF Command Comments (continued) REFRESH CONTROL DISK, REFRESH Performs a refresh operation for a disk when all paths have been stopped. REDEFINEVIRTDISK ALTER DISK, TYPE VIRTUAL Changes any specified attributes for the virtual disk. REMOVE STOP DISK Performs an implicit remove. (An implicit remove is also performed when the system is shut down.
Converting D-Series PUP and COUP Commands to SCF Commands Comparison of PUP Object States and SCF Object States and Substates Comparison of PUP Object States and SCF Object States and Substates The SCF STATUS command displays the current state and substate of an object. For a description of states and substates: • • • For DISK objects, see Object States and Substates of Magnetic Disks on page 2-5. For SCSI objects, see SCSI Object States on page 2-11.
Converting D-Series PUP and COUP Commands to SCF Commands COUP Commands and Equivalent SCF Commands COUP Commands and Equivalent SCF Commands Magnetic disks are a COUP DEVICE, and virtual disks are a COUP PROCESS.
D Upgrade and Replacement Procedures Replacing a Tape Drive If you physically remove a tape drive and replace it with another tape drive that is controlled by the same adapter, the tape process automatically recognizes the new tape drive. For other details about installing or removing a tape drive, see the documentation that comes with the tape drive or contact your service provider. 1. Stop the tape drive: -> STOP $TAPE0 2. Verify the tape drive is in the STOPPED state: -> STATUS $TAPE0 3.
Upgrade and Replacement Procedures Replacing an Open SCSI Device Replacing an Open SCSI Device To replace an Open SCSI device: 1. Stop access to the device: -> STOP $S11500 2. Verify the device is in the STOPPED state: -> STATUS $S11500 3. Physically remove the device from the SCSI chain. 4. Configure the SCSI ID and LUN on the device according to the manufacturer’s instructions. 5. Physically install the new device in the SCSI chain. 6.
Upgrade and Replacement Procedures Upgrading a Mirrored Volume Online If this is an internal disk, it powers on and immediately begins to revive if you have enabled AUTOSTART (page 6-12) and AUTOREVIVE (page 6-13) for both the specific disk and for the subsystem. 6.
Upgrade and Replacement Procedures Upgrading a Mirrored Volume Online SCF Reference Manual for the Storage Subsystem—529937-008 D- 4
Glossary 45xx disk. A disk drive that resides in slots 0 through 7 of a modular disk subsystem outside of NonStop S-series system enclosures. The disk subsystem connects to the server through a ServerNet/DA Adapter (SNDA). 6760 ServerNet device adapter (ServerNet/DA). See ServerNet device adapter (ServerNet/DA). ACL. See automatic cartridge loader (ACL). action. An operation that can be performed on a selected resource. adapter. See ServerNet adapter. ADAPTER object type.
block Glossary block. A grouping of one or more system enclosures that an HP NonStop S-series system recognizes and supports as one unit. A block can consist of either one processor enclosure, one I/O enclosure, or one processor enclosure with one or more I/O enclosures attached. boot. A synonym for load. Load is the preferred term used in this and other HP NonStop S-series system manuals. See load. cache (cache memory).
Configuration Utility Program (COUP) Glossary Configuration Utility Program (COUP). A utility used in D-series and earlier RVUs to make online changes to the configuration of devices and controllers. COUP is part of the Dynamic System Configuration (DSC) facility. In G-series RVUs, COUP functions are performed by the Subsystem Control Facility (SCF). controller. See ServerNet addressable controller (SAC). COUP. See Configuration Utility Program (COUP). current configuration file. See configuration file.
enclosure Glossary enclosure. Similar to a cabinet in HP NonStop K-series systems. An enclosure can contain components of a system or a peripheral. Base enclosures are placed on the floor and can have other enclosures stacked on top of them. Stackable enclosures can be placed on top of other enclosures. See also system enclosure and peripheral enclosure. enclosure interleaving. On HP NonStop S-series systems, configuring a mirrored disk volume to use two separate system enclosures.
Fibre Channel switch (FC switch) Glossary Fibre Channel switch (FC switch). Networking hardware that can connect an Enterprise Storage System and a NonStop server. This switch allows any-to-any connectivity. file name. A unique name for a file. File names for disk files normally have at least two parts (the disk name and the file name); an example of a file name on a PC is B:MYFILE.
HP Tandem Advanced Command Language (TACL) Glossary HP Tandem Advanced Command Language (TACL). The user interface to the HP NonStop operating system. The TACL product is both a command interpreter and a command language. Users can write TACL programs that perform complex tasks simply or provide a consistent user interface across independently programmed applications. input/output process (IOP).
I/O multifunction (IOMF) 2 CRU Glossary I/O multifunction (IOMF) 2 CRU. A HP NonStop S-series customer-replaceable unit (CRU) that connects an I/O enclosure to a processor enclosure through a ServerNet cable and supplies power to the components within the IOMF 2 CRU as well as redundantly to the disk drives, SCSI terminators, and ServerNet adapters in that enclosure.
modular ServerNet expansion board (MSEB) Glossary of data written to the primary drive is also written to the mirror drive; if the primary drive fails, the mirror drive can continue operations. See also volume. modular ServerNet expansion board (MSEB). A ServerNet expansion board (SEB) that uses plug-in cards (PICs) to provide a choice of connection media for routing ServerNet packets. See also ServerNet expansion board (SEB). module.
operator message Glossary operator message. A message, intended for an operator, that describes a significant event on a HP NonStop S-series system. An operator message is the displayed-text form of an Event Management Service (EMS) event message. See also event message. OSM. Stands for HP Open System Management (OSM) Interface. Replaces TSM as the system management tool of choice for NonStop servers. Provides the same functionality as TSM while overcoming limitations of TSM.
processor enclosure Glossary but a HP NonStop system has multiple cooperating processors rather than a single CPU. (2) One or more computer chips, typically mounted on a logic board, that are designed to perform data processing or to manage a particular aspect of computer operations. processor enclosure.
ServerNet adapter Glossary the group of the owner of the subsystem. The owner of a subsystem is the user who started that subsystem (or any user whose application ID is the same as the server ID—the result of a PROGID option that requires super-group access). Contrast with nonsensitive command. ServerNet adapter. A component that connects peripheral devices to the rest of the system through a ServerNet bus interface (SBI).
state Glossary state. In SCF, one of the generally defined possible conditions of an object with respect to the management of that object. Examples of states are DEFINED, STARTED, and STOPPED. Storage Management Foundation (SMF). A subsystem used by the storage subsystem that facilitates automation of storage management tasks by providing locationindependent naming, storage pools, and virtual disks on HP NonStop S-series systems. storage subsystem.
subsystem manager Glossary SCP also processes a few commands itself. It provides security features, version compatibility, support for tracing, and support for applications implemented as process pairs. subsystem manager. A process that performs configuration and management functions for a Subsystem Control Facility (SCF) subsystem. subvolume. A group of related files stored on a disk; all the files have the same volume and subvolume name, but each file has a unique file identifier. summary report.
TACL Glossary TACL. See HP Tandem Advanced Command Language (TACL). tape drive. A device that moves magnetic tape past magnetic read/write heads, which read data from or write data to the tape. TAPE object type. The Subsystem Control Facility (SCF) object type for all tape drives attached to your system. TB. See terabyte (TB). terabyte (TB). A unit of measurement equal to 1,099,511,627,776 bytes (1024 gigabytes). See also gigabyte (GB), kilobyte (KB), and megabyte (MB). TMF.
WWN zone Glossary WWN zone. Similar to Ethernet virtual LANs (VLANs), WWN zones organize the cabling and interactions between components in a storage and server system. X fabric. The X side of the internal or external ServerNet fabrics. See also fabric. Y fabric. The Y side of the internal or external ServerNet fabrics. See also fabric. $ZCNF. The name of the configuration utility process. $ZZSTO. The name of the storage subsystem manager process.
$ZZSTO Glossary SCF Reference Manual for the Storage Subsystem—529937-008 Glossary -16
Index Numbers 45xx disks ADD DISK example 6-19 defined 6-2 mirroring attributes 6-13 A ABANDON attribute, REPLACE ADAPTER command 14-101 ABORT DISK command prevents a disk path from starting 7-12 puts disk in HARDDOWN substate 2-5 stops a magnetic disk 7-10 ABORT MON command 14-6 ABORT POOL command 14-6 Adapter See also ADAPTER object configuring and managing 11-1/11-21 ADAPTER object defined 2-3 DELETE command for 14-75 INFO command for 14-80 object name for 2-1 STATUS command for 14-118 SWITCH command fo
B Index Altering magnetic disk attributes 6-22/6-23 Open SCSI device attributes 12-9 profile attributes 6-10 SMF master process attributes 4-5 storage pool attributes 9-9 system configuration, safely 1-3 tape drive attributes 13-11 virtual disk attributes 10-10 ALTNAME attribute ALTER DISK command for magnetic disks 6-22, 14-12 not copied from the LIKE object 14-48 ANTCAPACITY attribute ALTER DISK command for virtual disks 14-12 ANTLOCATION attribute ADD DISK command for virtual disks 14-12 when deleting
C Index BACKUPCPU attribute (continued) ALTER MON command 14-53 ALTER POOL command 14-55 ALTER SCSI command 14-60 ALTER TAPE command 14-66 BACKUPDEVICEID attribute ALTER DISK command for magnetic disks 14-14 cannot be altered 6-22 not copied from the LIKE object 14-48 BACKUPLOCATION attribute ADD SCSI command 14-40 ALTER DISK command for magnetic disks 14-15 ALTER SCSI command 14-60 not copied from the LIKE object 14-49 BACKUPPORTNAME ALTER SCSI command 14-60 BACKUPPORTNAME attribute ALTER DISK command fo
D Index Command file behavior of SCF commands in 14-3 helps change configuration safely 1-3 using OBEYFORM results in 1-3 Command timeouts 14-3 COMPRESSION attribute ADD TAPE command 14-43 ALTER TAPE command 14-66 CONFIG attribute INFO DISK command 14-81 INFO DISK display 5-5 Configuration information See INFO command Configuration state in INFO DISK report 10-9 Configuration state of virtual disk in INFO DISK report 10-4 in STATUS DISK report 10-9 Configuring See Adding CONFIG-ERROR substate, defined 2-5
E Index DETAIL attribute INFO command 14-80 STATUS command 14-118 VERSION command 14-140 Device states and substates See States and substates, SCF DEVICEID attribute ADD TAPE command 14-44 ALTER TAPE command 14-66 CONTROL SAC command 14-73 DEVICEID attribute, REPLACE SAC command 14-102 Disk cache, reconfiguring 6-23 Disk load balancing 8-1/8-18 Disk naming conventions, set by NAMEMASK attribute 14-23 DISK object ABORT command for 14-5 ADD command for 14-8 ALLOWOPENS command for 14-46 ALTER command for 14-
F Index Error messages B-1/B-74 collecting information about B-1 Guardian file system B-2 positive error numbers B-2/B-74 ESS disks ADD DISK example 6-19 defined 6-2 special considerations 6-4 Event Management Service (EMS) message See EMS message EXCLUDE command, PUP C-2 EXTENTINTERVAL attribute ADD POOL command 14-34 ALTER POOL command 14-56 EXTENTTHRESHOLD attribute ADD POOL command 14-35 ALTER POOL command 14-56 External disk, cannot be automatically configured 6-6 FORCED attribute ABORT DISK command
I Index HIGHPIN attribute (continued) ALTER MON command 14-53 ALTER POOL command 14-56 ALTER SCSI command 14-61 ALTER TAPE command 14-67 I IGNOREINCONSISTENCY attribute ALTER DISK command for magnetic disks 14-19 DELETE DISK command 14-76 DELETE POOL command 14-78 INACCESSIBLE substate, defined 2-6 INCLUDE command, PUP C-2 INFO ADAPTER command IOMF display example 11-5 PMF display example 11-3 SNDA display example 11-6 INFO DISK command magnetic disk display examples 5-3/5-20 syntax 14-81 virtual disk di
M Index LIKE attribute ADD DISK command 14-8 ADD POOL command 14-33 ADD PROFILE command 14-37 ADD SCSI command 14-39 ADD TAPE command 14-42 adding a magnetic disk 6-20 adding a storage pool 9-6 adding a tape drive 13-9 adding a virtual disk 10-8 adding an Open SCSI device 12-8 ALTER DISK command 14-48 ALTER POOL command 14-54 ALTER SCSI command 14-59 ALTER TAPE command 14-65 compared to OBEYFORM attribute of INFO command 1-4 LISTBAD command, PUP C-3 LISTCACHE command, PUP C-3 LISTCACHE, INIT command, PUP
M Index MAGNETIC attribute ADD POOL command 14-35 ALTER POOL command 14-56 Magnetic disks adding 6-18 allowing file opens 7-23 altering 6-22 configuration information for 5-3/5-20 configuring and managing 6-1/D-3 correcting doubly allocated file extents 7-17 deleting 6-34 initializing 6-33 load balancing 8-2/8-14 preventing file opens 7-22 renaming 6-26/6-30 replacing the bootstrap program 7-19 resetting 7-11 resolving disk-naming conflicts 6-27 sparing a defective sector 7-14 starting 7-3 status informat
N Index MIRRORLOCATION attribute ADD DISK command for magnetic disks 14-22 not copied from the LIKE object 14-49 MIRRORLUN attribute ALTER DISK command for magnetic disks 14-22 not copied from the LIKE object 14-49 MIRRORPORTNAME attribute ALTER DISK command for magnetic disks 14-22 not copied from the LIKE object 14-49 MIRRORPORTNAME disk attribute 14-22 MIRRORSAC attribute ALTER DISK command for magnetic disks 14-23 cannot be altered 6-22 not copied from the LIKE object 14-49 MODE attribute ADD MON comm
P Index OBEYFORM attribute (continued) to add SMF master process 4-4 to create command file 1-3 Object name template 2-1 Object names 2-1 wild-card characters in 2-1 Object states and substates See States and substates, SCF Object types 2-3 ADAPTER 2-3 DISK 2-4 MON 2-7 POOL 2-8 PROFILE 2-8 SCSI 2-10 SUBSYS 2-11 TAPE 2-12 Online disk remirroring 6-15 Online software replacement (OSR) state in STATUS DETAIL report 5-28 Online upgrade of a mirrored volume D-2 Open SCSI device adding 12-8 altering 12-9 changi
P Index POOL object (continued) states and substates 2-8 STATUS command for 14-122 STOP command for 14-132 Pool, storage adapter deletion impact on 11-21 adding 9-6 adding a magnetic disk to 9-8 altering 9-9 configuration information for 9-2/9-4 defined 9-1 deleting 9-10 removing a magnetic disk from 9-8 resetting 9-13 starting 9-12 status information for 9-5 swapping processors for 9-13 Port Name Fibre Channel tape 13-3 Open SCSI Fibre Channel device 12-6 Port Name, disks 5-8 PORTNAME attribute ALTER TAP
Q Index PRIMARYSAC attribute ADD SCSI command 14-41 ALTER DISK command for magnetic disks 14-26 ALTER SCSI command 14-61 not copied from the LIKE object 14-49 Processor configuration for a disk 1-6 load balancing See Load balancing Profile See also PROFILE object adding a custom profile 6-9 altering 6-10 configuration information for 5-11/5-13 configuring and managing 6-9/6-11 defined 6-9 deleting 6-11 used with adding a disk 6-7 PROFILE object 2-8 ADD command for 14-37 ALTER command for 14-58 DELETE comm
S Index Renaming a magnetic disk 6-26/6-30 REPLACE ADAPTER command syntax 14-101 REPLACE SAC command syntax 14-102 REPLACEBOOT attribute, CONTROL DISK command 7-19, 14-71 REPLACEBOOT command, PUP C-4 Replacement, CRU 11-23, 14-96, 14-137 Replacing bootstrap program 7-19 Open SCSI device D-2 tape drive D-1 RESET attribute, STATS command 14-115, 14-116 resets counters in STATS display 5-15, 6-25 RESET DISK command for a magnetic disk 7-11 for a virtual disk 4-8, 10-13 recovers disks from SERVICING state 2-6
S Index SCF (continued) object names defined 2-1 object types 2-1 PUP equivalent commands C-2 states and substates See States and substates, SCF SCSI device See also SCSI object See Open SCSI device SCSI object 2-10 See also Open SCSI device ADD command for 14-38 ALTER command for 14-59 DELETE command for 14-79 INFO command for 14-86 object name 2-10 PRIMARY command for 14-95 RESET command for 14-106 START command for 14-112 states and substates 2-11 STATUS command for 14-127 STOP command for 14-133 SWITC
S Index SPARE attribute, CONTROL DISK command 14-72 SPARE command, PUP C-4 Spare Tracks Table entries displayed by INFO, BAD command 5-19 Sparing a defective sector procedure for 7-14/7-16 using SPARE attribute of CONTROL DISK command 14-72 SPECIAL attribute START DISK command 14-110 used when changing the label 6-14 START MON command 14-111 START POOL command 14-111 SPECIAL substate DISK object changed by RESET command 7-3 defined 2-5 recovering from 2-6 resetting a virtual disk 10-13 used when changing
S Index STATUS DISK command magnetic disk display examples 5-21/5-29 virtual disk display examples 10-6/10-7 STATUS MON command display examples 4-3/4-4 STATUS POOL command display examples 9-5 STATUS SCSI command configuration display examples 12-6/12-7 display examples 12-6/12-7 STATUS SUBSYS command display example 3-2 STATUS TAPE command display examples 13-5/13-8 STOP DEVICE command, PUP C-4 STOP DISK command stops a magnetic disk 7-9 stops a virtual disk 10-13 STOP MON command stops SMF master proce
T Index Swapping processors for disk 7-24/7-26 for Open SCSI device 12-12 for pool process 9-13 for SMF master process 4-8 for virtual disk 10-13 SWITCH ADAPTER command 11-23 SWITCH DISK command 14-138 changes active data path for disk 7-27 considerations for 7-27 SWITCH SCSI command changes the active data path for an Open SCSI device 12-11 System configuration database 1-2 System disk alternate location 6-5 considerations for 6-5 do not use STOPOPENS command on 7-22, 14-135 T Tape drive See also TAPE o
V Index V Virtual disk 10-1/10-13 adding 10-7 altering 10-10 configuration information for 10-3/10-6 defined 10-1 deleting 10-11 relation to physical disks 10-2 resetting 10-13 starting 10-12 status information for 10-6/10-7 stopping 10-13 swapping processors for 10-13 VOLNAME attribute, ALTER DISK command for magnetic disks 14-30 $SYSTEM.ZSYSCONF.
Special Characters Index SCF Reference Manual for the Storage Subsystem—529937-008 Index -20
