Optiwize: devices, monitoring, and backups

Integration scope

Optiwize connects ISP Billing with provider-side router organization, onboarding, monitoring, administrative access, hardware information, and configuration backups. ISP Billing keeps customer and service context while Optiwize remains authoritative for managed devices and sessions.

Use it only for equipment enrolled in the intended account. Creating a device does not replace RouterOS configuration, network authorization, change control, or a verified backup.

Account setup and connection check

Enter the authorized Optiwize username and password under settings. Opening Devices, Groups or Backups performs a lightweight provider read; missing credentials or a failed connection returns the operator to setup. Use a dedicated integration account where available and never expose the password in screenshots or support tickets.

Saving credentials stores them for the ISP tenant but does not prove that every device operation is authorized. Verify with a harmless list before creating or changing provider records.

Groups

Groups organize devices by POP, site, customer or operational responsibility. Create a clear group name and optional provider-side password; editing sends group ID, new name and applicable values to Optiwize.

Do not reuse RouterOS credentials as a group password. Before renaming or moving equipment, review provider dashboards, access policy and operators that rely on the group.

Add a device

Create the provider record with a recognizable name and appropriate optional group. Verify POP, customer or operational ownership before saving. Creation prepares inventory but does not connect the MikroTik; check the returned provider device ID and avoid recreating it when onboarding is the only missing step.

Onboard a MikroTik

OnBoard retrieves provider-generated commands for the selected device. Back up the router, review every command, verify target identity and RouterOS compatibility, and execute them only through the authorized change procedure.

Afterward confirm serial, model, RouterOS, management IP, group, last contact, and the independent Monitoring, Backup, SD-WAN, and OnBoard states.

Read device state

The provider inventory exposes device ID, name, serial, model, RouterOS version, public or management IP, group, and last contact. Monitoring, Backup, SD-WAN, and OnBoard are independent indicators.

Use timestamp and status together. A listed device may be offline or partially configured, and an old backup does not prove that current configuration is protected.

Edit a device

Editing updates supported metadata such as name or group while retaining provider identity. Compare device ID, serial, management IP, current group, and ownership before saving.

The change does not migrate network configuration or access policy automatically. Reload the provider record and verify group permissions, monitoring, and backup association afterward.

Console, WinBox, and board

Console and WinBox request a provider token and redirect to an administrative session for the selected device ID. The board action retrieves current hardware information. Verify device and title before opening, never share the tokenized URL and close the session afterward.

Changes performed remotely are outside the ordinary ISP Billing form lifecycle and must follow the ISP’s authorization, backup and change-record procedure.

Backups and downloads

The backup area first lists devices and then the backup files available for one device. Download requires both device ID and exact backup name and returns the provider content as a plain-text attachment with that name.

Validate device, timestamp, RouterOS version, completeness and restore procedure. Store configurations as secrets because they may contain network topology and credentials.

Checklist

Use authorized credentials
Verify a harmless provider read
Define groups and ownership
Use distinct group passwords
Create recognizable device names
Review onboarding commands
Run them on the correct router
Check last contact and all four states
Confirm device ID before remote access
Protect Console/WinBox tokens
Verify and secure backups