When topology is split into multiple domains, connections that cross domain boundaries are broken. To monitor such connections to ensure proper correlation across all domains, the Topology Split Manager adds proxy devices, or replicated devices, to neighboring domains. Representation of a connection that crosses a domain boundary—Example provides an example.
The domain that contains the “real” device in its topology is said to “own” the device and has primary responsibility for managing the device. As such, the domain is responsible for managing all components of the device.
The domain that contains the “proxy” device in its topology has partial management responsibility for that device. As such, the domain is responsible for managing only those components of the proxy device that are involved in the “across the domain” connection from the proxy device to the device that is owned by the domain (Router C in Figure 3).
The Topology Split Manager determines the proxy devices for the domains, adds them to the domain seed files, and places them on the appropriate IP Availability Manager’s Pending Devices list for subsequent pending discovery. During the discovery of the proxy devices, and assuming that an operating feature called TSM hook script is enabled, the IP Availability Manager sets the Domain attribute of the devices to “Proxy.”