Specifications

1.2.4 NetBoot Settings
In Server Admin, click on the NetBoot item. You should see an overview
status of the other services that NetBoot depends on. Ensure that these services
are shown as running (except DHCP, if your network already has a DHCP
server).
Click on the Settings tab at the bottom of the window. Under the General
tab, you’ll have a few choices on how to store client data and images. Note
that ”images” here refers to images that the clients will boot off of, not system
restore images.
Check the box(es) for the drives you wish to use for the different types of data.
If possible, split up the data between drives (this helps with speed).
At this point, you don’t have any images to serve via NetBoot, so there are
no other settings to change. See the next section for information on creating a
NetBoot image that clients can start up from.
1.2.5 Network Settings
If you’re booting your clients on the same subnet as the server, you should be
set to go. However, if you’re going to be booting accross subnets, you’ll need to
do a little more work.
Because NetBoot discovery requests are sent from the client using DHCP, pack-
ets from the client must be forwarded on to the server. If you have Cisco equip-
ment, you must use the ip helper-address statement in your router configu-
ration to forward the packets.
For example, if your server is on VLAN 10 with IP address 172.16.10.100 and
your client is on VLAN 20, your configuration should look something like this:
interface Vlan10
description Server VLAN
ip address 172.16.10.1
interface Vlan20
description Client VLAN
ip address 172.16.20.1
ip helper-address 172.16.10.100
This tells the router to forward broadcast packets accross VLANs to the address
you specify. By default, DHCP packets are forwarded, along with other common
broadcast traffic. See your network equipment manuals for more information on
the default forwarded ports.
7