The standalone AliasNames Server illustrated in Figure A-5 provides a list of AliasNames that reference Nodes in multiple separate Servers. This type of configuration might be used for Servers that do not have the resources to manage AliasNames on their own. It might also be used in a system where the configuration of AliasNames occurs after the devices that are represented by the Servers have already been deployed or if a Server just does not have support for AliasNames. The standalone AliasNames Server can function as a lookup Server for all of the AliasNames defined in the system. It is the responsibility of the standalone AliasNames Server to ensure that the mapping of AliasNames to actual Nodes is correct. The standalone AliasNames Server might have a subscription to each Server monitoring the status of the Server and monitoring for ModelChangeEvents that occur on the source Servers.
Figure A-5 - AliasNames Server example