If multiple edges in the same network zone have the same protocol server activated with the same configuration, a single server communication profile is declared for all edges.
During Central Governance registration, for each network zone, protocol servers activated on each edge are imported as server communication profiles.
An edge can belong to one or more network zones. One or more SecureTransport Edge servers can be grouped in a network zone in SecureTransport. Unique and duplicate server communication profilesīefore registering you should understand how unique and duplicate server communication profiles are determined when SecureTransport has SecureTransport Edge servers deployed within its infrastructure. Once you have upgraded to SecureTransport 5.5 or higher, you can manually update the status in the Central Governance user interface using the SecureTransport health check option.Īs of SecureTransport 5.5, you can only registration using REST API registering via the user interface is not supported for version 5.5 and higher. This occurs even though the original SecureTransport had the status Started, as it is stopped during the upgrade procedure. After upgrading a registered SecureTransport 5.4 or 5.3.6 to SecureTransport 5.5, its status is Unreachable in Central Governance.