In this section:
Number of IP Addresses per Call Leg Size
The number of call legs supported for a given number of IP Addresses on different SBC platforms are listed below:
- SBC 7000, assuming UDP ports 4,000 through 64,444 are configured for media port usage - See table below.
- SBC 5400 with 10GE interfaces - Supports a maximum of 75000 sessions, requiring 4 IP addresses per call leg.
- SBC SWe - Supports a maximum of 64000 sessions, requiring 3 IP addresses per call leg.
For SBC 7000 media resource allocation scenarios, the SBC requires a minimum of 10 IP addresses configured to support 150,000 call legs (one Primary IP address plus 9 alternate IP addresses in non-VLAN configuration).
The number of IP addresses needed to support call legs:
| Number of Call Legs | Number of IP Addresses |
|---|---|
| 150,000 | 10 |
| 140,000 | 9 |
| 130,000 | 8 |
| 120,000 | 7 |
| 110,000 | 6 |
| 96,000 | 5 |
| 80,000 | 4 |
| 64,000 | 3 |
| 45,000 | 2 |
| 25,000 | 1 |
For example, to use 100,000 call legs configure at least six (6) IP addresses because five IP addresses will only allow up to 96,000 call legs through the SBC.
The SBC Core supports configuring up to 14 alternate media addresses. For more details, refer to Alternate Media IP Addresses Support.
Configuration Limits
The SBC 7000 supports a large number of configurable objects and is capable of supporting from a few very large customers to thousands of small customers. Important details about the provisioning system include:
- Interactive provisioning of configuration objects (such as commands typed at the CLI or entered in the EMA or EMS) does not affect call handling or capacity.
- Provisioning behavior does not depend on the number of existing entities. The addition of the 10,000th instance is roughly comparable to adding the first such instance.
Caution
Bulk or non-interactive provisioning may affect call handling. Operations such as sourcing a CLI script with many configuration commands (or even a few commands affecting particularly large objects) should only be done during a maintenance window or at non-busy-hour intervals.
Provisioning Limits
The SBC Core provisioning limits are shown in the following table.
Info
The term '5xx0' represents SBC models 5100, 5200, 5110 and 5210.
Modified: for 9.2.4
The two "largeuseracl" profiles are added to the table in the 9.2.4 release.
Configuration Objects | Provisioning Limits | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
SBC 7000 | SBC 5400 | SBC 5210 | SBC 5x00 | SBC SWe | SLB | |||||
| VM Memory >= 10 GiB RAM ("small" profile) | VM Memory ≥ 18 GiB RAM ("large" profile) | VM Memory ≥ 18 GiB RAM | VM Memory >= 10 GiB RAM ("small" profile) | VM Memory ≥ 18 GiB RAM ("large" profile) | VM Memory ≥ 18 GiB RAM | |||||
| Address Contexts | 4,000 | 2,048 | 2,048 | 2,048 | 129 | 2,048 | 2,048 | 129 | 2,048 | 2,048 |
| SIP Signaling Ports | 4,000 | 2,048 | 2,048 | 2,048 | 129 | 4,000 | 256 | 129 | 4,000 | 256 |
| H.323 Signaling Ports | 2,048 | 2,048 | 2,048 | 2,048 | 129 | 129 | 129 | N/A | N/A | N/A |
| SIP Trunk Groups | 40,000 | 20,000 | 10,000 | 10,000 | 1,024 | 20,000 | 20,000 | N/A | N/A | N/A |
| H.323 Trunk Groups | 2,048 | 2,048 | 2,048 | 2,048 | 129 | 256 | 256 | N/A | N/A | N/A |
| Gateway Trunks | 128 | 128 | 128 | 128 | 128 | 128 | 128 | N/A | N/A | N/A |
| Maximum IP Trunk Groups of All Signaling Types | 40,000 | 20,000 | 10,000 | 10,000 | 1,024 | 20,000 | 20,000 | N/A | N/A | N/A |
| Zones | 4,000 | 2,048 | 2,048 | 2,048 | 129 | 4,000 | 4,000 | 129 | 4,000 | 4,000 |
| DNS Groups | 2,048 | 2,048 | 2,048 | 2,048 | 129 | 129 | 129 | |||
| IP Interfaces | 4,0965 | 4,0965 | 4,0965 | 4,0965 | 1295 | 2,0485 | 2,0485 | 1295 | 2,0485 | 2,0485 |
| IP Interfaces Groups | 4,000 | 2,048 | 2,048 | 2,048 | 129 | 1,024 | 1,024 | 129 | 1,024 | 1,024 |
| IP Peers | 40,000 | 20,000 | 10,000 | 10,000 | 1,024 | 20,000 | 20,000 | N/A | N/A | N/A |
| Alternate Media IP Addresses (per LIF) | 254 | 254 | 254 | 254 | 254 | 254 | 254 | N/A | N/A | N/A |
| IP Addresses | 8,192 | 8,192 | 8,192 | 8,192 | 258 | 4,096 | 4,096 | 258 | 4,096 | 4,096 |
| IP ACLs | 50,0001 | 25,0002 | 17,8242 | 17,8242 | 2,0003 | 10,5924 | 10,5926 | 2,0003 | 10,5924 | 10,5926 |
| Dynamic Black List Entries | 4,000 | 2,000 | 1,024 | 1,000 | 100 | 100 | 100 | N/A | N/A | N/A |
| Enhanced DBL Profiles | 100 | N/A | N/A | N/A | ||||||
| SIP Adaptor Profiles | 512 | 512 | 512 | 512 | 256 | 512 | 512 | N/A | N/A | N/A |
| Tone Package Profiles | 2,048 | N/A | N/A | N/A | ||||||
Surrogate Registration Profiles | 256 | N/A | N/A | N/A | ||||||
AoRs for Surrogate Registrations | 10,000 | N/A | N/A | N/A | ||||||
| SWe Traffic Profiles | Refer to SBC SWe Traffic Profiles for details. | |||||||||
| Shared CAC Limits Pools | 4,000 Modified: for 9.2.4 | N/A | N/A | N/A | ||||||
Footnotes
1 - Includes approximately 10,000 IP ACLs for signaling ports (2 x 4,000 SIP, 2,000 H323) and 100 IP ACLs for OAM. A maximum of 35,648 IP ACLs are allowed for users.
2 - Includes approximately 4,000 IP ACLs for signaling ports and 100 IP ACLs for OAM. A maximum of 11,232 (for SBC 51x0/52x0 series) and 17,824 (for SBC 5400) IP ACLs are allowed for users.
3 - The number of user-defined ACLs is 772.
4 - The number of user-defined ACLs is 628.
5 - The maximum number of IP interfaces on a single SR-IOV packet interface is limited by the maximum number of VLANs supported on the VF.
The maximum VLANs supported on SR-IOV VF interfaces depend on NIC type/capability.
- For Intel X540, X550 NICs, the maximum VLANs supported on the SR-IOV VF interface is 63.
- For X710 with trust mode enabled, the maximum VLANs supported on SR-IOV interfaces is 63.
For the other NIC types, refer to the NIC specification provided by the vendor.
6 - The number of user-defined ACLs is 8308.
Note
The IP address number is twice that of the IP interface number. You can assign each interface an IPv4 and IPv6 address.
Note
One GiB (gibibyte) = 2^30 (1,073,741,824 bytes).
The time required to add an object to an existing configuration is immaterial (It takes much longer to actually type the command or complete the EMA/EMS fields). However, bulk loading of a large configuration from the CLI may take a substantial amount of time.
Caution
See cautionary note above about the potential bulk configuration loading on call handling performance.
While the SBC 7000 supports large limits on multiple types of configuration objects, a few typical usage scenarios exist. The length of time to bulk load a configuration depends on the size of the configuration. Consequently, four SBC Core profile classes are defined to give customers a rough idea for the bulk loading time relevant to their configuration:
- 1K profile – comprised of 1,000 instances each of Address Contexts, Zones, IP Interface Groups, IP Interfaces, Signaling Ports, and Trunk Groups
- 4K profile – comprised of 4,000 instances each of Address Contexts, Zones, IP Interface Groups, IP Interfaces, Signaling Ports, and Trunk Groups
- 4K/10K profile – comprised of 4,093 instances of IP Interfaces, 2,048 instances each of Zones, Address Contexts, IP Interface Groups, SIP Signaling Ports, 10,000 IP Peer, and 10,000 IP Trunks (see Note below).
- 4K/40K profile [SBC 7000 series only] – comprised of 4,000 instances each of Address Contexts, Zones, IP Interface Groups, IP Interfaces, Signaling Ports; and 40,000 Trunk Groups
Note
If both IPv4 and IPv6 are combined on every sipSigPort on an SBC 5200, the system limits the number of sipSigPorts to 1,980.
SIPREC-based Recording Limitations
| Criteria/Cluster/Profile | PSX | ERE |
|---|---|---|
| Call Recording Criteria (CRC) | There is no hard-coded limit on the number of CRC objects you can create. | Up to 128 CRC objects are allowed. |
| SRS Group Cluster (SRSGC) | Up to 256 SRSGC objects are allowed. | Up to 256 SRSGC objects are allowed. |
| SRS Group Profile (SRSGP) | Up to 256 SRSGP objects are allowed. | Up to 256 SRSGP objects are allowed. |
Maximum CLI Load Times
The following table lists the maximum CLI load times for the above profile classes.
| Configuration Profile | Maximum CLI Load Time |
|---|---|
| 1K | 2.5 hours |
4K | 4 hours |
| 4K/10K | 3 hours |
| 4/40K (7000 only) | 10 hours |
For a system previously loaded with configuration, the start-up time also depends on the amount of configuration. The start-up time is considered the time from when the SBC application is started (by PM) to the time that the SBC is ready to accept calls.
Note that this start-up time is typically only relevant to standalone systems after an upgrade. For a HA system, the standby is activated to handle calls while the SBC is being started or restarted.
Approximate Start-up Times for Standalone SBC
The following table lists the approximate start-up times for a standalone SBC based on its configuration profile:
| Configuration Profile | Maximum Time to Service Ready |
|---|---|
| No configuration | 5 minutes |
| 1K | 10 minutes |
| 4K | 20 minutes |
| 4K/10K | 22 minutes |
| 4K/40K (7000 only) | 45 minutes |
Overview
Content Tools