If you see the following error, then like me you might be wondering what the issue is -
It would seem that PowerVC has performed more stringent checking then I have, and in this case it doesn't like my HMC, its a model 7042C06. If you have been paying attention and looking at my previous blogs you will see that the supported models are CR5/C08 or later.. So if you see AEVCOM021E too, take a look at your HMC model, switching to a spare CR6 model I had resolved my problem.
Note: I would like to point out that this is only one example of the issues that the AEV code covers. I have seen it reproduced in the event of a network failure, in that case it had slightly different explanation and response text. Looking at the '/var/log/nova/api.log' should give you more information.
More about Interpreting messages in IBM PowerVC (taken from the installation and user's guide):
- The characters AEV indicate that the message is a PowerVC message.
- The next 0-3 alphabetic characters (XXX) identify the area of the product where the error originated, as follows:
|Area of the product||Message identifier|
|Verify environment tool||TTV|
The next 3 to 6 digits (######) identify the unique message number.
- Note: Zero padded numbers in message identifiers are not unique. For example, numbers 029, 0029, and 00029 all represent the same message.
- The last character (Z) identifies the severity code, as follows:
E - Indicates that the message is an error message.
I - Indicates that the message is an information message.
S - Indicates that a process completed successfully.
W - Indicates that the message is a warning message.