Comment by nspada@gilrma.fr :

Hi,

The issue having not being solved yet, we have proceeded to a new setting-up of the VMs.

Could you also open the following ports 8010, 8020, 8030, 8040, 8050 on the address http://185.38.252.29 in order to make them accessible ?

Many thanks

Regards

NS

Hi all,

The policy have been changed and the ports 8010, 8020, 8030, 8040, 8050 are open on the IP 185.38.252.29 ( TCP and UDP ).

Could you please give us feedback , so to close the ticket ?

Thanks,

BR
Trento Node team

The issue has been emailed:

• Time sent: 13/Jun/16 4:08 PM
• To: nspada@gilrma.fr
• with subject: *(HELP-6748) [Fiware-lab-help] Inseat - problem on filab *
  

Hi all,

The policy have been changed and the ports 8010, 8020, 8030, 8040, 8050 are open on the IP 185.38.252.29 ( TCP and UDP ).

Could you please give us feedback , so to close the ticket ?

Thanks,

BR
Trento Node team

Comment by nspada@gilrma.fr :

Hi,

Thank you, everything is fine on your side now.

Regards,

Nicola SPADA 

----Message d'origine----
De : Help-Desk jira-help-desk@fi-ware.org
Envoyé : lundi 13 juin 2016 16:09
À : Nicola SPADA
Objet : [FIWARE-JIRA] (HELP-6748) [Fiware-lab-help] Inseat - problem on filab

Hi all,

The policy have been changed and the ports 8010, 8020, 8030, 8040, 8050 are open on the IP 185.38.252.29 ( TCP and UDP ).

Could you please give us feedback , so to close the ticket ?

Thanks,

BR
Trento Node team

-------------------------------------------------------------------------------
Trento Node Team created HELP-6748:
--------------------------------------

Summary: [Fiware-lab-help] Inseat - problem on filab
Key: HELP-6748
URL: https://jira.fiware.org/browse/HELP-6748
Project: Help-Desk
Issue Type: extRequest
Components: FIWARE-LAB-HELP
Reporter: FW External User
Assignee: Trento Node Team
Priority: Critical

Hello,

For the Inseat project we are using 2 virtual machines:

• wildspitze lan ip 192.168.111.16 - public ip 185.38.252.29

• grossglockner lan ip 192.168.111.174

We access to both virtual machines via 1 public ip and using NAT for access to grossglockner services

One week ago we have completed development of application and deployed all components into these virtual machines.

Yesterday moorning services that are installed on grossglockner weren't reachable and the grssglockner is not reachable from weildspitze using ssh.

We have tried to restart both virtual machines and check al configuratins in wildspitze (grossglcokner is not reachable)

Could you please check the cloud setup in order to restore correct behavior of the virtual machines

Thanks and Regards

Nicola SPADA

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.

Hi all,

The user provided positive feedback and the ticket will be closed.

Regards,
Trento Node team