Fix my mistake in the behavior of VIP ping check

EnterpriseDB · Nov 2, 2023 · c160ae3 · c160ae3
1 parent 3c495a3
commit c160ae3
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/product_docs/docs/efm/4/04_configuring_efm/05_using_vip_addresses.mdx b/product_docs/docs/efm/4/04_configuring_efm/05_using_vip_addresses.mdx
@@ -25,7 +25,7 @@ This allows you to upgrade and perform maintenance on EFM services without inter
 
 The VIP should be initially assigned to the primary node. When EFM detects failure of the primary node's database, it will release the VIP and then assign it to a standby node as that node is promoted to be the new primary. 
 
-EFM verifies (via the command configured via the [`ping.server.command`](01_cluster_properties.mdx#ping_server_command) cluster property) that the VIP is not currently in use during promotion of a standby, and will not assign it to the new primary node until the ping indicates it is unreachable. You can disable this behavior via the [`check.vip.before.promotion`](01_cluster_properties.mdx#check_vip_before_promotion) cluster property. 
+EFM verifies (via the command configured via the [`ping.server.command`](01_cluster_properties.mdx#ping_server_command) cluster property) that the VIP is not currently in use during promotion of a standby, and will not promote a new primary node until or unless the ping indicates the VIP is unreachable. You can disable this behavior via the [`check.vip.before.promotion`](01_cluster_properties.mdx#check_vip_before_promotion) cluster property. 
 
 !!!tip "Meaning of the ping command exit code"
    Failover Manager uses the exit code of the ping command to determine whether an address is reachable. A zero exit code indicates the address is reachable (in this context, this means the VIP is assigned). A non-zero exit code indicates the address isn't reachable (in this context, this means the VIP is unassigned).