TMS zl Management and Configuration Guide ST.1.2.100916

1-68
Overview
Routing
By default, the TMS zl Module does not redistribute routes to its own con-
nected interfaces. In other words, the module only advertises routes to the
interfaces on which you enable RIP. However, you can configure the module
to redistribute connected routes as well as static routes and routes discovered
through OSPF. You can configure the metric for redistributed routes, but all
types of redistributed routes have the same metric.
By default, the TMS zl Module firewall allows all RIP updates between any
zone and the Self zone. For greater security, the TMS zl Module supports these
types of RIP authentication:
■ Simple password
■ MD5
You can also modify firewall access policies to further secure routing mes-
sages.
For more information and for instructions on configuring this feature, see
“RIP” in Chapter 9: “Routing.”
OSPF
The TMS zl Module supports all fives types of OSPF Link State Advertisements
(LSAs). You can place one or more TMS interfaces (TMS VLANs or GRE
tunnels) in one or more of these types of OSPF areas:
■ Backbone area and normal areas
■ Stub areas
Stub areas connect only to the backbone. They receive summary routes
to other areas (type 3 LSAs) instead of advertisements to specific net-
works in other areas.
■ Not so stubby areas (NSSAs)
NSSAs are stub areas that are allowed to receive external and redistrib-
uted routes (type 5 LSAs). NSSAs are typically used so that a stub area
can provide the connection to the Internet.
When you enable OSPF on an interface, you specify the area ID for that
interface, which also creates the area. You must then define the area as stub
or NSSA. If the area is the backbone (area ID 0) or a normal area, you do not
have to perform any configuration beyond specifying the ID when you enable
OSPF on an interface.