This documentation applies to the 8.1 version of Remedy ITSM Deployment, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

BMC Atrium Core checks

This topic provides information about the checks performed by the BMC Remedy Configuration Check utility for BMC Atrium Configuration Management Database (BMC Atrium CMDB). It also describes the expected results of the checks and corrective actions to be taken if a check fails.

BMC recommends that you run all the pre-upgrade checks before you upgrade to a higher version. If you encounter any error or warning, address the issue as it may prevent a successful upgrade.

 

AIRAppPassword Check

Description(Version 8.1.02 or later) This check validates whether the BMC Remedy Configuration Check utility can communicate with the BMC Remedy AR System server by using the password provided for members of the server group. This check validates whether a valid password is stored in the UDM:RAppPassword form.
TypeConfiguration check
Check performed and expected result

If no password is stored in the UDM:RAppPassword form or the stored password is incorrect, the following error message is displayed:
The check could not verify the password for: 'Remedy Application Service' on '<hostname>' : <full error message>.

Corrective ActionUpdate the password on the UDM:RAppPassword form for the suggested server.

Go to top

CMDB Class Overlay Check

DescriptionThis check validates whether any overlays are created for BMC Atrium CMDB forms. BMC Atrium CMDB does not support overlay forms.
TypePre-upgrade check, Configuration Check
Check performed and expected result

If overlays are created for BMC Atrium CMDB forms, the details of the overlays are displayed.

Corrective actionDelete the overlays.

Go to top

CMDB Data threshold check

Description

(Version 8.1.02 or later) This check validates forms that have exceeded the data threshold limit for the number of records present.

TypePre-upgrade check; configuration check
Check performed and expected result

Following forms and their data threshold limits are validated:

  • UDM:JobLog — 1000

  • RE:Job_Runs — 1000

  • RE:Job_Events — 10000

  • EIE:Log — 5000

  • EIE:Exchange_Runs — 1000

  • NE:JobRun — 1000

  • DSM:Log — 500

If the number of records in any of the forms is higher than the threshold limit, the check fails and displays the name of the form.

Corrective actionManually reduce the number of records in the forms so that the number in each form is lower than the threshold limit.

Go to top

CMDB Metadata Check

Description

This check validates whether BMC Atrium CMDB metadata has any pending metadata operation, using the CDMChecker utility.

TypePre-upgrade check, Configuration check
Check performed and expected result

This check performs the following validations:

  • If a pending metadata operation fails, the log file information is displayed. The log file is AtriumCoreInstallDir/Logs/pending_entries.log
  • If a specific functional failure occurs, a reference to a knowledge article is displayed.

Note:
If the BMC Remedy Configuration Check utility does not find the CDMChecker utility under the cmdb/server/bin directory, it displays an error.

Corrective actionPerform corrective actions according to the log file information or knowledge article information.

Go to top

CMDB OOTB Index Check

Description

This check validates whether any out-of-the-box (OOTB) indexes are missing and if so, displays an error. By default, BMC Atrium CMDB creates OOTB indexes on forms.

TypeConfiguration check
Check performed and expected result

If any OOTB index is missing, the following error message is displayed:
Index <index name> is not present.

Corrective actionCreate the missing index manually.

Go to top

CMDB System Information Check

DescriptionThis check validates the configuration of the system on which BMC Atrium CMDB is installed.
TypePre-upgrade check, Configuration check
Check performed and expected result

This check displays the following information in an informative message:

  • System configuration information such as OS, architecture, and OS version
  • BMC Remedy AR System database type, version, and character set
Corrective actionBecause this check provides an informative message, no corrective action is required.

Go to top

Max-Num-Caches Check

Description(Version 8.1.02 or later) This check validates whether the value of Max-Num-Caches is other than 1 and whether the Development cache mode is ON.

If the parameter Max-Num-Caches:1 is enabled in the ar.cfg (or ar.conf) file and the Development cache mode is OFF, the installation of BMC Atrium Core 8.1 can fail. However, if you set the Development cache mode to ON, Max-Num-Caches:1 has not effect.

TypePre-upgrade check; configuration check
Check performed and expected result

If the the parameter Max-Num-Caches:1 is enabled in the ar.cfg (or ar.conf) file and the Development cache mode is OFF, the following error message is displayed:

Max-Num-caches set to 1. This may cause Atrium upgrade failure. Disable this parameter in ar.cfg/ar.conf file -OR- turn ON Development cache mode.

Corrective actionDisable the parameter Max-Num-Caches:1 in the ar.cfg (or ar.conf) file, or set the Development cache mode to ON.

Go to top

Plugin Server check

Description(Version 8.1.02 or later) This check validates the plug-in port number and host name with the plug-in server configuration information.
TypeConfiguration check
Check performed and expected result

This check performs the following validations:

  • If the plug-in port specified in the ar.cfg (or ar.conf) file matches the port specified in the pluginsvr_config.xml file, the check passes. If the ports do not match, following error is displayed:
    Plug in port is not configured correctly, values in ar.cfg and pluginsvr_config.xml do not match
  • For all the plug-ins configured in the pluginsvr_config.xml file, the check validates whether the files specified in the <filename> and <pathelement> parameters actually exist. If the files do not exist, following error is displayed:
    File <filename> configured for Plug-in: <plugin name> does not exists, check pluginsvr_config.xml.
  • For all plug-ins configured in the pluginsvr_config.xml file, the check validates whether a corresponding entry is present in the ar.cfg (or ar.conf) file:
    • If a corresponding entry is present, the check validates whether the port in the pluginsvr_config.xml file matches the port in the ar.cfg (or ar.conf) file.
    • If a corresponding entry is not present in the pluginsvr_config.xml file and the ar.cfg (or ar.conf) file, but the port numbers do not match, the following error message is displayed:
      Plug in port is not configured correctly, for Plug-in: <plugin name> in Server-Plugin-Alias entry ar.cfg.
    • If corresponding entries are not present in the pluginsvr_config.xml file and the ar.cfg (or ar.conf) file, the following error message is displayed:
      Configuration for plug-in: <plugin name> is missing in ar.cfg.
  • Whether any duplicate entries exist in the pluginsvr_config.xml for a single plug-in. If duplicates exist, a warning message is displayed.

Note:
The BMC Remedy Configuration Check utility considers that pluginsvr_config.xml is always present in the %ATRIUMCORE_HOME%\cmdb\plugins\shared\ directory.

Corrective actions

 Perform the following corrective actions:

  • Ensure that the plug-in port specified in the ar.cfg (or ar.conf) file matches the plug-in port specified in the pluginsvr_config.xml file.
  • For all plug-ins configured in the pluginsvr_config.xml file, ensure that the files specified in the <filename> and <pathelement> parameters actually exist.
  • For all plug-ins configured in the pluginsvr_config.xml file, ensure that a corresponding entry is present in the ar.cfg (or ar.conf) file. Also ensure that the port in the pluginsvr_config.xml file matches the port in the ar.cfg (or ar.conf) file.
  • Ensure that no duplicate entries exist in the pluginsvr_config.xml for a single plug-in.

Recon Engine Private Queue Check

DescriptionThis check validates whether the Reconciliation Engine private queue is configured to use either port 390698 or port 390699.
TypeConfiguration check
Check performed and expected result

This check performs the following validations:

  • In the ar.cfg (or ar.conf) file, if the value of the Reconciliation Engine private queue is set to any port other than 390698 or 390699, the following error message is displayed:
    Reconciliation Private Port <port number> is not set according to recommended values.
  • In the ar.cfg (or ar.conf) file, if the value of the Reconciliation Engine private queue is not set, the following error message is displayed:
    Private port is not configured for Reconciliation Engine.
  • In the ar.cfg (or ar.conf) file, if the parameter for the Reconciliation Engine private queue is specified but the parameter for BMC Remedy AR System private queue is not specified, the following error message is displayed:
    AR private port is not configured for RE-Private-Port <Port no>.
Corrective actionsPerform the following corrective actions:
  • In the ar.cfg (or ar.conf) file, set the value of Reconciliation Engine private queue to either 390698 or 390699.
  • In the ar.cfg (or ar.conf) file, specify the value of the AR System private queue.

Go to top

Related topics

BMC Remedy AR System checks

BMC Remedy ITSM checks

BMC Service Level Management checks

BMC Service Request Management checks

BMC Remedy ITSM Preconfigured Stack Installer checks

Unified Data Management (UDM) checks

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments