[SUMMARY] JumpStart accross VLANs ...

From: Wilkinson, Alex <alex.wilkinson_at_dsto.defence.gov.au>
Date: Sun Oct 23 2005 - 08:16:49 EDT
Thanks To:

Al Saenz
Donovan, Jeffrey
Hudes, Dana
Bhaskara, Srikalyan
Matt Clausen
Charles Gagnon
Matthew Stier
Angelo McComis
Ricardo Meleschi

Solaris 10 Solution:

WANBoot i.e over HTTP:

Solaris 7/8/9 Solution:

"It is quite simple if you have control over the router or the people
 who control the router are cooperative. You need to configure the router
 as a BOOTP/DHCP relay agent. Obviously, the router needs to attach to the
 VLANs in question as well as be able to reach the network on which the
 jumpstart server is located. "


"The biggest problem with jumpstart is the need to tftpboot a host via
 the ARP/RARP protocol (which I imagine is what you're using). Since
 ARP/RARP doesnt cross router boundries, this is why a tftpboot server
 is required in each VLAN/Subnet that has hosts needing jumpstarts in.
 Now supposedly using the DHCP mechanism instead of the ARP/RARP method
 allows you to bypass this, but I personally have never gotten it
 working. DHCP supports directing a client directly to the tftp server
 without the need of doing a ARP/RARP MAC <--> IP assignment then
 loading the bootstrap."


"Not to my knowledge. I currently VLANs for this. If your network
supports VLANs (802.1Q trunks or other types) you can setup your
jumpstart server with a trunk, allowing it to respond on multiple
from requests on multiple VLANs (so networks)."

"You only need one Jumpstart Install server, but you need a Jumpstart
Boot server on each network.  (The diskless client boot code in the
OpenBoot Prom, is incapable of working across networks, however, once
client can load a minimal operating system off the Boot server, it can
connect across a router, to the Install server.

If you want an all in one solution, put a multiport network interface
card in the Jumpstart Install server and have it connect each network.
(Ensure that IP forwarding is disabled, so the Install server doesn't
become a router.)"


"The way Jumpstart works, it is not possible for the traffic to cross
VLANs, because during the jumpstart process, the systems are not
communicating with TCP/IP, they are only speaking at the MAC address
layer (also known as Layer 2). Layer 2 traffic cannot be routed,
(routing occurs at Layer 3) thus the need to be connected as you are


"We have a single jumpstart server with multiple network interfaces,
and we have an active interface on every network we need to jumpstart
servers from...

It's technically not the same as jumpstarting across vlans, but it
works and only requires additional network ports, not an additional
jumpstart server."

Thanks to all those that replyed to my question.

sunmanagers mailing list
Received on Sun Oct 23 08:23:23 2005

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:52 EST