1. Jumpstart issue: Could not find matching rule in rules.ok
Okay, I'm not a JumpStart novice here, but I've hit a problem I just
can't seem to solve myself. I'm trying to jump a SunFire V240 with the
Dec. 2003 release of Solaris 9. I initiate the jump from the ok prompt
with "boot net -v install". The process is smooth sailing (it downloads
and boots up from the miniroot in /tftpboot, it configures the proper
interface, it finds and reads the proper sysidcfg) until I get the
following:
Configured interface bge0
Searching for configuration file(s)...
Using sysid configuration file
198.72.70.186:/jumpstart/Sysidcfg/Solaris_9/sysidcfg
Search complete.
The system is coming up. Please wait.
Begin system identification...
Starting remote procedure call (RPC) services: sysidns done.
System identification complete.
Starting Solaris installation program...
Searching for JumpStart directory...
not found
Warning: Could not find matching rule in rules.ok
So, I do some checking by exiting out of the install process. The
network interface is set up with the correct IP address and netmask and
broadcast address on the system to be installed. netstat -rn returns the
correct route on the system to be installed. The jumpstart directory
from the jumpstart server is correctly mounted under /cdrom of the
machine to be installed. The rules and rules.ok file are world readable.
Here is some pertinent file info:
rules:
hostname uranus.bor.usg.edu - Profiles/dirserv.profile
Drivers/dirserv.driver
hostname pegasus.bor.usg.edu - Profiles/pegasus.profile
Drivers/pegasus.driver
rules.ok:
hostname uranus.bor.usg.edu - Profiles/dirserv.profile
Drivers/dirserv.driver
hostname pegasus.bor.usg.edu - Profiles/pegasus.profile
Drivers/pegasus.driver
# version=2 checksum=15128
/etc/bootparams entry:
uranus.bor.usg.edu
root=thor.bor.usg.edu:/jumpstart/OS/Solaris_9_2003-12/Solari
s_9/Tools/Boot install=thor.bor.usg.edu:/jumpstart boottype=:in
sysid_config=thor.bor.usg.edu:/jumpstart/Sysidcfg/Solaris_9
rootopts=:rsize=32768
The /etc/hosts and /etc/ethers file is correct as well (they would have
to be in order to get the initial networking info in order to boot up
from the miniroot). Also, in the /tftpboot directory here are the
entries for this system:
C64846BB.SUNW,SUN-FIRE-V240 -> inetboot.SUNW,SUN-FIRE-V240.Solaris_9-1
C64846BB -> inetboot.SUNW,SUN-FIRE-V240.Solaris_9-1
Okay, so any help here would be greatly appreciated. I've tried making
many changes (including adding an any entry at the end of the rules
file, using sun4u instead of SUNW,SUN-FIRE-V240) to no avail. The check
script runs with no errors or warnings.
Thanks in advance for the help,
Bob Jones
2. PCI SCSI & graphics card support for Linux
3. rules.ok doesn't match (Sol8-Jumpstart)
4. Mime error in Koffice
5. Jumpstart client doesn't find rules file
6. HELP: man!!
7. JumpStart Failing to find rules.ok
8. Anyone successfully using Motorola Bitsurfer for PPP dialout?
9. Help!!!Jumpstart keep looking for floppy for sysidcfg/rules.ok file !!!
10. Rules.ok file on jumpstart server
11. Jumpstart keep looking for floppy for sysidcfg/rules.ok file
12. solaris 10 3/05 jumpstart still won't find ypserv
13. 'Find' 'Updatedb' or find database replacement for Solaris 2.X?