Unsolved
This post is more than 5 years old
4 Posts
0
41012
June 25th, 2015 23:00
8132F optical SFP not recognised after firmware upgrade
Hi Dell Community,
I had a pair of PowerConnect 8132F switches running firmware 5.1.2.3. Around a week ago I wanted to connect a new server, so I plugged in a new SFP optical transceiver to switch 1 and went to enable it, but the management software crashed. I scheduled down time, reset the switch by disconnecting its power, and updated the system firmware to 6.2.1.6 following Dell's instructions. Seemed to go smoothly although there were somee console messages complaining about port configuration. The switch management pauses sometimes when I issue a command but it hasn't crashed yet. The real problem is that the new optical SFP doesn't work and neither does the one that was already connected and working previously. Most of the switch ports are connected with Twinax cable and they are working fine.
sw1#show fiber-ports optical-transceiver
No interface with a pluggable module that supports fiber diagnostics found.
The working ports are all connected with Dell Twinax Cable with SFP+ Connector, the optical ports are using Dell DP/N 0WTRD1 FTLX8571D3BCL-FC GP-10GSFP-1S 10GB SFP+ 850nm Transcivers.
The second switch, same model, same SFP transceivers but still on 5.1.2.3 firmware is working as expected.
sw2#show fiber-ports optical-transceiver
Output Input
Port Temp Voltage Current Power Power TX LOS
[C ] [Volt] [mA] [dBm] [dBm] Fault
-------- ---- ------- ------- ------- ------- ----- ---
Te1/0/19 46.5 3.356 7.9 -2.558 -2.094 No No
Te1/0/20 46.4 3.307 8.5 -2.350 -2.311 No No
I'm not sure what I should do next except perhaps go back to the older firmware? But I suspect switch 1 may have a fault that isn't firmware related. Any advice?
lucasjb
4 Posts
0
June 28th, 2015 21:00
Hi Daniel, thanks for your reply. Logging shows these messages which I think were the same as shown on the console during boot:
<188> Jun 24 18:55:33 sw1 TRAPMGR[trapTask]: traputil.c(735) 1291 %% INSERT_OPTICS: Optics SFP inserted in Te1/0/19
<187> Jun 24 18:55:33 sw1 BOXSERV[boxs Req]: boxs.c(1430) 1272 %% 1/0/19 Port programming failed with error 0x1 for event OPERATIONAL. Port may not be Up.
Same for port 20. The port configurations are very simple:
interface Te1/0/19
spanning-tree disable
mtu 9216
switchport general pvid 163
switchport access vlan 163
exit
I'll try unplug and reconnect the SFP and watch the console later today to check it's the same message.
lucasjb
4 Posts
0
June 29th, 2015 00:00
OK I tried removing and re-inserting the SFP in Te1/0/19 which caused the switch management to stop responding (it eventually seemed to come back to life several minutes later, but logging doesn't record anything about this event). I removed the optical SFPs from sw1 and installed them in sw2 where they were immediately recognised. I'm starting to be more and more convinced that sw1 has a fault.
lucasjb
4 Posts
0
July 6th, 2015 22:00
Thanks again Daniel C, just had time to come back to this issue. Ports 17 and 18 seem to recognise the SFP, ports 19 and 20 do not. I can't test any others. 19 and 20 were the ports with optical transceivers installed the first time the switch crashed. The management software still hangs for a while at random but so far it has always recovered. I wonder if there's some way to reset a port?