View source for KitsNet Network:LAN:absolut:CAPsMAN Migration


= CAPsMAN Migration: Courvoisier → Absolut =

This document describes the complete migration of CAPsMAN control from
'''courvoisier''' to the CHR instance '''absolut''' while keeping wireless client
traffic off the CHR in the final state.

The migration is performed in two stages:

# '''Interim migration state''' – CAPsMAN moves to Absolut while Guest traffic temporarily traverses the CHR.
# '''Final controller‑only state''' – client traffic no longer traverses Absolut.

----

== Supporting Configuration Patch Files ==
[[File:Courvoisier-final-post-migration-patch.rsc.txt]]
[[File:Absolut-final-controller-only-patch.rsc.txt]]
[[File:Courvoisier-interim-guest-transport-patch.rsc.txt]]
[[File:Absolut-interim-migration-patch.rsc.txt]]
----

== Architecture Context ==

Final architecture goals:

{| class="wikitable"
! Component !! Role
|-
| '''absolut'''
| CAPsMAN controller (control plane only)
|-
| '''courvoisier'''
| edge router and Guest DHCP server
|-
| '''radix.kitsnet.us (192.168.15.1)'''
| DHCP server for main and IoT WLAN
|}

Wireless data traffic must remain on the physical network and must not
traverse the CHR once the migration is complete.

----

== SSID Design ==

{| class="wikitable"
! SSID !! Purpose !! DHCP Source
|-
| KitsNet
| trusted WLAN
| radix.kitsnet.us
|-
| KitsNetIN
| IoT devices
| radix.kitsnet.us
|-
| KitsNetGN
| guest WLAN
| courvoisier
|}

----

== Preconditions ==

Before beginning the migration verify:

=== CAP state ===

On Courvoisier:

<pre>
/caps-man remote-cap print detail
</pre>

Expected:

* able – Run
* baker – Run

=== CAP configuration ===

On Able and Baker:

<pre>
/interface wireless cap print
</pre>

Verify:

<pre>
enabled: yes
lock-to-caps-man: no
caps-man-addresses: 192.168.15.6
</pre>

=== Guest DHCP ===

On Courvoisier:

<pre>
/ip dhcp-server print detail
</pre>

Confirm DHCP server bound to bridge:

<pre>
BWF.KitsNetG
</pre>

----

== Stage A – Interim Migration State ==

During migration Guest traffic may temporarily traverse Absolut.
This allows the CAPsMAN controller to move while keeping Guest DHCP
hosted on Courvoisier.

=== Design ===

* KitsNet → local forwarding → Radix DHCP
* KitsNetIN → unchanged during migration
* KitsNetGN → temporarily central forwarded to Absolut and bridged back to Courvoisier

----

== Prepare Absolut ==

On Absolut:

<pre>
/caps-man manager set enabled=yes
</pre>

Import CAPsMAN certificates copied from Courvoisier.

Create temporary Guest bridge:

<pre>
/interface bridge add name=BWF.KitsNetG
</pre>

Create EoIP transport to Courvoisier:

<pre>
/interface eoip add name=EOIP.KitsNetG.to.Courvoisier \
 local-address=&lt;ABSOLUT_IP&gt; \
 remote-address=192.168.15.6 \
 tunnel-id=120
</pre>

Attach EoIP to bridge:

<pre>
/interface bridge port add bridge=BWF.KitsNetG interface=EOIP.KitsNetG.to.Courvoisier
</pre>

Change Guest datapath:

<pre>
/caps-man datapath set [find name="DP.KitsNetG"] local-forwarding=no bridge=BWF.KitsNetG
</pre>

----

== Prepare Courvoisier ==

Create matching EoIP interface:

<pre>
/interface eoip add name=EOIP.KitsNetG.to.Absolut \
 local-address=192.168.15.6 \
 remote-address=&lt;ABSOLUT_IP&gt; \
 tunnel-id=120
</pre>

Attach to Guest bridge:

<pre>
/interface bridge port add bridge=BWF.KitsNetG interface=EOIP.KitsNetG.to.Absolut
</pre>

----

== Migration Procedure ==

=== Step 1 – Move Able ===

On Able:

<pre>
/interface wireless cap set caps-man-addresses=&lt;ABSOLUT_IP&gt;
</pre>

Verify on Absolut:

<pre>
/caps-man remote-cap print
/caps-man interface print
</pre>

Test:

* KitsNet connectivity
* KitsNetGN guest DHCP
* IoT connectivity

----

=== Step 2 – Move Baker ===

On Baker:

<pre>
/interface wireless cap set caps-man-addresses=&lt;ABSOLUT_IP&gt;
</pre>

Verify both CAPs on Absolut:

<pre>
/caps-man remote-cap print
</pre>

----

=== Step 3 – Disable Courvoisier CAPsMAN ===

Once both CAPs are stable:

<pre>
/caps-man manager set enabled=no
</pre>

Lock CAPs:

<pre>
/interface wireless cap set lock-to-caps-man=yes
</pre>

----

== Validation ==

On Absolut:

<pre>
/caps-man registration-table print
</pre>

On Courvoisier:

<pre>
/ip dhcp-server lease print
</pre>

Confirm:

* clients on KitsNet obtain DHCP from Radix
* guest clients obtain DHCP from Courvoisier
* both CAPs remain connected to Absolut

----

== Rollback ==

If migration fails revert CAPs to Courvoisier.

On CAP:

<pre>
/interface wireless cap set caps-man-addresses=192.168.15.6
</pre>

Re-enable CAPsMAN on Courvoisier if necessary:

<pre>
/caps-man manager set enabled=yes
</pre>

----

== Stage B – Final Controller‑Only State ==

After a permanent Guest L2 path exists outside the CHR:

On Absolut:

<pre>
/caps-man datapath set [find name="DP.KitsNetG"] local-forwarding=yes
</pre>

Remove temporary EoIP:

<pre>
/interface bridge port remove [find interface="EOIP.KitsNetG.to.Courvoisier"]
/interface eoip remove EOIP.KitsNetG.to.Courvoisier
/interface bridge remove BWF.KitsNetG
</pre>

On Courvoisier:

<pre>
/interface bridge port remove [find interface="EOIP.KitsNetG.to.Absolut"]
/interface eoip remove EOIP.KitsNetG.to.Absolut
</pre>

----

== Final State ==

* Absolut runs CAPsMAN only
* Courvoisier serves Guest DHCP
* Radix serves LAN DHCP
* CAPs locally forward all client traffic
* no wireless data traffic transits the CHR