ùISO8859-1.K&a ˆ”¬%Ê&ð1)Mw‹ œ(½æü, '9$aF†Íßõ#6R b q|™¸×ñ    2 < S#k!± È0â2 M(^%‡­  ÇÕï  " / =! R, t7 ¡ Ù! ö  5$ S& x& Ÿ Æ( Ý% ; , h* ‰= ´[ ò. N^ }Q ÜP . `  I à I* 2t I§4ñHost Fibre Channel adapter hardware has failedInformational MessageFailure reported in the frame responseBad AdapterReplace adapter in VIOSFibre channel LINK_DEAD errorLINK_DEAD events reported by the VIOSFibre channel cable probably unpluggedCheck fibre channel cableConnection to VIOS was lostTransport event while requests are activeVIOS closed the CRQVIOS has crashedInvestigate VIO Server PartitionConnection to the VIOS has been restoredInformational messagePHYP Call ErrorUnexpected error returned from calls to PHYPContact Customer Service RepresentativeThe connection to the VIOS was resetConnection to the VIOS was reset at the request of the protocol driverNPIVlogin failureInformational messageRequest was rejected by VIOSResponse was rejected by the clientTemporary unknown VFC errorUndefined errorError LocationError TypeRCVIO Server Partition NamePhysical Adapter Instance NamePhysical Adapter Location CodePhysical Adapter DRC NameAdapter N Port IDAdapter StateFrame FlagFrame Response StatusCall MadeAdditional InformationMADS/IO Transport ERRORError during MADS/IO TransportationVerify the Detailed Error sectionReconfigure VFC ClientMemory Allocation FailureMemory Allocation Failure from system/DMA memoryInsufficient system/DMA memoryIncrease the system memoryVFC Global errorVFC Global error prior to Adapter configAdapter already Configured/RegisteredVerify the error locationAdapter FlagsAdapter Max transfer sizeNumber of Channels ConfiguredDMA size Per ChannelVFC Log DataDetailed DataVirtual Host AdapterFC SCSI Protocol driver violationProtocol violation from FC SCSI Proto driverFC SCSI Proto driver has passed the Invalid informationProtocol violation from VIOSError Received from VIOS/VFC HostVerify the Error log on VIOSFibre channel LINK_DOWN errorLINK_DOWN event reported by the VIOSFibre channel adapter/connection errorCheck fibre channel adapter/connectionInternal/Generic ErrorInternal/Generic error for debug purposeExecution may have entered error pathContact Customer Service Representative if problem persistsUnable to create Multiple QueuesUnable to create Multiple Queues after LPMPartition is migrated from/to Multi-Queue unaware environmentAfter migrating the partition to supported Multi-Queue environment, reconfigure the adapterVIOS reports Multiple Queues are not supportedEither one or multiple components (VIOS, PHYP-FW, FC adapters) does/do not support Multi-QueueVerify partner VIOS error log to identify why Multi-Queues did not get configuredUnable to create Multiple Queues due to unsupported Processor compatibility modePartition is running in Multi-Queue unsupported processor compatibility mode (Ex: Power8/Power7)Activate the Partition in Power9 (or higher) Processor compatibility modeUnable to create Multiple Queues in Active Memory Sharing (AMS) PartitionMultiple Queues are not supported in AMS partitionActivate the partition in Dedicated Memory mode to enable Multiple QueuesConfigure VIOS-vfchost in Multi-Queue supported mode