Table of Contents INTRODUCTION ..........................6 TYPICAL NETWORK TOPOLOGY .................. 7 HA PREREQUISITES ....................... 8 Prerequisites .................................. 8 Connecting FCM for HA Setup ............................ 8 Network Configuration ..............................8 HA CONFIGURATIONS ....................10 HA CONFIGURATION PARAMETERS ................15 VERIFY HA SETTINGS ....................21 ACTIVE/STANDBY ROLE IN HA ..................
Page 3
Table of Figures Figure 1: Typical Network Topology ........................... 4 Figure 2: Network Settings ............................6 Figure 3: HA Settings on Primary FCM ........................7 Figure 4: HA Settings on Secondary FCM ........................ 8 Figure 5: HA Configured on Secondary FCM ......................9 Figure 6: HA Status on Secondary FCM ........................
INTRODUCTION High Availability feature on FIBERME FCM630A provides enterprises a reliable solution for PBX redundancy and failover support. In HA setup, there are two FCM with one FCM in “active” role and the other in “standby” role. The two FCM must be the same model and use the same firmware version. The data on the active FCM will be synchronized to the standby FCM in real-time manner and the standby FCM monitors active FCM’s running status regularly.
TYPICAL NETWORK TOPOLOGY Figure 1: Typical Network Topology The two FCM in High Availability setup must be deployed in the same location and connected directly to each other via heartbeat port on each FCM. The primary FCM and secondary FCM can be connected to each other via a straight-through Ethernet cable on the heartbeat port.
HA PREREQUISITES Prerequisites The two FCM used for High Availability deployment must be the same model and use the same firmware version to ensure proper sync-up on the configuration and data. Connecting FCM for HA Setup The two FCM in High Availability setup must be deployed in the same location and connected directly to each other via heartbeat port on each FCM.
HA CONFIGURATIONS For two new FCM on factory default setting, system admin can choose to configure any of them for HA first. However, if one of the FCM is already configured, up and running for PBX service, system admin should configure this FCM as HA Primary server and complete all HA settings on it first so it can act as active role.
4. Verify HA status on FCM A. Log in FCM A using its static IP and admin login information. On web UI→System Settings→HA page, ensure HA function is enabled. HA status should display “Active”. 5. After ensuring FCM A’s HA status as active, configure FCM B as secondary FCM and complete FCM B’s HA settings.
HA CONFIGURATION PARAMETERS Table 1: HA Related Parameters Value Default Settings Description Notes Range Value High Available Enable or disable HA. Yes/No Enable Caution: Please do not use this Force to switch the roles of function unless necessary Force Switch active FCM and standby (e.g., it can be used during FCM.
Page 12
If the standby FCM detects the This is the heartbeat active FCM disconnected, when Heartbeat timeout period that active it reaches the timeout, failover Timeout and standby FCM will 3 - 10 will be triggered and the standby Period (s) check with each other for FCM will start taking over as the status (in seconds).
Page 13
• HA Cluster IP (mandatory): This is the IP address for the FCM that provides PBX service in HA setup. This IP is always associated with the FCM in active status. For example, when configuring IP phone to register to FCM, this is the SIP server IP address to be configured on the IP phone.
VERIFY HA SETTINGS 1. After configuring HA settings on both FCM, log in the FCM web UI from each FCM’s static IP using the active FCM’s login information and check HA status. Under HA status page, both FCM should show HA Status as “Dual”. One of the FCM should show its role as “Active” and the other one should show “Standby”.
ACTIVE/STANDBY ROLE IN HA Automatic Failure Detection Figure 9: Active and Standby FCM Failover Active FCM: Self-Failure Detection The active FCM monitors and regularly checks whether there is any failure on itself. When there is failure detected on itself, it will notify the standby FCM to take over as active server. Then the original active FCM will reboot automatically and become the standby server.
Standby FCM: Periodic Heartbeat On HA mode, the standby FCM will check the active FCM’s status periodically by sending heartbeat message to the active FCM. The heartbeat message is sent via the heartbeat port. If the active FCM is under normal working condition, it will respond to the standby FCM after it receives heartbeat request from the standby FCM.
FIRMWARE UPGRADE To ensure that there is no service interruption in HA setup, upgrading FCM requires user to follow below steps strictly: Step 1: Log in the web UI of the standby FCM (A), upload firmware via web UI and the standby FCM will reboot.
REPLACING FCM IN HA Assuming 2 FCM (A and B) in HA setup, FCM A is in active status and FCM B is in standby status. FCM B becomes defective and requires replacement. Please follow the steps below to replace the defective FCM B with FCM C: 1.
SERVICE STATUS Active/Standby Status After HA setup is completed, the PBX will provide service using the HA cluster IP. During initial stage, standby FCM will request and synchronize up all data from the active FCM. The standby FCM monitors and prepares to become active at any time when needed. Manual configuration on standby FCM is restricted because it always synchronizes up data from active FCM.
FAILOVER DURING CALL When the active server encounters failure, if there is ongoing call on the active server, the switchover process will only cause a few seconds of audio cutoff and then it will be recovered automatically. Notes: • Currently, if the call is using UDP as transport method, the call can be recovered after switchover.
MAINTENANCE In HA setup, system admin can check HA related alerts under FCM web UI’s system events page to learn if there is any abnormal event related to HA. According to the alerts, admin can further diagnose by checking the event time and logs with more details. Figure 11: System Alert Events HA log also shows all HA backup and failover logs.
Need help?
Do you have a question about the FCM630A Series and is the answer not in the manual?
Questions and answers