System information

Remote Servers and Split Boot Servers
123
4.5.1.2 Remote Boot with Centralized Configurations
This example, is perhaps the most common configuration (see Figure 33).
Figure 33. Remote Reboot with Centralized Configurations
By deploying a boot server at each remote site, we get better usage of the
remote and local bandwidth available. We use the remote bandwidth to get
the configuration files from the central server and the local LAN to get the
base code. In this scenario, the user configuration settings are still centralized
on the main server.
The advantages of this strategy are:
• Centralized configuration management
• Lower bandwidth connection
• Faster boot
The disadvantages for this strategy are:
• More hardware is needed
• Somewhat decentralized (more servers to manage, potentially one per
site)
Distributed Configuration
ConfigurationFiles
Authentication
Central Site
Networkstations
Remote Sites
NSM
High Speed
Connection
(T1 or better)
Boot Code
Boot Code
Boot Code