Logical Network

About This Menu

About This Menu

  • This menu provides L2 Network (hereafter called as Logical Network) that Customers can use in their tenants.

  • The Logical Network can be connected with each resource that Customers have in their tenants. By this, Customers can establish L2 connectivity between any resources and realize flexible network design within their tenant.

  • Operations such as adding/modifying/deleting Logical Network are automated, so the commands via Customer Portal or API of Enterprise Cloud 2.0 will reflect instantly to Customers’ Tenants.

Features

Following are the features of “Logical Network” in Enterprise Cloud 2.0.

  • Versatility that enables flexible network design

    • Logical Network excludes fixed network architectures proprietary specified by providers such as existing cloud services. As it is free to connect or not to connect with each resource provided with this service, Customers can migrate the architectures as are configured in the on premises environments today or realize complex network architectures being investigated by Customers.

  • Automated Provisioning with SDN technology

    • Customers are able to utilize on-demand network architectures with automated provisioning by the latest SDN technology to keep up their business agility. This menu is optimized for the cloud environment due to its on-demand function.

Available Functions

List of Functions

Overview

Functions available in the Logical Network menu are as follows.
機能概要

No.

Function

Overview

1
Network Function
(Logical Network)

It provides L2 network and L2 connectivity between any resources within the tenant.

2
Common address management function
(Subnet)

Address information commonly used in a Logical Network (IP address block, default gateway, DNS server, NTP server, etc.) can be managed.

3
Resource address management function
(port)

Provides the function of managing individual resource settings (IP address, MAC address, etc.) connected to the logical network.

4
Self-Management Function
(Logical Network)

Customers are provided with functions to manage a logical network via Customer Portal and API.

5
Self-Management Function
(Subnet)

Customers are provided with functions to manage subnet via Customer Portal / API.

6
Self-Management Function
(Port)

Customers are provided with functions to manage ports via Customer Portal / API.

Communications overview

Communications through the Logical Network menu are realized with the following steps.
通信概要

No.

Communications step

Overview

1

Create address table

  • The logical network is a menu that provides the L2 network function. In order to maintain communication even after live migration of Virtual Server and HA (High Availability) function is activated, communication is realized by using IP address information.

  • An address table is created, based on the system registration information (“common address management function (subnet)” and “resource address management function (port)”).

  • With a virtual menu (virtual server, Managed Firewall, load balancer (NetScaler VPX), etc.), information of the IP address specified at the time of connections from a resource to a logical network is registered in the system.

2

Address learning

  • With a physical menu (such menu which does not use a virtual server foundation as baremetal server, collocation connection, Enterprise Cloud 1.0 connection), communications are performed by automatically learning a MAC address, based on ARP from a resource. However, the address is not automatically registered in the system.

  • Design so that an IP address of a physical menu will be chosen from those not belonging to the IP address assignment pool, or manually register the currently used static IP address in the “resource address management function (port)”.

  • With a virtual menu, addresses are not automatically learned. Therefore, when intending communications with an IP address other than the one specified at the time of connections, register the IP address in the “resource address management function (port)”.

3

Start of communications

Transferring packets in accordance with the address table

Function details

1.Network Function

  • Resource that Customers have in their tenants can be connected each other in L2.

  • For restrictions on this function, see: ref: restriction.

  • Logical Network has following two planes depending on their use.

プレーン種別

Plane Type

Purpose

Connectable resources

Data Plane

  • Logical Network used for data communication.

All except File Storage (Premium)

Storage Plane

  • The plane dedicated for the connections between storages and servers.

  • This is provided with the infrastructure optimized for the transmission between storages and servers, and does not get effected from any traffic of data transmission.

Baremetal Server / File Storage (Premium) / Block Storage (Provisioned I/O Performance)
*Virtual Servers cannot be connected.

2.Address Management function (Subnet)

  • Address information commonly used in a Logical Network (IP address block, default gateway, DNS server, NTP server, etc.) can be managed.

  • For restrictions on this function, see: ref: restriction.

  • Parameters that can be specified are as follows.

Function Types

Conditions

Details

Network Address

Mandatory

  • Set a network address.

  • An address range that includes following address ranges cannot be registered.

    • link local address (169.254.0.0/16)
    • ISP shared address (100.64.0.0/10)
  • The range of the mask length that can be specified is /30 to /2.

Gateway IP

Optional

  • Set a default gateway for distribution with DHCP.

  • Select and specify an arbitrary IP address from the network addresses.

  • If not setting the default gateway, select “No gateway”.

DHCP enabling (Address setting function)

Optional
Selecting enabling is recommended.
  • Specify whether to enable or disable the function which automatically sets addresses to resources.

  • With the function enabled, one IP address for the address setting server (DHCP server) is used by the service-side.

  • Up to one subnet is allowed to enable DHCP in one Logical Network.

  • If multiple subnets are created in one Logical Network and DHCP of multiple subnets are enabled, they will be outside of our support.

  • When using VRRP, enable the DHCP function (address setting function) of the logical network to be connected. With the DHCP function disabled, an ARP request is sent from the network of Service Provider, with source address 0.0.0.0. It has been confirmed that in this case an ARP reply is not returned from such products provided by Service Provider as a load balancer and Managed FW/UTM: redundancy by means of VRRP can be affected and communications can be disconnected at the time of switching.

IP Address Pool

Optional

  • This is a function for specifying an IP address pool to be used for auto IP address assignment.

  • If having omitted to specify an IP address at the time of resource connection, an IP address is automatically assigned from this pool.

  • To alter, deletion and re-generation of a subnet is required.

DNS Server

Optional

  • The address of the DNS server for distribution with DHCP can be specified.

    • How to specify the DNS server address in the customer portal

      • Check “DIsable DNS server”... DNS server address is not delivered

      • No check in “Disable DNS server” · · · Specified address is delivered as DNS server address.

      • If there is no ‘Disable DNS server’ checkbox, please specify the address like API.

    • How to specify DNS server address in API

      • Blank or specifying address 0.0.0.0

      • Specifying arbitrary address · · · Specified address is advertised as DNS server address.

NTP Server

Optional

  • The address of the NTP server for distribution with DHCP can be specified.

Setting additional route

Optional

  • A static route for distribution with DHCP can be specified.


(Reference) Address setting function (DHCP)

  • With the address setting function (DHCP), addresses are set to resources using the DHCP protocol, based on system registration information (common address management function (subnet) and resource address management function (port)).

  • Unlike general DHCP, address information is passed as indefinite lease. The same address is to be set every time.

  • Even with this function enabled, an arbitrary IP address can be assigned as a fixed one. When connecting with a resource, specify an arbitrary address using the address assignment function of the port.

  • With this function enabled, one IP address for the address setting logic port (DHCP server port) is used by the service-side. The smallest number among the addresses not used for the “resource address management function (port)”, in the IP address assignment pool is assigned automatically.

  • Please note that addresses secured once can not be used with customer resources even if you disable the address setting function (DHCP). In order to use secured addresses on customer resources, it is necessary to delete common address management function (subnet), and it is necessary to disconnect connected resources.

  • Up to one subnet is allowed to enable DHCP in one Logical Network. If multiple subnets are created for one logical network and the DHCPs of multiple subnets are enabled, it is not known from which DHCP server an address will be assigned, and thus support is not provided.

3.Resource Address Management Function (Port)

  • Provides the function of managing individual resource settings (IP address, MAC address, etc.) connected to the logical network.

  • For restrictions on this function, see: ref: restriction.

  • Parameters that can be specified are as follows.

Types

Details

Static IP address

  • IP addresses for use by the resources can be registered.

  • Manual delivery (specify any address) or automatic delivery can be selected.

    • Manual assignment: Customers will specify any unused IP address within the network address.

    • Auto assignment: The smallest number among the addresses not registered for the “resource address management function (port)”, in the IP address assignment pool is assigned automatically.

MAC Address

  • MAC addresses for use by resources can be registered.

  • The standard is automatic allocation.

