I just bought a lightly used CCR1016 and fired it up. Being a SFP slot only model, there is no copper port. Luckily there is a serial console port that I could use to login using Cisco rollover cable and a DB9 to RJ45 coupler (from an old HP procurve switch I had) and using 115200 8N1, I could login to initialize the router.
I added Cisco GLC-T (about 2 years old) and they get detected with no-link. So I plugged in the cable to my laptop and I was hoping link to go up, but it did not. Then I read and accordingly set the port to speed=1G full-duplex=yes auto-negotiation=no and this caused LED to show up on the port, and link shows up, but I could not ping the default IP from a laptop directly attached with a static IP in the same subnet. And NIC on the laptop did not come up.
I unplugged the cable and to my surprise, the LED stay lit on the port.
command interface ethernet monitor sfp1 shows all okay.
I also tried with a Cisco small business Copper SFP and that too gets detected and have exact same issues.
In fact, even if I take the SFP out, the port LED remains lit with auto-neg set to off.
I have latest 6.47.3 installed by seller, so that implies it must have been working and accessible thru SFP ports, but I somehow cannot make any SFP port work to be able to downgrade or change to any other code to see if that resolves the issues. Does not make sense to have a SFP cage only router or switch for issues exactly like mine.
Can someone please suggest how to make the SFPs work in this router?
I also have a CCR1009 model.
I can get the SFP port to talk to other smart devices, specifically to SFP port on 260GS for example and other vendor SFP ports.
HOWEVER, no matter what I do I cannot connect my SFP + port to my TWO ISPs, one is straight normal ethernet cable, and the other is bell fibre via a VLAN.
The SFP port I didnt try that as well to my ISP, and if I get a chance in the next week I will and report back.
I did supply a ticket about my SFP+ port using the MT cage by the way (SJ10+) and I sent them supouts. They wanted me to try different etherports as well and they all work fine.
Havent heard anything from them in weeks and have given up on support on this issue.
The issue is somewhat resolved for me. Here is what I had to do:
After the changes and reboot (with SFPs in) using system reboot command issued from serial console, it did not work. Then I took out the SFPs and did a hard reboot by unplugging the power and then added the SFPs back in and now both LAN and WAN side is working.
I then did a reboot again with SFPs in and on logging back in, I could see that on the LAN side, the same model SFP works fine as I can then ping from a test laptop attached to it (I had to set the laptop NIC speed to 1Gig and duplexity to full) but I could not ping the upstream router thru the WAN port. I unplug the SFP and plug it back in and then it starts working. Repeated it twice. Switched the SFPs around and sfp1 / LAN side always works with SFP remaining in, on reboot, but sfp12 / wan side does not.
Just make sure to have fairly recent Cisco GLC-T models or others that you test by rebooting the router, as I also tried with bit older that work in Cisco and TP-link switches I have and they did not work in CCR. They do get recognized, but you will find that they never bring link up at other end (though router end will show link-up). Also small business Cisco MGBT1 did not work at all (though they get recognized). At this time, I don’t have any other copper SFPs to test with, so will buy some and retest.
Hi anav, sorry saw your post after I posted my solution. I believe if you will use SFP port, not SFP+ and use generally available Cisco GLC-T newer revisions (4 or better), then it should work for you to interface with ISP with copper handoff. The only issue you may run into is that ISP will not do a speed duplexity change for you, but good thing with gig is that it is never half-duplex (though some equipment has option to set it, not sure why) and I have tested it with ISPs who insist (for commercial service) to have customer firewall be set to 100 or 1000 full duplex depending upon service and I have tested with Cisco ASA and fortigate and with both, if I leave my port to auto, with ISp side 1000-full, my end negotiates to 1000-full as it does not have option to set to 1000-half. I believe auto part in 1000 is for speed negotiation and not duplexity negotiation.
I apologize. The model I had was 1016 and not 1009. I have edited the label on the post accordingly.
I purchased another two copper SFPs (Phantom SFP) and they work in Cisco switch fine without any config change in Cisco. However, they did not work in 1016.
Then I found that I have two Cisco GLC-T rev 4. One is labeled as Made in US and has all metallic pull out handle and that works great on reboots after auto-neg is set to off. The second GLC-T of same rev4 looks little different and is Made in MY and has a yellow plastic sleeve on the a thin wire pull out handle. That one requires interface disable and enable on the reboots.
So anyone looking for copper SFPs that work, please try the rev 4 (30-1410-04) Made in US if you can find them on eBay or some other.
Can someone confirm that Mikrotik Copper SFPs will work 100% on the CCRs?
I tried that already and copper / RJ45 1G SFPs don’t work. Only one that works is what I listed with even reboots. The other one does not work unless I do manually port disabled / enabled after router reboots.
Here is the script that I added to fix this issue. I have only port sfp1, but any other ports can be added by comma separating.
Just to add that with ports set to autoneg off and this boot time script bouncing the ports, all Cisco Copper SFPs that I could find in lab switches (version 2 thru 4) work now. Cisco small business copper SFPs ( from SG300 and SG500 switches) don’t work. Many of you may have copper SFPs form old Cisco gear that you may want to reuse for some of these fiber ports, so that seems to be possibility now. I will strongly recommend for anyone who needs to buy new ones, good idea is to go for Mikrotik branded. For lab or home use, sure any old Cisco or even from eBay should work.
try like that