[c-nsp] Cisco and third party transceivers
Martin T
m4rtntns at gmail.com
Wed Nov 9 04:12:35 EST 2011
In addition, anyone seen a situation where DDM support depends on IOS
image version? For example I have one "ProLabs X2-10GB-LR-C"
transceiver, which outputs DDM information in case of
"cat4500-ipbasek9-mz.122-54.SG.bin", but displays nothing in "show
interfaces transceiver" output when IOS image is
"cat4500-ipbasek9-mz.122-37.SG1.bin". Anyone seen something like this?
Last but not least, any ideas why do different switch models display
transceiver EEPROM information(show idprom interface X) differently?
Example below with third-party SFP-BIDI-240B-D Cisco-compatible
transceiver:
A) in ME-C3750-24TE switch:
C3750#show idprom interface Gi1/0/1
General SFP Information
-----------------------------------------------
Identifier : 0x03
Connector : 0x07
Transceiver : 0x00 0x00 0x00 0x02 0x00 0x00 0x00 0x00
Encoding : 0x01
BR_Nominal : 0x0D
Vendor Name : OEM
Vendor Part Number : SFP-BIDI-240D
Vendor Revision : 0x41 0x20 0x20 0x20
Vendor Serial Number : GB1110260604
-----------------------------------------------
Other Information
-------------------------------------------------------
Port asic num : 00
Port asic port num : 00
SFP presence index : 00
SFP iter cnt : 4654580
SFP failed oper flag : 0x00000000
IIC error cnt : 0
IIC error dsb cnt : 0
IIC max sts cnt : 35
Chk for link status : 01
Link status : 00
Autoneg enable : 01
Flow control Pause : 00
Flow control asymPause: 00
Duplex mode : 00
PcsInfo : 0x041960A8
MacInfo : 0x04196098 0x04196090
AutoNeg : 0x04196090 0x04196098
Sfp selection asic reg map
--------------------------------
phyLoopback : 0x00
sfpControl : 0x4E
Regs Loc : 0xF0000000
--------------------------------
SFF-8472 MSA EEPROM Data
===========================================
000 : 03 04 07 00 00 00 02 00 00 00
010 : 00 01 0D 00 28 FF 00 00 00 00
020 : 4F 45 4D 20 20 20 20 20 20 20
030 : 20 20 20 20 20 20 00 00 0B 40
040 : 53 46 50 2D 42 49 44 49 2D 32
050 : 34 30 44 20 20 20 41 20 20 20
060 : 06 0E 00 5B 00 1A 00 00 47 42
070 : 31 31 31 30 32 36 30 36 30 34
080 : 20 20 20 20 31 31 31 30 32 35
090 : 20 20 58 F0 01 CB 37 34 30 2D
100 : 30 31 31 36 31 34 20 52 45 56
110 : 20 30 31 00 00 00 00 00 00 00
120 : 00 00 00 00 00 00 00 00
SFF-8472 Digital Diagnostic Monitoring Data
===========================================
000 : 55 00 F6 00 50 00 FB 00 90 88
010 : 71 48 8C 9F 75 30 7E F4 13 88
020 : 75 30 17 70 62 1F 04 EB 4D F1
030 : 06 31 31 2D 00 14 27 10 00 19
040 : 00 00 00 00 00 00 00 00 00 00
050 : 00 00 00 00 00 00 00 00 00 00
060 : 00 00 00 00 00 00 00 00 3F 80
070 : 00 00 00 00 00 00 01 00 00 00
080 : 01 00 00 00 01 00 00 00 01 00
090 : 00 00 00 00 00 DA 19 B3 80 A4
100 : 33 18 13 E4 00 01 00 00 00 00
110 : 02 00 00 40 00 00 00 40 00 00
120 : 00 FF FF FF FF FF FF FF
YETI INTERNAL REGS
-----------------------------------------------
Location=0xD8000500 : Value=0x00
Location=0xD8000501 : Value=0x00
Location=0xD8000502 : Value=0x00
Location=0xD8000503 : Value=0x00
Location=0xD8000504 : Value=0x00
Location=0xD8000505 : Value=0x00
Location=0xD8000506 : Value=0x00
Location=0xD8000507 : Value=0x02
Location=0xD8000508 : Value=0x00
Location=0xD8000509 : Value=0x40
Location=0xD800050A : Value=0x00
Location=0xD800050B : Value=0x00
Location=0xD800050C : Value=0x05
Location=0xD800050D : Value=0x00
Location=0xD800050E : Value=0x01
Location=0xD800050F : Value=0x00
Location=0xD8000510 : Value=0x0F
yetiIICinited : Value=0x00000001
yetiIICLockPassCnt : Value=0
yetiIICLockFailCnt : Value=0
yetiIICLockApp : Value=11
-----------------------------------------------
-------------------------------------------------------
C3750#
B) and this very same SFP in WS-C4506 switch:
Catalyst4500#show idprom interface Gi1/3
GBIC Serial EEPROM Contents:
Common Block:
Identifier = Not available [0x3]
Extended Id = GBIC is compliant with MOD_DEF 4 [0x4]
Connector = LC Connector [0x7]
Transceiver
Type = Gbic 1000BaseZX
Speed(FC,byte 10)= Not available [0x0]
Media = Not available [0x0]
Technology = Not available [0x0]
Link Length = Not available [0x0]
GE Comp Codes = 1000BASE-LX [0x2] (LX used generically for LX, LH or ZX)
SONET Comp Codes = Not available [0x0]
Encoding = 8B10B [0x1]
BR, Nominal = 1300 Mbps (million bits per second)
Length(9u) in km = 40 km
Length(9u) = > 25.4 km
Length(50u) = GBIC does not support 50 micron multi-mode fibre, or the
length must be determined from the transceiver technology.
Length(62.5u) = GBIC does not support 62.5 micron multi-mode fibre, or
the length must be determined from transceiver technology.
Length(Copper) = GBIC does not support copper cables, or the length must
be determined from the transceiver technology.
Vendor name = OEM
Vendor OUI = 2880
Vendor Part No. = SFP-BIDI-240D
Vendor Part Rev. = A
Wavelength = 1550 nanometers
CC_BASE = 0x5B
Extended ID Fields
Options = Loss of Signal implemented TX_FAULT signal
implemented TX_DISABLE is implemented and disables the serial output
[0x1A]
BR, max = Unspecified
BR, min = Unspecified
Vendor Serial No. = GB1110260604
Date code = 111025
Diag monitoring = Implemented
Calibration type = External
Rx pwr measuremnt = Average Power
Address change = Not required
CC_EXT = 0xCB
Vendor Specific ID Fields:
1797097C 37 34 30 2D 30 31 31 36 31 34 20 52 45 56 20 30 740-011614 REV 0
1797098C 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1...............
SEEPROM contents (hex) size 128:
0x0000 03 04 07 00 00 00 02 00 00 00 00 01 0D 00 28 FF ..............(.
0x0010 00 00 00 00 4F 45 4D 20 20 20 20 20 20 20 20 20 ....OEM
0x0020 20 20 20 20 00 00 0B 40 53 46 50 2D 42 49 44 49 ... at SFP-BIDI
0x0030 2D 32 34 30 44 20 20 20 41 20 20 20 06 0E 00 5B -240D A ...[
0x0040 00 1A 00 00 47 42 31 31 31 30 32 36 30 36 30 34 ....GB1110260604
0x0050 20 20 20 20 31 31 31 30 32 35 20 20 58 F0 01 CB 111025 Xp.K
0x0060 37 34 30 2D 30 31 31 36 31 34 20 52 45 56 20 30 740-011614 REV 0
0x0070 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1...............
Catalyst4500#
Any explanation to this?
regards,
martin
2011/10/3 Dennis <daodennis at gmail.com>:
> On Tue, Sep 27, 2011 at 1:17 PM, Martin T <m4rtntns at gmail.com> wrote:
>> Hello,
>> there are providers like Flexoptix(http://www.flexoptix.net) who are
>> able to flash SFP EEPROM memory with different vendor data, probably
>> set custom serial numbers etc. However, why is such service needed at
>> nowadays for Cisco equipment? Every router/switch I have seen supports
>> the "service unsupported-transceiver"(should turn of checking the
>> "Cisco Quality ID") and "no errdisable detect cause gbic-invalid"
>> commands and thus doesn't check the ID code in EEPROM..
>> In addition, am I correct, that some old Cisco IOS versions did not
>> have the "service unsupported-transceiver" and "no errdisable detect
>> cause gbic-invalid" commands and thus one really was forced to use
>> transceivers with Cisco serials?
>>
>
> Some ASAs won't take some 3rd party transceivers no matter what voodoo
> you type, as far as I've been able to figure out anyway. It really
> depends on your business model so to speak.
>
More information about the cisco-nsp
mailing list