Rapid Discovery

For quick overview, please refer to the attached Discovery Process Flow: -

========================================================

Updated 03/11/2020

An Overview of a Scrum Board for Rapid Discovery Project:

Collect High Level Architecture and other
Artifacts
Kick-off meeting with Customer Team Leads, Project Manager & System Admins with
presentation on steps of Discovery Process.

Collect preliminary data such as Application & its groups, Server, Networking, etc. Compile the
data in Skymap upload .csv template after discovery scan phase

Explain the tentative questionnaire and involvement of App owners during the Data
Enhancement phase of the project.

Inputs

 Request for POCs (Point of Contacts) and Contact details of Customer’s Project manager,
Technical Lead, DBA Lead, System Admins, Application infrastructure owners, etc. and
set up Communication channel such as Teams, Chime, slack, etc.

Output

 High-level Architecture diagram which will include Applications, Servers, Storage,

Environment, Firewalls, Application groups, Network topology, inter-dependencies, etc

 Preliminary details on Database server clusters, Storage servers, Network Architecture.

 Understanding of in-scope and out-of-the-scope infrastructure.

1. Get Architecture Diagram

 You may get high-level architecture by requesting to customer’s lead DBA, System
Admins, Application infrastructure and owners, etc.

 Collect details on Database server clusters, Storage servers, Network Architecture

 Conversation with Chief Architect on High-level Architecture

2. Obtain rules and dump files from System Admins
Obtain Firewall rules and/or dumps from load balancer configuration files from system admin
which will provide us information about network topology, inter-dependencies of App Servers
and inventory.

3. Request CMDB Details from Customer

Request for Configuration Management database (CMDB) access. CMDB used to store
information about hardware and software assets. Using the CMDB, EQ will get preliminary
information about Applications and Servers.
Discovery Tool Deployment & Configuration
Select the Discovery Tool Reference Discovery Tools . Here, we have selected RISC Tool for
following pages.

 All RISC Networks engagements require a subscription and licenses.

Inputs

 RISC Networks subscription and licenses.

 Dedicated host for RISC and access credentials

Output

 RISC tool deployed and configured. Credentials applied. Ready to start the scan.

1. Prerequisites
Review/complete the Deployment Requirements. We are not having access to these
Deployment requirements
In addition to our quick start guide below, find more information on professional services please
contact info@riscnetworks.com

All RISC Networks engagements require a subscription and licenses.

If you do not have a subscription or if you have a subscription and need to purchase node
licenses, please contact your account manager or contact help@riscnetworks.com.

RISC Quick Start Guide

2. Create an Assessment
The first step to using the RISC Networks Platform is to create an assessment. Follow the
instructions below to get started.

1. Navigate to the RISC Networks Portal.

1. Log in or register if you don’t already have an account.

2. Click the +Add an Assessment button in the assessment list window.

3. Enter your subscription code in the field. If you do not have a subscription code, please
reach out to your account manager or to info@riscnetworks.com

4. Fill in the company information fields in the +Add an Assessment window, company
name will be the name of the assessment.

5. To invite other users, click the Invite button. You will be taken to the User Access
screen, where invitations can be sent via email. Users can also be invited later on. Click
Dashboard to return to the main screen.

6. Upon completion, you should see a pane with your new assessment.

RISC Quick Start Guide

3. Deploy the RN150

In order to start discovery we need to download and deploy the RISC Networks RN150 virtual
appliance.
 1. Click your assessment to open the Appliance Status page.

2. Click the Download RN150 button in the section titled: Step 1 - Download Virtual
Appliance.

3. While waiting on your download to complete, copy the code provided in the section Step
2 - Bootstrap Virtual Appliance with the Code in the Appliance Status page, and save
it where you can retrieve it at a later time.

4. When your download completes, extract the files to a safe place.

5. Follow VMware documented procedures for Deploying OVF Templates in your specific
version of VMware.

o Deploy OVF Template (Using VI Client in vSphere 5.1) vSphere 5.1

o Deploy OVF Template (Using Web Client in vSphere 5.5) vSphere 5.5

o Deploy OVF Template (Using VMware Player) VMware Workstation Player

6. Once the machine is deployed and powered on, you should see the RISC Networks Logo
and briefly see a white screen before being redirected to a log in screen.

RISC Quick Start Guide

