8DG61258GAAATPZZA - V1 - 7.0 DCN Planning and Engineering Guide

Title page
Alcatel-Lucent 1830
Photonic Service Switch (PSS) | Release 7.0
DCN Planning and Engineering Guide (Photonic applications)
8DG-61258-GAAA-TPZZA
Issue 1 | April 2014
Legal notice
Legal notice
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 © 2014 Alcatel-Lucent. All rights reserved.
Conformance statement
Interference Information: Part 15 of FCC Rules

NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits
are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy. If the equipment is not installed and used in accordance with the guidelines in this document, the
equipment may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference,
in which case the user will be required to correct the interference at the expense of the user.
Security Statement
In rare instances, unauthorized individuals make connections to the telecommunications network through the use of remote access features. In such an event,
applicable tariffs require that the customer pay all network charges for traffic. Alcatel-Lucent cannot be responsible for such charges and will not make any
allowance or give any credit for charges that result from unauthorized access.
Limited Warranty
For terms and conditions of sale, contact your Alcatel-Lucent Account Team.
Contents
About this document

Purpose .......................................................................................................................................................................................... xiii
xiii
Intended audience ...................................................................................................................................................................... xiii

xiii
Supported systems ..................................................................................................................................................................... xiii

xiii
Conventions used ....................................................................................................................................................................... xiv

xiv
Related information .................................................................................................................................................................... xv

xv
Technical support ..................................................................................................................................................................... xviii

xviii
How to comment ..................................................................................................................................................................... xviii

xviii
1 Introduction
Overview ...................................................................................................................................................................................... 1-1

1-1
Basic aspects of network design
Network layers ........................................................................................................................................................................... 1-2

1-2
Physical layer ............................................................................................................................................................................. 1-3

1-3
Data Link layer .......................................................................................................................................................................... 1-4

1-4
Network layer ............................................................................................................................................................................. 1-5

1-5
Transport layer ........................................................................................................................................................................... 1-8

1-8
Application layer ....................................................................................................................................................................... 1-9

1-9
2 DCN planning
Overview ...................................................................................................................................................................................... 2-1

2-1
General
Preconditions and requirements ........................................................................................................................................... 2-2

2-2
Connection of Alcatel-Lucent 1830 PSS equipment to the management DCN ................................................. 2-8
2-8
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS iii
8DG-61258-GAAA-TPZZA Release 7.0
Issue 1 April 2014
Contents
....................................................................................................................................................................................................................................
MCN and SCN aspects
Overview ................................................................................................................................................................................... 2-20

2-20
Management DCN aspects .................................................................................................................................................. 2-20

2-20
Signaling DCN aspects ......................................................................................................................................................... 2-29

2-29
Network topology concept and dimensioning
The Alcatel-Lucent 1830 PSS management network ............................................................................................... 2-39

2-39
Basic network topologies .................................................................................................................................................... 2-42

2-42
Address planning
Network IP architecture ....................................................................................................................................................... 2-45

2-45
Engineering guidelines
Summary of important rules and guidelines ................................................................................................................. 2-52

2-52
3 DCN configuration
Overview ...................................................................................................................................................................................... 3-1

3-1
Physical configuration
Procedure 3-1: Configure physical properties of interfaces ...................................................................................... 3-3

3-3
IP network configuration
DCN configuration overview ............................................................................................................................................... 3-5

3-5
Procedure 3-2: Configure IP addresses and TCP/IP parameters .............................................................................. 3-5

3-5
Procedure 3-3: Configure OSPF parameters ................................................................................................................... 3-7

3-7
Procedure 3-4: Create an OSPF area ............................................................................................................................... 3-11

3-11
Procedure 3-5: Create static routes .................................................................................................................................. 3-13

3-13
Time management
Network Time Protocol (NTP) .......................................................................................................................................... 3-14

3-14
Security
NE firewall with provisionable IP access control lists (IP ACL) .......................................................................... 3-15
3-15
RADIUS for user authentication ...................................................................................................................................... 3-17

3-17
....................................................................................................................................................................................................................................
iv Alcatel-Lucent 1830 PSS
Issue 1 April 2014
Contents
....................................................................................................................................................................................................................................
Secure/unsecure mode .......................................................................................................................................................... 3-18
3-18
Firewall configuration .......................................................................................................................................................... 3-21

3-21
IPSec tunnel .............................................................................................................................................................................. 3-22

3-22
Syslog server ............................................................................................................................................................................ 3-24

3-24
Advice on security hardening on the Alcatel-Lucent 1830 PSS ........................................................................... 3-24

3-24
Software Server NE (SWNE)
SWNE functionality .............................................................................................................................................................. 3-26

3-26
4 GMPLS Routing Engine (GMRE)
Overview ...................................................................................................................................................................................... 4-1

4-1
Specific considerations regarding the GMPLS Routing Engine (GMRE) .......................................................... 4-1
4-1
5 Supervision and troubleshooting
Overview ...................................................................................................................................................................................... 5-1

5-1
Monitoring, diagnosis and troubleshooting of abnormal situations ....................................................................... 5-1

5-1
Glossary
Index
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS v
Issue 1 April 2014
Contents
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
vi Alcatel-Lucent 1830 PSS
Issue 1 April 2014
List of tables
1 Information products related to Alcatel-Lucent 1830 PSS .......................................................................... xv
1-1 Network layers in TCP/IP model and ISO/OSI reference model ............................................................. 1-3
2-1 TCP/IP protocol stack .............................................................................................................................................. 2-2

2-2
2-2 User service interfaces ............................................................................................................................................. 2-3

2-3
2-3 DCN-related external interfaces (USRPNL) ................................................................................................... 2-5
2-4 OSPF metrics for an MRN control plane ....................................................................................................... 2-33
2-5 Organization of the networks .............................................................................................................................. 2-47
2-6 Default behavior of DCN-related interfaces ................................................................................................. 2-49
2-7 Engineering rules and guidelines ...................................................................................................................... 2-52
2-8 Required buffering and table sizes .................................................................................................................. 2-54
3-1 TCP/UDP ports used to access the NE .............................................................................................................. 3-6
3-2 Ports that support ACL filtering ......................................................................................................................... 3-16
3-3 System-defined port/filter associations ........................................................................................................... 3-16
3-4 Management flows and ports toward the GNE (secure mode) ............................................................... 3-21
3-5 Management flows and ports toward the GNE (unsecure mode) .......................................................... 3-22
3-6 Parameters of the SET-ATTR-SECUDFLT command .............................................................................. 3-24
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS vii
Issue 1 April 2014
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
viii Alcatel-Lucent 1830 PSS
Issue 1 April 2014
List of figures
1-1 ISO/OSI network architecture ............................................................................................................................... 1-2
1-2 Typical interconnection of OSPF areas ............................................................................................................. 1-7
2-1 Alcatel-Lucent 1830 PSS-32 User Panel faceplate ....................................................................................... 2-4
2-2 Alcatel-Lucent 1830 PSS-16 User Panel faceplate ....................................................................................... 2-5
2-3 Front view of the EC ................................................................................................................................................ 2-7

2-7
2-4 Schematic diagrams of Alcatel-Lucent 1830 PSS system compounds .................................................. 2-9
2-5 Management DCN connection of a photonic compound GNE .............................................................. 2-10
2-6 Management DCN connection of a converged system (GNE connection option 1) ...................... 2-11
2-9 Management DCN connection of a converged system RNE with partial LAN connectivity ..... 2-16
2-10 Management DCN connection of a converged system RNE with full LAN connectivity ........... 2-18
2-11 Basic GNE DCN setup (photonic application) ........................................................................................... 2-21
2-12 Basic RNE DCN setup (photonic application) ............................................................................................ 2-23
2-13 OSPF peering model (photonic application) ................................................................................................. 2-24
2-14 OSPF non-peering model via proxy ARP (photonic application) ......................................................... 2-26
2-15 Types of communication relations in MRN .................................................................................................. 2-31
2-16 Example MRN DCN setup with OSPF peering ........................................................................................... 2-35
2-17 Example MRN DCN with an OSPF non-peering setup (option 1) ....................................................... 2-37
2-18 Example MRN DCN with an OSPF non-peering setup (option 2) ....................................................... 2-38
2-19 Network management overview ........................................................................................................................ 2-39
2-20 IP addressing scheme (nodes have separate sub-networks) ..................................................................... 2-40
2-21 IP addressing scheme (nodes sharing a common sub-network) ............................................................. 2-41
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS ix
Issue 1 April 2014
List of figures
....................................................................................................................................................................................................................................
2-22 Linear architecture .................................................................................................................................................. 2-42
2-42
2-23 Ring architecture ..................................................................................................................................................... 2-43

2-43
2-24 Meshed architecture ............................................................................................................................................... 2-44

2-44
2-25 IP architecture overview ....................................................................................................................................... 2-45
3-1 IPSec tunneling ........................................................................................................................................................ 3-23

3-23
3-2 Usage of SWNEs in a WDM network ............................................................................................................. 3-27
....................................................................................................................................................................................................................................
x Alcatel-Lucent 1830 PSS
Issue 1 April 2014
List of procedures
3 DCN configuration
3-1 Configure physical properties of interfaces ..................................................................................................... 3-3
3-2 Configure IP addresses and TCP/IP parameters ............................................................................................. 3-5
3-3 Configure OSPF parameters .................................................................................................................................. 3-7
3-4 Create an OSPF area .............................................................................................................................................. 3-11

3-11
3-5 Create static routes .................................................................................................................................................. 3-13

3-13
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS xi
Issue 1 April 2014
List of procedures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xii Alcatel-Lucent 1830 PSS
Issue 1 April 2014
About this document
About this document
Purpose
This document provides information for the planning and configuration of a Data
Communication Network (DCN) for photonic applications of the Alcatel-Lucent
1830 Photonic Service Switch (PSS), Release 7.0.
Intended audience
The primary audience for the present document is personnel who work with the
Alcatel-Lucent 1830 PSS system, that is:
• Network operation and maintenance specialists,
• System administrators,
• Engineers with responsibility for network planning, design, configuration, or
optimization.
Supported systems
This document applies to photonic applications of the Alcatel-Lucent 1830 Photonic
Service Switch (PSS), Release 7.0, that is to Alcatel-Lucent 1830 PSS-16 and
Alcatel-Lucent 1830 PSS-32 systems.
Note:
• The terms “photonic applications” and “WDM applications” are used synonymously
throughout this document.
• The terms “system” and “NE” (Network Element) in the context of this document
refer to the photonic compound of an Alcatel-Lucent 1830 PSS Release 7.0 node only.
The terms “photonic compound” and “photonic node” are used synonymously.
• The term “main shelf” in the context of this document refers to the main shelf of the
photonic compound of an Alcatel-Lucent 1830 PSS Release 7.0 node only.
...................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS xiii
Issue 1 April 2014
About this document
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS system concept
Please note that Alcatel-Lucent 1830 PSS systems support both switching as well as
photonic applications, either as separate switching or photonic compounds or as a
converged system within a single node. Note furthermore that two distinct DCN Planning
and Engineering Guides exist, one document for each application; see also “Related
information” (p. xv).
Important! In case you want to plan and configure a DCN for a converged system, or
if you want to extend a single-compound node to a converged system in a future
configuration, please take both documents into consideration.
Interconnection of switching and photonic compounds
From a DCN perspective, switching and photonic compounds can be interconnected by
placing both into the same OAMP LAN subnet.
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 the conventions used for page numbering
The first number in a reference to a particular page refers to the corresponding chapter.
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.
....................................................................................................................................................................................................................................
xiv Alcatel-Lucent 1830 PSS
Issue 1 April 2014
About this document
....................................................................................................................................................................................................................................
Typographical conventions
Special typographical conventions apply to elements of the graphical user interface
(GUI), file names and system path information, keyboard entries, alarm messages, and so
on:
• Text appearing 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)
– Administration → Security → User Provisioning… (path for invoking a window)
• File names and system path information:
– setup.exe
– C:/Program Files/Alcatel-Lucent
• Keyboard entries:
– F1, Esc X, Alt-F, Ctrl-D, Ctrl-Alt-Del (simple keyboard entries)
A hyphen between two keys means that you have to press both keys. Otherwise,
you have to press a single key, or a number of keys in sequence.
– copy abc xyz (command)
A complete command that you enter.
• Alarms and error messages:
– Loss of Signal
– HP-UNEQ, MS-AIS, LOS, LOF
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.
Related information
Table 1 Information products related to Alcatel-Lucent 1830 PSS
Document title Document code
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Safety Guide 8DG-61258-GAAA-TAZZQ
Provides users of Alcatel-Lucent 1830 PSS systems with the relevant information
and safety guidelines to safeguard against personal injury. Furthermore, the Safety
Guide is useful to prevent material damage to the equipment. The Safety Guide
must be read by the responsible technical personnel before performing relevant
work on the system. The valid version of the document must always be kept close
to the equipment.
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS xv
Issue 1 April 2014
About this document
....................................................................................................................................................................................................................................
Table 1 Information products related to Alcatel-Lucent 1830 PSS (continued)
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Product 8DG-61258-GAAA-TQZZA
Information and Planning Guide
Presents a detailed overview of the system, describes its applications, gives
planning requirements, engineering rules, ordering information, and technical
specifications.
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 User Provisioning 8DG-61258-GAAA-TCZZA
Guide
Provides step-by-step information for use in daily system operations. The manual
demonstrates how to perform system provisioning, operations, and administrative
tasks.
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Maintenance and 8DG-61258-GAAA-TMZZA
Trouble-Clearing Guide
Gives detailed information on each possible alarm message. Furthermore, it
provides procedures for routine maintenance, troubleshooting, diagnostics, and
component replacement.
Alcatel-Lucent 1830 Photonic Service Switch 16/32 (PSS-16/PSS-32) Release 7.0 8DG-61258-GAAA-TJZZA
Installation and System Turn-Up Guide
A step-by-step guide to system installation and set up. It also includes information
needed for pre-installation site planning and post-installation acceptance testing.
Alcatel-Lucent 1830 Photonic Service Switch 36 (PSS-36) Release 7.0 Installation 8DG-61258-GAAA-TKZZA
and System Turn-Up Guide
Alcatel-Lucent 1830 Photonic Service Switch 64 (PSS-64) Release 7.0 Installation 8DG-61258-GAAA-TLZZA
and System Turn-Up Guide
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Key Management 8DG-61258-GAAA-TIZZA
Tool (KMT) Installation Guide
Provides detailed step-by-step description of how to install the Key Management
Tool including prerequisite SW download and installation.
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Command Line 8DG-61258-GAAA-THZZA
Interface Guide
Provides information about the Command Line Interface (CLI) for Alcatel-Lucent
1830 PSS and describes the CLI attributes and commands.
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Engineering and 8DG-61258-GAAA-TEZZA
Planning Tool User Guide
Provides step-by-step information for use in daily system operations for the EPT.
The manual demonstrates how to perform system provisioning, operations, and
commissioning tasks.
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 TL1 Commands 8DG-61258-GAAA-TFZZA
and Messages Guide (Switching Applications)
Describes the external TL1 interface for Alcatel-Lucent 1830 PSS in terms of TL1
command, responses, and notification definitions.
....................................................................................................................................................................................................................................
xvi Alcatel-Lucent 1830 PSS
Issue 1 April 2014
About this document
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 TL1 Commands 8DG-61258-GAAA-TGZZA
and Messages Guide (Photonic Applications)
Describes the external TL1 interface for Alcatel-Lucent 1830 PSS in terms of TL1
command, responses, and notification definitions.
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 GMRE/GMPLS 8DG-61258-GAAA-TWZZA
Guide
Contains information about the GMPLS Routing Engine (GMRE) of the
Alcatel-Lucent 1830 PSS; it provides a high-level functional overview of the
GMRE and describes the steps to plan and set up a GMRE-controlled network.
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Quick Reference 8DG-61258-GAAA-TNZZA
Guide
Provides users of Alcatel-Lucent 1830 PSS a streamlined, easy-to-use navigation
aid to facilitate the use of the system.
Alcatel-Lucent 1354 RM-PhM Release 12.0 Photonic Manager EMS Reference 8DG-61258-GAAA-TXZZA
Guide
Provides information for accessing the 1354 RM-PhM and using it to configure
and manage the Alcatel-Lucent 1830 PSS network.
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 DCN Planning 8DG-61258-GAAA-TPZZA
and Engineering Guide (Photonics Applications)
Provides information for the planning and configuration of a Data Communication
Network (DCN) for photonic applications, that is for Alcatel-Lucent 1830 PSS-16
and Alcatel-Lucent 1830 PSS-32 systems (WDM).
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 DCN Planning 8DG-61258-GAAA-TRZZA
and Engineering Guide (Switching Applications)
Provides information for the planning and configuration of a Data Communication
Network (DCN) for switching applications, that is for Alcatel-Lucent 1830 PSS-36
and Alcatel-Lucent 1830 PSS-64 systems (OCS).
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Key Management 8DG-61258-GAAA-TUZZA
Tool (KMT) Administration Guide
Provides information about the steps that an administrator needs to take in order to
set up network sites and elements, and to assign priorities and privileges.
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Key Management 8DG-61258-GAAA-TVZZA
Tool (KMT) User Guide
Provides information about how a user can use the KMT to assign keys, rotate the
keys, and access security logs and alarms.
Alcatel-Lucent Smart Compact Ethernet Demarcation Device (Smart cEDD) User 8DG-61259-AAAA-TYZZA
Guide
Provides instructions for use and descriptions of the features of the Smart Compact
Ethernet Demarcation Device (Smart cEDD).
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Commissioning 8DG-61258-GAAA-TBZZA
and Power Balancing Tool User Guide
Provides instructions for use and descriptions of the features of the Commissioning
and Power Balancing (CPB) Tool.
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS xvii
Issue 1 April 2014
About this document
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Federal 8DG-61258-GAAA-TSZZA
Information Processing Standards (FIPS) User Guide and Logbook
Describes the target FIPS configurations for Alcatel-Lucent 1830 PSS.
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 7.0 Electronic 8DG-61258-GAAA-TYZZA
Documentation Library
Contains all documents related to Alcatel-Lucent 1830 PSS in electronic formats.
Alcatel-Lucent 1830 Photonic Service Switch 16/32 (PSS-16/PSS-32) Release 7.0.0 8DG-62697-AAAA
Customer Release Notes
Alcatel-Lucent 1830 Photonic Service Switch 36/64 (PSS-36/PSS-64) Release 7.0.0 3AG-34247-AAAA
Customer Release Notes
These documents can be downloaded from the Alcatel-Lucent Online Customer Support
Site (OLCS) (https://support.alcatel-lucent.com) or through your Local Customer
Support.
Technical support
For technical support, contact your local Alcatel-Lucent customer support team. See the
Alcatel-Lucent Support web site (http://www.alcatel-lucent.com/support/) for contact
information.
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
xviii Alcatel-Lucent 1830 PSS
Issue 1 April 2014
1 Introduction
1
Overview
Purpose
The present section provides some theoretical background information relating to the
basic network design principles; the main focus is on TCP/IP-based communication.
Contents
Basic aspects of network design 1-2

Network layers 1-2
Physical layer 1-3
Data Link layer 1-4
Network layer 1-5
Transport layer 1-8
Application layer 1-9
...................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS 1-1
Issue 1 April 2014
Introduction Overview
....................................................................................................................................................................................................................................
Network layers
Network architecture
The network architecture is in general described by means of the ISO/OSI reference
model, which defines seven “layers”, as shown in the following figure:
Figure 1-1 ISO/OSI network architecture
End host End host
Application layer Application layer

(Data) (Data)
Presentation layer Presentation layer

(Data) (Data)
Session layer Session layer

(Data) (Data)
Transport layer Transport layer

(Segment) (Segment)
One or more intermediate network elements
Network layer Network layer Network layer Network layer

(Packet) (Packet) (Packet) (Packet)
Data Link layer Data Link layer Data Link layer Data Link layer
(Frame) (Frame) (Frame) (Frame)
Physical layer Physical layer Physical layer Physical layer

(Bit) (Bit) (Bit) (Bit)
A “layer” is a collection of conceptually similar functions that provide services to the

layer above it and receives service from the layer below it.
....................................................................................................................................................................................................................................
1-2 Alcatel-Lucent 1830 PSS
Issue 1 April 2014
Introduction Network layers
....................................................................................................................................................................................................................................
The Physical layer just transports bits, whereas the Data Link layer handles structured
frames. The Network layer has to route/forward packets from the sender NE along some
intermediate NEs towards the destination NE. This service is on behalf of the Transport
layer which is handling segments as pieces of data exchanged by the actual applications.
Note: The ISO/OSI reference model defines explicit Session and Presentation layers
whereas the TCP/IP model summarizes the layers above the Transport layer to a
single Application layer.
Table 1-1 Network layers in TCP/IP model and ISO/OSI reference model
TCP/IP model ISO/OSI reference model

Application layer Application layer
Presentation layer
Session layer
Transport layer Transport layer
Network layer Network layer
Data Link layer Data Link layer
Physical layer Physical layer
Physical layer
The physical layer is the lowest layer in the ISO/OSI network architecture, it deals with
the basic transmission characteristics of the hardware. In particular, it defines the
relationship between a device and a physical medium in terms of media, signal, and
binary transmission.
The major functions and services performed by the physical layer are the establishment
and termination of a connection to the communication medium – including the conversion
between the digital representation of data and the corresponding signal transmitted over
the communication channel.
....................................................................................................................................................................................................................................
Issue 1 April 2014
Introduction Data Link layer
....................................................................................................................................................................................................................................
Data Link layer

Introduction
The Data Link layer provides means to transfer data frames between adjacent network
elements. In addition it may be able to detect and possibly correct errors occurred at the
Physical Layer.
The Data Link layer may operate on point-to-point media (PPP) or on broadcast-capable
multiaccess media (Ethernet LAN).
Point-to-Point protocol (PPP)

The Point-to-Point protocol (PPP) is a full duplex, bit-synchronous data link protocol
commonly used to establish a direct connection between two NEs. In addition to the basic
functionality it can optionally provide connection authentication, transmission encryption,
and compression.
The PPP is conformant to RFC 1661 (LCP), RFC 1662 (PPP in HDLC-like framing), and
RFC 1332 (Internet Protocol Control Protocol, IPCP).
Connectivity
LCP (Link Control Protocol) - as a part of PPP - provides automatic consistent
configuration of the interfaces in terms of:
• Setting the maximum frame size, Maximum Transmission/Receive Unit (MTU/MRU)
- by default 1500 octets. Frames less than 4 octets are silently discarded.
• Escaped characters.
• Options like magic number (for loop detection), authentication.
The LCP is specified by the same RFC 1661 as the PPP, and runs on top of the PPP.
Therefore, a basic PPP connection has to be established before LCP is able to configure it.
The PPP permits multiple network layer protocols to operate on the same communication
link. For every network layer protocol used, a separate Network Control Protocol (NCP)
is provided in order to encapsulate and negotiate options for the multiple network layer
protocols. The Internet Protocol (IP), for example, uses the IP Control Protocol (IPCP).
Ethernet
The Ethernet protocol is based on the following sub-layers:
• Media Access Control (MAC) which manages the interaction of devices with the
shared medium.
• Logical Link Control (LLC) which deals with addressing and multiplexing.
....................................................................................................................................................................................................................................
Issue 1 April 2014
Introduction Data Link layer
....................................................................................................................................................................................................................................
Connectivity
MAC address is a 6-byte identifier with specific ranges per equipment supplier. Some
systems may allow reassignment of the MAC addresses; if this is the case take care on
uniqueness. Network elements may support different rates, 10 Mb/s, 100 Mb/s, 1 Gb/s for
example, which are to be configured and/or aligned by auto-sensing and auto-negotiation
according to IEEE 802.3.
Ethernet networks are limited in physical length and number of hosts connected to them
(< 1024). ARP must be available in the IP context and used to resolve IP to MAC address
translation.
Network layer
Introduction
The Network layer handles packet routing among the network nodes.
The Network layer is handled by two components:
• Protocol for forwarding the packets
• Routing protocol for updating the routing/forwarding tables
In the TCP/IP environment, the protocol for forwarding the packets is IP, and the routing
protocol is OSPF (Open Shortest Path First).
Internet Protocol (IP)

The Internet Protocol (IP) is a connectionless protocol used for communicating data
across a packet-switched network using the Internet Protocol Suite, also referred to as
TCP/IP. It has the task to deliver distinguished protocol datagrams (packets) from the
source host to the destination host solely based on their addresses.
ICMP and ARP are needed as supporting protocols:
• ICMP messages are typically generated in response to errors in IP datagrams, or for
diagnostic or routing purposes.
• ARP is a protocol that allows dynamic distribution of the information needed to
translate a local IP address into a 48-bit Ethernet address. The scope of the ARP
protocol is limited to a single subnet. Prior to message exchange, it may be necessary
to obtain the MAC address for the next-hop IP address, so ARP must be available and
enabled.
Connectivity
In order to provide connectivity, it is essential to guarantee uniqueness of the IP addresses
assigned to the NE. In addition to a unique IP address, it is necessary to configure for
each numbered interface of an NE a sub-network mask (short: netmask). A netmask other
....................................................................................................................................................................................................................................
Issue 1 April 2014
Introduction Network layer
....................................................................................................................................................................................................................................
than /32 (in CIDR notation) has to be used on broadcast layer 2 networks, where multiple
hosts can be reached via a single network interface. All these hosts have to be in the same
subnet, as defined by the address and netmask. Note that routing problems will occur, if
the hosts in one subnet are not all connected to a common layer 2 network. On
point-to-point networks, a /32 netmask can be used, as there can be only one host behind
the network interface, and hence only the interface Id is needed for forwarding.
In general the subnetworks may be determined by physical or administrative facts at the
customer site.
If it is possible to influence the distribution of NEs over different subnetworks, the
following aspects must be considered:
• Physical distribution
• Configuration constraints (scalability) of the routing domain:
– Convergence time after route changes.
– End to end forwarding performance influenced by routing performance and by
path length.
The path length is particularly related to the connectivity, since the Time To Live
(TTL) is expressed in number of hops traversed and is set in accordance to the
expected length.
• Gateway NEs have to handle additional message exchange.
In order to avoid bottlenecks, it is necessary to allocate corresponding bandwidth and
processing power to the gateways. Often it is not clear in advance how much traffic
will be going through. Therefore, it is a good idea to observe the load of the gateway
as well as the bandwidth thresholds per interface.
Open Shortest Path First (OSPF)

OSPF is a link-state routing protocol used in the IP environment.
Connectivity
OSPF behavior must be conformant with RFC 2328 - Open Shortest Path First (OSPF)
version 2, April 1998.
OSPF allows hierarchical routing by splitting a routing domain (Autonomous System,
AS) in areas, which may improve performance. Connectivity between different areas is
managed by routers. Routers can participate with their interfaces in multiple areas,
assuming the Area Border Router (ABR) role. Each area must be connected to the
backbone area (0.0.0.0), either directly or by a virtual link . A typical OSPF topology is
shown in Figure 1-2, “Typical interconnection of OSPF areas” (p. 1-7). Connectivity to
external areas is possible via an Autonomous System Boundary Router (ASBR).
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
OSPF topology
The logical topology created by OSPF is a backbone area (area 0) through which all
inter-area traffic must pass. Around this backbone area, spider web or star topologies of
many directly attached areas can be created. Areas are delineated on the interface, so that
an Area Border Router (ABR) is always part of at least two areas.
The following figure shows the backbone with one Backbone Router (BR) and two
ABRs:
• ABR1 has an interface configured for the area 1. Area 1 contains an Autonomous
System Boundary Router (ASBR) which is connected to a non OSPF area.
• ABR2 has one interface configured for the area 2, and one interface configured for the
area 3; area 2 and area 3 each contain some Internal Routers (IR).
Figure 1-2 Typical interconnection of OSPF areas
IR
ASBR Non OSPF area
Area 1
ABR 1
Backbone area (area 0) BR
ABR 2
IR Area 2 Area 3
IR
IR IR
IR IR
Legend:
ABR Area border router

ABRs are located at the border of the backbone area; they have connections to
two or more areas and have information about each area they belong to.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
ASBR Autonomous System (AS) boundary router

ASBRs are located at the boundary of an AS; they are capable of importing
external information into the local area.
BR Backbone router
BRs are located inside the backbone area (area 0); they have information about
the backbone area topology and about destinations that are reachable outside
the backbone.
IR Internal router
IRs are located inside a non-backbone area; they have neighbors only in the
same area and have information only about that area.
Transport layer
Overview
The Transport layer provides end-to-end communication services for the Application
layer.
The most commonly known Transport layer protocols are the Transmission Control
Protocol (TCP) and the User Datagram Protocol (UDP).
TCP, UDP
TCP and UDP are end-to-end protocols that provide logical channels on behalf of the
application programs. Both are based on the underlying IP routing protocol.
TCP is a connection-oriented protocol with a three-way handshake mechanism. Regular
data exchange starts after connection setup.
UDP is a connectionless protocol, message exchange starts immediately, without a
preliminary setup phase.
Connectivity
In addition to the source and destination IP addresses, source and destination port
numbers are of particular importance for the transport layer addressing. They are part of
the protocol header, and are used to identify the sending and receiving application of the
messages.
The combination of source and destination IP addresses with the source and destination
port numbers are also referred to as “socket”.
....................................................................................................................................................................................................................................
Issue 1 April 2014
Introduction Application layer
....................................................................................................................................................................................................................................
Application layer
The purpose of any DCN is to exchange information on behalf of the applications
supporting one of the following:
• Management Communication Network (MCN) functionality:
Exchange of management commands with the corresponding responses, spontaneous
notifications, file transfer.
• Signaling Communication Network (SCN) functionality:
Exchange of signaling messages. The signaling protocol of choice is the Reservation
Protocol (RSVP).
....................................................................................................................................................................................................................................
Issue 1 April 2014
Introduction Application layer
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 1 April 2014
2 DCN planning
2
Overview
Purpose
This section provides information on how to plan DCN for the use with Alcatel-Lucent
1830 PSS.
Contents
General 2-2
Preconditions and requirements 2-2
Connection of Alcatel-Lucent 1830 PSS equipment to the management DCN 2-8
MCN and SCN aspects 2-20
Management DCN aspects 2-20
Signaling DCN aspects 2-29
Network topology concept and dimensioning 2-39
The Alcatel-Lucent 1830 PSS management network 2-39
Basic network topologies 2-42
Address planning 2-45
Network IP architecture 2-45
Engineering guidelines 2-52
Summary of important rules and guidelines 2-52
...................................................................................................................................................................................................................................
Issue 1 April 2014
DCN planning Preconditions and requirements
General
....................................................................................................................................................................................................................................
General
Preconditions and requirements

Introduction
This section describes preconditions, requirements, and limitations imposed by system
design.
Major system design features

• The system supports TCP/IP, including OSPF routing support.
• The system does not support OSI-based communication.
• The system does not support a strict separation of Management Communication
Network (MCN) and Signaling Communication Network (SCN) IP traffic.
• The system does not support separate LAN interfaces for SCN traffic.
TCP/IP support
TCP/IP is supported over:
• Customer LAN interfaces
• Embedded Communication Channel (ECC)
• Optical Supervisory Channel (OSC)
The TCP/IP protocol stack supported for an IP-based DCN is shown in the following
table.
Table 2-1 TCP/IP protocol stack
Layer Name Service/Protocol

7 Application raw terminal TL1, telnet TL1, telnet CLI, FTP, NTP,
RSVP-TE (GMPLS signaling), SFTP, SNMP
6 Presentation
5 Session SSH, SSL
4 Transport TCP, UDP
3 Network IPv4, ICMP, ARP, OSPF
2 Data Link PPP over HDLC (RFC 1662), IPCP (RFC 1332), LCP (RFC
1661), Ethernet
1 Physical LAN, ECC (OSC, GCC)
....................................................................................................................................................................................................................................
Issue 1 April 2014
General
....................................................................................................................................................................................................................................
Important! The maximum NE SNMP packet size is 2047. The maximum NE MTU
size that can be set on any NE external communication interface (Ethernet, OSC,
GCC) is 1500.
SNMP packets larger than the path MTU size will be fragmented. As a result
customer DCN routers should not be configured with any firewall that blocks
fragmented packets.
User service interfaces

The Alcatel-Lucent 1830 PSS systems provide user service interfaces for local craft
terminal access or for the connection of external management systems or other external
equipment.
Depending on the type of shelf, these user service interfaces are located on the following
equipment components:
Table 2-2 User service interfaces
Type of shelf Equipment components providing the user service interfaces

PSS-16/PSS-32 User Panel (USRPNL); see “User Panel (USRPNL) of PSS-16/PSS-32
shelves” (p. 2-3)
Equipment controller (EC); see “Equipment controller (EC) of
PSS-16/PSS-32 shelves” (p. 2-6)
User Panel (USRPNL) of PSS-16/PSS-32 shelves

The User Panel provides four (4) general purpose switched auto-sensing LAN ports
(10/100BaseTX):
• OAMP – External LAN interface that can be used to connect to an External
Management System (EMS) or to interconnect Alcatel-Lucent 1830 PSS NEs
together.
• VoIP – The VoIP port can be used to connect to an IP phone or to interconnect
Alcatel-Lucent 1830 PSS NEs together.
• E1 and E2 – External LAN interfaces that can be used to connect to externally
managed devices or to interconnect Alcatel-Lucent 1830 PSS NEs together.
These ports are auto-sensing, so either a cross-over or straight-through Ethernet cable can
be used.
....................................................................................................................................................................................................................................
Issue 1 April 2014
General
....................................................................................................................................................................................................................................
The following ports are available for craft terminal access:
• The Alcatel-Lucent 1830 PSS-32 supports 2 craft ports. There is a female 9-pin
D-subminiature (DB9) connector and a USB-B port. Both support local RS-232C
serial interface (support setting: 34800 baud, 1 stop bit, no parity) for connection to a
craft terminal via serial link.
• The Alcatel-Lucent 1830 PSS-16 supports a USB-B port which supports local
RS-232C serial interface (support setting: 34800 baud, 1 stop bit, no parity) for
connection to a craft terminal via serial link.
Note: Either the DB9 port or the USB-B port can be used to connect serially to the
NE. However, only one port should be active at any given time.
The front views of the Alcatel-Lucent 1830 PSS-32 and Alcatel-Lucent 1830 PSS-16
User Panels are shown in the following figures.
Figure 2-1 Alcatel-Lucent 1830 PSS-32 User Panel faceplate
....................................................................................................................................................................................................................................
Issue 1 April 2014
General
....................................................................................................................................................................................................................................
Figure 2-2 Alcatel-Lucent 1830 PSS-16 User Panel faceplate
1 18 11 2 9 6 4 8
12 13 14 15 16 17 3 5 7
USERPNL
Legend:
1 “STATUS” LED 10 “CRAFT” interface (PSS-32 User Panel only)

2 “HOUSEKEEPING” interface 11 “ALARM” interface
3 “MJ/PROMPT” LED 12 “OAMP” interface
4 “CR/PROMPT” LED 13 “VOIP” interface
5 “WARNING” LED 14 “E1” interface

6 “MN/DEFRD” LED 15 “E2” interface
7 “ABNORMAL” LED 16 “CRAFT” USB connector

8 “ATTENDED” LED 17 “LAMP TEST” button
9 Alarm cut-off button (ACO) 18 “RACK LAMP” interface
Table 2-3 DCN-related external interfaces (USRPNL)
CRAFT DB9 connector supporting RS-232C serial interface (support setting: 38,400 baud, 1 stop
(PSS-32 User Panel bit, no parity) for connection to craft terminal via a serial link.
only)
OAMP OAMP LAN port to connect the NE to a management system.

VOIP VoIP LAN interface to connect an IP phone to an IP managed DCN.
E1 E1 LAN extension subrack connection

E2 E2 LAN extension subrack connection
....................................................................................................................................................................................................................................
Issue 1 April 2014
General
....................................................................................................................................................................................................................................
Table 2-3 DCN-related external interfaces (USRPNL) (continued)
CRAFT USB connector supporting RS-232C serial interface (support setting: 38,400 baud, 1 stop
bit, no parity) for connection to craft terminal via a serial link.
During an EC switchover caused by a failure of the active EC, there may be a brief loss of
communication to the NE from NMS. The applications will be launched on the standby
EC. Through the back plane a LAN communication is established between the User Panel
and the two EC boards.
Equipment controller (EC) of PSS-16/PSS-32 shelves

Every Alcatel-Lucent 1830 PSS-32 and Alcatel-Lucent 1830 PSS-16 shelf contains at
least one EC; two if EC redundancy is required.
Each EC provides four (4) RJ45 LAN ports (10/100BaseTX). These ports are auto
sensing and provide the following functionality:
• CIT – is dedicated to CIT connection.
Only the ECs in the main shelf have the CIT port enabled.
• AUX – is disabled. This port is for future use.
• ES1 and ES2 – are reserved for inter-shelf connectivity (between main shelf and
extension shelf, or between extension shelves).
....................................................................................................................................................................................................................................
Issue 1 April 2014
General
....................................................................................................................................................................................................................................
The front view of the Alcatel-Lucent 1830 PSS-32 and Alcatel-Lucent 1830 PSS-16
equipment controller (EC) is shown in the following figure:
Figure 2-3 Front view of the EC
Legend:
1 “STATUS” LED
2 USB interface
3 “CIT” interface
4 “AUX” interface
5 “ES 1” interface
6 “ES 2” interface
Duplex mode
Duplex mode is configurable on the EC CIT port and the OAMP, VoIP, E1, and E2 ports
on the User Panel (PSS-16/PSS-32).
....................................................................................................................................................................................................................................
Issue 1 April 2014
General
....................................................................................................................................................................................................................................
The ports can be configured for the following duplex modes:
• Full duplex
• Half duplex
• Auto (default setting)
“Auto” indicates that the port will participate in auto negotiation of the duplex mode.
Link speed
Link speed is configurable on the EC CIT port and the OAMP, VoIP, E1, and E2 ports on
the User Panel (PSS-16/PSS-32).
The ports can be configured for the following values of the link speed:
• 10 Mb/s
• 100 Mb/s
• Auto (default setting)
“Auto” indicates that the port will participate in auto negotiation of the link speed.
Connection of Alcatel-Lucent 1830 PSS equipment to the

management DCN
Introduction
The present section provides information concerning the physical connections that need
to be established between the Alcatel-Lucent 1830 PSS equipment and the management
DCN.
Note: As Alcatel-Lucent 1830 PSS can be used as a pure photonic or pure switching
system, or as a combination of both in a converged node, and as these systems can act
as gateway NEs (GNEs) or remote NEs (RNEs) in an Alcatel-Lucent 1830 PSS
management network, the following scenarios are described:
• “Connection of a pure photonic system to the management DCN” (p. 2-10)
• “Connection of a converged system as a GNE (GNE connection option 1)”
(p. 2-10)
(p. 2-12)
(p. 2-14)
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN planning Connection of Alcatel-Lucent 1830 PSS equipment to the
General management DCN
....................................................................................................................................................................................................................................
• “Connection of a converged system as an RNE (RNE connection option 1)”
(p. 2-16)
• “Connection of a converged system as an RNE (RNE connection option 2)”
(p. 2-17)
The following schematic diagrams will be used throughout this section to illustrate the
DCN connections of Alcatel-Lucent 1830 PSS system compounds:
Figure 2-4 Schematic diagrams of Alcatel-Lucent 1830 PSS system compounds
E1 E2 VOIP OAMP OAMP OAMP
LSW (RSTP) LSW (RSTP)
Active EC
FLC A
FLC B
(active)
Photonic
compound Switching compound
OSC GCC GCC
Note:
• External LAN ports (OAMP, E1, E2) are provided on both MTC1T9 cards.
Only the ports on the currently active MTC1T9 card are enabled, the ports on the
standby card are disabled (shown as hatched boxes in the figure).
Important! Use twisted-pair LAN cables (halogen-free standard CAT6 LAN cables)
with RJ45 connectors at both ends to connect the system compounds to the DCN
equipment (routers or LAN switches).
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
Connection of a pure photonic system to the management DCN
The following figure shows the recommended way of connecting a photonic compound to
the management DCN as a GNE.
Figure 2-5 Management DCN connection of a photonic compound GNE
x
Management network
(IP based)
E1 E2 VOIP OAMP
Active EC
Photonic (PSS-16/PSS-32)
compound
OSC GCC
The OAMP port on the user panel has to be connected to a single port of the management
DCN LAN infrastructure.
Management DCN connection of photonic compound RNEs
Photonic compound RNEs have direct or indirect in-band OSC connectivity to one or
more GNEs.
Connection of a converged system as a GNE (GNE connection option 1)

Figure 2-6, “Management DCN connection of a converged system (GNE connection
option 1)” (p. 2-11) shows a way of connecting a converged system as a GNE where both
compounds are connected independently to the management DCN.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
Figure 2-6 Management DCN connection of a converged system (GNE connection

option 1)
Management
system
x Management network
(IP based)
x(RSTP)
LSW
OAMP OAMP E1 E2 VOIP OAMP
Active EC
FLC A
FLC B
(active)
Photonic
Switching compound compound
GCC OSC GCC
The following criteria characterize this GNE connection option:

• The photonic compound needs a single LAN port on the management DCN to
connect the OAMP LAN port to.
• The switching compound offers OAMP LAN port redundancy.
– To make use of this, both OAMP LAN ports need to be connected to an
RSTP-enabled LAN switching infrastructure. In the easiest case, this is a single
LAN switch, as depicted in Figure 2-6, “Management DCN connection of a
converged system (GNE connection option 1)” (p. 2-11). More complex
topologies are possible, which offer better resiliency against LAN equipment
failures.
– Both OAMP LAN ports have to be connected to a common IP subnetwork.
– It is possible, but strongly discouraged, to not make use of OAMP LAN
redundancy. As each OAMP LAN port is provided by one FLC, an equipment
outage of the connected FLC would interrupt GNE reachability.
• For uplink card management, the management DCN has to provide connectivity
between both compounds.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
This is reached most easily by connecting the OAMP LAN ports of both compounds
to a common IP subnetwork. This is indicated in Figure 2-6, “Management DCN
connection of a converged system (GNE connection option 1)” (p. 2-11) by the
extended external LAN switch (dashed line).

option 2)” (p. 2-13) shows an alternate way of connecting a converged system as a GNE.
One of the OAMP ports of the switching compound is connected to the out-of-band DCN
(OOB DCN, management DCN). The OAMP port (or one of the other external LAN ports
E1/E2/VOIP) of the photonic compound is connected to the second OAMP port of the
switching compound. Via the on-board LAN switches of the switching compound FLCs,
this setup puts FLCs and ECs into a common IP subnet with the OOB gateway router.
Management traffic for the photonic compound passes through the LAN switches without
impacting switching compound FLC CPUs. In-band DCN has to be used as a backup, as
the OAMP LAN connections are single points of failure. This requires OSPF on OAMP
LANs and ECCs, and careful design of the in-band DCN to provide the right level of
DCN redundancy.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................

option 2)
Management
system
Management network
(IP based)

E1 E2 VOIP OAMP OAMP OAMP
LSW (RSTP) LSW (RSTP) Active EC
FLC A
Active EC FLC B
FLC A (active)
FLC B
(active) Photonic
Photonic Switching compound compound
compound Switching compound GCC GCC OSC OSC
OSC OSC GCC GCC
In-band DCN (GCCs)
In-band DCN (OSCs)
Advantages
The GNE connection option 2 provides the following advantages:
• Only one customer LAN port needed.
• Low latency/high throughput inter-compound communication, as long as the
connected FLC card is available.
• No additional IP forwarding load on FLC/EC CPUs, as long as LAN connectivity is
operational.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
Disadvantages
The GNE connection option 2 provides the following disadvantages:
• The OAMP LAN port redundancy feature of the switching compound is not used. If
the OOB-connected FLC is not operational, OOB DCN connectivity of the
dual-compound node is lost.
• Photonic compound OOB-connectivity depends on availability of both switching
compound FLC on-board LAN switches. That means that interruptions are possible
during maintenance scenarios (FLC reset, FLC switch, ISU, FLC replacement).
• In a split LAN scenario, if one or both of the LAN links are down, some of the IP
addresses on the OAMP LAN may become unreachable from parts of the network:
– This happens, because the OSPF routers connected to the split LAN each
advertise a subnet route for the entire split LAN, but only a part of the split LAN
is reachable via each of the routers.
– This can affect all addresses on the subnet (gateway router address, FLC A
address, FLC B address, EC OAMP address), except for the activeFLC address of
the switching compound.
– The affected addresses are not essential for managing the node. But e.g. debug
access to the standby FLC can be affected.
– The activeFLC address, which is used for managing the switching compound, is
advertised by the active FLC as a host route, which takes precedence over the
subnet route.
– The photonic compound is managed via a loopback address, which is not
impacted by a split LAN scenario

option 3)” (p. 2-15) shows a further alternative of connecting a converged system as a
GNE.
The GNE connection option 3 is a combination of the preceding connection options: Each
compound is connected to the out-of-band DCN (OOB DCN, management DCN) via one
OAMP LAN port. Moreover, the second OAMP port of the switching compound is
connected to one of the additional external LAN ports (E1/E2/VOIP) of the photonic
compound. This additional port is in the same IP subnet as the OAMP LAN of the
switching compound, whereas the OAMP port of the photonic compound has to be in a
different IP subnet. With OSPF running on all involved LAN ports, LAN port redundancy
is achieved for the dual compound node, as long as the inter-compound link is available.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................

option 3)
Management
system
Management network
(IP based)

E1 E2 OAMP VOIP OAMP OAMP
LSW (RSTP) LSW (RSTP) Active EC
FLC A
Active EC FLC B
FLC A (active)
FLC B
(active) Photonic
Photonic Switching compound compound
compound Switching compound GCC GCC OSC OSC
OSC OSC GCC GCC
In-band DCN (GCCs)
In-band DCN (OSCs)
Advantages
The GNE connection option 3 provides the following advantages:
inter-compound LAN link is available, or both OOB connections are available.
• No additional load on FLC CPU, as connection to photonic compound via switching
compound OAMP port is via FLC LAN switches.
• No additional load on EC CPU, as long as the OOB-connected FLC card is available.
• LAN redundancy for dual compound node.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
Disadvantages
The GNE connection option 3 provides the following disadvantages:
• Two OOB DCN LAN ports needed.
• Two IP subnets needed on OOB LAN.
• One of the external LAN ports of the photonic compound is occupied by the
connection to the switching compound, and cannot be used for its original purpose
(external equipment for E1/E2 ports, IP phone for VOIP port).
• Split LAN scenario (applies analogously to GNE connection option 2).
Connection of a converged system as an RNE (RNE connection option 1)

Figure 2-9, “Management DCN connection of a converged system RNE with partial LAN
connectivity” (p. 2-16) shows a converged system as RNE with partial LAN connectivity.
One of the OAMP ports of the switching compound is connected to the OAMP port (or
one of the other external LAN ports) of the photonic compound via a point-to-point LAN
cable. As long as this connection is operational, inter-compound communication is via
LAN. The path via in-band DCN, GNEs, and out-of-band DCN is used as a backup for
the LAN. To enable dynamic routing via either LAN or DCN, OSPF needs to be enabled
on the interconnected LAN interfaces of both compounds.
Figure 2-9 Management DCN connection of a converged system RNE with partial
LAN connectivity
Active EC
FLC A
FLC B
(active)
Photonic
GCC GCC OSC GCC
Inband DCN (GCCs)

Inband DCN (OSCs)
GNE
Out-of-band DCN GNE
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
Advantages
The RNE connection option 1 provides the following advantages:
• Only limited LAN equipment needed (1 cable).
LAN-connected FLC card is available.
Disadvantages
The RNE connection option 1 provides the following disadvantages:
• Permanent External LAN Failure (EXTLANFAIL) alarm on the unconnected
OAMP LAN port of the switching compound.
• Rerouting via DCN needed as soon as the LAN-connected FLC fails, resulting in high
latency and low throughput for inter-compound communication, and IP forwarding
load in all intermediate NEs caused by inter-compound traffic.
Connection of a converged system as an RNE (RNE connection option 2)

Figure 2-10, “Management DCN connection of a converged system RNE with full LAN
connectivity” (p. 2-18) shows a converged system as RNE with full LAN connectivity.
Both OAMP ports of the switching compound are connected to the OAMP port (or one of
the other external LAN ports) of the photonic compound via an external LAN switch,
which needs to be configured for running RSTP. OSPF should be configured on the
OAMP LAN of both compounds to allow the usage of in-band and out-of-band DCN as a
last resort backup for the LAN. Further external equipment, such as Raman amplifiers or
booster amplifiers, can be connected to the same LAN switch.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
Figure 2-10 Management DCN connection of a converged system RNE with full LAN
connectivity
LSW (RSTP)
Active EC
FLC A
FLC B
(active)
Photonic
GCC GCC OSC GCC
Inband DCN (GCCs)

Inband DCN (OSCs)
GNE
Out-of-band DCN GNE
Advantages
The RNE connection option 2 provides the following advantages:
• Fully leverages the OAMP LAN port redundancy of the switching compound.
• Low latency/high throughput/highly resilient inter-compound communication, as long
as the LAN-connectivity is available.
Disadvantages
The RNE connection option 2 provides the following disadvantages:
• An additional external LAN switch is needed, which needs to be properly configured
(RSTP).
RNE connection option assessment

From the described RNE connection options, the option with partial LAN connectivity
(RNE connection option 1) might be preferrable in sunny-day scenarios because the
demands concerning the required LAN equipment are kept to a minimum (single cable).
On the other hand, the option with full LAN connectivity (RNE connection option 2)
provides the best level of failure resiliency, but comes with additional cost (external LAN
switch, LAN switch management).
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
For cases, where external equipment is connected to the E1 or E2 port via an external
LAN switch (i.e. there are more than two external equipment entities), the option with full
LAN connectivity (RNE connection option 2) can be used without extra cost, as both
compounds and the external equipment can all be connected to the same external LAN
switch. Instead of the OAMP port, one of the E1/E2 ports of the photonic compound can
then be connected to the external LAN switch.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN planning Overview
MCN and SCN aspects
....................................................................................................................................................................................................................................
MCN and SCN aspects
Overview
Purpose
The present chapter describes the DCN aspects of management communication and
signaling communication.
No strict separation of MCN and SCN traffic

There is no strict separation of Management Communication Network (MCN) and
Signaling Communication Network (SCN) IP traffic. The same DCN infrastructure is
used for both.
Contents
Management DCN aspects 2-20

Signaling DCN aspects 2-29
Management DCN aspects

Management DCN setup of a photonic node
The management DCN setup of a photonic node is depicted in Figure 2-11, “Basic GNE
DCN setup (photonic application) ” (p. 2-21) for a GNE and in Figure 2-12, “Basic RNE
DCN setup (photonic application) ” (p. 2-23) for an RNE.
The SYSTEM loopback address, which is configured on the active EC, is used as
management address, that is as the address, which is contacted by management systems
(for CORBA as well as for TL1 management). This address is also used as local source
address for outward-directed connections (e.g. for file transfer).
The SYSTEM IP address is used as local interface address by all unnumbered interfaces
(OSCs, GCCs).
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN planning Management DCN aspects
MCN and SCN aspects
....................................................................................................................................................................................................................................
Figure 2-11 Basic GNE DCN setup (photonic application)
Out-of-band DCN
Gateway Router IP Phone
External External
equipment equipment
OAMP connector E1 connector E2 connector VOIP connector
EC A OAMP E1 E2 VOIP EC B OAMP E1 E2 VOIP

(main shelf) (main shelf)
EC A EC B
CPU CPU
(active) IP addresses: (standby)
- OAMPIP, E1IP, E2IP, VOIPIP
act.
pas. LO
pas.
OSPF pas. IP address:
- SYSTEMIP
act. act.
IP address: IP address:
- SYSTEMIP - CITIP
GCC / GCC /
OSC OSC CIT connector CIT connector
In-band DCN
WebUI
Four external LAN interfaces are provided via the user panel:
• The OAMP LAN is intended to connect a GNE to the OOB DCN.
• The E1 and E2 external LAN interfaces can be used to connect to externally managed
devices or to interconnect Alcatel-Lucent 1830 PSS NEs together.
• The VOIP LAN is foreseen to optionally connect an IP phone.
If used, all external LAN interfaces have to be configured for an IP subnet of their own.
A GNE or RNE is connected to the in-band DCN via OTU GCC0 or OSC interfaces.
These are unnumbered interfaces, using the SYSTEM loopback address as their local
interface address.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
As the SYSTEM loopback address is used as the management address, this address has to
be reachable throughout the DCN, and has to be allocated from an official address range.
The same is true for the IP subnets on the E1, E2, and VOIP LANs. These addresses have
to be officially assigned and routed to facilitate the management of external equipment,
and the reachability of the IP phone.
For these addresses to be reachable from management systems, routing information has to
be exchanged between the NEs and the OOB DCN. OSPF is used for this purpose. Please
note that static routes are an alternative to the OSPF dynamic routing protocol.
The stub networks E1, E2, VOIP, and the SYSTEM loopback address are included in the
router LSA emitted by the NE. Note that, apart from the simple setup shown in Figure
2-11, “Basic GNE DCN setup (photonic application) ” (p. 2-21), arbitrary network
topologies can be connected to the E1, E2, and VOIP LANs, and OSPF can be configured
in active mode on these LANs. Any of these LANs can also be used for dual-compound
node interconnections; see “Connection of Alcatel-Lucent 1830 PSS equipment to the
management DCN” (p. 2-8).
Typically, OSPF runs in active mode on the OAMP LAN of GNEs, and on OSC/GCC
interfaces.
In general, the behavior regarding OSPF is as follows:
• OSPF may be configured to be Disabled/Enabled (active mode) or Redistributed
(passive mode) on any of the OAMP/VoIP/E1/E2 interfaces of a photonic compound.
• OSPF may be configured to be Disabled or Redistributed (passive mode) on the CIT
interface of a photonic compound.
• When an OSC/GCC interface is enabled, OSPF is enabled (active mode) and cannot
be disabled.
Important! Due to the mechanism for the distribution of wavekeys via OSPF opaque
LSAs, all OSC/GCC interfaces of all NEs in a WDM domain must be in a single
OSPF area. LAN interfaces can be placed in separate areas.
The OAMP IP addresses are only needed for routing purposes, and can therefore be kept
private to their area.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
Figure 2-12 Basic RNE DCN setup (photonic application)

IP Phone
External External
equipment equipment
OAMP connector E1 connector E2 connector VOIP connector
EC A OAMP E1 E2 VOIP EC B OAMP E1 E2 VOIP

(main shelf) (main shelf)
EC A EC B
CPU CPU
(active) IP addresses: (standby)
- E1IP, E2IP, VOIPIP
pas. LO
pas.
OSPF pas. IP address:
- SYSTEMIP
act. act.
- SYSTEMIP - CITIP
GCC / GCC /
OSC OSC CIT connector CIT connector
In-band DCN
WebUI
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
OSPF peering model (photonic application)
The OSPF peering mode, as depicted in Figure 2-13, “OSPF peering model (photonic
application)” (p. 2-24), is the default setup with properties equivalent to those described
for switching NEs; see “” (p. xv).
Figure 2-13 OSPF peering model (photonic application)
A split OAMP LAN scenario does not have adverse effects on the manageability of the
GNE, as OAMP LAN addresses are not used for connecting to the GNE. A backup route
to the SYSTEM loopback address via another GNE and the in-band DCN are
automatically found.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
OSPF non-peering model (photonic application)
As the SYSTEM loopback IP address is used as the management address, there is no
exact equivalent of the OSPF non-peering mode of the switching NE.
As an alternative, proxyARP can be configured on the OAMP LAN of GNEs, as depicted
in Figure 2-14, “OSPF non-peering model via proxy ARP (photonic application)”
(p. 2-26). The GNE answers ARP requests for all IP addresses, for which it knows the
routes. To the gateway router, this makes the whole NE sub-domain – including the
in-band DCN – look like a single IP subnet.
This makes routing in the OOB DCN independent from the in-band DCN, but it does not
provide resiliency against split LAN scenarios in GNE sites: All gateway routers advertise
the NE sub-domain “subnet” address into the OOB DCN. Each node in the OOB DCN
selects the nearest gateway router for routing to the NE sub-domain. If the selected
gateway router is detached from its GNE, the NE sub-domain is not reachable from the
part of the OOB DCN, which is closest to the detached GNE.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
Figure 2-14 OSPF non-peering model via proxy ARP (photonic application)
NOC 2
NOC 1
Gateway Router
Gateway Router NOC 2
Out-of-band DCN
NOC 1
OOB IFs Gateway Router OOB IFs Gateway Router

