Amer Networks E5Web GUI - Manual (Page 310)

Network The network consisting of the smaller routers.
Advertise If the aggregation should be advertised or not.
In most, simple OSPF scenarios, OSPF Aggregate objects will not be needed.
4.6.3.6. OSPF VLinks
All areas in an OSPF AS must be physically connected to the backbone area (the area with ID 0).
In some cases this is not possible and in that case a Virtual Link (VLink) can be used to connect to
the backbone through a non-backbone area.
cOS Core OSPF VLink objects are created within an OSPF Area and each object has the following
parameters:
General Parameters
Name Symbolic name of the virtual link.
Neighbor Router ID The Router ID of the router on the other side of the virtual link.
Authentication
Use Default For AS Use the values configured in the AS properties page.
Note: Linking partitioned backbones
If the backbone area is partitioned, a virtual link is used to connect the different parts.
In most, simple OSPF scenarios, OSPF VLink objects will not be needed.
4.6.4. Dynamic Routing Rules
This section examines Dynamic Routing Rules. These rules determine which routes can be
exported to an OSPF AS from the local routing tables and which can be imported into the local
routing tables from the AS.
4.6.4.1. Overview
The Final OSPF Setup Step is Creating Dynamic Routing Rules
After the OSPF structure is created, the final step is always to create a Dynamic Routing Rule on
each Clavister Security Gateway which allows the routing information that the OSPF AS delivers
from remote security gateways to be added to the local routing tables.
Dynamic routing rules are discussed here in the context of OSPF, but can also be used in other
contexts.
The Reasons for Dynamic Routing Rules
In a dynamic routing environment, it is important for routers to be able to regulate to what
extent they will participate in the routing exchange. It is not feasible to accept or trust all
Chapter 4: Routing
310