Neverfail Continuity Engine Recloning limitations when static routes are configured

Follow

Summary

This Knowledgebase article provides details about the supported use cases of Recloning feature when persistent static routes are configured on the Neverfail Continuity Engine cluster. It also offers details about the known limitations and workaround procedure for the situation when the static routes configuration is not correct after a passive server node recloning.

 

More information

Supported use cases 

  • IPv4 static routes created using the route command
    • The route command is used to view and modify the network routing tables of an IP network
    • Example: route add 192.168.33.63 mask 255.255.255.255 192.168.33.254 IF 12 -p
    • Explanation: Above command adds a persistent static route for the 192.168.33.63 destination IP address (only) using 192.168.33.254 as next hop/gateway, associated with NIC interface with index 12
  • all the single NIC deployments
  • all the V2V deployments, where the recloning is done via VMware vCenter cloning method
  • all the V2V2V deployments, where the recloning is done via VMware vCenter cloning method
  • any of the Automated, Manual and Scheduled Automated recloning options considering all of the above conditions are met

Known limitations in addition to the supported use cases

  • only IPv4 static routes are supported. IPv6 static routes are not supported
  • routes added using Routing and Remote Access management console require manual reconfiguration after the recloning
  • P2V pair with multiple NICs: in this scenario, after a passive node recloning it is possible that static route is not correctly configured on the desired NIC: to solve this situation, follow the procedure described below.
  • P2V2V trio configurations with multiple NICs, when Secondary node only or the full cluster are recloned (Tertiary only recloning is supported): in this scenario, after a passive node recloning it is possible that static route is not correctly configured on the desired NIC: to solve this situation, follow the procedure described below.

 

Procedure

When recloning is performed in a scenario which is not fully supported, user intervention is required for reconfiguring the static routes on the passive recloned server node.

Symptom

  • possible channel disconnection and/or Engine replication traffic is not using the desired route

Cause

  • existing static routes are correctly persisted and reconfigured post recloning on the (recloned) passive node but they're not associated with the correct network interface.

Workaround

  • manual reconfiguration of static route(s) on the affected passive, so the correct NIC is associated with a given route. This should be done by deleting (route delete) and re-adding the persistent static route to the correct network interface index, as indicated in the route add example from above

  

Applies To

Neverfail Continuity Engine v8.5

 

KBID-3020

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.