THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.
Migration to new field notice system
|Affected OS Type
||Affected Release Number
Please check the "Workaround/Solution" section for affected ASA interim release numbers.
||ARP functions fail after 213 days of uptime, drop with error 'punt-rate-limit-exceeded'|
All Cisco Industrial Security Appliance 3000 (ISA3000) devices that run the affected software versions do not pass network traffic after approximately 213 days 12 hours (~ 5,124 hours) of uptime.
In the near term, immediately reboot the deployed security appliances in order to prevent this issue.
The Cisco ISA3000 units shipped with manufacturing image ASA 9.6.2 are not impacted. These devices are impacted only if the customer has upgraded the software to any of the affected versions.
On March 29, 2017 Cisco became aware of an issue that affects all Cisco ISA3000 security appliances that run certain versions of software. The affected versions of software cause the security appliance to stop passing network traffic after approximately 213 days 12 hours (~ 5,124 hours) of uptime.
The issue detailed in this Field Notice is not a security vulnerability and there is no associated risk to the integrity of the security appliance.
The Cisco ISA3000 security appliances stop passing all network traffic.
Entering the show asp drop command over the console port will indicate that packets are being dropped due to the reason Punt rate limit exceeded (punt-rate-limit).
In order to mitigate the risk and impact of the device not passing network traffic, Cisco urges customers to proactively reboot their Cisco ISA3000 security appliances that run affected versions of the software.
For customers with failover configurations, it is recommended to reboot the standby devices first, make them active after they complete booting, and then reboot the formerly active devices.
The reboot of the security appliance must be performed prior to 213 days 12 hours of uptime. After the reboot, the security appliance avoids an encounter with this issue for another 213 days 12 hours.
Enter the show version | grep up command in order to display the uptime of the security appliance.
The output is shown here:
ciscoasa# show version | grep up
Config file at boot was "startup-config"
ciscoasa up 210 days 11 hours
The device can be rebooted with one of these methods:
- CLI - Enter the reload command in privileged mode
- ASDM GUI - Choose Tools > System Reload
A physical power-cycle can be used in order to perform a reboot.
Updated ASA software versions that address this issue are available from Cisco Software Central for customers with a valid service contract. The recommended upgrade paths are shown in the table below.
|Impacted Release Number(s)
||Fixed Release Number(s)
|ASA 9.5.3, ASA 188.8.131.52, ASA 184.108.40.206, ASA 220.127.116.11
||ASA 18.104.22.168 or later
|ASA 22.214.171.124, ASA 126.96.36.199, ASA 188.8.131.52, ASA 184.108.40.206, ASA 220.127.116.11, ASA 18.104.22.168, ASA 22.214.171.124, ASA 9.6.3
||ASA 126.96.36.199 or later
|ASA 9.7.1, ASA 188.8.131.52
||ASA 184.108.40.206 or later
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
Receive Email Notification For New Field Notices
Cisco Notification Service—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.