Guest

Cisco ASA 5500-X Series Next-Generation Firewalls

ASA INVALID_NICNUM Error Troubleshooting TechNote

Document ID: 113391

Updated: Jan 13, 2012

Contributed by Michael Robertson, Cisco TAC Engineer.

   Print

Introduction

This document describes the INVALID_NICNUM error that might appear when you run Cisco Adaptive Security Appliance (ASA) 8.4(2) or later.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

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.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Error: nic_get_channel: INVALID_NICNUM

Problem

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

or

nic_get_channel: INVALID_NICNUM (39) from 0x00000000011fbfb3

Note: Hex values and NIC numbers might change.

Solution

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:

  • 5505 only

    CSCtq96332 (registered customers only) —ASA 5505 logs "INVALID_NICNUM" messages to console (This issue is fixed in versions 8.4(2)2 and higher.)

  • Non-5505

    CSCtr83349 (registered customers only) —ASA logs "INVALID_NICNUM" messages to console (This issue is fixed in versions 8.4(2)6 and higher.)

Related Information

Updated: Jan 13, 2012
Document ID: 113391