RX Filtered Error?

User avatar
sbyrd
Experienced Member
 
Posts: 236
Joined: Fri Apr 10, 2015 6:16 pm
Has thanked: 16 times
Been thanked: 26 times

RX Filtered Error?

Wed Jul 01, 2015 9:25 am

I just have a quick question. So far on the two WISP switches I have deployed I always see a large value on all active Interfaces under Receive Error counters ->RX Filtered. What does that mean and should I be concerned? Also to a lesser extent I see an occasional RX Jabber. What is that?

I can give more info about my setup if necessary.

User avatar
sirhc
Employee
Employee
 
Posts: 7414
Joined: Tue Apr 08, 2014 3:48 pm
Location: Lancaster, PA
Has thanked: 1608 times
Been thanked: 1325 times

Re: RX Filtered Error?

Wed Jul 01, 2015 9:35 am

As far as Rx Filtered Errors here is a post:
viewtopic.php?f=6&t=747&p=5516&hilit=rx+filter#p5516

Here is a description for Jabber found on this page:
http://www.networkcomputing.com/netdesi ... rrors.html


Jabber At times, Ethernet network interface card s and external transceivers also generate a problem called jabbering. This is when garbled bits of data are emitted within the frame sequence in a continuous transmission fashion. The packet length is usually more than 1,518 bytes. This can be identified by a protocol analyzer as a CRC error. As mentioned earlier, when nodes detect collisions they emit a normal JAM signal on the network segment to clear transmission. Sometimes certain nodes attempt to keep jamming the network due to excessive high collision rates; this also can be captured as high CRC or late collision error rate. The cause can be overloaded traffic levels. If the bandwidth- utilization levels are normal or low for the particular Ethernet segment, it is possible that the collision detection pair of a jamming node's NIC or transceiver cannot hear the network signal and may not know a collision has stopped. If this occurs, it continues to jam the network.
If a certain node on an Ethernet segment emits a lot of jabber, the node's NIC and transceiver should be troubleshot through consecutive replacement and re-analysis.
If an Ethernet network has intermittent high network bandwidth usage that causes performance problems, the cause can be re-created by loading the network with traffic-generation features in a protocol analyzer. But you must be careful when using this technique. First, be aware of the current network usage and any possible impacts to the network-user community. Second, you really have to understand all the Ethernet network bandwidth considerations discussed earlier, including the actual maximum bandwidth available, the overall network bandwidth baseline view and individual Ethernet node bandwidth consumption. Make sure that a proper baseline is performed on the lower and upper layers of the Ethernet.

November 15, 1996
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.

User avatar
sirhc
Employee
Employee
 
Posts: 7414
Joined: Tue Apr 08, 2014 3:48 pm
Location: Lancaster, PA
Has thanked: 1608 times
Been thanked: 1325 times

Re: RX Filtered Error?

Wed Jul 01, 2015 9:39 am

Here is a screen grab of my second busiest tower and the main interface feeding it.

I too have those Rx Filters which I am not really concerned about but I do not have any Jabbers anywhere on any of my switches so I might try and find out where the problem piece of equipment is. I would be concerned about the Jabbers Errors.

errors.jpg
errors.jpg (216.61 KiB) Viewed 12236 times
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.

Return to General Discussion

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 24 guests