Page History

Panel
In this section: Table of Contents maxLevel 4

 

Number of IP Addresses per Call Leg Size

The table below defines the number of

Spacevars
0 series2

call legs supported for a given number of IP Addresses assuming UDP ports 4,000 through 64,444 are configured for media port usage.

For 

Spacevars
0 series2

media resource allocation scenarios, the 

Spacevars
0 product

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).

Caption
0 Table 1 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 you must configure at least six (6) IP addresses because five IP addresses will only allow up to 96,000 call legs through the

Spacevars
0 product

.

The  

Spacevars
0 series4

supports configuring up to 14 alternate media addresses. For more details, see Alternate Media IP Addresses Support.

Configuration Limits

The 

Spacevars
0 series2

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 1st such instance.

Note
title 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

Spacevars
0 series4

provisioning limits are shown in the following table.

series4 supports up to 512 SIP Adaptor Profiles.

Info
title Info
The term '5xx0' represents SBC models 5100, 5200, 5110 and 5210.
Info
title Note
The
Spacevars
0

Caption
0 Table 1 SBC Provisioning Limits
Configuration Objects Provisioning Limits   SBC 7000   SBC 5400   SBC 5xx0 SBC SWe VM  Memory >= 10 GiB RAM ("small" profile) VM  Memory ≥ 18 GiB RAM ("large" profile) Address Contexts 4,000 2,048 2,048 129 700 SIP Signaling Ports 4,000 2,048 2,048 129 700 H.323 Signaling Ports 2,048 2,048 2,048 129 129 SIP Trunk Groups 40,000 20,000 10,000 1,024 5,000 H.323 Trunk Groups 2,048 2,048 2,048 129 256 Gateway Trunks 128 128 128     Maximum IP Trunk Groups of All Signaling Types 40,000 20,000 10,000 1,024 5,000 Zones 4,000 2,048 2,048 129 700 DNS Groups 2,048 2,048 2,048 129 129 IP Interfaces 4,000 4,000 4,000 129 2,048 IP Interfaces Groups 4,000 2,048 2,048 129 1,024 IP Peers 40,000 20,000 10,000 1,024 5,000 Alternate Media IP Addresses (per LIF) 254 254 254 129 129 IP Addresses 8,192   4,096     IP ACLs 50,0001 25,0002 17,8242  1,8003 2,8004 Dynamic Black List Entries 4,000 2,000 1,000  100 100 Enhanced DBL Profiles 100 SIP Adaptor Profiles 512 512 512 256 256 Tone Package Profiles 2,048 Surrogate Registration Profiles AoRs for Surrogate Registrations 256 10,000 SWe Traffic Profiles Refer to SBC SWe Traffic Profiles for details.   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.

Info
title Info
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. 

Note
title Caution
See cautionary note above about the potential bulk configuration loading on call handling performance.

While the 

Spacevars
0 series2

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

Spacevars
0 series4

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
title 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.

Maximum CLI Load Times

The following table lists the maximum CLI load times for the above profile classes.

Caption
0 Table 1 Maximum CLI Load Times 3 Maximum CLI Load Times
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

Spacevars
0 product

application is started (by PM) to the time that the

Spacevars
0 product

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

Spacevars
0 product

based on its configuration profile:

Caption
0 Table 1 Approximate Start-up Times for Standalone SBC
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

Pagebreak