CSCvs82369 - Threat Data Updates - Cisco Cloud Configuration - Failure - 2

[Jose Anda]

In my case, both files show the same region. So this workaround is not helpful. We are running 6.6.4

wetmore2:~$ cd /ngfw/etc/sf/connector.properties
bash: cd: /ngfw/etc/sf/connector.properties: Not a directory
wetmore2:~$ cd /ngfw/etc/sf/
wetmore2:/ngfw/etc/sf$ cat connector.properties
registration_interval=180
connector_port=8989
region_discovery_endpoint=https://api-sse.cisco.com/providers/sse/api/v1/regions
connector_fqdn=api-sse.cisco.com
wetmore2:/ngfw/etc/sf$ cd /ngfw/etc/sf/connector.properties
bash: cd: /ngfw/etc/sf/connector.properties: Not a directory
wetmore2:/ngfw/etc/sf$ cd /ngfw/var/tmp/
wetmore2:/ngfw/var/tmp$ cat tds
tds-cloud-events.json tds_health.status
wetmore2:/ngfw/var/tmp$ cat tds-cloud-events.json
{
"events" : {
"connection" : 1,
"file" : 1,
"intrusion" : 1
},
"csd" : "1",
"region" : "api-sse.cisco.com"

[martin-christiansen]

Same scenario here, both files shows the same and correct region.

My errors started appearing after FMCv migration to FMCv300, and I solved it, by turning off Cisco Cloud Event Configuration and then turning it on again after a few minutes.

Settings -> Integration -> Cloud Services -> Cisco Cloud Event Configuration

[jai_chandra2001]

That worked like a charm!!