Sponsored Content
Operating Systems AIX Connected and Running with half duplex speed Post 302678405 by mugunthanvh on Friday 27th of July 2012 08:22:36 PM
Old 07-27-2012
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 ethernet adapter is having half duplex speed and how to fix this back to full duplex.

Sometime back it was running as full duplex and recently there were no changes/upgrades on both switch and VIO server level.

Code:
 
$ ioslevel
2.1.2.10-FP-22
 
# lsdev -Cc adapter | grep -i ent14
ent14    Available       Shared Ethernet Adapter
 
# entstat -d ent14 | grep -i media
Media Speed Selected: Auto negotiation
Media Speed Running: 10 Mbps Half Duplex
 
# lsattr -El ent14 | grep -i real
real_adapter  ent4     Physical adapter associated with the SEA                           True

- Mugunth
 

8 More Discussions You Might Find Interesting

1. 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

2. Solaris

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... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

3. 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

4. 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

5. 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

6. 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

7. Linux

Network 10Mb/s half duplex only. r8168 on Centos 5.

Hi, For some reason my network card started going 10Mb/s half duplex instead of 1000Mb/s full duplex. System is connected to 8x1Gb HP switch. Other devices connect fine through the switch and get full 1Gb network. I have Centos 5 with all updates. Driver comes from elrepo and as well is... (1 Reply)
Discussion started by: columb
1 Replies

8. SCO

System Clock running at half speed

SCO Openserver 6.0.0 had an issue with a NIC losing it's config on reboot. Netconfig would not allow "view protocol" and apparently zeroed out the existing IP info. Repaired from console. After this event, however, the system clock seems to lose 30 seconds for every RTC minute that passes. As a... (1 Reply)
Discussion started by: DoublePanic
1 Replies
SK(4)							   BSD Kernel Interfaces Manual 						     SK(4)

NAME
sk, skc -- SysKonnect XMAC II and Marvell GMAC based gigabit ethernet SYNOPSIS
skc* at pci? dev ? function ? sk* at skc? mskc* at pci? dev ? function ? msk* at skc? DESCRIPTION
The sk driver provides support for SysKonnect based gigabit ethernet adapters and Marvell based gigabit ethernet adapters, including the fol- lowing: o SK-9821 SK-NET GE-T single port, copper adapter o SK-9822 SK-NET GE-T dual port, copper adapter o SK-9841 SK-NET GE-LX single port, single mode fiber adapter o SK-9842 SK-NET GE-LX dual port, single mode fiber adapter o SK-9843 SK-NET GE-SX single port, multimode fiber adapter o SK-9844 SK-NET GE-SX dual port, multimode fiber adapter o SK-9521 V2.0 single port, copper adapter (32-bit) o SK-9821 V2.0 single port, copper adapter o SK-9843 V2.0 single port, copper adapter o 3Com 3c940 single port, copper adapter o Belkin Gigabit Desktop Network PCI Card, single port, copper (32-bit) o D-Link DGE-530T single port, copper adapter o Linksys EG1032v2 single-port, copper adapter o Linksys EG1064v2 single-port, copper adapter The msk driver provides support for the Marvell Yukon-2 based Gigabit Ethernet adapters, including the following: o Marvell Yukon 88E8035, copper adapter o Marvell Yukon 88E8036, copper adapter o Marvell Yukon 88E8038, copper adapter o Marvell Yukon 88E8050, copper adapter o Marvell Yukon 88E8052, copper adapter o Marvell Yukon 88E8053, copper adapter o Marvell Yukon 88E8055, copper adapter o SK-9E21 1000Base-T single port, copper adapter o SK-9E22 1000Base-T dual port, copper adapter o SK-9E81 1000Base-SX single port, multimode fiber adapter o SK-9E82 1000Base-SX dual port, multimode fiber adapter o SK-9E91 1000Base-LX single port, single mode fiber adapter o SK-9E92 1000Base-LX dual port, single mode fiber adapter o SK-9S21 1000Base-T single port, copper adapter o SK-9S22 1000Base-T dual port, copper adapter o SK-9S81 1000Base-SX single port, multimode fiber adapter o SK-9S82 1000Base-SX dual port, multimode fiber adapter o SK-9S91 1000Base-LX single port, single mode fiber adapter o SK-9S92 1000Base-LX dual port, single mode fiber adapter o SK-9E21D 1000Base-T single port, copper adapter The SysKonnect based adapters consist of two main components: the XaQti Corp. XMAC II Gigabit MAC (sk) and the SysKonnect GEnesis controller ASIC (skc). The XMAC provides the Gigabit MAC and PHY support while the GEnesis provides an interface to the PCI bus, DMA support, packet buffering and arbitration. The GEnesis can control up to two XMACs simultaneously, allowing dual-port NIC configurations. The Marvell based adapters are a single integrated circuit, but are still presented as a separate MAC (sk) and controller ASIC (skc). At this time, there are no dual-port Marvell based NICs. The sk driver configures dual port SysKonnect adapters such that each XMAC is treated as a separate logical network interface. Both ports can operate independently of each other and can be connected to separate networks. The SysKonnect driver software currently only uses the second port on dual port adapters for failover purposes: if the link on the primary port fails, the SysKonnect driver will automatically switch traffic onto the second port. The XaQti XMAC II supports full and half duplex operation with autonegotiation. The XMAC also supports unlimited frame sizes. Support for jumbo frames is provided 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. Hardware TCP/IP checksum offloading for IPv4 is supported. The following media types and options (as given to ifconfig(8)) are supported: media autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode. media 1000baseSX mediaopt full-duplex Set 1000Mbps (Gigabit Ethernet) operation on fiber and force full-duplex mode. media 1000baseSX mediaopt half-duplex Set 1000Mbps (Gigabit Ethernet) operation on fiber and force half-duplex mode. media 1000baseT mediaopt full-duplex Set 1000Mbps (Gigabit Ethernet) operation and force full-duplex mode. For more information on configuring this device, see ifconfig(8). To view a list of media types and options supported by the card, try ifconfig -m <device>. For example, ifconfig -m sk0. DIAGNOSTICS
sk%d: couldn't map memory A fatal initialization error has occurred. sk%d: couldn't map ports A fatal initialization error has occurred. sk%d: couldn't map interrupt A fatal initialization error has occurred. sk%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. sk%d: no memory for jumbo buffers! The driver failed to allocate memory for jumbo frames during initialization. sk%d: watchdog timeout The device has stopped responding to the network, or there is a problem with the network connection (cable). SEE ALSO
ifmedia(4), intro(4), netintro(4), pci(4), ifconfig(8) XaQti XMAC II datasheet, http://www.xaqti.com. SysKonnect GEnesis programming manual, http://www.syskonnect.com. HISTORY
The sk device driver first appeared in FreeBSD 3.0. OpenBSD support was added in OpenBSD 2.6. NetBSD support was added in NetBSD 2.0. The msk driver first appeared in OpenBSD 4.0, and was ported to NetBSD 4.0. AUTHORS
The sk driver was written by Bill Paul <wpaul@ctr.columbia.edu>. Support for the Marvell Yukon-2 was added by Mark Kettenis <kettenis@openbsd.org>. BUGS
This driver is experimental. Support for checksum offload is unimplemented. Performance with at least some Marvell-based adapters is poor, especially on loaded PCI buses or when the adapters are behind PCI-PCI bridges. It is believed that this is because the Marvell parts have significantly less buffering than the original SysKonnect cards had. BSD
September 9, 2006 BSD
All times are GMT -4. The time now is 11:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy