Migration to NSM r11. © 2005 Computer Associates International, Inc. (CA). All trademarks, trade...

Migration to NSM r11

2 © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Agenda

- Migration Overview

- In-place Upgrade

- Parallel Upgrade

- Pre-Migration Considerations

- Worldview Migration

- Agent Technologies Migration

- Enterprise Management Migration

- Q&A


Migration Overview

- Unicenter NSM R11 supports direct in-place and parallel upgrades from Unicenter NSM 3.x

- Component data previously stored within multiple databases of MS SQL will be migrated to the new Ingres MDB

- Top-down and parallel migration approach continues to be a best practice


Migration Outline

1) Know your current architecture

2) Check hardware and software levels

3) Plan the new Unicenter NSM r11 architecture

4) Plan the migration approach

5) Backup!

6) Setup a test lab to simulate production environment

7) Deploy test machines to the production environment


Unsupported 3.1 NSM Components

- EM Problem Management

- EM Report Management

- EM File Management

- Worldview 3D Map

- Cleverpath Reporter

- GCU (Replaced by UCM).

- GCU supported for Agents that cannot be managed by UCM

- EM Security Management (Only file and logon based security policies are no longer supported)

In-place Upgrade


Migration – In-place


Upgrade

System automatically detects presence of NSM 3.x and force upgrade


Unsupported Components


Upgrade Considerations


Upgrade Considerations

- Unsupported Components

- System Performance

- CleverPath -> WRS


Pre-Selected Components

NSM 3.1 components automatically selected and cannot unselect them


eTrust Antivirus

eTrust AntiVirus will also be selected as it is installed on NSM 3.1

Watch the colour code for component selection


Ingres Server

Ingres server / client will be required


Components Selection


Ingres Configuration


MDB Configuration


3.1 Database Configuration


Directory Configuration


Reboot

Reboot will be required as some of the NSM 3.1 files will be in use


dbMigrate

- dbMigrate to migrate 3.1 databases to MDB

Parallel Upgrade


Dummy Registry


Parallel Upgrade


MDB configuration


3.x Database Configuration


3.x Database Selection


Response File – Enterprise Management


Response File - Worldview


Parallel Upgrade

Unicenter NSM Worldview Migration


Worldview Upgrade

- Parallel approach is recommended

- Increasing hardware requirements against expanding infrastructure

- Preserve existing NSM 3.1 Worldview

- Database Migration from MS SQL to Ingres MDB

- Dbmigrate utility can be used to migrate NSM 3.x TNGDB to a remote freshly installed Ingres MDB

- Upgrade CORes before the DSMs that report to them

- If running multiple CORes, upgrade central CORes before remote CORes.


Backing up Worldview

- Backup the TNGDB using MS-SQL backup utility

- If any customizations were made, backup the following WV directories:

- NSM\ICONS\

- NSM\IMAGES\

- NSM\MODELS\

- NSM\MAP\

- Unicenter Bridge

- Backup configuration .ini file (NSM\Bridge\Config)

- Configuration will require changes before they can be used in r11

- Unicenter BPVM

- Backup configuration .ini file


Worldview Migration Steps

1) Backup the NSM 3.x CORe (MS SQL Server Utility)

2) Backup any customized files, maps, icons, methods or cursor configuration

3) Note any customized environment variables

4) Designate a machine as the target NSM R11 MDB/Worldview server. Be certain that the server meets the proper prerequisites.



5) Begin the NSM R11 installation For in-place upgrades, the

migration will automatically be initiated and the TNGDB will be migrated to the Ingres MDB

For parallel migrations, following a clean NSM R11 installation, the dbmigrate utility should be used to import Worldview data to new Ingres MDB



7) After installation has completed, copy over the necessary customized WV files (icons .ico, bitmaps .bmp, etc)

8) Upgrade remote DSMs and Agents as needed.


Worldview Upgrade Considerations

- Upgrade the NSM 3.x CORes to R11 MDB prior to any Remote Admin Client (RAC) or Unicenter Explorer upgrades

- In a bridged environment, upgrade the “central CORe” to which other repositories are bridging first.


Worldview Migration Process

- By default, all classes and object will be migrated to the MDB except for the agent objects

- Agent objects will be recreated at time of DSM discovery

Unicenter NSM Agent Technology Migration


Agent Technology Upgrade

- The NSM r11 level DSM and Worldview are backwards compatible, able to manage 3.x Agents

- NSM 3.x DSMs can not communicate to an R11 Worldview server

