TMS zl Management and Configuration Guide ST.1.1.100430

1-67
Overview
Routing
Routing
When it operates in routing mode, the TMS zl Module must be able to route
the traffic that it is filtering and analyzing for threats. The module’s VPN
capabilities also require the module to know the correct routes.
The module supports these routing capabilities:
■ Static routing
■ Routing Information Protocol (RIP)
■ Open Shortest Path First (OSPF)
The TMS zl Module supports up to 10,000 total route entries, including static
and dynamic routes.
Static Routing
The TMS zl Module automatically routes traffic between connected VLANs.
You can add three types of static routes:
■ Default route (through the default gateway)
You can create more than one default route. The route with the lowest
administrative distance (or that has the lowest metric and is tied for the
lowest administrative distance) is preferred.
Multiple default routes are useful when a GRE tunnel is the forwarding
interface for the default route, and you want create a secondary route
through a standby tunnel.
■ Routes to particular hosts
■ Routes to networks
When creating a static route, you can set the metric and administrative
distance, making it possible to create floating static and default routes.
RIP
The TMS zl Module supports RIP versions 1 and 2. You can choose the version
for messages that are sent and received on each interface (VLAN or GRE
tunnel). However, the module does not support RIP compatibility mode, so
you must make sure to set the correct version. The module does support
passive interfaces, which are interfaces that receive, but do not advertise,
routing updates.