Dear Yasir

In order to provide help from our regional helpdesk team, could you
please specify which region you are using?

Kind regards
IWAVE team, on behalf of helpdesk team

_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

Berlin...

Sent from my Windows Phone

Please send the answer to this request to yasirk@connecterra.io

The following message was send to the user:

Your VMs have two tenant networks assigned. The configuration you did, isn't really expected.

You should either use the shared network (node-int-net-01 / 192.168.1.0/24), then you don't need a virtual router and additional tenant network, or you create an virtual router and attach your own tenant network to it. VMs can be launched afterwards using the newly created tenant network. As you have already created a vrouter and a tenant network, you should only attach this network to your instances.

After you did this ICMP and SSH connections to the VMs are possible, if your default security group has the appropriate rules configured. Any other connections are blocked at the moment by the firewall of the Berlin node. Additional ports could be opened on request.

Thanks, I am able to SSH into the machines now but the machiens don’t have internet access. Do I need to opn the ports for outgoing access as well?

Secondly, would you also know how to access the COSMOS GE? What user/pass is to be used?

From: Help-Desk jira-help-desk@fi-ware.org
Sent: Tuesday, June 9, 2015 2:25 PM
To: Yasir Khokhar
Subject: [FI-WARE-JIRA] (HELP-3234) [Fiware-lab-help] FI-Lab Assistance

Your VMs have two tenant networks assigned. The configuration you did, isn't really expected.

You should either use the shared network (node-int-net-01 / 192.168.1.0/24), then you don't need a virtual router and additional tenant network, or you create an virtual router and attach your own tenant network to it. VMs can be launched afterwards using the newly created tenant network. As you have already created a vrouter and a tenant network, you should only attach this network to your instances.
6860e4ae-ebd2-43a5-8186-dac7f2de37b4

CTRABIGBOX

ACTIVE

Running

public-ctra=192.168
.191.100, 193.175.132.48; node-int-net-01=192.168.1.165

23611e15-8898-4ec8-bc11-eb467c0d26f3

CTRASMALLBOX

ACTIVE

Running

public-ctra=192.168
.191.102, 193.175.132.47; node-int-net-01=192.168.1.166

After you did this ICMP and SSH connections to the VMs are possible, if your default security group has the appropriate rules configured. Any other connections are blocked at the moment by the firewall of the Berlin node. Additional ports could be opened on request.
[cid:image001.jpg@01D0A30A.26F168A0]

FW External User</secure/ViewProfile.jspa?name=fw.ext.user> created an issue

Help-Desk<https://jira.fiware.org/browse/HELP> / [extRequest] <https://jira.fiware.org/browse/HELP-3234> HELP-3234<https://jira.fiware.org/browse/HELP-3234>

[Fiware-lab-help] FI-Lab Assistance<https://jira.fiware.org/browse/HELP-3234>

Issue Type:

[extRequest]extRequest

Assignee:

Berlin Node Helpdesk</secure/ViewProfile.jspa?name=BerlinSupportTeam>

Components:

FIWARE-LAB-HELP

Created:

08/Jun/15 2:19 PM

Priority:

[Major]Major

Reporter:

FW External User</secure/ViewProfile.jspa?name=fw.ext.user>

Status:

[In Progress]In Progress

Hello there,

I'm trying to connect to our VM's via public IP but the connection is refused. The router is setup, IP's assigned and security group has the port open as well. The tenant ID is 8781, can you please have a look and let us know what we're doing wrong?

Regards,
YSK

Are you just not able to reach an internet service by its domain name or even with its IP-address?

Please check on your VMs if you can ping for example "8.8.8.8". And after that please try the same with "google.de".

As I can see your subnet "ctra-subnet" has no nameserver configured. If the ping just fails by using a domain name, please add a nameserver to your subnet.