Providing information on how VCF 4.3 supports OSPF.
This is a new feature in NSX-T 3.1.1.
Request for information on OSPF Support in VCF 4.3.
NSX has recently added Edge cluster support for OSPF, but this is not explicitly supported by VCF automation.
BGP remains the recommended means of distributing routes. For those customers who cannot use BGP, this KB describes how to manually configure a VCF-deployed Edge cluster to distribute routes using OSPF.
The overall process consists of three phases:
The preceding steps may also be used when expanding an Edge cluster which is already enabled for OSPF. As in creation, VCF expansion will accept only static-routed (non-BGP) Tier-0 uplink interface descriptions. Then in NSX, OSPF peering will only need to be enabled for any new Tier-0 interfaces added as part of the expansion.
Use of the Edge cluster shrinkage VCF workflow is unchanged with OSPF-enabled Edge clusters.
Use of the Edge cluster cleanup utility (KB-78635) is likewise unchanged: it will also clean up any OSPF NSX configuration associated with the Edge cluster's Tier-0 gateway.
First, deploy an Edge cluster via VCF's Edge cluster creation automation. The Edge cluster must be specified to VCF as using static routing. High-availability may be set to ACTIVE_ACTIVE or ACTIVE_STANDBY as preferred.
So the Edge creation spec (or equivalent fields if using the UI) will include either
"tier0RoutingType":"STATIC", "tier0ServicesHighAvailability":"ACTIVE_ACTIVE"
or
"tier0RoutingType":"STATIC", "tier0ServicesHighAvailability":"ACTIVE_STANDBY"
Please ensure that the top-of-rack switches supporting the deployed Edge cluster are configured to enable OSPF peering for all hosts in the VC cluster(s) where the Edge node VMs are located.
Once your Edge cluster is available and the TORs have been prepared, it is time to manually enable OSPF for the Edge cluster. This may be done using the NSX UI. Please follow the instructions provided in the NSX Data Center Administration Guide
in the section Tier-0 Gateways > Configure OSPF