Rx fcs error mikrotik что это

Rx fcs error mikrotik что это

Sun Oct 04, 2015 4:12 pm

Yesterday replaced a rb1100AH running v.6.30.2 to a brand new CCR1009-8G-1S-1S+ router.

Looked in the log today and found it filled with fcs errors?

All ethernet cables are almost new and connect to new routers and on the rb1100AH showed no errors and were Gigabit connected (auto negotiation on)

Now these failures?
I installed the CCR with 6.32.2 but reverted back to 6.30.2 as the most stable version but the problem didn’t disappear.

1. It can’t be the cables, they were all fine on the rb1100AH and basically all new.
2. It can’t be the software? 6.32.2 or 6.30.4 makes no difference. And most of my other routers now work fine with either one of these two versions.

I ran 2 ping tests with 100ms timeout to adjacent router and that is fine. 1st is 100ms and 50 bytes packet size, 2nd is 100ms but 1500 packet size. On the latter I see an occasional time out and I see 1% package loss.
The stats of the interface is also showing the error. 2100 errors in 25 mins uptime.

Do I have a failing CCR? Where is this error coming from?

Show your appreciation of this post by giving me Karma! Thanks.

WISP operator based on MT routerboard & ROS.

Re: fcs error on new CCR1009

Tue Oct 06, 2015 11:19 am

Show your appreciation of this post by giving me Karma! Thanks.

WISP operator based on MT routerboard & ROS.

Re: fcs error on new CCR1009

Tue Oct 06, 2015 7:37 pm

Three things cause FCS errors typically, with the first two being the most likely.

1) Physical cabling issues

2) Speed / duplex mismatch or errors

Steps to resolve.

1) Change the cable with a known good one on the link you are getting FCS and reset counters.

2) Hard code speed and duplex to match on both sides of the link.

Re: fcs error on new CCR1009

Tue Oct 06, 2015 7:50 pm

be sure you have updated the firmware (not routeros)

put a manageable switch as a bypass on that link to see if switch receives the same errors

Re: fcs error on new CCR1009

Tue Oct 06, 2015 8:14 pm

Three things cause FCS errors typically, with the first two being the most likely.

1) Physical cabling issues

2) Speed / duplex mismatch or errors

Steps to resolve.

1) Change the cable with a known good one on the link you are getting FCS and reset counters.

2) Hard code speed and duplex to match on both sides of the link.

Show your appreciation of this post by giving me Karma! Thanks.

WISP operator based on MT routerboard & ROS.

Re: fcs error on new CCR1009

Wed Oct 07, 2015 5:35 pm

Really sounds like you may have a bad board out of the box. few comments below

1) If you can swap the 1100 back in and the FCS goes away, then i would agree cabling is prob not it

2) This is true only on copper (and you can set 100M Full on each side just for testing) SFP ports can be hard coded to 1000/Full as well.

3) In our lab we have a CCR1009 connected to MikroTik, Cisco and HP network equipment on copper and fiber without issue. unfortunately you probably got a bad CCR.

There was a batch of bad CCR1009s early on and it’s possible you got one that’s been on the shelf for a while as all the new CCR1009s shipping seem to be pretty solid.

Re: fcs error on new CCR1009

Wed Oct 07, 2015 6:49 pm

Re: fcs error on new CCR1009

Thu Oct 08, 2015 11:53 am

Nailed the issue for 95%:

All links / ethernet cables leave from CCR1009 over some 15 meter of ftp cable (all well grounded on both ends. ) to a tower cabinet.
In the cabinet a 24V PoE battery fed midspan power inserter with lighting/surge protector is fit. From here some 8-10 meter of ftp (all well grounded on both ends. ) run up the tower to connect to the radios. Mostly Netmetals.

The midspan PoE injector is from Cyberteam, Poland. This is a managed Gigabit version. This is actually the 3rd box that give me problems. One just died, the second had no more webserver working and became useless because of that en this last one after 2 months again fell without web server control. So my suspicion went to this device. Last night I replaced it to a brand new unmanaged gigabit net-protector and almost all fcs error disappeared from the logs.
So this is the 3rd managed netprotector heading for the bin (with 2 unmanaged going the same before. poor quality stuff. )

I still suspect the last remaining errors, now only on one link, are due to this new netprotector. But to be honest there are not a lot 24V multiple port passive PoE midspan injectors in gigabit version with IP management on the market. The nearest solution I can find are Netonix WISP switch but I need to convert it into 1:1 port to port switch only since the several routes have different dhcp-servers and hence these ‘pipe’s need to stay separated.

