Known limits

We would rather you read this here than find it out on a live network.

Restore and push

• Restore is a proposal, not a rollback. Read it before confirming. Banners, certificates and order-sensitive lists such as ACLs may need manual correction. FortiOS restore re-applies changed blocks only; RouterOS restore is not supported.
• Push sends exactly what you type. It adds no configuration-mode or save commands and does not work out commands for you. There is no automatic rollback.

Firmware

• Retivo does not check the vendor's upgrade path. Check it yourself.
• Cisco: .bin images only (no .tar). Stacks and install mode need extra care. Reload order does not follow the topology.
• Always try one device first.

Data and matching

• Vulnerability matching uses the OS version only, not the hardware model or which features are enabled. Some matches will not apply to a given device.
• Data over SSH covers RouterOS, Cisco IOS and IOS XE, FortiOS and TP-Link JetStream.
• Service checks fall back to whether the port answers from the node, which a firewall in between can change.
• Storage space is read over SNMP, or over SSH on RouterOS and Cisco. Other devices show none.

Access

• SSH logins use username and password. SSH keys are not supported yet. Host keys are accepted on first contact.

Specific platforms

• Starlink has no SSH or SNMP. Retivo only checks that it answers.
• Aruba Instant On is experimental and read-only. It uses the same sign-in as the Instant On portal, so it can stop working when the portal changes, and the account must not use two-factor authentication. Use a separate view-only account.

Notifications

• Notifications appear under the bell in Retivo. Apart from the scheduled status report, nothing is sent by email or chat yet.

NetBot

• Without a model, NetBot matches questions to its built-in guide by keywords. With a model, answers depend on the model; small local models may pick the wrong tool. Every change still waits for your confirmation.