450-3708-011 - Z-Series - DCN - Planning-And - Configuration - 2.0

Ciena Z-Series
Packet-Optical Transport Networking Platform
Z-Series Data Communications Network

Planning and Configuration Reference Guide
450-3708-011 – Standard Issue 2.0
May 2018
Copyright© 2018 Ciena® Corporation. All Rights Reserved.

Z-Series DCN Planning and Configuration Ciena
Legal Notices, Copyright, and Trademark

LEGAL NOTICES
THIS DOCUMENT CONTAINS CONFIDENTIAL AND TRADE SECRET INFORMATION OF
CIENA CORPORATION AND ITS RECEIPT OR POSSESSION DOES NOT CONVEY ANY RIGHTS
TO REPRODUCE OR DISCLOSE ITS CONTENTS, OR TO MANUFACTURE, USE, OR SELL
ANYTHING THAT IT MAY DESCRIBE. REPRODUCTION, DISCLOSURE, OR USE IN WHOLE
OR IN PART WITHOUT THE SPECIFIC WRITTEN AUTHORIZATION OF CIENA CORPORATION
IS STRICTLY FORBIDDEN.
EVERY EFFORT HAS BEEN MADE TO ENSURE THAT THE INFORMATION IN THIS
DOCUMENT IS COMPLETE AND ACCURATE AT THE TIME OF PUBLISHING; HOWEVER, THE
INFORMATION CONTAINED IN THIS DOCUMENT IS SUBJECT TO CHANGE.
While the information in this document is believed to be accurate and reliable, except as otherwise
expressly agreed to in writing CIENA PROVIDES THIS DOCUMENT “AS IS” WITHOUT
WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information
and/or products described in this document are subject to change without notice. For the most up-to-date
technical publications, visit www.ciena.com.
Copyright© 2018 Ciena® Corporation – All Rights Reserved

The material contained in this document is also protected by copyright laws of the United States of
America and other countries. It may not be reproduced or distributed in any form by any means, altered in
any fashion, or stored in a database or retrieval system, without the express written permission of Ciena
Corporation.
Ciena®, the Ciena logo, Z22™, Z33®, Z77®, Blue Planet® and other trademarks and service marks of
Ciena appearing in this publication are the property of Ciena. Trade names, trademarks, and service marks
of other companies appearing in this publication are the property of the respective holders.
Security
Ciena cannot be responsible for unauthorized use of equipment and will not make allowance or credit for
unauthorized use or access.
© 2018 Ciena® Corporation – All Rights Reserved.
450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. Page 2
Contacting Ciena
Corporate headquarters 410-694-5700 or 800-921-1144 www.ciena.com
Customer technical support/warranty
In North America 1-800-CIENA24 (243-6224)
410-865-4961
In Europe, Middle East, and Africa 800-CIENA-24-7 (800-2436-2247)
+44-207-012-5508
In Asia-Pacific 800-CIENA-24-7 (800-2436-2247)
+81-3-6367-3989
+91-124-4340-600
In Caribbean and Latin America 800-CIENA-24-7 (800-2436-2247)
410-865-4944 (USA)
Sales and General Information 410-694-5700 E-mail: sales@ciena.com
In North America 410-694-5700 or 800-207-3714 E-mail: sales@ciena.com
In Europe +44-207-012-5500 (UK) E-mail: sales@ciena.com
In Asia +81-3-3248-4680 (Japan) E-mail: sales@ciena.com
In India +91-124-434-0500 E-mail: sales@ciena.com
In Latin America 011-5255-1719-0220 (Mexico City) E-mail: sales@ciena.com
Training 877-CIENA-TD (243-6283) E-mail: sales@ciena.com
or 410-865-8996
For additional office locations and phone numbers, visit the Ciena website at www.ciena.com.
Naming Conventions
The following graphical icons identify specific features or functions to stress importance:
Important! — Information that must be seriously considered.
Note: Special suggestions, advice, or information that should be seriously considered.
Safety Symbols and Labels

Read and understand all warning labels before working with equipment.
Warning
This warning symbol means danger. You are in a situation that could cause bodily injury.
Caution
Environment requires a moderate level of awareness. There is a moderate level of danger to
yourself or others.
Laser Equipment Present
Electrostatic Discharge (ESD) Sensitive Equipment
Contents
1.1 Equipment DCN ports, connection types, and protocols .............................................................. 8
1.1.1 BOSS Termination Module .................................................................................................. 8
1.1.2 Common Equipment Module (CEMi) ................................................................................... 8
1.1.3 LAD modules....................................................................................................................... 9
1.1.4 Wavelength Selective Switch (WSS) modules .................................................................... 10
1.1.5 L-AMP shelf ...................................................................................................................... 10
1.1.6 Z-Series line modules ......................................................................................................... 11
1.2 Routing feature − default settings ............................................................................................. 11
1.3 Limits and constraints............................................................................................................... 12
1.3.1 Maximum number of OSPF areas in a node ........................................................................ 12
1.3.2 Maximum number of hosts and routes per NE/module type ................................................ 12
1.3.3 Z77 shelves ........................................................................................................................ 13
1.3.4 Non-Z77 Z-Series shelves .................................................................................................. 13
1.3.5 IP address restrictions......................................................................................................... 13
1.3.6 Latency (RTD) ................................................................................................................... 13
1.3.7 Bandwidth required ............................................................................................................ 13
1.3.8 Security.............................................................................................................................. 13
1.4 Topology Discovery and Routing ............................................................................................. 14
1.5 Simple planning rule of thumb.................................................................................................. 14
1.6 DCN elements .......................................................................................................................... 15
1.6.1 Node-type definitions ......................................................................................................... 15
1.6.2 Connection Type definitions............................................................................................... 15
1.7 Scenarios .................................................................................................................................. 16
1.7.1 Standard scenarios.............................................................................................................. 16
1.7.2 Dual GNE OSPF ................................................................................................................ 16
1.8 Ingress and egress paths............................................................................................................ 26

1.9 Workaround ............................................................................................................................. 26
1.10 Configuration ........................................................................................................................... 26
1.10.1 Admin State provisioning ................................................................................................... 26
1.10.2 OSPF ................................................................................................................................. 27
1.10.3 IB Connection type ............................................................................................................ 28
1.10.4 MAN Connection Type ...................................................................................................... 31
1.10.5 Enable Routing for a Z22 or Z33 shelf ................................................................................ 31
1.10.6 Enable OSPF for a Z77 shelf MGMT port .......................................................................... 32
1.11 Using the Owner field to identify DCN Connection Type as carrying Routing .......................... 33
1.11.1 MGMT ports ...................................................................................................................... 33
1.11.2 LAN/WAN and OTN ports ................................................................................................ 35
1.11.3 OSC Ports .......................................................................................................................... 36
1.12 Checks ..................................................................................................................................... 36
1.12.1 OSPF Information tab ........................................................................................................ 36
1.12.2 Ping ................................................................................................................................... 38
1.12.3 Traceroute .......................................................................................................................... 38
1.12.4 Route ................................................................................................................................. 39
1.13 Conformity ............................................................................................................................... 40
1.14 Exception handling ................................................................................................................... 40
1.15 Sources of error ........................................................................................................................ 40
1.15.1 Incorrect configurations...................................................................................................... 40
1.15.2 Route flap .......................................................................................................................... 40
1.15.3 Backhaul DCN ................................................................................................................... 40
1.15.4 Route list exhaustion .......................................................................................................... 40
1.15.5 Transmission errors ............................................................................................................ 41
1.15.6 Routing loops ..................................................................................................................... 41
Appendix A: Default Route for Node Management ........................................................................... 42
Table of Figures
Figure 1: DCN Network Example .......................................................................................................... 17
Figure 2: Z-Series DCN Planning Tool – Output Example...................................................................... 19
Figure 3: Shelf/Site Configuration Example ........................................................................................... 20
Figure 4: Shelf Connections Example 1 .................................................................................................. 20
Figure 7: DCN Assignment for nodeD ................................................................................................... 22
Figure 8: Example of area1 .................................................................................................................... 22
Figure 9: IB Connection for Link 6 ........................................................................................................ 23
Figure 10: OSPF Area Access Example 1............................................................................................... 23
Figure 11: OSPF Area Access Example 2............................................................................................... 24
Figure 12: OOB Connection Example 1 ................................................................................................. 25
Figure 13: OOB Connections Example 2 ................................................................................................ 25
Figure 14: OSPF Configuration Dialog Box Example............................................................................. 27
Figure 15: Transport Resources > Physical Resources Tab Example ....................................................... 29
Figure 16: Routing Parameter................................................................................................................. 29
Figure 17: MAN Connection .................................................................................................................. 33
Figure 18: Port Information & Configuration Screen .............................................................................. 34
Figure 19: OOB Connection................................................................................................................... 34
Figure 20: Example of Using the Description Field (Transport Resources / General Tab) ....................... 35
Figure 21: Owner Field .......................................................................................................................... 35
Figure 22: OSC Ports ............................................................................................................................. 36
Figure 23: OSPF Information – Neighbors Tab ...................................................................................... 37
Figure 24: OSPF Information – Routers Tab .......................................................................................... 37
Figure 25: OSPF Information – ARP Tab ............................................................................................... 37
Figure 26: Valid CLI Ping Example ....................................................................................................... 39
Figure 27: CLI Route Command Example .............................................................................................. 39
This reference guide provides an overview of the Ciena Z-Series packet-optical platform Data
Communications Network (DCN). This guide provides information on typical Z-Series data
communications network configurations/models, and examples and guidance. For general product
information about the Z-Series platform, see the Z-Series Engineering and Planning Guide.
The guide provides information on DCN planning for Z-Series products including general information on
data communications and addressing for use as a reference for data communications information.
Note: Defining a full DCN design taking into account all factors of that design is outside the scope of this
reference guide. However, the performance and design limits and planning rules have been included
where they have a bearing on configuring Z-Series nodes in the DCN.
1.1 Equipment DCN ports, connection types, and protocols

