[c-nsp] GBIC error message, any clue? (cpd_port_enable: port 25 xcvr_enable_link: FALSE)

[Michael K. Smith - Adhost]

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Alexander Koch
Sent: Saturday, November 26, 2005 2:42 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] GBIC error message,any clue? (cpd_port_enable: port 25
xcvr_enable_link: FALSE)

The GBIC on this 2950 is killing me. Saying shut/ no shut
gets it into error-disabled immediately. I had to say
'speed nonegotiate' to bring this one up. Anyone seen these
scary messages before?

Regards,
Alexander

Nov 26 10:43:33: %LINEPROTO-5-UPDOWN: Line protocol on
Interface GigabitEthernet0/2, changed state to up
Nov 26 10:43:35: %LINEPROTO-5-UPDOWN: Line protocol on
Interface GigabitEthernet0/2, changed state to down
Nov 26 10:43:36: %PM-4-ERR_DISABLE: link-flap error detected
on Gi0/2, putting Gi0/2 in err-disable statecpd_port_enable:
port 25 xcvr_enable_link: FALSE
Nov 26 10:43:44: %SYS-5-CONFIG_I: Configured from console by
vty0 (213.200.88.76)
Nov 26 10:43:46: %PM-4-ERR_DISABLE: link-flap error detected
on Gi0/2, putting Gi0/2 in err-disable state
Nov 26 10:47:03: %LINK-5-CHANGED: Interface
GigabitEthernet0/2, changed state to administratively
downcpd_port_enable: port 25 xcvr_enable_link: FALSE

<end>

Hello Alexander:

I haven't seen that error specifically and CCO is of no help, but I've seen
the link-flap errors before.  The speed nonegotiate command just means you
are hard-setting speed and duplex settings for the interface.  I've never
seen a duplex-mismatch cause an error-disable; normally the interface won't
come up.  So, I would look for physical layer issues with the connected
fiber or the seating of the GBIC in the chassis itself.  Are you seeing any
other interface errors such as CRC's?

Mike