I don't get exactly the question but first of all: BeeGFS does not support the Fiber Channel protocol nor it's a block device sharing like an FC device, it needs TCP/IP networking or RDMA (with Infiniband, RoCE or Omni-Path). BeeGFS is much more like a filer than a SAN storage.
That's stated on the product brief: https://www.beegfs.io/c/home/key-aspects-of-beegfs/
Where it reads: BeeGFS is built on highly efficient and scalable multithreaded core components with native RDMA support. File system nodes can serve RDMA (InfiniBand, (Omni-Path), RoCE and TCP/IP) network connections at the same time and automatically switch to a redundant connection path in case any of them fails.
There's also the same question on the BeeGFS FAQ: https://www.beegfs.io/wiki/FAQ#net_types
That's the answer regarding the Fiber Channel question. Regarding the IP change, you can aggregate multiple interfaces and consequently multiple IP addresses. To achieve this you just configure the connNetFilterFile
and connInterfacesFile
in each configuration file on the machine that provides the BeeGFS service, there's more info on the FAQ too: https://www.beegfs.io/wiki/FAQ#multiple_nics