1.1.1 BOSS Termination Module
The BOSS Termination Module (BTM) provides physical termination for the various alarm and
management interfaces supported by the BOSS (BOSS and BOSS2) cards. One BTM connects to both
Z77 BOSS shelf control cards simultaneously, and uses two slots at the rear of the Z77 shelf. This allows
either BOSS card to serve as master and access all the physical connections to the system. The BTM
contains no active components, except for relays used for BOSS failover and a small EEPROM for
inventory purposes.
The BTM Ethernet interface, labeled MGMT1, provides access to the out-of-band Data Communication
Network (DCN). Use the DCN as a communication network for network management. These interfaces
support VLANs and make use of OSPF routing on the BOSS cards.
The iLAN Ethernet interfaces provide DCN connectivity and make use of OSPF routing (iLAN-to-iLAN
connection). The iLAN ports provide IP access to secondary shelves (Z22, Z33, and other Z77 nodes).
1.1.2 Common Equipment Module (CEMi)

The CEMi I-Temp module provides the timing subsystem, telco alarms, inventory management, fan
control, active/standby arbitration, and an integrated DCN for the Z22 and Z33 shelves.
• Craft: 1 x 10/100/1000Base-T RJ-45
• iLAN: 2 x 10/100/1000Base-T RJ-45
• DCN: 1 x 100Base-FX SFP
The CEMi DCN Ethernet 100Base-FX SFP port provides an optional method for supporting DCN
management connectivity to the node.
The iLAN Ethernet interfaces provide DCN connectivity and make use of OSPF routing (iLAN-to-iLAN
connection). The iLAN ports can provide IP access to secondary shelves (Z22, Z77, and other Z33 nodes).
Important! — Multiple connections from a single CEMi module to different
far-end CEMi modules is supported in both point-to-point and ring topologies.
However, avoid multiple connections between the Ethernet ports (fiber or
copper) of two CEMi modules in the same shelf as this can result in an
inadvertent Ethernet loop that could severely affect system performance.
1.1.3 LAD modules

The 2, 4, 8, 40, and 96-channel Z‑Series Lambda Add/Drop (LAD) modules provide DWDM
connectivity. For the DCN, LAD modules provide an integrated 1510 nm Optical Supervisory Channel
(OSC) 100Base-FX Ethernet management channel for management visibility to all nodes. The purpose of
the Ethernet management channel is inter-node communication, but it can also carry other management
traffic from third-party systems if an out-of-band DCN network is required.
Note: LAD-2P and LAD-2G modules, deployed in Z22 systems, do not provide an
OSC. PME or PSW line card in-band management channels can be used.
Several versions of the optical LAD modules are available:

• LAD-2P: 2-channel (I-Temp) – no OSC
• LAD-2G 2-channel (I-Temp) – no OSC
• LAD-4: 4-channel
• LAD-4A: 4-channel with booster amplifier
• LAD-8i: 8-channel (I-Temp)
• LAD-8A: 8-channel with booster amplifier
• LAD-8E: 8-channel with pre-amp and booster amplifier
• LAD-8X: 8-channel with pre-amp and booster amplifier (40 dB reach)
Note: Only the Z22 shelf supports LAD-2 modules. The Z33 and Z77 shelves support
all other versions of LAD modules.
1.1.3.1 LAD OSC specifications

The following OSC specifications apply to all LAD modules (except the LAD‑2P and LAD‑2G, which
do not provide an OSC):
• Frequency: 198.5 THz 1510 nm
• Data Format: 100Base‑FX
• Maximum TX Power: 5 dBm Ethernet
• Minimum TX Power:
§ LAD‑8X: +1 dBm
§ Other LAD Modules: –1 dBm
• Maximum RX Power:
§ LAD‑8X: –7 dBm
• Minimum RX Power:
§ LAD‑8X: –43 dBm
• OSC Link Budget:
§ LAD‑8i: 5 – 22 dB
§ LAD‑8X: 12 – 44 dB
§ Other LAD Modules: 8 – 32 dB
1.1.4 Wavelength Selective Switch (WSS) modules

The Z-Series Wavelength Selective Switch (WSS) single-slot modules are multi-degree (2, 4, 8)
"Reconfigurable Optical Add Drop Multiplexer (ROADM)-on-a-blade." WSS modules are full ROADM
with Optical-Optical-Optical (OOO) switching and optical pass through. Both pre- and boost amplification
are included with automatic gain amplification and span activation.
WSS Module OSC Available Chassis
WSS-F2 Yes Z22, Z33, Z77
WSS-402 Yes Z22, Z33, Z77
WSS-404 Yes Z22, Z33, Z77
WSS modules provide a supervisory channel working on a non-traffic wavelength. Management VLANs
use this 100 Mbps channel to provide DCN connections to adjacent nodes.
The WSS module OSC specifications are as follows:
• Frequency: 198.5 THz 1510 nm
• Data Format: 100Base‑FX Ethernet
• Minimum TX Power: –2 dBm
• Minimum RX Power: –33 dBm
• Link Budget: 36 dB
1.1.5 L-AMP shelf

The Z-Series Lambda Amplifier (L-AMP) is a fully self-contained 1 RU module that functions as a bi-
directional mid-span optical amplifier / repeater. Each L-AMP shelf supports bi-directional physical layer
amplification of multiple DWDM wavelengths where node-to-node optical spans are greater than 80
kilometers.
Two L-AMP shelf Ethernet interfaces provide autosensing 10/100/1000 Mbps Ethernet connectivity. The
Ethernet ports are labeled “MGMT” and “CRAFT”:
• MGMT: Use the shelf management port to access the DCN that is available over the DWDM
interfaces.
• CRAFT: You can connect a laptop PC to the shelf craft port for a direct connection to commission
the L‑AMP module.
450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 10

The L-AMP shelf provides the following optical interfaces and access:
• 4 optical fiber interfaces
• Optical Supervisory Channel (OSC) – 100Base‑FX Ethernet at 1510 nm
1.1.6 Z-Series line modules

The following table shows the Z-Series line modules that provide an in-band management channel.
Line Module In-Band Available Z-Series Shelf
PME-412 Yes Z22, Z33, Z77
PME-216i Yes Z22, Z33, Z77
TSW-10G10 Yes Z77
PSW-10G10 Yes Z77 (Z33, Z22 R5.2)
PSW-10G20 Yes Z22, Z33, Z77
PSW-618 Yes Z77 (Z33, Z22 R5.2)
PSW-100G Yes Z22, Z33, Z77
SFT-8 No Z22, Z33, Z77
SFT-10G16 No Z22, Z33, Z77
2.5G-LME4 No Z22, Z33, Z77
DTM-8 No Z22, Z33, Z77
LME-10G10 No Z22, Z33, Z77
LME-10G10d Yes (GCC only) Z22, Z33, Z77
DTM-100G No Z22, Z33, Z77
DTM-100G2 Yes (GCC only) Z22, Z33, Z77
FLX-216i No Z22, Z33, Z77
MSE-1482 No Z22, Z33, Z77
The Z-Series can use an in-band management channel of up to 100 Mbps in bandwidth. If you configure
the Z-Series shelf with a line module and the shelf does not have a LAD or WSS/AWG module, you can
use the in-band facility on the line modules to carry the management VLANs by enabling the Routing
feature on the intended interface.
1.2 Routing feature − default settings

The following list of Z-Series line cards shows which ports have Routing enabled by default for the line
card default signal type. Installing a Z-Series module into an empty card slot automatically enables
Routing by default for the intended ports. Note that if you change the port signal type, for example
changing the signal type from 10GE LAN to ODU2e, the Routing attribute may change.
Logical Ports with
Z-Series Module Routing Enabled by Port Names
Default
BTM (Z77 only) 3, 4 iLAN1, iLAN2
CEMi (Z22 and Z33 only) 2, 3, 4 DCN, iLAN1, iLAN2
DTM-100G2 1 100G Port 1

Logical Ports with

Z-Series Module Routing Enabled by Port Names
Default
LAC-8 1 OSC (over the CWDM line)
LAD 1 OSC (over the DWDM line)
(all LAD modules except the LAD-2P
and LAD-2G)
L-AMP shelf (LAMPCoreEqpt) 1, 2 OSC (over the DWDM line ports 1,2)
LME-10G10 1 100G Port 1
OLA 1, 2 OSC (over the DWDM line ports 1,2)
(OLA-010, OLA-200, and OLA-201)
PME 1, 2 [XFP] Port 1, 2
(PME-216i and PME-412)
PSW-10G10 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 Ports 1−10
PSW-100G 1 100G Port 1
PSW-10G20 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, Ports 1−20
11, 12, 13, 14, 15, 16, 17,
18, 19, 20
PSW-618 1, 2, 3, 4, 5, 6 [XFP] Ports 1−6
TSW-10G10 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 Ports 1−10
WSS (all WSS modules) 1 OSC (over the DWDM line)
1.3 Limits and constraints

This section describes the limits and constraints that influence the design of DCN networks.
1.3.1 Maximum number of OSPF areas in a node

The Z-Series Z22, Z33, and Z77 nodes are limited to one OSPF area per node. Z-Series nodes do not
provide Area Border Router (ABR) functionality.
1.3.2 Maximum number of hosts and routes per NE/module type

Exceeding the upper routes limit in a Z-Series shelf can cause other processes, such as service
provisioning, to delay in varying degrees in its execution. For large networks with a significant number of
IP/OSPF routes, limiting the number of routes injected into the Z Series network will avoid excessive
network routes and host routes.
In a network with a large number of IP/OSPF routes, exceeding either or both of the network routes and
host routes supported by the shelf controller card can cause other processes, such as service provisioning,
to delay in varying degrees in its execution. Additionally, a node might lose its connectivity and report a
COMM Fail alarm when participating in a large network with several network routes and host routes that
exceeds the limit supported by a shelf controller card.
If you are using proxy ARP or static routing, there should be no affect unless you have 256 or more
Z-Series nodes in a single network.

1.3.3 Z77 shelves

Z77 Broadband Operating System Supervisor (BOSS/BOSS2) shelf controller cards support the following
number of network routes and host routes:
• BOSS: 256 network routes, 512 host routes
• BOSS2: 512 network routes, 768 host routes
1.3.4 Non-Z77 Z-Series shelves

Shelf management cards for non-Z77 Z-Series shelves — including the Z22, Z33 and L-AMP shelves —
provide up to 700 host routes combined for each shelf.
1.3.5 IP address restrictions

The Z‑Series DCN architecture is based on the ITU‑T G.7712 standard supporting IP‑based
communication with OSPF routing. All Z‑Series nodes require a unique IP address.
While the Z-Series routing tables can support larger numbers, as a planning rule you should not design an
OSPF area to exceed 126 remote network elements per gateway. This allows for a maximum network size
of 128 nodes with a dual-gateway configuration. If a network exceeds this number, you should design
additional gateways and OSPF areas.
Each Z-Series node in the network must have a unique IP address provisioned. When commissioning Z-
Series equipment the following IP addresses are not supported:
• 192.168.0.1 – 192.168.0.255 Subnet 255.255.255.0
• 192.168.1.0 – 192.168.1.255 Subnet 255.255.255.0
• 192.168.2.0 – 192.168.2.255 Subnet 255.255.255.0
• 192.168.3.0 – 192.168.3.255 Subnet 255.255.255.0
• 172.16.0.1 – 172.16.0.255 Subnet 255.255.255.0
• 169.254.0.1 – 169.254.254.254 Subnet 255.255.255.0
1.3.6 Latency (RTD)

A Z-Series shelf should not exceed a maximum of 300ms latency, though sub 100ms is desired.
1.3.7 Bandwidth required

All DCN communications channels are 100 Mbps maximum. The minimum gateway connection
bandwidth available through the router/LAN should be no less than 5 Mbps for small networks, and 10
Mbps for medium to large networks.
1.3.8 Security
The Z-Series uses OSPF as a routing protocol.
• The Z-Series supports configuring OSPF Authentication.
• Ciena recommends that you configure the DCN with OSPF Authentication per your corporate IT
policy.

• If you configure the Authentication fields (Simple Password or Cryptographic Auth) for an
interface, all neighboring nodes in the same network or all nodes with the same OSPF Area
• ID must use the same Authentication password/key to exchange routing information.
Important! — When you commission a new node on an authentication-enabled DCN

network, the new node will NOT have connectivity until you configure OSPF
Authentication on the new node.
1.4 Topology Discovery and Routing

Applicable Z-Series ports allow you to enable or disable Topology Discovery and Routing. When to
enable these settings depends on your network. Often both settings are either enabled or disabled, but they
work independently and do not have to be set to the same value.
• Routing: This specifically relates to IP connectivity through the nodes for the management
network. Enabling routing adds the interface to the OSPF interface table. If there is an OSPF
neighbor at the other end of the link, and the parameters match, they will form an OSPF
adjacency. Routing does not impact A‑to‑Z provisioning in Planet Operate. If you need to restrict
the number of IP routes within the Z‑Series management network, you can disable routing on
specific links. This will segment the IP network without breaking the physical topology for the
TESI paths. Do not enable Routing on ports that are fiber patched to another port in the same
shelf.
• Topology Discovery: Enables or disables physical topology discovery. This setting enables OSC-
like functionality between neighboring shelves. A reserved VLAN is used to transmit network
control and management information between nodes, mimicking the OSC that is present in LAD
and WSS spans.
By default, Routing and Topology Discovery are enabled when an NNI port is configured as 10GE WAN
or 10GE LAN. VLANs 4093 (Topology) and 4094 (Routing) are used to transmit topology and routing
information to adjacent nodes. Ciena recommends using the default values, but you can disable routing if
needed. This is the recommended setting when transporting 10G Ethernet over LAD or WSS DWDM
spans.
For a port configured as OTU2, OTU2e, or OTU1e, the system disables both Topology Discovery and
Routing by default. Ciena recommends this setting when transporting 10G Ethernet over LAD or WSS
DWDM spans.
Note: For the configuration, define the Design state for each interface on each module
and the rule for each. See the Z-Series DCN Planning Tool (Z-
Series_DCN_Planning_Tool.xlsm is available on the Ciena doc portal).
Starting in Z-Series CyOS Release 10.0, Ciena supports default routes for Z-Series node management.
This option allows DCN routers to propagate the default route 0.0.0.0/0 to Z-Series nodes. For details, see
Appendix A: Default Route for Node Management on page 42.
1.5 Simple planning rule of thumb

Taking the limits and constraints (described in section 1.3) into account, you can make a simple planning
rule of thumb:

• Plan one DCN routing link per direction and in a linear stub plan for two. OSC takes precedence
over other interfaces and the other interfaces should disable OSPF.
Only assign a /25 to an OSPF area.
1.6 DCN elements

The Z-Series has a simple DCN structure and does not have Interface addressing or sophisticated routing.
Segmentation is maintained by managing the physical connections and enabling routing on those
connections. Thus, classification of the connection type and respecting that classification in a working
network maintains the integrity of the DCN.
To aid design and documentation, node types are defined to aid IP addressing and connection types
assigned to categorize configuration procedures. The low-level design uses these node and connection
types to define the design and act as a reference.
1.6.1 Node-type definitions

This section provides node-type definitions and settings.
1.6.1.1 AMP
AMP indicates a line amplifier node.
Action: Assign and configure an IP address and OSPF area.
1.6.1.2 GNEn
The Gateway Network Element (GNE) is a shelf connected to a local router with access to the OSPF
backbone. The n signifies an ordinal number within the OSPF area. GNE1 is typically connected to
Router1 within the same subnet. Likewise, GNE2 is connected to Router2 within a different subnet. GNE1
and GNE2 provide access to RNEs within an area. A distinction is made between the GNEs so addressing
can be assigned from different subnets. There may be situations where more than two GNEs are required
in which case you will increment the GNE number. This allows a track of GNE connections per OSPF
area.
1.6.1.3 RNE
This is the shelf address of a non-gateway node. Typically, there is not any MGMT connection on the
backplane. The node may have iLAN or other connections to other shelves.
1.6.1.4 ROUTERn
ROUTERn is an external router that provides connectivity. An IP address and OSPF area assignment is
required. These form a pair of connections for a MGMT connection.
1.6.2 Connection Type definitions

1.6.2.1 IB
The Z-Series can use an in-band management channel of up to 100 Mbps in bandwidth. If the Z-Series
shelf is configured with a line module and the shelf does not have a LAD or WSS/AWG module, you can

use the in-band facility on the line modules to carry the Management VLANs by enabling the Routing
option on that interface.
The Routing information is carried within VLAN 4094, along with the other Management VLANs in a
100 Mbps channel formed between the peer in-band ports. Configure the remote line module the same as
the local port to ensure correct operation.
IB connections normally terminate on line module ports.
Action: Enable Routing on the interface.
1.6.2.2 iLAN
An iLAN connection is between modules, not the backplane; as such, you must configure two modules.
An IP address is not required. The system uses the shelf IP address for this connection type.
iLAN connections are typically connections between Z-Series shelves in the same site. For resilience,
typically two connections are required.
Action: Enable Routing on the interface.
1.6.2.3 MAN
A MAN connection is a connection to the management port on the backplane, or BTM within a Site, i.e.
an Intra-Site Link. If a connection is to a remote site, it is considered an out-of-band (OOB) link.
Action: Enable the interface for Routing.
1.6.2.4 OOB
Out-of-band connections to traffic ports; on Z-Series nodes, third-party equipment, or a rented circuit from
another network operator. The termination of an OOB link is typically on another site.
Action: Enable the interface for Routing and the identification (designation) of the Bearer circuit.
1.6.2.5 OSC
The Ethernet facility associated with the optical path, typically on a LAD or WSS module. In order to
supervise all network elements in the network, without relying on an external DCN, Z-Series systems
provide an Optical Supervisory Channel (OSC). Each Z-Series shelf connects to its neighbors via a
100 Mbps Ethernet channel carried in-band over the optical network.
The system provides an embedded OSC that is resident in each Z‑Series network element. These select Z‑
Series optical interfaces insert a 100 Mbps OSC on 1510 nm and provide transparent links between each Z-
Series NE in the network. The OSC is a separate channel that carries overhead information for network
management purposes that is added and dropped at each network element. The OSC does not affect
traffic.
Action: Enable the interface for Routing.
1.7 Scenarios
1.7.1 Standard scenarios
1.7.2 Dual GNE OSPF

This section describes standard scenarios with one OSPF area, two GNEs with All addressing with a
single /25 subnet assignment of IP address for RNE and GNE with examples of assigning addresses.

All new Z-Series networks are expected to have dual, redundant gateways to the management network.
Routers that are not collocated within the same office must provide dual gateways. The functionality of
dual gateways is intended to provide alternate management when a path to the primary gateway node is
unavailable, or in case of failure on the router or transport GNE. The transport GNE /30 IP address range
will be single homed to the directly connected local router interface, while the subtended subnet devices
will be dual homed to both router interfaces.
For Z-Series-to-Z-Series shelf communication, Ciena reserves VLANs 4090 through 4096 to pass
proprietary signaling. If using an offnet, or third-party system (i.e. OOB), you must be sure that the system
will allow this traffic for all of the management communications channels to work properly.
Two OSPF area network dual GNE – example

The following graphic shows an example of a DCN network.
Figure 1: DCN Network Example

Figure 1 shows an example of a network containing 2 OSPF

areas: area1 (indicated in orange) and area2 (in green).
The rectangles represent Z-Series nodes. The line types defined
in the DCN Key opposite describes interface types.
Follow these basic planning rules: plan one DCN routing link per direction and in a linear stub plan for
two. OSC takes precedence over other interfaces and disable OSPF on the other interfaces. Only assign a
/25 to an OSPF area.
The following steps were used to plan the network shown in Figure 1:
1. Use OSC channels to connect adjacent nodes. In the network example, these are links with an
ID of >100, with solid lines.
2. If an OSC channel does not exist between adjacent nodes, select a traffic channel to act as a
DCN link. Document the selected channels as to which interfaces are used on what nodes.
On the node, enable Routing on the intended interface.
3. Any site with more than a single shelf may be connected using the iLAN ports on the CEMi
module (or similar). An A and B route is required as a single provisioned module could cause
a single point of fail.
4. Where access to a Router is available, make an OSPF connection to the router, and connect to
the rear chassis connection. Selection of the site may depend on planning requirements for the
segmentation of networks into OSPF areas.
5. Line amplifier sites are also included as an AMP type connection as IP addressing is required.
6. After completing steps 1 through 5, you can assign IP addresses.
After applying these planning rules to the network, record the results in a DCN planning document.
Z-Series DCN planning tool

In the network example shown in Figure 1, some Excel functions were used to automate the addressing of
node types and a classification of connection types used so that a standard provisioning configuration
could be used.
The Z-Series DCN Planning Tool (Z-Series_DCN_Planning_Tool.xlsm is available on the Ciena
doc portal) is an Excel spreadsheet used to record each device and each connection on each device as a
line in the worksheet. Upon entering the Location, Addressing, and Connection sections, the Calculation
section returns IP addressing based on the Node Type.
Do not edit columns H and L through P (greyed on the headings). Columns Q, R, and S are freeform and
available to use a filter or additional markers. Column L is a counter, it will count the number of rows that
any filter selects for viewing (useful to count node types or numbers of GNEs in certain OSPF areas).
The format for the Z-Series DCN Planning Tool, as shown in Figure 2, demonstrates the assignment of IP
addressing and interfaces. The exact format used depends on your local processes.

Assign IP addresses to the Nodes, AMPs, and Routers. This is done from a /25 subnet containing 128 IP
addresses. If the number of IP addresses exceeds 128, you can assign additional address space.
Interfaces are marked with a type to aid classification and the connection points noted. The following
shows the format used for the interface:
<nodeHostname>-<Interface ID>
You can then filter the list to provide a provisioning template per node.
For each node:
• Assign an OSPF area. (This is shelf wide and assigned to the interfaces at creation.)
• Assign a shelf IP address along with a subnet mask.
• Connections are required to adjacent nodes—as in the design.
• At GNEs, connections are required to ABR OSPF routers with the connected interface in the same
OSPF area as the Z-Series node.
• An example output of the described in the Z-Series DCN Planning Tool spreadsheet.
Figure 2: Z-Series DCN Planning Tool – Output Example

1.7.2.1 Configuration per node

This section describes and provides examples of per node configurations using the Z-Series DCN
Planning Tool spreadsheet.
nodeA_1
Figure 3 shows an example configuration for shelf nodeA_1.
Figure 3: Shelf/Site Configuration Example
Figure 4 isolates the nodeA_1 connections.
Figure 4: Shelf Connections Example 1
Note that there is not a DCN connection between nodeA_1 (OSPF area1) and nodeZ (OSPF area2). You
must disable Routing on ALL links between these sites.
Shelf IP address is 10.50.50.2.
Link 1 to nodeB is an OSC link. Assume that the DCN routing is enabled on a WSS or LAD module—in
this example nodeA_1-ETH-1-6-1.
Link 100 is the connection to the local router (connection type MAN). OSPF must be enabled on the
Router and the OSPF area for the interface connected to nodeA_1 set the same as that node, in this case
OSPF area1. The physical connection from nodeA_1 -REFAC-1-1 uses in the rear management
connection and on the router a connection to a Cisco 1 Gigabit interface - Router1atA-gi0/20.

Links 901 and 902 form a ring between the iLAN ports of the two shelves to provide intra-site
communications. As the iLAN ports are located on single modules and not a protected interface, the
service is made resilient by providing a path from each of two modules.
Second shelf nodeA_2

Figure 5 and Figure 6 show the setup of the second shelf, nodeA_2.
nodeA_1
area1
10.50.50.2 /30
901 902
nodeA_2
area1
10.10.0.2
nodeD
area1
10.10.0.4
The shelf IP address is 10.10.0.2.

In this example, links 901 and 902 between the iLAN ports are connected between the shelves as shown in
the connections nodeA_1-1-A-ILAN1 to nodeA_2-1-A-ILAN2 for iLAN connection A and nodeA_1-1-B-
ILAN2 to nodeA_2-1-B-ILAN1 for iLAN connection B. Then, enable Routing for ALL of the iLAN
ports.
For the OSC link, link 4, to nodeD, Routing must be enabled locally on the interface of nodeA_2-ETH-1-
6-1 (a LAD-8 module).

DCN assignment at nodeD
Figure 7: DCN Assignment for nodeD
nodeA_2
area1
10.10.0.2
nodeE 5 nodeD nodeC

area1 area1
3 area1
6
10.10.0.5 10.10.0.4 10.10.0.3
Figure 8: Example of area1
The shelf IP address is assign as 10.10.0.4. The OSPF area is area1.

There are three OSC type links:
Link 8 nodeD-ETH-1-6-1 LAD-8
This interface has the Routing option enabled on the Ethernet interface associated with the LAD-8 OSC
channel.
IB connection
Figure 8 shows the basic planning rule of one DCN link for each direction. However, as there is a linear
link to the node, a second DCN connection is required for resilience (in case the OSC channel fails).

Figure 9: IB Connection for Link 6
Link 6 is assigned an IB connection type, which uses nodeD_ETH-1-1-1 locally.

To enable this DCN connection, enable Routing on the 10G WAN/LAN interface, as the Z-Series DCN
Planning Tool dictates that this is a DCN connection by design.
As no other traffic interface is marked as an IB connection type, then ALL other traffic interfaces must be
disabled by inference.
For the nodeD example, Routing is required on the traffic interface nodeD-ETH-1-1-1 ONLY.
1.7.2.2 OSPF area access
Figure 10: OSPF Area Access Example 1
In the example in Figure 10, nodeZ, nodeY, nodeX, and nodeW are all in area2.
Configurations for these nodes are similar to those in OSPF area1, except the OSPF area needs to be set to
“2.” Additionally, since there is a separate OSPF area, an OSPF connection back to the OSPF routers
providing ABR functionality is required. In the example in Figure 10, links 200 and 201 provide that
connectivity.
These links are assigned the Connection type of MAN. The physical connections required are from the Z-
Series backplane management port to a port on the local router/switch. In the example, link 200 is
connected from Router1atA-gi0/2 to nodeZ-REFAC-1-1 and link 201 Router1atB-gi0/21 to nodeY-
REFAC-1-1. These two connections, as with links 101 and 102 for area1, provide a resilient service for
accessing the area.

Figure 11 shows this example in the Z-Series DCN Planning Tool spreadsheet.
Figure 11: OSPF Area Access Example 2
1.7.2.3 OOB connections

There may be a requirement to connect non-adjacent OSPF areas. This can be through a traffic circuit
carried by Z-Series equipment, or it may be carried via third-party equipment or a rented circuit from
another network operator.
In this case, the circuit must reserve VLANs 4090−4094 for use by the Z-Series DCN.
The circuit used must have a circuit designation (name) as any other customer circuit requires. This circuit
designation is then used to identify the service being used no matter the medium carrying that service.

Figure 12: OOB Connection Example 1
In the example shown in Figure 12, the OOB connections are identified as link 45 and link 46. Note that
these IDs are used on the spreadsheet and may have no significance outside of this example.
Figure 13: OOB Connections Example 2
The two OOB connections provide connectivity for nodes K, L, M, N, and AMP22_1 to OSPF area 2 at
nodeW and nodeX. These two connections provide resilience. Make the physical connection to the
management interface on the rear of the chassis to provide resilience in the case of module failure.

1.8 Ingress and egress paths

The ingress and egress paths of the packets to and from the management platform may take different
routes as they are based on the lowest cost. When using “Tracepath“ or “Ping,” keep in mind that the
routes may be asymmetrical.
1.9 Workaround
If you create a workaround configuration, you should provide an explanation for the workaround; the
issue, the reason for the issue, the workaround and what should have been the correct standard solution, if
one was possible.
1.10 Configuration
This should be viewed in reference to the High Level Design (HLD) and section 1.7 Scenarios starting on
page 16. Ideally, there should be a Low Level Design (LLD) document that details which role each
Connection type was assigned for the DCN and details the addresses to be used and the settings used for
the DCN (i.e., Routing enabled).
1.10.1 Admin State provisioning

Planet Operate provides the following Admin State options on Transport Resources sub-tabs:
Admin State Provisioning
• Unlocked: The object is unlocked and allowed to go into service.

• Automatic In-Service: Automatic in-service provisioning. Alarm reporting is inhibited on a per managed-
object basis to allow sufficient time for service provider and customer testing or other maintenance
activities in an "alarm free" state. This state automatically transitions to Unlocked when all qualifying faults
have cleared and the provisioned soak time has expired. The soak time only starts when all qualifying
faults have cleared, and restarts if a qualifying fault occurs prior to its expiration.
• Locked for Maint: Locked for maintenance. Alarms for the managed object are suppressed, but
otherwise the managed object is allowed to function normally. This enables service provider and customer
testing or other maintenance activities in an alarm free state. When the admin state is set to Locked for
Maint, Planet Operate does not display alarms.
• Locked to Disable: Locked to disable service. The managed object is functionally disabled and all alarms
are suppressed. The system suspends traffic for the slot, card, port, and transceiver. Use this
administrative state, for example, when changing a signal type for a port.
Important! — The "Locked to Disable" administrative state is service affecting with

traffic suspended. Additionally, the system does not display alarms.

1.10.2 OSPF
The Z‑Series platform uses Open Shortest Path First (OSPF), a link-state routing protocol, for node-to-
node communication. Nodes send Link State Announcements (LSAs) to all other nodes within the same
hierarchical area. Based on the OSPF link-state data gathered, the nodes use a Shortest Path First (SPF)
algorithm to calculate the shortest path to each node.
From the Planet Operate main menu, select Node > OSPF Configuration to view or modify OSPF
information. Figure 1 shows an example of the OSPF Configuration dialog box. Node-level settings
display in the Common Settings area in the top half of the window and include the ability to
enable/disable OSPF and configure OSPF Area IDs. Card/port level settings display in the Interface
Settings area in the bottom half of the window and include the ability to configure OSPF parameters for
individual line cards and ports.
Figure 14: OSPF Configuration Dialog Box Example
1.10.2.1 OSPF area ID

You can divide an OSPF network into logical sub-domains referred to as areas. Use the OSPF Area ID to
define logical areas of the network. Creating OSPF areas reduces the size of the topological database
maintained by the node and the number of routes to propagate. Nodes within the same area share the same
information and have identical topological databases.
The area ID of 0 is the backbone area.
The OSPF Area ID is a 32‑bit integer set to 0 or 0.0.0.0 (where each 0 represents a value in 1 of 4 bytes).
This value indicates the backbone area. Each of the 4 bytes can have value 0 to 255.

1.10.2.2 IP interface
To view an applicable Z‑Series module IP Interface or set the interface Admin State, follow this
procedure.
Step Procedure
1 From the Network view tab, double-click the intended shelf to open the Front and Rear Panel tabs.
2 From the main menu, select Node > OSPF Configuration to open the OSPF Configuration dialog box.
3 In the Interface Settings area, click the module IP Interface (row) to view related information in the lower
panel and/or to set the Admin State or OSPF Area ID.
If you change the Admin State or OSPF Area ID, click Apply.
1.10.2.3 OSPF interface parameters

The Z-Series module OSPF interface contains the following key parameters:
• Hello Interval: This field shows the time in seconds that an OSPF hello packet transmission. The
configured value must be consistent with all nodes in the same network or area ID. The range is 1
to 65535 seconds. The default is 10 seconds.
• Retransmit Interval: This field shows the time to wait before retransmitting a packet when there
has not been an acknowledgment. The range is 0 to 3600 seconds. The default is 5 seconds.
• Router Dead Interval: This field shows the time in seconds to wait before declaring a neighbor
down. By default, the dead timer interval is four times the hello interval. The configured value
should be consistent with all nodes in the same network or area ID. The default is 40 seconds.
• Authentication Type: The authentication type is configurable on per-area basis. Select one of the
following options:
• Null Authentication: Indicates that no authentication is used. You can also use this option to
disable authentication on the interface. The default is Null Authentication.
• Simple Password: Select this option to use a simple password authentication for an area. Use the
Authentication Key field to assign the password. The password can be up to 8 upper or lower-case
alphanumeric characters.
• Cryptographic Auth: Select this option to assign an encryption key based on the Message Digest
type 5 (MD5) encryption standard. Use the Authentication Key field to assign the MD5 key. The
MD5 key can be up to 16 upper or lower-case alphanumeric characters. There is no default value.
1.10.3 IB Connection type

The In-Band Connection type uses the either the 10G WAN/LAN Termination type or the OTN
termination type Line to piggy-back the DCN channel either using a dedicated 100Mbs service and
assigned VLANs, for the WAN/LAN or a dedicated GCC channel.
1.10.3.1 10G WAN/LAN line
The port can be identified as being a 10G LAN port by the encapsulation shown in the Planet Operate
Transport Resources > Physical Resources tab.
The example in Figure 15 shows that Port 1-1-1 has an XFP fitted and configured as a 10GE/OTU2 Fiber
port. In turn, the Fiber Port XAUI has been formatted as a 10G Ethernet Term (see panel 1 in Figure 15).
Note: By default, the 10G WAN/LAN ports have the Routing feature enabled. This must be
disabled if Routing and therefore a DCN connection is NOT required.

Figure 15: Transport Resources > Physical Resources Tab Example
If a LAD or WSS module OSC and the traffic-carrying module interfaces are fiber patched to a LAD or
WSS/AWG module to provide the Z-Series shelf comms, you have no requirement to use the line modules
interface for DCN communication and the Routing option should be disabled.
Figure 16: Routing Parameter
To configure the Routing feature for this configuration example, follow this procedure.
Step Procedure
2 From the main menu, select Node > Transport Resources to open the Transport Resources tab.
3 In the Physical Resources sub-tab, double-click the Line module. Right-click the XFP slot and select
Expand Subtree to expand the view. Click the 10G Ethernet Term level to view the General sub-tab.
4

Step Procedure
In the General sub-tab, do the following:
A. From the Admin State list, select the appropriate administrative state. For details, see section 1.10.1
Admin State provisioning on page 26.
B. From the Routing list, select Enabled or Disabled. If the FPP type is provisioned as NNI, Routing is
enabled by default. Check with your Low Level Design to determine if the Routing parameter needs to
be enabled, otherwise the Routing parameter should be disabled.
C. Click Apply.
1.10.3.2 OTN Line - GCC

Some Z-Series line modules can use OTN as the interface protocol (as opposed to 10G WAN/LAN).
See the example in the following procedure for an OTN module – LME-10G10d.
Follow this procedure to provision the OTN line GCC.
Step Procedure
2 From the main menu, select Node > Transport Resources to open the Transport Resources tab.
3 In the Physical Resources sub-tab, double-click the Line module.
The Line module displays in the Equipment Tree and in Physical Resources, the Physical Resources subtree
displays a OTU GCC0 level to provision Topology Discovery and Routing.
Right-click the CFP slot and select Expand Subtree to expand the view. Click the OTU GCC0 level to view
the General sub-tab.
4 In the General sub-tab, do the following:

A. From the Admin State list, select the appropriate administrative state. For details, see section 1.10.1
Admin State provisioning on page 26.
B. Note: To configure the Auto-In-Service Soak Time, set the Admin. State to Automatic In-Service. The
soak period default is 00:05:00 minutes.
C. In the Description text box, accept the default or enter a new description.
D. From the Topology Discovery list, select Enabled or Disabled. The default is Disabled.
E. From the Routing list, select Enabled or Disabled. The default is Enabled.
F. Click Apply.

1.10.4 MAN Connection Type

A Management Access Network (MAN) connection is typically terminated on at least one MGMT port.
The MGMT port is located on the rear of the Z-Series shelf to provide a connection to local routers or
other devices within the curtilage of the site. Enable OSPF for a Z22 or Z33 shelf MGMT port.
1.10.5 Enable Routing for a Z22 or Z33 shelf

To enable routing on a Z22 or Z33 shelf, follow this procedure.
Step Procedure
1 From the Network Tree or the Network view tab, double-click the intended Z22 or Z33 node to open the
Front Panel tab.
2 In the equipment tree, click the Shelf.
3 In the toolbox area, click the Ports tool tab.
(From the main menu, select Tools > Ports to display the Ports tab.)
4 In the Ports tool tab, select the MGMT port and click the Details button to open the Port Information and
Configuration dialog box.
5
In the Port Information and Configuration dialog box, do the following:

A. In the left-side panel, click Port Configuration.
B. In the right-side panel, click Routing.
C. From the Enter New Value drop-down list, select Enabled.
D. Click Apply

1.10.6 Enable OSPF for a Z77 shelf MGMT port

Step Procedure
1 In the equipment tree, double-click the Rear Linecards level. Double-click the Slot 1: BTM Slot level.
Click the BOSS Termination Module.
2 In the toolbox area, click the Ports tool tab.
(From the main menu, select Tools > Ports to display the Ports tab.)
3 In the Ports tool tab, do the following:

A. In the right-side panel, select (click) the MGMT Gigabit Ethernet Port (or an iLAN GbE Port depending
on your configuration).
B. Click the Details button to open the Port Information and Configuration dialog box.
4
In the Port Information and Configuration dialog box, do the following:

A. In the left-side panel, click Port Configuration.
B. In the right-side panel, click Routing.
C. From the Enter New Value drop-down list, select Enabled.
D. Click Apply.

1.11 Using the Owner field to identify DCN Connection Type

as carrying Routing
Z-Series OSC and line ports provide the distant end shelf with their termination point information to aid in
fault management and identification of connections. Ethernet ports on the Z-Series shelf, BOSS/BOSS2
cards, and CEMi cards do not provide this capability and can make working on these circuits challenging.
Use this format:
<type >_ <destination>_<destination port>.[OOB Circuit Name]
• Where type is the Connection type, which is IB, ILAN, MAN, OOB, or OSC.
• destination is the remote terminal device, for example, the Z-Series shelf or Router Hostname
terminating the connection, not the equipment transporting the circuit.
• destination port is the termination port of the remote device.
• OOB Circuit Name is (only appended if OOB type) the designation given to the circuit
transporting the DCN connection through either the Z-Series network or a third-party network. As
the DCN connection will consume network bandwidth, treat the circuit as any other traffic circuit.
Document and track it the same way.
1.11.1 MGMT ports

MGMT ports on the Z-Series shelf backplane typically terminate MAN or OOB connections.
Consider MAN connections as intra-site and OOB connections as inter-site.
MAN connections
For Management Access Network (MAN) connections the MGMT port for the shelf has an “Owner” field
where the value can be <= 80 characters. Use this field to identify the DCN type and destination, allowing
for easier troubleshooting.
Figure 17: MAN Connection
MAN_z22_Router-Gi0/23 (connected to the MGMT port)

MAN_z22_REFAC-1-1
The example above shows the connection within the site where it is connected to shelf “z22.” On that
shelf, the connection is terminated on the MGMT port (REFAC-1-1). The Owner field on that port is set
to the shelf originating the cct (shown in red italics).

Figure 18: Port Information & Configuration Screen
OOB connection
WASHDC12O0Y
OOB cct
MXNE12345678
WASHDC12O0Y-REFAC-1-1
z22-REFAC-1-1
z22
Figure 19: OOB Connection
OOB_WASHDC12O0Y_REFAC-1-1.MXNE12345678 (on REFAC-1-1 owner at z22)

OOB_z22_REFAC-1-1.MXNE12345678 (on HYVLMDHYO0Y in the owner field for REFAC-1-1)
In this OOB connection example, the connection is to a transport circuit “MXNE12345678” which is
connected to the rear MGMT port, REFAC-1-1, at WASHDC12O0Y. At the WASHDC1200Y node, enter
the port connected at this shelf.

1.11.2 LAN/WAN and OTN ports

The LAN/WAN and OTN ports typically have IB connections.
Optionally, you can use the Description field interface to mark the use of Routing for the DCN as shown
in Figure 20. You can determine the destination from the other fields.
Figure 20: Example of Using the Description Field (Transport Resources / General Tab)
In this example of the Transport Resources General tab, the Facility ETH-1-1 / 10G Ethernet Termination,
the Description field has the addition of “With routing” that identifies the requirement to enable Routing
on this port.
Alternatively, you can use the Ports tool to display the Owner field as shown in Figure 21.
Figure 21: Owner Field

1.11.3 OSC Ports

