Issue
Server data may be combined in Building Advisor if a server connected to Building Advisor is cloned or detached without first disabling Cloud Connectivity (Cloud Plugin) and resetting its System ID. This can result in duplicate System IDs and incorrect data associations between servers.
Product Line
EcoStruxure Building Advisor, EcoStruxure Building Operation
Environment
- EcoStruxure Building Operation Enterprise Server (ES)
- Enterprise Central (EC)
- EcoStruxure Building Advisor
- Cloud Connectivity (Cloud Plugin)
Cause
Cloud Connectivity (Cloud Plugin) was not disabled, and the System ID was not reset before the server was cloned or detached.
As a result, the new server retained the original server's identification, which can lead to duplicate System IDs and combined server data in Building Advisor.
Resolution
Identifier terminology: In EcoStruxure Building Operation, the identifier is displayed as Server Id.
In the tracelog, the same identifier is shown as sysID. Because the tracelog provides the most accurate and current value, this article refers to it as the System ID.
The System identifier field shown in EcoStruxure Building Operation is a different value. Although it may be used when connecting a server to the Building Advisor Portal, it is not used in this cloning or detaching procedure.
Do not reset or modify the System identifier field for this process.
Before adding a new top server, cloning a server, or detaching a server connected to Building Advisor:
-
If Cloud Agent is installed on the server, review the referenced article and complete the Cloud Agent removal procedure before continuing with the server modification activities
How to remove Cloud Agent Components Before Performing Server Changes - Disable Cloud Connectivity (Cloud Plugin)
- Reset the Server Id shown in EcoStruxure Building Operation. This is the value identified as sysID in the tracelog and is referred to as the System ID in this article.
Figure 1. Reset the value labeled Server Id. Do not modify the System identifier field for this procedure.
- Perform the server architecture change, such as adding a new top server, cloning the server, or detaching the server.
Resetting the Server Id/System ID allows the new server to generate a unique identifier and establish its own Building Advisor registration. The System identifier field is not part of this procedure.
Following this procedure helps prevent duplicate System IDs and prevents data from multiple servers from being combined in Building Advisor. This is especially important when the servers belong to different customers.
If a server was cloned, detached, or a new top server was added before Cloud Connectivity was disabled and the System ID was reset, open a PSS ticket for assistance with separating the server data.
