Hey @Johannes Luther
The information you provided from the Cisco ACI Virtualization Guide for version 5.2x indicates that Cisco APIC creates alarms for Distributed Virtual Switch (DVS) and port-group when an Endpoint Group (EPG) or Domain policy is deleted on the Cisco APIC. However, you mentioned that you cannot see any alarm definitions at the folder level in vCenter.
Here are a few points to consider:
Version and Documentation Accuracy: Ensure that you are referring to the correct version of the documentation that matches your Cisco ACI and vCenter versions. Sometimes, documentation might have discrepancies or might not be updated to reflect the latest changes.
Alarm Location: The documentation states that the alarms are created in the folder, but it does not specify the exact location within vCenter. Typically, alarms in vCenter can be found under the "Alarm Definitions" section for the specific object (e.g., DVS, port-group, or folder). If you do not see them at the folder level, try checking the DVS and port-group levels directly.
Permissions and Visibility: Ensure that you have the necessary permissions to view and manage alarms in vCenter. Sometimes, certain alarms or configurations might not be visible due to permission restrictions.
Integration and Configuration: Verify that the integration between Cisco ACI and vCenter is correctly configured. If there are any issues with the integration, the alarms might not be properly created or propagated to vCenter.
Alarm Definitions: If the alarms are not visible, it might be possible that the alarm definitions were not created or propagated correctly. You might need to manually check the configuration or re-establish the integration.
Support and Updates: If you are still unable to locate the alarms, consider reaching out to Cisco support or checking for any updates or patches that might address this issue.
To summarize, while the documentation states that alarms should be created, there might be several reasons why you are not seeing them in vCenter. Double-check the integration, permissions, and specific locations within vCenter. If the issue persists, contacting Cisco support for further assistance would be a prudent next step.
Hope This Helps!!!
AshSe
Forum Tips:
- Insert photos/images inline - don't attach.
- Always mark helpful and correct answers, it helps others find what they need.
- For a prompt reply, kindly tag @name. An email will be automatically sent to the member.
