Part Two: Verifying Scope with RSG-Out of Scope Services

Important:The product name for this user guide has changed from Foundation and Cloudscape to Business Service Discovery and Migration Planning. Previous UI pages known as Foundation have changed to Business Service Discovery. Previous UI pages known as CloudScape have changed to Migration Planning.

The initial and primary mechanism of setting the scope for is the discovery phase (as described in How We Collect). During this phase you will select the subnets to include in discovery and ensure you have access to the workloads contained within the boundaries of those subnets. However, additional scope validation can be performed post-licensing through a review of a special auto-generated application stack called RSG-Out Of Scope Services.

The following includes the steps needed for a detailed review of the RSG-Out Of Scope Services group. The level to which you will need to perform this is dependent on the need for true “discovery” of the environment. In other words, if you are leveraging the discovery aspects of the platform to find systems you may not know about or have documentation on, then you would perform this validation in detail. If you are running the Business Service Discovery and Migration Planning platform against a known subset of the environment, then a more cursory review of RSG-Out Of Scope Services may be sufficient.

•

Step One: Verify Whether Hosts Should Be Brought Into Licensing/Scope

•

Step Two: Make Sure There Are No Unlicensed Consumers

•

Step Three: Verify Whether the Out-of-Scope IPs Should Be Licensed

Step One: Verify Whether Hosts Should Be Brought Into Licensing/Scope

Iterate through the RSG-Out Of Scope Services group and verify whether or not the hosts in this group should be brought into licensing/scope. Our default advice is that everything in the environment should be licensed during the burst, so working through this group can be an important first step in ensure a complete scope.

Once you license the devices in the RSG-Out Of Scope Services group (or decide that they are to remain out of scope), you should re-run auto-grouping to make sure that the group is empty – or that all hosts can be safely ignored.

Caution:You should routinely re-run auto-grouping and check this group as new services may come online at any time.

Step Two: Make Sure There Are No Unlicensed Consumers

Make sure that there are not any CONSUMERS of services that are not licensed. This means going through the individual application stacks and checking their connectivity to “locations”. For specific definitions of locations please refer to our Glossary under the subsection Connectivity Definitions.

To check consumption of important services, click View All Connections when viewing the RSG-Out Of Scope Services stack. This will bring up a table of all group- to-group and group-to-location connectivity. Sort this table by the destination group such that the RSG-Out Of Scope Services group is the destination. Once sorted, on the far right of the table you will see a “View Details” link, you should click this link for the first location listed in the source column. This will bring up another table that you should then click the button in the top left of the table to show a protocol view. Review the listed protocols to understand connectivity and if there are important services being consumed outside of this group. You want to verify that the traffic is not on a well-known port or protocol name, such as MSSQL, oracle, MySQL, etc… To understand particular IPs that are communicating on a protocol select the “View Details” link on the far right of the table, this will bring up another table that lists out the specific IP addresses. You should verify this list to understand if those items currently not licensed should be brought into scope. Repeat these steps for every location group within the first group to group/location table.

Tip:If you have a large environment where going through all the AutoApp stacks would be too time consuming, then the best way to determine consumers of services out of scope is to run the auto-grouping with the 95th group and view this information against the RSG-95th Highly Connected Stack. The RSG-95th Highly Connected Stack is the top 5% of hosts by connectivity in the network. In other words, it is the list of servers that talk the MOST. The “hosts with the most” we like to say.

Step Three: Verify Whether the Out-of-Scope IPs Should Be Licensed

Verify whether or not the out of scope IPs that are CONSUMERs or are OFFERING important services described in Part Two: Verifying Scope with RSG-Out of Scope Services should be licensed. The group of the service host (the one offering the service) is inconsequential. The important thing is to determine if all of those hosts should be brought into scope and licensed as they may be front end servers or other applications that are accessing servers you are focused on. Once this process has been repeated, and there are not major connections in or out of the 3 major groups (Isolated Devices, RSG-95th Highly Connected Stack, and RSG-Out Of Scope Services), you can move on to application review.