MIPC connects all multiplex nodes to support distributed query processing and high availability.
As multiplex servers start, they establish MIPC connections.
MIPC is a fully meshed communication framework that runs on both public and private interconnection configurations. Public interconnection configuration is mandatory while private configuration is optional.
Private high-speed interconnection configurations are for distributed query processing. Currently, private interconnection configurations are restricted to physical networks supporting the TCP/IP protocol.
If no private interconnection configuration is provided, MIPC uses the legacy public interconnection configuration specified in the system table column SYSIQMPXSERVER.conn_info. This set of host/port addresses is shared between external user connections, INC connections, and internal MIPC connections.
Redundant networks provide a more robust cluster. If both private and public interconnection configurations exist, MIPC uses the private connections if available, and reroutes traffic to the public connections if the private network fails. The multiplex monitors the messages between nodes to detect failures.
For recommendations on planning network configurations for distributed query processing, see the Installation and Configuration Guide.