Instance trendalyze2 shows status running but we can't access from SSH

root@trendalyze1:~# ssh -i trendalyze_spain2.pem root@130.206.118.226
^C
root@trendalyze1:~# ping 130.206.118.226
PING 130.206.118.226 (130.206.118.226) 56(84) bytes of data.
^C
— 130.206.118.226 ping statistics —
11 packets transmitted, 0 received, 100% packet loss, time 10078ms

We can access from the console under FIWARE lab (see attached from console)

I tried to disassociate and re-associate the floating IP address but it
didn't help

I also disassociate and re-associate the floating IP with another instance
(trendalyzeOrion) but this didn't work either

I released the floating IP and allocate a new one 130.206.119.185 and
associate this with trendalyze2

130.206.119.185 Trendalyze2 public-ext-net-01

But having similar issues to access with this IP address

root@trendalyze1:~# ssh -i trendalyze_spain2.pem root@130.206.119.185
ssh: connect to host 130.206.119.185 port 22: No route to host
root@trendalyze1:~# ping 130.206.119.185
PING 130.206.119.185 (130.206.119.185) 56(84) bytes of data.
From 130.206.112.2 icmp_seq=1 Destination Host Unreachable
From 130.206.112.2 icmp_seq=3 Destination Host Unreachable
From 130.206.112.2 icmp_seq=2 Destination Host Unreachable
From 130.206.112.2 icmp_seq=4 Destination Host Unreachable
From 130.206.112.2 icmp_seq=5 Destination Host Unreachable
From 130.206.112.2 icmp_seq=6 Destination Host Unreachable
^C
— 130.206.119.185 ping statistics —
7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6017ms
pipe 4
root@trendalyze1:~#

So I conclude this is a network access issue

–

Dave Watson
+447741675325 (UK)
+17862642749 (USA)

[Created via e-mail received from: Dave Watson <watson.dave@gmail.com>]