Jumpstart -- Warning: Could not find matching rule in rules.ok

I just setup a new jumpstart server, and I'm having problems with rules.ok errors.

I'm coming up blank after many Google searches, forum searches, etc.....

This is the error I receive:

Skipped interface e1000g1
Attempting to configure interface e1000g0...
Configured interface e1000g0
Reading ZFS config: done.
Setting up Java. Please wait...
Serial console, reverting to text install
Beginning system identification...
Searching for configuration file(s)...
Using sysid configuration file 192.168.1.173:/security/jumpstart/sysidcfg
Search complete.
Discovering additional network configuration...
Completing system identification...
Starting remote procedure call (RPC) services: done.

-------

System identification complete.
Starting Solaris installation program...
Searching for JumpStart directory...
not found
Warning: Could not find matching rule in rules.ok
Press the return key for an interactive Solaris install program...

Here is output from the jumpstart server, which is at 192.168.1.173. There are no DNS or naming services in this environment.

This is the command I used to add the client: ./add_install_client -c 192.168.1.173:/security/jumpstart -p 192.168.1.173:/security/jumpstart client-host sun4v

root@jumpstart-server# grep client-host /etc/hosts
192.168.1.123   client-host
root@jumpstart-server# cat /etc/ethers
0:24:6f:82:bb:7a client-host
root@jumpstart-server# cat /etc/bootparams
client-host  root=192.168.1.173:/security/jumpstart/OS/S10_sparc_u9/Solaris_10/Tools/Boot install=192.168.1.173:/security/jumpstart/OS/S10_sparc_u9 boottype=:in sysid_config=192.168.1.173:/security/jumpstart install_config=192.168.1.173:/security/jumpstart rootopts=:rsize=8192
root@jumpstart-server# dfshares | grep jumpstart
jumpstart-server:/security/jumpstart       jumpstart-server  -         -
root@jumpstart-server# cd /security/jumpstart
root@jumpstart-server# ./check
Validating rules...
Validating profile profile...
The custom JumpStart configuration is ok.
root@jumpstart-server# cat rules
any -   -   profile  -
root@jumpstart-server# cat rules.ok
any -   -   profile  -
# version=2 checksum=1514
root@jumpstart-server# cat profile
install_type flash_install
archive_location nfs 192.168.1.173:/security/jumpstart/GOLD/sol_10_142900-13_sun4v_v2-2a.archive
partitioning explicit
  filesys c0t0d0s0 20480 /
  filesys c0t0d0s1 16256 swap
  filesys c0t0d0s5 20480 /var
  filesys c0t0d0s6 10240 /export/home
root@jumpstart-server# cat sysidcfg
name_service=none
root_password=XXXXXXXXXXXXX
system_locale=C
timeserver=localhost
timezone=US/Eastern
terminal=vt100
security_policy=none
network_interface=e1000g0 { primary
ip_address=192.168.1.123
netmask=255.255.255.0
protocol_ipv6=no
default_route=192.168.1.1
}
nfs4_domain=dynamic


root@jumpstart-server# grep secur /etc/dfs/dfstab
share  -F nfs  -o ro,anon=0 /security/jumpstart

root@jumpstart-server# cd /security/jumpstart
root@jumpstart-server# ls
check          GOLD           profile        profile.ufs    rules.ok
config         OS             profile.flash  rules          sysidcfg
root@jumpstart-server#

---------- Post updated at 06:07 AM ---------- Previous update was at 01:38 AM ----------

I just thought I would share my solution to this problem with everyone just it helps someone else in the future. I just now finally figured it out on my own after a lot of troubleshooting.

I suspected an NFS problem at the beginning, but I booted the server I was trying to jumpstart, and successfully mounted the jumpstart NFS mount point to it. When I saw it could do it successfully I stopped looking at NFS as part of the problem.

However, the problem ultimately came down to whoever originally setup the server I installed jumpstart on didn't set the subnet mask correctly. The subnet mask is supposed to be 255.255.255.0, and that's what was on the original client server's Solaris install. However, the jumpstart server was at /8, 255.0.0.0. (I used 192.168 as a substitution for my work's real addresses.) A regular NFS mount to it works from any client, but jumpstart certainly didn't like it. For jumpstarting this client server I was able to change it to match, at 255.0.0.0 and it worked. I'll just have to switch it back to the correct subnet after the install, and later get approval to fix the subnet mask on the server I just setup jumpstart on.