Migration path from cdm mcs template 5.80 to 6.43 enhanced
search cancel

Migration path from cdm mcs template 5.80 to 6.43 enhanced

book

Article ID: 139945

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) DX Unified Infrastructure Management (Nimsoft / UIM) Unified Infrastructure Management for Mainframe CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

This document covers the correct path to follow in order to migrate from the CDM MCS template 5.80 to 6.42 Enhanced.

Environment

Release : 9.2.0, 20.3

Component : UIM - MON_CONFIG_SERVICE

Resolution

CDM Migration Path: 

Legacy 5.80 -> Legacy 6.30 -> Legacy 6.34 -> Legacy 6.42

Legacy 6.42 -> Enhanced 6.42

 

Different Template Version and Corresponding Packages:

Serial Number Template Name 5.80 6.30 6.34 6.42 6.42 Corresponding Enhanced Template Name 6.42 Corresponding Enhanced Template Version Comments
1 CPU Monitor 2.33 2.49 2.50 2.54 CPU Monitor (Enhanced) 6.42.1  
2 Memory Monitor 2.36 2.43 2.44 2.48 Memory Monitor (Enhanced) 6.42.1  
3 NIC Monitor 1.7 1.18 1.19 1.23 NIC Monitor (Enhanced) 6.42.1  
4 Setup CDM 1.29 1.40 1.42 1.46 Setup cdm (Enhanced) 6.42.1  
5 Default Disk(s) 2.32 2.52 2.53 2.56 Default Disk(s) (Enhanced) 6.42.1  
6 Disk(s) 2.36           There is no corresponding Enhanced profile. Similar configuration can be achieved by using Default Disk(s) (Enhanced) and Disk(s) (Enhanced) child profile.
7 Iostat   1.11 1.12 1.16 Iostat (Enhanced)  6.42.1  
8 Iostat Devices              
9 Disk IO Monitors   1.10 1.11 1.15 Disk IO Monitors (Enhanced)  6.42.1  
10 Shared Disk(s)   1.04 1.05 1.09     No Corresponding Enhanced template

Additional Information

From CDM 5.80 to 6.30: Migration is not supported for Disk templates from cdm 5.80 to cdm 6.30. If you are using cdm 5.80, you must delete Disk profiles and must re-create the child template for Default disk. You can migrate other templates such as CPU and memory.