SAN Volume Controller tasks
- Getting started
- About the SAN Volume Controller Infocenter
- What's in the SAN Volume Controller Infocenter?
- Who should use the SAN Volume Controller Infocenter?
- How to send your comments
- Conventions used in this information center
- Syntax diagrams
- CLI special characters
- Emphasis
- Numbering conventions
- Accessibility
- Using the Information Center
- Using the SAN Volume Controller
- Preinstallation tasks
- Installation tasks
- Configuration tasks
- SAN Volume Controller Console
- SAN Volume Controller Console layout
- SAN Volume Controller Console banner area
- SAN Volume Controller Console task bar
- SAN Volume Controller Console portfolio
- SAN Volume Controller Console work area
- Accessing the SAN Volume Controller Console
- Launching the SAN Volume Controller Console
- Signing on to the SAN Volume Controller Console
- Using the SAN Volume Controller Console application on the master console
- Scenario: typical usage for the SAN Volume Controller Console
- Adding nodes to a cluster
- Displaying node properties using the SAN Volume Controller Console
- Creating managed disk groups
- Creating virtual disks
- Creating hosts
- Showing VDisks mapped to a host
- Creating virtual disk-to-host mappings
- Creating consistency groups
- Creating FlashCopy mappings
- Getting started with the Command-Line Interface
- Preparing the SSH client system overview
- Preparing the SSH client system to issue command-line
interface (CLI) commands
- Preparing the SSH client on an AIX host
- Issuing CLI commands from a PuTTY SSH Client system
- Running the PuTTY and plink utilities
- Configuring the cluster using the CLI
- Setting the cluster time using the CLI
- Reviewing and setting the cluster features using
the CLI
- Displaying cluster properties using the CLI
- Maintaining passwords using the CLI
- Scenario: typical usage for the command-line interface
- Adding nodes to the cluster using the CLI
- Displaying node properties using the CLI
- Discovering MDisks using the CLI
- Creating managed disk (MDisk) groups
using the CLI
- Adding MDisks to MDisk groups using the CLI
- Create virtual disks (VDisks)
- Creating host objects using the CLI
- Create VDisk-to-host mappings using the CLI
- Creating a FlashCopy consistency group and adding
mappings using the CLI
- Preparing and triggering a FlashCopy mapping using
the CLI
- Create FlashCopy mappings using the CLI
- Preparing and triggering a FlashCopy Consistency
Group using the CLI
- Concepts
- Application servers
- Overview of backup functions
- CIM agent
- Common Information Model
- CIM-related concepts
- CIM agent client
- CIM agent server
- CIM Agent for the SAN Volume Controller
- Extrinsic methods
- Intrinsic methods
- CIM Agent object classes
- Clusters
- Cluster state
- Cluster operation and quorum disks
- Cluster configuration backup
- Configuration restore
- Copy Services
- FlashCopy
- Background copy
- FlashCopy applications
- Dependent writes
- FlashCopy mappings
- Remote Copy
- Asynchronous remote copy
- Synchronous Remote Copy
- Remote Copy relationships
- Remote Copy partnerships
- Consistency groups
- FlashCopy consistency groups
- Remote Copy consistency groups
- Storage subsystems
- Host objects
- Input/Output (I/O) groups
- Managed disks (MDisks)
- Managed disk (MDisk) groups
- Master console
- IBM Director
- Tivoli Storage Area Network Manager
- Migration
- Nodes and clusters
- Clusters
- Cluster configuration backup
- Configuration restore
- Nodes
- Configuration node
- Object overview
- Object naming
- Storage area networks (SANs)
- Redundant SANs
- Counterpart SANs
- SAN Volume Controller
- Small computer system interface (SCSI) back-end
layer
- Quorum disks
- Controlling access to disk controller systems
and devices
- Small computer system interface (SCSI) front-end
layer
- Input/output (I/O) governing
- Secure copy (SCP)
- Secure Shell (SSH)
- Storage Management Initiative Specification
- Storage pools
- Switches
- Uninterruptible power supply overview
- User roles
- Vital product data (VPD)
- Virtual disks (VDisks)
- Virtual disk-to-host mapping
- Virtualization
- The need for virtualization
- Fabric level virtualization models
- Asymmetric virtualization
- Symmetric virtualization
- Implementation of virtualization in the SAN Volume Controller
- Planning
- Preparing the physical configuration
- Completing the hardware location chart
- Hardware location chart instructions
- Hardware location chart
- Completing the cable connection table
- Cable connection table
- Completing the configuration data table
- Configuration data table
- Installation planning
- Preparing your SAN Volume Controller environment
- Preparing your uninterruptible
power supply environment
- Preparing your master console environment
- Ports and connections
- Planning guidelines for using your SAN Volume Controller in a SAN
environment
- Storage Area Network
- SAN fabric
- Fibre-channel extenders
- Nodes
- I/O groups and uninterruptible power supply
- Uninterruptible power
supply and power domains
- Disk controllers
- Planning for your SAN Volume Controller configuration
- Maximum configuration
- Configuration rules and requirements
- Configuration rules
- Storage susbystems
- Host bus adapters
- Nodes
- Fibre-channel switches
- Power
- Configuration requirements
- Installing
- Preparing for installation
- Installing the uninterruptible power supply
- Installing the support rails for the uninterruptible
power supply
- Installing the support rails for the uninterruptible
power supply
- Installing the uninterruptible power supply into
the rack
- Connecting the uninterruptible power supply
to the SAN Volume Controller
- Installing the master console
- Installing the support rails and the SAN Volume Controller into a
rack
- Installing the support rails for the SAN Volume Controller
- Installing the SAN Volume Controller into the rack
- Connecting the SAN Volume Controller to the uninterruptible power supply
- Connecting the SAN Volume Controller to the SAN and to the Ethernet
network
- Verifying the SAN Volume Controller installation
- Installation overview for the SAN Volume Controller Console
- Obtaining the software packages
- SAN Volume Controller Console hardware installation requirements
- SAN Volume Controller Console workstation space requirements
- SAN Volume Controller Console software installation requirements
- Installing the software
- Installing or upgrading the SAN Volume Controller Console in graphical mode
- Installing or upgrading the SAN Volume Controller Console in unattended
(silent) mode
- Installing anti-virus software
- Upgrading the SAN Volume Controller Console software
- Verifying the Windows services associated
with the SAN Volume Controller Console
- Determining the version of the software
- Post installation tasks
- Removing the SAN Volume Controller Console
- SAN Volume Controller and host system overview
- Requirements for attaching to a Hewlett-Packard
9000 host
- Installing the adapter drivers for the HP-UX 11.0
and HP-UX 11.i operating systems
- Locating the WWPN for a Hewlett Packard host
- Known problems and limitations
- Requirements for attaching to an IBM RS/6000 or IBM eServer pSeries host
- Preparing for installation
- Installing the host attachment package
- Completing the installation
- Verifying the configuration
- Making SAN changes
- Configuring SAN Volume Controller devices with multiple paths
per LUN
- Locating the WWPN for an IBM eServer pSeries or an RS/6000 host
- Known issues and limitations
- Attaching to an Intel host running Linux
- Installing the QLogic adapter card
- Downloading the current QLogic adapter driver
- Installing the QLogic adapter drivers
- Defining the number of disks on Linux
- Setting queue depth
- SAN Volume Controller storage configuration
- SAN Volume Controller disk partitions
- Assigning the system ID to the partition
- File systems on the SAN Volume Controller
- Locating the WWPN for a Linux host
- Known problems and issues
- Attaching to a Sun host
- Installing the JNI PCI adapter card
- Downloading the current JNI PCI adapter driver
- Installing the JNI PCI adapter driver
- Installing the JNI SBUS adapter card
- Downloading the current JNI SBUS adapter driver
- Installing the JNI SBUS adapter driver
- Configuring the host bus adapters
- Running the LUN configuration method
- Parameter settings for the JNI FCE-6460 and
JNI FCE-1473 adapters
- Setting the Sun host system parameters for JNI adapters
- Setting the Sun host system parameters for QLogic
adapters
- Locating the WWPN for a Sun host
- Attaching to a Microsoft Windows 2000 or 2003 host
- Installing and configuring the Netfinity FAStT
adapter card
- Checking the level of the device driver in the Netfinity FAStT adapter card
- Documentation included with the Netfinity FAStT
adapter card
- Installing the device driver for a Netfinity FAStT
adapter card
- Updating the Microsoft Windows 2000 or 2003 device driver
- Installing the QLogic QLA23xx adapter card
- Downloading the QLogic adapter driver
- Installing the QLogic adapter driver
- Installing the Emulex adapter card
- Downloading the Emulex adapter driver
- Installing the Emulex adapter drivers
- Configuration settings for the Emulex adapter
drivers
- Configuration for availability and recovery
- Setting the TimeOutValue registry
- Locating the WWPN for a Windows 2000 or 2003 host
- Windows 2000 known problems and issues
- Configuring
- Authorized users
- Adding users
- Modifying users
- Clusters
- Adding a cluster
- Setting cluster time
- Create cluster from the front panel
- Connecting to the cluster
- Configuring a cluster using the SAN Volume Controller Console
- Updating feature settings
- Configuration requirements
- Configuring and servicing storage subsystems
- Identifying your storage subsystem
- Configuration guidelines
- Storage subsystem logical disks
- RAID array configuration
- Optimal managed disk group configurations
- Considerations for FlashCopy mappings
- Image mode and migrating existing data
- Migrating data with an equivalent amount of free
capacity
- Migrating data with a smaller amount of free capacity
- Configuring a balanced storage subsystem
- Expanding a logical unit
- Modifying a logical unit mapping
- Creating a quorum disk
- Manual discovery
- Configuring the EMC CLARiiON controller
- Configuring the EMC CLARiiON controller with Access
Logix installed
- Registering the SAN Volume Controller Ports with your
EMC CLARiiON
- Configuring your storage groups
- Supported models of the EMC CLARiiON
- Supported firmware levels for the EMC CLARiiON
- Concurrent maintenance on the EMC CLARiiON
- Sharing the EMC CLARiiON between a host and
the SAN Volume Controller
- Switch zoning limitations for the EMC CLARiiON
- Quorum disks on the EMC CLARiiON
- Advanced functions for the EMC CLARiiON
- Logical unit creation and deletion on the EMC
CLARiiON
- Configuring settings for the EMC CLARiiON
- Global settings for the EMC CLARiiON
- Controller settings for the EMC CLARiiON
- Port settings for the EMC CLARiiON
- LU settings for the EMC CLARiiON
- Configuring the EMC CLARiiON controller (Access Logix
not installed)
- Configuring the EMC Symmetrix
- Supported models of the EMC Symmetrix controller
- Supported firmware levels for the EMC Symmetrix
controller
- Concurrent maintenance on the EMC Symmetrix
- Sharing the EMC Symmetrix controller between
a host and the SAN Volume Controller
- Switch zoning limitations for the EMC Symmetrix
- Quorum disks on EMC Symmetrix
- Advanced functions for EMC Symmetrix
- Logical unit creation and deletion on EMC Symmetrix
- Configuration interface for the EMC Symmetrix
- Configuring settings for the EMC Symmetrix
- Global settings for the EMC Symmetrix
- Port settings for the EMC Symmetrix
- LU settings for the EMC Symmetrix
- Mapping and virtualization settings for the
EMC Symmetrix
- Configuring the Enterprise Storage Server
- Configuring the Enterprise Storage Server (ESS)
- Supported models of the ESS
- Supported firmware levels for the ESS
- Concurrent maintenance on the ESS
- Sharing the ESS between a host and the SAN Volume Controller
- Switch zoning limitations for the ESS
- Quorum disks on the ESS
- Advanced functions for the ESS
- Logical unit creation and deletion on the ESS
- Configuring the FAStT disk controller system
- Configuring FAStT disk controllers for the storage
server
- Support actions for the FAStT controller
- Supported models of the IBM FAStT controller
- Supported firmware levels for the FAStT
- Concurrent maintenance on the IBM FAStT
- Sharing the IBM FAStT controller between a host
and the SAN Volume Controller
- Quorum disks on the IBM FAStT
- Advanced functions for the IBM FAStT
- Data migration on an existing FAStT installation
which contains partitions
- Logical unit creation and deletion on the IBM
FAStT
- Configuration interface for the IBM FAStT
- Controller settings for the IBM FAStT
- Configuring settings for the IBM FAStT
- Global settings for the IBM FAStT
- LU settings for the IBM FAStT
- Miscellaneous settings for the IBM FAStT
- Mapping and virtualization settings for IBM
FAStT
- Configuring the HDS Thunder disk controller system
- Supported models of the HDS Thunder
- Supported firmware levels for HDS Thunder
- Concurrent maintenance on the HDS Thunder
- Sharing the HDS Thunder between host and the
SAN Volume Controller
- Setting up a Thunder with greater than 4 ports
- Quorum disks on HDS Thunder
- Advanced functions for HDS Thunder
- Logical unit creation and deletion on HDS Thunder
- Configuring settings for HDS Thunder
- Global settings for the HDS Thunder
- Controller settings for HDS Thunder
- Port settings for the HDS Tunder
- LU settings for the HDS Thunder
- Mapping and virtualization settings for HDS
Thunder
- Configuring the HDS Lightning disk controller system
- Supported models of the HDS Lightning
- Supported firmware levels for HDS Lightning
- Concurrent maintenance on the HDS Lightning
99xxV
- Sharing the HDS Lightning 99xxV between host
and the SAN Volume Controller
- Quorum disks on HDS Lightning 99xxV
- Advanced functions for HDS Lightning
- Configuring the HP StorageWorks subsystem
- HP StorageWorks definitions
- Configuring the HP StorageWorks controller
- HP StorageWorks controllers
- Supported models of the HP StorageWorks controller
- Supported firmware levels for the HP StorageWorks
controller
- Concurrent maintenance on the HP StorageWorks
- Sharing the HP StorageWorks controller between
a host and the SAN Volume Controller
- Switch zoning limitations for the HP StorageWorks
subsystem
- Quorum disks on HP StorageWorks
- Support for HP StorageWorks advanced functions
- HP StorageWorks advanced functions
- Logical unit creation and deletion on the HP
StorageWorks
- Configuring settings for the HP StorageWorks
- Global settings for the HP StorageWorks
- Configuration interface for the HP StorageWorks
- Controller settings for the HP StorageWorks
- Port settings for the HP StorageWorks
- LU settings for the HP StorageWorks
- Connection settings for the HP StorageWorks
- Mapping and virtualization settings for the
HP StorageWorks
- Renaming a storage subsystem
- Servicing storage subsystems
- Master console
- Configuring the master console
- Configuring the network
- Connecting to the Local Area Connection on the master
console
- Setting up the host name
- Configuring the browser
- Setting up Remote Support
- Firewall configuration
- Routing configuration
- Downloading the virtual network computing (VNC) server
- IBM Director
- Configuring IBM Director overview
- Configuring IBM Director for the SAN Volume Controller Call-Home
and Event Notification
- Call-Home
- Setting up an event action plan
- Setting up an e-mail
- Event notification
- Call-Home test
- Setting up an e-mail user notification
- Switches
- Switch zoning for the SAN Volume Controller
- Zoning considerations for Remote Copy
- Error logs
- Configuring error notification settings
- Clearing the Windows(TM) event
logs
- Web browsers
- Web browsers
- Prerequisites for creating a cluster using the SAN Volume Controller Console
- Configuring the browser
- Setting up SNMP traps
- Managing
- Copy Services
- FlashCopy mappings
- Creating FlashCopy mappings
- Deleting FlashCopy mappings
- Filtering FlashCopy mappings
- Modifying FlashCopy mappings
- Starting FlashCopy mappings
- Stopping FlashCopy mappings
- FlashCopy consistency groups
- Creating consistency groups
- Deleting FlashCopy consistency groups
- Filtering FlashCopy consistency groups
- Modifying FlashCopy consistency groups
- Starting FlashCopy consistency groups
- Stopping FlashCopy consistency groups
- Host considerations for FlashCopy integrity
- Preparing Windows volumes for FlashCopy
- Remote Copy relationships
- Creating relationships
- Filtering Remote Copy relationships
- Modifying relationships
- Deleting relationships
- Setting copy direction
- Starting Remote Copy relationships or consistency
groups
- Stopping Remote Copy relationships or consistency
groups
- Creating a synchronous copy
- Using the full synchronization-after-create method
- Using the synchronized-before-create method
- Using the quick synchronization-after-create method
- Remote Copy consistency groups
- Creating consistency groups
- Deleting Remote Copy consistency groups
- Filtering Remote Copy consistency groups
- Renaming a Remote Copy consistency group
- Starting Remote Copy relationships or consistency
groups
- Stopping Remote Copy relationships or consistency
groups
- Remote Copy partnerships
- Creating partnerships
- Modifying Remote Copy partnerships
- Deleting partnerships
- Clusters
- Adding a cluster
- Shutting down the cluster in the SAN Volume Controller
- Dumping cluster configurations
- Maintaining cluster passwords
- Maintain SSH keys
- Adding subsequent SSH public keys to the SAN Volume Controller
- Modifying Internet Protocol (IP) addresses
- Removing clusters
- Renaming a cluster
- Resetting the SSH fingerprint
- Resetting a refused SSH key
- Starting statistics collections
- Stopping statistics collections
- Copying statistics files from the cluster
- Shutting down a cluster or node
- Viewing the feature log
- Create cluster from the front panel
- Configuring a cluster using the SAN Volume Controller Console
- Increasing the size of your cluster using the SAN Volume Controller Console
- Adding a node to increase the size of your cluster
- Migrating a VDisk to a new I/O group
- Re-scanning the fibre-channel network for new
managed disks
- Disk Controller Systems
- Adding a new storage controller to a running configuration
using the SAN Volume Controller Console
- Changing a configuration for an existing storage
subsystem
- Removing a storage subsystem using the SAN Volume Controller Console
- Removing managed disks that represent de-configured
LUs
- Renaming a storage subsystem
- Determining a storage subsystem name from its SAN Volume Controller name
using the SAN Volume Controller Console
- Disks and disk groups
- Managed disks
- Viewing the mdisk status
- Filtering managed disks
- Discovering managed disks
- Including managed disks
- Renaming managed disks
- Setting quorum disks
- Showing managed disk group
- Showing virtual disks
- Determining the relationship between managed disks
and RAID arrays or LUNs using the SAN Volume Controller Console
- Managed disk groups
- Filtering managed disk groups
- Adding managed disks to managed disk groups
- Creating managed disk groups
- Deleting managed disk groups
- Removing managed disks from an MDisk group
- Renaming managed disk groups
- Showing virtual disks
- Virtual disks
- Viewing the vdisk status
- Filtering virtual disks
- Creating virtual disks
- Creating image-mode virtual disks
- Deleting virtual disks
- Expanding VDisks
- Expanding a Virtual disk that is mapped to an AIX
host
- Expanding a Virtual disk that is mapped to a Windows
2000 host
- Migrating virtual disks
- Shrinking virtual disks
- Virtual disk-to-host mappings
- Creating virtual disk-to-host mappings
- Deleting virtual disk-to-host mappings
- Determining the relationship between VDisks and MDisks
using the SAN Volume Controller Console
- Fibre-channel network speed
- Determining the fibre-channel port speed
- Changing the fibre-channel port speed for a node
not in a cluster
- Changing the fibre-channel port speed for a
node in a cluster
- Hosts
- Adding ports to a host
- Creating hosts
- Deleting hosts
- Deleting ports from a host
- Filtering hosts
- Renaming hosts
- Showing VDisks mapped to a host
- I/O groups
- Renaming input/output (I/O) Groups
- Master console
- Master console security overview
- Overview of passwords
- Starting the Tivoli SAN Manager
- Modifying your IBM Director settings
- Configuring the master console host name
- Nodes
- Adding nodes to a cluster
- Adding a node to the cluster using the CLI
- Adding a node to a cluster using the SAN Volume Controller Console application
on the master console
- Deleting a node from a cluster
- Deleting a node from the cluster using the CLI
- Deleting a node using the SAN Volume Controller Console application on the
master console
- Renaming a node
- Shutting down a node
- Fibre-channel network speed
- Determining the fibre-channel port speed
- Changing the fibre-channel port speed for a node
not in a cluster
- Changing the fibre-channel port speed for a
node in a cluster
- Determining the WWPNs for a node using the SAN Volume Controller Console
- Users
- Adding a superuser
- Adding users
- Changing passwords
- Deleting users
- Modifying users
- CIM Agent for the SAN Volume Controller
- Storage configuration
- Performing basic storage configuration
- Adding a candidate node to a cluster
- Creating a new storage pool
- Modifying a storage pool
- Creating a new storage volume
- Copy Services
- Creating a new FlashCopy relationship between storage
volumes
- Creating a FlashCopy relationship for a synchronized
set
- Creating a synchronous copy relationship between
volumes in the same cluster
- Creating a synchronous copy relationship between
volumes in different clusters
- LUN masking
- Performing LUN masking
- Advanced functions with the CLI
- Determining a nodes WWPNs using the CLI
- Determining a storage subsystem name from its SAN Volume Controller name
using the CLI
- Determining the VDisk name from the vpath number
on the host
- Determining the host that a VDisk is mapped to
- Determining the relationship between VDisks and MDisks
using the CLI
- Determining the relationship between MDisks and RAID
arrays or LUNs using the CLI
- Increasing the size of your cluster using the CLI
- Adding a node to increase the size of your cluster
using the CLI
- Migrating a VDisk to a new I/O group
- Replacing a faulty node in the cluster using the
CLI
- Recovering from offline VDisks after a node or an
I/O group failed using the CLI
- Recovering a node and including it back into the
cluster
- Moving offline VDisks to the recovery I/O group
- Moving offline VDisks to their original I/O group
using the CLI
- Replacing an HBA in a host using the CLI
- Adding a new storage controller to a
running configuration using the CLI
- Expanding a VDisk using the CLI
- Shrinking a VDisk using the CLI
- Migrating extents using the CLI
- Migrating VDisks between MDisk groups using the CLI
- Migrating a VDisk between I/O groups using the CLI
- Creating an image mode VDisk from an unmanaged MDisk
using the CLI
- Advanced function cluster overview using the
CLI
- Deleting a node from a cluster using the CLI
- Maintaining passwords using the CLI
- Modifying passwords using the CLI
- Maintaining SSH keys using the CLI
- Setting up error notifications using the CLI
- Modifying IP addresses using the CLI
- Listing log or dump files using the CLI
- Changing the language setting using the CLI
- Viewing the feature log using the CLI
- Analyzing the error log using the CLI
- Shutting down a cluster or single node using
the CLI
- Secure copy (SCP)
- Monitoring
- Clusters
- Viewing clusters
- Viewing general properties
- Viewing space properties
- Viewing Internet Protocol (IP) addresses
- Viewing Simple Network Management Protocol (SNMP)
properties
- Viewing statistics properties
- Retrieving statistics files
- Viewing feature settings and log
- Listing and saving log and dump files
- Displaying cluster properties using the SAN Volume Controller Console
- Copy Services
- FlashCopy
- FlashCopy mappings
- FlashCopy consistency groups
- Remote Copy
- Remote Copy relationships
- Viewing general details
- Remote Copy consistency groups
- Viewing general details
- Remote Copy Partnerships
- Disk Controller Systems
- Checking disk controller status
- Viewing general details
- Viewing port details
- Disks and Disk groups
- Managed disks
- Listing managed disks
- Including managed disks
- Checking managed disk group status
- Viewing general details
- Managed disk groups
- Viewing general details
- Virtual disks
- Viewing general details
- Hosts
- Viewing general details
- Viewing port details
- Viewing input/output (I/O) groups
- Nodes
- Viewing general details
- Node identification
- Checking the status of the node
- Checking the status of the node ports
- Viewing port details
- Viewing vital product data
- Displaying the VPD
- Viewing the node status using the SAN Volume Controller Console application
on the master console
- Listing and saving dump data
- Viewing users
- Virtual disk-to-host mappings
- Viewing the error log using the SAN Volume Controller Console application
on the master console
- Maintaining
- Backing up and restoring the cluster configuration
- Backing up the cluster configuration
- Restoring the cluster configuration
- Deleting a backup configuration file
- Maintenance procedures
- Starting maintenance using the SAN Volume Controller Console application
on the master console
- Enabling concurrent maintenance
- Using directed maintenance procedures
- Performing the cluster maintenance procedure using
the CLI
- Checking the grounding of the SAN Volume Controller and
the uninterruptible power supply
- Checking the labels on the outside of the uninterruptible
power supply
- Checking the safety labels on the SAN Volume Controller
- Enabling the cluster maintenance procedure using
the SAN Volume Controller Console
- Power-on self-tests (POSTs)
- Marking errors as fixed
- Removing parts
- Preparing to remove and replace parts
- Removing a SAN Volume Controller from a rack
- Removing the uninterruptible power supply
- Removing the support rails for an uninterruptible
power supply
- Removing the support rails for a SAN Volume Controller
- Removing the front panel from the SAN Volume Controller
- Removing the top cover from the SAN Volume Controller
- Removing the service controller from the SAN Volume Controller
- Removing the service controller cables
- Removing the disk drive
- Removing the disk drive cables
- Removing the disk drive fan
- Removing the microprocessor fan
- Removing the power from the SAN Volume Controller
- Removing the power from the uninterruptible power
supply
- Removing the SAN Volume Controller power supply
- Removing the uninterruptible power supply battery
- Removing and replacing the system board CMOS battery
- Removing the memory modules
- Removing an adapter
- Removing the system board
- Removing the uninterruptible power supply electronics
- Removing a version of the software
- Replacing objects
- Replacing an HBA in a host using the SAN Volume Controller Console
- Replacing a faulty node with a spare node using the SAN Volume Controller Console
- Replacing the uninterruptible power supply
- Replacing the front panel on the SAN Volume Controller
- Replacing the top cover on the SAN Volume Controller
- Replacing a disk drive and a service controller
- Replacing an adapter
- Support rails for the SAN Volume Controller
- Replacing the fibre-channel cable or GBICs
- Recovering from software installation failures
- Performing the node rescue
- Recovering from offline VDisks after a node or an
I/O group failed
- Recovering a node and including it back into the
cluster
- Moving offline VDisks to the recovery I/O group
- Moving offline VDisks to their original I/O group
- Recovering from offline VDisks after a node or an
I/O group failed using the CLI
- Recovering a node and including it back into the
cluster
- Moving offline VDisks to the recovery I/O group
- Moving offline VDisks to their original I/O group
using the CLI
- Rewriting the SAN Volume Controller serial number
- Removing a storage subsystem using the CLI
- Software upgrade strategy
- Upgrading software on the master console
- Obtaining the software packages
- Upgrading the SAN Volume Controller firmware using the SAN Volume Controller Console
- Installing the upgrade using the CLI
- Disruptive software upgrade
- Recovering from software installation failures
- Manual recovery from software upgrade problems
- Automatic recovery from upgrade problems
- Determining the version of the software
- Removing a version of the software
- Automatic upgrade
- Maintaining cluster passwords using the SAN Volume Controller Console
- Reinstalling the preinstalled software
- Obtaining the software packages
- Determining the version of the software
- Removing a version of the software
- Maintaining the master console
- Performing software recovery
- Recovering from a master console disk drive failure
- Viewing error information on the master console
- Troubleshooting
- Analyzing the error log
- Understanding the error codes
- Using the error code tables
- Managing the error log
- Viewing the error log
- Describing the fields in the error log
- Error reporting
- Determining the failing enclosure or disk controller
- Determining a hardware boot failure
- Using directed maintenance procedures
- Using the MAPs
- MAP 5000: Start
- MAP 5100: Power
- MAP 5200: Uninterruptible power supply
- MAP 5300: Uninterruptible power supply repair verification
- MAP 5400: Front panel
- MAP 5500: Ethernet
- MAP 5600: Fibre-channel
- MAP 5700: Repair verification
- SAN problem determination
- Recovering from a Disruptive Software Upgrade
- Re-establishing contact with a cluster when the
network goes down
- Replacing expired LDAP and CIMOM certificates in
the truststore file
- Starting the CIM object manager (CIMOM) trace log
- SAN Volume Controller Console
- CIM Object Manager (CIMOM)
- Troubleshooting master console problems
- Ensuring that TsanM Netview information is not
lost
- Recovering from a voltage-sensor error message
- Connecting to the Remote Support
Center
- Resolving Windows 2000 boot problem
- Recovering from SAN Volume Controller Console signing off
- Reference
- User interface panels for the SAN Volume Controller Console
- Copy Services
- Managing FlashCopy mappings
- Creating FlashCopy mappings
- Deleting FlashCopy mappings
- Filtering FlashCopy mappings
- Modifying FlashCopy mappings
- Starting FlashCopy mappings
- Confirming the start of a FlashCopy mapping
- Confirming the preparation of a FlashCopy mapping
- Stopping FlashCopy mappings
- Viewing FlashCopy mappings
- Managing FlashCopy consistency groups
- Creating FlashCopy consistency groups
- Deleting FlashCopy consistency groups
- Filtering FlashCopy consistency groups
- Renaming FlashCopy consistency groups
- Starting FlashCopy consistency groups
- Stopping FlashCopy consistency groups
- Viewing FlashCopy consistency groups
- Managing Remote Copy relationships
- Creating Remote Copy relationships
- Introducing the Creating a Remote Copy Relationship
wizard
- Selecting the Auxiliary Cluster
- Filtering Master VDisk Candidates
- Selecting the Master VDisk
- Selecting the Auxiliary Virtual Disk
- Selecting options for Remote Copy relationship
- Verifying Remote Copy Relationship
- Filtering Remote Copy relationships
- Modifying Remote Copy relationships
- Deleting Remote Copy relationships
- Switching the direction of a Remote Copy consistency
group or a Remote Copy relationship
- Starting Remote Copy relationships or consistency
groups
- Stopping Remote Copy relationships or consistency
groups
- Remote Copy relationships
- Viewing general details
- Creating a synchronous copy
- Using the full synchronization-after-create method
- Using the synchronized-before-create method
- Using the quick synchronization-after-create method
- Managing Remote Copy consistency groups
- Creating Remote Copy consistency groups
- Introduction
- Selecting Auxiliary Cluster
- Adding Remote Copy Relationships
- Verifying Settings
- Deleting Remote Copy consistency groups
- Filtering Remote Copy consistency groups
- Renaming Remote Copy consistency groups
- Starting Remote Copy relationships or consistency
groups
- Stopping Remote Copy relationships or consistency
groups
- Remote Copy consistency groups
- Viewing general details
- Managing Remote Copy partnerships
- Creating Remote Copy partnerships
- Modifying Remote Copy partnerships
- Deleting Remote Copy partnerships
- Remote Copy cluster partnerships
- Clusters
- Cluster
- Identifying a cluster
- Analyzing the error logs
- Configuring error notification settings
- Backing up a cluster configuration
- Restoring a cluster configuration
- Deleting a backup cluster configuration file
- Dumping the cluster configuration
- Maintaining SSH public keys
- Modify Internet Protocol (IP) addresses
- Removing a cluster
- Renaming cluster
- Resetting the SSH fingerprint
- Setting cluster time
- Viewing space capacity information
- Starting statistics collection
- Stopping statistics collection
- Shutting down the cluster
- Software upgrades
- View feature log
- Viewing clusters
- Viewing general properties
- Viewing space properties
- Viewing Internet Protocol (IP) addresses
- Viewing Remote Copy properties
- Viewing Simple Network Management Protocol (SNMP)
properties
- Viewing statistics properties
- Updating feature settings
- Viewing the feature settings
- Listing log and dump files
- Hosts
- Adding ports to host objects
- Creating a host object
- Deleting hosts objects
- Deleting ports from a host object
- Confirming the forced deletion of ports
- Filtering host objects
- Renaming a host
- Viewing Hosts
- Viewing general details
- Viewing port details
- I/O groups
- Renaming input/output (I/O) groups
- Viewing Input/Output (I/O) groups
- Disk Controller Systems
- Renaming a Disk Controller System
- Viewing general details
- Viewing Port Details
- Disks and Disk groups
- Managed disks (MDisks)
- Filtering managed disks (MDisks)
- Discovering managed disks
- Including managed disk (MDisks)
- Renaming managed disks (MDisks)
- Setting a quorum disk
- Showing virtual disks (VDisks)
- Viewing managed disks (MDisks)
- Viewing Managed Disk Details
- Managed disk (MDisk) groups
- Filtering managed disk groups
- Adding managed disks to a Managed Disk group
- Creating a managed disk group
- Introduction
- Create a managed disk group
- Selecting extent size
- Verifying attributes
- Deleting a managed disk (MDisk) group
- Forcing the deletion of a managed disk (MDisk) group
confirmation
- Deleting managed disks (MDisks) from managed disk
group
- Confirming the deletion of a managed disk (MDisk)
from an MDisk group
- Renaming managed disk (MDisk) groups
- Showing managed disks (MDisks) in this group
- Showing virtual disks (VDisks) in a managed disk
(MDisk) group
- Viewing managed disk groups
- Viewing managed disk (MDisk) group details
- Virtual disks (VDisks)
- Filtering virtual disks (VDisks)
- Creating virtual disks wizard
- Introduction
- Create a managed disk group
- Selecting extent size
- Selecting groups
- Select type and quantity
- Name the virtual disk
- Setting attributes for virtual disks
- Setting the attributes for striped virtual disks
- Setting attributes for an image-mode virtual disk
- Verifying attributes
- Deleting a virtual disk (VDisk)
- Confirming the forced deletion of a virtual disk
(VDisk)
- Expanding virtual disks (VDisks)
- Migrating virtual disks (VDisks)
- Modify virtual disks (VDisks)
- Shrinking virtual disks (VDisks)
- Viewing virtual disks (VDisks)
- Viewing virtual disk (VDisk) details
- Nodes
- Node
- Adding a node to a cluster
- Deleting a node
- Confirming the deletion of a node
- Renaming nodes
- Shutting down the node
- Confirming the forced shut down of a node
- Viewing Nodes
- Viewing general details
- Viewing port details
- Viewing vital product data
- Users
- Adding a superuser
- Adding users
- Changing a password
- Deleting users
- Modifying users
- Viewing users
- Virtual disk-to-host mappings
- Filtering Virtual Disks-to-Host Mappings
- Creating virtual disk (VDisk)-to-host mapping
- Deleting a virtual disk-to-host mapping
- Viewing VDisk-to-host mappings
- Confirming the deletion of a virtual disk-to-host
mapping
- CIM Agent for the SAN Volume Controller
- Functional views of the CIM Agent
- CIM base elements
- CIM logical elements
- Logical device mapping
- CIM service elements
- CIM system elements
- Clustering service
- Storage configuration service
- LUN masking
- Copy services
- Security service
- Settings for a new volume
- CIM Agent object classes
- Core object classes
- IBMTS2145_AccessControlInformation
- IBMTS2145_BackendController
- IBMTS2145_BackendVolume
- IBMTS2145_CandidateCluster
- IBMTS2145_CandidateHardwareAccount
- IBMTS2145_CandidateNode
- IBMTS2145_CandidateVolume
- IBMTS2145_Chassis
- IBMTS2145_Cluster
- IBMTS2145_Controller
- IBMTS2145_FCPort
- IBMTS2145_Features
- IBMTS2145_FlashCopySynchronizedSet
- IBMTS2145_HardwareAccount
- IBMTS2145_Host
- IBMTS2145_Job
- IBMTS2145_Node
- IBMTS2145_NodeVPD
- IBMTS2145_Product
- IBMTS2145_RedundancyGroup
- IBMTS2145_RemoteCluster
- IBMTS2145_RemoteVolume
- IBMTS2145_StoragePool
- IBMTS2145_StorageSettingPool
- IBMTS2145_StorageSettingVolume
- IBMTS2145_StorageVolume
- IBMTS2145_SyncCopySynchronizedSet
- IBMTS2145_TimeZone
- Service object classes
- IBMTS2145_AccountManagementService
- IBMTS2145_AuthorizationService
- IBMTS2145_ClusteringService
- IBMTS2145_FilteringService
- IBMTS2145_StorageConfigurationService
- Security object classes
- IBMTS_Account
- IBMTS_AccountManagementService
- IBMTS_ObjectManager
- Association object classes
- IBMTS2145_AccountManagementServiceForSystem
- IBMTS2145_AccountOnSystem
- IBMTS2145_AllocatedFromStoragePool
- IBMTS2145_AuthorizationServiceForSystem
- IBMTS2145_AuthorizationSubject
- IBMTS2145_AuthorizationTarget
- IBMTS2145_AuthorizedUse
- IBMTS2145_AvailableAccount
- IBMTS2145_AvailableTimeZone
- IBMTS2145_BackendSCSILUN
- IBMTS2145_BasedOn
- IBMTS2145_ClusteringCandidate
- IBMTS2145_ClusteringServiceForSystem
- IBMTS2145_ClusterScopeACI
- IBMTS2145_ClusterScopeCandidateCluster
- IBMTS2145_ClusterScopeCandidateVolume
- IBMTS2145_ClusterScopeChassis
- IBMTS2145_ClusterScopeController
- IBMTS2145_ClusterScopeFCPort
- IBMTS2145_ClusterScopeFCSet
- IBMTS2145_ClusterScopeHost
- IBMTS2145_ClusterScopeNodeVPD
- IBMTS2145_ClusterScopeProduct
- IBMTS2145_ClusterScopeRedgroup
- IBMTS2145_ClusterScopeRemoteCluster
- IBMTS2145_ClusterScopeSCSet
- IBMTS2145_ClusterScopeVolume
- IBMTS2145_ComputerSystemPackage
- IBMTS2145_ConnectedBackendController
- IBMTS2145_ControllerFCPort
- IBMTS2145_ControllerView
- IBMTS2145_CopyCandidate
- IBMTS2145_CurrentTimeZone
- IBMTS2145_FilteringServiceForSystem
- IBMTS2145_FlashCopyStorageSynchronized
- IBMTS2145_FlashCopySynchronizedMember
- IBMTS2145_HostedAccount
- IBMTS2145_HostedACI
- IBMTS2145_HostedJob
- IBMTS2145_HostedStoragePool
- IBMTS2145_ManagesAccount
- IBMTS2145_ParticipatingCS
- IBMTS2145_ProductPhysicalComponent
- IBMTS2145_RedundancyComponent
- IBMTS2145_RemoteSystemVolume
- IBMTS2145_SCSILUN
- IBMTS2145_StorageConfigurationServiceForSystem
- IBMTS2145_StoragePoolComponent
- IBMTS2145_SyncCopyStorageSynchronized
- IBMTS2145_SyncCopySynchronizedMember
- IBMTS2145_SystemBackendVolume
- IBMTS2145_SystemController
- IBMTS2145_SystemFCPort
- IBMTS2145_SystemFeatures
- IBMTS2145_SystemVolume
- IBMTS2145_SystemVPD
- IBMTS_AccountManagementServiceForSystem
- IBMTS_AccountOnCIMOM
- IBMTS_AccountOnSystem
- IBMTS_ManagesAccount
- CIM Agent methods
- Intrinsic methods
- Associators()
- AssociatorNames()
- CreateInstance()
- DeleteInstance()
- EnumerateClasses()
- EnumerateClassNames()
- EnumerateInstances()
- EnumerateInstanceNames()
- ExecQuery()
- GetClass()
- GetInstance()
- GetProperty()
- ModifyInstance()
- References()
- ReferenceNames()
- SetProperty()
- Extrinsic methods
- AddNode()
- AddNodeToRedundancyGroup()
- AssignAccess()
- AttachDevice()
- CreateAccount()
- CreateFlashCopySynchronization()
- CreateHardwareAccount()
- CreateOrModifyStoragePool()
- CreateOrModifyElementFromStoragePool()
- CreateRemoteClusterPartnership()
- CreateReplica()
- CreateSynchronization()
- CreateSynchronizedSet()
- CreateSyncCopySynchronization()
- CreateSyncCopySynchronizedSet()
- CreateView()
- DeleteAccount()
- DeleteHardwareAccount()
- DeleteRemoteClusterPartnership()
- DeleteSynchronization()
- DeleteSynchronizedSet()
- DeleteStoragePool()
- DeleteView()
- DumpConfiguration()
- EvictNode()
- ForcedDeleteFlashCopySynchronization()
- ForcedDeleteFlashCopySynchronizedSet()
- ForcedDeleteHardwareAccount()
- ForcedDeleteStoragePool()
- ForcedDeleteSyncSynchronizedSet()
- ForcedReturnToStoragePool()
- GetResetPasswordChangeFeatureStatus()
- GetSupportedSizeRange()
- GrantGlobalAccess()
- GrantSystemAccess()
- IncludeBackendVolume()
- MigrateVolume()
- ModifyResetPasswordChangeFeature()
- ModifySynchronization()
- ModifySynchronizedSet()
- ModifySyncCopySynchronization()
- ModifySyncCopySynchronizedSet()
- RemoveAccess()
- RemoveDevice()
- RequestDiscovery()
- ReturnToStoragePool()
- SetLocale()
- SetPassword()
- SetPasswords()
- SetQuorum()
- SetRedundancyGroup()
- SetTimeZone()
- StartStatisticsCollection()
- StopStatisticsCollection()
- Shutdown()
- CLI commands
- Syntax diagrams
- Using wildcards in the SAN Volume Controller
Command-Line Interface (CLI)
- Data types and value ranges
- Terminology
- CLI flags
- CLI parameters
- Emphasis
- CLI special characters
- Overview of the list dump commands
- Attributes of the -filtervalue argument
- Cluster commands
- addnode
- chcluster
- chiogrp
- chnode
- cleardumps
- cpdumps
- detectmdisk
- dumpconfig
- rmnode
- setclustertime
- setpwdreset
- settimezone
- startstats
- stopcluster
- stopstats
- Backup and restore commands
- backup
- clear
- help
- restore
- Cluster diagnostic and service-aid commands
- addnode
- applysoftware
- cherrstate
- clearerrlog
- dumperrlog
- finderr
- rmnode
- setevent
- setlocale
- writesernum
- Host commands
- addhostport
- chhost
- mkhost
- rmhost
- rmhostport
- Virtual disk commands
- chvdisk
- expandvdisksize
- mkvdisk
- mkvdiskhostmap
- rmvdisk
- rmvdiskhostmap
- shrinkvdisksize
- Managed disk group commands
- addmdisk
- chmdiskgrp
- mkmdiskgrp
- rmmdisk
- rmmdiskgrp
- Managed disk commands
- chmdisk
- includemdisk
- setquorum
- FlashCopy commands
- chfcconsistgrp
- chfcmap
- mkfcconsistgrp
- mkfcmap
- prestartfcconsistgrp
- prestartfcmap
- rmfcconsistgrp
- rmfcmap
- startfcconsistgrp
- startfcmap
- stopfcconsistgrp
- stopfcmap
- Remote Copy commands
- chpartnership
- chrcconsistgrp
- chrcrelationship
- mkpartnership
- mkrcconsistgrp
- mkrcrelationship
- rmpartnership
- rmrcconsistgrp
- rmrcrelationship
- startrcconsistgrp
- startrcrelationship
- stoprcconsistgrp
- stoprcrelationship
- switchrcconsistgrp
- switchrcrelationship
- Migration commands
- migrateexts
- migratevdisk
- Tracing commands
- setdisktrace
- settrace
- starttrace
- stoptrace
- Information commands
- caterrlog
- caterrlogbyseqnum
- ls2145dumps
- lscluster
- lsclustercandidate
- lsconfigdumps
- lscontroller
- lserrlogbyfcconsistgrp
- lserrlogbyfcmap
- lserrlogbyhost
- lserrlogbyiogrp
- lserrlogbymdisk
- lserrlogbymdiskgroup
- lserrlogbynode
- lserrlogbyrcconsistgrp
- lserrlogbyrcrelationship
- lserrlogbyvdisk
- lserrlogdumps
- lsfcconsistgrp
- lsfcmap
- lsfcmapcandidate
- lsfcmapprogress
- lsfeaturedumps
- lsfreeextents
- lshbaportcandidate
- lshost
- lshostvdiskmap
- lsiogrp
- lsiogrpcandidate
- lsiostatsdumps
- lsiotracedumps
- lslicense
- lsmdisk
- lsmdiskcandidate
- lsmdiskextent
- lsmdiskgrp
- lsmdiskmember
- lsmigrate
- lsnode
- lsnodecandidate
- lsnodevpd
- lsrcconsistgrp
- lsrcrelationship
- lsrcrelationshipcandidate
- lsrcrelationshipprogress
- lssoftwaredumps
- lssshkeys
- lstimezones
- lsvdisk
- lsvdiskextent
- lsvdiskhostmap
- lsvdiskmember
- lsvdiskprogress
- showtimezone
- Error log commands
- finderr
- dumperrlog
- clearerrlog
- cherrstate
- setevent
- Featurization commands
- chlicense
- dumpinternallog
- Secure shell (SSH) key commands
- addsshkey
- rmallsshkeys
- rmsshkey
- Service mode commands
- applysoftware
- cleardumps
- dumperrlog
- exit
- Service mode information commands
- ls2145dumps
- lsclustervpd
- lsconfigdumps
- lserrlogdumps
- lsfeaturedumps
- lsiostatsdumps
- lsiotracedumps
- lsnodes
- lsnodevpd
- lssoftwaredumps
- Controller command
- chcontroller
- Messages and codes
- CIMOM messages
- CMMVC1000I The job completed successfully.
- CMMVC4000W Select a row from the table.
- CMMVC8000E There was an unexpected error.
- CMMVC8001E The job failed.
- CMMVC8002E The parameter is not valid.
- CMMVC8003E A time-out occurred.
- CMMVC8004E An unknown error occurred.
- CMMVC8005E The action is not supported.
- CMMVC8006E The name is not valid.
- CMMUI8000E Unexpected error. Run the task again. If the problem continues, contact
your service representative.
- CMMUI8100E Field field_name cannot be empty.
- CMMUI8101E Field field_name must be numeric.
- CMMUI8102E Field field_name must be between
minimum_value and maximum_value.
- CMMUI8103E Field field_name must be less than
maximum_value.
- CMMUI8104E Field field_name must be greater than or
equal to minimum_value.
- CMMUI8105E Field field_name must be exactly
field_length characters long.
- CMMUI8106E Field field_name must be less than
maximum_length characters long.
- CMMUI8107E Field field_name must be at least
minimum_length characters long.
- CMMUI8108E Field field_name must be between
minimum_length and maximum_length characters
long.
- CMMUI8109E Field field_name must be an integer.
- CMMUI8200E You must enter a user name.
- CMMUI8201E You must enter a password.
- CMMUI8202E You must enter a user name and a password.
- CMMUI8203E The administrative server could not authenticate the user name.
- CMMUI8204E The user name you entered does not exist.
- CMMUI8205E The password you entered is not valid.
- CMMUI8300E An unexpected error occurred when accessing the CIM agent.
- CMMUI8301E The user name or password is not valid. The CIM agent could not
authenticate the user name.
- CMMUI8302E The Administrative server could not connect to the CIM agent. It
might be down.
- CMMUI8303E The Administrative server is unable to access the truststore file.
- CMMUI8304E The Administrative server is unable to find a valid certificate in
the truststore file.
- CMMUI8305E The user role for this user name is undefined.
- SAN Volume Controller Console Messages
- CMMVC1050I The specified dump file was successfully saved.
- CMMVC1051I The error log was successfully cleared.
- CMMVC1052I The features were successfully changed.
- CMMVC1056I The configuration was successfully restored.
- CMMVC1057I The backup file was successfully created.
- CMMVC1100I The candidate nodes are not available.
- CMMVC1101W There is no I/O group available to add the node to.
- CMMVC1300I No new managed disks were discovered.
- CMMVC1301I One or more new managed disks were discovered.
- CMMVC1501I You have asked to stop a FlashCopy consistency group.
- CMMVC1600I The cluster does not have a remote cluster partner.
- CMMVC3000I Checking that a valid cluster IP address has been entered.
- CMMVC3200W Are you sure you want to remove the following cluster?
- CMMVC3201W Do you want to reset the SSH fingerprint stored in the Windows registry
for the following cluster?
- CMMVC3300W Are you sure you want to delete the following user?
- CMMVC3400E The IP address entered is not valid.
- CMMVC3401E Select the cluster that you want to delete.
- CMMVC3402E Select the cluster where you want to launch the svcc.
- CMMVC3403E No cluster was found at the specified IP address.
- CMMVC3404E There was an error when configuring the CIM Agent for the svc.
- CMMVC3405E There was an error when restarting the CIM Agent for the svc.
- CMMVC3406E The configuration file for the CIM Agent for the svc was not found.
- CMMVC3407E There was an error when resetting the CIM Agent for the svc.
- CMMVC3408E The specified cluster already exists.
- CMMVC3409E The specified cluster is unavailable.
- CMMVC3410E No fingerprint entry was found in the Windows registry.
- CMMVC3411E Error occurred deleting fingerprint entry from the Windows registry.
- CMMVC3412E Select the cluster whose SSH fingerprint you want to delete.
- CMMVC3436E Select one cluster that you want to rename.
- CMMVC3437E Select the cluster whose SSH configuration you want to change.
- CMMVC3500E Select the user that you want to delete.
- CMMVC3501E Select the user that you want to modify.
- CMMVC3502E The user name entered is not valid.
- CMMVC3503E The password entered is not valid.
- CMMVC3504E You cannot delete a user name that you are currently using.
- CMMVC3505E The specified user already exists.
- CMMVC3506E No clusters have been selected.
- CMMVC3507E No clusters are configured.
- CMMVC3508E The default password was entered.
- CMMVC3509E Select a non-superuser to modify.
- CMMVC3510E The password entered is not valid. The length of the password is
not valid.
- CMMVC3511E The password entered is not valid. It contains characters that are
not valid.
- CMMVC3512E The password entered is not valid. The password and re-entered password
do not match.
- CMMVC3800E There was an error when resetting the node. Enable the trace log
and run the task again. If the problem continues, contact your service representative.
- CMMVC3801E A node is missing in the redundancy group. Enable the trace log and
run the task again. If the problem continues, contact your service representative.
- CMMVC4020W Are you sure you want to stop the collection of statistics?
- CMMVC4021W Are you sure you want to shut down the following cluster?
- CMMVC4025W Are you sure that you want to restore the cluster configuration?
- CMMVC4026W Are you sure that you want to delete all of the backup configuration
files?
- CMMVC4027W The backup operation ended with errors and warnings.
- CMMVC4028W The preparation phase of the restore ended with warnings.
- CMMVC4040W Attention: You have asked to deleteremove the last node in this cluster.
- CMMVC4041W The shutdown failed.
- CMMVC4042W You are about to shut down the last node in the cluster.
- CMMVC4043W If you are re-adding this node to the SAN, ensure that you are adding
the node to the same I/O Group it was removed from. Failure to do this can
result in data corruption. Utilize the information that was recorded when
the node was originally added to the cluster. If you do not have access to
this information, call IBM Service to add the node back onto the cluster without
corrupting data. If you are adding the node into the cluster for the first
time, please record the node serial number, WWNN, all WWPNs, and the I/O Group
to which it has been added.
- CMMVC4044W Are you sure that you want to delete the following node? Before you
do, record the node serial number, WWNN, all WWPNs, and the I/O group that
currently contains it. This can avoid a possible data corruption exposure
if the node must be re-added to the cluster.
- CMMVC4140W The deletion failed because there are virtual disk-to-host mappings
for this host.
- CMMVC4141W Are you sure you want to delete the following ports from their host?
- CMMVC4142W Are you sure you want to delete the following port or ports from
their host?
- CMMVC4160W The deletion failed.
- CMMVC4200W Prepare FlashCopy Mappings
- CMMVC4201W Are you sure you want to stop the following FlashCopy consistency
group?
- CMMVC4202W The deletion failed because this consistency group still contains
FlashCopy Mappings.
- CMMVC4240W The deletion failed because there are Remote Copy relationships that
belong to this consistency group.
- CMMVC4241W To create Remote Copy relationships between virtual disks on two
different clusters, you must create a partnership on both clusters. Click
Create to create a cluster partnership.
- CMMVC5006E The name is not valid.
- CMMVC5007E The name is not valid.
- CMMVC5050E The cluster failed to shutdown.
- CMMVC5051E The value entered is not correct.
- CMMVC5052E The start statistics operation failed.
- CMMVC5053E The locale is not valid.
- CMMVC5054E The stop statistics operation failed.
- CMMVC5055E The dump of the cluster failed.
- CMMVC5056E Select a dump file.
- CMMVC5057E The specified dump file was not saved.
- CMMVC5058E The specified dump file could not be retrieved.
- CMMVC5059E The specified dump file was not deleted.
- CMMVC5060E All of the dump files were not deleted.
- CMMVC5061E The dump associated with the cluster could not be loaded.
- CMMVC5062E The error log associated with the cluster could not be loaded.
- CMMVC5063E The error log does not exist.
- CMMVC5064E The number of entries that was specified is not valid.
- CMMVC5065E The FlashCopy feature was not modified.
- CMMVC5066E The Remote Copy feature was not modified.
- CMMVC5067E The virtualization setting was not set.
- CMMVC5068E The virtualization limit must be set to a number greater than 0.
- CMMVC5069E The IP address entered is not valid.
- CMMVC5070E The file prefix for the configuration dump is not valid.
- CMMVC5072E The IP address was not modified because of an error.
- CMMVC5075E The feature log was not retrieved because an unexpected error occurred.
- CMMVC5076E The error notification setting was not changed.
- CMMVC5077E The file path of the software package has to be entered.
- CMMVC5078E The software was not upgraded.
- CMMVC5079E The code level of the currently installed software could not be retrieved.
- CMMVC5080E The feature log could not be retrieved.
- CMMVC5081E The selected entry in the error log was not marked as fixed or unfixed
because this type flag does not permit this.
- CMMVC5083E The backup configuration file was not deleted.
- CMMVC5084E There is no backup cluster configuration to delete.
- CMMVC5085E There is no backup cluster configuration to restore.
- CMMVC5086E The preparing phase of the restore ended with errors and warnings.
- CMMVC5087E The backup cluster configuration was not restored.
- CMMVC5088E The configuration was not backed up because of errors and warnings.
- CMMVC5089E No backup configuration file can be found.
- CMMVC5090E The restore failed because the backup script could not be uploaded
to the cluster.
- CMMVC5091E The backup failed because the backup script could not be downloaded
from the cluster.
- CMMVC5100E Select a node to delete
remove.
- CMMVC5101E Select a node to rename.
- CMMVC5102E Select a node to shutdown.
- CMMVC5103E The node was not renamed.
- CMMVC5104E The node was not deleted
removed.
- CMMVC5105E The node was not shut down.
- CMMVC5150E Select an I/O group to rename.
- CMMVC5151E The I/O group was not renamed.
- CMMVC5201E Select a disk controller system to rename.
- CMMVC5202E The disk controller system was not renamed.
- CMMVC5250E Select an MDisk group to delete.
- CMMVC5251E Select an MDisk group to rename.
- CMMVC5252E Select an MDisk group to add MDisks.
- CMMVC5253E Select an MDisk group to remove MDisks from.
- CMMVC5254E The MDisk group was not renamed.
- CMMVC5255E The MDisk group was not created.
- CMMVC5256E The MDisks were not deleted.
- CMMVC5257E The MDisks were not added to the MDisk group.
- CMMVC5258E The name entered is not valid.
- CMMVC5259E Select at least one MDisk to create an MDisk group.
- CMMVC5260E Select an MDisk group to view managed disks.
- CMMVC5261E Select an MDisk group to view virtual disks.
- CMMVC5262E There are no MDisks to remove.
- CMMVC5263E Select an MDisk to add to the MDisk group or click Cancel to return.
- CMMVC5264E Select an MDisk to remove or click Cancel to return.
- CMMVC5265E The maximum number MDisks for a MDisk Group is 128
- CMMVC5266E No candidate MDisks available.
- CMMVC5300E Select an MDisk to rename.
- CMMVC5301E Select an MDisk, with a mode of managed, to assign as a quorum disk.
- CMMVC5302E Select an MDisk to include in the cluster.
- CMMVC5303E Select an MDisk to show group information.
- CMMVC5304E The MDisk was not renamed.
- CMMVC5305E The Show MDisk group command failed.
- CMMVC5306E The Set quorum disk command failed.
- CMMVC5307E The Include MDisk command failed.
- CMMVC5308E The Discover MDisks command failed.
- CMMVC5309E The managed disk (MDisk) group is not available.
- CMMVC5310E Virtual disks for the selected MDisk are not available.
- CMMVC5311E Select an MDisk to show the virtual disk.
- CMMVC5312E Select an unmanaged MDisk to create an image-mode VDisk.
- CMMVC5313E The name entered is not valid.
- CMMVC5350E Select a host.
- CMMVC5351E Select or specify at least one port.
- CMMVC5352E A host with no ports attached to it cannot be deleted with the svcc.
- CMMVC5353E A worldwide port name (WWPN) is not valid.
- CMMVC5354E The additional WWPN port number is not valid.
- CMMVC5355E The host has no ports that can be deleted.
- CMMVC5356E Unable to create a host because duplicate worldwide port names (WWPN)
were defined.
- CMMVC5357E Unable to add ports to the host because duplicate worldwide port
names (WWPN) were defined.
- CMMVC5400E Select one virtual disk.
- CMMVC5401E Enter a valid capacity.
- CMMVC5402E Specify at least one I/O group and MDisk Group to continue.
- CMMVC5403E Enter a valid virtual disk name.
- CMMVC5404E Enter a valid host name.
- CMMVC5405E Specify at least one logical unit number (LUN) ID is needed to continue.
- CMMVC5406E Specify one host to continue.
- CMMVC5407E The logical unit number (LUN) was not mapped.
- CMMVC5408E The virtual disk-to-host mapping was not deleted.
- CMMVC5409E Try to delete the virtual disk (VDisk) using the Force option.
- CMMVC5410E The small computer system interface (SCSI) LUN ID that was entered
is not valid.
- CMMVC5411E Select at least one MDisk.
- CMMVC5412E The I/O group was not renamed.
- CMMVC5413E The capacity must be smaller than the current capacity.
- CMMVC5414E The capacity must be larger than the current capacity.
- CMMVC5415E The I/O governing rate is not valid.
- CMMVC5416E Specify at least one managed disk to continue.
- CMMVC5417E The selected I/O group does not have a node associated with it.
- CMMVC5418E Entered capacity is larger than the available space in the MDisk
Group.
- CMMVC5419E The virtual disk-to-host mapping failed.
- CMMVC5420E The selected host doesn't have a hardware account.
- CMMVC5421E There are no hosts available for the selected virtual disk or disks.
- CMMVC5422E The number entered is not valid. Enter a number between 1 and 1024.
- CMMVC5423E Select one or more VDisks.
- CMMVC5424E The number of selected MDisks is not equal to the number of VDisks
to be created.
- CMMVC5425E The maximum number of virtual disks has been reached.
- CMMVC5426E Select an MDisk to create an image-mode virtual disk.
- CMMVC5427E There are no managed disks in the cluster that have a mode of unmanaged.
Therefore, you cannot create an image-mode virtual disk.
- CMMVC5450E Select one source virtual disk and one target virtual disk.
- CMMVC5451E The source virtual disk and target virtual disk cannot be the same
virtual disk.
- CMMVC5452E The FlashCopy mapping was not prepared or started because the mapping
is not in the expected state. The mapping must be stopped and prepared first
or already has the target state.
- CMMVC5453E The FlashCopy mapping was not prepared because the mapping is in
the prepared or copying state.
- CMMVC5454E The FlashCopy mapping is already in the copying state.
- CMMVC5455E The FlashCopy mapping was not started because the mapping is not
in the prepared state. The mapping must be prepared first.
- CMMVC5500E Select a FlashCopy consistency group.
- CMMVC5501E The FlashCopy consistency group was not prepared.
- CMMVC5502E The FlashCopy consistency group was not prepared.
- CMMVC5503E The FlashCopy consistency group is already in the copying state.
- CMMVC5504E The FlashCopy consistency group was not prepared because the consistency
group is in the prepared or copying state.
- CMMVC5550E Select at least one primary (source) and one secondary (target) virtual
disk.
- CMMVC5551E The primary (source) and secondary (target) virtual disk cannot be
the same.
- CMMVC5554E Select a virtual disk.
- CMMVC5555E Select a copy direction.
- CMMVC5556E The selection was not valid.
- CMMVC5557E There are no auxiliary VDisk candidates.
- CMMVC5558E The selected remote copy relationship is not valid. Select a relationship
with proper name.
- CMMVC5559E Select a Remote Copy relationship.
- CMMVC5600E Select a Remote Copy consistency group.
- CMMVC5601E Enter a valid bandwidth.
- CMMVC5602E Select a remote cluster.
- CMMVC5650E Select a Virtual Disk-to-Host Mapping to delete.
- CMMVC8350E Select a host.
- CMMVC8351E The host was not created.
- CMMVC8354E The host was not created.
- CMMVC8355E The name entered is not valid.
- CMMVC8550E Select at least one source and one target VDisk.
- CMMVC8551E Enter a valid number.
- CMMVC8600E Select a Remote Copy consistency group.
- CMMVC8601E Select a Remote Copy consistency group.
- CLI messages
- CMMVC5700E The parameter list is not valid.
- CMMVC5701E No object ID was specified.
- CMMVC5702E [%1] is below the minimum level.
- CMMVC5703E [%1] is above the maximum level.
- CMMVC5704E [%1] is not divisible by the permitted step level.
- CMMVC5705E A required parameter is missing.
- CMMVC5706E CMMVC5706E An invalid argument has been entered for the [%1] parameter.
- CMMVC5707E Required parameters are missing.
- CMMVC5708E The %1 parameter is missing its associated arguments.
- CMMVC5709E [%1] is not a supported parameter.
- CMMVC5710E No self describing structure for identifier parameter [%1].
- CMMVC5711E [%1] is not valid data.
- CMMVC5712E Required data is missing.
- CMMVC5713E Some parameters are mutually exclusive.
- CMMVC5714E There are no items in the parameter list.
- CMMVC5715E There is no parameter list.
- CMMVC5716E Nonnumeric data was entered for a numeric field ([%1]). Enter a numeric
value.
- CMMVC5717E No match was found for the specified unit.
- CMMVC5718E An unexpected return code was received.
- CMMVC5719E A value of %2 requires the parameter %1 to be specified.
- CMMVC5720E [%1] is not a valid argument for the -o parameter.
- CMMVC5721E [%1] is not a valid time-stamp format. The valid format is MMDDHHmmYY.
- CMMVC5722E [%1] is not a valid month.
- CMMVC5723E [%1] is not a valid day.
- CMMVC5724E [%1] is not a valid hour.
- CMMVC5725E [%1] is not a valid minute.
- CMMVC5726E [%1] are not valid seconds.
- CMMVC5727E [%1] is not a valid filter.
- CMMVC5728E [%1] should be in the format minute:hour:day:month:weekday.
- CMMVC5729E One or more components in the list is not valid.
- CMMVC5730E %1 is only valid when %2 has a value of %3.
- CMMVC5731E %1 can only be entered when %2 has been entered.
- CMMVC5732E The shared-memory interface is not available.
- CMMVC5733E Enter at least one parameter.
- CMMVC5734E A combination of values was entered that is not valid.
- CMMVC5735E The name entered is not valid. Enter an alphanumeric string that
does not start with a numeric.
- CMMVC5736E -c is not a valid unit.
- CMMVC5737E The parameter %1 has been entered multiple times. Enter the parameter
once.
- CMMVC5738E The name contains too many characters. Enter an alphanumeric string
of 1 - 15 characters that is composed of any of the following characters:
A - Z, a - z, 0 - 9, -, or _. The first character cannot be numeric.
- CMMVC5739E The argument %1 does not contain enough letters.
- CMMVC5740E The filter flag %1 is not valid.
- CMMVC5741E The filter value %1 is not valid.
- CMMVC5742E A specified parameter is out of its valid range.
- CMMVC5743E A specified parameter does not comply with the step value.
- CMMVC5744E Too many objects were specified in the command.
- CMMVC5745E Not enough objects were specified in the command.
- CMMVC5746E The operation that was requested is not valid for the this object.
- CMMVC5747E The operation that was requested is not valid.
- CMMVC5748E The operation that was requested is not valid.
- CMMVC5749E The dump file name already exists.
- CMMVC5750E The dump file was not created. The file system might be full.
- CMMVC5751E The dump file could not be written to disk.
- CMMVC5752E The operation failed because the object contains child objects. Delete
the child objects and then resubmit the request.
- CMMVC5753E The specified object does not exist.
- CMMVC5754E The specified object does not exist, or the name does not meet the
naming rules.
- CMMVC5755E The sizes of the specified objects do not match.
- CMMVC5756E The operation failed because the object is already mapped.
- CMMVC5757E The defaults for the self describing structure were not found.
- CMMVC5758E The object filename already exists.
- CMMVC5759E Memory cannot be allocated.
- CMMVC5760E The node could not be added to the cluster.
- CMMVC5761E The node could not be deleted from the cluster.
- CMMVC5762E The operation failed because the timeout period expired.
- CMMVC5763E The node failed to go online.
- CMMVC5764E The specified mode change is not valid.
- CMMVC5765E The select object is no longer a candidate. A change occurred during
the request.
- CMMVC5767E One or more of the specified parameters is not valid.
- CMMVC5769E The operation requires that all nodes be online. One or more nodes
are not online.
- CMMVC5770E The file for the ssh key is not valid.
- CMMVC5771E The operation failed, probably, because the object contains child
objects. To complete the operation, specify the force flag.
- CMMVC5772E The operation failed because a software upgrade is in progress.
- CMMVC5773E The operation failed because the selected object is in the wrong
mode.
- CMMVC5774E The userid is not valid.
- CMMVC5775E The directory attribute is not valid.
- CMMVC5776E The directory listing could not be retrieved.
- CMMVC5777E The node was not added to the I/O group because the other node in
the I/O Group is in the same power domain.
- CMMVC5778E The cluster was not created because one already exists.
- CMMVC5780E The action could not be completed using the Remote Cluster name.
Use the Remote Cluster Unique ID instead.
- CMMVC5781E The cluster ID specified is invalid.
- CMMVC5782E The object is offline.
- CMMVC5784E The cluster name is not unique. Specify the cluster using the cluster
ID.
- CMMVC5785E The filename contains an illegal character.
- CMMVC5786E The action failed because the cluster is not in a stable state.
- CMMVC5787E The cluster was not created because a cluster already exists.
- CMMVC5788E The service IP address is not valid.
- CMMVC5789E The cluster was not modified because the IP address, subnet mask,
service address, SNMP address, or gateway address is not valid.
- CMMVC5790E The node was not added to the cluster because the maximum number
of nodes has been reached.
- CMMVC5791E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5792E The action failed because the I/O group is used for recovery.
- CMMVC5793E The node was not added to the cluster because the I/O group already
contains a pair of nodes.
- CMMVC5794E The action failed because the node is not a member of the cluster.
- CMMVC5795E The node was not deleted because a software upgrade is in progress.
- CMMVC5796E The action failed because the I/O group that the node belongs to
is unstable.
- CMMVC5797E The node was not deleted because this is the last node in the I/O
group and there are virtual disks (VDisks) associated with the I/O group.
- CMMVC5798E The action failed because the node is offline.
- CMMVC5799E The shut down was not successful because there is only one online
node in the I/O group.
- CMMVC5800E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5801E The upgrade of the cluster software could not proceed because every
node in the cluster must be online. Either delete the node that is offline
or bring the node online and resubmit the command
- CMMVC5802E The upgrade of the cluster software could not proceed because there
is an I/O group in the cluster that contains only one node. The software upgrade
requires that each node in an I/O group be shut down and restarted. If there
is only one node in an I/O group, I/O operations could be lost if I/O operations
are not stopped before beginning the software upgrade. To upgrade the cluster,
the force option is required.
- CMMVC5803E The entry in the error log was not marked because the sequence number
was not found.
- CMMVC5804E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5805E The progress information was not returned because the FlashCopy statistics
are not ready yet.
- CMMVC5806E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5807E The action failed because the managed disk (MDisk) cannot be changed
to the specified mode.
- CMMVC5808E The action failed because the managed disk (MDisk) does not exist.
- CMMVC5809E The tracing of I/O operations was not started because it is already
in progress.
- CMMVC5810E The quorum index number for the managed disk (MDisk) was not set
because the MDisk is offline.
- CMMVC5811E The quorum index number for the managed disk (MDisk) was not set
because the quorum disk does not exist.
- CMMVC5812E The quorum index number for the managed disk (MDisk) was not set
because the MDisk is in the wrong mode. Select an MDisk that has a mode of
managed.
- CMMVC5813E The quorum index number for the managed disk (MDisk) was not set
because the MDisk has a sector size that is not valid.
- CMMVC5814E The quorum index number for the managed disk (MDisk) was not set
because the unique identifier (UID) type is not valid.
- CMMVC5815E The managed disk (MDisk) group was not created because an entity
that was specified in the command does not exist.
- CMMVC5816E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5817E The managed disk (MDisk) group was not renamed because the name was
not valid.
- CMMVC5818E The managed disk (MDisk) group was not deleted because there is at
least one MDisk in the group.
- CMMVC5819E The managed disk (MDisk) was not added to the MDisk group because
the MDisk is part of another MDisk group.
- CMMVC5820E The managed disk (MDisk) was not added to the MDisk group because
an entity that was specified in the command does not exist.
- CMMVC5821E The managed disk (MDisk) was not added to the MDisk group because
not enough MDisks were included in the list.
- CMMVC5822E The managed disk (MDisk) was not added to the MDisk group because
too many MDisks were included in the list.
- CMMVC5823E The managed disk (MDisk) was not deleted from the MDisk group because
the MDisk is part of another MDisk group.
- CMMVC5824E The managed disk (MDisk) was not deleted from the MDisk group because
it does not belong to the MDisk group.
- CMMVC5825E The managed disk (MDisk) was not deleted from the MDisk group because
a virtual disk (VDisk) is allocated from one or more of the specified MDisks.
A forced deletion is required.
- CMMVC5826E The virtual disk (VDisk) was not created because an entity that
was specified in the command does not exist.
- CMMVC5827E The command failed as a result of an inconsistency between two or
more of the entered parameters.
- CMMVC5828E The virtual disk (VDisk) was not created because the I/O group contains
no nodes.
- CMMVC5829E The image-mode virtual disk (VDisk) was not created because the number
of managed disks (MDisks) specified is greater than one.
- CMMVC5830E The image-mode virtual disk (VDisk) was not created because no managed
disk (MDisk) was specified in the command.
- CMMVC5831E The virtual disk (VDisk) was not created because the preferred node
for I/O operations is not part of the I/O group.
- CMMVC5832E The property of the virtual disk (VDisk) was not modified because
an entity that was specified in the command does not exist.
- CMMVC5833E The property of the virtual disk (VDisk) was not modified because
there are no nodes in the I/O group.
- CMMVC5834E The I/O group for the virtual disk (VDisk) was not modified because
the group is a recovery I/O group. To modify the I/O group, use the force
option.
- CMMVC5835E The virtual disk (VDisk) was not expanded because an entity that
was specified in the command does not exist.
- CMMVC5836E The virtual disk (VDisk) was not shrunk because it is locked.
- CMMVC5837E The action failed because the virtual disk (VDisk) is part of a FlashCopy
mapping.
- CMMVC5838E The action failed because the virtual disk (VDisk) is part of a Remote
Copy mapping.
- CMMVC5839E The virtual disk (VDisk) was not shrunk because an entity that was
specified in the command does not exist.
- CMMVC5840E The virtual disk (VDisk) was not deleted because it is mapped to
a host or because it is part of a FlashCopy or Remote Copy mapping.
- CMMVC5841E The virtual disk (VDisk) was not deleted because it does not exist.
- CMMVC5842E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5843E The virtual disk (VDisk)-to-host mapping was not created because
the VDisk does not have a capacity greater than zero bytes.
- CMMVC5844E The virtual disk (VDisk)-to-host mapping was not created because
the SCSI logical unit number (LUN) ID is not valid.
- CMMVC5845E The extent was not migrated because an entity that was specified
in the command does not exist.
- CMMVC5846E The virtual disk (VDisk) was not migrated because an entity that
was specified in the command does not exist.
- CMMVC5847E The virtual disk (VDisk) was not migrated because its associated
managed disk (MDisk) is already in the MDisk group.
- CMMVC5848E The action failed because the virtual disk (VDisk) does not exist
or it is being deleted.
- CMMVC5849E The migration failed because some or all of the extents are already
being migrated.
- CMMVC5850E The extent was not migrated because there is a problem with the source
extents.
- CMMVC5851E The extent was not migrated because there is a problem with the target
extents.
- CMMVC5852E The migration failed because there are too many migrations in progress.
- CMMVC5853E The action failed because there was a problem with the MDisk group.
- CMMVC5854E The extent information was not returned because the extent is not
used or does not exist.
- CMMVC5855E The extent information was not returned because the managed disk
(MDisk) is not used by any virtual disk (VDisk).
- CMMVC5856E The action failed because the virtual disk (VDisk) does not belong
to the specified managed disk (MDisk) group.
- CMMVC5857E The action failed because the managed disk (MDisk) does not exist
or it is not a member of the managed disk (MDisk) group.
- CMMVC5858E The action failed because the virtual disk (VDisk) is in the wrong
mode, the managed disk (MDisk) is in the wrong mode, or both are in the wrong
mode.
- CMMVC5859E The migration did not complete because an error occurred while migrating
the last extent on an image-mode virtual disk (VDisk).
- CMMVC5860E The action failed because there were not enough extents in the managed
disk (MDisk) group.
- CMMVC5861E The action failed because there were not enough extents on the managed
disk (MDisk).
- CMMVC5862E The action failed because the virtual disk (VDisk) is being formatted.
- CMMVC5863E The migration failed because there are not enough free extents on
the target managed disk (MDisk).
- CMMVC5864E The extent information was not returned because the source extent
is not used.
- CMMVC5865E The extent information was not returned because the extent is out
of range for the managed disk (MDisk) or virtual disk (VDisk).
- CMMVC5866E The extent was not migrated because the extent contains internal
data.
- CMMVC5867E The action failed because the worldwide port name is already assigned
or is not valid.
- CMMVC5868E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5869E The host object was not renamed because the host ID or name is not
valid.
- CMMVC5870E The host object was not deleted because an entity that was specified
in the command does not exist.
- CMMVC5871E The action failed because one or more of the configured worldwide
port names is in a mapping.
- CMMVC5872E The port (WWPN) was not added to the host object because an entity
that was specified in the command does not exist.
- CMMVC5873E The action failed because there is no matching worldwide port name.
- CMMVC5874E The action failed because the host does not exist.
- CMMVC5875E The action failed because the virtual disk (VDisk) does not exist.
- CMMVC5876E The virtual disk (VDisk)-to-host mapping was not created because
the maximum number of mappings has been reached.
- CMMVC5877E The virtual disk (VDisk)-to-host mapping was not created because
the maximum number of SCSI LUNs has been allocated.
- CMMVC5878E The virtual disk (VDisk)-to-host mapping was not created because
this VDisk is already mapped to this host.
- CMMVC5879E The virtual disk-to-host mapping was not created because this SCSI
LUN is already assigned to another mapping.
- CMMVC5880E The virtual disk (VDisk)-to-host mapping was not created because
the VDisk has a capacity of zero bytes.
- CMMVC5881E The FlashCopy mapping was not created because an entity that was
specified in the command does not exist.
- CMMVC5882E The FlashCopy mapping was not created because a mapping for the source
or target virtual disk (VDisk) already exists.
- CMMVC5883E The FlashCopy mapping was not created because the recovery I/O group
is associated with the source or target virtual disk (VDisk).
- CMMVC5884E The FlashCopy mapping was not created because the source or target
virtual disk (VDisk) cannot be a member of a Remote Copy mapping.
- CMMVC5885E The FlashCopy mapping was not created because this source or target
virtual disk (VDisk) cannot be a member of a FlashCopy mapping.
- CMMVC5886E The FlashCopy mapping was not created because the source or target
virtual disk (VDisk) is associated with the recovery I/O group.
- CMMVC5887E The FlashCopy mapping was not created because the source or target
virtual disk (VDisk) must not be in router mode.
- CMMVC5888E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5889E The FlashCopy mapping was not deleted because an entity that was
specified in the command does not exist.
- CMMVC5890E The FlashCopy mapping or consistency group was not started because
starting consistency group 0 is not a valid operation.
- CMMVC5891E The FlashCopy consistency group was not created because the name
is not valid.
- CMMVC5892E The FlashCopy consistency group was not created because it already
exists.
- CMMVC5893E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5894E The FlashCopy consistency group was not deleted because you are trying
to delete consistency group 0 or the name of the consistency group is not
valid.
- CMMVC5895E The FlashCopy consistency group was not deleted because it contains
mappings. To delete this consistency group, a forced deletion is required.
- CMMVC5896E The FlashCopy mapping was not deleted because the mapping or consistency
group is in the preparing state. The mapping or consistency group must be
stopped first.
- CMMVC5897E The FlashCopy mapping was not deleted because the mapping or consistency
group is in the prepared state. The mapping or consistency group must be stopped
first.
- CMMVC5898E The FlashCopy mapping was not deleted because the mapping or consistency
group is in the copying state. The mapping or consistency group must be stopped
first.
- CMMVC5899E The FlashCopy mapping was not deleted because the mapping or consistency
group is in the stopped state. To delete the mapping, a forced deletion is
required.
- CMMVC5900E The FlashCopy mapping was not deleted because the mapping or consistency
group is in the suspended state. The mapping or consistency group must be
stopped first.
- CMMVC5901E The FlashCopy mapping was not prepared because the mapping or consistency
group is already in the preparing state.
- CMMVC5902E The FlashCopy mapping was not prepared because the mapping or consistency
group is already in the prepared state.
- CMMVC5903E The FlashCopy mapping was not prepared because the mapping or consistency
group is already in the copying state.
- CMMVC5904E The FlashCopy mapping was not prepared because the mapping or consistency
group is already in the suspended state.
- CMMVC5905E The FlashCopy mapping or consistency group was not started because
the mapping or consistency group is in the idle state. The mapping or consistency
group must be prepared first.
- CMMVC5906E The FlashCopy mapping or consistency group was not started because
the mapping or consistency group is in the preparing state.
- CMMVC5907E The FlashCopy mapping or consistency group was not started because
the mapping or consistency group is already in the copying state.
- CMMVC5908E The FlashCopy mapping or consistency group was not started because
the mapping or consistency group is in the stopped state. The mapping or consistency
group must be prepared first.
- CMMVC5909E The FlashCopy mapping or consistency group was not started because
the mapping or consistency group is in the suspended state.
- CMMVC5910E The FlashCopy mapping or consistency group was not stopped because
the mapping or consistency group is in the idle state.
- CMMVC5911E The FlashCopy mapping or consistency group was not stopped because
the mapping or consistency group is in the preparing state.
- CMMVC5912E The FlashCopy mapping or consistency group was not stopped because
the mapping or consistency group is already in the stopped state.
- CMMVC5913E The properties of the FlashCopy mapping were not modified because
the mapping or consistency group is in the preparing state.
- CMMVC5914E The properties of the FlashCopy mapping were not modified because
the mapping or consistency group is in the prepared state.
- CMMVC5915E The properties of the FlashCopy mapping were not modified because
the mapping or consistency group is in the copying state.
- CMMVC5916E The properties of the FlashCopy mapping were not modified because
the mapping or consistency group is in the suspended state.
- CMMVC5917E The FlashCopy mapping was not created because there is no memory
to create the bitmap.
- CMMVC5918E The FlashCopy mapping was not prepared because the I/O group is offline.
- CMMVC5919E The FlashCopy mapping or consistency group was not started because
the I/O group is offline.
- CMMVC5920E The FlashCopy mapping was not created because the consistency group
is not idle.
- CMMVC5921E The properties of the FlashCopy mapping were not modified because
the consistency group is not idle.
- CMMVC5922E The FlashCopy mapping was not created because the destination virtual
disk (VDisk) is too small.
- CMMVC5923E The FlashCopy mapping was not created because the I/O group is offline.
- CMMVC5924E The FlashCopy mapping was not created because the source and target
virtual disks (VDisks) are different sizes.
- CMMVC5925E The remote cluster partnership was not created because it already
exists.
- CMMVC5926E The remote cluster partnership was not created because there are
too many partnerships.
- CMMVC5927E The action failed because the cluster ID is not valid.
- CMMVC5928E The action failed because the cluster name is a duplicate of another
cluster.
- CMMVC5929E The Remote Copy partnership was not deleted because it has already
been deleted.
- CMMVC5930E The Remote Copy relationship was not created because an entity that
was specified in the command does not exist.
- CMMVC5931E The Remote Copy relationship was not created because the master or
auxiliary virtual disk (VDisk) is locked.
- CMMVC5932E The Remote Copy relationship was not created because the master or
auxiliary virtual disk (VDisk) is a member of a FlashCopy mapping.
- CMMVC5933E The Remote Copy relationship was not created because the master or
auxiliary virtual disk (VDisk) is in the recovery I/O group.
- CMMVC5934E The Remote Copy relationship was not created because the master or
auxiliary virtual disk (VDisk) is in the router mode.
- CMMVC5935E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5936E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5937E The action failed because an entity that was specified in the command
does not exist.
- CMMVC5938E The Remote Copy consistency group was not deleted because the consistency
group contains relationships. To delete the consistency group, the force option
is required.
- CMMVC5939E The action failed because the cluster is not in a stable state.
- CMMVC5940E The cluster that contains the auxiliary virtual disk (VDisk) is unknown.
- CMMVC5941E The cluster that contains the master virtual disk (VDisk) has too
many consistency groups.
- CMMVC5942E The cluster that contains the auxiliary virtual disk (VDisk) has
too many consistency groups.
- CMMVC5943E The specified relationship is not valid.
- CMMVC5944E The specified consistency group is not valid.
- CMMVC5945E The specified master cluster is not valid.
- CMMVC5946E The specified auxiliary cluster is not valid.
- CMMVC5947E The specified master virtual disk (VDisk) is not valid.
- CMMVC5948E The specified auxiliary virtual disk (VDisk) is not valid.
- CMMVC5949E The specified relationship is unknown.
- CMMVC5950E The specified consistency group is unknown.
- CMMVC5951E The operation cannot be performed because the relationship is not
a stand-alone one.
- CMMVC5952E The relationship and consistency group have different master clusters.
- CMMVC5953E The relationship and group have different auxiliary clusters.
- CMMVC5954E The master and auxiliary virtual disks (VDisks) are different sizes
- CMMVC5955E he maximum number of relationships has been reached.
- CMMVC5956E The maximum number of consistency groups has been reached.
- CMMVC5957E The master virtual disk (VDisk) is already in a relationship.
- CMMVC5958E The auxiliary virtual disk (VDisk) is already in a relationship.
- CMMVC5959E There is a relationship that already has this name on the master
cluster.
- CMMVC5960E There is a relationship that already has this name on the auxiliary
cluster.
- CMMVC5961E There is a consistency group that already has this name on the master
cluster.
- CMMVC5962E There is a consistency group that already has this name on the auxiliary
cluster.
- CMMVC5963E No direction has been defined.
- CMMVC5964E The copy priority is not valid.
- CMMVC5965E The virtual disks (VDisks) are in different I/O groups on the local
cluster.
- CMMVC5966E The master virtual disk (VDisk) is unknown.
- CMMVC5967E The auxiliary virtual disk (VDisk) is unknown.
- CMMVC5968E The relationship cannot be added because the states of the relationship
and the consistency group do not match.
- CMMVC5969E The Remote Copy relationship was not created because the I/O group
is offline.
- CMMVC5970E The Remote Copy relationship was not created because there is not
enough memory.
- CMMVC5971E The operation was not performed because the consistency group contains
no relationships.
- CMMVC5972E The operation was not performed because the consistency group contains
relationships.
- CMMVC5973E The operation was not performed because the consistency group is
not synchronized.
- CMMVC5974E The operation was not performed because the consistency group is
offline.
- CMMVC5975E The operation was not performed because the cluster partnership
is not connected.
- CMMVC5976E The operation was not performed because the consistency group is
in the freezing state.
- CMMVC5977E The operation was not performed because it is not valid given the
current consistency group state.
- CMMVC5978E The operation was not performed because the relationship is not synchronized.
- CMMVC5979E The operation was not performed because the relationship is offline.
- CMMVC5980E The operation was not performed because the master and auxiliary
clusters are not connected.
- CMMVC5981E The operation was not performed because the relationship is in the
freezing state.
- CMMVC5982E The operation was not performed because it is not valid given the
current relationship state.
- CMMVC5983E The dump file was not created. The file system might be full.
- CMMVC5984E The dump file was not written to disk. The file system might be full.
- CMMVC5985E The action failed because the directory that was specified was not
one of the following directories: /dumps, /dumps/iostats, /dumps/iotrace,
/dumps/feature, /dumps/configs, /dumps/elogs, or /home/admin/upgrade.
- CMMVC5986E The tracing of I/O operations was not started because the virtual
disk (VDisk) or managed disk (MDisk) failed to return statistics.
- CMMVC5987E Address is not valid.
- CMMVC5988E This command should not be issued if you are logged in with a root
user ID. Use the admin userid.
- CMMVC5989E The FlashCopy consistency group was not started as there are no FlashCopy
mappings within the group.
- CMMVC5990E The FlashCopy consistency group was not stopped as there are no FlashCopy
mappings within the group.
- CMMVC5991E The FlashCopy consistency group was not stopped as there are no FlashCopy
mappings within the group.
- CMMVC5992E The Remote Copy consistency group was not stopped as there are no
Remote Copy relationships within the group.
- CMMVC5993E The specific upgrade package does not exist.
- CMMVC5994E Error in verifying the signature of the upgrade package.
- CMMVC5995E Error in unpacking the upgrade package.
- CMMVC5996E The specific upgrade package cannot be installed over the current
version.
- CMMVC5997E The action failed because the capacity of the MDisk is smaller than
the extent size of the MDisk group.
- CMMVC5998E This command can not be run on a node that is in service mode.
- CMMVC5998W The virtualized storage capacity exceeds the amount that you are
licensed to use. Nevertheless, the action you have requested has been completed.
- CMMVC5999W Featurization for this facility has not been enabled.
- CMMVC5999E Undefined error message.
- CMMVC6000W Featurization for this facility has not been enabled.
- CMMVC6001E The FlashCopy consistency group was not started as there are no FlashCopy
mappings within the group.
- CMMVC6002E This command can only be run on a node that is in service mode.
- CMMVC6003E This command can not be run on a node that is in service mode.
- CMMVC6004E The delimiter value, %1, is invalid.
- CMMVC6005E The view request failed as the specified object is not a member of
an appropriate group.
- CMMVC6006E The managed disk (MDisk) was not deleted because the resource was
busy.
- CMMVC6007E The two passwords that were entered do not match.
- CMMVC6008E The key already exists.
- CMMVC6009E Unable to malloc a block of memory in which to copy the returned
data.
- CMMVC6010E Unable to complete the command as there are insufficient free extents.
- CMMVC6011E At least one remote cluster partnership has been found. This upgrade
package cannot be applied to the current code level until all remote cluster
partnerships are deleted.
- CMMVC6012W The virtualized storage capacity is approaching the amount that you
are licensed to use.
- CMMVC6013E The command failed because there is a consistency group mismatch
on the aux cluster.
- CMMVC6014E The command failed because the requested object is either unavailable
or does not exist.
- CMMVC6015E A delete request is already in progress for this object.
- CMMVC6016E The action failed as there would be, or are, no more disks in the
MDisk group.
- CMMVC6017E %1 contains invalid characters. Ensure that all characters are ASCII.
- CMMVC6018E The software upgrade pre-install process failed.
- CMMVC6019E The software upgrade failed as a node pended while the upgrade was
in progress.
- CMMVC6020E The software upgrade failed as the system was unable to distribute
the software package to all nodes.
- CMMVC6021E The system is currently busy performing another request. Please try
again later.
- CMMVC6022E The system is currently busy performing another request. Please try
again later.
- CMMVC6023E The system is currently busy performing another request. Please try
again later.
- CMMVC6024E The auxiliary VDisk entered is invalid.
- CMMVC6025E The RC consistency group Master cluster is not the local cluster.
- CMMVC6026E The RC consistency group is not in the stopped state.
- CMMVC6027E The RC consistency group is not the primary master.
- CMMVC6028E This upgrade package cannot be applied to the current software level
because it contains changes to the cluster state and there are remote cluster
partnership defined.
- CMMVC6029E All nodes must have identical code level before a concurrent code
upgrade can be performed.
- CMMVC6030E The operation was not preformed because the FlashCopy mapping is
part of a consistency group. The action must be performed at the consistency
group level.
- CMMVC6031E The operation was not preformed because the FlashCopy consistency
group is empty.
- CMMVC6032E The operation was not preformed because one or more of the entered
parameters is invalid for this operation.
- CMMVC6033E The action failed due to an internal error.
- CMMVC6034E The action failed because the maximum number of objects has been
reached.
- CMMVC6036E An invalid action was requested.
- CMMVC6037E The action failed as the object is not empty.
- CMMVC6038E The action failed as the object is empty.
- CMMVC6039E The action failed as the object is not a member of a group.
- CMMVC6040E The action failed as the object is not a parent.
- CMMVC6041E The action failed as the cluster is full.
- CMMVC6042E The action failed as the object is not a cluster member.
- CMMVC6043E The action failed as the object is a member of a group.
- CMMVC6044E The action failed as the object is a parent.
- CMMVC6045E The action failed as the force flag was not entered.
- CMMVC6046E The action failed as too many candidates were selected.
- CMMVC6048E The action failed as the object is busy.
- CMMVC6049E The action failed as the object is not ready.
- CMMVC6050E The action failed as the command was busy.
- CMMVC6051E An unsupported action was selected.
- CMMVC6052E The action failed as the object is a member of a Flash Copy mapping.
- CMMVC6053E An invalid WWPN was entered.
- CMMVC6054E The action failed as not all nodes are online.
- CMMVC6055E The action failed as an upgrade is in progress.
- CMMVC6056E The action failed as the object is too small.
- CMMVC6057E The action failed as the object is the target of a Flash Copy mapping.
- CMMVC6059E The action failed as the object is in an invalid mode.
- CMMVC6060E The action failed as the object is in the process of being deleted.
- CMMVC6061E The action failed as the object is being resized.
- CMMVC6071E The virtual disk is already mapped to a host. To create additional
virtual disk-to-host mappings, you must use the command-line interface.
- CMMVC6073E The maximum number of files has been exceeded.
- CMMVC6074E The command failed as the extent has already been assigned.
- CMMVC6075E The expand failed as the last extent is not a complete extent.
- CMMVC6076E The command failed due to an error while flushing the VDisk.
- CMMVC6077E WARNING - Unfixed errors should be fixed before applying software
upgrade. Depending on the nature of the errors, they may cause the upgrade
process to fail. It is highly recommended to fix these errors before proceeding.
If you cannot fix a particular error then please contact your IBM service
representatives.
- CMMVC6083E Metadata recovery could not allocate the resources necessary to complete
the operation.
- CMMVC6085E Metadata recovery could not create/open/write the dump file, the
disk might be full.
- CMMVC6086E Metadata recovery could not create/open/write the progress file,
the disk might be full.
- CMMVC6087E Metadata recovery could not map the buffers necessary to complete
the operation
- CMMVC6088E The lba at which metadata recovery was requested does not contain
metadata
- CMMVC6089E The metadata at the requested lba is flagged as invalid
- CMMVC6090E The metadata header checksum verification failed
- CMMVC6091E The metadata region checksum verification failed
- CMMVC6092E The metadata recovery operation was aborted
- CMMVC6093E Metadata recovery internal error - (read only)
- CMMVC6095E Metadata recovery encountered the end of the disk.
- CMMVC6096E Metadata recovery encountered an error from a lower layer - (vl no
resource)
- CMMVC6097E Metadata recovery encountered an error from a lower layer - (vl failure)
- CMMVC6098E The copy failed as the specified node is the configuration node.
- CMMVC6100E -option not consistent with action
- CMMVC6101E -option not consistent with -option
- CMMVC6102E -option and -option are alternatives
- CMMVC6103E Problem with file-name: details
- CMMVC6104E Action name not run
- CMMVC6105E Different names for source (name) and target
(name) clusters
- CMMVC6106W Target cluster has non-default id_alias alias
- CMMVC6107E x io_grp objects in target cluster;
y are required
- CMMVC6108I Disk controller system with a WWNN of wwnn found.
- CMMVC6109E Disk controller system with a WWNN of wwnn not
available.
- CMMVC6110E Bad code level level
- CMMVC6111E Cluster code_level could not be determined from
level
- CMMVC6112W object-type object-name has a default name
- CMMVC6113E Sub-command failed with return code:
details
- CMMVC6114E No help for action action
- CMMVC6115W Feature property mismatch:
value1 expected; value2 found
- CMMVC6116I Feature match forproperty
- CMMVC6117E fix-or-feature is not available
- CMMVC6118I type with property value
[and property value] found
- CMMVC6119E type with property value
[and property value] not found
- CMMVC6120E Target is not the configuration node
- CMMVC6121E No cluster id or id_alias in backup configuration
- CMMVC6122E No type with property
value present in table
- CMMVC6123E No property for type name
- CMMVC6124E No type with property
value
- CMMVC6125E No unique ID for type
name
- CMMVC6126E No type with unique ID
value
- CMMVC6127I SSH key identifier for
user already defined; will not be restored
- CMMVC6128W details
- CMMVC6129E vdisk-to-host map objects have vdisk_UID values that are not consistent
- CMMVC6130W Inter-cluster property will not be restored
- CMMVC6131E No location cluster information
- CMMVC6132E An object of a given type has a property with an incorrect
value. The operation cannot proceed until the property has the correct value.
Take administrative action to change the value and try again.
- CMMVC6133E Required type property
property not found
- CMMVC6134E No argument for -option
- CMMVC6135E Argument value for
-option is not valid
- CMMVC6136W No SSH key file file-name
- CMMVC6137W No SSH key file file-name; key not restored
- CMMVC6138E -option is required
- CMMVC6139E Incorrect XML tag nesting in filename
- CMMVC6140E No default name for type type
- CMMVC6141E -option does not contain any argument
- CMMVC6142E Existing object-type
object-name has a non-default name
- CMMVC6143E Required configuration file file-name does
not exist
- CMMVC6144W Object with default name name restored as substitute-name
- CMMVC6145I Use the restore -prepare command first
- CMMVC6146E Problem parsing object-type data:
line
- CMMVC6147E type name has a name beginning with
prefix
- CMMVC6148E Target cluster has n-actual objects of type type instead of n-required
- CMMVC6149E An action is required
- CMMVC6150E The action, action, is not valid
- CMMVC6151E The -option option is not valid
- CMMVC6152E vdisk name instance number instance is not
valid
- CMMVC6153E object not consistent with
action
- CMMVC6154E Required object-type property
property-name has a null value
- CMMVC6155I SVCCONFIG processing completed successfully
- CMMVC6156W SVCCONFIG processing completed with errors
- CMMVC6164E The SVCCONFIG CRON job, which runs overnight on a daily overnight,
has failed.
- CMMVC6165E Target is not the original configuration node with WWNN of value.
- CMMVC6206E The software upgrade failed as a file containing the software for
the specified MCP version was not found.
- Hardware messages
- Defining cluster error codes
- 1002
- 1010
- 1012
- 1020
- 1040
- 1044
- 1050
- 1060
- 1070
- 1071
- 1075
- 1076
- 1077
- 1080
- 1081
- 1135
- 1140
- 1145
- 1150
- 1155
- 1160
- 1165
- 1170
- 1175
- 1180
- 1185
- 1190
- 1195
- 1200
- 1210
- 1220
- 1230
- 1310
- 1320
- 1330
- 1335
- 1340
- 1370
- 1400
- 1550
- 1610
- 1620
- 1625
- 1630
- 1660
- 1670
- 1720
- 1900
- 1910
- 1920
- 1930
- 2010
- 2030
- 2040
- 2100
- Understanding the boot codes
- 100
- 110
- 120
- 130
- 135
- 137
- 140
- 150
- 155
- 160
- 170
- 174
- 175
- 180
- 185
- 190
- 195
- 200
- 205
- 210
- 215
- 220
- 225
- 230
- 235
- 240
- Understanding the node rescue codes
- 300
- 310
- 320
- 330
- 340
- 345
- 350
- 360
- 370
- Understanding the node error codes
- 510
- 511
- 513
- 520
- 540
- 550
- 555
- 558
- 560
- 562
- 564
- 570
- 572
- 574
- 576
- 578
- 579
- 580
- 900
- 990
- Understanding the create cluster error codes
- 700
- 710
- Controls and indicators for the SAN Volume Controller
- Controls for the SAN Volume Controller
- Power button
- Navigation buttons
- Select button
- Indicators for the SAN Volume Controller front panel
- Power LED
- Check LED
- Node identification label
- Cluster identification
- SAN Volume Controller rear panel indicators
- System board power LED
- System board fault LED
- Monitor LED
- Lower Ethernet connection LED
- Upper Ethernet connection LED
- Controls and indicators for the uninterruptible
power supply
- Controls for the uninterruptible power supply
- On button
- Off button
- Test and alarm reset button
- Indicators for the uninterruptible power supply
- Battery mode indicator
- Mode indicator
- Uninterruptible power supply battery mode indicator
- Uninterruptible power supply mode indicator
- Load-level indicators
- Site wiring fault indicators
- Battery service indicator
- General alarm indicator
- Load-level indicators
- Front panel display
- Status indicators
- Boot progress indicator
- Boot failed
- Hardware boot
- Node rescue request
- Power failure
- Powering off
- Restarting
- Shutting down
- Error codes
- SAN Volume Controller menu options
- Cluster options
- Status
- IP address
- Subnet mask
- Gateway
- Recover cluster?
- Node options
- Status
- Create cluster?
- Ethernet option
- Fibre channel port-1 through 4 option
- Select language? option
- Selecting the Language
- Recover cluster navigation
- Create cluster menu navigation
- Deleting the cluster
- IP address
- Subnet mask
- Gateway
- Create now
- Password
- Create failed
- Navigating through the change language menu
- Changing the language settings
- Master console components
- SAN Volume Controller Console
- IBM Director
- Vital product data (VPD)
- Viewing the vital product data
- Understanding the fields for the node VPD
- Understanding the fields for the cluster VPD
- Physical characteristics of the SAN Volume Controller
- SAN Volume Controller hardware
- Using the power control for the SAN Volume Controller
- SAN Volume Controller connectors
- Parts catalog
- Assembly 1-: SAN Volume Controller
- Assembly 2-2: Uninterruptible power supply
- Country or region power cables for the uninterruptible
power supply
- Hardware for the uninterruptible power supply
- Service mode overview
- Definitions of the FRU names for the SAN Volume Controller
- Definitions of the FRU names for the uninterruptible
power supply
- Copy Services
- Valid combinations of FlashCopy and Remote Copy
functions
- Valid combinations of virtualization, FlashCopy,
and Remote Copy features
- Interaction of one virtualization feature with
another virtualization feature
- Maximum configuration
- FlashCopy indirection layer
- Grains and the FlashCopy bitmap
- Writes to the source or target
- FlashCopy limits
- Source and target reads
- FlashCopy mapping events
- Logs and traces
- Configuration dumps
- Error logs
- Feature logs
- SAN Volume Controller supported environment
- Supported host attachments
- Fibre Channel (SCSI-FCP) attached open-systems
host support
- Targets and LUNs
- FlashCopy and Remote Copy restrictions
- Fibre Channel port name identification
- Sample AIX error log
- Supported storage subsystems
- Supported fibre-channel host bus adapters
- Supported switches
- Switch operations over long distances
- Supported fibre-channel extenders
- Object types
- Event codes
- Information event codes
- Configuration event codes
- Legal Information
- Notices
- Trademarks
- Safety and environmental notices
- Definitions of notices
- Danger notices for the uninterruptible power
supply
- Danger notices for the SAN Volume Controller
- Caution notices for the uninterruptible power
supply
- Caution notices for the SAN Volume Controller
- Inspecting the SAN Volume Controller for unsafe conditions
- External machine checks
- Internal machine checks
- Checking the grounding of the SAN Volume Controller and
the uninterruptible power supply
- Inspecting the uninterruptible power supply for unsafe
conditions
- Uninterruptible power supply requirements
- Emergency power-off (EPO) event
- Checking the safety labels on the SAN Volume Controller
- Checking the labels on the outside of the uninterruptible
power supply
- Checking the labels on the battery of the uninterruptible
power supply
- Environmental notices and statements
- Product recycling
- Product disposal
- Battery disposal
- Handling static-sensitive devices
- Product recycling
- Electronic emission notices
- Federal Communications Commission (FCC) statement
- Industry Canada compliance statement
- New Zealand compliance statement
- European Union (EU) statement
- Japanese Voluntary Control Council for Interference
(VCCI) statement
- China Class A EMC compliance in Simplified Chinese
- International Electrotechnical Commission (IEC)
statement
- Avis de conformité à la réglementation
d'Industrie Canada
- United Kingdom telecommunications requirements
- Radio protection for Germany
- Korean Government Ministry of Communication
(MOC) statement
- Taiwan Class A compliance statement
- SAN Volume Controller resources
- Related publications
- How to order IBM publications
- Related Web sites
- Glossary
- Index