Product data

Chapter 12. High availability and redundancy 305
Primary node This is the node you use to set up high
availability. It is initially the active node. When
you set up a high availability cluster, the IBM
Systems Director data, remote authentication
configuration settings, users, and firewall
settings on this node are replicated to the
secondary node.
Secondary node This is the node that you set up to take over if
the primary node fails. It is initially the passive
node, but takes over as the active node if the
primary node fails.
Network status IP address The cluster nodes use this IP address to
determine which node is connected to the
network. If they cannot contact each other, the
node that can connect this IP address becomes
the active node.
Floating IP address This address is always assigned to the active
node. Users should always access this address
so they do not have to know which node is
active. It also enables you to use IBM Systems
Director Common Agent with high availability.
12.2.2 SDMC High Availability synchronized data
The following data changes on the active SDMC are synchronized to the standby
SDMC:
򐂰 User additions
򐂰 User modifications
򐂰 User deletions
򐂰 Firewall changes
򐂰 NTP configuration
򐂰 Kerberos/LDAP configuration
򐂰 Initial High Availability configuration
– DRBD configuration
–Users
– Authentication files (LDAP and Kerberos)
– Firewall settings
– DNS resolver
– NTP configuration