Hi All,
I am testing on CentOS 6.5. Now I am stuck while the primary storage adding
Something went wrong; please correct the following:
Failed to add data store: Can not create storage pool through host 1 due to
Catch Exception com.cloud.utils.exception.CloudRuntimeException, create
StoragePool failed due to com.cloud.utils.exception.CloudRuntimeException:
Unable to create NFS SR Pool[2|10.10.100.11:2049|/Primary] on
host:a4e0efec-d177-45ef-b5e4-d449aca2bdfa pool: 10.10.100.11/Primary
I could not able to ping 10.10.100.11 from xenserver.
I added the IPaddress vi xencenter.
serverInterface Network NIC IPSetup IPAddress
Subnet Gateway
Xenserver01 Management MGMT NIC0 static 192.168.56.12
255.255.255.0 192.168.56.1
xenserver02 PRI-STOR PRI-STORAGE NIC3 static 10.10.100.11
255.255.255.0
xenserver02 SEC-STOR SEC-STORAGE NIC3 static 10.10.101.11
255.255.255.0
What really went wrong. I could not able to ping 10.10.100.1 101.1 from
xenserver.
Thanks,
Keerthi
On Sun, Feb 8, 2015 at 4:14 PM, Rohit Yadav rohit.ya...@shapeblue.com
wrote:
Hi Keerthiraja,
Avoid relying on testing repos http://packages.bhaisaab.org as they are
temporary and may change from time to time without notification.
I would suggest removing old CloudStack management server cache after
every upgrade:
- Stop management server one by one
- For each stopped management server, on Debian for example - remove rm
-fr /var/cache/cloudstack/management/work/*
- Start management server again, this will remove old UI’s cache which may
be affecting you
If you’re using CentOS, let me know if this worked for you as the above
has been tested only on Debian.
On 08-Feb-2015, at 4:05 pm, Keerthiraja SJ sjkeer...@gmail.com wrote:
I am using the repo with below link. I have choose Advance Network with
Security Group.
http://packages.bhaisaab.org/cloudstack/testing/centos/4.5/
This are my below csman configuration.
eth0 Link encap:Ethernet HWaddr 08:00:27:8D:E8:E2
inet addr:192.168.56.11 Bcast:192.168.56.255
Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe8d:e8e2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2400 errors:0 dropped:0 overruns:0 frame:0
TX packets:3274 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:523822 (511.5 KiB) TX bytes:3401559 (3.2 MiB)
Interrupt:19 Base address:0xd020
eth1 Link encap:Ethernet HWaddr 08:00:27:97:87:7A
inet addr:10.0.2.11 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe97:877a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:33 errors:0 dropped:0 overruns:0 frame:0
TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10791 (10.5 KiB) TX bytes:4245 (4.1 KiB)
eth2 Link encap:Ethernet HWaddr 08:00:27:CB:13:18
inet addr:172.30.0.11 Bcast:172.30.0.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fecb:1318/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:186 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:63612 (62.1 KiB) TX bytes:746 (746.0 b)
eth3 Link encap:Ethernet HWaddr 08:00:27:C3:5F:72
inet6 addr: fe80::a00:27ff:fec3:5f72/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:181 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:61902 (60.4 KiB) TX bytes:2140 (2.0 KiB)
eth3.100 Link encap:Ethernet HWaddr 08:00:27:C3:5F:72
inet addr:10.10.100.11 Bcast:10.10.100.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fec3:5f72/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:816 (816.0 b)
eth3.101 Link encap:Ethernet HWaddr 08:00:27:C3:5F:72
inet addr:10.10.101.11 Bcast:10.10.101.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fec3:5f72/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:746 (746.0 b)
Is any thing wrong. I am really worried about my testing getting delayed
from migration 4.2 to 4.5
Thanks,
