efiutil, LUNS command and Integrity Servers

[Abra]

This question is related to a problem I'm having with HDS storage and VMS posted here: http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1139926.

Please do not use this thread for discussion of that problem.

My question here is fairly straight forward. There is a utility efiutil, found on the Integrity offline tools CD. That utility has a command called LUNS. When I run that command for each of the 4 FC adapters on my system, it reports no devices.

For Example:

efiutil.efi> luns
A0 devices counted 0

efiutil.efi> lun_names
A0 devices counted 0

efiutil.efi> lun_paths

efiutil.efi> lun_attribs

efiutil.efi>

This tells me that the SAN storage being allocated to the Integrity Server is not being seen by the Integrity Server.

Is that the correct interpretation? This is an important question becuase the storage "don't know VMS" and are trying to blame the problem on VMS. And, I have to acknowledge that I don't know storage so maybe the problem is VMS.

But, based on the output from the efiutil tool, my thinking is this has nothing to do with VMS becuase the Integrity server can't even see the LUNS. We could be booting any of the 4 OS's that run on Integrity, the box still can't see the LUNs.

IS that the correct thinking? Is that the correct interpretation of that tool?

Thank you.

[Luk Vandenbussche]

I agree with your way of thinking.

But i also think you need a solution for you problem.
Is is a box connected to a san? If this is the case, check your zoning this might be the problem

[Torsten.]

Hi,

not 100% sure, but I think you need to adjust the scan level first.

See

eficfg.pdf and
efiutil.pdf

on the CD for more information (step-by-step).

[kris rombauts · Accepted solution]

Hi,

if the objective is to test that LUNs can be seen by the fibre cards or not , did you tried the following ?

Assuming the fibre HBA is successfully logged into the SAN switch and the disk array FC ports also and both can be seen as F-port i.e. (or are you using direct connect ?).

1) run map command at EFI level
If there are block devices seen via the fibre (aka LUNs on your disk array) then they should be visible here already i.e. :
(Both fs1: and fs2: seen here are filesystems on LUNs on a fibre disk array)

