【Completed】Virtual network maintenance in Japan regions
[2018/11/26] Updated maintenance work status[2018/11/13] Updated maintenance work status [2018/11/1] Updated FAQ, affected services, maintenance work status
[2018/10/12] Update information regarding maintenance date at JP1[2018/9/26] Updated about virtual network maintenance
Thank you for using NTT Communications Enterprise Cloud 2.0 (ECL) service.
We will conduct maintenance for virtual network service in Japan region (JP5, JP2 & JP1).
This maintenance is to improve service quality especially for network infrastructure of ECL.
Thank you for your understanding.
The details are as follows:
JP5 (completed), JP2(completed), JP1(completed)
JP5 (Tokyo 2nd Datacenter) region: Completed
JP2 (Osaka 5th Datacenter) region:Completed
JP1 (Saitama 1st Datacenter) region:Completed
Affected Services during maintenance window
1.GUI (ECL2.0 portal) and APIs are not available*
In this maintenance window, GUI/API configuration to the resources of regions is not available,
so users cannot boot and shut the resources.
In the term of maintenance window, the access is limited only via console connectivity to Virtual Servers and Baremetal Servers.
We highly recommend not to connect or conduct resources just before the maintenance window, as there might be affection to use services.
On the other hand, it is available to connect to other regions via GUI/API.
2.Interruption of Unicast: Less than 1 min.
One time per VM* (in case of failback as well)
Affected services ：Virtual Server, Firewall, Load Balancer, Security (Managed)
And Services connected above. e.g., Block Storage connected Virtual Server
Broadcast, Unknown unicast and Multicast may be unstable during the maintenance.
However, there may be no impact for services as we have functionality of retransmission the traffic.
Regarding the redundant configuration, FW and LB may switch to the redundant side.
Any query regarding the case, please refer to customer support via ticket.
Q: Are there any operations required from customer side before or after the maintenance?
A: Switch between active and redundant side of FW and LB may occur during the maintenance. We recommend customer to confirm the redundant configuration (VRRP related and DHCP settings in logical network) before the operation.
Service details are in the following links:
②Configuration to connect between virtual server and block storage
As for traffic from virtual server to block storage, it occurs interruption of unicast at virtual servers but in case that official template and users set configuration following our tutorial, disk I/O communication is not to be interrupted by multi-path device functionality, even when iSCSI connection is to be interrupted.
However depending on application there might be some interruption hence please check the configuration at each tenant by customer.
Also we highly recommend that customer who don’t set multi-path configuration, change the configuration of time-out amount of iSCSI initiator as “120 seconds”. (Please check impact to each applications in case of change configurations.)
On the other hand, there’s no impact to connectivity between Virtual Server instance and Volume, and Baremetal Server and Block Storage as well.
Q: Is it possible to operate VMs during maintenance?
A: During maintenance, it is not available to create/refer/update/delete VM via portal or API.
SSH connection to VM may be influenced due to any network service impact caused by the maintenance. We recommend customer to operate VM out of maintenance window.
Q: Please describe the impact on the application layer due to the network service impact caused by the maintenance.
A: We apologize that we cannot provide detailed information since the impact in application layer are depending on each customer’s environment.
Q:Which service menus are affected due to the interruption of multicast at this maintenance duration?
A:There is interruption for logical network which connect to Virtual Server, Firewall, Load Balancer, Security (Managed). Hence in case of the source/destination of the traffic are from/to these service components there may be affected to use, such as Baremetal Server, Storage, Internet Connectivity, VPN Gateway, SD-Exchange, Colocation Inter-Connectivity (CIC), Enterprise Cloud 1.0 Inter-Connectivity (EIC), Amazon Web Services Inter-Connectivity, Google Cloud Platform Inter-Connectivity, Microsoft Azure Inter-connectivity, Enterprise Cloud 2.0 Inter-Connectivity, DC Inter-Connectivity).