- Database and other NSM 3.x Agents will be preserved and continue to operate within the r11 AT Common Services


Agent Technology Upgrade Overview

- First, upgrade the NSM 3.x WorldView/CORe to NSM r11 Worldview/MDB

- Then, the DSMs to which the Agents communicates

- Lastly, the Agents


Agent Technology New Functionality

- Gwipfltii.dat and Pollset Browser moved to DSM Configuration within MCC

- UCM – Enhanced GCU

- UCM uses DIA for delivery

- Migration allows GCU to operate against MDB to accommodate pre-R11 agents

- Adaptive Configuration (AC)

- Agents upgrades that include AC will retain configset and enter into Self-Adaptation mode

- DIA


Backing up Agent Technologies

- The following directories should be backed up:

- $AGENTWORKS_DIR\services\config\aws_nsm (DSM Policy)

- $AGENTWORKS_DIR\services\config\aws_wvgate (.WVC File

- $AGENTWORKS_DIR\services\config\aws_sadmin (sadmin store Config File)

- $AGENTWORKS_DIR\services\config\aws_snmp (SNMP Gateway Config File)

- $AGENTWORKS_DIR\services\config\aws_store (Object Store Config File

- $AGENTWORKS_DIR\services\config\awservices (Awservices config File)

- $AGENTWORKS_DIR\services\mibs (Agent MIB File)


Backup Agent Configuration Sets

- While the upgrade will retain the 3.x agent configurations, you may want to create a backup

- You may use the mkconfig utility:

- mkconfig agentName[@host] [-i instances] [name1….,nameN] >filename

- To load a configset, use the ldconfig utility:

- ldconfig [-h host] filename [-d level] [-f logfile] [mibname:configName]


NSM R11 Agent Conversion Utility

- If the caiWinA3 System Agent migration was not in-place, you may want to manually apply a NSM 3.x configset to a newly installed caiWinA3 System Agent.

- A utility must to be run to convert the configset to R11 standards:

caiW2kOsCvt 3.xConfigSetFile R11ConfigSetFileLocation: %AGENTWORKS_DIR%\AGENTS\BIN

- The Log Agent and Active Directory Agent do not require configset conversions

Unicenter NSM R11 Enterprise Management Migration


Enterprise Management Migration

- Enterprise Management now consists of:

- Event Management- Event Manager

- Event Agent

- AEC

- Universal Job Management Agent

- Job Management Option

- Alert Management


Backing up Event and Workload Management

- During in-place upgrades, database migration occurs during NSMR11 EM installation.

- Parallel migrations of Event and Workload policy require the backing up and restoring of data using the oprdb/cauexpr/cautil utilities

- Backup EM and Workload databases using MS SQL utilities or cadbbkup

- Event Console logs should be backed up and restored


Upgrading Enterprise Management

- Multiple Event Managers

- Upgrade central Event Manager first

- Multiple Event Workstations

- Upgrade Event Manager prior to upgrading Event Consoles

- Message Forwarding

- If you are forwarding messages from one or more consoles to a target console, upgrade the target console first

- Message Records/Actions are stored in the MDB

- Import NSM 3.x Event and Workload policy into NSM R11 using the cautil command


Event Agents

1) Upgrade Event Managers and Consoles first

2) Upgrade the Event Agent machine itself, or install a new Event Agent on a fresh machine.

3) Verify that the “master policy” Event server (the server from which the Event Agent gets its DSB) is correctly identified (especially if it has changed).

4) Execute an OPRELOAD to obtain an updated copy of the DSB


NSM Security Migration

- It is recommended as a best practice to install eAC over NSM 3.x prior to performing an upgrade of NSM

- On a machine with NSM 3.x security installed and no eTrust Access Control present, the install will:

- Upgrade automatically

- Create new security tables in CA-MDB

- Migrate asset rules from CADB to CA-MDB

- Access rules are preserved


Summary- Goal is to make migration easy and organized- Review current architecture and plan for the future- Top-down, parallel migration is best practice- Remember to backup- Migration Guide will be available to assist in

upgrading environments and preserving configurations

- Migration Guide will be available on http://supportconnect.ca.com

http://supportconnect.ca.com/

Questions & Answers

Date post:	26-Dec-2015
Category:	Documents
Upload:	barrie-dorsey
View:	218 times
Download:	2 times

Migration to NSM r11. © 2005 Computer Associates International, Inc. (CA). All trademarks, trade...

Documents