Only if you ordered the SAF with a fiber port... I'm not sure if there's any way they can be added if you got it with copper only. I made that mistake on ours... but it was a long time ago, when I didn't know any better (it also doesn't even cause any issue, so I don't really care, but still... ).
On Mon, Apr 24, 2017 at 9:50 AM, Josh Luthman <[email protected]> wrote: > Should have a "fiber port" with their badass connector on it. Or an SFP. > > > Josh Luthman > Office: 937-552-2340 <(937)%20552-2340> > Direct: 937-552-2343 <(937)%20552-2343> > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > On Mon, Apr 24, 2017 at 1:05 AM, Steve Jones <[email protected]> > wrote: > >> do i drill a hole in the saf and push the fiber in the hole and the radio >> mites will just make it work? :-) >> [image: Inline image 1] >> >> >> On Sun, Apr 23, 2017 at 11:57 PM, Josh Luthman < >> [email protected]> wrote: >> >>> Best solution would be to do fiber IMO. SFP right into the RB. >>> >>> >>> Josh Luthman >>> Office: 937-552-2340 <(937)%20552-2340> >>> Direct: 937-552-2343 <(937)%20552-2343> >>> 1100 Wayne St >>> Suite 1337 >>> Troy, OH 45373 >>> >>> On Mon, Apr 24, 2017 at 12:32 AM, Steve Jones <[email protected] >>> > wrote: >>> >>>> thanks man >>>> >>>> i would lock it down but i dont know whats causing it, im fearful it >>>> would just dump the link all together, which is fine if im on the network, >>>> but if im off network (as i found out the hard way tonite) my remote access >>>> to the shop drops and all the site routers ACLs limit access to the office >>>> IP. I had to VPN into a contact services customer who is on our network and >>>> then connect to our office so i could flip the port back on, this, btw is >>>> also why i hate having to have static routes on our OSPF network, >>>> >>>> On Sun, Apr 23, 2017 at 11:08 PM, Adam Moffett <[email protected]> >>>> wrote: >>>> >>>>> I'm 100% sure a script could do that. >>>>> >>>>> :global interfacestats >>>>> :global int "ether2" >>>>> :set interfacestats value=[/interface ethernet monitor [find >>>>> name=$int] as-value] >>>>> :if (($interfacestats->"rate")!="1000Mbps") do={/interface ethernet >>>>> disable [find name=$int]; :delay 3; /interface ethernet enable [find >>>>> name=$int]} >>>>> >>>>> That took me a strangely long time to figure out how to do because >>>>> Mikrotik scripts are friggin weird. But there it is. You could schedule >>>>> that every xx minutes if you wanted. >>>>> :delay 3; might not be necessary. I'm not sure. >>>>> >>>>> On the other hand, what if you just disallow all auto-negotiation >>>>> options except for 1000/F ? >>>>> >>>>> >>>>> ------ Original Message ------ >>>>> From: "Steve Jones" <[email protected]> >>>>> To: "[email protected]" <[email protected]> >>>>> Sent: 4/23/2017 10:59:17 PM >>>>> Subject: [AFMUG] mikrotik port monitor script >>>>> >>>>> we have a saf 11ghz primary link interconnecting our two upstream >>>>> locations, about once every 6 or 7 months the mikrotik renegotiates to >>>>> 100mbps. disable/enable the port fixes it. >>>>> >>>>> Ive never been able to reproduce it because it only happens once or >>>>> twice a year. >>>>> >>>>> Is there a script i can run on the mikrotik that monitors that >>>>> specific port and flaps it if it is ever not running 1gbps? >>>>> >>>>> >>>> >>> >> >
