This page explains the manual work part when use the FLAT type network for M-CORD 3.0.
1. Find the mac address of the VM interface with IP address in 184.108.40.206/24 subnet.
such as: fa:16:3e:be:1b:62
2. Use "ifconfig" to find the tap interface name on compute node though part of the mac address “16:3e:be:1b:62”
" tap4dc7d35c-46 " is the interface name we need.
3. [optional] Confirm the tap interface is inside br-int (ovs bridge)
4. Remove the "tap4dc7d35c-46" port from the br-int
5. Create linux bridge with "brctl" tool
6. Find the available 10G interface, and connect it to the Fabric switch. In my case, it is eth3.
7. Add the eth3 and the VM port to the flatbr.
ubuntu@aggravating-glove:~$ sudo brctl addif flatbr eth3
device eth3 is already a member of a bridge; can't enslave it to bridge flatbr.
If you meet the error above, then, you should comment out "bond-master fabric" inside /etc/network/interfaces, and restart the eth3.
8. Bring the flatbr up
9. Reconfig the fabric switch https://github.com/opencord/cord/blob/cord-3.0/docs/quickstart_physical.md#post-deployment-configuration-of-the-onos-fabric
The baremental host such as enodeb should be configed in a same network, which is 103.0.0.x/24.
10. Then reactivate the org.onosproject.segmentrouting
It should work until now. You can try ping between the vm and the baremental host.
In this way, you can create multiple VMs inside a same compute node, and let all the VMs (such as MME, SGW) to ping the baremental host (such as enodeb).