Symptom
When you add more number of SLA objects givng an ID number which is between the existing SLA Objects IDS, FMC can push the commands in an incorrect order and cause deployemt failure. Here are the steps to recreate the issue
1. Create SLA monitor object with ID 1, 10, 20, 30, 40 and 50. Use that in the static route and push the policy. Deoployment shoudl be successfull.
2. Cretae SLA monitor object with ID 2, ID 3 and ID 4, then use that in a static route and try to do the deployment it will never go through as FMC will be pushing the commands in an incorrect order.
Here is one transcript
###Flex-config Prepended CLI ###
###CLI generated from managed features ###
!configure session LINA_UNSUPPORTED
dp-tcp-proxy
!commit noconfirm revert-save
vpn-addr-assign local
sla monitor schedule 35 life forever start-time now ---> This command is in the wrong place.
sla monitor schedule 30 life forever start-time now
no sla monitor schedule 35 life forever start-time now
no sla monitor schedule 30 life forever start-time now
sla monitor 3
type echo protocol ipIcmpEcho 1.1.1.3 interface inside
exit
sla monitor schedule 3 life forever start-time now
###Flex-config Appended CLI ###
Conditions
FTD on HA pair with SLA monitor configuration.
Workaround
Change SLA ID to a higher value than the highest existent ID.
