Adding an OMD Insights Indexer to a Single-Site Cluster

This appendix provides the steps to add an OMD Insights Indexer to a single-site cluster.


Caution

Contact your Cisco Account team before adding an OMD Insights Indexer to an existing setup.

Prepare the New OMD Insights Indexer and Initialize the Salt Minion

To initialize the Salt Minion on the new OMD Insights Indexer, you will use the OMD Server init script. Perform the following steps to use the OMD Server init script to initialize the salt minion on the OMD Insights Indexer:

Before you begin

Before you add an OMD Insights Indexer:

Procedure

Step 1

To prepare the new OMD Insights Indexer, perform the steps in Prepare the Servers in the Media Streamer Deployment.

Step 2

After the server reboots, if ICMP is allowed through the firewall, confirm that the new OMD Insights Indexer can ping the IP address of the Salt Master.

Step 3

Perform the following steps to copy the public key file needed by the omd_server_init.py script to the OMD Insights Indexer:

  1. Log in to the Salt Master as ocdn_adm and switch to root:

    [ocdn_adm@omd-repo-salt ~]# sudo su - root

  2. Copy the public key file to the OMD Insights Indexer:

    Note 

    This step uses the IP address of the OMD Insights Indexer and not the FQDN.

    		 
    [root@omd-repo-salt ~]# ssh-copy-id -i ~/.ssh/id_rsa.pub root@<IP_Address_of_new_OMD 
Insights Indexer>

  3. Test the keys by performing an SSH connection to the new OMD Insights Indexer:

    Note 

    This step uses the IP address of the OMD Insights Indexer and not the FQDN.

    		 
    [root@omd-repo-salt ~]# ssh root@<IP_Address_of_new_OMD Insights Indexer>

    You should connect successfully to the OMD Insights Indexer without being asked for a password. Close the SSH connection to that server.

Step 4

Repeat Steps 3 on any additional new OMD Insights Indexer.
Step 5

On the Salt Master logged in as root, you will create a CSV file that will be used with the OMD Server init script. This file will contain one row for each new OMD Insights Indexer. This CSV file defines the hostname, IP address, and roles for the new OMD Insights Indexer.

  1. On the Salt Master logged in as root, make sure you are in the /home/ocdn_adm directory.

  2. Using a text editor, use the following information to create the CSV file:

    Note 

    You can use any filename that you would like, but you will need the filename when you run the OMD Server init script.

    Enter a row for the new OMD Insights Indexer, using the following format:

    <FQDN hostname>, <IP address>,, splunk_indexer, monitor-client, snmp-agent
    Note 

    The hw_profile parameter is entered between the IP address and role parameters. Because the OMD Insights Indexer do not use the hw_profile parameter, enter two consecutive commas to leave this field blank, as shown in the syntax above.

    Note 

    If your Media Streamer deployment is not running OMD Monitor, do not enter the monitor-client role. If you will not be using an SNMP management station to query the OMD Director Master portal, do not enter the snmp-agent role. If you will be using Check_MK server to connect to OMD Servers, add the nagios-agent minion role, similar to the snmp-agent role.

    • FQDN hostname: The hostnames that you enter must be the FQDN names. The names that you enter will be used as the salt minion key names.

    • Server IP address: Enter the IP address that the server uses to communicate with the Salt Master. This value will be used to populate the ext_ip: grain in the /etc/salt/grain file.

    Note 

    When you execute the omd_server_init.py script, you will reference the CSV file you are creating and the IP address of the Salt Master. All of the server IP addresses listed in the CSV file that you reference must be able to connect to the Salt Master address that is provided when you run the omd_server_init.py script.

    If some of the servers need to use a different address to communicate with the Salt Master, such as a NAT’d IP address, you will need to create a separate CSV file for those servers. You can then re-execute the omd_server_init.py script referencing this new CSV file and the Salt Master IP address to which these servers can communicate.

  3. When you are finished, your CSV file should look similar to the following:

    Note 

    Make sure that the file only contains entries for the new OMD Insights Indexer that you are adding.

    		 
    omd-insights-ind4.companyx.example, 172.31.28.95,, splunk_indexer, monitor-client

  4. Save and close the file.
Step 6

Run the OMD Server init script. Make sure for the <salt_master_ip> parameter, you enter the IP address of the Salt Master that the servers listed in the CSV file can communicate with. Make sure you are still logged in as root when you execute this command. 

[root@omd-repo-salt ~]# /opt/cisco/bin/omd_server_init.py -f <csv_file_name> <salt_master_ip>

where <csv_file_name> is the name of the CSV file that you created in Step 5. For example:

[root@omd-repo-salt ~]# /opt/cisco/bin/omd_server_init.py -f servers.csv 10.63.232.24
Note 

You can ignore messages that the salt minion returns during this script; this is expected and normal as the init process proceeds.
Note 

It will take several minutes to initialize each server listed in the CSV file.

The OMD Server init script will configure the Salt Minion, interface properties, and base services.

Highstate the Servers for the new OMD Insights Indexer

Perform the following steps, in the order specified, to install the new OMD Insights Indexer. Ensure that you enter the commands in the order listed. If you do not, manual intervention may be required to resolve any sync up issues between the OMD Insights servers. If you encounter any failures while executing any of the following commands, stop and contact your Cisco Account or Support teams before proceeding on to the next command.


Note

Do not copy and paste the commands. Enter the commands manually.

Note

In the following commands, replace <splunk_indexer_5> with the salt-key of the OMD Insights Indexer you are adding.

 
[root@omd-repo-salt ~]# salt "<splunk_indexer_5>" state.highstate
[root@omd-repo-salt ~]# salt -G "roles:splunk_dep" state.apply splunk_dep/update_int_outputs_conf
[root@omd-repo-salt ~]# salt -C 'G@roles:edge or G@roles:mid or G@roles:router' state.apply 
splunk_UF/update_ext_outputs_conf