Configure a core group transport
When you configure a core group, we can specify the type of network transport we want the high availability manager to use for network communications.
Complete the following actions before you start to configure a core group transport.
- Make sure that you are familiar with the content of the topic Core group transports.
- Confirm that all node agents in the core group are running.
- Determine which transport type is appropriate for the core group.
Change the transport setting for a core group if the current transport type does not meet the needs. For example, we might need to increase security, you might want to maximize replication throughput, or a core group might need to use the core group bridge service.
Avoid trouble: If a core group needs to use the core group bridge service, you must select Channel framework as its transport mechanism. If we select Unicast, you might receive error message CHFW0029E, which indicates that the transport chain was not initialized because the address was already in use.gotcha
To change the core group transport for a core group, complete the following procedure.
- In the console, click Servers > Core Groups > Core group settings, and select an existing core group, or click New if you are creating a new core group.
- Under Transport type, select the type of transport to use for this core group.
Deprecated feature: We can select one of the following types of transports. However, if possible, select Channel framework because support for unicast transports is deprecated.depfeat
- Channel framework is the default transport type, and is a flexible point-to-point transport. If we choose this transport
type, you must also select one of the transport chains that is listed
in the Transport chain field.
- If we select DCS, the high availability manager performs related network communication over non-secure sockets.
- If we select DCS-Secure, the high availability manager performs related network communication over SSL encrypted sockets.
- If we select DCS, the high availability manager performs related network communication over non-secure sockets.
- Unicast, is a point-to-point transport over standard non-secure operating system-level TCP/IP network connection facilities.
- Channel framework is the default transport type, and is a flexible point-to-point transport. If we choose this transport
type, you must also select one of the transport chains that is listed
in the Transport chain field.
- Click Synchronize changes with nodes, and then click OK.
- Select Synchronize changes with nodes, and then click Save again.
- Restart the servers containing core group members.
Results
The new transport values are in effect after the servers restart.
Subtopics
- Interoperating with Version 6.0.1.2 processes
The high availability manager supports multihomed hosts, which means that the product processes can communicate with each other even if they are running on different versions of the product. If we are running Version 6.0.1.2 processes that need to communicate with each other, there are high availability manager-related issues that we need to consider. - Interoperating with Version 6.0.2 and later processes
The high availability manager supports multihomed hosts, which means that the product processes can communicate with each other even if they are running on different versions of the product. If we are running Version 6.0.2 and later processes that need to communicate with each other, we need to consider there are high availability manager-related issues. - Core group transports
Core group members communicate with each other over a specialized and dedicated network transport. Multiple transport implementations are supported, each with its own set of advantages and disadvantages.
Related concepts