4. RISC Configuration
Log in to the RN150

After powering on the RN150, you can log in and accept the RISC Networks End User License
Agreement. In the top right corner of the page is the IP address of the appliance which can then
be navigated to via a web browser. We recommend accessing the RN150 through your web
browser as copy/paste may not be available through the hypervisor console. Open your browser
of choice and navigate to the IP address. Once the site has loaded, you can close the
hypervisor console. Follow the instructions below to log in.

1. Enter your username (Email address).

2. Enter your password.

3. Go to the box on the right to read the eula. Scroll to the botton.

4. Elect whether or not use professional services.

 5. Accept the End User License Agreement.

6. Click Login.

RISC Configuration Steps:

 Add subnets which the RISC appliance RN150 needs to scan (EQ)

 Check the deployment requirements: that the ports and protocols allow the RISC
installation on VMware on the customer's network (EQ)

 Get required credentials for the RISC installation (EQ)

 Install RISC on VMware on the network. In the case of different environments, install
different appliances (EQ and Client)

Inputs:

 RISC subscription (EQ on Client’s behalf)

Output:

 RISC installed and ready for scan (EQ)

Customer’s Obligation:

 Dedicate 1 or 2 vCPUs in network for RISC installation, 8GB RAM, 50 GB Hard Drive
(thin Provisioned)

 Required internet access, port and protocols for RISC network, WMI, SSH, SNMP

 IP subnets client likes to scan

 VMware credentials

 Database credentials IP/SIDs

 Give Preliminary list of Assets (hostnames and application) to EQ. This is optional;
however it will be useful to match the RISC output with expectation.

RISC Quick Start Guide

5. Enter Information and Credentials

Enter Your Assessment Key

Now it is time to enter the assessment key we copied in "Deploy the RN150" above. Again, we
recommend using the RN150 in a browser window because copy/paste may not be available in a
hypervisor console.

1. Enter your assessment key.

2. You will be prompted to choose whether or not you are using FlexDeploy. If you are
unsure, click no.

3. If you are using Flex Deploy, enter the network address of the FlexDeploy appliance you
have previously set up

Enter Subnet Information

Now it is time to enter Subnet information. We can’t go any further without entering at least one
subnet. There are three options for entering subnet information. You can enter a subnet
individually, populate from a routing table, or populate from a .csv file.

Click the Subnets link on the dashboard page.

1. To enter subnets individually, enter a network address >> select Subnet Mask from the
dropdown >> Click Add

2. To populate from a routing table, click Populate from routing table >> at the prompt,
select the version of SNMP you are using >> enter your credentials

3. To enter subnets using a .csv file, click Populate from CSV >> click Choose File and
browse to your subnets.csv file >> select the file and click Open, and click Upload

1. The file must be under 1MB and formatted as either network address/CIDR
prefix, or network address/CIDR prefix new line. (ex.
63.146.167.192/26,65.125.73.180/30)

4. In the table below, make sure to select all of the subnets you wish to scan.

After you have confirmed that you have selected all subnets for which you want information,
click the Dashboard button.

Enter SNMP Information

1. Click the SNMP link on the dashboard page.

 2. Enter an SNMP string in the input box, or click the Add SNMP Version 3 button if you
are using SNMP version 3 >> click Add

3. Enter the IP address. and click Test

4. After testing successfully, click Ok and return to the dashboard

Enter Windows Credentials

Be sure to enable netstat application socket collection in order to collect and view workload
dependencies. Refer to the Windows Collection Module for more information.

1. Click the Windows link on the Dashboard page.

2. Enter the domain for your credential, optional.

3. Enter your user name and password.

4. Select an option for application socket collection.

5. We recommend you select Enable >> confirm your choice >> click Next >> Select
whether you want to enable this feature on workstations.

6. Click Add

7. Click Test to verify your credential. We recommend testing all credentials. This helps
ensure we collect information on all relevant devices and prevents problems later on.

8. After receiving confirmation that your credential is correct, click ok and either add more
credentials, or click the Dashboard button to go back to the main page.

We recommend testing all credentials prior to starting a scan. This ensures information is
collected on all relevant devices the first time, and that the complete set of analytics is available.

Enter VMWare Credentials

It is time to enter your VMWare credentials

1. Click the VMWare link on the Dashboard page.

2. Enter a network address

3. Confirm you are hitting the right port. The default is port 443.
 4. Enter a username and password

5. Click Add

6. Click Test to verify your credential

7. After receiving confirmation that your credential is correct, click ok and either add more
credentials, or click the Dashboard button.

Enter SSH Credentials

It is time to enter your SSH credentials

1. Click the SSH link on the Dashboard page.

2. Enter the username for the credential in the Username field.

3. From the drop-down list entitled Credential Type, select the type of authentication
desired.

1. If Password is selected, an additional entry field will be presented, in which the

password should be entered.

2. If Public Key is selected, a text input field will be presented. The full text
contents of the private key associated with the credential should be pasted here.

4. Click Add.

5. Click Test to verify your credential

6. After receiving confirmation that your credential is correct, click ok and either add more
credentials, or click the Dashboard button.

Additional Credentials

The RN150 supports additional credentials under the sections Cisco CallManager, Cisco
Discovery Services, and Additional Credentials. The Additional Credentials sections can
contain Database Credentials if that is enabled, and CLI for Cisco Devices. If you have these
credential types or if they are relevant to your desired analysis then please enter them, otherwise
proceed to the next section.

Complete Bootstrap and Start Scan

 1. After entering or opting out of all credential categories, You have the option to start the
assessment. Click the Start Assessment button.

2. You will be prompted to confirm your settings. Confirm that all of the credentials you
entered are accounted for in this pop up.

3. Click Start.

4. You are done for now. You will receive an email when the discovery process is complete.

You have now completed the RN150 setup. You will receive an email when the discovery
process is complete.

Discovery Scan
Run Discovery scan on selected ports, match credentials with devices

Check for expected server counts. In case of difference, repeat the scan a few times. Trouble
shoot for accessibility or protocol issues, if any.

Inputs

 RISC Readiness

 Configured host for RISC and applied credentials

Output

 Hardware, Software and Operational information of servers. For details on Windows,

Linux/Unix, database, VmWare see output page. Discovery Scan Output

1. Start RISC Discovery Scan

Steps:

 ICMP sweep (opt-in subnets)

 Select port scans, match credentials with devices

 Check for expected server counts. In case of difference from preliminary data, repeat the
scan a few times. Trouble shoot for accessibility or protocol issues, if any.

 Revisit interesting workload specific data

 Interface with vCentre (give credentials)

 May be repeated multiple times as scope is refined

Customer’s Obligation:

 Once RISC output comes, match with the expected result.

 The output will be showing isolated devices too such as printers, network devices,
standalone PC, etc.

 Customer needs to define the assets under the scope for further Performance Scan

2. Review Assets and Request Rescan

You will receive an email notifying you that the scan is complete. Once you receive this email,
you should review your assets to verify that all devices that are in-scope for the assessment are
accessible. We have more detailed documentation on the discovery troubleshooting and the
process in general here:

Discovery: How to

We recommend reviewing the page above before proceeding so you understand the resources
available.

1. Log in to https://portal.riscnetworks.com and select your assessment.

2. Click the Consume Intelligence dropdown >> click Assets

 3. Verify all devices and subnets are in scope and in scope devices are accessible (i.e. Make
sure Windows Servers are in the “Windows Devices” section and not under “Inaccessible
Devices”).

4. If needed, go back to the RISC Networks RN150 appliance and add missing credentials
and click the Request Rescan button as needed.

License Devices for Data Collection

Now it is time to license devices in your network to start data collection. You may or may not
want to license everything. For instance, you may want to license Windows Servers only or,
devices in a certain ip range. You can do this by filtering the list of devices in the licensing page.
Generally, it is recommended that all devices whose device type contains "server" should be
licensed. These are devices that we are collecting both performance and dependency data on as
we have OS level access.

1. Log in to https://cs-portal.riscnetworks.com and select your assessment.

2. Click the Collect Data dropdown >> click Licensing

3. On the Core Licensing tab, filter to the devices you would like to license (you can apply
filters by clicking the down arrow in a column header and enter a filter value).

4. Depending on your subscription you may need to select the Start 30 Day Burst button to
make your licensing available (this activates a clock which makes the burst licensing
available for 30 days)

5. To license check the License box.

6. Devices will start collecting as soon as they are checked. Uncheck the device to remove it
from collecting.

Next Steps

