5.4. Google Cloud Platform Inter-Connectivity¶
5.4.1. Service Menu Overview¶
This provides a customer who contracted for Enterprise Cloud 2.0 (hereafter, ECL2.0) with a function for closed-network connections with the Google Cloud Platform(TM) (hereafter, GCP).
Using this menu allows stable closed-network connections and realizes a multi-cloud solution having ECL2.0 and GCP combined.
5.4.1.1. Service Menu Features¶
The Google Cloud Platform Inter-Connectivity menu has the following features:
Secure connections
The GCP and ECL2.0 are directly connected through the network of NTTCom to provide closed-network connections separated from the Internet.
Stable connections
Stable connections are enabled by making the GCP connection platform redundant in terms of both facilities and routes.
Wide-ranging rate menu
The Wide-ranging rate plans from 50 Mbps to 1 Gbps allow to choose line speed which meets the demand of a customer.
On-demand provisioning
All operations can be performed through a portal/API, and flexible scale-up/scale-out functions which comply with the traffic status of a customer are provided.
5.4.2. Available Functions¶
5.4.2.1. List of Functions¶
This menu provides the following functions:
Functions which conform to Google Cloud Partner Interconnect of Google LLC are provided. For details, refer to GOOGLE CLOUD INTERCONNECT .
Functions |
Function Overview |
|---|---|
GCP gateway function |
An L3 gateway function which connects between the “ECL2.0 logical network” and “Google could router” is provided. |
Self-Management Function |
A function is provided which allows to manage this function through operations by a customer via the customer portal/API. |
5.4.3. Description of Functions¶
5.4.3.1. GCP gateway function¶
An L3 gateway function for connecting with the GCP is provided.
For the connection destination GCP region name, check the connection destination GCP information.
When the service is released, only compute menus (e.g., Compute Engine and Kubernetes Engine) of GCP are connectable. Connections with public services (such as G.suite) are not possible.
The GCP gateway and Google could router are to be interconnected through BGP.
Enable communications between ECL2.0 and GCP through delivery of needed routes by ECL2.0 and GCP services.
A main backup redundancy configuration by means of BGP is used for the provision.
The outline of the GCP gateway function is as follows:
No. |
Functions |
Functions |
|---|---|---|
| 1 | Network Connectivity Function |
|
| 2 | Address Setting Function |
|
| 3 | Advertisement using BGP / Static Route Function |
|
| 4 | Bandwidth Setting Function |
|
1.Network Connectivity Function¶
The GCP gateway provides the following two kinds of interface:
Functions |
Specs / Restrictions |
|---|---|
GCP connection interface |
|
Gateway Interface |
|
2.Address Setting Function¶
For the interface which connects with the Google cloud router, /29 address allocated from the link local address (169.254.0.0/16) by Google is set.
A function for setting the addresses below to the gateway interface is provided:
Parameter |
Details |
|---|---|
Gateway IPv4 Address |
The Virtual IP Address for VRRP. |
Primary IPv4 Address |
IP address to be assigned to the primary-side interface of the redundant GCP gateways |
Secondary IPv4 Address |
IP address to be assigned to the secondary-side interface of the redundant GCP gateways |
VRRP Group ID |
The identifier of the specific VRRP group. |
3.Advertisement using BGP / Static Route Function¶
A BGP connection function with the Google cloud router is provided.
Customers are allowed to set a static route from the GCP gateway to the logical network.
The destination network address of a static route and the connection network address of a gateway interface can be advertised to GCP as a BGP route.
The maximum number of allowable Static Routes is 32.
No restrictions are imposed to IP address ranges which can be set to the destination network of a static route. However, do not set a network which includes the IP address below and whose mask length is longer than the IP address below. BGP and VRRP operations may be affected resulting in communication disconnection, due to longest match.
Gateway IPv4 address, primary IPv4 address, and secondary IPv4 address of the gateway interface (Figure in the address setting section: G1/P1/S1)
IPv4 address of the GCP connection interface and IPv4 address of the Google cloud router (Figure in the address setting section: P2/S2/P3/S3)
The default route can be set to the destination network of a static route.
4.Bandwidth setting function¶
A band which can be handled by the GCP gateway can be set. A band to be set conforms to the band plan for which the customer contracted.
5.4.3.2. Self-Management Function¶
Customers are able to perform the following operations via the Customer Portal / API.
No. |
Operations |
Operable Actions |
Details |
|---|---|---|---|
| 1 | Add / Remove Gateway Interface |
Add / Remove Connectivity |
Customers are able to create a Gateway Interface and connect to any Logical Network.
Customers are able to assign an IP Address to the Gateway Interface.
Customers are able to remove, and disconnect from the Gateway Interface.
|
| 2 | Static Routing Setting / Routing Advertisement |
Add or Remove Static Route / Advertised routes |
A static route can be set to the GCP gateway, and a BGP route can be advertised to the GCP side. |
1.Addition and deletion of a gateway interface¶
Customers are able to create a Gateway Interface and connect with any Logical Network. Customers can remove, and disconnect from the Gateway Interface.
When creating a gateway interface, assigning an arbitrary IP address is possible. Due to redundancy of gateway interfaces with the VRRP protocol, the address below can be set:
Parameter |
Details |
|---|---|
Connected Network |
Customers are able to connect to any Logical Network. |
Gateway IPv4 Address |
The Virtual IP Address for VRRP. |
Primary IPv4 Address |
IP address to be assigned to the ACT-side GCP gateway among the redundant GCP gateways |
Secondary IPv4 Address |
IP address to be assigned to the STANDBY-side GCP gateway among the redundant GCP gateways |
VRRP Group ID |
VRRPID to be used for the gateway interface |
Note
If a VRRP group ID duplicates on the same logical network, communications may not be performed properly. Therefore, be sure to specify a different value.
Customers are duly advised that the IP Address cannot be modified. Hence, if Customers would like to change / modify the IP Address, they are required to first remove and add a new connectivity for the Logical Network.
2. スタティックルートの設定／経路広告¶
Parameter |
Details |
|---|---|
Name |
The name of specific Static Routes can be set. |
Description |
Letters of this particular Static Routing can be set. |
Destination |
The network (IP address block) of the transmission destination of this static route can be set. Also, this address is advertised to the GCP side as route information. |
Next Hop |
Customers are able to set the Next Hop to communicate with the Destination Network. |
Note
Maximum number of Static Route will be 32.
The destination and next hop cannot be changed. If changes are to be made, deletion and creation of the static route are required.
5.4.4. Service Menu¶
5.4.4.1. Service List¶
This menu provides customers with the following plan:
ECL2.0 Region |
JP5 | |
|---|---|---|
Guaranteed Bandwidth |
50M | ◯ |
| 100M | ◯ | |
| 200M | ◯ | |
| 300M | ◯ | |
| 400M | ◯ | |
| 500M | ◯ | |
| 1G | ◯ |
5.4.4.2. Connection destination GCP information¶
The location information of the GCP to be connected through this menu is as follows:
Service |
Types |
Details |
|---|---|---|
| ECL2.0 | Region |
JP5 |
| GCP | Region |
|
City |
|
|
Availability zone of a city (Main) |
|
|
Availability zone of a city (Backup) |
|
5.4.4.3. Order Types and Methods¶
This menu can be applied for via a customer portal/API.
Order Types |
Order Methods |
Offering Date |
|---|---|---|
Application for new opening of Google Cloud Platform connections |
Application through operations by a customer via the customer portal/API.
After the application, activating with Google Cloud Console is needed.
|
Same Day Availability |
Bandwidth change regarding Google Cloud Platform connections |
Application through operations by a customer via the customer portal/API. |
Same Day Availability |
Termination of Google Cloud Platform connections |
Application through operations by a customer via the customer portal/API. |
Same Day Availability |
Note
Note that change of the band causes communications to be disconnected for several minutes.
When band change which results in rate increase is to be made, note that the customer may be asked to deal with through termination and new creation, depending on the accommodation status.
30 days after application of new opening for Google Cloud Platform connections, the application is automatically canceled and the status before the application is restored, in the following cases:
Activation with Google Cloud Console was not performed.
Application failed for reasons such as inappropriate parameters
5.4.4.4. Important Things to Note when Ordering¶
Conditions
This menu provides services under a redundancy configuration (main/backup). Note that this menu is not available under a non-redundancy configuration.
The connection destination GCP information includes “availability zones of cites” to be designated as the main and backup ones. Also on the GCP side, application and redundancy control which meet them need to be performed.
Regarding application for Google Cloud Platform connections, the upper-limit and lower-limit numbers and the sales unit are as follows:
Maximum Number |
Minimum Number |
Unit |
|
Google Cloud Platform Inter-Connectivity |
4 | 0 | 1 |
Preparation
Before applying for this menu, contract for use of the Google Cloud Platform(TM), and creation of cloud routers and partner interconnect attachments need to be carried out.
Create two cloud routers and two partner interconnect attachments for the purpose of redundancy.
When applying for through the customer portal/API, enter a “pairing key” ID issued when partner interconnect attachments are applied for.
Monitoring application status to the Google system
After start of opening processing on ECL2.0, activation status of the partner interconnect attachments in terms of the Google system is periodically monitored by ECL2.0. Note that, because of the specifications, GCP connection is automatically abolished when abolishment of either of the partner interconnect attachments is detected during monitoring.
Once opening processing is completed, periodical monitoring regarding the Google system is not performed by ECL2.0. If either or both of the partner interconnect attachments are deleted in this status, single side-use operations or communication disconnection result. Operations with the both side-use are assumed, so avoid to perform single side-use operations. If having deleted the partner interconnect attachments unintentionally after completion of the opening processing, abolish the corresponding lines and make an application again.
Regarding application during one-piece maintenance
There is a case where a part of new create / change / terminate can not be done during one-piece maintenance.
Depending on the content of maintenance, customer may not be able to apply for about a few days.
Please confirm that customers are connected redundantly after applying. Please refer to the tutorial for confirmation method.
Others
After newly applying for this menu, it can be canceled through the customer portal/API before activation with Google Cloud Console.
If a new application for this menu fails for any reason, the status before the application is restored. At that time, the partner interconnect attachments are abolished. Therefore, to make an application again, create partner interconnect attachments again and use a new pairing key.
This menu does not support operations of Google Cloud Console. Check with any GCP support (e.g., official documents).
5.4.5. Terms And Conditions¶
5.4.5.1. Usage Conditions with Other Service Menus¶
This service menu can be combined with all other service menus. Connections with the Logical Network is only possible with connectivities to the Data Plane.
5.4.5.2. Minimum Usage Period¶
There is no minimum contract period.
5.4.6. Pricing¶
5.4.6.1. Initial Fee¶
There is no initial fee for this service.
5.4.6.2. Monthly Fees¶
This menu charges a Monthly usage fee. Monthly usage fee will be the Monthly billing maximum.
Note
Regarding this menu, customers are charged by Google LLC and NTT Communications separately for their respective sections.
For the section provided by NTT Communications, charge will be started after the completion of application with the customer portal/API and that of activation with Google Cloud Console.
5.4.7. Quality of Service¶
5.4.7.1. Support Coverage¶
The functions described in this Service Description are subject to Support Services.
After contract for this menu was made, problems attributed to inappropriate parameter settings (e.g., static-routing settings) by the customer are out of the support coverage.
5.4.7.2. Operations¶
The Quality of Operation for this Service Menu meets the Operation quality of the prescribed Enterprise Cloud 2.0 Standards.
The operational quality of the section provided by Google LLC conforms to the operational quality prescribed by Google LLC. Regarding failure of the section provided by Google LLC, NTT Communications will not notify of and deal with the failure.
5.4.7.3. SLA¶
The SLA for this Service Menu meets the SLA Standards defined by Enterprise Cloud 2.0.
This menu realizes 99.9 percent SLA provision only when main/backup redundancy has been applied for and the settings have been made properly.
5.4.7.4. Points to Note¶
Configuration
If multiple GCP gateways have been connected with the same logical network, communications fail due to the duplication of MAC addresses. Connect GCP gateways to different logical networks.
The MTU size in the GCP is 1,440 bytes. Set 1,440 bytes as the MTU size of the server which communicates with the GCP. If this setting is not made, communications may be disabled.
Do not connect to a logical network for common-function gateway connections. A link local address is allocated by Google as an IP address for the GCP connection segment, and thus address duplication can occur.
Operations
The sections other than the one to be connected regarding this menu are out of the support coverage. For failures (and others) regarding the section which Google LLC directly serves to the customer, notification by NTT Communications will not be made.
Restrictions of communications to the GCP connection gateway
For communications to the GCP connection gateway, flow rate restriction is executed to protect the service platform.
For communications passing over the GCP connection gateway, flow rate restriction is not executed and the quality and rate based on the contracted plan are served.