GNE A GNE B
IP subnet spanning: IP subnet spanning:

RProtX RProtX
- all NE’s SYSTEMIP - all NE’s SYSTEMIP
- all OAMP subnets - all OAMP subnets
pas. pas.
- all E1, E2, VOIP subnets - all E1, E2, VOIP subnets
OAMP LAN OAMP LAN
OAMP E1 E2 VOIP OAMP E1 E2 VOIP

GNE A GNE B
IP addresses: IP addresses:
- OAMP IP subnet, - OAMP IP subnet,
proxyARP - E1, E2, VOIP subnets proxyARP
- E1, E2, VOIP subnets
pas. LO pas. LO
pas. pas.
OSPF IP address: OSPF IP address:
act. act. - SYSTEMIP act. act. - SYSTEMIP
- SYSTEMIP - SYSTEMIP
OSC OSC OSC OSC
In-band DCN
OAMP E1 E2 VOIP
RNE C
IP addresses:
- E1, E2, VOIPsubnets
pas.
OSPF pas. LO
IP address:
act. act. - SYSTEMIP
IP address:
- SYSTEMIP
OSC OSC
Recommendations for an MRN control plane

In a network – be it MRN, overlay, pure switching, or pure photonic – NE management
more or less is a relationship between the management system and each single NE. The
DCN has to provide proper end-to-end routing.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
In principle, the concepts existing for switching and photonic NEs could be used
independent of each other. However, this would produce two NE sub-domains, each with
its own in-band DCN and specific OOB DCN attachment. For converged nodes, also a
convergence of both NE sub-domains is needed, if synergies of the converged-node
concept shall be used for the OOB DCN attachment; also see section “Connection of
Alcatel-Lucent 1830 PSS equipment to the management DCN” (p. 2-8).
The following address allocation rules apply:
• Addresses to be allocated from the official address space:
– Switching node OAMP subnets (including ACTIVEFLCIP management
addresses)
– Photonic node SYSTEM loopback addresses
– Photonic node E1, E2, VOIP subnets (if used)
• Addresses, which might be allocated from a private address space, and can be kept
contained in the NE area/NE domain:
– Switching node LOOPBKIP addresses
– Photonic node OAMP subnets (if not already contained in the switching node
OAMP subnet of a dual-compound node)
Important! For an MRN network, it is essential to set up a single NE sub-domain.
This is required mainly for signaling purposes, in order to facilitate NE-to-NE
communication between layers.
The preferred setup for an MRN network is an OSPF peering model, as this model is
supported in a very similar way by switching nodes and photonic nodes as well; see “”
(p. xv).and “OSPF peering model (photonic application)” (p. 2-24).
OSPF peering model (MRN)
Important! All NEs, that is the complete in-band DCN connecting the NEs, needs to
be in a single OSPF area.
There are two options for the location of the area boundary:
• Inside GNEs, configuring the OAMP LAN into the backbone area:
– This might be an option for large numbers of NEs, in order to keep a reasonably
low area size.
– This might cause a conflict between the need for a reasonably high number of
GNEs, and the need for a reasonably low number of ABRs.
• In the OOB DCN:
– Some part of the OOB DCN, including the NEs’ gateway routers and enough
connectivity to ensure OOB routing resiliency from all ABRs to all GNEs needs to
be in the same area as the NEs.
– A reasonably low number of ABRs are selected in the OOB DCN.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
A fair number of GNEs from each type of node (switching or photonic) needs to be
defined to keep management traffic out of the in-band DCN as much as possible.
Otherwise, bandwidth usage conflicts might arise between management and signaling
traffic.
What can be considered a “fair number of GNEs”, depends on the network topology:
• For ring networks, at least two GNEs per ring should be assigned at “opposite ends”
of the ring, that is at distant points of the ring.
• For mesh networks, there should be not more than 3 or 4 hops from each RNE to the
nearest GNE.
• In control plane networks, there should be at least one GNE per 10 up to 20 RNEs at
the maximum.
OSPF non-peering model (MRN)
If a non-peering model is mandatory in an operator network (for example if the OOB
DCN uses a routing protocol other than OSPF), the following options exist:
• Option 1: Configure all NEs as GNEs (similar to “” (p. xv))
– Connect each NE via its OAMP LAN to a gateway router (dual-compound nodes
can use a common subnet to connect to a single router).
– Each gateway router, which is connected to a photonic node, has to be configured
with a static route via the OAMP LAN to the SYSTEM loopback address of that
node, and has to redistribute that static route into the OOB routing domain.
– Each photonic node has to be configured with a static default route via the
gateway router on the OAMP LAN.
– For management purposes, no dynamic routing is needed on the NEs.
– Restriction: Split LAN scenarios or in-band DCN partitioning scenarios cannot be
mitigated in this setup.
• Option 2: Follow the non-peering model of the switching nodes
– Only switching nodes are used as GNEs.
– Photonic nodes are attached to switching nodes either via LAN (dual-compound
nodes), or via GCC0. Best performance is reached, if dual-compound nodes are in
GNE locations, in order to keep photonic management traffic off GCCs.
Be aware, that OSPF has to be active on the OAMP LAN of dual-compound
nodes. This has to be tolerated by the non-peering gateway routers.
– The non-peering mode with tunnels between GNEs and NOC sites has to be used
to ensure routing to photonic NEs and switching RNEs.
Drawback: All management traffic needs to go through the FLC CPUs (tunnel
endpoints) of the switching GNEs.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
• Option 3: Follow the non-peering model of the photonic nodes
– Only photonic nodes are GNEs, supporting proxy ARP. All externally visible IP
addresses are allocated from a reasonably small IP range; see Figure 2-14, “OSPF
non-peering model via proxy ARP (photonic application)” (p. 2-26).
– Switching nodes are attached to photonic nodes either via LAN (dual-compound
nodes), or via GCC0.
Be aware, that OSPF has to be active on the OAMP LAN of dual-compound
nodes. This has to be tolerated by the non-peering routers.
– Drawback 1: All management traffic needs to go through the EC CPUs of a few
photonic GNEs.
– Drawback 2: Split LAN scenarios or in-band DCN partitioning scenarios cannot
be mitigated.
• Option 4: Set up a complete OSPF domain comprising the NEs and a small part of
the OOB DCN (quasi-peering setup)
– This can be a backbone-only domain, which in essence follows the principles of
the OSPF peering model.
– ASBRs can be configured to interact with the main part of the OOB DCN.
Address summarization should be applied for route import from the main DCN.
– Enough connectivity needs to be present in the OSPF domain, to provide routing
resiliency between ASBRs and GNEs.
The latter option should be preferred, where an end-to-end peering model is not feasible.
Please note that all NEs do not necessarily have to be GNEs as described in option 1 but
static routes may be configured instead.
Signaling DCN aspects

Introduction
The aim of the present chapter is to describe the general considerations for the signaling
DCN with regard to switching NEs and photonic NEs, and to provide recommendations
for an MRN control plane:
• “Signaling DCN setup for photonic NEs” (p. 2-30)
• “Recommendations for an MRN control plane” (p. 2-30)
In some cases, a distinction is necessary between releases prior to Release 6.0.0 (that is
releases without MRN support) and later releases, where an MRN-capable control plane
is introduced.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN planning Signaling DCN aspects
MCN and SCN aspects
....................................................................................................................................................................................................................................
Signaling DCN setup for photonic NEs
In some ways, the design of the signaling DCN for photonic NEs is similar to the design
for switching NEs. In other aspects, the design differs.
The signaling DCN setup for photonic NEs is similar to the one for switching NEs in the
following points:
• For each node, a GMRE node address is defined, which is used for the
communication between data-plane neighbors.
• For each node, a GMRE notify address is defined, which is used for addressing RSVP
notify messages.
The signaling DCN setup for photonic NEs differs from the one for switching NEs in the
following points:
• No static routes are used for GMRE node addresses. Direct neighbor communication
completely relies on OSPF routing.
– The restoration anomaly (see “” (p. xv)) cannot be avoided. However, the
additional time for routing convergence is tolerable compared to the restoration
times in a photonic network that are much longer than those in a switching
network anyway.
– The stranded resources anomaly (see “” (p. xv)) does not occur as long as the NE
area does not become partitioned.
– The GMRE node addresses are visible throughout the NE area. They may be kept
contained in the area, and not exported to other areas.
• The GMRE notify addresses are separate loopback addresses, not equal to any other
address of the NE. Like the GMRE node addresses, they have to be routed throughout
the area, but may be kept contained inside the area.
• IP-in-IP tunnels are not supported for photonic NEs. The in-band DCN is protected by
the standard routing mechanisms.
Recommendations for an MRN control plane

A multi-region network (MRN) is defined as a traffic engineering domain supporting at
least two different switching types, either hosted on the same device or on different ones
and under the control of a single GMPLS control plane instance.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
In an MRN setup, switching and photonic nodes interoperate in a common network.
MRN-specific types of communication relations are supported, as depicted in Figure
2-15, “Types of communication relations in MRN” (p. 2-31).
Figure 2-15 Types of communication relations in MRN
The communication relations in MRN are characterized as follows:

• In dual compound nodes (A/D, C/F), both the switching compound and the photonic
compound each run their own instance of the control-plane. Both instances need to
communicate as control-plane neighbors.
– Each of the compounds needs to reach the GMRE node address of its peer.
– There are no in-band channels available via the uplinks between the compounds.
– OOB connectivity between the co-located compounds is provided via LAN,
independent of whether the node is in the GNE or RNE role. Options for
interconnecting dual compound nodes are described in the section “Connection of
Alcatel-Lucent 1830 PSS equipment to the management DCN” (p. 2-8).
• Switching NEs can be connected to photonic NEs via black-and-white (B&W) links,
NEs E and B for example. Both NEs need to communicate as control-plane neighbors.
– Each of the NEs needs to reach the GMRE node address of its peer.
– GCC0 can be used as direct in-band channel between the NEs.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
• On-demand HO-ODU links (FA-UNTERM) can be set up between switching NEs (D,
F) via the photonic infrastructure (A-B-C). The NEs D and F need to communicate as
control-plane neighbors.
– Each of the NEs needs to reach the GMRE node address of its peer.
– By setting up FA-UNTERM links, the number of neighbors of a switching node
can become very large (in theory up to a full mesh of all switching nodes).
– HO-ODU GCC1 can be set up via the FA-UNTERM link by management request.
Due to limited GCC resources, this setup is not done automatically; some
FA-UNTERM links may remain with GCC1 disabled.
The following listing contains recommendations and other important information that
should be observed for the setup of the MRN signaling DCN:
• All NEs should be in one common OSPF area.
This recommendation is mainly driven by the wavekey distribution mechanism via
OSPF opaque LSAs. Moreover, it also helps keeping signaling traffic off the
backbone area, and keeping NE addresses contained inside the single area.
• Support/Usage of OOB tunnels or static routing by photonic NEs:
– Photonic NEs do not support OOB tunnels.
– In principle, photonic NEs do support static routing. However static routing is
intentionally not used by the GMRE for strictly binding in-band signaling to the
data-plane.
• On direct links between switching NEs, GMRE automatically sets up in-band and
OOB IPCCs including the associated static routes to neighbor GMRE node addresses.
• If an in-band IPCC is configured over an FA-UNTERM link, a static route to the
neighbor GMRE node address is configured automatically. If both peers are GNEs,
also an OOB IPCC including the static routes is configured automatically.
• Switching and photonic NEs support the free routing of GMRE node addresses.
– Thus, the GMRE node addresses of switching as well as photonic NEs are visible
in the routing domain. For a single NE-area setup, the addresses can be kept
contained inside that area.
– Static routes via direct in-band IPCCs take precedence over static routes via OOB
IPCCs, which in turn take precedence over routes learned via OSPF.
– If there are no direct IPCCs between neighbors, all signaling is freely routed.
As a result, the general recommendation to connect (almost) all NEs to the OOB
DCN can be relaxed. by using signaling messages that are freely routed through
the in-band DCN, stranded resources can be released, even if all direct in-band
IPCCs between neighbors fail.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
However, it is still recommended to configure a fair amount of GNEs (both
switching and photonic), in order to keep management traffic in the OOB DCN as
much as possible, and to allow OOB signaling, where in-band GCC resources do
not provide a proper level of resiliency.
• It is ensured by system design that links, for which the directly associated in-band or
OOB IPCCs are not operational, cannot be used as part of pre-computed backup
paths. This is to avoid the restoration anomaly as shown in “” (p. xv).
That means that at least one operational in-band or OOB IPCC is required,
independent from the fact that signaling traffic can be freely routed. This would
automatically include all FA-UNTERM links without an enabled GCC. Therefore, the
demand for at least one operational in-band or OOB IPCC does not apply for
FA-UNTERM links.
• To minimize the risk of the restoration anomaly as shown in “” (p. xv), it is
recommended to apply a modified scheme of OSPF metrics, which prefers small
hop-counts over high bandwidth. In this scheme, any two-IPCC-hop path is
considered less preferable than any single-hop path. The following table shows the
OSPF metrics for an MRN control plane while also considering the other
recommendations made in this section.
Table 2-4 OSPF metrics for an MRN control plane
Type of link OSPF metric

LAN link inside the OOB DCN 1
OSC 10
OAMP LAN link (of a dual-compound RNE node) 11
In this case, the LAN link is in the role of a direct link between two
control plane nodes.
OTU4/ODU4 GCC 12
OTU3e2/ODU3e2 GCC 13
OTU3/ODU3 GCC 14
OTU2e/ODU2e GCC 16
OTU2/ODU2 GCC 17
IP-in-IP tunnel 18
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
Table 2-4 OSPF metrics for an MRN control plane (continued)
Type of link OSPF metric

OAMP LAN link (of a dual-compound GNE node) 19
This is the case, where a switching compound, a photonic
compound, and a gateway router are on the same OAMP LAN.
As a link between an NE and a gateway router, the metric value
needs to be high enough to prevent management traffic from
entering the in-band DCN at an inappropriate position, and to
prevent OOB tunnels from going via the in-band DCN.
As a link between both compounds of the NE, the metric value
needs to be low enough to prevent inter-compound traffic from
going via in-band channels and other nodes.
OAMP LAN link (of a single compound GNE node) 28
This case is only relevant in the OSPF peering model. This link only
carries management traffic and OOB tunnel traffic. Setting the
metric too high would encourage that traffic to take non-optimal
detours via dual-compound GNEs and the in-band DCN.
Note: The values for OTUk/ODUk GCCs and IP-in-IP tunnels as listed in Table 2-4,
“OSPF metrics for an MRN control plane” (p. 2-33) are set up automatically by the
GMRE, the metrics for the remaining types of links need to be set manually.
The following sections provide information regarding the impact of the OSPF peering or
non-peering setup as described in the sections “OSPF peering model (MRN)”
(p. 2-27)and “OSPF non-peering model (MRN)” (p. 2-28).
OSPF peering model (MRN)
The OSPF peering model should be the preferred setup, as it is supported by switching
and photonic NEs in a common manner.
Except for the OSPF metrics, the discussion of section “” (p. xv) remains valid for the
MRN case.
A setup with a limited number of ABRs in the OOB DCN and resilient intra-area OOB
routing between ABRs and GNEs should be preferred.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
An example network is shown in the following figure:
Figure 2-16 Example MRN DCN setup with OSPF peering
Gateway Out-of-band DCN Gateway

Router G Router B
l
OOB IP-in-IP tunne
Gateway
Router A/E
LAN
LAN OAMP
LAN Switching
GNE E
UL
GCC1
over FA-UNTERM
OAMP OAMP GCC1

over FA-UNTERM
Switching Photonic
GNE G GNE A
OSC OSC
In-band DCN OAMP

GCC0
Photonic Photonic
RNE D GNE B
OAMP
Switching
RNE F
UL
OSPF interface NE area OSC OSC
(active)
OAMP
OSPF interface NE area or
backbone area (active) Photonic
RNE C
Static route to neighbor
gmreNode
Static default route
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
OSPF non-peering model (MRN)
Apart from / in contrast to the statements made in the sections “OSPF non-peering model
(MRN)” (p. 2-28) and “” (p. xv), the following has to be considered for the options of the
non-peering model:
• Option 1: Configure all NEs as GNEs
– Gateway routers have to tolerate OSPF running on the OAMP LAN of
dual-compound GNEs, as OSPF needs to be running in the in-band DCN and
between the compounds for proper signaling interaction.
– An example network is shown in Figure 2-17, “Example MRN DCN with an
OSPF non-peering setup (option 1)” (p. 2-37).
• Option 2: Follow the non-peering model of the switching nodes
– Metrics on tunnels between GNE and NOC should be much higher than those for
GNE-GNE tunnels.
– In case of lack of photonic in-band DCN resources, switching in-band resources
or GNE-GNE OOB tunnels are used as backup. This enhances signaling
resiliency, but puts a burden on switching FLCs and GCC bandwidth usage. (In a
peering model, rerouting via the OOB DCN would occur without involving
switching nodes.)
– An example network is shown in Figure 2-18, “Example MRN DCN with an
OSPF non-peering setup (option 2)” (p. 2-38).
• Option 3: Follow the non-peering model of the photonic nodes
– This option should not be used, because OOB IPCCs are not available to
switching nodes.
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
• Option 4: Set up a complete OSPF domain comprising the NEs and a small part of
the OOB DCN (quasi-peering setup)
– This setup shares most properties with the peering setup, it should be used, if no
end-to-end peering setup is feasible.
– The example setup follows the principle shown in Figure 2-16, “Example MRN
DCN setup with OSPF peering” (p. 2-35).
Figure 2-17 Example MRN DCN with an OSPF non-peering setup (option 1)
Gateway Out-of-band DCN Gateway

Router D/G Router B
l
OOB IP-in-IP tunne
Gateway Gateway
-IP
Router C/F -in Router A/E
IP
B
OOnnel
tu LAN
LAN LAN LAN OAMP
LAN Switching
GNE E
UL
GCC1
over FA-UNTERM
OAMP OAMP GCC1
over FA-UNTERM
Switching Photonic
GNE G GNE A
OSC
OSC
OAMP OAMP
In-band DCN
GCC0
Photonic Photonic
GNE D GNE B
OAMP
Switching
GNE F
UL
(active)
OAMP
gmreNode Photonic
GNE C
Static redistributed route
to photonic NE System
address
....................................................................................................................................................................................................................................
Issue 1 April 2014
MCN and SCN aspects
....................................................................................................................................................................................................................................
Figure 2-18 Example MRN DCN with an OSPF non-peering setup (option 2)
Gateway Out-of-band DCN

