> Source: https://docs.nometa.az/device-panels/apic

# Cisco ACI (APIC)

SAMURAI reads the ACI fabric through the APIC controllers — fabric nodes, tenants, application profiles, EPGs, bridge domains, VRFs, contracts and filters — and resolves endpoints to their owning leaf.

> Open a device from the **Devices** page or the sidebar to reach these tabs.

## Fabric

ACI fabric inventory — spine/leaf switches and APIC controllers — with role, model and reachability.

![Fabric](/img/05-device-panels/apic/apic-01-fabric.png)

## Hosts

Endpoints learned by the fabric (fvCEp), resolved to tenant / application-profile / EPG.

![Hosts](/img/05-device-panels/apic/apic-02-hosts.png)

## Vrfs

VRFs (private networks) and their associations.

![Vrfs](/img/05-device-panels/apic/apic-03-vrfs.png)

## Bds

Bridge domains and their subnets.

![Bds](/img/05-device-panels/apic/apic-04-bds.png)

## Epgs

Endpoint groups — the policy unit endpoints belong to.

![Epgs](/img/05-device-panels/apic/apic-05-epgs.png)

## Contracts

Contracts and their consumer/provider EPGs — the ACI access policy.

![Contracts](/img/05-device-panels/apic/apic-06-contracts.png)

## App Profiles

Application profiles grouping related EPGs.

![App Profiles](/img/05-device-panels/apic/apic-07-app-profiles.png)

## Filters

Filters and entries (protocol/port) referenced by contracts.

![Filters](/img/05-device-panels/apic/apic-08-filters.png)

## Changes

Configuration changes over time, correlated to the responsible admin where audit data is available. Cards expand to a field-level diff.

![Changes](/img/05-device-panels/apic/apic-10-changes.png)
