Symptom
Packet drop because of no arp for the destination.
Conditions
The ARP entry for destination doesn't exist.
Workaround
Create a static arp entry or check why the next hop is not replying to the ARP request.
Further Problem Description
The customer's return traffic was being dropped with the reason "Punt no memory".
We took the pcap with trace and found drop reason as "Punt no memory"
GBSLO-D1-ECIFA-001/GBSLO-D1-ECIFA-0722/act/sec(config)# show cap 3 packet-number 2 trace
6 packets captured
2: 06:57:34.512790 802.1Q vlan#1386 P0 10.29.122.79.443 > 10.234.123.180.47470: S 1588843152:1588843152(0) ack 3937274213 win 65535
Phase: 1
Type: CAPTURE
Subtype:
Result: ALLOW
Config:
Additional Information:
MAC Access list
Phase: 2
Type: ACCESS-LIST
Subtype:
Result: ALLOW
Config:
Implicit Rule
Additional Information:
MAC Access list
Phase: 3
Type: FLOW-LOOKUP
Subtype:
Result: ALLOW
Config:
Additional Information:
Found flow with id 2669474460, using existing flow
Phase: 4
Type: ROUTE-LOOKUP
Subtype: Resolve Egress Interface
Result: ALLOW
Config:
Additional Information:
found next-hop 10.234.19.189 using egress ifc OUTSIDE
Result:
input-interface: INSIDE
input-status: up
input-line-status: up
output-interface: OUTSIDE
output-status: up
output-line-status: up
Action: drop
Drop-reason: (punt-no-mem) Punt no memory
Letter we found the actual issue was No ARP and this drop reason was miss leading.
