Skip to end of metadata
Go to start of metadata

 

Once the SBC 5400 hardware is successfully installed, install the SBC 5400 application software. As part of this installation, you are prompted for configuration information by the EMA platform mode.

Create an IP Plan prior to installing the 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 SBC 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.

If required, contact Sonus support team for an example IP Plan.

The steps for installing the application are included in section SBC 5400 - Installing Application.

Example IP Plan Details

The following example is for a redundant High Availability (HA) configuration with one standby SBC protecting the active SBC.

Caution

Ensure the Management and Media IP addresses are on different subnets to avoid potential conflicts.

Click here to download an example spreadsheet.

FieldDescriptionExample/Recommendation
System Name

This is the name of the overall SBC system, and is used as the designation of all servers within HA pair. See SBC 5400 - 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.

DALSBC01
Time zone

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

Note: changing the time zone will cause the application to restart.

gmtMinus06-Central- US
Contact InformationWho to contact about the system

Joe Smith 888-555-1212

LocationLocation of the systemDallas, TX
NTP PrimaryThe IP 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 SecondaryThe IP address of the NTP server. A NTP source is necessary for correct system operation.10.11.12.3/24
or
fd00:10:6b50:4130:2
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.

10.11.13.3
(or any IP address within the Management IP subnet)
Logical Management IP Address - NameThe name (used of reference only) of the Logical Management IPDALNBS01_MGMT
Unit A and Unit B:Configure on Unit A only (IP address moves from one Unit to the other on a fail over) 
Packet Ports
Packet Port 0 IP Address

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

Packet Port 2 IP Address

The IP address of the 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.16.1

Packet Port 2 VLAN

The VLAN tag of the interface. This is optional.300

Packet Port 2 Netmask

The Netmask of the interface (in “prefix” format)./24

Packet Port 3 IP Address

The IP address of the 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.17.1

Packet Port 3 VLAN

The VLAN tag of the interface. This is optional.400

Packet Port 3 Netmask

The Netmask of the interface (in “prefix” format)./24

HA Ports (not applicable for stand-alone configuration)

The HA ports of active and standby SBC 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.

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

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.

Management Interface0 IPv4 addressThe physical management IPv4 address10.11.13.10
Management Interface0 IPv4 Address PrefixIP Prefix of the network configured on the Active management IPv424

Management Interface0 IPv4
(Default Gateway)

The Default Gateway IPv4 address connected to the Active management interface

10.11.13.1

Management Interface0 IPv6 addressThe physical management IPv6 addressfd00:10:6b50:4150::23
Management Interface0 IPv6 Address PrefixIP Prefix of the network configured on the Active management IPv664
Management Interface0 IPv6
(Default Gateway)
The Default Gateway IPv6 address connected to the Active management interfacefd00:10:6b50:4150::1
Management Interface1 IPv4 addressThe physical management IPv4 address10.12.13.10
Management Interface1 IPv4 Address PrefixIP Prefix of the network configured on the Active management IPv424
Management Interface1 IPv4
(Default Gateway)
The Default Gateway IPv4 address connected to the Active management interface10.12.13.1
Management Interface1 IPv6 addressThe physical management IPv6 addressfd00:10:6b50:4160::23
Management Interface1 IPv6 Address PrefixIP Prefix of the network configured on the Active management IPv664
Management Interface1 IPv6
(Default Gateway)
The Default Gateway IPv6 address connected to the Active management interfacefd00:10:6b50:4160::1
Management Interface2 IPv4 addressThe physical management IPv4 address10.13.13.10
Management Interface2 IPv4 Address PrefixIP Prefix of the network configured on the Active management IPv424

Management Interface2 IPv4
(Default Gateway)

The Default Gateway IPv4 address connected to the Active management interface10.13.13.1
Management Interface2 IPv6 addressThe physical management IPv6 addressfd00:10:6b50:4250::23
Management Interface2 IPv6 Address PrefixIP Prefix of the network configured on the Active management IPv664

Management Interface2 IPv6
(Default Gateway)

The Default Gateway IPv6 address connected to the Active management interfacefd00:10:6b50:4250::1
Management Interface3 IPv4 addressThe physical management IPv4 address10.14.13.10
Management Interface3 IPv4 Address PrefixIP Prefix of the network configured on the Active management IPv424

Management Interface3 IPv4
(Default Gateway)

The Default Gateway IPv4 address connected to the Active management interface10.14.13.1
Management Interface3 IPv6 addressThe physical management IPv6 addressfd00:10:6b50:4270::23
Management Interface3 IPv6 Address PrefixIP Prefix of the network configured on the Active management IPv664

Management Interface3 IPv6
(Default Gateway)

The Default Gateway IPv4 address connected to the Active management interfacefd00:10:6b50:4270::1

 

  • No labels