[Info-vax] satellite with more than one boot server

[Phillip Helbig---undress to reply]

In article <Bk3XXRgOnZgg at eisner.encompasserve.org>,
koehler at eisner.nospam.encompasserve.org (Bob Koehler) writes: 

>    Any MOP server that is serving MOP in the cluster can download the
>    image.  Any disk server that is serving the system disk can
>    complete the boot service.
> > 
> > Is there any reason not to configure a satellite to boot from more than 
> > one boot server in a given cluster?
> 
>    Having more than one provides redundancy, you can set up the
>    satellite so that it can run while either server is down.

So the satellite requests a MOP download and essentially any machine can 
serve this request.  OK.  Then the satellite requests a boot and any 
node which is configured can boot it.  Except for the ethernet address 
of the satellite, which of course is fixed, these configurations could
presumably be identical or completely different (SCSSYSTEMID, IP 
address, ALLOCLASS, SYS$SPECIFIC).  I'm not sure if I would prefer them 
to be identical or different.  If I opt for different, the only 
potential problem would be with TCPIP, and then only if I have common 
TCPIP configuration files (i.e. for all system disks in the cluster).  
IIRC, some node-specific TCPIP stuff is not in SYS$SPECIFIC but rather 
in SYS$COMMON (or, when properly set up, somewhere else, even off the 
system disk) with the node name used as a key.  Is this right?  If so, 
then at least the TCPIP configuration would have to be the same.