Hello,
I have a requirement to learn the IP address of VM's, given its MAC 
address/Vlan tag when OVS is the virtual switch deployed. This is a very 
generic requirement since the VM's IP address can either be launched through 
Orchestrator like Openstack/vCenter or external DHCP agents or even assigned 
manually. Even the VM's IP address can be changed manually.

I wrote a utility using libpcap that does the job. But, I wanted to see if I 
could make use of existing OVS utilities. Ideally, am looking for new IP learn 
notification scheme. Some logical approaches that i can think of are below, 
please comment on the feasibility or the caveats with the approaches below.

1)
When any new flow gets added to kernel DP, is there any notification mechanism? 
And does that notification has the L3 header as well? I understand the first 
frame may not have the IP address, but wanted to see if I can improve on this 
option, if available. Latest 'ovs-dpctl' didn't have the monitor option.

2)
What about the reverse notification option of (1), that is, when a new flow is 
punted to user space, that also could be made use of.

3)
Is OVSDB monitor an option? From what I understand, events are generated only 
for  bridges/ports/interfaces/ etc. For extended header fields like IP, it 
isn't available. Please correct me, if I am wrong.
 
4)
The FDB has the MAC table. Is there any options to extend it to also maintain 
the associated IP address :)? I don't know the implementation details, but for 
any IP based tunnels (LISP), is not the IP address learnt and stored?

Appreciate any response, pointers/suggestions.
Thanks,Paddu

_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to