Skip to content

Commit 1d0a24b

Browse files
v-regandownerv-regandowner
authored
Merge pull request #232371 from James-Green-Microsoft/2303-PR
2303 PR 1
2 parents f68e99f + d53b88c commit 1d0a24b

17 files changed

+431
-172
lines changed

‎articles/private-5g-core/azure-stack-edge-disconnects.md

Lines changed: 31 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -10,55 +10,54 @@ ms.date: 11/30/2022
1010
ms.custom: template-concept
1111
---
1212

13-
# Azure Stack Edge disconnects
13+
# Temporary AP5GC disconnects
1414

15-
There are several reasons why your *Azure Private 5G Core (AP5GC)* may have *Azure Stack Edge (ASE)* disconnects. These disconnects can either be unplanned short-term [Temporary disconnects](#temporary-disconnects) or periods of [Disconnected mode for up to two days](#disconnected-mode-for-azure-private-5g-core).
15+
Azure Stack Edge (ASE) can tolerate up to 5 days of unplanned connectivity issues. The following sections detail the behavior expected during these times and behavior after ASE connectivity resumes.
1616

17-
## Temporary disconnects
17+
Throughout temporary disconnects, the **Azure Stack Edge overview** displays a banner stating `The device heartbeat is missing. Some operations will not be available in this state. Critical alert(s) present. Click here to view details.`
1818

19-
ASE can tolerate small periods of unplanned connectivity issues. The following sections detail the behavior expected during these times and behavior after ASE connectivity resumes.
19+
> [!CAUTION]
20+
> Limited Azure Private 5G Core (AP5GC) support is available if you encounter issues while disconnected. If you encounter issues during a disconnect, we recommend you reconnect to enable full support. If it is not possible to reconnect, support is provided on a best-effort basis.
2021
21-
Throughout any temporary disconnects, the **Azure Stack Edge overview** will display a banner stating `The device heartbeat is missing. Some operations will not be available in this state. Critical alert(s) present. Click here to view details.`
22+
While disconnected, AP5GC core functionality persists through ASE disconnects due to network issues, network equipment resets and temporary network equipment separation. During disconnects, the ASE management GUI displays several banners stating that it's currently disconnected and describing the impact on functions.
2223

23-
### Configuration and provisioning actions during temporary disconnects
24-
25-
It's common to see temporary failures such as timeouts of configuration and provisioning while ASE is online, but there is a connectivity issue. AP5GC can handle such events by automatically retrying configuration and provisioning actions once the ASE connectivity is restored. If ASE connectivity is not restored within 10 minutes or ASE is detected as being offline, ongoing operations will fail and you will need to repeat the action manually once ASE reconnects.
24+
## Unsupported functions during disconnects
2625

27-
The **Sim overview** and **Sim Policy overview** blades display provisioning status of the resource in the site. This allows you to monitor the progress of provisioning actions. Additionally, the **Packet core control plane overview** displays the **Installation state** which can be used to monitor changes due to configuration actions.
26+
The following functions are not supported while disconnected:
2827

29-
### ASE behavior after connectivity resumes
28+
- Deployment of the packet core
29+
- Updating the packet core version
30+
- Updating SIM configuration
31+
- Updating NAT configuration
32+
- Updating service policy
33+
- Provisioning SIMs
3034

31-
Once ASE connectivity resumes, several features will resume:
35+
### Monitoring and troubleshooting during disconnects
3236

33-
- ASE management will resume immediately.
34-
- **Resource Health** will be viewable immediately.
35-
- **Workbooks** will be viewable immediately and will populate for the disconnected duration.
36-
- **Kubernetes Cluster Overview** will show as **Online** after 10 minutes.
37-
- **Monitoring** tabs will show metrics for sites after 10 minutes, but won't populate stats for the disconnected duration.
38-
- **Kubernetes Arc Insights** will show new stats after 10 minutes, but won't populate stats for the disconnected duration.
39-
- **Resource Health** views will be viewable immediately.
40-
- [Workbooks](../update-center/workbooks.md) for the ASE will be viewable immediately and will populate for the disconnected duration.
37+
While disconnected, you cannot enable local monitoring authentication or sign in to the [distributed tracing](distributed-tracing.md) and [packet core dashboards](packet-core-dashboards.md) using Azure Active Directory. However, you can access both distributed tracing and packet core dashboards via local access if enabled.
4138

42-
## Disconnected mode for Azure Private 5G Core
39+
If you expect to need access to your local monitoring tools while the ASE device is disconnected, you can change your authentication method to local usernames and passwords by following [Modify the local access configuration in a site](modify-local-access-configuration.md).
4340

44-
*Disconnected mode* allows for ASE disconnects of up to two days. During disconnected mode, AP5GC core functionality persists through ASE disconnects due to: network issues, network equipment resets and temporary network equipment separation. During disconnects, the ASE management GUI will display several banners alerting that it's currently disconnected and the impact on functions.
41+
Once the disconnect ends, log analytics on Azure updates with the stored data, excluding rate and gauge type metrics.
4542

46-
### Functions not supported while in disconnected mode
43+
### Configuration and provisioning actions during temporary disconnects
4744

48-
The following functions aren't supported while in disconnected mode:
45+
It's common to see temporary failures such as timeouts of configuration and provisioning while ASE is online but with a connectivity issue. AP5GC can handle such events by automatically retrying configuration and provisioning actions once ASE connectivity is restored. If ASE connectivity is not restored within 10 minutes, or ASE is detected as being offline, ongoing operations will fail and you will need to repeat the action manually once the ASE reconnects.
4946

50-
- Deployment of the 5G core
51-
- Updating the 5G core version
52-
- Updating SIM configuration
53-
- Updating NAT configuration
54-
- Updating service policy
55-
- Provisioning SIMs
47+
The **Sim overview** and **Sim Policy overview** blades display provisioning status of the resource in the site. This allows you to monitor the progress of provisioning actions. Additionally, the **Packet core control plane overview** displays the **Installation state** which can be used to monitor changes due to configuration actions.
5648

57-
### Monitoring and troubleshooting during disconnects
49+
### ASE behavior after connectivity resumes
5850

59-
While in disconnected mode, you won't be able to change the local monitoring authentication method or sign in to the [distributed tracing](distributed-tracing.md) and [packet core dashboards](packet-core-dashboards.md) using Azure Active Directory. If you expect to need access to your local monitoring tools while the ASE is disconnected, you can change your authentication method to local usernames and passwords by following [Modify the local access configuration in a site](modify-local-access-configuration.md).
51+
Once ASE connectivity resumes, several features resume:
6052

61-
Once the disconnect ends, log analytics on Azure will update with the stored data, excluding rate and gauge type metrics.
53+
- ASE management resumes immediately.
54+
- **Resource Health** is viewable immediately.
55+
- **Workbooks** is viewable immediately and populates for the disconnected duration.
56+
- **Kubernetes Cluster Overview** shows as **Online** after 10 minutes.
57+
- **Monitoring** tabs show metrics for sites after 10 minutes but don't populate stats for the disconnected duration.
58+
- **Kubernetes Arc Insights** shows new stats after 10 minutes but doesn't populate stats for the disconnected duration.
59+
- **Resource Health** views are viewable immediately.
60+
- [Workbooks](../update-center/workbooks.md) for the ASE are viewable immediately and populate for the disconnected duration.
6261

6362
## Next steps
6463

‎articles/private-5g-core/collect-required-information-for-private-mobile-network.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,7 @@ Note that once the SIM group is created, the encryption type cannot be changed.
7575

7676
- Manually entering values for each SIM into fields in the Azure portal. This option is best when provisioning a few SIMs.
7777
- Importing a JSON file containing values for one or more SIM resources. This option is best when provisioning a large number of SIMs. The file format required for this JSON file is given in [JSON file format for provisioning SIMs](#json-file-format-for-provisioning-sims). You'll need to use this option if you're deploying your private mobile network with an ARM template.
78+
- Importing an encrypted JSON file, provided by your SIM vendor, containing values for one or more SIM resources. You'll need to use this option if you're deploying your private mobile network with a JSON file provided by one of our SIM vendor partners. See [Collecting information for provisioning SIM vendor provided SIMs](#collecting-information-for-provisioning-sim-vendor-provided-sims) rather than collecting the values the next step.
7879

7980
1. Collect each of the values given in the following table for each SIM resource you want to provision.
8081

@@ -112,6 +113,58 @@ The following example shows the file format you'll need if you want to provision
112113
]
113114
```
114115

116+
## Collecting information for provisioning SIM vendor provided SIMs
117+
118+
Collect and edit each of the values in the following table for each SIM resource you want to provision using an encrypted JSON file, provided by your SIM vendor.
119+
120+
|Value | JSON file parameter name |
121+
|---------|---------|
122+
|The name for the SIM resource. The name must only contain alphanumeric characters, dashes, and underscores.|`name`|
123+
|The type of device that is using this SIM. This value is an optional, free-form string. You can use it as required to easily identify device types that are using the enterprise's mobile networks.|`deviceType`|
124+
|The SIM policy ID to apply to the SIM. See [Decide whether you want to use the default service and SIM policy](#decide-whether-you-want-to-use-the-default-service-and-sim-policy).|`simPolicy`|
125+
|The static IP configuration values for the SIM: **attachedDataNetwork**, **slice**, and **staticIp**.|`staticIpConfigurations`|
126+
127+
### Encrypted JSON file format for provisioning vendor provided SIMs
128+
129+
The following example shows the file format to provision your SIM resources using a SIM vendor provided encrypted JSON file.
130+
131+
```json
132+
{ 
133+
  "version": 1, 
134+
  "azureKey": 1, 
135+
  "vendorKeyFingerprint": "A5719BCEFD6A2021A11D7649942ECC14",
136+
  "encryptedTransportKey": "0EBAE5E2D31A1BE48495F6DCA65983EEAE6BA6B75A92040562EAD84079BF701CBD3BB1602DB74E85921184820B78A02EC709951195DC87E44481FDB6B826DF775E29B7073644EA66649A14B6CA6B0EE75DE8B4A8D0D5186319E37FBF165A691E607CFF8B65F3E5E9D448049704DE4EA047101ADA4554A543F405B447B8DB687C0B7624E62515445F3E887B3328AA555540D9959752C985490586EF06681501A89594E28F98BF66F179FE3F1D2EE13C69BC42C30A8D3DC6898B8160FC66CDDEE164760F27B68A07BA4C4AE5AFFEA45EE8342E1CA8470150ED6AF4215CEF173418E60E2B1DF4A8C2AE6F0C9A291F5D185ECAD0D94D48EFD06570A0C1AE27D5EC20", 
137+
  "signedTransportKey": "83515CC47C8890F62D4A0D16DE58C2F2DCFD827C317047693A46B9CA1F9EBC33CCDB8CABE04A275D65E180813CCFF43FC2DA95E19E2B9FF2588AE0914418DC9CB5506EB7AEADB272F5DAB9F0B1CCFAD62B95C91D4F4680A350F56D2A7F8EC863F4D61E1D7A38746AEE6C6391D619CCFCFA2B6D554671D91A26484CD6E120D84917FBF69D3B56B2AA8F2B36AF88492F1A7E267594B6C1596B81A81079540EC3F31869294BFEB225DFB171DE557B8C05D7C963E047E3AF36D1387FEDA28E55E411E5FB6AED178FB9C92D674D71AF8FEB6462F509E6423D4EBE0EC84E4135AA6C7A36F849A14A6A70E7188E08278D515BD95A549645E9D595D1DEC13E1A68B9CB67", 
138+
  "sims": [ 
139+
    { 
140+
      "name": "SIM 1", 
141+
      "properties": { 
142+
        "deviceType": "Sensor", 
143+
       "integratedCircuitCardIdentifier": "8922345678901234567", 
144+
        "internationalMobileSubscriberIdentity": "001019990010002", 
145+
        "encryptedCredentials": "3ED205BE2DD7F0E467283EC55F9E8F3588B68DC98811BE671070C65EFDE0CCCAD18C8B663231C80FB478F753A6B09142D06982421261679B7BB112D36473EA7EF973DCF7F634124B58DD945FE61D4B16978438CB33E64D3AA58B5C38A0D97030B5F95B16E308D919EB932ACCD36CB8C2838C497B3B38A60E3DD385", 
146+
        "simPolicy": { 
147+
          "id": "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.MobileNetwork/mobileNetworks/testMobileNetwork/simPolicies/MySimPolicy" 
148+
        }, 
149+
        "staticIpConfiguration": [
150+
{
151+
"attachedDataNetwork": {
152+
"id": "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.MobileNetwork/packetCoreControlPlanes/TestPacketCoreCP/packetCoreDataPlanes/TestPacketCoreDP/attachedDataNetworks/TestAttachedDataNetwork"
153+
},
154+
"slice": {
155+
"id": "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.MobileNetwork/mobileNetworks/testMobileNetwork/slices/testSlice"
156+
},
157+
"staticIp": {
158+
"ipv4Address": "2.4.0.1"
159+
}
160+
          } 
161+
        ] 
162+
      } 
163+
    } 
164+
  ] 
165+
} 
166+
```
167+
115168
## Decide whether you want to use the default service and SIM policy
116169

117170
Azure Private 5G Core offers a default service and SIM policy that allow all traffic in both directions for all the SIMs you provision. They're designed to allow you to quickly deploy a private mobile network and bring SIMs into service automatically, without the need to design your own policy control configuration.

0 commit comments

Comments
 (0)