Skip to content

Commit 62569fd

Browse files
robswainrobswain
committed
Add dual router support
1 parent c7d59fc commit 62569fd

File tree

5 files changed

+35
-8
lines changed

5 files changed

+35
-8
lines changed

‎articles/private-5g-core/collect-required-information-for-a-site.md

Lines changed: 21 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -88,30 +88,41 @@ Collect all the values in the following table to define the packet core instance
8888
:::zone pivot="ase-pro-gpu"
8989
|Value |Field name in Azure portal |
9090
|---------|---------|
91-
| The IP address for the control plane interface on the access network. For 5G, this interface is the N2 interface; for 4G, it's the S1-MME interface; for combined 4G and 5G, it's the N2 and S1-MME interfaces. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying the AKS-HCI cluster on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md#order-and-set-up-your-azure-stack-edge-pro-devices). |**N2 address (Signaling)** (for 5G), **S1-MME address** (for 4G), or **S1-MME/N2 address (Signaling)** (for combined 4G and 5G). |
92-
| The virtual network name on port 5 on your Azure Stack Edge Pro device corresponding to the control plane interface on the access network. For 5G, this interface is the N2 interface; for 4G, it's the S1-MME interface; for combined 4G and 5G, it's the N2/S1-MME interface; for combined 4G and 5G, it's the N2/S1-MME interface. </br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N2 virtual subnet** (for 5G), **ASE S1-MME virtual subnet** (for 4G), or **ASE N2/S1-MME virtual subnet** (for combined 4G and 5G). |
91+
| The virtual network name on port 3 on your Azure Stack Edge Pro 2 corresponding to the control plane interface on the access network. For 5G, this interface is the N2 interface; for 4G, it's the S1-MME interface; for combined 4G and 5G, it's the N2/S1-MME interface. |**ASE N2 interface** (for 5G), **ASE S1-MME interface** (for 4G), or **ASE S1-MME/N2 interface** (for combined 4G and 5G). |
92+
| The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying the AKS-HCI cluster on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices). </br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N2 virtual IP address** (for 5G), **ASE S1-MME virtual IP address** (for 4G), or **ASE S1-MME/N2 virtual IP address** (for combined 4G and 5G). |
93+
| The virtual network name on port 3 on your Azure Stack Edge Pro 2 corresponding to the user plane interface on the access network. For 5G, this interface is the N3 interface; for 4G, it's the S1-U interface; for combined 4G and 5G, it's the N3/S1-U interface. |**ASE N3 interface** (for 5G), **ASE S1-U interface** (for 4G), or **ASE S1-U/N3 interface** (for combined 4G and 5G). |
94+
| The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying the AKS-HCI cluster on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices).</br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N3 virtual IP address** (for 5G), **ASE S1-U virtual IP address** (for 4G), or **ASE S1-U/N3 virtual IP address** (for combined 4G and 5G). |
9395
| The ID number of the VLAN for the N2 network | S1-MME/N2 VLAN ID |
9496
| The subnet for the IP address configured for the N2 interface e.g. 10.232.44.0/24 | S1-MME/N2 subnet |
9597
| The gateway for the IP address configured for the N2 interface e.g. 10.232.44.1. If the subnet does not have a default gateway, use another IP address in the subnet which will respond to ARP requests (such as one of the RAN IP addresses). If there's more than one gNB connected via a switch, choose one of the IP addresses for the gateway. | S1-MME/N2 gateway |
98+
| The IP address of one of a redundant pair of access network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | S1-MME/N2 gateway BFD endpoint 1 |
99+
| The IP address of one of a redundant pair of access network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | S1-MME/N2 gateway BFD endpoint 2 |
96100
| The virtual network name on port 5 on your Azure Stack Edge Pro device corresponding to the user plane interface on the access network. For 5G, this interface is the N3 interface; for 4G, it's the S1-U interface; for combined 4G and 5G, it's the N3/S1-U interface. </br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N3 virtual subnet** (for 5G), **ASE S1-U virtual subnet** (for 4G), or **ASE N3/S1-U virtual subnet** (for combined 4G and 5G). |
97101
| The ID number of the VLAN for the N3 network | S1-U/N3 VLAN ID |
98102
| The local IP address for the N3 interface | S1-U/N3 address |
99103
| The subnet for the IP address configured for the N3 interface e.g. 10.232.44.0/24 | S1-U/N3 subnet |
100104
| The gateway for the IP address configured for the N3 interface e.g. 10.232.44.1. If the subnet does not have a default gateway, use another IP address in the subnet which will respond to ARP requests (such as one of the RAN IP addresses). If there's more than one gNB connected via a switch, choose one of the IP addresses for the gateway. | S1-U/N3 gateway |
105+
| The IP address of one of a redundant pair of access network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | S1-U/N3 gateway BFD endpoint 1 |
106+
| The IP address of one of a redundant pair of access network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | S1-U/N3 gateway BFD endpoint 2 |
101107
:::zone-end
102108
:::zone pivot="ase-pro-2"
103109
|Value |Field name in Azure portal |
104110
|---------|---------|
105-
| The IP address for the control plane interface on the access network. For 5G, this interface is the N2 interface; for 4G, it's the S1-MME interface; for combined 4G and 5G, it's the N2 and S1-MME interfaces. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying the AKS-HCI cluster on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices). |**N2 address (Signaling)** (for 5G), **S1-MME address** (for 4G), or **S1-MME/N2 address (Signaling)** (for combined 4G and 5G). |
106-
| The virtual network name on port 3 on your Azure Stack Edge Pro 2 corresponding to the control plane interface on the access network. For 5G, this interface is the N2 interface; for 4G, it's the S1-MME interface; for combined 4G and 5G, it's the N2/S1-MME interface. </br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N2 virtual subnet** (for 5G), **ASE S1-MME virtual subnet** (for 4G), or **ASE N2/S1-MME virtual subnet** (for combined 4G and 5G). |
107-
| The virtual network name on port 3 on your Azure Stack Edge Pro 2 corresponding to the user plane interface on the access network. For 5G, this interface is the N3 interface; for 4G, it's the S1-U interface; for combined 4G and 5G, it's the N3/S1-U interface. </br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N3 virtual subnet** (for 5G), **ASE S1-U virtual subnet** (for 4G), or **ASE N3/S1-U virtual subnet** (for combined 4G and 5G). |
111+
| The virtual network name on port 3 on your Azure Stack Edge Pro 2 corresponding to the control plane interface on the access network. For 5G, this interface is the N2 interface; for 4G, it's the S1-MME interface; for combined 4G and 5G, it's the N2/S1-MME interface. |**ASE N2 interface** (for 5G), **ASE S1-MME interface** (for 4G), or **ASE S1-MME/N2 interface** (for combined 4G and 5G). |
112+
| The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying the AKS-HCI cluster on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices). </br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N2 virtual IP address** (for 5G), **ASE S1-MME virtual IP address** (for 4G), or **ASE S1-MME/N2 virtual IP address** (for combined 4G and 5G). |
113+
| The virtual network name on port 3 on your Azure Stack Edge Pro 2 corresponding to the user plane interface on the access network. For 5G, this interface is the N3 interface; for 4G, it's the S1-U interface; for combined 4G and 5G, it's the N3/S1-U interface. |**ASE N3 interface** (for 5G), **ASE S1-U interface** (for 4G), or **ASE S1-U/N3 interface** (for combined 4G and 5G). |
114+
| The IP address for the control plane interface on the access network. You identified this address in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br> This IP address must match the value you used when deploying the AKS-HCI cluster on your Azure Stack Edge Pro device. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro devices](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#order-and-set-up-your-azure-stack-edge-pro-devices).</br></br> For an HA deployment, this IP address MUST NOT be in any control plane or user plane subnets; it's used as the destination of routes in the access network gateway routers. | **ASE N3 virtual IP address** (for 5G), **ASE S1-U virtual IP address** (for 4G), or **ASE S1-U/N3 virtual IP address** (for combined 4G and 5G). |
108115
| The ID number of the VLAN for the N2 network | S1-MME/N2 VLAN ID |
109116
| The subnet for the IP address configured for the N2 interface e.g. 10.232.44.0/24 | S1-MME/N2 subnet |
110117
| The gateway for the IP address configured for the N2 interface e.g. 10.232.44.1. If the subnet does not have a default gateway, use another IP address in the subnet which will respond to ARP requests (such as one of the RAN IP addresses). If there's more than one gNB connected via a switch, choose one of the IP addresses for the gateway. | S1-MME/N2 gateway |
118+
| The IP address of one of a redundant pair of access network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | S1-MME/N2 gateway BFD endpoint 1 |
119+
| The IP address of one of a redundant pair of access network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | S1-MME/N2 gateway BFD endpoint 2 |
111120
| The ID number of the VLAN for the N3 network | S1-U/N3 VLAN ID |
112121
| The local IP address for the N3 interface | S1-U/N3 address |
113122
| The subnet for the IP address configured for the N3 interface e.g. 10.232.44.0/24 | S1-U/N3 subnet |
114123
| The gateway for the IP address configured for the N3 interface e.g. 10.232.44.1. If the subnet does not have a default gateway, use another IP address in the subnet which will respond to ARP requests (such as one of the RAN IP addresses). If there's more than one gNB connected via a switch, choose one of the IP addresses for the gateway. | S1-U/N3 gateway |
124+
| The IP address of one of a redundant pair of access network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | S1-U/N3 gateway BFD endpoint 1 |
125+
| The IP address of one of a redundant pair of access network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | S1-U/N3 gateway BFD endpoint 2 |
115126
:::zone-end
116127

117128
## Collect UE usage tracking values
@@ -143,6 +154,8 @@ For each data network that you want to configure, collect all the values in the
143154
| The ID number of the VLAN for the data network | SGi/N6 VLAN ID |
144155
| The IP address of the N6 interface | SGi/N6 address |
145156
| The gateway for the IP address configured for the N6 interface | SGi/N6 gateway |
157+
| The IP address of one of a redundant pair of data network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | SGi/N6 gateway BFD endpoint 1 |
158+
| The IP address of one of a redundant pair of data network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | SGi/N6 gateway BFD endpoint 2 |
146159
| The network address of the subnet from which dynamic IP addresses must be allocated to user equipment (UEs), given in CIDR notation. You don't need this address if you don't want to support dynamic IP address allocation for this site. You identified this in [Allocate user equipment (UE) IP address pools](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-gpu#allocate-user-equipment-ue-ip-address-pools). The following example shows the network address format. </br></br>`192.0.2.0/24` </br></br>Note that the UE subnets aren't related to the access subnet. |**Dynamic UE IP pool prefixes**|
147160
| The network address of the subnet from which static IP addresses must be allocated to user equipment (UEs), given in CIDR notation. You don't need this address if you don't want to support static IP address allocation for this site. You identified this in [Allocate user equipment (UE) IP address pools](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-gpu#allocate-user-equipment-ue-ip-address-pools). The following example shows the network address format. </br></br>`203.0.113.0/24` </br></br>Note that the UE subnets aren't related to the access subnet. |**Static UE IP pool prefixes**|
148161
| The Domain Name System (DNS) server addresses to be provided to the UEs connected to this data network. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-gpu#allocate-subnets-and-ip-addresses). </br></br>This value might be an empty list if you don't want to configure a DNS server for the data network. In this case, UEs in this data network will be unable to resolve domain names. | **DNS Addresses** |
@@ -154,7 +167,9 @@ For each data network that you want to configure, collect all the values in the
154167
| The name of the data network. This could be an existing data network or a new one you'll create during packet core configuration. |**Data network name**|
155168
| The ID number of the VLAN for the data network | SGi/N6 VLAN ID |
156169
| The IP address of the N6 interface | SGi/N6 address |
157-
| The gateway for the IP address configured for the N6 interface | SGi/N6 gateway |
170+
| The gateway for the IP address configured for the N6 interface | SGi/N6 gateway |
171+
| The IP address of one of a redundant pair of data network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | SGi/N6 gateway BFD endpoint 1 |
172+
| The IP address of one of a redundant pair of data network gateway routers in a highly available (HA) deployment. Used to establish a BFD session between the packet core and each router to maintain service if one router goes down. | SGi/N6 gateway BFD endpoint 2 |
158173
| The network address of the subnet from which dynamic IP addresses must be allocated to user equipment (UEs), given in CIDR notation. You don't need this address if you don't want to support dynamic IP address allocation for this site. You identified this in [Allocate user equipment (UE) IP address pools](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-user-equipment-ue-ip-address-pools). The following example shows the network address format. </br></br>`192.0.2.0/24` </br></br>Note that the UE subnets aren't related to the access subnet. |**Dynamic UE IP pool prefixes**|
159174
| The network address of the subnet from which static IP addresses must be allocated to user equipment (UEs), given in CIDR notation. You don't need this address if you don't want to support static IP address allocation for this site. You identified this in [Allocate user equipment (UE) IP address pools](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-user-equipment-ue-ip-address-pools). The following example shows the network address format. </br></br>`203.0.113.0/24` </br></br>Note that the UE subnets aren't related to the access subnet. |**Static UE IP pool prefixes**|
160175
| The Domain Name System (DNS) server addresses to be provided to the UEs connected to this data network. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md?pivots=ase-pro-2#allocate-subnets-and-ip-addresses). </br></br>This value might be an empty list if you don't want to configure a DNS server for the data network. In this case, UEs in this data network will be unable to resolve domain names. | **DNS Addresses** |

0 commit comments

Comments
 (0)