To reply to some of your comments;

3) In our lab we have a CCR1009 connected to MikroTik, Cisco and HP network equipment on copper and fiber without issue. unfortunately you probably got a bad CCR.

There was a batch of bad CCR1009s early on and it’s possible you got one that’s been on the shelf for a while as all the new CCR1009s shipping seem to be pretty solid.

Show your appreciation of this post by giving me Karma! Thanks.

WISP operator based on MT routerboard & ROS.

Re: fcs error on new CCR1009

Thu Oct 08, 2015 11:56 am

Show your appreciation of this post by giving me Karma! Thanks.

WISP operator based on MT routerboard & ROS.

Re: fcs error on new CCR1009

Thu Oct 08, 2015 3:31 pm

Last night at around 1 am we replaced the gigabit netprotector (Poe midspan injector) for another more simple one (Also giga, also Cyberteam, but no remote access, no control whatsoever) brand new out of the box.
Immediately after the change the fcs errors didn’t come back. Well, instead of every 30 seconds until this morning 10 am when I logged in again the log only showed 4 fcs errors in total since the change. good!
. You would think. =>

While looking over a remote winbox session in this CCR1009’s log this morning I saw the errors coming back! First every 10 mins, then every 5 mins, every 3-4 mins and now they are back to every 2 mins.
How is this possible? Overnight the problem vanished just to come back in the morning. Very, very weird.

