show running-config ip-client
> show running-config ip-client
ip-client outside
show conn address fmc_ip
> show conn address 10.89.5.35
5 in use, 16 most used
Inspect Snort:
preserve-connection: 0 enabled, 0 in effect, 0 most enabled, 0 most in effect
TCP nlp_int_tap 10.89.5.29(169.254.1.2):51231 outside 10.89.5.35:8305, idle 0:00:04,
bytes 86684, flags UxIO
TCP nlp_int_tap 10.89.5.29(169.254.1.2):8305 outside 10.89.5.35:52019, idle 0:00:02,
bytes 1630834, flags UIO
>
Check for a successful DDNS update
At the FTD CLI, check for a successful DDNS update:
debug ddns
> debug ddns
DDNS update request = /v3/update?hostname=domain.example.org&myip=209.165.200.225
Successfuly updated the DDNS sever with current IP addresses
DDNS: Another update completed, outstanding = 0
DDNS: IDB SB total = 0
If the update failed, use the debug http and debug ssl commands. For certificate validation failures,
check that the root certificates are installed on the device:
show crypto ca certificates trustpoint_name
To check the DDNS operation:
show ddns update interface fmc_access_ifc_name
> show ddns update interface outside
Dynamic DNS Update on outside:
Update Method Name Update Destination
RBD_DDNS not available
Last Update attempted on 04:11:58.083 UTC Thu Jun 11 2020
Status : Success
FQDN : domain.example.org
IP addresses : 209.165.200.225
Check FMC log files
See https://cisco.com/go/fmc-reg-error.
Roll Back the Configuration if the FMC Loses Connectivity
If you use a data interface on the FTD for FMC management, and you deploy a configuration change from
the FMC that affects the network connectivity, you can roll back the configuration on the FTD to the
Cisco Firepower 1100 Getting Started Guide
149
Firepower Threat Defense Deployment with a Remote FMC
Roll Back the Configuration if the FMC Loses Connectivity