We saw some reports from the client that said noVNC is unusable on the LAX site.
This is due to Proxmox and WHMCS module's limitations;
the DMIT dev team is engaging with this problem. It will be fixed soon.
This is due to Proxmox and WHMCS module's limitations;
the DMIT dev team is engaging with this problem. It will be fixed soon.
/var/log/DMIT-NOC.log
We saw some reports from the client that said noVNC is unusable on the LAX site. This is due to Proxmox and WHMCS module's limitations; the DMIT dev team is engaging with this problem. It will be fixed soon.
Fixed; Patch has been loaded.
Clipboard and xTerm.js feature will be available soon.
We will push patch to HKG site ASAP.
This patch will help to reduce the response time of API and VNC.
Clipboard and xTerm.js feature will be available soon.
We will push patch to HKG site ASAP.
This patch will help to reduce the response time of API and VNC.
/var/log/DMIT-NOC.log
Bandwidth capacity 📈 to the moon
After a month of cable patching work by CTA, this circuit is ready now. Traffic is loaded and ready to use.
/var/log/DMIT-NOC.log
The below message is for LAX.sPro and HKG.Pro only. Due to multiple limitations which listed below by our architecture, we need time to do more research on PVE code to make sPro stable and fast. - Cloudflare required TCP MSS lower than 1450 - Juniper does…
Scheduled maintenance:
Datecenter: LAX
Time: April 10, 4: 00 pm Eastern Time;
Content: DMIT will restart BGP session with AS4809; This will result in the loss of CN2(AS4809) route for 1 hour.
Impact: within the time, China traffic transit by Premium Routing Profile does not pass through AS4809
After maintenance: LAX.sPro no longer needs to modify MTU to avoid packet loss.
Datecenter: LAX
Time: April 10, 4: 00 pm Eastern Time;
Content: DMIT will restart BGP session with AS4809; This will result in the loss of CN2(AS4809) route for 1 hour.
Impact: within the time, China traffic transit by Premium Routing Profile does not pass through AS4809
After maintenance: LAX.sPro no longer needs to modify MTU to avoid packet loss.
Known issues:
Data center: HKG
Issues: high packet loss to China telecom (AS4134).
Service: PVM.HKG (without premium or lite tag)
ETR: April 11th to April 15th.
Data center: HKG
Issues: high packet loss to China telecom (AS4134).
Service: PVM.HKG (without premium or lite tag)
ETR: April 11th to April 15th.
Due to high deamon on Layer 7 DDoS Protection on sPro serial in LAX;
DMIT team decied to build a in datacenter Layer 7 DDoS firewall soon;
Our management team and NOC team are evaluating firewall appliances from several vendors.
hopefully, the firewall will be ready in June.
At that time, DMIT will offer basic protection for the entire LAX data center(Lite & Pro) and the best protection for sPro.
DMIT team decied to build a in datacenter Layer 7 DDoS firewall soon;
Our management team and NOC team are evaluating firewall appliances from several vendors.
hopefully, the firewall will be ready in June.
At that time, DMIT will offer basic protection for the entire LAX data center(Lite & Pro) and the best protection for sPro.
Untitled Diagram (4).png
249.5 KB
The diagram shows 3 situations with CFMT, just FYI.
Cloudflare Magic Transit only offer Layer 3/4 protection; so in the basic, all Layer 7 attack will be ignored at present.
The IP will lose routing optimization if the client chose to use Cloudflare CDN/WAF even without CFMT IP.
Cloudflare Magic Transit only offer Layer 3/4 protection; so in the basic, all Layer 7 attack will be ignored at present.
The IP will lose routing optimization if the client chose to use Cloudflare CDN/WAF even without CFMT IP.
/var/log/DMIT-NOC.log
Due to high deamon on Layer 7 DDoS Protection on sPro serial in LAX; DMIT team decied to build a in datacenter Layer 7 DDoS firewall soon; Our management team and NOC team are evaluating firewall appliances from several vendors. hopefully, the firewall…
We already ordered the appliances🥳
HKG Down for 30mins+:
Due to power failure in a switch at HKG datacenter and the configuration we made last time was not save;
the default spanning-tree configs start to work after power back; the STP block storage and management VLAN/Ports which leads to Ceph system failure and management lost;
The system should now back to normal;
50% VM was impacted;
Due to power failure in a switch at HKG datacenter and the configuration we made last time was not save;
the default spanning-tree configs start to work after power back; the STP block storage and management VLAN/Ports which leads to Ceph system failure and management lost;
The system should now back to normal;
50% VM was impacted;
For all Lite clients,
Due to insufficient IPv4 subnet resources for the Lite network.
DMIT will not offer free IPv4 replacement for the Lite network start with your next billing date.
We think you accepted this change once you paid for your next invoice.
This will be updated to TOS soon.
There is no impact on Pro network.
Due to insufficient IPv4 subnet resources for the Lite network.
DMIT will not offer free IPv4 replacement for the Lite network start with your next billing date.
We think you accepted this change once you paid for your next invoice.
This will be updated to TOS soon.
There is no impact on Pro network.
/var/log/DMIT-NOC.log pinned «For all Lite clients, Due to insufficient IPv4 subnet resources for the Lite network. DMIT will not offer free IPv4 replacement for the Lite network start with your next billing date. We think you accepted this change once you paid for your next invoice.…»
Recently, some of our customers have deployed services in DMIT Los Angeles datacenter that violate US laws;
Here, we want to let all our customer know:
DMIT will actively cooperate with the US government in order to ensure the stability of the service for other customers.
DMIT will provide all data we have of the suspect, including the disk of VM if PD, DHS, FBI, or any dept required for it.
Please ensure that your business complies with U.S. law in LAX Datacenter.
FYI: Cogent Co, is the IPv4 vendor of DMIT Inc in LAX Datacenter.
Here, we want to let all our customer know:
DMIT will actively cooperate with the US government in order to ensure the stability of the service for other customers.
DMIT will provide all data we have of the suspect, including the disk of VM if PD, DHS, FBI, or any dept required for it.
Please ensure that your business complies with U.S. law in LAX Datacenter.
FYI: Cogent Co, is the IPv4 vendor of DMIT Inc in LAX Datacenter.
/var/log/DMIT-NOC.log
Due to high deamon on Layer 7 DDoS Protection on sPro serial in LAX; DMIT team decied to build a in datacenter Layer 7 DDoS firewall soon; Our management team and NOC team are evaluating firewall appliances from several vendors. hopefully, the firewall…
FW Appliance arrived our datacenter. Deploy soon.
We proudly introduce every client and friend, the DMIT Dev.
DMIT Dev is a sub-brand of DMIT, Inc which focuses on software development and offers support to service providers.
At the first step, DMIT Dev offers 3 WHMCS modules:
1. Transfer Manager;
2. Client Status Manager;
3. Email Verification.
Please check our website at: https://DMIT.dev
The channel for DMIT Dev:
https://t.me/dmit_dev
The channel for mandarin speaker of DMIT Dev: https://t.me/dmit_dev_cn
DMIT Dev is a sub-brand of DMIT, Inc which focuses on software development and offers support to service providers.
At the first step, DMIT Dev offers 3 WHMCS modules:
1. Transfer Manager;
2. Client Status Manager;
3. Email Verification.
Please check our website at: https://DMIT.dev
The channel for DMIT Dev:
https://t.me/dmit_dev
The channel for mandarin speaker of DMIT Dev: https://t.me/dmit_dev_cn
Telegram
DMIT Dev Channel
Official: https://dmit.dev/
/var/log/DMIT-NOC.log pinned «We proudly introduce every client and friend, the DMIT Dev. DMIT Dev is a sub-brand of DMIT, Inc which focuses on software development and offers support to service providers. At the first step, DMIT Dev offers 3 WHMCS modules: 1. Transfer Manager; 2.…»
NOC get a report that AS58453 will go thru Miami Zayo first when AS58453 connects with DMIT LAX.
After inspection, it was caused by AS58453 peer with AS6461 in Miami Equinix last week; and AS58453 prefer the peering routes and didn't perform the geolocation community route path optimization.
We withdrawal the announcement to AS58453 from AS6461; Traffic from AS58453 will now be transited through NTT to DMIT.
After inspection, it was caused by AS58453 peer with AS6461 in Miami Equinix last week; and AS58453 prefer the peering routes and didn't perform the geolocation community route path optimization.
We withdrawal the announcement to AS58453 from AS6461; Traffic from AS58453 will now be transited through NTT to DMIT.