Allowed Address Pair
(Allowed Address Pair)
  • Virtual IP address and virtual MAC address used in redundancy protocol such as VRRP can be registered.

  • Please note that if this setting is not implemented, communication to virtual IP address which is used in redundancy protocol is not possible.

  • Register the same Virtual IP address and the same virtual MAC address for each of the multiple ports where Customers want to operate the redundancy protocol.

  • Only manual assignment (specify any address) is possible.

  • Redundancy scheme to use the same IP address by different MAC addresses will not work.

Segment Type

  • With Baremetal Servers, VLAN type of the segment between port and resource can be selected from the following two types.

    • flat type: Connects between the port of a logical network and a resource using untag VLAN.

    • vlan type: Connects between the port of a logical network and a resource using tag VLAN.

  • For details, please refer to the Service Description of Baremetal Server Menu.


(Reference) Address Assignof Logical Network

When a port is created, an IP address for a resource to be connected with is assigned. Manual assignment and auto assignment can be selected.

アドレス割当

Address Assign Types

Details

Manual

Customers will specify any unused IP address within the network address.

Automatic

The smallest number among the addresses not registered for the “resource address management function (port)”, in the IP address assignment pool is assigned automatically.


(Reference) Specification details for each menu

  • Operations for each menu are described in the table below. For details about the individual menus, refer to the service instruction manuals for the respective menus.

  • Address settings with the address setting function (DHCP) are made only when address information has been registered in the system registration information (common address management function (subnet) and resource address management function (port)) and also when the menu-side address setting has been made so as to enable DHCP acquisition. Match the IP addresses to be used for resources with IP addresses registered in the system.

  • For virtual network appliances (Managed Firewall, Managed UTM, load balancer (NetScaler VPX), firewall (Brocade 5600 vRouter), etc.), the ports are managed by Service Provider and thus cannot be checked with customer tenants. Check information such as IP addresses through individual menu screens.

Connection menu side

 

Logical network side

   

Menu Name

Set Address

“Static IP address” registration(*1)

“Allowed address pair” registration(*1)

Route learning regarding an address not registered

  • Virtual Server

DHCP acquisition or fixed setting

Registration of an address to be specified at the time of menu connections For addresses other than those above, manual registration is to be performed.

Registration is needed. (Redundancy with addresses not registered do not work.)(*3)

Learning is not performed. (Non-learning unicast communications result and restriction occurs.)

  • Baremetal Server

DHCP acquisition or fixed setting

Registration of an address to be specified at the time of menu connections For addresses other than those above, manual registration is to be performed.

Registration is not needed.

Learning is performed. (Unicast communications)

  • Block Storage (Provisioned I/O Performance)

  • FileStorage(Premium)

  • File Storage(Standard)

  • Internet Connectivity

  • VPN Connectivity

  • Amazon Web Services Inter-Connectivity

  • DC Inter-Connectivity

Fixing only

Registration of an address to be specified at the time of menu connections For addresses other than those above, setting is not possible.

Registration is not needed.

Learning is performed. (Unicast communications)

  • Managed Firewall
  • Managed UTM
  • Managed WAF
  • Firewall (Brocade 5600 vRouter)

  • Load Balancer(NetScaler VPX)

Fixing only

Registration of an address to be specified at the time of menu connections For addresses other than those above, setting is not possible.

Registration is needed. (Redundancy with addresses not registered do not work.)(*4)

Learning is not performed. (Non-learning unicast communications result and restriction occurs.)

  • Colocation Inter-Connectivity (CIC)

  • Enterprise Cloud Inter-Connectivity (EIC)

No IP addressed due to the L2 menu (*2)

No IP addressed due to the L2 menu (*2)

Registration is not needed.

Learning is performed. (Unicast communications)

Note

  • (*1) Registration in the resource address management function (port) is performed.

  • (*2) If intending to make address settings with the DHCP function, for customer resources of the L2 menu target, it is necessary to make DHCP settings for the customer resources and register static IP addresses in the resource address management function (port).

  • (*3) Registration of “allowed address pair” with the virtual server menu needs to be performed through edition of a port created at the time of logical network connections.

  • (*4) Registration of “allowed address pair” with the virtual network appliance menu needs to be performed through portal/API of each menu.


4.Self-Management Function (Logical Network)

As the self-management functions regarding the network functions (logical network), the following operations are available.

Operations

Operation Details

Reference to logical network

View details of subscribed Logical Network.

Create logical network

Create a new contract of Logical Network.

Edit logical network

Modify settings of subscribed Logical Network.

Delete Logical Network

Delete subscribed Logical Network.


** Reference to logical network **

Customers can view the details of subscribed Logical Network via Customer Portal / API.

Available Information

Details

ID

Customers can check Logical Network IDs added by system.

Name

Customers can view the name of a Logical Network which they specified.

Description

Customers can view specified description of Logical Network.

Plane

Customers can check Plane types (Data Plane/ Storage Plane) of Logical Network.

Management Status

Customers can view validity/invalidity status of Logical Network. Invalid Logical Network cannot be utilized for transmission.

Status

Customers can view the operation status for Logical Network.

Subnet

Customers can view Subnets assigned to Logical Network.

Tag

Customers can view tags set up to Logical Network. These tags can be utilized to specify conditions via Customer Portal / API.

** Create logical network **

Customers can create new Logical Network by operations via Customer Portal / API. Following parameters can be specified.

Configurable Information

Details

Name

Customers can set an arbitrary name to a Logical Network.

Description

Customers can set any string for the description of Logical Network.

Plane

Customers can specify Plane types (Data Plane/ Storage Plane) of Logical Network

Management Status

Customers can set up validity/invalidity status of Logical Network. Invalid Logical Network cannot be utilized for transmission.

Tag

Customers can set tags to Logical Network. These tags can be utilized to specify conditions via Customer Portal / API.


** Edit logical network **

Customers can change settings of subscribed Logical Network setting via Customer Portal / API.
Following are details of parameters Customers can modify:

Configurable Information

Details

Name

Customers can set an arbitrary name to a Logical Network.

Description

Customers can set any string for the description of Logical Network.

Management Status

Customers can set up validity/invalidity status of Logical Network. Invalid Logical Network cannot be utilized for transmission.

Tag

Customers can set tags to Logical Network. These tags can be utilized to specify conditions via Customer Portal / API.


Delete Logical Network

  • Customers can delete subscribed Logical Network via Customer Portal / API.

  • Customers can delete Logical Network when there is no Subnet that belongs to it.


5.Self-Management Function (Subnet)

As the self-management functions regarding the resource address management function (subnet), the following operations are available.

Operations

Operation Details

View Subnet

Customer can view the Subnet details that are registered on Logical Network.

Create Subnet

Customers can register Subnet settings such as IPv4 address block on Logical Network.

Modify Subnet

Customers can change Subnet settings on Logical Network that they have registered.

Delete Subnet

Customers can delete Subnet settings from Logical Networks that they have registered.


View Subnet Information

Customers can view registered information of Subnet.
Following are the details.

Available Informations

Details

Name

View Friendly Name Customers set to Subnet

ID

View Subnet ID

Description

View Description Customers set to Subnet

Tenant ID

View Tenant ID where Subnet exists.

Logical Network ID

View Logical Network ID where the the Subnet is assigned.

CIDR (network address)

View network addresses Customers set to Subnets.

IP Address Pool

View IPv4 address range as target of automatic assign to each resource.
It is a range of IP address automatically assigned if IP address specification is omitted when each resource is connected to Logical Network.

Gateway IP

It is allowed to view the IPv4 address of the default gateway, automatically assigned to resources with the DHCP function.

Validity / Invalidity of DHCP

It is allowed to check whether the address setting function (DHCP) of the subnet has been enabled or disabled.

DNS Server

It is allowed to view the IPv4 address of a DNS server, automatically assigned to resources with the DHCP function.

Setting additional route

It is allowed to view the IPv4 address of a static route, automatically assigned to resources with the DHCP function.

NTP Server

It is allowed to view the IPv4 address of an NTP server, automatically assigned to resources with the DHCP function.

Tag

View tags set to Subnet.


