Command
weka cluster host net add
Note: If the new client is to communicate with the Content Software for File system cluster over the kernel UDP stack, it is not necessary to run this command. If a high-performance client is required and the appropriate network NIC is available, use the following command to configure the networking interface used by the client to communicate with the Content Software for File system cluster hosts:
weka cluster host net add <host-id> <device> --ips=<ip-address> --netmask=<netmask> --gateway=<gateway>
Parameters
| Name | Type | Value | Limitations | Mandatory | Default |
|---|---|---|---|---|---|
| host-id | String | Identifier of the host to be added to the cluster | Must be a valid host identifier | Yes | |
| device | String | Network interface device name for example, eth1 | Must be a valid network device name | Yes | |
| ips | IP address | The IP address of the new interface | Must be a valid IP address | Yes | |
| gateway | IP address | The IP address of the default routing gateway | The gateway must reside within the same IP network of ip-address (as described by netmask). Not relevant for IB / L2 non-routable networks | No | |
| netmask | Number | Number of bits in the net mask, for example, the net mask of 255.255.0.0 has 16 netmask bits | Describes the number of bits that identify a network ID (also known as CIDR) | No |
Note: When configuring an InfiniBand client, do not pass the --ips, --netmask, and --gateway parameters.
Note: InfiniBand clients can only join a cluster with InfiniBand backends. It is not possible to mix InfiniBand and Ethernet clients/backends.