Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Strange IP address for EIGRP message

I am getting strange ip address sequence in my 3640 router log messages. Does anyone know what this ip address 13.13.13.13 has beeing used for?

Iam getting strange message in my 3640 router with strange ip address 13.13.13.13

Do you know any information about usi

Sep 12 15:33:41 EDT: %DUAL-3-SIA: Route 13.13.13.13 0xD0D0D0D stuck-in-active state in IP-EIGRP 9. Cleaning up

Sep 12 15:39:41 EDT: %DUAL-3-SIA: Route 10.61.35.0/24 stuck-in-active state in IP-EIGRP 9. Cleaning up

.Sep 12 17:26:41 EDT: %DUAL-3-SIA: Route 172.27.58.16/30 stuck-in-active state in IP-EIGRP 9. Cleaning up

.Sep 12 17:36:41 EDT: %DUAL-3-SIA: Route 13.13.13.13 0xD0D0D0D stuck-in-active state in IP-EIGRP 9. Cleaning up

.Sep 12 18:07:41 EDT: %DUAL-3-SIA: Route 172.27.58.16/30 stuck-in-active state in IP-EIGRP 9. Cleaning up

.Sep 12 18:07:42 EDT: %DUAL-3-SIA: Route 10.35.132.0/24 stuck-in-active state in IP-EIGRP 9. Cleaning up

.Sep 12 18:13:40 EDT: %DUAL-3-SIA: Route 13.13.13.13 0xD0D0D0D stuck-in-active state in IP-EIGRP 9. Cleaning up

.Sep 12 18:39:40 EDT: %DUAL-3-SIA: Route 172.27.58.16/30 stuck-in-active state in IP-EIGRP 9. Cleaning up

.Sep 12 19:17:41 EDT: %DUAL-3-SIA: Route 172.27.58.16/30 stuck-in-active state in IP-EIGRP 9. Cleaning up

.Sep 12 20:27:41 EDT: %DUAL-3-SIA: Route 13.13.13.13 0xD0D0D0D stuck-in-active state in IP-EIGRP 9. Cleaning up

.Sep 12 21:37:40 EDT: %DUAL-3-SIA: Route 13.13.13.13 0xD0D0D0D stuck-in-active state in IP-EIGRP 9. Cleaning up

.Sep 13 02:01:10 EDT: %DUAL-3-SIA: Route 172.27.57.60/30 stuck-in-active state in IP-EIGRP 9. Cleaning up

.Sep 15 08:02:37 EDT: %SYS-5-CONFIG_I: Configured from console by ambgdby on vty0 (10.32.32.1)

4 REPLIES
Cisco Employee

Re: Strange IP address for EIGRP message

Does Stuck-in-active process proceed normally other than the strange address in the message? If so, then you may be hitting CSCdu78538. If there is any other noteworthy behavior please share that as well as the code version.

New Member

Re: Strange IP address for EIGRP message

These messages (with 13.13.13.13 addresses) are sporadic, and are appearing in other routers too. We are running EIGRP but we do not have network 13.0.0.0 (which belongs to Xerox). Other problems in the networ are routers running out of memory due to the worm situation - which we are fighting back identifying and patching the machines.

Below you have more router details. I will search for the bug you mentioned.

Thanks,

USADANR3640C#sh ip prot

Routing Protocol is "eigrp 9"

Outgoing update filter list for all interfaces is

Incoming update filter list for all interfaces is

Default networks flagged in outgoing updates

Default networks accepted from incoming updates

EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0

EIGRP maximum hopcount 100

EIGRP maximum metric variance 1

Default redistribution metric is 64 100 255 1 1500

Redistributing: static, eigrp 9

Automatic network summarization is not in effect

Routing for Networks:

10.0.0.0

172.20.0.0

172.27.0.0

Routing Information Sources:

Gateway Distance Last Update

10.32.33.11 90 00:00:29

(this router) 90 1w1d

10.32.32.11 90 00:00:29

10.32.33.3 90 00:00:29

10.32.32.3 90 00:00:29

10.32.33.1 90 00:00:29

10.32.32.1 90 00:00:29

10.32.32.6 90 00:00:29

10.32.32.7 90 00:00:29

10.32.33.6 90 00:00:29

172.27.56.2 90 00:00:29

172.27.56.66 90 18w4d

Distance: internal 90 external 170

USADANR3640C#

USADANR3640C#sh ver

Cisco Internetwork Operating System Software

IOS (tm) 3600 Software (C3640-D-M), Version 12.2(1), RELEASE SOFTWARE (fc2)

Copyright (c) 1986-2001 by cisco Systems, Inc.

Compiled Fri 27-Apr-01 02:47 by cmong

Image text-base: 0x60008950, data-base: 0x60B62000

ROM: System Bootstrap, Version 11.1(20)AA2, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

USADANR3640C uptime is 24 weeks, 6 days, 14 hours, 24 minutes

System returned to ROM by power-on

System restarted at 21:29:01 EDT Tue Apr 8 2003

System image file is "flash:c3640-d-mz.122-1.bin"

cisco 3640 (R4700) processor (revision 0x00) with 93184K/5120K bytes of memory.

Processor board ID 28025818

R4700 CPU at 100Mhz, Implementation 33, Rev 1.0

Bridging software.

X.25 software, Version 3.0.0.

2 FastEthernet/IEEE 802.3 interface(s)

4 Serial network interface(s)

DRAM configuration is 64 bits wide with parity disabled.

125K bytes of non-volatile configuration memory.

32768K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102

USADANR3640C#

Silver

Re: Strange IP address for EIGRP message

What you can do to troubleshoot this is 'sh ip eigrp topology active' This will show the routes SIA , look for the 13.13.13.13 entries . The reason it is SIA is the it is waiting for a response from one of its neighbors or one of your neighbors neighbors all the way to the network boundary .

in the output of 'sh ip eigrp top active' look for entries that have an 'r' next to them , this is who the router is waiting on a response from , From there go to that router and use the same process to trace down the problem . Another good command is 'sh ip eigrp events .

Gold

Re: Strange IP address for EIGRP message

CSCdu78538:

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdu78538

It's a memory corruption issue--anytime you see 0xD0D0D0D0 like this in the output, you should immediately suspect a memory corruption, a process stepping on memory structure, or a process trying to access a free'd memory block (0xD0D0D0D0 is the "magic number" for poisoned free memory).

David is taking you down the right path for troubleshooting the stuck in actives--I'd figure out where the route normally originates, and then figure out why it's flapping so much if you're constantly seeing SIA's for it. But, that only solves half the problem, the reason it's active so much. The stuck part is harder--you'll need to do a show ip eigrp top active on a periodic basis, and telnet to the router this router is waiting on. Repeat this process, stepping through the network, until you find the router that isn't waiting on any other neighbor.

You might find a query loop, since there were a couple in code, primarily involving a metric change before the route failure, and typically involved in a "figure 8" topology, or something similar.

:-)

Russ.W

162
Views
0
Helpful
4
Replies
CreatePlease login to create content