| View previous topic :: View next topic |
| Author |
Message |
brainscan
n00b
Joined: 17 Aug 2006
Posts: 7
|
 Posted: Sun Apr 08, 2007 11:01 am Post subject: 3COM 3C905b-FX wrong media type? |
 |
|
Hi!
i'm having a little problem, i have 2 network cards:
00:10.0 Ethernet controller: 3Com Corporation 3c905B-FX Fast Etherlink XL FX 100baseFx [Cyclone]
00:11.0 Ethernet controller: 3Com Corporation 3c905B-FX Fast Etherlink XL FX 100baseFx [Cyclone]
and when i run ethtool for interfaces eth0 and eth1, the results are this:
| Code: |
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised auto-negotiation: No
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Current message level: 0x00000001 (1)
Link detected: yes
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised auto-negotiation: No
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Current message level: 0x00000001 (1)
Link detected: yes
|
booth cards are connected to a cisco 2900XL in 2 fiber-ports, but in the switch the ports the status are:
| Code: |
FastEthernet1/1 is up, line protocol is up
Hardware is Fast Ethernet, address is 0002.b9c0.cede (bia 0002.b9c0.cede)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 100Mb/s
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 1000 bits/sec, 2 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1812853 packets input, 337803985 bytes
Received 65 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 6 multicast
0 input packets with dribble condition detected
2977148 packets output, 1541065434 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
FastEthernet1/2 is up, line protocol is up
Hardware is Fast Ethernet, address is 0002.b9c0.cedf (bia 0002.b9c0.cedf)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 100Mb/s
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:46, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 1 packets/sec
5 minute output rate 2000 bits/sec, 1 packets/sec
3918 packets input, 456924 bytes
Received 14 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 6 multicast
0 input packets with dribble condition detected
419876 packets output, 22214181 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
|
however I have configured the 2 cards to do etherchannel, so i made the bonding configuration.
put this line in "/etc/modules.autoload.d/kernel-2.6"
bonding miimon=100 mode=0 max_bonds=1
the ifconfig result is:
| Code: |
bond0 Link encap:Ethernet HWaddr 00:10:5A:10:03:FD
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:10268 errors:0 dropped:0 overruns:0 frame:0
TX packets:8885 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:948356 (926.1 Kb) TX bytes:1011140 (987.4 Kb)
eth0 Link encap:Ethernet HWaddr 00:10:5A:10:03:FD
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:2033 errors:0 dropped:0 overruns:0 frame:0
TX packets:4552 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:167345 (163.4 Kb) TX bytes:535708 (523.1 Kb)
Interrupt:17 Base address:0x4f80
eth1 Link encap:Ethernet HWaddr 00:10:5A:10:03:FD
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:8249 errors:0 dropped:0 overruns:0 frame:0
TX packets:4346 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:782219 (763.8 Kb) TX bytes:477340 (466.1 Kb)
Interrupt:18 Base address:0xcf00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:35 errors:0 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3032 (2.9 Kb) TX bytes:3032 (2.9 Kb)
|
so, for now, network is working (i guess), but when if 1 connection goes down, sometimes in ping i get some packets lots, even worst if I disconnect the first card, it takes long to get the network work without problems, anyway, the cards declare that are runing in 10Mb/s in half-duplex when in cisco switch are in 100Mb/s in full-duplex 
BTW, i'm using the standard gentoo linux kernel 2.6.19-gentoo-r5 in SMP mode without any tweaks to avoid any possible problem...
i'm missing something here?
thanks for your attention,
NBA |
|
| Back to top |
|
 |
erik258
Advocate
Joined: 12 Apr 2005
Posts: 2650
Location: Twin Cities, Minnesota, USA
|
| Posted: Fri Apr 13, 2007 4:16 pm Post subject: |
|
|
I just stumbled across your post. How's it going now? Still the same problems? I borrowed the following mode descriptions from http://www.linuxhorizon.ro/bonding.html :
| Quote: |
mode=0 (balance-rr)
Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.
mode=1 (active-backup)
Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode.
mode=2 (balance-xor)
XOR policy: Transmit based on [(source MAC address XOR'd with destination MAC address) modulo slave count]. This selects the same slave for each destination MAC address. This mode provides load balancing and fault tolerance.
mode=3 (broadcast)
Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.
mode=4 (802.3ad)
IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification.
Pre-requisites:
1. Ethtool support in the base drivers for retrieving
the speed and duplex of each slave.
2. A switch that supports IEEE 802.3ad Dynamic link
aggregation.
Most switches will require some type of configuration
to enable 802.3ad mode.
mode=5 (balance-tlb)
Adaptive transmit load balancing: channel bonding that does not require any special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave.
Prerequisite:
Ethtool support in the base drivers for retrieving the
speed of each slave.
mode=6 (balance-alb)
Adaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server.
The most used are the first four mode types... |
Have you tried any other modes? You probably have to use one that the CISCO supports. I have had similar problems with mode 0 and mode 2. I have cheap switches and cheap tulip-based network cards, and I couldn't get mode 6 (which sounds really nice) working. I use mode 5 right now, which works even on this kind of crummy hardware.
_________________
Configuring a Firewall? Try my iptables configuration
LinuxCommando.com is my blog for linux-related scraps and tidbits. Stop by for a visit! |
|
| Back to top |
|
|
brainscan
n00b
Joined: 17 Aug 2006
Posts: 7
|
| Posted: Fri Apr 13, 2007 8:00 pm Post subject: |
|
|
Hi erik258,
the problem is not directly with the bonding driver, cause i'm using a cisco switch 2900XL with etherchannel enabled in 2 fiber-ports, the problem is the 3c59x driver using ethtool or mii-diag, they are telling me that the 2 cards 3COM 3C905B-FX are using 10baseT in half-duplex mode and the switch reports 100mbs in full-duplex, anyway the network... works (i guess) but the 2 tools telling me wrong media types for the 2 3COM cards just bothers me, because i guess that bonding will not work correctly if 1 link fails and don't recover from the other...
i did some tests disconnecting 1 link, than the other, and reversed order, they take too much time to get up and running... like 10sec or more...
and by the way, getting information from the driver using MII port not even work...
Anyone has used 3COM 3C905B-FX cards? even not using any bonding drivers... please, make some comment here if it works ok, and if it is detected correctly with mii-diag and ethtool.
thanks for your attention,
best regards,
NBA |
|
| Back to top |
|
|
erik258
Advocate
Joined: 12 Apr 2005
Posts: 2650
Location: Twin Cities, Minnesota, USA
|
| Posted: Fri Apr 13, 2007 8:46 pm Post subject: |
|
|
one more thought, I've heard often that auto-negotiation can be tricky. Evidently it doesn't work too well. you may want to try disabling it and setting the speed manually/.
_________________
Configuring a Firewall? Try my iptables configuration
LinuxCommando.com is my blog for linux-related scraps and tidbits. Stop by for a visit! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
