From: Lloyd Ardoin (Lloyd@TheWizKid.biz)
Date: Thu Sep 18 2008 - 14:57:34 ART
First if this is a production router you may want to check the CPU before you
get started to see how busy it is. Also you may want to send the output to the
buffer not the console or the VTY line of you are remoting in.
config t
no logging console
no logging monitor
logging buffered debug
or if you don't want to turn off console or monitor logging altogether you
might set both to informational
loggging console informational
logging monitor informational
end
Make sure your access-list number doesn't over write an existing ACL number.
access-list 1 permit host 163.1.10.6
debug ip packet detail 1
show logging buffered (to view the output)
undebug all (to turn off) or just un all
HTH,
Lloyd V Ardoin
From: yungli2008@gmail.com
Sent: Thu 9/18/2008 12:33 PM
To: ccielab@groupstudy.com
Subject: debug ip packet
Hi experts
I want to debug a IP packet sourced from 163.1.10.6.
How to do this?
Can anyone guide me?
Advance thanks
Li
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sat Oct 04 2008 - 09:26:18 ART