Versions Compared

Old Version 31

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1ghoppeUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
JIRAIDAUTHSBX-71854106599
REV5ghoppeUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6ghoppeUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3sashuklaUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ced70cb1, userName='null'}
REV1dkumarUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ced70cb1, userName='null'}



Panel

In this section:

Table of Contents
maxLevel4

 


Number of IP Addresses per Call Leg Size

The table below defines the number of

Spacevars
0series2
call legs supported for a given number of IP Addresses on different SBC platforms are as follows:

  • Spacevars
    0series2
    , assuming UDP ports 4,000 through 64,444 are configured for media port usage - See table below.
  • Spacevars
    0model5
     with 10GE interfaces - Supports a maximum of 75000 sessions, requiring 4 IP addresses per call leg.
  • Spacevars
    0product2
    - Supports a maximum of 64000 sessions, requiring 3 IP addresses per call leg.

Anchor
7000table
7000table
For 
Spacevars
0series2
media resource allocation scenarios, the 
Spacevars
0product
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
0Table
1Number of IP Addresses Needed to Support Call Legs


Number of Call LegsNumber of IP
Addresses
150,00010
140,0009
130,0008
120,0007
110,0006
96,0005
80,0004
64,0003
45,0002
25,0001


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
0product
.

The  

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

Configuration Limits

The 

Spacevars
0series2
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
titleCaution

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
0series4
provisioning limits are shown in the following table.

0 supports up to 512 SIP Adaptor Profiles.

Info
titleInfo

 The term '5xx0' represents SBC models 5100, 5200, 5110 and 5210.

Info
titleNote

The

Spacevars
series4


 

 
Caption
0Table
1SBC Provisioning Limits




Configuration Objects

Provisioning Limits

 


SBC 7000

 


SBC 5400

 


SBC 5xx0

SBC SWe
VM  Memory
< 18
>= 10 GiB RAM
("small" profile)		VM  Memory ≥ 18 GiB RAM
("large" profile)
Address Contexts4,0002,0482,048
128
129
700
1,024
SIP Signaling Ports4,0002,0482,048
128
129
700
1,024
H.323 Signaling Ports2,0482,0482,048
128
129
128
129
SIP Trunk Groups

40,000

20,000

10,000

128
1,024
1
5,
656
000
H.323 Trunk Groups

2,048

2,048

2,048

128
129256
Gateway Trunks

128

128128
 
 


Maximum IP Trunk Groups
of All Signaling Types		40,00020,00010,000
128
1,024
1
5,
656
000
Zones4,0002,0482,048
128
129700
DNS Groups2,0482,0482,048
128
129
128
129
IP Interfaces4,0004,0004,000
128
1292,048
IP Interfaces Groups4,0002,0482,048
128
1291,024
IP Peers40,00020,00010,000
128
1,024
1
5,
656
000
Alternate Media IP Addresses
(per LIF)		254254254254
3
1283

254

IP Addresses8,192
 

4,096
  


IP ACLs50,000125,000217,8242 1,800
4
32,800
5
4
Dynamic Black List Entries4,0002,0001,000 100100
Enhanced DBL Profiles100
SIP Adaptor Profiles512512512256256
Tone Package Profiles2,048

Surrogate Registration Profiles

AoRs for Surrogate Registrations

256

10,000

 
SWe Traffic ProfilesRefer to SBC SWe Traffic Profiles for details.5


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 - SBC SWe supports a maximum of 64 alternate media IP addresses per vNICThe number of user-defined ACLs is 772.

4 - The number of user-defined ACLs is 772628.

5 - The number of user-defined ACLs is 628.maximum VLANs supported on SR-IOV VF interface is 64, limiting the maximum number of IP interfaces on the SBC VM with an SR-IOV packet interface to 64. 


Info
titleInfo

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
titleCaution

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

While the 

Spacevars
0series2
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
0series4
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
titleNote

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


Configuration ProfileMaximum CLI Load Time
1K2.5 hours

4K

4 hours
4K/10K3 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
0product
application is started (by PM) to the time that the
Spacevars
0product
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
0product
based on its configuration profile:

Caption
0Table
1Approximate Start-up Times for Standalone SBC


Configuration ProfileMaximum Time
to Service Ready
No configuration5 minutes
1K10 minutes
4K20 minutes
4K/10K22 minutes
4K/40K (7000 only)45 minutes

Pagebreak



OpenStack Cloud Configuration Elements

The following table presents the number of elements that can be configured in an OpenStack environment.

Caption
0Table
1OpenStack Cloud Configuration


Configuration NameNumber of Elements

Address Contexts

149

SIP Signaling Ports

138

SIP Trunk Groups

5,000

Zones

150

IP Interfaces

150

IP Interface Groups

150

IP ACLs

148

IP-Peer

5,000

VLAN70


 


Pagebreak