When a topology split is invoked, the topology-split driver runs scripts that perform core topology-split tasks, as described in “Core topology-split functions” on page 18. If IsTopoSyncEnabled and EnableAutoEdgeManagement are both TRUE (and IsTrialLearningEnabled is FALSE), additional scripts run, such as the ones that perform the following tasks:

  • For each domain, build a table that contains entries for network adapters on proxy devices that are associated with connections that are not fully managed by the specified domain.

  • Forward the respective tables to the respective IP Availability Managers.

    In each domain, during the postprocessing phase of pending discovery, the domain’s IP Availability Manager performs the following tasks:

  • Sets a flag on any protocol endpoint (IP or MAC, for example) that is LayeredOver any network adapter that has an entry in the table.

    The flag is a new attribute, named ForceLocalManagement, for protocol endpoints. ForceLocalManagement is FALSE by default.

  • Unmanages each network adapter that has an entry in the table.

    Because of the set ForceLocalManagement flag, the unmanaging of the network adapters does not unmanage any protocol endpoints that are LayeredOver the network adapters. Without the flag, the unmanaging of a network adapter will unmanage any protocol endpoint that is LayeredOver the network adapter.

    The IP Availability Manager keeps a list of protocol endpoints for which it has set the ForceLocalManagement flag. After all network adapters that have entries in the table have been unmanaged, the IP Availability Manager checks all instances of protocol endpoints and clears the flag on any protocol endpoint that is not in the list. This behavior ensures that ForceLocalManagement is FALSE on any protocol endpoint that might have had ForceLocalManagement set during an earlier topology split but no longer needs it set.