Looks like it is missconfiged
Inviato da Outlook
On Thu, Jun 25, 2015 at 7:54 AM -0700, "Silvia Fichera" <[email protected]>
wrote:
I also noticed that when I try:
sudo ovs-ofctl dump-flows br-int
to check if the flow was installed properly I receive this message:
2015-06-25T14:36:37Z|00001|vconn|WARN|unix:/var/run/openvswitch/br-int.mgmt:
version negotiation failed (we support version 0x01, peer supports version
0x04)ovs-ofctl: br-int: failed to connect to socket (Broken pipe)
Moreover, in Karaf, I've done:
web:list
and I can see that the services related to neutron are active but in a failed
web state.
ID | State | Web-State | Level | Web-ContextPath
| Name
-------------------------------------------------------------------------------------------------------------------------------------------------219
| Active | Failed | 80 | /controller/nb/v2/connectionmanager
| connectionmanager.northbound (0.1.4.Helium-SR2) 220 | Active
| Failed | 80 | /controller/nb/v2/flowprogrammer |
flowprogrammer.northbound (0.4.4.Helium-SR2) 221 | Active |
Failed | 80 | /controller/nb/v2/hosttracker |
hosttracker.northbound (0.4.4.Helium-SR2) 222 | Active |
Failed | 80 | /controller/nb/v2/networkconfig/bridgedomain |
networkconfig.bridgedomain.northbound (0.0.5.Helium-SR2)223 | Active |
Failed | 80 | /controller/nb/v2/neutron |
networkconfig.neutron.northbound (0.4.4.Helium-SR2) 224 | Active |
Failed | 80 | /controller/nb/v2/staticroute |
forwarding.staticrouting.northbound (0.4.4.Helium-SR2) 225 | Active |
Failed | 80 | /controller/nb/v2/statistics |
statistics.northbound (0.4.4.Helium-SR2) 226 | Active |
Failed | 80 | /controller/nb/v2/subnetservice |
subnets.northbound (0.4.4.Helium-SR2) 227 | Active |
Failed | 80 | /controller/nb/v2/switchmanager |
switchmanager.northbound (0.4.4.Helium-SR2) 228 | Active |
Failed | 80 | /controller/nb/v2/topology |
topology.northbound (0.4.4.Helium-SR2) 229 | Active |
Failed | 80 | /controller/nb/v2/usermanager |
usermanager.northbound (0.0.4.Helium-SR2) 232 | Active |
Failed | 80 | /controller/nb/v2/vtn |
manager.northbound (0.2.2.Helium-SR2) 238 | Active |
Failed | 80 | /ovsdb/nb |
OpenDaylight OVSDB Northbound APIs (0.6.2.Helium-SR2)
Could this be helpful?Thanks
2015-06-25 11:45 GMT+02:00 Silvia Fichera <[email protected]>:
I'm sorry, I have another doubt about promiscuos mode.The controller node and
the compute nodes, as you said, are created with vSphere. But in this
environment there is not only those VMs that I'm using, but also some other.
Who manages this system enabled in promiscuos mode the bridges that connect my
VMs (data network), and the bridge related to the management network.I did not
enabled the bridge that exposes externally ALL VMs that are in the server
(security reasons). Could be this the problem?
Thanks
2015-06-24 15:17 GMT+02:00 Silvia Fichera <[email protected]>:
Hi Venkat,I've checked that everything is in promiscuos mode, the interfaces
are enabled and I have also added the flow that you told me (it's the same of
the wiki). Nothing has changed, links are still broken.Any other hypothesis or
something that I could try?
2015-06-23 21:09 GMT+02:00 Venkatrangan G - ERS, HCL Tech
<[email protected]>:
Hi Silvia,
Thanks for your interest in this integration.
Assuming you are using Helium release (these are some tested steps in Helium
when the same problems were reported).
There are multiple things that you could do to debug this situation
a.
If you are using vsphere to create the control node and compute VM’s then
please enable the (Accept
Promiscuous mode)
b.
Sometimes, the Ethernet interfaces may not be “UP” so please check ifconfig and
if the interface name does ot show up, it is probably
nnot iun UP. Please bring it up manually ifup <interface_name>
c.
Finally, try adding the default flow
ovs-ofctl --protocols=OpenFlow13 add-flow br-int
priority=0,actions=output:CONTROLLER
in all the nodes and try the dlux GUI to cjheck if the links appeared.
Kindly let us know in case of any queries.
Regards,
Venkat G
From: [email protected]
[mailto:[email protected]]
On Behalf Of Silvia Fichera
Sent: 23 June 2015 08:50
To: [email protected]; [email protected]
Subject: [vtn-dev] Broken links
Hi all,
I have installed openstack following the wiki for VTN integration, but when I
visualize the topology I can see the switches but there are no links between
them.
The stacking operation seems to be successful.
Someone can help me.
Ask if you need further details.
Regards
--
Silvia Fichera
::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction,
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and
other defects.
----------------------------------------------------------------------------------------------------------------------------------------------------
--
Silvia Fichera
--
Silvia Fichera
--
Silvia Fichera
!DSPAM:1,558c162049109380587472!
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
