<div class="table-wrap"><table data-ke-type="table" data-ke-align="alignLeft" style="width: 100%;" border="1"><tbody><tr><td>1</td><td>[root@dbi-pg-essentials network-scripts]#  service efm-3.3 start</td></tr></tbody></table></div><p>Running again the status command should show the VIP address. Restarting efm should be enough but if ever the virtual IP is not shown we can use following command to add the virtual IP.</p><div class="table-wrap"><table data-ke-type="table" data-ke-align="alignLeft" style="width: 100%;" border="1"><tbody><tr><td>1</td><td>[root@dbi-pg-essentials network-scripts]# /usr/edb/efm-3.3/bin/efm_address add4 enp0s9 <a style="color: #1155cc;" href="http://192.168.22.105/24" target="_blank" class="ke-link">192.168.22.105/24</a></td></tr></tbody></table></div><p>Then the status should be</p><div class="table-wrap"><table data-ke-type="table" data-ke-align="alignLeft" style="width: 100%;" border="1"><tbody><tr><td>1<br>2<br>3<br>4<br>5<br>6<br>7<br>8<br>9<br>10<br>11<br>12<br>13<br>14<br>15<br>16<br>17<br>18<br>19<br>20<br>21<br>22<br>23<br>24<br>25<br>26</td><td>[root@dbi-pg-tools ~]# /usr/edb/efm-3.3/bin/efm cluster-status efm<br>Cluster Status: efm<br><br><br>        Agent Type  Address              Agent  DB       VIP<br>        -----------------------------------------------------------------------<br>        Witness     192.168.22.100       UP     N/A      192.168.22.105<br>        Master      192.168.22.101       UP     UP       192.168.22.105*<br>        Standby     192.168.22.102       UP     UP       192.168.22.105<br><br><br>Allowed node host list:<br>        192.168.22.101 192.168.22.102 192.168.22.100<br><br><br>Membership coordinator: 192.168.22.101<br><br><br>Standby priority host list:<br>        192.168.22.102<br><br><br>Promote Status:<br><br><br>        DB Type     Address              XLog Loc         Info<br>        --------------------------------------------------------------<br>        Master      192.168.22.101       0/301BEE0<br>        Standby     192.168.22.102       0/301BEE0<br><br><br>        Standby database(s) in sync with master. It is safe to promote.<br>[root@dbi-pg-tools ~]#</td></tr></tbody></table></div><p>We can manually ping the virtual IP from both servers. There should not exist any loss packets</p><div class="table-wrap"><table data-ke-type="table" data-ke-align="alignLeft" style="width: 100%;" border="1"><tbody><tr><td>1<br>2<br>3<br>4<br>5<br>6<br>7</td><td>[root@dbi-pg-tools ~]# ping -q -c3 -w5 192.168.22.105<br>PING 192.168.22.105 (192.168.22.105) 56(84) bytes of data.<br><br><br>--- 192.168.22.105 ping statistics ---<br>3 packets transmitted, 3 received, 0% packet loss, time 2001ms<br>rtt min/avg/max/mdev = 0.278/0.366/0.528/0.116 ms<br>[root@dbi-pg-tools ~]#</td></tr></tbody></table></div><p>And from the master we can see that the VIP address is assigned to enp0s9</p><div class="table-wrap"><table data-ke-type="table" data-ke-align="alignLeft" style="width: 100%;" border="1"><tbody><tr><td>1<br>2<br>3<br>4<br>5<br>6<br>7<br>8<br>9<br>10</td><td>[root@dbi-pg-essentials network-scripts]# ifconfig enp0s9                      <br>enp0s9: flags=4163  mtu 1500<br>        inet 192.168.22.105  netmask 255.255.255.0  broadcast 0.0.0.0<br>        ether 08:00:27:53:1c:ed  txqueuelen 1000  (Ethernet)<br>        RX packets 3394  bytes 397433 (388.1 KiB)<br>        RX errors 0  dropped 0  overruns 0  frame 0<br>        TX packets 3096  bytes 571448 (558.0 KiB)<br>        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0<br><br><br>[root@dbi-pg-essentials network-scripts]#</td></tr></tbody></table></div><p>So we can use the virtual address to connect to the primary database</p><div class="table-wrap"><table data-ke-type="table" data-ke-align="alignLeft" style="width: 100%;" border="1"><tbody><tr><td>1<br>2<br>3<br>4<br>5<br><br><br></td></tr></tbody></table></div><p>...</p>
<!-- -->
