Ask a Question

InfraStruXure Manager remains in a critical state when monitoring another InfraStruXure Manager

"When two or more InfraStruXure Managers are monitoring each other, any alarm state that occurs within one of the InfraStruXure Managers will remain active in the second InfraStruXure Manager even after the alarm has cleared.

For Example:

InfraStruXure Manager A is listed in InfraStruXure Manager B's device list and InfraStruXure Manager B is listed in InfraStruXure Manager A's device list. In this scenario, each of the InfraStruXure Managers are monitoring each other. If an alarm state occurs with a device InfraStruXure Manager A is monitoring, InfraStruXure Manager A will transition to an alarm state and InfraStruXure Manager B will transition to the same an alarm state. Because InfraStruXure Manager A and InfraStruXure Manager B are managing each other in a peer to peer structure, both InfraStruXure Managers will remain in an alarm state even after the alarm clears in the device managed by InfraStruXure Manager A. This continual state occurs because InfraStruXure Manager A sees InfraStruXure Manager B in an alarm state, which in turn keeps it in an alarm state thus creating an alarm loop between the two InfraStruXure Managers.

APC suggests not to monitor ISX managers as a peer to peer relationship. APC recommends setting up a Master/Slave relationship between two managers where one is monitoring the other but not vice versa."