Apollo

Reference Manual
Version 9.5R2
Document Revision 01
Published: June 2021
Apollo Reference Manual
V9.5R2
Catalog No: X18956
Drawing No: 497016-2701-213-A00
June 2021
Revision 01

NPT-1800, NPT-1300, NPT-1250, NPT-1200, NPT-1100, NPT-1050, NPT-1022, NPT-

1021, NPT-1020, and NPT-1010/1010D are CE2.0 certified/compliant.

NPT-1800, NPT-1300, NPT-1250, NPT-1200, NPT-1100, NPT-1050, and NPT-1022 are

MEF3.0 Carrier Ethernet certified/compliant for E-Line, E-LAN, E-Tree, E-Access, and E-
Transit services.

ECI's qualification lab is accredited by A2LA for competence in electrical testing according
to the International Standard ISO IEC 17025-2005 General Requirements for the
Competence of Testing and Calibration Laboratories.

ECI's management applications run on VMWare virtualization hypervisors.

Copyright by ©Ribbon Communications Inc., including its affiliates, 2012-2021. All rights reserved worldwide.
ECI is a Ribbon affiliate and part of the Ribbon group of companies (“Ribbon”).
This is a legal agreement between you, the end user, and ECI Ltd. (“ECI”). BY OPENING THE DOCUMENTATION AND/OR DISK
PACKAGE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS
OF THIS AGREEMENT, PROMPTLY RETURN THE UNOPENED DOCUMENTATION AND/OR DISK PACKAGE AND THE
ACCOMPANYING ITEMS (INCLUDING WRITTEN MATERIALS AND BINDERS OR OTHER CONTAINERS), TO THE PLACE FROM
WHICH YOU OBTAINED THEM.
All documentation and/or disk and all information and/or data contained in the documentation and/or disk ["ECI's Proprietary"] is ECI's
proprietary and is subject to all copyright, patent, and other laws protecting intellectual property, and any international treaty provisions,
as well as any specific agreement protecting ECI's rights in the aforesaid information. Any use of ECI's Proprietary for any purposes
[included but not limited: published, reproduced, or disclosed to third parties, in whole or in part] other than those for which it was disclosed,
without the express prior written permission of ECI, is strictly forbidden.
ECI's Proprietary is provided "AS IS" and may contain flaws, omissions, or typesetting errors. No responsibility and or liability whatsoever
are assumed by ECI for you or any other party, for the use thereof, nor for the rights of third parties, nor for any loss or damage whatsoever
or howsoever caused, arising directly or indirectly in connection with ECI's Proprietary, which may be affected in any way by the use
and/or dissemination thereof. ECI reserves the right, without prior notice or liability, to make changes in equipment design or specifications
including any change in and to the ECI's Proprietary.
Any representation(s) in ECI's Proprietary concerning performance of ECI's product(s) are for informational purposes only and are not
warranties of product performance or otherwise, either express or implied. No warranty is granted nor liability assumed in relation thereto,
unless specifically undertaken in ECI's sales contract or order confirmation. ECI's Proprietary is periodically updated, and changes will be
incorporated in subsequent editions. All graphics included in this document are for illustrative purposes only and might not correspond
with your specific product version.
The documentation and/or disk and all information contained therein is owned by ECI and is protected by all relevant copyright, patent,
and other applicable laws and international treaty provisions. Therefore, you must treat the information contained in the documentation
and disk as any other copyrighted material (for example, a book or musical recording).
Other Restrictions. You may not rent, lease, sell, or otherwise dispose of ECI's Proprietary, as applicable.
YOU MAY NOT USE, COPY, MODIFY, OR TRANSFER THE DOCUMENTATION AND/OR DISK OR ANY COPY IN WHOLE OR PART,
EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE. ALL RIGHTS NOT EXPRESSLY GRANTED ARE RESERVED BY ECI.
All trademarks mentioned herein are the property of their respective holders.
Notwithstanding the generality of the aforementioned, you expressly waive any claim and/or demand regarding liability for indirect, special,
incidental, or consequential loss or damage which may arise in respect of ECI's Proprietary contained therein, howsoever caused, even
if advised of the possibility of such damages.
The end user hereby undertakes and acknowledges that they read the "Before You Start/Safety Guidelines" instructions (when provided
by ECI) and that such instructions were understood by them. ECI shall not be liable to you or to any other party for any loss or damage
whatsoever or howsoever caused, arising directly or indirectly in connection with you fulfilling and/or failure to fulfill in whole or in part the
"Before You Start/Safety Guidelines" instructions.
Contents
Useful information ................................................................................................ xiii
Related documents .....................................................................................................................xiii
Contact information .....................................................................................................................xiii
Revision history ..........................................................................................................................xiii

1 OPT9932/OPT9914 platform architecture ................................................... 1-1

1.1 OPT9932 platform layout ...............................................................................................1-2
1.2 OPT9914 platform layout ...............................................................................................1-4
1.3 OPT99xx control and communications subsystem .........................................................1-5
1.3.1 OPT99xx control............................................................................................................... 1-5
1.3.2 OPT99xx communications ............................................................................................... 1-6
1.3.3 OPT99xx flexible support for management mixtures ....................................................... 1-7
1.3.4 OPT99xx routing and forwarding functionality.................................................................. 1-7
1.3.5 OPT99xx management channel with dynamic OSPF ...................................................... 1-8
1.4 OPT99xx timing and synchronization .............................................................................1-8
1.5 OPT99xx universal fabric system .................................................................................1-10
1.6 OPT99xx cross-connect functionality ...........................................................................1-11
1.7 OPT99xx Lite Packet support .......................................................................................1-12
1.8 OPT99xx power feed subsystem .................................................................................1-13
1.9 OPT99xx air cooling subsystem ...................................................................................1-15
1.10 OPT99xx management system ....................................................................................1-20

2 OPT9932/OPT9914 common cards ............................................................. 2-1

2.1 xRCP/xRCP1 .................................................................................................................2-1
2.2 xFM ................................................................................................................................2-4
2.3 xMIM ..............................................................................................................................2-6
2.4 xTAM ..............................................................................................................................2-7
2.5 xTEM ............................................................................................................................2-10
2.6 xPFM-14 .......................................................................................................................2-12
2.7 xFCM-14 ......................................................................................................................2-14
2.8 xCBM ...........................................................................................................................2-17
2.9 xPFM-32 .......................................................................................................................2-20
2.10 xFCM-32 ......................................................................................................................2-22

Ribbon Communications Inc. Proprietary iii

Apollo Reference Manual Contents

3 OPT9932/OPT9914 service cards ................................................................ 3-1

3.1 HIO500 and HIO400/HIO400EN ....................................................................................3-1
3.1.1 HIO500 port configuration and usage guidelines ............................................................. 3-5
3.2 HIO100_2 .......................................................................................................................3-6
3.3 HIO10_40 .......................................................................................................................3-9
3.3.1 HIO10_40 fan-out port configuration rules ..................................................................... 3-12
3.4 HIO10_20 .....................................................................................................................3-14
3.5 TIOMR_32 ....................................................................................................................3-16

4 OPT9904X platform architecture and cards ............................................... 4-1

4.1 OPT9904X platform layout .............................................................................................4-1
4.2 OPT9904X common cards .............................................................................................4-3
4.2.1 RCP04X ........................................................................................................................... 4-3
4.2.2 PFM04X ........................................................................................................................... 4-5
4.2.3 PFM04X_H ....................................................................................................................... 4-6
4.2.4 FCM04X ........................................................................................................................... 4-8
4.2.5 TAMIM04X ..................................................................................................................... 4-10
4.3 OPT9904X passive and photonic cards .......................................................................4-13
4.4 MIO200/MIO200EN ......................................................................................................4-13
4.5 MIO700 ........................................................................................................................4-17

5 OPT9901X platform architecture and cards ............................................... 5-1

5.1 OPT9901X platform layout .............................................................................................5-2
5.2 OPT9901X common cards and modules........................................................................5-4
5.2.1 PFM01X_DC/PFM01X_AC .............................................................................................. 5-4
5.2.2 FCM01X ........................................................................................................................... 5-7
5.3 ADM functionality ...........................................................................................................5-9
5.3.1 Service configuration guidelines (ADM100) ................................................................... 5-10
5.4 Multi-ADM functionality.................................................................................................5-11
5.4.1 Service configuration guidelines (MADM10) .................................................................. 5-12
5.5 CPE10 functionality ......................................................................................................5-13
5.5.1 Service configuration guidelines (CPE10) ...................................................................... 5-13
5.6 Agg200 functionality .....................................................................................................5-14
5.6.1 Service configuration guidelines (Agg200) ..................................................................... 5-14

Ribbon Communications Inc. Proprietary iv

Apollo Reference Manual Contents

6 OPT96xx platform architecture ................................................................... 6-1

6.1 OPT9624 platform layout ...............................................................................................6-2
6.1.1 OPT9624 platform configurations..................................................................................... 6-3
6.2 OPT9608 platform layout ...............................................................................................6-5
6.3 OPT9603 platform layout ...............................................................................................6-6
6.4 OPT96xx control and communications subsystem .........................................................6-6
6.4.1 OPT96xx control............................................................................................................... 6-7
6.4.2 OPT96xx communications ............................................................................................... 6-8
6.4.3 OPT96xx flexible support for management mixtures ....................................................... 6-9
6.4.4 OPT96xx routing and forwarding functionality................................................................ 6-10
6.4.5 OPT96xx management channel with dynamic OSPF .................................................... 6-10
6.4.6 VoIP in OPT96xx ............................................................................................................ 6-11
6.5 OPT96xx universal fabric functionality .........................................................................6-11
6.6 Cross-connect functionality ..........................................................................................6-11
6.6.1 Types of cross-connections............................................................................................ 6-13
6.7 OTN technology ...........................................................................................................6-16
6.7.1 OTN topologies .............................................................................................................. 6-18
6.8 OPT96xx power feed subsystem .................................................................................6-20

7 OPT9624 common cards .............................................................................. 7-1

7.1 RCP................................................................................................................................7-1
7.1.1 RCP24_T: universal controller ......................................................................................... 7-1
7.1.2 RCP24_O: optimized for pure DWDM .............................................................................. 7-4
7.2 PFM24............................................................................................................................7-7
7.3 CEM24 ...........................................................................................................................7-9
7.4 FCM24 .........................................................................................................................7-11
7.4.1 FCM24 air filters ............................................................................................................. 7-12
7.5 FM1000 ........................................................................................................................7-14

8 OPT9608 common cards .............................................................................. 8-1

8.1 RCP08_O .......................................................................................................................8-1
8.2 RCP1_4AD_T ................................................................................................................8-3
8.3 PFM08_AC .....................................................................................................................8-6
8.4 PFM with a circuit breaker (DC) .....................................................................................8-8
8.5 PFM without a circuit breaker .......................................................................................8-10
8.6 PFM08H_DC ................................................................................................................8-11
8.7 FCM air filters ...............................................................................................................8-13
8.7.1 FCM................................................................................................................................ 8-15
8.7.2 FCM08_S ....................................................................................................................... 8-17

Ribbon Communications Inc. Proprietary v

Apollo Reference Manual Contents

9 OPT9603 common cards .............................................................................. 9-1

9.1 RCP03/RCP03R.............................................................................................................9-1
9.2 PFM03............................................................................................................................9-3
9.3 PFM03_H .......................................................................................................................9-4
9.4 PFM03_AC .....................................................................................................................9-5
9.5 PFM03_RAC ..................................................................................................................9-7
9.6 FCM03 ...........................................................................................................................9-8
9.6.1 FCM03 air filter ............................................................................................................... 9-10

10 OPT96xx optical cards and modules ........................................................ 10-1

10.1 Understanding I/O card slot sizes ................................................................................10-1
10.2 Understanding CD and CDC DWDM architecture ........................................................10-2
10.3 Understanding optical network control parameters ......................................................10-4
10.4 Multi-degree CDC ROADM cards.................................................................................10-7
10.4.1 ROADM_20TF................................................................................................................ 10-9
10.4.2 ROADM_20CF ............................................................................................................. 10-13
10.4.3 ROADM_8x24CDCF .................................................................................................... 10-18
10.4.4 ROADM_9TF................................................................................................................ 10-21
10.4.5 ROADM_9FS ............................................................................................................... 10-25
10.4.6 ROADM_9F .................................................................................................................. 10-29
10.4.7 ROADM_9A50.............................................................................................................. 10-32
10.4.8 ROADM_4FS ............................................................................................................... 10-36
10.4.9 ROADM_4F .................................................................................................................. 10-39
10.4.10 ROADM_4A.................................................................................................................. 10-42
10.4.11 ROADM_4A50.............................................................................................................. 10-45
10.4.12 ROADM_2A.................................................................................................................. 10-48
10.4.13 ROADM_2A50.............................................................................................................. 10-51
10.4.14 TFA_8........................................................................................................................... 10-54
10.5 Mux/DeMux cards ......................................................................................................10-58
10.5.1 MXD88 ......................................................................................................................... 10-58
10.5.2 MXD44 ......................................................................................................................... 10-60
10.5.3 MXD16 ......................................................................................................................... 10-62
10.5.4 MXD8 ........................................................................................................................... 10-64
10.6 CWDM components ...................................................................................................10-65
10.6.1 CMXD8 ......................................................................................................................... 10-66
10.6.2 COADM4_xx ................................................................................................................ 10-68
10.7 OADM cards ...............................................................................................................10-70
10.7.1 FOADM2_xx ................................................................................................................. 10-70
10.7.2 FOADM4_xx ................................................................................................................. 10-73
10.7.3 FOADM850_xx ............................................................................................................. 10-75

Ribbon Communications Inc. Proprietary vi

Apollo Reference Manual Contents

10.8 Optical filters, splitters, and couplers ..........................................................................10-77

10.8.1 CT_1310_2................................................................................................................... 10-77
10.8.2 CT_1510_2................................................................................................................... 10-79
10.8.3 CT_OTDR_2 ................................................................................................................ 10-81
10.8.4 CT_OTDR_2_WIDE ..................................................................................................... 10-83
10.8.5 C_OTDR_2................................................................................................................... 10-85
10.8.6 SP_SM_4 ..................................................................................................................... 10-88
10.8.7 SP_MM_4..................................................................................................................... 10-90
10.8.8 SP_CE4_2.................................................................................................................... 10-92
10.8.9 SP_CE8_1.................................................................................................................... 10-94
10.8.10 SP_CE16_1.................................................................................................................. 10-95
10.8.11 SP_CE32_1.................................................................................................................. 10-97
10.9 Synchronization filters ..............................................................................................10-100
10.9.1 CT_1510/1490............................................................................................................ 10-101
10.9.2 CT_1510/1490_OTDR ............................................................................................... 10-102
10.9.3 CT_1590_1511_OTDR .............................................................................................. 10-105
10.9.4 CT_1610..................................................................................................................... 10-107
10.10 Bidirectional single-fiber DWDM networks ...............................................................10-108
10.10.1 R/B_2 ......................................................................................................................... 10-110
10.10.2 CLT_1510/1590.......................................................................................................... 10-111
10.11 Optical protection cards............................................................................................10-113
10.11.1 OMSP ......................................................................................................................... 10-113
10.11.2 OLP_S2 ...................................................................................................................... 10-117
10.12 Optical amplifiers ......................................................................................................10-120
10.12.1 Raman amplification: Principles of operation ............................................................. 10-121
10.12.2 High power laser safety .............................................................................................. 10-121
10.12.3 Automatic laser shutdown (ALS) ................................................................................ 10-122
10.12.4 OA_PA ....................................................................................................................... 10-123
10.12.5 OA_FB........................................................................................................................ 10-126
10.12.6 OA_M ......................................................................................................................... 10-129
10.12.7 OA_ML ....................................................................................................................... 10-132
10.12.8 OA_L .......................................................................................................................... 10-135
10.12.9 OA_LF ........................................................................................................................ 10-137
10.12.10 OA_HF .................................................................................................................. 10-140
10.12.11 OA_HFS ................................................................................................................ 10-142
10.12.12 OA_FHBS ............................................................................................................. 10-145
10.12.13 OA_MHS ............................................................................................................... 10-148
10.12.14 OA_HRS ............................................................................................................... 10-151
10.12.15 OA_EHRS ............................................................................................................. 10-154
10.12.16 OA_HRSF ............................................................................................................. 10-157

Ribbon Communications Inc. Proprietary vii

Apollo Reference Manual Contents

10.12.17 OA_EHRSF ........................................................................................................... 10-160

10.12.18 OA_LEHRSF ......................................................................................................... 10-164
10.12.19 OA_USPBF ........................................................................................................... 10-167
10.12.20 OA_DLF ................................................................................................................ 10-170
10.12.21 OA_DLHF ............................................................................................................. 10-173
10.12.22 OA_DVLF .............................................................................................................. 10-176
10.12.23 OA_DPR ............................................................................................................... 10-179
10.12.24 OA_DFBL .............................................................................................................. 10-182
10.12.25 OPA_FBS ............................................................................................................. 10-184
10.12.26 OPA_VLFS ........................................................................................................... 10-186
10.12.27 OPA_LFS .............................................................................................................. 10-187
10.12.28 OPA_HFS ............................................................................................................. 10-188
10.13 OTDR modules ........................................................................................................10-190
10.13.1 Miniature OTDR ......................................................................................................... 10-190
10.13.2 SFP OTDR commands............................................................................................... 10-191
10.13.3 OTDR_8 ..................................................................................................................... 10-192
10.13.4 OTDR1610_8S ........................................................................................................... 10-194
10.13.5 OTDR test applications .............................................................................................. 10-197
10.13.6 OTDR one-end test .................................................................................................... 10-198
10.13.7 OTDR two-end test for high power EDFAs ................................................................ 10-199
10.13.8 OTDR Raman span test ............................................................................................. 10-200
10.14 DCF ......................................................................................................................10-200
10.14.1 DCF652_xx ................................................................................................................ 10-201
10.14.2 DCF655_xx ................................................................................................................ 10-202
10.15 OSC_8 .....................................................................................................................10-203

11 OPT96xx advanced Layer 1 service cards ............................................... 11-1

11.1 Advanced OTN features ...............................................................................................11-1
11.1.1 Understanding ODU0 containers ................................................................................... 11-2
11.1.2 Understanding ODUflex ................................................................................................. 11-4
11.1.3 Understanding PT21 (Payload Type = 21) ..................................................................... 11-5
11.2 AoC10 and AoC10B .....................................................................................................11-6
11.2.1 Assignment of AoC10 as AoC25 .................................................................................... 11-9
11.3 TR10_4 ......................................................................................................................11-10
11.4 Encrypted transponder/muxponder cards ..................................................................11-12
11.4.1 Cryptography: basic terminology .................................................................................. 11-12
11.4.2 Configurable Diffie Hellman (DH) groups ..................................................................... 11-14
11.5 TR10_4EN .................................................................................................................11-15
11.5.1 Optical encryption in TR10_4EN .................................................................................. 11-19
11.5.2 TR10_4EN protection schemes ................................................................................... 11-23

Ribbon Communications Inc. Proprietary viii

Apollo Reference Manual Contents

11.6 TR10_12/TR10_12R ..................................................................................................11-23

11.7 TR10_12ULL ..............................................................................................................11-27
11.7.1 ULL channels for transponder applications .................................................................. 11-30
11.8 CMR40B .....................................................................................................................11-32
11.9 CMR100 and CMR100L .............................................................................................11-34
11.9.1 CMR100/CMR100L transceivers.................................................................................. 11-38
11.10 CMR100M ..................................................................................................................11-39
11.11 TR100/TR100L ...........................................................................................................11-43
11.11.1 TR100 and TR100L usage guidelines .......................................................................... 11-46
11.12 TM100 ........................................................................................................................11-48
11.12.1 TM100 usage guidelines .............................................................................................. 11-52
11.13 TM100_2EN ...............................................................................................................11-53
11.14 TM100_2ENB .............................................................................................................11-58
11.15 TM200EN ...................................................................................................................11-63
11.15.1 TR10_12EN usage guidelines...................................................................................... 11-70
11.16 TM200ENB .................................................................................................................11-71
11.17 FIPS 140-2 Level 2 security implementation ..............................................................11-77
11.17.1 FIPS 140-2 Level 2 encryption ..................................................................................... 11-77
11.17.2 Understanding FIPS 140-2 Level 2 security ................................................................. 11-78
11.17.3 FIPS installation procedure and guidelines .................................................................. 11-80
11.18 TR200_2 ....................................................................................................................11-81
11.18.1 TR200_2 applications................................................................................................... 11-84
11.18.2 TR200_2 port configuration options ............................................................................. 11-86
11.19 TM400 ........................................................................................................................11-86
11.19.1 TM400 configuration options ........................................................................................ 11-90
11.19.2 TM400_REG100 regenerator application..................................................................... 11-91
11.20 TM400_2 ....................................................................................................................11-92
11.20.1 TM400_2 applications .................................................................................................. 11-95
11.20.2 TM400_2 port configuration options ............................................................................. 11-96
11.21 TM1200 ......................................................................................................................11-97
11.22 TM800 ......................................................................................................................11-100
11.23 TM1200E ..................................................................................................................11-103
11.24 TM800E....................................................................................................................11-106
11.25 FIO10_5/5B ..............................................................................................................11-109
11.26 FIOMR_16/16B ........................................................................................................11-111
11.27 FIO100 .....................................................................................................................11-114
11.28 FIO100M ..................................................................................................................11-116
11.29 Pluggable transceiver modules ................................................................................11-119

Ribbon Communications Inc. Proprietary ix

Apollo Reference Manual Contents

12 OPT96xx Layer 2 service cards ................................................................. 12-1

12.1 AoC10_L2 ....................................................................................................................12-1

13 Artemis product line ................................................................................... 13-1

13.1 Artemis features and functions .....................................................................................13-2
13.2 Artemis platform layout .................................................................................................13-2
13.2.1 Artemis-1P...................................................................................................................... 13-2
13.2.2 Artemis-2A...................................................................................................................... 13-3
13.2.3 Artemis-2PE ................................................................................................................... 13-3
13.2.4 Artemis-4A...................................................................................................................... 13-5

14 Accessories................................................................................................. 14-1
14.1 Power Distribution Units (PDU) ....................................................................................14-1
14.1.1 PDU55AL ....................................................................................................................... 14-2
14.1.2 PDU77AL ....................................................................................................................... 14-5
14.1.3 PDU99 ............................................................................................................................ 14-9
14.2 RAP-E ........................................................................................................................14-13
14.3 xRAP-100 ...................................................................................................................14-17
14.4 RAP-4B ......................................................................................................................14-21
14.5 AC/DC-DPS850-48-3 power system ..........................................................................14-23
14.5.1 AC/DC-DPS850-48-3 front view ................................................................................... 14-24
14.5.2 AC/DC-DPS850-48-3 rear view.................................................................................... 14-25
14.6 AC/DC PS 6/8.7kW power system .............................................................................14-27
14.6.1 AC/DC PS 6/8.7kW front view ...................................................................................... 14-28
14.6.2 AC/DC PS 6/8.7kW rear view....................................................................................... 14-29
14.7 Fiber storage accessories ..........................................................................................14-31
14.7.1 FST............................................................................................................................... 14-31
14.7.2 Fiber spooler ................................................................................................................ 14-32
14.8 FMT-1U patch panel...................................................................................................14-33
14.8.1 FMT4F-10x10G-MM fiber connection module.............................................................. 14-33
14.8.2 FMT4F-2x4x10G-SM fiber connection module ............................................................ 14-34
14.8.3 FMT4F-2x4x10G-MM fiber connection module ............................................................ 14-34
14.9 Cable guiding accessories .........................................................................................14-35
14.9.1 Fiber and cable guide ................................................................................................... 14-35
14.9.2 Fiber bridges ................................................................................................................ 14-37
14.10 External fiber duct ......................................................................................................14-37

15 Timing and synchronization ...................................................................... 15-1

15.1 Timing and synchronization modules ...........................................................................15-1
15.1.1 xCTM2: central timing module........................................................................................ 15-1
15.1.2 xCTM2 block diagram .................................................................................................... 15-2

Ribbon Communications Inc. Proprietary x

Apollo Reference Manual Contents

15.1.3 Synchronization modes .................................................................................................. 15-3

15.1.4 Synchronization interfaces ............................................................................................. 15-4
15.1.5 Reference clocks ............................................................................................................ 15-5
15.1.6 Built In Test (BIT) ........................................................................................................... 15-6
15.1.7 High availability protection.............................................................................................. 15-6

16 Protection and restoration mechanisms .................................................. 16-1

16.1 OMSP 1:1 protection ....................................................................................................16-1
16.2 OLP 1+1 protection ......................................................................................................16-2
16.3 OCH port protection .....................................................................................................16-4
16.4 SNC-N protection .........................................................................................................16-5
16.5 Combination network traffic and equipment protection.................................................16-6
16.6 Interoperability with SDH/SONET equipment running MSP 1+1 protection .................16-6
16.7 ODU DNI and DRI protection .......................................................................................16-7
16.8 Y-protection for network traffic on transponders ...........................................................16-9
16.9 AoC10/AoC10B ring protection schemes ...................................................................16-10
16.10 WSS ROADM protection ............................................................................................16-11
16.11 ASON, WSON, and SSON GMPLS-based restoration...............................................16-14
16.11.1 Apollo optical control plane architecture....................................................................... 16-16
16.11.2 Multiple protection and restoration schemes ................................................................ 16-22
16.12 Equipment redundancy ..............................................................................................16-24

17 Management system .................................................................................. 17-1

17.1 LightSOFT NMS management .....................................................................................17-1
17.1.1 Layered architecture maximizes flexibility ...................................................................... 17-3
17.1.2 Graphic user interface .................................................................................................... 17-4
17.1.3 Topology management................................................................................................... 17-4
17.1.4 DWDM trails ................................................................................................................... 17-5
17.1.5 Optical trail provisioning and management .................................................................... 17-8
17.1.6 LightPath availability maps ........................................................................................... 17-10
17.1.7 Control map .................................................................................................................. 17-11
17.1.8 Management security mechanisms .............................................................................. 17-12
17.1.9 Management interfaces ................................................................................................ 17-12
17.2 Shade Tree Management System (STMS) ................................................................17-13
17.2.1 STMS key features ....................................................................................................... 17-16
17.3 CLI configuration ........................................................................................................17-18
17.3.1 Command line interface ............................................................................................... 17-18
17.4 NETCONF ..................................................................................................................17-20
17.4.1 Disaggregation application ........................................................................................... 17-24
17.5 Integration with other products ...................................................................................17-25

Ribbon Communications Inc. Proprietary xi

Apollo Reference Manual Contents

17.6 DC power management .............................................................................................17-25

18 Embedded management ............................................................................ 18-1

18.1 Equipment management ..............................................................................................18-1
18.1.1 Shelf types...................................................................................................................... 18-1
18.1.2 Card types ...................................................................................................................... 18-2
18.1.3 Transceiver types ........................................................................................................... 18-2
18.1.4 Equipment hierarchy ...................................................................................................... 18-3
18.1.5 Equipment entities .......................................................................................................... 18-3
18.1.6 Transport entities............................................................................................................ 18-6
18.1.7 Compliance with "Green" requirements ......................................................................... 18-7
18.1.8 Inventory information ...................................................................................................... 18-7
18.1.9 Auto discovery ................................................................................................................ 18-8
18.2 Fault management .......................................................................................................18-8
18.3 Configuration management ........................................................................................18-10
18.3.1 Apollo platforms minimal configuration......................................................................... 18-10
18.3.2 User configuration ........................................................................................................ 18-11
18.3.3 Implicit configuration..................................................................................................... 18-11
18.3.4 Preplanned and manual configuration.......................................................................... 18-11
18.3.5 Transactions ................................................................................................................. 18-12
18.3.6 Rollback operations ...................................................................................................... 18-12
18.4 Performance monitoring .............................................................................................18-13
18.5 Password authentication ............................................................................................18-13
18.6 Fiber connectivity .......................................................................................................18-14
18.6.1 Power control and equalization .................................................................................... 18-14
18.6.2 Diagnostic information .................................................................................................. 18-15
18.6.3 LightSOFT top-down information ................................................................................. 18-16
18.6.4 NE alarm correlation ..................................................................................................... 18-16
18.6.5 Alien lambda................................................................................................................. 18-17
18.6.6 Fiber connectivity to external equipment ...................................................................... 18-17
18.7 Built-In Test (BIT) .......................................................................................................18-18
18.8 Ease of use ................................................................................................................18-18

19 Maintenance ................................................................................................ 19-1

19.1 Maintenance operations ...............................................................................................19-1
19.2 Short MTTR ..................................................................................................................19-1
19.3 Built-In Test (BIT) .........................................................................................................19-2
19.4 Alarms system ..............................................................................................................19-2
19.5 Troubleshooting ...........................................................................................................19-3

Ribbon Communications Inc. Proprietary xii

Useful information
This Apollo Reference Manual describes the key components of the Apollo platforms, including cards,
modules, accessories, and related capabilities. It also provides detailed descriptions for interpreting
indicator functions, enabling field personnel to troubleshoot hardware-related problems.

Related documents
 Apollo Documentation Suite
 STMS Documentation Suite
 LightSOFT® Documentation Suite

Contact information
Telephone Email

IP Optical +972-3-9268145 techdoc.feedback@rbbn.com

Documentation Group
IP Optical +972-3-9266000 on.support@rbbn.com
Customer Support

Revision history
Revision Section Description
1 N/A New

Ribbon Communications Inc. Proprietary xiii

1 OPT9932/OPT9914 platform
architecture
This section describes the layout and architecture of the OPT9932 and OPT9914 platforms (referred to
as OPT99xx in this section). Apollo OPT99xx platforms support ODU-XC applications as well as being
data-ready for MPLS-TP applications. System capacity starts at 5.6 Tbps/12.8 Tbps/16 Tbps
configurable, upgradeable to multiple 10 x Tbps capacity.
The OPT99xx service interface cards are a set of hybrid cards that can be used on the line or client
side, supporting OTN and Packet over OTN uplinks. Consistent with our modular distributed
architecture design philosophy, the OPT99xx platforms utilize the same fabric/controller and service
cards. Service cards or photonic modules can be installed in any of the I/O slots.
Apollo platforms have been designed to facilitate simple installation and easy maintenance. Hot
insertion of cards and modules enables quick maintenance and repair activities without affecting traffic.
The cage design and mechanical practice of all platforms conform to international mechanical
standards and specifications.
This section describes the layout and architecture of the OPT99xx platforms, focusing on the following
components:
 Platform layout
 Control and communications subsystems, including:
 Control
 Communications
 Timing and synchronization
 Universal fabric
 Cross-connect functionality
 Distributed forwarding architecture
 Packet processing
 Power feed subsystem
 Cooling subsystem
 Management system
The simplified block diagram of the OPT9914 is shown in the following figure.

Ribbon Communications Inc. Proprietary 1-1

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

OPT9914 block diagram

NOTE: All installation instructions, technical specifications, restrictions, and safety

warnings are provided in the Apollo Platform Installation and Maintenance Manuals. See
these manuals for specific instructions before beginning any Apollo installation.

1.1 OPT9932 platform layout

The OPT9932 platform is sized for ETSI racks, with 2000 mm height, 600 mm width, and 300 mm
depth. Redundant protection mechanisms include 1:1 protection for control, timing, and power
mechanisms, as well as 7 + 2, or 8+1 switching fabric protection. The OPT9932 platform includes the
following:
 32 universal slots for hybrid service cards that support a mix of Layer 1 and Layer 2 (MPLS-TP)
services, up to 400G/500G single-slot density, (correlated to fabrics configuration, 7+2/8+1) with
slot allocation optimized per application.
 2 xRCP/xRCP1 main controller cards, integrated with FM fabric modules.

Ribbon Communications Inc. Proprietary 1-2

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

 7 xFM universal fabric cards

 Both 2 xRCP/xRCP1 and 7 xFM create 7+2 or 8+1 fabric configuration providing 12.8 Tbps or
16 Tbps (with integrated xRCP/xRCP1), ready for 32/64 Tbps (cascading shelves). The universal
fabric supports OTN switching (ODUk cross-connect 0, 1, 2, 3, 4, Flex) and packet switching
(Layer 2 and MPLS-TP).
 12 xPFM-32 power supply cards. Enabling up to 14 kW future Maximal power utilization making
the platform ready for future high density and capacity transceivers.
 3 xFCM fan units, distributed across the platform for maximum cooling effect.
 One xMIM card providing an interface to external management.
 One xTAM card providing the physical interface to alarms and hardware ready clock devices,
including the following:
 BITS interface T3/T4 – E1 (framed) or 2MHz/1.5MHz (unframed).
 External 1588v2 (input or output) with the following interfaces: 10MHz clock, 1PPS, ToD,
1PPS monitor point.

OPT9932 platform layout and slot allocation

Ribbon Communications Inc. Proprietary 1-3

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

1.2 OPT9914 platform layout

The OPT9914 platform is sized for 19" racks, with 974 mm height (22U), 477 mm width, and 305 mm
depth. One OPT9914 platform can be installed in a 19" rack together with up to two OPT9608
platforms. Redundant protection mechanisms include 1:1 protection for control, timing, and power
mechanisms, as well as 1+3 switching fabric protection. The OPT9914 platform includes the following:
 14 universal slots for hybrid service cards that support a mix of Layer 1 and Layer 2 (MPLS-TP)
services, up to 400G single-slot density, with slot allocation optimized per application.
 2 xRCP/xRCP1 main controller cards, integrated with FM fabric modules.
 Two xFM plus two FE (Fabric Elements) on the xRCP/xRCP1 cards providing 5.6 Tbps universal
fabric for OTN switching (ODUk cross-connect 0, 1, 2, 3, 4, Flex) and packet switching (Layer 2
and MPLS-TP).
 Both 2 xRCP/xRCP1 and 2 xFM create 3+1 fabric configuration.
 xPFM-14 power supply cards. Enabling up to 7.2 kW future Maximal power utilization, making the
platform ready for future high density and capacity transceivers (e.g. 1Tbps).
 Two xFCM-14 fan units, distributed across the platform for maximum cooling effect.
 One xMIM card providing an interface to external management.
 One xTAM card providing the physical interface to alarms and hardware ready clock devices,
including the following:
 BITS interface T3/T4 – E1 (framed) or 2MHz/1.5MHz (unframed).
 External 1588v2 (input or output) with the following interfaces: 10 MHz clock, 1PPS, ToD,
1PPS monitor point.
 One CEM card providing the physical interface to external management and clock devices.

OPT9914 platform layout and slot allocation

Ribbon Communications Inc. Proprietary 1-4

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

1.3 OPT99xx control and communications

subsystem
The controller subsystem (xRCP/xRCP1) is responsible for the following functionality in the OPT99xx
platforms:
 Internal control and traffic processing, accomplished through the main processor that has the main
activation software and a nonvolatile backup memory (NVM).
 Internal platform and card control.
 Internal communications and processing.
 Timing and synchronization.
 ODUk cross connection or packet switching.
 High availability (HA), ensuring xRCP/xRCP1 switching from the active to the standby is
non-traffic affecting.
 Communication with external equipment and management.
 Comprehensive management functionality using General Communications Channel (GCC), out of
band management, or in-band management, with dynamic Open Shortest Path First (OSPF)
routing.
 Fault management, performance monitoring (PM), and maintenance.
 Optical and traffic planning tools with smooth automation and plug&play capabilities.
 Built-In Test (BIT).
 NE software and configuration backup.

1.3.1 OPT99xx control

The main controller subsystem supports central control, alarms, maintenance, and communication
functions. It also communicates with the control processors of the various cards using a master-slave
control hierarchy.
Each controller unit contains an NVM that stores a complete backup of both the system software and its
NE configuration. Through the NVM, the OPT99xx benefits from superior management and control
availability, ensuring that a faulty controller unit does not affect traffic.
Double redundancy in every platform can be obtained using a redundant NVM unit in the second
redundant controller subsystem, which is updated automatically on a regular basis. To maintain
synchronization, the operator can also initiate a manual NVM update whenever a change occurs in the
configuration.
The controller also provides the following functions:
 Manages software versions of the platform
 Downloads software to the I/O cards
 Collects PM and log information
 Manages SNCP protection scheme
 Collects LightPulse (AKA ONCP) information
 Controls the fabric matrix

Ribbon Communications Inc. Proprietary 1-5

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

In the OPT9932 and OPT9914, the platforms are operated in a redundant configuration, in which the
main controller card is protected with a second identical card. The redundant card contains a database
identical to the active card, and operates as a full capability standby control and communication card.

OPT99xx control subsystem

The controller subsystem enables easy software upgrades using a remote software procedure operated
from the STMS® management system. It can store several different software versions at the same time
and enables quick switchover between the different versions when required.

1.3.2 OPT99xx communications

The main control processor subsystem is responsible for communications with external NEs and
management stations.
Communications with other NEs is through one of the following mechanisms:
 GCC channel - embedded in each OTU/ODU link via OTN services cards
 In band management over Ethernet signals in Layer 2 cards
 External Data Communications Network (DCN)
Apollo performs IP forwarding between all network interfaces, including gateway management
interfaces. The management communication channel enables operators to integrate several platforms
with their own workstations, and to pass this management traffic through the Apollo system.
Apollo implements dynamic OSPF routing over the network interfaces to automatically determine the
routing table. OSPF support includes P2P protocol, (PPP) encapsulation of IP packets with high-level
data link control (HDLC), and framing over one of the management channels.
An Ethernet interface is used to communicate with STMS. The controller subsystem can also
communicate with a desktop or laptop PC-based craft terminal (Apollo CLI) via serial interface or
Ethernet.

Communications module
All OPT99xx platform configurations work with a communications module, featuring:
 Electrical interface connectors that are integrated into the I/O modules, eliminating the need for
separate electrical interface modules
 Easy routing of external management interfaces
 A monitoring system for acceptance test purposes
 Hot insertion of cards and modules to support quick maintenance and repair activities, without
affecting traffic

Ribbon Communications Inc. Proprietary 1-6

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

1.3.3 OPT99xx flexible support for management mixtures

Management information is transmitted from the NMS/EMS to individual NEs through one of the
following mechanisms:
 External DCN
 GCC channel: Apollo platforms support in band management utilizing the GCC incorporated in
Layer 1 service cards (either standalone or fabric I/O cards). The GCC enables remote
management of equipment at any site where optical channels are dropped. This can increase
margins and extend distances of optical links as OSC filters are eliminated. Apollo supports
GCC0, GCC1, and GCC2. GCC1 and GCC2, integrated in the ODU overhead bytes, are usually
used when transmitting management over a third party domain that is not based on vendor
equipment. GCC0 is transmitted over OTU overhead bytes and terminated every time the OTN
signal is terminated. GCC is available for OTU1, OTU2, OTU3, and OTU4 signals.
 In band Ethernet channel: OPT99xx platforms can transmit management information over a
dedicated VLAN via in band Ethernet signals. In band Ethernet can be transmitted over GbE, 10
GbE, and 100 GbE interfaces. In band Ethernet management is only available when using Layer 2
cards. The Layer 2 cards terminate the VLAN and extract the management information.
Management infrastructure, routing communications, and internal system control traffic all go
through the internal link between the xRCP/xRCP1 and the XC Packet Control Processor Module
(XPT-CPM) on the data cards.
The Apollo OPT99xx platforms fully integrates the GCC, in band Ethernet, and external DCN
management channels, thus providing the operator with the flexibility to choose the most appropriate
management channel. Operators can even mix the different channels in a network or in the same
platform.

1.3.4 OPT99xx routing and forwarding functionality

The routing and forwarding capabilities of the OPT99xx platforms are based on standard OSPF
dynamic routing, suitable for small, medium, and larger networks, and including a richer set of features
for network communications management.
In the OPT99xx platforms, the main control processor subsystem is responsible for communications
with external NEs and management stations. Communications with other Apollo NEs is via the GCC in
each OTN link, in band Ethernet, or external DCN.
An Ethernet interface is used to communicate with STMS. The controller subsystem can also
communicate with a desktop or laptop PC-based craft terminal (Apollo CLI) via a serial interface or
Ethernet. It also provides alarm outputs. Some of these network communications components and their
functionality are described in this chapter.

Ribbon Communications Inc. Proprietary 1-7

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

1.3.5 OPT99xx management channel with dynamic OSPF

A management channel enables operators to integrate several platforms with their own workstations
and to pass this management traffic through the Apollo OPT99xx platforms. The operator sets up an
IP–based DCN to carry IP packets between the management stations and the NEs. The DCN is
composed of Embedded Communication Channels (ECCs) supported by the equipment itself and an
external DCN supported by standard data equipment.
The Apollo performs IP forwarding between all network interfaces, implementing dynamic OSPF routing
over these network interfaces to automatically determine the routing table. OSPF can be configured for
any subset of network interfaces and supports:
 P2P and broadcast interfaces
 Up to four OSPF areas
 Address summarization
 Area Border Router functionality
 Autonomous System Border Router functionality, including redistribution of static routes
 Loopback address as a router ID
 Configuration of HELLO protocol parameters
 "Passive" interfaces to allow distribution of routes to attached devices
OSPF functionality enables a wide range of DCN configurations, adds resiliency to management
communications between NEs and the management stations, and reduces the ECC load, for a
significant improvement in management performance and NE capacity.
Under dynamic ECC routing, NEs ping each other through the available ECC interfaces and build their
own routing tables. Working with dynamic routing tables that respond to real time circumstances
simplifies ECC planning and maintenance, and reduces the ECC load by making it unnecessary to
reserve ECC protection paths in advance. There is also no need to plan ECC rings, since dynamic ECC
routing enables NEs to automatically set up new routes if the existing ones fail.

1.4 OPT99xx timing and synchronization

Apollo OPT99xx platforms feature a central synchronization subsystem that provides fully redundant
high quality system timing to all traffic cards and functions.
Timing and alarm interfaces of the OPT99xx shelves are located on timing and alarm module (xTAM).
The xTAM is hardware ready for terminating/driving BITS (T3/T4) and 1588v2 (Clk, 1PPS, ToD, 1PPS
monitor) standard interfaces to/from the Central Timing Module (xCTM) residing on the xRCP/xRCP1.
Timing is distributed redundantly from the xCTM to all traffic cards requiring synchronization, minimizing
unit types and reducing operation and maintenance costs.
The following figure shows the timing signals distribution in the OPT99xx platforms.

Ribbon Communications Inc. Proprietary 1-8

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

OPT9914 timing distribution

The xCTM and internal and external timing paths are fully redundant. The distributed BIT mechanism
ensures top performance and availability.
To provide a reliable timing source, the OPT99xx is hardware ready to support multiple synchronization
reference options. Up to seven of the following timing references can be monitored simultaneously by
each OPT99xx platform:
 2 x 2MHz/1.5MHz (T3) external timing input sources
 2 x E1 (T3) external timing input sources
 1588v2 (In clock, 1PPS, ToD) External
 1588v2 (PTP massages)
 2 x Reference clock from Line cards (like Sync-E/Sync-O)
 Mate CTM (Mate xRCP/xRCP1)
High Availability of the timing system is guaranteed by the fact that the OPT99xx is always operating
with two xRCP/xRCP1 cards in the shelf. HA includes also the xCTM function redundancy. The active
xCTM always resides on the active xRCP/xRCP1 and HA switch-over refers both to xRCP/xRCP1 and
xCTM logics.
The xCTM provides direct control over the source selection (which it receives from the system software)
and the frequency control loop. The definition of the synchronization source depends on the source
quality and on the synchronization mode, according to the network timing topology.
The operator can remotely manage network synchronization and can select and determine the priority
for each OPT99xx timing source reference.

Ribbon Communications Inc. Proprietary 1-9

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

Synchronization references are classified at any given time according to a predefined priority and
prevailing signal quality. The Apollo OPT99xx synchronization subsystem synchronizes to the best
available timing source using the Synchronization Status Message (SSM) protocol. The system is
synchronized to this central timing source.
In addition, the system provides synchronization outputs to synchronize external equipment within the
site. Two external T4 interfaces can provide 2 MHz/E1 external timing as required. These outputs can
be used to synchronize any peripheral equipment or switch.
Apollo supplies a 4.6 ppm stable holdover mode when all alternative synchronization sources are
temporarily unavailable.
Apollo default clock accuracy complies with applicable ITU-T and Telcordia standards at the network
level. Optional G.812 or G.811 synchronization quality can be provided using additional external units.
In addition, the system infrastructure supports distributions of phase and frequency synchronization via
1PPS and ToD interfaces.

1.5 OPT99xx universal fabric system

The heart of the OPT99xx product family is a powerful, high capacity, non-blocking universal fabric. The
universal fabric supports ODU cross connecting (packet and Hybrid XC will be supported in a future
release). The fabric system is built of xFM cards and Fabric Elements (FEs) residing on the
xRCP/xRCP1 cards. Each xRCP/xRCP1 is equipped with a single FE.
FEs on the xRCP/xRCP1 operate as independent units and have no direct reference to the
xRCP/xRCP1 functions. That means the FE on both xRCP/xRCP1 cards, main and standby, are always
operating.
The OPT9932 platform is equipped with seven xFM cards working together with the two FEs on the
xRCP/xRCP1 in a 7+2 or 8+1 protection scheme.
Two xFM cards are installed in the OPT9914 platform that work together with the two FEs on the
xRCP/xRCP1 in a 3+1 protection mode. The fabric capacity is 5.6 Tbps (in the first release xIO cards
are of 200 Gbps, so only 2.8 Tbps is used).
All xIO cards are directly connected to all fabric cards and elements (FEs) with 36 lanes:
 In the OPT9932 with 9 FEs (7 xFM cards + 2 FEs on xRCP/xRCP1) the connection includes : 9 x
4 = 36 lanes; OPT9932 can work in two modes:
 7+2 FEs – provide up to 400 Gbps per slot, up to two FEs failure will not cause system traffic
degradation
 7+1 FEs – provide up to 500 Gbps per slot, up to one FE failure will not cause system traffic
degradation
 In the OPT9914 with 4 FEs (2 xFM cards + 2 FEs on xRCP/xRCP1) the connection includes : 4 x
9 = 36 lanes; OPT9914 has a single mode:
 3+1 FEs – provide up to 400 Gbps per slot, up to one FE failure will not cause system traffic
degradation
The following functionality is provided:
 Each xIO card works with all FEs in the system
 Traffic load is balanced over all active links of the fabric
The following figures show the simplified OPT9932 and OPT9914 internal traffic connectivity. It
provides an overview of both the physical and functional partitioning of the system. Each I/O slot can
accommodate any type of card with 400/500 Gbps bitrate and service.

Ribbon Communications Inc. Proprietary 1-10

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

OPT9932 universal fabric connectivity

OPT9914 universal fabric connectivity

1.6 OPT99xx cross-connect functionality

Cross-connects are used to define connectivity between tributaries and L1 interfaces having compatible
bandwidth. The connectivity can be between tributaries on the same card or between different cards via
the fabric matrix (ODU XC). The Apollo OPT99xx fabric (xFM) enables efficient and cost-effective
cross-connect capabilities with ODUk granularity for all tributary signals.
There are three XC modes in the Apollo OPT99xx:
 Fixed XC: configured by the NE when there is one single fixed connectivity, for example XC in
passive optical or amplifier cards
 User-configurable XC: connection between cards via the fabric, or connection between services
in a card
 Signaling/dynamic XC: created and deleted by signaling protocols
The traffic cross-connect functions are implemented by the non-blocking high capacity cross connect
xFM fabric and FEs on the xRCP/xRCP1 cards. Four cards in the OPT9914 are configured in a 3+1,
(Nine for OPT9932 in 7+2 or 8+1) protection scheme that provides a capacity of 5.6Tbps (OPT9914),
12.8Tbps or 16Tbps (OPT9932) with 400 Gbps or 500 Gbps per I/O slot.

Ribbon Communications Inc. Proprietary 1-11

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

The fabric matrix cards receive the traffic from the various xIO cards installed in the platform through
wideband buses, using a format that does not depend on the type of xIO card installed in any specific
slot. At any time, the main and protection card are active (that is, switch the traffic).
The fabric supports ODU XC at the ODUk level for Layer-1 services and ODU-Flex for Layer-2 services.
The XC is supported for cards residing on the same platform.

Examples of different ODU XC options through the fabric cards

1.7 OPT99xx Lite Packet support

OPT9914 and OPT9932 support Lite Packet capabilities over existing fiber and HIO cards. Lite Packet
features provide E-Line services over ODU XC domains. Lite Packet for Apollo platforms enhances the
network performance with the following capabilities:
 LAG-based resiliency for packet connectivity
 I/O port protection for packet ports that are not part of a LAG configuration
 Enhanced traffic grooming for traffic aggregation on Layer 2
 Hitless BW adaptation using Layer 2 CIR/EIR and G.HAO for hitless BW adaptation for ODUflex
The primary application for which Lite Packet features were designed is a classic router interconnect
across an ODU XC domain. Lite Packet capabilities and enhancements are implemented through a
combination of software and hardware functionality.
A license is required to enable Lite Packet.

Ribbon Communications Inc. Proprietary 1-12

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

1.8 OPT99xx power feed subsystem

OPT99xx platforms are designed to support high power consumption for future 400 Gbps and 1 Tbps
transceivers, thus they support up to 9.6 kW in the OPT9914 and up to 14.4 kW in OPT9932, (the
typical power consumption is significantly lower).
Multiple Power Filtering Modules (xPFM) are used to connect power to the OPT99xx platforms. In the
OPT9914, the power sources are connected to the external Power Distribution Unit (PDU) and the
output from the PDU is connected to the xPFMs in the platform. In the OPT9932, the power sources are
connected directly to xCBM (housed in the platform) that feeds the xPFMs. The xCBMs provide a PDU-
like functionality for the OPT9932.
OPT99xx features a distributed fully redundant power feed subsystem. Two different power sources
(Source A and Source B) feed the xPFMs, connected in pairs in a 1:1 protection scheme. In the
OPT99xx platforms, the power distribution was divided into separate areas such that each pair of
xPFMs is responsible to supply power to one area. This enables customers to use the "Install as you
Grow" approach and turn on more xPFMs as additional cards are installed in the system.
The xPFM filters and monitors the -48 VDC nominal input voltage, distributes it to cards, protects the
system from external abnormal voltage connectivity and provides Hold up capacitors.
Two types of xPFM modules are available for the OPT99xx according to the platform type:
 xPFM-14 - for the OPT9914; 6 units are required for a fully populated platform
 xPFM-32 - for the OPT9932; 12 units are required for a fully populated platform
Both modules have the same electronic design and differ only in the 48 VDC power input connection
and mechanical dimensions.

NOTE: The generic name xPFM is used to describe features that are common to both
types: xPFM-14 and xPFM-32.

The output voltage of a redundant xPFM pair is connected together to a bus-bar that feeds an area in
the shelf (specific slots of its responsibility). The module with the higher voltage provides the power to
the shelf area. If a fault occurs in the active xPFM, the standby takes over and is capable of supplying
the full power to that area.
The following figure shows the power distribution structure in the OPT9914. In this figure, the color of
an xPFM-14 pair is identical to the color of the corresponding cards it is feeding. For example, the color
of the pair xPFM-14 A1 and xPFM-14 B1 is blue and it is feeding the following cards: xMIM-L, xTAM,
xMIM-R, xFCM-M, xRCP-A, xRCP-B, xFM-1, xFM-2, xIO-00, and xIO-01.

Ribbon Communications Inc. Proprietary 1-13

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

Power distribution in the OPT9914

In the OPT9914, the power sources are connected to the xPFM-14 cards via a PDU55AL, PDU77AL, or
PDU99 unit. In the OPT9932, the power sources are connected directly to xCBM modules, saving the
need for an external PDU.
In the OPT9932, an xCBM module connects the input power source to the xPFM-32.
There are 12 independent xCBMs in the platform arranged in six pairs. To ensure platform power
redundancy each module in a pair must be connected to a different source. The xCBM provides a PDU-
like functionality for the OPT9932, saving the need for an external PDU. Each xCBM feeds an xPFM-32
installed under it, which in-turn feeds the cards (xRCP, xFM, xMIM, xIO, etc.) and subsystems in the
OPT9932. The two leftmost pairs must always be connected to power, as they provide power to
common cards and subsystems.
The left xCBM in a pair connects to source A and the right to source B. The following figure identifies
the xCBMs and the corresponding power sources. The colors of the xPFM-32 cards correspond to
colors of the cards they are feeding.

Ribbon Communications Inc. Proprietary 1-14

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

Power distribution areas in the OPT9932

1.9 OPT99xx air cooling subsystem

The Apollo ventilation system is designed with fan units that efficiently pump cold air to flow over the
cards and components and cool them. The OPT9932 is divided into three independent cooling areas,
and that of the OPT9914 into two, without thermal interaction between them.
The routes of cold and hot air in the system are schematically shown in the following figures. Cold air
flow is marked blue; hot flow is marked red; air flow through the platforms is marked orange.
In the OPT9932 platform, fan units in the upper part of the platform pump cooling air from the top part
over the components; the hot air is expelled through the exhaust in the upper mid-section. Fan units in
the middle part pump cooling air from the right; the hot air is expelled through the exhaust to the left.
Fan units in the lower part pump cooling air from the bottom over the components; the hot air is
expelled through the exhaust in the lower mid-section.

Ribbon Communications Inc. Proprietary 1-15

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

OPT9932 Cold and hot air routes in the ventilation system

Ribbon Communications Inc. Proprietary 1-16

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

The OPT9932 cooling subsystem includes three fan trays:

 xFCMH-32 - horizontally installed at the upper area of the OPT9932. Draws air from an air duct at
the middle of the chassis (under the upper xIO card cage) and pumps it through the vertically
mounted cards xIO, xPFM-32, and xCBM cards through the top of the chassis.
 xFCMH-32 - horizontally mounted at the bottom of the OPT9932. Draws air from an air duct at the
lower part (under the common card cage: xRCP/xRCP1, xFM, etc.) and pumps it through the
vertically mounted cards (lower xIO cage) through the bottom of the chassis.
 xFCMV-32 - vertically mounted at the middle-left side of the OPT9932. Draws air from the middle-
right side of the chassis and pumps it through the horizontally mounted cards (xRCP/xRCP1, xFM,
etc.) through the left side of the chassis.

In the OPT9914 platform, fan units in the upper part of the platform pump cooling air from right and
expel the hot air through the exhaust to the left. Fan units in the lower part pump cooling air from the
bottom over the components; the hot air is expelled through the exhaust in the mid-section.

OPT9914 Cold and hot air routes in the ventilation system

The OPT9914 cooling subsystem includes two fan trays:

 xFCMH-14 - horizontally installed at the bottom of the OPT9914. Draws air from an air duct at the
middle of the chassis and pumps it through the vertically mounted cards (xIO) through the bottom
of the chassis.
 xFCMV-14 - vertically mounted at the upper-left side of the OPT9914. Draws air from the upper-
right side of the chassis and pumps it through the horizontally mounted cards through the left side
of the chassis.

NOTE: The generic term xFCM is used to describe functions that are common to all xFCM
types.

To increase the OPT99xx reliability, air is pumped into the system by the xFCMs through air filters that
reduce dust and air particles that can be accumulated on the fans.

Ribbon Communications Inc. Proprietary 1-17

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

CAUTION: Filter cleaning intervals must be strictly observed, as clogging by trapped

particles can severely impair equipment reliability and performance.

OPT9932 location of fan trays and cooling areas

Ribbon Communications Inc. Proprietary 1-18

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

OPT9914 location of fan trays and cooling areas

The different xFCM types have the same electrical design and principal of operation and differ only in
the number of fans and mechanical layout. Because there is no redundancy for each xFCM, high
availability must be guaranteed by each fan unit. This is achieved by a separate power supply and
controller for each fan in the xFCM.
xFCM fan control mechanism is based on temperature sensors located on each common and xIO card
in the OPT99xx platforms. The sensor measures the ambient temperature in each card and reports it to
the active xRCP/xRCP1. The xRCP/xRCP1 processes this data and in-turn sends control signals to the
corresponding fan controller. The controller can change the speed of the fan in 16 steps to keep the
temperature in the allowed range. The speed change is controlled by changing a Pulse Width
Modulator (PWM).
The xFCM is turned into turbo mode (fans operate in highest speed) in case a major failure is detected
like, failure of the xRCP/xRCP1, control bus, etc.

Ribbon Communications Inc. Proprietary 1-19

 Apollo Reference Manual OPT9932/OPT9914 platform architecture

1.10 OPT99xx management system

Description
The xMIM is the Management Interface Module card of the OPT99xx family. It is connected to both
xRCP/xRCP1 cards and provides a physical interface between the OPT99xx platforms and the external
management (STMS).

Functions
 Out-of-band management Ethernet port supporting 10/100/1000 Mbps, connected to the STMS.
 Four slave management interfaces for subtending platforms; enables managing five shelves with
a single IP (future option).
 Redundancy of management interfaces by a second xMIM (optional); both operate together in a
1:1 protection mode (future option).

Ribbon Communications Inc. Proprietary 1-20

2 OPT9932/OPT9914 common cards
The OPT99xx family includes cards and modules that provide its common functionality, such as routing
and control, management and timing connections, power supply, air cooling, control required for
operation, and cross-connect and packet switching fabric.

2.1 xRCP/xRCP1
Supported platforms
 OPT9932
 OPT9914

Description
The xRCP/xRCP1 is the central control component in the OPT99xx platforms, providing the main
system processor responsible for essential system management, timing, and control. The card supports
timing functionality for a wide range of synchronization standards by the Central Timing Module (xCTM)
residing on it. In addition, xRCP/xRCP1 cards include a Fabric Element (FE) used as part of the
OPT99xx system fabric.
xRCP/xRCP1 cards enable comprehensive management communication functionality with dynamic
OSPF routing. These cards are responsible for communications with external NEs and network
management (STMS) communication. xRCP/xRCP1 cards can be configured for 1:1 redundancy. All
connectivity from the xRCP/xRCP1 to any card is kept redundant via the dedicated internal
communication links.

Functions
The xRCP/xRCP1 provides the following main functions:
 Control:
 Control and alarms from/to all other cards in the platforms
 Software versions management
 Downloads SW to the managed xIO cards
 Collects PM and log information
 SNCP traffic protection
 Fabric control
 Collects ONCP information
 Supports xRCP/xRCP1 redundancy by two cards operating in 1:1 protection scheme (High
Availability - HA)
 Management:
 Connectivity to the STMS/LCT-STMS management systems
 Supports DCN network functionality
 Management of subtending shelves (future)

Ribbon Communications Inc. Proprietary 2-1

 Apollo Reference Manual OPT9932/OPT9914 common cards

 Timing:
 Distributes timing signals to all cards
 Synchronizing 3rd party equipment via external timing interfaces (on xTAM)
 Hardware ready to support various clock signals including: BITS (T3/T4), 1588v2 (10 MHz,
1PPS, ToD), Sync-E
 Redundancy via xCTM located on each xRCP/xRCP1
 Fabric system:
 FEs on the xRCP/xRCP1 cards are part of the universal fabric
 7+2 or 8+1 fabric protection scheme available in the OPT9932
 3+1 fabric protection scheme available in the OPT9914
 Provides connectivity and fabric switching functions between xIO cards in OPT99xx platforms

WARNING: When an OPT99xx platform is configured to operate in ODU-XC, removal of

both xRCP/xRCP1 cards and insertion of one or both cards will cause a traffic down time
of about 3 minutes.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 2-2

 Apollo Reference Manual OPT9932/OPT9914 common cards

Ports
Port indicators
Marking Connector Functions
CONSOLE RJ-45 connector Serial RS-232 communication port for use by technical support
personnel (debug, maintenance, etc.).
EXP1 RJ-45 connector L2 debug port
EXP2 RJ-45 connector L3 debug port
CRAFT RJ-45 connector Management interface for connecting to an LCT

LED indicators
Marking Item Functions
Controller LEDs
ACT Green LED On -
During upload time
xRCP/xRCP1 is active and has no BIT failure
Off - xRCP/xRCP1 has BIT failure
SBY Yellow LED On -
1. During upload time
2. xRCP/xRCP1 configured as SB
Blinks - One of microswitches is open
Off – xRCP/xRCP1 is defined as Active
FAIL Red LED On - xRCP/xRCP1 has BIT failure or has not come out of reset
Off - no BIT failure
Fabric LEDs
ACT Green LED On - FE (on this xRCP/xRCP1) is Active, both micro-switches are
close and no BIT failure
Off -
1. During upload time
2. One of the micro-switches is open
3. Fabric element has BIT failure
SBY Yellow LED On - During upload time or green shutdown
Off -
1. Fabric element is in service (Active)
2. Fabric element has BIT failure
FAIL Red LED On - Fabric element has BIT failure or has not come out of reset
Off - no BIT failure on the fabric element
SD LED
SD WRITE Blue LED Blinks - Writing operation on SD card
Off - No writing operation on SD card
Ethernet (RJ-45) link speed and port traffic activity LEDs
Rate Link and Speed Activity LED color
LED color
1 Gbps Green - solid Yellow – blinks
100 Mbps Yellow - solid Yellow – blinks

Ribbon Communications Inc. Proprietary 2-3

 Apollo Reference Manual OPT9932/OPT9914 common cards

2.2 xFM
Supported platforms
 OPT9932
 OPT9914

Description
The xFM card is part of the universal fabric in <OPT9XX> platforms together with FEs residing on the
xRCP/xRCP1 cards.

Functions
The xFM provides the following main functions:
 TDM (ODU) and data (packet) matrix
 Multicast transmission at the fabric level
 Fabric redundancy scheme (HA)
 200G per xIO slot (phase 1) and 400G (phase 2)
 Card can be removed without affecting traffic
Note that the FE on each xRCP/xRCP1 is always active, even on the xRCP/xRCP1 that is in Standby
mode. From this perspective the FEs on the xRCP/xRCP1 are independent entities, physically located
on the xRCP/xRCP1 and powered from its circuits.
The traffic is coming in via the xIO card, which converts it to a common structure regardless of the
ingress traffic type. This fabric can process this common type. In the opposite, the fabric provides the
traffic in the common structure to a xIO card that translated the traffic back to a format required at the
egress port of this card.
The xFM also transmits multicast traffic as required to different parts of the fabric system. In addition, it
is responsible to transmit multicast traffic to required xIO cards connected to the fabric system.
The xFM and FE on the xRAPs operate in N+m protection mode. All fabric elements in the system are
active and forwarding traffic. In case an xFM, an FE on an xRCP/xRCP1, or a link fails, the traffic
continues to flow through the available links. The OPT9914 operates with 4 FMs in a 3+1 protection
scheme; it means that if one of the fabric elements is not active the system continues to work without
performance degradation.

Ribbon Communications Inc. Proprietary 2-4

 Apollo Reference Manual OPT9932/OPT9914 common cards

Card views
General view

Front panel

Ports
Marking Item Functions
ACTIVE Green LED On - the xFM is Active, both micro-switches are closed and no BIT
failure was detected.
Off -
1. During upload time
2. One of the micro-switches is open
3. xFM has BIT failure
NOT IS Yellow LED On - During software upload
Blinks - one µswitch is open
Off -
1. In Service (xFM is Active)
2. xFM has a BIT failure
FAIL Red LED On - xFM has BIT failure or has not come out of reset
Off - no BIT failure

Ribbon Communications Inc. Proprietary 2-5

 Apollo Reference Manual OPT9932/OPT9914 common cards

2.3 xMIM
Supported platforms
 OPT9932
 OPT9914

Description
The xMIM is the connection unit between the OPT99xx family and the external management. It is
installed at the upper part of the OPT9914 section or at the middle section of the OPT9932 platform
(near the xRCP-A).

Functions
The xMIM provides the following main functions:
 Out-of-band management interface for connecting an STMS
 Four management ports for cascading up to four OPT96xx or OPT9914 platforms (future)
 Connects to both xRCP/xRCP1 cards to support service continuity in case one of the
xRCP/xRCP1 fails
 Management redundancy can be supported by two xMIM cards working in a 1:1 protection
scheme (future)

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 2-6

 Apollo Reference Manual OPT9932/OPT9914 common cards

LEDs
Marking Item Functions
Card LEDs
ACT Green LED On –
1. During upload time
2. xMIM is Active and no BIT failure
Off - xMIM has BIT failure
SB Yellow LED On -
1. During upload time
2. xMIM is Active and no BIT failure
Off - xMIM is defined as Active
FAIL Red LED On -
1. During upload time
2. xMIM has BIT failure
Off - no BIT failure
IMG RJ-45 connector Out-of-band management Ethernet interface
(10/100/1000BaseT) for connecting to an element
management station (STMS) or a CLI terminal.
MULTI SHELF Four RJ-45 Management interface (10/100/1000BaseT) for connecting
MNG. 1 to 4 connectors management to up to 4 subtending shelves.
RJ45 Connector LEDs
Port link Green LED Indicate the port link rate:
 3 blinks and pause - 1 Gbps
 2 blinks and pause - 100 Mbps
 1 blink and pause - 10 Mbps
Off - During upload time
Port Activity Yellow LED Indicate the port activity:
Blinks - Activity
Off -
1. During upload time
2. No Activity

2.4 xTAM
Supported platforms
 OPT9932
 OPT9914

Description
xTAM is the Timing and Alarm interfaces Module, serving as the connection between the OPT99xx
platforms and the external world. It provides interfaces for timing and alarms. The xTAM is installed at
the upper part of the OPT9914 or middle part of the OPT9932 between the two xMIM cards. It is
connected to both xRCP/xRCP1 cards and provides a physical interface between the OPT99xx
platforms, the synchronization system (BITS, 1588v2), and the alarms system (severity, in/out).

Ribbon Communications Inc. Proprietary 2-7

 Apollo Reference Manual OPT9932/OPT9914 common cards

Functions
The xTAM features:
 Hardware ready for terminating/driving BITS (T3/T4) and 1588v2 (Clk, 1PPS, ToD) standard
interfaces to/from the xCTM.
 Terminates Alarm In (through opto-couplers) and drives system and Alarms Out directly to the
client or through a PDU relay dry contacts.
 Provides a LED Test pushbutton to check all LEDs in the system.
 Provides an ACO pushbutton that stops the buzzer of the system.
The xTAM provides the following main functions:
 Timing and synchronization inputs and outputs, including:
 BITS-T3/BITS-T4 (for future support)
 1 PPS for supporting IEEE 1588v2 (for future support)
 ToD for supporting IEEE 1588v2 (for future support)
 10 MHz clock for IEEE 1588v2 (for future support)
 Alarm interfaces and indications, including:
 Severity alarm outputs (Critical, Major, Minor)
 External alarm outputs and inputs:
 4 output alarms (relay dry contacts)
 4 input alarms (opto-couplers)
 LEDs for displaying the operation and alarms of the system
 Activations, including:
 LED tests for the entire platform
 ACO

Card views
General view

Ribbon Communications Inc. Proprietary 2-8

 Apollo Reference Manual OPT9932/OPT9914 common cards

Front panel

LEDs
Marking Item Functions
Card LEDs
ACT Green LED On:
 During upload time
 xTAM is Active and no BIT failure
Off: xTAM has BIT failure
FAIL Red LED On:
 During upload time
 xTAM has BIT failure
Off: no BIT failure
System Severity Alarm LEDs
CR Red LED On: System has a Critical Alarm
Off:
 During upload time
 no Alarms
MJ Orange LED On: System has a Major Alarm
Off:
 During upload time
 no Alarms
MIN Yellow LED On: System has a Minor Alarm
Off:
 During upload time
 no Alarms

Ports and pushbuttons

Marking Connector Functions
1PPS OUT DIN 1.0/2.3 connector 1PPS output signal for supporting Ethernet timing per IEEE
1588v2 standard (for future support).
10 MHz IN/OUT DIN 1.0/2.3 connector 10 MHz input/output signals for supporting Ethernet timing per
IEEE 1588v2 standard (for future support).
ToD & 1PPS RJ-45 connector Time of Day and 1PPS input/output signals for supporting
IN/OUT Ethernet timing per IEEE 1588v2 standard (for future support).
BITS (T3/T4) 1 RJ-45 connector Main timing input/output clock using an E1/2MHz/1.5MHz
signal (for future support).
BITS (T3/T4) 2 RJ-45 connector Additional timing input/output clock using an E1/2MHz/1.5MHz
signal (for future support).
ALARMS 36-pin VHDCI female Connects alarm input and output lines via a RAP or directly to
connector the client.

Ribbon Communications Inc. Proprietary 2-9

 Apollo Reference Manual OPT9932/OPT9914 common cards

Marking Connector Functions

LED-TEST Pushbutton Turns on all LEDs located on cards/modules installed in the
platform, for test purposes.
ACO Pushbutton Used to temporarily disable the buzzer and set off the
corresponding alarm LED when an alarm condition is present.
The buzzer is activated again when a new alarm condition is
detected.

2.5 xTEM
Supported platforms
 OPT9932

Description
The xTEM is an optional extension module for the xTAM card. The OPT9914 uses a PDU for power
supply and alarm connectivity. The OPT9932 is designed with direct connections to the power sources
(via the xCBM modules) and PDU is not used with it. To support client alarm connectivity and other
PDU functions, the xTEM emulates PDU-like functionality for the OPT9932. The xTEM is an optional
card in the OPT9932. In addition to client alarms, it provides a buzzer and system alarms LEDs.

Functions
 Alarms:
 Severity alarms – Critical, Major, Minor
 4 x output alarms
 4 x Input alarms
 Buzzer
 LED test pushbutton
 System severity LEDs: Critical, Major, Minor.

Ribbon Communications Inc. Proprietary 2-10

 Apollo Reference Manual OPT9932/OPT9914 common cards

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 2-11

 Apollo Reference Manual OPT9932/OPT9914 common cards

LEDs

Marking Item Functions

Card LEDs
ON Green LED On - xTEM get power
Off - no power
System Severity Alarm LEDs
CRITICAL Red LED On - System has a Critical Alarm
Off - no Alarms
MAJOR Orange LED On - System has a Major Alarm
Off - no Alarms
MINOR Yellow LED On - System has a Minor Alarm
Off -no Alarms

Connectors and pushbuttons

Marking Connector Functions

xTAM 36-pin SCSI connector Connects the alarm input and output lines between the xTAM
and xTEM.
CLIENT 36-pin VHDCI connector Connects the alarm input and output lines to the client's alarm
collecting facility.
LED-TEST Pushbutton Turns on all LEDs located on cards/modules installed in the
platform, for test purposes.

2.6 xPFM-14
Supported platforms
 OPT9914

Description
The xPFM-14 is an input power filter for the DC voltage connected to the OPT9914. Each platform has
up to six xPFM-14 units for redundancy purposes. To support redundancy, the xPFM-14 work in pairs,
where each module is connected to a different power source. Each pair is responsible to supply power
to one feed area in the OPT9914. The output voltages of each module in a pair are connected together
and the module with the higher voltage supplies power to the dedicated area. In case of a failure in the
active xPFM-14, the standby module takes over and supply the full power. The faulty unit can be
replaced without affecting traffic.

Functions
The xPFM-14 provides the following main functions:
 Input DC voltage filtering (-48 V)
 Control and alarms
 Temperature sensing
 Input voltage monitoring

Ribbon Communications Inc. Proprietary 2-12

 Apollo Reference Manual OPT9932/OPT9914 common cards

 Reverse polarity protection

 Surge protection (2 kV line to line, 4 kV line to ground)
 Redundancy between PFM units
 Passive 10 msec Hold-up capacitors
 Under voltage detection
 Lightning strike protection
 Input power measurement
 Fail indication

Card views
General view

Front panel

LEDs

Marking Item Functions

POWER ON Green LED Lights steadily when the xPFM-14 input supply voltage through the
POWER IN connector is in the allowed range.
FAIL Red LED Normally off. Lights steadily when a fault is detected in the unit.
POWER IN 5W5 D-type connector Connects DC input power to the filter in the unit.

Ribbon Communications Inc. Proprietary 2-13

 Apollo Reference Manual OPT9932/OPT9914 common cards

2.7 xFCM-14
Supported platforms
 OPT9914

Description
The OPT9914 has two types of fan trays that provide cooling air to the platform: xFCMV-14, and
xFCMH-14. The two types have identical electronic design and cooling and control functionality, and
differ only in physical structure and number of fan units. The xFCMV-14 includes six fans and the
FCMH-14 eight. The fans are fed through circuits that improve the system's performance and support
its redundancy.

NOTE: The generic name xFCM-14 is used through this manual to describe functions
related to both card types.

Functions
Features of the xFCM-14 include:
 Separate power supply for each fan unit
 Each adjacent pair of fans have a control of its own:
 Multiple speed levels are defined for each pair; see System Specifications for details
 The levels are controlled by the active xRCP/xRCP1 via a control bus
 Separate psophometric filter with a separate fuse for each fan
 Large capacitor with a fuse on the DC supply bus
 Parallel dual inrush current circuit with a separate fuse for each circuit
 Hold up capacitors (serves the xPFM-14)
A controller in the active xRCP/xRCP1 controls the fans operation. If one of the fans fails, the remaining
start to operate in turbo mode and the fail LED lights until the xFCM-14 is replaced. If done in a few
minutes, the xFCM-14 can be extracted and replaced without interrupting the OPT9914 operation (hot
swapping).

WARNING: Do not leave the system without one of the fan tray units for more than five
minutes.

Ribbon Communications Inc. Proprietary 2-14

 Apollo Reference Manual OPT9932/OPT9914 common cards

Card views
General view

General view

Ribbon Communications Inc. Proprietary 2-15

 Apollo Reference Manual OPT9932/OPT9914 common cards

xFCMH-14 front panel

xFCMV-14 front panel

Ribbon Communications Inc. Proprietary 2-16

 Apollo Reference Manual OPT9932/OPT9914 common cards

LEDs
xFCMH-14

Marking Item Functions

ACTIVE Green Lights steadily when the card is powered and operating normally.
LED
FAIL Red LED Normally off. Lights steadily when a fault is detected.

xFCMV-14

Marking Item Functions

ACTIVE Green Lights steadily when the card is powered and operating normally.
LED
FAIL Red LED Normally off. Lights steadily when a fault is detected.

2.8 xCBM
Supported platforms
 OPT9932

Description
The xCBM provides power input terminals for connecting the - 48 VDC power source to the xPFM-32
card. Each xPFM-32 connects to an independent xCBM, totaling up to 12 xCBM modules in an
OPT9932 platform. The OPT9932 comes with 12 xCBM modules installed in the platform.
You must connect power source input cables and install the circuit breaker on each xCBM. These
procedures are described in the OPT9932 Installation and Maintenance Manual.
There are 12 independent xCBMs in the platform arranged in six pairs. To ensure platform power
redundancy each module in a pair must be connected to a different source. The xCBM provides a PDU-
like functionality for the OPT9932, saving the need for an external PDU. Each xCBM feeds an xPFM-32
installed under it, which in-turn feeds the cards (xRCP, xFM, xMIM, xIO, etc.) and subsystems in the
OPT9932. The two leftmost pairs must always be connected to power, as they provide power to
common cards and subsystems.
The left xCBM in a pair connects to source A and the right to source B. The following figure identifies
the xCBMs and the corresponding power sources. The colors of the xPFM-32 cards correspond to
colors of the cards they are feeding.

Ribbon Communications Inc. Proprietary 2-17

 Apollo Reference Manual OPT9932/OPT9914 common cards

Power distribution areas in the OPT9932

Functions
 Sockets for the Circuit Breaker (CB)
 Surge protection
 Connector for the xPFM-32 card
 Pin guide for connection of the xPFM-32

Ribbon Communications Inc. Proprietary 2-18

 Apollo Reference Manual OPT9932/OPT9914 common cards

Card views
General view

Connection of xPFM-32 to the xCBM

Ribbon Communications Inc. Proprietary 2-19

 Apollo Reference Manual OPT9932/OPT9914 common cards

2.9 xPFM-32
Supported platforms
 OPT9932

Description
The xPFM-32 is an input power filter for the DC voltage connected to the OPT9932. Each platform has
up to 12 xPFM-32 units for redundancy purposes. To support redundancy, the xPFM-32 work in pairs,
where each module is connected to a different power source. Each pair is responsible to supply power
to one feed area in the OPT9932. The output voltages of each module in a pair are connected together
and the module with the higher voltage supplies power to the dedicated area. In case of a failure in the
active xPFM-32, the standby module takes over and supply the full power. The faulty unit can be
replaced without affecting traffic.
The connection of the xPFM-32 to the power source is made through two power plugs at the rear of the
card; one plugs into a socket on the xCBM module and the other plugs into the OPT9932 motherboard.
The following figure shows the xPFM-32 with the two power plugs. To ensure good contact of the power
plugs with their mates, a guide pin in the xCBM is inserted into the xPFM-32 during its insertion.

Functions
The xPFM-32 provides the following main functions:
 Input DC voltage filtering (-48 V)
 Control and alarms
 Temperature sensing
 Input voltage monitoring
 Reverse polarity protection
 Surge protection (2 kV line to line, 4 kV line to ground)
 Redundancy between PFM units
 Passive 10 msec Hold-up capacitors
 Under voltage detection
 Lightning strike protection
 Input power measurement
 Fail indication

Ribbon Communications Inc. Proprietary 2-20

 Apollo Reference Manual OPT9932/OPT9914 common cards

Card views
General view

Front panel

LEDs

Marking Item Functions

POWER ON Green LED Lights steadily when the xPFM-32 input supply voltage through the
POWER IN connector is in the allowed range.
FAIL Red LED Normally off. Lights steadily when a fault is detected in the unit.

Ribbon Communications Inc. Proprietary 2-21

 Apollo Reference Manual OPT9932/OPT9914 common cards

2.10 xFCM-32
Supported platforms
 OPT9932

Description
The OPT9932 has two types of fan trays that provide cooling air to the platform: xFCMV-32, and
xFCMH-32. The two types have identical electronic design and cooling and control functionality, and
differ only in physical structure and number of fan units. The xFCMV-32 includes six fans and the
FCMH-32 ten. The fans are fed through circuits that improve the system's performance and support its
redundancy.

NOTE: The generic name xFCM-32 is used to describe functions related to both card
types.

Functions
Features of the xFCM-32 include:
 Separate power supply for each fan unit
 Each adjacent pair of fans have a control of its own:
 Multiple speed levels are defined for each pair; see System Specifications for details
 The levels are controlled by the active xRCP/xRCP1 via a control bus
 Separate psophometric filter with a separate fuse for each fan
 Large capacitor with a fuse on the DC supply bus
 Parallel dual inrush current circuit with a separate fuse for each circuit
 Hold up capacitors (serves the xPFM-32)
A controller in the active xRCP/xRCP1 controls the fans operation. If one of the fans fails, the remaining
start to operate in turbo mode and the fail LED lights until the xFCM-32 is replaced. If done in a few
minutes, the xFCM-32 can be extracted and replaced without interrupting the OPT9932 operation (hot
swapping).

WARNING: Do not leave the system without one of the fan tray units for more than five
minutes.

Ribbon Communications Inc. Proprietary 2-22

Apollo Reference Manual OPT9932/OPT9914 common cards

Card views
General view:xFCMH-32

Ribbon Communications Inc. Proprietary 2-23

Apollo Reference Manual OPT9932/OPT9914 common cards

General view: xFCMV-32

Front panel: xFCMH-32

Ribbon Communications Inc. Proprietary 2-24

Apollo Reference Manual OPT9932/OPT9914 common cards

Front panel: xFCMV-32

LEDs

Marking Item Functions

ACTIVE Green Lights steadily when the card is powered and operating normally.
LED
FAIL Red LED Normally off. Lights steadily when a fault is detected.

Ribbon Communications Inc. Proprietary 2-25

3 OPT9932/OPT9914 service cards
The Apollo OPT99xx high capacity switching platforms work with a set of service cards, supporting a
mix of Layer 1 and Layer 2 services. These cards have access to the universal switching fabric that
supports OTN switching (ODUk cross-connect 0,1,2,3,4,Flex) and packet switching (Layer 2). The HIO
cards are hardware-ready for MPLS-TP software upgrade.
This section provides a detailed description of the service cards available for the OPT99xx platforms.
The prefix of the card name refers to the type of traffic supported:
 HIO - Hybrid traffic
 TIO - OTN traffic
 PIO - Packet (Data) traffic (future)

OPT99xx service cards

Name Description
HIO500 Up to 400G capacity in the current release, supporting a mixture of L1/L2 client/line
interfaces with a configurable mixture of 200G/100G/10G rates.
HIO100_2 2 x 100G CFP based ports, each port can be used as line or client, 100GbE, OTU4,
with coherent CFPs or Non-colored CFPs.
HIO10_40 Up to 400G capacity, supporting a mixture of L1/L2 interfaces with a configurable
mixture of rates, both client (OTU4, OTU2e, OTU2, 40GbE, STM-64) and line
(OTU4 with ODUflex NNI uplinks).
HIO10_20 20 port 10G multi-service interface card for any mix of: OTU2, OTU2e, STM-64/OC-
192, OC-192, FC1200, FC800, 40GbE, and 10GbE.
TIOMR_32 32 port low-rate service interface card for any mix of: STM-1/OC-3, STM-4/OC-12,
STM-16/OC-48, FC1/FC2/FC4, and GbE.

3.1 HIO500 and HIO400/HIO400EN

Supported platforms
 OPT9932
 OPT9914

Description
The HIO500 is a single slot hybrid (OTN/packet) I/O card with ODUflex NNI uplink and G.HAO support
for the OPT9932 and OPT9914 platforms, providing 500G/400G capacity, depending on the platform
configuration. This is a configurable-rate card based on coherent transmission with adaptive
modulation, 15% SD-FEC, NCG 11-12dB, supporting a mixture of Layer1/Layer2 client/line interfaces
with a rate mixture of 200G/100G/10G.
The HIO500 enables full utilization of the OPT99xx slot capacity of 400/500 Gbps. From a management
perspective the card can be configured in two operation modes:
 HIO400: With a capacity of 400 Gbps
 HIO500: With a capacity of 500 Gbps (OPT9932)

Ribbon Communications Inc. Proprietary 3-1

 Apollo Reference Manual OPT9932/OPT9914 service cards

The HIO500 is optimized for client/line low rate/high rate solutions that provide up to 2 x 200G lines for
short-medium ranges, or up to 5 x 100G lines for high ranges, or 5 x 100G/50 x 10G clients.
The HIO500/HIO400 works with D-CFP2 coherent line transceivers, supporting configurable QPSK,
8QAM, or 16QAM modulation, with Flex-Grid capabilities. This transceiver includes a coherent receiver,
DSP processing, and soft decision forward error correction, for superior noise tolerance, as well as an
exceptional ability to mitigate CD and PMD impairments.
When client ports are configured for 100G/OTU4, SR10 and LR4 transceivers are supported, as well as
ER4DR (40Km) and ZR4DR (80Km) for OTU4 grey output. The supported FEC mode for ZR4DR is RS-
FEC.

HIO400EN
The HIO400 card is also available with a software encryption option. When configured as an
HIO400EN, encryption is supported for OTU4 and OTUC2 rates on the line ports. Authentication is via
private/public keys, with the key period configured per NE.

Functions
The HIO500 provides the following main functions:
 Elastic rate line configuration:
 Up to 2 x 200G (OTUC2), where each port can be configured independently:
 QPSK, for distances of over 2500km
 8QAM, for distances of over 800km
 16QAM, for distances of over 600km
 Up to 5 x 100G (OTU4) QPSK, for ultra-long haul distances of over 3000km. Each port can
be configured independently.
 Up to 5 x 10 x 10G MPO MM fanout for 10GE SR client support
 Client configuration of up to 100GE/OTU4, for L1 or L2 line interfaces
 High density client configuration with up to 4 x 100GbE; each port can be configured
independently
 Hot insertion/removal of CFP2 transceivers without traffic affecting of other ports in the card.
 Protection mechanisms:
 SNCP, DRI, and DNI
 Port protection (excluding 10G Fanout cases)
 ASON/WSON
 OLP/OMSP
 Lite-Packet (L2 over ODUflex, G.HAO)
 SyncE and 1588v2 synchronization
 Interoperability support:
 HIO100_2 for OTU4 coherent and non-coherent modes.
 MIO200 for OTU4 coherent and non-coherent modes.
 TR200_2 for OTU4 coherent and OTUC2. OTU4 non-coherent mode is not supported.
 TM200EN for OTU4 coherent and OTUC2. OTU4 non-coherent mode is not supported.

Ribbon Communications Inc. Proprietary 3-2

 Apollo Reference Manual OPT9932/OPT9914 service cards

 TM400 for OTU4 coherent differential mode (DQPSK) and non-coherent modes. OTUC2 is
not supported.
 Standard SC-FEC for 100Gbps line rate interoperability (supported OTR200_CFO modules).
 GCC features:
 GCC interoperability with the following cards:
 HIO100_2
 MIO200
 TR200_2
 TM200EN
 TM400
 GCC supported in standard (full rate) mode.
 Up to 4 GCC channels for OTUC2/OTU4 supported.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.

Card views
General view

Ribbon Communications Inc. Proprietary 3-3

 Apollo Reference Manual OPT9932/OPT9914 service cards

Front panel: (left)

Front panel: (right)

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when
there is no fault in the HIO500.
CFP2 port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the CFP2 pluggable transceiver, or
the supply voltage or temperature is OOR.

Ribbon Communications Inc. Proprietary 3-4

 Apollo Reference Manual OPT9932/OPT9914 service cards

Functional block diagram

3.1.1 HIO500 port configuration and usage guidelines

HIO500 supports up to 41 ports (Port 0 to Port 40) (Port 0 is disabled in the current release.
The card can house up to four CFP2 transceivers. Each transceiver may represent 10 potential ports
(for supporting 10G fan-out mode). The four CFP2 ports are divided into four Groups as follows:
 Group 1 (G1) - Ports 1 to 10
 Group 2 (G2) - Ports 11 to 20
 Group 3 (G3) Ports 21 to 30
 Group 4 (G4) Ports 31 to 40
If the first port in a group is configured to 100G/200G, all other ports in the group are disabled.

NOTE: A port type with a rate of 200G is OTUC2 (only supported in ports 11 & 31). Port
types with rates of 100G include: OTU4, ETY100G, GE100 and GE100-OTU4.

The following table describes the port groups configuration options.

HIO500 port groups configuration options

Group rates option Ports 1-10 (G1) Ports 11-20 (G2) Ports 21-30 (G3) Ports 31-40 (G4)
2 x 200G Disabled 200G (port 11) Disabled 200G (port 31)
4 x 100G 100G/10 x 10G 100G/10 x 10G 100G/10 x 10G 100G/10 x 10G
Mixed rates A Disabled 200G (port 11) 100G/10 x 10G 100G/10 x 10G
Mixed rates B 100G/10 x 10G 100G/10 x 10G Disabled 200G (port 31)

Ribbon Communications Inc. Proprietary 3-5

 Apollo Reference Manual OPT9932/OPT9914 service cards

The following table describes the supported port types for the HIO500 in the current release.

Supported port types for the HIO500.

Port No. Ports 0 Port 1 and 21 Port 11 and 31 Ports 2-10, 12-20, 22-30, 32-
40
Supported port types Disabled OTU4 OTUC2 ETY10Goc
ETY100G OTU4 GE10
GE100 ETY100G
GE100-OTU4 GE100
ETY10Goc GE100-OTU4
GE10 ETY10Goc
GE10

Usage guidelines and applications

The HIO500 supports the following main applications:
 Dual 200 Gbps operation for short/medium range links
 4 x 100 Gbps operation for long-haul links
 High density and capacity of 10G clients – up to 40 x 10G (fanout-mode)
 Up to 400G L2 – ODUflex traffic
 Single card solution both for clients and for lines (Joker card) – the entire network can be based
on HIO500 – single card type
 Enabling 5.6 Tbps/12.8 Tbps capacities in OPT9914/OPT9932
 Better watt per bit due to higher density
 Interoperability with 3rd party OTN systems

3.2 HIO100_2
Supported platforms
 OPT9932
 OPT9914

Description
HIO100_2 provides an OTU4 uplink for the OPT9932 and OPT 9914 platforms. HIO100_2 also
supports up to two 100G ports in a single slot card with CFP pluggable optics. The client-side signals
are mapped to G.709 ODU-k and cross connected through the central universal fabric to the egress
side.
The HIO100_2 provides a multi-service, cost-effective solution to customers for Metro, Regional, and
Long haul applications over OTN DWDM networks.
The HIO100_2 works with D-CFP coherent line transceivers that enable transmission of 100Gbps DP-
QPSK modulation, with Flex-Grid capabilities. This transceiver includes a coherent receiver, DSP
processing, and soft decision forward error correction, for superior noise tolerance, as well as an
exceptional ability to mitigate CD and PMD impairments.

Ribbon Communications Inc. Proprietary 3-6

 Apollo Reference Manual OPT9932/OPT9914 service cards

Functions
The HIO100_2 provides the following main functions:
 Single-slot card
 2 x 100 Gbps uplink for OTN switching sites
 100 G ports based on CFP pluggable. Each port can be configured by the user to one of the
following:
 ETY 100G
 ODU4
 Optionally supports dual rate LR4 and SR10 CFPs
 Hybrid data and ODUk grooming capability:
 ODUk switching (L1)
 Low order ODUk L1 and L2 mixing (Lite Packet)
 OTU4 interfaces Metro coherent transceiver:
 Dual rate LR4 and SR10 CFP transceivers and if available CFP ER4 as well
 100 GbE interfaces:
 Supports LR4 and SR10 CFP transceivers and if available CFP ER4 as well
 Processes and multiplexes any combination of low-order ODUs and packets that arrive from the
fabric into ODU4 (100 Gbps line)
 Supports port protection (IOP) for 100GE client and SNCP
 GCC features:
 GCC interoperability with the following cards:
 HIO500
 CMR100M/CMR100
 TM100/TR100
 TM200EN
 TR200_2
 TM400
 GCC supported in standard (full rate) mode by default, as well as Apollo proprietary (¼ rate
GCC) reduced mode, user selectable.
 Up to 2 GCC channels for OTU4 supported.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.

Ribbon Communications Inc. Proprietary 3-7

 Apollo Reference Manual OPT9932/OPT9914 service cards

Card views
General view

Front panel

Usage guidelines and assignment rules

 HIO00_2 ports are 0 and 1.
 Both ports support OTU4 and ETY100G port type.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when
there is no fault in the HIO100_2.

Ribbon Communications Inc. Proprietary 3-8

 Apollo Reference Manual OPT9932/OPT9914 service cards

Marking Item Functions

Client (CFP) port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the CFP pluggable transceiver, or the
supply voltage or temperature is OOR.

3.3 HIO10_40
Supported platforms
 OPT9932
 OPT9914

Description
The HIO10_40 is a high-density single-slot QSFP-based card with full hybrid capability. This card
supports any mix of the following client interface connections to the OPT9900 universal fabric:
 Maximum card capacity of 400G, in any port combination
 Elastic rate client configuration:
 4 x 100GbE/OTU4 L1 or L2
 40 x 10GbE/OTU2e L1 or L2
 40 x OTU2 L1
 8 x 40GbE L1
 24 x STM-64/OC-192
 Line configuration of OTU4 black & white uplinks, for L1 or L2, with ODUflex NNI uplinks and
G.HAO support
 SNCP and port protection
 Hardware ready for SyncE and 1588v2 synchronization
 GCC features:
 GCC supported in standard (full rate) mode.
 Up to 10 GCC channels for OTUC2/OTU4/OTU2/OTU2e supported.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.

Ribbon Communications Inc. Proprietary 3-9

 Apollo Reference Manual OPT9932/OPT9914 service cards

Card views
General view

Front panel

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when
there is no fault in the HIO10_20.
Client port (QSFP+ and QSFP28) LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the SFP+/QSFP+ pluggable
transceiver, or the supply voltage or temperature is OOR. LOS
condition is not indicated in FAN-out mode.

Ribbon Communications Inc. Proprietary 3-10

 Apollo Reference Manual OPT9932/OPT9914 service cards

Port configuration guidelines and assignment rules

HIO10_40 ports are numbered from 0 to 39. The marking above each port identifies the Transmit (Tx)
and Receive signals (Rx). The client port LEDs are off when configured for a fan-out application.
The HIO10_40 provides the following configuration options:
 If of the ports is configured to 100G or 40G service, the rest of the ports in same transceiver will
be disabled.
 100G and 40G service configuration will not be accepted if a 10G port type is configured in same
transceiver.
There are 2 OTN mapper devices on each card. Each mapper consists of 2 slices. The ports are
organized in 4 groups that support accumulated bandwidth of 100G. The groups and port assignments
are organized as follows.
 Group 1: Ports number 8, 9, 10, 11, 16, 17, 18, 19, 24, 25
 Ports 8-11 support 100, 40 and 10G
 Ports number 16-19 support 10 and 40G
 Ports number 24 and 25 support 10G
 Group 2: Ports number 12, 13, 14, 15, 20, 21, 22, 23, 26, 27
 Ports number 12-15 support 100, 40 and 10G
 Ports number 20-23 support 40 and 10G
 Ports number 26 and 27 support 10G
 Group 3: Ports number 0, 1, 2, 3, 28, 29, 30, 31, 36, 37
 Ports number 0-3 support 100, 40 and 10G
 Ports number 28-31 support 40 and 10G
 Ports number 36 and 37 support 10G
 Group 4: Ports number 4, 5, 6, 7, 32, 33, 34, 35, 38, 39
 Ports number 4-7 support 100, 40 and 10G
 Ports number 32-35 support 40 and 10G
 Ports number 38 and 39 support 10G
The following table lists the port configuration options. A Yes in the following table indicates an allowed
(supported) configuration option.

Ribbon Communications Inc. Proprietary 3-11

Apollo Reference Manual OPT9932/OPT9914 service cards

3.3.1 HIO10_40 fan-out port configuration rules

Port Transceiver OTU4 ETY100G GE100 GE100_OTU4 ETY40G ETY10GOC GE10 GE10_OTU2e OTU2/OTU2e STM64/OC192
0 1 Yes Yes Yes Yes Yes Yes Yes Yes Yes
1 1 Yes Yes Yes Yes
2 1 Yes Yes Yes Yes
3 1 Yes Yes Yes Yes
4 2 Yes Yes Yes Yes Yes Yes Yes Yes Yes
5 2 Yes Yes Yes Yes
6 2 Yes Yes Yes Yes
7 2 Yes Yes Yes Yes
8 3 Yes Yes Yes Yes Yes Yes Yes Yes Yes
9 3 Yes Yes Yes Yes
10 3 Yes Yes Yes Yes
11 3 Yes Yes Yes Yes
12 4 Yes Yes Yes Yes Yes Yes Yes Yes Yes
13 4 Yes Yes Yes Yes
14 4 Yes Yes Yes Yes
15 4 Yes Yes Yes Yes
16 5 Yes Yes Yes Yes Yes Yes
17 5 Yes Yes Yes Yes Yes
18 5 Yes Yes Yes Yes Yes
19 5 Yes Yes Yes Yes Yes

Ribbon Communications Inc. Proprietary 3-12

Apollo Reference Manual OPT9932/OPT9914 service cards

Port Transceiver OTU4 ETY100G GE100 GE100_OTU4 ETY40G ETY10GOC GE10 GE10_OTU2e OTU2/OTU2e STM64/OC192
20 6 Yes Yes Yes Yes Yes Yes
21 6 Yes Yes Yes Yes Yes
22 6 Yes Yes Yes Yes Yes
23 6 Yes Yes Yes Yes Yes
24 7 Yes Yes Yes Yes Yes
25 7 Yes Yes Yes Yes Yes
26 7 Yes Yes Yes Yes Yes
27 7 Yes Yes Yes Yes Yes
28 8 Yes Yes Yes Yes Yes Yes
29 8 Yes Yes Yes Yes Yes
30 8 Yes Yes Yes Yes Yes
31 8 Yes Yes Yes Yes Yes
32 9 Yes Yes Yes Yes Yes Yes
33 9 Yes Yes Yes Yes Yes
34 9 Yes Yes Yes Yes Yes
35 9 Yes Yes Yes Yes Yes
36 10 Yes Yes Yes Yes Yes
37 10 Yes Yes Yes Yes Yes
38 10 Yes Yes Yes Yes Yes
39 10 Yes Yes Yes Yes Yes

Ribbon Communications Inc. Proprietary 3-13

 Apollo Reference Manual OPT9932/OPT9914 service cards

3.4 HIO10_20
Supported platforms
 OPT9932
 OPT9914

Description
The HIO10_20 is a 10G multi-service interface card for the OPT9932 and OPT9914 platforms that
supports up to 20 client interfaces, SFP+ based transceivers. Each port can be configured to OTU2,
OTU2e, STM-64/OC-192, OC-192, FC1200, FC800, 40GbE, or 10GbE. Client-side signals are mapped
to G.709 ODU-k and cross connected through the central universal fabric to the egress side. Two
additional client interfaces can be configured to 40 GbE. These are QSFP+ based ports and the
configuration of such interface is at the expense of four SFP+ ports.
The HIO10_20 provides a multi-service, cost-effective solution to customers for grooming 10G services
over OTN DWDM networks.

Functions
The HIO10_20 provides the following main functions:
 Single slot card
 20 SFP+ based client ports, software configurable to support any mix of the following services:
 OTU2
 OTU2e
 STM-64/OC-192
 OC-192
 FC1200
 FC800
 10 GbE
 2 QSFP+ based ports software configurable to 40 GbE:
 Configuration of an 40GbE port is at the expense of four SFP+ "regular" ports
 Interoperability with existing OPT96xx cards
 Transparent timing for SDH/SONET signals support CoC applications
 End-to-end PM (including regeneration) and OTN mapping and termination
 Pluggable client and line interfaces support in service upgrade
 Tunable line interfaces for dynamic networks
 1+1 OCH path and equipment protection based on ODU2 PM
 Supports port protection (IOP) and SNCP protection
 Hardware ready for SyncE and 1588v2 synchronization

Ribbon Communications Inc. Proprietary 3-14

 Apollo Reference Manual OPT9932/OPT9914 service cards

Card views
General view

Front panel

Ports
The numbering of the HIO10_20 ports is from 0 to 21. The first two ports (0 and 1) are dedicated to
QSFP+ interfaces that can be configured only to 40 GbE. The SFP+ ports are numbered from 2 to 21.
When a QSFP+ port is configured, four SFP+ ports are disabled; for example if port number 0 is
configured the corresponding SFP+ ports 2 to 5 will be disabled.
The marking above each port identifies the Transmit (Tx) and Receive signals (Rx).

Ribbon Communications Inc. Proprietary 3-15

 Apollo Reference Manual OPT9932/OPT9914 service cards

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off when
the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the HIO10_20.
Client port (QSFP+ and SFP+) LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter is
off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a BIT fault is
detected in the SFP+/QSFP+ pluggable transceiver, or the supply voltage or
temperature is OOR.

3.5 TIOMR_32
Supported platforms
 OPT9932
 OPT9914

Description
The TIOMR_32 is a single-slot multi-rate interface card that supports up to 32 low-rate client interfaces
using SFP transceivers. Each port can be configured to STM-1/OC-3, STM-4/OC-12, STM-16/OC-48,
FC100/FC200/FC400, or GbE. Client-side signals are mapped to G.709 ODU-k and cross connected
through the central universal fabric to the egress side. The TIOMR_32 provides a multi-service, cost-
effective solution to customers for grooming low-rate (< 10G) services over OTN DWDM networks.

Functions
The TIOMR_32 provides the following main functions:
 32 SFP-based client ports, software-configurable to support any mix of the following services:
 GbE (optical and electrical)
 FC100
 FC200
 FC400
 STM-1/OC-3
 STM-4/OC-12
 STM-16/OC-48
 OTU1
 Interoperability with existing OPT96xx cards
 Transparent timing for SDH/SONET signals

Ribbon Communications Inc. Proprietary 3-16

 Apollo Reference Manual OPT9932/OPT9914 service cards

 End-to-end PM (including regeneration) and OTN mapping and termination

 Pluggable client and line interfaces support in service upgrade
 Tunable line interfaces for dynamic networks
 SNCP and port protection based on PM
 ODU0, ODU1 and ODUflex FC4G cross-connections
 GCC features:
 GCC supported in standard (full rate) mode.
 One GCC supported per OTU1 port, configurable to either GCC0, GCC1, or GCC2, user
selectable.

Card views
General view

Ribbon Communications Inc. Proprietary 3-17

 Apollo Reference Manual OPT9932/OPT9914 service cards

Front panel

Usage guidelines and assignment rules

 Numbering of the TIOMR_32 ports is from 0 to 31.
 Any client type, except FC400, can be assigned to any port.
 FC400 client type can be assigned only to even-numbered ports (0,2,4...30).
 When FC400 is assigned to a port, the RCP rejects assignment of the consecutive port. For
example: port 0 is assigned to FC400, any assignment to port 1 is rejected.
 FC400 assignment to a port will be rejected if the consecutive port is assigned to any other port.
For example: port 1 is assigned to STM1, the assignment of FC400 to port 0 is rejected.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when
there is no fault in the TM100.
Port LEDs
0 to 31
Bi-color LED
(Green or Red):
Green Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
Red Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the SFP+ pluggable transceiver, or
the supply voltage or temperature is OOR.

Ribbon Communications Inc. Proprietary 3-18

4 OPT9904X platform architecture and
cards
This section describes the platform layout and cards of the OPT9904X platform. The OPT9904X is
based on a unique “fabric-less” design that enables smooth switching capacity expansion, either in
200G increments up to a total of 800G per platform with the MIO200 card, or 700G increments up to a
total of 2.8T per platform with the MIO700 card, without having to invest in separate switching fabrics.
Moreover, the OPT9904X integrates packet services, generating savings by aggregating L2 traffic and
reducing the number of costly router ports.
Apollo platforms have been designed to facilitate simple installation and easy maintenance. Hot
insertion of cards and modules enables quick maintenance and repair activities without affecting traffic.
The cage design and mechanical practice of all platforms conform to international mechanical
standards and specifications.
The OPT9904X system architecture includes the following components:
 Control and communications subsystems, including:
 Control
 Communications
 Timing and synchronization
 Cross-connect functionality
 Distributed forwarding architecture
 Packet processing
 Power feed subsystem
 Management system
The OPT9904X system architecture is based on the OPT96xx architecture, described in detail in
OPT96xx platform layout and architecture. The architecture design of the OPT9904X is identical except
for the section describing the universal fabric, since the OPT9904X operates with no fabric. Therefore,
this section focuses on the OPT9904X platform layout and cards.

NOTE: All installation instructions, technical specifications, restrictions, and safety

warnings are provided in the Apollo Platform Installation and Maintenance Manuals. See
these manuals for specific instructions before beginning any Apollo installation.

4.1 OPT9904X platform layout

The OPT9904X integrates full WDM functionality and Ethernet Layer 2 switching in a single compact
platform, and can be optimized for a range of working configurations. Platform dimensions are sized for
19" racks, with 220 mm height (5U) and 253 mm depth. The platform includes:
 Four universal I/O slots for hybrid service cards that support a mix of Layer 1, Layer 2, and
photonic services, providing a density of up to 700G for each slot.
 Switching capacity of up to 2.8T. Universal support for OTN switching (ODUk cross-connect 0, 1,
2, 2e, 4, Flex) and packet switching. No separate switching fabric is required.

Ribbon Communications Inc. Proprietary 4-1

 Apollo Reference Manual OPT9904X platform architecture and cards

 Cross connections are supported within the MIO cards or between cards with no limitations. The
platform must be configured with either MIO200 cards or MIO700 cards; a mixture of MIO card
types within a single platform is not supported.
 Two high-availability RCP main shelf controllers (RCP04X).
 Two power feed modules (PFM04X) using a -40.8 - -57.6 VDC power source.
 One fan control module (FCM04X) with four fans.
 One timing, alarm, and management interface module (TAMIM04X)
 Filter tray.

Platform layout

Slot allocation

Ribbon Communications Inc. Proprietary 4-2

 Apollo Reference Manual OPT9904X platform architecture and cards

4.2 OPT9904X common cards

The OPT9904X includes cards and modules that provide its common functionality, such as routing and
control, management and timing connections, power supply, air-cooling, control required for operation
and cross-connect.

4.2.1 RCP04X
Supported platform
 OPT9904X

Description
The RCP04X is the central control component in the platform, providing the main system processor
responsible for essential system management, timing, and control. The card supports timing
functionality for a wide range of synchronization standards by the Central Timing Module (xCTM)
residing on it.

Functions
The RCP04X provides the following main functions:
 Main system processor, responsible for essential system management
 CTM
 Routing and control:
 Management communication
 CPU offload
 4 Gb CF (Compact Flash) card memory (NVM) hardware ready for 8 Gb memory
 Stores the platform's software code and configuration data base (on the NVM)
 Ethernet intra-platform networking
 Hardware ready for L2 (Lite Packet) switching
 EMS and LCT management support
 Timing to all I/O cards
 Announces the active RCP to all Field Replaceable Units (FRUs)
 Self BIT
 Single or redundant RCP
 Activations, including:
 LED tests for the entire platform
 ACO
 HA (High Availability):
 Active fabric distribution done immediately
 Hardware detection of major fabric card faults and switchover

Ribbon Communications Inc. Proprietary 4-3

 Apollo Reference Manual OPT9904X platform architecture and cards

Card views
General view

Front panel

LEDs

Marking Item Functions

Controller LEDs
ACT Green LED On -
1. During upload time
2. RCP04X is active and has no BIT failure
Off - RCP04X has BIT failure
SBY Yellow LED On -
1. During upload time
2. RCP04X configured as SB
Blinks - One of microswitches is open
Off – RCP04X is defined as Active
FAIL Red LED On - RCP04X has BIT failure or has not come out of reset
Off - no BIT failure
SD LED
SD Blue LED Blinks - Writing operation on SD card
Off - No writing operation on SD card

Ports and pushbuttons

Ribbon Communications Inc. Proprietary 4-4

 Apollo Reference Manual OPT9904X platform architecture and cards

Marking Connector Functions

Connectors
CONSOLE RJ-45 connector Serial RS-232 communication port for connecting a CLI station.
LOCAL MNG. RJ-45 connector Interface for connecting an LCT.
DEBUG RJ-45 connector Interface for technical staff used to debug both L2 & L3 switches.
Pushbuttons
ACO Pushbutton Used to temporarily disable the buzzer and set off the
corresponding alarm LED when an alarm condition is present. The
buzzer is activated again when a new alarm condition is detected.
LED TEST Pushbutton Turns on all LEDs located on cards/modules installed in the
platform, for test purposes.

4.2.2 PFM04X
Supported platform
 OPT9904X

Description
The PFM04X is an input power filter for the DC voltage connected to the OPT9904X and protects the
equipment from external abnormal voltage connectivity. Each platform has two PFM04X units for
redundancy purposes. It is recommended to connect each to a different power source (unless only one
power source is available). When only one power source is available, it is recommended to connect it to
the two power inputs of both units. In such case, and provided a redundant PFM04X is installed, the
faulty unit can be replaced without affecting traffic.

Functions
The PFM04X performs the following functions:
 Input DC voltage filtering (-48 V)
 Control and alarms
 Provision of maximum power of 2000 W
 Reverse polarity protection
 Surge protection (2 kV line to line, 4 kV line to ground)
 Over-voltage protection
 Over-current and short circuit protection
 Temperature sensing
 Input voltage monitoring
 Part of Hold-up capacitors (other capacitors are on the FCM04X)
 Power Good indication
 Fail indication
 Protection mechanism that prevents module extraction while connected to a power source

Ribbon Communications Inc. Proprietary 4-5

 Apollo Reference Manual OPT9904X platform architecture and cards

Card views
General view

Front panel

LEDs

Marking Item Functions

ACT Green LED Lights steadily when the PFM04X input supply voltage
through the POWER IN connector is in the allowed range.
FL Red LED Normally off. Lights steadily when a fault is detected in the
unit.
POWER IN 5W5 D-type connector Connects DC input power to the filter in the unit.

4.2.3 PFM04X_H
Supported platform
 OPT9904X

Description
The PFM04X_H is a high-power input power filter for the DC voltage connected to the OPT9904X, and
protects the equipment from external abnormal voltage connectivity. When using the PFM04X_H
module, the platform is configured as an <OPT9904>_H (higher-power) platform, supporting the use of
more high-power-consumption cards, such as the MIO700.

Ribbon Communications Inc. Proprietary 4-6

 Apollo Reference Manual OPT9904X platform architecture and cards

Each platform has two PFM04X_H units for redundancy purposes. It is recommended to connect each
to a different power source (unless only one power source is available). When only one power source is
available, it is recommended to connect it to the two power inputs of both units. In such case, and
provided a redundant PFM04X_H is installed, the faulty unit can be replaced without affecting traffic.

Functions
The PFM04X_H performs the following functions:
 Input DC voltage filtering (-48 V)
 Control and alarms
 Provision of maximum power of 2600 W
 Reverse polarity protection
 Surge protection (2 kV line to line, 4 kV line to ground)
 Over-voltage protection
 Over-current and short circuit protection
 Temperature sensing
 Input voltage monitoring
 Part of Hold-up capacitors (other capacitors are on the FCM04X)
 Power Good indication
 Fail indication
 Protection mechanism that prevents module extraction while connected to a power source

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 4-7

 Apollo Reference Manual OPT9904X platform architecture and cards

LEDs and connectors

Marking Item Functions

ACT Green LED Lights steadily when the PFM04X_H input supply voltage
through the POWER IN connector is in the allowed range.
FL Red LED Normally off. Lights steadily when a fault is detected in the
unit.
POWER IN 5W5 D-type connector Connects DC input power to the filter in the unit.

4.2.4 FCM04X
Supported platform
 OPT9904X

Description
The FCM04X provides cooling air to the system from nine separate fans and is positioned at the right
side of the OPT9904X. Air is drawn in by the fans from the right side of the chassis and pumped out
through the horizontally mounted cards and modules through the left side of the chassis. The fans are
fed through circuits that improve the system's performance and support its redundancy.
The FCM04X includes a controller that controls the operation of the fans. If one of the fans fails, the
remaining ones operate in turbo mode and the fail LED lights until the FCM04X is replaced. If the
operation does not take more than four minutes, the FCM04X can be extracted and replaced without
interrupting the router operation (hot swapping). We recommend preparing the replacement module in
advance and so shortening replacement time to a minimum.

WARNINGS:
 Don't leave the OPT9904X platform operating without an FCM04X.
 If you must replace an FCM04X, don't leave the system without an FCM unit for
more than 2 minutes.

Functions
Features of the FCM04X include:
 Separate power supply for each fan unit
 Each adjacent pair of fans have a control of its own:
 Multiple speed levels are defined for each pair; see System Specifications for details
 The levels are controlled by the active RCP04X via a control bus
 Separate psophometric filter with a separate fuse for each fan
 Large capacitor with a fuse on the DC supply bus
 Parallel dual inrush current circuit with a separate fuse for each circuit
 Part of Hold up capacitors (serves the PFM04X)

Ribbon Communications Inc. Proprietary 4-8

 Apollo Reference Manual OPT9904X platform architecture and cards

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 4-9

 Apollo Reference Manual OPT9904X platform architecture and cards

LEDs

Marking Item Functions

ACT Green LED Lights steadily when the card is powered and operating normally.
FAIL Red LED Normally off. Lights steadily when a fault is detected.

4.2.5 TAMIM04X
Supported platform
 OPT9904X

Description
The TAMIM04X is the timing, alarms, and management connection unit between the OPT9904X
platform and the external world. It provides interfaces for timing, alarms and the external management.
The TAMIM04X is installed at the upper part of the OPT9904X.

Functions
The TAMIM04X provides the following main functions:
 Out-of-band management interface for connecting an STMS
 Two management ports for cascading up to two OPT96xx platforms
 Timing interfaces:
 Two BITS (T3/T4) connectors
 1588v2/PTP (ToD, 1PPS) in/out connectors
 10 MHz clock In/Out connector
 Alarm interfaces and indications, including:
 Severity alarm outputs (Critical, Major, Minor)
 External alarm outputs and inputs to client or:
 4 output alarms (relay dry contacts)
 4 input alarms (opto-couplers)
 LEDs for displaying the operation and alarms of the system

Ribbon Communications Inc. Proprietary 4-10

 Apollo Reference Manual OPT9904X platform architecture and cards

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 4-11

Apollo Reference Manual OPT9904X platform architecture and cards

Ports
Marking Connector Functions
ALARMS 36-pin SCSI Connects alarm input and output lines via a RAP or
connector directly to the client.
BITS (T3/T4) 1 RJ-45 connector Main timing input/output clock using an E1/2MHz/1.5MHz
signal (for future support).
BITS (T3/T4) 2 RJ-45 connector Additional timing input/output clock using an
E1/2MHz/1.5MHz signal (for future support).
ToD & 1PPS RJ-45 connector Time of Day and 1PPS input/output signals for supporting
Ethernet timing per IEEE 1588v2 standard (for future
support).
MULTI SHELF MNG. 1, RJ-45 connectors Management interfaces for multi-shelf control.
2
IMG RJ-45 connector Out-of-band management Ethernet interface
(10/100/1000BaseT) for connecting to an element
management station (STMS) or a CLI terminal.
1PPS OUT DIN 1.0/2.3 1PPS output signal for supporting Ethernet timing per
connector IEEE 1588v2 standard (for future support).
10 MHz IN/OUT DIN 1.0/2.3 10 MHz input/output signals for supporting Ethernet
connector timing per IEEE 1588v2 standard (for future support).

LEDs
Marking Item Functions
Card LEDs
ACT Green LED On -
1. During upload time
2. xTAM is Active and no BIT failure
Off - TAMIM04X has BIT failure
FL Red LED On -
1. During upload time
2. TAMIM04X has BIT failure
Off - no BIT failure
System Severity Alarm LEDs
MIN Yellow LED On - System has a Minor Alarm
Off -
1. During upload time
2. no Alarms
MAJ Orange LED On - System has a Major Alarm
Off -
1. During upload time
2. no Alarms
CRT Red LED On - System has a Critical Alarm
Off -
1. During upload time
2. no Alarms

Ribbon Communications Inc. Proprietary 4-12

 Apollo Reference Manual OPT9904X platform architecture and cards

4.3 OPT9904X passive and photonic cards

Passive cards for the OPT9904X are supported only via an Artemis shelf.
The following OPT96xx photonic cards are supported in the OPT9904X platform:
 OA_LF
 OA_DLF
 OA_DLHF
 OLP_S2
 OMSP
 OTDR_8

4.4 MIO200/MIO200EN
Supported platform
 OPT9904X

Description
MIO200 is a multipurpose ODU-XC base card with 100G CFP based uplink interface and up to 12 x
SFP/SFP+ based client ports. The card also supports packet switching over OTN and 200G bandwidth.
The card throughput is 200 Gbps, and four cards together comprise a 800G mesh cross-connect,
without the need for a central matrix. MIO200 is a multi-rate IO card and supports 100G, 10G, and 1G
clients.
The OPT9904X equipped with MIO200 cards provides a multi-service, low cost, minimal size sub 1T
ODU-XC solution to customers for grooming 10G and sub 10G services over the OTN DWDM
networks.
The MIO200 works with D-CFP coherent line transceivers that enable transmission of 100Gbps DP-
QPSK modulation, with Flex-Grid capabilities. This transceiver includes a coherent receiver, DSP
processing, and soft decision forward error correction, for superior noise tolerance, as well as an
exceptional ability to mitigate CD and PMD impairments.

MIO200EN
The MIO200 card is also available with an encryption option. When configured as an MIO200EN,
encryption is supported for OTU4 rates on the line ports. Authentication is via private/public keys, with
the key period configured per NE.

Functions
The MIO200 is a double-slot long card that provides the following main features:
 CFP line interface supporting ETY100G and OTU4
 12 x SFP/SFP+ based client ports, software-configurable to support any mix of the following
services:
 GbE (optical and electrical)
 10GE

Ribbon Communications Inc. Proprietary 4-13

Apollo Reference Manual OPT9904X platform architecture and cards

 FC1G
 FC2G
 FC4G
 FC8G
 FC16G
 STM-1/OC-3
 STM-4/OC-12
 STM-16/OC-48
 STM-64/OC-192
 OTU2
 OTU2e
 Client Ports 1 to 4 support SFP+ transceivers only
 Client Ports 5 to 12 support SFP or SFP+ transceivers
 800G ODU-XC capacity
 ODU0 granularity
 High port density
 Supports SD-FEC for coherent CFP and FEC for non-coherent CFP
 All services (SDH/SONET, FC, Ethernet) are supported with full transparency, including timing
and OH
 SNCP for ODU0/1/2/2e and ODU-flex services
 Support port protection in ODU-XC configuration using splitters and couplers
 Pluggable client and line interfaces support in service upgrade
 Standard SC-FEC for 100Gbps line rate interoperability (supported OTR200_CFO modules)
 GCC features:
 GCC interoperability with the following cards:
 HIO500
 TR200_2
 TM200EN
 TM400 (100G mode)
 GCC supported in standard (full rate) mode.
 Up to 8 GCC channels for OTU2/OTU2e and 1 GCC channel for OTU4 supported.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.

Ribbon Communications Inc. Proprietary 4-14

 Apollo Reference Manual OPT9904X platform architecture and cards

Card views
General view

Front panel

Port configuration guidelines

The line port is numbered 0. The numbering of the client ports is from 1 to 12.

NOTE: Several limitations apply when configuring MIO200 ports to specific rates. These
limitations are described in the following table. Yes in the table indicates the allowed
(supported) configuration option.

Ribbon Communications Inc. Proprietary 4-15

 Apollo Reference Manual OPT9904X platform architecture and cards

MIO200 port configuration rules

Port No. 1 2 3 4 5 6 7 8 9 10 11 12

Rate
OC192, STM64,
ETY10G, FC8G, X X X X X X X X X X
FC10G
FC16G X X X X
STM16, OC48, STM1,
OC3, STM4, OC12, X X X X X X X X
FC1G, FC2G, ETY1G
FC4G
X X X X X X X X
(up to 4 ports)

The marking above each port identifies the Transmit (Tx) and Receive signals (Rx). The client port
LEDs are at the middle of the card. Each port has two LEDs: Tx and F/L, and can be identified
according to the number between the pair.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when
there is no fault in the MIO200.
Line (CFP) port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the CFP pluggable transceiver, or the
supply voltage or temperature is OOR.
Client port (SFP and SFP+) LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the SFP+/QSFP+ pluggable
transceiver, or the supply voltage or temperature is OOR.

Ribbon Communications Inc. Proprietary 4-16

 Apollo Reference Manual OPT9904X platform architecture and cards

4.5 MIO700
The MIO700 is a Gen2 mini-OTN module, providing 2 x 100G/200G or 1 x 300G/400G coherent
uplinks. Each MIO700 card supports up to a total of 400G uplink capacity on the line side and up to
300G capacity on the client side, with ODU-Flex granularity. The MIO700 can be configured with a
digital CFP2 optical module, supporting dual rates of 100GBE/OTU4, for distances up to 80km (70km
between CFP2 and QSFP28).
The OPT9904X platform can be configured with up to 4 MIO700 cards, supporting up to 8 x 200G or 4 x
400G interfaces. The MIO700 is fully interoperable with the OPT99xx and OPT96xx platforms.

NOTES:
 The MIO700 requires installation of the higher-power PFM04X_H power supply, in which
case the platform is configured as an OPT9904X_H.
 Mixtures of MIO700 and MIO200 cards configured in the same platform are not allowed.
 In the current version, the maximum supported bandwidth for the MIO700 is 660G. 400G is
reserved for the lines ports (0, 1). 260G is available for the for the rest of the (client) ports.
Port 0 supports OTU4, OTUC2, and OTUC4. If Port 0 is configured to OTUC4, then Port 1
is not assignable (since the maximum bandwidth of Port 0 and Port 1 together is 400G).
Port 1 supports OTU4 and OTUC2.

The MIO700 card can be configured with:

 2 x CFP2, with each one supporting OTUC1/2/4, for a total of 400G uplink
 24 x 10G ports, configured with:
 6 x QSFP+, with each one supporting any mixture of:
 SDH/SONET: STM-64/OC-192 (ports 3-7)
 40GbE
 10GbE
 OTN: OTU2, OTU2e
 3 x QSFP28, supporting:
 ETY100G
 OTU4
 Port 2 supports SR4/CWDM4/ER4 with FEC-enabled 100GbE
 LR4 is supported in all QSFP28 ports
 All services (SDH/SONET, FC, Ethernet) are supported with full transparency, including timing
and OH
 ODUflex and G.HAO support hardware ready
 Traffic protection options include ODU SNC, DRI, DNI, and ASON
 SNCP for ODU0/1/2/2e/3 and ODU-flex services
 Client port protection (splitter coupler)
 GCC features:
 GCC supported in standard (full rate) mode
 One GCC channel supported per port, either GCC0, GCC1, or GCC2, software configurable

Ribbon Communications Inc. Proprietary 4-17

 Apollo Reference Manual OPT9904X platform architecture and cards

 Line ports 0 and 1 support 1 GCC channel per port, up to OTUC2/OTU4 rate, software
configurable
 Client port 2 supports 1 OTU4 GCC channel
 Maximum of 2 OTUC2/OTU4 GCC channels per card
 Maximum of 4 OTU2/OTU2e GCC channels per card
 Standard SC-FEC for 100Gbps line rate interoperability (supported OTR200_CFO modules)

Card views
General view

Front panel

The line ports are numbered 0 and 1. The numbering of the client ports is from 2 to 7.

Port configuration guidelines

NOTE: Several limitations apply when configuring MIO700 ports to specific rates. These
limitations are described in this section. Yes in the following table indicates an allowed
(supported) configuration option.

MIO700 fan-out port configuration rules

STM64/
Port Transceiver OTUC4 OTUC2 OTU4 OTU/OTU2e ETY100G ETY40G ETY10GOC OC192
0 1 Yes Yes Yes
1 2 Yes Yes
2 3 Yes Yes Yes
3 3 Yes

Ribbon Communications Inc. Proprietary 4-18

 Apollo Reference Manual OPT9904X platform architecture and cards

STM64/
Port Transceiver OTUC4 OTUC2 OTU4 OTU/OTU2e ETY100G ETY40G ETY10GOC OC192
4 3 Yes
5 3 Yes
6 4 Yes Yes Yes Yes Yes Yes
7 4 Yes Yes Yes
8 4 Yes Yes Yes
9 4 Yes Yes Yes
10 5 Yes Yes Yes Yes Yes Yes
11 5 Yes Yes Yes
12 5 Yes Yes Yes
13 5 Yes Yes Yes
14 6 Yes Yes Yes Yes
15 6 Yes Yes Yes
16 6 Yes Yes Yes
17 6 Yes Yes Yes
18 7 Yes Yes Yes Yes
19 7 Yes Yes Yes
20 7 Yes Yes Yes
21 7 Yes Yes Yes
22 8 Yes Yes Yes
23 8 Yes Yes Yes
24 8 Yes Yes Yes
25 8 Yes Yes Yes

Note the following assignment guidelines:

 If either ETY40G, ETY100G, or 100GE_OTU4 is configured on a transceiver, then you will not be
allowed to also configure the other 3 ports sharing same transceiver.
 If 10G service is configured for the fan-out ports on a transceiver, then you will not be allowed to
also configure ETY40G, ETY100G, or 100GE_OTU4 on that transceiver.
 Each slice (0 or 1) supports up to 100G. You will not be allowed to add any other assignments that
would exceed this maximum bandwidth.
 In the current version, the maximum supported bandwidth is 660G. 400G is reserved for the lines
ports (0, 1). Therefore:
 If Port 0 is configured to OTUC4, then Port 1 is not assignable (since the maximum
bandwidth of Port 0 and Port 1 together is 400G).
 If Port 0 is configured to OTUC4, or if Port 0 and Port 1 are both configured to OTUC2,
reaching a total of 400G, then any client assignment beyond 260G is not allowed. Client
assignments of 300G are only allowed if the line port assignment doesn't reach 400G.

Ribbon Communications Inc. Proprietary 4-19

 Apollo Reference Manual OPT9904X platform architecture and cards

The marking above each port identifies the Transmit (Tx) and Receive signals (Rx). The client port
LEDs are at the middle of the card. Each port has two LEDs: Tx and F/L, and can be identified
according to the number between the pair.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when
there is no fault in the MIO200.
Line (CFP) port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the CFP pluggable transceiver, or the
supply voltage or temperature is OOR.
Client port (SFP and SFP+) LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the SFP+/QSFP+ pluggable
transceiver, or the supply voltage or temperature is OOR.

Ribbon Communications Inc. Proprietary 4-20

5 OPT9901X platform architecture and
cards
The Apollo OPT9901X platform supports multiple network functionalities in a single platform, through
software configuration of virtual assignable I/O cards. To change the platform functionality, you don't
have to manually replace a physical card. You simply right-click the platform in the management
software and select a configuration (ADM , MADM , CPE , AGG) from the menu.
The OPT9901X changes the equation for provisioning L1 business services. Rather than mapping
multiple colored interfaces onto a ring using muxponders, each requiring engineering, it enables
supporting all services on a single 100G wavelength. L1 services connect to the OPT9901X via low-
cost gray interfaces, and are added to the ring traffic under software control.
The OPT9901X platform is designed for small regional or metro access networks requiring ODU-XC for
flexible grooming of 10G and sub-10G networks to OTU4. The OPT9901X integrates full OTN,
Ethernet, TDM, and SAN functionality in a single compact platform, and can be configured for cost-
effective 100G ADM or CPE applications, with up to 20x10G or 16x1G client interfaces, for efficient
grooming of services at the SDH/SONET/Ethernet/ODU level, in ring, hub, or terminal topologies.
This section describes the platform layout of the OPT9901X platform. The OPT9901X is based on an
efficient “fabric-less” design, generating savings by aggregating L3 traffic and reducing the number of
costly router ports. Apollo platforms have been designed to facilitate simple installation and easy
maintenance. Platform dimensions are sized for 19" racks, with 44 mm height (1U) and 290 mm depth.
The OPT9901X platform can also be installed in ETSI racks when the front of the rack is left open. The
cage design and mechanical practice of all platforms conform to international mechanical standards
and specifications.

The OPT9901X system architecture includes the following components:

 Control and communications subsystems built-in
 Cross-connect functionality
 Power feed subsystem, supporting a mixture of AC+DC
 Management system:
 IMG port for in-band management
 LCT/ports for debugging and LCT connections
 Additional/3rd-party shelf management

Usage guidelines
 All installation instructions, technical specifications, restrictions, and safety warnings are provided
in the Apollo Platform Installation and Maintenance Manuals. See these manuals for specific
instructions before beginning any Apollo installation.
 Contact Ribbon customer support for help configuring specific traffic flows, with the appropriate
GCC communication, protection, and encryption mechanisms in place.

Ribbon Communications Inc. Proprietary 5-1

 Apollo Reference Manual OPT9901X platform architecture and cards

5.1 OPT9901X platform layout

The OPT9901X integrates full OTN, Ethernet, TDM, and SAN functionality in a single compact platform,
and can be configured for cost-effective 100G ADM or CPE applications, for efficient grooming of
services at the SDH/SONET/Ethernet/ODU level, in ring, hub, or terminal topologies. The platform
includes:
 Switching capacity of 400G. Universal support for OTN switching (ODUk cross-connect [0, 1, 2,
2e, 4, Flex])
 Line interfaces supporting 2 x 100G (OTU4) uplinks up to 10/40/80Km
 Client interfaces supporting up to 20x10G or 16x1G client interfaces, with the following modes:
 Ethernet: GbE, 10GbE
 OTN: OTU2/2e, OTU4
 TDM: STM-1/4/16, OC3/12/48
 Encryption supported for ODU2/2e/4 uplink with end-to-end encryption, interoperable with
encryption cards such as the MIO200EN and HIO500EN
 AUX XFP ports: OTDR + optical booster (amplifier) (future)
 Restoration: ODU SNC-N protection
 GCC for in-band management:
 Supporting up to 6 GCC channels as follows:
 2 GCC channels supported on line ports #22 and #23, in ODUk or OTUk bytes
 Up to 4 GCC channels (2 per slice) supported on client ports with OTU2/OTU2e services
(over ODUk or OTUk)
 In AGG200 and ADM100 modes, supporting up to 10 GCC ports in total on OTU2/2e clients
and on OTU4 uplinks.
 Power supply: Dual removable AC or DC power supplies, max power consumption <250W
 AC: Two power feed modules for 110/220V
 DC: Two power feed modules using a 40.5 to 60 VDC power source
 Mixture: Combination of one AC module and one DC module
 Built-in controller module
 Built-in fan control module (FCM01X) (field-replaceable)
 Built in filter tray (field-replaceable)

Ribbon Communications Inc. Proprietary 5-2

Apollo Reference Manual OPT9901X platform architecture and cards

LEDs and ports on OPT9901X

Marking Item Functions
Platform ports
IMG RJ-45 10/100/1000Mbps management connection to DCN.
connector
CONSOLE RJ-45 Serial RS-232 communication port for use by technical support personnel
connector (CLI, debug, maintenance, etc.). All standard baud rates are supported;
typically set to 115200.
MSM RJ-45 Multi-shelf management enabling 10/100/1000Mbps management
connector connection to 3rd-party.
LCT RJ-45 10/100/1000Mbps terminal management interface for connecting to an LCT.
connector
USB USB2 / Currently disabled
USB3
Port LEDS
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter
is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a BIT fault is
detected in the CFP pluggable transceiver, or the supply voltage or
temperature is OOR.
Platform LEDs
IS Green LED Lights during one of the following:
 During upload time
 When platform is active and has no BIT failure
Off in case of BIT failure.
FAIL Red LED Lights during one of the following:
 In case of BIT failure
 If platform still in mid-reset
Off if there is no BIT failure.
SSD Yellow LED Blinks during writing operation on SSD card.
Off when there is no writing operation on SSD card.
MJR Orange LED Lights when a major alarm is detected in the platform. Remains lit while any
such alarm is active. Turns off upon termination of all alarms of this degree.
MIN Yellow LED Lights when a minor (or warning) alarm is detected in the platform. Remains
lit while any such alarm is active. Turns off upon termination of all alarms of
this degree.
CR Red LED Lights when a critical alarm is detected in the platform. Remains lit while
any such alarm is active. Turns off upon termination of all alarms of this
degree.

Ribbon Communications Inc. Proprietary 5-3

 Apollo Reference Manual OPT9901X platform architecture and cards

5.2 OPT9901X common cards and modules

The OPT9901X includes cards and modules that provide common functionality such as power supply
and air-cooling.

5.2.1 PFM01X_DC/PFM01X_AC
Supported platform
 OPT9901X

Description
The PFM01X_DC and PFM01X_AC are input power supplies for the OPT9901X, protecting the
equipment from external abnormal voltage connectivity. Each platform has two power supply units for
redundancy purposes. It is recommended to connect each to a different power source (unless only one
power source is available). When only one power source is available, it is recommended to connect it to
the two power inputs of both units. In such case, and provided a redundant power supply is installed,
the faulty unit can be replaced without affecting traffic.

Functions
The power supply units perform the following functions:
 PFM01X_DC: Input DC voltage (-48 V)
 PFM01X_AC: Input AC voltage (110/120V AC)
 Provision of maximum power of 250 W
 Reverse polarity protection (PFM01X_DC)
 Surge protection (1KV line to line, 2KV line to ground)
 Over-voltage protection
 Over-current and short circuit protection
 Part of hold-up capacitors
 Power Good indication
 Fail indication

Ribbon Communications Inc. Proprietary 5-4

Apollo Reference Manual OPT9901X platform architecture and cards

Module views
PFM01X_DC front panel

PFM01X_AC front panel

PFM01X_DC module

Ribbon Communications Inc. Proprietary 5-5

Apollo Reference Manual OPT9901X platform architecture and cards

PFM01X_AC module

LEDs and connectors

Description Item Functions

Status LED Lights steadily GREEN when working correctly.
Lights RED if there is a failure on in the module output voltage.
PFM01X_AC C14, 3-pin Connects AC power to the unit.
POWER IN connector
PFM01X_DC 5W5 D-type Connects the DC power source to the module.
POWER IN connector

Ribbon Communications Inc. Proprietary 5-6

 Apollo Reference Manual OPT9901X platform architecture and cards

5.2.2 FCM01X
Supported platform
 OPT9901X

Description
The FCM01X provides cooling air to the system from five separate fans, positioned at the right side of
the OPT9901X. Air is drawn in by the fans from the right side of the chassis and pumped out through
the left side of the chassis. The fans are fed through control circuits that improve the system's
performance and support its redundancy.
The FCM01X includes a controller that controls the operation of the fans. If one of the fans fails, the
remaining ones operate in turbo mode and the Fail LED lights in red until the FCM01X is replaced.
If the operation does not take more than two minutes, the FCM01X can be extracted and replaced
without interrupting system operation (hot swapping). We recommend preparing the replacement
module in advance and so shortening replacement time to a minimum.

WARNINGS:
 Don't leave the OPT9901X platform operating without an FCM01X.
 If you must replace an FCM01X, don't leave the system without an FCM unit for
more than 2 minutes.

Functions
Features of the FCM01X include:
 Each adjacent pair of fans has a PWM control of its own:
 PWM speed control levels are defined for all 5 fans; see System Specifications for details
 The levels are controlled by the built-in controller unit via a control bus
 LED status indicators:
 Green LED indicates all fans are working properly
 Red LED indicates a fan failure
 External alarm outputs and inputs:
 4 output alarms (relay dry contacts)
 4 input alarms (opto-couplers)

Ribbon Communications Inc. Proprietary 5-7

 Apollo Reference Manual OPT9901X platform architecture and cards

Card views
Front panel

General view

LEDs and ports

Marking Item Functions

ACT Green LED Lights steadily when the card is powered and operating normally.
FAIL Red LED Normally off. Lights steadily when a fault is detected.
ALARMS 36-pin SCSI Connects alarm input and output lines via a RAP or directly to the client.
connector

Ribbon Communications Inc. Proprietary 5-8

 Apollo Reference Manual OPT9901X platform architecture and cards

5.3 ADM functionality

The OPT9901X can be configured for ADM100 "virtual card" functionality, supporting 10-20 clients
mapped to 2 x OTU4 lines, as follows:
 Line:
 2 x OTU4 with encryption support
 Client:
 Up to 16 x 1GbE/STM-1/STM-4/OC-3/OC-12
 Up to 8 x STM-16/OC-48
 Up to 10 x 10GbE/OTU2/OTU2e
 Up to 10 x OTU2x
 Support for up to 10 GCC ports in total on OTU2/2e clients and OTU4 uplinks.

Ribbon Communications Inc. Proprietary 5-9

Apollo Reference Manual OPT9901X platform architecture and cards

5.3.1 Service configuration guidelines (ADM100)

SFP/SFP+ SFP/SFP+ SFP/SFP+ SFP/SFP+ SFP/SFP+ SFP/SFP+ SFP+ QSFP-DD QSFP-DD

ADM100 Service TS # [0,4,8] [2,6] [12] [10,14] [1,3,5,7,9] [11,13,15] [16-19] [22] [23]
(Client) (Client) (Client) (Client) (Client) (Client) (Client) (Line-EN) (Line-EN)
Ethernet 1GbE 1 Yes Yes Yes Yes Yes Yes
10GbE 8 Yes Yes Yes
SDH STM-1/4 1 Yes Yes Yes Yes Yes Yes
STM-16 2 Yes Yes Yes Yes
SONET OC-3/12 1 Yes Yes Yes Yes Yes Yes
OC-48 2 Yes Yes Yes Yes
OTNx OTU2e 8 Yes Yes Yes Yes Yes Yes Yes
OTU2 8 Yes Yes Yes Yes Yes Yes Yes
OTU2ch 8 Yes Yes Yes Yes
OTU4 80 Yes Yes

Ribbon Communications Inc. Proprietary 5-10

 Apollo Reference Manual OPT9901X platform architecture and cards

5.4 Multi-ADM functionality

The OPT9901X can be configured for MADM10 "virtual card" functionality, supporting 16 sub-10G
clients mapped to 4 x OTU2 lines, as follows:
 Line:
 4 x OTU2x with encryption support
 Client:
 Up to 16 x 1GbE/STM-1/STM-4/OC-3/OC-12
 Up to 8 x STM-16/OC-48
 Up to 2 x 10GbE/OTU2/OTU2e

Ribbon Communications Inc. Proprietary 5-11

Apollo Reference Manual OPT9901X platform architecture and cards

5.4.1 Service configuration guidelines (MADM10)

SFP/SFP+ SFP/SFP+ SFP/SFP+ SFP/SFP+ SFP/SFP+ SFP/SFP+ SFP/SFP+ SFP/SFP+ SFP+

QSFP-DD
MADM10 Service TS # [0,4] [2,6] [1,3,5] [7] [8] [10,14] [12] [9,11,13,15] [16-19]
[22-23]
(Client) (Client) (Client) (Client) (Client) (Client) (Client) (Client) (Line-EN)
Ethernet 1GbE 1 Yes Yes Yes Yes Yes Yes Yes Yes
10GbE 8 Yes Yes
SDH STM-1/4 1 Yes Yes Yes Yes Yes Yes Yes Yes
STM-16 2 Yes Yes Yes Yes Yes
SONET OC-3/12 1 Yes Yes Yes Yes Yes Yes Yes Yes
OC-48 2 Yes Yes Yes Yes Yes
OTNx OTU2e 8 Yes Yes Yes
OTU2 8 Yes Yes Yes
OTU2ch 8 Yes

Ribbon Communications Inc. Proprietary 5-12

 Apollo Reference Manual OPT9901X platform architecture and cards

5.5 CPE10 functionality

The OPT9901X can be configured for CPE10 "virtual card" functionality, supporting 1-4 x 10G clients
mapped to 2-8 x OTU2/2e lines, as follows:
 Line: 2 x 4 x OTU2/OTU2e with encryption support
 Client: 4 x 10GbE/OTU2/OTU2e

 Mixtures of ADM10 and CPE10 are supported (1x10G mapped to 2xOTU2E)

5.5.1 Service configuration guidelines (CPE10)

SFP+ SFP+
QSFP-DD QSFP-DD
CPE10 Service TS # [0-9] [10-19]
[22] [23]
(Client) (Line-EN)
Ethernet 10GbE 8 Yes
OTNx OTU2e 8 Yes Yes
OTU2 8 Yes Yes

Ribbon Communications Inc. Proprietary 5-13

 Apollo Reference Manual OPT9901X platform architecture and cards

5.6 Agg200 functionality

The OPT9901X can be configured for Agg200 "virtual card" functionality, supporting 20 x OTU2/2e (can
be channelized) mapped to 2 x OTU4, as follows:
 Line:
 2 x OTU4
 Client: (with encryption support)
 10 x OTU2/OTU2e
 10 x OTU2x
 Support for up to 10 GCC ports in total on OTU2/2e clients and OTU4 uplinks.

5.6.1 Service configuration guidelines (Agg200)

SFP/SFP+ SFP/SFP+ QSFP-DD
Agg200 Service [0-9] [10-19] [22-23]
(Client-EN) (Client-EN) (Line)
Ethernet 1GbE
10GbE
SDH STM-1/4/16

STM-64
SONET OC-3/12/48

OC-192
FC100/200/400
FC
FC800/1200/1600
OTNx OTU2e Yes Yes
OTU2 Yes Yes
OTU2ch Yes
OTU4 Yes

Ribbon Communications Inc. Proprietary 5-14

6 OPT96xx platform architecture
This section describes the layout and architecture of the OPT96xx platforms. OPT96xx transport
platform offer a total client and network capacity of up to 19.2T, with an arsenal of transponders and
muxponders including 100G, 200G, and 400G network interfaces that are software programmable for
varied client mixes. The platforms support up to 20 degrees of all-optical networking using flexible-grid
CDC ROADMs. Consistent with our modular distributed architecture design philosophy, the OPT99xx
platforms utilize the same optical, Layer 1, and Layer 2 service cards. Service cards or photonic
modules can be installed in any of the I/O slots. Once all the available slots are in use, one or more
cages can be added to the system and additional cards plugged in to the new cages with no disruption
of service.
Apollo platforms have been designed to facilitate simple installation and easy maintenance. Hot
insertion of cards and modules enables quick maintenance and repair activities without affecting traffic.
The cage design and mechanical practice of all platforms conform to international mechanical
standards and specifications.
This section describes the layout and architecture of the OPT96xx platforms, focusing on the following
components:
 Platform layout
 Control and communications subsystems, including:
 Control
 Communications
 Timing and synchronization
 Universal fabric
 Cross-connect functionality
 Distributed forwarding architecture
 Packet processing
 Power feed subsystem
 Management system

NOTE: All installation instructions, technical specifications, restrictions, and safety

warnings are provided in the Apollo Platform Installation and Maintenance Manuals. See
these manuals for specific instructions before beginning any Apollo installation.

Ribbon Communications Inc. Proprietary 6-1

 Apollo Reference Manual OPT96xx platform architecture

6.1 OPT9624 platform layout

The OPT9624 dimensions are sized for ETSI racks, with 674 mm height (15U), 492 mm width, and 311
mm depth.
The OPT9624 integrates ODU cross connect, Ethernet Layer 2/MPLS/Layer 3 switching, and full WDM
functionality. This is a versatile, scalable, cost-effective system in a single compact platform that caters
to virtually every demand.
The OPT9624 platform includes:
 Two slots for redundant Routing Control Processor (RCP_24T) cards.
 Two slots for redundant Power Filter Modules (PFM24), using a DC power source.
 One slot for the FCM24 fan unit.
 One slot for the CEM24 card providing the physical interface between Apollo and external
management and clock devices.
 24 universal I/O slots, with slot allocation optimized per application:
 Up to 4 slots for fabric cards or service and photonic cards.
 Additional 20 slots for service and photonic cards.

Platform layout

The following figure shows the OPT9624 slot allocation.

Ribbon Communications Inc. Proprietary 6-2

 Apollo Reference Manual OPT96xx platform architecture

Slot allocation

The OPT9624 also includes fiber management areas to help neatly route cables, and fibers connected
to the platform and one slot for an air filter located at the bottom.

6.1.1 OPT9624 platform configurations

The OPT9624 platform can be configured with different fabric matrix cards or without fabric at all, to
support various applications. According to the fabric installed, there are two main OPT9624
configurations:
 High capacity 1 Tbps fabric, suitable for mixed OTN and data applications
 No fabric, suitable for pure WDM applications and packet OTS
The following figures depict the layout of the three OPT9624 configurations.

Ribbon Communications Inc. Proprietary 6-3

 Apollo Reference Manual OPT96xx platform architecture

OPT9624 with four FM1000 cards

OPT9624 with no fabric cards

Ribbon Communications Inc. Proprietary 6-4

 Apollo Reference Manual OPT96xx platform architecture

The following table summarizes the OPT9624 configuration options.

OPT9624 platform configurations

Configuration Fabric Fabric Number of Number of I/O card Application

capacity card type fabric cards I/O cards types
High capacity 1 Tbps FM1000 3:1 20 Optical/data Mixed
OTN/data/WDM
No fabric -- -- -- 24 Optical only Pure OTN/WDM

6.2 OPT9608 platform layout

The OPT9608 dimensions are sized for 19" racks, with 221 mm height (5U), 443 mm width, and
253 mm depth.
The OPT9608 platform includes:
 Two slots for redundant Routing Control Processor cards.
 Eight I/O slots for photonic and I/O cards.
 Two slots for redundant Power Filter Modules (PFMs), using an AC or DC power source.
 One slot for Fan Control Module (FCM) drawer with nine fans, including an internal alarm
connector module (ACM) and built-in air filter. When using the FCM08_S, three optional multi-
shelf management ports are available. Airflow is directed horizontally from right to left.

OPT9608 platform layout

The following figure shows the OPT9608 slot layout.

OPT9608 slot layout

Ribbon Communications Inc. Proprietary 6-5

 Apollo Reference Manual OPT96xx platform architecture

6.3 OPT9603 platform layout

The OPT9603 dimensions are sized for 19" racks, with 88 mm height (2U), 442 mm width, and 240 mm
depth.
The platform includes:
 Three universal slots for data service and photonic cards.
 One slot for the main controller card.
 Two slots for redundant power feed modules using a -48 VDC power source.
 One drawer for the fan control module with nine fans.
 Filter tray.

OPT9603 platform layout

The following figure shows the OPT9603 slot allocation.

OPT9603 slot numbering

6.4 OPT96xx control and communications

subsystem
In all Apollo platforms, the controller subsystem is responsible for the following functionality:
 Internal control and traffic processing, accomplished through the main processor that has the main
activation software and a nonvolatile backup memory (NVM).
 Internal platform and card control.
 Internal communications and processing.
 Timing and synchronization.
 ODUk cross connection or packet switching.
 Double redundancy backup protection.
 Communication with external equipment and management.
 Comprehensive management functionality using General Communications Channel (GCC),
Optical Supervisory Channel (OSC), out of band management, or in-band management, with
dynamic Open Shortest Path First (OSPF) routing.
 Fault management, performance monitoring (PM), and maintenance.
 Built-In Test (BIT).
 NE software and configuration backup.

Ribbon Communications Inc. Proprietary 6-6

 Apollo Reference Manual OPT96xx platform architecture

6.4.1 OPT96xx control

The main controller subsystem supports central control, alarms, maintenance, and communication
functions. It also communicates with the control processors of the various cards using a master-slave
control hierarchy.
Each controller unit contains an NVM that stores a complete backup of both the system software and its
NE configuration. Through the NVM, Apollo benefits from superior management and control availability,
ensuring that a faulty controller unit does not affect traffic, even when only a single component is
installed.
Double redundancy in every platform can be obtained using a redundant NVM unit in the second
redundant controller subsystem, which is updated automatically on a regular basis. To maintain
synchronization, the operator can also initiate a manual NVM update whenever a change occurs in the
configuration.
The choice of redundant or nonredundant configuration depends on user preferences.
In the OPT9624 and OPT9608, the platforms can be operated in a redundant configuration, in which
the main controller card is protected with a second identical card. The redundant card contains a
database identical to the active card, and operates as a full capability standby control and
communication card.
In the OPT9603, the controller is implemented in a single RCP card (RCP03/RCP03R). The platform
doesn't support redundancy, therefore if the RCP fails or is extracted, communication capability with the
management station is lost; traffic that is already running is not affected but the ability to control the
platform is lost.
The OPT9624 and OPT9608 control subsystem is separate from the traffic subsystem. Traffic is not
impaired if the controller unit fails or is extracted. In this case, communication capability with the
management station is switched over to the second controller unit, as shown in the following figure. In
fact, once started, Apollo can operate without either controller unit when operating in pure WDM mode
with timing synchronization not required, since each unit has a separate local controller. In this case,
however, it loses its communication capability with the management station.

Control system block diagram

The controller subsystem enables easy software upgrades using a remote software procedure operated
from the STMS® management system. It can store several different software versions at the same time
and enables quick switchover between the different versions when required.

Ribbon Communications Inc. Proprietary 6-7

 Apollo Reference Manual OPT96xx platform architecture

6.4.2 OPT96xx communications

The main control processor subsystem is responsible for communications with external NEs and
management stations.
Communications with other NEs is through one of the following mechanisms:
 GCC channel, embedded in each OTU/ODU link via OTN services cards
 Out of band OSC channel
 In band management over Ethernet signals in Layer 2 cards
 External Data Communications Network (DCN)
Apollo performs IP forwarding between all network interfaces, including gateway management
interfaces. The management communication channel enables operators to integrate several platforms
with their own workstations, and to pass this management traffic through the Apollo system.
Apollo implements dynamic OSPF routing over the network interfaces to automatically determine the
routing table. OSPF support includes P2P protocol (PPP) encapsulation of IP packets with high level
data link control (HDLC), and framing over one of the management channels.
An Ethernet interface is used to communicate with STMS. The controller subsystem can also
communicate with a desktop or laptop PC-based craft terminal (Apollo CLI) via serial interface or
Ethernet.

Communications module
All OPT96xx platform configurations work with a communications module, featuring:
 Electrical interface connectors that are integrated into the I/O modules, eliminating the need for
separate electrical interface modules
 Easy routing of external management interfaces
 A monitoring system for acceptance test purposes
 Hot insertion of cards and modules to support quick maintenance and repair activities, without
affecting traffic

Ribbon Communications Inc. Proprietary 6-8

 Apollo Reference Manual OPT96xx platform architecture

6.4.3 OPT96xx flexible support for management mixtures

Management information is transmitted from the NMS/EMS to individual NEs through one of the
following mechanisms:
 External DCN
 GCC channel: Apollo platforms support in band management utilizing the GCC incorporated in
Layer 1 service cards (either standalone or fabric I/O cards). The GCC enables remote
management of equipment at any site where optical channels are dropped. This can increase
margins and extend distances of optical links as OSC filters are eliminated. Apollo supports
GCC0, GCC1, and GCC2. GCC1 and GCC2, integrated in the ODU overhead bytes, are usually
used when transmitting management over a third party domain that is not based on vendor
equipment. GCC0 is transmitted over OTU overhead bytes and terminated every time the OTN
signal is terminated. GCC is available for OTU1, OTU2, OTU3, and OTU4 signals.
 In band Ethernet channel: OPT96xx platforms can transmit management information over a
dedicated VLAN via in band Ethernet signals. In band Ethernet can be transmitted over GbE, 10
GbE, and 100 GbE interfaces (future). In band Ethernet management is only available when using
Layer 2 cards. The Layer 2 cards terminate the VLAN and extract the management information.
Management infrastructure, routing communications, and internal system control traffic all go
through the internal link between the RCP and the Forwarding Control Processor Module (FCPM)
on the data cards.
 OSC for WDM link management, implemented in one of the following modes:
 With an integrated Optical Time Domain Reflectometer (OTDR) functionality on top of the
supervisory channel. This is implemented either through dedicated OSC cards or integrated
into certain Apollo amplifier cards. It is based on an OSC-OTDR SFP, with FE at 1510 nm for
DWDM links. The OSC-OTDR SFP supports:
 1510 nm 30dB OSC reach
 40-80km OTDR reach – depending on the fiber type
 When the data channels themselves do not include embedded communication channels or if
there are no channel drops, as at an in-line amplifier site. The OSC is used as a
communication channel to enable the STMS to communicate with and control the Apollo.
OSC card enhances the optical layer functionality of the Apollo with out-of-band signaling and
a communications and control channel, completely separating the management function from
customer data.
This OSC implementation is either through dedicated OSC cards or integrated into certain
Apollo amplifier cards. OSC options include FE at 1310 nm for CWDM links, FE at 1510 nm
for DWDM links, or 2 Mbps at 1510 nm for extended spans (OSC card only). The OSC card
supports:
 Six FE management ports, allowing management information connections of up to six
degrees, using 1510 nm (DWDM) and 1310 nm (CWDM) SFPs.
 Two 2 Mbps management ports for extended reach applications, using 1510 nm SFPs.
Since the OSC operates at either 1510 nm or 1310 nm, it does not interfere with optical
channels operating in the 1550 nm range (C band). In addition, since the Apollo fully
integrates the smart optical layer with the OTN layer, GCC management channels can also
be used when available.
The Apollo OPT96xx platforms fully integrates the GCC, OSC, in band Ethernet, and external DCN
management channels, thus providing the operator with the flexibility to choose the most appropriate
management channel. Operators can even mix the different channels in a network or in the same
platform.

Ribbon Communications Inc. Proprietary 6-9

 Apollo Reference Manual OPT96xx platform architecture

6.4.4 OPT96xx routing and forwarding functionality

The routing and forwarding capabilities of the Apollo platforms are based on standard OSPF dynamic
routing, suitable for small, medium, and larger networks, and including a richer set of features for
network communications management.
In the OPT96xx platforms, the main control processor subsystem is responsible for communications
with external NEs and management stations. Communications with other Apollo NEs is via the GCC in
each OTN link, OSC, in band Ethernet, or external DCN.
An Ethernet interface is used to communicate with STMS. The controller subsystem can also
communicate with a desktop or laptop PC-based craft terminal (Apollo CLI) via a serial interface or
Ethernet. It also provides alarm outputs. Some of these network communications components and their
functionality are described in this chapter.

6.4.5 OPT96xx management channel with dynamic OSPF

A management channel enables operators to integrate several platforms with their own workstations
and to pass this management traffic through the ApolloOPT96xx platforms. The operator sets up an IP–
based DCN to carry IP packets between the management stations and the NEs. The DCN is composed
of Embedded Communication Channels (ECCs) supported by the equipment itself and an external DCN
supported by standard data equipment.
The Apollo performs IP forwarding between all network interfaces, implementing dynamic OSPF routing
over these network interfaces to automatically determine the routing table. OSPF can be configured for
any subset of network interfaces and supports:
 P2P and broadcast interfaces
 Up to four OSPF areas
 Address summarization
 Area Border Router functionality
 Autonomous System Border Router functionality, including redistribution of static routes
 Loopback address as a router ID
 Configuration of HELLO protocol parameters
 "Passive" interfaces to allow distribution of routes to attached devices
OSPF functionality enables a wide range of DCN configurations, adds resiliency to management
communications between NEs and the management stations, and reduces the ECC load, for a
significant improvement in management performance and NE capacity.
Under dynamic ECC routing, NEs ping each other through the available ECC interfaces and build their
own routing tables. Working with dynamic routing tables that respond to real time circumstances
simplifies ECC planning and maintenance, and reduces the ECC load by making it unnecessary to
reserve ECC protection paths in advance. There is also no need to plan ECC rings, since dynamic ECC
routing enables NEs to automatically set up new routes if the existing ones fail.

Ribbon Communications Inc. Proprietary 6-10

 Apollo Reference Manual OPT96xx platform architecture

6.4.6 VoIP in OPT96xx

The Apollo product line Voice over IP (VoIP) defines a way to carry voice calls over an IP network,
including the digitization and packetization of the voice streams.
Apollo VoIP is based on Session Initiation Protocol (SIP) for implementing the over-packet network
design.
SIP is a signaling protocol, widely used for controlling multimedia communication sessions such as
voice and video calls over Internet Protocol. The protocol can be used for creating, modifying and
terminating two-party (unicast) or multiparty (multicast) sessions consisting of one or several media
streams.
VoIP lines are used between a remote site and a central office during initial installation of the system, or
when no telephone line is available. All calls are bidirectional.
The VoIP capability is a fully integrated feature of the Apollo product line. It supports P2P, conference
calls, and all broadcast calls (future), and allows a person at any NE site to communicate individually or
simultaneously with the sites in the network.
The VoIP phone plugs into the Common External Module (CEM) in the OPT9624, or into the IMG
connector on the FCM in the OPT9608, or into the RCP03/RCP03R on the OPT9603 with Ethernet
cable connections.

6.5 OPT96xx universal fabric functionality

The heart of the Apollo OPT9624 is a powerful, high capacity, non-blocking universal fabric. The
universal fabric supports ODUk cross connecting. Apollo is equipped with four fabric cards working in a
3:1 protection scheme. Each I/O module is directly connected to all four fabric cards. In case of fabric
card failure, the I/O interface cards switch to the fourth card within less than 50 msec.
The following figure illustrates the simplified Apollo internal traffic flow. It provides an overview of both
the physical and functional partitioning of the system. Each of the blocks represents an I/O slot that can
accommodate any type of card with any bitrate and service.

Universal fabric system architecture

6.6 Cross-connect functionality

Cross connects are used to define connectivity between tributaries and L1 interfaces having compatible
bandwidth. The connectivity can be between tributaries on the same card or between different cards via
the fabric matrix (ODU XC). The Apollo fabric (FM1000) enables efficient and cost-effective cross-
connect capabilities with ODUk granularity for all tributary signals.

Ribbon Communications Inc. Proprietary 6-11

 Apollo Reference Manual OPT96xx platform architecture

There are three XC modes in the Apollo:

 Fixed XC: configured by the NE when there is one single fixed connectivity, for example XC in
passive optical or amplifier cards
 User-configurable XC: connection between cards via the fabric, or connection between services
in a card
 Signaling/dynamic XC: created and deleted by signaling protocols
The traffic cross-connect functions are implemented by the non-blocking high-capacity cross-connect
FM1000 fabric cards. Four cards are configured in a 3:1 protection scheme that provides a capacity of 1
Tbps with 50 Gbps per I/O slot.
The fabric matrix cards receive the traffic from the various I/O cards installed in the platform through
wideband buses, using a format that does not depend on the type of I/O card installed in any specific
slot.
At any time, the main and protection card are active (that is, switch the traffic). This means that each
trail terminated in the platform is independently processed by each cross-connect matrix; the resulting
streams are sent in parallel to the trail I/O drop cards, and each card selects the stream to be
connected to the external equipment via the receive path.
The fabric supports ODU XC at the ODUk level for I/O cards. The XC is supported for cards residing on
the same platform. In addition to ODU XC, the fabric also supports data traffic switching for L2 cards
(future).
ODUSlot (equivalent to ODU0), provides cross connect for ports with BW less than 1.25 Gbps. This
enables ODU XC of ports with STM-1/OC-3, STM-4/OC-12, 1 GbE, and FC100 rates.
The following figure shows examples of different ODU XC options through the fabric cards.

ODU XC in fabric cards example

Ribbon Communications Inc. Proprietary 6-12

 Apollo Reference Manual OPT96xx platform architecture

6.6.1 Types of cross-connections

Unidirectional and bidirectional
A unidirectional connection connects a single input port to a single output port in one direction only. A
bidirectional connection connects the input and output of a single port to the output and input of another
port in both directions. Both connection types are shown in the following figures.

Unidirectional XCs

Bidirectional XCs

Connectivity types
Apollo supports the following XC connectivity types:
 One way unprotected, implemented through one of the following options:
 Option 1: The XC is from one tributary/L1 interface in an input port to an equal (in bandwidth)
tributary/L1 interface in an output port. The corresponding tributaries/L1 interface in the
opposite direction can be used for a different XC. This option is shown in the following figure.

P2P one-way XC

 Option2: A tributary/L1 interface on an input port can be connected to more than one
tributary/L1 interface in output ports. We can use such a connectivity type for multicast
applications, broadcast applications, drop-and-continue, etc. This option is shown in the
following figure.

Ribbon Communications Inc. Proprietary 6-13

Apollo Reference Manual OPT96xx platform architecture

P2MP one-way XC

 Two way unprotected, from one tributary/L1 interface in an input port to an equal (in BW) output
port, and vice versa.

P2P 2-way XC

 One way protected, where the output port is protected by two input ports that are unidirectional.

One way protected XC

 Two way protected, where the input port is protected by two output ports. This is also called Sub-
Network Connection Protection (SNCP). When such an XC is applied inside a card, it is also
called a YP (Y-protection) XC.

2-way protected XC

Ribbon Communications Inc. Proprietary 6-14

 Apollo Reference Manual OPT96xx platform architecture

 Two way fully protected, where the XC comprises 4 x 2-way protected ports. The traffic is
protected against more than a single failure.

2-way XC with full protection

 SNCP N bidirectional XC: This XC has all alternative paths used to protect a line port. Since
there is more than one protecting leg, the operator must specify which leg is the main. The XC
consists of N legs that such an XC can have.

Ribbon Communications Inc. Proprietary 6-15

 Apollo Reference Manual OPT96xx platform architecture

 Protection Group: The user can create a protection group that includes several Deg-n ports
(user selection). One of the Deg-n ports is the default active port connected to the line port. In
case of a defect in the active port, the line port switches to the other Deg-n port in the protection
group, and if this port is also in a fail state, it switches to the next one in the protection group.

SCNP N bidirectional XC

6.7 OTN technology

The Apollo system is based on OTN technology, ensuring carrier-grade capabilities and unmatched
Quality of Service (QoS). OTN adapts capabilities developed for SDH/SONET technology and extends
them to the Optical Transport Hierarchy (OTH) layers. It enables clear supervision of the full optical
channel data unit (ODU) path or any section of the network, providing the ability to monitor,
troubleshoot, and isolate any fault in the network. This capability significantly reduces OPEX.
The OTN transmission layer provides a converged pathway for legacy SDH/SONET as well as
advanced high-capacity Ethernet offerings. Sub-lambda services can be groomed over a single pipe.
Each service is kept intact, with its own overhead and original timing clock, using its own protection
scheme, according to the customer SLA. Apollo combines OTN technology with ASON GMPLS-based
control and restoration to provide carrier-grade capabilities and ensure the appropriate QoS for each
service type.

Ribbon Communications Inc. Proprietary 6-16

 Apollo Reference Manual OPT96xx platform architecture

OTN as a universal transport layer, access to core

Apollo supports both Generic and Enhanced Forward Error Correction (GFEC/EFEC) compliant with
G.709. This increases maximum span length, reducing the need for regeneration sites and enabling
more ROADM nodes to be deployed along the signal path without 3R regeneration.
Similar to SDH/SONET, OTN is a simple technology to operate, with uncompromisingly strong OAM&P
capabilities. OTN also enjoys an advantage over SDH/SONET since it was designed to be
"DWDM-friendly". In addition, the OTN is not synchronized to a common clock source. Hence, OTN is
capable of carrying different services, providing full transparency for both overhead and timing.
With a full range of fixed and variable gain amplifiers, Apollo networks can be designed, simulated, and
implemented for distances greater than 2500 km (1550 miles). Apollo also provides highly cost-effective
solutions based on Raman amplifiers for repeaterless applications such as undersea implementations
of up to 400 km (250 miles).
Optical Network Control Parameters (ONCP) software continuously ensures network resiliency,
automatically monitoring and adjusting to changes in optical power induced by variations in span loss
and/or in the number of active channels, while ignoring fiber cuts and maintenance actions as well as
providing comprehensive status and history information. In addition to reducing OPEX, improves
service reliability, enabling an agile response to customer expansion that can ultimately increase
revenue.

Ribbon Communications Inc. Proprietary 6-17

 Apollo Reference Manual OPT96xx platform architecture

6.7.1 OTN topologies

This section presents the terms used to describe OTN topologies. As the topology of networks is
determined by communication requirements, the actual topology of any practical network is often a
combination of several basic topologies. Because of the flexible fine granularity of their cross-connect
matrix, Apollo platforms can support any network topology. Moreover, they can easily adapt to changing
network topologies as the customer’s needs evolve.

Point-to-point topology
A basic point-to-point topology is a connection between two terminal multiplexers (TM), without
protection. The link requires two fibers.

Point-to-point topology

If you want to add protection, then an additional set of fibers, which can be implemented using OMSP
cards, can be used for protection.

Ring topology
A ring topology links multiple Apollo platforms into a circle. The links require two fibers. The Apollo
platforms act as OTN ADM add/drop multiplexers, with SNC-N protection.

Ring topology

If you want to add protection for critical segments, then an additional set of fibers can be used, so there
are four fibers on those segments.

Multi-ring topology
A multi-ring topology consists of several rings that interconnect at one or more nodes. The main ring
thus provides connectivity between the secondary rings. Applications include metro and resilient
backhaul networks. When a secondary ring joins the main ring at two different nodes, it can provide
additional protection paths. Protection is generally provided through ODU DNI or DRI mechanisms.

Ribbon Communications Inc. Proprietary 6-18

 Apollo Reference Manual OPT96xx platform architecture

Multi-ring topology

Mesh topology
The mesh topology consists of nodes interconnected by many point-to-point links. This provides dense
connectivity between the nodes. Any desired segment may be protected using SNC-N or ASON
GMPLS.

Note: The border between multi-ring and mesh topologies is often blurred. For example,
the network shown in the following figure could easily be redrawn as a complex set of
interconnected rings. Mesh topology also includes star topologies, since stars are simply
subset variations of a complete mesh structure.

Mesh topology

Ribbon Communications Inc. Proprietary 6-19

 Apollo Reference Manual OPT96xx platform architecture

6.8 OPT96xx power feed subsystem

OPT96xx platforms feature a distributed fully redundant power feed subsystem. Two different power
sources (Source A and Source B) feed the xPFMs. The two redundant PFM modules filter and
distribute the -48 VDC nominal battery plant inputs to all internal cards through fully redundant power
buses. Each card generates its own local voltage using high quality DC/DC converters. This distributed
power concept assures system upgrading and efficient heat distribution. It also ensures maximum
reliability of the power feed subsystem.

Power distribution

Both connectors in the PFM module must be connected for power to be supplied to the whole platform.
Additional features of the power subsystem include:
 Reverse polarity protection
 Surge protection (2 kV line to line, 4 kV line to ground)
 Over-voltage protection
 Over-current and short circuit protection
 Redundancy and current sharing between PFM units
 Power fail detection + up to 10 msec holdup
 Under-voltage detection
 Lightning strike protection

Ribbon Communications Inc. Proprietary 6-20

7 OPT9624 common cards
The OPT9624 platform includes cards and modules that provide its common functionality like:
 Routing and control
 Management and timing connections
 Power supply
 Air cooling
 Control required for operation
 Packet switching fabric.
These units are described in the following sections.

7.1 RCP
The RCP card is the central control component in the OPT9624 system architecture, providing the main
system processor responsible for essential system management and timing control. Two RCP modules
must be installed in the platform for redundancy.
RCP cards enable comprehensive management communication functionality with dynamic OSPF
routing. These cards are responsible for communications with external NEs and network management
(STMS) communication. RCP cards can be configured for 1:1 redundancy. All connectivity from the
RCP to any card is kept redundant via the dedicated internal communication links.
The OPT9624 offers two different RCP options, RCP24_T and RCP24_O.

7.1.1 RCP24_T: universal controller

Supported platform
 OPT9624

Description
The RCP24_T is the central control component in the OPT9624 system. It supports the following
management and alarm interfaces and functions:
 Main system processor, responsible for essential system management.
 Serial RS232 interface for local CLI connection.
 Terminal Ethernet management interface port supporting 100 Mbps.
 Operation and alarm LEDs.
 Active CTM.
Two RCP24_T modules may be installed in an OPT9624 platform for redundancy.
The Apollo product line relies on a highly scalable, internet-class routing engine designed specifically to
interoperate seamlessly with current IP backbones. As the main platform controller, the RCP runs the
system software and a full suite of routing protocols, including BGP, OSPF-TE, IS-IS-TE, and RIPv2, as
well as MPLS signaling (RSVP-TE, LDP), MPLS-TP, and multicast (PIM-SM, MBGP, IGMPv2).

Ribbon Communications Inc. Proprietary 7-1

 Apollo Reference Manual OPT9624 common cards

The Apollo product line has an efficient modular design that is expressed in every aspect of the system.
This design works well with all the different line cards, offering the same top quality features and
benefits across all types of interfaces. Technology reuse also means a shorter time to market for later
follow on’ cards.

Functions
The RCP24_T provides the following main functions:
 Routing and control:
 Management communication
 CPU offload
 8 Gb SD card memory (NVM)
 Stores the platform's software code and configuration data base (on the NVM)
 Ethernet intra-platform networking
 EMS and LCT management support
 Timing to all I/O cards
 Announces the active RCP to all Field Replaceable Units (FRUs)
 Announces the active fabric(s) to all FRUs
 Self BIT
 Single or redundant RCP
 HA (High Availability):
 Active fabric distribution done immediately
 Hardware detection of major fabric card faults and switchover

WARNING: When the OPT9624 is configured to operate in ODU-XC, removal of both

RCP24_T cards and insertion of one or both cards will cause traffic down time of about 3
minutes.

Ribbon Communications Inc. Proprietary 7-2

 Apollo Reference Manual OPT9624 common cards

Card views
General view

Front panel

LEDs

Marking Item Functions

ACT Green LED Lights together with the STBY and FAIL LEDs during software
download. Lights steadily when the RCP is configured as the active
card. Off when the RCP has a failure or is configured as the standby
card.
STBY Yellow LED Lights together with the ACT and FAIL LEDs during software
download. Lights steadily when the RCP is configured as the standby
card. Off when the RCP is the active card.

Ribbon Communications Inc. Proprietary 7-3

 Apollo Reference Manual OPT9624 common cards

Marking Item Functions

FAIL Red LED Lights together with the ACT and STBY LEDs during software
download. Lights steadily when a fault is detected in the card. Off
when there is no fault in the RCP.
CTM Orange LED Lights when the CTM on the RCP24_T is active.

Ports

Marking Connector Functions

CONSOLE RJ-45 connector Serial RS-232 communication port for use by technical support
personnel (debug, maintenance, etc.).
EXP1 RJ-45 connector For future use.
EXP2
LOCAL MNG. RJ-45 connector Terminal management interface for connecting to an LCT.

7.1.2 RCP24_O: optimized for pure DWDM

Supported platform
 OPT9624

Description
The RCP24_O is an RCP card optimized for pure optical DWDM applications. The RCP24_O module
includes all the functionality of the standard RCP24_T except for the CTM module, which is not relevant
for pure optical configurations.
The RCP24_O is the central control component in the OPT9624 system architecture, providing the
main system processor responsible for essential system management and control. Two RCP modules
may be installed in the platform for redundancy. The RCP24_O supports the following management
and alarm interfaces and functions:
 Main system processor, responsible for essential system management.
 Serial RS232 interface for local CLI connection.
 Terminal Ethernet management interface port supporting 100/1000 Mbps.
 Two management Ethernet ports for connections to subtending platforms used in multiplatform
configurations (future function).
 Operation and alarm LEDs.
Two RCP24_O modules may be installed in an OPT9624 platform for redundancy.
The Apollo product line relies on a highly scalable, internet-class routing engine designed specifically to
interoperate seamlessly with current IP backbones. As the main platform controller, the RCP runs the
system software and a full suite of routing protocols, including BGP, OSPF-TE, IS-IS-TE, and RIPv2, as
well as MPLS signaling (RSVP-TE, LDP), MPLS-TP, and multicast (PIM-SM, MBGP, IGMPv2).
The Apollo product line has an efficient modular design that is expressed in every aspect of the system.
This design works well with all the different line cards, offering the same top quality features and
benefits across all types of interfaces. Technology reuse also means a shorter time to market for later
follow on cards.

Ribbon Communications Inc. Proprietary 7-4

 Apollo Reference Manual OPT9624 common cards

Functions
The RCP24_O provides the following main functions:
 Routing and control:
 Management communication
 CPU offload
 8 Gb SD card memory (NVM)
 Stores the platform's software code and configuration data base (on the NVM)
 Ethernet intra-platform networking
 Multi-platform infrastructure (future)
 EMS and LCT management support
 Announces the active RCP to all Field Replaceable Units (FRUs)
 Self BIT
 Single or redundant RCP
 HA (High Availability)

Card views
General view

Ribbon Communications Inc. Proprietary 7-5

 Apollo Reference Manual OPT9624 common cards

Front panel

LEDs

Marking Item Functions

ACT Green LED Lights together with the STBY and FAIL LEDs during software
download. Lights steadily when the RCP is configured as the active
card. Off when the RCP has a failure or is configured as the standby
card.
STBY Yellow LED Lights together with the ACT and FAIL LEDs during software
download. Lights steadily when the RCP is configured as the standby
card. Off when the RCP is the active card.
FAIL Red LED Lights together with the ACT and STBY LEDs during software
download. Lights steadily when a fault is detected in the card. Off
when there is no fault in the RCP.
EXP1 RJ-45 connector For future use.
EXP2
LOCAL MNG. RJ-45 connector Terminal management interface for connecting to an LCT.
CONSOLE RJ-45 connector Serial RS-232 communication port for use by technical support
personnel (debug, maintenance, etc.).

Ports

Marking Connector Functions

CONSOLE RJ-45 connector Serial RS-232 communication port for use by technical support
personnel (debug, maintenance, etc.).
EXP1 RJ-45 connector For future use.
EXP2
LOCAL MNG. RJ-45 connector Terminal management interface for connecting to an LCT.

Ribbon Communications Inc. Proprietary 7-6

 Apollo Reference Manual OPT9624 common cards

7.2 PFM24
Supported platform
 OPT9624

Description
OPT96xx platforms feature a distributed fully redundant power feed subsystem. Two different power
sources (Source A and Source B) feed the xPFMs. The two redundant PFM modules filter and
distribute the -48 VDC nominal battery plant inputs to all internal cards through fully redundant power
buses. Each card generates its own local voltage using high quality DC/DC converters. This distributed
power concept assures system upgrading and efficient heat distribution. It also ensures maximum
reliability of the power feed subsystem.

Power distribution

Additional features of the power subsystem include:

 Reverse polarity protection
 Surge protection (2 kV line to line, 4 kV line to ground)
 Over-voltage protection
 Over-current and short circuit protection
 Redundancy and current sharing between PFM units
 Power fail detection + 10 msec holdup
 Under-voltage detection
 Lightning strike protection
PFM24 power feed modules take a -48 VDC power feed input and distribute power to all cards in the
platform, providing up to 3500 W. Both connectors in the PFM module must be connected for power to
be supplied to the whole platform. OPT9624 platforms work with two PFM24 modules configured in a
load-sharing protection scheme.
The PFM24 serves as an input power filter for the DC voltage connected to the OPT9624. Each
platform has two PFM24 units for redundancy purposes. It is recommended to connect each to a
different power source (unless only one power source is available). When only one power source is
available, it is recommended to connect it to the two power inputs of both units. In such case, and
provided a redundant PFM24 is installed, the faulty unit can be replaced without affecting traffic.
The PFM24 provides power of up to 3500 W to the OPT9624. To supply this power, the unit structure
includes two input filters, each fed through a separate connector. Both connectors in the PFM module
must be connected for power to be supplied to the whole platform.

IMPORTANT: Even if only one power source is used, both input power feed ports should
be connected to the power source with standard cables.

Ribbon Communications Inc. Proprietary 7-7

 Apollo Reference Manual OPT9624 common cards

Functions
The PFM24 performs the following functions:
 Dual independent DC voltage input filters (-48 V)
 Control and alarms for each input
 Provision of maximum power of 3500 W
 Temperature sensing
 Input voltage monitoring
 Two DC power input connectors
 Power Good indication
 Fail indication

Card views
General view

PFM24 unit front panel

Ribbon Communications Inc. Proprietary 7-8

 Apollo Reference Manual OPT9624 common cards

LEDs
Marking Item Functions
POWER ON Green LED Lights steadily when the PFM24 input supply voltage through the
1 POWER IN 1 connector is in the allowed range.
POWER ON Green LED Lights steadily when the PFM24 input supply voltage through the
2 POWER IN 2 connector is in the allowed range.
FAIL Red LED Normally off. Lights steadily when a fault is detected in the unit.

Connectors
Marking Connector Functions
POWER IN 1 5W5 D-type connector Connects DC input power to the first filter in the unit.
POWER IN 2 5W5 D-type connector Connects DC input power to the second filter in the unit.

7.3 CEM24
Supported platform
 OPT9624

Description
The CEM24 module is connected to both RCP cards and provides a physical interface between the
OPT9624 platform and the external management, alarms, and clock devices. The CEM24 is the
connection unit between the OPT9624 and the external world. It provides interfaces to management,
timing, and alarms. The CEM24 is installed at the middle top of OPT9624 between the two PFM24 filter
modules.

Functions
The CEM24 provides the following main functions and interfaces:
 In-band management Ethernet port supporting 100 Mbps, connected to STMS
 Timing and synchronization inputs and outputs, including:
 E1/T1
 2MHz (BITS1/BITS2) (future)
 Pulse-per-second (1 PPS) (future)
 Time of Day (ToD) (future)
 Alarm interfaces and indications, including:
 Alarm severity LEDS (Critical, Major, Minor)
 External alarm outputs and inputs to client or RAP
 Operation LEDs displaying system operation and alarms
 Activations, including:
 LED tests for the entire platform
 Alarm Cut Off (ACO)

Ribbon Communications Inc. Proprietary 7-9

 Apollo Reference Manual OPT9624 common cards

Card views
General view

CEM24 unit front panel

Ports and pushbuttons

Marking Item Functions

ALARMS 36-pin SCSI connector Connects alarm input and output lines via a RAP or directly to
the client.
IMG RJ-45 connector Out-of-band management Ethernet interface for connecting to
an element management station (STMS) or a CLI terminal.
TOD RJ-45 connector Time of Day signal for supporting Ethernet timing per
IEEE 1588v2 standard (Not operational).
1PPS IN/OUT DIN 1.0/2.3 connectors 1PPS input/output signals for supporting Ethernet timing per
IEEE 1588v2 standard (Not operational).
ACO Pushbutton Used to temporarily disable the buzzer and set off the
corresponding alarm LED when an alarm condition is present.
The buzzer is activated again when a new alarm condition is
detected.
LED-TEST Pushbutton Turns on all LEDs located on cards/modules installed in the
platform, for test purposes.
BITS1 RJ-45 connector Main timing input/output clock using an E1/2MHz/1.5MHz
signal (Not operational).
BITS2 RJ-45 connector Additional timing input/output clock using an E1/2MHz/1.5MHz
signal (Not operational).

Ribbon Communications Inc. Proprietary 7-10

 Apollo Reference Manual OPT9624 common cards

LEDs

Marking Item Functions

POWER Green LED Indicates that the CEM24 card is powered and operating
normally.
FAIL Red LED Lights steadily when a fault is detected in the card.
CR Red LED Lights when a critical alarm is detected in the platform.
Remains lit while any such alarm is active. Turns off upon
termination of all alarms of this degree.
MAJ Orange LED Lights when a major alarm is detected in the platform.
Remains lit while any such alarm is active. Turns off upon
termination of all alarms of this degree.
MIN Yellow LED Lights when a minor (or warning) alarm is detected in the
platform. Remains lit while any such alarm is active. Turns off
upon termination of all alarms of this degree.

7.4 FCM24
Supported platform
 OPT9624

Description
The FCM24 fan control module, installed at the lower edge of the platform, includes 10 separate and
independent fans for secured resiliency. In case one or more of the fans fails, the rest increase the
ventilation speed to compensate. Air is drawn in from the lower part of the chassis and pumped through
the vertically mounted cards through the top of the chassis. The fans are fed through circuits that
improve the system's performance and support its redundancy.

Functions
Features of the FCM24 include:
 Separate power supply for each fan unit
 Each adjacent pair of fans has a control of its own:
 Multiple speed levels are defined for each pair; see System Specifications for details
 The levels are controlled by the active RCP24_T via a control bus
 Separate psophometric filter with a separate fuse for each fan
 Large capacitor with a fuse on the DC supply bus
 Parallel dual inrush current circuit with a separate fuse for each circuit
 Hold up capacitors (serves the PFM24)
A controller in the active RCP24_T controls the fans operation. If one of the fans fails, the remaining
start to operate in turbo mode, and the fail LED lights until the FCU is replaced. If done in a few
minutes, the FCU can be extracted and replaced without interrupting the OPT9624 operation (hot
swapping).

Ribbon Communications Inc. Proprietary 7-11

 Apollo Reference Manual OPT9624 common cards

WARNING: Do not leave the system without an FCU unit for more than a couple of
minutes.

Card views
General view

Front panel

Ports

Marking Item Functions

ACTIVE Green Lights steadily when the card is powered and operating normally.
LED
FAIL Red LED Normally off. Lights steadily when a fault is detected.

7.4.1 FCM24 air filters

OPT9624 platforms operating in extremely dusty and/or humid environments must be equipped with an
air filter. The OPT9624 has a dedicated slot for the air filter at the bottom of the platform.
The purpose of the air filter is to reduce the accumulation of dust and dirt on its internal components
carried by the cooling air flowing through the platform. The combination of dust and humidity produces
a capacitive/conductive layer between components installed on cards and modules. This may degrade
equipment performance or even cause malfunctions. Moreover, the insulating effect of a dust layer
causes components to operate at higher temperatures, so ultimately decreasing equipment reliability.
An air filter reduces dirt accumulation and thus prevents degradation of equipment reliability and
performance. However, filters do increase the resistance to airflow and should therefore carefully be
selected according to the actual operating conditions.
Apollo offers two types of FCM24 air filters:
 Low density foam filter, with a density of 10 PPI.
 High density foam filter (45 PPI) in compliance with NEBS standards. This is the default type
supplied with the OPT9624.

NOTE: The low density filter (10 PPI) must be ordered separately.

Ribbon Communications Inc. Proprietary 7-12

 Apollo Reference Manual OPT9624 common cards

Installing the air filter in the OPT9624

In extremely dusty sites or when NEBS compliance is required, the 45 PPI filter is suitable. For all other
sites, the 10 PPI filter is preferred.

NOTE: The insertion of the air filter into the OPT9624 activates a switch that reports its
presence to the system management. If an air filter is not installed, a "filter missing" alarm
is generated and reported.

Filter maintenance intervals must strictly be observed. These are application-specific and depend on
the environmental conditions. Clean or replace loaded filters. It is accepted for electronic equipment
design to recommend cleaning/replacing air filters every three months. The high density air filter (45
PPI) may become blocked in a shorter time and must be maintained more frequently.

CAUTION: After maintaining an air filter, carefully examine the material. If holes or tears
are detected, replace with a new filter.

Ribbon Communications Inc. Proprietary 7-13

 Apollo Reference Manual OPT9624 common cards

7.5 FM1000
Supported platform
 OPT9624

Description
FM1000 is a universal fabric switching matrix for the OPT9624 that provides up to 1 Tbps of ODU cross
connect, Ethernet Layer 2/MPLS packet switching, or any combination thereof OPT9624 is equipped
with four fabric cards working in 3:1 protection scheme. The cards are installed in four dedicated slots in
the middle of the platform. Each I/O card is directly connected to all four fabric cards. In case of fabric
card failure, the I/O interface cards switch to the fourth card within less than 50 msec.
The dedicated slots for the FM1000 in the OPT9624 are 8, 9, 10, and 11, as shown in the following
figure. The rest of the 20 slots can be populated with various optical, service, or data I/O cards.

OPT9624 with four FM1000 cards

NOTE: Configuration of the FM1000 in an OPT9624 must include two RCP24_Ts

(redundancy option).

Ribbon Communications Inc. Proprietary 7-14

 Apollo Reference Manual OPT9624 common cards

Functions
The FM1000 provides the following main functions:
 Total capacity of 1 Tbps
 20 slots for I/O cards with 50 Gbps per slot
 Unified fabric for OTN and data applications
 FM1000 protection in 3:1 protection scheme with three active and one standby card
 1 Tbps traffic evenly divided between the three active FM1000 cards
 Each line card configured to work towards the fabric in either OTN or data mode
 Each ODUk container carrying its own timing

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 7-15

 Apollo Reference Manual OPT9624 common cards

Ports
Front panel indicator functions

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the FM1000.

Ribbon Communications Inc. Proprietary 7-16

8 OPT9608 common cards
The OPT9608 platform includes cards and modules that provide its common functionality, such as
power supply, air cooling, and control required for operation. These units are described in the following
sections.

8.1 RCP08_O
Supported platform
 OPT9608

Description
The RCP08_O is an RCP card optimized for pure optical applications. The card is the central control
component in the OPT9608 system architecture, providing the main system processor responsible for
essential system management. Two RCP modules may be installed in the platform for redundancy.
Two RCP08_O modules may be installed in an OPT9608 platform for redundancy.
The Apollo product line relies on a highly scalable, internet-class routing engine designed specifically to
interoperate seamlessly with current IP backbones. As the main platform controller, the RCP runs the
system software and a full suite of routing protocols, including BGP, OSPF-TE, IS-IS-TE, and RIPv2, as
well as MPLS signaling (RSVP-TE, LDP), MPLS-TP, and multicast (PIM-SM, MBGP, IGMPv2).
The Apollo product line has an efficient modular design that is expressed in every aspect of the system.
This design works well with all the different line cards, offering the same top quality features and
benefits across all types of interfaces. Technology reuse also means a shorter time to market for later
follow on cards.

Functions
The RCP08_O supports the following management and alarm interfaces and functions:
 Main system processor, responsible for essential system management.
 Serial RS232 interface for local CLI connection.
 Terminal Ethernet management interface port supporting 100 Mbps.
 Two management Ethernet ports for connections to subtending platforms used in multiplatform
configurations (future function).
 Operation and alarm LEDs.
The RCP08_O provides the following main functions:
 Routing and control:
 Management communication
 CPU offload
 8 Gb SD card memory (NVM)
 Stores the platform's software code and configuration data base (on the NVM)
 Ethernet intra-platform networking
 Multi-platform infrastructure (future)
 EMS and LCT management support

Ribbon Communications Inc. Proprietary 8-1

 Apollo Reference Manual OPT9608 common cards

 Announces the active RCP to all Field Replaceable Units (FRUs)

 Self BIT
 Single or redundant RCP
 HA (High Availability)

Card views
General view

Front panel

LEDs
Marking Item Functions
ACT Green LED Lights together with the STBY and FAIL LEDs during software
download. Lights steadily when the RCP is configured as the
active card. Off when the RCP has a failure or is configured as
the standby card.
STBY Yellow LED Lights together with the ACT and FAIL LEDs during software
download. Lights steadily when the RCP is configured as the
stand-by card. Off when the RCP is the active card.
FAIL Red LED Lights together with the ACT and STBY LEDs during software
download. Lights steadily when a fault is detected in the card.
Off when there is no fault in the RCP.
CRT. Red LED Lights when the highest severity unacknowledged alarm in the
platform is critical.

Ribbon Communications Inc. Proprietary 8-2

 Apollo Reference Manual OPT9608 common cards

Marking Item Functions

MAJ. Orange LED Lights when the highest severity unacknowledged alarm in the
platform is major.
MIN. Yellow LED Lights when the highest severity unacknowledged alarm in the
platform is minor.

Ports and pushbuttons

Marking Connector Functions
CONSOLE RJ-45 connector Serial RS-232 communication port for use by technical support
personnel (debug, maintenance, etc.).
LOCAL MNG. RJ-45 connector Terminal management interface for connecting to an LCT.
EXP1 RJ-45 connector For future use
EXP2 RJ-45 connector
ACO Pushbutton Used to temporarily disable the buzzer and set off the
corresponding alarm LED when an alarm condition is present.
The buzzer is activated again when a new alarm condition is
detected.
LED-TEST Pushbutton Turns on all LEDs located on cards/modules installed in the
platform, for test purposes.

8.2 RCP1_4AD_T
Supported platform
 OPT9608

Description
The RCP1_4AD_T card is the central control component in the OPT9608 system architecture, providing
the main system processor responsible for essential system management and timing control. Two
RCP1_4AD_T modules may be installed in an OPT9608 platform for redundancy.
The Apollo product line relies on a highly scalable, internet-class routing engine designed specifically to
interoperate seamlessly with current IP backbones. As the main platform controller, the RCP runs the
system software and a full suite of routing protocols, including BGP, OSPF-TE, IS-IS-TE, and RIPv2, as
well as MPLS signaling (RSVP-TE, LDP), MPLS-TP, and multicast (PIM-SM, MBGP, IGMPv2).
The Apollo product line has an efficient modular design that is expressed in every aspect of the system.
This design works well with all the different line cards, offering the same top quality features and
benefits across all types of interfaces. Technology reuse also means a shorter time to market for later
follow on cards.
The RCP1_4AD_T supports the following management and alarm interfaces and functions:
 Main system processor, responsible for essential system management.
 Serial RS232 interface for local CLI connection.
 Terminal Ethernet management interface port supporting 100 Mbps.

Ribbon Communications Inc. Proprietary 8-3

 Apollo Reference Manual OPT9608 common cards

 Two management Ethernet ports for connections to subtending platforms used in multiplatform
configurations (future function).
 Operation and alarm LEDs.
 Active CTM.

Functions
 Routing and control:
 Management communication
 CPU offload
 8 Gb CF (Compact Flash) card memory (NVM)
 Stores the platform's software code and configuration data base (on the NVM)
 Ethernet intra-platform networking
 Multi-platform infrastructure (future)
 EMS and LCT management support
 Timing to all I/O cards
 Announces the active RCP to all Field Replaceable Units (FRUs)
 Self BIT
 Single or redundant RCP
 HA (High Availability):
 Active fabric distribution done immediately
 Hardware detection of major fabric card faults and switchover

NOTE: The RCP1_4AD_T is supported only in the OPT9608 platforms.

Card views
General view

Ribbon Communications Inc. Proprietary 8-4

 Apollo Reference Manual OPT9608 common cards

Front panel

LEDs

Marking Item Functions

ACT Green LED Lights together with the STBY and FAIL LEDs during software
download. Lights steadily when the RCP is configured as the
active card. Off when the RCP has a failure or is configured as
the standby card.
STBY Yellow LED Lights together with the ACT and FAIL LEDs during software
download. Lights steadily when the RCP is configured as the
stand-by card. Off when the RCP is the active card.
FAIL Red LED Lights together with the ACT and STBY LEDs during software
download. Lights steadily when a fault is detected in the card.
Off when there is no fault in the RCP.
CRT. Red LED Lights when the highest severity unacknowledged alarm in the
platform is critical.
MAJ. Orange LED Lights when the highest severity unacknowledged alarm in the
platform is major.
MIN. Yellow LED Lights when the highest severity unacknowledged alarm in the
platform is minor.

Ports and pushbuttons

Marking Connector Functions

CONSOLE RJ-45 connector Serial RS-232 communication port for use by technical support
personnel (debug, maintenance, etc.).
LOCAL MNG. RJ-45 connector Terminal management interface for connecting to an LCT.
EXP1 RJ-45 connector For future use
EXP2 RJ-45 connector
ACO Pushbutton Used to temporarily disable the buzzer and set off the
corresponding alarm LED when an alarm condition is present.
The buzzer is activated again when a new alarm condition is
detected.
LED-TEST Pushbutton Turns on all LEDs located on cards/modules installed in the
platform, for test purposes.

Ribbon Communications Inc. Proprietary 8-5

 Apollo Reference Manual OPT9608 common cards

8.3 PFM08_AC
Supported platform
 OPT9608

Description
The PFM08_AC is an AC to DC power converter that supplies 48 VDC to the OPT9608 platform. The
unit occupies one PFM slot in the OPT9608. While a single card can provide the total power required by
the OPT9608, AC power redundancy is supported by installing two PFM08_AC cards in the platform.
To support the full redundancy, each PFM08_AC must be fed from a different AC source. You can also
install a mixture of one PFM08_AC module and one PFM module (DC, with or without circuit breaker).
The AC input voltage plug on this card has a special front cover that protects it against unintended
disconnection. After inserting the AC plug, the cover is lifted on the plug and the captive screw is
fastened, to protect the AC plug from removal.

CAUTION: To protect the PFM08_AC against lightning (up to 4 Kv) Line to protected
Ground, the customer must add the following components on the AC power source feeding
the card:
 Surge protection varistors between Line to Neutral
 Surge arrestors between Line to Ground

WARNING: Before connecting the PFM08_AC to power, make sure that the 230 VAC
source is protected by an 8A circuit breaker, or if you are using 110 VAC source, by a 16A
circuit breaker.

Functions
The PFM08_AC provides the following main functions:
 Wide AC input voltage range from 110 VAC to 230 VAC (50/60 Hz)
 Output voltage ranging from 52 VDC to 55 VDC, with up to 650 W of power
 Input and output voltage filters
 Hot swappable card
 Control and alarms
 Temperature sensing
 Redundancy
 DC output voltage indication
 Fail indication

Ribbon Communications Inc. Proprietary 8-6

 Apollo Reference Manual OPT9608 common cards

Card views
General view

Front panel

LEDs

Marking Item Functions

ACT Green LED  On  48 VDC output is OK
 Off  48 VDC output is Out of Range
FAIL Red LED  On  3.3 VDC power supply and 3.3 VDC backplane are under 3 VDC or high
temperature on the card
 Off  3.3 VDC and card temperature are OK

Connectors

Marking Connector Functions

POWER IN C14, 3-pin connector Connects AC power to the unit.

Ribbon Communications Inc. Proprietary 8-7

 Apollo Reference Manual OPT9608 common cards

8.4 PFM with a circuit breaker (DC)

Supported platform
 OPT9608

Description
The PFM serves as an input power filter for the DC voltage connected to the OPT9608, and provides
the alarm interfaces for the platform. Each platform has two PFM units for redundancy purposes. To
support full redundancy, each PFM should be fed from a different power source, if available. When only
one power source is available, it should be connected to both units. The PFM can then be replaced
without affecting traffic. The standard PFM module for the OPT9608 platform is available either with or
without a circuit breaker. A mix of both types is allowed in the same platform. You can also install a
mixture of one PFM08_AC module and one PFM module (DC, with or without circuit breaker).

Functions
 Input DC voltage filtering (range from -40.8 VDC to -57.6 VDC)
 Control and alarms
 Temperature sensing
 Input voltage monitoring
 Circuit breaker on the module's front panel used as an ON/OFF switch for the platform and over-
current protection for the DC power source
 Hold-up capacitors
 Power Good indication
 Fail indication
 Simple protection mechanism that prevents module extraction while connected to a power source

Card views
General view with circuit breaker

Ribbon Communications Inc. Proprietary 8-8

 Apollo Reference Manual OPT9608 common cards

PFM (with circuit breaker) front panel

LEDs

Marking Item Functions

ACTIVE Green LED Lights steadily when the PFM receives input power and operates
normally.
FAIL Red LED Normally off. Lights steadily when a fault is detected in the unit.

Connectors

Marking Connector Functions

- 2W2 D-type connector Connects the DC power source to the module.
- Protection lever Activated by the power cable when plugged into the
corresponding connector on the front panel. As a result,
the lever slides a locking pin into the chassis and
prevents extraction of the module.
- Circuit breaker 40 A Used as an ON/OFF power switch for the platform and
over-current protection for the DC power source.

Ribbon Communications Inc. Proprietary 8-9

 Apollo Reference Manual OPT9608 common cards

8.5 PFM without a circuit breaker

Supported platform
 OPT9608

Description
The PFM serves as an input power filter for the DC voltage connected to the OPT9608, and provides
the alarm interfaces for the platform. Each platform has two PFM units for redundancy purposes. To
support full redundancy, each PFM should be fed from a different power source, if available. When only
one power source is available, it should be connected to both units. The PFM can then be replaced
without affecting traffic. The standard PFM module for the OPT9608 platform is available either with or
without a circuit breaker. A mix of both types is allowed in the same platform. You can also install a
mixture of one PFM08_AC module and one PFM module (DC, with or without circuit breaker).

Functions
The PFM performs the following functions:
 Input DC voltage filtering (range from -40.8 VDC to -57.6 VDC)
 Control and alarms
 Temperature sensing
 Input voltage monitoring
 Hold-up capacitors
 Power Good indication
 Fail indication
 Simple protection mechanism that prevents module extraction while connected to a power source

Card views
General view without circuit breaker

Ribbon Communications Inc. Proprietary 8-10

 Apollo Reference Manual OPT9608 common cards

Front panel

LEDs

Marking Item Functions

ACTIVE Green LED Lights steadily when the PFM receives input power and operates
normally.
FAIL Red LED Normally off. Lights steadily when a fault is detected in the unit.

Connectors

Marking Connector Functions

- 2W2 D-type connector Connects the DC power source to the module.
- Protection lever Activated by the power cable when plugged into the
corresponding connector on the front panel. As a result,
the lever slides a locking pin into the chassis and
prevents extraction of the module.

8.6 PFM08H_DC
Supported platform
 OPT9608

Description
The PFM08H_DC serves as a high-power input power filter for the DC voltage connected to the
OPT9608, and provides the alarm interfaces for the platform. When using the PFM08H_DC module, the
platform is configured as an OPT9608H (higher-power) platform, supporting the use of more high-
power components, such as the higher-capacity I/O modules.
Each platform has two PFM08H_DC units for redundancy purposes. To support full redundancy, each
PFM should be fed from a different power source, if available. When only one power source is
available, it should be connected to both units. The PFM08H_DC can then be replaced without affecting
traffic. The PFM08H_DC supplies up to 1800W of power, a higher amount than the standard PFM
module, and therefore cannot be installed in combination with a different type of PFM module. When
working with the PFM08H_DC, the platform must be configured with the corresponding high-powered
FCM08H fan.

Ribbon Communications Inc. Proprietary 8-11

 Apollo Reference Manual OPT9608 common cards

Functions
The PFM performs the following functions:
 Input DC voltage filtering (range from -40.8 VDC to -57.6 VDC)
 Control and alarms
 Temperature sensing
 Input voltage monitoring
 Hold-up capacitors
 Power Good indication
 Fail indication
 Simple protection mechanism that prevents module extraction while connected to a power source

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 8-12

 Apollo Reference Manual OPT9608 common cards

LEDs
Marking Item Functions
ACTIVE Green LED Lights steadily when the PFM receives input power and operates
normally.
FAIL Red LED Normally off. Lights steadily when a fault is detected in the unit.

Connectors
Marking Connector Functions
- 5W5 D-type connector Connects the DC power source to the module.
- Protection lever Activated by the power cable when plugged into the
corresponding connector on the front panel. As a result,
the lever slides a locking pin into the chassis and
prevents extraction of the module.

8.7 FCM air filters

Supported platform
 OPT9608

Description
OPT9608 platforms operating in extremely dusty and/or humid environments must be equipped with an
air filter in the dedicated slot on the right side of the FCM/FCM08_S.
The purpose of the air filter is to reduce the accumulation of dust and dirt carried by the cooling air
flowing through the platform on its internal components. The combination of dust and humidity produces
a capacitive/conductive layer between components installed on cards and modules. This may degrade
equipment performance or even cause malfunctions. Moreover, the insulating effect of a dust layer
causes components to operate at higher temperatures, so ultimately decreasing equipment reliability.
An air filter reduces dirt accumulation and thus prevents degradation of equipment reliability and
performance. However, filters do increase the resistance to airflow and should therefore carefully be
selected according to the actual operating conditions.
Apollo offers two types of air filters:
 Low density foam filter, with a density of 10 PPI.
 High density foam filter (45 PPI) in compliance with NEBS standards. This is the default type
supplied with the OPT9608.

NOTE: The low density filter (10 PPI) must be ordered separately.

Ribbon Communications Inc. Proprietary 8-13

 Apollo Reference Manual OPT9608 common cards

Installing the air filter in the OPT9608

In extremely dusty sites or when NEBS compliance is required, the 45 PPI filter is required. For all other
sites, the 10 PPI filter is sufficient.

NOTE: The insertion of the air filter into the FCM activates a switch that reports its
presence to the system management. If an air filter is not installed, a "filter missing" alarm
is generated and reported.

Filter maintenance intervals must strictly be observed. These are application-specific and depend on
the environmental conditions. Loaded filters are handled by cleaning or replacing. It is accepted for
electronic equipment design to recommend cleaning/replacing air filters every three months. The high
density air filter (45 PPI) may become blocked in a shorter time and must be maintained more
frequently.

Ribbon Communications Inc. Proprietary 8-14

 Apollo Reference Manual OPT9608 common cards

8.7.1 FCM
Supported platform
 OPT9608

Description
The FCM is positioned at the right side of the OPT9608 platform and provides cooling air to the system
from nine separate fans. Air is drawn in by the fans from the right side of the chassis and pumped out
through the horizontally mounted cards and modules through the left side of the chassis.
The FCM includes a controller that controls the operation of the fans. If one of the fans fails, the
remaining ones operate in turbo mode and the fail LED lights until the FCM is replaced. If the operation
does not take more than four minutes, the FCM can be extracted and replaced without interrupting the
router operation (hot swapping). Apollo recommends preparing the replacement module in advance and
so shortening replacement time to a minimum.

WARNINGS:
 Don't leave the OPT9608 platform operating without an FCM.
 If you must replace an FCM, don't leave the system without an FCM unit for more than
4 minutes.

Functions
The main functions of the FCM include:
 Cooling air for the OPT9608 platform
 Controlling the operation of the nine fans according to the ambient temperature and sensors on
the OPT9608 platform
 Multiple speed levels are defined for the fans; see System Specifications for details
 Supporting hot swapping
 Collecting system alarms via the internal ACM:
 Four alarm inputs
 Four alarm outputs (dry contacts)
 Alarm severity : Critical, Major, Minor
 Alarm buzzer
 Accommodating the air filter for the fans
 Supplying -48 VDC power for the fans
 Out-of-band management (IMG)

Ribbon Communications Inc. Proprietary 8-15

 Apollo Reference Manual OPT9608 common cards

Card views
General view

Front panels: FCM

Ribbon Communications Inc. Proprietary 8-16

 Apollo Reference Manual OPT9608 common cards

Ports and LEDs

Marking Item Functions

EXP RJ-45 connector For future use.
IN-BAND MNG. RJ-45 connector Used to connect the management station.
ACT. Green LED Lights steadily when the card is powered and operating normally.
FAIL Red LED Normally off. Lights steadily when a fault is detected.
ALARMS 36-pin SCSI Connects alarm input and output lines via a RAP or directly to the
connector client.
AIR FILTER Housing Accommodates the air filter.

8.7.2 FCM08_S
Supported platform
 OPT9608

Description
The FCM08_S is positioned at the right side of the OPT9608 platform and provides cooling air to the
system from nine separate fans. Air is drawn in by the fans from the right side of the chassis and
pumped out through the horizontally mounted cards and modules through the left side of the chassis.
The FCM08_S includes an integral built-in Layer 2 switch with four ports: one port is for connecting the
OPT9608 to management (IMG port), and three multi-shelf ports to connect to additional Apollo system
management ports at same site.
The FCM08_S includes a controller that controls the operation of the fans. If one of the fans fails, the
remaining ones operate in turbo mode and the fail LED lights until the FCM08_S is replaced. If the
operation does not take more than four minutes, the FCM08_S can be extracted and replaced without
interrupting the router operation (hot swapping). Apollo recommends preparing the replacement module
in advance and so shortening replacement time to a minimum.

WARNINGS:
 Don't leave the OPT9608 platform operating without an FCM08_S.
 If you must replace an FCM, don't leave the system without an FCM08_S unit for more
than 4 minutes.

Ribbon Communications Inc. Proprietary 8-17

 Apollo Reference Manual OPT9608 common cards

Functions
The main functions of the FCM include:
 Cooling air for the OPT9608 platform
 Controlling the operation of the nine fans according to the ambient temperature and sensors on
the OPT9608 platform
 Multiple speed levels are defined for the fans; see System Specifications for details
 Supporting hot swapping
 Collecting system alarms via the internal ACM:
 Four alarm inputs
 Four alarm outputs (dry contacts)
 Alarm severity : Critical, Major, Minor
 Alarm buzzer
 Accommodating the air filter for the fans
 Supplying -48 VDC power for the fans
 Layer 2 switch with four ports:
 1 port for connecting the system to management (IMG)
 3 ports for connecting to other Apollo systems (multi-shelf MNG)

Usage guidelines
The FCM08_S includes an integral built-in Layer 2 switch with three multi-shelf ports to connect to
additional Apollo system management ports at same site. You can define a cluster configuration with up
to three network elements (Slaves NE1, NE2, NE3) connected to an OPT9608 (Master NE0) through
the MNG ports on the FCU08_S fan unit. A typical example of this topology, illustrated in the following
figure, is explained here.

Ribbon Communications Inc. Proprietary 8-18

 Apollo Reference Manual OPT9608 common cards

In this sample topology, the Master NE0 communicates with the management system using GCC
(through NE4). NE4 may be connected to the management through the IMG port, or using GCC as well.
(Other topology options are not described here.)

The following guidelines apply:

1. IMG/DCN IP of NE4 and NE0-3 should be assigned to different sub-networks.
2. Configure routing between all NEs using one of the following two methods:
 OSPF is active on the Master NE0 fe-rcp.0 interface (with FCU08_S) and on the Slave
NEs. No static routes are required on the Master and Slaves. Routing is defined by OSPF.
 Static routes are configured in a mesh arrangement, between Slaves and Master, between
Slaves themselves, and from Slaves to NE4. Additionally, Master should export its static
routes. For this export, the following CLI commands are used:
set policy-options policy-statement export-static term 1 from protocol
static
set policy-options policy-statement export-static term 1 then accept
set routing-instances DCN-routing-instance protocols ospf export export-
static
commit

Ribbon Communications Inc. Proprietary 8-19

 Apollo Reference Manual OPT9608 common cards

Card views
General view

Ribbon Communications Inc. Proprietary 8-20

 Apollo Reference Manual OPT9608 common cards

Front panel

Ribbon Communications Inc. Proprietary 8-21

Apollo Reference Manual OPT9608 common cards

Ports and LEDs

Marking Item Functions

IMG RJ-45 connectors Used to connect the management station. Status options include:
(IN-BAND MNG)  No cable
Multi Shelf MNG Green and Yellow LED both off
 Cable inserted and port disabled (configuration SW setting)
Green and Yellow LED both off
 10/100Mbps and traffic active
Green LED off, Yellow LED blinking
 10/100Mbps and no traffic
Green LED off, Yellow LED steady on
 1Gbps and traffic active
Green LED blinking, Yellow LED off
 1Gbps and no traffic
Green LED steady on, Yellow LED off
ACT. Green LED Lights steadily when the card is powered and operating normally.
FAIL Red LED Normally off. Lights steadily when a fault is detected.
ALARMS 36-pin SCSI Connects alarm input and output lines via a RAP or directly to the
connector client.
AIR FILTER Housing Accommodates the air filter.

Ribbon Communications Inc. Proprietary 8-22

9 OPT9603 common cards
The OPT9603 platform includes cards and modules that provide its common functionality, such as
routing and control, and management connections, power supply, air cooling, and control required for
operation. These units are described in the following sections.

9.1 RCP03/RCP03R
Supported platform
 OPT9603

Description
The RCP03/RCP03R card is the central control component in the OPT9603 system architecture,
providing the main system processor responsible for essential system management and control. The
card has no redundancy, as only one RCP03/RCP03R can be installed in the OPT9603 platform.

NOTE: The RCP03 card has been designated as end of life, and has been replaced by
the RCP03R. The same feature description applies to both cards. The RCP03R is fully
interoperable with the RCP03; there are no restriction on use of the RCP03R.

Functions
The RCP03/RCP03R provides the following main functions:
 Control processor for the system
 Controls all cards and modules in the platform using Ethernet and I2C busses
 Supports Ethernet/IP connectivity between the RCP and all optical cards (OPBs) for GCC, OSC,
and internal communication
 Stores the platform's software code and configuration data base on an NVM (SD type, 8 Gb)
 Performance monitoring logging
 Alarm interfaces and indications, including:
 Alarm severity outputs (Critical, Major, Minor)
 External alarm outputs and inputs to client or RAP
 LEDs for displaying the operation and alarms of the system
 Activations, including:
 LED tests for the entire platform
 ACO
 Management and debug interfaces via GbE and RS-232 ports

Ribbon Communications Inc. Proprietary 9-1

 Apollo Reference Manual OPT9603 common cards

Card views
General view

Front panel

Ports and LEDs

Marking Item Functions
ACT Green LED Indicates that the RCP03/RCP03R card is powered and operating normally.
FAIL Red LED Lights steadily when a fault is detected in the card.
ALARMS 36-pin SCSI Connects alarm input and output lines via a RAP or directly to the client.
connector
CR Red LED Lights when a critical alarm is detected in the platform. Remains lit while any
such alarm is active. Turns off upon termination of all alarms of this degree.
MAJ Orange LED Lights when a major alarm is detected in the platform. Remains lit while any
such alarm is active. Turns off upon termination of all alarms of this degree.
MIN Yellow LED Lights when a minor (or warning) alarm is detected in the platform. Remains lit
while any such alarm is active. Turns off upon termination of all alarms of this
degree.
ACO Pushbutton Used to temporarily disable the buzzer and set off the corresponding alarm
LED when an alarm condition is present. The buzzer is activated again when a
new alarm condition is detected.
LED-TEST Pushbutton Turns on all LEDs located on cards/modules installed in the platform, for test
purposes.
IMG RJ-45 Out-of-band management Ethernet interface (10/100/1000BaseT) for
connector connecting to an element management station (STMS) or a CLI terminal.
LCT RJ-45 Terminal management interface for connecting to an LCT.
connector
CONSOLE RJ-45 Serial RS-232 communication port for use by technical support personnel
connector (debug, maintenance, etc.).

Ribbon Communications Inc. Proprietary 9-2

 Apollo Reference Manual OPT9603 common cards

9.2 PFM03
Supported platform
 OPT9603

Description
The PFM03 serves as an input power filter for the DC voltage connected to the OPT9603. Each
platform has two PFM03 units for DC redundancy purposes. It is recommended to connect each to a
different power source (unless only one power source is available). When only one power source is
available, it is recommended to connect it to both units. The PFM03 can then be replaced without
affecting traffic, provided that the second PFM03 is installed and connected to power.

NOTES:
 The PFM03 and PFM03_RAC may be installed side by side in the same platform, providing
another redundancy option.
 The OPT9603 can also be equipped with a PFM03_AC card. In this case the PFP03_AC
occupies both PFM slots and power redundancy is not supported.

Functions
The PFM03 performs the following functions:
 Input DC voltage filtering (-48 V)
 Control and alarms
 Input voltage monitoring
 Hold-up capacitors
 Power Good indication
 Fail indication

Card views
Front panel

Ports and LEDs

Marking Item Functions

POWER ON Green LED Lights steadily when the PFM03 receives input power and operates
normally.
FAIL Red LED Normally off. Lights steadily when a fault is detected in the unit.
POWER IN 2-pin connector Connects the DC power source to the module.

Ribbon Communications Inc. Proprietary 9-3

 Apollo Reference Manual OPT9603 common cards

9.3 PFM03_H
Supported platform
 OPT9603

Description
The PFM03_H serves as a high-power input power filter for the DC voltage connected to the OPT9603,
and provides the alarm interfaces for the platform. When using the PFM03_H module, the platform is
referred to as an OPT9603H (higher-power) platform, supporting the use of more high-power
components, such as the higher-capacity I/O modules.
Each platform has two PFM03_H units for DC redundancy purposes. To support full redundancy, each
PFM should be fed from a different power source, if available. When only one power source is
available, it should be connected to both units. The PFM03_H can then be replaced without affecting
traffic, provided that the second PFM03_H is installed and connected to power.
The PFM03_H supplies up to 480W of power, a higher amount than the standard PFM module, and
therefore cannot be installed in combination with a different type of PFM module.

Functions
The PFM03_H performs the following functions:
 Input DC voltage filtering (-48 V)
 Control and alarms
 Temperature sensing
 Input voltage monitoring
 Hold-up capacitors
 Power Good indication
 Fail indication
 Simple protection mechanism that prevents module extraction while connected to a power source

Card views
Front panel

Ribbon Communications Inc. Proprietary 9-4

 Apollo Reference Manual OPT9603 common cards

Ports and LEDs

Marking Item Functions

POWER ON Green LED Lights steadily when the PFM03_H receives input power and operates
normally.
FAIL Red LED Normally off. Lights steadily when a fault is detected in the unit.
POWER IN 2-pin connector Connects the DC power source to the module.

9.4 PFM03_AC
Supported platform
 OPT9603

Description
The PFM03_AC is an AC to DC power converter that supplies power to the OPT9603 platform. The unit
occupies the two PFM slots in the OPT9603 and power redundancy is not supported in this option. A
divider bracket, located between the two PFM slots, must be removed to enable the installation of the
PFM03_AC in the OPT9603. The procedure for performing it is described in the OPT9603 Installation
and Maintenance Manual.

Functions
The PFM03_AC provides the following main functions:
 Wide AC input voltage range from 110 VAC to 230 VAC
 Output voltage of 48 VDC with up to 320 W of power
 Input and output voltage filters
 Control and alarms
 DC output voltage indication
 Fail indication

Ribbon Communications Inc. Proprietary 9-5

 Apollo Reference Manual OPT9603 common cards

Card views
General view

Front panel

Ports and LEDs

Marking Item Functions

ACTIVE Green LED Lights steadily when the PFM03_AC provides DC output voltage.
FAIL Red LED Normally off. Lights steadily when a fault is detected in the unit.
AC POWER IN 3-pin connector Connects AC power to the unit.

Ribbon Communications Inc. Proprietary 9-6

 Apollo Reference Manual OPT9603 common cards

9.5 PFM03_RAC
Supported platform
 OPT9603

Description
The PFM03_RAC is an AC to DC power converter that supplies 48 VDC to the OPT9603 platform. The
unit occupies one PFM slot in the OPT9603. AC power redundancy is supported by installing two
PFM03_RAC cards in the platform. To support the redundancy each PFM03_RAC must be fed from a
different AC source. A single card can provide the total power required by the OPT9603.

NOTES: The PFM03 and PFM03_RAC may be installed side by side in the same
platform, providing another redundancy option.

WARNING: Before connecting the PFM03_RAC to power, make sure that the AC source
is protected by a 6A circuit breaker.

Functions
The PFM03_RAC provides the following main functions:
 Wide AC input voltage range from 110 VAC to 230 VAC (50/60 Hz)
 Output voltage of 48 VDC with up to 320 W of power
 Input and output voltage filters
 Hot swappable card
 Control and alarms
 DC output voltage indication
 Fail indication

Ribbon Communications Inc. Proprietary 9-7

 Apollo Reference Manual OPT9603 common cards

Card views
General view

Front panel

Ports and LEDs

Marking Item Functions

POWER ON Green LED Lights steadily when the PFM03_RAC provides DC output voltage.
FAIL Red LED Normally off. Lights steadily when a fault is detected in the unit.
POWER IN 3-pin connector Connects AC power to the unit.

9.6 FCM03
Supported platform
 OPT9603

Description
The FCM03 is positioned at the right side of the OPT9603 platform and provides cooling air to the
system from two separate fans. Air is drawn in by the fans from the right side of the chassis and
pumped out through the horizontally mounted cards and modules through the left side of the chassis.

Ribbon Communications Inc. Proprietary 9-8

 Apollo Reference Manual OPT9603 common cards

The FCM03 includes a controller that controls the operation of the fans. If one of the fans fails, the
second one operates in turbo mode and the fail LED lights until the FCM03 is replaced. If the operation
does not take more than four minutes, the FCM03 can be extracted and replaced without interrupting
the platform operation (hot swapping). Apollo recommends preparing the replacement module in
advance and so shortening replacement time to a minimum.

WARNINGS:
 Don't leave the OPT9603 platform operating without an FCM03.
 If you must replace an FCM03, don't leave the system without an FCM03 unit for more
than 4 minutes

Functions
The main functions of the FCM03 include:
 Cooling air for the OPT9603 platform
 Controlling the operation of the two fans according to the ambient temperature and sensors on the
OPT9603 platform
 Multiple speed levels are defined for the fans; see System Specifications for details
 Supporting hot swapping
 Dual power supply -48 VDC support redundancy
 Accommodating the air filter for the fans
 Parallel dual inrush current circuit
 Psophometric filter

Card views
General view

Ribbon Communications Inc. Proprietary 9-9

 Apollo Reference Manual OPT9603 common cards

Front panel

Ports and LEDs

Marking Item Functions

ACTIVE Green Lights steadily when the card is powered and operating normally.
LED
FAIL Red LED Normally off. Lights steadily when a fault is detected.

9.6.1 FCM03 air filter

Supported platform
 OPT9603

Description
OPT9603 platforms operating in extremely dusty and/or humid environments must be equipped with an
air filter in the dedicated slot on the right side of the FCU.
The purpose of the air filter is to reduce the accumulation of dust and dirt carried by the cooling air
flowing through the platform on its internal components. The combination of dust and humidity produces
a capacitive/conductive layer between components installed on cards and modules. This may degrade
equipment performance or even cause malfunctions. Moreover, the insulating effect of a dust layer
causes components to operate at higher temperatures, so ultimately decreasing equipment reliability.
An air filter reduces dirt accumulation and thus prevents degradation of equipment reliability and
performance. However, filters do increase the resistance to airflow and should therefore carefully be
selected according to the actual operating conditions.
The vendor offers a medium density foam filter, with a density of 25 PPI for the FCM03.

Ribbon Communications Inc. Proprietary 9-10

 Apollo Reference Manual OPT9603 common cards

Installing an air filter in the FCM03

Filter maintenance intervals must strictly be observed. These are application-specific and depend on
the environmental conditions. Loaded filters are handled by cleaning or replacing. It is accepted for
electronic equipment design to recommend cleaning/replacing air filters every three months.

Ribbon Communications Inc. Proprietary 9-11

10 OPT96xx optical cards and modules
Apollo platforms support a wide range of passive optical cards, including C/DWDM Mux/DeMuxes,
OADMs, splitters/couplers, filters, and Dispersion Compensating Fibers (DCFs). These platforms can
be deployed together with Artemis passive optical platforms (that also include a wide range of similar
optical cards), offering a low cost, high modularity, and very high density solution. This leaves the
photonic slots in the Apollo platforms available for active cards, such as optical amplifiers, ROADMs,
service cards, and fabric.
In addition we offer a variety of optical amplifiers for the Apollo platforms based on different
technologies:
 Erbium-Doped Fiber Amplifier (EDFA) optical amplifiers, capable of amplifying the entire C band
and supporting multichannel applications. Both fixed gain and variable gain EDFA-based
amplifiers are available.
 Raman optical amplifiers for long-span applications. Raman amplifiers are used in conjunction
with EDFA-based amplifiers to achieve distributed amplification along the fiber, thus minimizing
Optical Signal to Noise Ratio (OSNR) degradation on the amplified link and avoiding nonlinear
effects.

10.1 Understanding I/O card slot sizes

The Apollo I/O cards have different sizes. In the following sections the size of each card is defined
according to the number of slots it occupies in Apollo platforms, for example:
 Single-slot cards
 Double-slot cards
 Double-wide-slot cards
 Quad-slot cards
The installation of single-slot and double-wide-slot cards is simple and does not require any
preparations. The installation of the other cards (with slot size other than these), requires removal of
mechanical brackets between the slots to form the slot size. The mechanical procedures required for
these operations are described in the corresponding OPT9624, OPT9608, and OPT9603 Installation
and Maintenance Manual.

Ribbon Communications Inc. Proprietary 10-1

 Apollo Reference Manual OPT96xx optical cards and modules

Slot size definitions

10.2 Understanding CD and CDC DWDM

architecture
Apollo's cutting-edge colorless, directionless, and contentionless ROADM architecture addresses
operator demands for greater flexibility and enhanced optical protection options.
 Directionless switching enables the ROADM to connect any signal from any direction (“degree”)
or drop port to any other degree without restriction.
 Colorless switching enables the ROADM to connect an add/drop port to any wavelength without
restriction.
 Contentionless switching means that two or more services can be transmitted from the site in
different directions using the same wavelength channel.
The colorless, directionless, and contentionless (CDC) ROADM network solutions commonly
implemented in the industry today are based on combinations of multicast switches (MCS) and EDFA
arrays. Several limitations are inherent to this approach:
 Insertion loss and EDFA array power scaling
 An EDFA array is required for MCS when working with more than 4-6 add/drop ports. The
MCS loss increases directly with the number of add/drop ports.
 EDFA arrays can leverage uncooled pumps when supporting up to about 16 add/drop ports.
For greater numbers of ports, higher complexity pumps are required.

Ribbon Communications Inc. Proprietary 10-2

 Apollo Reference Manual OPT96xx optical cards and modules

 Transmitter wideband noise accumulation

Transceivers emit wideband optical noise (Tx_OSNR specification). This wideband noise
accumulates in filterless MCS modules, degrading OSNR before any transmission. More MCS
add/drop ports means proportionately more accumulated noise and degraded OSNR. Using a
tunable filter array solves noise accumulation degradation, by effectively increasing Tx_OSNR.
But this approach increases cost, size, and insertion loss.
 Impact of unwanted channels on Rx
Network configurations include a large number of wavelengths at a single coherent receiver. As
port count (N) increases, the dynamic range of the receiver can become inadequate, resulting in
signal quality degradation. This issue is significantly worse for superchannel transceivers.
 Support for NG superchannel transceivers
The telecom industry is evolving to superchannel transceivers with multiplexed wavelength
subcarriers, such as 2 x 200Gbps for 400Gb/s, and even 4 x 250Gb/s for 1Tbps. A
superchannel has n times more power per CDC add/drop port, where n is the number of
superchannel carriers. Currently, EDFA array power is engineered for only a single channel per
port. Multiple channels per add/drop port requires n-times more output power in the EDFA array.
Therefore, supporting 2- and 4-carrier superchannels with >10 ports per MCS requires complex
EDFA arrays.
With all these limitations built into the MCS+EDFA array combination, this approach simply will not work
for NG CDC ROADM networks, which will require:
 Improved cost per add/drop port, allowing them to leverage higher port count modules.
 More add/drop ports per module, increasing from 16 to 24 and up to 32 ports per module with
better total node capacity scalability.
 Support for more degrees, increasing from 8 to 16 and even more.
 Channel filtering for improved performance and relaxed transceiver requirements, including
Tx_OSNR and receiver dynamic range.
 Support for superchannel transceivers, which emit multiplexed superchannels, such as 2 x
200Gbps.
Apollo's contentionless solution is not based on the current MCS + EDFA approach. Instead, we
'skip a generation', and use a NG contentionless MxN WSS configuration, which is a far superior
solution:
 Low loss eliminates the need for EDFA arrays, offering a lower cost total solution.
 WSS device cost and loss scales minimally with port count, enabling higher port count and lower
cost per port.
 Without EDFA arrays, there is no power dependency on port count, and we support superchannel
transceivers without specification of power per port.
 WSS passband filters wideband noise, providing high performance independent of port count
while relaxing requirements on Tx and Rx.
For example, in a typical configuration, the ROADM20CF and ROADM_8x24CDCF cards' degree ports
are linked to the degree ports of other ROADMs in the site. The OCHP client ports are linked directly to
transceivers while the OMS client ports are linked to transceivers through splitters and Mux cards. The
client ports can be configured for single or multiple wavelengths per port.

Ribbon Communications Inc. Proprietary 10-3

 Apollo Reference Manual OPT96xx optical cards and modules

20 degrees of any-to-any CD and CDC connectivity

The preceding figure depicts a typical 3-degree ROADM node that sends/receives traffic to/from East,
West, and North. Each line connecting between the ROADMs represents a physical jumper fiber
connection carrying a programmable, flexible spectrum allocation. The ROADM_20CF (CD) and
ROADM_8x24CDCF (CDC) ROADM units operate as add/drop collectors that concentrate the channels
from all directions (East, West, North) and enable extraction of the required ones.

10.3 Understanding optical network control

parameters
Network designers know what an ideal optical network should include. Modern dynamic mesh optical
networks require automatic power control (APC) based on changes in the network; optical amplifiers
should automatically set their gain to the desired value, and ROADMs should automatically equalize the
power of all channels passing through.
To enable proper gain setting and power equalization along the entire network, Apollo platforms utilize
a set of optical network control parameters (ONCPs) transmitted periodically. These values are
generated independently at any optical node and transmitted through the network, from one optical card
to the next and from one node to the next, following the actual optical transmission direction. Each
optical card updates the ONCP values before transmitting them onward to the adjacent card. The
optical gain values are changed accordingly, as needed.

Ribbon Communications Inc. Proprietary 10-4

 Apollo Reference Manual OPT96xx optical cards and modules

ONCP data include advanced channel and link parameters beyond power, such as OSNR, dispersion,
and other estimated parameters (a combination of measurements and calculations) that can be used to
dynamically monitor and control the network. Note that real time monitoring of channel parameters is
available at the optical trail (OMS and OCH) and port (OCH or OTS) levels.
The result is simplicity, easier network operation, and significant savings of time and money in terms of
real time fault management, since instead of sending a technician to a remote site with expensive
testing equipment, you have complete information and remote control.

ONCP monitored parameters

Optical data is collected from all active optical components, such as transceivers, amplifiers (photo
diode measurements), and ROADM optical channel monitors, as well as intra-node and inter-node
connectivity. Optical data communicated between sites includes fiber type, fiber loss, amplification
levels, number of channels (maximum and active), channel rate, OSNR, chromatic dispersion, distance,
attenuation, non-linear status, and more. As the measured optical parameters are propagated inside
each site and then transferred between the sites, a network and site topology map is created, reflecting
the information collected.
A proprietary algorithm run through the embedded software at the NE level analyzes the gathered
information and fine-tunes the network for equalization and optimization. ONCP functionality is
supported for alien wavelengths too; just create a UME alien transceiver and define the optical
parameters according to the object specifications.
ONCP calculations are used for:

Ribbon Communications Inc. Proprietary 10-5

 Apollo Reference Manual OPT96xx optical cards and modules

 Automatic gain and power control (APC) for automatic amplifiers and ROADM configuration.
With ONCP, automatic responses to changes in the network, such as fiber attenuation and
channel changes, optimize network efficiency 24/7. This constant automatic tuning is essential for
efficient management of dynamic colorless-directionless networks with WSON restoration, running
high bit rates such as 100 Gbps and 200 Gbps per carrier.
 Indicating optical impairments in real time, informing the NOC engineer of all link optical
values, including OSNR, power, dispersion, and non-linear values. ONCP's real time network
analysis gives network operator full remote control. Collecting the necessary optical information in
hand, such as OSNR and Non-Linear status, is always the first step in analyzing network
abnormalities. ONCP provides all this information with high accuracy, in real time - a key factor in
saving precious debugging time. For example, measuring 100 Gbps/200 Gbps OSNR, especially
in ROADM networks, would otherwise require complicated and expensive Optical Spectrum
Analyzers, as well as the time and overhead required for traveling to the relevant sites.
 Enhanced path finding for WSON. WSON configuration takes into consideration the optical
values of alternative restoration paths. WSON networks use ONCP data to calculate an optically
validated restoration path, crucial to ensure that restored services will actually be able to maintain
the highest SLA.
ONCPs are generated by the transceivers and transmitted along the network following the optical
transmission path. A port receives and transmits the ONCP from/to the ports to which it is physically
connected (either in the same node or in an adjacent node). Upon receiving the ONCP in an input port,
the card updates the ONCP according to predetermined rules, and transmits the updated ONCP to the
next card via an output port. The following figures illustrate ONCP propagation within a site and
between sites.

ONCP propagation inside a site

Ribbon Communications Inc. Proprietary 10-6

 Apollo Reference Manual OPT96xx optical cards and modules

Transmission of ONCPs along the network

ONCP enables the following network functionalities:

 Power/gain control in EDFA, ROADM, and FOADM cards.
 Real time diagnostics.
 Span/connection loss diagnostics.
 Performance diagnostics, including channel OSNR, dispersion, polarization mode dispersion
(PMD), and nonlinear phase.
 Performance verification for a preinstalled trail.

10.4 Multi-degree CDC ROADM cards

Operators’ increasing need for capacity and flexibility in DWDM networks is the driving force behind the
development and deployment of a comprehensive set of reconfigurable optical add-drop multiplexer
(ROADM) solutions. ROADMs permit E2E routing of optical wavelengths through multiple nodes
without a need for electronic conversion. They reduce CAPEX and OPEX while providing full
management of wavelength services. A key building block in today's network is the multi-degree
ROADM (MD-ROADM).
Apollo offers 2-degree and multi-degree ROADMs that provide native support for 96 channels with
50 GHz or flexible grid spacing. Native 50 GHz spacing means that there are no additional “Day 2”
expenses. The 96-channel ROADM provides better slot utilization, less energy consumption, simpler
installation, and enhanced channel-use flexibility for all 96 channels. Flexible grid spacing optimizes
optical spectrum usage to accommodate different transmission rates, particularly for super-channel
transmission rates above 100G (Flexible Grid DWDM Networks). The ROADM_20TF offers up to
20 degrees of connectivity with other nodes in the optical network, with complete software-controlled
flexibility to switch wavelengths between incoming and outgoing DWDM streams.

Ribbon Communications Inc. Proprietary 10-7

 Apollo Reference Manual OPT96xx optical cards and modules

Apollo ROADMs are based on Wavelength Selective Switches (WSS) using core technologies like
optical MEMS for fixed grid 50/100GHz MD-ROADMs, and LCOS for flexible grid MD-ROADMs. On the
add side, the ROADMs connect all wavelengths from input to output (line) ports. Operators can
remotely switch or add any wavelength from any input port to any output port at any time. In add
configurations, these ROADMs can connect access rings to the core ring, dropping wavelengths at
remote sites, including star or full mesh topologies. On the drop side, all wavelengths from the input
port are broadcast to all drop ports, optimized for broadcast video applications. The ROADM_20TF,
built around a state-of-the-art 1x20 WSS, employs a route and select architecture using back-to-back
WSS that minimizes insertion loss across the ROADM node. The ROADM8x24_CDCF is a 4-slot
collector ROADM for CDC networks that provides the solution needed for NG contentionless networks,
with support for superchannel transceivers.
MD-ROADM cards support:
 Broadcast function.
 Full n-degree operation for multiple rings, star, and full mesh topologies.
 Cost-effective solution for high channel count.
 Full built-in optical channel monitoring (OCM) for all output channels
 Superior solution for alien wavelengths fed to Apollo DWDM networks from third party equipment
that supports the ITU-T DWDM grid.
 Low insertion loss for through channels.
 Advance protection and restoration.
 Flexible spectrum at 12.5GHz resolution.
Apollo's cutting-edge colorless, directionless, and contentionless ROADM architecture (CD and CDC
DWDM architecture) with Tunable Filter Array (TFA) modules connected to the local port supplements
WSS ROADM technology to meet operator demands for greater flexibility and enhanced optical
protection options.
 Directionless switching enables the ROADM to connect any signal from any direction (“degree”)
or drop port to any other degree without restriction.
 Colorless switching enables the ROADM to connect an add/drop port to any wavelength without
restriction.
 Contentionless switching means that two or more services can be transmitted from the site in
different directions using the same wavelength channel.

Ribbon Communications Inc. Proprietary 10-8

 Apollo Reference Manual OPT96xx optical cards and modules

MD-ROADM with colorless/directionless/contentionless functionality

10.4.1 ROADM_20TF
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The ROADM_20TF is a 20 degree double-long-slot ROADM card. The ROADM_20TF supports the
following:
 Flex-Grid operation over the extended C-band
 96/48 fixed grid channels with 50/100 GHz spacing
 DROP and ADD components implemented by two WSS modules
 OCM (Optical Channel Monitor) including channel power monitoring
 Channels power equalization at the line output port.
 Fiber connectivity module, based on an 100 Mbps, 1528 nm SFP enabling verification and
inspection of the fiber-connectivity for the ROADM OTS Degree ports
 Optical loopback
 WSON operation

Ribbon Communications Inc. Proprietary 10-9

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-10

Apollo Reference Manual OPT96xx optical cards and modules

Ports
Port name Number Function
1-20 20 pairs Degree ports with LC connectors
The path-through (input) signal is connected to the IN connector in the
pair and the path-through (output) comes out through the OUT
connector in the pair. The marking OUT and IN near the connectors
identifies the function of each of the corresponding ports. Note: The
function ADD and DROP of each duplex connector in the upper row are
reversed in the lower row.
LINE 1 pair
Line port with LC connector
MON -20dB 1
Monitor port for connection of line monitoring equipment

Usage guidelines
 The ROADM_20TF can be used as a line ROADM in any network site.
 The ROADM's 20 degree ports can be assigned for either pass-through or add/drop traffic:
 Pass-through ports are configured as OTS ports by default.
 Add/drop ports are configured as OTS by default; however, they can also be configured as
OHCP ports.
 We recommend connecting the OHCP add/drop ports to a transceiver, which enables a
simple colorless direction-aware architecture.

LEDs

Marking Item Functions

Card LEDs
IS Green Lights when the card is IS (assigned and completed configurations). Off
LED when the card is not assigned.
SW-U Yellow Currently not in use.
LED
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the module.
Degree port LEDs
Red LED Each channel's indicator lights if insufficient power is detected at the
, DEGREE corresponding Degree (Add) input.
LOS (Ports 1 to 20) Note: he direction of the arrow near each LED points to the
corresponding port it is indicating. For example, the arrow near the left
LED under ports 1 and 2 points up, meaning the LED will indicate a
LOS condition at the input (Add) of port 1. The arrow near the left LED,
under these ports, points down and will indicate a LOS condition at the
input (Add) of port 2.
Red LED Lights steadily when a LOS condition is detected at the line input.
LOS (LINE)

Ribbon Communications Inc. Proprietary 10-11

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

External Tx-Rx optical loopback

ROADM optical loopback functionality enables fiber verification through loopback of any selected
channel entering the line input port. The optical loopback is provided only for the line port, and only for a
single channel at a time.
To enable loopback functionality, one of the Degree ports is physically connected to itself (by a short
jumper) and then configured as a "Tx-Rx-loop" using STMS. A channel entering the line input port is
looped back by configuring a bi-directional cross-connect between the line port and the Tx-Rx-loop port
at the specified wavelength.
To configure a Tx-Rx-loop port:
 Select a single Degree port to be configured as the Tx-Rx-loop port.
 Use STMS to:
 Delete all cross-connects on the selected Degree port.
 Delete all fiber-connectivity of the selected Degree port.
 Connect a fiber patch cord between the input and output connectors of the Degree port to be
tested.
 Use STMS to configure the port as a Tx-Rx-loop. The necessary fiber connectivity between the
port input and output is generated automatically.
See Run an optical loopback in the STMS User Guide.

Ribbon Communications Inc. Proprietary 10-12

 Apollo Reference Manual OPT96xx optical cards and modules

Simplified ROADM_20TF loopback block diagram

10.4.2 ROADM_20CF
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The ROADM_20CF is a double-long-slot field configurable collector card with 20 ports. The ports are
field configured to be either degree or client ports. The ROADM_20CF supports the following:
 Field configurable: 4,6, or 8 degree ports with 16, 14, or 12 client ports respectively
 Flex-Grid operation over the extended C-band
 96/48 fixed grid channels with 50/100 GHz spacing
 Fiber connectivity module, based on an 100 Mbps, 1528 nm SFP enabling verification and
inspection of the fiber-connectivity for the ROADM OTS Degree ports
 WSON operation
 Internal optical loopback of client port
 OCM (Optical Channel Monitor) including channel power monitoring
 DROP and ADD components implemented by two WSS modules
 Colorless directionless applications
 Optical power monitoring (via PDs) of degree input ports
 Reconfigurable Add/Drop of any desired channel from any degree port to/from any client port
 Indirect connection between ROADM site transceivers and the line ROADMs

Ribbon Communications Inc. Proprietary 10-13

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-14

 Apollo Reference Manual OPT96xx optical cards and modules

Ports
Each port has an input and an output connector. The function of each connector (input or output) varies
according to row and configuration. You must adhere to the port connectivity rules listed in the following
tables.

Port name Number Connector

1-4 4 pairs Degree ports with LC connectors
5-8 4 pairs
Configurable Degree or client ports with LC connectors

9-20 12 pairs Client only ports with LC connectors

Port Connectivity rules

Port Row Port Function Left side Right side

Upper
Degree B Output (Drop) A Input (Add)
Client B Input (Add) A Output (Drop)
Lower
Client A Output (Drop) B Input (Add)

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off when
the card is not assigned.
SW-U Yellow Currently not in use.
LED
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault in
the module.
Degree Port LEDs

(Ports 1 Red LED Each channel's indicator lights if insufficient power is detected at the
to 8) corresponding Degree (Add) input.

Note: The card includes 8 Degree port LEDs at the bottom of the panel.
These LEDS relate to the ports in the upper row configured as Degree
ports.

Ribbon Communications Inc. Proprietary 10-15

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

Internal Tx-Rx optical loopback

ROADM_20CF optical loopback functionality enables fiber verification through loopback of any selected
channel entering a client port. The loopback mechanism is implemented through an internal port in
which the transmit and receive are directly connected. Loopback is configured by directing the required
channel in a client port to the internal port and receiving it back again.
See Run an optical loopback in the STMS User Guide.

Usage guidelines
The main application of the ROADM_20CF is as a collector in Colorless-Directionless network nodes. A
simplified block diagram of this application is shown in the following figure.

Ribbon Communications Inc. Proprietary 10-16

 Apollo Reference Manual OPT96xx optical cards and modules

ROADM_20CF applications

The node ROADMs, connected to the ROADM_20CF Degree ports can be of different types like:
ROADM_4F, ROADM_9F, ROADM_20TF, etc.
The ROADM_20CF supports several options for connecting to the Client ports, including:
 Direct connection of a single Coherent or non-Coherent transceiver to a Client port configured as
OCHP channel.
 When the Client port is configured as OTS channel, several Coherent transceivers, can be
connected through a Splitter/Coupler outputs/inputs. This application supports Coherent
transceivers only. In addition the connection of the Splitter/Coupler must be made through an
amplification block to compensates for the Splitter/Coupler attenuation.
 Another option to connect several transceivers to a single Client port configured as OTS channel
is through a Mux/DeMux. In this case, the transceivers are 10 G, non-Coherent connected to the
Mux/DeMux ports. The Mux/DeMux is connected to the Client port through an amplification block
that compensates for the Mux/DeMux attenuation.

Ribbon Communications Inc. Proprietary 10-17

 Apollo Reference Manual OPT96xx optical cards and modules

10.4.3 ROADM_8x24CDCF
Supported platforms
 OPT9624
 OPT9608

Description
The ROADM_8x24CDCF is a 4-slot (double-wide and double-long) ROADM card with 8 degree ports
and 24 client ports. The ROADM_8x24CDCF supports the following:
 8 degree ports
 24 client colorless directionless contentionless (CDC) ports
 Flex-Grid operation over the extended C-band
 96/48 fixed grid channels with 50/100 GHz spacing
 Internal optical loopback
 DROP and ADD components implemented by double WSS modules

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-18

 Apollo Reference Manual OPT96xx optical cards and modules

Ports
The OUT/IN label near the connectors identifies the function of each of the corresponding ports. The
input signal is connected to the IN (ADD) connector in the pair and the output signal comes out through
the OUT (DROP) connector

Port name Number Function

DEGREE (n) 8 pairs Degree ports with LC connectors
CLIENT (n) 24 pairs
Client ports with LC connectors
MON -20dB 1
Monitor port for connection of line monitoring equipment

(n) port number

Usage guidelines
The most common application of the ROADM_8x24_CDCF module is as a collector for colorless-
directionless-contentionless (CDC) applications.
 Ports 1-8 are connected to the degree ports of the site in-line ROADMs.
 Ports 9-32 are connected to transceivers directly (OCHP) or via splitters (OTS).
The most common configuration is illustrated in the following figure.

Ribbon Communications Inc. Proprietary 10-19

 Apollo Reference Manual OPT96xx optical cards and modules

Contentionless operation of the ROADM8x24_CDCF is demonstrated below.

The same wavelength (red in this example) is connected to two (or more) different degree ports and
transmitted in different directions in the network.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when
there is no fault in the module.
Port LEDs
DEGREES LOS (n) Red LEDs Each channel's indicator lights if insufficient power is detected
at the corresponding DEGREE port input.

(n) port number

Ribbon Communications Inc. Proprietary 10-20

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

Internal Tx-Rx optical loopback

ROADM_8x24CDCF optical loopback functionality enables fiber verification through loopback of any
selected channel entering a client port. The loopback mechanism is implemented through an internal
port in which the transmit and receive are directly connected. Loopback is configured by directing the
required channel in a client port to the internal port and receiving it back again.
See Run an optical loopback in the STMS User Guide.

10.4.4 ROADM_9TF
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The ROADM_9TF is a 9 degree double-slot ROADM card. The ROADM_9TF supports the following:
 Flex-Grid operation over the extended C-band
 96/48 fixed grid channels with 50/100 GHz spacing
 DROP and ADD components implemented by two WSS modules
 OCM (Optical Channel Monitor) including channel power monitoring
 Fiber connectivity module, based on an 100 Mbps, 1528 nm SFP enabling verification and
inspection of the fiber-connectivity for the ROADM OTS Degree ports
 Internal optical loopback
 Power equalization of the channels at the line output
 WSON operation

Ribbon Communications Inc. Proprietary 10-21

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-22

 Apollo Reference Manual OPT96xx optical cards and modules

Ports

Port name Number Function

DEGREES (n) 9 pairs Degree ports with LC connectors
The input (ADD) and output (DROP) of each port is identified by the
marking below each port as IN and OUT
LINE 1 pair
Line port with LC connector
The input output is identified by the marking as IN and OUT below
the port
MON -20dB 1
Monitor port for connection of line monitoring equipment

(n) Port number

Usage guidelines
The most common application of the ROADM_9TF module is as a line ROADM in the network. It is
located at each of the site's ROADM network interfaces. The ROADM_9TF is a twin ROADM module.
This means that both the Add and Drop components are based on WSS technology rather than a
splitter. Therefore, the ROADM_9TF is a more appropriate choice for use in a Route & Select context,
rather than in a Broadcast & Select context (where a ROADM_9F or ROADM_9FS would be a better
choice).
A typical ROADM_9TF network configuration is illustrated in the following figure.

 The line port is connected to the transmission fiber (usually via amplifiers), while some of the 9-
degree ports are interconnected (mesh) with any of the other ROADM_9TF devices.
 The rest of the degree ports can be connected directly to the transceivers, splitters, Mux/DeMux
devices, or collector degree ports.

Ribbon Communications Inc. Proprietary 10-23

 Apollo Reference Manual OPT96xx optical cards and modules

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the module.
Port LEDs
Red LED Lights steadily when a LOS condition is detected at the corresponding
LOS (DEG Degree (Add) input.
ports 1 to 9)
Red LED Lights steadily when a LOS condition is detected at the LINE input.
LOS (LINE)

Block diagram

Internal Tx-Rx optical loopback

ROADM_9TF optical loopback functionality enables fiber verification through loopback of any selected
channel entering the line port. The optical loopback is provided only for the line port, and only for a
single channel at a time. The loopback mechanism is implemented through an internal ("10th Degree")
port in which the transmit and receive are directly connected. This port is then configured as a "Tx-Rx-
loop" using STMS. Any Degree port can be configured as a Tx-Rx-loop port.
A channel entering the line input port is looped back by configuring a bi-directional cross-connect
between the line port and the Tx-Rx-loop port at the specified wavelength.

Ribbon Communications Inc. Proprietary 10-24

 Apollo Reference Manual OPT96xx optical cards and modules

To configure a Tx-Rx-loop port:

 Select a single Degree port to be configured as the Tx-Rx-loop port.
 Use STMS to:
 Delete all cross-connects on the selected Degree port.
 Delete all fiber-connectivity of the selected Degree port.
 Configure the port as a Tx-Rx-loop. The necessary fiber connectivity between the port input
and output is generated automatically.
See Run an optical loopback in the STMS User Guide.

Loopback block diagram

10.4.5 ROADM_9FS
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The ROADM_9FS is a 9-degree single-slot ROADM card that supports the following:
 Flex-Grid operation over the extended C-band
 96/48 fixed grid channels with 50/100 GHz spacing
 DROP component implemented by a 1 x 9 splitter
 ADD component implemented by a WSS module
 OCM (Optical Channel Monitor)

Ribbon Communications Inc. Proprietary 10-25

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ports
The path-through (input) signal is connected to the IN connector in the pair and the path-through
(output) comes out through the OUT connector in the pair. The marking OUT and IN near the
connectors identifies the function of each of the corresponding ports.

Marking Number Function

DEGREES (1-9) 9 pairs Add and Drop ports
LOCAL-DEG1 Dual purpose LOCAL and DEG1 port

Ribbon Communications Inc. Proprietary 10-26

 Apollo Reference Manual OPT96xx optical cards and modules

Marking Number Function

LINE 1 pair
LINE IN (0) and LINE OUT (0)
MON -20dB 1
Monitors the line output signal for connecting monitoring
equipment

Usage guidelines
The most common application of the ROADM_9FS module is as a line ROADM in the network. It is
located at each of the site's ROADM network interfaces. The Add component of the ROADM_9FS
module is based on WSS technology and Drop component on splitter. Therefore, the ROADM_9FS is
more appropriate choice for use in a Broadcast & Select context, rather than in Route & Select context
(where ROADM_9TF would be a better choice). A typical ROADM_9FS configuration is illustrated in the
following figure.

 The line port is connected to the transmission fiber (usually via amplifiers), while some of the 9
degree ports are interconnected (mesh) with any of the other ROADM_9FS devices.
 The rest of the degree ports can be connected directly to the transceivers, splitters, Mux/DeMux
devices, or collector degree ports.

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when
there is no fault in the module.
Port LEDs

, LINE and Red LEDs Each channel's indicator lights if insufficient power is detected
DEGREES LOS at the corresponding LINE or DEGREE port input.
(Ports 0 to 9)

Ribbon Communications Inc. Proprietary 10-27

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram
ROADM_9FS functional block diagram

External Tx-Rx optical loopback

ROADM optical loopback functionality enables fiber verification through loopback of any selected
channel entering the line input port. The optical loopback is provided only for the line port, and only for a
single channel at a time.
To enable loopback functionality, one of the Degree ports is physically connected to itself (by a short
jumper) and then configured as a "Tx-Rx-loop" using STMS. A channel entering the line input port is
looped back by configuring a bi-directional cross-connect between the line port and the Tx-Rx-loop port
at the specified wavelength.
To configure a Tx-Rx-loop port:
 Select a single Degree port to be configured as the Tx-Rx-loop port.
 Use STMS to:
 Delete all cross-connects on the selected Degree port.
 Delete all fiber-connectivity of the selected Degree port.
 Connect a fiber patch cord between the input and output connectors of the Degree port to be
tested.
 Use STMS to configure the port as a Tx-Rx-loop. The necessary fiber connectivity between the
port input and output is generated automatically.
See Run an optical loopback in the STMS User Guide.

Ribbon Communications Inc. Proprietary 10-28

 Apollo Reference Manual OPT96xx optical cards and modules

10.4.6 ROADM_9F
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The ROADM_9F is a 9-degree double-slot ROADM card that supports the following:
 Flex-Grid operation over the extended C-band
 96/48 fixed grid channels with 50/100 GHz spacing
 DROP component implemented by a 1 x 9 splitter
 ADD component implemented by a WSS module
 OCM (Optical Channel Monitor)

Card views
General view

Ribbon Communications Inc. Proprietary 10-29

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

Ports
The path-through (input) signal is connected to the ADD connector in the pair and the path-through
(output) comes out through the DROP connector in the pair.
The marking ADD and DROP near the connectors identifies the function of each of the corresponding
ports.

Port name Number Function

DEG (1-9) 9 pairs ADD and DROP ports
DEG1 Dual purpose LOCAL and DEG1 port
LINE 1 pair
LINE IN (0) and LINE OUT (0)
MON -20dB 1
Monitors the line output signal for connecting monitoring equipment

Usage guidelines
 The most common application of the ROADM_9F module is as a line ROADM in the network. It is
located at each of the site's ROADM network interfaces. The line port is connected to the
transmission fiber (usually via amplifiers), while some of the 9-degree ports are interconnected
(mesh) with any of the other ROADM_9F devices.
 The rest of the degree ports can be connected directly to the transceivers, splitters, Mux/DeMux
devices, or collector degree ports.

Ribbon Communications Inc. Proprietary 10-30

Apollo Reference Manual OPT96xx optical cards and modules

LEDs

Marking Item Functions

Card LEDs
LOS Green LED Lights when the card is (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the module.
Port LEDs
DEG (1)-DEG (9) Red LEDs Each channel's indicator lights if insufficient power is detected at the
LOS corresponding DEGREE port input.
LINE LOS Red LED Lights if insufficient power is detected at the LINE port input.

Block diagram

Ribbon Communications Inc. Proprietary 10-31

 Apollo Reference Manual OPT96xx optical cards and modules

External Tx-Rx optical loopback

ROADM optical loopback functionality enables fiber verification through loopback of any selected
channel entering the line input port. The optical loopback is provided only for the line port, and only for a
single channel at a time.
To enable loopback functionality, one of the Degree ports is physically connected to itself (by a short
jumper) and then configured as a "Tx-Rx-loop" using STMS. A channel entering the line input port is
looped back by configuring a bi-directional cross-connect between the line port and the Tx-Rx-loop port
at the specified wavelength.
To configure a Tx-Rx-loop port:
 Select a single Degree port to be configured as the Tx-Rx-loop port.
 Use STMS to:
 Delete all cross-connects on the selected Degree port.
 Delete all fiber-connectivity of the selected Degree port.
 Connect a fiber patch cord between the input and output connectors of the Degree port to be
tested.
 Use STMS to configure the port as a Tx-Rx-loop. The necessary fiber connectivity between the
port input and output is generated automatically.
See Run an optical loopback in the STMS User Guide.

10.4.7 ROADM_9A50
Supported platforms
 OPT9624
 OPT9608

Description
The ROADM_9A50 is a 9-degree double-wide slot ROADM card that supports the following:
 88 channels with 50 GHz spacing in the C band
 Compatible with all 10 Gbps, 40 Gbps, and 100 Gbps cards

Ribbon Communications Inc. Proprietary 10-32

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-33

 Apollo Reference Manual OPT96xx optical cards and modules

Ports
The marking ADD and DROP near the connectors identifies the function of each of the corresponding
ports.

Port name Number Function

DEG (1-9) 9 pairs Add and Drop ports
LOCAL-DEG1 Dual purpose LOCAL and DEG1 port
LINE 1 pair
LINE IN (0) and LINE OUT (0)
MON -20dB 1
Monitors the line output signal for connecting monitoring
equipment

Usage guidelines
The most common application of the ROADM_9A50 is as a line ROADM in the network. It is located at
each of the site's ROADM network interfaces. The ROADM_9A50 is suitable for connection to channels
with 50GHz bandwidth that are centered over the 50GHz ITU grid.
 The line port is connected to the transmission fiber (usually via amplifiers), while some of the 9-
degree ports are interconnected (mesh) with any of the other ROADM_9A50 devices.
 The rest of the degree ports can be connected directly to the transceivers, splitters, Mux/DeMux
devices, or collector degree ports.

LEDs

Marking Item Functions

Card LEDs
IS Green Lights when the card is IS (assigned and completed configurations).
LED Off when the card is not assigned.
SW-U Yellow Currently not in use.
LED
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is
no fault in the module.
Port LEDs
DEG (2-9) LOS Red LEDs Each channel's indicator lights if insufficient power is detected at the
corresponding port input.
LOCAL/DEG (1) LOS Red LED Lights if insufficient power is detected at the LOCAL port input.
LINE LOS Red LED Lights if insufficient power is detected at the LINE port input.

Ribbon Communications Inc. Proprietary 10-34

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

External Tx-Rx optical loopback

ROADM optical loopback functionality enables fiber verification through loopback of any selected
channel entering the line input port. The optical loopback is provided only for the line port, and only for a
single channel at a time.
To enable loopback functionality, one of the Degree ports is physically connected to itself (by a short
jumper) and then configured as a "Tx-Rx-loop" using STMS. A channel entering the line input port is
looped back by configuring a bi-directional cross-connect between the line port and the Tx-Rx-loop port
at the specified wavelength.

Ribbon Communications Inc. Proprietary 10-35

 Apollo Reference Manual OPT96xx optical cards and modules

To configure a Tx-Rx-loop port:

 Select a single Degree port to be configured as the Tx-Rx-loop port.
 Use STMS to:
 Delete all cross-connects on the selected Degree port.
 Delete all fiber-connectivity of the selected Degree port.
 Connect a fiber patch cord between the input and output connectors of the Degree port to be
tested.
 Use STMS to configure the port as a Tx-Rx-loop. The necessary fiber connectivity between the
port input and output is generated automatically.
See Run an optical loopback in the STMS User Guide.

10.4.8 ROADM_4FS
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X

Description
The ROADM_4FS is a 4-degree single-slot ROADM card that includes all the features and functionality
of the double-slot ROADM_4F.
The ROADM_4FS supports the following:
 Flex-Grid operation over the extended C-band
 96/48 fixed grid channels with 50/100 GHz spacing
 DROP component implemented by a 1 x 4 splitter
 ADD component implemented by a WSS module
 OCM (Optical Channel Monitor)
 Colored, colorless/directionless, or colorless/directionless/contentionless (CDC) sites, by adding
the relevant collector cards
 2 pluggable CFP2 MSA amplifiers:
 Booster (OPA_FBS)
 Pre-amp (OPA_VLFS , OPA_LFS , or OPA_HFS)
 Built-in OSC

Ribbon Communications Inc. Proprietary 10-36

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ports
The marking OUT and IN near the connectors identifies the function of each of the corresponding ports.

Marking Number Function

DEG (1-4) 4 pairs Add and Drop ports
DEG1 Dual purpose LOCAL and DEG1 port
LINE 1 pair
LINE IN (0) and LINE OUT (0)
MON -20dB 1
Monitors the line output signal for connecting monitoring equipment
Pluggable Pre-Amp/Booster EDFA amplifiers marked 11-13 and 21-23
PRE-AMP 2

OSC 1 Built-in OSC filter

Ribbon Communications Inc. Proprietary 10-37

Apollo Reference Manual OPT96xx optical cards and modules

Usage guidelines
 The most common application of the ROADM_4FS module is as a line ROADM in the network. It
is located at each of the site's ROADM network interfaces. The line port is connected to the
transmission fiber (usually via amplifiers), while some of the 4-degree ports are interconnected
(mesh) with any of the other ROADM_4FS devices.
 The rest of the degree ports can be connected directly to the transceivers, splitters, Mux/DeMux
devices, or collector degree ports.

LEDs

Marking Item Functions

Card LEDs
IS Green Lights when the card is IS (assigned and completed configurations). Off
LED when the card is not assigned.
SW-U Yellow Currently not in use.
LED
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the module.
Amplifier LEDs
LOS Red LED Lights steadily when the signal on the return line (fiber) is missing. This
usually indicates a fiber cut.
ON Green Lights when the output power of the amplifier is above the threshold
LED level.
OSC LEDs
Tx Green Lights steadily when the OSC laser transmits.
LED
F/L Red LED Blinks when the OSC input signal is missing, or is too low for normal
operation. Lights when a fault is detected in the OSC path.
Port LEDs

, LINE and Red Each channel's indicator lights if insufficient power is detected at the
DEGREES LOS LEDs corresponding LINE or DEGREE port input.
(Ports 0 to 4)

Ribbon Communications Inc. Proprietary 10-38

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.4.9 ROADM_4F
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The ROADM_4F is a 4-degree double-slot ROADM card that supports the following:
 Flex-Grid operation over the extended C-band
 96/48 fixed grid channels with 50/100 GHz spacing
 DROP component implemented by a 1 x 4 splitter
 ADD component implemented by a WSS module
 OCM (Optical Channel Monitor)

Ribbon Communications Inc. Proprietary 10-39

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-40

 Apollo Reference Manual OPT96xx optical cards and modules

Ports
The path-through (input) signal is connected to the ADD connector in the pair and the path-through
(output) comes out through the DROP connector in the pair.
The marking ADD and DROP near the connectors identifies the function of each of the corresponding
ports.

Marking Number Function

DEGREE 4 pairs Add and Drop ports
LOCAL-DEG1 Dual purpose LOCAL and DEG1 port
LINE 1 pair
LINE IN (0) and LINE OUT (0)
MON -20dB 1
Monitors the line output signal for connecting monitoring equipment

Usage guidelines
 The most common application of the ROADM_4F module is as a line ROADM in the network. It is
located at each of the site's ROADM network interfaces. The line port is connected to the
transmission fiber (usually via amplifiers), while some of the 4 degree ports are interconnected
(mesh) with any of the other ROADM_4F devices.
 The rest of the degree ports can be connected directly to the transceivers, splitters, Mux/DeMux
devices, or collector degree ports.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when
there is no fault in the module.
Port LEDs
DEG (2)-DEG (4) LOS Red LEDs Each channel's indicator lights if insufficient power is detected
at the corresponding port input.
LOCAL/DEG (1) LOS Red LED Lights if insufficient power is detected at the LOCAL port input.
LINE LOS Red LED Lights if insufficient power is detected at the LINE port input.

Ribbon Communications Inc. Proprietary 10-41

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.4.10 ROADM_4A
Supported platforms
 OPT9624
 OPT9608

Description
The ROADM_4A is a 4-degree double-slot ROADM card that supports the following:
 44 channels with 100 GHz spacing in the C band
 Compatible with all 10 Gbps, 40 Gbps, and 100 Gbps cards

Ribbon Communications Inc. Proprietary 10-42

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ports
The path-through (input) signal is connected to the ADD connector in the pair and the path-through
(output) comes out through the DROP connector in the pair. The marking ADD and DROP near the
connectors identifies the function of each of the corresponding ports.

Marking Number Function

DEG (1-4) 4 pairs ADD and DROP ports
LOCAL-DEG1 Dual purpose LOCAL and DEG1 port
LINE 1 pair
LINE IN (0) and LINE OUT (0)
MON -20dB 1
Monitors the line output signal for connecting monitoring equipment

Ribbon Communications Inc. Proprietary 10-43

 Apollo Reference Manual OPT96xx optical cards and modules

Usage guidelines
The most common application of the ROADM_4A module is as a line ROADM in the network. It is
located at each of the site's ROADM network interfaces. The ROADM_4A is suitable for connection to
channels that are centered over the 100GHz ITU grid.
 The line port is connected to the transmission fiber (usually via amplifiers), while some of the 4-
degree ports are interconnected (mesh) with any of the other ROADM_4A devices.
 The rest of the degree ports can be connected directly to the transceivers, splitters, Mux/DeMux
devices, or collector degree ports.

LEDs

Marking Item Functions

Card LEDs
IS Green Lights when the card is IS (assigned and completed configurations). Off
LED when the card is not assigned.
SW-U Yellow Currently not in use.
LED
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the module.
Port LEDs
DEG (2)-DEG (4) Red LEDs Each channel's indicator lights if insufficient power is detected at the
LOS corresponding port input.
LOCAL/DEG (1) LOS Red LED Lights if insufficient power is detected at the LOCAL port input.
LINE LOS Red LED Lights if insufficient power is detected at the LINE port input.

Ribbon Communications Inc. Proprietary 10-44

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.4.11 ROADM_4A50
Supported platforms
 OPT9624
 OPT9608

Description
The ROADM_4A50 was originally designed as a 4-degree double-slot ROADM card that supports the
following:
 88 channels with 50 GHz spacing in the C band
 Compatible with all 10 Gbps, 40 Gbps, and 100 Gbps cards
Upon system upgrade to V9.0, the ROADM_4A50 will automatically be upgraded to ROADM_4F
functionality, enabling Flex-Grid operation.

Ribbon Communications Inc. Proprietary 10-45

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ports
The marking ADD and DROP near the connectors identifies the function of each of the corresponding
ports.

Marking Number Function

DEG (1-4) 4 pairs Add and Drop ports
LOCAL/DEG1 Dual purpose LOCAL and DEG1 port
LINE 1 pair
LINE IN (0) and LINE OUT (0)
MON -20dB 1
Monitors the line output signal for connecting monitoring
equipment

Ribbon Communications Inc. Proprietary 10-46

 Apollo Reference Manual OPT96xx optical cards and modules

Usage guidelines
The most common application of the ROADM_4A50 module is as a line ROADM in the network. It is
located at each of the site's ROADM network interfaces. The ROADM_4A50 is suitable for connection
to channels with 50GHz bandwidth that are centered over the 50GHz ITU grid.
 The line port is connected to the transmission fiber (usually via amplifiers), while some of the 4-
degree ports are interconnected (mesh) with any of the other ROADM_4A50 devices.
 The rest of the degree ports can be connected directly to the transceivers, splitters, Mux/DeMux
devices, or collector degree ports.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off
when there is no fault in the module.
Port LEDs
DEG (2)-DEG (4) LOS Red LEDs Each channel's indicator lights if insufficient power is
detected at the corresponding port input.
LOCAL/DEG (1) LOS Red LED Lights if insufficient power is detected at the LOCAL port
input.
LINE LOS Red LED Lights if insufficient power is detected at the LINE port
input.

Ribbon Communications Inc. Proprietary 10-47

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.4.12 ROADM_2A
Supported platforms
 OPT9624
 OPT9608

Description
The ROADM_2A is a 2-degree double-slot ROADM card that supports the following:
 44 channels with 100 GHz spacing in the C band
 Compatible with all 10 Gbps, 40 Gbps, and 100 Gbps cards

Ribbon Communications Inc. Proprietary 10-48

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
Front panel

Ports
The path-through (input) signal is connected to the ADD connector in the pair and the path-through
(output) comes out through the DROP connector in the pair. The marking ADD and DROP near the
connectors identifies the function of each of the corresponding ports.

Marking Number Function

EXPRESS 1 pair EXPRESS IN and EXPRESS OUT
LOCAL 1 pair LOCAL IN and LOCAL OUT
LINE 1 pair
LINE IN and LINE OUT
MON -20dB 1
Monitors the line output signal for connecting monitoring equipment

Usage guidelines
The most common application of the ROADM_2A module is as a line ROADM in the network. It is
located at each of the site's ROADM network interfaces. The ROADM_2A is suitable for connection to
channels that are centered over the 100GHz ITU grid.
 The line port is connected to the transmission fiber (usually via amplifiers), while some of the 2-
degree ports are interconnected (mesh) with any of the other ROADM_2A devices.
 The rest of the degree ports can be connected directly to the transceivers, splitters, Mux/DeMux
devices, or collector degree ports.

Ribbon Communications Inc. Proprietary 10-49

Apollo Reference Manual OPT96xx optical cards and modules

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the module.
Port LEDs
EXPRESS LOS Red LEDs Lights if insufficient power is detected at the EXPRESS input.
LOCAL LOS Red LED Lights if insufficient power is detected at the LOCAL input.
LINE LOS Red LED Lights if insufficient power is detected at the LINE input.

Block diagram

Ribbon Communications Inc. Proprietary 10-50

 Apollo Reference Manual OPT96xx optical cards and modules

10.4.13 ROADM_2A50
Supported platforms
 OPT9624
 OPT9608

Description
The ROADM_2A50 is a 2-degree wide double-slot ROADM card. The ROADM_2A50 supports the
following:
 88 channels with 50 GHz spacing in the C band
 Compatible with all 10 Gbps, 40 Gbps, and 100 Gbps cards

Card views
General view

Ribbon Communications Inc. Proprietary 10-51

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

Ports
The path-through (input) signal is connected to the ADD connector in the pair and the path-through
(output) comes out through the DROP connector in the pair. The marking ADD and DROP near the
connectors identifies the function of each of the corresponding ports.

Marking Number Function

EXPRESS 1 pair EXPRESS IN and EXPRESS OUT
LOCAL 1 pair LOCAL IN and LOCAL OUT
LINE 1 pair
LINE IN and LINE OUT
MON -20dB 1
Monitors the line output signal for connecting monitoring equipment

Usage guidelines
The most common application of the ROADM_2A50 module is as a line ROADM in the network. It is
located at each of the site's ROADM network interfaces. The ROADM_2A50 is suitable for connection
to channels with 50GHz bandwidth that are centered over the 50GHz ITU grid.
 The line port is connected to the transmission fiber (usually via amplifiers), while some of the 2-
degree ports are interconnected (mesh) with any of the other ROADM_2A50 devices.
 The rest of the degree ports can be connected directly to the transceivers, splitters, Mux/DeMux
devices, or collector degree ports.

Ribbon Communications Inc. Proprietary 10-52

Apollo Reference Manual OPT96xx optical cards and modules

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the module.
Port LEDs
EXPRESS LOS Red LEDs Lights if insufficient power is detected at the EXPRESS input.
LOCAL LOS Red LED Lights if insufficient power is detected at the LOCAL input.
LINE LOS Red LED Lights if insufficient power is detected at the LINE input.

Block diagram

Ribbon Communications Inc. Proprietary 10-53

 Apollo Reference Manual OPT96xx optical cards and modules

10.4.14 TFA_8
Supported platforms
 OPT9624
 OPT9608

Description
The TFA_8 is a Tunable Filter Array card that occupies a double-slot. It provides the colorless
functionality for the ROADM cards. It enables the operator to control the color of the drop ports. The
TFA_8 supports the following:
 Colorless Add/Drop of up to eight 50 GHz spaced DWDM channels
 88 DWDM channels of the ITU-T 50 GHz grid (Ch. 17 to Ch. 60.5)
 Compatible with all 10 Gbps, 40 Gbps, and 100 Gbps cards

Card views
General view

Ribbon Communications Inc. Proprietary 10-54

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

Ports
The path-through (input) signal is connected to the IN connector in the pair and the path-through
(output) comes out through the OUT connector in the pair.

Port name Number Function

C (1-8) 8 pairs
MON 1 Local monitoring
LINE 1 pair
LINE IN and LINE OUT

Ribbon Communications Inc. Proprietary 10-55

 Apollo Reference Manual OPT96xx optical cards and modules

Usage guidelines
A common application of TFA_8 is illustrated in the following figure.

The TFA line is connected to one of the site in-line ROADM degree ports, directly, or through a splitter.
The channel ports of the TFA (1-8) are connected to non-coherent transceivers. The TFA module
directs only a single channel to each of the connected transceivers, enabling non-coherent, colorless
operation.

NOTE: The TFA_8 card can only operate in a 50GHz fixed-grid network.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily if a fault is detected in the card. Off when there is no
fault in the TFA_8.
Line Port LEDs
LOS Red LED Lights if insufficient power is detected at the LINE input.

Ribbon Communications Inc. Proprietary 10-56

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram
The TFA_8 card includes eight tunable filters that determine the individual wavelength that will be
dropped in a certain port of a ROADM. The card has two sections (drop and add), each with its own line
input and line output connectors.

The incoming signal to the drop section is connected to the line connector LINE IN. The drop section is
implemented by a 1 x 8 splitter followed by an 8 channel tunable filter unit. In addition, a controller unit,
connected through the RS232 interface to the system's management, enables controlling the channels
that are dropped by the filters. The output signals from the eight splitter ports are fed into eight
independent tunable filters (wavelength blockers). The tunable filter can block or pass individual
channels according to control signals received from the management as configured by the user. The
resulting drop signals are provided at the C1 OUT to C8 OUT connectors.
The add section includes a 1 x 8 splitter that receives signals through eight input C1 IN to C8 IN
connectors, combines them, and provides the resulting signal at the LINE OUT connector. An isolator
on the output line prevents reflection from the connected WSS. In addition, a sample of the output
add-signal is connected to the monitoring port MON, enabling monitoring the signal for test or
maintenance purposes.

Ribbon Communications Inc. Proprietary 10-57

 Apollo Reference Manual OPT96xx optical cards and modules

10.5 Mux/DeMux cards

Apollo platforms offer a range of passive Mux/DeMux cards. The DWDM Mux/DeMux cards are based
on flat-top technology, enabling back-to-back connectivity with lower attenuation compared to other
technologies. With this configuration, minimal (if any) regeneration is required for the back-to-back
Mux/DeMux connectivity. Mux/DeMux cards are available for DWDM with 8, 16, 44, 48, 88, or 96
channels.
The following sections describe the Mux/DeMux cards available for Apollo platforms:
 MXD88
 MXD44
 MXD16
 MXD8

10.5.1 MXD88
Supported platforms
 OPT9624
 OPT9608

Description
The MXD88 is a quad-slot DWDM Mux/DeMux card for 88 channels in the C band (includes Ch. 17 to
Ch. 60.5 with 50 GHz spacing) and E/W configuration. The system management can detect and read
MXD88 properties like the Serial No. and HW Rev. All connections to the card are through LC type
connectors on the front panel.

Card views
Front panel

Ribbon Communications Inc. Proprietary 10-58

 Apollo Reference Manual OPT96xx optical cards and modules

The two sections of the front panel are:

 Mux: Operates as an 88-channel (50 GHz spacing) C band multiplexer. This section has a group
of 88 CHxx connectors (xx designates the channel number), each marked with the number of the
channel in accordance with the ITU T Recommendation G.694.1 grid. The marking M at the right
side of the panel identifies the corresponding multiplexer port input. The Mux output connector is
identified as LINE OUT. The LINE OUT level can be monitored at the MON -20 dB OUT
connector.
 DeMux: Operates as an 88-channel (50 GHz spacing) C band demultiplexer. This section has a
group of 88 CH Dxx connectors (xx designates the channel number) also marked with the G.694.1
channel number. The marking D at the right side of the panel identifies the corresponding
demultiplexer port output. The DeMux input connector is identified as LINE IN. The LINE IN level
can be monitored at the MON -20 dB IN connector.

Block diagram
88-channel C band Mux/DeMux functional block diagram

The functional block diagram of the MXD88 shows:

 The Mux section, whose functional block diagram is shown in part A of the preceding figure,
combines the optical signals applied to the CHxx connectors (xx designates the channel number),
and provides the resulting signal at the connector marked LINE OUT.
The -20 dB/0 dB splitter connected in the line output path provides a -20 dB sample of the optical
output signal to the MON -20dB OUT connector, thereby enabling monitoring of the optical Mux
output signal.
 The DeMux section, whose functional block diagram is shown in part B of the previous figure,
separates the optical signals applied to the LINE IN connector in accordance with their
wavelength, and provides the resulting signals at the CHxx connectors (xx designates the channel
number).
The -20 dB/0 dB splitter connected in the line input path provides a -20 dB sample of the optical
input signal to the MON -20dB IN connector, thereby enabling monitoring of the optical DeMux
input signal.

Ribbon Communications Inc. Proprietary 10-59

 Apollo Reference Manual OPT96xx optical cards and modules

10.5.2 MXD44
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The MXD44 is a double-slot DWDM Mux/DeMux card for 44 channels in the C band (Ch. 17-Ch. 60)
with 100 GHz spacing and E/W configuration. The system management can detect and read MXD44
properties like the Serial No. and HW Rev. All connections to the card are through LC type connectors
on the front panel.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-60

 Apollo Reference Manual OPT96xx optical cards and modules

The two sections of the front panel are:

 Mux: Operates as a 44-channel C band multiplexer. This section has a group of 44 CHxx
connectors (xx designates the channel number), each marked with the number of the channel in
accordance with the ITU T Recommendation G.694.1 grid. The marking M at the right side of the
panel identifies the corresponding multiplexer port input. The Mux output connector is identified as
LINE OUT. The LINE OUT level can be monitored at the MON -20 dB OUT connector.
 DeMux: Operates as a 44-channel C band demultiplexer. This section has a group of 44 CHxx
connectors (xx designates the channel number), also marked with the G.694.1 channel number.
The marking D at the right side of the panel identifies the corresponding demultiplexer port output.
The DeMux input connector is identified as LINE IN. The LINE IN level can be monitored at the
MON -20 dB IN connector.

Block diagram

The functional block diagram of the MXD44 shows:

 The Mux section, whose functional block diagram is shown in part A of the preceding figure,
combines the optical signals applied to the CHxx connectors (xx designates the channel number),
and provides the resulting signal at the connector marked LINE OUT.
The -20 dB/0 dB splitter connected in the line output path provides a -20 dB sample of the optical
output signal to the MON -20dB OUT connector, thereby enabling monitoring of the optical Mux
output signal.
 The DeMux section, whose functional block diagram is shown in part B of the previous figure,
separates the optical signals applied to the LINE IN connector in accordance with their
wavelength, and provides the resulting signals at the CHxx connectors (xx designates the channel
number).
The -20 dB/0 dB splitter connected in the line input path provides a -20 dB sample of the optical
input signal to the MON -20dB IN connector, thereby enabling monitoring of the optical DeMux
input signal.

Ribbon Communications Inc. Proprietary 10-61

 Apollo Reference Manual OPT96xx optical cards and modules

10.5.3 MXD16
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The MXD16 is a single-slot DWDM Mux/DeMux card for 16 channels in the C band (Ch.21-Ch.36) with
100 GHz spacing and E/W configuration. All connections to the card are through LC type connectors on
the front panel.

Card views
MXD16 general view

MXD16 front panel

Ribbon Communications Inc. Proprietary 10-62

 Apollo Reference Manual OPT96xx optical cards and modules

The two sections of the front panel are:

 Mux: Operates as a 16-channel C band multiplexer. This section has a group of 16 CHxx
connectors (xx designates the channel number), each marked with the number of the channel in
accordance with the ITU T Recommendation G.694.1 grid. The marking M at the right side of the
panel identifies the corresponding multiplexer port input. The Mux output connector is identified as
LINE OUT. The LINE OUT level can be monitored at the MON -20 dB OUT connector.
 DeMux: Operates as a 16-channel C band demultiplexer. This section has a group of 16 CHxx
connectors (xx designates the channel number) also marked with the G.694.1 channel number.
The marking D at the right side of the panel identifies the corresponding demultiplexer port output.
The DeMux input connector is identified as LINE IN. The LINE IN level can be monitored at the
MON -20 dB IN connector.

Functional block diagram

The functional block diagram of the MXD16 shows:

 The Mux section, whose functional block diagram is shown in part A of the preceding figure,
combines the optical signals applied to the CHxx connectors (xx designates the channel number),
and provides the resulting signal at the connector marked LINE OUT.
The -20 dB/0 dB splitter connected in the line output path provides a - 20 dB sample of the optical
output signal to the MON -20dB OUT connector, thereby enabling monitoring of the optical Mux
output signal.
 The DeMux section, whose functional block diagram is shown in part B of the previous figure,
separates the optical signals applied to the LINE IN connector in accordance with their
wavelength, and provides the resulting signals at the CHxx connectors (xx designates the channel
number).
The -20 dB/0 dB splitter connected in the line input path provides a - 20 dB sample of the optical
input signal to the MON -20dB IN connector, thereby enabling monitoring of the optical DeMux
input signal.

Ribbon Communications Inc. Proprietary 10-63

 Apollo Reference Manual OPT96xx optical cards and modules

10.5.4 MXD8
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The MXD8 is a single-slot DWDM Mux/DeMux card for 8 channels in the C band (Ch. 21-Ch. 28) with
100 GHz spacing and E/W configuration. All connections to the card are through LC type connectors on
the front panel.

Card views
MXD8 general view

MXD8 front panel

The two sections of the front panel are:

 Mux: Operates as a 8-channel C band multiplexer. This section has a group of 8 CHxx connectors
(xx designates the channel number), each marked with the number of the channel in accordance
with the ITU T Recommendation G.694.1 grid. The marking M at the right side of the panel
identifies the corresponding multiplexer port input. The Mux output connector is identified as LINE
OUT. The LINE OUT level can be monitored at the MON -20 dB OUT connector.
 DeMux: Operates as a 8-channel C band demultiplexer. This section has a group of 8 CHxx
connectors (xx designates the channel number) also marked with the G.694.1 channel number.
The marking D at the right side of the panel identifies the corresponding demultiplexer port output.
The DeMux input connector is identified as LINE IN. The LINE IN level can be monitored at the
MON -20 dB IN connector.

Ribbon Communications Inc. Proprietary 10-64

 Apollo Reference Manual OPT96xx optical cards and modules

MXD8 functional block diagram

The functional block diagram of the MXD8 shows:

 The Mux section, whose functional block diagram is shown in part A of the preceding figure,
combines the optical signals applied to the CHxx connectors (xx designates the channel number),
and provides the resulting signal at the connector marked LINE OUT.
The -20 dB/0 dB splitter connected in the line output path provides a - 20 dB sample of the optical
output signal to the MON -20dB OUT connector, thereby enabling monitoring of the optical Mux
output signal.
 The DeMux section, whose functional block diagram is shown in part B of the previous figure,
separates the optical signals applied to the LINE IN connector in accordance with their
wavelength, and provides the resulting signals at the CHxx connectors (xx designates the channel
number).
The -20 dB/0 dB splitter connected in the line input path provides a - 20 dB sample of the optical
input signal to the MON -20dB IN connector, thereby enabling monitoring of the optical DeMux
input signal.

10.6 CWDM components

Artemis offers several CWDM optical components that enable direct interworking with Apollo CWDM
equipment. This provides the flexibility to add and drop CWDM channels directly at the DWDM site
without affecting other traffic. The designation of the CWDM cards includes the prefix C, for example,
COADM4_xx for a 4-channel CWDM OADM unit.
The components include:
 CMXD8 : CWDM Mux/DeMux card for eight channels with built-in 1310 nm OSC filters
 COADM4_xx : CWDM OADM card with four add/drop channels

Ribbon Communications Inc. Proprietary 10-65

 Apollo Reference Manual OPT96xx optical cards and modules

10.6.1 CMXD8
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The CMXD8 is a single-slot CWDM Mux/DeMux card for eight channels with built-in 1310 nm OSC
filters and E/W configuration. The channels processed by the Mux/DeMux have nominal wavelengths of
1471 nm, 1491 nm, 1511 nm, 1531 nm, 1551 nm, 1571 nm, 1591 nm, and 1611 nm. All connections to
the card are through LC type connectors on the front panel.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-66

 Apollo Reference Manual OPT96xx optical cards and modules

The card has two sections:

 Mux: Operates as an 8-channel CWDM multiplexer with an additional OSC channel at 1310 nm.
This section has a group of eight CHxx connectors (xx designates the channel number), each
marked with the number of the channel in accordance with the ITU T Recommendation G.694.2
grid. The marking M at the right side of the panel identifies the corresponding multiplexer port
input. In addition, the Mux has a ninth input channel marked OSC 1310nm IN. The Mux output
connector is identified as LINE OUT. The LINE OUT level can be monitored at the MON -20dB
OUT connector.
 DeMux: Operates as an 8-channel demultiplexer with an additional OSC channel output at 1310
nm. This section has a group of eight CHxx connectors (xx designates the channel number) also
marked with the G.694.2 channel number. The marking D at the right side of the panel identifies
the corresponding demultiplexer port output. The ninth connector is for the OSC channel output,
and is marked OSC OUT. The DeMux input connector is identified as LINE IN. The LINE IN level
can be monitored at the MON -20dB IN connector.

Functional block diagram

The functional block diagram of the CMXD8 shows the Mux and DeMux sections with an OSC
capability:
 The Mux section, whose functional block diagram is shown in part A of the previous figure,
combines the optical signals applied to the CHxx connectors (xx designates the channel number).
The -20 dB/0 dB splitter connected in the line output path provides a -20 dB sample of the optical
output signal to the MON -20 dB OUT connector, thereby enabling monitoring of the optical Mux
output signal.
A second Mux combines the main line signal with the OSC signal (1310 nm) applied to the OSC
1310nm IN connector, and provides the resulting signal at the connector marked LINE OUT.
 The DeMux section, whose functional block diagram is shown in part B of the previous figure,
includes two demultiplexer units. The first separates the supervisory channel (OSC 1310 nm) from
the input signal. The resulting OSC signal appears at the OSC 1310nm OUT connector.
The -20 dB/0 dB splitter connected in the line input path provides a -20 dB sample of the optical
input signal to the MON -20 dB IN connector, thereby enabling monitoring of the optical DeMux
input signal.

Ribbon Communications Inc. Proprietary 10-67

 Apollo Reference Manual OPT96xx optical cards and modules

The second demultiplexer, separates the optical signals applied to the LINE IN connector in
accordance with their wavelength, and provides the resulting signals at the CHxx connectors (xx
designates the channel number).
 The card's OSC ports enable managing the card from a remote management station, without
occupying any of the eight CWDM channels used for data transmission.

10.6.2 COADM4_xx
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The COADM4_x is a single-slot CWDM OADM card with four add/drop channels for E/W configuration.
The xx in the COADM4_xx designates the number of the first add/drop channel in the CWDM ITU-T
grid. All connections to the card are through LC type connectors on the front panel.

Card views
General view

Front panel

In the preceding drawing, the markings D and A designate the Drop (output) and Add (input) of the port.

Ribbon Communications Inc. Proprietary 10-68

 Apollo Reference Manual OPT96xx optical cards and modules

Add/Drop channels
The COADM4_xx family includes two members. One adds/drops the four center channels: 1511 nm,
1531 nm, 1551 nm, and 1571 nm; the second adds/drops the four side channels: 1471 nm, 1491 nm,
1591 nm, and 1611 nm. The card types and add/drop channels are listed in the following table.

COADM4_xx card types and add/drop channels

Card type Add/Drop channels

COADM4_51 51, 53, 55, 57
COADM4_47 47, 49, 59, 61

Functional block diagram

The COADM4_xx card is a CWDM OADM designed to operate in an E/W configuration. The card has
two sections (drop and add), each with its own line input and line output connectors:
 The incoming line signal is applied to the line input connector LINE IN. The drop section is
implemented by four CWDM filters that extract the channel signal from the LINE IN signal.
 The dropped channel signals appear at the CHxx through CHxx+3 connectors (xx designates the
specific first channel).

Ribbon Communications Inc. Proprietary 10-69

 Apollo Reference Manual OPT96xx optical cards and modules

 The output signal of the filters appears at the EXP OUT connector of the drop section.
 The add section includes four CWDM filters which combine the channel add signals applied to the
CHxx through CHxx+3 connectors (xx designates the specific first channel) with the signal applied
to the EXP IN connector. The resulting signal appears at the LINE OUT connector.
In addition, -20 dB splitters are installed at the drop line side and at the add line side, enabling the
monitoring of the OADM line input and output signals. The drop line side monitoring signal appears at
the MON -20 dB IN connector and the add line side monitoring signal at the MON -20 dB OUT
connector.

10.7 OADM cards

Passive Optical ADM (OADM) cards perform the channel add-and-drop function. Artemis platforms
work with a wide range of passive OADM cards with various numbers of channels:
 2-channel
 4-channel
 8-channel
Two basic types of multichannel OADM cards are available for Neptune platforms:
 Fixed channel OADM cards which add/drop any of the predefined channels. The designation of
the fixed OADM cards includes the prefix F, for example, FOADM4_xx for a 4-channel fixed
OADM unit.
 Fixed OADM cards are a special branch of the FOADM family. These cards drop a predetermined
number of adjacent DWDM channels and enable adding any (colorless) same number of DWDM
channels.
The following sections describe the OADM cards available for Apollo platforms:
 FOADM2_xx
 FOADM4_xx
 FOADM850_xx

10.7.1 FOADM2_xx
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The FOADM2_xx is a single-slot fixed OADM card with two add/drop channels for E/W configuration.
The card adds/drops two adjacent DWDM 100 GHz-spaced channels. The xx in the FOADM2_xx
designates the number of the first add/drop channel in the ITU-T grid. All connections to the card are
through LC type connectors on the front panel.

Ribbon Communications Inc. Proprietary 10-70

 Apollo Reference Manual OPT96xx optical cards and modules

Add/Drop channels
The FOADM2_xx enables operators to add/drop several of the propagating channels as a low-cost
alternative to the more expensive ROADM cards. The FOADM2_xx family includes 22 members
corresponding to 22 combinations of two adjacent channels. Note that in the FOADM2_xx the channels
are spaced 100 GHz from each other (increments of 1 in the ITU-T grid). The card types and add/drop
channels are listed in the following table.

FOADM2_xx card types and add/drop channels

Card type Add/Drop channels

FOADM2_17 17, 18
FOADM2_19 19, 20
FOADM2_21 21, 22
FOADM2_23 23, 24
FOADM2_25 25, 26
FOADM2_27 27, 28
FOADM2_29 29, 30
FOADM2_31 31, 32
FOADM2_33 33, 34
FOADM2_35 35, 36
FOADM2_37 37, 38
FOADM2_39 39, 40
FOADM2_41 41, 42
FOADM2_43 43, 44
FOADM2_45 45, 46
FOADM2_47 47, 48
FOADM2_49 49, 50
FOADM2_51 51, 52
FOADM2_53 53, 54
FOADM2_55 55, 56
FOADM2_57 57, 58
FOADM2_59 59, 60

Card views
Front panel

The markings D and A designate the Drop (output) and Add (input) of the port.

Ribbon Communications Inc. Proprietary 10-71

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

The FOADM2_xx card is designed to operate in an E/W configuration. The card has two sections (drop
and add), each with its own line input and line output connectors:
 The incoming line signal is applied to the line input connector LINE IN. The drop section is
implemented by a 2-skip-0 filter followed by two serial 100 GHz filters that extract the channel
signal from the LINE IN signal.
 The dropped channel signals appear at the CHxx and CHxx+1 connectors (xx, designates the
specific channels).
 The output signal of the filters appears at the EXP OUT connector of the drop section.
 The add section includes two serial 100 GHz filters and a 2-skip-0 filter which combine the
channel add signals applied to the CHxx and CHxx+1 connectors (xx, designates the specific
channels) with the signal applied to the EXP IN connector. The resulting signal appears at the
LINE OUT connector.
In addition, -20 dB splitters are installed at the drop line side and at the add line side, enabling the
monitoring of the OADM line input and output signals. The drop line side monitoring signal appears at
the MON -20 dB IN connector and the add line side monitoring signal at the MON -20 dB OUT
connector.

Ribbon Communications Inc. Proprietary 10-72

 Apollo Reference Manual OPT96xx optical cards and modules

10.7.2 FOADM4_xx
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The FOADM4_xx is a single-slot fixed OADM card with four add/drop channels for E/W configuration.
The card adds/drops four adjacent DWDM 100 GHz-spaced channels. The xx in the FOADM4_xx
designates the number of the first add/drop channel in the ITU-T grid. All connections to the card are
through LC type connectors on the front panel.

Add/Drop channels
The FOADM4_xx enables operators to add/drop several of the propagating channels as a low-cost
alternative to the more expensive ROADM cards. The FOADM4_xx family includes 11 members
corresponding to 11 combinations of four adjacent channels. Note that in the FOADM4_xx the channels
are spaced 100 GHz from each other (increments of 1 in the ITU-T grid). The card types and add/drop
channels are listed in the following table.

FOADM4_xx card types and add/drop channels

Card type Add/Drop channels
FOADM4_17 17, 18, 19, 20
FOADM4_21 21, 22, 23, 24
FOADM4_25 25, 26, 27, 28
FOADM4_29 29, 30, 31, 32
FOADM4_33 33, 34, 35, 36
FOADM4_37 37, 38, 39, 40
FOADM4_41 41, 42, 43, 44
FOADM4_45 45, 46, 47, 48
FOADM4_49 49, 50, 51, 52
FOADM4_53 53, 54, 55, 56
FOADM4_57 57, 58, 59, 60

Card views
Front panel

The markings D and A designate the Drop (output) and Add (input) of the port.

Ribbon Communications Inc. Proprietary 10-73

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram
FOADM4_xx functional block diagram

The FOADM4_xx card is designed to operate in an E/W configuration. The card has two sections (drop
and add), each with its own line input and line output connectors:
 The incoming line signal is applied to the line input connector LINE IN. The drop section is
implemented by a 4-skip-0 bandpass filter followed by a block of four 100 GHz filters that extract
the channel signal from the LINE IN signal.
 The dropped channel signals appear at the CHxx through CHxx+3 connectors (xx designates the
specific channels).
 The output signal of the filters appears at the EXP OUT connector of the drop section.
 The add section includes a block of four 100 GHz filters followed by a 4-skip-0 bandpass filter
which combine the channel add signals applied to the CHxx through CHxx+3 (xx designates the
specific channels) connectors with the signal applied to the EXP IN connector. The resulting signal
appears at the LINE OUT connector.
In addition, -20 dB splitters are installed at the drop line side and at the add line side, enabling the
monitoring of the OADM line input and output signals. The drop line side monitoring signal appears at
the MON -20 dB IN connector and the add line side monitoring signal at the MON -20 dB OUT
connector.

Ribbon Communications Inc. Proprietary 10-74

 Apollo Reference Manual OPT96xx optical cards and modules

10.7.3 FOADM850_xx
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The FOADM850_xx is a fixed OADM single-slot card with seven add/drop channels for E/W
configuration. The card adds/drops seven adjacent DWDM 50 GHz-spaced channels; the eighth
channel is cut by the card's filter and cannot be used. The xx in the FOADM850_xx designates the
number of the first add/drop channel in the ITU-T grid. All connections to the card are through LC type
connectors on the front panel.

Card views
General view

Front panel

Add/Drop channels
The FOADM850_xx enables operators to add/drop several of the propagating channels, as a low-cost
alternative to the more expensive ROADM cards. The FOADM850_xx family includes 11 members
corresponding to 11 combinations of eight adjacent channels. Note that in the FOADM850_xx, the
channels are spaced 50 GHz from each other (increments of 0.5 in the ITU-T grid). Each card
adds/drops seven channels. The closest channel to these seven channels (at both ends) is blocked by
the FOADM and does not come out on any port.

Ribbon Communications Inc. Proprietary 10-75

 Apollo Reference Manual OPT96xx optical cards and modules

The card types, add/drop, and blocked channels are listed in the following table.

FOADM850_xx card types, add/drop, and blocked channels

Card type Add/Drop channels Blocked channels
FOADM850_17 17, 17.5, 18, 18.5, 19, 19.5, 20 20.5
FOADM850_21 21, 21.5, 22, 22.5, 23, 23.5, 24 20.5, 24.5
FOADM850_25 25, 25.5, 26, 26.5, 27, 27.5, 28 24.5, 28.5
FOADM850_29 29, 29.5, 30, 30.5, 31, 31.5, 32 28.5, 32.5
FOADM850_33 33, 33.5, 34, 34.5, 35, 35.5, 36 32.5, 36.5
FOADM850_37 37, 37.5, 38, 38.5, 39, 39.5, 40 36.5, 40.5
FOADM850_41 41, 41.5, 42, 42.5, 43, 43.5, 44 40.5, 44.5
FOADM850_45 45, 45.5, 46, 46.5, 47, 47.5, 48 44.5, 48.5
FOADM850_49 49, 49.5, 50, 50.5, 51, 51.5, 52 48.5, 52.5
FOADM850_53 53, 53.5, 54, 54.5, 55, 55.5, 56 52.5, 56.5
FOADM850_57 57, 57.5, 58, 58.5, 59, 59.5, 60 56.5, 60.5

Block diagram
FOADM850_xx functional block diagram

Ribbon Communications Inc. Proprietary 10-76

 Apollo Reference Manual OPT96xx optical cards and modules

The FOADM850_xx card is designed to operate in an E/W configuration. The card has two sections
(drop and add), each with its own line input and line output connectors:
 The incoming line signal is applied to the LINE IN connector of the drop section. The drop function
is performed by a 7-skip-1 bandpass filter with 50 GHz spacing, followed by an interleaver and two
demultiplexers that extract the channel signals from the LINE IN signal.
 The dropped channel signals spaced 50 GHz apart appear at the CHxx, CHxx+0.5, CHxx+1,... to
CHxx+3 connectors (xx designates the first drop channel, the marking D designates the drop
channel output).
 The resulting signal after the channels drop appears at the EXP OUT (Express output) connector
of the drop section.
 The input signal to the add section is applied to the EXP IN (Express input) connector of the add
section and through a 75%/25% splitter to a 7-skip-1 filter. The add function is performed by three
100 GHz filters and three 50%/50% splitters followed by the 7-skip-1 bandpass filter with 50 GHz
spacing.
 The add signals are applied through the CHxx, CHxx+0.5, CHxx+1,... to CHxx+3 connectors to
the 100 GHz filters, except for the 7th that is directly applied to the second 50%/50% splitter (xx
designates the first add channel, the marking A designates the add channel input).
 The resulting signal of the express input with the added channels appears at the LINE OUT
connector.
In addition, -20 dB/0 dB splitters are installed at the drop line side and at the add line side, enabling the
monitoring of the OADM line input and output signals. The drop line side monitoring signal appears at
the MON -20 dB IN connector and the add line side monitoring signal at the MON -20 dB OUT
connector.

10.8 Optical filters, splitters, and couplers

Artemis and Apollo platforms offer several options for optical filters, splitters, and couplers, described in
this section.

10.8.1 CT_1310_2
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The CT_1310_2 is a single-slot optical card that includes two separate CT filters with a 1310 nm OSC
port each. All connections to the card are through LC type connectors on the front panel.

Ribbon Communications Inc. Proprietary 10-77

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
CT_1310_2 front panel

The card incorporates two sets of filters whose ports are marked with suffix 1 and 2. Each filter works
with an OSC Mux/DeMux pair. The functions of set 1 are as follows (the functions of set 2 are identical):
 The OSC DeMux is used to separate the 1310 nm optical OSC from the C band payload signal (in
the 1550 nm range). The DeMux has one input connector (LINE 1 IN) and two output connectors,
C-BAND 1 OUT (C band) and 1310 nm 1 OUT (OSC signal).
 The OSC Mux is used to combine the two signals before they are sent to the line. The Mux has
two input connectors, C-BAND 1 IN and 1310 nm 1 IN (OSC signal), and one output connector,
LINE 1 OUT.

Functional block diagram

Ribbon Communications Inc. Proprietary 10-78

 Apollo Reference Manual OPT96xx optical cards and modules

10.8.2 CT_1510_2
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The CT_1510_2 is a single-slot optical card that includes two separate CT filters with a 1510 nm OSC
port each. All connections to the card are through LC type connectors on the front panel.

Card views
General view

Front panel

The card incorporates two sets of filters whose ports are marked with suffix 1 and 2. Each filter works
with an OSC Mux/DeMux pair. The functions of set 1 are as follows (the functions of set 2 are identical):
 The OSC DeMux is used to separate the 1510 nm optical OSC from the C band payload signal (in
the 1550 nm range). The DeMux has one input connector (LINE 1 IN) and two output connectors,
C-BAND 1 OUT (C band) and 1510 nm 1 OUT (OSC signal).
 The OSC Mux is used to combine the two signals before they are sent to the line. The Mux has
two input connectors, C-BAND 1 IN and 1510 nm 1 IN (OSC signal), and one output connector,
LINE 1 OUT.

Ribbon Communications Inc. Proprietary 10-79

Apollo Reference Manual OPT96xx optical cards and modules

Functional block diagram

Ribbon Communications Inc. Proprietary 10-80

 Apollo Reference Manual OPT96xx optical cards and modules

10.8.3 CT_OTDR_2
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The CT_OTDR_2 is a single-slot optical card that includes two separate filters. Each filter
Muxes/DeMuxes the 1610 nm OTDR, C-Band, and 1510 nm OSC signals. The OTDR signal is a light
pulse that enables to determine the location of a fiber cut, by connecting an OTDR device to the OTDR
port. All connections to the card are through LC type connectors on the front panel.
The CT_OTDR_2 Muxes/DeMuxes the 1610 nm OTDR, C-band, and 1510 nm OSC signals. OTDR
filter cards may be placed at the end of the span that should be monitored by OTDR. Usually, it is
placed between an EDFA card and the transmission fiber end. The OTDR filter card should not be
employed on spans that include Raman amplification.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-81

 Apollo Reference Manual OPT96xx optical cards and modules

The CT_OTDR_2 includes two independent CLT filter pairs – each performs full Mux/DeMux of the C-
band, 1510nm OSC, and 1610nm OTDR signals. The card incorporates two sets of filters whose ports
are marked with suffix 1 and 2. Each filter works with a Mux/DeMux pair. The functions of set 1 are as
follows (the functions of set 2 are identical):
 The DeMux separates the 1510 nm optical OSC, C band payload signal (in the 1550 nm range),
and 1610 nm OTDR from the line signal. The DeMux has one input connector (LINE 1 IN) and
three output connectors: C-BAND 1 OUT (C band), OSC-1510 1 OUT (OSC signal), and OTDR-
1610 1.
 The Mux combines the three signals before they are sent to the line. The Mux has three input
connectors: C-BAND 1 IN, OSC -1510 1 IN (OSC signal), OTDR-1610 1 IN, and one output
connector: LINE 1 OUT.

Block diagram

Usage guidelines
When a fiber span includes OTDR filters (C_xxx_OTDR) at both sides, an open (non-terminated) OTDR
tap port at the far side of the span will result in high back-reflection of the OTDR signal. The strong
back-reflected signal may be double back-reflected by the fiber splices/connectors and result in
generation of "ghost events".
This can be prevented by connecting "OTDR termination" to the open OTDR Tap ports.
The OTDR termination is supplied with the filter card installation kit, and it is highly recommended to
use it.

Ribbon Communications Inc. Proprietary 10-82

 Apollo Reference Manual OPT96xx optical cards and modules

OTDR deployment, two typical scenarios

The red circles mark the ports that should be terminated with the "OTDR termination".

10.8.4 CT_OTDR_2_WIDE
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The CT_OTDR_2_WIDE is a single-slot optical card that includes two separate filters. Each filter
Muxes/DeMuxes the 1610 nm OTDR, C-Band, and OSC 1510 nm with Wide-band channels (marked
as WIDE port). The OTDR signal is a light pulse that enables to determine the location of a fiber cut, by
connecting an OTDR device to the OTDR port. The CT_OTDR_2_WIDE is similar to the CT_OTDR_2 ,
and differs only in the WIDE port that provides an option for transferring more optical channels. All
connections to the card are through LC type connectors on the front panel.
The CT_OTDR_2_WIDE Muxes/DeMuxes the 1610 nm OTDR, C-band, and WIDE port signals. OTDR
filter cards may be placed at the end of the span that should be monitored by OTDR. Usually, it is
placed between an EDFA card and the transmission fiber end. The OTDR filter card should not be
employed on spans that include Raman amplification.

Ribbon Communications Inc. Proprietary 10-83

 Apollo Reference Manual OPT96xx optical cards and modules

The OSC-1510 WIDE port enables transmission of the following channels:

 OSC 1510 nm signal (supervisory channel)
 Additional wavelengths in the ranges:
 1270 - 1520 nm
 1580 - 1597 nm
 1623 - 1650 nm
This provides an additional option for transmitting extra channels more than the channels transferred
via the C-Band port.

Card views
General view

Front panel

The CT_OTDR_2_WIDE includes two independent CLT filter pairs – each performs full Mux/DeMux of
the C-band, Wide-band, and 1610nm OTDR signals. The card incorporates two sets of filters whose
ports are marked with suffix 1 and 2. Each filter works with a Mux/DeMux pair. The functions of set 1
are as follows (the functions of set 2 are identical):
 The DeMux separates the OSC-1510 signal and the other WIDE port channels, C band payload
signal (in the 1550 nm range), and 1610 nm OTDR from the line signal. The DeMux has one input
connector (LINE 1 IN) and three output connectors: C-BAND 1 OUT (C band), OSC-1510 WIDE 1
OUT (OSC and other channels in the Wide-band), and OTDR-1610 1.
 The Mux combines the three signals before they are sent to the line. The Mux has three input
connectors: C-BAND 1 IN, OSC-1510 WIDE 1 IN (OSC and other Wide-band channels), OTDR-
1610 1 IN, and one output connector: LINE 1 OUT.

Ribbon Communications Inc. Proprietary 10-84

 Apollo Reference Manual OPT96xx optical cards and modules

Note that the OSC 1510 nm signal must be mixed with the required Wide-band channels through an
additional filter before connecting it to the OSC-1510 WIDE port. Similarly, at the other end the OSC-
1510 nm signal is mixed with the other Wide-band channels. A filter must be used at the OSC-1510
WIDE OUT port to separate the signals.

Functional block diagram

10.8.5 C_OTDR_2
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The C_OTDR_2 is a single-slot optical card that includes two separate filters. Each filter
Muxes/DeMuxes the 1610 nm OTDR signal with the combined 1510 nm OSC and C-Band signals. The
OTDR signal is a light pulse that enables you to determine the location of a fiber cut, by connecting an
OTDR device to the OTDR port. All connections to the card are through LC type connectors on the front
panel.
OTDR filter cards may be placed at the end of the span that should be monitored by OTDR. Usually, it
is placed between an EDFA card and the transmission fiber end. The OTDR filter card should not be
employed on spans that include Raman amplification.

Ribbon Communications Inc. Proprietary 10-85

 Apollo Reference Manual OPT96xx optical cards and modules

The C_OTDR_2 differs from the CT_OTDR_2 by the fact that in this card the C-Band and OSC 1510
nm signals arrive already combined at the input and the output for these signals is also a combined
one.

TIP: The C-Band+OSC port can support 1310nm (O-Band) signals as well, for combining
OTDR and 1310nm gray interfaces.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-86

 Apollo Reference Manual OPT96xx optical cards and modules

The C_OTDR_2 includes two independent CLT filter pairs – each performs full Mux/DeMux of the C-
band, and the combined 1510nm OSC and 1610nm OTDR signals. The card incorporates two sets of
filters whose ports are marked with suffix 1 and 2. Each filter works with an OSC Mux/DeMux pair. The
functions of set 1 are as follows (the functions of set 2 are identical):
 The DeMux separates the combined 1510 nm optical OSC and C-band payload signals from the
OTDR 1610 nm signal. The DeMux has one input connector (LINE 1 IN) and two output
connectors, C-BAND + OSC 1 OUT (combined C-BAND and OSC signals) and OTDR-1610 nm 1
OUT (OTDR signal).
 The Mux combines the two signals before they are sent to the line. The Mux has two input
connectors, labeled C-BAND 1 + OSC 1 IN and OTDR-1610 1 IN (OTDR signal), and one output
connector, LINE 1 OUT.

Block diagram

Usage guidelines
When a fiber span includes OTDR filters (C_xxx_OTDR) at both sides, an open (non-terminated) OTDR
tap port at the far side of the span will result in high back-reflection of the OTDR signal. The strong
back-reflected signal may be double back-reflected by the fiber splices/connectors and result in
generation of "ghost events".
This can be prevented by connecting "OTDR termination" to the open OTDR Tap ports.
The OTDR termination is supplied with the filter card installation kit, and it is highly recommended to
use it.

Ribbon Communications Inc. Proprietary 10-87

 Apollo Reference Manual OPT96xx optical cards and modules

OTDR deployment, two typical scenarios

The red circles mark the ports that should be terminated with the "OTDR termination".

10.8.6 SP_SM_4
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The SP_SM_4 is a single-slot quad splitter/coupler for single mode (SM) fibers with 50% ratio card that
includes four identical splitter/coupler units. All connections to the card are through LC type connectors
on the front panel.
The splitters divide an input signal into two equal signals. The couplers combine two input signals. The
SP_SM_4 provides four splitter/coupler units, supporting up to four fixed protected services
simultaneously.

Ribbon Communications Inc. Proprietary 10-88

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

The front panel markings do not refer to splitter or coupler but rather to users and services. The
corresponding ports are marked with numbers from 1 to 4 accordingly.
The SP_SM_4 has four splitters/couplers, each marked with numbers from 1 to 4. Each unit has three
connectors, marked USER, SERV-A, and SERV-B with the corresponding number suffix. The following
describes the ports of unit 1 (the same functions are provided by the other three units). The input signal
to the splitter is connected to the USER 1 IN connector. Two equal output signals are received at
connectors SERV-A 1 OUT and SERV-B 1 OUT. The coupler in unit 1 receives two signals connected
to connectors SERV-A 1 IN and SERV-B 1 IN, and the resulting combined signal is provided at
connector USER 1 OUT.

Ribbon Communications Inc. Proprietary 10-89

 Apollo Reference Manual OPT96xx optical cards and modules

Functional block diagram

10.8.7 SP_MM_4
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The SP_MM_4 is a single-slot quad splitter/coupler for multi-mode (MM) fibers with 50% ratio card that
includes four identical splitter/coupler units. All connections to the card are through LC type connectors
on the front panel.
The splitters divide an input signal into two equal signals. The couplers combine two input signals. The
SP_MM_4 provides four splitter/coupler units, supporting up to four fixed protected services
simultaneously.

Ribbon Communications Inc. Proprietary 10-90

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
Front panel

The front panel markings do not refer to splitter or coupler but rather to users and services. The
corresponding ports are marked with numbers from 1 to 4 accordingly.
The card has four splitters/couplers, each marked with numbers from 1 to 4. Each unit has three
connectors, marked USER, SERV-A, and SERV-B with the corresponding number suffix. The following
describes the ports of unit 1 (the same functions are provided by the three other units). The input signal
to the splitter is connected to the USER 1 IN connector. Two equal output signals are received at
connectors SERV-A 1 OUT and SERV-B 1 OUT. The coupler in unit 1 receives two signals connected
to connectors SERV-A 1 IN and SERV-B 1 IN and the resulting combined signal is provided at
connector USER 1 OUT.

Functional block diagram

Ribbon Communications Inc. Proprietary 10-91

 Apollo Reference Manual OPT96xx optical cards and modules

10.8.8 SP_CE4_2
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The SP_CE4_2 is a single-slot double splitter/coupler card for four services with 25% ratio. The card
includes two identical splitter/coupler units. All connections to the card are through LC type connectors
on the front panel.
The splitters divide an input signal into four equal signals (25% ratio). The couplers combine four input
signals. The SP_CE4_2 provides two splitter/coupler units, supporting up to four fixed protected
services simultaneously suitable for directionless/colorless ROADM sites.

Card views
General view

Front panel

The front panel markings refer to SPLITTER A and SPLITTER B, where each unit includes a 4-way
splitter/coupler. The corresponding ports are marked with numbers from 1 to 4 accordingly.

Ribbon Communications Inc. Proprietary 10-92

 Apollo Reference Manual OPT96xx optical cards and modules

The card has two splitters/couplers marked SPLITTER A and SPLITTER B. The following describes the
ports of unit A (the same functions are provided by the second unit (B)). The input signal to the splitter
is connected to the LINE-A IN connector. Four equal output signals (25% of the input signal each) are
provided at connectors P1-A OUT through P4-A OUT. The coupler in unit A receives four signals
connected to connectors P1-A IN through P4-A IN, and the resulting combined signal is provided at
connector LINE-A OUT.

Functional block diagram

Ribbon Communications Inc. Proprietary 10-93

 Apollo Reference Manual OPT96xx optical cards and modules

10.8.9 SP_CE8_1
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The SP_CE8_1 is a single-slot 1 x 8 splitter/coupler card, used for C/CD reception of coherent channels
in both coherent networks and mixed networks (including both coherent and non-coherent channels).
All connections to the card are through LC type connectors on the front panel.
The SP_CE8_1 provides a splitter/coupler unit, supporting up to eight fixed protected services
simultaneously suitable for directionless/colorless ROADM sites. The splitter divides an input signal into
eight equal signals (12.5% ratio). The coupler combines eight input signals into a single signal.

Card views
General view

Front panel

The input signal to the splitter is connected to the LINE IN connector. Eight equal signals (12.5 % of the
input signal each) are provided at connectors P1 OUT to P8 OUT.

Ribbon Communications Inc. Proprietary 10-94

 Apollo Reference Manual OPT96xx optical cards and modules

The coupler unit receives eight signal, connected to connectors P1 IN to P8 IN, and the resulting
combined signal is provided at connector LINE OUT.

Functional block diagram

10.8.10 SP_CE16_1
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The SP_CE16_1 is a single-slot 1 x 16 splitter/coupler card, used for C/CD reception of coherent
channels in both coherent networks and mixed networks (including both coherent and non-coherent
channels). All connections to the card are through LC type connectors on the front panel.
The SP_CE16_1 provides a splitter/coupler unit, supporting up to sixteen fixed protected services
simultaneously, suitable for directionless/colorless ROADM sites. The splitter divides an input signal
into sixteen equal signals (6.25% ratio). The coupler combines sixteen input signals into a single signal.

Ribbon Communications Inc. Proprietary 10-95

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

The input signal to the splitter is connected to the LINE IN connector. Sixteen equal signals (6.25% of
the input signal each) are provided at connectors P1 OUT to P16 OUT.
The coupler unit receives sixteen signals, connected to connectors P1 IN to P16 IN, and the resulting
combined signal is provided at connector LINE OUT.

Ribbon Communications Inc. Proprietary 10-96

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.8.11 SP_CE32_1
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The SP_CE32_1 is a double-slot card that includes two independent splitter/coupler sections: a 1 x 32
bidirectional splitter/coupler unit and a 1 x 2 bidirectional splitter/coupler unit. It is used for coherent CD
(colorless-directionless) and CDC reception in ROADM nodes. In particular, the card is employed in
pure coherent networks. All connections to the card are through LC type connectors on the front panel.

Ribbon Communications Inc. Proprietary 10-97

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

The line port of the 1 x 32 bidirectional splitter/coupler (at the left side of the card) is marked LINE; the
other ports are marked P1 to P32. Similarly, the line port of the 1 x 2 bidirectional splitter/coupler (at the
right side of the card) is marked LINE and the two other ports are marked P34 and P35.
The 1 x 32 section divides an input signal into 32 equal signals (3.125% ratio). The coupler combines
32 input signals.
The 1 x 2 section divides an input signal into two equal signals (50% ratio). The coupler of this section
combines 2 input signals.

Ribbon Communications Inc. Proprietary 10-98

Apollo Reference Manual OPT96xx optical cards and modules

Functional block diagram

Ribbon Communications Inc. Proprietary 10-99

 Apollo Reference Manual OPT96xx optical cards and modules

10.9 Synchronization filters

Today's communication networks require extremely accurate timing signals over DWDM for NG
applications. The Apollo and Artemis platforms provide a set of synchronization filters that address
increasing requirements for accurate timing signals over DWDM for various applications.
Apollo synchronization filters distribute frequency and phase/time timing over an out-of-band Optical
Timing Channel (OTC) over WDM links through the bi-directional wavelength, on single fiber.
The actual timing is carried by a Boundary Clock (BC), either in Neptune or 3rd party BC devices,
connected to a single fiber filter over an Apollo DWDM network. Delivering the synchronization signals
generated with two wavelengths over a single fiber assures minimum asymmetric delay.
The basic filter is based on OTC over two CWDM channels; the Chromatic Dispersion (CD) delay
between the two CWDM channels is 40ns/100Km. The high accuracy filter is based on OTC over two
adjacent DWDM channels in the S-band grid; the CD delay between the two DWDM channels is
1.3ns/100Km. In both filters the OTC does not consume any portion of the extended DWDM C-band
grid.
The following figure illustrates the basic principles of how to place the filters in order to effectively
deliver the synchronization signal over the Apollo optical network.

The following single slot filters are installed in Artemis and/or Apollo platforms:
 CT_1510/1490 : Single slot C/T filter, in which the synchronization signal is carried on a single TX
fiber (1510/1490nm).
 CT_1510/1490_OTDR : Single slot C/T filter, in which the synchronization signal is carried on a
single TX fiber (1510/1490nm), with OTDR over 1610nm in service monitoring on RX fiber.
 CT_1590_1511_OTDR : Single slot C/T filter, in which the synchronization signal is carried on a
single TX fiber (1511.05/1511.81nm), with OSC signal carried over 1590nm and OTDR signal
over 1610nm.
 CT_1610 : Single slot C/T filter, in which the synchronization signal is carried on a single TX fiber
(1610.93/1611.80nm). This filter is appropriate for use in situations where external filters can’t be
added at the xHRSF line input, due to the Raman pump.

Ribbon Communications Inc. Proprietary 10-100

 Apollo Reference Manual OPT96xx optical cards and modules

10.9.1 CT_1510/1490
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The CT_1510/1490 is a single-slot C/T filter, in which the synchronization signal is carried on a single
TX fiber (1510/1490nm).

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-101

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.9.2 CT_1510/1490_OTDR
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The CT_1510/1490_OTDR is a single-slot C/T filter, in which the synchronization signal is carried on a
single TX fiber (1510/1490nm), with OTDR over 1610nm in-service monitoring on the RX fiber.

Ribbon Communications Inc. Proprietary 10-102

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Usage guidelines
When a fiber span includes OTDR filters (C_xxx_OTDR) at both sides, an open (non-terminated) OTDR
tap port at the far side of the span will result in high back-reflection of the OTDR signal. The strong
back-reflected signal may be double back-reflected by the fiber splices/connectors and result in
generation of "ghost events".
This can be prevented by connecting "OTDR termination" to the open OTDR Tap ports.
The OTDR termination is supplied with the filter card installation kit, and it is highly recommended to
use it.

Ribbon Communications Inc. Proprietary 10-103

 Apollo Reference Manual OPT96xx optical cards and modules

OTDR deployment, two typical scenarios

The red circles mark the ports that should be terminated with the "OTDR termination".

Block diagram

Ribbon Communications Inc. Proprietary 10-104

 Apollo Reference Manual OPT96xx optical cards and modules

10.9.3 CT_1590_1511_OTDR
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The CT_1510_1511_OTDR is a single-slot C/T filter, in which the synchronization signal is carried on a
single TX fiber (1511.05/1511.81nm), with OSC signal carried over 1590nm and OTDR over 1610nm.

Card views
General view

Front panel

Usage guidelines
When a fiber span includes OTDR filters (C_xxx_OTDR) at both sides, an open (non-terminated) OTDR
tap port at the far side of the span will result in high back-reflection of the OTDR signal. The strong
back-reflected signal may be double back-reflected by the fiber splices/connectors and result in
generation of "ghost events".

Ribbon Communications Inc. Proprietary 10-105

 Apollo Reference Manual OPT96xx optical cards and modules

This can be prevented by connecting "OTDR termination" to the open OTDR Tap ports.
The OTDR termination is supplied with the filter card installation kit, and it is highly recommended to
use it.

OTDR deployment, two typical scenarios

The red circles mark the ports that should be terminated with the "OTDR termination".

Block diagram

Ribbon Communications Inc. Proprietary 10-106

 Apollo Reference Manual OPT96xx optical cards and modules

10.9.4 CT_1610
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The CT_1610 is a single-slot C/T filter, in which the synchronization signal is carried on a single TX
fiber (1611.93/1610.80nm). This filter is appropriate for use in situations where external filters can’t be
added at the xHRSF line input, due to the RAMAN pump.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-107

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.10 Bidirectional single-fiber DWDM networks

Most DWDM communication systems use two fibers, one for transmission and one for reception.
Although communication on a single fiber is not common, there might be cases where customers need
to connect systems with a single fiber (due to the relatively high cost of fiber deployment, or because
they need to use existing infrastructure, etc.). The following figure illustrates a typical DWDM
communication system connected with a pair of fibers. In this system we transmit the same channels in
each direction, and the 32 channels (Ch. 1 to Ch. 32) can deliver 32 services. The figure below shows a
two-fiber 32 channel system that delivers 32 services.

Two-fiber DWDM link (unamplified)

Ribbon Communications Inc. Proprietary 10-108

 Apollo Reference Manual OPT96xx optical cards and modules

In a single-fiber bidirectional DWDM communication system, half of the channels are used to transmit in
one direction, while the other half carries the traffic in the other direction. The 44 channels can deliver
22 services. The following figure illustrates a block diagram of a single-fiber bidirectional DWDM link.

Single-fiber bidirectional DWDM link (unamplified)

The following figure illustrates a typical single-fiber bidirectional DWDM link application.

Typical bidirectional DWDM link

The Blue channels are transmitted from left to right and the Red in the opposite direction. The R/B
filters separate the Blue and Red channels passing the link. Optical amplifiers compensate for the
signal loss caused by the various Mux/DeMux and filters. Two different OCS channels control the
amplifiers' operation; one at 1510 nm, and the second at 1590 nm. The CLT filters separate the traffic
(Red/Blue channels) and the OSC signals. In-Line amplifiers, as shown in the middle section, are
required only for very long spans.

Ribbon Communications Inc. Proprietary 10-109

 Apollo Reference Manual OPT96xx optical cards and modules

10.10.1 R/B_2
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The R/B_2 is a single-slot Red/Blue filter card for use in single-fiber bidirectional network applications. It
includes two different Red/Blue filters. All connections to the card are through LC type connectors on
the front panel.

Card views
R/B_2 front panel

The card incorporates two sets of different R/B filters whose ports are marked with suffix 1 or 2:
 The functions of set 1 are as follows:
 The C-band payload is delivered to/from the filter through the bidirectional port LINE 1. The
filter separates the Blue channels from the incoming signal and provides them through the
unidirectional port BLUE 1 OUT.
 The filter combines the Red channels coming in through the unidirectional port RED 1 IN with
the C-band payload and provides the resulting signal in the opposite direction via port LINE 1.
 The functions of set 2 are as follows:
 The C-band payload is delivered to/from the filter through the bidirectional port LINE 2. The
filter separates the Red channels from the incoming signal and provides them through the
unidirectional port RED 2 OUT.
 The filter combines the Blue channels coming in through the unidirectional port BLUE 2 IN
with the C-band payload and provides the resulting signal in the opposite direction via port
LINE 2.

Ribbon Communications Inc. Proprietary 10-110

 Apollo Reference Manual OPT96xx optical cards and modules

Functional block diagram

10.10.2 CLT_1510/1590
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The CLT_1510/1590 is a single-slot CLT filter card for use in bidirectional network applications. It
includes two different CLT filters. All connections to the card are through LC type connectors on the
front panel.
The CLT_1510/1590 enables to add/drop two Optical Supervisory Channels (OSCs) at 1590 nm and
1510 nm that carry management information between optical nodes in bidirectional DWDM
applications. SFP transceivers (typically combined with optical amplifiers in ILA sites) support the OSC
functions.

Ribbon Communications Inc. Proprietary 10-111

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
Front panel

Functional block diagram

Typical application

Ribbon Communications Inc. Proprietary 10-112

 Apollo Reference Manual OPT96xx optical cards and modules

10.11 Optical protection cards

Apollo hardware provides comprehensive options for protection against equipment failure. In system
applications that require protection against any type of failure, including failure of the optical fibers,
Apollo platforms can be configured with the following optical protection cards:
 OMSP (Optical Multiplexer Section Protection)
 OLP_S2 (Optical Line Protection)

10.11.1 OMSP
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X

Description
The OMSP is a single-slot card that provides multiplex section protection at the optical line level. OMSP
modules switch traffic to the protection path when a failure occurs on the main path, and vice versa.
The OMSP provides the following main features and functions:
 Low-loss fiber protection
 Real-time monitoring of protected fibers
 Bidirectional operation
 Protection switching in less than 50 msec

Ribbon Communications Inc. Proprietary 10-113

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-114

 Apollo Reference Manual OPT96xx optical cards and modules

Ports
The OMSP card consists of two sections:
 Transmit section, including:
 Input signal monitor (PD in) for monitoring the incoming signal level (received at the
COMMON IN connector).
 Pilot transmitter for generating an optical signal that enables monitoring the condition of the
protection fiber; (in the preceding figure it's the PATH-B OUT connector. However, it can also
be the PATH-A OUT, depending which is the protection path).
 Path selector, an optical switch that normally connects the incoming signal to the main fiber
(in the preceding figure it's the PATH-A OUT connector. However, it can also be the PATH-B
OUT, depending which is the main path) and the pilot signal to the protection fiber.
The connections are interchanged when the path selector changes position (see dashed lines
in the preceding figure).
 Receive section, including:
 PD1 photo diode detector for monitoring the input power signal provided to the COMMON
OUT connector from the (far end) main path; (in the preceding figure it's the PATH-A IN
connector. However, it can also be PATH-B IN, depending which is the main path).
 PD2 pilot detector for monitoring the protection fiber (in the preceding figure it's the PATH-B
IN connector. However, it can also be the PATH-A IN, depending which is the protection
path), and evaluating the pilot optical signal received from the far side.
 Path selector, an optical switch that normally connects the optical signal received through the
main fiber (in the preceding figure it's the PATH-A IN connector. However, it can also be the
PATH-B IN, depending which is the protection path) to the COMMON OUT connector and the
optical signal received through the protection fiber to the PD2 pilot detector.
The connections are interchanged when the path selector changes position (see dashed lines
in the preceding figure).

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the OLP_S2.
COMMON port LED
LOS Red LED Blinks when the input power signal is missing, or is too low for normal
operation (LOS condition). Off when the input signal is normal.
IVLD Red LED Blinks when a pilot signal is detected on the main path. This is mainly due to
a change between the Main and Protection fiber connections.
PATH port LEDs
ACT Green LED Lights steadily under the corresponding PATH port, which is selected by the
optical switch to pass the signal.
LOS Red LED Blinks when the corresponding PATH port input signal is missing or is too
low for normal operation.

Ribbon Communications Inc. Proprietary 10-115

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram
OMSP functional block diagram

10.11.1.1 OMSP typical application

The following figure shows a typical application topology for OMSP modules. For simplicity, the
figure omits the ALS functions.

OMSP typical application

During normal operation, the OMSP modules connect the signals to the main fibers while monitoring
the protection fibers via the pilot signal.

Ribbon Communications Inc. Proprietary 10-116

 Apollo Reference Manual OPT96xx optical cards and modules

In the event of a failure on one of the main fibers, the traffic is switched to the protection fibers by the
following process:
1. The signal no longer reaches the LOS detector at the receive side. This condition causes the path
selector at the corresponding side to interchange the main and protection fibers.
2. The detectors at the other side sense the interchange between the two paths as they receive the
signals on different fibers. In response, the path selector of the remote OMSP module also
switches to the protection path.
As a result, the payload paths through the whole system are restored, using the protection pair of fibers.

10.11.2 OLP_S2
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X

Description
The OLP_S2 is an Optical Line Protection (OLP) card that provides protection for two services of Apollo
DWDM networks, while increasing the network's reliability and availability in a cost-effective manner.
The card enables protection against fiber cuts, signal failures, loss of signal quality or power
degradation, and card failures at the DWDM layer and saves duplicating the network infrastructure.
The card was designed as an integrated solution for Apollo platforms that saves the use of high-cost
external OEM protection units. It protects Apollo service cards such as transponders, combiners, AoC,
and FIO cards. The card occupies one slot in the platforms. The OLP_S2 is intended to work with SM
(Single Mode) fibers.
In a protection mechanism a single failure may trigger multiple recovery mechanisms, which may
interact with each other, and cause the protection switching respond to non-stable network states. To
prevent this, a hold-off timer is used. The timer is used by underlying traffic layers to filter out non-stable
link faults.
The OLP_S2 has a configurable hold-off timer that can be provisioned by the user according to the
card/service it is protecting.
The hold-off timer is activated when one or more defect conditions are detected in the protection group,
and it runs for a provisioned period. When the time interval of the timer expires, the fault status of all
traffic signals is passed to the protection switching process to act upon them.
The OLP_S2 provides the following main features and functions:
 1 + 1 protection of two services for optical line and client.
 Service protection for all Apollo service cards with OTUk ports.
 Fiber protection for all Apollo optic cards with DWDM OTS ports. Useful in cases where pilot tone
is not required and/or using unidirectional protection.
 Protection switching in less than 50 msec.
 Ability to configure protection reversion. By default it is a non-reversion protection.
 Ability to configure hold-off timer values. By default its value is 0 seconds.
 Metro and long-haul traffic protection.

Ribbon Communications Inc. Proprietary 10-117

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Usage guidelines
OLP_S2 protection capabilities include:
 (1+1) service protection on network ports (i.e. OTUk)
 (1+1) fiber protection on DWDM ports
 (1+1) service protection on non OTUk ports (using non-colored transceivers)
 (1+1) service protection on non-OTUk ports (using colored transceivers)

Ribbon Communications Inc. Proprietary 10-118

 Apollo Reference Manual OPT96xx optical cards and modules

Triggers for protection

Protection type Triggers for protection

Service protection on network ports (OTUk ports) LOS signal
Fiber protection  LOS signal
 SF
(1+1) service protection on non OTUk ports (using non- LOS signal
colored transceivers)
(1+1) service protection on non-OTUk ports (using colored LOS signal
transceivers)

Port configurable LOS threshold

Protection type Common ports Path ports

Service protection (OTUk ports) -11 dBm -31 to -21 dBm
Default value:-21 dBm
Service protection on non-OTUk -11 dBm -31 to -21 dBm
ports with colored transceivers Default value: -21 dBm
Fiber protection -30 to 0 dBm -33 to -24 dBm
Default value: -5 dBm Default value:-30 dBm
Service protection on non-OTUk -30 to-15 dBm -30 to-15 dBm
ports w/o colored transceivers Default value=-25 dBm Default value=-25 dBm

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off when
the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the OLP_S2.
COMMON port LED
LOS Red LED Blinks when the input power signal is missing, or is too low for normal
operation (LOS condition). Off when the input signal is normal.
PATH port LEDs
ACT Green LED Lights steadily under the corresponding PATH port, which is selected by the
optical switch to pass the signal.
LOS Red LED Blinks when the corresponding PATH port input signal is missing or is too low
for normal operation.

Ribbon Communications Inc. Proprietary 10-119

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.12 Optical amplifiers

As optical signals are attenuated by the fiber through which they travel, the signal can drop to power
levels below the sensitivity of the optical receiver at the other end. Before this occurs, the signal must
be regenerated. In the past this regeneration was performed exclusively using
optical-to-electrical-to-optical (OEO) transceivers. But since the development of the Optical Fiber
Amplifier (OFA), amplification can be performed more cost effectively in the optical domain, without
expensive conversion to and back from the electrical domain.
Apollo platforms offer a large variety of EDFAs and Raman amplifiers to suit any need and application,
such as:
 Amplified metro core DWDM networks.
 Regional and long-haul DWDM networks.
 Repeaterless undersea DWDM networks.
Apollo supports dynamic variable and fixed gain amplifiers. The variable gain EDFAs are typically used
in regional and long-haul networks. Using dynamic EDFA technology, these amplifiers automatically
adjust themselves to the attenuation of the fiber span for which they are compensating, providing
optimized amplification over the entire spectral band. By maintaining an optimal OSNR at the output of
each amplifier, far longer spans and many more amplifiers can be cascaded, resulting in an OSNR that
is sufficiently high for clear reception at the end of the link. This capability is essential in real world
regional and long-haul optical networks, where the fiber spans between amplifier sites vary in length
and attenuation. As a result, fewer spare amplifiers are needed.
Along with the ability to provide the correct gain at each site while maintaining flat amplification and
optimal OSNR, the two-stage amplifiers include midstage access optimized for DCF integration that
does not affect the link power budget.
Fixed gain amplifiers are offered as a low-cost alternative for specific configuration requirements, such
as a booster after ROADM nodes.

Ribbon Communications Inc. Proprietary 10-120

 Apollo Reference Manual OPT96xx optical cards and modules

Several safety mechanisms are implemented in the optical amplifier cards to prevent human-eye
exposure to dangerous laser light.

10.12.1 Raman amplification: Principles of operation

Raman amplification is based on a nonlinear effect that uses the fiber itself as the amplification
medium: by driving the payload-carrying fiber with a very strong optical signal (called pump signal)
having a wavelength approximately 100 nm lower than the payload wavelength, the loss incurred by the
payload signal is significantly decreased.
By selecting an appropriate combination of pump signals, the Raman gain can be made available over
the full C band, and even at the T/OSC band used by the OSC (which uses a wavelength of 1510/1528
nm).
The Raman gain (that is, the difference between the signal levels received at the remote end with and
without a pump signal) depends on the pump signal power, attenuation per km, and the length and type
of the fiber. (Another factor is the fiber cross-sectional area, but this parameter is highly standardized.)
Thus, the Raman effect is optimal for long spans of fiber with low attenuation per km.
The fiber characteristics affect the actual Raman gain used for signal amplification. Therefore, the pump
power of the distributed Raman amplifiers (DRAs) must be adjusted accordingly, adapted to the actual
fiber properties in order to provide accurate automatic gain control. The relevant cards should be
calibrated after first installation and during subsequent maintenance periods.

NOTE: Fiber discontinuities, such as those caused by sharp bends, improper splicing, and
so on, have a negative effect on the achievable gain. Therefore, discontinuities must
carefully be avoided.

The maximum pump power that can be used is influenced by safety considerations and not only by
component limitations (the pump signal remains at Hazard Level 3B for many kilometers, and special
precautions are needed to protect personnel in case the fiber is cut or disconnected at a remote
location).

10.12.2 High power laser safety

The OA_HRS, OA_HRSF, and OA_USPBF amplifiers are designed to ensure that all optical power is
confined to the fiber during normal operation. Also, when optical connectors are opened, the optical
power is limited. Therefore, they are defined as a Class 1M Laser Product.
Special precautions have been taken to meet the safety requirements. These include physical
protection for the LINE connector and a safety subsystem.
The OA_HRS, OA_HRSF, and OA_USPBF amplifiers transmit high-power signals (up to 0.4/0.7 W) into
the fiber. These power levels correspond to a potential Hazard Level 3B, however, the inherent
protection mechanisms reduces the Hazard Level to 1M. During installation and maintenance it may be
required to bypass the protection mechanisms. In such case, personnel handling the card must use
Fiber Telecom protection optical goggles. Moreover, all personnel must pass laser safety training in
accordance with standard IEC 60825 (AS/NZS 2211.2) before being allowed to install and maintain
these amplifiers and systems including them. For detailed safety requirements, see the Apollo
Installation, Operation, and Maintenance Manual.

Ribbon Communications Inc. Proprietary 10-121

 Apollo Reference Manual OPT96xx optical cards and modules

The following special precautions have been taken:

 The high-power LINE output connector is located behind a special cover and is therefore not
visible. Moreover, a special interlock mechanism detects the opening of the connector and
automatically turns the laser pumps off, even when transmission is enabled.
 A special safety subsystem ensures that the high-power laser signals are confined to the fiber.
During transmission this subsystem continuously monitors and analyzes various optical
parameters, for example, input signal levels, back reflection, and supervisory channel signal. It is
therefore capable of detecting fiber disconnections and fiber cuts, even when they occur many
kilometers from the card's location. In these cases, the safety subsystem automatically turns the
card's laser pumps off. After the safety subsystem is activated, normal operation is automatically
resumed once normal conditions have been restored by the management system.
The signal sent to the line is always monitored, and an alarm is generated whenever its power is too
low or too high.
The other monitored signals that result in safety subsystem activation are:
 High back reflection from the LINE connector
 Loss of OSC1510/OSC1528 signal (OA_HRS, OA_HRSF)

10.12.3 Automatic laser shutdown (ALS)

The OA_FHBS, OA_MHS, and OA_USPBF cards support ALS. In the event of a fiber break, ALS stops
the transmission of the signal. This minimizes information loss and leads to greater safety by minimizing
the laser light leakage.
ALS requires a pair of OA_FHBS/OA_MHS/OA_USPBF amplifiers at either end of a span. The
following figure shows an example of ALS functionality with an OA_FHBS.

Automatic laser shutdown example

Switching to ALS mode

(1) A fiber cut on the span causes LOS at the express input PD (2) in the right OA_FHBS. The right
card shuts down the transmission (3), causing LOS at express input PD (4) in the left OA_FHBS. The
left-hand OA_FHBS (5) shuts down, which enables full ALS.
Transition to ALS mode creates the following results:
 The EDFA module is disabled.
 The EDFA/Booster configuration is modified to AGC mode with a limited output of 20 dBm.
 The ALS LED turns on.

Ribbon Communications Inc. Proprietary 10-122

 Apollo Reference Manual OPT96xx optical cards and modules

Restarting from ALS mode

The EDFA is disabled while in ALS mode. Once every three minutes, the EDFA is enabled for 30
seconds, during which it transmits in AGC mode with output power (20 dBm) lower than the Hazard
Level 1M. If “pass-through” LOS is cleared, the EDFA is enabled (still with a 20 dBm output limit). If
LOS is cleared for more than 40 seconds, ALS mode is removed and the card returns to its previous
normal operation mode with the following results:
 Enabling the EDFA module.
 Modifying the EDFA configuration back to its last operation state (with the last normal Gain and
Tilt values).
 The ALS LED turns off.

NOTE: When an OA_FHBS/OA_MHS/OA_USPBF card is reset, the EDFA card begins in

ALS mode.

10.12.4 OA_PA
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_PA is a fixed gain EDFA-based amplifier optimized as a preamplifier for metro applications.
The card occupies one slot in the platforms.
The OA_PA amplifier operates at a very specific gain value, maintaining a fixed ratio between input and
output power to provide flat amplification. To achieve this, the OA_PA uses a built-in VOA to
automatically adjust the fiber span loss it is compensating for to its optimized gain value. This VOA
lowers the channel power at the input of the amplifier, thereby degrading the OSNR at the output of the
amplifier.

Functions
 Optical amplification (power and gain control)
 Transients suppression
 Output power monitoring point
 High sensitivity
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Back-reflection (BR) detection mechanism
 Monitoring and alarms
 1510 nm SFP for OSC channel (optional)

Ribbon Communications Inc. Proprietary 10-123

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

NOTE: The EDFA amplifier LED markings are indicated in a rectangle at the lower left
side of the front panel.

Ribbon Communications Inc. Proprietary 10-124

 Apollo Reference Manual OPT96xx optical cards and modules

Ports
Port name Connector Function
AMP IN LC Amplifier line input connector
AMP OUT LC Amplifier output connector
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides an -20 dB sample from the amplifier output signal.
OSC SFP To house an optional 1510 nm SFP that provides an FE control
communications channel.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault
EDFA LEDs
IN Red LED Blinks when the input power signal is missing or is too low for normal
operation (LOS condition). Off when the input signal is normal.
OUT Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually this
indicates a disconnection or break in the fiber connected to the AMP
OUT connector.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Block diagram

Ribbon Communications Inc. Proprietary 10-125

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.5 OA_FB
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_FB is a fixed gain EDFA-based amplifier optimized as a power booster for terminal and
ROADM sites with up to 88 DWDM channels. The card occupies one slot in the platforms.
In addition to the standard amplifier mode, the OA_FB can work in two other modes:
 Automatic Power Control (APC) mode, for Noise Generator applications, intended to support to
support third parties requirements. In APC mode, the amplifier pumps are turned on although
there is no input signal. Such operation mode leads to generation of strong ASE (amplified
spontaneous emission) noise at the amplifier output, thereby turning the amplifier into a noise
source.
 Automatic Current Control (ACC) mode, optimized to work in optical supervisory channel (OSC)
signal amplifier application for the OA_HRSF. Generally, the OA_HRSF is used to amplify optical
signals on ultra-high spans. The OSC has also to reach the end of these spans with adequate
power. However, this signal is significantly attenuated when traversing such distances. The
solution is to amplify the OSC to the required level. The OA_FB-R is used for this application.
In its regular operation an optical amplifier determines the gain by sampling the input and the
output signals and calculating the required amplification according to the average. Because the
OSC control signal operates at a relatively low rate (2 Mpbs, 5 Mbps, 100 Mbps) the sampling
photo-diodes will provide mistaken results. To overcome this problem, the OA_FB is operated in
an ACC mode, in which the pump current is automatically controlled. In addition, each amplifier
gain is checked at manufacturing to make sure it provides the required gain.
The OA_FB amplifier operates at a very specific gain value, maintaining a fixed ratio between input and
output power to provide flat amplification. To achieve this, the OA_FB uses a built-in VOA to
automatically adjust the fiber span loss it is compensating for to its optimized gain value. This VOA
lowers the channel power at the input of the amplifier, thereby degrading the OSNR at the output of the
amplifier.

Functions
 Optical amplification (power and gain control)
 Transient suppression
 Output power monitoring point
 High output power
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 BR detection mechanism
 Monitoring and alarms
 1510 nm SFP for OSC channel (optional)

Ribbon Communications Inc. Proprietary 10-126

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

NOTE: The EDFA amplifier LED markings are indicated in a rectangle at the lower left
side of the front panel.

Ports
Port name Connector Function
AMP IN LC Amplifier line input connector
AMP OUT LC Amplifier output connector
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides an -20 dB sample from the amplifier output signal.
OSC SFP To house an optional 1510 nm SFP that provides an FE control
communications channel.

Ribbon Communications Inc. Proprietary 10-127

Apollo Reference Manual OPT96xx optical cards and modules

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault
EDFA LEDs
IN Red LED Blinks when the input power signal is missing or is too low for normal
operation (LOS condition). Off when the input signal is normal.
OUT Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually this
indicates a disconnection or break in the fiber connected to the AMP
OUT connector.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Block diagram

Ribbon Communications Inc. Proprietary 10-128

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.6 OA_M
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_M is a variable gain EDFA-based amplifier with MSA, optimized for high gain spans before In-
Line and ROADM sites in Regional/LH applications supporting up to 88 DWDM channels. The card
occupies one slot in the platforms.
The OA_M has variable gain control and high output power (+20.5 dBm). Considering its multistage
design which enables the insertion of a dispersion compensation unit without affecting the link optical
budget, the OA_M is especially suited for long-haul applications. High channel count DWDM networks
with a reach of beyond 1500 km without OEO regeneration are possible.
The OA_M amplifier gain can be adjusted without using VOA, thereby maintaining optimal OSNR for
any fiber span length. In addition, the OA_M has a higher output power, which means that fewer
amplifiers are needed.
The OA_M amplifier structure is very similar to the OA_ML; for a detailed description of the signal path
in the amplifier see OA_ML Functional Description.

Functions
 Optical amplification (power and gain control)
 Transient suppression
 Output power monitoring point
 Two amplification stages
 Midstage for connecting a dispersion compensation unit
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 BR detection mechanism
 Monitoring and alarms
 1510 nm SFP for OSC channel (optional)

Ribbon Communications Inc. Proprietary 10-129

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

.
Front panel

Ribbon Communications Inc. Proprietary 10-130

Apollo Reference Manual OPT96xx optical cards and modules

Ports
Port name Connector Function
AMP IN LC
Amplifier external line input connector that is also the input to the
1st.stage.
MID STAGE LC
OUT Output from the 1st stage.
MID STAGE IN LC
Input to the 2nd stage
AMP OUT LC
Amplifier external line output connector that is also the output from
the 2nd stage.
MON OUT - LC
20dB Monitor connector used to connect test equipment (like OPM or
OSA); provides an -20 dB sample from the amplifier output signal.

OSC SFP To house an optional 1510 nm SFP that provides an FE control

communication channel.

NOTE: The EDFA amplifier LED markings are indicated in a rectangle at the lower left
side of the front panel.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the OA_ML.
EDFA LEDs
IN Red LED Blinks when the input power signal is missing, or is too low for normal
operation (LOS condition). Off when the input signal is normal.
OUT Green LED Lights steadily when the pump laser is on and the output power is above
the preset threshold. Off when the output power is below the threshold
(LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually this
indicates a disconnection or break in the fiber connected to the AMP OUT
connector.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Ribbon Communications Inc. Proprietary 10-131

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

The OA_ML consists of two amplification stages with separate input and output connectors. It is
therefore possible to insert optical components between the MID-STAGE OUT and MID-STAGE IN
connectors (this is referred to as “the midstage”). The high power second (output) stage is located at
the middle of the card.
The external input line is connected to the AMP IN connector, and the external output line is connected
to the AMP OUT connector. The output power of the second stage can be monitored at the MON -20
dB connector.
The advantages of this capability are evident in many typical applications. For example, when the
OA_ML is used as an inline amplifier in a long-haul network, a dispersion compensation device can be
inserted in the midstage to compensate for the chromatic dispersion of the fiber span.

10.12.7 OA_ML
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_ML is a variable gain EDFA-based amplifier with-mid stage access (MSA), optimized for low
gain spans before In-Line and ROADM sites in Regional/LH applications with up to 88 DWDM
channels. The card occupies one slot in the platforms.
The OA_ML has variable gain control and high output power (+20.5 dBm). Considering its multistage
design that enables the insertion of a dispersion compensation unit (DCF) without affecting the link
optical budget, the OA_ML is especially suited for long-haul applications. High channel count DWDM
networks with a reach of beyond 1500 km without OEO regeneration are possible.
The OA_ML amplifier gain can be adjusted without using VOA, thereby maintaining optimal OSNR for
any fiber span length. In addition, it has a higher output power, which means that fewer amplifiers are
needed.

Functions
 Optical amplification (power and gain control)
 Transient suppression
 Output power monitoring point

Ribbon Communications Inc. Proprietary 10-132

 Apollo Reference Manual OPT96xx optical cards and modules

 Two amplification stages

 Mid-stage for connecting a dispersion compensation unit
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 BR detection mechanism
 Monitoring and alarms
 1510 nm SFP for OSC channel (optional)

Card Views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-133

Apollo Reference Manual OPT96xx optical cards and modules

Ports

Port name Connector Function

AMP IN LC
Amplifier external line input connector that is also the input to the
1st.stage.
MID STAGE LC
OUT Output from the 1st stage.
MID STAGE IN LC
Input to the 2nd stage
AMP OUT LC
Amplifier external line output connector that is also the output from
the 2nd stage.
MON OUT - LC
20dB Monitor connector used to connect test equipment (like OPM or
OSA); provides an -20 dB sample from the amplifier output signal.

OSC SFP To house an optional 1510 nm SFP that provides an FE control

communication channel.

NOTE: The EDFA amplifier LED markings are indicated in a rectangle at the lower left
side of the front panel.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the OA_ML.
EDFA LEDs
IN Red LED Blinks when the input power signal is missing, or is too low for normal
operation (LOS condition). Off when the input signal is normal.
OUT Green LED Lights steadily when the pump laser is on and the output power is above
the preset threshold. Off when the output power is below the threshold
(LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually this
indicates a disconnection or break in the fiber connected to the AMP OUT
connector.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Ribbon Communications Inc. Proprietary 10-134

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

The OA_ML consists of two amplification stages with separate input and output connectors. It is
therefore possible to insert optical components between the MID-STAGE OUT and MID-STAGE IN
connectors (this is referred to as “the midstage”). The high power second (output) stage is located at
the middle of the card.
The external input line is connected to the AMP IN connector, and the external output line is connected
to the AMP OUT connector. The output power of the second stage can be monitored at the MON -20
dB connector.
The advantages of this capability are evident in many typical applications. For example, when the
OA_ML is used as an inline amplifier in a long-haul network, a dispersion compensation device can be
inserted in the midstage to compensate for the chromatic dispersion of the fiber span.

10.12.8 OA_L
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_L is a variable gain single-stage EDFA optimized for medium gain spans in coherent networks
applications. The EDFA is supporting up to 88 DWDM channels. The card occupies one slot in the
platforms.
The OA_L is an EDFA optimized for coherent networks that do not require DCF support.
The OA_L amplifier structure is very similar to the OA_FB and OA_PA; for a detailed description of the
signal path in the amplifier see OA_PA and OA_FB.

Functions
 Variable gain optical amplification (15-28 dB)
 High output power (20.5 dBm)
 Transient suppression
 Output power monitoring point
 Single amplification stage

Ribbon Communications Inc. Proprietary 10-135

 Apollo Reference Manual OPT96xx optical cards and modules

 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 BR detection mechanism
 Monitoring and alarms
 1510 nm SFP for OSC channel (optional)

Card views
General view

Front panel

NOTE: The EDFA amplifier LED markings are indicated in a rectangle at the lower left
side of the front panel.

Ports
Port name Connector Function
AMP IN LC Amplifier line input connector
AMP OUT LC Amplifier output connector
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides an -20 dB sample from the amplifier output signal.
OSC SFP To house an optional 1510 nm SFP that provides an FE control
communications channel.

Ribbon Communications Inc. Proprietary 10-136

Apollo Reference Manual OPT96xx optical cards and modules

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault
EDFA LEDs
IN Red LED Blinks when the input power signal is missing or is too low for normal
operation (LOS condition). Off when the input signal is normal.
OUT Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually this
indicates a disconnection or break in the fiber connected to the AMP
OUT connector.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Block diagram

10.12.9 OA_LF
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X

Ribbon Communications Inc. Proprietary 10-137

 Apollo Reference Manual OPT96xx optical cards and modules

Description
The OA_LF is a variable gain single-stage EDFA optimized as an ILA for coherent networks with short
span applications. The amplifier supports up to 96 DWDM channels in the extended C-Band. The card
occupies one slot in the platforms and in addition to ILA can also be utilized in Booster or Preamp
applications.
The OA_LF is an EDFA optimized for coherent networks that do not require DCF support.
The OA_LF amplifier structure is very similar to the OA_L; for a detailed description of the signal path in
the amplifier see OA_L.

Functions
 Variable gain optical amplification (15-28 dB)
 High output power (20.5 dBm)
 Transient suppression
 Output power monitoring point
 Single amplification stage
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 BR detection mechanism
 Monitoring and alarms
 1510 nm SFP for OSC channel (optional)

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-138

 Apollo Reference Manual OPT96xx optical cards and modules

NOTE: The EDFA amplifier LED markings are indicated in a rectangle at the lower left
side of the front panel.

Ports
Port name Connector Function
AMP IN LC Amplifier line input connector
AMP OUT LC Amplifier output connector
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides an -20 dB sample from the amplifier output signal.
OSC SFP To house an optional 1510 nm SFP that provides an FE control
communications channel.

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault
EDFA LEDs
IN Red LED Blinks when the input power signal is missing or is too low for normal
operation (LOS condition). Off when the input signal is normal.
OUT Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually this
indicates a disconnection or break in the fiber connected to the AMP
OUT connector.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Block diagram

Ribbon Communications Inc. Proprietary 10-139

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.10 OA_HF
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_HF is a variable gain single-stage EDFA optimized as an ILA for coherent networks with long
span applications. The amplifier supports up to 96 DWDM channels in the extended-C-Band. The card
occupies one slot in the platforms and in addition to ILA can also be utilized in Preamp applications.
The OA_HF is an EDFA optimized for coherent networks that do not require DCF support.
The OA_HF amplifier structure is very similar to the OA_M but without the midstage; for a detailed
description of the signal path in the amplifier see OA_M.

Functions
 Variable gain optical amplification (25-37 dB)
 High output power (20.5 dBm)
 Transient suppression
 Output power monitoring point
 Single amplification stage
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 BR detection mechanism
 Monitoring and alarms
 1510 nm SFP for OSC channel (optional)

Card views
General view

Ribbon Communications Inc. Proprietary 10-140

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

NOTE: The EDFA amplifier LED markings are indicated in a rectangle at the lower left
side of the front panel.

Ports

Port name Connector Function

AMP IN LC Amplifier line input connector
AMP OUT LC Amplifier output connector
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides an -20 dB sample from the amplifier output signal.
OSC SFP To house an optional 1510 nm SFP that provides an FE control
communications channel.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault
EDFA LEDs
IN Red LED Blinks when the input power signal is missing or is too low for normal
operation (LOS condition). Off when the input signal is normal.
OUT Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually this
indicates a disconnection or break in the fiber connected to the AMP
OUT connector.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Ribbon Communications Inc. Proprietary 10-141

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.12.11 OA_HFS
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_HFS is a high power variable gain EDFA-based single-slot amplifier, optimized for coherent
networks, which can be used as a booster after ROADM/MXD or ILA modules. The OA_HFS amplifier
is designed for terminal and ROADM sites in E/W configuration, supporting up to 96 DWDM channels,
and including built-in OSC C/T filters. The OA_HFS includes extended tilt support for (future) L-band
integration in 5G networks.
This is the first high power amplifier that can be used as a ROADM pre-amp. To ensure eye safety, the
OA_HFS includes both automatic and manual eye safety mechanisms. If there is a disconnection at
any point in the fiber connecting the pre-amp to the ROADM, the module immediately shuts itself off.

Functions
 Variable gain optical amplification (20-35 dB) with automatic gain control
 High output power (23 dBm)
 ROADM pre-amp functionality
 Automatic eye-safety verification
 Transient suppression
 Output power monitoring point
 Single amplification stage
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 BR detection mechanism
 Monitoring and alarms
 1510 nm SFP for OSC channel (optional)
 Mechanisms for ensuring eye-safety (Class 1M):
 Spring-loaded protective cover on the amplifier output connector

Ribbon Communications Inc. Proprietary 10-142

 Apollo Reference Manual OPT96xx optical cards and modules

 BR detection
 LOS of signal detection from the far end
 Automatic laser shutdown (ALS)
 Automatic power reduction (APR)
 Built-in C/T filters to support OSC functionality
 Monitoring and alarms
 1510 nm SFP for OSC channel (optional)

Card views
General view

The OA_HFS is an E/W configured card designed to provide enhanced ALS and APR function to shut
down the amplifier in case of fiber cut. The “LINE IN” (Express In) and “EXP OUT” ports are connected
to one of the fiber directions. An internal photo-diode (PD) on the connection between these ports
facilitates the ALS function; see Automatic laser shutdown.

Front panel

NOTE: The EDFA amplifier LED markings are indicated in a rectangle at the lower left
side of the front panel.

Ribbon Communications Inc. Proprietary 10-143

 Apollo Reference Manual OPT96xx optical cards and modules

Ports

Port name Connector Function

AMP IN LC Amplifier external line input connector that is also the input to the 1st
stage.
EXP OUT LC Express output signal after the PD (fiber cut detection).
MON OUT LC Monitor connector used to connect test equipment (like OPM or OSA);
-20dB provides a -20 dB sample from the amplifier output signal.
OSC 1510 IN LC OSC input signal connector from built-in C/T filter.
OSC 1510 OUT LC OSC output signal connector to built-in C/T filter.
OSC SFP To house an optional 1510 nm SFP that provides an FE control
communications channel.
LINE IN LX.5 Line input fiber connector located behind spring loaded cover for safety.
LINE OUT LX.5 Line output fiber connector located behind spring loaded cover for
safety.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault
EDFA LEDs
AMP IN Red LED Blinks when the input power signal is missing or is too low for normal
operation (LOS condition). Off when the input signal is normal.
OUT Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually this
indicates a disconnection or break in the fiber connected to the AMP
OUT connector.
ALS Orange LED Lights steadily when the card is in ALS state.
LINE LOS Red LED Lights steadily when the signal on the return line (fiber) is missing;
usually indicates a fiber cut.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Ribbon Communications Inc. Proprietary 10-144

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.12.12 OA_FHBS
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_FHBS is a high power fixed gain EDFA-based amplifier optimized for terminal and ROADM
sites in E/W configuration supporting up to 88 DWDM channels. For safety reasons the OA_FHBS is
designed to operate in E/W configuration, and it includes built-in C/T filters. The card occupies one slot
in the platforms.

Functions
 Optical amplification (power and gain control)
 Transient suppression
 Output power monitoring point
 Mechanisms for ensuring eye-safety:
 Spring-loaded protective cover on the amplifier output connector
 BR detection
 LOS of signal detection from the far end
 Automatic Laser Shutdown (ALS)
 Built-in C/T filters to support OSC functionality

Ribbon Communications Inc. Proprietary 10-145

 Apollo Reference Manual OPT96xx optical cards and modules

 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Monitoring and alarms
 1510 nm SFP for OSC channel (optional)

Card views
General view

The OA_FHBS is an E/W configured card designed to provide enhanced ALS function to shut down the
amplifier in case of fiber cut. The “LINE IN” (Express In) and “EXP OUT” ports are connected to one of
the fiber directions. An internal photo-diode (PD) on the connection between these ports facilitates the
ALS function; see Automatic laser shutdown.

Front panel

Ribbon Communications Inc. Proprietary 10-146

 Apollo Reference Manual OPT96xx optical cards and modules

Ports

Port name Connector Function

AMP IN LC Amplifier external line input connector that is also the input to the
1st.stage.
EXPOUT LC Express output signal after the PD (fiber cut detection)
OSC 1510 IN LC OSC input signal connector from built-in C/T filter
OSC 1510 OUT LC OSC output signal connector to built-in C/T filter
AMP OUT LC Amplifier external line output connector that is also the output from the
2nd stage.
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides an -20 dB sample from the amplifier output signal.
OSC SFP To house an optional 1510 nm SFP that provides an FE control
communication channel.
LINE IN LX Return line fiber connector located behind spring loaded cover for
safety
AMP OUT LX Amplifier output connector located behind spring loaded cover for safety

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the OA_FHBS.
EDFA LEDs
IN Red LED Blinks when the input power signal is missing, or is too low for normal
operation (LOS condition). Off when the input signal is normal.
OUT Green LED Lights steadily when the pump laser is on and the output power is above
the preset threshold. Off when the output power is below the threshold
(LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually, this
indicates a disconnection or break in the fiber connected to the AMP OUT
connector.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing, or is too low for normal
operation. Lights when a fault is detected in the OSC path.
LINE LEDs
LOS Red LED Lights steadily when the signal on the return line (fiber) is missing. This
usually indicates a fiber cut.
ALS Orange LED Lights steadily when the card is in ALS state.

Ribbon Communications Inc. Proprietary 10-147

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.12.13 OA_MHS
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_MHS is a high power variable gain EDFA-based amplifier with MSA, optimized for in-line sites
in regional/LH applications, E/W configuration supporting up to 88 DWDM channels. For safety reasons
the OA_MHS is designed to operate in E/W configurations and it includes built-in C/T filters. The card
occupies one slot in the platforms.
he OA_MHS is an E/W configured card designed to provide enhanced ALS function to shut down the
amplifier in case of fiber cut. The “LINE IN” (Express In) and “EXP OUT” ports are connected to one of
the fiber directions. An internal photo-diode (PD) on the connection between these ports facilitates the
ALS function; see Automatic laser shutdown.

Functions
 Optical amplification (power and gain control)
 Transient suppression
 Output power monitoring point
 Two amplification stages
 Midstage for connecting a dispersion compensation unit

Ribbon Communications Inc. Proprietary 10-148

 Apollo Reference Manual OPT96xx optical cards and modules

 Mechanisms for ensuring eye safety:

 Spring-loaded protective cover on the amplifier output connector
 BR detection
 LOS detection from the far end
 ALS
 Built-in C/T filters to support OSC functionality
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Monitoring and alarms
 1510 nm SFP for OSC channel (optional)

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-149

Apollo Reference Manual OPT96xx optical cards and modules

Ports

Port name Connector Function

AMP IN LC Amplifier line input connector
EXPOUT LC Express output signal after the PD (fiber cut detection)
OSC 1510 IN: LC OSC input signal connector from built-in C/T filter
OSC 1510 OUT: LC OSC output signal connector to built-in C/T filter
MID-STAGE LC Output from the 1st stage.
OUT
MID-STAGE IN: LC Input to the 2nd stage.
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides an -20 dB sample from the amplifier output signal.
OSC SFP To house an optional 1510 nm SFP that provides an FE control
communication channel.
LINE IN (EXP LX.5 Far end fiber connector (fiber cut detection) located behind spring
IN) loaded cover
AMP OUT (LINE LX.5 Amplifier output connector located behind spring loaded cover
OUT)

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the OA_FHBS.
EDFA LEDs
IN Red LED Blinks when the input power signal is missing, or is too low for normal
operation (LOS condition). Off when the input signal is normal.
OUT Green LED Lights steadily when the pump laser is on and the output power is above
the preset threshold. Off when the output power is below the threshold
(LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually, this
indicates a disconnection or break in the fiber connected to the AMP OUT
connector.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing, or is too low for normal
operation. Lights when a fault is detected in the OSC path.
LINE LEDs
LOS Red LED Lights steadily when the signal on the return line (fiber) is missing. This
usually indicates a fiber cut.
ALS Orange LED Lights steadily when the card is in ALS state.

Ribbon Communications Inc. Proprietary 10-150

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.14 OA_HRS
Supported platforms
 OPT9624
 OPT9608

Description
The OA_HRS is a Raman optical amplifier especially optimized for long-haul multispan and undersea
applications. OA_HRS is intended for use in conjunction with EDFA amplifiers over G.652, G.654, and
G.655 fibers. It supports multichannel applications capable of amplifying the entire C band, and also
transports the OSC at 1510 nm. For safety reasons the OA_HRS is designed to operate in E/W
configurations and it includes built-in C/T filters. The OA_HRS card occupies a double-wide I/O slot in
Apollo platforms.
The OA_HRS operates in the backward mode. The mode indicates the direction of signal flow relative
to the amplifier line side. Backward mode means that the OA_HRS is located at the receiving end of an
optical span to provide an effect similar to that of using a low noise figure preamplifier before further
amplifying the low-level signals received from the line (C band and OSC) by an EDFA amplifier.
For additional safety information, see Raman amplification principles of operation and High power laser
safety.

Functions
 Raman amplification (power and gain control)
 Transient suppression
 Output power monitoring point
 Mechanisms for ensuring eye-safety:
 Spring-loaded protective covers on connectors carrying high power signals
 BR detection
 LOS detection from the far end
 ALS
 Built-in C/T filters to support OSC functionality
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Monitoring and alarms
 1510 nm SFP for OSC channel

Ribbon Communications Inc. Proprietary 10-151

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

OA_HRS front panel

Ribbon Communications Inc. Proprietary 10-152

Apollo Reference Manual OPT96xx optical cards and modules

Ports
Port name Connector Function
NODE IN LX.5 Connects to a booster amplifier output to the line. This signal passes
through the unit and connects to the LINE OUT connector. Connector is
located behind spring loaded cover for safety
NODE OUT LX.5 Connects the Raman amplifier output to an EDFA amplifier. Connector
is located behind spring loaded cover for safety
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides an -20 dB sample from the Raman amplifier output signal
LINE IN (PUMP E2000 Connects the pump signal output to the line and the line signal to the
OUT) Raman input. Connector is located behind spring loaded cover for
safety
LINE OUT E2000 Connects the line output signal (typically comes from a booster
amplifier). Connector located behind spring loaded cover for safety
OSC 1510 IN LC For connecting the input 1510 nm supervisory channel
OSC 1510 OUT LC For connecting the input 1510 nm supervisory channel
OTDR ACCESS LC For connecting an OTDR device to test the characteristics of the line
fiber

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the OA_HRS.
LINE LEDs
BR Orange LED Lights when the level of BR signal exceeds the preset threshold. Usually,
this indicates a disconnection or break in the fiber connected to the NODE
connector.
RAMAN ON Green LED Lights when laser power is transmitted through the line port (power source
may be the OA_HRS and/or the EDFA amplifier).
OSC LOS Red LED Blinks when the 1510 nm OSC signal is missing or below the preset
threshold.
LINE LOS Red LED Blinks when the signal on the line (fiber) is missing or under the preset
threshold. This usually indicates a fiber cut.
NODE LED
NODE LOS Red LED Blinks when the signal arriving from the node (normally connected to a
booster amplifier) is missing or under the preset threshold.
OSC2M LEDs
Tx Green LED Lights steadily when the OSC2M laser transmits.
F/L Red LED Blinks when the OSC2M input signal is missing, or is too low for normal
operation. Lights when a fault is detected in the OSC2M path.

Ribbon Communications Inc. Proprietary 10-153

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.15 OA_EHRS
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_EHRS is a hybrid Raman/EDFA optical amplifier, providing optimized high dynamic gain (23 to
37 dB), designed for DCF-less coherent networks. It combines a distributed low-noise Raman
amplification and high-power EDFA amplification in a single module, providing low-noise figure, wide
gain, and high output power, while improving the system OSNR. The OA_EHRS is intended for use
over G.652, G.654, and G.655 fibers. It supports multichannel applications capable of amplifying the
entire C band, and also transmits the OSC on 1528 nm (ITU-T Ch. 62). For safety reasons the
OA_EHRS is designed to operate in E/W configurations and it includes special built-in C/T filters and
OSC SFP (1528 nm) that provide an enhanced safety mechanism and enable controlled Raman
operation. The OA_EHRS card occupies a double I/O slot in Apollo platforms.
The Raman section of the OA_EHRS operates in the backward mode. The mode indicates the direction
of signal flow relative to the amplifier line side. Backward mode means that the Raman pumps of the
OA_EHRS are located at the receiving end of an optical span to provide an effect similar to that of
using a low noise figure preamplifier before further amplifying the low-level signals received from the
line (C band and OSC) by the EDFA section of the OA_EHRS amplifier.
To ensure high reliability, the connectivity of the Raman amplifier output pump to the fibers is first
checked, before full output power is allowed, using built-in special software commands.

Functions
 Combines a Backward Raman amplification and an Erbium-based amplification in a single module
 Low NF (Noise Figure) across the entire C-Band
 High dynamic gain (23 to 37 dB)
 High output power (up to 20.5 dB ambient suppression
 Gain and tilt control
 Output power monitoring point
 Built-in SFP OSC operating on 1528 nm (ITU-T Ch. 62) at 100 Mbps
 Mechanisms for ensuring eye-safety:
 Spring-loaded protective covers on connectors carrying high power signals
 BR detection
 LOS detection from the far end
 OSC signal detection
 Built-in C/T filters for 1528 nm (ITU-T Ch. 62) to support OSC functionality
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Monitoring and alarms

Ribbon Communications Inc. Proprietary 10-154

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ports
Port name Connector Function
EXP IN LX.5 Connect to counter-propagating signal.
AMP OUT LX.5 Connect to amplified signal output.
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides a -20 dB sample from the amplifier output signal.
LINE IN (PUMP E2000HP For connecting the pump signal output to the line input fiber and the line
OUT) input signal to Raman input.
LINE OUT E2000HP For connecting the line output signal to the line output fiber.

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the OA_EHRS.

Ribbon Communications Inc. Proprietary 10-155

Apollo Reference Manual OPT96xx optical cards and modules

Marking Item Functions

OSC 100M LED
Tx Green LED Lights steadily when the OSC SFP laser transmits.
LINE LEDs
LOS Red LED Blinks when the signal on the line (fiber) is missing or below the preset
threshold; this signal is valid only when the Raman is off. This usually
indicates a fiber cut.
BR Orange LED Lights when the level of BR line signal exceeds the preset threshold.
Usually, this indicates a disconnection or break in the fiber connected to the
LINE IN connector.
RAMAN ON Green LED Lights when laser power is transmitted through the line port.
OSC LOS Red LED Blinks when the 1528 nm (ITU-T Ch. 62) OSC signal is missing or below the
preset threshold.
AMP LEDs
BR Orange LED Lights when the level of BR amplifier output signal exceeds the preset
threshold. Usually, this indicates a disconnection or break in the fiber
connected to the AMP OUT connector.
ON Green LED Lights when the output power of the amplifier is above the threshold level.
EXP. IN LED
LOS Red LED Blinks when the EXP. IN input signal is missing, or is too low for normal
operation.

Block diagram

Ribbon Communications Inc. Proprietary 10-156

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.16 OA_HRSF
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_HRSF is a Raman amplifier card that provides low-noise amplification for Apollo networks. It
provides a mean to improve the system OSNR, but specifically employed on ultra-long links (>40dB
loss). In addition, the Raman amplifier cards enable the generation and termination of the optical
supervision channel (OSC). The OSC is an optical channel at 1528 nm that operates at 2 Mbps and
carries management data between optical network nodes. For eye-safety reasons, operation of the 2
Mbps OSC channel is essential.
The gain of the amplifier depends on the fiber type and fiber quality, connected to the Line input port:
for G.652/654 it's 11 to 14 dB; for G.655 it's 13 to 16 dB.
OA_HRSF is intended for use in conjunction with EDFA amplifiers over G.652, G.654, and G.655 fibers.
It supports multichannel applications capable of amplifying the entire C band, supports Flex-Grid, and
also transports the OSC at 1528 nm. For safety reasons the OA_HRSF is designed to operate in E/W
configurations and it includes built-in C/T filters. The OA_HRSF also includes an OTDR filter to enable
monitoring of the fiber span.
The OA_HRSF operates in the backward mode. The mode indicates the direction of signal flow relative
to the amplifier line side. Backward mode means that the OA_HRSF is located at the receiving end of
an optical span to provide an effect similar to that of using a low noise figure preamplifier before further
amplifying the low-level signals received from the line by an EDFA amplifier.
The OA_HRSF occupies a double (long) slot in the OPT96xx platforms.

Functions
 Output power monitoring point
 OSC termination (2 Mbps)
 OSC add and drop
 Mechanisms for ensuring eye-safety:
 Spring-loaded protective covers on connectors carrying high power signals
 BR detection
 LOS detection from the far end
 ALS
 Built-in C/T filters to support OSC functionality
 OTDR port to enable monitoring of the fiber span
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Monitoring and alarms
 1528 nm SFP for OSC channel

Ribbon Communications Inc. Proprietary 10-157

 Apollo Reference Manual OPT96xx optical cards and modules

For additional safety information, see Raman amplification principles of operation and High power laser
safety.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-158

Apollo Reference Manual OPT96xx optical cards and modules

Ports

Port name Connector Function

NODE IN LX.5 For connecting a booster amplifier output to the line. This signal passes
through the OA_HRSF and connects to the LINE OUT connector.
Connector is located behind spring loaded cover for safety
NODE OUT LX.5 For connecting the Raman amplifier output to an EDFA amplifier.
Connector is located behind spring loaded cover for safety
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides an -20 dB sample from the amplifier output signal
LINE IN (PUMP E2000 For connecting the pump signal output to the line and the line signal to
OUT) Raman input. Connector is located behind spring loaded cover for
safety
LINE OUT E2000 For connecting the line output signal (typically comes from a booster
amplifier). Connector located behind spring loaded cover for safety
OSC 1528 IN LC For connecting the input 1528 nm supervisory channel
OSC 1528 OUT LC For connecting the input 1528 nm supervisory channel
OTDR ACCESS LC For connecting an OTDR device to test the characteristics of the line
fiber

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the OA_HRSF.
LINE LEDs
BR Orange LED Lights when the level of BR signal exceeds the preset threshold. Usually,
this indicates a disconnection or unclean connectors toward or at the LINE
IN port.
RAMAN ON Green LED Lights when laser power is transmitted through the line port (power source
may be the OA_HRSF and/or the EDFA amplifier).
OSC LOS Red LED Blinks when the 1528 nm OSC signal is missing or below the preset
threshold.
LINE LOS Red LED Blinks when the signal on the line (fiber) is missing or under the preset
threshold. This usually indicates a fiber cut.
NODE LED
NODE LOS Red LED Blinks when the signal arriving from the node (typically connected to a
booster amplifier) is missing or under the preset threshold.
OSC2M LEDs
Tx Green LED Lights steadily when the OSC2M laser transmits.
F/L Red LED Blinks when the OSC2M input signal is missing, or is too low for normal
operation. Lights when a fault is detected in the OSC2M path.

Ribbon Communications Inc. Proprietary 10-159

 Apollo Reference Manual OPT96xx optical cards and modules

Block diagram

10.12.17 OA_EHRSF
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_EHRSF is a hybrid Raman/EDFA optical amplifier supporting operation in Flex-Grid, for both
ILA and pre-amp configurations in DCF-less coherent networks. It combines a distributed low-noise
Raman amplification and a high-gain, high-power EDFA amplification in a single module, providing low-
noise figure, high gain, and high output power, while improving the system OSNR. The OA_EHRSF is
intended for use over G.652, G.654, and G.655 fibers. It supports multichannel applications capable of
amplifying the entire C band, and also transmits the OSC on 1528 nm. For safety reasons the
OA_EHRSF is designed to operate in E/W configurations and it includes special built-in C/T filters and
OSC SFP (1528 nm) that provide an enhanced safety mechanism and enable controlled Raman
operation. The OA_EHRSF card occupies a double I/O slot in Apollo platforms.
The Raman section of the OA_EHRSF operates in the backward mode. The mode indicates the
direction of signal flow relative to the amplifier line side. Backward mode means that the Raman pumps
of the OA_EHRSF are located at the receiving end of an optical span to provide an effect similar to that
of using a low noise figure preamplifier before further amplifying the low-level signals received from the
line by the EDFA section of the OA_EHRSF amplifier. The OA_EHRSF also includes an OTDR filter to
enable monitoring of the fiber span.
To ensure high reliability, the connectivity of the Raman amplifier output pump to the fibers is first
checked, before full output power is allowed, using built-in special software commands.

Ribbon Communications Inc. Proprietary 10-160

 Apollo Reference Manual OPT96xx optical cards and modules

Functions
 Combines a Backward Raman amplification and an Erbium-based amplification in a single module
 Supports operation in Flex-Grid
 Low NF (Noise Figure) across the entire C-Band
 High dynamic gain (19 to 37 dB)
 High output power (up to 20.5 dBm)
 Transient suppression
 Gain and tilt control
 Output power monitoring point
 Built-in SFP OSC operating on 1528 nm, at 100 Mbps
 Mechanisms for ensuring eye-safety:
 Spring-loaded protective covers on connectors carrying high power signals
 BR detection
 LOS detection from the far end
 OSC signal detection
 Built-in C/T filters for 1528 nm to support OSC functionality
 OTDR port to enable monitoring of the fiber span
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Monitoring and alarms

Card views
General view

Ribbon Communications Inc. Proprietary 10-161

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

Ports

Port name Connector Function

EXP IN LX.5 Connect to counter-propagating signal.
AMP OUT LX.5 Connect to amplified signal output.
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides a -20 dB sample from the amplifier output signal.
LINE IN (PUMP E2000HP For connecting the pump signal output to the line input fiber and the line
OUT) input signal to Raman input.
LINE OUT E2000HP For connecting the line output signal to line output fiber.
OTDR 1610 LC To connect an OTDR device to test the characteristics of the line fiber.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the OA_EHRSF.
OSC 100M LED
Tx Green LED Lights steadily when the OSC SFP laser transmits.
LINE LEDs
LOS Red LED Blinks when the signal on the line (fiber) is missing or below the preset
threshold; this signal is valid only when the Raman is off. This usually
indicates a fiber cut.

Ribbon Communications Inc. Proprietary 10-162

Apollo Reference Manual OPT96xx optical cards and modules

Marking Item Functions

BR Orange LED Lights when the level of BR line signal exceeds the preset threshold.
Usually, this indicates a disconnection or unclean connectors toward or at
the LINE IN port.
RAMAN ON Green LED Lights when laser power is transmitted through the line port.
OSC LOS Red LED Blinks when the 1528 nm OSC signal is missing or below the preset
threshold.
AMP LEDs
BR Orange LED Lights when the level of BR amplifier output signal exceeds the preset
threshold. Usually, this indicates a disconnection or unclean connectors
toward or at the AMP OUT port.
ON Green LED Lights when the output power of the amplifier is above the threshold level.
EXP. IN LED
LOS Red LED Blinks when the EXP. IN input signal is missing, or is too low for normal
operation.

Block diagram

Ribbon Communications Inc. Proprietary 10-163

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.18 OA_LEHRSF
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_LEHRSF is a hybrid Raman/EDFA optical amplifier supporting operation in Flex-Grid, for both
ILA and pre-amp configurations in DCF-less coherent networks. These amplifiers are optimized for low-
gain 100/200G coherent regional and long-haul in-line sites to increase network reach, providing
optimized dynamic gain for short spans (15 to 26 dB).
The OA_LEHRSF combines a distributed low-noise Raman amplification and a high-power EDFA
amplification in a single module, providing low-noise figure, wide gain, and high output power, while
improving the system OSNR. The OA_LEHRSF is intended for use over G.652, G.654, and G.655
fibers. It supports multichannel applications capable of amplifying the entire C band, and also transmits
the OSC on 1528 nm. For safety reasons the OA_LEHRSF is designed to operate in E/W
configurations and it includes special built-in C/T filters and OSC SFP (1528 nm) that provide an
enhanced safety mechanism and enable controlled Raman operation. The OA_LEHRSF card occupies
a double I/O slot in Apollo platforms.
The Raman section of the OA_LEHRSF operates in the backward mode. The mode indicates the
direction of signal flow relative to the amplifier line side. Backward mode means that the Raman pumps
of the OA_LEHRSF are located at the receiving end of an optical span to provide an effect similar to
that of using a low noise figure preamplifier before further amplifying the low-level signals received from
the line by the EDFA section of the OA_LEHRSF amplifier. The OA_LEHRSF also includes an OTDR
filter to enable monitoring of the fiber span.
To ensure high reliability, the connectivity of the Raman amplifier output pump to the fibers is first
checked, before full output power is allowed, using built-in special software commands.

Functions
 Combines a Backward Raman amplification and an Erbium-based amplification in a single module
 Supports operation in Flex-Grid
 Low NF (Noise Figure) across the entire C-Band
 Optimized dynamic gain for short spans (15 to 26 dB)
 High output power (up to 20.5 dBm)
 Transient suppression
 Gain and tilt control
 Output power monitoring point
 Built-in SFP OSC operating on 1528 nm, at 100 Mbps
 Mechanisms for ensuring eye-safety:
 Spring-loaded protective covers on connectors carrying high power signals
 BR detection
 LOS detection from the far end
 OSC signal detection

Ribbon Communications Inc. Proprietary 10-164

 Apollo Reference Manual OPT96xx optical cards and modules

 Built-in C/T filters for 1528 nm to support OSC functionality

 OTDR port to enable monitoring of the fiber span
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Monitoring and alarms

Card views
General view

Front panel

Ports
Port name Connector Function
EXP IN LX.5 Connect to counter-propagating signal.
AMP OUT LX.5 Connect to amplified signal output.
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides a -20 dB sample from the amplifier output signal.
LINE IN (PUMP E2000HP For connecting the pump signal output to the line input fiber and the line
OUT) input signal to Raman input.
LINE OUT E2000HP For connecting the line output signal to the line output fiber.
OTDR 1610 LC To connect an OTDR device to test the characteristics of the line fiber.

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the OA_LEHRSF.

Ribbon Communications Inc. Proprietary 10-165

Apollo Reference Manual OPT96xx optical cards and modules

Marking Item Functions

OSC 100M LED
Tx Green LED Lights steadily when the OSC SFP laser transmits.
LINE LEDs
LOS Red LED Blinks when the signal on the line (fiber) is missing or below the preset
threshold; this signal is valid only when the Raman is off. This usually
indicates a fiber cut.
BR Orange LED Lights when the level of BR line signal exceeds the preset threshold.
Usually, this indicates a disconnection or unclean connectors toward or at
the LINE IN port.
RAMAN ON Green LED Lights when laser power is transmitted through the line port.
OSC LOS Red LED Blinks when the 1528 nm OSC signal is missing or below the preset
threshold.
AMP LEDs
BR Orange LED Lights when the level of BR amplifier output signal exceeds the preset
threshold. Usually, this indicates a disconnection or unclean connectors
toward or at the AMP OUT port.
ON Green LED Lights when the output power of the amplifier is above the threshold level.
EXP. IN LED
LOS Red LED Blinks when the EXP. IN input signal is missing, or is too low for normal
operation.

Block diagram

Ribbon Communications Inc. Proprietary 10-166

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.19 OA_USPBF
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_USPBF is a high-gain power booster amplifier with an output power of 26 dBm. It can be used
in dispersion-managed 10G networks, cascaded to MSA ILA, or in DCF-less coherent networks,
cascaded to non-MSA ILA. The OA_USPBF supports multichannel applications and is capable of
amplifying the Extended-C-band.
For safety reasons the OA_USPBF is designed to operate in E/W configurations and includes a special
built-in C/T filter for the OSC signal. The OSC signal can be connected from another amplifier or from
an OSC_8 card. For additional safety information, see High power laser safety and Automatic laser
shutdown.
The OA_USPBF occupies a double I/O slot in Apollo platforms.
The OA_USPBF is an E/W configured card designed to provide enhanced ALS function to shut down
the amplifier in case of fiber cut. The “LINE IN” and “LINE OUT” ports are connected to one of the fiber
directions. An internal photo-diode (PD) on the connection between these ports facilitates the ALS
function (for a detailed description see Automatic Laser Shutdown). A comprehensive APR system
complements the eye-safety mechanisms of the card (see Automatic Power Reduction).

NOTE: The OA_USPBF operation requires this amplifier type at both span ends.

Functions
 Low NF (Noise Figure) across the Extended-C-Band
 Optimized fixed gain (5 to 7 dB)
 High output power (up to 26 dBm)
 Transient suppression
 Gain and tilt control
 Output power monitoring point
 Mechanisms for ensuring eye-safety:
 Spring-loaded protective covers on connectors carrying high power signals
 BR detection
 Automatic Laser Shutdown (ALS)
 Automatic Power Reduction (APR)
 LOS detection from the far end
 OSC signal detection
 Built-in C/T filters for 1510 nm to support OSC functionality

Ribbon Communications Inc. Proprietary 10-167

 Apollo Reference Manual OPT96xx optical cards and modules

 Full PM by means of management stations, including monitoring of optical power levels

 Monitoring and alarms

Card views
General view

Front panel

Ports

Port name Connector Function

AMP IN LC Amplifier line input connector
EXP OUT LC Express output signal after the PD (fiber cut detection)
OSC 1510 IN LC OSC input signal connector from built-in C/T filter
OSC 1510 OUT LC OSC output signal connector to built-in C/T filter
AMP OUT LC Amplifier external line output connector that is also the output from the
2nd stage.
MON OUT - LC Monitor connector used to connect test equipment (like OPM or OSA);
20dB provides an -20 dB sample from the amplifier output signal.
LINE IN E2000 Connect the EDFA pump output to the line. Located behind spring
loaded cover for safety
LINE OUT E2000 Connect the line output signal (usually comes from a booster amplifier).
Located behind spring loaded cover for safety

Ribbon Communications Inc. Proprietary 10-168

 Apollo Reference Manual OPT96xx optical cards and modules

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the OA_USPBF.
AMP IN LED
Blinks when the AMP IN input signal is missing or below the preset
LOS Red LED
threshold.
LINE LEDs
ALS Orange LED Lights when the ALS protection mechanism is activated. Usually, this
indicates a disconnection in the fiber connected to the amplifier output.
APR Green LED Lights when the APR protection mechanism is activated. This occurs
when there is high back reflection and the amplifier's output power is
above the allowed threshold.
OUT BR Orange LED Lights when the level of BR amplifier output signal exceeds a preset
threshold. Usually, this indicates a disconnection or break in the fiber
connected to the amplifier output (LINE OUT) connector.
OUT ON Green LED Lights when the output power of the amplifier is above the threshold level.
IN LOS Red LED Lights when there is no input signal, or the signal to the LINE IN connector
is under a preset threshold. Usually, this indicates a disconnection or
break in the fiber connected from the far side, or no output power from the
amplifier at the far side.

10.12.19.1 Automatic power reduction

A special Automatic Power Reduction (APR) subsystem ensures that the high-power signals are
confined to the fiber. During transmission this subsystem continuously monitors and analyzes various
optical parameters, for example, input signal levels, back reflection, and supervisory channel signal. It is
therefore capable of detecting fiber disconnections and fiber cuts, even when they occur many
kilometers from the card's location. In these cases, the APR subsystem automatically reduces the
amplifier output power below an eye-safe predetermined level in accordance with ITU-T Rec. G.664.
After the APR subsystem is activated, normal operation is automatically resumed once normal
conditions have been restored by the management system. Other monitored signals that result in APR
activation are High back reflection from the line output.

Ribbon Communications Inc. Proprietary 10-169

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.20 OA_DLF
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X

Description
The OA_DLF is a dual EDFA card that includes two independent EDFA amplifiers in a single package.
The two EDFAs are defined as pre-amp and Booster amplifiers. The pre-amp EDFA amplifies the
optical signal received from the line, and the Booster amplifies the light transmitted to the line. The pre-
amp EDFA in the OA_DLF is optimized for medium-span applications.
For safety reasons the OA_DLF is designed to operate in E/W configurations and includes built-in C/T
filters. The card occupies one slot in the OPT96xx platforms and includes an 1510nm OSC filter and a
pluggable 100 Mbps 1510nm OSC SFP.
The OA_DLF card operates over the extended C-band spectral range.

Functions
 Includes two independent EDFA modules
 Single-slot card for the OPT96xx family
 Accommodate an 100 Mbps 1510 nm OSC SFP
 Built-in E-W C/T filters to support OSC functionality
 Operates in Bi-directional configuration to support safety
 Optical amplification (power and gain control)
 Transient suppression
 Monitoring and alarms
 OSC termination (optional)
 Extended C-band (96 channels) operation

Card views
General view

Ribbon Communications Inc. Proprietary 10-170

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

Ports

Port name Connector Function

NODE IN LC Booster input connector
NODE OUT LC Pre-amp output connector
MON OUT - LC Monitor connector (near NODE) used to connect test equipment (like
20dB OPM or OSA); provides an -20 dB sample from the Pre-amp output signal
LINE IN LC Pre-amp input connector
LINE OUT LC Booster output connector
MON OUT - LC Monitor connector (near LINE): used to connect test equipment (like OPM
20dB or OSA); provides an -20 dB sample from the Booster output signal.
OSC 1510 IN LC Input signal connector to built-in C/T filter.
OSC 1510 OUT LC Output signal connector to built-in C/T filter
OSC100M SFC Port that can house an optional 1510nm SFP that provides FE control
communication channel

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off when
the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault in
the OA_DLF.
Booster amplifier LEDs
ON Green LED Lights steadily when the pump laser is on and the output power is above the
preset threshold. Off when the output power is below the threshold (LOP
condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually, this
indicates a disconnection or break in the fiber connected to the LINE OUT
connector.
LOS Red LED Blinks when the input power signal is missing, or is too low for normal
operation (LOS condition). Off when the input signal is normal.

Ribbon Communications Inc. Proprietary 10-171

Apollo Reference Manual OPT96xx optical cards and modules

Marking Item Functions

Preamplifier LEDs
ON Green LED Lights steadily when the pump laser is on and the output power is above the
preset threshold. Off when the output power is below the threshold (LOP
condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually, this
indicates a disconnection or break in the fiber connected to the NODE OUT
connector.
LOS Red LED Blinks when the input power signal to the Preamp is missing, or is too low for
normal operation (LOS condition). Off when the input signal is normal.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing, or is too low for normal operation.
Lights when a fault is detected in the OSC path.

Block diagram

Ribbon Communications Inc. Proprietary 10-172

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.21 OA_DLHF
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X

Description
The OA_DLHF is a dual EDFA card that includes two independent EDFA amplifiers in a single
package. The two EDFAs are defined as pre-amp and booster amplifiers. The pre-amp EDFA amplifies
the optical signal received from the line, and the Booster amplifies the light transmitted to the line. The
pre-amp EDFA in the OA_DLHF is optimized for long-span applications.
For safety reasons the OA_DLHF is designed to operate in E/W configurations and it includes built-in
C/T filters. The card occupies one slot in the OPT96xx platforms and includes an 1510nm OSC filter
and a pluggable 100 Mbps 1510nm OSC SFP.
The OA_DLHF card operates over the extended C-band spectral range.

Functions
 Includes two independent EDFA modules
 Booster 15-28dB
 Pre-amplifier 25-37dB
 Single-slot card for the OPT96xx family and for the OPT9904X
 Accommodate an 100 Mbps 1510 nm OSC SFP
 Built-in E-W C/T filters to support OSC functionality
 Operates in Bi-directional configuration to support safety
 Optical amplification (power and gain control)
 Transient suppression
 Monitoring and alarms
 OSC termination (optional)
 Extended C-band (96 channels) operation

Card views
General view

Ribbon Communications Inc. Proprietary 10-173

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

Ports

Port name Connector Function

NODE IN LC Booster input connector
NODE OUT LC Pre-amp output connector
MON OUT - LC Monitor connector (near NODE) used to connect test equipment (like
20dB OPM or OSA); provides an -20 dB sample from the Pre-amp output signal
LINE IN LC Pre-amp input connector
LINE OUT LC Booster output connector
MON OUT - LC Monitor connector (near LINE): used to connect test equipment (like OPM
20dB or OSA); provides an -20 dB sample from the Booster output signal.
OSC 1510 IN LC Input signal connector to built-in C/T filter.
OSC 1510 OUT LC Output signal connector to built-in C/T filter
OSC100M SFC Port that can house an optional 1510nm SFP that provides FE control
communication channel

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations).
Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is
no fault in the OA_DLHF.
Booster amplifier LEDs
ON Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually, this
indicates a disconnection or break in the fiber connected to the LINE
OUT connector.
LOS Red LED Blinks when the input power signal is missing, or is too low for normal
operation (LOS condition). Off when the input signal is normal.
Preamplifier LEDs

Ribbon Communications Inc. Proprietary 10-174

Apollo Reference Manual OPT96xx optical cards and modules

Marking Item Functions

ON Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually, this
indicates a disconnection or break in the fiber connected to the NODE
OUT connector.
LOS Red LED Blinks when the input power signal to the Preamp is missing, or is too
low for normal operation (LOS condition). Off when the input signal is
normal.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing, or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Block diagram

Ribbon Communications Inc. Proprietary 10-175

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.22 OA_DVLF
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X

Description
The OA_DVLF is a dual EDFA card that includes two independent EDFA amplifiers in a single package.
The two EDFAs are defined as pre-amp and booster amplifiers. The pre-amp EDFA amplifies the
optical signal received from the line, and the booster amplifies the light transmitted to the line. The pre-
amp EDFA in the OA_DVLF is optimized for short-span applications.
For safety reasons the OA_DVLF is designed to operate in E/W configurations and it includes built-in
C/T filters. The card occupies one slot in the OPT96xx and OPT9904X platforms and includes an
1510nm OSC filter and a pluggable 100 Mbps 1510nm OSC SFP.
The OA_DVLF card operates over the extended C-band spectral range.

Functions
 Includes two independent EDFA modules
 Booster 14-21dB
 Pre-amplifier 8-18dB
 Single-slot card for the OPT96xx family and for the OPT9904X
 Accommodate an 100 Mbps 1510 nm OSC SFP
 Built-in E-W C/T filters to support OSC functionality
 Operates in bi-directional configuration to support safety
 Optical amplification (power and gain control)
 Transient suppression
 Monitoring and alarms
 OSC termination (optional)
 Extended C-band (96 channels) operation

Card views
General view

Ribbon Communications Inc. Proprietary 10-176

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

Ports

Port name Connector Function

NODE IN LC Booster input connector
NODE OUT LC Pre-amp output connector
MON OUT - LC Monitor connector (near NODE) used to connect test equipment (like
20dB OPM or OSA); provides an -20 dB sample from the Pre-amp output signal
LINE IN LC Pre-amp input connector
LINE OUT LC Booster output connector
MON OUT - LC Monitor connector (near LINE): used to connect test equipment (like OPM
20dB or OSA); provides an -20 dB sample from the Booster output signal.
OSC 1510 IN LC Input signal connector to built-in C/T filter.
OSC 1510 OUT LC Output signal connector to built-in C/T filter
OSC100M SFC Port that can house an optional 1510nm SFP that provides FE control
communication channel

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations).
Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is
no fault in the OA_DLHF.
Booster amplifier LEDs
ON Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually, this
indicates a disconnection or break in the fiber connected to the LINE
OUT connector.
LOS Red LED Blinks when the input power signal is missing, or is too low for normal
operation (LOS condition). Off when the input signal is normal.
Preamplifier LEDs
ON Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).

Ribbon Communications Inc. Proprietary 10-177

Apollo Reference Manual OPT96xx optical cards and modules

Marking Item Functions

BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually, this
indicates a disconnection or break in the fiber connected to the NODE
OUT connector.
LOS Red LED Blinks when the input power signal to the Preamp is missing, or is too
low for normal operation (LOS condition). Off when the input signal is
normal.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing, or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Block diagram

Ribbon Communications Inc. Proprietary 10-178

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.23 OA_DPR
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OA_DPR is a low-cost Red Band, dual EDFA card that includes two independent EDFA amplifiers
in a single package. The two EDFAs are defined as pre-amp and Booster amplifiers. It can operate only
in the Red Band (ITU-T Ch. 21 to Ch. 36) and support 16 (100 GHz spacing), or 32 channels (50 GHz
spacing).
The OA_DPR is designed to operate in E/W configurations and includes built-in C/T filters. The card
occupies one slot in the OPT96xx platforms and includes an 1510nm OSC filter and a pluggable 100
Mbps 1510nm OSC SFP.

Functions
 Includes two independent EDFA modules
 Single-slot card for the OPT96xx family
 Accommodate an 100 Mbps 1510 nm OSC SFP
 Supports 16 or 32 channels in the Red Band
 Built-in E-W C/T filters to support OSC functionality
 Operates in Bi-directional configuration to support safety
 Optical amplification (power and gain control)
 Transient suppression
 Monitoring and alarms
 OSC termination (optional)

Card views
General view

Ribbon Communications Inc. Proprietary 10-179

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

Ports

Port name Connector Function

NODE IN LC Booster input connector
NODE OUT LC Pre-amp output connector
MON OUT - LC Monitor connector (near NODE) used to connect test equipment (like
20dB OPM or OSA); provides an -20 dB sample from the Pre-amp output signal
LINE IN LC Pre-amp input connector
LINE OUT LC Booster output connector
MON OUT - LC Monitor connector (near LINE): used to connect test equipment (like OPM
20dB or OSA); provides an -20 dB sample from the Booster output signal.
OSC 1510 IN LC Input signal connector to built-in C/T filter.
OSC 1510 OUT LC Output signal connector to built-in C/T filter
OSC100M SFC Port that can house an optional 1510nm SFP that provides FE control
communication channel

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations).
Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is
no fault in the OA_DPR.
Booster amplifier LEDs
ON Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually, this
indicates a disconnection or break in the fiber connected to the LINE
OUT connector.
LOS Red LED Blinks when the input power signal is missing, or is too low for normal
operation (LOS condition). Off when the input signal is normal.

Ribbon Communications Inc. Proprietary 10-180

Apollo Reference Manual OPT96xx optical cards and modules

Marking Item Functions

Preamplifier LEDs
ON Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
BR Orange LED Lights when the level of BR exceeds the preset threshold. Usually, this
indicates a disconnection or break in the fiber connected to the NODE
OUT connector.
LOS Red LED Blinks when the input power signal to the Preamp is missing, or is too
low for normal operation (LOS condition). Off when the input signal is
normal.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing, or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Block diagram

Ribbon Communications Inc. Proprietary 10-181

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.24 OA_DFBL
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X

Description
The OA_DFBL is a dual EDFA card that includes two independent EDFA amplifiers in a single package.
The two EDFAs are defined as pre-amp and Booster amplifiers. The pre-amp EDFA amplifies the
optical signal received from the line, and the Booster amplifies the light transmitted to the line. The card
is optimized for Metro applications with up to 44 channels.
For safety reasons the OA_DFBL is designed to operate in E/W configurations and it includes built-in
C/T filters. The card occupies one slot in the OPT96xx platforms and includes an 1510nm OSC filter
and a pluggable 100 Mbps 1510nm OSC SFP.
The pre-amp EDFA is a 16 dBm VGA (Variable Gain Amplifier), while the Booster is a 20 dBm FGA
(Fixed Gain Amplifier).

Functions
 Includes two independent EDFA modules
 Single-slot card for the OPT96xx family and for the OPT9904X
 Accommodate an 100 Mbps 1510 nm OSC SFP
 Built-in E-W C/T filters to support OSC functionality
 Operates in Bi-directional configuration to support safety
 Optical amplification (power and gain control)
 Monitoring and alarms
 OSC termination (optional)
 Reduced C-band ( channels)

Card views
General view

Ribbon Communications Inc. Proprietary 10-182

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

Ports

Port name Connector Function

NODE IN LC Booster input connector
NODE OUT LC Pre-amp output connector
MON OUT - LC Monitor connector (near NODE) used to connect test equipment (like
20dB OPM or OSA); provides an -20 dB sample from the Pre-amp output signal
LINE IN LC Pre-amp input connector
LINE OUT LC Booster output connector
MON OUT - LC Monitor connector (near LINE): used to connect test equipment (like OPM
20dB or OSA); provides an -20 dB sample from the Booster output signal.
OSC 1510 IN LC Input signal connector to built-in C/T filter.
OSC 1510 OUT LC Output signal connector to built-in C/T filter
OSC100M SFC Port that can house an optional 1510nm SFP that provides FE control
communication channel

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations).
Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is
no fault in the OA_DFBL.
Booster amplifier LEDs
ON Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
LOS Red LED Blinks when the input power signal is missing, or is too low for normal
operation (LOS condition). Off when the input signal is normal.

Ribbon Communications Inc. Proprietary 10-183

 Apollo Reference Manual OPT96xx optical cards and modules

Marking Item Functions

Preamplifier LEDs
ON Green LED Lights steadily when the pump laser is on and the output power is
above the preset threshold. Off when the output power is below the
threshold (LOP condition).
LOS Red LED Blinks when the input power signal to the Preamp is missing, or is too
low for normal operation (LOS condition). Off when the input signal is
normal.
OSC LEDs
Tx Green LED Lights steadily when the OSC laser transmits.
F/L Red LED Blinks when the OSC input signal is missing, or is too low for normal
operation. Lights when a fault is detected in the OSC path.

Block diagram

10.12.25 OPA_FBS
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X
The OPA_FBS pluggable booster amplifier is used in these platforms when installed within a
ROADM_4FS module.

Description
The OPA_FBS is a pluggable CFP2 form-factor amplifier, hosted by the ROADM_4FS module, for use
as a booster in the designated booster module slot. The OPA_FBS is a 20.5dBm single-stage variable
gain pluggable EDFA that operates over the extended C-band. The operating gain range is 15 to 28dB.
A 1510nm OSC channel may be added via the OSCin port.

Ribbon Communications Inc. Proprietary 10-184

 Apollo Reference Manual OPT96xx optical cards and modules

Functions
 Variable gain booster amplifier (15-28 dB)
 High output power (20.5 dBm)
 Transient suppression
 Output power monitoring point
 Single amplification stage
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Monitoring and alarms
 1510 nm add OSC filter built-in

Functional block diagram

Pluggable amplifier indicators

The OPA_FBS pluggable booster amplifier is housed within a ROADM_4FS module. The amplifier port
labels and LEDs are marked on the ROADM_4FS module casing. The OPA ports are also marked on
the amplifier front panel. For convenience, the amplifier type is identified by the handle color, allowing
you to distinguish between the three types of OPA modules without any need to extract them.

Amplifier indicators

Panel marking Connector Function

=> (IN) LC Amplifier line input connector.
<= (OUT) LC Amplifier output connector.
O (OSC add) LC Built-in 1510 nm OSC filter that provides an FE control communications
channel.
Red handle Identifies the OPA_FBS booster amplifier.

Ribbon Communications Inc. Proprietary 10-185

 Apollo Reference Manual OPT96xx optical cards and modules

10.12.26 OPA_VLFS
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X
The OPA_VLFS pluggable very low-gain pre-amplifier is used in these platforms when installed within a
ROADM_4FS module.

Description
The OPA_VLFS is a pluggable CFP2 form-factor amplifier, hosted by the ROADM_4FS module, for use
as a very low-gain pre-amp in the designated pre-amp module slot. The OPA_VLFS is a 20.5dBm
single-stage variable gain pluggable EDFA that operates over the extended C-band. The operating gain
range is 8 to 18dB. A 1510nm OSC channel may be dropped via the OSCout port.

Functions
 Variable gain pre-amplifier (8-18 dB)
 High output power (20.5 dBm)
 Transient suppression
 Output power monitoring point
 Single amplification stage
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Monitoring and alarms
 1510 nm drop OSC filter built-in

Functional block diagram

Ribbon Communications Inc. Proprietary 10-186

 Apollo Reference Manual OPT96xx optical cards and modules

Pluggable amplifier indicators

The OPA_VLFS pluggable pre-amplifier is housed within a ROADM_4FS module. The amplifier port
labels and LEDs are marked on the ROADM_4FS module casing. The OPA ports are also marked on
the amplifier front panel. For convenience, the amplifier type is identified by the handle color, allowing
you to distinguish between the different types of OPA modules without any need to extract them.

Amplifier indicators

Panel marking Connector Function

 (IN) LC Amplifier line input connector.
 (OUT) LC Amplifier output connector.
 (OSC drop) LC Built-in 1510 nm OSC filter that provides an FE control communications
channel.
Yellow handle Identifies the OPA_VLFS low-gain pre-amplifier.

10.12.27 OPA_LFS
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X
The OPA_LFS pluggable low-gain pre-amplifier is used in these platforms when installed within a
ROADM_4FS module.

Description
The OPA_LFS is a pluggable CFP2 form-factor amplifier, hosted by the ROADM_4FS module, for use
as a low-gain pre-amp in the designated pre-amp module slot. The OPA_LFS is a 20.5dBm single-
stage variable gain pluggable EDFA that operates over the extended C-band. The operating gain range
is 15 to 28dB. A 1510nm OSC channel may be dropped via the OSCout port.

Functions
 Variable gain pre-amplifier (15-28 dB)
 High output power (20.5 dBm)
 Transient suppression
 Output power monitoring point
 Single amplification stage
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Monitoring and alarms
 1510 nm drop OSC filter built-in

Ribbon Communications Inc. Proprietary 10-187

 Apollo Reference Manual OPT96xx optical cards and modules

Functional block diagram

Pluggable amplifier indicators

The OPA_LFS pluggable pre-amplifier is housed within a ROADM_4FS module. The amplifier port
labels and LEDs are marked on the ROADM_4FS module casing. The OPA ports are also marked on
the amplifier front panel. For convenience, the amplifier type is identified by the handle color, allowing
you to distinguish between the three types of OPA modules without any need to extract them.

Amplifier indicators

Panel marking Connector Function

 (IN) LC Amplifier line input connector.
 (OUT) LC Amplifier output connector.
 (OSC drop) LC Built-in 1510 nm OSC filter that provides an FE control communications
channel.
Blue handle Identifies the OPA_LFS low-gain pre-amplifier.

10.12.28 OPA_HFS
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X
The OPA_HFS pluggable high-gain pre-amplifier is used in these platforms when installed within a
ROADM_4FS module.

Description
The OPA_HFS is a pluggable CFP2 form-factor amplifier, hosted by the ROADM_4FS module, for use
as a high-gain pre-amp in the designated pre-amp module slot. The OPA_HFS is a 20.5dBm single-
stage variable gain pluggable EDFA that operates over the extended C-band. The operating gain range
is 25 to 37dB. A 1510nm OSC channel may be dropped via the OSCout port.

Ribbon Communications Inc. Proprietary 10-188

 Apollo Reference Manual OPT96xx optical cards and modules

Functions
 Variable gain pre-amplifier (25-37 dB)
 High output power (20.5 dBm)
 Transient suppression
 Output power monitoring point
 Single amplification stage
 Full PM by means of management stations, including monitoring of optical power levels and pump
current
 Monitoring and alarms
 1510 nm drop OSC filter built-in

Functional block diagram

Pluggable amplifier indicators

The OPA_HFS pluggable pre-amplifier is housed within a ROADM_4FS module. The amplifier port
labels and LEDs are marked on the ROADM_4FS module casing. The OPA ports are also marked on
the amplifier front panel. For convenience, the amplifier type is identified by the handle color, allowing
you to distinguish between the three types of OPA modules without any need to extract them.

Amplifier indicators

Panel marking Connector Function

 (IN) LC Amplifier line input connector.
 (OUT) LC Amplifier output connector.
 (OSC drop) LC Built-in 1510 nm OSC filter that provides an FE control communications
channel.
Purple handle Identifies the OPA_HFS high-gain pre-amplifier.

Ribbon Communications Inc. Proprietary 10-189

 Apollo Reference Manual OPT96xx optical cards and modules

10.13 OTDR modules

An Optical Time-Domain Reflectometer (OTDR) is an optoelectronic device used to test the
characteristics of an optical fiber. It injects a series of optical pulses into the fiber under test and
extracts, from the same end of the fiber, light that is scattered or reflected back from points along the
fiber. The scattered or reflected light that is gathered back is used to analyze the optical fiber
characteristics. The strength of the return pulses is measured and integrated as a function of time.
The purpose of an OTDR is to detect, locate, and measure elements at any location on a fiber optical
link. The OTDR test results are processed and enable to display a graphical representation of the entire
fiber optic link. The OTDR provides the user a trace (graphic representation) of the fiber's attenuation
as a function of distance from the OTDR connection point. An example of an OTDR trace signatures is
shown in the following figure.

OTDR data graph

Operation of an OTDR can be simple, however it requires familiarity with fiber testing best practices to
perform good, reliable tests. OTDR traces can be analyzed and well interpreted only by trained and
experienced people. An intelligent software application, integrated into the device, can help technicians
use an OTDR more effectively, without the need to understand or interpret OTDR traces. The user only
sets the fiber span distance and the system automatically determines the pulse width, resolution, and
acquisition time.

10.13.1 Miniature OTDR

The Optical Time Domain Reflectometer (OTDR) is an optoelectronic device used to test the
characteristic of an optical fiber. The OTDR injects a series of optical pulses into the tested fiber and
examines the light scattered or reflected back from the end of the fiber. The strength of the return
pulses is measured and integrated as a function of time.
OTDR functionality can be supported in any Apollo amplifier that supports 100 Mbps OSC with an SFP,
by simply replacing the regular OSC SFP with an OSC SFP that is also able to operate as an OTDR.
This approach provides a low-cost and compact OTDR device, specifically designed to determine the
location of a fiber cut. The SFP used for the OTDR application is OTDR1_L5, which is a 1510 nm, 100
Mbps OSC SFP with OTDR capabilities.

Ribbon Communications Inc. Proprietary 10-190

 Apollo Reference Manual OPT96xx optical cards and modules

The OTDR1_L5 provides the following main functions:

 Operates normally as a 100 Mbps OSC SFP
 OTDR functionality triggered by management commands
 OTDR commands can be sent from a CLI or STMS station.

NOTES:
 OTDR operation requires OTDR SFPs at both span ends
 The total span loss should not be more than 15 dB

For a description of the commands, refer to OTDR Commands.

10.13.2 SFP OTDR commands

The user can control the OTDR by two commands sent from the CLI or STMS stations. These
commands and their outcome are described in this section.
The OTDR control commands are:
 Start OTDR calibration
 Start OTDR test
The OTDR calibration is an action initiated by the user after installation of a new fiber span and each
time after the fiber span is modified or repaired. The user is responsible to perform the calibration.
A "Start OTDR calibration" command results in the OTDR testing of the fiber span connected to the
SFP output. At the end of the calibration test the OTDR reports a list of numbers that represent the
location of points with high reflection. This list is stored by the RCP and used to evaluate the fiber
characteristics in a real test.
After a "Start OTDR calibration" command the following actions are performed:
1. The SFP stops transmitting as an OSC.
2. The SFP starts to transmit OTDR pulses.
3. The “Reference list” that shows the location (in km) of high-reflection points is retrieved.
4. The results are reported to the management station:
a. If the test has been completed successfully and a “Reference list” was achieved a “OTDR
calibration completion" is sent.
b. In case of time-out or another hardware failure a “OTDR calibration failed” message is
reported.
5. The SFP returns to normal operation as an OSC in less than 15 sec.
If a new "Start OTDR calibration" is sent, a new “Reference list” is created, which is overwritten on the
previous.
If no reflection has been detected in a calibration test the “Reference list” will have a single value of 500
km.
The user can read the reflection points detected by the last OTDR test by a debug command.
After a "Start OTDR Test” command the following actions are performed:
1. The SFP stops transmitting as an OSC.
2. The SFP starts to transmit OTDR pulses.

Ribbon Communications Inc. Proprietary 10-191

 Apollo Reference Manual OPT96xx optical cards and modules

3. The “Reference list” that shows the location (in km) of high-reflection points is retrieved.
4. Compare the furthest reported point with the “Reference list” created by the last “calibration test”:
a. If the “furthest reported point” is different from any of the points in the “Reference list” by at
least +/-25 m – it will be considered as a “fiber cut” and its location will be reported to the
management station. )

b. If the “furthest reported point” is equal to one of the reference points +/-25m, the “furthest
reported point” will be reported as the fiber cut with the following warning note:
“Warning: Inconclusive results!!!
Fiber cut is indicated at a reference point”.
c. If no reflection point was detected a “No information” note will be reported.
d. If no “Reference list” exist (for example, because a calibration test was not performed)
“furthest point” will be reported with the following warning:
“Warning: Inconclusive results!!!
Calibration test has not been performed“.
e. In case of time-out or any other hardware failure the message “OTDR test failed” will be
reported.
5. The SFP returns to normal operation as an OSC in less than 15 sec.
The test results are displayed on the management station as "Distance to fiber cut” in units of meter.
The user can read the reflection points detected by the last OTDR test by a debug command.

10.13.3 OTDR_8
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 OPT9904X

Description
The Optical Time Domain Reflectometer (OTDR) is an optoelectronic device used to test the
characteristic of an optical fiber. The OTDR injects a series of optical pulses into the tested fiber and
examines the light scattered or reflected back from the end of the fiber. The strength of the return
pulses is measured and integrated as a function of time.
The OTDR_8 is a double-slot card that includes an integrated OTDR module with an 1610 nm laser and
an 1 x 8 optical switch. You can select one out of eight fibers connected to the card.

Features
 Various OTDR tests including:
 Manual - initiated by the user
 Scheduled - configured by the user to perform periodic test (Daily, Weekly, Monthly, etc.)
 Automatic - initiated by the system management (LightSOFT) in case a LOS is detected
 Saves a reference test for each fiber as a baseline to evaluate test results

Ribbon Communications Inc. Proprietary 10-192

 Apollo Reference Manual OPT96xx optical cards and modules

 Raises alarms in case of fiber-cut or fiber-degradation compared to a reference test

 Provides a visualized OTDR GUI in LightSOFT
 Built-in intelligent software helps technicians use the OTDR more effectively
 Light pulse operates at 1610 nm (outside the C-band) to enable in-service tests
 Includes an 1610 nm passive filter to reject ASE noise (created by stimulated Raman)
 1 x 8 optical switch enables to connect up to eight fibers (one at a time)
 Saves records of test history in LightSOFT database
 In-service and out-of-service tests
 Pre-Raman test - enables evaluation of fiber quality to be connected to a Raman
 Range of 1 km to 250 km (in 1 km steps) with a default value of 80 km
A simplified block diagram of the OTDR module is shown in the following figure.

Simplified block diagram

Card views
General view

Ribbon Communications Inc. Proprietary 10-193

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

Ports

Port marking Quantity Connector Functions

P1 to P8 8 LC 1 x 8 optical switch that enables to select one out of eight
fibers connected to the card.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations).
Off when the card is not assigned.
SW-U Yellow Currently not in use.
LED
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is
no fault in the OTDR_8
OTDR port LEDs
P1 to P8 LED Lights when the fiber connected to the corresponding OTDR port (P1
to P8) is tested.

10.13.4 OTDR1610_8S
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The Optical Time Domain Reflectometer (OTDR) is an optoelectronic device used to test the
characteristic of an optical fiber. The OTDR injects a series of optical pulses into the tested fiber and
examines the light scattered or reflected back from the end of the fiber. The strength of the return
pulses is measured and integrated as a function of time.
The OTDR1610_8S is a single-slot card that includes an integrated OTDR module with a 1610 nm laser
and a 1 x 8 optical switch. You can select one out of eight fibers connected to the card.

Ribbon Communications Inc. Proprietary 10-194

 Apollo Reference Manual OPT96xx optical cards and modules

Features
 Various OTDR tests including:
 Manual - initiated by the user
 Scheduled - configured by the user to perform periodic test (Daily, Weekly, Monthly, etc.)
 Automatic - initiated by the system management (LightSOFT) in case a LOS is detected
 Saves a reference test for each fiber as a baseline to evaluate test results
 Raises alarms in case of fiber-cut or fiber-degradation compared to a reference test
 Provides a visualized OTDR GUI in LightSOFT
 Built-in intelligent software helps technicians use the OTDR more effectively
 Light pulse operates at 1610 nm (outside the C-band) to enable in-service tests
 Includes an 1610 nm passive filter to reject ASE noise (created by stimulated Raman)
 1 x 8 optical switch enables to connect up to eight fibers (one at a time)
 Saves records of test history in LightSOFT database
 In-service and out-of-service tests
 Pre-Raman test - enables evaluation of fiber quality to be connected to a Raman
 Range of 1 km to 250 km (in 1 km steps) with a default value of 80 km
A simplified block diagram of the OTDR module is shown in the following figure.

Simplified block diagram

Ribbon Communications Inc. Proprietary 10-195

 Apollo Reference Manual OPT96xx optical cards and modules

Card views
General view

Front panel

Ports

Port marking Quantity Connector Functions

P1 to P8 8 LC 1 x 8 optical switch that enables to select one out of eight
fibers connected to the card.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations).
Off when the card is not assigned.
SW-U Yellow Currently not in use.
LED
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is
no fault in the OTDR_8
OTDR port LEDs
P1 to P8 LED Lights when the fiber connected to the corresponding OTDR port (P1
to P8) is tested.

Ribbon Communications Inc. Proprietary 10-196

 Apollo Reference Manual OPT96xx optical cards and modules

10.13.5 OTDR test applications

The main OTDR test applications are:
 Determining the location of a fiber cut.
 Providing the characteristics of a fiber span before turning on services (out-of service test).
 Providing characteristics of a fiber span before connecting it to a Raman amplifier. It is most
important to receive a reliable report on the fiber's first 20 km characteristics because Raman
operation depends on high quality fibers.
One of the main uses of the OTDR is for in-service fiber tests that can detect degradation in service
quality carried by the fiber. This can be due to bad splicing connection, fiber bends, damaged fiber, etc.
In such cases maintenance actions, like renewing the splice or replacing problematic parts of the fiber,
can be performed in advance, before a serious fault occurs.

CAUTION: You can run OTDR tests in networks including Raman amplifiers only when
the Raman is not active.

In general, connecting an OTDR to a fiber doesn't affect traffic. However, traffic may affect the OTDR
signal and may cause inaccurate test results. Therefore, the OTDR modules include an internal 1610
nm passive filter that rejects ASE noise at 1610 nm (generated by stimulated Raman lasers).
In addition, to prevent other types of traffic from affecting test results, the OTDR module is connected to
the tested fiber through OTDR filters. Two types of OTDR filter cards are offered:
 CT_OTDR_2 : Used in applications where the OTDR, C-Band, and OSC signals are separate
from each other
 C_OTDR_2 : Used in applications where the C-Band and OSC signals are combined and the
OTDR signal is separate
OTDR operation is based on a light pulse sent into the fiber. The pulse width determines its power; the
wider the pulse, the stronger the power it carries. To be able to test long span fibers, we need a wide
pulse; on the other hand, a wide pulse reduces the resolution of the OTDR test results. The optimal
pulse width to select would be a compromise between these contradictory requirements. In addition, the
width of the pulse generates an error area of several meters within the test results, called the dead-
zone. This error can't be observed by the OTDR module. To improve the accuracy of test results, a
built-in 30 m fiber is connected inside the OTDR module.

Ribbon Communications Inc. Proprietary 10-197

 Apollo Reference Manual OPT96xx optical cards and modules

10.13.6 OTDR one-end test

The following figure shows a typical connection of the OTDR module to fibers for a test from one end.

OTRD fiber test connection

The OTDR connection is typical for -20 dBm EDFA amplifiers fiber testing:
 The user connects the OTDR to the fiber span under test via OTDR filter (CT_OTDR_2 or
C_otdr_2) card
 The OTDR test parameters are automatically set according to the span’s length
 The test enables monitoring of both transmit and receive fibers from a single end
 A Reference Test is performed, and stored as an expected baseline
 The user can set more manual or periodic tests
 If fiber cut or fiber-degradation is detected compared to the reference test, alarms are raised by
the system

Ribbon Communications Inc. Proprietary 10-198

 Apollo Reference Manual OPT96xx optical cards and modules

10.13.7 OTDR two-end test for high power EDFAs

A typical connection of OTDR modules for high power EDFA amplifiers is shown in the following figure.

OTDR connection to high EDFA amplifiers

This configuration is based on the following principals:

 The OTDR is limited to monitor the receive fibers only, because of the high power
 Two OTDR cards are required, one at each end
 This configuration supports both in-service and out-of-service tests

Ribbon Communications Inc. Proprietary 10-199

 Apollo Reference Manual OPT96xx optical cards and modules

10.13.8 OTDR Raman span test

A typical OTDR connection for Raman span testing is shown in the following figure.

OTRD Raman span test

The configuration is based on the following principals:

 An OTDR is required at both ends
 The test is limited to Out-of-Service operation (Raman amplifiers are shut down)
 The OTDR uses built-in OTDR filters on Raman cards

10.14 DCF
Apollo offers a variety of DCF cards to properly compensate for chromatic dispersion. To select the
optimal solution for specific installations, the following cards are available, differing mainly in their
compensation capabilities.
 DCF652_xx
 DCF655_xx
 RM_DCF652_xx

Ribbon Communications Inc. Proprietary 10-200

 Apollo Reference Manual OPT96xx optical cards and modules

10.14.1 DCF652_xx
Supported platforms
 OPT9624
 OPT9608
 OPT9603
 Artemis 1P/2PE/2A/4A

Description
The DCF652_xx is a single-slot DCF card that is suitable for G. 652 compliant fibers. The card is
available for compensation for various distances (5, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 110, or
120 km). The marking xx in the name of the card indicates the compensated distance in km. All
connections to the card are through LC type connectors on the front panel.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 10-201

 Apollo Reference Manual OPT96xx optical cards and modules

10.14.2 DCF655_xx
Supported platforms
 OPT9624
 OPT9608
 Artemis 2A/4A

Description
The DCF655_xx is a double-wide-slot DCF card that is suitable for G. 655 compliant fibers. The card is
available for compensation for various distances (40 km, 80 km, or 120 km). The marking xx in the
name of the card indicates the compensated distance in km. All connections to the card are through LC
type connectors on the front panel.

Card views
DCF655_xx general view

Ribbon Communications Inc. Proprietary 10-202

 Apollo Reference Manual OPT96xx optical cards and modules

10.15 OSC_8
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The OSC_8 is a single-slot optical supervisory channel (OSC) card that provides up to eight OSC
management channels for the Apollo system. The OSC_8 provides the following main functions:
 Eight OSC SFP-based ports providing support for both 1510 nm and 1310 nm links as detailed in
the ports table that follows.
 Interoperability with Apollo optical amplifier OSC ports.
 Up to two cards in Apollo platforms.

Card views
General view

Ribbon Communications Inc. Proprietary 10-203

 Apollo Reference Manual OPT96xx optical cards and modules

Front panel

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the OSC_8.
OSC port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port is
unassigned.
F/L Red LED Lights steadily when a failure is detected in the port. Blinks when a LOS
condition is detected in the port. Off when the port is unassigned.

Ports

Port marking Number Connector Functions

6 SFP  Operates at 100 Mbps
OSC100M(0) to
OSC100M(5)  1510 nm with a typical span of 150Km or
 1310 nm with a typical span of 100Km for CWDM
applications
 Operates at 2 MHz using proprietary format
OSC2M(1) to 2 SFP
OSC2M(2)  1510 nm only used for long spans (typically over 200
km reach).

Ribbon Communications Inc. Proprietary 10-204

11 OPT96xx advanced Layer 1 service
cards
Apollo supports a variety of Layer 1 service cards, providing one of the densest systems in the market.
The Layer 1 cards are designed to support multiple rates and protocol services, thereby reducing the
number of I/O modules and spare parts required at each site.
To support this high density system, Apollo Layer 1 cards are designed as multichannel cards, with
pluggable transceivers providing a pay-as-you-grow option. In addition, tunable transceivers enable
development of a dynamic network from access to core.
Layer 1 cards are available for a range of line rates (10 Gbps, 40 Gbps, and 100 Gbps), in two
configurations:
 As standalone cards, including transponders, muxponders, regenerators, and AoCs.
 As fabric interface cards, used with 1 Tbps universal fabric.
Layer 1 service cards support internal Pseudo-Random Binary Sequence (PRBS) generation and
reception both to and from any OTU2/2e/2f line port. PRBS capabilities enhance the efficiency of
internal PM operations such as loopback testing. PRBS pattern generation testing enables faster
installation and easier management since there is no need for additional optical testers.
Apollo service cards comply with ITU-T standards for 50 GHz and 100 GHz multichannel spacing
(DWDM) using fixed or tunable XFP transceivers. They support PM and GCC in-band management,
with PM for client side signals in the signals' native layer (SDH/SONET and Ethernet).

11.1 Advanced OTN features

The Optical Transport Network (OTN) is based on Recommendation G.709 of the ITU-T and includes
all aspects of optical networking including rates, formats, and optical Wavelength Division Multiplexing
(WDM). The foundations of this technology are based on the well experience and benefits gained from
the SDH and SONET networks including, a layered structure, in-service PM, protection, and other
management functions.
In addition, OTN offers more benefits that improves performance and reduces cost, including:
 Management of optical channels in the optical domain
 Forward error correction (FEC) to improve error performance and enable longer optical signal
reach
Enhanced recommendations were released since the first publication of the G.709, and include:
 Support of new client signals
 ODU0
 GMP
 ODUflex (in two flavors: CBB and GFP)
 Hitless resizing of ODUflex (GFP)
 1.25 Gbps tributary slots (known as PT21 Payload Type)
 Multistage Multiplexing
 Delay Measurement
Several of these features are now supported in Apollo and described in the following sections.

Ribbon Communications Inc. Proprietary 11-1

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.1.1 Understanding ODU0 containers

The world of telecommunications has changed dramatically since OTN emerged in the late 1990s. OTN
was originally defined in ITU-T Recommendation G.709. The initial standard supported three
containers: ODU1, ODU2, and ODU3. The migration towards packet-based networks introduced
Ethernet as natural client signals for the OTN. ITU-T faced the challenge of efficiently supporting these
new client signals while retaining backward compatibility with the installed base.
The rapid growth of GbE in metro networks increased the need for cost-effective transparent transport
of GbE over OTN. Transport equipment already supports GbE over SDH/SONET virtual concatenated
containers. However, this solution would not enable carriers to phase SDH/SONET out of their
networks. Therefore, an OTN-specific solution was required.
Although the existing standard already enabled mapping GbE into ODU1 using transparent GFP
(GFP-T), this approach wasted large amounts of bandwidth and was not acceptable for such a
widely-used client signal. Another solution was to multiplex two GbE signals into the same ODU1 using
GFP's linear extension mode; but this approach leads to the loss of client-level supervision and only
allows networking at the undesirable GFP level. Therefore, a new ODU0 container was added, sized to
hold exactly half the payload area of an ODU1 container. Since each ODU0 can transparently map one
GbE client, the GbE transport capacity is effectively doubled. By definition, ODU0 is a lower-order
ODUk for sub-wavelength networking.

Mapping GbE into ODU1  ODU0 increases mapping efficiency

Ribbon Communications Inc. Proprietary 11-2

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

OTN hierarchy

The main benefits of ODU0 are that this is a switchable entity that is consistent with other ODUk signals
and is optimized for efficient transport of most sub-ODU1 clients. The ODU0 structure is similar to other
OTN containers, including three main areas:
 Overhead area for Operation, Administration, Maintenance, and Provisioning (OAM&P) functions
 Payload area for customers data
 Forward Error Correction (FEC) data

Ribbon Communications Inc. Proprietary 11-3

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Since the payload area of an ODU0 container (half of ODU1) is not enough to transparently transport
GbE, a transcoding method is specified. The 1000BaseX signal (8B/10B coded, nominal bit rate of
1,250,000 kbit/s and a bit-rate tolerance up to +100 ppm) is synchronously mapped into a 75-octet
GFP-T frame stream with a bit rate of 15/16 x 1,250,000 kbit/s +100 ppm (approximately
1,171,875 kbit/s +100 ppm). This process is referred to as timing transparent transcoding (TTT). The
15/16 x 1,250,000 kbit/s +100 ppm signal is then mapped into an OPU0 by means of the generic
mapping procedure (GMP). GMP was also chosen for use when mapping new client signals into OPU1,
OPU2, and OPU3 signals. The main reason for the introduction of GMP is the limited ability of AMP to
conveniently accommodate new client signals with rates that are significantly different than the OPUk
payload rates, or to handle client signals with a clock tolerance significantly greater than +20 ppm.

11.1.2 Understanding ODUflex

ODUflex was introduced to enable efficient client signal mapping also for the newer client signals
produced by evolving services. Experience with Ethernet clients has shown that it is difficult to predict
the rate of future client signals. As Ethernet services have evolved a number of other candidate clients
appeared, such as Fiber Channel and video distribution signals. Most of these would not fit into any
existing ODUk without significant loss of bandwidth. In addition, defining a new container each time a
new client signal is added is impractical. Using ODUk virtual concatenation to map CBR clients is
considered too complex and does not provide homogeneous mapping. For example, mapping a
12 Gbps client signal requires five ODU1 or two ODU2 containers.
The solution is to define a flexible container (ODUflex) that can be "sized" to fit any client rate and thus
occupies the minimum time slots in the higher order ODUk. For example, an FC-400 (Fiber Channel,
4Gbps) can be mapped into an ODUflex occupying four time slots of OPU2. This leaves the other time
slots of the OPU2 free for other use. The ODUflex frame is consistent with the generic ODUk frame.
ODUflex is standardized in two flavors:
 ODUflex (CBR):
 Supports any possible client bit rate as a service circuit transport networks.
 CBR clients use bit-sync mapping into ODUflex (239/238 x client rate).
 ODUflex (packet/GFP):
 Creates variable size packet trunks (containing GFP-F mapped packet data) for transporting
packet flows using L1 switching of LO ODU.
 In principal can be of any size; in practical implementation, set to multiples of the lowest
tributary slot in the network.
CBR clients are mapped into ODUflex using a bit-synchronous mapping procedure (BMP). The
procedure is simple and involves wrapping ODUk/OPUk overhead around the client data. Therefore,
the later exactly fits the ODUflex payload area without the need for justification. The ODUflex is exactly
the right size for its client.

Flexible sizing of ODUflex

Ribbon Communications Inc. Proprietary 11-4

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

To map an ODUflex into a higher order ODUk, the appropriate number of higher order OPUk time slots
is allocated. The selection is arbitrary, but all time slots should be part of the same ODUk. The mapping
of the ODUflex into the ODUk is made through GMP, since both the ODUflex rate and the allocated
time slot rate can vary.
Another application of ODUflex is transport of GFP-encapsulated packet streams, like Ethernet and
MPLS-TP, providing resizable tunnels between L2/L3 switch fabric. The ODUflex make most efficient
use of the OTN bandwidth when configured in exact multiples of the lowest ODTUk.1 in the network.
It might be tempting to consider ODUflex as a generic solution for all CBR client mapping. However,
this is not always reasonable, since client signals with a rate close enough to an existing ODUk can be
mapped more efficiently directly into this ODUk. ODUflex is only preferred if it will occupy fewer time
slots than the smallest fixed-rate ODUk capable of fitting the client signal.
In the current version of Apollo only ODUflex for CBR is supported and only the AoCB card is
supported.

11.1.3 Understanding PT21 (Payload Type = 21)

With ODU0, ODUflex (CBR), and ODUflex (GFP), lower tributary slot granularity than 2.5 Gbps is
required. To support this need, a 1.25 Gbps tributary slot was defined to enable efficient multiplexing of
Low Order (LO) client signals ODUj (j = 0, 1, 2, 3, flex) into High Order (HO) OPUk (k = 2, 3, 4). To
distinguish this structure from the 2.5 Gbps structure, a new Payload Type, 21 (PT = 21), was
designated, which is communicated in the Payload Structure Identifier byte of the High Order OPUk
Overhead.
Similar to an ODU2 that is mapped into four 2.5 G tributary slots of an OPU3 (ODTU2.3, PT = 20), it
can be mapped into eight 1.25 G tributary slots of an OPU3 (ODTU2.3, PT = 21). Mapping of ODU1 to
OPU2/3 and ODU2 to OPU3 uses AMP regardless, if the tributary slots used are 1.25 Gbps or 2.5
Gbps.
Because ODU0 was defined before ITU-T G.709 Issue 3 (which included the Payload Type 21), ODU0
is mapped into one 1.25 Gbps tributary slot of an OPU1 using AMP (ODTU0.1). All other mapping of
ODUj into 1.25 Gbps tributary slots of OPUk use GMP.
The following table summarizes the payload type of mapping ODUj into OPUk.

Mapping of ODUj to OPUk summary

2.5 Gbps tributary slots 1.25 Gbps tributary slots

OPU2 0PU3 OPU1 OPU2 OPU3 OPU4
ODU0 --- --- AMP GMP GMP GMP
(PT = 20) (PT = 21) (PT = 21) (PT = 21)
ODU1 AMP AMP --- AMP AMP GMP
(PT = 20) (PT = 20) (PT = 21) (PT = 21) (PT = 21)
ODU2 --- AMP --- --- AMP GMP
(PT = 20) (PT = 21) (PT = 21)
ODU2e --- --- --- --- GMP GMP
(PT = 21) (PT = 21)
ODU3 --- --- --- --- -- GMP
(PT = 21)
ODUflex --- --- --- GMP GMP GMP
(PT = 21) (PT = 21) (PT = 21)

Ribbon Communications Inc. Proprietary 11-5

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

PT21 is supported for the following Apollo cards:

 FIOMR_16B
 FIO10_5B
 AoC10B
 FIO100

11.2 AoC10 and AoC10B

Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The AoC10/AoC10B provides 10 Gbps ADM service on a single-slot card. It supports up to 16 client
interfaces, which are multiplexed into the G.709 multiplexing structure and sent via two OTU2 line
interfaces.
Any of the client interfaces can be configured to accept an STM-1/OC-3, STM-4/OC-12, GbE,
FC/FC2/FC4, OTU-1, STM-16/OC-48, DVB-ASI, SDI, or HD-SDI signal. The card has integrated
cross-connect capabilities, providing more efficient utilization of the lambda. Any of the signals can be
added or dropped at each site, while the rest of the traffic continues on to the next site. Broadcast TV
services can be dropped and continued (duplicated), eliminating the need for external equipment to
provide this functionality.

Features
 16 SFP-based client ports, software configurable to support GbE, 1G FC, 2G FC, 4G FC, STM-
1/OC-3, STM-4/OC-12, STM-16/OC-48, and OTU1 services
 Two independent XFP-based OTU2 line ports
 Supports new tunable XFP transceivers
 Can be used as a multi-rate combiner up to OTU2
 Can operate as two separate muxponders with sets of eight clients multiplexed into one OTU2 line
 Supports GFEC, EFEC (I.4 and I.7), and ignore-FEC modes towards the line
 Provides GFEC on the client side when it is configured to OTU1
 GCC features:
 GCC supported in standard (full rate) mode.
 Up to 2 GCC channels for OTU2/OTU2e supported.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.
 Supports Subnetwork Connection Protection (SNCP) mechanisms
 Complies with ITU-T standards for 50 GHz and 100 GHz multichannel spacing (DWDM)
 Supports in-service module insertion and removal without any effect on other active ports
 Supports interoperability with XDM AoC cards

Ribbon Communications Inc. Proprietary 11-6

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

IMPORTANT: The AoC10B card is very similar to the AoC10. Both cards support the
same functionality except for the following OTN features, supported only by the AoC10B.

Features supported only by the AoC10B include:

 ODU0 (instead of OPTM-8) protection instead of ODU1; improves ODU resources utilization
 ODUflex including:
 Standard mapping of FC-4
 New client HD-SDI 3G based ODUflex
 New OTU1 port including two ODU0 containers

Card views
General view

Ribbon Communications Inc. Proprietary 11-7

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Front panel

The port number is indicated under/above each port. The markings T (transmit) and R (receive) near
each port indicate only the port's output and input connections and don't relate to the port LEDs.

Usage guidelines
Several limitations apply when configuring AoC10B/AoC10 ports to specific rates from V8.2 and on.
These limitations are described in the following table. X in the table indicates the allowed (supported)
configuration option.

AoC10/AoC10B port configuration rules

Port No. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Rate
FC-4 X X X X

STM-16/ FC2G/OTU1/HD-SDI X X X X X X X X

STM-1/4/GBE/FC- X X X X X X X X X X X X X X X X
1G/DVB/SDI

 STM-16/ FC2G/OTU1/HD-SDI port assignment is rejected if the following odd port is assigned.
 When an STM-16/ FC2G/OTU1/HD-SDI port is assigned, an assignment to the following odd port
is rejected.
 When an FC-4 port is assigned, 3 following port assignments are rejected and an FC-4 port
cannot be assigned if any of the 3 following ports are already assigned.
 Any assignment of a client that requires more than the allocated BW of 20G is rejected.
 When an HD-SDI port is assigned, the two ports following it must remain empty. The third one can
be assigned to a port type occupying an ODU0, for example ETY1G.

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the AoC10/AoC10B.

Ribbon Communications Inc. Proprietary 11-8

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Marking Item Functions

Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter is
off.
F/L Red LED Lights steadily when a BIT fault is detected in the pluggable transceiver, or
the supply voltage or temperature is OOR. Blinks when a LOS condition is
detected in the port.

11.2.1 Assignment of AoC10 as AoC25

The AoC10 can be assigned as an AoC25 operating in 2.5 Gbps mode, and enabling the user high
flexibility in implementation of more applications with the same hardware. When assigned as an AoC25
the card can work as a Multi-service OTU1 muxponder and/or transponder.
For convenience, the front panel of the AoC10 is illustrated again in the following figure.

Front panel: AoC10/AoC10B

The two Line ports (port 16 and 17) are disabled in this mode, and only the 16 client ports are used.
The first eight ports (Port 0 to Port 7) are configured as Client ports, and the last eight (Port 8 to Port
15), as Line ports.
The AoC25 provides the following main features:
 8 x SFP-based client ports, software configurable to support GbE, 1G FC, 2G FC, STM-1/OC-3,
STM-4/OC-12, and STM-16/OC-48 services
 8 x SFP-based line ports configured to ODU1
 Quadruple OTU1 muxponder (two client ports connected to a single line port)
 Y-protected Quadruple OTU1 muxponder (two client ports connected to a double line ports)
 8 x OTU1 transponder card (one client connected to a single line port)
 Y-protected Quadruple OTU1 transponder (one client connected to a double line ports)
The following rules apply for assignment of the client ports (Port 0 to Port 7) and Line ports (Port 8 to
Port15):
 Port 0 to Port 7 can be assigned as clients only.
 Assignment of the client ports to OTU1 will be rejected.
 Ports 0 and 1, 2 and 3, 4 and 5, 6 and 7 are couples.
 If a member of a couple is assigned to a port type occupying ODU-slot, the second member can't
be assigned to a type occupying ODU1.
 All cross-connects must be explicitly configured by the user.

Ribbon Communications Inc. Proprietary 11-9

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 Cross-connects are allowed only between ports 0 to 7 and ports 8 to 15.

 Cross-connects between client ports or between line ports are not supported.

11.3 TR10_4
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TR10_4 is a single-slot 10 Gbps transponder card that maps the client signal according to G.709
and transmits a colored signal towards the network. The card includes two transponders (client and
line) providing full functionality in a space saving form factor and operating in an East/West
configuration. Each one can be configured independently for transponder or regenerator applications.

Features
 20 Gbps total capacity
 Two pairs of independent 10 Gbps transponders (client + line)
 Multiservice client interfaces, software configurable, supporting:
 10G LAN
 GFP extended overhead (OH) mapping to ODU2
 BMP mapping to ODU2e (overclocking)
 STM-64/OC-192
 OTU2/OTU2e
 FC800/FC1200
 Client signals mapped to OTU2, OTU2e, and OTU2f
 Complies with ITU-T standards for 50 GHz and 100 GHz multichannel spacing (DWDM) using
fixed or tunable XFP transceiver
 Supports PM and GCC in-band management, with PM for client side signals in the signals' native
layer (SDH/SONET and Ethernet).
 GCC features:
 GCC supported in standard (full rate) mode.
 Up to 2 GCC channels for OTU2/OTU2e supported.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.
 Provides GFEC, EFEC (I.4 and I.7), and no FEC modes towards the line. GFEC is also available
on the client side when it is configured to OTU2 regeneration mode. In addition, the TR10_4 offers
an optional ignore-FEC mode.
 Can be configured for the following applications:
 Two independent transponders. Services in this mode can be configured as either
unprotected or with full equipment protection.
 Y-protected transponder with a single client.

Ribbon Communications Inc. Proprietary 11-10

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Card views
General view

Front panel

The transponder ports are marked C1 for client and L1 for line for the first transponder and similarly C2
and L2 for the corresponding ports of the second transponder.

Ribbon Communications Inc. Proprietary 11-11

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the TR10_4.
Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter
is off.
F/L Red LED Lights steadily when a BIT fault is detected in the pluggable transceiver, or
the supply voltage or temperature is Out of Range (OOR). Blinks when a
LOS condition is detected in the port.

11.4 Encrypted transponder/muxponder cards

The growing demand for bandwidth in metro networks is driven by the deployment of new infrastructure
for quadruple play (voice, data, video and mobile) delivery, business data, storage services and cellular
backhaul. Metro Core networks are based on ring, star and/or point-to-point topologies. The main
objective of encrypted transponder/muxponder cards is to provide a Multi-Service, low cost, minimal
size encrypted solution to customers for DWDM networks.
The Apollo offers the following encryption cards:
 TR10_4EN
 TM200EN
 TM100_2EN
 TM200ENB
 TM100_2ENB
These cards are targeted for applications that will be used in small regional or metro access networks
requiring flexible grooming 10G to OTU2 and 10G\100G OTU4\OTUC2, encrypted or non-encrypted.
Cryptography is a complex subject that involves industry standards, practices and mathematics; these
subjects are out the scope of this manual. However, the next section presents some basic terminology,
dealing with cryptography, which will facilitate the understanding of the encrypted cards functionality.
Encrypted card functionality is described in the sections following cryptography terminology.

11.4.1 Cryptography: basic terminology

This section provides descriptions and definitions of several terms used in cryptography to help you
understand the functionality of the encryption system in the TR10_4EN and TM200EN.
In general, cryptography refers almost exclusively to encryption, which is the process of converting
meaningful information (called plaintext) into meaningless text (called ciphertext).
Encryption: the process of turning a clear-text message into a data stream which looks like a
meaningless and random sequence of bits (ciphertext).
Decryption: the process of turning ciphertext back into plaintext (revers process of encryption).

Ribbon Communications Inc. Proprietary 11-12

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Algorithm (cryptographic): also known as cipher; a mathematical function which uses plaintext as
the input and produces ciphertext as the output and vice versa.
Key: a word or phrase that modifies the encryption/decryption process in such a way that knowledge of
the algorithm alone is insufficient to decipher an enciphered message.
Asymmetric Algorithm: an algorithm in which the key used for encryption is different from that used
for decryption. Also known as public key cryptography.
Symmetric Algorithm: an encryption algorithm where the encryption key is the same as the decryption
key, or where one key is easily calculated from the other. The sender and receiver have to agree on a
key before they can communicate securely.
Private Key: the secret part of a private key/public key pair used in public key cryptography. The
Private Key is normally known only to the key owner. Messages are encrypted using the Public Key and
decrypted using the Private Key. For digital signatures, however, a document is signed with a Private
Key and authenticated with the corresponding Public Key.
Public Key: the encryption key is made public but only the person who holds the corresponding private
key can decrypt the message. This concept was first proposed by Diffie and Hellman in 1975.
Man in the Middle Attack (MIMA): is a form of actively listening to or eavesdropping on network traffic
of one or more computer hosts. In this method, the attacking computer will make an independent
connection with each identified computer host or “victim.” Once establishing these connections, the
computer will then relay messages between the victims creating the illusion of each computer
communicating with the other via a secure connection. This dialogue; however, is fully controlled by the
rogue computer or attacker. In order for the attack to be a true MIMA, 100% of the network traffic has to
be controlled. The attack focuses on the lack of mutual authentication between the two victims.
Message Integrity Check (MIC): a cryptographic algorithm value which is computed on a per-message
basis, to allow the integrity of the message to be validated to prevent the MIMA. For encrypt, it is an
output which is transmitted at the end of each message. For decrypt, it is an input which is compared
against the recomputed value. Essentially, it is a secure checksum.
Authentication: the process of identifying an individual, usually based on a username and password. It
makes sure that the individual at the other end (of the network) is who he or she claims to be.
Authorization: is the process of giving individuals access to system objects based on their identity.
Digital Signature: an encrypted message digest which is appended to a plaintext or encrypted
message to verify the identity of the sender. The signature is encrypted with the user's private key and
can only be decrypted with the corresponding public key. The same key pairs may be used for
signature and encryption purposes but separate key pairs for each purpose are usually recommended.
Digital Certificate: an electronic "passport" that allows a person, computer or organization to exchange
information securely over the Internet using the public key infrastructure.
X.509 certificate: a digital certificate that uses the widely accepted international X.509 public key
infrastructure (PKI) standard to verify that a public key belongs to the user, computer or service identity
contained within the certificate. The certificate includes the following main subjects:
 User's ID information
 User's public key
 Period of validity
 Digital signature of the issuer
SSL (Secure Sockets Layer): commonly-used protocol for managing the security of a message
transmission on the Internet. SSL uses a program layer located between the Internet's Hypertext
Transfer Protocol (HTTP) and Transport Control Protocol (TCP) layers.

Ribbon Communications Inc. Proprietary 11-13

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

PKI (Public Key Infrastructure): enables users of a basically unsecure public network such as the
Internet to securely and privately exchange data and money through the use of a public and a private
cryptographic key pair that is obtained and shared through a trusted authority.
CA (Certificate Authority): is an authority in a network that issues and manages security credentials
and public keys for message encryption. CA checks with a registration authority (RA) to verify
information provided by the requestor of a digital certificate. If the RA verifies the requestor's
information, the CA can then issue a certificate.
Advanced Encryption Standard (AES): is an encryption algorithm for securing sensitive but
unclassified material by U.S. It was developed to find a more robust replacement for the Data
Encryption Standard (DES). Its specification includes an symmetric algorithm using block encryption of
128 bits in size, supporting key sizes of 128, 192 and 256 bits.
Internet Key Exchange (IKE): is an IPsec (Internet Protocol Security) standard protocol used to
ensure security for virtual private network (VPN) negotiation and remote host or network access.
Diffie-Hellman key exchange: also called exponential key exchange, is a method of digital encryption
that uses numbers raised to specific powers to produce decryption keys on the basis of components
that are never directly transmitted, making the task of a would-be code breaker mathematically
overwhelming.
Initialization Vector (IV): a cryptographic algorithm input which varies on a per-message basis to
ensure that no two messages of possibly similar data are ever encrypted the same way. The IV is
generated at the encryptor and sent to the decryptor prior to the message – it is not secret. The IV must
be a Nonce “number used once”, for which a simple message counter is sufficient.

11.4.2 Configurable Diffie Hellman (DH) groups

Diffie-Hellman (DH) is a ubiquitous cryptographic technique used for establishing symmetric encryption
keys between two encryption peers in encryption products. In the symmetric key cryptography, both the
encrypter (sender) and decrypter (receiver) use the same cryptographic key to encrypt and decrypt the
data respectively. However, the encryption keys need to be established over an unsecured network,
where there may be eavesdroppers watching the parameters exchanged during key-establishment. DH
facilitates secure establishment of keys over unsecured channels. DH and its variants are used in
virtually all non-military grade products today.
Security/cryptographic-strength of the DH technique mainly depends on the specific DH variant and/ or
length of the modulus used. The specific variant of DH is defined by static, globally known,
standardized, pre-shared parameters called DH-groups. A given DH Group is known to encryption
peers that need to establish common encryption keys. Typically a DH Group is also publicly known and
standardized, so that its integrity and security can be scrutinized and trusted. We offer a range of DH
groups to choose from; each instance of key-establishment can be configured for a specific DH group.
The following table shows the cards that support the different DH Groups.

Ribbon Communications Inc. Proprietary 11-14

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Cards supporting DH Groups

Modules DH Groups
 TR10_4EN  MODP-Group-5
 TR10_12EN  MODP-Group-14
 HIO400EN  MODP-Group-15
 TM100_2EN  MODP-Group-16
 MIO200EN  MODP-Group-17
 TM200EN  MODP-Group-18
 OPT9901X  MODP-Group-24
 ECDH-Group-SECP256R1
 ECDH-Group-SECP384R1
 ECDH-Group-SECP521R1
 TM200ENB  MODP-Group-14
 TR10_12ENB  MODP-Group-15
 TM100_2ENB  MODP-Group-16
 MODP-Group-17
 MODP-Group-18
 ECDH-Group-SECP256R1
 ECDH-Group-SECP384R1
 ECDH-Group-SECP521R1

11.5 TR10_4EN
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TR10_4EN is a single-slot 10 Gbps transponder card with encryption capabilities. The card maps
the client signal according to G.709 to OTU2/ODU2e/ODU2f. The encryption is performed at the optical
ODU2/2e layer, using an encryption system and sends it to the line. The encryption system encodes
the data with AES-GCM 256 algorithm to ensure a high security level. In addition to its main role as a
transponder, the TR10_4EN provides encryption on the optical (ODU2/e) layer.
The card includes two separate transponders (client and line) providing full functionality in a space
saving form factor and operating in an East/West configuration. The line traffic at OTU2 is encrypted
using the AES (256 bit) algorithm.

Ribbon Communications Inc. Proprietary 11-15

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Features
 Two pairs of independent 10 Gbps transponders (client + line),for a total capacity of 20 Gbps.
 Multiservice client interfaces, software configurable, supporting:
 10 GbE.
 STM64.
 OTU2/OTU2e.
 FC800/FC1200.
 OC192.
 Supports line for OTU2, OTU2e and OTU2f.
 FEC support:
 Regular FEC on all ports when configured to OTU2/OTU2e/OTU2f (OTU2f only on the line).
 EFEC I4 and I7 on all ports when configured to OTU2/OTU2e/OTU2f.
 GCC features:
 GCC supported in standard (full rate) mode.
 Up to 2 GCC channels for OTU2/OTU2e supported.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.
 Support port protection using splitter/coupler and Y protection.
 Powerful encryption capabilities:
 Wire speed mode with no added latency.
 When installed in two NE peers, they can communicate through a secured line at the ODU2
level, using an encrypted line (encryption is AES-GCM 256).
 NEs provisioned to support such an encrypted line authenticate each other using
private/public key authentication. Private/Public key is generated by the NE.
 NEs provisioned to support an encrypted line exchange symmetric encryption keys for the
encryption algorithm using Diffie-Hellman group 5, 14, and 24 algorithms.
 Key management using IKE:
 IKE messages can be transmitted using GCC0, GCC1, GCC2, OSC or out of band, like
common management packets. Hitless keys change.
 When the Key exchange trigger is sent, in next frame the encrypt and decrypt side uses
the new key.
 Implemented encryption algorithms:
 AES-GCM 256 – Advanced Encryption Standard, key length 256 bits. The AES algorithm
is a symmetric block cipher that can encrypt and decrypt information.
 IV – Initialization Vector. A cryptographic algorithm input which varies on a per-message
basis to ensure that no two messages of possibly similar data are ever encrypted the
same way. The IV is generated at the encryptor and send it to the decryptor prior to the
message – it is not secret. The IV must be a Nonce “number used once”, for which a
simple message counter is sufficient.
 MIC – Message Integrity Check. A cryptographic algorithm value computed on a per-
message basis, to allow the integrity of the message to be validated. For encrypt, it is an
output which is transmitted at the end of each message. For decrypt, it is an input which
is compared against the recomputed value. Essentially, it is a secure checksum.

Ribbon Communications Inc. Proprietary 11-16

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 Symmetric keys are rotated periodically to increase security. The period is software
configurable from one minute up to one hour in steps of one minute.
 Keys remain synchronized and encrypted traffic experience no hit upon RCP switchover.
 Symmetric keys are not equal on both direction (i.e. KeyA-> B is not the same as KeyB->A).
 Key rotation doesn't create any traffic hit.
 Card encryption logic supports 2 keys in parallel (i.e. Keyn and Keyn+1).
 Minor alarm is rise upon a failure on negotiating the symmetric key.
 Major alarm is rise when the IV counter is full.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 11-17

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Usage guidelines
 Port 0 and port 2, labeled C1 and C2, are client ports only (even in case of OTU2 regenerators)
 Ports 1 and 3, labeled L1 and L2, are line ports only.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the TR10_4EN.
Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Lights steadily when a BIT fault is detected in the pluggable transceiver,
or the supply voltage or temperature is Out of Range (OOR). Blinks
when a LOS condition is detected in the port.

Functional block diagram

Ribbon Communications Inc. Proprietary 11-18

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.5.1 Optical encryption in TR10_4EN

This section provides a brief description of traffic encryption/decryption process in Apollo peer NEs,
equipped with TR10_EN.

Stage 1 - creating the NE key pairs and certificate

Creating the NE key pairs and certificate

 The NE can receive the key pairs (private key + public key) in one of the following two modes:
 Full secure (Manual) - the key pairs are created elsewhere and transported to the NE site in
an encrypted file, and then loaded manually through a local craft terminal (LCT).
OR
 Automatic - the LCT or STMS instructs the NE to create the key pairs itself using an internal
generator.
 In both modes, the NE creates and self-signs its X.509 certificate, that contains its public key.
 The private key always remains within the NE in protected non-volatile memory.

Ribbon Communications Inc. Proprietary 11-19

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Stage 2 - distributing the NE certificate to the STMS

Distributing the NE certificate to the STMS

 The STMS obtains the NE certificate based on the two modes:

 Full secure (Manual) - the certificate is physically transported to and locally installed in the
STMS.
 Automatic - the STMS opens an SSL session with the NE (using a temporary default NE
certificate) and then uploads the new certificate.

Ribbon Communications Inc. Proprietary 11-20

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Stage 3 - distributing the certificates to the NE peers

Distributing the certificates to the NE peers

 NE-A and NE-B are defined as peer devices.

 Through manual entry to the STMS of the peer IP addresses.
 From an NMS as part of a trail creation process.
 The STMS distributes the certificates with the public keys over SSL sessions
 NE-A receives NE-B’s Certificate/Public key
 NE-B receives NE-A’s Certificate/Public key

Ribbon Communications Inc. Proprietary 11-21

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Stage 4– creating a shared key and beginning encryption

Creating a shared key and beginning encryption

 NE-A and NE-B use their private keys and each other’s public keys to create a symmetric session
key.
 This is done using Diffie-Hellman Group 5, 14, and 24 algorithms.
 Symmetric key strength is AES256-GCM.
 This session key is used to encrypt the data transported on the WDM channel.
 The keys are changed periodically. The time is configurable (typically keys are changed each
hour).

Ribbon Communications Inc. Proprietary 11-22

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.5.2 TR10_4EN protection schemes

The TR10_4EN supports OCH 1 + 1 add and drop equipment protection as well as Y protected add and
drop for facility protection. These protections are activated in less than 50 msec, and operate even
when the main controller (RCP) is not installed or has failed.
OCH 1 + 1 network and hardware protection, is implemented via external splitter/coupler and a built-in
mechanism providing switching capabilities. The OCH protection is activated based on OTN
Performance Monitoring (PM) that leads to signal degrade (SD) or loss of signal (LOS). The following
figure shows an example of OCH 1 + 1 protection for the TR10_4EN.

OCH 1+1 protection scheme for TR10_4EN

Triggers for protection include extracting the TR10_4EN, line or client SFP+ transceiver, or failure of
SFP+.
Protection at the service level is supported, using splitters/couplers or Y cables (which reduces the cost
of the solution and saves slots in the passive platform).
In addition internal Y protection in a single card is supported as well, using 2 lines and one client on the
same card. The Y protection is activated based on OTN Performance Monitoring (PM) that leads to
signal degrade (SD) or loss of signal (LOS). Only ports C1 L1, and L2 can be configured for this type of
protection.

11.6 TR10_12/TR10_12R
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TR10_12/TR10_12R is a single-slot 10 Gbps transponder card that maps the client signals
according to G.709 and transmits a colored signal towards the network. The card includes six
transponders (client and line) providing full functionality in a space saving form factor and operating in
an East/West configuration. They can also be configured as six regenerators between the line ports.

Ribbon Communications Inc. Proprietary 11-23

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

NOTE: The TR10_12 card has been designated as end of life, and has been replaced by
the TR10_12R. The same feature description applies to both cards. The TR10_12R is fully
interoperable with the TR10_12; there are no restriction on use of the TR10_12R.

Features
 60 Gbps mapping capacity.
 Six pairs of independent 10 Gbps transponders (client + line).
 Client and line ports based on SFP+.
 Supports tunable SFP+ transceivers.
 Supports DWDM, CWDM, and non-color transceivers.
 Multiservice client interfaces, software configurable to support:
 10G LAN
 GFP extended overhead (OH) mapping to ODU2
 BMP mapping to ODU2e (overclocking)
 STM-64/OC-192
 OTU2/OTU2e
 FC800/FC1200
 FC1200 transponder is supported in overclocking mode only with OTU2e line rate.
 FC800 transponder is supported mapping the signal to ODUflex.
 Line ports configurable to support OTU2 and OTU2e.
 Complies with ITU-T standards for 50 GHz and 100 GHz multichannel spacing (DWDM) using
fixed or tunable SFP+ transceiver.
 Supports PM and GCC in-band management, with PM for client side signals in the signals' native
layer (SDH/SONET and Ethernet).
 GCC features:
 GCC supported in standard (full rate) mode.
 One GCC supported per port (OTU2/OTU2e), configurable to either GCC0, GCC1, or GCC2,
user selectable.
 Provides GFEC and EFEC (I.7) modes towards the line. GFEC is also available on the client side
when it is configured to OTU2 regeneration mode. In addition, the TR10_12/TR10_12R offers an
optional ignore-FEC mode.
 Can be configured for the following applications:
 Six independent transponders. Services in this mode can be configured as either unprotected
or with full equipment protection.
 Y-protected transponder with a single client.
 Up to four Y-protected transponders per card.
 Six independent regenerators using line ports.

Ribbon Communications Inc. Proprietary 11-24

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Card views
General view

Ribbon Communications Inc. Proprietary 11-25

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Front panel

Usage guidelines
The transponder ports are numbered (0) to (11). Each port can be configured as client or line, with a
maximum of six client ports.
Any client port can be configurable to support OTU2/2e B&W or colored (fixed) services.
Any line ports can be configured to OTU2/2e B&W or colored (fixed or tunable) services.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the TR10_12/TR10_12R.
Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter
is off.
F/L Red LED Lights steadily when a BIT fault is detected in the pluggable transceiver, or
the supply voltage or temperature is Out of Range (OOR). Blinks when a
LOS condition is detected in the port.

Ribbon Communications Inc. Proprietary 11-26

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Functional block diagram

11.7 TR10_12ULL
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TR10_12ULL is a single-slot 10 Gbps transponder card that maps the client signals according to
G.709 and transmits a colored signal towards the network. The card has 12 ports:
 Four dedicated for ULL (Ultra Low Latency) transponder channels with very low latency for FC16,
FC12, and ETY10GOC clients.
 Eight ports can be configured as four independent transponders
TR10_12ULL includes six transponders (client and line) providing full functionality in a space saving
form factor and operating in an East/West configuration. The eight regular ports can also be configured
as four regenerators between the line ports.

Ribbon Communications Inc. Proprietary 11-27

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Features
 40 Gbps mapping capacity.
 Four pairs of independent 10 Gbps transponders (client + line).
 Client and line ports based on SFP+.
 Supports tunable SFP+ transceivers.
 Supports DWDM, CWDM, and non-color transceivers.
 Multiservice client interfaces, software configurable to support:
 10G LAN.
 STM-64/OC-192.
 OTU2/OTU2e.
 FC800/FC1200.
 FC1200 transponder is supported in overclocking mode only with OTU2e line rate.
 FC800 transponder is supported mapping the signal to ODUflex.
 Line ports configurable to support OTU2 and OTU2e.
 Complies with ITU-T standards for 50 GHz and 100 GHz multichannel spacing (DWDM) using
fixed or tunable SFP+ transceiver.
 Supports PM and GCC in-band management, with PM for client side signals in the signals' native
layer (SDH/SONET and Ethernet).
 GCC features:
 GCC supported in standard (full rate) mode.
 One GCC supported per port (OTU2/OTU2e), configurable to either GCC0, GCC1, or GCC2,
user selectable.
 Provides GFEC and EFEC (I.7) modes towards the line. GFEC is also available on the client side
when it is configured to OTU2 regeneration mode. In addition, the TR10_12ULL offers an optional
ignore-FEC mode.
 Can be configured for the following applications:
 Four independent transponders. Services in this mode can be configured as either
unprotected or with full equipment protection.
 Y-protected transponder with a single client.
 Up to two Y-protected transponders per card.
 Four independent regenerators using line ports.

Ribbon Communications Inc. Proprietary 11-28

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 11-29

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Ports
The transponder ports are numbered (0) to (11). Each port can be configured as client or line, with a
maximum of six client ports. The limitation of six client ports refers to the eight regular ports only, in
addition of the ULL ports.
The following table describes the TR10_12ULL front panel component functionality.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the TR10_12ULL.
Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Lights steadily when a BIT fault is detected in the pluggable transceiver,
or the supply voltage or temperature is Out of Range (OOR). Blinks when
a LOS condition is detected in the port.

11.7.1 ULL channels for transponder applications

ULL channels for use in ultra-low latency transponder applications are implemented through direct
connections of a pair of line ports in the TR10_12ULL card. The ports are connected via the internal
EDC (Electronic Dispersion Compensation) module, which also features 2 x 2 switching.
Two pairs of line ports in the TR10_12ULL support this functionality:
 (1) and (3)
 (9) and (11)
An example of a ULL channel is shown in the following figure.

Ribbon Communications Inc. Proprietary 11-30

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

ULL channel block diagram example

The non-colored signal is connected to the SFP+ of port (1) on the TR10_12ULL front panel (that acts
as a "client input"). This SFP+ is connected at the other end to the EDC P4 and switched to P3 at the
opposite side of the EDC; the output of this channel (P3 of the EDC) is directly connected to the second
SFP+ on one side; the other side of the SFP+ is connected to port (3) on the TR10_12ULL front panel.
According to the required application, the second SFP+ is selected at the rate of the corresponding
client input signal (FC1200/FC1600, or 10 GbE LAN) or if a colored signal is required at the output, a
DWDM SFP+ is selected. This application only connects the signal through the SFP+ transceivers and
EDC module without passing the mapper, forming a ULL channel.
The ULL channel is characterized by the following features:
 PM is not supported on these ports, only LOS alarm
 ULL port has a new sub-interface (dummy) to configure XC
 When LOS is detected on one of the ports of the ULL transponder the other port shuts down its
laser
 Latency is less than 1 µsec for FC12, FC16, and ETY10GOC clients
The protection scheme for the ULL ports is based on the following principals:
 The protected ports are on two cards located in adjacent slots in the platform
 The card types are identical
 The ports carry identical services
 The port numbers on the two cards are identical
The following figure shows a typical protection scheme for the ULL ports.

Ribbon Communications Inc. Proprietary 11-31

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Protection scheme for ULL ports

11.8 CMR40B
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The CMR40B is a double-slot multiservice combiner card that supports 4 x 10G
LAN/STM-64/OC-192/OTU2/OTU2e aggregation to OTU-3e. It enjoys enhanced noise tolerance with
improved chromatic dispersion tolerance, and offers good bandwidth efficiency. It reduces the number
of wavelengths, increases capacity, and simplifies management, and can be used in both metro/core
and long-haul networks.
The CMR40B uses a coherent receiver and DP-DQPSK modulation format. The client side utilizes
XFPs for 10G interfaces.

Features
 4 x client interface ports supporting:
 STM-64/OC-192
 10 GbE LAN
 Overclocking Sup43.7.1
 10 GbE WAN
 OTU2
 OTU2e
 FC800
 FC1200
 Each client signal can be configured independently of the other clients
 Fully tunable line side DWDM port supporting up to 88 channels, and available in Dual
Polarization Differential Quadrature Phase Shift Keying (DP-DQPSK) modulation format
 Optimized for long-reach transmission over older fiber infrastructures with high PMD

Ribbon Communications Inc. Proprietary 11-32

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 Complies with ITU-T standards for 50 GHz and 100 GHz multichannel spacing (DWDM)
 Supports PM and GCC in-band management, with PM for client side signals in the signals' native
layer (SDH/SONET and Ethernet)
 GCC features:
 GCC supported in standard (full rate) mode.
 One GCC supported per port (OTU2/OTU2e), configurable to either GCC0, GCC1, or GCC2,
user selectable.
 OTU3e Long haul line with 10% EFEC I.7 (EFEC7_10)
 OTU-2 client supports FEC and EFEC7
 Full support of RMON on 10 Gbps Ethernet ports
 Standard mapping per ITU-T G.709 Rev.3
 Payload Type (PT) 21 complies with ITU-T G.709, Edition 3
 CD and GDG fiber parameters measured for accurate compensation (can be displayed to the
user)
 Supports Client Signal Fail (CSF) alarm for easy client failure identification

Card views
General view

Front panel

Usage guidelines
Client ports are numbered 0 to 3 and labeled C1 to C4. Line port is port number 4 and labeled LINE.

Ribbon Communications Inc. Proprietary 11-33

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the TR10_4.
Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Lights steadily when a BIT fault is detected in the pluggable
transceiver, or the supply voltage or temperature is OOR. Blinks when
a LOS condition is detected in the port.
Line LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
LOS Red LED Blinks when a LOS condition is detected in the port.

11.9 CMR100 and CMR100L

Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The CMR100/CMR100L double-slot combiner (muxponder) interfaces to any combination of ten of the
following client signals through XFPs, and maps them into a 100 Gbps colored line signal for WDM
network transport, according to the G.709 standard: 10GbE/STM64/OC192/FC8/FC10/OTU2/OTU2e. It
occupies a double slot in Apollo platforms.
The CMR100/CMR100L uses DP-QPSK modulation, a coherent receiver, DSP processing, and soft
decision forward error correction, for superior noise tolerance, and an exceptional ability to mitigate CD
and PMD impairments.
The CMR100 is optimized for Ultra Long Haul networking applications, and the CMR100L supports
regional applications. While the TR100L does not support single fiber bi-directional WDM operation, in
terms of all other capabilities, the cards are identical and they are interoperable with each other. The
client side utilizes XFPs for 10G interfaces.
The CMR100/CMR100L offers the following main features:
 10 x client interface ports supporting:
 STM-64/OC-192
 10 GbE LAN
 10 GbE WAN

Ribbon Communications Inc. Proprietary 11-34

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 OTU2
 OTU2e
 FC1200
 FC800
 Each client signal can be configured independently of the other clients
 Fully tunable line side DWDM port supporting up to 88 channels, and available in Non Return to
Zero Diverse Polarization Differential Quadrature Phase Shift Keying (NRZ DP QPSK) modulation
format
 Optimized for long reach transmission over older fiber infrastructures with high PMD
 Complies with ITU T standards for 50 GHz and 100 GHz multichannel spacing (DWDM)
 One stage multiplexing according to latest ITU-T standards
 Supports PM and GCC in band management, with PM for client side signals in the signals' native
layer (SDH/SONET and Ethernet)
 GCC features:
 GCC interoperability with the following cards:
 HIO100_2
 FIO100/FIO100M
 TR100 (100G REG)
 TM400 (100G REG)
 GCC supported in standard (full rate) mode by default, as well as Apollo proprietary (¼ rate
GCC) reduced mode, user selectable.
 Supports up to 5 GCC channels for OTU2/OTU2e in standard mode, 1 GCC channel for
OTU4 in reduced mode.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.
 OTU2 and OTU2e client supports GFEC and EFEC
 Line service configured for SD FEC mode

Ribbon Communications Inc. Proprietary 11-35

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Card views
General view

Front panel

Usage guidelines
The CMR100/CMR100L can be assigned to slots 0, 2, 4, 6, 8, 10, 12, ,14, 16, 18, 20, 22 of OPT9624 or
slots 0, 2, 4, 6 of OPT9608 platforms.
Client ports of CMR100/CMR100L card are numbered 1 to 10 and labeled C1 to C10. Line port is port
number 0 and labeled LINE.

Ribbon Communications Inc. Proprietary 11-36

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Ports
LED indicators
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations).
Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is
no fault in the CMR100/CMR100L.
Client port LEDs (C1-C10)
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Lights steadily when a BIT fault is detected in the pluggable
transceiver, or the supply voltage or temperature is OOR. Blinks when
a LOS condition is detected in the port.
Line LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
LOS Red LED Blinks when a LOS condition is detected in the port.

Functional block diagram

Ribbon Communications Inc. Proprietary 11-37

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.9.1 CMR100/CMR100L transceivers

The CMR100/CMR100L client interfaces support the transceivers shown in the following table.

CMR100/CMR100L client transceivers reference table

Transceivers (client interfaces) Description

OTR64_PI3 STM-64/OC-192 transceiver
Intra-office non-colored
Range: 2 km
Wavelength 1310 nm
(1290-1330 nm)
OTR64_PS5 STM-64/OC-192 transceiver
Long-haul non-colored
Range: 40 km
Wavelength 1550 nm
(1529-1560 nm)
OTR64_AL5 STM-64/OC-192 transceiver
Extra haul non-colored
Range: 80 km
Wavelength 1550 nm
(1530-1565 nm)
OTR10_ASxx STM-64/OC-192/OTU2/10G LAN transceiver
8 CWDM channels
Long-haul, colored
Range: 40 km
Wavelength range (1464-1618 nm)
OTR10_ALxx STM-64/OC-192/OTU2/10G LAN transceiver
OTC10_ALxx 44 DWDM channels
Extra haul, colored
Range: 80 km
Wavelength range 1464-1618 nm
OTR103_SR 10.3 Gbps LAN/10G FC transceiver
Range: 300 m
Wavelength: 850 nm
OTR103_LR 10.3 Gbps LAN/10G FC/11.1G LAN + OTU2 transceiver
Range: 10 km
Wavelength: 1310 nm
OTR103_ER 10.3 Gbps LAN/10G FC/11.1G LAN + OTU2 transceiver
Long-haul, Range: 40 km
Wavelength: 1310 nm
OTR103_ZR 10.3 Gbps LAN/10G FC/11.1G LAN + OTU2 transceiver
Extra haul, Range: 80 km
Wavelength: 1550 nm

Ribbon Communications Inc. Proprietary 11-38

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.10 CMR100M
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The CMR100M is a double-slot combiner card that interfaces to any combination of ten of the following
client signals through SFP+, and maps them into a 100 Gbps colored line signal for WDM network
transport, according to the G.709 standard: 10GbE/STM64/40GbE.
The CMR100M is optimized for metro applications (up to 1200 km without regeneration). The client side
utilizes SFP+ transceivers for 10G interfaces.
The CMR100M works with D-CFP coherent line transceivers that enable transmission of 100Gbps DP-
QPSK modulation, with Flex-Grid capabilities. This transceiver includes a coherent receiver, DSP
processing, and soft decision forward error correction, for superior noise tolerance, as well as an
exceptional ability to mitigate CD and PMD impairments.
The CMR100M line can be deployed with non-colored CFP (instead the coherent CFP) for simple point
to point over dark fiber or any other application. The card supports SR10 or LR4 100G line
transmission. The CMR100M is configured with a 100G CFP on the line side. The target application
determines the type of transceiver chosen. For long haul (LH) applications, an MR1 transceiver is used.
The CMR100M offers the following main features:
 10 x SFP+ based client interface ports supporting:
 STM64/OC192
 10 GbE LAN
 10 GbE WAN
 OTU2
 OTU2e
 FC1200
 FC800
 Up to 2 x 40 GbE based QSFP+ client ports at the expense of 4 x 10 G SFP+ ports per each, with
the following options:
 2 x 40 GbE (QSFP+) + 2 x 10 GbE/STM64/OC192/FC800/FC1200/OTU2/OTU2e (SFP+)
 1 x 40 GbE (QSFP+) + 6 x 10 GbE/STM64/OC192/FC800/FC1200/OTU2/OTU2e (SFP+)
 Each client signal can be configured independently of the other clients
 OTU4 line port using a pluggable CFP transceiver (Coherent, SR10 or LR4)
 Fully tunable line side DWDM pluggable supporting:
 Up to 88 channels, and available in Dual Polarization Differential QPSK (DP-DQPSK)
modulation format
 Optimized for metro reach transmission over older fiber infrastructures with high PMD
 Complies with ITU-T standards for 50 GHz and 100 GHz multichannel spacing (DWDM)

Ribbon Communications Inc. Proprietary 11-39

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 One stage multiplexing according to latest ITU-T standards

 Supports PM and GCC in band management, with PM for client side signals in the signals' native
layer (SDH/SONET and Ethernet)
 GCC features:
 GCC interoperability with the following cards:
 HIO100_2
 FIO100/FIO100M
 TR100
 TM400
 GCC supported in standard (full rate) mode by default, as well as Apollo proprietary (¼ rate
GCC) reduced mode, user selectable.
 Supports up to 3 GCC channels for OTU2/OTU2e in standard mode, 1 GCC channel for
OTU4 in reduced mode.
 One GCC supported per port (OTU2/OTU2e/OTU4), configurable to either GCC0, GCC1, or
GCC2, user selectable.
 SD/HD FEC are supported on the line port
 Supports interoperability with TR100/TR100L in regenerator mode

Card views
General view

Ribbon Communications Inc. Proprietary 11-40

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Front panel

Usage guidelines
The CMR100M can be assigned to slots 0, 2, 4, 6, 8, 10, 12, ,14, 16, 18, 20, 22 of OPT9624 or slots 0,
2, 4, 6 of OPT9608 platforms.
The 10 Gb client ports are numbered under the line C1-C10 with numbers from (1) to (10) above each
SFP+ housing. The 40 GbE ports are marked C11 and C12 above the QSFP+ housings. When an 40
GbE port is configured, the corresponding four 10 Gb ports are disabled. For example, if port C11 is
provisioned, ports C1 to C4 are disabled.

LED indicators

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the CMR100M.
Client port LEDs (C1-C10)
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Lights steadily when a BIT fault is detected in the pluggable transceiver,
or the supply voltage or temperature is OOR. Blinks when a LOS
condition is detected in the port.
Line LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
LOS Red LED Blinks when a LOS condition is detected in the port.

Ribbon Communications Inc. Proprietary 11-41

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Functional block diagram

Ribbon Communications Inc. Proprietary 11-42

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.11 TR100/TR100L
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TR100/TR100L double-slot transponder maps a 100 GbE client signal into a 100 Gbps colored line
signal for WDM network transport, according to the G.709 standard. The TR100/TR100L uses DP-
QPSK modulation, a coherent receiver, DSP processing, and soft decision forward error correction, for
superior noise tolerance, and an exceptional ability to mitigate CD and PMD impairments.
The TR100 is optimized for Ultra Long Haul networking applications, and the TR100L supports regional
applications. While the TR100L does not support single fiber bi-directional WDM operation, in terms of
all other capabilities, the cards are identical and they are interoperable with each other.
The TR100/TR100L can be used in regenerator applications when installed adjacent to another
TR100/TR100L card, or in add/drop mode with an IOP protection option. For regenerator applications
the TR100/TR100L is supported only in OPT9624 and only in slots 0, 2, 4, 6, 12, 14, 16, 18, 20, 22.
Slots 8 and 10 are not supported for regenerator applications.
The TR100/TR100L supports the following main features:
 Maps 100 GbE client signals according to G.709 clause 17.7.5 into ODU4
 Uses a coherent receiver based DP-QPSK modulation
 Mapping uses timing transparent General Mapping Procedure (GMP)
 Supports transponder and regenerator applications
 Line interface OIF1.1-based transceiver:
 Fully C band tunable 50 GHz channel spacing with 88 channels
 OTU4v compliant
 SD-FEC (Soft Decision FEC)
 Capable to retrofit into existing DWDM infrastructure:
 Supports 50 GHz channel spacing
 Supports up to 24 cascaded ROADMs @ 100 GHz spacing
 Supports up to 18 cascaded ROADMs @ 50 GHz spacing
 Transmission over mixed fiber types
 Same CD/PMD tolerance as current 10G transponders
 Transmission with mixed traffic (10G/40G)
 Reach of up to 2500 km for greenfield installations without in-line DCMs
 Client interface:
 Fixed CFP pluggable transceiver
 Transponder service supports 100GBASE-LR4/SR10 interfaces

Ribbon Communications Inc. Proprietary 11-43

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 GCC features:
 GCC interoperability with the following cards:
 HIO100_2
 FIO100/FIO100M
 CMR100 (100G REG)
 TM400 (100G REG)
 GCC supported in standard (full rate) mode by default, as well as Apollo proprietary (¼ rate
GCC) reduced mode, user selectable.
 One GCC channel supported for OTU4 port, in reduced mode, configurable to either GCC0,
GCC1, or GCC2, user selectable.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 11-44

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Ports
LED indicators

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the TR100/TR100L.
Client Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter is
off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a BIT fault is
detected in the CFP pluggable transceiver, or the supply voltage or
temperature is OOR.
Line Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter is
off.
LOS Red LED Lights steadily when a BIT fault is detected in the OIF1.1 transceiver or the
supply voltage or temperature is OOR.

Functional block diagram

Ribbon Communications Inc. Proprietary 11-45

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.11.1 TR100 and TR100L usage guidelines

Transponder applications
The TR100/TR100L can be used in transponder applications that enable efficient transmission and
reception of optical payload signals provided by local user's equipment through the DWDM network. For
example, if the user needs to connect between two 100 GbE routers at a distance of 100 km, direct
connection will not enable the communication. The routers provide digital signals that enable
communication to relatively short distances (300 m to 10 km). To provide a solution to the distance
requirement, a TR100/TR100L is connected to the router at each end. The digital output signals from
each router are applied to the CFP client interface of each TR100/TR100L. The TR100/TR100L
processes the digital signals and provides them as OTU4 optical signals at the line OIF1.1 interfaces.
The OIF1.1 transceivers can drive the line signal to fibers with 100 km spans.

TR100/TR100L transponder application example

Regenerator applications
In a regenerator application, the transponder cleans up and amplifies optical signals transmitted
through the optical line (3R regeneration). The regenerator is used when the required distance is longer
than the transponder maximum reach. Two TR100/TR100L cards residing in adjacent slots on the
Apollo platform are used to implement the regenerator configuration. The following figure shows the
connections of the TR100/TR100L cards in this application. The OIF1.1 transceivers connect to the
lines at both ends. The connection between both cards is made through the platform's backplane. The
client is not connected to the CFP transceivers in this application.

Ribbon Communications Inc. Proprietary 11-46

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

TR100/TR100L regenerator connections

TR100/TR100L regenerator application example

Protection options
The TR100/TR100L supports client protection using a splitter/coupler. The active client is selected
using the IOP lines as in other Apollo service cards. Client protection is shown in the following figure.

Client protection with splitter/coupler

Ribbon Communications Inc. Proprietary 11-47

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.12 TM100
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TM100 is a single-slot 100G coherent transponder and muxponder card optimized for metro
applications (up to 1200 km without regeneration). When assigned as a transponder (TR100M) the
TM100 maps a 100 GbE client signal into a 100 Gbps colored line signal for WDM network transport,
according to the G.709 standard. In addition it can be configured as a muxponder in two modes: to
multiplex 10 x 10 GbE clients (MXP100E10) or to multiplex 2 x 40 GbE clients (MXP100E40).
The TM100 supports the new generation of compact pluggables (CFP at the line and CFP2 at the
client). Changes in the card's operation mode is implemented by software configuration to assign it to
one of the three modes (TR100M, MXP100E10 and MXP100E40).
The TM100 supports the following main features:
 Transponder applications (assigned as TR100M):
 Maps 100 GbE client signals according to G.709 clause 17.7.5 into ODU4
 Uses a CFP coherent receiver based DP-DQPSK modulation
 Mapping uses timing transparent General Mapping Procedure (GMP)
 Line interface CFP-based pluggable transceivers:
 Fully C band tunable 50 GHz channel spacing with 88 channels
 OTU4v compliant
 Very low latency SD-FEC (Soft Decision FEC - provides NCG of 11.1 dB)
 Client interface:
 Fixed CFP2 pluggable transceiver
 Transponder service supports LR4/SR10 interfaces
 LR4 long-reach up to 10 km
 SR10 short-reach up to 300 m
 Supports client protection in less than 50 msec, using splitters/couplers
 When there is a failure at the client signal or at the line signal it is replaced by an LF alarm
signal
 Hot insertion or removal of transceivers is supported without causing traffic interruption or
errors
 OTU4 port supports one embedded channel for embedded management, user selectable
from GCC0, GCC1, or GCC2

Ribbon Communications Inc. Proprietary 11-48

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 Interoperability with CMR100/CMR100L

 10 x 10 GbE muxponder application (card assigned as MXP100E10):
 Uses either a CFP coherent receiver based DP-DQPSK modulation (same as TR100M) or
non-colored CFP (SR10 or LR4) for 100G line transmission
 Supports 10 x ETY10Goc ports at the client side
 CFP2 based SR10 interface (up to 300 m reach) with 10 x 10 GbE independent lanes, using
a special adapter to support 10 clients
 Port protection is not supported in this mode
 2 x 40 GbE muxponder application (card assigned as MXP100E40):
 Uses either a CFP coherent receiver based DP-DQPSK modulation (same as TR100M) or
non-colored CFP (SR10 or LR4) for 100G line transmission
 Supports 2 x 40ETY10G ports at the client side
 CFP2 based SR10 interface with 10 x 10 GbE independent lanes; using a special adapter to
support 4 x 10 GbE for each 40 GbE client (total 2 x40 GbE clients)
 Port protection is not supported in this mode
 GCC features:
 GCC interoperability with the following cards:
 HIO100_2
 FIO100/FIO100M
 TM400 (100G REG)
 GCC supported in standard (full rate) mode by default, as well as Apollo proprietary (¼ rate
GCC) reduced mode, user selectable.
 Supports 1 GCC channel for OTU4, in reduced mode.
 One GCC channel supported per port, configurable to either GCC0, GCC1, or GCC2, user
selectable.

Ribbon Communications Inc. Proprietary 11-49

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 11-50

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Ports
LED indicators

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there
is no fault in the TM100.
Client Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a
BIT fault is detected in the CFP2 pluggable transceiver, or the
supply voltage or temperature is OOR.
Line Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED
Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the CFP pluggable transceiver, or the
supply voltage or temperature is OOR.

Functional block diagram

Ribbon Communications Inc. Proprietary 11-51

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.12.1 TM100 usage guidelines

TR100M transponder configuration
The TM100 can be configured to operate as a transponder (software assigned as TR100M).
Transponder applications enable efficient transmission and reception of optical payload signals
provided by local user's equipment through the DWDM network. For example, if the user needs to
connect between two 100 GbE routers at a distance of 100 km, direct connection will not enable the
communication. The routers provide digital signals that enable communication to relatively short
distances (300 m to 10 km). To provide a solution to the distance requirement, a TM100 configured as
a TR100M is connected to the router at each end. The digital output signals from each router are
applied to the CFP2 client interface (LR4 type for long-reach up to 10 km; SR10 type for short-reach up
to 300 m) of each TM100. The TM100 processes the digital signals and provides them as OTU4 optical
signals at the line CFP interfaces. The CFP transceivers can drive the line signal to fibers with 100 km
spans.

TM100 transponder application (TR100M)

MXP100E10 muxponder configuration

The TM100 can be configured to operate as a 10 x 10GbE muxponder (software assigned as
MXP100E10). As a MXP100E10 muxponder the card supports 10 x 10GbE short-reach client interfaces
for an ideal low-cost solution to aggregate multiple interfaces, for example in a data center, disaster
recovery, or triple play backhaul.
This mode requires a breakout patch cord (MTP24 to 20 x LC connectors) or a patch panel to physically
split the MTP24 ribbon fiber to 10 Tx and Rx interfaces (20 x LC connectors). For further details refer to
the relevant IMM.

TM100 muxponder application (MXP100E10)

Ribbon Communications Inc. Proprietary 11-52

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

MXP100E40 muxponder configuration

Another possible application of the TM100 is as a muxponder for 2 x 40 GbE (software provisioned as
MXP100E40). As a MXP100E40 muxponder the card supports 2 x 40GbE short-reach client interfaces
for an ideal low-cost solution to aggregate 40 GbE clients.
This mode requires a breakout patch cord (MTP24 to 2 x MTP12) in order to physically split the MTP24
ribbon fiber to two MTP12 interfaces. For further details refer to the relevant IMM.

TM100 muxponder application (MXP100E40)

11.13 TM100_2EN
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TM100_2EN is a double-slot 2 x 100G multi-service, minimal size transponder/muxponder card.
The card is enhanced with optional encryption capabilities (license-based) and software add-ons,
tailored to encrypted/unencrypted applications. By default, TM100_2EN is supplied without the
encryption option.
Card applications are typically in small regional or metro access networks requiring flexible grooming of
mixed rate services up to OTU4. A very useful application would be adding encryption capabilities for
users connecting to third party networks that do not support encryption.
The TM100_2EN is very similar to the TM200EN in all client port aspects. The main difference is in the
line ports; TM200EN has a single CFP2-based line port, while the TM100_2EN has two QSFP28-based
line ports that can be configured to OTU4. The TM100_2EN works with QSFP28 line transceivers,
supporting non-colored LR4, SR4, and ER4 applications.

TM100_2EN features
 Flexible configuration modes as a muxponder for N x 10G/16G/32G to dual OTU4
 Each service is configurable to operate with or without encryption. Encryption is based on the
AES256 and GCM standards. Optional encryption capabilities are license-based.
 GCC features:
 GCC supported in standard (full rate) mode.
 Up to 2 GCC channels for OTU2/OTU2e, and 2 GCC channels for OTU4 supported.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.

Ribbon Communications Inc. Proprietary 11-53

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 Various protection schemes for high redundancy including:

 DWDM network protection based on OLP_S2 or OMSP cards (< 50 mSec switchover for all
line types).
 100G line protection based on OLP_S2 card (< 50 mSec switchover for all line types).
 Port protection (< 50 mSec switchover for all line types) for all LR4 clients
 Each service could be protected/unprotected regardless of other services. Protection is
selectable per port.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 11-54

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Usage guidelines and assignment rules

The TM100_2EN provides the following configuration options:
 2 x line ports (Ports 0 and 21), based on QSFP28 form factor, for non-colored LR4/SR4/ER4
applications
 Users should first assign a selected line port (0 or 21) to OTU4. The user should then
explicitly configure the corresponding client ports and connects (sub interfaces) to the line
port low order ODUk.
 When a line port is configured to OTU4 it supports up to 80 tributary slots of ODU0.
Assignment of more clients beyond this limit are rejected.
 20 x client ports, numbered from 1 to 20, with three types of ports:
 2 independent QSFP+/QSFP28-based modules.
 The two modules are configured independently.
 Each module includes 4 port openings, numbered 1-4 and 5-8.
 The 4 ports within each module must be configured consistently, either as ETY100G, or
as ETY40G, or as 4 x ETY10GOC ports.
 The full set of 8 x 10GE ports (on both modules) can be operated as 4 fan-out ports.
 4 x SFP+/SFP28-based ports, Ports 9-12, supporting the following port rates:
 10GE/OTU2/2e
 FC8/FC10/FC16/FC32
 STM-64/OC192
[These ports do not support rates ETY100G and ETY40G.]
 8 x SFP+ based ports, Ports 13-20, supporting the following port rates:
 10GE/OTU2/2e
 FC8/FC10/FC16
 STM-64/OC192
[These ports do not support rates ETY100G, ETY40G, and FC32.]
 The TM100_2EN client ports are organized into two groups: Group 1 and Group 2.
 When configuring TM100_2EN ports, the maximum number of ports available in each group
is calculated independently, with each group mapped to a different ODU4.
 When working with OTU4 uplinks, the client ports must all be based on ports in the same
group.
For example, when configuring OTU4 on line port 0, which is part of Group 1, then you can assign
up to a maximum of 80 x ODU0 client rates from among the client ports in Group 1. Assignment of
more clients beyond this limit will be rejected.
The allocation of ports per Group is listed in the table at the end of this section, and also marked
on the card's front panel.
 The following assignment limitations apply:
 You cannot assign more than 3 x FC32 to the same ODU4.
 You cannot assign more than 1 x ETY40G with an OTU4 line port.
 If port 9 is configured with FC32, then ports 13 and 14 are disabled.
Conversely, if either port 13 or port 14 is already assigned, then you cannot assign FC32 to
port 9.

Ribbon Communications Inc. Proprietary 11-55

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 If port 10 is configured with FC32, then ports 15 and 16 are disabled.

Conversely, if either port 15 or port 16 is already assigned, then you cannot assign FC32 to
port 10.
 If port 11 is configured with FC32, then ports 17 and 18 are disabled.
Conversely, if either port 17 or port 18 is already assigned, then you cannot assign FC32 to
port 11.
 If port 12 is configured with FC32, then ports 19 and 20 are disabled.
Conversely, if either port 19 or port 20 is already assigned, then you cannot assign FC32 to
port 12.

Ports
The TM100_2EN line ports are numbered 0 and 21.
The client ports are numbered from 1 to 20, with three types of ports:
 2 QSFP+/QSFP28-based ports, Ports 1-4 and 5-8
 4 SFP+/SFP28-based ports, Ports 9-12
 8 SFP+ based ports, Ports 13-20
The marking above each port identifies the Transmit (Tx) and Receive signals (Rx). The port LED
indicators are under each port.
The TM100_2EN ports are organized into two groups, Group 1 and Group 2. Port types and rates and
group association are listed in the following table. The information is also marked on the card's front
panel.

TM100_2EN Client and Line ports per Group

Client port No. Port type Port rates Group
1-4 QSFP+/QSFP28 OTU4/100GE 1
40GE
4 x 10GE
5-8 QSFP+/QSFP28 OTU4/100GE 2
40GE
4 x 10GE
9-10 SFP+/SFP28 10GE / OTU2/2e 1
FC8/FC10/FC16/FC32
STM-64/OC192
11-12 SFP+/SFP28 10GE / OTU2/2e 2
FC8/FC10/FC16/FC32
STM-64/OC192
13-16 SFP+ 10GE / OTU2/2e 1
FC8/FC10/FC16
STM-64/OC192
17-20 SFP+ 10GE / OTU2/2e 2
FC8/FC10/FC16
STM-64/OC192
Line port No.

0 QSFP28 OTU4 1
21 QSFP28 OTU4 2

Ribbon Communications Inc. Proprietary 11-56

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

The port LED indicators are under each port.

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when
there is no fault in the TM100_2EN.
Line (QSFP28) port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the CFP pluggable transceiver, or the
supply voltage or temperature is OOR.
Client port (QSFP+/QSFP28/SFP+/SFP28 and SFP+) LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the SFP+/QSFP+ pluggable
transceiver, or the supply voltage or temperature is OOR.

Ribbon Communications Inc. Proprietary 11-57

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Functional block diagram

11.14 TM100_2ENB
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TM100_2ENB is a double-slot long 2 x 100G multi-service, minimal-size transponder/muxponder
card for DWDM networks. The card provides a high level of encryption that complies with FIPS 140-2
Level 2 encryption standards, the same encryption capabilities and security features as the TM200ENB;
described in FIPS 140-2 Level 2 security implementation. The traffic of each client port can be
configured, by the user, to be encrypted or not.
The TM100_2ENB is very similar to the TM200ENB in all client port aspects. The main difference is in
the line ports; TM200ENB has a single CFP2-based line port, while the TM100_2ENB has two
QSFP28-based line ports that can be configured to OTU4. The TM100_2ENB works with QSFP28 line
transceivers, supporting non-colored LR4, SR4, and ER4 applications.

Ribbon Communications Inc. Proprietary 11-58

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

TM100_2ENB features
 Flexible configuration modes:
 Muxponder N x 10G/16G/32G to dual 100G
 Muxponder N x 10G/16G/32G
 Dual 100G transponders
 Each service is configurable to operate with or without encryption, using AES256, FIPS 140-2
Level 2, and GCM standards. Optional encryption capabilities are license-based.
 GCC support for in-band management.
 Communication channels:
 Embedded management support by GCC0 on line ports (one channel per port).
 Five embedded user-selectable communication channels (GCC0/GCC1/GCC2) per client
port.
 Various protection schemes for high redundancy including:
 DWDM network protection based on OLP_S2 card (< 50 mSec switchover for all line types).
 DWDM network protection based on OMSP card (< 50 mSec switchover for all line types).
 100G line protection based on OLP_S2 card (< 50 mSec switchover for all line types).
 Port protection (< 50 mSec switchover for all line types) for all client, excluding SR4
transceiver for QSFP28/QSFP+ clients.
 Each service could be protected/unprotected regardless of other services. Protection is
selectable per port.

Card views
Front panel

Ribbon Communications Inc. Proprietary 11-59

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Usage guidelines and assignment rules

The TM100_2ENB provides the following configuration options:
 2 x line ports (Ports 0 and 21), based on QSFP28 form factor, for non-colored LR4/SR4/ER4
applications
 Users should first assign a selected line port (0 or 21) to OTU4. The user should then
explicitly configure the corresponding client ports and connects (sub interfaces) to the line
port low order ODUk.
 When a line port is configured to OTU4 it supports up to 80 tributary slots of ODU0.
Assignment of more clients beyond this limit are rejected.
 20 x client ports, numbered from 1 to 20, with three types of ports:
 2 independent QSFP+/QSFP28-based modules.
 The two modules are configured independently.
 Each module includes 4 port openings, numbered 1-4 and 5-8.
 The 4 ports within each module must be configured consistently, either as ETY100G, or
as ETY40G, or as 4 x ETY10GOC ports.
 The full set of 8 x 10GE ports (on both modules) can be operated as 4 fan-out ports.
 4 x SFP+/SFP28-based ports, Ports 9-12, supporting the following port rates:
 10GE/OTU2/2e
 FC8/FC10/FC16/FC32
 STM-64/OC192
[These ports do not support rates ETY100G and ETY40G.]
 8 x SFP+ based ports, Ports 13-20, supporting the following port rates:
 10GE/OTU2/2e
 FC8/FC10/FC16
 STM-64/OC192
[These ports do not support rates ETY100G, ETY40G, and FC32.]
 The TM100_2ENB client ports are organized into two groups: Group 1 and Group 2.
 When configuring TM100_2ENB ports, the maximum number of ports available in each group
is calculated independently, with each group mapped to a different ODU4.
 When working with OTU4 uplinks, the client ports must all be based on ports in the same
group.
For example, when configuring OTU4 on line port 0, which is part of Group 1, then you can assign
up to a maximum of 80 x ODU0 client rates from among the client ports in Group 1. Assignment of
more clients beyond this limit will be rejected.
The allocation of ports per Group is listed in the table at the end of this section, and also marked
on the card's front panel.
 The following assignment limitations apply:
 You cannot assign more than 3 x FC32 to the same ODU4.
 You cannot assign more than 1 x ETY40G with an OTU4 line port.
 If port 9 is configured with FC32, then ports 13 and 14 are disabled.
Conversely, if either port 13 or port 14 is already assigned, then you cannot assign FC32 to
port 9.

Ribbon Communications Inc. Proprietary 11-60

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 If port 10 is configured with FC32, then ports 15 and 16 are disabled.

Conversely, if either port 15 or port 16 is already assigned, then you cannot assign FC32 to
port 10.
 If port 11 is configured with FC32, then ports 17 and 18 are disabled.
Conversely, if either port 17 or port 18 is already assigned, then you cannot assign FC32 to
port 11.
 If port 12 is configured with FC32, then ports 19 and 20 are disabled.
Conversely, if either port 19 or port 20 is already assigned, then you cannot assign FC32 to
port 12.

Ports
The TM100_2ENB line ports are numbered 0 and 21.
The client ports are numbered from 1 to 20, with three types of ports:
 2 QSFP+/QSFP28-based ports, Ports 1-4 and 5-8
 4 SFP+/SFP28-based ports, Ports 9-12
 8 SFP+ based ports, Ports 13-20
The marking above each port identifies the Transmit (Tx) and Receive signals (Rx). The port LED
indicators are under each port.
The TM100_2ENB ports are organized into two groups, Group 1 and Group 2. Port types and rates
and group association are listed in the following table. The information is also marked on the card's
front panel.

TM100_2ENB Client and Line ports per Group

Client port No. Port type Port rates Group
1-4 QSFP+/QSFP28 OTU4/100GE 1
40GE
4 x 10GE
5-8 QSFP+/QSFP28 OTU4/100GE 2
40GE
4 x 10GE
9-10 SFP+/SFP28 10GE / OTU2/2e 1
FC8/FC10/FC16/FC32
STM-64/OC192
11-12 SFP+/SFP28 10GE / OTU2/2e 2
FC8/FC10/FC16/FC32
STM-64/OC192
13-16 SFP+ 10GE / OTU2/2e 1
FC8/FC10/FC16
STM-64/OC192
17-20 SFP+ 10GE / OTU2/2e 2
FC8/FC10/FC16
STM-64/OC192
Line port No.

0 QSFP28 OTU4 1
21 QSFP28 OTU4 2

Ribbon Communications Inc. Proprietary 11-61

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

The port LED indicators are under each port.

LED indicators
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there
is no fault in the TM100_2ENB.
SECURITY Green/Red (bi- Described in the table below (as it has multiple states).
color) LED
Line (QSFP28) port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a
BIT fault is detected in the CFP pluggable transceiver, or the
supply voltage or temperature is OOR.
Client port (QSFP+/QSFP28/SFP+/SFP28 and SFP+) LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a
BIT fault is detected in the SFP+/QSFP+ pluggable transceiver, or
the supply voltage or temperature is OOR.

SECURITY LED functions

LED state State set by Description
Red CPLD Card tampered. HCPM in reset.
Green SW Card operating in FIPS mode with CSPS loaded.
1.5 sec Green/3.0 sec Red CPLD Initial state after power on.
2.5 sec on/2.5 sec off Red CPLD Low-battery/Tamper-check warning.
1.5 sec Red/3 sec Green CPLD CPLD initialization complete, HCPM reset released, Boot-ROM
running.
5.0 sec on/5.0 sec off Green SW IO application initializing and running algorithmic self-tests.
2.5 sec on/2.5 sec off Green SW Algorithmic self-tests passed; hardware self-test.
5.0 sec on/5.0 sec off Red SW Failure in algorithms tests or crypto hardware test.
1.5 sec Red/3.0 sec Green SW CSPS self tests (key pairs and certificates).
1 sec on/1 sec off Red SW Missing CSPS.
2.0 sec Green/2.0 sec Red Unassigned CSPS self-test failure.
1 sec on Red+ Green/1 sec off CPLD CO password missing.
Off (no light) Unassigned
5.0 sec Green/5.0 sec Red SW Transient FIPS failure (e.g. TRNG continuous monitoring failure).

Ribbon Communications Inc. Proprietary 11-62

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Functional block diagram

11.15 TM200EN
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TM200EN is a double-slot 200G multi-service, low cost, minimal size transponder/muxponder card
for DWDM networks. The card is enhanced with optional encryption capabilities (license-based) and
software add-ons, tailored to encrypted/unencrypted applications. By default, TM200EN is supplied
without the encryption option.
Card applications are typically in data centers and SAN interconnectivity, as well as expansion of
existing networks with 200G encrypted wavelengths, grooming any mixture of services into OTU4 or
OTUC2.

Ribbon Communications Inc. Proprietary 11-63

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

The TM200EN works with D-CFP2 coherent line transceivers, supporting configurable DP-QPSK, 8-
QAM, or 16-QAM modulation, with Flex-Grid capabilities. This transceiver includes a coherent receiver,
DSP processing, and soft decision forward error correction, for superior noise tolerance, as well as an
exceptional ability to mitigate CD and PMD impairments.
TM200EN can be configured to operate in two modes (expected types):
 TM200EN - for muxponder applications of OTU or OTUC2, user selectable:
 10GE/40GE/100GE
 FC8/16/32
 STM-64/OC-192
 OTU2/2e
 TR10_12EN - for six 10G encrypted transponder applications

TM200EN features
 Flexible configuration modes:
 Muxponder N x 10G/16G/32G to single 100G or 200G
 Muxponder N x 10G/16G/32G/100G to 200G
 Muxponder 2 x 100G to 200G
 Single 100G transponder
 6 x 10G transponders
 Up to 4 x 10G Y-protected (1 x client to 2 x lines)
 Each service is configurable to operate with or without encryption. Encryption is based on the
AES256 and GCM standards. Optional encryption capabilities are license-based.
 GCC features:
 GCC interoperability with the following cards:
 HIO100_2
 HIO500
 MIO200
 TR200_2
 TM400 (100G REG)
 GCC supported in standard (full rate) mode.
 Up to 3 GCC channels for OTU2/OTU2e, and 1 GCC channel for OTUC2/OTU4, supported.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.
 Various protection schemes for high redundancy including:
 WSON restoration using coherent OTU4\OTUC2 wavelengths (< 5 sec switchover).
 DWDM network protection based on OLP_S2 or OMSP cards (< 50 mSec switchover for all
line types).
 100G/200G line protection based on OLP_S2 card (< 50 mSec switchover for all line types).
 Port protection (< 50 mSec switchover for all line types) for all client, excluding SR4
transceiver for QSFP28/QSFP+ clients.

Ribbon Communications Inc. Proprietary 11-64

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 Y-protection (<50 mSec switchover) for TR10_12EN mode, up to four protection groups.
 Each service could be protected/unprotected regardless of other services. Protection is
selectable per port.

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 11-65

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Usage guidelines and assignment rules

The TM200EN provides the following configuration options:
 1 x line port (Port 0), based on D-CFP2 form factor, for coherent 100/200G transceivers.
 Users should first assign the line port to either OTU4 or OTUC2. The user should then
explicitly configure the corresponding client ports and connects (sub interfaces) to the line
port low order ODUk.
 When the line port is configured to OTUC2, it supports up to 160 tributary slots of ODU0.
Assignment of more clients beyond this limit are rejected.
 When the line port is configured to OTU4 it supports up to 80 tributary slots of ODU0.
Assignment of more clients beyond this limit are rejected.
 20 x client ports, numbered from 1 to 20, with three types of ports:
 2 independent QSFP+/QSFP28-based modules.
 The two modules are configured independently.
 Each module includes 4 port openings, numbered 1-4 and 5-8.
 The 4 ports within each module must be configured consistently, either as ETY100G, or
as ETY40G, or as 4 x ETY10GOC ports.
 The full set of 8 x 10GE ports (on both modules) can be operated as 4 fan-out ports.
 4 x SFP+/SFP28-based ports, Ports 9-12, supporting the following port rates:
 10GE / OTU2/2e
 FC8/FC10/FC16/FC32
 STM-64/OC192
[These ports do not support rates ETY100G and ETY40G.]
 8 x SFP+ based ports, Ports 13-20, supporting the following port rates:
 10GE / OTU2/2e
 FC8/FC10/FC16
 STM-64/OC192
[These ports do not support rates ETY100G, ETY40G, and FC32.]
 The TM200EN ports are organized into two groups, Group 1 and Group 2.
 When configuring TM200EN ports, the maximum number of ports available in each group is
calculated independently, with each group mapped to a different ODU4.
 When working with an OTU4 uplink, the client ports must all be based on ports in the same
group; with an OTUC2 uplink, ports from both groups are used.
For example, when configuring OTU4 on line port 0, configured as part of Group 1, then you can
assign up to a maximum of 80 x ODU0 client rates from among the client ports in Group 1.
Assignment of more clients beyond this limit will be rejected.
If you configure OTUC2 on line port 0, then you can assign up to a maximum of 160 x ODU0 client
rates from among the client ports in both groups. Assignment of more clients beyond this limit will
be rejected.
The allocation of ports per Group is listed in the table at the end of this section, and also marked
on the card's front panel.

Ribbon Communications Inc. Proprietary 11-66

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 The following assignment limitations apply:

 You cannot assign more than 3 x FC32 to the same ODU4.
 You cannot assign more than 1 x ETY40G with an OTU4 line port.
 If port 9 is configured with FC32, then ports 13 and 14 are disabled.
Conversely, if either port 13 or port 14 is already assigned, then you cannot assign FC32 to
port 9.
 If port 10 is configured with FC32, then ports 15 and 16 are disabled.
Conversely, if either port 15 or port 16 is already assigned, then you cannot assign FC32 to
port 10.
 If port 11 is configured with FC32, then ports 17 and 18 are disabled.
Conversely, if either port 17 or port 18 is already assigned, then you cannot assign FC32 to
port 11.
 If port 12 is configured with FC32, then ports 19 and 20 are disabled.
Conversely, if either port 19 or port 20 is already assigned, then you cannot assign FC32 to
port 12.

Ports
The TM200EN line port is numbered 0.
The client ports are numbered from 1 to 20, with three types of ports:
 2 QSFP+/QSFP28-based ports, Ports 1-4 and 5-8
 4 SFP+/SFP28-based ports, Ports 9-12
 8 SFP+ based ports, Ports 13-20
The marking above each port identifies the Transmit (Tx) and Receive signals (Rx). The port LED
indicators are under each port.
The TM200EN ports are organized into two groups, Group 1 and Group 2. Port types and rates and
group association are listed in the following table. The information is also marked on the card's front
panel.

Ribbon Communications Inc. Proprietary 11-67

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

TM200EN Client and Line ports per Group

Client port No. Port type Port rates Group
1-4 QSFP+/QSFP28 OTU4/100GE 1
40GE
4 x 10GE with fan out
5-8 QSFP+/QSFP28 OTU4/100GE 2
40GE
4 x 10GE with fan-out
9-10 SFP+/SFP28 10GE / OTU2/2e 1
FC8/FC10/FC16/FC32
STM-64/OC192
11-12 SFP+/SFP28 10GE / OTU2/2e 2
FC8/FC10/FC16/FC32
STM-64/OC192
13-16 SFP+ 40GE with fan-out 1
10GE / OTU2/2e
FC8/FC10/FC16
STM-64/OC192
17-20 SFP+ 40GE with fan-out 2
10GE / OTU2/2e
FC8/FC10/FC16
STM-64/OC192
Line port No.

0 CFP2 OTU4/OTUC2 1&2

The port LED indicators are under each port.

LED indicators

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there
is no fault in the TM200EN.
Line (CFP2) port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a
BIT fault is detected in the CFP pluggable transceiver, or the
supply voltage or temperature is OOR.
Client port (QSFP+/QSFP28/SFP+/SFP28 and SFP+) LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a
BIT fault is detected in the SFP+/QSFP+ pluggable transceiver, or
the supply voltage or temperature is OOR.

Ribbon Communications Inc. Proprietary 11-68

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Functional block diagrams

TM200EN functional block diagram

Ribbon Communications Inc. Proprietary 11-69

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

TR10_12EN functional block diagram

11.15.1 TR10_12EN usage guidelines

As explained in TM200EN , the TR10_12EN is a user-configurable operation mode of the TM200EN.
When assigning the TR10_12EN, the Chassis View displays the card with Ports 0 to 8 grayed-out. This
indicates that these ports cannot be assigned while working in TR10_12EN mode.

Assignment rules
The following rules apply in TR10_12EN operation mode:
 Ports 9 to 12 are always client ports, so the label CLIENT is marked above the port numbers.
 Ports 13 and 14 can be client or line ports, so they have no label except the number of the port.
 Ports 15 to 20 are always line ports, so the label LINE is marked above the port numbers.
 The assignable Ports (9 to 20) can be configured to the following rates:
 ETY10G
 ETY10GOC
 STM-64
 OC-192
 FC800

Ribbon Communications Inc. Proprietary 11-70

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 FC1200
 OTU2
 OTU2e

NOTE: Although ports have dedicated roles, the user can XC any two ports described
here.

TR10_12EN features
TR10_12EN provides the basic features of the TR10_12/TR10_12R with the additional capability of
encryption.
In addition the card provides the following functionality:
 Six 10G transponders
 Protection:
 SNCP
 Up to 4 groups of Y Protection
 WSON restoration
 GCC features:
 GCC supported in standard (full rate) mode.
 Up to 4 GCC channels for OTU2/OTU2e supported.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.

11.16 TM200ENB
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TM200ENB is a double-slot long card providing 200G multi-service, minimal size encrypted
solution for DWDM networks. The card provides a high level of encryption that complies with FIPS 140-
2 Level 2 encryption standards, described in FIPS 140-2 Level 2 security implementation. The traffic of
each client port can be configured, by the user, to be encrypted or not.
Card applications are typically in data centers and SAN interconnectivity, as well as expansion of
existing networks with 200G encrypted wavelengths, grooming any mixture of services into OTU4 or
OTUC2.
The TM200ENB works with D-CFP2 coherent line transceivers, supporting configurable DP-QPSK, 8-
QAM, or 16-QAM modulation, with Flex-Grid capabilities. This transceiver includes a coherent receiver,
DSP processing, and soft decision forward error correction, for superior noise tolerance, as well as an
exceptional ability to mitigate CD and PMD impairments.

Ribbon Communications Inc. Proprietary 11-71

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

TM200ENB can be configured to operate in two modes (expected types):

 TM200ENB - for muxponder applications of N x 10G/16G/32G/100G to 100G or 200G user
selectable
 TR10_12ENB - for six 10G transponders application

TM200ENB features
 Flexible configuration modes:
 Muxponder N x 10G/16G/32G to single 100G or 200G
 Muxponder N x 10G/16G/32G/100G to 200G
 Muxponder 2 x 100G to 200G
 Single 100G transponder
 6 x 10G transponders
 Up to 4 10G Y-protected (1 x client to 2 x lines)
 Each service is configurable to operate with or without encryption, using AES256, FIPS 140-2
Level 2, and GCM standards. Optional encryption capabilities are license-based.
 GCC support for in-band management.
 Communication channels:
 Embedded management support by GCC0 on line ports (one channel per port).
 Five embedded user-selectable communication channels (GCC0/GCC1/GCC2) per client
port.
 Various protection schemes for high redundancy including:
 WSON restoration using coherent OTU4\OTUC2 wavelengths (< 5 sec switchover).
 DWDM network protection based on OLP_S2 card (< 50 mSec switchover for all line types).
 DWDM network protection based on OMSP card (< 50 mSec switchover for all line types).
 100G/200G line protection based on OLP_S2 card (< 50 mSec switchover for all line types).
 Port protection (< 50 mSec switchover for all line types) for all client, excluding SR4
transceiver for QSFP28/QSFP+ clients.
 Y-protection (<50 mSec switchover) for TR10_12EN mode, up to four protection groups.
 Each service could be protected/unprotected regardless of other services. Protection is
selectable per port.
 Encryption keys are rotated by the RCP per NE.

Ribbon Communications Inc. Proprietary 11-72

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Card views
General view

Front panel

Usage guidelines and assignment rules

The TM200ENB provides the following configuration options:
 1 x line port (Port 0), based on CFP2 form factor, for coherent 100/200G transceivers.
 Users should first assign the line port to either OTU4 or OTUC2. The user should then
explicitly configure the corresponding client ports and connects (sub interfaces) to the line
port low order ODUk.
 When the line port is configured to OTUC2, it supports up to 160 tributary slots of ODU0.
Assignment of more clients beyond this limit are rejected.
 When the line port is configured to OTU4 it supports up to 80 tributary slots of ODU0.
Assignment of more clients beyond this limit are rejected.

Ribbon Communications Inc. Proprietary 11-73

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 20 x client ports, numbered from 1 to 20, with three types of ports:

 2 independent QSFP+/QSFP28-based modules.
 The two modules are configured independently.
 Each module includes 4 port openings, numbered 1-4 and 5-8.
 The 4 ports within each module must be configured consistently, either as ETY100G, or
as ETY40G, or as 4 x ETY10GOC ports.
 The full set of 8 x 10GE ports (on both modules) can be operated as 4 fan-out ports.
 4 x SFP+/SFP28-based ports, Ports 9-12, supporting the following port rates:
 10GE / OTU2/2e
 FC8/FC10/FC16/FC32
 STM-64/OC192
[These ports do not support rates ETY100G and ETY40G.]
 8 x SFP+ based ports, Ports 13-20, supporting the following port rates:
 10GE / OTU2/2e
 FC8/FC10/FC16
 STM-64/OC192
[These ports do not support rates ETY100G, ETY40G, and FC32.]
 The TM200ENB ports are organized into two groups, Group 1 and Group 2.
 When configuring TM200ENB ports, the maximum number of ports available in each group is
calculated independently, with each group mapped to a different ODU4.
 When working with an OTU4 uplink, the client ports must all be based on ports in the same
group; with an OTUC2 uplink, ports from both groups are used.
For example, when configuring OTU4 on line port 0, configured as part of Group 1, then you can
assign up to a maximum of 80 x ODU0 client rates from among the client ports in Group 1.
Assignment of more clients beyond this limit will be rejected.
If you configure OTUC2 on line port 0, then you can assign up to a maximum of 160 x ODU0 client
rates from among the client ports in both groups. Assignment of more clients beyond this limit will
be rejected.
The allocation of ports per Group is listed in the table at the end of this section, and also marked
on the card's front panel.
 The following assignment limitations apply:
 You cannot assign more than 3 x FC32 to the same ODU4.
 You cannot assign more than 1 x ETY40G with an OTU4 line port.
 If port 9 is configured with FC32, then ports 13 and 14 are disabled.
Conversely, if either port 13 or port 14 is already assigned, then you cannot assign FC32 to
port 9.
 If port 10 is configured with FC32, then ports 15 and 16 are disabled.
Conversely, if either port 15 or port 16 is already assigned, then you cannot assign FC32 to
port 10.

Ribbon Communications Inc. Proprietary 11-74

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 If port 11 is configured with FC32, then ports 17 and 18 are disabled.

Conversely, if either port 17 or port 18 is already assigned, then you cannot assign FC32 to
port 11.
 If port 12 is configured with FC32, then ports 19 and 20 are disabled.
Conversely, if either port 19 or port 20 is already assigned, then you cannot assign FC32 to
port 12.

Ports
The TM200ENB line port is numbered 0.
The client ports are numbered from 1 to 20, with three types of ports:
 2 QSFP+/QSFP28-based ports, Ports 1-4 and 5-8
 4 SFP+/SFP28-based ports, Ports 9-12
 8 SFP+ based ports, Ports 13-20
The marking above each port identifies the Transmit (Tx) and Receive signals (Rx). The port LED
indicators are under each port.
The TM200ENB ports are organized into two groups, Group 1 and Group 2. Port types and rates and
group association are listed in the following table. The information is also marked on the card's front
panel.

TM200ENB client and line ports per group

Client port No. Port type Port rates Group

1-4 QSFP+/QSFP28 OTU4/100GE 1
40GE
4 x 10GE with fan-out
5-8 QSFP+/QSFP28 OTU4/100GE 2
40GE
4 x 10GE with fan-out
9-10 SFP+/SFP28 10GE / OTU2/2e 1
FC8/FC10/FC16/FC32
STM-64/OC192
11-12 SFP+/SFP28 10GE / OTU2/2e 2
FC8/FC10/FC16/FC32
STM-64/OC192
13-16 SFP+ 40GE with fan-out 1
10GE / OTU2/2e
FC8/FC10/FC16
STM-64/OC192
17-20 SFP+ 40GE with fan-out 2
10GE / OTU2/2e
FC8/FC10/FC16
STM-64/OC192
Line port No.

0 CFP2 OTU4/OTUC2 1&2

Ribbon Communications Inc. Proprietary 11-75

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

The port LED indicators are under each port.

LED indicators
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when
there is no fault in the card.
SECURITY Green/Red (bi-color) Described in the table below (as it has multiple states).
LED
Line (CFP2) port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a
BIT fault is detected in the CFP pluggable transceiver, or the
supply voltage or temperature is OOR.
Client port (QSFP+/QSFP28/SFP+/SFP28 and SFP+) LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a
BIT fault is detected in the SFP+/QSFP+ pluggable transceiver,
or the supply voltage or temperature is OOR.

SECURITY LED functions

LED state State set by Description
Red CPLD Card tampered. HCPM in reset.
Green SW Card operating in FIPS mode with CSPS loaded.
1.5 sec Green/3.0 sec Red CPLD Initial state after power on.
2.5 sec on/2.5 sec off Red CPLD Low-battery/Tamper-check warning.
1.5 sec Red/3 sec Green CPLD CPLD initialization complete, HCPM reset released, Boot-ROM
running.
5.0 sec on/5.0 sec off Green SW IO application initializing and running algorithmic self-tests.
2.5 sec on/2.5 sec off Green SW Algorithmic self-tests passed; hardware self-test.
5.0 sec on/5.0 sec off Red SW Failure in algorithms tests or crypto hardware test.
1.5 sec Red/3.0 sec Green SW CSPS self tests (key pairs and certificates).
1 sec on/1 sec off Red SW Missing CSPS.
2.0 sec Green/2.0 sec Red Unassigned CSPS self-test failure.
1 sec on Red+ Green/1 sec off CPLD CO password missing.
Off (no light) Unassigned
5.0 sec Green/5.0 sec Red SW Transient FIPS failure (e.g. TRNG continuous monitoring failure).

Ribbon Communications Inc. Proprietary 11-76

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Functional block diagram

11.17 FIPS 140-2 Level 2 security implementation

FIPS (Federal Information Processing Standard) is a US government encryption standard accepted in
North America and other territories. Apollo's TM200ENB and TM100_2ENB cards offer FIPS 140-2
Level 2 encryption capabilities and security features, described in this section. The encryption, security,
and installation details apply to both the TM200ENB and the TM100_2ENB cards; the examples and
figures in these sections are based on the TM200ENB cards.

11.17.1 FIPS 140-2 Level 2 encryption

Encryption in the optical-layer is a powerful way to ensure secure communication over interconnecting
networks. The TM200ENB and TM100_2ENB cards provide optical encryption via both transponder
and muxponder applications of the card, supporting pre-service encryption of up to 100 Gbps, with line
rates of up to 200 Gbps, without any impact on optical interoperability, scalability, or flexibility. These
capabilities enable a variety of flexible options for optical encryption as a service. The encryption is
certified per FIPS 140-2 Security Level 2 US government computer security standards.
As a muxponder, the card combines lower-speed signals into a 200 Gbps line signal. Each client
service can be independently encrypted or unencrypted. Services can be combined on the same line,
without restrictions.

Ribbon Communications Inc. Proprietary 11-77

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

The main features of the TM200ENB/TM100_2ENB encryption engine include:

 Communication between NEs is through a secured line on the ODU sub-interface level, using an
AES256-encrypted line.
 NEs provisioned to support encryption authenticate each other using private/public key pairs.
 NEs exchange symmetric encryption keys for the encryption algorithm using Diffie-Hellman group
5, 14, and 24 algorithms.
 Symmetric keys are the standard choice for parallel encrypted lines between the same peers,
whether on the same card or on different cards.
 Upon RCP HA switchover, keys are synchronized and encrypted; traffic doesn't experience any
traffic hit.
 Replacement of a single RCP doesn't cause any traffic hit.
 In case key rotation has not been completed when the IV (Initialization Vector) counter reaches
the maximum number, traffic is considered insecure, and an alarm is raised.
 Up to ten channels, of the 96 supported, can be configured as encrypted or unencrypted (the
remaining are in bypass mode).
 Bypass mode allows non-encrypted data to bypass the encryption engine without additional
latency.

11.17.2 Understanding FIPS 140-2 Level 2 security

The TM200ENB/TM100_2ENB cards are high density transponder/muxponder cards that take client
traffic, encrypt it with a high strength cipher, and map it to line side OTN ports. In the reverse direction,
traffic arriving from line ports is de-mapped, decrypted, and then forwarded to the appropriate client
port.
The TM200ENB/TM100_2ENB cards are fully compliant, and in some cases even exceed, the FIPS
140-2 Level 2 standard. These cards efficiently implement the FIPS-approved cryptographic algorithms
and functions only while running in FIPS mode. FIPS 140-2 Level 2 compliance includes physical
tamper detection mechanisms which the TM200ENB/TM100_2ENB cards meet and exceed.
The cards are manufactured and shipped to customer sites in a secure way so that any tamper
attempts can be detected. Furthermore, the module must be installed by the Cryptographic Officer (CO)
following detailed guidelines. Secret keys must be installed in a secure manner so they can be
accessed and used only by FIPS-approved cryptographic functions. The cards provide status
information through physical and logical interfaces. Card health and FIPS status can be monitored
continuously through a secure management application. Basic card health and FIPS status is also
indicated by LEDs on the front panel.
Specialized and sensitive circuitry on the card can detect tampering. The module can report tamper
events through physical and logical interfaces. For Level-2 compliance, it’s mandatory to generate
tamper indications (such as broken label marks or LED colors). These modules actually exceed this
requirement, since they also attempt to take corrective actions (i.e., tamper-response) so that critical
information is not compromised after a tamper event.

NOTE: ‘Tamper-Evidence’ is a FIPS Level-2 requirement while ‘Tamper-Response’ is a

Level-3 requirement. Not only do our modules have overall Level-2 certification, they also
exceed Level-2 requirements in certain aspects. The ‘Tamper-response’ leading to
automatic erasure of secret data (i.e., CSP zeroization) is a key security feature supported
by the ‘B’ series (TM200ENB, TM100_2ENB, etc.) cards.

Ribbon Communications Inc. Proprietary 11-78

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Three different tamper covers protect components relevant to FIPS functionality. These areas are
defined as "cryptographic boundary" areas, such that all the components within that boundary are
covered by a tamper cover. The following figure shows the block diagram of the TM200ENB, with the
cryptographic areas outlined in blue. Components within the blue-outline boundary are shielded by a
FIPS-compliant tamper cover.

TM200ENB block diagram and cryptographic areas

The cover is installed on the PCB in a secure, FIPS-compliant manner. There are three different tamper
covers:
 HCPM tamper cover: Also referred to as the "main" tamper cover. It covers most of the
cryptographically sensitive components on the module, including a CPLD used for control, the
main CPU (called HCPM), the system RAM, etc.
 JTAG tamper cover: Covers the JTAG port. The JTAG port is used only at the manufacturer site,
during a manufacturing or rework procedure, to load the CPLD image or a secure Boot ROM
software image into the components located underneath the HCPM cover. The JTAG port is
enclosed in a separate FIPS-compliant cover. It allows the manufacturer to utilize the JTAG port
without touching the main HCPM cover.
 DEBUG tamper cover: Secured using a FIPS-approved tamper evident sticker. The debug port
secured by this cover can be accessed from the front panel as long as the tamper sticker is not
applied.
The following figure shows a general view of the TM200ENB and the location of the tamper covers.

Ribbon Communications Inc. Proprietary 11-79

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

TM200ENB tamper covers

11.17.3 FIPS installation procedure and guidelines

NOTE: FIPS Level 2 products require a designated Cryptographic Officer (CO) who is
responsible for all installation and management activities. Specific instructions for the CO
are provided in a separate manual, the User Guide for Cryptographic Officers. This section
includes general guidelines for FIPS module installation and management.

FIPS card installation requires a few steps at the customer site, to be performed only by the responsible
cryptographic officer (CO). This includes the physical module installation, application of tamper
detecting labels on certain surfaces, loading the critical security parameters (CSPs), and periodic
inspection and maintenance tasks.
To guarantee FIPS security, the card must be installed on-site according to the following guidelines.
Details for specific procedure steps are provided in this document.
 The card is shipped from the manufacturer loaded with a trusted boot-ROM image and with the
HCPM and JTAG tamper covers sealed.
 The designated CO at the customer site is responsible for the entire installation process.
 In addition to the sealed tamper covers physically mounted on the card, tamper evident stickers
are provided. Each sticker has a unique serial number.
 Additional dummy-cards can be provided to populate empty slots adjacent to the card. Real (non-
encryption) or dummy cards that surround the encryption card installed in the platform further
block access to the card's PCB surface. It is therefore recommended that customers either install
the encryption card in an end slot (first or last) or install it such that there are other cards (dummy
or real) surrounding the encryption card.
Since sensitive card circuitry is covered by tamper shield installed on the card itself, from a FIPS
perspective the card is safe even without surrounding cards. Nevertheless, dummy card
installation is recommended.
 Stickers and dummy-cards can be ordered as separate parts for the installation process or for
later use.
 The CO is responsible for keeping labels in safe custody, recording their serial numbers, and
keeping track of inventory.

Ribbon Communications Inc. Proprietary 11-80

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 Upon removing the card from its packaging, the CO must inspect these tamper covers for any
gaps or broken labels. If the seals or covers look suspicious, the CO should not proceed with the
installation and should contact the manufacturer.
 When the encryption card is installed and powered up, the CO connects a CLI terminal with a
serial cable to the debug port. A message is displayed on the screen, indicating that the CPLD
password is invalid and must be configured.
 The CO must then configure a password. The password must be stored in a safe location. There
is no other factory or back-door password. If the CPLD password is lost, the card must be shipped
back to the manufacturer for restoration.
 After the CPLD password is configured, the CPLD logic displays more options on-screen, to either
run CPLD diagnostics or proceed directly with the system boot.
 The CO is the only person authorized to load the {private, public} key-pair owned by the card. This
key pair is essentially the identity of the card and is expected to be globally unique.
 After the card is fully configured, loaded with keys, and operates as expected, the CO must apply
tamper stickers to the relevant components. A tamper sticker should also be applied across the
debug port, unless the port must be left accessible for some other purpose. These are not FIPS
requirements, but a recommended security procedure to help expose unauthorized activities
around the card.
 FIPS installation ends with CSPs loaded and front panel secured.
 If there is subsequently any indication that these stickers were tampered with (without being
accounted for by the CO), this is considered a security breach. The CO should periodically inspect
the front panel for any tamper evidence.
 HCPM or JTAG tamper events are serious security issues. In such cases the card must be sent
back to the manufacturer.
 If stickers are broken but the tamper covers are intact, the CO should consider this as a security
event and proceed with full FIPS re-installation using the CPLD password. In this case it's not
required to send the card back to the manufacturer.

11.18 TR200_2
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TR200_2 is a low-cost, single-slot high-density double independent transponder/muxponder that
supports transport of one ETY100G/OTU4 service over OTU4 or two ETY100G/OTU4 services over
OTUC2. It occupies a single slot in OPT96xx platforms. The card maps the ETY100G/OTU4 client
signals to OTU4 or OTUC2.
The TR200_2 works with D-CFP2 coherent line transceivers, supporting configurable DP-QPSK, 8-
QAM, or 16-QAM modulation, with Flex-Grid capabilities. This transceiver includes a coherent receiver,
DSP processing, and soft decision forward error correction, for superior noise tolerance, as well as an
exceptional ability to mitigate CD and PMD impairments.

Ribbon Communications Inc. Proprietary 11-81

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

The TR200_2 provides the following main features:

 Transport of one ETY100G/OTU4 service over OTU4 or two ETY100G/OTU4 services over
OTUC2.
 Four QSFP28 based client transceivers.
 Two CFP2 based line transceivers.
 Hot insertion/removal of QSFP28/CFP2 service without traffic affecting of other ports in the card.
 Supports packet switching.
 GCC features:
 GCC interoperability with the following cards:
 HIO100_2
 HIO500
 MIO200
 TM200EN
 TM400 (100 REG)
 GCC supported in standard (full rate) mode.
 Up to 2 GCC channels for OTUC2/OTU4 ports supported.
 One GCC supported per line port, configurable to either GCC0, GCC1, or GCC2, user
selectable.
 Protection options:
 Switching to protection in under 50 msec.
 WSON restoration using coherent OTU4\OTUC2 wavelengths (< 5 sec switchover).
 DWDM network protection (OTS) based on OLP_S2 or OMSP cards.
 100G/200G line protection (OCHP) based on OLP_S2 card.
 OCH1+1 card protection based on adjacent (< 50 msec switchover for 100G/200G line rates)
with splitter/coupler towards the client. Only single mode clients are supported (LR4 P1).
 Each service can be protected/unprotected regardless of other services. Protection is select-
able based on the port.
 Switching to protection is < 50 msec
 Interoperability support:
 In general TR200_2 interoperates with Apollo OPT96xx and OPT99xx service cards at OTU4
level.
 TM100 (OTU4 DP-QPSK, no GCC).
 HIO500 (OTU4 and OTUC2 in all line code modes supported with GCC).
 TM200_EN (OTU4 and OTUC2 in all line code modes supported with GCC) for 100GE client
drops only.

Ribbon Communications Inc. Proprietary 11-82

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Card views
General view

Front panel

LEDs
LED indicators
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the TR200_2.

Ribbon Communications Inc. Proprietary 11-83

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Marking Item Functions

Client Port (QSFP28) LEDs
(2), (3), (4), Bi-color LED
(5) (Green or
Red):
No fault Lights Green when the Laser is transmitting. Off when the port's transmitter
is off.
LOS Blinks Green/Red when a LOS condition is detected and the Laser is on.
Blinks Red when a LOS condition is detected and the Laser is off.
Fault Lights steadily Red when a BIT fault is detected Laser is on or off.
Line Port (CFP2) LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter is
off.
LOS Red LED Lights steadily when a BIT fault is detected in the OIF1.1 transceiver or the
supply voltage or temperature is OOR.

Functional block diagram

11.18.1 TR200_2 applications

The TR200_2 has four main applications:
 LH 100G transponder - in this application the TR200_2 is used as an Apollo main 100G
transponder service card and can replace TM400 (100G mode), TR100 and TM100 (with PTF)
cards.
 200G 8QAM muxponder - in the application the TR200_2 is used for big metros, long reach DCI,
or small regional networks as a low cost per bit 100GE transport solution. It replaces TM400
(200G mode) and further improves the reach.
 200G 16QAM muxponder - in the application the TR200_2 is used for small metros or short
reach DCI networks as a low cost per bit 100GE transport solution. It replaces TM400 (200G
mode).

Ribbon Communications Inc. Proprietary 11-84

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 OTU4 or OTUC2 regenerator - in this application the TR200_2 is used to regenerate OTU4 or
OTUC2 signals. In the OTU4 regenerator application the OTU4 is fed to one Line port. Two Client
ports equipped with OTU4/SRDR transceivers and connected between themselves and provide
the OTU4 regeneration. The regenerated OTU4 signal is fed from the second Line port.
Similarly, for OTUC2 regenerator application the OTUC2 is fed to one Line port. Two pairs of
Client ports equipped with OTU4/SRDR transceivers are connected between themselves, such
that each pair regenerate an OTU4 signal, totaling an OTUC2 signal. The resulting regenerated
OTUC2 signal is output via the second Line port.
The following figures shows block diagrams of the OTU4 and OTUC2 signals regeneration with
the TR200_2.

OTU4 regenerator application with TR200_2

OTUC2 regenerator application with TR200_2

Ribbon Communications Inc. Proprietary 11-85

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.18.2 TR200_2 port configuration options

The following table describes the line port encoding and FEC type supported configurations.

Line ports configuration

Port No. Port type Encoding FEC type Comments
0,1 OTU4 DP-DQPSK SD-FEC For Interop with AC100M
cards
DP-DQPSK SD-FEC15 Default

DP-DQPSK FEC Low latency

OTUC2 DP-QAM8 SD-FEC15 Default

DP-QAM16 SD-FEC15 --

The following table describes the line port encoding and FEC type supported configurations.

Client ports configuration

Port No. Port type Mapping
2, 3, 4, 5 ETY100G GMP
2, 3, 4, 5 OTU4

OTU4 client port types support FEC only and FEC Ignore is not supported. ETY100G client port types
support RS FEC, depending on the transceiver type.

11.19 TM400
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TM400 is a double-slot Flex-grid and Flex-rate transponder/muxponder card designed for ultra-long
haul, metro-long haul, and metro-regional network configurations. It has four client ports and two line
ports supporting line rates of 2 x 200 Gbps, or 2 x 100 Gbps. The card occupies a double (long) slot in
the Apollo supported platforms. The card can be configured to operate in one of two modes:
transponder or muxponder.
TM400 provides a multi-service, cost-effective solution with 100G/200G wavelengths. The card's OTN
framer terminates with two internal transceivers, each directly connected to a line.

Ribbon Communications Inc. Proprietary 11-86

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Features
 Transponder/muxponder with two independent line ports, supporting OTU4 (100 G) or OTUC2
(200 G).
 High order phase modulation selected for best OSNR and signal reach:
 100 G line - DP-QPSK.
 200 G line - DP-16QAM.
 Four client ports supporting any mix of the following services:
 100 GbE
 OTU4
 10 x 10 GbE (via fanout cable or patch panel)
 Pluggable CFP2 client interface:
 LR4 long-reach up to 10 km (100GE/OTU4)
 SR10 short-reach up to 300 m (OTU4/100GE/10x10GE)
 LR10 up to 10 Km (10x10GE)
 Supports two SD-FEC modes:
 SD-FEC25; provides maximum performance but not compatible with other Apollo cards like:
TM100, CMR100,etc.
 SD-FEC (regular also marked SD-FEC15) for compatibility operation with other Apollo cards.
 GCC features:
 GCC interoperability with the following cards:
 HIO100_2 (100G REG)
 HIO500 (100G REG)
 MIO200 (100G REG)
 FIO100/FIO100M (100G REG)
 CMR100M/CMR100 (100G REG)
 TM100/TR100 (100G REG)
 TM200EN (100G REG)
 TR200_2 (100G REG)
 GCC supported in standard (full rate) mode.
 Up to 4 GCC channels for OTU4 client ports supported.
 Up to 2 GCC channels for OTUC2/OTU4 line ports supported.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.

Ribbon Communications Inc. Proprietary 11-87

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Card views
General view: TM400

Front panel

Ribbon Communications Inc. Proprietary 11-88

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Usage guidelines
The four client interfaces are organized in groups of ten ports each:
Group 1: ports 2 to 11,
Group 2: ports 12 to 21,
Group 3: ports 22 to 31 and
Group 4: 32 to 41.
In each group only one port type of similar rate can be accepted; 100G (OTU4 or 100GE), or N x 10G
(N<=10) up to the aggregate bandwidth of 100G (per client).
For example:
 If port 2 is configured to OTU4, then any configuration to ports 3 to 11 will be rejected.
 If port 2 is configured to 10GE, any attempt to configure one of the other ports to 100G will be
rejected.
 If port 2 is configured to ETY40G, port 3 can be configured only to ETY40G and any configuration
to ports 4 to 11 will be rejected.

LEDs
LED indicators
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there
is no fault in the TM400.
Client Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a
BIT fault is detected in the CFP2 pluggable transceiver, or the
supply voltage or temperature is OOR.
Line Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
LOS Red LED
Blinks when a LOS condition is detected. Lights steadily when
a BIT fault is detected in the TM400 transceiver, or the supply
voltage or temperature is OOR.

Ribbon Communications Inc. Proprietary 11-89

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Functional block diagram

11.19.1 TM400 configuration options

The TM400 provides 4 CFP2 client ports (100GE/OTU4; ER4/LR4/SR10), including fan out connections
for multiple 10G clients. Up to 400G uplink is provided through 2 line ports by one of the following
configurations:
 1 x 100G DP-4QAM (DP-QPSK) up to 5000 Km
 2 x 100G DP-4QAM (DP-QPSK) up to 5000 Km
 1 x 200G DP-16QAM up to 800 Km
 2 x 200G DP-16QAM up to 800 Km
 1 x 100G DP-4QAM (DP-QPSK) up to 5000 Km + 1 x 200G DP-16QAM up to 800 Km

NOTES:
 Operation of the second line port is subject to software license.
 When line ports are configured for 100G and/or 200G, each port in the pair acts
independently and can be configured for a different path.

Typical configuration options are illustrated in the following figure.

Ribbon Communications Inc. Proprietary 11-90

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

TM400 configuration options

11.19.2 TM400_REG100 regenerator application

The TM400 can be configured as a regenerator by assigning it as TM400_REG100. The two LINE ports
are used to implement the regenerator configuration, while the Client ports are not used.
The functions of the regenerator are to clean up and amplify the optical signals transmitted through the
optical line (3R regeneration). Any attempt to assign the Client ports in the TM400_REG100 mode will
be rejected by the software.
When the TM400 is assigned as regenerator (TM400_REG100), the software implicitly configures both
line ports to operate as independent OTU4 ports. It also configures the cross-connect between the lines
for the regenerator application. The user only has to configure the SD-FEC modes, including:
 SD-FEC15 (regularly marked SD-FEC (legacy))
 SD-FEC25

Block diagram

Ribbon Communications Inc. Proprietary 11-91

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

The default mode of the TM400_REG100 is SD-FEC. With SD-FEC, the card operates with
compatibility to legacy SD-FEC (SD-FEC15) and differential QPSK encoding of other devices for
Regional/Long-Haul applications. SD-FEC25 provides a very high error correction, maximizing the
performance of the TM400 for Ultra Long-Haul applications. This mode increases the Bit Rate,
consuming about 25 % more of Over Head (bandwidth) of the OTU4 frame. The SD-FEC25 is not
compatible with legacy SD-FEC, and can be used only if the peer device is configured to the same
mode. In addition, when SD-FEC25 is selected Non Differential QPSK encoding is used.
In the TM400_REG100, each line can be configured to a different SD-FEC mode, according to the
mode of the peer device connected to the line as follows:
 SD-FEC15 <> SD-FEC15
 SD-FEC25 <> SD-FEC25
 SD-FEC15 <> SD-FEC25
 SD-FEC25 <> SD-FEC15

11.20 TM400_2
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The TM400_2 is a new single-slot service card for the Apollo family, a dual transponder-muxponder that
combines software-programmable modulation with an internal switch to provide compact, low power,
and versatile 400G transport of 100GbE and 400GbE clients for metro, regional, and long haul
applications. The card includes a high baud rate standard 400G DCO CFP2 ZR transceiver for line,
configurable to full standard OTUC2 or OTUC4.
The TM400_2 400G offers maximum density (up to 12.8Tbps (client and line) in 5RU) at lowest cost.
These low power cards utilize ~0.15W per Gbps, and ~125W for a fully populated card. These cards
enable a pay-as-you-grow approach by supporting both 100GE and 400GE interfaces in the same card.
The TM400_2 provides the following main features:
 Up to 1.6T total capacity
 D-CFP2 line interfaces supporting 2 x 400G uplinks, with the following modes:
 Metro/DCI and other short distance applications: 400G (OTUC4)
 Regional/long haul: 200G (OTUC2)
 Two QSFP28/56/DD client interfaces with the following modes:
 Dual 100GE muxponder, mapping 2 x 100GE/OTU4 signals to OTUC2.
 Dual 100GE muxponder, mapping 4 x 100GE/OTU4 signals to OTUC4.
 Dual 400GE metro transponder, mapping 2 x 400GE signals to 2 x OTUC4.
 Single 400GE long-haul transponder, mapping 400GE signals to 2 x OTUC2.
 Regenerator mode with fixed OTUC2.

Ribbon Communications Inc. Proprietary 11-92

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 Protection: OCH 1+1, OLP

 GCC for in-band management, supporting 2 GCC channels on uplink ports
 Regeneration mode support
 Interoperable with MIO700, HIO500, and TM200EN cards with new 400G DCO

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 11-93

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

LEDs
LED indicators
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the TR200_2.
Client Ports (QSFP28/56/DD) LEDs
(2-5), (6-9) Bi-color LED
(Green or
Red):
No fault Lights Green when the Laser is transmitting. Off when the port's transmitter
is off.
LOS Blinks Green/Red when a LOS condition is detected and the Laser is on.
Blinks Red when a LOS condition is detected and the Laser is off.
Fault Lights steadily Red when a BIT fault is detected Laser is on or off.
Line Ports (CFP2) LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter is
off.
LOS Red LED Lights steadily when a BIT fault is detected in the OIF1.1 transceiver or the
supply voltage or temperature is OOR.

Functional block diagram

Ribbon Communications Inc. Proprietary 11-94

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.20.1 TM400_2 applications

The TM400_2 is a flexible card that can be configured in any of the following:
 Dual 100GE transponder, mapping 4 x 100GE/OTU4 signals to OTUC4
 Dual 400GE metro transponder, mapping 2 x 400GE signals to 2 x OTUC4
 Single 400GE long-haul transponder, mapping 400GE signals to 2 x OTUC2
 OTU4/C2/C4 regenerator

These high density cards can be combined to maximize transport capacity in the OPT96xx platforms.
For example:
 OPT9603: Up to 3 dual muxponder cards in the platform,
supporting 3 x 2 x 400G --> 6 x 400G muxponders/transponders per platform
 OPT9608: Up to 8 dual muxponder cards in the platform,
supporting 8 x 2 x 400G --> 16 x 400G muxponders/transponders per platform
 OPT9624: Up to 24 dual muxponder cards in the platform,
supporting 24 x 2 x 400G --> 48 x 400G muxponders/transponders per platform
The TM400_2 can be configured into three different modes:
 TM400_2: Configured in regular mode where you can use all clients and all ports.
 TM400_MC: Fixed port configuration with 2 x lines and 1(OTUC2) x client (ETY400G).
 TM400_REG: 2 x line configuration with OTUC2.

Ribbon Communications Inc. Proprietary 11-95

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

The following is an example of TM400_MC configuration.

In this example, the client port ETY100G (port 2) is split into 2 x OTUC2 line ports (ports 0 and1). The
port numbers and cross-connections are fixed, but you can change the wavelengths and line codes.
When used as a TM400_REG, you cannot configure any client port, which are completely disabled.
You can only configure the 2 x line ports, as fixed OTUC2 ports. You can change the wavelength and
line codes of these ports.

The TM400_2 can be used as a transponder or a muxponder. As a transponder, you configure the
ETY400G as a client directly connected into OTUC4 to transmit to the other side.
In muxponder mode, you can configure the ETY100G port to multiplex the lines to OTUC2/OTUC4,
meaning you will have 2 x ODU4s / 4 x ODU4s.

11.20.2 TM400_2 port configuration options

Line ports configuration
Port No. Port type Encoding FEC type Comments
0,1 OTUC2 DP-DQPSK HG-SD-FEC Default
DP-16QAM-PS HG-SD-FEC

OTUC4 DP-16QAM HG-SD-FEC Default

DP-16QAM-PS HG-SD-FEC

Client ports configuration

Port No. Port type Transceiver form Fan out? Number of ports per Sub-interface Mapping
factor transceiver
2 ETY400G QSFP56-DD No 1 ODUFlex BMP
400G
ETY100G QSFP56-DD Yes 4 ODU4 GMP

QSFP28-DD Yes 2 ODU4 GMP

QSFP28 No 1 ODU4 GMP

OTU4 QSFP28-DD Yes 2 ODU4

QSFP28 No 1 ODU4

Ribbon Communications Inc. Proprietary 11-96

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Port No. Port type Transceiver form Fan out? Number of ports per Sub-interface Mapping
factor transceiver
3 ETY100G QSFP56-DD Yes 4 ODU4 GMP
QSFP28-DD Yes 2 ODU4 GMP

OTU4 QSFP28-DD Yes 2 ODU4

4 ETY100G QSFP56-DD Yes 4 ODU4 GMP

5 ETY100G QSFP56-DD Yes 4 ODU4 GMP
6 ETY400G QSFP56-DD No 1 ODUFlex BMP
400G
ETY100G QSFP56-DD Yes 4 ODU4 GMP

QSFP28-DD Yes 2 ODU4 GMP

QSFP28 No 1 ODU4 GMP

OTU4 QSFP28-DD Yes 2 ODU4

QSFP28 No 1 ODU4

7 ETY100G QSFP56-DD Yes 4 ODU4 GMP

QSFP28-DD Yes 2 ODU4 GMP

OTU4 QSFP28-DD Yes 2 ODU4

8 ETY100G QSFP56-DD Yes 4 ODU4 GMP

9 ETY100G QSFP56-DD Yes 4 ODU4 GMP

11.21 TM1200
Supported platforms
 OPT9624
 OPT9608 (requires FCM revision F.00 or higher)
 OPT9603

Description
The TM1200 is a flexible grid, flexible rate, 1.2T transponder/muxponder designed to maximize traffic
carrying capacity for any application or line condition. It maps up to 12 x 100GbE or OTU4 clients, on to
two line interfaces that can be configured from 100 Gbps to 600 Gbps in 50 Gbps increments.
The TM1200 can be configured for use for all applications and in all bit rates and baud rates, including:
 600G DCI
 400G metro
 200G long haul
 100G ultra long haul
The TM1200 provides software-controllable dials for the modulation scheme (BPSK up to 64QAM),
baud rate (34G to 72G), and transmit power. The TM1200 combines this with full spectral flexibility to
select the best channel width to find the “sweet spot” that maximizes the line rate – and thus the
services capacity – for any set of channel conditions. The TM1200 features SD-FEC of 15% and 27%,
with NCG of 12.7dB.

Ribbon Communications Inc. Proprietary 11-97

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Features
 OTU-A adaptive line rates, mapping up to 12 x 100GbE or OTU4 clients, on to two line interfaces
that can be configured on-the-fly from 100 Gbps to 600 Gbps in 50 Gbps increments.
 Transponder/muxponder with 2 independent line ports, supporting up to 600Gbps per line.
 Coupling mode offers the option to split an odd number of clients into two separate lines. For
example, 5x100GbE clients can be split over 2x250Gbps line ports.
 Continuously configurable modulation selected for best OSNR and signal reach:
 1-6 bits/symbol modulation options
 100-600Gbps line rate
 Expert mode - enables fine tuning of the b/sym configuration for maximal link performance
 Up to 12 client ports supporting the following services:
 100 GbE
 OTU4
 Mixtures of OTU4 and 100GE are supported. The 12 ports are organized into 3 groups of 4 ports
each. Each group can be configured separately to either 100G or OTU4. The 4 ports within each
group must have the same configuration, either 100G or OTU4. The dual rate CFP transceivers
can be configured for either OTU4 or 100GE interfaces.
 Pluggable QSFP28 client interfaces, for example:
 AOC30 100GbE active optical cable, up to 30m
 SR4DR short-reach, up to 100m
 LR4DR long-reach, up to 10km
 ER4DR extended reach, up to 40km
 All line to client port cross connects supported; any combination of client and line ports can be
configured.
 Supports two SD-FEC modes in the line:
 SD-FEC27 for maximum performance
 SD-FEC15 for short range applications with minimal spectral bandwidth
 GCC features:
 GCC supported in standard (full rate) mode by default, as well as Apollo proprietary (¼ rate
GCC) reduced mode, user selectable.
 Supports up to 2 channels for OTUA in reduced mode.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.
 Built-in OSNR monitoring and E2E latency measurement

Ribbon Communications Inc. Proprietary 11-98

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Card views
General view

Front panel

Usage guidelines
The TM1200 provides 2 line ports (Port 0 and 1) and 12 client ports (Port 2 to 13).
The line rates supported for OTUA ports in TM800 are 50, 100, 150, 200, 250, 300, 350 and 400, 450,
500, 550, 600 Gbps.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there
is no fault in the TM400.
Client port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a
BIT fault is detected in the CFP2 pluggable transceiver, or the
supply voltage or temperature is OOR.
Line port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
LOS Red LED
Blinks when a LOS condition is detected.

Ribbon Communications Inc. Proprietary 11-99

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Functional block diagram

11.22 TM800
Supported platforms
 OPT9624
 OPT9608 (requires FCM revision F.00 or higher)
 OPT9603

Description
The TM800 is a flexible grid, flexible rate, 800G transponder/muxponder designed to maximize traffic
carrying capacity for any application or line condition. It maps up to 8 x 100GbE or OTU4 clients, on to
two line interfaces that can be configured from 100 Gbps to 400 Gbps in 50 Gbps increments.
The TM800 can be configured for use for all applications and in all bit rates and baud rates, including:
 400G metro
 200G long haul
 100G ultra long haul

Ribbon Communications Inc. Proprietary 11-100

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

The TM800 provides software-controllable dials for the modulation scheme (BPSK up to 64QAM), baud
rate (34G to 72G), and transmit power. The TM800 combines this with full spectral flexibility to select a
channel width to always find the “sweet spot” that maximizes the line rate – and thus the services
capacity – for any set of channel conditions. The TM800 features SD-FEC of 15% and 27%, with NCG
of 12.7dB.

Features
 OTU-A adaptive line rates, mapping up to 8 x 100GbE or OTU4 clients, on to two line interfaces
that can be configured on-the-fly from 100 Gbps to 400 Gbps in 50 Gbps increments.
 Transponder/muxponder with 2 independent line ports, supporting up to 400Gbps per line.
 Coupling mode offers the option to split an odd number of clients into two separate lines. For
example, 5x100GbE clients can be split over 2x250Gbps line ports.
 Continuously configurable modulation selected for best OSNR and signal reach:
 2-4 bits/symbol modulation options
 100-400Gbps line rate
 Expert mode - enables fine tuning of the b/sym configuration for maximal link performance
 Up to 8 client ports supporting the following services:
 100 GbE
 OTU4
 Mixtures of OTU4 and 100GE are supported. The 8 ports are organized into 2 groups of 4 ports
each. Each group can be configured separately to either 100G or OTU4. The 4 ports within each
group must have the same configuration, either 100G or OTU4. The dual rate CFP transceivers
can be configured for either OTU4 or 100GE interfaces.
 Pluggable QSFP28 client interfaces, for example:
 AOC30 100GbE active optical cable, up to 30m
 SR4DR short-reach, up to 100m
 LR4DR long-reach, up to 10km
 ER4DR extended reach, up to 40km
 All line to client port cross connects supported; any combination of client and line ports can be
configured.
 All ports must be configured consistently; all 100G or all OTU4.
 Supports two SD-FEC modes in the line:
 SD-FEC27 for maximum performance
 SD-FEC15 for short range applications with minimal spectral bandwidth
 GCC features:
 GCC supported in standard (full rate) mode by default, as well as Apollo proprietary (¼ rate
GCC) reduced mode, user selectable.
 Supports up to 2 channels for OTUA in reduced mode.
 One GCC supported per port, configurable to either GCC0, GCC1, or GCC2, user selectable.
 Built-in OSNR monitoring and E2E latency measurement

Ribbon Communications Inc. Proprietary 11-101

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Card views
General view

Front panel

Usage guidelines
The TM800 provides 2 line ports (Port 0 and 1) and 8 client ports (Port 2 to 9.
The line rates supported for OTUA ports in TM800 are 50, 100, 150, 200, 250, 300, 350 and 400 Gbps.

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there
is no fault in the TM400.
Client Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a
BIT fault is detected in the CFP2 pluggable transceiver, or the
supply voltage or temperature is OOR.
Line Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
LOS Red LED
Blinks when a LOS condition is detected.

Ribbon Communications Inc. Proprietary 11-102

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Functional block diagram

11.23 TM1200E
Supported platforms
 OPT9624
 OPT9608 (requires FCM revision F.00 or higher)
 OPT9603

Description
The TM1200E programmable transponder/muxponder can transport up to 3 x 400GE clients. The
modulation scheme is adjusted automatically by the device, based on the line rate and bits/symbol, to
optimize the optical performance for a wide range of distances and fiber conditions. Built-in monitoring
provides continuous OSNR and performance feedback.
The TM1200E can be configured for use for all applications, with the following line rates. The
modulation setting (b/sym) can be configured per rate.
 1x400GE (over 2 carriers of 200Gbps line rates) for long haul
 2x400GE for metro
 3x400GE, mapping to 2x600G for DCI applications
The TM1200E maximizes 400GE transport in networks where a flexible grid is available, as well as in
networks with technological constraints to a 50GHz grid.

Features
 OTU-A adaptive line rates, mapping up to 3 x 400GbE clients, on to two line interfaces that can be
configured on-the-fly from 200 Gbps to 600 Gbps in 200 Gbps increments.
 Transponder/muxponder with 2 independent line ports, supporting up to 600Gbps per line.

Ribbon Communications Inc. Proprietary 11-103

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 Coupling mode offers the option to split clients into two separate lines. For example, 400GbE
clients can be split over 2x200Gbps line ports.
 The TM1200E can be configured to snoop LLDP information on an ETY400G port that is
connected to a client device such as a router. When enabled, the following snooping information is
gathered at the ingress of the ETY400G port:
 Chassis ID
 Port ID
 Management Address
 Continuously configurable modulation selected for best OSNR and signal reach:
 1-6 bits/symbol modulation options
 200, 400, 600Gbps line rates
 Expert mode - enables fine tuning of the b/sym configuration for maximal link performance
 Pluggable QSFP56-DD client interfaces, for example:
 AOC10 400GbE active optical cable, up to 10m
 DR4 short-reach, single mode, 1310nm, up to 500m
 FR4 long-reach, single mode, up to 2km
 Supports two SD-FEC modes:
 SD-FEC27 for maximum performance
 SD-FEC15 for short range applications with minimal spectral bandwidth
 GCC features:
 GCC supported in standard (full rate) mode by default, as well as Apollo proprietary (¼ rate
GCC) reduced mode, user selectable.
 Supports up to 2 channels for OTUA in reduced mode.
 One GCC supported per line port, configurable to either GCC0, GCC1, or GCC2, user
selectable.
 Built-in OSNR monitoring and E2E latency measurement

Card views
General view

Ribbon Communications Inc. Proprietary 11-104

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Front panel

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there
is no fault in the TM400.
Client port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a
BIT fault is detected in the CFP2 pluggable transceiver, or the
supply voltage or temperature is OOR.
Line port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
LOS Red LED
Blinks when a LOS condition is detected.

Functional block diagram

Ribbon Communications Inc. Proprietary 11-105

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.24 TM800E
Supported platforms
 OPT9624
 OPT9608 (requires FCM revision F.00 or higher)
 OPT9603

Description
The TM800E programmable transponder/muxponder can transport two 400GE clients, offering the most
400GE clients per application. The modulation scheme is adjusted automatically by the device, based
on the line rate and bits/symbol, to optimize the optical performance for a wide range of distances and
fiber conditions. Built-in monitoring provides continuous OSNR and performance feedback.
The TM800E can be configured for use for all applications, with the following line rates. The modulation
setting (b/sym) can be configured per rate.
 1x400GbE (over 2 carriers of 200Gbps line rates) for long haul
 2x400GbE for metro
 Regeneration mode: Supports optical-electrical-optical (OEO) regeneration of 100G-400G line
rates for all TM800/E and TM1200/E cards. When configured as TM800E_REG, the card supports
OTU-A regeneration of line rates with 100G-400Gbps via both line ports.
The TM800E maximizes 400GE transport in networks where a flexible grid is available, as well as in
networks with technological constraints to a 50GHz grid.

Features
 OTU-A adaptive line rates, mapping up to 2 x 400GbE clients, on to two line interfaces that can be
configured on-the-fly from 100 Gbps to 400 Gbps in 50 Gbps increments.
 Transponder/muxponder with 2 independent line ports, supporting up to 400GbE per line.
 Coupling mode offers the option to split clients into two separate lines. For example, 400GbE
clients can be split over 2x200Gbps line ports.
 The TM800E can be configured to snoop LLDP information on an ETY400G port that is connected
to a client device such as a router. When enabled, the following snooping information is gathered
at the ingress of the ETY400G port:
 Chassis ID
 Port ID
 Management Address
 Continuously configurable modulation selected for best OSNR and signal reach:
 2-4 bits/symbol modulation options
 200, 400Gbps line rates
 Expert mode - enables fine tuning of the b/sym configuration for maximal link performance
 Pluggable QSFP56-DD client interfaces, for example:
 AOC10 400GbE active optical cable, up to 10m
 DR4 short-reach, single mode, up to 500m
 FR4 long-reach, single mode, up to 2km

Ribbon Communications Inc. Proprietary 11-106

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 Supports two SD-FEC modes:

 SD-FEC27 for maximum performance
 SD-FEC15 for short range applications with minimal spectral bandwidth
 GCC features:
 GCC supported in standard (full rate) mode by default, as well as Apollo proprietary (¼ rate
GCC) reduced mode, user selectable.
 Supports up to 2 channels for OTUA in reduced mode.
 One GCC supported per line port, configurable to either GCC0, GCC1, or GCC2, user
selectable.
 Built-in OSNR monitoring and E2E latency measurement

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 11-107

Apollo Reference Manual OPT96xx advanced Layer 1 service cards

LEDs
Marking Item Functions
Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the TM400.
Client port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
F/L Red LED Blinks when a LOS condition is detected. Lights steadily when a BIT fault
is detected in the CFP2 pluggable transceiver, or the supply voltage or
temperature is OOR.
Line port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's
transmitter is off.
LOS Red LED
Blinks when a LOS condition is detected.

Functional block diagram

Ribbon Communications Inc. Proprietary 11-108

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.25 FIO10_5/5B
Supported platform
 OPT9624

Description
FIO10_5 and FIO10_5B are single-slot fabric interface I/O cards that support up to five 10G interfaces
using fixed or tunable pluggable XFP transceivers. Each port of these cards can be configured to serve
as either client or line interface port. The cards are very similar except the support of different traffic
rates. FIO10_5 client interface ports accept 10G LAN, STM-64/OC-192, FC800, FC1200, OTU2, or
OTU2e signals. Client signals are mapped to ODU2 or ODU2e (G.709) and cross connected through
the central universal fabric to the line side. FIO10_5B client interface ports accept 10G LAN, STM-
64/OC-192, OTU2, or OTU2e signals. Client signals are mapped to ODU2 or ODU2e (G.709) and cross
connected through the central universal fabric to the line side.

Features
 50 Gbps total capacity
 Five XFP-based client ports
 Line interface signals are terminated to tributary ODUk signals and transmitted through the fabric
to the outgoing side
 Complies with ITU-T standards for 50 GHz and 100 GHz multichannel spacing (DWDM)
 Supports PM and GCC in-band management, with PM for the signals' native layer (SDH/SONET
and Ethernet)
 Supports GFEC, EFEC (I.4 and I.7), and ignore-FEC modes for OTU2/2e signals
 The FIO10_5 client interfaces are multiservice, software configurable, supporting:
 10G LAN
 STM-64/OC-192
 OTU2
 OTU2e
 FC800
 FC1200
 The FIO10_5B client interfaces are multiservice, software configurable, supporting:
 10G LAN
 STM-64/OC-192
 OTU2
 OTU2e
In FIO10_5B the ODU2 sub-interface under OTU2 port is with PT=21. In addition, FIO10_5B supports
ODU0 but doesn't support the following:
 ODUSlot
 ODUFlex
 FC1200
 FC800

Ribbon Communications Inc. Proprietary 11-109

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

The OPT96xx platforms support a mix FIO10_5 and FIO10_5B, including in the same cage. It is
possible to configure cross-connects between FIO10_5 and FIO10_5B cards (High order ODUs). It is
also possible to reassign FIO10_5 to FIO10_5B keeping the previous configurations.
In addition, FIO10_5B are fully interoperable with FIO10_5 cards. To interoperate with FIO10_5 cards
the user shall edit PT changing it to 20.

Card views
General view

Front panel: FIO10_5

Ribbon Communications Inc. Proprietary 11-110

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Front panel: FIO10_5B

The markings Tx (transmit) and Rx (receive) above each port indicate the port's output and input
connections.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no
fault in the FIO10_5/5B.
Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter
is off.
F/L Red LED Lights steadily when a BIT fault is detected in the pluggable transceiver, or
the supply voltage or temperature is OOR. Blinks when a LOS condition is
detected in the port.

11.26 FIOMR_16/16B
Supported platform
 OPT9624
When using FM1000 1 Tbps universal fabric

Description
The FIOMR_16 and FIOMR_16B are single-slot fabric interface I/O cards that support up to 16 low-rate
client interfaces using SFP transceivers. The cards are very similar except the support of different traffic
rates. Each FIOMR_16 port can be configured to STM-1/OC-3, STM-4/OC-12, GbE, FC1/FC2/FC4,
OTU-1, STM-16/OC-48, DVB-ASI, SDI, and HD-SDI signals. Client-side signals are mapped to G.709
ODU-k and cross connected through the central universal fabric to the egress side. Each FIOMR_16B
port can be configured to STM-1/OC-3, STM-4/OC-12, STM-16/OC-48, GbE, OTU-1,signals. Client-side
signals are mapped to G.709 ODU-k and cross connected through the central universal fabric to the
egress side.

Ribbon Communications Inc. Proprietary 11-111

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Features
 OTU-1 signals are terminated to tributary ODU-k signals and transmitted through the fabric to the
egress side
 OTU-1 ports support GFEC mode
 Supports PM and GCC in-band management, with PM for the signals' native layer (SDH/SONET
and Ethernet)
 Supports subnetwork connection protection with nonintrusive monitoring (SNC-N) for the tributary
signals
The difference between the cards is in the traffic rates they support:
 The FIOMR_16 provides 16 SFP-based client ports, software-configurable to support GbE, 1G
FC, 2G FC, 4G FC, STM-1/OC-3, STM-4/OC-12, STM-16/OC-48, and OTU1 services
 The FIOMR_16B provides 16 SFP-based client ports, software-configurable to support GbE,
STM-1/OC-3, STM-4/OC-12, STM-16/OC-48, and OTU1 services
In addition, the FIOMR_16B supports ODU1 and ODU0 cross-connections to any other FIOMR_16B
and FIO10_5B. It doesn't support any other type of cross-connection through the central fabric (like
ODU2). FIOMR_16B can work with FIOMR_16B via FIO10_5B or FIO100 only. FIOMR_16 can work
with FIOMR_16 via FIO10_5 or FIO100 only.

Card views
General view

Ribbon Communications Inc. Proprietary 11-112

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Front panels: FIOMR_16

Front panels: FIOMR_16B

The port number is indicated under/above each port. The markings T (transmit) and R (receive) near
each port indicate only the port's output and input connections and don't relate to the port LEDs.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the FIOMR_16/16B.
Port LEDs
Tx Green LEDs Lights steadily when the port is transmitting. Off when the port's transmitter is
off.
F/L Red LED Lights steadily when a BIT fault is detected in the pluggable transceiver, or
the supply voltage or temperature is OOR. Blinks when a LOS condition is
detected in the port.

Ribbon Communications Inc. Proprietary 11-113

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.27 FIO100
Supported platform
 OPT9624
When using FM1000 1 Tbps universal fabric

Description
The FIO100 card is a double-slot OTU4v uplink for the 1 Tbps universal fabric of the OPT9624 platform.
The 100G OTU-4 is terminated to its tributary signals (ODUk) and cross connected through the fabric to
the egress side. The FIO100 offers the following main features:
 Multiplexing of up to 80 Low Order (LO) ODUk channels into OTU4
 Low order ODUk including: ODU0, ODU1, ODU2, ODU2e, ODUflex, and ODU4
 Line side interface OTU4v using an OIF1.1 module, supporting:
 PM-QPSK modulation
 Bit rate, 120.579 Gbps (OTU4v)
 SD-FEC (provides NCG of 11.1 dB)
 GCC features:
 GCC interoperability with the following cards:
 CMR100CMR100M (Add and Drop)
 TR100/TM100 (Regenerator)
 TM400 (100G REG)
 GCC supported in standard (full rate) mode.
 One GCC channel supported, configurable to either GCC0, GCC1, or GCC2, user selectable.
 Protection capabilities:
 Employs 1 + 1 Sub Net Connection Protection (SNCP)
 Supports 1+1 Optical Line Protection (OLP)
 ODU4 has a default Payload Type of (PT21)
 The PT for low order ODUk (that are other than ODU4) is PT21

Ribbon Communications Inc. Proprietary 11-114

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Card views
General view

Front panel

Usage guidelines
The FIO100 card can be assigned in any even IO slot of the OPT9624 configured as fabric NE.

Ribbon Communications Inc. Proprietary 11-115

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the FIO100.
Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter is
off.
LOS Red LED Blinks when a LOS condition is detected in the port.

11.28 FIO100M
Supported platform
 OPT9624
When using FM1000 1 Tbps universal fabric

Description
The FIO100M card is a double-slot OTU4 uplink for the 1 Tbps universal fabric of the OPT9624
platform. The 100G OTU-4 is terminated to its tributary signals (ODUk) and cross connected through
the fabric to the egress side.
The FIO100M offers the following main features:
 Multiplexing of up to 80 Low Order (LO) ODUk channels into OTU4
 Low order ODUk including: ODU0, ODU1, ODU2, ODU2e, ODUflex, and ODU4
 Line side interface OTU4v using an CFP module, supporting:
 PM-QPSK modulation
 Bit rate, 120.579 Gbps (OTU4v)
 SD-FEC (provides NCG of 11.1 dB)
 GCC features:
 GCC interoperability with the following cards:
 CMR100/CMR100M (Add and Drop)
 TR100/TM100 (Regenerator)
 TM400 (100G REG)
 GCC supported in standard (full rate) mode.
 One GCC channel supported, configurable to either GCC0, GCC1, or GCC2, user selectable.

Ribbon Communications Inc. Proprietary 11-116

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

 Protection capabilities:
 Employs 1 + 1 Sub Net Connection Protection (SNCP)
 Supports 1+1 Optical Line Protection (OLP)
 ODU4 has a default Payload Type of (PT21)
 The PT for low order ODUk (that are other than ODU4) is PT21

Card views
General view

Front panel

Ribbon Communications Inc. Proprietary 11-117

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

Ports
LED indicators

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed configurations). Off
when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there is no fault
in the FIO100M.
Port LEDs
Tx Green LED Lights steadily when the port is transmitting. Off when the port's transmitter is
off.
F/L Red LED Lights steadily when a BIT fault is detected in the pluggable transceiver, or
the supply voltage or temperature is OOR. Blinks when a LOS condition is
detected in the port.

Functional block diagram

Ribbon Communications Inc. Proprietary 11-118

 Apollo Reference Manual OPT96xx advanced Layer 1 service cards

11.29 Pluggable transceiver modules

Apollo supports pluggable optical transceivers (SFP, SFP+, XFP, QSFP, QSFP28, QSFP-DD, CFP,
and CFP2) for all services, in both colored and noncolored interfaces. Transceiver modules are used for
the entire spectrum of interfaces, including intra-office, short range, and long range. The standardized
modular design of the transceiver components facilitates network maintenance and upgrades since
interchangeable transceiver components are utilized throughout the product line. Instead of replacing
an entire circuit board, a single module can be removed or replaced, for a considerable cost savings.
SFP+ and XFP transceivers are available in colored and noncolored, tunable, and fixed versions. The
tunable SFP+/XFP transceivers support 50 GHz spacing and are available for long-haul network
configurations. QSFP+ transceivers support 40GbE with 4x10G fanout, QSFP28 transceivers support
100GbE/OTU4, QSFP-DD transceivers support up to 400GbE, CFP transceivers are used for client
side (100GbE/OTU4) or line coherent interfaces, and CFP2 transceivers are used for 100 GbE/OTU4
client or fan-out (10GbE or 40GbE) applications.
All pluggable transceivers are field-replaceable, enabling pay-as-you-grow architecture. Simply remove
the old transceiver and plug in a new one.
The following figure illustrates the evolution of 100Gbps optics. DWDM 100G optics are moving from
CFP to CFP2, while “gray” 100G optics are approaching the size of 10G SFPs.

Ribbon Communications Inc. Proprietary 11-119

12 OPT96xx Layer 2 service cards
The following AoC card with L2 switching capabilities is introduced in the current version:
 AoC10_L2: grooms multiple GbE packet flows to GE, 10 GE, or 10 GE wrapped in OTU2e (P2P
or ring). The card occupies a single slot and can be installed in all Apollo platforms. The
AoC10_L2 supports the following features:
 16 x GbE SFP-based ports. These ports are typically client (UNI) ports. Electrical SFPs can
be installed, making the corresponding port 3-speed.
 4 x 10GbE/OTU2e SFP+ based ports with EFEC and tunable SFP+ as uplinks for maximum
reach and 88ch support. These are typically NNI ports, though they can also be used as
client ports.

12.1 AoC10_L2
Supported platforms
 OPT9624
 OPT9608
 OPT9603

Description
The AoC10_L2 is an MPLS service card that supports an advanced Ethernet-based metro-core layer,
enabling NG Ethernet applications such as triple play, VPLS business connectivity, 3G Ethernet-based
aggregation, and CoC bandwidth applications. The AoC10_L2 cards provides complete PB (QinQ) and
MPLS switching functionality, offering scalability and smooth interoperability with IP/MPLS core routers.
The AoC10_L2 supports full interoperability with data cards in the NPT, XDM, and BroadGate
platforms, as well as seamless interfacing with external third-party hardware.

Features
 16 SFP-based client ports, support electrical/optical 1 x GbE interfaces (the port type depends on
inserted SFP).
 Configurable 4 SFP+ -based 10 GbE LAN or OTU2e line ports.
 Two additional internal 10 GbE ports for connecting a AoC10_L2 to a mate card via platform
backplane. (Supported only for OPT9624 and OPT9608 platforms).
 Supports new tunable SFP+ transceivers on the line ports.
 Data throughput of 60 Gbps.
 Configurable data switching modes:
 Ethernet PB (QinQ) switch, based on 802.1d/q/ad - default.
 MPLS-TP Layer 2 switch.
 Interoperability with XDM MCS, BG and NPT L2 cards.
 General MPLS-TP and Ethernet interoperability with third party datacom equipment.

Ribbon Communications Inc. Proprietary 12-1

 Apollo Reference Manual OPT96xx Layer 2 service cards

 Supports Ethernet services including:

 E-LINE Point to Point (P2P) – implemented by VPWS
 E-LAN Multi Point to Multipoint (MP2MP) – implemented by VPLS
 Multicast services
 OAM support:
 Ethernet link OAM
 Ethernet service OAM
 MPLS-TP OAM
 PW OAM
 Port mirroring
 Traffic management including: classifications and mapping, scheduling, and policing.
 Supports in-band and out-of-band management, including: Apollo IMG, OSC, and standard Apollo
GCC0 bytes of OTU2e.
 Layer 2 protection mechanisms including:
 Multi ring ERP < 50 msec Ethernet Ring Protection.
 1:1 linear protection < 50msec for bidirectional LSPs.
 Supports RSTP.
 PW redundancy in MPLS-TP (future).
 Supports GFEC and EFEC
 Environmentally friendly green design disables unused components, minimizing energy
consumption.

Card views
General view

Ribbon Communications Inc. Proprietary 12-2

 Apollo Reference Manual OPT96xx Layer 2 service cards

Front panel

A number and arrow are marked near each port LED. The number identifies the port number and the
arrow points to the location of the port in the upper or lower row. The 16 x 1 GbE SFP ports are
numbered from 0 to 15. The four 10 GbE SFP+ ports are in the lower row at the left and are numbered
from 16 to 19.
The following table describes the AoC10_L2 front panel component functionality.

LEDs

Marking Item Functions

Card LEDs
IS Green LED Lights when the card is IS (assigned and completed
configurations). Off when the card is not assigned.
SW-U Yellow LED Currently not in use.
FAIL Red LED Lights steadily when a fault is detected in the card. Off when there
is no fault in the AoC10_L2.
1 GbE Port LEDs
0 to 15 Bi-color LED Green:
(Green/Yellow)  On - 1 G link is up
 Blinking - link activity
 Off - link is down
Yellow:
 On - 100 M link is up
 Blinking - link activity
 Off - link is down
10 GbE Port LEDs
16 to 19 Bi-color LED Green:
(Green/Red)  On - link is up
 Blinking - link activity
 Off - link is down
Red:
 On - BIT fail
 Blinking - LOS (but BIT is OK)
 Off - BIT is OK and no LOS

Ribbon Communications Inc. Proprietary 12-3

Apollo Reference Manual OPT96xx Layer 2 service cards

Functional block diagram

Ribbon Communications Inc. Proprietary 12-4

13 Artemis product line
Artemis units are fully passive optical platforms that complement the Apollo product line. Artemis
platforms offer a low cost, high modularity, and very high density solution. All passive cards can be
installed in the Artemis, saving the Apollo slots for active service or optical cards (amplifiers, ROADMs,
service cards, fabric, etc.).
Network operators can tailor the Artemis platform configuration to meet specific site requirements,
choosing from a range of cage sizes and number of slots as well as two configuration options: fully
passive platform or active platform that can retrieve inventory information.
The passive cage configuration does not require any power feed. The active cage requires a minimal
power feed to retrieve inventory data (card type, revision, cage location) and transmit it to the main
Apollo controller. Note that while the Artemis platform in this configuration is technically considered
active, all cards installed in the cage are still passive and do not require any power feed.
The Artemis product line includes passive optical platforms that address all your passive optical
component needs for all size range and configurations. It is available in the following shelf types:
 Artemis-1P: compact 1U passive shelf with two single slots

 Artemis-2A: compact 2U active shelf with four single slots

 Artemis-2PE: compact 2U passive shelf with four single slots

 Artemis-4A: compact 4U active shelf with eight single slots

The Artemis shelves can be installed in different rack types, including ETSI, 19", and 23". They feature
an extended operating temperature range of 5 ºC to +60 ºC that makes them ideal for deployment in
street cabinets for outdoor applications.

Ribbon Communications Inc. Proprietary 13-1

 Apollo Reference Manual Artemis product line

A wide range of CWDM and DWDM Mux/DeMux, OADMs, splitters/couplers, DCFs, and filters are
available for use with the Artemis shelves. In addition Apollo passive cards are also supported in the
Artemis.
The passive optical components are available in three different module sizes:
 Single slot
 Double slot
 Quad slot

13.1 Artemis features and functions

Artemis platforms support a wide range of features and functionalities for building an advanced cost-
effective optical network, including:
 Support of both CWDM and DWDM.
 No need for power installation (fully passive elements).
 Used with a range of optical modules, including:
 All filters (OADMs and Mux/DeMux), CWDM and DWDM, include two monitoring points, which is
extremely useful in the process of wavelength equalization.
 Mux/DeMux modules are based on flat-top technology, especially designed to support back-to-
back connectivity, with minimal loss.
 OADMs are based on East-West configuration, allowing network designers and users to use them
as small Mux/DeMux modules.
 Although designed for high density, the Artemis uses LC connectors so that adapters are not
required.
 Artemis meets the CE mark, a mandatory requirement in different parts of the globe.

13.2 Artemis platform layout

This section describes the layout of each Artemis platform. Artemis platforms have been designed to
facilitate simple installation and easy maintenance. Live insertion of modules is allowed to support quick
maintenance and repair activities without affecting traffic. The cage design and mechanical practice of
all platforms conform to international mechanical standards and specifications.

13.2.1 Artemis-1P
The Artemis-1P is a 1U platform housed in a 239.5 mm (9.43 in.) deep, 443 mm (17.4 in.) wide, and
43.4 mm (1.7 in.) high equipment cage. The Artemis-1P features a highly flexible structure with a
significantly small footprint. All modules can be inserted even when the platform delivers live traffic
without affecting it.

Artemis-1P shelf general view

The Artemis-1P platform has a default configuration of two single slots. These slots can be configured
as a double slot, by removing the divider bracket between the single slots.

Ribbon Communications Inc. Proprietary 13-2

 Apollo Reference Manual Artemis product line

The following figure shows the slot numbering of the Artemis-1P.

Artemis-1P slot numbering

13.2.2 Artemis-2A
The Artemis-2A is a 2U platform housed in a 239.5 mm (9.43 in.) deep, 443 mm (17.4 in.) wide, and
87.9 mm (3.46 in.) high equipment cage. The Artemis-2A features a highly flexible structure with a
significantly small footprint. All modules can be inserted even when the platform delivers live traffic
without affecting it. The platform can accommodate a controller card, which enables it to report
inventory information. The Artemis-2A must be connected to a power source to enable the controller
card to operate.

Artemis-2A shelf general view

The Artemis-2A supports Artemis passive cards, as well as passive cards of the Apollo product line.
The Artemis-2A platform has a default configuration of four single slots. These slots can be configured
as two double slots or one quad slot by removing the divider brackets between the single slots.

NOTE: Mix of two single slots and one double slot is also supported in the Artemis-2A.

The following figure shows the slot numbering of the Artemis-2A.

Artemis-2A slot numbering

13.2.3 Artemis-2PE
The Artemis-2PE is a 2U platform housed in a 239.5 mm (9.43 in.) deep, 443 mm (17.4 in.) wide, and
87.9 mm (3.46 in.) high equipment cage. The Artemis-2PE features a highly flexible structure with a
significantly small footprint.

ARTEMIS 2PE front view

Ribbon Communications Inc. Proprietary 13-3

 Apollo Reference Manual Artemis product line

The Artemis-2PE supports the Artemis passive cards, as well as the passive cards of the Apollo
product line.
The Artemis-2PE has a default configuration of four single slots. At the customer site, the platform can
be configured, using the appropriate divider brackets, into various slot combinations, including:
 Up to four single slots (default)
 One or two double slots
 One quad slot
 Any combinations of quad, double, or single slots that fit into the platform frame
The following figures illustrate a few of the slot configuration options in the Artemis-2PE.

Artemis-2PE slot layout options

Ribbon Communications Inc. Proprietary 13-4

 Apollo Reference Manual Artemis product line

13.2.4 Artemis-4A
The Artemis-4A is a 4U platform housed in a 239.5 mm (9.43 in.) deep, 443 mm (17.4 in.) wide, and
175.8 mm (6.92 in.) high equipment cage. The Artemis-4A features a highly flexible structure with a
significantly small footprint. All modules can be inserted even when the platform delivers live traffic
without affecting it. The platform can accommodate a controller card, which enables it to report
inventory information. The Artemis-4A must be connected to a power source to enable the controller
card to operate.

Artemis-4A shelf general view

The Artemis-4A supports Artemis passive cards, as well as passive cards of the Apollo product line.
The Artemis-4A platform has a default configuration of eight single slots. These slots can be configured
in different options to form double slots and quad slots by removing the divider brackets between the
single slots.

NOTE: Any combinations of single slots, double slots, and quad slots are supported in the
Artemis-4A.

The following figure shows the slot numbering of the Artemis-4A.

Artemis-4A slot numbering

Ribbon Communications Inc. Proprietary 13-5

14 Accessories
We offer a variety of accessories for efficient and optimal installation of equipment in racks. The main
types of accessories are described in this section. Contact your local sales representative if you must
make any custom modifications to a standard item.

14.1 Power Distribution Units (PDU)

The Power Distribution Unit (PDU) is a family of devices that can provide power to loads with up to 12
kW power consumption. PDU55AL and PDU77AL also support alarms interface connections.
The PDU family consists of the following units:
 PDU55AL - distributing power for up to 5 loads with 2.4 kW each, including alarms support.
 PDU77AL - distributing power for up to 7 loads, including three loads with 2.4 kW each and 4 with
1200 W each, and including alarms support.
 PDU99 - distributing power for up to 9 loads with up to 2.4 kW each and 12 kW in total, including
circuit breaker tripped alarm support.
The PDU units all have a similar electrical design and differ only in the number of loads that they can
feed. PDU55AL and PDU77AL units have an identical alarms module that provides the alarm
functionality. The PDU99 unit has an integrated CB Tripped alarm circuit.

NOTE: In this manual the generic name PDU or PDUxx is used to describe features and
functions that are common to all three PDU55AL, PDU77AL, and PDU99 units.

A front cover protects the access to the PDU's terminal blocks, power connectors, and circuit breakers.
To gain access to the parts in the PDU this cover must be removed.

NOTE: Maximum operating temperature of the PDU units is 45°C.

The following figure shows a general view of the PDU55AL (the general view of the PDU77AL is
similar). PDU99 has a cover without LEDs.

PDU55AL general view

Ribbon Communications Inc. Proprietary 14-1

 Apollo Reference Manual Accessories

14.1.1 PDU55AL
The PDU55AL is a power distribution unit installed in racks for loads (platforms) that consume up to 12
kW.
The PDU55AL performs the following main functions:
 Redundant power distribution for five loads consuming up to 12 kW. The PDU55AL can
supply power to five loads, each with a power consumption of up to 2400 W. Each load works with
two power sources, where one is the main source (A) and the second is an optional protective
backup source (B).
 Bay alarm indications. The PDU55AL includes three alarm indicators, one for each alarm
severity. When alarms of different severities are received simultaneously, the corresponding alarm
indications light simultaneously.
A buzzer is activated whenever an alarm is present in platforms connected to the PDU55AL. The
buzzer can be shut off by pressing an ACO button on the corresponding platform (xTAM card).
This action doesn't clear the alarm.
 Connecting external alarms from three platforms, each platform supporting up to four alarm
inputs, totaling up to 12 alarm inputs in the PDU55AL. Alarm inputs are implemented by
optocoupler circuits.
The PDU55AL also supports up to 8 alarm outputs, implemented by relay dry contacts, each with
NO and NC positions. Four alarm outputs are allocated to SHELF 1. SHELF 2 and SHELF 3 have
2 alarm outputs each.
 Exporting severity alarms. Three separate groups of severity alarms (a group of four (Critical,
Major, Minor, and buzzer) for each platform) are provided via dry contacts for the customer's
central alarm monitoring system.
 Equipment cable wiring. Use proper cable to feed the equipment, tighten the PDU connectors
and secure two flat screws with a flat screwdriver.
 Feeding cables and wiring. Use proper two hole ring terminal (45° or 90°) for the feeding
connections. Crimp the terminal using proper crimp tools. Add a shrink tube on the neck of each
ring terminal to prevent touching the wiring by accident. Tighten the nuts securely on the PDU
connectors using a ratchet and 10mm socket.

CAUTION: Do not exert excessive tightening torque to secure the connector as this may
cause damage.

The PDU55AL terminal blocks, connectors, and circuit breakers are located on its main board, as
shown in the following figure. The table lists the component functions. The marking in the table
correspond to those in the figures.

NOTE: The description in the table below refers to left side (source A) components of the
PDU55AL. The right side (source B) is a mirror image of the left side and the description is
therefore identical.

Ribbon Communications Inc. Proprietary 14-2

 Apollo Reference Manual Accessories

PDU55AL main board

PDU55AL main board component functions

Marking Designation Function

1, 2, 3, 4, 5 DC output power connectors Five 5W5 connectors for connecting DC power to the
Apollo platforms (loads) with a power consumption of up
to 2400 W.
Circuit breakers Five circuit breaker sockets for inserting (typical 60 A)
A1 to A5 CBs to protect the loads connected to the corresponding
output connectors.
A1 to A5 DC input power terminals For connecting the DC input power to the PDU55AL.
A1 to A5 LED indicators Five Green LEDs. When a LED lights it indicates the
presence of DC input power in the corresponding input
power terminals.

The following figure shows the PDUxxAL Alarms board, and the table lists the functions of the
components corresponding to the figure.

PDUxxAL alarm board

Ribbon Communications Inc. Proprietary 14-3

 Apollo Reference Manual Accessories

PDUxxAL alarms board component functions

Designation Function
SHELF 1, SHELF Three 36-pin SCSI connectors, designated SHELF 1, SHELF 2, and SHELF 3 used to
2, SHELF 3 connect alarm cables to the Apollo platforms installed in the rack. These cables
transmit alarms from the Apollo platform to the PDUxxAL unit.
ALARM IN/OUT 68-pin SCSI connector, used to connect an alarm cable to the customer alarm
monitoring system. This alarm cable transmits the alarms received from the Apollo
platforms by the SHELF 1, SHELF 2 and SHELF 3 connectors, including external
alarm inputs, external alarm outputs, and Apollo severity alarms.
TEST Pushbutton for activating the buzzer and turning on the indicators for test purposes.
ON (power) Green indicator, lights when at least one DC power source is connected to the
PDUxxAL.
CRITICAL Red indicator, lights when the severity of an unacknowledged alarm in the platforms
connected to the PDUxxAL is Critical.
MAJOR Orange indicator, lights when the severity of an unacknowledged alarm in the
platforms connected to the PDUxxAL is Major.
MINOR Yellow indicator, lights when the severity of an unacknowledged alarm in the platforms
connected to the PDUxxAL is Minor.

14.1.1.1 PDU55AL power supply flow example

An example of the power supply flow for an OPT9914 platform and an OPT9624 is illustrated in the
following figure. This configuration uses three DC outputs to feed the three xPFM-14 (A) and (B) pairs
of the OPT9914. The two other outputs feed the two PFM24 (A) and (B) units of the OPT9624.

PDU55AL power supply flow example

Ribbon Communications Inc. Proprietary 14-4

 Apollo Reference Manual Accessories

The PDU55AL supplies independent streams of power to five separate loads. Input power circuits (A1
to A5) for each load is kept completely separate from the input power for the others. Separate input
power cables from the power sources feed into independent circuit breakers on the PDU55AL. (There
are a total of ten circuit breakers on the PDU55AL, supporting redundant power supplies for up to five
loads).
The PDU55AL has ten 5W5 DC output connectors for supplying redundant power to the supported
platforms (OPT9914, OPT9624, OPT9608). The maximum power supplied to each output is up to 2400
W.
The connection of the power sources to the PDU55AL is made through ten pairs of 35 mm2 power
cables from the user's power supply sources (five for each source) and circuit breakers do not have to
be more than 60 A, because the maximum power consumption per cable is never more than 2400 W.
Each input circuit is monitored by a LED. The ten LEDs, located at the middle of the main board, enable
the user to view the status of each input circuit at a glance. This saves the need to connect test
equipment, in case troubleshooting is required.
The nominal DC power voltage is -48 VDC however the input voltage can range from -40.8 VDC
to -57.6 VDC. The internal circuits of the PDU55AL are powered whenever at least one power source is
connected. The required circuit breakers are included in the installation parts kit supplied with the
platforms, and therefore their current rating is in accordance with the order requirements.

14.1.2 PDU77AL
The PDU77AL is a power distribution unit installed in the rack for loads (platforms) that consume up to
12 kW.
The PDU77AL performs the following main functions:
 Redundant power distribution for seven loads consuming up to 12 kW. The PDU77AL can
supply power to seven loads, three with a power consumption of up to 2400 W and four with a
power consumption of up to 1200 W each. Each load works with two power sources, where one is
the main source (A) and the second is an optional protective backup source (B).
 Bay alarm indications. The PDU77AL includes three alarm indicators, one for each alarm
severity. When alarms of different severities are received simultaneously, the corresponding alarm
indications light simultaneously.
A buzzer is activated whenever an alarm is present in platforms connected to the PDU77AL. The
buzzer can be shut off by pressing an ACO button on the corresponding platform (xTAM card).
This action doesn't clear the alarm.
 Connecting external alarms from three platforms, each platform supporting up to four alarm
inputs, totaling up to 12 alarm inputs in the PDU77AL. Alarm inputs are implemented by
optocoupler circuits.
The PDU77AL also supports up to 8 alarm outputs, implemented by relay dry contacts, each with
NO and NC positions. Four alarm outputs are allocated to SHELF 1. SHELF 2 and SHELF 3 have
2 alarm outputs each.
 Exporting severity alarms. Three separate groups of severity alarms (a group of four (Critical,
Major, Minor, and buzzer) for each platform) are provided via dry contacts for the customer's
central alarm monitoring system.
 Equipment cable wiring. Use proper cable to feed the equipment, tighten the PDU connectors
and secure two flat screws with a flat screwdriver.
 Feeding cables and wiring. Use proper two hole ring terminal (45° or 90°) for the feeding
connections. Crimp the terminal using proper crimp tools. Add a shrink tube on the neck of each
ring terminal to prevent touching the wiring by accident. Tighten the nuts securely on the PDU
connectors using a ratchet and 10mm socket.

Ribbon Communications Inc. Proprietary 14-5

 Apollo Reference Manual Accessories

CAUTION: Do not exert excessive tightening torque to secure the connector as this may
cause damage.

The following figure shows the front panel of the PDUxxAL, and the table lists the functions of the front
panel components corresponding to the figure callouts.

NOTE: The description in the table below refers to left side (source A) components of the
PDU77AL. The right side (source B) is a mirror image of the left side and the description is
therefore identical.

PDU77AL main board

PDU77AL main board component functions

Marking Designation Function
1, 2, 3, DC output power Three 5W5 connectors for connecting DC power to the Apollo
connectors platforms (loads) with a power consumption of up to 2400 W.
4, 5, 6, 7 DC output power terminal Four three pin terminal blocks for connecting DC power to the
blocks. Apollo platforms (loads) with a power consumption of up to 1200
W. .
Circuit breakers sockets Three circuit breaker sockets for inserting (typical 60 A) CBs to
A1 to A3 (type A) protect the loads connected to the corresponding output
connectors.
C1 to C4 Circuit breakers sockets Four circuit breaker sockets for inserting (typical 30 A) CBs to
(type B) protect the loads connected to the corresponding output terminal
blocks.

Ribbon Communications Inc. Proprietary 14-6

 Apollo Reference Manual Accessories

Marking Designation Function

A1 to A5 DC input power terminals For connecting the DC input power to the PDU77AL.
A1 to A5 LED indicators Five Green LEDs. When a LED lights it indicates the presence of
DC input power in the corresponding input power terminals.

The following figure shows the PDUxxAL Alarms board, and the table lists the functions of the
components corresponding to the figure.

PDUxxAL alarm board

PDUxxAL alarms board component functions

Designation Function
SHELF 1, SHELF 2, SHELF 3 Three 36-pin SCSI connectors, designated SHELF 1, SHELF 2, and
SHELF 3 used to connect alarm cables to the Apollo platforms installed
in the rack. These cables transmit alarms from the Apollo platform to the
PDUxxAL unit.
ALARM IN/OUT 68-pin SCSI connector, used to connect an alarm cable to the customer
alarm monitoring system. This alarm cable transmits the alarms
received from the Apollo platforms by the SHELF 1, SHELF 2 and
SHELF 3 connectors, including external alarm inputs, external alarm
outputs, and Apollo severity alarms.
TEST Pushbutton for activating the buzzer and turning on the indicators for
test purposes.
ON (power) Green indicator, lights when at least one DC power source is connected
to the PDUxxAL.
CRITICAL Red indicator, lights when the severity of an unacknowledged alarm in
the platforms connected to the PDUxxAL is Critical.
MAJOR Orange indicator, lights when the severity of an unacknowledged alarm
in the platforms connected to the PDUxxAL is Major.
MINOR Yellow indicator, lights when the severity of an unacknowledged alarm
in the platforms connected to the PDUxxAL is Minor.

Ribbon Communications Inc. Proprietary 14-7

 Apollo Reference Manual Accessories

14.1.2.1 PDU77AL power supply flow example

The PDU77AL supplies independent streams of power to three separate loads from three (A1 to A3)
out of the five input circuits. Input power for each load is kept completely separate from the input power
for the others. Separate input power cables from the power sources feed into independent circuit
breakers on the PDU77AL. The maximum power supplied to each output is up to 2400 W. The circuit
breaker rating for this power is 60 A. The backup for these outputs is via input circuits (B1 to B3) and
the corresponding output connectors of Source B.
The two other input power circuits (A4 and A5) supply power to four loads as follows:
 The input A4 splits to two output terminals blocks C1, C2 of 30A max each (corresponding to 1200
W each).
 The input A5 splits to two output terminals blocks C3, C4 of 30A max each (corresponding to 1200
W each).
The backup circuits (B4 and B5) supply power to four corresponding loads as follows:
 The input B4 splits to two output terminals blocks D1, D2 of 30A max each (corresponding to 1200
W each).
 The input B5 splits to two output terminals blocks D3, D4 of 30A max each (corresponding to 1200
W each).
An example of the power supply flow for OPT9914, OPT9603, and OPT9608 platforms is illustrated in
the following figure. This configuration uses three DC outputs to feed the three xPFM-14 (A) and (B)
pairs of the OPT9914. The other outputs (connecting through terminal blocks) are used to feed the two
PFM units of two OPT9608 (A) and (B) and a PFM03 of an OPT9603 (A) and (B).

PDU77AL power supply flow example

Ribbon Communications Inc. Proprietary 14-8

 Apollo Reference Manual Accessories

Each input circuit is monitored by a LED. The ten LEDs, located at the middle of the main board, enable
the user to view the status of each input circuit at a glance. This saves the need to connect test
equipment, in case troubleshooting is required.
The nominal DC power voltage is -48 VDC however the input voltage can range from -40.8 VDC
to -57.6 VDC. The internal circuits of the PDU77AL are powered whenever at least one power source is
connected. The required circuit breakers are included in the installation parts kit supplied with the
platforms, and therefore their current rating is in accordance with the order requirements.

14.1.3 PDU99
The PDU99 is a power distribution unit installed in the racks for loads (platforms) that consume up to 12
kW.

PDU99 general view

NOTE: Maximum operating temperature of the PDU99 unit is 45°C.

WARNINGS:
 PDU99 must be installed only above concrete or other non-combustible surfaces.
 Only trained, qualified personnel should install, maintain, or replace the PDU99

Ribbon Communications Inc. Proprietary 14-9

 Apollo Reference Manual Accessories

The PDU99 performs the following main functions:

 Redundant power distribution for nine loads consuming up to 12 kW: The PDU99 can supply
power to nine loads, with a power consumption of up to 2400 W.
 Alarm indications: The PDU99 includes alarm indication of a tripped circuit breaker by a Red
LED and a dry contact per source. The Red LED and the corresponding relay activates only if
there is a load connected to the relevant circuit breakers.
 Feeding cables and wiring: Use proper two hole lug terminal (45° or 90°) for the feeding
connections.
 Equipment cable wiring. Use proper cable to feed the equipment, tighten the PDU terminal block
connectors and secure two flat screws for each equipment (+/-) with a flat screwdriver.
The PDU99 can be powered with either:
 Single wire connection from an external power supply, using one terminal lug LCDX3/0-14AH-X to
the PDU99 input
or
 Two wire connection from an external power supply, using two terminal lugs LCDX1/0-14AH-X to
the PDU99 input.

The following figure shows the front panel of the PDU99, and the table lists the functions of the front
panel components corresponding to the figure callouts. Front panel components are accessed by lifting
the PDU99 front cover.

NOTE: The description in the table below refers to left side (source A) components of the
PDU99. The right side (source B) is a mirror image of the left side and the description is
therefore identical.

PDU99 main board front view

Ribbon Communications Inc. Proprietary 14-10

Apollo Reference Manual Accessories

PDU99 main board component functions

Marking Designation Function
1 to 9 DC output power terminal Nine power terminal pairs for connecting DC power to the
blocks platforms (loads) with a power consumption of up to 2400
W. Up to 5x60A connections on each source.
A1 to A9 Circuit breakers sockets Nine circuit breaker sockets for inserting CBs to protect the
(source A) loads connected to the corresponding output connectors.
The CB should be up to 60 A each and up to 300 A in total.
Ds 1 LED indicators Two green LEDs. LED lights ON indicates the presence of
Ds 2 DC input power in the corresponding input power source.
Ds 1 is for source A and ds 2 is for source B.
Ds 3 LED indicators Two red LEDs. LED lights ON indicates that one of the
Ds 4 circuit breakers is tripped. Ds 3 indicates source A CB fell
and ds 4 indicates that source B CB fell.

PDU99 main board back view

PDU99 main board component functions

Marking Designation Function

A1 to A4 DC input power terminals Terminals for connecting the DC input power to the
PDU99.

Ribbon Communications Inc. Proprietary 14-11

 Apollo Reference Manual Accessories

14.1.3.1 PDU99 power supply flow example

An example of the power supply flow for an OPT9914 platform and an OPT9624 is illustrated in the
following figure. This configuration uses three DC outputs to feed the three xPFM-14 (A) and (B) pairs
of the OPT9914. The two other outputs feed the two PFM24 (A) and (B) units of the OPT9624. PDU99
can distribute power to all types of our platforms as well as 3rd party products.

PDU99 power supply flow example

Each input source is monitored by a green LED. The two LEDs, located at the middle of the main
board, enable the user to view the status of each input source.
The nominal DC power voltage is 48 VDC, however the input voltage can range from -40.8 VDC to 57.6
VDC. The internal circuits of the PDU99 are powered whenever at least one power source is
connected. The required circuit breakers are included in the installation parts kit supplied with the
platforms, and therefore their current rating is in accordance with the order requirements.

Ribbon Communications Inc. Proprietary 14-12

 Apollo Reference Manual Accessories

14.2 RAP-E
The RAP-E is a power distribution and alarm panel installed in the rack for platforms that consume
more than 3000 W.

NOTE: The RAP-E supports power supply for any platform that consumes more than
3000 W in any of the following product lines:
 Apollo product line
 Neptune product line
 XDM product line

The RAP-E performs the following main functions:

 Redundant power distribution for one or two platforms. The RAP-E can support either one or
two platforms. Each platform works with two power sources, where one is the main source (A) and
the second is an optional protective backup source (B).
In the default configuration, the RAP-E supplies independent streams of power to two separate
platforms. Input power for one platform is kept completely separate from the input power for the
second. Separate input power cables from the power sources feed into independent circuit
breakers on the RAP-E unit. (There are a total of eight circuit breakers on the RAP-E, supporting
redundant power supplies for up to two platforms.) An example of the power supply flow for two
OPT9624 platforms is illustrated in the following figure.

Example of RAP-E connections to two OPT9624

Ribbon Communications Inc. Proprietary 14-13

Apollo Reference Manual Accessories

An example of the power supply flow for two XDM-3000 platforms is illustrated in the following
figure. Note that in the case of XDM-3000 only three out of the four DC circuits of the RAP-E are
used.

Example of RAP-E connections to two XDM-3000

The RAP-E has eight 5-pin DC output connectors for supplying redundant power to the supported
platforms. The maximum power supplied to each platform is up to 4500 W, in accordance with the
platform type.
Note that with the default configuration, the power cables from the user's power supply sources to
the RAP-E do not have to be more than 25 mm2 thick, and the circuit breakers do not have to be
more than 65A, because the maximum power consumption per cable is never more than 2250 W.
 Redundant power distribution for one platform. The RAP-E can support power supply to one
platform. In this case the platform works with two power sources, where one is the main source
(A) and the second is an optional protective backup source (B). Separate input power cables from
the power sources feed into independent circuit breakers on the RAP-E unit. (There are a total of
four circuit breakers installed in this case). The power supply flow for a single platform is illustrated
in the following figure.

Ribbon Communications Inc. Proprietary 14-14

 Apollo Reference Manual Accessories

RAP-E redundancy connections to a single platform

NOTE: The following connection options are possible:

 Optimal power connection: Works with four 25 mm2 power cables to support two
OPT9624 platforms, with maximum power of 4500 W each. Or, works with two 25 mm2
power cables to support one OPT9624 platform, with a maximum of 4500 W.
 Single cable connection: Works with a single 25 mm2 power cable to support a single
OPT9624 platform only, with maximum 2200 W for that platform. This requires the use
of a metal bridge, designed with two circuit breakers, and two power cables connected
from the RAP-E to the platform.

The nominal DC power voltage is -48 VDC ranging to -72 VDC. The internal circuits of the RAP-E
are powered whenever at least one power source is connected. The presence of DC power within
the RAP-E is indicated by a POWER ON indicator.
Each DC power circuit of each platform is protected by two circuit breakers that also serve as a
power on/off switch for the corresponding circuit. The required circuit breakers are included in the
installation parts kit supplied with the platforms, and therefore their current rating is in accordance
with the order requirements.
The circuit breakers are installed during the RAP-E installation. To prevent accidental changing of
a circuit breaker’s state, the circuit breakers can be reached easily after opening the front cover of
the RAP-E. The circuit breaker state (ON or OFF) can be seen through openings in the RAP-E
cover.

Ribbon Communications Inc. Proprietary 14-15

 Apollo Reference Manual Accessories

 Bay alarm indications. The RAP-E includes three alarm indicators, one for each alarm severity.
When alarms of different severities are received simultaneously, the corresponding alarm
indications light simultaneously.
A buzzer is activated whenever an alarm is present in platforms connected to the RAP-E. The
buzzer can be shut off by pressing an ACO button on the corresponding platform. This action
doesn't clear the alarm.
 Connecting external alarms from two platforms, each platform supporting up to four alarm inputs
and four alarm outputs (via dry contacts) to the customer's central alarm monitoring system.
Customers who wish to define external alarms should refer to the explanation of the dry contacts
electrical maximum rating requirements for external alarms in the System Specification.
Note that the RAP-E supports up to eight input and output external alarms. These alarms are
allocated four to each platform.
 Exporting severity alarms. Two separate groups of severity alarms (a group of four (Critical,
Major, Minor, and buzzer) for each platform) are provided via dry contacts for the customer's
central alarm monitoring system.
The following figure shows the front panel of the RAP-E, and the table lists the functions of the front
panel components corresponding to the figure callout numbers.

RAP-E front panel

RAP-E front panel component functions

No. Designation Function
1 SOURCE A Opening for the four circuit breakers (two per Apollo platform installed
in the rack). These circuit breakers are used as ON/OFF power
switches and overcurrent protection for the DC power source A.
2 TEST Pushbutton for activating the buzzer and turning on the indicators for
test purposes.
3 POWER ON Green indicator, lights when at least one DC power source is
connected to the RAP-E.
4 CRITICAL Red indicator, lights when the severity of an unacknowledged alarm
in the platforms connected to the RAP-E is Critical.
5 MAJOR Orange indicator, lights when the severity of an unacknowledged
alarm in the platforms connected to the RAP-E is Major.
6 MINOR Yellow indicator, lights when the severity of an unacknowledged
alarm in the platforms connected to the RAP-E is Minor.
7 Buzzer (concealed under Operates when at least one unacknowledged Major or Critical alarm
cover) is present in the platforms connected to the RAP-E.
8 SOURCE B Same as Item 1 for DC source B.

Ribbon Communications Inc. Proprietary 14-16

 Apollo Reference Manual Accessories

The RAP-E connectors are located on the circuit board, as shown in the following figure. The table lists
the connector functions. The index numbers in the table correspond to those in the figures.

RAP-E connectors

RAP-E connector functions

No. Designation Function

1, 2, 3, 4 Output 1, Output 2, Output 3, Four 5-pin D-type connectors, designated Output 1, Output 2,
and Output 4 Output 3, and Output 4, used to connect DC power to the Apollo
DC output power platforms.
5 ALARM IN/OUT 68-pin SCSI connector, used to connect an alarm cable to the
customer alarm monitoring system. This alarm cable transmits
the alarms received from the Apollo platforms by the SHELF 1
and SHELF 2 connectors, including external alarm inputs,
external alarm outputs, and Apollo severity alarms.
6, 7 SHELF 1 and SHELF 2 Two 36-pin SCSI connectors, designated SHELF 1 and
SHELF 2, used to connect alarm cables to the Apollo platforms
installed in the rack. These cables transmit alarms from the
Apollo platform to the RAP-E unit.

14.3 xRAP-100
The xRAP-100 is a power distribution and alarm panel for platforms installed in racks.

NOTE: The xRAP-100 supports power supply for the following product lines:
 BG product line
 XDM-100
 OPT96xx product line

The xRAP-100 performs the following main functions:

 Power distribution for up to four platforms. The nominal DC power voltage is -48 VDC or -60
VDC. The xRAP-100 supports connection to two separate DC power sources, where one is the
main power input (A) and the second is an optional protective backup power input (B). This
enables power source redundancy to platforms that support this feature. The CB rating installed in
the xRAP-100 for feeding a single platform is max. 35 A. The total power that can be provided by
the xRAP-100 is max. 5.2 kW.

Ribbon Communications Inc. Proprietary 14-17

Apollo Reference Manual Accessories

xRAP-100 power supply flow

Each power source can be connected to the xRAP-100 with a dual input line; we will designate
this option as dual input power cable configuration (for feeding platforms like the OPT96xx product
line). However, in the default configuration, the xRAP-100 is supplied with bridge components,
connecting the negative terminals of the two power input lines. This enables users to connect the
unit with an up to 50 mm2 single input power cable. When feeding with dual input power cable
configuration is preferred, the bridge components must be removed.
Power is connected through four independent circuit breakers to three 3-pin and one 5-pin output
connectors for feeding the platforms. The total power that can be provided by the unit is 5.2 kW
maximum. The power is equally distributed via each input power line: 2600 W to two 3-pin
connectors (up to 1300 W per platform), and 2600 W to the third 3-pin and to the 5-pin
connectors. The 5-pin output power connector can feed a high-power platform (for example, XDM-
1000 requiring 2200 W). In such a case, the third 3-pin connector is able to provide the rest of the
power (in this example, 2600 - 2200 = 400 W). We recommend not using the third 3-pin connector
when a high-power platform is connected.

NOTE: The xRAP-100 can provide power to four 9600 platforms. In this case, three of
them are connected to the 3-pin and one to the 5-pin D-type connectors.

Note that with the dual input cable configuration, the power cables from the user's power supply
sources to the xRAP-100 do not have to be more than 25 mm2 thick, and the circuit breakers do
not have to be more than 32A, except for the circuit breaker connected to the 5-pin connector that
can be up to 65A because the maximum power consumption per cable is never more than 2600
W. The xRAP-100 reflects the response to the need of customers who are not able to support 50
mm2 feeding power cables when connecting four platforms.

Ribbon Communications Inc. Proprietary 14-18

 Apollo Reference Manual Accessories

NOTE: Users who prefer to work with a single power cable from their main power supply
(and optionally, a single power cable from the protective power supply) can still work with a
single cable if they:
 Work with a single 25 mm2 power cable to support two platforms only, with a maximum
of 2600 W for both platforms, where each platform is limited to a maximum of 1300 W
per platform.
 Work with a single 25 mm2 power cable to support four platforms, where each platform
is limited to a maximum of 650 W per platform. This configuration option requires the
use of the metal bridge component supplied for this purpose.
 Work with a single 50 mm2 power cable to support four platforms with a maximum of
1300 W for each platform. This configuration option requires the use of the metal
bridge component supplied for this purpose.

The nominal DC power voltage is -48 VDC ranging to -72 VDC. The internal circuits of the xRAP-
100 are powered whenever at least one power source is connected. The presence of DC power
within the xRAP-100 is indicated by a POWER ON indicator.
Each DC power circuit of each platform is protected by a circuit breaker that also serves as a
power on/off switch for the corresponding circuit. The required circuit breakers are included in the
installation parts kit supplied with the platforms, and therefore their current rating is in accordance
with the order requirements. To prevent accidentally changing a circuit breaker state, the circuit
breakers can be reached only after removing the xRAP-100 front cover. The circuit breaker state
(ON/OFF) can be seen through openings in the cover.

NOTE: For connecting an OPT96xx platform to the 5-pin connector, use a 5-pin D-type
male to 2-pin D-type female cable.

 Bay alarm indications: The xRAP-100 includes three alarm indicators, one for each alarm
severity. When alarms of different severities are received simultaneously, the different alarm
indications light simultaneously.

NOTE: BG platforms support only two alarm indications: Major and Minor.

A buzzer is activated whenever a Major or Critical alarm is present in a XDM platform connected
to the xRAP-100 or a Major alarm in a BG or OPT96xx platform connected to the xRAP-100.
 Connection of alarms from up to four supported platforms, each with maximum four alarm inputs
and two alarm outputs.
The following figure shows the front panel of the xRAP-100, and the table lists the functions of the front
panel components corresponding to the figure callout numbers.

Ribbon Communications Inc. Proprietary 14-19

 Apollo Reference Manual Accessories

xRAP-100 front panel component functions

No. Designation Function
1 SOURCE A Four circuit breakers (designated SHELF 1, SHELF 2, SHELF 3, and SHELF 4
– one per platform installed in the rack). These circuit breakers are used as
ON/OFF power switches and overcurrent protection for the DC power source A.
-- Buzzer (concealed Operates when at least one unacknowledged Major or Critical alarm is present
under cover) in the platforms connected to the xRAP-100.
2 TEST Pushbutton for activating the buzzer and turning on the indicators for test
purposes.
3 POWER ON Green indicator, lights whenever at least one DC power source is connected to
the xRAP-100.
4 CRITICAL Red indicator, lights when the severity of an alarm in the platform connected to
the xRAP-100 is Critical.
5 MAJOR Orange indicator, lights when the severity of an alarm in the platform connected
to the xRAP-100 is Major.
6 MINOR Yellow indicator, lights when the severity of an alarm in the platform connected
to the xRAP-100 is Minor.
7 SOURCE B Same as Item 1 for DC source B.

The xRAP-100 connectors are located on its circuit board, as shown in the following figure. The table
lists the connector functions. The index numbers in the table correspond to those in the figure.

xRAP-100 connectors

xRAP-100 connectors
No. Designation Function
1, 2, 3, 4 Shelf alarms Four 36-pin SCSI connectors designated SHELF 1, SHELF 2,
SHELF 3, and SHELF 4, for connecting alarm input and output lines
to the platforms and other equipment installed in the rack
5 ALARM IN/OUT 68-pin SCSI connector, for connecting alarm input and output lines
to the customer alarm monitoring facility
6, 7, 8 Platforms DC input power Three 3-pin D-type connectors designated Shelf 1, Shelf 2, and
Shelf 3 for connecting DC power to regular power platforms
9 Shelf DC input, high power 5-pin D-type connector designated Shelf 4 for connecting a high or
regular power platform

Ribbon Communications Inc. Proprietary 14-20

 Apollo Reference Manual Accessories

14.4 RAP-4B
The RAP-4B is a power distribution and alarm panel for platforms installed in racks.

NOTE: The RAP-4B supports operation with BG, XDM (100, 300, 900), Neptune, and
OPT96xx platforms.

The RAP-4B performs the following main functions:

 Power distribution for up to four protected platforms installed on the same rack. The nominal
DC power voltage is 48 VDC or 60 VDC. Since the supported platforms can use redundant power
sources, the RAP-4B supports connection to two separate DC power circuits.
Each DC power circuit of each platform is protected by a circuit breaker, which also serves as a
power on/off switch for the corresponding circuit. The required circuit breakers are included in the
installation parts kit supplied with the platforms, and therefore their current rating is in accordance
with the order requirements. The CB rating installed in the RAP-4B for feeding a single platform is
max. 35 A. The total power that can be provided by the RAP-4B is max. 4 x 1.1 kW (4.4 kW).

NOTE: The maximum power that can be supplied by the RAP-4B to a single platform is
not more than 1.1 kW.

The circuit breakers are installed during the RAP-4B installation. To prevent accidentally changing
a circuit breaker state, the circuit breakers can be reached only after removing the RAP-4B front
cover. The circuit breaker state (ON/OFF) can be seen through translucent covers.
 Bay alarm indications: The RAP-4B includes three alarm indicators, one for each alarm severity.
When alarms of different severities are received simultaneously, the different alarm indications
light simultaneously.

NOTE: BG platforms support only two alarm indications, Major and Minor.

A buzzer is activated whenever a Major or Critical alarm is present in an XDM platform or a Major
alarm in a BG or 96xx platform connected to the RAP-4B.
 Connection of alarms from up to four platforms, with max. four alarm inputs and two alarm
outputs.
The following figure shows the front panel of the RAP-4B, and the table lists the functions of the front
panel components corresponding to the figure callout numbers.

RAP-4B front panel

Ribbon Communications Inc. Proprietary 14-21

 Apollo Reference Manual Accessories

RAP-4B front panel component functions

No. Designation Function
1 SOURCE A Four circuit breakers (designated PLATFORM 1, PLATFORM 2, PLATFORM 3,
and PLATFORM 4 – one per platform installed in the rack). These circuit
breakers are used as ON/OFF power switches and overcurrent protection for
the DC power source A.
--- Buzzer (concealed Operates when at least one unacknowledged Major or Critical alarm is present
under cover) in the platform connected to the RAP-4B.
2 TEST Pushbutton. Press to activate the buzzer and turn the indicators on for test
purposes.
3 POWER Green indicator; lights when at least one DC power source is connected to the
RAP-4B.
4 CRITICAL Red indicator; lights when the severity of at least one of the alarms in the
platform connected to the RAP-4B is Critical.
5 MAJOR Orange indicator; lights when the severity of at least one of the alarms in the
platform connected to the RAP-4B is Major.
6 MINOR Yellow indicator; lights when the severity of at least one of the alarms in the
platform connected to the RAP-4B is Minor.
7 SOURCE B Same as Item 1 for DC source B.

The RAP-4B alarm connectors are on its circuit board, as shown in the following figure. The table lists
the connector functions. The index numbers in the table correspond to those in the figure.

Rap-4B alarm connectors on the circuit board

RAP-4B connector functions

No. Designation Function
1, 2, 3, 4 Platform alarms Four 36-pin SCSI connectors designated PLATFORM 1, PLATFORM 2,
PLATFORM 3, and PLATFORM 4, for connecting alarm input/output lines
from the platforms to the RAP-4B.
5 ALARM IN/OUT 68-pin SCSI connector, for connecting alarm input lines from the
customer's equipment to the platforms, and alarm output lines from the
platforms to the customer alarm monitoring facility.

Ribbon Communications Inc. Proprietary 14-22

 Apollo Reference Manual Accessories

14.5 AC/DC-DPS850-48-3 power system

The AC/DC-DPS850-48-3 power system is a high efficient and extreme compact system that provides
an optimal solution for space-critical, low power telecommunication applications, requiring flexible DC
power supplies.
The main components of the power system are three rectifier units, each capable of supplying up to
850 W at a nominal voltage of 48 VDC.
Each power system includes three DPR-850B-48 rectifier units, an CSU-502 controller unit, two battery
circuit breakers, and six load circuit breakers, all enclosed in an 437.4 x 270 x 43.4 mm (W x D x H)
miniature platform. All connections to the system are made from the rear of the unit.
The rectifiers are connected in parallel in a redundant (n+1) load-sharing mode. The current-sharing
mode enables each rectifier to supply an equal load current, thus increasing system reliability. In case a
failure occurs in one of the units, the current drawn from the other rectifiers is increased to supply the
required load current. The DPR-850B-48 is designed for online replacement (hot-swappable) to support
non-traffic-affecting operation of telecommunication equipment.
In addition, to support high availability, the system has an option to connect backup batteries. In this
case, while the system is operating normally it also charges the batteries in addition to supplying power
to the load. If the AC source fails, the batteries, which are connected on the rectifier output bus, supply
the load current.
The state-of-the-art power supply is designed to match constant-power characteristics of modern
telecom loads, and thus reduces the number of rectifiers required in battery backed-up systems. The
AC/DC-DPS850-48-3 features a modular architecture for easy system maintenance and repair.

AC/DC-DPS850-48-3 power system, general view

The AC/DC-DPS850-48-3 system has connectors for connecting the load, batteries, AC source, and
the system alarms, at the rear of the unit. It also includes circuit breakers that protect the power supply
against load overcurrent at the battery and rectifier outputs.
The CSU-502 module provides control and monitoring functions. It is supplied preconfigured, ready for
immediate use. It supports system voltage, load current, status, and alarms that can be changed and
displayed on the LCD display.
The AC/DC-DPS850-48-3 platform is preconfigured for fast installation and setup. All system settings
are fully software-configured and stored in transferable configuration files for repeated one-step system
setup.
The AC/DC-DPS850-48-3 platform is supplied with two kits of brackets for installation in 19" or ETSI
racks.

Ribbon Communications Inc. Proprietary 14-23

 Apollo Reference Manual Accessories

The following main features are supported by the AC/DC-DPS850-48-3 power system:
 19"/ETSI power platform for 48 VDC @ 2250 W (max.) in non-redundant application
 Single phase 100-240 VAC input source
 Three DPR-850B-48 rectifier units
 Light weight plug-in modules for simple installation and maintenance
 Hot swappable rectifier and control modules
 Front access to the circuit breakers and control module for simplified operation and maintenance

14.5.1 AC/DC-DPS850-48-3 front view

The AC/DC-DPS850-48-3 front view is shown in the following figure.

AC/DC-DPS850-48-3 front view

The following table describes the AC/DC-DPS850-48-3 front view components.

AC/DC-DPS850-48-3 front component functions

Designation Component Function
LD1 to LD6 Load DC voltage circuit Act as ON/OFF switches for connecting loads LD1 to LD6 to
breakers. Ratings: the system DC voltage bus. Protect the system from load
LD1, LD2 = 12 A overcurrent.
LD3, LD4 = 20 A
LD5, LD6 = 30 A
BAT1, BAT2 Battery circuit breakers, 50 Act as ON/OFF switches for connecting two battery systems
A each to the DC voltage bus. Protect the system from battery
overload.
Controller unit Provides control, provisioning, configuration, and display for
CSU-502 the system.
SNMP Remote control connector, Provides SNMP communication with the CSU 502 for
interface RJ-45 (optional per order) controlling the system from remote (via a modem).
DPR-850B-48 Rectifier unit 850 W
Provides AC to DC power conversion for the system. Up
to three units can be installed in a platform. The system
max. power is 2250 W.

Ribbon Communications Inc. Proprietary 14-24

 Apollo Reference Manual Accessories

14.5.2 AC/DC-DPS850-48-3 rear view

The AC/DC-DPS850-48-3 general rear view is shown in the following figure.

AC/DC-DPS850-48-3 general rear view

To enable understanding enlarged views of sections on the rear panel are provided in the following
figures.
The AC/DC-DPS850-48-3 detailed battery and load connections are shown in the following figure.

AC/DC-DPS850-48-3 battery and load connections

The AC/DC-DPS850-48-3 AC source and alarm connections are shown in the following figure.

Ribbon Communications Inc. Proprietary 14-25

 Apollo Reference Manual Accessories

AC/DC-DPS850-48-3 AC source and alarm connections

The following table describers the AC/DC-DPS850-48-3 rear panel component functions (connections).

AC/DC-DPS850-48-3 rear panel component functions

Designation Component Function
TA RJ-45 connector Connects the Ambient temperature sensor to the system. The
sensor with an appropriate cable is supplied, by default, with the
system. If not connected, Ambient Temperature will not affect the
power supply control system.
TB RJ-45 connector Connects the BAT1 temperature sensor to the system. The sensor
with an appropriate cable is supplied, by default, with the system. It
must be connected, in case backup batteries are used.
LOAD1 to Screw terminal Each terminal provides load connection to the system DC output
LOAD6 socket, 2-positions (6 bus. The recommended cable cross-section for connecting the
places) loads are:
 LOAD1 and LOAD2, AWG 14 (2.5 mm2)
 LOAD3 and LOAD4, AWG 12 (4 mm2)
 LOAD5 and LOAD6, AWG 10 (10 mm2).
BAT 2 and Screw terminal Connects the corresponding BAT 2 and BAT 1 battery packs to the
BAT 1 socket, 2-positions (2 system DC output bus. The recommended cable cross-section for
places) connecting the each battery pack is AWG 6 (16 mm2).
ALARM D-type, 26-pin, female Connects the Systems alarm output signals. The signals are
SIGNAL connector delivered by six sets of relay dry contacts.
PE, L, N, Terminal socket, Connects the AC source input voltage to the system:
3-positions  PE - Ground
 L - Line
 N - Neutral
The connections must be made with 3 x AWG 14 (2.5 mm2) cables.

Ribbon Communications Inc. Proprietary 14-26

 Apollo Reference Manual Accessories

14.6 AC/DC PS 6/8.7kW power system

The AC/DC PS 6/8.7kW power system is an ideal solution for supplying high power to
telecommunication applications requiring compact, efficient, and flexible DC power supplies. The main
components of the power system are two types of rectifier units, one capable of supplying up to 2 kW
and the other up to 2.9 kW at a nominal voltage of 48 VDC.
We offer two types of the power system as described in the following table.

AC/DC PS 6/8.7kW configurations

System Designation Rectifier type Max. system power

AC/DC PS 6kW DPR 2000 6 kW
AC/DC PS 8.7kW DPR 2900 8.7 kW

The two power systems are identical in features, functionality, and physical dimension and differ only in
the maximum output power capability.

IMPORTANT: Each AC/DC PS 6/8.7kW system must be equipped with rectifiers of the
same type. Mixing rectifiers of different types is not allowed. For example, if an AC/DC PS
6kW is configured, the three rectifiers must be DPR 2000.

Each power system includes a number of DPR 2000/DPR 2900 rectifier units, an CU-19C A controller
unit, and a Power Distribution Unit (PDU), all enclosed in a 482 x 299 x 88 mm (W x D x H) platform. All
connections to the system are made from the rear on the PDU.
The rectifiers are connected in parallel in a redundant (n+1) load-sharing mode. The current-sharing
mode enables each rectifier to supply an equal load current, thus increasing system reliability. In case a
failure occurs in one of the units, the current drawn from the other rectifiers is increased to supply the
required load current. The DPR 2000/DPR 2900 is designed for online replacement (hot-swappable) to
support non-traffic-affecting operation of telecommunication equipment.
In addition, to support high availability, the system has an option to connect to two sets of backup
batteries. In this case, while the system is operating normally it also charges the batteries in addition to
supplying power to the load. If the AC source fails, the batteries, which are connected on the rectifier
output bus, supply the load current.
The state-of-the-art power supply is designed to match constant-power characteristics of modern
telecom loads, and thus reduces the number of rectifiers required in battery backed-up systems. The
AC/DC PS 6/8.7kW features a modular architecture for easy system maintenance.
The AC/DC PS 6/8.7kW system PDU has terminals for connecting the load, battery, AC source, and
system alarms. It also includes circuit breakers that protect the power supply against load overcurrent
at the battery and rectifier outputs.
The CU-19C A module provides control and monitoring functions. It is supplied preconfigured, ready for
immediate use. It supports system voltage, load current, status, and alarms that can be changed and
displayed on the LCD display.
The AC/DC PS 6/8.7kW platform is preconfigured for fast installation and setup. All system settings are
fully software-configured and stored in transferable configuration files for repeated one-step system
setup.

Ribbon Communications Inc. Proprietary 14-27

 Apollo Reference Manual Accessories

14.6.1 AC/DC PS 6/8.7kW front view

The AC/DC PS 6/8.7kW front view is shown in the following figure.

AC/DC PS 6/8.7kW front view

The following table describes the AC/DC PS 6/8.7kW front view components.

AC/DC PS 6/8.7kW front component functions

Designation Component Function

AC I/P AC circuit breaker, 2P-50 A Acts as an ON/OFF switch for connecting the power system
to the AC source and protects the AC source from AC/DC
PS 6/8.7kW overload.
L1 to L6 Load DC voltage circuit Act as an ON/OFF switch for connecting loads L1 to L6 to
breakers, 1P-50A the system DC voltage bus. Protects the system from load
overcurrent.
Bat1, Bat2 Battery circuit breakers, Act as an ON/OFF switch for connecting two battery systems
1P-100 A to the DC voltage bus. Protects the system from battery
overload.
CU-19C A Controller unit Provides control, provisioning, configuration, and display for
the system.
SNMP Remote control connector, Provides SNMP communication with the CU-19C A for
interface RJ-45 (optional per order) controlling the system from remote (via a modem).
DPR 2000 or Rectifier unit (2 kW or 2.9 Provides AC to DC power conversion for the system. Up to
DPR 2900 kW) three units can be installed in a platform. The type of the unit
determines the system max. power.

Ribbon Communications Inc. Proprietary 14-28

 Apollo Reference Manual Accessories

14.6.2 AC/DC PS 6/8.7kW rear view

The AC/DC PS 6/8.7kW general rear view is shown in the following figure.

AC/DC PS 6/8.7kW general rear view

To facilitate understanding enlarged views of sections on the rear panel are provided in the following
figures.
The AC/DC PS 6/8.7kW detailed dry contact relay and sensor connections are depicted in the following
figure.

Relay dry contact and sensor connections

The AC/DC PS 6/8.7kW detailed battery and load connections are shown in the following figure.

Ribbon Communications Inc. Proprietary 14-29

 Apollo Reference Manual Accessories

Battery and load connections

The AC/DC PS 6/8.7kW AC power source connections are shown in the following figure.

AC source connections

The following table describers the AC/DC PS 6/8.7kW rear panel component functions (connections).

Ribbon Communications Inc. Proprietary 14-30

 Apollo Reference Manual Accessories

AC/DC PS 6/8.7kW rear panel component functions

Designation Component Function
TB2 Not used Not used
TB1 Terminal socket, 2-positions Connects the Bat1 temperature sensor to the system. The
sensor with an appropriate cable is supplied, by default, with
the system. It must be connected, in case backup batteries
are used.
TA Terminal socket, 2-positions Connects the Ambient temperature sensor to the system.
The sensor with an appropriate cable is supplied, by default,
with the system. If not connected, Ambient Temperature will
not affect the power supply control system.
Relay1 to Push terminal socket, Each terminal provides connection to three dry contacts
Relay6 3-positions (6 places) (relay):
 NO - Normally Open
 NC - Normally Closed
 COM - Common
The connections must be made with wires of up to 22 AWG.
Battery2 Screw terminal socket, Connects the Battery2 pack to the system DC output bus.
2-positions The connections must be made with cables of up to 25 mm2.
Battery1 Screw terminal socket, Connects the Battery1 pack to the system DC output bus.
2-positions The connections must be made with cables of up to 25 mm2.
LOAD1 to Screw terminal socket, Each terminal provides load connection to the system DC
LOAD6 2-positions (6 places) output bus. The connections must be made with cables of up
to 16 mm2.
Screw terminal socket, Connects the AC source input voltage to the system:
L, N,
3-positions  L - Line
 N - Neutral

 - Ground
The connections must be made with 3 x 10 mm2 cables.

14.7 Fiber storage accessories

Fiber spoolers and Fiber Storage Trays (FSTs) are used to store excess of various optical fibers. We
provide FSTs for 19”, ETSI, and ANSI racks.

14.7.1 FST
When optical modules are used, platforms can be supplied with an FST where a length of surplus
optical fiber is stored to enable hot module replacement without disconnecting fibers from other
modules in the platform. The FST can hold up to 48 fibers, where the fiber size is 3 m x 2 mm
(10 ft. x 0.08 in.).
The FST can be opened in two positions:
 Halfway (first click when pulling the tray out)
 Completely (to enable threading of the fibers in the tray)

Ribbon Communications Inc. Proprietary 14-31

 Apollo Reference Manual Accessories

FST top view

14.7.2 Fiber spooler

The fiber spooler is used to roll and store excess optical fibers. Depending on the spooler configuration,
several hundreds of optical fibers can be stored (each stored fiber can be max. 2.5 meters (8.1 ft. long).
The following figure shows a front view of the spooler.

Spooler front view

The spooler units are attached to the rack frame using the two anchoring panels on the two sides. Fiber
cables are wrapped in a figure-eight pattern around the four storage posts in the spooler. These posts
are large enough to accommodate a large number of fibers that can be part of a typical installation. The
following figure illustrates the depth of the fiber storage area available within the spooler.

Spooler side view

Ribbon Communications Inc. Proprietary 14-32

 Apollo Reference Manual Accessories

14.8 FMT-1U patch panel

The FMT-1U is a patch panel shelf that can host up to four FMT4F fiber connection modules. The shelf
is 1U high and can be installed in ETSI or 19" racks. In addition, the unit includes two fiber supports
(one at each side) to help neatly route of the fibers connected to the FMT4F modules.
The FMT-1U supports the following FMT4F types:
 FMT4F-10x10G-MM
 FMT4F-2x4x10G-SM
 FMT4F-2x4x10G-MM
The FMT4F modules are described in the following sections.

14.8.1 FMT4F-10x10G-MM fiber connection module

The FMT4F-10x10G-MM fiber connection module can connect up to 10 x 10GE clients of TM100
(configured as MXP100E10 muxponder), TM400, and HIO500 cards to end users. The client ports on
these cards use CPF2-SR10 transceivers with an MTP24 connector. This connector is connected by an
MTP24 to MTP24 fiber patch cord to the IN connector on the FMT4F-10x10G-MM panel. The module
converts the MTP24 interface to standard 20 x LC connectors. Each pair of LC connectors connects to
a 10 GbE (Tx and Rx) end user interface with a pair of LC to LC MM patch fibers, totaling 10 x 10 GbE.
The slim size of the FMT4F-10x10G-MM provides an elegant solution for high density installations
which require 100 Gbps to 10 x 10 Gbps connectivity. The following figure shows a general view of the
FMT4F-10x10G-MM module.

FMT4F-10x10G-MM general view

The front panel of the FMT4F-10x10G-MM is depicted in the following figure.

FMT4F-10x10G-MM front panel

Ribbon Communications Inc. Proprietary 14-33

 Apollo Reference Manual Accessories

14.8.2 FMT4F-2x4x10G-SM fiber connection module

The FMT4F-2x4x10G-SM fiber connection module connects up to 2 x 4 x 10GE clients of TM200EN/B
cards to end users. The client ports on these cards use QSFP+-LR10 transceivers with an MTP12
connector. This connector is connected by an MTP12 to MTP12 fiber patch cord to the IN 1 connector
on the FMT4F-2x4x10G-SM panel. The module converts the MTP12 interface to standard 8 x LC
connectors on the upper row of the unit. Each pair of LC connectors connects to a 10 GbE (Tx and Rx)
end user interface with a pair of LC to LC SM patch fibers. Similarly, the lower IN 2 MTP12 connector
connects to another client interface of a TM200EN/B with an MTP12 to MTP12 fiber patch cord. The
end user 10 GbE interfaces connect to the lower row of the LC connectors.
The FMT4F-2x4x10G-SM supports connection to up to 8 x 10 GbE end user interfaces. The
transceivers (LR10) and fiber types are suitable for long reach applications.
The slim size of the FMT4F-2x4x10G-SM provides an elegant solution for high density installations
which require 80 Gbps to 8 x 10 Gbps connectivity. The following figure shows a general view of the
FMT4F-2x4x10G-SM module.

FMT4F-2x4x10G-SM general view

The front panel of the FMT4F-2x4x10G-SM is shown in the following figure.

FMT4F-2x4x10G-SM front panel

14.8.3 FMT4F-2x4x10G-MM fiber connection module

The FMT4F-2x4x10G-MM fiber connection module connects up to 2 x 4 x 10GE clients of TM200EN/B
cards to end users. The FMT4F-2x4x10G-MM has very similar design, functionality and features as the
FMT4F-2x4x10G-SM. The differences are that the Multi-Mode version is used for short range
applications were the transceivers on the card client ports are QSFP+-SR and the end user fibers are
MM type. For a detailed description of the module see FMT4F-2x4x10G-SM fiber connection module.

Ribbon Communications Inc. Proprietary 14-34

 Apollo Reference Manual Accessories

14.9 Cable guiding accessories

We offer a wide range of accessories for guiding cables and fibers in rack installations.

14.9.1 Fiber and cable guide

Fiber/Cable guides are dual-purpose units that can be used for fiber and cable routing. They help to
neatly route fibers connected to the front panels of modules installed in racks into ducts on the rack
sides. The guide also helps keep the recommended bending radius of the routed fibers to prevent fiber
break or signal degradation within the fiber.
The fiber/cable guide has a significant advantage over a guide dedicated only to fibers or only to
cables, as you have the choice to route fibers and cables separately or together for equipment with
mixed optical and electrical interfaces.
Routing the fibers through fiber guides cancels the load on the optical connectors resulting from the
fibers’ weight. It also enables optimal distribution of fiber bundles according to the location of the cards
they serve, and comfortable card removal for maintenance or repair purposes.
The use of fiber/cable guides gives an organized look and feel to the system, especially in installations
with multiple fibers/cables.
We offer two types of fiber/cable guides:
 Upper fiber/cable guide - for routing fibers/cables connected to interfaces in the upper part of the
equipment
 Lower fiber/cable guide - for routing fibers/cables connected to interfaces in the lower part of the
equipment
These fiber/cable guides are available for both ETSI and 19" equipment racks and can also be adapted
for use in other racks. The 19" guides can be installed in ANSI 19" racks using a spacer adapter kit. The
ETSI guides can be installed in ANSI 23" racks using a bracket kit.

Upper fiber/cable guide

The upper fiber/cable guide is always installed above the platform and serves cards/modules installed
in the upper part of the platform.

Upper fiber/cable guide

Ribbon Communications Inc. Proprietary 14-35

 Apollo Reference Manual Accessories

The guide has two types of radius-limiting elements:

 Fixed radius limiter
 Adjustable radius limiter
For efficient fiber (or cable) routing, the radius limiters are located on both sides of the guide so that
they can handle fibers/cables entering the guide from either side. In addition, the guide has openings
that facilitate the path of fibers and cables to the required route towards the rack's cable conduits or
fiber channels.

Lower fiber/cable guide

The lower fiber/cable guide is always installed below the platform, and serves cards/modules installed
in the lower part of the platform. In general the lower and upper fiber/cable guide are similar.

Lower fiber/cable guide

The lower fiber/cable guide has two types of radius-limiting elements:

 Fixed radius limiter
 Adjustable radius limiter
For efficient fiber (or cable) routing, the radius limiters are located on both sides of the guide so that
they can handle fibers/cables entering the guide from either side. In addition, the guide has openings
that facilitate the path of fibers and cables to the required route towards the rack's cable conduits or
fiber channels. The main difference between the upper and lower fiber/cable guides is that the latter
also has a cable support that helps neatly route fibers/cables and supports their weight.
The smart design of the upper and lower fiber/cable guides enables the technical staff to maintain and
repair the required hardware (card/module) without affecting traffic on adjacent cards/modules. This is
due to the fixed and adjustable radius limiters.

Ribbon Communications Inc. Proprietary 14-36

 Apollo Reference Manual Accessories

14.9.2 Fiber bridges

Fiber bridges are used to route fiber bundles horizontally between both sides of a rack and between
equipment units. The bridge can support up to 400 x 2 mm fibers.
We offer fiber bridges for ETSI and 19” racks. They are very similar. The following figure shows the
fiber bridge for an ETSI rack.

Fiber bridge general view

14.10 External fiber duct

External fiber ducts can be added to our optical ETSI rack to expand its fiber capacity by up to 1500
fibers. The ducts can be added to either one side, or both sides simultaneously. The ducts include
internal fiber spoolers that help manage the large fiber capacity.
The dimensions of the duct are 150 mm width, 306 mm depth, and 2200 mm height. Note that adding
ducts to the rack increases its width. For example, if you add ducts on both sides, the rack width
increases by 150 x 2 = 300 mm. The following figure shows the external fiber duct.

External fiber duct

Ribbon Communications Inc. Proprietary 14-37

15 Timing and synchronization
Network synchronization is used to propagate timing information from Master NEs to Slave (remote)
NEs. The Master NE is an NE directly connected to the primary reference clock device. NEs can be
synchronized with each other in term of frequency, phase, and time.
A typical master/slave synchronization configuration is illustrated in the following figure. The propagated
timing information can be used by the Slave NE for internal purposes, and/or be provided to customer
equipment (CE) via the timing output interface.

Network synchronization model

The Apollo series supports the following methods for PRC distribution over PSN:
 SyncE, according to G.8261 and G.8264 carried over Ethernet physical links between NEs.
 IEEE 1588v2 (PTP), a packet-based method supporting master and slave modes.
Apollo synchronization filters distribute frequency and phase/time timing over an out-of-band Optical
Timing Channel (OTC) over WDM links through the bi-directional wavelength, on single fiber.

15.1 Timing and synchronization modules

Timing and synchronization in Apollo platforms is implemented through xCTM2 modules installed on
xRCP/xRCP1 cards in OPT99xx platforms, and on OSC_8T cards in OPT96xx platforms. This section
describes the timing and synchronization features built into the xCTM2 central timing modules.

15.1.1 xCTM2: central timing module

Timing and synchronization in the Apollo is implemented through xCTM2 modules installed on
xRCP/xRCP1 cards in OPT99xx platforms, and on OSC_8T cards in OPT96xx platforms. xCTM2 is
responsible for synchronization of the I/O and common cards within platform equipment connected to
timing interfaces located on xTAM/TAMIM04X/OSC cards. xCTM2 supports frequency, phase, and time
synchronization.
Redundancy is provided through the use of two xCTM2s. The network reference timing clock can be
implemented through either IEEE 1588v2 or SyncE. xCTM2 modules must be used whenever timing
synchronization is required.
xCTM2 modules support the following clock inputs and outputs:
 Clock inputs
 BITS_in (T3): E1/T1 or 2 MHz, selectable by management (including SSM handling)
 Free running (internal): Oven Controlled Crystal Oscillator (OCXO) with Stratum 3E
compliance
 Line timing: Clock recovered from any OTN/Ethernet interfaces

Ribbon Communications Inc. Proprietary 15-1

 Apollo Reference Manual Timing and synchronization

 IEEE 1588v2 recovered clocks (PTP massages) or external inputs

 Clock outputs:
 BITS_out (T4): E1/T1 or 2 MHz, selectable by management (including SSM handling)
 System clock (to all I/O slots via backplane)
 IEEE 1588v2 Master PTP massages or external outputs (1PPS, ToD, Clock)

15.1.2 xCTM2 block diagram

The xCTM2 includes two blocks.
 The PLL block is responsible for frequency synchronization. The PLL block can work with several
timing reference inputs (T3, Sync-E, PTP, Ext_1588); the user defines the timing reference inputs.
The PLL block locks on the selected timing reference inputs and distributes this timing reference
within the platform as a system clock (MF or Tx_Clk). The PLL block chooses the best available
timing reference, performs a basic cleaning (jitter, wander), and then distributes the clock
(frequency) among all cards in the shelf (T0 clock). The best timing reference inputs for the
current network configuration take into account criteria such as reference availability, reference
quality level, and user preferences.
 The PTP block is responsible for running PTP (1588v2) logic, supporting frequency, phase, and
time synchronization. The PTP block’s frequency output can be one of the timing reference inputs
for the PLL block. The PTP block includes both software and hardware elements.
The following figure illustrates the logical architecture of the xCTM2 module.

xCTM2 architecture

Ribbon Communications Inc. Proprietary 15-2

 Apollo Reference Manual Timing and synchronization

The main xCTM2 components include:

 Timing over Packet (ToP) component: Used in PTP Master, Slave, or Boundary modes.
Incorporates IEEE 1588v2 timestamp generation and termination engine as well as clock
reconstruction functionality from:
 PTP massages
 Mate xCTM2 1PPS, ToD
 External 1PPS, ToD, 1588 clocks
 Phase Lock Loop (PLL) component: Provides a common system clock synchronized to one of the
following sources:
 BITS_in, E1/T1 or 2 MHz
 External 1588 clock
 Free running (internal) with results from OCXO
 ToP recovered clock
 Line card reference clock
 Mate xCTM2 module
 Dual E1/T1 Framer/Line Interface Unit (LIU) component: Provides channelized E1/T1 traffic
interface I/O (T3/T4 respectively). Monitors incoming E1/T1 signals for alarms, errors, and clock
quality.
 OCXO component: Serves as a free running Stratum 3E clock for ToP and SyncE components.

15.1.3 Synchronization modes

xCTM2 modules support three synchronization modes, (BITS, SyncE, and IEEE 1588v2), integrating
smoothly within networks configured to work with any or all of these modes, and thereby enabling the
broadest range of applications. Each of these modes is described in this section.

Synchronous Ethernet
xCTM2 support for SyncE

In SyncE modes, the xCTM2 receives a PRC reference timing signal through an external clock port.
The clock signal is extracted and processed by an internal synchronization function that includes jitter
filtering before adding timing to the Ethernet bit stream. SyncE distributes frequency synchronization
only. These modes cannot be used for phase or ToD synchronization.
As illustrated in the preceding figure, there may be a number of platforms involved in reference timing
signal distribution, with each platform capable of recovering synchronization line timing from the
incoming bit stream. SyncE clock recovery performance is independent of network load.

Ribbon Communications Inc. Proprietary 15-3

 Apollo Reference Manual Timing and synchronization

To avoid timing loops, each NE should automatically send a Do Not Use (DNU) message back to the
direct source NE from which it receives a timing signal. This ensures that the source NEs do not receive
back their own timing signals from the current NE.

PTP (1588v2)
Precision Time Protocol (PTP) is based on the IEEE1588v2 standard. This standard defines a
packet-based method for frequency, phase, and time synchronization via Packet Switched Networks
(PSN). PTP is a Client-Server hierarchy protocol; it enables client synchronization on the server’s clock
domain by exchanging special packets (PTP packets) between client and server.
The PTP server is referred to as the PTP Master clock. The PTP client is referred to as the PTP Slave
clock. The Master clock is connected to a clock source (freq, phase, time) such as a GPS receiver and
uses PTP packets to distribute the timing information towards the Slave clock. The Slave clock uses
these PTP packets to recover timing information (freq, phase, time) that can then be provided to a
directly-connected CE, such as an LTE base station. This master/slave configuration is illustrated in the
following figure.

PTP network synchronization

15.1.4 Synchronization interfaces

xCTM2 clock source inputs may come from any of the following:
 BITS_in (T3): Connected to the xCTM2 as the clock input. A BITS_in signal is connected to both
xCTM2 cards. BITS_in signals may be any of the following:
 E1 (G.704, G.704 with CRC, or unframed)
 T1 (T1-SF, T1-ESF)
 2.048 MHz
The E1/T1 (2 Mbps) signal may carry reference timing information via SSM in addition to the
payload. Users may optionally override the SSM value, a valuable ability in case the E1/T1 traffic
interface has received a signal with no SSM value. E1/T1 alarms that are monitored and reported
include loss of signal (LOS), loss of frame (LOF, only relevant if configured for framed signal), and
alarm indication signal (AIS).

NOTE: The 2.048 MHz signal does not indicate the quality level of the source generating
the timing information.

 ToP recovered clock: Used in ToP slave mode, the device locks to PTP timing packets and
implements IEEE 1588v2 slave functions.
 External 1588_In: External 1588v2 inputs (such as GPS) for reference clock, 1PPS, ToD.

Ribbon Communications Inc. Proprietary 15-4

 Apollo Reference Manual Timing and synchronization

 Free running: OCXO used as free running clock, compliant with Stratum 3E. Devices revert to
free-run mode after a power-on or device reset.
 Line timing: I/O cards can recover the Ethernet clock signals (respectively) that were received
and pass them on as reference clock signals to the xCTM2. These signals can then be used to
synchronize all outgoing Ethernet/OTN interfaces with the same selected reference clocks.
 Mate xCTM2: Each xCTM2 provides its mate with a reference clock.
 BITS_out (T4): Optional, used to synchronize other equipment. When working with redundant
xCTM2 modules, BITS output is only enabled for the active xCTM2.
 1588_Out: xCTM2 has 1588v2 outputs (reference clock, 1PPS(1Hz), ToD(UART)).
 The internal 1PPS pulse and ToD is used for RTC register synchronization on I/O cards with RTC
registers on xCTM2. RTC is used for timestamping PTP packets when a packet is either received
from or transmitted to the network. The PTP packet timestamps are used for clock, phase, and
time recovery by the PTP block. 1588_Out signals can drive external 1588 interface (Clock, 1PPS,
ToD) for monitoring or external equipment connectivity.
 T0 and MF: xCTM2 drives T0 (125MHz) and Multi Frame (MF) (8KHz) to synchronize I/O card
transmission clocks.
 PTP Massage Out: ToP module in xCTM2 generates PTP Massages in 1588v2 Master mode.
Holdover mode refers to the operating condition of a clock that has lost its reference and is controlling
the output signal using previously acquired data. The holdover value is usually an average value
calculated over some period of time to minimize the impact of short term variations in the reference
frequency that may occur during normal operation.
The xCTM2 module is a universal component that is used in most of the Apollo platforms. Obviously,
the xCTM2 works together with different types of cards, depending on the specific platform type and
configuration.

15.1.5 Reference clocks

xCTM2 modules can utilize a range of timing clock sources. This section describes the logical steps of
reference clock selection.
The following factors are taken into consideration when selecting a timing source.
 Clock presence
 Quality Level (QL)
 External/management command
 User priority
As a general rule, the best quality level timing source available is the one selected (QL mode). QL
settings are received via SSM, ESMC, or explicitly assigned by the user. When multiple timing sources
are of the same quality, predefined priority factors are added to the decision process. Ethernet networks
synchronized with SyncE check the quality value of each timing source distributed along the network
via the ESMC. If the quality of the active reference is degraded, or if an alternate reference offers a
better synchronization quality, a reference switch is triggered.
CLI commands may override the automatic selection process. It is possible to configure a working
mode that ignores the quality of the timing sources or does not support ESMC/SSM capabilities. In this
case, the timing source with the highest priority that is not in a failed state is selected (priority mode).

Ribbon Communications Inc. Proprietary 15-5

 Apollo Reference Manual Timing and synchronization

Timing sources
Users may configure multiple reference clock sources for the xCTM2 (out of a maximum of 32 possible
clocks) as input timing sources. These reference clocks are in addition to the BITS_in, 1588v2, and free
running clock inputs.
Priority values are assigned to an NE's synchronization sources, with preferred sources assigned a
higher priority level.

ESMC
Clock quality level indications are transmitted as part of a protocol running over SyncE links. Two types
of messages are defined for this protocol:
 A continuous stream of 1s sent as a background (heartbeat) message, providing a continuous
indication of clock quality level.
 An event message indicating a new SSM quality level. When a sync source signal recovers from a
failure condition, the source is considered available for selection after the signal fail indicator has
been cleared at a minimum for the time defined by WTR (5 min to 12 min).
To protect against possible failure, a lack of messages is considered a failure condition. The SSM value
is set to DNU if no SSM messages are received after a 5 sec period.

15.1.6 Built In Test (BIT)

Built in tests are used to constantly monitor xCTM2 operation. Two types of BITs are defined:
 Power Up (PU) BIT, during RCP power up or cold reset.
 Periodic (PER) BIT, on a regular periodic basis.
BIT failure detection triggers an immediate switchover to the protection xCTM2.

15.1.7 High availability protection

Systems configured with redundant xCTM2 modules support a high availability level of protection
through a 1+1 protection switching scheme. Each xCTM2 provides a single system clock signal
(125 MHz) to all I/O cards. The I/O cards monitor the clock signal from both xCTM2s. If the clock activity
check within an I/O card fails, it immediately switches over to the protection xCTM2 and informs the
active xRCP/xRCP1.

NOTE: For PTP synchronization, xCTM2 cards operate in 1:1 mode since only one
xCTM2 participates in the protocol sessions.

Ribbon Communications Inc. Proprietary 15-6

16 Protection and restoration mechanisms
Protection is of the utmost importance in the high-capacity traffic transmitted through WDM systems.
Apollo's high-level reliability is achieved through a comprehensive set of protection schemes
implemented at different network levels. Protection schemes are provided per physical component as
well as at Layer 0, Layer 1, and Layer 2 network levels.
Equipment redundancy is available for all units (common units, traffic units, I/O cards, fabrics, and
network connections). Automatic protection switching is initiated by a robust internal built-in test (BIT)
diagnostic system. Layer 0 protection includes optical line and WSS ROADM-based protection
mechanisms.
Layer 1 protection mechanisms include various forms of line protection, SNC-N, DNI, and DRI
protection schemes, protection based on the AoC card, and a complete range of OCH protection
mechanisms.
PB protection mechanisms include RSTP and ERP protection, as well as CCN, LLCF, and selective
FDB flushing, ensuring enhanced performance in a dynamic network setting. MPLS protection
mechanisms include 1:1 linear protection, LAG, and PW redundancy. Apollo also offers essential ASON
GMPLS-based restoration mechanisms.
Network operators can choose a combination of protection schemes optimized for their specific network
configuration and functionality. For example, consider a typical metro network that mixes EPL services
at the access layer with shared PB network at the core. This network design enables operators to offer
the most cost-effective access technology, while the shared PB networks at the edge and metro-core
offer the benefits of shared infrastructure and MP2MP services. This very common network
configuration may utilize a mixture of L2 RSTP/MSTP and SNCP protection schemes. Some of the
Apollo protection mechanisms are introduced in this section.

16.1 OMSP 1:1 protection

Apollo features a fiber protection scheme based on either signal power degradation or LOS, providing
line protection for P2P optical links with minimal insertion loss (less than 3 dB). In the event of a fiber
cut, the Optical Multiplexer Section Protection (OMSP) optical switch automatically switches traffic to
the protection fiber in under 50 msec. Protection can be configured to revert automatically to the main
fiber upon repair. OMSP protection is generally used for fiber spanning in linear topologies. A pilot tone
monitors the protection fiber. We offer the OMSP card for this protection scheme.
This low-cost approach protects all DWDM channels simultaneously without hardware redundancy. The
OMSP operates independently of data rates, protocols, or number of channels, and provides protection
for future upgrades when additional DWDM channels are added to the network.

OMSP protection

Ribbon Communications Inc. Proprietary 16-1

 Apollo Reference Manual Protection and restoration mechanisms

16.2 OLP 1+1 protection

Apollo's optical line protection (OLP) is a 1+1 protection module based on signal power degradation or
loss of signal (LOS) [<50msec]. OLP cards can be mated to service cards for signal failure (SF)
protection [<100msec]. OLP 1+1 protection can be configured to revert automatically to the main fiber
upon repair. OLP is usually employed in three general protection scenarios:
 Fiber span(s) protection
 Service card protection
 Client side protection

Fiber spans(s) protection

The OLP_2S card can be used to provide fiber span(s) protection between two Network sites. In this
scenario, the OLP directs traffic between Site-1 and Site-2 into 2 different fiber spans, thus enabling
fiber protection between the sites.
The OLP card at the span input point splits incoming traffic into two different paths, through a 1x2
splitter, while a 1x2 optical switch at the span output point selects the working path. The OLP switches
from one path to another when an optical LOS is detected.
You can configure which fiber pair (for example, either Fiber-A or Fiber-B in the following figure) should
be the 'main' pair by default. The protection paths may include several fiber spans and in-line amplifier
sites. OLP is typically used for fiber protection in situations when OMSP cannot be used, such as when
you are working with ILAs or RAMAN amplifiers.

Ribbon Communications Inc. Proprietary 16-2

 Apollo Reference Manual Protection and restoration mechanisms

Service card protection

In this scenario, the OLP is connected to the service card line port, at both ends of the network. The
OLP directs the relevant Channel in two non-disjoints paths over the entire Network, thus enable
Service card protection.
Signal Failure (SF) vs. optical LOS
OLP switching from one path to another is usually based on detection of optical LOS. However in
colorless coherent networks, several channels (the designated channel plus others) may be directed
towards the transceiver input. As a result, LOS of the designated channel may still not trigger an optical
LOS signal and the OLP may not switch.
To overcome this problem, Apollo takes advantage of service card capabilities to detect the signal
failure. When the service card detects that the signal has been lost, the service card sends a signal
failure message to the OLP through the backplane IOP, and then the OLP switches. Error indicators in
the service card are based either on complete signal failures (SF), or on a degradation in OTN data
quality (DQ), from an OTUk port in the adjacent service card. This feature can be configured for service
cards and OLP cards in adjacent slots, with SF monitoring enabled and the fiber connectivity defined
accordingly.

NOTES:
 When configuring service card protection on signal failure for single slot cards, the OLP and
service card must be placed in associated protection slot pairs.
 In the OPT9603, service card protection on signal failure is not supported for double slot
cards.

Oscillation prevention
When a fault is initially detected, the OLP immediately initiates a protection switch. However, to avoid
oscillations, the next switch is allowed only after one minute, a third switch is allowed only after two
minutes, and so on. Each switching incident increases the waiting time, up to a maximum of 64
minutes. When all faults are cleared, with a clean stabilization time of 7 seconds, the waiting time is
also reset.

Ribbon Communications Inc. Proprietary 16-3

 Apollo Reference Manual Protection and restoration mechanisms

Client side protection

OLP card protection can be configured at the client side, where the OLP card is located between the
client's router and the client-side ports of the service cards that can even reside on different platforms.
The OLP cards select the line path to be used for that client. This configuration, usually working at
1310 nm wavelength, provides total 1+1 redundancy protection for the line and service cards from
network and/or equipment failures.
The following figure illustrates a typical card configuration. Note that this protection can be configured
with exclusively Apollo equipment, and it is also appropriate for networks that include both our own and
3rd party regions.

16.3 OCH port protection

Apollo provides port protection very similar to its path protection mechanism. By using double
transponder/combiner cards, a dual-traffic path goes around the ring and is received by both the main
and the protection transponder/combiner. Both perform continuous PM to ensure channel integrity.
If PM on the main transponder/combiner does not indicate a problem, a message is sent through the
backplane to the protection transponder/combiner for it to shut down its laser to the client, thereby
ensuring transmission to the client from only one transponder/combiner (the main). Protection switching
to the protection transponder/combiner occurs automatically when a failure is detected by the main
transponder/combiner.
The protected channels in the following figure are user selected.

OCH 1+1 port protection

Ribbon Communications Inc. Proprietary 16-4

 Apollo Reference Manual Protection and restoration mechanisms

OCH port protection is currently the most popular optical protection method for the optical layer. The
mechanism transports each optical channel in two directions, clockwise and counterclockwise. The
shortest path is defined as the main or working channel; the longer path as the protection channel.
The main benefit of OCH port protection is its ability to separately choose the shortest path as the
working path for each client port. There are no dedicated working and protection fibers. Each fiber
carries traffic with both working and protection signals in a single direction.
The OCH 1+1 port protection scheme provides separate protection for each client port. For
SDH/SONET, GbE, and 10G, protection switching is based on PM parameters. Switching criteria can
be Loss of Signal (LOS), Loss of Frame (LOF), or Degraded Signal (SD). The switch-to-protection
mode is automatic when a malfunction is detected in a single channel. This is very convenient as users
can choose the client ports to be protected, as well as choosing the main or protection paths.
Switch-to-protection time in the OCH 1+1 port protection scheme is less than 50 msec.

Usage guidelines
 Multi-mode transceivers cannot be used to configure OCH 1+1 port protection, because the signal
intensity could be below the sensitivity lower limit of the transponder.
 In platforms from the OPT96xx family, port protection must be configured between cards in
adjacent slots (#N and #N+2), assigning matching port numbers on the two cards.
 In platforms from the OPT99xx family, port protection can be configured between any two ports on
any two cards in any two slots. The slots do not have to be adjacent, and the port numbers do not
have to be identical.

16.4 SNC-N protection

The SNC-N point serves as a ‘bridge/switch’ point within a trail. In the transmit direction, the trail is split
into two independent routes (1+1 bridging). In the receive direction, a selection is made between these
two incoming routes (switching), based on signal quality criteria.
Protection based on ODU0/1/2/3/4/Flex faults is provided in less than 50 msec, and can be either
revertive or non-revertive. The traffic protection source and sink points are SNC-N points. Client traffic
protection may also employ SNC-N points (on the egress and ingress sides).

SNC-N points

SNC-N points may exist at the trail endpoints and also within the network. SNC-N protection is relevant
for all Apollo platforms, configured with or without matrix cards, since SNC-N points exist in both service
and matrix cards.

Ribbon Communications Inc. Proprietary 16-5

 Apollo Reference Manual Protection and restoration mechanisms

16.5 Combination network traffic and equipment

protection
Equipment protection protects against card/module failures. The purpose of equipment protection is to
allow service continuation in the event of failure or extraction of the service source/sink card or
module/transceiver. By nature, equipment protection involves two adjacent cards protecting each other.
Port protection is activated on a per-service basis, using an external splitter/coupler to connect two
Apollo client-side ports (one on each Apollo card) to the client’s equipment. A pair of cards assigned to
protect at least one service, as described here, is considered a protection card pair. Note that on the
same protection card pair, some services may have port protection while other services may be
unprotected or protected with other types of protection, such as client traffic protection. The following
figure illustrates a combination of two types of protection in the network: SNC-N and client protection
with external splitters/couplers.

Combined network traffic (SNC-N) and equipment protection

16.6 Interoperability with SDH/SONET

equipment running MSP 1+1 protection
In SDH/SONET networks, both cards are active and sending signals. With MSP 1+1 protection, the
ADM modules are connected to two protected interfaces (1+1). Note that protection is unidirectional
and non-revertive, based on LoS indication only.

Combined network traffic (SNC-N) and equipment protection

Ribbon Communications Inc. Proprietary 16-6

 Apollo Reference Manual Protection and restoration mechanisms

16.7 ODU DNI and DRI protection

The universal fabric can be used to provide multi-ring connectivity on a single node (DRI) or dual node
(DNI) basis. DNI and DRI protection schemes provide robust protection in under 50 msec that keeps
traffic moving without interruption even in the face of two fiber cuts (one in each ring).
Signals from both sides (East/West) of one ring are transmitted to both sides (East/West) of the second
ring. Based on ODU signal PM, both sides decide which signal to process.
The following figure displays a simple DRI configuration, with a single node serving as the connection
point between two rings.

DRI protection at the universal fabric

The following figure displays a simple DNI configuration, with two independent NEs serving as the
connection points between two rings. Each NE receives traffic either from other NEs in the same ring or
from NEs in the other ring. Based on SNC-N at the ODU level, NEs decide which signal to process.

Ribbon Communications Inc. Proprietary 16-7

 Apollo Reference Manual Protection and restoration mechanisms

DNI protection at the universal fabric

ODU DNI and DRI protection is relevant for all Apollo platforms, configured with or without matrix cards.

Ribbon Communications Inc. Proprietary 16-8

 Apollo Reference Manual Protection and restoration mechanisms

16.8 Y-protection for network traffic on

transponders
Network traffic protection protects against network failures within the trail which carries the traffic,
working with the assumption that the protected trail is conveyed over two independent network
paths/routes. In network traffic protection, the trail is bridged to different paths at the traffic protection
source point. At the traffic protection sink point, the traffic protection mechanism chooses one of the
incoming paths. Protection switching criteria are based on incoming signal quality. Switch-to-protection
time is less than 50 msec.
On its own, network traffic protection provides protection from the point the service/trail leaves the
source card to the point it enters the sink card. Network traffic protection may also be combined with
other protection types described in the following sections.
The 10G service cards can operate in line (facility) protection mode, with a single 10 Gbps client
connected to two lines. This mode protects the network from fiber cuts.
In line protection mode, the signal is transmitted and received on both lines. Only one of the signals
received by the card is processed and forwarded to the client side. The choice of which signal to
process is based on PM parameters for the OTU2 signal.

Y-protection example

Ribbon Communications Inc. Proprietary 16-9

 Apollo Reference Manual Protection and restoration mechanisms

16.9 AoC10/AoC10B ring protection schemes

The AoC can be used to create an OTU2 ring, multiplexing GbE, SAN, TDM, and video client
interfaces. Protection is per service at the SNC/N ODU0 level. Protection can be configured as either
1+1 protection or unprotected. Card protection can also be provided, through use of a splitter-coupler. A
mixture of network and card protection is illustrated in the following figure.

AoC protection mixture

When used in ring applications the AoC supports optical DRI protection, illustrated in the following
figure. (Note that inter-ring traffic is through OTU1 client ports.)

Ribbon Communications Inc. Proprietary 16-10

 Apollo Reference Manual Protection and restoration mechanisms

AoC: optical DRI protection

16.10 WSS ROADM protection

ROADM configurations facilitate implementation of advanced protection schemes such as N+1 Path
dynamic restoration and protection, 1+1 Forever protection and restoration in under-50 msec, and
optical Dual Node Interface/Dual Ring Interface (DNI/DRI). This unique all-optical protection can handle
and overcome multiple fiber cuts - ideal for mesh-based networks and topologies.
Apollo provides preplanned fixed protection against multiple fiber cuts or an NE failure along the main
and protection routes by using WSS switching capabilities with a single transponder/combiner card.
Additional protection against transponder/combiner failure requires a combination of both OCH 1+1 and
WSS restoration.
When configuring WSS ROADM restoration, the client transponder/combiner connects via optical
splitter to a ROADM WSS array with up to nine routing possibilities in the WSS add/drop node.
Protection route(s) can be active at all times, so reducing the total restoration time as switching to
protection only requires an update of the relevant ROADM port in the drop site.

N+1 protection
The following illustrates a typical example of N+1 optical protection based on the WSS ROADM. This
configuration includes one main route and two protection routes, segments of which can be used for
restoration. For each working primary route, up to 15 secondary routes can be configured. All the routes
are set automatically through the management system. If the primary working route fails, the system
switches automatically to the Secondary 1 route. If the Secondary 1 route also fails, the Secondary 2
route is automatically activated. Protection routes can be kept active and dedicated to shorten
restoration time.

Ribbon Communications Inc. Proprietary 16-11

 Apollo Reference Manual Protection and restoration mechanisms

WSS ROADM N+1 protection

1+1 forever protection

Optical 1+1 Forever protection is similar to OCH 1+1 protection with the added advantage of providing
protection for more than one fiber cut. Optical 1+1 Forever protection is an extension of the traditional
OCH 1+1 protection, where failure in the main or protection path results in sub-50 msec switching by
the transponders. After this switching the failed path(s) are restored, returning the network to full
OCH 1+1 protection. This enables continuing OCH 1+1 protection against multiple fiber cuts.

WSS ROADM 1+1 Forever

Optical DRI
Optical DRI protection uses a single NE to bridge two rings. In a typical example of optical DRI
protection, a single connection point is used to close two rings, providing protection for scenarios that
include two fiber cuts. Optical DRI trails are created automatically by LightSOFT.

Ribbon Communications Inc. Proprietary 16-12

 Apollo Reference Manual Protection and restoration mechanisms

Optical DRI classic protection model

Traditional protection schemes rely upon configuration of two paths, main and protection. Traffic is
simply switched from the main path to the protection path if there are any (one or more) fiber cuts in the
main path. Optical DRI topologies improve upon the traditional model by protecting against fiber cuts in
both the main and protection paths.
Optical DRI configures additional links between the main and protection paths to provide multiple
alternate route possibilities between the main and protection paths. This is illustrated in the following
figure.

Optical DRI classic protection model

The preceding figure portrays two endpoints linked by main and protection paths. Two links are
configured between the two paths, represented by the X-shape link topology in the center of the figure.
The first fiber cut on the main path (labeled A), triggers a switch at both endpoints from the main path to
the protection path. A second fiber cut on the protection path (labeled B), triggers a switch at the
appropriate points from the protection path back to the main path. After each fiber cut, the optical
equipment used at the DRI-configured nodes at either end of the DRI links must also switch their
internal Rx/Tx settings accordingly.

Optical DNI enhanced protection model

Classic optical DNI configurations require two fiber links between the main and protection paths. Under
certain circumstances, such as complex or distant topologies, it may be difficult to ensure two fiber
connections between the paths. Therefore, we have designed an enhanced optical DNI configuration
that can be implemented with a single fiber link between the two paths. This is illustrated in the
following figure.

Optical DNI enhanced protection model

Ribbon Communications Inc. Proprietary 16-13

 Apollo Reference Manual Protection and restoration mechanisms

With enhanced optical DNI, a single BD link is configured between the two paths. The OCH trail is
defined as asymmetrical, using a different channel in each direction. This prevents signal overlapping
over the link connecting the two paths.
Using WSS for restoration is exceptionally cost effective for 40G and 100G wavelengths as no OEO
cross connection is necessary. Routing is completed optically automatically by the WSS ROADM
according to the wavelength provisioning via LightSOFT.

16.11 ASON, WSON, and SSON GMPLS-based

restoration
Transmission network solutions underwent a tremendous evolution in technology over the years. In
addition to dramatically increasing the bandwidth and reach of the network, there has been significant
progress automating service provisioning and management. The intelligent Generalized Multiprotocol
Label Switching (GMPLS) control plane enhances networks by adding restoration to the sub-50 msec
protection schemes and automated service provisioning. The Automatic Switched-Transport Network
(ASTN) architecture boosts network capabilities, thereby further reducing CAPEX and OPEX.
Apollo platforms offer Automatic Switched Optical Network (ASON) restoration using GMPLS
technology for Optical Transport Network (OTN) trails with dynamic service provisioning, as well as
Wavelength Switched Optical Network (WSON) and Spectrum Switched Optical Networks (SSON)
restoration for OCH trails.
Our innovative networking framework enables carriers to reduce CAPEX and OPEX by efficiently
planning and operating intelligent networks using ASON, WSON, and SSON capabilities, based on NG
transmission technology and a GMPLS control plane. ASON, WSON, and SSON offer the ability to
control and manage transmission networks more flexibly, conveniently, and effectively. For example,
the WSON/SSON control plane considers the optical values of alternative restoration paths, based on
intelligent analysis of standard metrics such as OSNR, length, latency, cost, and number of hops.
ASON decisions are based on similar sets of metrics.
The distributed dynamic routing capability enables rapid cost-effective creation of new nodes and
increases in bandwidth, without the extensive offline operations usually required.
Apollo's ASTN architecture, compliant with ITU-T G.8080, is composed of three main layers or planes:
 Transport plane: Represents the switching equipment. The transport plane carries the client
payload over a trail that consists of the connection endpoints plus any number of intermediate
NEs along the trail.
 Control plane: Represents the processing engines within each Apollo RCP. The control plane
software inter-operates with the transport plane via a connection control interface (CCI). Control
plane processors transmit management information over a dedicated DCN (inbound or outbound),
connected through internal network-to-network interfaces (I-NNIs).
 Management plane: Represents the interface with client equipment. The management plane is
implemented over the UNI where the connections that can be configured over other domains
(such as other carriers, other layers, or third party equipment) are expanded. A dedicated
management-to-network interface (MNI) is used between the control plane and the NMS.
Key components of the Apollo management and control suite include automatic topology discovery,
resource dissemination, point-and-click connection provisioning, user-initiated automatic setup, E2E
performance management, and path protection and restoration across an OTN network.

Ribbon Communications Inc. Proprietary 16-14

 Apollo Reference Manual Protection and restoration mechanisms

Network management via the control plane, especially when combined with advances in DWDM
hardware such as ODU-XC fabric for OTN switching or multi-degree ROADMs with colorless,
directionless, and contentionless (CDC) switching for OTN transport (or both), give operators the
following benefits:
 Network availability: Availability is improved, as the network is tolerant of multiple failures, with
the ability to reroute wavelengths without complex re-planning exercises and service calls.
 Network optimization: Network topology is modified over a period of time, as service
requirements change. The optical-aware WSON/SSON control plane helps to optimize and reduce
or eliminate network fragmentation.
 Wavelength on demand: Time to market is significantly improved with rapid service setup. There
is no need for complicated network planning; a simplified GUI as well as script-oriented (CLI)
User-Network Interface (UNI) allows users to dynamically demand wavelength services across
DWDM networks.
 Cost savings: With this intelligent control plane, operators can now efficiently use the benefits of
switching components such as ODU-XC fabric or ROADMs, and reduce the number of ODUs or
wavelengths and I/O service cards needed in the network. Affecting the lowest layer in the
network, this directly translates to savings not just in DWDM equipment, but also in ports at
higher-layer equipment (cross-connects and routers), resulting in tremendous CapEx savings for
operators.
 Value-added services: The control plane provides dynamic rerouting capabilities, allowing
service providers to offer services with new SLA levels in addition to their present modes of
operations.
Our platforms provide a variety of bandwidth-efficient protection and restoration schemes, while
supporting ring, mesh, and point-to-point network topologies. Recovery modes include a range of
protection mechanisms and mesh restoration modes. ASON/WSON/SSON capabilities offer new types
of restoration schemes, increasing network survivability with, for example, optical 1++ protection for
very high CoS services, and optical 1+1 and 1+R protection for low CoS services.
Our platforms offer control plane architecture, capable of offering intelligent services in mesh transport
networks over colorless, directionless, and contentionless configurations. This is achieved by adding a
GMPLS control plane that enhances network functionality by adding restoration to the sub-50 msec
protection schemes for multiple failure (optical 1++ services) and automated service provisioning. It also
adds other capabilities that contribute to reduced CAPEX and OPEX. The Apollo control plane
architecture, protocols, and functionalities are described in this section.
The ASON/WSON/SSON family solutions are based on the "Add-On" concept, adding unique
capabilities to existing and new networks. Expandable and scalable, the inter-compatible product line
supports seamless integration of NEs with dynamic E2E WSON/SSON-based applications.

Ribbon Communications Inc. Proprietary 16-15

 Apollo Reference Manual Protection and restoration mechanisms

16.11.1 Apollo optical control plane architecture

The need for intelligent optical networking in carrier networks triggered an ongoing effort by leading
standardization bodies, including the ITU-T, IETF, and OIF, towards a unified control plane architecture.
By adopting proven protocols and approaches, a unified architecture standard would lead to
development of a new generation of transmission networks that enable fast provisioning and restoration
along multiple carrier domains using infrastructure from multiple vendors.
The ITU-T focuses on the switched transport control plane, developing the ASTN umbrella of
specifications. The set of ASTN standards includes WSON architecture, as well as multiple generic and
specific standards addressing issues such as call connection management (signaling), discovery and
link management, routing, and others. WSON adds a new facet to the complex ASON/GMPLS domain,
introducing the colors or wavelength associated with each service and taking into account the physical
optical impairments that were ignored/neglected in the OTN layer.
Apollo implements ASON and WSON-compliant network architecture (ITU-T G.8080). The following
figure illustrates a high-level view of the ASON/WSON architecture, composed of three layers or
planes:
 Transport plane
 Control plane
 Management plane

ASON/WSON architecture

The IETF has defined the well-known GMPLS architecture and protocols, extending MPLS for
circuit-switching and other non-IP-based systems. GMPLS protocols include signaling protocols
(RSVP-TE), routing protocols (OSPF-TE), and others.
The GMPLS protocols enable advanced switching platforms such as Apollo to add “intelligence” by
integrating a control plane.
The OIF focuses on integration and interoperability issues by defining the User to Network Interface
(UNI) and the External Network to Network Interface (E-NNI). These standards cover the gaps
between ASON, WSON and GMPLS architectures, enabling a smoother integration of carrier networks.

Ribbon Communications Inc. Proprietary 16-16

 Apollo Reference Manual Protection and restoration mechanisms

Control plane interfaces

16.11.1.1 Transport plane

The transport plane represents the switching equipment. This carries the client payload between
endpoints of a connection (trail) over any number of NEs. The transport plane is responsible for
transporting the services, including switching and multiplexing, fault detection, and restoration. The
transport plane is implemented through the assembly of intelligent components and subsystems that
make up switching elements and line systems. The transport plane also includes gateways for service
adaptation.
Apollo supports ASON functionality through three different platforms, providing a choice of ODU-XC
fabric sizes (1T, 5.6T, or 16T) with line rates ranging from 10G up to 200G per channel.

Network configuration offering ASON restoration options

Ribbon Communications Inc. Proprietary 16-17

 Apollo Reference Manual Protection and restoration mechanisms

Apollo supports WSON functionality through built-in DWDM layers based on state-of-the-art ROADM
modules with colorless, directionless, contentionless, and gridless (Flex-Grid) configurations (CDCF).
 Directionless switching enables the ROADM to automatically select the direction of the add/drop
wavelength without having to physically visit the site and connect the fiber to the required port.
 Colorless switching enables remote wavelength retuning of add/drop wavelengths, again, without
the need visit the site. With this architecture, an add/drop port can be assigned to any wavelength
and coupled to any direction(s) in a fully flexible fashion. The colorless feature is implemented
utilizing the TFA card, drop configured for direct colorless operation.
 Contentionless switching means that two or more services can be transmitted from the site in
different directions using the same wavelength channel.
 Gridless/flexible grid network, as defined in the G.694.1 WDM wavelength grid specification. This
standard divides the wavelengths available in the C-band spectrum into 'slices', with a granularity
of 12.5GHz. Flex-Grid's finer granularity enables optimal usage of the available bandwidth.
Groups of 12.5GHz spacing can be combined into whatever size is required, including Super
Channel spectral widths of N x 12.5GHz, accommodating any combination of optical carriers,
modulations, and data rates.
WDM cards can be added in any of Apollo slots in the same cage with or without the ODU-XC fabric
and service cards. 10G, 40G, and 100G channels are supported with a choice of 100 GHz spacing
(48 channels) and 50 GHz spacing (96 channels) or flexible grid network design. Both mixed and pure
coherent networks are available.
The Apollo transport plane supports standard-compliant Automatic Discovery and DCN, critical for the
implementation of ASON and WSON architecture.

16.11.1.2 Control plane features

The control plane enables mesh restoration and intelligent optical networking. The control plane
consists of individual processors (control plane instances) running control plane software and
interconnected via communication channels to create an overlay plane that controls the switching
elements. The control plane is mainly responsible for creating the original connections as well as
restoration in response to failed connections. The control plane software interoperates with the
transport place via a CCI (Connection Control Interface), and control plane processors are
interconnected with an I-NNI interface over a dedicated DCN (in- or outbound). A signaling
communication network (SCN) transmits the control plane instances between all NEs and the
management system.
The control plane in the Apollo is integrated within the RCP controller card. Each Apollo shelf may be
equipped with two RCP cards for 1:1 protection, avoiding a SPoF.

Path computation
The protection and restoration capabilities of links and the Shared Risk Link Groups (SRLG) associated
with links can also be advertised by the routing protocols. Based on the Physical layer, SRLG
constrains the information and capabilities provided by the GMPLS routing and signaling protocols. The
path computation algorithm CSPF (Constrained Shortest Path First) can select disjointed paths based
on link, node, or SRLG diversity.

Enhanced WSON restoration

The WSON control plane considers the optical values of alternative restoration paths, based on
intelligent analysis of standard metrics such as OSNR, length, latency, cost, and number of hops.
WSON restoration uses LightPULSE data to calculate an optically validated restoration path. OSNR
values at the endpoints are crucial to ensure that restored services will actually be able to maintain the
highest SLA.

Ribbon Communications Inc. Proprietary 16-18

 Apollo Reference Manual Protection and restoration mechanisms

One of the control plane objectives is to reuse the main-LSP resources for the restoration-LSP where
possible. When working with Flex-grid, there might be scenarios where only part of the resources can
be reused.

Enhanced optical path finder

LightSOFT PathFinder enables end-to-end route selection of an optical trail. PathFinder finds a trail
candidate using traditional metrics (distance, cost, etc.) or 'OSNR weight' criterion. PathFinder uses
LightPULSE data to obtain these metric values and calculate the expected OSNR before provisioning,
alerting the network operator if the OSNR is under the transceiver threshold. Once PathFinder suggests
a trail path, network operators can decide whether to accept the proposed trail or recalculate it.

Set maximum to restoration

A user can restrict the maximum trail hop count, the maximum trail cost, the maximum trail length, and
the maximum latency for the restoration route selected by the NE. If the restoration route exceeds these
limits, it will not be activated. Latency can be downloaded to the NE as an optimization criterion for
selecting the restoration route. Maximum values can be configured system-wide, or individual values
can be specified per trail. This allows for finer calibration of ASON/WSON protection schemes.
A checkbox enables operators to control ‘fallback to provisioned wavelength’ in WSON restoration.
When activated, the NE will always go through the original (provisioned) wavelength before assigning a
new wavelength for the restoration path. This prolongs the restoration time but ensures that any splitter-
coupler along the way will free previously assigned restoration wavelengths.

LightSOFT monitors ASON/WSON link status. An icon next to the A/W shield reflects the link’s
operational state (up/down/degraded/mismatch), and a new field reflecting it has been added to the link
properties window.

Ribbon Communications Inc. Proprietary 16-19

 Apollo Reference Manual Protection and restoration mechanisms

Restoration modes
GMPLS restoration can be implemented in one of the following modes:
 On-the-fly: If a fiber cut or some other LOS condition is detected, the head-end dynamically
calculates the best possible restoration path 'on the fly', using an intelligent CSPF algorithm.
 Pre-planned: The network prepares in advance a list of all possible failure scenarios. If a fiber cut
or some other LOS condition is detected, the head-end searches in the table to choose the most
appropriate restoration path. If the head-end doesn't find any appropriate path in the table, the
system automatically reverts to on-the-fly mode.

Coloring
Network operators can use 'coloring' of the network to designate a restoration area. Coloring limits the
area within which a service can be restored to a specific subset of the network.

Association for exclusion

Network operators may manually associate up to 3 ASON/WSON trails of the same technology into an
‘exclusion group’. This information is downloaded to the NEs, and when the control plane searches for
a restoration path for any of those trails, it will try to avoid overlap with the routes of the other trails in
the exclusion group.
Each group’s association may be either strict or loose.
 If it is strict, and there is no disjoint restoration path available, restoration will not take place.
 If it is loose and the control plane is unable to find a disjoint restoration route, it will still reroute the
trail, even though it overlaps one of the other trails in the group.
This feature is useful, for example, when trails are unrelated at the LightSOFT level but are actually all
serving the same end customer, and the network operator wishes them to be as disjoint as possible
when rerouted or restored. These more sophisticated understanding of trail overlaps enhances
management of the restoration schemes.

Ribbon Communications Inc. Proprietary 16-20

 Apollo Reference Manual Protection and restoration mechanisms

Manual ASON/WSON reroute away from specific data links

Network operators can reroute an ASON/WSON trail away from specific links selected by the user. This
is accomplished by marking these links as excluded, and triggering a reroute of the trail. Excluded links
are marked with a distinct orange color (instead of green/red) on the map. The exclusion may later be
revoked. This ability to exclude specific links enhances operator control of the ASON/WSON network.

Differentiating PM of ASON trails in restoration

PM data of ASON trails differentiates between objects in the provisioned and restoration routes,
enhancing the operators' ability to troubleshoot in the ASON network.

16.11.1.3 Management plane features

The management plane provides provisioning and operation (FCAPS) functions of NEs in the transport
plane. The management plane is expanded to accommodate the operations, administration,
maintenance, and provisioning (OAM&P) of control plane-related functionalities. Components of the
control plane are modeled as managed entities within the management plane, fitting into the existing
OAM architecture to minimize disruption to existing operational procedures.
All our transmission equipment is managed by a single management system, LightSOFT. The
LightSOFT NMS features a unique multidimensional approach to managing today's converged
networks. LightSOFT handles one physical layer and several technological layers, including
SDH/SONET, Ethernet, OTN, and optical.
LightSOFT offers on-demand service provisioning, pinpoint bandwidth allocation, and dramatic
reductions in equipment and operating costs that multiple management systems often require. It does
this by providing complete network management from a single platform, including configuration, fault
management, performance management, administrative procedures, maintenance operations, and
security control.

Ribbon Communications Inc. Proprietary 16-21

 Apollo Reference Manual Protection and restoration mechanisms

LightSOFT simplifies provisioning and day-to-day monitoring of optical services. Information on light
paths, wavelengths, channel availability, rates, is available through lists of optical links and trails.
LightSOFT provides fully automated optical trail provisioning, eliminating the need for operator
intervention at the EMS level. Automatic trail provisioning is also vital in networks based on ROADMs
and ODU cross-connects. ASON and WSON working at the wavelength and sub-wavelength levels
allow creation of complex mesh and ring network topologies. LightSOFT and STMS, working at the
NMS and EMS levels, are coordinated with the LightPLAN planning tool for full plug and play
automation.

Plug and play life cycle

16.11.2 Multiple protection and restoration schemes

The unique value proposition of ASON/WSON for carriers is the ability to improve existing network
resiliency by introducing the well-known restoration approach of IP networks. Service re-establishment
in case of failure has been a key feature of transmission networks, which offer service protection in less
than 50 msec.
Adding ASON/WSON to transmission networks brings added benefits without affecting the already
superior performance of today's network. With ASON/WSON restoration, the network itself monitors
services and restores them in the event of failure. (The ASON/WSON control plane is capable of
restoring services in case of multiple network failures.) Furthermore, the existing network capacity is
utilized more efficiently by sharing protection resources.
Our management applications support a range of protection schemes, allowing network planners to
balance the time needed for protection switching against the amount of resources that must be
dedicated to protection. For mission-critical services, distributed restoration mechanisms enable
50 msec service recovery and dedicated protection. For less critical services, distributed shared mesh
restoration schemes can be implemented. For efficient use of installed resources, pre-emptible services
can be established using the protecting resources.
Our management applications support coexistence of multiple protection and restoration schemes,
described in this section.

Ribbon Communications Inc. Proprietary 16-22

 Apollo Reference Manual Protection and restoration mechanisms

Apollo control plane restoration modes

1++ (Gold) protection

1++ (Gold) protection enables creation of a protected (ODU or LP) 1++ bidirectional trail for high priority
services. In the event of a problem on the main path, traffic is switched to the protection path within
50 msec. During restoration, an additional restoration path is also created, to provide a restoration
option for any subsequent problem that might occur on the same path. Sub-50 msec restoration times
are maintained "forever" for any number of failures, as long as valid restoration paths are available.
This protection scheme is an extension of the traditional 1+1 path protection, with failure in the main or
protection path resulting in restoration of the failed path. 1++ protection has the advantage of providing
recovery from multiple consecutive failures. This option exceeds the five nines standard, providing high
service availability with no service downtime, since ASON/WSON continuously builds a new protection
trail after each fiber cut. This protection scheme is the most bandwidth consuming, since traffic is
duplicated at all times.

1+1+R (Silver) protection

1+1+R (Silver) protection provides <50ms SNCP-based restoration on the first fiber cut via the
ASON/WSON control plane. Any subsequent fiber cuts are restored within a few seconds. This option
is less bandwidth consuming than 1++ (Gold) protection, providing additional protection while allowing
for efficient use of network resources.
1+R (Bronze) protection creates an unprotected 1+R bidirectional trail. In the event of a problem on the
main path, the system finds an alternative path using existing free resources. There is no SNCP
switching and traffic is restored dynamically within a few seconds.
Recovery paths are protected in the same way as the main path. New recovery paths can be
implemented as long as additional paths satisfying current criteria can be found. 1+R is also known as
reroute restoration.

1+R (Bronze) protection

1+R is an improvement over the corresponding unprotected option of regular SDH/SONET in that
service is restored dynamically on an alternate path within seconds, without operator intervention.
Typically, traffic is restored within one to two seconds. In more complex restoration topologies that
contain a large number of ASON/WSON nodes, restoration time can reach up to four seconds
maximum.
All ASON/WSON CoSs can be used in conjunction with underlying protection (for example, multiroute
OCH trails).

Ribbon Communications Inc. Proprietary 16-23

 Apollo Reference Manual Protection and restoration mechanisms

1+1 path protection

1+1 path protection is based on SNC-N path protection, with the network allocating a protection trail for
each working trail. The protection trail is activated automatically in case of failure, restoring service in
less than 50 msec.

1+0 unprotected trails

In the event of a problem on the main path, unprotected trails do not benefit from SNCP switching and
traffic fails.

Priority and preemption

The setup priority also defines the relative importance of the LSPs on the same restoration route.
During fault recovery, the setup priority determines the order in which LSPs are serviced. Higher-priority
LSPs tend to be re-established first and therefore enjoy more optimal path selection.
When there is not insufficient bandwidth to establish a more important LSP, you may choose to tear
down a less important existing LSP to free the necessary bandwidth. You do this by preempting the
existing LSP.

Regeneration pool
The regeneration pool/bank allows operators to minimize allocation of regenerators, in order to support
a given traffic matrix without sacrificing network survivability.
The goal is to design an allocation strategy that supports full demand while also placing a few
regenerators in strategic site(s), to regenerate the signal during restoration.
Efficient pool design means that Apollo uses the minimum quantity of shared regenerators necessary in
order to recover from multiple failures. Using shared resources enables a more efficient design while
reducing the total number of ports.

16.12 Equipment redundancy

Apollo provides redundancy protection for common unit equipment:
 The fan units are protected 1:n.
 The power supply is protected 1+1.
 The main controller is protected 1:1.
 The 1 Tbps universal fabric is protected 3:1.

Ribbon Communications Inc. Proprietary 16-24

17 Management system
The Apollo product line is managed by the LightSOFT multidimensional NMS, the STMS, and the
Apollo CLI, with an intuitive user-friendly GUI that makes new services easy to deploy and supervise.

17.1 LightSOFT NMS management

Our powerful network management suite, LightSOFT, is a unified NMS that provisions, monitors, and
controls all NEs and layers. Multiple transmission technologies are controlled: each is represented as a
layer (Ethernet/MPLS, OTN, optics, and SDH/SONET) in addition to the physical layer (fibers, copper,
etc.). This approach enables you to manage multiple technology layers independently of the physical
layer.
E2E tunnels, services, and trails are supported across the products, allowing services to be set that
start, for example, at the Neptune and terminate at an XDM or Apollo. LightSOFT also supports top-
down service and tunnel provisioning, reducing the time needed to provision new services.
Multidimensional LightSOFT manages our complete family of EMSs and enables you to assume full
control of all equipment in your network, including:
 NPT family of All-Native transport platforms for the metro
 Apollo family of NG transport platforms
 XDM family of multiservice transport platforms for the metro aggregation and metro core
 BroadGate family of multiservice transport for the metro access
 Multivendor networks

Ribbon Communications Inc. Proprietary 17-1

 Apollo Reference Manual Management system

One management system

LightSOFT offers on-demand service provisioning, pinpoint bandwidth allocation, and dramatic
reductions in equipment and operating costs that multiple management systems often require. It does
this by providing complete network management from a single platform, including configuration, fault
management, performance management, administrative procedures, maintenance operations, and
security control. Within one integrated management system, LightSOFT's network manager enables
you to fully control all your NEs regardless of their manufacturer, and view the complete network at a
glance. Multiple operators can simultaneously configure the network without any conflicts.
Network provisioning, particularly in the data era, has become very complex. For example, tunnels must
be pre-provisioned with various protection schemes. Service configuration requires setting multiple
parameters for each service. LightSOFT offers a number of powerful automation tools to ease the
provisioning process, thereby saving valuable OPEX for service providers. More services can be
created in the same amount of time, which is directly reflected in revenues. Automation tools include
automatic creation of tunnels per network or per service, automatic creation of bypass tunnels, reusable
templates, automatic configuration of the tunnels needed for mesh topologies, and more.
LightSOFT's comprehensive, E2E perspective supports comprehensive definition of MPLS tunnels,
Ethernet services, and SDH/SONET and optical trails, for primary and protection paths. LightSOFT
supports all types of trails and links (MoT, MoE, EoS, ETY, SDH/SONET, optical), protection schemes,
and user constraints. Simply point and click to connect any two endpoints, even in the most complex
topology. LightSOFT provides powerful trail reconstruction options to reconcile discrepancies between
different layers, as well as batch traffic management capabilities. LightSOFT provides smoothly
integrated management for packet, optical, and MSPP-based platforms.

Ribbon Communications Inc. Proprietary 17-2

 Apollo Reference Manual Management system

17.1.1 Layered architecture maximizes flexibility

Our management concept is based on a layered architecture in accordance with the ITU-T M.3010
standard for compliant layer architecture.
Separate layers make up the management structure as follows:
 The lowest level, the Network Element Layer (NEL), constitutes the embedded agent software of
the NEs.
 The second layer, the Element Management Layer (EML), controls many individual NEs.
 The third layer, the Network Management Layer (NML), controls the main network management
functions.

LightSOFT layered architecture management concept

LightSOFT functions at the NML while STMS functions at the EML. A northbound interface can connect
either STMS or LightSOFT to your Operations Support System (OSS).
At the NEL, the Apollo features the local craft terminal (LCT) system, providing fast easy connectivity to
the NE and enabling access to configuration and management functions through a user-friendly GUI as
well as an efficient CLI.

Ribbon Communications Inc. Proprietary 17-3

 Apollo Reference Manual Management system

17.1.2 Graphic user interface

The LightSOFT GUI provides a powerful yet easy-to-use tool for managing your network. The GUI
combines security, configuration, maintenance, and performance management tools with fault handling,
E2E trail definition, and database backups for uninterrupted and reliable network operation.
Multi-layer topology views enable you to display the topology of each technology layer independently of
the topology of the physical layer.

LightSOFT main window

17.1.3 Topology management

NEs can be deployed in a wide range of topologies, including single or multiple rings with appendages
and composite mesh topologies. You do not have to specify the type of topology in advance: simply
define and add NEs and LightSOFT creates the appropriate network plan. You move intuitively from an
overall survey of the network to detailed status and control views of any NE, transmission level, system
card, or trail.
LightSOFT makes it possible to manage NEs at multiple layers. It distinguishes between the managed
elements (MEs) that make up the network and the logical elements (LEs) these MEs represent. You
can:
 Focus on MEs when creating and deleting NEs (physical layer).
 Focus separately on the logical topology available at each technology level (Ethernet/MPLS, OTN,
optical, or SDH/SONET) when managing traffic (technology layer).
In IP/MPLS networks, the LightSOFT topology map includes IP/MPLS routers, ports with IP capabilities
over logical interfaces (LIFs), LAGs, IP network links between routers, and third party routers, listed as
IP/MPLS UMEs.

Ribbon Communications Inc. Proprietary 17-4

 Apollo Reference Manual Management system

Two types of LAG modes are supported: Load Sharing or 1:1 Protection. A typical LAG configuration is
illustrated in the following port properties window.

Properties for Port - ETH/MPLS tab

Whenever an ME is added to the network at the physical layer, an LE is automatically projected into the
relevant technology layer. If an ME contains ports that belong to multiple technologies, LEs are created
at each technology layer containing only the ports relevant to that layer. Nested groups are supported
and can be defined differently in the various layers.

17.1.4 DWDM trails

OTN technology offers a range of rates up to 600 Gbps.
OTN interfaces are supported through the following types of trails:
 Optical Multiplex Section (OMS) trails at the foundation level carry multiple wavelengths,
running through Optical Transmission Section (OTS) ports. OTS ports are configured on
equipment with more than one wavelength supporting OMS interfaces. These ports are used, for
example, in amplifiers or DCF cards, or in OADM or Mux/DeMux cards for channelization
purposes.
 Optical Channel (OCH) trails represent a single channel, running on top of OMS trails between
the appropriate Optical Transport Unit (OTU) ports, and possibly running through Optical
Channel Ports (OCHP) used for single-wavelength OCH interfaces. OTU ports are configured for
port rates ranging from OTU1 to OTUC4.

Ribbon Communications Inc. Proprietary 17-5

 Apollo Reference Manual Management system

 Optical Data Unit (ODU) trails usually represent server trails for lower-rate Lightpath services
running on top of OCH trails, between appropriate OTU ports. An ODU trail can also act as a
service for comparable OTU services running between appropriate OTU ports.
 LightPath (LP) trails represent an end-to-end service, running over ODU or OCH trails, between
client ports. If the line rate is equivalent to the client rate, then the LP runs directly over an OCH
trail. If the line rate is greater than the client rate, then the LP runs over an ODU server trail which
runs over the underlying OCH trail.
In a typical optical network, components are configured into a hierarchy of OMS, OCH, ODU, LP trails,
as illustrated in the following figure:

Hierarchy of optical trails

OMS trails run at the most basic, foundation level between multiplexing devices (MDs).
They can be unidirectional or bidirectional. They behave as server trails that carry multiple OCH trails in
fixed groups. DWDM is typically configured for 8, 16, 32, 44, 48, 88, 96 or flex-grid channel groups.
CWDM is configured for 4 or 8 channels. Amplifiers may be included in the path of an OMS trail.
Multiple OMSs, connected in tandem, cause alarms to be reported only with respect to the directly
associated OMS trail segments and not at other segments along the path.
LightSOFT also supports ODU packet trails, a special type of ODU server trail used to carry data
traffic over the OTN. These packet trails can have a main and a secondary component – the secondary
trail enables LAG-based resiliency of packet connectivity upon a failure of one of the two links – and
their bandwidth may be hitlessly adjusted, as per ITU recommendation G.7044. Each endpoint of an
ODU packet trail is always connected to a VPP (Virtual Packet Port), a virtual data port used to pass
data traffic over the OTN.
Hitless Adjustment of ODUflex (HAO) is a set of protocols which enables the user to perform
bandwidth resizing of the ODU packet server trail without a traffic hit, hence the name. HAO is defined
in ITU G.7044. HAO is initiated from LightSOFT, with participation of STMS at the EMS level.

LightSOFT simplifies provisioning and day-to-day monitoring of optical services. Information on light
paths, wavelengths, channel availability, rates, is available from optical links and optical trail lists.
LightSOFT provides fully automated optical trail provisioning, eliminating operator intervention at the
EMS level. Automatic trail provisioning is also vital in networks based on ROADMs and ODU cross-
connect that allow creation of complex mesh and ring network topologies at the wavelength and sub-
wavelength levels.

Ribbon Communications Inc. Proprietary 17-6

 Apollo Reference Manual Management system

The following features are especially valuable:

 Point-and-click functionality for optical trail creation and activation of optical services for all types
of trails, including OMS, OCH, ODU, LightPath (LP), EoS over optics, protected and unprotected,
P2P, and P2MP (drop-and-continue).
 Top-down trails provisioning beginning at the NMS level with LightSOFT (creating trails) and
automatically continuing down to the EMS (implementing details).
 Rapid trail creation, with a choice of either:
 Fully automatic pathfinding, where you specify the endpoints and LightSOFT chooses the
optimal path for both main and protection segments.
 Fully manual, where you specify the exact trail path and LightSOFT completes the trail
provisioning tasks.
 Combination, where you specify the trail endpoints and specific segments of the path and
LightSOFT automatically completes the rest of the path route and provisioning.
 Sophisticated ODU multiplexing capabilities that provide the following benefits:
 Support of lower granularity ODU0 - 125Gbps (PT21).
 Flat ODU hierarchy means that ODUk can sit directly on an ODU4 trail.
 High order ODU trails can include ODUk trails of various rates. Rates do not need to be of a
single, uniform type.
 Choice of ODU interfaces provide greater efficiency of resource usage.
 GCT split single-card LEs on technology layers (such as the optical layer) directly opening the
internal card view.
 Utilization tables showing the state of the channels through a DWDM or CWDM OMS trail, helping
you decide which channel to utilize.
 Availability maps and tables and sophisticated maintenance tools enhance trail provisioning and
management.
 Optical network control parameters (s) are utilized by our platforms to enable proper gain setting
and power equalization along the entire network. s are a set of optical parameters generated
independently at a terminal or ROADM node, and are transmitted periodically through the entire
network, from one optical card to the next and from one node to the next, following the actual
optical transmission direction.
 OSNR Weight, estimated OSNR value assigned per OMS trail, calculated internally by
LightSOFT, based on the physical signal parameters. Higher OSNR values correlate with better
signal quality. Assigning a greater priority to OSNR Weight values means that PathFinder gives
these values greater importance when provisioning an OCH trail. OSNR levels can be displayed in
LightSOFT on demand for any existing Apollo trail or link.
You can automatically acquire all OMS, ODU, OCH, LP, and EoS trails in a single optical trail discovery
operation. This is especially useful when the system is first installed. Optical trails can also be
provisioned by the OSS via NBI.

Ribbon Communications Inc. Proprietary 17-7

 Apollo Reference Manual Management system

17.1.5 Optical trail provisioning and management

Different optical components may require specific network management capabilities. LightSOFT
provides all the tools necessary for effective network design, configuration, and management of all
components. For example:
 LightSOFT utilizes specific payload objects (SPOs) when supporting trails using the multiprotocol
AoC or OMCM cards. LightSOFT also supports P2MP LightPaths for AoC and OMCM25 cards.
 If a wavelength (line port) is connected to a multiplexer or ROADM, LightSOFT provides enhanced
validation, preventing mistakes during link creation.
 LightSOFT displays the reason why an optical trail is classified as a Flex trail, allowing you to
detect and correct it. Flex trails are non-classified trails with non-standard trail patterns.
Route selection for optical trails can be fully automatic using LightSOFT’s PathFinder algorithm, fully
manual using LightSOFT’s GUI, or partially automated. PathFinder selects the optimal main path based
on the minimum hops criterion. You can apply route constraints, such as segments that must be
included. This algorithm takes into consideration wavelength switching within the topology.
For maximum protective value, PathFinder selects protection path routes that offer the maximum
diversity from the main traffic paths, as illustrated in the following example.

Main and protection trails highlighted

LightSOFT verifies the correctness of the endpoints and user-selected trails. Parameters such as
Forward Error Correction (FEC) and line code are checked, significantly reducing the chance of
configuration errors.
Once a path is selected, optical XCs are automatically provisioned on the NEs along the trail.
LightSOFT provides a table with a list of available frequencies across multiple OMS trails, making it
simple to select the frequency used at trail endpoints.

Ribbon Communications Inc. Proprietary 17-8

 Apollo Reference Manual Management system

Frequency availability table

Creating and editing optical trails in single and bulk operations is possible using the XML file import
feature.
To enable proper gain setting and power equalization along the entire network, Apollo utilizes optical
network control parameters (s), a set of optical parameters transmitted periodically. They are generated
independently at a terminal or ROADM node, and are transmitted through the entire network.
LightSOFT enables LS operator to check the OSNR level of an optical trail during its creation and select
a different path if so indicated.

Ribbon Communications Inc. Proprietary 17-9

 Apollo Reference Manual Management system

17.1.6 LightPath availability maps

LightSOFT includes enhanced availability maps for OCH via LightPath. These maps show resource
availability, ensuring that link capacity suits the required services.
First check the area in which you wish to create a new trail to verify that the links have enough capacity.
The following figure shows a simple availability map for a network fragment after a traffic segment was
added.

Availability map after additional trails added

Network availability information can be exported to external applications in CSV format using a
command line.

Ribbon Communications Inc. Proprietary 17-10

 Apollo Reference Manual Management system

17.1.7 Control map

LightSOFT has a Control Map, which enables the operator to visualize the management channels. It
enables the operator to view the route of the management communication channel between STMS and
all Apollo NEs in the network. It also provides information on the transport layers of each span of the
management channel (GCC, external DCN, OSC, VLAN using L2 cards).

Control map

Ribbon Communications Inc. Proprietary 17-11

 Apollo Reference Manual Management system

17.1.8 Management security mechanisms

We are committed to incorporating powerful, advanced security technology and methodology across
the full range of our product offering. For example, the data cards, through the LightSOFT NMS and the
EMS software, support a full range of features to keep your network running smoothly and protect it
from unauthorized and malicious use. Supported features include:
 Cluster solution that provides high availability and load balancing, essential features for large
networks and/or mission-critical management.
 Remote Database Replication (RDR), a field-proven flexible redundancy mechanism providing
full network management backup capabilities for Disaster Recovery Plans (DRPs).
 Customer Network Management (CNM), enabling SPs to lease exclusive network resources to
customers for self-management. This sophisticated scheme allows both the autonomous end
customer and the SP to concurrently manage alarms and performance, provision services, and
handle maintenance operations on the resources.
Additional key security enhancements are now in development and will be implemented in upcoming
releases. The STMS can be upgraded to apply enhanced security settings to the EMS, and to selected
NEs managed by the EMS. Communication channels between entities with enhanced security settings
are secured and information is sent via SSH2 protocol.

17.1.9 Management interfaces

Communications between the user and the management system is through a choice of interfaces.
The standard CORBA-based interface complies with the MultiTechnology Network Management
(MTNM) information model developed by the TeleManagement Forum (TMF), a consortium of all major
telecom equipment vendors. LightSOFT works with both north- and southbound CORBA-based
interfaces for managing third-party equipment or being managed by upper-level management systems.
The EML level supports the same interface, northbound.
An SNMP alarm gateway is available for sending alarms from the NMS/EMS to an OSS application that
can handle SNMP traps.
LightSOFT provides additional interfaces, such as export of current alarms via FTP, email, or SMS,
import/export of XCs/NEs and platform configurations, and database access. In addition, the EML level
supports interfaces such as retrieval of daily performance files, export of device inventory and alarms in
HTML format, and Java RMI for integration with third-party OSS/NMS solutions.

Client/Server architecture
The LightSOFT network management suite implements an advanced client/server software architecture
that supports a large number of processes. The NMS server can be run on either single or multiple
workstations. This distributed architecture enables you to scale easily, as well as provide high
availability and load balancing. LightSOFT supports dozens of concurrent clients. The multiconfigurator
feature of LightSOFT gives each operator the means to initiate sessions and manage the network
simultaneously, either in whole or in part.

Ribbon Communications Inc. Proprietary 17-12

 Apollo Reference Manual Management system

17.2 Shade Tree Management System (STMS)

Shade Tree Management System (STMS) is the element management, service provisioning, and
monitoring solution for the Apollo series. STMS provides Fault, Configuration, Administration,
Performance, and Security (FCAPS) management. It offers powerful service management capabilities
for a complete suite of Wavelength Division Multiplexing (WDM) and Optical Transport Network (OTN)
services.
 Integrated management: STMS includes smooth integration with the LightSOFT® management
system. STMS can also be operated in standalone mode on a Linux PC, a cost-effective
management option for small networks.
 Intelligent troubleshooting: STMS offers advanced troubleshooting tools to detect and resolve
network issues, such as Ethernet, WDM, and OTN service failures, misconfiguration, incorrect
software versions, and disconnected interfaces. STMS reduces the time to provision, deploy, and
define network elements, cards and interfaces by providing a user-friendly GUI to simplify the
configuration process.
 Efficient preconfiguration: STMS supports preconfiguration of cards and interfaces. After
installing the actual equipment, STMS verifies the configuration, and sends notification if there is a
configuration mismatch.
 Comprehensive reports: STMS gathers, processes, and stores statistical information that is
collected by the network elements to generate complete and accurate performance management
reports.

Multiple management modes

STMS offers three management options:
 E2E network management solution, for larger, more complex networks, including smooth
integration with LightSOFT and the added benefits of the LightPLAN planning tools.
 Independent small network management solution, with STMS providing all the necessary NMS
layer functionality.
 Local management for individual equipment, offering a cost-effective solution for specific
configuration niches.

STMS management options

Ribbon Communications Inc. Proprietary 17-13

 Apollo Reference Manual Management system

STMS functions at the EMS level, featuring:

 Smooth integration with LightSOFT at the NMS level.
 Plug&Play functionality for easy commissioning and deployment of Apollo networks.
 Powerful optical management capabilities.
 Comprehensive set of management tools for:
 Installation.
 NE commissioning (including slot assignment, IP routing, and DCN configuration).
 Port and XC provisioning.
 Troubleshooting.
 Performance monitoring in STMS provides 15-minute and 24-hour PM on all optical interfaces and
sub-interfaces.
 Best-of-breed fault, configuration, accounting, performance, and security (FCAPS) management,
including alarm and event management, inventory, security management, and system
administration.

ONCP monitoring and analysis

LightPulse, LightSOFT's sophisticated network-wide power equalization capability, is based on STMS's
optical network control parameters (ONCPs), a set of optical parameters transmitted periodically
through the entire network. ONCP data includes advanced channel and link parameters beyond power,
such as OSNR, dispersion, and other estimated parameters that can be used to dynamically monitor
and control the network. ONCP data analysis enables the following network functionalities:
 Power/gain control in EDFA, ROADM, and FOADM cards.
 Real time diagnostics.
 Span/connection loss diagnostics.
 Performance diagnostics, including channel OSNR, dispersion, polarization mode dispersion
(PMD), and nonlinear phase.
 Performance verification for a preinstalled trail.
The result is simplicity, easier network operation, and significant savings of time and money in terms of
real time fault management, since instead of sending a technician to a remote site with expensive
testing equipment, you have the information and control you need even from afar.

Ribbon Communications Inc. Proprietary 17-14

 Apollo Reference Manual Management system

Optical parameters

Fiber connectivity
STMS supports fiber connectivity, for easy creation of links bottom-up to LightSOFT. Fiber connectivity
can be defined either bottom up (defined in STMS, and automatically uploaded to LightSOFT, or top-
down (defined in LightSOFT during topology link creation, and automatically downloaded to STMS).
The STMS GUI enables easy configuration of optical cross connections. When creating links in the
STMS, fiber connectivity information is uploaded to LightSOFT by default. LightSOFT creates the
relevant topology links and updates the link parameters accordingly.
Additional features include:
 Optical protection (port and SNCP)
 PM/FM profiles (shelf/card assignment and port/transceiver configuration)
 Actual/Expected comparison for equipment preconfiguration
 Inventory, maintenance, and port loopback operations
 Timing configurations
 Alien wavelength support enables installation and configuration of third party transceivers

Ribbon Communications Inc. Proprietary 17-15

 Apollo Reference Manual Management system

17.2.1 STMS key features

STMS features a rich set of provisioning, monitoring, and management capabilities.
 Carrier class network management: STMS works in a highly-available, warm-standby,
redundant configuration, eliminating a single point of failure (SPOF) and allowing carriers to
minimize downtime. STMS clients are synchronized with the STMS CLI to enable operators and
engineers to coordinate and enable troubleshooting. STMS uses efficient configuration change
events sent from the device to the STMS that communicate only with those configuration parts
that changed.

 Comprehensive network planning: The comprehensive and accurate data stored in the STMS
database enable effective network planning. Managed device, inventory, and available slot reports
assist capacity planning and inventory control. Device-monitoring capabilities prevent problems
from reaching a critical stage by providing proactive monitoring of components, such as CPU
utilization, file system size, memory usage, and device temperature, sending alerts when
thresholds are exceeded.
 LightSOFT integration: STMS can be integrated with LightSOFT to support inventory
management, alarm management, WDM and OTN service management. It supports Multi
Technology Network Management (MTNM) CORBA-based interface. In addition, the rest of STMS
functionality is available with GUI cut-through (GCT). LightSOFT delivers comprehensive support
and management capabilities across multiple layers, networks, and technologies. The GCT
enables LightSOFT to open an STMS window in a specific context and allows the LightSOFT
operator to get to it quickly, thus providing a mechanism for performing any operation that is
available in STMS but not in LightSOFT.
 Lite Packet support: STMS supports Apollo's Lite Packet feature, which provides MEF-compliant
Ethernet services over an ODU XC domain. Lite Packet includes the following capabilities:
 LAG-based resiliency for packet connectivity
 I/O port protection for packet ports that are not participating in a LAG configuration
 BW on demand for packet connectivity, also known as hitless BW adaptation for ODUflex
(GFP-F)

Ribbon Communications Inc. Proprietary 17-16

Apollo Reference Manual Management system

 Report generation: You can generate various types of reports using STMS. The reports are
saved in HTML format to the reports directory on the STMS server and can be viewed using a
web browser. You can change the default reports directory as required. The following STMS
reports are available:
 Managed devices: General information about managed NEs. Reports can be generated for
the STMS domain (listing all managed NEs), for a group (listing all of the NEs in that group),
or for a single NE.
 Inventory: General information about populated card cage slots. Reports can be generated
for the STMS domain (listing all managed NEs), for a group (listing all of the NEs in that
group), or for a single NE.
 Available slots: List of available (empty) card cage slots. Reports can be generated for the
STMS domain (listing all managed NEs), for a group (listing all of the NEs in that group), or
for a single NE.
 Customers: Information about the logical interfaces and E Line services assigned to
customers. Reports can be generated for all customers (listing the interfaces and services
assigned to each customer in your network) or for a single customer (listing only the
interfaces and services assigned to that customer).
 Interface utilization: Utilization information about logical interfaces. Reports can be
generated for a single logical interface or for a single customer (listing all of the logical
interfaces assigned to that customer).
 Security management: Security management features enable easy creation and management of
STMS users and permissions. The Action Log module also provides monitoring capabilities for
security management. Only users defined with Administrator and Security privileges have access
to all of the security management options. Other users are limited to minimal access to security
settings.
 ASON/WSON protection and restoration: ASON/WSON-protected trails are created and
managed at the NMS level through LightSOFT. STMS offers the ability to view
ASON/WSON-related information for a selected NE.
 License management: A License Manager manages STMS licenses. Some STMS features are
only available if the relevant license has been purchased. Use the License Manager to view a list
of available features and to update licensing as required.

Ribbon Communications Inc. Proprietary 17-17

 Apollo Reference Manual Management system

17.3 CLI configuration

Our platforms support a fully functional CLI capable of configuring, monitoring, troubleshooting, and
debugging any configurable and measurable parameter. CLI uses a transaction-based mechanism. CLI
can be run in multiple sessions, and supports multiple users. For example, if you enter configuration
mode while other users are editing the configuration, the CLI displays a list of users who are editing the
configuration and the amount of time they have been idle.

17.3.1 Command line interface

CLI is the primary device management interface, whether a user is logged in from a console or from a
remote location via Telnet or a secure shell. CLI starts automatically when you log into the device,
either from the console or via Telnet or SSH. The intuitive text-based command interface features:
 Operation and configuration modes
 Hierarchical command and configuration structure
 Context-sensitive help
 Command completion
CLI commands are organized in a hierarchical structure. Common keyboard commands can be used to
navigate within the hierarchy, such as CTRL-W to erase words, or CTRL-A/CTRL-E to go to the
beginning or end of the line.

CLI commands

Ribbon Communications Inc. Proprietary 17-18

 Apollo Reference Manual Management system

CLI operates in two modes:

 Operation:
Initial login is in operation mode. Use operation mode commands to view, monitor, and
troubleshoot the system as it is running. Commands are organized into a hierarchical structure.
Commands with similar functions are grouped together under a common command name and
start with the same word.
The following figure illustrates the command structure. For example, all commands that reset
statistics or connections begin with clear.

 Configuration:
In configuration mode, you create and edit the configuration of the device, such as interfaces,
routing protocols, routing policy, and CoS parameters. Configuration changes are not
implemented until the user commits them, at which time the changes are pushed out to the
hardware.
The configuration statements are also organized into a hierarchical structure. Because the
configuration is structured, you view the configuration statement and determine the command you
would use to set, edit, or delete the statement.
For example, the command to configure a Gigabit Ethernet interface with an IP address is set
interfaces ge-ts1/0 unit 0 family inet address 172.18.1.154/24
When you display the configuration, it displays as:
interfaces {
ge-ts1/0 {
unit 0 {
family inet {
address 172.18.1.154/24;
}
}
}
}
The structure of the command statements also allow you to edit and delete parts of the statements
at different levels. For example, to delete only the IP address from the previous configuration, you
type:
delete interfaces ge-ts1/0 unit 0 family inet address
172.18.1.154/24
To delete the entire configuration for interface ge-ts1/0, you type:
delete interfaces ge-ts1/0
CLI is also used to load NE configuration files and/or XML files. Initial NE installation or NE expansion is
faster and easier when loading an NE configuration generated by a planning tool.
Most of the debug, output, and show commands are very similar to JunOS CLI, which purposely makes
the 24 x 7 first line support of the product very familiar.

Ribbon Communications Inc. Proprietary 17-19

 Apollo Reference Manual Management system

17.4 NETCONF
The Network Configuration protocol (NETCONF) is an IETF network management protocol published in
RFC 4741 (2006) and revised in RFC6241 (2011). NETCONF has gained strong industry support and
is being adopted by major network equipment providers as the primary candidate for provisioning
network functions. Using protocols like NETCONF and data models such as YANG, SDN controllers
can provision services across vendor and technology domains because they have a standardized
method to provision different network functions, using a consistent set of data models.
NETCONF is specifically not meant to replace SNMP, but rather to provide significant improvements in
the area of configuration management, by offering Seamless integration with existing and future
OSS/BSS environments. The loosely-coupled and modular architecture leverages open APIs and
standard protocols, enabling orchestration across multi-domain and multi-layer for centralized policy
and services across the entire network. NETCONF provides universal mechanisms to install,
manipulate, and delete network device configurations. Operations are realized on top of a simple
Remote Procedure Call (RPC) layer. The NETCONF protocol uses XML based data encoding for the
configuration data as well as the protocol messages.
NETCONF is designed to be a replacement for CLI-based programming interfaces, such as Perl +
Expect over Secure Shell (SSH). NETCONF is usually transported over the SSH protocol using the
“NETCONF” sub-system, and in many ways it mimics the native proprietary CLI over SSH interface
available in a device. However, it uses structured schema-driven data and provides detailed structured
error return information, which CLI cannot provide.
NETCONF is based on ACID to define a transaction:
 Atomicity: Transactions are like a bulk operation, where the whole set either takes or it fails.
 Consistency: Transactions can be implemented simultaneously. They are not order-dependent as
with CLI. If this cannot be done, the implication is that the system is not transactional.
 Independence: Parallel transactions are independent. They do not conflict, and always appear to
be in-sequence.
 Durability: Committed data is not expected to be withdrawn.
NETCONF provides operators with a standardized method to distribute changes to participating devices
and validate them locally before activating them. This is accomplished through a system of data stores
and device states. For example, configuration data can be sent to candidate databases in the devices
before they are committed to running in production applications. This is illustrated in the lower two rows
of the following figure.

Ribbon Communications Inc. Proprietary 17-20

Apollo Reference Manual Management system

NETCONF datastores

Ribbon Communications Inc. Proprietary 17-21

 Apollo Reference Manual Management system

All NETCONF devices must allow the configuration data to be locked, edited, saved, and unlocked. In
addition, all modifications to the configuration data must be saved in non-volatile storage. A typical
example from RFC 4741 illustrates this approach. The following code sample adds an interface named
“Ethernet0/0” to the running configuration, replacing any previous interface with that name.

NETCONF provides operators with a standardized, regimented, yet flexible means to manipulate
network device configuration, using XML with an applied structure that can be validated effectively.
YANG (Yet Another Next Generation) data modeling language is used to model configuration and state
data. The YANG modeling language was defined in RFC 6020 by IETF through the NETCONF Data
Modeling Language Working Group (NETMOD). YANG extensions allow codeless, intuitive, GUI-based
modeling and provisioning. This enables operators to provide higher level abstraction for orchestrating
and automating devices and network services.
YANG is tree-structured rather than object-oriented. Configuration data is organized into a tree
hierarchy, and the data can be of complex types such as lists and unions. The definitions are contained
in modules, where one module can augment the tree within another module. YANG also differentiates
between configuration and operational data. YANG differs from previous network management data
model languages by its strong support of constraints and data validation rules. Strong revision rules are
defined for modules.

Ribbon Communications Inc. Proprietary 17-22

 Apollo Reference Manual Management system

A simple YANG coding example is illustrated in the following figure.

NETCONF/YANG‘s ambition is to enable universal multi-vendor R/W element and service

management, thereby supporting a truly open standard programmability architecture.

Ribbon Communications Inc. Proprietary 17-23

 Apollo Reference Manual Management system

17.4.1 Disaggregation application

Disaggregation allows network operators to pursue a best-of-breed approach to building optical
networks. It relies on vendors creating standalone optical subsystems with well-defined control
interfaces.
The primary approach is where a single vendor provides an Open Optical Line System (Open OLS)
composed of ROADMs and amplifiers. These transport alien wavelengths and even alien spectrums
from third-party vendors of transponder and muxponder subsystems, as well as the wavelengths and
spectrums of the Open OLS vendor itself.
Initially, Open OLS is expected to be deployed for short-haul, point-to-point applications, like data
center interconnects. Then, as experience is gained, it will be used for more complex metro and long-
haul optical networking applications.

Apollo platforms support open interfaces using NETCONF/YANG. We are a member in the
OpenROADM MSA (http://openroadm.org/ http://www.openroadm.org/) and part of the group
implementing the OpenROADM data model. As an active participant in professional conferences such
as SC19 (International Conference for High Performance Computing, Networking, Storage, and
Analysis, and OFC 2020 (Optical Fiber Communications Conference and Exhibition), we have
demonstrated openness and interoperability with 3rd party OpenROADM optical domain controllers
(ODC), together with OTN and standard FEC interoperability. We have achieved:
 E2E service creation directly from AT&T controller using only NETCONF/YANG
 Line rate interoperability with 3rd party switchponders using SC-FEC
 OTN switching interoperability with 3rd party switchponders

Ribbon Communications Inc. Proprietary 17-24

 Apollo Reference Manual Management system

17.5 Integration with other products

The Apollo has been designed to integrate smoothly with networks that are based on 3rd party
equipment. You can build multivendor networks with a free flow of management information between
Ethernet/MPLS, SDH/SONET, OTN, and other complementary access, radio, and switching products.

17.6 DC power management

The DC power management feature provides the capability of measuring and displaying the values of
DC power consumption of each Apollo card installed in an OPT99xx platform and the DC power value
of the full platform. The DC power values can be monitored on the Apollo management system (STMS,
LightSOFT, CLI).
The DC power management is supported in the Apollo OPT99xx family and provides the following
functions:
 Display of online measured DC power values for each card inserted in the platform.
 Display of online measured DC power value of the platform with existing cards (inserted and
assigned).
 The measurement results are stored in the xRCP/xRCP1 database.
 Supported management systems include:
 STMS
 CLI
 LightSOFT (cut-through to the level of STMS)
 In cards with fixed transceivers, they are considered as part of the card.
 For cards with pluggable transceivers the value is displayed as a single figure for the card.
 Events that trigger a refresh or update in the DC power stored value include:
 Inserting a card/transceiver.
 Extracting a card/transceiver.
 Assignment of a card/transceiver.
 Unassignment of a card/transceiver.
 Change in fan speed level.

Ribbon Communications Inc. Proprietary 17-25

18 Embedded management
Network operators face serious operation challenges as they deploy converged networks including
optical and data capabilities. The main challenges are provisioning, fault management, maintenance
and performance monitoring. These are even more important as strict SLA requirements increase, and
operators must have the capability to efficiently detect, isolate, and troubleshoot E2E network
performance and connectivity. Usually, network management is applied from outside the network.
Embedded management brings a new dimension, as it is from within the network and the NEs.
The Apollo embedded management provides comprehensive tools for operators to cope with these
challenges successfully, and includes the following main functions:
 Equipment management
 FCAPS, related to the following:
 Fault management
 Configuration
 Administration/Accounting (not applicable for the Apollo)
 PM
 Security
 Fiber connectivity with embedded power control equalization
 Ease of use
Embedded management enables enhanced maintenance and repair capabilities, including rapid fault
allocation, shorter equipment downtime, and fewer traffic-affecting incidences. Due to built-in fault
management, the user can detect malfunctioning equipment in a much shorter time.

18.1 Equipment management

Apollo supports equipment entities management of Field Replaceable Units (FRUs). The Apollo
managed equipment is divided into three main groups:
 Shelves
 Cards
 Pluggable transceivers

18.1.1 Shelf types

Apollo equipment includes passive and service shelf types:
 Passive optical shelf: Accommodates passive I/O cards, with or without a controller card. Such
shelf doesn’t require any configuration commands in order to operate its cards. Thus a controller
is not a must and the shelf can operate without it. If a controller is added to the shelf, it provides
inventory management capabilities (future function). Examples of passive shelves are Artemis-1P
and Artemis-2A.
 Service shelf: Requires a controller card in order to operate the platform and its cards. It includes
several card categories:
 Common cards like controller cards, fan units, power supply, fabric cards.
 Service cards like AoC10, CMR40B, TR10_4
 Optic cards like Amplifiers, ROADMs

Ribbon Communications Inc. Proprietary 18-1

 Apollo Reference Manual Embedded management

 Passive optic cards like Mux/DeMux, DCFs, OADMs

 Layer 2 data cards (future release)
Examples of service shelves are: OPT9624, OPT9608, OPT9603.

18.1.2 Card types

The Apollo cards include the following main categories:
 Common cards
 Passive optical cards
 Optical cards
 Service cards
 L2 data cards
Common cards: Provide the common functionality of a shelf such as: controller cards, fan units, fabric
cards.
Passive optical cards: All optical cards that don’t require power for their operation. Such cards don’t
have VOA and continue to operate even if they are plugged out from a shelf, for example, Mux/DeMux,
DCFs.
Optical cards: Optical cards that need power for their operation, for example, amplifier cards,
ROADMs.
Service cards: Cards supporting different type of services with and/or without interface to the fabric
cards.
Examples:
Service cards with no interface to fabric are: TR10_4, AOC10, and CMR40B.
FIO10_5, FIOMR_16, FIO100 and FIO100M are service cards with interface to the fabric.
L2 data cards: Support L2 functionality.

18.1.3 Transceiver types

Transceivers are used only for optical/electrical (O/E) conversion and are part of service cards, L2 data
cards, and cards having SFPs.
The following transceivers are supported:
 Extractable single transceiver
 Non-extractable transceiver
Extractable single transceiver: Managed as part of a port entity. Any transceiver failure is handled as
an equipment alarm of the port. Examples are, SFP, XFP.
Third party transceivers can be used for non-OTN ports.
Non-extractable transceiver: Managed as part of a port entity. Failure in the transceiver generates a
failure on the port and on its supporting equipment.

Ribbon Communications Inc. Proprietary 18-2

 Apollo Reference Manual Embedded management

18.1.4 Equipment hierarchy

Apollo equipment hierarchy is a model that implies configuration, ordering of equipment, and/or
relations between entities for alarm management. The following figure depicts this model.

Equipment hierarchy model

Equipment hierarchy also includes modules that are extractable with multiple transceivers. Port is a
bundle of equipment and/or L1 interfaces and services. When the port contains transceiver FRU, it
reports equipment alarms. Only in such a case is the port part of equipment hierarchy.

18.1.5 Equipment entities

Equipment entities for management are divided into the following groups:
 Equipment holder:
 Shelf, such as passive shelf and service shelf
 Slot
 Cards
 Ports having pluggable transceiver, such as XFP and SFP

18.1.5.1 Apollo slot occupation size

All Apollo shelves (service shelves and/or optic shelves) comply with the following slot occupation
types:
 Single slot
 Double slot

Ribbon Communications Inc. Proprietary 18-3

 Apollo Reference Manual Embedded management

Double slot card

 Double-wide slot

Double-wide slot card

 Quad slot

Quad slot card

Ribbon Communications Inc. Proprietary 18-4

 Apollo Reference Manual Embedded management

The slot numbering is identical for single-slot cards and double-slot cards in both service shelves (e.g.
OPT9624, OPT9608) and passive shelves (e.g. Artemis-1P, Artemis-4A).
The following figure depicts the identical slot numbering in the case of double-slot card.

Double slot numbering

The slot numbering is different in double-wide cards as shown in the following figure.

Double-wide slot numbering

The slot numbering is different in quad cards as shown in the following figure.

Ribbon Communications Inc. Proprietary 18-5

 Apollo Reference Manual Embedded management

Quad slot numbering

18.1.6 Transport entities

Transport entities in Apollo are divided into two main groups:
 Port entity: Bundles transceiver equipment and/or interfaces for transmission (extractable or
soldered physical ports), for example, STM-64 port, OTU2 port, 1GFC port, 10 GbE port.
 L1 interface entity: Standardized unit that is part of SDH/SONET or OTN payload, including its
management overhead and synchronization, for example, in OTN (ODU1, ODU2, OCH).
Apollo transport entities support the following technologies:
 OTN
 SDH/SONET
 Fiber Channel (FC)
 Ethernet
 Constant Bit Rate (CBR)
The L1 interface is created automatically by the NE on top of a port entity, as shown in the following
figure.

L1 interface entity

The L1 interface may have hierarchy in the case of OTN technology, as shown in the following figure.

Ribbon Communications Inc. Proprietary 18-6

 Apollo Reference Manual Embedded management

L1 interface hierarchy

18.1.7 Compliance with "Green" requirements

The Apollo shelves have been designed to save power and be as eco-friendly (“Green”) as possible. In
addition to the overall design approach to use components consuming minimal power and high-
efficiency power supplies. Green requirements is a built in feature in the NE and it is operated without
operator intervention. The following features minimize power consumption:
 The installed shelves are automatically discovered by the NE embedded management (future).
 Each slot reports its inventory to management. If equipment is plugged into an unassigned slot or
there is a mismatch between the plugged equipment and the slot assignment, the NE moves the
card into shut down mode that consumes minimal power. In case of mismatch between the
assigned slot and the plugged in equipment the NE generate Equipment Mismatch alarm.
 Each transceiver reports its inventory to management. If the transceiver is plugged into an
unconfigured port or there is a mismatch between the actual transceiver and the configured one,
the NE powers off the transceiver in order to save power.

18.1.8 Inventory information

Each Apollo FRU (shelf, card, pluggable transceiver) is equipped with a non-volatile memory (ID-
PROM) that stores its inventory information. The inventory information can be retrieved via a CLI or
STMS command. Inventory attributes of each FRU includes the information listed in the following table.

Inventory attributes for Apollo FRUs

Inventory attributes Shelf Card Pluggable transceiver

Type   
Serial number   
Part number N/A N/A 
Size N/A number of slots occupation N/A
Vendor name   
Vendor date code N/A N/A 
HW revision   
HW option   N/A
Replaces ST "hardware configuration"
SW version N/A Boot SW version N/A

Inventory information of a main shelf also provides inventory information of subtending passive shelves.

Ribbon Communications Inc. Proprietary 18-7

 Apollo Reference Manual Embedded management

18.1.9 Auto discovery

Apollo supports auto discovery of each FRU that is plugged in and reports its inventory to the CLI
and/or external management system. Currently, ST supports discovery for pluggable FRUs that have a
CPU and/or pluggable cards whose location is known, such as fan units. Inventory information can be
retrieved before configuration. Managed shelves (subtending and/or passive with controller card) are
also discovered.
An unassigned slot behaves as follows:
 New inserted FRU is discovered and reported to the external management system.
 Any FRU insertion into the slot is detected.
 Inserted I/O card:
 Performs power up BIT.
 Inventory information includes BIT status.
 Upon BIT completion the card is set to consume minimal power.
Configured slot behavior:
 Empty slot generates "unequipped" alarm.
 Insertion of a matched FRU clears the alarm.
 Insertion of a mismatched FRU causes a "mismatch" alarm.
 Insertion of a mismatched transceiver causes a "mismatch" alarm associated to its transmission
entity.
 Insertion of an I/O card:
 Performs power up BIT.
 Periodically Performs background BIT.

18.2 Fault management

Changes in the NE are notified via the following notification types:
 Alarm notifications requiring operator involvement, reported concurrently in three different
methods:
 Automatic output message to external management system after stabilization period.
 Visual indicator in the NE.
 Audible/visible indicators at central office under control of the NE.
Typical alarm examples include: LOS, LOF, Equipment Out, Equipment Mismatch, and 15-min
threshold-crossing alert (TCA) reports.
 Non-alarm notifications informing the operator of a change in the system. These notifications
are sent as automatic output messages to the external management system without waiting for a
stabilization period.
Typical examples include a protection switching event or a 1-day TCA.
Both alarm and non-alarm notifications are reported to STMS and also via SNMP to external
management systems using an SNMP agent.

Ribbon Communications Inc. Proprietary 18-8

 Apollo Reference Manual Embedded management

Alarms generated by Apollo are classified as:

 Transmission: Alarms associated with a malfunction of any transmission path. The Apollo
supports a full set of alarms in compliance with applicable standards.
 Communication: Alarms associated with the procedures and/or processes required to convey
information from one point to another.
 Timing: Alarms associated with a malfunction of any Apollo timing source.
 Equipment: Alarms associated with any hardware malfunction.
 Environment: Alarms mainly associated with a condition relating to an enclosure in which the
equipment resides. Alarm types in this category are: temperature too high, low power in the power
supply board, etc.
 Processing error: Alarms mainly associated with a software or processing fault.
 SW processing: Alarms associated the same as processing error alarms but related to SW.
 QoS: Alarms mainly associated with degradation in the QoS. The causes may be: Excessive
Response Time, Exceeded Queue Size, reduced BW, Excessive Retransmission Rate, Threshold
Crossed, Degraded Performance, and Congestion.
A system of severity levels is used to prioritize the alarms in the order of urgency:
 Critical: Always requires immediate attention.
 Major: Gives notice that attention is required, but does not require attention outside normal
working hours.
 Minor: Does not require attention after normal hours.
 Warning: Malfunction warning or unreleased maintenance action.
 Non-alarmed: Extended severity for transient condition reports (such as protection switch events,
timing-switching, or 1-day TCA reports).
In addition to the management interfaces listed previously, some additional optional means can be
provided for alarms control and display:
 Terminal displays, including LEDs that indicate malfunctions of specific plug-in units or
transmission paths
 Alarm contacts, delivering critical, major, and minor alarm indications to the station alarm bus
 Four input alarm and four output alarm dry contacts, to be explicitly configured by the user. By
default there is no configuration of external dry contacts.
 Rack alarm buzzer with station acknowledgment mechanism.
 Alarm server, delivering network aggregated alarms from LightSOFT to the operator's Central
Monitoring Station (CMS).
 Alarm inputs from in-station devices (such as security sensors, fire detectors, external monitoring
equipment) and other in-station telecommunication equipment (like flexible multiplexers and
DWDM units).
Each managed entity (such as a card, port, or interface) that supports fault management functionality
works with a severity profile, a list of all alarm and non-alarm notifications that can be suppressed.
Using the severity profile, a user can modify the severity of each alarm and suppress reporting of
selected alarm or non-alarm reports.

Ribbon Communications Inc. Proprietary 18-9

 Apollo Reference Manual Embedded management

Apollo NEs also provide log functionality:

 All reported alarms are logged to a persistent NE alarm log.
 All non-alarm reports (if so configured in the severity profile) are logged to a persistent NE event
log.
There are several levels of alarm report suppression:
 Per specific alarm: Suppressed by changing the reporting attribute of the specific alarm in a
specific severity profile.
 Per managed entity: Suppressed by changing the alarm master mask attribute value.
 AINS: Suppressed until getting into service for the first time (future).
Current reported alarms can be retrieved via CLI, STMS, and SNMP requests. In addition, CLI and
STMS allow retrieval of reported and non-reported alarm conditions per managed entity.

18.3 Configuration management

The Apollo platform, provides enhanced configuration features, including
 User configuration
 Implicit configuration
 Pre-planned and manual configuration
 Transactions
 Rollback operations
Configuration is performed using the CLI and/or STMS. The configuration features are described in the
following sections.

18.3.1 Apollo platforms minimal configuration

The Apollo requires minimal NE configurations in order to operate, including equipment entities and
definition of NE attributes, such as default password of newly defined users. The minimal equipment
configuration is required only for Apollo service shelves (OPT9624 and OPT9608). The shelf that is
controlled by external management is named Main shelf and must have the following minimal installed
FRUs:
 1 x RCP controller card
 2 x PFM power supply units
 1 x FCM cooling unit in the FCM slot
 1 x CEM card (for OPT9624 only)

NOTE: In order to comply with availability requirements it is highly recommended to have

redundancy of RCP and PFM.

The above minimal equipment configuration is also applicable for subtending service shelves.
The Apollo NEs support live insertion and extraction of equipment without affecting traffic.

Ribbon Communications Inc. Proprietary 18-10

 Apollo Reference Manual Embedded management

18.3.2 User configuration

As part of Apollo platforms installation, the user is required to configure parameters for I/O and fabric
card slots. The common equipment cards like controller, power supply, and fan cards are implicitly
configured by the NE. For a detailed description of this feature, see Implicit Configuration.
In addition, there are other instances when the user must configure equipment entities, for example,
cards with unique multiple configuration of the supported entities. User configuration is also required in
Pre-planned and Manual Configuration.

18.3.3 Implicit configuration

Implicit configuration is the ability of an NE to configure equipment and/or supported entities without
operator intervention. This feature is supported by the Apollo.
Implicit configuration is applied to:
 Main service shelf with minimal equipment configuration (the shelf itself, RCP, fan units, and
PFMs)
 Cards with unique configuration of supported entities
 Ports with unique configuration of their supported entities
Implicit configuration of equipment: As part of implicit configuration, the main shelf configures the
minimal equipment configuration, including its RCP, fan unit (FCM) and power supplies (PFMs) to their
default values. In addition, the main shelf configures RCPs of subtending shelves to their default
values, and controller cards of subtending passive shelves.
Cards with unique configuration of supported entities: The user sets the card type and all ports,
and supported entities are implicitly configured to their default values. Examples are all the cards
belonging to passive optics cards (e.g., DCFs, splitters/couplers), amplifiers, some ports in Add
ROADMs, and service cards having non-FRU transceivers. This category also includes cards with
multiple configurations. In this case, the user sets the card type, and the card is configured to its default
values; the supported entities are not configured. For example, client cards, line cards, transponders.
Ports with unique configuration of supported entities: The user configures the port type, and all
supported entities are implicitly configured. For example, service cards, data cards, and ROADMs.

18.3.4 Preplanned and manual configuration

Apollo platforms support preplanned and manual configuration initiated by the user. The following
modes are supported:
 Manual configuration, performed by a single command from the CLI.
 Transfer of a configuration file to the Apollo NE to be saved and executed, immediately or later.
 Performing the configuration by the user sending command by commend from external
management.
As part of manual configuration, the user can perform the following activities:
 Assigning an ID number to subtending service and passive shelves.
 Creation and configuration an empty slot.
 Deletion of a populated slot and assignment to another FRU.
 Modification of a populated slot to another FRU type.

Ribbon Communications Inc. Proprietary 18-11

 Apollo Reference Manual Embedded management

The user can configure multiple entities of the same type, using the Copy command via the CLI or
STMS. For example, if the user has configured a slot, he doesn't have to repeat the changes manually
to another slot in the same or other shelves. He can use this slot as a template and copy it's
configuration to another slot. This functionality is also supported for cards and shelves of the same
type.

18.3.5 Transactions
Apollo supports transactions, enabling the user to perform several configuration activities in a single set
of commands. Transaction can be composed of a single or several changes followed by the "commit"
command. The result of a transaction can be "OK" or "Fail". Partial successful configuration is
impossible. The order of commands is not mandatory as long as all commands are part of the same
transaction.
The following are examples of successful and failed transactions:

Example 1
1. To assign on slot u2 trp10-4 and configure port 1 as otu2, use the following set of commands:
 Set chassis slot u2 phye-tr10-4 port 1 port-type otu2
2. To assign on slot u3 tr10-4 and configure port 2 as otu2, use the following set of commands:
 Set chassis slot u3 phye-tr10-4 port 2 port-type otu2
3. To define fiber connectivity between the above two ports, use the following set of commands:
 Set chassis slot u2 phye-tr10-4 port 1 fiber-connectivity internal bidirectional peer-slot u3
peer-port 2
 Commit
The result of these transactions will be: Successful transaction

Example 2
 To define fiber connectivity between two ports u2 and u3, use the following set of commands:
 Set chassis slot u2 phye-tr10-4 port 1 fiber-connectivity internal bidirectional peer-slot u3
peer-port 2
 Commit
The result of these transactions will be: Transaction fails (because the cards and ports are not
defined)

18.3.6 Rollback operations

Apollo platforms support rollback functionality. This enables the operator to load a previously committed
configuration out of the nine most recent copies of committed configurations. Rollback functionality is
used by issuing the "rollback" command, the number of the committed recent configuration, and the
"commit" command.
Rollback is used in several cases, for example:
 After a failed implicit configuration
 Failed configuration operations
 Failed XC operation
 Failed command
 Failed deletion operation

Ribbon Communications Inc. Proprietary 18-12

 Apollo Reference Manual Embedded management

18.4 Performance monitoring

Apollo as a transport system provides PM interval collection on its transport entities, such as ports and
interfaces. PM collection is applied for both L1 service cards and/or photonic cards with monitoring
points. Apollo also supports PM on the OSC-100M ports used for in-band management.
The NE collects PM information every 15 minutes, and at the end of each day, the historical PM
information from each entity. The collected information is stored in a non-volatile memory in the NE in
one zipped file per each PM interval.
The NE can store up to 95 historical PM files for 15-minute intervals and 7 historical PM files for 1-day
intervals.
Any external managed system can acquire the PM files from the NE.
PM profiles contain a list of PM threshold setting values configured for each technology. Only entities
supporting PM interval functionality can be associated with a PM profile. By default, PM is enabled.

NOTE: A future function is Apollo support of PM intervals on L2 data cards. Therefore, at

this stage, their ports have no association with a PM profile and PM is always disabled.

PM TCA reports follow transport system standards as follows:

 15-minute TCAs are reported as standing condition reports (having alarm severity types).
 1-day TCAs are reported as transient condition reports (having non-alarmed severity type).
 PM TCAs are defined in the severity profile for each technology, following the alarms and events
approach.
 Current interval and historical PM information per entity can be retrieved upon user request.
Current intervals and historical intervals have a suspect flag attribute notifying if the interval
information is reliable or not.
 The flag is enabled by configuration changes on the monitored entities (e.g., resetting counters,
PM updates).
PM for L2 data cards is supported by continuous counters collection. These counters can be configured
by the user to collect information every 2, 4, or 6 hours.

18.5 Password authentication

The Apollo platforms support the following security features:
 Authentication and password manipulation: Authentication is performed according to the user
ID and a complex password.
 User privileges: Users are explicitly granted permission to create, configure, and delete
interfaces, customers, and services. Service operators can also enable and disable interfaces and
services.
 Separate resource domains per user, down to the port level.
 System log.

Ribbon Communications Inc. Proprietary 18-13

 Apollo Reference Manual Embedded management

18.6 Fiber connectivity

Fiber connectivity provides the connectivity between ports connected by fibers or cables. Two types of
fiber connectivity are defined in the Apollo system:
 Intra (internal) connectivity: connectivity inside the NE, for example:
 Connectivity between cards residing on the same shelf
 Connectivity between a card on a service shelf (OPT9624, OPT9608) and a card in a passive
shelf (Artemis)
 Inter (external) connectivity: connectivity with NE neighbors

Fiber connectivity types

Applications that rely on fiber connectivity configuration include:

 Power control and equalization
 Diagnostic information (fiber loss, dispersion, OSNR)
 LightSOFT top-down application
 NE alarm correlation (future function)

18.6.1 Power control and equalization

Two main criteria must be met to achieve optimal results - maximum range without exceeding a given
bit error rate:
 Each component in the network must operate at its optimal design point
 The total available power must be divided equally among the optical channels (wavelengths)
These criteria are met by simultaneously applying two approaches:
 Power control, which ensures that the correct total signal power is achieved at all the relevant
points
 Equalization, which ensures that each channel receives its correct share of the total signal power
Fiber connectivity configuration defines the physical topology of the network.
Based on the topology of the WDM ports (i.e., OTS ports, OTUk ports), the NE prepares the
appropriate optical information for each one of the ports in order to achieve power and channel
equalization.

Ribbon Communications Inc. Proprietary 18-14

 Apollo Reference Manual Embedded management

The RCP card in each NE processes and controls the optical components having internal fiber
connectivity configuration. It uses the in-band communication channels (i.e., GCC or OSC) to convey
the optical information for optical components that are external fiber connected. The following figure
shows the power control and equalization in the network.

Power control and equalization

In addition, the measured signal values are processed by management which uses an advanced
algorithm to adjust power levels in the entire network in an optimal way, and to automatically
compensate for changes such as span loss over the network operational lifetime. The algorithm also
analyzes operational conditions, such as number of channels, span loss, and accumulated noise, and
the configuration parameters of the various optical components, and compares them with various user-
defined and automatically generated thresholds to determine the optimal conditions and the method
used to respond to changes.

18.6.2 Diagnostic information

Optical measurements and/or estimations are collected by the NE using the physical topology defined
via fiber connectivity. Detailed information on each optical port can be retrieved upon user request.
Optical measurements with high importance (e.g., min. power, max. power, actual span loss) are
handled as PM counters and follow the PM functionality.

Ribbon Communications Inc. Proprietary 18-15

 Apollo Reference Manual Embedded management

18.6.3 LightSOFT top-down information

LightSOFT top-down information acquires fiber connectivity configuration from the NE for NMS link
creation in trail configuration. As part of the creation of trails, in addition to XC, LightSOFT also sends
the fiber connectivity configuration to the NE.
Fiber connectivity configuration can be provided by LightSOFT, CLI users, and/or STMS, and offline via
the planning tools.

Top-down information transfer

The STMS station downloads the NE configuration and intra connectivity information to XML files, and
sends them to LightSOFT. LightSOFT exports the network topology, services, trails, and intra node
connectivity information to Planning Tools via XML. Planning Tools processes the information and the
updated information is sent back to LightSOFT, retrieved by the STMS, and updates the NE.

18.6.4 NE alarm correlation

Network alarm correlation is handled by the NMS. Apollo, as an embedded management device, should
provide an advanced fault detection and repair, and is required to report only the root cause alarms and
not the affected alarms. Fiber connectivity configuration allows the NE to provide an advanced
algorithm for NE alarm report correlation. An example of this important function is shown in the
following figure.

Alarm correlation example

Ribbon Communications Inc. Proprietary 18-16

 Apollo Reference Manual Embedded management

In case the ROADM card is reset or pulled out of its slot, the NE would normally generate a ROADM
alarm and all cards connected to the ROADM would also generate alarms. It would be very difficult for
the user to identify the problem. The alarm correlation feature ensures that only the root cause of the
failure generates an alarm, making troubleshooting much easier and more accurate.

18.6.5 Alien lambda

As part of power equalization, it is important to take into account the optical impairments of third-party
and/or non-Apollo connected lambdas.
This is achieved by explicit configuration of the optical parameters of the alien lambda. In this case,
fiber connectivity configuration is marked as external and unspecified.

Alien lambda solution

The user can use the parameters to manually configure the power control and equalization system
accordingly, so that critical optical parameters are considered by the system and power control and
equalization is maintained.

18.6.6 Fiber connectivity to external equipment

Apollo ports may be connected to test equipment and/or other families. In this case the fiber
connectivity is defined as external, but the peer port information is irrelevant. Fiber connectivity is
external and unspecified.

Ribbon Communications Inc. Proprietary 18-17

 Apollo Reference Manual Embedded management

18.7 Built-In Test (BIT)

The BIT hardware and its related software assist in the identification of any faulty card in the system.
BIT checks are performed during power up and at periodic intervals afterwards.
There are three BIT levels:
 BIT failed: Card devices don’t work (or partially work); service is affected.
 BIT degraded: Service might be somewhat affected (for example, higher degree of BER).
 BIT slightly degraded: Service not affected but there is some unusual or non-optimal behavior
(for example, a heated device). This level usually doesn’t require immediate technician attention.
Unsuccessful BIT raises an alarm according to the BIT level, including a list of all associated error
codes and some explanation.
Based on this information, the technician decides how to fix the problem.

18.8 Ease of use

Apollo embedded management provides enhanced features that makes operation of the system very
simple, easy, and user-friendly. These features include:
 The user assigns a card or configures a port; the NE implicitly configures the supported entities
and updates the STMS.
 The user configures a port number and port type; the NE implicitly configures the port layers.
 Apollo platforms support plug-and-play. Using auto-discovery, each plugged FRU is detected and
its inventory reported.
 Fiber connectivity supports several applications:
 Power equalization.
 Diagnostic.
 Alarm correlation (future).
 Unified planning tools support:
 Network resources optimization and simplified operation.
 Download of NE configuration, intra-connectivity, and network topology.
 Simplified network expansion.

Ribbon Communications Inc. Proprietary 18-18

19 Maintenance
The Apollo family is a fully redundant all-in-one system that eliminates and replaces interconnections
and cables with a few ultra-reliable optical connections in a self-contained integrated package. As a
result, the Apollo inherently provides high reliability.
Operating features and benefits of the Apollo include:
 Redundancy of all subsystems and optional switchover to protection, offering the operator
uninterrupted service.
 Comprehensive alarms system, detecting and reporting transmission and equipment malfunctions.
 Loopback capabilities on the transmission interfaces and a sophisticated BIT feature facilitating
quick and accurate fault location, so minimizing mean time to repair (MTTR).
 Maintenance configuration functions controlled by the management system.

NOTE: All installation instructions, technical specifications, restrictions, and safety

warnings are provided in the Apollo Installation and Maintenance Manuals. See these
manuals for specific instructions before beginning any Apollo platform installation.

19.1 Maintenance operations

The NE generates event notifications to any external management system of maintenance activities in
the NE. Maintenance operation can be issued on cards, ports, L1 interfaces, and protection groups.
The following sections describe these operations.

19.2 Short MTTR

Apollo features ensure a minimum MTTR, reducing the probability of service interruptions:
 Internal diagnostic capability and automatic switchover to protection equipment
 Automatic PM and BIT mechanism for fast and accurate fault isolation
 Efficient fault location at the element, card, and component levels
 Replacement of cards and modules when power is on
 Remote diagnostics activation and control by the STMS
 Remote installation of new software versions through management interfaces with minimum effect
on traffic

Ribbon Communications Inc. Proprietary 19-1

 Apollo Reference Manual Maintenance

19.3 Built-In Test (BIT)

The BIT hardware and its related software assist in the identification of any faulty card in the system.
BIT checks are performed during power up and afterwards at periodic intervals.
There are three BIT levels:
 BIT failed: Card devices don’t work (or partially work), service is affected.
 BIT degraded: Service might be somewhat affected (for example, higher degree of BER).
 BIT slightly degraded: Service not affected but there is some unusual or nonoptimal behavior (for
example, a heated device). This level usually doesn’t require immediate technician attention.
BIT outputs provide:
 Fault detection
 Maintenance alarms
 Redundancy switching
 System reset
 Management reports
On-card dedicated test circuits implement the BIT procedure under the control of an integrated software
package.
The RCP cards perform the BIT procedures on all signal paths and buses. The RCPs also monitor the
slave processors on the other NE cards by means of test messages.
A BIT program is automatically activated after the platform is switched on. It is performed for both the
initialization and normal operation phases.
BIT testing covers general tests (including card presence tests and periodic sanity checks of I/O card
processors), traffic path tests, RCP environment tests, data tests, and more. The BIT detects
traffic-affecting failures as well as failures in other system cards, including invisible failures in
nonoperating redundant cards.

19.4 Alarms system

Alarms generated by the Apollo are classified as:
 Transmission: Alarms associated with a malfunction of any transmission path. The Apollo
supports a full set of alarms in compliance with applicable standards.
 Timing: Alarms associated with a malfunction of any Apollo timing source.
 Equipment: Alarms associated with any hardware malfunction.
The network administrator assigns severity levels to each alarm type:
 Critical: Always requires immediate attention.
 Major: Gives notice that attention is required, but does not require attention outside normal
working hours.
 Minor: Does not require attention after normal hours.

Ribbon Communications Inc. Proprietary 19-2

 Apollo Reference Manual Maintenance

In addition to the management interfaces listed previously, additional optional means can be provided
for alarms control and display:
 Local displays, including LEDs that indicate malfunctions of specific plug-in units or transmission
paths
 Alarm contacts, delivering critical, major, and minor alarm indications to the station alarm bus
 Rack alarm buzzer with station acknowledgment mechanism
 Alarm server, delivering network aggregated alarms from LightSOFT to the operator's Central
Monitoring Station (CMS)
 Alarm inputs from in-station devices (such as security sensors, fire detectors, external monitoring
equipment) and other in-station telecommunications equipment (like flexible multiplexers and
DWDM units)

19.5 Troubleshooting
In the event of an alarm, troubleshooting procedures are used to determine the severity and location of
the problem and the appropriate alarm-clearing action.
Alarms are handled first by severity and then by type. In order of priority, alarm types are:
 Equipment
 Transmission
 Timing
Each card is a standalone unit. By adopting our modular system concept, the customer's planning and
maintenance personnel achieve flexible and efficient operation. By following a simple procedure,
maintenance personnel can quickly replace faulty cards or other assemblies. Faulty units are then sent
for repair to the assigned Customer Support Center. The easy maintenance concept of Apollo allows
the user to perform these repairs and test actions:
 Connecting/disconnecting cable fibers to/from the Apollo
 Removing/inserting any cards in Apollo cards cage when power is on
 Connecting/disconnecting power cable(s) to/from the system
 Performing system test procedures
 Removing/inserting I/O modules

Ribbon Communications Inc. Proprietary 19-3