HP-UX vPars 6.0 N-Port ID Virtualization (NPIV) - A brief overview

16
Known issues
1. With the default driver configuration, typical vPar O/S installations have their boot storage LUNs enumerated and
configured in EFI to provide for quicker vPar startup times. However, the default driver configuration may not map
all the NPIV devices. To overcome this, once the vPar boot process reaches the EFI shell, issue the command:
Shell> drvcfg –s
HP AVIO Stor Driver Configuration
==================================
Warning: Enumerating all SCSI or FC LUNs increases initialization times.
Enumerate all SCSI LUNs (Y/N)? [current setting: N]: N
Enumerate all FC LUNs (Y/N)? [current setting: N]: Y
Answer the last question “Y” to ensure that EFI can map the NPIV LUNs. You also have to issue the reset
command to make the change active.
2. If there are a large number of LUNs configured for the vHBA, entering the vPar EFI shell could be slow. This issue
can be overcome, by setting the “Enumerate all LUNs” options to “N”:
Shell> drvcfg –s
HP AVIO Stor Driver Configuration
==================================
Warning: Enumerating all SCSI or FC LUNs increases initialization times.
Enumerate all SCSI LUNs (Y/N)? [current setting: N]: N
Enumerate all FC LUNs (Y/N)? [current setting: N]: N
Note that doing this will cause EFI to not “see” any devices that have not been configured as boot devices in the
EFI boot manager even if those devices have boot partitions.
3. If the zoning or presentation of LUNs has any errors, the following messages are displayed at the vPar’s EFI when
the vPar is booted, regardless of whether there is storage visible to the vPar:
VsdIportInfo: IportInfo error 0x8000000000000006 on HBA 0x28000000000000
VsdDriverBindingStart: Exiting with 0x8000000000000006.
- - - - - - - - - - - - Live Console - - - - - - - - - - - -
VsdIssueIocbRequest: ComplQProducerIndex=0x0, ComplQConsumerIndex=0x0.
vsd_iocb_hdr_t vch_iocb_hdr = {
uint16_t iocb_index = 0x0
uint16_t next_iocb_index = 0xFFFF
uint16_t num_iocbs = 0x1
uint16_t reserved = (omitted)
uint64_t guest_context = 0x0
uint32_t iocb_type = 0x6
uint32_t iocb_status = 0x0
}
}
VsdIssueIocbRequest: The IOCB has not been processed within 60 seconds.
VsdIportInfo: IportInfo error 0x8000000000000006 on HBA 0x8020000000000
VsdDriverBindingStart: Exiting with 0x8000000000000006.
VsdIportInfo: IportInfo error 0x8000000000000006 on HBA 0x28000000000000
VsdDriverBindingStart: Exiting with 0x8000000000000006.
VsdIportInfo: IportInfo error 0x8000000000000006 on HBA 0x8020000000000
VsdDriverBindingStart: Exiting with 0x8000000000000006.
The message, “The IOCB has not been processed within 60 seconds,” occurs because the hvsd is still waiting for the
NPIV probe to complete.
During boot, the VSP creates the NPIV HBAs and does a Fibre Channel probe on each of them to find the FC targets
and LUNs. This probe can take a long time (100 seconds) if there are any unresponsive FC targets. The fcd driver
times out after 20 seconds, and retry up to 5 times before giving up (20 x 5 = 100 seconds).
The fix is to remove the unresponsive FC target from the FC zone.
Actions:
You need to give your SAN Administrator:
• The port WWN of the NPIV HBAs where the probe takes too long
• The list of FC target WWNs that are responsive and that should be presented to the NPIV HBA
• The list of FC target WWNs that are not responsive and that should not be presented to the NPIV HBA