cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3302
Views
55
Helpful
8
Replies

CSCvi91153 - "[FSM.FAILED]. external aaa server configuration" health alert

meconomou
Level 1
Level 1

I'm having the exact same Platform Fault on the FTD 2110 firewalls as well. Cisco suggested to re-image back to code 6.2.2 since it is stable and 6.2.3 has numerous bugs.

platform fault.png

 

 

 

 

 

2 Accepted Solutions

Accepted Solutions

It appears to be fixed in 6.2.3.6.

I've upgraded one of the 2110 from 6.2.3.3 and this error message has disappeared.

I'll be upgrading again on Thursday, hopefully this annoying 'critical' error has now been resolved.

 

Note: I did not apply your workaround.

Perhaps revert the workaround prior to upgrading to 6.2.3.6?

 

Update 14/11/2018:- It's a confirm on upgrading to 6.2.3.6 will fix this 'critical' message.

Have upgraded the other 2110 and it's looking solved.

 

 

View solution in original post

8 Replies 8

I have the same error on several 2110 - even on 6.2.3.2-42

Ran into it on 2120.

Workaround suggested by Cisco TAC worked for me:

 

-----------------------------------------------------------------

The root cause of the issue is that one of the processes in code tries to open the /home/ldap or /home/radius directory even if external authentication is not enabled.

 

Can you please apply the following workaround to linux in the FTD device:

 

> expert

:~$ cd /home

:/home$ sudo su

:/home# mkdir ldap radius

:/home# chown admin ldap radius

:/home# chgrp users ldap radius

---------------------------------------------------------------------

Hi Sergei, thanks! It works perfectly!

Did you have to reboot after adding this configuration?

yes have to reboot to take affect

This workaround worked for me on the base version 6.2.3 after a reboot.

It appears to be fixed in 6.2.3.6.

I've upgraded one of the 2110 from 6.2.3.3 and this error message has disappeared.

I'll be upgrading again on Thursday, hopefully this annoying 'critical' error has now been resolved.

 

Note: I did not apply your workaround.

Perhaps revert the workaround prior to upgrading to 6.2.3.6?

 

Update 14/11/2018:- It's a confirm on upgrading to 6.2.3.6 will fix this 'critical' message.

Have upgraded the other 2110 and it's looking solved.

 

 

I'm currently on 6.2.3.3-76 and still seeing the same error.

Previously saw it on 6.2.3.1-43 and was hoping it would be fixed in 6.2.3.3-76...

I'll have to try the posted workaround.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: