Moving from DeltaSIB
This page explains the technical side of migrating, for the network team. For the overall path, see Move to Farava Platform.
First rule: no outage
Section titled “First rule: no outage”Throughout the pilot, DeltaSIB and your current customer app keep running. Only the small pilot group is on Farava, and every stage can be rolled back.
Isolate the pilot
Section titled “Isolate the pilot”- Pick a separate NAS, PPPoE service, or VLAN for the pilot.
- Start with staff, technicians, or volunteer users — not sensitive business customers.
Never split one session’s accounting
Section titled “Never split one session’s accounting”Each RADIUS session must report to one accounting system. The START, INTERIM, and STOP packets of a session must not be split between DeltaSIB and Farava, or neither system’s usage will be correct. Also do not assume that two RADIUS servers configured on a router receive the same accounting data.
The router is controlled over RADIUS, not an API
Section titled “The router is controlled over RADIUS, not an API”Unlike DeltaSIB, Farava does not create MikroTik queues through the API. Speed limits are sent as RADIUS attributes. Before migrating, review with our team any queues or scripts that DeltaSIB creates on the router. Details are in How it works.
Automatic import from DeltaSIB is in development. During the pilot, the pilot group’s subscribers are created through the admin panel, and no invented usage or financial history is entered into the system.
Bring each customer’s balance (debt or credit) over once with an opening balance, using the DeltaSIB reference.