Sponsored Content
Full Discussion: Network performance problem
Top Forums UNIX for Dummies Questions & Answers Network performance problem Post 302282978 by teradatadba on Monday 2nd of February 2009 09:55:26 AM
Old 02-02-2009
Sounds like a duplex mismatch - one end is half and the other full. I know you've already checked, but do make sure that both ends are set to full.

Cisco have a good troubleshooting guide on their website (http://www.cisco.com/application/pdf/paws/17053/46.pdf). Your symptoms align well with their description of duplex mismatch.

However, note also that the section on "NIC Compatibility" has Intel Pro/1000 listed as a known problem, for which the "latest drivers" are required, so maybe that's worth a try.

There is a note on the Teradata Forum (albeit four years old) that suggests turning off "in-line power" from the switch. Re: Slow Responding State - looking for bottleneck [From Anomy Anom: Fri, 18 Jun 2004 @ 17:07 GMT]

Once the basic connectivity is sorted don't forget to enable jumbo frames on the switch and set the NICs mtu to 9000 and enable "full-size frames". You'll probably also need to increase your TCP send and receive buffer sizes (to at least 1000Mbit times your ping time in seconds) in order to get the best throughput. All these parameters can be seen using ifconfig.

Finally, if your Teradata/MP-RAS machines were not shipped to you with gigabit NICs (i.e. you've upgraded some old machines) then you may need to increase the MAXETHERPACKETSIZE kernel variable and recompile/reboot in order to get the full 9000 packet size. Use idtune -g MAXETHERPACKETSIZE to see what it's set to.

HTH.
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

performance problem

Hello, I have a mail server (sendmail) with SUNOS 5.5.1. Just recently it began to respond very slowly. I used vmstat to check the performance data. Only interupt, system call and CPU context swiching are relatively high. Other statistics are normal, especially CPU utilization are very... (5 Replies)
Discussion started by: caoai
5 Replies

2. AIX

Network performance problem between AIX and SUN ethernet gigabit

I am posting this as an FYI. I burned a lot of time on digging for this solution. The problem was performance between newer AIX p series boxes and a sun 4500 with a fiber nic. I tried many misc. solutions but this turned out to fix the issue. My bandwidth benchmark went from around 20MB/sec to... (1 Reply)
Discussion started by: chuckw
1 Replies

3. Linux

Wireless network card performance

I am running FC4: Linux maincomp 2.6.13-1.1532_FC4smp I recently changed the OS from windows XP, and have a feeling that for some reason my wireless network card is slower on Fedora Core 4. The Belkin PCI 802.11b card was automatically detected and configured by FC4 when I installed the OS,... (0 Replies)
Discussion started by: dangral
0 Replies

4. Solaris

Performance problem

Hi All, There is a virtual user "ecoouk" which logs on to the server and runs some scripts. I want to know how much server performance can I gain if I put off all the scripts run by this user. Please tell me how to analyse how much resources a specific user is using. Regards, Abhishek (3 Replies)
Discussion started by: max29583
3 Replies

5. Solaris

Solaris 11.1 Slow Network Performance

I have identical M5000 machines that are needing to transfer very large amounts of data between them. These are fully loaded machines, and I've already checked IO, memory usage, etc... I get poor network performance even when the machines are idle or copying via loopback. The 10 GB NICs are... (7 Replies)
Discussion started by: christr
7 Replies

6. AIX

Network performance changes

Hi, Recently I've been doing some performance changes for inter-lpar configs and completing some testing. So far test have been successful and promising but only completed in a dev environment. Here is what I've done created a separated vlan for inter-lpar communications separate from the... (1 Reply)
Discussion started by: techy1
1 Replies
IE(4)							 BSD/i386 Kernel Interfaces Manual						     IE(4)

NAME
ie -- Ethernet device driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device ie Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_ie_load="YES" In /boot/device.hints: hint.ie.0.at="isa" hint.ie.0.port="0x300" hint.ie.0.irq="5" hint.ie.0.maddr="0xd0000" HARDWARE
The ie driver provides supports the following 8 and 16bit ISA Ethernet cards that are based on the Intel i82586 chip: o 3COM 3C507 o AT&T EN100 o AT&T Starlan 10 o AT&T Starlan Fiber o Intel EtherExpress 16 o RACAL Interlan NI5210 DIAGNOSTICS
ie%d: unknown board type code %d An i82586 chip was found, but the driver was unable to determine the actual board type during the probe. ie%d: kernel configured maddr %x doesn't match board configured maddr %x The device probe detected a different maddr than the one specified in the kernel configuration file. ie%d: can't find shared memory The device probe could not access the shared memory to determine its size. ie%d: kernel configured msize %d doesn't match board configured msize %d The device probe found a different size for the shared memory than the one specified in the kernel configuration file. ie%d: kernel configured irq %d doesn't match board configured irq %d The device probe detected that the board is configured for a different interrupt than the one specified in the kernel configuration file. ie%d: reset The Intel i82586 had to be reset by the driver. ie%d: transceiver problem The driver has detected a problem with the Ethernet transceiver. This is usually due to a loose or broken trans- ceiver cable when using an external transceiver. When you experience this problem with an on-card transceiver your card may be incorrectly jumpered for to use an external transceiver. Worst case your on-board transceiver may be broken. ie%d: TDR detected an open %d clocks away The driver detected an open circuit in the Ethernet cable. Check your coax cable and terminator resistors. ie%d: TDR detected a short %d clocks away The driver detected a short circuit in the Ethernet cable. Check your coax cable and terminator resistors. ie%d: TDR returned unknown status %x The driver got an unknown status from the card during the Ethernet cable test. ie%d: multicast address setup command failed The card could not be put into multicast mode. ie%d: configure command failed The card refused to respond correctly during configuration. ie%d: individual address setup command failed The programming of the Ethernet (MAC) address failed. CAVEATS
The Racal Interlan NI5210 comes in variants with 8 and 16 kbytes of shared memory. It is strongly advisable to use the 16 kbyte variant. You can upgrade your 8 kbyte card to 16 kbyte by adding an additional RAM chip. SEE ALSO
arp(4), netintro(4), ng_ether(4), ifconfig(8) AUTHORS
The ie device driver was written by Garrett A. Wollman, based on code by William F. Jolitz and Lawrence Berkeley Laboratories. 3C507 support was written by Charles M. Hannum. This manual page was written by Wilko C. Bulte. BSD
July 16, 2005 BSD
All times are GMT -4. The time now is 07:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy