This document describes the INVALID_NICNUM error that might appear when you run Cisco Adaptive Security Appliance (ASA) 8.4(2) or later.
There are no specific requirements for this document.
The information in this document is based on the Cisco Adaptive Security Appliance (ASA).
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
When you run ASA 8.4(2) or later, the ASA might print to the console messages similar to these:
nic_get_channel: INVALID_NICNUM (19) from 0x08db6275
nic_get_channel: INVALID_NICNUM (39) from 0x00000000011fbfb3
Note: Hex values and NIC numbers might change.
This issue is cosmetic and is triggered when the snmp-server command is configured on the ASA.
These Cisco Bug IDs are used to track this issue on the appropriate platform:
CSCtq96332 (registered customers only) —ASA 5505 logs "INVALID_NICNUM" messages to console (This issue is fixed in versions 8.4(2)2 and higher.)
CSCtr83349 (registered customers only) —ASA logs "INVALID_NICNUM" messages to console (This issue is fixed in versions 8.4(2)6 and higher.)