Galaxy Expand - High Availability UCx Configuration

UCx High Availability Server Configuration

The Galaxy Expand is ideally suited for creating a High Availability solution through the use of redundant Server Cards. The chassis is always equipped with dual power supplies providing maximum protection against power outages, as the two power supplies can be connected to different power circuits. A High Availability deployment using Galaxy Expand requires the use of two separate chassis with a server card in each one.

Galaxy Expand Hardware Requirements

Required cards

When deployed as a High Availability Redundant Configuration (HARC) UCx server, the configuration requires two identical Galaxy Expand Server Cards. The choice of which Server card is based upon the number of extensions required or the number of simultaneous calls required for the call server.  The capacities of the server cards is described in Galaxy Expand - Platform Hardware.

Optional Cards

In a HARC system, all connecting equipment must use IP communication between the UCx and itself.  For this reason, only the Telephony interface cards using the Ethernet backplane can be used in the chassis.  As noted in Galaxy Expand - Platform Hardware, these cards include the DSM16, PRI, and FXS16 cards.  If a single chassis is used, these can be configured in any of the nine remaining slots. An additional server card can also be installed, but the third server card would be used as a standalone InfinityOne server, which is described later in this document. Note that for an all IP based configuration with only IP telephones and SIP trunks, no telephony cards are required. 
For details on how to configure the optional Telephony Interface Cards, refer to the following:

  1. DSM16 Card Configuration (Ethernet Enabled)
  2. PRI Card Configuration (Ethernet Enabled)
  3. FXS16 Card Configuration (Ethernet Enabled)

Server Card Network Connection and Configuration

Slot assignment for Required Cards

When deploying the Galaxy Expand as a High Availability UCx server, you will be required to install one of the selected Galaxy Expand Server Cards in either slot 2a, 7a, or 11a as noted in Galaxy Expand - Platform Hardware. When the single slot 2930 Call Server card is used the corresponding "b" slot for that location should be covered with a blank card slot cover. The 2930 Server card in the second chassis can be installed in any of the server cards slots.

Recommended IP Addressing - 2930 Server Card

When using a Galaxy Expand 2930 Server Card, there is only a single "customer facing" ethernet interface.  As with all UCx software, the default value for the IP address of the ETH interface on the server card is 192.168.1.200.  However, as documented in the High Availability - Installation and Configuration, this address should be be changed so that the default UCx address can be used as the Cluster IP Address. In the example below eth0 in the UCx software on one of the two server cards has been configured as 192.168.1.201 and should be connected to the customer LAN. All configuration of the 2930 Server Card parameters should be done in accordance with the UCx Network Parameters documentation.  The eth0 interface on the second server card should also be changed from the default value; in the example it is set to 192.168.1.202 and should also be connected to the customer LAN. A third address will be configured per the High Availability - Installation and Configuration documentation, as is shown as 192.168.1.200.

The Galaxy Expand chassis backplane ethernet network will be identified in the UCx software as eth2. The E-MetroTel recommended addressing for this interface on the first chassis is 192.168.11.201 with a subnet mask of 255.255.255.0 for consistency with the Primary Server address. The DHCP Server in the UCx software on one server card should be set to Active during the initial configuration of the two chassis units in order to allow any PRI, DSM16P and FXS16 cards to acquire an address via DHCP. However, once the the cards have been configured, the cards should be assigned static IP addresses in the same subnet but outside of the defined DHCP range, so that they can be accessed by either of the two server cards via the backplane ethernet network. If the address range conflicts with your network addressing, following the instructions in the UCx DHCP Server documentation. 

Note that the second Galaxy Expand Server Card should have DHCP Server disabled prior to connecting the two chassis to avoid potential addressing conflicts.

GEStandaloneServer.png

Recommended IP Addressing - i5 Server Card

The IP Addressing scheme identified above for the 2930 Server card should be used as the baseline configuration for High Availability configuration using the Galaxy Expand i5 Server Card.  However, the i5 Server Card has an additional Ethernet interface on the front panel.  This second ethernet connector should be configured on a distinct subnet.  The default value of the card eth1 address is 192.168.10.200 when in a standalone configuration, but E-MetroTel recommends changing the eth1 to correspond with the eth0 interfaces on each card, so for this example they would be configured as 192.168.10.201 and 192.168.10.202, respectively.

GE_HARC_i5.png

Page Tags: 
fxo
fxs
Galaxy
Expand
harc