Search this Blog

Tuesday, March 19, 2013

Cisco Catalyst WS-C2960S-48TD-L + SFP-10G-SR-AX issues

We ordered 2 WS-C2960S-48TD-L switches. We also ordered the Axiom equivelent to the SFP-10G-SR (SFP-10G-SR-AX) per the 10-Gigabit Ethernet Transceiver Modules Compatibility Matrix (http://www.cisco.com/en/US/docs/interfaces_modules/transceiver_modules/compatibility/matrix/OL_6974.html)
 

We have tested this issue with both the c2960s-universalk9-mz.122-55.SE5 and c2960s-universalk9-mz.150-2.SE2 (currently loading c2960s-universalk9-mz.122-55.SE5).

When inserting the SFP+ module, I am presented with the following:
*Mar  1 00:16:00.831: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/49 has bad crc
*Mar  1 00:16:00.831: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/49, putting Gi1/0/49 in err-disable state

The first thing we noticed was that the output was related to Gi1/0/49, which is the other incorrect combo port for the 10GB transceiver modle.  We ran the following commands:
Switch(config)# service unsupported-transceiver
Switch(config)# no errdisable detect cause gbic-invalid

After running the commands, We are still getting the following:
*Mar  1 00:28:25.000: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/49 has bad crc

With the above configurations present, or otherwise, the following is shown with the SFP+ module inserted:
Switch#sh ip int g1/0/49
GigabitEthernet1/0/49 is down, line protocol is down (notconnect)
  Hardware is Gigabit Ethernet, address is c062.6bbd.1f31 (bia c062.6bbd.1f31)

Switch#sh int t1/0/1
TenGigabitEthernet1/0/1 is down, line protocol is down (notconnect)
  Hardware is not present

Removing the SFP+ module:
Switch#sh int g1/0/49
GigabitEthernet1/0/49 is down, line protocol is down (notconnect)
  Hardware is not present

Switch#sh int t1/0/1
TenGigabitEthernet1/0/1 is down, line protocol is down (notconnect)
  Hardware is Ten Gigabit Ethernet, address is c062.6bbd.1f33 (bia c062.6bbd.1f33)

Why does the 10GB SFP+ module persuade the switch to mark the T1/0/1 interface as "Hardware Not Present", and choose the G1/0/49 port instead?


The Axiom-branded module may not work because the IDPROM inside has a MD5 code which does not match the Cisco's code check.  This is why the port went into error-disable.  This behavior is normal when you use a non-Cisco branded module.

We have seen the manufacturer of the SFP/SFP+ to reflash the module's IDPROM in order to "trick" the appliance.



Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

No comments :

Post a Comment

 
/* Google Analytics begin ----------------------------------------------- */ /* Google Analytics end ----------------------------------------------- */