Optical Supervisory Channel (OSC) ports typically have OSC connections like the LAN ports on the shelf.
Figure 22: OSC Ports
The OTS facility has a management port associated with it. Use this and the General tab to identify the
port as being used for routing as shown in Figure 22.
1.12 Checks
When provisioning a new node, check the node for reachability.
Check for reachability with these options:
• Use Planet Operate to select the node and open the OSPF Information tab
• Ping from another Z-Series node
• Traceroute from another Z-Series node
• Route on the node under test
Ciena recommends that you record the ping latency and if possible, the tracepath—this provides a baseline
for future troubleshooting. Additionally, ping/trace on adjacent nodes is useful, as would a check of the
routes on both GNEs to ensure the network has resolved correctly.
1.12.1 OSPF Information tab

From the Planet Operate Network view tab, select a node. Next, from the main menu, select Tools >
OSPF Information to display the three sub-tabs of OSPF information related to the node selected:
• Neighbors
• Routes
• ARP

The Neighbors sub-tab provides OSPF information, such as IP address and neighbor State, on adjacent
nodes for the selected node.
Figure 23: OSPF Information – Neighbors Tab
The State field shows “Fully adjacent” which means that OSPF has exchanged Hello Packet and that Link
State Adverts have been received, that is, an OSPF session has been established to that neighbor. The
ifindex should match the interfaces configured for routing. If there are unexpected interfaces or interfaces
missing from the configuration on this node and/or adjacent nodes, it requires a thorough review.
The Routes sub-tab displays a host route table as shown in Figure 24.
Figure 24: OSPF Information – Routers Tab

The ARP (Address Resolution Protocol) sub-tab displays the Host ARP table as shown in the next figure.
Figure 25: OSPF Information – ARP Tab

Use the Host and ARP tables to check reachable nodes within the network. This displays the Planet
Operate Host system IP address.
1.12.2 Ping
Typically, when adding a node, the GNE will be present. Therefore, use this as a fixed point in the
network to check reachability of a node from the GNE within an OSPF area. Reachability between OSPF
areas is not required for the operation of Z-Series equipment.
Planet Operate does not provide tools to use ping or traceroute commands. Use the CLI for access as
described in the following procedure.
Step Procedure
1 Telnet or SSH into a GNE for the OSPF area of the node under test.
2 At the CyCli []> prompt type: exec ping hostname <IP address>
Use the IP address of the node under test.
3 The below shows a good Ping echo – 1 packet Transmitted and 1 packet received
4 The Round-Trip delay (0.627 ms) is the time taken for the echo to return to the sender. Long round trip delay
can be indicative of network problems e.g. busy nodes updating routing tables.
Ciena recommends that you record round trip delays as a baseline for future troubleshooting.
Note: You may possibly ping from third-party equipment depending on firewall and
network connectivity. Although a useful tool, it is outside of the scope of this document
to describe this function due to the various configurations of systems and networks.
1.12.3 Traceroute
Typically, when adding a node, the GNE will be present. Therefore, use this as a fixed point in the
network to check reachability of a node from the GNE within an OSPF Area. Reachability between OSPF
areas is not required for the operation of Z-Series equipment.
Planet Operate does not provide tools to use ping or traceroute commands. Use the CLI for access as
described in the following procedure.
Step Procedure
1 Telnet or SSH into a GNE for the OSPF area of the node under test.
2 At the CyCli []> prompt type: exec other command “traceroute <IP address>”
Use the IP address of the node under test. You must enter the quote marks “ “ as they are part of the
command string.
Figure 26 shows a good ping echo—1 packet Transmitted and 1 packet received. You will see an entry for
each node the packet passes through.

Figure 26: Valid CLI Ping Example
You can use traceroute when a node is not reachable or if a ping fails to locate the problem. When the last
reachable node is identified, Telnet or SSH into that node and check the configuration to determine why
the next expected node is not reachable.
1.12.4 Route
Use the CLI route command when logged into the CLI and want to view the routing table. This CLI
routing table should match the Planet Operate host Routes tab on OSPF Information tab.
Use the CLI route command locally via the craft port or remotely by Telnet or SSH.
Step Procedure
1 Access the CLI of the node under test.
2 At the CyCli []> prompt type: exec route
Figure 27 shows the output of the CLI route command.
Figure 27: CLI Route Command Example

1.13 Conformity
Perform a conformity test to ensure that a configuration meets a design element. For example, the node or
interface is configured as one of the NE roles and adheres to the planning rules, if not the configuration
should generate an exception.
1.14 Exception handling

Note that there may be exceptions to the planning rules due to local constraints or historic factors.
Document the exceptions. Any configurations not to standard type should be included in the configuration
guide with the caveat that they have particular use cases and require approval for use.
Include these exceptions in your high-level design process.
1.15 Sources of error

Use traceroute, ping, and routing tables to pin point any areas of error.
1.15.1 Incorrect configurations

An incorrect configuration, such as incorrect security settings, incorrect OSPF area settings can cause the
DCN to fail. Perform a check of the present configuration against the planning documentation and make
corrections as necessary. For example, examine Loss of Comms, no ping response, or traceroute does not
reach the target node.
1.15.2 Route flap

A route flap indicates an interface is intermittently failing within a short period, typically a few seconds.
This causes the OSPF protocol to send updates continuously on the change in state of the link and
attempts to resolve a new network state map. This flapping will typically manifest itself as nodes in and
out of comms, slow comms, and a long ping round trip times.
1.15.3 Backhaul DCN

Some issues may not be related to the Z-Series portion of the DCN network. Issues may pertain to the
backhaul network, from the local router at the GNE, to the NMS platform. These problems can manifest
as loss of comms, slow comms, or loss of nodes in the NMS.
You can typically isolate a problem on the backhaul network by performing ping and traceroute
commands to points in the Z-Series network from the GNE. Good results toward the Z-Series node and
bad ping and traceroutes back to the NMS can indicate a backhaul issue.
1.15.4 Route list exhaustion

The primary function of the Z-Series is to transport customer traffic. The Z-Series has routing capability,
but this was designed to operate in a controlled environment. Therefore, it is limited in its ability to store
routes when compared to commercially available routers.
The Z-Series will discard older routes when the route list is filled newer routes. This will cause new link
state adverts to be sent updating other nodes, causing churn on those nodes. Due to churning, some nodes
become unreachable, as they do not have an ingress or egress route—referred to as convergence.

Ping fail, traceroute missing target node, and loss of comms are all symptoms of route list exhaustion. As
well as the failures, you can see slow comms, log round-trip delay times on pings and perhaps traceroute
expiration if circuitous routes are used.
1.15.5 Transmission errors

Transmission errors on the bearer circuits can also cause DCN issues causing packet loss. If you have
slow comms or loss of comms, the bearers along the route may be in error. Using the performance metrics
of the bearer circuits can help localize the cause of the errors.
1.15.6 Routing loops

OSPF is unlikely to form a routing loop if it is running autonomously within an OSPF area. Because
OSPF is an SPF algorithm user and a Link State database is kept on each node, loops only exist when
converging or a bug in the code. However, if redistribution takes place or static routes added, problems
may occur.
If steps are not taken to prevent loops arising from summary link state advertisements (LSAs) or other
networks bridging areas, the backbone network with may cause problems.

Appendix A: Default Route for
Node Management
Starting in Release 10.0.02 Ciena supports default routes for Z-Series node management. This feature
allows DCN routers to propagate a default route 0.0.0.0/0 to Z-Series nodes. This default route, often
termed the “route of last resort,” is the last route a router selects when there are no specific routes that
match an IP packet's intended destination.
1.16 Overview
A Z-Series node can discover the topology of your DCN network using the OSPF routing protocol, and
can construct an L3 routing table suitable for forwarding DCN traffic within a single OSPF area. Because
it supports only a single OSPF area, it can not serve as an Area Border Router (ABR).
• For OSPF configurations without an ABR, a Gateway Network Element (GNE) node within the
OSPF area connects to a router outside of the area. You can configure the GNE to proxy the ARP
protocol for each of the other non-gateway (RNE) OSPF nodes that the GNE has discovered. This
allows a connected router outside of the area to correctly forward RNE-bound traffic to the GNE,
where it is then appropriately routed within the area. For a Z-Series GNE node, this “Proxy ARP”
function can be enabled on its MGMT Ethernet interface.
• For OSPF configurations with one or more ABR nodes residing within the OSPF area, an ABR
node can route traffic between the nodes of the area and any external portions of the DCN
network to which the ABR node is also connected. The Z-Series GNE node's MGMT Ethernet
interface connects to the ABR node, but with the interface enabled for “Routing” instead of for
“Proxy ARP.” In this OSPF configuration, the ABR is able to inject a default route via this
interface into the OSPF area.
Feature Description
Role of the OSPF ABR
An ABR node can advertise network routes to destinations external to an OSPF area via the OSPF
protocol's Link State Advertisement (LSA) entries of Type 5 (“external”). These LSAs are redistributed
by each node in the OSPF area, allowing them to propagate to all of the nodes of the area. You can

