Hi team.

I have seen some discussions using interface groups with DDBoost.

I would like to configure it correctly from the start.  I understand that I just add the interfaces to the Interface Group in my DDBoost IP Interfaces tab, configure the clients, and DDBoost will find the least used IP and use that IP instead.  (If I'm wrong, please correct me!)

I have also seen some people discuss adding a 3rd, LACP device or Failover devices to their Interface Group?  If we only intend to use 2 physical connections to this Data Domain using the DDBoost IFGroup, why do I need this 3rd IP and entry in my IFGroup?

For Example, I have configured...

sysadmin@Some_Datadomain# ifgroup show config all

Group-name     Status     Interface   Clients   Replication
------------   --------   ---------   -------   -----------
default        disabled           0         0             0
Site A         enabled            2         1             0
------------   --------   ---------   -------   -----------

Group-name     Status      Interfaces
------------   -------   ------------
Site A      enabled   1.2.3.4
Site A      enabled   1.2.3.5
------------   -------   ------------

Group-name     Status    DD Boost Clients
------------   -------   ----------------
Site A   enabled   *
------------   -------   ----------------
No replication mtrees with remote hosts in ifgroup
File replication is allowed on ifgroup.
Client may use any interface.

And my networking looks like this...

sysadmin@Some_DataDomain# net show settings

port    enabled   state     DHCP   IP address                   netmask          type   additional setting

                                                                /prefix length

-----   -------   -------   ----   --------------------------   --------------   ----   ------------------

ethMa   yes       running   no     1.2.3.3                      255.255.255.0    n/a

                                   IP_v6_Nonsense**   /64

eth1a   yes       running   no     1.2.3.4                      255.255.255.0    n/a

                                   IP_v6_Nonsense**   /64

eth1b   yes       running   no     1.2.3.5                      255.255.255.0    n/a

                                   IP_v6_Nonsense**   /64

eth1c   no        down      no     n/a                          n/a              n/a

eth1d   no        down      no     n/a                          n/a              n/a

eth3a   no        down      no     n/a                          n/a              n/a

eth3b   no        down      no     n/a                          n/a              n/a

eth3c   no        down      no     n/a                          n/a              n/a

eth3d   no        down      no     n/a                          n/a              n/a

-----   -------   -------   ----   --------------------------   --------------   ----   ------------------

** auto_generated IPv6 address