You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Marcus Sorensen (JIRA)" <ji...@apache.org> on 2013/02/19 22:43:12 UTC
[jira] [Commented] (CLOUDSTACK-1328) console view unable to connect
- CPVM SSVM guest VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581654#comment-13581654 ]
Marcus Sorensen commented on CLOUDSTACK-1328:
---------------------------------------------
Some things to try:
You provided ping and ip route for s-1-VM, but not v-2-VM. What do its routes look like?
Can v-2-VM ping 10.223.123.1? If so, then the network was probably configured ok and set up fine by cloudstack. If not, I'd look to see if you configured correct advanced zone, because at first glance everything looks ok, and if it doesn't work it might be a sign that the VM is connected to a bridge that goes nowhere or a bridge that doesn't have access to whatever vlan hosts 10.223.123.0/26.
Can you ping 10.223.123.1 from your firefox host? can you ping 10.223.123.12?
> console view unable to connect - CPVM SSVM guest VMs
> ------------------------------------------------------
>
> Key: CLOUDSTACK-1328
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1328
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: MS rhel6.3 ASF 4.1
> host xen 6.0.2 xen 6.1
> Reporter: angeline shen
> Fix For: 4.1.0
>
> Attachments: management-server.log.gz, Screenshot-s-1-VM - Mozilla Firefox.png, Screenshot-v-2-VM - Mozilla Firefox.png, Screenshot-z1nonvpcV1 - Mozilla Firefox.png
>
>
> MS rhel6.3 ASF 4.1
> host xen 6.0.2 xen 6.1
> 1. advance zone, create VPC network, tier, VMs
> 2. create non-VPC network, VMs
> 3. CPVM SSVM guest VMs - console view displays Unable to connect - Firefox can't establish connection to server at 10-223-123-12.realhostip.com
> On host:
> root@v-2-VM:~# ip route
> 10.223.51.0/26 dev eth1 proto kernel scope link src 10.223.51.31
> 10.223.123.0/26 dev eth2 proto kernel scope link src 10.223.123.12
> 10.223.195.0/24 via 10.223.51.1 dev eth1
> 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.2.183
> default via 10.223.123.1 dev eth2
> root@v-2-VM:~# ifconfig
> eth0 Link encap:Ethernet HWaddr 0e:00:a9:fe:02:b7
> inet addr:169.254.2.183 Bcast:169.254.255.255 Mask:255.255.0.0
> inet6 addr: fe80::c00:a9ff:fefe:2b7/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:130 errors:0 dropped:0 overruns:0 frame:0
> TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:9188 (8.9 KiB) TX bytes:7174 (7.0 KiB)
> Interrupt:9
> eth1 Link encap:Ethernet HWaddr 06:84:16:00:00:15
> inet addr:10.223.51.31 Bcast:10.223.51.63 Mask:255.255.255.192
> inet6 addr: fe80::484:16ff:fe00:15/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:18079 errors:0 dropped:0 overruns:0 frame:0
> TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:2281171 (2.1 MiB) TX bytes:1150 (1.1 KiB)
> Interrupt:10
> eth2 Link encap:Ethernet HWaddr 06:33:8a:00:00:1b
> inet addr:10.223.123.12 Bcast:10.223.123.63 Mask:255.255.255.192
> inet6 addr: fe80::433:8aff:fe00:1b/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:96 errors:0 dropped:0 overruns:0 frame:0
> TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:5372 (5.2 KiB) TX bytes:1518 (1.4 KiB)
> Interrupt:11
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:200 (200.0 B) TX bytes:200 (200.0 B)
> root@v-2-VM:~#
> root@s-1-VM:~# ip route
> 10.223.110.232 via 10.223.51.1 dev eth1
> 10.223.110.254 via 10.223.51.1 dev eth1
> 10.223.195.113 via 10.223.51.1 dev eth1
> 10.223.51.0/26 dev eth1 proto kernel scope link src 10.223.51.25
> 10.223.51.0/26 dev eth3 proto kernel scope link src 10.223.51.30
> 10.223.123.0/26 dev eth2 proto kernel scope link src 10.223.123.13
> 10.223.110.0/24 via 10.223.51.1 dev eth1
> 10.223.195.0/24 via 10.223.51.1 dev eth1
> 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.0.124
> default via 10.223.123.1 dev eth2
> root@s-1-VM:~# ping www.google.com
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira