cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
8600
Views
5
Helpful
2
Replies
frede_frede
Beginner

3rd party transceiver in Cisco Nexus 5500

Hi,

This is the output of a 3rd party transceiver:

Ethernet1/26

    transceiver is present

    type is 10Gbase-(unknown)

    name is Amphenol

    part number is 530-4451-01-

    revision is

    serial number is APF124900235KA

    nominal bitrate is 10300 MBit/sec

    Link length supported for copper is 3 m

    cisco id is --

    cisco extended id number is 4

This can bring problems, any special configuration for this cases?

This is a cable QSFP to 4xSFP+, the SFP+ is on the Nexus side.

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Steve Fuller
Engager

Hi,

There should be no special configuration needed as since NX-OS 4.1(3)N2(1) the Nexus will attempt to bring up the port even with non Cisco transceivers installed. The process is as follows:

If attached interconnect (transceiver) is a twinax cable, then verify transceiver SPROM to match Cisco magic code. If the check succeeds then bring up the interface else check whether the Vendor Part Number (PN) has been certified. If the Vendor PN is certified bring up the interface else print a warning message stating that non-Cisco transceiver is attached (shown below) and try to bring up the port.

2009 Oct 9 01:46:42 switch %ETHPORT-3-IF_NON-CISCO_TRANSCEIVER: Non-Cisco transceiver on interface Ethernet1/18 is detected.

The one are you might run into an issue is support, as stated in the Twinax Cables Certification Matrix for Cisco Nexus 2000 and Nexus 5000 Series Switches Data Sheet:

If a twinax cable that is not part of the compatibility matrix is connected into a system, Cisco TAC will still debug the problem provided the customer has valid support contract on the switches. However TAC may ask the customer to replace with Cisco qualified cables if there is a situation that points to cables possibly being faulty or the customer will be redirected to the cable provider for support

Regards

View solution in original post

2 REPLIES 2
Steve Fuller
Engager

Hi,

There should be no special configuration needed as since NX-OS 4.1(3)N2(1) the Nexus will attempt to bring up the port even with non Cisco transceivers installed. The process is as follows:

If attached interconnect (transceiver) is a twinax cable, then verify transceiver SPROM to match Cisco magic code. If the check succeeds then bring up the interface else check whether the Vendor Part Number (PN) has been certified. If the Vendor PN is certified bring up the interface else print a warning message stating that non-Cisco transceiver is attached (shown below) and try to bring up the port.

2009 Oct 9 01:46:42 switch %ETHPORT-3-IF_NON-CISCO_TRANSCEIVER: Non-Cisco transceiver on interface Ethernet1/18 is detected.

The one are you might run into an issue is support, as stated in the Twinax Cables Certification Matrix for Cisco Nexus 2000 and Nexus 5000 Series Switches Data Sheet:

If a twinax cable that is not part of the compatibility matrix is connected into a system, Cisco TAC will still debug the problem provided the customer has valid support contract on the switches. However TAC may ask the customer to replace with Cisco qualified cables if there is a situation that points to cables possibly being faulty or the customer will be redirected to the cable provider for support

Regards

View solution in original post

Thanks Steve

I didn't have any problems connecting the cables.

Regards

Fred

Content for Community-Ad
This widget could not be displayed.