This topic describes the input parameters for a multi-node EFA deployment.
Specify the deployment type using the multi-node command after the deployment. Use the peer-node command followed by the peer node IP address for the installation.
Use the vip4 command followed by the virtual IP address to provide the virtual IPv4 address for the installation.
efa deploy non-interactive multi-node package <package-name> peer-node <peer node ip> vip4 <virtual ip-address>
efa deploy non-interactive multi-node package /efaboot/efa-2.7.1-tar.gz peer-node 10.20.246.102 vip4 10.20.246.103
Use the vip6 command followed by the virtual IP address to provide the virtual IPv6 address for the installation.
As a best practice, do not use the virtual IPv6 address that is converted from IPv4 address.
efa deploy non-interactive multi-node package /efaboot/efa-2.7.1-tar.gz peer-node 10.20.246.102 vip4 10.20.246.103 vip6 fd00::56:45
Use the management-ip command if you need additional management IP networks. Do not use the command if it is not required. EFA supports adding only a single sub-interface.
efa deploy non-interactive multi-node package <package-name> peer-node <peer IP> vip4 <virtual IP> management-ip sub-interface-name <sub interface name> sub-vlan-id <vlan> external-subnet <virtual IP with subnet>
When deploying the management IP, some commands are sub-interface-name, which requires the name of the sub-interface. sub-vlan-id, which is the VLAN ID, and external-subnet, which is the external subnet address in CIDR format.
Example:
efa deploy non-interactive multi-node package /efaboot/efa-2.7.1-tar.gz peer-node 10.20.246.102 vip4 10.20.246.103 management-ip sub-interface-name sub201 sub-vlan-id 201 external-subnet 10.20.246.99/20
In a TPVM deployment, following are the available options for a multi-node build upgrade and replacement:
efa deploy non-interactive multi-node package /efaboot/efa-2.7.1-tar.gz replacement-ip 10.200.246.155