I'm having problems with the client portion of the Oscar 2.1
installation procedure.  
I can follow the documentation without a problem, and have attempted to
perform PXE boot, and BootDisk boot disk.

Server Node:  Sun LX-50 (intel Chip)
Client Nodes:  2 x IBM NetVista desktop machines (new - did not check
for compatability though)
Hub:  3 Com 10/100 Hub (not switch)
Linux Dist:  Red Hat Linux 7.3

Installed the 'Everything' installation on the Sun LX-50.  eth0 is the
public network (10.1.x.x), and eth1 is private network (192.168.1.x). 
Using 'root' as the only user on the system (during testing).  Download
the current Oscar package to /root.  Extracted.  set my OPD.  Updated
OPDs.  Ran ./install_cluster eth1 from the /root dir.  Left GUI steps 1,
2, & 3 default.  Changed step 4 for IDE drives, and verified correct
pathnames.  Captured MAC addresses, and assigned them to client nodes. 
Configured DHCP server, and verified the dhcpd.conf file for accuracy. 
Attempted to load image to clients...now I have the problems.

PXE Boot:
initial reading of screen shows correct IP address is mapped to
client...goes through the process, and tries to get an IP address for
loopback adapter, and then can't continue....What am I doing wrong
here?

BootDisk:
ran mkautoinstalldiskette -config /root/oscar_boot (which contains info
fromt the install guide pg 36).  System boots off the disk, but can't
find local.cfg.  Should I make local.cfg, and what should it contain.

Thanx in advanced.

Mark Gabryjelski
Systems Engineer
Expert Server Group
318 South River Road
Bedford, NH 03110
Phone:  (603) 668-9800 x5232
==============================
A+, CCDP, CCNP, CNE, MCSE, SCNA
Sun Certified Data Management Engineer VxVM
HP Master ASE - SAN Architect



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users

Reply via email to