
Configuring Remote Access
4-2 114084 Rev. A
Preparing Configuration and Image Files
Unless the router will use the default (generic) configuration file and software
image that ships on its local Flash memory card, you must create
• A unique configuration file for each remote router
• A uniform software image that all routers in your network can use
Creating Configuration Files
Prepare network configuration files as follows:
1. Use the Configuration Manager in local mode to create a configuration
file for each AN/ANH/ARN.
Refer to Configuring Routers for instructions. Also, refer to
• T
able 4-1 for the Site Manager module name to use when creating a
configuration file for BayStack AN routers
• T
able 4-2 for the module name to use when creating a configuration file
for BayStack ANH systems
• Tables 4-3 through 4-5 for the module names to use when creating a
configuration file for BayStack ARN routers.
2. Record the name of each configuration file and corresponding
AN/ANH/ARN for later reference when configuring network boot
options.
When you name configuration files, keep the following restrictions in mind:
• Bay Networks recommends that the operational configuration file for
each router be named config. If a router experiences a power failure, it
boots from the file called config once power returns. However, the
configuration files that you save on a BOOTP server for Directed Netboot
do not have to be named config because you specify the configuration file
pathname (refer to the Site Manager parameter “Boot Conf
ig Pathname.”)
• Configuration filenames must begin with an alphabetical character. The
remaining characters must be alphanumeric and may also include the
underscore (_) character. You cannot use spaces.
Comentarios a estos manuales