Professional Documents
Culture Documents
Revision Records
Date Revised version Description Author
2005-3-3
Page 2 of 35
Contents
Chapter 1 Guide to OptiX OSN 3500&2500 Service and Protection Configuration ................... 6 Chapter 2 Service Configuration Type ........................................................................................... 6 2.1 Networking and Protection Modes Supported by OptiX OSN3500/2500 ............................. 6 2.2 Other Special Service Configuration Types.......................................................................... 6 Chapter 3 Service Generation Principles of the Host................................................................... 7 3.1 The Service Configuration Is Based on Physical Optic/Electrical Ports Instead of Logical Systems. ..................................................................................................................................... 7 3.2 Service Configuration Is As Is, Without Automatic Service Duplication as in the PP Ring 8 3.3 Any Bi-directional Service Should be Composed of Two Unidirectional Service Configuration Commands. .......................................................................................................... 8 3.4 Generation of the MS Protection Data.................................................................................. 8 Chapter 4 Service Configuration Principles and Illustrations in Various Networking Modes . 9 4.1 Unprotected Modes of Chain Networking............................................................................. 9 4.1.1 Configuration Principles and Features....................................................................... 9 4.1.2 Configuration Illustration ............................................................................................ 9 4.2 Point to Point/Chain Linear MS protection.......................................................................... 10 4.2.1 Service Configuration Principles .............................................................................. 10 4.2.2 Configuration Illustration .......................................................................................... 11 4.2.3 Precautions for Configuration................................................................................... 13 4.3 Chain Hub Network............................................................................................................. 13 4.4 2-Fiber Bi-directional MS Shared Protection Ring.............................................................. 13 4.4.1 Service Configuration Features................................................................................ 13 4.4.2 Configuration Illustration .......................................................................................... 16 4.4.3 Service Configuration Principles .............................................................................. 17 4.5 2-Fiber Unidirectional MS Dedicated Protection Ring ........................................................ 17 4.5.1 Service Configuration Principles .............................................................................. 17 4.5.2 Configuration Illustration .......................................................................................... 18 4.6 4-Fiber Bi-directional MS Shared Protection Ring.............................................................. 18 4.6.1 Service Configuration Principles .............................................................................. 18 4.6.2 Configuration Notes ................................................................................................. 18 4.6.3 Configuration Illustration .......................................................................................... 19 4.7 Partial Multiplex Section Ring ............................................................................................. 19 4.7.1 Configuration Principles ........................................................................................... 19 4.8 Circumscribed MS Protection Rings ................................................................................... 20 4.9 Intersected MS Protection Rings ........................................................................................ 21 4.10 Multiplex Section Ring Chain............................................................................................ 22 4.11 SNCP ................................................................................................................................ 23 4.11.1 Service Configuration Principles ............................................................................ 23 4.11.2 Configuration Illustration ........................................................................................ 23 4.11.3 PP Protection Configuration................................................................................... 24 4.11.4 Working and Protection Paths in Various SNCP Networks ................................... 25 4.11.5 Configuration Notes ............................................................................................... 25 4.12 Shared Fiber Virtual Path Protection ................................................................................ 25 4.12.1 Concept of Shared Fiber Virtual Path Protection................................................. 25 4.12.2 Configuration Principles of Fiber Shared Virtual Path Protection of the OSN 3500/2500 ......................................................................................................................... 27 4.12.3 Configuration Illustration ........................................................................................ 27 4.13 Inter-ring Interworking Service Protection in the DNI Mode ............................................. 28 4.13.1 Service Configuration Principles ............................................................................ 28 4.13.2 Configuration Illustration ........................................................................................ 28
2005-3-3
Page 3 of 35
Chapter 5 Configurations of Other Special Types of Services.................................................. 32 5.1 Broadcast Services............................................................................................................. 32 5.1.1 Configuration Principles ........................................................................................... 32 5.1.2 Configuration Notes ................................................................................................. 32 5.2 Concatenation Services...................................................................................................... 32 5.2.1 Configuration Principles ........................................................................................... 32 5.2.2 Configuration Notes ................................................................................................. 33 5.2.3 Configuration Illustration .......................................................................................... 33 5.3 TPS Configuration............................................................................................................... 33 5.3.1 Configuration Notes ................................................................................................. 33 5.3.2 Configuration Illustration .......................................................................................... 34 5.4 Loopback Service of This Board......................................................................................... 34 5.5 Hardware REG.................................................................................................................... 34 5.5.1 Attribute Settings ...................................................................................................... 34 5.6 Extra Services of Multiplex Sections (Linear and Ring)...................................................... 35 Chapter 6 Configuration Restrictions .......................................................................................... 35
2005-3-3
Page 4 of 35
Keyword: OSN 3500/2500 Summary: The lowest cross-connect level of the OptiX OSN 3500/2500 V100R001 is VC12. The services are configured from board to board in a relatively simply way. The service types include vc12, vc3, vc4, au4-4c, au4-8c, au4-16c, au4-64c and au3. Abbreviation list: None. Reference list: None. Protection Configuration
2005-3-3
Page 5 of 35
MS protection ring
4 5
3.11 3.12
3. TPS configuration 4. Loopback service of this board 5. Hardware REG. Not supporting software REG 6. Extra services of multiplex sections (linear or ring)
Note that the following configuration parts are incorrect. Why? :cfg-add-xc:0, 12, 1&2, 1, 0, 5, 1, 1&2, 0, vc4;
2005-3-3 Huawei Confidential. No disclosure without permission. Page 7 of 35
:cfg-add-xc:0, 5, 1, 1&2, 0, 12, 1&2, 1, 0, vc4; The reason is that parameter repetition input is possible only for source channel number (or sink channel number) and source timeslot number (or sink timeslot number) in the command line configuration, but not for slot numbers and optical interface numbers. Therefore, it is not in compliance with the syntax for 12,1&2,1 to represent the first VC4 of Optical interface 1 and Optical interface 2.
3.2 Service Configuration Is As Is, Without Automatic Service Duplication as in the PP Ring
The host does not provide the function of automatic generation of SNCP/PP service protection paths. The network-wide complex service protection routes, such as SNCP, are sent to the host after being generated by the network management according to the appropriate algorithm (this is the actual function of network management), or the service routes are manually sent to the host through the command lines. In the old products (2500+, 155/622, etc.), for any service configured in a single direction for the SNCP/PP ring, the host will duplicate a reverse service automatically to make the service a bi-directional one.
3.3 Any Bi-directional Service Should be Composed of Two Unidirectional Service Configuration Commands.
This is based on the second principle mentioned above.
2005-3-3
Page 8 of 35
Figure 4-1 Figure 1 Point to point/chain unprotected modes The specific command line configurations are illustrated as follows. As shown in Figure 1, it is simple and made clear by the following illustration.
2005-3-3
Page 10 of 35
Figure 4-2 Figure 2 1:1 protection chain NE2 is configured as follows: :lognew:"szhw","nesoft"; :per-set-endtime:15m,1990@0@0@0@0@0; :per-set-endtime:24h,1990@0@0@0@0@0; :cfg-init-all; :cfg-set-devicetype:OptiXOsn3500,standard; :cfg-set-nename:64,"DEMO"; :cfg-add-board:9&10, gxcsa:1,ssn1sep1:7&8&11&12,ssn1sl16:18,nscc; :cfg-add-lmspg:1,1pn,1,rvt,biend; :cfg-set-lmsbdmap:1,0,8,1; :cfg-set-lmsbdmap:1,1,7,1; :cfg-set-lmsattrib:1,600; :cfg-add-lmspg:2,1pn,1,rvt,biend; :cfg-set-lmsbdmap:2,0,12,1; :cfg-set-lmsbdmap:2,1,11,1; :cfg-set-lmsattrib:2,600; :cfg-add-xc:0,7,1,1,0,11,1,1,0,vc4; :cfg-add-xc:0,11,1,1,0,7,1,1,0,vc4; :cfg-verify; NE3 is configured as follows: :lognew:"szhw","nesoft"; //:per-set-endtime:15m,1990@0@0@0@0@0; //:per-set-endtime:24h,1990@0@0@0@0@0; :cfg-init-all; :cfg-set-devicetype:OptiXOsn3500,standard; :cfg-set-nename:64,"DEMO";
2005-3-3 Huawei Confidential. No disclosure without permission. Page 11 of 35
:cfg-add-board:9&10,gxcsa:1,ssn1sep1:7&8,ssn1sl16:18,nscc; :cfg-add-lmspg:1,1pn,1,rvt,biend; :cfg-set-lmsbdmap:1,0,8,1; :cfg-set-lmsbdmap:1,1,7,1; :cfg-set-lmsattrib:1,600; :cfg-add-xc:0,7,1,1,0,1,1,1,0,vc4; :cfg-add-xc:0,1,1,1,0,7,1,1,0,vc4; :cfg-verify; In case of 1:3 linear MS protection, the configuration illustration is as follows: :lognew:"szhw","nesoft"; //:per-set-endtime:15m,1990@0@0@0@0@0; //:per-set-endtime:24h,1990@0@0@0@0@0; :cfg-init-all; :cfg-set-devicetype:OptiXOsn3500,standard; :cfg-set-nename:64,"DEMO"; :cfg-add-board:9&10,gxcsa:1,ssn1sep1:7&8,ssn1sl16:11&12,ssn1sl16:18,nscc; :cfg-add-lmspg:1,1pn,3,rvt,biend; :cfg-set-lmsbdmap:1,0,7,1; :cfg-set-lmsbdmap:1,1,8,1; :cfg-set-lmsbdmap:1,2,11,1; :cfg-set-lmsbdmap:1,3,12,1; :cfg-set-lmsattrib:1,600; :cfg-add-xc:0,7,1,1,0,1,1,1,0,vc4; :cfg-add-xc:0,1,1,1,0,7,1,1,0,vc4; :cfg-verify; In case of 1+1 uni-end switching, the service originating end must be configured in the dual transmit mode. In this way, the originating end must be configured with a dual transmit service through the command line configuration, which is illustrated as follows (NE3): :lognew:"szhw","nesoft"; //:per-set-endtime:15m,1990@0@0@0@0@0; //:per-set-endtime:24h,1990@0@0@0@0@0; :cfg-init-all; :cfg-set-devicetype:OptiXOsn3500,standard;
2005-3-3 Huawei Confidential. No disclosure without permission. Page 12 of 35
:cfg-set-nename:64,"DEMO"; :cfg-add-board:9&10,gxcsa:1,ssn1sep1:7&8,ssn1sl16:18,nscc; :cfg-add-lmspg:1,1j1,1,norvt,uniend; :cfg-set-lmsbdmap:1,0,8,1; :cfg-set-lmsbdmap:1,1,7,1; :cfg-add-xc:0,7,1,1,0,1,1,1,0,vc4;//Only one should be configured for receiving :cfg-add-xc:0,1,1,1,0,7,1,1,0,vc4;//This is sent to the 1+1 working channel :cfg-add-xc:0,1,1,1,0,8,1,1,0,vc4;//This is sent to the 1+1 protection channel :cfg-verify;
Figure 4-3 Figure 3 Chain hub network In Figure 3, the NE in the middle is configured as a chain hub point. The configuration is also based on the chain mode, so the command line is similar to that in the chain configuration, and refer to the related example for details.
2005-3-3
for the purpose of defining of the full-ring multiplex section parameters. 2) In the multiplex section node parameter definition for the equipment, such as the command :cfg-set-rmsattrib:1,1,5,2,600;, the second parameter 1 indicates the local node number, the third parameter 5 indicates the westbound node number, and the fourth parameter 2 indicates the eastbound node number. In this way, the node numbers of a NE and their relations with the left and right nodes are determined.
After node relations are defined for all the NEs in this way, the network-wide multiplex section networking relations are determined uniquely, like a circle formed by all nodes. One of the advantages in this node definition is easy capacity expansion, as shown in Figure 4 (A):
Figure 4-4 Figure 4 Multiplex section node definition (with OSN 3500 as an example) Originally, NE1 ~ NE4 form a MSP ring, with the nodes defined from 4 to 7. If you want to add one NE NE5 to the ring now, it is sufficient to modify part of the multiplex section nodes as follows: The node number of the added E5 is set to 8, the westbound node to 7, and the eastbound node to 4. For the multiplex section attributes of the original NE1, modify the westbound node number from 7 to 8. For the multiplex section attributes of the original NE4, modify the westbound node number from 4 to 8. The expansion is thus completed for the node, which involves only parameter modifications for the eastbound and westbound nodes adjacent to the added nodes. For the original multiplex section node settings, in contrast, it is necessary to increase by 1 the Maximum node number in the multiplex section attributes of all the NEs. Another advantage in this multiplex section node definition is willful and flexible setting, without need to increase from 0 by 1 in the primary ring direction. To be in agreement with the NM data, it is necessary to regard the NE with the minimum ID number in the ring network as the reference for the setting specifications of the node numbers, and set from 0 in the primary ring direction (to transmit in the east and receive in the west), allowing no leap. 3) When mapping VC4 to the multiplex section in the eastbound/westbound direction, it is sufficient to map the working channel and it is unnecessary to map the protection channel. For example, if SL16 is plugged in the slot 2,
Huawei Confidential. No disclosure without permission. Page 14 of 35
2005-3-3
the map command in the 2-fiber bi-directional multiplex section ring configuration is: :cfg-set-rmsbdmap:1,w1,2,1,1&&8; It is unnecessary to map the protection channel of 9&&16. Note: Make sure not to map the VC4 resources of the protection channel, otherwise errors may rise. To be specific, map the first 8 VC4s (or part of them) for SL16, and map the first 32 VC4s in the STM-64 for SL64. It could be easily concluded that, in the 2-fiber bi-directional multiplex section ring, the active channels must be defined in a number not larger than half of the maximum VC4 channel amount in the line, and only the first half could be used. The standby channels are duplicated automatically and correspond to the active channels one to one. The corresponding relation is active channel number + maximum channel number/2. The difference is that, in the unidirectional multiplex section ring, all the VC4s in the active optical path of span sections are working channels. In addition, the optical interface mapping relations of the 4-fiber ring are different, as detailed below. 4) As shown in the above mapping commands, the mapping of partial multiplex sections is supported. Refer to the subsequent Partial Multiplex Sections for details. There are restrictions to the dual slots of the plugboards in the ring networking.
5)
Try to form the multiplex section rings between the corresponding optical interfaces in dual slots, if not specially required. The reason lies in the existence of overhead bus interworking between the corresponding optical interfaces in dual slots, which could realize fast pass-through handling of the overhead (in K bytes) between the slots of ADM in the eastbound and westbound directions. Table 2 and table 3 list the layout of the dual slots of OSN 3500 and OSN 2500: Table 4-1 Table 2 Layout of OSN 3500 dual slots
Pairing slots 8 7 6 5 11 12 13 14 4 3 2 Pairing slots 15 16 17
The layout of dual slots is symmetric horizontally with the cross-connect board at the center. Try to use dual slots for form a ring network. The dual optical interfaces on the multiple optical interface board (sep1) in the dual slots are in the one-to-one relationship, namely optical 1 corresponds to optical 1, optical 2 corresponds to optical 2, and so on, and 8 optical interfaces are supported. The OSN3500 circuit board supports K-byte pass-through by software means, and any two optical interfaces can actually form a ring, but at a small switchover speed. This is not recommended unless no way is possible.
2005-3-3
Page 15 of 35
6) 7)
Twelve ring MS protection groups and forty linear MS protection groups are supported. Two minutes after successful configuration check and transmission, the MS protection groups will start automatically, and could be started with the command :cfg-start-rms: PgId; as well.
NE5
NE3
NE4
Figure 4-5 Figure 5 2-fiber bi-directional MS shared protection ring The configuration illustration is as follows (NE1): :lognew:"szhw","nesoft"; //:per-set-endtime:15m,1990@0@0@0@0@0; //:per-set-endtime:24h,1990@0@0@0@0@0; :cfg-init-all; :cfg-set-devicetype:OptiXOsn3500,standard; :cfg-set-nename:64,"DEMO"; :cfg-add-board:9&10,gxcsa:1,ssn1sep1:8&11,ssn2sl64:18,nscc; :cfg-add-rmspg:1,2fbi; :cfg-set-rmsbdmap:1,w1,8,1,1&&32; :cfg-set-rmsbdmap:1,e1,11,1,1&&32; :cfg-set-rmsattrib:1,1,5,2,600; :cfg-add-xc:0,1,1,1,0,8,1,1,0,vc4; :cfg-add-xc:0,8,1,1,0,1,1,1,0,vc4; :cfg-add-xc:0,1,2,1,0,11,1,1,0,vc4; :cfg-add-xc:0,11,1,1,0,1,2,1,0,vc4; :cfg-verify;
2005-3-3
Page 16 of 35
2005-3-3
Page 17 of 35
Because the relation between the protection channel and the working channel is determined for the 2-fiber bi-directional MS shared ring and needs no setting. For the 4-fiber ring, however, the indefinite slots result in the indefinite
2005-3-3 Huawei Confidential. No disclosure without permission. Page 18 of 35
correspondence between the working system and protection system, making setting necessary. 2) 3) The services need to be configured only to the working system. Refer to the related documentations for the protection principles of the 4-fiber ring.
working channels. Now five of them are mapped to the multiplex section and the others are reserved for future use. This is known as a partial multiplex section. After such configuration, the system will automatically treat the 9&&13 VC4 of SL16 as the protection channel for the working channel. Certainly, corresponding to the west, it is also necessary to map the 1&&5 VC4 to the multiplex section in the east. In the above illustration, what are the reserved 6&&8 VC4s for? They could be used to form chain configuration or SNCP configuration, thus realizing the sharing of different networking types in the same optical path. They could also be used to form another MS protection ring. Refer to the document OSN3500 Multiplex Section Descend and Multiplex Section Optical Path Shared Characteristics for detailed configurations. Evidently, the following configuration is also a partial multiplex section (the generated protection channel is 9&11&13&15): :cfg-set-rmsbdmap:1, w1, 7, 1, 1&3&5&7;
Figure 4-6 Figure 6 Circumscribed MS protection rings In the circumscribed point, configure two MS protection groups, map the corresponding optical interfaces to these two protection groups, and configure other NEs as multiplex section rings. The following is the configuration illustration of the circumscribed point: :lognew:"szhw","nesoft"; //:per-set-endtime:15m,1990@0@0@0@0@0; //:per-set-endtime:24h,1990@0@0@0@0@0; :cfg-init-all; :cfg-set-devicetype:OptiXOsn3500,standard; :cfg-set-nename:64,"DEMO"; :cfg-add-board:9&10,excsa:1,ssn1sep1:7&8&11&12,ssn2sl64:18,nscc; :cfg-add-rmspg:1,2fbi; :cfg-set-rmsbdmap:1,w1,7,1,1&&32; :cfg-set-rmsbdmap:1,e1,12,1,1&&32; :cfg-set-rmsattrib:1,1,4,2,600;
2005-3-3 Huawei Confidential. No disclosure without permission. Page 20 of 35
:cfg-add-rmspg:2,2fbi; :cfg-set-rmsbdmap:2,w1,8,1,1&&32; :cfg-set-rmsbdmap:2,e1,11,1,1&&32; :cfg-set-rmsattrib:2,5,8,6,600; :cfg-add-xc:0,1,1,1,0,7,1,1,0,vc4; :cfg-add-xc:0,7,1,1,0,1,1,1,0,vc4; :cfg-add-xc:0,7,1,3,0,11,1,3,0,vc4; :cfg-add-xc:0,11,1,3,0,7,1,3,0,vc4; :cfg-verify; The inter-ring services are protectable, and refer to the single multiplex section ring protection for their protection principles.
Figure 4-7 Figure 7 Intersected MS protection rings Figure 7 illustrates the intersecting of multiplex section rings. In the two intersected points, set two MS protection groups. The pass-through configuration of the inter-ring services in the intersected points has two following types: 1) In the principle of vicinity, select an intersected point of the two rings for inter-ring pass-through configuration. This is common configuration, because the two optical paths between the two intersected points are usually the same routes, which could break at the same time, avoiding frequent protection switchover. Configure in the same way as the circumscribed rings. Select one of the two intersected points, and configure all the inter-ring services between the two rings (acting like two circumscribed rings) to pass through this point.. Refer to the related documentations for detailed analysis of intersected rings.
2)
3)
2005-3-3
Page 21 of 35
2005-3-3
Page 22 of 35
4.11 SNCP
4.11.1 Service Configuration Principles
Known from Part 2 of this document Service Generation Principle, when SNCP is configured with the working routes of the services, the host will not automatically generate protection services, which are generated by NM according to the algorithm and then sent to the host, or the protection routes are sent to the host manually according to the ITU-T proposals. Thus, the SNCP configuration part is actually quite simple, and the complicated work is the application of the SNCP working and protection paths in the ITU-T proposals.
Figure 4-9 Figure 9 Schematic diagram of the SNCP ring-chain configuration Figure 9 illustrates an SNCP ring chain, where the slots 5 and 6 of NE1 form the SNCP ring, and the slot 1 ssn1sep1 is used for loading/unloading services. The configuration illustration is as follows:
2005-3-3 Huawei Confidential. No disclosure without permission. Page 23 of 35
:lognew:"szhw","nesoft"; //:per-set-endtime:15m,1990@0@0@0@0@0; //:per-set-endtime:24h,1990@0@0@0@0@0; :cfg-init-all; :cfg-set-devicetype:OptiXOsn3500,standard; :cfg-set-nename:64,"DEMO"; :cfg-add-board:9&10,excsa:1,ssn1sep1:5&6,ssn1sl16:18,nscc; :cfg-add-sncppg:1,rvt; :cfg-set-sncpbdmap:1,work,5,1,16,0,1,1,1,0,vc4; :cfg-set-sncpbdmap:1,backup,6,1,16,0,1,1,1,0,vc4; //Select service to receive. "work" for active, "backup" for standby :cfg-set-sncppgpara:1,rvt,600; :cfg-set-sncpattrib:1,work,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:1,backup,b3sd&hptim&b3exc,0; :cfg-add-xc:0,1,1,1,0,6,1,16,0,vc4; :cfg-add-xc:0,1,1,1,0,5,1,16,0,vc4; //Note that this is dually-transmitted service and it is not necessary to configure the "work" and "backup" attributes for SNCP//It should be configured only for selectively receiving. :cfg-verify;
2005-3-3
Page 24 of 35
:cfg-add-sncppg:1,rvt; :cfg-set-sncpbdmap:1,work,5,1,16,1,1,1,0,0,vc12; :cfg-set-sncpbdmap:1,backup,6,1,16,1,1,1,0,0,vc12; //Select service to receive"work" for active and "backup" for standby :cfg-set-sncpprotmode:1,pp :cfg-add-xc:0,1,1,1,0,6,1,16,0,vc4; :cfg-add-xc:0,1,1,1,0,5,1,16,0,vc4; :cfg-verify;
2005-3-3
Page 25 of 35
STM-64 ADM
11 12
STM-64 ADM
STM-64 ADM
Figure 4-10 Figure 10 Schematic diagram of shared fiber virtual path protection Figure 10 illustrates an STM-64 loop, with an STM-16 link in the middle, under the ordinary SDH loop protection. Obviously, since the STM-16 link fails to form a ring, the services on the chain could not be protected. However, from the angle of a channel loop, the optical path of STM-64 consists of four STM-16 channels in the channel structure, and it is possible to single out one STM-16 channel to form a ring with the STM-16 links. In practice, it is just as to virtualize an STM-16 half-ring in the STM-64 optical path to combine with the STM-16 link to form the STM-16 channel loop. In addition, it is feasible to set a protection mode to independently realize service transmit and protection loop functions. The original STM-64 loop continues to work independently and implement protection. The service interworking between the two loops are realized in the access node cross-connect matrix. In the STM-64 loop, the STM-64 optical path where the STM-16 channel loop is virtualized has only 3 STM-16 capacities left for the STM-64 loop. Furthermore, if the services needing loading/unloading on the STM-16 link are only n VC4s, it is workable to virtualize only a half ring with the bandwidth of n VC4s in this segment of the STM-64 optical path to combine with the corresponding n VC4s on the STM-16 link to form a channel loop with the bandwidth of n VC4s and realize independent protection. As a result, the services on the STM-64 loop that could be affected are only n VC4s. Features of the shared fiber virtual path protection The optical paths where various network holes intersect are divided logically into a combination of many channels. In the SDH equipment where various network holes intersect, the ADM mode is no longer based completely on optical paths, and could be treated as a combination of multiple channel layer ADMs. Each channel layer ADM realizes service loading/unloading and protection for the channel loop. Equipment requirements of the shared fiber virtual path protection First, the SDH equipment at a node must be able to provide multiple optical interfaces to meet complex networking requirements. Secondly, cross-connect capability must be sufficient. In complex networking, the nodes where multiple optical paths tandem may be required to virtualize several or more rings, and each ring could be a combination of different types of channels. Therefore, the SDH equipment that may serve as such a node must possess large capacity and cross-connect capability based on various levels of services.
2005-3-3 Huawei Confidential. No disclosure without permission. Page 26 of 35
4.12.2 Configuration Principles of Fiber Shared Virtual Path Protection of the OSN 3500/2500
Fiber Shared Virtual Path Protection of the OSN3500/2500 equipment is available in the following modes: 1) Define one part of VC4 on a segment of optical path in the MSP ring, and define the other part in the SNCP ring. The two parts of VC4 do not repeat each other and can provide respective protection for MSP and SNCP on the same segment of fiber, without mutual influence. This configuration actually uses the Partial Multiplex Section principle. In this configuration, it can be considered that there are two pairs of fiber in this span section, one for MSP protection, and the other for SNCP protection. Part of VC4 on this optical path is defined in both the MSP ring and the SNCP ring.
2)
In this mode, this part of VC4 are under dual protection: MSP protection and SNCP protection. Please note that the SNCP ring switchover will occur twice when the shared fiber breaks. First, the SNCP ring performs SNCP switchover, and then after the MSP ring performs switchover, the SNCP detection point detects that the signals in the invalid direction become OK, so the SNCP ring switches back to this direction. This is the second switchover. Please think it over. Therefore, it is necessary to use the command :cfg-set-sncpattrib to set the SNCP ring switchover delay time (longer than the actual multiplex section switchover time) to prevent two successive switchovers. 200ms would be OK (with a step of 100ms). However, if you want to test the SNCP switchover time, the delay time should not be set (set delaytime to 0), otherwise the switchover time would fail to meet the standard. On the shared fiber, any combination of the MSP and SNCP protection is possible, but could not be configured for the MSP attributes simultaneously, because one optical path can only provide one pair of K byte. (For 10G optical board, one single optical interface can support two groups of multiplex section rings)
:cfg-set-sncpbdmap:1,backup,12,1,2,0,1,2,1,0,vc4; //Selectively receiving of virtual ring SNCP :cfg-set-sncppgpara:1,rvt,600; :cfg-set-sncpattrib:1,work,b3sd&hptim&b3exc, 2; step of 100ms and the delay time is 200ms //Set delay time in the
:cfg-set-sncpattrib:1,backup,b3sd&hptim&b3exc, 2; //Set delay time :cfg-add-xc:0,1,1,1,0,8,1,1,0,vc4; :cfg-add-xc:0,8,1,1,0,1,1,1,0,vc4; :cfg-add-xc:0,1,2,1,0,8,1,2,0,vc4; SNCP :cfg-add-xc:0,1,2,1,0,12,1,2,0,vc4; ring SNCP :cfg-verify; //Dual transmitting of the virtual ring //Dual transmitting of the virtual
E point: Configure the pass-through route D F; F point: Configure the SNCP protection group, select the signals from E point and C point for reception; G point: Configure the pass-through route F H; H point: Configure to receive the signals from A point F H. The basic attribute of each NE is MSP. The A, B, C and D points form a MS protection ring, and the E, F, G and H points form another MS protection ring.
Figure 4-11 Figure 11 DNI structure networking of two MSP rings The D point configuration file is as follows: (note that the configuration file is actual an AH bi-directional service). :lognew:"szhw","nesoft"; //:per-set-endtime:15m,1990@0@0@0@0@0; //:per-set-endtime:24h,1990@0@0@0@0@0; :cfg-init-all; :cfg-set-devicetype:OptiXOsn3500,standard; :cfg-set-nename:64,"DEMO"; :cfg-add-board:9&10,gxcsa; :cfg-add-board:6,ssn1sl16:8&11,ssn2sl64:18,nscc; //Create multiplex section ring protection group :cfg-add-rmspg:2,2fbi :cfg-set-rmsbdmap:2,w1,8,1,1&&32; :cfg-set-rmsbdmap:2,e1,11,1,1&&32; :cfg-set-rmsattrib:2,0,3,1,600; //Configure inter-ring service (for dual-transmitting)
2005-3-3 Huawei Confidential. No disclosure without permission. Page 29 of 35
:cfg-add-xc:0,8,1,1&&8,0,11,1,1&&8,0,vc4; :cfg-add-xc:0,8,1,1&&8,0,6,1,1&&8,0,vc4; //Other services should be configured the same as that in the two-fiber multiplex section ring. It will not be repeated here. //Set SNCP protection group (selectively-receiving) :cfg-add-sncppg:1&&8,rvt; :cfg-set-sncpbdmap:1&&8,work,11,1,1&&8,0,8,1,1&&8,0,vc4; :cfg-set-sncpbdmap:1&&8,backup,6,1,1&&8,0,8,1,1&&8,0,vc4 :cfg-set-sncppgpara:1&&8,rvt,600; :cfg-set-sncpattrib:1,work,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:1,backup,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:2,work,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:2,backup,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:3,work,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:3,backup,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:4,work,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:4,backup,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:5,work,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:5,backup,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:6,work,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:6,backup,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:7,work,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:7,backup,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:8,work,b3sd&hptim&b3exc,0; :cfg-set-sncpattrib:8,backup,b3sd&hptim&b3exc,0; :cfg-verify; C and E have similar services, and only the C point configurations are given here: //Install Boards ...... //Create multiplex section ring protection group :cfg-add-rmspg:2,2fbi :cfg-set-rmsbdmap:2,w1,8,1,1&&32; :cfg-set-rmsbdmap:2,e1,11,1,1&&32; :cfg-set-rmsattrib:2,1,0,2,600; //Configure the pass-through service :cfg-add-xc:0,8,1,1&&8,0,6,1,1&&8,0,vc4; :cfg-add-xc:0,6,1,1&&8,0,8,1,1&&8,0,vc4; //Verify :cfg-verify;
2005-3-3 Huawei Confidential. No disclosure without permission. Page 30 of 35
F point configuration file: :lognew:"szhw","nesoft"; //:per-set-endtime:15m,1990@0@0@0@0@0; //:per-set-endtime:24h,1990@0@0@0@0@0; :cfg-init-all; :cfg-set-devicetype:OptiXOsn3500,standard; :cfg-set-nename:64,"DEMO"; :cfg-add-board:9&10,gxcsa; :cfg-add-board:6,ssn1sl16:8&11,ssn2sl64:18,nscc; //Set multiplex section protection group :cfg-add-rmspg:1,2fbi :cfg-set-rmsbdmap:1,w1,8,1,1&&32; :cfg-set-rmsbdmap:1,e1,11,1,1&&32; :cfg-set-rmsattrib:1,0,3,1,600; //Set SNCP protection group :cfg-add-sncppg:1&&8,rvt; :cfg-set-sncpbdmap:1&&8,work,6,1,1&&8,0,8,1,1&&8,0,vc4; :cfg-set-sncpbdmap:1&&8,backup,11,1,1&&8,0,8,1,1&&8,0,vc4; :cfg-set-sncppgpara:1&&8,rvt,600; :cfg-set-sncpattrib:1,work,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:1,backup,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:2,work,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:2,backup,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:3,work,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:3,backup,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:4,work,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:4,backup,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:5,work,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:5,backup,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:6,work,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:6,backup,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:7,work,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:7,backup,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:8,work,b3sd&hptim&b3exc,100; :cfg-set-sncpattrib:8,backup,b3sd&hptim&b3exc,100; //Set dual-transmitting service
2005-3-3 Huawei Confidential. No disclosure without permission. Page 31 of 35
65535
BCSUM represents the broadcast service types. The value 1 indicates non-broadcast service, 2 indicates a broadcast service with one origin and two homes, 3 indicates a broadcast service with one origin and three homes, and so on.
C-4 (149760Kbit) appear in the data communication services. To enable the STM-4-4C concatenation services to be transmitted by the SDH equipment, the concatenation mode is feasible. Concatenation is a process of combination, which combines multiple virtual containers to serve as a single container with bit sequence integrity due to their increased combined capacity. VC-4 concatenation is to combine X C-4 containers to form a large container to meet the requirement of large-capacity customer signal transmit beyond C-4. Concatenation is divided into adjacent concatenation and virtual concatenation. The adjacent concatenation is to use adjacent C-4 concatenations to form VC-4-Xc as an integral structure for transmission. The adjacent concatenations in the transmission travel through the same physical paths. The virtual concatenation is to combine the VC-4s (possibly in the same route or not) distributed in different STM-Ns to form a virtual large-structure VC-4-Xv for transmission. In the virtual concatenation, since the transmission of each VC-4 travels through different paths, transfer delay difference may occur between each VC-4 after reaching the home terminations. In extreme cases, the VC-4s with larger sequence numbers reach the home terminations earlier than those VC-4s with smaller sequence numbers, thus making it difficult to restore customer signals. Each circuit board can realize VC-4-4c, VC-4-8c, VC-4-16c and VC-4-64c concatenation services based on its own capacity.
CC represents the concatenation service types. The value 1 indicates non-concatenation services, 4 indicates au4-4c services, 8 indicates au4-8c services, and 16 indicates au4-16c services.
The slot 16 is for a protection board. The working slot is 13&&15, realizing 1:3 protection. As long as the protection and working slots do not conflict, multiple protection groups can co-exist. The TPS protection slots can also configure extra services, which would be overlaid after switchover. For detailed configuration principles, refer to the document Protection Characteristics of the OSN3500 and 2500 Electric Interface Board Level.
:cfg-set-tpsbdmap: 1, 0, 1; //The slot 1 is mapped as the protection unit of the protection group 1 (fixed) :cfg-set-tpsbdmap: 1, 1, 2; //The slot 2 is mapped as the work unit 1. :cfg-set-tpsbdmap: 1, 2,.3; //The slot 3 is mapped as the work unit 2. :cfg-set-tpsbdmap: 1, 3, 4; //The slot 4 is mapped as the work unit 3. :cfg-set-tpsbdmap: 1, 4,5; :cfg-set-tpswtrtime:1,600; //The slot 5 is mapped as the work unit 4.
Pid port number: 1-X. X is determined by the type of the board installed in this slot. Hardreg Enable Disable
2005-3-3
Page 35 of 35