SFP GLC-T in C3750

Unanswered Question

We cannot get our Cisco Systems SFP GLC-T GBIC modules to work in any of our C3750s. We are running SW versions greater than the required minimum.


When inserted, the entire GB bus recycles (bouncing network connections for any other GBIC modules in the switch) and then err-disables the port it's in and in other empty GB ports.



Hardware information:

Cisco Systems

GLC-T

30-1410-02

MTC008405



Logged messages on C3750 running SW version 12.2(25)SEE3:

Jan 22 12:00:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet

1/0/2, changed state to down

Jan 22 12:00:09: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state t

o down

Jan 22 12:00:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet

1/0/3, changed state to down

Jan 22 12:00:37: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state t

o down

Jan 22 12:00:39: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state t

o up

Jan 22 12:00:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet

1/0/3, changed state to up

Jan 22 12:01:08: %PHY-4-MODULE_DUP: SFPs in Gi1/0/2 and in Gi1/0/4 have duplicat

e vendor-id and serial numbers

Jan 22 12:01:08: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/2, putt

ing Gi1/0/2 in err-disable state

Jan 22 12:01:08: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/4, putt

ing Gi1/0/4 in err-disable state

Jan 22 12:01:09: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet

1/0/4, changed state to down

Jan 22 12:01:10: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/4, changed state t

o down



Logged messages on C3750 running SW version 12.2(25)SEB4:

0:05:206158430208: %SYS-3-CPUHOG: Task is running for (2097)msecs, more than (2

000)msecs (0/0),process = hpm main process.

-Traceback= 4A2B80 4A2B60 50B6A4 50BA0C 50BC88 5030C0 5036DC 501000 253824 5028E

4 5043C4 5025E0 254CBC 47C2B8 47B820 7599A8

00:05:214798696448: %SYS-3-CPUHOG: Task is running for (4194)msecs, more than (2

000)msecs (0/0),process = hpm main process.

-Traceback= 4A6874 4A2B60 4A2BE0 50B6A4 50BA0C 50BC88 5030C0 5036DC 501000 253A6

8 5028E4 3094F8 504408 5025E0 254CBC 47C2B8

00:05:223388631040: %SYS-3-CPUHOG: Task is running for (6291)msecs, more than (2

000)msecs (0/0),process = hpm main process.

-Traceback= 4A2B5C 4A2BE0 50B6A4 50BA0C 50BC88 5030C0 5036DC 501000 253A68 5028E

4 3094F8 504408 5025E0 254CBC 47C2B8 47B820




Are there known problems with this GBIC module?


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Loading.
Danilo Dy Tue, 01/22/2008 - 21:34
User Badges:
  • Blue, 1500 points or more

Hi,


The root cause of your problem are the following errors;


Jan 22 12:01:08: %PHY-4-MODULE_DUP: SFPs in Gi1/0/2 and in Gi1/0/4 have duplicate vendor-id and serial numbers


Explanation

This message means that the small form-factor pluggable (SFP) module was identified as a Cisco SFP, but its vendor ID and serial number match that of another SFP in the system. The first [chars] is the interface in which the SFP is installed, and the second [chars] is the interface where the duplicate SFP is installed.


Recommended Action

Cisco SFP modules are assigned unique serial numbers. Verify that the module was obtained from Cisco or a supported vendor. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.


Regards,

Dandy




Hi Dandy,


Thanks for your reply.


The modules say Cisco Systems, and we did purchase them from a supported vendor.


I tried your suggestions. The Output Interpreter reported "No information on error code PHY-4-MODULE_DUP". The Bug Toolkit doesn't have anything on this either. I also haven't found anything in the Cisco online support sites.


The odd thing about this is that there isn't another SFP in the system. Inserting this module in G1/0/2 generates this error message even though there isn't a SFP in G1/0/4.


Thanks again for your reply.


Dave


Actions

This Discussion