[Info-vax] RX4640 and Fibre channels
Joukj
joukj at hrem.nano.tudelft.nl
Thu Mar 22 03:03:39 EDT 2012
Jilly wrote:
>
> "Joukj" <joukj at hrem.nano.tudelft.nl> wrote in message
> news:jkcpju$9dp$2 at speranza.aioe.org...
>> Hi all,
>>
>> I have a Rx4640,which boots OpenVMS V8.4 fine. Presently I try to get
>> a FibreChannel storage (DS2400) working, but up to now no success.
>>
>> The controler looks within OpenVMS like this:
>> Device FGA0:, device type QLogic ISP23xx FibreChannel, is offline,
>> shareable,
>> error logging is enabled.
>>
>> Error count 2 Operations completed 3
>> Owner process "" Owner UIC [SYSTEM]
>> Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G,W
>> Reference count 0 Default buffer size 0
>> Current preferred CPU Id 0 Fastpath 1
>> Current Interrupt CPU Id 0
>> FC Port Name 2100-00E0-8B02-6299 FC Node Name 2100-00E0-8B02-6299
>>
>> Device FGB0:, device type QLogic ISP23xx FibreChannel, is online,
>> shareable,
>> error logging is enabled.
>>
>> Error count 0 Operations completed 3
>> Owner process "" Owner UIC [SYSTEM]
>> Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G,W
>> Reference count 0 Default buffer size 0
>> Current preferred CPU Id 1 Fastpath 1
>> Current Interrupt CPU Id 1
>> FC Port Name 2100-00E0-8B02-049D FC Node Name 2100-00E0-8B02-049D
>>
>> (The only difference between FGA and FGB is that FGB has no cable
>> connected and that FGA is connected to the storage array.)
>>
>> No disk-devices are visible.
>>
>>
>> What bothers me is that when I go into the EFI-shell before booting, I
>> do not see the device at all (I gave the command "devices")
>>
>> One Idea was that maybe the EFI driver was missing. However when
>> invoking the efiutil command from the firm-ware- CD
>> (
>> http://bizsupport1.austin.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=ux-36767-1&
>>
>> taskId=135&swLang=8&swEnvOID=2061&prodNameId=331475&lang=en&cc=us&idx=0&mode=4&
>>
>> )
>> it tells me that no FC-devices are present and that the driver cannot
>> be "updated"
>>
>>
>>
>> Any idea what maybe the problem?
>>
>>
>> Jouk
>
> Have the fibre ports of the storage appliance been zoned to either/both
> of these HBAs?
>
> $ SET TERM/WID=132
> $ ANALYZE/SYSTEM
> FC SET DEV FGA
> FC SHOW NAME
> FC SET DEV FGB
> FC SHOW NAME
not much info:
FGA0: / N-Port Handle Table 893C59D0 / FC-LA Table 893C7E50
-----------------------------------------------------------
FC-LA | LID Node WWID Port WWID | FC-LA
Address State Flags Marker | FC_LA$ NPH$
--------- + --- ------------------- ------------------- + ---------
------- ----- ----- -------- + -------- -------
>
> Do you see the WWPN's of the storage ports.
no...
>
> Have the storage luns been presented to these HBAs with a non-zero
> device identifier that VMS requires?
I wonder, since I do not see anything in the EFI-shell.
>
> SAN config in VMS is passive. VMS can only use the luns that have been
> presented to it thru the storage ports that have been zoned in with the
> system's HBAs. Once VMS can 'see' these luns it will create UCBs for
> them when a SYSMAN IO AUTO is executed.
Reading this, I think I have to focus on the problem, how to make the
controler+disks visisble in the EFI-shell
>
> You can also use the following to get a bit more detail as to what is
> 'seen' on the SAN.
>
> $ DEFINE/SYSTEM/EXEC IOGEN$VERBOSE TRUE
> $ MCR SYSMAN IO AUTO/LOG
> $ DEASSIGN/SYSTEM/EXEC IOGEN$VERBOSE
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port FGA0
%IOGEN-F-FTLIOERR, fatal I/O error while trying to access device
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port FGB0
>
> $ MCR SYS$ETC:FIBRE_SCAN
**************************************************************************
**************************************************************************
** **
** Scanning port FGA for all Fibre Channel devices (display only) **
** **
**************************************************************************
**************************************************************************
Probing Target 1 ==========================================================
Target = 1. LUN = 0.
----------------------
Standard Inquiry failed, status = 2c
None found on this port.
End of scan for port FGA.
*************************************************************************
**************************************************************************
** **
** Scanning port FGB for all Fibre Channel devices (display only) **
** **
**************************************************************************
**************************************************************************
Probing Target 1 ==========================================================
Target = 1. LUN = 0.
----------------------
Standard Inquiry failed, status = a58 (SS$_NOMOREDEV)
None found on this port.
End of scan for port FGB.
The status on FGB is to be expected since no device is connected. I have
no idea what "status = 2" for FGA means
>
> Jilly
More information about the Info-vax
mailing list