Sponsored Content
Operating Systems Solaris gigabit - fix speed/duplex on the switch ? or autoneg ? Post 302309241 by hcclnoodles on Tuesday 21st of April 2009 11:31:20 AM
Old 04-21-2009
gigabit - fix speed/duplex on the switch ? or autoneg ?

Hi there

We have a bit of a debate going here over what the prefered method is for setting 1000/Full on e1000g or nge interfaces is.

As you aware the Solaris configration files for nge and e1000g dont allow you to "fix" 1000/Full but instead allow you to set auto-negotiate to ON but only advertise the capability to set 1000/Full. All of our Solaris boxes have been configured using this method .... BUT, on the Cisco switch side we have recently discovered that half the sysadmins have been FIXING the switchport to 1000/FULL and the other half have been setting the switchport to autonegotiate ( mirroring the server config )

Now the thing is, both seem to work absolutely fine,


On the switch, the fixed ports come up as

Gi1/36 server1 connected 3 full 1000

and the ones where the switch is configured as auto-neg..like this

Gi1/12 server2 connected 3 a-full a-1000



"dladm show-dev" on both Solaris boxes confirms that 1000/Full is set as well

We are finally in the process of putting an absolute procedure together with the preffered method of doing this , so what is the prefered method? My understanding is that if you autoneg on one side it is best practice to autoneg on the other ? is this correct ....? but as i say, both methods seem to achieve the desired result


Any input would be greatly appreciated
 

10 More Discussions You Might Find Interesting

1. Solaris

100 gigabit full duplex

How can I tell on Solaris 9 sparc if my nics are running 100 gigabit full duplex... (4 Replies)
Discussion started by: csaunders
4 Replies

2. IP Networking

NIC speed 100M/full duplex problem

I have a TOSHIBA AS7000 B150 Sun Box I wanted to run it with 100M/full duplex I had added this to the /etc/system file to make to setting permenant So it would be set correctly on reboot. set eri:eri_adv_100fdx_cap=1 set eri:eri_adv_100hdx_cap=0 set eri:eri_adv_autoneg_cap=0 But when I... (4 Replies)
Discussion started by: AirWalker83
4 Replies

3. IP Networking

Gigabit Link throughput

As a rule of thumb in doing calculations, what figure would you use in Mbytes/sec? I know the answer varies grealty on the topolgy of the network but I wonde what newteok engineers use a rough rule of thumb? Many thanks. (1 Reply)
Discussion started by: debd
1 Replies

4. Infrastructure Monitoring

How to find the duplex speed on Windows

Hi, In UNIX, it's very easy to find the duplex speed. But in Windows, is there a easy way to find the duplex speed? I can't go to over 100 servers to find this out, I was wondering if I run one command to do this? Please advice. (2 Replies)
Discussion started by: samnyc
2 Replies

5. Solaris

Solaris 10 Speed and Duplex Settings: bge

Evening, I am attempting to change the speed and duplex settings on a single interface on a bge card on an m3000 SPARC server. Currently the settings are as follows: bge0 link: up speed: 1000 Mbps duplex: full bge1 link: up speed: 100 Mbps ... (13 Replies)
Discussion started by: brialt1
13 Replies

6. Filesystems, Disks and Memory

data from blktrace: read speed V.S. write speed

I analysed disk performance with blktrace and get some data: read: 8,3 4 2141 2.882115217 3342 Q R 195732187 + 32 8,3 4 2142 2.882116411 3342 G R 195732187 + 32 8,3 4 2144 2.882117647 3342 I R 195732187 + 32 8,3 4 2145 ... (1 Reply)
Discussion started by: W.C.C
1 Replies

7. UNIX for Advanced & Expert Users

check remote switch port speed setting

Hi, Someone told me how to check the remote switch port's speed setting on the other end of the cable, from linux. I forgot it. Anyone knows? I checked dmesg, ethtool (haven't checked this out thoroughly) , no luck. thanks, Marc (1 Reply)
Discussion started by: marcpascual
1 Replies

8. Solaris

How to find half duplex or full duplex

Hi, How to find whether the server is running with half duplex or full duplex. I tried with the following command ndd -get /dev/ but am not getting any output,. Is the command correct? Also let me know how to change from half to full duplex. (1 Reply)
Discussion started by: rogerben
1 Replies

9. AIX

How to change Speed Duplex

How to change Speed Duplex ! How to change Speed Duplex by command chdev -P -l ent1 -a media_speed=1000_Full_Duplex How to change Speed Duplex by Smitty . smitty chgenet -> select adapter -> change Media speed etc. -> set "Apply change to DATABASE only" to yes -> Enter -> ... (0 Replies)
Discussion started by: ITHelper
0 Replies

10. AIX

Connected and Running with half duplex speed

VIO Server connected to switch port and running with half duplex speed on one of the shared ethernet adapter. We have verified at switch end and everythings looks good. Other ethernet adapter in the VIO server are connected and running in Full duplex speed. Please help me find why this shared... (4 Replies)
Discussion started by: mugunthanvh
4 Replies
NGE(4)							   BSD Kernel Interfaces Manual 						    NGE(4)

NAME
nge -- National Semiconductor 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 nge Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_nge_load="YES" DESCRIPTION
The nge driver provides support for various NICs based on the National Semiconductor DP83820 and DP83821 Gigabit Ethernet controller chips. The DP83820 supports TBI (ten bit interface) and GMII transceivers, which means it can be used with either copper or 1000baseX fiber applica- tions. The DP83820 supports TCP/IP checksum offload and VLAN tagging/insertion as well as a 2048-bit multicast hash filter and up to 4 pat- tern match buffers. Most cards also use the DP83861 10/100/1000 copper gigabit transceiver chip, which supports autonegotiation of 10, 100 and 1000Mbps modes in full or half duplex. The DP83820 and DP83821 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 per- formance for certain tasks, such as file transfers and data streaming. The nge 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. full-duplex and half-duplex modes are supported. 1000baseSX Set 1000Mbps (Gigabit Ethernet) operation. Both full-duplex and half-duplex modes are supported. The nge 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 nge driver supports National Semiconductor DP83820 and DP83821 based Gigabit Ethernet adapters including: o Addtron AEG320T o Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T (64-bit PCI) o Asante FriendlyNet GigaNIX 1000TA and 1000TPC o D-Link DGE-500T o Linksys EG1032, revision 1 o Netgear GA621 o Netgear GA622T o SMC EZ Card 1000 (SMC9462TX) o Surecom Technology EP-320G-TX o Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 (64-bit PCI) SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables: dev.nge.%d.int_holdoff Maximum amount of time to delay interrupt processing in units of 100us. The accepted range is 0 to 255, the default is 1(100us). Value 0 completely disables the interrupt moderation. The interface has to be brought down and up again before a change takes effect. DIAGNOSTICS
nge%d: couldn't map memory A fatal initialization error has occurred. nge%d: couldn't map ports A fatal initialization error has occurred. nge%d: couldn't map interrupt A fatal initialization error has occurred. nge%d: no memory for softc struct! The driver failed to allocate memory for per-device instance information during initialization. nge%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. nge%d: no memory for jumbo buffers! The driver failed to allocate memory for jumbo frames during initialization. nge%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) National Semiconductor DP83820 datasheet, http://www.national.com. National Semiconductor DP83861 datasheet, http://www.national.com. HISTORY
The nge device driver first appeared in FreeBSD 4.4. AUTHORS
The nge driver was written by Bill Paul <wpaul@bsdi.com>. BSD
November 23, 2010 BSD
All times are GMT -4. The time now is 10:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy