TMS zl Management and Configuration Guide ST.1.0.090213

9-17
Routing
RIP
Poison Reverse
The TMS zl Module supports poison reverse, in which, when the module
receives a route to a network from a neighbor, it advertises a poison route
(metric 16) to that network back to the neighbor. This feature is intended to
prevent convergence problems by ensuring that routers do not advertise
routes back to the routers from which they received them.
Poison reverse is enabled by default. You can enable and disable poison
reverse from the CLI. See Appendix A, “Threat Management Services zl
Module Command-Line Reference.”
RIP Configuration
To configure RIP on the TMS zl Module, you must:
■ Enable RIP
■ Specify the interfaces that will participate in RIP
By enabling RIP on an interface, you enable the interface to exchange
routes with other RIP devices. On this interface, the TMS zl Module sends
updates that include the entire RIP routing table:
• All routes discovered by RIP
• All routes redistributed into RIP
If you want the TMS zl Module to advertise routes to its TMS VLANs, you
must redistribute connected routes (even if you have enabled RIP on
those VLANs).
You can also configure the following:
■ Redistribute connected, static, and OSPF routes into the RIP routing table
■ Configure passive interfaces to filter RIP messages
■ Configure RIP authentication on an interface
Note If you are configuring dynamic routing, but you want to configure a static
default route, you must configure the static default route first. Otherwise, the
module might receive a dynamic default route, preventing you from creating
your static default route. To remove the dynamic default route, you would
need to disable dynamic routing (RIP and OSPF), which you could re-enable
after configuring your static default route.
Follow these steps:
1. Click Network > Routing and click the RIP tab.