You have completed the quick start. After you have collected a sufficient amount of performance
and dependency data it will be time to proceed to the Application Review Process.
3. Discovery Scan Output
Export Performance Scan Output. The data may consist following details:

Inventory via Inventory

Inventory Inventory Inventory
SNMP & SSH (Network
(Windows) (Vmware) (Database)
(Linux/Unix) equipment)
Hardware Hardware Hardware Hardware Database
Information Information Information Information Information
Serial Number  Physical Memory Serial Number Server Model Hostname
Physical Memory Physical CPU Line Cards CPU Version
Physical Hard Network Schemas
Physical CPU Flash Size
Drive Connectivity Names
Physical Hard Physical
Network Interfaces Memory Size Connectivity
Drive Memory
Interface Disk Table
HBA Information  
Information Information Metadata
Network Card ENTITY-MIB
     
information information
Software Software Software Software
 
Information Information Information Information
OS Version OS Description Software version OS Version  
Installed Installed
Applications and Applications and DataStore
versions with versions with Flash file list mapping to  
process ID process ID hosts and guests
information information
Windows Services
Logical Disks Guest Inventory  
and status
Logical Disks Filesystems ESX Location  
HTTP get on port
Windows Shares Host Inventory  
80
HTTP get on port
  OS Version  
80
       
Operational Operational Operational
   
Information Information Information
Windows Event Virtual Switch
  Routing Table  
Log information  configuration
Citrix Metaframe
  ARP Table    
Server Inventory
L2 Forwarding
       
Table
Neighbor
    Information (CDP,    
FDP, LLDP, etc)
Spanning Tree
       
Topology
SAN Switch
Forwarding
    Information    
(WWN Names,
etc)
SCSI Lun
    Information (FC    
Switches only)
Quality of Service
       
Configuration
Cisco IP SLA
       
Configuration
Cisco Netflow
       
Configuration
Performance Scan
RISC Discovery scan output may contain information on isolated devices such as printers,
routers, network devices, standalone PC, etc. Customer needs to define the assets for further scan
for dependencies and application stack/group.

Performance scan is an iterative process with repetitive AppStack building

Inputs

 Discovery output. Defined assets under the scope for further performance scan.

 Output

 CPU Process specific performance metrics

 Memory & Disc Utilization I/O

 Network Flow Information & Network Interface Utilization

 Connectivity

1. RISC Performance Scan

Steps:

 Apply licensing on under the scope servers

 Build the application stack and collect ongoing dependency and performance data

 Review or Check for expected Application Stack details. In case of unexpected results,
rebuild stacks a few times. Continue until assessment is ended

Inputs:

 RISC RN150 Licenses

Customer’s Obligation:

 Review the Performance Scan output and match with the preliminary asset file.
  In case of unexpected app stacks, trouble shoot

2. AppStack Build Process

RISC Performance gives application groups and connectivity. This is an iterative process. Work
closely with customer and build-rebuild AppStack until it gives desired result. Refine and
validate the app stacks.

3. Performance Scan Output

Export Performance Scan Output. The data may consist following details:

Performance via
Performance Performance Performance Performance
SNMP & SSH
(windows) (network) (Vmware) (Databse)
(Linux/Unix)
CPU Utilization
Statistical
CPU Performance CPU Performance (wait time, Connectivity
Information
ready time, etc)
Process specific
Memory Memory
Performance
Performance (bytes Utilization Table Names
metrics (CPU,
used / % used ) (usage MB, etc)
Swap, etc)
Memory Interface Disk Utilization
Performance (bytes Physical Disk I/O Utilization and (I/O / sec,
used / % used) Error Statistics bytes/sec, etc)
Disk (Logical and
CPU and
Physical) Network
Memory
performance (I/O Running Processes Utilization
Utilization
per sec, I/O bytes, (bytes in/out)
Statistics
latency, etc)
Socket Connectivity
Windows Network
Information (uses
Interface Cisco MQC
TCP-MIB via
Utilization (I/O Statistics
SNMP / prefers
bytes, etc)
RFC 4022 version)
Windows Process Network Interface IP SLA Statistics
Information Utilization (TrafficSim)
Windows Netstat
Netflow flow
Connectivity
information
Information (opt-in
(TrafficWatch)
only)
DNS A records and
C names where
applicable

Attached below is an example of Discovery result file, after compilation

Application-Stack Building & Group
Mapping
RISC performance scan will identify Application groups with anonymous names for ex.
Appstack1, Appstack 2, etc. Customer needs to identify the group and give a user-friendly name
for ex. SIS, CMS, etc.

Inputs

 Performance output exported in excel spreadsheet

 Output

 Validated Application-server mapping. Defined Appstack/App group

1. Application Stacks Review

Work with customer to complete server-application-stack mapping (interviews with application
infrastructure owners)
Inputs

 RISC performance output

Output

 A spreadsheet having detailed server data with the corresponding application name

2. Identify app owners for each application

You have to involve customer to Identify app owners for each application and provide their
email addresses.

3. Refine and validate the app stacks

Once Risk networks builds all the app stacks you will involve the customer to Identify app stacks
and verify that all the dependent servers are included in app stack and rename them with user-
friendly titles. Risk network by default provides random names to the appstacks which are to be
changed by the user in this phase .

 
Skymap readiness & Data Enhancement on
Skymap
Once the Risk network tool is done with all the discovery we will get the Risk output and
populate the skymap csv file template which is available on skymap . we will get information
from the risk network discovery output and from the customers CMDB and populate the required
skymap csv template once we are done with this we will upload that template on skymap and
after that we will .Work with customer to update the required details on server and application
page. If necessary, interviews with application infrastructure owners. We can get the skymap
template from skymap as shown in the image below

Inputs

 Spreadsheet from RISC after application review and app stack grouping exercise.

Output

 Updated data on Skymap - Application and server page. With environment (stack)
mapping
1. Data population on Skymap
Application & Server Data upload on Skymap

First step Define the criterion those are decisive for Application migration planning. Some
information might not be derived from RISC output. This information will need to be fulfilled by
Application owners, Server Admins, DBA lead and/or Project Manager from customer side.
Create those fields on Skymap under custom fields.

Some of the commonly used Criterion fields are: -

Data
Asset Type Field Name
Type
Server Location string
Server Manufacturer string
Application Database Size >5 TB (Y/N) yes/no
Application Acceptable Downtime (in hours) string
Application Publicly Accessible Application? (Y/N) yes/no
Application DBA Lead string
Application DBA Lead Email string
Application Owning Organization string
Application University Service string
Application Blackout Dates string
Application Application Dependencies string
Application External Integrations (0, 1-3, 3+) string
Application Highly Visible Application? (Y/N) yes/no
Application Business Owner string
Application Business Owner Email string
Application Using Shared Storage (Y/N) ? yes/no
Application Load Balanced Application (Y/N)? yes/no
Application Preferred Migration Days/Times string
Application Replicated For DR ? (Y/N) yes/no
High Utilization Window/ Application Utilization
Application string
Requirements ?
Application Multi-Tenancy Or Dedicated Host string
Application Database Interoperability Requirements string
Application Provide Logging Requirement string
Application Stateful Vs Stateless string
Application Application Constraints string
Server Inbound Ports string
Server Inbound Connections string
Server Outbound Connections string

Inputs

 CMDB files collected from customer in the starting of the project

 Spreadsheet having RN150 output, application names, and app owner details

Customer’s Obligation:

 In case Application Owner requires, more reviewers can be added to review or edit the
Application on Skymap. Reviewers may have ‘read only’ OR ‘read & write’ privileges as
specified by the client.

 Application Reviewer will be able to review or update only the assigned applications.

 Technical owner or DBA lead can be added as reviewer as well if required by App
Owners.

2. App Owner Name & Email Correctness

Once we receive all the discovery data from Risk networks & Customer on Skymap. Check that
all the Applications have its Application Owner Name correctly described. It should have his
Email ID and preferably contact number. Review and get it validated from Customer Project
Manager.
This step can be simultaneously done since the beginning of the Discovery Project (optionally).
Once we receive CMDB from customer, data can be uploaded on Skymap before even the RISC
output comes because Risk output can take Several weeks and we can ask App owners to update
the information on their respective applications on Skymap. This will save time later on.

3. Inviting App Owners on Skymap

Step 1: An informational email should be sent to all the Application owners, Technical owners,
Server admins and DBA leads should be sent from client’s Project Manager. The email should
inform them about ongoing Discovery Process and their role of updating the data on their
respective fields on applications or servers owned by them. Email should inform app owners to
accept the “User Invites” from Skymap and create different password for their login. If required,
a “Skymap User Guide” attachment can be added in that email.

