Administration Guide › Troubleshooting › PMM Stops Polling an AIM

PMM Stops Polling an AIM

Symptom:

The PMM stops polling an AIM (all instances of AIM) and sends CAAM6504 message. Additionally, the UI shows the affected instance as Critical in the AIM panel, Administration tab.

The polling stops for Cisco UCS, Microsoft clusters, IBM LPAR, and Solaris Zones AIMs that monitor multiple instances.

The reason is that the PMM cannot keep polling the AIM. When an AIM in such state is restarted, the MIB is not populated with the data from the affected instance. The PMM would assume that data are no longer available and removes from the management database.

Solution:

• Verify why the instance is not in the Ready state. You can check for the following:
  • Invalid or expired credentials
  • Network connection
  • Hardware issue on the server
• Disable the instance in the Administration tab of the corresponding platform (not available on Cisco UCS).
• Remove the instance from the AIM.