When using VMware NSX for vSphere 6.2.3+, the default VXLAN port of 4789 used by cf-networking will not work.
To fix this issue, override the default cf_networking.vtep_port with another value.
When the policy server is backed by MySQL versions < 5.7, a user may see this error when trying to create a policy:
FAILED
adding policies: failed to make request to policy server
An operator inspecting the logs of the policy-server BOSH job may see this error:
creating destination: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE\n\t\tNOT EXISTS (\n\t\t\tSELECT *\n\t\t\tFROM destinations\n\t\t\tWHERE group_id = ? AND '
This issue can be resolved by upgrading your MySQL server to version 5.7+
Apps which were last pushed or restaged on older versions of CloudController may need to be restaged on a newer version of CloudController in order to connect to other apps via the container network.
Apps which have been pushed or restaged on capi-release v1.0.0 or higher, or cf-release v240 or higher should be ok.
One symptom of this issue is frequent log messages from the vxlan-policy-agent job on
the Diego Cell VMs which include the message
Container metadata is missing key policy_group_id. Check version of CloudController.
To resolve this, simply cf restage MYAPP.
Logging for UDP and ICMP ASGs is currently not supported, but this feature is on our roadmap.
Prior implementations of ASGs allowed opening security groups to other containers via the NATed port on the diego cell. With CF Networking, this is no longer supported. Direct addressing of other containers is only possible through the overlay network.
Following the instructions here, when the green app is deployed it will have a different app guid than blue, meaning any container to container policies that blue has configured will need to be configured for green as well.