Cisco ASA Series Cli Configuration Manual page 636

Guidelines and Limitations
Failover Guidelines
OSPFv2 and OSPFv3 support Stateful Failover.
IPv6 Guidelines
•
OSPFv2 does not support IPv6.
•
OSPFv3 supports IPv6.
•
OSPFv3 uses IPv6 for authentication.
•
The ASA installs OSPFv3 routes into the IPv6 RIB, provided it is the best route.
•
OSPFv3 packets can be filtered out using IPv6 ACLs in the capture command.
Clustering Guidelines
•
OSPFv2 and OSPFv3 support clustering.
•
OSPFv3 encryption is not supported. An error message appears if you try to configure OSPFv3
encryption in a clustering environment.
•
In the spanned interface mode, dynamic routing is not supported on management-only interfaces.
•
In individual interface mode, make sure that you establish the master and slave units as either
OSPFv2 or OSPFv3 neighbors.
•
When you configure both OSPFv2 and EIGRP, you can use either spanned interface mode or
individual interface mode; you cannot use the two modes at the same time.
•
In individual interface mode, OSPFv2 adjacencies can only be established between two contexts on
a shared interface on the master unit. Configuring static neighbors is supported only on point-to
point-links; therefore, only one neighbor statement is allowed on an interface.
•
The router ID is optional in the OSPFv2, OSPFv3, and EIGRP router configuration mode. If you do
not explicitly set a router ID, then a router ID is automatically generated and set to the highest IPv4
address on any data interface in each of the cluster units.
•
If the cluster interface mode has not been configured, then only a single, dotted-decimal IPv4
address is allowed as the router ID, and the cluster pool option is disabled.
•
If the cluster interface mode is set to a spanned configuration, then only a single, dotted-decimal
IPv4 address is allowed as the router ID, and the cluster pool option is disabled.
•
If the cluster interface mode is set to an individual configuration, then the cluster pool option is
mandatory, and a single, dotted-decimal IPv4 address is not allowed as the router ID.
•
When the cluster interface mode is changed from a spanned to an individual configuration and vice
versa without specifying the check-detail or nocheck options, then the entire configuration
including the router ID is removed.
•
If any of the dynamic routing protocol router ID configurations are incompatible with the new
interface mode, then an error message appears on the console and the interface mode CLI fails. The
error message has one line per dynamic routing protocol (OSPFv2, OSPFv3, and EIGRP) and lists
the names of each context in which the incompatible configuration occurs.
•
If the nocheck option is specified for the cluster interface mode command, then the interface mode
is allowed to change although all the router ID configurations may not be compatible with the new
mode.
•
When the cluster is enabled, the router ID compatibility checks are repeated. If any incompatibility
is detected, then the cluster enable command fails. The administrator needs to correct the
incompatible router ID configuration before the cluster can be enabled.
Cisco ASA Series CLI Configuration Guide
1-4
Chapter 1 Configuring OSPF