The user at 192.168.150.10 can reach the physical router but CANNOT reach edge-2 or any virtual machines.
What routing change would resolve the issue?
A.
Enable Default Originate on edge-2 for OSPF.
B.
Configure static routes on the physical router.
C.
Enable route redistribution on edge-2 between both routing protocols.
D.
Enable Default Originate on edge-2 for BGP
Either C or D – I can’t figure out which one
https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.3/com.vmware.nsx.admin.doc/GUID-2CA396D2-9712-4FC6-B0AF-5F1A0BE1CB33.html
Click Enable Default Originate to allow NSX Edge to advertise itself as a default gateway to its peers.
https://pubs.vmware.com/NSX-6/index.jsp#com.vmware.nsx.admin.doc/GUID-6DE97E5F-A147-4294-B162-08CB90B2699A.html
By default, routers share routes with other routers running the same protocol. In a multi-protocol environment, you must configure route redistribution for cross-protocol route sharing.
The graphic shows OSPF & BGP. My best guess is “C”
Clue is “you can’t reach edge-2”. This means ping can reach the physical router, which has a directly connected route so it forwards the packet to edge-2, edge-2 knows a lot of things for BGP and OSPF, but if it cannot reply is because it doesn’t have the route to 192.168.150.x network. This means BGP is only enabled for that link, not the rest of the links on the physical router.
If you enable route redistribution, OSPF routes will be injected at the physical router, which is good, but that won’t change the fact that edge-2 doesn’t know how to reach the 192.168.150.x network. Creating a static route on the physical router won’t fix the issue because edge-2 is the one that doesn’t know how to get there, hence default originate on edge-2 seems to be the right answer.