cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4970
Views
5
Helpful
3
Replies

INVALID_NICNUM message on ASA5505 8.4.2 upgrade

jgonzalez79
Level 1
Level 1

Hi,

I just upgraded an ASA5505 running 8.4.1 to 8.4.2 after noticing that I was experiencing the ssh bug described here: https://supportforums.cisco.com/docs/DOC-16513. Now every time I reload the unit I get the following message on the console:

Reading from flash...

!!...

Cryptochecksum (unchanged): b19f76ce 30b189e5 9272b4d4 4f746634

Type help or '?' for a list of available commands.

ASA5505> nic_get_channel: INVALID_NICNUM (16) from 0x08db6275

nic_get_channel: INVALID_NICNUM (16) from 0x08db6275

nic_get_channel: INVALID_NICNUM (16) from 0x08db6275

nic_get_channel: INVALID_NICNUM (15) from 0x08db6275

nic_get_channel: INVALID_NICNUM (15) from 0x08db6275

nic_get_channel: INVALID_NICNUM (15) from 0x08db6275

I tried searching for this message with no luck at all. The firewall seems to be working ok as I can still get online and my VPN tunnels are up, but I really have no clue what this is and if it's serious. Any help would be greatly appreciated.

Joel Gonzalez

1 Accepted Solution

Accepted Solutions

Andrew Ossipov
Cisco Employee
Cisco Employee

Hello Joel,

You're hitting the following known cosmetic defect:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtq96332

You can either wait until the next maintenance release or open a TAC case to obtain the interim image that would contain the fix.

Andrew

View solution in original post

3 Replies 3

Andrew Ossipov
Cisco Employee
Cisco Employee

Hello Joel,

You're hitting the following known cosmetic defect:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtq96332

You can either wait until the next maintenance release or open a TAC case to obtain the interim image that would contain the fix.

Andrew

Thanks Andrew, that answered my question down to the tee.

Joel

n_parshina
Level 1
Level 1

My collegue found another workaround - delete all "snmp-server" lines in the configuration and then re-add them.  Makes the messages go away.

Review Cisco Networking for a $25 gift card