Enterprise Cloud Knowledge Center
Close the Menu
Home > Enterprise Cloud 2.0 Support Information > FAQ - Enterprise Cloud 2.0 > After creating a new tenant, an error occurred when creating a logical network.

FAQ

After creating a new tenant, an error occurred when creating a logical network.

(:Last updated）

In some cases, you may receive an error for certain configuration changes, such as Network creation, directly following the creation of a new Tenant. If this occurs, simply retry the configuration change after 5 minutes.

Reference：Tutorial - How to Create & Connect Networks

Is this page helpful?

Yes No
  • ECL2.0
    •  
  • Logical Network
    •  

Related Pages

  • When I change DHCP function of Logical Network from disabled to enabled, is there any impact on existing resources?ECL2.0, Logical Network / Operation, Specification

    When DHCP is enabled, one IP address for logical port for setting (DHCP server port) is required. The lowest unused address in the IP address assignment pool will be automatically delivered.
    In addition, there is no impact on existing resources.

    DHCP (server address setting function) of Logical Network is a function to set the address to the server menu (Baremetal server / Virtual server).
    Unlike general DHCP, as it is a mechanism to pass address information as an indefinite lease based on information on port and subnet, we will set the same IP address every time.
    Even if this function is enabled, it is possible to assign an arbitrary IP address permanently.
    Please specify an arbitrary address by the address payout function on the port.
    Please refer to the following for details.
    Service Descriptions - Logical Network - (Reference) Address Assignof Logical Network

    Is this page helpful?

    Yes No
    Open in a new window
  • About the issue which subnet becomes error status when subnet of logical network editsECL2.0, Logical Network

    Issue

    If the following conditions are all satisfied on the logical network, the status of the subnet will be an error.
    ① When creating a logical network, disable the subnet address setting function (DHCP function)
    ② Edit the subnet in the state of ① and activate the address setting function (DHCP function)
    ③ Edit the subnet in the state of ② and change options such as DNS server function and NTP server function

    If you edit the resource connected to the subnet with subnet status error, the operation fails.

    Region

    JP1, JP2, JP3, JP4, JP5, DE1, UK1, SG1, US1

    Solution

    · If you want to change the subnet options (DNS server, NTP server, etc.) in the state of ②, please delete and re-create instead of editing the subnet
    · If you change the subnet option in the state of ② and the subnet becomes an error, please inquire with a ticket

    Open in a new window
  • About the issue which the DHCP server of the logical network announces an unintended cache (resolver) DNS server addressBaremetal Server, Common Function Gateway, ECL2.0, Logical Network, Virtual Server

    Overview of the Issue

    • The DHCP server of the logical network delivers an IP address (IP address of the DHCP server) that the customer does not intend as the IP address of the cache (resolver) DNS server.
    • If the OS of the virtual server instance or the bare metal server acquires the IP address (DHCP server IP address) that the customer does not intend as the IP address of the cache (resolver) DNS server by DHCP, the global name space name can be resolved.* Enterprise Cloud 2.0 does not offer cache (resolver) DNS server.

    Detail of the issue

    Region

    • JP3, JP4, JP5

    Menu

    • It occurs when both of the logical network and the server (virtual server or bare metal server) satisfy the following conditions.
    • Logical network
      • Case 1. Create from the Logical Network menu and enter the following items in the subnet
        • DHCP enabled: Checking
        • DNS server: You have not entered an IP address in the text box
      • Case 2. Common Functions Common Functions Created from Gateway Menu All logical networks for gateway
    • Server
      • Case 1. Create with virtual server menu, with the following settings
        • Interface: Connected to a logical network that meets the above conditions
        • OS: Obtained the IP address of the cache (resolver) DNS server by DHCP
      • Case 2. Bare metal server
        • Interface: Connected to a logical network that meets the above conditions
        • OS: Obtained the IP address of the cache (resolver) DNS server by DHCP

    Confirmation method

    • The method of checking whether the condition that this event meets is as follows.
    • Logical network
      • Subnet
        • Cloud Computing Control Panel> Network> Logical Network> Please press subnet name from subnet.
          • DHCP Enabled: Please confirm whether it is valid on "Subnet Details" screen
          • DNS Server: It may be applicable when DNS server is "None" on "Subnet Details" screen. In case of "None", it indicates whether the DNS server address has been delivered without entering the IP address in the DNS server, or 0.0.0.0 is entered to stop distributing the DNS server address.
    • Virtual Server
      • Interface
        • Please press the instance name from the cloud computing control panel> server> virtual server> instance and check on the "instance details" screen
      • OS
        • Windows Server 2012 R2 / Windows Server 2016: Network and Sharing Center> Changing adapter settings> "Interface name connected to logical network"> Properties> Internet Protocol Version 4 (TCP / IPv4) Please check on Internet Protocol Version 4 (TCP / IPv4) Properties screen
        • Execute the following command at Red Hat Enterprise Linux / CentOS: Shell and check the output.
          • nmcli connection show <interface name connected to the logical network>
    • Bare metal server
      • Interface
        • Cloud Computing Control Panel> Server> Please press the bare metal server name from the bare metal server and check on the "Bare Metal Server Details" screen.
      • OS
        • Windows Server 2012 R2: Network and Sharing Center> Changing Adapter Settings> "Logical (VLAN) Interface Connected to Logical Network"> Properties> Internet Protocol Version 4 (TCP / IPv4) Please check on the Properties of protocol version 4 (TCP / IPv4) screen
        • Execute the following command at Red Hat Enterprse Linux / CentOS: Shell and check the output
          • nmcli connection show <interface name connected to the logical network>

    Solution

    The solution is as follows.

    1. When it is necessary to acquire the IP address of the cache (resolver) DNS server by DHCP
      • Please perform the following setting in "Edit Subnet".
        • DNS Server: Enter the IP address of the cache (resolver) DNS server in the text box (* 1)
    2. When it is not necessary to acquire the IP address of the cache (resolver) DNS server by DHCP
      • Please perform the following setting in "Edit Subnet".
        • DNS Server: Check the "Disable DNS Server" check box. (* 2)

    * 1 We do not offer cache (resolver) DNS server in Enterprise Cloud 2.0. Therefore, please specify the IP address of your internal DNS server and the IP address of the cache DNS server provided by the customer's selected public DNS service.

    * 2 In the case of API, enter 0.0.0.0 in the DNS server section.

    Schedule

    We plan to change the setting of the logical network of existing customers and stop delivery of an unintended cache (resolver) DNS server address.

    If you need to take action before then, please take measures to deal with delivery / distribution of DNS server addresses referring to the above mentioned actions.

    Open in a new window
  • Does the number of logical networks that can be used for free include the logical network of common function GW?ECL2.0, Logical Network

    Logical networks are free up to 5 resources per tenant.
    Logical network for common function Gateway connection will also be counted as one of this free usage.

    (Reference) Service Description --Common Function Gateway

    Is this page helpful?

    Yes No
    Open in a new window
  • Is it possible to allocate IP address manually when DHCP is available?ECL2.0, Logical Network / Construction, Specification

    Even when DHCP is available, you can allocate IP address manually within IP address assignment pool.

    When DHCP is available and you do not specify IP address, IP address will be allocated from IP address assignment pool automatically.

    Is this page helpful?

    Yes No
    Open in a new window

Support Information

Enterprise Cloud 2.0

Enterprise Cloud 1.0

We appreciate your cooperation in improving the site

Did this FAQ be helpful? If you have any comments, please let us know.

Thank you

Your feedback has been received.

▲