Cisco Debug - Versionsgeschichte

Thomas am 24. Mai 2016 um 12:49 Uhr

2016-05-24T12:49:25Z

David am 4. Februar 2016 um 09:45 Uhr

2016-02-04T09:45:47Z

Thomas am 3. Februar 2016 um 11:10 Uhr

2016-02-03T11:10:25Z

Thomas: Die Seite wurde neu angelegt: „=Troubleshooting= Let's make the assumption that as the network administrator you only have access to the CaptureRouter and you need to prove if the packet lo…“

2016-02-03T10:07:20Z

Die Seite wurde neu angelegt: „=Troubleshooting= Let's make the assumption that as the network administrator you only have access to the CaptureRouter and you need to prove if the packet lo…“

Neue Seite

=Troubleshooting=

Let's make the assumption that as the network administrator you only have access to the CaptureRouter and you need to prove if the packet loss is on that device. The first step is to determine if the packets are actually coming in to the CaptureRouter. Previously one could use things such as an ingress ACL and watch hit counters or configure netflow on the ingress interface. This exercise is to show how to use the Packet Capture feature to isolate the loss.

All of the commands are done at the EXEC prompt so configuration access isn't required unless you need to define an access-list (ACL) to make the capture more granular.
The following steps are needed to capture the frames:

*Define a capture buffer -> This is where the frames are stored once captured

*Define a capture point -> This gives the user the ability to be more granular on what interface, switching path the frames are captured

*Associate the capture point with the capture buffer -> You can associate multiple points to the same buffer

*Start the capture

*View the capture and/or export it to a PCAP file for offline analysis

← Nächstältere Version		Version vom 24. Mai 2016, 12:49 Uhr
Zeile 1:		Zeile 1:
		+
		+
		+	=disable cef=
		+	*no ip cef
		+	=disable router-cache=
		+	*no ip route-cache
		+	=debug ip packets=
		+	*debug ip icmp
		+	*terminal monotor
		+	=abschalten des debugging=
		+	*no debug all
		+
		+
		+	For other I used the "no ip cef" command globally and confirmed CEF was not running by using "show ip cef" and "show ip cef interface " and then by disabling, on a per interface basis, route caching using the interface command "no ip route-cache"
		+
		+	=Links=
		+
		+	*https://supportforums.cisco.com/discussion/11210836/using-debug-ip-packet-detail-follow-icmp-traffic-across-multiple-hops
		+
		+
	=Troubleshooting=		=Troubleshooting=

← Nächstältere Version		Version vom 4. Februar 2016, 09:45 Uhr
Zeile 19:		Zeile 19:
	=Links=		=Links=
	*http://www.routereflector.com/2013/05/embedded-packet-capture-tcpdump-on-cisco-ios-routers/		*http://www.routereflector.com/2013/05/embedded-packet-capture-tcpdump-on-cisco-ios-routers/
		+
		+
		+	=debug algemein=
		+	debug kann hohe cpu auslstung verusachen
		+	=debug interface=
		+	*debug aktiviren für ein interface
		+	debug interface FA1/0/9
		+	Condition 1 set
		+	*debug deaktiviren für ein interface
		+	switch-gelb#no debug interface FA1/0/9
		+	This condition is the last interface condition set.
		+	Removing all conditions may cause a flood of debugging
		+	messages to result, unless specific debugging flags
		+	are first removed.
		+
		+	Proceed with removal? [yes/no]: yes
		+	Condition 1 has been removed
		+	=debdebug interfaces interfaces=
		+	*debug kann auf mehreren interfaces gleizeitg benutzt werden
		+	switch-gelb#debug interface FA1/0/9
		+	Condition 1 set
		+	switch-gelb#debug interface FA1/0/10
		+	Condition 2 set
		+	switch-gelb#debug interface FA1/0/11
		+	Condition 3 set
		+	=show debug=
		+	*zeigt uns die interfaces im debug modus an
		+	show debug
		+
		+	switch-gelb#debug interface FA1/0/9
		+	Condition 1 set
		+	switch-gelb#debug interface FA1/0/10
		+	Condition 2 set
		+	switch-gelb#debug interface FA1/0/11
		+	Condition 3 set
		+
		+
		+
		+	=debug ip ospf hello=

← Nächstältere Version		Version vom 3. Februar 2016, 11:10 Uhr
Zeile 16:		Zeile 16:

	*View the capture and/or export it to a PCAP file for offline analysis		*View the capture and/or export it to a PCAP file for offline analysis
		+
		+	=Links=
		+	*http://www.routereflector.com/2013/05/embedded-packet-capture-tcpdump-on-cisco-ios-routers/