PDF(40.4 KB) View with Adobe Reader on a variety of devices
ePub(84.3 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(70.7 KB) View on Kindle device or Kindle app on multiple devices
Updated:September 17, 2019
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the process in order to switch on the changing the default network bridge in the installer so that it does not conflict with a private network and the install can be completed.
The default suite docker bridge uses the IP range of 172.18.0.0/16 and this can interfere with a private network. When the installer loads, things might become unroutable from installer to private network. You can see this bridge via:
ip address show
When logged into the installer VM. You can also see this bridge in docker via:
docker network ls
It should look similar to this:
[root@rcdn-ccs-repo ~]# docker network ls
NETWORK ID NAME DRIVER SCOPE
eadee20d76ce bridge bridge local
3a009a3d7747 host host local
f4ca595dfac5 none null local
5b0dbc510082 suite bridge local
1. When you deploy installer VM (ova or qcow2), you must be able to login to it, so if you use VMware, you must change the default-instance-id and the hostname when you deploy the OVA and add a public key or password.
2. If you use Openstack, just pass in a key.
Step 1. Log in to the installer.
Step 2. Disconnect the suite installer containers from the current bridge via:
docker network disconnect suite suite-prod-mgmt
docker network disconnect suite suite-nginx
docker network disconnect suite suite-installer-ui
docker network disconnect suite suite-k8s-mgmt
Step 3. If there are any other containers connected to the suite bridge, you must disconnect them too, in a similar fashion.
Step 4. After you disconnect all containers from the bridge, you must remove the bridge via:
docker network rm suite
Step 5. You now must create a new docker bridge with the same name but a different /16 network as to not conflict with the private network. In this command example, 192.168.0.0/16 is used:
docker network create --driver=bridge --subnet=192.168.0.0/16 --gateway=192.168.0.1 suite
Note: It must be a /16 network and must be named suite.
Step 6. Reboot the installer VM via:
shutdown -r now
Step 7. Log back into the VM.
Step 8. Verify that the suite installer's containers are up and running via:
It should look like this:
[root@rcdn-ccs-repo ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8d437dab65b9 devhub-docker.cisco.com/multicloudsuite-release/suite-nginx:5.0.0-RC2.8 "/entrypoint.sh" 13 days ago Up 13 days 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp suite-nginx
6bbffff3c248 devhub-docker.cisco.com/multicloudsuite-release/suite-prod-mgmt:5.0.0-RC2.8 "/entrypoint.sh" 13 days ago Up 13 days 8080/tcp suite-prod-mgmt
515754611a28 devhub-docker.cisco.com/multicloudsuite-release/suite-k8s-mgmt:5.0.0-RC2.8 "/entrypoint.sh" 13 days ago Up 13 days 8080/tcp suite-k8s-mgmt
8cd9d0c6ddb4 devhub-docker.cisco.com/multicloudsuite-release/suite-installer-ui:5.0.0-RC2.8 "npm start" 13 days ago Up 13 days 8080/tcp suite-installer-ui
Step 9. You can then verify that the *NEW* suite bridge works fine with:
docker network inspect suite
It should look similar to this with your *NEW* ip range as the IPv4 addresses: