FTD 1120 - Fault - CommSvcEpUpdateSvcEp

[aaronO]

Hello,

I am doing an upgrade for a customer for different FTD platforms managed by FMC version 7.7.10 

While upgrading to the current (20/11/2025) recommended version from Cisco => 7.6.2 

We are seeing the following fault, only in the 1120 

1 Critical Events
Code - F1000272; Occurrence - 1; Time - 2025-11-19T12.02.46.266;
Description - [FSM.FAILED]. communication service configuration(FSM.sam.dme.CommSvcEpUpdateSvcEp)

Issue was not see on instances running in a 9300 chassis nor in the 1140 FW 

Doing my research the only information with the same code error is related to UCS products, so not really a match for this. 

Does anyone has more information on what the above means and how we can proceed forward? 

Thanks for the help 

Regards,

Aaron Olguin 

[Sheraz.Salim]

I see where you coming from as its a different set of appliances platform. While seraching I noted very similar bug description but not same ID. 

https://bst.cisco.com/quickview/bug/CSCtk84383

so the one you see issue 

communication service configuration(FSM.sam.dme.CommSvcEpUpdateSvcEp)

and the one i provided the link its asking could be due to invalid NTP issue. hence could you confirm if NTP is working. does it stop you doing any software upgrade/installation work. I could be incline more of cosmetic bug.

[aaronO]

Thanks for the reply .... Indeed i came across that one too and NTP is not a problem. I even change it to take NTP from FMC and that did not make a difference. 

To be fair I am not sure what the impact is, we upgraded the firewall 2 days ago, so I do not see any problems so far. 

We would like to fix it though  

BR,

Aaron 

[Sheraz.Salim]

Aaron, it’s good to hear that everything is functioning correctly. However, I understand that seeing these logs on production appliances can be uncomfortable. This appears to be a cosmetic issue, but at this point the best course of action would be to open a case with TAC for further investigation.

[aaronO]

Thanks for the advice. Yeah i was planning to do so. We upgrade FW to the latest patch ( 7.6.2.1 ) and now the alarm is gone. 

Looking at the list of resolved bugs in this patch I don't think they actually addressed this message, so I suspect the reload helped.

I hope this is useful for others.

Regards,

Aaron Olguin 

[Sheraz.Salim]

Aaron, that good to hear and thanks for giving the update on this.