Your first Opia workflow

Before you begin

• Use a supported Windows x64 workstation and an account that can approve installation elevation.
• Have authorised SSH access to at least one Cisco IOS or IOS-XE device. Include enable-mode access where the commands you need require it.
• Have the Opia installer and a route to your authorised licence-issuance process. The Opia workstation itself does not need internet access for activation.

1. Install and open Opia

Run OpiaSetup-26.8.1.exe. During setup, choose the Windows user or security group that will become the first Product Administrator. After installation, open Opia normally from the Start menu; routine use does not require Run as administrator.

See Installation for the full walkthrough.

2. Check the Dashboard

The Dashboard should show a current Opia Agent rather than a missing, stale, degraded or faulted state. The Agent is responsible for queued and scheduled work.

3. Activate the installation offline

1. Open Settings → Licensing.
2. Select Generate Licence Request, then Export Licence Request to save the .opiareq file.
3. Send that request through your authorised licensing route.
4. Return the signed .opialic file to the Opia workstation and select Import Licence.
5. Confirm the expected licence status, customer, capacity and entitlements.

See Licensing for renewals, capacity and troubleshooting.

4. Add your first device

1. Open Devices and select Add Device.
2. Enter a clear display name and the management IP address or resolvable hostname.
3. Choose the appropriate Cisco platform/driver context and assign a credential profile.
4. Save the device and run Test Connection.

A new device provisionally consumes one Managed Network Unit until trusted inventory evidence confirms its physical chassis or stack membership.

5. Configure secure device access

Create or select a credential profile using a password or private key, and add an enable secret only where the device requires it. Opia protects stored secrets through the Agent and does not display stored passwords or export private-key contents.

On first connection, review SSH host-key information carefully. Treat an unexpected host-key change as something to investigate before accepting it.

6. Run your first backup

Open Backups and run a backup for the device. A successful collection creates a history record. Once more than one successful backup exists, use the comparison view to review configuration changes.

7. Fingerprint the device

Run device fingerprinting to collect the identity and network evidence available from that platform. Depending on the device and enabled features, this can include chassis and stack data, interfaces, VLANs, trunks, neighbours, STP, HSRP, routes and routing-protocol information.

A partial result can still be useful. An unsupported or unavailable optional command is not automatically a failed collection.

8. Review inventory and topology

Use the device inventory to review the collected evidence, then open Topology. Observed CDP/LLDP relationships and evidence-based inferred relationships are shown differently; review inferred links before relying on them.

9. Review Operations and Issues

Open Operations → Activity Runs for execution, progress, results and history. Use Operations → Action Queue to review issues, inspect supporting evidence and take available follow-up actions.

10. Add automation when the basics are healthy

Once connectivity, backup and fingerprinting work reliably, create activities in Automation. Start with a small target set and confirm the next scheduled run before expanding to the wider environment.

Good first-run checks

• The Agent heartbeat is current.
• The application and Agent show the expected licence state.
• A representative device passes connectivity, backup and fingerprinting.
• Backup and report locations match your storage policy.
• SMTP is tested before email notifications are relied upon.
• You can generate and review a support bundle if required.