cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
662
Views
0
Helpful
4
Replies

Questions about CSCwa14518

longlong_liu
Spotlight
Spotlight

We just upgrade to FTD v7.0.1 & FMC v7.0.1 and afterwards we seeing an issue with a Health Alert that we cannot clear. The following is showing for FTDs.

111.png

 Question1:Does  this bug(CSCwa14518) affect these interfaces in the picture?  Because the eth16 interface can communicate with data normally before the upgrade, but the eth16 interface is abnormal after the upgrade (the interface light is normal ).  After clearing this error message, can the interface return to normal?

Question2:  Here is the fix to delete the messages. The following commands need to be run as root from the FMC cli (expert mode):  Forgot root password, how to get it back.

OmniQuery.pl -db mdb -e "select status,category,hex(uuid),body from notification where status=11;"
OmniQuery.pl -db mdb -e 'delete from notification where uuid=unhex("<insert the uuid that the first command returns here>");'
OmniQuery.pl -db mdb -e "select status,category,hex(uuid),body from notification where status=11;" 

 Thanks!

1 Accepted Solution

Accepted Solutions

Marvin Rhoads
Hall of Fame
Hall of Fame

Answered in the other thread where you posted the same questions.

https://community.cisco.com/t5/network-security/fmc-health-alert-not-clearable-interface-status-modified/td-p/4528153

Please do not double post the same question.

View solution in original post

4 Replies 4

Marvin Rhoads
Hall of Fame
Hall of Fame

Answered in the other thread where you posted the same questions.

https://community.cisco.com/t5/network-security/fmc-health-alert-not-clearable-interface-status-modified/td-p/4528153

Please do not double post the same question.

thank you very much .  I will test it later.

Hi,

The problem about the health alarm has been successfully cleared. However, the eth13, eht14, eth15, and eth16 interfaces of FTD still cannot exchange data. It was normal before the upgrade (version: 6.4.0), but it was abnormal after the upgrade (7.0.1.1). Physical media/network configuration/device interfaces have been checked several times. Can you help analyze the reason? Or is there a similar bug in this version.

Thank you!

We would need more details to troubleshoot. For instance:

What hardware are you using?

Are the interfaces possibly part of a portchannel?

Review Cisco Networking for a $25 gift card