Cisco Cisco Content Delivery System Manager Installation Guide

Step 3

Add IDX_B to the Primary JS node and remove IDX_B from the Secondary JS node again.
Primary JS Node

a) Log in to the Primary JS node (login as bnisplunk user)

b) cd /opt/splunk/etc/deployment-apps/CDN_JS/bin

c) Add IDX_B and IDX3, using the following commands:

/opt/splunk/bin/splunk cmd python configure_search_heads.py add IDX_B

/opt/splunk/bin/splunk cmd python configure_forwarders.py add IDX3
Secondary JS Node

a) Log in to the Secondary JS node (login as bnisplunk user)

b) cd /opt/splunk/etc/apps/CDN_JS/bin

c) Remove IDX_B and add IDX1, using the following commands:

/opt/splunk/bin/splunk cmd python configure_search_heads.py remove IDX_B

/opt/splunk/bin/splunk cmd python configure_forwarders.py add IDX1

Step 4

Stop Jboss process in the Secondary Core, UI, and CDN Manager nodes.
a) Log in to Core, UI, and CDN Manager nodes (login as bninet user)

b) Run the following command, to stop Jboss:

/etc/init.d/jboss stop

Step 5

Start DB replication script on both Primary and Secondary Core Services nodes.
mysql -uuser -ppassword

mysql> start slave;

Step 6

Start the Rsync process in the Secondary JS and SH nodes.
a) vi crontab –e

b) Uncomment cron entry and save the empty file

Steps to be Performed in the Secondary Setup

The steps tp be performed in the Secondary Setup are mentioned here. If needed, retain the Secondary node
as the Primary node, after migration.

Step 1

Stop the Forwarder process in the Primary Forwarder.
a) Log in to the Primary Forwarder node

b) Run the following command, to stop Splunkforwarder:

ssh bninet@bniforwarder

sudo /etc/init.d/splunkforwarder stop

Step 2

Remove IDX_A from the Primary JS node and add IDX_A to the Secondary JS node again.
Primary JS

Videoscape Distribution Suite Service Manager Software Installation Guide

OL-28652-01

VDS-SM Installation and Configuration

Upgrade Procedure for HA Setup