Router synchronization and session accounting

Prerequisites and authority

Network/RouterOS authority, known topology and a recovery management path are required. Preserve existing router configuration before managed changes.

Synchronize router state and accounting

Synchronization compares BryanNet entitlement/account state with router execution state. Accounting records connections and usage over time. They interact but should be investigated separately.

Inspect the router's recent successful synchronization, current account/profile and operation failures. For accounting, compare active router sessions, completed sessions and subscription usage segments. Stale polling can make the display lag behind actual traffic.

Identify the affected router and time window.
Confirm current reachability and source clock/timezone.
Check event delivery and worker progress.
Compare the specific account/session to its subscription.
Use a supported reconciliation action when safe.
Verify subsequent updates and historical totals.

At a subscription boundary, traffic must be attributed to the correct entitlement. The inspected activation service starts a fresh accounting segment for a session that remains connected. End-to-end handling of counter resets, reconnects and multi-router traffic still requires tests.

Never sum repeated cumulative router counters as if each sample were new usage. Similarly, do not add historical and live totals when they represent overlapping traffic. Subscription and provisioning state model describes the model and Usage or device/session accounting looks wrong covers diagnosis.

Keep the original session evidence before any correction. A repaired current account does not automatically establish that past accounting is correct.

Router synchronization and session accounting

Prerequisites and authority

Synchronize router state and accounting

Related guides