To install the GT.M Monitoring Reference Implementation, perform the following steps:

  1. Install InfoHub and create an InfoHub database. For more information, refer to Installing InfoHub.

  2. Install the FIS GT.M SNMP Plugin. For installation instructions and prerequisites, refer to Installing the SNMP Plugin.

  3. Change to the InfoHub configs directory.

  4. Open a new terminal session and execute gather_instance_info.sh passing it as a parameter the environment configuration of the GT.M database you want to monitor.

    /path/to/inofhub/samples/gather_instance_info.sh /path/to/gtm/instance/env_file > someinstance1.out

    Please ensure that you generate only one file per instance. Do not concatentate these files into one.

  5. Open a new terminal session and source environment of the InfoHub and configure the new instance using the output file from above

    $gtm_dist/mumps -run gtmConfGenerator someinstance1.out

    Follow the prompts to create a new configuration, modify an existing configuration or create a new configuration as a copy of another configuration. Copies will acquire the Publisher configuration of the original configuration will all of the InfoDict IDs changed for the new configuration.

  6. Copy all desired files from samples/IHRegionReplInfoDict.conf into configs/gtmfields.conf

    Copy all desired files from samples/IHGtmSyslogMessages.conf into configs/gtmmessages.conf or remove the "Include" directive from dbinstances.conf

  7. Copy all desired files from samples/IHRegionReplInfoDict.conf into configs gtmfields.conf

    Review the new configuration files as there may be some editing needed (use your favorite editor). If the global directory uses environment variables, add Env: directives for them. In the gather_instance_info.sh output file, e.g. someinstance1.out, look under the "GlobalDirectory" section for environment variables. If all of the environment variables share a common prefix, for example, "SCAU_DB_", then running env|grep SCAU_DB_*|sort may be helpful in gathering the environment variables and their corresponding values. If the global directory uses relative paths when referencing the database file(s), add an Env:IHCD directive containing the path to the start of the relative paths. Make sure that the gtmroutines entry includes InfoHub's PipeCmd directory.

    After each execution og gtmConfGenerator, load dbinstances.conf. This loads all newly generated IDs into the InfoHub so that subsequent executions of gtmConfGenerator can avoid re-using them.

    $gtm_dist/mumps -run InfoHub --action=configure --file=dbinstances.conf

    The next several steps are based upon using dbinstances.conf with the generated configuration files and port 161 for the port where the SNMP daemon listens (see the agentAddress line in snmpd.conf). Please adjust accordingly.

  8. Execute the following command to and start InfoHub.

    $gtm_dist/mumps -run InfoHub --action=start

    For more information, refer to Loading a Configuration File and Starting an InfoHub.

  9. Execute the following command to generate the MIB.

    $gtm_dist/mumps -run generatemib >INFOHUB-1-MIB
  10. Execute the following command to start the M SNMP Plugin using Subscriber Id 9. Note that the SNMP Subscriber Descriptor (entry starting with Subscriber:) in server1.conf specifies 9 as the Subscriber Id.

    $gtm_dist/mumps -run IHsnmp --action=start --plugin=9

    For more information, refer to Starting the SNMP Plugin.

  11. Execute the following command to see the most recent GT.M SysLog message.

    snmpget -v2c -c $communitystring -M +$PWD -m INFOHUB-1-MIB -Oaq 127.0.0.1:161 infohubtestserver1syslogSyslogGTMcurr.0
    

    Execute the following command to see the next ten most recent GT.M SysLog messages in reverse chronological order.

    snmpbulkget -v2c -c $communitystring -M +$PWD -m INFOHUB-1-MIB -Oaq 127.0.0.1:161 infohubtestserver1syslogSyslogGTMhist.0
    

    Execute the following command to see the most recent values for the first ten items from database "db1"'s "UBG" region.

    snmpbulkget -v2c -c $communitystring -M +$PWD -m INFOHUB-1-MIB -Oaq 127.0.0.1:161 infohubtestdb1RegReplFetchUBGGdregRnamecurr.0
    
  12. Execute the following commands to check the status of InfoHub and the SNMP Plugin:

    $gtm_dist/mumps -run InfoHub --action=status 
    $gtm_dist/mumps -run IHsnmp --action=status --plugin=9

    For more information, refer to Monitoring an InfoHub and Monitoring the SNMP Plugin.

  13. Congratulations! Your GT.M Monitoring Reference Implementation is now installed .