cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2346
Views
5
Helpful
7
Replies

APIC docker0 interface IP address

Trinh Nguyen
Beginner
Beginner

Hello community,

All my APICs are having a docker0 interface with the same IP address 172.17.0.1/16.  This subnet is in the production network VLAN 100 and causes the problem with VLAN 100 to access APIC because route was wrong.

Question: How do I change APICs docker0 ip address? I prefer to change them to a loop-back address like 127.0.0.2

Thanks,

7 Replies 7

gmonroy
Cisco Employee
Cisco Employee

Trinh,

I will take a look in our lab, but at the moment I am unaware of a method to change the docker0 address.

With that said, what type of service is the APIC trying to reach and what is its path through ACI fabric?

Are you using in-band management and you are expecting the APIC to reply using the VICs/in-band EPG to reach some external Endpoint sourced traffic within the 172.17.0.1/16 subnet?

-Gabriel

Gabriel,

I am using OOBMGMT interface.  This service is for management only, nothing wrong in ACI.  I have a TACACS server in 172.17.0.0 that cannot be reach by all APICs

Note that all three APICs are having the same docker0 ip address 172.17.0.1

external@APIC1:~> ifconfig docker0
docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0

RX packets 128 bytes 8576 (8.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2345321 bytes 98503674 (93.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Thanks for looking at this.

Regards,

_Trinh

Trinh,

I just got confirmation from our development team that it is not configurable at this point. I will file an enhancement to allow that to happen in the future.

As for immediate solutions, I am assuming it is not possible to change the address of the TACACS service that is on the 172.17.0.0/16 subnet outside of ACI?

Also, could you please send me the output of the following (if acceptable), otherwise please open an SR to send over this info:

>route -rm

>arp -an

>the address of your TACACS server

Thanks,

Gabriel