www.howtonetwork.org

CCNA & CCNP Certifcation Training

  • About
  • Contact
  • FAQ
  • Join
  • Home
  • CCNA
    • ICND1
    • ICND2
    • 101 CCNA LABS
  • CCNP
    • ROUTE
    • SWITCH
    • TSHOOT
    • 101 CCNP LABS
  • CompTIA
    • Security+
    • Network+
  • Design
    • CCDA
    • CCDP
You are here: Home / TSHOOT / Module 10 / Understanding and Troubleshooting EIGRPv6

Understanding and Troubleshooting EIGRPv6

EIGRPv6 retains the same basic core functions as EIGRPv4. For example, both versions still use DUAL to ensure loop-free paths, and both protocols use Multicast packets to send updates – although EIGRPv6 uses IPv6 Multicast address FF02::A instead of the 224.0.0.10 group address used by EIGRPv4. While the same core fundamentals are retained, there are some differences between these versions. Table 10-2 lists the differences between EIGRPv4 and EIGRPv6, or simply and more commonly between EIGRP for IPv4 and EIGRP for IPv6.

Protocol Characteristic EIGRP For IPv4 EIGRP For IPv6
Automatic Summarization Yes Not Applicable
Authentication or Security MD5 Built into IPv6
 Common Subnet for Peers Yes No
Advertisement Contents Subnet/Mask Prefix/Length
Packet Encapsulation IPv4 IPv6
Tab. 10-2. EIGRPv4 and EIGRPv6 Differences

Given the similarity of EIGRPv4 and EIGRPv6, the troubleshooting approaches for both of these protocols are also very similar. For example, EIGRPv6 still requires that the same autonomous system number be used in order for a neighbor relationship to be established. In addition to this, other EIGRP parameters such as authentication configuration and K values should also be the same; otherwise EIGRPv6 will not establish a neighbor relationship with peer routers.

However, there are some subtle differences because of the manner in which these two protocols operate and are configured that you should be familiar with. The first is that while there is no explicit configuration to enable the EIGRPv4 routing process; by default, when EIGRPv6 is enabled, the protocol defaults to a shutdown state in Cisco IOS software. This default state is displayed when you issue the show ipv6 eigrp neighbors command as is shown below:

R1#show ipv6 eigrp neighbors
IPv6-EIGRP neighbors for process 1
% EIGRP 1 is in SHUTDOWN

Alternatively, the default state is also displayed when you parse through the configuration as is illustrated in the following output:

R1#show running-config | section eigrp
ipv6 eigrp 1
ipv6 router eigrp 1
shutdown

When configuring EIGRPv6, you must issue the no shutdown router configuration command to enable the routing process. When the no shutdown command is issued, keep in mind that it is not included in the configuration.

Another common problem is forgetting to specify a router ID. Unlike EIGRPv4, if there are no interfaces with an IPv4 address, it is mandatory that you specify the router ID for EIGRPv6 using the router-id <ipv4-address> router configuration command. If EIGRPv6 is enabled on a router with no interfaces in the up state assigned an IPv4 address, the routing protocol is not enabled and the following error message is printed on the console when you issue the show ipv6 eigrp neighbors command:

R1#show ipv6 eigrp neighbors
IPv6-EIGRP neighbors for process 1
% No router ID for EIGRP 1

While basic WAN interface operation is the same for both EIGRPv4 and EIGRPv6, keep in mind that when EIGRPv6 uses link local addresses for peer relationships and as the next-hop IPv6 address for received updates. Therefore, when enabling EIGRPv6 over NBMA technologies such as ATM and Frame Relay, you must configure static mappings using the link local not the Global Unicast addresses. If you specify Global Unicast addresses, while the routing protocol neighbor relationships will be established, you will not have reachability to remote subnets. Following is a sample configuration of how to configure static Frame Relay mappings using the link local addresses on the routers:

R1(config)#interface serial 1/1
R1(config-if)#frame-relay map ipv6 FE80::205:5EFF:FE6E:5C80 111 broadcast
R1(config-if)#exit

This configuration can be validated using the show frame-relay map command as follows:

R1#show frame-relay map
Serial1/1 (up): ipv6 FE80::205:5EFF:FE6E:5C80 dlci 111(0x6F,0x18F0), static,
broadcast,
CISCO, status defined, active