Create Subnet

Customers can register Subnet to their existing Logical Network.
Customers can register Subnet to their existing Logical Network.

Configurable Information

Details

Name

Set a Name of Subnet

Description

Set any string for the description of Subnet

Network Address

Set network address of Subnet

Validity / Invalidity of DHCP

Specify whether to enable or disable the address setting function (DHCP) of the subnet.

IP Address Pool

Set IPv4 address range as target of automatic assigned to each resource.
It is a range of IP address automatically assigned if IP address specification is omitted when each resource is connected to Logical Network.

Gateway IP

Set the IPv4 address of the default gateway, to be automatically assigned to resources with the DHCP function.

DNS Server

You can edit the IPv4 address of the DNS server that automatically pays for each resource with the DHCP function. Please specify it in the following form.

  • How to specify the DNS server address in the customer portal

    • Check “DIsable DNS server”... DNS server address is not delivered

    • No check in “Disable DNS server” · · · Specified address is delivered as DNS server address.

    • If there is no ‘Disable DNS server’ checkbox, please specify the address like API.

  • How to specify DNS server address in API

    • Blank or specifying address 0.0.0.0

    • Specifying arbitrary address · · · Specified address is advertised as DNS server address.

Setting additional route

Set the IPv4 address of a static route, to be automatically assigned to resources with the DHCP function.

NTP Server

Set the IPv4 address of an NTP server, to be automatically assigned to resources with the DHCP function.

Tag

Set tags set to Subnet.


Modify Subnet

Customers can modify Subnet settings assigned to Logical Network.

Configurable Information

Details

Name

Modify the Name of Subnet

Gateway IP

Edit the IPv4 address of the default gateway, to be automatically assigned to resources with the DHCP function.

Validity / Invalidity of DHCP

Re-specify whether to enable or disable the address setting function (DHCP) of the subnet.

DNS Server

You can edit the IPv4 address of the DNS server that automatically pays for each resource with the DHCP function. Please specify it in the following form.

  • How to specify the DNS server address in the customer portal

    • Check “DIsable DNS server”... DNS server address is not delivered

    • No check in “Disable DNS server” · · · Specified address is delivered as DNS server address.

    • If there is no ‘Disable DNS server’ checkbox, please specify the address like API.

  • How to specify DNS server address in API

    • Blank or specifying address 0.0.0.0

    • Specifying arbitrary address · · · Specified address is advertised as DNS server address.

Additional Route

Edit the IPv4 address of a static route, to be automatically assigned to resources with the DHCP function.

Description of Subnet

Modify any string for the description of Subnet

Subnet Tag

Modify tags set to Subnet.


Delete Subnet

  • Customers can delete Subnet settings assigned to Logical Network.

  • Customers can delete Subnet only in case no Ports belongs to it. (i.e. in case all the Ports are deleted from Subnet)


6.Self-Management Function (Port)

As the self-management functions regarding the resource address management function (port), the following operations are available.
Generation and deletion of ports are to be performed at the menu-side of a connection source.

Operations

Operation Details

View Port

View additional information of Port added to Logical Network

Edit Port

Modify Port added to Logical Network

Delete Port

Delete Ports of Logical Network


View Port

View information about Port of Logical Network. Following are parameters Customers can view:

Available Informations

Details

Name

View Friendly Name of Ports.

ID

View Port ID.

Description

View any strings Customers set to Port.

Tenant ID

View Tenant ID where Port exists.

Logical Network

View Logical Network where the Port belongs.

MAC Address

View MAC address of Port.

Segment ID

View VLAN ID, in case VLAN segment type is “tagged”.

Segment Type

View tag / untag of VLAN connecting the Port and resources.

Status

View the running status of Port operation.

Function lock by the service-side

View whether the Port is managed by service-side or not.

Subnet ID

Display the subnet ID where the Port belongs.

IP Address

Display IPv4 address which is assigned to Port.

Allowed Address Pair
(IP address)

In addition to MAC address / IP address assigned to a Port, multiple IP address pairs (combination of MAC address and IP address) can be assigned to the same port. View the IP address of the IP address pair set up additionally.

Allowed Address Pair
(MAC address)

In addition to MAC address / IP address assigned to a Port, multiple IP address pairs (combination of MAC address and IP address) can be assigned to the same port. View the MAC address of the IP address pair set up additionally.

Device Owner

View Resource information.

DeviceID

View Resource ID.

Tag

View tags set to Ports. These tags can be utilized to specify conditions via Cutomer Portal / API.


Edit Port

Customers can modify Port of Logical Network. Following are parameters they can modify.

Available Parameters

Details

Name

Modify Friendly Name of Ports.

Description

Modify any strings Customers set to Port.

Tag

Modify tags set to Ports. These tags can be utilized to specify conditions via Cutomer Portal / API.

Static IP address

IP address to be assigned to Port can be added.

Allowed Address Pair

Allowed address pair to be assigned to Port can be added or deleted.


Menu

Menu / Plan

There is no plan in Logical Network.

Subscription Types and Methods

Customers who have contracted this service are eligible for subscription of Logical Network.
Following are subscription types. Prices change, based on the subscriptions types below.

Subscription Type

Subscription Method

Offered Date

Add New Logical Network

Customers’ operation via Customer Portal/API

Instant Offering

Delete Logical Network

Customers’ operation via Customer Portal/API

Instant Offering

Important Notes of Subscription

The following are the maximum/minimum numbers per Tenant, and a sales unit of Logical Network.
 

Uppermost Maximum

Lowermost Minimum

Unit for Sale

Logical Network

64 0 1

Subnet

128 0 1

Port

2048 0 1

Pricing

Initial Fee

There is no initial fee.

Monthly Fee

Monthly fee is applied for this menu
Every monthly fee consists with monthly capped max. metered bill.

Free of Charge Subscription

This menu provides Customers free of charge equivalent to five of Logical Networks per Tenant.
The Charge of maximum five Logical Networks (Maximum monthly charge) will be deducted from Customers’ overall charge of Logcal Network.

Note

※The following equation will be used to calculate the charge. (Monthly overall charge of Logical Network) = (Monthly charge of Logical Network 1) + (Monthly charge of Logical Network 2)...+ (Monthly charge of Logical Network n) - (Maximum monthly charge of Logical Network) × 5


Quality of Service

Support Coverage

Functions provided with this menu come within the support coverage.
Designing and configuring Customers’ network architectures utilizing Logical Network are not supported.

Operations

Qualities of this Menu’s Operation corresponds to the standard level of what this service requires. For details, refer to “Support” section in Service Description.

SLA

SLA on this menu has been established as a standard on Enterprise Cloud 2.0.

Restrictions

General

  • Following is restrictions for using this menu. Therefore please check this chapter.

  • Restrictions common to network menus (construction method of redundant configuration, NG configuration example, etc.) are described in Network common section <https://ecl.ntt.com/documents/service-descriptions/network-common> _ So please be sure to check.

  • For details of each menu connected to Logical Network, please refer to the Service Description of each menu.

Network Function(Logical Network)

  • Logical Network provides L2 Network in customer’s tenants. To access to outside of tenant, customer need to subscribe other menu which can connect to external tenant, such as Intenet Gateway and Colocation Inter-Connectivity.

  • Stable communication can be expected because it is designed to increase the bandwidth of customer traffic flowing over the logical network.

  • Any frames that has IEEE 802.1D MAC Bridge Filtered MAC Group Addresses (01-80-C2-00-00-00 to 01-80-C2-00-00-0F) cannot go through the Logical Network. (For example, following protocols cannot go through. However, this shall not apply to the vendor-specific protocols that do not use this MAC addresses.

    • BPDU (STP/RSTP/MSTP, etc)

    • Pause Frame
    • LLDP
    • LACP (Link Aggregation Control Protocol)
  • Multicast/broadcast/unknown unicast transmission(BUM) is restricted to 10Mbps or less by Service Provider.

  • Maximum 9000 bytes of MTU size is available.

  • In Logical Network, communication is controlled by combination of IP address and MAC address.

  • Redundancy scheme to use the same IP address by different MAC addresses will not work.

Common address management function (subnet)

  • It is recommended to create one subnet per logical network.

  • With multiple subnets created for one logical network, forwarding communications in terms of different address ranges is possible. However, it is not effective for security because communications are transferred to the same L2 network (same VLAN).

  • To divide communications for s security reason, be sure to create multiple logical networks.

  • An address range that includes the following address range cannot be registered as network addresses.

    • link local address (169.254.0.0/16)
    • ISP shared address (100.64.0.0/10)
  • Range of the mask length that can be specified is /30–/2.

  • Set an address range wider than the current need so that resource expansion will be possible.

  • When using VRRP, please make DHCP function of the Logical Network to be connected “valid”. When the DHCP function is “invalid” , the ARP request is executed at the source address of 0.0.0.0 on ECL2.0 Network. In this case, it is confirmed that Load Balancer, Managed Firewall/UTM, etc. provided by Service Provider do not reply ARP and interruption of transmission may occur at the time of VRRP switching.

  • How to determine the address of the IP address allocation pool

    • If having set a gateway IP without specifying an IP address assignment pool, the value below is used as the pool address.

      • Network address (segment start), broadcast address (segment end), and values excluding the gateway IP

      • Example: If the network address is 192.168.0.0/24 and the gateway IP is 192.168.0.1, the IP address assignment pool will be 192.168.0.2 - 192.168.0.254.

    • If not having specified an IP address assignment pool and not having set a gateway IP, the value below is used as the pool address.

      • Network address (segment start), broadcast address (segment end), and values excluding the 2nd address counted from the segment start.

      • Example: If the network address is 192.168.0.0/24 and the gateway IP is not specified, IP address assignment pool is 192.168.0.2-192.168.0.254.

  • Specify the DNS server address in the following form when creating / editing a logical network,

    • How to specify the DNS server address in the customer portal

      • Check “DIsable DNS server”... DNS server address is not delivered

      • No check in “Disable DNS server” · · · Specified address is delivered as DNS server address.

      • If there is no ‘Disable DNS server’ checkbox, please specify the address like API.

    • How to specify DNS server address in API

      • Blank or specifying address 0.0.0.0

      • Specifying arbitrary address · · · Specified address is advertised as DNS server address.

** Address setting function (DHCP) **

  • With the address setting function (DHCP), addresses are set to resources using the DHCP protocol, based on system registration information (common address management function (subnet) and resource address management function (port)).

  • Unlike general DHCP, address information is passed as indefinite lease. The same address is to be set every time.

  • Even with this function enabled, an arbitrary IP address can be assigned as a fixed one. When connecting with a resource, specify an arbitrary address using the address assignment function of the port.

  • With this function enabled, one IP address for the address setting logic port (DHCP server port) is used by the service-side. The smallest number among the addresses not used for the “resource address management function (port)”, in the IP address assignment pool is assigned automatically.

  • Please note that addresses secured once can not be used with customer resources even if you disable the address setting function (DHCP). In order to use secured addresses on customer resources, it is necessary to delete common address management function (subnet), and it is necessary to disconnect connected resources.

  • If you want to avoid allocating IP addresses that are not registered in “Resource Address Management Function (Port)”, you need to manually create the port and register the in-use IP address.

  • Up to one subnet is allowed to enable DHCP in one Logical Network. If multiple subnets are created for one logical network and the DHCPs of multiple subnets are enabled, it is not known from which DHCP server an address will be assigned, and thus support is not provided.

Resource address management function (port)

  • When auto IP address assignment is performed, the smallest number among the addresses not used as “static IP addresses” for the “resource address management function (port)”, in the IP address assignment pool is assigned automatically.

  • Operations of a virtual menu (virtual server, Managed Firewall, load balancer (NetScaler VPX), etc.)

    • An IP address specified at the time of connections from a resource to a logical network is registered in the “resource address management function (port)” for use.

    • When intending communications with an IP address within the same network address other than the IP address specified at the time of logical network connections, be sure to register the IP address in the “resource address management function (port)”. Because IP addresses are not automatically learned by a virtual menu, non-learning unicast communications result, possibly disabling communications.

    • If Customers want to use the same IP address for multiple ports for redundancy, register the same virtual IP address and the same virtual MAC address to [ Allowed Address Pair ] item of all the ports Customers want to make redundant. If this setting is not implemented, correct communication to virtual IP address is not possible.

  • Operations of a physical menu (such menu which does not use a virtual server foundation as baremetal server, collocation connection, Enterprise Cloud 1.0 connection)

    • Regarding also an address not registered, transfer as unicast communications is possible through auto MAC address learning based on ARP from a resource. However, auto registration in the “resource address management function (port)” is not performed.

    • Design so that an IP address of a “physical menu” or “allowed address pair” will be chosen from those not belonging to the IP address assignment pool, or manually register an address as a “static IP address” of the “resource address management function (port)”.

  • Operations of virtual network appliances (Managed Firewall, Managed UTM, load balancer (NetScaler VPX), firewall (Brocade 5600 vRouter), etc.)

    • The ports are managed by Service Provider and cannot be checked by customers. Check information such as IP addresses through individual menu screens.

    • In the case where Managed Firewall and Managed UTM have been applied for in terms of the HA configuration, virtual IP addresses to be used for VRRP redundancy are registered as “allowed address pair” of the “resource address management function (port)” but are not registered as “static IP addresses”. To exclude the addresses from auto address assignment, register them as “static IP addresses”.

    • With the load balancer (NetScaler VPX) and firewall (Brocade 5600 vRouter) menus, virtual IP addresses to be used for VRRP redundancy are registered as both “static IP addresses” and “allowed address pair” of the “resource address management function (port)” for use.

  • Redundancy setting

    • If Customers want to use the same IP address for multiple ports for redundancy, register the same virtual IP address and the same virtual MAC address to [ Allowed Address Pair ] item of all the ports Customers want to make redundant. If this setting is not implemented, correct communication to virtual IP address is not possible.

    • With the Managed Firewall and Managed UTM menus, settings for “allowed address pair” are made when the HA configuration is applied for.

    • With the load balancer (NetScaler VPX) and firewall (Brocade 5600 vRouter) menus, settings for “allowed address pair” are made when “registration of communication settings for VRRP” is performed.

    • Redundancy scheme to use the same IP address by different MAC addresses will not work.

    • In the “Allowed Address Pair” item, only one MAC address can be registered for the same IP address. If you register a different MAC address, it will be overwritten with the MAC address you registered later. Please note that communication addressed to the first registered MAC address can not be executed.

Cautions for connecting Baremtal server

  • A Baremetal Server has four physical NIC ports. With Logical Network, two ports are available for Data Plane connection and two ports for Storage Plane connection.

  • Physical NIC port for each Plane is housed in a different Network Interface Card, and physical NIC port is connected to a different peer switch.

  • Failure of physical NIC port / peer switch may occur. In that case, the connection point where a failure occurred will be disconnected.

  • Therefore, for each connection with Data Plane / Storage Plane, make redundant configuration to cope with physical NIC port failure and peer switch failure.

  • For details, please refer to the Service Description of Baremetal Server Menu.

Cautions for connecting Windows Server

  • When connecting to Windows Server, IP address may not be set due to conflict with DAD (Duplicate Address Detection) function of Windows OS. Please use it in the following setting.

    • DHCP function in Logical Network is enabled.

    • When it is necessary to disable the DHCP function of the logical network, please configure fixed IP address on the Windows OS and disable the DAD function. This workaround will minimize the frequency of this issue but cannot completely prevent it.

  • For details about this issue, refer to ‘FAQ <https://ecl.ntt.com/en/faq/2.0/virtual-server-windows-ip-assignment/>’_ .

Points to note for abolishment

  • Before deleting a network function (logical network), delete all common address management functions (subnet) and resource address management functions (port) which are connected with the network function (logical network) to be deleted.

  • Before deleting common address management functions (subnet), delete all resource address management functions (port) which are connected with the common address management functions (subnet) to be deleted.