can the nodes ping each other via the switch? You will need to get that working
first.
From: Mahardhika mahardika.gil...@andalabs.com
To: Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net
Sent: Wednesday, 26 June 2013, 9:04
Subject: Re:
: Mahardhika mahardika.gil...@andalabs.com
To: Darragh O'Reilly dara2002-openst...@yahoo.com; Sergey Skripnick
sskripn...@mirantis.com; openstack@lists.launchpad.net
openstack@lists.launchpad.net
Sent: Wednesday, 26 June 2013, 10:44
Subject: Re: [Openstack] Vlan or Gre on Switch
Sure it is, but it's
at all - take off the 'proto GRE' from tcpdump. Or try again
with the crossover to see how that worked.
From: Mahardhika mahardika.gil...@andalabs.com
To: Darragh O'Reilly dara2002-openst...@yahoo.com; Sergey Skripnick
sskripn...@mirantis.com; openstack
for some reason. Are you
using the same IP addresses for the switch connection as you used for the
direct connection? If you could post 'ovs-vsctl show' and 'ip link' from both
nodes.
From: Mahardhika mahardika.gil...@andalabs.com
To: Darragh O'Reilly dara2002-openst
size: 2 option: 26:mtu 05:ae
FYI, here is what Cisco say about mtu when using VXLAN
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/guide_c07-702975.html#wp989
Darragh.
- Original Message -
From: Darragh O'Reilly dara2002-openst...@yahoo.com
To: Farhan Patwa
rahulsharma...@gmail.com; Darragh O'Reilly
dara2002-openst...@yahoo.com
Cc: OpenStack Maillist openstack@lists.launchpad.net
Sent: Thursday, 30 May 2013, 15:54
Subject: Re: [Openstack] VM Issues on Grizzly Install on Ubuntu 12.04
Hi Darragh,
Thanks a lot for your suggestion. It solved the issue
not sure - try clearing the cookie for the Horizon IP.
From: Rajesh Upadhayay rupadha...@xavient.com
To: 'openstack@lists.launchpad.net' openstack@lists.launchpad.net
Sent: Wednesday, 29 May 2013, 12:02
Subject: [Openstack] Grizzly all-in-one error
Hi,
reducing the mtu for now.
Darragh.
- Original Message -
From: Farhan Patwa farhan.pa...@utsa.edu
To: Darragh O'Reilly dara2002-openst...@yahoo.com; OpenStack Maillist
openstack@lists.launchpad.net
Cc:
Sent: Wednesday, 29 May 2013, 18:14
Subject: Re: [Openstack] VM Issues
Hi,
the ping error connect: Network is unreachable means a route could not be
found.
The gateway 10.245.124.253 for the external subnet is not in the subnet CIDR
10.245.124.64/26.
So I guess a default route was not setup here:
netnode$ ip netns exec router ns route -n
You will need to
the bridge qbr876fed87-40 is supposed to be a Linux bridge and should not
appear in 'ovs-vsctl show'.
What is the value of BRCOMPAT in /etc/default/openvswitch-switch ?
What is the OS+level and how did you install OVS?
From: Qinglong.Meng
BRCOMPAT should be 'no'. What version of ubuntu is this?
From: Qinglong.Meng mengql112...@gmail.com
To: Darragh O'Reilly dara2002-openst...@yahoo.com
Sent: Tuesday, 21 May 2013, 10:40
Subject: Re: [Openstack] [openstack][quantum] How to understand 'ovs-vsctl
the reference to 10.0.2.15 is strange. This happens to be the address the
VirtualBox DHCP server gives to its VMs configured for NAT. Are you using
VirtualBox? Even so I have never found this to be a problem because a Quantum
DHCP namespace is isolated from the main one. Can you provide the
those extensions are specific to the Nicira NVP plugin
https://github.com/openstack/python-quantumclient/commit/d77f86218e4c0c2f5371accce64605e7cfff41c5
From: Qinglong.Meng mengql112...@gmail.com
To: openstack@lists.launchpad.net;
Hi,
I reckon this is because dnsmasq is isolated in the dhcp namespace. You can use
DHCP to push out a specific nameserver:
$ quantum subnet-update sub1 --dns_nameservers 8.8.4.4 8.8.8.8
I can't seem to figure out the syntax to pass just one (list=false is not
working). Or you could use
can you try using -e with tcpdump to see the ethernet headers - it may be arps
from the router to ff:ff:ff:ff:ff:ff that are not getting across in that
direction. You should continue tcpdumping on the devices along the path to the
instance to see where the arp request (or reply) stops. You do
In my setup I see the arp replies being answered by the instance - not dnsmasq.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help :
I'm not sure how to rectify that. You may have to delete the bad row from the
DB and restart the agents:
mysql use quantum;
mysql select * from ovs_tunnel_endpoints;
...
___
Mailing list: https://launchpad.net/~openstack
Post to :
how are you doing the additional snatting outside of openstack in order for
addresses on 192.168 /16 to access the internet?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
Hi,
I don't have an answer, but here are a couple of troubleshooting tips:
- use iptables-save -c to see which chains are being hit. Do a ping and run
iptables-save -c again to see which counters increased.
- use tcpdump to find out where the packets are getting lost. You could start
with the
is nova configured to use cinder?
in nova.conf
volume_api_class=nova.volume.cinder.API
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help :
it seems the ips for the targets are set at the time they were created
$ mysqlmysql use cinder;
mysql select provider_location from volumes;
Try creating a new volume - does it get the new iscsi_ip_address ?
___
Mailing list:
have a look at this
https://answers.launchpad.net/quantum/+question/227321
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help :
its not really obvious, but I believe the iscsi_ip_address needs to be set in
the nova.conf on the **controller** - just want to check you did it there.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
23 matches
Mail list logo
