5.2. Enterprise Cloud 1.0 Inter-Connectivity (EIC)

5.2.1. About This Menu

5.2.1.1. Overview

The Enterprise Cloud 1.0 Inter-Connectivity menu allows connectivities between Logical Network (Data Plane) of Enterprise Cloud 2.0 and Server Segment of ECL1.0 which NTTCom specifies in the same Zone.
EIC enables Customers to utilize both resources of Enterprise Cloud 2.0 and Enterprise Cloud 1.0 as a hybrid.

5.2.1.2. Features

The Enterprise Cloud 1.0 Inter-Connectivity (EIC) menu contains the following features.

  • EIC allows connectivities between Logical Network (Data Plane) of Enterprise Cloud 2.0 and Server Segment of ECL1.0 which NTTCom specifies in the same Zone.

  • EIC provides Layer 2 Connectivity which enables Customers to connect within the same segment.

  • Customers can either add, delete the connectivity in between Logical Network of Enterprise Cloud 2.0 and server segment of Enterprise Cloud 1.0 via Customer Portal / API. (Customers are required to submit the service order form for initial subscription of this menu.)


5.2.2. Available Functions

5.2.2.1. List of Functions

There are mainly two functions in Enterprise Cloud 1.0 Inter-Connectivity menu.

Function

Overview

Layer 2 Connectivity

EIC connects Customers’ Logical Network of Enterprise Cloud 2.0 designated by NTT Com within the the same Zone and server segment of Enterprise Cloud 1.0.
About the provider data centers, please confirm that the service is provided in each region. <https://ecl.ntt.com/documents/service-descriptions/rsts/service_region_list.html>

EIC Self-Management

Customers are provided with self-management function to operate EIC via Customer Portal / API.


5.2.2.2. Description of Functions

Layer 2 Connectivity

EIC menu enables Customers to connect their devices in both Enterprise Cloud 2.0 and 1.0 through the specification as follows:

  • Layer 2

  • Point to Point

Customers can have logical connections with each and every Logical Network.

  • Up to 24 VLANs are available per mEIC link.

  • Technically, the connectivity is made by VLAN, but Customers do not have to designate any VLAN ID.


Enterprise Cloud1.0 Inter-Connectivity (EIC) Self-Management function

Enterprise Cloud 1.0 Inter-Connectivity (EIC) provides Self-Management function that allows customers to manage EIC via the Customer Portal / API.
Following are available self-management operations:

#

Operations

Operation Details

1

View the information of Enterprise Cloud 1.0 Inter-Connectivity(EIC).

Customers can view the subscribed EIC information.
In the event that Customers are new to this menu, they are initially required to fill in the service order form in writing and submit to NTT Com. After NTT Com provisions the EIC, they are able to view the information.
2

Add EIC

Customers can add the connection between Logical Network of Enterprise Cloud 2.0 and sever segment of Enterprise Cloud 1.0.
In the event that Customers are new to this menu, they are initially required to fill in the service order form in writing and submit to NTT Com. After NTT Com provisions the EIC, they are able to view the information.
3

Delete Enterprise Cloud1.0 Inter-Connectivity

Customers can terminate their existing connectivity.


View the information of Enterprise Cloud1.0 Inter-Connectivity(EIC)

Customers can check their existing EIC information through Customer Portal / API. Following is the information details that Customers can refer to:

Available Information

Details

mEIC name (Distinguished Name)

Customers can refer to the distinguished name for every physical connectivity assigned by the Customers themselves.
As this is filled in at the start-up phase of this menu, Customers are not allowed to change this during their subscription.

EIC name (Distinguished Name)

Customers can refer to the distinguished name toward each connectivity included in mEIC.

Logical Network

Customers can refer to the information of Logical Network connected to EIC.

VLAN ID

Customers can refer to the server segment information of Enterprise Cloud 1.0 connected to EIC.


Add EIC

Customers can create a new EIC via Customer Portal / API. Customers are requested to assign the following parameters when they add EIC:

Configurable Information

Details

mEIC name (Distinguished Name)

Customers are required to designate which Enterprise Cloud 1.0 environment they would like to connect when subscribing this menu.

EIC name (Distinguished Name)

Customers can designate the distinguished name toward each connectivity included in mEIC.

Logical Network

Customers can assign the Logical Network connected to EIC.

VLAN ID

Customers can assign server segment of Enterprise Cloud 1.0 connected to EIC.


Delete Enterprise Cloud1.0 Inter-Connectivity

Customers can terminate their existing EIC via Customer Portal / API. Customers are requested to assign the following parameters when they terminate EIC:

Configurable Information

Details

mEIC name (Distinguished Name)

Customers can assign which ECL1.0 Connectivity to be terminated.

EIC name (Distinguished Name)

Customers can assign which EIC identifier to be terminated.


5.2.3. Menu

5.2.3.1. Menu / Plan

Provides only one plan in EIC menu,

Connectivity Plan

Overview

Guaranteed Bandwidth

Connect ECL2.0 with ECL1.0.


5.2.3.2. Subscription Types and Methods

Customers, who subscribe Enterprise Cloud 2.0 and have their existing Enterprise Cloud 1.0 subscription in designated NTT Com data centers with the same customer name, can place an order for EIC menu. Following is the subscription types:

Type of Subscription

Subscription Method

Offered Date

Subscribe new EIC menu

Customers are required to ask NTT Com sales person in charge of Enterprise Cloud 1.0 to subscribe a new EIC.
NTT Com will accept the service order after we confirm Customers’ contract information of their Enterprise Cloud 1.0.

5 business days after NTT Com accepts service order (in the case of data centers in Japan).

Add Connectivity between Enterprise Cloud 2.0 Logical Network and Enterprise Cloud 1.0 server segment

Customers can add via Customer Portal / API.

Immediately available

Delete Connectivity between Enterprise Cloud 2.0 Logical Network and Enterprise Cloud 1.0 server segment

Customers can add via Customer Portal / API.

Immediately available

Terminate EIC menu

Customers are required to ask NTT Com sales person in charge of Enterprise Cloud 1.0 to terminate CIC.

5 business days after NTT Com accepts termination order (in the case of data centers in Japan).


5.2.3.3. Important Notes of Subscription

  • Following is the respective limits in subscribing EIC:

 

Uppermost Maximum

Lowermost Minimum

Unit for Sale

Enterprise Cloud 1.0 Inter-Connectivity (EIC)

1 0 1
  • The Unit for Sale and the Uppermost Maximum number of EIC is one per one Enterprise Cloud 1.0 subscription.

  • Customers are required to have a certain lead time for NTT Com to check Enterprise Cloud 1.0 subsciption after receiving the service order.

  • Customers are generally required to allow a spare lead time in waiting for the service to start up.

  • Customers cannot add or terminate multiple subscription (or operation) at the same time.

  • Customers are required to operate one by one.

5.2.4. Terms and Conditions

5.2.4.1. Conditions for Usage with Other Menus

  • Customers are advised that they are not allowed to utilize EIC and Colocation Inter-Connectivity (CIC) concurrently to one Logical Network. In the event that the Customers would like to connect Enterprise Cloud 2.0, 1.0 and their colocation on the same network segment, they need to bring both Enterprise Cloud 2.0 CIC and 1.0 CIC together within their colocation rack, and connect them inside it.

  • Customers are noted that CIC cannot connect with Logical Network (Storage Plane).


5.2.4.2. Minimum Use Period

  • There is no minimum usage period for Enterprise Cloud1.0 Inter-Connectivity(EIC).


5.2.5. Pricing

5.2.5.1. Initial Fee

This service does not require initial fee.


5.2.5.2. Monthly Fee

This service does not require monthly fee.


5.2.6. Quality of Service

5.2.6.1. Support Coverage

Functions provided with this menu come within the support coverage. Furthermore, Customers are noted here that network architecture in utilizing this service and respective settings details will be excluded from the standard support coverage.

5.2.6.2. Operations

Qualities of this Menu’s Operation corresponds to the standard level of what Enterprise Cloud 2.0 requires. As with details, Customers are required to refer to the following pages:

Items

Details

Operation Hours

24/7

Troubleshooting Actions for the Failures of Backbone Infrastructure

Backbone equipments are redundantly configured. However, service interruption will require approximately 60 seconds (designed value) for switch-over.

5.2.6.3. SLA

The SLA of this menu is based on the standardized SLA for Enterprise Cloud 2.0; for the details please refer to the following pages, Service Description v1.0: SLA

5.2.7. Restrictions

5.2.7.1. Restrictions in Transmissions and Interface Setting

  • User Interface Conditions

    • Layer 2 Broadcast, Layer 2 Multicast and Unkown Unicast will be discarded only when the values exceed to a certain level.

    • Frame size is 68 byte (tagged) at minimum, 1,522 bytes (tagged) at maximum.

    • IPv6 is not available with this service.


  • MAC Address Conditions

    • Following is the MAC addresses used by the Enterprise Cloud 1.0 infrastructure end. At the Customers’ end, they are required to use the MAC Address which does not get mixed up with the following MAC Addresses. Furthermore, Customers are noted that NTT Com may change the following MAC addresses.

        • MAC Addresses starting with 00-50-56 (VMware)

        • MAC Address starting with a2

        • MAC Address starting with 00-0b-fc-fe-1b

        • MAC Address starting with 00-00-0c-07-ac (HSRPv1)

        • 00-00-0c-9f-f0-00~00-00-0c-9f-ff-9f (HSRPv2)(※1)

        • 00-00-5e-00-01-00~00-00-5e-00-01-fb (VRRP)(※2)

Note

*1 Customers end is required to utilize 00-00-0c-9f-ff-a0 and later. *2 Customers end is required to utilize 00-00-5e-00-01-fc and later.

5.2.7.2. Terms and Conditions

  • The company name of both Enterprise Cloud 2.0 and Enterprise Cloud 1.0 contracts need to be the same.


5.2.7.3. Installation and Termination

  • With Regards to Customers’ Support for Transmission Test

    • During the initial opening, the communication’s confirmation between the customer’s equipment of ECL1.0 and ECL2.0 will be done at NTT Com.

    • NTT Com would like Customers to submit the order form with needed information as NTT Com will conduct ping test towards the Customers’ devices.