SCF Reference Manual for the Storage Subsystem HP Part Number: 529937-022 Published: February 2014 Edition: J06.03 and subsequent J-series RVUs, H06.05 and subsequent H-series RVUs, G06.28 and subsequent G-series RVUs.
© Copyright 2010, 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents About This Document...................................................................................12 Supported Release Version Updates (RVUs)................................................................................12 Intended Audience..................................................................................................................12 New and Changed Information................................................................................................
The SUBSYS Object............................................................................................................38 The TAPE Object................................................................................................................39 3 Using the Storage Subsystem Manager.......................................................40 Displaying Information............................................................................................................
Creating a Custom Profile...................................................................................................75 Adding a Similar Custom Profile Using the OBEYFORM Attribute.............................................75 Altering a Profile................................................................................................................76 Deleting a Custom Profile....................................................................................................
Resetting a Disk....................................................................................................................103 Considerations for RESET DISK..........................................................................................103 Resetting One Disk...........................................................................................................103 Resetting a Group of Disks................................................................................................
Adding a Storage Pool.....................................................................................................137 Adding a Disk to a Storage Pool........................................................................................138 Removing a Disk From a Storage Pool.................................................................................138 Altering Storage Pool Attribute Values.................................................................................
Managing an Open SCSI Device............................................................................................176 Resetting an Open SCSI Device.........................................................................................176 Starting an Open SCSI Device...........................................................................................177 Stopping an Open SCSI Device.........................................................................................
DELETE Command................................................................................................................248 DELETE ADAPTER Command.............................................................................................248 DELETE DISK Command....................................................................................................248 DELETE MON Command..................................................................................................
STATUS ADAPTER Command.............................................................................................279 STATUS CLIM Command...................................................................................................280 STATUS DISK Command...................................................................................................282 STATUS MON Command..................................................................................................284 STATUS POOL Command..........
Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 .....................................................................................................................................13 CLIM Object States..........................................................................................................33 Object States and Substates of Disks..................................................................................34 Virtual Disk Object States................................................................
About This Document 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.
New and Changed Information in the August 2013 Edition Table 1 Chapter Change Chapter 5: “Displaying Information About Disk Drives” (page 48) • Added statement that the FastBulkWrite attribute affects all 512-byte-sector disks to “Displaying Disk Configuration Information” (page 50) and “Displaying Profile Attributes” (page 54) • Updated sample display and explanation of fields in “Displaying Disk Configuration Information” (page 50), “Displaying Disk Cache Configuration Information” (page 59), and “Disp
New and Changed Information in the August 2012 Edition Chapter Change Chapter 6: “Configuring Disks” (page 70) • Added Caution about partitioning SAS drives under “Partitioning HDDs and SSDs” (page 92). Chapter 13: “Configuring and Managing Tape Drives” (page 179) • Added the LTO-5 tape object under “Managing Encrypted Tape Drives” (page 189). Chapter 14: “Storage Subsystem Commands” (page 190) • Changed AUDITTRAILBUFFER description under “Attribute Descriptions for Disk Commands” (page 198).
New and Changed Information in the August 2011 Edition The following information was added or changed in this edition of the manual: Chapter Change Chapter 5: “Displaying Information About Disk Drives” (page 48) • Added paragraph to the beginning of this chapter: Effective with the H06.23/J06.12 RVU, Solid State Drives (SSDs) are supported in addition to Hard Disk Drives (HDDs). SSDs are configured and displayed in the same manner as HDDs.
Chapter Change “INFO DISK Command” (page 254) “INFO CLIM Command” (page 253) “STATUS CLIM Command” (page 280) • Under the ADD DISK command, changed heading from Disk Attribute Descriptions to “Attribute Descriptions for Disk Commands” (page 198), and added statements under disk commands referring to this section. • Added information to the WRITECACHE attribute under “Attribute Descriptions for Disk Commands” (page 198).
Chapter Change • Under Section : “Upgrading a Mirrored Volume Online” (page 363), added this note: You can only use a smaller replacement disk if it is able to accommodate the largest used sector address. Please note that because of fragmentation, the largest used sector address can be much larger than the actual disk space used. Appendix, SCF Command Summary • Deleted this appendix from the manual.
Chapter Change ◦ ENCRYPTRATE ◦ KEYALGORITHM ◦ KEYSIZE ◦ NEWENCRYPTKEY • “ALTER DISK Command” (page 228) to add these attributes: ◦ CLEARENCRYPTKEY ◦ ENCRYPTPRIORITY ◦ ENCRYPTRATE • “ALTER TAPE Command” (page 241) to add these attributes: ◦ KEYGENPOLICY ◦ NEWENCRYPTKEY • “INITIALIZE DISK Command” (page 260) to add these attributes: ◦ CLEARENCRYPTKEY ◦ KEYALGORITHM ◦ KEYSIZE ◦ NEWENCRYPTKEY • “STATUS CLIM Command” (page 280) • “STATUS DISK Command” (page 282) • “STATUS TAPE Comm
New and Changed Information in the August 2008 edition The following information was added or changed in this release of the manual: Chapter Change “Storage Subsystem Objects” (page 30) Added “The CLIM Object” (page 32) “Displaying Information About Disk Drives” (page 48) “Configuring Disks” (page 70) • Updated: ◦ “Displaying Disk Configuration Information” (page 50) to add WRITECACHE ◦ “Example of an INFO PROFILE Report” (page 54) to add WRITECACHE • Added “Write Caching” (page 94) • Updated “Cons
Chapter 3: Using the Storage Subsystem Manager Describes the storage subsystem manager ($ZZSTO) in detail. It describes how to display information about it and make changes to its configuration. Chapter 4: Configuring and Managing the SMF Master Process Describes the SMF master process ($ZSMS) in detail. It describes how to display information about the process, and how to add, alter, and delete a master process. It also describes how to start, stop, reset, and switch a master process.
Appendix B: Upgrade and Replacement Procedures Describes upgrade and replacement procedures for tape drives, Open SCSI devices, and upgrading a mirrored drive. Glossary : Glossary Defines terms used in this manual. Notation Conventions General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required.
FC [ num ] [ -num] [ text] K [ X | D ] address { } Braces A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic Text Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up.
P=%p-register E=%e-register Related Information For a listing of manuals describing NonStop NS-series and NonStop S-series servers, see the NonStop NS-Series Planning Guide , the NonStop S-Series Planning and Configuration Guide, and the NonStop BladeSystem Planning Guide.
1 Introduction to the Storage Subsystem The storage subsystem allows you to use SCF to configure and manage storage devices online.
object is restarted and persist through processor and system loads (unless you load the system with a new configuration file). The storage subsystem includes features to manage both SCSI and Fibre Channel devices. The Fibre Channel features are collectively called the FCS Manager. FCS Manager assigns Fibre Channel loops for Fibre Channel disk modules (FCDMs) to the FCS monitors. FCS Manager also passes OSM requests to the FCS Monitors.
Object Type Description Chapter SUBSYS The $ZZSTO storage subsystem manager process “Using the Storage Subsystem Manager” (page 40) TAPE Tape drive “Configuring and Managing Tape Drives” (page 179) Configuration Overview To Make Configuration Changes Safely 1. 2. 3. 4. Create a command file containing the SCF commands. Save the current $SYSTEM.ZSYSCONF.CONFIG file using the SCF SAVE command described in the SCF Reference Manual for G-Series RVUs.
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.
The primary and backup paths go to the primary device. A mirrored device, such as a mirrored disk, can be accessed through an additional two paths: a mirror path and a mirror-backup path. The paths are set by these attributes of the ADD command when the device is configured: MIRRORLOCATION MBACKUPLOCATION MIRRORSAC MBACKUPSAC The primary and backup paths go to the primary device. The mirror and mirror-backup paths go the mirror device.
2 Storage Subsystem Objects This chapter describes how storage subsystem components are organized for management through the SCF interface. It contains these sections: • “Object Names” (page 30) • “Object States and Substates” (page 31) • “Object Attributes” (page 31) • “Object Types for the Storage Subsystem” (page 31) 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.
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. For example, to start disks named $DATA00, $DATA01, and so on: -> START DISK $DATA0? You can use wild-card characters in any combination.
Object Type Definition “The SUBSYS Object” (page 38) The $ZZSTO storage subsystem manager process “The TAPE Object” (page 39) A tape drive When issuing SCF commands, you need not specify the object type of the device if either of these conditions exists: • You have fully specified the object name (no wild-card characters), and the device exists. • You have already issued an SCF ASSUME command for the object type.
$ZZSTO.clim-name $ZZSTO is the storage subsystem manager. clim-name is the user-defined CLIM name. The CLIM object in the CIP subsystem has this format: $ZZCIP.clim-name $ZZCIP is the cluster I/O protocol subsystem manager. clim-name is the user-defined CLIM name. Wild-card characters are supported. Examples $ZZSTO.S1002541 CLIM Object States The object state of a CLIM provides current status information about the disk or a path to that disk.
Wild-card characters are supported. Examples $DATA00-P $DATA00-M $DATA00-B $DATA00-MB $DATA03 Object States and Substates of Disks The object state and substate of a disk provide current status information about the disk or a path to that disk. Table 3 Object States and Substates of Disks State Substate Caused By Description SERVICING -- -- The disk volume or disk path is in transition and is unavailable due to a pending service operation.
Recovering From Various SCF Object States and Substates This table describes how to prepare a disk for restarting. For all situations except CONFIG-ERROR, the RESET command puts a disk into the STOPPED state, substate DOWN, ready for a START command. SCF State SCF Substate Description Recovery SERVICING SPECIAL The disk is reserved for service. Issue the RESET command. SERVICING TEST The disk is reserved for service. Issue the RESET command.
MON Object States The object state of a MON object provides current status information about the SMF master process Table 5 MON Object States State Substate Description STARTED The SMF master process is available. STOPPED The SMF master process is not available. SERVICING SPECIAL The SMF master process is reserved by OSM, TSM, SCF, or some other privileged process. The POOL Object The POOL object represents a storage pool, which is a collection of disk volumes, all on the same system.
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.
#type is the adapter type, for example FCSA. #SAC-n is the number of the SAC on the adapter. 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. Example $ZZSTO.#FCSA.SAC-2.GRP-111.MOD-2.SLOT-5 The SCSI Object The SCSI object represents an Open SCSI device, which is a storage device that uses the small computer system interface (SCSI) to connect the device to the system.
storage objects in the storage subsystem. For more information, see “Using the Storage Subsystem Manager” (page 40). The SUBSYS object has this format: $ZZSTO $ZZSTO is the storage subsystem manager process. 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“Configuring and Managing Tape Drives” (page 179) .
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. For information about this object, see “The SUBSYS Object” (page 38).
EncryptionLicense Shows whether encryption license is valid or invalid. UPS Shows whether the uninterruptible power supply option is on or off. Using the PRIMARY SUBSYS Command The PRIMARY SUBSYS command replaces a series of PRIMARY commands for individual IOPs in the topology branch. The PRIMARY SUBSYS command does not start any processes. At the completion of the command, the PRIMARY SUBSYS command returns a list of the IOPs that did not move the primary IOP.
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. For a description of this object, see “The MON Object” (page 35) and “MON Object States” (page 36).
PrimaryCPU The processor number of the primary SMF master process. Program The object file name of the SMF master process. Example of a Detailed INFO MON Report -> INFO MON $ZSMS, DETAIL STORAGE - Detailed Info MON \COMM.$ZSMS *BackupCPU............................. CatalogLocation....................... *HighPin............................... *Mode.................................. *PrimaryCPU............................ *Program............................... 4 $VIRCFG.ZSMSCAT0 OFF QUIET 5 $SYSTEM.
State The object state of the SMF master process. Primary PID Backup PID The processor number and PIN of the current primary and backup SMF master processes. Type The device type. The SMF master process is always type 52. Subtype The device subtype. The SMF master process is always subtype 0. 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.
• Enter the log file contents either by copying and pasting into an SCF command line or by using the log file as a command file. Altering the Values of the SMF Master Process Attributes The “ALTER MON Command” (page 232) changes attributes of the SMF master process in the system configuration database. Considerations for ALTER MON CAUTION: Using wild-card characters can affect the MON objects of other subsystems (QIO, for example).
1. Before removing an SMF master process from the system configuration database, verify that: • The MON process is stopped. • TMF is running. • The CATALOGLOCATION volume for the SMF master process is started and enabled by TMF. • Stop the SMF master process: -> STOP $ZSMS The SMF master process finishes any current activity before entering the STOPPED state. 2. Delete the SMF master process: -> DELETE MON $ZSMS 3.
Resetting the SMF Master Process The “RESET MON Command” (page 271) 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 Disk Drives This chapter describes displaying information about disk drives. For a description of the different types of disks that the storage subsystem supports, see “Types of Disks” (page 70). Effective with the H06.23/J06.12 RVU, Solid State Drives (SSDs) are supported in addition to Hard Disk Drives (HDDs). SSDs are configured and displayed in the same manner as HDDs.
• “Displaying Disk Configuration Information” (page 50) • “Displaying Disk Label Information” (page 52) • “Displaying Profile Attributes” (page 54) • “Displaying Information about Partitioned Disks” (page 56) • “Displaying Information about Encrypted Disks” (page 58) To display a report about all disks on the system: -> INFO DISK $* , SUB MAGNETIC An INFO Report for a Disk -> INFO $AUDIT STORAGE - Info Magnetic DISK configuration \COMM.
The INFO DETAIL,and INFO CONFIG reports start with this display. Explanation of Fields — INFO SYSTEM Report * Indicates an attribute whose value you can change by using the ALTER DISK command. BackupCpu The processor number of the backup disk process. HighPin Shows whether the disk process can run at a high PIN (ON) or must run at a low PIN (OFF). The PIN is the process identification number. PrimaryCpu The processor number of the primary disk process.
Location (Group,Module,Slot).......... (1,1,12) SAC Name.............................. $ZZSTO.#PMF.SAC-1.GRP-1.MOD-1.SLOT-55 SAC Number............................ 1 Mirror Backup Path Information: Adapter............................... Disk Device ID / Port Name............ Disk Device LUN....................... Location (Group,Module,Slot).......... SAC Name.............................. SAC Number............................ $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50 0 0 (1,1,12) $ZZSTO.#PMF.SAC-1.GRP-1.MOD-1.
PhysvolSelect (Physical disks only) shows whether a virtual disk process is allowed to consider the physical volume for file placement. Pool Shows which storage pool process the disk is associated with. ProtectDirectory Shows the tape of protection to use for the disk volume directory: full-block checking (CHECKPOINT), serial writes (SERIAL), or disabled (OFF). RecoveryTimeout The number of seconds that the NonStop storage controller must wait for the device to respond to a recovery I/O.
Volume Label Verifier................ Volume Label Version................. Operating System Last Mounted Under.. Volume Label Last Written............ Disk Subtype......................... 0. 1. 2. 3. 4. 5. 6. 10. 11. 12. Section Name -------------------Spare Tracks Table Boot Free Space Table Directory Label Unused Undo Pool Pool-LSA Free Space Table-LSA Boot-LSA Address ------------000000.003000 000106.024000 002054.014000 000000.110000 000000.000000 000000.120000 000000.000000 000000.000010 000002.
Explanation of Fields Volume Label Last Written The date and time when the volume label was last written to the volume. Disk Subtype The subtype of the disk on which the specified volume is located. This value is retrieved from the device. Section Name table The section name, address, length, version, and parameter for each section that resides on the disk volume label. Displaying Profile Attributes The “INFO PROFILE Command” (page 258) displays configured information about a disk profile.
AutoLabel Shows whether the storage subsystem manager should automatically write a label on an unlabeled disk that is inserted into a slot. AutoRevive Shows whether the storage subsystem manager automatically starts a revive operation on an internal SCSI or M8xxx disk that is inserted into a slot. AutoSelect (Physical disks only) shows whether a virtual disk process is allowed to automatically consider this physical volume when making file placement decisions.
ProtectDirectory The type of protection to use for the disk volume directory: full-block checking (CHECKPOINT), serial writes (SERIAL), or disabled (OFF). RecoveryTimeout The number of seconds that the NonStop storage controller must wait for the device to respond to a recovery I/O. This attribute only applies to ESS (Enterprise Storage) disks. ReviveBlocks The number of revive blocks of disk data to be copied during each copy interval when the disk is being revived.
None None 3 4 30 40 LUN Usage Information: Unpartitioned Size (GB)... 40 Total Size (GB)........... 140 Use the INFO DISK $disk-name, [CONFIG | DETAIL] command to display the partition number (if it exists) for each path. If the partition number is not displayed, the disk LDEV path is configured to a disk that is not partitioned. Here is an example of the INFO DISK, CONFIG command: > INFO DISK $SSD1, CONFIG STORAGE - Detailed Info Magnetic DISK \NBSTS01.
LUN................................... 201 PARTITION............................. 2 Mirror Backup Path Information: CLIM.................................. S1002531 LUN................................... 201 PARTITION............................. 2 Use the INFO CLIM $ZZSTO.clim-name, DETAIL command to display the partition number (if it exists) for each path. A disk LDEV path that is not configured to a partition will not display a partition number. > INFO CLIM $ZZSTO.
ChangeStatus..... No change in progress Mirror Backup path KeyName.......... VGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG_N_YYYYMMDDHHMMSS, VGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG_N_YYYYMMDDHHMMSS KeyAlgorithm..... XTS-AES KeySize.......... 256 ChangeStatus..... No change in progress Display information for a one-path disk with a change aborted by I/O error: STORAGE - Status DISK $DATA04, ENCRYPTION Primary path KeyName..........
Cn The number of blocks that either were requested by an ALTER DISK, CACHE configuration command or set by default for each block size. A value of -1 indicates that no default value is set for the number of blocks required. Al The number of blocks allocated to cache for each block size. Bytes Allocated To Cache The total memory allocated to cache. This value equals the number of blocks allocated for a particular block size, multiplied by the block size, and totaled for all block sizes.
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). Cache Reads The percentage of cache calls that the disk process made for user read requests. (When added together, the percentages displayed for Cache Reads and Cache Writes equal 100 percent.
Condition What to Do Audit Forces is high (indicates insufficient cache memory and tends to take resources from other processes). If the processor that controls the disk you are analyzing has enough available physical memory, use the ALTER DISK, CACHE command to allocate more memory to the cache (increase the number of blocks) for that cache block size. Cache Faults is not close to zero. Add more memory or reconfigure cache to use less memory.
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.$DATA01 Bad Sectors Information $DATA01 Primary: No bad sectors found. Bad Sectors Information $DATA01 Mirror: Logical Sector Address %H0000795C File Name Date Detected SEPTEMBER 22, 2000 15:25:12 File Address \GANESAN.$DATA01.DLSYS42X.
The defect log contains 1 defects of which 1 were displayed. Explanation of Fields — Defect Log Information Physical Sector Address List of physical sector addresses of defective sectors on the disk. The addresses are displayed as 8-digit hexadecimal numbers. Source Specifies the defect map that lists the defect.
State The current SCF state of the disk path. For an explanation, see “Object States and Substates of Disks” (page 34). Substate The current SCF substate of the disk path. Primary PID Backup PID The processor number and PIN of the primary and backup disk processes. Example 3: Displaying the Status of a Nonmirrored Disk To display the status of the nonmirrored disk $DATA11: -> STATUS $DATA11 STORAGE - Status DISK \COMM.
For an example of the output for the STATUS DISK $PART01, CONSISTENCY command, refer to “STATUS DISK Examples For Physical Disks” (page 283). Example of STATUS DISK Detailed Report for Disks To display detailed status of $SYSTEM: -> STATUS $SYSTEM, DETAIL STORAGE - Detailed Status DISK \COMM.
The values of Primary Drive Type and Mirror Drive Type must be the same except when the disks are being upgraded to a larger capacity. For information about mismatching disk types while upgrading, see “Swapping Processors for a Disk” (page 109). Mirror Drive Type The product number of the mirror disk retrieved from the device. Physical Record Size The size of the physical records on the disk retrieved from the device. Priority The execution priority of the disk process.
Pool Information: Autoselect............ ON Physvolselect......... ON Pool..................... $POOL01 Autoselect Shows whether Autoselect attribute of the disk is ON or OFF. When on, the physical volume is automatically considered for file placement when the placement decision is left up to the virtual disk process. Pool The name of the storage pool that the disk is in. Physvolselect Shows whether the Physvolselect attribute of the disk is set ON or OFF.
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. If the alternate disk process replaced the configured disk process but was automatically abandoned, the configured object-file name is displayed in this field.
6 Configuring Disks This chapter describes configuring disks. Disks share the object type of DISK with virtual disks. For information about disks and their states, see “The DISK Object” (page 33) and “Object States and Substates of Disks” (page 34). For commands that affect disks, see “Storage Subsystem Commands” (page 190). For configuration information, see “Configuring and Managing Virtual Disks” (page 143) . For information about disk load balancing, see “Disk Load Balancing” (page 118).
Type Description M8xxx Model M8xxx disks that reside in slots 1 through 14 of a Fibre Channel disk module (FCDM) connected to FCSAs in an IOAM enclosure. ESS Disks within an Enterprise Storage System. CLIM-attached disks Disks that attach to the system through CLIMs, such as Serial Attached SCSI (SAS) disk drives in a SAS disk enclosure. Configuring Paths for Different Disk Types The values you specify when configuring a disk vary depending on the type of disk and the NonStop server model.
• The primary disk and mirror disk of a mirrored pair of M8xxx disks must be in different FCDMs, connected to a different pair of Fibre Channel loops. • On NonStop S-series servers the system disk and its mirror cannot be M8xxx Fibre Channel disks. • During normal operations, a disk should be mirrored with another disk of the same type. If you revive an IOMF disk to a newer type of disk, the system will use a migratory revive that will down the source drive after the revive is complete.
• On NonStop S-series servers, the system disk and its mirror cannot be M8xxxFibre Channel disks. • These attributes cannot be changed: ◦ The system disk always runs with FSTCACHING ON. ◦ You cannot decrease these attribute values online because the disk must be stopped to decrease them. The configured value will can decreased, but the IOP will continue to run with the original, larger value until it is stopped and restarted.
-> ALTER $ZZSTO, AUTOCONFIG ON The storage subsystem looks for a custom profile (see “Creating a Custom Profile” (page 75)) for the enclosure. If no custom profile exists, the storage subsystem uses the default profile (see “Example of an INFO PROFILE Report” (page 54)) to configure the disk. To make internal disk configuration plug and play, enable these attributes: -> ALTER $ZZSTO, AUTOCONFIG ON, AUTOREVIVE ON, AUTOSTART ON 3. 4. 5.
You might want to use this configuration scheme: • Configure your system to have disks start automatically (by setting AUTOSTART ON for the subsystem). • Make exceptions where you want some disks to not start automatically (by setting those disks to AUTOSTART OFF). Configuring Custom Profiles You can automatically configure internal disks by using a custom or default set of attributes, called a profile.. This set of attributes has the object type of PROFILE.
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.
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.
For a partition capacity upgrade, you can temporarily mirror partitions of different sizes. If it is desired to keep both mirrored disks of different sizes up, the SCF CAPACITYMISMATCH option must be turned ON for the LDEV. Normally mirroring partitions of different sizes is used temporarily as part of an online disk capacity upgrade operation. To simplify disk replacement, a mirrored disk partition must be on two physical disks that are partitioned in the same configuration.
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” (page 89). 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.
Considerations for ALTER DISK, MIRRORLOCATION and Online Disk Remirroring • You cannot specify the attribute MIRRORLOCATION and the attribute SWAPMIRROR in the same ALTER DISK command. • You can issue this command when all paths to the primary disk drive are in a STARTED state. However, the paths to the mirror disk drive must be in a STOPPED state. • Effective with the H06.23/J06.
Considerations for DELETE DISK and Online Disk Remirroring • You must stop all paths to the mirror disk drive (-M and -MB) before you issue this DELETE command: ->DELETE DISK $disk-volume-name -M • To delete a disk drive currently serving as the primary disk drive, you must first change its role by using the SWAPMIRROR command. Example of Online Disk Remirroring NOTE: OSM automatically recognizes online remirrored disks. TSM does not.
-> STOP DISK $DATA1-M -> STOP DISK $DATA1-MB -> DELETE DISK $DATA1-M NOTE: Allow 20 seconds to ensure the DELETE DISK command completes before proceeding to the ALTER DISK command in the next step. When using a TACL obey file or SCF infile, put the DELETE DISK commands in a different obey file or infile from the ALTER command. 6.
ADD DISK Examples for Different Disk Types • To add a mirrored internal disk: -> ADD DISK $DATA01, SENDTO STORAGE, & -> PRIMARYLOCATION (1,1,1), MIRRORLOCATION (1,1,2) • To add a nonmirrored 45xx disk connected to a pair of 6760 adapters: -> -> -> -> • To add a mirrored M8xxx disk to an Integrity NonStop NS-series server: -> -> -> -> -> -> -> • ADD DISK $FCDISK8, SENDTO STORAGE, & PRIMARYLOCATION (111,2,1), PRIMARYSAC PRIMARYDEVICEID (1,8), & BACKUPLOCATION (111,3,1), BACKUPSAC 1 MIRRORLOCATION (112,
Adding a Similar Disk to Another System To configure the same or a similar disk on another system, 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 a different configuration file on the current system. 1. Capture the configuration for an existing disk: -> INFO / OUT LOG / $MAG1, OBEYFORM == STORAGE - Obeyform Information Magnetic DISK \COMM.
Considerations for ALTER DISK and Disks • To change these attributes, first put the disk in the STOPPED state by using the “STOP DISK Command” (page 290): ALTNAME MBACKUPLOCATION PRIMARYLOCATION AUDITTRAILBUFFER MBACKUPPORTNAME PRIMARYLUN BACKUPDEVICEID MBACKUPSAC PRIMARYPARTITION BACKUPCPU MIRRORDEVICEID PRIMARYPORTNAME BACKUPDEVICEID MIRRORLOCATION PRIMARYSAC BACKUPLOCATION MIRRRORLUN PROTECTDIRECTORY BACKUPPORTNAME MIRRORPARTITION PROGRAM BACKUPSAC MIRRORPORTNAME SERIALWRITES HIG
2. Change one or more of the “Disk Attributes for the ALTER DISK Command” (page 230). For example, this command changes the revive attributes for the disk: -> ALTER $DATA00, REVIVERATE 10, REVIVEPRIORITY 100 3. Verify the change is entered into the system configuration database: -> INFO $DATA00, DETAIL 4. See “Resetting a Disk” (page 103). Configuring the Size of Disk Cache The CACHE attribute specifies the disk cache configuration for an in-use volume.
Configuring Disk Cache 1. 2. Review information about the CACHE attribute. List current disk cache configuration information: 1-> INFO $DATA00, CACHE STORAGE - Cache Info Magnetic DISK \NBSTS01.$DATA00 (Cn = config, Al = alloc) Size______512_________1K_________2K_________4K________32K Cn Al -1 512 -1 512 -1 512 -1 4096 -1 512 Bytes Allocated To Cache: 34560 KB 3. Save accumulated statistical data before flushing it: 1-> STATS / OUT STATSLOG / $DATA00 SCF W20052 Creating file \NBSTS01.$DATA00.
7. Reset all counters for the disk: -> STATS $DATA10, RESET Resetting the statistics after a cache configuration change lets you see how the new values affect performance. For more information, see “Reconfiguring Cache to Resolve Performance Problems” (page 61). Naming a Disk All disk volumes have two names: a default volume name and an alternate volume name.
Considerations for RENAME DISK • When you issue the RENAME DISK command, the disk must be in one of these states: ◦ STOPPED state, substate DOWN ◦ SERVICING state, substate SPECIAL • During a rename operation, SCF puts the disk (or both halves of a mirrored volume) in the SERVICING state, substate SPECIAL, so no other processes can access the disk. When the operation finishes, SCF puts the disk in the STARTED state.
5. View the new volume name and alternate volume name: -> INFO $SPARE00, LABEL Changing Either the Volume Name or Alternate Volume Name The VOLNAME and ALTNAME attributes 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. The disk process reads the disk label and might change its process name to match either the VOLNAME or ALTNAME.
1. Verify the disk is stopped: -> STATUS $DATA02 2. Change the alternate volume name: -> ALTER $DATA02, ALTNAME $ALT00 3. View the new alternate volume name: -> INFO $DATA02, LABEL The alternate volume name in the display should be $ALT00. 4. Start the disk: -> START $DATA02 Because you changed only the alternate volume name and the volume name is still $DATA02, the disk name does not change.
-> STATUS $DATA01 3. Rename the disk $DATA01 to $BLANK01: -> ALTER $DATA01, LABEL $BLANK01 The disk is automatically started using the new names, $BLANK01-P and $BLANK01-M, even if AUTOSTART is not configured. 4. Verify the volume name of the disk has changed: -> STATUS $BLANK01 5.
You can use SCF commands to add, configure, delete, and view the partitions on a SAS disk. These commands are: • The “ADD PARTITION Command” (page 216) adds a new partition on a physical disk specified by the CLIM and LUN. • The “INFO PARTITION Command” (page 256) displays the disk partition information for the physical disk specified by the CLIM and LUN. • The “DELETE PARTITION Command” (page 250) deletes the last partition or all partitions on the physical disk specified by the CLIM and LUN.
• Deleting the mirror volume also deletes the mirror backup, if it exists. • Always note the location of the disk that you delete. Once you delete a disk from the system configuration database, it becomes unavailable to SCF. However: ◦ Installing an unconfigured disk in a slot generates an error message either at that time or when the system is restarted. ◦ You can use OSM or TSM to view disks that are physically currently installed in system slots.
• Altering a WRITECACHE setting of a disk partition sets the writecache setting of all the disk partitions that are configured on the same physical disk. Changes to the other disk partitions set the writecache setting of all their mirror disks. • Altering WRITECACHE setting must be done only when the Storage CLIMs are free.
7 Managing Disks This chapter describes managing disks. Disks share the object type of DISK with virtual disks. See “Configuring and Managing Virtual Disks” (page 143). For information about disk load balancing, see “Disk Load Balancing” (page 118).
Troubleshooting Disks For more information about troubleshooting disk drives, see the Service and Support Library of the NonStop Technical Library (NTL). Starting a Disk The “START DISK Command” (page 274) 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.
Reviving a Mirrored Disk The “START DISK Command” (page 274) makes a stopped disk accessible to user processes and revives the second half of a mirrored volume. Use this procedure if you have stopped one half of a mirrored volume and need to synchronize the two halves when restarting the disk. This situation can occur if: • You do something that affects only one disk of a mirrored volume. For an example, see “Replacing the Bootstrap Program” (page 107).
d. e. When the copy interval expires, the disk process finishes the request that it is currently handling and continues the disk revive operation again. 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.
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.
Temporarily Stopping a Revive Operation 1. Temporarily stop the disk being revived: -> RESET $DATA01-M The disk remains in the STARTING state, REVIVE substate. 2. 3. While the revive operation is suspended, do what needs to be done to resolve the problem. For example, spare the defective sector. Resume the revive operation: -> START $DATA01-M The revive operation resumes from the point at which it was stopped.
3. Confirm that the disk is in the STOPPED state, substate DOWN: -> STATUS $AUDIT If the STOP command does not work and you need to stop the disk, use the ABORT command.
Resetting a Disk The “RESET DISK Command” (page 271) puts a disk into the STOPPED state, substate DOWN, ready for restarting. • Use the RESET command to prepare a device to be started if: ◦ A disk is in the STOPPED state, substate HARDDOWN. ◦ A hardware error has occurred. ◦ You stopped the disk with an ABORT command. ◦ The disk was stopped for service. ◦ A STOP or ABORT command fails to put the device into the STOPPED state, substate DOWN. See “Resetting One Disk” (page 103).
5. Confirm that the disk has started: -> STATUS $DISK00 Resetting a Group of 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 $disk00-P 5.
Disabling Automatic Sector Reallocation If you want to disable automatic sector reallocation, you must disable it for all disks; you cannot enable or disable it for specific disks. To disable automatic sector reallocation: > STOP $ZRD9 You might want to disable $ZRD9 if you choose to manually spare a sector.
1. 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. If either of these events occur during a spare operation, the specified sector is not spared, and an error message is displayed: 2. • All spare sectors on the disk are in use. • The added defect map is full. • In either case, you must replace the disk.
Troubleshooting Doubly Allocated File Extents 1. 2. 3. Repeat “Identifying Doubly Allocated File Extents” (page 106) 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. Use FUP DUP or BACKUP to copy to another volume the files identified in the DSAP report that contain doubly allocated extents. Purge these files from the original volume.
If the disk is in the STARTING state, substate REVIVE, wait until the revive operation has finished before continuing to the next step. Both halves must be in the STARTED state before proceeding. 4. Replace the bootstrap program on the primary disk: -> CONTROL DISK $SYSTEM, REPLACEBOOT $SYSTEM.SYSnn.SYSDISC 5.
Enabling and Disabling File Opens on a Disk Preventing File Opens on a Disk The “STOPOPENS DISK Command” (page 293) prevents applications from opening files on a specific 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. If you do issue a STOPOPENS DISK command on the system disk, do not exit SCF. Immediately enter an ALLOWOPENS DISK, SUPERONLY command.
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). Then you can alter the disk configuration with new PRIMARYCPU and BACKUPCPU values. You typically swap processors for a disk when load balancing the system or preparing for disk replacement. PRIMARY DISK Consideration For G06.
1. Display the current status of the disk on which you intend to swap the processors: -> STATUS DISK $D0201-* STORAGE - Status DISK \WAGER.$D0201-* 2.
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 Backup PID 3,35 3,35 3,35 3,35 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.
Considerations for SWITCH DISK • If you attempt to switch the primary and backup paths but the backup path is unavailable, the paths are not switched. • If the specified path is already active, the SWITCH command has no effect. • Use the STATUS DISK command to verify the path switch. • Switching the path to the backup controller can create a SAC ownership conflict in G06.10 and earlier RVUs. See “Understanding SAC Ownership” (page 123).
Switching the Active Path for a Disk 1. Display the current status of the disk paths: -> STATUS $D0201-* STORAGE - Status DISK \WAGER.$D0201-* 114 LDev Path Status State 104 104 104 104 PRIMARY BACKUP MIRROR MIRROR-BACKUP ACTIVE INACTIVE ACTIVE INACTIVE STARTED STARTED STARTED STARTED Substate Primary PID Backup PID 2,107 2,107 2,107 2,107 3,35 3,35 3,35 3,35 • The $D0201 disk process is still executing in processor 2. • The $D0201 disk is now accessed through SACs in the same PMF CRU.
2. Change the active path accessing the primary disk: -> SWITCH $D0201-B 3. Display the changed status: -> STATUS $D0201-* STORAGE - Status DISK \WAGER.$D0201-* 4.
5. 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 INACTIVE ACTIVE INACTIVE ACTIVE STARTED STARTED STARTED STARTED Substate Primary PID Backup PID 2,107 2,107 2,107 2,107 3,35 3,35 3,35 3,35 Managing Encrypted Disk Drives SCF supports encryption of data-at-rest for disk objects that are connected with CLIMs.
Displaying Information about Encrypted Disks To display information about encrypted disks, see “Displaying Information about Encrypted Disks” (page 58). Changing the Speed of Encryption Key Rotation While an encryption key rotation operation is in progress, you can use the ALTER command to change its speed. Considerations for Changing the Speed of an Encryption Key Rotation • The defaults are 50 for ENCRYPTRATE and 4 for ENCRYPTPRIORITY.
8 Disk Load Balancing Disk load balancing seeks to distribute the disk work load across all fabrics and processors in the system. This chapter 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.
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 $OPER-M … 1 $OPER-B *STARTED 0,298 1,269 STARTED 0,298 1,269 However, these asterisks illustrate an unbalanced situation: Slot 50: 2 $OPER-MB … 1 $OPER-P Slot 55: 2 $OPER-M … 1 $OPER-B STARTED 0,298 1,269 STARTED 0,298 1,269 *STARTED 0,298 1,269 *STARTED 0,298 1,269 Both halves of the mirrored volume are running on one fab
For detailed guidelines about how to use the PRIMARY command, see “Swapping Processors for a Disk” (page 109). The disk processing load within each enclosure should be evenly balanced between the processor pair in that enclosure. Assuming that each disk handles the same processing load, each enclosure should have one processor managing half of the primary disk processes and the other processor managing the other half.
Disk Load Balancing Between Processors 121
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 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.
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: 124 • 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 On G05.00 through G06.10, the PRIMARY command changes processor ownership of active paths. (The FORCED option forces all SACs to change ownership.) This change in ownership in turn causes other IOPs in the same topology branch to perform additional path switches or processor swaps to recover from the loss of SAC ownership. Disk Load Balancing on G06.
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: 2. • SACs owned by processor 2 are shaded. • Disk processes that are primaried in processor 2 are shaded. • Primary paths are the bold lines.
3. Display the changed status: -> STATUS DISK $D0203-* STORAGE - Status DISK \WAGER.$D0203-* LDev Path Status State 104 104 104 104 PRIMARY BACKUP MIRROR MIRROR-BACKUP ACTIVE INACTIVE ACTIVE INACTIVE STARTED STARTED STARTED STARTED Substate Primary PID Backup PID 3,35 3,35 3,35 3,35 2,107 2,107 2,107 2,107 $D0203 also changes primary processors in because: 1. The disk process executing in processor 2 attempts to access $D0203-P. 2. The path to $D0203-P on the X fabric leads through SAC 2.
NOTE: 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. PRIMARY Command Function in G05.00 and Earlier On G05.00 and earlier RVUs, the PRIMARY command changes SAC ownership. Before the PRIMARY command is issued, the status of $D0203 is: STORAGE - Status DISK \WAGER.
1. Move the primary disk process of another disk in the same topology branch to processor 3: -> PRIMARY $D0201, 3 2. Display the changed status: -> STATUS DISK $D0203-* STORAGE - Status DISK \WAGER.$D0203-* LDev Path Status State 105 105 105 105 PRIMARY BACKUP MIRROR MIRROR-BACKUP INACTIVE ACTIVE INACTIVE ACTIVE 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 $D0203 changes paths to access the disk in because: 1.
4. The disk process, still executing in processor 2, attempts to access $D0203-M. The path to $D0203-M on the Y fabric leads through SAC 1. This SAC is now owned by processor 3. Because the disk process is executing in processor 2 but the SAC is owned by processor 3, the disk access fails. The disk process changes paths and tries to access $D0203-MB. The path to $D0203-MB on the X fabric leads through SAC 1. Because this SAC is still owned by processor 2 the disk access succeeds.
105 105 105 105 PRIMARY BACKUP MIRROR MIRROR-BACKUP ACTIVE INACTIVE ACTIVE INACTIVE STARTED STARTED STARTED STARTED 2,22 2,22 2,22 2,22 3,16 3,16 3,16 3,16 Substate Primary PID 2,112 2,112 2,112 2,112 Backup PID 3,45 3,45 3,45 3,45 Substate Primary PID 2,118 2,118 Backup PID 3,237 3,237 Substate Primary PID 2,122 2,122 Backup PID 3,86 3,86 STORAGE - Status DISK \WAGER.
STORAGE - Status DISK \WAGER.$D0207-* LDev Path Status State 112 112 PRIMARY BACKUP INACTIVE ACTIVE STARTED STARTED Substate Primary PID 2,118 2,118 Backup PID 3,237 3,237 Substate Primary PID 2,122 2,122 Backup PID 3,86 3,86 STORAGE - Status DISK \WAGER.$D0208-* 9. LDev Path Status State 114 114 PRIMARY BACKUP INACTIVE ACTIVE STARTED STARTED Move the corresponding disk processes to the other processor to match the switched paths.
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” (page 118). • 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.#*.GRP-2*, DETAIL STORAGE - Detailed Status ADAPTER \COMM.$ZZSTO.#PMF.GRP-2.MOD-1.
9 Configuring and Managing Storage Pools for Disks A storage pool is a collection of 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. For descriptions of this object and its states, see “The POOL Object” (page 36)and “POOL Object States” (page 36). For commands that affect POOL objects, see “Storage Subsystem Commands” (page 190).
Example of an INFO POOL Report -> INFO POOL $POOL3 STORAGE - Info POOL \COMM.$POOL3 *Audited CatalogLocation ALLOWED $VIRCFG.POOL3CAT *Magnetic REQUIRED *Mirrored REQUIRED *Updatestats 1 Explanation of Fields — INFO POOL Report * Indicates an attribute whose value you can change by using the SCF ALTER POOL command. Audited Shows whether audited volumes, protected by the TMF product, are allowed or required in the storage pool.
DiskThreshold The threshold percentage of disk space usage at which the disk processes associated with the physical volume in the storage pool should generate an EMS warning message. ExtentInterval The extent interval at which the disk processes associated with the physical volumes in the storage pool should generate additional file-extent usage EMS messages.
Pool I/O Process Information: Library File....... Program File....... $SYSTEM.SYS01.OPP Explanation of Fields — Detailed STATUS POOL Report LDev The logical device number for the storage pool process. State The object state of the storage pool process. Primary PID Backup PID The processor number and PIN of the current primary and backup storage pool processes. Type The type number of the storage pool process is 25 Subtype The subtype number of the storage pool process is 0.
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. Capture the configuration for an existing pool process: -> INFO / OUT LOG / $POOL1, OBEYFORM == STORAGE - Detailed Info POOL in obeyform: \COMM.
Considerations for Removing a Disk From a Storage Pool When you remove a disk from a storage pool: • The POOL name is removed from the disk label if the pool process for the disk is not defined in the system. • SCF asks you to confirm the command in these cases: • ◦ The POOL process for the disk is not in the STARTED state. ◦ Virtual disks associated with the pool are not in the STARTED state. ◦ The physical volume has storage-managed files on it.
Deleting a Storage Pool Use the “DELETE POOL Command” (page 251) 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.
-> -> -> -> 4. ALTER ALTER ALTER ALTER $P5D04, $P5D03, $P5D02, $P5D01, POOL POOL POOL POOL EXCLUDE EXCLUDE EXCLUDE EXCLUDE Stop the storage pool: -> STOP $POOL5 The storage pool enters the STOPPED state. 5. Delete the storage pool: -> DELETE $POOL5 6.
The storage pool finishes any current activity before it enters the STOPPED state. Virtual disks that use the stopped pool encounter an error. Resetting a Storage Pool The “RESET POOL Command” (page 272)puts a storage pool into the STOPPED state, substate DOWN, reading for restarting. 1. Check the current status of the storage pool: -> STATUS $POOL01 2. If it is not in the STOPPED state, substate DOWN: -> RESET $POOL01 3. Start the storage pool process: -> START $POOL01 4.
10 Configuring and Managing Virtual Disks Virtual disks share the object type of DISK with disks (discussed in “Configuring Disks” (page 70)). A virtual disk is created by configuring one or more disks in a storage pool as part of “Storage Management Foundation (SMF)” (page 26). For information about disks and their states, see “The DISK Object” (page 33)and “Object States and Substates of Disks” (page 34).
Any number of virtual disks can be associated with a pool. The files on a virtual disk are not necessarily placed by SMF on a single physical disk. The following examples summarize the relationships between virtual disks and physical disks: • One physical volume might be 12 virtual disks, allocated to 12 users who share space on the same disk. • Fifty physical disks might be 10 virtual disks, allocated to 10 users requiring a large amount of storage for completing their development work.
Examples • To display information about a virtual disk: -> INFO $VDISK00 The display is shown and explained under “Example of an INFO DISK Summary Report” (page 145). • To display detailed information about a virtual disk: -> INFO $VDISK00, DETAIL The display is shown and explained under “Example of an INFO DISK Detailed Report” (page 146).
Example of an INFO DISK Detailed Report For virtual disks, the INFO DISK, DETAIL command produces a short report (compared to the report for physical disks). -> INFO DISK $DATA1, DETAIL STORAGE - Detailed Info Virtual DISK \COMM.$DATA1 *ANTCapacity........................... 1000000 ANTLocation........................... $P1D02.ZYS00000.A0001MRG *BackupCPU............................. 5 *CacheSize............................. 30000 *Highpin............................... OFF *Mode...........................
Example of a Detailed STATUS DISK Report for Virtual Disks -> STATUS $DATA1, DETAIL STORAGE - Detailed Status VIRTUAL DISK \COMM.$DATA1 Virtual Disk Process Information: LDev State Primary Backup PID PID 386 STARTED 4,105 5,93 Type Subtype 3 36 Virtual Disk I/O Process Information: Library File....... Program File....... $SYSTEM.SYS01.
Example 1. Add the virtual disk to the system configuration database and associate it with a storage pool: -> ADD DISK $VDISK00, SENDTO STORAGE, ANTLOCATION $SYSTEM, & -> POOL $POOL01, PENDOPSLOCATION $SYSTEM, TYPE VIRTUAL 2. Verify the attributes recorded in the system configuration database: -> INFO DISK $VDISK00 3. See “Starting a Virtual Disk” (page 150).
The ADD DISK Command Fails An ADD DISK command can fail if a record for the given name exists or if the SMF Master Process already has a definition for a virtual disk of the given name. For example, if SCF successfully adds the configuration record but then cannot define the process by using the SMF Master Process, SCF attempts to delete the configuration records. If this action fails, SCF puts out a message to warn that configuration records remain although there is no definition in the SMF Master Process.
5. Restart the disk process: -> START $VDISK00 Deleting a Virtual Disk The “DELETE DISK Command” (page 248) 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. ◦ TMF must be running. ◦ $ZSMS must be in the STARTED state. ◦ The storage pool process specified by the POOL attribute must be started.
Considerations for START DISK and Virtual Disks • The disk specified must have a configuration record and a definition with the SMF master process (as verified by the INFO and STATUS commands). • TMF must be running on the system.
Swapping Processors for a Virtual Disk The“PRIMARY DISK Command” (page 264) swaps the primary and backup processors for a virtual 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. You typically swap processors when load balancing the system or preparing for disk replacement.
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. For information about ADAPTER objects and their states, see “The ADAPTER Object” (page 32) and “Object States and Substates” (page 31). For commands that relate to this object, see “Storage Subsystem Commands” (page 190).
-> INFO ADAPTER $ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-50, DETAIL The display is shown under “Example of a Detailed INFO IOMF ADAPTER Report” (page 155). • To display configuration information about the 6760 ServerNet device adapter in group 11, slot 51: -> INFO ADAPTER $ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-51 The display is shown under “Example of an INFO SNDA ADAPTER Report” (page 156). • To display detailed configuration information about the same 6760 ServerNet device adapter: -> INFO ADAPTER $ZZSTO.#SNDA.GRP-11.
1 3 7 11 13 15 17 DISK DISK DISK DISK DISK DISK DISK $OPER-P $MAG1-P $AOL1-P $SYSTEM-P $DSMSCM-P $AUDIT-P $NEWSYS-P CPU 0 1 0 0 0 0 0 CPU 1 0 1 1 1 1 1 Target ID 4 5 9 0 1 2 3 Lun 0 0 0 0 0 0 0 SAC \COMM.$ZZSTO.#PMF.SAC-3.GRP-1.MOD-1.
ServerNet Addressable Controllers: SAC \COMM.$ZZSTO.#IOMF.SAC-1.GRP-11.MOD-1.SLOT-50: Configured Devices ( group: 11, module: 1 ): Slot Type Name Primary Backup CPU CPU 2 DISK $ESD001-MB 0 1 4 DISK $ESD002-MB 0 1 6 DISK $D11105-MB 0 1 8 DISK $MAIL-MB 0 1 12 DISK $P1D04-MB 0 1 14 DISK $P5D04-MB 0 1 16 DISK $P6D04-MB 0 1 18 DISK $D11117-MB 0 1 Device Target ID 4 5 8 9 0 1 2 3 Lun 0 0 0 0 0 0 0 0 Device Target ID 4 5 8 9 0 1 2 3 Lun 0 0 0 0 0 0 0 0 SAC \COMM.$ZZSTO.#IOMF.SAC-2.GRP-11.MOD-1.
Configured Devices ( group: 11, module: 1 ): Slot Type Name Primary Backup CPU CPU 51 DISK $LANA-P 0 1 51 DISK $LANA-MB 0 1 Device Target ID 0 2 Lun 0 0 SAC \COMM.$ZZSTO.#SNDA.SAC-2.GRP-11.MOD-1.SLOT-51: SAC \COMM.$ZZSTO.#SNDA.SAC-3.GRP-11.MOD-1.SLOT-51: SAC \COMM.$ZZSTO.#SNDA.SAC-4.GRP-11.MOD-1.SLOT-51: This report shows that the 6760 ServerNet device adapter has two disks on SAC 1. See Explanation of Fields — Detailed INFO PMF ADAPTER Report.
-> STATUS ADAPTER $ZZSTO.#PMF.GRP-1.MOD-1.SLOT-50, DETAIL The display is shown and explained under “Example of a Detailed STATUS PMF ADAPTER Report” (page 158). • To display status of the adapter in the IOMF CRU in group 11, slot 50: -> STATUS ADAPTER $ZZSTO.#IOMF.GRP-11.MOD-1.SLOT-50 The display is shown and explained under “Example of a STATUS IOMF ADAPTER Report” (page 160). • To display detailed status of the same adapter in the IOMF CRU: -> STATUS ADAPTER $ZZSTO.#IOMF.GRP-11.MOD-1.
SAC Number..... POST Result.... SAC Type....... Status......... 1 PASSED SCSI PRESENT Firmware.......... T1067AAO SAC SSCI ID....... 6 Side.............. X-Fabric Configured Devices ( group: 1 , module: 1 ): Slot Name State Substate 2 4 8 12 14 16 18 $OPER-MB $MAG1-MB $AOL1-MB $SYSTEM-MB $DSMSCM-MB $AUDIT-MB $NEWSYS-MB STARTED STARTED STARTED STARTED STARTED STARTED STARTED Primary PID 0,298 0,295 0,287 0,257 0,291 0,288 0,297 Backup PID 1,269 1,272 1,280 1,257 1,276 1,279 1,270 SAC \COMM.$ZZSTO.
Revision Level The revision level stored in the adapter. Status Shows whether the adapter is present. Tracking Number The vendor ID stored in the adapter. Vendor ID The manufacturer of the adapter (when available). ServerNet Addressable Controllers: SAC Number The SAC within the adapter. Firmware The part number of the firmware. POST Result Shows whether the power-on self-test (POST) passed. SAC Type The protocol type of the SAC.
Configured Devices ( group: 11 , module: 1 Slot Name State Substate 2 4 6 8 12 14 16 18 $ESD001-MB $ESD002-MB $D11105-MB $MAIL-MB $P1D04-MB $P5D04-MB $P6D04-MB $D11117-MB STARTED STARTED STOPPED STARTED STARTED STARTED STARTED STOPPED ): Primary PID 0,292 0,293 0,289 0,296 0,299 0,300 0,301 0,290 HARDDOWN HARDDOWN Backup PID 1,275 1,274 1,278 1,271 1,268 1,267 1,265 1,277 SAC \COMM.$ZZSTO.#IOMF.SAC-2.GRP-11.MOD-1.SLOT-50: SAC Number..... 2 Firmware.......... T1067AAO POST Result....
SAC \COMM.$ZZSTO.#SNDA.SAC-1.GRP-11.MOD-1.SLOT-51: SAC Number..... 1 Firmware.......... T0054AAF POST Result.... PASSED SAC SSCI ID....... 0 SAC Type....... FIBER Side.............. X-Fabric Status......... PRESENT Configured Devices ( group: 11 , module: 1 Slot Name State Substate 51 51 $LANA-P $LANA-MB ): Primary PID 0,294 0,294 *STARTED STARTED Backup PID 1,273 1,273 SAC \COMM.$ZZSTO.#SNDA.SAC-2.GRP-11.MOD-1.SLOT-51: SAC Number..... 2 Firmware.......... T0054AAF POST Result.... PASSED SAC SSCI ID...
Tracking Number.. MP0008 Vendor ID.............. ServerNet Addressable Controllers: SAC \IO.$ZZSTO.#FCSA.SAC-1.GRP-11.MOD-2.SLOT-1: SAC Number..... 1 Firmware.......... T0630G06 POST Result.... PASSED SAC SCSI ID....... SAC Type....... FC Side.............. Both Status......... PRESENT Connection..... F port Port Id........ 65792 SAC State...... Ready Node Name......... 20060B00001CE5F8 Port Name......... 50060B00001CE5F8 SAC Subtype....... 1 SAC \IO.$ZZSTO.#FCSA.SAC-2.GRP-11.MOD-2.SLOT-1: SAC Number...
Example of a STATUS FCSA ADAPTER, SERVERNET Report -> STATUS ADAPTER $ZZSTO.#FCSA.GRP-11.MOD-2.SLOT-1, SERVERNET STORAGE - ServerNet Status ADAPTER \IO.$ZZSTO.#FCSA.GRP-11.MOD-2.
Connection..... F port Port Id........ 65792 SAC State...... Ready Node Name......... 20060B00001CE5F8 Port Name......... 50060B00001CE5F8 SAC Subtype....... 1 Configured Devices ( group: 11, module: 2 ): Slot Name State Substate Primary PID 2,272 3,283 3,282 1 $PT00-B STARTED 1 $PT01-B STARTED 1 $PT02-B STARTED SAC \IO.$ZZSTO.#FCSA.SAC-2.GRP-11.MOD-2.SLOT-1: SAC Number..... 2 Firmware.......... T0630G06 POST Result.... PASSED SAC SCSI ID....... SAC Type....... FC Side.............. Both Status......
Port Name The worldwide name (WWN) of the controller port. SAC Subtype Indicates the type of SAC. The numeral one (1) indicates a two-port, 2 GB Fibre Channel SAC For an explanation of the other fields, see Explanation of Fields — Detailed STATUS PMF ADAPTER Report.
system automatically adds an installed adapter back to the system configuration database in any of these cases: • You remove the adapter and then insert it back into the slot. • You restart the system. • You power off and on the adapter or its enclosure. • 1. Example Identify all the devices currently using the adapter: -> STATUS $ZZSTO.#SNDA.GRP-11.MOD-1.SLOT-51, DETAIL See “Example of a Detailed INFO SNDA ADAPTER Report” (page 156). 2. 3. 4. 5. 6.
Considerations for SWITCH ADAPTER • The SWITCH ADAPTER command replaces a series of SWITCH commands for individual paths and devices in the topology branch. • At the completion of the command, the SWITCH ADAPTER command returns a count of the number of paths that did not switch. Handle any exceptions individually. • You can use this command only on devices that are configured with dual paths. • Use the STATUS ADAPTER command to verify the path switch. • 1.
Testing Connections to the SACs on an FCSA You can use the PROBE SAC command to test the connection to a SAC on an FCSA. The connection can be either an arbitrated loop or a link to a Fibre Channel switch. For details, see “PROBE SAC Command” (page 268).
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.
“Open SCSI Path Attributes” (page 171) lists the possible attribute values for the different types of Open SCSI connections.
I/O Process Information: *BackupCpu............................. *HighPin............................... *PrimaryCpu............................ *Program............................... *RecSize............................... *StartState............................ 0 ON 1 $SYSTEM.SYSTEM.TDSCSI 57344 STARTED SCSI Device Settings: *MaxOpens.............................. *NumIO................................. *StructAreaSize........................ *TraceBufLen........................... *TraceLevel.........
RecSize The configured record size (in bytes) for the device. StartState Shows whether the IOP is configured to be in the STARTED or state when the system is loaded. SCSI Device Settings: MaxOpens The maximum number of concurrent opens allowed by the IOP. NumIO The maximum number of concurrent I/O operations the IOP can have outstanding; used by the SCSI IOP to determine the size of allocated data-buffer area.
SCSI I/O Process Information: Device Type.......... 8 Device Subtype........ 0 Physical Record Size. 4096 Priority.............. 220 Library File......... Program File......... $SYSTEM.SYS01.TDSCSI 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.
-> INFO $S11500 5. See “Starting an Open SCSI Device” (page 177). Adding a Similar Open SCSI Device to This System To add another Open SCSI device similar to an existing device, use the LIKE attribute: -> ADD SCSI $S11501, LIKE $S11500, PRIMARYLOCATION (11,1,51) Adding a Similar Open SCSI Device to Another System To configure the same or a similar Open SCSI device on another system, create a command file by using the OBEYFORM attribute of the INFO DISK command.
Altering Open SCSI Attribute Values The “ALTER SCSI Command” (page 237) alters the attributes of an Open SCSI device in the system configuration database. For a description of alterable Open SCSI attributes, see “ALTER SCSI Attributes” (page 238). 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.
3. Start the Open SCSI device: -> START $S11500 4. Verify the process is started: -> STATUS $S11500 Starting an Open SCSI Device The “START SCSI Command” (page 276) puts the storage pool into the STARTED state: 1. Start the device: -> START $S11500 2. Check the status of the process: -> STATUS $S11500 Stopping an Open SCSI Device The “STOP SCSI Command” (page 292) places an Open SCSI device in the STOPPED state: 1. Stop the device: -> STOP $S11500 2.
-> PRIMARY $DEV1 178 Configuring and Managing Open SCSI Devices
13 Configuring and Managing Tape Drives This chapter describes configuring tape drives. The tape drive processes on the system have the object type of TAPE. For details about this device, see “The TAPE Object” (page 39)and “TAPE Object States” (page 39). For commands that can affect this device, see “Storage Subsystem Commands” (page 190).
Table 11 Tape Device Path Attributes (continued) SNDA Connection PMF/IOMF Connection FCSA Connection Integrity NonStop NS-Series Module 1 1 2-3 (IOAM) Slot 51-54 50 or 55 1-5 (FCSA) SAC 1-4 3 1-2 DEVICEID 0-5 (S-pic) 4-5 (F-pic) 0-5 NA PORTNAME NA NA 64-bit WWN LUN 0 0 0-31 Fibre Channel Tape Connections To configure tape drives that are connected to the system through an FCSA follow these rules: • If a Fibre Channel tape drive is connected directly to an FCSA, you must specify th
Compression For cartridge tape drives, shows whether compression is configured. This setting is ignored by 5194 tape drives because compression is always on. For other tape drives, this field is not applicable (N/A). Adapter Location The physical location (group, module, and slot) of the adapter where the tape drive is attached.) 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.
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. Normally, tape device IDs are either 4 or 5. For Fibre Channel devices, the WWPN that is configured for the path to the device. The number is a 16 character hexadecimal number, without a leading %H.
State The current object state of the tape drive. For a list of tape drive states, see “TAPE Object States” (page 39). Primary PID The processor number and PIN of current primary tape process. Backup PID The processor number and PIN of current backup tape process. DeviceStatus The current status of the device. Values can be: NOT READY The tape drive is not ready to be used. ONLINE The tape drive is online and away from beginning of tape.
Short Write Mode 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. SubType Shows the device subtype of the tape drive, which varies by tape-drive model and function.
The display would be the same for non-encrypted tape media in encrypted, but disabled, drive. • This example shows a non-CLIM tape drive: STORAGE - Status TAPE $TAPE11, ENCRYPTION Drive Not encrypted (non-CLIM) Explanation of Fields — STATUS TAPE, ENCRYPTION Report Media If no media is present or encryption status is unknown, field will display “Not present or encryption status unknown”. If media is unencrypted, field will display “Not encrypted”.
• The tape IOP overrides any value provided in the ADD TAPE command that is not valid for that specific tape device. • For tape drives connected to the system through an FCSA, see “Fibre Channel Tape Connections” (page 180) Adding One Tape Drive 1. 2. Physically install the tape drive and note the group, module, and slot of its adapter. Add the tape drive to the system, specifying the group, module, and slot: -> ADD TAPE $TAPE0, SENDTO STORAGE, LOCATION (1,1,55) 3.
Adding a Fibre Channel Tape Drive To add a Fibre Channel tape device that is directly connected to an FCSA, you specify the PORTNAME (WWN) and LUN of the tape device. This command adds a Fibre Channel tape device to the system: -> ADD TAPE $LTO3, SENDTO STORAGE, LOCATION (110,3,4) & -> SAC 2, PORTNAME 210000E08B1755DC, LUN 0 Altering Tape Drive Attribute Values The “ALTER TAPE Command” (page 241) alters the attributes of a tape drive in the system configuration database.
Managing a Tape Drive Management tasks for tape drives include: • “Enabling or Disabling Labeled-Tape Processing” (page 188) • “Resetting a Tape Drive” (page 188) • “Starting a Tape Drive” (page 189) • “Stopping a Tape Drive” (page 189) For information about I/O commands for managing tape drives, see the Guardian Procedure Calls Reference Manual. Enabling or Disabling Labeled-Tape Processing The “ALTER SUBSYS Attributes” (page 240) of the ALTER command toggles labeled-tape processing.
4. Verify the process is started: -> STATUS $TAPE0 Starting a Tape Drive The “START TAPE Command” (page 276) makes a tape drive accessible to user requests. Considerations for START TAPE • To start a tape drive, the tape drive must be connected to the external port of the adapter and the tape drive must be powered on. • If the tape process does not start, reset it with the FORCED option; then start it again. Starting One Tape Drive 1. Start the tape drive: -> START $TAPE0 2.
14 Storage Subsystem Commands This chapter provides the syntax and description of SCF commands. Overview of Storage Subsystem Commands Table 12 Overview of Storage Subsystem Commands Command Page Description ABORT 192 Terminates the operation of an object without regard to the current state of its operation. ADD 194 Defines an object to the subsystem. ALLOWOPENS 227 Allows an object to once again accept opens; reverses the effect of the STOPOPENS command.
Table 13 Object Types for Storage Subsystem Commands (continued) Command ADAPTER CLIM DISK MON POOL PROFILE SAC SCSI SUBSYS TAPE ALLOWOPENS — X — — — — — — — ALTER — X X X X — X X X CONTROL — X — — — X — — — DELETE X X X X X — X — X EJECT — X — — — — — — — INFO X X X X X — X X X INITIALIZE — X — — — — — — — LABEL — X — — — — — — — NAMES X X X X X — X X X X PROBE X PRIMARY — X X X — — X X X RENAME
Command Special Notes STATS DISK, RESET If you use the FORCED option, the command behaves the same way in a command file as interactively. STOP DISK Can be used in a command file, but fails if you attempt to stop the last path on an audited volume or if the volume has open files. If you use the FORCED option, the command behaves the same way in a command file as interactively.
ABORT DISK Command The ABORT DISK command puts a disk into the STOPPED state, substate HARDDOWN, but leaves the disk process running. The syntax is: ABORT [ / OUT file-spec / ] DISK $disk[-P |-B |-M |-MB ] [ , FORCED ] [ , POOL $pool ] [ , SEL state ] [ , SUB { ALL | MAGNETIC | VIRTUAL } ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. DISK $disk[-P |-B |-M |-MB ] is the disk name and the path (primary, backup, mirror, or mirror backup).
ABORT MON Consideration Use the “RESET Command” (page 270) to prepare the process for restarting. ABORT MON Example -> ABORT MON $ZSMS ABORT POOL Command The ABORT POOL command makes a storage pool inaccessible to user requests (same as “STOP POOL Command” (page 291)). The syntax is: ABORT [ / OUT file-spec / ] POOL $pool Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. POOL $pool is the storage pool process.
DISK $disk is the name of the disk. 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.
[ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , , , , , , , , , , PHYSVOLSELECT { ON | OFF } ] POOL { $pool | EXCLUDE } ] PRIMARYCLIM clim-name PRIMARYCPU number ] PRIMARYDEVICEID { number | ( shelf,bay ) } ] PRIMARYLOCATION ( group,module,slot ) PRIMARYLUN number } PRIMARYPARTITION primary-part-num PRIMARYPORTNAME number ] PRIMARYSAC { number | name } ] PROGRAM [[$vol.]subvol.
• To add a disk volume that uses a Fibre Channel ServerNet adapter to communicate with an Enterprise Storage System: -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> • ADD DISK $DISK02, SENDTO STORAGE,& PRIMARYCPU 01 & BACKUPCPU 02 & PRIMARYLOCATION (11,2,5), & PRIMARYSAC 1, & BACKUPLOCATION (11,3,5), & BACKUPSAC 1, & MIRRORLOCATION (11,3,5), & MIRRORSAC 2, & MBACKUPLOCATION (11,2,5), & MBACKUPSAC 2 & PRIMARYPORTNAME 50060E8003501213, & BACKUPPORTNAME 50060E8003501225 & PRIMARYLUN 16 & MIRRORPORTNAME 5
REVIVEINTERVAL 100 , & REVIVEPRIORITY 0 , & REVIVERATE 0 , & SERIALWRITES ENABLED, & WRITECACHE ENABLED ADD DISK Example for Virtual Disks See the procedure and considerations for “Adding a Virtual Disk” (page 147).
AUDITTRAILBUFFER number (TMF audit-trail volumes only) specifies the number of megabytes to be allocated for the audit-trail buffer of an audit volume. This value improves the performance of systems that use the Remote Duplicate Database Facility. number is in the range 0 through 768. If you do not configure a value for AUDITTRAILBUFFER, or if the value you specify is 0, DP2 uses a value of 1. However, if you do not configure a value or if you specify 0, the value is displayed as 0, not 1.
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. 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).
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. BACKUPPORTNAME number specifies the Fibre Channel port name (WWN) used by the backup path to a disk volume on the Enterprise Storage System (ESS) NOTE: This attribute is not valid for the PROFILE object. The ESS administrator must give you the WWN so that you can specify it in this attribute.
The name cache is used to hold entries in the audit-name table. number is in the range 0 through 50000. The default is 0. Avoid making the cache too small, which can adversely affect file-management operations (such as FILE_OPEN_ and file information requests) serviced by a virtual disk process. CAPACITYMISMATCH { ON | OFF }, when a revive completes for a mirrored volume consisting of drives of different capacities, CAPACITYMISMATCH specifies whether the source drive remains UP (ON) or goes HARDDOWN (OFF).
FASTBULKWRITE { ON | OFF }, (effective for all 512-byte-sector disks) specifies whether the system is using Fast Cache Bulk Writes. ON Cache Bulk Write is done in Fast mode. OFF Cache Bulk Write is done in Traditional I/O mode. The default is OFF. When ON, applications and utilities using bulk writes to unstructured files may have higher throughput. Using FASTBULKWRITE ON can result in lost data in unstructured files if the CPU running the primary disk process fails.
NOTE: • This attribute is only valid for 514 byte per sector disks: internal SCSI disks in S-series enclosures • 45xx disks in modular disk subsystems DP2 ignores this attribute for 512-byte-sector disks: • disks in an FCDM disk drive enclosure • ESS disks in an Enterprise Storage array • SAS disks in an MSA70 or M8390-12CG disk enclosure HALTONERROR number specifies whether an internally detected, unrecoverable, disk-process error forces a halt (code %11500) in the primary processor, backup proces
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. The Softdoc for the T1083 product describes several inconsistencies and the procedures for reconciling them. KEYALGORITHM, specifies the encryption key algorithm on a disk.
MAXLOCKSPERTCB number is the maximum records and files that a transaction can lock. number is in the range 0 through 1,000,000. 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.
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. If you specify MBACKUPSAC in number format, you must also specify MBACKUPLOCATION.
For 45xx, ESS, and M8xxx disks, is the location of the adapter that controls the mirror path to the disk. This attribute is optional if MIRRORSAC is given in name format but required if given in number format. MIRRORLOCATION can be altered when all paths to the volume are in the STOPPED state. MIRRORLOCATION can also be altered when all configured paths to the primary drive are in STARTED state and MIRRORLOCATION is not yet configured. The result of an online reconfiguration must be symmetrical.
in group 31, slot 12 is named $D3112. For M8xxx Fibre Channel disks, the standard name format is $FCnn, where nn is supplied by the storage subsystem. nn begins in the range 00 through 99 and continues with A0 through ZZ. If MIRRORING is ON, the name is created when the first disk is inserted, and the same name is used when the second disk inserted for the mirrored volume. name The disk is named using a nonstandard naming convention. name can have up to 4 characters.
PHYSVOLSELECT { ON | OFF } specifies whether a virtual disk process can consider this physical volume for file placement. This attribute is valid only when this physical volume is a member of a storage pool ON A virtual disk process can consider this physical volume for file placement (default). OFF A virtual disk process cannot consider this physical volume for file placement, regardless of the information supplied in a command. If PHYSVOLSELECT is OFF, the value of AUTOSELECTis ignored.
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 physical 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.
PROTECTDIRECTORY { CHECKPOINT | OFF | SERIAL } is the type of protection to use for the disk volume directory: CHECKPOINT Use a full-block checkpoint to protect directory writes. OFF Do not perform special write protection of the directory. SERIAL A write to the directory also results in a serial write to the mirror disk, if available. If the mirror disk is not available, a full-block checkpoint writes the directory.
REVIVERATE number determines the amount of data revived between preemption checks. The higher the rate, the more the impact on higher priority workloads; the lower the rate, the less the impact on higher priority workloads. At the same time, the higher the rate, the faster the revive operation, and the lower the rate, the slower the revive operation. The minimum value is 0, and the maximum value is 100. The default value is 0, which causes DP2 to use its internal default of 50.
To change the SQLMXBUFFER attribute, first put the disk in the STOPPED state by using the “STOP DISK Command” (page 290): • If you specify too large or small a value, DP2 automatically sets the needed size. • If you specify a value of 0, DP2 automatically sets the size of the buffer to 128. • If SQL/MX is not installed, setting this attribute to 16 allows DPS to increase DP2 cache to its maximum.
• When adding a new disk on disk partitions, the writecache setting of the new disk must match the writecache setting of the existing disk partitions. • Altering a writecache setting of a disk partition sets the writecache setting of all the disk partitions that are configured on the same physical disk. Changes to the other disk partitions set the writecache setting of all their mirror disks. To use this attribute, see “Write Caching” (page 94).
If the ZSMSCAT0 subvolume exists on $vol, $ZSMS assumes that the subvolume contains valid catalog information. If the subvolume does not contain valid catalog information, $ZSMS abends. If the ZSMSCAT0 subvolume does not exist on $vol, $ZSMS creates the subvolume and initializes it with appropriate catalog information. HIGHPIN { ON | OFF } specifies whether the IOP can run at a high PIN (ON, the default) or only at a low PIN (OFF).
Wild-card characters are not supported. SENDTO STORAGE directs the command to the storage subsystem. PRIMARYCLIM clim-name is the name of the one CLIM that is connected to the disk. PRIMARYLUN lun specifies the logical unit number (LUN) on the PRIMARYCLIM. BACKUPCLIM backup-clim-name is the name of the other CLIM that is connected to the disk. BACKUPCLIM must be specified. BACKUPLUN backup-lun specifies the logical unit number (LUN) on the BACKUPCLIM. This attribute is optional.
• You can add a partition to a partitioned disk while other existing partitions on the disk are active (online). Adding the partition does not affect the data on other existing partitions. • After adding disk partitions, each disk partition can be configured to a NonStop DISK LDEV using the ADD DISK command. The NonStop DISK LDEV configured to a disk partition must be initialized before it can be started.
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.
This attribute has no effect if DISKTHRESHOLD is -1. DISKTHRESHOLD number is the threshold (as a percentage) that, with the DISKINTERVAL attribute, is used by the disk process to determine when to issue a disk-full EMS message for physical volumes in the storage pool. For example, if DISKTHRESHOLD is 75, the disk process generates an EMS message when the physical volume becomes 75 percent full.
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.]fileid is the object file name of the IOP. If not specified, PROGRAM is: $SYSTEM.SYSTEM.OPP If you specify PROGRAM as $SYSTEM.
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.
ADD [ / OUT file-spec / ] SCSI $SCSI-device , SENDTO STORAGE [ , LIKE object ] [ , attribute-spec ]... Wild-card characters are not supported. OUT file-spec directs all SCF output to the specified file. SCSI $SCSI-device is the name of the Open SCSI device. SENDTO STORAGE directs the command to the storage subsystem. This attribute is required unless you specified SENDTO STORAGE in a previous ASSUME command.
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. BACKUPSAC { number | name } is the SAC that controls the backup path to the device number is the SAC subdevice number on the adapter. If you specify BACKUPSAC in number format, you must also specify BACKUPLOCATION. name is the full name of the SAC location. For example:SNDA.SAC-1.GRP-1.MOD-1.
SCSIID number is the device ID of the Open SCSI device. Each device on the same SCSI interface must have a unique device ID. number is in the range 0 through 15 (6 and 7 are reserved for the adapters). The default is 2. 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. STRUCTAREASIZE number is the size (in kilobytes) of the memory area used for data structures.
attribute-spec is one or more “ADD TAPE Attributes”. ADD TAPE Attributes [ , BACKUPCPU number ] [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , COMPRESSION { ON | OFF } ] DENSITY { 1600 | 6250 } ] DEVICEID number ] HIGHPIN { ON | OFF } ] LOCATION ( group,module,slot ) ] LUN number ] MAXOPENS number ] PRIMARYCPU number ] PORTNAME number ] PROGRAM { [$vol.]subvol.
PORTNAME number is the Fibre Channel port name used by the path to a tape volume. The number should be entered as a 16 character hexadecimal number, without a leading %H. PRIMARYCPU number is the processor in which the primary IOP starts. If you omit this attribute, the processor is automatically chosen based on the physical location of the device. PROGRAM [[$vol.]subvol.]fileid is the object file name of the IOP. If not specified, PROGRAM is: $SYSTEM.SYSTEM.OTPPROCP If you specify PROGRAM as $SYSTEM.
Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. DISK $disk is the name of the disk. This disk must be in the STARTED state. POOL $pool specifies that the command is performed only on physical disks associated with the specified storage pool. 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.
Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. DISK $disk is the name of the disk. 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. If you specify LIKE, any attribute values that you explicitly specify override the attribute values of the LIKE object.
• • LUN attributes: ◦ MIRRORLUN ◦ PRIMARYLUN CLIM attributes: ◦ BACKUPCLIM ◦ MBACKUPCLIM ◦ MIRRORCLIM ◦ PRIMARYCLIM These virtual disk attributes are not copied from the LIKE object. To assign values to these attributes, you must explicitly specify them: • ANTLOCATION • PENDOPSLOCATION • POOL attribute-spec is one or more “Disk Attributes for the ALTER DISK Command” (page 230) or “Virtual Disk Attributes for the ALTER COMMAND” (page 231).
[ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , MAXLOCKSPERTCB number ] MBACKUPCLIM clim-name ] MBACKUPDEVICEID { number | ( shelf, bay ) } ] MBACKUPLOCATION {group,module,slot) ] MBACKUPPORTNAME number ] MBACKUPSAC { number | name } ] MIRRORCLIM clim-name ] MIRRORDEVICEID { number | ( shelf,bay ) } ] MIRRORLOCATION ( group,module,slot ) ] MIRRORPARTITION mirror-part-num ] MIRRORLUN
-> ALTER $DATA00, ALTNAME $SPARE99 • To change the volume name of a disk from $DATA00 to $SPARE00 and delete all files from the disk: -> ALTER $DATA00, LABEL $SPARE00 • To change the default volume name of a disk from $DATA00 to $SPARE98: -> ALTER $DATA00, VOLNAME $SPARE98 • To change the revive configuration for a disk: -> ALTER $DATA03, REVIVEPRIORITY 40, REVIVERATE 100.
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” (page 233). ALTER MON Attributes [ [ [ [ [ , , , , , BACKUPCPU number ] HIGHPIN { ON | OFF } ] MODE { NOISY | QUIET } ] PRIMARYCPU number ] PROGRAM [[$vol.]subvol.]fileid ] BACKUPCPU number is the processor in which the backup IOP starts.
ALTER [ / OUT file-spec / ] POOL $pool [ , LIKE object ] [ , attribute-spec ]... Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. POOL $pool is the storage pool process. 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.
DISKTHRESHOLD number is the threshold (as a percentage) that, with the DISKINTERVAL attribute, is used by the disk process to determine when to issue a disk-full EMS message for physical volumes in the storage pool. For example, if DISKTHRESHOLD is 75, the disk process generates an EMS message when the physical volume becomes 75 percent full. If you also specify DISKINTERVAL, the disk process generates an EMS message when the physical volume becomes 75, 80, 85, 90, and 95 percent full.
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. If not specified, PROGRAM is: $SYSTEM.SYSTEM.OPP 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.
[ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , AUTOSTART { ON | OFF } ] CAPACITYMISMATCH { ON | OFF } ] CBPOOLLEN number ] FASTBULKWRITE { ON | OFF } ] 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 } ] N
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 “ALTER SCSI Attributes”.
NUMIO number is the number of concurrent I/O operations that the Open SCSI IOP can have outstanding. This value determines the size of the allocated data-buffer area. number is in the range 1 through 15. The default is 8. 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. PRIMARYLOCATION ( group,module,slot ) is the location of the adapter that controls the primary path to the Open SCSI device.
To change the value of the SCSIID attribute: -> ALTER $DEV1, SCSIID 5 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”.
DISK AUTOSTART ON is ignored if SUBSYS AUTOSTART is OFF. For information about using this attribute, see “Mirrored Disk Placement” (page 77). BULKIO { ON | OFF } specifies whether the S-series system allows direct bulk I/O operations. The default is ON. Direct bulk I/O starts automatically and is transparent to all applications. It improves system performance during disk and tape bulk data transfers.
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. If you specify LIKE, any attribute values that you explicitly specify override the attribute values of the LIKE object. The LOCATION, SAC, and DEVICEID values are not copied from the LIKE object.
HIGHPIN { ON | OFF } specifies whether the IOP can run at a high PIN (ON, the default) or only at a low PIN (OFF). KEYGENPOLICY { KEYPERDRIVE | KEYPERTAPE | NOENCRYPTION specifies the key generation policy for the tape drive while it is stopped. You cannot use this attribute in the same command line as the NEWENCRYPTKEY attribute. NOTE: Only members of the SAFEGUARD security officer group on the local system can perform an ALTER TAPE command with the KEYGENPOLICY attribute.
ALTER TAPE Examples See the procedure for “Altering Tape Drive Attribute Values” (page 187). • To alter the data compression attribute: -> ALTER $TAPE0, COMPRESSION ON CONTROL Command CONTROL is a sensitive command.
[ , REFRESH ] [ , REPLACEBOOT [[$vol.]subvol.]fileid ] [ , SPARE [ % | %H ] lsa [ , FORCED ] ] CHECKSUM [s% | %H ] lsa (physical disks only) reads the specified sector, recomputes the sector checksum value for specified portions of a disk volume, and writes the sector back to disk again. (By comparison, FUP CHECKSUM recomputes the block checksum.) CHECKSUM corrects the checksum value for a disk address, even if the address is not within a file.
is suspended, which means that applications can time out waiting for the refresh operation to finish. REPLACEBOOT $SYSTEM.SYSnn.SYSDISC (physical disks only) replaces the disk system-load bootstrap program. $SYSTEM.SYSnn.SYSDISC is the location of the disk bootstrap program. SCF creates the temporary work file ZSYSDISC.ZSCFDISC during the REPLACEBOOT operation, installs the bootstrap program in a reserved area, and when the operation is finished, purges the ZSYSDISC.ZSCFDISC file.
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. #sac-name is the name of the SAC in the form #FCSA.SAC-sac.GRP-group.MOD-module.SLOT-slot. For example: #FCSA.SAC-2.GRP-110.MOD-2.
SPINUP causes the specified disk to be spun up. CONTROL SAC Examples • This command turns on the LED for disk 13 in enclosure 1 connected to SAC 2: -> CONTROL SAC $ZZSTO.#FCSA.SAC-2.GRP-110.MOD-2.SLOT-5, & -> DEVICEID (1,13), LED ON • This command bypasses disk 12 in enclosure 4 on the Fibre Channel loop connected to SAC 1: -> CONTROL SAC $ZZSTO.#FCSA.SAC-1.GRP-110.MOD-2.SLOT-5, & -> DEVICEID (4,12), BYPASS ON DELETE Command The DELETE command removes objects from the system configuration database.
[ , 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. DISK $disk[-B |-M |-MB ] is the disk name and, optionally, the path (backup, mirror, or mirror backup).
DELETE MON Example See the procedure for “Deleting the SMF Master Process” (page 45). To delete the SMF master process from the system configuration database: -> DELETE MON $ZSMS DELETE PARTITION Command The DELETE PARTITION command deletes the last partition or all partitions on the specified CLIM LUN. You can delete a partition only if the NonStop DISK LDEV configured to that partition are in the STOPPED state. If there is a NonStop DISK LDEV configured to that partition, SCF will ask for confirmation.
LASTPARTITION 4, & BACKUPCLIM S1002534 • This is an example of the DELETE PARTITION command with the ALLPARTITIONS option: DELETE PARTITION $ZZSTO, & SENDTO STORAGE, & PRIMARYCLIM S1002533 , & PRIMARYLUN 100 , & ALLPARTITIONS, & BACKUPCLIM S1002534 DELETE POOL Command The DELETE POOL command removes a storage pool from the system configuration database. The command syntax is: DELETE [ / OUT file-spec / ] POOL $pool [ , IGNOREINCONSISTENCY ] [ , SEL state ] Wild-card characters are supported.
DELETE PROFILE Example See “Deleting a Custom Profile” (page 76). 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 The INFO command displays system configuration information, such as the current attribute values for a specified object.
OUT file-spec directs all SCF output to the specified file. CLIM $ZZSTO.clim-name is the name of the CLIM. DETAIL returns a list of the storage devices configured to use the CLIM, including the LUN and partition number for each path. The DETAIL option is required. INFO CLIM Considerations Additional information for a CLIM is available from $ZZCIP.
LABEL (physical disks only) displays disk label information. LOG (physical 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 (physical disks only) displays information about the disk sector at logical sector address lsa.
See the display and explanation under “Displaying Profile Attributes” (page 54). INFO MON Command The INFO MON command displays configuration information about the SMF master process. The syntax is: INFO [ / OUT file-spec / ] MON $ZSMS [ , { DETAIL | OBEYFORM } ] [ , SEL state ] Wild-card characters are supported. MON $ZSMS is the SMF master process. DETAIL displays detailed configuration information. OBEYFORM displays information about the object in the format used in an ADD command.
OBEYFORM displays information about the object in the format used in an ADD command. The OBEYFORM option creates an obey file for configuring partitions on the disk. You can save the obey file and use that obey file to recreate partitions on the replacement disk. Save the obey file with a meaningful name.
INFO POOL Command The INFO POOL command displays configuration information about a storage pool. The syntax is: INFO [ / OUT file-spec / ] POOL $pool [ , { DETAIL | OBEYFORM } ] [ , SEL state ] Wild-card characters are supported. POOL $pool is the storage pool process. DETAIL displays detailed configuration information. OBEYFORM displays information about the object in the format used in an ADD command. SEL state specifies that the command affects only devices in the specified state.
-> INFO $ZZSTO.#INTERNAL-DISK-3 • To display information about all disk profiles on the system: -> INFO PROFILE $ZZSTO.* 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.
INFO TAPE Command The INFO TAPE command displays configuration information about a tape device. The syntax is: INFO [ / OUT file-spec / ] TAPE $tape [ , { DETAIL | OBEYFORM } ] [ , SEL state ] Wild-card characters are supported. TAPE $tape is the name of the tape device. DETAIL displays detailed configuration information. OBEYFORM displays information about the object in the format used in an ADD command. SEL state specifies that the command affects only devices in the specified state.
DISK $disk[-P |-M ] is the disk name and, optionally, the path (primary or mirror). LABEL $volume is the label for the disk being initialized. This attribute is ignored if you specify a disk path in this command. If you do not use this option, you must create a label using the ALTER DISK, LABEL command to give the disk a valid label. CLEARENCRYPTKEY clears encryption on an encrypted disk. This attribute changes the encryption status for a disk (single drive) while that drive is DOWN. Its mirror may be UP.
NAMES [ / OUT file-spec / ] [ object-spec ] [ , POOL $pool ] [ , SEL state ] [ , SUB subtype ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file.
PROFILE $ZZSTO.INTERNAL-DISK TAPE $TAPE4 • To display the names for all physical disks: -> NAMES $ZZSTO, SUB MAGNETIC DISK $SYSTEM $N01WHT $D0107M • $SWEETX $G02NEV $D0105M $R06WHT $FUDD $BROOK $R06NEV $DATA00 $AUDIT $R05WHT $D1103M $R05NEV $D0204 $R04NEV $D0118U $OPS $D0111M To display the names for all virtual disks: -> NAMES $ZZSTO, SUB VIRTUAL STORAGE Names SUBSYS \COMM.
Supported objects are: • “PRIMARY DISK Command” (page 264) • “PRIMARY MON Command” (page 265) • “PRIMARY POOL Command” (page 265) • “PRIMARY SCSI Command” (page 266) • “PRIMARY SUBSYS Command” (page 266) • “PRIMARY TAPE Command” (page 267) PRIMARY is a sensitive command. PRIMARY DISK Command The PRIMARY DISK command swaps the primary and backup processors for the disk process controlling the specified physical or virtual disk.
SUB { ALL | MAGNETIC | VIRTUAL } specifies that the command affects only disks of the specified type. The default is ALL. See “Attribute Descriptions for Disk Commands” (page 198) for descriptions of all attributes for disk commands. PRIMARY DISK Examples See the procedure for “Swapping Processors for a Disk” (page 109).
POOL $pool is the storage pool 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.
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. cpunumber is the processor number of the processor that you want to move storage subsystem IOPS into or away from. AWAY specifies that all storage subsystem IOPs currently running their primary processes in cpunumber be moved away from that processor.
-> PRIMARY $TAPE0 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.
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 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. $new-disk is the new volume name for the disk.
ABANDON specifies that the current REPLACE ADAPTER procedure for operational firmware should be aborted. Flash firmware replacement cannot be aborted. CPU n specifies that only IOPs in the CPU indicated by n should download the new firmware to the SACs they are using. If you do not specify a particular CPU number, all IOPs will download the new firmware, beginning with the IOPs in the highest numbered CPU FIRMWARE [[$volume.]subvol.]filename specifies the name of the new operational firmware file.
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 / ] DISK $disk[-P |-B |-M |-MB ] [ , FORCED ] [ , POOL $pool ] [ , SEL state ] [ , SUB { ALL | MAGNETIC | VIRTUAL } ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file.
FORCED terminates the IOP. SEL state specifies that the command affects only devices in the specified state. RESET MON Consideration The RESET command is ignored if the process is started. RESET MON Example See the procedure for “Resetting the SMF Master Process” (page 47). To terminate the SMF master process: -> RESET $ZSMS, FORCED RESET POOL Command The RESET POOL command puts a storage pool process into the STOPPED state, substate DOWN, ready for restarting.
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. RESET SCSI Example See the procedure for “Resetting an Open SCSI Device” (page 176).
• “START POOL Command” (page 275) • “START SCSI Command” (page 276) • “START TAPE Command” (page 276) START is a sensitive command. START DISK Command The START DISK command makes a stopped disk accessible to user processes. If needed, this command also revives the half of a mirrored volume that is in the STOPPED state, substate DOWN.
START MON Command The START MON command makes the SMF master process available. The syntax is: START [ / OUT file-spec / ] MON $ZSMS [ , DEBUG $terminal ] [ , SEL state ] [ , SPECIAL ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. MON $ZSMS is the SMF master process. 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 POOL $* • 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.
-> START TAPE $* • To start a tape drive: -> START $TAPE0 STATS Command The STATS command displays cache statistics about an object and optionally resets them. Supported objects are: • “STATS DISK Command” (page 277) • “STATS SAC Command” (page 278) STATS DISK Command The STATS DISK command displays cache statistics about physical disks.
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. SQLMX specifies that SQL/MX statistics be shown. SUB { ALL | MAGNETIC } specifies that the command affects only disks of the specified type. The default is ALL.
FORCED specifies that the command be executed without any interaction with the user. 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........ Fabric Device Changes... ISP Database Changes.... ISP Fabric LID Available ISP Hardware Errors..... LIP Errors Reported..... LIP Reset Requests...... Loop Up.................
OUT file-spec directs all SCF output to the specified file. ADAPTER $ZZSTO.#type.GRP-g.MOD-m.SLOT-s is a ServerNet adapter of type PMF, IOMF, or SNDA. g cannot have a leading zero. DETAIL displays detailed status information. FIRMWARE displays only the firmware currently running in each SAC. SACS displays detailed status for SACs but does not list devices. See “Example of a STATUS FCSA ADAPTER, SACS” (page 162). SERVERNET displays only the status of the adapter’s ServerNet paths.
DETAIL returns a list of the storage devices configured to use the CLIM, including LUN and any partition numbers. SERVERNET displays the status of the CLIM's storage ServerNet paths. ENCRYPTION returns a list of encrypted device paths that use the CLIM, including LUN and any partition numbers. The CLIM name can include wildcards. KEYMANAGER displays the status of the connection from the CLIM to key managers. The CLIM name can include wildcards.
$SAS12-MB $SAS13-MB $SAS14-MB $SAS15-MB $SAS16-MB $SAS17-MB $SASESS-MB $SAS20-MB $SAS21-MB $SAS22-MB $SAS23-MB $SAS24-MB $SAS25-MB $SE08-B • STARTED STARTED STARTED STARTED STARTED STARTED STOPPED STARTED STARTED STARTED STARTED STARTED STARTED STOPPED HARDDOWN HARDDOWN 0,351 0,350 0,349 0,348 0,347 0,346 0,357 0,345 0,362 0,361 0,360 0,359 0,358 0,355 1,314 1,315 1,316 1,317 1,318 1,319 1,326 1,320 1,321 1,322 1,323 1,324 1,325 1,328 To display the status of the S1002533's storage ServerNet paths.
DETAIL displays detailed status information. POOL $pool specifies that the command is performed only on disks associated with the specified storage pool. 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. ENCRYPTION displays encryption information for an encrypted disk. You cannot enter the ENCRYPTION option with the CONFIG or CONSISTENCY options.
-> STATUS DISK $DATA05-B, ENCRYPTION See the examples under “Displaying Information about Encrypted Disks” (page 58). • To display detailed encryption status for a disk: -> STATUS DISK $DATA05-B, ENCRYPTION, DETAIL See the examples under “Displaying Information about Encrypted Disks” (page 58). STATUS DISK Examples For Virtual Disks • To display the status of a virtual disk: -> STATUS $VDISK00 See the display and explanation under “Example of a STATUS DISK Report for Virtual Disks” (page 146).
STATUS POOL Command The STATUS POOL command displays current status information about the storage pool process. The syntax is: STATUS [ / OUT file-spec / ] POOL $pool [ , DETAIL ] [ , 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. DETAIL displays detailed status information. SEL state specifies that the command affects only devices in the specified state.
STATUS SAC Attributes [ [ [ [ [ [ [ [ , , , , , , , , EMU , DEVICEID (shelf, EMULIST LOCATION , PORTNAME wwn ] LUNLIST , PORTNAME wwn ] LUN number ] [ , DETAIL ] ] PATHSTATUS , DEVICEID (shelf, PORTLIST [ , PORTNAME wwn ] [ REPLACE , DEVICEID (shelf, 0) ] ] 0) , DETAIL ] 99) ] ] ] DETAIL displays additional information when used with LUNLIST or PORTLIST. EMU , DEVICEID (shelf , 0) displays a small subset of the inventory and status information from the environmental monitoring unit (EMU).
STORAGE - Emu Status SAC \OSM2.$ZZSTO.#FCSA.SAC-2.GRP-111.MOD-2.SLOT-1 Bay Port A WWN State Port B WWN State 1 2100000C502741B6 1 2200000C502741B6 1 2 2100000C50274285 1 2200000C50274285 1 3 2100000C5016D461 1 2200000C5016D461 1 4 2100000C502741E8 1 2200000C502741E8 1 • This command shows the worldwide names of the ports connected to SAC 1: -> STATUS SAC $ZZSTO.#FCSA.SAC-1.GRP-112.MOD-2.SLOT-4, PORTLIST STORAGE - Portlist Status SAC \IO.$ZZSTO.#FCSA.SAC-1.GRP-112.MOD-2.
00002E 2100000C504CFB71 2000000C504CFB71 Loop Login 00 First 64 bytes of Symbolic Name: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 PortId Port Name Node Name Connection 000032 2100000C504CFCA9 2000000C504CFCA9 Loop ADT State Login COS 00 First 64 bytes of Symbolic Name: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 PortId
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.
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: • “STOP DISK Command” (page 290) • “STOP MON Command” (page 291) • “STOP POOL Command” (page 291) • “STOP SCSI Command” (page 292) • “STOP TAPE Command” (page 292) STOP is a sensitive command.
• To stop all paths to a disk: -> STOP $DATA00 • To stop a virtual disk: -> STOP $VDISK00 STOP MON Command The STOP MON command stops access to the SMF master process. The syntax is: STOP [ / OUT file-spec / ] MON $ZSMS [ , FORCED ] [ , SEL state ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. MON $ZSMS is the SMF master process. FORCED specifies that the command be executed without any interaction with the user.
STOP POOL Example See “Stopping a Storage Pool” (page 141). To stop access to a storage pool process: -> STOP $POOL00 STOP SCSI Command The STOP SCSI command stops access to an Open SCSI device. The syntax is: STOP [ / OUT file-spec / ] SCSI $SCSI-device[-P |-B ] [ , FORCED ] [ , 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).
SEL state specifies that the command affects only devices in the specified state. STOP TAPE Examples See the procedure for “Stopping a Tape Drive” (page 189). To stop access to a tape drive: -> STOP $TAPE3 • To stop access to all tape drives whose names start with $TAPE: -> STOP $TAPE* STOPOPENS Command The STOPOPENS command prevents any additional opens to an object. STOPOPENS is a sensitive command.
SWITCH Command The SWITCH command designates the active a path to a device. Supported objects are: • “SWITCH ADAPTER Command” (page 294) • “SWITCH CLIM Command” (page 294) • “SWITCH DISK Command” (page 295) • “SWITCH SCSI Command” (page 296) 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.
Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. CLIM $ZZSTO.clim-name is the name of the CLIM. AWAY specifies that all active paths using the specified CLIM be switched to inactive, if possible. AWAY, FORCED specifies that all paths using the specified CLIM be stopped. This may stop the last path to a device. This command is useful prior to disconnecting a CLIM.
SWITCH [ / OUT file-spec / ] DISK $disk {-P |-B |-M |-MB } [ , POOL $pool ] [ , SEL state ] [ , SUB { ALL | MAGNETIC | VIRTUAL } ] Wild-card characters are supported. OUT file-spec directs all SCF output to the specified file. DISK $disk{-P |-B |-M |-MB } is the disk name and the path (primary, backup, mirror, or mirror backup). A single path specification is required. POOL $pool specifies that the command is performed only on disks associated with the specified storage pool.
SWITCH SCSI Examples See the procedure for “Changing the Active Data Path for an Open SCSI Device” (page 177). • To designate the backup path of an Open SCSI device as the primary access path: -> SWITCH $DEV01-B • To designate the primary path of an Open SCSI device as the primary access path: -> SWITCH $DEV02-P VERSION Command The VERSION command displays current version information. VERSION SUBSYS Command The VERSION SUBSYS command displays current version information for the subsystem manager.
A 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 NonStop Support Center (GNSC), supply this following log file: 1.
00002 STORAGE 00002 command rejected, file system error: nnnnn command is the SCF command you issued to a disk or tape device. nnnnn is the file-system error number. To get more information about the error, see “Handling File-System Error Messages” (page 298). Cause The command was rejected by the I/O process. Effect The command is not executed. Recovery Check the returned file-system error to determine what to do next.
Recovery Correct the command object type or object name and reissue the command. 00006 STORAGE 00006 INTERNAL ERROR: Case value out of range. Cause An invalid case value was generated with no associated case label. Effect The command is not executed. Recovery Report this problem immediately. See “If You Have to Contact Your Service Provider” (page 298) . 00007 STORAGE 00007 Duplicate attribute: attribute attribute is the attribute that you specified more than once in the command.
Cause All the paths to the given device can be down as a result of: • A hardware error • The operator stopping the device • The device being serviced Effect The command is not executed. 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.
Effect The command is not executed. Recovery Verify the state of the device using the STATUS command. If needed, use the RESET command to change the state of the device before retrying the operation. If online reconfiguration of a mirror drive is desired, your might need to terminate the $ZTSM process using ABORT PROCESS $ZZKRN.#TSM-SRM. Restart $ZTSM after the online reconfiguration is complete. 00013 STORAGE 00013 Invalid object name format, cmdformat expected.
Recovery Verify the database record using the SCF INFO command. If needed, reload the system using a saved version of the system configuration database. If the problem persists, contact your service provider. See “If You Have to Contact Your Service Provider” (page 298). 00016 STORAGE 00016 Unexpected error returned from system function, error: err-num, error detail: err-detailnum (errfunc). err-num is the error number returned from a system procedure.
Cause This error can be caused by different conditions: • The processor or the pair of processors that the I/O process (IOP) is configured for are not started. • The IOP is not running. • The configuration is not configured in the configuration database. Effect The command is not executed. 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.
Cause You did not specify the BACKUPCPU attribute with the command. Effect The command is not executed. 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. Recovery Reissue the command with the LOCATION attribute.
00027 STORAGE 00027 PRIMARYLOCATION and MIRRORLOCATION are equal. Cause You specified the same location for both the PRIMARYLOCATION and MIRRORLOCATION attributes. Effect The command is not executed. Recovery Reissue the command specifying the correct values for PRIMARYLOCATION and MIRRORLOCATION. 00028 STORAGE 00028 Negative response from SCSI Interface Module process, error: errnum (errdesc). errnum is the error number provided by the SCSI interface module. errdesc is the description of that error.
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 specified device is not powered on. Effect The command is not executed. Recovery Power on the device and reissue the command. If the problem persists, contact your service provider. See “If You Have to Contact Your Service Provider” (page 298). 00031 STORAGE 00031 System configuration database ($SYSTEM.ZSYSCONF.CONFIG) is locked.
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 The adapters controlling the device specified in the command are not controlled by the same processors. Effect The command is not executed. Recovery Correct the values and retry the command. The adapters controlling the device must be controlled by the same processors. 00035 STORAGE 00035 command failed.
Cause You specified different group values in the PRIMARYLOCATION and MIRRORLOCATION attributes. Effect The command is not executed. Recovery Reissue the command using the same group value for both the MIRRORLOCATION and PRIMARYLOCATION attributes. 00038 STORAGE 00038 objtype devname is not running. 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. Cause A designated processor for the device is not running.
Cause The specified object probably has other objects dependent on its existence. Effect The command is not executed. Recovery Correct the attributes and reissue the command. 00042 STORAGE 00042 Configuration database access timeout. Cause The configuration database is locked by some other process. Effect The command is not executed. Recovery Wait a few seconds and reissue the command. 00043 STORAGE 00043 Wrong path specified: object-type name.
cmd is the command that you issued. Cause You issued a RESET, FORCED command, which stops and restarts the I/O process. You can use this command only in interactive mode. Effect The I/O process is restarted if you acknowledge the verification request. Recovery Informational message only; no corrective action is required. 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.
Cause The ALTER command was issued with a storage pool attribute that is in conflict with the current configuration or was invalid or missing. Effect The command is not executed. 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.
00055 STORAGE 00055 PRIMARYLOCATION AND BACKUPLOCATION are equal. Cause You specified the same location for PRIMARYLOCATION and BACKUPLOCATION. Effect The command is not executed. Recovery Reissue the command using unique values for PRIMARYLOCATION and BACKUPLOCATION. 00056 STORAGE 00056 SMF pool communication error. Cause The command issued resulted in a error while communicating with the SMF storage pool process. Effect The command is not executed.
Recovery Answer Y or N at the prompt. 00060 STORAGE 00060 objname is in use. objname is the name of the object you specified in the command. Cause The object you issued the command to is currently in use by another requester. Effect In interactive mode, you are prompted to validate the request. In noninteractive mode, the command is not executed. Recovery In interactive mode, validate the request. In noninteractive mode, use the FORCED option to override this check.
cmd is the command you specified. sacpath is the path of the ServerNet addressable controller (SAC) specified in the command. Cause You attempted to configure a SAC for a device that the SAC does not support. Effect The command is not executed. Recovery Resolve the cause of the failure and reissue the command. 00064 STORAGE 00064 cmd failed. No CRU info; cru-info error: errnum cmd is the command you specified. cru-info is additional information about the CRU in the command you specified.
Cause The indicated SAC did not pass the power-on self-test (POST). Effect The command is not executed. Recovery Contact your service provider. See “If You Have to Contact Your Service Provider” (page 298). 00067 STORAGE 00067 cmd failed. Mismatched SAC type in sacpath. cmd is the command you specified. sacpath is the path of the ServerNet addressable controller (SAC) specified in the command. Cause The type of the SAC specified in the command does not match the SAC type in the PRIMARYSAC location.
Recovery Resolve the cause of the failure and reissue the command. 00070 STORAGE 00070 cmd failed. sacpath is already in use. cmd is the command you specified. sacpath is the path of the ServerNet addressable controller (SAC) specified in the command. Cause The device specified for the indicated path is already configured for another process. Effect The command is not executed. Recovery Resolve the cause of the failure and reissue the command.
Recovery Resolve the cause of the failure and reissue the command. 00074 STORAGE 00074 Operation invalid, REPLACE already committed. Cause You issued a REPLACE command twice. Effect The command is not executed. 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.
Effect The command is not executed. If the problem persists, contact your service provider. See “If You Have to Contact Your Service Provider” (page 298). 00078 STORAGE 00078 REPLACE DISK volname software replacement record insert, 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.
Recovery Reload the backup processor for that disk process and retry the command. 00082 STORAGE 00082 REPLACE DISK volname software replacement record update, 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 during an update of data in $SYSTEM.SYSnn.CONFALT. Effect The command fails, possibly with the replace operation half finished.
2. 3. Retry the command. If the problem persists, contact your service provider. See “If You Have to Contact Your Service Provider” (page 298). 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. For more information, refer to the Guardian Procedure Errors and Messages Manual. Cause A file-system error was returned from DSC_OLR_DEVICE_.
00088 STORAGE 00088 REPLACE DISK volname new object file 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 You initiated a replace operation, and a file-system error occurred while the new object file was being verified. Effect The command is not executed. Recovery 1. Ensure that the correct object is present. 2. Retry the command.
Recovery 1. Verify that the VPROC program: 2. • Resides on the system disk • Is executable 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 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 The command resulted in an internal NonStop C (NSC) language module error. Effect The command is not executed. Recovery 1. Retry the command. 2. If the problem persists, contact your service provider. See “If You Have to Contact Your Service Provider” (page 298).
Cause The process cannot be terminated. An OSL process cannot be terminated while it has paths in STARTED state. Effect The command is not executed. Recovery Verify the state of the paths using the STATUS command. If needed, use the STOP or ABORT command to change the state of the paths before retrying the operation. 00100 STORAGE E00100 Command failed. Too many devices configured on a SAC Cause Too many devices configured on a SAC or too many IOPs in the same processor configured to use an adapter.
Cause You tried to perform an action that is invalid for the specified disk volume. Effect The command is not executed. Recovery To determine why the command failed, consult the accompanying error message. 00105 STORAGE E00105 I/O operation failed. Cause The command failed when trying to send a command to the I/O process. Effect The command is not executed. Recovery Collect the information in the error text and contact your service representative for further assistance.
00109 STORAGE E00109 Can't access fiber because no FCSMON processes are assigned. Cause No FCSMON processes are running, or they have not yet been assigned to monitor the specified SAC. Effect The command is not executed. 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.
00115 STORAGE E00115 Lunmgr error. Cause Lunmgr returned an error. Effect The command is not executed. Recovery Correct the problem identified in the error text. 00116 STORAGE E00116 Key change is already in progress on this drive or its mirror. Cause Key change is already in progress on this drive or its mirror. Effect The command is not executed. Recovery STATUS DISK, ENCRYPTION will show where key change is in progress. 00117 STORAGE E00117 Key change is not in progress on this path.
Cause C I/O library error during communication with CLIM. Effect The command is not executed. Recovery Make sure $ZZSTO can read and write in the $SYSTEM.ZZSTO subvolume. 00122 STORAGE E00122 Can't determine IP address for CLIM. Cause Can't determine IP address for CLIM. Effect The command is not executed. Recovery Make sure that STATUS CLIM $ZZCIP.clim-name shows the CLIM in STARTED state and that INFO CLIM $ZZCIP.clim-name, DETAIL shows a Maintenance Interface IP address.
Recovery Log on as a member of the SECURITY-ENCRYPTION-ADMIN (65536) group. 00126 STORAGE E00126 This command requires an encryption license. Cause This command requires an encryption license. Effect The command is not executed. Recovery Install an NSVLE license file. Use STATUS SUBSYS command to verify that there is a valid license file installed on the NonStop system. 00127 STORAGE E00127 Filesystem error during encryption command.
Recovery Install a newer version of lunmgr on this CLIM. 1. Make sure SSH can communicate with the CLIM. 2. Run any CLIMCMD command manually for the same CLIM, which may also help to resolve this issue. If any error is reported by CLIMCMD, correct this problem and re-issue the command. -> CLIMCMD S1002531 pwd 00134 STORAGE E00134 Device WWN mismatch between PRIMARYLUN and BACKUPLUN. Cause For a PARTITION command, the device WWN of the PRIMARYLUN and the BACKUPLUN does not match.
00138 STORAGE W00138 Disk volume paths to the partition are in STOPPED state. Cause Warning: A configured NonStop disk partition is to be deleted. Effect In interactive mode, you are prompted to validate the request. In noninteractive mode, the command is not executed. Recovery Make sure the correct disk partition is to be deleted. In interactive mode, validate the request. In noninteractive mode, use the FORCED option to override this check.
Effect The command is not executed. Recovery Specify the correct source and target devices and reissue the command. 00143 STORAGE E00143 The number of disks that require WRITECACHE ENABLE or DISABLE exceeds the limit. Cause The changing of the WRITECACHE ENABLE or DISABLE affects more than the limit number of disks. Effect The command is not executed. Recovery Simplify the disk configurations so the chain of mirrored disk partitions involves fewer disks.
Recovery 1. Take online dump for the affected DP2 processors. After the online dump is completed, use SCF START DISK command to restart the affected DP2 processes, which resets the state of the processes. Online dump action must be completed before starting the disk process. 2. If the problem persists, contact your service provider. See “Upgrade and Replacement Procedures” (page 362) for additional information.
01004 STORAGE 01004 command rejected, disk contains active audit trail files. 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. 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.
Effect The command is not executed. Recovery 1. Reissue the command with the FORCED command option. 2. Execute the command from an interactive SCF prompt. 01008 STORAGE 01008 The command rejected, the disk contains numberof open files. command is the SCF command that you issued. numberof is the number of open files that exist for the device you specified in the command. Cause You issued a command that attempted to stop a disk that has open files. Effect The command is not executed.
01011 STORAGE 01011 The command operation could leave data in an INCONSISTENT state on volname. command is the SCF command that you issued. volname is the name of the volume that you specified in the command. Cause You issued the CONTROL DISK, CHECKSUM command in noninteractive mode. The CONTROL DISK, CHECKSUM command is available only in interactive mode. In interactive mode, you are prompted to verify the operation. Effect The checksum operation is not performed. Recovery 1.
Effect The disk sector is not spared. Recovery 1. Verify you used the correct sector address. 2. Reissue the command with the correct address, if needed. 01015 STORAGE 001015 The STATS DISK, RESET command will reset the counters used to compute the cache performance statistics on volname. volname is the name of the volume that you have specified a statistical reset for. Cause You issued the STATS DISK, RESET command in noninteractive mode.
01018 STORAGE 01018 command failed, reason unknown. command is the SCF command that you issued. Cause You issued a command to make a path switch but the storage subsystem manager process detected that it did not occur, even though no error was returned from the disk process. Effect The path switch did not occur. Recovery Check the EMS log for messages pertaining to the problem. 01019 STORAGE 01019 command rejected, disk is not demountable. command is the SCF command that you issued.
01022 STORAGE 01022 ALTER DISK volname, LABEL failed, work file error: err-num. volname is the name of the volume that you specified in the command. err-num 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. Recovery Contact your service provider. See “If You Have to Contact Your Service Provider” (page 298).
Recovery Contact your service provider to obtain a new bootstrap file and retry the command. See “If You Have to Contact Your Service Provider” (page 298). 01026 STORAGE 01026 CONTROL DISK volname, REPLACEBOOT failed (wrong bootstrap file for processor type). volname is the name of the volume that you specified in the command. Cause An incompatibility between the bootstrap file and the processor type prevented the REPLACEBOOT operation from finishing. Effect The REPLACEBOOT operation is not performed.
Cause A temporary work file error prevented the bootstrap replacement. Effect The REPLACEBOOT operation is not performed. Recovery Correct the problem indicated by the error number and reissue the command. 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.
Effect The system configuration database is updated with the new name. Recovery Informational message only; no corrective action is required. 01034 STORAGE 01034 Resuming suspended disk revive on devname. devname is the name of the device you specified in the command. Cause The disk revive operation was restarted in response to an SCF START DISK command. Effect The revive operation continues from the point where it was suspended. Recovery Informational message only; no corrective action is required.
Recovery Replace the disk with a formatted disk, or format the disk before retrying the REVIVE command. 01038 STORAGE 01038 Name conflict, the name is already in use on the system. Cause A name conflict was detected in a RENAME or ALTER, LABEL command. Effect The command is not executed. Recovery Resolve the name conflict before retrying the command. 01039 STORAGE 01039 A disk label discrepancy was detected. Cause The storage subsystem manager detected a discrepancy in the disk label.
Effect In interactive mode, you are prompted to confirm the operation. In noninteractive mode the operation is performed. Recovery Copy the SCF program to a disk other than $SYSTEM before continuing. Do not exit SCF without having another copy on another disk. 01043 STORAGE 01043 Operation succeeded, disk name contains num open files name is the name of the disk that has open files. num is the number of open files on the disk. Cause You issued a STOPOPENS command for a disk with open files.
Recovery Remove the disk from the storage pool and reissue the command. 01047 STORAGE 01047 Not allowed: The disk is audited. Cause This command, if executed, would leave the TMF product in an inconsistent state. Cause The command is not executed. Recovery Disable the disk under the TMF product and reissue the command. 01048 STORAGE 01048 Sector secnum is out of range. Maximum is maxsecnum secnum is the sector number you specified with the command.
Recovery Either: • Reissue the SCF command interactively. • Remove the command from the SCF command file. 01051 STORAGE 01051 The label is bad on disk device devname. The label was not altered. devname is the name of the device you specified in the command. Cause The label is bad on the indicated disk. Either the time stamp or the last mounted operating system (OS) field is null. Effect The command is not executed. Recovery Either: • Revive the disk volume using the SCF START DISK command.
command is the SCF command that you issued. devname is the name of the device you specified in the command. attribute is the attribute that you specified with an invalid value. Cause You attempted to decrease the value of an attribute while the I/O process is in a STARTED state. Effect The command is not executed. Recovery Either: • Correct the value for the indicated attribute. • Place the I/O process in a STOPPED state and reissue the command.
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 You're asked whether to perform the mirror-related configuration change while the disk volume is in a started state.
2. Issue a command specifying the previous configuration. The storage subsystem manager then returns the configuration to its original setting. For example, if you tried to add a mirror disk drive to a disk named $DATA, issue this SCF command.
Effect The command is executed. The checksum is corrected. This is a warning. Recovery Find the data on the sector using INFO DISK, SECTOR and then verify that it is valid. 01063 STORAGE E01063 Command failed. Another disk using the same adapter shares one CPU but not both CPUs. Cause Another disk using the same adapter shares one CPU but not both CPUs. 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.
Recovery This is a warning. No action is required, but HP recommends that the volume be connected to an HP rack mount UPS, which will give the drives enough time to write cached data to the media after the processor stops writing in the event of power loss. The SUBSYS attribute UPS should be ON either before WRITECACHE is enabled or before the IOP is started. Otherwise, the IOP will run with WRITECACHE disabled. 01067 STORAGE W01067 Enabling FASTBULKWRITE can impact data integrity on a volume.
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 The command you issued was rejected by SMF. Effect The command is not executed. Recovery Check the returned file-system error to determine what to do next. 09004 STORAGE 09004 cmd rejected, SMF MON file system error: errnum.
09007 STORAGE 09007 Required attribute not specified: ANTLOCATION Cause You did not specify the ANTLOCATION attribute in the command you issued. Effect The command is not executed. Recovery Reissue the command and include the ANTLOCATION attribute. 09008 STORAGE 09008 Required attribute not specified: PENDOPSLOCATION Cause You did not specify the PENDOPSLOCATION attribute in the command you issued. Effect The command is not executed. Recovery Reissue the command and include the PENDOPSLOCATION attribute.
09012 STORAGE 09012 Invalid subvolume name. It must begin with ZYS. Cause You issued a command using a subvolume name that did not begin with ZYS. Effect The command is not executed. Recovery Reissue the command using a proper subvolume name that begins with ZYS. 09013 STORAGE 09013 SMF dependency failure: Unable to obtain information from process name. name is the name of the process that the storage subsystem is trying to get information from.
Effect The command is not executed. Recovery Use the TMF product to enable the disk volume and reissue the command. 09017 STORAGE 09017 Invalid ANTLOCATION. The volume has PHYSVOLSELECT OFF. Cause You issued a command that specifies an ANTLOCATION for a disk that will not accept the file because PHYSVOLSELECT OFF disallows writing the file to that disk. Effect The command is not executed.
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. 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. Cause The configuration record is not readable. Effect The command is not executed.
Cause You are trying to delete a storage pool that still has virtual disks associated with it. Effect The command is not executed. Recovery Delete the virtual disks associated with the storage pool and then delete the storage pool. Use the SCF INFO POOL, DETAIL command to see which virtual disks are associated with the storage pool. 09026 STORAGE 09026 cmd failed. Mismatched attribute in attname. cmd is the command that you issued. attname is the name of the attribute with the mismatched value.
Effect The command is not executed. Recovery Delete the disks associated with the storage pool, then delete the storage pool. Use the SCF INFO POOL, DETAIL command to see which disks are associated with a storage pool. 09029 STORAGE 09029 The attribute refers to a device of an incorrect type. Cause You specified an attribute that is incompatible with the type of device specified in the command. Effect The command is not executed. Recovery Change the command so that the device and attribute match.
Recovery Issue the command with the correct names. 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. Recovery Make the request again, using the required attribute. 09034 STORAGE 09034 devname cannot be configured on a sacname which is on an adaptername. devname is the name of the device you specified in the command.
Recovery Change either the primary SAC or the backup SAC so that they have different controller IDs. The SCSI Bus IDs of the SACs on a ServerNet/DA are always 6 or 7.
B Upgrade and Replacement Procedures This section describes: • “Replacing a Tape Drive” (page 362) • “Replacing an Open SCSI Device” (page 362) • “Upgrading a Mirrored Volume Online” (page 363) 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.
Upgrading a Mirrored Volume Online You can replace online each disk in a mirrored volume (one at a time). The replacement disk can be a higher capacity or faster speed. For example, you can replace 8-GB disks with 36-GB disks without bringing down the entire volume. NOTE: You can only use a smaller replacement disk if it is able to accommodate the largest used sector address. Please note that because of fragmentation, the largest used sector address can be much larger than the actual disk space used. 1.
Glossary $ZCNF The name of the configuration utility process. $ZZSTO The name of the storage subsystem manager process. 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).
command A demand for action by or information from a subsystem or the operation demanded by an operator or application. A command is typically conveyed as an interprocess message from an application to a subsystem. command file An EDIT file that contains a series of commands and serves as a source of command input. Compaq TSM Identifies a client or server software component used to manage or service HP NonStop S-series servers.
enclosure interleaving On HP NonStop S-series systems, configuring a mirrored disk volume to use two separate system enclosures. For internal disk drives, the two disk drives of the mirrored volume can be in separate enclosures. For 45xx disk drives, the adapters connected to the two disk drives of the mirrored volume can be in separate enclosures. Enterprise Storage System (ESS) A collection of disks, their controllers, and the disk cache in a standalone cabinet or cabinets.
HP Integrity NonStop™ NS-series servers The HP NonStop servers having product numbers beginning with the letters NS. These servers implement the ServerNet architecture and run the HP NonStop operating system. HP NonStop™ operating system The operating system for HP NonStop systems. HP NonStop™ S-series servers The set of servers in the HP NonStop range of servers having product numbers beginning with the letter S.
KB See kilobyte (KB). Kernel subsystem In G-series RVUs, the subsystem for configuration and management of the Subsystem Control Facility (SCF) subsystem managers that are generic processes, some system attributes, and the ServerNet X and Y fabrics. kilobyte (KB) A unit of measurement equal to 1024 bytes. See also gigabyte (GB), megabyte (MB), and terabyte (TB). LDEV Logical device. The HP term for a disk in the ESS. load 1.
object One or more of the devices, lines, processes, and files in a subsystem; any entity subject to independent reference or control by one or more subsystems. In the Subsystem Control Facility (SCF), each object has an object type and object name. object name A unique name for an SCF object within a subsystem.
processor multifunction (PMF) CRU 1. A HP NonStop S-series customer-replaceable unit (CRU) that contains a power supply, service processor (SP), ServerNet router 1, Ethernet controller, three ServerNet addressable controllers (SACs), and a processor and memory system in a single unit. The PMF CRU consists of three subassemblies: the processor and memory board (PMB), the multifunction I/O board (MFIOB), and the power supply subassembly. 2.
SNDA See ServerNet device adapter (ServerNet/DA). 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 location-independent naming, storage pools, and virtual disks on HP NonStop S-series systems.
system configuration database The database file on the $SYSTEM.ZSYSCONF subvolume that contains configuration information for all system objects that can be configured by the Subsystem Control Facility (SCF). Configuration information for all system objects that can be configured by SYSGENR is contained on the $SYSTEM.SYSnn subvolume. See also configuration file and SYSnn subvolume. system enclosure An enclosure for NonStop S-series system components.
Index Symbols $ldev number, 28 $SYSTEM see System disk $SYSTEM.ZSYSCONF.
adding a disk, 73 finding installed nonconfigured disks, 48 internal disks, 73 Automatic revival of disks, 78 see also AUTOREVIVE attribute Automatic sector reallocation automatically spares defective sectors, 104 during a revive operation, 100 Automatic sector reallocation, displaying information about, 104 Automatic starting of disks, 74 see also AUTOSTART attribute AUTOREALLOCATE see Automatic sector reallocation AUTOREVIVE attribute ALTER SUBSYS command, 240 description of, 199 effect on automatic confi
STATUS command, 280 SWITCH command, 294 CLIM-attached disks ADD DISK example, 83 description of, 71 CLuster I/O module see CLIM Command file behavior of SCF commands in, 191 helps change configuration safely, 27 using OBEYFORM results in, 27 Command timeouts, 192 COMPRESSION attribute ADD TAPE command, 226 ALTER TAPE command, 242 CONFIG attribute INFO DISK command, 254 INFO DISK display, 50 CONFIG-ERROR substate, description of, 34 Configuration information See INFO command, 253 Configuration state of virtu
configuration information for, 49 configuring and managing, 70 correcting doubly allocated file extents, 106 deleting, 93 initializing, 92 load balancing, 119 partitioning, 92 preventing file opens, 109 renaming, 88 replacing the bootstrap program, 107 resetting, 103 resolving disk-naming conflicts, 88 See Physical disks, 70 sparing a defective sector, 104 starting, 97 stopping, 101 virtual disks, relationship to, 143 DISKTHRESHOLD attribute ADD POOL command, 220 ALTER POOL command, 235 Displaying configure
description of, 34 resetting, 103 STATUS command display, 102 HIGHPIN attribute ADD MON command, 216 ADD POOL command, 220 ADD SCSI command, 224 ADD TAPE command, 226 ALTER DISK command changing, 85 description of, 204 ALTER MON command, 233 ALTER POOL command, 235 ALTER SCSI command, 238 ALTER TAPE command, 243 I IGNOREINCONSISTENCY attribute DELETE DISK command, 249 DELETE POOL command, 251 description of, 204 INACCESSIBLE substate, description of, 34 INFO ADAPTER command IOMF display example, 155 PMF di
LOCATION attribute ADD TAPE command, 226 ALTER TAPE command, 243 STATUS SAC command, 286 Location-independent naming of virtual disks, 144 Lock key space, set by LKIDLONGPOOLLEN attribute, 205 LOG attribute, INFO DISK command description of, 255 spared sectors, 63 Logical device number see ldev number Logical sector address used in CHECKSUM attribute of CONTROL DISK command, 245 used in SECTOR attribute of INFO DISK command, 255 used in SPARE attribute of CONTROL DISK command, 246 Logical unit number (LUN)
STATUS command, 284 STOP command, 291 N NAMEMASK attribute, 208 NAMES command, 261 Naming conventions automatically configured disks, 208 Open SCSI devices, 174 Naming, location-independent, 144 NEWENCRYPTKEY attribute ALTER TAPE command, 243 NEWENCRYPTKEY attribute, description of, 209 NONAUDITEDINSERT attribute changing, 85 description of, 209 Nonconfigured disks, finding, 48 Noninteractive mode, commands, 191 Nonmirrored disks changing a mirrored volume into, 79 changing into a mirrored volume, 79 Nonse
ADD command, 218 ALTER command, 233 DELETE command, 251 description of, 36 INFO command, 258 PRIMARY command, 265 RESET command, 272 START command, 275 states and substates, 36 STATUS command, 285 STOP command, 291 Pool, storage adapter deletion impact on, 166 adding, 137 adding a disk to, 138 altering, 139 configuration information for, 134 deleting, 140 description of, 134 removing a disk from, 138 resetting, 142 starting, 141 status information for, 136 swapping processors for, 142 Port Name disks, 52 Fi
description of, 212 R REBUILDDFS attribute, CONTROL DISK command, 245 Rebuilding disk free space table, 106 RECOVERYTIMEOUT attribute changing, 85 description of, 212 RECSIZE attribute ADD SCSI command, 224 ADD TAPE command, 227 ALTER SCSI command, 239 ALTER TAPE command, 243 REFRESH attribute, CONTROL DISK command, 245 Refresh operation ABORT DISK command, 102 STOP DISK command, 290 Remirroring disks online, 79 Remote Duplicate Database Facility (RDF) performance, AUDITTRAILBUFFER attribute of ALTER DISK
SWITCH command for, 296 SCSIID attribute ADD SCSI command, 225 ALTER SCSI command, 239 Sector %H2 or %H3, do not spare, 105 SECTOR attribute INFO DISK command, 255 Sector reallocation, automatic see Automatic sector reallocation SEL attribute INFO DISK command, 255 STATUS DISK command, 283 SENDTO STORAGE attribute ADD DISK command, 195 ADD MON command, 215 ADD PARTITION command, 217 ADD POOL command, 219 ADD PROFILE command, 222 ADD SCSI command, 223 ADD TAPE command, 225 DELETE DISK command, 249 DELETE PAR
STATS DISK command collects cache configuration data, 87 disk examples, 60 STATUS ADAPTER command IOMF display example, 160 PMF display example, 158 SNDA display example, 161 STATUS command, 279 STATUS DISK command disk display examples, 64 encryption examples, 58 virtual disk examples, 146 STATUS MON command, examples, 43 STATUS POOL command, examples, 136 STATUS SCSI command, configuration examples, 173 STATUS SUBSYS command, example, 41 STATUS TAPE command encryption examples, 184 STATUS TAPE command, ex
object name, 39 PRIMARY command, 267 RESET command, 273 START command, 276 states and substates, 39 STATUS command, 289 STOP command, 292 Tape path configuration, 179 TEST substate, description of, 34 Timeouts for commands, 192 Topology branch description of, 118 G06.10 and earlier example, 123 G06.
