OpiaDocumentation

Opia documentation

Collect and understand device evidence

Collect structured device evidence that improves identity resolution and topology.

Applies to Opia 26.8.1

Fingerprinting and Inventory Collection gather read-only evidence from supported Cisco IOS and IOS-XE devices. The available detail depends on the platform, software release, enabled features and command privileges.

Run a collection

Start fingerprinting for a selected device or create a Fingerprint activity in Automation. Inventory Collection is a separate activity type. Both use the device's assigned credential profile and can run manually or on a schedule.

What Opia can collect

Where the device supports the relevant commands, Opia can collect and normalise:

  • Platform, serial number, software version, chassis and stack information.
  • Interfaces, descriptions and IP interface summaries.
  • VLANs, trunks and EtherChannel/port-channel membership.
  • CDP and LLDP neighbours.
  • MAC and ARP endpoint evidence.
  • STP root, role and state information.
  • HSRP groups, Active/Standby roles and virtual IP addresses.
  • IP routes, VRFs and available OSPF, EIGRP or BGP neighbour/summary information.

Partial results are expected

Not every command exists on every device. Optional commands can be unsupported, unavailable because a feature is disabled, denied by privilege, empty, timed out or incomplete. A partial collection can still contain valid evidence.

Router-like devices intentionally skip switch-only commands. Opia 26.8.1 does not claim general support for NX-OS, ASA or other vendors.

Use inventory to improve identity and topology

Consistent evidence from both ends of a link improves topology confidence, port labels, parallel-link grouping, device roles, HSRP peers and STP presentation. When identity evidence conflicts, compare management addresses, serial/platform information and neighbour observations before merging or separating records.

When a collection looks wrong

  • Run Test Connection first.
  • Review individual command outcomes rather than treating every partial result as a failed connection.
  • Confirm the feature exists on that exact device and software release.
  • Review Operations for related Inventory, Automation or Device issues.
  • Generate a support bundle if you need to escalate.