Cisco ASA Series Cli Configuration Manual page 703

Chapter 1 Configuring RIP
simultaneously attempting to update their neighbors. Each routing table entry has a route-timeout timer
associated with it. When the route-timeout timer expires, the route is marked invalid but is retained in
the table until the route-flush timer expires.
Using Clustering
For information about using clustering with RIP, see the
page
Licensing Requirements for RIP
The following table shows the licensing requirements for this feature:
Model License Requirement
All models Base License.
Guidelines and Limitations
This section includes the guidelines and limitations for this feature.
Context Mode Guidelines
Supported in single context mode only.
Firewall Mode Guidelines
Supported in routed and transparent firewall mode.
IPv6 Guidelines
Does not support IPv6.
Additional Guidelines
The following information applies to RIP Version 2 only:
•
•
•
Limitations
RIP has the following limitations:
•
1-9.
If using neighbor authentication, the authentication key and key ID must be the same on all neighbor
devices that provide RIP Version 2 updates to the interface.
With RIP Version 2, the ASA transmits and receives default route updates using the multicast
address 224.0.0.9. In passive mode, it receives route updates at that address.
When RIP Version 2 is configured on an interface, the multicast address 224.0.0.9 is registered on
that interface. When a RIP Version 2 configuration is removed from an interface, that multicast
address is unregistered.
The ASA cannot pass RIP updates between interfaces.
Licensing Requirements for RIP
"Dynamic Routing and Clustering" section on
Cisco ASA Series CLI Configuration Guide
1-3