Versions Compared

Key

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

...

Spacevars
0series4
provisioning limits are shown in the following table.

Note

A minimum of 9 GB RAM is required to support the below SBC SWe configuration.

Caption
0Table
1SBC Provisioning Limits
  

Configuration Objects

Provisioning Limits
 SBC 7000 SeriesSBC 5000 SeriesSBC SWe6
   VM 10-13 VM  Memory < 14 GB RAMVM VM  Memory >= 14 + GB RAM
Address Contexts4,0962,048128700
SIP Signaling Ports4,0962,048128700
H.323 Signaling Ports2,0482,048128128
SIP Trunk Groups

40,0001

10,0002

1281,400
H.323 Trunk Groups

2,0481

2,0482

128256
Gateway Trunks

1281

   
Zones4,0962,048128700
DNS Groups2,048512128128
IP Interfaces4,0964,0961282,048
IP Interfaces Groups4,0962,0481281,024
Alternate Media IP Addresses
(per LIF)
25425425452545
IP Addresses8,1924,096  
IP ACLs50,000316,0004 18002,800
Dynamic Black List Entries4,096  100128100

Footnotes

1 - The aggregate number of IP trunk groups (SIP + GW + H.323) cannot exceed 40,000. As a best practice, do not provision more than 20,000 trunk groups in a single zone.

2 - The aggregate number of IP trunk groups (SIP + GW + H.323) cannot exceed 10,000.

3 - Includes approximately 40,000 IP ACLs for peers, 10,000 IP ACLs for signaling ports (2 x 4,000 SIP, 2,000 H323) and 100 IP ACLs for OAM.

4 - Includes approximately 10,000 IP ACLs for peers, 4,000 IP ACLs for signaling ports and 100 IP ACLs for OAM.

5 - SBC SWe supports a maximum of 64 alternate media IP addresses per vNIC.6 - SBC SWe supports up to 1,000 G711 pass-through calls along with this configuration.

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. 

...