Sponsored Content
Special Forums IP Networking Two Servers via ethernet crossover cable Post 302419637 by Corona688 on Friday 7th of May 2010 04:21:19 PM
Old 05-07-2010
This:
Code:
UP BROADCAST MULTICAST  MTU:1500  Metric:1

...is odd. On my systems I have
Code:
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

It really doesn't believe the cable's plugged in. The LED's might just be hardwired. mii-tool talks with the transceiver itself, so it's the one I'd trust... Very strange that it autonegotiated a 100baseT link with a 1000baseT peer.

Have you tried a normal cable, not a crossover cable? I've sometimes experienced odd behavior with ports capable of autodetecting the cable type. You might also try forcing the speed and duplex, gigabit links often have problems negotiating -- though if you've discovered a gigabit interface that's incapable of negotiating with itself that's certainly something new! Smilie
 

9 More Discussions You Might Find Interesting

1. Solaris

Is the cable you are using a null modem cable or a modem cable

Hi all, Is there any difference between a null modem cable or a modem cable ? i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup. please correct if i am wrong, thks (2 Replies)
Discussion started by: waterbear
2 Replies

2. High Performance Computing

Normal (not crossover) cable for Sun cluster interconnect..

Hi grus, has anybody tried for Sun cluster interconnect normal cable ,, I mean not interconnect .. What do u think ..does it support this ? Not long ago I tried Veritas cluster and its interconnections work great with normal cable .. I wonder what will Sun cluster say to it :)) (3 Replies)
Discussion started by: samar
3 Replies

3. Red Hat

[RHEL4.5] server shutdown when I unplug the ethernet cable

hi.. I unplug my eth0 lan cable.. and suddenly my system shutdown... no idea :eek::confused: (3 Replies)
Discussion started by: flekzout
3 Replies

4. IP Networking

How to handle unplugging ethernet cable in socket programming

Hi, I am trying to implement a server-client socket communication. My server and clients are in different PCs. During communications if the ethernet cable is removed from the server side it shows broken pipe due to unable to write on the socket. I want to know how to check whether the ethernet... (0 Replies)
Discussion started by: JagadishB
0 Replies

5. UNIX for Dummies Questions & Answers

How to change ethernet cable of iscsi initiator (iscsi client)?

how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies

6. Programming

How detect TCP/IP socket shutdown when ethernet cable is disconnected

Hi, I want to code TCP/IP client/server in linux application capable to fastly detect ethernet cable disconnection in any condition. So I have activate SO_KEEPALIVE options and set TCP_KEEPCNT, TCP_KEEPIDLE and TCP_KEEPINTVL to 1. When I disconnect ethernet cable I have the following... (5 Replies)
Discussion started by: jeje_clb
5 Replies

7. Red Hat

Different hostnames with reboot while lan cable, no lan cable

I am facing strange problem regarding hostname on my Linux(2.6.18-164.el5xen x86_64 GNU/Linux), the hostname changes if reboot with lan cable and with NO lan cable Reboot with lan cable: The hostname is ubunut Unable to connect Oracle database using sqlplus some times database is not... (2 Replies)
Discussion started by: LinuxLearner
2 Replies

8. AIX

vio server ethernet to vio client ethernet(concepts confusing)

Hi In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID. Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies

9. AIX

How to check the ethernet status for vlan and lhea adapter in client servers?

Hi Techies, I have a doubt. ent0 Available Logical Host Ethernet Port (lp-hea) ent1 Available Logical Host Ethernet Port (lp-hea) ent2 Available Logical Host Ethernet Port (lp-hea) ent3 Available Logical Host Ethernet Port (lp-hea) ent4 Available... (4 Replies)
Discussion started by: jayadeava
4 Replies
SK(4)							   BSD Kernel Interfaces Manual 						     SK(4)

NAME
sk -- SysKonnect SK-984x and SK-982x 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 sk Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_sk_load="YES" DESCRIPTION
The sk driver provides support for the SysKonnect SK-984x and SK-982x series PCI Gigabit Ethernet adapters. The SysKonnect adapters consist of two main components: the XaQti Corp. XMAC II gigabit MAC and the SysKonnect GEnesis controller ASIC. The XMAC provides the gigabit MAC and PHY support while the GEnesis provides an interface to the PCI bus, DMA support, packet buffering and arbi- tration. The GEnesis can control up to two XMACs simultaneously, allowing dual-port NIC configurations. The SK-982x 1000baseT adapters also include a Broadcom BCM5400 1000baseTX PHY which is used in place of the XMAC's internal PHY. The Broad- com PHY is connected to the XMAC via its GMII port. 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. Also supported is the Marvell Semiconductor 88E100* gigabit PHY. 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. The sk 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 the /etc/rc.conf file. 1000baseTX Set 1000baseTX operation over twisted pair. This is only available for SK-982x series adapters with 1000baseT ports. Both full-duplex and half-duplex modes are supported. 1000baseSX Set 1000Mbps (Gigabit Ethernet) operation. Both full-duplex and half-duplex modes are supported. The sk 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 sk driver include: o 3Com 3C940 single port, 1000baseT adapter o 3Com 3C2000-T single port, 1000baseT adapter o Belkin F5D5005 single port, 1000baseT adapter o D-Link DGE-530T single port, 1000baseT adapter o Linksys (revision 2) single port, 1000baseT adapter o SK-9521 SK-NET GE-T single port, 1000baseT adapter o SK-9821 SK-NET GE-T single port, 1000baseT adapter o SK-9822 SK-NET GE-T dual port, 1000baseT 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 SMC 9452TX single port, 1000baseT adapter LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.skc.jumbo_disable Disable jumbo frame support. Systems with less memory can set it to a non-zero value to save memory. The default value is 0. SYSCTL VARIABLES
The following variable is available as both sysctl(8) variable and loader(8) tunable: dev.skc.%d.int_mod This variable controls interrupt moderation. The accepted range is 10 to 10000. The default value is 100 microseconds. The inter- face has to be brought down and up again before a change takes effect. 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: no memory for softc struct! The driver failed to allocate memory for per-device instance information during initialization. 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
altq(4), arp(4), miibus(4), netintro(4), ng_ether(4), vlan(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. AUTHORS
The sk driver was written by Bill Paul <wpaul@ctr.columbia.edu>. BSD
November 23, 2010 BSD
All times are GMT -4. The time now is 06:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy