Loading Software And Booting The Remote Annex; Configuring The Annex To Accept Rip 1 And/Or Rip 2 Packets - Bay Networks Baystream 7 Configuration And Troubleshooting Manual

Bay dial vpn services
Hide thumbs Also See for Baystream 7:
Table of Contents

Advertisement

Loading Software and Booting the Remote Annex

The Annex gets its operational code by downloading it over the network from
(among other sources) a UNIX host that runs Annex file server software. The
Annex boots each time it is powered up and whenever it receives a
command. You specify the source of the boot image by setting the preferred load
host.
Note: The actual installation procedures are different for a self-booting
Remote Annex (which already has an image loaded into it). Refer to the
readme file in the setup subdirectory of the Annex Host Tools install directory
for a complete description of how to install Annex software.
To load the Remote Annex software you must use the command line interface.
Refer to
with examples, of loading software and booting the Remote Annex using that
interface. The same chapter also describes and illustrates what you must do to set
Annex security and set the port parameters for Dial VPN.
Configuring the Annex to Accept RIP 1 and/or RIP 2 Packets
The Remote Annex Administrator's Guide for UNIX lists the syntax and options
for all the RIP configuration parameters. Before you change any default settings,
read the sections of that manual explaining the purposes for and consequences of
such changes.
When you configure the Remote Annex, you have to decide how the Annex will
communicate with the TMS. This can be by means of a static route, RIP, or even
the default compatibility mode. Then you configure the environment, as described
in the Remote Annex Administrator's Guide for UNIX, the Remote Annex 6300
Supplement to the Remote Annex Administrator's Guide for UNIX, or Managing
Remote Access Concentrators Using Command Line Interfaces.
The Annex's default RIP configuration accepts both Version 1 and Version 2
packets, making no distinction between Version 2 broadcast and multicast packets.
In most cases, do not change this default configuration, because some nodes on
your network may be configured for RIP Version 1, and accepting Version 2
packets as well does no harm. If all nodes on your network run only Version 2,
you may want to set some or all of the Annex interfaces to accept only Version 2
packets because RIP 2:
115623B Rev. 00
Chapter 4, "Configuring the Remote
BayStream Multiservice Software Version 7.2
Using Quick2Config and Annex Manager
Annex," for a complete description,
boot
C-6

Advertisement

Table of Contents
loading

This manual is also suitable for:

Remote annexBaydvsBay dial vpn

Table of Contents