Hi, is this crossbow feature:
Jan 12 16:09:06 xxxxx bnx: [ID 328528 kern.info] NOTICE: bnx0: Copper link is up
(100Mbps, Full Duplex)
root at xxxxx:~# ifconfig bnx0
bnx0: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 10
inet 0.0.0.0 netmask ff000000
ether 0:24:e8:40:20:2f
root at nbl-istorage7.pit.hel:~# dladm show-link bnx0
LINK CLASS MTU STATE BRIDGE OVER
bnx0 phys 1500 down -- --
Switch and rest of system says link is up but dladm shows it isn''t?
This is random event occurring on dell R710 servers causing networking to stall
and this is escalated to Sun and Dell atm.
This occurs on snv_123->
Any thoughts?
Yours
Markus Kovero
Nebula Oy
Hi Markus, On Wed, 2010-01-13 at 08:19 +0200, Markus Kovero wrote:> Hi, is this crossbow feature: > > Jan 12 16:09:06 xxxxx bnx: [ID 328528 kern.info] NOTICE: bnx0: Copper link is up (100Mbps, Full Duplex)It''s printed by bnx driver to show the link is up.> > root at xxxxx:~# ifconfig bnx0 > bnx0: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 10 > inet 0.0.0.0 netmask ff000000 > ether 0:24:e8:40:20:2fWhile this line shows it''s not connected to wire. It should contain a "RUNNING" state when connect to a host/network.> > root at nbl-istorage7.pit.hel:~# dladm show-link bnx0 > LINK CLASS MTU STATE BRIDGE OVER > bnx0 phys 1500 down -- --Not connected to wire?> > Switch and rest of system says link is up but dladm shows it isn''t?Can you use command "snoop -r -d bnx0" to see if there is any traffic?> > This is random event occurring on dell R710 servers causing networking to stall and this is escalated to Sun and Dell atm. > This occurs on snv_123->This interface doesn''t have IP, so it''s not configured. Did you see this issue on an configured interface? Regards, Crisson> > Any thoughts? > > Yours > Markus Kovero > Nebula Oy > > _______________________________________________ > crossbow-discuss mailing list > crossbow-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss
Hi, it is connected to wire and switch thinks link should be up and running, it even negotiates between 1000/100 full/half duplex alright. After assigning ip to interface its no different, I see no traffic on interface (except when I ping it''s ip) There are other interfaces on system using bnx-driver and these work very well, is here any way to debug whats going on with bnx0? Yours Markus Kovero -----Original Message----- From: Crisson.Hu at Sun.COM [mailto:Crisson.Hu at Sun.COM] Sent: 13. tammikuuta 2010 8:32 To: Markus Kovero Cc: crossbow-discuss at opensolaris.org; networking-discuss at opensolaris.org Subject: Re: [crossbow-discuss] bnx and crossbow? Hi Markus, On Wed, 2010-01-13 at 08:19 +0200, Markus Kovero wrote:> Hi, is this crossbow feature: > > Jan 12 16:09:06 xxxxx bnx: [ID 328528 kern.info] NOTICE: bnx0: Copper link is up (100Mbps, Full Duplex)It''s printed by bnx driver to show the link is up.> > root at xxxxx:~# ifconfig bnx0 > bnx0: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 10 > inet 0.0.0.0 netmask ff000000 > ether 0:24:e8:40:20:2fWhile this line shows it''s not connected to wire. It should contain a "RUNNING" state when connect to a host/network.> > root at xxxxx:~# dladm show-link bnx0 > LINK CLASS MTU STATE BRIDGE OVER > bnx0 phys 1500 down -- --Not connected to wire?> > Switch and rest of system says link is up but dladm shows it isn''t?Can you use command "snoop -r -d bnx0" to see if there is any traffic?> > This is random event occurring on dell R710 servers causing networking to stall and this is escalated to Sun and Dell atm. > This occurs on snv_123->This interface doesn''t have IP, so it''s not configured. Did you see this issue on an configured interface? Regards, Crisson> > Any thoughts? > > Yours > Markus Kovero > Nebula Oy > > _______________________________________________ > crossbow-discuss mailing list > crossbow-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss
Markus Kovero wrote:> Hi, it is connected to wire and switch thinks link should be up and running, it even negotiates between 1000/100 full/half duplex alright. > After assigning ip to interface its no different, I see no traffic on interface (except when I ping it''s ip) > There are other interfaces on system using bnx-driver and these work very well, is here any way to debug whats going on with bnx0?You should probably file a bug on it via bugs.opensolaris.org. bnx, I believe, is a third-party driver, and I don''t know if there''s much in the way of representation on the mailing lists. The lack of a RUNNING flag in the ifconfig output and the dladm output are consistent with each other: they both say that, as far as the OS can tell, the link is disconnected. It has no link status. I would look at "kstat bnx" to see if there are any useful statistics there, and I would also try swapping cables and using different switch ports before spending too much time trying to debug the software. -- James Carlson 42.703N 71.076W <carlsonj at workingcode.com>
Hi, thanks for reply, it is filed as CR6916413. After speaking with dell it seems it might be firmware-related issue. Yours Markus Kovero> You should probably file a bug on it via bugs.opensolaris.org. bnx, I > believe, is a third-party driver, and I don''t know if there''s much in > the way of representation on the mailing lists. > > The lack of a RUNNING flag in the ifconfig output and the dladm output > are consistent with each other: they both say that, as far as the OS can > tell, the link is disconnected. It has no link status. > > I would look at "kstat bnx" to see if there are any useful statistics > there, and I would also try swapping cables and using different switch > ports before spending too much time trying to debug the software. > > -- > James Carlson 42.703N 71.076W <carlsonj at workingcode.com>