A DSR VM Configurations
The following table provides a summary of the VM configurations used for the benchmarking data and the affinity rules for deploying those VMs. Using VM sizes different from these tested values may give unexpected results because the application profiles are tuned to this number of vCPUs and memory sizes.
Table A-1 VM Configurations and Affinity Rules
| VM Name | vCPU | RAM (GB) | Disk (GB) | Max Config | Redundancy Models | Affinity/Placement Rules (Per Site) | Notes |
|---|---|---|---|---|---|---|---|
| DSR NOAM (Regular) | 4 | 14 | 120 | 1 Pair | Active/Standby | 2 VMs per DSR network in any site. VMs to be deployed on separate servers. | |
| DSR NOAM (Large) | 8 | 14 | 120 | 1 Pair | Active/Standby | 2 VMs per DSR network in any site. VMs to be deployed on separate servers. | It is recommended to use large NOAM profile if the
deployment is more than 32 C level servers.
If SOAM profile is large, NOAM profile must be large. In large profiles, the scheduled two measurement exports run in parallel. |
| DSR SOAM (Regular) | 4 | 14 | 120 | 1 Pair per DSR NF | Active/Standby or Active/Standby/Spare | 2 VMs per site. VMs to be deployed on separate servers. | Redundancy model Active/Standby/Spare model is used for PCA mated-pair deployments. For all other deployments Active or Standby model is used. |
| DSR SOAM (Large) | 8 | 14 | 120 | 1 Pair per DSR NF | Active/Standby or Active/Standby/Spare | 2 VMs per site. VMs to be deployed on separate servers. | Redundancy model Active/Standby/Spare model is used for PCA mated-pair deployments. For all other deployments Active or Standby model is used. If the diameter connections are higher than 4K, it is recommended to use SOAM large profile. If NOAM profile is large, SOAM profile must be large. In large profiles, the scheduled two measurement exports will run in parallel. |
| DA-MP (Regular) | 12 | 16 | 120 | 32 per DSR NF | Active Cluster (N+0) | Should be spread over as many servers as possible to minimize capacity loss on server loss. | The limit of 32 is the combined total of DA-MPs, DA-MPs with IWF, and DA-MP with EIR. The vSTP MPs do not count against this 32. Cannot max out all types in one DSR (for instance 32 DA-MPs AND 32 vSTPs). Any solution using more than 500 ART (Application Route Tables)/ARR (Application Route Rules)+PRR (Peer Route Rules) beyond 20k please use the below profile (DAMP w/ IWF) which is with 24GB RAM. |
| DA-MP (Large) | 18 | 24 | 120 | 32 per DSR NF | Active Cluster (N+0) | Should be spread over as many servers as possible to minimize capacity loss on server loss. | The limit of 32 is the combined total of DA-MPs, DA-MPs with IWF, and DA-MP with EIR. The vSTP MPs do not count against this 32. Cannot max out all types in one DSR (for instance 32 DA-MPs and 32 vSTPs). Any solution using more than 500 ART (Application Route Tables)/ARR (Application Route Rules) + PRR (Peer Route Rules) beyond 20k please use the below profile (DAMP w/ IWF) which is with 24GB RAM. |
| vSTP MP | 8 | 12 | 120 | 32 per DSR NF | Active Cluster (N+0) | Should be spread over as many servers as possible to minimize capacity loss on server loss. | The vSTP MPs do not count against the 32 DA-MP limits in a single OCDSR node, so a DSR can have up to 32vSTP MPs. Cannot max out all types in one DSR (for instance 32 DA-MPs and 32 vSTPs). |
| HomeSMSC Service MP | 8 | 12 | 120 | 32 per DSR NF | Active Cluster (N+0) | Should be spread over as many servers as possible to minimize capacity loss on server loss. | The Service MPs do not count against the 32 DA-MP limits in a single OCDSR node, so a DSR can have up to 32service MPs. Cannot max out all types in one DSR (for instance 32 DA-MPs and 32 service). |
| vENUM Service MP | 8 | 12 | 150 | 32 per DSR NF | Active Cluster (N+0) | Should be spread over as many servers as possible to minimize capacity loss on server loss. | The vENUM MPs do not count against the 32 DA-MP limits in a single OCDSR node, so a DSR can have up to 32 ENUM MPs. Cannot max out all types in one DSR (for instance 32 DA-MPs and 32 service). |
| IPFE | 6 | 16 | 120 | 2 pairs per DSR NF | Active/Standby | Each VM in a pair must be deployed on separate server. | Deployed in pairs. Max 2 pairs (4VMs). |
| SBR(s) | 12 | 25 | 120 | 8 Server Groups per SBR(b) | Active/Standby/Spare | Active/Standby VMs to be deployed on separate servers,Spare is typically at another geographic location for geo-redundancy. | Can be either Active/Standby/Spare or Active/Standby depending on customer geo-redundancy requirements. |
| SBR(b) | 12 | 32 | 120 | 8 Server Groups per SBR(b) | Active/Standby/Spare | Active/Standby VMs to be deployed on separate servers,Spare is typically at another geographic location for geo-redundancy. | Can be either Active/Standby/Spare or Active/Standby depending on customer geo-redundancy requirements. |
| SBR(u) | 12 | 24 | 120 | 64 Server Groups per SBR(b | Active/Standby/Spare | Active/Standby VMs to be deployed on separate servers,Spare is typically at another geographic location for geo-redundancy. | Can be either Active/Standby/Spare or Active/Standby depending on customer geo-redundancy requirements. |
|
SDS NOAM (Regular) |
4 | 32 | 350 | 1 Pair per Network | Active/Standby | Anti-affinity between the Active/Standby VMs | Active/Standby. An optional "Disaster Recovery" SDS is supported that would typically be located at a different data center to provide geo-redundancy. |
|
Query Server (Regular) |
4 | 32 | 350 | 1 per SDS NOAM | N/A since non-redundant | Non, non-redundant | Optional 1 per site. Can have one for the primary SDS-NOAM and one for the Disaster Recovery SDS-NOAM |
| SDS SOAM (Regular) | 4 | 12 | 175 | 1Pair per DSR NF | Active/Standby | 2 VMs per site. VMs to be deployed on separate servers. | |
| SDS DP (Regular) | 6 | 10 | 175 | 10 per DSR NF | Active Cluster (N+0) | Should be spread over as many servers as possible to minimize capacity loss on server loss. | To be evenly distributed across servers to minimize capacity loss. |
|
SDS NOAM (Large) |
4 | 128 | 890 | 1 Pair per Network | Active/Standby | Anti-affinity between the Active/Standby VMs | Active/Standby. An optional "Disaster Recovery" SDS is supported that would typically be located at a different data center to provide geo-redundancy. |
| Query Server (Large) | 4 | 128 | 890 | 1 per SDS NOAM | N/A since non-redundant | Non, non-redundant | Optional 1 per site. Can have one for the primary SDS-NOAM and one for the Disaster Recovery SDS-NOAM. |
| SDS SOAM (Large) | 4 | 64 | 450 | 1 Pair per DSR NF | Active/Standby | 2 VMs per site. VMs to be deployed on separate server. | Supports |
| SDS DP (Large) | 24 | 64 | 450 | 10 per DSR NF | Active Cluster (N+0) | Should be spread over as many servers as possible to minimize capacity loss on server loss. | To be evenly distributed across servers to minimize capacity loss. |
| UDR NO
(Small) |
6 | 16 | 270 | n (Active,Standby) | Active/Standby/Spare | Active/Standby/Spare VMs to be deployed on separate servers, Spare is typically at another geographic location for geo-redundancy | Redundancy model Active/Standby/Spare model is used. Active/Standby on Site 1 and Spare on Site 2. UDR is scaled by adding UDR NOs. The Standby UDR NO also receives query traffic from STP-MP and DA-MP. |
|
UDR NO (Medium) |
12 | 32 | 450 | n (Active,Standby) | Active/Standby/Spare | Active/Standby/Spare VMs to be deployed on separate servers, Spare is typically at another geographic location for geo-redundancy | Redundancy model Active/Standby/Spare model is used. Active/Standby on Site 1 and Spare on Site 2. UDR is scaled by adding UDR NOs. The Standby UDR NO also receives query traffic from STP-MP and DA-MP. |
|
UDR NO (Regular) |
18 | 70 | 450 | n (Active,Standby) | Active/Standby/Spare | Active/Standby/Spare VMs to be deployed on separate servers, Spare is typically at another geographic location for geo-redundancy | Redundancy model Active/Standby/Spare model is used. Active/Standby on Site 1 and Spare on Site 2. UDR is scaled by adding UDR NOs. The Standby UDR NO also receives query traffic from STP-MP and DA-MP. |
|
UDR NO (Large) |
32 | 128 | 850 | n (Active,Standby) | Active/Standby/Spare | Active/Standby/Spare VMs to be deployed on separate servers, Spare is typically at another geographic location for geo-redundancy | Redundancy model Active/Standby/Spare model is used. Active/Standby on Site 1 and Spare on Site 2. UDR is scaled by adding UDR NOs. The Standby UDR NO also receives query traffic from STP-MP and DA-MP. |
|
UDR NO (Extra Large) |
56 | 256 | 850 | n (Active,Standby) | Active/Standby/Spare | Active/Standby/Spare VMs to be deployed on separate servers, Spare is typically at another geographic location for geo-redundancy | Redundancy model Active/Standby/Spare model is used. Active/Standby on Site 1 and Spare on Site 2. UDR is scaled by adding UDR NOs. The Standby UDR NO also receives query traffic from STP-MP and DA-MP. |
| VNFM | 8 | 10 | 80 | NA | N/A since non-redundant | None, non-redundant | VNF Manager deployment |
| iDIH Application | 4 | 8 | 64 | 1 per Site | N/A since non-redundant | None, non-redundant | Optional component for Diameter traffic monitoring |
| iDIH Mediation | 4 | 8 | 64 | 1 per Site | N/A since non-redundant | None, non-redundant | Optional component for Diameter traffic monitoring |
| iDIH Database | 4 | 8 | 120GB + 100GB (ephemeral) | 1 per Site | N/A since non-redundant | None, non-redundant | Optional component for Diameter traffic monitoring |
| ATS | 8 | 16 | 120 | NA | N/A since non-redundant | None, non-redundant | Automated Test Suite Tool |