6.13/3.14 on an RB2011iL. Yeah, likely the customers media converters are not Gig capable, they are pretty old, it was disconcerting not to be able to talk at 100M or even 10M though. I’m more worried that it doesn’t seem to talk to a CTM-2 on a GigE port. And who knows what else.
From: Nate Burke via Af Sent: Friday, October 17, 2014 9:32 AM To: [email protected] Subject: Re: [AFMUG] some devices won't talk to RB2011 GigE ports? What ROS/Routerboard version? Does the customers Media converter auto-negotiate, or does it only work at 1 speed? It's been a while since I've used them, but the 1G converters I had were only 1000base on the Ethernet port, no auto. On 10/17/2014 9:29 AM, Ken Hohhof via Af wrote: Yes, in this case the MT interface reported successfully negotiating 100 Full, but never counted any rcv packets. From: Adam Moffett via Af Sent: Friday, October 17, 2014 9:23 AM To: [email protected] Subject: Re: [AFMUG] some devices won't talk to RB2011 GigE ports? Well....autonegotiation failures happen sometimes, but typically those work ok when you force the speed on the link. In the case I'm thinking of, we could not get a working link no matter what. It was quite awhile ago now, but I think it would report a link was up while the input counters never climbed above 0. We have a couple devices that don't work with Mikrotik devices at all. Putting a switch in between fixes it but not ideal. On Fri, Oct 17, 2014 at 10:14 AM, Adam Moffett via Af <[email protected]> wrote: Yes...maybe. We had somebody not able to get link with an RB2011. I don't think we ever tried the 10/100 ports. The customer ended up getting a different router. Is there an issue with the GigE ports on Mikrotik RB2011 not talking to some devices no matter what settings you try? I had this with a customer's copper/fiber media converter, moved it to a 10/100 port on the 2011 and all was good. Now I think I'm seeing the same thing with a CTM. Setting the GigE port to only negotiate 100M didn't work, no amount of playing with the settings worked, had to physically move it to a 10/100 port. If this is a known problem and not my imagination, what other Mikrotik devices share this issue? If this had been an 1100 or CCR or CSR, I might not have had a 10/100 port available and I would have been stuck.
