Issue with PowerEdge 1850 network connectivity
JackHammer19
jackhammer19 at gmail.com
Mon May 1 09:35:55 CDT 2006
On 5/1/06, Stephen John Smoogen <smooge at gmail.com> wrote:
>
> Does dmesg on the affected box show anything? The problem is with eth1
> correct? The last time I saw something like this.. it was because the
> ethernet address was an IP address conflict.. in one case it was a
> router was trying to be fancy with failover, another case it was one
> of the boxes trying to be every IP address on a network but didn't run
> the services. [The last case was a DNS issue where to A records were
> for www.xyz.com.. the second record was a box that didnt run http.
Not a thing, unfortunately. I was looking out for issues such as netdev
watchdog timer timeout etc. which had been reported earlier for Intel
PRO/1000 based cards, but the dmesg output stays clear.
These are the last lines from dmesg:
----------------------------------------------------------------------------------------
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
ip_tables: (C) 2000-2002 Netfilter core team
e1000: eth1: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
lp: driver loaded but no devices found
NET: Registered protocol family 10
Disabled Privacy Extensions on device ffffffff803fc400(lo)
IPv6 over IPv4 tunneling driver
divert: not allocating divert_blk for non-ethernet device sit0
eth1: no IPv6 routers present
eth0: no IPv6 routers present
------------------------------------------------------------------------------------------
It stays this way even when the box has been running for hours - there are
no additional messages logged by the kernel.
I also initially suspected an ARP issue, but when I did an "arp -a" check
around 10 minutes after connecting the firewall (second host), I found all
ARP tables normal - the web server had arp entries pointing to the Cisco
router and the firewall, the firewall (Linux 2.4.21/ IP Tables) had ARP
entries pointing to the web server and the Cisco router, and the Cisco 1720
had arp entries to the other two. The firewall is a regular PC using
Linksys 10/100 network cards - it does not do anything fancy such as proxy
ARP etc. It does not seem to be a DNS issue either - I've checked and
rechecked and the DNS A and PTR records clearly point to the right machine.
Thanks,
JH
> On 4/30/06, David Hubbard <dhubbard at dino.hostasaurus.com> wrote:
> > > Are you using multiple vlans and tagging on any of the links
> > > so that when you add other machines into the mix a port goes
> > > active, causes a switch to start forwarding on a vlan it had
> > > been ignoring before and then you end up with a loop in your
> > > network without spanning tree? Just an idea; since the problem
> > > doesn't occur until another machine is on the network, and
> > > the behavior you describe, make it sound like a spanning tree,
> > > vlan or other similar issue.
> > >
> > > David
> > >
> > > > -----Original Message-----
> > > > From: linux-poweredge-bounces at dell.com
> > > > [mailto:linux-poweredge-bounces at dell.com] On Behalf Of
> > JackHammer19
> > > > Sent: Sunday, April 30, 2006 10:15 PM
> > > > To: linux-poweredge at dell.com
> > > > Subject: Issue with PowerEdge 1850 network connectivity
> > > >
> > > > I have a Dell PowerEdge 1850 web server with dual Intel PRO/1000
> > > > network interfaces built into the motherboard. The operating
> > > > system is
> > > > CentOS 4.2 (identical to Red Hat Enterprise Linux AS 4.2 - built
> from
> > > > Red Hat sources). I am running the latest kernel ( 2.6.9-34.ELsmp).
> > > > The lspci output reports the interfaces as Intel 82541GI/PI.
> > > >
> > > > The system has the latest patches applied.
> > > >
> > > > The e1000 driver information, as reported by modinfo, is:
> > > >
> > > >
> > --------------------------------------------------------------
> > > > ---------------
> > > > $ /sbin/modinfo e1000
> > > > filename:
> > > >
> > /lib/modules/2.6.9-34.ELsmp/kernel/drivers/net/e1000/e1000.ko
> > > > parm: debug:Debug level (0=none,...,16=all)
> > > > version: 6.1.16-k3-NAPI 4BCC06D27AAC4C711223CC9
> > > > license: GPL
> > > > description: Intel(R) PRO/1000 Network Driver
> > > > author: Intel Corporation, <linux.nics at intel.com>
> > > > parm: InterruptThrottleRate:Interrupt Throttling Rate
> > > > parm: RxAbsIntDelay:Receive Absolute Interrupt Delay
> > > > parm: RxIntDelay:Receive Interrupt Delay
> > > > parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay
> > > > parm: TxIntDelay:Transmit Interrupt Delay
> > > > parm: XsumRX:Disable or enable Receive Checksum offload
> > > > parm: FlowControl:Flow Control setting
> > > > parm: AutoNeg:Advertised auto-negotiation setting
> > > > parm: Duplex:Duplex setting
> > > > parm: Speed:Speed setting
> > > > parm: RxDescriptors:Number of receive descriptors
> > > > parm: TxDescriptors:Number of transmit descriptors
> > > > alias: pci:v00008086d000010B5sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000109Asv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001099sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000108Csv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000108Bsv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000108Asv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000107Fsv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000107Esv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000107Dsv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000107Csv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000107Bsv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000107Asv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001079sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001078sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001077sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001076sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001075sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001060sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000105Fsv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001028sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001027sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001026sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000101Esv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000101Dsv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000101Asv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001019sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001018sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001017sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001016sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001015sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001014sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001013sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001012sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001011sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001010sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000100Fsv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000100Esv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000100Dsv*sd*bc*sc*i*
> > > > alias: pci:v00008086d0000100Csv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001009sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001008sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001004sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001001sv*sd*bc*sc*i*
> > > > alias: pci:v00008086d00001000sv*sd*bc*sc*i*
> > > > depends:
> > > > vermagic: 2.6.9-34.ELsmp SMP gcc-3.4
> > > >
> > --------------------------------------------------------------
> > > > ---------
> > > >
> > > > The internal Ethernet interface is connected to a Dell 2708 Gigabit
> > > > switch which has two other hosts with gigabit interfaces
> > > > attached, one
> > > > host with a 100 Mbps full duplex LAN card and an uplink to a 3Com
> > > > SuperStack3 10/100 Mbps full duplex switch.
> > > >
> > > > The external interface connects to another 3Com SuperStack3
> > > > 10/100 Mbps
> > > > full duplex switch which also has a Cisco 1720 router
> > > > attached through a
> > > > 100 Mbps full duplex interface. The Cisco 1720's external serial
> > > > interface connects to a MCI T1 line that provides internet
> > > > connectivity
> > > > to the web server. The server's default route is set to the
> > > > T1 gateway.
> > > > The 3Com switch also has another Cisco 827 router connected to it on
> > > > another totally different IP subnet, which provides Internet
> > > > connectivity to a different set of hosts.
> > > >
> > > > The PE 1850 runs smoothly when it is the only host connected to the
> > > > Cisco router/ T1 line. However, when I attach another host to the
> > > > Cisco router/ T1 line, the web server exhibits huge delays in
> > > > serving web pages.
> > > > The internal interface is unaffected. However external
> > > > clients experience huge delays
> > > > and frequent timeouts and CGI processes accumulate on the web
> server,
> > > > increasing server load till it eventually crashes.
> > > >
> > > > I have tried several methods of fixing this, including moving the T1
> > > > line to a separate Cisco Catalyst 1900 switch, changing the router
> (I
> > > > first had a Cisco 1605R installed with a 10 Mbps half duplex
> > > > port which
> > > > was then upgraded to a Cisco 1720 with a 100 Mbps full duplex
> > > > port) etc.
> > > > I next tried adjusting the e1000 driver settings for the external
> > > > interface (eth1) including the following:
> > > >
> > > > * Interrupt Throttle Rate set to figures between 3000 to 7000
> > > > * Interrupt Throttle Rate set to 70,000
> > > > * Interrupt Throttle Rate turned off (0)
> > > > * Tx and Rx delays and absolute delays set to 0
> > > > * TCP segment offload turned off
> > > >
> > > > in various combinations. Nothing seems to work though, with the web
> > > > server seizing up whenever another host is attached. I still seem
> to
> > > > be able to ping out to the world when logged into the affected
> system
> > > > through the affected external interface though.
> > > >
> > > > Any advice or suggestions would be welcome.
> > > >
> > > > TIA,
> > > >
> > > > JH
> > > >
> > > >
> > > >
> > >
> > > _______________________________________________
> > > Linux-PowerEdge mailing list
> > > Linux-PowerEdge at dell.com
> > >
> > http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> > > Please read the FAQ at http://lists.us.dell.com/faq
> > >
> >
> >
> > _______________________________________________
> > Linux-PowerEdge mailing list
> > Linux-PowerEdge at dell.com
> > http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> > Please read the FAQ at http://lists.us.dell.com/faq
> >
> >
>
>
> --
> Stephen J Smoogen.
> CSIRT/Linux System Administrator
>
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20060501/56683c4c/attachment-0001.htm
More information about the Linux-PowerEdge
mailing list