Wrong "operstate" status on Emulex OneConnect card using be2net on Red Hat Enterprise Linux 5.8.
Issue
- The
operstate
of some of the 10GbE interfaces are incorrect. The interfaces are online and working (traffic is passing), but still the operstate isunknown
.
Eg:
# cat /proc/net/bonding/bond*
Ethernet Channel Bonding Driver: v3.4.0-1 (October 7, 2008)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer3+4 (1)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
802.3ad info
LACP rate: slow
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 2
Actor Key: 33
Partner Key: 32794
Partner Mac Address: 00:23:04:ee:be:88
Slave Interface: eth0
MII Status: up <<<
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:00:c9:bb:06:44
Aggregator ID: 1
Slave Interface: eth3
MII Status: up <<<
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:00:c9:b6:f0:22
Aggregator ID: 1
# cat /sys/class/net/eth{0,3}/operstate
unknown <<<
unknown <<<
Environment
- Red Hat Enterprise Linux 5.8
- Kernel-2.6.18-308
- Kernel-2.6.18-308.11.1
- Emulex OneConnect card
- be2net
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.