A useful EIGRPv6 command is the show ipv6 eigrp traffic command which provides information on EIGRP packet statistics, such as Hello packets, for example. This command can be used to troubleshoot EIGRP operational issues. For example, if the local router is sending Hellos but is not receiving any back, it may be due to Link layer issues or even EIGRP packet filtering or blocking. Following is a sample output of this command:

R1#show ipv6 eigrp traffic
IPv6-EIGRP Traffic Statistics for AS 1
Hellos sent/received: 409/392
Updates sent/received: 18/19
Queries sent/received: 0/0
Replies sent/received: 0/0
Acks sent/received: 6/0
SIA-Queries sent/received: 0/0
SIA-Replies sent/received: 0/0
Hello Process ID: 225
PDM Process ID: 224
IPv6 Socket queue: 0/50/1/0 (current/max/highest/drops)
Eigrp input queue: 0/2000/1/0 (current/max/highest/drops)

As is the case with EIGRPv4, the debug eigrp packets command can be used to view real-time information on EIGRP packets as illustrated in the following output:

R1#debug eigrp packets
EIGRP Packets debugging is on
(UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK, STUB, SIAQUERY, SIAREPLY)
R1#
R1#
*Mar  1 04:19:27.771: EIGRP: Sending HELLO on Serial1/1
*Mar  1 04:19:27.771:   AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
*Mar  1 04:19:28.519: EIGRP: Received HELLO on Serial1/1 nbr FE80::202:FDFF:FE06:6350
*Mar  1 04:19:28.519:   AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0
*Mar  1 04:19:32.459: EIGRP: Sending HELLO on Serial1/1
*Mar  1 04:19:32.459:   AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
*Mar  1 04:19:33.231: EIGRP: Received HELLO on Serial1/1 nbr FE80::202:FDFF:FE06:6350
*Mar  1 04:19:33.231:   AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

While the debug eigrp command can be used to troubleshoot both EIGRPv4 and EIGRPv6, you should use the debug ipv6 eigrp suite of commands to view EIGRPv6-specific events. This command supports the following options:

R1#debug ipv6 eigrp ?
<1-65535>      Autonomous System
neighbor       EIGRP neighbor debugging
notifications  EIGRP event notifications
summary        EIGRP summary route processing
<cr>

Following is a sample output of the debug ipv6 eigrp commands which prints real-time information on EIGRPv6 route events:

R1#debug ipv6 eigrp 1
IP-EIGRP Route Events debugging is on
R1#clear ipv6 eigrp 1 neighbors
R1#
*Mar  1 04:20:53.111: %DUAL-5-NBRCHANGE: IPv6-EIGRP(0) 1: Neighbor FE80::202:FDFF:FE06:6350 (Serial1/1) is down: manually cleared*Mar  1 04:20:56.807: %DUAL-5-NBRCHANGE: IPv6-EIGRP(0) 1: Neighbor FE80::202:FDFF:FE06:6350 (Serial1/1) is up: new adjacency*Mar  1 04:20:56.827: IPv6-EIGRP(0:1): Processing incoming UPDATE packet
*Mar  1 04:20:56.831: IPv6-EIGRP(0:1): 2001::/64 – do advertise out Serial1/1
*Mar  1 04:20:56.831: IPv6-EIGRP(0:1): Int 2001::/64 metric 20512000 – 20000000 512000*Mar  1 04:20:56.847: IPv6-EIGRP(0:1): Processing incoming UPDATE packet
*Mar  1 04:20:56.851: IPv6-EIGRP(0:1): Int 2001::/64 M 21024000 – 20000000 1024000 SM 2169856 – 1657856 512000*Mar  1 04:20:56.851: IPv6-EIGRP(0:1): 2001::/64 routing table not updated
*Mar  1 04:20:56.851: IPv6-EIGRP(0:1): 2001::/64 – do advertise out Serial1/1
*Mar  1 04:20:56.851: IPv6-EIGRP(0:1): Int 2001::/64 metric 20512000 – 20000000 512000

*Mar  1 04:20:56.867: IPv6-EIGRP(0:1): Processing incoming UPDATE packet
*Mar  1 04:20:56.871: IPv6-EIGRP(0:1): Int 2001::/64 M 21024000 – 20000000 1024000 SM 2169856 – 1657856 512000

 

Prev

Next

About Us

This is a free bonus site for members of www.howtonetwork.com

Copyright

The content on this copyright Reality Press Ltd.
Copyright Reality Press Ltd.