The Topology section provides information on specific classes, attributes, relationships, and events related to the topology objects created to represent Cisco ACI.
Cisco ACI version 4.1 is supported in VMware Telco Cloud Operations.
For more information on getting the topology data, see the #GUID-54DB1EFA-0E78-4154-A665-4988E8CA8C29.
The following logical entities are created on the top of existing physical fabric:
|Class||Key Attributes||Key relationship||Problem and Event|
IsAnyComponentDown IsClusterDown IsEveryComponentDown NumberOfComponent NumberOfFaultyComponents
ComposedOf Manages ProvidesClientServiceTo
AllComponentsDown AtRisk Down ReducedRedundancy
The table Support of Cisco ACI Components in IP describes the components which are discovered as a part of Cisco ACI
|AggregatePort||Aggregate Port / Port Channel||YES||YES||Only AdminStatus are monitored.|
|BridgeDomain||Bridge Domain||YES||NO||BridgeDomains which are not associated to any EPG are not discovered.|
|Card||Line Card, Supervisory Card||YES||YES|
|Contract||Contract||YES||YES||Contracts which are not associated to any EPG are not discovered.|
|ControlCluster||APIC Cluster||YES||NO||Events are raised based on ControllerNode monitoring.|
|EndPointGroup||End Point Group (EPG)||YES||NO|
|Fan||Fabric Switch Fan||YES||YES|
|MAC||MAC Address||YES||NO||Created only for a network Connection, but not associated to a Port.|
|Memory||Fabric Switch Memory||YES||YES||Only Free Memory monitored.|
|Port||Fabric Switch Port||YES||YES||Port use, error, and the discard rate are monitored with fault monitoring.|
|PowerSupply||Fabric Switch Power supply||YES||YES|
|Processor||Fabric Switch Processor||YES||NO||Cisco does not expose APIs to monitor the processor use.|
|Switch||Fabric Switch (Leaf and Spine)||YES||YES|
|TemperatureSensor||Fabric Switch Temperature Sensor||YES||YES|
|Tenant||Cisco ACI Tenant||YES||NO||Tenants which are not associated to any EPG are not discovered.|
Connection between Leaf to Spine
Leaf to Ext Switch, Spine to Ext Switch
|vAggregatePort||Virtual Port Channel||YES||NO|
Note: The Kafka_Service object is created to support fail-over as a part of discovery, for internal purposes. The text boxes DiscoveryTopic and Monitoring Topic are empty and must not be populated as they have no effect on either discovery or monitoring of Cisco ACI fabric.