5.5. Enterprise Cloud 2.0 Inter-Connectivity

Important

  • Customers already use Firewall(Brocade 5600 vRouter) in Enterprise Cloud 2.0 are able to use this menu.

  • NOTE: Customers who are not using Firewall(Brocade 5600 vRouter) menu is not able to use this menu since we already decided to stop sales of firewall(Brocade 5600 vRouter) in Enterprise Cloud 2.0.

5.5.1. Service Menu Overview

5.5.1.1. Service Menu Overview

  • The Enterprise Cloud 2.0 Inter-Connectivity service menu allows connectivities between Tenants.

  • Customers are able to connect the Firewall (Brocade 5600 vRouter) with another Tenant’s Logical Network within the same region, using the Interface.

../../_images/tenant_summary_jp.png

5.5.1.2. Menu Features

The Enterprise Cloud 2.0 Inter-Connectivity menu contains the following features and benefits.

  • Flexible Tenant Connectivity: Connect by mutual agreement between the Source Tenant and Destination Tenant. It is also possible to connect Tenants with differing names, and Tenants under differing contracts.

  • Abundant Gateway Functions: Abundance in Gateway functions by utilizing the services of the Firewall (Brocade 5600 vRouter).

  • Automatic Provisioning: Automatic provisioning utilizing SDN Technology.

5.5.1.3. Definition of Terms

  • Source Tenant: Tenant under contract with Firewall (brocade 5600 vRouter). Service application for Enterprise Cloud 2.0 Inter-Connectivity is put into effect.

  • Destination Tenant: Tenant under contract with Logical Network. Permission / Denial of service application for Enterprise Cloud 2.0 Inter-Connectivity is specified.

5.5.2. Available Functions

5.5.2.1. Overall Flow

../../_images/tenant_flow_jp.png

5.5.2.2. List of Functions

 

Functions

Implementation Tenant

Function Overview

1

Enterprise Cloud 2.0 Inter-Connectivity Service Application

Source Tenant

Customers are able to submit application requests for approval.

2

Cancel Enterprise Cloud 2.0 Inter-Connectivity Application

Source Tenant

Customers are able to cancel their request for approval application.

3

Authorize Enterprise Cloud 2.0 Inter-Connectivity

Destination Tenant

Customers are able to authorize application requests for approval.

4

Establish Enterprise Cloud 2.0 Inter-Connectivity

Source Tenant

Customers are able to establish Enterprise Cloud 2.0 Inter-Connectivity after authorization.

5

Terminate Enterprise Cloud 2.0 Inter-Connectivity

Source Tenant

Removal function is available.

6

Self-Management Function

Source Tenant
Destination Tenant

Customers are able to manage operations on the Customer Portal / API.

5.5.2.3. Description of Functions

Enterprise Cloud 2.0 Inter-Connectivity Service Application

  • Customers are able to submit application requests for approval for connectivities between Source Tenant and Enterprise Cloud 2.0.

  • The parameters for application requests for approval are as follows.

Categories

Parameter

Detail

Basic Information

Name

Customers are able to set the Name.

 

Description

Customers are able to set the description.

Source Tenant Information

Type of Interface

Please select firewall_interface.

 

Firewall

Customers are able to specify the Firewall for connectivity.

 

Interface

Customers are able to specify the Interface for connectivity.

 

IP Address

Customers are able to specify the IP Address for connectivity.

 

Virtual IP Address

(Optional) Customers are able to set the Virtual IP Address that uses VRRP for redundancy.

  VRID

(Optional) Customers are able to set the VRID that uses VRRP for redundancy.

Destination Tenant Information

Tenant ID

Customers are able to specify the ID of the Destination Tenant. Destination Tenants with the same name or differing names can each be specified individually.

 

Network ID

Customers are able to specify the ID of the Destination Logical Network.

Note

  • VRID, the IP Address for redundancy using VRRP, can only be configured at the start of Enterprise Cloud 2.0 Inter-Connectivity service. Please note that additions, deletion / editing of Enterprise Cloud 2.0 Inter-Connectivity will not be possible afterwards.

  • Please be aware not to create overlapping VRIDs within the same segment.

  • If the Destination Tenant does not approve / deny the request for approval , it will be automatically cancelled after the response deadline (30 Days) has passed.

Cancel Enterprise Cloud 2.0 Inter-Connectivity Application

  • The Source Tenant is able to cancel their request for approval.

Note

  • Only the Administrative User (user with contract management authority) can cancel requests for approval. This action cannot be completed by General Users.


Authorize Enterprise Cloud 2.0 Inter-Connectivity

  • The Destination Tenant is able to approve / deny the request for approval from the Source Tenant.

  • If multiple requests for approval are received, it is possible to approve / deny each request for approval individually.

Note

  • Only the Administrative User (user with contract management authority) can cancel requests for approval. This action cannot be completed by General Users.


Establish Enterprise Cloud 2.0 Inter-Connectivity

  • The Destination Tenant will be able to establish Enterprise Cloud 2.0 connectivites after authorization is given by the Source Tenant.

Note

  • Please note that the Firewall (Brocade 5600 vRoute) restarts at the time of execution.

  • If the Source Tenant does not begin the execution, actions already approved will be invalid once the approval expiration period (30 Days) has passed. If the Customer wants to continue, they must submit a request for approval again.

Terminate Enterprise Cloud 2.0 Inter-Connectivity

  • The Delete function is available to the Source Tenant.

  • It is not possible to disconnect from the Destination Tenant. Even when the Destination Tenant performs ‘Delete Tenant’ action, the Enterprise Cloud 2.0 Inter-Connectivity resources belonging to the Source Tenant will not be automatically deleted.

Note

  • Please note that the Firewall (Brocade 5600 vRoute) restarts at the time of execution.

Self-Management Function

  • The following functions are available for managing Enterprise Cloud 2.0 Inter-Connectivity via the Customer Portal / API.

Operations

Implementation Tenant

Functions

Display list of Enterprise Cloud 2.0 Inter-Connectivity connections

Source Tenant
Destination Tenant
Customers are able to verify the list of Enterprise Cloud 2.0 Inter-Connectivity connections. Customer is able to verify the status of the next request for approval.
  • registered: The request for approval has been successfully registered.

  • approved: The Destination Tenant has approved the request for approval.

  • denied: The Destination Tenant has denied the request for approval.

  • canceled: The Source Tenant has withdrawn the request for approval.

  • expired: The request for approval or approved request has expired.

5.5.3. Service Menu

5.5.3.1. Service List

There will be no service plans available for Enterprise Cloud 2.0 Inter-Connectivity.

5.5.3.2. Subscription Methods

The different Subscription Types are as follows.

Subscription Type

Subscription Methods

Offered Date

Establishment of Enterprise Cloud 2.0 Connectivity

Subscribe via Customer Portal / API

Instant Availability

Terminate Enterprise Cloud 2.0 Inter-Connectivity

Subscribe via Customer Portal / API

Instant Availability

Note

  • Before removing a tenant from Destination Tenants, please cancel the Enterprise Cloud 2.0 connectivity at the Source Tenant beforehand.


5.5.3.3. Important Notes of Subscription

5.5.4. Terms And Conditions

5.5.4.1. Conditions of Usage with Other Menus

  • In order to use this function, it is necessary to contract with Firewall (Brocade 5600 vRouter) beforehand.

  • This service menu can be combined with all other service menus. Connections with the Logical Network is only possible through connectivities to the Data Plane.

5.5.5. Pricing

5.5.5.1. Initial Fee

  • There is no initial fee with this service.

5.5.5.2. Monthly Fees

  • There is no monthly fees with this service.

5.5.6. Quality of Service

5.5.6.1. Coverage of Support

  • Customers should note that functions enlisted in Chapter 2 of this Service Description (2.1 List of Available Functions) are within the coverage of support.

5.5.6.2. Operation

  • Quality of this menu’s Operations corresponds to that of standardized regulations which NTTCom defines thereof in details.

5.5.6.3. SLA

  • The SLA of this menu is based on the standardized SLA for Enterprise Cloud 2.0.

5.5.7. Notes

  • By establishing the Enterprise Cloud 2.0 Inter-connectivity, communications between all of the connected Tenants will be possible. Please set filtering settings (eg. using the Firewall) to ensure only necessary communications are transmitted.

    • For the Source Tenant, please configure only the necessary transmissions (Firewall (Brocade 5600 vRouter) etc.) needed for Enterprise Cloud 2.0 Inter-Connectivity.

    • For the Source Tenant, it is recommended to have a dedicated Logical Network for Enterprise Cloud 2.0 Inter-Connectivity, and connect to other resources via Firewall (Brocade 5600 vRouter) or Managed Firewall. This allows Customers to send transmissions from the Source Tenant based on the policies of the Destination Tenant.

  • Please do not connect with Logical Networks (eg. “common_function_gw_access_ (unique ID)” or connectable NATs) that Enterprise Cloud 2.0 Inter-Connectivity is able to connect to through the Common Function Gateway. Once connected, the services (Backup, NPT etc.) that are available via the Common Function Gateway will become available to other Tenants.

  • When using Enterprise Cloud 2.0 Inter-Connectivity, failure notifications are available to handle failure reports from Connection Local Tenants or customers of the Connection Destination Tenant. Information regarding the failure of the Connection partner (Opposite Tenant) will be informed for early identification and recovery of the point of failure. At the same time, failure information of the Connection Local Tenant’s Firewall (Brocade 5600 vRouter) etc, may be notified to the other party (Opposite Tenant) at the time of failure.