See notice on first age
1675 LAMBDAUNITE MULTISERVICE SWITCH (MSS) OPTICAL NETWORK NAVIGATION SYSTEM (ONNS) – APPLICATIONS AND PLANNING GUIDE
ONNS-APG Alcatel-Lucent - Proprietary 365-375-026 This document contains proprietary information of Alcatel-Lucent and CC109647578 is not to be disclosed or used except in accordance with applicable agreements. ISSUE 5 JULY 2008 See notice on first age
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2008 Alcatel-Lucent. Unpublished and Not for Publication. All Rights Reserved.
Alcatel-Lucent - Proprietary See notice on first page Contents
About this document
Purpose ...... v
Reason for reissue ...... v
Intended audience ...... v
Conventions used ...... v
Related information ...... vii
How to comment ...... viii
1 Introduction
Overview ...... 1-1
ONNS Hardware prerequisites ...... 1-2
2 ONNS Functional overview
Overview ...... 2-1
ONNS applications ...... 2-2
Interfaces ...... 2-4
Connection management ...... 2-11
Protection and restoration ...... 2-20
Network optimization ...... 2-27
User-Network Interface (UNI) ...... 2-32
External Network-Network Interface (E-NNI) ...... 2-36
3 Network engineering and planning
Overview ...... 3-1
Specific rules and guidelines concerning the connection setup ...... 3-2
Basic mesh planning ...... 3-7
...... 365-375-026 Alcatel-Lucent - Proprietary iii Issue 5 July 2008 See notice on first page Contents
......
Transmission aspects ...... 3-9
Shared Risk Link Group (SRLG) ...... 3-15
Cost savings ...... 3-20
ONNS performance monitoring ...... 3-24
4 The Signaling Communication Network (SCN)
Overview ...... 4-1
Basic SCN principles ...... 4-2
SCN configurations ...... 4-6
SCN configuration guidelines ...... 4-10
Data communication channels for SCN ...... 4-13
SCN via LAN ...... 4-14
IP LAN provisioning ...... 4-15
ONNS signaling on network layer ...... 4-20
5 ONNS Management
Overview ...... 5-1
Operating the ONNS via the WaveStar® CIT ...... 5-2
Operating the ONNS via Optical Management System (OMS) ...... 5-4
Connection and path state definitions ...... 5-8
A
Standards ...... A-1
Glossary
Index
...... iv Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 About this document this document
Purpose This Applications and Planning Guide (APG) provides the following information about the Optical Network Navigation System (ONNS) for 1675 LambdaUnite MSS Release 11.0: • ONNS functional overview • Network engineering and planning • The Signaling Communication Network (SCN) • ONNS management
Reason for reissue This is a revised version of the Optical Network Navigation System APG with modifications for 1675 LambdaUnite MSS Release 11.0.
Intended audience The ONNS Applications and Planning Guide is primarily intended for network planners and engineers. In addition, others who need specific information about the features, applications, operation, and engineering of ONNS may find the information in this manual useful.
Conventions used These conventions are used in this document: Numbering The chapters of this document are numbered consecutively. The page numbering restarts at “1” in each chapter. To facilitate identifying pages in different chapters, the page numbers are prefixed with the chapter number. For example, page 2-3 is the third page in chapter 2. Cross-references Cross-reference conventions are identical with those used for numbering, i.e. the first number in a reference to a particular page refers to the corresponding chapter...... 365-375-026 Alcatel-Lucent - Proprietary v Issue 5 July 2008 See notice on first page About this document
...... Keyword blocks This document contains so-called keyword blocks to facilitate the location of specific text passages. The keyword blocks are placed to the left of the main text and indicate the contents of a paragraph or group of paragraphs. Typographical conventions Special typographical conventions apply to elements of the graphical user interface (GUI), file names and system path information, keyboard entries, alarm messages etc. • Elements of the graphical user interface (GUI) These are examples of text that appears on a graphical user interface (GUI), such as menu options, window titles or push-buttons: – Provision{, Delete, Apply, Close, OK (push-button) – Provision Timing/Sync (window title) – View Equipment Details{ (menu option) – Administration → Security → User Provisioning{ (path for invoking a window) • File names and system path information These are examples of file names and system path information: – setup.exe – C:\Program Files\Alcatel-Lucent • Keyboard entries These are examples of keyboard entries: – F1, Esc X, Alt-F, Ctrl-D, Ctrl-Alt-Del (simple keyboard entries) A hyphen between two keys means that both keys have to be pressed simultaneously. Otherwise, a single key has to be pressed, or several keys have to be pressed in sequence. – copy abc xyz (command) A complete command has to be entered. • Alarms and error messages These are examples of alarms and error messages: – Loss of Signal – Circuit Pack Failure – HP-UNEQ, MS-AIS, LOS, LOF – Not enough disk space available Abbreviations Abbreviations used in this document can be found in the “Glossary” unless it can be assumed that the reader is familiar with the abbreviation.
...... vi Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 About this document
...... Related information The manuals related to 1675 LambdaUnite MSS are shown in the following table:
Document title Document code
1675 LambdaUnite MSS Product Information and Planning Guide 109671750 Presents a detailed overview of the system, describes its applications, gives (365-374-195R11.0) planning requirements, engineering rules, ordering information, and technical specifications.
1675 LambdaUnite MSS User Provisioning Guide 109671776 Provides step-by-step information for use in daily system operations. The (365-374-196R11.0) manual demonstrates how to perform system provisioning, operations, and administrative tasks by use of WaveStar® CIT.
1675 LambdaUnite MSS Maintenance and Trouble-clearing Guide 109671768 Gives detailed information on each possible alarm message. Furthermore, it (365-374-197R11.0) provides procedures for routine maintenance, troubleshooting, diagnostics, and component replacement. 1675 LambdaUnite MSS Installation and System Turn-up Guide 109671792 A step-by-step guide to system installation and set up. It also includes (365-374-198R11.0) information needed for pre-installation site planning and post-installation acceptance testing. 1675 LambdaUnite MSS TL1 Command Guide 109671784 Describes the external TL1 interface for 1675 LambdaUnite MSS in terms (365-374-199R11.0) of TL1 command, responses, and notification definitions. ES64U Command Line Interface Guide 109681981 (365-374-200) ES64U SNMP Reference Guide 109681999 (365-374-201) 1675 LambdaUnite MSS Safety Guide 109510909 (365-374-159R11.0) Documentation CD-ROM 1675 LambdaUnite MSS (all manuals on a 109671800 CD-ROM) (365-374-181R11.0) 1675 LambdaUnite MSS Software Release Description This document is delivered with the NE software.
1675 LambdaUnite MSS Engineering and Ordering Information Drawing ED8C948-10
1675 LambdaUnite MSS Interconnect and Circuit Information Drawing ED8C948-20
These documents and drawings can be ordered at or downloaded from the Alcatel-Lucent Online Customer Support Site (OLCS) (https://support.lucent.com)or through your Local Customer Support.
...... 365-375-026 Alcatel-Lucent - Proprietary vii Issue 5 July 2008 See notice on first page About this document
...... How to comment To comment on this information product, go to the Online Comment Form (http://www.lucent-info.com/comments/enus/) or e-mail your comments to the Comments Hotline ([email protected]).
...... viii Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 1 1Introduction
Overview
Purpose This chapter introduces the Optical Network Navigation System (ONNS) used with 1675 LambdaUnite MSS.
ONNS functionality As a part of the intelligent network platform, ONNS comprises a set of capabilities that automates SONET/SDH connection setup. In addition to the traditional SDH/SONET services, 1675 LambdaUnite MSS systems support meshed restoration by making use of the so-called Optical Network Navigation System (ONNS). The Optical Network Navigation System (ONNS) is software that resides for instance on 1675 LambdaUnite MSS network elements and provides the basis for intelligent transport networking. The ONNS automates the transport network by introduction of a control plane and off loads much unnecessary effort from the operator. It was designed to meet the needs for an intelligent transport network to help increase revenue and cut operation costs. ONNS is a portable software package that accomplishes the connection management functions including automatically creating, deleting, restoring end-to-end data paths for the intelligent transport network. The ONNS allows network elements to communicate with each other in order to, amongst others, automatically set-up, restore and tear down connections.
Contents
ONNS Hardware prerequisites 1-2
...... 365-375-026 Alcatel-Lucent - Proprietary 1-1 Issue 5 July 2008 See notice on first page Introduction ONNS Hardware prerequisites
...... ONNS Hardware prerequisites
Hardware prerequisites Enabling the Optical Network Navigating System (ONNS) in a 1675 LambdaUnite MSS network element requires a specific hardware configuration: • Controller of type CTL/2, CTL/3S or CTL/4S – hosts the ONNS ORP software (topology/connection routing) – integrates SCN stack – forwarding of NNI, LSA messages to other NEs • Cross-connect and timing unit of type XC160, XC320/B, or XC640 – hosts the ONNS core software (connection set-up/tear down/restoration) – initialization and (operational) state handling for ONNS – defect information processing and evaluation for connection switching/restoration Important! It is recommended to use two suitable Controllers (duplex control) and two suitable cross-connect and timing units (XCs). Thus, both the Controllers as well as the cross-connect and timing units are automatically 1+1 equipment protected.
Network topology configuration rules For setting portClass from TRADITIONAL to EDGE be sure that no test access session must be active on any tributary of that port. For setting the portClass from TRADITIONAL to UNI, the following must be fulfilled: • The service condition servcond of the port must be INSERVICE • no HO cross connections are allowed to be associated with any tributary of the port • no LO cross connections are allowed to be associated with any tributary of the port • no test access session is active currently on any tributary of the port • no cross connect loopbacks are active on that port • the port is not involved in a MSSPRING/BLSR protection scheme • the UNI-N node must be already activated
...... 1-2 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 2 2ONNS Functional overview
Overview
Purpose This section gives a functional overview of the Optical Network Navigation System (ONNS) application
ONNS functions The Optical Network Navigating System (ONNS) application basically comprises the following functions: • Path setup and routing • Path tear-down • Automatic path restoration in case of failure • Topology discovery • Neighbor discovery
Contents
ONNS applications 2-2 Interfaces 2-4 Connection management 2-11 Protection and restoration 2-20 Network optimization 2-27 User-Network Interface (UNI) 2-32 External Network-Network Interface (E-NNI) 2-36
...... 365-375-026 Alcatel-Lucent - Proprietary 2-1 Issue 5 July 2008 See notice on first page ONNS Functional overview ONNS applications
...... ONNS applications
Supported topologies 1675 LambdaUnite MSS systems support the following ONNS topologies: • Single-domain application (comprising only Edge and I-NNI ports) • Single-domain application with User-Network Interface (UNI) • Multi-domain application The following diagrams serve to visualize these topologies.
1. Single-domain application (only Edge and I-NNI ports) ONNS domain
I-NNI I-NNI I-NNI I-NNI Edge Edge I-NNI I-NNI Z A I-NNI I-NNI
I-NNI I-NNI
...... 2-2 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview ONNS applications
......
2. Single-domain application with UNI
ONNS domain
I-NNI I-NNI I-NNI source destination UNI-N I-NNI UNI-N I-NNI I-NNI I-NNI source I-NNI UNI-C I-NNI destination I-NNI UNI-C
Please also refer to “User-Network Interface (UNI)” (p. 2-32).
3. Multi-domain application with E-NNI
ONNS domain (I-NNI)
E-NNI E-NNI Edge
ONNS domain ONNS domain (I-NNI) (I-NNI)
Edge
Please also refer to “External Network-Network Interface (E-NNI)” (p. 2-36). Important! Please note that network connections over UNI and E-NNI ports are currently not supported.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-3 Issue 5 July 2008 See notice on first page ONNS Functional overview Interfaces
...... Interfaces
Overview Optical Network Navigation System (ONNS) is the optical control plane at 1675 LambdaUnite MSS to provide different network interfaces connected to ports. These ports are characterized in the following paragraphs of its so-called port classes.
Interface ports Note, that port provisioning is not an ONNS function, but to support ONNS functionality, ports on an NE must be configured with the appropriate port classes. These port classes can be distinguished: • Traditional ports are ports outside the ONNS control and its topology. Traditional connections are setup manually by using the management system. • Edge ports delineate the boundary of a single ONNS routing domain. Edge ports interface to SNCP/UPSR nodes outside of the ONNS routing domain. The section “ONNS interface port parameters” (p. 2-6) lists the parameters used with Edge ports. Note, Edge ports do not maintain ONNS signaling with each other. • UNI ports The UNI (User-Network Interface) ports interface to client equipment by running a client-server protocol. The UNI is the service control interface between the transport network (UNI-N) and the client equipment (UNI-C). The UNI supports a multi-vendor inter-working, a multi-client by using IP, ATM, or TDM, a multi-service at SONET, SDH, and Ethernet, and a service monitoring interface for SLA management. The section “ONNS interface port parameters” (p. 2-6) lists the parameters used with UNI ports. • I-NNI ports The I-NNI (internal Network-Network Interface) ports interface to other I-NNI ports and connect one NE to another NE in the ONNS domain. The section “ONNS interface port parameters” (p. 2-6) lists the parameters used with I-NNI ports. • E-NNI ports The E-NNI (external Network-Network Interface) ports delineate the end points of the ONNS connection at routing domain boundaries. E-NNI is used independently of survivability schemes of each domain to interface to multi ONNS domains, and/or multi carrier domains. The section “ONNS interface port parameters” (p. 2-6) lists the parameters used with E-NNI ports. Note, if the source or destination is an E-NNI port, traditional cross connections will be rejected.
...... 2-4 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Interfaces
...... The following figure provides an overview of port connections. Please also take the supported ONNS topologies into account, see “Supported topologies” (p. 2-2).
Next ONNS Domain
UNI-C UNI-N iNNI
eNNI iNNI ONNS Domain iNNI eNNI
UNI-N iNNI iNNI iNNI iNNI UNI-N UNI-C UNI-C EDGE EDGE iNNI
Boundary of 1 routing domain
non-switching traditionally, network elements pre-provisioned Signaling connections Transport
In the bottom right part of the figure it is shown how two I-NNI ports are connected over a traditionally cross-connected network. This requires manual neighbor provisioning for the I-NNI ports and whenever possible, pre-provisioned pipe cross-connections in the interconnecting traditional network part corresponding to the rate of the port connection between the I-NNI ports.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-5 Issue 5 July 2008 See notice on first page ONNS Functional overview Interfaces
...... ONNS interface port parameters
Parameter Description Applicable to port classes Port class specifies whether the selected port is available Edge for ONNS applications (as an Edge, UNI, UNI I-NNI, or E-NNI port) or not (traditional). I-NNI The default values vary between Traditional E-NNI for outside the ONNS or Edge inside the ONNS because both values are controlled and initiated by the management plane. The values can be: • Traditional (default), see above. • Edge (default), see above. • UNI • I-NNI • E-NNI Tributary mode For SONET edge or E-NNI ports, the mode Adaptive can be adaptive or fixed. Fixed For other ports, the tributary mode is set to fixed and cannot be changed. Local port ID specifies the 32-bit local port ID for Edge unidirectional or bidirectional ports. UNI Alcatel-Lucent NEs will interpret the 32 bits I-NNI as a generic physical address of 4-bytes as E-NNI described below: • Bay# (1 byte / MSB) • Shelf# (1 byte) • Slot/Pack# (1 byte) • Port# (1 byte / LSB) for # = 0 (unused) or initial value Port bandwidth indicates the line signal rate depending on the Edge port class as shown in “ONNS port-rate to UNI port-class combinations” (p. 2-9). I-NNI E-NNI
...... 2-6 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Interfaces
......
Parameter Description Applicable to port classes Port control indicates the administrative mode of the port Edge is Normal or Lockout. UNI I-NNI E-NNI Min. Path/Conn. provision the minimum tributary and mapping Edge Rate rate supported for the port depending on its I-NNI port rate and interface standard. E-NNI Max. Path/Conn. provision the maximum tributary and mapping Edge Rate rate supported for the port depending on its I-NNI port rate and interface standard. E-NNI Line signal state indicates if the ONNS port connection is ok or Edge failed. UNI I-NNI E-NNI Local LPID provision the Logical Port Identifier for an Edge ONNS port from the local node’s UNI point-of-view. E-NNI Network TNA identifies the Edge connection endpoints by Edge Transport Network Assigned (TNA) adresses. UNI A TNA consists of a type and its value of the address which are composed to: • IPv4 (default type), address a 4-Byte address in a four dot-separated decimal form like 129.12.3.178 each. • IPv6, address a 16-Byte address in a eight dash-separated hexadecimal form like AE12-0-0-12-EDFB-89AB-2254-8A2E each. • NSAP, address a 20-Byte address in a hexadecimal form with 11AA22BB33DD44EE55FF66....77AB88AC99 each. Client node ID identifies the communication address of the UNI peer UNI-C using the NetworkTNA type IPv4 as written before.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-7 Issue 5 July 2008 See notice on first page ONNS Functional overview Interfaces
......
Parameter Description Applicable to port classes Neighbor ASTN identifies the I-NNI neighbor NE used for I-NNI node ID uniquely identifying the NE for the ONNS application within a single domain. Possible values are: an array of 4 integers a.b.c.d in the form of a, b, c,d={0,{, 255},.or 0.0.0.0 (default), or UNKNOWN. Neighbor node ID used IPv4 address for signaling between two I-NNI ONNS nodes connected by I-NNI links within a single domain. Possible values are IPv4 or UNKNOWN. Neighbor port ID identifies the remote I-NNI port is connected I-NNI to the local I-NNI port. Possible values are the port address in form of bay, shelf, slot, or port, or UNKNOWN. Propagation delay indicates the number of milliseconds it takes I-NNI for a bit to traverse the port connection. This time depends upon the physical length of the port connection for example 1 km = 4.5 µs. Shared risk link indicates port connections that share a certain I-NNI group ID list risk by values port risks, that share the same E-NNI card, or portConnection risks that share the same duct. The number of different SRLG values that need to be assigned to a specific port increases with the size of the network. Link resource class used to globally classify the abstract link the E-NNI corresponding E-NNI port is assigned to for E-NNI routing purposes. Administrative link realizes the link metric attribute as defined in I-NNI costs standard. E-NNI Neighbor detection specify the port of class I-NNI discover its I-NNI mode neighbor automatically or via manual provisioning. Remote advertised specifies the identification advertised by E-NNI node ID integer for the remote domain connected via the corresponding port. Remote TID specifies the NE name (TID) of the remote E-NNI physical node.
...... 2-8 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Interfaces
......
Parameter Description Applicable to port classes Local link ID specifies an advertised identification by E-NNI integer in the local scope for the link the corresponding port belongs to. Remote link ID specifies an advertised identification by E-NNI integer in the remote scope for the link the corresponding port belongs to. Remote routing defines a set of transport resources in the E-NNI area ID network for which the routing applies. Neighbor signaling specifies an advertised identification of the E-NNI PC identity neighbor node for signaling purposes by integer. Neighbor signaling specifies the IPv4 address of the neighbor E-NNI PC IP address node to be used for signaling purposes in a four dot-separated decimal form like 129.12.3.178 each.
Notes: 1. For the configuration parameters of an E-NNI port, please also refer to “External Network-Network Interface (E-NNI)” (p. 2-36).
ONNS port-rate to port-class combinations
Port Rate Port classes Edge UNI I-NNI E-NNI STM-1 yes yes yes yes STM-1e yes yes yes no STM-4 yes yes yes yes STM-16 yes yes yes yes STM-64 yes yes yes yes OC-3 yes yes yes yes OC-12 yes yes yes yes OC-48 yes yes yes yes OC-192 yes yes yes yes GbE-1 yes yes no no
...... 365-375-026 Alcatel-Lucent - Proprietary 2-9 Issue 5 July 2008 See notice on first page ONNS Functional overview Interfaces
......
Port Rate Port classes Edge UNI I-NNI E-NNI GbE-10 yes no no no
...... 2-10 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Connection management
...... Connection management
Connection modification / connection attributes ONNS supports the following modifications on existing, in-service ONNS connections: • Protection type Modification of protection type is allowed from unprotected to any protection type - except Y-connetions - or vice versa, or from revertive auto-reroute to non-revertive auto-reroute or vice versa. • Restoration priority Modification of the restoration priority is allowed for any connection with the protection types revertive auto-reroute or non-revertive auto-reroute. • Connection alias Each connection can be labeled with a specific alias. • Path PM Enable/disable. • 1+1 Protection parameters Modification of the Wait To Restore Time and the Holdoff Timer for 1+1 protected paths.
ONNS protection types The ONNS automates SONET/SDH path connection set-up and teardown through the network. Different protection types can be specified at provisioning time. These protection types include: • Unprotected An unprotected connection is a single path. If it fails, no attempt is made to protect or re-route it. The unprotected connection is intended for non-critical traffic or for traffic protected within the client layer, using diversely routed unprotected paths. • Auto-Reroute, non-revertive For a non-revertive auto-reroute connection, the existence of two disjoint paths is verified, but only one path is set up, not two. If and when the originally setup path fails, a maximal disjoint alternate path is calculated which meets all the original constraints. Once this path is setup, the original path is released to allow the network to reuse the resources. • Auto-Reroute, revertive For a revertive auto-reroute connection, the original path is not released and traffic will revert back to the original path once the failure has been fixed. • Auto-Reroute, manual revertive This type of service is similar to the Auto-Reroute, revertive type of service with the difference that traffic can be manually reverted back to the original path.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-11 Issue 5 July 2008 See notice on first page ONNS Functional overview Connection management
...... • 1+1 (revertive or non-revertive) The path from source to destination is set up as a 1+1 protected connection (revertive or non-revertive). A 1+1 protected connection contains two separate paths from source to destination, both set up and ready for use. If one fails, the other is selected. This type of service offers high availability. It is intended for mission critical services. A single service is assigned two disjoint paths. Information is transmitted in both paths and a selector at the destination picks the best signal for service. In the event of a failure, the selector at the destination simply switches over to the secondary path. This form of connection guarantees a high speed recovery. In revertive mode, the selector will switch back to the original path if this has been cleared of its failure(s). In non-revertive mode, the selector will maintain the current service in its secondary path even if the original path has been cleared of its failure(s). • 1+1 permanent A 1+1 permanent protected connection is a combination of a 1+1 end-to-end network protection (SNCP/UPSR, either revertive or non-revertive) with an auto-reroute path restoration. If one of the two legs of the 1+1 end-to-end network protection fails, then this failed leg will be restored. Thus, the service is still available in case of the failure of one leg. However, the service is “degraded” until the restoration of the failed leg is completed. A 1+1 permanent protected connection improves the service reliability of the 1+1 end-to-end network protection. This is true not only for a single point of failure, but also for rare double failure scenarios where both legs are faulty at the same time. Best Effort Disjointness: In case of a protection type modification from an unprotected to a 1+1 permanent protected connection, no degree of disjointness is specified. The two paths of the connection will be as disjoint as possible between the ingress node and the egress node. In worst case, the disjointness between the two paths of the connection is MAXIMAL. • M:N shared protection An M:N shared protection consists of N worker routes which are protected by M protection routes of equal bandwidth. The supported M:N protection ratios are 1:1, 1:2 and 1:3. Thus, one protection route is available to protect up to three worker routes. If one of the worker connections fails then the corresponding traffic is switched
...... 2-12 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Connection management
...... over to the protection connection. As M:N shared protection operates in revertive mode, traffic is switched back to the worker connection as soon as it is fault-free again. The protection path becomes available again after the wait to revert time has expired and the system reverted successfully to the old (previously failed but now recovered) worker path. • Y-connection A Y-connection contains two paths which start at the same source node (on the same port and timeslot), but terminate at different destination nodes. This ONNS construct can be used as a building block for a cross-domain 1+1 pair of paths (a logical ring), where the first half of both paths – in the ONNS domain – are set up by requesting a Y-connection, and the second half of both paths – outside of the ONNS domain – are set up by traditional means. The approach for routing a Y-connection is like the 1+1 connection described above, but performed with enhancements to the modified Dijkstra algorithm to handle two different destinations.
Service level The service level is the representation of the connection type of an ONNS connection segment of a UNI or E-NNI connection. The ONNS connection types are represented by the following values of the service level parameter:
...... 365-375-026 Alcatel-Lucent - Proprietary 2-13 Issue 5 July 2008 See notice on first page ONNS Functional overview Connection management
......
Service level Service level ONNS connection type (fixed (pipe connection) connection) 9 109 Unprotected 10 110 Auto-Reroute, non-revertive, COMPLETE disjoint 11 111 Auto-Reroute, non-revertive, FULLYSRLG disjoint 12 112 Auto-Reroute, non-revertive, MAXIMAL disjoint 20 not supported Auto-Reroute, revertive, COMPLETE disjoint 21 not supported Auto-Reroute, revertive, FULLYSRLG disjoint 22 not supported Auto-Reroute, revertive, MAXIMAL disjoint 23 not supported Auto-Reroute, manual revertive, COMPLETE disjoint 24 not supported Auto-Reroute, manual revertive, FULLYSRLG disjoint 25 not supported Auto-Reroute, manual revertive, MAXIMAL disjoint 30 35 1+1 (non-revertive), COMPLETE disjoint 31 36 1+1 (non-revertive), FULLYSRLG disjoint 40 45 1+1 (revertive), COMPLETE disjoint 41 46 1+1 (revertive), FULLYSRLG disjoint
Notes: 1. Y-connections are not suppported via UNI and for network connections (E-NNI connections). 2. M:N connections are not suppported via UNI and for network connections (E-NNI connections). 3. Permanent 1+1 protected connections are not suppported via UNI and for network connections (E-NNI connections).
Changing the protection type Using the Modify ONNS Connection (Path) window, you can modify the protection type of a selected ONNS connection. Depending on the protection type of the selected ONNS Connection (Path), the following modifications are possible: • A fixed ONNS connection with a protection type of Unprotected can be changed to a fixed ONNS connection with a protection type of: – Auto Reroute non-revertive – Auto Reroute revertive – Auto Reroute, manual revertive – 1+1 (revertive or non-revertive) – 1+1 permanent
...... 2-14 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Connection management
...... The 1+1 permanent connection will be setup with default settings (non-revertive). A pipe ONNS connection with a protection type of Unprotected can be changed to a pipe ONNS connection with a protection type of: – Auto Reroute non-revertive – 1+1 (revertive or non-revertive) • A fixed ONNS connection with a protection type of Auto-Reroute, non-revertive can be changed to a fixed ONNS connection with a protection type of: – Unprotected – Auto Reroute revertive – Auto Reroute, manual revertive • A pipe ONNS connection with a protection type of Auto-Reroute, non-revertive can be changed to a pipe ONNS connection with a protection type of: – Unprotected • A fixed ONNS connection with a protection type of Auto-Reroute, revertive can be changed to a fixed ONNS connection with a protection type of: – Unprotected – Auto Reroute non-revertive – Auto Reroute, manual revertive • A fixed ONNS connection with a protection type of Auto-Reroute, manual revertive can be changed to a fixed ONNS connection with a protection type of: – Unprotected – Auto Reroute non-revertive – Auto Reroute revertive • A fixed ONNS connection with a protection type of 1+1 (revertive or non-revertive) can be changed to a fixed ONNS connection with a protection type of: – Unprotected – 1+1 permanent • A pipe ONNS connection with a protection type of 1+1 (revertive or non-revertive) can be changed to a pipe ONNS connection with a protection type of: – Unprotected • A fixed ONNS connection with a protection type of 1+1 permanent can be changed to a fixed ONNS connection with a protection type of: – Unprotected – 1+1 • ONNS connections with a protection type of M:N shared protection or Y-connection cannot be modified using the Modify ONNS Connection (Path) window.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-15 Issue 5 July 2008 See notice on first page ONNS Functional overview Connection management
...... Connection modification / Bridge and Roll The Bridge and Roll capability allows the user to request modification of the node list (route) to an existing ONNS connection that is in-service. As a result, traffic for an ONNS connection is moved from the currently existing path to an alternative path. This type of request is useful when the need arises to do a manual and/or administrative operation on any node/link(s) of the existing path and free up the resources on that path. The user can specify path constraints including the explicit node list for the alternative path or have ONNS choose one, like in a normal connection request. The system calculates a new path through the network that share a common ingress (/egress) node and a common egress (/ingress) node with the existing path. The new path is then bridged from the ingress (/egress) node to egress (/ingress) node. After the bridge and roll is accomplished for a connection, the old path is removed. The following requirements have to be considered: • Reroute of a 1+1 connection or a Y-connection is not supported directly, the connection must be converted to an unprotected connection and then rerouted. Then the connection can be modified back to a network 1+1 connection or Y-connection. • Reroute of a revertive restoration protected connection is not possible during the restoration path is active. • A restoration protected connection is handled as an unprotected connection. • The rerouting request can use connection constraints as described in “Connection constraints” (p. 3-16) If no new constraints are given, the system uses no user constraints and sets up the path using the least cost criteria. Rerouting without constraints can be used for manual path optimization in case of network topology changes. This can lead to a chosen route which is exactly the same as the original route with different tributary numbers. This means that a traffic hit occurs independence of a route change or not. Reroute computation The path computation procedures of unprotected connections described in “Path Computation” (p. 3-17) are also used in cases where a reroute of an existing connection is requested. The level of disjoint is not considered because restoration protected connections are handled as unprotected connections. An unsuccessful reroute path calculation does not impair the existing connection.
...... 2-16 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Connection management
...... M:N group modification It is possible to extent an M:N protection group by additional connections, if: • free bandwidth is available in the existing worker routes if the current number of worker routes is equal N • free bandwidth is available for a new route if the current number of worker routes is less than N • free bandwidth is available in the protection routes if a new protection connection necessary.
GbE virtual concatenation groups The ONNS feature of 1675 LambdaUnite MSS supports automated transport provisioning between two virtual concatenation groups, corresponding to EDGE ports of type Gigabit Ethernet (GbE). Each VCG contains a number of members, the VCG tributaries (VCGTRIB), depending on the selected interface standard. These members are automatically created when the VCG is created, i.e. when the corresponding GE1 pack is provisioned. The following provisioning functions are supported: • Set up paths – for a single VCGTRIBs – for an arbitrary list of VCGTRIBs – for the whole VCG (all VCGTRIBs). When setting up the path via ONNS, it is possible to configure 1+1 protected, auto-reroute revertive or auto-reroute non-revertive protection for the respective group of VCGTRIBs with a single operation, given that the concerned tributaries of the respective VCG connect NEs within the ONNS domain (cf. the VCG connection topology Example 1 shown below). • Delete path for single VCGTRIB • Delete group • The enabling of individual VCGTRIBs, whether to take part in the virtual concatenation of the specific VCG or not, is done automatically. VCG connection topology examples With 1675 LambdaUnite MSS there are numerous application examples for Ethernet over ONNS transport, all of them can be typified with the following elementary topologies. Example 1: Both Ethernet terminating NEs with the respective edge VCGs are part of the ONNS domain, and the tributaries are routed within the ONNS domain:
...... 365-375-026 Alcatel-Lucent - Proprietary 2-17 Issue 5 July 2008 See notice on first page ONNS Functional overview Connection management
......
Edge VCG
Edge VCG ONNS domain
In this topology VCGTRIB paths can be set up with the automated ONNS function. Example 2: Only one Ethernet terminating NEs with the respective edge VCG is part of the ONNS domain, and the tributaries are routed partly outside the ONNS domain:
Edge VCG SDH/SONET edge tribs
SDH/SONET ONNS domain VCG
In this topology the automated path set-up between the VCGs is not supported.
...... 2-18 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Connection management
...... Minimization criteria of diverse routing For unprotected connections the routing algorithm of the n connections of a VCG for GbE is enhanced to calculate all n connections in one step, thereby using one of the following user specified optimization criteria: • Minimize total administrative cost of the n connections, • Minimize number of different routes. The algorithm tries to find a minimal number of different routes for the requested paths. Those routes may have nodes in common and therefore the solution may not always be optimal with respect to node diversity.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-19 Issue 5 July 2008 See notice on first page ONNS Functional overview Protection and restoration
...... Protection and restoration
Purpose ONNS automates SONET/SDH connection setup and tear down. It provides automated connection provisioning with several different protection types to support user’s various traffic types with different quality of service requirements.
Path setup and routing A user makes a connection setup request via the ONNS GUI or a network management system. The request for a new network connection is sent to the selected source node. The source node is the managed element that receives a user setup request, manages the setup, restoration, and tear down of both unidirectional and bidirectional connections, and is responsible for persistent storage of connection data and reporting of path fault status. The required bandwidth, protection scheme, and the edge ports at the source node and the destination node must be specified in the request. ONNS calculates the lowest cost route across the network which meets any specified constraints, based on the current network topology stored at the source node. The connection setup proceeds hop-by-hop along the calculated route. In the case of setup failure, a second attempt is made. The ONNS application puts the functionality of path routing from the management system into the NE. Example The inter-NE communication is setup via signaling protocol: 1. Call setup request for SDH/SONET path from SNP A to SNP Z with (best effort) protection. 2. (Unsuccessful) Setup request along path (A, E, D). 3. Setup rejection due to resource constraint. 4. (Successful) setup request along path (A, B, C, D). 5. Setup confirmation.
...... 2-20 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Protection and restoration
......
1 4 B 5 C A 2 A 3 E Z D
F
SONET/SDH Multiplexer
Path tear down Path tear down is performed as follows: 1. Path tear down request originates from source node A to node D with unique pathID. 2. Node D tear-downs the associated cross-connects and sends the path_release message backwards along the path C, B, A
ONNS: DLT-PATH command
B A C
D E
F
...... 365-375-026 Alcatel-Lucent - Proprietary 2-21 Issue 5 July 2008 See notice on first page ONNS Functional overview Protection and restoration
...... Path restoration ONNS automatically restores auto-reroute mesh connections when they fail. ONNS calculates a new disjoint path and sets up the path bridging the failed path. Mesh restoration is based on best effort and priority: if there is no available bandwidth, restoration doesn’t succeed. In this case, the failed connection will be restored automatically after the fault is recovered.
B A C
D E
F
The following describes the ONNS path restoration process: 1. Destination node detects the signal failure and notifies source node (via reliable message routing) 2. Source node checks the client input port & signal 3. Source node determines best alternate path (and the original path attributes are retained) 4. Source node initiates the set up of the alternative restoration path. (If successful, then at this point transmission is restored.) 5. Source node verifies the status of the restoration path (and performs a retry if necessary) 6. Source node tears down the old path (if non-revertive) 7. Source node notifies the management system of result 8. If restoration fails, then the connection is placed on a restoration queue for automatic restoration when resources become available Important! If for maintenance purposes a single port/multi-port circuit pack is to be pulled out which has auto-reroute meshed connections, the following rules have to be considered: • In case of a multi-port circuit pack set the remaining ports to LOCKOUT.
...... 2-22 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Protection and restoration
...... Topology discovery ONNS intelligent network elements auto-discover their neighbors and share the relevant data throughout the network allowing each node to automatically learn the topology of the entire network. Bandwidth availability for links with the same characteristics is aggregated in order to make the amount of data manageable. This information is redistributed throughout the network periodically, and immediately if it changes significantly. As soon as the port class of an optical port is changed to iNNI, the ONNS Topology Discovery function is started (in case the neighbor detection mode is set to AUTO). 1. Each NE auto-discovers its port-to-port neighbor adjacencies 2. Each NE floods the network with Link State Advertisements (LSA) containing NE adjacencies 3. The NEs use LSAs to build network database 4. Network database is used to allow path creation between endpoints.
WS-CIT WS-CIT
B B C C A A D E D F Add Node F Define NNI Ports
B B C C A A E D D
F F
The neighbor IP-address, that is made available by the ONNS Topology Discovery function per NNI-interface and/or LAN, is used to route IP packets to the neighbor.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-23 Issue 5 July 2008 See notice on first page ONNS Functional overview Protection and restoration
......
ONNS Topology Memory
LSAs
The network topology is discovered and populated in each node of an SCN.
Link State Advertisement Each Network Element sends to every other Network Element a message containing the state of all of its NN-links. This message is known as Link State Advertisement (LSA). Upon receipt of the LSA, the Network Element will update its Link State Database. The functionality described is called Optical Routing Protocol (ORP). ORP uses the UDP service of SCN to send LSAs. Link State Advertisements (LSAs) are sent when an NN-link is created, deleted and when the bandwidth of the NN-link changes.
...... 2-24 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Protection and restoration
......
B
X C
Y A
D Each Node has one LSA. The LSA for Node A has information on three link bundles: A-B, A-C, and A-D. Bandwidth information per NN link: Each link may contain multiple NN links; - minimum XC rate bandwidth is listed (bundled) per NN link. - maximum XC rate Each NN link may represent multiple port - bandwidth available at minimum rate connections (port-to-port), each with multiple link connections (matrix-to-matrix). - bandwidth available at maximum rate
Bundling criteria: min. XC rate - total bandwidth (used + available)
Neighbor discovery Automatic discovery of the physical neighbor by each NE refers to discovering the other end of a transmission link connection in terms of the neighbor’s node ID (and network address) and the neighbor’s port ID. Neighbors of interest to ONNS are those NEs running the ONNS software and that have a switching capability. As soon as the port class of an optical port is changed to iNNI, the iNNI neighbor discovery protocol is started. As soon as the neighbor of an iNNI port is known, the IP address of the neighbor is revealed to the SCN stack.
Neighbors SONET/ SONET/ SDH NE SDH NE
STS-1 STS-1
MS MS Neighbor discovery protocol RS RS STM-x / OC-x
STS-1 cross connect matrix
Termination function
Network Element
...... 365-375-026 Alcatel-Lucent - Proprietary 2-25 Issue 5 July 2008 See notice on first page ONNS Functional overview Protection and restoration
...... Manual neighbor provisioning Non ONNS sub-networks can be embedded in a SCN network domain. This requires manual neighbor provisioning. Such external equipment is required to be part of a dedicated network. In case the neighbor detection mode is set to manual, the following components have to be provisioned: • neighbor node ID • neighbor node IP • neighbor port ID In case the neighbor detection mode is set to manual, the neighbor port ID is used to provision the peer NE port per iNNI port. In all cases it is used to retrieve the detected (either automatically or manually provisioned) peer NE port per iNNI port. Source and destination node information Three types of data can be retrieved from any node. • Connection data describes an end-to-end connection, including the list of nodes the connection passes through. This data is stored at the source node for each connection. • Network topology data describes in summary form the node-to-node link bundles and resource availability for the entire network. This data can be obtained from any node, since all nodes have a consistent view of the network topology. • Neighbor data is unique to each node in the network. It describes the links to each neighbor, the status and availability of every port, and the local view of all paths through the node, including local cross connects.
...... 2-26 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Network optimization
...... Network optimization
Overview Network optimization includes: • “Link port defragmentation” (p. 2-27). • “Database audit and synchronization procedures” (p. 2-27) • “Supervision of used bandwidth on link bundles” (p. 2-29)
Link port defragmentation Defragmentation for SONET/SDH network is rearranging or repacking SONET/SDH signal assignment to eliminate bandwidth fragmentation. In other words, it is to pack the traffic in a HOVC [LOVC] component link in contiguous timeslots, to make the available bandwidth accessible by larger signal types. The following figure illustrates a fragmented fiber link connecting two SONET/SDH nodes and its compacted bandwidth after defragmentation for the same fiber link.
Database audit and synchronization procedures The NN GUI provides two types of database audit and sync. A local version which will detect discrepancies between the NE port/cross-connect data and the Network Navigator data, and a path-level version, that detects path discrepancies among NEs. Such discrepancies are rare, but can be caused by unrecoverable errors, such as unexpected resets and NVM failure.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-27 Issue 5 July 2008 See notice on first page ONNS Functional overview Network optimization
...... Port Data Inconsistencies If a discrepancy in port data between the NE and the ONNS topology is suspected, the Local Audit and Local Sync operation should be used. The Audit will show ports missing from the ONNS topology, and additionally, the extra ports that no longer exist on the host. The Local Sync operation can be used to clear up these discrepancies, as well as synchronize the port and tributary fault data. If a port unknown to the host also has cross-connects, the extra cross-connects will also be removed by the Local Sync. In all cases, the host NE data is assumed to be correct. Orphan NN Cross-Connects If the host contains an ONNS cross-connect in its map, but ONNS data has no record of the path or cross-connect, an orphan cross-connect has occurred. A Local Audit will detect this condition, but the Local Sync is not recommended for this case. Note: The Local Sync and Path Sync operations will not properly clean up this case, unless the cross-connect is manually deleted. To fix this case, the user should: 1. Determine the orphan cross-connects via a Local Audit. 2. Delete each cross-connect directly from the NE using the ED-NNCRS and DLT-CRS host commands [see OSEG, chapter 7, Cross-connection]. 3. Perfom a Path Audit and Sync to remove any broken paths related to the orphan cross-connects. If, instead, the Local Sync is executed, a dummy xcon record will be added to the ONNS database, because the host data is assumed to be correct. This dummy record can be removed by deleting the cross-connect directly from the NE, and performing a Local Audit and Local Sync. Note: In future releases, the dummy pathID can be replaced with a real pathID via a user operation. Cross-Connects in ONNS, Unknown to NE If the ONNS data contains references to ONNS or host cross-connects that do not exist in the host map, ONNS has extra cross-connect data. The host state is assumed to be correct, so the ONNS references should be removed. The Local Audit function will show these discrepancies and the Local Sync command will remove them. Stray Path IDs If a path record and cross-connect exists only on one NE, or the path record on the source node is missing, a stray path ID has occurred. On the GUI, the Path Audit function will detect this condition. Note that a Local Audit will report no inconsistencies in this case, as the local NE data and ONNS data are consistent.
...... 2-28 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Network optimization
...... Missing Path IDs If a path record and cross-connect is missing from one NE, perhaps due to replacing the database and resetting the machine, a missing pathID has occurred. The path will be in a CON&FAILED state, and a Path Audit will show “Connection record not found”. To clean up this situation, the user can run Path Sync or delete the path in the Path display. Both cleanup methods will remove the path data and delete all cross-connects from the host map. In this case, a Local Audit will report no inconsistencies, as the local NE data and ONNS data are consistent.
Supervision of used bandwidth on link bundles The bandwidth utilization of the link bundles is supervised by means of a Threshold Control Alert (TCA) mechanism with two user provisionable thresholds (a “lower TCA threshold” and a “higher TCA threshold”). For link bundles whose absolute bandwidth consumption reaches or exceeds one of these thresholds, a TCA event notification is generated and stored in the ONNS event log. The TCA mechanism has three states. Besides the inactive state, two alert levels are supported dependent on which of the thresholds is reached or exceeded. The two thresholds are provisionable per node in the range between 10% and 100% in steps of one percent and are stored in the non-volatile memory of the node. The TCA mechanism can be used to get an overview on potential bandwidth bottlenecks in an ASON. Such bottlenecks can occur during extensive provisioning operations, but can also be a result of multiple restoration scenarios. Countermeasures are part of traffic engineering as well as of network engineering: • Manual re-routing of paths • Reconfiguring port parameters or relabeling ports and thus implicitly changing the link bundles (port grouping) • Installation of additional port connections • Long term network planning Although TCAs are a warning mechanism to indicate a lack of available bandwidth, they do not indicate the ability of a port group (link bundle) to support further path setups or restorations in terms of fragmentation. Defragmentation might rather be necessary to make the remaining bandwidth of the port group (link bundle) again fully usable for all kind of cross-connection rates.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-29 Issue 5 July 2008 See notice on first page ONNS Functional overview Network optimization
...... TCA status The TCA status indicates the bandwidth utilization of a link bundle: • The TCA status is INACTIVE as long as the bandwidth utilization is below the lower TCA threshold. • The TCA status is LOW if the bandwidth utilization is above the lower TCA threshold but still below the higher TCA threshold. A corresponding TCA event notification (“LOW status entered”) is generated and stored in the ONNS event log. • The TCA status is HIGH if the bandwidth utilization is above the higher TCA threshold. A corresponding TCA event notification (“HIGH status entered”) is generated and stored in the ONNS event log.
100% HIGH Higher TCA threshold LOW Lower TCA threshold INACTIVE
TCA status (Used bandwidth)
When the lower TCA threshold is set to the same value as the higher TCA threshold, then the TCA status can only be INACTIVE or HIGH.
100% HIGH Higher TCA threshold = Lower TCA INACTIVE threshold
TCA status (Used bandwidth)
Furthermore, these rules apply concerning the TCAs and the TCA status: • When a link bundle is created, then initially the TCA status is INACTIVE. • When any of the two TCA thresholds is modified, then the bandwidth utilization is re-evaluated and the TCA status updated accordingly for the affected link bundles. • When the bandwidth utilization changes for a link bundle, then the TCA status is updated accordingly, and TCA event notifications are reported.
...... 2-30 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview Network optimization
...... • When the total available bandwidth of a link bundle changes as a result of provisioning, then the bandwidth utilization is re-evaluated and the TCA status updated accordingly for that link bundle. Bandwidth changes can for example occur due to path setup and path delete operations, restorations, reversion of restoration, line/port failures, and line/port recovery. • When a link bundle is deleted, then a possibly existing TCA for this link bundle is cleared.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-31 Issue 5 July 2008 See notice on first page ONNS Functional overview User-Network Interface (UNI)
...... User-Network Interface (UNI)
Introduction 1675 LambdaUnite MSS systems support a User-Network Interface (UNI) based on the following standards: • OIF UNI 1.0 Release 2: – OIF-UNI1-R2-Common - User Network Interface (UNI) 1.0 Signaling Specification Release 2: Common Part – OIF-UNI1-R2-RSVP - RSVP Extensions for UNI 1.0 Signaling, Release 2 The User-Network Interface (UNI) is an interface which makes it possible for a source client (source UNI-C) to request certain transport services to a destination client (destination UNI-C). These transport services are requested via the Optical Network Navigation System (ONNS) by the UNI network counterpart, the UNI-N.
source source destination UNI-C UNI-N UNI-C
destination UNI-N
Source client Destination connection client connection
ONNS connection
UNI connection
Transport connection UNI control channel
Legend:
UNI-C User-Network Interface - client side UNI-N User-Network Interface - network side ONNS connection An end-to-end connection between two UNI-N ports within the ONNS domain created by ONNS. Please also refer to “Types of connections (from a network topology perspective)” (p. 3-9). UNI connection An end-to-end connection between 2 UNI-Cs consists of a source and destination client connection and an ONNS connection.
...... 2-32 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview User-Network Interface (UNI)
......
Important! 1675 LambdaUnite MSS systems can take on the UNI-N role (Transport NE, TNE).
Transport services The transport services offered over the UNI include: • Connection setup • Connection release (tear-down) • Connection status query
UNI connection setup The creation of a UNI connection can be triggered by a connection create request from the source UNI-C. In this connection create request, the source and destination TNA addresses of the UNI connection must be specified as well as the attributes that describe the service requirements for the connection (signal rate, disjointness, etc.). UNI connection endpoints are identified by Transport Network Assigned (TNA) addresses. An individual data link within a group of links sharing the same TNA address is identified by a logical port identifier at each end.
UNI control channel For each pair of UNI-C/UNI-N connected to each other in an ONNS domain for the exchange of UNI signaling messages exactly one unique logical channel named “UNI control channel” must be defined. This logical channel may be realized by one or more physical communication channels (in-band DCC or out-of-band LAN). As the UNI control channel must support the transport of IP packets, it is often also referred to as IP control channel (IPCC).
No automatic neighbor discovery for UNI ports There is no automatic neighbor discovery between UNI-C and UNI-N. The UNI control channel as well as transport link address information needs to be provisioned manually.
UNI configuration parameters The following interface ports can be configured to be UNI ports: • SDH: – STM-1 – STM-1E – STM-4
...... 365-375-026 Alcatel-Lucent - Proprietary 2-33 Issue 5 July 2008 See notice on first page ONNS Functional overview User-Network Interface (UNI)
...... – STM-16 – STM-64 • SONET: – OC-3 – OC-12 – OC-48 – OC-192 • Gigabit Ethernet (WAN ports): – 1 GbE
Parameter Value(s) Parameter Meaning classification
UNI IP address IPv4 format: Four Node parameter, This parameter specifies the IP dot-separated decimal related to signaling address of the UNI node. This IP values, each in the address is used as signaling range [0...255] controller address for the UNI communication.
UNI network TNA IPv4 Port parameter, type IPv6 related to connection setup NSAP UNI network TNA Network TNA type Port parameter, address dependent related to connection setup
UNI network 32-bit identifier with a Port parameter, logical port value range of related to connection identifier [0...4294967295] setup UNI client node IPv4 format: Four Port parameter, The IP address of the UNI client identity dot-separated decimal related to connection node. values, each in the setup range [0...255]
Transport Network Assigned (TNA) addresses Network connection endpoints are identified by Transport Network Assigned (TNA) addresses. TNA addresses are used to identify network resources. A TNA consists of a type and the value of the address. Possible TNA types are: • IPv4: The TNA address is an IPv4 address • IPv6: The TNA address is an IPv6 address • NSAP: The TNA address is an NSAP address
...... 2-34 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview User-Network Interface (UNI)
...... An IPv4 address is a 4-Byte address represented by four dot-separated decimal values, each in the range [0...255], for example: 129.12.3.178. An IPv6 address is a 16-Byte address represented by eight dash-separated hexadecimal values, each in the range [0...FFFF], for example: AE12-0-0-12-EDFB-89AB-2254- 8A2E. An NSAP address is a 20-Byte address represented by a hexadecimal value in the range [0000000000000000000000000000000000000000... FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF], for example: FFAABBCCDD213141515A6A7EB2D433221100AAFF. In order to distinguish between different ports that are connected to the same network resource (TNA), so-called local Logical Port Identifiers (local LPIDs) can be used. The LPID is part of the TNA. A TNA can consist of more then one LPID, so the LPID identifies a particular port within a TNA. Each node in the network must use different TNAs. It must be avoided, that the same TNA is provisioned in different network elements of the network. Of course within one network element different ports may have the same TNA, but different local LPIDs. Important! Make sure the provisioned TNAs are unique between the NEs of the network.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-35 Issue 5 July 2008 See notice on first page ONNS Functional overview External Network-Network Interface (E-NNI)
...... External Network-Network Interface (E-NNI)
General An E-NNI port is a Network-Network Interface port connected to another E-NNI port in a peer network element in a different domain of the switched network. E-NNI ports run a standardized signaling and routing protocol for the purpose of interworking between control domains. This especially includes multi-vendor interworking as well as end-to-end routing in spite of different operators and different SLAs within the individual domains. 1675 LambdaUnite MSS systems support an External Network-Network Interface (E-NNI) based on the following standards: • OIF E-NNI 1.0: – OIF-E-NNI-Sig-01.0: Intra-Carrier E-NNI Signaling Specification – OIF-ENNI-OSPF-01.0 External Network-Network Interface (E-NNI) OSPF-based Routing - 1.0 (Intra-Carrier) Implementation Agreement
Transport services The transport services offered over the E-NNI include: • Connection setup • Connection release (tear-down) • Connection status query Protection or restoration mechanisms E-NNI inter-domain links can be unprotected or 1+1 MSP/APS protected. However, please note that a network connection wide end-to-end protection is not supported.
Network connection setup For a definition of various types of connections, please refer to “Types of connections (from a network topology perspective)” (p. 3-9). A new network connection can be setup by means of a network connection setup request which is initiated by a management system and sent to the source node of the new network connection. The source node (or “initiator node”) is addressed by the source TNA address. A network connection can be setup between Edge ports with provisioned TNA addresses. If the end point of a network connection is in a different ONNS control domain then the path for the network connection will be calculated using level 1 routing.
...... 2-36 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview External Network-Network Interface (E-NNI)
...... E-NNI routing 1675 LambdaUnite MSS systems support E-NNI routing based on the OIF-ENNI-OSPF-01.0 External Network-Network Interface (E-NNI) OSPF-based Routing - 1.0 (Intra-Carrier) Implementation Agreement. The following graphic serves as a reference for some of the terms and definitions related to E-NNI routing:
Legend:
RA: Routing area Defines a set of transport resources in the network for which the routing applies. A routing area is defined by a set of subnetworks, the links that interconnect them, and the links exiting that routing area. A routing area may contain smaller routing areas interconnected by links.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-37 Issue 5 July 2008 See notice on first page ONNS Functional overview External Network-Network Interface (E-NNI)
......
RC: Routing The routing controller provides the routing service interface and is controller responsible for coordination and dissemination of routing information. A single node in the level 0 area can be configured as routing controller, which advertises all intra-area information of the level 0 area into the level 1, thereby summarizing the complete level 0 area as a single node (“abstract node”, please also refer to “Topology abstraction” (p. 2-42)). TNA: Transport End points, which are not local to a specific ONNS control domain Network Assigned and which are addressable (or reachable) across control domains need a unique identifier. The Transport Network Assigned (TNA) address, together with a logical link identifier and a label is used for this purpose. A TNA address can be associated with a UNI or Edge port. Routing hierarchy A routing hierarchy describes the relationship between a routing area and a containing routing area or contained routing areas. routing areas at the same depth within the routing hierarchy are considered to be at the same routing level. The lowest level in a routing hierarchy, in which all the physical nodes (NEs) and links are visible, is denoted as “level 0”. A routing area, which contains a set of level 0 routing areas is referred to as level 1 routing area. The topology of the level 1 routing area may provide an abstract view, i.e. resources (nodes and links) may not represent physical resources.
E-NNI control channel For the exchange of E-NNI signaling messages between two adjacent E-NNI nodes (adjacent but in different ONNS control domains), a signaling control channel named “E-NNI control channel” must be defined. This logical channel may be realized by one or more physical communication channels (in-band DCC or out-of-band LAN). As the E-NNI control channel must support the transport of IP packets, it is often also referred to as IP control channel (IPCC). ENNI communication channel redundancy Note: Please note that a threefold redundant E-NNI communication channel configuration towards an adjacent E-NNI node consisting of one protected IPCC via DCC on a 1+1 protected E-NNI link (with DCC protection enabled) and one additional IPCC via DCC on an unprotected E-NNI link is not possible. The 1+1 protected IPCC as such is still protected against a single failure within the 1+1
...... 2-38 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview External Network-Network Interface (E-NNI)
...... protected link, but in case of a double failure in the 1+1 protected link, the additional IPCC via the unprotected link will not be used, i.e. communication to the affected neighbor will fail. Usually double redundancy should be sufficient, i.e either one protected IPCC via a 1+1 protected E-NNI link or two unproteced IPCCs via two separate unprotected E-NNI links. In case a threefold redundancy is really needed, it must be realized by three separate IPCCs via three unprotected E-NNI links.
Configurable neighbor relations for E-NNI ports The E-NNI control channel as well as neighbor information for signaling and routing are to be provisioned manually: • For the communication between routing controllers, routing controller adjacencies are to be configured manually. • For the communication between signaling controllers, manual routes towards the subnet of the neighbor domains are to be created.
E-NNI configuration parameters The following interface ports can be configured to be E-NNI ports: • SDH: – STM-1 – STM-4 – STM-16 – STM-64 • SONET: – OC-3 – OC-12 – OC-48 – OC-192 Important! Consistent provisioning of E-NNI configuration parameters is essential in order for E-NNI routing and signaling to work properly!
Parameter Value(s) Meaning
Local link ID 32-bit identifier with a value This parameter is used to identify (from the local node’s range of [0...4294967295] point-of-view) the link to which the corresponding E-NNI port is assigned. This parameter is used in level-1 routing advertisements. Important: Make sure the provisioned values for the local link ID parameter are unique to the routing area.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-39 Issue 5 July 2008 See notice on first page ONNS Functional overview External Network-Network Interface (E-NNI)
......
Parameter Value(s) Meaning
Remote link ID 32-bit identifier with a value This parameter is used to identify (from the remote range of [0...4294967295] node’s point-of-view) the link to which the corresponding E-NNI port is assigned. This parameter is used in level-1 routing advertisements. Local advertised node ID 32-bit identifier represented in This parameter is used to identify (from the local node’s (optional) the format of an IPv4 address point-of-view) the node to which the corresponding E-NNI port is assigned. This parameter is used in level-1 routing advertisements. The combination of local link ID and local advertised node ID identifies the local link end within the level 1 routing area. Remote advertised node ID 32-bit identifier represented in This parameter is used to identify (from the remote the format of an IPv4 address node’s point-of-view) the node to which the corresponding E-NNI port is assigned. This parameter is used in level-1 routing advertisements. The combination of remote link ID and remote advertised node ID identifies the remote link end within the level 1 routing area.
Neighbor signaling IPv4 format: Four dot-separated A logical identification of the neighbor node which is protocol controller (PC) decimal values, each in the range connected via the corresponding port for E-NNI identity [0...255] signaling purposes.
Neighbor signaling IPv4 format: Four dot-separated This parameter specifies the IP address of the remote protocol controller (PC) IP decimal values, each in the range node which is connected via the corresponding port for address [0...255] E-NNI signaling purposes. Routing function Primary This parameter defines if the corresponding node has Disabled level 1 routing controller functionality or not. Routing area ID IPv4 format: Four dot-separated The identifier of the routing area to which the decimal values, each in the range corresponding port belongs. [0...255] Remote routing area ID IPv4 format: Four dot-separated The identifier of the remote routing area the decimal values, each in the range corresponding port is connected to. [0...255] Parent routing area ID IPv4 format: Four dot-separated The identifier of the parent routing area (level 1 routing decimal values, each in the range area) to which the corresponding port belongs. [0...255] Routing controller ID IPv4 format: Four dot-separated The identifier of the level 1 routing controller. decimal values, each in the range [0...255] Routing controller IP IPv4 format: Four dot-separated The IP address of the level 1 routing controller. address decimal values with the following value ranges: [0...223].[0...255].[0...255].[0...255] (0.0.0.0 and 1.1.1.1 are not allowed)
...... 2-40 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview External Network-Network Interface (E-NNI)
......
Parameter Value(s) Meaning
Abstraction model Abstract node The abstraction model is fix preset to “Abstract node” for 1675 LambdaUnite MSS E-NNI ports; please also refer to “Topology abstraction” (p. 2-42). Abstract node ID IPv4 format: Four dot-separated The identifier of the abstract node. decimal values, each in the range This parameter is only applicable if the abstraction [0...255] model is “Abstract node”. Administrative cost (link Numeric string in the value range The provisioned administrative link cost setting for the cost) [0...65535] corresponding port. Link resource class 4 alphanumeric characters with used to globally classify the abstract link the hexadecimal values [00..FF] each corresponding E-NNI port is assigned to for E-NNI routing purposes. The link resource class is also referred to as “administrative group” or “link color”. SRLG identities list Ten numeric strings separated by An SRLG identities list may consist of up to 10 shared dashes, with each numeric string risk link group (SRLG) values. Shared risk link groups in the value range [0...65535] are groups of port connections that share the same risk. Default value: For instance: port connections that terminate on the same card, in the same network element or that share 0-0-0-0-0-0-0-0-0-0 the same fiber duct. Important: Please note that these SRLG settings are currently not evaluated for level 1 routing. Nevertheless, for network planning reasons, and to ensure a smooth upgrade to the first release when SRLG settings will be evaluated for level 1 routing, it is recommended to provision the SRLG identities list. Remote TID Alphanumeric string of up to 20 The NE name (target identifier, TID) of the neighbor characters node connected via the corresponding port. Neighbor detection mode manually provisioned The neighbor detection mode is fix preset to “manually provisioned” for E-NNI ports. The information regarding the adjacencies of E-NNI ports needs to be provisioned manually. Neighbor information for manually provisioned For the communication between routing controllers, signaling and routing routing controller adjacencies must be configured manually.
For the communication between signaling controllers, manual routes towards the subnet of the neighbor domains must be created.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-41 Issue 5 July 2008 See notice on first page ONNS Functional overview External Network-Network Interface (E-NNI)
...... For Edge ports, the following additional parameters apply:
Parameter Value(s) Meaning
Network TNA type IPv4 IPv6 NSAP Network TNA address Network TNA type dependent Local Logical Port 32-bit identifier with a value Identifier (LPID) range of [0...4294967295]
Topology abstraction In a hierarchical routing architecture, topology information of a contained routing area can be summarized (or “abstracted”) for several purposes, such as • to limit the amount of information in order to support scalability, or • to hide information, especially between routing areas of different carriers. Multiple levels of abstraction are possible with the extremes: “no abstraction” and “abstraction of the complete routing area into a single node”. The latter corresponds to the abstract node model which is used for 1675 LambdaUnite MSS systems to represent an ONNS level 0 routing area in the level 1 routing domain. The following figure illustrates different abstraction models.
...... 2-42 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview External Network-Network Interface (E-NNI)
......
Abstract node In the abstract node model the whole control domain is represented by a single abstract node AN with its inter-domain links. Intra-domain links are not visible. The identifiers for the abstract node and the inter-domain links are not identical to the node and link identifiers used within the control domain itself. Furthermore, reachable addresses of the control domain X (not shown in the figure) must be associated with AN. In 1675 LambdaUnite MSS systems, this abstraction model is implemented. Abstract link In the abstract link model the control domain is represented by its border nodes (B1, B2, B3), some abstract intra-domain links (providing connectivity through the CD), and the inter-domain links. The identifiers for the border nodes and inter-domain links may be identical to the identifiers used within the CD itself. The intra-domain links (AL1, AL2, AL3) have in general no 1:1 representation to links in the CD. Furthermore, reachable addresses of the control domain X (not shown in the figure) must be associated with the border nodes B1, B2 or B3.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-43 Issue 5 July 2008 See notice on first page ONNS Functional overview External Network-Network Interface (E-NNI)
...... Multi-domain topology – configuration example The following example network is used to clarify the provisioning actions that must be carried out. The example primarily serves to draw attention on the required consistency of configuration parameters. Consider the following example network:
E-NNI Routing domain (RAID = p.p.p.p)
L2 L3 L1 AN L4 N1* L6 L7 N5* L5 L8
Level 1
Level 0
SC 16-1 SC 2-1 3-1 12-1 i2 i5 i2 i4 SC SC 18-1 i1 i1 N4 i3 37-1 21-1 N2 i6 1-1 4-1 i2 22-1 i3 i3 i4 i5 i6 i5 N1 17-1 13-1 i1 N5 i3 8-1 I-NNI 5-1 i4 19-1 7-1 6-1 36-1 RC i2 N3 i3 RC 16-1 12-1 i1 i4 Domain A 18-1 RC 14-1 Domain B (RAID = a.a.a.a) (RAID = b.b.b.b) Core domain (RAID = c.c.c.c)
Edge port SC Signaling controller
E-NNI port RC Routing controller
I-NNI port RAIDRouting area ID
21-1, 18-1, etc. Port numbers (abbreviated notation; for example: '21-1' represents the port AID '1-1-#-#-21-1')
The configuration settings given in the drawing are examples. The following tables make use of these settings in order to clarify the necessary provisioning. The tables especially serve to visualize the relationship between the parameters, and to emphasize which parameters require consistent provisioning.
...... 2-44 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview External Network-Network Interface (E-NNI)
...... Example configuration of node N1: Edge port (port AID = 1-1-#-#-21-1):
Parameter Setting Port class Edge Network TNA type IPv4 Network TNA address i5.i5.i5.i5 Local Logical Port Identifier (LPID)1 for example: 15
Notes: 1. An LPID is an identifier for a physical port, which is implementation and vendor independent. The LPID is part of the TNA. A TNA can consist of more than one LPID, so the LPID identifies a particular port within a TNA.
Signaling Controller (SC):
Parameter Setting Local information (Local) Signaling PC identity the signaling PC identity of node N1: n1.s.c.id (Local) Signaling PC IP address the signaling PC IP address of node N1: n1.s.c.ip Neighbor information (must be consistent with the local signaling PC configuration in node N2) Neighbor signaling PC identity the signaling PC identity of node N2: n2.s.c.id Neighbor signaling PC IP address the signaling PC IP address of node N2: n2.s.c.ip
Level 1 Routing Controller (RC):
Parameter Setting Routing function Primary Routing area ID (RAID) a.a.a.a Parent routing area ID p.p.p.p Routing controller ID the identity of the Routing Controller in domain A: a.r.c.id
...... 365-375-026 Alcatel-Lucent - Proprietary 2-45 Issue 5 July 2008 See notice on first page ONNS Functional overview External Network-Network Interface (E-NNI)
......
Parameter Setting Routing controller IP the IP address of the Routing Controller in domain A: address a.r.c.ip Abstraction model Abstract node Abstract node ID N1*
Notes: 1. In addition to the listed parameters, for each neighbor domain, the level 1 routing controller IP address needs to be specified (E-NNI manual routes).
E-NNI ports:
Parameter port AID = 1-1-#-#-18-1 port AID = 1-1-#-#-19-1 Setting Port class E-NNI E-NNI Local link ID L1 L5 Remote link ID L2 L6 Local advertised node ID N1* N1* Remote advertised node AN AN ID Neighbor signaling PC the signaling PC identity of the signaling PC identity of identity node N2: n2.s.c.id node N2: n2.s.c.id Neighbor signaling PC IP the signaling PC IP address the signaling PC IP address address of node N2: n2.s.c.ip of node N2: n2.s.c.ip Remote routing area ID c.c.c.c c.c.c.c Administrative cost 1 1 Link resource class 00000000 00000000 SRLG 0-0-0-0-0-0-0-0-0-0 0-0-0-0-0-0-0-0-0-0 Remote TID The NE name (TID) of node The NE name (TID) of N2 node N2
...... 2-46 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview External Network-Network Interface (E-NNI)
...... Example configuration of node N2: Signaling Controller (SC):
Parameter Setting Local information (Local) Signaling PC identity the signaling PC identity of node N2: n2.s.c.id (Local) Signaling PC IP address the signaling PC IP address of node N2: n2.s.c.ip Neighbor information (must be consistent with the local signaling PC configuration in node N1) Neighbor signaling PC identity the signaling PC identity of node N1: n1.s.c.id Neighbor signaling PC IP address the signaling PC IP address of node N1: n1.s.c.ip
E-NNI ports:
Parameter port AID = 1-1-#-#-16-1 port AID = 1-1-#-#-17-1 Setting Port class E-NNI E-NNI Local link ID L2 L6 Remote link ID L1 L5 Local advertised node ID AN AN Remote advertised node N1* N1* ID Neighbor signaling PC the signaling PC identity of the signaling PC identity of identity node N1: n1.s.c.id node N1: n1.s.c.id Neighbor signaling PC IP the signaling PC IP address the signaling PC IP address address of node N1: n1.s.c.ip of node N1: n1.s.c.ip Remote routing area ID a.a.a.a a.a.a.a Administrative cost 1 1 Link resource class 00000000 00000000 SRLG 0-0-0-0-0-0-0-0-0-0 0-0-0-0-0-0-0-0-0-0 Remote TID The NE name (TID) of node The NE name (TID) of N1 node N1
...... 365-375-026 Alcatel-Lucent - Proprietary 2-47 Issue 5 July 2008 See notice on first page ONNS Functional overview External Network-Network Interface (E-NNI)
...... Example configuration of node N3: Level 1 Routing Controller (RC):
Parameter Setting Routing Function Primary Routing Area ID (RAID) c.c.c.c Parent Routing Area ID p.p.p.p Routing Controller ID the identity of the Routing Controller in the core domain: c.r.c.id Routing Controller IP the IP address of the Routing Controller in the core Address domain: c.r.c.ip Abstraction Model Abstract node Abstract node ID AN
Notes: 1. In addition to the listed parameters, for each neighbor domain, the level 1 routing controller IP address needs to be specified (E-NNI manual routes).
Example configuration of node N4: Signaling Controller (SC):
Parameter Setting Local information (Local) Signaling PC identity the signaling PC identity of node N4: n4.s.c.id (Local) Signaling PC IP address the signaling PC IP address of node N4: n4.s.c.ip Neighbor information (must be consistent with the local signaling PC configuration in node N5) Neighbor signaling PC identity the signaling PC identity of node N5: n5.s.c.ip Neighbor signaling PC IP address the signaling PC IP address of node N5: n5.s.c.ip
...... 2-48 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview External Network-Network Interface (E-NNI)
...... E-NNI ports:
Parameter port AID = 1-1-#-#-12-1 port AID = 1-1-#-#-13-1 Setting Port class E-NNI E-NNI Local link ID L3 L7 Remote link ID L4 L8 Local advertised node ID AN AN Remote advertised node ID N5* N5* Neighbor signaling PC the signaling PC identity of the signaling PC identity of identity node N5: n5.s.c.id node N5: n5.s.c.id Neighbor signaling PC IP the signaling PC IP address the signaling PC IP address address of node N5: n5.s.c.ip of node N5: n5.s.c.ip Remote routing area ID b.b.b.b b.b.b.b Administrative cost 1 1 Link resource class 00000000 00000000 SRLG 0-0-0-0-0-0-0-0-0-0 0-0-0-0-0-0-0-0-0-0 Remote TID The NE name (TID) of The NE name (TID) of node N5 node N5
Example configuration of node N5: Edge port (port AID = 1-1-#-#-21-1):
Parameter Setting Port class Edge Network TNA type IPv4 Network TNA address i3.i3.i3.i3 Local Logical Port Identifier (LPID)1 for example: 63
Notes: 1. An LPID is an identifier for a physical port, which is implementation and vendor independent. The LPID is part of the TNA. A TNA can consist of more then one LPID, so the LPID identifies a particular port within a TNA.
...... 365-375-026 Alcatel-Lucent - Proprietary 2-49 Issue 5 July 2008 See notice on first page ONNS Functional overview External Network-Network Interface (E-NNI)
...... Signaling Controller (SC):
Parameter Setting Local information (Local) Signaling PC identity the signaling PC identity of node N5, for example: n5.s.c.id (Local) Signaling PC IP address the signaling PC IP address of node N5, for example: n5.s.c.ip Neighbor information (must be consistent with the local signaling PC configuration in node N5) Neighbor signaling PC identity the signaling PC identity of node N4, for example: n4.s.c.ip Neighbor signaling PC IP address the signaling PC IP address of node N4, for example: n4.s.c.ip
Level 1 Routing Controller (RC):
Parameter Setting Routing Function Primary Routing Area ID (RAID) b.b.b.b Parent Routing Area ID p.p.p.p Routing Controller ID the identity of the Routing Controller in domain B: b.r.c.id Routing Controller IP the IP address of the Routing Controller in domain B: Address b.r.c.ip Abstraction Model Abstract node Abstract node ID N5*
Notes: 1. In addition to the listed parameters, for each neighbor domain, the level 1 routing controller IP address needs to be specified (E-NNI manual routes).
E-NNI ports:
Parameter port AID = 1-1-#-#-36-1 port AID = 1-1-#-#-37-1 Setting Port class E-NNI E-NNI
...... 2-50 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Functional overview External Network-Network Interface (E-NNI)
......
Parameter port AID = 1-1-#-#-36-1 port AID = 1-1-#-#-37-1 Setting Local link ID L4 L8 Remote link ID L3 L7 Local advertised node ID N5* N5* Remote advertised node ID AN AN Neighbor signaling PC the signaling PC identity of the signaling PC identity of identity node N4: n4.s.c.id node N4: n4.s.c.id Neighbor signaling PC IP the signaling PC IP address the signaling PC IP address address of node N4: n4.s.c.ip of node N4: n4.s.c.ip Remote routing area ID c.c.c.c c.c.c.c Administrative cost 1 1 Link resource class 00000000 00000000 SRLG 0-0-0-0-0-0-0-0-0-0 0-0-0-0-0-0-0-0-0-0 Remote TID The NE name (TID) of The NE name (TID) of node N4 node N4
...... 365-375-026 Alcatel-Lucent - Proprietary 2-51 Issue 5 July 2008 See notice on first page
3 3Network engineering and planning
Overview
Purpose Optical Network Navigation System (ONNS) is a system that can be used with some types of NEs to create an intelligent transport network in which all connection management functions are automatically managed by a software module called Network Navigator (NN).
Contents
Specific rules and guidelines concerning the connection setup 3-2 Basic mesh planning 3-7 Transmission aspects 3-9 Shared Risk Link Group (SRLG) 3-15 Cost savings 3-20 ONNS performance monitoring 3-24
...... 365-375-026 Alcatel-Lucent - Proprietary 3-1 Issue 5 July 2008 See notice on first page Network engineering and planning Specific rules and guidelines concerning the connection setup ...... Specific rules and guidelines concerning the connection setup
Traditional cross-connections It is not possible to set up traditional cross-connections with input or output tributaries located on UNI or iNNI ports.
1+1 end-to-end network protection A 1+1 end-to-end network protection can be set up for unidirectional and bidirectional paths and all supported rates. This 1+1 end-to-end network protection is realized as an SNCP/UPSR protected connection, unidirectional and non-revertive or revertive. Whether SNCP or UPSR is used as the protection scheme depends on the interface standard of the input tributaries. The protection path is calculated in a way that no nodes are common to the working and protection path except the A-node and Z-node of the paths. Thus no single line failure can affect both paths. The connection setup request will be rejected, if either path cannot be switched due to topological or capacity constraints.
UPSR/SNCP Termination The system supports the termination of an ONNS circuit onto UPSR/SNCP subnetworks. “ONNS to UPSR/SNCP Termination Support” requests the ability to combine an ONNS connection in its A-node or Z-node with an UPSR ring or an SNCP on the EDGE side. Such an “SNCP/UPSR to meshed” construct as introduced above, i.e. a construct combining an UPSR or SNCP protected path on EDGE ports with an ONNS connection in the ONNS connection’s A-node or Z-node, is referred to as an “ONNS/UPSR-Construct”, in the following abbreviated as OUC. Such an OUC allows a traditional SNCP/UPSR protected part of a network connection to be directly combined with an ONNS part of the network connection (i.e. an NN connection). It is setup in the A-node and in the Z-node of the NN connection independent of each other, i.e. such a OUC may only be setup in the A-node of an NN connection or only in its Z-node or in both. Setup and teardown of such constructs thus are local activities in the A-node or Z-node of an NN connection. The local end of an OUC can be • UPSR/SNCP protected or • unprotected;
...... 3-2 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Network engineering and planning Specific rules and guidelines concerning the connection setup ...... The subsequent ONNS circuit can be • an ONNS unprotected path • an ONNS restoration protected path • an ONNS 1+1 path • an ONNS Y-connection • an ONNS M:N protected connection; The remote end, in another traditional domain, can be • UPSR/SNCP protected or • unprotected or, • in the case of a Y-connection, the Y-legs. Important! Please note the following: • Any EDGE ports involved in an “ONNS to UPSR/SNCP termination support” construct (OUC) must not be in an equipment protection group, • Any EDGE ports involved in an “ONNS to UPSR/SNCP termination support” construct (OUC) must not be in an APS/MSP or BLSR/MSSPRING line protection group.
1+1 MSP/APS Please observe the following rules and guidelines concerning the 1+1 MSP/APS protection support on ONNS applications: • 1+1 MSP/APS is supported on EDGE ports for all those port and tributary rates where 1+1 MSP/APS is supported in traditional applications. • 1+1 MSP/APS is not supported on iNNI ports. • Only the working port of a 1+1 MSP/APS protection group can be an EDGE port, the protection port must be a traditional port. The attempt to create a 1+1 MSP/APS protection group with the protection port being an EDGE port will be denied. Moreover, it is also not possible to configure a port to be an EDGE port if it is currently involved in a 1+1 MSP/APS protection as a protection port. • Nesting of a 1+1 MSP/APS protection with a 1+1 SNCP/UPSR path protection is not supported.
1:1 MSP/APS Please observe the following rules and guidelines concerning the 1:1 MSP/APS protection support on ONNS applications: • 1:1 MSP/APS is supported on EDGE ports for all those port and tributary rates where 1:1 MSP/APS is supported in traditional applications. • 1:1 MSP/APS is not supported on iNNI ports.
...... 365-375-026 Alcatel-Lucent - Proprietary 3-3 Issue 5 July 2008 See notice on first page Network engineering and planning Specific rules and guidelines concerning the connection setup ...... • Only the working port of a 1:1 MSP/APS protection group can be an EDGE port, the protection port must be a traditional port. The attempt to create a 1:1 MSP/APS protection group with the protection port being an EDGE port will be denied. Moreover, it is also not possible to configure a port to be an EDGE port if it is currently involved in a 1:1 MSP/APS protection as a protection port. • Nesting of a 1:1 MSP/APS protection with a 1+1 SNCP/UPSR path protection is not supported.
2-fiber MS-SPRing/BLSR Please observe the following rules and guidelines concerning the 2-fiber MS-SPRing/BLSR support on ONNS applications: • 2-fiber MS-SPRing/BLSR is supported on EDGE ports for all those port rates and interface standards where 2-fiber MS-SPRing/BLSR is supported in traditional applications. • 2-fiber MS-SPRing/BLSR is not supported on iNNI ports. • Only the working port of a 2-fiber MS-SPRing/BLSR protection group can be an EDGE port. The attempt to create a 2-fiber MS-SPRing/BLSR protection group with the protection port being an EDGE port will be denied. Moreover, it is also not possible to configure a port to be an EDGE port if it is currently involved in a 2-fiber MS-SPRing/BLSR protection group as a protection port.
4-fiber MS-SPRing/BLSR Please observe the following rules and guidelines concerning the 4-fiber MS-SPRing/BLSR support on ONNS applications: • 4-fiber MS-SPRing/BLSR is supported on EDGE ports for all those port rates and interface standards where 4-fiber MS-SPRing/BLSR is supported in traditional applications. • 4-fiber MS-SPRing/BLSR is not supported on iNNI ports. • Only the working port of a 4-fiber MS-SPRing/BLSR protection group can be an EDGE port, the protection port must be a traditional port. The attempt to create a 4-fiber MS-SPRing/BLSR protection group with the protection port being an EDGE port will be denied. Moreover, it is also not possible to configure a port to be an EDGE port if it is currently involved in a 4-fiber MS-SPRing/BLSR protection group as a protection port. • 4-fiber MS-SPRing transoceanic protocol (TOP) can’t be used in conjunction with ONNS, i.e. worker ports can’t be EDGE ports.
...... 3-4 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Network engineering and planning Specific rules and guidelines concerning the connection setup ...... M:N shared protection Please observe the following rules and guidelines concerning the M:N shared protection support on ONNS applications: • M:N shared protection is supported between multiple EDGE. All connections pertaining to the M:N shared protection start at a common ingress SONET/SDH EDGE port and end at a common egress SONET/SDH EDGE port. • The supported M:N protection ratios are 1:1, 1:2 and 1:3, i.e. up to three worker channels can be protected by one protection channel. • The protection in an M:N shared protection scheme is revertive. • The capacity for the protection channel is reserved and cannot be used for other shared protections or auto-reroute connections. • Rerouting the connections of an M:N connection group is not allowed. • An M:N grouped connection will only be set up if all required connections (N worker channels + one protection channel) can be set up successfully. • M:N shared protection needs SRLG IDs ≠ 0, if more than one link bundle between two nodes is provisioned to identify the different connection routes. • It is possible to set up an M:N grouped connection even if one or both EDGE ports are only preprovisoned or in a failed state (equipment failure).
STM-1E equipment protection Please observe the following rules and guidelines concerning the STM-1E equipment protection support on ONNS applications: • The creation of 1+1 STM-1E equipment protection groups involving EDGE ports is supported only if these EDGE ports are located on the worker EP155 port unit. • The creation of 1+1 STM-1E equipment protection groups involving EDGE ports is not supported if these EDGE ports are located on the protection EP155 port unit. • The creation of 1+1 STM-1E equipment protection groups involving iNNI ports is not supported. • Unprotected, auto-reroute, and 1+1 end-to-end network protected ONNS connections are supported.
...... 365-375-026 Alcatel-Lucent - Proprietary 3-5 Issue 5 July 2008 See notice on first page Network engineering and planning Specific rules and guidelines concerning the connection setup ...... Gigabit Ethernet grouped connections Please observe the following rules and guidelines concerning grouped GbE connections: • All Gigabit Ethernet grouped connections must start at a common ingress VCG EDGE port and end at a common egress VCG EDGE port. • The ingress and egress VCG EDGE ports of a GbE connection or grouped GbE connection must be of the same interface standard (SDH or SONET). • It is possible to set up a grouped GbE connection even if one or both EDGE ports are only preprovisoned or in a failed state (equipment failure).
...... 3-6 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Network engineering and planning Basic mesh planning
...... Basic mesh planning
Description Shared mesh restoration is based on the idea to have a pool of bandwidth in a network that is made available to service bandwidth so that in the event of a network failure, the service traffic can be switched (cross-connected) to the idle bandwidth. In this case the protection bandwidth must be readily available, meaning that all required network equipment is already established and ready for use. Compared to end-to-end path restoration, link-based restoration is viewed as capable of providing faster protection times. This is due to keeping restoration activity closer to the point of failure, involving fewer nodes, less signaling, greater bundling opportunities, and less propagation delay. It is also viewed as simpler to understand and operate, and as making restoration capacity planning more manageable. Link restoration is a good conceptual fit with the SONET/SDH line protection model which customers are already comfortable with, and it is clearly scalable for large networks.
Instruction Assuming that all links have same capacity and traffic is demanded only between the A- and Z-node. The next two figures shows the differences to plan networks for automatic link restorations. In the 1st example the A-node has an option degree 2 with 2 routes (red/green), the Z-node has an option degree 3 with 3 routes (black/red/green), wherefore only 2 routes available between the A- and Z-node. Result: In this case a restoration protection does not have an advantage from capacity savings (same amount of capacity needed for working and restoration traffic), therefore a 1+1 protection is the better alternative with a 50 ms switching guaranty
...... 365-375-026 Alcatel-Lucent - Proprietary 3-7 Issue 5 July 2008 See notice on first page Network engineering and planning Basic mesh planning
......
B C D A Z
F
E G
In the 2nd example both, A- and Z-node have an option degree 3 with 3 different routes (violet/red/green) are available, therefore a real sharing of restoration capacity is possible. Result: Surviving a single failure each route should be loaded with less than 2/3 capacities. Leaving one route empty and loading the others possible capacity, but in case of a failure more connections can be affected (A- to B-node and D- to Z-node). In this case an additional connection from A- to D-node (dotted) would be favourable. For further risks scenarios in case of failure refer to section “Transmission aspects” (p. 3-9).
B C D A Z
F
E G
...... 3-8 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Network engineering and planning Transmission aspects
...... Transmission aspects
Types of connections In principle, these types of connections are defined: • Permanent connections This type of connection is established by configuring every network element along the path with the required information to establish an end-to-end connection. Provisioning is usually done by means of a management system. The connection is set up NE-by-NE and becomes permanent once established. • Switched connections This type of connection is established on demand by the communicating end points within the ONNS routing domain using a dynamic protocol message exchange in the form of signaling messages which flow across the internal NNI (iNNI) ports within the ONNS routing domain. Switched connections require a set of ONNS protocols and suitable network naming and addressing schemes. • Soft permanent connections This type of connections is a hybrid; it is setup by provisioning the permanent connection at the ingress and egress port of the network, with the network control plane setting up the switching connection in between.
Types of connections (from a network topology perspective) From a network topology perspective, the following types of connections can be distinguished: • Network connection A network connection is an end-to-end connection addressed by means of TNAs. A network connection can be setup using TL1 commands, and can be realized within one domain or across multiple domains. • ONNS connection (or “intra-domain connection”) An ONNS connection is a connection within one ONNS domain. In the context of a network connection it realizes a segment of the network connection within a domain. Regarding the available ONNS connection types, please also refer to “ONNS protection types” (p. 2-11). • Inter-domain connection The inter-domain connection is a connection between two domains. In the context of a network connection it realizes a segment of the network connection between domains.
...... 365-375-026 Alcatel-Lucent - Proprietary 3-9 Issue 5 July 2008 See notice on first page Network engineering and planning Transmission aspects
......
ONNS domain ONNS domain
ONNS domain
Edge port
E-NNI port ONNS ONNS ONNS connection connection connection Transport link Inter-domain Inter-domain connection connection
Network connection
Port connection A port connection is a physical connection between two line ports. It includes the port equipment and fiber connecting the two ports. The port connection is a conduit or transporter of bandwidth. This bandwidth can be segmented into one or more, actual or potential link connections. Each link connection: • is an addressable entity within an NE (bay/shelf/slot/port/tributary) • can carry a customer signal through the port connection i.e. can be part of an end to end path, • can be managed independently of other link connections. With ONNS, network management functions such as topology management and connection management are pushed down into the NE and ports become “network aware ports”.
...... 3-10 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Network engineering and planning Transmission aspects
......
ConnectPoint SONET/SDH NE-1 portID NE-2 Port Connection port portEqptmt
LinkConnection xconn (bandwidth)
Link bundling A link bundle is a collection of one or more Port Connections with similar properties such as minXCrate, cost, propagation delay and SRLG-id’s. Between any two nodes, all port connections with similar properties are grouped into a Bundle. Only transmit bandwidth is advertised to other nodes in the routing domain. Below is a list of criteria used for grouping transmit port connection bandwidth into the same bundle: • same neighboring nodeID, different from the local nodeID • same propagation delay • same administrative cost • same Shared Risk Link Group Settings • same minimum xconn (switching) granularity
Provisionable link cost settings The parameters administrative cost and propagation delay are provisionable per port and are used as bundling criteria. Adjacent ports must be provisioned with the same values. The administrative cost parameters are used to minimize the overall costs during path setup and restoration. The propagation delay (cf. “Propagation delay” (p. 3-12)) parameters may be used in addition to limit the overall propagation delay to a value specified with the path setup request. Note that an optimal path with respect to administrative cost is not always optimal with respect to propagation delay. Note that the minXCrate, SRLG and propagation delay parameters can not be modified when the corresponding port is in use (i.e. has cross-connections or reservations).
...... 365-375-026 Alcatel-Lucent - Proprietary 3-11 Issue 5 July 2008 See notice on first page Network engineering and planning Transmission aspects
...... Propagation delay The propagation delay associated with the link connections can calculate with a base factor of 4.5 µsec/km and can be set in a range from 0 to 255 milliseconds of the optical signal between a port and its neighbor. The summation of the propagation delays for each hop of the end-to-end path must not exceed the specified maximum. This constraint applies jointly to both paths. Some examples for propagation delay time settings are provided in the table below.
City (link) connections Connection Propagation delay distance in [ms] (rounded) Berlin-Hof 200 km 0 Berlin-Munich 500 km 2 Berlin-Florence 1000 km 5 Berlin-Madrid 2000 km 10 Berlin-NewYork 8000 km 40 Berlin-Tokyo 15000 km 75
Restoration priorities Restoration priorities are necessary when the restored path vary significantly in performances in opposite to little performance variations priority settings can be waived. With link restoration, all circuits on a single failed line are restored immediately at the same time. If multiple restorations from the same A node occurs at same time restoration priorities has to be set to avoid collisions. The table below shows the restoration priorities related to queue time and the collision time delay. The restoration priority determines the time until first attempt of restoration. The collision timer is used when setup fails if multiple restorations from the same A node occurs at same time.
Priority TL1 value Queue timer Collision timer High 0, 1, 2, 3 immediately 4 sec. Medium 4, 5, 12 sec. 12 sec. Low 6, 7 36 sec. 36 sec. Rest. Queue 324 sec.
...... 3-12 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Network engineering and planning Transmission aspects
...... The queue of restoration is as follows: • the restoration queue is checked by timer when resources become available. • connections are restored automatically based on restoration priority. • connections stay in queue until resources are available. Note: Restorations has higher priority than requests from the management system. Restoration priorities for SONET The major source of variation in link restoration performance is the number of SONET lines that fail simultaneously. The lines are restored in serial. Important! If high-priority and low-priority connections are mixed and spread across multiple lines which can fail together, it is problematic for priority to affect the order of restoration. The situation is the same for multiple ring failures on the same node.
Cost escalation 1675 LambdaUnite MSS supports a cost escalation function for the administrative cost per link bundle, which increases the costs in the local topology of the source node based on actual load on a link bundle. The cost escalation is used for path calculation in the source node to warrant a balanced and efficient link usage in the ONNS domain. The link capacity control is driven by link costs. The link cost escalation algorithm raises the cost of a link bundle to reduce the attractiveness as the link bundle fills up. The maximum value of link cost is 65553. This is also valid in case of cost escalation function. The cost escalation function is dependent on the used link capacity:
Used link capacity Link cost factor >0%≤ 76 % 1 >70%≤ 76 % 2 >76%≤ 82 % 3 >82%≤ 88 % 4 >88%≤ 94 % 5 >94%≤ 100 % 6
The cost escalation function can be turned off or on per NE; the default setting is on. Important! This function should be set consistently to on or off for all NEs in the ONNS network domain.
...... 365-375-026 Alcatel-Lucent - Proprietary 3-13 Issue 5 July 2008 See notice on first page Network engineering and planning Transmission aspects
...... Interfaces TL1 Interface The interface between the management systems and ONNS is TL1 over TCP/IP. This interface supports ONNS session functions, connection setup and tear down, restoration, notification of connection status changes, and queries of network and connection data.
Supported signal rates The following signal rates are supported for path creation:
SDH SONET
xi Tributary rate xi Tributary rate 3 VC-3 1 STS-1 4 VC-4 3 STS-3c 4c VC-4-4C 12 STS-12c 16c VC-4-16C 48 STS-48c c64 VC-4-64C 192 STS-192c
...... 3-14 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Network engineering and planning Shared Risk Link Group (SRLG)
...... Shared Risk Link Group (SRLG)
Description Shared Risk Link Group (SRLG) feature provides the capabilities to partition the network resources based on the common risk factors and to include or to exclude certain sets of partitioned resources as desired for an end-to-end connection (cf. “Connection constraints” (p. 3-16)). The SRLG feature allows the NN to provide automatic SRLG disjointness between multiple paths for better protection and restoration in NN managed connections. The network operator can provision the NN ports of an NE that are designated for use by NN with SRLG feature. The SRLG iD is one of the attributes of NN ports. A port connection is assigned with SRLG iDs based on common risk factors that it belongs to with the rest of resources in the network. For instance, one SRLG ID can be assigned to classify port connections in the same geographical zone or via the same fiber conduit. A port connection may belong to multiple risk factors. There can be up to ten SRLG iDs assigned per port connection. These values must match on both ends of a port connection that makes up an NN link. The management system will be responsible for provisioning identical SRLG iDs to both ends of a port connection and provide the user-oriented name-strings to users with a mapping between the NN numeric SRLG iDs and the name-strings. One SRLG ID consists of two bytes. The SRLG values for a port connection are used as a criterion to group a number of port connections as a link bundle. All port connections in the same link bundle have the same SRLG iDs.
Instruction Common risk factors are also given, if more SRLG connection uses in places the same way or bi-directional. It has to be considered when planning auto-restoration networks, that, if a failure of the first path occurs the disjoint restoration path can only than restored if it uses in places not the same physical conditions e.g. tunnels or bridges, as shown in the figure below (violet A- to F-node with green A- to E-node) or (red D- to Z-node with violet C- to Z-node), to avoid the same failure cause. Example: • 1st path A-E-G-Z-node (green) failed. • best effort calculated and disjointed restoration path (violet) will be set, but the disconnection is over a bridge where both fibers traverse. • Alternatively should be planned another route connection (violet dotted line A- to F-node) to avoid a restoration path failure with same cause of the first path.
...... 365-375-026 Alcatel-Lucent - Proprietary 3-15 Issue 5 July 2008 See notice on first page Network engineering and planning Shared Risk Link Group (SRLG)
......
B C
][ D ][ A Z
][ ][ F
E G
][Bridge / Tunnel
Connection constraints The ONNS application allows the user to specify constraints for a connection. ONNS supports the following connection constraints: • Exclude node list, to avoid nodes from the path creation. • Explicit node list, defines an exact set of nodes that consists of the path. • Include node list, to include nodes. • Exclusive SRLG, to avoid certain SRLG IDs from the path creation. • Inclusive SRLG, to include certain SRLG IDs • Maximum delay, a summation for each hop of the end-to-end path must not exceed the specified maximum. This constraint applies jointly to both paths. Shared risk link groups are groups of port connections that share the same risk. For instance: port connections that terminate on the same card, in the same network element or that share the same fiber duct. SRLGs are typically used for protected connections in which the two legs should not share a common risk. Multi-port circuit packs When multiple ports of a multi-port circuit pack are used as iNNI ports, they share a common risk that a circuit pack failure affects all ONNS traffic on these ports. Therefore, assign one common SRLG value to all iNNI ports on a multi-port circuit pack. Routing for 1+1 protected connections will then avoid that both paths are routed over the same circuit pack.
...... 3-16 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Network engineering and planning Shared Risk Link Group (SRLG)
...... Path Computation The system supports a command level parameter to influence the path computation logic for ONNS connection setup. Path computation logic for ONNS 1+1 protected connection setup The system supports a command level parameter to influence the path computation logic for ONNS 1+1 protected connection setup. The following modes are supported: • COMPLETE: The two paths of an 1+1 protected connection must be strict node and SRLG disjoint; if such two paths are not available a connection setup request is rejected. • FULLYSRLG: The two paths of an 1+1 protected connection must be strict SRLG disjoint and should be strict node disjoint; if such two paths are not available the system sets up two maximum node and strict SRLG disjoint paths (non-strictness of such a connection is reported as part of the connection information); if such two paths are also not available, the connection setup request is denied. The path computation logic for 1+1 protected connections is COMPLETE per default. The default logic can be changed per path setup to FULLYSRLG. Path computation logic for ONNS auto-reroute connection setup The system supports a command level parameter to influence the path computation logic for ONNS auto-reroute connection setup. The following modes are supported: • COMPLETE: The two paths of a auto-reroute connection (one which is setup, the other which is precalculated) must be strict node and SRLG disjoint, if such two paths are not available a connection setup request is rejected. • FULLYSRLG: The two paths of a auto-reroute connection must be strict node and SRLG disjoint, if such two paths are not available the system accepts also two strict SRLG and maximum node disjoint paths and sets up the primary path (if such two paths are also not available, the connection setup request is denied). Non-strictness of such a connection is reported as part of the connection information. • MAXIMAL: The path computation logic for Auto-reroute connections is MAXIMAL by default. The system in this case sets up two maximum node and SRLG disjoint paths. If maximal degree of disjointness is requested during setup command for a restoration protected connection, the connection is setup independent of the availability at the time of setup of an alternate path with specific characteristics. Important! This behavior does not apply to the path calculation during restoration.
...... 365-375-026 Alcatel-Lucent - Proprietary 3-17 Issue 5 July 2008 See notice on first page Network engineering and planning Shared Risk Link Group (SRLG)
......
1,{} Z B E 1,{} 1,{} 1,{2}
2,{1} 1,{} 1,{} A C
4,{2} F 2,{} 1,{} D G 3,{} 3,{}
cost,{SRLG} SPF: cost 4 FULLYSRLG COMPLETE MAXIMAL
The ONNS path computation algorithm minimizes total path cost, which is the summation of the assigned administrative costs for each hop. If all ports in the network have equal cost, the path computation will minimize number of hops. Cost should generally be set proportional to fiber distance to the neighbor – so that the path computation will minimize total end-to-end fiber distance.
...... 3-18 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ewr niern n planning and engineering Network su uy2008 July 5 Issue 365-375-026 ......
RegionalRegional MeshMesh Network Network Diagram Diagram
DMX in LGT site #1 Dresden Site COL- NN- LGT LGT NBG-ER Ring#1 DMX in DD Cologne CNN Ring#1 Nuremberg Network Center Powercomm site
C-LU#1 NN-LU#1 NN-LU#2 DD-LU#1 lae-uet-Proprietary - Alcatel-Lucent e oieo is page first on notice See CNN Ring#2 DD- LGT SRLG:11, 20 AS- WZ- SRLG:11 LGT LGT Frankf. Site Hof Site DJ HOF
SRLG:10 FM-LU#1 HF-LU#2 HF-LU#1 ...... FM-LU#2 SRLG:20
DJ- DG- LGT SRLG:21, 30 LGT Legend SRLG:21 SRLG:22 SRLG:22, 30 Existing 10G iNNI Link Stuttg. Site Munich Site Existing 10G iNNI Link STG MUC but will be replaced with new 10G Link not sharing same DWDM STG- STG- MUC-LU#2 MUC-LU#1 conduit LU#2 LU#1 SRLG:30 (SRLG) Group Link Risk Shared
Planned 10G iNNI Link STG- MUC and currently not existed LGT -LGT 3-19 Network engineering and planning Cost savings
...... Cost savings
Purpose This section describe the cost savings when operate ONNS applications.
Reduction of network equipment and fiber costs As traffic continues to grow, mesh topologies are becoming more interesting to network operators. For high traffic density, mesh topologies provide lower capital expenditures due to more efficient filling of direct shortest links. In this type of environment, ring-based networks require expensive and complex ring topologies. Meshed networks enable simpler provisioning of circuits in comparison to the complex routing required and stacked interconnected rings. As a consequence, a realistic ONNS implementation requires gateway network elements to support both, ONNS functionality and traditional ring networks. Both methods SDH/SONET rings and ONNS auto reroute use shared protection mechanisms: • in case of SDH/SONET ADMs (single ring closure nodes) long provisioning time occurs by means of overlay ADMs installations and the non-existing connections between rings – for each new span an entire working ring is needed – for each new span an entire protection ring is needed – protection is required for each ring separately; only shared within a ring • in case of efficient ONNS mesh networking flexible symmetric NEs are necessarily – for each new span only a point-to-point link is needed plus – protection links to be added where needed – protection can be shared “between rings”; protection capacity can be added to the network to increase overall availability (multiple failure scenarios) The following scenarios shall demonstrate the advantages of ONNS mesh restoration in opposite to the ring protection scheme.
SDH/SONET ring protection ONNS mesh restoration (auto re-route) 8 working links 7 working links 8 protection links 6 protection links Result: Result: SDH/SONET requires two protected rings ONNS hybrid mesh saves one unused working link and two overlay protection links
...... 3-20 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Network engineering and planning Cost savings
......
Reduction of operational and maintenance costs Meshed topologies provide more flexibility and allow easy enhancement and local elimination of bottlenecks as needed. The automatic topology discovery reduces installation and maintenance to a plug and use operations to prevent mis-connections. A de-centralized path setup reduces the operational burden, cost and time, of manual circuit provisioning.
SDH/SONET ring protection ONNS mesh restoration (auto re-route) SNCP/UPSR SLA protection SNCP/UPSR SLA protection <50 ms Core unprotected STS, VC trails Core meshed protected STS, VC trails Ring or path protection 1+1 permanent 50 ms switching SNCP/UPSR <50 ms 2/4 h MTTR No urgent need to repair Result: Result: Working path failure, traffic is switching Working path failure, traffic is switching to protection path to protection path
...... 365-375-026 Alcatel-Lucent - Proprietary 3-21 Issue 5 July 2008 See notice on first page Network engineering and planning Cost savings
......
SDH/SONET ring protection ONNS mesh restoration (auto re-route) Second failure of the protection path Second failure of the protection path occurs occurs Result: Result: Traffic is lost in consequence of non Traffic is rolling to path restoration for connections between rings multiple failures
Enhanced services Multiple QoS classes are supported for differentiated services as follows: • multiple levels of protection • restoration in case of multiple failure scenarios • enhanced survivability with ONNS 1+1 and restoration as backup
...... 3-22 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Network engineering and planning Cost savings
...... The automatic path setup via UNI speeds up network configuration and enables new service models like dynamic bandwidth flexible services.
Compatibility Hybrid mesh and conventional ring are supported: • SDH/SONET compliant • ONNS activation on a per port basis
...... 365-375-026 Alcatel-Lucent - Proprietary 3-23 Issue 5 July 2008 See notice on first page Network engineering and planning ONNS performance monitoring
...... ONNS performance monitoring
Path performance monitoring
Edge Missing iNNI PM points port Internal quality not measurable. NE1 NE3 Edge port
Ingress PM measurement Ingress PM NE2 point for direction measurement NE3 -> NE1 point for direction NE1 -> NE3 rerouted if failure occurs
Path PM can be enabled for the ingress tributary at the EDGE port of the source node (and for bidi-rectional paths also in the reverse direction for the ingress tributary at the EDGE port of the destination node) Path PM can NOT be enabled for the ingress tributary at the iNNI port of the destination node (and – for bidirectional paths – also in the reverse direction for the ingress tributary at the iNNI port of the source node) References Performance monitoring in general is described in .
...... 3-24 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 4 4The Signaling Communication Network (SCN)
Overview
Purpose This section deals with the basic theoretical background of Signaling Communication Network (SCN) and provides SCN configuration guidelines for 1675 LambdaUnite MSS systems.
Contents
Basic SCN principles 4-2 SCN configurations 4-6 SCN configuration guidelines 4-10 Data communication channels for SCN 4-13 SCN via LAN 4-14 IP LAN provisioning 4-15 ONNS signaling on network layer 4-20
...... 365-375-026 Alcatel-Lucent - Proprietary 4-1 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) Basic SCN principles
...... Basic SCN principles
Overview This section provides an overview of the Signaling Communications Network and describes the type of communication between the NEs in the network and the used protocols. The following subsection describes common SCN configurations. SCN configuration guidelines for 1675 LU products and other related information are provided thereafter.
Purpose of a signaling communications network The SCN provides a robust network that interconnects a number of NEs, for exchange of ONNS and UNI control messages. The SCN is optimized for support of high-speed forwarding of failure recovery messages (failure notification and path setup). Redundancy in the SCN is typically provided through a meshed network at least, where two node-diverse routes exist between any two ONNS NEs. A DCC/LAN data network, that is referred to as the SCN (Signaling Communications Network), is established per ONNS domain. The SCN is separated from the management network. The SCN is the network that ONNS uses to exchange its control messages via a protocol stack with TCP/UDP, IP, MPLS, PPP, DCC, Ethernet-LAN and exchange of UNI messages via a protocol stack with IP, Ethernet-LAN. The service that the SCN provides to the ONNS application is the ability to establish and use TCP and/or UDP connections for the exchange of signaling messages and routing information. Each node in the SCN has a unique IP address for exchanging ONNS control messages and additionally each node with connected UNI clients has a additional unique IP address for exchanging UNI control messages. All IP addresses are distributed by the ONNS Topology Discovery function .
...... 4-2 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) Basic SCN principles
...... MCN and SCN The DCN is divided in physically separated networks. Some of those messages (failure notification and path-setup) require immediate throughput or delivery since they are part of the transport-path restoration mechanism (path protection). The ONNS application requires exchange of messages over the DCC or LAN in a meshed network: • A Signaling Communications Network (SCN) per ONNS domain, is the network that ONNS uses for the exchange of its control messages (via IP-over-PPP-over- HDLC-over-DCC or IP over LAN) between the ONNS-NEs (and between ONNS-NEs and UNI clients). • A Management Communication Network (MCN) per management domain, is the network for the exchange of management information between the managers and the managed NE’s. • The topology of the MCN and the SCN domains is completely independent. The ONNS NE’s are interconnected via Network-Network interfaces (NNI). Over such interfaces the MS-DCC or RS-DCC channel is reserved for the SCN, while the other RS-DCC or MS-DCC channel is available for the MCN. On the non-NNI interfaces all DCCs are available for the MCN. Note: As a rule of thumb, the MS-DCC should be reserved for the SCN, the RS-DCC for the MCN. However, in case redundant MS-DCCs are available, they can of course be used for the MCN. This may especially be useful when a higher bandwidth is required, in case of a database backup or restore for example.
SCN protocols The protocols used in the SCN include: • Transmission Control Protocol (TCP) • User Datagram Protocol (UDP) • Internet Protocol (IP) • Resource ReSerVation Protocol Traffic Engineering (RSVP-TE) • Integrated ISIS (I-ISIS) • MPLS • Point-to-Point Protocol (PPP)
UDP User Datagram Protocol, a connectionless protocol that, like TCP, runs on top of IP networks. UDP provides a procedure for application programs to send messages to other programs with a minimum of protocol mechanism. The protocol is datagram oriented. Unlike TCP/IP, UDP/IP provides very few error recovery services, offering
...... 365-375-026 Alcatel-Lucent - Proprietary 4-3 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) Basic SCN principles
...... instead a direct way to send and receive datagrams over an IP network. Delivery is not guaranteed. There is no protection against out-of-order delivery or packet duplication. It’s used primarily for broadcasting messages over a network.
Integrated ISIS (I-ISIS) The integrated ISIS provides a single routing protocol which will simultaneously provide an efficient routing protocol for TCP/IP, and for OSI. This design makes use of the OSI ISIS routing protocol , augmented with IP-specific information. This design provides explicit support for IP subnetting, variable subnet masks, and external routing. Note that the Integrated ISIS protocol is used both in the SCN and in the MCN. In the SCN, it is run in IP-only mode, while in the MCN, it is run in OSI-only mode. 1675 LambdaUnite MSS products make use of the Integrated ISIS protocol defined in RFC1195.
Multiprotocol Label Switching (MPLS) Multi-Protocol Label Switching (MPLS) requires a set of procedures for augmenting network layer packets with “label stacks”, thereby turning them into ″labeled packets″. Routers which support MPLS are known as “Label Switched Routers”, or “LSRs”. In order to transmit a labeled packet on a particular data link, an LSR must support an encoding technique which, given a label stack and a network layer packet, produces a labeled packet.
Resource ReSerVation Protocol Traffic Engineering (RSVP-TE) RSVP-TE is used to distribute the labels for MPLS label switched paths (LSPs) and as UNI signaling protocol. Important! It is strongly recommended to only connect UNI clients to the system, that fully support RSVP Refresh Overhead Reduction Extensions acc. to RFC2961.
Point-to-Point Protocol (PPP) The DCC Layer 2 for the SCN uses PPP to provide point to point connectivity as a service to the TCP/IP stack of SCN. This PPP service for SCN runs in parallel and independent from the Layer 2 protocol of the management network (MCN). PPP is based on HDLC framing. PPP over HDLC framing uses bit-stuffed framing. PPP is a link layer protocol suite designed for moving datagrams across serial point-to-point links. These protocols are used to establish and configure the communications link, and the network layer protocols, and also to encapsulate datagrams.
...... 4-4 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) Basic SCN principles
...... PPP has several components: • A method for encapsulating multiple protocol datagrams. • The Link Control Protocol (LCP) must be used to establish communications over a PPP link. Each link end sends LCP packets to configure, and test the data link connection. Subsequently, when the link is established, the peer may be verified by authentication.
TCP/IP Service of SCN The TCP/IP protocol of the stack for the Signaling Communications Network (SCN) runs independent and in parallel with the TCP/IP stack of the Management Network (MCN). It is able to interoperate with MPLS, I-ISIS, PPP, Ethernet LAN. It consists of TCP, IP, ICMP, ARP and RDP. The reliable TCP connection is provided via sending the IP packets over a single route or over two diverse routes in parallel, as controlled by the application.
SCN neighbor map Provides information for all SCN neighbors over MS-DCC and LAN2 and LAN3, for those interfaces that are assigned to the SCN stack. Only neighbors that are available as valid route are indicated.
Management protocol: TL1 The management of 1675 LU products is based on the use of the Transaction Language 1 (TL1, defined by Telcordia Technologies, formerly Bellcore, standards) on the OSI application layer. Please also refer to the 1675 LambdaUnite MSS TL1 Reference Manual.
...... 365-375-026 Alcatel-Lucent - Proprietary 4-5 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) SCN configurations
...... SCN configurations
SCN functionality The Signaling Communications Network (SCN) is IP-only. It represents the signaling network between ONNS nodes and ONNS nodes and UNI client nodes (if present). ONNS signaling and UNI signaling are using different IP stacks and therefore having seperate IP adressing. The topology of the SCN between ONNS nodes maps not always one-to-one to the transmission network as known by the ONNS, because DCC must not be enabled between all ONNS-neighbors and there are also LAN ports available for SCN usage. UNI clients are connected via the LAN ports to the SCN. The SCN functionality comprises the following: • The SCN is optimized for response time (real time behaviour). It has priority over the MCN. • The SCN supports the I-ISIS routing protocol. • Support for a single-area I-ISIS network, with a single SCN node per NE, in the SCN. • The SCN supports IP over PPP, with HDLC framing over DCC over NNI-ports and IP over LAN ports. • A TCP socket interface is used by ONNS, to establish a TCP/IP connection over each link between ONNS-neighbors. • An UDP socket interface is provided to ONNS for flooding of the transport-network topology and capacity through the ONNS network. UDP is also used for link defragmentation • The IP address (Router-Id) of the ONNS-neighbor is provided to the SCN by the neighbor discovery function. This function is part of ONNS and will discover neighbor information via the J0 overhead byte or via manual configuration. • The IP address of the UNI client nodes is provided to the SCN via manual configuration. • Calculation of two routes between NEs (referred to as A nodes and Z nodes) in the SCN, for every source/destination pair of ONNS transmission paths.The two node diverse routes are determined by iISIS and are established via RSVP-TE as protected 1+1 MPLS LSP (label switched path) pair. • The MCN and the SCN are separate networks. • The SCN supports LAN. A LAN cannot be shared between the SCN and the MCN. LAN1 is reserved for MCN. LAN2 and LAN3 can be assigned to SCN or to MCN. • Non-ONNS sub-networks can be embedded in an ONNS network domain (as between F and G in the figure below). This requires manual ONNS neighbor provisioning and LAN inter-connection of the ONNS-neighbors via external equipment. The external equipment must support the SCN protocols as listed in “SCN protocols” (p. 4-3), especially I-ISIS.
...... 4-6 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) SCN configurations
......
SCN D E A Z Non-ONNS Network
Non-ONNS F G Network LAN External IP-router
TCP-connection with MPLS-forwarding, for failure notification messages
TCP connection between NN-neighbours
Integrated ISIS routing for IP The I-ISIS packet formats explicitly require that OSI-style addresses of routers appear in the I-ISIS packets. For example, these addresses are used to determine area membership of routers. It is therefore necessary for all routers making use of the I-ISIS protocol to have OSI style addresses assigned. For IP-only routers, these addresses will be used only in the operation of the I-ISIS protocol, and are not used for any other purpose (such as the operation of BGP, ICMP, or other TCP/IP protocols). The Integrated I-ISIS protocol supports point-to-point links over DCC channels. The Integrated ISIS protocol supports LAN links using encapsulation according to RFC 894 / 8802.2 (ANSI/IEEE 802.2).
IP routing via SCN DCC channels Per SCN DCC channel on an I-NNI-port an IP-route to the DCC-neighbor is available when all four conditions as listed below are met: • The DCC is provisioned as Enabled for SCN. • The neighbor IP-address is available from the ONNS application • The physical link is up. • The ISIS-adjacency over the DCC subnet is up. The route to the neighbor is correlated with the existence of an ISIS-adjacency over that DCC, to make sure that bi-directional connectivity is available over the DCC. The IP-route to an SCN-DCC is immediately removed or de-activated, when one of the conditions for this route is removed as listed below: • The DCC is provisioned as Disabled for SCN. • The neighbor IP-address not available (any more) from the ONNS application. • The physical link is down.
...... 365-375-026 Alcatel-Lucent - Proprietary 4-7 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) SCN configurations
...... MPLS based 1+1 packet protection 1675 LambdaUnite MSS systems support MPLS based 1+1 packet protection in accordance with the ITU-T Rec. G.7712/Y.1703 (03/2003) and the IETF RFCs 3031, 3032 and 2702. Among others, the SCN is used to signal path setup, path failures and path restorations within the ONNS network. In principle, the SCN is independent from the transport network. However, as the SCN often uses embedded communication channels (DCCs), parts of the SCN topology can be identical with parts of the transport network. In the example in the following figure, the transport network topology is identical with the SCN, except the SCN connection between NE A and NE C. For this connection there is no corresponding transport connection.
In case of a path failure the Z-node of the ONNS connection signals the path failure back to the A-node which is responsible for the path restoration. If, for example, an ONNS path from NE B to NE C fails, then the resulting message is lost because the failed transport connection is, at the same time, used to transport the path restoration message. In an MPLS based 1+1 packet protection configuration, the nodes are setup as MPLS label switch routers (LSRs) and can provide a pair of pre-setup label switched paths (LSP) for critical messages. 1+1 LSPs are established across the network over node-diverse routes. RSVP-TE is used for label distribution. Important! In case that the node-disjoint paths are routed between two adjacent nodes connected via two or more parallel link connections, a pair of these parallel link connections will be selected by the “Constrained Path Computation” algorithm.
...... 4-8 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) SCN configurations
...... The resulting LSPs are still node-disjoint. However, due to the parallel link connections, they share the same risk, in case of a cable break for example. Node-disjointness of two paths between two end nodes A and B means that there are no common intermediate nodes for these two paths. For the special case that the nodes A and B are adjacent nodes, it cannot be ruled out that parallel link connections are used for the two paths. The following figure illustrates the functional principle of MPLS based 1+1 packet protection, using the same path failure scenario as in the example above. The path fail message is sent redundantly via NE A and NE D via maximum disjoint routes.
...... 365-375-026 Alcatel-Lucent - Proprietary 4-9 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) SCN configuration guidelines
...... SCN configuration guidelines
ONNS SCN IP address This is the IP address for the ONNS HOST, in the ONNS application network and in the SCN (independent IP address). It is also used as the RouterID for the ONNS node. The ONNS SCN IP address is unique within a SCN domain. Important! If the ONNS SCN IP address is not configured the whole ONNS application cannot be enabled. Important! When configuring ONNS SCN IP addresses there are no validations applied in the NE nor in the management systems (WaveStar® CIT or OMS) to deny invalid values or value ranges (e.g. values 0.0.0.0 or 1.1.1.1) or check the uniqueness of the ONNS SCN IP address within a domain. ONNS SCN IP addresses not observing the following configuration rules would be accepted which could lead to unpredictable behavior of the ONNS network. Therefore, please be sure to observe the following configuration rules. The ONNS SCN IP address can be provisioned to any value in the range 0.0.0.0 to 223.255.255.255, with the following exceptions: • The ONNS SCN IP address shall not be in the range 224.0.0.0 to 255.255.255.255. Addresses in the range 224.0.0.0 to 239.255.255.255 are multicast group addresses. Addresses in the range 240.0.0.0 to 255.255.255.255 are reserved special case addresses. • The ONNS SCN IP address shall not be 0.0.0.0 or 1.1.1.1 • The first (most significant) number in the IP address shall not have the value 127. The IP addresses starting with 127 (127.x.x.x) are loopback addresses. • With the introduction of the MPLS Packet 1+1 Protection it should be verified that: SCN IP Adresses are unique with respect to the last 12 bits. This corresponds to 4095 unique addresses. The uniqueness can be checked by checking that the result of operating
SCN network topologies Below some examples of valid SCN topologies. Out-Of-Band, with two routers next to each ONNS-node to support diverse route between all ONNS SCN-neighbors
...... 4-10 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) SCN configuration guidelines
......
External router
D ONNS node D E A Z SCN DCC FG LAN
In-Band DCC-channels with overlay backbone of external equipment. Rings as in Legacy SDH/SONET with dual-node interworking between the rings.
E F B H External router C J A D G D ONNS node Z M P SCN DCC K L N O Q S LAN
In-Band DCC channels and some Out-Of-Band control channels.
Link D E A Z
F G
External router ONNS node X Y D SCN DCC
LAN
Important! The external routers X and Y must support the SCN protocols as described in “SCN protocols” (p. 4-3).
...... 365-375-026 Alcatel-Lucent - Proprietary 4-11 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) SCN configuration guidelines
...... SCN design rules Observe the following rules when creating an SCN: 1. Generally, it is recommended to configure the SCN topology in such a way, that for any pair of nodes which are directly connected on transmission layer at least one direct SCN communication channel between them (via DCC or LAN) should be configured. One additional LAN in parallel to DCC may be added. 2. If for any reason the SCN topology cannot be realized as recommended in item 1, then there should be at least two node-diverse SCN routes between any two ONNS nodes. 3. Be careful with SCN links on multi-port circuit packs (may fail simultaneously, single point of failure (SPoF)) 4. If only one LAN is used for SCN, the IP address of the LAN interface may be set identical to the ONNS SCN IP address (refer to “ONNS SCN IP address” (p. 4-10) ). 5. Additionally, it is recommended to configure the MCN topology for a capacity as large as possible. Whenever possible, use the MS-DCC for the MCN.
...... 4-12 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) Data communication channels for SCN
...... Data communication channels for SCN
Exchange of network management information Network management information can be exchanged between SONET/SDH network elements via Data Communication Channels (DCCs). The ONNS NE’s are interconnected via I-NNI-interfaces. Over such interfaces the MS-DCC can be used for the SCN, while the RS-DCC channel is available for the MCN. On the non-NNI interfaces all DCC channels are available for the MCN. Additional SCN interconnections can be made via LAN. The following figure illustrates the functional principle.
Fiber-pair, with DCC Link DCC D SCN TCP connection, used in the E diverse routes from Z to A EDGE EDGE TCP connection ports A Z ports The Z-node and the A-node are termination points for Z a NN (Network Navigator) transport path. F G
Each enabled SCN-DCC in a link provides connectivity to the neighbor and the routing table provides the information that such a DCC can be used to reach the IP-address of the DCC-neighbor. The DCC-neighbor is equal to the ONNS neighbor, and the IP-address of that neighbor is made available by the ONNS application. When the fiber is cut the routing information towards the embedded SCN-DCC is immediately removed, so that the still available links to the neighbor are used for IP-forwarding.
Termination of Data Communication Channels Inter connectivity with the neighbor is only available, when the related DCC is also Enabled for SCN on the neighbor NE.
Enabling of DCCs for SCN When a circuit pack is inserted into a slot, the RS/MS-DCC on a port is in disabled state. Each RS/MS-DCC has to be enabled explicitly on each port. The MS-DCC channels of any optical interface port can be enabled for SCN, as long as • the optical port is (pre-)provisioned • DCC channels are not related to MCN. A Data Communication Channel can be enabled for SCN manually by user provisioning.
...... 365-375-026 Alcatel-Lucent - Proprietary 4-13 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) SCN via LAN
...... SCN via LAN
Overview The LAN interfaces LAN2 and LAN3 are available for SCN. These two LAN interfaces support the Ethernet protocols according to the specification for IP over LAN. It is also possible to assign LAN2 and/or LAN3 to the UNI node or E-NNI node. Refer to “UNI node” (p. 4-21) or “E-NNI node” (p. 4-22), respectively.
SCN transport over LAN The neighbors on the LAN that run the integrated ISIS (I-ISIS) routing protocol for IP-routing are reported via the user interface. Only IP-adjacencies are available in the SCN. Therefore, any MCN nodes that only route OSI, are not shown as LAN-neighbors.
SCN LAN neighbors The reason to show LAN-neighbors is to identify the physical structure of the LAN, for an easy check that the LAN configuration is according to the network design. The I-ISIS protocol is used for neighbor identification, and the SID and LAN-IP-address are reported. All neighbors that report itself on the LAN via an IP adjacency of the I-ISIS protocol are reported with their SID and their LAN IP-address. The SID is made available to guarantee that a unique identification is available per node on the LAN. Per LAN neighbor the following parameters are reported: • SID (12 Hex digits, representing the 6 bytes of the SID • IP-address = 0.0.0.0 to 225.255.255.255 (4 decimal numbers) or an empty string. Only the neighbors for the specified LAN (LAN2 or LAN3) are reported.
Related information Please also refer to: • “IP LAN provisioning” (p. 4-15)
...... 4-14 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) IP LAN provisioning
...... IP LAN provisioning
Basic IP LAN provisioning The IP LAN provisioning data consists of an IP address and an IP subnetwork mask. The IP address identifies the interface itself, whereas the subnet mask defines - in conjunction with the IP address - the IP subnet that is reachable via the LAN. The subnetwork mask is a 32-bit value containing 1-bits for the subnet ID and 0-bits for the host ID. If, for example, the link address is 192.168.1.1 and the subnetwork mask is 255.255.255.0, then the subnetwork in which the LAN operates is 192.168.1. Thus the host can reach every other host with an IP address 192.168.1.1 - 192.168.1.255 via the LAN. Another way of specifying the combination IP address / subnetwork mask is acc. to the following syntax: IP-Address/subnet-id-size. For example, the combination IP address 192.168.1.1 with subnet mask 255.255.255.0 could be written as 192.168.1.1/24. Additionally to the LAN IP addresses and LAN subnetwork masks the IP address of the default router is provisonable. In the absence of manually provisioned static routes and integrated ISIS, the IP routing table of the NE consists of: • One static route for each provisioned IP LAN consisting of IP address and subnetwork mask. • One static route for the default router consisting of the default router’s IP address and a subnetwork mask of “0.0.0.0”. This static entry is only present if a default router has been provisioned. When the NE sends out an IP packet, routing is performed according to the following rules: 1. Search the IP routing table for an entry that matches the complete destination IP address. If found, send the packet to the associated interface. 2. Search the IP routing table for an entry that matches just the destination subnet. If found, send the packet to the associated interface. If there are several matches the match with the longest subnetwork mask will be selected (e.g. a match with /24 is preferred over a match with /16). 3. Send the packet to the default IP router (if provisioned). Important! The NE can forward IP packets to the default router only if the default router is reachable by the NE. Thus the default router must be part of a subnetwork of an IP LAN.
...... 365-375-026 Alcatel-Lucent - Proprietary 4-15 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) IP LAN provisioning
...... LAN Routing Entry and LAN Status Provisioning an IP LAN results in adding a static route in the NEs IP routing table. This route is independent from the link status of the LAN, i.e. the route is not removed in case the LAN gets disconnected and fails. This means that the NE will try to forward IP packets over a LAN no matter whether the LAN is operational or not.
Several LANs operating in the same or overlapping IP subnetwork In case LAN 2 and LAN 3 are provisioned to operate in the same subnetwork the NE will not necessarily reply to incoming IP packets on the LAN from which it received the packet, but will reply on any of the two LANs. This is correct behavior as acc. to the routing table both LANs reach the same subnet and thus it does not matter which one to use. Important! It is not recommended to operate both LANs in the same or overlapping IP subnetwork as this does not protect against LAN failures and there is currently no application seen that benefits from this configuration.
IP LAN provisioning and integrated ISIS For LANs which are assigned to the SCN node and configured to the IP-only mode, integrated ISIS is used as the OSI and IP routing protocol. Thus I-ISIS adds and removes routing information in the IP routing table as shown in the following example:
...... 4-16 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) IP LAN provisioning
......
Note that the IP routing tables given in this and the following figures show the entries related to the LAN which is shown in the figures only, and that I-ISIS has added a point-to-point link (subnetwork mask 255.255.255.255). In case the LAN fails I-ISIS will detect that the link went down and will remove “its” entries again:
...... 365-375-026 Alcatel-Lucent - Proprietary 4-17 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) IP LAN provisioning
......
I-ISIS, however, will not remove the static routes which have been added through the IP LAN provisioning, thus the NE will still try to forward IP packets via the LAN, although the link is down. Important! In order to have all IP routing entries for a LAN controlled by I-ISIS it is required to provision the subnetwork mask of the IP LAN as 255.255.255.255. This is recommended for all SCN applications using LANs as part of the signaling plane. Example with 255.255.255.255 as the subnetwork mask With 255.255.255.255 as the subnetwork mask the example would change to:
...... 4-18 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) IP LAN provisioning
......
The static route caused by the LAN provisioning tells the NE only that it can reach itself via the LAN 5 (the NE would never use a LAN interface to send IP packets to itself but use its loopback interface). Thus in case the link fails the NE assumes that it can reach no other IP node via the LAN.
...... 365-375-026 Alcatel-Lucent - Proprietary 4-19 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) ONNS signaling on network layer
...... ONNS signaling on network layer
Introduction This section provides a summary of the ONNS signaling on network layer (OSI layer 3), including a description of the specific SCN extensions for UNI and E-NNI.
ONNS signaling One important aspect of ONNS signaling, that differs from signaling of e.g. IP or MPLS routers, is that the topology of the transport network and the topology of the signaling network can differ significantly. Additionally ONNS distinguishes the management control network (MCN), which is used for communication with management systems, from the signaling network (SCN) which is used for ONNS signaling. The following figure shows an example network with 5 nodes. The gray bars between the NEs represent physical connectivity, for example SDH/SONET links, whereas the three line types (dotted lines, dashed lines, solid lines) show adjacencies for the different planes: • Solid lines for the MCN • Dotted lines for the SCN • Dashed lines for the transport plane
NE 1
NE 2 NE 3 NE 4
NE 5
Although each plane has connectivity to all nodes, the topologies of the planes are completely different:
...... 4-20 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) ONNS signaling on network layer
......
NE 1 NE 1 NE 1
NE 2 NE 3 NE 4 NE 2 NE 3 NE 4 NE 2 NE 3 NE 4
NE 5 NE 5 NE 5 MCN SCN Transport
ONNS domain border interfaces In addition to the connectivity between the three planes within an ONNS domain, the ONNS signaling is of importance for ONNS domain border interfaces, such as external network to network interfaces to other domains (E-NNI) and user network interfaces (UNI).
CD2/ RA2 B7 B4 B5 B6
B1 TNA 1 E-NNI UNI-C B2 B8 TNA 2 UNI-C T1 CD1/ RA1 CD3/ T2 B3 B9 RA3
Please note that ONNS domain-external communication is not done by the SCN, but by special nodes, the so-called E-NNI and UNI nodes (here, the term “node” refers to a separate instance of the communications stack, not to a network element); please also refer to “SCN connectivity” (p. 4-22). In the 1675 LambdaUnite MSS ONNS implementation, E-NNI and UNI nodes are separate architectural entities and therefore separately described. UNI node The UNI node is implemented as a separate communications stack, which supports the RSVP-TE signaling protocol over IP via LAN or DCC. The IP stack runs as a UNI node, apart from the 8 MCN nodes and the SCN node in the 1675 LambdaUnite MSS
...... 365-375-026 Alcatel-Lucent - Proprietary 4-21 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) ONNS signaling on network layer
...... NE. When the UNI node ID (IP-address) is provisioned, the UNI node is automatically created. LAN interfaces and DCC channels on UNI ports can be assigned to the UNI node. The UNI node is available in the system, when a valid IP address has been provisioned as UNI node ID. The system allows to provision the UNI Node ID only if a valid ASON IP-address has been provisioned. Removal of the UNI Node ID (IP address) is not supported. The UNI node is not internally interconnected to one of the MCN nodes or the SCN node in the NE. It is possible to assign LAN2 and/or LAN3 and/or DCCs of a UNI port to the UNI node. The system allows to enter manual routes for LAN ports assigned to the UNI node.
Source UNI UNI-C-C Source UNI UNI-N-N Destination UNI UNI-N-N Destination UNI UNI-C-C (Client NE) (TNE) (TNE) (Client NE)
Control Channel (LAN) Control Channel (LAN)
Transport Connection
UNI UNI UNI UNI
UNI Control ChannelSCN UNI Control Channel
E-NNI node The E-NNI node is implemented as a separate communications stack, which supports the RSVP-TE signaling protocol over IP via LAN or DCC. The E-NNI node is available in the system, when a valid IP address has been provisioned as the signaling protocol controller (PC) IP address. Removal of this signaling PC IP address is not supported. The E-NNI node serves two purposes: • Enable data exchange between two signaling controllers (SCs) • Enable data exchange between two routing controllers (RCs)
SCN connectivity The SCN interconnects all ONNS NEs within an ONNS domain. Its purpose is to transport ONNS signaling and routing messages. As the ONNS signaling and routing messages are IP based, the SCN establishes IP connectivity between all SCN nodes...... 4-22 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) ONNS signaling on network layer
...... The SCN is physically separated from the MCN as SCN and MCN do not use identical (layer 2) links. They can both use one and the same SDH/SONET link, but then the SCN uses the MS-DCC and the MCN uses the RS-DCC. The ONNS domain-external communication is not done by the SCN, but by the UNI and E-NNI nodes. The UNI node facilitates the communication between the client-side and the network-side UNI. The E-NNI nodes facilitate the communication between different domains. The following figure depicts the reachability of the SCN IP forwarding:
ONNS SCN node Domain IP Stack Application Application L1 - L3 SCN UNI UNI ENNI SCN node node node node Client IP Stack IP Stack IP Stack IP Stack SCN L1 - L3 L1 - L3 ONNS L1 - L3 L1 - L3 node Border NE Domain Border NE IP Stack L1 - L3
SCN forwarding reachability
Please note that the SCN has IP level connectivity to the E-NNI IP stack, whereas there is no IP level connectivity to the UNI IP stack.
Visibility of IP subnets outside the ONNS domain The SCN interconnects all SCN nodes and E-NNI nodes within an ONNS domain (see the reachability of the SCN IP forwarding above). For E-NNI, an extended visibility of the SCN is required, so that it is aware of IP subnets outside the ONNS domain. Nevertheless, the IP forwarding is still restricted to within the ONNS domain. The following figure depicts the IP subnets that are known to the SCN:
...... 365-375-026 Alcatel-Lucent - Proprietary 4-23 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) ONNS signaling on network layer
......
ASON SCN Domain node
UNI SCN UNI ENNI SCN Client node node node node ASON SCN Border NE Domain Border NE node
IP Subnets known by the SCN
E-NNI communication For E-NNI communication it is required to have IP connectivity between nodes which are located in different ONNS domains. The IP connectivity to other ONNS domains can be achieved by means of E-NNI manual routes, which can be created by manually provisioning the neighbor information, that is the respective signaling controller and routing controller IP addresses of the communication partners within other ONNS domains.
SCN node manual route info propagates SCN ENNI SCN E-NNI links as external reachable node node node networks SCN Border NE node
E-NNI links con- figured as manual routes into the E- NNI node
...... 4-24 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) ONNS signaling on network layer
...... Each border NE that has one or several E-NNI manual routes, instantiates an E-NNI node to which these links are attached. Internally the E-NNI node has IP level and application level connectivity to the SCN node. Routing controller to routing controller connectivity
Domain #1 Domain #2
RC Application SC Application SC Application RC Application SCN SCN ENNI ENNI SCN SCN node node node node node node IP Stack IP Stack IP Stack IP Stack IP Stack IP Stack L1 - L3 L1 - L3 L1 - L3 L1 - L3 L1 - L3 L1 - L3 RC NE #1 Border NE #1 Border NE #2 RC NE #2
In case a routing controller in one domain wants to communicate with a routing controller in another domain, then it sends out IP packets with the destination address set to the SCN IP address of the destination routing controller. It passes the IP packets to the IP stack of its SCN node (RC NE #1) which forwards the IP packets to the border NE (Border NE #1). Inside the border NE the IP packet is forwarded from the IP stack of the SCN node to the IP stack of the E-NNI node, which forwards the packets via an E-NNI link to the foreign domain. Inside the foreign domain the IP stack of the E-NNI node (Border NE #2) receives the packets and forwards them to the IP stack of the SCN node within the NE, which forwards the packets to the destination. When the packets arrive at the destination (RC NE #2) the IP stack of the SCN node passes the packets to the application.
...... 365-375-026 Alcatel-Lucent - Proprietary 4-25 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) ONNS signaling on network layer
...... Signaling controller to signaling controller connectivity
Domain #1 Domain #2
RC Application SC Application SC Application RC Application SCN SCN ENNI ENNI SCN SCN node node node node node node IP Stack IP Stack IP Stack IP Stack IP Stack IP Stack L1 - L3 L1 - L3 L1 - L3 L1 - L3 L1 - L3 L1 - L3 RC NE #1 Border NE #1 Border NE #2 RC NE #2
If a signaling controller in one domain wants to communicate with its peer signaling controller in another domain, then it sends out IP packets with the destination address set to the E-NNI node IP address of the destination signaling controller. It passes the IP packets to the IP stack of its E-NNI node (Border NE #1) which forwards them via the E-NNI link to the peer signaling controller. By examining the destination IP address the IP stack of the E-NNI node (Border NE #2) determines that the packets have reached their final destination and passes them to the application. Important! It is important to note that the IP address of a signaling controller is the IP address of the E-NNI node. The IP address of a routing controller is a separate IP address, which identifies the routing controller application on the SCN node.
E-NNI routing In each ONNS domain one node is defined that represents the whole domain. This node is called the routing controller (RC). The RC performs an abstraction of the whole domain, so that a domain can be considered like a single node, in which the node itself represents the domain and the domain border links are the links of this abstract node:
...... 4-26 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) ONNS signaling on network layer
......
RC2
RC1
RC3
B4 B7 B5 B6 B1 B2 RA4 B8 T1 T2 TNA 1 B3 B9 TNA 2
The routing controllers use OSPF to share the link states of their domains between each other, so that each routing controller has a complete view of all domains and the link states - including traffic engineering information - between the domains.
OSPF LSA
RC2
RC1 OSPF LSA RC3 OSPF LSA
B4 B7 B5 B6 B1 B2 RA4 B8 T1 T2 TNA 1 B3 B9 TNA 2
How nodes within one ONNS domain can exchange IP packets with nodes within another ONNS domain is described in the section “E-NNI communication” (p. 4-24).
...... 365-375-026 Alcatel-Lucent - Proprietary 4-27 Issue 5 July 2008 See notice on first page The Signaling Communication Network (SCN) ONNS signaling on network layer
...... UNI communication In contrast to E-NNI, where a node inside an ONNS domain must be able to communicate with a node inside another ONNS domain, the communication with an UNI client (UNI-C) is done exclusively by the node to which the UNI-C is attached (the UNI-N):
Legend:
LC Link Connection (ITU-T Rec. G.805) SNC SubNetwork Connection (ITU-T Rec. G.805)
Important! Please note that network connections over UNI and E-NNI ports (as shown in the diagram) are currently not supported. UNI provisioning and reachability Therefore, in contrast to the E-NNI, there is no need to propagate the external UNI-C reachability inside the SCN domain. In analogy to the E-NNI, the SCN is responsible for communication inside the ONNS domain, but the communication with the UNI clients is done by a separate IP stack, implemented as a UNI node (see “UNI node” (p. 4-21)). The IP stack of the SCN node has no IP connectivity to the IP stack of the UNI node. Information exchange between the SCN node and the UNI node is done on application level.
...... 4-28 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 The Signaling Communication Network (SCN) ONNS signaling on network layer
......
...... 365-375-026 Alcatel-Lucent - Proprietary 4-29 Issue 5 July 2008 See notice on first page
5 5ONNS Management
Overview
Purpose This chapter gives a short overview of the two input management systems, the local WaveStar® CIT and the Optical Management System (OMS). This chapter gives a short overview how to use ONNS applications
Contents
Operating the ONNS via the WaveStar® CIT 5-2 Operating the ONNS via Optical Management System (OMS) 5-4 Connection and path state definitions 5-8
...... 365-375-026 Alcatel-Lucent - Proprietary 5-1 Issue 5 July 2008 See notice on first page ONNS Management Operating the ONNS via the WaveStar® CIT
...... Operating the ONNS via the WaveStar® CIT
Overview The Graphical User Interface (GUI)oftheWaveStar® CIT is one means of accessing the Optical Network Navigation System (ONNS) to conduct operational activities efficiently. The GUI provides the user with a browser based interface to the Optical Network Navigation System. The ONNS system component name is often shortened to NN.
Functional Components The Optical Network Navigation System (ONNS) GUI consists of the following components: • Network Map • Network Discovery and Resource Management • Connection Management
Network Map The Network Map provides you with a view of the managed domain. The map provides a tool/menu bar providing the capability to conduct the necessary network operations. The map displays all the nodes and links with their respective labels that make up the network. The ONNS view Network Map allows you to: • Navigate through all major components of the application • Perform provisioning tasks and other major operational functions • View Links and connections • Save personal user settings
...... 5-2 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Management Operating the ONNS via the WaveStar® CIT
......
Title bar
Menu bar
Display area
ONNS GUI Network Map
Network Discovery and Resource Management Network Discovery displays all the nodes and links in their current state on the Network Map. After Network Discovery, the topology data is populated with data indicating the adjacencies and their port pair associations. Link properties data is available indicating total and available bandwidth, cost, delay, and other attributes of the link.
Connection Management Connection Management includes path creation, path deletion, and restoration management. You can create end-end connections, specifing the attributes desired. Links and connections are displayed as follows: • Created links are diplayed as grey lines • Pathes are displayed as green lines. • 1+1 pathes are displayed with colors light green and dark green. The colours (light green and dark green) are not a representations of working and protection. They are only different colours so that the user can see where the start and end points are otherwise it looks like a green rhombus with no clear ingress & egress. • If two overlapping paths exist in the map, the two paths are drawn as two parallel lines between the corresponding nodes.
...... 365-375-026 Alcatel-Lucent - Proprietary 5-3 Issue 5 July 2008 See notice on first page ONNS Management Operating the ONNS via Optical Management System (OMS) ...... Operating the ONNS via Optical Management System (OMS)
Overview The Optical Management System (OMS) is the second way of accessing the Optical Network Navigation System (ONNS) to conduct operational activities efficiently in a browser.
Functional Components The OMS consists of the following components: • Operate OMS GUI including the Network Map. • Supports both SONET and SDH transport structure environments. • Manage network infrastructure, individual network elements, and network capacity. • Manage all types of connections. • Establish and display the topology of the network. • Enables service activation and restoration • Provides end-to-end provisioning. • Provides service assurance through Fault Management, Performance Monitoring, and Profile Management
Network map The network map is embedded in the OMS browser environment. Upon login the home page appears with a set of icons as shown in the following figure. Click on the Network icon to start opening the Network Map page with the embedded network map.
...... 5-4 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Management Operating the ONNS via Optical Management System (OMS) ......
Top navigation zone
Toolbar
Map Control Toolbar
NE
Area
The map tools are divided in two menu bars, the left toolbar controls the displayed map (zoom, grid,{), the top(-right) toolbar provides some functions of the map (refresh, legend, find{, save{, display route, filter, new,{). With the “Legend” button you receive informations about the node icon design and its different colour settings. To display the available NEs, click right to an existing area, if minimum one or an other NE already exists in a map, select from the drill-down menu “Expand all” and the NEs are displayed in an exploded view on the map. If no area exists click in the above toolbar on the “New” button and create a new area and/or other NEs to this map. For further activities on the OMS, refer to the Lucent OMS Documentation library described in section “Online help” (p. 5-5).
Online help On each OMS browser page where the top navigation zone is displayed a respective online help is available. From this navigation zone, shown in the next figure, click Help, select On-line doc and the Lucent OMS Documentation page appears. Select the guide you are interested for and wish to display either in HTML or PDF format.
...... 365-375-026 Alcatel-Lucent - Proprietary 5-5 Issue 5 July 2008 See notice on first page ONNS Management Operating the ONNS via Optical Management System (OMS) ......
Top navigation zone
For informations regarding the actual OMS browser page, click Help from the top navigation zone and a list of aids scrolled out (see next figure). Select About this page and the About this page page is populated containing the purpose, the toolbar tools, and a description of each field about this page. At the bottom of this page further links are provided. Use the Interface tips link to populate a content list of the most important information sections for OMS usage derived from chapter one of the Lucent OMS Getting Started Guide.
Top navigation zone
To check the running OMS software release, click Help from the top navigation zone, select About OMS and the OMS release information page is populated as shown the figure below.
...... 5-6 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Management Operating the ONNS via Optical Management System (OMS) ......
Top navigation zone
Enable operating terminology SDH or SONET To change the terminology from SDH to SONET or in the reverse way, click My preferences from the top navigation zone, select Preferences and the Preferences page is displayed. Open the Application Preferences panel by clicking the “+” and customize the Terminology for your use by the radio button. Click Submit and a process indication followed by a confirmation is issued in the Message section and the terminology is changed.
Top navigation zone
...... 365-375-026 Alcatel-Lucent - Proprietary 5-7 Issue 5 July 2008 See notice on first page ONNS Management Connection and path state definitions
...... Connection and path state definitions
Overview This next two sections provides the connection status and the path state codes reported when ONNS connections and paths are manually established or modified by TL1 commands and/or those change autonomously by the system. The connection status or path state parameters of a connection and path appear in the REPT PTHCHG message just as reported in the connection record that is returned in a TL1 command response. If a connection object’s configuration changes autonomously, the pst, sst and tst parameters of the REPT PTHCHG are the actual pst, sst and tst parameters of the connection object after the configuration change has occurred. If a connection status or path state changes autonomously (e.g. restoration), the new state of the ingress (and local egress) paths are returned in a single REPT PTHEVT message. The connection status and path state parameters are composed to as follows: • pst – primary state • sst – secondary state • tst – tertiary state (optional). The types of both states can have up to three &-separated value sets for example pst&sst(&tst).
The connection status codes Connection state summarizes the state of the service. Overview of the connection status codes
TL1 ConnStatus code Description CON&OK Normal Connection Status CON&FAILED Connection failure CON&NO-IN No Input, source or destination (Initial setup) CON&FAILED&RSTRFL Restoration attempt failed / connection going to the Restoration Queue CON&TRDOWN Connection Delete (In Progress) DLT Connection Deleted CON&DLT-FL Connection delete failed, path not deleted
...... 5-8 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 ONNS Management Connection and path state definitions
......
TL1 ConnStatus code Description CON&OK&RSTRD Auto-Reroute Revertive Connection Status (after initial restoration) NOCON&SETUP Initial connection setup in progress NOCON&PREMPTD Connection has been disconnected from original path CON&OK&WTORV AUTORV Connection ready, waiting for WTR (wait-to-revert) timer to revert to original path NOCON&WTORSTR Preempted path removed & Connection has been added to the Restoration Queue. CON&FAILED&WTORSTR Auto Connection failed & has been added to the Restoration Queue. CON&SETUP Initial connection setup completed, waiting for check of signal NOCON&SETUPFL Initial connection setup failed NOCON Connection has been disconnected from original path by maintenance operation CON&OK&FL-NVM Normal Connection Status, but NVM write failed DLT&FL-NVM Connection Deleted & NVM write failed CON&STBY Protecting connection not being allocated for protecting a working one CON&USED Protecting connection not being allocated for protecting a working one CON&UNKNOWN Connection Status is not known after a recovery until the fault status is retrieved from the z-node.
The path state codes Path state summarizes the state of an individual path of a connection. Overview of the path state codes
TL1 PathState code Description CON&OK Normal path status CON&FAILED Path failure CON&NO-IN No Input, source or destination, during initial setup CON&TRDOWN Path delete, in Progress
...... 365-375-026 Alcatel-Lucent - Proprietary 5-9 Issue 5 July 2008 See notice on first page ONNS Management Connection and path state definitions
......
TL1 PathState code Description DLT Path deleted CON&DLT-FL Path delete failed CON&OK&RSTRD Auto-Reroute Revertive Restoration NOCON&SETUP Initial connection setup completed, waiting for signal confirmation from the egress node NOCON&PREMPTD Path has been disconnected from original EDGE port and will be re-used on another restored connection CON&OK&WTORV AUTORV Path ready, waiting for WTR (wait-to-revert) timer to revert to original path CON&FAILED&WTORSTR Restoration attempt failed and will be restored when a new path is available CON&SETUP Initial connection setup completed, waiting for signal confirmation from the egress node NOCON&SETUPFL Initial connection setup failed NOCON Pre-calculated restored path available for use CON&UNKNOWN Path State is not known after a recovery until the fault status is retrieved from the z-node. RSVD&OK Normal Path Status while associatedto a protecting connection RSVD&FAILED Path failure while associated to a protecting connection RSVD&DLT-FL Path delete failed for a path associated to a protecting connection RSVD&SETUPFAIL Initial connection setup failed for protecting connection RSVD&TRDOWN Path Delete in progress for path associated to protecting connection RSVD&SETUP Initial connection setup completed, for path associated to protecting connection, waiting for signal confirmation from the egress node RSVD&UNKNOWN Path State for a path associated to a protecting connection is not known after a recovery until the fault status is retrieved from the z-node.
...... 5-10 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Appendix A:
Standards
Standards overview The following standards are related to ONNS applications: • ITU-T Rec. G.8070/Y.1301 (2001), Requirements for the Automatic Switched Optical Network (ASON) • ITU-T Rec. G.8080/Y.1304 (2001), Architecture of the Automatic Switched Optical Network (ASON) • ITU-T Rec. G.7712/Y.1703 (2001), Architecture and Specification of Data Communication Network • ITU-T Rec. G.7713/Y.1704 (2001), Distributed Call and Connection Management (DCM) • ITU-T Rec. G.7714/Y.1705 (2001), Generalized Automatic Discovery • ITU-T Rec. G.7714.1/Y.1705.1 ( ), Automatic Discovery Protocol • ITU-T Draft Rec. G.7715/Y.1706 (2002), Routing Architecture and requirements for ASON Networks • ITU-T Draft Rec. G.7718.1 (), Management aspects of ASON control plane • OIF UNI 1.0-R2, Common User Network Interface (UNI), Signalling specification R2.0; (cf. ITU-T Rec. G.7713/Y.1704)
...... 365-375-026 Alcatel-Lucent - Proprietary A-1 Issue 5 July 2008 See notice on first page
Glossary
......
Numerics
1+1 Optical Port/Line Protection A protection architecture in which one physical port or line is protected by one standby physical port or line. The signal is transmitted on both the active and protection ports and lines. The receiving equipment monitors both lines using optical power level and performance criteria. If a switching condition is detected, the receiving equipment will perform a protection switch to the active line.
2-Fiber BLSR/MS-SPRing Protection A ring configuration in which traffic is bidirectional between each pair of adjacent NEs and is protected by redundant bandwidth on the bidirectional lines that inter-connect the NEs in the ring. Protection is provided by using ring loopback switching from the service to the protection logical ports using the opposite directions of the ring at the point of failure.
4-Fiber BLSR/MS-SPRing Protection A ring configuration in which traffic is bidirectional between each pair of adjacent NEs and is protected by redundant bandwidth on the bidirectional lines that inter-connect the NEs in the ring. Protection is provided by using ring loopback switching from the service to the protection logical ports using the opposite directions of the ring at the point of failure.
......
A ADM Add / Drop Multiplexer
AIS Alarm Indication Signal
ANSI American National Standards Institute
APG Application and Planning Guide
APS (Automatic Protection Switching) APS is a SONET protection mechanisms for linear and ring applications.
ARPANET (Advanced Research Projects Agency Network) ...... 365-375-026 Alcatel-Lucent - Proprietary GL-1 Issue 5 July 2008 See notice on first page Glossary
...... In 1969 the Advanced Research Projects Agency (ARPA) funded a research and development project to create an experimental packet-switching network. This network, called the ARPANET, was built to study techniques for providing robust, reliable, vendor-independent data communications. Many techniques of modern data communications were developed in the ARPANET.
ATM Asynchronous Transfer Mode
......
B Bandwidth 1. The difference in Hz between the highest and lowest frequencies in a transmission channel. 2. The data rate that can be carried by a given communications circuit.
Bellcore Bell Communications Research Inc.
BGP Border Gateway Protocol
BLSR (Bidirectional Line Switched Ring) BLSR is a SONET ring protection mechanism.
......
C C-SPF Constraint-based - Signal Point Failure
CCITT original (fr): Comité Consultatif International Télégraphique & Téléphonique translation (en): International Telegraph and Telephone Consultative Committee
CEPT Conférence Européenne des Administrations des Postes et des Télécommunications
CIC Lucent Customer Information Center
CIT (Craft Interface Terminal) The user interface terminal used by craft personnel to communicate with a network element.
CLI Command Line Interface
COBRA Common Object Request Broker Architecture
...... GL-2 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Glossary
......
CPE Customer Premises Equipment
CR-LDP Constraint-based Routed - Label Distribution Protocol
CRC Cyclic Redundancy Check
CTL ConTrolLer
CTP Connection Termination Point
CXI Controler - Xconnect Interface
......
D DCC (Data Communications Channel) The embedded overhead communications channel in the synchronous line, used for end-to-end communications and maintenance. The DCC carries alarm, control, and status information between network elements in a synchronous network.
DCF Data Communication Function
DCN Data Communications Network and Data Communications Network (DCN) Subnetwork.
DDRP Domain-to-Domain Routing Protocol
Downstream At or towards the destination of the considered transmission stream, for example, looking in the same direction of transmission.
DSS Digital Signature Standard
DWDM (Dense Wavelength Division Multiplexing) Multiplexing using close spectral spacing of individual wavelengths to take advantage of desirable transmission characteristics, for example minimum dispersion or attenuation, within a given fiber, while reducing the total fiber count needed to provide a given amount of information-carrying capacity.
...... 365-375-026 Alcatel-Lucent - Proprietary GL-3 Issue 5 July 2008 See notice on first page Glossary
......
......
E EDGE port Provides SNPs that are at the end of the ONNS connection. An SNP in an EDGE port can not be an intermediate point in an ONNS connection. An SNP in an EDGE port can be used for both switched as well as traditional connections.
EIS External Interface System
EMF Element Management Function
EMS Element Management System, refer to OMC-P
EP Electrical Pack
ETSI (European Telecommunications Standards Institute) Established in 1988, ETSI is a non-profit making organization whose mission is to determine and produce the telecommunications standards that will be used for decades to come. ETSI represents one of the largest international technical associations in the field of telecommunications, information and communication technology and broadcasting and brings together an impressive array of expertise, all working together towards the ultimate goal of a universal information network.
......
FFA Functional Area
FASTN Full-Automatic Switched Transport Network
......
GGB GigaByte
GbE or GE Gigabyte Ethernet
GMPLS Generalized MPLS Signal
GUI Graphical User Interface
...... GL-4 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Glossary
......
......
H HDLC (High level Data Link Control) OSI reference model datalink layer protocol.
HOVC Higher Order Virtual Container
......
I I-ISIS Integrated-ISIS
ICMP (Internet Control Message Protocol) ICMP is the error and control message protocol used by the Internet protocol family. It is used by the kernel to handle and report errors in protocol processing. It may also be accessed by programs using the socket interface or the Transport Level Interface (TLI) for network monitoring and diagnostic functions. ICMP is an datagram protocol layered above IP. It is used internally by the protcol code for various purposes including routing, fault isolation, and congestion control.
ID IDentifier
IEC (International Electro-Technical Commission) The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes international standards for all electrical, electronic and related technologies. These serve as a basis for national standardization and as references when drafting international tenders and contracts. The IEC charter embraces all electrotechnologies including electronics, magnetics and electromagnetics, electroacoustics, multimedia, telecommunication, and energy production and distribution, as well as associated general disciplines such as terminology and symbols, electromagnetic compatibility, measurement and performance, dependability, design and development, safety and the environment. IEC’s international standards facilitate world trade by removing technical barriers to trade, leading to new markets and economic growth. Put simply, a component or system manufactured to IEC standards and manufactured in country A can be sold and used in countries B through to Z.
IEEE (Institute of Electrical and Electronics Engineers) IEEE Standards affect world trade, ensure safety, drive technology, and develop markets. For more than a century, the IEEE Standards Association (IEEE-SA) has offered an established standards development program that offers balance, openness, due process, and consensus. Products based upon internationally recognized IEEE technology standards are more competitive in the marketplace, and consumers worldwide value products based upon top-quality standards development.
...... 365-375-026 Alcatel-Lucent - Proprietary GL-5 Issue 5 July 2008 See notice on first page Glossary
......
IESG Internet Engineering Steering Group
IETF (Internet Engineering Task Force) The Internet Engineering Task Force (IETF) is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. It is open to any interested individual.
iNNI (internal Network - Network Interface port) An iNNI port is connected to another iNNI port within a single routing domain running an internal NNI protocol within a single vendor’s network. iNNI ports provide intermediate connection points in the ONNS connection.
IP Internet Protocol
IS (Intermediate System) In the ISO-OSI network protocol, intermediate systems (IS) are used for routing data between nodes and (sub) networks. A network element can act both as an end system as well as an intermediate system.
IS-IS (ISIS) (Intermediate System to Intermediate System) The Network Elements in a management network route packets (data) between each other, using an IS-IS level protocol. The size of a network running IS-IS Level 1 is limited, and therefore certain mechanisms are employed to facilitate the management of larger networks. • For STATIC ROUTING, the capability exists for disabling the protocol over the LAN connections, effectively causing the management network to be partitioned into separate IS-IS Level 1 areas. In order for the network management system to communicate with a specific Network Element in one of these areas, the network management system must identify through which so-called Gateway Network Element this specific Network Element is connected to the LAN. All packets to this specific Network Element are routed directly to the Gateway Network Element by the network management system, before being re-routed (if necessary) within the Level 1 area. • For DYNAMIC ROUTING an IS-IS Level 2 routing protocol is used allowing a number of Level 1 areas to interwork. The Network Elements which connect an IS-IS area to another area are set to run the IS-IS Level 2 protocol within the Network Element and on the connection between other Network Elements. Packets can now be routed between IS-IS areas and the network management system does not have to identify the Gateway Network Elements.
ISO International Standards Organization
...... GL-6 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Glossary
......
ITU International Telecommunications Union
ITU-T (International Telecommunications Union – Telecommunication standardization sector) ITU-T was created on 1 March 1993, replacing the former CCITT whose origins go back to 1865. The public and the private sectors cooperate within ITU-T for the development of standards that benefit telecommunication users worldwide.
......
L LAN (Local Area Network) A communications network that covers a limited geographic area, is privately owned and user administered, is mostly used for internal transfer of information within a business, is normally contained within a single building or adjacent group of buildings, and transmits data at a very rapid speed.
LDP Label Distribution Protocol
LMP Link Management Protocol
LOVC Lower Order Virtual Container
LOXC (Lower-order cross-connection unit) Optional circuit pack for cross-connections on lower-order signal levels: VT1.5, VC-12 and VC-3 (lower order).
LPID (Logical Port IDentifier) A LPID is the equivalant of a physical port and is the logical representation of it in the system. The LPID is part of the TNA. One TNA can consist of more then one LPID. It is used in the context of UNI.
LSA Link State Advertisement
LSP (Label Switched Paths) Is used in the UNI context within the RSVP-TE protocol. LSPs are also used within MPLS.
......
M M:N N worker connections which are protected by M protection connections
MB MegaByte
...... 365-375-026 Alcatel-Lucent - Proprietary GL-7 Issue 5 July 2008 See notice on first page Glossary
......
MCN Management Communications Network
Mesh A topology where the network elements are not connected in a ring. A mesh can be one unprotected physical connection.
MN MiNor (alarm)
MPLS MultiProtocol Label Switching
MS Multiplexer Section
MS-DCC Multiplexer Section-DCC
MS-SPRing (Multiplex Section-Shared Protection Ring) MS-SPRing is an SDH ring protection mechanism. A self-healing ring configuration in which traffic is bidirectional between each pair of adjacent NEs and is protected by redundant bandwidth on the bidirectional lines that interconnect the NEs in the ring. Because traffic flow is bidirectional between NEs, traffic can be added at one NE and dropped at the next without traveling around the entire ring. This leaves the spans between other NEs available for additional traffic. Therefore, with distributed traffic patterns, this type of ring can carry more traffic than the same facilities could carry if configured for a unidirectional ring. In the event of a fiber or node failure, service is restored by switching traffic from the working capacity of the failed line to the protection capacity in the opposite direction around the ring. The SONET equivalent of this ring topology is the BLSR ring.
MSP (Multiplex Section Protection) MSP is used to protect the traffic in a point-to-point connection against transmission failures (MS-AIS, LOF, LOS, MS-DEG) and port equipment failures. A requirement for this kind of protection is that the transmission lines are doubled (one working line, one protection line). A trail continues to use the working route until a fault condition occurs or an external switch request is issued to switch to the protection route.
MSS MultiService Switch, part of product 1675 LambdaUnite MSS
MTTR MeanTime To Repair
MX MultipleXer ...... GL-8 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Glossary
......
......
N NCP Network Control Protocol
NDP Neighbor Discovery Protocol
NE (Network Element) A node in a telecommunication network that supports network transport services and is directly manageable by a management system.
Neighbor Neighbor cross connect matrices connected via a link. Note that Network Elements with different matrix types will never be neighbors. Neighbor can change depending on the port connections in the server layer.
NEM NE Management
NEMIF NE Model Interface
Network connection A network connection is an end-to-end connection addressed by means of TNAs, and can be realized within one domain or across multiple domains.
NMS Network Management System
NN Network Navigator
NNI Network - Network Interface
Node A network element in a ring or, more generally, in any type of network. In a network element supporting interfaces to more than one ring, node refers to an interface that is in a particular ring. Node is also defined as all equipment that is controlled by one system controller. A node is not always directly manageable by a management system.
NSA Non-Service Affecting
NSAP Network Service Access Point address
...... 365-375-026 Alcatel-Lucent - Proprietary GL-9 Issue 5 July 2008 See notice on first page Glossary
......
NTP Network Time Protocol
NVM (Non-Volatile Memory) Memory that retains its stored data after power has been removed. An example of NVM would be a hard disk.
......
O OAM&P Operations, Administration, Maintenance, and Provisioning
OC Optical Carrier
ODSI Optical Domain Service Interconnect
OED Optical Edge Device
OHI OverHead Interface
OIF (Optical Internetworking Forum) The OIF promotes the development and deployment of interoperable networking solutions and services through the creation of Implementation Agreements (IAs) for optical networking products, network processing elements, and component technologies.
OMC-P Operations & Maintenance Center – PlexView
OMS Optical Management System (OMS)
ONI Operations Network Interface
ONN Optical Network Navigator
ONNS (Optical Network Navigation System) Software and hardware present on some NEs, which performs connection management functions for synchronous connections, across a network of switched NEs. The ONNS system consists of a number of ONNS modules. Each module resides on a different switched NE in the network.
...... GL-10 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Glossary
......
ONNS domain The portion of the network that is under the control of ONNS is known as the ONNS domain. The ONNS domain is a collection of switched NEs that are able to signal amongst themselves and use this information to maintain the neighbor topology data to provide routing and restoration within the domain.
ONNS-link ONNS-link is the set of all port connections between a pair of nodes.
OP Optical Pack
ORP Optical Routing Protocol
OSI (Open Systems Interconnection) Referring to the OSI reference model, a logical structure for network operations standardized by ISO.
OSM Optical Services Manager
OSPF Open Shortest Path First
OTN Optical Transmission Network
OUC ONNS-UPSR-Cunstruct
OXC Optical Xconnect
......
P PDH Plesiochronous Digital Hierarchy
PM (PM (Performance Monitoring) Measures the quality of service and identifies degrading or marginally operating systems (before an alarm would be generated).
PNNI Private Network to Network Interface
Port (also called Line) The physical interface, consisting of both an input and output, where an electrical or optical transmission interface is connected to the system and may be used to carry traffic
...... 365-375-026 Alcatel-Lucent - Proprietary GL-11 Issue 5 July 2008 See notice on first page Glossary
...... between network elements. The words “port” and “line” may often be used synonymously. “Port” emphasizes the physical interface, and “line” emphasizes the interconnection. Either may be used to identify the signal being carried.
PPP Point-to-Point Protocol
PSE Protection Switch Events
PSTN Public Switched Telephone Network
......
Q QoS (Quality of Service) A connection parameter that defines the level of service for a connection.
......
RRA Routing Area
RC Routing Controller
RFC (Request for Comments) The RFC document series is a set of technical and organizational notes about the Internet (originally the ARPANET), beginning in 1969. Memos in the RFC series discuss many aspects of computer networking, including protocols, procedures, programs, and concepts, as well as meeting notes, opinions, and sometimes humor. The official specification documents of the Internet Protocol suite that are defined by the Internet Engineering Task Force (IETF) and the Internet Engineering Steering Group (IESG) are recorded and published as standards track RFCs. As a result, the RFC publication process plays an important role in the Internet standards process. In addition, the RFC Editor publishes as independent submissions some RFCs that are outside the IETF process but are relevant to the Internet community. RFCs must first be published as Internet Drafts.
RS Regenerator Section (SONET: section)
RSVP Resource ReserVation Protocol
RSVP-TE (RSVP with Traffic Engineering extensions) RSVP-TE is used by UNI and for the distribution of LSPs within MPLS.
...... GL-12 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Glossary
......
......
S SASTN Semi-Automatic Switched Transport Network
SC Switched Connection
SCF System Control Function
SCN (Signaling Communication Network) This includes internal communication within the ONNS domain as well as external communication like in the context of UNI or eNNI.
SDH (Synchronous Digital Hierarchy) An international digital telecommunications network hierarchy which standardizes transmission on the STM-1 bit rate of 155.52 megabits per second. Higher frame rates are derived from multiples of STM-1 (Synchronous Transport Module-Level 1). SDH specifies how payload data is framed and transported synchronously across optical fiber transmission links without requiring all the links and nodes to have the same synchronized clock for data transmission and recovery (that is, both the clock frequency and phase are allowed to have variations, or be plesiochronous).
sink-node Network Element containing the ’sink’ of the onnsPath. In case of a bi-directional onnsPath, the sink-node also contains a ’source’ of this bi-directional onnsPath.
SLA Service Level Agreement
SNC Sub-Network Connection
SNCP (Sub-Network Connection Protection) SNCP is a type of path protection that is used to protect the traffic for a pre-selected path. A working path is replaced by a protection path if the working path fails, or if its performance falls below a required level.
SNMP Simple Network Management Protocol
SNNS SONET/SDH Network Navigation System
SNP (SubNetwork Point) An alias for either a TTP or a CTP. An example usage of the term SNP is if there is a need to refer to the end points of a connection without caring if the end-point is a TTP or CTP (NN-connections are set-up between SNPs)...... 365-375-026 Alcatel-Lucent - Proprietary GL-13 Issue 5 July 2008 See notice on first page Glossary
......
SONET (Synchronous Optical NETwork) An industry standard for high-speed transmission over optical fiber, which specifies a hierarchy of rates and formats for optical transmission ranging from 51.84 Mbps to 13.271 Gbps. These rates were created to provide the flexibility needed to transport many digital signals with different capacities and to provide a design standard for manufacturers. The SONET protocol stack consists of the following four layers: • The photonic layer is the electrical and optical interface for the transport of information bits across the physical medium. It converts STS-N electrical signals to OC-N optical signals. It performs functions associated with the bit rate, optical-pulse shape, power, and wavelength. It does not use any overhead. • The section layer transports the STS-N frame across the optical cable and establishes frame synchronization and the maintenance signal. Its functions include framing, scrambling, error monitoring, and orderwire communications. • The line layer provides the synchronization, multiplexing, and automatic protection switching (APS) for the path layer. Because it is primarily concerned with the reliable transport of the path layer payload (voice, data, or video) and overhead, it allows automatic switching to another circuit if the quality of the primary circuit drops below a specified threshold. Overhead includes line-error monitoring, maintenance, protection switching, and express orderwire. • The path layer maps services such as DS3, FDDI, and ATM into the SONET payload format. It provides end-to-end communications, signal labeling, path maintenance, and control and is accessible only through terminating equipment. A SONET ADM accesses the path layer overhead; a cross-connect system that performs section and line layer processing does not require access to the path layer overhead.
Span An uninterrupted bidirectional fiber section between two network elements
SPC Soft Permanent Connection
SPF Signal Point Failure
SRCP Simple Reporting & Configuration Protocol
SRG Shared Risk Group
SRLG (Shared Risk Link Group) SRLG of port connections that share the same risk. Examples: port connections that terminate on the same card, in the same network element or that share the same fiber duct. SRLGs are typically used for protected connections in which the two legs should
...... GL-14 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Glossary
...... not share a common risk.
STS Synchronous Transport Signal (SONET)
SwiSS Switched SONET/SDH
......
T TCA (Threshold Crossing Alert) A transient condition message issued by an NE if the value of a performance monitoring (PM) parameter exceeds or falls below a set threshold value. An example of a PM parameter for which a TCA can be issued if the threshold value is exceeded is the Number of Errored Seconds.
TCM Tandem Connection Monitoring
TCP (Transmission Control Protocol) A reliable protocol that provides connection- and stream-oriented services at the Open Systems Interconnection transport layer. It uses Internet Protocol (IP) to deliver its packets, and guarantees delivery of an ordered stream of data packets.
TDM (Time Devision Multiplexing) A multiplexing technique whereby two or more channels are derived from a transmission medium by dividing access to the medium into sequential intervals. Each channel has access to the entire bandwidth of the medium during its interval. This implies that one transmitter uses one channel to send several bit streams of information.
TL1 (Transaction Language 1) This term is applicable for only TL1 NEs. A machine-to-machine communications language that is a subset of the ITU human-machine language.
TNA (Transport-Network Assigned) TNA is used to identify a network resource between UNI-C and UNI-N. A TNA consists of a type and an address. A TNA can consist of one or more LPIDs.
TNE (Transport Network Element) synonym for UNI-N
TOP TransOceanic Protocol
TP Termination Point
...... 365-375-026 Alcatel-Lucent - Proprietary GL-15 Issue 5 July 2008 See notice on first page Glossary
......
TSI Time Slot Interchange
TTP (Trail Termination Point) TTP end point of a trail; terminates trail overhead numbered. A TTP is addressed relatively to a port.
TXI Transmission Interface
......
U UAS Un-Available Second
UDP User Datagram Protocol
UL Underwriter Labratories
UNEQ UN-EQuipped
UNI (User Network Interface, see also TNE) UNI specifies the protocols to interface between a User Network Interface user device and the edge of the ONNS network. UNI defines the Network Interface Type of the port that is used to specify that part of the port that is to be used for UNI connections.
UNI-C UNI-Client side
UNI-N UNI-Network side
UNITE UNIversal high speed TDM Equipment
UPSR (Unidirectional Path-Switched Ring) UPSR is typically a SONET ring architecture. It provides path-level protection for STS-N circuits within in physical ring network. The SDH equivalent of this ring topology is the SNCP ring.
Upstream At or towards the source of the considered transmission stream, for example, looking in the opposite direction of transmission.
...... GL-16 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008 Glossary
......
......
VVC Virtual Container
VCG (Virtual Concatenation Group) Virtual concatenation is an inverse multiplexing protocol that allows multiple transport containers to be grouped and treated as a single entity that is transported across the network. This entity is referred to as a Virtual Concatenation Group (VCG). A VCG is a group of logical ports that, while they may be routed individually through a network, behave as a single concatenation group for carrying Ethernet packets.
VCGTRIB VCG TRIButary
......
WWAN Wide Area Network
WRT Wait to Restore Time
......
X XC (XConnection) cross-connection, synonym for CC
......
Z Z-node synonym for sink-node; Term is used in the signaling plane normally.
...... 365-375-026 Alcatel-Lucent - Proprietary GL-17 Issue 5 July 2008 See notice on first page
Index
Numerics ...... Online help, 5-5 1+1 (revertive or E E-NNI node, 4-22 Operating ONNS non-revertive), 2-11 E-NNI port, 2-4 via CIT, 5-2 1+1 permanent, 2-11 Edge port, 2-4 via Navis® OMS, 5-4 ...... Enabling of DCCs, 4-13 Optical Routing Protocol A Admin costs, 3-11 (ORP), 2-24 ...... Auto-Reroute, manual revertive, OSI protocol stack, 4-13 2-11 H Higher TCA threshold, 2-29 ...... Auto-Reroute, non-revertive, ...... 2-11 P Path State Codes, 5-9 I I-ISIS, 4-3, 4-6 Auto-Reroute, revertive, 2-11 Performance monitoring, 3-24 I-NNI port, 2-4 ...... Port connection, 3-10 Interfaces, 2-4 PPP, 4-3 B Bandwidth utilization, 2-29 Internet Protocol (IP), 4-3 Propagation delay, 3-11 Basic mesh planning, 3-7 ...... L Label Switched Path, 4-6 R Restoration priorities, 3-12 C Connection Status Codes, 5-8 LAPD channels, 4-13 ...... Conventions, v Link bundling, 3-11 S SCN Neighbor Map, 4-5 Cost escalation, 3-13 Link State Advertisements Cost savings, 3-20 (LSA), 2-24 Signaling Communications Network (SCN), 4-2 customer comment form; Lower TCA threshold, 2-29 SRLG commenting, vii LSP, 4-6 ...... COMPLETE, 3-16 ...... Exclude node list, 3-16 D Data Communication Channel M M:N shared protection, 2-11 (DCC), 4-13 Exclusive SRLG, 3-16 ...... DCC controller, 4-5, 4-13 Explicit node list, 3-16 O OMS DCC termination, 4-13 FULLYSRLG, 3-16 Network map, 5-4 Document conventions, v Include node list, 3-16 ...... 365-375-026 Alcatel-Lucent - Proprietary IN-1 Issue 5 July 2008 See notice on first page Index
......
Inclusive SRLG, 3-16 MAXIMAL, 3-16 Maximum delay, 3-16 ......
T TCA status, 2-29 TNA address, 2-34 Topology discovery, 2-23 Traditional port, 2-4 Transmission aspects, 3-9 Transmission Control Protocol (TCP), 4-3 Transport Network Assigned (TNA), 2-34 ......
U UDP, 4-3 UNI node, 4-21 UNI port, 2-4 ......
Y Y-Connection, 2-11
...... IN-2 Alcatel-Lucent - Proprietary 365-375-026 See notice on first page Issue 5 July 2008