Hi Vishal, Daya, Thanks a lot for helping me to understand it more clearly. BR Ran

Hello good ovsdb people, would any of you be motivated to help clean up some (18x) apparently overlapping classes which somehow end up being duplicated inside both schema.hardwarevtep &

hi ran, one addition on top of what vishal said. in case 2, the HWVTEPs cannot function independently, they still need to present a logical switch view to ODL, and have a backend mechanism to sync

Hi Ran, Yes, you're correct. 2 was added for use cases/devices that don't support 1. For devices that support 1, nothing is needed on ODL side as it will see the stack as a single HWVTEP device. Note

Hi, I have some questions about the target of ODL HWVTEP HA function. For HWVTEP HA, I think the HA configuration can also be realized by stacking HWVTEPs, instead of using "ODL HWVTEP HA"

Hi ZHUANGYANG, Welcome to ODL community. Could you clarify the question? Would help if you could share the document where you came across these terms. ‘use as hardware vTep’ means

Hi I would love to try use a Pica8 switch as a hardware vTep via OVSDB Hardware vTep Plugin. And the Pica8 switch supports OVSDB protocol. But what is the difference between 'use as a hardware SDN

Hi I would love to try use a Pica8 switch as a hardware vTep via OVSDB Hardware vTep Plugin. And the Pica8 switch supports OVSDB protocol. But what is the difference between 'use as hardware SDN

Sure Jamo :) Will do that!! Thanks, Vamsi

Hi Mohamed, Thanks for your responseJ Please find my answers inline. Regards, Vamsi From: Mohamed El-Serngawy [mailto:m.elserngawy@...] Sent: Friday, January 05, 2018 12:35 AM To:

Hey Vamsi, like I noted in my other email about SSL+Restconf, if you've learned anything that you can update the wiki with for this OVSDB+SSL, please feel free. It's open for anyone to help keep

Hi Vamsikrishna, Glad that it works, for the cipher suite issue: 1- first you need to make sure that this cipher (TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256) is supported in both sides client/server.

Hi Mohamed, Sorry!!! That’s a typo in previous email. It’s working after setting as<use-mdsal>false<use-mdsal> Any idea about the non-working cipher issue ? Thanks, Vamsi From:

Hi Mohamed, It worked after setting below tag to trueJ <use-mdsal>false<use-mdsal> I have attached all the steps that I have followed for reference. After adding cipher suite it’s

Hi Vamsikrishna, - As you r using jks files, you need to set <use-mdsal>false<use-mdsal> otherwise ODL will look for the ovs certificate in Mdsal not the jks file. - also please confirm that you used

Hi Mohamed & Jamo, Thanks for your responseJ Also sometimes I see below errors in ODL and OVS logs: D: [id: 0x78b62606, L:/192.168.56.1:6640 - R:/192.168.56.102:41618] -01-03 14:31:42,261

Hi Vamsikrishna, So you are following the previous wiki to establish OVS TLS communication without any cipher-suites specific (just to be not confused with ur other emails). Let's do the

sending again with Mahamed's gmail address

Vamsi, I've added Mohamed explicitly to this email, as he was the author of the wiki page you are referring to. I've personally never set up ovsdb with TLS, so not sure if it even works. It does

Hi All, I am following below wiki for OVSDB-TLS communication: https://wiki.opendaylight.org/view/OVSDB_Integration:TLS_Communication I am seeing below error in ODL logs: