BD 8810 does not recognize Extreme XFP

[HarrySo]

Hi Experts!

We have two BD8810 with 10G8Xc modules installed. Now we have the Problem, that some of the inserted XFPs are not recognized. They are marked as !Unknown.

This happens with FW 15.7, 15.6.2.12, 15.5.4.2.

Has anyone seen this on Extreme devices?

[EtherMan-Dupe]

It for sure can be safely ignored till they get this fixed in a future patch... we discovered this bug over a year ago on our 8900's and have had no service or performance issues with the blades reporting the xfp's as "unknown"... It is annoying but ok..

[OscarK]

Hi, I think the !XFP is the issue I mentioned in my first reply, this will be fixed in 15.7.2 that will come out soon.

[HarrySo]

so i've changed the XFP's, an i'm getting more confused!

2:6 --> 1:5, the Status goes from !UNKN to !XFP_SR

i've placed a "new" used XFP in port 1:6, an it's marked as !XFP_SR

the XFP from port 1:6 went's to port 1:4 and stays in Status !UNKN

and finaly, the now empty Slot 2:6 shows the Status !NONE

FW 15.7.1.4 patch 1-1

================================================================================
1:1 VR-Default E A OFF 10000 10000 FULL FULL NONE 1:1 XFP_SR
1:2 VR-Default E A OFF 10000 10000 FULL FULL NONE 1:2 XFP_SR
1:3 VR-Default E R OFF 10000 FULL 1:3 NONE
1:4 VR-Default E R OFF 10000 FULL 1:4 !UNKN
1:5 VR-Default E R OFF 10000 FULL !XFP_SR
1:6 VR-Default E A OFF 10000 10000 FULL FULL NONE !XFP_SR
1:7 VR-Default E A OFF 10000 10000 FULL FULL NONE 1:7 XFP_SR
1:8 VR-Default E A OFF 10000 10000 FULL FULL NONE 1:8 XFP_SR
2:1 VR-Default E A OFF 10000 10000 FULL FULL NONE 1:1 XFP_SR
2:2 VR-Default E A OFF 10000 10000 FULL FULL NONE 1:2 XFP_SR
2:3 VR-Default E R OFF 10000 FULL 1:3 NONE
2:4 VR-Default E R OFF 10000 FULL 1:4 NONE
2:5 VR-Default E R OFF 10000 FULL NONE
2:6 VR-Default E R OFF 10000 FULL !NONE
2:7 VR-Default E A OFF 10000 10000 FULL FULL NONE 1:7 XFP_SR
2:8 VR-Default E A OFF 10000 10000 FULL FULL NONE 1:8 XFP_SR
================================================================================

[Firas_Ayoub]

Harry So, an output of !UNKN may very well indicate corruption in the data retrieved from EEPROM. I would suggest moving that XFP to another port to see if the problem follows it or stays on the port, if the problem follows the device, then you will know that is is broken and you could try replacing it.