Hello,
I understood the issue. Let me try to summarize:
1) The floating IPs related to the "federation-ext-net-*" are private so you cannot ping them because they are not routable on the Internet.
2) You cannot attach the floating IP related to the "federation-ext-net-" using the "node-int-net-" as your private network. So basically you don't have to use the federation-ext-net-*.

In order to associate a public IP to your VM, you should:
1) allocate a floating IP from the "public-ext-net-0*"
2) Create a VM attached to the "node-int-net-0*"
3) Associate the allocated floating IP to your VM. NOTE: Please make sure that the floating IP is correctly associated, if you receive errors on that, you cannot try the next step.
4) If you have enabled ICMP on security group you should ping your VM.

Try to follow that and let me know. If you still have issues we'll try to figure it out.

Regards,
Giuseppe

Comment by mariarenata.russo@eng.it :

Hello Giuseppe,

thank you for your indication.
The issue is solved and now my VM instance is running.

Best regards

Renata

----Messaggio originale----
Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: martedì 19 aprile 2016 15:18
A: Russo Maria Renata
Cc: Ponticiello Vincenzo
Oggetto: [FIWARE-JIRA] (HELP-6420) [Fiware-lab-help] FIWARE Lab Assistance

From FIWARE JIRA - Main Help Desk ----

-------------------------------------------------------------------------------
Comments:

Giuseppe Cossu - Today 3:17 PM
------------------
Hello,
I understood the issue. Let me try to summarize:
1) The floating IPs related to the "federation-ext-net-*" are private so you cannot ping them because they are not routable on the Internet.
2) You cannot attach the floating IP related to the "federation-ext-net-" using the "node-int-net-" as your private network. So basically you don't have to use the federation-ext-net-*.

In order to associate a public IP to your VM, you should:
1) allocate a floating IP from the "public-ext-net-0*"
2) Create a VM attached to the "node-int-net-0*"
3) Associate the allocated floating IP to your VM. NOTE: Please make sure that the floating IP is correctly associated, if you receive errors on that, you cannot try the next step.
4) If you have enabled ICMP on security group you should ping your VM.

Try to follow that and let me know. If you still have issues we'll try to figure it out.

Regards,
Giuseppe

------------------------
Issue id: HELP-6420
Description:
Hi,
I'm trying to create an Instance from https://cloud.lab.fiware.org/#nova/instances/.
I used images base_ububntu_14.04.
I generated from security tab a specific security group, keypair and floating ip using federation-ext-net-01.
I associated floating ip generated to my instance.
When I try to reach, by ping command, both ip (10.1.66.62 192.168.131.234) address associated to my instance I received "request timeout".

After I disassociated IP from my instance and I generate new one using public-ext-net-01
But when I associate this IP to my instance I received :
undefined. Cause: 400 Error
{"badRequest": {"message": "Unable to associate floating ip 130.206.120.136 to fixed ip 192.168.131.234 for instance 492d2b97-6f60-4659-b3f7-20ba98c6fcc4. Error: External network 51563cad-83a8-46fc-be47-9e9f3cea9ee8 is not reachable from subnet da4b671e-087c-4b15-b26c-36288f068fd9. Therefore, cannot associate Port 2161dfa4-b0a1-45a2-805f-2aacc02a668f with a Floating IP.", "code": 400}}

Furthermore, when I try to connect by ping command public-ext-net-01 ip address (130.206.120.136) associated to my instance I received I received "destination host unreachable".

Could you help me to resolve these issues.

Best Regard

Renata

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.