- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2014 04:44 AM - edited 03-07-2019 05:27 PM
there is any reasons for switch port sfp module going to err-disable state
Solved! Go to Solution.
- Labels:
-
Other Switching
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2014 06:40 AM
Which is the model number of the SFP you are using?
The following error suggests the switch does not support that module, is it a 3rd party one?
%PM-4-ERR_DISABLE: gbic-invalid error detected on Gi0/1, putting Gi0/1 in err-disable state
I 'think' Catalyst switches can have problems with third party SFP's so it may be worth doing the following to make the SFP work:
no errdisable detect cause gbic-invalid
service unsupported-transceiver

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2014 04:47 AM
Can you post "show errdisable cause"?
HTH,
John
*** Please rate all useful posts ***
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2017 06:37 AM
hope you can help me
facing the same issue in Cisco WS-C3560-48TS-S
LQZNL-OFFICE-SW#show
ALQZNL-OFFICE-SW#show
ErrDisable Reason Detection Mode
----------------- --------- ----
arp-inspection Enabled port
channel-
community-limit Enabled port
inline-power Enabled port
invalid-policy Enabled port
l2ptguard Enabled port
link-flap Enabled port
loopback Enabled port
mac-limit Enabled port
port-mode-failure Enabled port
security-violation Enabled port
small-frame Enabled port
storm-control Enabled port
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2014 04:50 AM
could you paste the logs ? , sh log
the reason must be there itself
for example:
%PM-SP-4-ERR_DISABLE: udld error detected on Gix/y, putting Gi x/y in err-disable state
, so here the reason would be udld .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2014 06:22 AM
1 has bad crc
%PM-4-ERR_DISABLE: gbic-invalid error detected on Gi0/1, putting Gi0/1 in err-disable state
%LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
%PM-4-ERR_RECOVER: Attempting to recover from gbic-invalid err-disable state on Gi0/1
%GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi0/1 has bad crc
%PM-4-ERR_DISABLE: gbic-invalid error detected on Gi0/1, putting Gi0/1 in err-disable state
%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
%LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
%LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up
%PM-4-ERR_RECOVER: Attempting to recover from gbic-invalid err-disable state on Gi0/1
%LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to administratively down
%LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
%LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to administratively down
%LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
%LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
%LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
%LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
%LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
INEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
%LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
%LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2014 06:40 AM
Which is the model number of the SFP you are using?
The following error suggests the switch does not support that module, is it a 3rd party one?
%PM-4-ERR_DISABLE: gbic-invalid error detected on Gi0/1, putting Gi0/1 in err-disable state
I 'think' Catalyst switches can have problems with third party SFP's so it may be worth doing the following to make the SFP work:
no errdisable detect cause gbic-invalid
service unsupported-transceiver
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2014 11:48 PM
Hi devils,
yes your right,
im using non cisco tx:1310nm rx:1550nm module.
i changed the gig port in other side switch(Gi3 to Gi4), now its working..
and i used that
no errdisable detect cause gbic-invalid
command..
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2014 11:11 AM
Thanks for the command post. This resolve the issue I was having also until we can get a new SFP put in.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2023 10:06 AM
I had the same problem, i changed the SFP and that resolved the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2021 11:00 PM - edited 08-17-2021 11:01 PM
This worked for me.
If multiple interfaces are in this state then we have to use this command once on one of the interfaces and simply reset the other interfaces.
