Common Troubleshooting and Actions

The most common issue is data missing or data discrepancy in the report. This may include an individual graph on a report not containing data through to all reports containing no data. Use the following steps to diagnosing these and other types of issues:
camm27
Common Issue
The most common issue is data missing or data discrepancy in the report. This may include an individual graph on a report not containing data through to all reports containing no data. Use the following steps to diagnosing these and other types of issues:
  • Confirm the status of DX NetOps MM components:
  • Log in to the Web Manager. Ensure the status of each Component and Sub Component is active (represented by a green tick). If any component is down, attempt to start them using ‘startall’ command ($CAMM_HOME/tools/startall).
  • If any Sub Component is down, attempt to start it through the GUI by clicking on ‘Start’.
  • If any Component or Sub Component continues to fail, increase the logging level as explained in “Using the Log files” section, reproduce the problem and collect the following log files:
    • $CAMM_HOME/MC/repository/*
    • $CAMM_HOME/<(sub)component>/log/*<current_date>.log
Other Issues
Engine common problems are related to:
  • Lose of connectivity to the EMS
  • The input data format is changed on the EMS
For connectivity to EMS lost:
  • Check Log files in $CAMM_HOME/COMPONENTS/ENGINE_<device_pack>/logs directory, specifically the STD-ERROR-<timestamp>.log files.
  • Check the file $CAMM_HOME/COMPONENTS/ENGINE_<devicePack>/.local/EngineStatistics.xml. It indicates the performance, success or failure of every part of the Poll.
  • Check the file $CAMM_HOME/COMPONENTS/ENGINE_<devicePack>/repository/work/InventoryDeviceList.xml
For change of input EMS data format:
  • In addition to the above log files, EngineStatistics.xml and InventoryDeviceList.xml files, also check the Engine output is making it to the Delivery Service by stopping the Presenter and checking the Queue directory.
Presenter common problems are related to:
Data not arriving from the Delivery Service
The common problem when Data are not seen in the Presenter is when the processed data is not delivered by the Delivery Service. The troubleshooting steps in this case are the following:
  • Check the log files in the log directory specific to the device pack presenter specifically focusing on the STDERR log files, e.g. $CAMM_HOME/COMPONENTS/PRESENTER_<device_pack>/logs/*
  • Check if the Engine output is making it to the Delivery Service by stopping the Presenter and checking the $CAMM_HOME/Queue directory.
Stop the Presenter and check if the processed data from the Engine is reaching the Delivery Service.
The processed file should be present under the $CAMM_HOME/Queue directory.
  • Check to see if CSV, XML or DDI files are present in the $CAMM_HOME/output directory
  • If data are expected to be presented in the SNMP format, try querying the SNMP MIB using snmpwalk.