You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Simon Schneider <ss...@mackoy.de> on 2013/04/30 13:26:13 UTC

Network Problems from within SSVM

Hi List,

we are trying to setup a Cloudstack configuration, and have it working to the point that the SSVM is starting up and running.
The problem is, that from within the SSVM one cannot ping the management server. Which is the reason, we think,
that we are getting log entries in the management server log saying:

There is no secondary storage VM for secondary storage host nfs://192.168.122.130/export/secondary

Following some information about our configuration:

/etc/network/interfaces on SSVM:
auto lo eth0 eth1 eth2
iface lo inet loopback

iface  eth0 inet static
  address 169.254.2.31 
  netmask 255.255.0.0
iface  eth1 inet static
  address 192.168.122.197 
  netmask 255.255.255.0
iface  eth2 inet static
  address 192.168.122.223 
  netmask 255.255.255.0

auto eth3
iface  eth3 inet static
  address 192.168.122.199 
  netmask 255.255.255.0
------------------------------------------------

Output of netstat -rn on SSVM:
root@s-6-VM:~# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
8.8.8.8         192.168.122.2   255.255.255.255 UGH       0 0          0 eth1
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 eth1
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 eth2
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 eth3
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth0
0.0.0.0         192.168.122.2   0.0.0.0         UG        0 0          0 eth2
---------------------------------------------------------------------------------------------------

/etc/network/interfaces on Management Server:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#auto eth0
#iface eth0 inet dhcp

auto eth0.100
iface eth0.100 inet static
    address 192.168.122.130
    netmask 255.255.255.0
    gateway 192.168.122.2
    dns-nameservers 8.8.8.8 8.8.4.4
    vlan_raw_device eth0

auto eth0.200
iface eth0.200 inet manual
    vlan_raw_device eth0

auto eth0.300
    iface eth0.300 inet manual
    vlan_raw_device eth0

# Public network
auto cloudbr0
iface cloudbr0 inet manual
    bridge_ports eth0.200
    bridge_fd 5
    bridge_stp off
    bridge_maxwait 1

# Private network
auto cloudbr1
iface cloudbr1 inet manual
    bridge_ports eth0.300
    bridge_fd 5
    bridge_stp off
    bridge_maxwait 1
---------------------------------------------------

netstat -rn on Management Server:
root@managment:~# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.122.2   0.0.0.0         UG        0 0          0 eth0.100
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 cloud0
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 eth0.100


Any help greatly appreciated.

Regards, Simon



RE: Network Problems from within SSVM

Posted by Oliver Leach <Ol...@tatacommunications.com>.
Can you ping your gateway, 192.168.122.2? Are there any iptables rules on the mgmt server? And are your exports set up correctly on 192.168.122.130? How about if you downed some on the interfaces on the SSVM and then tried to ping the management server. Say ifconfig eth0 down etc.. Does any of the interfaces work if the others are all disabled? 

Oliver
--


-----Original Message-----
From: Simon Schneider [mailto:sschneider@mackoy.de] 
Sent: Tuesday, April 30, 2013 12:26 PM
To: users@cloudstack.apache.org
Subject: Network Problems from within SSVM

Hi List,

we are trying to setup a Cloudstack configuration, and have it working to the point that the SSVM is starting up and running.
The problem is, that from within the SSVM one cannot ping the management server. Which is the reason, we think, that we are getting log entries in the management server log saying:

There is no secondary storage VM for secondary storage host nfs://192.168.122.130/export/secondary

Following some information about our configuration:

/etc/network/interfaces on SSVM:
auto lo eth0 eth1 eth2
iface lo inet loopback

iface  eth0 inet static
  address 169.254.2.31
  netmask 255.255.0.0
iface  eth1 inet static
  address 192.168.122.197
  netmask 255.255.255.0
iface  eth2 inet static
  address 192.168.122.223
  netmask 255.255.255.0

auto eth3
iface  eth3 inet static
  address 192.168.122.199
  netmask 255.255.255.0
------------------------------------------------

Output of netstat -rn on SSVM:
root@s-6-VM:~# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
8.8.8.8         192.168.122.2   255.255.255.255 UGH       0 0          0 eth1
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 eth1
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 eth2
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 eth3
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth0
0.0.0.0         192.168.122.2   0.0.0.0         UG        0 0          0 eth2
---------------------------------------------------------------------------------------------------

/etc/network/interfaces on Management Server:
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#auto eth0
#iface eth0 inet dhcp

auto eth0.100
iface eth0.100 inet static
    address 192.168.122.130
    netmask 255.255.255.0
    gateway 192.168.122.2
    dns-nameservers 8.8.8.8 8.8.4.4
    vlan_raw_device eth0

auto eth0.200
iface eth0.200 inet manual
    vlan_raw_device eth0

auto eth0.300
    iface eth0.300 inet manual
    vlan_raw_device eth0

# Public network
auto cloudbr0
iface cloudbr0 inet manual
    bridge_ports eth0.200
    bridge_fd 5
    bridge_stp off
    bridge_maxwait 1

# Private network
auto cloudbr1
iface cloudbr1 inet manual
    bridge_ports eth0.300
    bridge_fd 5
    bridge_stp off
    bridge_maxwait 1
---------------------------------------------------

netstat -rn on Management Server:
root@managment:~# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.122.2   0.0.0.0         UG        0 0          0 eth0.100
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 cloud0
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 eth0.100


Any help greatly appreciated.

Regards, Simon



Re: Network Problems from within SSVM

Posted by pr...@assistanz.com.
Hi,

 I have implemented new cloudstack build dated on april 23. I  receive
same error.

There is no secondary storage VM for secondary storage host

 any fix?


Regards,
Prakash.M


> Hi List,
>
> we are trying to setup a Cloudstack configuration, and have it working to
> the point that the SSVM is starting up and running.
> The problem is, that from within the SSVM one cannot ping the management
> server. Which is the reason, we think,
> that we are getting log entries in the management server log saying:
>
> There is no secondary storage VM for secondary storage host
> nfs://192.168.122.130/export/secondary
>
> Following some information about our configuration:
>
> /etc/network/interfaces on SSVM:
> auto lo eth0 eth1 eth2
> iface lo inet loopback
>
> iface  eth0 inet static
>   address 169.254.2.31
>   netmask 255.255.0.0
> iface  eth1 inet static
>   address 192.168.122.197
>   netmask 255.255.255.0
> iface  eth2 inet static
>   address 192.168.122.223
>   netmask 255.255.255.0
>
> auto eth3
> iface  eth3 inet static
>   address 192.168.122.199
>   netmask 255.255.255.0
> ------------------------------------------------
>
> Output of netstat -rn on SSVM:
> root@s-6-VM:~# netstat -rn
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt
> Iface
> 8.8.8.8         192.168.122.2   255.255.255.255 UGH       0 0          0
> eth1
> 192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0
> eth1
> 192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0
> eth2
> 192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0
> eth3
> 169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0
> eth0
> 0.0.0.0         192.168.122.2   0.0.0.0         UG        0 0          0
> eth2
> ---------------------------------------------------------------------------------------------------
>
> /etc/network/interfaces on Management Server:
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> #auto eth0
> #iface eth0 inet dhcp
>
> auto eth0.100
> iface eth0.100 inet static
>     address 192.168.122.130
>     netmask 255.255.255.0
>     gateway 192.168.122.2
>     dns-nameservers 8.8.8.8 8.8.4.4
>     vlan_raw_device eth0
>
> auto eth0.200
> iface eth0.200 inet manual
>     vlan_raw_device eth0
>
> auto eth0.300
>     iface eth0.300 inet manual
>     vlan_raw_device eth0
>
> # Public network
> auto cloudbr0
> iface cloudbr0 inet manual
>     bridge_ports eth0.200
>     bridge_fd 5
>     bridge_stp off
>     bridge_maxwait 1
>
> # Private network
> auto cloudbr1
> iface cloudbr1 inet manual
>     bridge_ports eth0.300
>     bridge_fd 5
>     bridge_stp off
>     bridge_maxwait 1
> ---------------------------------------------------
>
> netstat -rn on Management Server:
> root@managment:~# netstat -rn
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt
> Iface
> 0.0.0.0         192.168.122.2   0.0.0.0         UG        0 0          0
> eth0.100
> 169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0
> cloud0
> 192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0
> eth0.100
>
>
> Any help greatly appreciated.
>
> Regards, Simon
>
>
>