OVS Based NA Responder for IPv6 default Gateway <ovs_based_na_responder_for_gw>
Retain Earlier Elected Napt Switch After Upgrade for SNAT<retain-napt-switch-after-upgrade-for-snat>
Subnet routing for hidden IPv6 addresses <subnet-routing-for-hidden-ipv6>
- Support Neutron BGPVPN API on OpenDaylight L3VPN Service
+ Support Neutron BGPVPN API on OpenDaylight L3VPN Service <neutron-bgpvpn-api-support>
Tap as a Service <Tap-as-a-Service>
EVPN and l2gw integration <evpn-l2gw-integration>
- Enable discovery of Virtual IPs (or Movable IPs) holding Virtual MACs
+ Enable discovery of Virtual IPs (or Movable IPs) holding Virtual MACs <vpn_vmac_movement>
Evpn Route Type 3 support <evpn-rt3-support>
Enable discovery of Virtual IPs (or Movable IPs) holding Virtual MACs
-==========================================
+=====================================================================
https://git.opendaylight.org/gerrit/#/q/topic:vpn_vmac_movement
connectivity established for such Virtual IPs.
8. All the above steps will be certified for discovered IPv6 addresses with Virtual
- MAC too as the following spec addresses IPv6 address discovery:
+ MAC too as the following spec addresses IPv6 address discovery:
https://git.opendaylight.org/gerrit/70912
Proposed change
References
==========
-
If the DHCP provisioning does not succeed, e.g., if the dhcp agent is down, the port will not
transition to active. In order to determine if DHCP provisioning worked look for *either* of
the following two lines in the neutron logs:
+
``Provisioning for port <uuid of port> completed by entity DHCP.``
``Provisioning complete for port <uuid of port> triggered by entity DHCP.``