Ran into a bit of an issue today with upgrading to AirWave 8.2.3.
Seems the docker service was added in with the default network bridge.
The default bridge is 172.17.0.0/16 and is connected so all traffic going to 172.17.0.0-172.17.255.255 will go to the docker0 interface rather than eth0.
Waiting to hear back from TAC, but using the Docker documentation this seems to work.
Login as root on the console/ssh:
Stop the service
Bring the interface down
Delete the interface
Modify the configuration to use the new IP address
Start the service
ifconfig to confirm docker0 has been changed.
Would you mind sharing the TAC case / ticket number?
Here is what our engineering team came back with:
To delete the interface, we can execute the below commands:
[root@localhost mercury]# sudo ip link delete docker0 type bridge
[root@localhost mercury]# service network restart
To change the IP Address of the docker interface, we can execute the below commands:
[root@localhost mercury]# ip addr add 127.0.0.2/16 dev docker0
Let us know if this works or if you need more assistance.
Just a heads up if this hit you it looks like HPE did the same thing for ClearPass with 6.6.7
HPE didn't changing this to something more approperate like a 169 address and then allow us to configure the docker bridge, or use a smaller netmask to reduce the blast radius.
I'm sure we will need all 65,534 address to run ClearPass Exchange, or AirWave Glass. At least it was in the release notes for ClearPass.
Looks like an upgrade to 18.104.22.168 restores the configuration.
From the CLI to disable the service from start up.
SSH in as root, and run the following commands:
chkconfig docker offchkconfig docker --del
chkconfig docker --add
chkconfig docker off 2,3,4,5
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.