Professional Documents
Culture Documents
Confidential
1 Introduction
TNMS Core V9.0 supports the automatic detection and routing of paths via NE's which support optical
protection. The OCU family realizes the optical protection with the OCP card while the FSP 3000 uses
the protection module (PM).
In order to achieve the best routing results, some care has to be taken during the creation of the port
connections which terminate at the PM module or the OCP card. Additionally, the operator has to
modify automatically created port connections terminating at these cards (these are NE-'internal' port
connections, not visible on the network map but accessible via the port connection list of the NE).
This document will first state the general rules, illustrated afterwards by some examples. The following
advantages will be achieved by following these rules:
• The path analyser will achieve the most simple and most intuitive results.
• The number of server paths will be reduced.
2 Concerned NE's
• FSP 3000 R2.2 (=Waveline MN 3.1) equipped with PM module
• FSP 3000 R2.3 (=Waveline MN 3.2) equipped with PM module
• FSP 3000 R3.1 equipped with PM module
• OCU 1.2.5 equipped with OCP card
• OCU 2.1.5 equipped with OCP card
• OCU 2.2 equipped with OCP card
• OCU 2.6 equipped with OCP card
BEWARE:
• Port connections terminating at the same OCP/PM card have to be restricted to the same layer.
Do not forget 'internal' port connections which are accessible via the context menu of a NE.
E.g.Figure 1: OCU 1.2.5: internal PC's and PC's to the "other NE" must be restricted to same layer
• No paths must pass the port connection when changing the layer restriction. This applies to
managed and unmanaged paths!
Confidential
OCR10G
OCR10G
Ports
Port Conection
Termination Point internal
Port Connections
Figure 1
Figure 2
• Only if you have no other choice, restrict to "OPTICAL": fFor some NE's (e.g. certain WL8
and 16, MTS 1.1E, MTS 1.1A, MTS 2.03, hiT 7550 types), the layer of the port connection to the
other NE can only be restricted to "OPTICAL". In this case, restrict the internal port connections to
"OPTICAL", too. Note, that these are very rare cases, in which the protection card is connected
directly (i.e. without any transponder or multiplexer cards) to the optical line equipment. (This is
the default setting which gives usable results in all cases. However, the results obtained are often
not very user friendly or intuitive - see example below).
Confidential
Figure 2
Confidential
3.3 Later changes
If later changes have to be made, when both general rules 3.1 and 3.2 have not been complied,
proceed as follows:
• Deactivate the Path Analyzer in the TNMS Client: Choose “Disable Analyzer” on Unmanaged
Paths Tree.Deactivate the analyser in TNMS client
• Open “Port Connection Properties” and check the paths using this port connection. All paths on
layers OPTICAL, OCH, RSx, MSx have to be deleted from managed or unmanaged path tree. In
order to make sure, that no cross connection will be deleted and no alarm mask setting will be
changed, the concerned NEs have to be deactivated in DCN Management of TNMS SysAdmin
first! Attention: The deletion of server paths will affect all client paths, which might to be adapted
manually after changing the layer set!
• Restrict the layer sets of the port connections in “Port Connection Properties” window according to
the rules described above at “CHOOSING THE LAYER”.
• Activate the Path Analyzer in the TNMS Client.Activate the analyser in the TNMS client.
• “Adopt nNetwork rRoute” for all concerned client paths, if necessary.
4 Examples
4.1 Two OCU 1.2.5 with OCP, without further SDH NEs
4.1.1 Two OCU 1.2.5 with OCP: uUsing the default setting
This first example will show the results obtained by the Path Analyzer if the operator just uses the
default settings and doesn't adjust any layer restrictions. Remember that the default setting is
"OPTICAL".
This examples (see Figure 3) uses two OCU 1.2.5, both configured in the same way as Figure 1
shows (but without any "other NE"). Thus each NE contains one OCP card and four OCR 10G cards.
Both NE's are connected by four unidirectional port connections, and each NE contains additionally
four internal port connections. The internal port connections connect the OCP card with the 4 OCR
10G cards:
OCR10G OCR10G
OCR10G OCR10G
OCU125_001 OCU125_002
OCP OCP
OCR10G OCR10G
OCR10G OCR10G
Figure 3
The following two pictures (Figure 4 and Figure 5) that the Analyzer finds 4 paths in the OCH layer
and 4 paths on the RS64 layer. The pictures what these paths look like.
Confidential
Figure 4
Figure 5
Confidential
4.1.2 Two OCU 1.2.5 with OCP: oOptimiszed lLayer rRestrictions
This example shows the same situation as above, but this time all internal PCs have been restricted to
OCH. The Figure 6 shows how to do this.
Figure 6
The next picture, Figure 7 shows, that the Analyzer finds just one bi-directional path instead of the 8
unidirectional paths above.
Confidential
Figure 7
This examples (see Figure 8) uses two FSP3000 SL 3.1, both configured with PM Modules and WCM
Transponder Cards implementing both Tributary and Line side. Thus each NE contains one PM
Module and two WCM Cards. Both NE's are connected by two bidirectional port connections, and
each NE contains additionally two internal port connections. These internal port connections connect
the PM Module with both WCM Cards:
WCM WCM
FSP3000_001
PM FSP3000_002 PM
WCM WCM
Figure 8
Confidential
4.2.1 Using the default setting
Unlike the possibly expected end-to-end protected path on RS16 layer, two independent RS16 paths
with common half-open protected OCH server are found using the default layer restrictions, see Figure
10 for RS16 client path in collapsed expansion mode and Figure 10 for RS16 client path with its
expanded half-open protected OCH server paths.
Figure 9
Confidential
Figure 10
Confidential
Figure 11
WCM WCM
SDH SDH
FSP3000_001
PM FSP3000_002 PM
NE NE
WCM WCM
Figure 12
Confidential
Figure 13
Confidential
Figure 14