Description
Sets the name of the NIC used by the host during HCCL initialization. HCCL obtains the host IP address based on the NIC name and communicates with the root node to create a communicator.
- eth: Use all NICs prefixed with eth.
If multiple NIC prefixes are specified, separate them with commas (,).
For example, export HCCL_SOCKET_IFNAME=eth,enp indicates that all NICs prefixed with eth or enp are used.
- ^eth: Do not use NICs prefixed with eth.
If multiple NIC prefixes are specified, separate them with commas (,).
For example, export HCCL_SOCKET_IFNAME=^eth,enp indicates that no NIC prefixed with eth or enp is used.
- =eth0: Use the specified eth0 NIC.
If multiple NICs are specified, separate them with commas (,).
For example, export HCCL_SOCKET_IFNAME==eth0,enp0 indicates that the eth0 and enp0 NICs are used.
- ^=eth0: Do not use the specified eth0 NIC.
If multiple NICs are specified, separate them with commas (,).
For example, export HCCL_SOCKET_IFNAME=^=eth0,enp0 indicates that the eth0 and enp0 NICs are not used.
- Multiple NICs can be configured in HCCL_SOCKET_IFNAME. The first matched NIC is used as the communication NIC.
- The HCCL_IF_IP environment variable takes higher priority than HCCL_SOCKET_IFNAME.
- If HCCL_IF_IP and HCCL_SOCKET_IFNAME are not specified, the priority is as follows:
NICs other than Docker or local NICs (in ascending alphabetical order of NIC names) > Docker NICs > local NICs
Note that if HCCL_IF_IP or HCCL_SOCKET_IFNAME is not configured, the system automatically selects NICs based on their priorities. If the NIC specified for the current node is disconnected from that for the root node, the HCCL link establishment will fail.
Example
# Use eth0 or endvnic NICs. export HCCL_SOCKET_IFNAME==eth0,endvnic
Constraints
None
Applicability
Atlas 350 Accelerator Card