[c-nsp] WS-G5486 GBIC faulty Tx laser

[John Brown]

Dirty connectors?
Connector not fully seated in GBIC/SFP?
   Problem went away when you mechanically exercised the links ?

Did you take the DUT (device under test) and put it back into the same scenario where it was failing to see if the failure continues ?
If the failure didn't continue then I would suspect a "bumped fiber/connector not seated properly" 
If the failure did continue, then maybe the GBIC slot has an issue.

Could also be that the DIQ wasn't fully seated in the cage....

Any other work on the chassis the DIQ was failing in ?



> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of Martin T
> Sent: Saturday, January 21, 2012 7:52 AM
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] WS-G5486 GBIC faulty Tx laser
> 
> Has anyone experienced a situation where GBIC occasionally does not
> transmit properly with required power? I had a WS-G5486 GBIC in WS-X4306-
> GB module connected to a SFP in another switch and all of the sudden link
> started to flap with 4-6min intervals. It had been stable for years. Rx power at
> the SFP end was very low(SFP had a DOM support). I replaced the GBIC with
> another one(link came up instantly and become stable) and tested the
> problematic GBIC in another switch(same model and module) and GBIC
> transmits with nominal
> power(-6dBm) and links with another SFP just fine. What bothers me the
> most is that in the second switch the problematic GBIC seems to works as
> good as ever. Any experience with similar occasions?
> 
> 
> regards,
> martin
> _______________________________________________
> 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/