Spectrum OneClick server host migration while integrated with Performance Management

Products

• CA Spectrum
• DX NetOps
• CA Performance Management - Usage and Administration

Issue/Introduction

There is a need to migrate the Spectrum OneClick tomcat web server from it's current host to a new host.

This OneClick server is currently integrated with Performance Management as a Data Source.

In this instance Performance Management Group membership is based on Rules that look to the synchronized Spectrum Global Collections for members. In turn those Performance Management Groups are set as the source for many Dashboards, On-Demand Reports and Scheduled Reports. This may also be the case for Collection Groups.

As a result any interruption to these membership rules and the integration would cause a serious issue with rebuilding the rules.

Maintaining this relationship between the integrated products is critical to successful integration.

Environment

Release: All Supported Releases

Component: SPCINT - Integrations

Resolution

NOTE: Starting from DX NetOps Spectrum 21.2.4, the default root password for MySql is "MySqlR00t". For DX NetOps Spectrum versions prior to 21.2.4, the default root password is "root". In the following MySql commands, replace <PASSWD> with the root password for your DX NetOps Spectrum version.

Global Collection names and IDs are stored in the Spectrum SpectroSERVER SSdb. As long as the SSdb isn't rebuilt, those names and IDs won't change. 

 

As a result any Performance Management Group Rules referencing synced Spectrum Global Collections for it's membership should continue to function post OneClick host change. 

 

Move OneClick to new host with same name and IP

 

A) Disable Spec DS in PC to temporarily halt sync. 

 

B) Move OC to new host, load netqos_integ DB from old host in new. Ensure anything custom is also migrated per the Spectrum docs. 

 

B1) Stop tomcat 

B2) $SPECROOT/mysql/bin/mysqldump --defaults-file=$SPECROOT/mysql/my-spectrum.cnf -uroot -p<PASSWD>  netqos_integ > netqos_integ.sql 

B3) copy the sql to other machine. 

 

Note: If the netqos_integ database already exists ($SPECROOT/mysql/data/netqos_integ) you can skip B4 and go right to step B5

B4) $SPECROOT/mysql/bin/mysql --defaults-file=$SPECROOT/mysql/my-spectrum.cnf -uroot -p<PASSWD> -e "create database netqos_integ;"  

B5) $SPECROOT/mysql/bin/mysql --defaults-file=$SPECROOT/mysql/my-spectrum.cnf -uroot -p<PASSWD> netqos_integ < netqos_integ.sql 

B6) Start tomcat 

 

C) Re-Enable the Spec DS in PM 

 

Move OneClick to new host with different name and IP

 

A) Disable Spec DS in PC to temporarily halt sync. 

 

B) Move OC to new host, load netqos_integ DB from old host in new. 

 

B1) Stop tomcat 

B2) $SPECROOT/mysql/bin/mysqldump --defaults-file=$SPECROOT/mysql/my-spectrum.cnf -uroot -p<PASSWD> netqos_integ > netqos_integ.sql 

B3) copy the sql to other machine. 

 

Note: If the netqos_integ database already exists ($SPECROOT/mysql/data/netqos_integ) you can skip B4 and go right to step B5

 

B4) $SPECROOT/mysql/bin/mysql --defaults-file=$SPECROOT/mysql/my-spectrum.cnf -uroot -p<PASSWD> -e "create database netqos_integ;" 

B5) $SPECROOT/mysql/bin/mysql --defaults-file=$SPECROOT/mysql/my-spectrum.cnf -uroot -p<PASSWD> netqos_integ < netqos_integ.sql 

B6) start tomcat 

 

C) Edit the Spec DS in PM with the new name or IP and save the changes. 

 

D) Re-Enable the Spec DS in PM