I don’t know what to do now. Cannot go to 100mbps setting on each end since this is my main backhaul that at times has more traffic than 100mbps. Fast Ethernet will create a bottleneck again. (I spend a lot of time and money and energy into reforming a previously duo bonded link with double antenna sets etc. high in towers into a ‘ac’ single 40Mhz wide link to get up to 300Mbps over this new link. (tested up to 280M!)

I also cannot fit in the gigabit power inserters from Mikrotik. Because the poe insert is in the middle of a cable. Both ends need to be at least 10 meters.
I don’t seem to be able to find any passive poe midspan inserters that work on 24V battery power and have gigabit port and are remotely controllable.

So, main question; Until I find any solution, how bad is it these errors are there? They fill the log, but do they have any other harm? I don’t seem to notice problems (yet?). Ping on long and short package see no losses and ping times are good and traffic flows.
But out of the 12 NetMetals installed over the last weeks, all running with latest ROS and firmware in bridge mode (fastpath enabled) I have 3 of them that just stop passing traffic once a 2 or 3 weeks. only a power reboot brings these back in working order again. Can this have anything to do with some fcs error too? (Since the Netmetals don’t show these errors in the logs I never looked for them. )

Show your appreciation of this post by giving me Karma! Thanks.

WISP operator based on MT routerboard & ROS.

Источник

Fcs error on link mikrotik

Столкнулся с проблемой на MikroTik – ошибки в логах и отсутствие интернета на порту Ether1. Стал искать ответ в интернете, но решения не нашел. Существует предположение, что проблема появления ошибки interface,warning ether1 fcs error on link связана с наводками от кабелей 220v.

К сожалению, проблема не имеет стойкого графика появления. Цикл между ошибками разный, может быть неделя, а может быть и пару месяцев. Помогает либо полная перезагрузка MikroTik или отключение порта. До текущего момента мы делали это вручную, после был найден скрипт. К сожалению автора скрипта, найти не удалось. Но раз ошибка популярная, то думаю не лишним будет его указать, как решение проблемы.

На микротике RB951G-2HnD установлена последняя RouterOS 6.19.
Провайдер (Ростелеком) подключен в первый порт роутера, скорость соединения в микротике определяется, как 100 full duplex.

При поднятии PPPoE соединения с провайдером теряется около 40% пакетов через это соединение. Пробовал ping 8.8.8.8 и ping ya.ru и просто открывал сайты через http.

Важно, что при использовании старого оборудования (сервер на Intel Atom) таких потерь не обнаруживается. Пробовал подключать ноутбук с Ubuntu напрямую тоже все работает без проблем.

Что делал:
Менял MTU PPPoE соединения и flow control Ethernet port1.
Менял роутер для исключения не работоспособности железа.
Менял физический порт роутера на 5й эффект сохранялся.
На форуме микротика нашел схожую проблему, которая якобы исправлена в версии 6.11 RouterOS.

Также как и предложено на форуме микротика включил между микротиком и провайдером Dlink-DGS 1005d и потери пакетов исчезли.

Как исправить проблему с потерей пакетов? Хочу подключать напрямую, а не через доп. оборудование.

суббота, 27 декабря 2014 г.

Значения счетчиков ошибок

Не всегда понятно что может означать та или иная ошибка при передаче. Ниже моя попытка объяснить значение счетчиков ошибок, которые регистрирует коммутатор.

Счетчики ошибок при получении кадров (RX):

CRC Error

Counts otherwise valid packets that did not end on a byte (octet) boundary.

Счетчик ошибок контрольной суммы (CRC). В свою очередь, является суммой счетчиков Alignment Errors и FCS Errors.
FCS (Frame Check Sequence) Errors – ошибки в контрольной последовательности кадра. Счетчик регистрирует кадры с ошибками FCS, при этом кадры имеют корректный размер (от 64 до 1518 байт) и получены без ошибок кадрирования или коллизий.
Alignment Errors – ошибки выравнивания (некорректной длины кадра). Счетчик регистрирует кадры с ошибками FCS, при этом кадры имеют корректный размер (от 64 до 1518 байт), но были получены с ошибками кадрирования.
В случае, если кадр был классифицирован как имеющий ошибку Alignment Error, счетчик FCS при этом не увеличивается. Иными словами, инкрементируется либо счетчик FCS либо Aligment, но не оба сразу.

UnderSize

The number of packets detected that are less than the minimum permitted packets size of 64
bytes and have a good CRC. Undersize packets usually indicate collision fragments, a normal
network occurrence.

Счетчик кадров с правильной контрольной суммой и размером менее 64 байт. Такие кадры могут возникать в результате коллизий в сети.

OverSize

Counts valid packets received that were longer than 1518 octets and less than the
MAX_PKT_LEN. Internally, MAX_PKT_LEN is equal to 1536.

Счетчик кадров с правильной контрольной суммой, размер которых превышает 1518 байт, но не превышает 1536 байт – внутреннего максимального значения кадра.

Fragment

The number of packets less than 64 bytes with either bad framing or an invalid CRC. These
are normally the result of collisions.

Счетчик кадров с неправильной контрольной суммой или структурой кадра и размером менее 64 байт. Такие кадры могут возникать в результате коллизий в сети.

Jabber

Counts invalid packets received that were longer than 1518 octets and less than the
MAX_PKT_LEN. Internally, MAX_PKT_LEN is equal to 1536.

Счетчик кадров с неправильной контрольной суммой, размер которых превышает 1518 байт, но не превышает 1536 байт – внутренного максимального значения кадра.

Счетчик ошибок при отправке кадров (TX):

Excessive Deferrral

Counts the number of packets for which the first transmission attempt on a particular
interface was delayed because the medium was busy.

Счетчик кадров, первая попытка отправки которых было отложена из-за занятости среды передачи.

CRC Error

Counts otherwise valid packets that did not end on a byte (octet) boundary.

Счетчик ошибок контрольной суммы (CRC). На практике никогда не увеличивается.

Late Collision

Counts the number of times that a collision is detected later than 512 bit-times into the
transmission of a packet.

Счетчик случаев когда коллизия обнаруживалась после передачи первых 64 байт (512 бит) кадра.

Excessive Collision

Excessive Collisions. The number of packets for which transmission failed due to excessive
collisions.

Счетчик кадров, отправка которых не удалась из-за чрезмерного количества колизий.

Single Collision

Single Collision Frames. The number of successfully transmitted packets for which
transmission is inhibited by more than one collision.

Счетчик успешно отправленных кадров, передача которых вызвала более одной коллизии.

Collision

Моно добавить, что на практике RX CRC обычно является результатом деградации среды передачи (медный кабель или оптоволокно), а TX-коллизии – результатом неправильного согласования скорости соединения, например half-линка.

Неплохая расшифровка значений счетчиков приведена тут.

Источник

Rx fcs error mikrotik что это

Tue Apr 29, 2014 7:01 am

Have an AF 24 link running v2.0 firmware. Root end terminated at a CCR1016-12G on RouterOS v6.12. Remote end terminated at a RB1200 on RouterOS v6.7. Using stock PoE injectors. UBNT ToughCable all within distance spec. Grounded.

Since going to AF 24 v2.0 I’m seeing ridiculously high Rx FCS ERRORs and Rx CODE ERRORs on the interfaces of each router.

OSPF randomly drops out on the link and lately some customers have been complaining about intermittent connectivity. Not sure if this is related or not.

Anyone else having this problem?

Tue Apr 29, 2014 7:14 am

Tue Apr 29, 2014 5:23 pm

OK, slightly updated information to share.

First of all, the CCR on v6.12 is logging hundreds of «fcs error on link» events. About one per minute.

The problem started on 4/24/14 when I upgraded the CCR from v6.7 to v6.12. To be exact, it started at 11:22 exactly one minute after I upgraded the router OS and router firmware.

We did the AirFiber 24 v2.0 upgrade on 4/15/14 and ran without any of these errors on RouterOS v6.7

I am only seeing these errors logged on the interface which the AirFiber is on.

Thu May 01, 2014 6:03 pm

We are seeing the exact same thing, with the AF24/CCR
but also with some older Trango licensed gear, and the CCR.

It’s not exclusive to the AF24, is what I’m trying to say.. The CCR is the common denominator.

Thu May 01, 2014 6:40 pm

Sun May 04, 2014 6:20 am

I downgraded both AirFibers to 1.5.

I continue to see one «FCS ERROR» per minute in the log of both routers.

No, this was not a result of updating the UBNT gear. I should have made it clearer in my first post that the upgrade to v2.0 of each AirFiber occurred a few weeks before the router at the root end (the CCR) was updated from v6.7 to v6.12.

When the CCR was on v6.7 and the AirFibrs on v2.0, this issue was non-existent. It started with an upgrade to RouterOS v6.12

Mon May 05, 2014 4:02 am

Starting from ROS 6.11 there are changes related ethernet:

Also check that you are using the latest bios on your CCR.

Mon May 05, 2014 6:16 pm

I am aware of the changes to ethernet.

I am running firmware v3.13 as of the day I upgraded the CCR to v6.12

I have enabled flow control on both the AirFibers and on the CCR. Doesn’t seem to help.

Mon May 05, 2014 11:13 pm

Tue May 06, 2014 1:27 am

Fri May 16, 2014 3:56 pm

I might try upgrade to 6.13 but will have to be during the night.

Fri May 16, 2014 7:39 pm

Let me know what RouterOS v6.13 does for you. Also, if it has a new firmware upgrade in it too.

We get the FCS errors logged one a minute, both ends of the link.

CCR at root. RB1200 at remote.

Never saw these ever before until I upgraded the CCR to v6.12

Mon May 26, 2014 8:00 pm

I put a ubnt tough switch inbetween my tik and air fibre.
No more fcs errors on tik, but the tough switch reports rx errors on the port connected to the air fibre.

This is clearly an air fibre problem.
Have seen this on approx. 80% of all air fibre deployed.

Tue May 27, 2014 1:19 am

Tue May 27, 2014 9:53 pm

Interesting, but as @marcin21 points out, he has no problems with CCR on RouterOS v6.5.

My scenario is very similar to his, I was also pushing 400-450mbps and no FCS Errors while on RouterOS v6.7

My problem started after the upgrade to v6.12

I will be downgrading next Monday and will post results.

Fri Jun 27, 2014 8:27 pm

Sat Jun 28, 2014 2:36 am

RouterOS downgrade did not fix it.

I put a managed switch in between the AF 24 and the CCR. As stated by someone above, the switch begins to log errors on the port connected to the AF 24 and the issue is eliminated from the router.

I went back to UBNT support on this and am awaiting a reply.

This is basically not a Mikrotik issue or RouterOS issue as far as I’m concerned. I’m baffled as to why the upgrade to the CCR started the problem in the first place, but the truth is in the pudding once I installed that switch.

I’ll update this thread when I have more info.

Sat Jun 28, 2014 2:41 am

One Docker OS to rule them all.

Sat Jun 28, 2014 8:04 pm

Mon Jul 14, 2014 5:06 pm

Hi everybody, I’m currently having same issue here, FCS errors on RB750GL (on 6.15) port
with UBNT NS5 Loco (latest firmware and RF Armor shields) connected.
NS5 Loco is powered by PoE injector.

What I did so far without success:
— replaced cable (tough cable) connectors
— replaced cable by certified Cat.6
— replaced RB750GL (also on 6.15)

I’m about to replace NS5Loco now and see.

By reading «other RF equipment», would you count LNB from satellite dish as well?
I’ve mounted NS5Loco right on the same pole above the dish.
Could this be a possible source of the FCS errors caused by RF interference of LNB?

What do you think? Could LNB cause FCS errors?

Mon Jul 14, 2014 6:11 pm

Hi everybody, I’m currently having same issue here, FCS errors on RB750GL (on 6.15) port
with UBNT NS5 Loco (latest firmware and RF Armor shields) connected.
NS5 Loco is powered by PoE injector.

What I did so far without success:
— replaced cable (tough cable) connectors
— replaced cable by certified Cat.6
— replaced RB750GL (also on 6.15)

I’m about to replace NS5Loco now and see.

By reading «other RF equipment», would you count LNB from satellite dish as well?
I’ve mounted NS5Loco right on the same pole above the dish.
Could this be a possible source of the FCS errors caused by RF interference of LNB?

What do you think? Could LNB cause FCS errors?

Tue Jul 15, 2014 12:46 pm

Hi everybody, I’m currently having same issue here, FCS errors on RB750GL (on 6.15) port
with UBNT NS5 Loco (latest firmware and RF Armor shields) connected.
NS5 Loco is powered by PoE injector.

What I did so far without success:
— replaced cable (tough cable) connectors
— replaced cable by certified Cat.6
— replaced RB750GL (also on 6.15)

I’m about to replace NS5Loco now and see.

By reading «other RF equipment», would you count LNB from satellite dish as well?
I’ve mounted NS5Loco right on the same pole above the dish.
Could this be a possible source of the FCS errors caused by RF interference of LNB?

What do you think? Could LNB cause FCS errors?

Источник

Rx fcs error mikrotik что это

Sun Dec 29, 2019 10:32 pm

My network completely stopped. Couldn’t get anything to work. Couldn’t statically set an IP and reach the router.

Rebooted router. nope.
Noticed even my caps had stopped transmitting.

Rebooted switch. Everything came back.

Looked at the log from my router.
Sfp-sfpplus1 fcs error on link

After rebooting the switch.
Sfp-sfpplus1 link down
Sfp-sfpplus1 link up (Speed 10G, full duplex)

Few seconds later. Everything got IP addresses and returned to normal.

Re: FCS error on link

Sun Dec 29, 2019 10:42 pm

Re: FCS error on link

Sun Dec 29, 2019 11:39 pm

Unit had been in operation for a few weeks at this point.

During lockup.
It still provided POE to a hAP AC2 and to a 5 port 260.

Re: FCS error on link

Mon Dec 30, 2019 9:38 am

Re: FCS error on link

Mon Dec 30, 2019 6:02 pm

Re: FCS error on link

Mon Dec 30, 2019 7:21 pm

Re: FCS error on link

Mon Dec 30, 2019 7:22 pm

Re: FCS error on link

Mon Dec 30, 2019 8:16 pm

Re: FCS error on link

Mon Dec 30, 2019 11:10 pm

The FCS error was what the router was reporting when the switch was locked up.

That cable had been used before with another manufacture’s switch, and the switch never locked up.

The cable is a direct connect type where the modules that go into the router and switch are part of the cable.

I was hoping I was providing meaningful data that could be used to CORRECT whatever made this happen.

And remember. This is the first time I observed this problem at the office, and the system had been running for over a week. Infact. It was working one second then not. I was watching something on Amazon Prime on my computer at the time. I only noticed when the error screen popped up.

Источник

Ethernet

Sub-menu: /interface ethernet
Standards: IEEE 802.3

Properties

Read-only properties

Menu specific commands

Monitor

To print out a current link rate, duplex mode, and other Ethernet related properties or to see detailed diagnostics information for transceivers, use /interface ethernet monitor command. The provided information can differ for different interface types (e.g. Ethernet over twisted pair or SFP interface) or for different transceivers (e.g. SFP and QSFP).

Properties

Example output of an Ethernet status:

Example output of a SFP status:

Detect Cable Problems

Cable test can detect problems or measure the approximate cable length if the cable is unplugged on the other end and there is therefore, «no-link». RouterOS will show:

Here is example output:

In the above example, the cable is not shorted but “open” at 4 meters distance, all cable pairs equally faulty at the same distance from the switch chip.

Currently cable-test is implemented on the following devices:

Note: Currently cable-test is not supported on Combo ports.

Stats

Using /interface ethernet print stats command, it is possible to see a wide range of Ethernet related statistics. The list of statistics can differ between RouterBoard devices due to different Ethernet drivers. The list below contains all available counters across all RouterBoard devices. Most of the Ethernet statistics can be remotely monitored using SNMP and MIKROTIK-MIB.

For example, output of Ethernet stats on hAP ac2 device:

Источник