It might be the case that MIIMon is not supported. From RHEL 6 Deployment guide (section about bonding directives, page 399): Specifies (in milliseconds) how often MII link monitoring occurs. This is useful if high availability is required because MII is used to verify that the NIC is active. To verify that the driver for a particular NIC supports the MII tool, type the following command as root: ~]# ethtool <interface_name> | grep "Link detected:" In this command, replace <interface_name> with the name of the device interface, such as eth0, not the bond interface. If MII is supported, the command returns: Link detected: yes Kind Regards, -- Paul Preston Proxar IT Ltd. Registered in England and Wales: 6744401- VAT: 942985479 Tubs Hill House, London Road, Sevenoaks, Kent, TN13 1BL Tel: (+44) 0844 809 4335 Fax: (+44) 01732 459 423 Mob: (+44) 077 9509 3450 Web: www.proxar.co.uk Email: paul.preston@xxxxxxxxxxxx -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Allen Chen Sent: 01 March 2011 16:18 To: General Red Hat Linux discussion list Subject: Re: ethtool - Link detected: no nani wrote: > Check with the Network team, from switch side what will be the > settings like 100 base full duplex and through ethtool command set > those values > > and see you will get the link detected = yes > > > > On Mon, Feb 28, 2011 at 3:01 PM, Parvez Shaikh <parvez.h.shaikh@xxxxxxxxx>wrote: > > >> Hi all, >> >> When I run ethtool against ethernet card, I get following output - >> >> [root@datablade1 ~]# ethtool eth3 >> Settings for eth3: >> Supported ports: [ FIBRE ] >> Supported link modes: 1000baseT/Full >> Supports auto-negotiation: Yes >> Advertised link modes: 1000baseT/Full >> Advertised auto-negotiation: Yes >> Speed: Unknown! >> Duplex: Unknown! (255) >> Port: FIBRE >> PHYAD: 2 >> Transceiver: internal >> Auto-negotiation: on >> Supports Wake-on: g >> Wake-on: g >> * Link detected: no* >> >> Note "Link detected: no"; what does it mean? >> >> When I do ethtool -t eth3, I get following output - >> >> [root@datablade1 ~]# ethtool -t eth3 >> *The test result is FAIL* >> The test extra info: >> register_test (offline) 0 >> memory_test (offline) 0 >> loopback_test (offline) 0 >> nvram_test (online) 0 >> interrupt_test (online) 0 >> link_test (online) 1 >> >> Note "*The test result is FAIL", *somehow I believe the above two >> outputs are interlinked (the test result is FAIL because link detected is 'No'). >> >> How to fix this to make test result pass and link detected to 'Yes'? >> For other ethernet card I can see the test result passing and link >> detected is 'Yes' >> >> Thanks >> Parvez >> -- >> redhat-list mailing list >> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >> https://www.redhat.com/mailman/listinfo/redhat-list >> >> You can try to update the latest firmware on those network cards. I have a HS20 blade, and I use bonding to do the failover. for somehow, "Link detected" is not stable(it's stable if I remove bonding). After I updated it to the latest firmware, "Link detected" is stable. and bonding is working fine. Allen -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list Please note that we may monitor or record telephone calls, email traffic data and also the content of email for the purposes of security and staff training. This message (and any associated files or documentation) is intended only for the use of the individual or entity to whom it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files and documentation associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company. -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
