[c-nsp] bad GBICs?

Greg Schwimer gschwimer at godaddy.com
Sat Apr 30 12:39:40 EDT 2005


I've been seeing bad GBICs and SFPs of all types lately.  I'm guessing
about 15-20% infant mortality lately.  No complaints about eeprom, they
just don't work.


> -------- Original Message --------
> Subject: [c-nsp] bad GBICs?
> From: "Daniel Medina" <medina at columbia.edu>
> Date: Fri, April 29, 2005 2:40 pm
> To: cisco-nsp at puck.nether.net
> 
> We frequently receive bad long haul GBIC and SFP transceivers,
> specifically WS-G5486 and GLC-LH-SM.  The Catalyst error messages that
> appears in the switch log complains that the GBICs have bad EEPROM.
> 
>     %C4K_GBICMAN-3-BADGBIC: Port Gi2/1: Gbic's seeprom is bad, try
>      reinserting: vendor: CISCO-AGILENT, p/n: WS-G5486, s/n:...
> 
>  We've seen this on Cat4000+12.2(25)EW, as well as on 3750s.  The GBICs
> have also failed after working for some short period of time (resulting
> in outages).
> 
>  Just wondering if this is a known issue, and/or is there a known batch
> of bad hardware out there?  The last 50-75 transceivers we have
> purchased have yielded about a dozen bad ones.
> 
>  I've seen
> 
>     GBIC EEPROM Errors Incorrect in Cisco IOS
>     http://www.cisco.com/en/US/products/hw/switches/ps700/products_field_notice09186a00800fd312.shtml
> 
> but these errors are not cosmetic.
> 
>  Looking through a bag of failed GBICs here I see they are all serials
> A009716## (WS-G5486 1000BASE-LX).
> 
> -- 
> Daniel Medina
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list