We will perform scheduled maintenance on the CloudCore platform starting Tuesday, Sept 23 at 00:00–02:00 PDT (UTC-07:00).
Why: Microsoft is retiring certain legacy Azure resources. We are upgrading public IPs and load balancers to Standard SKUs and migrating VMs to managed disks.
Expected impact (depending on your configuration, one or more may apply):
OMC portal/TR-069/EPC/BOSS API: Intermittent availability for ~30-60 minutes within the window.
CBSDs using Domain Proxy (DP): Service is impacted for the duration of any OMC/TR-069 disconnect.
eNBs on Cloud EPC: During periods when the cloud MME is offline, affected eNBs will have S1 disconnects and inactive cells.
HaloB-enabled eNBs: RAN stays up; however, SAS-enabled eNBs will RF mute (transmission disabled) while the cloud OMC is offline.
We cannot access https://cloudcore.baicells.com:4443 and all of our radios are offline. I tried to access the site from 3 different networks. Your status pages shows operational but omc/boss/portal are red. Do you have an update on this?
We are down too since the update! Have had to disable SAS to get back up but now we just went down again because OMC enabled the SAS on all of our CPE’s without our knowledge. Have been waiting for a response to urgent ticket for hours!
We had SAS off for all eNB’s and all CPE’s and things were working but OMC turned them all back on. Have turned them all back off again. We need an update form someone so we know what to expect.
To follow up here, an update has been posted to Status Page (https://status.cloudcore.baicells.com/). To prevent any service disruption during the maintenance window, SAS was temporarily disabled and re-enabled afterwards. There was a period after the migration in which security policies on the newly upgraded load balancers caused networking issues, including connectivity to SAS. As of 8am CDT, CloudCore services are 100% operational.
On CloudCore URL, the default port did change to 443. As browser histories were retaining the old port, we added a redirect from 4443 to 443.
Note, the only known issue at this time is a report of CBSDs failing to register with SAS again. This was due to the original CPI cert being expired. In this case, the CBSD installation parameters need to be updated again with CPI re-uploaded.
Our CPI certs are not expired. If someone will call back on the ticket and voice messages we left we can provide information needed to resolve the outstanding issues resulting from the upgrade. We still have major problems.