Same device classified differently in separate underlying domains

The Global Manager can receive conflicting topology information when two underlying domains discover the same device but classify it differently. The scenarios where this may occur are as follows:

• A device has the same name, but is an instance of different classes in two or more underlying domains. In addition, the device is classified as Host, Uncertified, or Node in one or more of the underlying domains. When this occurs, the Global Manager replaces an instance of a less specific class, Host, Uncertified or Node, with an instance of a more specific class. Incoming event information for the device is consolidated to the instance in the Global Manager’s topology.

  For example, device1.mydomain.com is classified as Uncertified in one underlying domain and classified as a Router in a second underlying domain. The Global Manager classifies the device as a Router in its topology. All incoming notifications related to device1.mydomain.com are associated with the Router instance in the Global Manager’s topology.

• A device has the same name, but is an instance of different classes in two or more underlying domains. In this case, the device is not classified as Host, Uncertified, or Node in any underlying domain. The Global Manager classifies the device according to the first topology information it receives from an underlying domain. Relationship information for the device is updated during consecutive topology synchronizations. Incoming event information for the device is consolidated to the instance in the Global Manager’s topology.

  For example, device2.mydomain.com is classified as a Probe in one underlying domain and a Router in a second underlying domain. If the first underlying domain synchronizes first with the Global Manager, the Global Manager classifies the device as a Probe in its topology. However, any relationship information for the router from the second underlying domain is preserved by the Global Manager and added to the Probe instance. All incoming notifications related to device2.mydomain.com are associated with the Probe instance in the Global Manager’s topology.

  Note:

  If there is only one domain, the Global Manager will change the classification of an object when the domain changes it. For example, if IP Availability Manager discovers a device as a Probe, the Global Manager will create a Probe. If IP Availability Manager rediscovers the same device as a Switch, then Global Manager will delete the Probe and re-create the instance as a Switch.