Download Avaya Configuring BayStack Remote Access User's Manual

Configuring BayStack Remote Access
Selecting the Routine Startup Option
This section provides information to help you select the boot configuration for
routine startup operations.
Recommendations
Bay Networks recommends that you do the following:
•
Maintain the complete software image file (an.exe or arn.exe) on the local file
system at all times, in case the network connection to the BootP server goes
down and the BayStack router needs to use Local Boot for startup.
•
Set up the network to support Netboot even if you plan to use the Local Boot
option. With the network set up to support Netboot, you can boot the
BayStack router over the network for some procedures and boot it locally for
others.
Netboot
Netboot takes longer than the other startup options, but has many benefits.
Note: Over a low-speed WAN, or after configuring the BayStack router to run
several protocols, netbooting can take up to 15 minutes. It takes less time to
netboot only the kernel file or configuration file.
Using Netboot for routine startups allows you to:
•
Manage software image and configuration files from a remote location by
storing them on the BootP server
This option greatly simplifies the management of remote routers by allowing
you to keep the startup files up-to-date in a single location -- the BootP server.
•
Minimize the need to maintain the BayStack router’s local file system
When the BayStack router obtains files from a BootP server, it stores them in
memory, not in its file system, reducing the need for frequent file-system
compactions. (See Using Technician Interface Software or Configuring and
Managing Routers Using Site Manager to learn about compacting a file
system.)
1-16
117341-B Rev. 00