IBM Support

MustGather details for Probe Integrations on UNIX

Question & Answer


Question

MustGather : What files are required for troubleshooting probe problems on UNIX?

Cause

n/a

Answer

There are a number of common details and problem specific information that need to be collected when troubleshooting probe problems. Please refer the probe's Summary page to understand the type of probe being used.

  • Probe Target - EMS version details
  • Probe Supported On - Netcool/OMINbus and platforms
  • Requirements - product and fix pack dependencies
  • Connection Method - type of connection to the EMS


For all probes provide the probe and Netcool/OMNIbus version details:

Probe's version is given by;
$OMNIHOME/probes/nco_p_<probe> -version

Identify the version of Netcool/OMNIbus using nco_id or listIU.

Confirm the version of the EMS or probe sources.

The files required for initial analysis of probe related problems are the debug log file and probe property file:
$OMNIHOME/log/<probe>.log
$OMNIHOME/probes/<arch>/<probe>.props

If you are using Process Control, include the nco_pa.conf file that runs the probe.

Additionally provide the Operating System details when applicable:
  • uname -a > $OMNIHOME/var/details.txt
  • For Red Hat linux include,
    • cat /etc/redhat-release >> $OMNIHOME/var/details.txt
  • For SuSE linux include,
    • cat /etc/suse-release >> $OMNIHOME/var/details.txt
  • For AIX include,
    • oslevel –r >> $OMNIHOME/var/details.txt
  • Other commands should be consistent on UNIX platforms
      • ulimit –a >> $OMNIHOME/var/details.txt
      env >> $OMNIHOME/var/details.txt
      ps -ef >> $OMNIHOME/var/details.txt
      vmtstat 5 5 >> $OMNIHOME/var/details.txt
      df –k >> $OMNIHOME/var/details.txt

Send the resulting details.txt file [$OMNIHOME/var/details.txt].

For rules file problems provide all related rules files:
$OMNIHOME/probes/<arch>/<probe>.rules
$OMNIHOME/probes/includes/*
$OMNIHOME/probes/lookups/*

For an attempt to replicate a rules file problem, the Support engineer may also require;
· Recent ObjectServer tab files
· The ObjectServer’s property file
· An example probe raw capture file
· The ObjectServer's root user's login details

For Java based probes include details of the probes java files:
ls -al of $OMNIHOME/probes > $OMNIOHME/var/java-details.txt
ls –Rl $OMNIHOME/probes/java >> $OMNIOHME/var/java-details.txt


Note : Java based probes specify ‘probe-nonnative-base’ and ‘Jave Runtime Environment requirements’ in the Summary->Minimum requirements section of the probes manual.

For ObjectServer connectivity related problems include this information:
· $NCHOME/etc/omin.dat
· ls –l $OMNIHOME/var
· ObjectServer property file[s]
· Output of ‘nco_ping NCOMS’

For EMS connectivity problems:
· Check and confirm that the EMS log can be made available.
· For TCP/IP based EMS connections you may be required to provide TCP data, please check your system and confirm your sites security policy on providing this data. TCP data will only be requested when required and always needs to be provided alongside the probes debug log file.

Example : How to collect debug log data for probe start-up problems:
  • Ensure that the log file is suitably sized [e.g. 100Mb]

    • MaxLogFileSize : 104857600
  • Stop the probe under process control
  • Remove the probes log file [$OMNIHOME/log/<probe>.log]
  • Start the probe from the command line as the normal probe user with the correct user environment

    • e.g.
    $OMNIHOME/probes/nco_p_<probe> -propsfile $OMNIHOME/probes/<arch>/<probe>.props -messagelevel debug
  • Monitor the probes log file

    • tail -f $OMNIHOME/log/<probe>.log
  • Wait until the problem is seen in the probes log file
  • Stop the probe using control-c, if required
  • Collect the probes debug log and other data


MustGather Check list:
· version details
· debug log
    o additional logging
· property file
    o other probe configuration files
· $OMNIHOME/var/details.txt
· rules file
    o lookup files
    o include files
· nco_pa.conf
· $OMNIHOME/probes/java/*
· ObjectServer connectivity details
· Confirm the availability of additional information

[{"Product":{"code":"SSSHTQ","label":"Tivoli Netcool\/OMNIbus"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"7.4.0;8.1.0","Edition":"Edition Independent","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21642785

Page Feedback