# Cisco ACI Analyzer · Monitoring & Visibility

> Analyze and monitor Cisco ACI fabrics from APIC and NDO: tenants, EPGs, bridge domains, contracts, endpoints, and fabric health. Read-only, self-hosted.

Last updated: June 2026

Read-only analysis and monitoring of ACI fabrics:

- **APIC + NDO**: tenants, application profiles, EPGs, bridge domains, contracts, and endpoints, searchable, so you can answer "what talks to what" on the fabric.
- **Endpoint visibility**: fabric endpoints (fvCEp) correlated with MAC, IP, and the leaf and port they live on, joined to the wider endpoint table.
- **NDO multi-site**: Nexus Dashboard Orchestrator schemas and templates for multi-site fabrics.
- **APIC clustering with automatic failover**: configurable thresholds and cooldown windows keep the fabric monitored even when a controller goes down.
- **Change detection** transaction-grouped (txId) per APIC, attributed to the admin.

Monitoring and visibility only; SAMURAI does not push configuration to the fabric.

## How SAMURAI fits next to APIC

| | SAMURAI | APIC alone |
|---|---|---|
| Role | Read-only monitoring, search, and change history across fabrics | The fabric controller and configuration source of truth |
| Scope | ACI plus firewalls, routers, switches, ISE, and vCenter in one view | The ACI fabric it controls |
| Change history | Cross-fabric change timeline, transaction-grouped, admin-attributed | Per-controller audit log |
| Deployment | Single self-hosted Docker container, air-gap friendly | Part of the ACI fabric |

## Frequently asked questions

### How does SAMURAI connect to Cisco ACI?

Read-only to the APIC REST API, and to Nexus Dashboard Orchestrator (NDO) for multi-site fabrics. It reads tenants, EPGs, bridge domains, contracts, endpoints, and fabric state. It does not push configuration.

### Does it support APIC clustering?

Yes. SAMURAI tracks the APIC cluster per site and, after a configurable number of consecutive failures, fails over to a healthy controller automatically with a cooldown, so monitoring continues if the primary is unavailable.

### Can it track who changed ACI configuration?

Yes. Changes are detected from real fabric state, grouped by APIC transaction (txId), and attributed to the admin, with timezone-aware timestamps, so you get a readable change history without parsing the raw audit log.

### Does it cover multi-site ACI?

Yes, via Nexus Dashboard Orchestrator (NDO): schemas and templates are read alongside the per-site APIC state, so cross-site policy is visible in the same dashboard.

---

Canonical page: https://nometa.az/en/cisco-aci-analyzer/
Part of SAMURAI, a self-hosted, multi-vendor network monitoring & security platform. Overview: https://nometa.az/llms.txt
Contact: info@nometa.az · Docker Hub: https://hub.docker.com/r/beyrak44/samurai