Router G s)
O C(
lt oN
l ne
OOB IP-in-IP tunne Tu
n
Gateway
Router A/E
Tunnel to NOC(s)
LAN
LAN OAMP
Switching
GNE E
UL
GCC1
over FA-UNTERM
OAMP GCC1
OAMP over FA-UNTERM
Switching Photonic
GNE G RNE A
OSC OSC
In-band DCN
GCC0
Photonic Photonic
RNE D RNE B
OAMP
Switching
RNE F
UL
(active)
OAMP
OSPF interface NE area
(passive) Photonic
RNE C
gmreNode
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN planning The Alcatel-Lucent 1830 PSS management network
....................................................................................................................................................................................................................................
The Alcatel-Lucent 1830 PSS management network

Introduction
In a WDM network, management information and control from the Operations System
(OS) is carried from one NE to the other over the internal Alcatel-Lucent 1830 PSS DCN
via the Optical Supervisory Channel (OSC), a GCC embedded in an optical signal, or a
LAN connection.
The following figure shows the high-level management overview:
Figure 2-19 Network management overview
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
The remotely managed device, as shown in Figure 2-19, “Network management
overview” (p. 2-39), can be an IP-managed device co-located with the Alcatel-Lucent
1830 PSS NE, a Raman amplifier for example, connected via the extension LAN.
IP addressing scheme (separate sub-network per node)

Figure 2-20, “IP addressing scheme (nodes have separate sub-networks)” (p. 2-40)shows
an example where each Alcatel-Lucent 1830 PSS NE belongs to a separate class C
sub-network. For example, the GNE, with Router ID 135.1.1.1/32, belongs to subnet
135.1.1.0/24, while NE2, with Router ID 135.1.2.1/32, belongs to subnet 135.1.2.0/24.
Figure 2-20 IP addressing scheme (nodes have separate sub-networks)
Each NE becomes essentially a router for its sub-network; in addition, each NE is a router
for multiple locally defined sub-networks, for instance OAMP, VoIP, and E1/E2-LAN.
Packets destined for an NE, or destined for devices connected to the NE, are routed over
one or more NEs prior to reaching the destination. Externally connected devices such as
VoIP phones and units connected to the E1/E2-LAN ports will need to be advertised
throughout the network. Therefore, each NE's routing table can potentially become very
large, based on the number of NEs and devices that are supported.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
In the example in Figure 2-20, “IP addressing scheme (nodes have separate
sub-networks)” (p. 2-40), there are eight (8) separate NE sub-networks, not including the
VoIP and externally managed devices. The management router(s), which are located in
the IP network that provides the connection to the management system, must be aware of
all of these routing entries, either via static entries, or dynamically discovered via OSPF.
IP addressing scheme (common sub-network)

The software allows the Alcatel-Lucent 1830 PSS NEs to share a common sub-network.
Doing so will reduce the number of routing entries that the management router(s) must
keep, thereby providing a simpler design especially if these management routers employ
static routing entries. As such, the following IP addressing scheme will be supported.
Figure 2-21 IP addressing scheme (nodes sharing a common sub-network)
In this example, all Alcatel-Lucent 1830 PSS NEs share the same subnet 135.1.1.0/24.
This makes it easier for the management network to communicate to the NE. In other
words, only one routing entry needs to be statically added to the management router
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
(135.1.1.0/24) in order to access every 1830 PSS network element. TCP/IP support is
required over the LAN interface(s) and all Embedded Communication Channels (ECC),
e.g. OSC and GCC0.
Basic network topologies

Introduction
The Alcatel-Lucent 1830 PSS is not standalone equipment; it is part of WDM
sub-networks. The communications, internal and external, are IP based. It has to be
managed through an IP network.
An Alcatel-Lucent 1830 PSS network includes mainly three kinds of equipments.
Basically the same boards and shelves but with different functions:
• Line terminal
• Fixed, Reconfigurable, or Tunable Optical Add-Drop Multiplexers (FOADM,
ROADM, TOADM)
• ILA (In Line Amplifier)
Each Alcatel-Lucent 1830 PSS NE can be configured as a Gateway Network Element
(GNE) to provide an access from the DCN to all the NEs on the optical network.
Generally the following three topologies can be distinguished:
• Linear architecture
• Ring architecture
• Meshed architecture
Linear architecture
At least the two NEs terminating the line must be configured as GNEs, providing
redundancy for management access to the other intermediate NEs, in case of a network
fault.
Figure 2-22 Linear architecture
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN planning Basic network topologies
....................................................................................................................................................................................................................................
Ring architecture
The Alcatel-Lucent 1830 PSS network element (NE) is not standalone equipment; it is
one part of a larger WDM transport network. The management and control
communications, internal and external, are supported over an IP based network that
connects the various NEs.
Figure 2-23 Ring architecture
Meshed architecture
Carefully choose more than one GNE to prevent a network fault from disconnecting one
or more NEs from the management system.
In the example depicted in following figure, all WDM network elements remain reachable
by the management system despite the failure of any single optical link.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN planning Basic network topologies
....................................................................................................................................................................................................................................
Figure 2-24 Meshed architecture
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN planning Network IP architecture
Address planning
....................................................................................................................................................................................................................................
Address planning
Network IP architecture
Overview
In the following figure the IP architecture is illustrated on a meshed network but applies
to all the topologies.
Figure 2-25 IP architecture overview
Workstation EMS
@PhM @OMS
1830 EMS
Customer Management Backbone Subnet
@W1
@OAMP_8
Workstation
@OAMP_1 @OAMP_6
@SYSTEM_3 @SYSTEM_8
@SYSTEM_1 @SYSTEM_2 @SYSTEM_9
@SYSTEM_4
DCN
@SYSTEM_5 @SYSTEM_7 Customer
@VoIP_2 @SYSTEM_6 @E1 addresses
OSPF area
TOADM
ILA TOADM ILA
1830PSS GNE
Internal
addresses
1830PSS GNE
ZIC 172.16.1.0/24
IP phone SNMP external device
Local dhcp connection
Local dhcp connection Local dhcp connection
(1 per 1830)
(1 per 1830) (2 per 1830)
@GMRE_3 @GMRE_8
@GMRE_1 @GMRE_4 @GMRE_9
@GMRE_2@GMRE_5 @GMRE_7 Per @GMRE_#:

@GMRE_6 @GMRENODE
Control OSPF area @GMRENOTIFY
....................................................................................................................................................................................................................................
Issue 1 April 2014
Address planning
....................................................................................................................................................................................................................................
DCN customer addresses
DCN customer addresses include the IP addresses assigned to the following interfaces:
• OAMP LAN connector on the User Panel of the main shelf.
• CIT LAN connector on one of the Equipment Controllers (EC) in the main shelf.
• VOIP LAN connector on the User Panel of the main shelf.
• E1 LAN connector on the User Panel of the main shelf.
• E2 LAN connector on the User Panel of the main shelf.
These customer addresses are used for the network management.
Good practice dictates that each Alcatel-Lucent 1830 PSS NE must be reachable from the
management network through a Gateway NE (GNE) even in case of a single failure of an
OSC/GCC link.
In order to help summarization, routing and filtering at the border of a WDM
sub-network, IP addresses shall be assigned depending on the nature and usage of the
interface. For that purpose, several types of networks shall be identified; a dedicated
range of addresses shall be reserved for each sub-network.
Types of networks
These types of networks can be distinguished:
• MGMT network for management loopback addresses (SYSTEM): Each
Alcatel-Lucent 1830 PSS is assigned a management IP address. Typically, this address
is advertized outside the WDM sub-network in order to reach management systems.
• CP network for control plane loopback addresses (GMRENODE &
GMRENOTIFY): when GMPLS is used in a WDM sub-network, each
Alcatel-Lucent 1830 PSS is assigned 2 IP addresses for GMRE.
• VOIP network for VoIP addresses: used for IP phone access. Each Alcatel-Lucent
1830 PSS can be assigned a VOIP /30 subnet (→ 1 IP address for VOIP LAN
interface + 1 IP address for IP phone) in order to connect an IP phone to the
Alcatel-Lucent 1830 PSS. This network which is the summarization of all VOIP
subnets can be advertized or not outside the WDM sub-network depending on
whether the Phone network goes on beyond the WDM sub-network or not.
• EXTD network for External Devices addresses (E1 & E2). When connecting an
external device to E1 or E2 LAN port, the NE can be assigned a /30 subnet (→ 1 IP
address for the LAN interface + 1 IP address for the external device). Typically, this
network is advertized outside the WDM sub-network in order to reach management
systems.
• INT network for addresses needed in order to reach interfaces which are involved in
routing process. This network is useful within an Area and is not advertized outside
the WDM sub-network.
....................................................................................................................................................................................................................................
Issue 1 April 2014
Address planning
....................................................................................................................................................................................................................................
• OAMP addresses – several cases are possible (typically the OAMP address is
different from the SYSTEM address):
– In case of direct link between OAMP and external router, a /30 subnet within the
‘INT network’ range can be used;
– In case there are also other devices on the same LAN, it could be useful to take
several contiguous /30 (we need in that case at least a /29) within the EXTD
network;
– Otherwise, the need is to assign a free IP address to OAMP port within an already
existing sub-network.
Note: The OAMP LAN interface is a numbered interface which is used for connecting
the NE to the DCN for central management. As a numbered interface, it requires a
unique IP address. The SYSTEM address, however, is shared as interface address by
all unnumbered network interfaces. Hence, the OAMP IP address and the SYSTEM
address cannot be the same.
Organization of the networks

Organization of the networks which belong to the Area corresponding to a WDM
sub-network:
Table 2-5 Organization of the networks
Name Function Subnet address Organization of the Network (based on a /24 network)
Number of First address Last address

groups
MGMT Management network, x.x.x.0 (given 256 MGMT0=x.x.x.0/32 MGMT255=x.x.x.255/32

loopback addresses for by customer)
management
CP GMPLS control plane x.x.x.0 (given 128 CP0=x.x.x.0/30 CP127=x.x.x.252/30
(2 addresses per GMRE by customer)
node)
VoIP IP phone x.x.x.0 (given 64 VOIP0=x.x.x.0/30 VOIP63=x.x.x.252/30
by customer)
EXTD External Devices addresses x.x.x.0 (given 64 EXTD0=x.x.x.0/30 EXTD63=x.x.x.252/30
by customer)
INT LAN interfaces which are x.x.x.0 (given 64 INT0=x.x.x.0/30 INT63=x.x.x.252/30

advertised by OSPF but are by customer)
internal in the Area. INT
range does not need to be
advertised outside the Area.
OAMP External DCN access. Customer At least 2 - -

(Recommended to defined (1 per
configure as a point to point GNE)
network between the GNE
and its front router)
....................................................................................................................................................................................................................................
Issue 1 April 2014
Address planning
....................................................................................................................................................................................................................................
Rules and guidelines
Observe the following guidelines for the organization of networks within a WDM
sub-network:
• The MGMT network addresses range shall be provided by the customer for the
assignment of NE management addresses.
• The CP network addresses range shall be provided by the customer for the assignment
of Control Plane addresses if GMPLS is enabled in the WDM sub-network.
• The VoIP network addresses range shall be provided by the customer for the
assignment of VoIP addresses if Voice over IP solution is used in the WDM
sub-network.
• The EXTD network addresses range shall be provided by the customer for the
assignment of External Devices addresses if needed.
• The INT network addresses range shall be provided by the customer for enabling
LAN interfaces involved in routing process within an Area but invisible to the
management system.
The size of each network depends on the WDM sub-network size. Typically each range of
addresses corresponds to a /24 subnet.
Note: The following subnets are reserved for internal addresses, and cannot be used:
• 100.0.0.0/16
• 172.16.0.1/24
DCN IP networks summary of an 1830 PSS
Name Function Subnet Mask Initial commissioning Interface

address
Factory Manually OSPF
default updated
or
acknowl-
edged
SYSTEM Loopback address for MGMT /32 None Yes PAS- Loopback0
(Router ID) management SIVE
OAMP External DCN access. Customer At least None Yes EN- OAMP on the
(Recommended to defined /30 ABLE if User Panel
configure as a point to GNE (PSS-16/32)
point network between
the GNE and its front
router)
CIT ZIC/Local craft Default or INT /30 172.16.0.1 Yes No CIT port on EC
terminal or EXTD
VoIP IP phone access VOIP /30 0.0.0.0/0 Yes PAS- VoIP on USRPNL
SIVE if
used
....................................................................................................................................................................................................................................
Issue 1 April 2014
Address planning
....................................................................................................................................................................................................................................
Name Function Subnet Mask Initial commissioning Interface

address
Factory Manually OSPF
default updated
or
acknowl-
edged
E1-LAN, Connection with 135.50.10.1 /30 0.0.0.0/0 Yes PAS- E1-LAN, E2-LAN
E2-LAN externally managed SIVE if on the User Panel
device used (PSS-16/32)
GMRE node GMPLS control plane see “Example /32 None Yes PAS- Loopback1
(CP node) loopback address for GMRE SIVE
node
addresses”
(p. 4-2)
GMRE notify Additional GMPLS see “Example /32 None Yes PAS- Loopback2
(CP notify) control plane loopback for GMRE SIVE
address node
addresses”
(p. 4-2)
Notes:
Several possibilities for CIT port:
• If only local NE managed, keep the default address (default mask is /24).
• If purpose is to reach other NEs within the WDM sub-network, assign a /30 subnet
within the INT range.
• If purpose is to reach any NE outside the WDM sub-network, assign a /30 subnet
within the EXTD range.
The SYSTEM address is the only IP address which must always be set on an
Alcatel-Lucent 1830 PSS system.
The SYSTEM address is the NE's loopback IP address, which is shared as interface
address by all unnumbered network interfaces and which will also be used as the OSPF
Router ID.
Default settings
Table 2-6 Default behavior of DCN-related interfaces
Interface Default settings

CIT LAN interface Enabled by default on the active Controller in the main shelf.
Disabled by default on the standby Controller in the main shelf,
and on extension shelves.
Default network address:172.16.0.1/24
....................................................................................................................................................................................................................................
Issue 1 April 2014
Address planning
....................................................................................................................................................................................................................................
Table 2-6 Default behavior of DCN-related interfaces (continued)
Interface Default settings

OAMP LAN interface Enabled in the main shelf, disabled in extension shelves
OSPF is disabled
E1/E2 LAN interfaces Enabled in the main shelf, disabled in extension shelves
OSPF is disabled
VOIP LAN interface Enabled in the main shelf, disabled in extension shelves
OSPF is disabled
OSC/GCC interfaces OSPF is enabled (and cannot be modified)
Default MTU size is 1491 bytes for OSC interfaces, and 1473
bytes for GCC interfaces
Controller: EC card for PSS-16/PSS-32
Note: On standby cards, the LAN interface ports are disabled in order to prevent
loops from forming and to prevent any external LAN switches from learning the same
MAC address on multiple ports.
OSPF mode
OSPF is enabled individually on each interface:
• For GCC and OSC interfaces, OSPF is always enabled in active mode.
• OSPF is always enabled in passive mode on SYSTEM management loopback address
• OSPF is automatically enabled in passive mode on GMRE loopback addresses when
the GMRE is used; otherwise it is disabled.
• OSPF on customer LAN interfaces:
– OSPF is disabled by default for the OAMP, VOIP, E1, and E2 ports.
– OSPF is typically enabled on the OAMP interface if the NE is a GNE.
– OSPF is typically disabled on the CIT port because the CIT port is not assigned a
routable address.
– OSPF is typically enabled in passive mode on the VOIP interface if an IP phone is
connected.
– OSPF is typically enabled in passive mode on E1 and E2 interfaces if an external
device is connected.
• OSPF is disabled within the Internal LAN (ES1/ES2).
....................................................................................................................................................................................................................................
Issue 1 April 2014
Address planning
....................................................................................................................................................................................................................................
OSPF advertisement:
• When OSPF is enabled in active mode on an interface, then OSPF messages are
exchanged via this interface, and OSPF advertises the loopback addresses, the serial
interfaces, and the directly connected sub-networks on all other OSPF enabled
interfaces.
• When OSPF is enabled in passive mode on an interface, no OSPF message is sent on
this interface but OSPF advertises this interface subnet on all other OSPF enabled
interfaces.
OSPF mode configuration:
• To disable OSPF on an interface, set the OSPF status to disable.
• To enable OSPF in active mode on an interface, set the OSPF status to enable.
• To enable OSPF in passive mode on an interface, set the OSPF status to redistribute.
In a network design where OSPF is enabled on the GNE OAMP/VOIP/E1/E2
management ports or where static routes are configured such that an alternate path for the
Alcatel-Lucent 1830 PSS NEs is available via the customer DCN in addition to inter-NE
paths via OSC/NETIF interfaces, the following should be adhered to:
• At the GNE NEs the Loopback IP should be provisioned with the snmp_src option
such that all SNMP requests to the NE must use ONLY the Loopback IP of the NE
(the OAMP/VOIP/E1/E2 IP address will not be valid for SNMP requests). Likewise,
any SNMP traps from the NE will contain the Loopback IP as the source IP address.
• When OSPF is enabled at the OAMP/VOIP/E1/E2 port the OSPF metric should be
provisioned to be greater than the largest inter-NE path cost. This will allow for
NE-NE application data messages to prefer inter-NE path over customer DCN paths.
• When static routes are configured at the GNE in order to provide an alternate path for
the Alcatel-Lucent 1830 PSS NE-NE communication via the customer DCN in
addition to inter-NE paths via OSC/NETIF interfaces – the distance value provisioned
for each static route should be greater than 110. This will allow for NE-NE
application data messages to prefer inter-NE paths over customer DCN paths.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN planning Overview
....................................................................................................................................................................................................................................
Summary of important rules and guidelines
Table 2-7 Engineering rules and guidelines
Topics Rules and guidelines
Connectivity A node belongs to an OSPF area if at least one of its interfaces is enabled in this area.
Each Alcatel-Lucent 1830 PSS NE must have links to at least two different neighbors.
Links can be OSC, GCC0 or Ethernet; neighbors can be an Alcatel-Lucent 1830 PSS NE
or an IP router.
WDM sub-network and OSPF area Due to wavelength key distribution constraints, all nodes of a WDM sub-network must
belong to the same OSPF area..
Typically, a DCN OSPF area is assigned per WDM sub-network.
It is possible to set several WDM sub-networks in the same OSPF area if this is still
compatible with the maximum number of NEs.
Number of NEs per OSPF area In the DCN network, the maximum number of nodes per area is 500.
Number of GNEs The recommendation is to have at least two GNEs per OSPF area.
Additional rules (fair load sharing of outgoing traffic between GNEs):
• GNEs are defined in such a way that any RNE is at a reasonable distance from the
closest GNE.An equal distribution of RNEs to GNEs is desirable as far as the
distance of RNEs to their nearest GNE is concerned.
• Typically, 2 GNEs are required for areas of up-to 100 NEs + 1 GNE per additional
group of 100 NEs in the OSPF area.
OAMP on GNE An Alcatel-Lucent 1830 PSS plays the GNE role when it provides an access to the
external DCN.
Typically, the following applies:
• This access is performed via the OAMP interface towards an external router.
• OSPF is enabled on the OAMP interface, and the OAMP interface is in the same
OSPF area as other interfaces.
• OAMP access is secured by other GNEs, and there is no need to be locally resilient
to OAMP failure.
Nevertheless, it is not forbidden to use another LAN interface (for example E1 or E2)
in order to locally secure the OAMP link.
Number of GMPLS NEs in a WDM If GMPLS is enabled in a WDM sub-network, the maximum number of Alcatel-Lucent
sub-network 1830 PSS NEs which run GMPLS is 400.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN planning Summary of important rules and guidelines
....................................................................................................................................................................................................................................
Table 2-7 Engineering rules and guidelines (continued)
External routers Front routers for the Alcatel-Lucent 1830 PSS DCN must provide routes to join the
management systems (Alcatel-Lucent 1350 OMS) and the other Alcatel-Lucent 1830 PSS
NEs through the DCN.
The following rules apply to front routers:
• There must be one router per GNE.
• Dynamic routing is recommended (see also “Routes management for front router”).
• Redundancy is not required on each GNE, the route(s) to other GNE(s) provide(s)
the redundancy (see also “Number of GNEs”).
• The router needs one physical interface connected to the Alcatel-Lucent 1830 PSS
NE (10/100 Mb/s).
• The OAMP port is used to connect to external routers; see Table 2-3, “DCN-related
external interfaces (USRPNL)” (p. 2-5).
• The IP address of the external router port connected to the Alcatel-Lucent 1830 PSS
NE must be in the OAMP subnet.
Route management for front router Dynamic routing configuration:
• The routing protocol is OSPF; it must be activated at the interface with the GNE.
• The interface to the GNE must be set in the same area than the 1830 OAMP
interface.
• The configuration of the interface to the backbone depends on the customer DCN
(for example, routing protocol is customer specific). It is the responsibility of the
network design team to adapt the external interface to particular needs of the
customer DCN.
• Summarization: Routes summarization has to be activated at the border of the area.
Only a subset of the addresses shall be summarized (see “Types of networks”
(p. 2-46)).
• Routes to advertise to the GNE: We recommend to use a totally stubby area so only a
default route is advertised to the GNE.
If a normal area must be used (not recommended), the management subnet must be
advertised. This avoids routes recalculation if the Alcatel-Lucent 1350 OMS has to
move inside the management subnet.
Optional features of the front router:
• Depending on other capabilities of the router, the following features are useful:
– Access lists - They can restrict the access to the Alcatel-Lucent 1350 OMS
(the active one and the standby one) inside the management subnet
– IP port filtering
– QoS marking
– IPsec tunneling - Mandatory if IP flow has to cross an unsecure network
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
Table 2-7 Engineering rules and guidelines (continued)
Intra-area path redundancy between front A direct path has to be set between each front router inside a DCN area, if the path
routers redundancy is not ensured by a fully meshed architecture of the WDM network (through
the OSC/GCC0).
Due to hosts (Alcatel-Lucent 1830 PSS) routes summarization inside the front routers, this
path must be an intra-area path, it can be any kind of direct link or a tunnel via the
backbone.
This path will ensure the defense of routing in case of OSC/GCC0 failure in a linear
network for instance.
IP access control lists (ACL) The following limitations apply:

• Maximum 100 empty filters can be created
• Maximum 256 patterns can be created
• The filter mapping table has maximum 4000 filter mapping entries (mapped with
patterns)
• Internal packets (packets in EC/FLC, packets between EC/FLC and local line cards,
packets between active and standby EC/FLC) shall never be dropped.
Table 2-8 Required buffering and table sizes
Maximum value Comment
Number of NETIF instances per NE 128

Number of NETIF instances per shelf 64
Number of OSC instances 20
Number of simultaneous file transfers over At least 1 One file transfer operation on a NETIF
NETIF connection carrying OTU1/ODU1 rate
traffic.
2 or more on higher rate NETIFs.
Number of simultaneous file transfers over 2 or more

OSC
Recommended guaranteed Customer DCN 10 Mbps or greater

Bandwidth from EMS to GNE
RNEs managed from one GNE via OSC 32

RNEs managed from one GNE via NETIF 8
of OTU2 rate or higher
RNEs managed from one GNE via NETIF 4

of OTU1 rate
Size of TID-IP MAP per GNE 500
Active users 32 Combinations of TL1, WEB, CLI, and

SNMP users.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
Table 2-8 Required buffering and table sizes (continued)
Maximum value Comment
Active CLI sessions 10
Active WebUI sessions 20 Without any performance degradation.

Active TL1 sessions 40
Number of degrees supported by one NE 148 128 NETIF + 20 OSC

Number of NEs in one OSPF area 500 Default OSPF area is area 0.
Number of OSPF areas supported on the 4 0, 1, 2, 3

NE
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 1 April 2014
3 DCN configuration
3
Overview
Purpose
This section provides instructions explaining how to setup DCN for Alcatel-Lucent
1830 PSS.
Contents
Physical configuration 3-3

Procedure 3-1: Configure physical properties of interfaces 3-3
IP network configuration 3-5
DCN configuration overview 3-5
Procedure 3-2: Configure IP addresses and TCP/IP parameters 3-5
Procedure 3-3: Configure OSPF parameters 3-7
Procedure 3-4: Create an OSPF area 3-11
Procedure 3-5: Create static routes 3-13
Time management 3-14
Network Time Protocol (NTP) 3-14
Security 3-15
NE firewall with provisionable IP access control lists (IP ACL) 3-15
RADIUS for user authentication 3-17
Secure/unsecure mode 3-18
Firewall configuration 3-21
IPSec tunnel 3-22
Syslog server 3-24
Advice on security hardening on the Alcatel-Lucent 1830 PSS 3-24
...................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Overview
....................................................................................................................................................................................................................................
Software Server NE (SWNE) 3-26

SWNE functionality 3-26
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Configure physical properties of interfaces
....................................................................................................................................................................................................................................
Procedure 3-1: Configure physical properties of interfaces

Purpose
Use this procedure to configure physical properties of customer LAN ports or OSC/GCC
network interfaces that have an influence on data transmission.
Physical properties include:
• Duplex mode and transport capacity (link speed) of customer LAN ports
• MTU size for OSC/GCC network interfaces
Steps
...................................................................................................................................................................................................
1 For the customer LAN ports, set the duplex mode to one of the following values:
• Full duplex - Chose this setting to use full duplex mode on the LAN port.
• Half duplex - Chose this setting to use half duplex mode on the LAN port.
• Autonegotiated (System Default) - Chose this setting if you want the duplex mode to
be autonegotiated between the LAN port and its link partner.
The default value is the previously existing value or the system default AUTO.
...................................................................................................................................................................................................
2 For the customer LAN ports, set the transport capacity (link speed) to one of the
following values:
• 10 Mb/s
• 100 Mb/s
• 1000 Mb/s
• Autonegotiated (System Default) - Chose this setting if you want the link speed to be
autonegotiated between the LAN port and its link partner.
The default setting is the previously existing value or the system default.
...................................................................................................................................................................................................
3 Configure the MTU size for the OSC/GCC network interfaces.

The MTU (maximum transmission unit) defines the maximum size (in bytes) that a
protocol data unit (PDU) can have to be sent or received via the interface. The greater the
MTU the lower is the probability for fragmentation of data, and the more efficient is the
data transmission.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Procedure 3-1: Configure physical properties of interfaces
....................................................................................................................................................................................................................................
Possible values range from 576 to 1500 bytes.
The default MTU size is 1491 bytes for OSC interfaces, and 1473 bytes for GCC
interfaces.
Note: When a virtual link is created across an OSC or GCC path, be sure to set the
MTU size to 1500 bytes for the OSC/GCC interfaces on that path. Be aware that no
automatic checking is done by the NE regarding this MTU size setting.
Important! The MTU size must be consistently configured at both ends of an
OSC/GCC link.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration DCN configuration overview
....................................................................................................................................................................................................................................
DCN configuration overview

Overview
1 Use a LAN cable to directly connect a local management system to the CIT interface
and configure IP addresses and TCP/IP stack parameters for NE interfaces (LAN
interfaces (OAMP, VOIP, E1/E2, ES1/ES2), SYSTEM, GMRENODE, GMRENOTIFY)
- based on IP address and subnet planning.
Local management systems can be the 1830 Command Line Interface (CLI), the TL1
command line interface (TL1), or the web-based user interface (WebUI), for example.
Part of this configuration step is typically done during initial commisioning.
2 Create OSPF areas.
3 Define static routes (if needed)
4 Configure OSPF
5 Enable OSPF per interface
6 Enable ECCs (OSC/GCC0)
OSC or GCC0, once enabled, will be used for management traffic. OSPF will be enabled
automatically and cannot be disabled.
Procedure 3-2: Configure IP addresses and TCP/IP parameters

Purpose
Use this procedure to configure IP addresses and TCP/IP parameters for the system (Host
ID), for customer LAN ports (OAMP, VoIP, E1, E2, and CIT), or for the control plane
node (control plane node address, control plane notify address).
The following IP addresses are typically assigned during the initial commissioning:
• OAMP:
One interface address with the backbone. The front router will have an interface in the
same subnet. Could be routed or not. At least /30 subnet.
• SYSTEM:
Loopback IP address of the NE. It is the management address of the NE. Must be
routed toward the backbone.
• GMRENODE :
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Procedure 3-2: Configure IP addresses and TCP/IP
IP network configuration parameters
....................................................................................................................................................................................................................................
Loopback address assigned to the GMRE node interface. It is the main control plane
address of the GMRE, it must be routed toward the backbone for redundancy.
• GMRENOTIFY :
Loopback address assigned to the GMRE notify interface. It is a secondary control
plane address of the GMRE, it must be routed toward the backbone for redundancy.
SYSTEM address
The SYSTEM address must be set prior to connection into the NE via remote methods.
Until it is set, only local access will be allowed. Once the SYSTEM address is set, remote
TL1, CLI, WebUI, or SNMP commands may be sent to the NE using the provisioned IP
interface.
The TCP/UDP port numbers used to access the NE are the following:
Table 3-1 TCP/UDP ports used to access the NE
Port Protocol Usage

number
20 TCP FTP-Data - File Transfer Protocol [Data]
21 TCP FTP - File Transfer Protocol [Control]
23 TCP Telnet
69 UDP TFTP - Trivial File Transfer Protocol
123 UDP NTP - Network Time Protocol
161 UDP Simple network Management Protocol (SNMP)
162 UDP Simple network Management Protocol (SNMPTRAP)
3082 TCP TL1 raw encoding unsecure mode
3083 TCP TL1 telnet encoding unsecure mode
Steps
Important!
• Note, that the IP address range 100.0.0.0/8 is not allowed to be configured as an
external IP address. This address range is used for internal purposes of the NE.
Therefore, the NE cannot communicate with any external partner, which uses an
address from this range.
• Also note, that the IP address range 101.0.0.0/8 is allowed, yet discouraged to be
used as an external IP address. Other Alcatel-Lucent NEs use this address range
for internal purposes, and hence forbid its usage for external addresses. Therefore,
if configured for the 101.0.0.0/8 address range, the NE cannot communicate with
those NEs.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Procedure 3-2: Configure IP addresses and TCP/IP
IP network configuration parameters
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 If not yet done during the initial commissioning phase, set the SYSTEM address.
This is the loopback IP address of the NE, which is shared as interface address by all
unnumbered network interfaces, and which is also used as the OSPF router Id.
...................................................................................................................................................................................................
2 At the GNE, provision the loopback IP address of the NE with the “SNMP source” option
such that all SNMP requests to the NE must use the loopback IP address of the NE only
(the OAMP IP address will not be valid for SNMP requests).
...................................................................................................................................................................................................
3 If not yet done during the initial commissioning phase, set the IP addresses on the
customer LAN ports (OAMP, VoIP, E1, E2, and CIT).
...................................................................................................................................................................................................
4 Specify the subnet masks for the customer LANs (OAMP, VoIP, E1, E2, and CIT).
...................................................................................................................................................................................................
5 Specify whether customer LAN ports (OAMP, VoIP, E1, E2, and CIT) shall support the
Proxy ARP function.
A customer LAN port that supports the Proxy ARP function replies back to ARP
requests from the remote server for all RNEs within the internal network, using its
own MAC address for the response.
...................................................................................................................................................................................................
6 When a customer LAN port (OAMP, VoIP, E1, E2, and CIT) supports the DHCP Server
function, then define the range of the IP pool for the DHCP server, and specify whether
the IP address of the customer LAN port is to be distributed as the Default Gateway via
DHCP.
E...................................................................................................................................................................................................
N D O F S T E P S
Procedure 3-3: Configure OSPF parameters

Purpose
Use this procedure to configure the global OSPF parameters as well as the parameters
associated with OSPF on the OSPF-enabled interfaces.
OSPF is enabled by interface:
• For GCC and OSC interfaces, OSPF is enabled by default and cannot be modified.
• OSPF is always enabled in passive mode on SYSTEM management loopback address.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Procedure 3-3: Configure OSPF parameters
....................................................................................................................................................................................................................................
• OSPF is enabled in passive mode on GMRE loopback addresses if the GMRE is used.
• OSPF on customer LAN interfaces:
– OSPF is disabled by default for the OAMP, VOIP, E1, and E2 ports.
– OSPF is typically enabled on the OAMP interface if the NE is a GNE.
– OSPF is typically disabled on the CIT port because the CIT port is not assigned a
routable address.
– OSPF is typically enabled in passive mode on the VOIP interface if an IP phone is
connected.
– OSPF is typically enabled in passive mode on E1 and E2 interfaces if an external
device is connected.
• OSPF is disabled within the Internal LAN (ES1/ES2).
Each one of these interfaces can be configured independently.
Note: The global OSPF parameters are typically set once in the lifetime of the NE
while the interface-specific parameters have to be set once per OSPF-enabled
interface.
Steps
...................................................................................................................................................................................................
1 Configure the global OSPF parameters.

The global OSPF parameters include:
• Static Route External Metric
Determines the cost metric value to be set in all AS-external LSAs (Type 5 LSAs),
which result from advertised static routes.
Possible values range from 0 to 16777214, factory default is 20.
• Static Route External Metric Type
Determines the metric type to be set in all AS-external LSAs (Type 5 LSAs), which
result from advertised static routes.
– INT Internal metric type (metric type 1): The metric value is assumed comparable
to intra-AS metric values.
– EXT External metric type (metric type 2): The metric value is assumed higher
than the path cost of any intra-AS path.
Factory default is EXT
• Default Route External Metric
Determines the cost metric value to be set in all AS-external LSAs (Type 5 LSAs),
which result from advertised default routes.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
• Default Route External Metric Type
Determines the metric type to be set in all AS-external LSAs (Type 5 LSAs), which
result from advertised default routes.
– INT Internal metric type (metric type 1): The metric value is assumed comparable
to intra-AS metric values.
– EXT External metric type (metric type 2): The metric value is assumed higher
than the path cost of any intra-AS path.
Factory default is EXT
...................................................................................................................................................................................................
2 Configure the parameters associated with OSPF on each OSPF enabled interface.
These OSPF parameters include:
• OSPF Hello interval timer (in seconds)
This is the time elapsed before the next Hello PDU is sent.
• OSPF Router Dead timer (in seconds)
This is the time elapsed between not hearing a router's Hello PDU before the
neighbors will declare it down. The router dead interval is a timer used to timeout
inactive adjacencies.
The value of the OSPF Router Dead timer is typically four times the value of the
OSPF Hello interval timer, and must always be greater than the OSPF Hello interval
timer.
• Metric or cost of the OSPF interface
This is the cost metric of the route.
The system default setting is 10, the lower the cost, the better. OSPF determines the
“shortest path” in the sense of a least-cost calculation. Typically, lower costs are
assigned to higher bandwidth links, and vice versa. Setting all routes to equal costs
automatically enables load balancing between the paths.
• Router priority
This parameter is used on the LAN to determine which router will become the
designated router (DR).
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
OSPF Hello interval and router dead timer: The OSPF Hello interval and router
dead timer are of particular importance because they relate to the OSPF Hello
protocol which is a central OSPF protocol, used for example to establish and maintain
neighbor relationships and thus to form OSPF adjacencies. When no adjacencies can
be formed, then no OSPF LSAs can be exchanged and OSPF routing is not possible.
The OSPF Hello interval and router dead timer determine the interval between two
Hello PDUs and the waiting time before declaring a neighbor down, when no Hello
PDUs are received. The OSPF router dead timer restarts each time an OSPF Hello
PDU is received. Thus, it takes at least the router dead interval to detect a neighbor
down condition.
The OSPF Hello interval and router dead timer directly influence to the OSPF
convergence time. Reducing the timer values can improve the convergence time.
However, decreasing the timer values on the other hand increases the risk of
premature or toggling neighbor down decisions.
Note: As a general rule, the default settings of the OSPF Hello interval and router
dead timer strike a balance between convergence time and reliability.
Observe the following rules and guidelines:
• When you change the OSPF Hello interval and router dead timer then be sure to
change these timers on all interconnected OSPF-enabled interfaces consistently.
Interconnected OSPF-enabled interfaces exchange Hello PDUs with each other, and
the timer values in these Hello PDUs must match.
• Do not set the OSPF Hello interval and router dead timer to the same value; set the
OSPF router dead timer to at least twice the value of the Hello interval timer.
• Always set the OSPF router dead timer to an integer multiple of the Hello interval
timer.
...................................................................................................................................................................................................
3 Administratively enable or disable an OSPF interface by setting the OSPF interface status
to one of the following values:
• Enable - The interface will participate in OSPF LSA exchanges.
• Disable - The interface does not run the OSPF protocol.
• Redistribute - The interface does not run the OSPF protocol, but it does advertise.
The initial default setting for the OAMP, E1, E2, and VOIP ports is Disable.
The CIT port only supports Disable and Redistribute.
The status of the GCC and OSC ports cannot be modified. The status is always set to
Enable for these ports.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Procedure 3-4: Create an OSPF area
....................................................................................................................................................................................................................................
Procedure 3-4: Create an OSPF area

Purpose
Use this procedure to create an OSPF area.
Steps
...................................................................................................................................................................................................
1 Specify the name of the OSPF area to be created, for example OSPFAREA-1.
If you do not explicitly specify a name, then the OSPF area will be assigned a name
automatically.
...................................................................................................................................................................................................
2 Define the OSPF area ID, for example 1.1.1.1 or 0.0.0.1.

The OSPF area ID has the format of an IP address, for example '0.0.0.0' for the backbone
area, or '1.1.1.1' or '0.0.0.1' for OSPF area 1. Note that area ID and area index are not
numerically coupled as shown in this example. The backbone area always has the area ID
'0.0.0.0'. For other areas, any 32-bit value except '0.0.0.0' is allowed.
...................................................................................................................................................................................................
3 Specify the type of OSPF area to be created.

The following types of OSPF areas are supported:
• NORMAL areas are defined as areas that can accept intra-area, inter-area and
external routes.
• STUB areas do not accept routes belonging to external autonomous systems (AS);
however, these areas have inter-area and intra-area routes. This reduces the size of the
routing databases for the area's internal routers. Routers in the stub area also contain a
default route which is advertised to the area by the Area Border Router (ABR).
• TOTALLY-STUB areas do not allow routes other than intra-area and the default
route to be propagated within the area. This further reduces the size of the routing
databases for the area's internal routers. The ABR advertises a default route into the
area and all the routers belonging to this area use the default route to send any traffic
outside the area.
• NSSA (Not So Stub Areas) can import AS external routes from within the area and
send them to other areas, but cannot receive AS external routes from other areas.
Inter-area and intra-area routes are allowed along with a default route which is
advertised to the area by the ABR.
• NSSA-TOTALLY-STUB areas are similar to NSSA with the additional restriction
that inter-area routes are not allowed.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Define the default metric (cost setting) for areas of type stub or NSSA.
Possible values range from 0 to 16777215, the default setting is 10.
Default metric for areas of type stub or NSSA: In areas of type stub or NSSA, each
Area Border Router (ABR) advertises a default route to the area; see Step 3. The
default metric indicates the cost setting of that default route.
If you have more than one ABR, and you want a particular ABR to take precedence
over other ABRs for routes towards the backbone area, for example due to bandwidth
limitations, then you can use the default metric to achieve this.
Note: Be sure to assign the lowest default metric to the preferred ABR. Increasing
values of the default metric indicate a decreasing order of precedence.
...................................................................................................................................................................................................
5 Specify whether opaque LSAs for the DNS application shall be distributed into this OSPF
area, and received from this area.
Note: DNS opaque LSAs can only be enabled in one OSPF Area.
...................................................................................................................................................................................................
6 Specify whether opaque LSAs for the Wave KEY application shall be distributed into this
OSPF area, and received from this area.
Note: Wave Key opaque LSAs can only be enabled in one OSPF Area.
...................................................................................................................................................................................................
7 If needed, set up virtual links.

Virtual links: OSPF requires that all areas attach directly to the backbone area (area
0.0.0.0), but the attachment need not be physical.
One can take any physical arrangement of areas and attach them logically through
OSPF virtual links. Specify the loopback interface IP address of the NE to terminate
the virtual link. This NE should have an interface that is connected to Area 0.0.0.0 and
a non 0.0.0.0 Area.
If the NE is not attached to the backbone area, the specified virtual link address is the
address of an ABR, which is attached to the backbone area.
If the NE is attached to the backbone area, the specified virtual link address is the
address of the NE, which has set up the corresponding reverse virtual link.
....................................................................................................................................................................................................................................
Issue 1 April 2014
....................................................................................................................................................................................................................................
Note:
• A virtual link must be configured on both NEs, that is two unidirectional links
have to be set up. Virtual links cannot be established through the backbone area,
stub areas, or areas of type NSSA.
• When a virtual link is created across an OSC or GCC path, be sure to set the MTU
size to 1500 bytes for the OSC/GCC interfaces on that path. Be aware that no
automatic checking is done by the NE regarding this MTU size setting.
E...................................................................................................................................................................................................
N D O F S T E P S
Procedure 3-5: Create static routes

Purpose
Use this procedure to add a new static IP route into the IP routing table.
Steps
...................................................................................................................................................................................................
1 Specify the IP address of the destination host or network and the subnet mask of the route.
...................................................................................................................................................................................................
2 Specify the IP address of the next interface (next hop) in the route. This is also known as
the “gateway address”.
Note: The destination host or network must be directly connected to this interface.
...................................................................................................................................................................................................
3 Define the distance value of the static route.

The NE allows to create multiple static routes to the same destination address via
different interfaces. The distance value can be used to decide which of the routes shall be
used for forwarding decisions. The route with the lowest distance value shall take
precedence.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Network Time Protocol (NTP)
Time management
....................................................................................................................................................................................................................................
Time management
Network Time Protocol (NTP)

Time of day synchronization
The NE supports an automatic time of day synchronization mode that uses the Network
Time Protocol (NTP).
NTP synchronization can be enabled or disabled, it is enabled by default.
Time-of-day synchronization modes

The NE shall support the following time-of-day synchronization modes:
• Non-synchronized, free-running mode: The NE is not synchronized to an NTP
server and is instead using its own internal clock as a source.
• Synchronized mode: The NE is using the NTP protocol to synchronize to an NTP
server. The NE is polling the NTP server and periodically making corrections to its
internal clock so as to maintain the same clock time as the NTP server.
• Non-synchronized, holdover mode: NTP is enabled, and the NE has lost NTP server
connectivity, and is using the last known clock update to synchronize its clock.
Supported protocol versions

The NE supports the NTP protocol version 4 which is backward compatible with NTP
version 3 and version 2.
NTP configuration
Please refer to the Alcatel-Lucent 1830 PSS User Provisioning Guide for NTP
configuration procedures.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration NE firewall with provisionable IP access control lists (IP
Security ACL)
....................................................................................................................................................................................................................................
Security
NE firewall with provisionable IP access control lists (IP ACL)

NE firewall
Alcatel-Lucent 1830 PSS systems provide an integrated NE firewall with provisionable
IP access control lists (IP ACL) to protect the system against security threats.
The basic configuration of the NE firewall consists of fixed filtering rules which cover
well known security threats. The functional range of the NE firewall can be extended by
adding user-specific filtering rules.
Important! User-specific filtering rules can only impose further restrictions on the
default setup of the NE firewall, it is not possible to open the NE firewall more than
the basic configuration allows.
Filters
The WebUI supports viewing a list of all filters and their associated patterns. Each filter
may be associated with up to 256 patterns. The WebUI also supports creating a new filter.
Up to 100 filters may be defined on the system.
The WebUI supports adding a pattern to an existing Filter ID. When adding a pattern, the
WebUI displays a picklist of existing patterns that are not already associated with this
filter to choose from. The user must specify a Pattern Index with each selected pattern.
The WebUI also supports deleting a pattern from an existing Filter ID. A filter can only be
deleted when all patterns have been removed for this filter.
Note: If the user specifies a Pattern Index that is already associated with this Filter ID,
the WebUI will delete the existing Pattern/Filter pair and create a new one with the
specified Pattern ID/Index.
Patterns
The WebUI supports viewing a list of all patterns used for IP access control. The WebUI
also supports creating, modifying, deleting, and viewing of patterns. A pattern can only be
deleted if it is not associated with a filter.
Ports
The WebUI supports viewing a list of all port to ACL filter associations.
The WebUI allows a user to create, modify, and view an association between an ACL
filter and a specified port and direction. When creating or modifying an association, the
WebUI displays a picklist of existing filters to choose from. An association between a
filter and port/direction can also be deleted.
....................................................................................................................................................................................................................................
Issue 1 April 2014
Security ACL)
....................................................................................................................................................................................................................................
Note: Up to 2 filters can be associated with each port, one in the receive direction and
one in the transmit direction. If a filter/port association already exists in a direction,
the WebUI will not allow the creation of another association to this port in the same
direction.
The following ports support ACL filtering.
Table 3-2 Ports that support ACL filtering
Card Port Signal Rate
112SCX10 L1 OTL4.4
11DPE12 L{1-2} OTU2

11DPE12A, 11DPE12E L{1-2} OTU2
11DPM12 L{1-2} OTU2

11QPA4, 11QPEN4 L{1-4} OTU2
11QPA4, 11QPEN4 C{1-4} OTU2

11QPE24 X{1-4} OTU2, 10GbE
11STAR1, 11STAR1A L1 OTU2
11STAR1, 11STAR1A C1 OTU2
11STMM10 C{1-10} OTU1
4DPA4 L{1-2} OTU1
A2325A, AHPHG, AHPLG, ALPHG, OSC
A2P2125, AM2125A, AM2318A, OSCT OSCSFP

MTC1T9 E1, E2, OAMP
USRPNL E1, E2, OAMP, VOIP
For the following ports, the user can view the system-defined port/filter associations. The
user may not edit the associations for these ports.
Table 3-3 System-defined port/filter associations
Card Port
EC CIT
EC (PSS-16, PSS-32 only) AUX
EC LAN-PPP
EC LAN-NODE
MTC1T9 CIT
MXEC320H
MTC1T9 LAN-PPP
MXEC320H
....................................................................................................................................................................................................................................
Issue 1 April 2014
Security ACL)
....................................................................................................................................................................................................................................
Table 3-3 System-defined port/filter associations (continued)
Card Port
MTC1T9 LAN-NODE
MXEC320H
Provisioning
Important! The provisioning of IP access control lists is reserved for security
administrators only.
Provisioning includes:
• Adding a new access control rule to the NE firewall
• Modifying an existing access control rule of the NE firewall
• Retrieving information concerning an existing access control rule of the NE
firewall
• Removing an access control rule from the NE firewall
Please refer to the Alcatel-Lucent 1830 PSS User Provisioning Guide for detailed
provisioning procedures.
RADIUS for user authentication

Introduction
At the first installation of the Alcatel-Lucent 1830 PSS, user authentication is done with
local database user definitions. Using Remote Authentication Dial In User Service
(RADIUS) permits the user to reinforce this security and share the same user definitions
between several NEs.
The procedure for setting RADIUS is:
1. Choose a RADIUS server
2. Activate the server for user authentication
Set the RADIUS server

The following TL1 or CLI command will set the RADIUS server on the Alcatel-Lucent
1830 PSS:
• TL1:
ENT-RADIUS-SERVER RAD1,ENABLE:IPADDR=<ip>[,PORT=<port>],
SECRET=< sharedSecret>;
• CLI:
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration RADIUS for user authentication
Security
....................................................................................................................................................................................................................................
config admin authentication radius add RAD1 <ip> [:<port>]
<sharedSecret>
<ip> is the IP address of the RADIUS server.
<port> is the IP port used by your RADIUS server. Possible values range from 1 to
65536, (0-1024 reserved) the default value is 1812.
<sharedSecret> is a password consisting of 5 to 32 characters .
Enable RADIUS usage

The following TL1 or CLI command will force user authentication using RADIUS server
on the Alcatel-Lucent 1830 PSS:
• TL1:
SET-RADIUS-AUTH:::::RADIUS;
• CLI:
config admin authentication order radius
Secure/unsecure mode
Introduction
At commissioning the Alcatel-Lucent 1830 PSS is provided in unsecure mode. In secure
mode, for the TL1/CLI flow, the telnet (23, 3082, 3083), ftp (20&21) and http (80) flow
will be disabled and only SSH, sFTP (22) and HTTPs (443) will be available; port
assignment in brackets.
SSH is designed as a replacement for TELNET and other insecure remote shells which
send informations notably passwords, in plaintext, leaving them open to interception. The
encryption used by SSH provides confidentiality and integrity of data over an insecure
network, such as Internet. Secure Shell allows a trusted path of communication between
two ends (eg., NE and EMS) using encrypted data stream.
Secure Shell (SSH)

Secure Shell (SSH) is a network protocol that allows data to be exchanged using a secure
channel between two network devices. This protocol implements ciphering and provides
authentication of the Alcatel-Lucent 1830 PSS. It has to be implemented on each
1830PSS NE (GNE or not) and the Alcatel-Lucent 1830 PSS will act as a server, clients
are applications on the Alcatel-Lucent 1350 OMS or any other terminal or customer
management system. The Alcatel-Lucent 1830 PSS supports SSH version 2.0 (SSHv2).
Important! The SSH key needs to be generated before the NE mode can be changed
to secure mode.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Secure/unsecure mode
Security
....................................................................................................................................................................................................................................
The procedure for implementing the secure mode is:
1. Generate the SSH key.
2. Set the secure mode on. In secure mode the user will not be able to connect without
SSH. So the key must have been generated before commuting to secure mode.
Certificate generation
Important! Generating an SSH key requires security administrator privileges.
The Alcatel-Lucent 1830 PSS is provided without any SSH key. A standard certificate can
be generated using TL1 or CLI:
• TL1:
INIT-SSH-KEY:[TID]::[CTAG]:::[KEYTYPE=][,MODULUS=];
KEYTYPE is DSA.
MODULUS is 0.
• CLI:
crypto key generate
Note that in principle two possible types of keys exist, DSA (Digital Signature Algorithm)
and RSA (cryptographic algorithm, named after its designers, Ron Rivest, Adi Shamir and
Leonard Adleman). In the current release, only the generation of DSA-type keys with
modulus zero is supported.
Example
To generate a DSA key with modulus zero:
INIT-SSH-KEY::::::KEYTYPE=DSA,MODULUS=0;
The network administrator can then get the public key, see “Getting the public key”
(p. 3-20), and install it on the servers.
Note: A regeneration of the SSH key will render all previous trusted entities using the
old key to flag the NE as untrusted because of the key change.
Hypertext Transfer Protocol Secure (HTTPS)

The Alcatel-Lucent 1830 PSS is provided with a self signed certificate. It is up to the
customer to allow this certificate in his network by adding it to his trusted certificates list.
The first time a user will connect to the NE, he will obtain a security alert stating that
there is a problem with the site's security certificate, or that the website is certified by an
unknown authority.
The right action is to select “No” or “Do not accept this certificate ...” and contact your
network administrator. The network administrator should examine the certificate and if he
recognizes it, add it to the trusted certificates list.
....................................................................................................................................................................................................................................
Issue 1 April 2014
Security
....................................................................................................................................................................................................................................
Secure mode initialization
Attention: Before changing the secure mode to ENCRYPTED, check the ability of the
managers to use SSH, HTTPs and sFTP. All the remote systems must be compliants.
Changing the secure mode will provoke a reboot of the Alcatel-Lucent 1830 PSS, and
if the remote systems cannot use SSH, HTTPs and sFTP, they will no longer be able
to connect to the Alcatel-Lucent 1830 PSS.
The following TL1 or CLI commands can be used to set the secure mode:
• TL1:
SET-ATTR-SECUDFLT::::::SECACC=ENCRYPTED;
• CLI:
crypto admin ui mode encrypted
Getting the public key

Important! Retrieving the public key requires security administrator privileges.
The following TL1 or CLI commands can be used to get the public key of the NE:
• TL1:
RTRV-SSH-KEY;
• CLI:
crypto key details
This key should be distributed on the SSH clients. If it is not, the client must be allowed
to accept the key at first connection.
This command can be used whatever is the secure mode (secure or unsecure).
Certificate modification
To modify the certificate, a new key generation must be performed, see “Certificate
generation” (p. 3-19).
OSPF authentication
The system supports independent OSPF authentication configuration on each NE
interface.
These interfaces include:
• OAMP
• VOIP
• E1 and E2
• GCC
....................................................................................................................................................................................................................................
Issue 1 April 2014
Security
....................................................................................................................................................................................................................................
• OSC
• LAN
The cryptographic algorithm is MD5 (Message Digest 5), it uses an MD5 128-bits hash
value generated from a key string (from 1 to 16 characters) that identifies the message
digest, and a key identifier (from 1 to 255) that identifies the secret key used to create the
message digest. The MD5 key string and key ID can be configured through user
interfaces.
In order to have successful authentication, both NEs must be configured with the same
parameters having the same parameter values.
If MD5 authentication is not successful for any reason, this will be treated as data link
failure causing an “OSPF Adjacency not Full” alarm.
The authentication can be turned on or off on a given NE interface.
Firewall configuration
Protocols/ports in secure mode
Table 3-4 Management flows and ports toward the GNE (secure mode)
Name Source Destination Dialogue Comment

port port initiator
SSH 22/tcp Manager Secured telnet and ftp. Use SSH
TL1 secure session Manager
opened through CLI
session over SSH
port 22 using “tools
tl1” CLI command
HTTPS 443/tcp Manager HTTPS
sFTP 22/tcp 1830 PSS
NTP 123/udp 1830 PSS Network time of day
synchronisation port
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Firewall configuration
Security
....................................................................................................................................................................................................................................
Protocols/ports in unsecure mode
Table 3-5 Management flows and ports toward the GNE (unsecure mode)
Name Source Destination Dialogue Comment

port port initiator
Telnet 23/tcp Manager
HTTP 80/tcp Manager
TL1 3082/tcp Manager Destination port opened by OAM
server TL1 agent – raw mode
3083/tcp Manager Destination port opened by OAM
server TL1 agent
MTNM/Corba 34567/tcp Manager GMPLS MTNM management
GMRE CLI 30000/tcp Manager GMPLS CLI management
FTP 20/tcp 1830 PSS
21/tcp
sFTP 22/tcp 1830 PSS Secured FTP
MTNM/Corba 5066/tcp 1830 PSS GMPLS MTNM management
NTP 123/udp 1830 PSS Network time of day
synchronisation port
IPSec tunnel
Network security level
It is up to the customer to determine the security level of his network and so to decide if
IPSec tunneling is required.
Note: If IPSec tunneling is needed, then the front router must be able to manage IPSec
tunneling because this feature is not available on Alcatel-Lucent 1830 PSS systems.
IPSec tunneling
Important! If the communication channel has to go through an unsecure network
between the management system and the Alcatel-Lucent 1830 PSS GNE, IPSec
tunneling is highly recommended. The same recommendation holds for the intra-area
links between the front routers of the GNEs.
An unsecure network could be the Internet domain or a third party network, for instance.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration IPSec tunnel
Security
....................................................................................................................................................................................................................................
The following figure shows an example.
Figure 3-1 IPSec tunneling

IPSEC tunnel,
for management
Management Centre
through Internet
EMS/NMS
Customer Intranet
Customer
Emergency
Access
CustomerManagement Internet
network
Customer Aggregation network
IPSEC or GRE First LAN

Second LAN
tunnel, for
management Direct link through
IP R1 IPSEC or GREtunnel,
inside Area #1 R2
IP
OSPF area GNE 1 OSC GNE 2
OADM
#i Terminal
OSC Terminal
Repeater OSC
Optional firewall Mandatory firewall End/Start of tunnel
The graphic describes three possible use cases of tunnels:

• The first one is to secure the rescue intra-area link between the two routers R1 and
R2. This allows the extension of the OSPF area and builds a ring with the 1830 PSS,
R1 and R2 inside the OSPF area #i. (green surrounded).
• The second one is to secure communications coming through a not trusted network,
such as the Internet, for example. Tunnel must be established to cross the unsecured
network. Firewalls are mandatory. Typically, these tunnels are set toward the
management center.
• The third one is to secure the communication channel between R1 and the
management center. In the example, a tunnel is set between the customer LAN and
R1; another one is set between the customer LAN and R2. Firewalls are optional,
depending on the security level of each zone. Note that it is recommended to end the
tunnel before crossing a firewall (and reopen it on the other side of the firewall, if
needed).
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Syslog server
Security
....................................................................................................................................................................................................................................
Syslog server
The Alcatel-Lucent 1830 PSS supports syslog server.
Advice on security hardening on the Alcatel-Lucent 1830 PSS

