Issue
When using the SBO xbk Analyzer, a warning with the following details is observed:
- *** possible configuration issue *** (QC#49504)
- Issue: 'Communication failed' alarms between servers, even if no bindings are made
- Action: Make sure servers can communicate with each other so they can synchronize.
Product Line
EcoStruxure Building Operation
Environment
Building Operation Server backups version 3.x and above.
Cause
The defect mentioned in the tool (QC#49504 / DBSQA-57599) was initially created because alarms were generated between two (or more) Automation Servers that had no bindings (or references) between them. This behavior is considered normal.
This occurs because the servers attempt to synchronize references but fail due to communication issues, resulting in the alarms. These Automation Servers were previously part of the same system but were separated before reference synchronization was completed.
A possible scenario for this issue is:
- Two servers can see each other.
- Bindings are established between the two servers.
- The connection between the two servers is then disrupted (i.e., offline).
- Subsequently, one or more of the bindings are deleted, leading to offline alarms between these servers, even if no binding exists now, due to pending synchronization.
Resolution
The XBK analyzer tool detects this situation via a "SyncPending" flag, indicating that it needs to be investigated if a "Communication Alarm" exists between these servers.
This warning can be ignored if no communication alarms are associated with the servers listed by the analyzer tool.
In most cases, if the server names listed by the tool are part of the system, the issue can be resolved by checking and verifying for unresolved bindings via Binding Diagnostics. while connected to a working EBO System.
If the tool lists any other server names that are not part of the system, these server names can be cleared by upgrading to EBO 2024 (v6.0.x) and above. As stated, it is only a warning for earlier versions and can be ignored, as there can be instances where this is not cleared until upgraded to this release.