Reference attachment here consists of similar file for NYU (Please don't share the file prepared
for NYU to other parties. Prepare a similar one for that customer)

Step 2: After Step 1 all the App owners will be sent ‘Skymap User Invites’ from Skymap
console.
4. Notification for Application Update to App Owners
Once majority of the App owners accept the invite from Skymap, an additional email should be
sent from EQ prompting them to review, edit and update the information for the application
assigned to them on Skymap. This email can either be auto sent from Skymap or manual having
name and url link of the application owned by the corresponding app owner.

If App owner needs, he can invite other reviewer on his application. This can be technical owner,
DBA lead, Technical owner or anyone else. but this reviewer also needs to have login access
(user invite) on Skymap. EQ co-coordinator shall provide that access email to reviewers.
5. Application Data Enrichment Review and Validation
Review the data enhancement on Skymap. If any App owner has not updated his application,
follow up with him or bring into knowledge of their Project Manager and get it done.

Application Prioritization
EQ Technical lead and team will define the criterion for migration wave planning and respective
weight for each criterion. Accordingly following prioritization steps will be followed.

1. Define Criterion for Prioritization

2. Assign Weight to Each Criterion
3. Map Criterion and Process Mapping
4. Review, Modify or Enter values in unmapped criterion

Attach priority chart

Inputs

 Criterion values from Skymap Application page

Output

 Prioritization Score and Rank for each application, based on it the wave planning will be
done
1. Review of Criterion Weight and Scoring Strategy
Review and validation of prioritization criterion weight and scoring strategy with customer
before starting scoring and ranking
2. Define Criterion for Prioritization
Step 1: Define criterion for prioritization based on Application questionnaire/criterion decided by
EQ Technical lead

3. Assign Weight to Each Criterion

Step 2: Give relative weight to defined criterion

4. Map Criterion and Process Mapping

Step 3: Map the criterion with Application page of Skymap. and “Process Mapping”

5. Review, Modify or Enter values in unmapped criterion

Step 4: Review values on criterion fields. This input is brought from application page.

Modify or enter values in any of the criterion that has no mapping link to application page fields.

For instance, any of the server page fields)

Migration Wave Planning
After creating project on wave planning page on Skymap proceed for wave planning. Auto
assign will create wave planning based on App-environment stack & Prioritization score. Current
default system assigns servers in order of: “ Dev >> Test or QA >> Stage >> Prod or others “
That means servers with Dev environment of all applications will be assigned in initial waves,
however, Servers with Prod environment of those applications will be assigned in last few
waves.

You can manually drag and drop the cards to change the auto -assigned wave.

Once the wave plan is finalized, get it reviewed by the customer. Do necessary alteration and
then assign them to the wave. Once you hit the assign servers button, then you lose the wave
planning board. You will see a new task board with assigned servers on unscheduled column
(getting ready for migration) Wave List will show the list of the servers per wave. To change the
wave for particular server, go to server page and change the assigned wave there.

Inputs

 List of Applications with Prioritization Score.

Output

 Task Board with unscheduled servers for migration

1. Create a project
Create a project on Wave planning page of Skymap. Define start date, end date, wavelength,
number of servers per wave, etc. This can be edited if required later.

2. Start wave planning

Initiate Wave planning can be done based on Application or Stack.

Auto Wave Assign will plan waves based on logic- Dev>QA(TEST)>Stage>Prod. That means
initial waves will have servers with Dev environments whilst Prod environment will go in last
few waves.

Manual drag and drop will help to change the wave assignment.
Discovery Result
Once the wave planning is done. Work out on Migration strategy for the in-scope servers. Define
the servers for Replatform, Retire, etc. Find out Run rate cost for the servers under ‘Rehost'.
Share the Discovery result with customer and do necessary changes as per customer’s feedback

Inputs

 Validated Task board and Application as well as server details

Output

 Final Result.

 Server to Application mapping, Migration R strategy, Estimated Monthly Cost, Storage

and Compute Cost, Connectivity and Wave plan for in-scope servers.

An example of Discovery Result is attached for reference. The final worksheet comprises of
Summary, Application-server mapping, Wave plan, Connectivity, Migration strategy, EC2 right
size mapping, R strategy, and cost per server/ Application, etc. The output can be slightly
different for various customers.

