I realize that RFC 7047 isn't very clear that the monitor ID has to be unique. I added a clarification to ovsdb-server(1) in the OVS distribution.
On Fri, Apr 04, 2014 at 01:38:36AM +0000, Duggisetty, Sudheer wrote: > Thanks Ben for your responses... > > Sudheer > > -----Original Message----- > From: Ben Pfaff [mailto:[email protected]] > Sent: Thursday, April 03, 2014 9:54 PM > To: Duggisetty, Sudheer > Cc: [email protected]; Krishnamurthy, Manikantan; Manjeshwar, Radhika > Hegde; Kenchappa, Ravindra > Subject: Re: [ovs-discuss] OvsdbServer Issues.... > > On Thu, Apr 03, 2014 at 06:40:18AM +0000, Duggisetty, Sudheer wrote: > > I'm using ovsdb-server of openvswitch > > 2.1.0<http://openvswitch.org/releases/openvswitch-2.1.0.tar.gz> version > > with VTEP schema. I see the following issues: > > > > > > 1. Unable to use multiple times "Monitor" request for the same table. > > > > * First time, when I sent "Monitor" request for Manager table, it > > is success. > > Request-> > > ["hardware_vtep",null,{"Global":{"columns":["managers"]},"Manager":{"c > > olumns":["target"]}}] > > > > Response -> {"id":"100","result":{},"error":null} > > > > > > > > * Second time, when I sent "Monitor" request for Manager table with > > same/different "id" and I got the following "duplicate monitor ID" error. > > > > Request-> ["hardware_vtep",null,{"Global":{"columns":["managers"]},"Ma > > Request-> nager":{"columns":["target"]}}] > > > > Response -> {"id":"101","result":{"error":"syntax > > error","details":"duplicate monitor ID","syntax":"null"},"error":null} > > > > I have opened TCP connection and send the multiple "Monitor" requests. Why > > it is not possible to send multiple times of "Monitor" protocol for the > > same table and on the same connection? > > Because you used a duplicate monitor ID. Use something different for the > monitor ID in each request. You used null in each case. > > > > > 2. "Monitor Cancel" operation is not all working after "Monitor" > > request is sent and getting the "invalid parameters" error. > > > > Request-> ["hardware_vtep",null,{"Global":{"columns":["managers"]},"Ma > > Request-> nager":{"columns":["target"]}}] > > > > monitor cancel response-> {"id":"103","error":"invalid parameters"} > > That isn't the right format for the arguments to a monitor_cancel, which just > takes the monitor ID. > > > 3. How to get the current table data without using "Monitor" request? > > Because I'm unable to use multiple times of "Monitor" request as > > mentioned in point 1 and also I will get notification for rows I > > created. Is it possible to read the tables data of OVSDB-Server > > without using "Monitor" request? > > Yes. Use a transaction. > > Have you read the OVSDB specification, or RFC 7047? The latter is slightly > better written. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
