Visit Our UNIX and Linux User Community


Stange problem Dell PowerEdge 1950/ Boradcom Netextreme NIC


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Stange problem Dell PowerEdge 1950/ Boradcom Netextreme NIC
# 1  
Old 10-17-2007
Stange problem Dell PowerEdge 1950/ Boradcom Netextreme NIC

I have 2 Dell Poweredge 1950 servers running . I have been having intermittent performance issues with the NIC cards on one of them. The two servers are identical and are running the same operating system. The server that has the issue is on the DMZ on a a static IP and is hosting a website. THe issue is, that any network related activity becomes very slow at times. When I connect to the server, the ssh tunnel taken time to establish, if I do pings it takes time to bring up the response. However, once I am on the box, things fly! At the same time if I do the same pings and run the same networking commands on the other servers in the DMZ, they are responsive - the pings themselves don't take time... but there is a long lag between the time I execute the command and the time the response displays. Please advise.
OS: CentOS release 4.5 (Final)
Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11)
Linux version 2.6.9-55.ELsmp (mockbuild@builder6.centos.org) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-8)) #1 SMP Wed May 2 14:04:42 EDT 2007
 

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Solaris

Solaris 10 installation on dell power edge 1950

Hi, I am about to try Solaris 10 on a dell power edge 1950 server. I have googled and found some articles(2007) saying its not supported. Anybody tried this recently? Thanks in advance (2 Replies)
Discussion started by: ./hari.sh
2 Replies

2. SCO

Dell PowerEdge 2600 tape backup

I was asked to get a Dell PowerEdge 2600 server, out of warranty, running SCO 3.2v5.06 to perform a full backup. I spent hours researching and preparing a strategy only to fail on-site. The only device names in /dev for a tape drive were /dev/xStp0 /dev/xcdt0 /dev/xct0 ... (6 Replies)
Discussion started by: ezlarry
6 Replies

3. Programming

/dev/mem on Dell Poweredge

Hi, I have a C++ program to access /dev/mem and retrieve details like Vendor, Manufacturer details of the motherboard. This works fine on all the machines except for on Dell Poweredge 2850,1950... machines. I receive a 'EFAULT' when I try to access /dev/mem on these servers. I suspect some... (1 Reply)
Discussion started by: ragisreekanth
1 Replies

4. SCO

Continueing relyability problems with SCO 6.0 on Dell Poweredge 1800 with PERC DC4.

Hello all, I'am experiencing weird relyability problems with a SCO 6.0 Openserver server that runs on a Dell Poweredge 1800 equipped with a PERC DC4 raid controller and 4 36 GB 15 K rpm hot swappable scsi harddisks. It runs a RAID 10 configuration. It uses the mega hba, Revision 8.03a Release... (1 Reply)
Discussion started by: frederik1
1 Replies

5. Filesystems, Disks and Memory

Linux and Dell 1500sc Poweredge Server

Does anybody no how to get around the fact that the Red Hat installation does not see the SCSI hard drives. It lets you manually pick the proper device, but still fails saying no drive detected (or something to that effect). I was going to install windows 2003 Server and use VMware...but again,... (1 Reply)
Discussion started by: Fatflea
1 Replies

6. Solaris

Installing Solaris 10 on Dell PowerEdge 2800

hi, i am trying to install solaris 10 (on 4 cd's downloaded from the sun website) on my dell poweredge 2800 server. 2 xeon processors, 2GB of RAM and 2 NICS, 73 GB SCSI (maxtor ultra320, 3.5 series), i can give more details on request... the installation crashes when trying to detect the NICS... (0 Replies)
Discussion started by: xinugeek
0 Replies

7. Linux Benchmarks

Dell Poweredge 2400 / 533

CPU/Speed: Dual PIII 533 Ram: 256Mb PC133 Motherboard: Unknown, Intel Chipset Cache: 256k on board Controller: PARC Raid 2/Si, AIC-7880U Disk: 30Gb RAID 5 Load: 1 user. Clean boot, init 5 but X-Windows not loaded. Kernel: See Benchmarks. pgms: gcc 3.2.3 ... (2 Replies)
Discussion started by: Garp
2 Replies

8. Linux Benchmarks

Dell Dual Xeon PowerEdge 4600

Notes: System Configuration: Dell Computer Corporation PowerEdge 4600 (4 X Intel(R) XEON(TM) CPU 2.00GHz 1988.782 MHz) hyperthreaded System clock frequency: 99.0827 MHz Memory size (approximate): 2559 Megabytes ========================= CPUs ======================== CPU # CPU... (0 Replies)
Discussion started by: tnorth
0 Replies
BGE(4)							   BSD Kernel Interfaces Manual 						    BGE(4)

NAME
bge -- Broadcom BCM57xx/BCM590x Gigabit/Fast Ethernet driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device bge Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_bge_load="YES" DESCRIPTION
The bge driver provides support for various NICs based on the Broadcom BCM570x, 571x, 572x, 575x, 576x, 578x, 5776x and 5778x Gigabit Ether- net controller chips and the 590x and 5779x Fast Ethernet controller chips. All of these NICs are capable of 10, 100 and 1000Mbps speeds over CAT5 copper cable, except for the SysKonnect SK-9D41 which supports only 1000Mbps over multimode fiber. The BCM570x builds upon the technology of the Alteon Tigon II. It has two R4000 CPU cores and is PCI v2.2 and PCI-X v1.0 compliant. It supports IP, TCP and UDP checksum offload for both receive and transmit, multiple RX and TX DMA rings for QoS applications, rules-based receive filtering, and VLAN tag stripping/insertion as well as a 256-bit multicast hash filter. Additional fea- tures may be provided via value-add firmware updates. The BCM570x supports TBI (ten bit interface) and GMII transceivers, which means it can be used with either copper or 1000baseX fiber applications. Note however the device only supports a single speed in TBI mode. Most BCM5700-based cards also use the Broadcom BCM5401 or BCM5411 10/100/1000 copper gigabit transceivers, which support autonegotiation of 10, 100 and 1000Mbps modes in full or half duplex. The BCM5700, BCM5701, BCM5702, BCM5703, BCM5704 and BCM5717 also support 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 bge 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). 10baseT/UTP Set 10Mbps operation. The ifconfig(8) mediaopt option can also be used to select either full-duplex or half-duplex modes. 100baseTX Set 100Mbps (Fast Ethernet) operation. The ifconfig(8) mediaopt option can also be used to select either full-duplex or half-duplex modes. 1000baseTX Set 1000baseTX operation over twisted pair. Only full-duplex mode is supported. 1000baseSX Set 1000Mbps (Gigabit Ethernet) operation. Both full-duplex and half-duplex modes are supported. The bge 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
The bge driver provides support for various NICs based on the Broadcom BCM570x family of Gigabit Ethernet controller chips, including the following: o 3Com 3c996-SX (1000baseSX) o 3Com 3c996-T (10/100/1000baseTX) o Dell PowerEdge 1750 integrated BCM5704C NIC (10/100/1000baseTX) o Dell PowerEdge 2550 integrated BCM5700 NIC (10/100/1000baseTX) o Dell PowerEdge 2650 integrated BCM5703 NIC (10/100/1000baseTX) o Dell PowerEdge R200 integrated BCM5750 NIC (10/100/1000baseTX) o Dell PowerEdge R300 integrated BCM5722 NIC (10/100/1000baseTX) o IBM x235 server integrated BCM5703x NIC (10/100/1000baseTX) o HP Compaq dc7600 integrated BCM5752 NIC (10/100/1000baseTX) o HP ProLiant NC7760 embedded Gigabit NIC (10/100/1000baseTX) o HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseTX) o HP ProLiant NC7771 PCI-X Gigabit NIC (10/100/1000baseTX) o HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseTX) o Netgear GA302T (10/100/1000baseTX) o SysKonnect SK-9D21 (10/100/1000baseTX) o SysKonnect SK-9D41 (1000baseSX) LOADER TUNABLES
The following tunable can be set at the loader(8) prompt before booting the kernel, or stored in loader.conf(5). hw.bge.allow_asf Allow the ASF feature for cooperating with IPMI. Can cause system lockup problems on a small number of systems. Disabled by default. SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables: dev.bge.%d.forced_collapse Allow collapsing multiple transmit buffers into a single buffer to increase transmit performance with the cost of CPU cycles. The default value is 0 to disable transmit buffer collapsing. dev.bge.%d.forced_udpcsum Enable UDP transmit checksum offloading even if controller can generate UDP datagrams with checksum value 0. UDP datagrams with checksum value 0 can confuse receiver host as it means sender did not compute UDP checksum. The default value is 0 which disables UDP transmit checksum offloading. The interface need to be brought down and up again before a change takes effect. DIAGNOSTICS
bge%d: couldn't map memory A fatal initialization error has occurred. bge%d: couldn't map ports A fatal initialization error has occurred. bge%d: couldn't map interrupt A fatal initialization error has occurred. bge%d: no memory for softc struct! The driver failed to allocate memory for per-device instance information during initialization. bge%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. bge%d: no memory for jumbo buffers! The driver failed to allocate memory for jumbo frames during initialization. bge%d: watchdog timeout The device has stopped responding to the network, or there is a problem with the network connection (cable). SEE ALSO
altq(4), arp(4), miibus(4), netintro(4), ng_ether(4), polling(4), vlan(4), ifconfig(8) HISTORY
The bge device driver first appeared in FreeBSD 4.5. AUTHORS
The bge driver was written by Bill Paul <wpaul@windriver.com>. BSD
November 23, 2010 BSD

Featured Tech Videos