Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Fibre Channel HBA stuff

465 views
Skip to first unread message

Marc Van Dyck

unread,
Mar 5, 2018, 11:49:10 AM3/5/18
to
I need to collect information about the fibre channel HBAs that connect
my systems (Blades) to the SAN.

I know I can do things like that :

For Qlogic:

SDA> FC SET DEVICE FGA ! Or FGB, etc.
SDA> EXAMINE LSDB+LSDB$L_LINK_DATA_RATE

! 0 = down ,1 = 1G, 2 = 2G, 3 = 4G, …

For Emulex:

SDA> FC SET DEVICE FGA ! Or FGB, etc.
SDA> EXAMINE @(@(LSDB+LSDB$PS_READ_LA_FCCD)+FCCD$PS_MBX_RSP)+8*4
SDA>

! In bits 15:8, 0 = down, 4 = 1G, 8 = 2G, 0x10 = 4G

But I'm after two other pieces of information that I can't find a
source
for :

1) Whether the FC interface is in autonegociate mode or not
2) The version of the firmware which is loaded in the HBA

The question 2 is tricky because the OVMS HBA driver pushes its own
version of firmware on the HBA when OpenVMS boots. It's not that
version
I'm after, but rather the version loaded on the HBA before boot time.

I need to know that because my systems boot from a disk on the SAN,
so at boot time, it's not the standard OVMS version which is running
yet. I must ensure that the loaded version is compatible with the
disk arrays (3PAR) requirements.

I can't find any place in OVMS where this info is available, and the
enclosure's management web interface doesn't seem to show it either.

My local contacts at HP could not find an answer to this question, so
you really are my last resort.

Thank you very much in advance !

P.S. Blade type I1, I2, or I4, and OVMS V8.4 or V8.4-2

--
Marc Van Dyck

kennethnos...@gmail.com

unread,
Mar 5, 2018, 12:31:41 PM3/5/18
to
I don't know you can get either of those on a running system.

To determine QLOGIC (all I have) HBA autonegotiate mode, the only way I know of is to get into EFI and use DRVCFG -S xx yy and use the menu options to edit the adapter settings; the next menu option for 'Data Rate' will show you the current setting.

For QLOGIC firmware, you can see this during the EFI system boot, in my case:

HP PCIe 2Port 8Gb Fibre Channel Adapter (driver 2.22, firmware 5.03.015)

Hope this helps.

Robert A. Brooks

unread,
Mar 5, 2018, 2:57:41 PM3/5/18
to
On 3/5/2018 11:49 AM, Marc Van Dyck wrote:
> I need to collect information about the fibre channel HBAs that connect
> my systems (Blades) to the SAN.
>
> I know I can do things like that :
>
> For Qlogic:
>
> SDA> FC SET DEVICE FGA ! Or FGB, etc.
> SDA> EXAMINE LSDB+LSDB$L_LINK_DATA_RATE
>
> ! 0 = down ,1 = 1G, 2 = 2G, 3 = 4G, …
>
> For Emulex:
>
> SDA> FC SET DEVICE FGA ! Or FGB, etc.
> SDA> EXAMINE @(@(LSDB+LSDB$PS_READ_LA_FCCD)+FCCD$PS_MBX_RSP)+8*4
> SDA>
>
> ! In bits 15:8, 0 = down, 4 = 1G, 8 = 2G, 0x10 = 4G
>
> But I'm after two other pieces of information that I can't find a source
> for :
>
> 1) Whether the FC interface is in autonegociate mode or not
> 2) The version of the firmware which is loaded in the HBA
$ write sys$output f$getdvi( "fga0", "fc_hba_firmware_rev")
HS1.91X6

Dates back to either V8.3 or V8.3-1H1; likely backported to V7.3-2.

In a coming version of VMS (V8.5), you'll be able to do

$ write sys$output f$getdvi( "fga0", "fc_hba_max_speed" )
8
$ write sys$output f$getdvi( "fga0", "fc_hba_current_speed" )
8

and . . .

$ sho dev/full fga0

Device FGA0:, device type QLogic ISP253x FC, is online, shareable, error logging
is enabled.

Error count 0 Operations completed 952
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 8 Fastpath 1
Current Interrupt CPU Id 8
FC Port Name 5001-4380-21DA-C2B0 FC Node Name 5001-4380-21DA-C2B1
Firmware version 4.04.04 Adapter Qlogic ISP2532 PCIe Fibre
Current speed (Gbits/sec) 8 Adapter max speed (Gbits/sec) 8

--

-- Rob

Eberhard Heuser

unread,
Mar 6, 2018, 2:09:38 AM3/6/18
to
It is important to activate a parameter in the FC controller
(example Qlogic FC):
Get into the EFI-shell:

Shell> cdrvcfg
Configurable Components
Drv[21] Ctrl[22] Lang[eng]
Drv[29] Ctrl[2C] Lang[eng]
Drv[2A] Ctrl[2B] Lang[eng]
Drv[30] Ctrl[48] Lang[eng]
Drv[4F] Ctrl[23] Lang[eng]
Drv[4F] Ctrl[24] Lang[eng]

Shell> drvcfgdrvcfg -s 29 2c
Set Configuration Options
Drv[29] Ctrl[2C] Lang[eng]Fibre Channel Driver Configuration Utility

NOTE: Do not redirect console output to a file.


Main Menu

NVRAM Parameters
1. Edit Adapter Settings
2. Edit Advanced Settings
3. Edit Database
4. Edit Boot Settings
Information
5. Show Database
6. Show Translation
7. Show NVRAM Buffer
8. Info
9. Help
Operation
10. Abandon
11. Write
12. Quit


Enter a Selection: 4


Edit Boot Settings

0. Previous Menu
1. Help
2. Enable Alternate Boot Device [n]
3. Enable Selective Login [n]
4. Enable Selective Lun Logins [n]
5. OS Mode [HP-UX/OpenVMS]
6. EFI Variable EFIFCScanLevel [1]
7. Enable World Login [n]


Enter a Selection: 6


EFI Variable EFIFCScanLevel [1]? 1


Edit Boot Settings

0. Previous Menu
1. Help
2. Enable Alternate Boot Device [n]
3. Enable Selective Login [n]
4. Enable Selective Lun Logins [n]
5. OS Mode [HP-UX/OpenVMS]
6. EFI Variable EFIFCScanLevel [1]
7. Enable World Login [n]


Enter a Selection: 0


Main Menu

NVRAM Parameters
1. Edit Adapter Settings
2. Edit Advanced Settings
3. Edit Database
4. Edit Boot Settings
Information
5. Show Database
6. Show Translation
7. Show NVRAM Buffer
8. Info
9. Help
Operation
10. Abandon
11. Write
12. Quit


Enter a Selection: 12


Exiting...
Drv[29] Ctrl[2C] Lang[eng] - Options set. Action Required is None

Shell>

By default the parameter is 0 and the machine is unable to find the
FC disks as a boot device.

Eberhard

Marc Van Dyck

unread,
Mar 6, 2018, 7:56:28 AM3/6/18
to
My concern is not booting... We are booting from SAN already (we were
already doing that in Alpha times 15 years ago) so I suppose we have
indeed done that... It's just to ensure that we remain in spec with the
3PAR requirements, hence the need to know the firmware level loaded in
the HBAs.

Eberhard Heuser was thinking very hard :
--
Marc Van Dyck

Marc Van Dyck

unread,
Mar 6, 2018, 8:01:31 AM3/6/18
to
Your two commands seen to show different things. The F$GETDVI command
returns, in your case, "HS1.91X6", while, I suppose on the same device,
the SHOW DEV/FULL returns "4.04.04". Which is what ? Also I need to be
sure that the revision level returned is the one of the firmware
natively loaded in the HBA, not the one that the FG driver pushes in
it.
Can you elaborate on that ?

Many thanks,
Marc.

Robert A. Brooks submitted this idea :

> $ write sys$output f$getdvi( "fga0", "fc_hba_firmware_rev")
> HS1.91X6
>
> Dates back to either V8.3 or V8.3-1H1; likely backported to V7.3-2.
>
> In a coming version of VMS (V8.5), you'll be able to do
>
> $ write sys$output f$getdvi( "fga0", "fc_hba_max_speed" )
> 8
> $ write sys$output f$getdvi( "fga0", "fc_hba_current_speed" )
> 8
>
> and . . .
>
> $ sho dev/full fga0
>
> Device FGA0:, device type QLogic ISP253x FC, is online, shareable, error
> logging is enabled.
>
> Error count 0 Operations completed
> 952 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 8 Fastpath
> 1 Current Interrupt CPU Id 8
> FC Port Name 5001-4380-21DA-C2B0 FC Node Name
> 5001-4380-21DA-C2B1 Firmware version 4.04.04 Adapter
> Qlogic ISP2532 PCIe Fibre Current speed (Gbits/sec) 8 Adapter max
> speed (Gbits/sec) 8

--
Marc Van Dyck

Marc Van Dyck

unread,
Mar 6, 2018, 8:04:13 AM3/6/18
to
That one I knew already. I'm after a way to find that on a live system
(without having to return to the cockpit manager console logs).

After serious thinking kennethnos...@gmail.com wrote :
>
> For QLOGIC firmware, you can see this during the EFI system boot, in my case:
>
> HP PCIe 2Port 8Gb Fibre Channel Adapter (driver 2.22, firmware 5.03.015)
>
> Hope this helps.

--
Marc Van Dyck

Robert A. Brooks

unread,
Mar 6, 2018, 9:45:29 AM3/6/18
to
On 3/6/2018 8:01 AM, Marc Van Dyck wrote:
> Your two commands seen to show different things. The F$GETDVI command
> returns, in your case, "HS1.91X6", while, I suppose on the same device,
> the SHOW DEV/FULL returns "4.04.04". Which is what ? Also I need to be
> sure that the revision level returned is the one of the firmware
> natively loaded in the HBA, not the one that the FG driver pushes in it.
> Can you elaborate on that ?

Yes, sorry for the confusion.

The differences in the output from $GETDVI and SHOW DEVICE /FULL is because
those commands were issued on two different systems.

The firmware version from $GETDVI was done an an Alpha with Emulex adapters;
SHOW DEVICE /FULL was done on an I64 blade with Qlogic adapters running a
a pre-release version of V8.5

Note that for the 16Gb FC adapters on IA64 and the 32Gb adapters on X86_64, we
will not be force-feeding a driver-held copy of the adapter firmware; we'll use
the firmware that's provided by the adapter itself.

There is no way at runtime to determine the version of the firmware in the adapter
itself.

--

-- Rob

Marc Van Dyck

unread,
Mar 6, 2018, 9:49:24 AM3/6/18
to
I have tried the two commands you gave me on one of our systems.

At boot time, retrieved from console logs, this is what I can see :

25-FEB-2018 07:24:09.76|HP PCIe 2Port 8Gb Fibre Channel Adapter (driver
2.22, firmware 5.03.015)

$ sh dev fga0/full

Device FGA0:, device type QLogic ISP253x FC, is online, shareable,
error logging
is enabled.

Error count 0 Operations completed
5757
Owner process "" Owner UIC
[APLSCY,SYSTEM]
Owner process ID 00000000 Dev Prot
S:RWPL,O:RWPL,G,W
Reference count 0 Default buffer size
0
Current preferred CPU Id 4 Fastpath
1
User preferred CPU Id 4
Current Interrupt CPU Id 4
FC Port Name 5001-4380-2665-E9D4 FC Node Name
5001-4380-2665-E9D5

So does not show the last two lines that you have mentioned.

The F$GETDVI command reports 4.04.04, which is the same as what SDA
shows :

SDA> fc set device fgb
SDA> fc show port

Overview
--------
Context ........ Live from ROCK (1.107), 6-MAR-2018 14:49:34.23
Device ......... FGB0:, PCI, Device ID 2532, Rev 02, QLogic ISP2532
Images ......... FW 4.04.04, SYS$PGQDRIVER X-51 linked 28-SEP-2016
16:11:49.14
FibreChannel ... Node WWID 5001.4380.2665.E9D7, Port WWID
5001.4380.2665.E9D6, Port ID 2A3300

which is obviously the version pushed on the card by the driver and not
the version running before OpenVMS boots.

This is OpenVMS 8.4-2 plus most official patches.
Any other hints ?

Marc.

--
Marc Van Dyck

Robert A. Brooks

unread,
Mar 6, 2018, 10:36:50 AM3/6/18
to
On 3/6/2018 9:49 AM, Marc Van Dyck wrote:
> I have tried the two commands you gave me on one of our systems.
>
> At boot time, retrieved from console logs, this is what I can see :
>
> 25-FEB-2018 07:24:09.76|HP PCIe 2Port 8Gb Fibre Channel Adapter (driver 2.22, firmware 5.03.015)
>
> $ sh dev fga0/full
>
> Device FGA0:, device type QLogic ISP253x FC, is online, shareable, error logging
>    is enabled.
>
>    Error count                    0    Operations completed              5757
>    Owner process                 ""    Owner UIC               [APLSCY,SYSTEM]
>    Owner process ID        00000000    Dev Prot              S:RWPL,O:RWPL,G,W
>    Reference count                0    Default buffer size                  0
>    Current preferred CPU Id       4    Fastpath                             1
>    User preferred CPU Id          4
>    Current Interrupt CPU Id       4
>    FC Port Name 5001-4380-2665-E9D4    FC Node Name        5001-4380-2665-E9D5
>
> So does not show the last two lines that you have mentioned.

That's because I wrote . . .

> In a coming version of VMS (V8.5), you'll be able to do
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> $ write sys$output f$getdvi( "fga0", "fc_hba_max_speed" )
> 8
> $ write sys$output f$getdvi( "fga0", "fc_hba_current_speed" )
> 8

> and . . .
^^^^^^^^^^^^

> $ sho dev/full fga0

--

-- Rob
0 new messages