Diagnostics and Troubleshooting › Missing Solaris Non-Global Zones, Resource Pools, and Processor Sets Inventory

Missing Solaris Non-Global Zones, Resource Pools, and Processor Sets Inventory

Symptom:

I cannot see any inventory related to Solaris non-global zones.

Solution:

You must install the asset management agent on the global zone. There is no need to configure a virtual host inventory collect task, because information about the non-global zones, resource pools, and processor sets is collected by default by the agent.

The non-global zones inventory is reported under Virtualization, Zones in the DSM Explorer. The resource pools inventory is reported under Virtualization, Resource Pools, Resource Pools, and the processor sets information is reported under Virtualization, Resource Pools, Processor Sets.

Script Compilation Errors in an Intellisig

Symptom:

A particular Intellisig always shows script compilation errors.

Solution:

Verify that the version of dmscript.exe on the target computer is not below R12.5.1010. An updated version is required because Intellisig scripts use new features of dmscript that were not available before R12.5.1010.

Intellisig fails to Execute even when Collect Task Runs Successfully

Symptom:

A particular Intellisig does not execute even though the Collect Task runs successfully.

Solution:

Follow these steps:

1. Navigate to Software, Definitions, Intellisigs.
2. Verify that the Intellisig you want to execute has Enable for Discovery set to Yes. If not, right-click and select Enable Scan.
3. Right-click on the Intellisig, select Properties and view the Versions tab. Verify that the correct Intellisig version has Active set to Yes. If no versions are active, the Intellisig does not run.

Check Execution of Intellisgs

Symptom:

I want to check if my Intellisigs are executing correctly.

Solution:

If there are any errors generated during the running of software inventory, you can view them in the System Status portal on the DSM Explorer main page.

Follow these steps:

1. Navigate to Computer, Configuration, Collect Tasks.

   Software Inventory Configuration is displayed as one of the collection tasks, if software inventory has been configured on that asset.

2. Right-click the task and select Status to see detailed error information about the software inventory execution.

You can view the state of software inventory execution on individual computers.

Execution of Intellisigs on Target Computers Times Out

Symptom:

The execution of some Intellisigs on some target computers always times out.

Solution:

Intellisigs are designed to run as background processes, to help ensure that that there is minimum impact on the performance of the target computer when the scripts are running. Because of this reason, it is possible that some long running scripts on highly loaded computers take a longer time to execute. In such cases, Intellisigs exceed the available execution timeout.

You can control the available execution timeout using configuration policies. You can find the configuration policy value that controls the default Intellisig execution timeout value at the following location:

Control Panel, Configuration, Configuration Policy, policy name, DSM, Agent, Asset Management, Intellisig Default Execution Timeout.

With CA ITCM Configuration policies, you can define the timeout value to a different period in different policies. You can apply different policies to different computers, or groups of computers. In this way, you can modify the configuration value only on the policies that are active on the computers where the Intellisig timeout is detected.

Review of Intellisig Scripts that Run on Agents

Symptom:

I want to review the Intellisig scripts that run on agents.

Solution:

Follow these steps:

1. Navigate to DSM explorer, Software, Definitions, Intellisigs.
2. Right-click on the Intellisig you want to review.
3. Click the Version tab and then select the Intellisig version you want to review.

   Note: An Intellisig can have a number of versions, but only one version is active at a time. It is the active version that is executed on your agent computers.

4. Select the version you want to review and click the Properties button.

   A dialog displays detailed information of the Intellisig.

5. Click the Script tab to view the name of the Intellisig script.
6. Click the Preview button to view the contents of the file.

Export of Intellisig Definitions by the Domain Manager

Symptom:

I want to confirm that the latest Intellisig definitions have been exported by the Manager.

Solution:

Intellisig definitions are exported by the CA ITCM engine to XML and DAT files in the folder %ALLUSERSPROFILE%\Application Data\CA\eso_fingerprints. Intellisig definitions for Windows are available in Xnnnnnnn.xml and Xnnnnnnn.dat files, and for UNIX in Mnnnnnnn.xml and Mnnnnnnn.dat, where nnnnnnn is a number which increments whenever there is a change to the definitions.

The XML files contains a list of the Intellisig definitions, the name of the main script file, and any triggers and additional files.

The DAT files contain the main script and any additional files. It is in a compressed format and can be uncompressed for example, by using 7-Zip. You can compare the contents of the XML and DAT files with the Intellisig definitions that you see in the DSM Explorer.

Modification of Engine-Managed Policy Parameter does not Change its Behavior

Symptom:

I have changed an engine-managed policy parameter but the behavior has not changed.

Solution:

Verify that the machine on which the engine is running has received the updated configuration policy. You can do this from the DSM Explorer by navigating to All Computers, Computer, Configuration Policy, Request Configuration Report, View Configuration report. Verify that the policy parameter has the required value.

After the policy parameter has changed on the computer, the CA ITCM engine on that computer gets notified of the change and re-reads the parameter. You can check this in the detailed engine log, by looking for CONFIGURATION_CHANGED. To help ensure that the new configuration is retrieved, you can restart the engine process.

Note: Verify that the Convert replicated Intellisgs on unlinking parameter is effective on the computer where the operation is initiated. This computer is usually the enterprise manager.

Replicated Intellisig Definition does not Replicate after Manual Deletion

Symptom:

I have manually deleted a replicated Intellisig definition on my Domain Manager. The Intellisig definition did not replicate again from the enterprise manager.

Solution:

Replication works on a delta mechanism depending on what has been created, updated, or deleted from an MDB. If you manually delete a replicated object (for example, a replicated Intellisig definition at a domain manager), it is not re-replicated unless there is a change to it at the enterprise manager.