s

Confidential
Date 2002/03/28 2003/09/30 2004/04/30

Layer Restrictions At Optical Protections

Technical Note

Technical Note: Layer Restrictions at Optical Protection
Issue/State 1. issue TNMS Core V8.0 2. issue TNMS Core V8.5 3. issue TNMS Core V9.0 Name Woller / Dold Woller Pieper Comments Initial creation Adapted to TNMS Core V8.5 Adapted to TNMS Core V9.0

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

3 The General Rules
The operator has to restrict the layer of port connections terminating at OCP/PM cards. This can be done via "Restrict To"-field of the port connection property page. 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! CHOOSING THE LAYER: • Do not care if the "Other NE" is a SHDH NE: If the "Other NE" in figure 1 is a SDH NE (e.g. a SL64), no adjustments have to be made. In cases of doubt, one can check the tooltip for the port of the "other NE" (see Figure 2. If the terminated layer set (TL) of this port include SDH layers (e.g. one of the following: RS64, MS64, RS16, MS16, etc), everything should work fine. However, it would be also possible to restrict the terminated layer set of Port Connections in this case in order to reduce the number of server paths, see example in chapter 4.3 Two FSP3000 with PM Module, with SDH NEs • Otherwise, restrict to layer OCH: If the "Other NE" is not a SDH NE (in the sense explained above), but if the port connections between the "Other NE" and the OCP/PM card can be restricted to "OCH", choose "OCH".

© Copyright Siemens AG 2003
ICN CP D NM EM2

all rights reserved Technical Note 56544589.doc page 1/12

without any transponder or multiplexer cards) to the optical line equipment. in which the protection card is connected directly (i. In this case. the layer of the port connection to the other NE can only be restricted to "OPTICAL".1E. restrict to "OPTICAL": fFor some NE's (e.g. MTS 2. certain WL8 and 16.5 Other NE OCP OCR10G OCR10G OCR10G OCR10G internal Port Connections Ports Port Conection Termination Point Figure 1 Figure 2 • Only if you have no other choice. © Copyright Siemens AG 2003 ICN CP D NM EM2 all rights reserved Technical Note 56544589. the results obtained are often not very user friendly or intuitive .1A. (This is the default setting which gives usable results in all cases.e. MTS 1.see example below).03. that these are very rare cases. Note.2.s Confidential Layer Restrictions At Optical Protections Technical Note OSN OCU 1. restrict the internal port connections to "OPTICAL". MTS 1.doc page 2/12 . too. However. hiT 7550 types).

5 After migration.2 Migration from TNMS Core V7V8.doc page 3/12 . • Figure 2 © Copyright Siemens AG 2003 ICN CP D NM EM2 all rights reserved Technical Note 56544589. the Terminated Layer Set of port connections involving OCP/PM cards (thus involving GENP ports) is might be restricted to "OPTICAL" by default.0 when not following this recommendation (even though the path possibly appeared as desired in V8 already). This ensures that no paths (in TNMS database) pass the concerned port connections.s Confidential 3. No further steps are necessary.0. However. Generally.5 and V9. Make sure that the layer setting is consistent with the rules explained above. • Choose the layers according to the rules described above. a change of the layer set restriction is recommended in all cases stated above in chapter “General Rules”.If this needs to be changed. Start the usual path migration. proceed as follows: • Deactivate the Path Aanalyszer in the TNMS cClient: Choose “Disable Analyzer” on Unmanaged Paths Tree. if haven’t been performed yet. too. Admin.0/ V8. Note. there is no further adjustment necessary and avoids eventually conflicting unmanaged paths. It is highly recommended to adapt the port connection layer sets very carefully at this step.5 will be used in TNMS Core V9. • Activate the Path Analyzer analyser in the TNMS Cclient. This procedure ensures.1 Layer Restrictions At Optical Protections Technical Note New NE introduced to TNMS Whenever new NEs equipped with OCP or PM Card having already configured port assignments are to be introduced to TNMS Core. • Activate the NE in the DCN management of the TNMS Sys. because a wrong setting may result in split paths in TNMS database. • Move the NE icon to its place on the TNMS network map and create the port connections connected to the NE. the same layer set restriction set up in TNMS Core V8. proceed as follows: • Follow the instructions given during the migration process on Migration Wizard’s page 3: The system offers to adapt the layer sets of port connections before the actual path migration is started. that the path representation might change in some cases between V8/V8. • Check also the adjacent NE's: these NE's might have internal port connections. 3.

1 Two OCU 1. Remember that the default setting is "OPTICAL". The internal port connections connect the OCP card with the 4 OCR 10G cards: OCR10G OCR10G OCR10G OCU125_002 OCR10G OCR10G OCU125_001 OCP OCR10G OCR10G OCR10G OCP 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.5 with OCP.1 and 3. © Copyright Siemens AG 2003 ICN CP D NM EM2 all rights reserved Technical Note 56544589. RSx. MSx have to be deleted from managed or unmanaged path tree. without further SDH NEs Two OCU 1. both configured in the same way as Figure 1 shows (but without any "other NE").Activate the analyser in the TNMS client. and each NE contains additionally four internal port connections. proceed as follows: • Deactivate the Path Analyzer in the TNMS Client: Choose “Disable Analyzer” on Unmanaged Paths Tree. • “Adopt nNetwork rRoute” for all concerned client paths.Deactivate the analyser in TNMS client • Open “Port Connection Properties” and check the paths using this port connection.2.1. The pictures what these paths look like. Both NE's are connected by four unidirectional port connections.2 have not been complied.3 Later changes Layer Restrictions At Optical Protections Technical Note If later changes have to be made. In order to make sure. when both general rules 3.doc page 4/12 . 4 Examples 4. This examples (see Figure 3) uses two OCU 1.s Confidential 3. if necessary. • Activate the Path Analyzer in the TNMS Client. OCH. 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”.2. All paths on layers OPTICAL.2.5.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. that no cross connection will be deleted and no alarm mask setting will be changed.1 4. Thus each NE contains one OCP card and four OCR 10G cards. 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.

s Confidential Layer Restrictions At Optical Protections Technical Note Figure 4 Figure 5 © Copyright Siemens AG 2003 ICN CP D NM EM2 all rights reserved Technical Note 56544589.doc page 5/12 .

doc page 6/12 .1.5 with OCP: oOptimiszed lLayer rRestrictions This example shows the same situation as above.2. Figure 7 shows.s Confidential 4.2 Layer Restrictions At Optical Protections Technical Note Two OCU 1. Figure 6 The next picture. The Figure 6 shows how to do this. but this time all internal PCs have been restricted to OCH. © Copyright Siemens AG 2003 ICN CP D NM EM2 all rights reserved Technical Note 56544589. that the Analyzer finds just one bi-directional path instead of the 8 unidirectional paths above.

1. without SDH NEs This examples (see Figure 8) uses two FSP3000 SL 3. Both NE's are connected by two bidirectional port connections. Thus each NE contains one PM Module and two WCM Cards.s Confidential Layer Restrictions At Optical Protections Technical Note Figure 7 4. both configured with PM Modules and WCM Transponder Cards implementing both Tributary and Line side.doc page 7/12 . These internal port connections connect the PM Module with both WCM Cards: WCM WCM FSP3000_001 PM FSP3000_002 WCM WCM PM Figure 8 © Copyright Siemens AG 2003 ICN CP D NM EM2 all rights reserved Technical Note 56544589. and each NE contains additionally two internal port connections.2 Two FSP3000 with PM Module.

s Confidential 4. Figure 9 © Copyright Siemens AG 2003 ICN CP D NM EM2 all rights reserved Technical Note 56544589. 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.doc page 8/12 .2.1 Layer Restrictions At Optical Protections Technical Note Using the default setting Unlike the possibly expected end-to-end protected path on RS16 layer.

Procedure for restricting the layer set as shown in Figure 6 © Copyright Siemens AG 2003 ICN CP D NM EM2 all rights reserved Technical Note 56544589.2 Optimized Layer Restrictions This example shows the same situation as above.s Confidential Layer Restrictions At Optical Protections Technical Note Figure 10 4.doc page 9/12 . see Figure 11. but this time all internal PCs have been restricted to OCH.2.

It uses 4 independent server paths (two RS16 server paths are used once. see Figure 13: Since the PM Module is connected directly to STM-16 ports in an SDH NE. SDH NE WCM WCM FSP3000_001 PM FSP3000_002 WCM WCM PM SDH NE Figure 12 4. with SDH NEs As already mentioned in cahpter 3 General Rules.3. i. one can proceed as described herein.s Confidential Layer Restrictions At Optical Protections Technical Note Figure 11 4.doc page 10/12 . two OCH server paths are used twice on both sides). If it is for some reasons required to reduce the number of server paths. © Copyright Siemens AG 2003 ICN CP D NM EM2 all rights reserved Technical Note 56544589. SDH NEs are connected directly to OCP or PM Cards on both ends.e. the Path Analyzer detects an MS16 trail between both SDH NEs. it is not mandatory to restrict layer sets of port connections in network topologies like shown in Figure 12.3 Two FSP3000 with PM Module.1 Using the default setting Using the default layer restrictions shoud lead in all cases to a complete end-to-end SDH path between ports of both adjacent SDH NEs.

3.doc page 11/12 . The result (without unnecessary server paths) is displayed in Figure 14. © Copyright Siemens AG 2003 ICN CP D NM EM2 all rights reserved Technical Note 56544589.2 Optimized Layer Restrictions In order to reduce the number of server paths as displayed in Figure 13. layer sets can be resticted as well to layer OCH.s Confidential Layer Restrictions At Optical Protections Technical Note Figure 13 4.

doc page 12/12 .s Confidential Layer Restrictions At Optical Protections Technical Note Figure 14 © Copyright Siemens AG 2003 ICN CP D NM EM2 all rights reserved Technical Note 56544589.

Sign up to vote on this title
UsefulNot useful