NT8E65AP 323-1201-103

SONET Transmission Products

S/DMS TransportNode
OC-48 NE
Signal Flow and Protection Switching
Descriptions
Standard Rel 16.1 February 2001

What’s inside...
Signal flow
OC-48 transport protection
Matched nodes on GR-1230 Rings
DS3 and STS-1 tributary protection
OC-3, STM-1J, STS-12, and OC-12 tributary protection
OPTera Packet Edge System protection
OPC protection
ESI protection
User-initiated protection-switching features
Extra traffic
Protection exerciser
Path trace and section trace
Copyright  1990–2001 Nortel Networks, All Rights Reserved

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to
its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third
parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except
as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Nortel Networks, the Nortel Networks logo, the Globemark, How the World Shares Ideas, Unified Networks, OPTera, and S/DMS
TransportNode are trademarks of Nortel Networks.

UNIX is a trademark of X/Open Company Limited.

Printed in Canada
 iii

Contents 0
About this document ix
Renaming guidelines x
Roadmap xi

Signal flow 1-1

Single-shelf 1+1, 1:1, and 0:1 terminal configurations 1-2
Transmitting into fiber (1+1, 1:1, and 0:1 single shelf) 1-3
Receiving from fiber (1+1, 1:1, and 0:1 single shelf) 1-6
Multishelf 1:N terminal configurations 1-7
Transmitting into the fiber of a working channel 1-10
Receiving from the fiber of a working channel 1-12
Signal flow in the protection loop (on working shelves) 1-13
Signal flow on the protection shelf 1-13
Signal flow on the protection shelf for extra traffic 1-14
Managing STS connections in linear systems (timeslot assignment) 1-14
Defining the linear configurations 1-15
Concatenated payloads (STS-3c and STS-12c) 1-15
SDH payloads (STM-1o and STM-4o) 1-15
In-service channel rollover 1-16
Ring ADM shelf configuration 1-18
Transmitting into fiber (ring ADM node) 1-18
Receiving from fiber (ring ADM node) 1-23
Defining the ring configuration 1-24
Managing STS connections in a GR-1230 Ring (timeslot assignment) 1-27
Concatenated payloads (STS-3c and STS-12c) 1-27
SDH payloads (STM-1J, STM-1o and STM-4o) 1-27
Defining STS connections 1-28
OC-48 regenerator/optical amplifier shelf 1-32
Non-route-diverse regenerators supporting 1+1 and 1:1 systems 1-33
Non-route-diverse regenerators supporting multishelf 1:N systems 1-33
Route-diverse regenerators supporting a single 1+1, 1:1, or 0:1 system 1-34
Route-diverse regenerators supporting a single GR-1230 Ring system 1-35
Route-diverse regenerators supporting two systems 1-35
Regenerator application 1-35
Optical amplifier application 1-38
Unidirectional services 1-41
Linear systems 1-41
GR-1230 Rings 1-45
Signal synchronization (linear terminals) 1-50

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
iv Contents

In the OC-48 receive direction 1-52

In the OC-48 transmit direction 1-52
Synchronization on the 1:N protection loop 1-53
Signal synchronization (ring ADM nodes) 1-55
In the OC-48 receive direction 1-56
In the OC-48 transmit direction 1-57
Passthrough traffic 1-57
OAM&P communications 1-57
Data communications using the SONET line 1-58
Data communications using CNet 1-59
Data communications using Ethernet 1-60

OC-48 transport protection 2-1

Switch initiation 2-3
Switch times 2-3
Definitions 2-5
Line switching 2-5
Path switching 2-5
Switching modes 2-6
1+1 protection (non-revertive) 2-8
1:1 protection (single shelf) 2-10
Multishelf 1:N protection (revertive) 2-12
Protection-switching operation 2-12
K-byte signaling in a 1:N system 2-17
Protection loop 2-19
Protection oscillation control 2-19
Orderwire protection in 1:N multishelf systems 2-21
Data communications protection in multishelf 1:N systems 2-21
Protection in an OC-48 GR-1230 Ring (revertive) 2-24
Normal operation 2-25
Protected operation 2-25
Extra traffic on a ring 2-33

Matched nodes on GR-1230 Rings 3-1

Overview 3-1
Tributaries 3-4
Protection scheme 3-4
STS connection rates 3-4
Gateway nodes 3-5
OPC Connection Manager 3-5
Drop-and-continue on working (DCW) 3-5
Normal operation 3-5
Provisioning matched-node gateways 3-9
Protected operation 3-10
Drop-and-continue on protection (DCP) 3-14
Timeslot usage 3-17
Survivability with DCW and DCP 3-17
Using DCW and DCP in combination 3-21
STS connections 3-25
Link failures 3-25

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Contents v

Node failures and node isolation 3-28

Opposite-side routing 3-31

DS3 and STS-1 tributary protection 4-1

Switch initiation 4-3
Switch times 4-3
Path switching 4-3
DS3 and STS-1 tributary protection signal flow 4-5
In the DS3 or STS-1 receive direction 4-5
In the DS3 or STS-1 transmit direction 4-5
DS3 and STS-1 protection exerciser 4-6

OC-3, STM-1J, STS-12, and OC-12 tributary protection 5-1

Definitions 5-1
Line switching 5-1
Path switching over matched-nodes 5-1
1+1 protection on OC-3, STM-1J, STS-12, and OC-12 tributaries 5-3
Switching modes 5-6
Availability of protection switching 5-8
Switch initiation 5-8
System-initiated protection switches 5-8
User-initiated protection switches 5-9
Switch times 5-9

OPTera Packet Edge System protection 6-1

Protection switching 6-1
Layer 1 protection 6-1
Layer 2 protection 6-1
Point-to-point connections 6-2
Protected connections 6-4
Unprotected connections 6-5
Shared ring 6-5

OPC protection 7-1

Provisioning OC-48 configurations and STS connections using the backup OPC 7-2

ESI protection 8-1

Equipment protection switching 8-1
Timing reference protection switching 8-2

User-initiated protection-switching features 9-1

DS3 and STS-1 protection-switching commands 9-1
Lockout 9-2
Forced switch 9-2
Manual switch 9-2
Wait to restore 9-2
Priority selection 9-3
DS3 and STS-1 loopback 9-3
DS3 and STS-1 protection-switching hierarchy 9-5
OC-3 and OC-12 protection-switch commands 9-5

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
vi Contents

Lockout 9-6
Forced switch 9-7
Manual switch 9-7
OC-3, STS-12, and OC-12 protection-switching hierarchy 9-8
STM-1J protection-switch commands 9-9
Lockout 9-9
Forced switch 9-10
Wait to restore 9-10
Detection guard time 9-11
Recovery guard time 9-11
Response verification time 9-11
STM-1J protection-switching hierarchy 9-12
OC-48 protection-switch commands for linear systems 9-13
Lockout 9-13
Forced switch 9-13
Manual switch 9-13
Wait to restore 9-14
OC-48 protection-switching hierarchy for linear systems 9-14
Protection oscillation control in single-shelf 1:1 and multishelf 1:N systems (extended
wait to restore) 9-16
Protection switch interactions 9-17
Extra traffic 9-18
Alarms and logs 9-18
OC-48 protection-switching commands for GR-1230 Rings 9-18
Lockout of working and lockout of protection 9-18
Forced switch 9-19
Manual switch 9-20
Wait to restore 9-20
OC-48 protection-switching hierarchy for GR-1230 Rings 9-21
Matched-nodes protection-switch commands 9-21
Lockout of protection 9-21
Forced switch 9-22
Manual switch 9-22
Wait to restore 9-22
Matched-nodes protection-switching hierarchy for GR-1230 Rings 9-23

Extra traffic 10-1

Extra traffic on a linear 1:N protection shelf 10-1
Unidirectional and bidirectional extra traffic 10-1
Low-priority and high-priority extra traffic 10-3
Extra traffic operation 10-4
Extra traffic on GR-1230 Rings 10-5

Protection exerciser 11-1

DS3 and STS-1 exerciser tests 11-3
OC-3, STS-12, and OC-12 exerciser tests 11-6
OC-48 exerciser tests 11-7
Exerciser bridge test (1+1 and 1:1 systems) 11-7
Exerciser run sequence 11-8
Exerciser bridge test (multishelf 1:N configurations) 11-10

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Contents vii

The exerciser and 1:N extra traffic 11-10

Exerciser run sequence 11-11
Exerciser bridge test (GR-1230 Ring configurations) 11-13
Exerciser alarms and logs 11-15
Exerciser limitations 11-17

Path trace and section trace 12-1

Path trace 12-1
Section trace 12-3

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
viii Contents

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 ix

About this document 0

This document provides details on the signal flow and the protection switching
architectures and mechanisms involved in the OC-48 network element.

Topics covered include general concepts such as:

• line switching and optical line protection schemes for 1+1, 1:1, multishelf
1:N, and GR-1230 Ring configurations
• matched-node path level protection for GR-1230 Rings
• DS3, STS-1, OC-3, STM-1J, STS-12, and OC-12 tributary protection
• layer 2 protection for OPTera Packet Edge System (formerly iPT1000)
tributaries
• maintenance features such as:
— lockouts
— user-initiated manual and forced switches
— loopbacks
— the protection exerciser
— path-trace and section trace
The intended audience for this document includes:
• planners
• system lineup and test personnel (SLAT)
• provisioners
• network administrators
• transmission standards engineers
• maintenance personnel
If you need technical assistance, contact your next level of support or Nortel
Networks according to About the OC-48 NE Library, 323-1201-090.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
x About this document

Renaming guidelines
iPT1000
OPTera Packet Edge System (or the shortened version, Packet Edge) was
previously known as interWAN Packet Transport (iPT).

OPTera Packet Edge System tributary was previously known as iPT1000

tributary.

The OPTera Packet Edge System circuit pack used by the OC-48 network
element is the 2x1000SX circuit pack. 2x1000SX circuit pack was previously
known as iPT1000 circuit pack.

In the user interfaces, except for the Transaction Language 1 (TL1) interface,
the parameter used to query information for the OPTera Packet Edge System
remains iPTGE.
OC-3 Express as well as other Express versions
OPTera Metro 3000 Series Multiservice Platform (or the shortened version,
OPTera Metro 3000 Series) was previously known as the group of Express
products which included OC-3 Express (or Express MX), OC-12 Express (or
Express HX) and OC-48 Express (or Express GX).

The Optera Metro 3000 Series now includes: OPTera Metro 3100, OPTera
Metro 3300, OPTera Metro 3400, and OPTera Metro 3500.
Integrated Network Management (INM) Broadband
Preside Applications Platform was previously known as Integrated Network
Management (INM) Broadband.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 About this document xi

Roadmap
F5732-nsm_R16

Operating, Supporting
Planning Installing and Commissioning Administrating, Maintaining Documentation
an maintaining an and Testing an and an for the
OC-48 Network OC-48 Network OC-48 Network Provisioning an OC-48 Network OC-48 Library
OC-48 Network

OC-3/OC-12
NE TBM
Volume 1 Volume 2 Volume 3 Volume 4 Volume 5

System Installation Commissioning User Interfaces Network Optical

Description (100) Procedures (201) Procedures (220) Description (301) Surveillance Networks
Procedures (510) Applications
Software Feature Site Testing System
Common Performance
Description (101) Procedures (221) Administration
Procedures (846) Monitoring
Procedures (302)
Circuit Pack Procedures (520)
List of System Testing Software
Descriptions (102) Trouble Clearing
Terms (850) Procedures (222) Administration OPTera Metro
and 3000 Series
Signal Flow and Procedures (303)
System Alarm Reference
Protection Expansion Data Guide (542)
Switching Procedures (224) Administration
Descriptions (103) Procedures (304) Alarm Clearing
Procedures (543) OC-192 NE
Alarms and Provisioning
Surveillance and Operations Recovery
Description (104) Procedures (310) Procedures (545)
Performance Protection Multiservice
Routine
Monitoring Switching MOA
Maintenance
Description (105) Procedures (311) Procedures (546)
System Module
Applications Replacement
Description (150) SONET
Procedures (547)
Radio 4/40
Ordering
Log Report
Information (151)
Manual (840)
Technical
Specifications Preside
(180)
TL1 Interface
Description (190)

Supporting Documentation for Signal Flow and Protection Switching Descriptions (103)
· About the OC-48 NE Library, 323-1201-090 · System Administration Procedures, 323-1201-302
· System Description, 323-1201-100 · Provisioning and Operations Procedures, 323-1201-310
· Alarms and Surveillance Description, 323-1201-104 · Protection Switching Procedures, 323-1201-311
· Technical Specifications, 323-1201-180 · Alarm Clearing Procedures, 323-1201-543
· TL1 Interface Description, 323-1201-190 · Module Replacement Procedures, 323-1201-547
· Commissioning Procedures, 323-1201-220 · Log Report Manual, 323-1201-840
· System Testing Procedures, 323-1201-222

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
xii About this document

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 1-1

Signal flow 1-
This chapter describes the signal flow for the OC-48 network element
configurations. These configurations can be any of the following types:
• single-shelf OC-48 terminals configured for 1+1 and 1:1 protection
schemes
• single-shelf OC-48 terminals with unprotected 0:1 OC-48 transport
• multishelf OC-48 terminals configured for 1:N protection with or without
extra traffic on the protection channel where N is less than or equal to 11
• OC-48 terminal shelves configured for use in a GR-1230 Ring
• OC-48 regenerator/optical amplifier shelves used as regenerators
configured for either route diversity or non-route diversity
• OC-48 regenerator/optical amplifier shelves equipped with OC-48 high
performance transmitter, OC-48 optical amplifier, or OC-48 bidirectional
1533/1557 nm optical line amplifier circuit packs
In linear systems, the OC-48 terminal shelves function as the end points, or
terminals, in a point-to-point topology. The SONET standard classifies these
shelves as line-terminating equipment (LTE).

In ring applications, the OC-48 terminal shelves function as add-drop

multiplexer (ADM) nodes in the ring. The SONET standard classifies these
nodes as line-terminating equipment.

OC-48 regenerator/optical amplifier shelves configured as regenerators

provide intelligent regeneration of OC-48 signals between terminals or
add-drop multiplexer nodes. SONET classifies these regenerator shelves as
section-terminating equipment (STE).

OC-48 regenerator/optical amplifier shelves can contain up to eight OC-48

high performance transmitter, OC-48 optical amplifier, or OC-48 bidirectional
1533/1557 nm optical line amplifier circuit packs. These circuit packs amplify
an OC-48 signal to extend the reach of the signal before regeneration. They
cannot access the SONET overhead and are therefore neither

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-2 Signal flow

section-terminating equipment nor line-terminating equipment. As an option,

OC-48 terminal shelves can support up to two OC-48 high performance
transmitter or OC-48 optical amplifier circuit packs.

Each configuration described in this chapter is supported by a functional block

diagram. Any signal going into the shelf is considered the receive (Rx)
direction and any signal going out of the shelf is considered the transmit (Tx)
direction.

Single-shelf 1+1, 1:1, and 0:1 terminal configurations

The single-shelf 1+1, 1:1, and 0:1 configurations can accommodate, on a
per-quadrant basis, several tributary types, from DS3, STS-1, OC-3, STM-1J,
STS-12, and OC-12, for a maximum capacity equal to 48 STS-1 signals.
Linear systems do not support STM-1J or OPTera Packet Edge System
(formerly iPT1000) tributaries.

You can mix DS3 mappers, STS-1 interfaces, and half-height OC-3 interfaces
(NT8E08) in the same quadrant. You cannot mix double-width OC-3
interfaces (NT7E01), STS-12 interfaces, or OC-12 interfaces with any other
tributary types in the same quadrant. For example, an OC-48 terminal shelf
could have quadrant 1 equipped with a mix of DS3 mappers and half-height
OC-3 interfaces (NT7E08), quadrant 2 equipped with double-width OC-3
interfaces (NT7E01), quadrant 3 equipped with a mix of DS3 mappers and
STS-1 interfaces, and quadrant 4 equipped with OC-12 interfaces.

Figure 1-1 shows the labeling of the signals. All signals going into the OC-48
terminal shelf are labeled receive (Rx), and all signals going out of the shelf
are labeled transmit (Tx).

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-3

Figure 1-1
OC-48 signal labeling in a 1+1, 1:1, or 0:1 system
F0568_R12

OC-3 or OC-12 OC-3 or OC-12

terminal or ADM terminal or ADM

Rx Tx Rx Tx

DS3 or DS3 or
STS-1 Tx Rx Tx Rx STS-1
Rx Tx Rx Tx Rx Tx
DS3 or LTE Regenerator LTE DS3 or
STS-1 Tx Rx STS-1
Tx Rx Tx Rx

OC-48 OC-48 OC-48

terminal regenerator/optical terminal
shelf amplifier shelf shelf

Transmitting into fiber (1+1, 1:1, and 0:1 single shelf)

An OC-48 shelf transmits DS3, STS-1, OC-3, OC-12, or STS-12 signals into
fiber by converting the original signals to STS-1 and then combining the STS-1
signals into an OC-48 signal for transmission.
DS3 and STS-1 signals
In the optical transmit direction, added DS3 signals coming from the
termination panel are connected to the interface port circuit packs. The
interface ports then route the signals to the DS3 mappers, which map them into
an STS-1 signal format and send them on to the OC-48 or STS-48 transmit
interface. The STS-48 transmit interface is used in conjunction with an OC-48
high performance transmitter circuit pack.

When STS-1 tributaries are used, the STS-1 signals coming from the
termination panel are connected to the interface port circuit packs. The
interface ports then route the signals to the STS-1 interfaces, where the STS-1
signals are mapped and sent to the OC-48 or STS-48 transmit interface. For a
signal flow diagram from DS3 and STS-1 tributaries to the OC-48 transport
circuit pack groups, see Figure 1-2.
STS-48 or OC-48 signal
The OC-48 or STS-48 transmit interface then multiplexes the 48 STS-1 signals
into one STS-48, adds transport overhead, and scrambles the signal. The
OC-48 transmit interface also converts the STS-48 electrical signal into an

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-4 Signal flow

OC-48 optical signal. The signal is then either transmitted over the fiber from
the OC-48 transmit interface or over coaxial cable to the OC-48 high
performance transmitter from the STS-48 transmit interface.

Figure 1-2 also illustrates how an OC-48 terminal can be equipped with OC-48
high performance transmitters or OC-48 optical amplifiers. When equipped
with OC-48 high performance transmitters, STS-48 transmit interfaces must
be installed in place of OC-48 transmit interfaces in the G1 and G2 transport
circuit pack groups.

The STS-48 signal produced by the STS-48 transmit interface is transmitted

along a coaxial cable to the OC-48 high performance transmitter. The OC-48
high performance transmitter converts the STS-48 signal into an OC-48 optical
signal and amplifies it before transmission. The OC-48 high performance
transmitter outputs a more powerful signal than the OC-48 transmit interface,
thus increasing the range of the signal.

When an OC-48 terminal is equipped with OC-48 optical amplifiers, each

OC-48 optical amplifier is connected to an OC-48 transmit interface by way of
a fiber patchcord. The OC-48 signal produced by the OC-48 transmit interface
travels over the optical patchcord to the OC-48 optical amplifier. The OC-48
optical amplifier then amplifies the signal and transmits it over the transmit
fiber, thereby extending the range of the signal.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-5

Figure 1-2
Traffic signal flow for 1+1, 1:1, or 0:1 systems (DS3 and STS-1 tributaries)
F0069_R15

DS3/STS-1
termination
panel
DS3
or Transport
STS-1 overhead
1 to 24 DS3
Interface mappers
ports or
STS-1
interfaces
1 to 8 STS-48 or OC-48 high OC-48
OC-48 performance
transmit transmitter Tx G1
interface or optical
Switcher (Note) amplifier
1
OC-48
DS3 OC-48
mapper OC-48 Rx G1
demultiplexer receive
protection interface
Switch
controller STS-1
interface OC-48
protection STS-48 or OC-48 high
OC-48 performance Tx G2
transmit transmitter
Switcher interface or optical
2 (Note) amplifier
DS3
or OC-48
STS-1 OC-48 Rx G2
OC-48
25-48 demultiplexer receive
DS3 interface
Interface mappers
ports or
STS-1 FW-0069 (R15)
interfaces
9 to 16

Note 1: The OC-48 optical amplifier requires the OC-48 transmit interface to provide its optical input.
When the OC-48 high performance transmitter is used, the STS-48 transmit interface provides its
electrical STS-48 input. If neither the OC-48 optical amplifier nor the OC-48 high performance
transmitter is used, the OC-48 transmit interface connects directly to the transmit fiber.

Note 2: A 0:1 system does not include the OC-48 G2 circuit packs.

OC-3, OC-12, and STS-12 tributaries

If the OC-48 shelf is equipped with OC-3 or OC-12 tributaries (one or more
quadrants equipped with OC-3 or OC-12 interfaces), the incoming OC-3 or
OC-12 signal is received on the OC-3 or OC-12 interface circuit pack of the
OC-48 shelf. The OC-3 or OC-12 interface circuit pack converts the received
OC-3 or OC-12 optical signal into an electrical STS-3 or STS-12 signal. This
STS-3 or STS-12 signal is then demultiplexed, framed, and descrambled into
3 or 12 STS-1 signals that are synchronized to the system clock after the
transport overhead has been extracted.

If STS-12 interfaces are used instead of OC-12 interfaces, the processing of the
STS-12 electrical signal is the same.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-6 Signal flow

The STS-1 signals from the tributaries are then sent to the OC-48 or STS-48
transmit interface, which processes the signals for transmission as described
for DS3 or STS-1 tributaries. For a signal flow diagram from OC-3, STS-12,
and OC-12 tributaries to the OC-48 transport circuit pack groups, see
Figure 1-3.

Figure 1-3
OC-48 terminal shelf equipped with OC-3, STS-12, and OC-12 tributaries—functional block
diagram
F0069_R12

OC-3
interface OC-48
1 Tx G1

OC-3,
STS-12, OC-3 OC-48
OC-48
and OC-12 interface Demux
2 Rx G1
tributaries G1
from an
OC-48 shelf
or from an OC-12 OC-48
OC-3 or interface Tx G2
OC-12 TBM 3
shelf
OC-48 OC-48
STS-12 Demux Rx G2
interface G2
4

Receiving from fiber (1+1, 1:1, and 0:1 single shelf)

In the optical receive direction, the OC-48 receive interface circuit pack
converts the received OC-48 optical signal into an STS-48 electrical signal.

The STS-48 signal is then sent to the OC-48 demultiplexer, framed,

descrambled, and demultiplexed into 48 STS-1 signals that are synchronized
to the system clock after the transport overhead has been extracted. The STS-1
signals are then dropped to the tributaries.
DS3 and STS-1 signals
For DS3 tributaries, the STS-1 signals to be dropped are fed from the
demultiplexer to the corresponding DS3 mapper, where the DS3 signals are
extracted from the STS-1 SONET format. Then, the DS3 signals are routed
through the interface port circuit packs. Finally, the DS3 signals are sent to the
termination panel.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-7

If STS-1 tributaries are used, the STS-1 signals are fed to the corresponding
STS-1 interface circuit pack where the STS-1 signals are framed and
scrambled. Then, the STS-1 signals are routed through the interface port
circuit packs and then sent to the termination panel. For a signal flow diagram
from the OC-48 transport circuit pack groups to the DS3 and STS-1 tributaries,
see Figure 1-2 on page 1-5.
OC-3, OC-12, and STS-12 tributaries
When the OC-48 shelf is equipped with OC-3 or OC-12 tributaries (one or
more quadrants equipped with OC-3 or OC-12 interfaces), the STS-1 signals
from the demultiplexer are received by the OC-3 or OC-12 interface circuit
pack, which multiplexes the 3 or 12 STS-1 signals into an electrical STS-3 or
STS-12, adds transport overhead, and then scrambles and converts the STS-3
or STS-12 signal into an OC-3 or OC-12 optical signal for transmission over
the OC-3 or OC-12 line.

If STS-12 interfaces are used instead of OC-12 interfaces, the STS-1 signals
are then received by the STS-12 interface, which multiplexes 12 STS-1 signals
into an STS-12 signal, adds transport overhead, and scrambles it for
transmission. For a signal flow diagram from the OC-48 transport circuit pack
groups to the OC-3, STS-12, and OC-12 tributaries, see
Figure 1-3 on page 1-6.

Multishelf 1:N terminal configurations

The 1:N configuration consists of a group of OC-48 single-shelf network
elements which share the same protection channel (fibers). There can be up to
11 working channels for the one protection channel. The set of working and
protection channels at a terminal site is called a protection group.

Note: STM-1J and OPTera Packet Edge System (Packet Edge) tributaries
are not supported on linear systems.

Physically, the 1:N configuration consists of N+1 OC-48 terminal shelves at

each terminating end of the channel: one shelf for each working channel
(called working shelves) and one for the protection channel (called the
protection shelf). A 1:1 protection configuration can use two shelves in certain
applications, such as when extra traffic is carried on the protection channel.

To share a common protection channel, the information contained on every

working OC-48 channel must also be routed to the protection shelf using a
dedicated channel called the protection loop. Refer to Chapter 2, “OC-48
transport protection”, for a description of the operation of the protection loop.

There are two transport interfaces on each OC-48 terminal shelf, called circuit
pack groups G1 and G2. Each circuit pack group requires a transmit interface,
receive interface, and demultiplexer.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-8 Signal flow

On each working shelf, G1 is dedicated to a working channel. G2 on each

working shelf is dedicated to the protection loop. On the protection shelf, G1
contains the optical receive interface and the protection loop transmit interface
and G2 contains the optical transmit interface and the protection loop receive
interface. Figure 1-4 illustrates the protection loop.

The working shelf can accommodate, on a per-quadrant basis, a mix of DS3,

STS-1, OC-3, STS-12, and OC-12 tributary types for a maximum capacity
equivalent to 48 STS-1 signals. You can mix DS3 mappers, STS-1 interfaces,
and half-height OC-3 interfaces (NT8E08) in the same quadrant. You cannot
mix double-width OC-3 interfaces (NT7E01), STS-12 interfaces, or OC-12
interfaces with any other tributary types in the same quadrant. For example, an
OC-48 terminal shelf could have quadrant 1 equipped with a mix of DS3
mappers and half-height OC-3 interfaces (NT7E08), quadrant 2 equipped with
double-width OC-3 interfaces (NT7E01), quadrant 3 equipped with a mix of
DS3 mappers and STS-1 interfaces, and quadrant 4 equipped with OC-12
interfaces.
Extra traffic
The protection shelf can be equipped to support extra traffic by installing
tributary interfaces, such as DS3 mappers, STS-1, OC-3, STS-12, or OC-12
interfaces, and the associated circuit packs such as switcher, switch controller,
and interface ports. For extra traffic, the shelf is equipped using the rules that
apply to the single-shelf OC-48 terminal configuration. If STS-48 connections
are used for the protection loop, the G1 OC-48 transmit interface and the G2
OC-48 receive interface are replaced, respectively, with the STS-48 transmit
interface and the STS-48 receive interface.

For 1:N systems, tributary protection is not available for STS-1 extra traffic. A
“circuit pack mismatch” alarm is raised whenever an STS-1 interface is
inserted in slot 16 of the protection shelf.

If no extra traffic is carried over the protection channel, the protection shelf
does not contain any tributary interfaces, such as DS3 mappers, STS-1, OC-3,
STS-12, or OC-12 interfaces, or circuit packs associated with DS3 and STS-1
protection such as switcher, interface carriers, and interface ports. A switch
controller is installed on the shelf for alarm monitoring of the lower half of the
shelf.

Figure 1-5 shows the labeling of the signals. All signals going into the OC-48
terminal shelf are labeled Rx (receive), and all signals going out of the shelf
are labeled Tx (transmit).

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-9

Figure 1-4
STS-48 protection loop and associated circuit packs in a 1:N (N=3) system
F1609

Slot 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Protection shelf

Slot 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Working shelf 1

Slot 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Working shelf 2

Slot 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Working shelf 3

Legend:
= STS-48 transmit I/F
= STS-48 receive I/F
= P - loop

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-10 Signal flow

Figure 1-5
OC-48 1:N (N=3) system configuration (with one regenerator site)
F1610_R13

OC-48 OC-48
1: N (N=3) 1: N (N=3)
terminal Protection Protection terminal
DS3, OC-3, STS-12, DS3, OC-3, STS-12,
or OC-12 In channel OC-48 regenerator channel or OC-12 In
Tx Rx
DS3, OC-3, STS-12, LTE LTE DS3, OC-3, STS-12,
or OC-12 Out Rx Tx or OC-12 Out
Rx Tx
(extra traffic) Tx Rx (extra traffic)
G1
Protection Channel 1 Channel 1 Protection
loop Rx Tx loop
DS3, OC-3, STS-12, DS3, OC-3, STS-12,
or OC-12 In Rx Tx Tx G2 Rx Rx Rx or OC-12 In
LTE LTE
DS3, OC-3, STS-12, DS3, OC-3, STS-12,
or OC-12 Out Tx Rx Tx Tx or OC-12 Out

DS3, OC-3, STS-12, Channel 2 DS3, OC-3, STS-12,

OC-48 regenerator Channel 2
or OC-12 In Rx Tx Rx Rx or OC-12 In
LTE
LTE
DS3, OC-3, STS-12, Rx Tx DS3, OC-3, STS-12,
or OC-12 Out Tx Rx Tx Tx or OC-12 Out
Tx G2 Rx

Channel 3 Channel 3
Rx Tx
DS3, OC-3, STS-12, DS3, OC-3, STS-12,
or OC-12 In Rx Tx Tx G1 Rx Rx Rx or OC-12 In
LTE LTE
DS3, OC-3, STS-12, DS3, OC-3, STS-12,
or OC-12 Out Tx Rx Tx Tx or OC-12 Out

Transmitting into the fiber of a working channel

DS3 and STS-1 signals
In the optical transmit direction, DS3 signals coming from the termination
panel are connected to the interface port circuit packs. The interface port
circuit packs route them to the DS3 mappers, where they are mapped into
STS-1 signals and then sent to the OC-48 and STS-48 transmit interfaces.
STS-48 transmit interfaces are used on the working channel in conjunction
with OC-48 high performance transmitters. These STS-48 transmit interfaces
are a different version than the STS-48 transmit interfaces used on the
protection loop. For an illustration of signal flow in a 1:N multishelf system,
see Figure 1-6.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-11

When STS-1 tributaries are used, the STS-1 signals coming from the
termination panel are connected to the interface port circuit packs. The
interface ports then route the signals to the STS-1 interface circuit packs,
where the STS-1 signals are mapped and sent to the OC-48 and STS-48
transmit interfaces.
STS-48 or OC-48 signal
The OC-48 or STS-48 transmit interface then multiplexes the 48 STS-1 signals
into one STS-48, adds transport overhead, and then scrambles the signal. The
OC-48 transmit interface also converts the STS-48 electrical signal into an
OC-48 optical signal. The signal is then transmitted over the fiber in the case
of the OC-48 transmit interface, or over coaxial cable to the OC-48 high
performance transmitter in the case of the STS-48 transmit interface.
Figure 1-6
Traffic signal flow for OC-48 terminals (1:N multishelf system with extra traffic)
F1611-1_R13

Site A Protection channel Site B

G1 extra traffic G1
(see Note 3)
• • Demux OC-48 Rx OC-48 Rx Demux • •
• •
• STS-48 Tx STS-48 Tx •
see see see see
Note 1 Note 2 Note 2 Note 1
• •
• OC-48 Tx OC-48 Tx •
• •
Demux STS-48 Rx STS-48 Rx Demux
G2 G2
P-Loop P-Loop
G1 G1
Channel 1
• Demux OC-48 Rx OC-48 Rx Demux •
• •
• • OC-48 Tx OC-48 Tx • •
see see see see
Note 1 Note 2 Note 2 Note 1
• •
• STS-48 Tx STS-48 Tx •
• •
• Demux STS-48 Rx STS-48 Rx Demux
G2 • • • • G2
• • • •
• • • •
G1 G1
Channel 11
• Demux OC-48 Rx OC-48 Rx Demux •
• •
• • OC-48 Tx OC-48 Tx • •
see see see see
Note 1 Note 2 Note 2 Note 1
• •
• STS-48 Tx STS-48 Tx •
• •
Demux STS-48 Rx STS-48 Rx Demux
G2 G2 Legend:
= selector (switch)
Note 1: To and from DS3, STS-1, OC-3, STS-12, or OC-12 tributaries.
Demux = demultiplexer
Note 2: DS3 mappers or STS-1 interfaces (G1 to G16 or protection) or OC-3, STS-12, or OC-12 interfaces.
Rx = receive interface
Note 3: The protection channel cannot carry STS-1 tributary traffic as extra traffic.
Tx = transmit interface

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-12 Signal flow

In a system equipped with the OC-48 high performance transmitters, each of

the working channel OC-48 transmit interfaces is replaced with an STS-48
transmit interface and an OC-48 high performance transmitter (not shown in
Figure 1-6). In a system equipped with OC-48 optical amplifiers, an OC-48
optical amplifier supplements the OC-48 transmit interface in each working
channel to amplify the signal before transmission over the OC-48 line.
OC-3, OC-12, and STS-12 tributaries
If the OC-48 shelf is equipped with OC-3 or OC-12 tributaries (one or more
quadrants equipped with OC-3 or OC-12 interfaces), the incoming OC-3 or
OC-12 signal is received on the OC-3 or OC-12 interface circuit pack of the
OC-48 shelf. The OC-3 or OC-12 interface circuit pack converts the received
OC-3 or OC-12 optical signal into an electrical STS-3 or STS-12 signal.

This STS-3 or STS-12 signal is then demultiplexed, framed, and descrambled

into 3 or 12 STS-1 signals that are synchronized to the system clock after the
transport overhead has been extracted. The STS-1 signals from the tributaries
are then sent to the OC-48 or STS-48 transmit interface, which processes the
signals for transmission as described for DS3 and STS-1 tributaries.

If STS-12 interfaces are used instead of OC-12 interfaces, the processing of the
STS-12 electrical signal is the same.

Receiving from the fiber of a working channel

In the optical receive direction, the OC-48 receive interface converts the
received OC-48 optical signal into an STS-48 electrical signal. The STS-48
signal is sent to the OC-48 demultiplexer, and then framed, descrambled, and
demultiplexed into 48 STS-1 signals that are synchronized to the system clock
after the transport overhead has been extracted. For an illustration of signal
flow in a 1:N multishelf system, see Figure 1-6.
DS3 and STS-1 signals
For DS3 tributaries, the demultiplexer feeds the STS-1 signals to the
corresponding DS3 mappers, where the DS3 signals are extracted from the
STS-1 signals. The DS3 signals are then routed through the interface port
circuit packs. Finally, the DS3 signals are sent to the termination panel.

If STS-1 tributaries are used, the STS-1 signals are fed to the corresponding
STS-1 interface where the STS-1 signals are framed and scrambled. Then, the
STS-1 signals are routed through the interface port circuit packs and then sent
to the termination panel.
OC-3, OC-12, and STS-12 tributaries
When the OC-48 shelf is equipped with OC-3 or OC-12 tributaries (one or
more quadrants equipped with OC-3 or OC-12 interfaces), the STS-1 signals
are received by the OC-3 or OC-12 interface circuit pack, which multiplexes

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-13

the 3 or 12 STS-1 signals into an electrical STS-3 or STS-12, adds transport

overhead, and then scrambles and converts the STS-3 or STS-12 signal into an
OC-3 or OC-12 optical signal for transmission.

If STS-12 interfaces are used instead of OC-12 interfaces, the STS-1 signals
are then received by the STS-12 interface, which multiplexes 12 STS-1 signals
into an STS-12 signal, adds transport overhead, and scrambles it for
transmission.

Signal flow in the protection loop (on working shelves)

The STS-48 transmit interface selects between the 48 STS-1 signals created by
the DS3 mappers and the STS-48 recovered by the STS-48 receive interface
after being passed through the demultiplexer. When the channel is not bridged
to protection, the STS-48 signal recovered by the STS-48 receive interface is
selected and transmitted to the adjacent shelf by the STS-48 transmit interface.
If the channel is bridged to protection, the STS-48 transmit interface selects the
STS-1 signals created by the tributaries. The 48 STS-1 signals are then
multiplexed into a single STS-48 signal. The STS-48 is scrambled and
transmitted to the adjacent shelf.

The STS-48 receive interface recovers the STS-48 from the adjacent shelf. The
signal is sent to the demultiplexer for monitoring purposes and then to the
STS-48 transmit interface. The STS-48 signal is then transmitted electrically
to either the next working shelf or the protection shelf.

Signal flow on the protection shelf

The OC-48 receive interface converts the received OC-48 optical signal of the
protection channel into an STS-48 electrical signal. The signal is sent to the
demultiplexer for monitoring purposes and then to the STS-48 transmit
interface. The STS-48 is then transmitted electrically to the shelf that handles
the highest-numbered (channel N) optical channel in the 1:N system.

The STS-48 receive interface recovers the STS-48 signal from the adjacent
shelf. The signal is fed to the demultiplexer for monitoring purposes, and then
to the OC-48 transmit interface. The OC-48 transmit interface adds transport
overhead, and then scrambles and converts the STS-48 electrical signal into an
OC-48 optical signal for transmission over the fiber dedicated to the protection
channel.

Note: The protection loop works using either STS-48 or OC-48 transmit
and receive interfaces or a combination of both. If adjacent terminals on the
protection loop are more than 30 m (98 ft.) apart, use OC-48 interfaces.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-14 Signal flow

Signal flow on the protection shelf for extra traffic

Transmit
With extra traffic on the protection channel, the G2 OC-48 or STS-48 transmit
interface selects the 48 STS-1 signals mapped from the tributaries (DS3
mappers or STS-1, OC-3, STS-12 or OC-12 interfaces).

The STS-1 signals are multiplexed into an STS-48 signal, transport overhead
is added, and then the signal is scrambled. If an OC-48 transmit interface is
used, it converts the STS-48 signal to an optical OC-48 signal for transmission
over the fiber dedicated to the protection channel.

If an STS-48 transmit interface is used on the protection channel, it is used in

conjunction with an OC-48 high performance transmitter circuit pack. The
OC-48 high performance transmitter converts the STS-48 signal to an OC-48
signal, then amplifies the OC-48 signal for transmission. The STS-48 transmit
interface used with an OC-48 high performance transmitter is a different
version than the STS-48 transmit interface used on the protection loop. The
OC-48 transmit interface can be connected to an OC-48 optical amplifier in
post amplifier mode in a similar arrangement to provide amplification of the
signal before transmission.

Protection-switching signaling for extra traffic is carried on the protection

loop. Any failure on the protection loop overrides the extra traffic.
Receive
In the receive direction, the G1 OC-48 receive interface converts the received
OC-48 optical signal into an STS-48 electrical signal. This signal is sent to the
demultiplexer, framed, descrambled, and demultiplexed into 48 STS-1 signals
that are synchronized to the system clock after the transport overhead has been
extracted. The STS-1 signals are then routed from the demultiplexer to the
corresponding tributaries.

For DS3 mappers, DS3 signals are extracted from the STS-1 signals, then
routed through the interface ports and transmitted to external equipment as
with working shelves. For OC-3, STS-12, or OC-12 tributaries, the STS-1
signals are routed from the demultiplexer to the corresponding OC-3, STS-12,
or OC-12 interface where 3 or 12 STS-1 signals are multiplexed into an
electrical STS-3 or STS-12 signal and transport overhead is added. For OC-3
or OC-12 interfaces, the signal is then scrambled and converted into an optical
OC-3 or OC-12 signal, then transmitted over the OC-3 or OC-12 line. For
STS-12 tributaries, the STS-12 signal is transmitted over coaxial cable to the
connected external equipment.

Managing STS connections in linear systems (timeslot assignment)

Defining STS connections establishes traffic continuity. For add and drop
connections, an STS connection is a cross-connect point between STS-1
timeslots on the OC-48 transport circuit pack groups and the STS-1

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-15

equivalents at the tributaries. An STS path is a series of STS connections from

the asynchronous entry point to the SONET network to the point where the
signal leaves the SONET network. A bidirectional STS path is the same route
viewed in two directions.

You can define STS connections using the OPC Connection Manager tool,
Preside, Integrated Network Management (INM) Broadband, Network
Manager, or Transaction Language 1 (TL1) interface. The OPC Connection
Manager tool maintains a centralized database of up-to-date cross-connect
information for the network elements within its span of control. It eliminates
provisioning conflicts between the different interfaces.

Defining the linear configurations

When you use the OPC Connection Manager tool, Preside, INM, or Network
Manager to define the STS connections, you must use the OPC Configuration
Manager tool to configure the two terminals in 1+1, 1:1, and 0:1 single-shelf
systems as a linear system. In multishelf 1:N systems, you must define the two
terminals serving each channel as well as the two terminals serving the
protection channel.

Concatenated payloads (STS-3c and STS-12c)

OC-3, STS-12, and OC-12 tributaries can carry STS-3c payloads. STS-12 and
OC-12 tributaries can carry STS-12c payloads. STS-3c payloads require three
adjacent STS-1 timeslots. STS-12c payloads require 12 adjacent STS-1
timeslots. The system supports bidirectional and unidirectional STS-3c and
STS-12c payloads. For more information about concatenated payloads, see
System Description, 323-1201-100.

SDH payloads (STM-1o and STM-4o)

Half-height OC-3 interfaces (NT8E08) can carry STM-1o traffic formatted for
the European market. OC-12 interfaces (NT7E02Px) can carry STM-4o traffic.
Internally, the OC-48 ring treats STM-1o traffic as STS-3c traffic and STM-4o
traffic as STS-12c traffic.

Note: STM-1J and Packet Edge tributaries are not supported on linear
configurations.

CAUTION
Risk of service interruption
For OC-3 facilities equipped with half-height interfaces, install
only NT8E08 OC-3 interface circuit packs in the OC-3 carrier.
Installing STM-1o circuit packs for the European market in the
OC-3 carrier can result in a service interruption.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-16 Signal flow

In-service channel rollover

The OPC Connection Manager tool allows you to reassign timeslots for all
supported types of STS connections while a system is in service. The impact
on traffic is less than 50 ms. You can reassign timeslots on working channels
1 to 48 on linear systems and protection channels 1 to 48 on 1:N multishelf
systems.

The system performs the reassignment in three phases:

• bridge — the system duplicates the signal over the new timeslot
• switch — the system switches the traffic from the old to the new timeslot
• deprovision — the system deprovisions the connections of the old timeslot
For a diagram showing the phases for bidirectional connections, see
Figure 1-7. For details on how to reassign timeslots on an in-service system,
see Provisioning and Operations Procedures, 323-1201-310.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-17

Figure 1-7
In-service channel rollover phases for a same route, bidirectional connection
F3879_R14

Original Connection
NE1 NE2 NE3

Step 1. Bridge

NE1 NE2 NE3 NE1 NE2 NE3

Step 2. Switch line-to-line line-to-line

NE1 NE2 NE3 NE1 NE2 NE3

Step 3. De-provision

NE1 NE2 NE3

original timeslot new timeslot

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-18 Signal flow

Ring ADM shelf configuration

In a GR-1230 Ring, the OC-48 terminal shelf is configured as an add-drop
multiplexer (ADM) node. It can accommodate, on a quadrant basis, a mix of
DS3, STS-1, STM-1J, OC-3, STS-12, OC-12, and Packet Edge tributary types
for a maximum capacity equal to 48 add-drop STS-1 signals. In addition, up to
48 signals can be provisioned as passthrough connections. Passthrough
connections are neither added nor dropped at the node but are passed through
the node from the neighbor node on one side to the neighbor node on the other
side.

You can mix DS3 mappers, STS-1 interfaces, half-height OC-3 interfaces, and
STM-1J interfaces (NT8E08) in the same quadrant. You cannot mix
double-width OC-3 interfaces (NT7E01), STS-12 interfaces, OC-12
(NT7E02) interfaces or Packet Edge 2x1000SX (formerly iPT1000) (NT8E27)
circuit packs with any other tributary types in the same quadrant. For example,
an OC-48 terminal shelf could have quadrant 1 equipped with a mix of DS3
mappers, STS-1 interfaces, half-height OC-3 interfaces, and STM-1J
interfaces (NT7E08), quadrant 2 equipped with double-width OC-3 interfaces
(NT7E01), quadrant 3 equipped with a mix of DS3 mappers and STS-1
interfaces, and quadrant 4 equipped with OC-12 interfaces.

In a GR-1230 Ring architecture, G1 and G2 each carry 24 working and 24

protection timeslots. Each timeslot corresponds to one STS-1 signal. In normal
operation, both optical circuit pack groups are always active and the green
LEDs on the circuit packs are lit. Normal operation means there is no active
OC-48 protection switch.

Note: The OC-48 G1 and G2 circuit pack groups provide the optical
transport interfaces. Each circuit pack group consists of one transmit
interface, one receive interface, and a demultiplexer circuit pack.

The extra traffic feature allows the normally reserved 24 protection timeslots
to carry working traffic. This increases the working bandwidth of the ring.
However, the extra traffic bandwidth is not protected and is lost when there is
either an automatic or user-initiated OC-48 protection switch.

As shown in Figure 1-8, all signals going into the OC-48 terminal shelf are
labeled receive (Rx), and all signals going out of the shelf are labeled transmit
(Tx).

Transmitting into fiber (ring ADM node)

In the optical transmit direction, DS3 signals coming from the termination
panel (added signals) are connected to the interface port circuit packs (see
Figure 1-9). The interface ports then route the signals to the DS3 mappers,
which map them into an STS-1 signal format and send them on to the OC-48
ring transmit interface.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-19

Figure 1-8
OC-48 signal labeling in a GR-1230 Ring
F0599-1-48_R16.1
24 working STS-1s and 24 protection STS-1s
on each fiber

DS3, DS3,
STS-1, Site A Site B
STS-1,
OC-3, OC-3,
• OC-48 OC-48
STM-1J, • • STM-1J,
ADM ring ADM ring
STS-12, • • STS-12,
node node •
OC-12, OC-12,
Packet Edge Packet Edge
tributaries tributaries

DS3,
DS3, OC-48
STS-1,
STS-1, regenerator
OC-3,
OC-3, OC-48 OC-48 STM-1J,
STM-1J, • ADM ring ADM ring •
• STS-12,
STS-12, • node node •
• OC-12,
OC-12,
Packet Edge
Packet Edge Site C Site D
tributaries
tributaries

When STS-1 tributaries are used, the STS-1 signals coming from the
termination panel are connected to the interface port circuit packs. The
interface ports then route the signals to the STS-1 interfaces, where the STS-1
signals are mapped and sent to the OC-48 ring transmit interface.

The OC-48 ring transmit interface then multiplexes the 48 STS-1 signals into
one STS-48, adds transport overhead, and then scrambles the signal. The
OC-48 ring transmit interface also converts the STS-48 electrical signal into
an OC-48 optical signal. The signal is then transmitted over the transmit fiber.

Figure 1-9 illustrates how an OC-48 terminal can be equipped with OC-48
high performance transmitters or OC-48 optical amplifiers. When equipped
with OC-48 high performance transmitters, STS-48 ring transmit interfaces
must be installed in place of OC-48 ring transmit interfaces in the G1 and G2
transport circuit pack groups.

The STS-48 signal produced by the STS-48 ring transmit interface is

transmitted along a coaxial cable to the OC-48 high performance transmitter.
The OC-48 high performance transmitter converts the STS-48 signal into an
OC-48 optical signal and amplifies it before transmission. The OC-48 high
performance transmitter outputs a more powerful signal than the OC-48 ring
transmit interface, thus increasing the range of the signal.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-20 Signal flow

Figure 1-9
Traffic signal flow for a ring ADM node in a GR-1230 Ring
F0069-blsr_R15

DS3/STS-1
termination
panel
DS3
or Transport
STS-1 overhead
1 to 24 DS3
Interface mappers
ports or
STS-1
interfaces
1 to 8 STS-48 or OC-48 high OC-48
OC-48 ring performance
transmit transmitter Tx G1
interface or optical
Switcher (Note 1) amplifier
1
OC-48
DS3 OC-48
mapper OC-48 ring Rx G1
demultiplexer receive
protection interface
Switch G1 (Note 2)
controller STS-1
interface STS-48 or OC-48 high OC-48
protection OC-48 ring performance Tx G2
transmit transmitter
Switcher interface or optical
2 (Note 1) amplifier
DS3
or OC-48
STS-1 OC-48 ring OC-48 Rx G2
25-48 demultiplexer receive
DS3 interface
mappers G2 (Note 2)
Interface
ports or
STS-1 FW-0069 (blsr R15)
interfaces
9 to 16

Note 1: The OC-48 optical amplifier requires the OC-48 ring transmit interface to provide its optical input.
When the OC-48 high performance transmitter is used, the STS-48 ring transmit interface provides its
electrical STS-48 input. If neither the OC-48 optical amplifier nor the OC-48 high performance
transmitter is used, the OC-48 ring transmit interface connects directly to the transmit fiber.

Note 2: Under normal conditions, the G1 demultiplexer handles all drop traffic from both G1 and G2
demultiplexers. If there is a failure of G1 transport circuit pack group, then the G2 demultiplexer handles
the drop traffic.

When an OC-48 terminal is equipped with OC-48 optical amplifiers, each

OC-48 optical amplifier is connected to an OC-48 ring transmit interface by
way of a fiber patchcord. The OC-48 signal produced by the OC-48 ring
transmit interface travels over the optical patchcord to the OC-48 optical
amplifier. The OC-48 optical amplifier then amplifies the signal and transmits
it over the transmit fiber, thereby extending the range of the signal.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-21

If the OC-48 shelf is equipped with OC-3, STM-1J, or OC-12 tributaries (one
or more quadrants equipped with OC-3, STM-1J, or OC-12 interfaces), the
incoming OC-3, STM-1J, or OC-12 signal is received on the OC-3, STM-1J,
or OC-12 interface circuit pack of the OC-48 shelf. The OC-3, STM-1J, or
OC-12 interface circuit pack converts the received OC-3, STM-1J, or OC-12
optical signal into an electrical STS-3 or STS-12 signal in the same way as
shown in Figure 1-3 on page 1-6 for a linear terminal.

This STS-3 or STS-12 signal is then demultiplexed, framed, and descrambled

into 3 or 12 STS-1 signals that are synchronized to the system clock after the
transport overhead has been extracted. If STS-12 interfaces are used instead of
OC-12 interfaces, the processing of the STS-12 electrical signal is the same.

The STS-1 signals from the tributaries are then sent to the OC-48 or STS-48
transmit interface, which processes the signals for transmission as described
for DS3 or STS-1 tributaries.

Each point at which an STS signal is mapped from a tributary to the OC-48
transport circuit pack group at the ADM node is called a service access point
(SAP) for the STS path. The equivalent point at which the STS path is
terminated at a far-end ADM node is called an end node. Figure 1-10 shows
four STS-1 paths (paths a to d), including their service access points and end
nodes.
Figure 1-10
A bidirectional STS-1 path spanning a ring
F2247

Node A Node B
STS #3
(path a)
(path b) (path b)
(path c)

STS #1 STS #2 STS #2 STS #3

Line

STS #2
(path c) (path a)
STS #1 (path d)
(path d)

Node D Node C
Line

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-22 Signal flow

Passthrough signals
As with receiving added signals, the OC-48 ring transmit interface can receive
passthrough STS-1 signals from its associated OC-48 ring demultiplexer,
which in turn receives the signal from the demultiplexer in the opposite receive
direction. These passthrough signals are multiplexed with the added signals to
form the OC-48 optical signal. Figure 1-11 details the STS signal flow within
the transport circuit pack groups. Nodes traversed by an STS-1 path that are
not service access points or end nodes are called intermediate nodes.
Figure 1-11
STS signal flow in the OC-48 G1 and G2 transport circuit pack groups a ring ADM node
F2523-48_R12

OC-48 circuit pack OC-48 circuit pack

group G1 group G2

OC-48 ring OC-48 ring

transmit transmit
interface interface
G1 G2
West line STS-1 East line
Add buses
OC-48 OC-48
receive Loopback Loopback receive
interface bus bus interface
G1 G2

STS-1 STS-1
OC-48 passthrough passthrough OC-48
ring ring
demux STS-1 drop bus from G2 demux
G1 G2

STS-1 drop bus STS-1 drop bus, in the

(See Note) case of a G1 failure

Tributaries
DS3, STS-1, OC-3,
STS-12, or OC-12

Add/drop traffic

Note: Under normal conditions, the G1 demultiplexer (demux) handles all drop traffic from both the
G1 and G2 demultiplexer circuit packs. If there is a failure of the OC-48 G1 circuit pack group, then
the G2 demultiplexer handles the drop traffic.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-23

Receiving from fiber (ring ADM node)

In the optical receive direction, the OC-48 receive interface circuit pack
converts the received OC-48 optical signal into an STS-48 electrical signal.
The STS-48 signal is then sent to the OC-48 ring demultiplexer, framed,
descrambled, and demultiplexed into 48 STS-1 signals that are synchronized
to the system clock after the transport overhead has been extracted. The STS-1
signals are then either dropped to the tributaries or passed through.
DS3 and STS-1 signals
For DS3 tributaries, the STS-1 signals to be dropped are fed from the
demultiplexer to the corresponding DS3 mapper, where the DS3 signals are
extracted from the STS-1 SONET format. Then, the DS3 signals are routed
through the interface port circuit packs. Finally, the DS3 signals are sent to the
termination panel.

If STS-1 tributaries are used, the STS-1 signals are fed to the corresponding
STS-1 interface where the STS-1 signals are framed and scrambled. Then, the
STS-1 signals are routed through the interface port circuit packs and then sent
to the termination panel.
OC-3, STM-1J, OC-12, and STS-12 tributaries
When the OC-48 ADM node is equipped with OC-3, STM-1J, or OC-12
tributaries, the STS-1 signals that comes from the OC-48 ring demultiplexer
are received by the OC-3, STM-1J, or OC-12 interface circuit pack, which
multiplexes 3 or 12 STS-1 signals into an electrical STS-3 or STS-12, adds
transport overhead, and then scrambles and converts the STS-3 or STS-12
signal into an OC-3, STM-1J, or OC-12 optical signal for transmission.

If STS-12 interfaces are used instead of OC-12 interfaces, the STS-1 signals
that come from the OC-48 ring demultiplexer are then received by the STS-12
interface, which multiplexes 12 STS-1 signals into an STS-12 signal, adds
transport overhead, and scrambles it for transmission.
Service access point and end node
The ring ADM node that terminates a given STS-1 path is called an end node.
For each service access point in Figure 1-10 on page 1-21, there is a
corresponding end node. For bidirectional communications, a complementary
STS-1 path is required with a service access point and an end node.
Passthrough signals
STS-1 signals to be passed through are sent from the demultiplexer associated
with the OC-48 receive interface to the demultiplexer for the other optical line
(that is, from the G1 demultiplexer to that of G2, and from the G2
demultiplexer to the G1 demultiplexer). These passthrough STS-1 signals are
then sent to the OC-48 ring transmit interface for multiplexing with added
signals and transmission as an OC-48 optical signal. Nodes traversed by an
STS-1 path that are not service access points or end nodes are called
intermediate nodes.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-24 Signal flow

Defining the ring configuration

The nodes in the ring are interconnected according to a node map, which
defines the position of each of the ADM nodes in the ring in relation to the
other ADM nodes. A node map consists of network element numbers and
automatic protection-switch identifiers (APS IDs). Each network element in a
network is assigned a unique identifier from 1 to 65534, which is used in
inter-shelf communications. In addition, the APS ID is a number from 0 to 15
that is assigned to each ADM node in the ring and is used for signaling
protection-switching requests and status information between the ring ADM
nodes. The APS ID is sometimes called a node ID.

Note 1: The maximum number of nodes in the ring (16) is set by the
Telcordia (formerly known as Bellcore) GR-1230-CORE standard.
Note 2: Only ADM nodes are given an APS ID, not regenerators. This is
because no protection switching is performed at regenerators.
Defining the fiber connectivity
The node map created using the OPC defines the direction of signal flow
between the optical circuit pack groups of the respective nodes in the ring.
Then, this node map is downloaded to each of the two demultiplexers in each
ADM node. Adjacent ring ADM nodes can have their optical circuit pack
groups interconnected in any combination—that is, from G1 to G1, G1 to G2,
or G2 to G2. For a diagram, see Figure 1-12.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-25

Figure 1-12
Example of connectivity between optical circuit pack groups in a GR-1230 Ring
F2244-2-48

G1 ADM G2
ring
G1 node G2

G2 G2 G2 G2
ADM ADM
ring C B ring
node node
G1 G1 G1 G1

G2 G2 G2 G2

Regenerator Regenerator
G2 G2 G2 G2

G2 ADM G1
ring
G2 node G1

The node map reflects the G1 connectivity for the ring and each ADM node
then derives the G2 connectivity as the inverse of the G1 connectivity. This
establishes a closed, bidirectional ring. Figure 1-13 illustrates the connectivity
of a four node ring, showing the node map direction including network element
numbers and APS IDs for G1. After receiving the provisioning data for the
ring, the demultiplexers extend it to the OC-48 ring transmit interface circuit
packs.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-26 Signal flow

Figure 1-13
Node map in a GR-1230 Ring
F2245

60-7
58-9
52-11
55-5
Node map for G1
NE ID 60
APS ID 7

Node A

55-5 58-9
60-7 NE ID 55 NE ID 58 60-7
Node D Node B
58-9 APS ID 5 APS ID 9 55-5
52-11 52-11

Node C

NE ID 52
APS ID 11
Node map for G1
52-11
55-5 (FW-2245)
60-7
58-9

Provisioning audits for the ring configuration

The OPC periodically audits the ring’s node map, and in the event of a
discrepancy imposes its version on the ring. Backups of the provisioning data
can be scheduled through the OPC as well. These backups should be scheduled
so that no two network elements in the ring are backed up at the same time.
The backup should be done from the network element to the OPC first, and
then from the primary to the backup OPC.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-27

Managing STS connections in a GR-1230 Ring (timeslot assignment)

Defining STS connections establishes traffic continuity. In a GR-1230 Ring,
you must assign STS-1 signals as add, drop, or passthrough at each of the
add-drop multiplexer (ADM) nodes in the ring.

For add and drop connections, an STS connection is a cross-connect point

between STS-1 timeslots on the OC-48 transport optics and the STS-1
equivalents at the tributaries. For passthrough connections, an STS connection
is a cross-connect point between the receiving and transmitting optics at the
ADM node.

An STS-1 path is defined by the series of STS connections at each of the ring
ADM nodes on that path.

As shown in Figure 1-10 on page 1-21, an STS path is the route taken by an
STS-1 signal from its service access point node, where the payload from a DS3
mapper, STS-1 interface, OC-3 interface, STM-1J interface, STS-12 interface,
OC-12 interface or 2x1000SX circuit pack gains access to the STS-1
bandwidth, through its intermediate nodes (passthrough connections), to its
end node. The payload from a DS3 mapper, STS-1, OC-3, STS-12, OC-12
interface or 2x1000SX circuit pack gains access to the STS-1 bandwidth at the
service access point. A bidirectional STS-1 path is the same route, viewed in
two directions.

Concatenated payloads (STS-3c and STS-12c)

OC-3, STS-12, OC-12 and Packet Edge tributaries can carry STS-3c payloads.
STS-12, OC-12 and Packet Edge tributaries can carry STS-12c payloads.

Note: When Packet Edge connections are provisioned as protected

point-to-point connections, the only supported rate is STS-12c.

STS-3c payloads require three adjacent STS-1 timeslots. STS-12c payloads

require 12 adjacent STS-1 timeslots. The system supports bidirectional and
unidirectional STS-3c and STS-12c payloads. Packet Edge connections must
be bidirectional. For more information about concatenated payloads, see
System Description, 323-1201-100.

SDH payloads (STM-1J, STM-1o and STM-4o)

Half-height OC-3 interfaces (NT8E08x) can carry STM-1o traffic formatted
for the European market on either point-to-point tributary connections or
matched-node connections. STM-1J interfaces (NT8E08x) can carry J-SDH
traffic. OC-12 interfaces (NT7E02x) can carry STM-4o traffic formatted for
the European market on either point-to-point tributary connections or
matched-node connections. Internally, the OC-48 ring treats STM-1o traffic
and STM-1J traffic as STS-3c traffic, and STM-4o traffic as STS-12c traffic.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-28 Signal flow

CAUTION
Risk of service interruption
Install only NT8E08 (OC-3 or STM-1J) interface circuit packs
in the OC-3 carrier. Installing STM-1o circuit packs for the
European market in the OC-3 carrier can result in a service
interruption.

Defining STS connections

You can use the OPC Connection Manager tool, Preside, Integrated Network
Management (INM) Broadband, Network Manager, or Transaction Language
1 (TL1) to assign STS-1 connections in the GR-1230 Ring. The OPC
Connection Manager tool maintains a centralized database of up-to-date
cross-connect information for the network elements within its span of control.
It eliminates provisioning conflicts between the different interfaces.
Timeslot assignment for STS connections
The OPC Connection Manager tool, through the timeslot assignment (TSA)
feature, allows the STS-1 timeslots to be allocated between the OC-48 G1 and
G2 circuit pack groups at the ring ADM nodes regardless of the physical
routing. The add and drop connections to and from the tributaries are achieved
through SONET STS-1 path termination to STS-1 channel termination
connections (PT to CT). Passthrough connections are achieved through
SONET channel-to-channel terminations (CT to CT).
Squelch map for STS connections
The OPC Connection Manager tool includes a squelch map, which is
automatically derived from the STS connection data. This squelch map defines
which STS-1 timeslots are automatically injected with an alarm indication
signal (STS path AIS) in the event of a protection switch. For more information
on the squelch map, see “Protected operation—node failure” on page 2-31.
Provisioning audits for the STS connections
The OPC periodically audits STS connection provisioning, and in the event of
a discrepancy imposes its version on the ring. Backups of the provisioning data
can be scheduled through the OPC as well. These backups should be scheduled
so that no two network elements in the ring are backed up at the same time.
The backup should be done from the network element to the OPC first, and
then from the primary to the backup OPC.
In-service channel rollover
The OPC Connection Manager tool allows you to reassign timeslots for all
supported types of STS connections while a system is in service. The impact
on traffic is less than 50 ms. You can reassign timeslots on channels 1 to 24 or
on channels 25 to 48 on the ring. You cannot reassign timeslots from working
to protection channels or for matched-node connections.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-29

The system performs the reassignment in three phases:

• bridge — the system duplicates the signal over the new timeslot
• switch — the system switches the traffic from the old to the new timeslot
• deprovision — the system deprovisions the connections of the old timeslot
For a diagram showing the phases for bidirectional connections, see Figure 1-7
on page 1-17. For a diagram showing the steps for unidirectional
drop-and-continue connections, see Figure 1-14. For detailed information on
how to reassign timeslots on an in-service system, see Provisioning and
Operations Procedures, 323-1201-310.
In-service route rollover
The OPC Connection Manager allows you to reverse the route a connection
follows through a ring. The two possible routes are long or short according to
the number of intermediate nodes between the source and the destination
nodes. The new connection can use the same or a different timeslot. The
in-service route rollover follows the same phases as for an in-service channel
rollover.
Matched nodes for inter-ring STS paths
With the matched-nodes feature, an STS path can traverse multiple rings. You
can use the OPC Connection Manager to define the path. The path must use
SONET tributaries, that is, STS-1, OC-3, STS-12, or OC-12, to link ADM
nodes of the two rings. Each direction of the STS connection between rings has
a designated primary and a secondary path to provide path-switched protection
between the rings (see Figure 1-15).

Note 1: DS3 tributaries cannot be used as matched node gateway

connections. However, they can be used as service access points (SAP) to
the ring for matched node STS paths.
Note 2: STM-1J and Packet Edge tributaries do not support matched-node
connections.
An ADM node serving as the broadcast point receives the signal from the
source. It then drops the signal over the tributary to the matching node in the
adjoining ring. The matching node in the adjoining ring is the primary
(selector) node. At the same time, the broadcast node broadcasts the same
signal on a passthrough connection over the OC-48 transport optics to a second
node in the first ring.

The broadcast bridging is a drop-and-continue technique. The portion of the

signal that continues on the OC-48 optics can use either working or protection
bandwidth. If it uses working bandwidth, it is a drop-and-continue on working
(DCW) secondary segment. If it uses protection bandwidth, it is a
drop-and-continue on protection (DCP) secondary segment.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-30 Signal flow

Figure 1-14
In-service channel rollover phases for a same route, drop and continue, unidirectional connection
F3880_R14

Original Connection
NE1 NE2 NE3

Step 1. Bridge

NE1 NE2 NE3

Step 2. Switch line-to-line

NE1 NE2 NE3 NE1 NE2 NE3

Step 3. De-provision

NE1 NE2 NE3

Legend: original timeslot new timeslot

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-31

Figure 1-15
Matched nodes in a GR-1230 Ring for inter-ring STS paths
F2569

Source
Service access point

Broadcast
Ring A point
(3 ADM nodes)

Secondary feed

Secondary
feed
Decision
point
Primary feed
Primary
Secondary feed Secondary
node
(selector node
node)

Ring B
(6 ADM nodes) Intermediate
(passthrough)
node

Broadcast
point

Secondary feed

Decision
point Primary feed Secondary feed
Primary
Secondary feed
node Secondary
(selector node
Ring C node)
(4 ADM nodes)

Destination
End
node

Legend:
= Inter-ring STS path
= Fibers not used by the STS path

Note: For clarity, only one direction of the STS path is shown.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-32 Signal flow

The second node in the first ring drops the signal over a tributary to its
matching node in the adjacent ring. The matching node routes the signal over
the transport optics of the second ring to the primary node.

The primary node is also called the selector node. It acts as the decision point
and selects either the primary feed (normal operation) or the secondary feed
(protected operation). The primary feed is always the feed received at the
selector node from the first ring over a tributary. The secondary feed is always
the feed received at the selector node over the OC-48 optics.

The selector node makes the selection according to the condition of the
primary and secondary signals. If the secondary signal is failed or both the
primary and secondary signals are failed, the primary feed remains selected.

All inter-ring connections are bidirectional and both transmit and receive
directions must use the same STS timeslot for the secondary feed.

OC-48 regenerator/optical amplifier shelf

The OC-48 regenerator/optical amplifier shelf is used in long-haul toll
networks and interoffice networks. You can configure the shelf for regenerator
applications or for optical amplifier applications. The shelf supports OC-48
regenerator circuit packs (regenerator/transmit interface and receive interface
circuit packs), OC-48 high performance transmitter, OC-48 optical amplifiers,
and OC-48 bidirectional 1533/1557 nm optical line amplifiers.

When configured as a regenerator, the shelf regenerates the OC-48 signal for
transmission over long distances. The high performance transmitters, optical
amplifiers, and bidirectional 1533/1557 nm optical line amplifiers are used to
amplify the output power of a transmitted optical signal. This extends the
distance of the optical signal before regeneration of this signal is required.

These functions can be mixed on the same shelf. For example, in a

route-diverse configuration, four shelf slots are used by the OC-48 regenerator
circuit packs, leaving four shelf slots available for high performance
transmitters, optical amplifiers, and bidirectional 1533/1557 nm optical line
amplifiers. However, because of the configuration required for
non-route-diverse applications, the conventional regenerator circuit packs
occupy all the available shelf slots.

As a regenerator, each regenerator/optical amplifier shelf can accommodate a

maximum of two bidirectional channels (for example, the working and
protection channels of a linear system in both the transmit and receive
directions).

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-33

Each of the two bidirectional regenerator channels is supported by an optical

interface, called a circuit pack group. An OC-48 circuit pack group for a
regenerator consists of two each of the OC-48 receive interface and
regenerator/transmit interface circuit packs (a transmit/receive pair for each
direction). These are the only traffic-carrying circuit packs used in the
regenerator/optical amplifier shelf when equipped as a conventional
regenerator. One circuit pack group (G2) is used for route diversity
applications and both (G1 and G2) are used for non-route diversity.

For shelf equipping rules for when the shelf is equipped with high performance
transmitters, optical amplifiers, or bidirectional 1533/1557 nm optical line
amplifiers, see HPTx and Optical Amplifier Applications, 323-1251-230.

For a functional block diagram of the regenerator/optical amplifier shelf, see

Figure 1-16.

Note: In linear systems configured for non-route diversity, fibers

associated with G2 at a regenerator site are connected to G1 at the terminal
site. Conversely, G1 at a regenerator site is connected to G2 at the terminal
site.

Non-route-diverse regenerators supporting 1+1 and 1:1 systems

In a 1+1 and 1:1 linear systems, both G1 and G2 of the regenerator/optical
amplifier shelf are always active, regardless of the protection status of the
terminals to which the regenerator is connected (that is, all G2 OC-48 receive
interface circuit packs and all G2 OC-48 regenerator/transmit interface circuit
packs have their green Active LEDs lit).

Non-route-diverse regenerators supporting multishelf 1:N systems

In a multishelf 1:N system with more than one working channel (that is, N is
greater than 1), multiple regenerator/optical amplifier shelves are required at
each consecutive regenerator site, each of which can support two bidirectional
or four unidirectional optical channels. The current maximum number of
optical channels in a 1:N system is 11. Route diversity cannot be used in a
multishelf 1:N protection architecture.

The first regenerator/optical amplifier shelf must have G1 dedicated to the

protection channel and G2 assigned to the first working channel, channel 1. On
the second and subsequent regenerator/optical amplifier shelves, the
even-numbered or lower-numbered working channel (that is, channel 2, 4, 6,
8, or 10) is served by the G2 circuit pack group. Odd-numbered or
higher-numbered channels (channels 3, 5, 7, 9, and 11) are served by the G1
circuit pack group.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-34 Signal flow

Route-diverse regenerators supporting a single 1+1, 1:1, or 0:1 system

In 1+1, 1:1, and 0:1 linear systems configured for route diversity, OC-48 G1
(slots 5 through 8) of the regenerator/optical amplifier shelf is always
unequipped. Circuit pack group G2 (slots 9 through 12) carries an optical
signal from either OC-48 G1 or G2 of the terminals to which it is connected.
Figure 1-16
Traffic signal flow for OC-48 regenerators
F0070-48

OC-48 OC-48
(G2E) OC-48 (G2E)
OC-48 STS-48
receive regenerator/
interface transmit
interface

Overhead bus Working or

to shelf processor protection
channel
OC-48 OC-48
(G2W) OC-48 (G2W)
regenerator/ STS-48 OC-48
transmit receive
interface interface

OC-48 OC-48
(G1E) OC-48 (G1E)
OC-48 STS-48
regenerator/
receive
transmit
interface
interface

Working or
Overhead bus protection
to shelf processor channel

OC-48 OC-48
(G1W) OC-48 (G1W)
regenerator/ STS-48 OC-48
transmit receive
interface interface

FW-0070 (oc48)

In a regenerator in a 1+1, 1:1, or 0:1 system, G2 is always active, regardless of

the protection status of the terminals (OC-48 terminal shelves) to which the
regenerator is connected (that is, all OC-48 receive interface circuit packs, and
all regenerator/transmit interface circuit packs have their green LEDs lit).

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-35

Route-diverse regenerators supporting a single GR-1230 Ring system

GR-1230 Rings are always configured for route diversity. When a
regenerator/optical amplifier shelf supports only one ring, the G1 (slots 5
through 8) circuit pack group is unequipped. G2 (slots 9 through 12) carries an
optical signal from either G1 or G2 of the ADM nodes (OC-48 terminal
shelves) to which it is connected. G2 is always active, regardless of the
protection status of the ring (that is, all G2 OC-48 receive interface and OC-48
regenerator/transmit interface circuit packs have their green Active LEDs lit).

Route-diverse regenerators supporting two systems

Because route-diverse systems use only one bidirectional channel in a
regenerator/optical amplifier shelf, a given shelf can serve two route-diverse
systems. The SONET SDCCs must be provisioned for fixed operation. The
same shelf can support a channel from each of two linear systems, two rings,
or a linear system and ring in any combination.

When a regenerator/optical amplifier shelf is equipped for two route-diverse

systems, circuit pack group G1 (slots 5 to 8) is equipped for one of the
route-diverse systems. G1 carries an optical signal from either OC-48 G1 or
G2 of the terminal shelves to which the regenerator is connected. G1 is always
active, regardless of the protection status of the terminal shelves to which the
regenerator is connected (that is, all G1 OC-48 receive interface and OC-48
regenerator/transmit interface circuit packs have their green Active LEDs lit).

Circuit pack group G2 (slots 9 to 12) is equipped for the other route-diverse
system. G2 carries an optical signal from either OC-48 G1 or G2 of the
terminal shelves to which the regenerator is connected. G2 is always active,
regardless of the protection status of the terminal shelves to which the
regenerator is connected (that is, all G2 OC-48 receive interface and OC-48
regenerator/transmit interface circuit packs have their green Active LEDs lit).

Regenerator application
Traffic signal flow for an OC-48 regenerator is shown in Figure 1-16. The
OC-48 receive interface converts the incoming optical signal to its electrical
STS-48 equivalent. The STS-48 signal is passed by way of the STS-48 bus to
the OC-48 regenerator/transmit interface. The regenerator/transmit interface
extracts the section overhead and inserts updated overhead into the outgoing
STS-48 signal. This signal undergoes parallel-to-serial conversion and is then
reconverted into an optical signal for transmission to the next site.

You can enhance the regenerator performance by supplementing OC-48

regenerator/transmit interfaces with OC-48 optical amplifiers or by replacing
each OC-48 regenerator/transmit interface with an STS-48
regenerator/transmit interface and an OC-48 high performance transmitter.
This increases the transmission range of the optical signals output from the
regenerator.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-36 Signal flow

Signal flow in a regenerator using high performance transmitters

Figure 1-17 shows two regenerator/optical amplifier shelves equipped with
STS-48 regenerator/transmit interface and OC-48 high performance
transmitter pairs. The OC-48 high performance transmit interfaces occupy one
shelf. The other circuit packs occupy the other shelf.

The signal processing is exactly the same as for a conventional regenerator,

except that after the parallel-to-serial conversion of the outgoing STS-48
signal, the signal is passed to the OC-48 high performance transmitter through
a coaxial cable. The OC-48 high performance transmitter converts the
incoming electrical signal into an optical signal, then amplifies the optical
signal before transmitting it.
Figure 1-17
Traffic signal flow in regenerator/optical amplifier shelves equipped with STS-48
regenerator/transmit interfaces and OC-48 high performance transmitters
F0070-HPTx

OC-48 OC-48
(G2E) STS-48 (G2E)
OC-48 STS-48 OC-48
regenerator/ STS-48
receive high performance
transmit
interface transmitter
interface

Overhead bus Working or

to shelf processor protection
channel
OC-48 OC-48
(G2W) OC-48 STS-48 (G2W)
STS-48 regenerator/ STS-48 OC-48
high performance receive
transmitter transmit
interface interface

OC-48 OC-48
(G1E) STS-48 (G1E)
OC-48 STS-48 STS-48 OC-48
regenerator/
receive high performance
transmit
interface transmitter
interface

Working or
Overhead bus protection
to shelf processor channel

OC-48 OC-48
(G1W) OC-48 STS-48 (G1W)
STS-48 OC-48
high performance STS-48 regenerator/ receive
transmitter transmit
interface interface

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-37

Signal flow in a regenerator using optical amplifiers

Figure 1-18 shows the signal flow in two regenerator/optical amplifier shelves
where one shelf is equipped with OC-48 optical amplifiers in post mode. The
other regenerator/optical amplifier shelf is equipped with OC-48 receive
interfaces and OC-48 regenerator/transmit interfaces. Each optical amplifier
accepts an OC-48 optical signal from an OC-48 regenerator/transmit interface
and amplifies it. The amplified OC-48 signal is then transmitted.
Figure 1-18
Traffic signal flow in a regenerator/optical amplifier shelf equipped with OC-48 optical amplifiers
operating in post mode
F0070-OLA

OC-48 OC-48
(G2E) OC-48 (G2E)
OC-48 STS-48 OC-48
receive regenerator/ optical
transmit amplifier
interface
interface

Overhead bus Working or

to shelf processor protection
channel
OC-48 OC-48
(G2W) OC-48 OC-48 (G2W)
regenerator/ STS-48 OC-48
optical receive
amplifier transmit
interface interface

OC-48 OC-48
(G1E) OC-48 OC-48 (G1E)
OC-48 STS-48
regenerator/ optical
receive
transmit amplifier
interface
interface

Working or
Overhead bus protection
to shelf processor channel

OC-48 OC-48
(G1W) OC-48 (G1W)
OC-48 STS-48 OC-48
optical regenerator/
transmit receive
amplifier interface
interface

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-38 Signal flow

Optical amplifier application

Two types of optical amplifier circuit packs can be used. The optical amplifier
circuit pack operating in line mode can amplify an optical signal for only one
direction. The bidirectional 1533/1557 nm optical line amplifier circuit packs
can amplify an optical signal for both directions.
Optical amplifier circuit packs
An OC-48 regenerator/optical amplifier shelf equipped with optical amplifiers
operating in line mode accepts up to eight OC-48 signals, amplifies them, and
retransmits them. The signal flow for the regenerator/optical amplifier shelf in
this configuration appears in Figure 1-20. Each incoming OC-48 signal passes
through a single OC-48 optical amplifier circuit pack.

The incoming optical signal is not converted into an electrical signal within the
optical amplifier circuit pack. Consequently, signal overhead is neither
extracted nor added to optical signals that pass through the shelf.

The optical amplifier configured in line mode can also be used as a

pre-amplifier. As can be seen in Figure 1-19, pre-amplification boosts the
OC-48 signal as the signal arrives at the OC-48 network element. For more
information, see HPTx and Optical Amplifier Applications, 323-1251-230.
Bidirectional 1533/1557 nm optical line amplifiers circuit packs
An OC-48 regenerator/optical amplifier shelf equipped with bidirectional
1533/1557 nm optical line amplifiers accepts up to eight OC-48 signals in each
direction of transmission, amplifies them, and retransmits them. One direction
carries a 1533 nm signal and the other direction carries a 1557 nm signal.

The signal flow for the regenerator/optical amplifier shelf in this configuration
appears in Figure 1-21. Each incoming bidirectional OC-48 signal passes
through a single OC-48 bidirectional 1533/1557 nm optical line amplifier
circuit pack.

The incoming optical signal is not converted into an electrical signal within the
circuit pack. Consequently, signal overhead is neither extracted nor added to
optical signals that pass through the shelf.
Figure 1-19
Optical amplifier as a pre-amplifier
F5926_R16

OLA OLA
λ Tx

λ Rx
λ Rx

λ Tx

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-39

Figure 1-20
Traffic signal flow in a regenerator/optical amplifier shelf fully equipped with optical amplifiers
operating in line mode
F2974

OC-48 OC-48 OC-48

optical
amplifier

OC-48 OC-48 OC-48

optical
amplifier

OC-48 OC-48 OC-48

optical
amplifier

OC-48 OC-48 OC-48

optical
amplifier

OC-48 OC-48 OC-48

optical
amplifier

OC-48 OC-48 OC-48

optical
amplifier

OC-48 OC-48 OC-48

optical
amplifier

OC-48 OC-48 OC-48

optical
amplifier

Note: There is no overhead connection between the shelf processor and any
of the optical amplifier circuit packs in this configuration.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-40 Signal flow

Figure 1-21
Traffic signal flow in a regenerator/optical amplifier shelf fully equipped with bidirectional
1533/1557 nm optical line amplifiers
F2974-BiOLA

OC-48 Bidirectional OC-48

optical
line amplifier

OC-48 Bidirectional OC-48

optical
line amplifier

OC-48 Bidirectional OC-48

optical
line amplifier

OC-48 Bidirectional OC-48

optical
line amplifier

OC-48 Bidirectional OC-48

optical
line amplifier

OC-48 Bidirectional OC-48

optical
line amplifier

OC-48 Bidirectional OC-48

optical
line amplifier

OC-48 Bidirectional OC-48

optical
line amplifier

Note: There is no overhead connection between the shelf processor and any
of the bidirectional 1533/1557nm optical line amplifier circuit packs in this
configuration.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-41

Unidirectional services
Rings and 1+1, 1:1, 0:1, and 1:N linear systems can be configured for
unidirectional traffic on their DS3 and STS-1 tributaries as follows:
• Unidirectional and bidirectional traffic are mixed in a network.
• Unidirectional and bidirectional tributaries are mixed on the same network
element.
• A single DS3 mapper or STS-1 interface, each with three facilities,
supports mixed bidirectional and unidirectional facilities.
OC-3, STS-12, and OC-12 tributaries on OC-48 network elements are
bidirectional carriers, but their STS payloads can be either unidirectional or
bidirectional. Unidirectional services terminated on OC-3 or OC-12 Transport
Bandwidth Manager (TBM) network elements, Nortel Networks OPTera
Metro 3000 multiservice platform series (formerly OC-3/12 Express) network
elements, or OPTera Metro 3100 (formerly OC-3 Express CX) network
elements are treated as being bidirectional. Unidirectional traffic can also pass
through regenerators.

Note: STM-1J and Packet Edge tributaries support bidirectional

connections only.

Linear systems
Figure 1-22 shows a unidirectional connection between two linear terminals.
A DS3 tributary on terminal 1 receives unidirectional traffic, and a DS3
tributary on terminal 2 transmits unidirectional traffic.

Note: STM-1J and Packet Edge tributaries are not supported on linear
systems.
Figure 1-22
Unidirectional traffic between two terminals
F3030-1

This tributary is
receiving
unidirectional service

DS3 DS3
DS3 DS3
This tributary is
DS3 DS3 transmitting a
unidirectional
OC-48 OC-48
service
Terminal 1 Terminal 2

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-42 Signal flow

It is possible to transmit a DS3 service on an STS-1 tributary. Thus, a

unidirectional DS3 signal can enter the receiving terminal on a DS3 mapper
circuit pack and exit the transmitting terminal on an STS-1 interface circuit
pack. Because the DS3 path is not terminated by the STS-1 interface circuit
pack, the DS3 “Drop-STS1 Rx” series of alarms cannot be raised at the site
with the STS-1 interface. However, these alarms become active as required at
the DS3 path termination site downstream from the STS-1 interface.

On a linear system, the receive and transmit traffic on a tributary can occupy
different STS-1 or DS3 tributary channels, and can be routed to different
tributaries at the far-end node. Figure 1-23 shows two independent
unidirectional connections to the same DS3 tributary on terminal 2. Node 2
receives and transmits independent unidirectional traffic on the same DS3
tributary. Node 1 uses two separate DS3 tributaries to receive and transmit
independent unidirectional traffic.
Figure 1-23
Two unidirectional connections on a single tributary
F3030

This tributary is
transmitting
unidirectional traffic

DS3 DS3
DS3 DS3 This tributary is
receiving and
DS3 DS3 transmitting
OC-48 OC-48 independent
Terminal 1 Terminal 2 unidirectional
services
This tributary is
receiving
unidirectional traffic

Collocated terminals
A terminal must drop unidirectional traffic that originates at the prior terminal.
However, sites with collocated terminals can either pass unidirectional traffic
through or drop and continue the traffic.
• Passthrough functionality allows collocated terminals to pass
unidirectional traffic to a downstream site. See Figure 1-25.
• Drop-and-continue functionality allows collocated OC-48 terminals to
drop a unidirectional signal for local use at the site and pass it to a
downstream site. The connection between the terminals must be at the DS3
level. For example in Figure 1-24, site B drops and continues a
unidirectional signal and provides both site B and site C with access to the
unidirectional signal.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-43

Figure 1-24
Implementing drop-and-continue functionality with collocated terminals
F3036-1

OC-48 OC-48 OC-48 OC-48

Terminal 1 Terminal 2 Terminal 3 Terminal 4
DS3

DS3s DS3s

Site A Site B Site C

This tributary Unidirectional traffic is This tributary

is receiving dropped by Terminal 2 is transmitting
unidirectional traffic and picked up by Terminal 3 unidirectional traffic
FW-3036.1

In Figure 1-25, OC-48 terminals located at site B allow unidirectional traffic

from site A to pass through to site C. Unidirectional traffic that originates at
site A is dropped (for example, using an STS-1 or STS-12 tributary) at
terminal 2 in site B, and added to terminal 3 at site B. The unidirectional signal
is then transmitted to site C where it is dropped. Because the unidirectional
signal is carried on an STS-1 or STS-12 connection between terminal 2 and
terminal 3, the signal cannot be accessed locally at site B as a
drop-and-continue signal.
OC-3 or OC-12 TBM, and OPTera Metro 3000 series, or OPTera Metro 3100
An OC-3 or OC-12 TBM, OPTera Metro 3000 series, or OPTera Metro 3100
can transmit or receive unidirectional signals on its tributaries, but does not
support unidirectional STS connections in both directions at the same time on
the same timeslot. Whenever a DS3 or STS-1 tributary on an OC-3 or OC-12
TBM or OPTera Metro 3000 series system is used for unidirectional traffic,
either the transmit or receive bandwidth of that tributary is lost. To fully
support unidirectional STS services, a terminal must be able to receive and
transmit independent signals on a single DS3 or STS-1 tributary. Figure 1-26
shows an OC-3 or OC-12 terminal operating with bidirectional facilities but
receiving a unidirectional signal on one of its DS3 tributaries.

The receive and transmit signals on different OC-3 or OC-12 tributaries can be
independently routed.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-44 Signal flow

Figure 1-25
Implementing passthrough functionality with collocated terminals
F3036

OC-48 OC-48 OC-48 OC-48

Terminal 1 Terminal 2 Terminal 3 Terminal 4

STS-1/
DS3s STS-12 DS3s

Site A Site B Site C

This tributary Unidirectional traffic is This tributary

is receiving passed through Site B is transmitting
unidirectional traffic FW-3036 unidirectional traffic

Figure 1-26
Routing linear unidirectional traffic through OC-3 or OC-12 TBM shelves
F3032_R12

OC-48 OC-48
terminal 1 terminal 2

DS3s

OC-3,
STS-12, The OC-3, STS-12,
or OC-12 or OC-12
carrier tributary is transmitting
unidirectional
traffic and operating
OC-3 or AIS as a bidirectional facility
OC-12 DS3s
TBM

Note: The OC-3 and OC-12 TBM network elements do not support unidirectional traffic.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-45

GR-1230 Rings
Figure 1-27 shows unidirectional traffic on a ring where there is one source
(add) point and one drop point. A DS3 tributary on ADM node 1 receives
unidirectional traffic but does not transmit traffic, while a DS3 tributary on
ADM node 3 transmits unidirectional traffic but does not receive any traffic.
ADM node 2 operates in passthrough mode. Unlike terminals in linear
systems, an ADM node in a ring can be provisioned to pass through
unidirectional traffic as well as adding or dropping it.
Figure 1-27
A single unidirectional connection on a GR-1230 Ring
F3031-1

The signal
is passed through
this node

OC-48 ring
ADM node 2 The signal
is dropped
The signal at this node
is added
at this node This tributary is
transmitting a
unidirectional
service
OC-48 ring
DS3s OC-48 ring DS3s
ADM node
ADM node 1
3

OC-48 ring
ADM node 4

DS3s

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-46 Signal flow

Figure 1-28 shows two independent unidirectional connections to the same

DS3 tributary on ADM node 3. This allows ADM node 3 to receive a
unidirectional signal that originates at ADM node 1 and transmit a
unidirectional signal to ADM node 4.
Figure 1-28
Two unidirectional signals on a single tributary
F3031

The signal
is passed through
this node

OC-48 ring
ADM node 2

The signal
is added The signal
at this node is dropped
at this node

OC-48 ring
DS3s OC-48 ring DS3s
ADM node
ADM node 1
3

The tributary is
receiving and
transmitting
independent
OC-48 ring unidirectional
ADM node 4 services

The signal is
dropped at this node

DS3s

Drop-and-continue
Unidirectional services on GR-1230 Rings support a drop-and-continue
feature which allows an ADM node to send a unidirectional signal to multiple
ADM nodes. An example of this is shown in Figure 1-29. ADM node 1 sends
a signal to ADM nodes 2, 3, and 4. The signal is dropped and continued at
ADM nodes 2 and 3, and dropped at ADM node 4.

Note: A drop-and-continue connection must occupy the same STS

timeslot throughout the ring.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-47

OC-3 or OC-12 TBM and OPTera Metro 3000 series, or OPTera Metro 3100
An OC-3, OC-12 TBM, OPTera Metro 3000 series, or OPTera Metro 3100 can
transmit or receive unidirectional signals on its tributaries, but does not support
unidirectional STS connections in both directions at the same time on the same
timeslot. Whenever a DS3 or STS-1 tributary on an OC-3 or OC-12 TBM or
an OPTera Metro 3000 series system is used for unidirectional traffic, either
the transmit or receive bandwidth of that tributary is lost. (To fully support
unidirectional STS services, a terminal must be able to receive and transmit
independent signals on a DS3 or STS-1 tributary.)
Figure 1-29
Unidirectional drop-and-continue connection on a GR-1230 Ring
F3031-2

DS3s
The signal is
dropped and
continued
at these nodes

OC-48 ring
ADM node 2

The signal
is added
at this node

OC-48 ring
DS3s OC-48 ring DS3s
ADM node
ADM node 1
3

OC-48 ring
ADM node 4

The signal is
dropped at this node

DS3s

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-48 Signal flow

Figure 1-30 shows an OC-3 or OC-12 terminal operating with bidirectional

facilities but receiving a unidirectional signal on one of its DS3 tributaries.
Figure 1-30
Routing unidirectional traffic through OC-3 or OC-12 TBM shelves
F3033-R12

The signal
is added at
this node

OC-48 ring
ADM node 2

The signal
is passed through
at this node

OC-48 ring
DS3s OC-48 ring DS3s
ADM node
ADM node 1
3

OC-48 ring
ADM node 4

The OC-3, STS-12,

or OC-12
OC-3 or tributary is transmitting
OC-12 unidirectional
TBM traffic and operating
as a bidirectional facility

Note: The OC-3 and OC-12 TBM network elements do not support unidirectional traffic.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-49

Matched nodes
Unidirectional DS3, STS-1, OC-3, STS-12, and OC-12 traffic can pass
between matched nodes in a GR-1230 Ring. Traffic entering the ring on a
mapper must be dropped to the adjacent ring over a SONET tributary. STM-1J
and Packet Edge tributaries do not support matched nodes.

For an example of a unidirectional connection across a matched-node

connection, see Figure 1-31. A DS3 drop-and-continue connection enters ring
A at node 1, is dropped at nodes 2 and 5 on ring A, and nodes 8 and 10 on ring
B. The matched-node connection between the two rings in this example uses
STS-1 interface circuit packs.
Figure 1-31
Unidirectional connections across matched nodes
F3034-R14

DS3s DS3s

OC-48 ring OC-48 ring

ADM node 2 ADM node 8

Drop point
STS-1
Primary OC-48 ring OC-48 ring
ADM node 3 ADM node 7

OC-48 ring
OC-48 ring Ring A Ring B ADM node
ADM node
Drop point 9
1
STS-1
Secondary OC-48 ring OC-48 ring
ADM node 4 ADM node 6

OC-48 ring OC-48 ring

ADM node 5 ADM node 10

DS3s DS3s

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-50 Signal flow

Signal synchronization (linear terminals)

Linear systems use several internal clocks to synchronize transport signals.
These systems may use an external synchronization interface (ESI) to give a
timing reference to the internal clocks.

The OC-48 terminal shelf can hold one full-slot ESI carrier holding up to two
ESI circuit packs. The second circuit pack is for protection. The network
element software automatically recognizes the several types of ESI circuit
packs available.

The ESI at a terminal can be either connected to a building integrated timing

supply (BITS) or loop timed from a terminal that is connected to a BITS. With
the ESI synchronization status messaging feature, the ESI can select the signal
with the highest quality level from up to four input signals. For more
information on ESI features and applications, see the chapter on network
synchronization in System Description, 323-1201-100.
External timing
When externally timed, the terminal synchronizes both the system transmit
and receive clocks to a common reference clock. The ESI generates this
reference clock from an external synchronization source such as a building
integrated timing supply (BITS).

The ESI reads the synchronization status message to select the highest quality
signal from up to two BITS input signals (BITSA and BITSB). For more
information on ESI features and applications, see the chapter on network
synchronization in System Description, 323-1201-100.
Loop timing
Loop timing is a variation of external timing. The ESI generates the reference
clock from the embedded clock signal in the OC-48 transport signal coming
from another terminal. The upstream terminal is connected to a BITS. Because
linear demultiplexers squelch optical clock signals, the ESI selects the active
(ACT) OC-48 transport signal (OCA or OCB) for a reference.

For the block diagram of the timing distribution functions of the ESI, see
Figure 1-32.
Freerun mode
In freerun mode, the terminal is not equipped with ESI circuit packs. The
system transmit and receive clocks run independently. Only use this mode for
terminals in linear systems that are equipped only with asynchronous DS3
tributaries.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-51

Through timing
Regenerators do not have ESI circuit packs. The regenerator uses the clock it
receives from an adjacent upstream network element, either a regenerator or a
terminal, to synchronize the data it transmits to the adjacent downstream
network element.
Figure 1-32
ESI external timing and the timing distribution functions—block diagram
F1973-48

ESI carrier
8-kHz OC-48 G1
ESI G1 Rx timing Dmx Rx
Sw3 reference A Ck
G1 Out DS1
Rec
Gen
38.88-MHz
Tx timing
Building BITSA Sw1 reference A Sw5
integrated
timing BITSB
Tx
supply
(BITS)
OC-48 G2
ESI G2
Dmx Rx
G2 Out Sw4
DS1
Ck
Gen
8-kHz Rec
Rx timing
reference B Sw6
Sw2

38.88-MHz Tx
Tx timing
reference B

Sw1, Sw2: Used for timing reference input protection

Sw3, Sw4: User provisioned FW-1973 (OC48)
Sw5, Sw6: Used for ESI equipment protection

Note 1: Sw1 and Sw2 move together, Sw5 and Sw6 move together.

Note 2: Under normal operating conditions, the OC-48 transmit interface of OC-48 G1 is the master timing
reference for the entire shelf. OC-48 G2 becomes the master timing reference in the event of an automatic
protection switch on OC-48 G1 or failure of the OC-48 G1 circuit pack group.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-52 Signal flow

In the OC-48 receive direction

In the OC-48 receive direction, the shelf clock source comes from the OCA or
OCB OC-48 signal and not from the BITSA or BITSB signal.
Freerun mode
When the shelf clock source is in freerun mode, the OC-48 receive interface
circuit pack extracts the timing information from the received OC-48 signal
and sends the timing information to the OC-48 demultiplexer. The
demultiplexer generates a frame/clock and distributes it to every tributary
circuit pack in the shelf. Using this frame/clock, the tributaries extract the
synchronous payload envelope (SPE) that maps the payload signal. Jitter is
minimized during the receive process because the SONET pointer does not
need to be adjusted.
ESI timing
When the shelf clock source is timed through the ESI, the OC-48 receive
interface circuit pack extracts timing information from the received OC-48
signal. The timing information goes to the demultiplexer along with the data.
SONET pointer adjustments synchronize the data to the system frame/clock.
Using the system frame/clock, the tributary circuit packs then extract the
synchronous payload envelope where the tributary signals are mapped.

The demultiplexer uses the OC-48 line timing information to generate an

8 kHz signal. The ESI uses this signal to synchronize a DS1 generator. The
DS1 output can then distribute SONET OC-48 timing.

In the OC-48 transmit direction

In the OC-48 transmit direction, the shelf clock source comes from the OCA
or OCB OC-48 signal and not the BITSA or BITSB signal.
Freerun mode
When the shelf clock source is in freerun mode, the OC-48 or STS-48 transmit
interface serving each working channel uses its own clock source to generate
a frame/clock to distribute to every tributary in the shelf. The accuracy of this
clock source is ±20 parts per million. Each tributary uses the frame/clock to
construct the STS-1 signals. Jitter is minimized during the transmission
process because the SONET pointer does not need to be adjusted.
ESI timing
When the shelf clock source is the ESI, the OC-48 transmit direction operates
as if in freerun mode. However, the OC-48 or STS-48 transmit interface
on-board clock source synchronizes to the ESI system clock. This ESI clock
has an accuracy of ±4.6 parts per million.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-53

Synchronization on the 1:N protection loop

The OC-48 or STS-48 transmit interfaces serving the working channels and
those bridged to the protection loop use their own on-board clock sources.
However, the OC-48 or STS-48 transmit interface circuit packs not bridged to
the protection loop take the frame/clock from the adjacent demultiplexer
circuit packs. Jitter is minimized during the transmission process because the
SONET pointer does not need to be adjusted.

Note: Neither the OC-48 G1 or G2 circuit pack groups on the protection

shelf nor the OC-48 G2 circuit pack group on the working shelves should
be used as a reference source for timing distribution. These circuit pack
groups carry the protection loop, and can be timed from any shelf during
protection switches. This timing arrangement could therefore change
dynamically during OC-48 protection switches.
OC-48 1:N protection loop timing: system idle
An idle system does not have any active protection switches. Enabling extra
traffic on the protection shelves does not affect the timing throughout the
protection loop.

For example in Figure 1-33, the G2 transmit interface of NE 1 is the timing

master for the east protection loop. The clock signal is passed through the east
protection loop and terminates at the G2 demultiplexer at NE 5. The G2
transmit interface at NE 5 is the timing master for the west protection loop. The
clock signal is passed through the west protection loop and terminates at the
G2 demultiplexer of NE 1.
OC-48 1:N protection loop timing: switch active
If a protection switch occurs, the G2 transmit interface of the switched channel
takes over timing from the protection channel’s G2 transmit interface. A
unidirectional or bidirectional switch mode does not affect the protection loop
timing.

For example, if NE 3 has an active protection switch, the G2 transmit interface

at NE 3 supplies timing for the following transmit interfaces.
• NE 2 G2 transmit interface
• NE 1 G2 transmit interface
• NE 5 G1 transmit interface
• NE 8 G2 transmit interface
The clock signal terminates at the G2 demultiplexer of NE 7. The timing
master on the east protection loop changes from the G2 transmit interface of
NE 5 to the G2 transmit interface of NE 7. See Figure 1-33.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-54 Signal flow

Figure 1-33
OC-48 1:N (N = 3) protection loop timing, system idle (no active protection switch)
F3361

West East
NE 1 NE 5
Protection channel

G1 G2 G1 G2
Tx Tx Tx Tx

G1 G2 G1 G2
Rx/ Rx/ Rx/ Rx/
demux demux demux demux

NE 2 NE 6

G1 G2 Channel 1 G1 G2
Tx Tx Tx Tx

G1 G2 G1 G2
Rx/ Rx/ Rx/ Rx/
demux demux demux demux

NE 3 NE 7

G1 G2 Channel 2 G1 G2
Tx Tx Tx Tx

G1 G2 G1 G2
Rx/ Rx/ Rx/ Rx/
demux demux demux demux

NE 4 NE 8

G1 G2 Channel 3 G1 G2
Tx Tx Tx Tx

G1 G2 G1 G2
Rx/ Rx/ Rx/ Rx/
demux demux demux demux

Note 1: NE 1 G2 transmit interface is the timing master for East protection loop, terminating at the NE 5 G2 demultiplexer.
Note 2: NE 5 G2 transmit interface is the timing master for West protection loop, terminating at the NE 1 G2 demultiplexer.
Note 3: If a switch occurs, the G2 transmit interface of the switched channel takes over timing from the
G2 transmit interface on the protection channel.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-55

Signal synchronization (ring ADM nodes)

The OC-48 GR-1230 Ring requires an external timing reference, such as a
BITS. See Figure 1-34. At least one ADM node in the ring must be connected
to an external timing reference. The other ADM nodes can then derive timing
(line timing) from the ADM connected to the BITS. With the ESI
synchronization status messaging feature, the ESI hardware can select the
signal with the highest quality level from up to four input signals. For more
information on ESI features and applications, see the chapter on network
synchronization in System Description, 323-1201-100.

The timing reference is derived locally through the external synchronization

interface (ESI), which is either connected to the BITS or is line timed. Each
ADM node must have at least one ESI circuit pack. A second ESI circuit pack
provides protection. The network element software automatically recognizes
the several types of ESI circuit packs available.
External mode
In an OC-48 GR-1230 Ring, you must set the ESIs on at least one add-drop
multiplexer (ADM) node to external mode. These interfaces read the
synchronization status message to select the highest quality reference from up
to two BITS signals (BITSA or BITSB). The external timing reference should
be traceable to a Stratum 1 clock source according to the SONET standard. For
an example of external timing, see Figure 1-34.
Line-timed mode
As long as at least one ADM node is timed from a BITS, the other nodes can
be line timed. These interfaces select the highest quality reference from the
OC-48 transport signal (OCA or OCB) received from one of the BITS-timed
nodes. If the quality level of both signals is the same, the ESI selects OCA.

Using a local timing source prevents a link or node failure from disrupting the
synchronization of the ring.

For an illustration of synchronization signal flow, see Figure 1-32 on page

1-51. For more information on ESI features and applications, see System
Description, 323-1201-100.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-56 Signal flow

Figure 1-34
External timing scheme in a GR-1230 Ring using a BITS at each ADM node
F2246

Timing
BITS
reference

Timing Timing
reference reference

BITS A C BITS

Timing
BITS
reference

In the OC-48 receive direction

The ADM node derives its timing from the following process:
• The OC-48 receive interface circuit pack extracts the clock from the
incoming optical signal and passes it through to the OC-48 demultiplexer.
• Each ESI derives its 38.88 MHz timing reference from either the external
or line-timed source. Each then sends a frame/clock to the STS-48 or
OC-48 transmit interface.
• The transmit interface selects the best quality reference (ACT). It
distributes this frame/clock to the demultiplexer and to the tributaries.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-57

• The demultiplexer straddles the receive and transmit timing zones. It

synchronizes the dropped traffic again to the new clock reference it
receives from the OC-48 ring transmit interface.
• Using the new frame/clock, the tributaries extract the synchronous payload
envelope (SPE) where the dropped signal is mapped.
Jitter is minimized during the receive process because the SONET pointer does
not need to be adjusted.

In the OC-48 transmit direction

The ADM node synchronizes transmission according to the following process:
• The OC-48 or STS-48 ring transmit interface derives an on-board clock
source from the external timing reference.
• The transmit interface uses the on-board clock source to generate a
frame/clock.
• The transmit interface distributes the frame/clock to the tributaries
assigned to add traffic.
• The tributaries use this frame/clock to construct the STS-1 signals
containing the payload.
Jitter is minimized during the transmission process because the SONET
pointer does not need to be adjusted.

Passthrough traffic
For passthrough traffic, the STS-48 or OC-48 ring transmit interface uses the
frame/clock from the adjacent demultiplexer circuit packs. It does not use its
own on-board clock source.

OAM&P communications
S/DMS TransportNode network elements, including OC-48, have several
means of communicating operations, administration, maintenance, and
provisioning (OAM&P) information between network elements. This type of
communication is also known as data communications. Such communications
can be established using either the SONET section data communications
channels (SDCCs), a local-area network called the control network (CNet),
Ethernet, or a combination of these methods. For an illustration of these data
communication methods, see Figure 1-35.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-58 Signal flow

Figure 1-35
Data communications in a 1:N system, where N = 3
F1629

SONET SDCC from channel 1

during a protection switch of channel 1
Terminal 1 Terminal 7
Channel P Channel P
(protection) Regenerator 5 (protection)
CNet SP SP CNet
G1E/W G1E/W
NE 1 NE 7
SDCC 1 SDCC 2
Channel 1 Channel 1
Terminal 2 G2E/W SP G2E/W Terminal 8

SDCC 3 CNet SDCC 3

NE 5 SP
CNet SP CNet

NE 2 NE 8
Regenerator 6
Terminal 3 Terminal 9
CNet NE 6
Channel 2 Channel 2
SDCC 3 SDCC 3
CNet SP SP SP CNet
G2E/W G2E/W

NE 3 SDCC 1 SDCC 2
NE 9
Channel 3 Passthru Channel 3
Terminal 4 G1E/W G1E/W Terminal 10

SDCC 3 SDCC 3
CNet SP SP CNet

NE 4 NE 10

Protection loop Protection loop

Data communications using the SONET line

The data communications between two network elements on the same SONET
line is achieved by using the SONET overhead bytes. The SONET section data
communications channels (SDCCs) operate at the section level in the SONET
hierarchy. This means that the SONET SDCCs are available at both
line-terminating equipment (LTEs) and section-terminating equipment
(STEs).

The transport SDCCs are automatically provisioned according to the system

configuration. The default provisioning provides data communications over
the OC-48 line, that is, from one OC-48 network element to the next. In
addition, SDCCs are available over OC-3, STS-12, and OC-12 tributaries. For
half-height OC-3 interfaces, there is support for SDCCs on a maximum of
eight OC-3 tributaries.

Note: The Japanese market does not use SDCCs.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Signal flow 1-59

In most configurations, the default provisioning does not have to be changed.

However, the provisioning can be manually changed to suit specific
requirements, such as for an unprotected (0:1) system, and to assign SONET
SDCCs to OC-3, STS-12, or OC-12 tributaries. For details on the default
provisioning and the possible SDCC assignments for your system, refer to
System Testing Procedures, 323-1201-222.

Data communications at a regenerator site are bidirectional. The SONET data

communications channels on both G1 and G2 circuit pack groups at the
regenerator are required to have visibility in both the eastbound and westbound
directions. The SDCCs communicate through the SONET overhead channel
and are sent out by the eastbound and westbound transmit interface circuit
packs.

The SDCC capability is provided by physical ports on the shelf processor,

called LAP-D ports. LAP-D is the data communications protocol and stands
for link access protocol for the Integrated Services Digital Network D channel.
Each physical port has access to the SONET section overhead bytes D1 to D3
in the transmit and receive directions. A number of possible SDCC
assignments can be made to each physical port, as described in System Testing
Procedures, 323-1201-222.

Note: OC-48 high performance transmitter, optical amplifier, and

bidirectional 1533/1557 nm optical line amplifier circuit packs cannot
access the SONET section data communications channels. For a
regenerator/optical amplifier shelf equipped with these circuit packs,
deprovision these data channels and their corresponding alarms to avoid
“SONET SDCC link fail” alarms.

Data communications using CNet

Every shelf processor and operations controller (OPC) is equipped with a CNet
port, which provides access to a CNet local-area network (LAN). This LAN
connects the OPC to the network elements and, when used as a SONET SDCC
bridge, interconnects for OAM&P purposes network elements that are not on
the same SONET line. For example, the terminals in the protection group at
either end of the OC-48 lines in a multishelf 1:N system are interconnected by
CNet for OAM&P purposes. For CNet engineering rules, see Technical
Specifications, 323-1201-180.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
1-60 Signal flow

Data communications using Ethernet

OC-48 regenerator/optical amplifier shelves can be equipped with an Ethernet
port if the shelf is used in an OC-192 network element application and is
equipped with only high performance transmitter, optical amplifier, or
bidirectional 1533/1557 nm optical line amplifier circuit packs. These circuit
packs do not have access to the SDCCs in the SONET overhead. Data
communications must therefore be provided by Ethernet, CNet, or by
installing an OPC in the shelf. For more information, see HPTx and Optical
Amplifier Applications, 323-1251-230. For Ethernet engineering rules, see
Technical Specifications, 323-1201-180.

Ethernet can also be used to connect an OC-192 shelf equipped with

multiwavelength optical repeaters (MORs) to an OC-48 terminal or ring
add-drop multiplexer (ADM) node. The MOR circuit pack does not have
access to the SDCCs in the SONET overhead. However, it can be provisioned
with an optical service channel (OSC) that provides data communications. For
more information, see MOR Optical Layer OAM&P, 323-1251-100.

You can also use the Ethernet port to connect an OC-48 network element with
an OPTera Metro 3000 series network element as follows:
• You can use an intershelf local area network (ILAN) port on the OPTera
Metro 3000 series network element for data communications visibility.
• You can use the central office local area network (COLAN) port to bridge
the Multiservice Managed Object Agent (MOA) and Preside or Integrated
Network Management (INM) with the OPTera Metro 3000 series network
element.
For more information on these configurations, see Software Administration
Procedures, 323-1201-303.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 2-1

OC-48 transport protection 2-

This chapter describes the automatic protection-switching features at the
OC-48 transport rate. These features protect the optical transport between
OC-48 network elements.

Table 2-1 lists the protection-switching schemes available at the OC-48

transport rate.

The OC-48 protection switching is done on a SONET line basis, between

terminals in linear systems and between add-drop multiplexer (ADM) nodes in
rings.

For 1+1, 1:1, and multishelf 1:N protection schemes, the user can select either
unidirectional or bidirectional switching modes. The default mode for these
systems is bidirectional switching. GR-1230 Rings are provisioned as
bidirectional and the mode cannot be changed.

The optical-line protection (OC-48 rate) is independent of the tributary

protection (DS3 and STS-1 tributary protection is described in Chapter 3 and
OC-3, STM-1J, STS-12, and OC-12 protection in Chapter 4). OC-48 transport
protection is controlled by the OC-48 demultiplexer in a linear system and the
OC-48 ring demultiplexer circuit pack in a ring.

OC-48 protection switching is available for circuit packs in the in-service state
and, unlike DS3 and STS-1 protection, automatic protection switching is
available during software downloads and shelf processor restarts (if the system
was previously provisioned).

OC-48 linear systems can operate without optical protection by equipping only
one OC-48 transport circuit pack group (G1). These unprotected systems are
also called 0:1 systems. In this case a failure of an OC-48 interface circuit pack
or a signal failure results in the loss of OC-48 transport traffic.

When rings are linked by the matched nodes feature, the inter-ring protection
mechanism works with the OC-48 protection switching. These interactions are
described later in Chapter 3, “Matched nodes on GR-1230 Rings”.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-2 OC-48 transport protection

Table 2-1
Protection switching at the OC-48 rate

Scheme Description

Single-shelf 1+1 systems By definition, 1+1 switching is non-revertive (that is, a second OC-48
channel takes over when the first fails, but does not revert to the first when
the failure clears).

Single-shelf 1:1 systems This configuration provides one dedicated protection channel for one
dedicated working channel with revertive switching, which means that once
a failure is cleared, the traffic reverts to the original working channel after a
user-provisionable wait-to-restore period. For a description of extended
wait-to-restore, see Chapter 9, “User-initiated protection-switching features”.

Single-shelf 0:1 systems In this configuration, there is no protection for the working channel.
(unprotected) Therefore, there is no protection switching at the OC-48 level. If a failure
occurs on the OC-48 optics, traffic is lost.

Multishelf 1:N systems This configuration provides one protection channel for N working channels,
where N is less than or equal to 11. The switching is revertive, which means
that once a failure is cleared, the traffic reverts to the original working
channel after a user-provisionable wait-to-restore period. For a description
of extended wait-to-restore, see Chapter 9, “User-initiated
protection-switching features”.
The protection channel can be equipped to carry extra traffic, which is lost
in the event of an OC-48 transport switch. Route diversity is not
provisionable in 1:N configurations and is automatically turned off. (Route
diversity is not supported in 1:N systems because each consecutive set of
regenerators must be connected by CNet, and therefore must be
collocated.)

OC-48 GR-1230 Rings This is a revertive shared protection scheme as defined by the Telcordia
(formerly known as Bellcore) GR-1230-CORE standard, with a
user-provisionable wait-to-restore feature. Shared protection means that 24
working and 24 protection STS-1 signals are carried on each of the two
fibers around the ring, which form a closed two-fiber bidirectional loop. In the
event of a protection switch, the working traffic on the affected fiber is
rerouted in the opposite direction around the ring over the protection STS
signals of the unaffected fiber.
For a description of provisionable wait-to-restore, see Chapter 9,
“User-initiated protection-switching features”.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-3

Switch initiation
OC-48 protection switching is automatically initiated on detection of the
following:
• signal failures
— loss of signal (LOS)
— loss of frame (LOF)
— line alarm indication signal (AIS)
— failure of OC-48 transport interface circuit packs
• signal degradation (at thresholds set by the user)
Note: A protection switch because of a signal degrade on a working
channel of a linear system is not dropped if a signal degrade subsequently
occurs on a protection channel. Both channels are declared degraded.
Similarly, a protection switch because of a signal degradation of a working
timeslot for a GR-1230 Ring is not dropped if a signal degrade
subsequently occurs on the corresponding protection timeslot. Both lines
are declared degraded.

The OC-48 transport interface circuit packs whose failures can result in OC-48
protection switching are the transmit interface, receive interface, and the
OC-48 demultiplexer. Failures of a transmit interface cause a protection switch
at the corresponding downstream tail-end terminal.

A signal degrade triggers automatic protection when the optical bit-error rate
(BER) exceeds a user-selectable threshold ranging from 10-4 to 10-10 (the
default is 10-6).

The user can also operate a forced or manual switch or a lockout. For
additional information on these operations, see Chapter 9, “User-initiated
protection-switching features”.

Switch times
Automatic protection switching initiated by the failure of an OC-48 signal is
detected within 10 ms. The switch is completed within 50 ms of detection. This
period includes a frame loss detect holdoff of 3 ms to prevent unnecessary
switching.

In the event of a signal-degrade condition, the detection and recovery times

varies with the user-selectable bit-error-rate (BER) threshold, as shown in
Table 2-2. Once the signal-degrade condition is detected, the switch is
completed within 50 ms. The signal-degrade condition is cleared when the
BER improves by a factor of 10 (for example, from 10-8 to 10-9).

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-4 OC-48 transport protection

OC-48 transport protection switching is not guaranteed if the protection path

is degraded above 10-6. To complete the switch, switching information (carried
in the K-bytes of the SONET overhead) must be validated on the protection
path. Switching might be delayed until valid switching information can be
passed. A “Protection switch fail” alarm becomes active if the switch is
delayed longer than 60 ms at the OC-48 rate or 150 ms for matched node
gateway protection switching in rings.

In GR-1230 Rings, the 60 ms switch time is guaranteed for a model with a

maximum size of 16 ADM ring nodes over a 1200 km fiber loop. With extra
traffic provisioned, an OC-48 protection switch is completed within 110 ms.

Note: In ring systems with eight or more ADMs, if the shelves are not
equipped with NT8E06AB demultiplexers or above, the 110 ms switch
time may be exceeded.

Table 2-2
Degrade detection and recovery times for BER thresholds

BER threshold Detection time TA-TSY-000253 detection Minimum recovery time

(see note) time requirement

10-4 40 ms 100 ms 25 ms

10-5 300 ms 1s 108 ms

10-6 3s 10 s 1.08 s

10-7 30 s 100 s 10.8 s

10-8 250 s 16.7 min 108 s

(4.2 min) (1.8 min)

10-9 2,000 s 2.8 h 1081 s

(33.3 min) (18 min)

10-10 100,000 s — 10,828 s

(27.7 h) (3 h)

Note: This table assumes uniformly distributed errors.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-5

Definitions
Line switching
According to the SONET definition, a line (see Figure 2-1 for a linear system
and Figure 2-2 for a GR-1230 Ring) is defined as that segment of a fiber
transmission system located between network elements where line overhead
originates and terminates. For example, between two terminal sites, between a
terminal and an add-drop multiplexer (ADM) site, or between two ADM sites.
A line has a head end, where traffic originates, and a tail end, where traffic
terminates. Both the head end and the tail end are defined with respect to the
direction of transmission. If the direction is reversed, so are the head and tail
ends of the line.
Figure 2-1
Typical lines in a linear system
F0036_R12

Line 1 Line 2 Line 3

Head Tail Head Tail Head Tail

Add-drop Add-drop
Terminal Regenerator multiplexer multiplexer Terminal
(Note 2) (Note 2)

DS3, STS-1, DS3, STS-1, DS3, STS-1, DS3, STS-1,

OC-3, STS-12, OC-12, STS-12 OC-12, STS-12 OC-3, STS-12,
OC-12 OC-12
Note 1: This drawing shows only one direction of transmission. If the direction of transmission is reversed,
the head end of the line becomes the tail end.

Note 2: Single-shelf ADM nodes are not available in OC-48 linear systems. However, back-to-back terminals
can be used with interconnecting tributaries to form an ADM.

Path switching
Although the transport protection occurs at the OC-48 rate, in matched node
applications of GR-1230 Rings, the inter-ring protection occurs at the STS
path level. This requires path switching from a primary STS connection to a
secondary STS connection.

For matched-node connections, protection switching within a ring (both at the

transport and tributary levels) has a higher priority than protection switching
of the STS path between rings. Consequently, when path AIS is detected on a
matched-node connection, the protection switch to the secondary path is
subject to a hold-off period of 100 ms to allow time for a protection switch to
complete at the tributary or transport levels. The protection switch of the path
then occurs within 50 ms following the hold-off period.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-6 OC-48 transport protection

Figure 2-2
Typical lines in a ring
F0036-blsr

Line 1

Head Tail

Add-drop Add-drop
multiplexer multiplexer
Tail node node Head

Regenerator Regenerator
Line 4 Line 2

Head Add-drop Add-drop Tail

multiplexer multiplexer
node node

Line 3

Tail Head

Note: This drawing shows only one of the two fibers in the ring. For the second fiber loop,
which is routed in the reverse direction, the head end of the line becomes the tail end.

Switching modes
Linear systems (those which use the 1+1, 1:1, 0:1, and multishelf 1:N
protection schemes) can use either of two switching modes: unidirectional or
bidirectional. The switching modes for these protection schemes are illustrated
in Figure 2-3. The default mode in linear systems is bidirectional.

Bidirectional switching in linear systems consists of transferring both

directions of transmission onto the protection channel, whereas unidirectional
switching transfers only the affected direction onto protection. (Unidirectional
and bidirectional protection switching are not to be confused with
unidirectional and bidirectional STS connection services.)

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-7

Figure 2-3
Unidirectional and bidirectional switching modes in a linear system—normal
and failure conditions
F0039

Working Working
Normal
condition Protection Protection

Failed channel
Working Working
Failure
condition Protection Protection

(a) Unidirectional (b) Bidirectional

Legend:
Carrying traffic
Not carrying traffic
Failed

The GR-1230 Ring scheme is inherently bidirectional and has 24 working and
24 protection STS-1 signals on each of the two fibers. For illustrations of
bidirectional switching in a GR-1230 Ring under normal and failure
conditions, refer to Figure 2-13 on page 2-26, Figure 2-14 on page 2-30, and
Figure 2-15 on page 2-32.

The switching modes of tributaries are independent of the OC-48 transport

interfaces. DS3 and STS-1 tributary protection switching is always
bidirectional. When a DS3 mapper or an STS-1 interface fails, every facility
on the failed DS3 mapper or STS-1 interface is rerouted to the protection DS3
mapper or STS-1 interface in both directions. OC-3, STS-12, and OC-12
tributaries can be provisioned for either unidirectional or bidirectional
protection switching. STM-1J tributaries are bidirectional only. Packet Edge
(formerly iPT1000) tributaries do not support equipment-level protection
switching, but do support layer 2 protection (path level). For more information
on tributary protection switching, see Chapter 4, “DS3 and STS-1 tributary
protection”, Chapter 5, “OC-3, STM-1J, STS-12, and OC-12 tributary
protection”, and Chapter 6, “OPTera Packet Edge System protection”.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-8 OC-48 transport protection

1+1 protection (non-revertive)

The 1+1 protection architecture (Figure 2-4) consists of two identical
channels, G1 and G2, both of which can carry traffic (that is, either can be the
working channel). There is no dedicated protection channel: in 1+1 protection,
one channel takes over when the other fails. This requires that a permanent
physical bridge be present at the head end.
Figure 2-4
Line protection-switching architecture—1+1 application
F1686

Active
Tail Head
G1 Head Tail

Protection
G2

Legend:
Carrying traffic
Not carrying traffic

OC-48 1+1 protection switching can be provisioned in either unidirectional or

bidirectional mode. In unidirectional mode, when a failure is detected on the
working channel, the affected live traffic is routed to the protection channel
only in the failed direction. In bidirectional mode, both directions are switched
to protection.

Figure 2-5 shows what happens at both ends of the line in the case in which,
respectively, G1 is carrying traffic and G2 is carrying traffic. At the head end
of the line, there is a permanent physical bridge between the tributary circuit
packs (DS3, STS-1, OC-3, STS-12, or OC-12) and the transport circuit packs
(OC-48 transmit interface, receive interface, and demultiplexer). At the tail
end of the line, the tributaries are instructed to accept traffic from the current
working OC-48 demultiplexer (G1 or G2).

Note: STM-1J interfaces are not supported on linear systems.

When a failure is detected on the channel carrying traffic (either G1 or G2), a

switch to the other channel (either G2 or G1) takes place. The traffic remains
on this latter channel even after the failure is cleared. This is referred to as
non-revertive switching.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-9

Figure 2-5
1+1 protection (non-revertive)
F0509_R12

G1 Active G2 Active
Active Standby
Transmit Transmit
interface interface
G1 G1
DS3, DS3,
STS-1, Standby STS-1, Active
OC-3, Transmit OC-3, Transmit
STS-12, interface STS-12, interface
OC-12 G2 OC-12 G2

(a) (b)
Head end of line: permanent bridge between OC-48 transport interface
and tributary circuit packs

Active Standby
Receive Receive
Demultiplexer
interface Demultiplexer interface
G1 DS3, G1 DS3,
G1 G1
STS-1, STS-1,
Standby OC-3, Active OC-3,
STS-12, STS-12,
Receive Receive
Demultiplexer OC-12 Demultiplexer OC-12
interface interface
G2 G2
G2 G2

Use OC-48 G1 transport optics Use OC-48 G1 transport optics

(d) (c)

Tail end of line: tributary circuit packs are instructed to accept traffic
from either the G1 or G2 demultiplexer

Legend:
Carrying traffic
Not carrying traffic

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-10 OC-48 transport protection

1:1 protection (single shelf)

A single-shelf 1:1 protection scheme consists of one dedicated protection
channel (OC-48 G2) for one working channel (OC-48 G1). When a failure
occurs on G1, the traffic switches to G2 (see Figure 2-6). When G1 is ready for
service again, the traffic automatically switches back to G1 (the original
channel) after a hysteresis (wait-to-restore) period. This is referred to as
revertive switching. The user can change the default wait-to-restore period by
using the extended wait to restore feature. For a description, see Chapter 9,
“User-initiated protection-switching features” on page 9-1.

Note: When a manual switch is active on the working channel (OC-48 G1)
and a short loss of signal (LOS) occurs on G1 (that is, from 0.3 to 1
second), the system drops the manual switch as expected, and the traffic
switches back to G1, sometimes without entering the wait-to-restore
period.

OC-48 1:1 protection switching can be provisioned in either unidirectional or

bidirectional mode. In unidirectional mode, when a failure is detected on the
working channel, the affected live traffic is routed to the protection channel
only in the failed direction. In bidirectional mode, both directions are switched
to protection.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-11

Figure 2-6
OC-48 protection switching—1:1 single-shelf system
F0075_R12

48 Transmit
interface
G1

48 Receive
To/from Demultiplexer
interface
DS3, STS-1, G1
Tributary G1
OC-3, STS-12, protection
or OC-12 48 Transmit
tributaries interface
G2

48 Receive
Demultiplexer
interface
G2
G2

(a) Normal operation

48 Transmit
interface
G1

48 Receive
Demultiplexer interface
To/from
G1 G1
DS3, STS-1, Tributary
OC-3, STS-12, protection
or OC-12 48 Transmit
tributaries interface
G2

48 Receive
Demultiplexer interface
G2 G2

(b) Failure condition with a bidirectional switch

Legend:
Carrying traffic
Not carrying traffic

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-12 OC-48 transport protection

Multishelf 1:N protection (revertive)

A 1:N protection (see Figure 2-7) scheme consists of one dedicated protection
channel for up to N working channels (channels 1 to N, where N ≤ 11). In a
multishelf 1:N system, each channel (working and protection) is terminated at
a separate shelf (that is, there is a single shelf at each end of the SONET line
for each channel, rather than having the protection and working channel both
served by a single shelf at each end of the line as in single-shelf systems).

When a failure is detected on a working channel, a request is sent to the head

end to reroute the traffic to the protection channel (head-end bridge), and the
completion of the switch takes place at the tail end.

When the failure is cleared, the traffic returns to its original channel after a
hysteresis (wait-to-restore) period. This is referred to as revertive switching.
The user can change the default wait-to-restore period by using the extended
wait to restore feature. For a description, see Chapter 9, “User-initiated
protection-switching features” on page 9-1.
Figure 2-7
Line protection-switching architecture—1:N application
F0038

Head Tail
Protection

Working channel 1

Working channel 2

Working channel 3

• •
• •
• •

Legend:
Carrying traffic
Not carrying traffic

Protection-switching operation
The protection channel is placed on a separate shelf from the working shelves.
In the event of a failure on one of the working OC-48 channels, the traffic is
rerouted to the protection channel on the protection shelf. This rerouting is
done over the protection loop, as shown in Figure 2-8.

OC-48 multishelf 1:N protection switching can be provisioned in either

unidirectional or bidirectional mode.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-13

Figure 2-8
OC-48 protection switching (1:N, where N = 11)—normal operation
F1612_R13

Demux OC-48 Rx
G1
DS3, OC-3, STS-48 Tx Protection
STS-12, or OC-12
channel
extra traffic
(optional)
OC-48 Tx

G2
Demux STS-48 Rx

Protection
loop

Channel 1
DS3 Demux OC-48 Rx
mappers or G1
STS-1 OC-48 Tx
To/from interfaces
DS3, STS-1, (G1 to G16,
OC-3, STS-12, protection)
or OC-12 or OC-3, STS-48 Tx
tributaries STS-12, G2
OC-12
interfaces Demux STS-48 Rx
• •
• •
• •
Channel 11

DS3 Demux OC-48 Rx

mappers or G1
STS-1 OC-48 Tx
To/from
interfaces
DS3, STS-1, (G1 to G16,
OC-3, STS-12, protection)
or OC-12 or OC-3, STS-48 Tx
tributaries STS-12, G2
OC-12
interfaces Demux STS-48 Rx

Legend:

= Fiber carrying traffic

= Fiber not carrying traffic

In unidirectional mode, when a failure is detected on one of the working

OC-48 channels, the affected live traffic is routed to the protection shelf over
the protection loop only in the failed direction (Figure 2-9 and Figure 2-10).
Bidirectional mode causes both directions of the failed OC-48 channel to
switch to protection (Figure 2-11). Regardless of the switch mode, all circuit
packs serving the protection loop at both terminal sites become active.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-14 OC-48 transport protection

Figure 2-9
OC-48 protection switching (1:N, where N = 11)—unidirectional switching on channel 1 (tail end)
F1614_R13

DS3, OC-3, Demux OC-48 Rx

STS-12,
G1
or OC-12
STS-48 Tx Protection
tributaries
extra traffic channel
(optional)
OC-48 Tx

G2
Demux STS-48 Rx

Protection
loop

Channel 1
DS3 Demux OC-48 Rx
mappers or G1
STS-1 OC-48 Tx
To/from interfaces
DS3, STS-1, (G1 to G16,
OC-3, STS-12, protection)
or OC-12 or OC-3, STS-48 Tx
tributaries STS-12, G2
OC-12
interfaces Demux STS-48 Rx
• •
• •
• •
Channel 11

DS3 Demux OC-48 Rx

mappers or G1
STS-1 OC-48 Tx
To/from interfaces
DS3, STS-1, (G1 to G16,
OC-3, STS-12, protection)
or OC-12 or OC-3, STS-48 Tx
tributaries STS-12, G2
OC-12
interfaces Demux STS-48 Rx

Legend:

= Fiber carrying traffic

= Fiber not carrying traffic

= Failed fiber or channel

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-15

Figure 2-10
OC-48 protection switching (1:N, where N = 11)—unidirectional switching on channel 1 (head end)
F1615_R13

Demux OC-48 Rx
DS3,
OC-3, STS-12, G1
or OC-12 STS-48 Tx Protection
extra traffic channel
(optional)
OC-48 Tx

G2
Demux STS-48 Rx

Protection
loop

Channel 1
DS3 Demux OC-48 Rx
mappers or G1
To/from STS-1 OC-48 Tx
DS3, STS-1, interfaces
OC-3, STS-12, (G1 to G16,
or OC-12 protection)
or OC-3, STS-48 Tx
tributaries
STS-12, G2
OC-12
interfaces Demux STS-48 Rx
• •
• •
• •
Channel 11

DS3 Demux OC-48 Rx

mappers or G1
To/from STS-1 OC-48 Tx
DS3, STS-1, interfaces
OC-3, STS-12, (G1 to G16,
or OC-12 protection)
or OC-3, STS-48 Tx
tributaries
STS-12, G2
OC-12
interfaces Demux STS-48 Rx

Legend:

= Fiber carrying traffic

= Fiber not carrying traffic

= Failed fiber or channel

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-16 OC-48 transport protection

Figure 2-11
OC-48 protection switching (1:N, where N = 11)—bidirectional switching on channel 1
F1613_R13

Demux OC-48 Rx
DS3, OC-3, G1
STS-12, or OC-12 STS-48 Tx Protection
extra traffic channel
(optional)
OC-48 Tx

G2
Demux STS-48 Rx

Protection
loop

Channel 1
DS3 Demux OC-48 Rx
mappers or G1
STS-1 OC-48 Tx
To/from interfaces
DS3, STS-1, (G1 to G16,
OC-3, STS-12, protection)
or OC-12 or OC-3, STS-48 Tx
tributaries STS-12, G2
OC-12
interfaces Demux STS-48 Rx
• •
• •
• •
Channel 11
DS3 Demux OC-48 Rx
mappers or G1
STS-1 OC-48 Tx
To/from interfaces
DS3, STS-1, (G1 to G16,
OC-3, STS-12, protection)
or OC-12 or OC-3, STS-48 Tx
tributaries STS-12, G2
OC-12
interfaces Demux STS-48 Rx

Legend:

= Fiber carrying traffic

= Fiber not carrying traffic

= Failed fiber or channel

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-17

Each OC-48 channel can be assigned a protection-switch priority of either high

or low. A failure on a high-priority OC-48 channel forces any low-priority
traffic off the protection channel. However, these protection-switch priority
settings are relevant only when the protection switch is an automatic protection
switch, as the priority settings have no effect on user-initiated protection
switches.

The protection loop is typically routed over coaxial cables at an STS-48 rate.
However, if the shelves in the protection group are more than 30 m (98 ft.)
apart, optical (OC-48) interfaces must be used.

Each working shelf in the protection group has two circuit pack groups (G1
and G2) for the OC-48 transport interfaces. G2 on each working shelf is
dedicated to the protection loop and G1 is dedicated to the working channel.

On the protection shelf, the G1 transmit circuit pack serves the protection loop
(it is therefore an STS-48 transmit interface circuit pack), and the G1 receive
interface serves the OC-48 transport protection fiber. The G2 receive interface
serves the protection loop and the G2 transmit interface serves the OC-48
transport protection fiber.

If required, extra traffic can be carried on the protection channel. A failure on

one of the working channels (regardless of the channel priority) overrides extra
traffic. Refer to Chapter 10, “Extra traffic”, for a detailed description of the 1:N
extra traffic feature.

K-byte signaling in a 1:N system

Automatic protection switch requests are sent by the working terminal
detecting the failure to the far-end terminal using the K1 byte in the SONET
overhead. When the far-end terminal receives the request, it initiates the
protection switch. If the switch is successful, the far-end terminal signals back
using the K2 byte. The near-end terminal compares the channel number in the
K2 byte with the channel that is requesting the switch. If the bytes are the same,
the near-end terminal completes the switch to the protection loop. The K-bytes
are defined in Table 2-3 to Table 2-7.

Table 2-3
K1 byte definitions

Active switch request Active switch request channel

identifier

7 6 5 4 3 2 1 0

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-18 OC-48 transport protection

Table 2-4
K1 active switch request channel identifier

K1 value Channel identifier Active switch request

(bits 7 through 4) (bits 3 through 0)

1100 0 Low priority signal fail

1111 0 Lockout of protection

1110 0 to 15 Forced switch

1101 1 to 14 High priority signal fail

1100 1 to 14 Low priority signal fail

1011 0 to 14 High priority signal degrade

1010 0 to 14 Low priority signal degrade

1000 0 to 15 Manual switch

0110 1 to 14 Wait to restore

0100 1 to 15 Exerciser

0001 0 or 1 Do not revert

0000 0 Idle or no request

0000 15 Extra traffic

0010 0 to 15 Reverse request

Table 2-5
K2 byte definitions

Identifier of channel Protection Status code

bridged to protection scheme

7 6 5 4 3 2 1 0

Table 2-6
K2 protection scheme field (bit 3)

Value Protection scheme

1 1:N

0 1+1

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-19

Table 2-7
K2 status code field (bits 0 to 2)

Value Status code

111 Line AIS

110 Line RFI

101 Bidirectional switch mode

100 Unidirectional switch mode

011 Reserved

010 Reserved

001 Reserved

000 Line RFI clear

Protection loop
The protection loop can serve only one channel at a time, regardless of the
protection-switching mode. For example, if a channel fails in one direction, a
subsequent failure on any other channel in either direction has its
protection-switch request denied, except when the protection-switching
priority of the second failed channel is higher than that of the currently
protected channel. In that case, the first protection switch is dropped and the
higher-priority channel is protected instead.

Note 1: In multishelf 1:N systems, the protection loop is a bidirectional

loop. A failure at any point on the loop causes the entire loop to be
unavailable. OC-48 transport protection is then unavailable until the
protection-loop continuity is restored.
Note 2: In the case of unidirectional extra traffic, the extra traffic in the
unaffected direction is not affected by a protection switch from a working
channel to protection in the other direction. Only the extra traffic in the
direction experiencing the protection switch is lost.
Note 3: On a 1:N system with unidirectional switching and a lockout of
protection (LOP) in one direction, any attempt to switch traffic from a
working channel to the protection channel in the opposite direction to the
LOP will cause the working traffic to be lost.
Protection oscillation control
Each terminal in the system monitors the number and duration of
protection-loop failures and automatic switch requests. If the number of
failures and protection switches exceed thresholds set by the network element
software, an alarm becomes active. This protection oscillation alarm indicates
that there is potentially a condition on the system, such as equipment
degradation, that is causing multiple protection switches over a period of time.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-20 OC-48 transport protection

Such protection switches may clear on their own, resulting in the traffic
reverting to the working channel after the wait-to-restore period. A further
protection switch might then later occur. Such repeated protection switches are
referred to as oscillating protection switches.

Before raising the alarm, the network element monitors the duration of all
protection-loop failure conditions and automatic switch requests. It also
monitors the time that elapses between each consecutive failure or automatic
switch request.

The alarm becomes active based on the frequency of failures and requests over
various time thresholds. For example, some protection switches resulting from
progressive degradations might occur every few days, with increasing
frequency over time. Other failures might result in multiple protection switch
requests in the span of milliseconds. (Failures with a duration of less than
300 ms might not be detected for the purposes of this alarm.)
Protection oscillation control with the misconviction prevention capability
The misconviction prevention capability, when enabled, enhances the
protection oscillation control feature. This capability ensures that in cases of
severe protection oscillation, the circuit pack is not indicated as failed.

The misconviction prevention capability is triggered when the “Protection

oscillation, type Q FWPROSCI” alarm becomes active. In such a case, this
capability prevents the network element software from raising certain OC-48
equipment alarms against the transmit interface and the demultiplexer. Such
alarms can still become active, however, if a hardware fault is detected. For a
list of the affected equipment alarms, see the “Protection oscillation, type Q
FWPROSCI” alarm-clearing procedure in Alarm Clearing Procedures,
323-1201-543.

This capability is enabled by default, but the user can enable or disable it
manually by using the FWPROSCI command interpreter (CI) tool. This CI
tool can query information related to the protection switches and can clear the
“Protection oscillation, type Q FWPROSCI” alarm. For instructions on how to
enable and disable the 1:N misconviction prevention capability, see Protection
Switching Procedures, 323-1201-311.
Extended wait-to-restore
The user can also set the wait-to-restore period to control protection oscillation
(extended wait-to-restore). For example, the user could provision a
wait-to-restore period of infinity, thereby preventing any occurrences of
protection oscillations. For a description of this feature, see “Protection
oscillation control in single-shelf 1:1 and multishelf 1:N systems (extended
wait to restore)” on page 9-16.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-21

Orderwire protection in 1:N multishelf systems

The orderwire is protected only on channel 1 in a 1:N system. Local and
express orderwire are not protected during a protection switch on other
channels. For more information on orderwire, see System Description,
323-1201-100.

Data communications protection in multishelf 1:N systems

The OC-48 S/DMS TransportNode uses a combination of SONET section data
communication channels (SDCCs) and the control network (CNet) local-area
network to communicate operations, administration, maintenance and
provisioning (OAM&P) information between network elements in a 1:N
system (see Figure 2-12).

The shelf processor provides the physical circuitry that accesses the CNet and
the SONET SDCCs. There is one physical CNet port per shelf processor. The
physical ports access the section overhead bytes (D1 to D3) in the transmit and
receive directions, and the SDCCs are carried in the SONET overhead.
Depending on the type of shelf processor, there are either two or ten physical
ports to support SDCCs. For the provisioning rules to assign SDCCs to OC-48
lines and tributaries, see System Testing Procedures, 323-1201-222.

Information is passed between the terminals in a protection group (one

terminal site in the 1:N system) by means of the CNet. Information is passed
between the terminals of the two protection groups over the OC-48 fiber lines
using the SONET SDCCs. The SDCCs are provisioned according to whether
a given shelf is an OC-48 terminal shelf or an OC-48 regenerator/optical
amplifier shelf.

Except for channel 1, the SONET SDCC overhead bytes are neither accessed
nor modified on regenerator/optical amplifier shelves for the odd 1:N channels
(3, 5, 7, 9, and 11). That is, the SDCCs are assigned only to the G2 east and G2
west regenerator circuit pack groups. For the G1 east and G1 west regenerator
circuit pack groups, the SONET SDCC overhead bytes are passed through
with the rest of the payload directly to the terminal network element at the
other end of the line.
SDCC protection
When one of the working OC-48 channels fails, payload traffic is
automatically rerouted to the protection channel. Protection is therefore
provided for all working channels (though only one channel can switch to
protection at a time).

However, because the protection channel passes through the same

regenerator/optical amplifier shelves as working channel 1, only the SDCC on
working channel 1 is protected. That is, when working channel 1 switches to
the protection channel, the shelf processor at the regenerator/optical amplifier

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-22 OC-48 transport protection

shelves serving these channels (regenerator 5 in the example in Figure 2-12)

reassigns the SDCC from G2 east and G2 west to G1 east and G1 west along
with the payload.

When other channels (2 to 11) are switched to protection, working channel 1

is still using the only available SDCCs on regenerator 5, and therefore the
SDCCs on working channels 2 to 11 cannot be protected.

If, for instance, the fiber for channel 2 between terminal 3 and regenerator 6 is
cut, the traffic is protected by the protection channel, but not the SDCC,
because the SDCCs at regenerator 5 are already used to route the SDCC of
channel 1. However, OAM&P visibility to the shelves on the troubled channel
are not lost because of the CNet connections at both protection groups.

In this failure example, both terminal 3 and regenerator 6 raise alarms.

Communications between the two network elements are then rerouted by way
of CNet and other fiber channels using the shortest path. For example, if
working channel 2 fails, the data communications between terminal 3 and
regenerator 6 is reestablished using the following path:
• CNet between terminal 3 and terminal 2
• fiber between terminal 2 and regenerator 5
• CNet between regenerator 5 and regenerator 6
Although data communications traffic takes the above route, the SDCC itself
is not restored. In addition to the alarms caused by the failure condition, both
ends of the SDCC link (terminal 3 and regenerator 6) have “SONET DCC link
fail” alarms.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-23

Figure 2-12
Data communications in 1:N systems—normal operation
F1629

SONET SDCC from channel 1

during a protection switch of channel 1
Terminal 1 Terminal 7
Channel P Channel P
(protection) Regenerator 5 (protection)
CNet SP SP CNet
G1E/W G1E/W
NE 1 NE 7
SDCC 1 SDCC 2
Channel 1 Channel 1
Terminal 2 G2E/W SP G2E/W Terminal 8

SDCC 3 CNet SDCC 3

NE 5 SP
CNet SP CNet

NE 2 NE 8
Regenerator 6
Terminal 3 Terminal 9
CNet NE 6
Channel 2 Channel 2
SDCC 3 SDCC 3
CNet SP SP SP CNet
G2E/W G2E/W

NE 3 SDCC 1 SDCC 2
NE 9
Channel 3 Passthru Channel 3
Terminal 4 G1E/W G1E/W Terminal 10

SDCC 3 SDCC 3
CNet SP SP CNet

NE 4 NE 10

Protection loop Protection loop

Because the protection channel is used to protect the SDCC of channel 1, the
two OC-48 terminals handling the protection channel (terminals 1 and 7) have
no SDCCs of their own provisioned. Consequently, they can only
communicate with the other network elements in the system using the CNet
connections.

Because working channel 1 is the only channel with protected SDCC, all
same-site network elements, including regenerators, must be connected to
each other by CNet. Because CNet is a local-area network that requires all its
connected nodes to be collocated, 1:N systems must be configured for
non-route diversity so that the regenerators for each all the channels (working
and protection) can be collocated at each consecutive regenerator site.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-24 OC-48 transport protection

Protection in an OC-48 GR-1230 Ring (revertive)

The OC-48 can be configured as a two-fiber bidirectional line-switched ring
(BLSR), called the OC-48 GR-1230 Ring. This protection scheme complies
with the Telcordia (formerly known as Bellcore) GR-1230-CORE standard
and supports bidirectional switching of the SONET line between add-drop
multiplexer (ADM) nodes. One OC-48 terminal shelf is configured as each
ADM node in the ring.

The GR-1230 Ring is a shared protection ring, which means that the 48 STS-1
timeslots on each of the two fibers in the ring are equally shared between
working and protection functions (that is, there are 24 working and 24
protection STS-1 signals on each fiber).

The two fibers form independent closed loops, which allow traffic to be routed
in both directions around the loop (see Figure 2-13 on page 2-26). This
provides an alternate route for traffic in the event of a link or node failure.
Should a link (Figure 2-14 on page 2-30) or a node (Figure 2-15 on page 2-32)
fail, the working traffic on the affected fiber is bridged to the protection
timeslots on the second fiber and rerouted in the opposite direction around the
ring to the intended destination. During an active protection switch, the
protection timeslots are used on all the spans of the ring.

The GR-1230 Ring is revertive; after a failure is cleared, traffic reverts from
the protection STS signals on one fiber to the working STS signals on the
second fiber. The wait-to-restore period is user-provisionable (the default is
5 minutes). The fibers are terminated at each ADM node by the circuit pack
groups that form their optical interfaces, G1 and G2. These optical interfaces
provide the add-drop multiplexing and demultiplexing.

The number of STS-1 signals to be added and dropped is provisionable on an

ADM-by-ADM basis. The STS-1 signals can be added and dropped using
various formats, by way of DS3, STS-1, OC-3, STM-1J, STS-12, OC-12, or
Packet Edge tributaries. As well, traffic can be passed through from one ADM
node in the ring to the next by way of tributaries. With the matched-nodes
feature, interconnections between rings can be protected on an STS path basis
using path-switched protection (using STS-1, OC-3, STS-12, or OC-12
tributaries only).

The ring ADM nodes are spaced apart according to engineering limits for links
and can use regenerators between nodes. Regenerators do not take part in the
protection switching.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-25

Normal operation
The traffic on each of the two fibers between adjacent ring ADM nodes is
assigned a specific direction of transmission, with the traffic on one fiber
routed in the opposite direction from the traffic on the other fiber. Of the 24
working and 24 protection timeslots on each fiber, the lower-numbered
timeslots (STS-1 timeslots 1 to 24) are the working timeslots and the
higher-numbered timeslots (25 to 48) are the protection timeslots.

The working timeslots on one fiber are paired off with the protection timeslots
on the second fiber. Working timeslots 1 to 24 on fiber 1 are protected by
protection timeslots 25 to 48 on fiber 2, respectively. Conversely, the working
timeslots 1 to 24 on fiber 2 are protected by protection timeslots 25 to 48 on
fiber 1. The logical signal flow under normal operation is shown in
Figure 2-13.

Any tributary signal can be assigned to any STS-1 timeslot on the OC-48
optical line. Each STS signal at any given ADM node is designated as an add,
drop, or passthrough signal. Any combination of added, dropped, and
passthrough signals is allowed up to the maximum of 48 working timeslots per
ADM node. The maximum capacity of the ring is 48 STS-1 equivalents per
node in the ring (24 per each fiber on each span).

The physical fiber and optics equipment (OC-48 G1 or G2) carrying the traffic
is determined by the routing (the long or short route around the ring) rather
than by explicit assignment to G1 or G2. That is, a given STS-1 timeslot (for
example, STS-1 number 1) can have two connections provisioned against it,
one for the long route and one for the short route.

To achieve maximum bandwidth use, traffic between ADM nodes is usually

routed along the shortest path. Using the example in Figure 2-13, traffic
intended to travel between nodes A and B is normally routed directly from A
to B. This leaves the same-numbered working timeslots free for use by other
connections from A to D to C to B. Any given STS payload assigned within
the ring must remain within the same working timeslots in each line it uses.

Because of the bidirectional ring configuration of the two fibers, if a payload

requirement is greater than can be carried by one fiber (that is, more than 24
STS-1 timeslots), the additional payload can be routed over the working
timeslots of the second fiber. If, for example, connections between nodes A
and C require 28 STS-1 timeslots, some of the requirements can be routed from
A to B to C and the remainder from A to D to C.

Protected operation
The ring backbone is designed to protect against catastrophic failures such as
optical line cuts, ADM node failures, regenerator failures, and signal
degradation through its bidirectional shared-protection architecture.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-26 OC-48 transport protection

The GR-1230 Ring automatically detects and isolates trouble and reroutes
traffic around the failed portion of the ring within milliseconds (a maximum of
10 ms switch-detection time with up to an additional 50 ms for switch
completion). In the event of multiple faults, the ring backbone divides into as
many individually protected segments as required to restore traffic within the
interconnected subnetworks.
Figure 2-13
GR-1230 Ring—normal operation
F2142

(Add-drop)
A-D A-B

Fiber 1
A
Ring ADM node

Fiber 2

D-A B-A
D-C D B B-C
D-B B-D

Passthrough
(D-B)

Legend:

= Single fiber cable with 24 working

and 24 protection timeslots C-D C-B

= Working STS-1 timeslots (1 through 24)

= Protection STS-1 timeslots (25 through 48)

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-27

The protection switching is invoked on the basis of a node map contained in

each of the two OC-48 ring demultiplexer circuit packs of each ring ADM
node which defines the order of the ADM nodes around the ring.

The node map is created using the OPC Configuration Manager tool. It assigns
to each ADM node in the ring a unique automatic protection switch identifier
(APS ID), in addition to the usual 1- to 5-digit network element number. The
APS ID is a number from 0 to 15 (with 16 ADM nodes being the maximum
allowed in the ring according to the Telcordia (formerly known as Bellcore)
GR-1230-CORE standard). A single OPC can support several rings, up to the
limits of its span of control.

Protection switching occurs on a line basis, at the ADM nodes on either side
of the failure. No protection switching occurs at regenerator sites. As well as
having a map of its position in the ring relative to its two neighboring ADM
nodes, each node is also provisioned with the interconnections of the fiber
spans between it and its neighbor nodes based on their respective optical
interfaces, circuit pack groups G1 and G2.

The circuit pack groups can be interconnected between neighboring nodes in

any combination of G1 to G1, G1 to G2, or G2 to G2. When a failure occurs,
a protection switch is initiated (using K-byte signaling in the SONET
overhead) on the basis of the APS IDs of the appropriate ADM nodes and is
applied at the circuit pack group level.

Automatic switches occur whenever an ADM within the ring detects a loss of
the optical signal, an optical equipment failure (that is, a failure of G1 or G2),
or a signal degrade (a bit error rate greater than a provisioned threshold).

The operations controller (OPC) monitors the protection status of all the ADM
nodes in the ring on a scheduled basis and reports this information as event
logs. The OPC also periodically audits the node map, circuit pack group
provisioning, and STS-1 connections on a scheduled basis to ensure
consistency of provisioning information throughout the ring.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-28 OC-48 transport protection

K-byte signaling in a ring

The GR-1230 Ring protection is based on the SONET line layer and is
activated by the SONET K-bytes. The K-bytes are structured so that a network
element or node that requests a switch can identify itself as the source node and
broadcast the destination node to which the request is directed. The K-byte
structure is shown in Table 2-8 and Table 2-9.

Table 2-8
K1 byte functions

Switch priority Destination node

Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8

Table 2-9
K2 byte functions

Source node identifier Long or Status

short path

Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8

All the nodes in the ring network constantly monitor the K-bytes. If a switch
request is issued, all the nodes in the network know which node issued the
request and the node to which it is destined. If a node detects a switch request
and the node is not the destination node, it relays (or passes through) the
K-bytes to the next node. The nodes participating in the protection switching
are considered to be in the active (or switching) state. Nodes that are passing
through (or relaying) K-bytes are considered to be in the passthrough state.
When there is no protection-switching activity in the network, all the nodes are
considered to be in the idle state.
Protected operation—link failure
A link failure can occur as the result of an isolated circuit pack failure, a cut
fiber optic cable, or a regenerator failure. In such an event, the GR-1230 Ring
enters into a bidirectional protected state of operation, as shown in Figure 2-14.
Because the ring protection scheme is based on the SONET line layer, all
protection operations are invoked at the line-terminating equipment (ring
ADM nodes) adjacent to the fault.

When a link failure occurs, traffic intended to traverse the working STS-1
timeslots of the affected fiber must be rerouted to the protection STS-1
timeslots on the second fiber, and proceed in the opposite direction around the
ring to the destination node. In the event of a failure on fiber 1, traffic on
working timeslot 1 on fiber 1 is bridged to protection timeslot 25 of fiber 2,
timeslot 2 to 26, and so on. Similarly, in the event of a failure on fiber 2,
working timeslot 1 of fiber 2 is bridged to protection timeslot 25 of fiber 1 and
so on.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-29

Figure 2-14 shows a fiber-cable cut between nodes D and C. When the link
failure is detected, add, drop, and passthrough traffic intended to traverse that
link is treated as follows:
• Tributaries (DS3, STS-1, OC-3, STM-1J, STS-12, OC-12, or Packet Edge)
that are to be added by way of tributary circuit packs are bridged onto the
appropriate protection STS-1 timeslots (on the unaffected fiber) that
correspond to the normal working timeslots (of the affected fiber), and are
routed in the opposite direction around the ring (that is, from D to A to B
to C or from C to B to A to D).
• Similarly, at nodes D and C, the STS-1 timeslots that are to be dropped to
tributaries (DS3, STS-1, OC-3, STM-1J, STS-12, OC-12, or Packet Edge)
are received from the protection timeslots on the unaffected fiber (and in
the opposite direction from the working timeslots as normal).
• Passthrough traffic that normally transits through nodes D and C is bridged
from the working STS-1 signals to the corresponding protection STS-1
signals, and switched from the protection to the corresponding working
timeslots. For example, traffic from node B in Figure 2-14 (normally
intended to pass through node C to node D) is sent to node C on the normal
working timeslots, then looped back at node C onto the corresponding
protection timeslots on the opposite fiber back to node B, then on to
node D by way of node A.
Figure 2-14 shows both cables cut, to illustrate the circumstances should the
fiber for either or both directions be cut. Because the ring is route diverse
(which means both fibers use different routes between ADM nodes), it would
be rare for both fibers to be cut as part of the same outage. When a fiber is cut,
the receiving node signals the upstream transmitting node using the K-bytes to
initiate a bridge.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-30 OC-48 transport protection

Figure 2-14
GR-1230 Ring—link failure
F2141

(Add-drop)
A-D A-B

Fiber 1
A
Ring ADM node

Fiber 2

D-A B-A
Passthrough
D-C D B-C
(D-B)
D-B Bridge B
B-D
(D-B)

Fiber cable cut

Loopback
(D-B)
C

Legend:

= Single fiber cable with 24 working

and 24 protection timeslots C-D C-B

= Working STS-1 timeslots (1 through 24)

= Protection STS-1 timeslots (25 through 48)

For example, if a signal fail is detected at ADM node C, ADM node D is

signaled by way of the K-bytes on both the short and the long paths. In the case
of a single fiber being cut, the upstream ADM node receives the bridge request
from both directions. In the case of both fibers being cut, as shown in
Figure 2-14, the upstream ADM node can receive the bridge request only over
the long route, as the fiber cut makes the short route (ADM C to D)
unavailable.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-31

The K1 byte includes the information that ADM node D is the destination node
(using its APS ID) and the switch priority is set as “signal fail protection”. The
K2 byte on the short path is set to indicate the APS ID of ADM node C as the
source node for the switch request. The K2 byte on the long path indicates the
status of the switch. When ADM node D receives the switch request on either
the short or long path, it issues a return message requesting a “signal fail
protection” request to ADM node C on the long path. This signal from ADM
node D to C ensures the completion of a bidirectional switch. (This return
request is also sent from node D to C over the short path, but cannot reach its
destination because of the fiber cut.)
Protected operation—node failure
In the event of a node failure, the GR-1230 Ring enters into a bidirectional
protected state of operation, as shown in Figure 2-15. The protection operation
is much the same as for the loss of a link, except that add-drop traffic at the
affected node is lost.

Figure 2-15 illustrates a failure of node C. Traffic normally intended to pass

through node C is looped back to the appropriate protection timeslots at nodes
B and D. The traffic is then routed to the intended destinations as described for
link failures. The nodes performing the protection switch are termed switch
nodes.

During protection switching, traffic that normally exits the ring at the lost node
has the potential to be misconnected to another path termination. To ensure
that this does not happen, the nodes adjacent to the failed node (in the example,
nodes B and D) squelch the appropriate working and protection paths by
inserting into them a path AIS (alarm indication signal) before completing the
protection switch. These paths continue to be given path AIS until the ring
returns to normal operation.

The squelching is performed by the switch nodes on the basis of a squelch map
that is automatically derived from the node map and STS-1 cross-connection
map when these maps are provisioned. The squelch map has an entry for each
STS-1 cross-connection provisioned at the ADM node. Each entry contains the
APS IDs of the nodes providing the service access point (SAP) and end node
for that STS-1.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-32 OC-48 transport protection

Figure 2-15
GR-1230 Ring—node failure
F2140

(Add-drop)
A-D A-B

Fiber 1
A
Ring ADM node

Fiber 2

D-A B-A
D-C (AIS) D B
B-C (AIS)
D-B Bridge B-D
(B-D)

Node
failure
Legend:

= Single fiber cable with 24 working C-D C-B

and 24 protection timeslots
= Working STS-1 timeslots (1 through 24)
= Protection STS-1 timeslots (25 through 48)
AIS = Alarm indication signal

If a node loses communication with the SAP or end node for a particular STS-1
(for example, because of a failure of the SAP or end node or because of a ring
segmentation isolating the SAP or end node), it can then squelch the path.
Passthrough connections at the failed node are not squelched, as these can be
successfully rerouted over the protection path. Figure 2-16 shows an example
of a four-node ring with four STS-1 paths (a, b, c, and d). The arrows indicate
the direction of each path, from the originating node (SAP) to the end node.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-48 transport protection 2-33

Figure 2-16
STS paths and squelch map for a four-node GR-1230 Ring
F2247

Node A Node B
STS #3
(path a)
(path b) (path b)
(path c)

STS #1 STS #2 STS #2 STS #3

Line

STS #2
(path c) (path a)
STS #1 (path d)
(path d)

Node D Node C
Line

The following table specifies the squelch map for node D:

Connection SAP node ID End node ID

b A B

c D A

d C D

If node D fails, path c is squelched at node A and path d is squelched at node C.

Path b is not squelched, as the path is rerouted from node A to node B by the
protection switch. Path a is unaffected by the protection switch, as it does not
route through the failed node.

The ADM nodes periodically perform a scheduled audit of all provisioned STS
connections, which compares the squelch map stored in the network element
database with the squelch map stored in the OC-48 ring demultiplexer circuit
packs. If a discrepancy is found, the version in the demultiplexers is
overwritten with the version from the network element database.

Extra traffic on a ring

Extra traffic on a ring is preempted by protection switches. For a description
of extra traffic, see “Extra traffic on GR-1230 Rings” on page 10-5 of Chapter
10.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
2-34 OC-48 transport protection

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 3-1

Matched nodes on GR-1230 Rings 3-

This chapter describes the matched-node feature available with the OC-48
GR-1230 Ring. The GR-1230 Ring is a bidirectional line-switched ring.

The matched-node feature supports both the drop-and-continue on working

(DCW) and drop-and-continue on protection (DCP) schemes. The DCW
scheme uses only working timeslots on the OC-48 optics. The DCP scheme
uses a combination of working and protection timeslots. This chapter describes
these schemes in detail.

Overview
As shown in Figure 3-1 and Figure 3-2, a matched-node connection provides
redundant STS routes between two rings. Tributary connections provide the
routes (called feeds) between rings. One feed connects an add-drop
multiplexer (ADM) node in one ring with an ADM node in the adjacent ring.
Similarly, the second feed connects two different ADM nodes, one in each
adjacent ring.

The two feeds carry an identical signal. An ADM node that serves as a
broadcast point drops the signal at a tributary. This tributary serves one of the
two feeds of the matched-node connection.

At the same time, the broadcast node bridges the signal to the outgoing OC-48
transport optics to be routed to another ADM node in the same ring. This other
ADM node serves as the matched node for the connection. It drops the signal
over a tributary to the adjacent ring. The OC-48 optics in the second ring then
routes the signal to the same node that receives the signal dropped at the first
tributary.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-2 Matched nodes on GR-1230 Rings

Figure 3-1
Matched nodes in OC-48 GR-1230 Rings (STS connections spanning multiple rings)
F2569

Source
Service access point

Broadcast
Ring A point
(3 ADM nodes)

Secondary feed

Secondary
feed
Decision
point
Primary feed
Primary
Secondary feed Secondary
node
(selector node
node)

Ring B
(6 ADM nodes) Intermediate
(passthrough)
node

Broadcast
point

Secondary feed

Decision
point Primary feed Secondary feed
Primary
Secondary feed
node Secondary
(selector node
Ring C node)
(4 ADM nodes)

Destination
End
node

Legend:
= Inter-ring STS path
= Fibers not used by the STS path

Note: For clarity, only one direction of the STS path is shown.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-3

Figure 3-2
Matched nodes in OC-48 GR-1230 Rings (opposite direction)
F2569-6

Destination

Decision
point
Ring A
Primary Secondary feed
(3 ADM nodes) Secondary
node
(selector node
node)

Primary Secondary
feed feed

Secondary feed
Broadcast
Ring B point
(6 ADM nodes) Intermediate
(passthrough)
node
Decision
point

Primary Secondary feed

node Secondary
(selector node
node)

Primary Secondary
feed feed

Secondary feed
Ring C
(4 ADM nodes) Broadcast
point

Source
End
node

Legend:
= Inter-ring STS path
= Fibers not used by the STS path
FW-2569.6

Note: For clarity, only one direction of the STS path is shown.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-4 Matched nodes on GR-1230 Rings

The node that receives both signals can compare them and select the one to use.
It is therefore called a selector node. The signal it receives by way of a tributary
is the primary feed and is the signal used in normal circumstances. In SONET
terminology, the selector node is the primary node.

Tributaries
Matched-node connections between rings offer an additional level of
protection over and above the protection offered by tributaries. Any tributary
link can be protected by a protection circuit pack. Matched-node protection
takes effect if the protection provided by the tributary fails or if there is a
second failure that causes the tributary protection to be unavailable.

Matched-node connections link two pairs of ADM nodes, one pair from each
ring. The tributary links between rings are called gateways. There is a primary
gateway and a secondary gateway. Matched-node gateways require SONET
tributaries (STS-1, OC-3, STS-12, or OC-12).

Note: The STM-1J and OPTera Packet Edge System (formerly iPT1000)
interfaces do not support matched-node connections.

You can establish non-matched-node connections between rings over DS3,

STS-1, OC-3, STM-1J, STS-12, or OC-12 tributaries. If you convert a DS3
connection between rings to a matched-node connection, you must replace any
DS3 tributaries at the gateways with SONET tributaries (for example, STS-1
interfaces). However, you can use DS3 tributaries as service access points
(SAPs) to matched-node connections.

Matched-node connections can provide a continuous STS path through any

number of rings.

Protection scheme
The links between rings (primary and secondary gateways) have path-switched
protection on a 1:1, revertive basis at the STS level. The matched-node
protection is in addition to the standard tributary protection at the equipment
and facility level on the affected ADM nodes.

Matched-node connections can be configured to use either the DCW or DCP

schemes, or both schemes together in a single connection.

STS connection rates

Matched-node STS connections can be unidirectional or bidirectional STS-1,
STS-3c or STS-12c connections.

STS-3c matched-node connections must use OC-3, STS-12, or OC-12

tributaries. STS-12c concatenated signals must use STS-12 or OC-12
tributaries.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-5

Gateway nodes
Matched-node links between rings occur over gateways. The gateways are
located at ADM nodes. Each gateway is assigned to a given STS path between
the rings. One gateway for each side of a ring boundary is designated the
primary gateway. The other is designated the secondary gateway.

The designation of primary and secondary gateways is a logical assignment on

the basis of the STS paths. A given physical ADM node can therefore be
designated as the primary gateway node for some STS connections and as the
secondary gateway node for others.

OPC Connection Manager

The Connection Manager tool on the operations controller (OPC) provides the
user interface for provisioning matched-node connections. It also provides for
user-requested protection switches (forced switches) of matched-node
connections.

Because each ring can be served by its own OPC, typically more than one OPC
is required to provision an STS path spanning multiple rings. Each OPC is used
to provision the portion of the STS path that traverses the network elements
within its span of control. Care must be taken to ensure that provisioning is
aligned in both OPCs for each STS connection between the two spans of
control. Such connections are called mid-span meet or span-of-control meet
connections.

The OPC also monitors the protection-switching status for matched-node

connections within its span of control. A single OPC can monitor several rings,
up to the limits of its span of control.

Drop-and-continue on working (DCW)

During normal operation, the DCW scheme uses only working timeslots for
the portion of the matched-node connection on the OC-48 optics. Normal
operation means that there are no protection switches active on the OC-48
transport optics.

Normal operation
Figure 3-1 on page 3-2 shows an example of a single direction of an STS path
traversing three rings, which applies to either a unidirectional connection or
one direction of a bidirectional connection. Figure 3-2 on page 3-3 shows an
example of the reverse direction in the case of a bidirectional STS connection.
The reverse direction must use the same route and STS timeslots on the OC-48
transport optics through each respective ring. In this example, rings A and C
are the end rings and ring B is an intermediate ring.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-6 Matched nodes on GR-1230 Rings

The STS path has its source in ring A at the node designated the service access
point. The STS signal is dropped over matched primary and secondary
gateways to ring B. One signal is dropped directly from an ADM node in
ring A to an ADM node in ring B. This drop connection is called the primary
feed. At the same time, a copy of the signal is broadcast to pass through on a
working timeslot to another node in ring A. This second signal is called the
secondary feed. The first node therefore provides a broadcast point for the
signal. This technique is known as drop-and-continue on working (DCW).

The node in ring A receiving the broadcast signal over the OC-48 line similarly
drops the signal to an ADM node in ring B. The secondary feed continues on
a working timeslot on the transport optics of ring B until it reaches the decision
point. The secondary feed can pass through multiple nodes before reaching the
node at which it is to be dropped to the second ring. Similarly, the secondary
feed can pass through multiple nodes from the node receiving it in the adjacent
ring to the node acting as the decision point.

The decision point is the node at which both the primary or secondary feeds
are available and one or the other is selected for use. This node serves as the
selector node and is considered the primary node.

The primary node monitors both the primary and secondary signals. In normal
operation, the primary feed is selected. In cases in which the primary feed is
served by protected tributaries at the connected nodes, matched-node selector
switches provide an additional level of protection because the standard
tributary protection switching protects the primary feed. The secondary feed is
selected when the primary signal fails, provided the secondary signal itself is
not failed.

Selector switches occur on the basis of a loss of signal, loss of frame, path loss
of pointer, path AIS, or line AIS condition. Selector switches also occur on
signal degrade, signal fail, STS path unequipped, and path defect indicator
(PDI) conditions if:
• the ADM node is equipped with the transmit interface (see Ordering
Information, 323-1201-151 for the supported transmit interface circuit
packs)
• the ADM node is equipped with the NT8E06AD demultiplexer
• the enhanced matched-node capabilities are enabled
Selector switching based on PDI also requires that PDI switching be enabled
for that connection.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-7

Standard tributary protection for OC-3, STS-12, and OC-12 tributaries

includes both equipment and line protection. For these tributaries,
matched-node protection switches are rare, as a matched-node selector switch
to the secondary feed would only occur if there were a double failure involving
both the working and protection tributary or the loss of the node itself.

As described in Chapter 4, “DS3 and STS-1 tributary protection”, STS-1

tributaries have equipment protection only. Line failures on the external side of
the STS-1 interface are not protected. Matched-node gateways therefore
provide protection in the event of line failures, as well as additional protection
for double failures of protected STS-1 interfaces and node failures.

The SONET standard defines the primary feed as always being the feed
received at the selector node by way of a tributary, rather than by way of the
OC-48 optics. The feed received by way of the optics is therefore always
considered the secondary feed. The selector node is therefore also called the
primary node. Its matching node is called the secondary node, which is the
node from which it receives the secondary feed.

In Figure 3-1, the selector (or primary) node then routes the selected signal
over the OC-48 optics of ring B to the next ADM node. This ADM node is then
used as a broadcast point to drop the signal to ring C by way of matched-node
gateways. In this example, the gateways between rings B and C are set up
exactly the same as those between ring A and B. The signal received in ring C
is then routed over the OC-48 optics to its destination (the end node for the STS
path).

In Figure 3-2, the traffic flow is exactly the opposite of the flow in Figure 3-1,
except that the relationship between broadcast points and decision points is
reversed from ring to ring. In SONET, this arrangement is called same-side
routing. In same-side routing, the primary feed in one direction is received by
a selector node that is directly opposite the node receiving the primary feed in
the other direction. Similarly, the nodes handling the secondary gateways in
both directions are aligned.

It is not necessary for the primary and secondary nodes for both directions to
be aligned. In SONET, this non-alignment of primary and secondary nodes is
called opposite-side routing. As shown in Figure 3-3 and Figure 3-4, such an
arrangement can be advantageous to conserve bandwidth, depending on the
destination of the STS path. Typically, a route is defined so that a given STS
signal takes the shortest possible path from source to destination.

In Figure 3-3, the gateways between rings A and B are aligned, just as in
Figure 3-1. However, the gateways between rings B and C are not aligned
because of the different destination for the signal.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-8 Matched nodes on GR-1230 Rings

Figure 3-3
Opposite-side routing
F2569-7

Source
Service access point

Broadcast
Ring A point
(3 ADM nodes)

Secondary feed

Decision
point Primary feed Secondary feed

Primary
Secondary feed Secondary
node
(selector node
node)

Ring B
(6 ADM nodes) Intermediate
(passthrough)
node

Broadcast
point

Primary feed

Secondary feed Primary feed

Decision
point

Secondary feed Primary

Secondary node
node (selector
Ring C node)
(4 ADM nodes)

Destination

End
node
Legend:
= Inter-ring STS path
= Fibers not used by the STS path

Note: For clarity, only one direction of the STS path is shown.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-9

The feed received by way of a tributary by the selector node is always

considered the primary feed, and therefore the selector node is always the
primary node for that direction of traffic flow. In the case of non-aligned
primary and secondary gateways, this means that the broadcast point in ring B
drops the secondary feed to ring C and broadcasts the primary feed to the
adjacent ADM node in ring B. This node then drops the primary feed to ring C,
where it is added at the selector (or primary) node.

The secondary feed is received by the selector node over the OC-48 optics in
ring C. Both signals are monitored and the selected signal is then routed to the
destination.

Figure 3-4 shows the reverse direction, in which the broadcast point in ring C
drops the secondary feed to ring B. The primary feed is broadcast over the
OC-48 optics in ring C to the adjacent ADM node, then dropped to the selector
node in ring B. Meanwhile, the secondary feed is routed from the receiving
node in ring B over the OC-48 optics of ring B to the decision point at the
selector node. The selected signal is then routed over the OC-48 optics of
ring B to the matched-node gateways between rings A and B as described for
Figure 3-2.

Provisioning matched-node gateways

When a matched-node connection is provisioned using the OPC Connection
Manager tool, only one direction is defined. For bidirectional connections, the
opposite direction is then automatically derived from the first direction. For
unidirectional connections, the bandwidth in the opposite direction of the
connection is free to be used as required for other unidirectional connections.

A matched-node connection with the DCW scheme uses the same timeslots on
all primary and secondary segments of the OC-48 fibers within one ring as
follows:
• STS-1 connections use the same timeslot.
• STS-3c connections use the same three STS-1 timeslots.
• STS-12c connections use the same 12 STS-1 timeslots.
Bidirectional connections use the same timeslots in both directions. Those
segments are devoted to the matched-node connection, whether or not they are
currently selected. Both the primary and secondary feeds continuously carry
traffic because of the drop-and-continue scheme. Different timeslots can be
used in the adjacent ring, as long as the same timeslots are used on all affected
OC-48 fibers within a given ring.

If a matched-node connection is defined at the same node at which the signal

is added to or dropped from the ring, the STS path must go around the entire
ring. For example, if a signal from DS3 G1 port 1 IN is mapped to STS-1
channel 1 on the same node at which it is to be dropped to the adjacent ring as

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-10 Matched nodes on GR-1230 Rings

a matched-node connection, the signal must traverse STS-1 channel 1 all

around the ring before it can be dropped to the second ring (for example, using
a tributary such as STS-1 G4 port 1 OUT).

For detailed provisioning guidelines, see Provisioning and Operations

Procedures, 323-1201-310.

Protected operation
Figure 3-5 shows a failure at the primary gateway between rings A and B. In
this example, the secondary feed is selected in ring B at the decision point.
Once the selection of the secondary path is made, the entire secondary path is
used for the duration of the protection switch.

When the failure clears and the signal on the primary path is again ready for
service, the selection reverts to the primary connection after a wait-to-restore
(WTR) period. If both the primary and the secondary feeds have failed, the
primary feed remains selected. If the secondary feed fails while a protection
switch of the path is active, the selection reverts to the primary feed, regardless
of its condition.

Note: On a matched-node system, when a failed facility is restored at the

Service Access Point, a WTR can be detected for the primary feed at the
Primary Gateway Service Selector. When a WTR is raised and then cleared
at the end of the WTR on the primary feed, it will cause an inter-ring switch
traffic hit when reverted back to the primary feed.

This behavior can only occur if the primary gateway node is equipped with
the Demux (NT8E06AD) and the Tx (NT8E01PX).

The inter-ring protection is triggered when the network element detects a

failure condition on the primary feed at the selection point, subject to a
hold-off period of 100 ms. At the end of the hold-off period, the switch
completes within 50 ms. Because an intra-ring protection switch can be
triggered by the same condition that caused the path AIS, the hold-off period
allows time for the intra-ring protection switch to complete. If the intra-ring
protection switch restores the traffic, the path AIS is cleared, thereby avoiding
unnecessary protection switches of the inter-ring path. With the exception of
the 100 ms hold-off period, inter-ring and intra-ring protection switching are
independent.

Note: When you remove an active but unprotected OC-3, STS-12, or

OC-12 interface circuit pack from a network element equipped with
NT8E06AA or AB demultiplexers, the path switch can take several
seconds to complete. This is because the circuit pack is not available to
provide path AIS, and therefore the condition must be detected and
handled by software. It is recommended that you always use protected
OC-3, STS-12, or OC-12 tributaries for matched-node gateway

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-11

connections. In the event of a failure of the working circuit pack (the

left-most shelf position in the quadrant, or the upper position in the OC-3
carrier), the failed circuit pack should be left in the shelf or carrier until it
can be replaced to ensure matched-node protection switching occurs
within specifications. If the network element is equipped with the
NT8E60AD or later demultiplexer, protection switching occurs within
specifications if the tributary circuit pack is unprotected. However, it is
recommended that you always use protected tributary circuit packs.

The relationship between inter-ring and intra-ring protection also serves in the
case of multiple failures. Consider what happens if a second failure occurs
after the failure of the primary gateway as shown in Figure 3-5. The second
failure affects the OC-48 span in ring B that routes the secondary feed to the
decision point. In this case, the normal intra-ring OC-48 transport protection
mechanism protects the secondary feed. This protection is possible because the
secondary feed uses the working path on that span. The traffic is transferred to
that span’s protection path for the duration of the intra-ring protection switch.

When there is no active inter-ring protection switch, intra-ring protection

switching has no effect on inter-ring traffic flow because the inter-ring traffic
continues to use the primary feed. The only difference is that during intra-ring
protection of a failure on the OC-48 span serving the secondary feed adjacent
to the primary node, the secondary feed is monitored on the protection path
rather than the working path.

If an ADM node serving a matched-node connection as a primary drop node

fails completely, the intra-ring protection reroutes the traffic over the
protection timeslots to the secondary drop node defined for that STS path. As
shown in Figure 3-5, the primary drop node is the first node dropping the
matched-node signal for that direction. The first drop node is always the
primary drop node, regardless of whether the primary or secondary feed is the
signal dropped first.

If the primary drop node is the neighbor node of the secondary drop node (that
is, there are no passthrough ADM nodes between them), the secondary drop
node then drops the traffic from the protection timeslots to the adjacent ring.
The traffic is then routed to the decision point and selected, thereby protecting
the matched-node connection.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-12 Matched nodes on GR-1230 Rings

Figure 3-4
Opposite-side routing (reverse direction)
F2569-8

Destination

Decision
point
Ring A
Primary Secondary feed
(3 ADM nodes) Secondary
node
(selector node
node)

Primary Secondary
feed feed

Secondary feed

Broadcast
Ring B point
(6 ADM nodes) Intermediate
(passthrough)
node
Decision
point
Primary Secondary feed
node Secondary
(selector node
node)

Primary Secondary
feed feed

Primary feed
Ring C
(4 ADM nodes) Broadcast
point

Source
End
node

Legend:
= Inter-ring STS path
= Fibers not used by the STS path

Note: For clarity, only one direction of the STS path is shown.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-13

Figure 3-5
Failure on a tributary (primary) connection of matched nodes in inter-connected rings
F2569-1

Source
Service access point

Broadcast
Ring A point
(3 ADM nodes)

Secondary feed
Unprotected
tributary failure Secondary feed

Decision Primary feed Second failure

point results in OC-48
protection switch
Secondary feed
Primary
Secondary
node
node
(selector
node)

Ring B
(6 ADM nodes) Intermediate
(passthrough)
node

Broadcast
point

Secondary feed

Decision Primary feed Secondary feed

point
Secondary feed
Primary Secondary
node node
Ring C (selector
(4 ADM nodes) node)

Destination
End
node
Legend:
= Inter-ring STS path
= Fibers not used by the STS path

Note: For clarity, only one direction of the STS path is shown.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-14 Matched nodes on GR-1230 Rings

Drop-and-continue on protection (DCP)

The DCP scheme offers an alternative to the DCW scheme. The DCP scheme
offers greater survivability than tributary protection alone. At the same time, it
helps preserve bandwidth by using protection timeslots for part of the
matched-node path.

The difference between the DCW and DCP schemes is in how the ring routes
the signals on the OC-48 optics. In DCW, the signal travels over a working
timeslot or timeslots on the OC-48 optics from the service access point to both
the primary and secondary gateways. In DCP, the signal travels over a working
timeslot or timeslots from the service access point to the primary gateway. It
then travels over a protection timeslot or timeslots between the primary and
secondary gateway nodes. Figure 3-6 and Figure 3-7 illustrate the DCW and
DCP routing, respectively.

When you plan a matched-node network, consider the merits of both DCW and
DCP. DCW and DCP both offer improved survivability for a SONET network
by protecting traffic at the STS path level between rings. This path-level
protection is in addition to the line-level protection at the tributaries that
interconnect the rings. Matched-node protection switching is also independent
of the line-switched protection of the OC-48 optics within a given ring.

The DCW scheme achieves improved survivability at the cost of bandwidth.

Both DCW and DCP use bandwidth on the OC-48 optics that could otherwise
be used by other STS connections. In the case of DCW, working timeslots are
used. In the case of DCP, protection timeslots are used that could otherwise be
assigned to extra traffic.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-15

Figure 3-6
Drop-and-continue on working
F3907

Service
access
point
Source
node

Fiber 1

Ring A Fiber 2

Primary Secondary
node node

Tributary Tributary

Primary SS Secondary
node node
Ring B

End
node

Service
Legend: access
point

= Single fiber cable with 24 working

and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-16 Matched nodes on GR-1230 Rings

Figure 3-7
Drop-and-continue on protection
F3907-1

Service
access
point
Source
node

Fiber 1

Ring A Fiber 2

Primary Secondary
node node

Tributary Tributary

Primary SS Secondary
node node
Ring B

End
node

Service
Legend: access
point

= Single fiber cable with 24 working

and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-17

Timeslot usage
Figure 3-8 and Figure 3-9 show examples of timeslot usage for DCW and DCP,
respectively. In both examples, the matched-node connection enters the ring at
node A and is assigned to STS-1 timeslot 1. It is dropped at node B and is
routed to node C over the OC-48 optics. In Figure 3-8, the signal is routed as
a DCW signal and must therefore continue to use STS-1 timeslot 1. In ring B,
it is assigned to use STS-1 timeslot 4.

Figure 3-9 shows the DCP connection routed over a protection timeslot
between the primary and secondary gateway. The example shows STS-1
timeslot 25 (the working timeslot number plus 24). In the DCP case, STS-1
timeslot 1 between nodes B and C is therefore available to be used by another
high-priority STS connection. In ring B, the working portion of the path is
assigned to use STS-1 timeslot 4. The protection portion of the path therefore
must use STS-1 timeslot 28.

Figure 3-10 shows how the use of the protection timeslots between the primary
and secondary nodes in ring A allows the working timeslots to be used by other
connections. In this example, the DCP secondary segments of the connections
use the 24 protection timeslots between the primary and secondary node. Other
connections use the 24 working timeslots between those same nodes.

Survivability with DCW and DCP

Because DCW uses working timeslots, it offers greater survivability than DCP
in the case of multiple-fault conditions. In the case of single-fault conditions
that affect a fiber or OC-48 line, either one, the other, or both of the
matched-node tributaries continues to feed the matched-node signal to the
adjacent ring.

The greater survivability of DCW results from the fact that a protection switch
on the OC-48 transport optics within a ring causes the DCW traffic switch to
protection. The ring then routes the traffic on the protection timeslots in the
opposite direction according to the intra-ring protection switching behavior.
The protection switch routes the signal to both the primary and secondary
node, if possible. If the signal reaches both the primary and secondary nodes,
both the primary and secondary feeds survive. There is no effect on the
adjacent ring. If another fault occurs while the protection switch is active, the
matched-node connection can still be protected.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-18 Matched nodes on GR-1230 Rings

Figure 3-8
STS-1 timeslot usage—DCW
F3907-6

Service
access
point
Source
node

Node A
Fiber 1

Ring A STS-1 1 Fiber 2

Primary Secondary
node node
Node B Node C
STS-1 1
Tributary Tributary

STS-1 4

Primary SS Secondary
node node
Ring B

STS-1 4

End
node

STS-1 4 Service
Legend: access
point

= Single fiber cable with 24 working

and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-19

Figure 3-9
STS-1 timeslot usage—DCP
F3907-7

Service
access
point
Source
node

Node A
Fiber 1

Ring A STS-1 1 Fiber 2

Primary Secondary
node node
Node B Node C
STS-1 25
Tributary Tributary

STS-1 28

Primary SS Secondary
node node
Ring B

STS-1 4

End
node

STS-1 4 Service
Legend: access
point

= Single fiber cable with 24 working

and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-20 Matched nodes on GR-1230 Rings

Figure 3-10
Using protection timeslots to preserve working bandwidth
F3907-5

Service access point

Up to 24 DS3 signals Source
node

Fiber 1

Ring A Fiber 2
Primary Secondary
node node
Service Service
access point access
point
Up to 24 DS3
signals Tributary Tributary

Primary Secondary
node node
SS
Ring B

End
node
Service access point
Legend:
= Single fiber cable with 24 working
and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-21

In the case of a connection with a DCP secondary segment, an OC-48

protection switch within the ring causes any extra traffic on the protection
timeslots, including DCP traffic on the secondary path, to be lost. Because
there is still a signal being dropped at a tributary at the primary drop node, the
loss of the DCP traffic does not cause a loss of service on the matched-node
connection. However, it does mean that the portion of the DCP path carried by
the OC-48 optics can no longer protect the matched-node connection if a
subsequent failure affects the primary feed. In this respect, DCP offers slightly
less survivability than DCW.

In Figure 3-10, an OC-48 protection switch protects the connections using the
24 working timeslots between the primary and secondary nodes.
Consequently, the DCP traffic using the 24 protection timeslots between those
two nodes is preempted. However, the matched-node traffic is still dropped at
the primary node. As long as a second fault does not affect the traffic dropped
at the primary node, the matched-node traffic is maintained.

The benefit of DCP derives from the fact that the portion of the path carried on
the OC-48 protection timeslots can be treated as low-priority traffic. Because
the likelihood of double-fault conditions is relatively rare, DCP conserves
working timeslots that can be used by higher-priority traffic.

Using DCW and DCP in combination

DCW and DCP can be used in combination within a network. Use of both
DCW and DCP means that a total of 48 bidirectional interconnections between
rings can be achieved using two nodes from each ring (see Figure 3-11). With
DCP or DCW alone, only 24 such interconnections are possible because there
are only 24 working or protection timeslots available between the matched
nodes in one ring. Therefore, with DCW alone, only 24 matched-node
connections can be established using the 24 working timeslots. For DCP alone,
only 24 matched-node connections can be established using the 24 protection
timeslots.

Also, because the portions of matched-node paths within each given ring are
independent of the portions of the path in all other rings, DCP and DCW can
be combined on a single matched-node path. An example is shown in
Figure 3-12. Ring A uses the DCW scheme, whereas ring B uses DCP.

A matched-node connection in an intermediate ring can have both a DCW and

DCP secondary segment in the same connection. A matched-node connection
in an intermediate ring has two secondary segments (see Figure 3-13). One
secondary segment exists between the primary and secondary nodes on the add
side of the ring (the primary add node and the secondary add node). The other
secondary segment exists between the primary drop node and the secondary
drop node on the drop side of the ring. These secondary segments can be both
DCW, both DCP, or either DCW or DCP in any combination.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-22 Matched nodes on GR-1230 Rings

Figure 3-11
Configuring 48 matched-node connections at a pair of primary and secondary nodes
F3907-2

Service
access Up to 48 DS3
point signals

Fiber 1

Ring A Fiber 2

Up to 48 STS-1 tributaries

Up to 48 STS-1 tributaries

SS
SS
Ring B

Service
access
point

Service
Legend: access
point

= Single fiber cable with 24 working

and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-23

Figure 3-12
Using a combination of DCW and DCP for the same matched-node path
F3907-8

Service
access
point
Source
node

Fiber 1

Ring A Fiber 2

Primary Secondary
node node

Tributary Tributary

Primary SS Secondary
node node
Ring B

End
node

Service
Legend: access
point

= Single fiber cable with 24 working

and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-24 Matched nodes on GR-1230 Rings

Figure 3-13
Using both DCW and DCP in the same connection (intermediate ring)
F3907-13

Service
access
point
Source
node

Fiber 1

Ring A Fiber 2

Primary Secondary
drop node drop node

Primary SS Secondary
add node add node
Ring B

Primary Secondary
drop node drop node

Primary SS Secondary
add node add node
Ring C

End
node

Legend: Service
access
point
= Single fiber cable with 24 working
and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-25

STS connections
Connections with DCP secondary segments can be bidirectional or
unidirectional at the STS-1, STS-3c or STS-12c rates. The connections follow
the same rules for timeslot assignment as other connections. These rules are
specified in Chapters 5 and 6 of Provisioning and Operations Procedures,
323-1201-310.

In general, DCP provisioning also follows the same rules that apply to other
extra traffic connections. In addition, the DCP secondary segment of the
connection must use the protection timeslot that corresponds to the working
timeslot used between the service access point and the primary gateway. The
protection timeslot is the working timeslot plus 24 on the opposite circuit pack
group. For example, if the working timeslot is STS-1 timeslot 1 on G1, the
associated protection timeslot is STS-1 timeslot 25 on G2.

For a DCW connection, both the primary and secondary feeds survive an
intra-ring OC-48 protection switch, unless the primary drop node is isolated.
For a DCP connection, only the primary feed survives.

Link failures
For single failures of OC-48 links, the matched-node traffic is maintained in
both the DCW and DCP schemes by the intra-ring OC-48 protection
switching.

When two or more failures occur at the same time, traffic may or may not be
maintained. The DCW scheme offers more survivability than DCP. In the
example shown in Figure 3-14, a failure of the OC-48 optics in the drop ring
and the loss of the tributary serving the primary feed is protected in the DCW
case. Although the secondary feed is no longer available on the optics between
the primary and secondary drop nodes, an OC-48 protection switch protects
the signal on the transport optics at the primary drop node. The protection
switch routes the traffic in the opposite direction around the ring to be dropped
at the secondary drop node from the protection timeslots. The tributary serving
the secondary feed at the secondary drop node therefore continues to serve the
matched-node connection.

In the DCP case with similar failures (shown in Figure 3-15), the
matched-node traffic is lost. The reason is that the secondary feed uses
protection timeslots between the primary drop node and the secondary drop
node. The OC-48 protection switch preempts the protection timeslots serving
the secondary feed with the traffic from the equivalent working timeslots. The
matched-node traffic therefore does not reach the secondary drop node.
Because the primary feed has also failed, neither the primary nor the secondary
feed is available in the add ring.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-26 Matched nodes on GR-1230 Rings

Figure 3-14
Link failures (DCW)
F3907-4

Service
access
point
Source
node

Fiber 1

Ring A Fiber 2

Primary Secondary
drop node Fiber drop node
cable cut

Tributary failure Tributary

Primary SS Secondary
add node add node
Ring B

End
node

Service
Legend: access
point

= Single fiber cable with 24 working

and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-27

Figure 3-15
Link failures (DCP)
F3907-3

Service
access
point
Source
node

Fiber 1

Ring A Fiber 2

Primary Secondary
drop node Fiber drop node
cable cut

AIS
Tributary failure Tributary

Primary SS Secondary
add node add node
Ring B

End
node

Service
Legend: access point
(receives AIS)

= Single fiber cable with 24 working

and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)
AIS = Alarm indication signal

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-28 Matched nodes on GR-1230 Rings

Node failures and node isolation

If one of the four nodes serving a matched-node connection fails or becomes
isolated, there is no add or drop traffic at that node. This means the primary or
secondary feed served by a tributary at that node is lost. Such a failure is
protected by the intra-ring OC-48 protection.
Primary drop node
Failure or isolation of the primary drop node results in the traffic being routed
to the secondary drop node over the protection channel. In the DCW scheme,
the traffic flow depends on whether there is an intermediate node between the
secondary drop node and the failed primary drop node.

If there is an intermediate node in the DCW scheme, the traffic continues on

protection past the secondary drop node to the intermediate node (see
Figure 3-16). The intermediate node detects that the primary drop node has
failed or is isolated. It therefore switches the traffic to the working timeslot
according to the standard intra-ring protection switching behavior. It routes the
traffic back on the working timeslot to the secondary drop node. The secondary
drop node drops the traffic from the working timeslot.

If the secondary drop node and the primary drop node in the DCW scheme are
neighbor nodes, the secondary drop node detects that the primary drop node
has failed or is isolated. It therefore drops the traffic directly from the
protection timeslot (see Figure 3-17).

In the DCP scheme, the traffic is dropped directly from the protection timeslots
regardless of whether there is an intermediate node (see Figure 3-17).
Primary add node
If the primary add node fails or becomes isolated, DCW traffic from the
secondary add node is protected by an intra-ring protection switch in the add
ring. The secondary feed is then routed to the destination.

For the DCP scheme, the traffic is placed directly on the protection channel at
the secondary add node in the direction going away from the primary add node.
Secondary drop or add nodes
For both the DCW and DCP schemes, if either the secondary drop or add node
fails or becomes isolated, the traffic is not affected. The matched-node traffic
continues to be selected from the primary feed at the selector node. However,
there is no protection for the matched-node traffic if the primary feed also fails.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-29

Figure 3-16
Node failure (DCW with intermediate node between primary and secondary drop nodes)
F3907-12

Service access point

Source node

Fiber 1

Ring A Fiber 2

Primary Node Secondary

drop node failure drop node

Tributary Tributary

Primary SS Secondary
add node add node

Ring B

End
node

Service access point

Legend:

= Single fiber cable with 24 working

and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-30 Matched nodes on GR-1230 Rings

Figure 3-17
Node failure (DCW without intermediate node and DCP)
F3907-9

Service access point

Source node

Fiber 1

Ring A Fiber 2

Primary Node Secondary

drop node failure drop node

Tributary Tributary

Primary SS Secondary
add node add node

Ring B

End
node

Service access point

Legend:
= Single fiber cable with 24 working
and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Matched nodes on GR-1230 Rings 3-31

Opposite-side routing
In many cases, the primary drop node for one ring is connected to the primary
add node of the adjacent ring. The secondary drop node is therefore connected
to the secondary add node. Such an arrangement is called same-side routing.

It is also possible to connect the primary drop node to the secondary add node
and to connect the secondary drop node to the primary add node. This
arrangement is called opposite-side routing.

Opposite-side routing is fully supported for the DCW scheme. However, for
the DCP scheme, opposite-side routing must only be used if only one of the
two interconnected rings has a DCP secondary segment. The other ring must
have a DCW secondary segment (as shown in Figure 3-18).

If opposite-side routing is used when both rings have a DCP secondary

segment, the matched-node traffic is lost if both rings experience an OC-48
protection switch at the same time. The reason is that the protection timeslots
are preempted by the protection switches. It is therefore strongly
recommended that you do not use opposite-side routing in configurations
using the DCP scheme.

The secondary drop node normally receives traffic from the DCP secondary
segment over the protection timeslots. A protection switch in ring A preempts
this traffic so that it is no longer dropped at the secondary drop node.

Similarly, a protection switch in ring B means that the traffic received over the
protection timeslots at the primary add node (selector) is preempted. If both
rings have a DCP secondary segment, the primary add node does not receive
traffic from either the primary or the secondary feed. The result is a traffic
outage.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
3-32 Matched nodes on GR-1230 Rings

Figure 3-18
Opposite-side routing
F3907-10

Service
access
point
Source
node

Fiber 1

Ring A Fiber 2

Primary Secondary
drop node drop node

DCW secondary segment

Tributary Tributary

Secondary Primary
add node SS add node
Ring B
DCP secondary segment

End
node

Service
Legend: access
point

= Single fiber cable with 24 working

and 24 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 24)
= Direction of traffic flow on protection STS-1 timeslots (25 through 48)

SS = Service selector

Note: For clarity, only one direction of traffic flow is shown.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 4-1

DS3 and STS-1 tributary protection 4-

This chapter describes the automatic protection-switching features for the DS3
mappers and STS-1 interfaces on the OC-48 system.

Protection switching at the DS3 and STS-1 tributary rates (Figure 4-1) is
offered on a shelf-by-shelf basis and is controlled by the shelf processor. One
standby DS3 mapper circuit pack provides bidirectional protection for up to 16
working DS3 mapper circuit packs (three DS3 facilities for each circuit pack).
Similarly, one standby STS-1 interface circuit pack provides bidirectional
protection for up to 16 working STS-1 interface circuit packs (three STS-1
facilities for each circuit pack). With bidirectional protection, protection
switching is performed for both the transmit and receive directions at the same
time.

DS3 and STS-1 tributary protection is available only if the working DS3
mapper or STS-1 interface circuit pack is in the in-service state and if at least
one of the DS3 or STS-1 facilities served by the circuit pack is in the in-service
state. All DS3 and STS-1 protection switches are performed independently of
any OC-48 transport protection switch, and of any other tributary protection
switching or switching activity at other shelves.

Only one DS3 or STS-1 protection switch can be active at a time, with the
switch granted according to the relative priority of the switch requests and the
circuit packs affected. If the OC-48 terminal shelf is equipped with both DS3
and STS-1 tributaries, the protection STS-1 interface and the protection DS3
mapper share the switcher circuit pack and the switch controller circuit pack.

The user can set either a high or a low level of priority to each DS3 mapper and
STS-1 interface. Higher priority signals preempt lower priority signals. If
protection switching receives two equal-priority switch requests, it honors the
first one received. If it receives two equal-priority switch requests at the same
time, it chooses the request from the circuit pack with the lower slot number.
Place facilities with similar priorities on the same circuit pack.

Protection-switching statistics are recorded by the performance-monitoring

feature.

For a diagram of DS3 and STS-1 1:N protection, see Figure 4-1.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
4-2 DS3 and STS-1 tributary protection

Note 1: DS3 and STS-1 tributary protection is not available while the
system is downloading software to the shelf processor or during a shelf
restart.
Note 2: For 1:N OC-48 systems, tributary protection is not available for
STS-1 extra traffic. A “Circuit pack mismatch” alarm becomes active
whenever an STS-1 interface is inserted in slot 16 of the protection shelf.
Note 3: The shelf exerciser detects protection-path failures for the
protection-switching mechanism in DS3 and STS-1 tributaries. For more
information, see Chapter 11, “Protection exerciser”.
Figure 4-1
DS3 and STS-1 tributary protection switching—normal operation
F0073_R12

24
DS3 DS3 mapper
Interface
or or STS-1
STS-1 port
interface
1 to 24 1 to 24
1 to 8

24 24

OC-48
Switcher transmit
1 interface

3 Protection
Switch 3 DS3 mapper 3
controller or STS-1
interface 3
3

Switcher OC-48 OC-48

2 demultiplexer receive
interface

24 24

DS3 DS3 mapper

or Interface or STS-1
STS-1 port interface
25 to 48 25 to 48 9 to 16
24

Legend:
Carrying traffic
Not carrying traffic

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 DS3 and STS-1 tributary protection 4-3

Switch initiation
Automatic protection switching is initiated on detection of a failure of a DS3
mapper (NT7E08) circuit pack or an STS-1 interface (NT7E09) circuit pack.
In addition, the user can initiate forced and manual switches or a lockout. For
a diagram showing failure conditions, see Figure 4-2.

All failures are analyzed to determine their nature. Whereas a DS3 mapper or
STS-1 interface failure initiates a protection switch, a previous section failure
cannot be protected, such as a loss of signal on the external DS3 or STS-1 line.
The interface port and interface carrier circuit packs are part of the previous
section, and therefore failures of these circuit packs are not protected.

A failure of the standby DS3 mapper or STS-1 interface circuit pack causes
DS3 or STS-1 protection, respectively, to be unavailable.

Switch times
For a single failed circuit pack, the total switching time is 60 ms or less from
the start of the fault to the completion of the switch. This complies with
Telcordia (formerly known as Bellcore) TA-TSY-000253 specification of
10 ms or less to detect the fault, and 50 ms or less from detection to switch
completion.

Note: When an OC-48 terminal shelf is equipped with both STS-1 and
DS3 tributaries, some failures are not protected within 60 ms. Only one
failure, whether DS3 or STS-1, can be protected at one time.

Path switching
In matched-node applications of GR-1230 Rings, the inter-ring protection
occurs at the STS path level. This requires path-switching from a primary STS
connection to a secondary STS connection.

For matched-node connections, protection switching within a ring both at the

transport and tributary levels has a higher priority than protection switching of
the STS path between rings. Consequently, when path alarm insertion signal
(AIS) is detected on a matched-node connection that uses an STS-1 tributary,
the protection switch to the secondary path is subject to a hold-off period of
100 ms to allow time for a protection switch to complete at the tributary or
transport levels. The protection switch of the path then occurs within 50 ms
following the hold-off period.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
4-4 DS3 and STS-1 tributary protection

Figure 4-2
DS3 and STS-1 tributary protection switching—failure conditions
F0074_R12

One of the
DS3 mappers
or STS-1
interfaces
has failed

24
DS3 DS3 mapper
Interface
or or STS-1
STS-1 port
interface
1 to 24 1 to 24
1 to 8

24 24

OC-48
Switcher transmit
1 interface

3 Protection
Switch 3 DS3 mapper 3
controller or STS-1
interface 3
3

Switcher OC-48 OC-48

2 demultiplexer receive
interface

24 24

DS3 DS3 mapper

or Interface
or STS-1
STS-1 port
interface
25 to 48 25 to 48
9 to 16
24

Legend:
Carrying traffic
Not carrying traffic

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 DS3 and STS-1 tributary protection 4-5

DS3 and STS-1 tributary protection signal flow

The following subsections describe the signal flow within the shelf when a
protection switch is active on a DS3 or STS-1 tributary.

In the DS3 or STS-1 receive direction

Circuit pack failure
When a single DS3 mapper or STS-1 interface fails, the network element’s
software instructs the appropriate switcher and the switch controller to select
the three affected DS3 or STS-1 signals. The three signals are then routed to
the protection DS3 mapper or STS-1 interface, as appropriate.

The STS-1 interface sends the three signals to the OC-48 or STS-48 transmit
interface. In the case of DS3 signals, the protection DS3 mapper maps the three
signals into three STS-1 signals, then sends the three STS-1 signals to the
transmit interface. These three signals from the protection circuit pack replace
the STS-1 signals from the failed working circuit pack.
Faulty signal
When a working DS3 mapper or STS-1 interface receives a faulty signal, all
three signals on that circuit pack are bridged (routed without interrupting the
original signal) to the protection DS3 mapper or STS-1 interface, where they
are analyzed. If the protection circuit pack detects the same problems reported
by the working circuit pack, the bridging is dropped and the received signal is
declared faulty. If the protection circuit pack detects a normal signal, the
working DS3 mapper or STS-1 interface is declared failed and the protection
switch is completed.

In the DS3 or STS-1 transmit direction

When a single DS3 mapper or STS-1 interface fails, the shelf processor
instructs the OC-48 demultiplexer to bridge the three STS-1 signals, originally
routed to the failed DS3 mapper or STS-1 interface, to the protection DS3
mapper or STS-1 interface. In the case of DS3 tributaries, the protection DS3
mapper then extracts the DS3s from the STS-1 signals. For both DS3 and
STS-1 tributaries, the signals are then routed to the switch controller.

The shelf processor instructs the switch controller and the appropriate switcher
to route the DS3 or STS-1 signals to the appropriate interface ports. Finally,
the relays on the interface ports are switched on to select the DS3 or STS-1
signals incoming from the switcher, and to ignore the signals coming from the
failed DS3 mapper or STS-1 interface.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
4-6 DS3 and STS-1 tributary protection

DS3 and STS-1 protection exerciser

The protection exerciser is a software tool that ensures that the protection paths
used for protection on a given shelf are not faulty. For DS3 and STS-1
tributaries, this includes the switcher, switch controller, and protection DS3
mapper or STS-1 interface. The protection exerciser is run automatically at
scheduled intervals and can also be invoked manually.

When the DS3 and STS-1 portions of the protection exerciser routine are
executed, the DS3 or STS-1 signal is bridged to the protection DS3 mapper or
STS-1 interface, where it is analyzed. If the protection circuit pack detects a
faulty DS3 signal, and if the working circuit pack does not report a faulty
signal, the software then concludes that there is a failure in the path used for
DS3 or STS-1 protection and raises the DS3 or STS-1 “Protection path fail”
alarm, as appropriate.

Similarly, every STS-1 signal dropped by the demultiplexer to DS3 or STS-1

tributaries is bridged to the protection DS3 mapper or STS-1 interface. The
bridged STS-1 signals are then analyzed and the results compared with an
analysis of the working DS3 mapper or STS-1 interface circuit packs. If there
is a discrepancy, the software concludes that there is a failure in the path used
for DS3 or STS-1 protection and raises the DS3 or STS-1 “Protection path fail”
alarm, as appropriate. For a detailed description of the exerciser, see Chapter
11, “Protection exerciser”.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 5-1

OC-3, STM-1J, STS-12, and OC-12

tributary protection 5-
This chapter describes the automatic protection-switching features for the
OC-3, STM-1J, STS-12, and OC-12 tributaries on OC-48 shelf applications.

Note: STS-12 tributaries are treated as if they are OC-12 tributaries. The
user interface reports protection switches, alarms, user interface screens,
and protection-switching statistics for STS-12 tributaries as OC-12
protection switches, alarms, user interface screens, and
protection-switching statistics.

Definitions
Line switching
As defined in the SONET standard, a line is the segment of a fiber transmission
system between network elements where traffic originates and terminates (for
example, between two terminal sites). For a diagram, see Figure 5-1. A line has
a head end, where traffic originates, and a tail end where traffic terminates.
Both the head end and the tail end are defined with respect to the direction of
transmission; if the direction is reversed, then so are the head and tail ends of
the line.

Path switching over matched-nodes

In matched-node applications of GR-1230 Rings, inter-ring protection occurs
at the STS path level. Path switching is from a primary STS connection to a
secondary STS connection.

For matched-node gateway connections, protection switching within a ring of

both transport and tributary traffic has a higher priority than protection
switching of the STS path between rings.

When a path alarm indication signal (AIS) is raised on an OC-3, STS-12, or

OC-12 tributary across a matched-node connection, the protection switch to
the secondary path is delayed for a hold-off period of 100 ms. This allows time
for a protection switch to complete at the tributary or transport levels. The
protection switch of the path occurs within 50 ms following the hold-off
period.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
5-2 OC-3, STM-1J, STS-12, and OC-12 tributary protection

Note: STM-1J interfaces do not support matched-node configurations.

For protection switching to occur within these specifications, the affected

quadrants must be equipped with protection circuit packs. Even if the working
circuit pack is failed, the switching times will meet these specifications.
Figure 5-1
Typical lines in an OC-48 linear system with an OC-3 or OC-12 tributary
F0036-OC3

Line 1

Head Tail

OC-48 OC-48
network Regenerator network
element element

Head

Line 2
DS3, STS-1
OC-3, STS-12,
OC-12
OC-3/

Tail
OC-12
network
element

DS1, DS3,
STS-1, OC-3

Note: This drawing shows only one direction of transmission.

If the direction of transmission is reversed, the head end of the
line becomes the tail end.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-3, STM-1J, STS-12, and OC-12 tributary protection 5-3

1+1 protection on OC-3, STM-1J, STS-12, and OC-12 tributaries

For 1+1 protection on OC-3, STM-1J, STS-12, and OC-12 tributaries, the
OC-48 shelf can be equipped with a working and a protection OC-3, STM-1J,
STS-12, or OC-12 circuit pack. If there is a signal failure because of
degradation on the working channel or a failure of a circuit pack, the traffic
switches over to the protection channel.

1+1 protection is non-revertive. The traffic remains on the latter channel even
after the failure is cleared. For an illustration of 1+1 protection, see Figure 5-2.
The 1+1 protection scheme has a permanent physical bridge at the head end of
the line.

Normally the working channels occupy the odd-numbered circuit pack groups
and the protection channels occupy the even-numbered circuit pack groups.
The protection-switching exerciser only exercises the odd-numbered circuit
packs. To keep the odd-numbered circuit pack group as the active interface
after a protection switch, manually switch the traffic back from the
even-numbered circuit pack to the odd-numbered circuit pack.

Note 1: Protection switches on OC-3, STM-1J, STS-12, or OC-12

tributaries operate independently of both OC-48 transport protection
switches and of any other tributary protection switches at any network
elements in the system.
Note 2: Lockouts on OC-3, STS-12 and OC-12 tributaries can only be
applied to the odd-numbered channels. If the traffic is on the
odd-numbered channel, the lockout keeps the traffic on that channel. If the
traffic is on the even-numbered channel, the lockout moves it to the
odd-numbered channel.
Note 3: The lockout command on an STM-1J tributary causes the traffic
to remain on the STM-1J tributary which was carrying the traffic before the
lockout was performed.
Note 4: Protection switching is not available if the protection circuit pack
is not installed or is out of service. All automatic and user-initiated
protection-switching requests are denied. Whenever a circuit pack is
placed from the in-service state to the out-of-service state, all protection
switches are cleared on both circuit packs.
Note 5: If an “Invalid K-bytes” alarm occurs on a channel with an active
protection switch, the protection switch is dropped.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
5-4 OC-3, STM-1J, STS-12, and OC-12 tributary protection

Figure 5-2
Line protection-switching architecture—1+1 application
F0037

Head Tail
Active

Standby

Half-height OC-3 or STM-1J interfaces

Equipped with half-height OC-3 or STM-1J interfaces (NT8E08), an OC-48
terminal shelf can support up to 16 OC-3 or STM-1J tributaries (up to four
tributaries in a quadrant). The OC-3 and STM-1J tributaries in each quadrant
can be a mix of 1+1 protected and unprotected tributaries.

Each 1+1 protected tributary requires an OC-3 carrier in one slot in the
network element shelf, and a half-height OC-3 or STM-1J interface in both the
top and bottom positions of the OC-3 carrier. The upper circuit pack serves the
working channel and the lower circuit pack serves the protection channel.

Each unprotected tributary requires an OC-3 carrier in one slot in the network
element shelf with a half-height OC-3 or STM-1J interface in the top position.

CAUTION
Risk of service interruption
Operating an unprotected half-height OC-3 or STM-1J
interface (NT8E08) in the bottom position of an OC-3 carrier
can cause a service interruption.

Half-height OC-3 and STM-1J interfaces are identified as circuit pack groups
G9 to G40 according to their quadrants and shelf positions. The odd-numbered
circuit pack groups occupy the upper position of each OC-3 carrier. The
even-numbered circuit pack groups occupy the lower position.

Note: If an OC-3 carrier fails, the LEDs on the half-height OC-3 or

STM-1J interfaces light, and the OC-3 or STM-1J tributary can lose
switching capability. However, depending on the type of failure, a faulty
carrier may still carry traffic. If the OC-3 or STM-1J tributary is still
carrying traffic, the faulty carrier can be replaced without service
interruption if it contains a protected tributary. For in-service carrier
replacement instructions, see Module Replacement Procedures,
323-1201-547.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-3, STM-1J, STS-12, and OC-12 tributary protection 5-5

Double-width OC-3 interfaces

Equipped with double-width OC-3 interfaces (NT7E01), an OC-48 terminal
shelf can support up to four 1+1 protected OC-3 tributaries (one tributary in a
quadrant). Alternatively, the terminal shelf can support up to eight unprotected
OC-3 tributaries (up to two tributaries per quadrant).

Each 1+1 protected tributary requires two double-width OC-3 interfaces. Each
of these circuit packs occupy two slots in the network element shelf. The
tributary is automatically configured for 1+1 protection when the circuit packs
are installed.

Each unprotected tributary requires an unprotected double-width OC-3

interface (NT7E01Ex/Fx/Gx series only). Normally, the circuit pack occupies
the even-numbered circuit pack group. The circuit pack can be manually
provisioned to operate in the odd-numbered circuit pack group. A
double-width filler card inserted in the unused circuit pack group aids in
cooling and EMI shielding. Two unprotected OC-3 tributaries can be manually
provisioned in a quadrant. For manual provisioning procedures, see
Commissioning Procedures, 323-1201-220.

The interfaces are identified as circuit pack groups G1 to G8 according to their

quadrants and shelf positions. These circuit pack groups each span two slots.

Note 1: You can mix DS3 mappers, STS-1 interfaces, and half-height
OC-3 interfaces (NT8E08) in the same quadrant. You cannot mix
double-width OC-3 interfaces (NT7E01) with any other tributary types in
the same quadrant.
Note 2: You cannot mix double-width and half-height OC-3 interfaces
with each other in a quadrant.

CAUTION
Risk of service interruption
Operating an unprotected double-width OC-3 interface
(NT7E01Cx/Dx series only) in the G2, G4, G6, or G8 circuit
pack group can cause a service interruption.

STS-12 or OC-12 interfaces

An OC-48 terminal shelf can support up to four STS-12 or OC-12 tributaries,
one tributary in a quadrant.

Each 1+1 protected tributary requires two STS-12 interfaces or two OC-12
interfaces. Each of these circuit packs occupy two slots in the network element
shelf. The tributary is automatically configured for 1+1 protection when the
circuit packs are installed.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
5-6 OC-3, STM-1J, STS-12, and OC-12 tributary protection

Each unprotected tributary requires one STS-12 interface or one OC-12

interface. The circuit pack must occupy the odd-numbered circuit pack group.
Unprotected operation of a second STS-12 or OC-12 interface in a quadrant is
not supported.

The interfaces are identified as circuit pack groups G1 to G8 according to their

quadrants and shelf positions. These circuit pack groups each span two slots.

Note: You cannot mix STS-12 interfaces or OC-12 interfaces with any
other tributary types in the same quadrant.

CAUTION
Risk of service interruption
Operating an unprotected STS-12 or OC-12 interface in the
G2, G4, G6, or G8 circuit pack group can cause a service
interruption.

Switching modes
The protection-switching mode for OC-3, STS-12, and OC-12 tributaries can
be changed between bidirectional non-revertive and unidirectional
non-revertive. The bidirectional mode transfers both directions of transmission
onto the protection channel during a protection switch. Unidirectional mode
only transfers the affected channel. The default switching mode is
bidirectional non-revertive. For a diagram of bidirectional and unidirectional
switching modes, see Figure 5-3.

Note: The switch mode for the STM-1J interface is bidirectional

non-revertive only.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-3, STM-1J, STS-12, and OC-12 tributary protection 5-7

Figure 5-3
Bidirectional and unidirectional switching mode—normal and failure conditions
F0039

Working Working
Normal
condition Protection Protection

Failed channel
Working Working
Failure
condition Protection Protection

(a) Unidirectional (b) Bidirectional

Legend:
Carrying traffic
Not carrying traffic
Failed

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
5-8 OC-3, STM-1J, STS-12, and OC-12 tributary protection

Availability of protection switching

OC-3, STM-1J, STS-12, and OC-12 protection switching is available if both
working and protection circuit packs are in service.

OC-3 and STM-1J tributaries are automatically provisioned for 1+1 protection
when the circuit packs are installed in a quadrant. Half-height OC-3 and
STM-1J interfaces automatically operate as unprotected if the lower position
in the OC-3 carrier is empty.

Double-width OC-3 interfaces can be manually provisioned as unprotected.

STS-12 and OC-12 tributaries are automatically provisioned for 1+1
protection when the protection circuit pack is installed.

A protection switch on an OC-3, STM-1J, STS-12, or OC-12 tributary is

performed independently of an OC-48 transport protection switch, of any
protection switch of another tributary at that network element, and of any
protection-switching activity at other OC-48 network elements in the system.

Protection switching is also provided during software downloads and shelf

processor restarts. It is not available during the initial system power-up.

Switch initiation
System-initiated protection switches
Automatic protection switching is initiated due to a signal failure or a signal
degrade.
Signal failure
The following conditions can cause a signal failure:
• loss of signal (LOS)
• loss of optical frame (LOF)
• line alarm indication signal (AIS)
• OC-3, STM-1J, STS-12, or OC-12 interface circuit pack failure when
provisioned for 1+1 protection
Signal degrade
A signal degrade triggers automatic protection when the optical bit-error-rate
(BER) exceeds a user-selectable threshold ranging from 10-4 to 10-10. The
default is 10-6. If the protection channel becomes degraded after an automatic
switch because of a signal degradation on the working channel, the switch
remains active. However, if the degradation of the protection channel occurs
before a degradation of the working channel is detected, no automatic switch
is performed.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OC-3, STM-1J, STS-12, and OC-12 tributary protection 5-9

Note: On an STM-1J interface, a signal degrade induced-automatic switch

is not indicated by an “R” at the far end network element. This is a result
of a permanent limitation due to Japan standards. When a node encounters
a signal degrade on protection, a K-byte signal degrade indication is not
sent to the far end network element due to Japan standards.

User-initiated protection switches

The user can manually operate lockouts, forced switches, and manual switches
from the user interface. STM-1J interfaces do not support manual switches.
For descriptions, see Chapter 9, “User-initiated protection-switching
features”. For related procedures, see Protection Switching Procedures,
323-1201-311.

Switch times
The system detects degradation or failures in an OC-3, STM-1J, STS-12, or
OC-12 signal within 10 ms. It then completes automatic protection switching
within 50 ms. To prevent unnecessary switching activity, these switch times
include a frame-loss detection hold-off period of 3 ms.

For signal-degrade conditions, the detection time varies with the

user-selectable BER thresholds specified in Table 5-1.

The signal-degrade condition clears when the bit error rate improves by a
factor of 10, for example from 10-8 to 10-9.
Table 5-1
Signal degradation thresholds for protection switching
BER threshold Detection time TR-TSY-000253
requirements

10-4 35 ms 100 ms

10-5 370 ms 1s

10-6 3s 10 s

10-7 30 s 100 s

10-8 300 s 16.7 min

10-9 55 min 2.8 h

10-10 8.9 h —

Note: The detection times in this table assume uniformly distributed errors.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
5-10 OC-3, STM-1J, STS-12, and OC-12 tributary protection

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 6-1

OPTera Packet Edge System

protection 6-
This section describes protection available for OPTera Packet Edge System
(formerly iPT1000) traffic on OC-48 network elements. There is no equipment
protection available with the 2x1000SX circuit pack.

Note: The OC-48 GR-1230 Ring supports the 2x1000SX circuit pack on
a two-fiber bidirectional line-switched ring (BLSR). The 2x1000SX circuit
packs are not supported on linear systems, and Packet Edge interfaces
cannot be used for matched-node connections.

Protection switching
You can provision either protected or unprotected Packet Edge point-to-point
connections, or shared ring Packet Edge connections. Protected Packet Edge
connections use layer 1 protection. Shared ring connections use layer 2
protection. Traffic is not protected by either layer 1 or layer 2 protection for
unprotected point-to-point connections.

Layer 1 protection
Layer 1 protection is provided through the redundant routes of the
bidirectional line-switched ring SONET protection. Refer to Chapter 2,
“OC-48 transport protection” for a complete description. Layer 1 automatic
protection mode coexists with Packet Edge layer 2 protection to protect both
the circuit switching traffic and the connectionless packet traffic.

Layer 2 protection
Layer 2 protection is data link layer protection (path-level protection), and is
only available for shared ring connections. The 2x1000SX circuit pack
provides layer 2 protection within the SONET network. When there is a failure
on any span in a Packet Edge shared ring connection, Packet Edge traffic is not
lost. The layer 2 protection switch feature reroutes the traffic in the direction
away from the fiber cut. In such a case, traffic that was transported on both
sides of the ring is now transported through just one side of the ring. Certain
conditions can cause a layer 2 protection switch. You can manually initiate a

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
6-2 OPTera Packet Edge System protection

layer 2 protection switch by placing one of the Packet Edge wide area network
ports out of service. For instructions on how to perform a manual layer 2
protection switch, see the Packet Edge System OC-48 Data Guide.

The following conditions and failures cause an automatic layer 2 protection

switch:
• fiber cut
• signal degrade
• receive alarm indication signal (Rx AIS)
• 2x1000SX circuit pack removal or insertion
• 2x1000SX circuit pack or node failure
• WAN port disabled
• circuit pack attachment to a ring or detachment from a shared ring
• deletion of cross-connects on a passthrough node
After the condition or failure clears and a wait-to-restore period expires, the
system reroutes traffic to the original path. The wait-to-restore period is
5 seconds for all cases except for a signal degrade, in which case it is
60 seconds.

Figure 6-1 shows an unbroken ring carrying both SONET and data traffic. The
data connection in this example is unprotected (no layer 1 protection). When a
failure occurs on a span that is adjacent to a node where a 2x1000SX circuit
pack terminates, the physical layer 1 ring does not protect unprotected
connections. Layer 2 protection redirects the data traffic to the terminating
Packet Edge network element as shown in Figure 6-2, where a layer 1 and layer
2 traffic pattern exists.

Point-to-point connections
The Packet Edge point-to-point connection supports Ethernet connectivity
between two Packet Edge nodes on a SONET transport ring. With
point-to-point configurations, data from one 2x1000SX circuit pack is
delivered to only one other 2x1000SX circuit pack. Figure 6-3 shows a Packet
Edge point-to-point connection.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OPTera Packet Edge System protection 6-3

Figure 6-1
Traffic on an unbroken span of a Packet Edge connection
IW0132

2x1000SX

2x1000SX

Legend

- SONET traffic
- Data traffic connection
- Data traffic path

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
6-4 OPTera Packet Edge System protection

Figure 6-2
Traffic using layer 2 protection for a Packet Edge connection
IW0133

2x1000SX

2x1000SX

Legend

- SONET traffic
- Data traffic connection
- Data traffic path

Protected connections
Packet Edge protected point-to-point connections use layer 1 (SONET)
protection. The 2x1000SX circuit pack supports one protected connection for
each circuit pack. A protected point-to-point connection can be provisioned at
a rate of STS-12c on one facility.

When the SONET connection is cut on a protected point-to-point connection,

the GR-1230 Ring maintains the data connection.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OPTera Packet Edge System protection 6-5

Figure 6-3
Packet Edge point-to-point connection
F6406t.eps

NE 2

NE 1 NE 3
Ethernet
2x1000SX 2x1000SX
equipment

Legend:

= SONET optical connections

Unprotected connections
Each point-to-point application without layer 1 (SONET) protection can have
one or two point-to-point unprotected connections. Unprotected point-to-point
applications can be provisioned at rates of STS-1, STS-3c, or STS-12c on each
facility.

When the SONET connection is cut on a point-to-point unprotected

connection, the frames are lost.

Shared ring
The OC-48 GR-1230 Ring supports shared bandwidth connections for Packet
Edge nodes around the ring, with a rate of STS-1, STS-3c, and STS-12c. One
shared ring connection is provisioned per 2x1000SX circuit pack. For
example, up to 4 STS-12c shared ring connections can be set up per OC-48
ADM node. In this case, because the traffic is flowing on both sides of the ring,
double the bandwidth is available per OC-48 shelf. Figure 6-4 shows an
example of a Packet Edge shared ring connection and Figure 6-5 shows the
detailed Packet Edge shared ring connection.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
6-6 OPTera Packet Edge System protection

Figure 6-4
Packet Edge shared ring connection
F6405p.eps

NE 1 NE 2

NE 6 NE 3
Ethernet
equipment 2x1000SX 2x1000SX

NE 6 NE 4
2x1000SX

Legend:

= SONET optical connections

A shared ring application is protected by the layer 1 (SONET) protection of the

GR-1230 Ring. If the layer 1 protection is unavailable, the Ethernet frames are
switched using layer 2 protection and share the remaining data path.

Note: It is possible to have point-to-point connections protected at layer 2

if they are built as regular shared ring connections.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 OPTera Packet Edge System protection 6-7

Figure 6-5
Packet Edge shared ring connection--Detail
F6404t.eps

NE
2x1000SX

NE
2x1000SX

Add Drop

Ethernet
equipment

Legend:

= SONET optical connections

= passthrough

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
6-8 OPTera Packet Edge System protection

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 7-1

OPC protection 7-
Each OC-48 system requires at least one operations controller (OPC). For 1:1
protection, equip the system with two OPCs. One serves as the primary OPC
and the other as the backup OPC. For a diagram, see Figure 7-1. The primary
OPC provides service to the network. The backup OPC remains in warm
standby mode, ready to take over the functionality of the primary OPC should
it be necessary.

The primary OPC becomes active when neither of the two OPCs is currently
active, and remains active when both OPCs are available for service. The
backup OPC becomes active only when the primary OPC fails or is not active
for any reason or loses communications with the primary OPC (as in the case
of a fiber cut). The backup OPC is also used to protect operations,
administration, maintenance, and provisioning (OAM&P) operations during
software downloads and maintains a backup of the primary OPC database.

The backup arrangement is revertive, which means that after the primary is put
back into service after a failure, control reverts to it from the backup OPC. The
backup OPC then returns to warm standby mode. The revertive switch is
implemented by the primary OPC. The OPCs monitor each other continuously,
each using a copy of the OPC warm standby (OWS) program. The protection
switch occurs when one OPC fails to respond to the poll requests of the other.

The OPC as a forced activity switching capability. This feature allows the
system administrator to manually force an activity switch from the primary to
the backup OPC or from the backup to the primary OPC. For more
information, see System Administration Procedures, 323-1201-302.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
7-2 OPC protection

Figure 7-1
The primary/backup OPC configuration (1:1 protection)
F0508

O OC-48 OC-48 O
OC-48 OC-48
P
terminal regenerator
··· regenerator terminal
P
C C
Primary OPC Backup OPC
(Standby)

Provisioning OC-48 configurations and STS connections using the

backup OPC
The provisioning of ring and linear configurations and the STS connections is
done through the OPC. Typically, the primary OPC should be used, but the
provisioning can also be done using the backup OPC.

If the backup OPC is used, the user must manually apply the provisioning data
to the primary OPC when it returns to service. Provisioning instructions are
provided in Provisioning and Operations Procedures, 323-1201-310.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 8-1

ESI protection 8-
The external synchronization interface (ESI) feature has two types of
protection, equipment protection for the ESI subunit circuit packs and timing
reference protection.

Protection-switching operations are performed independently at each terminal

or add-drop multiplexer (ADM) node that is equipped with ESI.

Neither equipment nor timing reference protection-switching operations affect

the traffic payload on the OC-48 lines or the tributaries.

The ESI alarms related to ESI protection activities are included in the critical,
major, minor, and warning counts shown on the network element user
interface’s banner line (at the top of the user interface screen), but not in the
FailProt, Lockout, and ActProt banner line indications.

Equipment protection switching

ESI equipment protection is automatically enabled when the shelf clock source
is set to ESI.

The two ESI subunit circuit packs protect each other on a 1+1 non-revertive
basis. The ESI equipment protection-switching functions are supported with
the following hierarchy, with the highest priority shown at the top:
• lockout (user initiated)
• forced (user initiated)
• automatic (system initiated as the result of an equipment failure of the
active ESI subunit)
• manual (user initiated)
Note: If both ESI subunits fail or if the system is forced to use a failed ESI
subunit, the shelf reverts to the OC-48 clock of ±20 parts per million (ppm)
as the timing source, which is equivalent to a network element not
equipped with ESI (that is, equivalent to freerunning mode).

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
8-2 ESI protection

Timing reference protection switching

ESI reference protection switching is automatically enabled when the ESI
circuit pack is in the in-service normal (active) state and the target filter mode
is normal. The protection scheme is N:1 (non-revertive), where N can be up to
three (three standby references for one currently active working reference).

The scheme is considered non-revertive because the network element does not
revert to the originally active reference in the case in which it automatically
switched to a timing reference of equal quality. However, if the originally
active reference was of a higher quality, the network element does revert to it
once it has been repaired because the best available timing reference is always
used.

The four possible timing references that can be provisioned as inputs are
BITSA, BITSB, OCA, and OCB. BITSA and BITSB are inputs from a
building integrated timing supply (BITS). OCA is a timing reference carried
on the OC-48 G1 optics and OCB is carried by the G2 optics.

The protection-switching functions are supported with the following

hierarchy, with the highest priority shown at the top:
• forced (user initiated)
• automatic (system initiated)
• manual (user initiated)
Lockouts of the timing references are not supported. However, a forced switch
can be applied to any one or more of the currently provisioned inputs to prevent
it being used as a timing reference source.

The behavior of the timing reference protection-switching features depend on

whether the ESI synchronization status messaging feature is available. This
feature requires a special versions of the ESI subunit and shelf processor.

With the ESI synchronization status messaging feature, the system ensures that
the best available timing reference input is used at each terminal or ADM node
according to a hierarchy of signal quality levels. The quality level corresponds
to the stratum level clock provided by the signal or other quality designation
(see System Description, 323-1201-100, for a detailed description of quality
designations and the ESI synchronization status messaging feature).
Automatic protection switches of the timing references are therefore
performed as required to maintain reference to the best available clock source.

If any two or more of the available references are equal in terms of their quality
level, the references are selected in the order in which they appear on the
timing reference provisioning screen. This screen lists up to four timing
references, numbered from 1 to 4. Priorities are assigned on a descending basis
from 1 to 4 when timing references are otherwise equal.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 ESI protection 8-3

Forced switches similarly cause the system to switch to the best of the
available timing references. Selection between timing references that are equal
in terms of their signal quality are made the same way as for automatic
switches (that is, based on the order they appear in the provisioning list).

With the ESI synchronization status messaging feature, manual switches of

timing references can only be made between timing references of equal
quality. This is because the highest quality signal is always used. If the
available signals change, an automatic switch to the next highest clock signal
occurs. At the same time, the timing reference hierarchy does not allow a
manual switch to a signal of a lesser quality clock signal.

If the ESI synchronization status messaging feature is not available, the

protection switching features work exclusively on the basis of the order in
which the timing reference inputs appear on the provisioning screen. That is,
the protection switch, whether automatic, forced, or manual, is always to the
next timing reference input in the list in descending order (from 1 to 4).

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
8-4 ESI protection

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 9-1

User-initiated protection-switching
features 9-
This chapter describes the user-initiated DS3, STS-1, OC-3, STM-1J, STS-12,
OC-12, and OC-48 protection-switching features, which are typically used for
maintenance purposes. These features are all available from the network
element user interface. In addition, various protection switching commands
can be operated through the operations controller (OPC), Transaction
Language 1 (TL1) interface, and telemetry, byte-oriented serial (TBOS)
interface.

Note 1: For the OC-48 transport circuit pack groups, you cannot provision
a circuit pack group to be out of service if there is an active protection
switch or lockout of protection against the opposite circuit pack group. If
a user-initiated protection switch exists against a circuit pack, deleting the
circuit pack removes the active protection switch. An automatic switch
replaces the user-initiated switch. When you place the equipment back into
service, the original protection switch is not restored. For revertive
protection-switching schemes, the automatic switch enters the
wait-to-restore state. For non-revertive schemes, the automatic switch
clears. If the user-initiated protection switch was performed from the OPC,
it remains active at the far-end network element.
Note 2: There is no support for external provisioning from the TL1
interface for STM-1J tributaries.
Note 3: The OPTera Packet Edge System (formerly iPT1000) interfaces
do not support any user-initiated protection switch commands. To
manually force a layer protection switch, see OPTera Packet Edge System
OC-48 User Guide.

DS3 and STS-1 protection-switching commands

DS3 tributary protection-switching is applied to DS3 mappers, each of which
supports three DS3 facilities. STS-1 tributary protection-switching is applied
to STS-1 interface circuit packs, each of which supports three STS-1 facilities.
In both cases, all three facilities are switched at the same time.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-2 User-initiated protection-switching features

Lockout
When the lockout command is invoked, a working DS3 mapper or STS-1
interface circuit pack is denied access to the associated protection DS3 mapper
or STS-1 interface circuit pack. The manual lockout overrides all other
protection-switching features, including automatic protection switching. If the
traffic is already on the protection circuit pack, it switches back to the working
circuit pack, even if the working circuit pack is declared failed (which can
result in a loss of traffic).

Any number of DS3 mapper or STS-1 interface circuit packs can be locked out
at the same time. Locking out the protection DS3 mapper circuit pack prevents
all DS3 mapper circuit packs from being protected. Similarly, locking out the
protection STS-1 interface circuit pack prevents all STS-1 interface circuit
packs from being protected.

For both DS3 and STS-1 tributaries, if traffic is on the protection circuit pack,
locking out the protection circuit pack switches traffic back to the working
circuit pack. If the standby is unequipped and unprovisioned, any lockout
attempt is denied.

Forced switch
For DS3 and STS-1 protection, a forced switch causes the traffic of a working
DS3 mapper or STS-1 interface circuit pack to be rerouted to the associated
protection DS3 mapper or STS-1 interface circuit pack. This occurs regardless
of the condition of the protection DS3 or STS-1, as long as no lockout or other
forced switch is active. Forced switches cannot be entered against the
protection DS3 mapper or STS-1 interface.

Manual switch
A manual switch is used to reroute the traffic on a working DS3 mapper or
STS-1 interface circuit pack to the associated protection circuit pack. The
traffic is rerouted only if the protection path does not have a fail condition. A
manual switch does not override automatic protection, another manual switch
of the same priority, a forced switch, or a lockout. Manual switches cannot be
entered against the protection DS3 mapper or STS-1 interface.

Wait to restore
There is a 300-second wait-to-restore period after a DS3 or STS-1 failure
clears. During the wait-to-restore period, the shelf processor monitors the DS3
or STS-1 working path to ensure that the failure is cleared. If no problem is
found during the wait-to-restore period, the protection switch is dropped and
the traffic is routed back through the normal working path. The protection path
is then available again for protection.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 User-initiated protection-switching features 9-3

Priority selection
The priority select feature allows the user to assign one of two priority levels
(low or high) to DS3 mapper and STS-1 interface circuit packs. The default
priority setting is low. A request for protection on a high-priority circuit pack
overrides a similar request on a low-priority circuit pack.

If the OC-48 shelf is equipped with both DS3 and STS-1 tributaries, the
protection DS3 mapper and the protection STS-1 interface share the switcher
and the switch controller circuit packs. Because these circuit packs can handle
only one protection switch at a time, the highest-priority protection switch
request is honored. If two equal priority requests are outstanding, the first
request received is honored.

DS3 and STS-1 loopback

Terminal and facility loopbacks are available for each DS3 and STS-1. The
loopback command is used when commissioning a system or adding a DS3 or
an STS-1 facility. Loopbacks can also be used to sectionalize faults.

In a DS3 or an STS-1 terminal loopback (TERMAIS), the selected DS3 or

STS-1 signal is looped back over the optics and the terminal AIS is sent to the
DS3 or STS-1 port. Figure 9-1 and Figure 9-2 illustrate a TERMAIS with
either network element 1 or network element 2 selected.

In a DS3 or an STS-1 facility loopback (FACAIS), the selected incoming DS3

or STS-1 signal is looped back to the DS3 or STS-1 out port. Figure 9-3 and
Figure 9-4 illustrate a FACAIS with either network element 1 or network
element 2 selected.
Figure 9-1
DS3 or STS-1 terminal loopback (TERMAIS) with network element 2 selected
F0033_R8

NE 1 NE 2
STS-1 or local LTE remote LTE STS-1 or
DS3 line DS3 line
in out
AIS AIS

STS-1 or STS-1 or
DS3 line DS3 line
out in
DS3

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-4 User-initiated protection-switching features

Figure 9-2
DS3 or STS-1 terminal loopback (TERMAIS) with network element 1 selected
F1465_R8

NE 1 NE 2
STS-1 or local LTE remote LTE STS-1 or
DS3 line DS3 line
in out

STS-1 or STS-1 or
DS3 line DS3 line
out in
AIS AIS

STS-1 or DS3 port STS-1 or DS3 port FW-1465 (R8)

Figure 9-3
DS3 or STS-1 facility loopback (FACAIS) with network element 1 selected
F0034_R8

NE 1 NE 2
STS-1 or local LTE remote LTE STS-1 or
DS3 line DS3 line
in out
AIS

STS-1 or STS-1 or
DS3 line DS3 iine
out in

STS-1 or DS3 port STS-1 or DS3 port FW-0034 (R8)

Figure 9-4
DS3 or STS-1 facility loopback (FACAIS) with network element 2 selected
F1466_R8

NE 1 NE 2
STS-1 or local LTE remote LTE STS-1 or
DS3 line DS3 line
in out

STS-1 or STS-1 or
DS3 line DS3 line
out in
AIS

DS3 or STS-1 port DS3 or STS-1 port

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 User-initiated protection-switching features 9-5

DS3 and STS-1 protection-switching hierarchy

Table 9-1 summarizes the DS3 and STS-1 protection hierarchy.
Table 9-1
DS3 and STS-1 protection-switching hierarchy and control

Priority Type of protection switch Control

1 Lockout User

Forced switch

2 High priority User

3 Low priority User

Automatic switch

4 High priority Automatic

5 Low priority Automatic

Manual switch

6 High priority User

7 Low priority User

8 Wait to restore Automatic

9 Exerciser Automatic/User

Note: User-initiated protection switching can be applied to DS3 mappers

or STS-1 interfaces that are not carrying traffic. All signals on the DS3
mapper or STS-1 interface are out of service (OOS). In this case, the
hierarchy in Table 9-1 is still valid.

OC-3 and OC-12 protection-switch commands

These maintenance descriptions apply to the OC-3, STS-12, and OC-12
tributaries on OC-48 terminal shelves. The affected tributary must be equipped
with a working and a protection OC-3, STS-12, or OC-12 interface for 1+1
non-revertive protection. OC-3 tributaries using double-width interfaces must
also be provisioned as protected.

OC-3 carriers support two half-height OC-3 interfaces. The odd-numbered

circuit pack group (G9 to G39) includes interfaces in the upper position of the
OC-3 carriers. The even-numbered circuit pack group (G10 to G40) includes
interfaces in the lower position of the OC-3 carriers.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-6 User-initiated protection-switching features

Double-width OC-3 interfaces and STS-12 and OC-12 interfaces are identified
as circuit pack groups G1 to G8 according to their quadrants and shelf
positions. Each quadrant has an odd-numbered and an even-numbered circuit
pack group.

In normal operation, the odd-numbered circuit packs are used for the normally
working interfaces and the even-numbered circuit packs for the normally
protection interfaces.

If a protection switch occurs from the working to the protection interface, the
protection channel becomes active for the duration of the protection switch.
Normally, the odd-numbered circuit pack is the working interface. After the
conditions that caused an automatic protection switch are cleared, manually
switch the traffic back from the even-numbered circuit pack to the
odd-numbered circuit pack.

These commands have no affect on quadrants containing unprotected

tributaries, including quadrants equipped with two double-width OC-3
interfaces provisioned as unprotected tributaries.

Lockout
Only the odd-numbered circuit pack groups can be locked out. The
even-numbered circuit pack groups cannot be locked out. When traffic is on
the odd-numbered circuit pack, a lockout causes the traffic to remain on that
circuit pack regardless of any other type of protection switch. For a list of the
relative priorities of protection switches, see Table 9-2. If the traffic is on the
even-numbered circuit pack when the lockout is performed, the traffic reverts
to the odd-numbered circuit pack.

Note 1: If a signal failure is detected on the corresponding even-numbered

circuit pack while a lockout is active, the user interface indications change.
Although the traffic remains on the odd-numbered circuit pack (that is, no
actual protection switch occurs), the user interface indicates that an
automatic switch has occurred and that a lockout is pending.
Note 2: If the even-numbered circuit pack group (equipment) is not
provisioned or is out of service (OOS) when a lockout command is entered,
the lockout is denied. Protection-switching commands are not accepted if
the protection slot is empty or unprovisioned.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 User-initiated protection-switching features 9-7

Forced switch
The forced switch command can be used on either the working or the
protection channel (on whichever circuit pack is the current working to the
current protection circuit pack). A forced switch moves the OC-3, STS-12, or
OC-12 traffic from one circuit pack group to the other. For example, a forced
switch on G1 moves the traffic to G2, and a forced switch on G2 moves the
traffic to G1.

A forced switch to the protection circuit pack (even-numbered circuit pack

group) is completed only if there is no failure condition on the protection
channel, and no active lockout or forced switch on the working circuit pack
(odd-numbered circuit pack group).

If the protection channel is active (the traffic is being carried on the

even-numbered circuit pack), the traffic is switched to the odd-numbered
circuit pack. The switch occurs if there is no lockout or active forced switch on
the odd-numbered circuit pack, even if there is a failure condition on that
channel.

When a forced switch moves traffic to an odd-numbered (working) circuit

pack from the corresponding even-numbered circuit pack (protection) when
there is a failure on the working channel, an appropriate alarm is raised for the
working channel.

Manual switch
The manual switch command can be used on either the working or the
protection channel (on whichever circuit pack is currently active to the current
standby circuit pack). A manual switch moves the OC-3, STS-12, or OC-12
traffic from one circuit pack group to the other. For example, a manual switch
on G1 moves the traffic to G2, and a manual switch on G2 moves the traffic to
G1.

A manual switch is completed only if there is no signal-degrade or failure

condition on the channel to which the switch is being made. A manual switch
does not override any other switch type, that is, an automatic protection switch,
another manual switch, a forced switch, or a lockout.

Because the protection scheme is non-revertive, the manual switch request

indications in the user interface are released automatically as soon as the
switch is completed, and there is no manual switch active indication. This
means that there is no need to issue a manual switch release command as there
is to release a forced switch. To return the traffic to the originally active
channel, another manual switch must be performed.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-8 User-initiated protection-switching features

OC-3, STS-12, and OC-12 protection-switching hierarchy

Table 9-2 summarizes the protection-switching hierarchy for OC-3, STS-12,
and OC-12 tributaries.
Table 9-2
OC-3, STS-12, and OC-12 protection-switching hierarchy and control

Priority Type of protection switch Control

1 Automatic protection switch to the working channel Automatic

(odd-numbered) due to a signal failure on the
corresponding protection channel (even-numbered)

2 Lockout User

3 Forced switch User

4 Automatic protection switch to the protection channel Automatic

(even-numbered) due to the removal of the
corresponding working circuit pack (odd-numbered)

5 Automatic protection switch to the protection channel Automatic

(even-numbered) due to a signal failure on the
corresponding working channel (odd-numbered)

6 Automatic protection switch due to a signal-degrade Automatic

condition on either the working or protection channel
(see Notes 1 and 2)

7 Manual switch User

8 Exerciser Automatic/User

Note 1: When a signal degrade occurs on the working channel, a

protection switch takes place. If the protection path signal degrades while
traffic is on the protection channel, the protection switch does not drop.
Note 2: If the protection channel signal is degraded (see “Switch times”
on page 2-3), a forced or automatic switch can only occur at the end at
which the protection path is not degraded.
Note 3: It is recommended that the half-height OC-3 interface in slot 16
(P1/P2) be provisioned only during carrier replacement. The OC-48
network element does not support any other operations done on this
tributary (including protection switches).

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 User-initiated protection-switching features 9-9

STM-1J protection-switch commands

These maintenance descriptions apply to the STM-1J tributaries on OC-48
terminal shelves. The affected tributary must be equipped with a working and
a protection STM-1J interface for 1+1 non-revertive protection.

OC-3 carriers support two STM-1J interfaces. The odd-numbered circuit pack
group (G9 to G39) includes interfaces in the upper position of the OC-3
carriers. The even-numbered circuit pack group (G10 to G40) includes
interfaces in the lower position of the OC-3 carriers.

There is no pending state for protection switch requests on the STM-1J

interface.

Protection-switching commands are not accepted if the protection slot is

empty or unprovisioned.

Lockout
A lockout is performed on the currently designated protection channel. The
traffic never switches channels as a result of a lockout. The traffic remains
where it is at the time of the lockout.

When the wait-to-restore period expires after an automatic switch or when you
release a forced switch, the traffic on the protection channel does not revert to
the corresponding working channel. The network element exchanges the
working and protection designation for the channels, which means that the
channel that now carries the traffic becomes the working channel.

The lockout is always performed on the channel designated as the protection

channel, which can be either the odd-numbered or even-numbered circuit
pack. You therefore do not need to specify which circuit pack group you are
locking out.

Lockouts on the STM-1J interface are nodal. Only the local network element
is locked out. The system does not signal the lockout to the far-end equipment
using the K-bytes. When a lockout is active, the contents of the K-bytes remain
as they were when the lockout was initiated.

Note: This note outlines a permanent limitation due to Japan standards.

The K-byte signaling is frozen after a lockout is applied and the automatic
switch remains active until the lockout is released. If a lockout is applied
and both tributary circuit cards are removed from the shelf, when the first
tributary is reinserted, the STM-1J circuit pack will detect any line
problems, such as LOS (loss of signal), before the shelf processor has time
to send the lockout request to the tributaries. As a result, an asterisk (*) is
displayed against both lockout and auto switch at the same time.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-10 User-initiated protection-switching features

Note: This note outlines a permanent limitation due to Japan standards. If

the far-end lockout is issued after the near end is in wait-to-restore period,
then the near end requests a forced switch be completed. Generally, the
forced switch request is denied if the far end is in lockout state. But with
Japan standards, it will not be obvious to the operator that a far-end lockout
exists until an attempt is made to release the forced switch.

Forced switch
The forced switch command can only be used to switch traffic from the
working channel to the protection channel. Either the odd-numbered or
even-numbered circuit pack group can be designated as the working channel
at a given point. For example, if G9 is currently designated as the working
channel, G10 is the protection channel, and you can apply a forced switch on
G9 to move the traffic to G10.

While the forced switch is active, G10 remains designated as the protection
channel. When you release the forced switch, the traffic remains on G10 but
the designations of the channels are exchanged. G10 becomes designated as
the working channel and G9 becomes designated as the protection channel.
You enter a subsequent forced switch against G10 which is the current working
channel.

A forced switch to the protection circuit pack is completed only if there is no

failure condition on the protection channel and no active lockout of the
protection channel or forced switch on the working channel. If you initiate a
forced switch, an appropriate alarm is raised for the working channel. If you
attempt to force the traffic from the protection channel to the working channel,
the system does not accept the command.

Wait to restore
The wait-to-restore period after an STM-1J failure clears is, by default, set to
5 minutes. However, this wait-to-restore period is provisionable through the
network element user interface. The user can choose to set this period at 30
seconds, as well as at 1, 2, 3, 5 or 10 minutes. For instructions on how to
provision the STM-1J wait-to-restore period, see Protection Switching
Procedures, 323-1201-311.

The wait-to-restore period only begins when the channel returns to the normal
state after recovering from a failure. During the wait-to-restore period, the
shelf processor monitors the STM-1J working path to ensure that the failure is
cleared. If no problem is found during this period, the protection switch is
dropped. Once the wait-to-restore period has expired, the traffic on the
protection channel does not revert to the corresponding working channel. The
network element exchanges the working and protection designation for the
channels, which means that the channel that now carries the traffic becomes
the working channel.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 User-initiated protection-switching features 9-11

The wait-to-restore period is dropped, however, if a higher priority switch is

initiated during this wait-to-restore period.

Detection guard time

A channel is not declared to be in the failed state when a signal fail or a signal
degrade begins. The signal fail or signal degrade must be present on the
channel for a period of time, a period called the detection guard time. For the
STM-1J tributary, this guard time can be provisioned to be 50, 100 or 500
milliseconds as well as 1, 2, 3, 4 or 5 seconds. By default, the detection guard
time is set to one second. For more instructions on how to provision the
detection guard time, see Protection Switching Procedures, 323-1201-311.

Note: This note outlines a permanent limitation due to Japan standards. If

the Detection Guard Times (TDGs) are set differently on the STM-1J of
near-end and far-end network elements, then the time taken to switch
differs depending on whether the working or the protection channel
tributary circuit card is removed.

When the working channel tributary circuit card is removed, both near end
and far end will switch according to the far-end TDG. The far end, where
the LOS is received, will send out a non-zero value to indicate working is
in failed state; then the near end will switch when the far-end TDG expires.

When the protection channel tributary circuit card is removed, the far end
will switch based on its TDG but the near end will switch based on its TDG
due to the Japan standard of sending a zero to indicate the protection
channel failures. The far end where the LOS is received will send out a zero
to indicate protection failed state, but the near end will see this as idle and
will not switch until its own TDG expires.

Recovery guard time

A channel is not declared to be in the normal state when a signal fail or a signal
degrade ends. The signal fail or signal degrade must be absent on the channel
for a period of time, a period called the recovery guard time. For the STM-1J
tributary, this guard time can be provisioned to be 50, 100 or 500 milliseconds
as well as 1, 2, 3, 4 or 5 seconds. By default, however, the recovery guard time
is set to one second. For instructions on how to provision the recovery guard
time, see Protection Switching Procedures, 323-1201-311.

Response verification time

The response verification time is the set time after a protection switch request
is made but before a protection switch becomes active. By default, the response
verification time is set at 500 milliseconds. The user can provision the response
verification time to be 1 second. For instructions on how to provision the
response verification time, see Protection Switching Procedures,
323-1201-311.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-12 User-initiated protection-switching features

STM-1J protection-switching hierarchy

Table 9-3 summarizes the protection-switching hierarchy for STM-1J
tributaries.
Table 9-3
STM-1J protection-switching hierarchy and control

Priority Type of protection switch Control

1 Lockout (see Note 1) User

2 Automatic protection switch to the working channel Automatic

(odd-numbered) due to a signal failure, signal degrade,
or equipment fault on the corresponding protection
channel (even-numbered)

3 Forced switch (see Note 2) User

4 Automatic protection switch to the protection channel Automatic

(even-numbered) due to an equipment failure or signal
failure on the corresponding working channel
(odd-numbered)

5 Automatic protection switch due to a signal-degrade Automatic

condition on the working channel

6 Wait to restore Automatic

Note 1: If a lockout is activated, the wait-to-restore period continues.

Note 2: A forced switch cancels the wait-to-restore period.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 User-initiated protection-switching features 9-13

OC-48 protection-switch commands for linear systems

OC-48 transport-level protection-switching operations apply to all 48 STS-1
timeslots on the affected optical circuit pack group. All 48 timeslots are
switched at the same time.

Lockout
When the lockout command is invoked, the traffic on the G1 working channel
is denied access to the OC-48 G2 protection channel. The manual lockout
overrides all other protection features, including automatic protection
switching.

Locking out the G2 protection channel prevents any G1 working channel

traffic from being protected. This is true even in the case of a unidirectional
switch request where the far-end protection shelf is locked out. If traffic is on
the G2 protection channel, locking out the G2 protection channel switches
traffic back to the G1 working channel.

If the standby is unequipped and unprovisioned, any lockout attempt is denied.

Note: All terminals in a multishelf 1:N system should be in the same OPC
span of control. This ensures that the network banner line on the OPC
screen carries information which might be unavailable if the system is
contained in more than one OPC span of control. A lockout of an OC-48
working channel is visible only on the user interface and the maintenance
interface at the network element at which it was initiated. For the network
element at the opposite end of the channel, the lockout of the working
channel appears on the network banner line, provided both network
elements are in the same span of control.

Forced switch
If a forced protection switch is initiated on an OC-48 channel, working traffic
is rerouted to protection if the protection path has no fail condition and there
is no lockout or other active forced switch. All traffic is rerouted in
bidirectional switching, whereas only receive traffic is rerouted in
unidirectional switching.

Manual switch
A manual switch is used to reroute the traffic from one OC-48 circuit pack
group to the other. The switch is performed only if there is no higher-priority
protection-switch request.

A manual switch does not override automatic protection, another manual

switch, a forced switch, or a lockout.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-14 User-initiated protection-switching features

For OC-48 1+1 protection, the manual switch is automatically released after
the switch is completed. The traffic then remains on the channel to which it
was switched. To move traffic back to the original channel, another manual
switch must be performed.

Wait to restore
In single-shelf 1:1 systems and multishelf 1:N systems, the default
wait-to-restore period is 5 minutes (300 seconds). The EWTRCI CI tool can
be used to change the wait-to-restore period from 1 to 24 hours or to infinite
wait to restore. For a description of extended wait to restore, see “Protection
oscillation control in single-shelf 1:1 and multishelf 1:N systems (extended
wait to restore)” on page 9-16.

After the cause of an automatic protection switch from the working channel is
cleared, the OC-48 demultiplexer circuit pack monitors the working channel
for the duration of the wait-to-restore period to ensure that the failure is
cleared.

If no problem is found during the wait-to-restore period, the protection switch

is dropped and the traffic is routed back through the normal working channel,
making the protection channel available for protection.

OC-48 protection-switching hierarchy for linear systems

Table 9-4 summarizes the OC-48 protection hierarchies for linear systems,
starting with the highest-priority feature. The table also shows how each
protection switch is controlled.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 User-initiated protection-switching features 9-15

Table 9-4
OC-48 maintenance features and control for linear systems

Priority Type of protection switch Control

1 Automatic protection switch from protection to Automatic

working due to a signal failure of the protection
channel (see Note 1)

2 Lockout User

3 Forced switch User

4 Automatic protection switch due to a signal failure on Automatic

the working channel (see Note 2)
Automatic protection switch due to a signal-degrade Automatic
(see Note 2, Note 3, and Note 4)

5 Manual switch User

6 Wait to restore Automatic

7 Exerciser Automatic/User

8 Extra traffic on multishelf 1:N systems only (see User

Note 5 and Note 6)

Note 1: A signal failure on the protection channel has a higher priority

than a lockout when OC-48 NT8E05 demultiplexers with PEC codes
ending with CB or higher are being used.
Note 2: In 1:N systems, working channels can be assigned high or low
priority. If a high-priority channel requires protection switching, it
overrides the equivalent type of protection switch granted to low-priority
channels. However, note that the priority settings have no effect when the
protection switches are user-initiated.
Note 3: A protection switch as the result of signal degradation on a
working channel is not dropped if signal degradation subsequently occurs
on a protection channel. Both channels are declared degraded.
Note 4: If the protection channel degrades before a working channel
degrades, there is no automatic switch to the protection channel.
Note 5: Extra traffic is viewed by the system as an idle request (that is, no
protection switch is active).

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-16 User-initiated protection-switching features

Note 6: While extra traffic is enabled, the exerciser cannot run the OC-48
portion of the routine on any shelf (working or protection) in the 1:N
system. However, the tributaries are exercised. If extra traffic is enabled
while the exerciser is currently running, the extra traffic request remains
pending until the exerciser has completed the routine (on the shelf, if run
from the network element user interface or, if run from the OPC, on all
shelves within the protection group). The user has the option of squelching
the extra traffic for the duration of a manual exerciser run (upon
completion of which the extra traffic is automatically reestablished).

Protection oscillation control in single-shelf 1:1 and multishelf 1:N

systems (extended wait to restore)
Protection oscillation is caused by an intermittent condition that causes
repeated automatic protection switches over a period of time. Extended wait to
restore prevents protection oscillation in single-shelf 1:1 systems and
multishelf 1:N systems.

Extended wait to restore is controlled by the EWTRCI command interpreter

(CI) tool. The EWTRCI tool can be used to:
• enable or disable extended wait to restore
• provision a wait-to-restore period of infinity or from 1 to 24 hours in
1-hour increments
• reset the timer
• release a protection switch before the wait-to-restore period expires
• query the amount of time left in an in-progress wait-to-restore period
Note: For instructions on how to provision the EWTRCI tool, see
Procedure 1-8, “Provisioning the wait-to-restore period” in Protection
Switching Procedures, 323-1201-311.

Traffic reverts from the protection channel to the original working channel
after the cause of the switch is cleared and after the wait-to-restore period
expires.

On newly installed systems, extended wait to restore is disabled by default and

the wait-to-restore period is set to 5 minutes (300 seconds). Once the user
enables extended wait to restore, the wait-to-restore period is set to infinite.
The user can then set a new wait-to-restore period.

Note 1: To maintain consistency throughout the OC-48 system, set the

extended wait-to-restore parameters to the same values on each network
element.
Note 2: In multishelf 1:N systems, the FWPROSCI tool inhibits the
EWTRCI tool. For instructions on how to use this tool, see Alarm Clearing
Procedures, 323-1201-543.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 User-initiated protection-switching features 9-17

Note 3: If the system was running Release 10.31 before an upgrade to

Release 14, the extended wait-to-restore parameters are based on the
previous values.
Note 4: If the system was running Release 13 before an upgrade to Release
14, the extended wait-to-restore parameters are set to the previous infinite
wait-to-restore values. If infinite wait to restore is turned on before the
upgrade, extended wait to restore turns on after the upgrade with the period
set to infinite.
Note 5: After restarts that last less than 4 minutes, the extended
wait-to-restore period resets from the beginning and any previous
protection switch continues on protection. After restarts that last longer
than 4 minutes and after reboots, the wait-to-restore period expires and any
previous protection switch reverts to working.

Protection switch interactions

Extended wait to restore interacts with the various types of protection switches
on the system. These interactions depend on the type of protection switch,
whether the switches are on the same or different channels for 1:N systems,
and whether the protection switching is bidirectional or unidirectional.
Higher priority switch requests
Extended wait to restore is dropped when higher-priority switches occur in the
system. These include lockouts, forced switches, signal fail, automatic
switches due to signal degrade or equipment failure, protection-loop fail, and
manual switches. Once the higher-priority switch is cleared, the extended
wait-to-restore timer resets and the lower-priority switch resumes for the full
wait-to-restore period.

To manually drop the extended wait-to-restore period before it expires:

• release the timer by using the ewtr_timer release command
• issue, then release, a manual switch on the same network element
• turn extended wait to restore off

Lower priority switch requests

Lower priority switch requests do not interrupt the protection switch or the
wait-to-restore period. These lower-priority switches include requests to
enable extra traffic, and switch requests from the protection exerciser.
Bidirectional protection switching
In systems provisioned for bidirectional protection switching, if a protection
switch of equal or higher priority exists when the protection switch request is
received, the protection switch request is not completed.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-18 User-initiated protection-switching features

Unidirectional protection switching

In systems provisioned for unidirectional protection switching, the two
directions of traffic can be switched independently. If a higher-priority
protection switch exists when the protection switch request is received for the
same working channel, it is accepted if the request is for the opposite direction.
The protection switch request is rejected if it is on the same terminal in the
same direction as the higher or equal priority switch.

For unidirectional protection switching, to switch traffic away from an OC-48

transmit interface, manually switch the traffic at the far-end terminal. To
switch traffic away from an OC-48 demultiplexer or OC-48 receive interface,
manually switch the traffic at the near-end terminal. The green LEDs on the
circuit packs turn off when the circuit packs are not carrying traffic.

On a 1:N system with unidirectional switching and a lockout of protection

(LOP) in one direction, any attempt to switch traffic from a working channel
to the protection channel in the opposite direction to the LOP will cause a lost
of working traffic.

Extra traffic
Extra traffic on the protection channel is lost during any protection switch and
for the duration of the wait-to-restore period. The traffic from the working
channel preempts the extra traffic on the protection channel.

Alarms and logs

While the system is in an extended-wait-to-restore state, the “Extended WTR
in progress” alarm becomes active and an FAC403 log is generated. The alarm
becomes active within 2 minutes after the start of the protection switch. The
alarm clears after the wait-to-restore expires, or if the traffic is manually
reverted back to the working channel. No alarm becomes active if a signal fail
is shorter than 300 ms. The alarm and log are provided for information
purposes only, and therefore no user action is required either as a result of the
alarm or the log. To clear the “Extended WTR in progress” alarm, see Alarm
Clearing Procedures, 323-1201-543. For log details, see Log Report Manual,
323-1201-840.

OC-48 protection-switching commands for GR-1230 Rings

OC-48 transport level protection-switching operations apply to only 24 STS-1
timeslots on the affected circuit pack group (that is, switching 24 working
timeslots from one circuit pack group to the 24 protection timeslots of the
other, or returning the traffic from the protection timeslots to the working
timeslots). All 24 timeslots are switched at the same time.

Lockout of working and lockout of protection

In the OC-48 GR-1230 Ring, separate lockout of working and lockout of
protection commands are provided. The separate commands are required
because each of the two fibers in the GR-1230 Ring carry 24 working and 24

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 User-initiated protection-switching features 9-19

protection STS-1 timeslots. They allow the working and protection timeslots
to be locked out separately on a circuit pack group basis (at the OC-48 G1 and
G2 transport interfaces) at the add-drop multiplexer (ADM) nodes in the ring.
Lockout of working
The lockout working command prevents a protection switch for the specified
circuit pack group on the span to which it is applied. For example, if a lockout
of working is applied to G1, G1’s working timeslots cannot switch to G2’s
protection timeslots.

Because the lockout of working command is not signaled by way of the

K-bytes, it must be applied at both ends of the fiber span. If the command is
issued from the OPC and both ADMs are in the same span of control, the
command can be entered for only one ADM node and the OPC signals both
ADMs for the lockout of working request.

If the lockout of working command is issued from the local network element
user interface, the user must explicitly enter it at both ADM nodes terminating
the span. A warning message is presented when the command is entered
through the network element user interface that indicates that the command
must also be issued at the adjacent ADM node. If the command is entered at
only one end, a protection switch is still prevented on that span. However, if a
protection switch is requested at the far end, a “Protection switch fail” alarm
becomes active. Entering the command at both ends prevents this alarm from
being active. Extra traffic on the protection timeslots is not affected by the
lockout of working.
Lockout of protection
When lockout of protection is applied to a circuit pack group, the protection
timeslots on the optical line of the whole ring cannot be used by any other
nodes in the ring. For example, if a lockout of protection is applied to G2, G1’s
working timeslots cannot switch to G2’s protection timeslots. Extra traffic on
the protection timeslots is not affected by the lockout of protection.

If a lockout of protection and a protection request are operated on the same

span but initiated from different ends, the protection request is not completed.
This applies to all types of protection requests.

Equipment cannot be placed out of service on an OC-48 ring if a lockout of

protection is active.

Forced switch
In an OC-48 GR-1230 Ring, the forced switch command transfers the working
add-drop STS-1 timeslots (a maximum of 24 STS-1 signals, including any of
STS-1 signals 1 to 24) on one circuit pack group at an ADM node to the
corresponding protection timeslots (any of STS-1 signals 25 to 48) on the
second circuit pack group at that ADM node.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-20 User-initiated protection-switching features

The incoming passthrough timeslots are received on the protection timeslots

(which can be any of STS-1 signals 25 to 48) of the protecting circuit pack
group, rather than on the circuit pack group originally carrying the working
timeslots. These protection timeslots are then looped back into the protecting
circuit pack group’s own corresponding working timeslots.

Any extra traffic provisioned on the protection channels is dropped and traffic
is squelched on tributaries that have extra traffic. An alarm indication signal
(AIS) is inserted on the tributaries provisioned for extra traffic and the “Loss
of extra traffic” alarm becomes active.

Having more than one forced switch command active around the ring results
in the ring being segmented.

Manual switch
The manual switch command transfers the working add-drop timeslots (a
maximum of 24 STS-1 signals, including any of STS-1 signals 1 to 24) on one
circuit pack group at an ADM node to the corresponding protection timeslots
(any of STS-1s 25 to 48) on the second circuit pack group at that ADM node.

The incoming passthrough timeslots are received on the protection timeslots

(which can be any of STS-1 signals 25 to 48) of the protecting circuit pack
group, rather than on the circuit pack group originally carrying the working
timeslots. These protection timeslots are then looped back into the protecting
circuit pack group’s own corresponding working timeslots.

When extra traffic is lost because of a manual switch, traffic is squelched and
an AIS is inserted on the tributaries provisioned for extra traffic. The “Loss of
extra traffic” alarm becomes active.

This command is allowed only if the protection path has no fail condition and
there is no lockout or other active forced switch on that ADM node. While a
manual switch is active in the ring, any request for a manual switch on a
different span in the ring is rejected. A manual switch request is removed when
a protection switch of a higher priority is requested anywhere in the ring.

Wait to restore
The user can provision a wait-to-restore period of 1 to 12 minutes or to infinity
after an automatic switch clears. The default period is 5 minutes. During the
wait-to-restore period, the OC-48 ring demultiplexer circuit pack monitors the
affected span. If it finds no problems during the wait-to-restore period, it drops
the protection switch, and routes the traffic back through the normal working
path. The protection path is again available for protection.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 User-initiated protection-switching features 9-21

If there are two unidirectional failures at the same time on the same span, and
if one of the failures is removed before the other, both network elements
initiate the wait-to-restore period only after the second failure clears. If the two
wait-to-restore periods are different, the overall wait-to-restore period equals
the longer value.

Note: During the expiry of a wait-to-restore period on the G1 circuit pack

of a specific NE, the G2 side of the same NE may send line AIS
downstream to its neighboring NE, causing an auto-switch on the span
facing the G2 circuit pack group. There is a 0.47% (61/13046) occurrence
of this problem.

Working traffic on the switched span will experience a 60ms hit and extra
traffic in the ring is lost.

OC-48 protection-switching hierarchy for GR-1230 Rings

Table 9-5 summarizes the OC-48 protection hierarchies for GR-1230 Ring
ADM nodes, starting with the highest-priority feature. The table also shows
how each feature is controlled.

Table 9-5
OC-48 protection-switching and maintenance hierarchy for GR-1230 Rings

Priority Type of protection switch Control

1 Lockout of protection, User

lockout of working, or User
signal fail of protection Automatic

2 Forced switch User

3 Automatic protection switch of working

Due to signal failure Automatic

Due to signal degrade Automatic

4 Manual switch User

5 Wait to restore Automatic

6 Exerciser Automatic/User

Matched-nodes protection-switch commands

Lockout of protection
A lockout of protection applied to an STS path in a matched-node inter-ring
connection prevents traffic from being selected from the secondary feed,
regardless of the condition of the primary feed or secondary feed.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-22 User-initiated protection-switching features

If a lockout of protection and a protection request are operated on the primary

gateway, the protection request is not completed. This applies to all types of
protection requests.

You must have the transmit interfaces and demultiplexers equipped on the
selector node that support the enhanced matched-node capabilities. For the
currently available circuit packs, see Ordering Information, 323-1201-151.

Forced switch
A forced switch applied to an STS path in a matched-node inter-ring
connection forces the traffic to be selected from the secondary feed, regardless
of the condition of the secondary feed (that is, a forced switch overrides an
automatic protection switch).

If the secondary feed was selected prior to the forced switch, the forced switch
has no effect.

Manual switch
A manual switch applied to an STS path in a matched-node inter-ring
connection forces the traffic to be selected from the secondary feed, regardless
of the condition of the secondary feed.

The incoming passthrough timeslots are received on the protection timeslots

(which can be any of STS-1 signals 25 to 48) of the protecting circuit pack
group, rather than on the circuit pack group originally carrying the working
timeslots. These protection timeslots are then looped back into the protecting
circuit pack group’s own corresponding working timeslots.

This command is allowed only if the secondary feed has no fail condition and
there is no lockout or other active forced switch on the primary gateway. A
manual switch request is removed when a protection switch of a higher priority
is requested on the primary gateway.

You must have the transmit interfaces and demultiplexers equipped on the
selector node that support the enhanced matched-node capabilities. For the
currently available circuit packs, see Ordering Information, 323-1201-151.

Wait to restore
A 300-second wait-to-restore period is allowed after the clearance of a failure
on an STS path between matched nodes, which resulted in a protection switch.
During the wait-to-restore period, the OPC monitors the primary path to
ensure that the failure is cleared. Then, if no further problem is found during
the wait-to-restore period, the protection switch is dropped and the traffic is
routed back through the primary path.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 User-initiated protection-switching features 9-23

The wait-to-restore period for a matched-node protection switch can be of

indefinite duration when an OC-48 line switch is active at the same time as the
matched-node switch. When the OC-48 line switch is cleared, then the
matched-node wait-to-restore period takes effect as usual.

If the secondary feed fails at any time during an active matched-node

automatic protection switch or wait-to-restore period, the primary feed is
selected.

Matched-nodes protection-switching hierarchy for GR-1230 Rings

Table 9-6 summarizes the OC-48 protection hierarchies for ADM nodes in a
GR-1230 Ring starting with the highest-priority feature. The table also shows
how each feature is controlled.

Note: All types of protection switch (user-initiated and automatic) within

a ring have a higher priority than inter-ring protection switches.

Table 9-6
Protection-switching and maintenance hierarchy for matched nodes

Priority Type of protection switch Control

1 Lockout of protection User

2 Forced switch User

3 Automatic protection switch

Due to path alarm indication signal, loss of Automatic

pointer, or STS path unequipped

Due to signal failure Automatic

Due to path defect indicator Automatic

Due to signal degrade Automatic

4 Manual switch User

5 Wait to restore Automatic

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
9-24 User-initiated protection-switching features

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 10-1

Extra traffic 10-

This chapter describes the extra traffic features available on OC-48 multishelf
1:N systems and GR-1230 Rings. The 1:N extra traffic feature allows
additional traffic to be carried on the protection channel. In a GR-1230 Ring,
extra traffic can be carried on the protection timeslots of either fiber in the ring.

Extra traffic on a linear 1:N protection shelf

Extra traffic allows the protection channel of a multishelf 1:N system to carry
traffic when it is not protecting a failure. For an example, see Figure 10-1.

For the protection channel to carry extra traffic:

• the tributaries on the protection shelf must be present and provisioned
• equip the protection shelf with the appropriate DS3 mappers or STS-1
interfaces, switchers, switch controller, interface ports, interface carriers;
OC-3, STS-12, or OC-12 interfaces
Note: STM-1J and OPTera Packet Edge System (formerly iPT1000)
interfaces are supported on GR-1230 Rings only.

Any protection switch, such as automatic, forced, and manual switches, from
a working channel to the protection channel causes the extra traffic to be
dropped. If the protection channel is locked out or there is a failure anywhere
on the protection loop, extra traffic is also dropped. In the case of automatic
switches, including intermittent failures, extra traffic remains dropped until the
wait-to-restore period expires.

All extra traffic events, such as enable, disable, or loss of traffic because of a
protection switch, are logged on the protection shelf and routed to the
Transaction Language 1 (TL1) and telemetry byte-oriented serial (TBOS)
interfaces for remote monitoring.

Unidirectional and bidirectional extra traffic

The OC-48 network element supports both unidirectional and bidirectional
extra traffic.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
10-2 Extra traffic

Bidirectional extra traffic

Bidirectional extra traffic is similar to bidirectional protection switching in a
1:N system, in that both or neither direction of the protection channel is used
by extra traffic, depending on whether a working channel is overriding extra
traffic.

Extra traffic must be enabled at both ends of the line (that is, for each direction)
for which extra traffic is required, regardless of the protection-switching mode.
Figure 10-1
Multishelf 1:N system with extra traffic
F1611-1_R13

Site A Protection channel Site B

G1 extra traffic G1
(see Note 3)
• • Demux OC-48 Rx OC-48 Rx Demux • •
• •
• STS-48 Tx STS-48 Tx •
see see see see
Note 1 Note 2 Note 2 Note 1
• •
• OC-48 Tx OC-48 Tx •
• •
Demux STS-48 Rx STS-48 Rx Demux
G2 G2
P-Loop P-Loop
G1 G1
Channel 1
• Demux OC-48 Rx OC-48 Rx Demux •
• •
• • OC-48 Tx OC-48 Tx • •
see see see see
Note 1 Note 2 Note 2 Note 1
• •
• STS-48 Tx STS-48 Tx •
• •
• Demux STS-48 Rx STS-48 Rx Demux
G2 • • • • G2
• • • •
• • • •
G1 G1
Channel 11
• Demux OC-48 Rx OC-48 Rx Demux •
• •
• • OC-48 Tx OC-48 Tx • •
see see see see
Note 1 Note 2 Note 2 Note 1
• •
• STS-48 Tx STS-48 Tx •
• •
Demux STS-48 Rx STS-48 Rx Demux
G2 G2 Legend:
= selector (switch)
Note 1: To and from DS3, STS-1, OC-3, STS-12, or OC-12 tributaries.
Demux = demultiplexer
Note 2: DS3 mappers or STS-1 interfaces (G1 to G16 or protection) or OC-3, STS-12, or OC-12 interfaces.
Rx = receive interface
Note 3: The protection channel cannot carry STS-1 tributary traffic as extra traffic.
Tx = transmit interface

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Extra traffic 10-3

Unidirectional extra traffic

Unidirectional extra traffic results in one, both, or neither direction of the
protection channel carrying extra traffic. This is based on whether extra traffic
is enabled at both ends of the system and whether it is overridden by a
higher-priority protection-switch request.

Unlike bidirectional protection switching, in which only one channel can

occupy the protection channel at a time, unidirectional extra traffic permits a
working channel to use one direction of the protection channel while extra
traffic is carried in the opposite direction. If the system is in unidirectional
protection-switching mode and extra traffic is enabled, an automatic switch
request only causes the extra traffic to be dropped in the direction of the
automatic switch. The other direction of the extra traffic is unaffected.

Note: In the direction opposite to the flow of the extra traffic, if the receive
STS-1 timeslots detect an STS-1 alarm indication signal (AIS) condition,
their state goes to partial failure and they send an STS-1 yellow indication
to the far end (that is, to the path termination). If the path termination at the
far end is a DS3 at an OC-48 network element, the alarm is a DS3
“Drop-STS1 Rx yellow” alarm. If unidirectional extra traffic is used with
DS3 path terminations, it is recommended that the DS3 “Drop-STS1 Rx
yellow” alarm potentially raised by an STS-1 yellow condition be disabled
at the far-end protection shelf.

Low-priority and high-priority extra traffic

Extra traffic has the lowest priority in the protection-switching hierarchy.
Consequently, extra traffic, with no working channel lockouts, is useful for
situations in which the traffic being carried on the working channels is deemed
to be of a higher priority than the extra traffic. In this case, the working channel
traffic is not lost under failure conditions that are automatically protected by
the system. Rather, the working channel traffic preempts the extra traffic on the
protection channel.

If the extra traffic is more important than some or all of the traffic being carried
by working channels, the working channels that are deemed less important
than the extra traffic should be locked out. This ensures that failures on those
working channels do not cause extra traffic to be dropped.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
10-4 Extra traffic

Extra traffic operation

Automatic switch
In the event of an automatic switch, extra traffic is dropped and an alarm is
generated to indicate that extra traffic has been lost. If the system is in the
unidirectional protection-switching mode and extra traffic is enabled, an
automatic switch request only causes the extra traffic to be dropped in the
direction of the automatic switch. The other direction of the extra traffic is
unaffected.
Lockout
If the protection channel is locked out, no traffic can be carried on it, and any
active extra traffic is dropped. If a lockout of the protection channel is
performed in one direction while extra traffic is provisioned for unidirectional
operation, extra traffic can be carried in the other direction.
Forced switch
Extra traffic cannot be carried when a working channel is forced on to the
protection channel. Consequently, if extra traffic is enabled and a forced switch
is requested, the forced switch completes and the extra traffic is dropped,
accompanied by the appropriate alarms.

If extra traffic is enabled and a forced switch is active, the forced switch is
unaffected and the extra traffic is not carried. The appropriate alarm is
generated, indicating that the extra traffic is lost.

If the system has been provisioned to be unidirectional, both a forced switch

and extra traffic can be active at the same time, as long as the direction of the
switch and extra traffic are different.
Manual switch
Extra traffic cannot be carried when a working channel is switched to the
protection channel. If a user attempts a manual switch while extra traffic is
active, the extra traffic is dropped and the appropriate alarm is generated.

If the system is operating in unidirectional mode and extra traffic is enabled in

only one direction, a manual switch of a working channel in the other direction
is permitted.
Exerciser tests and extra traffic
A protection exerciser request does not effect extra traffic, as the OC-48
portion of the exerciser routine does not run on any shelf in the 1:N system if
extra traffic is enabled. However, the exerciser does run for the tributaries on
all shelves (working and protection). The user has the option of squelching the
extra traffic for the duration of a manual exerciser run (upon completion of
which the extra traffic is automatically reestablished). For more information on
the interaction between the exerciser and extra traffic, see Chapter 11, “The
exerciser and 1:N extra traffic” on page 11-10.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Extra traffic 10-5

Wait to restore
The extra traffic is lost in the event of a protection switch until the
wait-to-restore period expires. In the case of power outages to more than one
network element in the system, the extra traffic is not recovered until the
wait-to-restore period has expired for all working channels.
Path trace
The path-trace feature can be provisioned for extra traffic STS channels on the
protection channel.
Circuit pack LEDs on the protection loop
The active LEDs light on the entire protection loop when any traffic is being
carried on it, including extra traffic, regardless of direction. Hence,
unidirectional extra traffic causes all green Active LEDs of the OC-48 circuit
pack groups (G1 and G2) on the protection shelf circuit packs and the OC-48
G2 circuit packs on all the working shelves to light.

The LEDs of the entire protection loop light when unidirectional traffic is
active because the K-bytes signaling the unidirectional switch are being
carried around the protection loop. Although in the case of unidirectional extra
traffic, actual traffic is not carried around the protection loop, the extra traffic
would be lost if a circuit pack were to be removed, thereby interrupting the
K-byte information.
Extra traffic alarm inhibition
When extra traffic is disabled at either one of the protection shelves, DS3,
STS-1, OC-3, STS-12, and OC-12 tributary alarms are automatically disabled
at that protection shelf.

DS3, STS-1, OC-3, STS-12, and OC-12 tributary facilities, as displayed on

facility screens on the network element user interface, show their actual state
(IS-TRBL), even though the corresponding alarm has been inhibited.

Extra traffic on GR-1230 Rings

Extra traffic can be carried on the protection timeslots (25 to 48) on both fibers
of the GR-1230 Ring. Extra traffic requires tributary equipment to be available
at the ADM nodes at which the traffic is added to the ring and dropped from
the ring.

Note: The Packet Edge System tributary can be used to carry extra traffic
only for unprotected point-to-point connections or shared ring
connections. There cannot be any extra traffic carried on a GR-1230 Ring
when the Packet Edge connections are provisioned as protected
point-to-point connections.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
10-6 Extra traffic

The extra traffic connections are provisioned using the OPC Connection
Manager tool. A protection switch on the OC-48 optics anywhere in the ring,
whether automatic or user-initiated, causes all extra traffic on the ring to be lost
if there is no lockout of protection active anywhere in the ring.

An automatic switch request is a system-initiated action and is performed

whenever the system detects a signal degrade or failure of the OC-48 optics or
the failure of a node in the ring. User-initiated protection switches include
manual and forced switches.

A completed protection switch immediately results in a loss of extra traffic and

the appropriate alarms are raised. When extra traffic is lost, traffic to those
tributaries carrying extra traffic is squelched and the appropriate alarm
indication signal (AIS) is inserted.

Note: If a ring switch occurs where the STS path performance monitoring
is enabled, a channel-based alarm is raised on a working channel, and the
corresponding STS protection channel is carrying extra traffic and does not
have a channel-based alarm, then the protection channel drops the extra
traffic and the channel-based alarm from the working channel is raised
against the STS protection channel. Because STS path performance
monitoring does not recognize extra traffic, after the ring switch is released
and extra traffic is restored, the channel-based alarm still shows for the
protection channel during the alarm detector hold-off period (10 +/- 0.5
seconds).

Before the extra traffic is restored after the cause of an OC-48 automatic switch
has been corrected, the currently provisioned wait-to-restore period must
expire. The default wait-to-restore period is 5 minutes. In the case of power
outages to more than one network element in the ring, the extra traffic is not
recovered until the wait-to-restore period has expired for all working traffic.

When a manual or forced switch is dropped, no wait-to-restore period is

applied before restoring extra traffic. If the wait-to-restore period is set to
infinity, if the extra traffic is lost for any reason, it remains lost until manually
recovered. For example, you can operate and release a manual switch to
recover the extra traffic or temporarily reprovision the wait to restore to a short
period, such as 1 minute.

When a ring with extra traffic completes the protection switch, its behavior is
the same as a ring that did not have extra traffic before the switch setup.

Do not provision extra traffic over matched-node gateways except as a

drop-and-continue on protection (DCP) secondary segment. Otherwise, the
traffic is lost if there is an OC-48 protection switch, including the traffic on
both the primary and secondary feeds on the gateways.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Extra traffic 10-7

Matched-node gateways can be provisioned as unidirectional STS

connections. This means that only one ring requires matched-node
provisioning. The other ring views itself as a standalone ring whose STS feeds
into the other ring are drop-and-continue connections.

Matched-node gateways can also be provisioned as drop points for

unidirectional drop-and-continue STS connections. However, in this case, if a
drop point is deleted there is no protection switch. Traffic is therefore lost.

The protection exerciser can be run while extra traffic is active, as there is no
bridging required.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
10-8 Extra traffic

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 11-1

Protection exerciser 11-

This chapter describes the protection exerciser. The exerciser tests the
protection paths of the network element shelf at the tributary and the transport
levels, including the DS3, STS-1, OC-3, OC-12, and OC-48 exerciser tests.
The OC-12 tests include tests of STS-12 tributaries, and the OC-48 tests
include tests of STS-48 equipment.

Note: The protection exerciser does not test protection paths for STM-1J
tributaries and does not run for OPTera Packet Edge System (formerly
iPT1000) tributaries.

To fully exercise the protection paths, both ends of a SONET line must be
exercised (that is, at both terminals of a linear system or at each pair of
neighboring ADM nodes in a ring). However, do not run the exerciser at both
ends at the same time (as described in the following detailed descriptions for
each system configuration).

These tests can be run manually or automatically from the network element
user interface, the OPC 1:N Protection Manager tool (for multishelf 1:N
systems), and the OPC Protection Manager tool (for 1+1 and 1:1 linear
systems and GR-1230 Rings). The exerciser can also be run using commands
issued through the Transaction Language 1 (TL1) and telemetry, byte-oriented
serial protocol (TBOS) interfaces. For instructions, refer to the following
documents:
• Protection Switching Procedures, 323-1201-311, for instructions on how
to run the exerciser using the network element user interface and on how
to run the exerciser and schedule it through the OPC 1:N Protection
Manager and Protection Manager tools
• System Administration Procedures, 323-1201-302, for instructions on how
to schedule the exerciser using the network element user interface
• TL1 Interface Description, 323-1201-190, for instructions on how to
schedule the exerciser using the TL1 interface
• Alarms and Surveillance Description, 323-1201-104, for information on
how to use the TBOS interface

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
11-2 Protection exerciser

When the exerciser run is completed on a network element, an EQP603 log is

generated on that network element, indicating the results. If no failures are
found for each portion of the routine, the log indicates a pass for that portion
of the routine.

If a failure is detected on a DS3, STS-1, OC-3, OC-12, or OC-48 protection

path, the following occurs:
• The red TESTFAIL LED on the maintenance interface lights.
• The EQP603 on the network element user interface indicates that a failure
was detected on a particular path or an EQP604 log is raised if the routine
could not run at all.
• A protection path fail minor alarm is raised.
The exerciser does not test a protection path under certain conditions. These
conditions include equipment that is locked out, out of service, deleted,
unequipped, or subject to an active protection switch, including extra traffic
applications. Also, the traffic for even-numbered circuit pack groups for OC-3,
STS-12, and OC-12 tributaries is not exercised. The exerciser does not run on
any quadrant equipped with these tributaries unless the traffic is on the
odd-numbered channel. The exerciser does not run on quadrants equipped with
two double-width OC-3 interfaces that are provisioned as unprotected
tributaries.

With the exception of 1+1 systems, the exerciser does not run at all if an OC-48
transport protection switch is active. In a 1+1 configuration (with the switch
mode either unidirectional or bidirectional), the protection exerciser runs the
DS3 and STS-1 bridge A test even if the traffic is on OC48 G2. The OC-48 test
and the DS3 and STS-1 bridge B test do not run if the traffic is on OC48 G2.

If a tributary protection switch is active, only the portion of the exerciser

routine related to that tributary type does not run. Similarly, if an OC-48
protection switch occurs at any point during the exerciser routine, the entire
exerciser run is aborted. If there is a tributary protection switch during an
exerciser run, only the portion of the routine related to that tributary type is
aborted. Provisioning changes on the shelf while the exerciser is running (for
example, adding new equipment) can cause the exerciser to abort.

Although the exerciser does run for DS3 and STS-1 tributary facilities that are
provisioned to be out of service, it does not run for OC-3, STS-12, or OC-12
tributary facilities that are out of service.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Protection exerciser 11-3

DS3 and STS-1 exerciser tests

The DS3 and STS-1 exerciser tests verify the operation of the DS3 and STS-1
protection paths. A DS3 or STS-1 protection path consists of all the equipment
required to bridge traffic from a working DS3 or STS-1 channel to the
protection DS3 or STS-1 channel. The equipment involved in a single DS3 or
STS-1 bridge test includes the following:
• the DS3 mapper or STS-1 interface circuit pack serving the working
channel
• the protection DS3 mapper or STS-1 interface circuit pack
• the switch controller
• both switcher circuit packs
• the interface carrier circuit pack serving the working channel
• the interface circuit pack serving the working channel (testing one
interface port circuit pack proves the protection path for all three interface
port circuit packs in the DS3 or STS-1 circuit pack group served by the
working DS3 mapper or by the working STS-1 interface)
Note: The DS3 exerciser tests are performed before the STS-1 exerciser
tests.

To test the DS3 or STS-1 protection paths, the exerciser performs the following
bridging tests sequentially on each working DS3 mapper or STS-1 interface
circuit pack to ensure that:
• the DS3 receive traffic (DS3 incoming to the network element) can be
bridged to the protection DS3 mapper circuit pack (bridge DS3 receive
traffic test)—see Figure 11-1
• the OC-48 receive traffic (OC-48 incoming to the network element) from
the G1 (working) circuit pack group can be selected and routed to the DS3
protection circuit pack (bridge G1 test)—see Figure 11-1
• the OC-48 receive traffic (OC-48 incoming to the network element) from
the G2 (protection) circuit pack group can be selected and routed to the
DS3 protection circuit pack (bridge G2 test)—see Figure 11-2
• the STS-1 receive traffic (STS-1 incoming to the network element) can be
bridged to the protection STS-1 interface circuit pack (bridge STS-1
receive traffic test)—see Figure 11-1

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
11-4 Protection exerciser

• the OC-48 receive traffic (OC-48 incoming to the network element) from
the G1 (working) circuit pack group can be selected and routed to the
STS-1 protection circuit pack (bridge G1 test)—see Figure 11-1
• the OC-48 receive traffic (OC-48 incoming to the network element) from
the G2 (protection) circuit pack group can be selected and routed to the
STS-1 protection circuit pack (bridge G2 test)—see Figure 11-2
Note: Both the bridge G1 and G2 tests include a bridge DS3 or STS-1
receive traffic test.

The DS3 and STS-1 tests pass if the protection and working DS3 mapper or
STS-1 interface have the same set of receive and transmit alarms during the
tests. A complete switch on the DS3 mapper or STS-1 interface is not done
because to do so would be service affecting.

The EQP logs indicate a failure if the DS3 protection or STS-1 protection
mappers fail during the exerciser run. The EQP603 log indicates the failure.

If a DS3 or STS-1 protection switch occurs during the exerciser run, the
exerciser aborts the DS3 or STS-1 portion of the routine because the protection
DS3 mapper or STS-1 interface is carrying service and is no longer available
for bridging tests. The EQP604 log shows that the exerciser aborted due to
provisioning changes, an exerciser control point change, a protection switch,
entity set problems, or alarm point changes. However, if a DS3 or STS-1
protection switch is active before the exerciser runs, then the DS3 and STS-1
tests are not run at all. Again, the log indicates that the test was not run, with
an indication as to why, such as “Not Run (Protection Unavailable)”.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Protection exerciser 11-5

Figure 11-1
Bridge G1 test
F1822_R8

Working DS3 mapper OC-48 G1

Interface port or STS-1 interface circuit pack group

DS3 or
STS-1 receive

Protection
bus Switch Protection DS3 mapper OC-48 G2
Switcher controller or STS-1 interface circuit pack group

Working DS3 mapper OC-48 G1

Interface port or STS-1 interface circuit pack group

DS3 or
STS-1 transmit

Protection
bus Switch Protection DS3 mapper OC-48 G1
Switcher controller or STS-1 interface circuit pack group

FW-1822 (R8)

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
11-6 Protection exerciser

Figure 11-2
Bridge G2 test
F1823_R8

Working DS3 mapper OC-48 G1

Interface port or STS-1 interface circuit pack group

DS3 or
STS-1 receive

Protection
bus Switch Protection DS3 mapper OC-48 G2
Switcher controller or STS-1 interface circuit pack group

Working DS3 mapper OC-48 G1

Interface port or STS-1 interface circuit pack group

DS3 or
STS-1 transmit

Protection
bus Switch Protection DS3 mapper OC-48 G2
Switcher controller or STS-1 interface circuit pack group

FW-1823 (R8)

OC-3, STS-12, and OC-12 exerciser tests

The OC-3 and OC-12 part of the exerciser routine tests the different protection
mechanisms associated with OC-3, STS-12, and OC-12 tributaries as follows
(the OC-12 portion of the exerciser also exercises STS-12 tributaries):
• The exercising of the OC-3, STS-12, and OC-12 tributaries only includes
an OC-3 or OC-12 bridge test.
• The only action performed is the exercising of the switching activity but
without actually completing the switch.
• An OC-3 or OC-12 protection switch during an exerciser run does not
abort the entire protection exerciser run. The run completes, including
testing all other OC-3 or OC-12 protection groups in that shelf are tested.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Protection exerciser 11-7

• The exerciser is not run for OC-3, STS-12, or OC-12 tributaries if traffic is
on the protection channel. The traffic must be on the working channel.
• The exerciser does not run for double-width OC-3 interfaces if they are in
unprotected mode.
The exerciser simulates a switch to the point of completion, but without
actually completing the switch. The exerciser detects failures in the protection
path by establishing bridges between the working and standby circuit packs,
and by verifying the integrity of the signal to the point at which the final switch
is to be made.

The exerciser is the lowest priority user command and does not run if a
higher-priority feature or command is in effect. If a failure occurs while the
exerciser is running, the exerciser is aborted and an extra 10 ms is required in
addition to the usual protection-switching time.

OC-48 exerciser tests

The OC-48 transport portion of the exerciser tests the SONET K-byte
communications between the switching sections to do the following:
• ensure that the protection switching signaling is working by initiating an
exerciser bridge
• determine if there is an optical loopback on the protection optics in linear
systems (1+1, 1:1, and multishelf 1:N)
Note: The optical loopback test is not performed on add-drop multiplexer
(ADM) nodes in a ring.

Exerciser bridge test (1+1 and 1:1 systems)

In 1+1 and 1:1 single-shelf configurations, both the working (G1) and
protection (G2) circuit pack groups are permanently bridged. They therefore
both carry the same traffic, and unlike in the DS3 and STS-1 tests, no bridging
takes place. Instead, when the exerciser is run on a network element, an
exerciser switch priority request and the circuit pack group number (G1 or G2)
is sent to the far-end network element on the K1 byte.

When the far-end network element receives the exerciser switch priority
request, it sends the channel number received back to the near-end network
element using the K2 byte. The near-end network element then checks this
channel number to see if it is the same as the one it sent out originally. If they
match, the K-byte communication has been verified and the OC-48 portion of
the exerciser test passes. The OC-48 protection switch is not completed
because it would affect service.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
11-8 Protection exerciser

Optical loopback conditions are detected when the exerciser bridge test is
initiated. When the exerciser bridge request is sent on the K1 byte to the
far-end network element, the near-end network element checks to see if it
receives an exerciser bridge request at the same time. If it does, the exerciser
has found an optical loopback and the EQP logs reflect this (see Figure 11-3).

The exerciser detects any optical loopback on the protection path of any node
in the system (terminal or regenerator). If the exerciser is scheduled to run at
the same time at two adjacent terminals in the same system, the exerciser on
each end sends bridge requests simultaneously. This causes the exercisers at
both ends to conclude that there is an optical loopback when none exists. Tests
for adjacent terminals should therefore be scheduled at least 2 minutes apart.

Although in a 1+1 system the exerciser does not run for the OC-48 optics if the
traffic is on G2, the K2 byte is continuously monitored, thereby providing
validation of the protection-switching status. However, the K1 byte signaling
is not monitored when traffic is on G2. It is therefore recommended that traffic
normally be left to operate on G1, so that the exerciser can be run as regularly
scheduled.
Figure 11-3
Exerciser with optical loopback
F1824

Exerciser bridge request originated here

Exerciser bridge request received here

Exerciser bridge request

should be received here
Optical loopback

Receive Transmit
Protection path
Transmit Receive

Receive Transmit
Working path
Transmit Receive
Near end NE Far-end NE

Exerciser run sequence

The exerciser runs 1+1 and 1:1 Protection switch scheme tests in the order
shown in Figure 11-4.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Protection exerciser 11-9

Figure 11-4
1+1 and 1:1 exerciser run sequence
F3019_R12

Run Exerciser
(automatic or Manual)

Bridge G1 test for DS3 and

STS-1 tributaries, where
applicable
(see Notes 1 and 2)

OC-48 exerciser bridge test

(transport interface test)
(see Note 2)

Check for optical loopback

(transport interface test)

Bridge G2 test for DS3 and

STS-1 tributaries, where
applicable (see Notes 1 and 2)

Drop OC-48 exerciser bridge

Test STS-12 and OC-12

tributaries, where applicable

Test OC-3 tributaries,

where applicable

EQP log generated FW-3019

Note 1: The exerciser tests all DS3 mappers first, in the order of the circuit pack group
numbers (from G1 to G16). It then tests all STS-1 interfaces, also in the order of the
circuit pack group numbers.

Note 2: The OC-48 exerciser bridge stays up until bridge G2 tests are done. There are no
bridge G2 tests for OC-3, STS-12, or OC-12 tributaries.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
11-10 Protection exerciser

Exerciser bridge test (multishelf 1:N configurations)

The exerciser in OC-48 1:N multishelf configurations performs the same tests
as the exerciser in 1+1 and 1:1 single-shelf configurations. However, the
exerciser can be scheduled for all the network elements within a protection
group using the OPC 1:N Protection Manager tool. The OPC then
automatically manages the exerciser runs on the individual network elements
within the protection group.

The exerciser can also be run manually on each individual network element
using the network element user interface, although this exercises only one
channel at a time.

Ensure that the exerciser is not run on both ends of a channel at the same time,
either when running the exerciser manually or when scheduling it from the
OPC. This avoids situations where the system would declare optical loopbacks
during an exerciser run. When scheduling from the OPC 1:N Protection
Manager, allow at least 2 minutes per network element in the protection group
between the scheduled times for testing different protection groups. For
example, in a 1:11 system, allow 22 minutes between testing the two
protection groups.

In the 1:N configuration in idle operation (that is, with no active protection
switch), none of the optical channels is bridged to the protection channel (as
opposed to the 1+1 and 1:1 single-shelf configurations, which are permanently
bridged). When the exerciser is run from the OPC, although the same time is
scheduled for each network element within the same protection group, each
channel bridges one at a time to the protection channel.

The exerciser and 1:N extra traffic

In systems with extra traffic enabled, the exerciser operates for the tributaries,
but not the OC-48 transport optics. This includes both working and protection
shelves. The OC-48 transport protection path cannot be exercised because the
bridging required on the protection loop by the exerciser would cause the extra
traffic to be dropped.

It is advisable to periodically disable extra traffic and run the exerciser

manually to verify the OC-48 protection path. When a manual exerciser
request is made, the user has the option of squelching the extra traffic for the
duration of a manual exerciser run. On completion of the exerciser run, the
extra traffic is automatically reestablished. The “Loss of extra traffic” alarm is
raised when the traffic is squelched and it clears when the extra traffic is
reestablished. For 1:N system in which N is 11, the extra traffic is squelched
for approximately 5 minutes (assuming 16 DS3 tributaries per channel). (No
squelching is done during scheduled exerciser runs.)

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Protection exerciser 11-11

In the case of unidirectional extra traffic, the extra traffic is squelched in only
the direction of the exerciser request. The extra traffic in the other direction
experiences a burst of errors (a small traffic hit) at the moment of the exerciser
request.

Working shelves support DS3, STS-1, OC-3, STS-12, and OC-12 tributaries.
STS-1 tributaries are not supported for extra traffic, and therefore are not
present on protection shelves in 1:N systems.

If extra traffic is disabled, only the OC-48 optics are exercised on the
protection shelf to verify the K-byte signaling. For more information on extra
traffic, see Chapter 10, “Extra traffic”.

If an attempt is made to run the exerciser while extra traffic is enabled, an

EQP603 log is generated by the affected network element, indicating that the
OC-48 protection path was not exercised.

If the exerciser is running when extra traffic is enabled, the extra traffic request
remains pending until the exerciser completes the routine (on the shelf, if run
from the network element user interface or, if run from the OPC, on all shelves
within the protection group).

Exerciser run sequence

When the exerciser is run manually from the network element user interface
on a 1:N system, only the specified shelf is tested. In the case of a working
shelf on a system with no extra traffic, the exerciser run sequence is the same
as for 1+1 and 1:1 systems, as shown in Figure 11-4. For a protection shelf or
a 1:N system with extra traffic, the exerciser behavior is discussed in “The
exerciser and 1:N extra traffic” on page 11-10.

When the exerciser is run from the OPC user interface (using the 1:N
Protection Manager tool), all the network elements in the protection group are
exercised. In this case, the exerciser runs its tests in the order shown in
Figure 11-5 and as described below.

The OPC broadcasts an “exerciser run” command simultaneously to all the

network elements in the protection group. This command causes each of the
network elements to run the exerciser on its shelf. All of the network elements
in the protection group run the bridge G1 tests at the same time because the G1
tests do not involve bridging to the protection channel. However, the G2 tests
involve bridging the OC-48 channel on to the protection channel.

The sequence therefore follows that the first available working channel bridges
to the protection channel (for example, working channel 1). Because the
protection channel is then in use by the bridged channel for the remainder of
its exerciser run, the other network elements must wait their turn before
beginning their G2 bridging tests.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
11-12 Protection exerciser

Figure 11-5
The exerciser run sequence on a 1:N system (initiated from the OPC 1:N Protection Manager)
F3020_R12

Run Exerciser from OPC

(Automatic or Manual)

Run Exerciser Run Exerciser Run Exerciser

(automatic or Manual) (automatic or Manual) (automatic or Manual)

Bridge G1 test for DS3 and Bridge G1 test for DS3 and Bridge G1 test for DS3 and
STS-1 tributaries, where STS-1 tributaries, where STS-1 tributaries, where
applicable applicable applicable
(see Notes 1, 2, and 3) (see Notes 1, 2, and 3) (see Notes 1, 2, and 3)

OC-48 exerciser bridge test OC-48 exerciser bridge test OC-48 exerciser bridge test
(transport interface test) (transport interface test) (transport interface test)
(see Note 2) (see Note 2) (see Note 2)

Check for optical loopback Check for optical loopback Check for optical loopback
(transport interface test) (transport interface test) (transport interface test)

Bridge G2 test for DS3 and Bridge G2 test for DS3 and Bridge G2 test for DS3 and
STS-1 tributaries, where STS-1 tributaries, where STS-1 tributaries, where
applicable (see Notes 1 and 2) applicable (see Notes 1 and 2) applicable (see Notes 1 and 2)

Drop OC-48 exerciser bridge Drop OC-48 exerciser bridge Drop OC-48 exerciser bridge

Test STS-12 and OC-12 Test STS-12 and OC-12 Test STS-12 and OC-12
tributaries, where applicable tributaries, where applicable tributaries, where applicable

Test OC-3 tributaries, Test OC-3 tributaries, Test OC-3 tributaries,

where applicable where applicable where applicable

EQP log generated EQP log generated EQP log generated

Note 1: The exerciser tests all DS3 mappers first, in the order of the circuit pack group numbers (from G1 to G16).
It then tests all STS-1 interfaces, also in the order of the circuit pack group numbers.
FW-3020 (R12)
Note 2: The OC-48 exerciser bridge stays up until bridge G2 tests are done. There are no bridge G2 tests for
OC-3, STS-12, or OC-12 tributaries.

Note 3: The DS3 and STS-1 bridge G1 tests are done at the same time on all working channels. The remaining
tests are done on the working channels are tested in the order in which they complete the DS3 and STS-1 bridge
G1 tests. This is not necessarily in numerical order by working channel number.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Protection exerciser 11-13

The sequence then continues through the protection group according to which
the working channels complete their bridge G1 tests. This means the working
channels do not necessarily proceed through the remainder of the tests in
numerical order. For example, if working channel 4 finishes the bridge G1 test
first, it is the first to use the protection channel and complete its tests. Because
particular network elements might not be available at a specific moment in
time, the order in which the channels bridge to protection might vary from one
exerciser run to another.

When all the network elements have been tested, the exerciser run is complete.
There are separate EQP logs generated for each network element that is
exercised when the exerciser is run from the OPC.

To determine whether the exerciser was successful, check the EQP logs and
alarms generated by all the network elements in the protection group. If all
parts of the exerciser routine were successful, this is indicated in the EQP603
log for each network element and there are no alarms. If there are alarms
(notably “Protection path fail” alarms), check the EQP logs for the network
element with the failure for additional information related to the failure.

If the exerciser is scheduled to run automatically for the OPC user interface,
the OPC broadcasts the scheduled time to all the network elements in the
protection group. The network elements then automatically run the exerciser
at the scheduled time. However, the scheduled time on the OPC is in
Greenwich Mean Time (GMT), and not the local time of the network elements
in the protection group.

For example, if the exerciser is scheduled on the OPC to run automatically at

2:00 am and the protection group network elements have a GMT offset of
–300 minutes, the exerciser runs on the network elements at 9:00 pm local
time, not 2:00 am local time. If the protection groups in the system are in
different time zones, the different GMT offsets of the network elements must
be taken into account when scheduling the exerciser on the OPC.

Note: Daylight saving time adjustments are made automatically according

to time zones.

Exerciser bridge test (GR-1230 Ring configurations)

The exerciser in a OC-48 GR-1230 Ring configuration performs the same tests
as the exerciser in 1+1 and 1:1 single-shelf configurations. However, the
exerciser can be scheduled for all the ring ADM nodes using the OPC
Protection Manager tool, which includes the exerciser scheduler.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
11-14 Protection exerciser

As described for 1+1 and 1:1 configurations, exerciser tests for each ADM
node in the ring should be scheduled so that they do not coincide with each
other, to avoid the possibility of the system declaring optical loopbacks. At
least 2 minutes should be scheduled between testing the different ADM nodes
in the ring.

When invoked using the OPC Protection Manager tool, the exerciser runs its
tests in the order the network elements appear in the Protection Manager tool
according to the order of the user-specified time intervals. To specify when the
scheduled exerciser is run and in which order, use the Protection Manager
tool’s scheduler. The Protection Manager tool also allows the user to specify
whether to exercise all ADM nodes in the ring or just individual ADMs.

The network element user interface can be used to run the exerciser on
individual ADM nodes. When testing individual ADM nodes or when
scheduling exerciser runs for more than one ADM node, stagger the exerciser
runs to avoid collisions during tests of the OC-48 optics.

Of the OC-48 optical tests, only the software protocol is exercised. The bridge
is not exercised and the optical loopback test is not performed. The exerciser
can therefore be run even if extra traffic is provisioned on the protection STS
paths. The exerciser request does not affect extra traffic because it exercises the
protection channel signaling but does not actually complete the bridge or
switch to the protection channels.

The exerciser tests the two optical interfaces (circuit pack groups G1 and G2)
at the network element in turn (G1 first, then G2) using the K-bytes. The
OC-48 ring transmit interface of G1 at the originating ADM node sends an
exerciser request over the optical link using the K1 byte to its neighboring node
(destination ADM node). The K1 byte includes the automatic
protection-switch identifier (APS ID) of the destination node.

When the destination node receives the exerciser request, it responds with a
K2-byte that reports its switching status as idle (that is, no bridge active), as
well as including the APS ID of the originating node for routing purposes. This
test is repeated for G2 and the second neighboring node.

When testing of all the nodes in the ring is complete, each protection path has
been tested from both ends of each link between nodes.

In inter-ring connections using matched nodes, no exerciser test is required

because the secondary feed for a protected STS path is permanently bridged at
the broadcast point.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Protection exerciser 11-15

Exerciser alarms and logs

Alarms that can be raised by the exerciser are listed in Table 11-1.
Table 11-1
Alarms that can be raised by the exerciser

Alarm text Description

DS3 or STS-1 protection path fail The exerciser has failed to establish a bridge
between the working and standby DS3 mapper
or STS-1 interface circuit packs because of a
problem in the protection path.

OC-48 protection path fail The K-byte communication has failed during the
OC-48 exerciser switch request test.

OC-12 protection path fail The K-byte communication has failed during the
OC-12 exerciser switch request test.

OC-3 protection path fail The K-byte communication has failed during the
OC-3 exerciser switch request test.

Mapper parity error on port 1/2/3 The K-byte communication has failed during the
from G2 optics exerciser switch request test (DS3 tributaries).

Bp parity error on port 1/2/3 from The K-byte communication has failed during the
G2 optics exerciser switch request test (STS-1 tributaries).

Exerciser fail The exerciser did not begin or did not complete
one of its tests.

If a “Protection path fail” alarm becomes active after the exerciser is run, the
alarm remains active until the failed circuit pack or packs are removed and the
exerciser is run a second time. To clear a “Protection path fail” alarm, refer to
Alarm Clearing Procedures, 323-1201-543.

A special case of the DS3 or STS-1 “Protection path fail” alarm occurs when
over 75% of the DS3 or STS-1 protection paths tested by the exerciser fail.
When this happens, the DS3 protection mapper circuit pack or STS-1
protection interface raises a “Protection path fail” alarm.

Backplane parity errors are more difficult to diagnose because they involve
data links between circuit packs. If the receiving circuit pack detects a fault,
then the link is presumed failed. It cannot be determined if the sending circuit
pack, receiving circuit pack, or backplane is causing the failure. Backplane
parity-error alarms are internal integrity checks between circuit packs on the
shelf, as shown in Figure 11-6.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
11-16 Protection exerciser

Figure 11-6
Backplane parity error alarm
F1821

Internal data between circuit packs

Circuit pack 1 Circuit pack 2

data send data receive
(Backplane) parity check
on Rx data

Data link data corrupted

Parity error alarm

The backplane parity error alarms behave the same as the “Protection path fail”
alarms. If a backplane parity error alarm becomes active after the exerciser run,
the alarm remains active until the failed circuit pack or packs are removed.

The exerciser logs are listed in Table 11-2. Refer to Log Report Manual,
323-1201-840, for a detailed description of the logs.
Table 11-2
Exerciser logs

Log Log Text Description

Buffer Number

EQP 603 Exerciser This log is generated whenever the

operation results exerciser completes at least one of the
tests. It displays the test results: pass,
fail, optical loopback, fail and optical
loopback, or not run. If the result of one of
the tests is “not run”, the reason why it
was unable to run may be included as
well.
You can also use the XRESULTS CI tool
to see a detailed report of the results of
the protection exerciser run. In addition to
the information available through the
exerciser logs, the report identifies which
tributaries have failed.

EQP 604 Exerciser The exerciser did not run any of its tests.
operation aborted

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Protection exerciser 11-17

Exerciser limitations
Because the exerciser tests cannot affect service on the system, protection
switches are never completed. This means that there are parts of the protection
path that cannot be tested.

The exerciser should not be scheduled to run at the same time (automatically
or manually) on the network elements at both ends of an optical link (that is,
the terminals in a linear system, the ADM nodes in a ring, or between an
OC-48 terminal or ADM node and the OC-3, STS-12, or OC-12 equipment to
which it is connected by way of an OC-3, STS-12, or OC-12 tributary). Allow
at least 2 minutes between the testing of each terminal and ADM.

Note: Any switch activity on the protection channel inhibits the OC-48
portion of the exerciser.

OC-48 backplane parity error faults are not detected by the exerciser because
most of the paths are constantly monitored. The paths that are not monitored
cannot be tested by the exerciser because the tests would affect service.

In a ring configuration, if the exerciser runs while there is an active lockout of

protection, the exerciser fails and raises a “Protection path fail” alarm on the
far-end network element of the span. The exerciser is not run on other ADM
nodes due to the active lockout of protection. To clear the alarm, release the
lockout and run the exerciser again.

In a 1:1 configuration, with an active remote OC-48 lockout (that is, the OC-48
lockout has been raised from the far end), the exerciser generates an OC-48 G1
“Protection path fail” alarm. An OC-48 “Protection path fail” alarm is raised
whenever the exerciser is run with a remote lockout. In this case, remove the
remote lockout and run the exerciser again to clear the alarm. To avoid the
alarm, do not run the exerciser while a remote lockout is active.

In a 1+1 configuration, when traffic is switched from OC-48 G1 to G2, because

of the non-revertive nature of the protection scheme, the traffic remains on
OC-48 G2 after the switch request is removed. The network element uses an
infinite wait-to-restore period to maintain the traffic on G2. Because wait to
restore has a higher protection-switching priority than the exerciser, any
exerciser request for the OC-48 optics is aborted until traffic is switched back
to G1. However, the protection-switching K2 (status) byte continues to be
monitored because of the wait-to-restore request. This monitoring provides
some protection validation, although the K1 (signaling) byte is not monitored.
It is therefore recommended that traffic normally be left to operate on G1, so
that the exerciser can be run as regularly scheduled.

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
11-18 Protection exerciser

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 12-1

Path trace and section trace 12-

This chapter describes the path-trace and section trace features of the OC-48
network element.

Path trace
The path-trace feature serves as an independent backup for the standard
failure-detection features of the OC-48 by detecting faults in the STS-1 paths.
It is based on the SONET TA-NWT-000253 standard. Path trace can also
validate signals in mixed-vendor networks if the equipment supports
SONET-compliant path trace.

The path-trace feature determines whether proper connectivity exists at the

STS-1 level through the use of a user-provisionable signature on each STS-1
signal passing through the network. It can indicate path-trace signature
mismatches resulting from such causes as the following:
• failures affecting backplane connectivity for STS-1 connections
• connection mapping errors
• if the STS-1 signal quality falls below a bit error rate of 10−6, but the
signal-degrade threshold is set to 10−5 or 10−4
• hardware failures that would normally not be detected
• a stuck bit in a transport or tributary circuit pack
• accidental OC-48 fiber loopbacks
The path-trace mechanism verifies the integrity of the path overhead (POH)
embedded in the synchronous payload envelope (SPE) of the STS-1 signal. It
uses a 64-character signature of fixed length that is provisioned at both
asynchronous terminations (DS3 level in OC-48 network elements) for each
STS-1 channel. Currently, only STS-1 channels are supported, and not
concatenated STS channels (for example, STS-3c and STS-12c).

At each path termination, a transmit and an expected receive signature are

provisioned when the STS-1 channel is created, thereby providing a unique
signature for both directions of the STS-1 channel. Preprovisioning of

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
12-2 Path trace and section trace

path-trace values is not supported (that is, the equipment and facilities serving
the terminations must be in service before the STS connection and path-trace
values can be provisioned).

When the STS-1 channel is active, the appropriate path-trace signature is

repeatedly transmitted from each end of the STS-1 connection. The
path-terminating hardware continuously monitors the actual signature it
receives against the expected signature for any mismatch.

If a mismatch in the expected and actually received signatures is detected, the

system holds off taking any action for 4 seconds. This hold-off period allows
the standard diagnostic routines to be completed and to take corresponding
action if a fault is found. For example, a condition affecting the path-trace
signature might also cause other alarms to be generated. In such a case, these
other alarms would mask the path-trace failure.

If, after the hold-off period, the condition still exists and no other alarm has
been raised, a path-trace alarm is raised against the DS3 facility terminating
the affected path. Protection switching is not initiated as the result of a
path-trace failure.

When the path-trace alarm is active, follow the appropriate alarm-clearing

procedure according to Alarm Clearing Procedures, 323-1201-543.

The hold-off period also ensures that the path-trace alarm is not raised as the
result of transient conditions. Any potential path-trace failures on the
protection paths remain undetected until the paths are made active (that is,
because of a protection switch or having extra traffic enabled).

If the path-trace signature is not provisioned for an STS-1 connection, a default

signature of null characters is used. If the expected receive signature consists
of the default null characters, the receiving network element does not raise an
alarm in the case of mismatches in the path-trace values.

The path-trace feature is also useful when provisioning new connections to

verify that the connection is originating at the correct source and terminating
at the correct destination. If a path-trace alarm is displayed against the
connection, the connection is not provisioned correctly or is experiencing a
problem.

Once provisioned, the path-trace signatures are downloaded to the network

element, where they are stored in the network element database. The path-trace
signatures are not stored in the OPC database.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
 Path trace and section trace 12-3

To assist with troubleshooting, the path-trace feature allows the user to use the
OPC to retrieve the transmit, expected receive, and actual receive signatures
for each path termination. (If the path terminations are in different OPC spans
of control, path-trace provisioning and retrieval operations are performed in
the OPC for each respective span of control.)

In addition, there is a command interpreter (CI) tool on the network element,

called the PTSAMPLER, that allows the user to retrieve the transmit, expected
receive, and actual receive signatures at the path-terminating equipment. The
CI tool can also access the actual receive path-trace signature at any
intermediate nodes for the connection in GR-1230 Rings (that is, nodes
equipped with the OC-48 ring demultiplexer).

A path-trace audit is run automatically following the scheduled connection

audit. The results of this audit are displayed as logs using the OPC Event
Browser tool.

If a connection terminates on a network element that does not support path

trace (for example, an OC-48 network element using Release 9 software or
earlier), path trace must be disabled on that network element.

Section trace
Section trace allows the OC-48 network element to validate bidirectional STS
signals on facilities using half-height OC-3 or STM-1J interfaces (NT8E08).
Section trace can also validate STS signals between these OC-3 or STM-1J
interfaces and those from other vendors that support SONET-compliant
section trace.

By default, section trace is off. If the far-end equipment does not support
section trace, make sure section trace is provisioned off at the near end.
Otherwise, a “Section trace mismatch” alarm becomes active.
Operation of section trace
The transmitting half-height OC-3 or STM-1J interface (NT8E08) inserts a
message in the J0 byte of the section overhead of the SONET signal. The user
sets the value of the message either as a number from 0 to 255 or a 15-character
ASCII string.

The receiving OC-3 or STM-1J interface compares the value it receives to the
value it expects to receive. If the value received does not match the expected
value, the system raises a “Section trace mismatch” alarm. For instructions on
how to clear this alarm, see Alarm Clearing Procedures, 323-1201-543.

The difference in expected and actual values can result from one of the
following causes:
• an incorrectly provisioned section trace value at either the near end or the
far end of the OC-3 or STM-1J facility

Signal Flow and Protection Switching Descriptions 323-1201-103 Rel 16.1 Standard Feb 2001
12-4 Path trace and section trace

• crossed fibers or other incorrectly connected cables at any point along the
STS path
• a defective transmitter upstream from the OC-3 or STM-1J interface
receiving the signal
• the OC-3 or STM-1J interface receiving the signal is defective
• a signal-degrade condition that does not activate a “Signal degrade” alarm.
For example, signal quality falls below 10-6, which can corrupt the section
overhead, but the signal-degrade threshold is to set 10-4 or 10-5.
Any changes made to the section trace values will generate an FAC404 log.

S/DMS TransportNode OC-48 NE Vol 1 323-1201-103 Rel 16.1 Standard Feb 2001
SONET Transmission Products

S/DMS TransportNode
OC-48 NE
Signal Flow and Protection Switching
Descriptions
Copyright  1990–2001 Nortel Networks, All Rights Reserved

The information contained herein is the property of Nortel

Networks and is strictly confidential. Except as expressly
authorized in writing by Nortel Networks, the holder shall keep all
information contained herein confidential, shall disclose the
information only to its employees with a need to know, and shall
protect the information, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it uses
to protect its own confidential information, but with no less than
reasonable care. Except as expressly authorized in writing by
Nortel Networks, the holder is granted no rights to use the
information contained herein.

Nortel Networks, the Nortel Networks logo, the Globemark, How

the World Shares Ideas, Unified Networks, OPTera, and S/DMS
TransportNode are trademarks of Nortel Networks.

UNIX is a trademark of X/Open Company Limited.

323-1201-103
Standard Rel 16.1
February 2001
Printed in Canada