Dear Belen,

Apparently, taking into account your comments, you are working in Spain region. Usually, this message appears when you try to request a new public IP from the pool. Have you another IP allocated from the pool?

Fernando

Comment by bcanitrot@carsa.es :

Hola Fernando, buenas tardes.

Muchas gracias por su correo. No entiendo muy bien lo quiere decir… A ver si esto ayuda a situarnos:

• Trabajo en "Spain Region2".

• Sólo estoy haciendo uso de una IP ->

• Al seleccionarla -> clic sobre “Actions” -> imagen -> “Associate IP” -> Aparece el mensaje de error.

Gracias y saludos,

Belén Canitrot

----Mensaje original----
De: Help-Desk jira-help-desk@jira.fiware.org
Enviado el: lunes, 28 de agosto de 2017 9:24
Para: bcanitrot@carsa.es
Asunto: [FIWARE-JIRA] (HELP-12631) [Fiware-lab-help] Fiware Lab: problems in the process of allocating IP to Project

From FIWARE JIRA - Main Help Desk ----

-------------------------------------------------------------------------------

Comments:

Fernando Lopez - Today 10:23 AM

------------------

Dear Belen,

Apparently, taking into account your comments, you are working in Spain region. Usually, this message appears when you try to request a new public IP from the pool. Have you another IP allocated from the pool?

Fernando

------------------------

Issue id: HELP-12631

Description:

Hello, good afternoon.

I am a trial account user in Fiware Lab and I´m finding a few problems in the process “Allocate IP to Project”. Let me explain myself:

1. I´ve created my instance “SpagoBIbelen” (running), a Keypair “b1”, a Security Group Rule “b1” (and its Rules) -> Please see the screenshots below

2. When I try to allocate IP to Project, an error message it´s shown: “You exceeded the limit of floating IPs”, and there´s no instance or fixed address related to the IP Address -> Please see the screenshots below

3. Even so I went head and tried to Associate IP (Actions) but it did not work… -> Please see the screenshots below

{"badRequest": {"message": "Unable to associate floating ip 130.206.126.80 to fixed ip 192.168.134.204 for instance 700f5125-8773-476a-9d30-a13ae44ad224.

Error: External network 51563cad-83a8-46fc-be47-9e9f3cea9ee8 is not reachable from subnet da4b671e-087c-4b15-b26c-36288f068fd9.

Therefore, cannot associate Port 73646b3f-418f-4eae-96d8-77a61e144664 with a Floating IP.", "code": 400}}

I don´t know what´s going on. Could you please help me?

Thank you in advance.

Belen

The subnet da4b671e-087c-4b15-b26c-36288f068fd9 belongs to the network node-int-noinet-subnet-02 — This network (noinet = no Internet) is not connected to external networks. So, there is not way to associate a floating IP to that network.

Please, use any of the networks node-int-net-01 or node-int-net-01-dual (but not both of them if you don't know why) for your VMs.

Thank you.

Best regards,
José Ignacio