This is a discussion on Jumpstart Problems within the Sun Solaris Administration forums, part of the Solaris Operating System category; --> All-- First, apology for my lack of detail here, the issue is on some work boxes which I'm not ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| All-- First, apology for my lack of detail here, the issue is on some work boxes which I'm not in front of ... but I'll try to provide as much as I can. Basically I'm getting client RPC timeouts on the install_config parameter and it seems like my rules.ok file is being ignored. I've scoured docs.sun.com/Sunsolve/Google for solutions and think I've tried most pointers/solutions around. I set up both a Solaris 9 and 10 boot/config/install servers (each is all-in-one) on a /24 network and can not, for the life of me, get a client to find the supplied jumpstart directory. It picks up the boot and sysidcfg just fine. Thereafter it ends up stating: .... Searching for JumpStart directory... not found Warning: Could not find matching rule in rules.ok .... And thereafter says to hit wants to go into interactive install. I ran a 'add_install_client' for the test box with the -i, -e, -c and -p options (and in varying combinations). I'm sysidcfg'ing the box with all the reqs, DNS, and interface hostname/ip/netmask/router (client and server are configured for a /24). The jumpstart directory is shared out anon=0 and ro as stated in the docs. I even isolated the client and server on a small switch and still no-go (I suppose I should segment them to a /30 maybe). I just simply don't see where/when the install_config is being asked for. and ... I'm a few handfuls of hair away from being bald. TIA! Ben-- |
| |||
| Ben schrieb: > All-- > > First, apology for my lack of detail here, the issue is on some work > boxes which I'm not in front of ... but I'll try to provide as much as I > can. > > Basically I'm getting client RPC timeouts on the install_config > parameter and it seems like my rules.ok file is being ignored. I've > scoured docs.sun.com/Sunsolve/Google for solutions and think I've tried > most pointers/solutions around. > > I set up both a Solaris 9 and 10 boot/config/install servers (each is > all-in-one) on a /24 network and can not, for the life of me, get a > client to find the supplied jumpstart directory. It picks up the boot > and sysidcfg just fine. Thereafter it ends up stating: > > ... > Searching for JumpStart directory... > not found > Warning: Could not find matching rule in rules.ok > ... > > And thereafter says to hit wants to go into interactive install. > > I ran a 'add_install_client' for the test box with the -i, -e, -c and -p > options (and in varying combinations). > > I'm sysidcfg'ing the box with all the reqs, DNS, and interface > hostname/ip/netmask/router (client and server are configured for a /24). > > The jumpstart directory is shared out anon=0 and ro as stated in the > docs. > > I even isolated the client and server on a small switch and still no-go > (I suppose I should segment them to a /30 maybe). I just simply don't > see where/when the install_config is being asked for. > > and ... I'm a few handfuls of hair away from being bald. > > TIA! > > Ben-- Hello, check the required files: 1. /etc/bootparams -> suddenly change the server-name by his ip-number 2. /etc/inet/hosts -> numbers and hosts correct? 3. sysidcfg -> netmask and ip-number okay? 4. Try snoop on the install-server and watch the messages form the client. Good luck. Klaus Grote DNS GmbH |
| |||
| In message <42AF82F8.695762BF@en-ninguna-parte.com>, Ben <ben@en-ninguna-parte.com> writes > >I'm sysidcfg'ing the box with all the reqs, DNS, and interface >hostname/ip/netmask/router (client and server are configured for a /24). > Ben Try removing the hostname / ip from your sysidcfg and putting them in /etc/hosts of the install server. I saw the same last week and this worked. -- Clelland Ferguson |
| |||
| klaus.grote@web.de wrote: > > Ben schrieb: > > All-- > > > > First, apology for my lack of detail here, the issue is on some work > > boxes which I'm not in front of ... but I'll try to provide as much as I > > can. > > > > Basically I'm getting client RPC timeouts on the install_config > > parameter and it seems like my rules.ok file is being ignored. I've > > scoured docs.sun.com/Sunsolve/Google for solutions and think I've tried > > most pointers/solutions around. > > > > I set up both a Solaris 9 and 10 boot/config/install servers (each is > > all-in-one) on a /24 network and can not, for the life of me, get a > > client to find the supplied jumpstart directory. It picks up the boot > > and sysidcfg just fine. Thereafter it ends up stating: > > > > ... > > Searching for JumpStart directory... > > not found > > Warning: Could not find matching rule in rules.ok > > ... > > > > And thereafter says to hit wants to go into interactive install. > > > > I ran a 'add_install_client' for the test box with the -i, -e, -c and -p > > options (and in varying combinations). > > > > I'm sysidcfg'ing the box with all the reqs, DNS, and interface > > hostname/ip/netmask/router (client and server are configured for a /24). > > > > The jumpstart directory is shared out anon=0 and ro as stated in the > > docs. > > > > I even isolated the client and server on a small switch and still no-go > > (I suppose I should segment them to a /30 maybe). I just simply don't > > see where/when the install_config is being asked for. > > > > and ... I'm a few handfuls of hair away from being bald. > > > > TIA! > > > > Ben-- > > Hello, > > check the required files: > 1. /etc/bootparams -> suddenly change the server-name by his ip-number No, that was static throughout the trials. > 2. /etc/inet/hosts -> numbers and hosts correct? Positively, they were correct. Backward, forward, up, down etc. > 3. sysidcfg -> netmask and ip-number okay? Netmask is/was good. See my post below wrt the ip_address option. > 4. Try snoop on the install-server and watch the messages form the > client. Snooped ad nauseum. > > Good luck. Thanks. Got a solution, see below in the thread. > Klaus Grote > DNS GmbH |
| ||||
| Ben wrote: > > All-- > > First, apology for my lack of detail here, the issue is on some work > boxes which I'm not in front of ... but I'll try to provide as much as I > can. > > Basically I'm getting client RPC timeouts on the install_config > parameter and it seems like my rules.ok file is being ignored. I've > scoured docs.sun.com/Sunsolve/Google for solutions and think I've tried > most pointers/solutions around. > > I set up both a Solaris 9 and 10 boot/config/install servers (each is > all-in-one) on a /24 network and can not, for the life of me, get a > client to find the supplied jumpstart directory. It picks up the boot > and sysidcfg just fine. Thereafter it ends up stating: > > ... > Searching for JumpStart directory... > not found > Warning: Could not find matching rule in rules.ok > ... > > And thereafter says to hit wants to go into interactive install. > > I ran a 'add_install_client' for the test box with the -i, -e, -c and -p > options (and in varying combinations). > > I'm sysidcfg'ing the box with all the reqs, DNS, and interface > hostname/ip/netmask/router (client and server are configured for a /24). > > The jumpstart directory is shared out anon=0 and ro as stated in the > docs. > > I even isolated the client and server on a small switch and still no-go > (I suppose I should segment them to a /30 maybe). I just simply don't > see where/when the install_config is being asked for. > > and ... I'm a few handfuls of hair away from being bald. > > TIA! > > Ben-- Klaus/Clelland/All-- Pulling the hostname and ip_address options from the sysidcfg:network_interface option-list was the solution. BTW, I was/am set on the hosts entries. It appears that later in the cycle, those items may somehow stomp on the otherwise previously configured variables/config set up at boot and cause it to go south. I found a Sun Mgrs post which stated that as a possible cause/solution, although it wasn't the answer for the poster. In any event, removing those two bits worked like a charm. Apart from the hostname/ip_address sysidcfg options I was good on what the other posters mentioned. Thanks for the suggestions! Ben-- |