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
LGE(4)                                                     BSD Kernel Interfaces Manual                                                     LGE(4)

NAME
lge -- Level 1 LXT1001 NetCellerator PCI Gigabit Ethernet adapter driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device lge Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_lge_load="YES" DESCRIPTION
The lge driver provides support for various NICs based on the Level 1 LXT1001 NetCellerator Gigabit Ethernet controller chip. The LXT1001 supports fiber PHYs and also a GMII port for use with 10/100/1000 copper PHYs, however there are currently no NICs on the market that use this feature. The LXT1001 supports TCP/IP checksum offload for receive and VLAN-based filtering as well as a 64-bit multicast hash filter. It also sup- ports jumbo frames, which can be configured via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit jumbo frames. Using jumbo frames can greatly improve performance for certain tasks, such as file transfers and data streaming. The lge driver supports the following media types: autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to rc.conf(5). 1000baseSX Set 1000baseSX operation over fiber optic cable. Both full-duplex and half-duplex modes are supported. The lge driver supports the following media options: full-duplex Force full duplex operation. half-duplex Force half duplex operation. For more information on configuring this device, see ifconfig(8). HARDWARE
Adapters supported by the lge driver include: o SMC TigerCard 1000 (SMC9462SX) o D-Link DGE-500SX DIAGNOSTICS
lge%d: couldn't map memory A fatal initialization error has occurred. lge%d: couldn't map ports A fatal initialization error has occurred. lge%d: couldn't map interrupt A fatal initialization error has occurred. lge%d: no memory for softc struct! The driver failed to allocate memory for per-device instance information during initialization. lge%d: failed to enable memory mapping! The driver failed to initialize PCI shared memory mapping. This might happen if the card is not in a bus-master slot. lge%d: no memory for jumbo buffers! The driver failed to allocate memory for jumbo frames during initialization. lge%d: watchdog timeout The device has stopped responding to the network, or there is a problem with the network connection (cable). SEE ALSO
arp(4), miibus(4), netintro(4), ng_ether(4), ifconfig(8) Level 1 LXT1001 Programming Manual, http://www.FreeBSD.org/~wpaul/Level1/LXT1001SRM.pdf. HISTORY
The lge device driver first appeared in FreeBSD 4.4. AUTHORS
The lge driver was written by Bill Paul <william.paul@windriver.com>. BSD July 16, 2005 BSD
All times are GMT -4. The time now is 12:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy