When you encounter a problem when using the self-describing capability, first try to diagnose and resolve the problem using the steps outlined in this section.
For detailed steps, see Self-describing agent installation.
Look at the monitoring server audit log to determine if self-description is enabled at the monitoring server the agent connects to.
The monitoring server audit log can tell you if self-description is disabled because of the KMS_SDA setting at the local monitoring server or hub monitoring server. There might also be other configuration errors at the local monitoring server or hub monitoring server that could be causing a problem.
Look at the portal server audit log to verify that the agent's self-describing files were processed successfully at the portal server. Install successes or errors are displayed for the application support for the Tivoli Enterprise Portal Server (TPS) and the Tivoli Enterprise Portal browser client (TPW).
Look at the monitoring agent audit for any installation errors.
For more information see Audit logging.
Return code | Message description |
---|---|
KRAA0008 | Validation failed for Self-Describing Agent
manifest file variable PRODUCT variable. This message indicates a validation error occurred and that the agent is not be able to provide SDA support. Please refer to the Audit log and RAS1 for other similar messages indicating the specific SDA manifest file validation error. After correcting the error, recycle the agent to participate in SDA processing. |
KRAA0015 | Self-Describing Agent function disabled for
PRODUCT variable due to local SDA file validation error. This message indicates that agent SDA status has been disabled due to manifest file validation error. This condition can occur at agent startup time, or while the agent is running and has been asked to provide SDA support. After the error condition has been corrected, the agent must be recycled to enable its SDA function. |
KRAA0016 | Ignoring TEMA_SDA Configuration! Agent SDA
package not found for PRODUCT variable. This message indicates that the TEMA_SDA=Y setting is ignored because the agent SDA package was not found. The variable should only be set when an agent is packaged with SDA support files. |
KRAA0017 | Self-Describing Agent function disabled,
expected TEMA_SDA configuration not found for PRODUCT variable. This message indicates that SDA is disabled because TEMA_SDA configuration was not set (although the SDA package exists). This variable is required for the agent to provide its SDA support. |
Issue | Solution |
---|---|
You receive a parsing failure on the Tivoli Enterprise Console when baroc files become out of sync with the changed attribute and catalog files. |
|
If you chose not to initially install any application support on the Tivoli Enterprise Portal Server, and then application support is added through self-describing agents, the situation even console is not available. | Reconfigure the Tivoli Enterprise Portal Server. |