Christine Tran wrote:
Update.  (I'm keeping this thread here, instead of moving to
[EMAIL PROTECTED], to finish it out.)

I ripped out SUNWjet 4.1.0 and installed latest, 4.4.4, and the weird
refusal to make an nbp.SUNW.i86pc went away.  I'm working off Dan
Mick's "PXE netboot for x86 clients" and I have a couple of follow-on
questions.
Dan Mick's primer is great, but don't mix and match. JET will do all your dhcp config for you.

BTW, 4.4.4 will allow you to set dhcp, and will revert to grub automatically if available. Could you send the output of make_client using 4.4.4?
I don't have a DHCP net table, pntadm -P <my network> is blank.
Should I have something here?
You should. You needed to edit the /opt/SUNWjet/Products/base_config/solaris/make_dhcp script with your network information before running it.

Failing that, if the network is not defined, and the client template contains the defaultrouter entry, it will create the network macro for you.
My client and server are on same segment, a 10 network.  It's just my
automated install network, not used for anything else.  The server has
another interface, the default router and the rest of the world is
this way.

dhtadm shows my macro has having a router entry, with my non-10
default router.  I was expecting this to be blank.  Would this confuse
my client or my server, having this router set in here?  It shouldn't
ever be needed.
Which macro?
Can you send output of:
dhtadm -P
and
pntadm -P 10.0.1.0

C maimed-by-macros T
_______________________________________________
sysadmin-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
sysadmin-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss

Reply via email to