1-57
Cisco IOS XR Troubleshooting Guide for the Cisco CRS-1 Router
OL-21483-02
Chapter 1 General Troubleshooting
Packets
Apr 19 10:04:11.675 ipv4_arp/arp 0/RP0/CPU0 t1 ARP-TABLE: creating incomplete entry for
address: 172.18.105.255
Apr 19 10:04:16.272 ipv4_arp/arp 0/RP0/CPU0 t1 ARP-TABLE: address resolution failed for
172.18.105.255
Apr 19 10:04:30.028 ipv4_arp/arp 0/RP0/CPU0 t1 ARP-TABLE: entry 172.18.105.255: deleted
from table
Apr 19 10:04:44.097 ipv4_arp/arp 0/RP0/CPU0 t1 ARP-TABLE: received address resolution
request for 172.18.105.255
Apr 19 10:04:44.097 ipv4_arp/arp 0/RP0/CPU0 t1 ARP-TABLE: creating incomplete entry for
address: 172.18.105.255
Apr 19 10:04:48.810 ipv4_arp/arp 0/RP0/CPU0 t1 ARP-TABLE: address resolution failed for
172.18.105.255
Packets
By default, if packet capture is not enabled on an interface, the show packet-memory command displays
only punt packets and software switch packets (router generated packets or anything that impacts the line
card CPU). You have the option of retrieving information on packets that are switched and punted in the
software using the show captured packets command. You have to turn on packet capture using the
capture software packets command, then use the show captured packets command to display the
packet capture content.
The following example shows that interface does not have packet capture enabled using the capture
software packets command:
RP/0/RP0/CPU0:router# show captured packets ingress interface pos 0/1/0/0 location
0/RP0/CPU0
please enable packet capture on interface to see pkts
RP/0/RP0/CPU0:router#
Note This feature is supported on the Cisco CRS-1.
To turn on packet capture and view capture packet output, perform the following procedure.
SUMMARY STEPS
1. configure
2. interface type instance
3. capture software packets
4. end
or
commit
5. show captured packets {ingress | egress} [interface type instance] [hexdump] [last number]
[single-line] location node-id