Cabling for Redundancy

Owned by Kelli Higdon
Last updated: Apr 01, 2024
3 min read

 

 

This topic provides an example of the following redundant cabling scenarios:

  • Redundant CTRL Interface

    • Redundant Data A0/A1 Interfaces

    • Redundant Data B0/B1 Interfaces

Redundant CTRL Interface

The diagram below displays the connections needed to cable the CTRL 0 and CTRL 1 interfaces to a Host for services such as DHCP, FTP and connecting to the Web GUI. The scenario in the diagram displays the CTRL 0 and CTRL 1 interfaces connected in a redundant fashion. If the CTRL 0 interface should fail for any reason, the CTRL 1 interface will take over. The CTRL 0 and CTRL 1 interfaces are both given the same IP address through either the dhcpd.conf or the bootup.cfg file, but the MAC addresses for each of the interfaces are different. The CTRL 1 MAC address is attained by adding 1 to the CTRL 0 address. Refer to the example below:

CTRL 0 MAC Address - 00:20:1C:11:22:33

CTRL 1 MAC Address - 00:20:1C:11:22:34

 

The CTRL interfaces can be used for network management functions, as well as IP signaling and RTP Media. Refer to table below.

Function

Description

Download System Software

The system software can be sent to the IMG 2020 using a DHCP Server. The software is sent from the DHCP Server to the IMG 2020 through the CTRL 0 or CTRL 1 interface.

SNTP

The IMG 2020 can acquire the time by communicating with a Time Server. The time is sent using NFS from the Time Server to the IMG 2020 through the CTRL 0 or CTRL 1 interface. The server that is configured for DHCP can also be used as a time server. This is accomplished by configuring an sntp.conf file and pointing it to a time server. Refer to the Configure SNTP topic for more information.

Treatments and Announcements

Treatments and announcements are sent to the IMG 2020 using the NFS protocol. The audio files are transferred to the IMG 2020 through the CTRL 0 or CTRL 1 interfaces

HTTP Upload

Files such signaling variants are loaded to the IMG 2020 through the CTRL 0 or CTRL 1 interfaces

Web GUI communication

The Web GUI uses HTTP to communicate with the IMG 2020. All communications between the Web GUI and the IMG 2020 are sent through the CTRL 0 or CTRL 1 interfaces. Routing tables, license files, translation tables, etc are all send through the CTRL 0 or CTRL 1 interfaces.

SIP Signaling

SIP Signaling can be configured to communicate through the CTRL 0 or CTRL 1 interfaces. The IP addresses used for signaling cannot be on the same subnet that was set up through the dhcpd.conf or bootup.cfg files.

RTP Data

RTP data such as voice can be configured to communicate through the CTRL 0 or CTRL 1 interfaces.

SNMP

SNMP data can be configured to communicate through the CTRL 0 or CTRL 1interfaces


Redundant Control for OAMP management, IP Signaling, and RTP Voice

 

Redundant Data A0/A1

 

The DATA A0 and DATA A1 can be utilized for both IP Signaling and RTP Media. The diagram below displays the cabling needed to connect the two interfaces in a redundant fashion. Using the Web GUI application, a shared IP address can be configured to communicate between the IMG 2020 and the IP network. These ports can be used for RTP streams or IP signaling. The following illustration shows cabling for redundant data:

 

Redundant Data B0/B1

 

The DATA B0 and DATA B1 can be utilized for both IP Signaling and RTP Media. The diagram below displays the cabling needed to connect the two interfaces in a redundant fashion. Using the Web GUI application, a shared IP address can be configured to communicate between the IMG 2020 and the IP network. These ports can be used for RTP streams or IP signaling. The following illustration shows cabling for redundant data:

 

SS7 Redundancy

 

For information on SS7 Redundancy, refer to the  SS7 Redundancy topics in the online webhelp documentation.

Return to Documentation Home I Return to Sangoma Support