sim2cmdb CLI command


This topic provides information about running the sim2cmdb CLI command.

Note

After an Infrastructure Management upgrade, the following parameter values are not updated in the sim2cmdb.conf file.

  • IASServer
  • CMDBServer
  • CMDBUser
  • CMDBPassword

sim2cmdb CLI command to manually update the sim2cmdb.conf file with the values of the IASServer, CMDBServer, CMDBUser, CMDBPassword parameters.

Before you begin

For Direct Feed data--If you have not previously published data from BMC Atrium CMDB to a cell, then before executing a sim2cmdb, you must execute the CLI command pinit -n cellName . This prevents the default management data from being upgraded as part of the execution of sim2cmdb.

If a configuration item (CI) has events attached to it through its ID (mc_smc_id), and sim2cmdb is run on it to upgrade the data, then such events get lost or detached from that CI.

 sim2cmdb.conf file and parameters

The following table describes the sim2cmdb.conf file, which contains properties and parameters for managing the sim2cmdb CLI command.

Modify the following parameters in particular to suit your specific requirements before you run sim2cmdb:

  • ContinueOnSkip
  • ReverseCellAliases
  • ReconJobTimeout

 sim2cmdb.conf file

File name

sim2cmdb.conf

File path

MCELL_HOME/etc

Description

Contains the sim2cmdb CLI command configuration properties

Parameter name

Description

Default value

IASServers

Specifies the Impact Administration Server (usually by host name) against which the CLI commands authenticate CLI commands may be executed on a computer other than the computer on which Impact Administration Server is installed. If you specify a remote Impact Administration Server in the sim2cmdb.conf file, but do not provide user credentials, you must provide them as command line arguments when you run a CLI command. If the Impact Administration Server has a backup server, then you can specify the primary server and the secondary server. If the primary is not running, then the CLI will authenticate against the secondary server.

none

IASUserName

Specifies a valid Impact Administration Server user name to be presented as credentials to the specified Impact Administration Server

none

IASPassword

Specifies the valid Impact Administration Server password for the specified Impact Administration Server (IASUserName) to be presented as credentials for the specified Impact Administration Server Enter the IASPassword as plain text. Upon the first execution, it is encrypted. To set up remote automatic authentication of CLI commands, specify the user name (IASUserName), and password (IASPassword) to be used as valid credentials for the specified Impact Administration Server (IASServers) in the sim2cmdb.conf file.

none

ARSXLongTimeOut

Sets the time to stop waiting on a BMC Remedy AR System operation that occurs slowly

1800

ARSXLongTimeOutEstimate

Enables (T) or disables (F) the use of the estimate when the length of time exceeds the value that is calculated for committing bulk entry transactions

T (true)

ContinueOnSkip

Defines sim2cmdb behavior if one or more instances cannot be imported If ContinueOnSkip is set to T, true, instances that can be imported are imported and instances that cannot be imported are not imported. The output file contains the list of instances that could not be imported. If ContinueOnSkip is set to F, false (default), the occurrence of even one instance that cannot be imported results in no data being created in the BMC Atrium CMDB. In other words, if all instances can be imported, all data (with attributes) in BMC.SIM is exactly as it is in the cell. If even one instance cannot be imported, only previously existing data in BMC.SIM still exists. The output file indicates the results.

F (false)

ReverseCellAliases

Specifies which alias corresponds to which cell Format: cellName, cellAlias{, cellName, cellAlias} When several aliases point to the same cell, retrieving an alias from a cell name is not deterministic. With the ReverseCellAliases parameter, you can specify which alias corresponds to which cell. It must have only one cellAlias for a cell in ReverseCellAliases. The letters in cellAlias value are case sensitive. If this parameter is not set, makes an undefined, arbitrary choice.

none

ReconJobTimeout

Sets the length of time that sim2cmdb checks for the termination of the reconciliation job If the interval expires before the reconciliation job completes, the sim2cmdb output file does not indicate the results of the reconciliation job. It may or may not have completed successfully.

120 (seconds)

CommitRetryTimeOut

Defines the length of time, in seconds, thatsim2cmdb retries the bulk entry transaction If the transaction failed due to the data problem, sim2cmdb will drop the offending data and retry the transaction.sim2cmdb will successfully commit good data into CMDB within the time specified by the CommitRetryTimeOut parameter or terminates the transaction if it exceeds the time specified by theCommitRetryTimeOut parameter.

900 (seconds)

PublishingServerName

The name of the publishing server. This name is used in validating the published environment and for DirectPublish credentials.

None

  Running the upgrade

sim2cmdb is run as a CLI command.

sim2cmdb syntax

 _sim2cmdb \[-c ConfigFile\] \[-h\|-?\] \[-i User/Password \[@Host\[/Port\] \[,Host\[/Port\]\[,...\]\]\] \[-l HomeLocation\] \{-p "Var=Value"\} \[-v\] \[-z\] \[-f\] \[-q\] \[-e EnvId1\[,EnvId2\[...\]\] \[-n Cell1\[,Cell2\[...\]\] \[-o OutputFile\] \[close \| commit \| identify\]_


The three commands of sim2cmdb are close, commit, and identify. Unless you specify one of these commands, sim2cmdb will run in default command, meaning that it will only verify the data. For more information about each of these commands, refer to  Upgrade commitment, CI identification, and Dataset cleanup.

sim2cmdb command options

The following table lists the options for the sim2cmdb command:

sim2cmdb command options

Options

Description

{{<common options>}}

-c -h -? -i -q -l -p -v -z

 

{{-e EnvID envID1\[,envID2\[...\]\]}}

 

Identifies the specific environments. If an environment is not specified, then Direct Feed data is upgraded. If you are upgrading Direct Feed data only, EnvID must be empty; do not use the -e option for Direct Feed data. For example, the following command displays all the Direct Feed data present in the cell to be upgraded:

 

sim2cmdb -v -n <cellname>

For secured environments, you must provide a valid password by using the  -p "password=xx"  option. If multiple  EnvID  options are specified, you must provide a password value for each  EnvID . If one of the EnvID  command options fails during environment verification, the  sim2cmdb  execution terminates. If both Direct Feed data and Direct Publish data must be imported, the Direct Publish  EnvID  and one empty EnvID  has to be specified with the -e option. To display data in Direct Feed and Direct Publish environments, use one of the following examples:

 

sim2cmdb -v -n <cellname> -e ",DirectPubEnvId1,DirectPubEnvId2"

  {{envID1\[,envID2\[...\]\]}}

sim2cmdb -v -n <cellname> -e "DirectPubEnvId1,DirectPubEnvId2,"

sim2cmdb -v -n <cellname> -e "DirectPubEnvId1,DirectPubEnvId2,"

sim2cmdb -v -n <cellname> -e "DirectPubEnvId1,,DirectPubEnvId2"

The comma (,) at the beginning, end, or middle of the option represents an empty  EnvID .

-f

 

Forces the command execution without prompting you to confirm the action. If you do not specify the -foption, you must confirm the action when prompted to allow the action to execute.

{{-n cellName1\[,cellName2\[...\]\]}}

 

Specifies the specific cell or cells from which to retrieve the service model classes. On Windows platforms, you must enclose the cell list in quotation marks ("). If no cell name is specified and there is an-e option, all the cells involved in the EnvIds are included. If there is no -e option, all the cells in the Atrium CMDB PROD environment are included. If one of the cells fails during cell verification, the sim2cmdbrun terminates.

{{-o ReportFileName}}

File that contains the report of sim2cmdb execution. In other words, the list of data that will be imported into BMC Atrium CMDB and a list of data that will not be imported into BMC Atrium CMDB, and a list of errors that have occurred BMC Software recommends, examining this report each time you run sim2cmdb. You might need to correct the SIM date before executing sim2cmdb again. If you omit this option,sim2cmdb generates a default report file name.

 

 

-p Password=

Specifies the password for each environment listed in the -e option, if a password is required for the environment, separate additional passwords with commas (,). For example: If three environments exist, and environment 2 has no password (is unsecured), the command might look like this: sim2cmdb -e "Env1, NoSecEnv,Env3" -n cell -p "Password=pw1, ,pw3"

 

 

close

Removes all the instances in the BMC.SIM dataset. Although you can force removal of all the data in the BMC.SIM dataset, if the dataset is not clean, you must first return to the CI identification stage to identify CIs. Forcing removal of unidentified CIs can cause unsynchronized data between SIM and CMDB.

 

 

commit

Imports the SIM data into the CMDB BMC.SIM dataset. On a successful commit, sim2cmdbautomatically starts the reconciliation job to merge data into the BMC.ASSET dataset.

 

 

identify

Assigns a ReconciliationIdentity value to the components in BMC.SIM that have not been identified. See CI identification for more information.

sim2cmbd CLI command examples

sim2cmdb -e testEnv -i user/user

Verifies imported data. Data is imported from all the cells in the direct publish environment testEnv.

sim2cmdb -e testENV -n cellA -i user/user

Verifies imported data. Data is imported from cell cellA in the direct publish environment testEnv.

sim2cmdb -n cellB -i user/user

Verifies imported data. Data is imported from cellB created from direct feed.

sim2cmdb -e testSecuredEnv -i user/user -p Password=mypasswd

Verifies imported data from the secured environment testSecuredEnv with the password parameter.

sim2cmdb -n cellS1, cellS2 -i user/user -p Password=passwd1,passwd2

Verifies imported data from multiple cells with multiple password parameters.

sim2cmdb -e testEnv commit

Runs the commit command to import data into the BMC Atrium CMDB. The reconciliation and publish process takes place following the success of the commit.

sim2cmdb -i user/user identify

Assigns the ReconciliationId to the CIs in the BMC.SIM dataset if they are not automatically identified. The reconciliation and publish process takes place following the success of the commit.

sim2cmdb close

Removes all the data in the BMC.SIM dataset.

  Reviewing the output files for sim2cmdb

The output files report on the results of sim2cmdb execution. The output includes the following details:

  • The sim2cmdb command string that you entered
  • An indication of the success or failure of user authentication
  • An indication of the success or failure of connection to the BMC Remedy AR System
  • A list of instances in the cell that will be copied to the BMC Atrium CMDB (Exporting service impact data from cells)
  • A list of instances that could not be imported into the BMC Atrium CMDB with the reason (Importing service impact data into CMDB's dataset BMC.SIM). If there are no issues with the data, this section of the output file is blank. Only data instances that cannot be imported will be listed here.
  • An indication of the success or failure of the reconciliation job with a list of instances that you must manually reconcile (BMC SIM to CMDB reconciliation into CMDB's data BMC.ASSET)
  • An indication of the success or failure of the sim2cmdb execution

The following figure displays examples of output files:

Example output file without commit

sim2cmdb -e JZTest -n hou-jezhou-37 -o JTest_Data_Warning_no_commit.log -m
Sun, 24 Feb 2008 11:31:42:454 CST
Sun, 24 Feb 2008 11:31:42:454 CST
User jean successfully authenticated with IAS.
User jean successfully authenticated with IAS.
User Demo successfully connected to AR System hou-jezhou-37:0.
User Demo successfully connected to AR System hou-jezhou-37:0.
User Demo successfully connected to AR System hou-jezhou-37:0.
==================================================================
Exporting service impact data from cell(s).
==================================================================
==================================================================
ellName:hou-jezhou-37
Components -
1. BMC_ComputerSystem; mc_udid=JZTest_Computer_1; ComponentAliases=[JZTest_Computer_1]; AccountID=JZTest1; Description='test one end relationship publish Computer'; Name=JZTest_Computer_1; OwnerContact='713.918.8800'; OwnerName=jean; Type=WINDOWS_SYSTEM; HostName=JZTest_1;
2. BMC_ComputerSystem; mc_udid=JZTest_Computer_2; ComponentAliases=[JZTest_Computer_2]; AccountID=JZTest2; Description='simple test sim2cmdb 2'; Name=JZTest_Computer_2; OwnerContact='713.918.8800'; OwnerName=jean; Type=WINDOWS_SYSTEM; HostName=JZTest_2;
3. BMC_FileSystem; mc_udid=JZTest_Filesystem_2; ComponentAliases=[JZTest_Filesystem_2]; AccountID=JZTest2; Description='SIM2CMDB testing No SystemName, no weakrelationship'; Name=JZTest_Filesystem_2; SystemName=JZTest_Computer_2;
4. BMC_FileSystem; mc_udid=JZTest_Filesystem_TestWK; ComponentAliases=[JZTest_Filesystem_TestWK]; AccountID=JZTest2; Description='SIM2CMDB testing weakrelationship'; Name=JZTest_Filesystem_TestWK; SystemName='SME-Computer-Test-WkRel';
5. BMC_BusinessService; mc_udid=JZTest_BusService_4; ComponentAliases=[JZTest_BusService_4]; AccountID=JZTest4; Description='simple test sim2cmdb 2'; Name=JZTest_BusService_4; OwnerContact='713.918.8800'; OwnerName=jean;
6. BMC_ComputerSystem; mc_udid=JZTest_Computer_4; ComponentAliases=[JZTest_Computer_4]; AccountID=JZTest4; Description='simple test sim2cmdb 2'; Name=JZTest_Computer_4; OwnerContact='713.918.8800'; OwnerName=jean; Type=WINDOWS_SYSTEM; HostName=JZTest_4;
7. BMC_FileSystem; mc_udid=JZTest_Filesystem_4; ComponentAliases=[JZTest_Filesystem_4]; AccountID=JZTest4; Description='SIM2CMDB testing file to computer with weak_relationship'; Name=JZTest_Filesystem_4; SystemName=JZTest_Computer_4;
8. BMC_FileSystem; mc_udid=JZTest_Filesystem_4_1; ComponentAliases=[JZTest_Filesystem_4_1]; AccountID=JZTest4; Description='SIM2CMDB testing Wrong SystemName'; Name=JZTest_Filesystem_4_1; SystemName=WrongSystemName;
9. BMC_FileSystem; mc_udid=JZTest_Filesystem_4_2; ComponentAliases=[JZTest_Filesystem_4_2]; AccountID=JZTest4; Description='SIM2CMDB testing No SystemName'; Name=JZTest_Filesystem_4_2;
Relationships -
10. BMC_Impact; mc_udid=JZTest_File2_To_Computer2; consumer_id=JZTest_Computer_2; provider_id=JZTest_Filesystem_2; AccountID=JZTest2;
11. BMC_Impact; mc_udid=JZTest_Rel_ComputerToService_4; consumer_id=JZTest_BusService_4; provider_id=JZTest_Computer_4; AccountID=JZTest4;
12. BMC_Impact; mc_udid=JZTest_File4_To_Computer4; consumer_id=JZTest_Computer_4; provider_id=JZTest_Filesystem_4; AccountID=JZTest2;
13. BMC_Impact; mc_udid=JZTest_File4_1_To_Computer4; consumer_id=JZTest_Computer_4; provider_id=JZTest_Filesystem_4_1; AccountID=JZTest2;
14. BMC_Impact; mc_udid=JZTest_File4_2_To_Computer4; consumer_id=JZTest_Computer_4; provider_id=JZTest_Filesystem_4_2; AccountID=JZTest2;
14. BMC_Impact; mc_udid=JZTest_File4_2_To_Computer4; consumer_id=JZTest_Computer_4; provider_id=JZTest_Filesystem_4_2; AccountID=JZTest2;
==================================================================
Importing service impact data into CMDB's dataset BMC.SIM.
==================================================================
During the data import, the following issues were found:
During the data import, the following issues were found:
1. BMC_FileSystem; mc_udid=JZTest_Filesystem_4_1; ComponentAliases='[JZTest_Filesystem_4_1]'; Name=JZTest_Filesystem_4_1; 
Warning: No System instance with Name WrongSystemName exists in CMDB or input data source. No relationship BMC_HostedSystemComponents with instance JZTest_Filesystem_4_1 is created.
Reason/Suggestion: Please verify the valid System CI WrongSystemName is existing in either import source or in CMDB
Reason/Suggestion: Please verify the valid System CI WrongSystemName is existing in either import source or in CMDB
2. BMC_FileSystem; mc_udid=JZTest_Filesystem_4_2; ComponentAliases='[JZTest_Filesystem_4_2]'; Name=JZTest_Filesystem_4_2; 
Warning: Slot SystemName has no value. No BMC_HostedSystemComponents relationship created with a BMC_SystemComponent instance.
Reason/Suggestion: This CI is an instance of a subclass of BMC_SystemComponent. To create BMC_HostedSystemComponents relationship, it is required to have the SystemName slot value.
Reason/Suggestion: This CI is an instance of a subclass of BMC_SystemComponent. To create BMC_HostedSystemComponents relationship, it is required to have the SystemName slot value.
Reason/Suggestion: This CI is an instance of a subclass of BMC_SystemComponent. To create BMC_HostedSystemComponents relationship, it is required to have the SystemName slot value.
==================================================================
Reconcile data in BMC.SIM dataset into BMC.ASSET dataset in CMDB
==================================================================
==================================================================
The following CIs in BMC.SIM have not been automatically identified:
The following CIs in BMC.SIM have not been automatically identified:
1. BMC_ComputerSystem; mc_udid=JZTest_Computer_1; ComponentAliases='[JZTest_Computer_1]'; Name=JZTest_Computer_1; 
2. BMC_ComputerSystem; mc_udid=JZTest_Computer_2; ComponentAliases='[JZTest_Computer_2]'; Name=JZTest_Computer_2; 
3. BMC_FileSystem; mc_udid=JZTest_Filesystem_2; ComponentAliases='[JZTest_Filesystem_2]'; Name=JZTest_Filesystem_2; 
4. BMC_FileSystem; mc_udid=JZTest_Filesystem_TestWK; ComponentAliases='[JZTest_Filesystem_TestWK]'; Name=JZTest_Filesystem_TestWK; 
5. BMC_ComputerSystem; mc_udid=JZTest_Computer_4; ComponentAliases='[JZTest_Computer_4]'; Name=JZTest_Computer_4; 
6. BMC_FileSystem; mc_udid=JZTest_Filesystem_4; ComponentAliases='[JZTest_Filesystem_4]'; Name=JZTest_Filesystem_4; 
7. BMC_FileSystem; mc_udid=JZTest_Filesystem_4_1; ComponentAliases='[JZTest_Filesystem_4_1]'; Name=JZTest_Filesystem_4_1; 
8. BMC_FileSystem; mc_udid=JZTest_Filesystem_4_2; ComponentAliases='[JZTest_Filesystem_4_2]'; Name=JZTest_Filesystem_4_2; 
8. BMC_FileSystem; mc_udid=JZTest_Filesystem_4_2; ComponentAliases='[JZTest_Filesystem_4_2]'; Name=JZTest_Filesystem_4_2; 
lease identify them manually with Reconciliation Manager's Manual Identification Console.
Then start a new "BMC SIM to CMDB" reconciliation job from Reconciliation Manager's Job History Console.
Then start a new "BMC SIM to CMDB" reconciliation job from Reconciliation Manager's Job History Console.
Then start a new "BMC SIM to CMDB" reconciliation job from Reconciliation Manager's Job History Console.
==================================================================
sim2cmdb completed
==================================================================
Please verify that the automated publication triggered by the reconciliation was successful, or execute a manual publication with cli publish and verify that it is successful
Please verify that the automated publication triggered by the reconciliation was successful, or execute a manual publication with cli publish and verify that it is successful
Please verify that the automated publication triggered by the reconciliation was successful, or execute a manual publication with cli publish and verify that it is successful


 Example verify.log file

sim2cmdb -e testPSR -i user/**** -o test_y_commit.log commit
Wed, 14 May 2008 09:49:51:954 CDT
Wed, 14 May 2008 09:49:51:954 CDT
IAS Server version: 7.2.00 [Build 1544526 - 29-Apr-2008]
User user successfully authenticated with IAS server hou-jezhou-37:3084.
User user successfully authenticated with IAS server hou-jezhou-37:3084.
BMC Atrium CMDB version: 2.1.0.0
User Demo successfully connected to AR System hou-jezhou-37:0.
User Demo successfully connected to AR System hou-jezhou-37:0.
User Demo successfully connected to AR System hou-jezhou-37:0.
Upgrade data of all cells of the publish environment(s).
Using cell(s) hou-jz-37-psr for DirectPublish data of testPSR.
Using cell(s) hou-jz-37-psr for DirectPublish data of testPSR.
==================================================================
Exporting service impact data from cell(s)
==================================================================
==================================================================
Cell:hou-jz-37-psr
Components:
1. BMC_BusinessProcess; mc_udid=BusProcess_Y; ComponentAliases=[BusProcess_Y]; AccountID=Y; Description='SIM2CMDB testing no-InstanceId, relationships'; Name=BusProcess_Y;
2. BMC_ComputerSystem; mc_udid=Computer_Y; ComponentAliases=[Computer_Y]; AccountID=Y; Description='SIM2CMDB testing no-InstanceId, relationships'; Name=Computer_Y; Type=WINDOWS_SYSTEM; HostName=JZTest_1;
3. BMC_FileSystem; mc_udid=FileSystem_Y; ComponentAliases=[FileSystem_Y]; AccountID=Y; Description='SIM2CMDB testing no-InstanceId, relationships'; Name=FileSystem_Y; SystemName=Computer_wrongName;
Relationships:
4. BMC_Impact; mc_udid=Computer_Y_TO_BusProcess_Y; PropagationModel=DIRECT; consumer_id=BusProcess_Y; provider_id=Computer_Y; AccountID=Y;
5. BMC_Impact; mc_udid=FileSystem_Y_TO_Computer_Y; PropagationModel=DIRECT; consumer_id=Computer_Y; provider_id=FileSystem_Y; AccountID=Y;
5. BMC_Impact; mc_udid=FileSystem_Y_TO_Computer_Y; PropagationModel=DIRECT; consumer_id=Computer_Y; provider_id=FileSystem_Y; AccountID=Y;
==================================================================
Importing service impact data into CMDB's dataset BMC.SIM
==================================================================
==================================================================
During the data import, the following issues were found:
During the data import, the following issues were found:
1. BMC_FileSystem; mc_udid=FileSystem_Y; Name=FileSystem_Y; ComponentAliases=[FileSystem_Y];
Warning: No System instance with Name Computer_wrongName exists in CMDB or upgraded data. No relationship BMC_HostedSystemComponents with instance FileSystem_Y is created.
Reason/Suggestion: Please verify the valid System CI Computer_wrongName is existing in either import source or in CMDB.
Reason/Suggestion: Please verify the valid System CI Computer_wrongName is existing in either import source or in CMDB.
No SIM data is imported to CMDB because commit was not requested.
No SIM data is imported to CMDB because commit was not requested.
No SIM data is imported to CMDB because commit was not requested.
==================================================================
sim2cmdb result
==================================================================
Program ended with no SIM data imported to CMDB.
Program ended with no SIM data imported to CMDB.


 Example output file with commit

sim2cmdb -e testPSR -i user/**** -o test_commit.log commit
Wed, 14 May 2008 09:36:44:809 CDT
Wed, 14 May 2008 09:36:44:809 CDT
IAS Server version: 7.2.00 [Build 1544526 - 29-Apr-2008]
User user successfully authenticated with IAS server hou-jezhou-37:3084.
User user successfully authenticated with IAS server hou-jezhou-37:3084.
BMC Atrium CMDB version: 2.1.0.0
User Demo successfully connected to AR System hou-jezhou-37:0.
User Demo successfully connected to AR System hou-jezhou-37:0.
User Demo successfully connected to AR System hou-jezhou-37:0.
Upgrade data of all cells of the publish environment(s).
Using cell(s) hou-jz-37-psr for DirectPublish data of testPSR.
Using cell(s) hou-jz-37-psr for DirectPublish data of testPSR.
==================================================================
Exporting service impact data from cell(s)
==================================================================
==================================================================
ell:hou-jz-37-psr
Components:
1. BMC_BusinessProcess; mc_udid=BusProcess_X; ComponentAliases=[BusProcess_X]; AccountID=X; Description='SIM2CMDB testing no-InstanceId, relationships'; Name=BusProcess_X;
2. BMC_ComputerSystem; mc_udid=Computer_X; ComponentAliases=[Computer_X]; AccountID=X; Description='SIM2CMDB testing no-InstanceId, relationships'; Name=Computer_X; Type=WINDOWS_SYSTEM; HostName=JZTest_1;
3. BMC_FileSystem; mc_udid=FileSystem_X; ComponentAliases=[FileSystem_X]; AccountID=X; Description='SIM2CMDB testing no-InstanceId, relationships'; Name=FileSystem_X; SystemName=Computer_X;
Relationships:
4. BMC_Impact; mc_udid=Computer_X_TO_BusProcess_X; PropagationModel=DIRECT; consumer_id=BusProcess_X; provider_id=Computer_X; AccountID=X;
5. BMC_Impact; mc_udid=FileSystem_X_TO_Computer_X; PropagationModel=DIRECT; consumer_id=Computer_X; provider_id=FileSystem_X; AccountID=X;
5. BMC_Impact; mc_udid=FileSystem_X_TO_Computer_X; PropagationModel=DIRECT; consumer_id=Computer_X; provider_id=FileSystem_X; AccountID=X;
==================================================================
Importing service impact data into CMDB's dataset BMC.SIM
==================================================================
==================================================================
All data was successfully imported.
All data was successfully imported.
All data was successfully imported.
==================================================================
Reconciling data in BMC.SIM dataset into BMC.ASSET dataset in CMDB
==================================================================
==================================================================
The following CIs in BMC.SIM have not been automatically identified:
The following CIs in BMC.SIM have not been automatically identified:
1. BMC_ComputerSystem; mc_udid=Computer_X; Name=Computer_X; ComponentAliases=[Computer_X]; HomeCell=hou-jz-37-psr;
2. BMC_FileSystem; mc_udid=FileSystem_X; Name=FileSystem_X; ComponentAliases=[FileSystem_X]; HomeCell=hou-jz-37-psr;
2. BMC_FileSystem; mc_udid=FileSystem_X; Name=FileSystem_X; ComponentAliases=[FileSystem_X]; HomeCell=hou-jz-37-psr;
Please identify them manually with Reconciliation Manager's Manual Identification Console.
Then start a new "BMC SIM to CMDB Migration" reconciliation job from Reconciliation Manager's Job History Console.
Or, use sim2cmdb 'identify' command to automatically identify CIs in BMC.SIM dataset.
Or, use sim2cmdb 'identify' command to automatically identify CIs in BMC.SIM dataset.
Or, use sim2cmdb 'identify' command to automatically identify CIs in BMC.SIM dataset.
==================================================================
sim2cmdb result
==================================================================
Please verify that the automated publication triggered by the reconciliation was successful, or execute a manual publication with cli publish and verify that it is successful.
Please verify that the automated publication triggered by the reconciliation was successful, or execute a manual publication with cli publish and verify that it is successful.
Please verify that the automated publication triggered by the reconciliation was successful, or execute a manual publication with cli publish and verify that it is successful.

  Upgrade commitment

When you run sim2cmdb with the commit command, SIM data is imported into the BMC Atrium CMDB. The data is first imported into the BMC Atrium CMDB BMC.SIM dataset. Afterward, sim2cmdb starts the reconciliation job, BMC SIM to CMDB Migration, to merge the identified instances into the BMC.ASSET dataset. Finally, the SIM publish process is automatically triggered to push the data into the cell with new reconciliation IDs.

The sim2cmdb commit command is terminated for two reasons:

  • Issues are found in data verification and the configuration parameter ContinueOnSkip is set to false (default).

    To continue upgrading, you must fix the data or set ContinueOnSkip to true, which commits the data upgrade regardless of issues with the data.

  • The BMC.SIM dataset is not clean. A clean dataset means that all CIs in the BMC.SIM dataset are identified. In other words, all the component instances in the dataset have the unique ReconciliationIdentity value assigned.
    If the dataset is not clean, you must perform either of the following tasks:
    • Return to the CI identification step to identify CIs.
    • Return to the dataset cleanup step to force clean all the data in BMC.SIM dataset.

      The sim2cmdb commit reports CIs which have not been automatically identified. If the output report contains any unidentified CIs, you must return to the CI identification stage to identify the CIs.

      You must also verify the results of data publication, as explained in step 10 in the Recommended upgrade steps to upgrade a service model to BMC Atrium CMDB page.

  CI identification

The CI identification procedure identifies the component instances in the BMC.SIM dataset and triggers the BMC SIM to CMDB Migration reconciliation job.

You have three options to identify CIs, which are as follows:

  1. Manually assign ReconciliationIdentity values to unidentified CIs from the CMDB Reconciliation Manager, and then manually run the BMC SIM to CMDB Migration reconciliation job.
  2. Modify the identification rules in the BMC SIM to CMDB Migration - Identification and Merge job from the CMDB Console and manually run the reconciliation job. For more information, see Identifying components and data reconciliation.
  3. Run the sim2cmdb identify command. The sim2cmdb identify command assigns a unique ID to each unidentified CI in the BMC.SIM dataset and calls the reconciliation job.

Options 2 and 3 have the potential to create duplicates in the BMC Atrium CMDB. Duplicates must be avoided. Therefore, use options 2 and 3 only if SIM data is the sole resource of the BMC Atrium CMDB data or you are certain that the option will not cause duplication.

After CIs in the BMC.SIM dataset are identified and the reconciliation job successfully executed, you must verify whether the publication was successful.

  Dataset cleanup

The sim2cmdb close command cleans up all the data in the BMC.SIM dataset.

You cannot run the sim2cmdb commit command if the BMC.SIM dataset is not clean. A clean dataset means that all CIs in BMC.SIM dataset are identified. That is, all the component instances in the dataset have a unique ReconciliationIdentity value assigned.

Although you can force removal of all the data in BMC.SIM dataset, BMC Software recommends that if the dataset is not clean, you return to the CI Identification stage to identify those CIs. Forced removal of unidentified Cis can cause unsynchronized data between SIM and the BMC Atrium CMDB.

  sim2cmdb return codes

When the sim2cmdb command exits with a return value other than 0 (success), additional textual information on the error cause is displayed to standard output and to the generated trace file  installationDirectory\ pw\server \sim2cmdb.tra ce.

To enable debug tracing, comment out the last two sections in the installationDirectory /pw/server /sim2cmdb .trace configuration file.

These exit codes, their meanings, and recommended remedial actions are described in the following table.

error exit codes for sim2cmdb CLI command  

Error Exit Code

Description

Recommended remedial action

{{ 1 }}

 

Indicates a syntax error on one or more command-line arguments or options

Verify the correct syntax for the command string.

{{ 3 }}

 

Indicates that the home directory of the CLI is not defined

Perform the following tasks:

  1. Verify that the MCELL_HOME environment variable is set for the application.
  2. Verify that the CLI script (.bat or .sh) file correctly contains: -DhomeLocation= %MCELL_HOME%
  3. Specify the home directory (-D HomeLocation ) path at the command line.

4

 

Indicates that the supplied configuration file could not be found

Verify that the value of the -c argument is an existing, readable file.

5

 

Indicates that an I/O error occurred when reading the configuration file

Verify that the user has read access to the configuration file.

6

 

Indicates that the Impact Administration Server (IAS) interface cannot be initialized

Check whether the Impact Administration Server (IAS) is up and running.

7

 

indicates a security problem (for example, write access) to the CLI home directory

Check whether the user has read and write access to theetc/ log/ directory and write access to the temp/ directory in the CLI home directory.

8

 

Indicates that the home directory of the CLI does not exist

 

{{ 14 }}

 

Indicates that the CLI cannot find a file that it requires to run properly; for example, a FileNotFound exception

Verify that the file whose name appears as missing does exist.

{{ 15 }}

 

Indicates that the CLI cannot resolve a host name

Repair the computer's network settings.

{{ 16 }}

 

Indicates that the failure to authenticate with the BMC Portal server

Perform the following tasks:

  • If you are running a CLI command, verify the credentials that you specified.
  • If automatic authentication is set up in thesim2cmdb.conf file, verify that the credentials (IASUsername, IASPassword, and IASServers) are valid.

{{ 17 }}

 

Indicates that an error with starting impact CLI

Perform the following task: Verify that the fileinstallationdirectory /pw/server/ etc/locale/sim2cmdb.loadexists on the Infrastructure Management server host computer.

{{ 18 }}

 

Indicates that the UTF-8 character set is not supported by the host

The host computer must support the UTF-8 character set.

30

 

Indicates that verification of publish environment failed

 

31

 

Indicates that an error occurred when retrieving a cell directory from the BMC Atrium CMDB

Verify the access rights for the cell directory.

32

 

Indicates that an error occurred when communicating with a cell

Verify that the cell is running. Verify network connectivity.

33

 

Indicates that verification of the cell protocol version failed

 

34

 

Indicates that classes between CMDB and cell(s) are not synchronized

 

35

 

Indicates that an error occurred when communicating with BMC Atrium CMDB

Verify that BMC Remedy AR System is running. Verify network connectivity.

36

 

Indicates that an error occurred when executing a CMDB operation

 

37

 

Indicates that an error occurred when importing data into CMDB

Check standard out for more details regarding the error.

sim2cmdb.conf file

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*