APIC-EM PoC about LXC network (grape-br0)

Working on an APIC-EM PoC . Hitting some issue for setting up standalone APIC-EM server. The APIC-EM is using 169.254.0.0/16 network as LXC network (grape-br0) by default. The grape-br0 is defined in /etc/default/lxc-net.

Got the following questions

1. Is the LXC network NATed to the eth NIC interface to customer IP Subnet address. Currently can see the 169.254.0.0/16 subnet address in production network.
2. If the address is not NATed, is it possible to change the LXC network to a different IP Subnet as they have on their production network a similar 169.0.0.0 subnet.

169.254/16 is local link address as defined in RFC. It can be used only for communication only within broadcast domain.

• 169.254.xxx.xxx is non-routable in the Public network. But used 169.254.xxx.xxx in the Private Internal Production network for the servers hosts heart-beat purpose. This clashes with APIC-EM LXC network addresses range.  Later, setup the APIC-EM in an isolated network and the issue is resolved.

 Dont think change of IP subnet is supported...

From what I understand LXC address space is already isolated on APIC-EM. If you are using this subnet for servers heartbeat network only (isolated as well) there probably should be an issue.  it might have consequenses only when network devices use IPs from 169.254/16 subnet.

you can click on the "I wish this page would..." at the bottom of the controller UI to request enhancements. That will pop open an email to send to the product management team.Someone from the product management team will get back to you on this.