<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"><div>Thanks Andreas, that's a great vnc tip. I'll try that today. <br>
<br>
Tyler<br>
<br>
<font color="#888888"><font color="#888888">Sent from my android device.</font></font><br><br>-----Original Message-----<br>From: Andreas Scheuring <scheuran@linux.vnet.ibm.com><br>To: Tyler Couto <tcouto@certain.com><br>Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org><br>Sent: Wed, 18 Nov 2015 1:10 AM<br>Subject: Re: [Openstack] Trouble connecting to a new VM<br><br></div>Tyler, <br>
to access your vnc console you can try the following:<br>
<br>
- Login to your compute node<br>
- run "virsh list --all"<br>
- run "virsh dumpxml <vm-name>"<br>
- check the devic section about vnc. You should find something like this<br>
<graphics type='vnc' port='5900' autoport='yes' listen='0.0.0.0'><br>
<listen type='address' address='0.0.0.0'/><br>
</graphics><br>
<br>
Ensure that the listen address is either 0.0.0.0 or something that is<br>
reachable from your controller node. Remember the port.<br>
<br>
Now you can open the console using any vncviewer from the compute node<br>
with<br>
> vncviewer localhost:5900<br>
<br>
Or from your some other node<br>
vncviewer <compute-node-ip>:5900<br>
<br>
<br>
If the listen address is something else, make check your <a href="http://nova.conf">nova.conf</a><br>
regarding vnc settings<br>
<br>
If the whole section does not show up, check that you have vnc enabled<br>
in your <a href="http://nova.conf">nova.conf</a><br>
<br>
<br>
<br>
Regarding your ovs setup. Something seems to be wrong, as both of your<br>
routers interfaces go into br-int<br>
- qrxxxx<br>
- qqxxx<br>
<br>
qqxxx is the external leg of the router and should sit on br-ex. Please<br>
check your l3 configuration file. <br>
<br>
<br>
If you need some help, please provide the l3 configuration file and the<br>
ip configuration of your controller node. In addition the neutron<br>
network details (neutron net-list & neutron net-show xxx) would be<br>
helpful.<br>
<br>
-- <br>
Andreas<br>
(IRC: scheuran)<br>
<br>
<br>
<br>
On Di, 2015-11-17 at 09:31 -0800, Tyler Couto wrote:<br>
> Thanks Andreas. My security groups do allow icmp traffic.<br>
> +---------+----------------------------------------------------------------<br>
> ------+<br>
> | name | security_group_rules<br>
> |<br>
> +---------+----------------------------------------------------------------<br>
> ------+<br>
> | default | egress, IPv4<br>
> |<br>
> | | egress, IPv6<br>
> |<br>
> | | ingress, IPv4, 22/tcp, remote_ip_prefix: 0.0.0.0/0<br>
> |<br>
> | | ingress, IPv4, icmp, remote_ip_prefix: 0.0.0.0/0<br>
> |<br>
> | | ingress, IPv4, remote_group_id:<br>
> d404679b-aeed-4d2f-bea9-2c7d19ff3fb1 |<br>
> | | ingress, IPv6, remote_group_id:<br>
> d404679b-aeed-4d2f-bea9-2c7d19ff3fb1 |<br>
> +---------++<br>
> <br>
> I canΉt access my VMΉs console, so I do not know whether I can ping from<br>
> my VM. I figured this might be a related issue. I receive this error on<br>
> when trying to access the noVNC console:<br>
> Failed to connect to server (code: 1006)<br>
> <br>
> <br>
> This is a two node setup. I have one controller/neutron-network node.<br>
> HereΉs the output of 'ovs-vsctl showΉ:<br>
> <br>
> Bridge br-tun<br>
> fail_mode: secure<br>
> Port "gre-ac10183d"<br>
> Interface "gre-ac10183d"<br>
> type: gre<br>
> options: {df_default="true", in_key=flow, local_ip="<a href="http://172.16.24.60">172.16.24.60</a>",<br>
> out_key=flow, remote_ip="<a href="http://172.16.24.61">172.16.24.61</a>"}<br>
> Port gre-mirror<br>
> Interface gre-mirror<br>
> Port br-tun<br>
> Interface br-tun<br>
> type: internal<br>
> Port patch-int<br>
> Interface patch-int<br>
> type: patch<br>
> options: {peer=patch-tun}<br>
> Bridge br-ex<br>
> Port "enp4s0f0"<br>
> Interface "enp4s0f0"<br>
> Port phy-br-ex<br>
> Interface phy-br-ex<br>
> type: patch<br>
> options: {peer=int-br-ex}<br>
> Port br-ex<br>
> Interface br-ex<br>
> type: internal<br>
> Port "enp4s0f1"<br>
> Interface "enp4s0f1"<br>
> Bridge br-int<br>
> fail_mode: secure<br>
> Port "qr-a81f0614-0e"<br>
> tag: 2<br>
> Interface "qr-a81f0614-0e"<br>
> type: internal<br>
> Port "qg-289ea4d2-29"<br>
> tag: 5<br>
> Interface "qg-289ea4d2-29"<br>
> type: internal<br>
> Port br-int<br>
> Interface br-int<br>
> type: internal<br>
> Port patch-tun<br>
> Interface patch-tun<br>
> type: patch<br>
> options: {peer=patch-int}<br>
> Port int-br-ex<br>
> Interface int-br-ex<br>
> type: patch<br>
> options: {peer=phy-br-ex}<br>
> Port "tap468d3ee4-c0"<br>
> tag: 4095<br>
> Interface "tap468d3ee4-c0"<br>
> type: internal<br>
> ovs_version: "2.3.1"<br>
> <br>
> <br>
> I have on compute node. HereΉs the output of 'ovs-vsctl show':<br>
> <br>
> Bridge br-int<br>
> fail_mode: secure<br>
> Port "qvoc6d01e4b-1d"<br>
> tag: 1<br>
> Interface "qvoc6d01e4b-1d"<br>
> Port br-int<br>
> Interface br-int<br>
> type: internal<br>
> Port patch-tun<br>
> Interface patch-tun<br>
> type: patch<br>
> options: {peer=patch-int}<br>
> Bridge br-tun<br>
> fail_mode: secure<br>
> Port br-tun<br>
> Interface br-tun<br>
> type: internal<br>
> Port patch-int<br>
> Interface patch-int<br>
> type: patch<br>
> options: {peer=patch-tun}<br>
> Port "gre-ac10183c"<br>
> Interface "gre-ac10183c"<br>
> type: gre<br>
> options: {df_default="true", in_key=flow, local_ip="<a href="http://172.16.24.61">172.16.24.61</a>",<br>
> out_key=flow, remote_ip="<a href="http://172.16.24.60">172.16.24.60</a>"}<br>
> Port gre-mirror<br>
> Interface gre-mirror<br>
> Port "tap0"<br>
> Interface "tap0"<br>
> ovs_version: "2.3.1"<br>
> <br>
> <br>
> I also have a laptop on the same network as the openstack machines. I can<br>
> successfully ping the interface of the neutron router from my laptop.<br>
> <br>
> As far as the physical interfaces, I am only using one physical interface<br>
> on each openstack machine. I know this is not the recommended setup, but<br>
> since this is only a POC, I wanted to keep it simple.<br>
> <br>
> -Tyler<br>
> <br>
> <br>
> <br>
> On 11/17/15, 12:48 AM, "Andreas Scheuring" <<a href="mailto:scheuran@linux.vnet.ibm.com">scheuran@linux.vnet.ibm.com</a>><br>
> wrote:<br>
> <br>
> >ease check your Security Groups first. <br>
> <br>
<br>