IBM COPPEZ042E VALUE0 is not a valid device type, COPPEZ051E VALUE0 is not a valid device type

COPPEZ041E A generic data acquisition configuration error occurred.

Operator response: Validate the configuration of the acquisition engine.

COPPEZ042E VALUE_0" is not a valid device type.

Operator response: Validate the configuration of the acquisition engine.

COPPEZ043E The management IP address "VALUE_0" is not valid for device "VALUE_1".

Operator response: Verify the IP address of the device.

COPPEZ044E VALUE_0" is not valid for a VALUE_1" context.

Operator response: Validate the configuration of the acquisition engine.

COPPEZ045E The VALUE_0" application tier is not configured on load balancer VALUE_1".

Operator response: Validate the configuration of the acquisition engine.

COPPEZ046E A generic data acquisition subscription error occurred.

Operator response: Validate the configuration of the acquisition engine.

COPPEZ047E The data acquisition thread is not working.

Operator response: Review the data acquisition driver.

COPPEZ048E The system is running too many concurrent data acquisition tasks.

Explanation: No additional information is available for this message.

COPPEZ049E VALUE_0" is not a valid VALUE_1" metric.

Operator response: Validate the configuration of the acquisition engine.

COPPEZ050E VALUE_0" is not a valid aggregation type.

Operator response: Validate the configuration of the acquisition engine.

COPPEZ051E VALUE_0" is not a valid device type.

Explanation: This error can be triggered by a

tier/application configuration problem: all tiers and active/online (instead of "not in maintenance") applications must be configured for data acquisition.

COPPEZ052E The VALUE_0" signal is not configured for application tier VALUE_1".

Operator response: Validate the configuration of the acquisition engine.

COPPEZ053E The system does not support data acquisition for VALUE_0".

Explanation: No additional information is available for this message.

COPPEZ058E The IP address VALUE_0 is not valid.

Operator response: Review the server IP address in the configuration file.

COPPEZ060E One of the expected fitness parameters is not present in the PROPERTIES table.

Explanation: The policy engine evaluates a number of parameters to calculate the fitness, or appropriateness, of a decision to add or remove servers. These are called fitness parameters. The fitness parameters are stored in the PROPERTIES table in the database. In this instance, one of the expected parameters is not present in the PROPERTIES table.

Operator response: Confirm that there are no typing errors in the Resource-Pool.xml file. Also verify that the file was imported properly.

COPPEZ062E The system passed a null value for the data center model instead of a valid accessor object.

Explanation: No additional information is available for this message.

COPPEZ064E The object ID includes less than two numbers.

Operator response: Review the workflow parameters for the object ID.

COPPEZ070E An SNMP packet decode or structure error occurred.

Explanation: No additional information is available for this message.

Chapter 10. Tivoli Intelligent Orchestrator messages 151