Dear Forum,

I have rb133c version 2.9.43 on my client. I want to upgrade it to version 4, which support superchannel. How do i upgrade it in a safe way. Do i have to upgrade it to version 3.xx first and then upgrade it to version 4?

this is what the console says :
thx in advance

I have rb133c version 2.9.43 on my client. I want to upgrade it to version 4...

The format of the software key changed during 3.x, and I believe the upgrade path for that will also let you get at least to 4.x, but... I don't think you're going to have much luck running 4.x on a 133; in my experience the CPU will be pegged at 100% even when it's idle.

is it possibly because of stable / unstable version of 4.xx that caused the 100% cpu usage?

Step 1: Remove Rb133c

Step 2: Purchase RB711/Rb-SXT/Groove-5Hn

Step 3: Install

Step 4: Enjoy hardware that could actually handle more bandwidth.



I've heard of people upgrading to 4.X but the CPU on the RB133c is a it slow to handle increased

bandwidth.

Step 1: Remove Rb133c

Step 2: Purchase RB711/Rb-SXT/Groove-5Hn

Step 3: Install

Step 4: Enjoy hardware that could actually handle more bandwidth.



I've heard of people upgrading to 4.X but the CPU on the RB133c is a it slow to handle increased

bandwidth.

nice suggestion, mate But add cost for purchasing pair of boards and the time to climb the tower, which are triangle type of tower, to replace the board.

but is it really no happy ending story for this case? poor me..

I know some people, like wirelessrudy, have upgraded several RB133c to higher level ROS.

he experienced very high cpu usage on ROS 4.X though according to him, he was able to get ROS 5.1/5.2 working on those units.

give some time, i'm sure he will chime in about it

is it possibly because of stable / unstable version of 4.xx that caused the 100% cpu usage?

I have a couple 133s around the shop that I have tried with various versions of 4.x over the past year. It didn't matter whether it was an early or late 4.x, CPU is at 100% much of the time. Most recently, I tried to use them just to bridge wlan1 to eth1. They became unstable as soon as a couple people got on, probably because of the CPU situation.

Admittedly, I haven't tried 5.x on them, and maybe the software is now efficient enough that its idle loop won't bring it to its knees! In any case, I would plan on replacing the 133 with a 411 sooner or later.

I know some people, like wirelessrudy, have upgraded several RB133c to higher level ROS.

he experienced very high cpu usage on ROS 4.X though according to him, he was able to get ROS 5.1/5.2 working on those units.

give some time, i'm sure he will chime in about it

dear @wirelessrudy... please visit my thread...
@lazerusrm what is the magic words to summon mr wirelessrudy

is it possibly because of stable / unstable version of 4.xx that caused the 100% cpu usage?

I have a couple 133s around the shop that I have tried with various versions of 4.x over the past year. It didn't matter whether it was an early or late 4.x, CPU is at 100% much of the time. Most recently, I tried to use them just to bridge wlan1 to eth1. They became unstable as soon as a couple people got on, probably because of the CPU situation.

Admittedly, I haven't tried 5.x on them, and maybe the software is now efficient enough that its idle loop won't bring it to its knees! In any case, I would plan on replacing the 133 with a 411 sooner or later.

yes.. according to @lazerusrm, @wirelessrudy has done it before with 5.xx . but a live testimonial would be nice isn't it

to have more performance and throughput..
purchase the new routerboard will be the better idea.

I am running several 133C's on 5.2. They will run ok as long as you disable all unnecessary packages and don't a bunch of nat rules on it. The upgrade procedure I have done is.

1. Upgrade FW.
2. Reboot
3. Disable all packages other than what has to be there.
4. Reboot
5. Upload 3.0
6. Reboot
7. Update license and Upgrade FW if it needs it
8. Reboot
9. Upload 4.16
10. Reboot
11. Check FW and license again and update if needed
12. Reboot if either needed upgraded
13. Check to make sure I don't have noise floor threshold or custom data rates set, If you do disable noise floor threshold and set default rates.
14. Upload 5.2
15. Reboot
16. Change wireless mode to whatever mode you want. If it is a client set it to "any" if it is an AP set it to the mode you want to run.

A 133C running 5.2 is only going to move about 10Mbs traffic if it is setup as a simple CPE with masquerading.

Chadd

I am running several 133C's on 5.2. They will run ok as long as you disable all unnecessary packages and don't a bunch of nat rules on it. The upgrade procedure I have done is.

1. Upgrade FW.
2. Reboot
3. Disable all packages other than what has to be there.
4. Reboot
5. Upload 3.0
6. Reboot
7. Update license and Upgrade FW if it needs it
8. Reboot
9. Upload 4.16
10. Reboot
11. Check FW and license again and update if needed
12. Reboot if either needed upgraded
13. Check to make sure I don't have noise floor threshold or custom data rates set, If you do disable noise floor threshold and set default rates.
14. Upload 5.2
15. Reboot
16. Change wireless mode to whatever mode you want. If it is a client set it to "any" if it is an AP set it to the mode you want to run.

A 133C running 5.2 is only going to move about 10Mbs traffic if it is setup as a simple CPE with masquerading.

Chadd

Wow.. Finnaly a live testimonial and great detail too
I'll give it a try and get back here to give the report. Many thanks Mr.Chadd

Wow.. Finnaly a live testimonial and great detail too
I'll give it a try and get back here to give the report. Many thanks Mr.Chadd

No problem,

A few other things worth mentioning. It takes quite a while to load 4.x and 5.x on a 133C so be patient and make sure that if it is at a customer location that you let them know what is up so they don't power cycle it during an upgrade because you will have to net install then.

If it works out for you hit the karma button

Chadd