ùISO8859-1&°×%ô7J_(n +— à â ÷ "< LYm~(’»'× ÿ# /D«t‡ x¨ ! ¡r #| –  5 (A ^  ¼ ®ª kR Êl 7CZr„(¢0Ë'ü4$1Y-‹,¹ /æ / )F 'p $˜+½1é &&M dqw ‰“ ©¶Î á îø & : OY jv …*–7Á4ù;.j|– ;± &í < .Q 9€Dº/ÿ €/y°€* «¿*Ø$ ;Maz©¼Ô ì a a‚6äIKeH±[ú [V /² #â!9 P$Z$%¤!Ê'ì 'Virtual Target Device - Logical VolumeVirtual Target Device - DiskVirtual Target Device - Optical MediaVirtual Target Device - TapeTarget Device NameLogical Unit AddressClient ReserveVirtual Target Device - File-backed DiskVirtual Target Device - File-backed OpticalPaging Device - Logical VolumePaging Device - DiskVirtual Target Device HandleVASI DRC NameVirtual Real Memory StateRedundant UsageStorage PoolClient Partition IDDevice SelectionMetro/Global MirrorVirtual Target Device - Distributed FileVirtual Target Device - LogVirtual Target Device - Distributed LogVirtual Target Device - USB DiskAllow 520-byte blocks, if supportedVirtual Target Device - Shared File-backed Disk 0514-070 Only disks that support multi-path I/O (MPIO) or which have a physical volume identifier (PVID) or an IEEE volume name may be used as a virtual target device. 0514-070 Unknown optical device was used to back the virtual target device. Please select the correct optical device and try again. 0514-070 A virtual target device already has access to the backing optical device. Optical devices cannot be shared. 0514-070 The virtual target device fails to configure because the backing optical device is not in correct state or missing. 0514-071 Unknown tape device was used to back the virtual target device. Please select the correct tape device and try again. 0514-072 A virtual target device already has access to the backing tape device. Tape devices cannot be shared. 0514-073 The virtual target device fails to configure because the backing tape device is not in correct state or missing. Command syntax errorBlock Device is not compatible with source AttributesHMC profiles have changed and the VIOS is not aware of the changeUnknown errorAttempted to map a second virtual fibre channel port to a single physical port. There are not enough usable physical ports on the destination CEC to complete the partition migrationAn existing user defined VTD name (UDN) on the destination VIOS conflicts with a UDN from the source VIOS. If the partition migration is continued, the custom name will be replaced by a name of default vtscsiX form. To change the custom name on the source VIOS to a non-conflicting name, use the chdev command to change the mig_name field (e.g. chdev -l -a mig_name=) and retryThere are not enough physical fibre channel ports on the destination VIOS to allow this client to maintain path redundancy. The migration will result in the loss of one or more redundant paths leaving the client vulnerable to hardware/cable failureThe fibre channel port was not usable due to the following incompatibility(s):Unable to find a fibre channel port on the target side VIOS that is compatible with the migrating virtual adapter. Check max transfer size and SAN zoning on target side fibre channel (fcs) ports.Pool DevicePool Device IdentifierVolume Group IdentifierVolume Group Name cfg_vt_def_lua: Usage Error cfg_vt_def_lua: Error getting ODM lock cfg_vt_def_lua: Error running savebase command cfg_vt_def_lua: ODM Error encountered cfg_vt_def_lua: Invalid flag combination specified cfg_vt_def_lua: Invalid arg value: %s specified cfg_vt_def_lua: No backing device specified cfg_vt_def_lua: No parent device specified cfg_vt_def_lua: Invalid LUA specified! lua:%s cfg_vt_def_lua: Specified LUA is in use by %s cfg_vt_def_lua: No cluster id specified cfg_vt_def_lua: LU path not specified cfg_vt_def_lua: UDID not specified cfg_vt_def_lua: Error allocating %d bytes cfg_vt_def_lua: Error configuring the device:%s VIO ServerAllow 520-byte blocks where applicableVIOS Unique IdentifierMachine TypeModelSystem IdentifierOF PrefixVIOS Partition NumberVIOS ClusterDefault Pool IdentifierCluster IdentifierCluster NameSite NameDefault Pool NameVIOS Virtual Log RepositoryVIOS Suspend DeviceVIOS Suspend AdapterStream IDPartition NumberClient NameLocationStateVIOS LPM AdapterCreate mini-snap for successful migrationsMaximum number of VASI adapters used for LPM operationsMaximum number of concurrent LPM operations per VASIConfigured number of concurrent LPM operations for this MSPConcurrency levelTCP lowest ephemeral portTCP highest ephemeral portAutomatic selection of interface adapter for RDMA transportAutomatic creation of security tunnelsMaximum number of concurrent threads allowed per VASI deviceEnable or disable NPIV disk validation for LPMEnable or disable NPIV disk validation for remote restartChange the number of commands allocated for NPIV LPM disk validationAllow service hooks to work around unstable SAN 0514-070 Unknown USB disk device was used to back the virtual target device. Please select the correct device and try again. 0514-070 A virtual target device is already mapped to the backing USB disk device. USB disk devices cannot be shared. 0514-070 The virtual target device fails to configure because the backing USB disk device is not in correct state or missing. VIOS Change ManagerTurn on interactive modeAutomatically deploy update configurationsEvent Log SizeEvent Log offlineMemory pinning policy.VIOS Vendor RulesEMC CLARiiON DeviceEMC CLARiiON MPIO DeviceEMC SYMMETRIX DeviceEMC SYMMETRIX MPIO DeviceEMC INVISTA DeviceEMC INVISTA MPIO DeviceEMC Pseudo Power DeviceMessage Of The Day displayVIOS VNIC Server AdapterMaximum number of kernel threads spawned for processing RX Sub-CRQs, 0 means 1 thread per sub-CRQMaximum number of kernel threads spawned for processing TX Sub-CRQs, 0 means 1 thread per sub-CRQMinimum TX completion interval enforced by VNIC ServerMaximum number of TX descriptors from a single Sub-CRQ to process at onceMaximum number of RXBA descriptors from a single Sub-CRQ to process at onceRX/TX completions handled in thread context (1) or interrupt context (0)Maximum number of threads spawned for processing TX completions, 0 means 1 thread per queueMaximum number of threads spawned for processing RX completions, 0 means 1 thread per queueNumber of msecs between two failover heartbeatsSupport for PortLink link detectionVIOS RAS AdapterTime stamp RAS collection startedVIOS Disaster RecoveryVIOS NPIVNPIV Number of SCSI queues per rangeNPIV Number of NVME queues per rangeNPIV Number of local cmds per channelNPIV Number of local bufs per cmdGPFS Cluster - external mount shared FSCluster IdentifierCluster Name