Symptom

Using a SLA monitor object in Static route in 6.5 or 6.6 and upgrading to 6.6.1 results in SLAmonitor object being in "pending" state on the device. And this results in Static route to be deemed down

Conditions

Consider a FDM on 6.5 having Static routes with SLA monitor object User upgrades the box 6.6 or 6.6.1 Any config export-import with SLA monitor objects will run into this issue. SLA monitor object will be in pending state after upgrade or import

Workaround

Following is the workaround customer can employ if he knows he has Static routes with SLA monitor objects After FTD is upgraded. Go to FDM → Static Routes page Edit the static route having SLA monitor and remove associated SLA monitor Object and Save Open the same static route again and add back the SLA monitor object and Save. Deploy If the User is unaware of this issue and if he does not do #2 #3, he will run in to the issue, And if the static route used to reach FDM goes down user would lose access to FDM or SSH depending on his routing policies He will have to use a jump-box in the same network as FTD to access the box and repeat above workaround to gain back the access

Further Problem Description