If you are not using Microsoft DHCP, the process of getting the K2000 appliance and DHCP to work together is not as easy as setting two scope options. This information should assist you in getting the issue resolved. This has been used on Solaris and other non MS DHCP systems with success.
On the K2000 appliance, we set the "next server" and "boot filename" values in the "sname" and "file" fields in the DHCP header. Our instructions for Microsoft's DHCP server set these values in the options section of the DHCP message. They could try both to see if it is easier to configure Solaris to do one or the other.
I also recommend that the TFTP server name is an IP address instead of a hostname, but it doesn't seem like that's the problem they're having if opt 67 is the only one not working.
Here is what the end result should look like. Key values are in red:
#################################################
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.1;
next-server 192.168.1.23;
filename "k2000.0";
pool {
failover peer "mypeer";
deny unknown clients;
deny dynamic bootp clients;
range 192.168.1.71 192.168.1.254;
}
}
http://www.ietf.org/rfc/rfc2131.txt
FIELD OCTETS DESCRIPTION
----- ------ -----------
op 1 Message op code / message type.
1 = BOOTREQUEST, 2 = BOOTREPLY
htype 1 Hardware address type, see ARP section in "Assigned
Numbers" RFC; e.g., '1' = 10mb ethernet.
hlen 1 Hardware address length (e.g. '6' for 10mb
ethernet).
hops 1 Client sets to zero, optionally used by relay agents
when booting via a relay agent.
xid 4 Transaction ID, a random number chosen by the
client, used by the client and server to associate
messages and responses between a client and a
server.
secs 2 Filled in by client, seconds elapsed since client
began address acquisition or renewal process.
flags 2 Flags (see figure 2).
ciaddr 4 Client IP address; only filled in if client is in
BOUND, RENEW or REBINDING state and can respond
to ARP requests.
yiaddr 4 'your' (client) IP address.
siaddr 4 IP address of next server to use in bootstrap;
returned in DHCPOFFER, DHCPACK by server.
giaddr 4 Relay agent IP address, used in booting via a
relay agent.
chaddr 16 Client hardware address.
sname 64 Optional server host name, null terminated string.
file 128 Boot file name, null terminated string; "generic"
name or null in DHCPDISCOVER, fully qualified
directory-path name in DHCPOFFER.
options var Optional parameters field. See the options
documents for a list of defined options.
Table 1: Description of fields in a DHCP message
http://www.ietf.org/rfc/rfc2132.txt
9.4 TFTP server name
This option is used to identify a TFTP server when the 'sname' field
in the DHCP header has been used for DHCP options.
The code for this option is 66, and its minimum length is 1.
Code Len TFTP server
+-----+-----+-----+-----+-----+---
| 66 | n | c1 | c2 | c3 | ...
+-----+-----+-----+-----+-----+---
9.5 Bootfile name
This option is used to identify a bootfile when the 'file' field in
the DHCP header has been used for DHCP options.
The code for this option is 67, and its minimum length is 1.
Code Len Bootfile name
+-----+-----+-----+-----+-----+---
| 67 | n | c1 | c2 | c3 | ...
+-----+-----+-----+-----+-----+---