Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-2143

FIWARE.Request.Lab.Berlin.I cannot associate a public IP to a VM

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-LAB-HELP
    • Labels:
      None
    • HD-Node:
      Berlin

      Description

      nova add-floating-ip ddec8501-f261-4b14-8391-b565e1284bca 193.175.132.42
      ERROR: Error. Unable to associate floating ip (HTTP 400)

        Activity

        Hide
        BerlinSupportTeam Berlin Node Helpdesk added a comment -

        I assume your're working with the tenant 00000000000000000000000000000081, correct?
        For this tenant id, no vrouter is existing on the Berlin node.
        Without a vrouter you are not able to assign a floating IP to a VM. This is because we are using neutron instead of nova-network.
        If you create a new vrouter it seems to better to set first the gateway before attaching the tenant network.

        Show
        BerlinSupportTeam Berlin Node Helpdesk added a comment - I assume your're working with the tenant 00000000000000000000000000000081, correct? For this tenant id, no vrouter is existing on the Berlin node. Without a vrouter you are not able to assign a floating IP to a VM. This is because we are using neutron instead of nova-network. If you create a new vrouter it seems to better to set first the gateway before attaching the tenant network.
        Hide
        henar Henar Muñoz added a comment -

        mm I thought that the external network was asociated to a virtual router. If I create a virtual router, do I have permissions to add my network to the virtual router? I think this behaviour is a bit strange.
        Regards,
        Henar

        Show
        henar Henar Muñoz added a comment - mm I thought that the external network was asociated to a virtual router. If I create a virtual router, do I have permissions to add my network to the virtual router? I think this behaviour is a bit strange. Regards, Henar
        Hide
        BerlinSupportTeam Berlin Node Helpdesk added a comment -

        Please note that:

        – a VM must be attached to a private (tenant) network which is connected to a router (you need to create that router and network/subnet in your tenant).
        – The router's default gateway than can be set to either the "ext-net-public" or the "ext-net-federation" networks. After doing that you can associate a floating IP.from a public network.
        – Two firewalls are between public Internet and your VM then: one you can control by setting a security rule for your VM instance, the other one must be configured by the node. Please inform us about the ports you need to be open.

        Show
        BerlinSupportTeam Berlin Node Helpdesk added a comment - Please note that: – a VM must be attached to a private (tenant) network which is connected to a router (you need to create that router and network/subnet in your tenant). – The router's default gateway than can be set to either the "ext-net-public" or the "ext-net-federation" networks. After doing that you can associate a floating IP.from a public network. – Two firewalls are between public Internet and your VM then: one you can control by setting a security rule for your VM instance, the other one must be configured by the node. Please inform us about the ports you need to be open.
        Hide
        BerlinSupportTeam Berlin Node Helpdesk added a comment -

        I freed up 3 public IPs just a minute ago.

        Show
        BerlinSupportTeam Berlin Node Helpdesk added a comment - I freed up 3 public IPs just a minute ago.

          People

          • Assignee:
            BerlinSupportTeam Berlin Node Helpdesk
            Reporter:
            henar Henar Muñoz
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: