I run a small WISP - huge fan of Mikrotik routers. These work fantastically.

I decided to try out the RB260GSP switches and do some testing prior to deploying in the field.

The SFP modules would stop working (bug in 1.11) - this was fixed in 1.12. Seems like a MAJOR bug, but somehow made it into a production release.

I'm running pings from my desktop to the router and latency is 15-18ms, about 5% packet lost (pings not returned) and some come back "MISCOMPARE at offset 0 - time=32ms TTL=255".

These kinds of glitches make me hesitate before putting into production - I don't see these kinds of quality issues on the Routers. I'm also surprised that Winbox can't be used - which is a superb app.

What are your thoughts about the maturity of these devices and overall stability? Ready for prime time/production?

Thanks

260GSP(i have 3 units with different roles) runs without issues for me about 2 weeks.
Poe-out works fine, with vlans - no issues, SFP links automatically without any additional config.
They arrived with swos 1.12.
IMO these units are much beter than 260GS.
So answer to your question - sure these units ready for prime time

I have 30 RouterOS WAPs (wireless access points) in two warehouses. I just recently installed 6 RB260GSP switches in closets with POE to the WAPs. I set POE to "auto" and it powered up most of the WAPs, but would drop out sometimes. Some would indicate 4-7mA current draw and then they would show current too low and start power cycling. I know the WAPs draw more than 100mA and they had no issues when running from individual POE injectors. In fact, I disabled POE on the switch and reinstalled the individual POE injector and the power cycling stopped. I removed the individual POE injector and re-enabled POE on the switch to the "ON" state and it still power cycles randomly. I have a fiber distribution switch feeding the RB260GSP switches and the SFP interfaces work fine. I believe the current sensing circuit or software needs a little work still. Mikrotik is looking into it.

Edit: These switches are running SwitchOS Ver 1.13

Update,

Still having same problem with all six RB260GSP switches. Even though the POE mode is set to "ON" state, they still randomly drop out. Most of the time they power back up within a few seconds. Last weekend I had one drop out and not come back up. I logged in remotely and found the port status as "Overload". I set the port to Off and then back to On with no help. Next I went to Auto which did not help. Then I rebooted the switch and that did not help. I left it in Auto and it powered up by itself about an hour later. When I came to work on Monday, I disabled POE and installed a POE injector between the switch and the access point and I have had no problems since. I have this problem on all the switches and all ports.

Haven't heard from Mikrotik for 3 weeks. Hopefully they are working on it.

I have been using RouterOS access points for 8 years with no trouble on the individual POE injectors. This problem started when I installed the RB260GSP switches.

To troubleshoot this problem these are things that we need to know:

What power source you are using, is this 24V or 12V and how many amps it can supply?
How are you powering your RB260GSP (PoE-In or plug)? If PoE-In how long is the cable to the device?
How long are ethernet runs to the powered devices?
What devices you are trying to power up? What is their listed power consumption? What power consuption is reported by RB260GSP?

Thanks for responding.

The power supply is the one that came with the switches, Model # WT2402500, 24V 2.5A

RB260GSP is not powered by POE. It is powered by supply mentioned above.

Ethernet runs are approximately 100-300'

Most devices are RB912UAG-2HPnD. Most power consumption is between 4-6 watts. Sometimes they falsely show .16 watts. I know this is false because the access point is working fine with a strong RF signal.

ItsMe some problem here buy two 260GPS they or loosing power usually on port 1. Iswitch port 1 to on not auto its little help but today again lose power on port1 and need to off that on and power working again.

My switch have report maximal load per port 130mA and much worst because by default port 1 have higher poe priority plugin backbone link now loosing network every 12h and not have easy access to that switch. Before on some place have 750UP with some device never single problem.
This device have 2 week and before 2 days start loosing power, other device have 2 moths yesterday start losing power also on port3.
I start prepare network to switch to ac and gigabyte port seem to me must go back to 750UP that working.


What to do with this 260GSP send back to RMA ?

0000

we are working on the issue. Hopefully working solution will be ready soon.

we are working on the issue. Hopefully working solution will be ready soon.

Thanks for answer. I will wait sometime don't send back to RMA. If you need to test something I have two 260GSP in real network with this issue.

A little more information,

Looking back at the event log in The Dude, it is usually port 2 that looses power on each switch, but not always. If I understand correctly, Port 2 should have the highest priority and should be the last port to loose power if the overall power consumption maximum has been reached.

Yes some problem I have on two 260GSP, port 2 also on my two RB260GSP, I write port 1 thing first POE port but on case and web it is port 2, some time on port 4 in my case lost power.

if you are interested in trying out possible fix for the issue please write to support@mikrotik.com referring to this post/thread/issue. We will give you access to test firmware for RB260GSP

if you are interested in trying out possible fix for the issue please write to support@mikrotik.com referring to this post/thread/issue. We will give you access to test firmware for RB260GSP

I all ready receive from you 1.14beta2 Ticket#2014081466000195 I will test tomorrow morning and send you screen shoots. If you have new version send it I will tested.

nope beta2 is it.

nope beta2 is it.

Janisk: Why 1.14beta2 is not on pre-release web page? Only ROS 6.19rc
Thansk

I'm not sure if this is related, but I have a strange behavior on my 260GSP (FW 1.13).
Powering various devices like Unifi, NS5 and Aircam works flawless on auto settings.
Just my RB450G needs manual ON, not being detected by auto. After that it works ok.

I installed SwOS 1.14rc2 on three of the switches last Tuesday. One of the switches dropped port 2 and came back up within the first six hours. After that, there have been no problems. I will install 1.14 on the remaining switches and re-enable POE. Overall, 1.14rc2 seems to be a significant improvement in the past week of testing.

Edited to show correct revision number.

I spoke too soon. The same port that went down and came back up in the first six hours did it again yesterday evening. I upgraded the software on the remaining 3 switches to 1.14rc2 and rebooted. One port powered on and then the status read "low current" and it started power cycling again. I forced it to the ON mode and it has stayed up for over 6 hours now.

I also have two 260GSP updated to 1.14rc2 first one now have up time 8 days and 20 hours not losing power on port 2 also on port 4, second switch some up time but lost power on port 2 before 5 days, 3 days after update.
For now I satisfied with result before never have up time 8 days on port 2 also some time have problem also on port 4.

Glad to see that effort is being put on solving this issue. What I can tell, playing with PoE priority and Power-Out (forced on, auto) settings doesn't change anything, Port 2 keeps randomly crashing and in order to get AP accessible via ethernet again, you have to do a power-cycle through RB260GSP web interface. Since the problem started happening in production environment, I kept logging in and manually power-cycling until I placed ordinary gigabit PoE on Port2. No problems for a couple of months now. So it's definitely something with Port2 only.

I have a RB260GSP and it doesn't even show the power levels! I can see the data coming from the SwOS web server:My issue is with port 4 (see pic) - running firmware 1.13 at the moment.
Browser is Chromium Version 35.0.1916.114 (270117) - no Javascript errors in console.

problem is not ether2 (poe out port 1) exclusive it can be either of ports or all of them, i would suggest you to get your hands on 1.14beta2 (write to support)

janisk, could you please post changelog of 1.14?

no.

but it only contains power-out section fixes/changes if compared to 1.13

Coud you please make statistics counters 64-bit? On a fully loaded 1Gbps port it takes ~ 34 seconds for a 32-bit counter to reset. That's no good. Configurable MDP VLAN would also be nice feature to have. Now SwOS sends broadcasts only to VLAN 1.

P.S. PoE on 1.13 works fine to me. I use 260GSP to power 260GS and 951G

Is the power problem solved? I was planing to use the RB260GSP on 4 new locations to power all the on the roof equipment. But now i'm scared.

jaykay2342

The problem is not fixed yet.

The major RB260GSP PoE out problems have been fixed in SwOS v1.14: http://www.mikrotik.com/download
After upgrade it is recommended to do recalibration with "calibr" option in PoE out settings. Calibration process will ask to disconnect device from the port and return in auto mode when process is done. If this fix does not work for you, report to MikroTik support.

I have been running revision 1.14rc2 for over 2 weeks now and it is still reading low current and dropping out on some ports even when running in the "On" mode. I just upgraded to 1.14 from the download page on three different switches. I changed to Calibration mode, unplugged the devices for about 30 seconds, plugged them back in and changed to the Auto mode and some ports read "current too low" and then started power cycling again. I changed to the On mode and they powered up, but they are indicating 7mA or 33mA or 27mA when I know they draw over 100mA.

The problem is not fixed on the six switches that I am running.

I really like RouterOS and I have been very satisfied with the 30 wireless access points we have been using for the past 8 years, but these POE switches are not reliable at this time.

Edit: Has anyone else had success with rev.1.14 ? Am I doing something wrong? What is the exact calibration procedure?

Should I expect to be able to use an RB260GSP with a VoIP phone?
Or does it really only power Mikrotik wireless gear?

This setup does not work for me:
- Supplied power adapter (24V/2.5A)
- RB260GSP, SwOS 1.14
- SNOM 300 VoIP handset

The port LED on the stop of the switch cycles red slowly on and off.
The port shows 8mA current, 0.164W power when the red LED is on.

However, the phone does not start up.
Any ideas or am I just wrongly expecting that this should work?

The major RB260GSP PoE out problems have been fixed in SwOS v1.14: http://www.mikrotik.com/download
After upgrade it is recommended to do recalibration with "calibr" option in PoE out settings. Calibration process will ask to disconnect device from the port and return in auto mode when process is done. If this fix does not work for you, report to MikroTik support.

I've upgraded, but not been on site to unplug the cable to the radio.
The PoE to the radio still stops.
I'll report back, when I've been on site.

Can the ppl who had problems with POE report whether 1.14 fixed the Problem? I'm still unsure whether we should deploy a RB260GSP for our next locations.

I have two switch after update to 1.14 one lost power on port 2 after 5 days up time I see device on port 2 restart, now that device have 5 days up time after losing power.
Other switch now have 10 days and 19 hours up time and all devices connected on it have some up time.

For now I am satisfied with 1.14 but monitoring both device it is big improvement compare to 1.13 in 1.13 losing power on port 2 every 2-3 days and on one switch some time also on port 4.

jaykay2342

I have 6 switches in operation. Version 1.14 does seem to be more stable, but I am still experiencing drop outs. I have ordered some Cisco small business switches that have a secure connection and I will go back to PoE injectors.

jaykay2342

I have 6 switches in operation. Version 1.14 does seem to be more stable, but I am still experiencing drop outs. I have ordered some Cisco small business switches that have a secure connection and I will go back to PoE injectors.

Sound like i need also to use PoE injectors than. RB260GSP could be a perfect power(-cycling) solution for all the equipment which is on the roof of a location. like SEXTANTs, SXTs, etc. while having a fiber link to the inner building infrastructure.

I only have problem with PoE on port 2 after update is much more stable. If you don't need all ports for PoE try use other ports.
On other switch also lost power after almost 11 days on port 2 just checked.

Can the ppl who had problems with POE report whether 1.14 fixed the Problem? I'm still unsure whether we should deploy a RB260GSP for our next locations.

Hey,

I've updated the switch and recalibrate the ports, but...
I've connected the 912-radio on port 3, it was port 2, but when I recalibrated the ports, I moved it to port 3.

The uptime since I upgraded is 8d 20:04:39.00 with no outages, so I'm happy

I also don't have problem on other ports just on port2.
11 days is maximum up time on port 2 , on other port for now have up time 12 days and counting but before on 1.13 also don't have problem on other ports.

I never had problems on ports other than Port2. With v1.14 even port2 seems to be stable for over a week now..

@mikrotik can you please provide more details about the problem?! was this a problem with overload detection? what was the actual change in 1.14? If 1.14 should have solved this issue why do some ppl still report problems?

Hello,

----deleted,because changed state--------------

I can confirm, that port2 not operating normally.
In my case port 2 is feeding 433GL. Link is not stable - when 433 brings on, link is 1000, after
1-2 minutes the state is changing to 100(on both ends). The consumption is ~3W. And seems when 433 needs more power
260GSP do off/on cycle and 433 crashing.

Cabling issue is rejected, coz i have switched devices(All devices are 433), and device which is on port 2
crashing like other before

Waiting for 1.15

Can anyone post their experience with these power issues? Do ports have to be recalibrated once again if power loss is happening on them?

v1.14 helped a lot, I only have one to two crashes per week on about 12 switches, but it's still annoying. Crashing port seems to be random now, not only Port2. And when connected to Web GUI it shows different PoE states every time.. One time it's "waiting for load", other - "powered on" but no current and power readings, another time it's - "short circuit". Remote power cycling the port always makes it working again..

I do not lose hope that something will get figured out in v1.15. At least some setting 'to use at our own risk' that skips over-current or short circuit protection could be given. We handle plain stupid PoE's, we'll somehow manage with powered switch ports..

Crashed again. This time 'PoE status' somehow got 'disabled'.. Setting 'PoE out' to "on" made the unit energized

Some here after 17 days up time something happens on port 2.

Yeah, and current monitoring circuit is completely out of range mostly. If it's measured value is used to cause power-cut decisions, no wonder all these things happen. For example in my sshot you can see that RB912UAG is drawing more than 500mA which is just impossible for that plain board. RB260GSP shows 25.5V input voltage, while in reality (measured with voltmeter) it's 27,1V, so it's probably not the low voltage that causes such high current reading. I'd give anything to somehow bypass all this software controlled nonsense happening on GSP's. The switch works fine, power part needs serious refinement.

I have the feeling that there is something wrong with the current-calculation and therefore the switch turns of port to prevent overload. I hope Mikrotik will investigate this issue a bit deeper. This switch can be a awesome device but only if it's stable.

Am I the only one having issues here? Why it's so silent on this topic?

Today I had another unpleasant crash which caused me to physically get to the site to do local power-cycle (I haven't done that for ages).. I think it's about time to start burying MT warranties and physically solder bypasses on ports giving up remote power control for ports.. Thus eliminating the very purpose of the GSP itself.. At least it'll be a little more compact than GS with PoE's hanging..

Why you so nervous?
Don't you know about Mtik point of view to customers?
eg. I just replaced 260GSP's with poe injectors and non poe switch, and now no issues

I wouldn't say I'm nervous. I'm just curious why no one else is talking about it. That made me think maybe this issue affects only me and I'm doing something wrong. The very idea of this forum is to introduce a problem and try to achieve collective solution, out of which all would benefit.

I have problem only on port 2, plugin device not that important and monitoring that device with ping with email if power is down switch to off and again to on and working.
I have send couple screen shoot to support also replace device on port 2 and waiting solution from support.
With 1.14 is working much much better but port 2 is problem.

For now have only two 206GSP both suffering port 2 POE problem all other POE switches is 750UP not problem at all.

I can confirm that 9 times out of 10 - Port2 is the crashing port, but it happens on other ports also (the crashes are not very often, but on many switches it does add quite a number). Recalibrating PoE (with v1.14) did help, it doesn't crash as often as before, but it still happens (again, on large number of switches the problem gets kinda noticeable). Repeatedly recalibrating PoE doesn't change anything at all, ports still randomly crash. Rearranging PoE priorities have no effect too.

I avoid Port2 where I can, and in some places I use daisy-chained GSP's with Port2 unused or used with regular PoEs. In fact we don't really critically need power-cycling capability (or even more - current/voltage monitoring capability), since RB711's and 912's have proved to be very stable. GSP's having integrated PoEs just makes the installation more convenient and compact, plus for the price difference from GS you get 24V/2.5A PSU which is kinda handy for use elsewhere. This is the main reason to use GSPs over GSs for us.

If MT doesn't show up with SwOS update promising some changes in this part soon, I think we'll start rotating switches replacing them with hardwired power to ports. It'll be more work, but at least it works rock-solid.

My 4 devices show also strange behaviour. So at the moment I stay with the RB750UP.

Even the missing RSTP is a step back,...

We have installed a total of 3 RB260GS switches, and 2 out of 3 have failed within a month or two of initial installation. In both cases, it appeared to be some kind of internal power problem; no lights of any kind, but the ethernet ports appear to be sending carrier to connected equipment. We are now carrying two spares because it appears we may be re-visiting these frequently.

As this thread feared me to use the RB260GSP in the field. i took the device i bought a while ago and and use it at my own location. It's powering a old groove and a recently mounted sextant. It's running for 20 day. so far it's working.

Hi,
Just came home to see my RBMetal2SHPn going blip blip blip in the back room.

It and a Bullet-M2HP are plugged into a RB260GPS (So only two devices).
Both were idling in AP mode with no connections for some days).

The RB260GSP was reporting low current (4mA) on both ports 1 & 2. and then cycling the power.

I tried a software reset twice with no success.

So I Googled the problem and found this thread.

I have flashed the unit with the latest firmware 1.14 and after it self rebooted the devices have come back online again.

Running at about 1.10-1.45mA current for each device.

I just thought I should add my report to this issue.

We have 3x RB260GSP 's here (two in service and one spare) they are brand new units operating now for maybe a month or so.

I'll let you know if it fails again after this firmware update.

.-.-.

OK Just came home today to the exact same problem again.

So the issue has *not* been resolved with the latest firmware I'm sad to say.

Both devices on ports 2 & 3 were not functioning.

The RB260GSP would report that port 2 was connected and supplying about 100-140mA.
Port 3 would say connect for a few seconds no mA reported then say too low and cycle around again.

The RB260GSP web interface would also say connection lost every few seconds and not display the web page. (something new!)

I issued a soft reboot from the web interface and it all came up again OK.

So the problem is still there.

I can not deploy these at any of our remote sites as we would have no way to reboot them when they fail.

They are not fit for the purpose sold.
.-.-.

Watching this thread as I'm about to purchase one of these switches.

I recently exchanged an old RB450 on a site witha RB260GSP (the RB450 was running as a simple managed switch).
The RB450 was old and was crashing (had some stewed capacitors).

I have the RB260GSP connected directly to a 12v batery of 45Ah, and an intelligent battery charger. The RB260GSP reports like ~13v, and I use port2, port3 and port4 with PoE. The RB260GSP never reboots, but all 3 devices reboots frequently, and all at the same time. I have a Bullet 5, a SXT 5 lite and a Rocket M5 and they all reboot at the same time and frequently.

I have already updated to SwOS 1.14 a weak ago and it didn't help.

OK I've just checked the device again and now find something even more disturbing.

A few days ago we were requested to power off one of our high powered 5.8Ghz devices connected to a high gain antenna so people could work safely in the area directly in front of it.

Today I check the device and although it lists the device power as being set to OFF it is applying power to the device and it is functioning!.

So workers have been exposed to microwave radiation.

This has now become a major health and safety issue exposing us to possible prosecution.

We will be pulling all of these devices from our services.
.-.-.

Don't you know what is the safety switch used on machines under repair?

OK I've just checked the device again and now find something even more disturbing.

A few days ago we were requested to power off one of our high powered 5.8Ghz devices connected to a high gain antenna so people could work safely in the area directly in front of it.

Today I check the device and although it lists the device power as being set to OFF it is applying power to the device and it is functioning!.

So workers have been exposed to microwave radiation.

This has now become a major health and safety issue exposing us to possible prosecution.

We will be pulling all of these devices from our services.
.-.-.

i don't know how it is in your country, but here you can't have a setup with a legal EIRP which is a risk for the health. or are your technicians some kind of wavies?

They could also sue the sun, because it irradiates them with 1 kW/square meter. Which is maybe 1000 times more then that AP exposing them to maybe 1W/sq.m at lower, less energetic wavelengths.
This is an technical issue, but to escalate this to a health hazard is a little far fetched. A microwave oven has more escaping RF power than this. And I assume they don't use mobile phones either - having a up to 1 W transmitter near your head...

Don't you know what is the safety switch used on machines under repair?

Yes! POE Out >> **OFF** is OFF!!! Yes? Well not with this devices. Very dangerous!

Why have if not to be used???
.-.-.

OK So again today. Another device does the same thing POE is set to Off but port one is powered!

So set both 1 & 2 to Auto and apply. Then port 2 says Low Current bug again!.

Finally both back on after soft reset.

This device has big problems even with current firmware!
.-.-.

They could also sue the sun, because it irradiates them with 1 kW/square meter. Which is maybe 1000 times more then that AP exposing them to maybe 1W/sq.m at lower, less energetic wavelengths.
This is an technical issue, but to escalate this to a health hazard is a little far fetched. A microwave oven has more escaping RF power than this. And I assume they don't use mobile phones either - having a up to 1 W transmitter near your head...

Regardless of your thoughts EMR rules in our country are not to be laughed at unless you like being poor from legal actions!

61dBm focused on human life @ less then a meter's distance @ 5.8Ghz not welcome by the authorities! (31dBm rf + Grid @ 30dBi).

Tell them your thoughts. Not me. I have no interest in breaking laws. !!
.-.-.

Sure the device doesn't work as it should. No doubt. On the other side you cannot use such features as safety features. Never. If you mean honestly what you wrote than you have already implemented real safety tools that definitely block radiation from antennas by visible manner. For example metal deck over the active part of antenna.... You should learn safety principles and implement them into your work instead yelling here.

Sure the device doesn't work as it should. No doubt. On the other side you cannot use such features as safety features. Never. If you mean honestly what you wrote than you have already implemented real safety tools that definitely block radiation from antennas by visible manner. For example metal deck over the active part of antenna.... You should learn safety principles and implement them into your work instead yelling here.

Who is yelling? You maybe. Not I!

I am simply pointing out the facts.

- The device does not work as designed.
- The latest firmware (1.14) does not solve this issue.
- The issue of the power coming back on at some random point after it has been turned off creates a safety issue.

Whether or not you consider the use of the POE Off feature to be adequate in isolating the function of a microwave device or not is immaterial. The device does not work as designed.

We are now forced to replace all these devices with Ubiquiti Tough switches at around double the cost until the RB260GSP 's can be proven safe.

Anyhow I see no benefit in debating the mater further with you. This thread is more about reporting the problem and or success of any further possible firmware or hardware updates.
.-.-.

Hey guys please keep calm.

i still have not faced any problems with the one switch i run for testing. I might be just lucky with it. But it seems ppl here have still problems. I would like to hear something from Mikrotik and what they think about these problems which obviously still existing. @Mikrotik, it's your turn now.

Ok. I admitted in the beginning that the device doesn't work as designed. But it is not designed to be safety switch for the cases you referred to anyway.

Ok. I admitted in the beginning that the device doesn't work as designed. But it is not designed to be safety switch for the cases you referred to anyway.

I agree on it and if people use a software based "switch" safety it's a practices but let us keep that topic out of this thread.

Well our last unit that we have left set up for testing and upgrades in the hope the problem will be solved so we can re-implement the model back into our networks has failed again today.

Once again a software reset brings the devices online again. Of course sooner or later it will fail again.

I have a suspicion: As usual a battery/solar setup has some voltage fluctuation this might confuses the overload detection and it turns of a port ? do you guys use the device powered by batteries ?

wel, my rma replaced rb260gsp with fw 1.14 works "almost flawless" from a first day, powering main rb951g-2HnD for 24/7.
What I found is that when I try to use 12V power supply, it causes PoE power failures and especially on port 2,
but using original 24V adapter, or even 19V another, it works for 2nd month now without a single outage.
I went through "Callibrate" on port 2 as it dropped PoE even at 19V once, and it seem to be solved since then,
but I agree that the usable working voltage is far from free fluctuating 8-30V as printed on a box.
PoE part _is_ voltage sensitive, without doubt.

But on the other side, now there are 3 devices, rb2011 and another rb951g, and no outage repeated..
Well but.. I still think the PoE part is not what I would put massively into production anyway - but it can be easily avoided by Microtik gigabit PoE injector, when no software control is necessary. Anyway, You have no scheduller there in swOS to turn power on and off by event or at specific time..

What I appreciate much more, is that SFP/optical link between rb260gs and rb260gsp, had zero issues and this is what I consider really great.
As for toppic, I think rb260gs (without "P") is ready..

connected a M900 to port 2 and all was going great until I changed the ip address of the rb. the m900 dropped from network. rb show power on, ping was dead for 15sec and then connected and cycled that without any changes. reboots and power cycles did not help. Had to replace the m900 and rb. m900 required reset. rb looks and feels fine but? I did notice that when I set port 2 off that the power continued to flow? running 1.14

I've seen the "reset" bug on other radio's and never really figured out why. Just had to deal with replacing it when it happened. Maybe 1 out of 100's? Seems to follow power outages and/or reboots.

but, it works if handled with care and you follow good troubleshooting.

Dear MK team. Latest SWOS is 1year old !. 1.14 is from 2014-Mar-26

Please add name ports and other wishes here from forum.
Thanks

Dear MK team. Latest SWOS is 1year old !. 1.14 is from 2014-Mar-26

Happy Birthday!

Please add name ports and other wishes here from forum.

• → Named ports (or a comment field)
  → DHCP client
  → Power-cycle a port as an atomic operation; the switch may be powering the router that connects it to the rest of your network!

I dont think anyone cares anymore about RB260GSP not working.

I still have my test RB260GSP. It's running without any problems. But i only power 2 devices with it.

are you all powering the switch with the 2.5 amp 24v power supply directly?

or using a poe injector on port 1??

I also see problems with my RB260GSP, powered by factory adapter. SWOS 1.17

I don't believe I have issues on the PoE side (three wireless AP)
but I do see 14-18 ms ping and 1-5% dropped packets and time from PC directly connected to the RB260GSP.
I get a consistent 0% dropped, 0-1 ms ping time from my CRS226 connected passing through the RB260GSP.

I also see problems with my RB260GSP, powered by factory adapter. SWOS 1.17

I don't believe I have issues on the PoE side (three wireless AP)
but I do see 14-18 ms ping and 1-5% dropped packets and time from PC directly connected to the RB260GSP.
I get a consistent 0% dropped, 0-1 ms ping time from my CRS226 connected passing through the RB260GSP.

thats normal, the chip which runs webconfigurator (and replies to ICMP) is slow. The actual switching is normal.

I'm also facing issues, just like others here, with the RB260GSP.
I cannot log in to them. I've reset them and cleared my browser cache.
When I navigate to the login page, it just says "Loading..." nothing else. Wish we could know how soon this will be resolved.
See attached image.

rb260gsp_login_blank.PNG

Do u have another RB260GSP to try? Different browser/computer? Did it just happen or its a new switch and never worked?