The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to configure EIGRP IPV6 on Cisco Adaptive Security Appliance (ASA).
Min Supported Manager Version |
Managed Devices |
Min Supported Managed Device Version Required |
Notes |
ASA |
All ASA platforms |
9.20.1 |
CLI |
CSM |
All ASA platforms |
4.27 |
CSM GUI |
ASDM |
All ASA platforms |
7.20.1 |
ASDM GUI |
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and hardware versions:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
• EIGRP is already supported and available on ASA. The demand for EIGRP IPV6 is increasing.
• The configuration for EIGRPv4 and EIGRPv6 are similar, but they can be configured and managed independently.
• Due to differences in protocols, configuration and operation differ slightly.
• In earlier releases EIGRP was supported only for IPv4 and from ASA 9.20 onwards, EIGRP would be supported with IPV6.
• Support for EIGRP IPv6 with link-local address on ASA only.
• EIGRPv6 is currently supported on ASA only on routed mode, HA, and cluster.
• EIGRPv6 neighborship can be enabled only with link local address.
• Transparent mode
• Multi Context
• Authentication
• On FTD
• EIGRP for IPv6 uses the same framework as EIGRP for IPv4.
• EIGRP IPv6 would communicate only with IPv6 peers and advertise only IPv6 routes.
EIGRP IPV4 and EIGRP IPv6 share similar characteristics as well like:
• Neighbor, routing, and topology tables are maintained.
• It uses DUAL stack for fast convergence and loop free network.
The differences are:
• The network command under router-mode is not used for EIGRP IPv6.
• Use ipv6 router eigrp <AS> to enable EIGRP IPV6 router process.
• Explicitly configure ipv6 eigrp <AS> to enable EIGRP IPv6 on specific interface.
• User configured IPv6 address cannot be used to establish neighborship.
• Authentication is not supported in current release.
• EIGRP for IPv6 would be same as EIGRP IPv4.
• EIGRP uses the Diffusing Update Algorithm (DUAL) to achieve rapid convergence.
DUAL not only calculates the best routes but also loop free routes.
There are mainly two tables used by DUAL to for calculation of best route. They are neighbor routing table, topology table.
DUAL calculates alternative path based on reported feasible distance.
• The neighbor table keeps track of all directly connected neighbors. Hello packets are used to check that status of neighbor.
• Topology table keeps information on metrics of all routes in the network. Successor and feasible successor keep the best path and alternate path information.
Hello messages are used to discover neighbor before establishing adjacency.
Update messages are exchanged between neighbors to build topology table and routing table.
Query messages are sent to other EIGRP neighbors for a feasible successor when DUAL is re-computing a route in which the firewall does not have a feasible successor.
Reply messages are sent as the response to an EIGRP Query packet.
Acknowledge messages are used to acknowledge EIGRP Updates, Queries, and Replies.
EIGRP IPv6 uses a Hello packet to discover other EIGRP-capable devices on directly attached links and to form neighbor relationships.
EIGRP IPv6 transmits Hello packets with a source address being the link-local address of the transmitting interface.
Hello messages are like keep alive messages to keep track of the neighbor status.
Default timer of hello message is 5 seconds. Upon Hello message exchange, an update message is received and sent. This is used to build the topology table and install the routes in the RIB accordingly.
To establish neighborship, router mode config is needed. It is the same for IPv4 except for the config starts with IPv6 keyword.
It also needs to attach the participating interface to autonomous system.
Neighborship can be formed in two ways, using either multicast or unicast.
You have simply directed connected topology and configuration for unicast and multicast neighborship.
show ipv6 eigrp neighbors is used to check the neighborship state.
ciscoasa(config-rtr)# show ipv6 eigrp neighbors
EIGRP-IPv6 Neighbors for AS(50)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
1 Link-local address: m3 12 1w3d 270 1620 0 153 fe80::250:56ff:fe9f:e7e8
0 Link-local address: m2 12 1w3d 174 1044 0 152 fe80::250:56ff:fe9f:8d83
ciscoasa(config-if)# ipv6 hello-interval eigrp 100 ?
interface mode commands/options:
<1-65535> Seconds between hello transmissions
ciscoasa(config-if)#
ciscoasa(config-if)# ipv6 hold-time eigrp 200 ?
interface mode commands/options:
<1-65535> Seconds before neighbor is considered down
ciscoasa(config-if)#
ciscoasa(config-rtr)# passive-interface ?
ipv6-router mode commands/options:
Current available interface(s):
default Suppress routing updates on all interfaces
g0 Name of interface GigabitEthernet0/0
mgmt Name of interface Management0/0
ciscoasa(config-rtr)#
ciscoasa(config-rtr)# distribute-list prefix-list abc ?
ipv6-router mode commands/options:
in Filter incoming routing updates
out Filter outgoing routing updates
ciscoasa(config-rtr)#
ciscoasa(config-rtr)# redistribute ?
ipv6-router mode commands/options:
bgp Border Gateway Protocol (BGP)
connected Connected Routes
eigrp Enhanced Interior Gateway Routing Protocol (EIGRP)
isis ISO IS-IS
ospf Open Shortest Path First (OSPF)
static Static Routes
ciscoasa(config-rtr)#
The configuration for Multicast router mode is similar to that for Unicast Router Mode.
1. None
2. Default
3. Specific Interface
EIGRP IPv6 Filter Rules Tab
Show ipv6 eigrp events
show ipv6 eigrp events displays important event logging in the systems which are helpful in debugging.
ciscoasa(config-rtr)# show ipv6 eigrp events
Event information for AS 50:
1 18:05:56.203 Metric set: 1001::/64 768
2 18:05:56.203 Route installing: 1001::/64 fe80::250:56ff:fe9f:e7e8
4 18:05:56.203 FC sat rdbmet/succmet: 768 512
5 18:05:56.203 Rcv update dest/nh: 1001::/64 fe80::250:56ff:fe9f:e7e8
6 18:05:56.203 Change queue emptied, entries: 1
7 18:05:56.203 Metric set: 1001::/64 768
8 18:05:56.203 Update reason, delay: new if 4294967295
Show ipv6 eigrp timers
show ipv6 eigrp timers shows the current hello timer and the hold timer applied.
ciscoasa(config-rtr)# show ipv6 eigrp timers
EIGRP-IPv6 Timers for AS(50)
Hello Process
Expiration Type
| 0 .406 (parent)
| 0 .406 Hello (m2)
Update Process
Expiration Type
| 11.600 (parent)
| 11.600 (parent)
| 11.600 Peer holding
| 11.930 (parent)
| 11.930 Peer holding
Show ipv6 eigrp topology
show ipv6 eigrp topology The topology table consists of all destinations advertised by a neighboring router.
ciscoasa(config-rtr)# show ipv6 eigrp topology
EIGRP-IPv6 Topology Table for AS(50)/ID(172.27.173.103)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 1001::/64, 1 successors, FD is 768, serno 8907
via fe80::250:56ff:fe9f:8d83 (768/512), m2
P 3001::/64, 1 successors, FD is 768, serno 8906
via fe80::250:56ff:fe9f:8d83 (768/512), m2
P 2001::/64, 1 successors, FD is 768, serno 8905
via fe80::250:56ff:fe9f:8d83 (768/512), m2
Show Tech for EIGRP
Show tech can be used for troubleshooting as it collects useful information including timer parameters, neighborship details, traffic statistics for EIGRP, memory usage counters, and others.
ciscoasa(config-if)# show eigrp tech-support detailed ?
exec mode commands/options:
| Output modifiers
<cr>
ciscoasa(config-if)#
Problem Seen with Neighbor Formation
Revision | Publish Date | Comments |
---|---|---|
2.0
|
19-Jul-2024
|
Updated Formatting.
|
1.0
|
18-Jul-2024
|
Initial Release
|
Revision | Publish Date | Comments |
---|---|---|
1.0 |
29-Jul-2024 |
Initial Release |