User`s guide

242 XgOS User’s Guide • September 2014
A chassis first becomes a standby XDS, then a master. Only a standby XDS can
become a master. This approach enables the system to always have backup
information, which avoids conditions where SM or a master XDS dies. In these cases,
all state information would be lost.
Add Server Profiles
Regardless of the number of chassis in your network, there is only one designated
master and one designated standby.
After the master and standby XDS are identified, each cluster member can
participate in server-profile creation.
When you issue the add server-profile command, for example:
The Oracle Fabric Interconnect sends this server record to both the master and
standby XDS. This record is retransmitted at periodic intervals. To ensure database
synchronization, each cluster member sends periodic updates to both the master and
standby XDS. If the master XDS fails, the standby will become the master and
another Oracle Fabric Interconnect in the cluster will become the new standby.
Each host server knows the address for SM, which in turn sends the master XDS
address to the host server. However, the host server has no knowledge of a standby
XDS. The master XDS provides a list of chassis-cluster members to the host server.
add server-profile <name> <server-name>@<f1-15>:ServerPort<num>