Only one person responded to this posting and it was correct. Our thanks
to Kevin Amorin who
provided the solution.
The client and it's boot server reach a point in their conversation in which
the client needs to reach it's
install server (in our case on another subnet). Within the rcS script,
/usr/sbin/hostconfig -p bootparams
issues a request to the bootparamd server, which replies with several items,
among which is a default route
that the client needs to reach outside the subnet (to its install server).
Use the following options to hostconfig
to check the response of any bootparamd service:
# /usr/sbin/hostconfig -p bootparams -d -n -v
If the bootparamd server doesn't respond with a route, you must add the
default route to the boot server's
/etc/defaultrouter file and/or manually add the default route with the route
command:
/etc/defaultrouter:
192.168.2.254 192.168.3.254
ORIGINAL POST:
>Our Jumpstart boot server and install server reside on different subnets
and we use static routing. During the client boot in >the rcS init step,
the network interface is configured (rev-arp), but the system later
hangs/pauses because it cannot connect >to its install server (which is on a
different subnet).
>We've had to modify rcS so that it adds a default route to the install
server's subnet after the interface is configured to solve >this problem.
This is true for Solaris 2.6, 7, and 8.
FROM KEVIN:
>during the boot process the client machine does a
>"whoami" request and the boot server responds with config info including
>the default router of that server. A problem arises if the boot server is
>multi-homed as some clients will receive the wrong default route. To fix
>this add a multiple default route entries to /etc/defaultrouter and touch
>/etc/norouter so that packets will not get routed between the various
>interfaces. The client will then receive the correct defaultroute for the
>subnet on which it is on. Hope this helps. If you have a chance please
>summarize as someone had a similar question a bit back.
S
U BEFORE POSTING please READ the FAQ located at
N ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/faq
. and the list POLICY statement located at
M ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/policy
A To submit questions/summaries to this list send your email message to:
N sun-managers@sunmanagers.ececs.uc.edu
A To unsubscribe from this list please send an email message to:
G majordomo@sunmanagers.ececs.uc.edu
E and in the BODY type:
R unsubscribe sun-managers
S Or
. unsubscribe sun-managers original@subscription.address
L To view an archive of this list please visit:
I http://www.latech.edu/sunman.html
S
T
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:16 CDT