[Implemented] Better config backup support for Siklu MH-T280?
Posted: Mon Sep 12, 2022 6:50 pm
I recently added a Siklu MH-T280 device to our Unimus instance. Discovery appeared to work ok, with the device being detected as Vendor: Siklu, Type: MultiHaul, Model: MH-T280.
However, the way Unimus supports this device is imperfect because there is some status information that changes regularly that is included in the "config" that is backed up. This causes Unimus to detect a "configuration change" every day.
The specific items that are changing are in the stanza under "radio-common { links { active { ...". For example, the rssi, snr, mcs-rx, mcs-tx, speed-rx, speed-tx, and the values under the counters stanza nested in there, too.
I'd like to see Unimus ignore this link status information and counters when it backs up the config.
Is there any other info I should provide to make this request more clear? Thanks!
However, the way Unimus supports this device is imperfect because there is some status information that changes regularly that is included in the "config" that is backed up. This causes Unimus to detect a "configuration change" every day.
The specific items that are changing are in the stanza under "radio-common { links { active { ...". For example, the rssi, snr, mcs-rx, mcs-tx, speed-rx, speed-tx, and the values under the counters stanza nested in there, too.
I'd like to see Unimus ignore this link status information and counters when it backs up the config.
Is there any other info I should provide to make this request more clear? Thanks!