Page History
...
| Panel |
|---|
...
| borderColor | green |
|---|---|
| bgColor | transparent |
| borderWidth | 2 |
...
Back to Installing SBC SWe on Virtual Platforms
In this section:
|
Creating a SBC SWe IP Plan
| Div | ||||
|---|---|---|---|---|
| ||||
Prior to installing the |
...
|
...
VMware or KVM Host. Create an IP Plan prior to installing the |
...
The following tables provide example |
...
|
Create an IP Plan prior to installing the
...
| Spacevars | ||
|---|---|---|
|
...
| Spacevars | ||
|---|---|---|
|
| Note |
|---|
| If needed, please contact Sonus for an example IP Plan. |
Example IP Plan Information
The following example is for a redundant High Availability (HA) configuration with one standby
...
| Spacevars | ||
|---|---|---|
|
...
| Spacevars | ||
|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
Click here to download sample spreadsheet.
SBC SWe System Information | Description | Example/Recommendation |
|---|
...
| This is the name of the overall |
...
If external routing is used, the system name is referred to by the PSX. You MUST use the same name on the Active and Standby system installation. | DALVSBC01 | ||||
| Local Host/Node name (ceName) | Name of the primary server. Typical naming convention is "<system name>a". A best practice is to include the "a" suffix even for stand-alone systems to facilitate easy upgrade to HA in the future. | DALVSBC01a | |||
| Peer Host/Node name (ceName) | (HA only) Name of the secondary server. Typical naming convention is "<system name>b". | DALVSBC01b, or none | |||
| Server Role | Specifies the role of the |
...
| Active/Standby | ||||
| Time zone | The time zone used in your billing records. Can be the time zone of the location of the SBC system.
| gmtMinus06-Central- US |
...
| Contact name and phone number to use for physical support. | Joe Smith 888-555-1212 |
...
| Physical location of the system. | Dallas, TX | ||||
| NTP Primary IP Address | The primary IPv4 or IPv6 address of the NTP server. A NTP source is necessary for correct system operation. | 10.11.12.2/24 or fd00:10:6b50:4130:1 | ||||
| NTP Secondary IP Address | The optional secondary IPv4 or IPv6 address of the NTP server. | 10.11.12.3/24 or fd00:10:6b50:4130:2 | ||||
| TIPC NETID | Specifies unique Transparent Inter-process Communication (TIPC) network communications protocol network identity. This network identity must be same in both active and standby VMs for inter-process communication. Recommendation is to use default value when configured for single HA pair on HA subnet (subnet for HA ports of active/standby).
| 1500 (default) | ||||
| Logical Management IP Address | This IP address can be used to access the active unit, it is not tied to a particular physical unit. When a unit becomes active, this IP address “moves” to that unit. Logical management IP address should be from same subnet as the physical management IPs. | 10.11.13.3 (or any IP address within the Management IP subnet) | ||||
| Logical Management IP Address Name | The name of the Logical Management IP (used for reference purposes only). | DALNBS01_MGMT | ||||
|
| |||||
|---|---|---|---|---|---|---|
| Packet Ports | ||||||
| Packet Port 0 IP Address | The IP address of the pkt0 interface. SIP and RTP traffic use this physical interface. This IP address is used for RTP traffic (SIP traffic uses a different IP address). | 10.11.14.1 | ||||
| Packet Port 0 VLAN | The VLAN tag of the pkt0 interface (optional). | 100 | ||||
| Packet Port 0 Netmask | The Netmask of the pkt0 interface (in “prefix” format). | /24 | ||||
| Packet Port 1 IP Address | The IP address of the pkt1 interface. SIP and RTP traffic use this physical interface. This IP address is used for RTP traffic (SIP traffic uses a different IP address). | 10.11.15.1 | ||||
| Packet Port 1 VLAN | The VLAN tag of the pkt1 interface (optional). | 200 | ||||
| Packet Port 1 Netmask | The Netmask of the pkt1 interface (in “prefix” format). | /24 | ||||
HA Ports (not applicable for stand-alone configuration) | ||||||
| ||||||
...
| |||||||
| Active CE IP | Specifies the active VM IP address in HA pair. The Active CE uses this IP which is configured to the HA port to communicate/synchronize/mirror the data with the Standby CE. These Inter CE IP addresses should be in a different network from the management network. Recommendation is to use default value when configured for single HA pair on HA subnet (subnet for HA ports of active/standby). | 169.254.99.1 (default)
| |||||
| Standby CE IP | Specifies the standby VM IP address in HA pair. The Standby CE uses this IP which is configured to the HA port to communicate/synchronize/mirror the data with the Active CE. These Inter CE IP addresses should be in a different network from the management network. Recommendation is to use default value when configured for single HA pair on HA subnet (subnet for HA ports of active/standby). | 169.254.88.1 (default) | |||||
| HA Interface Mask (Inter CE Prefix) | Netmask of the network in which the Active/Standby IPs are configured.
| 255.255.0.0 (default) | |||||
| Management Ports | |||||||
| |||||||
| Primary Management IPv4 Address | This specifies the physical management IPv4 address associated with the primary management network. | 10.11.13.10 | |||||
| Primary Management Network Mask | This specifies the Netmask of the primary management network. | 255.255.255.0 | |||||
Primary Management Gateway IPv4 Address | This specifies the default gateway IPv4 address associated with the primary management network. | 10.11.13.1 | |||||
| Primary Management IPv6 Address | This specifies the physical management IPv6 address associated with the primary management network. | fd00:10:6b50:4300::10b | |||||
| Primary Management IPv6 Prefix Length (0-128) | This specifies the prefix of the primary management network. | 60 | |||||
| Primary Management Gateway IPv6 Address | This specifies the default gateway IPv6 address associated with the primary management network. | fd00:10:6b50:4300::1 | |||||
| Pagebreak |
|---|
...
Overview
Content Tools