Split-network scenario
In this case the primary and the secondary servers run in the active mode. The primary and secondary servers do not communicate with each other due to a network outage. Before making administration changes, the administrator must confirm the group membership using the webpage. The administrator must perform the administration changes on the primary System Manager for the Avaya Breeze® platform instances that the primary server manages. Similarly, the administrator must perform the administration changes on the secondary System Manager for the Avaya Breeze® platform instances that the secondary server manages. Each System Manager replicates the administration changes to the respective Avaya Breeze® platform servers. Administration changes must also be compatible with non-Avaya Breeze® platform elements in the split network. For example, a SIP user added on System Manager should have Avaya Breeze® platform Profile, Session Manager Profile and CM Endpoint Profile that reference the Avaya Breeze® platform, Session Manager, and Communication Manager elements managed by the same System Manager. In other words, the elements are all on the same side of the network split.
Caution:
Before making administration changes, you must assess the extent of the enterprise network split. The network split results in partitioning of Avaya Breeze® platform servers and other elements into two groups. The primary System Manager manages one group and the secondary System Manager manages the other group.
Note:
After a split-network scenario you can restore changes made only in one of the two System Manager servers.
Split-network warning messages
The Avaya Breeze® platform Server Administration page displays a warning message when the System Manager server detects that the administrator is configuring for a split-network scenario. The primary System Manager can detect the possibility of a split-network configuration if:
The primary System Manager does not manage all the Avaya Breeze® platform instances.
The secondary System Manager is not reachable on the network.
The secondary System Manager is active.
The secondary System Manager can detect the possibility of a split-network configuration if:
When the system displays a warning message, click the Avaya Breeze® Management Status link to go to the webpage. In this webpage, view the status of the System Manager that manages each Avaya Breeze® platform server. Click Minimize to hide the warning message.