fs0:\> map
Device mapping table
fs0 : Acpi(HWP0002,PNP0A03,0)/Pci(2|0)/Usb(0, 2)/CDROM(Entry0)/HD(Part1,Sig00000000)
fs1 : Acpi(HPQ0002,PNP0A08,300)/Pci(0|0)/Pci(0|1)/Fibre(WWN500508B3009111F1,Lun2000000000
1F074227D396)
fs2 : Acpi(HPQ0002,PNP0A08,300)/Pci(0|0)/Pci(0|1)/Fibre(WWN500508B3009111F1,Lun2000000000
44E4FA9B706A)
blk0 : Acpi(HWP0002,PNP0A03,0)/Pci(2|0)/Usb(0, 2)
blk1 : Acpi(HWP0002,PNP0A03,0)/Pci(2|0)/Usb(0, 2)/CDROM(Entry0)
blk2 : Acpi(HWP0002,PNP0A03,0)/Pci(2|0)/Usb(0, 2)/CDROM(Entry0)/HD(Part1,Sig00000000)
blk3 : Acpi(HPQ0002,PNP0A08,300)/Pci(0|0)/Pci(0|1)/Fibre(WWN500508B3009111F1,Lun2000000000
blk4 : Acpi(HPQ0002,PNP0A08,300)/Pci(0|0)/Pci(0|1)/Fibre(WWN500508B3009111F1,Lun2000000000
1F074227D396)
blk5 : Acpi(HPQ0002,PNP0A08,300)/Pci(0|0)/Pci(0|1)/Fibre(WWN500508B3009111F1,Lun2000000000
44E4FA9B706A)
blk6 : Acpi(HPQ0002,PNP0A08,300)/Pci(0|0)/Pci(0|1)/Fibre(WWN500508B3009111F1,Lun2000000000
9CC8853232C9)
blk7 : Acpi(HPQ0002,PNP0A08,300)/Pci(0|0)/Pci(0|1)/Fibre(WWN500508B3009111F1,Lun2000000000
9C1BBEA7608C)
blk8 : Acpi(HPQ0002,PNP0A08,300)/Pci(0|0)/Pci(0|1)/Fibre(WWN500508B3009111F9,Lun2000000000

fs0:\>

2) use the drvcfg command
-------------------------

did you verified the settings in the Qlogic adapter using the steps described in the eficfg.pdf document ?
In short it consists of three steps

- run drivers command and note the nr next to your Qlogic HBA
- run the drvcfg command and note the driver handle for that FC HBA
- run drvcfg ctrl nr handle nr -s , this will launch the Qlogic config utility where you have several settings like OS type, EFI scan level that can be set.

i.e.


fs0:\> drivers
T D
D Y C I
R P F A
V VERSION E G G #D #C DRIVER NAME IMAGE NAME
== ======== = = = == == =================================== ===================
13 00000011 B - - 6 19 PCI Bus Driver PciBus
1F 02010400 D X X 1 - LSI Logic Fusion MPT SAS Driver PciROM:02:01:00:001
23 00000108 B X X 1 2 HP 4 Gb Fibre Channel Driver PciROM:04:00:01:002
24 00000108 D X X 1 - HP 4 Gb Fibre Channel Driver PciROM:04:00:00:002
28 00000108 D X X 1 - HP 4 Gb Fibre Channel Driver PciROM:06:00:01:002
29 00000108 D X X 1 - HP 4 Gb Fibre Channel Driver PciROM:06:00:00:002
2E 00000014 D X - 1 - Usb Keyboard Driver UsbKb
...

fs0:\> drvcfg
Configurable Components
Drv[1F] Ctrl[20] Lang[eng]
Drv[23] Ctrl[27] Lang[eng]
Drv[24] Ctrl[26] Lang[eng]
Drv[28] Ctrl[2C] Lang[eng]
Drv[29] Ctrl[2B] Lang[eng]
Drv[2E] Ctrl[46] Lang[eng]
Drv[59] Ctrl[1D] Lang[eng]
Drv[59] Ctrl[1E] Lang[eng]
Drv[59] Ctrl[21] Lang[eng]
Drv[59] Ctrl[22] Lang[eng]


fs0:\> drvcfg 23 27 -s

(This starts the utility):


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 [Windows/Linux/Other]
6. EFI Variable EFIFCScanLevel [?]
7. Enable World Login [n]


EFI Variable EFIFCScanLevel
Used to disable Boot Order List Login. The variable EFIFCScanLevel
is maintained by EFI in the system NVRAM. If the variable is not
defined or set to 0, the OS Mode switch is used to enable/disable
Boot Order List Login. If the variable is set to any non zero value,
Boot Order List Login is disabled. The Driver Configuration protocol
allows this variable to be created if it does not exist. If the
variable does not exist, the menu will display a message asking if
it should be created.

Enable World Login
Specifies that the driver will login to all devices. When enabled,
this option will override all of the other Boot Settings. World Login
can significantly increase the boot time if there are many devices
connected to the adapter.


3) the efiutil provides this output (in my config)


fs0:\efi\hp\tools\io_cards\fc4> efiutil

Fibre Channel Card Efi Utility 2.17 (03/23/2006)

4 Fibre Channel Adapters found:

Adapter Path WWN Driver (Firmware)
A0 Acpi(00022211,PNP0A08,300/Pci(0|0)/Pci(0|0) 500110A000191270 1.08 (4.00.070)
A1 Acpi(00022211,PNP0A08,300/Pci(0|0)/Pci(0|1) 500110A000191272 1.08 (4.00.070)
A2 Acpi(00022211,PNP0A08,400/Pci(0|0)/Pci(0|0) 500110A0001911E4 1.08 (4.00.070)
A3 Acpi(00022211,PNP0A08,400/Pci(0|0)/Pci(0|1) 500110A0001911E6 1.08 (4.00.070)


efiutil> luns
A0-06:000 CNTL HP HSV210
A0-07:000 CNTL HP HSV210
A0-08:000 CNTL HP HSV210
A0-09:000 CNTL HP HSV210
A0 devices counted 4

efiutil> lun_paths

efiutil> lun_attribs
A0-06:000
FIRMWARE rev:4.00.070
CHIP rev:2
PCI busmode:PCIX-133MHZ
CONTROLLER loopid:0 portid:30500
CONTROLLER wwpn:500110A000191270 wwnn:500110A000191271
SWITCH wwpn:200500051E048773 wwnn:100000051E048773
FIBRE frame size:2048 bytes link speed:10G/s topology:FABRIC-P2P
LUN number:0 portid:10000 topology:FABRIC-P2P

A0-07:000
FIRMWARE rev:4.00.070
CHIP rev:2
PCI busmode:PCIX-133MHZ
CONTROLLER loopid:0 portid:30500
CONTROLLER wwpn:500110A000191270 wwnn:500110A000191271
SWITCH wwpn:200500051E048773 wwnn:100000051E048773
FIBRE frame size:2048 bytes link speed:10G/s topology:FABRIC-P2P
LUN number:0 portid:10100 topology:FABRIC-P2P
.....


Normally i'd say with just the map output you should have enough evidence, but obviously the settings should be correct in the adapter and SAN and LUN security/presentation from the array side.

If you don't see the luns at this level (EFI), it is not a Operating System issue.


HTH

Kris

[kris rombauts]

Obviously all of the above assumes you have Qlogic adapters and not Emulex since you gave the example of the efiutil.

If you just enter the efiutil command, it should already list you the Qlogic hba's that are present in the system, if none are shown, it means you have Emulex cards, not Qlogic cards, efiutil is only for Qlogic cards.

If you do have Emulex adapters, you need to use the " drvcfg x y -s" method to configure the card(s).

Kris

[Rob Leadbeater]

I seem to recall only QLogic cards being supported by VMS on Integrity servers...

Cheers,

Rob

[Abra]

Torsten and Kris - Thank you for your suggestions.

Kris, especially, thank you for taking the time to "spell it out" for me. It was most helpful to my understanding what may or may not be important.

I did find that the scan level was undefined, I changed, cycled powered, but it had no effect on what I observe.

Unfortunately, the problem is not solved, although I didn't come to this forum for a solution, I simply wanted to confirm that I wasn't doing anything wrong.

(the solution will come when I can get the storage folks to sit down for a few minutes and work on this problem. I may be back tot he ITRC at that time ;^) )

Just in case I am missing something, here is what I am seeing when I repeat Kris's steps:

This is what EFI is seeing:

Device mapping table
fs0 : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)/CDROM(Entry0)
fs1 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr5000C50003D87421,Lun0)/HD(Part1,Sig4F1ECEC1-09B2-11DC-81B6-AA000400FFFF)
fs2 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr5000C50003D87421,Lun0)/HD(Part4,Sig4F1ECEC0-09B2-11DC-81B7-AA000400FFFF)
blk0 : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)
blk1 : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)/CDROM(Entry0)
blk2 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr5000C50003D68FB5,Lun0)
blk3 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr5000C50003D87421,Lun0)
blk4 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr5000C50003D87421,Lun0)/HD(Part1,Sig4F1ECEC1-09B2-11DC-81B6-AA000400FFFF)
blk5 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr5000C50003D87421,Lun0)/HD(Part2,Sig4F1ECEC0-09B2-11DC-81B5-AA000400FFFF)
blk6 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr5000C50003D87421,Lun0)/HD(Part3,Sig4F1ECEC1-09B2-11DC-81B5-AA000400FFFF)
blk7 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr5000C50003D87421,Lun0)/HD(Part4,Sig4F1ECEC0-09B2-11DC-81B7-AA000400FFFF)
blk8 : Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr5000C50003D87421,Lun0)/HD(Part5,Sig4F1ECEC0-09B2-11DC-81B6-AA000400FFFF)


