cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthew Midgett <supp...@trickhosting.biz>
Subject Re: Help with SSVM routes
Date Fri, 28 Mar 2014 11:09:51 GMT
I am using kvm and a arp in the router table. I'm using centos and when I get in to the office
I will post my bridges.  Thanks For The help.


Sent from my Galaxy S®III

-------- Original message --------
From: Bjoern Teipel <bjoern.teipel@gmail.com> 
Date:03/28/2014  2:10 AM  (GMT-05:00) 
To: users <users@cloudstack.apache.org> 
Subject: Re: Help with SSVM routes 

If you can't ping 10.0.0.1, the internal network then most likely the
physical network connection or the bridge/vswitch has an issue on the
hypervisor. Wrong traffic label assigned or if you use VLANs then port
mode or tagging could be wrong.
What hypervisor do you use anyway ?

Bjoern

On Thu, Mar 27, 2014 at 10:28 AM, Matthew Midgett
<support@trickhosting.biz> wrote:
> Yes the whole 10.0.0.0/16 is behind our firewall and has Internet access.
>
>
>
> On 03/27/2014 01:22 PM, Erik Weber wrote:
>>
>> Does your management network have internet access? CS routes internal dns
>> over mgmt network and if your mgmt network doesnt have internet access
>> you're basically without dns if you specify the same dns servers (Looks
>> like you did).
>>
>> Erik
>> 27. mars 2014 17:57 skrev "Matthew Midgett" <support@trickhosting.biz>
>> følgende:
>>
>>> I am having trouble getting ssvm to connect to the management lan over
>>> the
>>> private ip. Also I can't get it connect to the outside world. I can ping
>>> the public gateway from ssvm and I can ping the public ip of the ssvm
>>> from
>>> an external address. Something I noticed is that I can't ping anything on
>>> the management lan from the ssvm.
>>>
>>> BTW my primary storage is on fiber so its really not across the
>>> management
>>> lan. My secondary storage is on the management lan.
>>>
>>> Management lan / Storage Network
>>>
>>> 10.0.0.0/16
>>>
>>> Guest Lan
>>>
>>> 10.1.0.0/16
>>>
>>> Public
>>> 216.249.111.0/24
>>>
>>> root@s-34191-VM:~# /usr/local/cloud/systemvm/./ssvm-check.sh
>>> ================================================
>>> First DNS server is  8.8.8.8
>>> PING 8.8.8.8 (8.8.8.8): 56 data bytes
>>> --- 8.8.8.8 ping statistics ---
>>> 2 packets transmitted, 0 packets received, 100% packet loss
>>> WARNING: cannot ping DNS server
>>> route follows
>>> Kernel IP routing table
>>> Destination     Gateway         Genmask         Flags Metric
Ref Use
>>> Iface
>>> 0.0.0.0         216.249.111.1   0.0.0.0         UG    0
0        0 eth2
>>> 8.8.4.4         10.0.0.1        255.255.255.255 UGH   0 0       
0 eth1
>>> 8.8.8.8         10.0.0.1        255.255.255.255 UGH   0 0       
0 eth1
>>> 10.0.0.0        10.0.0.1        255.255.255.0   UG    0 0       
0 eth1
>>> 10.0.0.0        0.0.0.0         255.255.0.0     U    
0 0        0 eth1
>>> 10.0.0.0        0.0.0.0         255.255.0.0     U    
0 0        0 eth3
>>> 169.254.0.0     0.0.0.0         255.255.0.0     U     0 0       
0 eth0
>>> 216.249.111.0   0.0.0.0         255.255.255.0   U     0 0       
0 eth2
>>> ================================================
>>> ERROR: DNS not resolving download.cloud.com
>>> resolv.conf follows
>>> nameserver 8.8.8.8
>>> nameserver 8.8.4.4
>>> nameserver 8.8.8.8
>>> nameserver 8.8.4.4
>>>
>>> root@s-34191-VM:~# ifconfig
>>> eth0      Link encap:Ethernet  HWaddr 0e:00:a9:fe:00:86
>>>            inet addr:169.254.0.134  Bcast:169.254.255.255
>>> Mask:255.255.0.0
>>>            inet6 addr: fe80::c00:a9ff:fefe:86/64 Scope:Link
>>>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>            RX packets:997 errors:0 dropped:0 overruns:0 frame:0
>>>            TX packets:763 errors:0 dropped:0 overruns:0 carrier:0
>>>            collisions:0 txqueuelen:1000
>>>            RX bytes:86924 (84.8 KiB)  TX bytes:103694 (101.2 KiB)
>>>
>>> eth1      Link encap:Ethernet  HWaddr 06:d8:72:00:5a:34
>>>            inet addr:10.0.90.53  Bcast:10.0.255.255  Mask:255.255.0.0
>>>            inet6 addr: fe80::4d8:72ff:fe00:5a34/64 Scope:Link
>>>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>            RX packets:3174 errors:0 dropped:0 overruns:0 frame:0
>>>            TX packets:698 errors:0 dropped:0 overruns:0 carrier:0
>>>            collisions:0 txqueuelen:1000
>>>            RX bytes:223025 (217.7 KiB)  TX bytes:49040 (47.8 KiB)
>>>
>>> eth2      Link encap:Ethernet  HWaddr 06:59:b4:00:fe:fe
>>>            inet addr:216.249.111.2  Bcast:216.249.111.255
>>> Mask:255.255.255.0
>>>            inet6 addr: fe80::459:b4ff:fe00:fefe/64 Scope:Link
>>>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>            RX packets:9223 errors:0 dropped:10 overruns:0 frame:0
>>>            TX packets:288 errors:0 dropped:0 overruns:0 carrier:0
>>>            collisions:0 txqueuelen:1000
>>>            RX bytes:614771 (600.3 KiB)  TX bytes:25160 (24.5 KiB)
>>>
>>> eth3      Link encap:Ethernet  HWaddr 06:96:be:00:18:d2
>>>            inet addr:10.0.24.211  Bcast:10.0.255.255 Mask:255.255.0.0
>>>            inet6 addr: fe80::496:beff:fe00:18d2/64 Scope:Link
>>>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>            RX packets:3051 errors:0 dropped:0 overruns:0 frame:0
>>>            TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
>>>            collisions:0 txqueuelen:1000
>>>            RX bytes:215627 (210.5 KiB)  TX bytes:318 (318.0 B)
>>>
>>> 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:0 errors:0 dropped:0 overruns:0 frame:0
>>>            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>            collisions:0 txqueuelen:0
>>>            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>>
>>>
>>>
>
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message