Configuring Active Rip; Defining Routes - Bay Networks Baystream 7 Configuration And Troubleshooting Manual

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

Advertisement

Configuring and Troubleshooting Bay Dial VPN Services
admin: quit
command: boot
The
Annex's operational code. Setting the load_broadcast parameter to N directs the
Annex to look for the load image only on the specified load host.
If a load host has a different network or subnet address, you must define a gateway
through which the Annex can reach the host. The
specifies the Internet address for that gateway.
During the initial boot of the operational code, the ROM monitor requires the
address of a gateway if the specified load host is on another network or has a
different subnet address. In this case, enter the gateway's address using the ROM
Monitor
table.
Configuring Active RIP
The following section assumes you have read the sections on active and passive
RIP in the Remote Annex Administrator's Guide for UNIX. Active RIP is enabled
by default. Once active RIP is enabled, both passive and active RIP are running on
all operational interfaces.
Defining Routes
Once you have enabled active RIP, you do not need to define the default and static
routes in most configurations. The network nodes learn about the routes to each
other and to other networks through RIP updates they exchange, provided that all
of the following conditions are met:
4-8
parameter specifies the name of the image file that contains the
image_name
command. The Annex automatically adds this gateway to its routing
addr
For subnetted networks, the
Annex is set to
Y
, (the default)
You have configured subnet masks correctly
The gateway is configured to handle the same type of RIP updates.
BayStream Multiservice Software Version 7.2
load_dump_gateway
rip_sub_advertise
parameter on the Remote
parameter
115623B Rev. 00

Advertisement

Table of Contents
loading

This manual is also suitable for:

Remote annexBaydvsBay dial vpn

Table of Contents