/var/log/DMIT-NOC.log
China Unicom (the Claimant) was unsuccessful in substantiating their claims in the arbitration case against DMIT (the Respondent) for the provision of services AS4837 and AS10099, valued at half a million US Dollars. Ultimately, it was determined that CUA…
Case closed and DMIT finally received awarded funds for corresponding legal action fee and the interests for CUA's late payment to us.. The process illustrates that DMIT did not violate the contract while not owing CUA any.
LAX: SEA <> SFO Cogent backbone congestion. withdrawal Cogent annoucement in temporary.
LAX was also impacted due to there are multiple faults which are related to Cogent LAX netowrk.
Arelion packet loss.
As we current information.
There might be a major issue in Los Angeles DT.
As we current information.
There might be a major issue in Los Angeles DT.
/var/log/DMIT-NOC.log
Arelion packet loss. As we current information. There might be a major issue in Los Angeles DT.
withdrawal AS1299 to avoid null route in temporary.
AS174 is back to normal
AS174 is back to normal
/var/log/DMIT-NOC.log
withdrawal AS1299 to avoid null route in temporary. AS174 is back to normal
Keep isolating AS1299 from the Internet in LAX.
Time: Apr 10 ~ Apr 30, 2025
Service: All VMs.
Impact: Lower IO & Network performance; couple reboot.
Duration: Less than 5 hrs per VM.
Description:
- Merge with LAX.T1.
Time: Apr 16 ~ Apr 24, 2025 (Changed to Apr 13 ~ Apr 17)
Service: All VMs.
Impact: Couple reboot.
Duration: Less than 3 hrs per VM.
Description:
- Replace CPU from 7402 to 7003 platform.
- Migrated from previous rack vendor to DMIT's Equinix rack.
/var/log/DMIT-NOC.log pinned «SJC Maintenance Time: Apr 10 ~ Apr 30, 2025 Service: All VMs. Impact: Lower IO & Network performance; couple reboot. Duration: Less than 5 hrs per VM. Description: - Merge with LAX.T1. HKG Maintenance Time: Apr 16 ~ Apr 24, 2025 (Changed to Apr 13 ~ Apr…»
/var/log/DMIT-NOC.log
SJC Maintenance Time: Apr 10 ~ Apr 30, 2025 Service: All VMs. Impact: Lower IO & Network performance; couple reboot. Duration: Less than 5 hrs per VM. Description: - Merge with LAX.T1. HKG Maintenance Time: Apr 16 ~ Apr 24, 2025 (Changed to Apr 13 ~ Apr…
SJC migration is fully completed.
/var/log/DMIT-NOC.log
HKG Maintenance
Time: Apr 16 ~ Apr 24, 2025
Service: All VMs.
Impact: Couple reboot.
Duration: Less than 3 hrs per VM.
Description:
- Replace CPU from 7402 to 7003 platform.
- Migrated from previous rack vendor to DMIT's Equinix rack.
Time: Apr 16 ~ Apr 24, 2025
Service: All VMs.
Impact: Couple reboot.
Duration: Less than 3 hrs per VM.
Description:
- Replace CPU from 7402 to 7003 platform.
- Migrated from previous rack vendor to DMIT's Equinix rack.
Plan change, the maintenance has been push 3 days earlier;
It will starts since today, and ends on Apr 17.
We will try to keep the downtime happens at ngith / off-peak hours.
It will starts since today, and ends on Apr 17.
We will try to keep the downtime happens at ngith / off-peak hours.
/var/log/DMIT-NOC.log
SJC Maintenance Time: Apr 10 ~ Apr 30, 2025 Service: All VMs. Impact: Lower IO & Network performance; couple reboot. Duration: Less than 5 hrs per VM. Description: - Merge with LAX.T1. HKG Maintenance Time: Apr 16 ~ Apr 24, 2025 (Changed to Apr 13 ~ Apr…
HKG Maintenance completed.
The timestamp issue happened after migration has been fixed as well.
The timestamp issue happened after migration has been fixed as well.
HKG one node experience major hardware error;
Working on the repairing.
Working on the repairing.
All the services were restored at 10PM HKT.
The compensation has been issued.
The control panel has been restored.
The new built node rather has CPU or motherboard failure which prevent it go thru the POST.
DMIT has ordered couple new nodes.
====
The WHMCS and corresponding modules currently used by DMIT are burdened with too many legacy issues. Even though DMIT has recoded most of it.
The configuration file loss is currently the main reason why VMs cannot recover quickly after node failure
We already figured out a new method for VM management which allows us have more secure and flexible way to manage the VM's configuration files.
This approach will be written in the new architecture and compatible with the current architecture to help smooth out the transition.
The compensation has been issued.
The control panel has been restored.
The new built node rather has CPU or motherboard failure which prevent it go thru the POST.
DMIT has ordered couple new nodes.
====
The WHMCS and corresponding modules currently used by DMIT are burdened with too many legacy issues. Even though DMIT has recoded most of it.
The configuration file loss is currently the main reason why VMs cannot recover quickly after node failure
We already figured out a new method for VM management which allows us have more secure and flexible way to manage the VM's configuration files.
This approach will be written in the new architecture and compatible with the current architecture to help smooth out the transition.
Our main site at Los Angeles was experiencing power outage.
There is a multiple incident happening in the downtown LA.
West7Center report:
There is a power cut to the suite; the power is restoring;
The issue happened in CoreSite LA1 has been resolved already:
A third-party vendor performing work on the street inadvertently damaged a water pipe. At this time, all building cooling systems are operating normally, and there is no indication of reduced water pressure entering the building. The Los Angeles Department of Water and Power (LADWP) has been notified, and we are currently awaiting an update on their estimated time of arrival.
You may direct any questions or concerns to the below department.
There is a multiple incident happening in the downtown LA.
West7Center report:
There is a power cut to the suite; the power is restoring;
The issue happened in CoreSite LA1 has been resolved already:
A third-party vendor performing work on the street inadvertently damaged a water pipe. At this time, all building cooling systems are operating normally, and there is no indication of reduced water pressure entering the building. The Los Angeles Department of Water and Power (LADWP) has been notified, and we are currently awaiting an update on their estimated time of arrival.
You may direct any questions or concerns to the below department.
The website and management systems are in Los Angeles core site. It won’t affected the service in other regions but the control panel will remain offline.
On-site engineers smell smoke onsite; no visible damage in the suite and in our cage.