configure the ABR to use this mechanism to advertise a network route of last resort, or “default route.” It
does this by injecting a Type 5 LSA with Link State ID and Network Mask fields having values of
“0.0.0.0”.
L3 Route Table Construction
A node running the OSPF protocol forms “adjacencies” with each of its discovered neighbors, during
which it exchanges a copy of its LSA database; the database contains a record of each LSA originated by
itself or by another neighbor. This discovery process converges with all of the nodes in the OSPF area
sharing an identical LSA database.
As updates to the LSA database are propagated, each node runs a routing computation on that database
using a Shortest Path First (SPF) algorithm, to give a node-specific L3 routing table that presents a
consistent routing solution throughout the OSPF area. The output of this SPF computation are a series of
commands to add, delete, or update an advertised route in the node's L3 routing table.
Z-Series GNE Node Operation
For a Z-Series node serving in a GNE role, its Primary Gateway address must be provisioned to a non-
zero IP address, which should be the address of the router connected to its MGMT Ethernet interface.
Whenever the operational state of this interface is “In-Service” (link is UP), the GNE constructs a static
default route against that interface with the Primary Gateway as the ‘next hop” destination of that route.
If the MGMT Ethernet interface's operational state is “Out-Of-Service” (link is DOWN), the GNE
attempts to construct a suitable alternate default route from among the advertised network routes
discovered through the OSPF protocol. It selects the best (lowest cost) route that can “reach” the
provisioned Primary Gateway address. Hence, a Z-Series GNE node uses a static default route, and as a
fallback, an alternate “dynamic” default route.
Z-Series RNE Node Operation
Release 10.0.02 introduces a change in how the L3 routing table is constructed for those Z-Series nodes
operating in the RNE role. Prior to release 10.0.02, all commands output by OSPF's SPF computation
referencing a “default route” were ignored. Hence, any default routes advertised via the Type 5 LSAs
injected by an ABR, although correctly accepted and redistributed by the Z-Series RNE node, would not
be applied by the node's L3 routing table.
With Release 10.0.02, this is still the behavior for a Z-Series node operating in the GNE role; however, in
the RNE role, the Z-Series node will now also apply default route commands from OSPF's SPF
computation to the node's L3 routing table.
Provisioning a Z-Series Node for a GNE or RNE Role
The Z-Series node's GNE/RNE role is provisioned by the value of the node's Primary Gateway IP address.
• Setting this attribute to the IP address of the connected router places the node in the GNE role.
• Setting this attribute to a value of zero (0.0.0.0) places it in the RNE role.
Note that setting an RNE node's Primary Gateway IP address to a value of zero (0.0.0.0) is only
appropriate in network configurations where an ABR router is advertising a default route into the OSPF
area. In this configuration, the RNE node's MGMT port must be configured with the “Proxy ARP”,
“Routing” and “Report Faults” attributes set to “Disabled”, and no Ethernet connection should be made to
that port.
In contrast, network configurations that do not use an ABR router, and where the head-end GNE node is
instead configured to use the Proxy ARP protocol, all RNE nodes must be configured with a valid, non-

zero Primary Gateway IP address, just as is the head-end GNE node. Without the RNE nodes so
configured, the Proxy ARP function will not work.
You can set the Primary Gateway IP address at the time of the node's commissioning via CyCT. With
Release 10.0.02, you can also set the attribute through the CYOS CLI by configuring the corresponding
attribute of the node's NE-ROOT object.
A note of caution when modifying the NE-ROOT object: This object includes three related attributes that
together serve to establish a Z-Series node's IP identity on the DCN network:
• dcnIpAddress – the node's IP address on the DCN network
• dcnIpSubnetMask – a mask identifying the “network” portion of that IP address
• gwIpAddress – the Primary Gateway IP address
If these attributes are reconfigured remotely (over the DCN) in a series of separate transactions, the node's
IP identity will be left in an inconsistent state, and all DCN communications to the node will be lost. For
this reason, Ciena recommends that you reconfigure all three attributes in a single transaction, that is,
naming all of these attributes in just one CYOS CLI command. The form of this command should be:
CyCli []> config equip node NE-ROOT dcnIpAddress <IP address>
dcnIpSubnetMask <IP mask> gwIpAddress <IP address>
For example, to configure the node for the GNE role:
CyCli []> config equip node NE-ROOT dcnIpAddress 10.71.10.2
dcnIpSubnetMask 255.255.255.128 gwIpAddress 10.71.10.1
To configure the node for the RNE role:
CyCli []> config equip node NE-ROOT dcnIpAddress 10.71.10.5
dcnIpSubnetMask 255.255.255.128 gwIpAddress 0.0.0.0
1.16.1 Caution on Provisioning a Z-Series Node's DCN Attributes Remotely

As mentioned above, Release 10.0.02's CLI function allows you to set the configuration of a node's DCN
IP identity remotely, over the DCN itself. With this function comes the responsibility to exercise due care,
as a mistake made in an attribute value of the “config equip node NE-ROOT” command can result in the
node losing its connection to the DCN network.
Such a “Communication Fail” fault can not be recovered remotely. It can only be recovered when a local
operator re-configures these attributes via CYCT, and then executes a Software Restart of the node's
common control module.

Z-Series
Packet-Optical Transport Networking Platform
Z-Series Data Communications Network

Planning and Configuration Reference Guide
Copyright © 2018 Ciena ® Corporation — All rights reserved.

Publication: 450-3708-011
Issue 2.0
Document release date: May 2018
CONTACT CIENA
For additional information, office locations, and phone numbers, visit the Ciena web site
at www.ciena.com.

450-3708-011 - Z-Series - DCN - Planning-And - Configuration - 2.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

450-3708-011 - Z-Series - DCN - Planning-And - Configuration - 2.0

Uploaded by

Copyright:

Available Formats

Ciena Z-Series

Packet-Optical Transport Networking Platform

Z-Series Data Communications Network

450-3708-011 – Standard Issue 2.0

Copyright© 2018 Ciena® Corporation. All Rights Reserved.

Legal Notices, Copyright, and Trademark

Copyright© 2018 Ciena® Corporation – All Rights Reserved

Important! — Information that must be seriously considered.

Note: Special suggestions, advice, or information that should be seriously considered.

Safety Symbols and Labels

Laser Equipment Present

Electrostatic Discharge (ESD) Sensitive Equipment

1.8 Ingress and egress paths............................................................................................................ 26

1.1 Equipment DCN ports, connection types, and protocols

1.1.2 Common Equipment Module (CEMi)

1.1.3 LAD modules

Several versions of the optical LAD modules are available:

1.1.3.1 LAD OSC specifications

1.1.4 Wavelength Selective Switch (WSS) modules

1.1.5 L-AMP shelf

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 10

1.1.6 Z-Series line modules

1.2 Routing feature − default settings

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 11

Logical Ports with

1.3 Limits and constraints

1.3.1 Maximum number of OSPF areas in a node

1.3.2 Maximum number of hosts and routes per NE/module type

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 12

1.3.3 Z77 shelves

1.3.4 Non-Z77 Z-Series shelves

1.3.5 IP address restrictions

1.3.6 Latency (RTD)

1.3.7 Bandwidth required

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 13

Important! — When you commission a new node on an authentication-enabled DCN

1.4 Topology Discovery and Routing

1.5 Simple planning rule of thumb

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 14

1.6 DCN elements

1.6.1 Node-type definitions

1.6.2 Connection Type definitions

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 15

1.7.2 Dual GNE OSPF

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 16

Two OSPF area network dual GNE – example

Figure 1: DCN Network Example

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 17

Figure 1 shows an example of a network containing 2 OSPF

Z-Series DCN planning tool

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 18

Figure 2: Z-Series DCN Planning Tool – Output Example

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 19

1.7.2.1 Configuration per node

Figure 3: Shelf/Site Configuration Example

Figure 4 isolates the nodeA_1 connections.

Figure 4: Shelf Connections Example 1

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 20

Second shelf nodeA_2

Figure 5: Shelf Connections Example 2

Figure 6: Shelf Connections Example 3

The shelf IP address is 10.10.0.2.

450-3708-011 Issue 2.0 © 2018 Ciena® Corporation – All Rights Reserved. P a g e 21