PCC load balancing does not work after upgrade
routes does not work
: urgent help I have the same problem with load balancing, I have a rb850
PCC load balancing does not work after upgrade
routes does not work
same here: I'm running 3 hap ac here (1 is capsman+cap the other two are cap) and since upgrading to 6.35.1 I see the cap (on the box with capsman running) missing in capsman. rebooting not solving anything, disable/enable caps not working. the wlan interfaces do show and scanning does work. however when turning them on (as local wlan) the default microtik ssid also does not come alive and no loggingwe can confirm observance that pcq load-balancing stopped working after upgrading to v6.35.1 because of main-routes becoming inactive.
also snmp health monitoring fails since the upgrade.
we are running capsman so we need the fixes in there...
reverting to v6.35 resolves the pcq balancing issue and health monitoring but introduces again loss of caps interfaces
reverting back to v6.35 resolves the problem
I'd like more specific info on each item with a date/timestampwa4zlw, this 2016-Apr-25 09:29 is a timestamp for the listed features, when they were added to the specific version.
What vendor - model transceiver you use in that CRS125? Possibly it is having some trouble reporting info back to host.Please FINALLY FIX SFP DDM INFORMATION READING
On CRS125, there is nothing shown in SFP tab...
HOWEVER i've successfully readen DDM data (and RX/TX power was updated few times a seconds too) today on CRS125.
How it's fixed?
Run CRS125 without SFP module.
Tick system restart, while restarting PLUG SFP module in.
DDM data is there.
If you will reboot CRS now, DDM will not come back anymore
[igb@rb2011-1] /system identity> /system routerboard print
routerboard: yes
model: 2011UiAS
serial-number: 444702957500
firmware-type: ar9344
factory-firmware: 3.09
current-firmware: 3.18
upgrade-firmware: 3.33
[igb@rb2011-1] /system identity> /system health print
voltage: 1143.7V
[igb@rb2011-1] /system identity>
[igb@rb2011-1] > /system health print
voltage: 24.1V
temperature: 27C
[igb@rb2011-1] > /system routerboard print
routerboard: yes
model: 2011UiAS
serial-number: 444702957500
firmware-type: ar9344
factory-firmware: 3.09
current-firmware: 3.33
upgrade-firmware: 3.33
[igb@rb2011-1] >
They are AscentOptics modules, you can get datasheet from there:What vendor - model transceiver you use in that CRS125? Possibly it is having some trouble reporting info back to host.Please FINALLY FIX SFP DDM INFORMATION READING
On CRS125, there is nothing shown in SFP tab...
HOWEVER i've successfully readen DDM data (and RX/TX power was updated few times a seconds too) today on CRS125.
How it's fixed?
Run CRS125 without SFP module.
Tick system restart, while restarting PLUG SFP module in.
DDM data is there.
If you will reboot CRS now, DDM will not come back anymore
The bug started on 6.34.1The voltage displayed for an RB2011UiAS is not plausible. 1143.7V?
Edit to add: fixed by firmware update, so the problem is 6.35.1 (and perhaps earlier, I don't know when this problem started) plus firmware 3.18 (ditto).Code: Select all[igb@rb2011-1] /system identity> /system routerboard print routerboard: yes model: 2011UiAS serial-number: 444702957500 firmware-type: ar9344 factory-firmware: 3.09 current-firmware: 3.18 upgrade-firmware: 3.33 [igb@rb2011-1] /system identity> /system health print voltage: 1143.7V [igb@rb2011-1] /system identity>
Code: Select all[igb@rb2011-1] > /system health print voltage: 24.1V temperature: 27C [igb@rb2011-1] > /system routerboard print routerboard: yes model: 2011UiAS serial-number: 444702957500 firmware-type: ar9344 factory-firmware: 3.09 current-firmware: 3.33 upgrade-firmware: 3.33 [igb@rb2011-1] >
[admin@Cendana] > sys reso pr
uptime: 18h25m32s
version: 6.35.1 (stable)
build-time: Apr/25/2016 09:29:50
free-memory: 86.5MiB
total-memory: 128.0MiB
cpu: MIPS 74Kc V4.12
cpu-count: 1
cpu-frequency: 600MHz
cpu-load: 28%
free-hdd-space: 104.0MiB
total-hdd-space: 128.0MiB
write-sect-since-reboot: 177879
write-sect-total: 100957409
bad-blocks: 0.8%
architecture-name: mipsbe
board-name: CRS125-24G-1S-2HnD
platform: MikroTik
[admin@Cendana] > sys heal pr
voltage: 24.5V
temperature: 39C
[admin@Cendana] > sys heal pr oid
active-fan: .1.3.6.1.4.1.14988.1.1.3.9.0
voltage: .1.3.6.1.4.1.14988.1.1.3.8.0
temperature: .1.3.6.1.4.1.14988.1.1.3.10.0
processor-temperature: .1.3.6.1.4.1.14988.1.1.3.11.0
current: .1.3.6.1.4.1.14988.1.1.3.13.0
power-consumption: .1.3.6.1.4.1.14988.1.1.3.12.0
psu1-state: .1.3.6.1.4.1.14988.1.1.3.15.0
psu2-state: .1.3.6.1.4.1.14988.1.1.3.16.0
.1.3.6.1.4.1.14988.1.1.3.9.0
.1.3.6.1.4.1.14988.1.1.3.14.0
The same issue!PCC load balancing does not work after upgrade
routes does not work
I don't have exactly those modules for testing, but I checked with various other vendor ones and no problems with any of them.Please FINALLY FIX SFP DDM INFORMATION READING
They are AscentOptics modules, you can get datasheet from there:
http://www.ascentoptics.com/en/dow.asp?Pid=93
These modules DDM works perfectly in other manufacturer equipment (i.e. DASAN networking).[
As I mentioned possibly modules them selves are acting up sometimes. System can stop attempting to read ddmi if there are to many failed attempts.
Yesterday I made the upgrade on my new router CRS125-24G-1S-2HnD, which I got 1 week ago and came running an old sw version, 6.6.
After the upgrade, the wifi clients keeps disconnecting all the time, even when signal is strong. On the logs, I see tons of for all wifi clients:
00:56:CD:XX:XX:XX@wlan1: disconnected, extensive data loss
I tried to downgrade, but for some reason, after the reboot, it came back with the same 6.35.1. I ried also searching the forum for problems like this, but none indicated what could be happening, and since the problem started after the upgrade...
Thanks for any help.
Normis, thank you for your response. Regarding your comments, the wifi signal was working perfectly before the upgrade. Is there any other report of problems with this newer version?Yesterday I made the upgrade on my new router CRS125-24G-1S-2HnD, which I got 1 week ago and came running an old sw version, 6.6.
After the upgrade, the wifi clients keeps disconnecting all the time, even when signal is strong. On the logs, I see tons of for all wifi clients:
00:56:CD:XX:XX:XX@wlan1: disconnected, extensive data loss
I tried to downgrade, but for some reason, after the reboot, it came back with the same 6.35.1. I ried also searching the forum for problems like this, but none indicated what could be happening, and since the problem started after the upgrade...
Thanks for any help.
1. the mentioned log means your signal was not great after all, it means weak signal due to low signal or noise
2. downgrade is done with a special command "/system package downgrade", simple reboot doesn't make downgrade like for upgrades
Normis, thank you for your response. Regarding your comments, the wifi signal was working perfectly before the upgrade. Is there any other report of problems with this newer version?Yesterday I made the upgrade on my new router CRS125-24G-1S-2HnD, which I got 1 week ago and came running an old sw version, 6.6.
After the upgrade, the wifi clients keeps disconnecting all the time, even when signal is strong. On the logs, I see tons of for all wifi clients:
00:56:CD:XX:XX:XX@wlan1: disconnected, extensive data loss
I tried to downgrade, but for some reason, after the reboot, it came back with the same 6.35.1. I ried also searching the forum for problems like this, but none indicated what could be happening, and since the problem started after the upgrade...
Thanks for any help.
1. the mentioned log means your signal was not great after all, it means weak signal due to low signal or noise
2. downgrade is done with a special command "/system package downgrade", simple reboot doesn't make downgrade like for upgrades
yes, the downgrade attempt was done using that command.. but for some reason, after the rebook, it came back with the same version. Just tried again:
[admin@ho-rt-01] > /system package downgrade
Router will be rebooted. Continue? [y/N]:
y
system will reboot shortly
[admin@ho-rt-01] >
And it still came back like:
MikroTik RouterOS 6.35.1 (c) 1999-2016
Any idea?
Best regards.
Now I feel stupid.. hahaDid you upload the old firmware version first to the files area?