satis egitimisatis egitimitengda.pro
Welcome, Guest
Username: Password: Remember me
This forum is dedicated to discussions around storage and networking in cloud computing.
  • Page:
  • 1
  • 2

TOPIC: Wrong routing table of SSVM

Wrong routing table of SSVM 1 year 11 months ago #9738

  • dingvn
  • dingvn's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 1
  • Karma: 0
Hi all,

I'm using CloudStack 3 on CentOS 6.2, my Hypervisor is XenServer. I have deployed SSVM and Console Proxy successfully. My Console Proxy can access internet, ping GW,... But my SSVM can' access internet because of wrong routing table (i think so).

When i edit SSVM's routing table
from
192.168.10.0 20.0.0.1 255.255.255.0 UG 0 0 0 eth1
to
192.168.10.0 0.0.0.0 255.255.255.0 UG 0 0 0 eth2

so it can access internet and resolve download.cloud.com. But i don't know how to make it default everytime SSVM start/restart. Anybody can help me ?


Console Proxy


My Console Proxy routing table
root@v-51-VM:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.10.0    0.0.0.0         255.255.255.0   U     0      0        0 eth2
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
20.0.0.0        0.0.0.0         255.0.0.0       U     0      0        0 eth1
0.0.0.0         192.168.10.1    0.0.0.0         UG    0      0        0 eth2


My SSVM routing table is
root@s-57-VM:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.10.0    20.0.0.1        255.255.255.0   UG    0      0        0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
20.0.0.0        0.0.0.0         255.0.0.0       U     0      0        0 eth1
20.0.0.0        0.0.0.0         255.0.0.0       U     0      0        0 eth3
0.0.0.0         192.168.10.1    0.0.0.0         UG    0      0        0 eth2

Thanks!
Last Edit: 1 year 11 months ago by dingvn.
The administrator has disabled public write access.

Re: Wrong routing table of SSVM 1 year 11 months ago #9741

  • chirauki
  • chirauki's Avatar
  • OFFLINE
  • Gold Boarder
  • Posts: 193
  • Thank you received: 19
  • Karma: 11
Hi there,

I guess your pod network range is 20.0.0.0/8? What about internal DNS? Everytime I had this situation is because system vm's will use the private address (in the pod rage it is) to access internal DNS. If they are not in the same network, it will try to reach the DNS throug the pod gateway address.

thx.
The administrator has disabled public write access.
The following user(s) said Thank You: prashanth.reddy

Re: Wrong routing table of SSVM 1 year 11 months ago #9754

  • Le
  • Le's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 13
  • Karma: 0
yes, our pod network range is 20.0.0.0/8.
Internal DNS is 20.0.0.1 (though it may not be configured)

ID 46fef82e-ed43-4080-8fa1-60943f040523
Allocation State Enabled
DNS 1 192.168.10.1
DNS 2
Internal DNS 1 20.0.0.1
Internal DNS 2
Domain
Network Type Advanced
Guest CIDR 10.0.0.0/8
Network Domain

BTW, could you elaborate more? Why DNS is related to routing table?
Thanks so much.
The administrator has disabled public write access.

Re: Wrong routing table of SSVM 1 year 11 months ago #9757

  • chirauki
  • chirauki's Avatar
  • OFFLINE
  • Gold Boarder
  • Posts: 193
  • Thank you received: 19
  • Karma: 11
Hi,

In that case, you have your internal DNS in the pod network range, so it's not that. If internal DNS was in another network you would get a route to that address via the pod gateway.

Anyway, who is your NFS server for secondary storage? If is some machine in the public range, maybe the same is happening but instead of DNS your route is to get to the NFS server. Is it possible?

thx
The administrator has disabled public write access.

Re: Wrong routing table of SSVM 1 year 11 months ago #9766

  • Le
  • Le's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 13
  • Karma: 0
For Internal DNS, we only filled 20.0.0.1 for the sake of fill-in, we don't actually have internal DNS.
For NFS server, both primary and secondary is in 20.0.0.0/8 network.

The management server has a public NIC (192.168.10.10). Will it affect something?
We changed the management cidr in Global setting to 20.0.0.0/8
The administrator has disabled public write access.

Re: Wrong routing table of SSVM 1 year 11 months ago #9811

  • Le
  • Le's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 13
  • Karma: 0
Any help? Thanks
The administrator has disabled public write access.
  • Page:
  • 1
  • 2
Time to create page: 0.323 seconds

Open@Citrix

Citrix supports the open source community via developer support and evangeslism. We have a number of developers and evangelists that participate actively in the open source community in Apache Cloudstack, OpenDaylight, Xen Project and XenServer. We also conduct educational activities via the Build A Cloud events held all over the world. 

Connect