The route of China Mobile AS9808 from China to Los Angles has been rerouted to Hong Kong.

There are still some issues on these nodes, we already fix it, but a reboot is still required.

The reboot will be operated today.

Due to specific reasons, we need to switch the IP for all VMs which in the LAX data center and 205.210.164.0/22 subnet recently.

The new subnet is 154.17.0.0/19;

Please keep looking your email, after switching, we will reboot your VM to update the configuration. If your VM has no cloud-init installed, we cannot update your IP configuration.

HKG Core Network Maintaining;
We are trying to recover the connection/BGP session CW(AS1273) and IEPL between HKG-LAX. The connection between CERNET2 and HKG will be rerouted back soon.

Since our Core Router does not support GE(1Gbps) interface, the currently 1Gbps module has no enough FIB memory, we have to move the IEPL connection to our Equinix HK1 PoP for compatibility connection.

Also, our contract with CW will be ended in Feb 2020, we will use AS3491 to connect with CERNET2. As we test and inquiry, AS3491 has PNI with CERNET2, which means it has a larger bandwidth than CW( CW connect with CERNET2 via HKIX).

We apologize for the recent unstable network.

- - - - - -

The new nodes in LAX Datacenter have been installed. These servers will be available within this month; It is expected to provide services to over 800 users, which means we can migrate all VMs to new nodes if you want.

The CPU is Xeon Gold 6230( running on full power, 3.9Ghz mode )
RAM is DDR4 2933Mhz
We are using S3510 MLC SSD (67k/15.3k IOPS, 500/460 MB/s) on these nodes.

HKG urgent:
unexpected BGP session down; it should caused by a huge DDoS attack. We already update the firewall policy. Already fixed.

Anchnet BGP session down. waiting for Anchnet

Partial Network Unreachable in HKG:
Message from NTT(AS2914):

Hello,

GIN-1-***** has been created for this inquiry. I am showing the service is down due to scheduled maintenance (ticket GIN-1-*****)
I am showing the following received notification on December 22nd.

a00.tkokhk01.hk.bb.gin.ntt.net-->et-0/0/**:0 - BC: AB dmit - TGAS stf-***** USID ***** -- direct
noc@biz.dmit.io - *****

-------------------------------------------------------------------------------------------------------------------------------------------
*Ticket Number*: GIN-1-******
*Start Date/Time*: 2020-01-21 21:00 UTC
*End Date/Time*: 2020-01-22 00:00 UTC
*Direct Impact*: Users connected to this device will experience latency/downtime as the router is reloaded and routing is reestablished.
*Indirect Impact*:
*Reason*: We will be performing a software upgrade affecting the service(s) listed below.
-------------------------------------------------------------------------------------------------------------------------------------------

DMIT@re0.hkg.DMIT.io> show bgp summary | match 2914
199.245.16.61 2914 13658 22 0 1 5:24 Establ
2001:218:6000:5000::85 2914 11339 14 0 1 5:12 Establ

Dears,

This is NOC team from DMIT Inc;

Due to the IP management policy inside of our company, we are going to replace all the IPv4 addresses in 205.210.164.0/22 subnets.

We will assign your IP automatically and then send you an email after replacement success.

The 205.210.164.0/22 will be disconnected from the Internet on Jan 29, 2019. That means the IP will be inaccessible.

Please do not send tickets about this; we will send you an email for each IP you have that include Current IP information and new IP information. The IP that we assigned to you is a brand new IP.

This is something that you have to know:

- Please install cloud-init if you removed it or you install the system on your own. Without cloud-init, your VM will not update the IP address after reboot.
- We have to reboot your VM after IP replacement.
- Please manually configure 2nd or more IP after replacement, cloud-init will not update non-primary IP.
Best regards,

NOC of DMIT.

Our NOC fixed one network policy error in Premium Anti-DDoS IP services in LAX. This issue will lead to packet loss and low speed network from LAX to China. Please check it if necessary.

Related networks: 2.56.184.0/22

We already reroute the incoming route of CU between China and LAX to AS4837 backbone to avoid high packet loss on AS4837-AS4809. (It should be caused by Cyber Attack used up all the bandwidth capability between AS4809 and AS4837)

Sales:
During Jan 28, 2020 to Feb 4, 2020, all the new LAX order which paid by the non-monthly payment can ask for 1.3x traffic bounce.

Also, premium Anti-DDoS IP is free for Semi-Annually and Annually payment orders.

These promotions do not include PVM.LAX.Pro.Share;

Ongoing, you will receive opened ticket and email with new IPs for each instance that include 205.210.164.0/22.

Please check your ticket first for any issues, please note the 2nd IP will become primary IP; If you have 2+ IPs, please use the 2nd IP to log into your VM.

All jobs are done.

205.210.164.0/22 has been returned to our supplier.

DMIT@re1.lax.DMIT.IO> show route 205.210.164.0

inet.0: 783306 destinations, 1860134 routes (783298 active, 8 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[Static/5] 13w1d 02:26:48
> to ****** via xe-3/0/2.0

GIA.inet.0: 789749 destinations, 1913818 routes (789741 active, 8 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[Static/5] 13w1d 02:26:48
> to ****** via xe-3/0/2.0