missing dbprofile command in EFI Shell

[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.