FusionDirector 1.6.4.SPC1 CentOS v7.9 LACP Bonding

Hi, dear

Sorry about that I can not understand what do you mean.

Do you want an excel template that allows you to bond  the interfaces in batches when configuring LDAP for FusionDretor?

A G.SHDSL interface card provides one RJ45 physical interface that can be virtualized into four G.SHDSL interfaces. G.SHDSL interfaces support the bonding function.
The four G.SHDSL interfaces support bonding of the following modes (only the interface with an even number can function as the primary interface):
-Bonding of interfaces 0 and 1
-Bonding of interfaces 0, 1, and 2
-Bonding of interfaces 0, 1, 2, and 3
-Bonding of interfaces 2 and 3

Important: Attempting to configure a single subnet on different network interfaces can result in unpredictable routing behavior, including possible loss of connectivity. In this case, a single network adapter on the 10GbE interface is generally suitable for both types of traffic because of the benefit of higher traffic throughput.

Important: It is recommended that you avoid using the following IP combinations while running the following commands:

 CLI mknw  command: avoid using the following IP combinations on a new network:
-Public network gateway IP as public IP
-Public network IP as gateway IP
-System Default Gateway (SDG) IP declared as public IP
-Management network service or management IP as gateway IP
-Management network gateway IP as public IP
-Management network service or management IP as public IP
-Public IP declared as a public IP on a different public network
-NAT gateway IP as public IP
-NAT gateway IP as gateway IP of a route

CLI chnw command: avoid using the following IP combinations on the current network:
-Public network gateway IP as public IP
-Public network IP as gateway IP
-System Default Gateway (SDG) IP declared as public IP
-Management network service or management IP as gateway IP
-Management network gateway IP as public IP
-Management network service or management IP as public IP
-Public IP declared as a public IP on a different public network
-NAT gateway IP as public IP
-NAT gateway IP as gateway IP

CLIN chnwmgt  command: avoid using the following IP combinations in a management network:
-Public network gateway IP as service or management IP
-NAT gateway IP as service or management IP
-NAT gateway IP as gateway IP
-IP of system default gateway (SDG) declared as service or management IP
-Management network gateway IP as a service or management IP
-Management Network Service or Management IP as Management Gateway IP
-Public IP as management network service or management IP
-Public IP as Management Gateway IP

-mknwnatgateway command: avoid using the following IP combinations:
-Management gateway IP as NAT gateway IP
-Public network gateway IP as NAT gateway IP
-Management Service or Management IP as NAT Gateway IP
-Public IP as NAT Gateway IP
-System Default Gateway IP (SDG) declared as the NAT gateway IP

chnwsdg command: avoid using the following IP combination:
-Management service or management IP as system default gateway (SDG) to public network.
-Public IP as System Default Gateway (SDG)
-NAT Gateway IP as System Default Gateway (SDG)

I created manually, like this.

xEL Linux 7.x MZ710-CX710 Mod4

============================

DEVICE=ens2

NAME=ens2

TYPE=Ethernet

BOOTPROTO=none

ONBOOT=yes

MASTER=bond0

SLAVE=yes

============================

DEVICE=ens2d1

NAME=ens2d1

TYPE=Ethernet

BOOTPROTO=none

ONBOOT=yes

MASTER=bond0

SLAVE=yes

============================

DEVICE=bond0

NAME=bond0

TYPE=Bond

BONDING_MASTER=yes

IPADDR=10.48.48.10

GATEWAY=10.48.48.1

NETMASK=255.255.255.0

DNS1=10.48.80.234

DNS2=10.48.80.235

PEERDNS=yes

ONBOOT=yes

BOOTPROTO=static

BONDING_OPTS="mode=802.3ad miimon=100 lacp_rate=fast arp_validate=0"

============================