[ale] Odd network issue

Lightner, Jeff JLightner at dsservices.com
Thu Jul 9 11:07:01 EDT 2015


Changing NIC ports was already next on our list but it’s a remote data center so someone has to go onsite for that.   As it happens we have both Broadcom and Intel in this system so we’ll be able to eliminate the controller by moving from the Broadcom to the Intel as well.


From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of leam hall
Sent: Thursday, July 09, 2015 9:38 AM
To: Atlanta Linux Enthusiasts
Subject: Re: [ale] Odd network issue

Okay, yeah...that's odd. Is there more than one NIC? Can you swap out NICs? Maybe freshen all the OS packages to ensure there's no module or kernel wonkiness?


On Thu, Jul 9, 2015 at 9:17 AM, Lightner, Jeff <JLightner at dsservices.com<mailto:JLightner at dsservices.com>> wrote:
We have a server that appears to be unable to connect to various IPs (mostly printers) in our WAN at times.

The odd thing is that the interface is not down on either the server or the printer.   The server can reach multiple other IPs when this occurs but for some reason can’t reach a few.    Similarly when this occurs we can reach these other IPs from other servers in the same VLAN.

There are no errors shown in statistics on the interface (eth0) on the server nor on the port it attached to on the switch.   There are no errors shown in /var/log/messages or dmesg.

The IPs are not always the same ones.   In fact yesterday when we saw the issue on IPs I tested the IPs that it couldn’t reach the day before that I’d resolved and they were still working.


We’ve tried:
Killing the lp process that is hung at the start of this issue on server side.
Clearing arp on the server.
Clearing arp on the switch.
Bouncing cups (note issue is NOT just cups – when this occurs we can not ping the affected IPs nor can we telnet in on port 9100 as we would normally be able to do).

The only thing that seems to resolve the issue (and does each time) is having the interface bounce on the server.
We’’ve done that by:
Rebooting the server
Ifup/ifdown on the server interface
Removing and reseating the cable.
Resetting the switch port.
In each of those we see the port go down then come back up and after that the previously unreachable IPs are again reachable.

I’m suspecting a bad interface port on either the server or the switch but in the absence of actual errors can’t prove one way or the other.

This is different than any other network issue I’ve seen.   I’m wondering if anyone has run into this and can shed any light on it?



CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you


_______________________________________________
Ale mailing list
Ale at ale.org<mailto:Ale at ale.org>
http://mail.ale.org/mailman/listinfo/ale
See JOBS, ANNOUNCE and SCHOOLS lists at
http://mail.ale.org/mailman/listinfo



--
Mind on a Mission<http://leamhall.blogspot.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20150709/9c46ea4b/attachment.html>


More information about the Ale mailing list