Document ID: 25049
Questions
- Q. Why does the transition of some auto discovered managed objects fail? Why are they reported as having an unknown state? How can I fix this? (Products affected : CEMF 3.0.x, 3.1)
- A. When objects are created using the Auto Discovery tool, the state attribute value is not set. As part of the object creation participation process, the Controller (via State Manager) attempts to add newly created managed objects to the appropriate state machine, using the initial state value of these objects. Since auto discovered objects do not have their state value set, State Manager uses the default state defined in the state machine file.
If a default state is not defined within the state machine configuration file for an object class, then that object is not added to a state machine but is still created. All state transitions fail on such objects, and the GUI reports their state as unknown.
The following is an example of a state definition within a state machine config file. The key word, DEFAULT_STATE, marks this state as the default for the class of object associated with this machine:
STATE_DESCRIPTOR NAME decommissioned DEFAULT_STATE TASK NAME DecommissionTask END_TASK ALARM ALARMCLASS technologyAlarm ALARMDESC testdesc ALARMSEVERITY minor END_ALARM OSI_MAPPING OSISTATE EnabledIdleUnlocked OSIALARM_STATE Minor|AlarmOutstanding OSIPROC_STATE Reporting OSICEMFAIL_STAT InTest|LogFull OSISTDBY_STAT ProvidingService OSIUNKNOWN_STAT False END_OSI_MAPPING END_STATE_DESCRIPTORState machine configuration files for objects that can be discovered using the Auto Discovery tool should have a default state specified as described above. This prevents auto-discovered objects being added with no state attribute value.
CEMF-SDK generated state machine configuration files have the decommissioned state marked as the default state (as described above). However, you must ensure that the appropriate classes of object have a default state marked in their configuration files.
Related Information
| Updated: Jan 31, 2006 | Document ID: 25049 |
