if it's clean then your looking at a buffer bump, sometime during the monitored time frame, one port (b=11) ran all 1's (FF)for more then a frame.. unless your seeing that as a flood, ignore it.. all one's is the cover all, no response from the far end.. could have been caused by midn or a stat.. but your right to enquire and follow up on all codes.. no other way to keep one clean
As a follow-up note... We did start having problems with the CCR after all. So I software shut down the system and then power cycled to hard reboot it. Results, back up and running error free.
that can happen. something lost sync between the two.. most of the time i remember the old rule, if it's not broke, do not fix it.. but with this box a small problem will always get worse.. and usually at the worst time... like friday at 4 o'clock before a three day weekend
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.