Satellite version 6.x uses some internal networks for docker communication. ip address range 172.17.0.0/16 and 172.16.0.0/24 . If you have a conflict and using these networks on the same vlans as Satellite version 6.x is installed, you can change these address assignments to avoid duplicates and routing loops.
To see what addresses are used by Satellite version 6.x do ,
and view interface addresses for docker0 and atantis0. If you feel there is a routing problem due to duplicates network assignments please use the steps below to resolve
Edit the last few lines of /home/deployer/atlantis/docker-compose-up.yml to the following:
- subnet: 192.168.200.0/24
- subnet: fd00:dead:beef::/48
Create the file /etc/docker/daemon.json with the following contents:
After the above procedures, restart the satellite.
Hello,Is there a limit to the number of "virtual accounts" that can be created underneath a "smart account".I am a service provider and have lots of customers. The way I wish my smart account to be structured is that underneath my org's smart account, I w...
Hello, I am looking to upgrade a multi instance FTD deployment via FMC. In case of single deployment OS can be pushed via FMC and then installed on FTDs.. however i didn't find any specific document to upgrade a multi instance ftd deployment.. will b...
I just bought a cisco 1000 series switch with web gui. I had a problem setting it up so I used the cli via com3 and it was in setup mode. Now I can't log in via the web site. I remember it ask me for a secret password. I am thinking the easiest thin...
Hi Experts, Recently upgrade a 3850WS-C3850-24T switches in Stack from 03.06.06E to 16.12.4 Version I observed that multiple QOS Statements are added by default which was not present before upgrade after each QOS configurationLike Bel...