None of those are FC block devices (aka LUNs), right?




D Y C I
R P F A
V VERSION E G G #D #C DRIVER NAME IMAGE NAME
== ======== = = = == == =================================== ===================
15 00000011 B - - 8 17 PCI Bus Driver PciBus
1E 03001300 B X X 1 1 Intel(R) PRO/1000 3.0.13 EFI-64 PciROM:0A:01:01:000
1F 03001300 B X X 1 1 Intel(R) PRO/1000 3.0.13 EFI-64 PciROM:0A:01:00:000
22 00000105 D X X 1 - HP 4 Gb Fibre Channel Driver PciROM:0F:01:01:002
23 00000105 D X X 1 - HP 4 Gb Fibre Channel Driver PciROM:0F:01:00:002
26 02010400 B X X 1 2 LSI Logic Fusion MPT SAS Driver PciROM:14:01:00:001
27 00002160 B - - 1 1 Intel(R) PRO/1000 v2.16 EFI-64 PciROM:14:02:01:000
28 00002160 B - - 1 1 Intel(R) PRO/1000 v2.16 EFI-64 PciROM:14:02:00:000
2C 03001300 B X X 1 1 Intel(R) PRO/1000 3.0.13 EFI-64 PciROM:1E:01:01:000
2D 03001300 B X X 1 1 Intel(R) PRO/1000 3.0.13 EFI-64 PciROM:1E:01:00:000
30 00000105 D X X 1 - HP 4 Gb Fibre Channel Driver PciROM:23:01:01:002
31 00000105 D X X 1 - HP 4 Gb Fibre Channel Driver PciROM:23:01:00:002


fs0:\> drvcfg
Configurable Components
Drv[1E] Ctrl[21] Lang[eng]
Drv[1F] Ctrl[20] Lang[eng]
Drv[22] Ctrl[25] Lang[eng]
Drv[23] Ctrl[24] Lang[eng]
Drv[26] Ctrl[29] Lang[eng]
Drv[2C] Ctrl[2F] Lang[eng]
Drv[2D] Ctrl[2E] Lang[eng]
Drv[30] Ctrl[33] Lang[eng]
Drv[31] Ctrl[32] Lang[eng]



Shell> drvcfg 22 25 -s
Set Configuration Options
Drv[22] Ctrl[25] 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]


Enter a Selection:


One thing that may, or may not, be of interest is that I do not have a #7: "7. Enable World Login "

[kris rombauts]

You are correct, none of the FSx: or block devices are on a SAN, they are all local and either USB (cdrom) or SAS disks.

The option 7 came with a higher firmware version i think, not sure anymore, but both EFI scan level and World login are disabled on my config and i boot from SAN.


It's time to talk to the SAN/storage guys and let them verify if the Qlogic card is properly logging into the SAN switches and if there is no zoning etc involved and obviously check the LUN security settings on the array and see if the right WWN port name is added.


Kris

[Abra]

Problem solved, resolution in the next reply.

Before I get to that however, I'd like to point out that in order to see the LUNS from the console (EFI) map command, it appears that you need to configure the "EFI Variable EFIFCScanLevel" as mentioned in kris rombauts post above. Without the scan level set, you aren't going to see the luns at EFI.

[Abra]

So, the key to getting the HDS served SAN disks available to VMS is in the following statements. The first point (bit settings), I never saw documented anywhere, although apparently HDS has them documented somewhere internally. The second point (LUN0) is more widely publicized.

1. The following host mode bits will need to be set on each storage
port the host resides on. This is done using the mode/mode setting from
the SVP of the storage array.

Mode bit 12 Deletion of Ghost LUN
Mode bit 16 Open - V
Mode bit 228 OpenVMS Alternate Path
Mode Bit 278 Adding and reducing Luns for Open VMS/True64 Online
Mode Bit 346 Enables lun security

2. A small Console Device needs to be allocated on Lun 00. This can be
a regular lun and not a command device. The OS ends up reserving
whatever is in Lun 00 for the open VMS console.