Attached below is a real business case of NewYork University, Jan. 2020

1. 6R’s Migration Strategy
Migration strategy based on 6R’s will be performed at high level- Rehost, Refactor, Repurchase,
Replat form, Retain, Retire.

Migration Patterns

2. Tweaking final Wave Planning

The wave planning draft will be prepared and discussed with clients; upon approval, it will be
configured on the Skymap Kanban board, the migration enhancement tool

3. EC2 Right Size Mapping & Cost Calculation Using AWS MPA
Use cost calculation tool such as AWS MPA. Enter the RISC output and it will give you cost for
servers under the scope.

AWS Migration Portfolio Assessment (MPA)

Available with AWS Professional Services and APN Partner services

Detailed portfolio assessment (server right-sizing, pricing, TCO comparisons, migration cost
analysis) as well as migration planning (application data analysis and data collection, application
grouping, migration prioritization, and wave planning) can be done online using Migration
Portfolio Assessment. The service is available free of charge to all AWS consultants and APN
Partner consultants. Configuration management database (CMDB) and application portfolio data
in varied formats can be imported into MPA with a web-based data ingestion process. MPA
offers extensive configurability and enables experienced consultants to model customers’
scenarios and generate data for business case analysis and migration planning.

Currently, the MPA application helps to create a consolidated view of a customer's on-premises
IT (server) assets, recommend migration strategy, estimate AWS usage cost for equivalent AWS
services, prioritize applications, group applications and create a migration plan.

 OS Name, CPU (Processors), Cores (Per Processor), Ram, Peak CPU Utilization, Peak
Ram Utilization, Server Usage %, Physical/Virtual, Server Usage (Uptime), Storage
Total Disk Size, and Storage Utilization are highly recommended for TCO analysis.
Whenever these fields are not provided, TCO will use industry standard values.

 Map Physical/Virtual attribute if your portfolio consist of physical and virtual servers.
'Physical' is the default value for the server. For Physical server, map Number or CPU
 and Number of CPU for accurate TCO, in case you don't have processor information,
map total CPU to Number of Processor. For Virtual Server, CPU count can be in Number
of CPU or Cores Per Processor.

 Select correct Unit of Measurement (TB, GB, MB, KB, or Byte) for Storage and Memory
attributes, and (Ratio, Percentage) for utilization attributes. UofM should be available in
the input file or check with customer.

Sample template as below:

What is the EC2 target right size mapping (AWS Server Recommendation)?

MPA takes server utilization data and maps the source server to a reasonably sized EC2 instance.
The tool assumes all processors are equal - comparisons are not based on performance
benchmarks; but does take into account how much of the provisioned resource is in use (average
or peak).

MPA calculate EC2 price for all payment types and recommend the cheapest the option

1. On-Demand - EC2 Rate Per Hour * 365 * 24 * TCO Duration (Years) * Server Usage %

2. 1 Year All Upfront - Upfront Cost * TCO Duration (Years)

3. 1 Year Partial Upfront - Upfront Cost * TCO Duration (Years) + Monthly Cost * 12 *
TCO Duration (Years)

4. 1 Year No Upfront - Monthly Cost * 12 * TCO Duration (Years)

5. 3 Year All Upfront - Upfront Cost * Roundup (TCO Duration (Years)/3) * TCO Duration
(Years) / 3*Roundup (TCO Duration (Years)/3)
 6. 3 Year Partial Upfront - (Upfront Cost * Roundup (TCO Duration (Years)/3) * TCO
Duration (Years) / 3*Roundup (TCO Duration(Years)/3)) + Monthly Cost * 12 * TCO
Duration(Years)

7. 3 Year No Upfront - Monthly Cost * 12 * TCO Duration (Years)

4. Final Discovery Results Sharing with Customer

Compile the R’s strategy and Run-time cost in a spread sheet. Bring out Summary of servers
under various R’s, environments, strategy, etc.

Share Discovery Results with Customer

An example of Discovery Result is attached for reference. The final worksheet comprises of
Summary, Application-server mapping, Wave plan, Connectivity, Migration strategy, EC2 right
size mapping, R strategy, and cost per server/ Application, etc. The output can be slightly
different for various customers.

Attached below is a real business case of NewYork University, Jan. 2020