I think I was having the same problem. If it is then most likely the reason for this is because on the other end of the connection (not your network) the IP pool that the Defense Center (DC) was using to connect to the dynamic cloud was modified and your DC was using one of the IPs that was removed during the modification. In order to fix this, you have to restart the process on the DC that is responsible for this connection and then it'll automatically pick a new IP. Keep in mind that I restarted my DC as part of my troubleshooting and it did not fix this issue, I had to specifically restart the process. This is how I did it:
1. SSH into the DC with a terminal application (e.g. putty, SecureCRT, etc.)
2. login with super user credentials
3. pidof stunnel
! notice the process umber
4. pmtool restartbyid stunnel
5. pidof stunnel
! notice the process number is different than the one on step 3. This confirms that the process restarted
This is what took care of my issue although I had to wait 5-10 min. after the restart to stop seeing the alerts (no downtime experienced). Hope this helps.
