missing dbprofile command in EFI Shell

[Tim Nelson]

Has anyone encountered / attempted to use the dbprofile command from the EFI shell ?

Ignite admin guide references the use of this in order to set Ignite server IP address for lanboots in lieu of DHCP.

Curious if FW update is required, did not see any mention of it in the latest FW release notes.

rx2640

[Tim Nelson]

I believe I found the reason.

I found a note in the forums that the dbprofile command is only available on partitionable systems. The rx2620 is not partitionable.

The mention of this is at the beginning of the Direct boot profiles chapter.

"All partitionable Itanium-based systems......"

[Tim Nelson]

Found more info: this is for rx4620 but there is also the same firmware update for rx2620.

PHSS_34994 system firmware 4.1

- Added support for Directed LAN Boot within the EFI 'lanboot' command.

[mits]

Here is lanboot command help output. As you can see, lanboot uses the dbprofile. It's why you need to update the firmware.

help lanboot
Perform boot over LAN using a default server or a directed boot profile

LANBOOT [select] [-od "optional_data"] | [-dn name]

select : Select from a list of available LAN devices
-od : Pass optional command line arguments to the boot file
"optional_data" : Optional command line arguments to pass to the boot file
-dn : Specify the db-profile name to use for the LAN boot
name : The db-profile name to access

Note:
1. Use 'select' when no default LAN device is provided, so a list
of available LAN devices will be provided for user selection.
2. Use '-od' to specify optional data to be passed to the boot file.
3. Use '-dn' to specify a Direct Boot Profile (db-profile) to be used
to handle the LAN boot. Use the 'dbprofile' command to create and
manage db-profiles.

[rick jones]

The initial dbprofile support was on the partitionable systems - eg the ones based on the sx1000 chipset (rx7620, rx8620 and initial Itanium Superdomes). This has been extended to the sx2000-based systems - eg the rx7640, rx8640 and the latest Itanium Superdomes.

It has also been extended to the zx2-based systems - eg the rx2660, rx3600, rx6600 and IIRC the BL860c.

If the Ignite admin guide is for a "current" version then it probably needs to have a defect filed against it via the Response Center to get it updated.

[Tim Nelson]

Thanks Guys..

[Maxim Yakimenko]

So, I did not get it, guys - is it possible to boot rx2620 with direct profile, when I tried, I created dbprofile, give command
lanboot select -db ..,choosen lancard, EFI written something like 'waiting for server', than 'pxe-timeout'. What is the problem? I need to start some specific server or I need to patch EFI or it is not possible at all?

[Tim Nelson]

if you were able to use the dbprofile command then the FW is probably up to date. The version I had did not have any dbprofile command.

send a snap shot of your dbprofile

need
sip, cip, gip set.

[rick jones]

well, there needs to be _some_ tftp server out there at least, and if you use -dhcp there has to be a dhcp server willing to give you an IP address (hence the suggestion about -cip etc). In the context of ignite, there likely needs to be an ignite server running somewhere - if dhcp doesn't give that as the "next server" IP then you need the -sip suggestion and perhaps -b to specify the file the machine should grab.

[Tim Nelson]

Rick,

The issue I ran into as well as some others was executing a lanboot and then some other DHCP server ( typically a windows server) answers the request faster than the Ignite server.

One other way around this and I use it for virtual machines is to boot an Ignite installer disk then select Ignite server recovery. Once the DHCP server gives me an IP and can change the information and then finish the boot/install from the Ignite server.

I believe the purpose of the direct boot profiles was to correct this "other" DHCP server issue.

Yes all the correct services must be running on the Ignite server in order to work.i.e. tftp and configured nfs.

[Maxim Yakimenko]

I have this:

###################################
Shell> dbprofile
Profile List

Profile Name: test
Network Type: IPv4
Server IP address: x.y.z.13
Client IP address: x.y.z.64
Gateway IP address: x.y.z.1
Subnet Mask: 255.255.255.0
Boot File: /opt/ignite/boot/nbp.efi
Optional Data:

Shell>



Shell> lanboot select -dn test
01 Acpi(HWP0002,PNP0A03,102)/Pci(1|0)/Mac(XXXXXXXXXA82)
02 Acpi(HWP0002,PNP0A03,102)/Pci(1|1)/Mac(XXXXXXXXXA83)
03 Acpi(HWP0002,PNP0A03,109)/Pci(1|0)/Mac(XXXXXXXXXBC6)
04 Acpi(HWP0002,PNP0A03,109)/Pci(1|1)/Mac(XXXXXXXXXBC7)
Select Desired LAN: 01

Client MAC address: XXXXXXXX XA 82

LAN Configuration:
Client MAC address : XXXXXXXX XA 82
Client IP Address : x.y.z.64
Subnet Mask : 255.255.255.0
Bootp Server IP Address: x.y.z.13

Retrieving File Size

Boot file name: /opt/ignite/boot/nbp.efi
Boot file size: 0 bytes

PXE-E18: Timeout. Server did not respond.

Usage:
LANBOOT [select] [-od "optional_data"] | [-dn name]

Execute 'help lanboot' for more help.
Shell>
###################################

Why timeout? What server did not respond?

[Maxim Yakimenko]

tftp and ignite are running on server x.y.z.13. I want to use dbprofile because in our network lives DHCP-server that can give address before my DHCP, used for Ignite. Also I don't want to put CD in box every time I want to install it.

[Tim Nelson]

Maxim,

In a nutshell this is how it should work. The dbprofile was implemented for direct lanboot to the ignite server.

I suggest checking / confirming that all is working on you ignite server. FYI, if your ignite server is on a different subnet then dbprofile will not neccessarily help. You will need to read about boot helpers in the ignite guide.

I suggest you start over and open a new thread.

[Maxim Yakimenko]

Let mt post my last reply in your thread :) 1)Ignite server is on the same subnet as client
2) Ignite server functions correctly - I can install box in two ways:
1) With initial boot from dvdrom
2) Using dhcp-server installed on Ignite- server
But dbprofile does not work

[Tim Nelson]

There is a FW update for the MP.. This is what I had to do just to get the dbprofile command on a couple of my servers.

MP:CM> sysrev

MP FW : E.03.30
BMC FW : 04.03
EFI FW : 05.46
System FW : 04.10

[Tim Nelson]

One more note...

I just took down a server to do a quick test.

executed lanboot select -dn ignite

got an immediate timeout.....

tried it again ..

got a timeout....

one more time.

it works .. ??

Go figure. Obviously there is some latency with something, but it does work.

You can also set up a new boot option called Ignite ( or anything you like). THat way your EFI boot screen will have the option and you will not have to try and remember a year from now.

[rick jones]

When in doubt, try to get a network trace of the traffic. Either slap a hub in front of the client, mirror its traffic to a monitor port on the switch, or trace at the server.