The standalone AliasNames Serverillustrated in Figure A-5provides a list of AliasNamesthat reference Nodesin multiple separate Servers. This type of configuration might be used for Serversthat do not have the resources to manage AliasNameson their own. It might also be used in a system where the configuration of AliasNamesoccurs after the devices that are represented by the Servershave already been deployed or if a Serverjust does not have support for AliasNames. The standalone AliasNames Servercan function as a lookup Serverfor all of the AliasNamesdefined in the system. It is the responsibility of the standalone AliasNames Serverto ensure that the mapping of AliasNamesto actual Nodesis correct. The standalone AliasNames Servermight have a subscription to each Servermonitoring the status of the Serverand monitoring for ModelChangeEventsthat occur on the source Servers.


Figure A-5– AliasNames Server example