dCloud pre_yarn
- Zane England
This lab guide is for use with the yarnlab dCloud for wrangler_ “Webex Dedicated Instance (DI) Wrangler tool (partnering with Yarnlab)” Cisco dCloud (note that it is availible in other regions also)
The pre_yarn lab guide below uses the same VM but you do not have to complete the wrangler_ lab as a prerequsite to this lab
preYarn
Preyarn is an application targeting Cisco partner presales engineers. It is a freestanding application running on a Windows or Mac PC that pulls configuration from a CUCM cluster, then analyses it and provides a summary of the configuration to assist in giving an accurate view of the system to assist in the quoting of a migration.
In addition to Configuration analysis providing insight into CUCM configured devices and features, it also provides EOL advice and MPP compatibility on end devices, usage analysis of licensing, registered devices at a point in time, firmware versions.
Furthermore, CDR data is analysed to understand Trunk and bandwidth (erlang) requirements, intersite traffic, Inactive lines
Preyarn can also provide an export of data in a Webex MT load format to assist in the migration of data from CUCM to Webex MT, providing CSV loaders for Users, Devices and other into Control Hub and also a summary of location specific data such as number range parsing to assist in the configuration of locations.
Setting up preYarn
Open the preYarn application from the dCloud desktop.
Enter Encryption credentials, these credentials can be anything but needs to be used in consecutive uses of preyarn, then select
Press
, enter details for CUCM Publisher, then select
Label: | Any descriptive name for source CUCM |
CUCM Address: | 198.18.133.3 (IP address of source CUCM Pub) |
CUCM Port: | 8443 (TCP Port to access CUCM Pub) |
Username: | Administrator (AXL user ID with a capital A) |
Password: | dCloud123! (AXL Password) |
preYarn Analysis
Now highlight the server just added from server list, then highlight the server just added from Server List, select
A check will now take place ensuring that the connectivity to CUCM is OK, select
Now choose path where the created analysis file will be placed
, then define the file name as required, or accept the prepared name, select
Now select the default country for the phone numbers, noting that countries may be also be selected on a site (Device Pool) basis, then
On completion of the analysis, The analysis result page details the extracted and analysed data, including start and finish time of analysis, duration of the same and the location of analysis file. Below this, there are four buttons for export of output to Excel, Analyse Phones, Analyse CDR and Create Webex Calling export.
Select
which will pull configuration directly from all physical phone handset, including serial numbers and versions, this info is then used to determine MPP compatibility of the handsets and more.
Note: Handsets must have Web enabled to allow for the Analyse Phones functionality
CDR Analysis
CDR file
This file has some generated calls from a prior lab (generated using test_mate) that shows the CDR analysis process with some data
To Analyse data from CDR, select
, then define the path where CDR data file/s exist
Note: the CDR must be extracted manually from CUCM and file/s placed in directory that can be accessed from the preYarn application
Now define the timeframe for CDR analysis, then select
On completion of the CDR, all the analysis data may be viewed on the summary page, it is divided into two sections with the top section displaying a brief summary of analysed data that may be expanded and details viewed by selecting the corresponding
button
Further down the page is a more detailed view of the findings
Export of Analysis
The data from the analysis may be saved in an Excel file by selecting
, then selecting the path where the sheet will be stored
Webex Calling MT Export
To create a Webex MT export, from which the output CSV files may be used to import into Webex MT Control Hub, select
, this will bring up screen allowing for the mapping of CUCM Device Pools to Webex Calling Locations, the specification of a default Webex Calling Location and subscription ID
Further down the screen, toggles and freeform text to globally define features and settings that cannot be mapped from CUCM data. Select toggles and enter freeform text as required, then
Select folder for the export
In the folder defined in output path from previous, find CSV files for User and Device Load and a report file with additional info to assist with the load into Contol Hub
If any of the settings need to be changed for individual users, this may be completed by changing manually in the CSV as required before importing to Control Hub