Switch inventory
Inventory identity, scope, availability and per-switch workspace.
Inventory fields
Switch records are organized by Site and Group and include management address, model/AOS identity, availability state and optional power-source association. Inventory management requires the inventory.manage capability and remains scope constrained.
Import
CSV/XLSX import is bounded in 2.0.0 against oversized and hostile files. The current hardening limits uploads, rows, columns, cell lengths, XLSX archive entries and expanded size/compression ratio.
Verification
Device verification uses the ALE identity path and driver detection. Device identity changes can invalidate learned capability evidence so commands may be evaluated again after software upgrades or hardware replacement.
Stack monitoring
Stack/Virtual Chassis health can use read-only SSH or SNMPv3 Monitoring Credentials. Baseline learning and degraded/recovered incident logic remain separate from simple management-IP reachability.
Inventory identity and verification
A switch record stores management identity, Site, Group, enabled state and resolved AOS profile. Personal SSH passwords are not stored with the device. Add and edit workflows can verify reachability and platform identity before operational use.
Runtime identity combines configured profile with observed model and AOS evidence. Capability learning is tied to device, profile, model and version, so a software upgrade or hardware replacement invalidates stale rejection evidence.
Bulk import
CSV and XLSX import validates the supplied template before persistence. Import creates inventory; it is not proof that every address is reachable or supported. Follow it with verification and an explicit health scan.