Grandstream Networks UCM630x/A User Manual
  1. Manuals
  2. Brands
  3. Grandstream Networks Manuals
  4. Network Hardware
  5. UCM630x/A
  6. User manual
Grandstream Networks UCM630x/A User Manual

Grandstream Networks UCM630x/A User Manual

Hide thumbs

Advertisement

Table of Contents

UCM630x/A – High Availability User Guide: Remote Disaster Recovery
OVERVIEW
A remote disaster recovery site refers to a separate location from the main site where the primary server is, and the secondary server in the remote
disaster recovery site is used for backing up data and recovering the service when the main location with primary server has any unexpected events
such as natural disaster causing service interruption. High availability remote disaster recovery feature on UCM6300/UCM6300A series provides
reliability and redundancy for deployment when the primary server has hardware failure, power outage, network outage or other disaster events.
To use remote disaster recovery feature, the primary UCM and secondary UCM must be the same model using the same firmware version. The UCM
providing service is in "active" role while the other UCM is in "standby" role. The data on active UCM is synced to the standby UCM in real-time
manner. The standby UCM always monitors active UCM. If the active UCM has failure, the standby UCM will take over and become active to ensure
the service is not interrupted.
Notes
1. The UCM63xx remote disaster recovery feature requires using Grandstream endpoints in the deployment. 3 party end points may not be fully
supported in UCM's HA remote disaster recovery scenario.
2. If Grandstream Wave application is used with UCMRC plan of UCM63xx, only Wave clients registered from external network can be supported in UCM's
HA remote disaster recovery scenario. Wave clients registered to UCM from the same LAN is not supported for recovery.
DEFINITIONS
Primary/Secondary：
The high availability remote disaster recovery sites have two types of UCM: primary and secondary. The UCM HA type doesn't change while the roles
of the UCM can change between "active" and "standby".
In HA scenario, the primary UCM has higher chance to be in "active" role. Therefore, if enabling remote disaster recovery on UCMs, please make sure
to configure the current UCM providing PBX service at the main site as type "Primary" and configure the backup failover UCM at the recovery site to
be "Secondary".
Active/Standby：
The HA remote disaster recovery involves two roles for the UCMs:
Active: this is for the UCM currently providing all PBX service.
Standby: this is for the backup UCM.
Please note "primary" UCM can be different from "active" UCM, "secondary" UCM can be different from "standby" UCM. The UCM can switch
between active role and standby role. However, the UCM always has the same type (primary or secondary) as configured on the UCM webUI.
rd

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the UCM630x/A and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Grandstream Networks UCM630x/A

Summary of Contents for Grandstream Networks UCM630x/A

  • Page 1 UCM630x/A – High Availability User Guide: Remote Disaster Recovery OVERVIEW A remote disaster recovery site refers to a separate location from the main site where the primary server is, and the secondary server in the remote disaster recovery site is used for backing up data and recovering the service when the main location with primary server has any unexpected events such as natural disaster causing service interruption.
  • Page 2 REMOTE DISASTER RECOVERY DEPLOYMENT TOPOLOGY Typical Topology for Remote Disaster Recovery Scenario The primary UCM and secondary UCM are deployed in server rooms in two separate locations. The two locations have network connecting all the devices between them. The end devices in the company LAN network register to the UCM using domain name via DNS SRV. The DNS server in the LAN network returns two servers with priority assigned.

  • Page 3: Hardware Requirements

    1. Both UCMs must be the same model. 2. Both UCMs must use the same firmware version. Hardware Requirements For end devices registered to the UCMs in remote disaster recovery deployment, only Grandstream end devices are fully supported for service recovery.
  • Page 4 8989 Data sync port File sync port 9292 Data sync port 8796 Data sync port Storage Device Requirements Before enabling HA remote disaster recovery, please check and ensure the two UCMs have the same type of external storage devices plugged in. For example, if UCM A has a SD card and a USB flash drive plugged in, UCM B must have a SD card and a USB flash drive with the exact same type and storage size.
  • Page 5 2. If one of the UCM is already deployed and providing PBX service, please use this UCM as UCM A. 2. If Cloud IM service is used, please enable Cloud IM on UCM A and ensure Cloud IM is turned off on UCM B. 3.
  • Page 6 HA Settings on UCM B After UCM B boots up, please verify the HA status on UCM B by logging in UCM B’s web UI via its IP address with UCM A’s admin credentials. Go to UCM web UI->System Settings->HA->HA Settings, it should show HA enabled with the Force Switch “Switch” button in grey (unavailable). Only HA heartbeat related settings, peer heartbeat IP and MAC address configurations are available for configuration.
  • Page 7 HA Configuration Parameters For Remote Disaster Recovery Please configure HA parameters and deploy HA when the UCM is not in service period to avoid service interruption. Table 1: HA Parameters Parameter Description Value Range Default Value Note High Available Enable or disable HA function Yes/No Enable Configure HA mode.
  • Page 8 Recovery Peer UCM for HA remote disaster recovery MAC Address deployment. The heartbeat port is configurable but it’s The port used for heartbeat suggested to keep the default value to Heartbeat Port communications between the active and 0 to 65535 9527 avoid misconfiguration issues.
  • Page 9 2. Make sure both UCMs have the same UCMRC plan with HA supported. If UCM A already has the UCMRC plan, then you just need to purchase UCMRC plan for UCM B. It’s OK if one of the UCM has the UCMRC plan purchased later than the other one. 3.
  • Page 10 Edit Device->Custom Server Address Example Please notify UCM users with the new server address so they can use it. For more details on how to configure custom server address, please refer to the GDMS user guide. Verify HA Status 1. After configurating HA on both UCMs, please use each UCM’s IP address to open UCM’s webUI and log in using the active UCM’s login credentials.
  • Page 11 HA Status for a Standby UCM 2. Log in the web UI of the active UCM and create an extension. Then log in the web UI of the standby UCM to check extension page. You should be able to see the same extension created on the standby UCM automatically. This indicates the standby UCM has synced up from the active UCM and the HA configuration is successful.

  • Page 12: Manual Switchover

    Standby UCM Heartbeat Detection In HA deployment, the standby UCM will check the active UCM’s status periodically. Standby UCM sends heartbeat message to active UCM and communicate the status via the heartbeat message. Normally, the active UCM will respond to the standby UCM via heartbeat port. Once the active UCM has failure or if the site encounters unexpected events causing power or network outage, the active UCM is unable to respond heartbeat message to the standby UCM.

  • Page 13: Firmware Upgrade

    Switch Roles Manually FIRMWARE UPGRADE To avoid service interruption, please follow below instructions to upgrade firmware for both UCMs in the HA deployment. 1. Log in the standby UCM’s web UI (UCM A). Upload firmware to UCM web UI and complete upgrade on the standby UCM first. 2.
  • Page 14 REPLACE DEFECTIVE UCM UCM With HA And UCMRC Plan This scenario assumes UCM A and UCM B in the HA deployment already have their individual UCMRC plan that supports HA. If UCM B is defective and needs replacement by UCM C, please follow the steps below. Scenario 1: UCM A is the primary UCM and active role.
  • Page 15 UCM With HA And No UCMRC Plan For the two UCMs (UCM A and UCM B) without UCMRC plan in HA deployment, if one of the UCM (UCM B) becomes defective such as hardware failure, please follow the steps below to replace the defective UCM B with a new UCM C. Assuming UCM A is the active role and UCM B is the standby role, regardless the station type on each UCM, the steps to replace UCM B with UCM C is the same as following: (1) Power off UCM B.
  • Page 16 HA DEPLOYMENT WITH UCMRC PLAN After purchasing UCMRC plan with HA supported and setting up HA, on GDMS, the UCM device will be displayed as Primary (Host) and Secondary (Spare). GDMS Device List Example ROLE CHANGE PROCESS Prerequisite： 1. Both UCM must have UCMRC plan with HA ability and the plans for each UCM must have the same specifications. 2.

  • Page 17: Restore Backup

    https://UCM IP/gswave/# UCM IP is the primary or secondary UCM’s IP. (Currently Wave doesn’t support automatic switchover after HA failover). 2. Wave login from remote network: On Wave, use the custom domain address for the primary UCM provided by GDMS. Currently, only Wave clients registered from remote network can switch over automatically after HA failover.
  • Page 18 System Alert Events Admin can also go to UCM web UI->System Settings->HA->HA Settings->HA Log to view HA backup log, HA failover log and external data sync log. HA Backup Log...
  • Page 19 HA Failover Log HA External Data Sync Log...

  • Page 20: Deployment Example

    DEPLOYMENT EXAMPLE HA Remote Disaster Recovery Deployment Example 172.16.0.1/23 is the enterprise network Two locations A and B have their own main router A and B. Router A and B can communication with each other via 172.16.0.1/23 network. UCM A is set up under router A in location A. UCM B is set up under router B in location B. UCM A and UCM B are configured with their own LAN network IP under their router with different network segment and they cannot directly communicate with each other.
  • Page 21 Heartbeat Port 172.16.0.100 9527 192.168.3.8 9527 Data Sync Port 1 172.16.0.100 3510 192.168.7.20 3510 Data Sync Port 2 172.16.0.100 8989 192.168.7.20 8989 File Sync Port 172.16.0.100 192.168.7.20 Data Sync Port 3 172.16.0.100 9292 192.168.7.20 9292 Data Sync Port 4 172.16.0.100 8796 192.168.7.20 8796...
  • Page 22 Note The configuration varies depending on the network topology.

Table of Contents