2017-01-06 18:05:37 +0200 | received badge | ● Self-Learner (source) |
2017-01-06 18:05:37 +0200 | received badge | ● Teacher (source) |
2017-01-01 09:44:55 +0200 | answered a question | OVS set_manager failed Thanks to Alin Serdean for the support. The log errors are fixed by this patch: http://patchwork.ozlabs.org/patch/705... Additional steps to make set-manager work vs. OpenDaylight (Windows Server 2012 R2), from the elavated command prompt: sc config ovsdb-server binPath= "\"C:\Program Files\Cloudbase Solutions\Open vSwitch\bin\ovsdb-server.exe\" --log-file=\"C:\Program Files\Cloudbase Solutions\Open vSwitch\logs\ovsdb-server.log\" --pidfile --service --service-monitor --unixctl=\"C:\ProgramData\openvswitch\ovsdb-server.ctl\" --remote=punix:\"C:\ProgramData\openvswitch\db.sock\" \"C:\Program Files\Cloudbase Solutions\Open vSwitch\conf\conf.db\" "\"--remote=db:OpenvSwitch,OpenvSwitch,manager_options\" net stop ovsdb-server /y net start ovsdb-server |
2016-12-16 13:50:50 +0200 | received badge | ● Famous Question (source) |
2016-12-15 10:27:51 +0200 | received badge | ● Notable Question (source) |
2016-12-15 05:49:29 +0200 | received badge | ● Popular Question (source) |
2016-12-13 08:17:51 +0200 | received badge | ● Editor (source) |
2016-12-12 16:01:43 +0200 | asked a question | OVS set_manager failed Hi, Trying to add Hyper-V with OVS as OpenStack compute Node. I have a Devstack machine as the control node, with OpenDaylight as the network controller. I followed the OVS for Hyper-V installation instructions but I never get to the state where the OVS shows is_connected to the Manager ( OpenDaylight in this case). I get the following errors all over the log: 2016-12-13T18:02:53.259Z|200207|netdev_windows|ERR|Call to GetAdaptersAddresses failed with error: The file name is too long. 2016-12-13T18:02:53.259Z|200208|inband|WARN|br-port1: cannot find route for controller (10.0.43.69): No such device or address 2016-12-13T18:02:53.261Z|200209|netdevwindows|ERR|Call to GetAdaptersAddresses failed with error: The file name is too long. 2016-12-13T18:02:53.261Z|200210|in_band|WARN|br-int: cannot find route for controller (10.0.43.69): No such device or address co |