We have 2x CUCM 14.x on 2x BE7K-M5 servers. IPs in the range of (172.17.0.0/16) have problem connecting with CUCM, IMP and CUC. However, If the same IP is assigned to a Windows machine it works fine, but with CUCM , IMP & CUC it doesn't.
While checking "show network route" on cucm, it shows there is a docker0 interface inside cucm that uses this IP range 172.17.0.0 apart from eth0 interface.
ARP is unable to resolve as it is using the docker0 interface instead of Eth0; therefore, traffic destined for 172.17.0.0 goes out of docker0 interface.
attached is the screenshot for:
"show network route"
Is there any work around available ? Since changing CUCM IP address to a different subnet range won't help as endusers voice VLAN and docker container are in same subnet.
Thanks
