Versions Compared

Key

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

In this section:

Table of Contents
maxLevel3

Creating a SBC SWe IP Plan

 

div
stylepadding-left:0%;
idindent

Prior to installing the

Spacevars
0product2
you need to have some information on hand to define the VM's communication interfaces and network configuration on the VMware or KVM Host. Create an IP Plan prior to installing the
Spacevars
0product2
software. It is important to record the IP information so that your system information is readily available when you begin installing the software. Maintain this information as a reference for future configuration changes.

Info
titleNote

Three management IP addresses are required for configuration of the VM management network: an IP address is required for each VM, and a shared IP address is used by both VMs, depending on required network connections. 

The following tables provide example

Spacevars
0product
IP plan information. The following table shows an example of IP information needed for the VMware or KVM Host.

Caption
0Table
1Installation IP Checklist for VMware or KVM Host
Parameter

Example

Primary network interface name (Host subnet - physical port)eth0
Host namenorwayxxx01
IP address of the Host subnet (Host Management interface)10.9.9.103
Default router10.9.9.1
Netmask of subnet255.255.255.0

 

Create an IP Plan prior to installing the

Spacevars
0product2
 software. The IP Plan is generally completed using an Excel spreadsheet, and is intended to capture information such as hostname, logical IP addresses, and so forth to help configure the
Spacevars
0product2
 system. It is important to complete this document (even for simple networks) so your system information is readily available when you begin installing the software, and to maintain this information as a reference for future configuration changes.

Info
titleNote

If needed, please contact

Spacevars
0company
for an example IP Plan. 

 

Example IP Plan Information

The following example is for a redundant High Availability (HA) configuration with one standby

Spacevars
0product
 Virtual Machine protecting the active
Spacevars
0product
 Virtual Machine.

Include Page
IP_for_MGMT_and_Media_on_diff_subnets
IP_for_MGMT_and_Media_on_diff_subnets

 

Click 

Noprint

Click here to download sample spreadsheet.


SBC SWe System Information

Description

Example/Recommendation
Spacevars
0product
System Name

This is the name of the overall

Spacevars
0product
system, and is used as the designation of all servers within HA pair. See System Name and Hostname Conventions for naming conventions.

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 RoleSpecifies the role of the
Spacevars
0product
VM.

Active/Standby

Time zone

The time zone used in your billing records. Can be the time zone of the location of the SBC system.

Info

Changing the time zone will cause the application to restart.

gmtMinus06-Central- US
Spacevars
0product2
System Contact
Contact name and phone number to use for physical support.Joe Smith 888-555-1212
Spacevars
0product2
System Location
Physical location of the system.Dallas, TX
NTP Primary IP AddressThe 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 AddressThe 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).

Info

TIPC NETID must be unique for a given HA pair in any given cluster.

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 NameThe name of the Logical Management IP (used for reference purposes only).DALNBS01_MGMT


Unit A and Unit B Information


Configure these details on Unit A only (IP address information moves from Unit A to B on a fail-over)

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 VLANThe VLAN tag of the pkt0 interface (optional).100
Packet Port 0 NetmaskThe Netmask of the pkt0 interface (in “prefix” format)./24
Packet Port 1 IP AddressThe 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 VLANThe VLAN tag of the pkt1 interface (optional).200
Packet Port 1 NetmaskThe Netmask of the pkt1 interface (in “prefix” format)./24

HA Ports (not applicable for stand-alone configuration)

Info

The HA ports of active and standby

Spacevars
0product
nodes should be on the same subnet when the boxes are not directly connected.

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)

Active and Standby CE IP addresses must be in the same subnet.

 

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.

Info

If default Active and Standby CE IP addresses are not used, use Inter CE prefix as '255.255.255.0'.

255.255.0.0 (default)
Management Ports
Info

The configuration of the IP management interface is performed as part of the initial-bootscript, and is not meant to be re-configured through the EMA. Each SBC SWe has a redundant pair of physical ports for managing traffic.

Primary Management IPv4 AddressThis specifies the physical management IPv4 address associated with the primary management network.10.11.13.10
Primary Management Network MaskThis 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 AddressThis 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 AddressThis specifies the default gateway IPv6 address associated with the primary management network.fd00:10:6b50:4300::1

 

Pagebreak