Middleware that provides libraries, GUI, and code generator to design multi-node (clustered) applications that are highly available, redundant, and scalable. Provides sub-second node and application fault detection and failover, and useful application libraries including distributed hash tables (checkpoint), event, logging, and communications. Implements SA-Forum APIs where applicable. Used anywhere reliability is a must -- like telecom, wireless, defense and enterprise computing. Download stable release with installer from: ftp.openclovis.com
Customer wants to use multiple network interfaces that a node A can talk to a group of nodes with interface ethA while talking to another group with interface ethB. Customer needs to create a network topology to support this and then configure TIPC to use multiple interfaces.
Here is the example of TIPC configuration for multiple interfaces:
$tipc-config -be=eth:eth0
$tipc-config -be=eth:eth1
Currently, our SAFplus only support single network interface. It is defined in asp.conf:
export LINK_NAME=eth0
Now, we need to support multiple interfaces definition separate by spaces:
export LINK_NAME=eth0 eth1
Note: we only support multiple interfaces configuration for TIPC (for now).
Customer wants to use multiple network interfaces that a node A can talk to a group of nodes with interface ethA while talking to another group with interface ethB. Customer needs to create a network topology to support this and then configure TIPC to use multiple interfaces.
Here is the example of TIPC configuration for multiple interfaces: $tipc-config -be=eth:eth0 $tipc-config -be=eth:eth1
Currently, our SAFplus only support single network interface. It is defined in asp.conf: export LINK_NAME=eth0
Now, we need to support multiple interfaces definition separate by spaces: export LINK_NAME=eth0 eth1
Note: we only support multiple interfaces configuration for TIPC (for now).