TL1 commands
These TL1 commands are available for hardening the 1830PSS:
• SET-ATTR-SECUDFLT
• SET-ATTR-SECULOG
• ED-USER-SECU
Note: We strongly advise to use these commands for hardening the 1830PSS DCN
interface.
Table 3-6 Parameters of the SET-ATTR-SECUDFLT command
Parameter Meaning
MINPIDLEN=10 Minimum password length
PAGE=30 Default value for password aging in days
PCND=7 Default number of days to change the password after PAGE
PCNN=3 Default number of login with aged password after PAGE
POINT=180 Default value for password obsolescence value in days
MINITVL=15 Default value for minimum interval in seconds between two invalid
login attempts
MXINV=3 Max Invalid Attempts, indicates the maximum number of
consecutive invalid login attempts (regardless of time interval or
number of sessions), before an NE shall logout a user and lockout
the user channel.
TMOUT=15 Default number of minutes of inactivity before closing session
KMINTVL=0 Keep Alive Message Interval, Not activated (not implemented in
1830PSS)
SECACC=SECURE Secure / unsecure mode
Router hardening
The security features of the router should be activated, that is policies, access lists,
authentication, encryption, etc.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Advice on security hardening on the Alcatel-Lucent
Security 1830 PSS
....................................................................................................................................................................................................................................
Firewalls
Firewalls can be implemented at the border of a WDM sub-network in order to filter
flows at going From/To WDM.
Attention: Firewalls must be implemented if the IP flow has to go through unsecure
zones, such as the Internet for example.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration Overview
....................................................................................................................................................................................................................................
SWNE functionality
Purpose
Software download to a network of nodes can be accelerated by first downloading the SW
release to the designated SWNE (Software Server NE).
Functional principle
The SWNE can be configured to serve as FTP servers for the other Remote NEs (RNEs)
within the Alcatel-Lucent 1830 PSS network. Given that the SWNE is to respond to FTP
requests, it is understood that the SWNE may be opened to malicious attacks. This
weakness can be addressed with IP Access Control Lists (IP ACL) to disallow FTP
requests from unspecified sources.
Any NE can be configured as a designated SWNE, which runs FTP server and be
available to accept FTP requests over OSC and GCC interfaces. More than one SWNE
can be configured in a WDM network. Incoming FTP requests must be locally
authenticated. SWNE is only working in normal mode, it is not working in encrypted
mode.
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration SWNE functionality
....................................................................................................................................................................................................................................
The following figure shows an example.
Figure 3-2 Usage of SWNEs in a WDM network
....................................................................................................................................................................................................................................
Issue 1 April 2014
DCN configuration SWNE functionality
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 1 April 2014
4 4 MPLS Routing Engine
G
(GMRE)
Overview
Purpose
This section provides information which is necessary to setup GMRE using
Alcatel-Lucent 1830 PSS.
Contents
Specific considerations regarding the GMPLS Routing Engine (GMRE) 4-1
Specific considerations regarding the GMPLS Routing Engine

(GMRE)
Control plane IP addresses
As all GMRE protocols are IP-based, a set of IP addresses needs to be defined for each
GMRE node.
Important! The SYSTEM address (loopback IP address) has first to be configured
before the control plane IP addresses can be set.
Each GMRE node requires the following IPv4 addresses:
• GMRE node address, used for the RSVP-TE, OSPF-TE and LMP protocols.
Setting the GMRE node address is essential for the GMRE network configuration.
Note that the control plane can start only after the GMRE node address has been
configured.
• GMRE notify address, used for fast restoration trigger notification.
...................................................................................................................................................................................................................................
Issue 1 April 2014
GMPLS Routing Engine (GMRE) Specific considerations regarding the GMPLS Routing Engine
(GMRE)
....................................................................................................................................................................................................................................
The GMRE notify address is used to signal failures on downstream nodes upstream to
the head node. The GMRE notify address is always freely routed, to ensure that the
packets are routed as fast as possible towards the head node.
• GMRE management address
The GMRE management address is used for the communication between the GMRE
and its management interfaces, such as CLI or MTNM CORBA. The GMRE
management address corresponds to the SYSTEM address (also known as the “OSPF
router ID” or “loopback IP address”).
Recommendations
The GMRE node address and the GMRE notify address have to be explicitly configured
by the operator via the 1830 WebUI or via the 1830 CLI. The GMRE addresses must be
unique within the GMRE network and disjoint to all subnets.
Attention: Ensure that the settings for GMRE node and notify address are correct.
After activating the GMRE, the modification of these addresses is not possible
anymore without traffic impact. To modify the GMRE node address, the node must be
reinstalled and all LSPs related to this node will be failed or deleted.
Attention: Never try to change the node or notify address after the activation of the
GMRE node. The applications of that node will not startup again.
Example for GMRE node addresses

A commonly used way to assign IP addresses in the network is the following approach:
1. Assign a unique natural number n to each GMRE node.
2. Derive the GMRE node and GMRE notify addresses using the number n:
• GMRE node address: 10.27.255.n
• GMRE notify address: 10.27.254.n
Here, “255” indicates GMRE node addresses while “254” indicates GMRE notify
addresses.
See also “Rules and guidelines” (p. 2-48).
Specific MCN and SCN considerations for an MRN control plane

For the MRN-specific DCN aspects of management communication (MCN) and signaling
communication (SCN), please refer to:
• MCN: “Recommendations for an MRN control plane” (p. 2-26)
• SCN: “Recommendations for an MRN control plane” (p. 2-30)
....................................................................................................................................................................................................................................
Issue 1 April 2014
5 S5upervision and
troubleshooting
Overview
Purpose
This section presents information specific for the area of fault handling.
Contents
Monitoring, diagnosis and troubleshooting of abnormal situations 5-1
Monitoring, diagnosis and troubleshooting of abnormal

situations
Alarms and troubleshooting
Typical sources of errors relating to the Data Communication Network (DCN) include:
• Improper cabling:
– Incorrect cable routing between communication partners
– Incorrect cable types
• Inconsistent provisioning on both sides of a connection
• Failures regarding the link integrity, for example on OAMP, VOIP, E1, and E2 ports.
• Improper powering, setup and configuration of connected equipment
As a result, dedicated alarms will be reported, for example:
• APR Active - OSC Disabled (APROSC)
• Data Link down (NET)
• Link Down (NET)
• Network Time Protocol is enabled-no server is reachable
(NTPOOSYNC)
• OSPF Adjacency not Full (OSPFADJ)
...................................................................................................................................................................................................................................
Issue 1 April 2014
Supervision and troubleshooting Monitoring, diagnosis and troubleshooting of abnormal
situations
....................................................................................................................................................................................................................................
Please refer to the Alcatel-Lucent 1830 PSS Maintenance and Trouble-Clearing Guide for
alarm descriptions and trouble-clearing procedures.
....................................................................................................................................................................................................................................
Issue 1 April 2014
Glossary
...................................................................................................................................................................................................................................
Numerics
1350 OMS
see “Alcatel-Lucent 1350 Optical Management System” (p. GL-1).
...................................................................................................................................................................................................................................
A ABR
Area Border Router
Alcatel-Lucent 1350 Optical Management System (OMS)

The Alcatel-Lucent 1350 OMS is a network management system which provides unified
end-to-end network management and operational support for all network element products in the
Alcatel-Lucent Optics portfolio. The Alcatel-Lucent 1350 OMS provides a common management
platform for end-to-end operations, including service provisioning over multi-technology optical
infrastructures (SDH/SONET, Carrier Ethernet, WDM, ROADM) and OSS/BSS (Operations
Support Systems/Business Support Systems) integration.
ARP
Address Resolution Protocol
ASBR
Autonomous System Boundary Router
ASON
Automatically Switched Optical Network
...................................................................................................................................................................................................................................
B B&W interface (Black-and-white interface, Uncolored interface, Fixed-wavelength interface)

An optical interface supporting a single wavelength only.
BR
Backbone Router
...................................................................................................................................................................................................................................
C CIDR
Classless Inter-Domain Routing
CIT
Craft Interface Terminal
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS GL-1
Issue 1 April 2014
Glossary
....................................................................................................................................................................................................................................
CLI
Command Line Interface
CORBA (Common Object Request Broker Architecture)

The communication interface between the Alcatel-Lucent 1350 OMS and the GMRE
CP
Control plane
...................................................................................................................................................................................................................................
D DCN
Data Communication Network
DSA
Digital Signature Algorithm
...................................................................................................................................................................................................................................
E E1, E2
E1/E2 LAN interface ports
EC
Equipment Controller
ECC
Embedded Communication Channel
...................................................................................................................................................................................................................................
F FLC
First-level Controller
FTP
File Transfer Protocol
...................................................................................................................................................................................................................................
G GCC
General Communication Channel
GMPLS
Generalized Multi-Protocol Label Switching
GMRE
GMPLS Routing Engine
GNE
Gateway Network Element
....................................................................................................................................................................................................................................
GL-2 Alcatel-Lucent 1830 PSS
Issue 1 April 2014
Glossary
....................................................................................................................................................................................................................................
GRE
Generic Routing Encapsulation
GUI
Graphical User Interface
...................................................................................................................................................................................................................................
H HDLC
High-Level Data Link Control
HTTPS
Hypertext Transfer Protocol Secure
...................................................................................................................................................................................................................................
I IANA
Internet Assigned Numbers Authority
ICMP
Internet Control Message Protocol
IEEE
Institute of Electrical and Electronics Engineers
IETF (Internet Engineering Task Force)

The IETF is a standards organization that develops and distributes standards for the Internet.
Documents published by the IETF are called Request for Comments (RFC).
ILAN
Internal LAN
Internet Protocol Security (IPSec)

IPSec is a set of protocols to provide secure IP communication by means of authentication and
encryption mechanisms.
IOR
Interoperable Object Reference
IP
Internet Protocol
IPCC
IP Control Channel
IPCP
IP Control Protocol
IPv4
Internet Protocol version 4
....................................................................................................................................................................................................................................
Issue 1 April 2014
Glossary
....................................................................................................................................................................................................................................
IR
Internal Router
ISO
International Organization for Standardization
...................................................................................................................................................................................................................................
L LAN
Local Area Network
LCP
Link Control Protocol
LLC
Logical Link Control
LSA
Link State Advertisement
LSW (RSTP)
LAN switching infrastructure that supports the Rapid Spanning Tree Protocol (RSTP) according
to the IEEE802.1D-2004 standard.
...................................................................................................................................................................................................................................
M MAC
Media Access Control
MAN
Metropolitan Area Network
MCN (Management Communication Network)

According to the RFC 5951, a DCN supporting management plane communication is referred to
as a Management Communication Network (MCN).
MD5 (Message Digest 5)

Message Digest 5 is an algorithm that is used to verify data integrity, intended to be used with
digital signature applications.
MLN (Multi-Layer Network)

According to the IETF RFC 5212, a multi-layer network (MLN) is a traffic engineering domain
comprising multiple data plane switching layers that are controlled by a single GMPLS control
plane instance.
MP
Management plane
MRN (Multi-Region Network)

A multi-region network (MRN) is defined as a traffic engineering domain supporting at least two
....................................................................................................................................................................................................................................
Issue 1 April 2014
Glossary
....................................................................................................................................................................................................................................
different switching types, either hosted on the same device or on different ones and under the
control of a single GMPLS control plane instance.
MTNM
Multi-Technology Network Management
MTU
Maximum Transmission Unit
...................................................................................................................................................................................................................................
N NE
Network Element
NM
Network Management
NMS
Network Management System
NOC
Network Operations Center
NTP
Network Time Protocol
...................................................................................................................................................................................................................................
O OADM
Optical Add/Drop Multiplexer
OAMP
Operations, Administration, Maintenance and Provisioning
OCh
Optical Channel
ODU
Optical Channel Data Unit
OPU
Optical Channel Payload Unit
OSC
Optical Supervisory Channel
OSI
Open System Interconnection
....................................................................................................................................................................................................................................
Issue 1 April 2014
Glossary
....................................................................................................................................................................................................................................
OSPF
Open Shortest Path First
OT
Optical Transponder
OTU
Optical Channel Transport Unit
...................................................................................................................................................................................................................................
P PhM
Photonic Manager
PPP
Point-to-Point Protocol
...................................................................................................................................................................................................................................
R RFC
Request for Comments; see also “IETF” (p. GL-3)
RMI
Remote Method Invocation
RNE
Remote Network Element (not a GNE)
RSA
A cryptographic algorithm for public-key encryption, named after Ron Rivest, Adi Shamir and
Leonard Adleman who developed the algorithm.
RSTP
Rapid Spanning Tree Protocol
RSVP
Reservation Protocol
...................................................................................................................................................................................................................................
S SCN (Signaling Communication Network)

According to the RFC 5951, a DCN supporting control plane communication is referred to as a
Signaling Communication Network (SCN).
SCP
Secure Copy
Secure Shell (SSH)

Secure Shell (SSH) is a network protocol that allows data to be exchanged using a secure channel
between two network devices.
....................................................................................................................................................................................................................................
Issue 1 April 2014
Glossary
....................................................................................................................................................................................................................................
Secure Shell File Transfer Protocol (SFTP)
SFTP is used for secure access to manage and download/upload files.
According to the IETF (see also “IETF” (p. GL-3)), the Secure Shell File Transfer Protocol
provides secure file transfer functionality over any reliable, bidirectional octect stream. It is the
standard file transfer protocol for use with the SSH2 protocol (SSH v2).
SFTP is also known as “SSH File Transfer Protocol”, “Secret File Transfer Protocol”, or “Secure
FTP”.
...................................................................................................................................................................................................................................
T TCP
Transmission Control Protocol
TCP/IP
Transmission Control Protocol/Internet Protocol
TL1
Transaction Language 1
TTL
Time To Live
...................................................................................................................................................................................................................................
U UDP
User Datagram Protocol
...................................................................................................................................................................................................................................
V VoIP
Voice over IP
...................................................................................................................................................................................................................................
W WDM
Wavelength Division Multiplexing
....................................................................................................................................................................................................................................
Issue 1 April 2014
Glossary
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
Issue 1 April 2014
Index
A Access control list (ACL), 3-15 .............................................................
............................................................. R Remote NE (RNE), 2-8, 2-10,

2-16, 2-17, 2-18
C Craft terminal, 2-5
.............................................................
.............................................................
U Uplink card management, 2-11
E E1/E2 LAN interfaces, 2-5
User Panel (USRPNL), 2-3
Extension subrack connection, 2-5
.............................................................
.............................................................
V VoIP LAN interface, 2-5
G Gateway NE (GNE), 2-8, 2-10,
2-10, 2-12, 2-14
GMRE management address, 4-1
GMRE node address, 4-1
GMRE notify address, 4-1
.............................................................
I IP access control list (IP ACL),

3-15
IP tunnel termination endpoints,
4-1
.............................................................
L Loopback IP address
(LOOPBKIP), 4-1
.............................................................
N NE firewall, 3-15
.............................................................
O OAMP LAN interface, 2-5
OAMP LAN port redundancy,

2-11, 2-14, 2-18
....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS IN-1
Issue 1 April 2014
Index
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
IN-2 Alcatel-Lucent 1830 PSS
Issue 1 April 2014

8DG61258GAAATPZZA - V1 - 7.0 DCN Planning and Engineering Guide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

8DG61258GAAATPZZA - V1 - 7.0 DCN Planning and Engineering Guide

Încărcat de

Drepturi de autor:

Formate disponibile

Title page

Interference Information: Part 15 of FCC Rules

About this document

Intended audience ...................................................................................................................................................................... xiii

Supported systems ..................................................................................................................................................................... xiii

Conventions used ....................................................................................................................................................................... xiv

Related information .................................................................................................................................................................... xv

Technical support ..................................................................................................................................................................... xviii

How to comment ..................................................................................................................................................................... xviii

Overview ...................................................................................................................................................................................... 1-1

Basic aspects of network design

Network layers ........................................................................................................................................................................... 1-2

Physical layer ............................................................................................................................................................................. 1-3

Data Link layer .......................................................................................................................................................................... 1-4

Network layer ............................................................................................................................................................................. 1-5

Transport layer ........................................................................................................................................................................... 1-8

Application layer ....................................................................................................................................................................... 1-9

Overview ...................................................................................................................................................................................... 2-1

Preconditions and requirements ........................................................................................................................................... 2-2

Overview ................................................................................................................................................................................... 2-20

Management DCN aspects .................................................................................................................................................. 2-20

Signaling DCN aspects ......................................................................................................................................................... 2-29

Network topology concept and dimensioning

The Alcatel-Lucent 1830 PSS management network ............................................................................................... 2-39

Basic network topologies .................................................................................................................................................... 2-42

Network IP architecture ....................................................................................................................................................... 2-45

Summary of important rules and guidelines ................................................................................................................. 2-52

Overview ...................................................................................................................................................................................... 3-1

Procedure 3-1: Configure physical properties of interfaces ...................................................................................... 3-3

DCN configuration overview ............................................................................................................................................... 3-5

Procedure 3-2: Configure IP addresses and TCP/IP parameters .............................................................................. 3-5

Procedure 3-3: Configure OSPF parameters ................................................................................................................... 3-7

Procedure 3-4: Create an OSPF area ............................................................................................................................... 3-11

Procedure 3-5: Create static routes .................................................................................................................................. 3-13

Network Time Protocol (NTP) .......................................................................................................................................... 3-14

RADIUS for user authentication ...................................................................................................................................... 3-17

Firewall configuration .......................................................................................................................................................... 3-21

IPSec tunnel .............................................................................................................................................................................. 3-22

Syslog server ............................................................................................................................................................................ 3-24

Advice on security hardening on the Alcatel-Lucent 1830 PSS ........................................................................... 3-24

Software Server NE (SWNE)

SWNE functionality .............................................................................................................................................................. 3-26

4 GMPLS Routing Engine (GMRE)

Overview ...................................................................................................................................................................................... 4-1

5 Supervision and troubleshooting

Overview ...................................................................................................................................................................................... 5-1

Monitoring, diagnosis and troubleshooting of abnormal situations ....................................................................... 5-1

1 Information products related to Alcatel-Lucent 1830 PSS .......................................................................... xv

2-1 TCP/IP protocol stack .............................................................................................................................................. 2-2

2-2 User service interfaces ............................................................................................................................................. 2-3

2-3 DCN-related external interfaces (USRPNL) ................................................................................................... 2-5

2-4 OSPF metrics for an MRN control plane ....................................................................................................... 2-33

2-5 Organization of the networks .............................................................................................................................. 2-47

2-6 Default behavior of DCN-related interfaces ................................................................................................. 2-49

2-7 Engineering rules and guidelines ...................................................................................................................... 2-52

2-8 Required buffering and table sizes .................................................................................................................. 2-54

3-1 TCP/UDP ports used to access the NE .............................................................................................................. 3-6

3-2 Ports that support ACL filtering ......................................................................................................................... 3-16

3-3 System-defined port/filter associations ........................................................................................................... 3-16

3-6 Parameters of the SET-ATTR-SECUDFLT command .............................................................................. 3-24

1-1 ISO/OSI network architecture ............................................................................................................................... 1-2

1-2 Typical interconnection of OSPF areas ............................................................................................................. 1-7

2-1 Alcatel-Lucent 1830 PSS-32 User Panel faceplate ....................................................................................... 2-4