💡 This article is relevant for FIs with on premise core set ups looking to add redundancy to the network.
Overview
In addition to the main VMware VeloCloud SD-WAN Device installed on premise, additional SD-WAN devices can be requested to add redundancy in a Disaster Recovery or High Availability manner.
VMware's physical VeloCloud SD-WAN devices is highly durable and exceptionally reliable, with issues being extremely rare. Most FIs do not leverage additional DR or HA devices. In addition, should core connection be disrupted, Glide is still able to accept new account opening applications and trigger these once the core is back online.
When determining if hardware redundancy is necessary, it's essential to consider your institution's policy and business continuity plan. Determine whether your goal is to be up and running within hours or 24 hours in case of a disaster and where Glide's platform fits into your broader system. Please refer to your contract with Glide or CSM for information around pricing for additional devices.
High Availability Devices (Onsite)
An additional device can be added onsite in a HA manner. Both the main device and HA device would sit at production and behave as one in a Active-Active manner. This set up may be beneficial solutions focus on eliminating single points of failure, ensuring that services remain uninterrupted in the event of hardware fail, such as power supply or box failure. In the event of software updates of the device (extremely rare), the second device kicks in for continuity.
VeloCloud devices utilize port GE1 for the HA heartbeat. Installation process generally follows the guide below:
Reconfiguration of main device:
If you are adding a HA device to an existing installed main device, the main device must be reconfigured before the HA device can be installted.
The main device is usually configured on GE1. We'll need to reconfigure this device to use GE2 for the internal interface and have the FI move the cable.
HA device Configuration:
Connect GE1 from each Velocloud device to each other to establish the HA heartbeat and activate the standby unit.
Plug in cables to the other two ports, respectively, to the switch ports configured for the correct VLANs.
For detailed steps and reference, consult the VMware SD-WAN Administration Guide.
Disaster Recovery Devices (Offsite)
We may refer to DR devices as a failover devices. While HA ensures your systems are resilient to component failures, DR prepares you for rapid recovery in the event of a disaster.
The set up for a DR device is similar to the set up for the main VeloCloud SD-WAN device. Glide will need the following information in order to configure and send out the DR device.
Client WAN Interface IP, Subnet, Gateway
Client LAN Interface IP, Subnet, Gateway
Core IP address
Shipping address for the client
Contact information for who at the FI is responsible for moving the traffic over to the DR device in the event of DR.
Sitting Dormant Device
Having a sitting dormant device is another strategy that may be used if it would make sense depending on your FIs business continuity plan. In the event of disruption with the initial device, the sitting dormant device could be installed within 2-4 hours depending on availability of personnel involved.