Scope transition mode

BMC Discovery uses scopes, a means of distinguishing overlapping IP addresses. All existing discovered devices are considered to be in the default scope. When you scan an endpoint, all scanned devices appear in the scan's scope and will be distinct from devices scanned in any other scope.

However, if an endpoint has already been discovered, and is then scanned using a non-default scope, this creates a duplicate inferred device. To avoid this, your BMC Discovery instance will use scope transition mode, where discovered endpoints that do not exist in the scan's scope are matched against existing endpoints in the default scope. If the endpoint is the same, it is updated, including the addition of the scope.

If you choose to use scope, you should leave the instance in transition mode until you have scanned the endpoints scanned by the BMC Discovery appliances or BMC Discovery Outposts where scope has been configured. There is a small performance overhead as endpoints are checked for existing endpoints in the default scope, so once you have scanned your estate, you should return the BMC Discovery appliance or BMC Discovery Outpost to full scope mode.

All AWS EC2 hosts have a scope whether discovered by using AWS Systems Manager or ssh. The scope is set automatically to the AWS VPC identifier by the discovery calls.

If you do not have overlapping IP addresses and do not scan EC2 hosts, you do not need to consider scopes.