09-11-2006 09:40 PM - edited 03-03-2019 04:58 AM
Hi,
when show logging, there are few lines display destroy peer message. what's the meaning and how to solve it?
========================================
router#sh logging
.Sep 12 12:13:31: destroy peer: 10.22.2.1
.Sep 12 12:13:31: destroy peer: 10.22.2.3
.Sep 12 12:13:31: destroy peer: 10.22.2.5
router#
========================================
Thanks!
Samuel
Solved! Go to Solution.
09-13-2006 01:32 PM
Sam,
The only reference is the BUG ID CSCdz86192 and the below URL to look up the bug.
http://www.cisco.com/kobayashi/support/tac/tools.shtml
I hope it helps.
Regards,
Arul
09-11-2006 10:14 PM
Samuel,
With the information provided I assume you are running EIGRP. The logging shows you that the connection to peer (neighboring router) has been destroyed, due to expiring of dead-timer.
The router has not heard from peer within the expected time frame and declares his neighbor dead.
If this event is intermittent you should use debug ip eigrp neighbor and/or debug ip eigrp packet. Look for reachability issues.
HTH
--Leon
* Please rate ALL posts.
09-11-2006 10:56 PM
Hi Leon,
How to check the dead-timer setting?
Samuel
09-12-2006 02:51 AM
yes, it is EIGRP.
Is there any other guy can help?
Samuel
09-12-2006 03:06 AM
Is dead-timer a term of ospf?
Is hold time has same meaning of dead-timer?
09-12-2006 07:00 AM
Your understanding is correct. Dead time is used in the context of OSPF and hold time is the term used with EIGRP.
show ip eigrp nei will show the corresponding hold time for that particular neighbor. The hold time is set by the neighbor.
See the example below.
This router uses the default hello/hold time of 5/15 seconds. In the first output, the hold time of 11 seconds indicate it has to receive another hello within 11 seconds and if it doesn't then it will clear the neighbor from the EIGRP neighbor table. In the second output (which was taken a second later) a hello packet was received and R3 reset the hold time to 14 seconds.
R3#show ip eigrp nei
IP-EIGRP neighbors for process 1
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 192.168.0.1 Fa0/0 11 00:13:58 573 3438 0 1
R3#show ip eigrp nei
IP-EIGRP neighbors for process 1
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 192.168.0.1 Fa0/0 14 00:13:59 573 3438 0 1
Hope this helps!
Sundar
09-12-2006 05:30 PM
Hi Sundar,
Thanks! I got it.
anyway, do you have any idea about the error message "destory peer"?
Samuel
09-12-2006 10:36 AM
Sam,
Please refer the below BUG ID for information on the logging messages.
CSCdz86192
You can look up the bug using the Bug Toolkit from the below URL:
http://www.cisco.com/kobayashi/support/tac/tools.shtml
BTW, what version of IOS are you running on the router.
I hope it helps.
Regards,
Arul
09-12-2006 05:27 PM
Hi Arul,
My cco account is not allow to browse your link.
IOS 12.2(15)T9
Samuel
09-12-2006 07:11 PM
Sam,
First and foremost, the message that you are seeing is cosmetic and should not affect any traffic or EIGRP behavior. It was basically a debug message that is showing up in log without you enabling eigrp debug.
The fix for this bug is in 12.3(1) and higher. So if you want to run a code with the fix, you can upgrade the router to 12.3(20) and this should fix the log message that you are seeing. Before you upgrade, make sure that you have enough Flash and RAM on the chassis.
I hope it helps.
Regards,
Arul
09-13-2006 05:26 AM
Hi Arul,
that's great!! :)=
Where can I find the cisco reference link?
Regards,
Samuel
09-13-2006 01:32 PM
Sam,
The only reference is the BUG ID CSCdz86192 and the below URL to look up the bug.
http://www.cisco.com/kobayashi/support/tac/tools.shtml
I hope it helps.
Regards,
Arul
09-13-2006 06:00 PM
Hi Arul,
Since I has not TAC service account, therefore I can't read it. anyway, thanks a lot!!
Samuel
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide