Ciena Networking Protocol Research
Ciena Networking Protocol Research
Scope: The report will focus on OSRP and OSPF routing protocols, specific Ciena
hardware such as PKCT/OTN cards, XCIF, XC, and OCLD, the term RNATs in Ciena
networking, and Ciena software facility types (PTP, ETTP, ODVCTP, TCMCTP) along
with their monitor types. The context is Ciena-based optical transport and
packet-optical networking.
The NMS can then utilize this information to construct a comprehensive topology
database. Based on this database, the NMS can launch Network Element (NE)
mediators, which are software components responsible for interacting with individual
NEs. These mediators can listen for updates and topology changes communicated via
OSRP, allowing the NMS to maintain an up-to-date view of the network.3 Furthermore,
systems using OSRP topology data can be designed to detect anomalies such as
duplicate addresses within the network. Upon detecting such a condition, the NMS
can assert a severe alarm, highlighting a practical aspect of OSRP network
configuration and troubleshooting.3 This capability underscores the importance of
OSRP in not only discovering topology but also in contributing to network integrity and
operational fault management.
In addition to in-band communication, the OSRP L0 control plane can also utilize
Out-Of-Band (OOB) communication.4 This OOB option provides an alternative
management path, which can be beneficial for network resilience or specific
architectural requirements. Configuring OSRP links for OOB communication involves
specifying a remote node identifier (ID). A critical operational detail is that this OOB
Remote Node ID requires translation if the 4-digit hexadecimal Node Identifier of the
far-end OSRP node contains any hexadecimal values from 'A' through 'F'. If all digits
are 9 or less, the OOB Remote Node ID is the same as the Node Identifier (in decimal).
Otherwise, a specific formula is used: the first two hex digits are converted to decimal
as the Most Significant Byte (MSB), and the second two hex digits are converted to
decimal as the Least Significant Byte (LSB). The OOB Remote node ID is then
computed as:
Integer(MSB/16)×1000+Remainder(MSB/16)×100+Integer(LSB/16)×10+Remainder(LSB
/16).4 For example, a Node Identifier of AAFF (hex) translates to MSB=170 and
LSB=255, resulting in an OOB Remote Node ID of 1010255 4 -> 10(A)10(A)15(F)15(F) ->
10101515. This specific translation method must be precisely followed for successful
OOB OSRP link establishment.
Ciena community discussions also indicate that from release 12.85 of certain software,
an option for an Out-Of-Band Channel (OOBC) was available to carry OSRP-related
messages, though it was noted that OSC is generally required to manage and operate
a Photonic L0 OSRP network.5
The OCLD provides the physical or logical link over which OSRP operates. OSRP L0
control plane configuration is explicitly mentioned in the context of Ciena OME6500
systems 4, a platform where OCLD modules are commonly deployed as part of the
photonic layer infrastructure. The continued relevance of OSRP in Ciena's advanced
networking solutions is further suggested by its association with modern platforms
like the WaveRouter and management suites such as Navigator Network Control Suite
(NCS) 7, indicating its role in coherent routing solutions.
The increasing complexity of optical networks, with specialized protocols like OSRP,
underscores the critical role of the Network Management System (NMS). Patent
information regarding NMS interaction with OSRP 3 highlights the need for robust
management tools to prevent misconfigurations and provide clear operational
visibility. The focus in such patents on detecting issues like duplicate addresses and
managing comprehensive topology databases for OSRP (and OSI/ISIS) environments
indicates a proactive approach to addressing potential operational challenges in
these sophisticated optical control planes. As control plane protocols become more
advanced, there is a corresponding need for equally sophisticated management
systems to ensure their correct and efficient operation, prevent errors, and simplify
troubleshooting.
To calculate routes, all routers run the exact same algorithm in parallel, typically
Dijkstra's algorithm.10 From the topological database, each router constructs a tree of
shortest paths with itself as the root, which provides the route to each destination in
the AS.9 OSPF gathers link-state information from all participating routers to create
this comprehensive topology map of the network, which then determines the entries
in the routing table.10
These features make OSPF a robust and versatile IGP suitable for a wide range of IP
network designs, including those that are layered over optical transport networks,
where Ciena equipment often provides both the IP/MPLS routing capabilities and the
underlying optical transport.
OSRP's routing function includes mechanisms for neighbor discovery and link status
exchange, which are conceptually similar to those found in OSPF networks.3 However,
the resources being managed and the objectives are different. OSRP is tailored for the
optical layer's specific needs, such as the fast-switched provisioning of entire or
fractional wavelengths.2 OSPF, on the other hand, uses Dijkstra's algorithm to
calculate the shortest path for IP packets based on link costs and converges quickly
to network topology changes.10
OSPF is generally considered more complex to configure and administer than simpler
protocols like RIP, but its features make it well-suited for large, hierarchical enterprise
and service provider IP networks.10 OSRP's complexity is specific to managing the
optical transport layer and its dynamic wavelength services.
Typical Use Case (Ciena) Control plane for photonic IP routing in Ciena platforms
networks (e.g., 6500 L0 supporting IP/MPLS (e.g.,
control plane), wavelength converged packet-optical
switching platforms)
Topology Discovery Exchanges "Hello" packets Exchanges Link State
and Topology State Elements Advertisements (LSAs) to
(TSEs) build a link-state database
Interaction with Network Provides topology to NMS for Provides IP topology to NMS
Management optical path visualization and for IP network monitoring and
management 3 management; interacts with
OSI/ISIS 3
This comparison clarifies that OSRP and OSPF are not mutually exclusive but rather
operate in different domains to provide comprehensive control and routing across
multiple network layers.
A central concept in OTN is that of the 'digital wrapper'. OTN encapsulates each client
service (such as Ethernet, IP, SONET/SDH, Fibre Channel, or digital video)
transparently into a digital container structure for transport across optical networks.
This encapsulation preserves the client's native structure, crucial timing information,
and any associated management information.15 This 'wrapping' process allows diverse
client signals to be carried uniformly over the optical transport infrastructure,
simplifying network operations and management irrespective of the specific client
signal type. This capability is fundamental for enabling service convergence on a
common transport platform. Since its inception, OTN has evolved beyond being a
simple wrapper for SONET/SDH to support flexible packet technologies including new
Ethernet interfaces, MPLS, and Segment Routing.15
The use of FEC significantly increases the system margin for a given Bit Error Rate
(BER) and signal power. This, in turn, allows for longer transmission spans between
optical amplifiers or regeneration sites. By extending the distance between optical
repeaters, network providers can reduce the number of active components in the
network, which helps in reducing both capital expenditures (CAPEX) and operational
expenses (OPEX). Furthermore, it can simplify the overall network topography, for
example, by enabling the skipping of amplifier sites.15 FEC is particularly crucial for
enabling the high data rates (e.g., 100G, 400G, 800G and beyond) used in modern
optical networks.
These OTN cards and modules are the fundamental building blocks for constructing
OTN-based transport networks. They implement the functionalities defined by ITU-T
G.709, including client signal mapping, multiplexing into OTN containers (ODUk),
switching of ODUk paths, and transport over high-capacity wavelengths with
integrated FEC and comprehensive monitoring capabilities.15
Furthermore, in the context of the Ciena OME 6500, terms like "PKT/OTN XCs"
(Packet/OTN Cross Connects) and "PKT/OTN XCIF" (Packet/OTN Cross Connect
Interface) are used, particularly when discussing alarms such as "Intercard
Suspected".23 This strongly suggests that packet cross-connect functionality is often
integrated with OTN cross-connect capabilities on the same interface cards or
modules.
3.4.1. XCIF (Cross-Connect Interface): Definition, Role, and Mating (e.g., with OCI)
XCIF stands for Cross-Connect Interface.23 These are specialized Ciena hardware
components, typically circuit packs or modules, that provide the physical and logical
interfaces necessary for cross-connecting optical signals, particularly within OTN
environments.
Specific examples of Ciena XCIF cards include the NTK620AA, which is a 40G OTN
XCIF 24, and various 100G PKT/OTN XCIFs used in the OME 6500 platform.6 These XCIF
cards are designed to work in conjunction with other types of cards, such as OCI
(Optical Channel Interface) cards or OCLD (Optical Control Link Domain) cards. For
example, the NTK525CFE5 (a 40G MUX OCI) can be mated with the NTK620AA (40G
OTN XCIF) 24, and 100G PKT/OTN XCIFs can be mated with 100G OCLD or OCI
modules.6
The process of mating these cards can involve specific configurations and adherence
to certain rules. For instance, to successfully mate an OCI card like the NTK525CFE5
with an XCIF like the NTK620AA, the OCI card might need to be switched from its
default "Transponder" mode to "POTS" (Photonic Optical Transport System) mode.
Additional rules may apply, such as specific settings on the XCIF equipment (e.g.,
configuring it for 10G operation rather than 4x10G) and ensuring the OCI card is
placed in a designated (e.g., odd-numbered) slot within the shelf.24 FTTP (Flexible
Termination Port) facilities residing on XCIF cards play a role in the automatic creation
of OSRP links when these XCIFs are mated with OCLD/OCI cards, highlighting the
XCIF's role in the control plane as well.6
Understanding these mating rules, configuration modes, and the role of XCIFs in the
overall system architecture is vital for network engineers when provisioning services
and troubleshooting connectivity issues in Ciena optical transport systems.
Ciena platforms offer tools for managing XCs. For example, on Ciena Z-Series nodes,
the Planet Operate Client allows users to create, delete, and verify cross-connections
on various types of cards, including Transponder, Packet, Muxponder, and even
passive cards.22 Within the Ciena 6500 platform, OTN cross-connects are typically
created between ODUCTP (Optical Data Unit Connection Termination Point) facilities.
This can be done using Ciena's Site Manager software, often found under menus such
as "Configuration / Nodal Connections / OTN Connections" 24 or "Configuration /
Cross-Connects / OTN Connections".26
The integrity of these cross-connects is also monitored. For instance, in Ciena's SAOS
6.x software, an "XC (Cross-connect) error flag" within the CFM (Connectivity Fault
Management) framework can indicate issues such as a Connectivity Check Message
(CCM) being received with an incorrect MA-id (Maintenance Association Identifier) or
MD (Maintenance Domain) Level.27 This demonstrates that the status of
cross-connects is tied into service assurance mechanisms. The Ciena 6500 platform
itself is capable of supporting very high-capacity cross-connects, including
SONET/SDH XCs (both low order and high order) and Packet/OTN XCs with capacities
scaling into the Terabit range.16
The modular design of Ciena hardware, which allows for combinations of cards like
OCIs and XCIFs, provides significant scalability and flexibility. However, this modularity
inherently introduces a layer of complexity. This complexity manifests in the need for
precise inter-card compatibility, adherence to specific provisioning rules (such as OCI
modes or XCIF settings 24, and OCLD/OCI mating rules 28), and can lead to unique fault
conditions like "Intercard Suspected" alarms involving PKT/OTN XCIFs.23 While
modularity enables tailored network solutions and growth, it necessitates detailed
technical knowledge, careful configuration, and robust NMS capabilities for effective
management and troubleshooting.
OCLDs are involved when 100G PKT/OTN XCIF and 40G OTN XCIF cards are mated
with their corresponding 100G OCLD or 40G OCLD modules.6 This mating facilitates
the establishment of OSRP links. For example, a Ciena community discussion
references the NTK539QV, a 200G OCLD with Encryption, acting as an aggregate or
line-side interface for client-side OCI cards.28 This suggests that OCLD cards can
serve as central aggregation points or line interface modules to which multiple
client-side OCIs connect. The OCLD card itself, such as the 200G OCLD, has specific
mating rules with OCI cards that depend on factors like bandwidth requirements and
modulation schemes (e.g., 16QAM versus QPSK).28
The OCLD is part of the photonic layer infrastructure that supports OSRP. While OSRP
can run over the in-band Optical Supervisory Channel (OSC), and there are options
for Out-Of-Band Channel (OOBC) communication for OSRP messages, the OCLD
appears to be a key hardware element that enables these control communications.5
Understanding the role of OCLD and its interaction with OSRP, OSC, XCIFs, and OCIs
is crucial for comprehending the architecture and operation of Ciena's Layer 0 control
plane.
The auto-creation of OSRP links for FTTP facilities on XCIFs when mated with
OCLD/OCI cards 6, alongside the general capability to configure cross-connects via
software tools like Planet Operate and Site Manager 22, points towards an increasing
reliance on software-defined control and programmability within Ciena's hardware
ecosystem. This aligns with broader industry movements towards more agile,
automated, and programmable network operations, allowing for faster service
provisioning and dynamic network adjustments.
3.6. Understanding RNATs in Ciena Networking
The term "RNATs" was investigated in the context of Ciena networking based on the
provided research materials. However, this term is not explicitly defined or explained
as a specific Ciena networking technology, protocol, or hardware component within
these documents.2 General Ciena company overviews and solution descriptions 32 do
not mention RNATs. Similarly, discussions of common optical networking technologies
like ROADMs (Reconfigurable Optical Add/Drop Multiplexer) 35 do not use this term.
Browser-based searches for "Ciena RNATs" also did not yield a specific networking
definition relevant to Ciena systems.3 Some search results were entirely unrelated to
Ciena or networking.36
Given the absence of information in the provided materials, it is not possible to define
"RNATs" as a recognized Ciena networking term or technology. It is conceivable that
"RNATs" could be an internal Ciena project code, a very new or niche technology not
yet covered in publicly available documentation, a typographical error in the original
query, or a concept from an entirely different domain mistakenly associated with
Ciena networking.
Therefore, this report must state that, based on the available research, "RNATs" could
not be defined in the context of Ciena networking.
The facility types discussed (PTP, ETTP, ODUCTP, TCMCTP) often represent a
hierarchical structure for service and signal termination and monitoring.26 Faults
occurring at a lower-layer facility, such as a Loss of Signal at a Physical Termination
Point (PTP), will typically propagate upwards and can cause alarms at higher-layer
facilities like an Ethernet Transport Termination Point (ETTP E-LOS), an Optical Data
Unit Connection Termination Point (ODUCTP alarm), or a Tandem Connection
Monitoring Connection Termination Point (TCMCTP LTC). This inherent characteristic
of layered networks implies that effective network management systems must
incorporate intelligent alarm correlation. Such correlation is essential to pinpoint the
root cause of a service issue rather than merely reacting to a cascade of sympathetic
alarms, thereby streamlining the troubleshooting process.
PTP (Physical/Path Physical port Loss of Clock (LOC), Physical layer issues,
TP) termination for Rx Loss of Clock, clock recovery failure,
client/line signals; Signal Degrade (SD), signal quality
synchronization Signal Fail (SF), Tx/Rx degradation,
(1588v2 PTP) Power "Unknown" SFP/XFP/QSFP issues,
fiber problems 30
ETTP (Ethernet Termination point for Ethernet Loss of Ethernet signal loss,
Transport TP) Ethernet services Signal (E-LOS), far-end Ethernet
Ethernet Remote fault, local Ethernet
Fault Indication fault signaled,
(E-RFI), EFFI, PM performance
errors, 15-Min TCAs degradation (CV, ES,
UAS) 43
ODVCTP (ODU Termination point for (Likely similar to Issues with member
Virtual Concatenation virtually ODUCTP, plus links of VCAT group,
TP) concatenated ODU VCAT-specific alarms differential delay,
groups (assumed) like LOM, SQM - not sequence errors
detailed in snippets) (general VCAT issues)
The concepts of Trail Termination Point (TTP) and Connection Termination Point (CTP)
are central to understanding OTN facilities. A TTP is defined as a point where the
overhead associated with an OTN trail (a complete end-to-end path) is terminated or
generated. In contrast, a CTP is a point where a specific connection or circuit (which
could be a segment of a trail) can be terminated or, crucially for service assurance,
monitored for performance.40 Ciena's technical documentation, such as the
"Provisioning CTP (323-1851-310.x)" guide for the 6500 product series, provides
detailed descriptions of the OTN facility model and how these concepts are applied.40
Effective facility management is paramount for network operators to interact with and
control services at a granular level. A thorough understanding of these logical entities,
their hierarchy, and their configurable parameters is essential for successful service
provisioning, ongoing service assurance, and efficient fault localization.
PTP facilities are provisioned and configured using Ciena's management software,
such as Site Manager.26 For example, the creation of PTPs is often a prerequisite step
before higher-layer facilities like ODUCTPs can be provisioned for a service, such as a
10G Ethernet service.26 PTPs are intrinsically linked to physical ports and their specific
characteristics, including parameters like transmitter optical power and operational
wavelength or frequency, which can be configured and monitored via the
management system.53 Monitoring these PTPs is crucial for verifying basic physical
layer connectivity and ensuring the integrity of the signal at its point of ingress or
egress.
It is worth noting that "PTP" also stands for Precision Time Protocol (as per IEEE
1588v2), which is used for network synchronization. Some Ciena devices, like the 3932
Service Delivery Switch, support IEEE 1588v2 PTP for delivering accurate timing over
packet networks.54 However, the primary focus here is on PTP as a facility type
representing a physical signal termination point.
4.2.2. Monitor Types and Common Error Messages (e.g., Loss of Clock, SD, SF)
PTP facilities are subject to various monitor types and can report several error
messages or alarms, primarily indicating physical layer problems or severe signal
degradation:
● Loss of Clock (LOC) / Rx Loss of Clock: This alarm indicates that the receiving
port is unable to recover a stable clock signal from the incoming data stream. It
can occur even if the port is receiving adequate optical power if the performance
layer (e.g., due to excessive errors or FEC issues) is not meeting acceptable
criteria. Other causes include frequency mismatches between the connected
equipment, faulty patch cords or connectors, hardware failures on the port or
associated circuitry, or an XCVR (transceiver) operating above its specified
temperature range (XCVR Over Temperature).41
● Signal Degrade (SD) / Signal Fail (SF): These are general alarms indicating that
the quality of the received signal at the PTP has fallen below acceptable
thresholds. SD typically signifies a deteriorating signal that may still be usable but
is at risk, while SF indicates a more severe degradation where the signal is likely
unusable.30 These can be triggered by various underlying issues affecting signal
integrity.
● OOS-MA (Out-of-Service Maintenance): This is a TL1 (Transaction Language 1)
code indicating that the facility has been administratively placed in an
out-of-service state, often for maintenance purposes like performing a loopback.
When a PTP port is set to OOS, any higher-layer CTP facilities that are dependent
on that PTP for service will also become faulty. This can lead to the incrementing
of performance monitoring counters such as UAS (Unavailable Seconds) for the
affected service.55
● Tx/Rx Power "Unknown": In Ciena's Site Manager, the transmit (Tx) or receive
(Rx) optical power level for a PTP facility might sometimes display as "Unknown."
This can indicate an issue with the SFP/XFP/QSFP transceiver itself or its
communication with the base module. Troubleshooting steps often include
performing a warm reset on the transceiver, reseating it, or ultimately replacing
the transceiver or the base module it plugs into.29
● Loss of Signal (LOS): Although not exclusively tied to PTPs in the provided
information, LOS is a fundamental physical layer alarm indicating that no optical
signal (or an extremely weak one) is being detected at the receiver. This is a
common PTP-level fault.
These alarms are critical indicators of the health of the physical connection. Prompt
attention to PTP alarms is essential as they often represent foundational issues that
will impact all services traversing that physical interface.
ETTPs are managed and monitored through Ciena's network management tools like
Site Manager and MCP (Management Control Platform). The operational status of an
ETTP, such as its Link State (Up or Down), can be observed through these systems.51
The primary purpose of an ETTP is to serve as the point where Ethernet frames are
processed. This processing can include functions like VLAN tagging, MAC address
learning, Quality of Service (QoS) policing/shaping, and mapping the Ethernet service
into an appropriate transport structure (such as an OTN ODU container or an MPLS
pseudowire). Furthermore, ETTPs are crucial for monitoring Ethernet-specific
performance parameters and alarms.
4.3.2. Monitor Types and Common Error Messages (e.g., E-LOS, E-RFI, PM errors)
ETTP facilities are associated with several monitor types and can generate specific
error messages and alarms that are vital for managing the health and performance of
Ethernet services:
● Ethernet Loss of Signal (E-LOS / Ethernet-LOS): This alarm on an ETTP
indicates that the incoming Ethernet signal is no longer detected at the physical
port associated with the ETTP. Troubleshooting steps typically involve checking
the far-end Ethernet transmitter, verifying the SFP/XFP/CFP transceivers at both
ends, inspecting the fiber optic cable and connectors for damage or
contamination, and potentially performing fiber loopbacks to isolate the fault.43
● Ethernet Remote Fault Indication (E-RFI): An E-RFI alarm signifies that the
equipment at the remote end of the Ethernet link has detected a fault and is
signaling this condition back to the local ETTP.43 This helps in fault domain
isolation by indicating that the problem likely lies towards the far end or is being
experienced by the far-end device.
● Ethernet Forward Fault Indication (EFFI): Conversely, an EFFI alarm indicates
that the local ETTP has detected a fault (e.g., E-LOS from its connected
equipment) and is signaling this fault condition towards the far-end Ethernet
device.43
● Intermittent PM (Performance Monitoring) errors: ETTP facilities can report
intermittent performance monitoring errors. These are typically tracked using
Ciena's Site Manager, which provides access to detailed PM counters for the
ETTP.44 Such errors might include excessive Frame Check Sequence (FCS) errors,
alignment errors, or other Ethernet layer issues.
● 15-Min Threshold Crossing Alert (TCA): For various ETTP performance
parameters, such as those related to the Physical Coding Sublayer (PCS) or
general Ethernet statistics like Coding Violations (CV), Errored Seconds (ES), and
Unavailable Seconds (UAS), thresholds can be set. If the count of these errors or
events exceeds the configured threshold within a 15-minute interval, a TCA event
is generated.45 TCAs serve as early warnings of degrading performance before a
hard failure might occur.
● Far End (FE) TX errors on ODUCTP layer: An interesting interaction can occur
when a loopback is placed on a client-facing ETTP facility. In such scenarios, it's
possible to observe "FE TX errors" (Far End Transmit errors) incrementing on the
ODUCTP layer that is carrying this Ethernet service. These errors are typically
propagated back from the downstream network element (NE) that receives the
looped signal and detects anomalies. This behavior is generally expected when
such a loopback is active.55
These alarms and performance monitors are critical for ensuring the operational
health of Ethernet services. E-LOS points directly to physical connectivity or signal
reception problems. E-RFI and EFFI are important for localizing faults within an
Ethernet segment. PM errors and TCAs provide valuable insights into the ongoing
quality and performance of the Ethernet service, enabling proactive maintenance and
SLA management.
4.4.2. Monitor Types and Common Error Messages (e.g., CFM faults, On Ramp
triggers)
Specific monitor types and error messages for ODVCTPs (with an emphasis on the
VCAT aspect) are not exhaustively detailed in the provided Ciena-specific material
beyond general ODUCTP monitoring. However, several related monitoring concepts
and alarms can be inferred or are directly applicable:
● ODUCTP On Ramp Condition Trigger: This is a Ciena-specific feature for
ODUCTPs. It can be configured with conditions like "Client Fault" or "Client Fault
and Port OOS" (Out-of-Service). The behavior is such that in the first case,
conditioning (an action, possibly related to protection switching or alarm
reporting) will occur if either the client fault is present or the port is OOS. In the
second case, conditioning will only trigger if both conditions (client fault and port
OOS) are true simultaneously. This feature generally triggers when there is an
alarm on the ODUCTP or the ODUCTP itself is administratively out-of-service.47
This mechanism allows for client-side conditions to influence the behavior or
status of the line-side ODU transport.
● CFM (Connectivity Fault Management) Service Faults: If an Ethernet service is
being transported over an ODVCTP (or ODUCTP), and CFM is used for
end-to-end Ethernet layer monitoring, then CFM faults could be relevant
indicators. These include:
○ XC (XconCCM): Indicates a mismatch of the MAID (Maintenance Association
Identifier) or MD (Maintenance Domain) Level in exchanged CCMs (Continuity
Check Messages).27
○ CC (Error CCM): Signifies a mismatch of MEPID (Maintenance End Point
Identifier) or the CCM-interval in the exchanged CCMs.46
○ RM (Remote MEP CCM defect): Raised when the local MEP is not receiving
CCMs from one or more Remote MEPs, often due to Layer 1 faults.46
○ MS (MAC Status) / PS (Port Status): Indicates that a remote MEP
transmitted a CCM for an interface that is not in a forwarding state (e.g., the
User Network Interface - UNI - is down).46 Accurate provisioning of these CFM
parameters is crucial, as mismatches are a common cause of these faults,
directly linking provisioning accuracy to service health.
● DOC (Domain Optical Control) Alarms: If the ODVCTP is part of an optical
domain managed by Ciena's DOC, then DOC-related alarms could be indicative of
issues affecting the ODU path. Alarms such as "DOC Action Failed: Optimize" or
"DOC Action Failed: Monitor" can occur due to maintenance activities (like
module replacement or fiber cuts) happening during a DOC auto-re-optimize run,
or due to other active alarms within the DOC span of control, such as "DOC
Invalid Photonic Domain," "Adjacency Far End Not Discovered," or "Optical Line
Fail".58
● ODU-AIS (Alarm Indication Signal) Receive Alarm: This alarm can be raised on
ODU facilities (e.g., an ODUTTP, which is closely related to an ODUCTP, on a 100G
PKTOTN card).48 ODU-AIS indicates that an upstream failure has occurred, and an
AIS signal is being propagated downstream at the ODU layer to suppress
consequential alarms. This is a critical alarm pointing to a service-affecting fault
elsewhere in the network.
For VCAT-specific monitoring (ODVCTP), one would typically expect to see alarms
related to the health of the VCG, such as Loss of Multi-frame (LOM) if the VCAT
framing is lost, or alarms related to excessive differential delay between member links,
or sequence errors if member payloads arrive out of order. While not detailed in the
Ciena snippets, these are standard VCAT monitoring parameters defined in ITU-T
G.709.
A TCMCTP facility in Ciena software represents the logical point where one of these
TCM layers is terminated or monitored. Ciena's 6500 platform, for example,
implements TCM to provide improved service assurance, enhanced service fault
correlation, and more precise troubleshooting capabilities, especially when handling
traffic that traverses third-party networks or multiple administrative domains.16 By
using TCMCTPs, an operator can monitor the health and performance of a specific
segment (a "tandem connection") of an end-to-end ODU path. This is invaluable for
fault isolation, as it helps pinpoint exactly where errors or failures are occurring along
a complex service path. This capability is critical for managing SLAs, especially when
multiple providers or network segments are involved in delivering a single service.
4.5.2. Monitor Types and Common Error Messages (e.g., TCM Loss of Tandem
Connection)
The primary alarm associated with TCMCTP facilities is indicative of issues within the
monitored tandem connection segment:
● TCM Loss of Tandem Connection (LTC): This alarm is raised against a TCMTTP
(Tandem Connection Monitoring Trail Termination Point, which is functionally very
similar to a CTP for monitoring purposes) or TCMCTP facility. It signifies a problem
with the specific tandem connection being monitored by that TCM level.49 The
ITU-T G.709 standard also defines LTC as a key TCM alarm.31 Clearing this alarm
typically involves:
1. Verifying that the TCM facility is correctly provisioned at both ends of the
monitored segment. Mismatches in TCM level provisioning or configuration
are a common cause of LTC alarms.
2. Ensuring that the underlying photonic path is clean and error-free, especially
if an OSRP Line (indicating an optical control plane managed path) is
provisioned for the service.49 Issues at lower layers (e.g., PTP alarms, ODU
layer alarms) will invariably affect the TCM layer.
● SFP Unknown / Tx,Rx Power "Unknown": While one Ciena article (related to
clearing SFP Unknown issues) is cross-referenced under TCMCTP alarms 29, the
issue described (Tx/Rx power showing "Unknown" in the PTP Facility) is
fundamentally a physical port or transceiver problem. Such an issue would
certainly impact any service traversing that port, including one monitored by a
TCMCTP, but the alarm itself originates at the PTP or physical interface level.
● Management System Issues: Alerts like "MCP: TCMCTP facility not showing on
MCP" 59 are related to the Network Management System itself (e.g., MCP not
displaying the facility correctly) rather than being a network fault alarm detected
by the TCMCTP.
● General Log Message Legend: Ciena systems use a log message legend with
indicators such as "!!!" (STOP or ERROR), "*" (WARNING), "+" (NOTICE), and "-"
(INFO) to denote the severity of logged events.62 These indicators would apply to
any events or status changes logged for TCMCTP facilities, helping operators
assess their impact.
● ITU-T Defined TCM Alarms/Events: The ITU-T G.709 standard, upon which
Ciena's TCM implementation is based, defines a range of TCM-related alarms and
error monitoring mechanisms. These include TCM-AIS (Alarm Indication Signal),
TCM-OCI (Open Connection Indication), TCM-LCK (Locked), TCM-TIM (Trace
Identifier Mismatch), TCM-BDI (Backward Defect Indication), TCM-IAE (Incoming
Alignment Error), TCM-BIAE (Backward Incoming Alignment Error), as well as error
performance counters like TCM-BIP-8 (Bit Interleaved Parity) and TCM-BEI
(Backward Error Indication).50 Ciena's specific alarm names and event reporting
would map to these standardized defect and monitoring conditions.
The "TCM Loss of Tandem Connection" alarm is the most direct indicator of a failure
or severe degradation within the specific network segment monitored by that TCM
level. However, troubleshooting often requires investigating underlying PTP, ETTP, or
ODUCTP alarms, as these can be the root causes for TCM layer issues. The accuracy
of provisioning for TCM facilities at both ends of the monitored segment is paramount;
mismatches or incomplete configurations are frequent sources of TCM-related
alarms. This highlights a direct causal relationship: meticulous provisioning is
fundamental to ensuring service health and minimizing alarms across all network
layers, including TCM.
5. Conclusion
This report has provided a detailed technical examination of key Ciena optical
networking protocols, hardware components, and software facility management
constructs. The Optical Signaling and Routing Protocol (OSRP) and Open Shortest
Path First (OSPF) serve distinct but complementary roles, with OSRP managing the
dynamic optical layer control plane and OSPF handling IP layer routing. This layered
approach to routing and control is a hallmark of Ciena's strategy to enable intelligent
automation across different network domains.
Core Ciena hardware components such as Optical Transport Network (OTN) cards,
Cross-Connect Interfaces (XCIFs), general Cross-Connect (XC) capabilities, and
Optical Control Link Domains (OCLDs) form the building blocks of resilient and flexible
optical transport solutions. OTN, with its 'digital wrapper' concept and robust Forward
Error Correction (FEC), provides a standardized and efficient means to transport
diverse client services. XCIFs and OCLDs are integral to the internal switching fabric
and control plane communication, respectively, particularly in platforms like the 6500
series. The term "PKCT card" was not found as a distinct Ciena component, though
packet cross-connect functionality is widely integrated. Similarly, "RNATs" could not
be defined as a Ciena networking term based on the available information.
6. Glossary of Terms
Table 3: Glossary of Acronyms and Key Terms
XC Cross-Connect A software-defined
connection within a network
element that routes signals
between ports or fabrics. 22
Works cited