hit counter script
IBM XIV User Manual

IBM XIV User Manual

Storage system
Hide thumbs Also See for XIV:
Table of Contents

Advertisement

Version 11.4.x
IBM XIV Storage System User Manual
GC27-3914-05

Advertisement

Table of Contents
loading

Summary of Contents for IBM XIV

  • Page 1 Version 11.4.x IBM XIV Storage System User Manual GC27-3914-05...
  • Page 2 Order publications through your IBM representative or the IBM branch office serving your locality. © Copyright International Business Machines Corporation 2008, 2012. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
  • Page 3: Table Of Contents

    Chapter 4. LUN Mapping Management Abbreviations . Parameter Definitions . Accessibility features for IBM XIV Storage System . Chapter 5. Volume Snapshot Management ... . 63 Chapter 2. Host and Cluster Changing a Snapshot Deletion Priority .
  • Page 4 Setting VPD Parameters . . 167 Deleting the Data Migration Process. . 243 Showing Values of Maintenance Module Listing Data Migration Statuses . . 244 Parameters. . . 169 Testing the Data Migration Definition . . 245 IBM XIV Storage System User Manual...
  • Page 5 Testing the Traceroute to a Remote IP . . 321 Deactivates IBM Hyper-Scale Mobility Migration Testing the Traceroute to a Remote IP . . 322 Aborts a Defined or Activated IBM Hyper-Scale Updating an IP Interface . 323 Mobility Process . . 252 Defines a New IPSec Connection .
  • Page 6 . 448 Resuming System Traces . 448 Glossary ... . . 639 Listing Status of System Traces . 449 Create traces snapshot . . 450 IBM XIV Storage System User Manual...
  • Page 7: Chapter 1. Introduction

    Chapter 1. Introduction Reliable high-end storage systems are critical for the successful operation of businesses. The XIV Grid Storage Platform is designed to guarantee secure, dependable, enterprise-grade data storage and access, straightforward and non-intrusive installation and upgrade and full scalability.
  • Page 8: Documentation Conventions

    Accessibility features ® ® These are the major accessibility features associated with the IBM Storage System: v You can use screen-reader software and a digital speech synthesizer to hear what is displayed on the screen. PDF documents have been tested using Adobe Reader version 7.0.
  • Page 9 See your browser or screen-reader software Help for a list of shortcut keys that it supports. IBM XIV and accessibility See the IBM Human Ability and Accessibility Center http://www-03.ibm.com/ able/ for more information about the commitment that IBM has to accessibility. Chapter 1. Introduction...
  • Page 10 IBM XIV Storage System User Manual...
  • Page 11: Chapter 2. Host And Cluster Management

    Chapter 2. Host and Cluster Management The following sections describe the XIV Command Line Interface (XCLI) for host and cluster management. The sections are listed as follows: cluster_add_host(Adds a host to a cluster.) cluster_create(Creates a new cluster.) cluster_delete(Deletes a cluster.) cluster_list(Lists a specific cluster or all of them.)
  • Page 12: Adding A Host To A Cluster

    The host or cluster is getting a single SCSI unit attention message, even if the change affects multiple volumes. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 13: Creating A Cluster

    Completion Codes: v HOST_BAD_NAME Host name does not exist v CLUSTER_BAD_NAME Cluster name does not exist v HOST_BELONGS_TO_ANOTHER_CLUSTER Host already belongs to another cluster v HOST_AND_CLUSTER_HAVE_CONFLICTING_MAPPINGS Host mapping conflicts with cluster mapping v HOST_AND_CLUSTER_HAVE_DIFFERENT_MAPPING_TYPE Host mapping type is not the same as the cluster mapping type Creating a Cluster Creates a new cluster.
  • Page 14: Listing Clusters

    This command lists a specific cluster or all of them. For each cluster, a special type and a comma separated list of hosts is listed. Name Default Position name Name hosts Hosts type Type creator Creator user_group User Group IBM XIV Storage System User Manual...
  • Page 15: Removing A Host From A Cluster

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Disallowed Removing a Host from a Cluster Removes a host from a cluster. cluster_remove_host cluster=ClusterName host=HostName Parameters: Name Type Description Mandatory...
  • Page 16: Renaming Clusters

    The FC port address or iSCSI initiator (port) name assigned to the host must be unique per XIV system. The FC port name must be exactly 16 characters long, in hexadecimal form. IBM XIV Storage System User Manual...
  • Page 17: Defining A New Host

    Remote port address is illegal or does not belong to the remote target v PORT_EXISTS Port is already defined v OLVM_LINK_IS_NOT_UP IBM Hyper-Scale Mobility link is not up. The mapping list cannot be updated. v REMOTE_MAX_VIRTUAL_HOSTS_REACHED Maximum number of remote virtual hosts already defined Defining a New Host Defines a new host to connect to the XIV system.
  • Page 18: Access Control

    CHAP is secret enabled This command defines a host that will attach to the IBM XIV Storage System. The name of the host must be unique in the system. Note: Use the Adding a Port to a Hostcommand to add port addresses to this host.
  • Page 19: Deleting A Host

    User Category Permission Read-only users Disallowed Technicians Disallowed Warnings: v ISCSI_CHAP_NAME_AND_SECRET_NOT_UNIQUE Both iSCSI CHAP name and secret are already used by another host. Are you sure you want to reuse those values? Completion Codes: v HOST_NAME_EXISTS Host name already exists v MAX_HOSTS_REACHED Maximum number of hosts already defined v CLUSTER_BAD_NAME...
  • Page 20: Listing Hosts

    Performance Class This command lists all the hosts that have been defined in the XIV system. A host name can be specified to list only a specific host or all the hosts. The list contains the following comma separated information:...
  • Page 21: Listing Ports

    Name Default Position cluster Cluster perf_class Performance Class iSCSI CHAP Name iscsi_chap_ name Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Disallowed Listing Ports Lists all the ports of a host host_list_ports host=HostName Parameters: Name...
  • Page 22: Removing A Port From A Host

    Port name for iSCSI Host is illegal Troubleshooting: Port names for iSCSI Hosts must contain only printable characters. v OLVM_LINK_IS_NOT_UP IBM Hyper-Scale Mobility link is not up. The mapping list cannot be updated. v TARGET_PORT_BAD_ADDRESS IBM XIV Storage System User Manual...
  • Page 23: Renaming A Host

    Remote port address is illegal or does not belong to the remote target v HOST_PORT_EXISTS Host with this port ID already defined v MAX_PORTS_REACHED Maximum number of ports already defined in the system v PORT_EXISTS Port is already defined v REMOTE_MAX_VIRTUAL_HOSTS_REACHED Maximum number of remote virtual hosts already defined Renaming a Host Renames a host.
  • Page 24: Updating A Host Definition

    Changing the chap_name and/or chap_secret: v A warning message will be presented stating that the changes will apply only on the next time the host is connected. Example: host_update host iscsi_chap_name iscsi_chap_secret IBM XIV Storage System User Manual...
  • Page 25: Mapping A Volume To A Host Or Cluster

    Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Warnings: v ISCSI_CHAP_NAME_AND_SECRET_NOT_UNIQUE Both iSCSI CHAP name and secret are already used by another host. Are you sure you want to reuse those values? v ISCSI_CHAP_SECRET_NOT_UNIQUE iSCSI CHAP secret is already used by another host.
  • Page 26 'Host' is part of a cluster. Are you sure you want to map this volume only for that specific host? v ARE_YOU_SURE_YOU_WANT_TO_MAP_VOLUME Are you sure you want to map volume Volume, which is already mapped to another host/cluster? Completion Codes: v HOST_BAD_NAME Host name does not exist IBM XIV Storage System User Manual...
  • Page 27: Listing The Mapping Of Volumes To Hosts Or Clusters

    MAX_PORTS_REACHED Maximum number of ports already defined in the system v OLVM_LINK_IS_NOT_UP IBM Hyper-Scale Mobility link is not up. The mapping list cannot be updated. v HOST_PORT_EXISTS Host with this port ID already defined v REMOTE_MAX_VIRTUAL_HOSTS_REACHED Maximum number of remote virtual hosts already defined Listing the Mapping of Volumes to Hosts or Clusters Lists the mapping of volumes to a specified host or cluster.
  • Page 28: User Category

    Allowed Security administrator Disallowed Read-only users Allowed Technicians Disallowed Completion Codes: v HOST_BAD_NAME Host name does not exist v CLUSTER_BAD_NAME Cluster name does not exist v TOO_MANY_MAPPINGS There are too many mappings to display IBM XIV Storage System User Manual...
  • Page 29: Setting The Special Type Of Hosts Or Clusters

    Setting the Special Type of Hosts or Clusters Sets the special type of a host or a cluster. special_type_set <host=HostName | cluster=ClusterName> type=<default|hpux|zvm|esx> Parameters: Name Type Description Mandatory host Object name Host name. cluster Object name Cluster name. type Enumeration Special map type.
  • Page 30: Unmapping A Volume From A Host Or Cluster

    This command unmaps a volume from a host or a cluster. The command to unmap from a cluster will unmap the volume from all the hosts that are contained in that cluster. IBM XIV Storage System User Manual...
  • Page 31: Host With This Port Id Already Defined

    VOLUME_IS_NON_PROXY_OLVM_DESTINATION The volume is in an IBM Hyper-Scale Mobility migration state. v OLVM_LINK_IS_NOT_UP IBM Hyper-Scale Mobility link is not up. The mapping list cannot be updated. v ISCSI_HOST_ILLEGAL_PORT_NAME Port name for iSCSI Host is illegal Troubleshooting: Port names for iSCSI Hosts must contain only printable characters.
  • Page 32: Set The Default Idle Time For Unmapping A Volume

    Name Type Description Mandatory perf_class String Name of a Performance Class This command creates a Performance Class. The Performance Class name must be unique. Up to 4 classes can be created. Example: perf_class_create perf_class=p1 IBM XIV Storage System User Manual...
  • Page 33: Deleting A Performance Class

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v PERF_CLASS_EXISTS Performance Class already exists. v MAX_PERF_CLASSES_REACHED Maximum number of Performance Class is already defined. Deleting a Performance Class Deletes a Performance Class perf_class_delete perf_class=perfClassName...
  • Page 34: Renaming A Performance Class

    Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v PERF_CLASS_EXISTS Performance Class already exists. v PERF_CLASS_BAD_NAME Performance Class does not exist IBM XIV Storage System User Manual...
  • Page 35: Listing Details On Performance Classes

    Listing Details on Performance Classes Lists Performance Classes perf_class_list [ perf_class=perfClassName ] Parameters: Name Type Description Mandatory Default perf_class String Name of a All Performance Performance Class. classes. If left unspecified - all performance classes will be listed. This command lists details of a specified Performance Class, or all Performance Classes.
  • Page 36: Removing A Host From Its Performance Class

    Parameters: Name Type Description Mandatory host Object name Name of a host that will be removed from its Performance Class This command removes a host from its Performance Class. Example: perf_class_remove_host host=h1 IBM XIV Storage System User Manual...
  • Page 37: Setting The Rate For A Performance Class

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v HOST_BAD_NAME Host name does not exist v PERF_CLASS_DOES_NOT_CONTAIN_ANY_HOSTS Performance Class is already empty Setting the Rate for a Performance Class Sets the rate for a Performance Class perf_class_set_rate perf_class=perfClassName [ max_io_rate=iops ] [ max_bw_rate=bw ] Parameters:...
  • Page 38: Listing Host Profiles

    Lists all Host Profiles or a specific one. Name Default Position host_name Host Name update_time Update Time profile Profile Example: xcli -u -c XIV1 host_profile_list host Output: Host Name Update Time Profile ---------------------------- --------------------- ----------------------- host1 2012-05-09 22:54:36 Windows 7 IBM XIV Storage System User Manual...
  • Page 39: Updates The Host Profile

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed Updates the Host Profile updates the host profile host_profile_set profile_value=Profile Parameters: Name Type Description Mandatory String The host profile value length up to 1024 profile_ characters...
  • Page 40: Removes The Profile Of The Specified Host

    No profile defined for the requested host Enable Host Profiler Functionality Enable host profiler functionality host_profiler_enable Enable host profiler functionality Example: xcli -u -c XIV1 host_profiler_enable Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed IBM XIV Storage System User Manual...
  • Page 41: Disable Host Profiler Functionality

    User Category Permission Application administrator Allowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Disable Host Profiler Functionality Disable host profiler functionality host_profiler_disable Disable host profiler functionality Example: xcli -u -c XIV1 host_profiler_disable Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed...
  • Page 42 IBM XIV Storage System User Manual...
  • Page 43: Chapter 3. Volume Management

    Chapter 3. Volume Management The following sections describe the XIV Command Line Interface (XCLI) for volume management. Other commands that are relevant to this topic are: Listing Volumes, Renaming a Volume, Moving a Volume between Storage Pools . See also:...
  • Page 44: Listing Reservation Keys

    Lists reservation keys. Example: reservation_key_list vol=Vol2 Output: Initiator Port Volume Name Reservation Key ------------------ ------------------ ----------------- 100000062B151C3C vol-dmathies-0a7 100000062B151C3C vol-dobratz-23a Name Default Position initiator_port Initiator Port Initiator ISID initiator_ port_isid vol_name Volume Name reg_key Reservation Key IBM XIV Storage System User Manual...
  • Page 45: Listing Volume Reservations

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Disallowed Completion Codes: v VOLUME_BAD_NAME Volume name does not exist Listing Volume Reservations Lists volume reservations. reservation_list [ vol=VolName ] Parameters: Name Type...
  • Page 46: Finding A Volume Based On A Scsi Serial Number

    This command prints the volume name according to its specified SCSI serial number. Name Default Position name Name size Size (GB) size_MiB Size (MiB) master_name Master Name cg_name Consistency Group pool_name Pool creator Creator IBM XIV Storage System User Manual...
  • Page 47 Name Default Position proxy Proxy capacity Capacity (blocks) modified Modified sg_name Snapshot Group Name Deletion Priority delete_ priority locked Locked serial Serial Number snapshot_time Snapshot Creation Time Master Copy Creation Time snapshot_time_ on_master Snapshot Internal Role snapshot_ internal_role snapshot_of Snapshot of sg_snapshot_of Snapshot of Snap Group mirrored...
  • Page 48: Copying Volumes

    ID, lock state, creation time and all other attributes. Immediately after the completion of the command, the volumes are independent of each other and are valid for any further operations (including deletion). IBM XIV Storage System User Manual...
  • Page 49 There is not enough free space in the Storage Pool that contains the target In the following example, the -y option suppresses the "ARE_YOU_SURE_YOU_WANT_TO_COPY_VOLUME Y/N" prompt. The volume can't be copied if it is part of an IBM Hyper-Scale Mobility relation and in Proxy phase. Example:...
  • Page 50: Creating A Volume

    Snapshot is formatted v VOLUME_TOO_BIG_TO_COPY Volume is too large to be copied v TARGET_VOLUME_HAS_OLVM This target volume is part of an IBM Hyper-Scale Mobility relation. v VOLUME_IS_OLVM_PROXY The volume is in an IBM Hyper-Scale Mobility Proxy phase. Creating a Volume Creates a new volume.
  • Page 51 Name Type Description Mandatory pool Object name The name of the Storage Pool to which the volume belongs. This command creates a new volume. The name of the volume must be unique in the system. Space for the volume is allocated from the specified Storage Pool and the volume belongs to that Storage Pool.
  • Page 52: Deleting A Volume

    Deletes a volume. vol_delete vol=VolName Parameters: Name Type Description Mandatory Object name Name of the volume to delete. This command deletes a volume. All data stored on the volume is lost and cannot be restored. IBM XIV Storage System User Manual...
  • Page 53 This command cannot be applied to a snapshot. To delete a snapshot, use Deleting a Snapshot. All storage space allocated (or reserved) for the volume is freed and returned to the volume's Storage Pool. The volume is removed from all LUN Maps that contain a mapping of the volume. This command deletes all snapshots associated with this volume.
  • Page 54: Formatting A Volume

    If a mirrored volume is not consistent then its ELCS is protected and cannot be deleted. v VOLUME_HAS_OLVM IBM Hyper-Scale Mobility relation is defined for this volume v VOLUME_IS_OLVM_PROXY The volume is in an IBM Hyper-Scale Mobility Proxy phase. Formatting a Volume Formats a volume. vol_format vol=VolName Parameters:...
  • Page 55: Listing Volumes

    Command executed successfully Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Warnings: v ARE_YOU_SURE_YOU_WANT_TO_FORMAT_VOLUME Volume Volume may contain data. Formatting will cause data loss. Are you sure you want to format volume Volume? Completion Codes: v VOLUME_BAD_NAME...
  • Page 56 Capacity (blocks) modified Modified sg_name Snapshot Group Name Deletion Priority delete_ priority locked Locked serial Serial Number snapshot_time Snapshot Creation Time Master Copy Creation Time snapshot_time_ on_master Snapshot Internal Role snapshot_ internal_role snapshot_of Snapshot of IBM XIV Storage System User Manual...
  • Page 57 Name Default Position sg_snapshot_of Snapshot of Snap Group mirrored Mirrored locked_by_pool Locked by Pool used_capacity Used Capacity (GB) Used Capacity (MiB) used_capacity_ short_lived_io Short Live IO enable_VAAI VAAI enabled VAAI disabled by user user_disabled_ VAAI Snapshot Format snapshot_ format ssd_caching SSD Caching State Use SSD Caching Default State use_ssd_...
  • Page 58: Locking A Volume

    If applied on a volume that is part of an IBM Hyper-Scale Mobility relation, the command has to be acknowledged by both source and destination volumes.
  • Page 59: Renaming A Volume

    Renaming a snapshot does not change the name of its master volume. Renaming a master volume does not change the names of its associated snapshots. If applied on a volume that is part of an IBM Hyper-Scale Mobility relation, the command has to be acknowledged by both source and destination volumes.
  • Page 60: Resizing A Volume

    If a mirrored volume is not consistent then its ELCS is protected and cannot be deleted. v OLVM_ERROR IBM Hyper-Scale Mobility error. v COMMAND_NOT_SUPPORTED_FOR_OLVM_VOLUMES This command is not supported for IBM Hyper-Scale Mobility volumes. Resizing a Volume Resizes a volume. vol_resize vol=VolName < size=GB | size_blocks=BLOCKS > [ shrink_volume=<yes|no> ] [ force_on_inactive_mirror=<yes|no> ]...
  • Page 61 Parameters: Name Type Description Mandatory Default Object name The name of the volume to be resized. size The new volume size. New size of volumes in size_ number of blocks. blocks Boolean Must be specified as yes if the new shrink_ size is smaller than volume...
  • Page 62 The same goes for resizing a snapshot: it does not change the size of its master volume. If applied on a volume that is part of an IBM Hyper-Scale Mobility relation, the command has to be acknowledged by both source and destination volumes.
  • Page 63 VOLUME_SIZE_ABOVE_LIMIT Volume size specified is above limit v COMMAND_NOT_SUPPORTED_FOR_OLVM_VOLUMES This command is not supported for IBM Hyper-Scale Mobility volumes. v MIRROR_IS_NON_OPERATIONAL Mirror is non-operational v VOLUME_IS_SLAVE Volume is defined as a slave volume...
  • Page 64: Unlocking A Volume

    The modification time is the time when the unlock command was executed, regardless of the actual changes performed on the volume via write commands. If applied on a volume that is part of an IBM Hyper-Scale Mobility relation, the command has to be acknowledged by both source and destination volumes.
  • Page 65 User Category Permission Condition Application administrator Conditionally Allowed The volume is a snapshot, where its master volume is mapped to a host or cluster associated with the user and the snapshot was created by an application administrator. Security administrator Disallowed Read-only users Disallowed Technicians...
  • Page 66 IBM XIV Storage System User Manual...
  • Page 67: Chapter 4. Lun Mapping Management

    Chapter 4. LUN Mapping Management All the LUN mapping commands are obsolete and were replaced by the clustering commands. The following commands are no longer in use: v map_add_vol (The concept of mapping has been replaced by clusters. See map_volume.) v map_create (The concept of mapping has been replaced by clusters.
  • Page 68 IBM XIV Storage System User Manual...
  • Page 69: Chapter 5. Volume Snapshot Management

    Chapter 5. Volume Snapshot Management The following sections describe the XIV Command Line Interface (XCLI) for snapshot management. Other commands that are relevant to this topic are: Listing Volumes, Renaming a Volume, Changing Pool Settings for Snapshots. See also: Volume Management...
  • Page 70: Creating A Snapshot

    Creates a snapshot of an existing volume. snapshot_create vol=VolName < [ name=Name ] [ delete_priority=del_value ] > | < overwrite=Name > Parameters: Name Type Description Mandatory Default Object name Name of the volumes to snapshot. IBM XIV Storage System User Manual...
  • Page 71 Name Type Description Mandatory Default name Object name Names of the new Auto-generated snapshots. names. Integer The deletion priority of the delete_ volume's snapshot. priority overwrite Object name Name of an existing snapshots to be overwritten with the current volumes content. This command creates a new snapshot for an existing volume, which is referred to as the snapshot's master volume.
  • Page 72 The volume is mapped to a host or a cluster associated with the user. If a snapshot overwrite is used, the target snapshot must be one created by a server administrator. Security administrator Disallowed Read-only users Disallowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 73: Deleting A Snapshot

    Completion Codes: v VOLUME_BAD_NAME Volume name does not exist v MAX_VOLUMES_REACHED Maximum number of volumes already defined v SNAPSHOT_ILLEGAL_PRIORITY Illegal snapshot priority; must be an integer between 1 and 4. v VOLUME_IS_SNAPSHOT Operation is not permitted on snapshots v VOLUME_EXISTS Volume name already exists v VOLUME_BAD_PREFIX Volume name has a reserved prefix...
  • Page 74: Duplicating A Snapshot

    Troubleshooting: Please wait for sync job to complete v SNAPSHOT_IS_CONSISTENT_ELCS If a mirrored volume is not consistent then its ELCS is protected and cannot be deleted. Duplicating a Snapshot Duplicates an existing snapshot. snapshot_duplicate snapshot=SnapshotName [ name=Name ] IBM XIV Storage System User Manual...
  • Page 75 Parameters: Name Type Description Mandatory Default snapshot Object name The name of the snapshot to duplicate. name Object name Name of the new Automatically snapshot to be generated name. generated. This command duplicates an existing snapshot. The newly created snapshot is initially locked for changes and is associated with the master volume of the existing snapshot.
  • Page 76: Formatting A Snapshot

    Reading from the formatted snapshot always returns zeroes v It can be overridden v It can be deleted v Its deletion priority can be changed Example: snapshot_format snapshot Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed IBM XIV Storage System User Manual...
  • Page 77: Listing Snapshot Information

    User Category Permission Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v SNAPSHOT_IS_PART_OF_SNAPSHOT_GROUP Snapshot is part of a Snapshot Group v SNAPSHOT_HAS_ACTIVE_SYNC_JOB Snapshot is currently a target of an active sync job Troubleshooting: Please wait for sync job to complete v VOLUME_BAD_NAME Volume name does not exist...
  • Page 78 Short Live IO enable_VAAI VAAI enabled VAAI disabled by user user_disabled_ VAAI Snapshot Format snapshot_ format ssd_caching SSD Caching State Use SSD Caching Default State use_ssd_ caching_ default unmap_support Unmap Support managed Managed enable_unmap unmap enabled IBM XIV Storage System User Manual...
  • Page 79: Restoring A Volume From A Snapshot

    Name Default Position unmap disabled by user user_disabled_ unmap marked Marked Example: snapshot_list vol=DBVolume Output: Name Size (GB) Master Name Consistency Group Pool DBVolume.sp1 2508 DBVolume default DBVolume.sp1.copy 2508 DBVolume default Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed...
  • Page 80 Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Warnings: v ARE_YOU_SURE_YOU_WANT_TO_RESTORE_SNAPSHOT Are you sure you want to restore the volume from snapshot Snapshot? Completion Codes: v VOLUME_HAS_DATA_MIGRATION Data Migration is defined for this volume IBM XIV Storage System User Manual...
  • Page 81 v VOLUME_BAD_NAME Volume name does not exist v VOLUME_IS_NOT_A_SNAPSHOT Operation is permitted only on snapshots v NOT_ENOUGH_SPACE No space to allocate volume v SNAPSHOT_IS_PART_OF_SNAPSHOT_GROUP Snapshot is part of a Snapshot Group v VOLUME_HAS_MIRROR Mirror is defined for this volume v VOLUME_LOCKED Volume is locked v SNAPSHOTS_BELONG_TO_DIFFERENT_MASTERS Target snapshot and source snapshot should be snapshots of the same volume...
  • Page 82 IBM XIV Storage System User Manual...
  • Page 83: Chapter 6. Consistency Group Management

    Chapter 6. Consistency Group Management The following sections describe the XIV Command Line Interface (XCLI) for Consistency Group management. Other commands that are relevant to this topic are: Snapshotting a Consistency Group, Moving a Volume between Storage Pools , Moving Consistency Groups between Storage Pools or or Grouped Pools.
  • Page 84 Consistency Group's peer. Once added, the mirrored volume will be set the RPO of the mirrored Consistency Group. The mirrored Consistency Group has one sync job for all pertinent mirrored volumes within the Consistency Group. In case of acknowledgment time out: IBM XIV Storage System User Manual...
  • Page 85 Consistency Group peers might not be the same). If applied on a volume that is part of an IBM Hyper-Scale Mobility relation: v The command is applicable only to a destination volume v This destination volume has to be in Proxy state Otherwise, a completion code is returned (see below).
  • Page 86 Volumes under Consistency Group Mirror should have the same mirroring activation state. v REMOTE_CONS_GROUP_MIRROR_SCHEDULE_MISMATCH Volumes under Consistency Group Mirror in remote machine should have identical mirroring schedule. v CONS_GROUP_MIRROR_TYPE_MISMATCH Volumes under Consistency Group Mirror should have the same mirroring type. IBM XIV Storage System User Manual...
  • Page 87: Creating Consistency Groups

    CONS_GROUP_APPLICATION_CONSISTENCY_MISMATCH Application consistency of the volume doesn't match the state of other volumes in the group. v VOLUME_HAS_OLVM IBM Hyper-Scale Mobility relation is defined for this volume Creating Consistency Groups Creates a Consistency Group. cg_create cg=cgName <pool=PoolName | gp=gpName>...
  • Page 88: Deleting A Consistency Group

    The Consistency Group is mirrored (even if empty). All snapshot groups associated with the Consistency Group are disbanded, meaning that the snapshots contained in these snapshot groups become independent snapshots. Example: cg_delete cg=DBvolumes Output: IBM XIV Storage System User Manual...
  • Page 89: Listing Consistency Groups

    Command completed successfully Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v CONS_GROUP_BAD_NAME Consistency Group name does not exist. v CONS_GROUP_NOT_EMPTY This operation is only allowed on an empty Consistency Group. v CONS_GROUP_HAS_MIRROR Consistency Group has mirroring defined for it.
  • Page 90: Removing A Volume From A Consistency Group

    Consistency Group will not include a snapshot that is associated with the removed volume. Following the volume removal: v Corresponding peer volume is removed from the peer Consistency Group IBM XIV Storage System User Manual...
  • Page 91 (MIRROR_POSSIBLE_CONS_GROUP_MEMBERSHIP_MISMATCH). If applied on a volume that is part of an IBM Hyper-Scale Mobility relation: v The command is applicable only to a destination volume v This destination volume must be in Proxy state Otherwise, a completion code is returned.
  • Page 92: Renaming Consistency Groups

    SNAPSHOT_HAS_ACTIVE_SYNC_JOB Snapshot is currently a target of an active sync job Troubleshooting: Please wait for sync job to complete v VOLUME_HAS_OLVM IBM Hyper-Scale Mobility relation is defined for this volume Renaming Consistency Groups Renames Consistency Groups. cg_rename cg=cgName new_name=Name...
  • Page 93: Suspend I/O Execution On Consistency Group

    This command succeeds even if the new name is identical to the current name. Example: cg_rename cg=DBgroup new_name=DBvolumes Output: Command completed successfully Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians...
  • Page 94: Resume I/O Execution

    Consistency Group name does not exist. v CONS_GROUP_IS_SLAVE Consistency Group is mirroring slave. v IO_PAUSE_ALREADY_ISSUED_FOR_CONS_GROUP Volume(s) belonging to the Consistency Group are already paused Resume I/O Execution Resume IO execution on CG previously suspended with resume_io io_resume token_id=Token IBM XIV Storage System User Manual...
  • Page 95: List Consistency Groups Pause I/O State

    Parameters: Name Type Description Mandatory token_id Positive integer token returned by resume_io command Resume IO execution on CG previously suspended with resume_io Example: io_resume token_id=6343971831808 Output: command: code = "SUCCESS" status = "0" status_str = "Command completed successfully" Access Control: User Category Permission Condition...
  • Page 96: Creates A Cross-System Consistency Group

    Snapshot Group must be one created by a server administrator. Security administrator Disallowed Read-only users Allowed Technicians Disallowed Creates a Cross-System Consistency Group Creates a Cross-system Consistency Group (XCG) definition. xcg_create xcg=XcgName IBM XIV Storage System User Manual...
  • Page 97: Associates An Existing Consistency Group To A Cross-System Consistency Group Definition

    Type Description Mandatory Object name Name of a Cross-system Consistency Group. Creates a Cross-system Consistency Group (XCG) definition to which Consistency Groups on different XIV systems may be associated. Example: xcg_create xcg=DBbackup Output: Command completed successfully Access Control: User Category...
  • Page 98 CONS_GROUP_IS_SLAVE Consistency Group is mirroring slave. v CONS_GROUP_BAD_NAME Consistency Group name does not exist. v CONS_GROUP_ALREADY_IN_XCG Consistency Group already belongs to Cross Consistency Group. v CONS_GROUP_BELONGS_TO_XCG Consistency Group belongs to another Cross Consistency Group. IBM XIV Storage System User Manual...
  • Page 99: Removes An Existing Consistency Group From A Cross-System Consistency Group Definition

    Removes an Existing Consistency Group from a Cross-System Consistency Group Definition Removes an existing Consistency Group from a Cross-system Consistency Group definition. xcg_remove_cg xcg=XcgName cg=cgName Parameters: Name Type Description Mandatory Object name Name of a Cross-system Consistency Group. Object name Name of a Consistency Group.
  • Page 100: Adds A Remote System Name To The Cross-System Consistency Group Definition

    If a Snapshot Group overwrite is used, then the target Snapshot Group must be one created by a server administrator. Security administrator Disallowed Read-only users Disallowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 101: Removes A Remote System Name From A Cross-System Consistency Group Definition

    Completion Codes: v XCG_BAD_NAME Cross Consistency Group name does not exist. v MAX_REMOTE_SYSTEMS_IN_XCG_REACHED Cross Consistency Group contains maximum number of remote systems. v REMOTE_SYSTEM_ALREADY_ADDED Remote system belongs to Cross Consistency Group Removes a Remote System Name from a Cross-System Consistency Group Definition Removes a remote system name from a Cross-system Consistency Group definition.
  • Page 102: Lists Cross-System Consistency Group Definitions Along With Contained Consistency Groups

    If a Snapshot Group overwrite is used, then the target Snapshot Group must be one created by a server administrator. Security administrator Disallowed Read-only users Allowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 103: Retrieve The Names Of Remote Systems Part Of The Specified Cross-System Consistency Group

    Completion Codes: v XCG_BAD_NAME Cross Consistency Group name does not exist. Retrieve The Names of Remote Systems Part of The Specified Cross-System Consistency Group Retrieve the names of remote systems part of the specified Cross-system Consistency Group. xcg_get_remote_systems xcg=XcgName Parameters: Name Type Description...
  • Page 104: Deletes A Cross-System Consistency Group

    Group must be one created by a server administrator. Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v XCG_BAD_NAME Cross Consistency Group name does not exist. v XCG_NOT_EMPTY Consistency Group is not empty. IBM XIV Storage System User Manual...
  • Page 105: Lists Cross-System Consistency Group Definitions

    Lists Cross-System Consistency Group Definitions Lists Cross-system Consistency Group definitions along with contained Consistency Groups. xcg_list [ xcg=XcgName ] Parameters: Name Type Description Mandatory Default Object name Name of a All Cross-system Cross-system Consistency Consistency Groups. Group. Lists Cross-system Consistency Group definitions . Name Default Position name...
  • Page 106 IBM XIV Storage System User Manual...
  • Page 107: Chapter 7. Snapshot Set Management

    Chapter 7. Snapshot Set Management The following sections describe the XIV Command Line Interface (XCLI) for Snapshot Set management. Use the cg_snapshot_create command to create the snapshot group. See also: Volume Management Volume Snapshot Management Consistency Group Management The sections are listed as follows: cg_snapshots_create(Creates a snapshot group of a Consistency Group.)
  • Page 108 The overwrite snapshot group must be an existing snapshot group of the given Consistency Group. This command fails if no snapshot space is defined for the Storage Pool containing the Consistency Group. IBM XIV Storage System User Manual...
  • Page 109 This command fails if one or more of the volumes in the Consistency Group is a slave of a synchronous mirroring, and it is currently inconsistent due to either a re-synchronization or an initialization process. Mirroring limitations: v This command fails if the volume is a slave of an asynchronous mirroring coupling (either synchronous or asynchronous).
  • Page 110: Changing Snapshot Group Deletion Priority

    See Changing a Snapshot Deletion Priority for more details about the valid deletion priority values and their meaning. Example: snap_group_change_priority snap_group=DBbackup delete_priority=4 Output: Command completed successfully. IBM XIV Storage System User Manual...
  • Page 111: Deleting A Snapshot Group

    Access Control: User Category Permission Condition Storage administrator Allowed Storage integration administrator Allowed Application administrator Conditionally Allowed At least one of the volumes in the master Consistency Group is mapped to a host or cluster associated with the user and Snapshot Group was created by a server administrator Security administrator...
  • Page 112: Disbanding A Snapshot Group

    The snapshot group does not exist anymore after this command. The snapshots retain the same names (snap_group_name.volumename). The command is inapplicable for a snapshot group of a mirrored Consistency Group. Example: snap_group_disband snap_group=DBbackup_copy IBM XIV Storage System User Manual...
  • Page 113: Duplicating A Snapshot Group

    Output: Command completed successfully. Access Control: User Category Permission Condition Storage administrator Allowed Storage integration administrator Allowed Application administrator Conditionally Allowed At least one of the volumes in the master Consistency Group is mapped to a host or cluster associated with the user and Snapshot Group was created by a server administrator Security administrator...
  • Page 114: Formatting A Snapshot Group

    The format operation has no impact on performance v The snapshot of the formatted snapshot group do not consume space v Reading from the snapshot of the formatted snapshot group always returns zeroes IBM XIV Storage System User Manual...
  • Page 115: Listing Snapshot Groups

    v They can be overridden v They can be deleted v Their deletion priority can be changed Example: snap_group_format snap_group Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Disallowed...
  • Page 116 Snapshot Time Deletion Priority DBbackup DBvolumes 2007-01-03 17:46:29 1 DBbackupdaily DBvolumes 2007-01-03 17:49:36 1 Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed IBM XIV Storage System User Manual...
  • Page 117: Locking A Snapshot Group

    User Category Permission Technicians Disallowed Completion Codes: v CONS_GROUP_DOES_NOT_EXIST Consistency Group does not exist. v SNAPSHOT_GROUP_BAD_NAME Snapshot Group name does not exist. Locking a Snapshot Group Locks a snapshot group by locking all its snapshot. snap_group_lock snap_group=SnapshotSetName Parameters: Name Type Description Mandatory snap_group...
  • Page 118: Renaming A Snapshot Group

    Snapshot Group was created by a server administrator Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v SNAPSHOT_GROUP_BAD_NAME Snapshot Group name does not exist. v SNAPSHOT_GROUP_NAME_EXISTS Snapshot Group name already exists. IBM XIV Storage System User Manual...
  • Page 119: Restoring A Consistency Group From A Snapshot Group

    Restoring a Consistency Group from a Snapshot Group Restores the master volumes of a Consistency Group, or a snapshot group from one of its associated snapshot groups. snap_group_restore snap_group=SnapshotGroupName [ target_snap_group=SnapGroupName ] Parameters: Name Type Description Mandatory snap_group Object name Name of the snapshot group from which to restore its master...
  • Page 120: Unlocking A Snapshot Group

    Target Snapshot Group is the same as Snapshot Group. Unlocking a Snapshot Group Unlocks a snapshot group by unlocking all its snapshots. snap_group_unlock snap_group=SnapshotGroupName Parameters: Name Type Description Mandatory snap_group Object name Name of the snapshot group to be unlocked. IBM XIV Storage System User Manual...
  • Page 121: Sets A Snapshot Group Descriptor

    This command unlocks a snapshot group by unlocking all its snapshots. This is functionally equivalent to executing Unlocking a Volume on each snapshot. You may refer to the documentation of Unlocking a Volume for a description of unlocking behavior. Example: snap_group_unlock snap_group=DBbackup Output: Command completed successfully...
  • Page 122: Returns The Snapshot Group's Descriptor

    Type Description Mandatory snap_group Object name Name of the snapshot group. Provides external software with an ability to obtain a descriptor attribute value for a snapshot group. Example: snap_group_get_descriptor snap_group=DBbackup Output: Command completed successfully IBM XIV Storage System User Manual...
  • Page 123 Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Disallowed Completion Codes: v SNAPSHOT_GROUP_BAD_NAME Snapshot Group name does not exist. Chapter 7. Snapshot Set Management...
  • Page 124 IBM XIV Storage System User Manual...
  • Page 125: Chapter 8. Storage Pool Management

    Chapter 8. Storage Pool Management The following sections describe the XIV Command Line Interface (XCLI) for Storage Pool management. See also: Volume Management Volume Snapshot Management Consistency Group Management The sections are listed as follows: cg_move(Moves a Consistency Group, all its volumes and all their snapshots and Snapshot Sets from one Storage Pool or Grouped Pool to another.)
  • Page 126: Changing Pool Limitation

    Object name Name of the Storage Pool. Enumeration Sets whether and how the Pool is locked upon lock_ space depletion. behavior This command changes the Pool behavior when running out of thin provisioning space. IBM XIV Storage System User Manual...
  • Page 127: Changing Pool Settings For Snapshots

    Example: pool_change_config pool=VOL_BREED_None_0 lock_behavior=read_only Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v POOL_DOES_NOT_EXIST Storage Pool does not exist Changing Pool Settings for Snapshots Changes the Storage Pool snapshot settings.
  • Page 128 If, for example, the value is set to 3: – The system will deactivate mirroring if not enough space can be freed even after the deletion of snapshots with deletion priority of 4. IBM XIV Storage System User Manual...
  • Page 129 – Snapshots with priority level 1, 2 and 3 will not be deleted. v If the value is set to 4, the system will deactivate mirroring before deleting any of the snapshots. v If the value is set to 0, the system can delete any snapshot regardless of deletion priority.
  • Page 130: Creating Storage Pools

    The system allows for the assignment of the entire available capacity to user created Storage Pools, while leaving the free space at zero size. IBM XIV Storage System User Manual...
  • Page 131 Both hard and soft sizes are subtracted from the free hard/soft space. For thin provisioned Storage Pools, the lock_behavior parameter sets whether and how the Pool is locked upon space depletion. The Pool can be locked for write, or for both read and write. Example: pool_create pool=DBPool size=1000 Output:...
  • Page 132: Deleting A Storage Pool

    Are you sure you want to delete Storage Pool Pool? Completion Codes: v POOL_DOES_NOT_EXIST Storage Pool does not exist v POOL_HAS_CG Storage Pool has Consistency Groups defined v POOL_IN_USE Storage Pool has volumes allocated in it IBM XIV Storage System User Manual...
  • Page 133: Listing Storage Pools

    Listing Storage Pools Lists all Storage Pools or the specified one. pool_list [ pool=PoolName ] Parameters: Name Type Description Mandatory Default pool Object name Name of a Storage All pools. Pool. This command lists all Storage Pools. When the pool parameter is provided, only the specified Storage Pool is listed. Example: pool_list Output:...
  • Page 134: Renaming A Storage Pool

    Renaming a Storage Pool Renames a specified Storage Pool. pool_rename pool=PoolName new_name=Name Parameters: Name Type Description Mandatory pool Object name Name of the Storage Pool. new_name Object name New name of the Storage Pool. IBM XIV Storage System User Manual...
  • Page 135: Resizing A Storage Pool

    This command renames a Storage Pool. The new name of the Storage Pool must be unique in the system. This command succeeds even if the new name is identical to the current name. Example: pool_rename pool=DBPool new_name=ERPPool Output: Command completed successfully. Access Control: User Category Permission...
  • Page 136 Resizing a Pool that stores asynchronous-mirrored volumes or Consistency Groups: v The Pool's hard and soft size have to be identical. Example: pool_resize pool=DBPool size=1300 Output: Command Executed Successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed IBM XIV Storage System User Manual...
  • Page 137: Moving A Volume Between Storage Pools

    User Category Permission Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Warnings: v POOL_SNAPSHOT_SIZE_TOO_SMALL Snapshot size is very small. It will only allow snapshots of volumes which do no change. All other snapshots will be deleted immediately. Are you sure? Completion Codes: v POOL_DOES_NOT_EXIST Storage Pool does not exist...
  • Page 138 Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v VOLUME_BAD_NAME Volume name does not exist v POOL_DOES_NOT_EXIST Storage Pool does not exist v NOT_ENOUGH_SPACE No space to allocate volume IBM XIV Storage System User Manual...
  • Page 139 v NOT_ENOUGH_HARD_SPACE No space to allocate for volume's current usage v VOLUME_IS_SNAPSHOT Operation is not permitted on snapshots v VOLUME_BELONGS_TO_CG Volume belongs to a Consistency Group v NOT_ENOUGH_SNAPSHOT_SPACE Snapshot usage will exceed snapshot limit Chapter 8. Storage Pool Management...
  • Page 140 IBM XIV Storage System User Manual...
  • Page 141: Chapter 9. System Management

    Chapter 9. System Management The following sections describe the XIV Command Line Interface (XCLI) for system management. The sections are listed as follows: cod_list(Displays current consumed capacity of the system.) config_get(Shows the values of configuration parameters.) config_set(Sets configuration parameters.) dns_test(Tests the DNS (Domain Naming Service).) help(Prints system help.)
  • Page 142: Displaying Current Consumed Capacity Of The System

    MN00013 machine_type 2810 system_id system_name XIV MN00013a time 10:13:31 timezone Asia/Jerusalem Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed IBM XIV Storage System User Manual...
  • Page 143: Printing Configuration Parameters

    - Controls the formatting of the email subject line. The tags {severity}, {description} and {system_name} can be used to insert the event's data. System default is "{severity}: {description}" iscsi_name - iSCSI initiator name. Used when configuring non-XIV system for Data Migration over iSCSI. machine_model -...
  • Page 144: Setting Configuration Parameters

    - Email address used as the sender's address when sending email messages. Once set, this parameter can not be set to a null value. email_reply_to_address - Reply-to address to be used when sending emails. This is useful for troubleshooting errors in email addresses. IBM XIV Storage System User Manual...
  • Page 145: Testing The Dns

    system_name - Name used as the sender's name when sending email messages. defaultuser - Default user to be used if no user is specified for the CLI. If null, a user must be specified. snmp_sysname - SNMP system name as shown in the SNMP MIB. (.1.3.6.1.2.1.1.5.0) snmp_location - SNMP location as shown in the SNMP MIB.
  • Page 146: Printing Help

    Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Completion Codes: v DNS_SERVER_NOT_DEFINED No DNS servers are defined Printing Help Prints system help. help [ category=Category | search=SearchString | command=CommandName ] [ format=<short|full> ] IBM XIV Storage System User Manual...
  • Page 147 Command with short output (default for command) - Prints the command name and short description. v Command with full output (default when used in XIV-internal mode) - Prints the command name, short description, syntax, list of parameters and their description, types and default values.
  • Page 148: Printing The Current Maintenance Urgency

    This command prints the current maintenance urgency of the system. Example: maintenance_urgency_list Output: maintenance_urgency = "NONE" Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed IBM XIV Storage System User Manual...
  • Page 149: Adding A Patch Script That Will Be Run On System's Modules

    Adding a Patch Script that will be Run on System's Modules Adds a patch script that will be run on system's module(s). patch_script_add tar_file=TarFile name=Name exe_file=ExeFile [ module_list=ModuleList ] [ module_type=<data|interface|specific|all> ] [ version=Version ] [ persistence=<yes|no> ] [ run_option=<Always|Once> ] [ parameters=(p1,p2,p3..p10) ] [ enabled=<yes|no>...
  • Page 150 Failed creating directory for the patch script. v PATCH_SCRIPT_FAILED_UNPACKING Failed unpacking patch script tar.gz file. v PATCH_SCRIPT_FAILED_CHMOD Failed chmod patch script directory. v PATCH_SCRIPT_SIGNATURE_IS_NOT_VERIFIED The patch script signature is not verified. v PATCH_SCRIPT_FAILED_TO_DISTRIBUTE Failed to distribute the patch script. IBM XIV Storage System User Manual...
  • Page 151: Deletes A Patch Script

    Deletes a Patch Script Deletes a patch script. patch_script_delete name=Name Parameters: Name Type Description Mandatory name String Script Name. Deletes a patch script. Example: xcli -u -c XIV1 patch_script_delete name=upgrade_script Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed...
  • Page 152 Persistence execution_ flags.persiste Version description_ info.version Description description_ info.descripti Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed IBM XIV Storage System User Manual...
  • Page 153: Updating A Patch Script That Will Be Run On Systems Modules

    Updating a Patch Script that will be Run on Systems Modules Updates a patch script that will be run on system's module(s). patch_script_update name=Name [ module_list=ModuleList ] [ module_type=<data|interface|specific|all> ] [ version=Version ] [ persistence=<yes|no> ] [ run_option=<Always|Once> ] [ parameters=(p1,p2,p3..p10) ] [ enabled=<yes|no> ] [ description=Description ] Parameters: Name...
  • Page 154: Gets A Patch Script Log

    Index line Line Example: xcli -u -c XIV1 patch_script_get_log module=1:Module:3 name=test1 Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed IBM XIV Storage System User Manual...
  • Page 155: Trigger Patch Script Execution On One Or All Modules

    Completion Codes: v PATCH_SCRIPT_DOESNT_EXIST Patch script does not exist. v CANNOT_READ_FROM_FILE Cannot read from file 'Filename' Troubleshooting: Contact support Trigger Patch Script Execution on One or All Modules. Trigger patch script execution on one or all modules. patch_script_activate name=Name [ module=ModuleNumber ] Parameters: Name Type...
  • Page 156: Get Patch Script Execution Inforamtion

    Times Failed Executing Last Execution Status Last Return Code ---------------- ------------------------ ----------------------- ------------------ Finished Name Default Position script_uid Patch Script UID script_name Script Name module_id Module ID current_pid Current PID Last Execution Time last_ execution_time IBM XIV Storage System User Manual...
  • Page 157: Shutting Down

    Name Default Position Times Executed number_of_ times_executed Times Failed Executing number_of_ times_failed_ to_execute Last Execution Status last_ execution_ status Last Return Code last_ execution_ return_code Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users...
  • Page 158 There is no master key server defined on the system. Troubleshooting: Please define a master key server by invoking encrypt_key server_update and retry. v KEYSERVER_COMMUNICATION_GENERIC_ERROR Cannot connect to an active key server. Troubleshooting: Invoke encrypt_key server_list and event_list for more details. IBM XIV Storage System User Manual...
  • Page 159: Changing The Operational State

    Changing the Operational State Changes the operational state of a system. state_change target_state=<shell|on> Parameters: Name Type Description Mandatory Enumeration The operational state after the command is target_ executed. state This command changes the system's states. The systems' states can be transitioned as follows: v Maintenance to On v On to Shell...
  • Page 160: Listing Operational State

    Read-only users Allowed Technicians Allowed Local Storage Free Space shows free space left in local storage. local_storage_show shows free space left in local storage Name Default Position module_id Module free_bytes Free space in bytes IBM XIV Storage System User Manual...
  • Page 161: Showing System Runtime, Power Consumption, System Alert, Numbet Of Psus With No Power In

    Example: xcli -u -c XIV1 local_storage_show Output: Module Free space in bytes -------- --------------------- 2017837056 2042654720 2041233408 2037891072 2042384384 Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Showing System Runtime, Power Consumption, System Alert, Numbet...
  • Page 162: Showing System Capacity, Free Space And Spares

    Target Spare Disks target_spare_ disks soft_MiB Soft (MiB) hard_MiB Hard (MiB) free_hard_MiB Free Hard (MiB) free_soft_MiB Free Soft (MiB) Capacity Limit (%) capacity_ limit_ percentage Access Control: User Category Permission Storage administrator Allowed IBM XIV Storage System User Manual...
  • Page 163: Showing The Current Time

    User Category Permission Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Disallowed Showing the Current Time Shows the current system time. time_list This command shows the current time, date and time zone. Name Default Position time Time date...
  • Page 164: Listing Optional Time Zones

    Standard POSIX time zones are used. http://www.timeanddate.com/worldclock/ provides a full description of all time zones. Name Default Position name Timezone Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Allowed IBM XIV Storage System User Manual...
  • Page 165: Setting The Time Zone

    User Category Permission Read-only users Allowed Technicians Allowed Setting the Time Zone Sets the time zone of the system. timezone_set timezone=TimeZone Parameters: Name Type Description Mandatory timezone String New time zone of the system. This command sets the new time zone of the system. See Listing Optional Time Zones for a complete list of optional time zones.
  • Page 166: Initiating Download Of A New Software Version

    Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Completion Codes: v SYSTEM_UPGRADE_IS_ALREADY_RUNNING Upgrade is already running v NO_ACTIVE_PORTS_OF_SPECIFIED_ROLE IBM XIV Storage System User Manual...
  • Page 167: Canceling An Upgrade Download Process

    None of the ports of the specified role is active. v UPGRADE_DOWNLOAD_COULD_NOT_BE_STARTED Failed starting upgrade download of an unknown reason. v REPOSITORY_IP_MUST_BE_SUPPLIED_FOR_DOWNLOAD Repository IP must be supplied for download if the interface type is Management or VPN. v NO_PORTS_OF_SPECIFIED_ROLE The system does not have any ports of the specified roles. v PORT_ROLE_IS_INVALID Specified port role is invalid.
  • Page 168: Displaying Status Of Upgrade Process

    Displaying Status of Upgrade Process Displays status of upgrade process. upgrade_get_status The output of this command displays the status of the upgrade process. The status can be any of the following: v Downloading - the upgrade package IBM XIV Storage System User Manual...
  • Page 169 v Ready for upgrade v Preparing v Finalizing upgrade (after the I/Os resumes) Additional upgrade-related values: v Requires a reboot v Update is required v The number of times the system attempted to stop I/Os v Time to the next retry v Abort reason (in case the upgrade was aborted) v Failed to communication with server v Server does not have the required software version...
  • Page 170: Upgrading A System

    Pre-upgrade validations cannot be invoked since the system is already in the process of performing those validations v NO_LIVE_ADMIN_SERVER_FOUND Could not invoke pre-upgrade script because no module can run cli commands v PRE_UPGRADE_VALIDATION_FAILED One or more of the conditions for starting an upgrade sequence failed IBM XIV Storage System User Manual...
  • Page 171: Validating The Prerequisites Of An Upgrade To A New Software Version

    v UPGRADE_RELATED_SCRIPT_ALREADY_RUNNING Pre-upgrade or post-upgrade script cannot be invoked since an upgrade related script is currently running v SYSTEM_UPGRADE_INCOMPATIBLE_UPGRADE_TYPE_SPECIFIED The specified upgrade type specified is incompatible with the kind of change imposed by the new version's files Troubleshooting: Specify the correct upgrade type Validating the Prerequisites of an Upgrade to a New Software Version Validates the ability to upgrade to a specified system version upgrade_validate_prerequisites [ upgrade_type=<hot|utilities_only>...
  • Page 172: Printing The Current System Version

    Showing Values of VPD Parameters. Shows the values of VPD parameters. vpd_config_get [ name=Name ] Parameters: Name Type Description Mandatory Default name String Name of the All parameters. parameter to print. Name Default Position name Name value Value IBM XIV Storage System User Manual...
  • Page 173: Setting Vpd Parameters

    Shows the values of VPD parameters. See Setting VPD Parameters for a full list of available settings. Example: vpd_config_get name=site.city Output: Name Value ----------- -------- site.city Gotham Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed...
  • Page 174 Example: IBM XIV Storage System User Manual...
  • Page 175: Showing Values Of Maintenance Module Parameters

    vpd_config_set name= value= Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Showing Values of Maintenance Module Parameters. Shows the values of Maintenance Module parameters. mm_config_get [ name=Name ] Parameters: Name Type...
  • Page 176: Displaying The System's Mib File

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Completion Codes: v CANNOT_READ_FROM_FILE Cannot read from file 'Filename' Troubleshooting: Contact support IBM XIV Storage System User Manual...
  • Page 177: Retrieves The Electronic License Acceptance Status

    Retrieves the Electronic License Acceptance Status. Retrieves the electronic license acceptance status. elicense_status_get Retrieves the electronic license acceptance status. Example: xcli -u -c XIV1 elicense_status_get Output: Status ---------- Accepted Name Default Position status Status Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed...
  • Page 178: Accept The Electronic License Agreement

    Accept the electronic license agreement. Example: xcli -u -c XIV1 elicense_accept version approver_name Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed IBM XIV Storage System User Manual...
  • Page 179 User Category Permission Technicians Disallowed Completion Codes: v ELICENSE_INCOMPATIBLE_VERSION The accepted version of the Electronic license dose not match the current version Troubleshooting: Please retrieve the current electronic license version and accept v ELICENSE_ALLREADY_ACCEPTED Electronic license already accepted Troubleshooting: You do not need to accept the electronic license v ELICENSE_DISABLED Electronic license check is disabled Troubleshooting: You do not need to accept the electronic license...
  • Page 180 IBM XIV Storage System User Manual...
  • Page 181: Chapter 10. Remote Target Connectivity

    Chapter 10. Remote Target Connectivity The following sections describe the XIV Command Line Interface (XCLI) for defining remote target connectivity. The sections are listed as follows: target_change_connection_threshold(Setting a threshold for link disruption that lasts more than a specified duration) target_config_sync_rates(Changes the target's mirroring configuration.) target_connectivity_activate(Activates connectivity between a port on the local storage system and a port on a remote target.)
  • Page 182: Setting A Threshold For Link Disruption Duration That Triggers An Event

    Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v TARGET_BAD_NAME Target name does not exist v TARGET_INVALID_CONNECTION_DURATION_THRESHOLD Target connection duration threshold should be in [1,1000000] range IBM XIV Storage System User Manual...
  • Page 183: Updating The Target Mirroring Configuration

    Updating the Target Mirroring Configuration Changes the target's mirroring configuration. target_config_sync_rates target=TargetName [ max_initialization_rate=MaxInitializationRate ] [ max_syncjob_rate=MaxSyncjobRate ] [ max_resync_rate=MaxResyncRate ] Parameters: Name Type Description Mandatory Default target Object name The updated target. Positive integer Specifies the Unchanged maximum rate for max_ initial initializa...
  • Page 184: Activating Connectivity To A Remote Target

    Target name does not exist v CONNECTIVITY_NOT_DEFINED Remote port is not connected through this local port v COMPONENT_IS_NOT_AN_FC_PORT Component must specify an FC port v COMMAND_NOT_ALLOWED_ON_MANAGEMENT_INTERFACE Operation is not allowed on Management IP Interface IBM XIV Storage System User Manual...
  • Page 185: Deactivating Connectivity To A Remote Target

    v IPINTERFACE_DOES_NOT_EXIST IP Interface name does not exist v TARGET_PORT_BAD_ADDRESS Remote port address is illegal or does not belong to the remote target v BAD_LOCAL_IP_PORT An ID of a local IP port must be specified Deactivating Connectivity to a Remote Target Deactivates connectivity between a port on the local storage system and a port on a remote target.
  • Page 186: Defining Connectivity To A Remote Target

    IPINTERFACE_DOES_NOT_EXIST IP Interface name does not exist v TARGET_HAS_OLVM_RELATIONSHIP Target has an IBM Hyper-Scale Mobility relationship - cannot be deactivate or deleted Defining Connectivity to a Remote Target Defines connectivity between a port on the local storage system and a port on a remote target.
  • Page 187 Name Type Description Mandatory Object name Local IP interface to be connected to the remote local_ port (iSCSI only). ipinterfac fcaddress FC address of the port on the remote target (FC targets only). local_port FC port (FC only). This command defines connectivity between a port on the local storage system and a port on a remote target.
  • Page 188: Deleting Connectivity To A Remote Target

    IBM Hyper-Scale Mobility peer. This command deletes a Target Connectivity definition. Only a previously defined connectivity definition can be deleted. Example: target_connectivity_delete target=XIV2 local_module=101 Output: Command completed successfully IBM XIV Storage System User Manual...
  • Page 189: Listing Target Connectivity Definitions

    An ID of a local IP port must be specified v IPINTERFACE_DOES_NOT_EXIST IP Interface name does not exist v TARGET_HAS_OLVM_RELATIONSHIP Target has an IBM Hyper-Scale Mobility relationship - cannot be deactivate or deleted Listing Target Connectivity Definitions Lists all the connectivity definitions of a remote target.
  • Page 190: Defining A Remote Target

    Printing Configuration Parameters of the system_id variable on the remote system. Boolean Defines the remote system as an XIV xiv_ system. Non-XIV features systems are used only for data migration. IBM XIV Storage System User Manual...
  • Page 191 This command defines the communication topology between a local storage system and a remote storage system in order to enable various features, such as remote mirroring. The local storage system can write to or read from the remote storage system or allow the target storage system to write to or read from it. The first step when defining a new Target Connectivity is to specify the name of the remote storage system and the protocol used to communicate with it.
  • Page 192: Deleting A Remote Target

    Target name does not exist v TARGET_HAS_PORTS Ports are defined for this target v TARGET_HAS_ASSOCIATIONS Remote volumes are defined on this target v TARGET_HAS_OLVM_RELATIONSHIP Target has an IBM Hyper-Scale Mobility relationship - cannot be deactivate or deleted IBM XIV Storage System User Manual...
  • Page 193: Listing Remote Targets

    - max initialization rate, max resync rate, and max sync job rate. Name Default Position name Name scsi_type SCSI Type connected Connected xiv_target XIV Target iscsi_name iSCSI Name system_id System ID num_ports Number of Ports creator Creator Max Initialization Rate max_...
  • Page 194: Allowing Remote Mirroring Access

    Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v TARGET_BAD_NAME Target name does not exist v TARGET_BAD_TYPE Target machine is not XIV machine IBM XIV Storage System User Manual...
  • Page 195: Activating A Port

    Activating a Port Activates a port of a remote target. target_port_activate target=TargetName < ipaddress=IPaddress | fcaddress=wwpn > Parameters: Name Type Description Mandatory target Object name Remote target of the port. ipaddress IP address of the port on the remote target (iSCSI targets only).
  • Page 196: Adding A New Port To A Remote Target

    MAX_PORTS_REACHED Maximum number of ports already defined in the system v TARGET_PORT_BAD_ADDRESS Remote port address is illegal or does not belong to the remote target v ISCSI_HOST_ILLEGAL_PORT_NAME Port name for iSCSI Host is illegal IBM XIV Storage System User Manual...
  • Page 197: Deactivating A Port

    Troubleshooting: Port names for iSCSI Hosts must contain only printable characters. v HOST_PORT_EXISTS Host with this port ID already defined Deactivating a Port Deactivates a port of a remote target. target_port_deactivate target=TargetName < ipaddress=IPaddress | fcaddress=wwpn > [ force_on_olvm_peer=<yes|no> ] Parameters: Name Type...
  • Page 198: Deleting A Port From A Remote System

    Remote port address is illegal or does not belong to the remote target v TARGET_BAD_PORT_STATE Port is already in requested activation state v TARGET_HAS_OLVM_RELATIONSHIP Target has an IBM Hyper-Scale Mobility relationship - cannot be deactivate or deleted Deleting a Port from a Remote System Deletes a port from a specified remote target.
  • Page 199: Listing The Ports Of A Remote Target

    User Category Permission Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v TARGET_BAD_NAME Target name does not exist v TARGET_PORT_BAD_ADDRESS Remote port address is illegal or does not belong to the remote target v TARGET_PORT_HAS_CONNECTIVITY Port has connectivity defined to it Listing the Ports of a Remote Target List all ports of a target.
  • Page 200: Renaming A Remote Target

    Target name does not exist v TARGET_NAME_EXISTS Target name is already assigned to another target Updating the Target Configuration Updates the target's configuration. target_update target=TargetName system_id=SystemId Parameters: Name Type Description Mandatory target Object name Target to be updated. IBM XIV Storage System User Manual...
  • Page 201 Name Type Description Mandatory system_id String ID of the remote system. Should be the same as the output of Printing Configuration Parameters of the system_id variable on the remote system. This command changes the system ID of the remote target. Access Control: User Category Permission...
  • Page 202 IBM XIV Storage System User Manual...
  • Page 203: Chapter 11. Remote Mirroring

    Chapter 11. Remote Mirroring The following sections describe the XIV Command Line Interface (XCLI) for remote mirroring. Other command that are relevant to this topic is: Setting a Threshold for Link Disruption Duration that Triggers an Event. The sections are listed as follows: mirror_cancel_snapshot( Cancels all Snapshot Mirrors ('ad-hoc' sync jobs) of a specified master volume or a master Consistency Group, that have not run yet.)
  • Page 204: Canceling A Snapshot Mirror (Ad Hoc Sync Job)

    The volume is mapped to a host or a cluster associated with the user. If a snapshot overwrite is used, the target snapshot must be one created by a server administrator. Security administrator Disallowed Read-only users Disallowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 205: Creating A Snapshot Mirror (Ad Hoc Sync Job)

    Warnings: v ARE_YOU_SURE_YOU_WANT_TO_CANCEL_SNAPSHOT_ MIRRORS_FOR_THE_VOLUME Are you sure you want to delete snapshot mirrors for Volume? ARE_YOU_SURE_YOU_WANT_TO_CANCEL_SNAPSHOT_ MIRRORS_FOR_THE_CONSISTENCY_GROUP Are you sure you want to delete snapshot mirrors for Consistency Group? Completion Codes: v VOLUME_BAD_NAME Volume name does not exist v VOLUME_NO_MIRROR Local volume does not have remote mirroring definitions v CONS_GROUP_BAD_NAME Consistency Group name does not exist.
  • Page 206 The snapshot mirror results with the following: v On the Slave - a snapshot is taken on the slave, named last_replicated v On the Master - the pertinent snapshot that is mirrored onto the slave is also named last_replicated IBM XIV Storage System User Manual...
  • Page 207 These two last_replicated snapshots are different and denoted" master" and "slave" accordingly. The outcome for the synchronous mirroring: v The Master blocks host I/O for the duration of creating the snapshots v The Master completes synchronizing pending writes v A snapshot of the Master and Slave is taken v The Master no longer blocks host I/O v An event is generated Access Control:...
  • Page 208 The Snapshot Group was given an illegal deletion priority. Illegal snapshot group priority; must be an integer between 1 and 4. v SNAPSHOT_GROUP_BAD_NAME Snapshot Group name does not exist. v SNAPSHOT_GROUP_BAD_PREFIX Snapshot Group name has a reserved prefix. IBM XIV Storage System User Manual...
  • Page 209: Activating Mirroring

    Operation not allowed on slave volume that is not consistent. v VOLUME_IS_SNAPSHOT Operation is not permitted on snapshots v VOLUME_IS_OLVM_PROXY The volume is in an IBM Hyper-Scale Mobility Proxy phase. Activating Mirroring Activates mirroring for a defined mirror coupling. mirror_activate < vol=VolName | cg=cgName >...
  • Page 210 Mirror local configuration does not match remote configuration v REMOTE_MAX_VOLUMES_REACHED Maximum number of volumes already defined on remote machine v SYNC_ALREADY_ACTIVE Synchronization is already active v VOLUME_BELONGS_TO_MIRRORED_CONS_GROUP Volume mirror is part of Consistency Group mirror. IBM XIV Storage System User Manual...
  • Page 211: Changing The Rpo For Local/Remote System

    v MIRROR_CAN_NOT_BE_ACTIVATED Mirroring cannot be activated because state cannot be established Troubleshooting: Delete and recreate mirror v MIRROR_CONS_GROUP_MEMBERSHIP_MISMATCH Mirrored CG contains different volumes on Master and Slave. This problem occurs whenever the cg_add_vol or cg_remove_vol commands were previously issued and the Master did not receive an acknowledgment from the Slave until the command timed out, or any other unexpected failure.
  • Page 212: Changing A The Mirroring Peers' Designation

    Synchronous Mirror does not have an RPO. Changing a the Mirroring Peers' Designation Changes the designation of mirroring peers - from Primary to Secondary, and from Secondary to Primary. mirror_change_designation < vol=VolName | cg=cgName > [ new_designation=<Primary|Secondary|None> ] IBM XIV Storage System User Manual...
  • Page 213 Parameters: Name Type Description Mandatory Default Object name Master volume name. Object name Master CG name. Enumeration The new none designation of the new_ peer designatio If not specified, the command will act as a toggle - changing the designation of the peers between Primary and Secondary.
  • Page 214: Changing A Mirroring Schedule For Remote Slave Peers

    An event is generated v New sync jobs are generated according to the updated schedule v Existing sync jobs are not affected (i.e. they run according to the previous schedule) Requirements for a successful command completion: IBM XIV Storage System User Manual...
  • Page 215 v The specified target exists v The specified target is mirrored v The specified target is not a volume that belongs to a mirrored Consistency Group v The specified target is of sync type ASYNC_INTERVAL v The specified target is a Master v The link is up Access Control: User Category...
  • Page 216: Changing The Roles Of A Mirrored Volume

    – An event is generated – The Master will cease accepting host requests – Unsynchronized data at the demoted Master is recorded in most updated snapshot – The demoted Master reverts to last_replicated snapshot IBM XIV Storage System User Manual...
  • Page 217 – Completion of process is recorded in log o Mirroring state is standby When applied on the slave: – The slave will become a master, start accepting requests from hosts, and upon explicit activation will start replicating to the other peer (the original master). –...
  • Page 218: Changing A Mirroring Schedule For Local Peers

    Master cannot be demoted to Slave role, Peer status mismatch Changing a Mirroring Schedule for Local Peers Changes the replication schedule for peers on the local system. mirror_change_schedule < vol=VolName | cg=cgName > schedule=Schedule IBM XIV Storage System User Manual...
  • Page 219 Parameters: Name Type Description Mandatory Object name Volume name on the local system. Object name CG name on the local system schedule Object name A reference to a mirroring schedule This command changes the replication schedule for a peer on the local system. The new scheduling will become effective only if the peer is set as Master.
  • Page 220: Creating A Mirroring Definition

    (the master). slave_cg Object name Name of the slave cg on the remote storage system. type Enumeration Name of SYNC_BEST_ replication type EFFORT target Object name Remote target to contain the slave volume. IBM XIV Storage System User Manual...
  • Page 221 Name Type Description Mandatory Default Positive integer Mirror Recovery [None] Point Objective value for Master. Ranges from 30 to 86400 seconds (i.e., up to 24 hours) Applies and mandatory to asynchronous mirroring only. remote_rpo Positive integer Mirror Recovery [Master RPO] Point Objective value when remote peer becomes...
  • Page 222 Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v ASYNC_MIRROR_MISSING_RPO Definition of Asynchronous Mirror requires RPO to be specified. v ASYNC_MIRROR_REMOTE_RPO_TOO_LONG Specified Remote RPO is too long. IBM XIV Storage System User Manual...
  • Page 223 v ASYNC_MIRROR_REMOTE_RPO_TOO_SHORT Specified Remote RPO is too short. v ASYNC_MIRROR_RPO_TOO_SHORT Specified RPO is too short. v ASYNC_MIRROR_RPO_TOO_LONG Specified RPO is too long. v ASYNC_NOT_SUPPORTED_IN_TARGET Asynchronous Mirror is not supported by specified Target. v BAD_REMOTE_VOLUME_NAME Slave volume name does not exist v BAD_REMOTE_VOLUME_SIZE Master and slave volumes contain a different number of blocks v CONS_GROUP_BAD_NAME...
  • Page 224 Volume has snapshots created by previous mirroring process. v SLAVE_VOLUME_NOT_FORMATTED Slave volume is not formatted v TARGET_DOES_NOT_ACCEPT_XIV_COMMANDS Target system does not accept XIV management commands v SYNC_MIRROR_HAS_NO_RPO Synchronous Mirror does not have an RPO. v REMOTE_CONS_GROUP_IS_MIRRORED Remote Consistency Group has mirroring defined for it.
  • Page 225: Deactivating Mirroring

    Volume size specified is above limit of remote machine v INVALID_SLICE_OFFSET Slice number out of range v VOLUME_IS_OLVM_PROXY The volume is in an IBM Hyper-Scale Mobility Proxy phase. v ENCRYPTION_IN_PROGRESS System is in the process of changing encryption activation state Deactivating Mirroring Deactivates mirroring for a defined mirror coupling.
  • Page 226 Volume mirror is part of Consistency Group mirror. v MIRROR_RETRY_OPERATION There is an operation in progress on this mirror , please retry your request in a few seconds Troubleshooting: Please retry the command in a few seconds IBM XIV Storage System User Manual...
  • Page 227: Deleting A Remote Mirroring Definition

    Deleting a Remote Mirroring Definition Deletes a remote mirroring coupling definition. mirror_delete < vol=VolName | cg=cgName > [ force_on_slave=<Yes|No> ] Parameters: Name Type Description Mandatory Default Object name Local Master volume name. Object name Local Master CG name. Boolean Forces the deletion of the remote force_on_ mirroring coupling...
  • Page 228 There is an operation in progress on this mirror , please retry your request in a few seconds Troubleshooting: Please retry the command in a few seconds v MIRROR_IS_NOT_INITIALIZING Operation is permitted only during the Initialization phase. IBM XIV Storage System User Manual...
  • Page 229: Viewing Mirroring Status

    Viewing Mirroring Status Lists the status and configuration of mirroring couplings mirror_list [ vol=VolName | cg=cgName | < [ scope=<cg|volume> ] [ sync_type=<sync_best_effort|async_interval> ] > ] Parameters: Name Type Description Mandatory Default sync_type Enumeration List type - All (if no SYNC_BEST_ parameter is EFFORT,...
  • Page 230 Operational sync_progress Sync Progress (%) mirror_error Mirror Error No Error, Secondary pool exhausted, Configuration error or No thin provisioning resources sync_type Mirror Type schedule_name Schedule Name Last Replicated last_ replicated_ snapshot_time IBM XIV Storage System User Manual...
  • Page 231 Name Description Default Position Has Last Replicated Snapshot last_ replicated_ snapshot_ exists specified_rpo remote_rpo Remote RPO App Consistency application_ consistent validate Validation Output: <command id="0"> <administrator> <command> <changes_session_id value="1288716489394201:1:1288903896317961:1"/> <code value="SUCCESS"/> <last_change_index value="32289"/> <status value="0"/> <status_str value="Command completed successfully"/> <return> <mirror id="100777">...
  • Page 232: Obtaining Statistics On Past Sync Jobs

    Job Size (MB) duration Job Duration (Sec) avg_sync_rate Average Sync Rate (MB/sec) Example: mirror_statistics_get vol=VolName Output: <job id="143"> <avg_sync_rate value="22.3333"/> <created_at value="2011-03-22 11:19:30"/> <duration value="6"/> <finished_at value="2011-03-22 11:19:36"/> <job_size value="134"/> <started_at value="2011-03-22 11:19:30"/> </job> IBM XIV Storage System User Manual...
  • Page 233: Switching Roles Between Master And Slave

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Allowed Technicians Disallowed Completion Codes: v VOLUME_BAD_NAME Volume name does not exist v CONS_GROUP_NO_MIRROR Local Consistency Group does not have remote mirroring definitions v MIRROR_HAS_NO_STATISTICS Job statistics were not collected for this Mirror.
  • Page 234 Operation is not permitted on a mirror with active sync jobs v MIRROR_RETRY_OPERATION There is an operation in progress on this mirror , please retry your request in a few seconds Troubleshooting: Please retry the command in a few seconds v MIRROR_MASTER_DIFFERS_FROM_SLAVE IBM XIV Storage System User Manual...
  • Page 235: Retrieving Rpo Threshold

    Mirror master was written to after the last replicated snapshot was taken v REMOTE_MIRROR_IS_NOT_ACTIVE Remote mirroring is not active Retrieving RPO Threshold Listing system RPO related thresholds, that once crossed will trigger the creation of a corresponding event rpo_thresholds_get This command lists the system's RPO-related thresholds, that once crossed will trigger the creation of a corresponding event.
  • Page 236: Changes The Interval For A Schedule

    Values should be in [1,1000000] range Changes the Interval For a Schedule Changes the interval of a schedule. schedule_change schedule=Schedule interval=IntervalSize Parameters: Name Type Description Mandatory schedule Object name The name of the schedule. IBM XIV Storage System User Manual...
  • Page 237 Name Type Description Mandatory interval A value that indicates the interval for asynchronous mirroring. Format: hh:mm [ :ss ]. This command updates the schedule definition. Such definition can be referenced to when specifying asynchronous mirroring couplings. Limitation: v Schedule must be one of the following: 00:00:30, 00:01, 00:02, 00:05, 00:10, 00:15, 00:30, 01:00, 02:00, 03:00, 06:00, 08:00, 12:00.
  • Page 238: Creating A Schedule Object

    The type Interval specifies that synchronization jobs for a mirror assigned the schedule will be triggered automatically based on the specified interval; the type IBM XIV Storage System User Manual...
  • Page 239: Triggering A Schedule

    Manual specifies that synchronization jobs for a mirror assigned the schedule can be triggered by the command schedule_create_tick v Once set - the schedule type cannot be changed Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator...
  • Page 240: Deletes A Schedule Object

    The command can be issued successfully only if the schedule specified is not referenced by a mirror coupling, or if it is not a pre-defined schedule (min_interval). Outcome: v Command will delete the schedule specified Example: IBM XIV Storage System User Manual...
  • Page 241: Listing A Schedule Object

    schedule_delete schedule=hourly Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v SCHEDULE_IS_ASSIGNED Specified Schedule is currently assigned to a mirror v SCHEDULE_CAN_NOT_BE_DELETED Specified Schedule cannot be deleted v SCHEDULE_DOES_NOT_EXIST...
  • Page 242: Renaming A Schedule Object

    This command renames the schedule. It is not possible to rename a predefined schedule. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 243: Viewing Sync Job Status

    Completion Codes: v SCHEDULE_DOES_NOT_EXIST Specified Schedule does not exist v SCHEDULE_NAME_EXISTS New Schedule name already exists v SCHEDULE_CAN_NOT_BE_UPDATED Specified Schedule cannot be updated Viewing Sync Job Status Lists the status of queued and running sync jobs for asynchronous couplings sync_job_list [ vol=VolName | cg=cgName ] Parameters: Name...
  • Page 244 Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 245: Chapter 12. Data Migration

    Chapter 12. Data Migration The following sections describe the XIV Command Line Interface (XCLI) for data migration. The sections are listed as follows: dm_activate(Activates the Data Migration process.) dm_deactivate(Deactivates the Data Migration process.) dm_define(Defines a Data Migration configuration.) dm_delete(Deletes the Data Migration process.) dm_list(Lists Data Migration configuration and status.)
  • Page 246: Deactivating Data Migration

    ARE_YOU_SURE_YOU_WANT_TO_DEACTIVATE_DATA_MIGRATION Deactivation will stop all applications, data migration can be deleted if it is done Completion Codes: v VOLUME_BAD_NAME Volume name does not exist v VOLUME_NO_DM Local volume does not have Data Migration definitions IBM XIV Storage System User Manual...
  • Page 247: Defining Data Migration Configuration

    Defining Data Migration Configuration Defines a Data Migration configuration. dm_define vol=VolName target=TargetName lun=SourceLUN source_updating=<yes|no> [ create_vol=<yes|no> ] [ pool=PoolName ] Parameters: Name Type Description Mandatory Default Object name Data Migration destination volume on the local system. target Object name Remote system containing the source volume.
  • Page 248 Volume name already exists v POOL_DOES_NOT_EXIST Storage Pool does not exist v VOLUME_BAD_PREFIX Volume name has a reserved prefix v NOT_ENOUGH_SPACE No space to allocate volume v NOT_ENOUGH_HARD_SPACE No space to allocate for volume's current usage IBM XIV Storage System User Manual...
  • Page 249: Deleting The Data Migration Process

    v MAX_VOLUMES_REACHED Maximum number of volumes already defined v ILLEGAL_VOLUME_SIZE Illegal volume size v REMOTE_VOLUME_NO_LUN Remote volume's LUN is unavailable v TARGET_NOT_CONNECTED There is currently no connection to the target system v VOLUME_CANNOT_HAVE_ZERO_SIZE Volume size cannot be zero v ILLEGAL_LUN LUN is out of range v TARGET_IS_MIRRORING Target machine is defined only for remote mirroring...
  • Page 250: Listing Data Migration Statuses

    Migration activation (active/inactive) v Migration status (synchronized, unsynchronized) v Migration remaining (GB) v Migration remaining (%) v Estimated time to completion Name Default Position Local Volume local_volume_ name target_name Remote System Remote LUN remote_volume_ active Active IBM XIV Storage System User Manual...
  • Page 251: Testing The Data Migration Definition

    Name Default Position sync_state Status connected Target Connected Size To Sync (MB) size_to_ synchronize operational Operational sync_progress Sync Progress (%) Start Data Migration Automatically start_ migration_ automatically Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed...
  • Page 252 There is currently no connection to the target system v REMOTE_VOLUME_NO_LUN Remote volume's LUN is unavailable v REMOTE_VOLUME_NO_READ_ACCESS Remote volume cannot be read v REMOTE_VOLUME_NO_WRITE_ACCESS Remote volume is write protected v BAD_REMOTE_VOLUME_SIZE Master and slave volumes contain a different number of blocks IBM XIV Storage System User Manual...
  • Page 253: Chapter 13. Ibm Hyper-Scale Mobility

    This command creates an IBM Hyper-Scale Mobility relationship between volumes. The command specifies the source volume and the destination system and destination storage pool. From now on, the source volume is also referred to as an IBM Hyper-Scale Mobility volume. Access Control:...
  • Page 254 Read-only users Disallowed Technicians Disallowed Completion Codes: v VOLUME_NOT_APPLICABLE_FOR_OLVM The volume is not applicable for IBM Hyper-Scale Mobility. v VOLUME_BAD_NAME Volume name does not exist v VOLUME_IS_SNAPSHOT Operation is not permitted on snapshots v TARGET_BAD_NAME Target name does not exist...
  • Page 255 INVALID_SLICE_OFFSET Slice number out of range v ILLEGAL_VOLUME_SIZE Illegal volume size v VOLUME_IS_OLVM_PROXY The volume is in an IBM Hyper-Scale Mobility Proxy phase. v VOLUME_IS_SLAVE Volume is defined as a slave volume v REMOTE_VOLUME_IS_SNAPSHOT Chapter 13. IBM Hyper-Scale Mobility...
  • Page 256: Activates The Volume Migration

    This command migrates a IBM Hyper-Scale Mobility volume to the destination system and storage pool as specified with the olvm_create command. From now on, we refer to the process as IBM Hyper-Scale Mobility migration. IBM XIV Storage System User Manual...
  • Page 257: Deactivates Ibm Hyper-Scale Mobility Migration

    Completion Codes: v VOLUME_BAD_NAME Volume name does not exist v COMMAND_NOT_SUPPORTED_FOR_OLVM_SOURCE_IN_THIS_STATE The source is in an unsupported IBM Hyper-Scale Mobility state v MIRROR_CONFIGURATION_ERROR Mirror local configuration does not match remote configuration v MIRROR_CONS_GROUP_MEMBERSHIP_MISMATCH Mirrored CG contains different volumes on Master and Slave. This problem...
  • Page 258: Aborts A Defined Or Activated Ibm Hyper-Scale Mobility Process

    Parameters: Name Type Description Mandatory Object name The source volume. This command deactivates the migration of an IBM Hyper-Scale Mobility volume. This command is issued on the source volume. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator...
  • Page 259 This command aborts the migration of an IBM Hyper-Scale Mobility volume. The migration can be either in a defined or activated stage of the process. This command is issued on the source volume and has the option to abort the migration either from the source volume or the destination volume.
  • Page 260: Moves The Ibm Hyper-Scale Mobility Source Volume To A Proxy State

    Object name The source volume. This command moves the IBM Hyper-Scale Mobility source volume to a Proxy state where the source acts as a proxy to the destination. The source becomes a Proxy and the destination becomes the data 'owner'. Host writes are no longer written to the source and the volume data on the source is freed.
  • Page 261: Deletes An Ibm Hyper-Scale Mobility Relationship

    The destination is in an unsupported IBM Hyper-Scale Mobility state v VOLUME_NOT_DEFINED_FOR_OLVM The volume does not have IBM Hyper-Scale Mobility definitions v OLVM_LINK_IS_NOT_UP IBM Hyper-Scale Mobility link is not up. The mapping list cannot be updated. v HOST_BAD_NAME Host name does not exist v ISCSI_HOST_ILLEGAL_PORT_NAME...
  • Page 262: Listing Ibm Hyper-Scale Mobility Status

    ARE_YOU_SURE_YOU_WANT_TO_DELETE_OLVM_ RELATIONSHIP_IN_THIS_PHASE Are you sure you want to delete IBM Hyper-Scale Mobility relationship? ARE_YOU_SURE_YOU_WANT_TO_FORCE_DELETE_ OLVM_RELATIONSHIP_IN_THIS_PHASE Are you sure you want to force delete IBM Hyper-Scale Mobility relationship? Completion Codes: v VOLUME_BAD_NAME Volume name does not exist v VOLUME_NOT_DEFINED_FOR_OLVM The volume does not have IBM Hyper-Scale Mobility definitions...
  • Page 263 No Error, Secondary pool exhausted, Configuration error or No thin provisioning resources Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Disallowed Chapter 13. IBM Hyper-Scale Mobility...
  • Page 264 IBM XIV Storage System User Manual...
  • Page 265: Chapter 14. Event Handling

    Chapter 14. Event Handling The following sections describe the XIV Command Line Interface (XCLI) for event handling, including listing events, filtering and sending notifications. The sections are listed as follows: custom_event(Generates a custom event.) dest_define(Defines a new destination for event notifications.) dest_delete(Deletes an event notification destination.
  • Page 266: Generating A Custom Event

    Example: custom_event description="Test started" Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 267: Defining A New Event Notification Destination

    Defining a New Event Notification Destination Defines a new destination for event notifications. dest_define dest=DestName type=<SNMP|EMAIL|SMS> < snmp_manager=SNMPManager | email_address=email | <area_code=AreaCode number=PhoneNumber> | user=UserName> [ smtpgws=<SMTPGW1 [,SMTPGW2 ] ... | ALL> | smsgws=<SMSGW1 [ ,SMSGW2 ] ... | ALL> ] [ heartbeat_test_hour=HH:MM [ heartbeat_test_days=Day ] ] Parameters:...
  • Page 268 Command executed successfully. Example: dest_define dest=monitoringserver type=SNMP snmp_manager=10.170.68.111 Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 269: Deleting A Destination

    Completion Codes: v CANNOT_CHANGE_EVENT_CONF_WITH_ALERTING_EVENTS Cannot change event configuration while there are alerting events Troubleshooting: Clear all alerting events before changing event configuration v DEST_MAX_REACHED Maximum number of destinations already defined v DEST_NAME_ALREADY_EXISTS Destination name already exists v DEST_NAME_IS_DESTGROUP_NAME Destination name already exists as a destination group name v EMAIL_NOT_ALLOWED_FOR_DEST_TYPE Destination cannot have an email address v GATEWAY_NAME_APPEARS_TWICE...
  • Page 270 Troubleshooting: Clear all alerting events before changing event configuration v DEST_IS_PART_OF_DESTGROUP Destination is part of a destination group and hence cannot be deleted v DEST_APPEARS_IN_RULE Destination appears in a rule Troubleshooting: To delete the destination, first delete the rule. IBM XIV Storage System User Manual...
  • Page 271: Listing Event Notification Destinations

    Listing Event Notification Destinations Lists event notification destinations. dest_list [ dest=DestName ] [ type=<SNMP|EMAIL|SMS> ] Parameters: Name Type Description Mandatory Default dest Object name Destinations to be All destinations. listed. type Enumeration Filter only All types. destinations of the specified type. This command lists the configuration of all defined destinations, or of a specific destination.
  • Page 272: Renaming A Destination

    Read-only users Disallowed Technicians Disallowed Completion Codes: v CANNOT_CHANGE_EVENT_CONF_WITH_ALERTING_EVENTS Cannot change event configuration while there are alerting events Troubleshooting: Clear all alerting events before changing event configuration v DEST_NAME_DOES_NOT_EXIST Destination name does not exist IBM XIV Storage System User Manual...
  • Page 273: Testing A Destination

    Boolean Must be specified for XIV-internal destinations This command tests a destination by sending a test message, SMS or SNMP trap. Note that a successful return code from this command does not ensure notification delivery. For SNMP, email and SMS the system may fail to detect some of the problems.
  • Page 274: Updating An Event Notification Destination

    Object name Destination name. IP address or DNS Keep unchanged. name of the SNMP snmp_ manager. manager Email address. Keep unchanged. email_ address smtpgws Object name List of SMTP Keep unchanged. gateways to be used. IBM XIV Storage System User Manual...
  • Page 275 Name Type Description Mandatory Default area_code Area code of the Keep unchanged. cellular number for SMS notification. number Cellular number Keep unchanged. for SMS notification. smsgws Object name SMS gateways to Keep unchanged. be used. user Object name User name, where Keep unchanged.
  • Page 276 SNMP destinations cannot refer to users v USER_EMAIL_ADDRESS_IS_NOT_DEFINED User's email address is not defined v SMTPGWS_NOT_ALLOWED_FOR_DEST_TYPE Destination cannot have SMTP gateways v DAY_APPEARS_TWICE The day 'Day' appears twice on the list. Troubleshooting: Each day must appear at most once. IBM XIV Storage System User Manual...
  • Page 277: Adding A Destination To A Destination Group

    v SNMP_MANAGER_MUST_BE_SPECIFIED_FOR_DEST_TYPE Destination must have an SNMP manager v NO_SMS_GATEWAYS_ARE_DEFINED An SMS Destination cannot be defined if no SMS gateways are defined Adding a Destination to a Destination Group Adding an event notification destination to a destination group. destgroup_add_dest destgroup=GroupName dest=DestName Parameters: Name Type...
  • Page 278: Creating A Destination Group

    Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v CANNOT_CHANGE_EVENT_CONF_WITH_ALERTING_EVENTS Cannot change event configuration while there are alerting events Troubleshooting: Clear all alerting events before changing event configuration IBM XIV Storage System User Manual...
  • Page 279: Deleting A Destination Group

    v DESTGROUP_MAX_REACHED Maximum number of destination groups already defined v DESTGROUP_NAME_ALREADY_EXISTS Destination group name already exists v DESTGROUP_NAME_IS_DEST_NAME Destination group name already exists as a destination name Deleting a Destination Group Deletes an event notification destination group. destgroup_delete destgroup=GroupName Parameters: Name Type Description...
  • Page 280: Listing Destination Groups

    Disallowed Read-only users Allowed Technicians Disallowed Removing a Destination from Destination Group Removes an event notification destination from a destination group. destgroup_remove_dest destgroup=GroupName dest=DestName Parameters: Name Type Description Mandatory destgroup Object name Group name. IBM XIV Storage System User Manual...
  • Page 281: Renaming A Destination Group

    Name Type Description Mandatory dest Object name Destination to be removed from the group. This command removes an event notification destination from a destination group. This command cannot be executed while there are uncleared alerting events. Example: destgroup_remove_dest destgroup=alladmins dest=john Output: Command executed successfully.
  • Page 282: Clearing Alerting Events

    Destination group name already exists as a destination name Clearing Alerting Events Clears alerting events. event_clear event_id=EventId [ all_preceding=<yes|no> ] [ internal=<yes|no|all> ] Parameters: Name Type Description Mandatory Default event_id Positive integer ID number of the event to clear. IBM XIV Storage System User Manual...
  • Page 283 Boolean Clears XIV-internal events. This command clears alerting events. In order to ensure that an event was indeed received, an event notification may be sent repeatedly until it is cleared by a CLI command or the GUI. Such events are called alerting events.
  • Page 284: Listing Events

    (not inclusive). If negative, then counts from the end. count_all Boolean If yes, it scans all the events between beg and end for computing the number of events meeting the criteria. IBM XIV Storage System User Manual...
  • Page 285 This command lists system events according to specified criteria, such as minimum severity, event type and so on. The event list displays the following information for each event: timestamp, severity, code, user and description. Events are listed and sorted by time of creation, where the latest events are listed last.
  • Page 286: Listing Uncleared Alerting Events

    Troubleshooting: Consult the manual for the list of event codes v CANNOT_READ_EVENTS Cannot read events. Troubleshooting: Contact support Listing Uncleared Alerting Events Lists uncleared alerting events. event_list_uncleared This command lists uncleared alerting events. Example: event_list_uncleared IBM XIV Storage System User Manual...
  • Page 287: Setting The Threshold For Events Notification

    Output: Index Code Severity ------- --------------- --------------- VOLUME_CREATE Informational VOLUME_DELETE Informational Name Default Position index Index code Code severity Severity Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Allowed Read-only users Allowed Technicians Allowed...
  • Page 288: Listing Thresholds

    Filter by a specific no filter. event code. Lists event thresholds. Name Default Position code Code has_thresholds Has Thresholds? not_in_use Not In Use replaced_by Replaced By INFORMATIONAL(def) default_ thresholds.0 WARNING(def) default_ thresholds.1 MINOR(def) default_ thresholds.2 IBM XIV Storage System User Manual...
  • Page 289 Name Default Position MAJOR(def) default_ thresholds.3 CRITICAL(def) default_ thresholds.4 thresholds.0 INFORMATIONAL thresholds.1 WARNING thresholds.2 MINOR thresholds.3 MAJOR thresholds.4 CRITICAL Example: event_threshold_list Output: Code INFORMATIONAL WARNING MINOR --------------------------------------- --------------- --------- ------- STORAGE_POOL_SNAPSHOT_USAGE_INCREASED none STORAGE_POOL_VOLUME_USAGE_INCREASED none MAJOR CRITICAL INFORMATIONAL(def) WARNING(def) MINOR(def) MAJOR(def) ------- ---------- -------------------- -------------- ------------ ------------ none none...
  • Page 290: Generating A Custom Event

    Receiving a MM Heartbeat Receives a mm heartbeat. mm_heartbeat data=HeartbeatData mm=ComponentId serial=SN part_number=PartNumber total_memory=2048 free_memory=100 temperature=20 version=4.6 free_disk_tmp=200 free_disk_root=1000 free_disk_opt=900 free_disk_var=900 Parameters: Name Type Description Mandatory data String Heartbeat data. Component id of maintenance module. IBM XIV Storage System User Manual...
  • Page 291 Name Type Description Mandatory serial String Serial number of MM. String Part number of MM. part_ number version String Version of SW running on MM. Integer Total RAM of MM. total_ memory Integer Free RAM on MM. free_ memory Integer Temperature of MM.
  • Page 292: Activating A Rule

    Parameters: Name Type Description Mandatory Default rule Object name Name of the new rule. Enumeration Minimum event All severities. severity for rule min_ filtering. severity codes Filter only events All events. with these codes. IBM XIV Storage System User Manual...
  • Page 293 Name Type Description Mandatory Default Filter only events All events. with other codes. except_ codes Boolean Specifies that this rule can only be escalation used for escalation. _only dests Object name Comma separated list of destinations and destination groups for event notification.
  • Page 294 Disallowed Technicians Disallowed Completion Codes: v CANNOT_CHANGE_EVENT_CONF_WITH_ALERTING_EVENTS Cannot change event configuration while there are alerting events Troubleshooting: Clear all alerting events before changing event configuration v EVENT_RULE_MAX_REACHED Maximum number of event rules already defined IBM XIV Storage System User Manual...
  • Page 295: Deactivating A Rule

    v EVENT_RULE_CANNOT_ESCALATE_TO_NON_ALERTING_RULES Event rule cannot escalate to non-alerting rule Troubleshooting: Alerting rule can only escalate to another escalating rule v DEST_APPEARS_TWICE Destination or destination group appears twice v EVENT_RULE_NAME_ALREADY_EXISTS Event rule name already exists v EVENT_RULE_NAME_DOES_NOT_EXIST Event rule name does not exist v NAME_IS_NEITHER_DEST_NOR_GROUP Name is neither the name of a destination group nor the name of a destination v ESCALATION_TIME_MUST_BE_LARGER_THAN_SNOOZE_TIME...
  • Page 296: Deleting Event Notification Rules

    Rules that are defined as the escalation of other rules cannot be deleted. It is not permitted to delete a rule while there are uncleared alerting events. Example: rule_delete rule=emergency_alerts Output: Command completed successfully. IBM XIV Storage System User Manual...
  • Page 297: Listing Event Notification Rules

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Warnings: v ARE_YOU_SURE_YOU_WANT_TO_DELETE_RULE Are you sure you want to delete Rule Rule? Completion Codes: v CANNOT_CHANGE_EVENT_CONF_WITH_ALERTING_EVENTS Cannot change event configuration while there are alerting events Troubleshooting: Clear all alerting events before changing event configuration v EVENT_RULE_NAME_DOES_NOT_EXIST Event rule name does not exist...
  • Page 298: Renaming Event Notification Rules

    Parameters: Name Type Description Mandatory rule Object name Rule to be renamed. new_name Object name New name of the rule. This command renames an event notification rule. Example: rule_rename rule=critical_alerts new_name=emergency_alerts Output: IBM XIV Storage System User Manual...
  • Page 299: Updating An Event Notification Rule

    Command completed successfully Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v CANNOT_CHANGE_EVENT_CONF_WITH_ALERTING_EVENTS Cannot change event configuration while there are alerting events Troubleshooting: Clear all alerting events before changing event configuration v EVENT_RULE_NAME_ALREADY_EXISTS Event rule name already exists v EVENT_RULE_NAME_DOES_NOT_EXIST...
  • Page 300 Cannot change event configuration while there are alerting events Troubleshooting: Clear all alerting events before changing event configuration v EVENT_RULE_CANNOT_ESCALATE_TO_ITSELF An event rule cannot be its own escalation rule v EVENT_RULE_CANNOT_ESCALATE_TO_NON_ALERTING_RULES Event rule cannot escalate to non-alerting rule IBM XIV Storage System User Manual...
  • Page 301 Troubleshooting: Alerting rule can only escalate to another escalating rule v DEST_APPEARS_TWICE Destination or destination group appears twice v EVENT_RULE_MISSING_ESCALATION_RULE An alerting event rule must have an escalation rule Troubleshooting: If escalation time is specified, then an escalation rule must be specified also.
  • Page 302: Defining An Sms Gateway

    SMS messages are encapsulated in the email message. When the XIV system sends an SMS message it uses the actual message text that describes the event and the destination number. The destination number is...
  • Page 303 {areacode}. This escape sequence is replaced by the destination's cellular number area code. {number}. This escape sequence is replaced by the destination's cellular local number. {message}. This escape sequence is replaced by the text to be shown to the user. v \{, \}, \\.
  • Page 304: Deleting An Sms Gateway

    CANNOT_CHANGE_EVENT_CONF_WITH_ALERTING_EVENTS Cannot change event configuration while there are alerting events Troubleshooting: Clear all alerting events before changing event configuration v GATEWAY_NAME_DOES_NOT_EXIST Gateway name does not exist v GATEWAY_USED_BY_DESTINATION Gateway is used by a destination IBM XIV Storage System User Manual...
  • Page 305: Listing Sms Gateways

    Listing SMS Gateways Lists SMS gateways. smsgw_list [ smsgw=SMSGatewayName ] Parameters: Name Type Description Mandatory Default smsgw Object name Name of SMS All gateways. gateway to list. Lists all SMS gateways or a specific one. For each SMS gateway all its configuration information is listed.
  • Page 306 This command sets the priority in which SMS gateways are used to send SMSs. SMS messages can be sent to cell phones through one of the email-to-SMS gateways in this list. This command determines the order in which XIV attempts to use these SMS gateways.
  • Page 307: Renaming An Sms Gateway

    Renaming an SMS Gateway Renames an SMS gateway. smsgw_rename smsgw=SMSGatewayName new_name=Name Parameters: Name Type Description Mandatory smsgw Object name SMS gateway to be renamed. new_name Object name New name for the SMS gateway. This command renames an SMS gateway. SMS gateways cannot be renamed while there are uncleared alerting events. Example: smsgw_rename smsgw=SMSGW2 new_name=external-SMSGW Output:...
  • Page 308: Updating An Sms Gateway

    Parameters which are not specified will not be changed. Example: smsgw_update smsgw=SMSGW1 email_address={areacode}{number}@sms2emailserver.yourcompany.com subject_line=NextraSMS email_body={message} Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed IBM XIV Storage System User Manual...
  • Page 309: Defining A New Smtp Gateway

    SMS messages via Email-to-SMS gateways. By default, XIV attempts to send each email notification through the first gateway according to the order that you specify. Subsequent gateways are only tried if the first in line returns an error.
  • Page 310 Troubleshooting: Clear all alerting events before changing event configuration v FROM_ADDRESS_NOT_DEFINED Neither the gateway's From Address nor the default From Address is defined v GATEWAY_MAX_REACHED Maximum number of gateways already defined v GATEWAY_NAME_ALREADY_EXISTS Gateway name already exists IBM XIV Storage System User Manual...
  • Page 311: Deleting An Smtp Gateway

    Deleting an SMTP Gateway Deletes a specified SMTP gateway. smtpgw_delete smtpgw=SMTPGatewayName Parameters: Name Type Description Mandatory smtpgw Object name SMTP gateway to be deleted. This command deletes a specified SMTP gateway. A gateway cannot be deleted if it is part of a notification rule, is being used as an SMS gateway or if it belongs to a destination.
  • Page 312: Listing Smtp Gateways

    Storage integration administrator Disallowed Application administrator Conditionally Allowed Only the technician can run this command with the internal parameter Security administrator Disallowed Read-only users Conditionally Allowed Only the technician can run this command with the internal parameter IBM XIV Storage System User Manual...
  • Page 313: Prioritizing Smtp Gateways

    Several email gateways can be defined to enable notification of events or the sending of SMS by email. By default, XIV attempts to send each email through the first gateway according to the order that is specified in this command. Only one gateway is used and subsequent gateways are only tried if the preceding ones in this priority list return an error.
  • Page 314: Renaming An Smtp Gateway

    Completion Codes: v CANNOT_CHANGE_EVENT_CONF_WITH_ALERTING_EVENTS Cannot change event configuration while there are alerting events Troubleshooting: Clear all alerting events before changing event configuration v GATEWAY_NAME_ALREADY_EXISTS Gateway name already exists v GATEWAY_NAME_DOES_NOT_EXIST Gateway name does not exist IBM XIV Storage System User Manual...
  • Page 315: Updating An Smtp Gateway

    SMTP gateway Leave unchanged. address (IP or DNS name). internal Boolean Should be specified as YES for XIV internal gateway. Sender's Email Leave unchanged. address used for from_ out-going emails address sent through this SMTP server, or DEFAULT for the system-wide default.
  • Page 316 Cannot change event configuration while there are alerting events Troubleshooting: Clear all alerting events before changing event configuration v FROM_ADDRESS_NOT_DEFINED Neither the gateway's From Address nor the default From Address is defined v ONLY_TECHNICIAN_CAN_REFER_TO_INTERNAL_EVENT_OBJECTS Only technician can refer to internal event objects IBM XIV Storage System User Manual...
  • Page 317: Chapter 15. Ip Configuration

    Chapter 15. IP Configuration The following sections describe the XIV Command Line Interface (XCLI) for IP configuration. The sections are listed as follows: ipinterface_add_port(Adds an Ethernet port to the link aggregation group of an IP interface.) ipinterface_create(Creates a new IP interface for iSCSI.) ipinterface_delete(Deletes an IP interface.)
  • Page 318 One of the physical ports specified is already assigned to an IP Interface v COMMAND_NOT_ALLOWED_ON_MANAGEMENT_INTERFACE Operation is not allowed on Management IP Interface v IPINTERFACE_NOT_AGGREGATED Ports cannot be added to a non-aggregated IP Interface IBM XIV Storage System User Manual...
  • Page 319: Creating A New Ip Interface

    Creating a New IP Interface Creates a new IP interface for iSCSI. ipinterface_create ipinterface=IPInterfaceName address=Address netmask=NetworkMask [ gateway=DefaultGateway ] [ mtu=MTU ] module=ModuleNumber ports=<P1,...> [ speed=<auto|10mb|100mb|1000mb|1gb|2500mb|2.5gb|10000mb|10gb> ] Parameters: Name Type Description Mandatory Default Object name Name of the IP interface to be ipinterfac created.
  • Page 320 TOO_MANY_PORTS_IN_AGGREGATION_GROUP Too many physical ports for one IP interface v ILLEGAL_IPADDRESS Illegal IP address was entered v DUPLICATE_IPADDRESSES Duplicate IP addresses were specified v ILLEGAL_GATEWAY_IPADDRESS Illegal IP address was specified for default gateway IBM XIV Storage System User Manual...
  • Page 321: Deleting Ip Interfaces

    Deleting IP Interfaces Deletes an IP interface. ipinterface_delete ipinterface=IPInterfaceName Parameters: Name Type Description Mandatory Object name IP interface to be deleted. ipinterfac This command deletes the IP interface. Only the interfaces defined for iSCSI traffic can be deleted. Management and VPN interfaces cannot be deleted. Access Control: User Category Permission...
  • Page 322 IPv6 Address gateway6 IPv6 Gateway module Module ports Ports speed Speed Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed IBM XIV Storage System User Manual...
  • Page 323: Listing Ip Interface Addresses

    Listing IP Interface Addresses Lists the IP addresses configured on a specific IP interface or all IP interfaces. ipinterface_list_ips [ ipinterface=IPInterfaceName | address=Address | address6=IPv6address | module=ModuleNumber ] Parameters: Name Type Description Mandatory Default Object name IP interface to be All interfaces listed.
  • Page 324: Showing The Status And Configuration Of Ethernet Ports

    Link Up? Negotiated Speed (Mb/s) negotiated_ speed_Mbs is_full_duplex Full Duplex? module_id Module Requires Service requires_ service service_reason Service Reason Flow control auto-negotiate? pause_ autonegotiate pause_rx RX Flow Control? pause_tx TX Flow Control? IBM XIV Storage System User Manual...
  • Page 325: Removing Ethernet Ports From Ip Interfaces

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed Removing Ethernet Ports from IP Interfaces Removes an Ethernet port from the link aggregation group of an IP interface. ipinterface_remove_port ipinterface=IPInterfaceName port=P Parameters: Name...
  • Page 326: Renaming An Ip Interface

    IP Interface name already used v COMMAND_NOT_ALLOWED_ON_MANAGEMENT_INTERFACE Operation is not allowed on Management IP Interface Printing the ARP Database of an IP Interface Prints the ARP database of the specified IP interface. ipinterface_run_arp localipaddress=IPaddress | localipaddress6=IPv6address IBM XIV Storage System User Manual...
  • Page 327: Testing The Traceroute To A Remote Ip

    Parameters: Name Description Mandatory IP address of the IP interface for which the ARP database should localipadd be printed. ress IPv6 address of the IP interface for which the ARP database localipadd should be printed. ress6 This command prints the ARP database of an IP interface, meaning a list of pairs of IP addresses and their associated Ethernet MAC addresses.
  • Page 328: Testing The Traceroute To A Remote Ip

    This command runs a route trace to the specified remote host through the specified IP interface. The IP address must be one of the IP addresses defined for iSCSI IP interfaces or the Management or VPN name. Name Default Position traceroute Output traceroute_ output IBM XIV Storage System User Manual...
  • Page 329: Updating An Ip Interface

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Completion Codes: v NO_IP_INTERFACE_MATCHES_CRITERIA No IP Interface matches given criteria v MORE_THAN_ONE_IP_INTERFACE_MATCHES More than one IP Interface matches given criteria Updating an IP Interface Updates the configuration of an IP interface.
  • Page 330 IP addresses management modules must all be in the same subnet v IPINTERFACE_MANAGEMENT_MISSING_IPS Number of IP addresses specified is less than the number of management modules v IPINTERFACE_MANAGEMENT_TOO_MANY_IPS Number of IP addresses specified is larger than the number of management modules v MTU_TOO_LARGE IBM XIV Storage System User Manual...
  • Page 331: Defines A New Ipsec Connection

    Specified MTU value is too large v ILLEGAL_IPADDRESS Illegal IP address was entered v DUPLICATE_IPADDRESSES Duplicate IP addresses were specified v ILLEGAL_GATEWAY_IPADDRESS Illegal IP address was specified for default gateway v ILLEGAL_IPV6ADDRESS Illegal IPv6 address was entered v DUPLICATE_IPV6ADDRESSES Duplicate IPv6 addresses were specified v ILLEGAL_GATEWAY_IPV6_ADDRESS Illegal IPv6 address was specified for default gateway v IPV6ADDRESS_AND_GATEWAY_ARE_NOT_ON_SAME_SUBNET...
  • Page 332 A connection between these endpoints already exists v LEFT_INTERFACE_NOT_FOUND The specified left side interface was not found v MAX_IPSEC_CONNECTIONS_REACHED The maximum allowed number of IPSec connections is already configured v IPSEC_UNSUPPORTED_FOR_ISCSI IPSec is unsupported for iSCSI ports IBM XIV Storage System User Manual...
  • Page 333: Updates An Existing Ipsec Connection

    Updates an Existing IPSec Connection Updates an existing IPSec connection ipsec_connection_update ipsec_connection=ConnectionName [ left=IPInterfaceName ] [ right_ip=RightIpAddress ] [ passkey=PassKey | certificate=PemCertificate ] Parameters: Name Type Description Mandatory Default Object name Name of the IPSec connection to be ipsec_ updated. connection left Object name...
  • Page 334: Removes An Existing Ipsec Connection

    Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Completion Codes: v IPSEC_CONNECTION_DOES_NOT_EXIST The specified IPSec connection does not exist Listing IPSec Connections Lists the IPSec connections. ipsec_connection_list [ ipsec_connection=ConnectionName ] IBM XIV Storage System User Manual...
  • Page 335: Listing Ipsec Tunnels

    Parameters: Name Type Description Mandatory Default Object name IPSec connection All IPsec to be listed. connections ipsec_ connection Lists specific IPSec connection or all of them. The following information is listed: v Name v Type (PSK, RSA, RSA/PSK) v Interface v Right ip Name Default Position...
  • Page 336: Connecting To A Support Center

    Read-only users Allowed Technicians Allowed Connecting to a Support Center This command connects to a support center. support_center_connect [ < timeout=Timeout [ idle_timeout=IdleTimeout ] > | always_on=<yes|no> ] [ module=ModuleNumber ] [ password=Password ] IBM XIV Storage System User Manual...
  • Page 337 Parameters: Name Type Description Mandatory Default timeout Specifies the none duration of the session. After the duration elapses, the session will be disconnected. Time is specified in hh:mm format. Specifies the idle [timeout] time for the idle_ session after which timeout it will be disconnected.
  • Page 338: Defining A Support Center

    This command defines a support center. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed IBM XIV Storage System User Manual...
  • Page 339: Deleting A Support Center

    CANNOT_DELETE_WHILE_SUPPORT_CENTER_IS_RUNNING Support Center is running. Disconnect before deleting. Disconnecting from a Support Center This command disconnects the IBM XIV Storage System from a support center. support_center_disconnect This command disconnects the IBM XIV Storage System from a support center. Chapter 15. IP Configuration...
  • Page 340: Listing Support Centers

    Name Default Position name Name address Address port Port priority Priority Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed IBM XIV Storage System User Manual...
  • Page 341: Presenting Status Of A Support Center

    Presenting Status of a Support Center This command lists information about all defined support centers. support_center_status This command lists information about all defined support centers. Name Default Position state State Connected sessions connected_ support_ sessions Timeout (min) minutes_to_ timeout Module running_from_ module start_time...
  • Page 342: Disabling Tcp Sack

    Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Completion Codes: v COULD_NOT_GET_HW_MON_LOCAL Could not get hardware monitor local from configuration IBM XIV Storage System User Manual...
  • Page 343: Chapter 16. Pki Configuration

    XIV allows you to install certificates generated by your own Certificate Authority (CA) for the different services that use digital certificates (SSL authentication, IPSec, etc). When you install a certificate in XIV, it is associated with a name that you provide which is used for managing it.
  • Page 344: Generate Certificate Signing Request

    The argument must be formatted as /type0=value0/ type1=value1/type2=..Generate Certificate Signing Request Example: xcli -u -c XIV1 pki_generate_csr name subject Name Default Position Access Control: User Category Permission Storage administrator Allowed IBM XIV Storage System User Manual...
  • Page 345: Generate A Private Key And Csr

    Completion Codes: v FAILED_CREATING_CERTIFICATE_SIGNING_REQUEST Failed to generate the certificate signing request Troubleshooting: Generate a certificate signing request specifying a correct subject (e.g., '/C=US/CN=IBM') v CERTIFICATE_NAME_DOES_NOT_EXIST Certificate name was not found Troubleshooting: Choose a different name Generate a Private Key and CSR...
  • Page 346: Delete A Pki Content

    String The certificate symbolic name Delete a PKI Content Example: xcli -u -c XIV1 pki_remove name="my_cert" Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Allowed IBM XIV Storage System User Manual...
  • Page 347: Change Pki Symbolic Name

    User Category Permission Read-only users Disallowed Technicians Disallowed Warnings: v ARE_YOU_SURE_YOU_WANT_TO_DELETE_CERTIFICATE Are you sure you want to delete certificate? Completion Codes: v CERTIFICATE_NAME_DOES_NOT_EXIST Certificate name was not found Troubleshooting: Choose a different name v DEFAULT_CERTIFICATE_CANNOT_BE_DELETED Default certificate cannot be deleted. Change PKI Symbolic Name Change PKI Symbolic Name pki_rename name=Name new_name=Name...
  • Page 348: Import Signed Certificate

    Troubleshooting: Check the certificate v PRIVATE_KEY_ALREADY_HAS_OTHER_CERTIFICATE The private key matching this certificate already has other certificate Troubleshooting: Use the pki_update command if you want to replace the certificate v CERTIFICATE_KEY_WAS_NOT_FOUND Failed to set certificate IBM XIV Storage System User Manual...
  • Page 349: Import Pkcs#12 Certificate

    Troubleshooting: Check the parameters Import PKCS#12 Certificate Import PKCS#12 Certificate pki_set_pkcs12 name=Name password=Password certificate=Base64Data [ services=<xcli [ ,cim ] [ ,ipsec ] ... | ALL | NONE> ] Parameters: Name Type Description Mandatory Default services Comma seperated none list of services to use this certificate password String...
  • Page 350: Show Signed Certificate Details

    Troubleshooting: Choose a different name Update PKI Certificate or Services Update PKI Certificate or Services pki_update name=Name [ services=<xcli [ ,cim ] [ ,ipsec ] ... | ALL | NONE> ] [ certificate=SigendCertificate ] IBM XIV Storage System User Manual...
  • Page 351 Parameters: Name Type Description Mandatory Default services Comma seperated none list of services that need to use this certificate name String The certificate symbolic name If this parameter is none mentioned - the certificat certificate will be replaced Update PKI Certificate or Services Example: xcli -u -c XIV1 pki_update name=cert services=xcli,cim Access Control:...
  • Page 352 IBM XIV Storage System User Manual...
  • Page 353: Chapter 17. Infiniband

    Chapter 17. Infiniband The following sections describe the XIV Command Line Interface (XCLI) for Infiniband Fabric management. The sections are listed as follows: ib_port_move(Moves existing infiniband port definition to a different port number on the same switch.) ib_port_list(Lists configured IB ports.) ib_port_perf_resume(Resume a port that was shutdown due to performance problems.)
  • Page 354: Lists Configured Ib Ports

    Status v Allow Any GUID v GUID v State v Currently Functioning v Requires Service v Service Reason v SM Port in Test v SM Port is Master v SM Port Target State IBM XIV Storage System User Manual...
  • Page 355: Resumes A Port That Was Shutdown Due To Performance Problems

    v SM Port Status Name Default Position port Port component_id Connected Component status Status skip_miswire Allow Any GUID GUID saved_ info.peer_guid State saved_ info.last_ state Failure Reason saved_ info.port_ down_reason Currently Functioning currently_ functioning Requires Service requires_ service service_reason Service Reason SM Port in Test sm_port_in_ test...
  • Page 356: Resumes A Module Infiniband Port That Was Shutdown Due To Performance Problems

    Resume a module Infiniband port that was shutdown due to performance problems. Port must be defined in the configuration an module must be not failed. Example: xcli -u -c XIV1 ib_port_power_on ib_component=1:IB_Module_Port:1:1 IBM XIV Storage System User Manual...
  • Page 357: Collecting Ib Switch Logs

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Completion Codes: v IB_PORT_NOT_VALID Illegal number for IB port was given. Collecting IB Switch Logs Collect IB switch logs. ib_get_switch_logs ib_switch=ComponentId target_module=ComponentId Parameters: Name...
  • Page 358: List Configured Ib Switches

    IS4 Ambient Temperature temp_is4_ ambient temp_board Board Temperature fans_rpm.0 Fan #1 RPM fans_rpm.1 Fan #2 RPM fans_rpm.2 Fan #3 RPM fans_rpm.3 Fan #4 RPM voltage.0 Expected Voltage #1 Expected Voltage #1 expected_ voltage.0 IBM XIV Storage System User Manual...
  • Page 359 Name Default Position voltage.1 Expected Voltage #2 Expected Voltage #2 expected_ voltage.1 voltage.2 Expected Voltage #3 Expected Voltage #3 expected_ voltage.2 voltage.3 Expected Voltage #4 Expected Voltage #4 expected_ voltage.3 voltage.4 Expected Voltage #5 Expected Voltage #5 expected_ voltage.4 voltage.5 Expected Voltage #6 Expected Voltage #6 expected_...
  • Page 360 Previous VPD - CPU S/N prev_vpd.cpu_ Previous ASIC firmware version prev_vpd.asic_ fw_version Previous Management firmware version prev_vpd.mgmt_ fw_version Initial VPD - Chassis type initial_ vpd.chassis_ type Initial VPD - Managemet type initial_ vpd.mgmt_type IBM XIV Storage System User Manual...
  • Page 361: List Sm Port Service Statuses

    Name Default Position Initial VPD - CPU type initial_ vpd.cpu_type Initial VPD - Chassis P/N initial_ vpd.chassis_pn Initial VPD - Management P/N initial_ vpd.mgmt_pn Initial VPD - CPU P/N initial_ vpd.cpu_pn Initial VPD - Chassis S/N initial_ vpd.chassis_sn Initial VPD - Management S/N initial_ vpd.mgmt_sn Initial VPD - CPU S/N...
  • Page 362 PORT2 Conf sm_port2_ config PORT1_IS_M is_port1_ master PORT2_IS_M is_port2_ master Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed IBM XIV Storage System User Manual...
  • Page 363: Chapter 18. Access Control

    Chapter 18. Access Control The following sections describe the XIV Command Line Interface (XCLI) for user access control. The sections are listed as follows: access_define(Defines an association between a user group and a host.) access_delete(Deletes an access control definition.) access_list(Lists access control definitions.) cr_show_console_access(Shows whether challenge-response authentication is enabled on system consoles.)
  • Page 364: Deleting An Access Control Definition

    Cluster name does not exist v HOST_BAD_NAME Host name does not exist v HOST_BELONGS_TO_CLUSTER Host is part of a cluster Deleting an Access Control Definition Deletes an access control definition. access_delete user_group=UserGroup < host=HostName | cluster=ClusterName > IBM XIV Storage System User Manual...
  • Page 365 Parameters: Name Type Description Mandatory user_group Object name User group of the access control definition to be deleted. host Object name Host of the access control definition to be deleted. cluster Object name Cluster of the access control definition to be deleted.
  • Page 366: Listing Access Control Definitions

    Example: access_list host=buffyvam Output: Type Name User Group host buffyvam testing Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 367: Determining Whether Challenge-Response Authentication Is Enabled On System Consoles

    Completion Codes: v HOST_BAD_NAME Host name does not exist v CLUSTER_BAD_NAME Cluster name does not exist v USER_GROUP_NAME_DOES_NOT_EXIST User group name does not exist Determining Whether Challenge-Response Authentication is Enabled on System Consoles. Shows whether challenge-response authentication is enabled on system consoles. cr_show_console_access Shows whether challenge-response authentication is enabled on system consoles.
  • Page 368: Adding An Ldap Server Definition

    LDAP server. base_dn Base_DN of the LDAP server. Serves as the starting reference point for searches The content of a no certificate .pem file, with certificat asterisks (*) instead of newlines. port Integer Port number IBM XIV Storage System User Manual...
  • Page 369: Testing An Ldap Configuration

    Name Type Description Mandatory Default Integer Secure port number secure_ port This command adds an LDAP server to the system. Example: ldap_add_server fqdn=ldap.example.com address=1.2.3.4 Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator...
  • Page 370 User User Name was not uniquely authenticated by LDAP server 'Server FQDN'. v LOGIN_FAILURE_LDAP_SERVER_UNREACHABLE No LDAP server can be reached. v LOGIN_FAILURE_XIV_USER_NOT_AUTHENTICATED_BY_LDAP_SERVER XIV User 'XIV User' was not authenticated by LDAP server 'Server FQDN'. v LOGIN_FAILURE_LDAP_SERVER_UNREACHABLE_OR_USER_NOT_FOUND User User Name was not found in LDAP servers 'Servers FQDN'. v LOGIN_FAILURE_INVALID_BASE_DN The base dn of server 'Server FQDN' is invalid.
  • Page 371: Listing Ldap Configuration Parameters

    User User Name was not authenticated by LDAP server 'Server FQDN'. v LOGIN_FAILURE_USER_HAS_NO_RECOGNIZED_ROLE User User Name has no recognized LDAP role. v LOGIN_FAILURE_USER_HAS_MORE_THAN_ONE_RECOGNIZED_ROLE User User Name has more than one recognized LDAP role. v LOGIN_FAILURE_USER_MISSING_ID_ATTRIBUTE User User Name is missing the LDAP ID attribute 'Attribute'. v LOGIN_FAILURE_USER_MISSING_GROUP_ATTRIBUTE User User Name is missing the group attribute 'Attribute'.
  • Page 372: Configuring Ldap In The System

    If not attrib specified, it is set to uid for Sun Directory servers userPrincipalName for Microsoft Active Directory servers. String LDAP attribute none designated to hold xiv_group_ XIV-mapped roles attrib IBM XIV Storage System User Manual...
  • Page 373 Name Type Description Mandatory Default String LDAP value none mapped to the XIV storage_ storage admin_role administrator role. Multiple (up to 8) values are supported and must be separated using a semicolon (;). Multiple roles are not available for Sun Directory LDAP Servers.
  • Page 374 Whenever an LDAP user - with a user name identical to any of the predefined names - tries to log into XIV (when LDAP authentication is enabled), that user will normally be denied access, since it is not authenticated against LDAP (but rather against XIV), and the user's (LDAP) password will likely not match the XIV password.
  • Page 375 LDAP settings (e.g., association with an XIV application admin role), as LDAP is not consulted for predefined users. Example: ldap_config_set base_dn version xiv_group_attrib...
  • Page 376: Listing Ldap Servers Defined In The System

    <last_change_index value="367896"/> <status value="0"/> <status_str value="Command completed successfully"/> Name Default Position fqdn FQDN address Address base_dn Base DN Has Certificate has_ certificate Expiration Date expiration_ date Valid Certificate valid_ certificate accessible Accessible port Port IBM XIV Storage System User Manual...
  • Page 377: List Ldap Server Users

    Name Default Position secure_port Secure Port Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed List LDAP Server Users List LDAP server users ldap_user_list role=Category Parameters: Name Type Description...
  • Page 378: Listing Ldap-Based Authentication Mode

    LDAP_IS_NOT_FULLY_CONFIGURED LDAP is not fully configured Troubleshooting: Check your settings. v LOGIN_FAILURE_XIV_USER_NOT_AUTHENTICATED_BY_LDAP_SERVER XIV User 'XIV User' was not authenticated by LDAP server 'Server FQDN'. v LOGIN_FAILURE_LDAP_SERVER_UNREACHABLE No LDAP server can be reached. v LOGIN_FAILURE_INVALID_BASE_DN The base dn of server 'Server FQDN' is invalid.
  • Page 379: Enabling Or Disabling Ldap-Based Authentication Mode

    User Category Permission Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Enabling or Disabling LDAP-Based Authentication Mode Enables/disables LDAP-based authentication mode. ldap_mode_set mode=Mode Parameters: Name Type Description Mandatory mode Boolean Required state of LDAP authentication. Available values: Active, Inactive. This command enables, or disables, LDAP-based authentication. Example: ldap_mode_set mode=active Output:...
  • Page 380: Updating An Ldap Server Definition

    Example: xcli -u -c XIV1 ldap_update_server fqdn=ldap.example.com address=1.2.3.4 remove_certificate=yes Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed IBM XIV Storage System User Manual...
  • Page 381: Removing An Ldap Server Definition

    User Category Permission Technicians Disallowed Warnings: v ARE_YOU_SURE_YOU_WANT_TO_UPDATE_LDAP_SERVER Are you sure you want to update the LDAP server configuration? Completion Codes: v LDAP_SERVER_NOT_FOUND LDAP server with specified FQDN is not defined in the system v SSL_CERTIFICATE_HAS_EXPIRED SSL certificate has expired. v ADDRESS_CURRENTLY_ASSOCIATED_WITH_ANOTHER_LDAP_SERVER The specified IP address is currently associated with another LDAP server v BAD_SSL_CERTIFICATE...
  • Page 382: Running Ldapsearch Utility

    Runs ldapsearch utility. there are 2 ldap search commands executed in the authentication process. the second one can be selected by setting the second_cmd to yes. Example: ldap_search fqdn user password Output: IBM XIV Storage System User Manual...
  • Page 383: Defining A New User

    Name Index Value -------------- ------- ------------------------------------------------------ command_line ldapsearch -H ldap://ldapwin2003.xivldap2.com:389... returncode stderr stdout dn: CN=employee,CN=Users,DC=xivldap2,DC=com stdout description: Group One stdout objectSid:: AQUAAAAAAAUVAAAAYcKhSnhmt01IPSuAbQQAAA== stdout stdout Name Default Position name Name index Index value Value Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed...
  • Page 384 Two predefined users are set system-wide: Admin and Technician. Example: user_define user=xiv_user1 password=s0mePassw0rd password_verify=s0mePassw0rd category=applicationadmin Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Allowed IBM XIV Storage System User Manual...
  • Page 385: Deleting A User

    User Category Permission Read-only users Disallowed Technicians Disallowed Completion Codes: v USER_NAME_ALREADY_EXISTS User name already exists v MAX_USERS_REACHED Maximum number of users already defined v PASSWORDS_DO_NOT_MATCH Passwords must be identical v USER_PHONE_NUMBER_MUST_ACCOMPANY_AREA_CODE Phone numbers and area code must be defined together v LDAP_AUTHENTICATION_IS_ACTIVE Command is not available while LDAP authentication is active Deleting a User...
  • Page 386: Adding Users To A User Groups

    A user may belong to only one user group. Only users defined as Application Administrators can be assigned to a group. This command fails when the user already belongs to the user group. Example: user_group_add_user user_group=ug1 user=user1 Output: Command executed successfully. IBM XIV Storage System User Manual...
  • Page 387: Creating User Groups

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v USER_GROUP_NAME_DOES_NOT_EXIST User group name does not exist v USER_NAME_DOES_NOT_EXIST User name does not exist v USER_ALREADY_INCLUDED_IN_ANOTHER_GROUP User is included in another user group v USER_GROUP_ALREADY_INCLUDES_USER...
  • Page 388 Example: user_group_create user_group=ug1 ldap_role="App Admin 1" access_all=yes Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 389: Deleting A User Group

    Completion Codes: v USER_GROUP_NAME_ALREADY_EXISTS User group name already exists v MAX_USER_GROUPS_REACHED Maximum number of user groups already defined v LDAP_ROLE_ALREADY_USED LDAP role is already in use in LDAP configuration or in a user group Deleting a User Group Deletes a user group. user_group_delete user_group=UserGroup Parameters: Name...
  • Page 390: Listing User Groups

    Users creator Creator Example: user_group_list Output: Name Access All LDAP Role Users myug1 Group1 myOtherUG OtherGroup App Admin 1 App Admin 2 Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed IBM XIV Storage System User Manual...
  • Page 391: Removing A User From A User Group

    User Category Permission Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Disallowed Removing a User from a User Group Removes a user from a user group. user_group_remove_user user_group=UserGroup user=UserName Parameters: Name Type Description Mandatory user_group Object name User group. user Object name User to be removed.
  • Page 392: Renaming User Groups

    Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v USER_GROUP_NAME_DOES_NOT_EXIST User group name does not exist v USER_GROUP_NAME_ALREADY_EXISTS User group name already exists IBM XIV Storage System User Manual...
  • Page 393: Updating A User Group

    Updating a User Group Updates a user group. user_group_update user_group=UserGroup [ ldap_role=LdapRole ] [ access_all=<yes|no> ] Parameters: Name Type Description Mandatory Default user_group Object name The name of the user group to be updated. ldap_role String The value Keep current representing the LDAP role.
  • Page 394: Listing Users

    Passwords are not shown in the list. Name Default Position name Name category Category group Group active Active email_address Email Address area_code Area Code number Phone Number access_all Access All creator Creator Creator Category creator_ category Example: user_list Output: IBM XIV Storage System User Manual...
  • Page 395: Renaming Users

    Name Category Group xiv_development xiv_development xiv_maintenance xiv_maintenance admin storageadmin technician technician Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Disallowed Renaming Users Renames a user. user_rename user=UserName new_name=Name Parameters: Name Type...
  • Page 396: Updating A User Definition

    (for event notification via SMS) excluding the area code. area_code Area code of the Leaves the current cellular phone area code. number of the user. This command updates the configuration of a user. IBM XIV Storage System User Manual...
  • Page 397 A user with the predefined password admin can change the passwords of other users. The Category (Role) of a user cannot be changed. The user Technician does not require a phone number and an email address. Limitations on password changes are as follows: v Any user can change his/her own password.
  • Page 398 User not allowed to have phone number v USER_NOT_ALLOWED_TO_HAVE_EMAIL_ADDRESS User not allowed to have email address v USER_NOT_ALLOWED_TO_CHANGE_PASSWORDS This user cannot change passwords of other users v USER_CANNOT_BE_UPDATED_WHILE_LDAP_ AUTHENTICATION_IS_ACTIVE User cannot be updated while LDAP authentication is active IBM XIV Storage System User Manual...
  • Page 399: Chapter 19. Fibre Channel And Iscsi Configuration And Status

    When type=target, the non-logged-in option can only be used to debug targets that rejected the XIV login. This command creates an error for a target-only port to list targets, or for an initiator-only port to list initiators.
  • Page 400: Changing Fc Port Configuration

    Line rate or auto Leaves the rate for auto-negotiated unchanged. rate. This command changes the configuration of a port. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed IBM XIV Storage System User Manual...
  • Page 401: Listing Fc Ports

    User Category Permission Read-only users Disallowed Technicians Disallowed Completion Codes: v COMPONENT_IS_NOT_AN_FC_PORT Component must specify an FC port v FC_PORT_DOES_NOT_EXIST Specified FC port does not exist Listing FC Ports Lists the status and configuration of the system's FC ports. fc_port_list [ module=ModuleNumber | fcport=ComponentId ] Parameters: Name Description...
  • Page 402 Original Model Requires Service requires_ service service_reason Service Reason port_up_cnt Port Up loss_sync_cnt Loss Sync Loss Signal loss_signal_ PER_cnt BER_cnt Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed IBM XIV Storage System User Manual...
  • Page 403: Resetting Fc Ports

    User Category Permission Security administrator Disallowed Read-only users Allowed Technicians Allowed Resetting FC Ports Resets an FC port. fc_port_reset fc_port=ComponentId fc_port_reset fc_port=ComponentId [ firmware_reset=<yes|no> ] Parameters: Name Type Description Mandatory Default fc_port FC port identifier. Boolean Performs a firmware reset firmware_ (resets all ports on reset...
  • Page 404 This command shows the connectivity status between a XIV port and a defined host. The output can be limited to a specific port, module or XIV port. Hosts can attach to the FC and iSCSI either directly (point-to-point), via an FC fabric or via a Gigabit Ethernet switch.
  • Page 405 User Category Permission Technicians Allowed Chapter 19. Fibre Channel and iSCSI Configuration and Status...
  • Page 406 IBM XIV Storage System User Manual...
  • Page 407: Chapter 20. Hardware Maintenance

    Chapter 20. Hardware Maintenance The following sections describe the XIV Command Line Interface (XCLI) for maintaining hardware components. The sections are listed as follows: ats_list(List information about ATS components) cf_list(Lists the CFs in the XIV system.) component_list(Lists system components and their status.) component_phaseout(Phases out a component.)
  • Page 408: Listing Ats Configuration

    Traces Snapshots on a module.) technician_work_in_progress(Notifies the system of a technician at work.) xiv_support_enable(Enables XIV support access for a specific period of time limiting access from the specific address.) xiv_support_disable(Disables XIV support access) xiv_support_show(Shows XIV support window)
  • Page 409 Component ID Status Currently Functioning Model L1 Input OK L2 Input OK -------------- -------- ----------------------- --------- ------------- ------------- 1:ATS:1 ATS-60A Cont.: Outlet 1 State Outlet 2 State Outlet 3 State Firmware Version ---------------- ---------------- ---------------- ------------------ Cont.: 3-Phase Dual Active --------- ------------- Name Default Position...
  • Page 410 RMS Current Outlet P1 rms_current_p2 RMS Current Outlet P2 rms_current_p3 RMS Current Outlet P3 Firmware J1 Version firmware_l1_ version Firmware J2 Version firmware_l2_ version Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed IBM XIV Storage System User Manual...
  • Page 411: Listing Cfs In The System

    Limits the listing to a All CFs in all modules. specific module. Lists only a specific cf. A specific CF. This command lists the CFs in the XIV system. Example: cf_list -f all Output: Component ID Status Currently Functioning...
  • Page 412: Listing System Components

    The output is a list of components, with the following information for each component: v Component identification v Component general status v Indication about whether the component is currently functioning IBM XIV Storage System User Manual...
  • Page 413: Phasing Out A Component

    Name Default Position component_id Component ID status Status Currently Functioning currently_ functioning Requires Service requires_ service service_reason Service Reason Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed Phasing Out a Component...
  • Page 414 Operation not allowed in current status of a subcomponent. v CONTROLLING_SERVICES_NOT_ALLOWED_FOR_USER_CATEGORY Controlling services not allowed for user category v NOT_ALL_PSUS_OK There is one or more PSUs disconnected or failed, this may cause the requested action to cause module failures IBM XIV Storage System User Manual...
  • Page 415: Phasing In A Component

    Troubleshooting: Check that all PSUs are properly wired, and ensure that none is failed v SYSTEM_UPGRADE_CANCELED_BECAUSE_OF_NODE_FAILURE_ DURING_UPGRADE Last upgrade was canceled because a node failed while the upgrade process was running v FAILED_NOT_SUPPORTED_FOR_THIS_COMPONENT_TYPE This component type cannot be failed v HOT_UPGRADE_IS_NOT_ONGOING Hot upgrade is not currently ongoing v FIRMWARE_UPGRADE_IN_PROGRESS Firmware upgrade in progress...
  • Page 416 FIRMWARE_UPGRADE_IN_PROGRESS Firmware upgrade in progress Troubleshooting: Contact support v CANNOT_WRITE_TO_KEY_REPOSITORY Failed writing keys to the key repository. Troubleshooting: Contact support. v NO_LIVE_KEYSERVER_GATEWAY_NODE There is no live key server gateway node on the system. IBM XIV Storage System User Manual...
  • Page 417: Testing A Component

    Component ID. This command instructs the XIV system to test the component. The command is used after a failed component is replaced. Components must be in a Failed status. Upon a successful test, the component changes to Ready status. Upon a failed test, the component remains in a Failed state.
  • Page 418: Setting A Component As Equipped

    This command configures the system to start using the component, assuming that it was assembled. The component is tested by the system. After completing the test, the component is marked as either Ready or Failed. IBM XIV Storage System User Manual...
  • Page 419 Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Warnings: v ARE_YOU_SURE_YOU_WANT_TO_HARD_RESET_MODULE Are you sure you want to hard reset the module? Completion Codes: v COMPONENT_DOES_NOT_EXIST Component does not exist v DISK_IS_NOT_FUNCTIONING Disk is not functioning.
  • Page 420: Listing System Components Requiring Service

    Component identification v Component general status v Indication about whether the component is currently functioning Name Default Position component_id Component ID status Status Currently Functioning currently_ functioning Requires Service requires_ service service_reason Service Reason IBM XIV Storage System User Manual...
  • Page 421: Forces The Service Required Of A Component To Ok

    Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed Forces the Service Required of a Component to OK Forces the service required of a component to be OK. component_service_force_ok component=ComponentId Parameters: Name...
  • Page 422 -u -c XIV1 component_firmware_upgrade firmware_type=USM scope=1:Module:3 Output: Command completed successfully. Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed IBM XIV Storage System User Manual...
  • Page 423: Aborting A Firmware Upgrade

    Completion Codes: v FIRMWARE_UPGRADE_IN_PROGRESS Firmware upgrade in progress Troubleshooting: Contact support v FIRMWARE_UPGRADE_UPS_CALIBRATING Firmware upgrade cannot start while a UPS is calibrating v MODULE_IS_NOT_OK Module status is not OK v FIRMWARE_UPGRADE_INVALID_LABEL Firmware upgrade label invalid v FIRMWARE_UPGRADE_NO_MATCHING_COMPONENTS Firmware upgrade did not find any matching components v FIRMWARE_UPGRADE_REQUIRES_ON_STATE Firmware upgrade only allowed in ON state v FIRMWARE_UPGRADE_INVALID_SCOPE...
  • Page 424: Status Of A Firmware Upgrade Process

    Number of components which failed upgrade. v num_noops: Number of components which did not perform an upgrade operation (usually because they were already at the correct firmware level). Name Default Position name Name IBM XIV Storage System User Manual...
  • Page 425: Per-Component Progress Of A Firmware Upgrade Process

    Name Default Position value Value Example: xcli -u -c XIV1 component_firmware_upgrade_status Output: Name Value ------------------ ------------ last_process_start 2012-11-08 12:30:46 last_process_end in_progress abort abort_reason firmware_type disk upgrade_type scope 1:Module:3 label PREFERRED current_timeout current_cooldown num_succeeded num_failed num_noops Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator...
  • Page 426: Listing Infiniband Hca Adapters In The System

    Limits the listing to a All InfiniBand HCA specific module. adapters in all modules. Lists only a specific A specific InfiniBand HCA. HCA. This command lists the InfiniBand HCA adapters in the XIV system. Example: IBM XIV Storage System User Manual...
  • Page 427 hca_list Output: Component ID Status Currently Functioning Board Description Board ID Part Number ------------- ------- ---------------------- ------------------ --------------- ----------- 1:HCA:10:1 FALCON DDR MT_0D80120008 MHRH29B-XTR 1:HCA:13:1 OWL DDR MT_0F90120008 MHRH2A-XTR 1:HCA:1:1 FALCON DDR MT_0D80120008 MHRH29B-XTR 1:HCA:4:1 FALCON DDR MT_0D80120008 MHRH29B-XTR 1:HCA:7:1 FALCON DDR MT_0D80120008 MHRH29B-XTR...
  • Page 428: Listing Cna Adapters In The System

    All CNA adapters in all specific module. modules. Lists only a specific A specific CNA. CNA. This command lists the CNA adapters in the XIV system. Example: cna_list Output: Component ID Status Currently Functioning Board Description Board ID Part Number...
  • Page 429: Listing Dimms In The System

    Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed Listing DIMMs in the System Lists the DIMMs in the XIV system. dimm_list [ module=ModuleNumber | dimm=ComponentId ] Chapter 20. Hardware Maintenance...
  • Page 430 Limits the listing to a All DIMMs in all specific module. modules. dimm Lists only a specific A specific DIMM. DIMM. This command lists the DIMMs in the XIV system. Example: dimm_list -f all Output: Component ID Status Currently Functioning Hardware Status...
  • Page 431: Listing Cpus In The System

    Description Mandatory Default module Limits the listing to a All CPUs in all specific module. modules. Lists only a specific A specific CPU. CPU. This command lists the CPUs in the XIV system. Example: cpu_list Output: Chapter 20. Hardware Maintenance...
  • Page 432 Current Speed(MHz) status_string Status manufacturer Manufacturer version Version model_string Model signature Signature core_count Cores core_enabled Enabled Cores thread_count Threads serial Serial Original Serial original_ serial part_number Part # Original Part Number original_part_ number IBM XIV Storage System User Manual...
  • Page 433: Listing Maintenancemodules In The System

    Lists the MaintenanceModules in the XIV system. mm_list [ mm=ComponentId ] Parameters: Name Description Mandatory Default Lists only a specific A specific mm. This command lists the MaintenanceModules in the XIV system. Example: mm_list -f all Output: Chapter 20. Hardware Maintenance...
  • Page 434 Original Part Number original_part_ number total_memory Total Memory free_memory Free Memory free_disk_root Free disk (/) free_disk_var Free disk (/var) link_1 Link#1 link_2 Link#2 Requires Service requires_ service service_reason Service Reason Last Heartbeat Time last_ heartbeat_time IBM XIV Storage System User Manual...
  • Page 435: Listing Nics In The System

    Default module Limits the listing to a All nics in all modules. specific module. Lists only a specific A specific NIC. NIC. This command lists the NICs in the XIV system. Example: nic_list -f all Output: Chapter 20. Hardware Maintenance...
  • Page 436 Status Currently Functioning currently_ functioning Hardware Status hardware_ status device_name Device Name serial Serial Original Serial original_ serial part_number Part # Original Part Number original_part_ number Requires Service requires_ service service_reason Service Reason IBM XIV Storage System User Manual...
  • Page 437: Listing Modules Internal Temperatures

    Description Mandatory Default module Limits the listing to a All temperatures in all specific module. modules. This command lists the modules' internal temperatures in the XIV system. Example: module_temperature_list -f all Output: root@nextra-6002207-module-1:~# xcli.py module_temperature_list Module Normalized Ambient Raw Ambient...
  • Page 438 DIMM 2 ses_ temperatures.7 DIMM 3 ses_ temperatures.8 DIMM 4 ses_ temperatures.9 DIMM 5 ses_ temperatures.1 DIMM 6 ses_ temperatures.1 DIMM 7 ses_ temperatures.1 DIMM 8 ses_ temperatures.1 DIMM 9 ses_ temperatures.1 IBM XIV Storage System User Manual...
  • Page 439 Name Default Position DIMM 10 ses_ temperatures.1 DIMM 11 ses_ temperatures.1 DIMM 12 ses_ temperatures.1 PCIe ses_ temperatures.1 InfiniBand HCA ib_hca_ temperature cna_ temperature SAS Controller sas_ controller_ temperature Fibre Channel Port fc-0 fc_adapter_ temperature.0 Fibre Channel Port fc-1 fc_adapter_ temperature.1 Fibre Channel Port fc-2 fc_adapter_...
  • Page 440: Monitoring Rebuild Or Redistribution Processes

    Time Started Estimated Time to Finish estimated_ time_to_finish time_elapsed Time Elapsed Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed IBM XIV Storage System User Manual...
  • Page 441: Listing Disk Status

    Listing Disk Status Lists special disk statuses. disk_list [ module=ModuleNumber | disk=ComponentId ] Parameters: Name Description Mandatory Default module Limits the listing to a All disks in all modules. specific module. disk Disk for which special All disks. statuses are to be listed. This command lists the statuses of the disk, including the following: v Component generic status v Disk capacity...
  • Page 442 Power On Minutes desc.power_on_ minutes Last Time Power On Minutes Was Modified desc.last_ time_pom_was_ desc.read_fail Read Fail SMART Code desc.smart_ code SMART Fail desc.smart_ fail Reported Temperature Severity desc.temperatu status.reporte d_severity Reported Temperature desc.temperatu status.reporte d_temperature IBM XIV Storage System User Manual...
  • Page 443: Listing Module Configuration

    Name Default Position Disk Temperature desc.temperatu status.tempera ture security_state Security State Last Security State security_ state_last Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed Listing Module Configuration Lists the configuration of all or of the specified modules.
  • Page 444 Fan Controller fan_ controller_ firmware Battery Firmware battery_ firmware sas_version InfiniBand HCA infiniband_ hca_version cna_version Requires Service requires_ service service_reason Service Reason memory_gb temperature SES Temperature chassis_serial Chassis Serial Chassis Part Number chassis_part_ number IBM XIV Storage System User Manual...
  • Page 445: Reset Ethernet Interface

    Name Default Position Electronics Serial electronics_ serial Electronics Part Number electronics_ part_number Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed Reset Ethernet Interface Reset ethernet interface ethernet_interface_reset interface=ComponentId Parameters: Name...
  • Page 446: Check Modules Serial Connections

    List serial consoles serial_consoles_list [ monitoring_module_id=ComponentId ] Parameters: Name Description Mandatory Default List the status only for All modules the specified module monitoring _module_id List serial consoles Example: xcli -u -c XIV1 serial_consoles_list Output: IBM XIV Storage System User Manual...
  • Page 447: Listing Ups Component Statuses

    Monitoring Module Desired Module Connected Module Status Is Module Alive ------------------- ---------------- ------------------ ---------------- ----------------- 1:Module:1 1:Module:3 1:Module:3 GOOD 1:Module:15 1:Module:14 1:Module:14 GOOD 1:Module:2 1:Module:1 1:Module:1 GOOD 1:Module:3 1:Module:2 1:Module:2 NO_SERIAL_DATA 1:Module:4 1:Module:6 1:Module:6 GOOD 1:Module:6 1:Module:5 1:Module:5 MODULE_FAILED 1:Module:7 1:Module:9 1:Module:9 GOOD...
  • Page 448 Self-test Status v Component Test Status v Batteries Date v UPS Manufacture Date v Cable check result Name Default Position component_id Component ID status Status Currently Functioning currently_ functioning input_power_on Input Power On IBM XIV Storage System User Manual...
  • Page 449 Name Default Position Runtime Remaining runtime_ remaining Battery Charge Level battery_ charge_level Last Self Test Date last_self_ test_date Last Self Test Result last_self_ test_result is_enabled Monitoring Enabled ups_status UPS Status Last Calibration Date last_ calibration_ date Last Calibration Result last_ calibration_ result serial...
  • Page 450: Listing Service Status

    User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed Listing Service Status Lists all the service specific statuses. service_list [ service=ComponentId ] IBM XIV Storage System User Manual...
  • Page 451: Listing Psus In The System

    Limits the listing to a All PSUs in all modules. specific module. Lists only a specific A specific PSU. PSU. This command lists the PSUs in the XIV system. Example: xcli -u -c Nextra1 psu_list Output: Chapter 20. Hardware Maintenance...
  • Page 452 Voltage (12V) voltage_5v Voltage (5V) current Current power Power fru_descriptor FRU descriptor Original FRU descriptor original_fru_ descriptor Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed IBM XIV Storage System User Manual...
  • Page 453: Resetting A Failed Command Service

    User Category Permission Read-only users Allowed Technicians Allowed Resetting a Failed Command Service. Resets a specified command service on a specified module. reset_command_service service=ServiceName module=ModuleNumber Parameters: Name Type Description Mandatory module Target module on which a failed service will be reset.
  • Page 454: Stopping System Traces

    Stopped Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Resuming System Traces Resumes system traces. traces_resume Resumes system traces. IBM XIV Storage System User Manual...
  • Page 455: Listing Status Of System Traces

    Name Default Position module Module status Status Example: xcli -u -c Nextra1 traces_resume Output: Module Status ------------- --------- 1:Module:1 Running 1:Module:2 Running 1:Module:3 Running 1:Module:4 Running 1:Module:5 Running 1:Module:6 Running 1:Module:7 Running 1:Module:8 Running 1:Module:9 Running 1:Module:10 Running 1:Module:11 Running 1:Module:12 Running 1:Module:13...
  • Page 456: Create Traces Snapshot

    Integer Time back from request time to Uses configuration snapshot_ include in the misc.internal.auto_ back_time snapshot. snapshot_ trace.snapshot_ back_time field. Create traces snapshot Example: IBM XIV Storage System User Manual...
  • Page 457: Lists Traces Snapshots On A Module

    xcli.py traces_snapshot snapshot_back_time=60 snapshot_delay_time=1 Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Lists Traces Snapshots on a Module. Lists Traces Snapshots on a module. traces_snapshot_list module=ModuleNumber Parameters: Name Description...
  • Page 458: Notifying The System Of A Technician At Work

    Notifies the system of a technician at work. Example: xcli -u -c XIV1 technician_work_in_progress comment="We are starting to replace module" mode=start timeout=1:30 Output: Command executed successfully. IBM XIV Storage System User Manual...
  • Page 459: Enables Xiv Support Access

    TECHNICIAN_WORK_COMMENT_NOT_SPECIFIED Comment must be specified when technician work starts. Enables XIV Support Access Enables XIV support access for a specific period of time limiting access from the specific address. xiv_support_enable [ start=TimeStamp ] < finish=TimeStamp | timeout=Timeout > from=IPaddress comment=Comment...
  • Page 460 String Reason why XIV support access is enabled. Enables XIV support access for a specific period of time limiting access from the specific address. Example: xcli -u -c XIV1 xiv_support_enable finish=2012-2-3.16:30 from=1.2.3.4 comment="Some reason" Output: Command executed successfully.
  • Page 461: Disables Xiv Support Access

    Disables XIV Support Access Disables XIV support access xiv_support_disable Disables XIV support acess Example: xcli -u -c XIV1 xiv_support_disable Output: Command executed successfully. Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator...
  • Page 462: Cancel Ups Calibration

    Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Completion Codes: v UPS_IS_UNMONITORED The specified UPS is not monitored and commands cannot be run on it Troubleshooting: Contact support v COMPONENT_DOES_NOT_EXIST IBM XIV Storage System User Manual...
  • Page 463: Check Ups Monitor Cables

    Component does not exist v UPS_NOT_IN_CALIBRATION UPS calibration is not in calibration Troubleshooting: Contact support Check UPS Monitor Cables Check UPS monitor cables ups_check_monitor_cables ups=ComponentId Parameters: Name Description Mandatory The UPS to check its monitor cables Check UPS monitor cables Example: xcli -u -c XIV1 ups_check_monitor_cables ups Access Control:...
  • Page 464: Start Ups Calibration

    The battery serial number is identical to the other battery's serial number Troubleshooting: Retype serial or contact support Start UPS Calibration Start UPS calibration ups_start_calibration ups=ComponentId Parameters: Name Description Mandatory The UPS to start calibration on IBM XIV Storage System User Manual...
  • Page 465: Start Ups Self Test

    Start UPS calibration Example: xcli -u -c XIV1 ups_start_calibration ups Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Completion Codes: v UPS_IS_UNMONITORED The specified UPS is not monitored and commands cannot be run on it Troubleshooting: Contact support v COMPONENT_DOES_NOT_EXIST Component does not exist...
  • Page 466: Turn Ups Off

    The UPS to turn off Turn UPS off Example: xcli -u -c XIV1 ups_turn_off ups Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed IBM XIV Storage System User Manual...
  • Page 467: Listing Fans In The System

    User Category Permission Technicians Allowed Warnings: v ARE_YOU_SURE_YOU_WANT_TO_TURN_UPS_OFF Are you sure you want to turn the UPS output power off? Troubleshooting: Contact support Completion Codes: v UPS_IS_UNMONITORED The specified UPS is not monitored and commands cannot be run on it Troubleshooting: Contact support v UPS_NOT_ENOUGH_SPARES There are not enough spare UPS's in the rack to safely complete the command...
  • Page 468: Listing Ssds That Are Used As Flash Cache In The System

    Lists SSDs used as flash cache in the system. ssd_list [ ssd=ComponentId ] Parameters: Name Description Mandatory Default Drive for which status All SSDs. is requested Lists SSDs used as flash cache in the system. Example: xcli -u -c Nextra1 ssd_list Output: IBM XIV Storage System User Manual...
  • Page 469 Component ID Status Currently Functioning ------------- -------- ----------------------- 1:SSD:1:1 1:SSD:10:1 1:SSD:2:1 1:SSD:3:1 1:SSD:4:1 1:SSD:5:1 1:SSD:6:1 1:SSD:7:1 1:SSD:8:1 1:SSD:9:1 Name Default Position component_id Component ID status Status Currently Functioning currently_ functioning capacity Capacity target_status Target Status vendor Vendor model Model size Size serial Serial...
  • Page 470: Disabling The Ssd Caching Feature

    Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed Disabling the SSD Caching Feature Disables Flash Caching ssd_caching_disable This command disables the SSD Caching feature. IBM XIV Storage System User Manual...
  • Page 471: Enabling The Ssd Cache Feature

    Example: xcli -u -c XIV1 ssd_caching_disable Output: command executed successfully Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Allowed Completion Codes: v SSD_CACHING_NOT_ENABLED SSD Caching feature was not enabled. Enabling the SSD Cache Feature Enables SSD Caching ssd_caching_enable...
  • Page 472: Getting The Default State Of The Ssd Caching

    This default value can be overriden by the vol_ssd_caching_set command. Example: xcli -u -c XIV1 vol_default_ssd_caching_get Output: Command executed successfully Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed IBM XIV Storage System User Manual...
  • Page 473: Setting A Default State For Ssd Caching

    Completion Codes: v SSD_CACHING_NOT_ENABLED SSD Caching feature was not enabled. Setting a Default State for SSD Caching Sets a Default State for SSD Caching vol_default_ssd_caching_set default=<ENABLED|DISABLED|DEFAULT> Parameters: Name Type Description Mandatory default Enumeration The SSD Caching state that will be the default. This command sets a default value for SSD caching state.
  • Page 474: Shows System Average Power Consumption

    Are you sure you want to disable SSD caching for all volumes? Completion Codes: v VOLUME_BAD_NAME Volume name does not exist v VOLUME_IS_SNAPSHOT Operation is not permitted on snapshots Shows System Average Power Consumption Shows system average power consumption. system_average_power_consumption Shows system average power consumption IBM XIV Storage System User Manual...
  • Page 475: Shows System Average Temperature

    Example: xcli -u -c XIV1 system_average_power_consumption Output: TODO Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed Shows System Average Temperature Shows system average temperature. system_average_temperature Shows system average temperature Example: xcli -u -c XIV1 system_average_temperature...
  • Page 476 IBM XIV Storage System User Manual...
  • Page 477: Chapter 21. Statistics

    Chapter 21. Statistics The following sections describe the XIV Command Line Interface (XCLI) for getting system statistics. Other command that are relevant to this topic is: Obtaining Statistics On Past Sync Jobs The sections are listed as follows: statistics_get(Retrieves performance statistics from the XIV system.) usage_get(Shows the usage history of a volume or a Storage Pool.)
  • Page 478 M - month (1-12) v D - day (1-31) v h - hour (0-23, with 0 as default) v m - minute (0-59, with 0 as default) v s - second (0-59, with 0 as default) Note: IBM XIV Storage System User Manual...
  • Page 479 The year, month and day are separated by dashes, and the optional hours, minutes and seconds are separated by colons. Output units: v Very Large blocks - are >512KB v Large blocks - are 64-512KB v Medium blocks - are 8-64KB v Small blocks - are 0-8KB v The latency is in Microsecond v The bandwidth is in KB...
  • Page 480 Read Miss Small - IOps read_miss_ small_iops Read Miss Small - Latency read_miss_ small_latency Read Miss Small - Throughput read_miss_ small_ throughput Write Hit Very large - IOps write_hit_ very_large_ iops IBM XIV Storage System User Manual...
  • Page 481 Name Default Position Write Hit Very large - Latency write_hit_ very_large_ latency Write Hit Very large - Throughput write_hit_ very_large_ throughput Write Hit Large - IOps write_hit_ large_iops Write Hit Large - Latency write_hit_ large_latency Write Hit Large - Throughput write_hit_ large_ throughput...
  • Page 482 Read Memory-Hit Large - IOps read_memory_ hit_large_iops Read Memory-Hit Large - Latency read_memory_ hit_large_ latency Read Memory-Hit Large - Throughput read_memory_ hit_large_ throughput Read Memory-Hit Medium - IOps read_memory_ hit_medium_ iops IBM XIV Storage System User Manual...
  • Page 483 Name Default Position Read Memory-Hit Medium - Latency read_memory_ hit_medium_ latency Read Memory-Hit Medium - Throughput read_memory_ hit_medium_ throughput Read Memory-Hit Small - IOps read_memory_ hit_small_iops Read Memory-Hit Small - Latency read_memory_ hit_small_ latency Read Memory-Hit Small - Throughput read_memory_ hit_small_ throughput Time (s)
  • Page 484: Retrieving History Usage

    12:00:00 AM, 1 January 1970. This command retrieves the usage history of a Storage Pool or volume, in units of one megabyte. Name Default Position time Time volume_usage Volume Usage (MiB) snapshot_usage Snapshot Usage (MiB) IBM XIV Storage System User Manual...
  • Page 485 Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Disallowed Read-only users Disallowed Technicians Disallowed Completion Codes: v VOLUME_BAD_NAME Volume name does not exist v POOL_DOES_NOT_EXIST Storage Pool does not exist v BAD_TIME_FORMAT Bad time format.
  • Page 486 IBM XIV Storage System User Manual...
  • Page 487: Chapter 22. Meta-Data

    Chapter 22. Meta-data The following sections describe the XIV Command Line Interface (XCLI) for meta-data handling. The sections are listed as follows: metadata_set(Sets a meta-data of an object.) metadata_delete(Deletes a meta-data of an object.) metadata_list(Lists a meta-data of an object.) Setting Meta Data Sets a meta-data of an object.
  • Page 488: Deleting Meta Data

    Object name Name of object String Metadata key. Access Control: User Category Permission Condition Storage administrator Allowed Storage integration administrator Allowed IBM XIV Storage System User Manual...
  • Page 489: Listing Meta Data

    User Category Permission Condition Application administrator Conditionally Allowed Metadata can be set for only volumes, snapshots, snapshot groups, clusters or hosts, and only for objects associated with the application administrator executing the command. Hosts or clusters should be associated with the user. Volumes should be mapped to a host or a cluster associated with the user.
  • Page 490 Name Default Position value Value Access Control: User Category Permission Storage administrator Allowed Storage integration administrator Allowed Application administrator Allowed Security administrator Disallowed Read-only users Allowed Technicians Allowed IBM XIV Storage System User Manual...
  • Page 491: Chapter 23. Encryption Enablement And Support Commands

    Chapter 23. Encryption enablement and support commands The following sections describe the XIV Command Line Interface (XCLI) for encryption configuration. The sections are listed as follows: encrypt_disable(Disable the data protection feature) encrypt_enable(Enable the data protection feature) encrypt_keyserver_define(Defines a keyserver to be used by the system)
  • Page 492 Troubleshooting: Please restart the key server gateway node and retry. v NO_MASTER_KEYSERVER_DEFINED There is no master key server defined on the system. Troubleshooting: Please define a master key server by invoking encrypt_key server_update and retry. v KEYSERVER_COMMUNICATION_GENERIC_ERROR IBM XIV Storage System User Manual...
  • Page 493: Enabling Encryption

    Cannot connect to an active key server. Troubleshooting: Invoke encrypt_key server_list and event_list for more details. Enabling Encryption Enable the data protection feature encrypt_enable [ recovery_keys=<yes|no> ] Parameters: Name Type Description Mandatory Default Boolean Are recovery keys required for recovery_ encryption keys activation...
  • Page 494: Define A Keyserver

    Boolean Is this keyserver the primary keyserver used for key retrieval ipv4 The IPv4 address NONE of the keyserver being added. Either one IPv4 and/or one IPv6 must be used IBM XIV Storage System User Manual...
  • Page 495 At least one keservers (but preferably two, and a maximum of four) must be defined and accessible in order for encrypt_enable to succeed. Only one of the keyservers may be defined as master. Example: xcli -u -c XIV1 encrypt_keyserver_define name=snocone ipv4=snocone.ibm.com ipv6=2002::a5a7 certificate=’’ Output: Command executed successfully.
  • Page 496: Remove Keyserver

    Storage integration administrator Disallowed Application administrator Disallowed Security administrator Allowed Read-only users Disallowed Technicians Disallowed Completion Codes: v UNSUPPORTED_HARDWARE Cannot utilize encryption on unsupported hardware. Troubleshooting: Contact support to verify encryption status. v ENCRYPTION_UNKNOWN_KEYSERVER IBM XIV Storage System User Manual...
  • Page 497: Display Keyserver Status

    UNKNOWN 2013/03/27 20:18:43 no 5696 snocone ACTIVE ACTIVE 2013/03/27 20:18:43 no 5696 TKLM-SA FAILED BAD_CERT 2013/03/27 20:18:43 no 5696 Address ------- 9.11.236.1 2002::1 snocone.tucson.ibm.com 2002:90b:e006:238:209:6bff:fe00:a5a7 tklm-sa.ibm.com Name Default Position module_id Module label Name Chapter 23. Encryption enablement and support commands...
  • Page 498: Obtain New Master Key

    This command initiates a rekeying(getting new cryptographic material) with the master keyserver. Example: xcli -u -c XIV1 encrypt_keyserver_rekey Output: Command executed successfully. Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed IBM XIV Storage System User Manual...
  • Page 499 Encryption is not enabled. Troubleshooting: Check that encryption is enabled and retry the command. v CANNOT_GET_XIV_MASTER_KEY Problem obtaining XIV master key from the key server. Troubleshooting: Check that the key server is active and serving keys, and contact support. v CANNOT_GET_NEW_KEY_REQUEST Error requesting encryption keys from the key server gateway node.
  • Page 500: Rename Keyserver

    Troubleshooting: Contact support to verify encryption status. v ENCRYPTION_UNKNOWN_KEYSERVER Unknown key server name. Troubleshooting: Check the currently defined key servers v ENCRYPTION_KEYSERVER_NAME_EXISTS Key server name already exists. Troubleshooting: Check the currently defined key servers IBM XIV Storage System User Manual...
  • Page 501: Change Keyserver Properties

    Change Keyserver Properties Change a keyserver ip address and/or port encrypt_keyserver_update name=Name [ ipv4=Address ] [ ipv6=Address ] [ port=PortNumber ] [ master=<yes|no> ] [ certificate=PemCertificate ] Parameters: Name Type Description Mandatory Default name String Name of the keyserver to update The public none...
  • Page 502: Recovery Key Enter

    "On" state, it has no effect, and can be used to check the validity of the recovery key. Example: xcli -u -c XIV1 encrypt_recovery_key_enter key=CBC9B398373FDE79CD38B23192DABACADB5DA63A915CB F5CA8C4E0C212819DE6 Output: Command executed successfully. Access Control: User Category Permission Storage administrator Disallowed Storage integration administrator Disallowed Application administrator Disallowed Security administrator Allowed IBM XIV Storage System User Manual...
  • Page 503: Recovery Key Generation

    User Category Permission Read-only users Disallowed Technicians Disallowed Completion Codes: v UNSUPPORTED_HARDWARE Cannot utilize encryption on unsupported hardware. Troubleshooting: Contact support to verify encryption status. v INVALID_RECOVERY_KEY_FRAGMENT Recovery key fragment given does not match stored key. Troubleshooting: Verify that the proper key(share) has been used v GENERIC_FAILED Generic encryption failure.
  • Page 504 Disallowed Technicians Disallowed Completion Codes: v UNSUPPORTED_HARDWARE Cannot utilize encryption on unsupported hardware. Troubleshooting: Contact support to verify the encryption status. v NO_LIVE_KEYSERVER_GATEWAY_NODE There is no live key server gateway node on the system. IBM XIV Storage System User Manual...
  • Page 505: Retrieve The Security Admin Recovery Key

    Troubleshooting: Please restart the key server gateway node and retry. v CANNOT_WRITE_TO_KEY_REPOSITORY Failed writing keys to the key repository. Troubleshooting: Contact support. v CANNOT_GET_NEW_KEY_REQUEST Error requesting encryption keys from the key server gateway node. Troubleshooting: Check that the key server is actively serving keys v KEYSERVER_COMMUNICATION_GENERIC_ERROR Cannot connect to an active key server.
  • Page 506 Once this is done successfully, encrypt_recovery_key_get will no longer present the users key. Using encrypt_recovery_key_get more than once will return the same value again. Example: xcli -u secadmin1 -p password -c XIV encrypt_recovery_key_get Output: Command executed successfully. key=B07C4374AC26C4DD3EC2E755EB3FAAF04EC792C8BE0D0CB1C1BAC79998EBEC6D Access Control:...
  • Page 507: Rekey The Security Admins

    Troubleshooting: Please define a master key server by invoking encrypt_key server_update and retry. v INVALID_RECOVERY_KEY_STATE Recovery key state is inconsistent with the option provided. Troubleshooting: Check the recovery key state using encrypt_recovery_key_list. v RECOVERY_KEY_ALREADY_VERIFIED The recovery key has already been verified. Troubleshooting: Check the recovery key state using encrypt_recovery_key_list Rekey the Security Admins Restarts the recovery key generation process as described in...
  • Page 508: Recovery Key Status

    This command shows status information regarding recovery keys, specifically: Before encrypt_enable or in the recovery key rekey process, which user has verified his recovery key When using the recovery key to unlock the disks, which user has IBM XIV Storage System User Manual...
  • Page 509 entered his recovery key. Information about how many shares have been defined and the minimum number required for recovery is available via encrypt_recovery_key_list. Example: xcli -u secadmin1 -p password -c XIV1 encrypt_recovery_key_status Output: Mon Aug 12 20:04:43 IDT 2013 Date Created User Status 2013-01-03 18:54:46...
  • Page 510: Recovery Key Verification

    Troubleshooting: Contact support to verify encryption status. v INVALID_RECOVERY_KEY_FRAGMENT Recovery key fragment given does not match stored key. Troubleshooting: Verify that the proper key(share) has been used v GENERIC_FAILED Generic encryption failure. Troubleshooting: Contact support. v INVALID_RECOVERY_KEY_USER IBM XIV Storage System User Manual...
  • Page 511: Recovery Key Share Information

    User is not a valid recovery key administrator. Troubleshooting: Check that the user names provided are valid v CANNOT_READ_FROM_KEY_REPOSITORY Failed reading keys from the key repository. Troubleshooting: Contact support. v RK_FAILED_VERIFY_SLEEP Too many failed verify attempts, please wait and try again. Troubleshooting: Wait a little and retry.
  • Page 512 Read-only users Allowed Technicians Allowed Completion Codes: v UNSUPPORTED_HARDWARE Cannot utilize encryption on unsupported hardware. Troubleshooting: Contact support to verify encryption status. v CANNOT_READ_FROM_KEY_REPOSITORY Failed reading keys from the key repository. Troubleshooting: Contact support. IBM XIV Storage System User Manual...
  • Page 513: Chapter 24. Events

    Chapter 24. Events VOLUME_CREATE Severity informational Description Volume was created with name 'volume.name' and size volume.sizeGB in Storage Pool with name 'volume.pool_name'. VOLUME_CREATE_FAILED_TOO_MANY Severity warning Description Volume with name 'name' could not be created. You are attempting to add more volumes than the system permits.
  • Page 514 Volume with name 'volume.name'. VOLUME_SET_SSD_CACHING Severity informational Description SSD Caching was set to be 'state' for Volume with name 'volume.name'. VOLUME_SET_ALL_SSD_CACHING Severity informational Description SSD Caching was set to be 'state' for all currently defined Volumes. IBM XIV Storage System User Manual...
  • Page 515 VOLUME_SET_DEFAULT_SSD_CACHING Severity informational Description Default SSD Caching for volumes was set to be 'state'. DATA_REBUILD_STARTED Severity informational Description Rebuild process started because system data is not protected. data_percent% of the data must be rebuilt. DATA_REBUILD_COMPLETED Severity informational Description Rebuild process completed. System data is now protected.
  • Page 516 Severity variable Description Usage by snapshots of Storage Pool with name 'pool.name' has reached current%. Troubleshooting STORAGE_POOL_SNAPSHOT_USAGE_DECREASED Severity informational Description Usage by snapshots of Storage Pool with name 'pool.name' has decreased to current%. Troubleshooting IBM XIV Storage System User Manual...
  • Page 517 HOST_CONNECTED Severity informational Description Host 'host' has connected to the system. Troubleshooting HOST_DISCONNECTED Severity informational Description Host 'host' has disconnected from the system. Troubleshooting HOST_MULTIPATH_OK Severity informational Description Host 'host' has redundant connections to the system. #paths=npaths Troubleshooting HOST_NO_MULTIPATH_ONLY_ONE_PORT Severity informational Description Host 'host' is connected to the system through...
  • Page 518 POOL_RESIZE_SNAPSHOTS Severity informational Description Snapshot size of Storage Pool with name 'pool.name' was resized from size old_sizeGB to pool.snapshot_sizeGB. POOL_CHANGE_LOCK_BEHAVIOR Severity informational Description Lock Behavior of Storage Pool with name 'pool.name' is now 'state'. IBM XIV Storage System User Manual...
  • Page 519 POOL_CONFIG_SNAPSHOTS Severity informational Description Management policy of Mirroring snapshots of Storage Pool with name 'pool.name' has changed'. POOL_DELETE Severity informational Description Storage Pool with name 'pool.name' was deleted. COMMAND_SERVICE_FAILED_TOO_MANY_TIMES Severity major Description Command service service name was restarted times times within seconds seconds on module module Troubleshooting Please contact support.
  • Page 520 Downloaded total of Number of files files. Status: Status MODULE_DOWNLOAD_TIMEOUT Severity warning Description Timeout expired trying to download current version of the system to module Module ID using interface Interface. Troubleshooting Please contact support. IBM XIV Storage System User Manual...
  • Page 521 MODULE_DOWNLOAD_VERSION_TIMEOUT Severity warning Description Timeout expired trying to download current version of the system to module Module ID. Troubleshooting Please contact support. ERROR_SETTING_UP_INTERFACE Severity major Description Error attempting setup Ethernet interface Interface name on module Module ID Troubleshooting Possible physical problem with Ethernet card. Contact support MODULE_CPU_HAS_LESS_CORES_THAN_EXPECTED Severity...
  • Page 522 Severity warning Description Grace period expired, but there are still not enough disks for boidem RAID on module module. BOIDEM_HAS_ENOUGH_DISKS Severity warning Description There are now enough disks for boidem RAID on module module. IBM XIV Storage System User Manual...
  • Page 523 BOIDEM_MISSING_MOUNT_POINT Severity warning Description Boidem is missing a mount point at Missing mount point on module module. BOIDEM_FS_IS_RO Severity warning Description Boidem mount point Read-only mount point is in a read-only state on module module. BOIDEM_DISK_UNRESPONSIVE Severity warning Description Disk Disk ID is unresponsive for time ms BOIDEM_DISK_RESPONSIVE Severity warning...
  • Page 524 Schedule of remote mirror of 'local peer name' is now 'schedule name'. MIRROR_CREATE_FAILED_TARGET_NOT_CONNECTED Severity warning Description Target could not be reached. Target with name 'target.name' is currently not connected. Troubleshooting Connect the target system to this system. IBM XIV Storage System User Manual...
  • Page 525 REMOTE_OPERATION_FAILED_TIMED_OUT Severity warning Description Operation on remote machine timed out. Invoking 'Function Name' on target 'Target Name' timed out. Troubleshooting Retry operation. If problem persists contact support. MIRROR_RESYNC_FAILED Severity major Description Synchronization of meta data with mirror failed. Configuration of remote mirror of volume 'local volume name' on target 'target name' does not match local configuration.
  • Page 526 MIRROR_DEACTIVATE_CONFIGURATION_ERROR Severity minor Description The Remote Mirror of peer 'local peer name' on Target 'target name' was deactivated since the Mirror configuration on the slave machine has changed. MIRROR_DELETE Severity informational IBM XIV Storage System User Manual...
  • Page 527 Description The Remote Mirror relation of peer 'local peer name' to a peer on Target 'target name' was deleted. MIRROR_REVERSE_ROLE_TO_SLAVE Severity informational Description Local peer 'local peer name' is now Slave of a peer on Target 'target name'. MIRROR_REVERSE_ROLE_TO_MASTER Severity informational Description Local peer 'local peer name' is now Master of a peer...
  • Page 528 Target 'target name' has started. DM_SYNC_ENDED Severity informational Description Migration to volume 'local volume name' from target 'target name' is complete. DM_ACTIVATE Severity informational Description Migration to Volume 'local volume name' from Target 'target name' was activated. IBM XIV Storage System User Manual...
  • Page 529 DM_DEACTIVATE Severity informational Description Migration to Volume 'local volume name' from Target 'target name' was deactivated. DM_DEACTIVATE_LUN_UNAVAILABLE Severity minor Description Migration to Volume 'local volume name' from Target 'target name' was deactivated since LUN is not available on one of the active paths to the target.
  • Page 530 MAP_VOLUME Severity informational Description Volume with name 'volume.name' was mapped to LUN 'LUN' for host_or_cluster with name 'host'. UNMAP_VOLUME Severity informational Description Volume with name 'volume.name' was unmapped from host_or_cluster with name 'host'. IBM XIV Storage System User Manual...
  • Page 531 CLUSTER_DEFINE_EXCEPTION Severity informational Description LUN 'LUN' was defined as having host specific mapping in cluster 'cluster'. CLUSTER_CANCEL_EXCEPTION Severity informational Description LUN 'LUN' was defined as having uniform mapping in cluster 'cluster'. SPECIAL_TYPE_SET Severity informational Description Type of host_or_cluster with name 'host' was set to 'type'.
  • Page 532 Module Component ID is not up. Troubleshooting Please contact support SINGLETON_NODE_IS_NOT_UP Severity minor Description No singleton of type Node Type is up. Troubleshooting Please contact support DISK_HAS_FAILED Severity variable Description Disk Component ID Failed. Troubleshooting Please contact your Administrator. IBM XIV Storage System User Manual...
  • Page 533 SSD_HAS_FAILED Severity major Description SSD Component ID Failed. Troubleshooting Please contact your Administrator. DISK_INFO_EXTRA_EVENT Severity informational Description Disk Component ID extra information event. Troubleshooting SSD_INFO_EXTRA_EVENT Severity informational Description SSD Component ID extra information event. Troubleshooting COMPONENT_TEST_OF_DISK_HAS_FAILED Severity major Description Test of Component ID has failed with error Error. Troubleshooting Please contact your Administrator.
  • Page 534 Disk Component ID is functioning again. Troubleshooting MODULE_STARTED_PHASEOUT Severity informational Description System started phasing out Component ID. Troubleshooting MODULE_INFO_PRE_EVENT Severity informational Description Component ID information pre event. Troubleshooting MODULE_FINISHED_PHASEOUT Severity informational Description System finished phasing out Component ID. Troubleshooting IBM XIV Storage System User Manual...
  • Page 535 MODULE_STOPPED_PHASEOUT_DUE_TO_MANAGEMENT_ REQUIREMENT Severity major Description System stopped phasing out Component ID due to management requirement. Troubleshooting MODULE_PHASEOUT_FAILURE_REASON Severity informational Description System could not phaseout Component ID due to lack of nodes of type Node Type. Troubleshooting START_WORK Severity informational Description System has entered ON state.
  • Page 536 Capacity GB should be freed. SYSTEM_SOFT_CAPACITY_CHANGED Severity informational Description System's soft capacity is now Capacity GB. MODULE_IS_MISSING_DATA_DISKS Severity major Description Module ID has Num Found of Num Expected data disks. IBM XIV Storage System User Manual...
  • Page 537 SERVICE_WAS_RESTARTED Severity informational Description Module ID was restarted. DATA_SERVICE_STARTED_PHASEOUT Severity informational Description System started phasing out Component ID. Troubleshooting DATA_SERVICE_FINISHED_PHASEOUT Severity informational Description System finished phasing out Component ID. Troubleshooting POWER_SUPPLY_UNIT_STATUS_IS_OK Severity informational Description The status of Component ID is now OK. Troubleshooting Please contact support.
  • Page 538 SSD Component ID of model SSD model, by vendor SSD vendor, User message Required model SSD_CACHING_ENABLED Severity informational Description SSD Caching feature enabled. SSDs can now be installed. Troubleshooting SSD_CACHING_DISABLED Severity informational Description SSD Caching feature disabled. Troubleshooting IBM XIV Storage System User Manual...
  • Page 539 FLASH_CACHE_ENABLE Severity informational Description Flash Cache feature enabled. SSDs can now be installed. Troubleshooting FLASH_CACHE_DISABLE Severity informational Description Flash Cache feature disabled. Troubleshooting CF_FAILED Severity major Description Component ID has failed. Hardware status: Status. Troubleshooting Please contact support. DIMM_FAILED Severity major Description Component ID has failed.
  • Page 540 Adapter Module serial number changed from old_serial to new_serial. Troubleshooting Was this InfiniBand HCA actually replaced? INFINIBAND_HCA_BOARD_CHANGE_DETECTED Severity major Description Adapter Module board type changed from 'old_board_description' to 'new_board_description'. Troubleshooting Was this InfiniBand HCA actually replaced? IBM XIV Storage System User Manual...
  • Page 541 INFINIBAND_HCA_BOARD_ID_CHANGE_DETECTED Severity major Description Adapter Module board ID changed from 'old board id' to 'new board id'. Troubleshooting Was this InfiniBand HCA actually replaced? CNA_CHANGE_DETECTED Severity major Description Adapter CNA Id serial number changed from old_serial to new_serial. Troubleshooting Was this CNA actually replaced? CNA_BOARD_CHANGE_DETECTED Severity major...
  • Page 542 Change in MM MM Name to a value of 'MM Value'. Troubleshooting NA. This information is for the event center. TECHNICIAN_WORK_STARTED Severity informational Description Technician work has started, expected to end at End Time. Comment: Comment. Troubleshooting IBM XIV Storage System User Manual...
  • Page 543 Technician work has timed out after Elapsed Time minutes. Comment: Comment. Troubleshooting XIV_SUPPORT_ENABLED Severity informational Description XIV support access from From is enabled from Start Time until Finish Time. Comment: Comment. Troubleshooting XIV_SUPPORT_ENABLED_NO_TIME_LIMIT Severity informational Description XIV support access from From is enabled from Start Time until explicitly disabled.
  • Page 544 Host with name 'host.name' was deleted. CLUSTER_DELETE Severity informational Description Cluster with name 'cluster.name' was deleted. HOST_ADD_PORT Severity informational Description Port of type type and ID 'port_name' was added to Host with name 'host.name'. IBM XIV Storage System User Manual...
  • Page 545 CLUSTER_ADD_HOST Severity informational Description Host with name 'host.name' was added to Cluster with name 'cluster.name'. HOST_REMOVE_PORT Severity informational Description Port of type type and ID 'port_name' was removed from Host with name 'host.name' was deleted. CLUSTER_REMOVE_HOST Severity informational Description Host with name 'host.name' was removed from Cluster with name 'cluster.name'.
  • Page 546 Severity informational Description Rule with name 'old name' was renamed 'new name'. SMTP_GATEWAY_DEFINE Severity informational Description SMTP gateway with name 'name' was defined. SMTP_GATEWAY_UPDATE Severity informational Description SMTP gateway with name 'name' was updated. IBM XIV Storage System User Manual...
  • Page 547 SMTP_GATEWAY_DELETE Severity informational Description SMTP gateway with name 'name' was deleted. SMTP_GATEWAY_RENAME Severity informational Description SMTP gateway with name 'old name' was renamed 'new name'. SMTP_GATEWAY_PRIORITIZE Severity informational Description SMTP gateways were prioritized; the new order is order. SMTP_GATEWAY_FAILED Severity major Description SMTP gateway with name 'name' has failed.
  • Page 548 Description Volume with name 'volume.name' was added to Consistency Group with name 'cg.name'. SLAVE_CONS_GROUP_ADD_VOLUME Severity informational Description Volume with name 'volume.name' was added to Consistency Group with name 'cg.name' by its remote peer. IBM XIV Storage System User Manual...
  • Page 549 CONS_GROUP_REMOVE_VOLUME Severity informational Description Volume with name 'volume.name' was removed from Consistency Group with name 'cg.name'. SLAVE_CONS_GROUP_REMOVE_VOLUME Severity informational Description Volume with name 'volume.name' was removed from Consistency Group with name 'cg.name' by its remote peer. CONS_GROUP_SNAPSHOTS_CREATE Severity informational Description Snapshot Group for Consistency Group with name 'cg.name' was created with name 'cs_name'.
  • Page 550 Group is named 'new_cs_name'. SNAPSHOT_GROUP_FORMAT Severity informational Description All Snapshots in Snapshot Group with name 'cs_name' were formatted'. SNAPSHOT_GROUP_DELETE Severity informational Description All Snapshots in Snapshot Group with name 'cs_name' were deleted. SNAPSHOT_GROUP_CHANGE_PRIORITY Severity informational IBM XIV Storage System User Manual...
  • Page 551 Description Deletion Priority of all Snapshots in Snapshot Group with name 'cs_name' were changed from 'old priority' to 'new priority'. SNAPSHOT_GROUP_LOCK Severity informational Description All Snapshots in Snapshot Group with name 'cs_name' were locked. SNAPSHOT_GROUP_UNLOCK Severity informational Description All Snapshots in Snapshot Group with name 'cs_name' were unlocked.
  • Page 552 Description Target 'target.name' is allowed to access this machine. TARGET_PORT_ADD Severity informational Description Port 'port_name' was added to target named 'target.name'. TARGET_PORT_REMOVE Severity informational Description Port 'port_name' was removed from target named 'target.name'. IBM XIV Storage System User Manual...
  • Page 553 TARGET_PORT_ACTIVATE Severity informational Description Port 'port_name' in target named 'target.name' was activated. TARGET_PORT_DEACTIVATE Severity informational Description Port 'port_name' was deactivated in target named 'target.name'. TARGET_CONNECTIVITY_CREATE Severity informational Description Port 'Connection Remote Port Address' of target named 'Connection Target Name' is connected to the system through Local FC Port.
  • Page 554 TARGET_DISCONNECTED Severity major Description Target named 'target.name' is no longer accessible through any gateway module. TARGET_LINK_DOWN_BEYOND_THRESHOLD Severity major Description Target named 'target.name' is not accessible for a long time. SNAPSHOT_CREATE Severity informational IBM XIV Storage System User Manual...
  • Page 555 Description Snapshot named 'snapshot.name' was created for volume named 'volume.name'. SNAPSHOT_OVERWRITE Severity informational Description Snapshot named 'snapshot.name' was overriden for volume named 'volume.name'. SNAPSHOT_FORMAT Severity informational Description Snapshot named 'snapshot.name' was formatted. SNAPSHOT_CREATE_FAILED_TOO_MANY Severity warning Description Snapshot for volume named 'volume.name' could not be created.
  • Page 556 Can not start async job without next job. volume uid volume uid Troubleshooting INVALID_DATA_GENERATION_ID Severity critical Description Rejected write with id write id on volume volume nr for lba lba. Expected id is expected id Troubleshooting IBM XIV Storage System User Manual...
  • Page 557 CACHE_HAS_LESS_MEMORY Severity warning Description Data module has less memory than expected. node=node - gb_missing GB missing. Troubleshooting some of the DIMMs might have failed UNUSUAL_CONF_LOCK_TIME Severity warning Description very long conf-lock duration. node=node, duration_msec=duration, Troubleshooting look at traces for more details. XDRP_FLAGS_ON_AND_NO_MIRROR Severity critical...
  • Page 558 Tracks Diff Count tracks are different. First diff track Track local: (Local Digest 0, Local Digest 1) Remote: (Remote Digest 0, Remote Digest 1), volume=Volume, partition=Logical Partition Number. Troubleshooting Compare data on primary and secondary. IBM XIV Storage System User Manual...
  • Page 559 SCRUBBING_REMOTE_DIGEST_DIFF_IDENTIFIED_AND_ CORRECTED Severity informational Description Scrubbing identified and corrected data on remote system. disk disk Tracks Diff Count tracks were different. First diff track Track local: (Local Digest 0, Local Digest 1) Remote: (Remote Digest 0, Remote Digest 1), volume=Volume, partition=Logical Partition Number.
  • Page 560 Description SSD SSD ID signaled deferred error on start lba=first_lba, last lba=last_lba, scsi_opcode=scsi_opcode, latency=latency usec, key=key Troubleshooting DISK_MEDIUM_ERROR Severity warning Description Media errors on Disk ID, start LBA=Start LBA, last LBA=Last LBA, latency=latency msec. IBM XIV Storage System User Manual...
  • Page 561 Troubleshooting DISK_DEFERRED_ERROR Severity warning Description Deferred error on Disk ID, start LBA=Start LBA, last LBA=Last LBA, latency=latency msec, key=key Troubleshooting SSD_MEDIUM_ERROR Severity warning Description Media errors on SSD ID, start LBA=Start LBA, last LBA=Last LBA, latency=latency msec. Troubleshooting DISK_ERROR_SENSE_INFORMATION Severity minor Description Disk Disk ID had sense information indicating an...
  • Page 562 SSD SSD ID is not responding to keepalives of type Type for Time from last success msecms Troubleshooting DISK_KEEPALIVE_OK Severity major Description Disk Disk ID is responding to keepalives of type Type after Time from last success msecms Troubleshooting IBM XIV Storage System User Manual...
  • Page 563 SSD_KEEPALIVE_OK Severity major Description SSD SSD ID is responding to keepalives of type Type after Time from last success msecms Troubleshooting DISK_UNRESPONSIVE Severity major Description Disk Disk ID is unresponsive for time msecs, cache dirty level is Dirty Level% SSD_UNRESPONSIVE Severity major Description...
  • Page 564 Severity informational Description User 'User Name' was added to user group 'User Group Name'. Troubleshooting USER_REMOVED_FROM_USER_GROUP Severity informational Description User 'User Name' was removed from user group 'User Group Name'. Troubleshooting USER_GROUP_CREATED Severity informational IBM XIV Storage System User Manual...
  • Page 565 Description A user group with name 'Name' was created. Troubleshooting USER_GROUP_DELETED Severity informational Description A user group with name 'Name' was deleted. Troubleshooting USER_GROUP_RENAMED Severity informational Description User group with name 'Old Name' was renamed 'New Name'. Troubleshooting LDAP_AUTHENTICATION_ACTIVATED Severity informational Description LDAP authentication activated.
  • Page 566 Expiration Date (Counter notification). Troubleshooting LDAP_SERVER_WAS_ADDED Severity informational Description LDAP server 'Server FQDN' was added to the system. Troubleshooting LDAP_SERVER_WAS_REMOVED Severity informational Description LDAP server 'Server FQDN' was removed from the system. Troubleshooting IBM XIV Storage System User Manual...
  • Page 567 ACCESS_TO_HOST_GRANTED_TO_USER_GROUP Severity informational Description User group 'User Group Name' was granted access to host 'Host Name'. Troubleshooting ACCESS_OF_USER_GROUP_TO_HOST_REMOVED Severity informational Description Access of User group 'User Group Name' to host 'Host Name' was removed. Troubleshooting ACCESS_TO_CLUSTER_GRANTED_TO_USER_GROUP Severity informational Description User group 'User Group Name' was granted access to cluster 'Cluster Name'.
  • Page 568 Troubleshooting COMPONENT_FAILURE_WAS_CANCELED Severity informational Description Component Component ID failure status was reset. Troubleshooting COMPONENT_WAS_PHASED_IN Severity informational Description Component ID was phased-in. Troubleshooting COMPONENT_WAS_EQUIPPED Severity informational Description Component ID was equipped. Troubleshooting COMPONENT_WAS_UNEQUIPPED Severity informational IBM XIV Storage System User Manual...
  • Page 569 Description Component ID was unequipped. Troubleshooting INTERFACE_SERVICES_ACTIVATED Severity informational Description Interface services of Module ID were activated. Troubleshooting INTERFACE_SERVICES_DEACTIVATED Severity informational Description Interface services of Module ID were deactivated. Troubleshooting COMPONENT_FIRMWARE_UPGRADE_ABORTING Severity warning Description Aborting Upgrade type upgrade of Firmware type firmware, version Label, on Scope.
  • Page 570 Description Gateway Node #Node ID: connection to target name:target's connection index mirroring connection was established, but being ignored because the remote end is not an XIV target or is not properly configured Troubleshooting Please make sure the target's designation is...
  • Page 571 EMERGENCY_CONSOLE_ACCESS Severity warning Description Emergency login to 'Unix Account Name' account on module 'Component ID' from tty 'TTY Device'. Troubleshooting CR_BYPASS_ACCESS Severity warning Description Command that bypasses CR mechanism access to 'Unix Account Name' account on module 'Component ID' from 'IP Address'. Troubleshooting CR_KEY_SETUP_OK Severity...
  • Page 572 Please contact support. DISK_PROBLEMATIC_BEHAVIOR_CLEARED Severity informational Description Component ID no longer exhibits problematic behavior. Troubleshooting Please contact support. DISK_HIGH_MEDIA_ERROR_RATE_DETECTED Severity variable Description Component ID exhibits high media error rate of rule rule_type. Troubleshooting Please contact support. IBM XIV Storage System User Manual...
  • Page 573 DISK_HIGH_MEDIA_ERROR_RATE_CLEARED Severity informational Description Component ID no longer exhibits high media error rate. Troubleshooting Please contact support. SSD_PROBLEMATIC_BEHAVIOR_DETECTED Severity variable Description Component ID exhibits problematic behavior. Troubleshooting Please contact support. SSD_PROBLEMATIC_BEHAVIOR_CLEARED Severity informational Description Component ID no longer exhibits problematic behavior.
  • Page 574 Power supply #PS Number failure for Component Troubleshooting Check power cables IB_SWITCH_POWER_RESTORED Severity informational Description Power supply #PS Number restored for Component IB_SWITCH_HAS_FAN_FAILURE Severity warning Description Fan #fan failure for Component ID. Troubleshooting Check fans, replace switch IB_SWITCH_FAN_FAILURE Severity warning IBM XIV Storage System User Manual...
  • Page 575 Description Fan #fan failure for Component ID. Troubleshooting Check fans, replace switch IB_SWITCH_FAN_RESTORED Severity informational Description Fan #fan restored for Component ID. IB_SWITCH_HAS_TEMPERATURE Severity variable Description Component ID - temperature of temperature sesnsor is temperatureC. Troubleshooting Please contact support. IB_SWITCH_HIGH_TEMPERATURE Severity variable Description...
  • Page 576 Severity informational Description The firmware version of 'Component ID' was updated to 'New Version'. Troubleshooting None. IB_SWITCH_PORT_POWER_UP_FAILED Severity minor Description Power up failed for port 'Component ID' Troubleshooting Please contact support IB_SWITCH_LOG_COLLECT_SUCCESSFUL Severity informational IBM XIV Storage System User Manual...
  • Page 577 Description Log collection for IB switch 'switch_id' completed successfuly. Log can be found in module 'log_module' in the following directory: 'log_location'. IB_SWITCH_LOG_COLLECT_FAILED Severity warning Description Log collection for IB switch 'switch_id' failed. Failure reason: 'failure_reason'. IB_SWITCH_PORT_ACTIVATION_FAILED Severity minor Description Power up failed for port 'Component ID' Troubleshooting Please contact support IB_PORT_MOVED...
  • Page 578 About to start a UPS self-test on UPS Component UPS_SELF_TEST_HAS_PASSED Severity informational Description A UPS self-test has passed on UPS Component ID. UPS_SELF_TEST_HAS_FAILED Severity major Description A UPS self-test has failed on UPS Component ID. IBM XIV Storage System User Manual...
  • Page 579 UPS_SELF_TEST_WAS_SKIPPED Severity warning Description A UPS self-test for UPS Component ID has been skipped since not all UPS's/PSU's are OK or too close to last self test. UPS_SELF_TEST_IS_POSSIBLY_INACCURATE Severity informational Description A UPS self-test for Component ID might be inaccurate, capacity is Battery Capacity and is lower or equal to the minimum capacity Minimum Capacity for Self Test.
  • Page 580 UPS_PREDICTIVE_REMAINING_RUNTIME_TOO_LOW Severity minor Description UPS Component ID has a remaining runtime of Remaining Runtime minutes, but the time will drop to Predictive Remaining Runtime minutes in case one of the other UPSes stops working. IBM XIV Storage System User Manual...
  • Page 581 Troubleshooting Contact support UPS_PREDICTIVE_REMAINING_RUNTIME_OK Severity informational Description UPS Component ID has a remaining runtime of Remaining Runtime minutes, the time will drop to Predictive Remaining Runtime minutes in case one of the other UPSes stops working. Troubleshooting Contact support UPS_HAS_FAILED Severity critical Description...
  • Page 582 Invalid reply from ATS Component ID, possible ATS failure. Troubleshooting ATS_SET_INPUT_LINE Severity informational Description ATS Component ID input line will be set to JInput Line. Troubleshooting ATS_SET_INPUT_LINE_FAILURE Severity warning Description Failed setting ATS Component ID input line to JInput Line. IBM XIV Storage System User Manual...
  • Page 583 Troubleshooting Try running command again, make sure input line wasn't switched by using ats_list and/or looking at the ATS LEDs. If all fail, switch the lines manually by disconnecting one input line and reconnecting it. ATS_SET_INPUT_TO_DOWN_LINE Severity warning Description Line JInput Line of ATS Component ID is down, will not switch input line.
  • Page 584 Description Serial link to UPS Component ID is down. Troubleshooting Please contact support. UPS_LINK_READ_IGNORED_DATA_TIMEDOUT Severity warning Description Link to UPS Component ID timed out skipping ignored data. Troubleshooting Please contact support. UPS_CABLE_CHECK_FAILED Severity minor IBM XIV Storage System User Manual...
  • Page 585 Description Cable check of Component ID failed, either its serial or network cables are crosswired with Hostname. Troubleshooting Either the cable is disconnected or network and serial cables are miswired. UPS_CABLE_CHECK_PASSED Severity informational Description Cable check of Component ID passed. UPS_CABLE_CHECK_CONNECTION_FAILED Severity minor...
  • Page 586 ID input line JLine, Phase. Troubleshooting ATS_OUTLET_OVER_CURRENT Severity warning Description Over-Current on ATS Component ID outlet POutlet. Troubleshooting Please contact support. ATS_OUTLET_CURRENT_RECOVERY Severity informational Description Recovered from over-current on ATS Component ID outlet POutlet. Troubleshooting ATS_FAILED Severity minor IBM XIV Storage System User Manual...
  • Page 587 Description ATS Component ID exhibits a failure state. Troubleshooting Please contact support. ATS_RECOVERED Severity informational Description ATS Component ID exited from the failure state. Troubleshooting MODULE_NO_IP_CONNECTIVITY Severity warning Description There is no IP connectivity to failed Component Id. Troubleshooting Information sent to event center in case of module failure.
  • Page 588 Component ID IPMI SDR Event Error. MODULE_SEL_LOG Severity warning Description Component ID:[Index] Log string. Raw event data is 'd0 d1 d2'. Troubleshooting Please contact support. MODULE_FAILURE_DATA Severity critical Description Component ID: Count lines Log string. Troubleshooting Please contact support. IBM XIV Storage System User Manual...
  • Page 589 CONNECTION_TO_MAINTENANCE_MODULE_IS_OK Severity informational Description The Maintenance module can now be reached from Component ID. Troubleshooting Please contact support NO_CONNECTION_TO_MAINTENANCE_MODULE Severity major Description The Maintenance module can not be reached from Component ID. Troubleshooting Please contact support MODULE_TEMPERATURE_INCONSISTENT_WITH_OTHERS Severity warning Description Component ID external temperature not consistent with other modules.
  • Page 590 Check air conditioning system or contact support. SERVICE_MODE_OF_SYSTEM_HAS_CHANGED Severity variable Description Service mode of system has changed. The urgency of service actions has changed from Previous Maintenance Urgency to Maintenance Urgency MM_OK Severity informational Description Component ID is now OK. IBM XIV Storage System User Manual...
  • Page 591 Troubleshooting Please contact support. MM_FAILED Severity major Description Component ID has failed. Hardware status: Status. Troubleshooting Please contact support. MM_CHANGE_DETECTED Severity major Description Component ID has been changed from a serial of old_serial to new_serial. Troubleshooting Was this MM actually replaced? MODULE_MCH_DATA Severity critical...
  • Page 592 Please contact support. DISK_BMS_ERROR_DETECTED Severity warning Description Component ID - BMS error detected: Sense Key/Additional Sense Code/Additional Sense Code Qualifier Sense Key - Sense Code (LBA: LBA). Troubleshooting Please contact support. DISK_EXCESSIVE_BMS_ACTIVITY Severity variable IBM XIV Storage System User Manual...
  • Page 593 Description Component ID exhibits excessive BMS activity, fill time is Time to fill BMS log minutes. Troubleshooting Please contact support. SATA_SMART_STATUS_READING_FAILED Severity warning Description reading SMART attributes of Disk ID failed. SMART trip value= Troubleshooting Please contact support. SATA_SMART_STATUS_READING_FAILURE Severity warning Description Component ID reading SMART attributes failed.
  • Page 594 Severity major Description The PDB on module module has failed. Troubleshooting Please contact support. SES_PDB_WARNING_ON Severity warning Description The PDB on module module displays some warning conditions. Troubleshooting Please contact support. SES_PDB_IS_WORKING Severity informational IBM XIV Storage System User Manual...
  • Page 595 Description The PDB module module is working now. Troubleshooting SES_BMC_ERROR_SIGNAL Severity warning Description The BMC on module module signals an error. Troubleshooting Please contact support. SES_BMC_IS_OK_NOW Severity informational Description The BMC on module module is OK now. Troubleshooting SES_ALARM_LED_IS_SIGNALING Severity warning Description On module alarm of type 'Component type (LED...
  • Page 596 Severity minor Description Component ID temperature is temperatureC. The temperature is stabilizing, but still abnormally high. COMPONENT_TEMPERATURE_IS_ABNORMALLY_HIGH_AND_ DROPPING Severity minor Description Component ID temperature is temperatureC. The temperature is dropping, but still abnormally high. IBM XIV Storage System User Manual...
  • Page 597 COMPONENT_TEMPERATURE_IS_VERY_HIGH Severity major Description Component ID temperature is temperatureC. The temperature is very high and may effect on component performance or even damage it. COMPONENT_TEMPERATURE_IS_VERY_HIGH_AND_ STABILIZING Severity major Description Component ID temperature is temperatureC. The temperature is stabilizing, but still very high. COMPONENT_TEMPERATURE_IS_VERY_HIGH_AND_DROPPING Severity major...
  • Page 598 PSU Voltage Type output DC voltage value is now Voltage, which is within the valid range. SES_PSU_MONITORING_UNAVAILABLE Severity minor Description Can't monitor PSU, but it seems to supply power. Troubleshooting Please contact support. SES_DOUBLE_PSU_FAILURE Severity major IBM XIV Storage System User Manual...
  • Page 599 Description Both PSUs on Module report critical failures, this is probably because of a faulty PDB. Troubleshooting Please contact support. SES_AMBIENT_TEMPERATURE_SEVERITY_CHANGED Severity variable Description Module module sensor desc reports (readingC) state desc. Troubleshooting Adjust ambient temperature at this module intake. SES_TEMPERATURE_SEVERITY_CHANGED Severity variable...
  • Page 600 PSU-2 of model 'PSU-2 Model'. Troubleshooting Replace one of the PSUs to appropriate model. PSU_MODEL_MIX_IS_OK_NOW Severity informational Description PSU-1, of model 'PSU-1 Model', is compatible with PSU-2 of model 'PSU-2 Model'. Troubleshooting FAN_CONTROLLER_FIRMWARE_VERSION_UNEXPECTED Severity warning IBM XIV Storage System User Manual...
  • Page 601 Description Fan controller firmware on Component - unexpected code-level, found Major.Minor.Level.Build (configuration Major.Minor.Level) which is old and should be upgraded Troubleshooting Please contact support. IPMI_BMC_FIRMWARE_VERSION_UNEXPECTED Severity warning Description IPMI BMC firmware on Module - version fmajor.fminor.faux is old and should be upgraded Troubleshooting Please contact support.
  • Page 602 SAS_RESET_DETECTED Severity warning Description SAS Controller reset was detected on component ID total Reset Count times. Troubleshooting Please contact support. IPMI_NOT_WORKING Severity major Description IPMI is not working on Module. Troubleshooting Please contact support. IBM XIV Storage System User Manual...
  • Page 603 IPMI_USER_SETUP_FAILED Severity major Description Error setting up IPMI USER for module Module. Troubleshooting Contact support. IPMI_LAN_SETUP_FAILED Severity major Description Error setting up IPMI LAN channel Channel for module Module. Troubleshooting Contact support. IPMI_SEL_ENTRY_CRIT Severity critical Description Entry Name SEL entry on component ID Date Time with data d0=d0 d1=d1 d2=d2 dir=direction.
  • Page 604 Network interface Interface Role #Interface Index on Component ID - link disconnected. Troubleshooting Please contact support. NETWORK_LINK_IS_NOW_UP Severity informational Description Network interface Interface Role #Interface Index on Component ID - link regained. Troubleshooting Please contact support. NETWORK_LINK_NO_DATA Severity minor IBM XIV Storage System User Manual...
  • Page 605 Description Network interface Interface Role #Interface Index on Component ID - link has no data flowing through for the last Time Not flowing seconds. Troubleshooting Please contact support. NETWORK_LINK_NO_DATA_LONG Severity major Description Network interface Interface Role #Interface Index on Component ID - link has no data flowing through for the last Time Not flowing seconds.
  • Page 606 Description Network interface Interface Role #Interface Role Index on Component ID has flow control turned on. Troubleshooting CF_PARTITION_INCONSISTENT Severity major Description Some of the partitions on the compact flash on Component ID have inconsistencies IBM XIV Storage System User Manual...
  • Page 607 Troubleshooting The compact flash has inconsistencies on some of it's partitions. UPS_WARMSTART Severity informational Description Component ID did a warmstart Troubleshooting Normally this is fine, if there is another issue at around the same time, it is worth mentioning this event to the support CPU_LOCKUP Severity...
  • Page 608 Delta since last sample. Troubleshooting SAS_LINK_TOO_MANY_RESETS Severity major Description SAS link SAS Type[ID] on module Module had Delta resets, only Allowed resets are allowed. Disk Disk will be automatically phased out. Troubleshooting Please contact support. IBM XIV Storage System User Manual...
  • Page 609 SAS_LINK_TOO_MANY_RESETS_PHASEOUT_DISK Severity minor Description SAS link SAS Type[ID] on module Module had Delta resets, only Allowed resets are allowed. Please phase out disk Disk. Troubleshooting Phase out the disk and contact support. ERROR_ON_SATA_HOST Severity major Description SATA device failure on Module. Troubleshooting Please contact support.
  • Page 610 Component ID does not conform to the specification. Troubleshooting Please contact support. CPU_COMPLIANCE_CHECK_FAILED Severity major Description Installed processor on module Component ID does not conform to the specification. Troubleshooting Please contact support. IBM XIV Storage System User Manual...
  • Page 611 PCI_ADAPTER_COMPLIANCE_CHECK_FAILED Severity major Description Specification compliance check failed for PCI adapters on module Component ID. Troubleshooting Please contact support. PCI_ADAPTER_COMPLIANCE_CHECK_ADAPTER_FAILED Severity major Description PCI adapter on module Component ID does not conform to the specification. Adapter details: 'Description'. Troubleshooting Please contact support. INFINIBAND_HCA_COMPLIANCE_CHECK_FAILED Severity major...
  • Page 612 SSD Component ID has a new firmware version already installed, upgrade skipped. Troubleshooting SSD_BIGGER_THAN_EXPECTED Severity warning Description Installed SSD Component ID has a size of SizeGB which is bigger than the expected size of Spec SizeGB. Troubleshooting Please contact support. IBM XIV Storage System User Manual...
  • Page 613 SSD_SMALLER_THAN_EXPECTED Severity major Description Installed SSD Component ID has a size of SizeGB which is smaller than the expected size of Spec SizeGB. Troubleshooting Please contact support. SSD_FOUND_UNEXPECTED Severity warning Description SSD Component ID was found while SSD Caching feature is disabled. Troubleshooting Please contact support.
  • Page 614 Memory ECC errors were detected on Module. Troubleshooting Please contact support. DIMM_CORRECTABLE_ERROR_DETECTED Severity variable Description Memory correctable ECC errors were detected on Module, Count errors on DIMM channel Channel, position Position. Troubleshooting Please contact support. DIMM_UNCORRECTABLE_ERROR_DETECTED Severity variable IBM XIV Storage System User Manual...
  • Page 615 Description Memory uncorrectable ECC errors were detected on Module, Count errors on DIMM channel Channel, position Position. Troubleshooting Please contact support. DIMM_ERRORS_PHASING_OUT_MODULE Severity major Description Module will be phased out as we detected too many DIMM errors there. Troubleshooting Please contact support. PCIE_LINK_FATAL_ERROR Severity major...
  • Page 616 IOs pending IOs Pending. Troubleshooting Please contact support. HOST_RESET_SUCCEEDED Severity informational Description Host reset on module module succeeded. Reset duration reset duration, IOs pending IOs Pending. Troubleshooting Please contact support. DISK_RESET_WAS_SENT Severity warning IBM XIV Storage System User Manual...
  • Page 617 Description A disk reset was sent to Component ID. Troubleshooting Please contact support. DISK_RESET_FAILED Severity major Description Reset to disk Component ID has failed. Reset duration reset duration, IOs pending IOs Pending. Troubleshooting Please contact support. DISK_RESET_SUCCEEDED Severity informational Description Reset to disk Component ID succeeded.
  • Page 618 Please contact your Administrator. DISK_FIRMWARE_VERSION_UNEXPECTED Severity warning Description Disks in module Component have unexpected firmware level. Check full event details for the complete list of the mismatched disks. Troubleshooting Please update the firmware level. SSD_FIRMWARE_VERSION_UNEXPECTED Severity warning IBM XIV Storage System User Manual...
  • Page 619 Description SSDs in module Component have unexpected firmware level. Check full event details for the complete list of the mismatched ssds. Troubleshooting Please update the firmware level. INTERFACE_NODE_CHOKING Severity warning Description Interface node #Node has long Cache latency. Entered choked state choke_time msec ago on node=Node Troubleshooting Please contact support.
  • Page 620 Interface node #Node reports partial write to volume 'volume' on lba lba, primary failed=primary_failed, secondary failed=secondary_failed, remote failed=remote_failed. PORT_PREP_FOR_UPGRADE_TIMED_OUT Severity warning Description Preparation of port_type port 'local_port_name' for hot-upgrade timed out due to host 'host_name' port 'host_port_name'host_port_addr IBM XIV Storage System User Manual...
  • Page 621 IPINTERFACE_CREATE Severity informational Description A new iscsi IP interface was defined with name 'interface name' on module module with ports 'port list' and IP address IP address IPINTERFACE_DELETE Severity informational Description ISCSI IP interface with name 'interface name' was deleted IPINTERFACE_RENAME Severity informational...
  • Page 622 Description A new IPSec connection named 'name' was added IPSEC_CONNECTION_UPDATED Severity informational Description The IPSec connection named 'name' was updated IPSEC_CONNECTION_REMOVED Severity informational Description The IPSec connection named 'name' was removed PRIVATE_KEY_ADDED Severity informational IBM XIV Storage System User Manual...
  • Page 623 Description A new private key named 'name' with fingerprint 'fingerprint' and size key_size bits was added. CERTIFICATE_REMOVED Severity informational Description The certificate named 'name' was removed. PKCS12_CERTIFICATE_ADDED Severity informational Description A new PKCS#12 named 'name' with fingerprint 'fingerprint' was added. PKI_RENAME Severity informational...
  • Page 624 Error message: 'Error Message'; timeout expired: Timeout Expired?. Troubleshooting Please contact support. EVENTS_WERE_NOT_SAVED Severity variable Description Node #Node could not save Num Lost events of maximal severity Maximal Severity. Troubleshooting Please contact support. EVENT_TEST Severity variable IBM XIV Storage System User Manual...
  • Page 625 Description Event Index of Count test events (description: Description; severity: Severity; node: Node). Troubleshooting CUSTOM_EVENT Severity variable Description Description Troubleshooting MM_EVENT Severity variable Description Maintenance Module Category event : Description Troubleshooting Events coming from the Maintenance Module TRACES_DUMPING Severity informational Description Description Troubleshooting...
  • Page 626 Finished downloading software needed for upgrade to version version. Upgrade consequence is consequence Troubleshooting UPGRADE_FILE_LIST_RETRIEVAL_FAILED Severity critical Description Could not receive new verions' files list from repository. error code is error. Troubleshooting Contact support IBM XIV Storage System User Manual...
  • Page 627 UPGRADE_STARTS Severity informational Description System starting an upgrade. Troubleshooting PRE_UPGRADE Severity informational Description System preparing an upgrade procedure type type Troubleshooting UPGRADE_IS_OVER Severity informational Description System went up after an upgrade. Troubleshooting IOS_RESTORED_AFTER_HOT_UPGRADE Severity informational Description System is able to perform I/Os after a hot upgrade.
  • Page 628 One or more of the pre-upgrade validations failed. Troubleshooting Fix the problems pointed out it previous events and revalidate. PRE_UPGRADE_VALIDATION_FAILED Severity critical Description One of the pre-upgrade validations failed with status error. Troubleshooting Contact support UPGRADE_IS_ALLOWED Severity informational IBM XIV Storage System User Manual...
  • Page 629 Description All of the pre-upgrade validations passed successfully. Troubleshooting POST_UPGRADE_SCRIPT_STARTED Severity informational Description Post-upgrade script started. Troubleshooting POST_UPGRADE_SCRIPT_FINISHED Severity informational Description Post-upgrade script finished successfully. Troubleshooting PRE_UPGRADE_SCRIPT_DISAPPROVES Severity critical Description Upgrade cannot commence because some of the vlidations in the pre-upgrade script failed. Explanation: explanation.
  • Page 630 Admin server SSL settings were changed. SSLv2 enabled: SSLv2 Enabled, cipher list: Cipher List. Change succeeded on Module? Change Succeeded. Troubleshooting METADATA_SET Severity warning Description Object type with name 'Object name' has new metadata value. Troubleshooting IBM XIV Storage System User Manual...
  • Page 631 METADATA_DELETE Severity warning Description Metadata object deleted for Object type with name 'Object name'. Troubleshooting PATCH_SCRIPT_ADDED Severity informational Description Added patch Patch Name. Troubleshooting Was patch supposed to have been added. PATCH_SCRIPT_DELETED Severity informational Description Deleted patch Patch Name. Troubleshooting REMOTE_SUPPORT_CONNECTED Severity informational...
  • Page 632 Troubleshooting Please approve the electronic license. MASTER_SM_CHOSEN Severity informational Description Subnet manager on module 'Component ID' becomes master. Troubleshooting MODULE_IB_PORTS_DOWN Severity warning Description SM: all infiniband ports on module 'Component ID' are down. IBM XIV Storage System User Manual...
  • Page 633 Troubleshooting MODULE_SM_PRIO_CHANGED Severity informational Description SM: SM priority changed on module 'Component ID' from 'Priority' to 'Priority'. Change reason: 'Change Reason'. Troubleshooting MASTER_SM_RESCAN Severity informational Description Master SM on module 'Component ID' has reloaded configuration and rescans network. Troubleshooting IB_MODULE_MISWIRE Severity warning Description...
  • Page 634 Troubleshooting IB_MODULE_PORT_BAD_GUID_FORMAT Severity warning Description Module port#Port Number, connected to switch port 'Component ID' has GUID:'Port GUID' which is not xiv-GUID or its serial is not compatible with the machine. Troubleshooting IB_BAD_CONFIGURATION Severity major Description Bad IB configuration values found. Given values are 'IB component ID'.
  • Page 635 IB_SWITCH_IS_MISSING Severity warning Description An Infiniband switch is missing 'Component ID'. Troubleshooting IB_MISSING_SWITCH_FOUND Severity informational Description An Infiniband switch 'Component ID' which was missing is now found. Troubleshooting IB_PORT_FORCE_DOWN_SUCCESS Severity critical Description IB port 'HCA Port' on module 'Module' was powered off.
  • Page 636 Description Performance Class name max BW rate was changed to BW rate PERF_CLASS_CREATE Severity informational Description Performance Class with name 'name' was created PERF_CLASS_DELETE Severity informational Description Performance Class with name 'name' was deleted IBM XIV Storage System User Manual...
  • Page 637 PERF_CLASS_ADD_HOST Severity informational Description Host with name 'host_name' was added to Performance Class with name 'name' PERF_CLASS_REMOVE_HOST Severity informational Description Host with name 'host_name' was removed from Performance Class with name 'name' STATUS_AGENT_ERROR Severity critical Description Status Agent error: message (value=value). Troubleshooting Please contact support.
  • Page 638 Troubleshooting HOST_PROFILE_CLEARED Severity informational Description Host profile value has been cleared for host host_name. Troubleshooting SYMON_COMPONENT_FAILURE_RECOMMENDED Severity informational Description Symptomatic monitoring recommends failing Component. Troubleshooting IBM XIV Storage System User Manual...
  • Page 639 SYMON_COMPONENT_FAILURE_WOULD_HAVE_BEEN_ RECOMMENDED Severity informational Description Symptomatic monitoring would have recommended failing ComponentId but SuppressionReason. Troubleshooting MEDIUM_ERROR_RECOVERED Severity informational Description Medium error on volume=Volume, logical-partition=Logical Partition Number was recovered. Troubleshooting MEDIUM_ERROR_NOT_RECOVERED Severity critical Description Medium error on volume=Volume, logical-partition=Logical Partition Number could not be recovered due to Reason.
  • Page 640 IBM XIV Storage System User Manual...
  • Page 641: Chapter 25. Return Codes

    Chapter 25. Return Codes The following are the return codes. Return Code Error Description Success. Command execution failed. No connection to the system. Password is required. Password does not match system password. Command not allowed from this client. Bad XCLI option. Internal XCLI error.
  • Page 642 IBM XIV Storage System User Manual...
  • Page 643: Notices

    Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
  • Page 644 IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created...
  • Page 645: Glossary

    Glossary This glossary includes terms and definitions for IBM XIV Storage System. This glossary includes selected terms and definitions from: access To obtain computing services or data. v The American National Standard Dictionary for In computer security, a specific type of Information Systems, ANSI X3.172–1990,...
  • Page 646 The storage product can use this destination link to place a call to IBM or to another See event destination. service provider when it requires service. With access to the machine, service...
  • Page 647 See functional module. SCSI commands over IP networks. functional module One of the icons of a functional area, on the left-hand pane of the IBM XIV Storage latency Management GUI screen. For example, Amount of time delay between the System (under Monitor) or Hosts and moment an operation is issued, and the LUNs (under Configuration).
  • Page 648 SNMP trap. state can never be used for restoring its master volume. SMS gateway An external server that is used to send multipathing SMSs. Enables host interface modules direct access to any volume. IBM XIV Storage System User Manual...
  • Page 649 SMTP gateway thin provisioning An external host that is used to relay The ability to define logical volume sizes e-mail messages through the SMTP that are much larger than the physical protocol. capacity installed on the system. snapshot set Transmission Control Protocol The resulting set of synchronized Transmission Control Protocol (TCP) on snapshots of a volume set in a consistency...
  • Page 650 When running a list of commands as a an authenticated LDAP user. batch XCLI system command An XCLI command that is sent to the XIV system for processing. IBM XIV Storage System User Manual...
  • Page 652 Printed in USA GC27-3914-05...

Table of Contents