The Diameter > Configuration > Capacity Summary page displays information about maximum allowed and currently configured Diameter Configuration components.
Use the Diameter > Configuration > Capacity Summary page when planning, configuring, and maintaining the Diameter Configuration. See Diameter User's Guide for the maximum values per NE and per Configuration Component.
The following table shows the Maximum values per NE and per Configuration Component.
Constraint Name | Description | Value | Related Notes |
---|---|---|---|
Application Routing Rules | Maximum number that can be configured per Network Element | 128 | |
Capacity Configuration Sets | Maximum number that can be configured | 1000 | |
Application Ids (Per network element) | The total number that can be configured | 1000 | Calculated using this formula: [(16 Application IDs) * (4 Command Codes) * (2 Routing Entity Types per Preference List)] |
Application Ids (Per Connection) | The total number that can be configured | 10 | |
Connection Configuration Sets | Maximum number per Network Element | 2000 | |
Connections (Per Network Element ) | Maximum number for this configuration | Lesser of 16,000 OR [sum of individual DA-MP maximums] |
|
Connections (Per Peer Node ) | Maximum number for this configuration | 64 | |
Connections (Per Connection Route Group) | Maximum number for this configuration | 160 | |
CEX Configuration Sets | Maximum number that can be configured | 2000 | |
Supported Application Ids | Maximum number per CEX Configuration Set | An Application ID configured can be any one of the following types:
|
|
Supported Vendor ID(s) | Maximum number per CEX Configuration Set | 10 | If set, it contains the Vendor-Ids configured for the Vendor-Specific-Application-Ids. |
Diagnose Connections | Maximum number of connections in Test Mode that are being diagnosed | 2 | In Diagnostics Tool |
Diagnose PDUs | Maximum number of PDUs per Test Connection for a single diagnostic cycle. | 1 | |
Signaling IP Addresses | Maximum number per Local Node | 8 Any combination of IPv4 and IPv6 |
|
IP Addresses | Maximum number per Peer Node | 128 | |
Local Nodes | Maximum number per Network Element | 32 | |
Peer Nodes (Per Network Element) | Maximum number that can be configured | 16000 | One Peer Node per connection. |
Peer Node Groups (Per Network Element) | Maximum number that can be configured | 2500 | |
Peer Nodes (Per Route Group) | Maximum number that can be configured | 160 | |
Route Groups | Maximum number per Network Element | 1000 | |
Route Groups Per Route List | Maximum number per Route List | 3 | Supports priority values 1 thru 3 . |
Reroute On Answer | Maximum number of Order Pair combinations of Application Id and Answer Result Code value that can cause a Request re-routing. | 1000 | |
Route Lists | Maximum number per Network Element | 1000 | |
Number of Route Groups per Route List | Maximum per Route List | 3 | |
Supported Vendor Ids | Maximum number per set | 10 | Supported Vendor Ids cannot be greater than the number of Vendor-Specific Application Ids. |
Test Connections | Maximum number of connections in Test Mode for testing with the Diagnostics Tool | 2 | |
Target Set Addresses | Maximum number of TSAs per Local Node | 32 | |
Maintenance Screen Refresh Rate | Time interval in seconds after which data is refreshed on the Diameter Maintenance screens | 10 | |
DA-MPs | Maximum number that can be configured | 16 | |
Pending Answer Timers | Maximum number that can be configured | 16 | |
Peer Route Tables | Maximum number configured Per Network Element | 1000 | |
Peer Routing Rules (Per Peer Route Table) | Maximum number that can be configured | 1000 | |
Peer Routing Rules (Per Network Element ) | Maximum number that can be configured | 10000 | |
Associations between Application Ids and Peer Route Tables | Maximum number allowed | 20 | |
Routing Option Sets | Maximum number that can be configured | 20 | |
Command Codes | Maximum number that can be configured | 1000 | |
Message Priority Configuration Sets | Maximum number that can be configured | 20 | |
Message Priority Configuration Set Rules | Maximum number of configured Rules per Message Priority Configuration Set | 50 | |
Message Throttling Configuration Sets | Maximum number that can be configured | 50 | |
Connections with Message Throttling Configuration Sets assigned | Maximum connections that can have Message Throttling Configuration Sets assigned to them | 50 | |
Invalid MCC Ranges | Maximum number that can be Configured | 10 | |
Trusted Network Lists | Maximum number that can be configured. | 500 | |
Trusted Network Realms | Maximum number of Trusted Network Realms per Trusted Network List that can be configured. | 100 | |
Path Topology Hiding Configuration Sets | Maximum number that can be configured. | 500 | |
Host Network Suffixes | Maximum number per Path Topology Hiding Configuration Set | 10 | |
S6a/S6d HSS Topology Hiding Configuration Sets | Maximum number that can be configured. | 500 | |
S6a/S6d HSS Topology Hiding Host Names | Maximum number per S6a/S6d HSS Topology Hiding Configuration Set | 500 | |
MME/SGSN Topology Hiding Configuration Sets | Maximum number that can be configured. | 500 | |
MME/SGSN Host Names | Maximum number per MME/SGSN Topology Hiding Configuration Set | 300 | |
Protected Network Configuration Sets | Maximum number that can be configured. | 500 | |
S9 PCRF Topology Hiding Configuration Sets | Maximum number that can be configured | 500 | |
S9 PCRF Host Names | Maximum number per S9 PCRF Topology Hiding Configuration Set | 500 | |
S9 AF/pCSCF Topology Hiding Configuration Sets | Maximum number that can be configured | 500 | |
S9 AF/pCSCF Host Names | Maximum number per S9 AF/pCSCF Topology Hiding Configuration Set | 500 |