AN-2030: Digital Diagnostic Monitoring Interface for Optical Transceivers F i n i s a r
1
Application Note AN-2030 2
Digital Diagnostic Monitoring Interface 3
for SFP Optical Transceivers 4
5
1. Scope and Overview 6
7
This document defines an enhanced digital diagnostic monitoring interface available in 8
Finisar SFP and GBIC optical transceivers. The interface allows real time access to 9
device operating parameters, and it includes a sophisticated system of alarm and 10
warning flags which alerts end-users when particular operating parameters are outside 11
of a factory set normal range. The interface is fully compliant with SFF-8472, “Digital 12
Diagnostic Monitoring Interface for Optical Transceivers", revision 9.3. 13
14
These digital diagnostic features are implemented in all Finisar SFP transceivers that 15
contain a “D” in the part number suffix (for example, FTRJ-1319-7D-2.5), as well as 16
DWDM and CWDM GBICs. All next generation Finisar SFPs utilizing the new part 17
numbering scheme (e.g. FTRJ1621P1BCL) also have the same diagnostic capability. 18
19
The interface is an extension of the serial ID interface defined in the GBIC specification 20
as well as the SFP MSA. Both specifications define a 256-byte memory map in 21
EEPROM, which is accessible over a 2-wire serial interface at the 8 bit address 22
1010000X (A0h). The digital diagnostic monitoring interface makes use of the 8 bit 23
address 1010001X (A2h), so the originally defined serial ID memory map remains 24
unchanged. The interface is identical to, and is thus fully backward compatible with both 25
the GBIC Specification and the SFP Multi Source Agreement. The complete interface is 26
described in Section 3 below. 27
28
The operating and diagnostics information is monitored and reported by a Digital 29
Diagnostics Transceiver Controller (DDTC), which is accessed via a 2-wire serial bus. 30
Its physical characteristics are defined in Section 4. 31
39 Small Form Factor Pluggable (SFP) Transceiver MultiSource Agreement (MSA), 40 September 14, 2000. 41 42 Digital Diagnostic Monitoring Interface for Optical Transceivers: SFF-8472, Draft 43 Revision 9. 3, August 1, 2002. 44 45 46
47
9/26/02 Revision D Page 1
AN-2030: Digital Diagnostic Monitoring Interface for Optical Transceivers F i n i s a r
1
3. Enhanced Digital Diagnostic Interface Definition 2
3
Overview 4
5
The enhanced digital diagnostic interface is a superset of the MOD-DEF interface 6
defined in the SFP MSA document dated September 14, 2000. The 2-wire interface pin 7
definitions, hardware, and timing are clearly defined there, as well as in Section 4 8
below. This section describes an extension to the memory map defined in the SFP 9
MSA. The enhanced interface uses the two wire serial bus address 1010001X (A2h) to 10
provide diagnostic information about the module’s present operating conditions. A 11
memory map is shown in Figure 3.1 below. 12 13
The transceiver generates this diagnostic data by digitizati on of internal analog signals. 14
Calibration and alarm threshold data is written during device manufacture. 15 16
In addition to generating digital readings of internal analog values, the device generates 17
various status bits based on comparison between current values and factory-preset 18
limits. 19
20
9/26/02 Revision D Page 2
AN-2030: Digital Diagnostic Monitoring Interface for Optical Transceivers F i n i s a r
0
1
Figure 3.1: Digital Diagnostic Memory Map 2
3
2 wire address 1010000X (A0h)
4 5
6
7 8 9 10
95
11 12 13 14 15
127
16 17 18 19 20 21 22 23 24 25 26
255
27 28 29 30 31 32 33 34 35 36 37
Specific Data Field Descriptions 38
39
Serial ID Defined by
SFP MSA (96 bytes)
Vendor Specific
(32 bytes)
Reserved in SFP
MSA (128 bytes)
2 wire address 1010001X (A2h)
0
Alarm and Warning
Thresholds (56 bytes)
55
Cal Constants
(40 bytes)
95
Real Time Diagnostic
Interface (24 bytes)
119
Password Entry (8 bytes)
127
User Writable
EEPROM (120 bytes)
247
Control Functions (8 bytes)
255
The information in italics in Table 3.1 indicates fields that are specific to the digital 40
diagnostics functions. 41
42
9/26/02 Revision D Page 3
AN-2030: Digital Diagnostic Monitoring Interface for Optical Transceivers F i n i s a r
Indicates which optional enhanced features are implemented (if any)
Table 3.1 Serial ID: Data Fields – Address A0 1
Data
Address
0 1 Identifier Type of serial transceiver (see table 3.2)
1 1 Ext. Identifier Extended identifier of type of serial transceiver
2 1 Connector Code for connector type (see table 3.3)
3-10 8 Transceiver Code for electronic compatibility or optical compatibility
11 1 Encoding Code for serial encoding algorithm (see table 3.5)
12 1 BR, Nominal Nominal bit rate, units of 100 MBits/sec.
13 1 Reserved
14 1 Length(9µm) -
15 1 Length (9 µm) Link length supported for 9/125 µm fiber, units of 100 m
16 1 Length (50µm) Link length supported for 50/125 µm fiber, units of 10 m
17 1 Length (62.5µm) Link length supported for 62.5/125 µm fiber, units of 10 m
18 1 Length (Copper) Link length supported for copper, units of meters
19 1 Reserved
20-35 16 Vendor name SFP vendor name (ASCII)
36 1 Reserved DWDM channel spacing - DWDM modules only
37-39 3 Vendor OUI SFP vendor IEEE company ID
40-55 16 Vendor PN Part number provided by SFP vendor (ASCII)
56-59 4 Vendor rev Revision level for part number provided by vendor (ASCII)
60-61 2 Wavelength Laser wavelength
62 1 Reserved DWDM wavelength fraction - DWDM modules only
63 1 CC_BASE Check code for Base ID Fields (addresses 0 to 62)
64-65 2
66 1
67 1
68-83 16
84-91 8
92 1
93 1
94 1
95 1
96-127 32
128-255 128
Size
(Bytes)
Monitoring Type
Vendor Specific Vendor Specific EEPROM
Name of
Field
BASE ID FIELDS
(see table 3.4)
Link length supported for 9/125 µm fiber, units of km
km
EXTENDED ID FIELDS
Options Indicates which optional transceiver signals are implemented
(see table 3.6)
BR, max Upper bit rate margin, units of %
BR, min Lower bit rate margin, units of %
Vendor SN Serial number provided by vendor (ASCII)
Date code Vendor’s manufacturing date code (see table 3.7)
Diagnostic
Enhanced
Options
SFF-8472
Compliance
CC_EXT Check code for the Extended ID Fields (addresses 64 to 94)
Reserved Reserved for future use.
Indicates which type of diagnostic monitoring is implemented (if
any) in the transceiver (see Table 3.8)
in the transceiver (see Table 3.9)
Indicates which revision of SFF-8472 the transceiver complies with.
(see table 3.11)
VENDOR SPECIFIC ID FIELDS
Description of Field
9/26/02 Revision D Page 4
AN-2030: Digital Diagnostic Monitoring Interface for Optical Transceivers F i n i s a r
Identifier 1
The identifier value specifies the physical device described by the serial information. 2
This value shall be included in the serial data. The defined identifier values are shown in 3
table 3.2. Finisar SFP modules have this byte set to 03h. Finisar GBIC modules have 4
this byte set to 01h. 5
7
TABLE 3.2: Identifier values 6
Value Description of physical device
00h Unknown or unspecified
01h GBIC
02h Module/connector soldered to motherboard
03h SFP
04-7Fh Reserved
80-FFh Vendor specific
8 9
Extended Identifier 10
The extended identif ier value provides additional information about the transceiver. 11
The field is set to 04h for all non-custom SFP and GBIC modules indicating serial ID 12
module definition. 13 14
Connector15
The connector value indicates the external connector provided on the interface. This 16
value shall be included in the serial data. The defined connector values are shown in 17
table 3.3. Note that 01h – 05h are not SFP compatible, and are included for 18
compatibility with GBIC standards. Finisar optical SFP modules currently have this byte 19
set to 07h (optical LC connector). GBIC modules have the byte set to 01h (SC). 20 21
22
9/26/02 Revision D Page 5
AN-2030: Digital Diagnostic Monitoring Interface for Optical Transceivers F i n i s a r
AN-2030: Digital Diagnostic Monitoring Interface for Optical Transceivers F i n i s a r
Transceiver 1
The following bit significant indicators define the electronicor optical interfaces that are 2
supported by the transceiver. At least one bit shall be set in this field. For Fibre Channel 3
transceivers, the Fibre Channel speed, transmission media, transmitter technology, and 4
distance capability shall all be indicated. The SONET Compliance Codes are described 5
in more detail in table 3.4a. 6
Table 3.4: Transceiver codes 7
8
Data
Addr
3 7-0 Reserved 7 7 very long distance (V)
4 7-5 Reserved 7 6 short distance (S)
4 4 SONET reach specifier bit 1 7 4 long distance (L)
4 3 SONET reach specifi er bit 2 Fibre Channel transmitter technology
4 2 OC 48, long reach 7 3-2 Reserved
4 1 OC 48, intermediate reach 7 1 Longwave laser (LC)
4 0 OC 48 short reach 7 0 Electrical inter-enclosure (EL)
5 7 Reserved 8 7 Electrical intra-enclosure (EL)
5 6 OC 12, single mode long reach 8 6 Shortwave laser w/o OFC (SN)
5 5 OC 12, single mode inter. reach 8 5 Shortwave laser w/ OFC (SL)
5 4 OC 12 multi-mode short reach 8 4 Longwave laser (LL)
5 3 Reserved 8 0-3 Reserved
5 2 OC 3, single mode long reach
5 1 OC 3, single mode inter. reach Fibre Channel transmission media
5 0 OC 3, multi-mode short reach 9 7 Twin Axial Pair (TW)
Gigabit Ethernet Compliance Codes 94 Video Coax (TV)
Description of transceiver Data
Addr
Bit1 Description of transceiver
1
Bit 7 is the high order bit and is transmitted first in each byte.
9/26/02 Revision D Page 7
AN-2030: Digital Diagnostic Monitoring Interface for Optical Transceivers F i n i s a r
The SONET compliance code bits allow the host to determine with which specifications 1
a SONET transceiver complies. For each bit rate defined in Table 3.5 (OC -3, OC-12, 2
OC-48), SONET specifies short reach (SR), intermediate reach (IR), and long reach 3
(LR) requirements. For each of the three bit rates, a single short reach (SR) 4
specification is defined. Two variations of intermediate reach (IR-1, IR-2) and three 5
variations of long reach (LR-1, LR-2, and LR-3) are also defined for each bit rate. Byte 6
4, bits 0-2, and byte 5, bits 0-7 allow the user to determine which of the three reaches 7
has been implemented – short, intermediate, or long. Two additional bits (byte 4, bits 3-8
4) are necessary to discriminate between different intermediate or long reach variations. 9
These codes are defined in Table 3.4a. 10
Table 3.4a: SONET Reach Specifiers 11
Speed Reach Specifier bit 1 Specifier bit 2 Description
OC-3/OC-12/OC-48 Short 0 0 SONET SR compliant
OC-3/OC-12/OC-48 Intermediate 1 0 SONET IR-1 compliant
OC-3/OC-12/OC-48 Intermediate 0 1 SONET IR-2 compliant
OC-3/OC-12/OC-48 Long 1 0 SONET LR-1 compliant
OC-3/OC-12/OC-48 Long 0 1 SONET LR-2 compliant
OC-3/OC-12/OC-48 Long 1 1 SONET LR-3 compliant
12
Encoding 13
The encoding value indicates the serial encoding mechanism that is the nominal design 14
target of the particular SFP. The value shall be contained in the serial data. The defined 15
encoding values are shown in table 3.5. Finisar Gigabit Ethernet/Fibre Channel 16
transceivers have this byte set to 01h (8B/10B encoding), and SONET transceivers 17
(including all SONET multi-rate transceivers) are set to 05h (SONET Scrambled). 18
Table 3.5: Encoding codes 19
20
Code Description of encoding mechanism
00h Unspecified
01h 8B10B
02h 4B5B
03h NRZ
04h Manchester
05h SONET Scrambled
06h -FFh Reserved
21
22
9/26/02 Revision D Page 8
AN-2030: Digital Diagnostic Monitoring Interface for Optical Transceivers F i n i s a r
BR, nominal 1
The nominal bit rate (BR, nominal) is specified in units of 100 Megabits per second, 2
rounded off to the nearest 100 Megabits per second. The bit rate includes those bits 3
necessary to encode and delimit the signal as well as those bits carrying data 4
information. A value of 0 indicates that the bit rate is not specified and must be 5
determined from the transceiver technology. The actual information transfer rate will 6
depend on the encoding of the data, as defined by the encoding value. 7
8
Length (9µ)-km 9
Note that this field is an addition to EEPROM data from the original GBIC definition. 10
This value specifies the link length that is supported by the transceiver while operating 11
in compliance with the applicable standards using single mode fiber. The value is in 12
units of kilometers. A value of 255 means that the transceiver supports a link length 13
greater than 254 km. A value of zero means that the transceiver does not support single 14
mode fiber or that the length information must be determined from the transceiver 15
technology. 16
17
Length (9µ) 18
This value specifies the link length that is supported by the transceiver while operating 19
in compliance with the applicable standards using single mode fiber. The value is in 20
units of 100 meters. A value of 255 means that the transceiver supports a link length 21
greater than 25.4 km. A value of zero means that the transceiver does not support 22
single mode fiber or that the length information must be determined from the transceiver 23
technology. 24
25
Length (50µ) 26
This value specifies the link length that is supported by the transceiver while operating 27
in compliance with the applicable standards using 50 micron multi-mode fiber. The 28
value is in units of 10 meters. A value of 255 means that the transceiver supports a link 29
length greater than 2.54 km. A value of zero means that the transceiver does not 30
support 50 micron multi -mode fiber or that the length information must be determined 31
from the transceiver technology. 32
33
Length (62.5µ) 34
This value specifies the link length that is supported by the transceiver while operating 35
in compliance with the applicable standards using 62.5 micron multi-mode fiber. The 36
value is in units of 10 meters. A value of 255 mea ns that the transceiver supports a link 37
length greater than 2.54 km. A value of zero means that the transceiver does not 62.5 38
micron multi-mode fiber or that the length information must determined from the 39
9/26/02 Revision D Page 9
AN-2030: Digital Diagnostic Monitoring Interface for Optical Transceivers F i n i s a r
transceiver technology. It is common for the trans ceiver to support both 50 micron and 1
62.5 micron fiber. 2 3
Length (Copper) 4
This value specifies the minimum link length that is supported by the transceiver while 5
operating in compliance with the applicable standards using copper cable. The value is 6
in units of 1 meter. A value of 255 means that the transceiver supports a link length 7
greater than 254 meters. A value of zero means that the transceiver does not support 8
copper cables or that the length information must be determined from the transceiver 9
technology. Further information about the cable design, equalization, and connectors is 10
usually required to guarantee meeting a particular length requirement. 11
12
Vendor name 13
The vendor name is a 16 character field that contains ASCII characters, left-aligned and 14
padded on the right with ASCII spaces (20h). The vendor name shall be the full name of 15
the corporation, a commonly accepted abbreviation of the name of the corporation, the 16
SCSI company code for the corporation, or the stock exchange code for the corporation. 17
At least one of the vendor name or the vendor OUI fields shall contain valid serial data. 18
Finisar transceivers contain the text string “FINISAR CORP.” in this address. 19
20
DWDM Channel Spacing 21
Byte 36 is reserved (set to 00h) in the SFP MSA as well as in SFF-8472. Finisar 22
DWDM transceivers use this byte to indicate their channel spacing. DWDM channel 23
spacing is an 8 bit unsigned integer indicating the DWDM channel spacing in units of 24
gigahertz. This byte is set to 00h in all non-DWDM Finisar transceivers. 25
26
Vendor OUI 27
The vendor organizationally unique identifier field (vendor OUI) is a 3-byte field that 28
contains the IEEE Company Identifier for the vendor. A value of all zero in the 3-byte 29
field indicates that the Vendor OUI is unspecified. Finisar transceivers contain the 30
values 00h, 90h and 65h in these addresses. 31
32
Vendor PN 33
The vendor part number (vendor PN) is a 16-byte field that contains ASCII characters, 34
left-aligned and padded on the right with ASCII spaces (20h), defining the vendor part 35
number or product name. A value of all zero in the 16-byte field indicates that the 36
vendor PN is unspecified. 37
38
9/26/02 Revision D Page 10
AN-2030: Digital Diagnostic Monitoring Interface for Optical Transceivers F i n i s a r
Vendor Rev 1
The vendor revision number (vendor rev) is a 4-byte field that contains ASCII 2
characters, left-aligned and padded on the right with ASCII spaces (20h), defining the 3
vendor’s product revision number. A value of all zero in the 4-byte field indicates that 4
the vendor rev is unspecified. All legacy Finisar transceivers contain zero in all 4 bytes 5
or ASCII space (20h) in all four bytes or one of two place holders: “X1—“ or “1A—“. 6
Early versions of the digital diagnostic standard (SFF-8472), used a scale factor of 7
1µA/AD Count for interpreting laser bias current readings. SFF-8472 later changed the 8
scale factor to 2µA/AD Count. All Finisar modules using a scale factor of 2µA/AD Count 9
have an ASCII “A” written in byte 56 of this field. 10
11
Laser Wavelength 12
Nominal transmitter output wavelength at room temperature. This field is a 16 bit value 13
with byte 60 as high order byte and byte 61 as low order byte. The laser wavelength is 14
equal to the the 16 bit integer value in nm. This field allows the user to read the laser 15
wavelength directly, so it is not necessary to infer it from the transceiver “Code for 16
Electronic Compatibility” (bytes 3 – 10). This also allows specification of wavelengths 17
not covered in bytes 3 – 10, such as those used in coarse WDM systems. 18
34
19
DWDM Wavelength Fraction 20
Byte 62 is reserved (set to 00h) in the SFP MSA as well as SFF-8472. Finisar DWDM 21
transceivers use this byte in conjunction with bytes 60-61 to indicate the DWDM 22
transceiver laser wavelength. Bytes 60-61 provide the integer wavelength in units of 23
nm. In DWDM transceivers, by 62 provides the fractional wavelength in units of 24
0.01nm. Thus the wavelength for a particular DWDM transceiver is given by: 25
(byte 60,61) + (byte 62 * 0.01nm). In all non-DWDM Finisar transceivers, this byte is set 26
to 00h. 27 28 CC_BASE29
The check code is a one byte code that can be used to verify that the first 64 bytes of 30
serial information in the SFP is valid. The check code shall be the low order 8 bits of the 31
sum of the contents of all the bytes from byte 0 to byte 62, inclusive. 32
33
9/26/02 Revision D Page 11
Loading...
+ 24 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.