Unsolved
This post is more than 5 years old
16 Posts
0
20727
December 9th, 2010 06:00
Failed to recover link status
I upgraded from 2.2.0.3 to 3.2.0.9 yesterday and now I'm seeing the following errors in the log. I have a stack of three PowerConnect 6248P switches with fiber connection to other PowerConnect 3xxx series switches.
I didn't receive the errors until I upgraded and I can't find any information on the errors anywhere.
| 1021 | 24809 | Error | DEC 09 09:45:54 | DRIVER | Port ge0: Failed to recover link status: Operation still running |
| 1022 | 24810 | Error | DEC 09 09:45:54 | DRIVER | Port ge0: Failed to recover link status: Operation still running |
| 1023 | 24811 | Error | DEC 09 09:45:55 | DRIVER | Port ge0: Failed to recover link status: Operation still running |
| 1024 | 24812 | Error | DEC 09 09:45:55 | DRIVER | Port ge0: Failed to recover link status: Operation still running |
| 1025 | 24813 | Error | DEC 09 09:45:56 | DRIVER | Port ge0: Failed to recover link status: Operation still running |
| 1026 | 24814 | Error | DEC 09 09:45:56 | DRIVER | Port ge0: temporarily removed from linkscan |
| 1027 | 24815 | Error | DEC 09 09:46:06 | DRIVER | Port ge0: Failed to recover link status: Operation still running |
| 1028 | 24816 | Error | DEC 09 09:46:07 | DRIVER | Port ge0: Failed to recover link status: Operation still running |
| 1029 | 24817 | Error | DEC 09 09:46:07 | DRIVER | Port ge0: Failed to recover link status: Operation still running |
| 1030 | 24818 | Error | DEC 09 09:46:08 | DRIVER | Port ge0: Failed to recover link status: Operation still running |
| 1031 | 24819 | Error | DEC 09 09:46:08 | DRIVER | Port ge0: Failed to recover link status: Operation still running |
| 1032 | 24820 | Error | DEC 09 09:46:08 | DRIVER | Port ge0: temporarily removed from linkscan |
No Events found!
bh1633
909 Posts
0
December 9th, 2010 16:00
Please post your config and any other information you think is relevant.
dyelton
16 Posts
0
December 13th, 2010 03:00
See attached for the running-config.
1 Attachment
running-config.txt
wgrayatBayPath
1 Message
0
December 15th, 2010 06:00
I am experiencing the same issue here. Getting ready to deploy a stack of 2 new PowerConnect 6248/6248P switches and am getting these errors on the console port. Have other 6248 series switches with 2.2.0.3 and 3.2.0.7 and have never seen this error before.
SMAA_IT
1 Message
0
January 5th, 2011 21:00
I'm also experiences the same problem. How do we go about resolving it?
68339
Error JAN 06 15:12:41 DRIVER Port ge0: Failed to recover link status: Operation still running
68340
Error JAN 06 15:12:42 DRIVER Port ge0: Failed to recover link status: Operation still running
68341
Error JAN 06 15:12:46 DRIVER Port ge0: Failed to recover link status: Operation still running
68342
Error JAN 06 15:12:47 DRIVER Port ge0: Failed to recover link status: Operation still running
68343
Error JAN 06 15:12:48 DRIVER Port ge0: Failed to recover link status: Operation still running
68344
Error JAN 06 15:12:50 DRIVER Port ge0: Failed to recover link status: Operation still running
68345
Error JAN 06 15:12:50 DRIVER Port ge0: Failed to recover link status: Operation still running
68346
Error JAN 06 15:12:51 DRIVER Port ge0: Failed to recover link status: Operation still running
68347
Error JAN 06 15:12:51 DRIVER Port ge0: Failed to recover link status: Operation still running
68348
Error JAN 06 15:12:55 DRIVER Port ge0: Failed to recover link status: Operation still running
68349
Error JAN 06 15:12:56 DRIVER Port ge0: Failed to recover link status: Operation still running
68350
Error JAN 06 15:12:56 DRIVER Port ge0: Failed to recover link status: Operation still running
68351
Error JAN 06 15:12:57 DRIVER Port ge0: Failed to recover link status: Operation still running
Richie.G
1 Message
0
January 18th, 2011 11:00
Not sure whether this error is having any sort of negative effect on performance, or are these errors strictly just an annoyance and an eye sore until the next firmware is released? :emotion-40:
Any luck?
Thx.
bh1633
909 Posts
0
January 24th, 2011 13:00
FW version 3.2.1.3 was posted to the website on Friday the 21st and fixes this issue as well as several other bugs.
http://support.dell.com/support/downloads/format.aspx?c=us&cs=555&l=en&s=biz&deviceid=12747&libid=5&releaseid=R294647&vercnt=12&formatcnt=0&SystemID=PWC_6224&servicetag=&os=WNET&osl=en&catid=-1&dateid=-1&typeid=-1&formatid=-1&impid=-1&checkFormat=true