Configuring and Supervising Physical Interfaces for Ipa Rnc

Nokia Networks

WCDMA RAN, Rel. WCDMA 16, Operating Documentation, Issue 03 Configuring and Supervising Physical Interfaces for IPARNC DN03549536 Issue 13A Approval Date 2014-08-22

Configuring and Supervising Physical Interfaces for IPA-RNC

The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof. The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY AVAILABILITY,, ACCURACY, ACCURACY, RELIABILITY, RELIABILITY, TITLE, NON-INFRINGEMENT NON-INFRINGEMENT,, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION INFORMATION IN IT, IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © 2016 Nokia Solutions and Networks. All rights reserved.

f

Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for any additional information.


The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof. The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY AVAILABILITY,, ACCURACY, ACCURACY, RELIABILITY, RELIABILITY, TITLE, NON-INFRINGEMENT NON-INFRINGEMENT,, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION INFORMATION IN IT, IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © 2016 Nokia Solutions and Networks. All rights reserved.

f

Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for any additional information.


Table of Contents This document has 31 pages Summary of changes..................................................................... 6 1 1.1 1.2 1.2.1 1.2.2 1.2 .2 1.2.3 1.2 .3 1.2.3.1 1.2.3 .1 1.2.3.2 1.2.3 .2 1.2.3. 1.2 .3.3 3 1.2.3. 1.2 .3.4 4 1.2.4 1.2 .4 1.2.4.1 1.2.4 .1 1.3 1.4 1. 4

Physical interfaces in the RNC....................................................... RNC.......................................................7 7 Physical interfaces in IP/ATM networ k........................................... k........................................... 7 Standards and specificat specifications ions related related to to the RNC physical interfaces......................................................................................10 interfaces...................................................................................... 10 Ethernet........................................................................................11 Ethernet........................................................................................1 Laser La ser... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ...... ....... ......1 ..11 1 SDH... SDH ...... ....... ....... ...... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ......11 ...11 ANSI.. ANS I..... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...1 11 Bellco Bel lcore. re.... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...11 ITU-T. ITU -T.... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ... 11 TTC JT. JT.... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ..... 12 Statis Sta tistic tics.. s..... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ...... ....... ....... ...... ......12 ...12 ITU-T. ITU -T.... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...... ...... ...... ...... ...... ....... ....... ...12 12 Physical layer Trail Termination Poin Pointt (phyTTP).......................... 12 Func Fu ncti tion onal al st stat ate e ha hand ndli ling ng fo forr ATM ne netw twor ork k in inte terf rfac ace e un unit its s .. .... .... .... ....13 ..13

2 2.1 2.2 2.3 2. 3

Faultt ma Faul mana nage geme ment nt.. .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .. 15 SDH supervision supervision.......................................................................... .......................................................................... 15 15 Ethernet supervision.................................................................... 16 16 Phys Ph ysic ical al la laye yerr re reso sour urce ce is de deta tach ched ed fr from om th the e ne netw twor ork k in inte terf rfac ace e unit............................................................................................... 17 unit............................................................................................... 17

3 3.1 3.2 3. 2 3.3 3. 3 3.4 3. 4

Configuring interfaces.................................................................. Configuring interfaces..................................................................20 20 Configuring Configurin g SDH for ATM transpor transport.............................................. t..............................................20 20 Crea Cr eati ting ng SD SDH H pr prot otec ecti tion on gr grou oup. p... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... 21 Crea Cr eati ting ng ph phyT yTTP TP fo forr ATM TM... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... ....2 ..23 3 Movi Mo ving ng ph phyT yTTP TP in ATM TM.. .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... .... .... .... .... .... .... .... .... .... ..... ..... 25

4 4.1 4. 1 4.2 4. 2 4.3 4. 3

Physic Phys ical al in inte terf rfac aces es pe perf rfor orma manc nce e mo moni nito tori ring ng.. .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 28 ATM in inte terf rfac ace e me meas asur urem emen entt sh show ows s tr tran ansm smis issi sion on er erro rors rs.. .... .... .... .... .... .... 28 STMST M-1 1 in inte terf rfac ace e me meas asur urem emen entt sh show ows s tr tran ansm smis issi sion on er erro rors rs.. .... .... .... ....28 ..28 SONE SO NET/ T/SD SDH H pr prot otec ecti tion on gr grou oup p me meas asur urem emen entt sh show ows s tr tran ansm smis issi sion on errors............................................................................................30


List of Figures Figure 1

Physical interfaces for SDH and IP over Ethernet transmission...........7

Figure 2

SDH layers........................................................................................... 8

Figure 3

Physical interfaces supervision for ATM traffic..................................... 9

Figure 4

Physical interfaces in the RNC...........................................................10

Figure 5

Physical layer Trail Termination Point (phyTTP) for an ATM interface... 12


List of Tables Table 1

SDH interfaces..................................................................................... 8

Table 2

SDH alarms available via alarm system ............................................15

Table 3

Ethernet alarms.................................................................................. 17

Table 4

Parameters and values for creating phyTTP...................................... 24

Summary of changes


Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues. Note that our issue numbering system, safety information, and product naming practice are changing. For more information, see Guide to WCDMA RAN Operating Documentation. Change between Issue 13 (2014-02-16, RU50) and 13A (2014-08-22, RU50) Physical interfaces in the RNC (1) The following chapters are deleted: • • • •

ATM over SDH SONET interface Transmission Convergence sublayer (TC) IP over Ethernet

Change between Issue 12A (2011-06-06, RU30) and 13 (2014-02-16, RU50) NIP1, NIS1 related information is removed from this document. Change between Issue 12 ( 2011-03-09, WCDMA RAN RU30) and 12A (2011-06-06, WCDMA RAN RU30) The product name is changed from RNC to IPA-RNC in the document title.


Physical interfaces in the RNC

1 Physical interfaces in the RNC 1.1 Physical interfaces in IP/ATM network Physical interfaces are used for connecting the network element to external transmission networks. They provide the means of executing a physical layer functionality, such as operation and maintenance (O&M) , asynchronous transfer mode (ATM) and timedivision multiplexing (TDM) traffic mapping to the transmission frame structure of synchronous digital hierarchy (SDH) , or Ethernet. A network interface unit includes one or more physical interfaces depending on the unit type. Figure 1

Physical interfaces for SDH and IP over Ethernet transmission

NPS1P

STM-1/VC-4 ATM

NPS1

MXU

SFU NPGEP NPGE

Optical/Electrical Gigabit Ethernet

RNC provides the following physical interface types: • •

STM-1 (VC-4) SDH ATM interfaces Electrical and optical Gigabit Ethernet interfaces

SDH interfaces Synchronous Digital Hierarchy (SDH) is a transfer mode in which there are specified limits to the timing relationship of the corresponding significant instants of a signal. SDH forms the basis of transport especially in backbone networks. SDH interfaces are used for connecting the network element to SDH-based IP/ATM networks. SDH is divided into three different layers: Regenerator Section, Multiplex Section, and Path. There are two different levels of paths depending on the interface type, higher order path and lower order path. Lower order paths, when used, are multiplexed to the higher order paths and higher order paths are multiplexed to the multiplex section.



SDH layers

Figure 2

SDH

SDH

Multiplexer

Regenerator

Multiplexer

Regenerator

Regenerator

Section

Section

Multiplex

Multiplex

Multiplex

Section

Section

Section

Path

t

Tip: In Synchronous Optical Network (SONET), the layers are section (regenerator section), line (multiplex section) and path. For the differences in terminology, see SONET interface. The higher order path numbering scheme refers to the higher order virtual container, VC4. From the SDH transmission network point of view, the RNC is equal to the Terminal Multiplexer presented in the figure SDH Layers. The RNC provides optical single mode fibre STM-1 interfaces. The transmission medium consists of two single-mode fibres, one for each direction. Table 1

SDH interfaces

Interface type

STM-1 optical (ITU-T G.957, table 1)

Bit rate

155 520 kbit/s

Mapping

VC-4 (capacity 149 760 kbit/s)

Multiplexing

VC-4: Multiplexing directly from container-4 using AU-4 to STM-1 (ITU-T G.707, figure 6-5, December 2003, ETSI EN 300 147 v1.4.1, May 2001 and ANSI T1.105-2001).

Nominal wavelength (nm)

1310

Medium

G.652 optical fibre (SM)

Connectors

LC

OAM F3

I.432.2 / G.707 POH


Table 1


SDH interfaces (Cont.)

Interface type

STM-1 optical (ITU-T G.957, table 1)

OAM F2

I.432.2 / G.707 SOH

OAM F1

I.432.2 / G.707 SOH

Transmission protection

Multiplex section protection supported

The RNC provides high bit rate SDH STM-1 ATM interfaces. SDH transmission protection and SDH interface unit protection are provided. For more information, see Multiplex Section Protection and SDH NIU redundancy in WCDMA RAN network protection. Synchronous Optical Network (SONET) is, like SDH, a transfer mode that is designed to run on an optical fiber. SONET is standardised by ANSI and used in the United States and Canada. It is a variation of the SDH international standard. Ethernet interfaces The RNC also provides Ethernet interfaces towards IP networks for IP over Ethernet connections. The interfaces include optical and electrical Gigabit Ethernet interfaces. Physical interfaces supervision In ATM traffic, the physical layer supervises the Physical Layer Trail Termination Point (phyTTP). In fault situations affecting ATM traffic, the physical layer informs the ATM OAM, and the operational state of the ATM interface is changed. The physical layer also collects statistics on the disturbances detected on the Transmission Convergence (TC) sublayer . Figure 3

Physical interfaces supervision for ATM traffic

AAL Layer ATM Layer

Physical Layer

Transmission Convergence Sublayer

Physical Medium Sublayer

Traditional TC

SDH STM-1

For more information on SDH statistics, see Transmission quality measurements. The Ethernet network interface units contain functionality to supervise the link state of all Ethernet interfaces on that unit. Alarms are set and reset correspondingly. Network interface units



The system makes decisions on setting and cancelling alarms and collects disturbance statistics according to the information it receives from the network interface units (NIU). NIUs are functional units controlling the exchange terminals. There are 2 types of NIUs for the SET exchange terminals: NPS1 and NPS1P. Each NIU includes 8 of these physical interfaces (exchange terminals), SETs, which can be configured to be used in different interfaces of the RNC. For example, the network interface units NPS1 and NPS1P are used in the Iu interface. NIUs connect physical interfaces to the supervising signalling computer units through ATM Multiplexer units (MXU) and the ATM Switching Fabric Unit (SFU). There is also one type of a network interface unit for the Ethernet connections. Each NIU includes an Ethernet interface, which can be configured to be used for connecting the RNC to IP networks. The various physical interfaces available in the RNC are presented in the following figure. Figure 4


For more information on the network interface units, see WCDMA RNC Engineering Description and the plug-in descriptions available in NOLS.

1.2 Standards and specifications related to the RNC physical interfaces Here are the most relevant specifications from the RNC physical interfaces point of view. There may be some variations between the specifications and the way the system supports the specifications. This is not a protocol implementation conformance statement.


1.2.1

Ethernet •

•

1.2.2

IEEE Std 802.3 Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications. The Institute of Electrical and Electronics Engineers, Inc. 2000. IEEE Std 802.1Q Virtual Bridged Local Area Networks. The Institute of Electrical and Electronics Engineers, Inc. December 1998.

Laser •

IEC 825-1 (1993) Safety of Laser Products: Equipment classification, requirements, and user's guide

1.2.3

SDH

1.2.3.1

ANSI • • • • •

1.2.3.2

T1.105-1995 Synchronous Optical Network (SONET) - Basic description including Multiplex Structure, Rates, and Formats T1.105.01-2000 Synchronous Optical Network (SONET) - Automatic Protection Switching T1.105.02-2001 Synchronous Optical Network (SONET) - Payload mappings T1.231-1997 Digital Hierarchy Layer 1 In-Service Digital Transmission Performance Monitoring T1.269-2000 Information Interchange - Structure and Representation of Trace Message Formats for the North American Telecommunications System

Bellcore •

1.2.3.3


GR-253-CORE (09/2000) Synchronous Optical Network (SONET) Transport Systems: Common Generic Criteria

ITU-T • • • • • • • • •

G.707/Y.1322 (10/2000) Network node interface for the Synchronous Digital Hierarchy (SDH) G.783 (02/04) Characteristics of Synchronous Digital Hierarchy (SDH) equipment functional blocks G.784 (6/99) Synchronous Digital Hierarchy (SDH) management G.806 (02/02) Characteristics of transport equipment – Description methodology and generic functionality G.841 (10/98) Types and characteristics of SDH network protection architectures G.957 (7/97) Optical interfaces for equipments and systems relating to the synchronous digital hierarchy G.958 (11/94) Digital line systems based on the synchronous digital hierarchy for use on optical fibre cables I.432.2 (2/99) B-ISDN user-network interface - physical layer specification: 155 520 kbit/s and 622 080 kbit/s I.610 (11/95) B-ISDN operation and maintenance principles and functions


1.2.3.4

TTC JT • • •

1.2.4 1.2.4.1


JT-G707 (04/97) Network Node Interface for Synchronous Digital Hierarchy JT-G783 (4/98) Maintenance Signal and Protection Switching Behaviour of Synchronous Digital Hierarchy (SDH) Multiplexing Equipment JT-I432.4 (4/97) B-ISDN user-network interface - physical layer specification for 155 520 kbit/s and 622 080 kbit/s

Statistics ITU-T •

• •

G.821 (08/96) Error performance of an international digital connection operating at a bit rate below the primary rate and forming part of an integrated services digital network G.826 (08/96) Error performance parameters and objectives for international, constant bit rate digital paths at or above the primary rate G.829 (12/2002) Error performance events for SDH multiplex and regenerator sections

1.3 Physical layer Trail Termination Point (phyTTP) Physical layer Trail Termination Point (phyTTP) is used for hiding the properties of the physical resources from the upper protocol layers. It is configured between the physical layer and the ATM layer. A phyTTP ID is given when configuring the ATM interface. The phyTTP can be used to transport the protocol data units of the upper layer, for example ATM cells. Configure the phyTTP after having configured the SDH or PDH interfaces. The MML for creating phyTTP includes a parameter, payload type, for separating ATM traffic from PPP traffic. However, only ATM traffic is supported in this release. The physical layer supervises the phyTTP for detecting failures in ATM transmissions. For more information, see Physical interfaces supervision. Figure 5

Physical layer Trail Termination Point (phyTTP) for an ATM interface

Related topics



Instructions Creating phyTTP for ATM Descriptions Physical interfaces in IP/ATM network

1.4 Functional state handling for ATM network interface units This chapter describes the functional unit state affects to different hierarchical network interface unit types and the functional unit state differences between hierarchical levels. The functional state of the different levels have different affects to the usability of the resources and to the transmission network traffic itself. Operation of SET in different states of the parent unit Parent unit of SET can be one of following: • •

NPS1 NPS1P

The state of the parent unit affects to all traffic of SETs. You can use SDH interfaces for traffic only when their parent units are in WO/SP state. When the functional unit state is TE, there are some differences how the transmission network sees the unit state between different parent units. Spare NPS1P in TE state requests remote end or ends to switch traffic to the sections of protection group in the WO unit. In ATM interface units, when the parent unit state is not WO-EX, the state of phyTTP will be disabled in non-redundant units. In 2N redundant units, the state of phyTTP depends on the state of protection group. For SDH transmission protection, when the pair units of NPSIP is not in SP-EX state, multiplex sections of SETs in the pair units are in signal fail condition. When the parent unit state is not in WO-EX or SP-EX, SDH alarms are not set and SDH related statistical measurements are not collected. You can configure SDH parameters regardless of the state of the parent unit. Operation of SET in different states In current release, the state of SET does not affect traffic, but the state of the parent does. You can disable a single SDH interface by these instructions: • •

When you create ATM interface on top of a single SET, related ATM interface can be locked by MML command LAS. Locked ATM interface is not used for new calls. When SET is a part of the SDH protection group, you can use the MML command YWF to force the traffic to the specific SDH interface. The other interface is out of use in this way.

The state of the SET does not affect phyTTP state or SDH transmission protection. So MSP 1+1 can continue working normally.



When the state of SET is not in WO-EX, SDH alarms are not set and SDH related statistical measurements are not collected. You can configure SDH parameters regardless of the state of the SET.


Fault management

2 Fault management 2.1 SDH supervision The physical layer takes care of the operations and maintenance functionality for optical SDH interfaces. Fault management and performance management functions related to OAM flows F1, F2, and F3 are also covered. Most of the functions of the physical layer OAM are implemented by hardware, which provides the Section Overhead (SOH) and Path Overhead (POH) bytes handling, regenerator section, multiplex section, path-level alarm detection, and performance monitoring. Software is used to initialise and monitor hardware and to provide accessdependent failure indications for alarm system, network management, and ATM layer management. The functionality is activated automatically by the system when the state of the SDH exchange terminal (SET) is changed into WO-EX. Note that SETs do not have the operational state SP-EX. When the operational state of the functional unit is SP-EX, the state of the SET is WO-EX. When the operational state of the functional unit is TE-EX, no alarms will be set. SDH alarms are set to the alarm system on different levels. NetAct uses the alarms listed in the following table. Table 2

SDH alarms available via alarm system

Fault name (alarm number)

SPI

Transmit Fail TF (2784)

X

Optical Module Detached (3364)

X

Optical Module Faulty (3365)

X

Loss of Signal LOS (3900)

X

Loss of Frame LOF (3902)

RS

MS

X

Loss of Pointer LOP (3903) Remote Defect Indication RDI (3906, 3907)

X X

Signal Label Mismatch SLM (2937) Alarm Indication Signal AIS (2938, 3905)

Path HOVC

X

X

X

Path LOVC

TU

Fault management

Table 2


SDH alarms available via alarm system (Cont.)


SPI

RS

MS

Unequipped SDH VC Signal (3941) X

Incoming SDH Signal Degraded (3979)

X

g

Path LOVC

TU

X

Excessive Errors in Incoming SDH Signal (3964)

Incorrect Tranceiver Type (3999)

Path HOVC

X

SPI

Synchronous Physical Interface

RS

Regenerator Section

MS

Multiplex Section

HOVC

Higher Order Virtual Container

LOVC

Lower Order Virtual Container

TU

Tributary Unit

Note: The protection group provides protection against a traffic cut when the alarm (2784, 3900, 3902, 2938, 3964, or 3979) is set for only one of the SETs in the protection group. Related topics Instructions Configuring SDH for ATM transport Descriptions ATM over SDH Transmission quality measurements

2.2 Ethernet supervision Ethernet driver supervises only those IP over Ethernet interfaces whose administrative state is UP. IP packets are not sent to IP addresses with administrative state DOWN. Ethernet failure alarms and their definitions are presented in the following table.


Table 3

Fault management

Ethernet alarms


Definition

BFD Link Failure (2878)

Bidirectional Forwarding Detection (BFD) protocol has failed. This alarm is used on the Iub and Iur interfaces.

Ethernet interface faulty (3239)

The interface under supervision is faulty or the Ethernet cable is disconnected.

Ethernet connectivity lost (3240)

The Ethernet connectivity of a 2N redundant or a non-redundant unit under supervision is lost.

Ethernet interfaces out of All the interfaces of a non-redundant unit, which are under supervision, are out of use (3277) use. Optical module missing (3364)

An optical module is missing.

Optical module faulty (3365)

An optical module is faulty.

Tx Power Level Decreased (3378)

The power level of the transmission has decreased.

Incorrect Tranceiver Type (3999)

The type of the tranceiver is incorrect.

g

Note: Alarms 3239 and 3240 cause a traffic cut. If the unit is 2N redundant, it also performs a switchover to the spare unit. Related topics Instructions Configuring IP parameters and addresses of interfaces Descriptions IP over Ethernet

2.3 Physical layer resource is detached from the network interface unit The alarm 3372 PHYSICAL LAYER RESOURCE DETACHED FROM NETWORK INTERFACE UNIT indicates that a physical layer resource has been detached from the physical interface. The alarm has two supplementary information fields: RESOURCE_TYPE and RESOURCE_ID which give more detailed information about the resource which has been detached.

Fault management


A physical layer resource can become detached due to the following two reasons: • •

a network interface unit has been removed from the configuration a phyTTP has been manually detached with the MML command YDR

The resource is detached automatically from the network interface unit when the unit is removed from the configuration with the equipment management MML command WFV. The resource can also be detached with the physical layer trail termination point handling MML command YDR. Before that the main state of the target unit has to be changed to SE with the unit administration MML command USC. The alarm is typically related to a hardware upgrade, when the network interface units are replaced with new units. The detaching and attaching of the phyTTP is utilized for reusing the existing resources in the new interface unit. The physical layer logical resource which is based on the phyTTP may also have ATM layer resources created on top of it. These ATM resources and the related virtual connections, and/or signalling links, will remain in the system, but they will be in the disabled state after the phyTTP has been detached. A reusable (RESOURCE_TYPE = 01 or 02) detached physical layer logical resource can be attached to the new network interface unit with the physical layer trail termination point handling MML command YDS. When the state of the new network interface unit is changed to WO, with the unit administration MML command USC, the resources and the related connections are automatically taken into use. The resource type of the detached resource can be one of following: •

01 physical layer trail termination point (phyTTP) based on a SET unit

•

02 phyTTP based on protection group In the case of resource types 01 and 02, the reusable detached physical layer logical resources can be attached with the MML command YDS. The resources which can be attached this way are the phyTTP which is based on a SET or the phyTTP which is based on a protection group. The alarm is cancelled automatically when the phyTTP is attached to a new physical interface. When this kind of a reusable resource is attached to a new network interface unit with the MML command YDS and the state of the unit is changed to WO with the MML command USC, the possible ATM interfaces and virtual connections, and/or signalling links (related to the reusable physical layer logical resource), are taken into use automatically. For more information on attaching a resource, see Moving phyTTP in ATM . A reusable resource can be removed, if there is no need to reuse it, that is, to attach it. The removal is executed with the MML command YDD in which case the alarm is cancelled automatically. The supplementary information field RESOURCE_ID indicates the id of the detached phyTTP.

•

05 protection group without a phyTTP created on top of it An alarm will not be raised in this case. If the unit to which the protection group is related to is removed and there is no phyTTP on top of the protection group, the protection group will be removed automatically by the system. In the case of 2N redundant unit NPS1P, the related protection groups will be removed when both units have been removed.

•

07 SET index of a section of a protection group


Fault management

The SET index of a section of a protection group will be attached automatically when the spare unit of the protected network interface unit has been created into the configuration with the MML command WFU. The alarm will then be cancelled automatically. The supplementary information field RESOURCE_ID indicates the protection group from which the section is missing. •

08 phyTTP based on a SET or a protection group with a SET in VC-3, VC-11 over VC-3, VC-12 over VC-3, VC11 over VC-4, or VC-12 over VC-4 mapping mode If the network interface unit which has a phyTTP based on a SET or a protection group with a SET in any other mode than VC-4 is removed from the configuration with the MML command WFV, the phyTTP will not detached (even if the alarm will be set). The alarm will be cancelled automatically when phyTTP has been deleted with the MML command YDD or the network interface unit has been created back into the configuration with the MML command WFU. The supplementary information field RESOURCE_ID indicates the phyTTP, which cannot be related to any unit because the unit is missing from the configuration.

Related topics Descriptions Physical layer Trail Termination Point (phyTTP)

Configuring interfaces


3 Configuring interfaces 3.1 Configuring SDH for ATM transport Purpose This procedure describes how to configure the SDH/ATM interface and modify the SDH exchange terminal (SET) configuration. You can define how the transmission capacity is divided, and change the threshold levels for performance monitoring to meet the expected quality of the transmission network. Before you start You must create the functional unit description for the SETs. For instructions, see Creating and attaching functional unit description in Hardware Configuration Management . Procedure

1

Interrogate the SET (YAI) With the following command you can find out the current exchange terminal configuration. ZYAI:,;

2

If you want to modify the default settings, configure the SET (YAN)

t

Tip: When VC mapping is changed, the affected higher and lower order paths are set to their default values. Note that for the NPS1, and NPS1P units, only one loopback status (diagnostic or line) can be active at a time. Currently the SES BIP, SD BER, and SF BER parameters are not used for the higher or lower order paths. The SES BIP threshold for the higher order paths is the same as the one used for the multiplex section of the SET. The following parameter values are irrelevant to the ATM traffic: • •

mapping mode parameter values VC4VC11 and VC4VC12 payload mapping mode parameter values ASYNCH, BITSYNCH, and BYTESYNCH

ZYAN:...,[|,]:[]:[]:[]:[DIA=(ON|OFF)|LINE=(ON|OFF)|LASER=(ON|OFF)] ...:[VC4|VC4VC11|VC4VC12]:[SDH|ATMML|SONET] :[ASYNCH|BITSYNCH|BYTESYNCH];


3


Set the SDH trace (YAS) You can set the SDH trace already during integration or later on, if necessary. The SDH trace trail must be configured identically to both trails related to a specific phyTTP (logical path) in a protection group. When you configure a trace for a trail that is part of a protection group, the system automatically applies the changes to the other trail of the pair and sends a notification on this.

t

Tip: Trace types EXPPATH and EXPREG are not currently supported. ZYAS:,[|,]:(OUTPATH|EXPPATH|OUTREG|EXPREG) ,(RESET|SET1|SET16|SET64),;

For more information on the trails, see Creating SDH protection group.

4

Create SDH protection group, if necessary If you want to secure the traffic even when a line fails, you need to create an SDH protection group. See instructions in Creating SDH protection group.

5

Create phyTTP See instructions in Creating phyTTP for AT M .

Example:Configuring SDH for ATM transport 1.

Modify the SES BIP threshold of the SET 1 to 2300 frames per second. ZYAN:1:2300;

2.

Modify the outgoing path trace of the VC path 1 of SET 1. Use the 16-byte format. ZYAS:1,1:OUTPATH,SET16,"OUT PATH TRACE";

Further information You can interrogate the incoming SDH traces with command YAT.

3.2 Creating SDH protection group Purpose You can create a protection group which is formed by two SDH exchange terminals (SET). Multiplex Section (MS) trail linear protection is used to protect a single multiplex section trail by replacing a working MS trail if the working trail fails or if the performance falls below the required level. The supported protection protocols are: • •

linear, bidirectional Multiplex Section Protection (MSP) 1+1 compatible with 1:n protocol, and linear, bidirectional Automatic Protection Switching (APS) 1+1.



NPS1P also support unidirectional MSP 1+1 and unidirectional APS 1+1. Both protocols can be used either in revertive or in non-revertive mode. The SDH trace trail must be configured identically to both trails related to the same logical path in a protection group. Otherwise, the system prevents the protection group creation. Procedure

1

Create SDH protection group (YWC) ZYWC:[| def],[|NONREV def],[|MSP def],[|B def]:,:[|300 seconds def];

For NPS1P, you must configure the resources identically. For example, if you choose the third SET of one unit for the protection group, you must choose the third SET also of the other unit.

2

Create Terminal Point, if necessary For protected SDH interfaces which are used for ATM traffic transport, you need to create Physical Trail termination point (phyTTP). See the instructions for creating the Physical layer Trail Termination Point in Creating phyTTP for ATM .

Expected outcome The system generates the 0101 SDH PROTECTION SWITCHING EXECUTED notice if the protection switch operation succeeds. Unexpected outcome The system generates the 3183 SDH PROTECTION SWITCHING FAILED alarm if the protection switch operation fails. If the far end has not been configured to support the correct SONET APS configuration, the system generates the 3307 MISMATCH IN SONET APS CONFIGURATION alarm. If the far end of the protected multiplex section is not able to use the protection section, the system generates the 3334 FAR END PROTECTION SECTION FAILURE alarm.

Example:Configuring SDH protection group with default protection protocol parameter values 1.

Create a protection group of SET 12 (working section) of NPS1P-1 and SET 4 (protection section) of NPS1P-0 with protection group ID 3. The default protection switching mode, bidirectional non-revertive, and protocol variant MSP 1+1 are used. ZYWC:3,,:12,4:;



Example:Configuring SDH protection group with SONET APS variant of the protection protocol and with revertive mode 1.

Create a protection group of SET 8 (working section) and SET 9 (protection section) of NPS1-0 with protection group ID 4. Revertive mode and APS 1+1 variant are used. Default of wait to restore time is used. ZYWC:4,REV,APS:8,9;

Example:Configuring SDH protection group with MSP 1+1 unidirectional protection protocol and with non-revertive mode 1.

Create a protection group of SET 16 (working section) and SET 32 (protection section) of NPS1P with protection group ID 5. Non-revertive mode, MSP 1+1 variant and unidirectional operation mode are used. ZYWC:5,NONREV,MSP,U:16,32;

Further information You can interrogate the protection group configuration and protection switching status information with the YWI command, modify the configuration with the YWM command, and delete the configuration with the YWD command. Note that a protection group cannot be deleted if a phyTTP has been created for it. Related topics Descriptions ATM over SDH

3.3 Creating phyTTP for ATM Purpose The Physical layer Trail Termination Point (phyTTP) is configured between the physical layer and the ATM layer. The phyTTP ID is used when creating the ATM interface. You can create a phyTTP for a single PDH exchange terminal (PET), an IMA group, a single SDH VC path, or a VC path of an SDH protection group.

g

Note: You cannot create a phyTTP for a single SDH VC path of a 2N redundant network interface unit. The phyTTP for a 2N redundant unit must be created for the VC path of the SDH protection group that has been created for the unit. Before you start You must configure the SDH interfaces (SET, a single SDH VC path or a VC path of an SDH protection group) before you can create the phyTTP for them. For configuration instructions, see Configuring SDH for ATM transport .



If you need to interrogate the phyTTP configuration or the operational state of the phyTTP, use the YDI command. Procedure

1

g

Create a physical layer Trail Termination Point (YDC) Note: The MML command for creating the phyTTP includes a parameter, payload type, for separating ATM traffic from PPP traffic. However, only ATM traffic is supported in this release. ZYDC::(PET=|IMA=|SET= |PROTGROUP= ):[|def]:[ATM def|PPP],[ON def|OFF];

Table 4

Parameters and values for creating phyTTP

Parameter

Value

If you are creating phyTTP to a SET: SET

index of the SET

VC path number

VC path number

If you are creating phyTTP to an SDH protection group: PROTGROUP

ID of the protection group

VC path number

VC path number

Example:Creating a phyTTP for a SET Create a phyTTP with ID 1 of the SET with index 0 and VC path number 1. ZYDC:1:SET=0:1:;

Example:Creating a phyTTP for an SDH protection group Create a phyTTP with ID 4 for path 1 of protection group 4. ZYDC:4:PROTGROUP=4:1:;

Further information You can delete a phyTTP with the YDD command. After the deletion, its physical resources are free to be used again; for example, you can protect SET by creating a protection group. On the other hand, protection group can be deleted if there is no phyTTP related to it.



The phyTTP cannot be deleted if it is used by the upper layer, that is, if there is an ATM interface created on it. You can use the YDI command to check whether the phyTTP is in use or not. Related topics Descriptions Physical layer Trail Termination Point (phyTTP)

3.4 Moving phyTTP in ATM Summary The detaching command YDR can be used when you want to detach a phyTTP, or all phyTTPs, of a unit from the physical interface. As the result of this command, the state of the phyTTP will be changed to detached. If the phyTTP is based on a protection group, the state of that protection group will also be changed to detached. The SDH parameters of the detached phyTTP will be stored and they will be used when the phyTTP is attached a new physical interface. The detaching of the phyTTP can be executed for the phyTTPs of the following network interface units: NPS1, and NPS1P. When detaching the phyTTP, the main working state of the target network interface has to be SE. When the network interface unit NPS1, or NPS1P is removed from the configuration, all phyTTPs related to that unit will be detached automatically. The unit must be removed by using the forced removal option. Otherwise the unit removal will be prevented. In the case of the network interface unit NPS1P, the phyTTP will be detached automatically only after both units of the pair have been removed. The detached phyTTP can be attached to a SET, a protection group of SETs, or to an existing protection group using the command YDS. If the phyTTP to be attached is based on a SET, it can be attached to a single SET or to an existing protection group. If the phyTTP to be attached is based on a protection group, it can be attached by defining both the working section SET index and the protection section SET index to which the phyTTP will be attached. A protection group based phyTTP can be attached also by defining only one SET index: the working or the protection section SET index. If the attaching is executed using the SET index of one protection group, the other SET will be added to the protection group automatically when the pair NPS1P unit is created. If the phyTTP to be attached is based on a protection group, it can be attached to another existing protection group or to a single SET. In this case, the protection group related to the detached phyTTP has to be removed first with the command YWD. After that the detached phyTTP can be attached to another existing protection group or to a single SET. The attached phyTTP will get the same SDH parameter values which had been stored when the destination phyTTP had been detached. After the execution of the attaching command, the SDH parameter values should always be checked, and also changed, if necessary, with the commands of the command group YA. Special cases If you accidentally remove the wrong interface unit, the phyTTPs can be attached back to the unit with the YDS command.



If you accidentally remove only the spare unit of NPS1P pair, the phyTTPs are not detached, because the working pair unit still exists. In this case, only the SET which belongs to the removed pair unit is automatically removed from the protection group. When you create the pair unit back into the configuration, the SET which belongs to this unit is automatically returned back to the protection group. •

In NPS1P case, this does not cause any downtime, but the protection is returned back when the spare unit is moved to SP-EX state.

Purpose The Physical layer Trail Termination Point (phyTTP) can be moved from one physical interface to another without the need to delete all the resources created on top of the phyTTP. This means that the relations between the phyTTP and the ATM interface will remain the same. The ATM interface related to the phyTTP and all the resources created on top of it will remain on top of the same phyTTP. The moving of the phyTTP can be used when replacing NPS1(P) units with another NPS1(P) units. Before you start Make a fallback copy before you start to move the phyTTP. For instructions on fallback copying, see Fallback and backup copying in Performing safecopying and restoring operations. When detaching or attaching a phyTTP, the main working state of the target network interface unit must be SE. If the target unit is NPS1P, also the pair unit's main working state must be SE. During a trial configuration it is also possible to detach a phyTTP from an interface unit which does not exist in the slice where the detaching command has been given. In this case there are no limitations for the unit state. Note that even if the target interface unit is located in the other slice, the configuration changes will be updated only to the configuration files of the slice in which the command was given. If you need to interrogate the phyTTP configuration or the operating state of the phyTTP, use the command YDI. If you need to interrogate information about the detached phyTTP, use the YDT command. With this command you can also see the SDH and the protection group information related to the detached phyTTP. Procedure

1

Detach the physical layer Trail Termination Point (YDR) ZYDR:[],[,];

2

Attach the physical layer Trail Termination Point (YDS) ZYDS:,(SET|PGSET|PROTGROUP),(|[]|,[]);


3


Check the SDH and the protection group configuration related to the phyTTP You can interrogate the phyTTP configuration with the command YDI. You can interrogate the protection group configuration with the command YWI. You can interrogate the SET configuration with the command YAI. You can interrogate the SDH traces with the command YAT.

Example Moving the phyTTP and protection group from NPS1 to NPS1P Detach the phyTTP with id 1 from NPS1. ZYDR:1;

Attach the phyTTP and the related protection group to the SETs with indexes 8 and 16 of an NPS1P pair. ZYDS:2:PGSET,8,16;

Example Moving the phyTTP and from NPS1 to NPS1P and taking MSP 1+1 in use Detach all phyTTPs from NPS1-0 by removing the functional unit. ZWFV:NPS1,0::1,1,12:FCD;

Create a protection group with id 4 with the MSP protocol for SET-9 (working section) and SET-17 (protection section) for NPS1P. ZYWC:4:9,17;

Attach the phyTTP to protection group 4. ZYDS:4:PROTGROUP,4;

Example Moving the phyTTP from NPS1P to unprotected SET of NPS1 Detach the phyTTP with id 3 from NPS1P. Also the related protection group will be detached. ZYDR:3;

Delete the protection group with id 3 which has a phyTTP with id 3 on top of it. ZYWD:3;

Attach the phyTTP with id 3 to a SET with index 9 of an NPS1. ZYDS:3:SET,9;

Physical interfaces performance monitoring


4 Physical interfaces performance monitoring 4.1 ATM interface measurement shows transmission errors Description The ATM interface measurement measures an ATM subnetwork's ability to process and deliver incoming ATM cells. It provides information about the amount of traffic between transmission path termination points. ATM interface measurement also reports protocol abnormalities (ATM cell headers becoming corrupted during transmission) detected on the transmission convergence sublayer of the broadband protocol stack. You can check the ATM interface statistics via the network management system. For more information, see ATM transport measurements.

Symptoms The ATM interface measurement shows the number of cells received with a header error control (HEC) violation. If the number of discarded cells suddenly exceeds the normal figures, there are many bit errors on the transmission path.

Recovery procedures Checking discarded cells Procedure

1

Check the discarded cells Take the path out of use and study the reason for bit errors.

4.2 STM-1 interface measurement shows transmission errors Description The STM-1 interface measurement measures a transmission path's ability to provide the agreed quality. If a satisfactory quality is not provided, the transmission path cannot be used.



The measurement gives information about the STM-1 interface in general. The information includes errors such as background block error (BBE), errored second (ES), severely errored second (SES), and unavailable second (UAS). You can check the STM-1 related statistics via the network management system. For more information, see STM-1 interface measurement in Transmission quality measurements.

Symptoms The counters regenerator section SES, multiplex section SES, path termination section SES, regenerator section UAS, multiplex section UAS, or path termination section UAS appear when measuring STM-1 interfaces. These counters do not usually appear, if the transmission path functions normally.

Recovery procedures Find out what is causing the counters to increase, and correct the error. Procedure

1

Check SES counter The increasing value of SES counter or counters indicates a high number of bit errors or defects, which last continuously for less than 10 seconds. If the continuous duration of the defect is more than 2 seconds, an alarm will be set. See SDH supervision for possible alarms. Depending on: • • •

2

the nature of the bit errors the configured threshold values of Signal Degrade (SD) and Signal Failure (SF) the configured threshold value of Severely Errored Seconds (SES), The alarm can be either 3979 INCOMING SDH SIGNAL DEGRADED or 3964 EXCESSIVE ERRORS IN INCOMING SDH SIGNAL.

Check UAS counter If the nature of a defect is more continuous (lasts continuously for 10 seconds or longer), or bit errors occur more continuously, the value of the UAS counter or counters will increase. The UAS indicates that there has been continuously 10 or more Severely Errored Seconds. During the UAS counting, there must be ten or more continuous available seconds before the UAS counting is stopped. If a defect is causing the increasing of the UAS counter values, there will be an alarm. See SDH supervisionfor possible alarms. Depending on the nature of the bit errors, configured thresholds values of Signal Degrade and Signal Failure, the alarm can be either 3979 INCOMING SDH SIGNAL DEGRADED or 3964 EXCESSIVE ERRORS IN INCOMING SDH SIGNAL.


t


Tip: These two alarms are set only for Multiplex section level bit errors. In both cases, check the alarms first. If there is an active alarm (see SDH supervision for possible alarms), follow the instructions of the alarm to repair the anomaly or defect. If there are no alarms, try to monitor the transmission network quality with an external SDH tester. If the situation is not normalised, take the transmission path out of use as no traffic can be transmitted via this path.

4.3 SONET/SDH protection group measurement shows transmission errors Description The SONET/SDH protection group measurement provides information on the switchover events between the working SONET/SDH link and the protection SONET/SDH link in one SONET/SDH protection group. If there are multiple switchover events in one measured SONET/SDH protection group during one measurement period or successive measurement periods, the transmission network is unstable. You can check the SONET/SDH protection group related statistics via the network management system.

Symptoms The counters Protection Switch Count (PSC) of Protection Group and/or Protection Switch Duration (PSD) of Protection Group appear when measuring the protection group.

Recovery procedures The switchover events in the SONET/SDH protection group may be caused by, for example: • • •

given external switch commands maintenance work of the transmission network maintenance work of the far-end network element.

Also check the active alarms for the sections of the protection group. The regenerator and multiplex section counters of the STM-1 measurement also maintain information about the condition of the sections. To improve the stability of the network, repair the transmission network failures according to the active alarms or investigate the reasons for the network failure more thoroughly with the help of the STM-1 measurement counters.

Configuring and Supervising Physical Interfaces for Ipa Rnc

Recommend Documents