1

In a previous post this was mentioned by @Celada in the Enhanced version section: Use NIC bonding with independent switches

My situation:
one centos 7.2 host with 4 100G NICs - all connected to ToR:

NIC1: 10.0.2.1/24

NIC2: 10.0.2.2/24

NIC3: 10.0.2.3/24

NIC4: 10.0.2.4/24

Requirement: How to configure an extra loopback addr on the centos host and publish it as a single IP for HA/LB access for client machines within the rack, for iSCSI data-path access for storage.

redcursor
  • 11
  • 1

1 Answers1

0

Quoting the answer you cited:

Configure with ip addr add 10.0.3.1/32 dev lo

So subnet 3 corresponds to the server resource. Edit /etc/sysconfig/network-scripts/ifcfg-* and systemctl restart network. Quagga will pick this up and send link-state advertisements out your four NICs, or fewer during a NIC outage e.g. when you unplug one.

Clients, such as iSCSI initiators, will refer to HA address 10.0.3.1, transparently sending via one of the four NICs that is currently up.

J_H
  • 636
  • 4
  • 8
  • Thanks! Do you happen to have any good step-by-step quagga install & config doc for this topology or similar. – redcursor Nov 24 '17 at 00:34
  • You might follow http://xmodulo.com/turn-centos-box-into-ospf-router-quagga.html or http://www.brianlinkletter.com/how-to-build-a-network-of-linux-routers-using-quagga/ – J_H Nov 24 '17 at 05:38
  • Thanks @J_H. Configured quagga (zebra and ospfd) on a centos 7 cloud instance (VM). My configs in linked gdoc. Please comment if this is in the right direction and what else must happen to publish loopback HA address for clients to connect. https://docs.google.com/document/d/1Hwlk3p1_NQBQYjT_g4BNbZY5iMsHNB39OzmGcV7_2KU/edit – redcursor Nov 26 '17 at 06:21