*N0150970* Optical Multiservice Edge 6110

NT6Q92AD
Nortel
Optical Multiservice Edge
6110
Planning Guide
Standard
Rel 2.2
Issue 1 May 2007
What’s inside...
Introduction
Feature overview
Configurations, upgrades, and interworking
Hardware description
User interface description
OAM&P description
Technical specifications
Ordering information and system engineering rules
Technical assistance
Appendix A: Data communications planning
*N0150970*
Copyright  2007 Nortel Networks, All Rights Reserved
This document is protected by copyright laws and international treaties. All information, copyrights and any other intellectual
property rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by Nortel
Networks, the holder is granted no rights to use the information contained herein and this document shall not be published, copied,
produced or reproduced, modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any form or media.
This information is provided “as is”, and Nortel Networks does not make or provide any warranty of any kind, expressed or implied,
including any implied warranties of merchantability, non-infringement of third party intellectual property rights, and fitness for a
particular purpose. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the
information contained herein.
Nortel, the Nortel logo, the Globemark are trademarks of Nortel Networks.
Printed in Canada
iii
Publication history
0
May 2007
First issue of the document.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
iv Publication history
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
ix
Contents
0
About this document
Introduction
v
1-1
OME6110 applications 1-3
OME6110 service interfaces 1-3
Small form-factor pluggable interfaces 1-4
Point-to-point optical broadband services 1-4
TDM switching 1-5
Network management 1-5
Key features and benefits 1-7
Feature overview
2-1
Physical description 2-7
Interface circuit packs 2-7
System Line-up and Test (SLAT) 2-8
Configurations 2-8
Connection management 2-9
Service mapping 2-9
Traffic protection 2-10
Synchronization 2-11
Alarms and events 2-11
Performance monitoring 2-11
Loopbacks 2-12
Data management 2-12
Security and administration 2-12
Topology Adjacency 2-13
Data communication network 2-13
OME6110 management 2-13
Local Craft Access Terminal 2-13
SNMP traps 2-14
Interworking with Nortel portfolio 2-14
Interoperating with non-Nortel portfolio 2-14
Configurations, upgrades, and interworking
3-1
Unprotected configuration 3-1
1+1 MSP/APS 3-2
SNCP/UPSR 3-2
Upgrade support 3-2
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
x Contents
Software 3-2
Hardware 3-2
OME6110 interworking with other products 3-3
Hardware description
4-1
Hardware architecture 4-2
Base chassis 4-2
Power supply units 4-4
DC PSU 35W Dual feed 4-4
AC PSU 50W 4-5
Fan module 4-5
ESD interface 4-6
Fan module filler 4-6
ESD interface 4-6
OAM and LCT ports 4-7
16 x E1/DS1 service interface 4-9
STM-1/OC-3 line interfaces 4-10
Interface circuit pack descriptions 4-11
8x10/100BT L1 circuit pack 4-11
28 x E1/DS1 circuit pack 4-13
3 x E3/DS3 circuit pack 4-14
2x155M circuit pack 4-15
Filler faceplate 4-17
E1 75 ohm termination panel 4-17
Cable routing 4-18
User interface description
5-1
OME6110 local craft access terminal 5-1
SNMP traps 5-2
OAM&P description
Global support 6-2
System Line-up and Test (SLAT) 6-3
Commissioning process 6-3
Testing process 6-3
Network element management 6-4
Equipment management 6-4
Facility management 6-5
Managing facilities 6-5
Loopbacks 6-6
Synchronization management 6-8
Timing generation 6-8
Timing distribution 6-11
Synchronization operating modes 6-12
Synchronization status messages 6-13
Viewing and management 6-14
Synchronization protection 6-14
Connection management 6-15
Hair-pinning 6-16
Connection management application 6-17
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-1
Contents xi
Traffic protection 6-18
Traffic Protection application 6-20
1+1 MSP/APS traffic protection 6-20
Provisioning MSP/APS protected connections 6-20
1+1 MSP/APS protection switch criteria 6-21
SNCP/UPSR Traffic Protection 6-21
Provisioning SNCP/UPSR connections 6-22
SNCP/UPSR protection switch criteria 6-22
Unprotected connections 6-23
Provisioning unprotected connections 6-23
Data communications 6-23
Interfaces 6-23
DCC Transparency 6-27
OAM comms management 6-27
OAM comms routing 6-27
Alarm and event management 6-30
OME6110 local alarm indications 6-30
Alarm management / surveillance 6-30
Alarm Reporting Control 6-32
PDH / DSn alarm monitoring 6-34
Performance monitoring 6-35
PDH / DSn performance monitoring 6-36
PM functions 6-36
STM / OCn PM parameters 6-36
PDH / DSn PM parameters 6-37
Ethernet PM parameters 6-38
WAN PM parameters 6-39
PM time intervals 6-39
PM enable/disable 6-39
PM inhibition 6-39
Security and administration 6-40
Local account user authentication 6-40
RADIUS Centralized authentication 6-40
Security levels 6-41
Login sessions 6-42
Local password management 6-43
Network element name 6-43
Date and time setting 6-43
Topology adjacency 6-44
Backing up and restoring the network element database 6-44
Installing and upgrading network element 6-45
Software upgrade 6-45
Technical specifications
7-1
Physical specifications 7-2
Power specifications 7-3
Connector pinouts 7-4
DC power connector 7-5
Base chassis connector pinouts 7-6
28xE1/DS1 connector pinouts 7-13
E1/DS1 cable pinouts and assemblies 7-17
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
xii Contents
Cable details 7-17
Optical specifications 7-23
STM-1/OC-3 SFP optical specifications 7-24
Electrical specifications 7-30
Environmental specifications 7-32
Operating environment specifications 7-33
Electromagnetic specifications 7-34
Safety specifications 7-35
General commercial and regulatory 7-35
Laser emission 7-35
Power and grounding specifications 7-36
DC input voltage range 7-36
AC input voltage range 7-36
Ordering information and system engineering rules
8-1
OME6110 network element configuration rules 8-2
Base chassis layout 8-2
Bay equipping rules 8-3
Shelf equipping rules 8-4
Site engineering recommendations 8-5
List of parts 8-6
OME6110 base chassis and components 8-6
OME6110 shelf assembly kit 8-8
Circuit packs 8-8
Small form-factor pluggable optic modules 8-9
Electrical interface hardware 8-10
E1/DS1 cable assemblies 8-11
E3/DS3 cable assemblies 8-12
STM-1e cable assemblies 8-12
Ethernet service cable assemblies 8-13
Optical fiber patch cords 8-14
OAM cable assemblies 8-16
Power and earthing cable assemblies 8-17
Software load 8-18
Right to use licenses 8-19
Engineering and support services 8-19
OME6110 documentation 8-20
Change application procedures 8-21
RoHS compliant equipment 8-21
Ordering procedures 8-22
List of procedures
8-1
Ordering OME6110 base chassis, circuit packs, and software 8-23
8-2
Ordering cables, documentation, and services 8-32
Technical assistance
Technical support and information 9-2
Nortel Networks web site 9-3
CE mark 9-3
Field return information 9-4
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
9-1
Contents xiii
Appendix A: Data communications planning
10-1
Introduction 10-2
OAM&P Ports 10-3
M1/F1 port 10-3
LCT port (LAN-1-5) 10-3
Network Interface 10-4
STM-1/OC-3 Data Communication Channel 10-6
Data link layer protocols 10-7
STM-1/OC-3 DCC operation mode 10-8
Overhead transparency 10-10
STM-1/OC-3 DCC implementation rules 10-10
IP communication 10-11
Static routing 10-12
Dynamic routing - OSPF 10-12
Dynamic routing - Integrated IS-IS 10-14
Routing protocol configuration 10-15
Proxy ARP 10-15
OSI data communications 10-16
CLNP 10-16
Configure OSI connection 10-17
Configure GRE tunnel 10-18
Configure IP routing 10-21
Application protocols 10-21
ftp 10-21
telnet 10-22
Diagnostic commands 10-22
arp 10-22
ifconfig 10-22
ping 10-22
route 10-22
tcpdump 10-22
Firewall considerations 10-22
Engineering guidelines 10-23
DCN performance 10-25
Supported DCN design examples 10-25
DCN example 1 - Using static routing with direct LAN connections to OME6110
network elements. 10-27
DCN example 2 - Using single OME6110 GNE with static routing to external DCN.
OSPF is used in between OME6110 network elements. 10-31
DCN example 3 - Using single OME6110 GNE with OSPF to external DCN. OSPF
is used in between OME6110 network elements. 10-35
DCN example 4 - Using OSPF with dual OME6110 GNEs to external OSPF
backbone. 10-39
DCN example 5 - Using single OM4000/3000 GNE with GRE tunnels through
OM4000/3000 network to reach remote OME6110 network elements in linear
spurs off OM4000/3000 NE. 10-44
DCN example 6 - Using single OM4000/3000 GNE with GRE tunnels through
OM4000/3000 network to reach remote OME6110 network elements in
SNCP/UPSR ring with an OM4000/3000 network element. 10-50
DCN example 7 - Using dual OM4000/3000 GNEs with GRE tunnels through
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
xiv Contents
OM4000/3000 network to reach remote OME6110 network elements in
SNCP/UPSR ring with generic SONET/SDH network elements. 10-56
DCN example 8 - Using single OME6110 GNE with iISIS through OM4000/3000
network to reach remote OME6110 network elements in SNCP/UPSR rings
with OM4000/3000 network elements. Proxy ARP used at OME6110 GNE for
access to remote OME6110 NEs. 10-62
DCN example 9 - Using single OME6500 GNE with iISIS through OME6500
network to reach remote OME6110 network elements. 10-69
DCN example 10 - Using single OME6500 GNE with iISIS to reach remote
OME6110 network elements in a SNCP/UPSR ring configuration with generic
SONET/SDH equipment. 10-75
DCN example 11 - Using VC12 management channels through OM4000 network
to reach remote OME6110 network elements in SNCP ring with OM4000 and
legacy OSI network elements. Transparent DCC used to provided resilient
OSI communications. 10-81
DCN example 12 - Using E1 and VC12 management channels to reach remote
OME6110 network elements in SNCP ring with OM4000 and legacy OSI
network element. Transparent DCC used to provided resilient OSI
communications. 10-87
IP networks, addressing, and masks 10-92
Dotted decimal notation for IP addresses 10-93
Circuitless IP interface 10-94
IP routing protocols 10-95
ARP 10-95
OSPF 10-96
Route preference 10-102
Static and default routes 10-102
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
v
About this document
0
This planning guide describes the applications and functionality provided by
the software and hardware of Nortel Optical Multiservice Edge 6110
(OME6110) Release 2.2.
This planning guide covers the following topics:
• Introduction
• Features overview
• Configurations and interworking
• Hardware description
• User interface description
• Operations, administration, maintenance and provisioning (OAM&P)
description
• Technical specifications
• Ordering information and system engineering rules
• Technical assistance
• Appendix A: Data communications planning
Supported software release
This document supports the software release for OME6110 Release 2.2.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
vi About this document
Audience
The following members of your company are the intended audience of this
Nortel technical publication (NTP):
• planners
• provisioners
• network administrators
• transmission standards engineers
• maintenance personnel
Optical Multiservice Edge 6110 NTP library
This roadmap identifies the OME6110 library structure and the use of
application guides and NTPs.
Planning a
Network
Installing,
Commissioning and
Testing a Network
Managing and
Provisioning
a Network
Maintenance and
Troubleshooting
a Network
Supporting
documentation
for the OME6110
Library
Network
Interworking Guide
(NTCA68CA)
About the
OME6110
NTP Library
(323-1853-090)
Installation,
Commissioning and
Testing Procedures
(323-1853-201)
Provisioning and
Protection Switching
Procedures
(323-1853-310)
Trouble Clearing and
Module Replacement
Procedures
(323-1853-543)
Data
Communication
Network
Planning Guide
(NTR710AM)
Planning Guide
(NT6Q92AD)
TL1 Reference
(323-1853-190)
Local Craft Access
User Guide
(323-1853-195)
References
This document refers to the following Optical Multiservice Edge 6110 NTPs:
• About the OME6110 NTP Library, 323-1853-090
• TL1 Reference, 323-1853-190
• Local Craft Access User Guide, 323-1853-195
• Installation, Commissioning and Testing Procedures, 323-1853-201
• Provisioning and Protection Switching Procedures, 323-1853-310
• Trouble Clearing and Module Replacement Procedures, 323-1853-543
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
About this document vii
This document to the following OME6110 supporting documentation:
• Data Communications Network Planning Guide, NTR710AM
• Network Interworking Guide, NTCA68CA
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
viii About this document
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
1-1
Introduction
1-
This chapter provides an overview of the capabilities architected on the Nortel
Optical Multiservice Edge 6110 (OME6110) platform. The chapters that
follow detail the specific features and functionality implemented in Release
2.2.
The OME6110 is a micro-MSPP (Multi-Service Provisioning Platform)
offering very cost effective transport of TDM and Ethernet services over SDH
and SONET networks. The OME6110 is designed for use in customer sites and
in collector networks where lower service capacity is required and small
footprint is paramount.
The OME6110 is a global platform and is software provisionable for either
SONET or SDH operation. Figure 1-1 displays the OME6110 base chassis.
PSU
Figure 1-1
OME6110 network element
2
ESD
MI / F1
ESI
LCT
r
ic
in
ajo
rit
Rx
Tx
2
1
Tx 2 Rx
Tx 1 Rx
FAN
Alm. In
M
al
Alm. Out
M
Power
Optical Multiservice Edge 6110
-48Vdc 2A
C
RET GND -48V
or
E1/DS1 1-16
1
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
1-2 Introduction
The OME6110 provides dramatic cost savings over currently deployed
solutions and offers deployment flexibility at multiple levels, including:
• Service flexibility: Full mix of services including E1/DS1, E3/DS3 and
Ethernet. SDH/SONET services are also planned in the next release.
• Reach flexibility: Small Form-Factor Pluggable (SFPs) optics are used,
allowing each shelf to be configured for the distance and wavelength
required.
• Protection flexibility: Can be deployed with or without line protection.
Both 1+1 MSP/APS and SNCP/UPSR network protection protocols are
supported.
• Interoperability flexibility: Can be networked either with other
OME6110 network elements, or subtended from other Nortel optical
products, such as OM3000, OM4000 or OME6500.
• Management flexibility: The OME6110 is fully integrated into Nortel’s
Optical Network Manager with OMEA. The OME6110 can also be
managed from an HTTP web-based craft user interface running on the
network element. In addition, SNMP alarm traps are supported, enabling
OME6110 fault management from SNMP management systems.
• Data communications flexibility: The OME6110 can be managed over
either OSI or IP DCN networks. Path DCC capabilities are also provided
for extending management reach over third-party networks.
The OME6110 is a carrier grade platform that builds upon the solid reputation
for dependability of Nortel Networks' widely deployed optical networking
products. The various protection options offered by the OME6110 further
enhance the dependability of service transport. For access head end
applications, service traffic can either be connected via sub-network
connection protection (SNCP)/unidirectional path-switched ring (UPSR) or
via protected point-to-point 1+1 connections.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Introduction 1-3
OME6110 applications
The OME6110 offers significant value across a range of network applications.
The principal OME6110 applications are:
• Feeder for Metro Optical networks: The OME6110 can be subtended
from Nortel’s larger Optical platforms to collect E1/DS1, E3/DS3 and
Ethernet traffic from the Access Edge. Its small footprint and low price
make it well suited for smaller customer locations where a full size
SDH/SONET multiplexer can not prove-in. The OME6110 can be
subtended either in a SNCP/UPSR or 1+1 MSP/APS configuration. The
capability to manage OME6110 using path DCC bytes also allows it to be
managed remotely over leased STM-1/OC-3 circuits. The Regenerator
Section/Section and Multiplexor Section/Line overhead tunnel capability
provides further flexibility in managing other SDH/SONET equipment
within the same ring.
• Private Enterprise Networks: The OME6110 can be deployed in smaller
private networks providing transport of E1/DS1, E3/DS3 and Ethernet
services between sites. A light weight management solution is available for
such applications consisting of a web-based craft interface running on the
OME6110 for NE provisioning and SNMP north bound interface for
reporting alarms to a generic SNMP alarm browser.
• Wireless Backhaul: The OME6110 is also well suited for wireless
backhaul applications where both space and cost are paramount. The
OME6110 can be used as a cost-effective backhaul of today’s E1/DS1s and
will support the 3G network transition to Ethernet.
OME6110 service interfaces
OME6110 offers transport and aggregation of asynchronous private lines,
SONET/SDH, and Ethernet. The OME6110 supports three basic categories of
interface:
• PDH
— 16 E1/DS1 ports are offered as part of the base OME6110 chassis. The
option slot can be equipped with a tributary circuit pack offering either
28 additional E1/DS1 ports or 3 E3/DS3 ports.
• Ethernet
— An 8-port 10/100 Base-T Ethernet Private Line (EPL) circuit pack is
available in the current release. In future releases, a GE EPL circuit
pack and a 10/100/1000 Layer 2 VPN circuit pack will also be offered.
• SDH/SONET
— STM-1/OC-3 client interfaces are being introduced in release 2.2.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
1-4 Introduction
Small form-factor pluggable interfaces
The OME6110 uses small form-factor pluggable (SFP) interfaces to deliver
optical rate and reach flexibility on a per port basis for the line interface.
As of release 2.1, the OME6110 offers the following SFP interface types:
SR-0, SR-1/I1.1, IR-1/S1.1, LR-1/L1.1, LR-2/L1.2, CWDM, STM-1e,
Bidirectional.
Nortel Networks has been collaborating closely with leading SFP vendors to
improve the reliability, robustness and manageability of SFPs. The use of such
carrier-grade SFP technology enables service providers to enjoy the flexibility
of provisioning the interfaces per the requirements of the specific application.
SFPs also reduce the cost of sparing by enabling an upgrade of the optical line
interfaces as they become readily available.
Figure 1-2
Pluggable optical modules summary
mall-form factor pluggable (SFP)
155/622 Mbit/s
- Carrier grade
- Service tolerance:
- Reach (SR/IR/LR)
- Rate (OC-3/STM-1, OC-12/STM-4 future)
- GE (future)
- CWDM with wavelength per pluggable slot
- Operational simplification
- Expenditure matched with reach requirements
- CAPEX savings through reduced sparing
Point-to-point optical broadband services
The OME6110 uses GFP, VCAT and LCAS standards for the mapping and
transport of Ethernet services.
GFP provides an efficient mechanism for Ethernet transport over a
SDH/SONET core network via efficiently mapping varying client signals into
SDH/SONET VC-12/VT1.5 and VC-3/STS frames. GFP mapping enables
efficient network resource utilization with low overhead requirements, and
limited over-provisioning with VCAT. End-to-end framing provides
demarcation for the Ethernet signal, and enables consistent SDH/SONET
based PMs through the network. Since the Ethernet is mapped into
SDH/SONET frames, the existing core network can transport the Ethernet
frames transparently.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Introduction 1-5
The OME6110 also supports Virtual Concatenation (ITU-T G.707 compliant)
with support at the VT1.5-nv and STS-1-nv SONET rates as well as VC-12-nv
and VC-3-nv SDH rates. A maximum of 48 ms of differential delay is
supported.
Along with VCAT the OME6110 also supports value added capabilities such
as soft protection via Link Capacity Adjustment Scheme (LCAS - G.7042).
LCAS has been specifically developed to overcome static link provisioning. It
enables service providers to efficiently offer dynamically-allocated bandwidth
as well as hitless throttling of the capacity of a VCAT link (or Virtual
Concatenated Group) by adding or removing STSs or VCs as required.
LCAS provides a soft protection and load-sharing mechanism to automatically
decrease the link capacity if an STS or VC path experiences a failure and
automatically increases the link capacity when the network fault is repaired.
This capability provides an extra level of network and service resiliency by
facilitating the support of SLAs through graceful service degradation when
necessary. In particular, during network and service restoration LCAS can
support hitless bandwidth expansion and contraction thereby reducing service
interruptions in the event of network failure and easing network operations and
maintenance actions.
TDM switching
In the OME6110 architecture, traffic is switched between working and
protection line interfaces via the switch matrix in the base chassis.
All ingress service traffic is mapped into VC-12/VT1.5, VC-3/STS-1 or
VC-4/STS-3c containers and directed towards the switch matrix which is
configured to switch the incoming traffic to the appropriate line interface. The
switch matrix allows any input channel to be connected to any output channel.
Hairpinning is also supported between client ports.
Network management
The OME6110 is managed as an integral part of Nortel Networks' market
proven end-to-end optical portfolio management capabilities. This framework
supports a sophisticated and highly customizable desktop providing
centralized topology view and fault management, centralized launch pad for a
full suite of management applications, easy to use nodal managers and
seamless network element reach-through for Nortel Networks' complete
optical networks portfolio. These network management capabilities are
supported by the Optical Manager and Optical Application Platform, such as
OMEA and Optical Network Manager (formerly known as Preside), in
alignment with Nortel Networks overall optical networks portfolio.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
1-6 Introduction
The OME6110 local craft access terminal, which is an HTTP web-based
graphical interface running on the network element, provides complete nodal
management that can be integrated into a centralized network wide view
through the Optical Network Manager.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Introduction 1-7
Key features and benefits
The OME6110 multi-services access platform provides customers with the
flexibility, scalability and management capabilities they need in a compact
cost effective package. The key benefits to customers of deploying the
OME6110 can be summarized as follows:
• support of a broad set of services (PDH/Async, Ethernet and
SDH/SONET)
• switching granularity and flexibility for service grooming and connection
management, such as unconstrained VC-12/VT1.5 level switching
• cost-efficient service deployment through
— low cost entry configuration for E1/DS1 services
— in-service expansion to support new services
— dynamically pluggable optical interfaces (lowers sparing costs)
— flexible, complete and easy to use network and service management
leading to simplified operations for rolling out and maintaining
services
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
1-8 Introduction
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
2-1
Feature overview
2-
This chapter provides a brief overview of the Optical Multiservice Edge 6110
(OME6110) features. The OME6110 supports both SDH and SONET optical
line interfaces (STM-1/OC-3) as well as transport of PDH/DSn, and 10/100
BaseT Ethernet services. OME6110 2.2 introduces the following new features:
•
•
security and administration enhancements:
– Centralized RADIUS authentication
– number of named users increased up to 100
new hardware:
– introduction of 2x155M service module
Table 2-1 lists the features available in different releases of the Optical
Multiservice Edge 6110. For more information about these features, refer to
the appropriate reference in this planning guide. The following sections in this
chapter give a brief description of the main features.
Table 2-1
Summary of features for previous and current releases
Topic
OME6110 OME6110 OME6110 Reference
R1.0
R2.0/R2.1 R2.2
OME6110 hardware
Base chassis
Yes
Yes
Yes
Base chassis on page 4-2
Dual feed DC power supply unit
Yes
Yes
Yes
Single feed AC power supply unit
No
Yes
Yes
Power supply units on page
4-4
Fan module
Yes
Yes
Yes
Fan module on page 4-5
Filler faceplate
Yes
Yes
Yes
Filler faceplate on page
4-17
75 ohm termination panel
Yes
Yes
Yes
E1 75 ohm termination
panel on page 4-17
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
2-2 Feature overview
Table 2-1 (continued)
Summary of features for previous and current releases
Topic
OME6110 OME6110 OME6110 Reference
R1.0
R2.0/R2.1 R2.2
Interface circuit packs
8x10/100BT L1
Yes
Yes
Yes
28xE1/DS1
No
Yes
Yes
3xE3/DS3
No
Yes
Yes
2x155M
No
No
Yes
OC-3/STM-1 SR0 1310 nm (ext. temp.) No
Yes
Yes
OC-3/STM-1 IR1/S1.1 1310 nm (std.
temp.)
Yes
Yes
Yes
OC-3/STM-1 LR1/L1.1 1310 nm (std.
temp.)
Yes
Yes
Yes
OC-3/STM-1 LR2/L1.2 1550 nm (std.
temp.)
Yes
Yes
Yes
OC-3/STM-1 LR2/L1.2 1550 nm (ext.
temp.)
No
Yes
Yes
OC-3/STM-1 CWDM (ext. temp.)
No
Yes
Yes
Yes
Yes
Interface circuit pack
descriptions on page 4-11
SFP modules
OC-3/12/STM-1/4 IR1/S1.1_S4.1 (std. Yes
temp.)
Small form-factor
pluggable optic modules on
page 8-9
Configurations
Unprotected
Yes
Yes
Yes
Unprotected configuration
on page 3-1
1+1 MSP
Yes
Yes
Yes
1+1 APS
No
Yes
Yes
SNCP
Yes
Yes
Yes
UPSR
No
Yes
Yes
Equipment management
No
Yes
Yes
Equipment management
on page 6-4
Facility Management
Yes
Yes
Yes
Facility management on
page 6-5
1+1 MSP/APS on page 3-2
SNCP/UPSR on page 3-2
Equipment and facility management
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Feature overview 2-3
Table 2-1 (continued)
Summary of features for previous and current releases
Topic
OME6110 OME6110 OME6110 Reference
R1.0
R2.0/R2.1 R2.2
Connection management
VC12 and VC3 cross-connects
Yes
Yes
Yes
VC11 cross-connects
No
Yes
Yes
VT1.5, VT2, and STS-1
cross-connects
No
Yes
Yes
Yes
Yes
Yes
Connection management
on page 6-15
Service Mapping
GFP-F to VC12-nv,
VC3-nv (virtual concatenation)
Ethernet
Ethernet GFP-F to VT1.5-nv and
STS-1-nv (virtual concatenation)
No
Yes
Yes
E1 to VC12
Yes
Yes
Yes
E1 to VT2
No
Yes
Yes
E3 to VC3/STS-1
No
Yes
Yes
DS1 to VC11/VT1.5
No
Yes
Yes
DS3 to VC3/STS-1
No
Yes
Yes
Unprotected - STM-1
Yes
Yes
Yes
Unprotected - OC-3
No
Yes
Yes
MSP - STM-1
Yes
Yes
Yes
1+1 APS - OC-3
No
Yes
Yes
Route Diversity for DCC on MSP/APS No
Yes
(R2.1)
Yes
SNCP
Yes
Yes
Yes
UPSR
No
Yes
Yes
Generic Framing
Procedure on page 6-15
Connection management
on page 6-15
Traffic protection
Unprotected connections
on page 6-23
1+1 MSP/APS traffic
protection on page 6-20
SNCP/UPSR Traffic
Protection on page 6-21
Synchronization
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
2-4 Feature overview
Table 2-1 (continued)
Summary of features for previous and current releases
Topic
OME6110 OME6110 OME6110 Reference
R1.0
R2.0/R2.1 R2.2
Internal, BITS, line
Yes
Yes
Yes
Timing generation hierarchy
Yes
Yes
Yes
Timing distribution hierarchy
Yes
Yes
Yes
SDH SSM generation/termination
Yes
Yes
Yes
SONET SSM generation/termination
No
Yes
Yes
2 MHz and 2Mbits/s ESI/ESO with
SSM
Yes
Yes
Yes
DS1 ES1/ESO with SSM
No
Yes
Yes
LEDs indication of shelf and circuit
pack status
Yes
Yes
Yes
Alarm and event reporting
Yes
Yes
Yes
Alarm reporting control
No
Yes
Yes
Section/RS, Line/MS, STS/HO path,
VT/LO path alarms
No
Yes
Yes
E1 and STM-1 alarms
Yes
Yes
Yes
E3/DS1/DS3/OC-3 alarms
No
Yes
Yes
SDH RS, MS and path
Yes
Yes
Yes
SONET section, line and path
No
Yes
Yes
Transceiver (physical PM for 2x155M
optical ports)
Yes
Yes
Yes
Ethernet and VCG
Yes
Yes
Yes
E1 PM parameters
Yes
Yes
Yes
E3/DS1/DS3 PM parameters
No
Yes
Yes
No
Yes
Yes
Synchronization
management on page 6-8
Alarms and events
Alarm and event
management on page 6-30
Performance monitoring
Performance monitoring on
page 6-35
System lineup and testing
SLAT (commissioning tool)
System Line-up and Test
(SLAT) on page 6-3
Loopbacks
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Feature overview 2-5
Table 2-1 (continued)
Summary of features for previous and current releases
Topic
OME6110 OME6110 OME6110 Reference
R1.0
R2.0/R2.1 R2.2
Facility and Terminal Loopbacks
(STM-1, E1)
Yes
Yes
Yes
Facility and Terminal Loopbacks
(OC-3, DS1, E3, DS3)
No
Yes
Yes
Terminal Loopback (Ethernet)
Yes
Yes
Yes
Yes
Yes
Yes
Backing up and restoring
the network element
database on page 6-44
Local user account/password
management
Yes
Yes
Yes
Security and administration
on page 6-40
Up to 100 named user accounts
No
No
Yes
Centralized RADIUS authentication
No
No
Yes
Network element naming, date and
time
Yes
Yes
Yes
No
Yes
Yes
Loopbacks on page 6-6
Data management
NE data backup and restore
Security and administration
Topology Adjacency
Topology adjacency provisioning and
discovery
Topology adjacency on
page 6-44
Data communication network
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
2-6 Feature overview
Table 2-1 (continued)
Summary of features for previous and current releases
Topic
OME6110 OME6110 OME6110 Reference
R1.0
R2.0/R2.1 R2.2
LAN, optical DCC physical interfaces
Yes
Yes
Yes
IP addressing
Yes
Yes
Yes
OSI addressing
Yes
Yes
Yes
Enable/disable OSPF per network
interface
No
Yes
Yes
OSPF authentication
No
Yes
(R2.1)
Yes
IP over OSI GRE tunnel
Yes
Yes
Yes
PPP/LAPD over DCC
Yes
Yes
Yes
F1 user channel access
No
Yes
Yes
OAM via Path DCC (F2/F3 bytes)
No
Yes
Yes
E1/VC12 management channel
No
Yes
Yes
Static route advertisement
No
Yes
(R2.1)
Yes
Proxy ARP
No
Yes
(R2.1)
Yes
Web User Interface
Yes
Yes
Yes
SNMP v1 trap monitoring
No
Yes
Yes
Nortel portfolio
Yes
Yes
Yes
Interworking with Nortel
portfolio on page 2-14
non-Nortel portfolio
Yes
Yes
Yes
Interoperating with
non-Nortel portfolio on
page 2-14
Network element upgrade
No
Yes
Yes
Unified upgrade
No
Yes
(R2.1)
Yes
Installing and upgrading
network element on page
6-45
Data communications on
page 6-23 and Appendix A:
Data communications
planning on page 10-1
OME6110 management
User interface description
on page 5-1
Interworking
Software upgrades
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Feature overview 2-7
Physical description
The OME6110 hardware platform consists of a base chassis which fits in a
standard ETSI (19 in. EIA), a NEBS2000 rack or an ANSI (23 in.) rack. The
base chassis is equipped with:
• power supply unit options:
— dual feed DC power supply
— single feed AC power supply
• 16xE1/DS1 service interface
• two STM-1/OC-3 optical ports (without SFP)
• optional service slot
• fan module
Figure 2-1 provides an overview of the OME6110 base chassis layout.
Figure 2-1
OME6110 base chassis layout
Power supply
unit
Optional
service
slot
Fan
module
PSU
16xE1/DS1 service
interface
2
ESD
MI / F1
ESI
or
ic
ajo
rit
C
Rx
Tx
2
LCT
1
Tx 2 Rx
Port 2
OAM ports
LCT port
- Ethernet
Network
Element
alarms
Tx 1 Rx
FAN
Alm. In
in
al
Alm. Out
M
Power
Optical Multiservice Edge 6110
-48Vdc 2A
M
RET GND -48V
r
E1/DS1 1-16
1
Port 1
ESD jack
location
2xSTM-1/OC-3
interface ports
For more information, refer to “Hardware description” on page 4-1 and
“OME6110 network element configuration rules” on page 8-2.
Interface circuit packs
The OME6110 architecture supports an optional service slot that can be
equipped with the following circuit packs:
• 8x10/100BT L1 circuit pack
• 28xE1/DS1 circuit pack
• 3xE3/DS3 circuit pack
• 2x155M circuit pack
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
2-8 Feature overview
Note: When the optional service slot is not equipped with a circuit pack,
a filler panel must be installed.
Table 2-2 provides a summary of the service modules supported on OME6110.
Table 2-2
OME6110 interface circuit pack summary
Circuit pack
Port density/ Notes
circuit pack
8x10/100BT L1
8
• GFP-F mapped (ITU-T G.7041
compliant)
28xE1/DS1
28
• unframed E1
• CRC4 framed E1
• Clear Channel DS1
• ESF framed DS1
3xE3/DS3
3
• unframed E3
• G.832 framed E3
• unframed DS3
• ASYNC DS3
2x155M
2
• STM-1/OC-3 optical and electrical SFPs
supported
For more information about the circuit packs, refer to Interface circuit pack
descriptions on page 4-11. For more information about slot equipping rules,
refer to Base chassis layout on page 8-2.
System Line-up and Test (SLAT)
The OME6110 supports the ability to configure the system when it is being
commissioned for the first time. The user is given an option to initialize the
system with a configuration compatible with the NE. For the chassis that
supports both SONET and SDH modes of operation, the user is given the
choice of initializing the NE in either mode of operation.
For more information, refer to System Line-up and Test (SLAT) on page 6-3
Configurations
OME6110 currently supports the following configurations for the
STM-1/OC-3 line interfaces.
Unprotected
OME6110 supports unprotected configurations. For more information, refer to
Unprotected configuration on page 3-1.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Feature overview 2-9
1+1 MSP/APS protection
OME6110 supports 1+1 Multiplex Section Protection (MSP)/Automatic
Protection Switching (APS) configurations. For more information, refer to 1+1
MSP/APS on page 3-2.
SNCP/UPSR
OME6110 supports Sub-network connection protection
(SNCP)/Unidirectional path switched ring (UPSR) ring configurations.
In a SNCP/UPSR configuration, traffic is transmitted simultaneously on two
separate ports. The traffic is transmitted via different routes through the
network to the destination node which selects one of the two paths based on
the quality of the received signal. For example, in a ring configuration, the
traffic can be transmitted simultaneously on the working fiber in the clockwise
direction and on the protection fiber in the counter-clockwise direction.
For more information, refer to SNCP/UPSR on page 3-2.
Connection management
OME6110 supports nodal port-to-port connection management. OME6110
supports the ability to provision bidirectional and unidirectional connections
at VC11/VT1.5, VC12/VT2 and VC3/STS-1 rates.
OME6110 supports various bandwidth management models that include the
following;
• bidirectional connections
•
•
unidirectional connections
port to port (hair-pinning)
For more information, refer to Connection management on page 6-15.
Service mapping
All services (Ethernet, E1, E3, DS1, and DS3) are mapped to appropriate
SDH/SONET containers and tributaries.
The OME6110 uses Generic Framing Procedure (GFP) as its standards based
SDH/SONET mapping for Ethernet services. GFP is an ITU standard
(G.7041) which describes a flexible mapping technique for transparent
transport of multiple protocols in SDH and SONET. GFP-Framed (GFP-F) is
used for mapping Ethernet to SDH/SONET tributaries and containers.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
2-10 Feature overview
Table 2-3 provides a summary of the service mappings supported in this
release.
Table 2-3
OME6110 service mapping
Services
Circuit Pack
Mapping/connection level
supported
E3/DS3
• 3 x E3/DS3
• VC3/STS-1
E1/DS1
• 16 x E1/DS1 service
interface (on base
chassis)
• VC11/VT1.5, VC12/VT2
• 28xE1/DS1
• 8 x 10/100BT L1
Ethernet
• GFP-F to VC12 and VC3
• GFP-F to VT1.5 and STS-1
For more information, refer to Connection management on page 6-15.
Traffic protection
OME6110 supports 1+1 MSP/APS and SNCP/UPSR traffic protection. The
system monitors the traffic facilities for performance degradation and failure
and performs protection switching when these conditions are present. Table
2-4 provides a summary of the protection schemes supported in this release.
Table 2-4
Traffic protection summary
Protection scheme
Supported interfaces or circuit packs
Unprotected
(default for all supported
interfaces)
• STM-1/OC-3 interfaces
• 3 x E3/DS3 circuit pack
• 16 x E1/DS1 interface
• 28 x E1/DS1 circuit pack
• 8 x 10/100BT L1 circuit pack
1+1 MSP/APS
• STM-1/OC-3 interfaces
SNCP/UPSR
• STM-1/OC-3 interfaces
• 3 x E3/DS3 circuit pack
• 16 x E1/DS1 interface
• 28 x E1/DS1 circuit pack
• 8x10/100BT L1 circuit pack
For more information, refer to Traffic protection on page 6-18.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Feature overview 2-11
Synchronization
Synchronization is a network level application that ensures all nodes across a
network can trace back to the same clock source. Within a single node,
synchronization prevents buffer overflow or underflow which avoids bit errors.
When OME6110 is provisioned in SONET mode, quality level codes used for
S1 byte for SSM are supported as per GR-253. Furthermore, E1/DS1
interfaces can also be used as BITS timing source to the network element.
For more information, refer to Synchronization management on page 6-8.
Alarms and events
The OME6110 provides several mechanisms to identify and localize faults and
events.
• light-emitting diodes (LEDs) on the front of the base chassis or the
faceplate of a circuit pack indicate the status of the functionality supported
on the equipment
— circuit pack failed on all circuit packs
— loss of signal on interface circuit packs
— power LED on the base chassis provides the power status
• visual alarms interface on the base chassis provides a summary of active
alarms at the shelf level
The OME6110 stores active alarms and events which can be viewed from the
local craft access terminal.
Several new alarm reporting control features are available: profile based path
alarm control, alarm filter, and facility alarm reporting. The user can now have
the option to enable or disable alarm reporting to the management system, on
a per alarm type and per port basis.
For more information, refer to Alarm and event management on page 6-30.
Performance monitoring
Performance monitoring (PM) refers to the continuous collection, analysis and
reporting of the performance data of a monitored entity. This monitoring
allows early detection of service degradations and facilitates preventive
maintenance without interruption of service. PMs can also be used to facilitate
trouble/fault isolation. Performance monitoring is performed on all in-service
optical/electrical interface ports.
This release supports the following PMs:
• regenerator section (RS)/section near-end PMs
• multiplex section (MS)/line near-end and far-end PMs
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
2-12 Feature overview
•
•
•
•
•
High Order (HO)/STS near-end and far-end path PMs
Low Order (LO)/VT near-end and far-end path PMs
PDH/DSn line PMs and near-end path PMs
physical layer PMs for all optical interfaces
Ethernet (client facing) and WAN (GFP-F mapped - line facing) PMs
The OME6110 allows the user to retrieve:
• current PM values (15 minute and 1-Day values in progress)
• recent history (32 previous 15 minute and previous day values stored on the
network element)
The OME6110 supports threshold crossing alerts (TCA) to advise the user
when a PM parameter threshold has been exceeded. The user can enable or
disable the TCAs for the RS/section, MS/line, and SDH/SONET path
parameters and when enabled, the PM thresholds are user-provisionable.
For more information, refer to Performance monitoring on page 6-35.
Loopbacks
The OME6110 supports facility loopbacks on the STM-1/OC-3 and DSn/PDH
ports, and terminal loopbacks on all ports, including the 10/100 Ethernet ports
on the 8x10/100BT L1 circuit pack. The loopbacks provide a quick and
reliable way to sectionalize connections during testing and troubleshooting.
For more information, refer to Loopbacks on page 6-6.
Data management
The OME6110 is responsible for the resilience of its provisioning data and
ensures that a copy is preserved on flash.
The OME6110 provides the capability to backup and/or restore the
provisioning data to/from an external storage device.
For more information, refer to Backing up and restoring the network element
database on page 6-44.
Security and administration
The OME6110 provides the following security and administration capabilities
managed from the Local Craft Access Terminal:
• Network element security
— security levels
— login sessions
— local password management
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Feature overview 2-13
•
— local user authentication
— centralized RADIUS authentication
Network element administration
— network element naming
— date and time setting
For more information, refer to Security and administration on page 6-40.
Topology Adjacency
The topology adjacency feature on the OME6110 provides the capability to
manually provision the neighbor status information, which is then used by the
network management application to build the network topology.
For more information, refer to Topology adjacency on page 6-44.
Data communication network
OME6110 uses an IP-based data communications infrastructure for network
element management and for interworking with IP-based network elements.
OME6110 also supports OSI-based DCC for interworking with OSI-based
network elements.
The OME6110 supports the following types of management interfaces:
• LCT port for interface to a data communications network (DCN).
• M1/F1 port for modem and user data channel access.
• RS/section, and MS/line and Path (F2, F3 and F2-F3) DCC for OAM&P
access to remote network elements
• management channel via VC12 circuit or E1 channel on base chassis
• overhead tunnel provisioning for DCC transparency (for interoperability
with other vendors’ equipment)
For more information, refer to Data communications on page 6-23 and
Appendix A: Data communications planning on page 10-1.
OME6110 management
Local Craft Access Terminal
The OME6110 supports a comprehensive suite of OAM&P functionality
which can be managed through a web-based local craft access user interface.
The local craft user interface is a graphical, nodal management tool that is
inherent on the network element software load and can be launched via a web
browser.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
2-14 Feature overview
The local craft access user interface is launched from a web browser which can
be running on Windows, UNIX or Solaris workstations ensuring field
technicians and NOC operators are operating with the same view.
For more information, refer to User interface description on page 5-1.
SNMP traps
The OME6110 system events can be monitored through SNMP traps raised by
the NE, based on the MIB tables.
For more information, refer to SNMP traps on page 5-2.
Interworking with Nortel portfolio
The OME6110 interworks with the following products:
• Nortel Optical Manager and Optical Applications Platform
• Nortel products through STM-1/OC-3 interfaces
OME6110 Release 2.2 will operate with the following network management
software:
• Optical Manager Element Adapter (OMEA) 5.1
In Release 2.2, the OME6110 interworks with
• the Optical Metro 3000/4000-series, the TransportNode TN-1C/1X, and
the Optical Multiservice Edge 6500 products through STM-1/OC-3
interfaces.
For more information, refer to OME6110 interworking with other products on
page 3-3.
Interoperating with non-Nortel portfolio
The OME6110 is a standards compliant product that can operate with
subtending products that support standard compliant STM-1/OC-3 interfaces.
You must note that multi-vendor mid span meet applications depend on the
configuration and APS mode of interest.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
3-1
Configurations, upgrades, and
interworking
3-
This chapter describes how the Optical Multiservice Edge 6110 (OME6110)
Release 2.2 fits in a network and interworks with other Nortel Networks
products. This chapter also describes the upgrade considerations for
OME6110. Table 3-1 lists the topics in this chapter.
Table 3-1
Topics in this chapter
Topic
Page
Unprotected configuration
3-1
1+1 MSP/APS
3-2
SNCP/UPSR
3-2
Upgrade support
3-2
OME6110 interworking with other products
3-3
For an overview of the OME6110 applications supported by this release, refer
to OME6110 applications on page 1-3.
Unprotected configuration
OME6110 unprotected configuration on the STM-1/OC-3 line interface ports
has a single pair of optical fibers interconnecting network elements.
Unprotected connection configuration is also supported on all service
interfaces and circuit packs available in this release:
• 8x10/100BT L1 circuit pack
• 16xE1/DS1 interface on base chassis
• 28xE1/DS1 circuit pack
• 3xE3/DS3 circuit pack
• 2x155M circuit pack
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
3-2 Configurations, upgrades, and interworking
For more information about the unprotected protection scheme, refer to
Unprotected connections on page 6-23.
1+1 MSP/APS
1+1 Multiplex Section Protection (MSP)/Automatic Protection Switching
(APS) configuration is a line level traffic protection scheme and consists of a
point-point configuration with two optical fiber pairs carrying the traffic (one
for working and the other for protection). Traffic is carried on both working
and protection STM-1/OC-3 lines and the receiving interfaces determine
which line to select based on signal quality or user-initiated actions.The
OME6110 supports 1+1 MSP/APS protection switching on the STM-1/OC-3
line interfaces. For more information about 1+1 MSP/APS protection
configuration rules, refer to Refer to Table 8-3 for OME6110 equipment rack
space requirements. on page 8-4. For more information about the 1+1
MSP/APS protection scheme, refer to 1+1 MSP/APS traffic protection on page
6-20.
SNCP/UPSR
A Sub-network connection protection (SNCP)/unidirectional path-switched
ring (UPSR) is a path level traffic protection scheme. In SNCP/UPSR
configuration, traffic is transmitted simultaneously on two separate ports. The
traffic is transmitted via different routes through the network to the destination
node which selects one of the two paths based on the quality of the received
signal.
The OME6110 supports SNCP/UPSR protection switching on all optical and
service interfaces on the network element.For more information about
SNCP/UPSR protection configuration rules, refer to Refer to Table 8-3 for
OME6110 equipment rack space requirements. on page 8-4. For more
information about the SNCP/UPSR protection scheme, refer to SNCP/UPSR
Traffic Protection on page 6-21.
Upgrade support
This section provides information when planning upgrades on the OME6110.
Software
The OME6110 supports the following in-service software upgrades:
• OME6110 Release 2.1 to OME6110 Release 2.2
Note: Upgrades must be performed following a specific procedure. Refer
to the upgrade change application procedure (CAP), NT6Q93AD, for
detailed upgrade procedures.
Hardware
No hardware upgrades are required when upgrading to Release 2.2, unless you
require the functionality provided by the new 2x155M circuit pack.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Configurations, upgrades, and interworking 3-3
OME6110 interworking with other products
OME6110 is compliant with SDH/SONET standards and therefore enables
interworking with other SDH/SONET compliant network elements. As shown
in Table 3-2, OME6110 Release 2.2 operates with the following network
management software.
Table 3-2
Network management software that operates with OME6110 Release 2.2
Product
Releases
Optical Network Manager
10 / 11
Optical Manager Element Adaptor
5.1
Functionality
• Fault
• Trail Manager
• PM
• Back-up & Restore
• OSP
• Software Delivery
• Radius
As shown in Table 3-3, OME6110 Release 2.2 interworks with Nortel
Networks products through STM-1/OC-3 optical interfaces or
Ethernet/DSn/PDH electrical interfaces. For more information on OME6110
interworking rules and guidelines, refer to the Network Interworking Guide,
NTCA68CA.
Table 3-3
Nortel Networks products that interwork with OME6110 Release 2.2
Product
Release
TN-1C
7 and higher
TN-1X
9 and higher
Optical Metro 3100
4.0 and higher
Optical Metro 3400
11.1 and higher
Optical Metro 3500
13.0 and higher
Optical Metro 4100
4.9
Optical Metro 4150
8.0 and higher
Optical Metro 4200
5.0 and higher
Optical Multiservice Edge 6110
2.0 and higher
Optical Multiservice Edge 6130
1.0, 2.0
Optical Multiservice Edge 6500
1.2 and higher
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
3-4 Configurations, upgrades, and interworking
Note: See Interoperating with non-Nortel portfolio on page 2-14 for more
details.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
4-1
Hardware description
4-
This chapter provides an overview of the Optical Multiservice Edge 6110
(OME6110) hardware. This chapter describes the OME6110 base chassis,
modules and circuit packs, as listed in Table 4-1.
Table 4-1
Topics in this chapter
Topic
Page
Hardware architecture
4-2
Base chassis
4-2
Power supply units
4-4
Fan module
4-5
Fan module filler
4-6
OAM and LCT ports
4-7
16 x E1/DS1 service interface
4-9
STM-1/OC-3 line interfaces
4-10
Interface circuit pack descriptions
4-11
Filler faceplate
4-17
E1 75 ohm termination panel
4-17
Cable routing
4-18
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
4-2 Hardware description
Hardware architecture
The OME6110 platform, as shown in Figure 4-1, consists of a base chassis
which is equipped with:
• power supply unit:
— dual feed DC power supply
— single feed AC power supply
• fan module
• OAM and LCT ports
• 16 x E1/DS1 service interface
• two STM-1/OC-3 optical ports
• service interface slot
Figure 4-1
OME6110 base chassis dimensions
1U
44.0 mm
(1.7 in.)
Base chassis
D
ES
FAN
1
2
3
4
5
Tx
6
Rx
7
1
Rx
Rx
M
r
2
er
Pow
H
ET
8X
0
ive
tus
Act
ice
16
1 1-
PSU
T
LC
I
611
ultis
lM
tica
Op
DS
ge
Ed
erv
Sta
E1/
C
riti
ca
l
M
ajo
8
Tx
1
2
in
or
Tx
445.0 mm
(17.5 in.)
ES
MI
2
270.0 mm
(10.6 in.)
1
/F
. In
Alm
D
1
T
RE
GN
ut
.O
-48V
dc
2A
Alm
-48V
Base chassis
Figure 4-2 provides an overview of the OME6110 base chassis layout.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Hardware description 4-3
Figure 4-2
OME6110 base chassis layout
Power supply
unit
Optional
service
slot
Fan
module
PSU
16xE1/DS1 service
interface
2
ESD
Alm. Out
Alm. In
MI / F1
ESI
Rx
Tx
Optical Multiservice Edge 6110
-48Vdc 2A
2
LCT
1
Tx 2 Rx
Port 2
OAM ports
LCT port
- Ethernet
Network
Element
alarms
Tx 1 Rx
FAN
al
or
ic
ajo
in
rit
C
M
Power
M
RET GND -48V
r
E1/DS1 1-16
1
Port 1
ESD jack
location
2xSTM-1/OC-3
interface ports
The OME6110, three versions of the base chassis are offered, as summarized
in Table 4-2. All circuit packs and field replaceable units (FRUs) can be used
on all hardware versions of the base chassis.
Table 4-2
OME6110 base chassis versions
Base Chassis version
OME6110 System
PEC
NE Mode support Notes
OME6110 Release 1
(standard temperature)
NT6Q50AA
SDH mode only
This system PEC is no longer
orderable.
OME6110 Release 2
(standard temperature)
NT6Q50AB
NT6Q51AA
SDH or SONET
modes
OME6110 Release 2.1
(standard temperature)
NT6Q50AC
NT6Q51AC
Up-release of the release 1 base
chassis with SONET GR-1244
compliant clock source.
OME6110 Release 2.2
(standard temperature)
NT6Q50ADE5
NT6Q51ADE5
SDH or SONET
modes.
For extended temperature
operation, the OME6110 system
must consist of extended
temperature base chassis and
FRUs (PSU, FAN and circuit pack).
OME6110 Release 2
NT6Q50BA
(extended temperature)
OME6110 Release 2.1 NT6Q50BC
(extended temperature)
OME6110 Release 2.2 NT6Q50BDE5
(extended temperature)
Refer to Ordering information and system engineering rules on page 8-1 for
more information.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
4-4 Hardware description
Power supply units
DC PSU 35W Dual feed
The OME6110 supports a power supply unit with dual -48 V dc power feeds.
The DC power supply unit, as shown in Figure 4-3, is located at the left of the
base chassis and provides the following functionality:
• operates over the range -40 V to -57.5 V dc
• 35 W capacity
• dual power inputs
• local safety ground point
• monitors voltage on input power feed and the value displayed on the user
interface can be used as general guidance
• low and high voltage thresholds for voltage alarms to the user interface
The OME6110 supports both standard temperature and extended temperature
DC PSUs. The DC PSU is equipped with a voltage monitoring circuit which
will properly alarm when:
• a bay fuse or circuit breaker blows
• a bay fuse or circuit breaker is removed
Refer to Ordering information and system engineering rules on page 8-1 for
the PEC information. The DC PSU comes equipped with the base chassis, but
can also be ordered separately for sparing.
PSU
Figure 4-3
OME6110 dual DC power supply unit
2
1
RET GND -48V
PSU
-48Vdc 2A
2
8
7
6
5
4
3
2
1
8XETH
ESD
Active
Status
RET GND -48V
Power
Optical Multiservice Edge 6110
-48Vdc 2A
Alm. Out
Alm. In
MI / F1
ESI
Optical Multiservice Edge 6110
LCT
al
r
ic
rit
C
ajo
M
or
in
M
Rx
Tx
2
1
Tx 2 Rx
Tx 1 Rx
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
FAN
E1/DS1 1-16
1
Hardware description 4-5
AC PSU 50W
The OME6110 supports a power supply unit with a 90-264V AC power feed.
The AC power supply unit, as shown in Figure 4-4, is located at the left of the
base chassis and provides the following functionality:
• operates over the range 90 Vac to 264 Vac at 47/63 Hz
• 50 W capacity
• single power input
• standard temperature support only
•
Universal AC power socket (IEC C14)
Refer to Ordering information and system engineering rules on page 8-1 for
the PEC. The AC PSU comes equipped with the base chassis, but can also be
ordered separately for sparing.
Figure 4-4
Universal AC power socket
Fan module
The OME6110 supports a fan module unit. The fan module unit is located on
the right side of the base chassis, as shown in Figure 4-2 on page 4-3. Two fans
are integrated within the module and are operating in load sharing mode (both
fans are running at the same time. The fans are continuously being monitored
for failures.
Starting with OME6110 release 2.2, the fan module is optional for standard
temperature applications. The fan module is mandatory for all extended
temperature applications.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
4-6 Hardware description
ESD interface
The fan module contains an ESD interface used to connect an antistatic wrist
strap required when handling circuit packs to avoid damage as a result of
electrostatic discharge. Figure 4-5 on page 4-6 shows the location of the ESD
interface on the fan module of the OME6110.
Figure 4-5
OME6110 fan module
ES
FAN
D
The OME6110 supports both standard and extended temperature fan modules.
Refer to Ordering information and system engineering rules on page 8-1 for
the PEC information. Starting with OME6110 release 2.2, only the extended
temperature OME6110 system kit comes equipped with the fan module. The
fan module can also be ordered separately for sparing.
Fan module filler
The fan module filler is required to cover an unused fan slot. If a fan module
is not used the fan module filler must be used to cover the empty slot to ensure
EMI compliance.
ESD interface
The fan module filler contains an ESD interface used to connect an antistatic
wrist strap required when handling circuit packs to avoid damage as a result of
electrostatic discharge. Figure 4-6 on page 4-7 shows the location of the ESD
interface on the fan module filler of the OME6110.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Hardware description 4-7
Figure 4-6
OME6110 fan module filler
Refer to Ordering information and system engineering rules on page 8-1 for
the PEC information. Starting with OME6110 release 2.2, standard
temperature system kits come equipped with the fan module filler. The fan
module filler can also be ordered separately for sparing.
OAM and LCT ports
The base chassis of the OME6110 provides a local craft terminal (LCT) port
which allows for remote access to the network element via the data
communications network. In addition, the base chassis is equipped with four
OAM ports:
• alarm output
• alarm input
• M1/F1
• external synchronization input (ESI)
Figure 4-7 shows the OAM interfaces available on the base chassis. Table 4-3
provides a description of the OAM interfaces.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
4-8 Hardware description
PSU
Figure 4-7
OAM and LCT ports on base chassis
2
8
7
6
5
4
3
2
1
8XETH
ESD
Active
Status
RET GND -48V
Power
Optical Multiservice Edge 6110
-48Vdc 2A
Alm. Out
Alm. In
MI / F1
ESI
Alm. Out Alm. In
al
r
ic
rit
C
ajo
M
or
in
M
Rx
Tx
2
LCT
MI / F1
ESI
1
Tx 2 Rx
Tx 1 Rx
FAN
E1/DS1 1-16
1
LCT
Table 4-3
OAM and LCT port descriptions
Port
Physical interface
Description
Alarm output
• RJ-45 connector
• Alarm output port enables the customer to monitor the shelf
level alarms (Critical, Major and minor) onto external equipment,
such as lights or sirens.
• These contacts are normally open.
Alarm input
• RJ-45 connector
• Seven telemetry inputs enable the customer to connect external
environmental monitoring equipment to the OME6110 (for
example, door open indicator, fire alarm, and flood alarm).
M1/F1
• RJ-45 connector
• Remote dial-in access through modem to the OME6110.
• F1 user byte access (for clear channel access)
ESI
• RJ-45 connector
• Two external synchronization inputs for timing generation
references which enable the OME6110 to be timed from an
external timing reference of G.813 Option 1/stratum 3 (ST3) or
better quality. Both clock and data formats are supported.
• External synchronization outputs for timing distribution
references which enable other network elements to be timed
from the OME6110.
LCT
• RJ-45 connector
• Central office LAN provides switched 10/100Base-T
connectivity between the carrier’s DCN and the OME6110.
Refer to Connector pinouts on page 7-4 for details on the connector pinouts for
the OAM and LCT ports.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Hardware description 4-9
16 x E1/DS1 service interface
Each OME6110 base chassis is equipped with an integrated 16 x E1/DS1
electrical service interface. As shown in Figure 4-8 on page 4-9, the E1/DS1
service interface uses a 64-pin Telco Connector and allows for up to sixteen
120/100 ohm balanced E1/DS1 electrical ports.
An E1 termination panel can be used in order to offer 75 ohm unbalanced E1
services. For more information, refer to E1 75 ohm termination panel on page
4-17.
Figure 4-8
16 x E1/DS1 electrical interface connector
PSU
E1/DS1 1-16
2
8
7
6
5
4
3
2
1
8XETH
ESD
Active
Status
RET GND -48V
Power
Optical Multiservice Edge 6110
-48Vdc 2A
Alm. Out
Alm. In
MI / F1
ESI
LCT
al
r
ic
rit
C
ajo
M
or
in
M
Rx
Tx
2
1
Tx 2 Rx
Tx 1 Rx
FAN
E1/DS1 1-16
1
E1/DS1 functionality overview
The E1/DS1 electrical interfaces provide the following functionality:
• supports up to 16 E1/DS1 services (120/100 ohm balanced)
• mapping of E1/DS1 signals to VC12/VT2/VC11/VT1.5 containers
• support for framed E1 (CRC4) / DS1 (ESF) or clear channel (unframed)
signal monitoring
Note: DS1 super frame signals can be supported via the clear channel
(unframed) application.
•
•
•
•
supports E1/DS1 line PMs and path PMs for framed E1/DS1
supports unprotected and SNCP/UPSR traffic protection schemes
supports NE synchronization on the first five (5) E1/DS1 ports
Defaults to E1 or DS1 traffic on all 16 ports of the service interface
according to NE mode (SDH or SONET). A mix of E1 and DS1 traffic
services is not supported.
Note 1: Only SDH mode is supported for OME6110 Rel 1 chassis
(NT6Q50AA), where the 16xE1/DS1 service interface defaults to carry
unframed E1 signals only.
Note 2: The 16xE1/DS1 ports cannot be used if both ports of the optional
2x155M circuit pack are in use.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
4-10 Hardware description
Refer to the sections in OAM&P description on page 6-1 for more details on
functionality supported.
STM-1/OC-3 line interfaces
OME6110 supports pluggable optical transceivers for the two STM-1/OC-3
line interfaces. The STM-1/OC-3 interfaces use SFP optics for short reach,
intermediate reach, long reach, and CWDM access applications or an STM-1e
SFP for intra-office applications. Figure 4-2 on page 4-3 shows the
STM-1/OC-3 optical interface ports on the right side of the base chassis.
STM-1/OC-3 functionality overview
The STM-1/OC-3 optical interfaces provide the following functionality:
• supports OC-3 (SONET) or STM-1 (SDH) services
• auto-detection of SFP modules, which are hot pluggable
• auto provisioning of STM-1/OC-3 specific SFPs
• terminates RS/section and MS/line overhead
— terminates RS/section and MS/line overhead bytes in Rx direction
— inserts RS/section and MS/line overhead bytes in Tx direction
• RS/section DCC, MS/line or path DCC selectable (default is Off). Path and
RS/Section DCC can be enabled on both ports. MS/line DCC can be
enabled on both ports when the STM-1/OC-3 ports are in unprotected
configuration in MSP/APS configuration with route diversity enabled.
Note: Route diversity is now supported for 1+1 MSP/APS configurations.
When route diversity is enabled, DCC follows the active traffic path and
when it is disabled, DCC is active on both working and protection paths.
•
•
•
•
•
•
supports RS/section DCC or MS/line DCC transparency for pass through
functionality on overhead tunnels
supports RS/section, MS/line, path and tributary unit (TU) PMs
monitors transceiver values, such as optical received and transmit powers
(optical power is not applicable to STM-1e SFPs)
selectable automatic laser shutdown controlled by software. For STM-1e
SFPs, you must ensure that automatic laser shutdown is disabled (see
Provisioning and Protection Switching Procedures, 323-1853-310).
supports unprotected, 1+1 MSP/APS, and SNCP/UPSR traffic protection
schemes
line timing synchronization support (provides the handover between the
line timing and the shelf)
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Hardware description 4-11
For PEC information, see “Small form-factor pluggable optic modules” on
page 8-9. For optical specifications, see “Optical specifications” on page 7-23.
For STM-1e electrical specifications, see “Electrical specifications” on page
7-30. For more details on functionality supported, see relevant sections in
Chapter 6, “OAM&P description”.
Interface circuit pack descriptions
This section provides an overview of the OME6110 circuit packs. The circuit
packs can be equipped in the optional service module slot of the base chassis
(see Figure 4-2 on page 4-3).
OME6110 Release 2.2 supports the circuit packs listed in Table 4-4.
Table 4-4
OME6110 service modules
Interface circuit pack
Page
8x10/100BT L1 circuit pack
4-11
28xE1/DS1 circuit pack
4-13
3xE3/DS3 circuit pack
4-14
2x155M circuit pack
4-15
8x10/100BT L1 circuit pack
The 8x10/100BT L1 circuit pack can be installed in the optional service slot
on the OME6110 base chassis to offer Ethernet services. Figure 4-9 shows the
faceplate of a 8x10/100BT L1 circuit pack.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
4-12 Hardware description
In this release, the OME6110 offers three hardware versions of the
8x10/100BT L1 circuit pack, as summarized in Table 4-5.
Table 4-5
8x10/100BT L1 circuit pack versions
8x10/100BT L1 circuit
pack version
PEC code
Notes
8x10/100BT L1 Rev1
NT6Q13AA
• Standard Temperature
• This circuit pack is no longer
orderable
8x10/100BT L1 Rev2
NT6Q13AB
• Standard Temperature
• Up-release of the Rev 1
8x10/100BT L1 circuit pack
8x10/100BT L1 Rev2
(Ext Temp)
NT6Q13BA
• Extended Temperature
• Should be installed in an
extended temperature base
chassis
Note: Shielded Ethernet cables must be used to connect to the 10/100BT ports on
the 8x10/100BT L1 circuit pack. Refer to Ethernet service cable assemblies on
page 8-13 for ordering information.
Figure 4-9
8x10/100BT L1 circuit pack
8x10/100BT L1 functionality overview
The 8x10/100BT L1 circuit pack consists of two entities (client facing and line
facing):
• client facing interfaces referred to as Ethernet ports
• line facing (mapped for transport via SDH/SONET containers) interfaces
referred to as WAN ports
The 8x10/100BT L1 circuit pack supports the following:
• supports the transport of up to eight (8) 10/100BT services ports
• mapping of 10/100BT Ethernet to/from SDH/SONET containers via
Framed GFP at following levels:
— VC12/VT1.5 and VC3/STS-1 operating granularity
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Hardware description 4-13
•
•
•
•
•
•
— virtual concatenation (VC12/VT1.5-nv, where n=1 to 63 and
VC3/STS1-nv, where n = 1 to 3)
supports provisionable Ethernet link integrity (Enabled or Disabled)
supports provisionable Ethernet auto-negotiation (Enable or Disable) with
the local Ethernet link partner as per clause 37 of IEEE 802.3-2000
supports half or full duplex mode
64 byte to 1600 byte Ethernet frame support
supports provisionable Ethernet maximum transfer unit (MTU) between
64 and 1600 (default) bytes
supports Ethernet flow control capabilities
— Manual Tx-Rx (default), Manual Tx-Only, Manual Rx-Only
— None (advertises flow control not supported)
— Both (advertises asymmetric or symmetric flow control toward the
local device)
— Asymmetric (advertises asymmetric flow control toward the link
partner)
— Symmetric (advertises symmetric flow control toward the link partner)
Note: This attribute is ignored when auto-negotiation is disabled.
•
supports provisionable Link Capacity Adjustment Scheme (LCAS)
(Enabled or Disabled) as per G.7402/Y.1305
•
•
Ethernet and WAN PMs
supports standard or extended temperature operation
Note: Ethernet services map to SDH/SONET containers and are assigned
as WAN associations to the STM-1/OC-3 interfaces. They can therefore
use the traffic protection schemes supported by the STM-1/OC-3 optical
interfaces to provide a protected Ethernet service without the requirement
of a redundant handoff from the subtending Ethernet equipment.
Refer to Ordering information and system engineering rules on page 8-1 for
the associated PEC and the sections in OAM&P description on page 6-1 for
more details on functionality supported.
28 x E1/DS1 circuit pack
The 28 x E1/DS1 circuit pack can be installed in the optional service slot of the
OME6110 base chassis. Figure 4-10 shows the faceplate of a 28 x E1/DS1
circuit pack.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
4-14 Hardware description
In this release, the OME6110 offers two hardware versions of the 28 x E1/DS1
circuit pack, as summarized in Table 4-6.
Table 4-6
28xE1/DS1 circuit pack versions
28xE1/DS1 circuit
pack version
PEC code
Notes
28xE1/DS1
NT6Q10AA
Standard temperature
28xE1/DS1(Ext Temp)
NT6Q10BA
Extended temperature
Note: Right routing E1 and DS1 cables connecting to the 28xE1/DS1 circuit pack
must have a shielded connector. Refer to Table 7-21 on page 7-21 for details on
the shielded connector specifications.
Figure 4-10
28 x E1/DS1 circuit pack faceplate
28 x E1/DS1 functionality overview
The 28 x E1/DS1 circuit pack supports the following:
• supports up to 28 E1/DS1 services (120/100 ohm balanced)
• mapping of E1/DS1 signals to VC12/VT2/VC11/VT1.5 containers
• support for framed E1 (CRC4) / DS1 (ESF) or clear channel (unframed)
signal monitoring
• supports E1/DS1 line PMs and path PMs for framed E1/DS1
• supports unprotected and SNCP/UPSR traffic protection schemes
• supports NE synchronization on any of 1, 4, 7, 10, 13, 16, 19, 22, 25 or 28
E1/DS1 ports
• can be configured to carry either E1 traffic or DS1 traffic on all 28 ports of
the circuit pack, independent of the NE mode (SDH or SONET). A mix of
E1 and DS1 traffic services is not supported.
Refer to the sections in OAM&P description on page 6-1 for more details on
functionality supported.
3 x E3/DS3 circuit pack
The 3 x E3/DS3 circuit pack can be installed in the optional service slot of the
OME6110 base chassis. Figure 4-11 shows the faceplate of a 3 x E3/DS3
circuit pack.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Hardware description 4-15
In this release, the OME6110 offers two hardware versions of the 3 x E3/DS3
circuit pack, as summarized in Table 4-7.
Table 4-7
3xE3/DS3 circuit pack versions
3xE3/DS3 circuit pack
version
PEC code
Notes
3xE3/DS3
NT6Q12AA
Standard temperature
3xE3/DS3 (Ext Temp)
NT6Q12BA
Extended temperature
Figure 4-11
3 x E3/DS3 circuit pack faceplate
3XE3DS3
3 x E3/DS3 functionality overview
The 3 x E3/DS3 circuit pack supports the following:
• supports up to 3 E3/DS3 services (75 ohm)
• mapping of E3/DS3 signals to VC3/STS1 containers
• support for framed E3 (G.832) / DS3 (M13 or C-BIT) or unframed signal
monitoring
• supports E3/DS3 line and path PMs
• supports unprotected and SNCP/UPSR traffic protection schemes
• each port can be independently configured to carry E3 or DS3 traffic. A
mix of E3 and DS3 services is supported.
2x155M circuit pack
The 2x155M circuit pack can be installed in the tributary slot of the OME6110
chassis. Figure 4-12 shows the faceplate of a 2x155M circuit pack.
The 2x155M circuit pack supports pluggable optical and electrical transceivers
for the two STM-1/OC-3 interfaces. The STM-1/OC-3 ports use small
form-factor pluggable (SFP) interfaces to deliver optical and electrical rate and
reach flexibility on a per port basis. The STM-1/OC-3 optical interfaces use
SFP modules for short reach, intermediate reach and long reach service
applications. The STM-1/OC-3 electrical interfaces use SFP modules for intra
office applications. Figure 4-12 shows the STM-1/OC-3 interface ports on the
center of the 2x155M circuit pack.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
4-16 Hardware description
The PEC for the 2x155M circuit pack is listed in Table 4-8.
Table 4-8
2x155M circuit pack
2x155M circuit pack
PEC code
2x155M
NT6Q17ABE5
Figure 4-12
2x155M circuit pack faceplate
2x155M functionality overview
The 2x155M circuit pack supports the following:
• supports up to 2 STM-1/OC-3 optical (o) or electrical (e) services
•
•
•
•
Note 1: Simultaneous use of both ports of the 2x155M tributary card is
allowed. In this setup the 16xE1/DS1integrated in the chassis cannot be
used.
Note 2: Simultaneous use of 16xE1/DS1 integrated in the chassis and the
first port of the 2x155M tributary card is allowed. In this setup the second
port of the 2x155M tributary card cannot be used.
auto-detection of SFP modules, which are hot pluggable
auto provisioning of STM-1/OC-3 specific optical and electrical SFPs
supports single fiber working (SFW) SFPs at the STM-1/OC-3 rate
terminates RS/section and MS/line overhead
— terminates RS/section and MS/line overhead bytes in Rx direction
— inserts RS/section and MS/line overhead bytes in Tx direction
• RS/section DCC selectable (default is Off)
• MS/line DCC selectable (default is Off)
• supports IP layer 3 protocol, MTU =240 and OSPF routing protocol for
DCC
•
up to six nodes can be supported through each 2x155M tributary DCC
• supports RS/section DCC or MS/line DCC transparency for pass through
functionality on overhead tunnels
• supports RS/section, MS/line, path and tributary unit (TU) PMs
• monitors transceiver values, such as optical received and transmit powers
• selectable automatic laser shutdown controlled by software
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Hardware description 4-17
• supports unprotected, 1+1 MSP/APS, and SNCP/UPSR traffic protection
schemes
•
Note 1: 1+1 MSP/APS protection group members must be of the same
slot.
supports route diversity enabled in 1+1 MSP/APS protection scheme
• line timing synchronization support (provides the handover between the
line timing and the shelf)
Refer to the sections in OAM&P description on page 6-1 for more details on
functionality supported.
Filler faceplate
The filler faceplate is required to cover the unused optional service slot. If no
additional circuit packs are required a filler faceplate must be used to cover the
empty slot to ensure proper airflow through the base chassis and to ensure EMI
compliance. Figure 4-2 on page 4-3 displays the base chassis with a filler
faceplate installed over the optional service slot.
Refer to Ordering information and system engineering rules on page 8-1 for
the associated PEC. The filler faceplate comes equipped with the base chassis,
but can also be ordered separately for sparing.
E1 75 ohm termination panel
The conversion from 120 ohm to 75 ohm E1 service interfaces can be achieved
for:
• the 16 x E1/DS1 service interface on the base chassis
• the 28 x E1/DS1 circuit pack
The conversion is achieved by connecting the Telco connectors of the 16 x
E1/DS1 service interface or the 28 x E1/DS1 circuit pack to a 1U high
16-channel termination panel. The termination panel is equipped with 16 BNC
connectors. This 75 ohm termination panel can only be used for E1 services.
Note: The 75 ohm termination panel is labeled from 1-16 by default, but
includes an additional overlay label which can be installed by the user
when connecting the ports 17-28 of the 28xE1/DS1 circuit pack.
A 64-pin to 64-pin male connector cable must be used to connect to the
termination panel. For more information regarding the 75 ohm termination
panel and the cable pinout information, refer to E1/DS1 cable pinouts and
assemblies on page 7-17
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
4-18 Hardware description
Cable routing
The cable routing brackets which are installed at either side of the OME6110
shelf allows for the management of the power cables, OAM & LCT cables,
optical fibers and the Ethernet/DSn/PDH service cables. The cable routing
brackets are placed over the mounting brackets during the installation of the
OME6110 shelf. Refer to Figure 4-13 for the various mounting and cable
routing brackets supported for OME6110.
For more information on the installation of the cable routing brackets, refer to
Installation, Commissioning and Testing Procedures, 323-1853-201. The
cable routing brackets come as part of the OME6110 assembly kit. Refer to
Ordering information and system engineering rules on page 8-1 for ordering
details of the OME6110 shelf assembly kit.
Figure 4-13
OME6110 mounting and cable routing brackets
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
5-1
User interface description
5-
This chapter provides an overview of the craft user interface available for the
Optical Multiservice Edge 6110 (OME6110) Release 2.2. Table 5-1 lists the
topics in this chapter.
Table 5-1
Topics in this chapter
Topic
Page
OME6110 local craft access terminal
5-1
SNMP traps
5-2
OME6110 local craft access terminal
The OME6110 local craft access user interface is a graphical, nodal
management tool that is available inherently on the network element software.
The local craft access user interface is launched via an HTTP web-browser that
runs on any computing platform. Table 5-2 provides a list of minimum
requirements for various web browsers. The craft user interface provides full
access to the OME6110 network element across TCP/IP and to other
OME6110 network element visible across DCC or locally across the network
element's LCT port.
Table 5-2
OME6110 local craft access terminal requirements
Web browser
Supported version
OS platform
Microsoft Internet
Explorer
6.x
• Win2K
Mozilla
1.6 and 1.7
• WinXp
• Red Hat Linux
• HP-UX
• Solaris 9.0
FireFox
1.5
• Red Hat Linux 7.x
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
5-2 User interface description
The local craft access terminal provides support for the following functions:
• fault and alarm management
• equipment and facility management
• shelf level view
• PM viewing and threshold setting
• synchronization management
• upgrades and software download
• backup and restore
• protection status and control
• nodal security management
• nodal connection management
• DCN communications management
• SNMP trap destination provisioning
Refer to Chapter 6, OAM&P description for more information about the
operations, administration, maintenance and provisioning (OAM&P)
capabilities supported by the OME6110 Release 2.2.
For more information on the Local Craft Access Terminal and the supported
applications, refer to the Local Craft Access User Guide, 323-1853-195.
SNMP traps
The OME6110 supports autonomous forwarding of system events through
SNMP traps for consolidated alarm reporting. The SNMP traps are sent to an
SNMP manager, such as HP Open View, where they can be used to alert a
system operator.
Up to eight SNMP trap managers can be provisioned for each OME6110
network element. For each trap destination, the IP address and the SNMP
version (v1 or v2) are provisioned.
For more information on how to provision the SNMP trap destinations, refer
to Provisioning and Protection Switching Procedures, 323-1853-310.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-1
OAM&P description
6-
This chapter provides the operations, administration, maintenance and
provisioning (OAM&P) description for the Optical Multiservice Edge 6110
network element. Table 6-1 lists the topics in this chapter.
Table 6-1
Topics in this chapter
Topic
Page
Global support
6-2
System Line-up and Test (SLAT)
6-3
Network element management
6-4
Equipment management
6-4
Facility management
6-5
Loopbacks
6-6
Synchronization management
6-8
Connection management
6-15
Traffic protection
6-18
1+1 MSP/APS traffic protection
6-20
SNCP/UPSR Traffic Protection
6-21
Unprotected connections
6-23
Data communications
6-23
Alarm and event management
6-30
Performance monitoring
6-35
Security and administration
6-40
Topology adjacency
6-44
Backing up and restoring the network element database
6-44
Installing and upgrading network element
6-45
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-2 OAM&P description
Global support
Optical Multiservice Edge 6110 is a global platform that can be deployed in
both SONET and SDH environments. The network element (NE) mode
determines the overall function of the network element in either a SONET or
SDH environment.
The user uses the Configure Node page from the Local Craft Terminal to set
the NE mode to either SONET or SDH during initial commissioning.
Note: You cannot change the mode from SONET to SDH or vice versa
while in-service. To change the mode of the network element, you must
first use the “Restore factory default” application to delete all
configuration, events, and PM data. Power cycle the network element and
then use the Configure Node page to enter the required commissioning
information and NE mode or to restore from a saved configuration.
The NE mode defines the defaults for some provisioning items as detailed in
Table 6-2. Some of these provisioning items can be overridden after the user
sets the NE mode.
Note: All other provisioning items are independent of the NE mode (for
example, OAM comms and security).
Table 6-2
NE mode - differences between SONET and SDH
Provisioning item
SONET mode
SDH mode
Port mode
Optical ports support OC-n
interfaces
Optical ports support STM-n
interfaces
Linear protection mode
Supports 1+1 APS linear
(Telcordia GR-253)
Supports 1+1 MSP linear
(ITU-T G.841)
Ring protection terminology
Uses UPSR
Uses SNCP
16xE1/DS1 service
DS1 service only
E1 service only
ESI/ESO mode
Supports DS1 (1.5 Mbit/s)
interfaces
Supports 2 MHz and E1
(2 Mbit/s) interfaces
SSM format
Optical and ESI/ESO ports use
SONET quality levels
Optical and ESI/ESO ports use
SDH quality levels
PMs
Supports bit based PMs
Supports block based PMs
Connection terminology
Uses VT and STS
Uses VC
Cannot be overridden by user
Can be overridden by user
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-3
Table 6-2 (continued)
NE mode - differences between SONET and SDH
Provisioning item
SONET mode
SDH mode
28xE1/DS1 service
E1 or DS1 for all ports
E1 or DS1 for all ports
3xE3/DS3 service
E3 or DS3 service for each port
E3 or DS3 service for each port
2x155M service
OC3 for each port
STM1 for each port
System Line-up and Test (SLAT)
System Line-up and Test (SLAT) is a two part process consisting of
commissioning an OME6110 network element and system testing.
Commissioning brings a newly installed OME6110 network element to an
in-service state ready to carry traffic. System testing consists of performing a
traffic continuity and performance test of the network.
Commissioning process
The commissioning process starts after completion of the installation of the
OME6110 base chassis into a 19”, 23” or ETSI rack, circuit pack in the
optional service slot, service cables and optical fibers routed but not connected,
and power cables connected but power switched off.
The commissioning process can be broken down into the following phases:
• network element powering up
In this phase, the user verifies the network element equipment and the
power supply, and then powers up the shelf.
•
network element commissioning
In this phase, the user logs in to the OME6110 network element by
connecting to the LCT port on the base chassis. The user uses the SLAT
WUI page to either restore a saved configuration onto the new network
element or manually enter the network element commissioning data, DCN
parameters and NE software mode (SONET or SDH).
Note: For OME6110 Release 1 base chassis (NT6Q50AA), the NE mode
is default to SDH only.
Testing process
The testing process occurs after the user has completed the powering up and
commissioning of the OME6110 network element. The testing process
consists of a system level test as follows:
• system testing
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-4 OAM&P description
The user performs system testing after all the network elements for a
system are physically connected into a linear or ring configuration. In this
phase, the user sets up and verifies the system configuration, connects the
test equipment, establishes a loopback, provisions a traffic connection, and
performs a traffic continuity and performance test on the system.
Refer to Installation, Commissioning and Testing Procedures, 323-1853-201,
for detailed installation, commissioning, and system testing procedures.
Network element management
NE information page is an application that allows you to retrieve general
information for the network element. You can display and/or edit different
network element parameters (general, IP provisioning,).
Equipment management
In OME6110, equipment is a logical entity and is the software representation
of a circuit pack. The user provisioned data about a circuit pack is stored in the
corresponding equipment object and the equipment object is not deleted from
the node inventory list when a circuit pack is removed. The equipment entities
for the OME6110 platform are as follows:
• chassis
• power supply unit
• 16 x E1/DS1 service interface
• 2 x 155M optical ports and cross-connect
• 8 x 10/100BT L1 circuit pack
• 28 x E1/DS1 circuit pack
• 3 x E3/DS3 circuit pack
• 2 x 155M circuit pack
• fan module
• SFP optical modules
The OME6110 supports automatic detection of new circuit packs in the
optional service slot. After insertion of a circuit pack in a previously
unprovisioned optional slot, the system autoprovisions the circuit pack with
default values and places the circuit pack in-service. The circuit packs are
immediately visible in the OAM&P management system through applications
such as Node inventory and Node slot view. Similarly, the SFP modules
inserted into the STM-1/OC-3 ports are automatically detected and are
auto-provisioned in-service. The SFP status and details are presented in the
Node inventory application.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-5
Before you can remove the equipment provisioning of a circuit pack from the
inventory, you must physically remove the module from its slot. For more
information, refer to Provisioning and Protection Switching Procedures,
323-1853-310.
Facility management
A facility represents an equipment’s OAM&P capabilities that allows the user
to provision, inspect, and control that interface. For the OME6110, a facility
represents optical or service interfaces, such as:
• STM-1/OC-3 optical interfaces on the base chassis
• STM-1/OC-3 optical and electrical interfaces on the 2x155M circuit pack
• E1/DS1 interface ports on the base chassis and on the 28xE1/DS1 circuit
pack
• E3/DS3 interface ports on the 3xE3/DS3 circuit pack
• Ethernet interface ports on the 8x10/100BT L1 circuit pack
• WAN ports associated to Ethernet interface ports
For a complete list of editable and retrievable facility parameters, refer to
Provisioning and Protection Switching Procedures, 323-1853-310.
Managing facilities
Facility provisioning is a nodal function that allows you to query and edit
facility attributes on a specific interface.
The user manages facilities from the corresponding application menu in the
Provisioning main menu:
• OCn/STM
• E1/E3/DS1/DS3
• Ethernet
• WAN
By default, the facility is Admin down. When a cross-connect is provisioned
with a PDH/DSn facility, its Admin status is automatically changed to Admin
Up. When you change a facility from Admin Up to the Admin Down state, the
following occurs:
• OCn/STM facility
— traffic will not be carried on the port
— Tx laser is shut off
— alarms present on the port are cleared
— alarm conditions are not declared
— performance monitoring is terminated
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-6 OAM&P description
•
•
— DCC will be disabled
E1/E3/DS1/DS3 facility
— traffic will not be carried on the port
— alarms present on the port are cleared
— alarm conditions are not declared
— performance monitoring is terminated
Ethernet facility
— traffic will not be carried on the port
— Client Signal Fail will be sent on the WAN facility
— alarms present on the port are cleared
— alarm conditions are not declared
— performance monitoring is terminated
Note: The WAN state follows the state of the associated Ethernet port. If
an Ethernet facility is placed in admin down state, the corresponding WAN
state will automatically be placed to admin down.
Loopbacks
The OME6110 supports loopbacks on STM-1/OC-3, E3/DS3, E1/DS1, and
Ethernet ports:
• Facility - the received signal is looped back towards the transmitter port
immediately on entering the interface port. AIS is inserted in the signal
towards the cross-connect on the base chassis.
• Terminal - the signal is looped back towards the cross-connect on the base
chassis just before reaching the interface transmitter.
Figure 6-1 provides an overview of terminal and facility loopbacks.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-7
Figure 6-1
Facility and terminal loopbacks
Facility loopback
Terminal loopback
AIS
Rx
Rx
Tx
Tx
STM-1/OC-3 optical interface ports
E1/DS1 and E3/DS3 services
Terminal loopback
Rx
Ethernet
interface
Tx
Ethernet interface ports
Table 6-3 on page 6-7 summarizes the supported loopback types for the
different ports and the appropriate AIS alarm conditioning.
Table 6-3
Loopbacks and AIS alarm conditioning
Port type
Facility loopback
AIS injection on
facility loopback
Terminal
loopback
AIS injection on
terminal loopback
STM-n/OC-n
Yes
Yes
Yes
No
E3/DS3
Yes
No
Yes
Yes
E1/DS1
Yes
Yes
Yes
Yes
Ethernet
No
No
Yes
No
The user performs loopbacks on an Ethernet, DS1/E1, DS3/E3, and
STM-1/OC-3 ports from the Maintenance application in the main menu of the
local craft access terminal. A facility and a terminal loopback cannot be
performed on the same interface port at the same time.
For complete procedures, refer to Provisioning and Protection Switching
Procedures, 323-1853-310.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-8 OAM&P description
Synchronization management
Synchronization is a network level application that ensures all nodes across a
network can trace back to the same clock source. Within a single node,
synchronization prevents buffer overflow or underflow which avoids bit errors.
Synchronization provisioning on the OME6110 is nodal based. However
synchronization must be planned at a network level to avoid hierarchy
violations and timing loops that cause excessive jitter and can result in traffic
loss.
A network level synchronization plan must take into consideration the
requirements for synchronization sources to be used for timing generation and
timing distribution. A detailed plan must be available to define how to
provision the synchronization parameters on the OME6110 network element
at each site.
Timing generation
Timing generation is the ability of the OME6110 to extract and use the
synchronization reference from any of the defined synchronization inputs. The
OME6110 generates shelf timing signals based on external, line or internal
(freerun or holdover) references. The OME6110 supports a timing generation
hierarchy for two timing references.
The OME6110 is capable of generating a 4.6 ppm quality clock internally. This
clock is the default synchronization reference. The OME6110 supports
synchronizing to a reference clock signal derived from the following sources
(provisioned by the user as defined by the network synchronization plan):
• internal timing
When the internal clock is provisioned as a timing reference, the network
element goes to internal freerun mode rather than holdover mode, when the
internal clock becomes the active timing reference. See Figure 6-2 on page
6-11 example (a).
• external timing
As shown in Figure 6-2 on page 6-11 example (b), from the external
synchronization input (ESI) port on the base chassis, the OME6110
supports external timing reference inputs. The supported BITS
combinations are detailed in Table 6-4 on page 6-8 below:
Table 6-4
Supported BITS combinations
NE mode
SDH
SONET
Optical Multiservice Edge 6110
BITS-1-4-1
BITS-1-4-2
2 MHz
2 MHz
E1 (2 Mbs)
E1 (2 Mbs)
DS1
DS1
DS1
DS1
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-9
The following needs to be considered when using an external source to provide
the timing reference for the OME6110:
— the external timing source and its quality
— the signal format of the external timing source (DS1 ESF for SONET,
E1 or 2.048 MHz for SDH)
— the connector type/impedance of the ESI port (120/100 ohm balanced
or 75 ohm unbalanced)
Note: DS1 timing reference sources with superframe (SF) framing format
should be provisioned as a line timing source originating from the 16 x
E1/DS1 service interface or the 28xE1/DS1 circuit pack, rather than an
external timing source.
•
line timing
Line timing is a clock derived from an STM-1/OC-3 interface or an
E1/DS1 port from the 16 x E1/DS1 service interface on the base chassis or
the 28xE1/DS1 circuit pack. See Figure 6-2 on page 6-11 example (c).
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-10 OAM&P description
When using line timing to provide the timing reference for the OME6110,
you may consider one of the following sources:
— any of the STM-1/OC-3 ports
— any of the first five (5) E1/DS1 ports of the 16 x E1/DS1 service
interface on the base chassis
— any of 1, 4, 7, 10, 13, 16, 19, 22, 25, 28 E1 /DS1 ports of the 28 x
E1/DS1 circuit pack
The OME6110 can identify a faulty synchronization source and switch to the
next highest quality source as defined in the input hierarchy. When all
synchronization sources (external or line) are unavailable (caused by faulty
sources or lockouts), the OME6110 falls into holdover mode. In the holdover
mode, the internal clock operates at a fixed frequency according to the last
known frequency reference for a minimum of 24 hours followed by freerun
mode (internal stratum 3 [ST3]/G.813 Option 1 compliant 4.6ppm clock). See
Figure 6-2 on page 6-11 example (a).
Refer to Viewing and management on page 6-14 for information about the
Synchronization application in the Configuration main menu of the local
craft access terminal for the OME6110.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-11
Figure 6-2
Flow of synchronization timing signals
Stratum 3/G.813
Option 1 or better
OME6110 faceplate
Port
Clock
Port
OME6110 faceplate
Port
Port
Base chassis
Base chassis
(a) Internal timing
(b) External timing
OME6110 faceplate
Port
Port
Base chassis
(c) Line timing
Legend
Port
Clock
Service interface port
Internal clock generator
Synchronization timing
External synchronization reference
Traffic flow
Timing distribution
Timing distribution is the ability of the OME6110 to provide a synchronization
reference to external devices. The OME6110 supports the following timing
distribution reference signals:
• CLKOUT or DATAOUT ports on the ESI port located on the faceplate of
the base chassis
• any of the two STM-1/OC-3 optical interfaces
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-12 OAM&P description
The following items need to be considered when using the OME6110 as a
timing source.
• the signal format of the external timing source (DS1 for SONET, E1 or
2.048 MHz for SDH)
• the connector type/impedance of the ESI port (120/100 ohm balanced or
75 ohm unbalanced)
• the reference sources to be used for timing distribution and the hierarchy
Synchronization operating modes
The OME6110 synchronization operating modes describe the state that the
synchronization hardware is operating in. These modes are not provisionable
by the user and consists of the following:
• freerun
• locked
• holdover
Freerun mode
In freerun mode, the system clock is not locked to a timing reference and runs
at its natural frequency. The synchronization hardware on the base chassis
provides timing references quality as specified in internal stratum 3
(ST3)/G.813 Option 1 (4.6 ppm). The OME6110 is in this mode if the user has
provisioned the shelf timing as internal or the holdover period has expired in
which case a warning condition is raised to advise the user.
Locked mode
In locked mode, the system clock is locked to a timing reference. The
OME6110 is in this mode when a timing reference is active and working
during trouble free operations.
Holdover mode
The synchronization hardware enters holdover mode automatically if the target
mode is locked but all timing references have become unavailable. The system
clock in the synchronization hardware holds within a certain frequency range
of the last locked-in timing reference in which case a warning condition is
raised to advise the user.
When a timing reference becomes available again, the synchronization
hardware automatically transitions to locked mode. The synchronization
hardware remains in holdover mode for a minimum of 24 hours. After
holdover mode, the synchronization hardware enters the freerun mode.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-13
Synchronization status messages
Synchronization status messages (SSM) indicate the quality of the timing
signals currently available to a network element. The timing sources that can
be provisioned in a network element include external timing (ESI), line timing
(timing derived from STM-1/OC-3 interfaces or E1/DS1 signals), and the
internal clock of the network element.
A network element can select the best of the two timing signals provided by
the timing sources provisioned by the user. The selection is based on the
quality values carried in the SSMs. As the timing passes from one network
element to the next, each network element sends SSMs. If the quality of the
timing changes, the SSMs inform the next network element of the change.
If a timing reference is not to be used for synchronization, the SSM will
contain a do not use for synchronization (DNU) message. See Table 6-5 on
page 6-13 for an overview of SSM designations supported by OME6110 in
SDH mode and see Table 6-6 on page 6-13 for the SSM designations in
SONET mode.
Table 6-5
Synchronization status messages in SDH mode
Description
Designation
Quality
Level
S1 bits (5-8)
PRC
2
0010
Traceable to Transit Clock
SSU-A
4
0100
Traceable to Local Clock
SSU-B
8
1000
Traceable to SDH Equipment Clock
SEC
11
1011
Do Not Use for Synchronization
DNU
15
1111
Designation
Quality
Level
S1 bits (5-8)
Stratum 1 Traceable
PRS
1
0001
Synchronized - Traceability Unknown
STU
2
0000
Stratum 2 Traceable
ST2
3
0111
Transit Node Clock Traceable
TNC
4
0100
Stratum 3E Traceable
ST3E
5
1101
Traceable to Primary Reference Clock
Table 6-6
Synchronization status messages in SONET mode
Description
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-14 OAM&P description
Table 6-6 (continued)
Synchronization status messages in SONET mode
Description
Designation
Quality
Level
S1 bits (5-8)
Stratum 3 Traceable
ST3
6
1010
SONET Minimum Clock Traceable
SMC
7
1100
Don’t Use for Synchronization
DUS
9
1111
Note 1: If the incoming quality level is not recognized by the OME6110,
the quality level is displayed as invalid. To use a timing source with an
invalid quality level as a timing reference, the user must override the
invalid quality level.
Note 2: The incoming quality level can not be overwritten if the timing
source is an optical port.
Quality level overrides
A user can specify or override the SSM quality level of an outgoing timing
source.
The outgoing override can be used when a remote network element expects a
particular SSM value.
Viewing and management
The network element provides all required synchronization source information
from the local craft access terminal. The Synchronization application in the
Configuration main menu allows users to view and provision synchronization
parameters for an OME6110 network element.
For complete procedures, refer to Provisioning and Protection Switching
Procedures, 323-1853-310.
Synchronization protection
Synchronization protection deals with the protection of the timing references.
The OME6110 supports the protection of the timing reference used for timing
generation. The timing generation reference for the system is selected from the
pool of provisioned reference sources.
From the local craft access terminal, the Timing Manager application in the
Protection main menu displays the protection status of the provisioned
synchronization hierarchies for the network element. The application shows
current quality level, the clock status, and any active synchronization
protection switches on the sources for each hierarchy. Synchronization
protection switches include the following:
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-15
•
•
•
•
automatic switch
manual switch
forced switch
lockout
For more information synchronization protection, refer to Provisioning and
Protection Switching Procedures, 323-1853-310.
Connection management
In the OME6110 architecture, traffic is switched between interface ports on the
base chassis or circuit packs through the cross-connect unit.
OME6110 supports the following connection management capabilities:
• fully non-blocking cross-connects at VC11/VT1.5, VC12/VT2 and
VC3/STS-1 granularity
• virtual concatenated connections for VC12/VT1.5-nv, n = 1 to 63 or
VC3/STS-1-nv, n = 1 to 3 for the Ethernet ports
• PDH/DSn signals mapping:
— E1 to VC12/VT-2
— E3 to VC3/STS-1
— DS1 to VC11/VT-1.5
— DS3 to VC3/STS-1
• bandwidth management models:
— bidirectional (2WAY) connection type
— unidirectional (1WAY) connection type
— hair-pinning
All services (Ethernet, E1/DS1 and E3/DS3) are mapped to the appropriate
VT/STS/VC containers. The OME6110 uses Generic Framing Procedure
(GFP) as its standards based SDH/SONET mapping for Ethernet services.
Note: Only bidirectional (2WAY) connection type is supported for
Ethernet/WAN ports.
Generic Framing Procedure
GFP is an ITU standard (G.7041) which describes a flexible mapping
technique for transparent transport of multiple protocols in SDH and SONET.
GFP provides an efficient mechanism for Ethernet data services to be
transported over an SDH/SONET network via efficiently mapping varying
client signals into VT/STS/VC containers with a virtual concatenation group
(VCG). OME6110 supports:
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-16 OAM&P description
•
Framed-mapped GFP (GFP-F), which maps one frame or packet of client
signal in one GFP frame. GFP-F processes client signal data streams on a
protocol data unit (PDU) basis and maps these streams into GFP-F frames
one packet at a time. GFP-F is recommended for Ethernet services as it
provides flow control capability and performance monitoring.
In GFP-F, idle frames are inserted as necessary to fill the transport payload.
Multiple GFP-F frames can be aggregated in a single SDH/SONET payload.
Table 6-7 provides a summary of the service mappings and interconnection
type supported by the OME6110.
Table 6-7
OME6110 service mapping
Service
Mapping
Interconnection type
10/100BT • SDH mode:
L1
— GFP-F to VC12 and VC3
Ethernet
— GFP-F to VC12-nv (n=1 to 63)
and VC3-nv (n=1 to 3)
E1
• SDH mode:
— non-concatenated at VC12 and VC3 level
— virtual concatenation at VC12-nv (n=1 to 63)
and VC3-nv (n = 1 to 3) for the VCG
• SONET mode:
• SONET mode:
— GFP-F to VT1.5 and STS-1
— non-concatenated at VT1.5 and STS-1 level
— GFP-F to VT1.5-nv (n=1 to 63)
and STS-1 (n=1 to 3)
— virtual concatenation at VT1.5-nv (n=1 to 63)
and STS-1 (n=1 to 3)
• VC12/TU12/AU4 (SDH mode)
• non-concatenated at VT2/VC12 level
• VT2/STS1 (SONET mode)
DS1
• VC11/TU11/AU4 (SDH mode)
• non-concatenated at VT1.5/VC11 level
• VT1.5/STS-1 (SONET mode)
E3/DS3
• VC3/TU3/AU4 (SDH mode)
• non-concatenated at STS-1/VC3 level
• STS-1 (SONET mode)
Ethernet and PDH services are mapped to SDH/SONET containers and
assigned as SDH/SONET level connections to optical interfaces. The traffic
protection schemes supported by the STM-1/OC-3 interfaces can therefore be
used to provide a protected Ethernet, E1/DS1 or E3/DS3 service without the
requirement of a redundant handoff from the subtending Ethernet, E1/DS1 or
E3/DS3 equipment. See Traffic protection on page 6-18 for more information.
Hair-pinning
The OME6110 provides the ability to provision hairpin connections for PDH
services.
• E1-to-E1
• DS1-to-DS1
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-17
•
•
E3-to-E3
DS3-to-DS3
Connection management application
OME6110 connection management is based on a nodal, port-to-port
connection management philosophy that takes protection schemes into
account to rearrange connections at the physical level to implement traffic
protection. See Traffic protection on page 6-18 for more details.
The Cross-connect application in the Configuration main menu of the local
craft access terminal allows the user to perform the following:
• filter, and display nodal connections
• provision nodal connections from any DS1/E1/DS3/E3 interface port to
any available timeslot of an STM-1/OC-3 optical interface or of another
E1/DS1/E3/DS3 interface port on the same OME6110 network element.
Each cross-connect can have a Circuit Identifier which allows the user to
label the cross-connect.
Note: The systems blocks any cross-connects that are illegal. For example,
if a low-order VC12/VT1.5 cross-connect is provisioned, the system
blocks cross-connects of the corresponding VC3/STS.
•
•
operate or release user-initiated switch commands on SNCP/UPSR
connections.
delete a nodal connection (supports multiple deletes)
The WAN application in the Facilities menu of the local craft access terminal
allows the user to perform the following:
•
•
•
•
provision VC/VT/STS associations within a WAN from any Ethernet
interface port to any available timeslot of an STM-1/OC-3 optical interface
on the same OME6110 network element.
operate or release user-initiated switch commands on SNCP/UPSR
VC/VT/STS connections.
delete a VC/VT/STS association within a WAN (supports multiple deletes)
click on hyperlink to Cross-connect application to filter, display or delete
nodal connections.
SDH payload instance numbering
In the local craft access terminal, SDH payload instances are displayed using
K, L, and M format where:
• K is the TUG-3 payload number (1 to 3)
• L is the TUG-2 payload number (1 to 7)
• M is the TU-12 payload number (1 to 3) or TU-11 payload number (1 to 4)
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-18 OAM&P description
For example, a format of K = 2, L = 6, M=2 identifies:
• TUG-3 number 2
• TUG-2 number 6
• TU-12/TU-11 payload number 2
SONET payload instance numbering
In the local craft access terminal, SONET payload instances are displayed
using STS #, VT Group, and VT # format where:
• STS # is the STS-1 payload number (1 to 3)
• VT Group is the VTG payload number (1 to 7)
• VT # is the VT2 payload number (1 to 3) or VT1.5 payload number (1 to 4)
For example, a format of K = 2, L = 6, M=2 identifies:
• STS-1 number 2
• VTG number 6
• VT2/VT1.5 payload number 2
For detailed procedures and associated rules, refer to Provisioning and
Protection Switching Procedures, 323-1853-310.
Traffic protection
Traffic protection is a mechanism to enhance the dependability of a transport
service. The OME6110 provides a variety of protection mechanisms which
can be deployed to tailor the resilience of the platform to that required by the
customer. The system monitors the traffic facilities for performance
degradation and failure and performs protection switching when these
conditions are present. The following traffic protection configurations are
currently available:
•
•
•
unprotected
1+1 Multiplex Section Protection (MSP)/Automatic Protection Switching
(APS)
Unidirectional Path Switch Ring (UPSR)/Sub-Network Connection
Protection (SNCP)
Table 6-8 provides an overview of the supported traffic protection schemes.
The OME6110 can be provisioned to support MSP/APS protection on the
STM-1/OC-3 interfaces or to support a mix of unprotected and SNCP/UPSR
configurations on a single network element. Refer to Refer to Table 8-3 for
OME6110 equipment rack space requirements. on page 8-4 for more
information.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-19
Table 6-8
Traffic protection summary
Protection
scheme
Interfaces
Notes
Unprotected
STM-1/OC-3 interfaces
E1/DS1 services
E3/DS3 services
10/100BT EPL services
A mix of unprotected and
SNCP/UPSR connections
can be provisioned.
1+1 MSP/APS
STM-1/OC-3 interfaces
When MSP/APS is
provisioned, SNCP/UPSR
connections are not
supported.
SNCP/UPSR
STM-1/OC-3 interfaces
E1/DS1 services
E3/DS3 services
10/100BT L1 services
STM-1/OC-3 interfaces
must be provisioned in
Unprotected mode.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-20 OAM&P description
Traffic Protection application
The user performs provisioning of traffic protection by selecting the
MSP/APS groups application in the Configuration main menu of the local
craft access terminal. The protection provisioning application displays the
protection provisioning data and allows the user to perform the following
actions:
• view the protection switch scheme and protection switch mode for the
STM-1/OC-3 optical interfaces
• change the protection scheme from 1+1 MSP/APS to unprotected for the
STM-1/OC-3 optical interfaces
• change the protection scheme from unprotected to 1+1 MSP/APS for the
STM-1/OC-3 optical interfaces
• operate or release a user-initiated switch request on the 1+1 MSP/APS
group for the STM-1/OC-3 optical interfaces
The SNCP/UPSR protection configuration is provisioned upon creation of the
nodal cross-connect or the VC/VT association for Ethernet services. For more
details on the local craft access terminal applications used to provision
SNCP/UPSR traffic protection, refer to Connection management application
on page 6-17
Note: The default traffic protection mode on the OME6110 network
element is unprotected.
1+1 MSP/APS traffic protection
1+1 MSP/APS traffic protection is supported for the STM-1/OC-3 optical
interfaces to provide line traffic protection. 1+1 MSP/APS traffic protection
uses the 1+1 MSP/APS protocol to handshake between adjacent network
elements to determine when a protection switch should occur. All of the
paths/payloads within the line are protected together.
Provisioning MSP/APS protected connections
The user performs protection group provisioning from the MSP/APS groups
application in the Configuration main menu of the local craft access terminal.
The user creates the 1+1 MSP/APS protection group for the STM-1/OC-3
optical interfaces of the OME6110.
Note: 1+1 MSP/APS protection group members must be of the same slot.
The user also provisions the Protection switching mode as either 2WAY
(bidirectional where both transmit and receive directions switch together) or
1WAY (unidirectional where only the transmit or receive direction switches
based on the fault or user initiated action). The Admin reversion mode must
also be set to either revertive or non-revertive mode. When revertive mode is
selected, the user must also specify the WTR Time period for the MSP/APS
group.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-21
Route diversity must also be set to enable or disable. When route diversity is
disabled, the DCC can only be provisioned on the working STM-1/OC-3
interface of the protection group. The transmit direction will be bridged and
the receive direction will be selected based on the active protection group
member. When route diversity is enabled, the DCC can be provisioned on both
the working and protection interfaces and each DCC is treated independently.
Note: 1+1 MSP/APS configuration of the STM-1/OC-3 ports on the
2x155M tributary card supports route diversity enable only.
For detailed procedures for 1+1 MSP/APS protection, refer to Provisioning
and Protection Switching Procedures, 323-1853-310.
1+1 MSP/APS protection switch criteria
1+1 MSP/APS protection switch request can occur automatically by the
system or by user initiated actions.
Note: User-initiated 1+1 MSP/APS switching commands are signaled via
MSP/APS channels (K1 and K2 bytes).
Table 6-9 summarizes the hierarchy of protection commands.
Table 6-9
1+1 MSP/APS protection - command hierarchy
Switch request
Priority
Lockout of protection
1 (highest)
Auto switch (Signal Fail) on protection
2
Forced switch
3
Auto switch (Signal Fail) on working
4
Auto switch (Signal Degrade) (Working or protection)
5
Manual switch to protection
6
Manual switch to working
7
Wait-to-Restore
8 (lowest)
For a complete procedures, see Provisioning and Protection Switching
Procedures, 323-1853-310.
SNCP/UPSR Traffic Protection
SNCP/UPSR traffic protection is defined as a 1 + 1 dedicated path protection
scheme where the transmit end is permanently bridged to both the working and
protection of the uni-directional path switched (UPS) or subnetwork
connections (SNC). At the receive end of the UPS connections or SNC, a
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-22 OAM&P description
protection switch is effected by selecting one of the signals based on the path
status. No 1+1 MSP/APS protocol is required as SNCP/UPSR is defined as a
unidirectional protection scheme.
Provisioning SNCP/UPSR connections
The user performs SNCP/UPSR connection provisioning from the
Cross-connect application in the Configuration main menu of the local craft
access terminal. The user selects the source and destination port interfaces for
the SNCP/UPSR connection and specifies the appropriate protection
requirements for each end-point of the end-to-end connection.
When protection is provisioned for the source or destination end-points of the
SNCP/UPSR connection, the user must also provision the revertive mode and
the WTR Time period when applicable.
Note: The OME6110 supports nodal provisioning. When provisioning an
end-to-end circuit, you must ensure that the traffic protection as well as
cross-connections are performed at the end-points as well as any
passthrough nodes that make up the end-to-end circuit.
For detailed procedures for SNCP/UPSR protection, refer to Provisioning and
Protection Switching Procedures, 323-1853-310.
SNCP/UPSR protection switch criteria
A SNCP/UPSR protection switch request can occur automatically by the
system or by user initiated actions.
Table 6-10 summarizes the hierarchy of protection commands.
Table 6-10:
SNCP/UPSR protection - command hierarchy
Switch request
Priority
Lockout of protection
1 (Highest)
Forced switch
2
Auto switch (P-AIS, P-LOP, P-UNEQ)
3
Auto switch (P-SF)
4
Auto switch (P-SD)
5
Manual switch on protection path
6
Manual switch on working path
7
Wait-to-Restore
8 (lowest)
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-23
For a complete description and procedures, see Provisioning and Protection
Switching Procedures, 323-1853-310.
Unprotected connections
Unprotected configurations consists of end-to-end paths that do not have an
alternate path. In the case of the a fault on the unprotected path, traffic is lost.
Note: Unprotected is the default traffic protection configuration for the
port interfaces in OME6110.
Provisioning unprotected connections
As unprotected is the default traffic protection configuration, unless the user
has already provisioned the STM-1/OC-3 optical interface circuit pack for 1+1
MSP/APS protection scheme, the user can simply provision cross-connects.
The user performs cross-connect provisioning from the Cross-connect
application in the Configuration main menu of local craft access terminal for
E1/DS1 and E3/DS3 services, while VC/VT/STS associations are provisioned
from the WAN application in the Facilities menu.
Note: The OME6110 supports nodal provisioning. When provisioning an
end-to-end circuit, you must provision the cross connections at the end
points and at any pass-through nodes that make up the end-to-end circuit.
For complete procedures for provisioning unprotected connections, see
Provisioning and Protection Switching Procedures, 323-1853-310.
Data communications
The OME6110 supports data communication features to provide the
capabilities for local and remote management of the OME6110 network
element and for interworking with other network elements to provide a
cohesive network management solution. The OME6110 OAM interfaces
provided are as follows:
• STM-1/OC-3 interfaces using RS/Section DCC (D1-D3 bytes),
RS/Section F1 byte, MS/Line DCC (D4-D12 bytes), or HO/STS Path (F2,
F3 and F2-F3 bytes) for OAM&P access to remote network elements
• LCT port for interface to a data communications network (DCN)
• M1/F1 port for modem access or for user byte access
• Management channel via physical E1 port
• Management channel via VC12 payload
Interfaces
The interfaces/protocols are configured from various applications available
from the local craft access terminal. For DCN provisioning procedures, see
Provisioning and Protection Switching Procedures, 323-1853-310.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-24 OAM&P description
LCT interface
The LCT interface provides a mechanism to connect the OME6110 network
element to the office DCN for connectivity to a management system for remote
management of the OME6110 network and subtending network elements.The
LCT interface consists of a 10/100Base-T RJ-45 LCT port located on the front
of the OME6110 base chassis.
The LCT port can be enabled or disabled with the default being enabled. It is
recommended to leave the LCT port in Admin Up state. If the LCT port must
be set to Admin down state, then an alternate communications channel should
be first established to the network element.
The LCT interface can be configured from the Network interface application
available from the Configuration/DCN menu item in the local craft access
terminal. For detailed procedures, see Provisioning and Protection Switching
Procedures, 323-1853-310. To know how to provision the IP address for the
LCT port, refer to Installation, Commissioning and Testing Procedures,
323-1853-201.
M1/F1 interface
The M1/F1 interface provides a mechanism to connect a PC or a modem to the
OME6110 network element for user byte clear channel access or remote
management. The serial port is exposed as a RJ-45 connector located on the
front of the OME6110 base chassis.
The M1/F1 interface can be provisioned for two applications:
• point-to-point protocol (PPP) - modem connectivity to the network
element through the serial port based on IP over PPP
• user data channel (UDC) - F1 byte user data channel limited to
asynchronous mode at 9600 kbps
The serial port can be configured from the Serial Port application available
from the Configuration/DCN menu item in the local craft access terminal. For
more details, refer to Provisioning and Protection Switching Procedures,
323-1853-310.
E1/VC12 management channel
The OME6110 supports up to two management channels that can be
provisioned over an E1 or VC12 channel. The management channel provides
a means to connect to isolated clusters over an E1 or VC12 channel.
An E1 management channel allows management data to be transmitted and
received over one of the physical E1 ports from the 16xE1/DS1 service
interface or 28xE1/DS1 circuit pack to manage remote network element. Since
Release 2.1, the E1 management channel can also be established with a remote
router.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-25
A VC12 management channel allows for management data to be transmitted
and received over one VC12 channel on the STM-1 optical ports to manage a
remote network element. The VC12 management channel can also be
established with an external router.
Note 1: In this release, the management channel is supported only over E1
or VC12 channels in SDH mode.
Note 2: E1/VC12 management is not supported when port 2 of the
optional 2x155M tributary circuit pack is in use.
The E1/VC12 management channel can be configured from the Network
Interface application available from the Configuration/DCN menu item in
the local craft access terminal. For more details, refer to Provisioning and
Protection Switching Procedures, 323-1853-310.
DCC interface
The DCC interfaces provide a mechanism for OME6110 network elements
and subtending network elements to communicate and exchange OAM
messages using the RS/Section, MS/Line or HO/STS Path overhead bytes. The
embedded communication channel (ECC) for the STM-1/OC-3 optical
interfaces can be configured to use any of the following byte groups:
• D1-D3 bytes of the Regenerator Section/Section overhead
• F1 byte of the Regenerator Section/Section overhead
• D4-D12 bytes of the Multiplex Section/Line overhead
• F2, F3 or F2-F3 bytes of the HO/STS path overhead
The OME6110 supports both IP and OSI based DCC interfaces and can
operate as a single point of entry for access to remote or subtending network
elements. The OAM for the OME6110 uses IP DCC and supports full routing
of DCC for other nodes which need to route through the OME6110. Each DCC
interface can be provisioned to support IP or OSI. The network element
supports dynamic and static GRE tunneling of IP/OSI on the STM-1/OC-3
interfaces.
The OME6110 is capable of supporting two standard DCN channels. The two
channels can be any one of the following:
• DCC channel from the STM-1/OC-3 ports on the base chassis. The DCC
bytes supported are RS/Section DCC, MS/Line DCC, F1, F2, F3 and F2F3.
• E1 based DCN channel originating from the 16xE1DS1 card.
• E1 based DCN channel originating from 28xE1DS1 card.
• VC12 based DCN channel originating from STM-1/OC-3 ports on the base
2x155M card.
• VC12 based DCN channel originating from the STM-1/OC-3 ports on the
tributary 2x155M card
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-26 OAM&P description
Note: Only two standard DCN channels are supported and hence only two
from the above choices can be created at a given time.
Each base chassis STM-1/OC-3 optical port is capable of supporting one DCC
channel with the following capabilities:
• A network interface that can be configured as MS/Line DCC, RS/Section
DCC, Path DCC or disabled. By default, there are no network interfaces
provisioned for the STM-1/OC-3 ports. The MS/Line and RS/Section
cannot coexist on the same port.
• Each DCC interface is capable of supporting either PPP (IP-based DCC
datalink layer) or LAPD (OSI-based DCC datalink layer). The default
value is PPP.
• Route diversity disabled (DCC follows traffic) or enabled (DCC active on
both working and protection paths) is supported on 1+1 MSP/APS
configurations. By default, route diversity is set to disabled.
• An alarm is raised when the DCC comms is lost on any port that is
configured and operational.
In addition to the standard DCN channels, an NE equipped with a 2x155M
tributary card can support two additional limited capacity DCN channels.
Each 2x155M tributary card STM-1/OC-3 optical port is capable of supporting
one DCC channel with the following capabilities:
• A network interface that can be configured as MS/Line DCC, RS/Section
DCC, Path DCC or disabled. By default, there are no network interfaces
provisioned for the STM-1/OC-3 ports. The MS/Line and RS/Section
cannot coexist on the same port.
• Each DCC interface supports PPP layer 2 protocol, IP layer 3 protocol,
OSPF routing and MTU of 240
• Route diversity enabled (DCC active on both working and protection
paths) for 1+1 MSP/APS configurations.
• An alarm is raised when the DCC comms is lost on any port that is
configured and operational.
Note: Up to six nodes can be managed through each limited capacity DCN
channel.
The DCC interface ports can be configured from the Network Interface
application available from the Configuration/DCN menu item in the local
craft access terminal. For more details on how to provision the DCC interfaces,
refer to Provisioning and Protection Switching Procedures, 323-1853-310. For
more information on DCN planning, refer to Appendix A: Data
communications planning on page 10-1.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-27
DCC Transparency
The OME6110 supports DCC transparency via overhead tunnel provisioning.
This feature allows the two STM-1/OC-3 optical ports to be connected
together so the network element appears transparent to subtending network
elements (NEs connected to the OME6110 via the STM-1/OC-3 interfaces).
The overhead tunnel allows DCC bytes to be forwarded transparently between
the two STM-1 optical ports. This feature offers advantages such as, allowing
interoperability with other vendor’s equipment that do not support a
standard-based OSI stack.
The user can select the bytes on which the overhead tunnel should be passing
through. The available values are:
• E1
• E2
• F1
• DCC_R
• DCC_M
The DCC transparency can be configured from the Overhead Tunnel
application available from the Configuration main menu item in the local
craft access terminal. For more details on how to provision the DCC interfaces,
refer to Provisioning and Protection Switching Procedures, 323-1853-310.
OAM comms management
The OME6110 uses an IP-based comms infrastructure for network element
management and interworking with IP-based DCC network elements.
However, OME6110 also supports OSI-based DCC for interworking with
OSI-based network elements.
For more information about provisioning the communication parameters, see
Provisioning and Protection Switching Procedures, 323-1853-310.
OAM comms routing
Support of IP-based and OSI-based DCC requires support of several routing
protocols. OME6110 supports the following routing protocols:
• Integrated ISIS (iISIS)
Integrated ISIS routing can be provisioned individually for each PPP or
LAPD network interface. iISIS routing facilitates the comms interworking
with various OSI-based products such as OM3000/OM4000, as well as for
IP-based products such as OME6500. The iISIS feature can be enabled or
disabled for each DCC network interface.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-28 OAM&P description
•
•
The iISIS nodal parameter setting and MAAs can be provisioned using the
iISIS application available from the Configuration/DCN menu item in the
local craft access terminal. The iISIS settings for the network interfaces
can be configured using the Network Interface application also available
from the Configuration/DCN menu. For more details on how to provision
iISIS, refer to Provisioning and Protection Switching Procedures,
323-1853-310. Refer to Appendix A: Data communications planning on
page 10-1 for more details on the iISIS routing protocol.
OSPF
The OSPF feature enables monitoring neighboring network elements and
retrieving routing information for In Band Communication (IBC). OSPF
routing can be enabled or disabled for the embedded channel interfaces or
for the LCT access to the public DCN.
The OSPF area can be provisioned using the OSPF application available
from the Configuration/DCN menu item in the local craft access terminal.
The OSPF settings for the embedded channel interface or the LCT port can
be configured using the Network interface application also available from
the Configuration/DCN menu.
For added security on OSPF networks, the user can provision the OSPF
authentication. The OSPF authentication setting and password can be
configured using the Network interface application also available from
the Configuration/DCN menu.
For more details on how to provision OSPF, refer to Provisioning and
Protection Switching Procedures, 323-1853-310. Refer to Appendix A:
Data communications planning on page 10-1 for more details on the OSPF
routing protocol.
Static routes
Static routing can be configured for the LCT port, as well as the network
interface ports.
Static route advertisement on OSPF and/or iISIS is available on OME6110.
When a static route is provisioned with the advertised parameter set to
enable, then the route will be automatically advertised to the routing
protocols configured on the network element. Refer to Table 6-11 for the
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-29
static route advertisement settings, based on routing protocol provisioning
on the NE. Static routes can be provisioned using the Static route
application available from the Configuration/DCN menu.
Table 6-11
Static route advertisement values
OSPF network
interface setting
iISIS nodal
parameter setting
Static Route
advertisement
Enable
Disable
OSPF
Disable
Enable
iISIS
Enable
Enable
OSPF and iISIS
•
Tunneling
Generic Routing Encapsulation (GRE) is the encapsulation mechanism for
transporting (tunneling) one protocol onto another protocol. OME6110
supports the following tunnels:
— IP over OSI tunneling
— static GRE tunneling, with a maximum of one tunnel for the network
element.
— dynamic GRE tunneling (auto-tunneling), allowing a “plug and play”
architecture
The GRE tunneling parameters can be provisioned using the Network
interface application available from the Configuration/DCN menu item
in the local craft access terminal.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-30 OAM&P description
•
Proxy ARP
Proxy ARP over the LCT port on the OME6110 allows the gateway
network element (GNE) to advertise routes on behalf of the other network
elements connected to it. Proxy ARP neighbour IP addresses are
provisioned at the gateway network element. The Proxy ARP neighbours
can be provisioned using the Proxy ARP Neighbour application from the
Configuration/DCN menu item in the local craft access terminal.
Alarm and event management
Active alarms are indicated on the OME6110 equipment and are visible from
the local craft access terminal. Alarm history and events are stored on the
OME6110 network element. Login sessions using craft user interface, and
Optical Network Manager (ONM) provide details of network element alarms.
The severity of an alarm is indicated by the following designations: Critical,
Major, minor, warning. Critical alarms have the highest priority and are
reported before Major, minor or warning alarms. Major alarms are reported
before minor alarms and minor alarms are reported before warnings.
OME6110 local alarm indications
Trouble conditions present on the OME6110 network element are indicated
locally by light-emitting diodes (LEDs) on the front of the base chassis, the
faceplate of a circuit pack, or the optical interfaces.
For more information about the local alarm indications, refer to Trouble
Clearing and Module Replacement Procedures, 323-1853-543.
Alarm management / surveillance
The local craft access terminal provides the user with the ability to view and
manage alarms and events for the OME6110 as follows:
• view summary of active alarms
• view active alarms
• view suppressed alarms
• view/provision alarm filters
• view event history
• view/provision alarm severities
• alarm reporting control
— view/provision STM/OC port profiles
— view/provision path alarm profiles
— enable/disable facility alarm reporting
• view/provision environmental alarms input
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-31
Viewing summary of active alarms
The WUI provides the user with an alarm banner which summarizes the active
alarms on the network element. The alarm banner is continuously displayed in
the WUI to provide the user with an accurate view of the current state of the
system while navigating through the different menus of the WUI. The alarm
banner has auto refresh enabled by default and is time-stamped, and it can be
disabled.
For more information about the alarm banner, refer to Local Craft Access User
Guide, 323-1853-195.
Viewing active alarms
The network element user interface provides the user with a list of active
alarms on the OME6110 shelf by selecting the Active alarms application in
the Faults menu of the local craft access terminal. The current active alarms
list is set to auto refresh by default, and it can be disabled.
For more information about the active alarm and alarm clearing procedures,
refer to Local Craft Access User Guide, 323-1853-195 and Trouble Clearing
and Module Replacement Procedures, 323-1853-543.
Viewing/provisioning alarm filters
The Alarm Filters application in the Faults menu of the local craft access
terminal provides the ability for users to create alarm filter rules whereby
selected alarms on chosen entities are not displayed in the active alarm list. The
application gives the user the ability to view, add or delete an alarm filter rule.
An alarm filter rule can be created for an alarm class against only one type,
where a selected alarm or all alarms are filtered out. When an alarm filter is
created, any active alarm which matches the filter rule are no longer displayed
in the active alarm list, and the filtered alarm is displayed in the suppressed
alarm list. An alarm filter can be deleted at any time.
For more information about the alarm filter and detailed procedures on
managing alarm filters, refer to Local Craft Access User Guide, 323-1853-195
and Trouble Clearing and Module Replacement Procedures, 323-1853-543.
Viewing suppressed alarms
The Suppressed alarms application in the Faults menu of the WUI allows the
user to view any alarms that have been suppressed by the Alarm Filter or by
the Alarm Reporting Control feature.
For more information about the suppressed alarms and alarm clearing
procedures, refer to Local Craft Access User Guide, 323-1853-195 and
Trouble Clearing and Module Replacement Procedures, 323-1853-543.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-32 OAM&P description
Viewing event history
The user views the events on an OME6110 shelf by selecting the Event
history application in the Faults menu of local craft access terminal. The
Events history application supports the viewing of historical (current and
cleared) alarms and events for the OME6110 network element.
The OME6110 network element stores up to 10000 events in non-volatile
storage.
For more information about the event history and alarm clearing procedures,
refer to Local Craft Access User Guide, 323-1853-195 and Trouble Clearing
and Module Replacement Procedures, 323-1853-543.
Viewing/provisioning alarm severities
The Alarm severity application in the Faults menu of the local craft access
terminal provides the ability for users to view or edit the severity of an alarm
for the OME6110 network element. The severity changes are applied to the
alarm type, but is not provisionable on an entity basis.
For more information about the alarm severities and detailed procedures on
managing alarm severities, refer to Local Craft Access User Guide,
323-1853-195 and Trouble Clearing and Module Replacement Procedures,
323-1853-543.
Alarm Reporting Control
The ARC feature provides a toolset to control the declaration of alarms from
the network element to the EMS/NMS applications. There are three
components of this feature:
• port profiles
• path alarm profiles
• facility alarm reporting
Viewing/editing port profiles
The STM/OC Port Profile application in the Profiles menu of the local craft
access terminal provides the ability for users to define the appropriate port
profiles for the STM/OC interfaces. The following are the two default port
profiles:
• internal-NNI - use within an EMS domain
• external-NNI - use between management domains
The port profile is a global setting and allows the user to assign the appropriate
path alarm profile to each of the eight individual connection types:
• terminating and unprotected TU/VT
• terminating and protected TU/VT
• passthrough and unprotected TU/VT
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-33
•
•
•
•
•
passthrough and protected TU/VT
terminating and unprotected AU/STS
terminating and protected AU/STS
passthrough and unprotected AU/STS
passthrough and protected AU/STS
The provisioned path alarm profile is automatically assigned to any
cross-connect that is created using the STM/OC interface.
For detailed procedures on managing port profiles, refer to Trouble Clearing
and Module Replacement Procedures, 323-1853-543.
Viewing/provisioning path alarm profiles
The Path Alarm Profiles application in the Profiles menu of the local craft
access terminal provides the ability for users to view the eight default path
alarm profiles, or create/edit/delete a user defined path alarm profile. The path
alarm profile is then assigned and applied to the eight connection types
according to the STM/OC Port Profile.
The path alarm profile specifies the consequent actions upon TIM, PLM and
UNEQ conditions. The path alarm profile also specifies the path level alarms
that should be masked. The eight default path alarm profiles can not be deleted
and their defined actions can not be modified, while the user can create or
delete the user defined path profiles and edit the defined actions.
Once a connection is created with the path alarm profile assigned according to
the STM/OC Port Profile, the path alarm profile can be manually changed at
the AU/STS/TU/VT levels.
For detailed procedures on managing path alarm profiles, refer to Trouble
Clearing and Module Replacement Procedures, 323-1853-543.
Enable/disable facility alarm reporting
User can enable or disable all alarm reporting associated to the following
facilities / alarm object instances:
• STM-n / OC-n
• AU / TU
• STS / VT
• PDHn / DSn
• WAN
• Ethernet
Once the alarm reporting is disabled for the facility / alarm object instance, any
active alarm will be suppressed and listed in the suppressed alarms application.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-34 OAM&P description
Viewing/provisioning environmental alarms
The OME6110 network element has 7 parallel telemetry input points. The
input points allow remote monitoring of other equipment in the office in which
the network element is located. For example, the input points can monitor
room temperature alarms or office door open alarms. Specific external alarm
must be set up during provisioning and are assigned to a specific contact pin.
The alarm input points are connected to the ALM.IN RJ-45 connector on the
front of the base chassis.
The Environmental alarm input application in the Configuration menu of
the local craft access terminal supports the provisioning of alarm for an alarm
input point.
The OME6110 also supports the capability of displaying the network element
summary alarms onto an external device. The Critical, Major, and Minor
alarms can be reported to an external control device by connecting to the
ALM.OUT RJ-45 connector on the front of the base chassis.
For more information on environmental alarms, refer to Local Craft Access
User Guide, 323-1853-195 and detailed procedures, refer to Trouble Clearing
and Module Replacement Procedures, 323-1853-543.
PDH / DSn alarm monitoring
Alarm monitoring support is limited for framed E1/DS1 ports. The level of
alarm monitoring depends on the PDH/DSn path monitoring mode assigned to
the unframed/framed PDH/DSn ports.
Below are the three provisionable modes of operations:
• no monitoring mode (NMM)
Alarm and performance monitoring is disabled for all ports and is the
default mode.
• alarm monitoring mode (AMM)
Path alarms are monitored in a round-robin basis. Under normal operating
condition, each port is polled at least 2-3 times in a 2.5 seconds interval.
• alarm and performance monitoring (APMM)
Only the nominated framed E1/DS1 port is monitored for path alarms and
performances.
The path alarm monitoring modes of operation are not applicable to framed
E3/DS3 ports. Each unframed/framed E3/DS3 port has full alarm and
performance monitoring support.
Table 6-12 on page 6-35 summarizes the PDH/DSn alarms for the different
chassis, service interface and circuit packs.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-35
For detailed procedures, refer to Provisioning and Protection Switching
Procedures, 323-1853-310.
Table 6-12
PDH / DSn alarm monitoring
Chassis
Card type
Line alarm
Path alarm (near-end) Path alarm (far-end)
OME6110 Rel 1.0
(Std. temp.)
16xE1DS1
(see Note1)
LOS
AIS
RAI
NT6Q50AA
28xE1DS1
(see Note2)
LOS
AIS, LOF, LOM
RAI
3xE3DS3
(see Note3)
LOS
AIS, LOF, LOM
RAI
OME6110 Rel 2.xx 16xE1DS1
(Std. & ext. temp.) (see Note2)
LOS
AIS, LOF, LOM
RAI
NT6Q50AB
NT6Q50AC
28xE1DS1
(see Note2)
LOS
AIS, LOF, LOM
RAI
NT6Q50ADE5
NT6Q50BA
NT6Q50BDE5
NT6Q51AA
NT6Q51AC
NT6Q51ADE5
3xE3DS3
(see Note3)
LOS
AIS, LOF, LOM
RAI
Note 1: Framed E1 alarm and performance monitoring is not available. All line and path alarms have
full monitoring support.
Note 2: The underlined path alarms have limited monitoring support and the non-underlined path
alarms have full monitoring support
Note 3: All line and path alarms have full monitoring support
Performance monitoring
Performance monitoring (PM) refers to the continuous collection, analysis,
and reporting of the performance data of a monitored entity. This monitoring
allows early detection of service degradations and facilitates preventive
maintenance without interruption of service. PMs can also be used to facilitate
trouble/fault isolation.
The OME6110 monitors the following entities for PM collection:
• STM/OCn performance monitoring parameters
• E1/E3/DS1/DS3 performance monitoring parameters
• Ethernet performance monitoring parameters
• WAN performance monitoring parameters
Note: Limited monitoring support for framed E1/DS1 path PM parameters
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-36 OAM&P description
The OME6110 craft user interface Performance application allows the user to
retrieve:
• current PM values (15 minute and 1-Day values in progress)
• recent history (32 previous 15 minute and previous day values stored on the
network element)
PDH / DSn performance monitoring
Path performance monitoring for E1/DS1 port is limited and dependant on the
PDH/DSn path monitoring mode assigned to the unframed/framed PDH/DSn
ports as described in the PDH / DSn alarm monitoring on page 6-34.
Path performance parameters are monitored when the path monitoring mode
for the selected framed port is set to Alarm and Performance Monitoring. Path
performance parameters are also counted for unframed E1/DS1 ports only
based on AIS condition.
Line performance monitoring is fully supported on all PDH/DSn ports. Path
performance monitoring is fully supported on all E3/DS3 ports.
PM functions
PM functions include:
• count binning
• thresholding
Count binning
Each monitored entity generates a set of PM parameter counts based on raw
data from hardware and other systems. These counts can be retrieved or reset
through user commands.
Thresholding
Performance thresholds are values associated with specific performance error
statistics. Aside from the physical PMs, each SDH performance parameter has
two thresholds which can be applied to either the current 15 minute or day
counts. When a PM parameter value exceeds its threshold settings, the system
generates a threshold crossing alert (TCA). TCAs are cleared when the PM
counts have been reset or the particular timed accumulation bin has terminated.
PM thresholds management for the STM-1/OC-3 optical interfaces is available
from the STM/OCn application in the Facility menu of the local craft access
terminal.
STM / OCn PM parameters
STM/OCn PM parameters are accumulated for the STM-1/OC-3 optical ports.
Table 6-13 provides a summary of the supported STM/OCn PM parameters.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-37
Table 6-13
SDH / SONET PM parameters summary
Facility
PM parameter
Regenerator
Section (RS) /
Section
SDH: ES, SES, UAS, SEP, EB, BBE, ESR, SESR, BBER, SEPI
SONET: CV, ES, SES, SEFS
Multiplex section
(MS)/Line
SDH: ES, SES, UAS, SEP, EB, BBE, ESR, SESR, BBER, SEPI, ES-FE,
SES-FE, UAS-FE, BBE-FE, SEP-FE
SONET: CV, ES, SES, UAS, FC, CV-FE, ES-FE, SES-FE, UAS-FE
Path (HO AU / STS) SDH: ES, SES, UAS, SEP, EB, BBE, PPJE, NPJE, ESR, SESR, BBER, SEPI,
ES-FE, SES-FE, UAS-FE, BBE-FE, SEP-FE
SONET: CV, ES, SES, UAS, FC, PPJE, NPJE, CV-FE, ES-FE, SES-FE,
UAS-FE
Tributary Unit (LO
TU / VT)
SDH: ES, SES, UAS, SEP, EB, BBE, ESR, SESR, BBER, SEPI, ES-FE,
SES-FE, UAS-FE, BBE-FE,SEP-FE
SONET: CV, ES, SES, UAS, FC, CV-FE, ES-FE, SES-FE, UAS-FE
Tranceiver
(physical)
Received Power, Transmit Power, Laser Bias, Laser Voltage, Laser
Temperature
PDH / DSn PM parameters
PM parameters are accumulated for the E1/E3/DS1/DS3 facilities on the:
• 16 x E1/DS1 service interface on the base chassis
• 28 x E1/DS1 circuit pack
• 3 x E3/DS3 circuit pack
Table 6-14 provides a summary of the supported PDH PM parameters.
Table 6-14
PDH / DSn PM parameters summary
Facility
PM parameter
Location
E1
Line: CV-L, ES-L, SES-L
Path: EB-P, BBE-P, ES-P, SES-P, UAS-P (see Note)
Near end
DS1
Line: CV-L, ES-L, SES-L
Path: CV-P, ES-P, SES-P, UAS-P, SAS-P, AISS-P (see Note)
Near end
E3
Line: CV-L, ES-L, SES-L
Path: ES-P, SES-P, UAS-P
Near end
DS3
Line: CV-L, ES-L, SES-L
Path: CV-P, ES-P, SES-P, UAS-P, SAS-P, AISS-P
Near end
Note: Limited path PM support for E1/DS1 facilities
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-38 OAM&P description
Ethernet PM parameters
Ethernet PM parameters are accumulated for the 10/100BT Ethernet interfaces
on the 8x10/100BT L1 circuit pack in the optional slot. Table 6-15 provides a
summary of the supported Ethernet PM parameters
.
Table 6-15
Ethernet PM parameters summary
Facility
PM parameter
Ethernet
• Alignment Errors
• Broadcast Frames Received
• Broadcast Frames Transmitted
• Collisions
• ES
• Ethernet Interval Valid
• Frame Too Long Errors
• Frame Too Short Errors
• Frames Aborted Due To Excessive Collisions
• FCS Errors
• Frames Received
• Frames Transmitted
• Frames With Deferred Transmissions
• Idle Seconds
• Late Collisions
• Multicast Frames Received
• Multicast Frames Transmitted
• Multiple Collision Frames
• Octets Received
• Octets Transmitted
• Pause Frames Received
• Pause Frames Transmitted
• SES
• Single Collision Frames
• UAS
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-39
WAN PM parameters
WAN PM parameters are accumulated for the Ethernet interfaces on the
8x10/100BT L1 circuit pack in the optional slot. Table 6-16 provides a
summary of the supported VCG PM parameters.
Table 6-16
WAN PM parameters summary
Facility
PM parameter
WAN
• Core Header CRC Errors
• Core Header Single Error Corrections
• ES
• Frames Dropped
• Idle Seconds
• Payload FCS Errors
• SES
• Type Header CRC Errors
• Type Header Single Error Corrections
• UAS
• Valid Bytes Received
• Valid Bytes Transmitted
• Valid Frames Received
• Valid Frames Transmitted
• WAN Interval Valid
PM time intervals
For PM parameters, the following PM counts are stored and can be retrieved:
•
•
•
•
current 15-minute interval
last 32 15-minute intervals
current day
previous day
PM enable/disable
The 15-minutes and 1-Day Threshold Cross Alerts for the
STM-1/OC-3/PDH/DSn facilities are disabled by default. The system does not
generate TCAs if the port/facility is in the admin down state.
PM inhibition
The system inhibits the collection of PMs when the associated facility is in the
the admin down state and for some parameters during various trouble
conditions.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-40 OAM&P description
For more details on performance layer parameters, refer to Trouble Clearing
and Module Replacement Procedures, 323-1853-543.
Security and administration
The OME6110 provides the following security and administration capabilities
managed from local craft access terminal:
• Network element security
— security levels
— login sessions
— local password management
— local user authentication
— centralized RADIUS authentication
• Network element administration
— network element naming
— date and time setting
For details of the procedures associated with security and administration, refer
to Provisioning and Protection Switching Procedures, 323-1853-310.
Local account user authentication
Local account user authentication uses a user ID and password and is the
default method on OME6110 network elements. A user ID and password is
managed individually at each network element.
Note 1: Local account user authentication is the default authentication
mode for network elements.
Note 2: This method of user authentication is not available for network
elements when RADIUS centralized authentication is enabled.
RADIUS Centralized authentication
OME6110 supports a Remote Access Dial-In User authentication Service
(RADIUS) as a centralized authentication solution. The RADIUS protocol is
an IETF Draft Standard (RFC 2865) widely used to support remote access
protocols (for example, PPP, telnet, and rlogin). The RADIUS protocol is a
UDP-based client-server protocol. OME6110 provides support for three
messages from this protocol:
• Access-Request - message sent from the network element to the
authentication server providing user information (user ID, password)
• Access-Reject - message sent from the authentication server to the network
element refusing access to the user
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-41
• Access-Accept - message sent from the authentication server to the
network processor allowing access to the user
The OME6110 operates as a RADIUS client, responsible for passing user
information to RADIUS servers, and then acting on the response. This remote
authentication feature is user provisionable, allowing system administrators to
enable or disable RADIUS. When RADIUS is enabled, the RADIUS server
processes all user authentications (local account user authentication is not
available). When RADIUS servers are not available or down, users can log in
with local account user authentication.
Attention: The OME6110 uses the following parameters which must be
configured on the RADIUS server:
— Vendor ID (Nortel): 562
— Vendor type (OME6110) 226
— Attribute values of 1 to 5 correspond to the UPC levels of OME6110
users
Network elements with RADIUS centralized authentication interoperate
seamlessly with network elements that do not support RADIUS centralized
authentication or have not enabled it.
The login/retry strategy is as follows:
• The RADIUS client on the network element sends up to three requests to
the primary server, followed by up to three requests to the secondary
server.
• The provisioned timeout value specifies the maximum amount of time
allowed to send and wait for responses for each server.
Users can provision on the OME6110:
• a primary RADIUS server’s IP address and port number
• a secondary RADIUS server’s IP address and port number
• the primary and secondary server shared secret
• timeout period for each RADIUS server
• state of the RADIUS feature (enabled/disabled)
Database save and restore operations include the centralized authentication
provisioning data on the OME6110. The centralized authentication
provisioning data on the OME6110 survives circuit pack restarts and
replacements.
Security levels
OME6110 network elements support multiple security access levels. This
feature reduces accidental or intrusive interruption of service. There are 4 user
access classes that allow a range of task execution capabilities.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-42 OAM&P description
Table 6-17
User access classes for OME6130
User Access
Classes
Privileges
USER
The USER has read-only access to all the management
information including configuration, faults and performance
OPERATOR
The OPERATOR can perform the following operations in
addition to the USER operations:
• configure interfaces and cross-connections
• reset performance statistics
• maintenance operations such as software/configuration
backup/restore, loopbacks
OPERATOR2
The OPERATOR2 can perform the following operations in
addition to the OPERATOR operations:
• provisioning of network element configuration parameters
like name, router ID, Ethernet IP / mask, contact, etc
ADMIN
The ADMIN can perform the following operations in
addition to the OPERATOR2 operations:
• create and delete UserIDs for the local authentication
mechanism on the network element
• configure the RADIUS parameters
The OME6110 has a default ADMIN level account named ADMIN with
ADMIN password. Nortel Networks recommends that the default passwords
be changed. See “Local password management” on page 6-43 for more
information.
There is no restriction on the number of user account per user access class, as
long as the total number of local user accounts does not exceed 100.
Login sessions
To manage an OME6110 network element and issue commands, the user must
be logged in on that node which creates a login session. The maximum number
of login sessions to a network element is ten.
Multiple login sessions
Several user accounts can be active at the same time as long as the maximum
number of ten login sessions is not exceeded. When several sessions are active,
commands can be sent to the network element simultaneously from each active
session.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-43
Local password management
The user performs local password management from the Security menu of the
local craft access terminal. The network element supports provisioning of up
to 100 user accounts.
Password restrictions
For the OME6110 network element, a valid password must be used in order to
activate a login session. The password is a confidential code to qualify the
authorized system user’s access to the account specified by the user name. The
password must be exactly 8 characters in length. The OME6110 uses a security
based on the Linux operating systems password encryption scheme.
Table 6-18
User ID and password details
User ID
• is unique
• can be alphabetic/numeric/alphanumeric
• supports special characters except space
• supports up to 32 characters
• is case sensitive
Password
• is unique
• must be exactly eight characters long
• can be alphabetic/numeric/alphanumeric
• supports special characters except space
• is case sensitive
• and the user ID cannot be identical
Network element name
The user can edit the network element name assigned during the
commissioning phase from the NE Information application in the System
main menu on the local craft access terminal.
Date and time setting
The user can edit the network element date and time settings provisioned
during the commissioning phase from the System Time application on the
local craft access terminal. This application provides the following time of day
synchronization features:
• Date and time setting
• Time zone setting
• Time server setting
Date and time setting
The network element date and time can be provisioned using the Set Time
application in the System Time menu.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-44 OAM&P description
Time zone setting
The time zone of the OME6110 network element can be provisioned to
correspond to the local settings using the Set time zone application in the
System Time menu.
Time server setting
The OME6110 network element can be provisioned to synchronize its time off
of NTP servers:
• up to 5 NTP servers can be provisioned (no servers set as default)
• synchronization frequency of the network element can be provisioned in
units of seconds (default is 1024 seconds)
• the synchronization to NTP server feature can be enabled or disabled by
user (default is disabled).
When NTP server synchronization is enabled, the network element time is
automatically adjusted after a restart of the network element or shelf power
failures. If no NTP server is available, the network element time is based on an
internal clock.
Note: When managing the OME6110 network element using OMEA, the
first NTP server will automatically be provisioned by the OMEA server.
For redundant OMEA servers, the first two NTP server will automatically
provisioned on the OME6110 NE. If additional time servers are desired,
these should be provisioned against other than the first two sources.
The user can provision TOD synchronization from the Set time server
application in the System Time menu of the local craft access terminal.
For a complete description of the security and network element administration
features and procedures, refer to Provisioning and Protection Switching
Procedures, 323-1853-310.
Topology adjacency
The topology adjacency feature on the OME6110 is used by the network
management to build the network topology for end-to-end connection
management. The network topology is built based on the neighbour status
information, which must be manually provisioned by the user.
For detailed procedures for provisioning the topology adjacency parameters,
refer to Provisioning and Protection Switching Procedures, 323-1853-310.
Backing up and restoring the network element database
The OME6110 network element is responsible for the resilience of its
provisioning data. A primary and backup copy of the configuration and
provisioning data is stored on the flash disk on the base chassis. This ensures
that in the event of a failure, the system can still recover on its own.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
OAM&P description 6-45
The user manages database backups from the Backup configuration and
Restore configuration applications in the Maintenance/Configuration
Management menu of the local craft access terminal. The applications allow
the user to manage backup copies of the network element database for each
network element within a network and restore the network element database to
an operational state following a system initialization.
Backup and restore operations can be performed remotely or locally from a
machine (server or PC). The remote operation uses FTP to move configuration
data between network elements and external backup repositories via a DCN.
A FTP server is required in order to perform remote backup and restore
operations onto the OME6110 network element. The OME6110 also supports
local restore operation using the inherent HTTP server to move configuration
files from an external backup repository (laptop or desktop), locally connected
to the LCT port, to the network element.
Refer to Installation, Commissioning and Testing Procedures, 323-1853-201,
for more information.
Installing and upgrading network element
Release 2.2 network element software, firmware and documentation (on-line
help) is factory installed on the base chassis and is also available on a CD in
the event the network element software needs to be re-installed on the base
chassis and circuit packs. Refer to Software load on page 8-18 for the
OME6110 Release 2.2 software load on CD product code.
Note: Software upgrades must be performed following a specific
procedure. Refer to the upgrade change application procedure (CAP),
NT6Q93AD, for details in performing the upgrade.
Software upgrade
A software upgrade is performed in a 5-step application from the Software
application in the Maintenance/Upgrade operations menu in the WUI:
• Deliver release
• Check upgrade
• Load upgrade
• Invoke upgrade
• Commit upgrade
Deliver release
The deliver release feature allows the user to transfer a software load to the
network element. The software load can be delivered to the network element
via the DCN from a remote machine running a FTP server or from a local
machine connected directly to the LCT port using HTTP.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
6-46 OAM&P description
The deliver release process consists of the following steps:
• Verifies that there is sufficient memory space on OME6110 shelf to store
the new software release.
• Transfers the software from the remote server to the OME6110 shelf file
system.
Check upgrade
The check upgrade is used to verify the downloaded software. The check
upgrade process consists of the following steps:
• Verifies the validity of the downloaded software through checksum.
• Verifies that downloaded software version is not the same as the current
running software version.
• Verifies that the downloaded software is a software for the OME6110
network element.
Load upgrade
During the load upgrade process, the network element proceeds to move the
software load into a persistent storage area.
Invoke upgrade
The invoke upgrade process initiates the execution of the downloaded software
load. In the event of un-successful execution of the invoke command, the NE
continues to execute using the existing software load. Once the invoke
command is successful, any restart or power-cycle of the NE will execute the
new software load. After a successful invoke operation, the NE can be reverted
back to the previous software load using the Cancel operation.
Commit upgrade
The commit upgrade process makes the downloaded software load the
currently active software release. Subsequent restarts of the network element
following a commit upgrade will not revert the system back to the previous
software release. Once the new software load is committed on the NE, the NE
can not be reverted back to the previous software load.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-1
Technical specifications
7-
This chapter provides technical specifications, as listed in Table 7-1, for the
Optical Multiservice Edge 6110 (OME6110) network element.
Table 7-1
Topics in this chapter
Topic
Page
Physical specifications
7-2
Power specifications
7-3
Connector pinouts
7-4
E1/DS1 cable pinouts and assemblies
7-17
Optical specifications
7-23
Electrical specifications
7-30
Environmental specifications
7-32
Electromagnetic specifications
7-34
Safety specifications
7-35
Power and grounding specifications
7-36
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-2 Technical specifications
Physical specifications
Table 7-2 lists the following physical specifications for OME6110 network
elements.
Table 7-2
Physical specifications for OME6110 platform
Equipment
Physical specification
Notes
Circuit packs
8 x 10/100BT L1 Ethernet 8 ports/circuit pack
(8 ports/shelf)
Refer to OME6110 network element
configuration rules on page 8-2.
3 x E3/DS3
3 ports/circuit pack
(3 ports/shelf)
28 x E1/DS1
28 ports/circuit pack
(maximum of 44 ports/shelf)
2 x 155M
2 ports/circuit pack
(2 tributary STM1/OC3
interfaces)
OME6110 Base chassis
Height
1U (44.0 mm / 1.7 in.)
Refer to:
Width
445.0 mm / 17.5 in.
• Figure 7-1 on page 7-2 for an overview
of the OME6110 base chassis
Depth
270.0 mm / 10.6 in.
• OME6110 network element
configuration rules on page 8-2 for
more information about physical
specifications
Figure 7-1
OME6110 base chassis - physical specifications
Power supply
unit
Optional
service
slot
Fan
module
PSU
16xE1/DS1 service
interface
2
ESD
E1/DS1 1-16
Alm. In
MI / F1
ESI
ic
rit
C
Rx
Tx
2
LCT
1
Tx 2 Rx
Port 2
OAM ports
Optical Multiservice Edge 6110
LCT port
- Ethernet
Network
Element
alarms
Tx 1 Rx
FAN
Alm. Out
M
Power
Optical Multiservice Edge 6110
-48Vdc 2A
M
RET GND -48V
ajo
r
in
or
al
1
Port 1
ESD jack
location
2xSTM-1/OC-3
interface ports
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-3
Power specifications
The OME6110 equipped with the DC PSU operates from -40 V DC to -57.5 V
DC measured at the input terminals of the network element. With the AC PSU,
the OME6110 operates from 90 Vac to 264 Vac from 47 to 63 Hz. The
following tables list the estimated power consumption for the different
modules:
• Table 7-3 lists the estimated power requirement for the common equipment
at -54 V dc
• Table 7-4 lists the estimated power requirement for each interface circuit
pack at -54 V dc
• Table 7-5 lists the estimated power requirement for each small form-factor
pluggable (SFP) optical module at -54 V dc
• Table 7-6 lists the recommended feeders for the base chassis
Table 7-3
Power consumption for components of the base chassis at -54 V dc
Base chassis components
Typical
(W)
Dual feed DC Power Supply Unit (normal and extended temp)
8
Single feed AC Power Supply Unit
12
Base chassis
18
Fan module
2
Service slot filler faceplate
0
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-4 Technical specifications
Table 7-4
Power consumption for each circuit pack at -54 V dc
Circuit pack
Typical
(W)
8x10/100BT L1
7.6
3xE3/DS3
8
28xE1/DS1
7.2
2x155M
8
Table 7-5
Power consumption for each SFP at -54 V dc
STM1/OC3 SFP modules
Typical
(W)
OC3/STM1 LR2/L1.2 XCT (normal and extended temp)
0.7
OC3/STM1 IR1/S1.1
0.7
OC3/STM1 SR0 (multimode) (extended temp)
0.7
OC3/STM1 LR1/L1.1
0.7
OC3/12/STM1 IR1/S1.1
0.7
OC-3/STM-1 CWDM (extended temp)
0.7
OC3/STM-1 Electrical
0.7
OC3/STM-1 (100Base) Bidirectional at 1310nm
0.7
OC3/STM-1 (100Base) Bidirectional at 1530nm
0.7
Table 7-6
Recommended feeders
Configuration
Feeders per shelf
OME6110 base chassis
(with DC PSU)
A feed (2 A) and redundant B feed (2 A)
Refer to Table 8-20 on page 8-17 for a list of power cables assemblies available
and the Installation, Commissioning and Testing Procedures, 323-1853-201
for details on installing and connecting power to an OME6110 shelf.
Connector pinouts
Table 7-7 lists the connectors and the respective tables providing the details of
their pin assignments and front views.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-5
Table 7-7
Connector pin assignment details
Connector
Details
DC power connector
Table 7-8
Base chassis connector pinouts
Alarm input connector
Table 7-9
Alarm output connector
Table 7-10
M1/F1 connector
Table 7-11
ESI connector
Table 7-12
LCT and 8x10/100BT port connector
Table 7-13
E1 connector (port 1 -16)
Table 7-14
DS1 connector (port 1 -16)
Table 7-15
28xE1/DS1 connector pinouts
E1 connector (port 1 -16)
Table 7-14
DS1 connector (port 1 -16)
Table 7-15
E1 connector (port 17-28) on 28xE1/DS1 circuit
pack
Table 7-16
E1 connector (port 17-28) on 28xE1/DS1 circuit
pack
Table 7-17
DC power connector
Table 7-8
DC power connector - pin assignment (in NT6Q59xA)
1
4
2
5
3
Pin
Connector
1
RET
2
GND
3
-48V
4
RET
5
GND
6
-48V
6
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-6 Technical specifications
Base chassis connector pinouts
Figure 7-1 on page 7-2 shows the interfaces available on the OME6110 base
chassis. Table 7-9 to Table 7-14 provide the details on the RJ-45 OAM ports
and the 16xE1/DS1 service interface.
Alarm input connector
Table 7-9
Alarm input connector - pin assignment (in NT6Q59AB)
1 2 3 4 5 6 7 8
Pin
Description
1
ALARMIN_1
2
ALARMIN_7
3
ALARMIN_6
4
ALARMIN_5
5
ALARMIN_4
6
ALARMIN_3
7
ALARMIN_2
8
GND
Alarm output connector
Table 7-10
Alarm output connector - pin assignment (in NT6Q59AB)
1 2 3 4 5 6 7 8
Optical Multiservice Edge 6110
Pin
Description
1
ALARMOUT_4_COM Unused
2
ALARMOUT_4
3
ALARMOUT_3_COM Minor
4
ALARMOUT_3
5
ALARMOUT_2_COM Major
6
ALARMOUT_2
7
ALARMOUT_1_COM Critical
8
ALARMOUT_1
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Usage
Technical specifications 7-7
M1/F1 connector
Table 7-11
M1/F1 connector - pin assignment (NT6Q71AG/AF)
1 2 3 4 5 6 7 8
Pin
Signal (M1) Signal (F1)
1
DSR
2
CD
3
DTR
4
GND
GND
5
RD
RD
6
TD
TD
7
CTS
8
RTS
ESI connector
Table 7-12
ESI connector - pin assignment (NT6Q71AC/AE)
1 2 3 4 5 6 7 8
Pin
Signal
1
CLKIN+ / DATAIN+
2
CLKIN- / DATAIN-
3
DATAIN+
4
CLKOUT- / DATAOUT-
5
CLKOUT+ / DATAOUT+
6
DATAIN-
7
DATAOUT+
8
DATAOUT-
Note 1: BITS-1-4-1 (IN) uses pins 1 & 2 and BITS-1-4-2 (IN) uses pins 3 & 6
Note 2: BITS-1-4-1 (OUT) uses pins 4 & 5 and BITS-1-4-2 (OUT) uses pins 7 & 8
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-8 Technical specifications
LCT and 8x10/100BT port connector
Table 7-13
LCT and 8x10/100BT port connector - pin assignment (NTUC58Px and
NTTC09C/Dx)
Pin
Signal
1
RX+
2
RX-
3
TX+
4
5
6
TX-
7
8
Note: The Ethernet cables connecting to the 8x10/100BT ports on the 8x10/100BT
circuit pack must be shielded twisted pair. Refer to Ethernet service cable
assemblies on page 8-13 for ordering information.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-9
E1 connector (port 1 -16)
Table 7-14
E1 connector - pin assignment (NT6Q72BA-EA / NT6Q73BA-EA)
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33
Pin Signal
Group Color
Pin Signal
1
TX1+
1
Orange 33
TX1-
1
Orange
P1
2
RX1+
1
Green
34
RX1-
1
Green
P2
3
TX2+
1
Blue
35
TX2-
1
Blue
P3
4
RX2+
1
Brown
36
RX2-
1
Brown
P4
5
TX3+
2
Orange 37
TX3-
2
Orange
P5
6
RX3+
2
Green
38
RX3-
2
Green
P6
7
TX4+
2
Blue
39
TX4-
2
Blue
P7
8
RX4+
2
Brown
40
RX4-
2
Brown
P8
9
TX5+
3
Orange 41
TX5-
3
Orange
P9
10
RX5+
3
Green
42
RX5-
3
Green
P10
11
TX6+
3
Blue
43
TX6-
3
Blue
P11
12
RX6+
3
Brown
44
RX6-
3
Brown
P12
13
TX7+
4
Orange 45
TX7-
4
Orange
P13
14
RX7+
4
Green
46
RX7-
4
Green
P14
15
TX8+
4
Blue
47
TX8-
4
Blue
P15
16
RX8+
4
Brown
48
RX8-
4
Brown
P16
17
TX9+
5
Orange 49
TX9-
5
Orange
P17
18
RX9+
5
Green
50
RX9-
5
Green
P18
19
TX10+
5
Blue
51
TX10-
5
Blue
P19
20
RX10+
5
Brown
52
RX10-
5
Brown
P20
21
TX11+
6
Orange 53
TX11-
6
Orange
P21
22
RX11+
6
Green
54
RX11-
6
Green
P22
23
TX12+
6
Blue
55
TX12-
6
Blue
P23
24
RX12+
6
Brown
56
RX12-
6
Brown
P24
25
TX13+
7
Orange 57
TX13-
7
Orange
P25
26
RX13+
7
Green
RX13-
7
Green
P26
58
Group Color
Pair
(White/)
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-10 Technical specifications
Table 7-14 (continued)
E1 connector - pin assignment (NT6Q72BA-EA / NT6Q73BA-EA)
27
TX14+
7
Blue
59
TX14-
7
Blue
P27
28
RX14+
7
Brown
60
RX14-
7
Brown
P28
29
TX15+
8
Orange 61
TX15-
8
Orange
P29
30
RX15+
8
Green
62
RX15-
8
Green
P30
31
TX16+
8
Blue
63
TX16-
8
Blue
P31
32
RX16+
8
Brown
64
RX16-
8
Brown
P32
Note: Right routing E1 cables connecting to the 28xE1/DS1 circuit pack must have a shielded
connector. Refer to Table 7-21 on page 7-21 for details on the shielded connector specifications.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-11
DS1 connector (port 1 -16)
Table 7-15
DS1 connector - pin assignment (NT6Q72QA/TA / NT6Q73QA/TA)
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33
Pin Signal
VTG Color
Pin Signal
VTG Color
Pair
1
TX1(tip)
1
White
(WH/BU)
33
TX1(ring)
1
Blue
(WH/BU)
P1
2
RX1(tip)
1
White
(WH/OR)
34
RX1(ring)
1
Orange
(WH/OR)
P2
3
TX2(tip)
1
White
(WH/GN)
35
TX2(ring)
1
Green
(WH/GN)
P3
4
RX2(tip)
1
White
(WH/BR)
36
RX2(ring)
1
Brown
(WH/BR)
P4
5
TX3(tip)
1
White
(WH/GR)
37
TX3(ring)
1
Gray
(WH/GR)
P5
6
RX3(tip)
1
Red
(RD/BU)
38
RX3(ring)
1
Blue
(RD/BU)
P6
7
TX4(tip)
1
Red
(RD/OR)
39
TX4(ring)
1
Orange
(RD/OR)
P7
8
RX4(tip)
1
Red
(RD/GN)
40
RX4(ring)
1
Green
(RD/GN)
P8
9
TX5(tip)
2
Red
(RD/BR)
41
TX5(ring)
2
Brown
(RD/BR)
P9
10
RX5(tip)
2
Red
(RD/GR)
42
RX5ring)
2
Gray
(RD/GR)
P10
11
TX6(tip)
2
Black
(BK/BU)
43
TX6(ring)
2
Blue
(BK/BU)
P11
12
RX6(tip)
2
Black
(BK/OR)
44
RX6(ring)
2
Orange
(BK/OR)
P12
13
TX7(tip)
2
Black
(BR/GN)
45
TX7(ring)
2
Green
(BK/GN)
P13
14
RX7(tip)
2
Black
(BK/BR)
46
RX7(ring)
2
Brown
(BK/BR)
P14
15
TX8(tip)
2
Black
(BK/GR)
47
TX8(ring)
2
Gray
(BK/GR)
P15
16
RX8(tip)
2
Yellow
(YL/BU)
48
RX8(ring)
2
Blue
(YL/BU)
P16
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-12 Technical specifications
Table 7-15 (continued)
DS1 connector - pin assignment (NT6Q72QA/TA / NT6Q73QA/TA)
17
TX9(tip)
3
Yellow
(YL/OR)
49
TX9(ring)
3
Orange
(YL/OR)
P17
18
RX9(tip)
3
Yellow
(YL/GN)
50
RX9(ring)
3
Green
(YL/GN)
P18
19
TX10(tip) 3
Yellow
(YL/BR)
51
TX10(ring) 3
Brown
(YL/BR)
P19
20
RX10(tip) 3
Yellow
(YL/GR)
52
RX10(ring) 3
Gray
(YL/GR)
P20
21
TX11(tip) 3
Purple
(PU/BU)
53
TX11(ring) 3
Blue
(PU/BU)
P21
22
RX11(tip) 3
Purple
(PU/OR)
54
RX11(ring) 3
Orange
(PU/OR)
P22
23
TX12(tip) 3
Purple
(PU/GN)
55
TX12(ring) 3
Green
(PU/GN)
P23
24
RX13(tip) 3
Purple
(PU/BR)
56
RX13(ring) 3
Brown
(PU/BR)
P24
25
TX13(T)
4
Purple
(PU/GR)
57
TX13(R)
4
Gray
(PU/GR)
P25
26
RX13(T)
4
Wh/Blue
58
RX13(R)
4
Blue
P26
(WH-BU/BU)
27
TX14(T)
4
Wh/Blue
(WH-BU/BU)
59
TX14(R)
4
(WH-BU/OR)
28
RX14(T)
4
Wh/Blue
TX15(T)
4
Wh/Blue
60
RX14(R)
4
RX15(T)
4
Wh/Blue
61
TX15(R)
4
TX16(T)
4
Wh/Or
62
RX15(R)
4
RX16(T)
4
Wh/OR
(WH-OR/OR)
Brown
Gray
63
TX16(R)
4
Blue
P30
P31
(WH-OR/BU)
64
RX16(R)
4
Orange
(WH-OR/OR)
Note: Right routing DS1 cables connecting to the 28xE1/DS1 circuit pack must have a shielded
connector. Refer to Table 7-21 on page 7-21 for details on the shielded connector specifications.
Optical Multiservice Edge 6110
P29
(WH-BU/GR)
(WH-OR/BU)
32
P28
(WH-BU/BR)
(WH-BU/GR)
31
Green
(WH-BU/GN)
(WH-BU/BR)
30
P27
(WH-BU/OR)
(WH-BU/GN)
29
Orange
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
P32
Technical specifications 7-13
28xE1/DS1 connector pinouts
Figure 7-2 on page 7-13 shows the faceplate of the 28xE1/DS1 circuit pack.
The first 64-pin Telco connector represents ports 1 to 16 of the circuit pack and
shares the same pinout as the 16xE1/DS1 service interface on the base chassis,
as shown in Table 7-14 for E1 services and Table 7-15 for DS1 services. The
second 64-pin Telco connector is used for ports 17 to 28 and the pinout
information is presented in Table 7-16 for E1 services and Table 7-17 for DS1
services.
Figure 7-2
28 x E1/DS1 circuit pack faceplate
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-14 Technical specifications
E1 connector (port 17-28) on 28xE1/DS1 circuit pack
Table 7-16
E1 connector (port 17-28) - pin assignment (NT6Q73BA-EA)
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33
Pin Signal
Group Color
1
TX17+
1
Orange 33
TX17-
1
Orange
P1
2
RX17+
1
Green
34
RX17-
1
Green
P2
3
TX18+
1
Blue
35
TX18-
1
Blue
P3
4
RX18+
1
Brown
36
RX18-
1
Brown
P4
5
TX19+
2
Orange 37
TX19-
2
Orange
P5
6
RX19+
2
Green
38
RX19-
2
Green
P6
7
TX20+
2
Blue
39
TX20-
2
Blue
P7
8
RX20+
2
Brown
40
RX20-
2
Brown
P8
9
TX21+
3
Orange 41
TX21-
3
Orange
P9
10
RX21+
3
Green
42
RX21-
3
Green
P10
11
TX22+
3
Blue
43
TX22-
3
Blue
P11
12
RX22+
3
Brown
44
RX22-
3
Brown
P12
13
TX23+
4
Orange 45
TX23-
4
Orange
P13
14
RX23+
4
Green
46
RX23-
4
Green
P14
15
TX24+
4
Blue
47
TX24-
4
Blue
P15
16
RX24+
4
Brown
48
RX24-
4
Brown
P16
17
TX25+
5
Orange 49
TX25-
5
Orange
P17
18
RX25+
5
Green
50
RX25-
5
Green
P18
19
TX26+
5
Blue
51
TX26-
5
Blue
P19
20
RX26+
5
Brown
52
RX26-
5
Brown
P20
21
TX27+
6
Orange 53
TX27-
6
Orange
P21
22
RX27+
6
Green
54
RX27-
6
Green
P22
23
TX28+
6
Blue
55
TX28-
6
Blue
P23
24
RX28+
6
Brown
56
RX28-
6
Brown
P24
25
NC
57
NC
P25
26
NC
58
NC
P26
Optical Multiservice Edge 6110
Pin Signal
Group Color
Pair
(White/)
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-15
Table 7-16 (continued)
E1 connector (port 17-28) - pin assignment (NT6Q73BA-EA)
27
NC
59
NC
P27
28
NC
60
NC
P28
29
NC
61
NC
P29
30
NC
62
NC
P30
31
NC
63
NC
P31
32
NC
64
NC
P32
Note: Right routing E1 cables connecting to the 28xE1/DS1 circuit pack must have a shielded
connector. Refer to Table 7-21 on page 7-21 for details on the shielded connector specifications.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-16 Technical specifications
DS1 connector (port 17-28) on 28xE1/DS1 circuit pack
Table 7-17
DS1 connector (port 17-28) - pin assignment (NT6Q73QA/TA)
Pin Signal
VTG Color
Pin Signal
VTG Color
Pair
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33
1
TX17(tip) 1
White
(WH/BU)
33
TX17(ring) 1
Blue
(WH/BU)
P1
2
RX17(tip) 1
White
(WH/OR)
34
RX17(ring) 1
Orange
(WH/OR)
P2
3
TX18(tip) 1
White
(WH/GN)
35
TX18(ring) 1
Green
(WH/GN)
P3
4
RX18(tip) 1
White
(WH/BR)
36
RX18(ring) 1
Brown
(WH/BR)
P4
5
TX19(tip) 1
White
(WH/GR)
37
TX19(ring) 1
Gray
(WH/GR)
P5
6
RX19(tip) 1
Red
(RD/BU)
38
RX19(ring) 1
Blue
(RD/BU)
P6
7
TX20(tip) 1
Red
(RD/OR)
39
TX20(ring) 1
Orange
(RD/OR)
P7
8
RX20(tip) 1
Red
(RD/GN)
40
RX20(ring) 1
Green
(RD/GN)
P8
9
TX21(tip) 2
Red
(RD/BR)
41
TX21(ring) 2
Brown
(RD/BR)
P9
10
RX21(tip) 2
Red
(RD/GR)
42
RX21(ring) 2
Gray
(RD/GR)
P10
11
TX22(tip) 2
Black
(BK/BU)
43
TX22(ring) 2
Blue
(BK/BU)
P11
12
RX22(tip) 2
Black
(BK/OR)
44
RX22(ring) 2
Orange
(BK/OR)
P12
13
TX23(tip) 2
Black
(BR/GN)
45
TX23(ring) 2
Green
(BK/GN)
P13
14
RX23(tip) 2
Black
(BK/BR)
46
RX23(ring) 2
Brown
(BK/BR)
P14
15
TX24(tip) 2
Black
(BK/GR)
47
TX24(ring) 2
Gray
(BK/GR)
P15
16
RX24(tip) 2
Yellow
(YL/BU)
48
RX24(ring) 2
Blue
(YL/BU)
P16
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-17
Table 7-17 (continued)
DS1 connector (port 17-28) - pin assignment (NT6Q73QA/TA)
17
TX25(tip) 3
Yellow
(YL/OR)
49
TX25(ring) 3
Orange
(YL/OR)
P17
18
RX25(tip) 3
Yellow
(YL/GN)
50
RX25(ring) 3
Green
(YL/GN)
P18
19
TX26(tip) 3
Yellow
(YL/BR)
51
TX26(ring) 3
Brown
(YL/BR)
P19
20
RX26(tip) 3
Yellow
(YL/GR)
52
RX26(ring) 3
Gray
(YL/GR)
P20
21
TX27(tip) 3
Purple
(PU/BU)
53
TX27(ring) 3
Blue
(PU/BU)
P21
22
RX27(tip) 3
Purple
(PU/OR)
54
RX27(ring) 3
Orange
(PU/OR)
P22
23
TX28(tip) 3
Purple
(PU/GN)
55
TX28(ring) 3
Green
(PU/GN)
P23
24
RX28(tip) 3
Purple
(PU/BR)
56
RX28(ring) 3
Brown
(PU/BR)
P24
25
NC
57
NC
P25
26
NC
58
NC
P26
27
NC
59
NC
P27
28
NC
60
NC
P28
29
NC
61
NC
P29
30
NC
62
NC
P30
31
NC
63
NC
P31
32
NC
64
NC
P32
Note: Right routing DS1 cables connecting to the 28xE1/DS1 circuit pack must have a shielded
connector. Refer to Table 7-21 on page 7-21 for details on the shielded connector specifications.
E1/DS1 cable pinouts and assemblies
Cable details
The 16xE1/DS1 service interface on the base chassis and the 28xE1/DS1
circuit pack both support 64-pin Telco connectors to offer the E1/DS1 services.
By default, the ports are 120/100 ohm balanced E1/DS1 electrical ports. A
termination panel can be used to convert the 120 ohm balanced E1 ports to 75
ohm unbalanced E1 ports.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-18 Technical specifications
The following sections detail the pinouts and port mappings for the 120/100
ohm cable assemblies and for the 75 ohm termination panel. The E1/DS1
cables come with left routing or right routing with equivalent specifications.
When connecting to the 16xE1/DS1 service interface on the base chassis, it is
recommended to use the left routing cables, while right routing cables should
be used on the 28xE1/DS1 circuit pack.
These cable assemblies can be ordered from Nortel (see E1/DS1 cable
assemblies on page 8-11) or produced locally to the specifications provided:
• Table 7-14 on page 7-9 provides the 120 ohm cable connector pin
assignment, which applies for E1 services on the 16xE1/DS1 service
interface and the first connector on the 28xE1/DS1 circuit pack.
• Table 7-15 on page 7-11 provides the 100 ohm cable connector pin
assignment, which applies for DS1 services on the 16xE1/DS1 service
interface and the first connector on the 28xE1/DS1 circuit pack.
•
•
•
•
•
•
•
•
•
•
Table 7-16 on page 7-14 provides the 120 ohm E1 cable connector pin
assignment for the second connector on the 28xE1/DS1 circuit pack.
Table 7-17 on page 7-16 provides the 100 ohm DS1 cable connector pin
assignment for the second connector on the 28xE1/DS1 circuit pack.
Figure 7-3 on page 7-19 shows the 75 ohm BNC termination panel for 16
channels. Using the termination panel, the 120 ohm balanced E1 services
can be converted to 75 ohm unbalanced.
Table 7-18 on page 7-19 lists the physical specifications for the 75 ohm
BNC termination panel
Table 7-19 on page 7-20 lists the cable specifications for connecting the E1
ports of the 16xE1/DS1 service interface or the 28xE1/DS1 circuit pack.
Table 7-20 on page 7-20 lists the cable specifications for connecting the
DS1 ports of the 16xE1/DS1 service interface or the 28xE1/DS1 circuit
pack.
Table 7-21 on page 7-21 lists the connector specifications for the shield
connector required for the right routing E1 and DS1 cables for use with the
28xE1/DS1 circuit pack.
Figure 7-4 on page 7-22 shows the 120 ohm twisted pair E1 cable bundle.
Figure 7-5 on page 7-23 shows the 64-pin 100 degree left routing cable
connector for the E1 and DS1 cables.
Figure 7-6 on page 7-23 shows the 64-pin 100 degree right routing cable
connector for the E1 and DS1 cables.
Note: The color codes and pinout provided apply to the suggested E1/DS1
cables. Color codes and pinout may vary by manufacturer.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-19
Figure 7-3
75 ohm termination panel - 16 channel
Note: The 75 ohm termination panel is labeled from 1-16 by default, but
includes an additional overlay label which can be installed by the user
when connecting the ports 17-28 of the 28xE1/DS1 circuit pack.
Table 7-18
Physical specifications for 75 ohm BNC termination panel
Feature
Physical specification
Data rate
2.048 Mbps
75 ohm connector
Dual coax female BNC
120 ohm connector
(for interconnection with
OME6110 shelf)
64-pin Telco
Power supply
none required
Link-to-data isolation
500 volts AC/DC
Temperature range
0-50oC
Height
1U (44.0 mm / 1.9 in.)
Width
483.0 mm / 19 in.
Depth
89.0 mm / 3.5 in.
Notes
See Table 7-14 on page 7-9 for pinout
information on 64-pin connector.
Table 7-19 lists the E1 cable specifications and Table 7-20 lists the DS1 cable
specifications for connecting E1 and DS1 ports respectively, on the
16xE1/DS1 service interface or the 28xE1/DS1 circuit pack.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-20 Technical specifications
Table 7-19
Cable specifications for connecting E1 ports
Feature
Physical specification
Conductor
26 AWG solid tin plated copper
Insulation
Solid polyolefin
Pairs
Two conductors twisted into pairs with varying lay length
Pair groups
Four twisted pairs are cabled together
Jacket
Four pair groups are jacketed with PVC and each group is numbered
Cable Groups
8 four pair groups are cabled together
Colour Code
• Pair 1: Orange-White/Orange
• Pair 2: Blue-White/Blue
• Pair 3: Green-White/Green
• Pair 4: Brown-White/Brown
Shield
Overall Aluminum/Mylar foil shield with aluminum side facing out. 26
AWG tinned copper drain wire over the foil with a 34 AWG tin plated
copper braid, 65% coverage.
Jacket
Gray PVC jacket. Overall dimension 15,6 mm Nom.
Electrical Characteristics
Impedance
120 +/- 10 Ohms Nom.
Capacitance
13.3 pF/ft Nominal
Velocity of propagation
65% Nominal
Near End Cross Talk
(NEXT) pair to pair
53 dB at 20 MHz
Dielectric Strength
Conductor to Conductor
2.5 KV DC
Core to Sheath
2.3 KV DC
Table 7-20
Cable specifications for connecting DS1 ports
Feature
Physical specification
Conductor
24 AWG solid tin plated copper
Insulation
Solid polyolefin or solid Polyethylene
Pairs
Two conductors twisted into pairs with varying lay length
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-21
Table 7-20 (continued)
Cable specifications for connecting DS1 ports
Feature
Physical specification
Pair groups
32 twisted pairs are cabled together
Jacket
32 pair groups are jacketed with PVC
Colour Code
Refer to Table 7-15 on page 7-11 for colour coding information
Shield
24 AWG tinned copper drain wire over the foil with a 34 AWG tin plated
copper braid, 65% coverage.
Jacket
Gray PVC jacket. Overall dimension 14.0 mm Nom.
Electrical Characteristics
Impedance
100 +/- 15 Ohms Nom.
Capacitance
13.3 pF/ft Nominal
Velocity of propagation
65% Nominal
Near End Cross Talk
(NEXT) pair to pair
53 dB at 20 MHz
Dielectric Strength
Conductor to Conductor
2.5 KV DC
Core to Sheath
2.3 KV DC
For applications with the 28xE1/DS1 circuit pack, right routing E1 or DS1
cables must be used. The cable connectors for the right routing cables must
comply to the specifications provided in Table 7-21. Refer to Figure 7-6 on
page 7-23 for more details.
Table 7-21
Connector specifications for right routing E1/DS1 cables
Feature
Physical specification
Connector
Connector type
64 POS Male AMP Champ (0.085) or equivalent ‘key telephone’
connector
Latching hardware
4-40 screws - 2 places
Component
Minimum 30uin Au over 50uin Ni plating on contacts
Hood
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-22 Technical specifications
Table 7-21 (continued)
Connector specifications for right routing E1/DS1 cables
Feature
Physical specification
Hood exit
• Angled exit recommended at 100 degrees.Close proximity of connector
positions on OME6110 faceplate prevents the user of many low profile
right angle exit hoods. (See Figure 7-6 on page 7-23)
Depth
60 mm maximum connector hood and cable depth from connector mating
face
Component
Metal plated plastic (100% coverage) or fully metal shielded connector
hood
Terminations
Shielded hood terminated to cable shield and to both hood mounting
screws via the cable drain wires (both mounting screws must attach to
the drain wire through Y’d arrangement, or two drain wires) and
interference contact to exposed braid at the exit of the cable from hood.
Figure 7-4
E1 coaxial cable bundle specification
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-23
Figure 7-5
64-pin E1/DS1 100 degree left routing cable connector
Note: The right routing cable connector presented in Figure 7-6 must be
used with the 28xE1/DS1 circuit pack.
Figure 7-6
64-pin E1/DS1 right routing cable connector specifications
Optical specifications
The following sections provide details of the optical specifications.
The following assumptions were made when calculating the dispersion and
attenuation limited distances quoted in the optical specifications:
• NSDF fiber plant is being used
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-24 Technical specifications
•
dispersion and attenuation coefficient are as listed in Table 7-22.
Table 7-22
Optical specifications - assumed dispersion and attenuation coefficient
Wavelength
1310 nm
1550 nm + C-band
Dispersion coefficient
(ps/nm/km)
6.0
17.0
Attenuation coefficient
(dB/km)
0.35
0.25
ATTENTION
The dispersion and attenuation limited distances quoted in the optical
specifications are based on the dispersion and attenuation coefficients
detailed in Table 7-22 and are for guidance only and must be verified by a full
link budget calculation. The actual limiting distance is the lower of the
dispersion limited or attenuation limited distances.
STM-1/OC-3 SFP optical specifications
Table 7-23 lists the optical specifications for the STM-1/OC-3 SFPs.
Table 7-23
Optical specifications for OC-3/STM-1 SFPs
Classification
SR0
IR1/S1.1
LR1/L1.1
LR2/L1.2
PEC
NTTP02AD
NTTP02CD
NTTP02ED
NTTP02FD/
NTTP02FF
Transmitter type
LED
FP laser
DFB laser
DFB laser
Nominal wavelength
1270 nm to
1380 nm
1310 nm
1310 nm
1550 nm
Transmit output power (max)
-14 dBm
-8 dBm
0 dBm
0 dBm
Transmit output power (min)
-20 dBm
-15 dBm
-5 dBm
-5 dBm
Spectral width
200 nm
(FWHM)
7.7 nm
(RMS)
1 nm
(-20 dB)
1 nm
(-20 dB)
Minimum side mode suppression
ratio
-
-
30 dB
30 dB
Minimum extinction ratio
10 dB
8.2 dB
10 dB
10 dB
Power monitor accuracy
(see Note 2)
+/- 2 dB
+/- 2 dB
+/- 2 dB
+/- 2 dB
Transmitter
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-25
Table 7-23 (continued)
Optical specifications for OC-3/STM-1 SFPs
Classification
SR0
IR1/S1.1
LR1/L1.1
LR2/L1.2
Receiver type
PIN
photodiode
APD
APD
APD
Wavelength range
1100 nm to
1600 nm
1261 nm to
1580 nm
1261 nm to
1580 nm
1260 nm to
1580 nm
Nominal wavelength
1310 nm
1310 nm
1310 nm
1550 nm
Receiver sensitivity
-30 dBm
-28 dBm
-34 dBm
-34 dBm
Receiver overload
-14 dBm
-8 dBm
-10 dBm
-10 dBm
Path penalty
-
1 dB
1 dB
1 dB
Maximum receive reflectance
-
-
-
-25 dB
Power monitor accuracy
(see Note 2)
+/- 2 dB
+/- 2 dB
+/- 2 dB
+/- 2 dB
Attenuation range
0 dB
to 10 dB
0 dB to 12 dB
10 dB to 28 dB 10 dB to
28 dB
Nominal reach (see Note 3)
2 km
15 km
40 km
80 km
Maximum dispersion
-
96 ps/nm
-
-
Minimum optical return loss
-
-
-
20 dB
Dispersion limited distance (see
Note 4)
-
16 km
-
-
Attenuation limited distance (see
Note 4)
2 km
34.3 km
80 km
112 km
Receiver
Optical path
Note 1: All parameter values in the above table achieve an optical system BER better than 1x10-10
when used over G.652 specified SMF-28 fiber. The exception is SR0 where the values are for use over
62.5 µm core, 500 MHz-km modal bandwidth MMF as specified in ANSI T1.416.01-1999.
Note 2: Power monitor accuracy figures are for normal operating range (minimum to maximum transmit
power, receiver sensitivity to overload).
Note 3: Nominal reach figures are for classification purposes only as defined in the appropriate
standards.
Note 4: The dispersion and attenuation limited distances are based on the dispersion and attenuation
coefficients detailed in Table 7-22 on page 7-24 and are for guidance only and must be verified by a full
link budget calculation. The actual limiting distance is the lower of the dispersion limited or attenuation
limited distances.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-26 Technical specifications
Table 7-24 lists the optical specifications for the STM-1/4/OC-3/12 SFPs.
Table 7-24
Optical specifications for STM-1/4/OC-3/12 SFPs
Classification
IR1/S1.1_S4.1
PEC
NTTP04CF
Transmitter
Transmitter type
FP laser
Nominal wavelength
1310 nm
Transmit output power (max)
-8 dBm
Transmit output power (min)
-15 dBm
Spectral width
2.5 nm (RMS)
Minimum extinction ratio
8.2 dB
Power monitor accuracy (see Note 2)
+/- 2 dB
Receiver
Receiver type
APD
Wavelength range
1274 nm to 1580 nm
Nominal wavelength
1310 nm
Receiver sensitivity
-28 dBm
Receiver overload
-8 dBm
Path penalty
1 dB
Power monitor accuracy (see Note 2)
+/- 2 dB
Optical path
Attenuation range
0 dB to 12 dB
Nominal reach (see Note 3)
15 km
Maximum dispersion
74 ps/nm
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-27
Table 7-24 (continued)
Optical specifications for STM-1/4/OC-3/12 SFPs
Classification
IR1/S1.1_S4.1
Dispersion limited distance (see Note 4)
12.3 km
Attenuation limited distance (see Note 4)
34.3 km
Note 1: All parameter values in the above table achieve an optical system BER
better than 1x10-10 when used over G.652 specified SMF-28 fiber.
Note 2: Power monitor accuracy figures are for normal operating range (minimum
to maximum transmit power, receiver sensitivity to overload).
Note 3: Nominal reach figures are for classification purposes only as defined in the
appropriate standards.
Note 4: The dispersion and attenuation limited distances are based on the
dispersion and attenuation coefficients detailed in Table 7-22 on page 7-24 and are
for guidance only and must be verified by a full link budget calculation. The actual
limiting distance is the lower of the dispersion limited or attenuation limited
distances.
Table 7-25 lists the optical specifications for the STM-1/4/16/OC-3/12/48
CWDM SFPs.
Table 7-25
Optical specifications for STM-1/4/16/OC-3/12/48 SFPs
Classification
2.5G NRZ CWDM
(S-C8L1-1Dx)
PEC
NTK590xH
(see Note 6)
Transmitter
Transmitter type
DFB laser
Nominal wavelength
1471 nm to 1611 nm
@ 20 nm +/-6.5 nm
Transmit output power (max)
+5 dBm
Transmit output power (min)
0 dBm
Spectral width
1 nm
(-20 dB)
Minimum side mode suppression ratio
30 dB
Minimum extinction ratio
8.2 dB
Power monitor accuracy
(see Note 2)
+/- 2 dB
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-28 Technical specifications
Table 7-25 (continued)
Optical specifications for STM-1/4/16/OC-3/12/48 SFPs
Classification
2.5G NRZ CWDM
(S-C8L1-1Dx)
Receiver
Receiver type
APD
Wavelength range
1260 nm to 1620 nm
Nominal wavelength
1471 nm to 1611 nm
@ 20 nm
Receiver sensitivity
-28 dBm
Receiver overload
-9 dBm
Path penalty
2.5 dB
Maximum receive reflectance
-27 dB
Power monitor accuracy
(see Note 2)
+/- 2 dB
Optical path
Attenuation range
14 dB to
25.5 dB
Nominal reach (see Note 3)
See Note 4
Maximum dispersion
1600 ps/nm
Minimum optical return loss
24 dB
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-29
Table 7-25 (continued)
Optical specifications for STM-1/4/16/OC-3/12/48 SFPs
Classification
2.5G NRZ CWDM
(S-C8L1-1Dx)
Dispersion limited distance (see Note 5)
See Note 4
Attenuation limited distance (see Note 5)
See Note 4
Note 1: All parameter values in the table achieve an optical system BER better than
1x10-10 when used over G.652 specified SMF-28 fiber except for the CWDM value
which is for an optical system BER better than 1x10-12.
Note 2: Power monitor accuracy figures are for normal operating range (minimum
to maximum transmit power, receiver sensitivity to overload).
Note 3: Nominal reach figures are for classification purposes only as defined in the
appropriate standards.
Note 4: CWDM reach is consistent with Appendix II of ITU-T G.695 (refer to G.695
Table II.2 for parameter values and G.695 Table II.1 for attenuation values).
Dispersion limits are based on 21.1 ps/nm-km.
Note 5: The dispersion and attenuation limited distances are based on the
dispersion and attenuation coefficients detailed in Table 7-22 on page 7-24 and are
for guidance only and must be verified by a full link budget calculation. The actual
limiting distance is the lower of the dispersion limited or attenuation limited
distances.
Note 6: Refer to Ordering information and system engineering rules on page 8-1 for
a list of supported wavelengths and PECs.
Table 7-26 lists the optical specifications for the STM-1/OC-3 (100Base)
Bidirectional SFPs.
Table 7-26
Optical specifications for STM-1/OC-3 (100Base) Bidirectional SFPs
Classification
100Base
BX10-U
(see Note 3)
100Base
BX10-D
(see Note 3)
PEC
NTTP09BD
NTTP10BD
Transmitter type
FP laser
FP laser
Nominal wavelength
1310 nm
1530 nm
Transmit output power (max)
-8 dBm
-8 dBm
Transmit output power (min)
-14 dBm
-14 dBm
Spectral width
7.7 nm (RMS)
4.4 nm (RMS)
Minimum extinction ratio
6.6 dB
6.6 dB
Transmitter
Receiver
Receiver type
PIN photodiode PIN photodiode
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-30 Technical specifications
Table 7-26 (continued)
Optical specifications for STM-1/OC-3 (100Base) Bidirectional SFPs
Classification
100Base
BX10-U
(see Note 3)
100Base
BX10-D
(see Note 3)
Wavelength range
1480 nm to
1580 nm
1260 nm to
1360 nm
Nominal wavelength
1530 nm
1310 nm
Receiver sensitivity
-28.2 dBm
-28.2 dBm
Receiver overload
- 8 dBm
- 8 dBm
Path penalty
4.5 dB
4.5 dB
Maximum receive reflectance
-12 dB
-12 dB
10 km
(see Note 2)
10 km
(see Note 2)
Optical path
Reach
Note 1: All parameter values in the above table achieve an optical system BER better than 1x10-12.
Note 2: 0.5 m to 10 km over G.652 SMF.
Note 3: Used for a bidirectional link over a single fiber with an upstream SFP fitted at one end of the
link and an downstream SFP fitted at the other end of the link. The upstream SFP transmits at 1310 nm
and receives at 1530 nm, the downstream SFP transmits at 1530 nm and receives at 1310 nm.
Electrical specifications
Table 7-27 to Table 7-31 lists the electrical specifications for the E1, E3, DS3,
DS1, and STM-1e interfaces.
Table 7-27
E1 electrical specifications
Parameter
Value
Line rate
2048 kbit/s +/- 50 ppm
Line code
HDB3
Framing application
CRC4
Impedance
75 ohm or 120 ohm (see Note)
Output voltage (nominal)
75 ohm: 2.37 V (mark), 0 ± 0.237 V (space)
120 ohm: 3.00 V (mark), 0 ± 0.300 V (space)
Minimum output return loss 6 dB (51 kHz to 102 kHz), 8 dB (102 kHz to 3072 kHz)
Cable loss to input
0 dB to 6 dB at 1024 kHz
Minimum input return loss
12 dB (51 kHz to 102 kHz), 18 dB (102 kHz to
2048 kHz), 14 dB (2048 kHz to 3072 kHz)
Note: A termination panel must be used for 75 ohm E1 applications.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-31
Table 7-28
E3 electrical specifications
Parameter
Value
Line rate
34368 kbit/s +/- 20 ppm
Line code
HDB3
Framing application
G.832
Impedance
75 ohm
Output voltage (nominal)
75 ohm: 1.0 V (mark), 0 ± 0.1 V (space)
Cable loss to input
0 dB to 12 dB at 17184 kHz
Minimum input return loss
12 dB (860 kHz to 1720 kHz), 18 dB (1720 kHz to
34368 kHz), 14 dB (34368 kHz to 51550 kHz)
Table 7-29
DS1 electrical specifications
Parameter
Value
Line rate
1544 kbit/s +/- 50 ppm
Line code
B8ZS
Framing application
Extended Super Frame (ESF)
Impedance
100 ohm ± 5%
Pulse amplitude
2.4 V to 3.6 V
Power level
In a band not wider than 3 kHz, the power level is less
than 19 dBm.
Cable distances
Maximum 200 m (655 ft)
Line build-out (LBO)
ranges
Using NT6Q72QA/TA or NT6Q73QA/TA cables:
0 to 133 ft (40.5 m), 133 ft (40.5 m) to 266 ft (81.1 m),
266 ft (81.1 m) to 399ft (121.6 m), 399 ft (121.6 m) to
533 ft (162.5 m), 533 ft (162.5 m) to 655 ft (200 m)
Table 7-30
DS3 electrical specifications
Parameter
Value
Line rate
44736 kbit/s +/- 20 ppm
Line code
B3ZS
Framing application
ASYNC
Impedance
75 ohm ± 5%, unbalanced
Pulse amplitude
0.36 V to 0.85 V peak
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-32 Technical specifications
Table 7-30 (continued)
DS3 electrical specifications
Parameter
Value
Power level
-4.7 dBm to +3.6 dBm
Cable distances
Maximum 450 ft (137.1 m)
Line build-out (LBO)
ranges
Using 735A cables (recommended) (NTTC03xx):
0 to 255 ft (77.7 m), 255 ft (77.7 m) to 450 ft (137.1 m)
Table 7-31
STM-1e electrical specifications
Parameter
Value
Line rate
155520 kbit/s +/- 20 ppm
Line code
CMI
Impedance
75 ohm
Peak output voltage
1.00 V ± 0.1 V
Minimum output return loss 15 dB (8 MHz to 240 MHz)
Cable loss to input
0 dB to 12.7 dB at 78 MHz
Minimum input return loss
15 dB (8 MHz to 240 MHz)
Environmental specifications
The following section outlines the environmental specifications including:
• operating environment specifications
• storage and transportation specifications
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-33
Operating environment specifications
Table 7-32 outlines the OME6110 operating environment specifications.
Table 7-32
Operating environmental specifications for OME6110 system
Attribute
Condition
Test method and specification
Normal operating
temperature
-5oC to 45oC (Std. temp.
equipment)
• Telcordia GR-63 CORE (NEBS)
Short term operating
temperature
-5oC to 55oC (Std. temp.
equipment)
• Telcordia GR-63 CORE (NEBS)
• ETSI EN 300 019-2-3 Class 3.1 (E)
(not more than 96 consecutive
hours and a total of not more
than 15 days in a year)
Normal operating
humidity
5% to 90% RH (Std.temp.
equipment)
• Telcordia GR-63 CORE (NEBS)
• ETSI EN 300 019-2-3 Class 3.1 (E)
(for Telecordia GR-63-CORE,
this also meets the short term
relative humidity specification)
Operational vibration
0.1 g from 5 to 100 Hz and
return to 5 Hz at a rate of 0.1
octave/minute
• Telcordia GR-63 CORE (NEBS)
Storage temperature
-40 oC to 70oC
• ETSI EN 300 019-1-1 Class 1.2
• Telcordia GR-63 CORE (NEBS)
Handling shock
Transportation
vibration
Packaged and unpackaged
criteria (by weight) per
specification
• Telcordia GR-63 CORE (NEBS)
• ETSI EN 300 019-2-2 Class 2.2 and Class 2.3
Sinusoidal, random, and
• Telcordia GR-63 CORE (NEBS)
non-stationary per respective • ETSI EN 300 019-2-2 Class 2.3
specifications
Table 7-33
Special operating environmental specification for OME6110 system - extended temperature
Attribute
Condition
Test method and specification
Extended operating
temperature
-40oC to 65oC (Ext. temp.
equipment only)
No specification. This option of the product has
been designed to withstand the specified
temperature range at the shelf inlet.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-34 Technical specifications
Electromagnetic specifications
Table 7-34 lists the electromagnetic compatibility of the OME6110 network
element.
Table 7-34
Electromagnetic specifications for OME6110
Electromagnetic topic
Attribute
Test method and specification
Electromagnetic interference
Radiated emissions: “Class A” • ICES-003 (Industry Canada), Iss.3
E-field: 10 kHz to 40 GHz
• EN 300 386 V1.3.2
H-field: 10 Hz to 30 MHz
• EN 55022:1998+A1:2000+A2:2003
• FCC Part 15 Subpart B
• Telcordia GR-1089-CORE, Iss.3
Conducted emissions
• EN 300 386 V1.3.2
10 Hz to 100 MHz
• EN 55022:1998+A1:2000+A2:2003
power and signal cables
• Telcordia GR-1089-CORE, Iss.3
• ETS 300 132-2 V2.1.2
• Bellcore GR-499-CORE, Iss.2
RF Immunity
Radiated RFI
• EN 300 386 V1.3.2
E-field: 10 kHz to 10 GHz
• Telcordia GR-1089-CORE, Iss.3
10V/m
• EN 55024:1998+A1:2001+A2:2003
Conducted RFI
• EN 300 386 V1.3.2
10 Hz to 80 MHz
• EN 55024:1998+A1:2001+A2:2003
power and signal cables
• ETS 300 132-2 V2.1.2
• 3 Vrms (voltage)
• Telcordia GR-1089-CORE, Iss.3
• 89 dBµArms (current)
• Bellcore GR-499-CORE, Iss.2
• 56 dBrnc (voice-band)
Operational Condition: no effect occurs when the system is exposed to
the RF levels described in the specifications above.
Direct and indirect
Direct and indirect ESD
electrostatic discharge (ESD) air discharge up to 15 kV
contact discharge up to 8 kV
• EN 300 386 V1.3.2
• Telcordia GR-1089-CORE, Iss.3
• Telcordia GR-78-CORE
• EN 55024:1998+A1:2001+A2:2003
Operational Condition: no effect occurs when the system is exposed to
the RF levels described in the specifications above.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-35
Table 7-34 (continued)
Electromagnetic specifications for OME6110
Electromagnetic topic
Attribute
Electrical fast transient (EFT) power and signal cables
Test method and specification
• EN 300 386 V1.3.2
4 kV - power and ground
• Telcordia GR-1089-CORE, Iss.3
1 kV - signal
• EN 55024:1998+A1:2001+A2:2003
Operational Condition: No effect occurs when the system is exposed to
the EFT levels described in the specifications above.
Surge (lightning)
signal cables
• EN 300 386 V1.3.2
1.5 kV, 2/10 µs pulse
• Telcordia GR-1089-CORE, Iss.3
0.5 kV, 1.2/50 µs pulse
• EN 55024:1998+A1:2001+A2:2003
Operational Condition: the system will continue to operate as intended
immediately after exposure to the surge levels described in the
specifications above.
Safety specifications
The following section outlines the safety specifications, including:
• general commercial and regulatory
• laser emissions
General commercial and regulatory
The OME6110 complies with the safety requirements of the following
specifications:
• IEC/EN 60950-1:2001+A11:2004
• Telcordia GR-1089-CORE, Iss.3
Laser emission
The OME6110 meets the requirements of the following specifications:
• IEC/EN 60825-1:1994+A11:1996+A2:2001+A1:2002
• IEC/EN 60825-2:2000
• FDA 21 CFR 1040.10
The OME6110 is a class 1 laser product/optical fiber communications system.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-36 Technical specifications
Power and grounding specifications
The following section outlines the power and grounding specifications
DC input voltage range
The operational input voltage range for the OME6110 is -40 V dc to -57.5 V
dc with DC feed. The OME6110 is not damaged when an input voltage of
correct polarity, with a value between zero and -40 V dc (minimum voltage),
is applied for any period of time. The system is not damaged by a reversed
polarity voltage supply, for example, zero to +57.5 V dc (the system does not
function with a reversed polarity supply).
The OME6110 automatically recovers when the input voltage returns to a
value exceeding the minimum voltage within an acceptable period of time and
without any manual intervention.
AC input voltage range
With an AC PSU, the OME6110 shall operate from 90 V to 264 V from 47 to
63 Hz.
The OME6110 meets the specifications listed in Table 7-35.
Table 7-35
Power, grounding, and noise references
Topic
References
Power
• ANSI T1.315-2001, Voltage Levels for DC Powered Equipment
Used in the Telecommunications Environment, 2001.
• ETS 300 132-2, Equipment Engineering (EE); Power supply
interface at the input to telecommunications equipment; Part 2:
Operated by direct current (dc)
• DS8171, Issue 2, 60 Hz and -48 V dc Power for DC Powered
Telecommunication Equipment, Bell Canada
Grounding
• ITU-T K.27, Bonding Configurations and Earthing Inside a
Telecommunication Building), May 1996
• TR-NWT-000295, Bellcore Technical Reference, Isolated Ground
Planes: Definition and Application to Telephone Central Offices.
July 1992
• ETSI EN 300 253, Equipment Engineering (EE); Earthing and
bonding of telecommunication equipment in telecommunication
centres, January 1995
• NFPA70, (US National Electrical Code)
• CSA 22.1, (Canadian Electrical Code)
• Telecordia: GR-1089-CORE, Electromagnetic Compatibility and
Electrical Safety, Issue 2, Revision 1, February 1999, Section 9
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical specifications 7-37
Table 7-35 (continued)
Power, grounding, and noise references
Topic
References
Noise
• ANSI T1.315-2001, Voltage Levels for DC Powered Equipment
Used in the Telecommunications Environment, November 2001
• DS8171, Issue 2, 600 Hz and -48 V dc Power for DC Powered
Telecommunication Equipment, Bell Canada
• ETS 300 132-2, Equipment Engineering (EE); Power supply
interface at the input to telecommunications equipment; Part 2:
Operated by direct current (dc), September 1996
• Telecordia: GR-63-CORE, Network Equipment Building System
(NEBS) Requirements (Bellcore, October 1995), Section 4.6
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
7-38 Technical specifications
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
8-1
Ordering information and system
engineering rules
8-
This chapter provides the ordering information and engineering rules for the
Optical Multiservice Edge 6110 (OME6110) network element. Table 8-1 lists
the topics in this chapter.
Table 8-1
Topics in this chapter
Topic
Page
OME6110 network element configuration rules
Base chassis layout
8-2
Bay equipping rules
8-3
Shelf equipping rules
8-4
Site engineering recommendations
8-5
List of parts
OME6110 base chassis and components
8-6
OME6110 shelf assembly kit
8-8
Circuit packs
8-8
Small form-factor pluggable optic modules
8-9
Electrical interface hardware
8-10
E1/DS1 cable assemblies
8-11
E3/DS3 cable assemblies
8-12
STM-1e cable assemblies
8-12
Ethernet service cable assemblies
8-13
Optical fiber patch cords
8-14
OAM cable assemblies
8-16
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
8-2 Ordering information and system engineering rules
Table 8-1 (continued)
Topics in this chapter
Topic
Page
Power and earthing cable assemblies
8-17
Software load
8-18
Right to use licenses
8-19
Engineering and support services
8-19
OME6110 documentation
8-20
Change application procedures
8-21
RoHS compliant equipment
8-21
Ordering procedures
Ordering OME6110 base chassis, circuit packs, and software
8-23
Ordering cables, documentation, and services
8-32
OME6110 network element configuration rules
This section documents the OME6110 network element configuration rules,
including slot numbering, bay equipping rules, shelf equipping rules, and site
engineering recommendations.
Base chassis layout
Table 8-2 lists the circuit packs or components that can be inserted into the
OME6110 base chassis and the corresponding slot numbers. Figure 8-1 shows
the OME6110 base chassis layout.
Table 8-2
Base chassis components
Circuit pack or component
Slot number
Note
8x10/100BT L1 circuit pack
Slot 4
1
3xE3/DS3 circuit pack
Slot 4
1
28xE1/DS1 circuit pack
Slot 4
1
2x155M circuit pack
Slot 4
1
Power supply unit
(AC or DC)
Slot 1
2
Fan module
Slot 5
2, 3
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-3
Table 8-2 (continued)
Base chassis components
Circuit pack or component
Slot number
Note
16 x E1/DS1 service interface
Slot 2
4
STM-1/OC-3 optical interfaces
Slot 3
4, 5
Note 1: This circuit pack is optional.
Note 2: This is a field replaceable unit.
Note 3: Starting with OME6110 release 2.2 the fan module is optional for standard
temperature applications
Note 4: This interface is inherent on the OME6110 base chassis.
Note 5: SFP modules must be ordered separately.
Figure 8-1
OME6110 base chassis layout
PSU
Power supply module
(dual DC shown)
16xE1/DS1
service interface
2
Optional
service
slot
8
7
6
5
4
Fan
module
3
2
1
8XETH
ESD
Active
Status
RET GND -48V
Power
Optical Multiservice Edge 6110
-48Vdc 2A
Alm. Out
Alm. In
MI / F1
ESI
al
r
ic
rit
C
ajo
M
or
in
M
Rx
Tx
2
LCT
1
Tx 2 Rx
Port 2
OAM ports
LCT port
- Ethernet
Network
Element
alarms
Tx 1 Rx
FAN
E1/DS1 1-16
1
Port 1
ESD jack
location
2xSTM-1/OC3
optical ports
Bay equipping rules
This section provides equipping rules for OME6110 installation in a bay. The
OME6110 shelf can be mounted in a variety of telecommunications equipment
bays, including 19”, NEBS, and ETSI standard bays. The OME6110 shelf also
supports wall-mount installation.
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-4 Ordering information and system engineering rules
Refer to Table 8-3 for OME6110 equipment rack space requirements.
Table 8-3
OME6110 equipment rack space requirements
Equipment
Rack units required
OME6110 shelf with dual DC power feeds
(NT6Q50AA/AB/AC/AD/BA/BC/BD)
1U
OME6110 shelf with single AC power feed
(NT6Q51AA/AC/AD)
1U
75 ohm BNC Termination Panel (NT6Q71EA)
1U
Shelf equipping rules
This section lists the equipping rules for the OME6110 shelf.
There are three types of OME6110 shelves available in Release 2.2:
• OME6110 dual DC power feed shelf (standard temperature)
• OME6110 dual DC power feed shelf (extended temperature)
• OME6110 single AC power feed shelf
For more information on the differences of the various OME6110 base chassis,
refer to Base chassis on page 4-2.
Engineering rules
1 Each shelf at an OME6110 site is a stand-alone network element.
2 Each shelf requires the following components:
— one power supply unit in slot 1
— one fan module for extended temperature applications or fan module
filler for standard temperature applications in slot 5
— one filler panel in slot 4 (if no circuit pack is used)
Note: The 16 x E1/DS1 interface and two STM-1/OC-3 optical interface
ports come equipped with the base chassis. The SFPs for the STM-1/OC-3
optical interfaces must be ordered separately.
3
4
5
Each shelf is capable of supporting only one circuit pack in the optional
service slot.
When equipping an extended temperature, ensure that the PSU, Fan and
circuit pack also support extended temperature, otherwise the system will
operate at standard temperature.
No fiber slack storage is provided for fibers terminating on the OME6110
shelf. Cable relief off the shelf can be handled using the routing brackets
provided with the OME6110 Assembly Kit.
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-5
6
7
8
9
You can only replace (spare) a circuit pack with a circuit pack with the
same product engineering code (PEC).
1+1 MSP/APS, SNCP/UPSR, and unprotected traffic protection schemes
are available. The STM-1/OC-3 optical interfaces must be provisioned in
a MSP/APS group for 1+1 MSP/APS protection, or in unprotected mode
for SNCP/UPSR or unprotected configuration.
1+1 MSP/APS protection group members must be of the same slot.
Only the 2 x 155M, 8 x 10/100BT L1, 28 x E1/DS1 or 3 x E3/DS3 circuit
packs can be inserted in the optional service slot (slot 4).
Note: When the optional service interface slot is not equipped with a
circuit pack, a filler panel must be installed.
10 The STM-1/OC-3 optical interface ports use small form-factor pluggable
(SFP) optic modules. Each active port requires a SFP optic module, which
are ordered separately. Dust covers for the pluggable positions are
included, therefore dust covers do not need to be ordered for unequipped
ports. A maximum of 4 SFP optic modules are required for an OME6110
network element.
11 The 16 x E1/DS1 service interface on the base chassis and the 28 x E1/DS1
circuit pack require the appropriate I/O interface cabling. The default
impedance for the E1/DS1 interfaces is 120/100 ohm. The E1/DS1
interface uses a 64-pin Telco connector. Conversion for E1 services to 75
ohm unbalanced interface can be achieved using the 75 ohm BNC
termination panel.
12 In a rack mount installation, it is recommended to install the 75 ohm BNC
termination panel directly below the OME6110 shelf. If more than one
termination panel is required (for converting impedance of ports on the 16
x E1/DS1 service interface and the 28 x E1/DS1 circuit pack), stack the
termination panels below the OME6110 shelf.
Site engineering recommendations
Consider the following site engineering recommendations when planning a
network deployment.
1 Breaker interface panels or fuse panels should be installed at the top of the
bay.
2 Recommendation is to use 2x2 Amp breakers or fuses for the dual DC
power feeds for each OME6110 base chassis.
3 In extended temperature application, a 1U space between the OME6110
shelves installed in the same rack is mandatory to ensure proper airflow
through the equipment.
4 In standard temperature application, it is recommended to leave 1U space
between OME6110 shelves when installed in the same rack to provide
added air flow through the equipment.
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-6 Ordering information and system engineering rules
5
Optical fiber cables should be routed on the right side of the bay.
Note: No fiber slack storage is provided for fibers terminating on the
OME6110 shelf. Use external fiber management drawers to store excess
fiber cable.
6
E1/DS1 electrical interface cables should be routed on the left side of the
bay for the 16 x E1/DS1 service interface and on the right side of the bay
for the 28 x E1/DS1 circuit pack.
Install power cables on the left side of the OME6110 bay.
Install OAM cables (for Alarm Input, Alarm Output, M1/F1 and ESI ports)
on the left side of the OME6110 bay.
The Ethernet cables should be routed on the right side of the bay for the
8xETH circuit pack, and on the left side of the bay for the LCT port for
DCN access.
7
8
9
List of parts
This section provides the orderable codes available for the OME6110 product.
Use these tables with the ordering procedures (Procedure 8-1 on page 8-23
through Procedure 8-2 on page 8-32) to make sure that a complete and
accurate bill of material is created.
OME6110 base chassis and components
Table 8-5 lists the ordering codes for the base chassis and components. For
rules on equipping the OME6110 base chassis, refer to Refer to Table 8-3 for
OME6110 equipment rack space requirements. on page 8-4.
Table 8-5
OME6110 base chassis and components
Description
Order code
Notes
OME6110 R1.0 DC System; Chassis, PSU, Fan & Filler
NT6Q50AA
1, 2, 11
OME6110 R2.0 DC System; Chassis, PSU, Fan & Filler
NT6Q50AB
1
OME6110 System Kits
OME6110 R2.0 DC System Ext Temp; Chassis, PSU, Fan & Filler NT6Q50BA
1, 3
OME6110 R2.0 AC System; Chassis, PSU, Fan & Filler
NT6Q51AA
1, 4
OME6110 R2.1 DC System; Chassis, PSU, Fan & Filler
NT6Q50AC
1
OME6110 R2.1 DC System Ext Temp; Chassis, PSU, Fan & Filler NT6Q50BC
1, 3
OME6110 R2.1 AC System; Chassis, PSU, Fan & Filler
NT6Q51AC
1, 4
OME6110 R2.2 DC System; Chassis, PSU, Fan Filler & Filler
NT6Q50ADE5 1
OME6110 R2.2 DC System Ext Temp; Chassis, PSU, Fan & Filler NT6Q50BDE5 1, 3
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-7
Table 8-5 (continued)
OME6110 base chassis and components
Description
Order code
Notes
OME6110 R2.2 AC System; Chassis, PSU, Fan Filler & Filler
NT6Q51ADE5 1, 4
OME6110 Power Supply Units
OME6110 DC PSU 35W Dual-feed Rev2
NT6Q30AB
5, 6
OME6110 DC PSU 35W Dual-feed Rev2 Ext Temp
NT6Q30BB
5, 6
OME6110 AC Power Supply Unit 50W
NT6Q31AA
6, 8
Filler Panel Circuit Pack Slot
NT6Q70AA
9
OME6110 Fan Tray with Filter
NT6Q32AA
10
OME6110 Fan Tray with Filter Ext Temp
NT6Q32BA
10
OME6110 Fan Module Filler
NT6Q70AC
OME6110 Filler and Fan modules
Note 1: The OME6110 base chassis is equipped with power supply unit, fan module or fan module filler
and a circuit pack filler. SFPs for the STM-1/OC-3 optical interfaces need to be ordered separately.
Note 2: The release 1.0 base chassis supports only SDH BITS timing sources (2.048 MHz clock or E1
source) and offers limited E1/DS1 path alarms and PMs for the 16xE1/DS1 service interface. This
chassis can only be provisioned in SDH mode.
Note 3: This OME6110 system supports extended temperature. Ensure to order an extended
temperature circuit pack to equip the optional service slot in this shelf. Refer to Table 8-7 on page 8-8
for list of circuit packs.
Note 4: This OME6110 AC system requires an earthing cable to be ordered separately. Refer to Table
8-20 on page 8-17 for the ordering code of the earthing cable.
Note 5: The DC PSU provides a dual-feed OME6110 shelf power termination up to 2 A.
Note 6: The PSU can be ordered as spare or replacement.
Note 7: The manufacturing of NT6Q30AA and NT6Q30BA is discontinued, use NT6Q30AB or
NT6Q30BB.
Note 8: The power cable for the AC PSU must be ordered separately with the appropriate connector
for the deployment region.
Note 9: An empty circuit pack slot must be covered with a filler panel. The filler panel comes equipped
with the base chassis, but can be ordered separately as spare or replacement.
Note 10: Each fan module consists of two fans. This module can be ordered as spare or replacement.
Note 11: The manufacturing of the NT6Q50AA DC system chassis is discontinued, use the equivalent
NT6Q50AB/AC/ADE5 DC system chassis for standard temperature application, NT6Q50BA/BC/BDE5
DC system chassis for extended temperature application.
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-8 Ordering information and system engineering rules
OME6110 shelf assembly kit
The OME6110 system kits described in Table 8-5 on page 8-6 include shelf
mounting brackets for a 19 in. rack. For 23 in. or ETSI standard bay
installations, separate brackets can be obtained with the OME6110 assembly
kit. For wall-mount installation, the required brackets are also available in the
shelf assembly kit. It is recommended to order one assembly kit for each
OME6110 network element, as listed in Table 8-6, for each NE.
Table 8-6
OME6110 shelf assembly kit
Description
Order code
Notes
OME6110 Assy Kit - Cable bracket, 21"/23” flange, rack mounting
screws, cage nuts
NT6Q70BA
1 and 2
Note 1: This assembly kit provides installation brackets for the OME6110 base chassis. Included in the
kit are rack mounting screws, cage nuts, 21”/23” flange and cable routing brackets.
Note 2: It is recommended to have an OME6110 shelf assembly kit for each OME6110 shelf
installation.
Circuit packs
Table 8-7 provides a list of all the circuit packs that can be inserted into the
optional service slot of the OME6110 base chassis.
For rules on equipping the shelf, refer to Refer to Table 8-3 for OME6110
equipment rack space requirements. on page 8-4.
Table 8-7
Circuit packs for optional service slot
Description
Order code
Notes
28xE1/DS1 Circuit Pack
NT6Q10AA
1
28xE1/DS1 Circuit Pack Ext Temp
NT6Q10BA
1, 2
3xE3/DS3 Circuit Pack
NT6Q12AA
1
3xE3/DS3 Circuit Pack Ext Temp
NT6Q12BA
1, 2
8x10/100BT L1 Circuit Pack
NT6Q13AA
1, 3
8x10/100BT L1 Circuit Pack Rev2
NT6Q13AB
1
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-9
Table 8-7
Circuit packs for optional service slot
Description
Order code
Notes
8x10/100BT L1 Circuit Pack Ext Temp
NT6Q13BA
1, 2
2x155M Circuit Pack
NT6Q17ABE5 1, 4
Note 1: Only one circuit pack can be inserted into the OME6110 base chassis.
Note 2: This circuit pack should be used in an extended temp OME6110 base chassis (NT6Q50Bx)
Note 3: The manufacturing of the NT6Q13AA 8x10/100BT L1 circuit pack is continued, use the
equivalent NT6Q13AB 8x10/100BT L1 Rev2 circuit pack.
Note 4: SFPs for the STM-1/OC-3 interfaces need to be ordered separately.
Small form-factor pluggable optic modules
Table 8-8 lists the small form-factor pluggable optic modules.
Table 8-8
Small form-factor pluggable optic modules
Description
Order Code
Notes
STM-1/OC-3 SR-0 (Multimode) 1310 nm Enhanced SFP Module
NTTP02AD
1, 2, 3
STM-1/OC-3 IR1/S1.1 1310 nm XCT Enhanced SFP Module
NTTP02CD
1, 2, 3
STM-1/OC-3 LR1/L1.1 1310 nm XCT Enhanced SFP Module
NTTP02ED
1, 2, 3
STM-1/OC-3 LR2/L1.2 1550 nm XCT Enhanced SFP Module
NTTP02FD
1, 2, 3
STM-1/OC-3 SFPs
STM-1/4/OC-3/12 SFPs
STM-1/4/OC-3/12 IR1/S1.1_S4.1 1310 nm XCT Enhanced SFP Module NTTP04CF
1, 2
STM-1/4/16/OC-3/12/48 CWDM SFPs
STM-1/4/16/OC-3/12/48 CWDM (1471 nm) XCT Enhanced SFP
Module
NTK590LH
1
STM-1/4/16/OC-3/12/48 CWDM (1491 nm) XCT Enhanced SFP
Module
NTK590MH
1
STM-1/4/16/OC-3/12/48 CWDM (1511 nm) XCT Enhanced SFP
Module
NTK590NH
1
STM-1/4/16/OC-3/12/48 CWDM (1531 nm) XCT Enhanced SFP
Module
NTK590PH
1
STM-1/4/16/OC-3/12/48 CWDM (1551 nm) XCT Enhanced SFP
Module
NTK590QH
1
STM-1/4/16/OC-3/12/48 CWDM (1571 nm) XCT Enhanced SFP
Module
NTK590RH
1
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-10 Ordering information and system engineering rules
Table 8-8 (continued)
Small form-factor pluggable optic modules
Description
Order Code
Notes
STM-1/4/16/OC-3/12/48 CWDM (1591 nm) XCT Enhanced SFP
Module
NTK590SH
1
STM-1/4/16/OC-3/12/48 CWDM (1611 nm) XCT Enhanced SFP
Module
NTK590TH
1
NTTP60AE
1, 2
NTTP09BD
1, 2, 3, 4
100-Base-BX10-D Bidirectional- downstream, 1530 nm Tx, 10 km SFP NTTP10BD
Module
1, 2, 3, 4
STM-1e SFPs
STM-1e Enhanced SFP Module
100-Base SFPs
100-Base-BX10-U Bidirectional- upstream, 1310nm Tx, 10 km SFP
Module
Note 1: This SFP module is used with the STM-1/OC-3 optical interface ports inherent on the
OME6110 base chassis..
Note 2: This SFP module is used with the STM-1/OC-3 optical interface of the 2x155M tributary circuit
pack (NT6Q17ABE5)
Note 3: This SFP module supports extended temperature and can be used on an extended temp
OME6110 base chassis (NT6Q50Bx).
Note 4: Used for a bidirectional link over a single fiber with an upstream SFP fitted at one end of the
link and an downstream SFP fitted at the other end of the link. The upstream SFP transmits at 1310 nm
and receives at 1530 nm, the downstream SFP transmits at 1530 nm and receives at 1310 nm.
Electrical interface hardware
Table 8-9 lists the hardware associated to the 16 x E1/DS1 electrical interface
on the base chassis and the 28 x E1/DS1 circuit pack, when conversion for 75
ohm ports is required for E1 services. For rules on equipping the shelf, refer to
Refer to Table 8-3 for OME6110 equipment rack space requirements. on page
8-4.
Table 8-9
E1 interface conversion hardware
Description
Order code
Notes
75 ohm BNC Term Panel, 16 channel
NT6Q71EA
1, 2
Telco to Telco 1M Cable - Left Routing
NT6Q74AA
3
Telco to Telco 5M Cable - Left Routing
NT6Q74CA
3
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-11
Table 8-9
E1 interface conversion hardware
Description
Order code
Notes
Telco to Telco 1M Cable - Right Routing
NT6Q75AA
4
Telco to Telco 5M Cable - Right Routing
NT6Q75CA
4
Note 1: This panel provides conversion from 120 ohm to 75 ohm for the E1/DS1 interfaces for E1
services only. The unit is a 1U high rack-mountable panel.
Note 2: This termination panel can be used to convert E1 services from the 16xE1/DS1 interface on
the base chassis or the 28xE1/DS1 circuit pack. An additional overlay sticker is provided for proper
labeling when converting the 17-28 E1 ports of the 28xE1/DS1 circuit pack.
Note 3: This cable is required for connecting the E1 ports on the 16xE1/DS1 interface on the base
chassis to the 75 ohm termination panel.
Note 4: This cable is required for connecting the E1 ports on the 28xE1/DS1 circuit pack to the 75
ohm termination panel.
E1/DS1 cable assemblies
Table 8-10 and Table 8-11 lists the available E1/DS1 interface cables,
respectively. These cables are used to provide E1 (input and output)
connectivity for 120 ohm applications, where no termination panel is required
and DS1 connectivity for 100 ohm applications.
Note: Refer to E1/DS1 cable pinouts and assemblies on page 7-17 for the
cable requirements if the cables are to be sourced locally.
Table 8-10
E1 cable assemblies
Description
Order code
Notes
120Ohm Telco 5M Cable - Left Routing
NT6Q72BA
1
120Ohm Telco 10M Cable - Left Routing
NT6Q72CA
1
120Ohm Telco 15M Cable - Left Routing
NT6Q72DA
1
120Ohm Telco 20M Cable - Left Routing
NT6Q72EA
1
120Ohm Telco 5M Cable - Right Routing
NT6Q73BA
2, 3
120Ohm Telco 10M Cable - Right Routing
NT6Q73CA
2, 3
120Ohm Telco 15M Cable - Right Routing
NT6Q73DA
2, 3
120Ohm Telco 20M Cable - Right Routing
NT6Q73EA
2, 3
Note 1: This cable provides 64-pin balanced 120 ohm for the E1 services on the 16xE1/DS1 interface
on the base chassis.
Note 2: This cable provides 64-pin balanced 120 ohm for the E1 services on the 28xE1/DS1 circuit
pack.
Note 3: This cable has a shielded connector to connect to the 28xE1/DS1 circuit pack.
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-12 Ordering information and system engineering rules
.
Table 8-11
DS1 cable assemblies
Description
Order code
Notes
100Ohm Telco 15M Cable - Left Routing
NT6Q72QA
1
100Ohm Telco 30M Cable - Left Routing
NT6Q72TA
1
100Ohm Telco 15M Cable - Right Routing
NT6Q73QA
2, 3
100Ohm Telco 30M Cable - Right Routing
NT6Q73TA
2, 3
Note 1: This cable provides 64-pin balanced 100 ohm for the DS1 services on the 16xE1/DS1 interface
on the base chassis.
Note 2: This cable provides 64-pin balanced 100 ohm for the DS1 services on the 28xE1/DS1 circuit
pack.
Note 3: This cable has a shielded connector to connect to the 28xE1/DS1 circuit pack.
E3/DS3 cable assemblies
Table 8-12 lists the available E3/DS3 coaxial cables for the 3 x E3/DS3 circuit
pack. These cables are used to provide E3/DS3 (input and output) connectivity
to the OME6110 network element.
Table 8-12
E3/DS3 cable assemblies
Description
Order code
Notes
BNC Connector (735A)
A0609866
1
DS3 735A Coaxial Cable - 10M BNC
NT7E43BB
2, 3
DS3 735A Coaxial Cable - 30M BNC
NT7E43BD
2, 3
DS3 735A Coaxial Cable - 60M BNC
NT7E43BG
2, 3
Note 1: Use this connector to terminate the E3/DS3 cabling at the customer interface equipment.
Note 2: Two cable assemblies are required per E3/DS3 port (for receive and transmit).
Note 3: This cable is terminated with a BNC at one end only. A BNC connector (A0609866) should be
ordered to connect to the customer interface equipment.
STM-1e cable assemblies
Table 8-13 lists the available STM-1 coaxial cableforms used to provide
STM-1e connectivity to the STM-1e SFP modules on the two optical ports on
the base chassis.
Table 8-13
STM-1e cable assemblies
Description
Order code
STM-1e cables
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Notes
Ordering information and system engineering rules 8-13
Table 8-13 (continued)
STM-1e cable assemblies
Description
Order code
Notes
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 10 m
NTTC04AA
1
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 20 m
NTTC04AB
1
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 30 m
NTTC04AC
1
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 40 m
NTTC04AD
1
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 50 m
NTTC04AE
1
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 60 m
NTTC04AF
1
Connector Coax, BNC 75 ohm, Male, Straight Plug for use with RG179DT
Cable
A0360953
2
Connector Coax, BNC 75 ohm, Female Straight, Bulkhead, Jack,
Crimp/Crimp, for use with RG179DT Cable
A0678277
2
Connector Coax, BT43 75 ohm, Male, Straight, Bulkhead DDF, Crimp/Crimp, A0620780
for use with RG179DT Cable
2
Connector Coax, HDC43 Bulkhead Plug (Male) Crimp/Crimp, RG179/U, DDF N0032563
Mount, Single PC. Body
2
Connector Coax, DIN 1.0/2.3 mm, Straight Cable Plug (Male) Crimp/Crimp
75 ohm RG179/U
2
Single connectors
N0032582
Note 1: This cable provides a single STM-1e co-axial connector. The cable uses RG179DT coaxial
cable. You must order an appropriate connector for the open end of each cable assembly. Two cable
assemblies are required for every STM-1e SFP module.
Note 2: These are single field terminable connectors for the STM-1e cable assemblies (NTTC04Ax).
Ethernet service cable assemblies
Table 8-14 lists the available Ethernet cableforms used to provide connectivity
to the 10/100BT interfaces associated with the 8x10/100BT L1 circuit packs.
Shielded twisted pair (STP) cables are required to connect to the Ethernet ports
on the 8x10/100BT L1 circuit pack.
Note: LAN ports on the 8x10/100BT circuit packs are wired as
MDI/MDI-X, and auto-detect the type of cable connected to it (straight or
crossover).
Table 8-14
Ethernet service cable assemblies
Description
Order code
Notes
Ethernet service (STP) cables
Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 5 m
NTTC09CAE6 1
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-14 Ordering information and system engineering rules
Table 8-14 (continued)
Ethernet service cable assemblies
Description
Order code
Notes
Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 15 m
NTTC09CCE6 1
Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 30 m
NTTC09CEE6 1
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 5 m
NTTC09DAE6 1
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 15 m
NTTC09DCE6 1
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 30 m
NTTC09DEE6 1
Note 1: This cable provides an Ethernet connection for the 10/100BT interfaces on the 8x10/100BT
circuit pack. Each cable has two RJ45 connectors and uses shielded twisted pair Category 5E cable.
Optical fiber patch cords
Table 8-15 lists the available optical fiber patch cords.
Table 8-15
Optical fiber patch cords
Description
Order code
Notes
Optical patchcords, LC-LC, SM, Simplex
NTTC50Ax
1,2
Optical patchcords, LC-SC, SM, Simplex
NTTC50Bx
1,2
Optical patchcords, LC-FC, SM, Simplex
NTTC50Cx
1,2
Optical patchcords, LC-ST, SM, Simplex
NTTC50Dx
1,2
Optical patchcords, LC-LC, SM, Duplex
NTTC53Ax
1,2
Optical patchcords, LC-SC, SM, Duplex
NTTC53Bx
1,2
Optical patchcords, LC-FC, SM, Duplex
NTTC53Cx
1,2
Optical patchcords, LC-ST, SM, Duplex
NTTC53Dx
1,2
Optical patchcords, LC-LC, MM 50 micron, Simplex
NTTC56Ax
1,3
Optical patchcords, LC-SC, MM 50 micron, Simplex
NTTC56Bx
1,3
Optical patchcords, LC-FC, MM 50 micron, Simplex
NTTC56Cx
1,3
Optical patchcords, LC-ST, MM 50 micron, Simplex
NTTC56Dx
1,3
Optical patchcords, LC-LC, MM 50 micron, Duplex
NTTC59Ax
1,3
Optical patchcords, LC-SC, MM 50 micron, Duplex
NTTC59Bx
1,3
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-15
Table 8-15 (continued)
Optical fiber patch cords
Description
Order code
Notes
Optical patchcords, LC-FC, MM 50 micron, Duplex
NTTC59Cx
1,3
Optical patchcords, LC-ST, MM 50 micron, Duplex
NTTC59Dx
1,3
Note 1: The optical patchcords are available in different lengths. The last digit of the order code defines
the length as shown in Table 8-16 on page 8-15.
Note 2: The singlemode fibers are used to transmit 1310 nm, 1550 nm and DWDM frequency signals
on singlemode fiber plant.
Note 3: The 50 micron multimode fibers are used to transmit 850 nm frequency signals on 50 micron
multimode fiber plant.
Table 8-16 lists the available lengths of optical fiber patchcords.
Table 8-16
Lengths of optical fiber patchords
Length
Last digit of order code
1 meter
A
2 meters
B
3 meters
C
5 meters
D
7 meters
E
10 meters
F
13 meters
G
15 meters
H
20 meters
J
25 meters
K
30 meters
L
Note: This table defines the length and last digit of the
order codes shown in Table 8-15 on page 8-14. For
example, an NTTC50AD is an optical patchcord,
LC-LC, SM, Simplex, 5 meters.
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-16 Ordering information and system engineering rules
OAM cable assemblies
Table 8-17 through Table 8-19 list the available OAM cable assemblies. These
cables are used to provide synchronization, alarm, user interface and network
element connectivity. Refer to Procedure 8-2 on page 8-32 for ordering
instructions.
Note: The LCT port on the OME6110 base chassis is wired as MDI. Use
crossover cables to connect the LCT port to other MDI ports (such as those
on workstations). Use straight-through cables to connect the LCT port to
MDI-X ports (such as those on switches).
Table 8-17
DCN and craft access cables
Description
Order code
Notes
F1 cable
NT6Q71AF
1
Modem Cable
NT6Q71AG
2
Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 5 m NTTC09CAE6 3
Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 15 m NTTC09CCE6 3
Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 30 m NTTC09CEE6 3
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 5 m
NTTC09DAE6 4
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 15 m NTTC09DCE6 4
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 30 m NTTC09DEE6 4
Note 1: This F1 interface cable connects to the serial port on the base chassis and supports an
asynchronous interface.
Note 2: This modem cable has the DSR pin isolated.
Note 3: This cable provides an Ethernet connection between the LCT port on the base chassis to
a PC directly connected. The cable has two RJ45 connectors and uses shielded twisted pair
Category 5E cable.
Note 4: This cable provides an Ethernet connection between the LCT port to the DCN network. The
cable has two RJ45 connectors and uses shielded twisted pair Category 5E cable.
Table 8-18
Alarm and telemetry cables
Description
Order code
Notes
OME6110 - Environmental alarm cable kit
NT6Q59AB
1
Note 1: This environmental alarm cable kit provides a pair of alarm cables for the ALMIN and ALMOUT
ports.These cables provide the 7 alarm inputs or the critical, major, minor alarm outputs of the shelf to
a cross connect location.
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-17
Table 8-19
Synchronization cable
Description
Order code
Notes
Clock (BITS) Cable (120 ohm)
NT6Q71AC
1, 3
Clock (BITS) Cable (inc 75 ohm convertor)
NT6Q71AE
2, 3
Note 1: This clock cable supports 120 ohm impedance with RJ-45 connector for connection to the
RJ-45 ESI port on the base chassis. This cable used for the timing cable for SDH and SONET modes.
Note 2: This clock cable supports 75 ohm impedance and comes with a balun converter for connection
to the RJ-45 ESI port on the base chassis.
Note 3: This clock cable supports 4 synchronization signals. (2 inputs and 2 outputs)
Power and earthing cable assemblies
Table 8-20 lists the available power and earthing cable assemblies for the
OME6110 base chassis. For OME6110 NEs equipped with a dual-DC feed
PSU, a DC cable kit must be ordered for each network element installation.
When the AC PSU is used, an earthing cable and an AC power cable,
compliant to the universal AC power socket (IEC C14) for the deployment
region, must be ordered. For more information on the PSU, refer to Power
supply units on page 4-4. Refer to Procedure 8-2 on page 8-32 for ordering
instructions.
Table 8-20
Power and earthing cable assemblies
Description
Order code
Notes
OME6110 - DC Cable kit - 3M
NT6Q59AA
1
OME6110 - DC Cable kit - 10M
NT6Q59BA
2
OME6110 - DC Cable Kit -3M North America
NT6Q59MA
3
OME6110 - DC Cable kit - 10M North America
NT6Q59NA
4
Earthing Cable
NT6Q71AA
5
Nortel Euro/C13 2 meter AC cord
NTK955CB
6
Nortel Danish/C13 2 meter AC cord
NTK955CC
6
Nortel Israel/C13 2 meter AC cord
NTK955CE
6
Nortel Italian/C13 2 meter AC cord
NTK955CF
6
Nortel Swiss/C13 2 meter AC cord
NTK955CG
6
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-18 Ordering information and system engineering rules
Table 8-20
Power and earthing cable assemblies
Description
Order code
Notes
Nortel U.K./C13 2 meter AC cord
NTK955CH
6
Nortel North America/C13 2.5 meter AC cord
NTK955CK
6
Note 1: This DC cable kit provides an earthing cable and a pair of 3 meter BL/BK/GR power cables.
Note 2: This DC cable kit provides an earthing cable and a pair of 10 meter BL/BK/GR power cables.
Note 3: This DC cable kit provides an earthing cable and a pair of 3 meter RD/BK/GR power cables
for North American standards.
Note 4: This DC cable kit provides an earthing cable and a pair of 10 meter RD/BK/GR power cables
for North American standards.
Note 5: An earthing cable kit must be ordered for each OME6110 AC system, NT6Q51AA.
Note 6: An AC power cord must be ordered for the corresponding deployment region of the OME6110
AC system, NT6Q51Ax.
Software load
This section provides the information for ordering OME6110 software, as
shown in Table 8-21.
Table 8-21
Software superset
Description
Order code
Notes
OME6110 R1.0 CD-ROM
NT6Q81AA
1
OME6110 R2.0 CD-ROM
NT6Q81BA
2
OME6110 R2.1 CD-ROM
NT6Q81BB
3
OME6110 R2.2 CD-ROM
NT6Q81BC
4
Note 1: This code provides one copy of the OME6110 Release 1.0 software load on a CD-ROM. The
local craft access terminal load is imbedded in the network element software load.
Note 2: This code provides one copy of the OME6110 Release 2.01 software load on a CD-ROM. The
local craft access terminal load is imbedded in the network element software load.
Note 3: This code provides one copy of the OME6110 Release 2.1 software load on a CD-ROM. The
local craft access terminal load is imbedded in the network element software load.
Note 4: This code provides one copy of the OME6110 Release 2.2 software load on a CD-ROM. The
local craft access terminal load is imbedded in the network element software load.
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-19
Right to use licenses
The right to use licences are listed in Table 8-22.
Table 8-22
Right to use licenses
Description
Order Code
Notes
OME6110 R1.0 SW Certificate 1/NE
NT6Q84AA
1
OME6110 R2.0 SW Certificate 1/NE
NT6Q84BA
1
OME6110 R2.1 SW Certificate 1/NE
NT6Q84BB
1
OME6110 R2.2 SW Certificate 1/NE
NT6Q84BC
1
OME6110 Base SW RTU 1/NE
NT6Q80AA
2
Note 1: One OME6110 software certificate is required for each OME6110 network element.
Note 2: One OME6110 Base RTU is required for each OME6110 network element.
Engineering and support services
Nortel offers the following engineering and support services for the
OME6110. In addition to the services described below, Nortel offers a
selection of services to help you plan, deploy, operate, and maintain your
optical networks. For more information about these services, contact your
Nortel representative or visit www.nortel.com/services.
Table 8-23
Engineering and support services
Description
Order code
Hot staging service for OME6110
NTYY99CJ
Notes
Note: Nortel staging services are designed to prepare network components for integration into a
customer’s network. By centralizing the execution of services typically performed in the field at a staging
facility, the product can be delivered to the customer in its most simplified, cost effective, and integrated
form. Hot staging services for the OME6110 product consist of system testing validation prior to delivery
to the customer site.
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-20 Ordering information and system engineering rules
OME6110 documentation
This section provides documentation ordering information and a brief
overview of the Nortel technical publication (NTPs) libraries and individual
documents that can be ordered for OME6110 network elements.
Documentation is available on paper and on CD-ROM. Table 8-24 lists the
ordering information for NTP packages.
Table 8-24
OME6110 documentation
Description
Order code
Release 1.0 documentation
OME6110 R1.0 NTP (Paper)
NT6Q65AA
OME6110 R1.0 NTP (CD-ROM)
NT6Q64AA
OME6110 R1.0 Planning Guide
NT6Q92AA
Release 2.0 documentation
OME6110 R2.0 NTP (Paper)
NT6Q65AB
OME6110 R2.0 NTP (CD-ROM)
NT6Q64AB
OME6110 R2.0 Planning Guide
NT6Q92AB
Release 2.1 documentation
OME6110 R2.1 NTP (Paper)
NT6Q65AC
OME6110 R2.1 NTP (CD-ROM)
NT6Q64AC
OME6110 R2.1 Planning Guide
NT6Q92AC
Release 2.2 documentation
OME6110 R2.2 NTP (Paper)
NT6Q65AD
OME6110 R2.2 NTP (CD-ROM) Note 2:
NT6Q64AD
OME6110 R2.2 Planning Guide
NT6Q92AD
Note 1: Refer to table Table 8-25 for a list of documents included in the NTP suite.
Note 2: The Interactive CD-ROMs are being replaced with the NTDA CD-ROM for new product
releases starting with OME6110 R2.2. Interactive CDs continue to be available for previous product
releases that are not manufacturing discontinued. The NTDA CD requires no custom software for users
to load, simply use your internet browser and Adobe Acrobat Reader to view PDFs and access various
Nortel technical support websites. The NTDA CD interface mirrors documentation that is available
online at www.nortel.com/support. This NTDA CD includes all OME6110 R2.2 NTPs and guides.
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-21
Table 8-25 lists the OME6110 NTP Library Suite.
Table 8-25
OME6110 NTP Library Suite
NTPs
Document code
About the OME6110 NTP Library
323-1853-090
TL1 Description and Procedures (See Note)
323-1853-190
Local Craft Access User Guide
323-1853-195
Installation, Commissioning and Testing Procedures
323-1853-201
Provisioning and Protection Switching Procedures
323-1853-310
Trouble Clearing and Module Replacement Procedures
323-1853-543
Note: The TL1 Description and Procedure NTP is introduced in OME6110 release 2.2.
Change application procedures
Table 8-26 lists the OME6110 change application procedures (CAPs).
Table 8-26
OME6110 CAPs
CAPs
Document code
OME6110 Upgrade CAP from Release 1.0 to Release 2.01
NT6Q93AA
OME6110 Upgrade CAP from Release 2.0/2.01 to Release 2.1
NT6Q93AB
OME6110 Upgrade CAP from Release 2.1 to Release 2.2
NT6Q93AD
RoHS compliant equipment
Nortel is fully committed to meeting the requirements of the European Union
Environmental Directives (EUED) and in particular the Restriction of
Hazardous Substances (RoHS) Directive 2002/95/EC. The RoHS Directive
becomes law for customers within the EU from 1st July 2006.
As a consequence of this, equipment for the OME6110 is being made RoHS
compliant. To help differentiate between the compliant and non-compliant
equipment, Nortel has adopted a policy for equipment that has been updated to
become for RoHS compliant of either:
•
adding “E5”, “E6” or “L6” as a suffix to the existing product equipment
code (PEC). E5 indicates that it is RoHS 5/6 compliant, E6 indicates that
it is RoHS 6/6 compliant, and L6 indicates that it is Low Smoke Zero
Halogen (LSZH) and RoHS 6/6 compliant.
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-22 Ordering information and system engineering rules
•
changing a single digit in the PEC (for example, ‘NTRU0501’ changes to
‘NTRU6501’ where the 5th digit is changed to ‘6’ to indicate that it is
RoHS 6/6 compliant)
The PEC for equipment that is already RoHS compliant remains the same.
Customers who operate within the EU must order the RoHS compliant version
of OME6110 equipment for equipment being supplied after 1st July 2006.
There is no change to the behavior or functionality of equipment that has been
updated to become RoHS compliant, nor is there any change required to the
software deployed - the revised RoHS compliant equipment is backward
compatible with the non-RoHS compliant version. Thus, customers outside the
EU may order the standard equipment but may receive a RoHS compliant
version.
RoHS compliant equipment include labels which indicate the RoHS
compliance level.
Further information on the Nortel RoHS strategy will be made available on the
appropriate product pages on the Nortel web site (www.nortel.com).
Table 8-29 on page 8-36 provides details for converting between the
non-RoHS and the RoHS codes.
Ordering procedures
Use the following procedures to order equipment, software, documentation,
and services for an OME6110 network deployment.
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-23
Procedure 8-1
Ordering OME6110 base chassis, circuit packs, and
software
Use this procedure to order OME6110 base chassis, circuit packs, and
software. Repeat this procedure for each network element at a site in the
OME6110 network.
Before you start
• Complete a network design.
• Read OME6110 network element configuration rules on page 8-2.
• Photocopy Table 8-27 on page 8-31 and Table 8-29 on page 8-36 (if required).
Procedure tasks
• Record requirements (step 1).
• Order base chassis (step 12).
• Order a circuit pack (step 15).
• Order OME6110 assembly kit (step 22).
• Order small form-factor pluggable optics modules (step 21).
• Order the 75 ohm termination panel (step 23)
• Order E1/DS1 cables (step 24).
• Order software and RTU licences (step 33).
Expected results
• You have a complete list of base chassis, circuit packs, and software for an OME6110 site.
• If the expected results do not occur:
— Review the network design and repeat the procedure.
— Contact your next level of support.
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-24 Ordering information and system engineering rules
Procedure 8-1 (continued)
Ordering OME6110 base chassis, circuit packs, and software
Action
Step
Action
Note: Use a photocopy of Table 8-27 on page 8-31 for this procedure. All line
number references are to this table unless noted otherwise.
1
2
Determine the software release required.
If software
Then
Release 2.0/2.01 is required
Enter ‘Rel 2’ on Line 1
Release 2.1 is required
Enter ‘Rel 2.1’ on Line 1
Release 2.2 is required
Enter ‘Rel 2.2’ on Line 1
Determine if extended temperature application is required for this site.
If you require an
Then
Extended temperature OME6110 Enter ‘yes’ on Line 2
otherwise
Enter ‘no’ on Line 2
Note: Extended temperature application is offered only with DC PSU.
3
Determine if AC power is required at this site.
If you require
Then
AC power for the OME6110
Enter ‘AC’ on Line 3
DC power for the OME6110
Enter ‘DC’ on Line 3
Note: The AC PSU does not support extended temperature application.
4
Determine the number of E1/DS1 services that are required, record the
number in Line 4. If no E1/DS1 services are required, enter ‘none’ on Line 4.
Note: A maximum of 44 E1/DS1 ports can be provisioned per OME6110
shelf. (16 ports from the 16xE1/DS1 interface on the base chassis and 28
ports from the optional 28xE1/DS1 circuit pack)
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-25
Procedure 8-1 (continued)
Ordering OME6110 base chassis, circuit packs, and software
Step
Action
5
Determine the additional circuit pack required.
If you need
Then
more than 16 E1/DS1 services
(see Line 4)
Enter ‘28xE1/DS1’ in Line 5.
E3/DS3 services
Enter ‘3xE3/DS3’ in Line 5.Go to step 9.
10/100BT L1 services
Enter ‘8x10/100BT’ in Line 5.Go to
step 10.
STM-1/OC-3 services
Enter ‘2x155M’ in Line 5.Go to step 14.
no additional services
Enter ‘none’ in Line 5.
Note: The OME6110 base chassis only has one optional slot for additional
services. Only one circuit pack can be added to the base chassis. Refer to
Table 8-3, OME6110 equipment rack space requirements on page 8-4 for
more details.
6
7
Determine the type of E1/DS1 cables required.
If you require
Then
E1 electrical interfaces
at 75 Ohm
Enter ‘75 ohm’ in Line 6.
E1/DS1 electrical interfaces
at 120 Ohm
Enter ‘120 ohm’ in Line 6.
DS1 electrical interfaces
Enter ‘100 ohm’ in Line 6.
no electrical E1/DS1 services
Enter ‘none’ in Line 6.
Determine the number of 64-pin Telco cables for E1/DS1 interface
requirements:
If Line 4 is in the range
Then
from 1 to 16
Enter ‘1’ in Line 7. Go to step 8
from 16 to 32
Enter ‘2’ in Line 7. Go to step 8
from 32 to 44
Enter ‘3’ in Line 7. Go to step 8
none
Enter ‘none’ on Line 7. Go to step 11
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-26 Ordering information and system engineering rules
Procedure 8-1 (continued)
Ordering OME6110 base chassis, circuit packs, and software
Step
Action
8
Determine the length for E1/DS1 cables.
If Line 6 is
Then determine the length of cable
75 ohm
Enter 1 or 5 for the length of the
required cable in Line 8.
120 ohm
Enter 5, 10, 15 or 20 for the length of the
required cable in Line 8.
100 ohm
Enter 15 or 30 for the length of the
required cable in Line 8.
none
Enter ‘none’ in Line 8.
9
Enter the number of E3/DS3 ports to be deployed in Line 9. Go to step 11.
10
Enter the number of 10/100BT ports to be deployed in Line 10.
11
Select the release of the OME6110 system to be ordered.
If
Then
Line 1 is ‘Rel 2.0/2.01’ Go to step 12
Line 1 is ‘Rel 2.1’
12
13
Go to step 13
Order the Release 2.0/2.01 OME6110 system:
If
Then order
Line 2 is ‘yes’
one (1) NT6Q50BA, OME6110 R2.0 DC system - ext
temp. Go to step 15.
Line 2 is ‘no’ and
Line 3 is ‘AC’
one (1) NT6Q51AA, OME6110 R2.0 AC system - std
temp. Go to step 16.
Line 2 is ‘no’ and
Line 3 is ‘DC’
one (1) NT6Q50AB, OME6110 R2.0 DC system - std
temp. Go to step 17
Order the Release 2.1 OME6110 system:
If
Then order
Line 2 is ‘yes’
one (1) NT6Q50BC, OME6110 R2.1 DC system - ext
temp. Go to step 15.
Line 2 is ‘no’ and
Line 3 is ‘AC’
one (1) NT6Q51AC, OME6110 R2.1 AC system - std
temp. Go to step 16.
Line 2 is ‘no’ and
Line 3 is ‘DC’
one (1) NT6Q50AC, OME6110 R2.1 DC system - std
temp. Go to step 17.
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-27
Procedure 8-1 (continued)
Ordering OME6110 base chassis, circuit packs, and software
Step
Action
14
Order the Release 2.2 OME6110 system:
15
16
If
Then order
Line 2 is ‘yes’
one (1) NT6Q50BDE5, OME6110 R2.2 DC system ext temp. Go to step 15.
Line 2 is ‘no’ and
Line 3 is ‘AC’
one (1) NT6Q51ADE5, OME6110 R2.2 AC system std temp. Go to step 16.
Line 2 is ‘no’ and
Line 3 is ‘DC’
one (1) NT6Q50ADE5, OME6110 R2.2 DC system std temp. Go to step 17.
Order the additional circuit pack required (for extended temp).
If Line 5 is
Then order
28xE1/DS1
one (1) NT6Q10BA, 28xE1/DS1 circuit pack - ext
temp. Go to step 22.
3xE3/DS3
one (1) NT6Q12BA, 3xE3/DS3 circuit pack - ext temp.
Go to step 18.
8x10/100BT
one (1) NT6Q13BA, 8x10/100BT L1 circuit pack - ext
temp. Go to step 19.
none
nothing (optional service slot will be equipped with filler
faceplate.Go to step 22.
Order an earthing cable, NT6Q71AA for the OME6110 AC system and order
the appropriate AC PSU cable for the deployment region.
Note: Refer to Table 8-20 on page 8-17 for orderable codes of the earthing
cable and the AC power cord for the deployment regions.
17
Order the additional circuit pack required (for standard temp).
If Line 5 is
Then order
28xE1/DS1
one (1) NT6Q10AA, 28xE1/DS1 circuit pack. Go to
step 21.
3xE3/DS3
one (1) NT6Q12AA, 3xE3/DS3 circuit pack
8x10/100BT
one (1) NT6Q13AB, 8x10/100BT L1 circuit pack. Go to
step 19. (see Note)
2x155M
one (1) NT6Q17ABE5, 2x155M circuit pack. Go to
step 20
none
nothing (optional service slot will be equipped with filler
faceplate. Go to step 22.
Note: Refer to 8x10/100BT L1 circuit pack on page 4-11 for details on the
different versions of the 8x10/100BT L1 circuit pack.
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-28 Ordering information and system engineering rules
Procedure 8-1 (continued)
Ordering OME6110 base chassis, circuit packs, and software
Step
Action
18
Order the number of E3/DS3 cables specified in Line 9 to connect to the
3xE3/DS3 circuit pack. Go to step 21.
Note: Refer to Table 8-12 on page 8-12 for orderable part numbers and
application rules.
19
Order the number of 8x10/100BT cables specified in Line 10 to connect to the
8x10/100BT L1 circuit pack. Go to step 21.
Note: Refer to Table 8-14 on page 8-13 for orderable part numbers and
application rules.
20
Order four (4) small form-factor pluggable optic modules. Go to step 22
21
Order two (2) small form-factor pluggable optic modules.
Note: Refer to Table 8-8 on page 8-9 and Table 8-3, OME6110 equipment
rack space requirements on page 8-4 for orderable part numbers and
application rules for the small form-factor pluggable optic modules.
22
Order one (1) NT6Q70BA, OME6110 assembly kit.
23
Order the 75 ohm termination panel:
24
25
If Line 6 is
Then
75 ohm
Order the number of NT6Q71E1, 75 ohm BNC
termination panel as specified on Line 7. Go to
step 24.
120 ohm
Go to step 27
100 ohm
Go to step 30
none
Go to step 33
Order the E1 cable for the 75 ohm termination panel for the 16xE1/DS1
service interface:
If Line 8 is
Then order
1
one (1) NT6Q74AA (Left routing - 1 meter cable)
5
one (1) NT6Q74CA (Left routing - 5 meter cable)
Subtract “1” from the value at Line 7.
If the result is
Then
0
Go to step 33
1 or 2
Go to step 26
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-29
Procedure 8-1 (continued)
Ordering OME6110 base chassis, circuit packs, and software
Step
Action
26
Order the E1 cables for the 75 ohm termination panel for the 28xE1/DS1
circuit pack:
If Line 8 is
Then order the number obtained at step 25 times of
1
NT6Q75AA (Right routing - 1 meter cable)
5
NT6Q75CA (Right routing - 5 meter cable)
Go to step 33.
27
28
29
Order the E1 cable for the 120 ohm application for the 16xE1/DS1 service
interface:
If Line 8 is
Then order
5
one (1) NT6Q72BA (Left routing - 5 meter cable)
10
one (1) NT6Q72CA (Left routing - 10 meter cable)
15
one (1) NT6Q72DA (Left routing - 15 meter cable)
20
one (1) NT6Q72EA (Left routing - 20 meter cable)
Subtract “1” from the value at Line 7.
If the result is
Then
0
Go to step 33
1 or 2
Go to step 29
Order the E1 cables for the 120 ohm application for the 28xE1/DS1 circuit
pack:Go to step 33.
If Line 8 is
Then order the number obtained at step 28 times of
5
one (1) NT6Q73BA (Right routing - 5 meter cable)
10
one (1) NT6Q73CA (Right routing - 10 meter cable)
15
one (1) NT6Q73DA (Right routing - 15 meter cable)
20
one (1) NT6Q73EA (Right routing - 20 meter cable)
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-30 Ordering information and system engineering rules
Procedure 8-1 (continued)
Ordering OME6110 base chassis, circuit packs, and software
Step
Action
30
Order the DS1 cable for the 16xE1/DS1 service interface:
31
32
33
If Line 8 is
Then order
15
one (1) NT6Q72QA (Left routing - 15 meter cable)
30
one (1) NT6Q72TA (Left routing - 30 meter cable)
Subtract “1” from the value at Line 7.
If the result is
Then
0
Go to step 33
1 or 2
Go to step 32
Order the DS1 cables for the 28xE1/DS1 circuit pack:
If Line 8 is
Then order the number obtained at step 31 times of
15
one (1) NT6Q73QA (Right routing - 15 meter cable)
30
one (1) NT6Q73TA (Right routing - 30 meter cable)
Order the required NE software.
If Line 1 is
Then Order
Rel 2.0/2.01
one (1) NT6Q81BA CD-ROM copy of Release 2.0
software for each site
Rel 2.1
one (1) NT6Q81BB CD-ROM copy of Release 2.1
software for each site
Rel 2.2
one (1) NT6Q81BC CD-ROM copy of Release 2.2
software for each site
34
Order RTU licences. Order one NT6Q80AA for each OME6110 shelf.
35
Order software certificates. Order one NT6Q84BC for each OME6110 shelf.
36
Repeat this procedure for each network element at this site. When all network
elements have been ordered for this site, continue the ordering process with
Procedure 8-2 on page 8-32.
—end—
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-31
Table 8-27
OME6110 shelf ordering worksheet
Line
Description
Value
Line 1
What software release is required (Rel 1,Rel 2.0/2.01, R2.1, or
Rel 2.2)?
Line 2
Is extended temp application required? (Yes/No)
Line 3
Is AC or DC PSU required?
Line 4
Number of E1/DS1 services
Line 5
Additional circuit packs required?
Line 6
Impedance of electrical E1/DS1 interfaces? (75 Ohm,120 Ohm,
100 Ohm, none)
Line 7
Number of 64-pin Telco connectors for E1/DS1 services on
system (1, 2, 3, none)?
Line 8
Length for the E1/DS1 cables
Line 9
Total number of E3/DS3 ports to be deployed
Line 10
Total number of 10/100BT ports to be deployed
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-32 Ordering information and system engineering rules
Procedure 8-2
Ordering cables, documentation, and services
Use this procedure to order cables, documentation, and services for the
OME6110 equipment ordered in Procedure 8-1 on page 8-23. Repeat this
procedure for each site in the OME6110 network.
Before you start
• Complete a network design, including a DCN and a synchronization plan.
• Read OME6110 network element configuration rules on page 8-2.
• Photocopy Table 8-28 on page 8-35 and Table 8-29 on page 8-36 (if required).
Procedure tasks
• Record site specific information (step 1).
• Order power cables (step 2).
• Order optical fiber patch cords (step 3).
• Order OAM and LCT cables (DCN, user interface, alarm and synchronization) (step 4).
• Order documentation (step 10).
• Order services (step 11).
Expected results
• You have a complete list of cables, documentation, and services for an OME6110 site.
• If the expected results do not occur:
— Review the network design and repeat the procedure.
— Contact your next level of support.
Action
Step
Action
Note: Use a photocopy of Table 8-28 on page 8-35 for this procedure. Line
references in this procedure refer to this table unless otherwise noted.
1
Record site specific information on Line 1 through Line 8 of Table 8-28 on
page 8-35.
2
Order DC power cables for the number of OME6110 NEs specified in Line 2.
Order the appropriate DC cable kit for the region, as specified in Line 1, and
for the length required, as shown on Line 3.
Note: Refer to Table 8-20 on page 8-17 and Bay equipping rules on page 8-3
for orderable codes and application rules.
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-33
Procedure 8-2 (continued)
Ordering cables, documentation, and services
Step
Action
3
Order fiber patchcords. Refer to Table 8-15 on page 8-14 and Table 8-16 on
page 8-15 for orderable codes and application rules.
Note: The OC-3/STM-1 optical SFP modules on the OME6110 support
duplex LC connections. Nortel Networks recommends the use of duplex
patchcords wherever allowed by the subtending equipment.
4
Order environmental alarm kits. Order one environmental alarm kit for the
number of OME6110 network elements specified on Line 4.
Note: Refer to Table 8-18 on page 8-16 for orderable part numbers and
application rules.
5
Order the number of LAN Ethernet cables specified in Line 5 to connect to the
OME6110 network elements to the DCN.
Note: A regular straight Ethernet cable (RJ-45 to HUB RJ-45) will
accommodate this connection. Refer to Table 8-17 on page 8-16 for orderable
part numbers and application rules.
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-34 Ordering information and system engineering rules
Procedure 8-2 (continued)
Ordering cables, documentation, and services
Step
Action
6
Determine the next step:
7
If Line 6 is
Then go to
Yes
step 7
No
step 8
Order one modem cable, NT6Q71AG, for each site.
Note: Refer to Table 8-17 on page 8-16 for orderable part numbers and
application notes.
8
9
Determine the next step:
If Line 7 is
Then go to
Yes
step 9
No
step 10
Order the synchronization cable required.
If Line 8 is
Then order
75 ohm
one (1) NT6Q71AE, Clock (BITS) Cable (inc 75 ohm
convertor)
100/120 ohm
one (1) NT6Q71AC, Clock (BITS) Cable (120 ohm)
Note: Refer to Table 8-19 on page 8-17 for orderable part numbers and
application notes.
10
Order documentation. Nortel Networks recommends that one CD-ROM be
ordered for each site. Alternatively, a paper library is available.
Note: Refer to Table 8-24 on page 8-20 for orderable codes and application
notes.
11
Staging services are available to simplify installation of OME6110 equipment.
Note: Refer to Engineering and support services on page 8-19 for a
description of this service.
Note: Nortel Networks offers a selection of services to help you plan, deploy,
operate, and maintain your optical networks. For more information about
these services, contact your Nortel Networks representative or visit
www.nortel.com/services.
12
Repeat this procedure for the next site in the network deployment, until all
sites have been completed.
—end—
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-35
Table 8-28
Worksheet for ordering cables, documentation and services for OME6110 network elements
Line
Description
Value
Line 1
Region of deployment for OME6110 shelves (North America or
other)?
Line 2
Total number of OME6110 shelves using DC PSUs at this site?
Line 3
Length required for the DC power cables (3M or 10M)?
Line 4
Total number of OME6110 shelves requiring environmental alarm
cables?
Line 5
Total number of OME6110 shelves connected to the DCN directly
via Ethernet at this site?
Line 6
Is a remote access dial-up modem connection required at this
site?
Line 7
Are external synchronization interfaces required at this site?
Line 8
Are 75 ohm or 100/120 ohm interfaces required for ESI connector
at this site?
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-36 Ordering information and system engineering rules
Table 8-29
RoHS codes and ordering summary
Description
Code
RoHS Code Quantity
OME6110 base chassis and components
• OME6110 System Kits
— OME6110 R2.0 DC System; Chassis, PSU, Fan & Filler
NT6Q50AB NT6Q50ABE5
— OME6110 R2.0 DC System Ext Temp; Chassis, PSU, Fan & Filler NT6Q50BA NT6Q50BAE5
— OME6110 R2.0 AC System; Chassis, PSU, Fan & Filler
NT6Q51AA NT6Q51AAE5
— OME6110 R2.1 DC System; Chassis, PSU, Fan & Filler
NT6Q50AC NT6Q50ACE5
— OME6110 R2.1 DC System Ext Temp; Chassis, PSU, Fan & Filler NT6Q50BC NT6Q50BCE5
— OME6110 R2.1 AC System; Chassis, PSU, Fan & Filler
NT6Q51AC NT6Q51ACE5
— OME6110 R2.2 DC System; Chassis, PSU, Fan Filler & Filler
NT6Q50ADE5
— OME6110 R2.2 DC System Ext Temp; Chassis, PSU, Fan & Filler
NT6Q50BDE5
— OME6110 R2.2 AC System; Chassis, PSU, Fan Filler & Filler
NT6Q51ADE5
• OME6110 Power Supply Units
— OME6110 DC PSU 35W Dual-feed Rev2
NT6Q30AB NT6Q30ABE5
— OME6110 DC PSU 35W Dual-feed Rev2 Ext Temp
NT6Q30BB NT6Q30BBE5
— OME6110 AC Power Supply Unit 50W
NT6Q31AA NT6Q31AAE5
• OME6110 Filler and Fan modules
— Filler Panel Circuit Pack slot
NT6Q70AA NT6Q70AAE6
— OME6110 Fan Tray with Filter
NT6Q32AA NT6Q32AAE5
— OME6110 Fan Tray with Filter Ext Temp
NT6Q32BA NT6Q32BAE5
OME6110 shelf assembly kit
• OME6110 Assy Kit - Cable bracket, 21”/23” flange, rack mounting
screws, cage nuts
NT6Q70BA NT6Q70BAE6
Interface circuit packs
• E1/DS1 circuit packs
— 28xE1/DS1 Circuit Pack
NT6Q10AA NT6Q10AAE5
— 28xE1/DS1 Circuit Pack Ext Temp
NT6Q10BA NT6Q10BAE5
• E3/DS3 circuit packs
— 3xE3/DS3 Circuit Pack
NT6Q12AA NT6Q12AAE5
— 3xE3/DS3 Circuit Pack Ext Temp
NT6Q12BA NT6Q12BAE5
• 10/100BT circuit packs
— 8x10/100BT L1 Circuit Pack Rev2
NT6Q13AB NT6Q13ABE5
— 8x10/100BT L1 Circuit Pack Ext Temp
NT6Q13BA NT6Q13BAE5
• 10/100BT circuit packs
— 8x10/100BT L1 Circuit Pack Rev2
NT6Q17BAE5
• STM-1/OC-3 circuit pack
— 2x155M Circuit Pack Rev2
NT6Q17ABE5
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-37
Table 8-29 (continued)
RoHS codes and ordering summary
Description
Code
RoHS Code Quantity
Pluggable modules
• STM-1/OC-3 SFPs
— OC-3/STM-1SR-0 (multimode) 1310 nm enhanced SFP module
(Ext Temp)
NTTP02AD NTTP02AD
— OC-3/STM-1 IR1/S1.1 1310 nm XCT enhanced SFP module (Ext NTTP02CD NTTP02CD
Temp)
— OC-3/STM-1 LR1/L1.1 1310 nm XCT enhanced SFP module (Ext NTTP02ED NTTP02ED
Temp)
— OC-3/STM-1 LR2/L1.2 1550 nm XCT enhanced SFP module (Ext NTTP02FD NTTP02FD
Temp)
— OC-3/STM-1 LR2/L1.2 1550 nm XCT enhanced SFP module
NTTP02FF NTTP02FF
• OC-3/12/STM-1/4 SFPs
— OC-3/12/STM-1/4 IR1/S1.1_S4.1 1310 nm XCT enhanced SFP
module
NTTP04CF NTTP04CF
• STM-1e SFPs
— STM-1e enhanced SFP module
NTTP60AE NTTP60AE
• 100Base SFPs
— 100-Base-BX10-U bidirectional-upstream, 1310 nm Tx, 10 km
SFP module
NTTP09BD NTTP09BD
— 100-Base-BX10-U bidirectional-downstream, 1490 nm Tx, 10 km
SFP module
NTTP10BD NTTP10BD
• OC-48/STM-16 SFPs
— OC-48/STM-16 CWDM 1471 nm SFP module
NTK590LH NTK590LH
— OC-48/STM-16 CWDM 1491 nm SFP module
NTK590MH NTK590MH
— OC-48/STM-16 CWDM 1511 nm SFP module
NTK590NH NTK590NH
— OC-48/STM-16 CWDM 1531 nm SFP module
NTK590PH NTK590PH
— OC-48/STM-16 CWDM 1551 nm SFP module
NTK590QH NTK590QH
— OC-48/STM-16 CWDM 1571 nm SFP module
NTK590RH NTK590RH
— OC-48/STM-16 CWDM 1591 nm SFP module
NTK590SH NTK590SH
— OC-48/STM-16 CWDM 1611 nm SFP module
NTK590TH NTK590TH
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-38 Ordering information and system engineering rules
Table 8-29 (continued)
RoHS codes and ordering summary
Description
Code
RoHS Code Quantity
Electrical interface hardware
• E1 interface conversion hardware
— 75 ohm BNC Term Panel, 16 channel
NT6Q71EA NT6Q71EAE5
— Telco to Telco 1M Cable - Left Routing
NT6Q74AA NT6Q74AAE6
— Telco to Telco 5M Cable - Left Routing
NT6Q74CA NT6Q74CAE6
— Telco to Telco 1M Cable - Right Routing
NT6Q75AA NT6Q75AAE6
— Telco to Telco 5M Cable - Right Routing
NT6Q75CA NT6Q75CAE6
• E1 cable assemblies
— 120Ohm Telco 5M Cable - Left Routing
NT6Q72BA NT6Q72BAE6
— 120Ohm Telco 10M Cable - Left Routing
NT6Q72CA NT6Q72CAE6
— 120Ohm Telco 15M Cable - Left Routing
NT6Q72DA NT6Q72DAE6
— 120Ohm Telco 20M Cable - Left Routing
NT6Q72EA NT6Q72EAE6
— 120Ohm Telco 5M Cable - Right Routing
NT6Q73BA NT6Q73BAE6
— 120Ohm Telco 10M Cable - Right Routing
NT6Q73CA NT6Q73CAE6
— 120Ohm Telco 15M Cable - Right Routing
NT6Q73DA NT6Q73DAE6
— 120Ohm Telco 20M Cable - Right Routing
NT6Q73EA NT6Q73EAE6
• DS1 cable assemblies
— 100Ohm Telco 15M Cable - Left Routing
NT6Q72QA -
— 100Ohm Telco 30M Cable - Left Routing
NT6Q72TA -
— 100Ohm Telco 15M Cable - Right Routing
NT6Q73QA -
— 100Ohm Telco 30M Cable - Right Routing
NT6Q73TA -
• E3/DS3 cable assemblies
— BNC Connector (735A)
A0609866
— DS3 735A Coaxial Cable - 10M BNC
NT7E43BB NT7E43BBE6
— DS3 735A Coaxial Cable - 30M BNC
NT7E43BD NT7E43BDE6
— DS3 735A Coaxial Cable - 60M BNC
NT7E43BG NT7E43BGE6
A0609866
Software/licences
• OME6110 R2.2 CD-ROM
NT6Q81BC N/A
• Right to use licences
— OME6110 R2.1 SW Certificate 1/NE
NT6Q84BC N/A
— OME6110 Base SW RTU 1/NE
NT6Q80AA N/A
Engineering and support services
• Hot staging for OME6110
NTYY99CJ N/A
Documentation
• OME6110 R2.2 NTP (Paper)
NT6Q65AD N/A
• OME6110 R2.2 NTP (CD-ROM)
NT6Q64AD N/A
• OME6110 R2.2 Planning Guide
NT6Q92AD N/A
• Change application procedures
— OME6110 Upgrade CAP from Release 2.1 to Release 2.2
NT6Q93AD N/A
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-39
Table 8-29 (continued)
RoHS codes and ordering summary
Description
Code
RoHS Code Quantity
Cables
• Optical fiber patch cords (add length and code as appropriate, see
Table 8-16 on page 8-15 for details).
E6 codes are RoHS compliant, L6 codes are Low Smoke Zero Halogen
(LSZH) and RoHS compliant.
— Optical patchcords, LC-LC, SM, Simplex
NTTC50Ax NTTC50AxE6
NTTC50AxL6
— Optical patchcords, LC-SC, SM, Simplex
NTTC50Bx NTTC50BxE6
NTTC50BxL6
— Optical patchcords, LC-FC, SM, Simplex
NTTC50Cx NTTC50CxE6
NTTC50CxL6
— Optical patchcords, LC-ST, SM, Simplex
NTTC50Dx NTTC50DxE6
NTTC50DxL6
— Optical patchcords, LC-LC, SM, Duplex
NTTC53Ax NTTC53AxE6
NTTC53AxL6
— Optical patchcords, LC-SC, SM, Duplex
NTTC53Bx NTTC53BxE6
NTTC53BxL6
— Optical patchcords, LC-FC, SM, Duplex
NTTC53Cx NTTC53CxE6
NTTC53CxL6
— Optical patchcords, LC-ST, SM, Duplex
NTTC53Dx NTTC53DxE6
NTTC53DxL6
— Optical patchcords, LC-LC, MM 50 micron, Simplex
NTTC56Ax NTTC56AxE6
NTTC56AxL6
— Optical patchcords, LC-SC, MM 50 micron, Simplex
NTTC56Bx NTTC56BxE6
NTTC56BxL6
— Optical patchcords, LC-FC, MM 50 micron, Simplex
NTTC56Cx NTTC56CxE6
NTTC56CxL6
— Optical patchcords, LC-ST, MM 50 micron, Simplex
NTTC56Dx NTTC56DxE6
NTTC56DxL6
— Optical patchcords, LC-LC, MM 50 micron, Duplex
NTTC59Ax NTTC59AxE6
NTTC59AxL6
— Optical patchcords, LC-SC, MM 50 micron, Duplex
NTTC59Bx NTTC59BxE6
NTTC59BxL6
— Optical patchcords, LC-FC, MM 50 micron, Duplex
NTTC59Cx NTTC59CxE6
NTTC59CxL6
— Optical patchcords, LC-ST, MM 50 micron, Duplex
NTTC59Dx NTTC59DxE6
NTTC59DxL6\
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-40 Ordering information and system engineering rules
Table 8-29 (continued)
RoHS codes and ordering summary
Description
Code
RoHS Code Quantity
• DCN and craft access cables
— F1 cable
NT6Q71AF NT6Q71AFE6
— Modem cable
NT6Q71AG NT6Q71AGE6
— Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, 5 m
NTTC09CA NTTC09CAE6
E6
NTTC09CAE6
NTTC09CC NTTC09CAE6
E6
NTTC09CAE6
NTTC09CE
NTTC09CAE6
E6
— Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, 15 m
— Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, 30 m
— Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, 5 m
— Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, 15 m
— Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, 30 m
NTTC09DA NTTC09CAE6
E6
NTTC09DC
E6
NTTC09DE
E6
• Alarm and telemetry cables
— OME6110 - Environmental alarm cable kit
NT6Q59AB NT6Q59ABE6
• Synchronization cables
— Clock (BITS) Cable (120 ohm)
NT6Q71AC NT6Q71ACE6
— Clock (BITS) Cable (inc 75 ohm convertor)
NT6Q71AE NT6Q71AEE5
• Power and earthing cable assemblies
— OME6110 - DC Cable Kit - 3M
NT6Q59AA NT6Q59AAE6
— OME6110 - DC Cable Kit - 10M
NT6Q59BA NT6Q59BAE6
— OME6110 - DC Cable Kit - 3M North America
NT6Q59M
A
— OME6110 - DC Cable Kit - 10M North America
— Earthing Cable
— Nortel Euro/C13 2 meter AC cord
— Nortel Danish/C13 2 meter AC cord
— Nortel Israel/C13 2 meter AC cord
— Nortel Italian/C13 2 meter AC cord
— Nortel Swiss/C13 2 meter AC cord
— Nortel U.K./C13 2 meter AC cord
— Nortel North America/C13 2.5 meter AC cord
-
NT6Q59NA NT6Q71AAE6
NT6Q71AA NTK955CBE6
NTK955CB NTK955CCE6
NTK955CC NTK955CEE6
NTK955CE NTK955CFE6
NTK955CF NTK955CGE6
NTK955CG NTK955CHE6
NTK955CH NTK955CKE6
NTK955CK
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Ordering information and system engineering rules 8-41
Table 8-29 (continued)
RoHS codes and ordering summary
Description
Code
RoHS Code Quantity
• STM-1e cable assemblies and connectors
— Cable assembly, co-axial, DIN 1.0/2.3, RG179DT cable, single, 10 NTTC04AA NTTC04AAE6
m
— Cable assembly, co-axial, DIN 1.0/2.3, RG179DT cable, single, 20 NTTC04AB NTTC04ABE6
m
— Cable assembly, co-axial, DIN 1.0/2.3, RG179DT cable, single, 30 NTTC04AC NTTC04ACE6
m
— Cable assembly, co-axial, DIN 1.0/2.3, RG179DT cable, single, 40 NTTC04AD NTTC04ADE6
m
— Cable assembly, co-axial, DIN 1.0/2.3, RG179DT cable, single, 50 NTTC04AE NTTC04AEE6
m
— Cable assembly, co-axial, DIN 1.0/2.3, RG179DT cable, single, 60 NTTC04AF NTTC04AFE6
m
— Connector coax, BNC 75 ohm, male, straight plug for use with
RG179DT cable
A0360953
N0104109
— Connector coax, BNC 75 ohm, female straight, bulkhead, jack,
crimp/crimp, for use with RG179DT cable
A0678277
N0104115
— Connector coax, BT43 75 ohm, male, straight, bulkhead DDF,
crimp/crimp, for use with RG179DT cable
A0620780
N0104112
— Connector coax, HDC43 bulkhead plug (male) crimp/crimp,
RG179/U, DDF mount, Single PC. body
N0032563
N0107154
— Connector coax, DIN 1.0/2.3 mm, straight cable plug (male)
crimp/crimp 75 ohm RG179/U
N0032582
N0104121
• Ethernet service cable assemblies (Shielded Twisted Pair -STP)
— Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, 5 m
— Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, 15 m
— Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, 30 m
— Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, 5 m
— Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, 15 m
— Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, 30 m
NTTC09CA NTTC09CAE6
E6
NTTC09CCE6
NTTC09CC NTTC09CEE6
E6
NTTC09DAE6
NTTC09CE
NTTC09DCE6
E6
NTTC09DA NTTC09DEE6
E6
NTTC09DC
E6
NTTC09DE
E6
Planning Guide NT6Q92AD Standard Rel 2.2 Issue 1 May 2007
8-42 Ordering information and system engineering rules
Optical Multiservice Edge 6110 NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
9-1
Technical assistance
9-
This chapter includes information on how to contact Nortel Networks for
technical assistance.
Table 9-1
Topics in this chapter
Technical assistance topics
Page
Technical support and information
9-2
Nortel Networks web site
9-3
CE mark
9-3
Field return information
9-4
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
9-2 Technical assistance
Technical support and information
For technical support and information from Nortel Networks, refer to the
following table.
Technical Assistance Service
For service-affecting problems:
For 24-hour emergency recovery or software upgrade
support, that is, for:
North America:
1-800-4NORTEL (1-800-466-7835)
• restoration of service for equipment that has been carrying
traffic and is out of service
International:
001-919-992-8300
• issues that prevent traffic protection switching
• issues that prevent completion of software upgrades
For non-service-affecting problems:
For 24-hour support on issues requiring immediate support
or for 14-hour support (8 a.m. to 10 p.m. EST) on upgrade
notification and non-urgent issues.
North America:
1-800-4NORTEL (1-800-466-7835)
Note: You require an express routing
code (ERC). To determine the ERC, see
our corporate Web site at
www.nortel.com. Click on the Express
Routing Codes link.
International:
Varies according to country. For a list of
telephone numbers, see our corporate
Web site at www.nortel.com. Click on
the Contact Us link.
Global software upgrade support:
North America:
1-800-4NORTEL (1-800-466-7835)
International:
Varies according to country. For a list of
telephone numbers, see our corporate
Web site at www.nortel.com. Click on
the Contact Us link.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical assistance 9-3
Nortel Networks web site
You can also contact us through the Nortel Networks web site at:
www.nortel.com. Select the link Support.
CE mark
The following is an example of the Conformité Européenne (CE) mark
indicating that all electromagnetic compatibility (EMC) and other
electrotechnical requirements are met and that the product complies with all
applicable standards.
This product/product family complies with the provisions of
the Low Voltage Directive 73/23/EEC, and with the essential
protection requirements of the EMC Directive 89/336/EEC as
amended by 92/31/EEC, when it is properly installed and
maintained and when it is used for the purposes for which it is
intended.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
9-4 Technical assistance
Field return information
Complete the following Field Return Information Form and include the form
when returning any damaged circuit packs to the factory. Insert the completed
form into an anti-static bag. Attach this bag to the failed circuit pack.
Note: Some of the information that you must provide (such as alarms
raised) require you to log in to the network element.
Field Return Information Form
Customer Identification
Customer name:
Site location:
Originator name:
Originator phone number:
Originator pager number:
Project manager name:
Project manager phone number:
Circuit pack description
PEC:
Release:
Serial number:
NE physical slot number (shelf # and slot #):
Network element
NE name:
NE number:
NE type:
NE configuration:
NE application load release:
Failure symptoms
List of raised alarms related to the failed circuit pack:
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Technical assistance 9-5
Field Return Information Form (continued)
Failure data
LED status:
Optical input power at the receive interface:
Optical output power at the transmit interface:
__ dBm
__ dBm
Failure time
Troubleshooting data
Visual inspection of the backplane pins:
Tested against other positions:
Slot #:___ Results:___
Slot #:___ Results:___
Slot #:___ Results:___
Slot #:___ Results:___
Actions performed to clear problems:
Internal pigtail cleaned:
External pigtail cleaned:
Special instructions:
General comments:
Tracking information
Change request (CR) number:
Emergency recovery (ER) contact name:
Emergency recovery (ER) contact telephone number:
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
9-6 Technical assistance
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-1
Appendix A: Data communications
planning
10-
This chapter provides an overview of Optical Multiservice Edge 6110
(OME6110) network data communications. Table 10-1 lists the topics covered
in this chapter.
Table 10-1
Topics in this chapter
Topic
Page
Introduction
10-2
OAM&P Ports
10-3
Network Interface
10-4
STM-1/OC-3 Data Communication Channel
10-6
IP communication
10-11
OSI data communications
10-16
Application protocols
10-21
Diagnostic commands
10-22
Firewall considerations
10-22
Engineering guidelines
10-23
Supported DCN design examples
10-25
IP networks, addressing, and masks
10-92
IP routing protocols
10-95
This Appendix provides information on typical DCN configurations/models
and provides some examples and guidance on provisioning different
configurations. For general information about the OME6110 data
communication architecture and features, refer to OAM&P description on
page 6-1.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-2 Appendix A: Data communications planning
The Data Communications Network Planning Guide, NTR710AM provides
information on DCN planning for some OSI-based Nortel Networks products.
This guide includes general information on OSI data communications and
addressing and can be used as a reference for OSI data communications
information.
Introduction
OME6110 is an IP managed optical network element (NE), which has the
capabilities to communicate through both TCP/IP Internet Protocol (IP) and
OSI Connectionless Network Protocol (CLNP) based networks.
Connectivity of the OME6110 network element to its management system can
be achieved through:
• the LCT port (10/100Base-T, RJ-45) located along the OAM port
interfaces on the base chassis.
• the M1/F1 port via modem.
• SDH/SONET Regenerator Section (RS)/Section 192 kbps DCC (D1-D3
bytes) of the optical line interfaces.
• SDH/SONET Regenerator Section (RS)/Section 64 kbps user channel (F1
byte) of the optical line interfaces.
• SDH/SONET Multiplexor Section (MS)/Line 576 kbps DCC (D4-D12
bytes) of the optical line interfaces.
• SDH/SONET Path DCC (F2, F3, or F2-F3 bytes) of the optical line
interfaces.
• SDH VC12 management channel of the optical line interfaces.
• SDH E1 management channel of the base chassis or circuit pack.
Depending on the network topology, the OME6110 can be configured to
operate as either:
• an IP router: IP communications are routed using static and/or dynamic
routing protocol to subtended NEs
• an IP host: IP communications are not forwarded to other NEs with static
routing entries providing default routing to the connected IP router.
The OME6110 can use integrated IS-IS (iIS-IS) protocol with auto-tunneling
in order to establish communications in OSI-based SONET/SDH networks.
OME6110 supports Generic Routing Encapsulation (GRE) which can tunnel
IP management communications into OSI Protocol Data Units (PDU). The
GRE tunnel can be terminated on an OME6110, other GRE capable NE, or a
dedicated router to extract the IP management communications before being
forwarded to the management system.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-3
OME6100 supports transparent DCC capabilities which allows the NE to
pass-through DCC bytes (E1, F1, D1-D3, E2, D4-D12) used by other network
elements. This functionality provides additional integration capabilities into an
existing network without affecting the current DCN configuration.
Remote access to an OME6110 NE can be achieved through asynchronous
RS-232 modem connection through the serial M1/F1 communication port.
OAM&P Ports
This section describes the ports which can be used to perform OAM&P
operations on an OME6110 network element.
M1/F1 port
OME6110 shelf supports a serial communication port which can operate under
the following applications:
•
•
Point-to-point (PPP) - asynchronous RS232 communication with external
modem.
User Data Channel (UDC) - asynchronous 9600 kbps clear channel using
the F1 byte of the regenerator section/section overhead.
LCT port (LAN-1-5)
The OME6110 shelf supports a 10/100BT Ethernet port on the base chassis to
interface with the Local Craft Terminal (LCT) or external DCN.
It auto-senses the operating speed (10 Mbit/s or 100 Mbit/s), but operates only
at half-duplex mode.
The LCT port is a Medium Dependent Interface (MDI), which requires a
straight-through cable for connection to a hub or switch, and a crossover cable
to a LCT PC or to a DCN router.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-4 Appendix A: Data communications planning
The provisionable IP subnet mask is in prefix notation which indicates the
number of binary 1s in the mask, preceded by the “/”.
Table 10-2
Subnet mask
Mask
Dotted equivalent
/24
255.255.255.0
/25
255.255.255.128
/26
255.255.255.192
/27
255.255.255.224
/28
255.255.255.240
/29
255.255.255.248
/30
255.255.255.252
/32
255.255.255.255
Network Interface
The network interfaces of the OME6110 network element are logical
representation of the management channels for OAM&P. Each network
element has a minimum of one network interface (eth0) for the LCT port. A
maximum of two DCC in-band channels can be provisioned per network
element. Besides the eth0 network interface, two additional DCC network
interfaces can be a combination of the E1/VC12 management channel (mgmt1
or mgmt2) and the embedded communication channel of the optical interfaces
(ecc_3_1 or ecc_3_2). Static and dynamic (Auto) GRE tunnels are also
represented as network interface entities.
The eth0 network interface is created by default and can not be deleted.
The mgmt1 and mgmt2 network interfaces are created when the E1/VC12
management channels are provisioned via the DCN/Management Channel
application, and they are deleted when the E1/VC12 management channels are
unprovisioned from the application. Only IP/PPP is supported over the
E1/VC12 management channels (and it supports only OSPF as routing
protocols).
The ecc_3_1 and ecc_3_2 network interfaces are created by selecting the
appropriate RS/Section or MS/Line overhead bytes (F1, F2, F3, F2F3, D1-D3,
or D4-D12) for the embedded communication channel in the Provision ECC
page. These ECC network interfaces are deleted from the network interface
page. Either IP/PPP or OSI/LAPD is supported over the embedded
communication channels.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-5
The static and dynamic GRE tunnels are also created as network interfaces.
When iIS-IS is enabled at the nodal level on the network element, the Auto
GRE tunnel (AGRE) network interface is automatically created and will be
deleted upon disabling the iIS-IS nodal parameter. Upon enabling nodal iIS-IS
on the NE, a static GRE tunnel (SGRE) network interface can be created by
specifying the remote manual area address, remote system ID (MAC address)
and the NSAP selector byte.
See Table 10-3 for a summary of the provisionable parameters applicable to
each type of network interfaces. Refer to Table 10-4 or more information on
the parameters supported for OSPF and iISIS routing protocols.
Table 10-3
Network interface provisionable parameters summary
Network
interface
Admin
Status
Layer 2 parameters
eth0
(LCT port)
<Up/Down> • Layer 2 Protocol=MAC
(see Note 1)
Layer 3
parameters
OSPF
iISIS
support support
• Layer3
Protocol=IP
Yes
No
Yes
No
Yes
Yes
(see
Note 2)
(see
Note 2)
No
Yes
• MTU=<1518>
bytes
mgmt1
mgmt2
(E1/VC12)
<Up/Down> • Layer2 Protocol=
<Standard PPP, RFC1661 /
PPP, HDLC framing>
• Magic Number=
<Disable/Enable>
ecc_3_1
<Up/Down> • Layer2 Protocol=
ecc_3_2
<Standard PPP, RFC1661 /
(STM-1 /
PPP, HDLC framing>
OC-3 ports)
• Magic Number=
<Disable/Enable>
• Layer2 Protocol=<Datalink
LAPD>
• Layer3
Protocol=IP
• MTU=<1518>
bytes
• Layer3
Protocol=IP
• MTU=<1518>
bytes
• Layer3
Protocol=OSI
• MTU=<512> bytes
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-6 Appendix A: Data communications planning
Table 10-3
Network interface provisionable parameters summary
Network
interface
Admin
Status
Layer 2 parameters
Layer 3
parameters
OSPF
iISIS
support support
AGRE
<Up>
• Layer2 Protocol=GRE
• Layer3
Protocol=IP
No
No
Yes
No
(see Note 3)
• MTU=446 bytes
SGRE-1
<Up/Down> • Layer2 Protocol=GRE
(see Note 4)
• Remote MAA=<490000>
• Layer3
Protocol=IP
• Remote SID=<000000000000> • MTU=<446> bytes
• NSAP Selector Byte=<2F>
Note 1: It is recommended to leave the Eth0 network interface port in Admin Up state.
Note 2: OSPF and iISIS can not be simultaneously for a network interface.
Note 3: The Auto GRE tunnel is automatically created when iISIS is enabled at the nodal level on the
NE. The AGRE network interface parameters are not user-provisionable.
Note 4: The Static GRE tunnel can only be created if iISIS is enabled at the nodal level.
Table 10-4
Dynamic routing protocol parameters
Routing
Protocol
Status
Provisionable parameters
Network Interface
support
OSPF
<Enable /
Disable>
• Hello Interval=<10>
• eth0
• Router Dead Interval=<40>
• mgmt1, mgmt2
• OSPF Authentication Mode=
<Disable authentication /
Simple password>
• ecc_3_1. ecc_3_2
• SGRE-1
• Password/Key=<>
iISIS
<Enable /
(see Note 1) Disable>
• L1 Default Metric=<4>
• ecc_3_1. ecc_3_2
• L2 Default Metric =<4>
• L2 Routing Only=<Disable /
Enable>
Note 1: In this release, the L2 Default Metric and L2 Routing Only parameters are not
supported for iISIS routing protocol.
For more information on the detail procedures, refer to Provisioning and
Protection Switching Procedures, 323-1853-310.
STM-1/OC-3 Data Communication Channel
Each line optical port can support communications on the selected regenerator
section (RS)/section or the multiplexer section (MS)/line overhead byte(s).
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-7
Each DCC interface supports High-Level Data Link Control (HDLC),
Point-to-Point Protocol (PPP), or Link Access Procedure D-Channel (LAPD).
HDLC and PPP are IP-based datalink layer and LAPD is an OSI-based
datalink layer. PPP is the default datalink layer.
The OME6110 uses an IP-based data communications infrastructure for
network element management and interworking with IP-managed network
elements. OME6110 also supports Open Systems Interconnection (OSI) based
infrastructures for interoperability with OSI-managed network elements.
Data link layer protocols
The following are the supported data link layer 2 protocols used with
OME6110 network element through the DCC channels:
LAPD
Link Access Procedure D-Channel (LAPD) is a data link layer 2 protocol used
by OME6110 for interworking with OSI networks over DCC.
The OME6110 network element supports LAPD layer 2 protocol on all
STM-n/OC-n ports terminating the layer 1 channel using the over-head bytes.
The OME6110 network supports at least as many LAPD instances as the
number of STM-n/OC-n ports in the OME6110 network element.
Note 1: The OME6110 network element can support presentation of either
LAPD or PPP to the layer 1 interface. Each layer 1 interface can only
terminate either LAPD or PPP protocol, but not both simultaneously.
Note 2: It is possible to configure layer 2 protocol for each layer 1
interface independently, on a per layer 1 interface basis.
LAPD detects and reports to higher layers the up or down status of the physical
interface. An alarm to indicate link failure shall be supported.
Standard PPP, RFC1661
Point-to-point protocol (PPP) is a data link layer 2 protocol used to pass data
between two systems on behalf of the network layer 3 protocol such as TCP/IP
Internet Protocol (IP). OME6110 uses the standard PPP as per RFC1661.
Note 1: As of Release 2.1, PPP uses IP Control Protocol (IPCP) over OSI
Network Layer Control Protocol (OSINLCP) to pass data between layer 2
and layer 3 protocols. Recommended for standard implementation.
Note 2: Use this option for interworking with any Nortel equipment which
supports IP/PPP over DCC channel.
Note 3: Operates in an un-numbered IP mode, using the Router ID (refer
to as circuitless IP for Nortel routers and loopback address for Cisco
routers).
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-8 Appendix A: Data communications planning
Note 4: The DCN interface that is configured to operate on IP over
Standard PPP does not support configuration of the interface IP address
through IP Control Protocol (IP CP) negotiation. The OME6110 network
element while sending IPCP IP Address Configure-Ack packet (which is
sent in response to the IPCP IP Address Configure-Req packet) will send
the Router-ID as its IP address.
PPP, HDLC framing
High-Level Data Link Control (HDLC) is a data link layer 2 protocol used to
pass data between two systems on behalf of the network layer 3 protocol such
as TCP/IP Internet Protocol (IP).
Note 1: The OME6110 uses the proprietary cHDLC encapsulation and
will not interwork with any Nortel equipment.
Note 2: Operates in an un-numbered IP mode, using the Router ID (refer
to as circuitless IP for Nortel routers and loopback address for Cisco
routers).
Note 3: Use for interworking with other cHDLC DCC network element.
STM-1/OC-3 DCC operation mode
The DCC operation depends on the implemented protection scheme.
1+1 MSP/APS system
The route diversity is provisionable and can either be Route-Diversity-Enabled
(ON) or Route-Diversity-Disabled (OFF) while configuring 1+1 MSP/APS.
On the OME6110 network element, the route diversity is disabled by default.
In the Route-Diversity-Disabled option, the DCN operation bridges transmit
and select receiver based on the MSP/APS state machine. The layer 2 and
above are presented with only one network interface:
• In the receiver direction, only one of the two layer 1 interfaces (from
among the configured working and configured protected belonging to the
MSP/APS pair) will be presented to the layer 2 termination protocol. The
presented interface shall follow the active path as defined by the MSP/APS
state machine.
• In the transmit direction, both layer 1 interfaces (configured working and
configured protected port of the MSP/APS pair) transmit the same
information sent from the layer 2 protocol (bridge).
Note: In the Route-Diversity-Disabled option, no DCN configuration is
allowed on the configured protected port of the MSP/APS pair.
“Route diversity disabled” mode uses a single DCC channel which is switched
with the traffic for management, which is unlike the “route diversity enabled”
mode where each interface of the 1+1 MSP/APS link has a separate DCC
channel that is not switched with the MSP/APS protected traffic.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-9
In the Route-Diversity-Enabled option, the DCN operation on the configured
working and configured protected ports belonging to MSP/APS are treated
independently. The transmit and receive data of the two layer 1 interfaces
(belonging to the configured working and configured protected ports
belonging of MSP/APS pair) is independently presented to the layer 2
termination protocol as two independent interfaces. The layer 2 and above are
presented with two independent network interfaces.
Note: In the Route-Diversity-Enabled option, DCN configuration is
allowed on the configured protected port of the MSP/APS pair.
If OME6110 NE is interworking with another network element (e.g
OM3000/4000) which has its interface set to bi-directional MSP/APS
switching mode, route diversity should be provisioned to the same at the
OME6110 NE and the far-end NE. Otherwise, DCC alarms may be raised on
the non-OME6110 NE which can be ignored or disabled.
When an OME6110 NE, which has its DCC route diversity disabled, is
interworking in a 1+1 MSP/APS uni-directional switching mode with other
NE (e.g. OM3000/4000) with route diversity enabled, a single fibre break in
the Rx direction of the non-OME6110 NE in working path can result in lost of
communication between the two NEs because the OME6110 NE can still
receive traffic on the working interface which the transmit has failed, therefore
bi-directional LAPD adjacency can not be established on neither the working
path nor the protection path, and hence loss of communication. There will no
loss of communication if both fibres (Tx and Rx) on the working path fail at
the same time so that bi-directional LAPD adjacency can be establish on the
protection path.
Bi-directional switching mode is the recommended protection scheme used for
1+1 MSP/APS in order to guarantee full data communication between
interworking network elements.
SNCP/UPSR or unprotected system
In this configuration, each STM-1/OC-3 link is considered as an individual
port, allowing the DCC to be configured independently. The following are the
supported combinations:
•
•
•
•
•
Both STM-1/OC-3 ports with DCC disabled
Both STM-1/OC-3 ports with PPP/IP or cHDLC/IP
One STM-1/OC-3 port with PPP/IP or cHDLC/IP and the other
STM-1/OC-3 port with LAPD/CLNP (OSI)
Single STM-1/OC-3 port with PPP/IP or cHDLC/IP
Single STM-1/OC-3 port with LAPD/CLNP (OSI)
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-10 Appendix A: Data communications planning
Overhead transparency
OME6110 supports overhead bytes transparency via overhead tunnel
provisioning, by specifying the source and destination optical port, and
selecting the passthrough RS/Section or MS/Line overhead byte(s). This
feature provides the following capabilities:
•
•
•
Designated byte(s) from the interworking or subtending networking
elements are passed transparently through the OME6110 network
elements.
Allows interoperability with other vendors’ equipment that do not support
a standard-based OSI communication stack.
Using transparent DCC to forward OSI packets.
The following are the overhead bytes which are allowed to pass transparently:
•
Regenerator Section/Section overhead:
— E1: 64 kbps orderwire channels
— F1: 64 kbps user channel
— D1-D3: 192 kbps OA&M data
•
Multiplexer Section/Line overhead
— E2: 64 kbps orderwire channels
— D4-D12: 576 kbps OA&M data
STM-1/OC-3 DCC implementation rules
You must observe the following rules when you implement the DCC:
• Only one section/regenerator section (RS) or line/multiplex section (MS)
DCC can be enabled per optical port.
• Each DCC can support HDLC, PPP or LAPD. The default is PPP.
•
•
— When using DCC to connect to an OME6110 (or any network element
that supports IP based DCC datalink layer), select PPP as the protocol.
— When using DCC to connect to an OSI-based DCC datalink layer,
select LAPD as the protocol.
Set the LAPD IP MTU size to 446 when interworking with Optical Cross
Connect DX/ HDXc/ HDX, Optical Metro 3000, and Optical Multiservice
Edge 6500. The user has to manually configure the connected
SONET/SDH interfaces to 512 bytes for the LAPD MTU. The OME6110
LAPD MTU is set to 512 by default.
Set the LAPD IP MTU size to 446 when interworking with Optical Metro
4000 and TN-1C family of products which has a fixed LAPD MTU of 512
bytes. The OME6110 LAPD MTU is set to 512 by default.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-11
•
On a DCC interface over SDH/SONET overhead bytes, both OSPF and
iISIS routing protocols cannot be enabled simultaneously.
IP communication
TCP/IP Internet Protocol (IP) is a network layer protocol and the OME6110
uses IPv4. Each OME6110 shelf must have one IP address assigned to it for
management purposes. Typically, the IP address used to manage the OME6110
is the circuitless IP address. The circuitless IP is designated as Router ID.
CAUTION
Circuitless IP (Router ID) address
The circuitless IP has a non-provisionable default subnet mask
of 255.255.255.255.
The LCT (LAN-1-5) Ethernet interface can be assigned with a single IP
address and subnet mask. A gateway network element requires an IP address
on a different subnet to the Router ID for the Ethernet interface connected to
the external DCN.
Supports multiple routing protocols,
For general information on assigning IP addresses in a network, see IP
networks, addressing, and masks on page 10-92.
IP addressing implementation rules
You must observe the following rules when you implement the IP addresses:
• Each network element must be assigned with an IP address and subnet
mask for the LCT port, and an IP address for the circuitless IP (Router ID)
address.
• For a gateway network element, you must provision an IP address for the
LCT port on a different subnet to the Router ID IP address. The LCT
•
•
•
interface must be assigned an IP address in the same subnet of the external
router port connected to the LCT interface of the gateway network
element.
A node reset (warm restart) on the NE is required after changing the Router
ID or Ethernet IP address in order for the new IP addresses to take effect
Overlapping IP addresses cannot be assigned.
When assigning private IP addresses, it is recommended that the IP
addresses in the range of 10.1.1.0 to 10.4.255.255 are not used. These IP
addresses are used by the OM5000 network elements for internal data
communications so should not be used in any OME6110 network that will
contain OM5000 network elements.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-12 Appendix A: Data communications planning
•
•
•
The LCT port has a default IP address of 192.168.1.254/24 which allows a
local craft PC with an IP address configured in the same subnet as the LCT
interface to access the network element. It is recommended that the IP
addresses in the range of 192.168.1.1 to 192.168.1.255 are not used.
The last octet of the router ID and LAN-1-5 IP addresses can not be 0 or
255.
For a remotely managed NE, for example, via the DCC of the optical line
interface, the LCT port can be left as default IP address of
192.168.1.254/24 for local craft access.
Note: OSPF routing should always be disabled on the LCT port if it is
provisioned with default IP address.
Static routing
As with standard routers, the OME6110 supports configuration of static
routes.
Static route implementation rules
You must observe the following rules when you implement a static route:
•
•
•
Static routes can be provisioned on any of the network interfaces up to a
maximum of 10.
Static routes on valid PPP interfaces, such as STM-1/OC-3 ports, SGRE,
AGRE, E1 or VC12 management channels, should be provisioned with
next hop IP address 0.0.0.0.
Set the OSPF parameter to Disable and provision the static route for the
appropriate PPP network interface.
Note: The static routes can be configured in the NE for redistribution
(advertising over routing protocols over to other NEs). The redistribution
is applied to the routing protocol that is provisioned on the NE: OSPF only,
iISIS only or both simultaneously. It is not possible to redistribute a static
route only over OSPF or only over iISIS, if both routing protocols are
enabled on the network element.
Dynamic routing - OSPF
Open Shortest Path First (OSPF) Protocol is an Interior Gateway Protocol
(IGP) that distributes routing information between routers belonging to a
single autonomous system (AS). Intended for use in large networks, OSPF is
a link-state protocol which supports IP subnetting and the tagging of
externally-derived routing information.
OME6110 provides OSPF v2 routing functionalities and acts as a standard
non-backbone OSPF router, interworking with an external customer OSPF
DCN.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-13
Note: OSPF routing is always active on the OME6110 network element,
and therefore does not need to be enabled at the nodal level. It must only
be provisioned on the network interface for which it is required.
The OME6110 supports enabling and disabling of OSPF routing protocol per
IP-carrying interface, including Eth0, PPP/cHDLC DCC, and SGRE
interfaces.
For more information about OSPF, see IP routing protocols on page 10-95.
OSPF routing implementation rules
You must observe the following rules when you implement the OSPF routing:
• Default user configurable OSPF area of 0.0.0.1 for all network interfaces
for which the OSPF parameter is enabled.
•
•
Set the OSPF parameter to Enable to use dynamic routing over the
network interfaces.
When OSPF is enabled on the eth0 network interface (LCT port), the
provisioned Ethernet sub-network is advertised as part of the OSPF link
state advertisement (LSA).
• The Router ID IP address is used only in OSPF hello packets to form OSPF
adjacencies. This allows multiple different OSPF areas of 0.0.0.1 to exist
in the customer network as long as the OME6110 NEs are connected to
different Area Border Routers (ABRs). See Figure 10-1 on page 10-14.
•
•
•
•
•
It is recommended to use the Ethernet IP address as the Router ID IP
address if the NE has only direct LAN connectivity.
It is recommended to use a different Router ID IP address other than the
Ethernet IP address if the NE has DCC enabled.
When OSPF is enabled on the Ethernet port and DCC is being used to
provide OA&M, the Router ID IP address should be in a different
sub-network other than the Ethernet IP address sub-network.
Re-distribution of static route into OSPF routing table is supported. By
default, static route re-distribution is disabled.
Route redistribution between OSPF and iISIS routing protocols is not
supported.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-14 Appendix A: Data communications planning
Figure 10-1
Multiple OSPF 0.0.0.1 areas
OSPF area 0.0.0.0
OSPF area 0.0.0.1
ABR 3
OMEA
ABR 2
ABR 1
OSPF area 0.0.0.1
Legend
=
=
=
=
IP connection
OSPF routing between NEs/Router
iISIS routing between NEs
Static/Default routing
Dynamic routing - Integrated IS-IS
Integrated ISIS (iISIS) is a routing protocol based on the OSI Intra-domain
routing protocol with IP specific extensions as specified in ISO/IEC10589 and
RFC1195. iISIS allows IP and OSI to co-exist in a single routing domain,
allowing IP-only routers, OSI-only routers, and dual IP/OSI routers to be
effective in routing in a single network.
OME6110 network elements support nodal level enabling and disabling of
iISIS routing protocol. When enabled at a nodal level, it is possible to enable
iISIS routing on a per layer 2 PPP interface or on a per LAPD interface. iISIS
is able to communicate with layer 2 protocols to forward OSI-NPDU packets
over the LAPD and PPP layer 2 links.
iISIS routing protocol allows the creation of an Link State Packet (LSP)
database of all OSI only, IP only, and Dual Stack network elements within its
level 1 area. iISIS routing protocol creates IP Routing Information Base (RIB)
that contains route information for all network elements that have at least one
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-15
IP address configured and is in the same level 1 area. iISIS routing protocol
also creates CLNP forward information base (FIB) updates based on LSP
database for all reachable OSI network elements.
iISIS routing implementation rules
You must observe the following rules when you implement the iISIS routing:
•
•
•
•
•
Support provisioning of three manual area addresses:
— MAA1 default value of 490000
— MAA2, blank with 3 to 13 bytes long
— MAA3, blank with 3 to 13 bytes long
Level 1 routing is supported
Enabling and disabling of iISIS routing protocol is done on a per PPP,
LAPD based DCN interface. The default value is iISIS-Disabled.
The iISIS routing protocol will support only configuration of default
metric as the routing metric for each circuit. The range of the default metric
shall be [1 - 63] and the default value is 4.
Route redistribution between OSPF and iISIS routing protocols is not
supported.
Routing protocol configuration
OME6110 supports nodal level configuration of enabling or disabling of
Integrated Intermediate System Intermediate System (iISIS) routing protocol.
By default, iISIS routing protocol is disabled. OSPF routing protocol is always
enabled at the nodal level, but must be provisioned per network interface.
OME6110 supports enabling of iISIS at a nodal level, while OSPF is also
enabled on the NE. The routing protocols must be specified for each network
interface individually. iISIS and OSPF routing can not be simultaneously
provisioned on the same network interface.
Proxy ARP
Proxy ARP allows a gateway network element to respond to address resolution
protocol (ARP) requests for subtending network elements that are within the
same subnet as the customer DCN address range. The proxy ARP feature
removes the need for customers to provision static routes on their routers and
routing protocols (OSPF) between the gateway network elements and the
customer DCN.
Proxy ARP is only supported on the LAN interface of the OME6110 network
element. At the gateway OME6110 network element, the IP address of
neighbouring network elements can be provisioned for Proxy ARP. The GNE
will perform proxy ARP for IP addresses of neighbouring NEs that are on the
same subnet s the DCN router connected to the LAN interface.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-16 Appendix A: Data communications planning
For more information about ARP, see ARP on page 10-95.
Proxy ARP implementation rules
You must observe the following rules when you implement proxy ARP. At
gateway network elements, you must:
•
•
•
•
•
assign a subnet on the DCN router port that connects to the LAN port of
the gateway network element that is large enough to support the LAN port
and the router ID address of every network element for which the gateway
network element will proxy ARP
provision the IP addresses of the proxy ARP neighbours for which the
gateway network element will respond for
provision a maximum of 13 proxy ARP neighbours
ensure that the DCN router interfaces connected to the LAN interface will
ARP for the specified ARP neighbours
provision a static route to the DCN network. At the remote/neighbouring
NEs, static routes do not need to be provisioned to the router
OSI data communications
The Data Communications Network Planning Guide, NTR710AM provides
information on DCN planning for some OSI-based Nortel products. This guide
includes general information on OSI data communications and addressing and
can be used as a reference for OSI data communications information.
CLNP
OSI Connectionless Network Protocol (CLNP) is a network layer 3 protocol
which provides services to the upper transport layer, similar to the Internet
Protocol (IP) in the a TCP/IP environment. CLNP is often referred to as
ISO-IP. CLNP uses NSAP addresses to identify network devices. The
OME6110 supports CLNP protocol as specified in ISO/IEC 8473-1.
Note: OME6110 supports a maximum CLNP packet size of 512 bytes.
The OME6110 provides the ability to tunnel IP communications over OSI. The
OME6110 will route (forward) only IP packets and OSI (CLNP) PDUs
(support of reassembly of segmented DPDUs).
In order to communicate to the OME6110 NE in an OSI network, the
OME6110 can use iISIS routing protocol with auto-tunneling to allow the OSI
route to the OME6110 NE to be learnt through the OSI network. Once iISIS
routing is provisioned, static (SGRE) or dynamic (AGRE) IP over OSI tunnels
can be provisioned on the network element.
In order to provide communications through the OSI network, the following
items need to be performed:
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-17
•
•
Configure the OME6110 NE to communicate to the OSI area it is
connected to.
Enable iISIS routing protocol at the nodal level, as well as the applicable
network interface. The AGRE interface will be automatically created once
iISIS is enabled at the nodal level. If required, a SGRE interface can also
be provisioned on GRE tunnel terminating equipment, such as OME6110,
OME6500 or external routers. A static or dynamic routing protocol must
also be provisioned for the SGRE interface.
CLNP and layer 2 protocols using SNDCF
Sub-Network Dependent Convergence Function (SNDCF) interfaces are used
for multiplexing and demultiplexing packets between layer 3 modules (CLNP,
GRE, ESIS, and ISIS) and layer 2 interfaces (LAPD, PPP or MAC).
The OME6110 provides a SNDCF interface that allows layer 2 protocols such
as LAPD and PPP to interface with CLNP, ESIS, and ISIS routing protocols.
The GRE layer module will interact with CLNP via the addition of Network
Service User of CLNP.
Configure OSI connection
You must observe the following rules when you configure the OSI data
communication:
•
•
•
•
•
•
OME6110 requires an OSI local manual area address to interop with other
OSI products. The local manual area addresses are used to form the NSAP
address of each network element in the OSI level 1 area.
The default manual area address is 490000.
Up to three local manual area address can be provisioned for iISIS.
All NSAP formats are supported:
— ISO Local Addressing Format - e.g. 490000
— ISO DCC Addressing Format - e.g. 39xxxxxxxxxxxxxxxx
In order to communicate with an Intermediate System (IS) network
element, provision the Local Manual Area Address to be the same as the
Manual Area Address of the connected IS NE.
For communication to network elements in different OSI area, the Local
Manual Area Address has to be the unique area address used in the
networks which use both the default 490000 Manual Area Address and a
unique 39xxxxxxxxxxxxxxxxx Manual Area Address.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-18 Appendix A: Data communications planning
Configure GRE tunnel
TCP/IP Generic routing encapsulation (GRE) is a standard transport layer
encapsulation protocol which provides a standard method for transporting one
arbitrary network layer protocol over another arbitrary network layer protocol
(tunneling). A tunnel is effectively a point-to-point connection which allows
packets to be enclosed/encapsulated within another packet.
GRE tunnel
Two GRE types are supported:
• Static GRE tunnel : Static tunnels are user defined point-to-point tunnels
used to pass packets from one node to another. Static tunnels are ideal for
bridging sections of a network which do not support a protocol (for
example, routing IP packets through an OSI network). The user creates a
static tunnel by specifying a protocol (OSI or IP) and a tunnel termination
point (MAC address).
Note: Creating a static tunnel to a specific destination only allows packets
to be sent to that destination. You must configure a tunnel in the opposite
direction for packets to be returned.
•
Auto GRE tunnel: Auto-tunnels are dynamically created and removed as
required by a dual router. Auto-tunnels do not require user intervention but
only operate over iISIS sections of the network. Auto-tunnels configure
multiple tunnels to multiple destinations depending upon the best route
through multi-protocol networks that support iISIS.
Note: Static GRE and Auto GRE tunnels support only IP over OSI
tunnelling.
Static GRE tunnel
OME6110 supports a maximum of one static GRE tunnel
per network
element. The user creates a static tunnel by specifying a protocol (IP) and a
tunnel termination point (OSI address). The static GRE supports only IP over
OSI tunneling.
Note 1: The static GRE tunnel is user provisionable. For optimal
performance the static GRE tunnel should be provisioned provided there is
a LAPD or PPP interface on which iISIS is enabled. If there is no interface
with iISIS enabled then all packets into static GRE shall be dropped.
Note 2: Creating a static tunnel to a specific destination only allows
packets to be sent to that destination. You must configure a tunnel in the
opposite direction for packets to be returned.
Note 3: The OME6110 supports enabling of OSPF routing protocol on a
static GRE tunnel interface. When enabled, OSPF exchanges packets over
the GRE interface and treats the NE of the other end of the GRE tunnel as
its neighbor.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-19
Auto GRE tunnel
OME6110 supports auto GRE tunneling with iISIS routing protocol to provide
seamless integration of OSI only networks with Dual or IP only networks
elements.
The auto GRE tunnel is automatically configured and enabled when iISIS
routing protocol is enabled at the nodal level. There is no specific user
configuration required. The IP over OSI tunnel creation is done automatically
on a per packet basis over all the packets forwarded to the auto GRE interface
by IP. A default static route shall be provisioned automatically on the auto
GRE (called agre0) interface that is presented to the IP protocol stack. In this
scenario, the IP protocol stack shall forward packets that are not routable by
any other IP routing table entry to the auto GRE tunnel for further processing.
The default route shall have the last priority, as any user provisioned specific
static route shall have higher priority than default route when routing packets.
Note: If an NE contains 0.0.0.0/0 and 10.0.0.0/8 as two routes already
present, then auto-GRE creation can cause packets reaching through one
of the routes to be dropped. It is better to reconfigure the 0.0.0.0/0 and/or
10.0.0.0/8 routes to another suitable route so that the automatic creation of
auto GRE interface route functions seamlessly.
AGRE IP/OSI routing interactions
Figure 10-2 presents a diagram describing the IP packet routing when iISIS
routing protocol is enabled. The OME6110 supports an IP routing table, which
is updated with the least cost route for each IP destination from Static IP
routes, OSPF learnt routes and iISIS routes learnt over PPP interfaces, such as
connection to IP-capable network elements. IP routes learnt over CLNP are not
stored in the native IP routing table, but they are added to the OSI/GRE routing
table as part of the OSI routing function. The AGRE interface when
provisioned with appropriate static routes, allows for packets to be pushed
from the native IP routing domain to the iISIS routing domain (with IP routes
that communicate through OSI network elements). At each network element,
the AGRE interface must be properly provisioned with static routes covering
all destinations which will need to be auto-tunnelled. Once in the OSI routing
domain, the IP destinations of a received IP packet are looked up against the
OSI/GRE forwarding table to determine the NSAP (OSI address) that provides
most specific and least cost route to that IP destination. If a match is found then
GRE encapsulation of the IP packet into a CLNP (OSI) PDU with this NSAP
as the destination is performed. This CLNP PDU is then routed to this NSAP
by looking it up in the OSI routing table.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-20 Appendix A: Data communications planning
Figure 10-2
IP Packet Routing
Generic GRE implementation rules
You must observe the following rules when you implement auto or static GRE:
• OME6110 supports presentation of both auto and static GRE interfaces to
IP layer protocol. The presentation to IP must be a Linux network interface
driver. The auto GRE interface presented to the IP protocol layer is called
agre0. The static GRE interface presented to the IP protocol layer is called
sgre1.
• OME6110 supports presentation of both auto and static GRE interfaces to
•
CLNP protocol layer.
The MTU of the GRE network interface presented to the IP must be 446
bytes. The MTU presented to CLNP must be 512 bytes. This is valid for
both auto and static GRE interfaces.
Static GRE implementation rules
You must observe the following rules when you implement static GRE:
• Only one static OSI tunnel can be configured for the IP protocol per NE.
•
Provision the Remote Manual Area address of the tunnel destination.
The tunnel can be either in the same or remote OSI area. The default is
0x490000.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-21
•
•
Provision the Remote System ID of the tunnel destination node. The MAC
address of the tunnel destination node can be used as the Remote System
ID. The default is 0x000000000000.
Provision the NSAP Selector Byte of the tunnel destination node. Use
hexadecimal 2F (47 in decimal) for GRE protocol.
Note: When provisioning a static GRE tunnel between the OME6110 and
OME6500, a mismatch of the NSAP selector bytes provisioned at the
OME6500 and the OME6110 is expected. The NSAP Selector Byte
provisioned at the OME6110 WUI should be set to 2F, and the network
selector (NSEL, last 2 bytes of NSAP) provisioned from the OME6500
craft interface must be set to 00. The OME6500 automatically sets the
NSEL internally to support the required transport service.
Auto GRE implementation rules
You must observe the following rules when you implement Auto GRE:
•
•
•
The default route of 0.0.0.0/0 should not be configured over the LAN port
(eth0) and should not be advertised over iISIS on the GNE. This route may
interfere with the static route that needs to be configured on the AGRE
interface on every network element.
On the all OME6110 network elements (GNE and remote NEs), it is
recommended to manually provision the static route for the AGRE to be
within the network element DCN subnet.
On all remote network elements, the default route of 0.0.0.0/0 can be
provisioned as the static route over the AGRE interface.
Configure IP routing
Configure the interface to use either static or dynamic routing scheme. Refer
to IP communication on page 10-11 for more details.
Application protocols
This section lists out the supported application protocols and commands which
can be useful while working and troubleshooting an OME6110 network
element.
ftp
TCP/IP File transfer protocol (FTP) is a standard application layer protocol
used for transferring files across a network. This protocol uses a client/server
architecture. Both the FTP client and server are enabled on the OME6110.
The FTP protocol is used mainly during firmware, software, or on-line
documentation upgrade to handle all file transfers between the source (server)
of the image files and the network elements (clients).
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-22 Appendix A: Data communications planning
telnet
TCP/IP Telnet is a standard application layer terminal protocol used for
accessing remote computers, in a text based communications session between
a client and a host.
Both the Telnet client and server are enabled on the OME6110.
Diagnostic commands
This section lists the diagnostic commands which can be used on an OME6110
network element in a telnet session.
arp
Address resolution protocol utility
ifconfig
Displays status information for all interfaces.
ping
ICMP echo request and reply to test IP layer 3 connectivity. This command
requires root privilege.
route
Displays the kernel IP routing table.
tcpdump
Prints out headers of packets on all or specified interface. This command
requires root privilege.
Firewall considerations
The following ports must be passed through any firewall between the
management systems and the OME6110 network:
• TCP
— 20 (data), 21 (control) - FTP ports used for upgrades, or backup and
restore configurations.
— 2023 - Telnet port used for troubleshooting.
— 10001 - Used by TL-1 without prompt and character echo
— 10002 - Used by TL-1 with prompt and character echo
— 20080 - Used by HTTP for Web User Interface (WUI)
• UDP
— None used
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-23
Engineering guidelines
The following are DCN engineering guidelines:
ATTENTION
For configurations that exceed the following guidelines, contact Nortel for
assistance.
•
STM-1/OC-3 DCC
— Maximum of 2 DCCs per network element
— Maximum of 1 Section/Regenerator section (RS) or Line/Multiplex
section (MS) DCC per optical interface
— Section/Regenerator section (RS) DCC using D1-D3 bytes at 192 kbps
— Line/Multiplex section (MS) DCC using D4-D12 bytes at 576 kbps
•
LAPD
— MTU frame size of 240 to 512 bytes (default is 512)
— Metric: The DCC default metric is set to 4. When interworking with
legacy network elements, use the following DCC metrics:
– MS/Line DCC: 5
– RS/Section DCC: 6
— CLNP supported over LAPD (Default MTU frame size of 512 bytes
when presented to CLNP. The MTU size is user configurable and
should be in the range [240-512] bytes).
•
PPP
— MTU frame size of 1518 bytes
— Non-configurable default parameters:
– Maximum receive unit: no limitation
Note: Does not perform negotiation for MRU and accepts packets of any
size
–
–
–
–
Authentication protocol: disabled
Quality protocol: None
Protocol field compressed: Disabled
Address and control field compressed: Disabled
– FCS alternatives: 16 bit FCS
— Configurable default parameter:
– Magic number: <Disable>
•
OSPF
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-24 Appendix A: Data communications planning
—
—
—
—
Configurable default area of 0.0.0.1
Maximum of 150 routers in the same OSPF area as the OME6110 NE
Supports non-stub area
Configurable parameters:
– Hello Interval: 10 seconds. The range is [1-65535] seconds.
– Dead Interval: 40 seconds. The range is [1-65535] seconds.
— Non-configurable default parameters:
– Retransmit Interval: 5 seconds
– Transmit Delay: 1 second
– OSPF Ethernet Cost: 1
– OSPF DCC Cost: 1
– OSPF GRE Costs: 1
– OSPF LAN priority: 1
— OSPF Authentication mode : disabled (default) or Simple Password:
– Enabling and disabling of password based authentication for OSPF
on a per layer 2 interface level. If password based authentication is
enabled, then password is configurable.
— OSPF Authentication key: String configurable by the user if the OSPF
Authentication mode is set to Simple Password.
Note: For maximum network performance, the external DCN intervals
should be aligned with OME6110.
•
IP
— Maximum of 4096 IP routes (static and dynamic). But for optimal
performance it is recommended that not more than 512 entries be
added in the IP routing table. (Note that the IP routing table entries
include the routing entries added by OSPF or iISIS or Static Route into
the IP routing protocol domain).
— Maximum of 10 static routes per NE
– Use Destination Network IP address of 0.0.0.0/0 with next hop IP
address for default route
— MTU packet size of 240 to 512 bytes for OSI CLNP/LAPD
— MTU packet size of 1518 bytes for IP/PPP
•
GRE
— Only a single static IP over OSI GRE tunnel
— Tunnels between different OSI areas are supported
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-25
— MTU packet size should be 66 bytes less than the MTU for LAPD
•
•
Telnet session
— on the number of concurrent sessions per network element
— Session timeout is not supported
TL-1 sessions
— maximum of 4 concurrent sessions per network element
DCN performance
This section details the guidelines for DCN performance.
•
•
•
Native IP forwarding capability:
— 400 kbps for typical management messages without OSI interworking
— 320 kbps with IP tunnelling through OSI with GRE
Maximum MS/Line DCC throughput for IP packets is 400 kbps.
DCN Loading:
— Minimum link required for OMEA management is 128 kbps
— Minimum link for Craft only connection is 15kbps under normal
conditions
— Average native IP traffic per NE is 4 kbps
— Average resulting OSI traffic per NE with GRE is 6-8 kbps for the core
DCN
— Maximum number of IP DCC hops is 15
Supported DCN design examples
In order to have a complete understanding of the DCN for OME6110 and to
ensure that the DCN has the proper level of resiliency and connectivity for all
the network elements in the configuration, the following needs to be reviewed
while designing the DCN:
• Physical and logical connectivity - Ethernet LAN port, DCC ports, and IP
via OSI tunnels usage and provisioning.
• IP network design - IP class, subnets, and IP routing scheme (static or
dynamic OSPF).
Note: For configurations using OSPF routing in the examples below, the
default OSPF area 0.0.0.1 is used. In actual network implementations, the
OSPF area may be changed, along with the other interfaces, to a unique
value.
•
OSI network design (if applicable) - Area addresses, IS-IS or iIS-IS
routing.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-26 Appendix A: Data communications planning
Different options are available for designing a data communications network
containing OME6110 network elements. The following are examples
describing the physical and logical implementations:
• DCN example 1 - Using static routing with direct LAN connections to
OME6110 network elements.
• DCN example 2 - Using single OME6110 GNE with static routing to
external DCN. OSPF is used in between OME6110 network elements.
• DCN example 3 - Using single OME6110 GNE with OSPF to external
DCN. OSPF is used in between OME6110 network elements.
• DCN example 4 - Using OSPF with dual OME6110 GNEs to external
OSPF backbone.
• DCN example 5 - Using single OM4000/3000 GNE with GRE tunnels
through OM4000/3000 network to reach remote OME6110 network
elements in linear spurs off OM4000/3000 NE.
• DCN example 6 - Using single OM4000/3000 GNE with GRE tunnels
through OM4000/3000 network to reach remote OME6110 network
elements in SNCP/UPSR ring with an OM4000/3000 network element.
• DCN example 7 - Using dual OM4000/3000 GNEs with GRE tunnels
through OM4000/3000 network to reach remote OME6110 network
elements in SNCP/UPSR ring with generic SONET/SDH network
elements.
• DCN example 8 - Using single OME6110 GNE with iISIS through
OM4000/3000 network to reach remote OME6110 network elements in
SNCP/UPSR rings with OM4000/3000 network elements. Proxy ARP
used at OME6110 GNE for access to remote OME6110 NEs.
• DCN example 9 - Using single OME6500 GNE with iISIS through
OME6500 network to reach remote OME6110 network elements.
• DCN example 10 - Using single OME6500 GNE with iISIS to reach
remote OME6110 network elements in a SNCP/UPSR ring configuration
with generic SONET/SDH equipment.
• DCN example 11 - Using VC12 management channels through OM4000
network to reach remote OME6110 network elements in SNCP ring with
OM4000 and legacy OSI network elements. Transparent DCC used to
provided resilient OSI communications.
• DCN example 12 - Using E1 and VC12 management channels to reach
remote OME6110 network elements in SNCP ring with OM4000 and
legacy OSI network element. Transparent DCC used to provided resilient
OSI communications.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-27
DCN example 1 - Using static routing with direct LAN connections to
OME6110 network elements.
In this example (see Figure 10-3 on page 10-28 and Figure 10-4 on page
10-29), each OME6110 is directly connected to external DCN via the LCT
ports.
Routing protocol (static or dynamic) is not required from the DCN router to
each of the OME6110 network element. The external router and the OME6110
LAN interfaces are in the same subnet. A static route is required from each of
the network element to the DCN router interface.
No DCC is used in between the network elements.
This example does not provide redundant access to any of the OME6110
network elements.
DCN provisioning details
Table 10-5 on page 10-29 and Table 10-6 on page 10-30 detail the DCN
parameters for the DCN example 1 configuration.
Note: For parameters not listed, use the default settings.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-28 Appendix A: Data communications planning
Figure 10-3
DCN example 1 - Static routing with direct LAN connections to OME6110 network elements
OMEA
R6
IP DCN
IP
R2
R1
R4
R3
R5
IP
IP
IP
IP
IP
Target
Node
OME
61x0
A
OME
61x0
B
OME
61x0
C
No DCC
OME
61x0
D
OME
61x0
E
Legend
=
=
=
=
=
OME61x0 =
iIS-IS/OSI/LAPD/DCC
OSPF/IP/PPP/DCC
IP/GRE/OSI
OSI
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-29
Figure 10-4
DCN example 1 - IP logical view
OMEA
IP DCN
Legend
=
=
=
=
IP connection
OSPF routing between NEs/Router
iISIS routing between NEs
Static/Default routing
Table 10-5
DCN example 1 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
OME6110 D
OME6110 E
47.1.3.5
/29
-
47.1.3.12
/29
-
47.1.4.5
/29
-
47.1.4.18
/29
-
47.1.4.22
/29
-
-
-
-
-
-
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-30 Appendix A: Data communications planning
Table 10-5 (continued)
DCN example 1 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
OME6110 D
OME6110 E
No
No
No
No
No
-
-
-
-
-
0.0.0.0
/0
47.1.3.1
LAN-1-5
Disable
0.0.0.0
/0
47.1.3.9
LAN-1-5
Disable
0.0.0.0
/0
47.1.4.1
LAN-1-5
Disable
0.0.0.0
/0
47.1.4.17
LAN-1-5
Disable
0.0.0.0
/0
47.1.4.21
LAN-1-5
Disable
Disabled
-
Disabled
-
Disabled
-
Disabled
-
Disabled
-
Disabled
-
Disabled
-
Disabled
-
Disabled
-
Disabled
-
2 Set up IP routing
Ethernet OSPF enable
OSPF area
Static routing 1:
Address
Netmask
Next hop IP address
Next hop interface
Advertise
3 Set up DCC
STM1-3-1:
Protocol
MTU
STM1-3-2
Protocol
MTU
Table 10-6
DCN example 1 - Router and OMEA provisioning details
Parameters
Router 1
Router 2
Router 3
Router 4
Router 5
Router 6
OMEA
47.1.3.1
/29
-
47.1.3.9
/29
-
47.1.4.1
/29
-
47.1.4.17
/29
-
47.1.4.21
/29
-
47.1.1.1
/29
-
47.1.1.5
/29
47.1.1.1
1 Set up IP address
Ethernet interface:
IP address
Netmask
Default gateway
2 Set up IP routing
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-31
DCN example 2 - Using single OME6110 GNE with static routing to
external DCN. OSPF is used in between OME6110 network elements.
In this example (see Figure 10-5 on page 10-32 and Figure 10-6 on page
10-33), a single OME6110 network element is used as the GNE to establish
communication between the external DCN and the OME6110 sub-system.
Static routes are used on both the OME6110 and the connected external DCN
router. The static route provisioned on the external DCN router is redistributed
inside the external DCN by the external DCN routing protocol so that the
proper route is available for the management system to reach the OME6110
sub-system.
OSPF routing protocol is used in between the OME6110 network elements
using IP over DCC.
This example does not provide redundant access to the OME6110 sub-system
from the external DCN.
DCN provisioning details
Table 10-7 on page 10-33 and Table 10-8 on page 10-34 detail the DCN
parameters for the DCN example 2 configuration.
Note: For parameters not listed, use the default settings.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-32 Appendix A: Data communications planning
Figure 10-5
DCN example 2 - Single OME6110 GNE with static routing
R1
OMEA
IP
R2
IP DCN
OME
61x0
B
Target
node
OME
61x0
A
OME
61x0
D
OME
61x0
C
Legend
=
=
=
=
=
OME61x0 =
iIS-IS/OSI/LAPD/DCC
OSPF/IP/PPP/DCC
IP/GRE/OSI
OSI
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-33
Figure 10-6
DCN example 2 - IP logical view
OMEA
Legend
=
=
=
=
IP connection
OSPF routing between NEs/Router
iISIS routing between NEs
Static/Default routing
Table 10-7
DCN example 2 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
OME6110 D
47.1.3.6
/29
-
192.168.1.254
/24
-
192.168.1.254
/24
-
192.168.1.254
/24
-
47.1.3.65
/32
47.1.3.66
/32
47.1.3.67
/32
47.1.3.68
/32
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-34 Appendix A: Data communications planning
Table 10-7 (continued)
DCN example 2 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
OME6110 D
No
No
No
No
-
-
-
-
2 Set up IP routing
Ethernet OSPF enable
OSPF area
Static routing 1:
Address
Netmask
Next hop IP address
Next hop interface
Advertise
-
-
0.0.0.0
/0
47.1.3.1
LAN-1-5
Enable
-
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
3 Set up DCC
STM1-3-1:
Protocol
MTU
OSPF
STM1-3-2
Protocol
MTU
OSPF
Table 10-8
DCN example 2 - Router and OMEA provisioning details
Parameters
Router 1
Router 2
OMEA
47.1.1.1
/29
-
47.1.3.1
/29
-
47.1.1.5
/29
47.1.1.1
47.1.1.128
/32
47.1.1.129
/32
-
1 Set up IP address
Ethernet interface:
IP address
Netmask
Default gateway
Circuitless IP/ Loopback
IP Address
Netmask
2 Set up IP routing
OSPF Enable
Static routing 1:
Address
Netmask
Next hop IP address
Next hop interface
Advertise
-
Optical Multiservice Edge 6110
47.1.3.64
/29
47.1.3.6
Ethernet
Yes
-
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-35
DCN example 3 - Using single OME6110 GNE with OSPF to external DCN.
OSPF is used in between OME6110 network elements.
In this example (see Figure 10-7 on page 10-36 and Figure 10-8 on page
10-37), a single OME6110 network element is used as the GNE to establish
communication between the external DCN and the OME6110 sub-system.
OSPF routing protocol is used in between the OME6110 GNE and the external
DCN router, and in between the OME6110 network elements using IP over
DCC.
The external DCN router connected to the OME6110 GNE is acting as an Area
Border Router (ABR) which can use the route summarization feature to group
the IP routes for the OME6110 sub-network into a single route covering all the
OME6110 Router ID IP addresses.
This example does not provide redundant access to the OME6110 sub-system
from the external DCN.
DCN provisioning details
Table 10-9 on page 10-37 and Table 10-10 on page 10-38 detail the DCN
parameters for the DCN example 3 configuration.
Note: For parameters not listed, use the default settings.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-36 Appendix A: Data communications planning
Figure 10-7
DCN example 3 - Single OME6110 GNE with OSPF
R1
OMEA
IP
R2
IP DCN
OME
61x0
B
Target
node
OME
61x0
A
OME
61x0
D
OME
61x0
C
Legend
=
=
=
=
=
OME61x0 =
iIS-IS/OSI/LAPD/DCC
OSPF/IP/PPP/DCC
IP/GRE/OSI
OSI
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-37
Figure 10-8
DCN example 3 - IP logical view
OSPF area 0.0.0.0
OMEA
OSPF area 0.0.0.1
Legend
=
=
=
=
IP connection
OSPF routing between NEs/Router
iISIS routing between NEs
Static/Default routing
Table 10-9
DCN example 3 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
OME6110 D
47.1.3.6
/29
-
192.168.1.254
/24
-
192.168.1.254
/24
-
192.168.1.254
/24
-
47.1.3.65
/32
47.1.3.66
/32
47.1.3.67
/32
47.1.3.68
/32
Yes
No
No
No
0.0.0.1
-
-
-
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
2 Set up IP routing
Ethernet OSPF enable
OSPF area
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-38 Appendix A: Data communications planning
Table 10-9 (continued)
DCN example 3 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
OME6110 D
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
3 Set up DCC
STM1-3-1:
Protocol
MTU
OSPF
STM1-3-2
Protocol
MTU
OSPF
Table 10-10
DCN example 3 - Router and OMEA provisioning details
Parameters
Router 1
Router 2
OMEA
47.1.1.1
/29
-
47.1.3.1
/29
-
47.1.1.5
/29
47.1.1.1
47.1.1.128
/32
47.1.1.129
/32
-
Yes
Yes
0.0.0.0
0.0.0.0
Yes
Yes
0.0.0.0
0.0.0.1
1 Set up IP address
Ethernet interface:
IP address
Netmask
Default gateway
Circuitless IP/ Loopback
IP Address
Netmask
2 Set up IP routing
Global OSPF enable
OSPF area
Ethernet OSPF enable
OSPF area
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-39
DCN example 4 - Using OSPF with dual OME6110 GNEs to external OSPF
backbone.
In this example (see Figure 10-9 on page 10-40 and Figure 10-10 on page
10-41), two OME6110 network elements are used as dual GNEs to establish
communication between the external DCN and the OME6110 sub-system.
Typically, the two gateway NEs are located in two different sites and subnets
to maximize the network resilience.
Multiple OME6110 sub-systems can be connected using Ethernet in between
the LCT ports to minimize the number of DCN sites required and to extend the
DCN coverage within the engineering limits.
When the OME6110 sub-system provides a resilient internal DCN structure
(e.g. ring with DCC) so that any link failure inside the ring will not result in
losing any connectivity to either of the gateway network elements, the external
DCN router, which is acting as the Area Border Router (ABR), can then be
configured to use the route summarization feature to group the IP routes for the
OME6110 sub-network into a single route covering all the OME6110 Router
ID IP addresses.
When the OME6110 sub-system does not provide a resilient internal DCN
structure (e.g. linear chain), route summarization should not be used at the
ABR or resilient communications will be lost.
Note: Two or more GNEs can be used within the engineering limits.
DCN provisioning details
Table 10-11 on page 10-42, Table 10-12 on page 10-42 and Table 10-13 on
page 10-43 detail the DCN parameters for the DCN example 4 configuration.
Note: For parameters not listed, use the default settings.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-40 Appendix A: Data communications planning
Figure 10-9
DCN example 4 - Dual OME6110 GNEs with OSPF
OMEA
R1
IP
IP DCN
R2
OME
61x0
A
Target
node
R3
OME
61x0
B
OME
61x0
C
OME
61x0
D
OME
61x0
E
OME
61x0
F
OME
61x0
G
Legend
=
=
=
=
=
OME61x0 =
iIS-IS/OSI/LAPD/DCC
OSPF/IP/PPP/DCC
IP/GRE/OSI
OSI
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-41
Figure 10-10
DCN example 4 - IP logical view
OSPF area 0.0.0.0
OMEA
OSPF area 0.0.0.1
Legend
=
=
=
=
IP connection
OSPF routing between NEs/Router
iISIS routing between NEs
Static/Default routing
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-42 Appendix A: Data communications planning
Table 10-11
DCN example 4 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
OME6110 D
47.1.3.6
/29
-
47.1.3.18
/28
-
47.1.3.81
/30
-
47.1.3.85
/30
-
47.1.3.65
/32
47.1.3.66
/32
47.1.3.67
/32
47.1.3.68
/32
Yes
Yes
Yes
Yes
0.0.0.1
0.0.0.1
0.0.0.1
0.0.0.1
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
2 Set up IP routing
Ethernet OSPF enable
OSPF area
3 Set up DCC
STM1-3-1:
Protocol
MTU
OSPF
STM1-3-2
Protocol
MTU
OSPF
Table 10-12
DCN example 4 - OME6110 DCN provisioning details
Parameters
OME6110 E
OME6110 F
OME6110 G
47.1.3.82
/30
-
47.1.3.86
/30
-
192.168.1.254
/24
-
47.1.3.69
/32
47.1.3.70
/32
47.1.3.71
/32
Yes
Yes
Yes
0.0.0.1
0.0.0.1
0.0.0.1
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
2 Set up IP routing
Ethernet OSPF enable
OSPF area
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-43
Table 10-12 (continued)
DCN example 4 - OME6110 DCN provisioning details
Parameters
OME6110 E
OME6110 F
OME6110 G
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
3 Set up DCC
STM1-3-1:
Protocol
MTU
OSPF
STM1-3-2
Protocol
MTU
OSPF
Table 10-13
DCN example 4 - Router and OMEA provisioning details
Parameters
Router 1
Router 2
Router 3
OMEA
47.1.1.1
/29
-
47.1.3.1
/29
-
47.1.3.17
/28
-
47.1.1.5
/29
47.1.1.1
47.1.1.128
/32
47.1.1.129
/32
47.1.1.130
/32
-
Yes
Yes
Yes
-
0.0.0.0
0.0.0.0
0.0.0.0
-
Yes
Yes
Yes
0.0.0.0
0.0.0.1
0.0.0.1
1 Set up IP address
Ethernet interface:
IP address
Netmask
Default gateway
Circuitless IP/ Loopback
IP Address
Netmask
2 Set up IP routing
Global OSPF enable
OSPF area
Ethernet OSPF enable
OSPF area
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-44 Appendix A: Data communications planning
DCN example 5 - Using single OM4000/3000 GNE with GRE tunnels
through OM4000/3000 network to reach remote OME6110 network
elements in linear spurs off OM4000/3000 NE.
In this example (see Figure 10-11 on page 10-45 and Figure 10-12 on page
10-46), the OME6110 is subtended as 1+1 MSP/APS link with OM4000/3000
and IP static routing between the router and OME6100 is possible using GRE
tunnel. The router has a static route over the GRE tunnel to the router ID IP
address of the OME6100 NE and the OME6100 NE has a static route over the
GRE tunnel to the router.
Note: In some configurations, static route is recommended over OSPF
routing on the GRE tunnel to the router, as route redistribution between
iISIS and OSPF is not currently supported on OME6110.
For resiliency, a separate OSI GRE tunnel is needed from the external router
to each of the OME6110 network elements (allowing use of static routing or
OSPF routing over SGRE). If resiliency is not required, then only one static IP
over OSI GRE tunnel can be provisioned from the router to one of the
OME6110 NEs. In this configuration, only static routing can b used over the
SGRE). Communication to the other OME6110 NE is established using iISIS
routing through the OM4000/3000 NE.
The external router redistributes the static IP route into a dynamic routing
protocol, in order to advertise the OME6110 router IP addresses to the external
DCN.
The router on which the IP over OSI GRE tunnels terminate can only be a
Cisco router that supports ISO CLNS, with an IOS which has the “IP over
CLNS tunnel (CTunnel)” using GRE encapsulation feature. Some older
versions of IOS support IP over OSI tunnels using Cisco proprietary
encapsulation which is not suitable in this application.
DCN provisioning details
Table 10-14 on page 10-46 and Table 10-15 on page 10-48 detail the DCN
parameters for the DCN example 5 configuration.
Note: For parameters not listed, use the default settings.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-45
Figure 10-11
DCN example 5 - Single OM4K/3K GNE with GRE tunnels to remote OME6110 NEs in linear 1+1
MSP/APS with OM4K/3K
R1
OMEA
IP and
OSI DCN
Target
node OME
61x0
A
1+1 MSP/APS
OM
4K/3K
E
IP
R2
OSI (4K/3K)
OM
4K/3K
C
OM
4K/3K
D
1+1 MSP/APS
OME
61x0
B
iIS-IS
Packets routed using IS-IS
Legend
=
=
=
=
=
OME61x0 =
iIS-IS/OSI/LAPD/DCC
OSPF/IP/PPP/DCC
IP/GRE/OSI
OSI
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-46 Appendix A: Data communications planning
Figure 10-12
DCN example 5 - IP logical view
OMEA
OSPF area 0.0.0.0
Legend
=
=
=
=
IP connection
OSPF routing between NEs/Router
iISIS routing between NEs
Static/Default routing
Table 10-14
DCN example 5 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
192.168.1.254
/24
-
192.168.1.254
/24
-
47.1.3.65
/32
47.1.3.66
/32
No
No
-
-
47.1.1.0
/29
0.0.0.0
SGRE-1
Yes (see Note)
47.1.1.129
/32
0.0.0.0
SGRE-1
Yes
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
2 Set up IP routing
Ethernet OSPF enable
OSPF area
Static routing 1:
Address
Netmask
Next hop IP address
Next hop interface
Advertise
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-47
Table 10-14 (continued)
DCN example 5 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
Enable
Enable
490000
-
490000
-
LAPD
512
Enable
LAPD
512
Enable
-
-
490000
-
490000
-
Remote MAA
490000
490000
Remote system ID
Router 2 MAC
Router 2 MAC
NSAP selector
2F
2F
OSPF
Disable
Disable
3 Set up iISIS (Nodal level)
iISIS Enable:
MAA 1
MAA 2
MAA 3
4 Set up DCC
STM1-3-1:
Protocol
MTU
iISIS
STM1-3-2
Protocol
MTU
5 Set up static GRE tunnel
OSI Local MAA:
MAA 1
MAA 2
MAA 3
Note: The IP static route can be set to Advertise = Yes, when a static GRE
tunnel is provisioned from the router to each of the OME6110 network
element. If only one tunnel is provisioned, then the static route should be set
to Advertise= No.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-48 Appendix A: Data communications planning
Table 10-15
DCN example 5 - Router, OMEA, and OM4K/3K DCN provisioning details
Parameters
Router 1
Router 2
OM4K/3K E OM4K/3K C OMEA
-
-
-
-
-
47.1.1.1
/29
-
-
-
-
-
-
-
-
-
-
-
-
-
47.1.1.5
/29
47.1.1.1
47.1.1.128
/32
47.1.1.129
/32
-
-
-
Global routing
-
-
iIS-IS
iIS-IS
-
Global OSPF Enable
Yes
Yes
-
-
-
0.0.0.0
0.0.0.0
-
-
-
Yes
No
-
-
-
0.0.0.0
-
-
-
-
-
47.1.3.65
/32
47.1.3.65
GRE-1
Yes
-
-
-
-
47.1.3.66
/32
47.1.3.66
GRE-2
Yes
-
-
-
1 Set up IP address
Interface:
IP address
Netmask
Interface:
IP address
Netmask
Default gateway
Circuitless IP/ NE-IP:
IP address
Netmask
2 Set up IP routing
OSPF area
Ethernet OSPF enable
OSPF area
Static routing 1:
Address
Netmask
Next hop IP address
Next hop interface
Redistribute
Static routing 2:
Address
Netmask
Next hop IP address
Next hop interface
Redistribute
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-49
Table 10-15 (continued)
DCN example 5 - Router, OMEA, and OM4K/3K DCN provisioning details
Parameters
Router 1
Router 2
OM4K/3K E OM4K/3K C OMEA
3 Set up DCC
Interface 1:
Protocol
MTU
-
-
-
-
Interface 2:
Protocol
MTU
S-5-1
S-5-1
LAPD
512
LAPD
512
S-6-1
S-6-1
LAPD
512
LAPD
512
-
-
-
LAPD
512
-
S-2-1
Interface 4:
Protocol
MTU
-
S-1-1
Interface 3:
Protocol
MTU
-
-
-
-
LAPD
512
-
39xxx...xx1
490000
-
39xxx...xx2
490000
-
490000
-
490000
-
-
-
490000
NE A MAC
2F
-
-
-
-
490000
NE B MAC
2F
-
-
-
4 Set up static GRE tunnel
OSI Local MAA:
MAA 1
MAA 2
MAA 3
GRE tunnel 1:
Remote MAA
Remote system ID
NSAP selector
GRE tunnel 2:
Remote MAA
Remote system ID
NSAP selector
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-50 Appendix A: Data communications planning
DCN example 6 - Using single OM4000/3000 GNE with GRE tunnels
through OM4000/3000 network to reach remote OME6110 network
elements in SNCP/UPSR ring with an OM4000/3000 network element.
In this example (see Figure 10-13 on page 10-51 and Figure 10-14 on page
10-52), a single ABR is used at the DCN gateway site to establish
communication between the external DCN and the OME6110/OM4000/3000
sub-systems.
A single OM4K/3K is connected to the external DCN via an OSI only enabled
port and acts as the GNE for the other OM4K/3K network elements.
For configurations with fully robust (meshed/ring) internal DCN connectivity
Data communication to the remote subtending OME6110 network elements is
achieved using IP over OSI GRE tunnels through the OM4K/3K network and
these tunnels are terminated directly on the ABR. In order to provide resilient
data communication against any fiber breaks in the OME6110 system, two
tunnels are required from the ABR through the OM4K/3KGNE. iISIS routing
is used to establish communication to all OME6110 within the ring.
Note: Static route is recommended over OSPF routing on the GRE tunnel
to the router, if iISIS routing is used between OME6110 network elements.
For configurations with non-redundant (linear) internal DCN connectivity
Data communication to the remote subtending OME6110 network elements is
achieved using IP over OSI GRE tunnels through the OM4K/3K network and
these tunnels are terminated directly on the ABR. In order to provide resilient
data communication against any fiber breaks in the OME6110 system, two
tunnels are required from the ABR through the OM4K/3K GNE. OSPF routing
is used to establish communication to all OME6110 within the subtending
ring.
Note: OSPF routing on the GRE tunnel to the router, and OSPF routing is
used between OME6110 network elements can be used.
The ABR on which the IP over OSI GRE tunnels terminate can only be a Cisco
router that supports ISO CLNS, with an IOS which has the “IP over CLNS
tunnel (CTunnel)” using GRE encapsulation feature. Some older versions of
IOS support IP over OSI tunnels using Cisco proprietary encapsulation which
is not suitable in this application.
DCN provisioning details
Table 10-16 on page 10-52 and Table 10-17 on page 10-54 detail the DCN
parameters for the DCN example 6 configuration.
Note: For parameters not listed, use the default settings.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-51
Figure 10-13
DCN example 6 - Single OM4K/3K with GRE tunnels to remote OME6110 NEs in SNCP/UPSR ring
with OM4K/3K
R1
OMEA
IP
IP and
OSI DCN
R2
OSI (4K/3K)
OSI area
e.g. 0002
OM
4K/3K
F
OME
61x0
A
OM
4K/3K
D
Target
node
OM
4K/3K
E
OME
61x0
B
OME
61x0
C
Packets routed using IS-IS
iIS-IS
Legend
=
=
=
=
=
=
OME 61x0 =
iIS-IS/OSI/LAPD/DCC
iIS-IS/IP/PPP/DCC
OSPF/IP/PPP/DCC
IP/GRE/OSI
OSI
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-52 Appendix A: Data communications planning
Figure 10-14
DCN example 6 - IP logical view
OMEA
OSPF area 0.0.0.0
OSPF area 0.0.0.1
Legend
=
=
=
=
IP connection
OSPF routing between NEs
iISIS routing between NEs
Static/Default routing
Table 10-16
DCN example 6 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
192.168.1.254
/24
-
192.168.1.254
/24
-
192.168.1.254
/24
-
47.1.3.65
/32
47.1.3.66
/32
47.1.3.67
/32
No
No
No
-
-
-
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
2 Set up IP routing
Ethernet OSPF enable
OSPF area
Static routing 1:
Address
Netmask
Next hop IP address
Next hop interface
Advertise
47.1.1.0
/29
0.0.0.0
SGRE-1
Yes (see Note)
Optical Multiservice Edge 6110
47.1.1.0
/29
0.0.0.0
SGRE-1
Yes (see Note)
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-53
Table 10-16 (continued)
DCN example 6 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
Enable
Enable
Enable
490000
-
490000
-
490000
-
LAPD
512
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
LAPD
512
Enable
490000
-
-
490000
-
Remote MAA
490000
-
490000
Remote system ID
Router 2 MAC
-
Router 2 MAC
NSAP selector
2F
-
2F
OSPF
Disable
-
Disable
3 Set up iISIS (Nodal level)
iISIS Enable:
MAA 1
MAA 2
MAA 3
4 Set up DCC
STM1-3-1:
Protocol
MTU
iISIS
STM1-3-2
Protocol
MTU
iISIS
5 Set up static GRE tunnel
OSI Local MAA:
MAA 1
MAA 2
MAA 3
Note: The IP static route can be set to Advertise = No if each OME6110 network element has a static
GRE tunnel to the router.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-54 Appendix A: Data communications planning
Table 10-17
DCN example 6 - Router, OMEA, and OM4K/3K DCN provisioning details
Parameters
Router 1
Router 2
OM4K/3K F
OM4K/3K D OMEA
-
-
-
-
-
47.1.1.1
/29
-
-
-
-
-
-
-
-
-
-
-
-
-
47.1.1.5
/29
47.1.1.1
47.1.1.128
/32
47.1.1.129
/32
-
-
-
Global Routing
-
-
IS-IS
IS-IS
-
Global OSPF enable
Yes
Yes
-
-
-
0.0.0.0
0.0.0.0
-
-
-
Yes
No
-
-
-
0.0.0.0
-
-
-
-
S-5-1
S-5-1
LAPD
512
LAPD
512
S-6-1
S-6-1
LAPD
512
LAPD
512
1 Set up IP address
Interface:
IP address
Netmask
Interface:
IP address
Netmask
Default gateway
Circuitless IP/ NE-IP:
IP address
Netmask
2 Set up IP routing
OSPF area
Ethernet OSPF enable
OSPF area
Static routing 1:
Address
Netmask
Next hop IP address
Next hop interface
47.1.3.64
/29
47.1.3.65
GRE Tunnel
3 Set up DCC
Interface 1:
Protocol
MTU
-
-
Interface 2:
Protocol
MTU
-
-
-
-
-
-
-
-
LAPD
512
-
S-2-1
Interface 4:
Protocol
MTU
-
S-1-1
Interface 3:
Protocol
MTU
-
Optical Multiservice Edge 6110
LAPD
512
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
-
Appendix A: Data communications planning 10-55
Table 10-17 (continued)
DCN example 6 - Router, OMEA, and OM4K/3K DCN provisioning details
Parameters
Router 1
Router 2
OM4K/3K F
OM4K/3K D OMEA
39xxx...xx1
490000
-
39xxx...xx2
490000
-
490000
-
490000
-
-
-
490000
NE A MAC
2F
-
-
-
-
490000
NE C MAC
2F
-
-
-
4 Set up GRE tunnel
OSI Local MAA:
MAA 1
MAA 2
MAA 3
GRE tunnel 1:
Remote MAA
Remote system ID
NSAP selector
GRE tunnel 2:
Remote MAA
Remote system ID
NSAP selector
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-56 Appendix A: Data communications planning
DCN example 7 - Using dual OM4000/3000 GNEs with GRE tunnels
through OM4000/3000 network to reach remote OME6110 network
elements in SNCP/UPSR ring with generic SONET/SDH network elements.
In this example (see Figure 10-15 on page 10-57 and Figure 10-16 on page
10-58), similar to previous configuration, but with multiple gateway locations
with GNEs and routers to maximize the resilience of this solution.
The ABR on which the IP over OSI GRE tunnels terminate can only be a Cisco
router that supports ISO CLNS, with an IOS which has the “IP over CLNS
tunnel (CTunnel)” using GRE encapsulation feature. Some older versions of
IOS support IP over OSI tunnels using Cisco proprietary encapsulation which
is not suitable in this application.
DCN provisioning details
Table 10-18 on page 10-58 and Table 10-19 on page 10-60 detail the DCN
parameters for the DCN example 7 configuration.
Note: For parameters not listed, use the default settings.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-57
Figure 10-15
DCN example 7 - Dual OM4K/3K GNEs with GRE tunnels to remote OME6110 NEs in SNCP/UPSR
ring with OM4K/3K
OMEA
R1
R2
OM
4K/3K
F
Target
node
OME
61x0
A
OM
4K/3K
D
OM
4K/3K
E
OME
61x0
B
OM
4K/3K
H
IP
OSI (4K/3K)
R3
OM
4K/3K
G
IP and
OSI DCN
OME
61x0
C
iIS-IS
Packets routed using IS-IS
Legend
=
=
=
=
=
=
OME 61x0 =
iIS-IS/OSI/LAPD/DCC
iIS-IS/IP/PPP/DCC
OSPF/IP/PPP/DCC
IP/GRE/OSI
OSI
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-58 Appendix A: Data communications planning
Figure 10-16
DCN example 7 - IP logical view
OMEA
OSPF area 0.0.0.0
OSPF area 0.0.0.1
Legend
=
=
=
=
IP connection
OSPF routing between NEs
iISIS routing between NEs
Static/Default routing
Table 10-18
DCN example 7 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
192.168.1.254
/24
-
192.168.1.254
/24
-
192.168.1.254
/24
-
47.1.3.65
/32
47.1.3.66
/32
47.1.3.67
/32
No
No
No
-
-
-
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
2 Set up IP routing
Ethernet OSPF enable
OSPF area
Static routing 1:
Address
Netmask
Next hop IP address
Next hop interface
Advertise
47.1.1.0
/29
0.0.0.0
SGRE-1
Yes (see Note)
47.1.1.0
/29
0.0.0.0
SGRE-1
Yes (see Note)
3 Set up iISIS (Nodal level)
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-59
Table 10-18 (continued)
DCN example 7 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
iISIS Enable:
Enable
Enable
Enable
490000
-
490000
-
490000
-
LAPD
512
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
LAPD
512
Enable
490000
-
-
490000
-
Remote MAA
490000
-
490000
Remote system ID
Router 2 MAC
-
Router 3 MAC
NSAP selector
2F
-
2F
OSPF
Disable
-
Disable
MAA 1
MAA 2
MAA 3
4 Set up DCC
STM1-3-1:
Protocol
MTU
iISIS
STM1-3-2
Protocol
MTU
iISIS
5 Set up GRE tunnel
OSI Local MAA:
MAA 1
MAA 2
MAA 3
Note: The IP static route can be set to Advertise = No if each OME6110 network element has a static
GRE tunnel to the router.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-60 Appendix A: Data communications planning
Table 10-19
DCN example 7 - Router, OMEA, and OM4K/3K DCN provisioning details
Parameters
Router 1
Router 2
Router 3
OM4K/3K
F, G & H
OM4K/3K
D&E
OMEA
-
-
-
-
-
-
47.1.1.1
/29
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
47.1.1.5
/29
47.1.1.1
47.1.1.128
/32
47.1.1.129
/32
47.1.1.130
/32
-
-
-
Global Routing
-
-
-
IS-IS
IS-IS
-
Global OSPF enable
Yes
Yes
Yes
-
-
-
0.0.0.0
0.0.0.0
0.0.0.0
-
-
-
Yes
No
No
-
-
-
0.0.0.0
-
-
-
-
-
47.1.3.64
/29
47.1.3.65
GRE Tunnel
47.1.3.64
/29
47.1.3.67
GRE Tunnel
S-5-1
S-5-1
LAPD
512
LAPD
512
S-6-1
S-6-1
LAPD
512
LAPD
512
1 Set up IP address
Interface:
IP address
Netmask
Interface:
IP address
Netmask
Default gateway
Circuitless IP/ NE-IP:
IP address
Netmask
2 Set up IP routing
OSPF area
Ethernet OSPF enable
OSPF area
Static routing 1:
Address
Netmask
Next hop IP address
Next hop interface
3 Set up DCC
Interface 1:
Protocol
MTU
-
-
-
Interface 2:
Protocol
MTU
-
-
-
-
-
-
-
-
-
-
-
LAPD
512
-
S-2-1
Interface 4:
Protocol
MTU
-
S-1-1
Interface 3:
Protocol
MTU
-
Optical Multiservice Edge 6110
LAPD
512
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
-
Appendix A: Data communications planning 10-61
Table 10-19 (continued)
DCN example 7 - Router, OMEA, and OM4K/3K DCN provisioning details
Parameters
Router 1
Router 2
Router 3
OM4K/3K
F, G & H
OM4K/3K
D&E
OMEA
39xxx...xx1
490000
-
39xxx...xx2
490000
-
39xxx...xx2
490000
-
490000
-
490000
-
-
-
490000
NE A MAC
2F
490000
NE C MAC
2F
-
-
-
4 Set up GRE tunnel
OSI Local MAA:
MAA 1
MAA 2
MAA 3
GRE tunnel 1:
Remote MAA
Remote system ID
NSAP selector
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-62 Appendix A: Data communications planning
DCN example 8 - Using single OME6110 GNE with iISIS through
OM4000/3000 network to reach remote OME6110 network elements in
SNCP/UPSR rings with OM4000/3000 network elements. Proxy ARP used
at OME6110 GNE for access to remote OME6110 NEs.
In this example (see Figure 10-17 on page 10-63 and Figure 10-18 on page
10-64), OME6110 network elements use iISIS routing to establish
communication to the remote OME6110 through the OM4K/3K network.
Connection between OME6110 and OM4K/3K is over SONET/SDH with
DCC enabled, with iISIS between various sub-tending OME6110 NEs in
SNCP/UPSR rings to provide resilience without the need for additional
OME6110 GNEs. The auto-tunnel interface (AGRE) should have a static route
provisioned within the subnet of the OME6110 network elements. The remote
OME6110 NEs are provisioned as proxy ARP neighbours at the OME6110
GNE.
An OSI enabled router can be used for the OSI communication for the
OM4K/3K to the DCN network.
DCN provisioning details
Table 10-20 on page 10-64, Table 10-21 on page 10-66, Table 10-22 on page
10-67 and Table 10-23 on page 10-68 detail the DCN parameters for the DCN
example 8 configuration.
Note: For parameters not listed, use the default settings.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-63
Figure 10-17
DCN example 8 - Single OME6110 GNE with iISIS routing in SNCP/UPSR rings with OM4K/3K
OMEA
R1
IP
IP and
OSI DCN
R3
OSI
(4K/3K)
OSI area
e.g. 0002
Target
node
R2
OM
4K/3K
L
OME
61x0
A
OM
4K/3K
H
OME
61x0
B
OM
4K/3K
J
OM
4K/3K
K
OME
61x0
D
OME
61x0
E
OME
61x0
F
OM
4K/3K
M
OME
61x0
C
Legend
=
=
=
=
=
=
OME 61x0 =
iIS-IS/OSI/LAPD/DCC
iIS-IS/IP/PPP/DCC
OSPF/IP/PPP/DCC
IP/GRE/OSI
OSI
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-64 Appendix A: Data communications planning
Figure 10-18
DCN example 8 - IP logical view
OSPF area 0.0.0.0
OMEA
OSI area 0.0.0.2
Legend
= IP connection
= OSPF routing between NEs/Router
= iISIS routing between NEs
= Static/Default routing
Table 10-20
DCN example 8 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
192.168.1.254
/24
-
192.168.1.254
/24
-
192.168.1.254
/24
-
47.1.3.65
/32
47.1.3.66
/32
47.1.3.67
/32
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-65
Table 10-20 (continued)
DCN example 8 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
No
No
No
-
-
-
0.0.0.0
/0
0.0.0.0
AGRE
No
0.0.0.0
/0
0.0.0.0
AGRE
No
0.0.0.0
/0
0.0.0.0
AGRE
No
47.1.3.64
/29
0.0.0.0
AGRE
No
47.1.3.64
/29
0.0.0.0
AGRE
No
47.1.3.64
/29
0.0.0.0
AGRE
No
Enable
Enable
Enable
490000
-
490000
-
490000
-
LAPD
512
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
LAPD
512
Enable
2 Set up IP routing
Ethernet OSPF enable
OSPF area
Static routing 1
Address
Netmask
Next hop IP address
Next hop interface
Advertise
Static routing 2
Address
Netmask
Next hop IP address
Next hop interface
Advertise
3 Set up iISIS (Nodal level)
iISIS Enable:
MAA 1
MAA 2
MAA 3
4 Set up DCC
STM1-3-1:
Protocol
MTU
iISIS
STM1-3-2
Protocol
MTU
iISIS
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-66 Appendix A: Data communications planning
Table 10-21
DCN example 8 - OME6110 DCN provisioning details
Parameters
OME6110 D
OME6110 E
OME6110 F
(see Note)
192.168.1.254
/24
-
192.168.1.254
/24
-
47.1.3.71
/29
-
47.1.3.68
/32
47.1.3.69
/32
47.1.3.70
/32
No
No
No
OSPF area
-
-
-
Static routing 1
-
-
Address
Netmask
Next hop IP address
Next hop interface
Advertise
0.0.0.0
/0
0.0.0.0
AGRE
No
0.0.0.0
/0
0.0.0.0
AGRE
No
47.1.3.64
/29
0.0.0.0
AGRE
No
47.1.3.64
/29
0.0.0.0
AGRE
No
47.1.3.64
/29
0.0.0.0
AGRE
No
47.0.0.0
/8
47.1.3.1
Eth0
Yes
LAPD
512
Enable
PPP
1518
Enable
LAPD
512
Enable
PPP
1518
Enable
LAPD
512
Enable
-
Enable
Enable
Enable
490000
-
490000
-
490000
-
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
2 Set up IP routing
Ethernet OSPF enable
Static routing 2
Address
Netmask
Next hop IP address
Next hop interface
Advertise
3 Set up DCC
STM1-3-1:
Protocol
MTU
iISIS
STM1-3-2
Protocol
MTU
iISIS
4 Set up iISIS (Nodal level)
iISIS Enable:
MAA 1
MAA 2
MAA 3
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-67
Table 10-21 (continued)
DCN example 8 - OME6110 DCN provisioning details
Parameters
OME6110 D
OME6110 E
OME6110 F
(see Note)
5 Set up Proxy ARP Neighbours
Proxy ARP Neighbour IP addresses:
47.1.3.65
47.1.3.66
47.1.3.67
47.1.3.68
47.1.3.69
Neighbour 1
Neighbour 2
Neignbour 3
Neighbour 4
Neighbour 5
Note: The OME6110 F (GNE) is being managed via the Eth0 IP address.
Table 10-22
DCN example 8 - OM4K/3K DCN provisioning details
Parameters
OM4K/3K H
OM4K/3K J
OM4K/3K K
OM4K/3K L
OM4K/3K M
Global Routing
IS-IS
IS-IS
IS-IS
IS-IS
IS-IS
Global OSPF enable
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Interface 1:
S-5-1
S-5-1
S-5-1
S-5-1
S-5-1
Protocol
MTU
LAPD
512
LAPD
512
LAPD
512
LAPD
512
LAPD
512
Interface 2:
S-6-1
S-6-1
S-6-1
S-6-1
S-6-1
Protocol
MTU
LAPD
512
LAPD
512
LAPD
512
LAPD
512
LAPD
512
Interface 3:
S-1-1
S-1-1
S-1-1
S-1-1
-
Protocol
MTU
LAPD
512
LAPD
512
LAPD
512
LAPD
512
-
Interface 4:
S-2-1
S-2-1
S-2-1
-
-
Protocol
MTU
LAPD
512
LAPD
512
LAPD
512
-
-
1 Set up IP routing
OSPF area
Ethernet OSPF enable
OSPF area
2 Set up DCC
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-68 Appendix A: Data communications planning
Table 10-23
DCN example 8 - Router and OMEA DCN provisioning details
Parameters
Router 1
Router 2
Router 3
OMEA
-
-
-
-
47.1.1.1
/29
-
-
-
-
Eth0: VLAN1
Eth0: VLAN1
-
-
47.1.3.72
/28
-
47.1.3.73
/28
-
47.1.1.5
/29
47.1.1.1
47.1.1.128
/32
47.1.1.129
/32
47.1.1.130
/32
-
Yes
Yes
Yes
-
0.0.0.0
0.0.0.0
0.0.0.0
-
Yes
No
No
-
0.0.0.0
-
-
-
47.1.3.64
/28
47.1.3.72
Eth0
Yes
47.1.3.64
/28
47.1.3.71
Eth0
Yes
1 Set up IP address
Interface:
IP address
Netmask
Interface:
IP address
Netmask
Default gateway
Circuitless IP/ NE-IP:
IP address
Netmask
2 Set up IP routing
Global OSPF enable
OSPF area
Ethernet OSPF enable
OSPF area
Static routing 1
Address
Netmask
Next hop IP address
Next hop interface
Advertise
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-69
DCN example 9 - Using single OME6500 GNE with iISIS through OME6500
network to reach remote OME6110 network elements.
In this example (see Figure 10-19 on page 10-70 and Figure 10-20 on page
10-71), a single OME6500 network element is used as the GNE to establish
communication between the external DCN and the OME6110 and the
OME6500 network elements.
iISIS routing protocol is used with auto-tunneling to establish communication
from the OME6500 GNE to the remote OME6110 through the OME6500
network.
The remote OME6110 NEs are provisioned as proxy ARP neighbours at the
OME6500 GNE.
DCN provisioning details
Table 10-24 on page 10-71, Table 10-25 on page 10-72 and Table 10-26 on
page 10-74 detail the DCN parameters for the DCN example 9 configuration.
Note: For parameters not listed, use the default settings.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-70 Appendix A: Data communications planning
Figure 10-19
DCN example 9 - Single OME6500 GNE with iISIS to remote OME6110 NEs
OMEA
R1
IP
IP and
OSI DCN
R2
OSI area
e.g. 0002
IP
OME
6500
H
OME
61x0
A
OME
6500
F
Target
node
OME
61x0
B
MS DCC
OME
6500
G
OME
61x0
C
Packets routed using iIS-IS/PPP
Legend
=
=
=
=
=
=
OME61x0 =
iIS-IS/OSI/LAPD/DCC
iIS-IS/IP/PPP/DCC
OSPF/IP/PPP/DCC
IP/GRE/OSI
OSI
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-71
Figure 10-20
DCN example 9 - IP logical view
OSPF area 0.0.0.0
OMEA
OSI area 0002
Legend
= IP connection
= OSPF routing between NEs/Router
= iISIS routing between NEs
= Static/Default routing
Table 10-24
DCN example 9 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
192.168.1.254
/24
-
192.168.1.254
/24
-
192.168.1.254
/24
-
47.1.3.65
/32
47.1.3.66
/32
47.1.3.67
/32
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-72 Appendix A: Data communications planning
Table 10-24 (continued)
DCN example 9 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
No
No
No
-
-
-
Enable
Enable
Enable
490000
-
490000
-
490000
-
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
PPP
1518
Enable
2 Set up IP routing
Ethernet OSPF enable
OSPF area
3 Set up iISIS (Nodal level)
iISIS Enable:
MAA 1
MAA 2
MAA 3
4 Set up DCC
STM1-3-1:
Protocol
MTU
iISIS
STM1-3-2
Protocol
MTU
iISIS
Table 10-25
DCN example 9 - OM6500 DCN provisioning details
Parameters
OM6500 H
OM6500 G
OM6500 F
COLANX
-
-
47.1.3.11
/25
-
-
-
-
-
-
-
-
47.1.3.92
/32
47.1.3.93
/32
47.1.1.94
/32
iIS-IS
iIS-IS
iIS-IS
1 Set up IP address
Interface:
IP address
Netmask
Interface:
IP address
Netmask
Default gateway
Circuitless IP/ NE-IP:
IP address
Netmask
2 Set up IP routing
Global Routing
Route redistribution
Ethernet OSPF enable
OSPF area
OSPF redistribution -
-
COLANX
-
-
0.0.0.0
-
-
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-73
Table 10-25 (continued)
DCN example 9 - OM6500 DCN provisioning details
Parameters
OM6500 H
OM6500 G
OM6500 F
Interface 1:
S-5-1
S-5-1
S-1-1
Protocol
MTU
PPP
1500
PPP
1500
PPP
1500
Interface 2:
S-6-1
S-6-1
S-2-1
Protocol
MTU
PPP
1500
PPP
1500
PPP
1500
Interface 3:
-
-
S-5-1
Protocol
MTU
-
-
PPP
1500
Interface 4:
-
-
S-6-1
Protocol
MTU
-
-
PPP
1500
490000
-
490000
-
490000
-
-
-
3 Set up DCC
4 Set up MAA
OSI Local MAA:
MAA 1
MAA 2
MAA 3
5 Set up Proxy ARP
Proxy ARP Neighbour IP
addresses:
Neighbour 1
Neighbour 2
Neignbour 3
Neighbour 4
Neighbour 5
47.1.3.65
47.1.3.66
47.1.3.67
47.1.3.93
47.1.3.94
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-74 Appendix A: Data communications planning
Table 10-26
DCN example 9 - Router and OMEA DCN provisioning details
Parameters
Router 1
Router 2
OMEA
-
-
-
47.1.1.1
/29
47.1.3.1
/25
-
-
-
-
-
-
47.1.1.5
/29
47.1.1.1
47.1.1.128
/32
47.1.1.129
/32
-
Yes
Yes
-
0.0.0.0
0.0.0.0
-
Yes
Yes
-
0.0.0.0
0.0.0.0
-
1 Set up IP address
Interface:
IP address
Netmask
Interface:
IP address
Netmask
Default gateway
Circuitless IP/ NE-IP:
IP address
Netmask
2 Set up IP routing
Global OSPF enable
OSPF area
Ethernet OSPF enable
OSPF area
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-75
DCN example 10 - Using single OME6500 GNE with iISIS to reach remote
OME6110 network elements in a SNCP/UPSR ring configuration with
generic SONET/SDH equipment.
In this example (see Figure 10-21 on page 10-76, Figure 10-22 on page 10-77
and Figure 10-23 on page 10-78), a single OME6500 network element is used
as the GNE to establish communication between the external DCN and the
OME6110 within a SNCP/UPSR ring with generic SONET/SDH equipment
(such as OM4000, TN-1C and OM3000 network elements).
iISIS routing protocol is used with auto-tunneling to establish communication
from the OME6500 GNE to the remote OME6110 network elements.
The remote OME6110 NEs are provisioned as proxy ARP neighbours at the
OME6500 GNE.
DCN provisioning details
Table 10-27 on page 10-79 and Table 10-28 on page 10-80 detail the DCN
parameters for the DCN example 10 configuration.
Note: For parameters not listed, use the default settings.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-76 Appendix A: Data communications planning
Figure 10-21
DCN example 10 - Single OME6500 with iISIS to reach remote OME6110 NEs in SNCP/UPSR with
generic SONET/SDH equipment
OSI and
IP DCN
R1
OMEA
IP
R2
IP
OSI area
e.g. 0002
OME
6500
H
OME
61x0
A
XXX
F
OME
61x0
B
OME
6500
G
RS DCC
XXX
C
Legend
=
=
=
=
=
=
OME61x0 =
iIS-IS/OSI/LAPD/DCC
iIS-IS/IP/PPP/DCC
OSPF/IP/PPP/DCC
IP/GRE/OSI
OSI
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-77
Figure 10-22
DCN example 10 - IP logical view
OSPF area 0.0.0.0
OMEA
OSI area 0002
Legend
=
=
=
=
IP connection
OSPF routing between NEs/Router
iISIS routing between NEs
Static/Default routing
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-78 Appendix A: Data communications planning
Figure 10-23
DCN example 10 - iIS-IS / IS-IS logical view
OMEA
R1
OSI and
IP DCN
OSI
R2
OSI area
e.g. 0002
RS DCC
OME
61x0
B
OME
6500
H
OME
61x0
A
XXX
F
OME
6500
G
XXX
C
Legend
OME61x0
= OSI connection
= iISIS/ISIS routing between NEs
= OME6110 or OME6130
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-79
Table 10-27
DCN example 10 - OME6110, OME6500, and OSI NE DCN provisioning details
Parameters
OME6110 A
OME6110 B
NE C
NE F
OME6500
G
OME6500
H
1 Set up IP address
COLANX
LAN-1-5 port:
IP address
Netmask
Default gateway
192.168.1.254 192.168.1.254 /24
/24
-
-
-
47.1.3.2
-
Router ID:
IP address
Netmask
47.1.3.65
/32
47.1.3.66
/32
-
-
47.1.3.93
/32
47.1.3.92
/32
-
-
IS-IS
IS-IS
iIS-IS
iIS-IS
-
-
-
-
-
OSPF
redistribution
Disable
Disable
-
-
-
Yes
-
-
-
-
-
0.0.0.2
2 Set up IP routing
Global Routing
Route redistribution
Ethernet OSPF enable
OSPF area
3 Set up iISIS (Nodal level)
Enable
Enable
490000
-
490000
-
STM1-3-1
STM1-3-1
S-5-1
S-5-1
S-5-1
S-5-1
LAPD
512
Enable
PPP
1518
Enable
LAPD
512
LAPD
512
LAPD
512
Yes
PPP
1500
Yes
STM1-3-2
STM1-3-2
S-6-1
S-6-1
S-6-1
S-6-1
PPP
1518
Enable
LAPD
512
Enable
LAPD
512
LAPD
512
PPP
1500
Yes
LAPD
512
Yes
Interface 3
-
-
-
S-1-1
-
-
Protocol
MTU
-
-
-
LAPD
512
-
-
Interface 4
-
-
-
S-2-1
-
-
Protocol
MTU
-
-
-
LAPD
512
-
-
iISIS Enable:
MAA 1
MAA 2
MAA 3
4 Set up DCC
Interface 1:
Protocol
MTU
iISIS
Interface 2
Protocol
MTU
iISIS
5 Set up Proxy ARP
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-80 Appendix A: Data communications planning
Table 10-27 (continued)
DCN example 10 - OME6110, OME6500, and OSI NE DCN provisioning details
Parameters
OME6110 A
Proxy ARP Neighbour IP addresses:
OME6110 B
NE C
NE F
OME6500
G
-
-
-
47.1.3.65
47.1.3.66
47.1.3.93
Neighbour 1
Neighbour 2
Neignbour 3
Table 10-28
DCN example 10 - Router and OMEA DCN provisioning details
Parameters
Router 1
Router 2
OMEA
1 Set up IP address
-
Interface:
IP address
Netmask
Interface:
IP address
Netmask
Default gateway
47.1.1.1
/29
47.1.3.1
/29
-
-
-
-
-
-
47.1.1.5
/29
47.1.1.1
47.1.1.128
/32
47.1.1.129
/32
-
Yes
Yes
-
0.0.0.0
0.0.0.0
-
Yes
Yes
-
0.0.0.0
0.0.0.0
-
Circuitless IP/ NE-IP:
IP address
Netmask
2 Set up IP routing
Global OSPF enable
OSPF area
Ethernet OSPF enable
OSPF area
OME6500
H
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-81
DCN example 11 - Using VC12 management channels through OM4000
network to reach remote OME6110 network elements in SNCP ring with
OM4000 and legacy OSI network elements. Transparent DCC used to
provided resilient OSI communications.
In this example (see Figure 10-24 on page 10-82 and Figure 10-25 on page
10-83), VC12 management channels are used to establish communication
between the external DCN and the OME6110 network element in a SNCP ring
of OME6110, OM4000 and legacy OSI network elements.
Note: This example is only applicable to SDH networks, as VC12
management channels are currently supported only for OME6110 network
elements provisioned in SDH mode.
Dual OM4000 network elements are connected to the external DCN via an OSI
only enabled port and act as the GNEs for the other OM4000 and legacy OSI
network elements.
Data communication to the remote subtending OME6110 network elements is
achieved using VC12 management channels through the OM4000 network
and are directly terminated on the routers. In order to provide resilient data
communication against any fiber breaks in the OME6110 system, two VC12
management channels are required from the routers to two OME6110 network
elements on the ring. Transparent DCC is provisioned on the OME6110
network elements to provide resilient data communications between the
OM4000 and the OSI legacy equipment.
Note: OSPF routing protocol will be used on the VC12 management
channels to the DCN routers.
The VC12 management channel can be terminated on a physical E1 interface
on the external DCN router. An E1 connection must be provisioned from the
OM4000 GNE to the router.
DCN provisioning details
Table 10-29 on page 10-83, Table 10-30 on page 10-84 and Table 10-31 on
page 10-85 detail the DCN parameters for the DCN example 11 configuration.
Note: For parameters not listed, use the default settings.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-82 Appendix A: Data communications planning
Figure 10-24
DCN example 11 - VC12 management channels to remote OME6110 NEs in SNCP ring with OM4K
and legacy OSI network elements
R1
OMEA
IP
R3
R2
IP and
OSI DCN
OSI area
e.g. 0002
OSI (4K)
OME
61x0
A
OME
61x0
B
XXX
D
OM
4000
G
OM
4000
H
OM
4000
F
MS DCC
XXX
E
OME
61x0
C
Packets routed using IS-IS
Legend
=
=
=
=
=
=
=
=
=
OME 61x0 =
iIS-IS/OSI/LAPD/DCC
iIS-IS/IP/PPP/DCC
OSPF/IP/PPP/DCC
OSPF/IP/PPP/VC12 MGMT
OSPF/IP/PPP/E1 MGMT
IP/GRE/OSI
OSI
Transparent DCC (Overhead Tunnel)
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-83
Figure 10-25
DCN example 11 - IP logical view
OSPF area 0.0.0.0
OMEA
OSPF area 0.0.0.1
Legend
= IP connection
= OSPF routing between NEs
Table 10-29
DCN example 11 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
192.168.1.254
/24
-
192.168.1.254
/24
-
192.168.1.254
/24
-
47.1.3.65
/32
47.1.3.66
/32
47.1.3.67
/32
No
No
No
-
-
-
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
2 Set up IP routing
Ethernet OSPF enable
OSPF area
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-84 Appendix A: Data communications planning
Table 10-29 (continued)
DCN example 11 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
OME6110 C
VC12
1508
PPP, HDLC Framing
Enable
0.0.0.1
VC12
1508
PPP, HDLC Framing
Enable
0.0.0.1
VC12
1508
PPP, HDLC Framing
Enable
0.0.0.1
VC12
1508
PPP, HDLC Framing
Enable
0.0.0.1
VC12
1508
PPP, HDLC Framing
Enable
0.0.0.1
VC12
1508
PPP, HDLC Framing
Enable
0.0.0.1
STM-1-3-1
STM-1-3-2
DCC_M
STM-1-3-1
STM-1-3-2
DCC_M
STM-1-3-1
STM-1-3-2
DCC_M
3 Set up VC12 Management Channels
MGMT-1:
Type
MTU
Layer 2 Protocol
OSPF
OSPF area
MGMT-2
Type
MTU
Layer 2 Protocol
OSPF
OSPF area
4 DCC Overhead Tunnel
Source Port:
Destination Port:
Overhead Byte
Table 10-30
DCN example 11 - OSI NE and OM4000 DCN provisioning details
Parameters
NE D
NE E
OM4000 F
OM4000 G
OM4000 H
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
IS-IS
IS-IS
IS-IS
IS-IS
IS-IS
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1 Set up IP address
Interface:
IP address
Netmask
Interface:
IP address
Netmask
Default gateway
Circuitless IP/ NE-IP:
IP address
Netmask
2 Set up IP routing
Global OSPF enable
OSPF area
Ethernet OSPF enable
OSPF area
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-85
Table 10-30 (continued)
DCN example 11 - OSI NE and OM4000 DCN provisioning details
Parameters
NE D
NE E
OM4000 F
OM4000 G
OM4000 H
Interface 1:
S-5-1
S-5-1
S-5-1
S-5-1
S-5-1
Protocol
IP MTU
LAPD
512
LAPD
512
LAPD
512
LAPD
512
LAPD
512
Interface 2:
S-6-1
S-6-1
S-6-1
S-6-1
S-6-1
Protocol
lP MTU
LAPD
512
LAPD
512
LAPD
512
LAPD
512
LAPD
512
-
-
3 Set up DCC
S-1-1
Interface 3:
Protocol
lP MTU
LAPD
512
-
-
S-2-1
Interface 4:
Protocol
lP MTU
-
-
LAPD
512
-
-
No
No
No
Yes
Yes
4 E1 Connection
E1 Connection to Router
Table 10-31
DCN example 11 - Router and OMEA DCN provisioning details
Parameters
Router 1
Router 2
(see Note)
Router 3
(see Note)
OMEA
47.1.1.1
/29
-
47.1.3.1
/29
-
47.1.3.17
/28
-
47.1.1.5
/29
47.1.1.1
47.1.1.128
/32
47.1.1.129
/32
47.1.1.130
/32
Yes
Yes
Yes
-
0.0.0.0
0.0.0.0
0.0.0.0
-
Yes
No
No
0.0.0.0
-
-
1 Set up IP address
IInterface:
IP address
Netmask
Default gateway
Circuitless IP/ loopback:
IP address
Netmask
2 Set up IP routing
Global OSPF enable
OSPF area
Ethernet OSPF enable
OSPF area
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-86 Appendix A: Data communications planning
Table 10-31 (continued)
DCN example 11 - Router and OMEA DCN provisioning details
Parameters
Router 1
Router 2
(see Note)
Router 3
(see Note)
E1 interface
E1 interface
Enable
1508
0.0.0.1
Enable
1508
0.0.0.1
OMEA
3 Set up E1 interface
Interface 1:
OSPF
MTU
OSFP area
-
-
Note: This solution was validated with a Cisco Router.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-87
DCN example 12 - Using E1 and VC12 management channels to reach
remote OME6110 network elements in SNCP ring with OM4000 and legacy
OSI network element. Transparent DCC used to provided resilient OSI
communications.
In this example (see Figure 10-26 on page 10-88 and Figure 10-27 on page
10-89), E1 and VC12 management channels are used to establish
communication between the external DCN and the OME6110 network
element in a SNCP ring of OME6110, OM4000 and legacy OSI network
elements.
Note: This example is only applicable to SDH networks, as E1 and VC12
management channels are currently supported only for OME6110 network
elements provisioned in SDH mode.
The OM4000 network element is connected to the external DCN via two paths.
An OSI connection to the OSI router, and an E1 connection to the IP router.
The OM4000 acts as the GNE for the legacy OSI network element.
Data communication to the OME6110 GNE is achieved using direct E1
management channel to the external DCN router. Connectivity to the remote
OME6110 is achieved using a mix of E1 and VC12 management channels
through the OM4000 and legacy OSI network elements. In order to provide
resilient data communication against any fiber breaks in the OME6110 system,
management channels are required from the routers to both OME6110
network elements on the ring. Transparent DCC is provisioned on the
OME6110 network elements to provide resilient data communications
between the OM4000 and the OSI legacy equipment.
Note: OSPF routing protocol will be used on the E1 and VC12
management channels.
The VC12 management channel can be terminated on a physical E1 interface
on the OSI network element. An E1 connection must be provisioned from the
OM4000 GNE to the router.
DCN provisioning details
Table 10-32 on page 10-89, Table 10-33 on page 10-90 and Table 10-34 on
page 10-91 detail the DCN parameters for the DCN example 12 configuration.
Note: For parameters not listed, use the default settings.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-88 Appendix A: Data communications planning
Figure 10-26
DCN example 12 - E1 and VC12 management channels to remote OME6110 NEs in SNCP ring with
OM4K and legacy OSI network elements
R1
OMEA
IP
R2
R3
IP and
OSI DCN
OSPF area
0.0.0.1
OSI (4K)
OME
61x0
A
MS DCC
XXX
C
OM
4000
D
OME
61x0
B
Legend
=
=
=
=
=
=
=
=
=
OME 61x0 =
iIS-IS/OSI/LAPD/DCC
iIS-IS/IP/PPP/DCC
OSPF/IP/PPP/DCC
OSPF/IP/PPP/VC12 MGMT
OSPF/IP/PPP/E1 MGMT
IP/GRE/OSI
OSI
Transparent DCC (Overhead Tunnel)
Static IP route/IP/PPP/DCC
OME6110 or OME6130
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-89
Figure 10-27
DCN example 12 - IP logical view
OMEA
OSPF area 0.0.0.0
OSPF area 0.0.0.1
Legend
=
=
=
=
IP connection
OSPF routing between NEs
iISIS routing between NEs
Static/Default routing
Table 10-32
DCN example 12 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
192.168.1.254
/24
-
192.168.1.254
/24
-
47.1.3.65
/32
47.1.3.66
/32
No
No
-
-
1 Set up IP address
LAN-1-5 port:
IP address
Netmask
Default gateway
Router ID:
IP address
Netmask
2 Set up IP routing
Ethernet OSPF enable
OSPF area
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-90 Appendix A: Data communications planning
Table 10-32 (continued)
DCN example 12 - OME6110 DCN provisioning details
Parameters
OME6110 A
OME6110 B
3 Set up E1 and VC12 Management Channels
MGMT-1:
Type
MTU
Layer 2 Protocol
OSPF
OSPF area
E1
1508
PPP, HDLC Framing
Enable
0.0.0.1
VC12
1508
PPP, HDLC Framing
Enable
0.0.0.1
E1
1508
PPP, HDLC Framing
Enable
0.0.0.1
VC12
1508
PPP, HDLC Framing
Enable
0.0.0.1
STM-1-3-1
STM-1-3-2
DCC_M
STM-1-3-1
STM-1-3-2
DCC_M
MGMT-2
Type
MTU
Layer 2 Protocol
OSPF
OSPF area
4 DCC Overhead Tunnel
Source Port:
Destination Port:
Overhead Byte
Table 10-33
DCN example 12 - OSI NE and OM4000 DCN provisioning details
Parameters
NE C
OM4000 D
-
-
-
-
-
-
-
-
-
-
IS-IS
IS-IS
-
-
-
-
-
-
1 Set up IP address
Interface:
IP address
Netmask
Interface:
IP address
Netmask
Default gateway
Circuitless IP/ NE-IP:
IP address
Netmask
2 Set up IP routing
Global OSPF enable
OSPF area
Ethernet OSPF enable
OSPF area
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-91
Table 10-33 (continued)
DCN example 12 - OSI NE and OM4000 DCN provisioning details
Parameters
NE C
OM4000 D
Interface 1:
S-5-1
S-5-1
Protocol
IP MTU
LAPD
512
LAPD
512
Interface 2:
S-6-1
S-6-1
Protocol
lP MTU
LAPD
512
LAPD
512
No
Yes
3 Set up DCC
4 E1 Connection
E1 Connection to Router
Table 10-34
DCN example 12 - Router and OMEA DCN provisioning details
Parameters
Router 1
Router 2
(see Note)
Router 3
(see Note)
OMEA
47.1.1.1
/29
-
47.1.3.1
/29
-
47.1.3.17
/28
-
47.1.1.5
/29
47.1.1.1
47.1.1.128
/32
47.1.1.129
/32
47.1.1.130
/32
Yes
Yes
Yes
-
0.0.0.0
0.0.0.0
0.0.0.0
-
Yes
No
No
0.0.0.0
-
-
E1 interface
E1 interface
-
Enable
1508
Enable
1508
-
-
0.0.0.1
0.0.0.1
-
1 Set up IP address
IInterface:
IP address
Netmask
Default gateway
Circuitless IP/ loopback:
IP address
Netmask
2 Set up IP routing
Global OSPF enable
OSPF area
Ethernet OSPF enable
OSPF area
3 Set up E1 interface
Interface 1:
OSPF
IP MTU
Note: This solution was validated with a Cisco Router.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-92 Appendix A: Data communications planning
IP networks, addressing, and masks
This section briefly explains the concepts of IP (Internet Protocol, version 4)
addressing and uses examples from DCN to illustrate.
• Every interface within an IP system must have a unique IP address (four
bytes expressed in decimal and separated by dots [for example,
192.168.12.43]). For more information on this notation, refer to Dotted
decimal notation for IP addresses on page 10-93.
• The IP addresses available for the system are divided into networks and
further subdivided into subnetworks.
• Devices must be grouped together such that they are directly connected
only to other devices with IP addresses conforming to the same
subnetwork addresses.
• There are two groups of networks: public and private networks.
— Public networks are those networks which can be connected to the
Internet; therefore they are accessible from any device outside that
network, as long as this device is also connected to the Internet.
— Private networks are isolated from the outside world; therefore they
cannot be connected to the Internet, and as such they are not accessible
by any device that does not belong to the same network. Well-defined
ranges of addresses are reserved for private networks.
– One of the address ranges available for private networks is
192.168.x.y (x = 0 to 255, y = 0 to 255, which is the decimal
representation of an 8-bit binary number); ‘x’ is the part of the IP
address which is available for the network address. For example,
192.168.1.0, 192.168.2.0, and 192.168.3.0 are three different
network addresses. Every device or interface connected to network
192.168.1.0 must have an IP address that is 192.168.1.y, where ‘y’
is the part of the IP address which is available for both the
subnetworks and the host ID (identifier).
• The subnetwork mask identifies the number of bits allocated to the host ID
and the number allocated to the subnetwork.
• When subnetting a network, two addresses are not available: those
identified by all ones (used as a broadcast address), and all zeros (reserved
by convention as it is used to identify the network).
• As for subnets, host addresses of all ones (broadcast) and all zeros (by
convention) are not available.
• The network designer will decide how many bits define the subnetwork
and how many define the host ID, according to the actual and possible
future network architecture.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-93
It is important to note that the original distinction of addresses between classes
A, B, and C did not allow the network designer to vary the length of the
subnetwork mask once an IP address was assigned. In fact, classes A, B, and
C defined a rigid scheme for assigning the number of bits which identify the
networks, and those which identify the host ID, regardless of the network
designer’s needs. For its intrinsic limits, the notation for classes A, B, and C is
no longer used.
The next section of this information shows the bit significance of the dotted
decimal notation.
Dotted decimal notation for IP addresses
An IP address is 32 bits long. To aid memory of this string of digits, the address
is split into 4 groups of 8 bits each. These are represented by a decimal number
between 0 and 255 for ease of display. The decimal number has no other
significance.
The decimal number represented by the eight bits can be determined by
looking up the decimal value of each bit and then simply adding them up:
•
•
•
•
•
•
•
•
00000001 is represented by 1
00000010 is represented by 2
00000100 is represented by 4
00001000 is represented by 8
00010000 is represented by 16
00100000 is represented by 32
01000000 is represented by 64
10000000 is represented by 128
Example: 10010001
• 10000000 is represented by 128
• 00010000 is represented by 16
• 00000001 is represented by 1
• Total 145
An IP address contains a 32-bit address field and a 32-bit subnet mask. The
mask defines which part of the address is a network address and which is a
device address. The mask thus allows a router to decide whether the address of
the packet is destined for one of the subnets to which it is connected. For
example:
An address of 47.9.64.172 has a mask of 255.255.240.0; the mask is
AND’ed with the address:
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-94 Appendix A: Data communications planning
Address of packet is:
00101111.00001001.01000000.10101100
Mask is:
11111111.11111111.11110000.00000000
This means that the network part of the address is:
00101111.00001001.01000000.00000000
The device part of the address is:
00000000.00000000.00000000.10101100
occupying the last 12 bits.
CIDR (Classless Inter-Domain Routing) addresses represent masks in a
different way. A CIDR address is defined by a starting address and a mask
which defines the size of the address allocation. For example:
An allocation of addresses in the range 196.0.16.0 to 196.0.31.255 can be
represented by:
196.0.16.0/20 (see note)
where the 20 is a mask of 20 contiguous 1 bits.
Start address is:
11000100.00000000.00010000.00000000
End address is:
11000100.00000000.00011111.11111111
And the mask is:
11111111.11111111.11110000.00000000
The last 12 bits are available to the user to use as subnet address and device
address.
Note: This notation is conventional for CIDR addresses. However, the
method in which an IP address is configured can vary according to the
router where it is performed. For example, the IP address notation
196.0.16.0/20 can be used to configure a Cisco router, whereas Nortel
Networks routers require the full notation 196.0.16.0 with the subnetwork
mask 255.255.240.0. There is no substantial difference between these two
methods.
Circuitless IP interface
A circuitless IP interface is a virtual interface that exists in software only. The
special property of this interface is that it always exists and is therefore always
included in the routing tables. Ethernet and serial interfaces cease to exist if a
connector falls out, or if the device at the other end of the cable fails for any
reason. The interface then shuts down and is removed from the routing tables.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-95
Note that circuitless IP is a Bay term; Cisco uses the term ‘loopback’ for these
interfaces. Having an interface that always exists within a router is very useful
for the following reasons:
1 If a tunnel is set up between two router interfaces and one of the interfaces
fails, the tunnel fails. However, when the tunnel is set up between two
circuitless IP interfaces, if the normal route fails, the tunnel is re-routed if
another route exists and does not fail.
2 If during a Telnet session on a router the interface to which the session is
connected goes down, then the session is lost. Another connection via the
IP address of an alternative interface must be made. If Telnet sessions are
set up to connect to the router using the circuitless IP interface, then loss
of one interface is not a problem, providing the router has at least one
working IP interface.
3 Other interfaces can be referenced to the circuitless IP interface. This is
known as an unnumbered interface. This applies only to point-to-point
interfaces (that is, not an Ethernet port). This reduces the number of IP
addresses needed.
Note: It is more difficult to find faults in a network with an unnumbered
link, and topologies from some network management systems are easier to
follow with unnumbered serial links. The use of unnumbered links is still
permissible where sufficient IP addressing space is not available.
4
The circuitless IP interface identifies a router for OSPF (Open Shortest
Path First), tunnelling, and management.
IP routing protocols
The primary function of IP, which resides at the network layer (3) of the OSI
(Open Systems Interconnect) model, is to receive data from the higher layer
protocols (TCP [Transmission Control Protocol] or UDP [User Datagram
Protocol] layers) on a source host, create a datagram and route the datagram
through a network to a destination host. Secondary functions of IP include
fragmentation and reassembly of the datagram, and packet lifetime control.
The most important IP routing protocols are explained in the following
sections.
ARP
ARP (Address Resolution Protocol) is used to map IP addresses to LAN
(Local Area Network) hardware addresses. When a host wishes to send a
packet to a host on another network, it sends the packet to its gateway for
forwarding. It can also do the same for a packet destined for a host within the
same network but it leads to excessively high traffic levels, especially if a large
number of hosts are on the LAN. Therefore, in order to reduce the traffic on a
LAN, a node uses ARP with another node when it determines that the
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-96 Appendix A: Data communications planning
destination address is on a directly attached network. The node can determine
if the host is local by comparing the network portion of its own IP address
(including the subnet) with the target address.
Therefore, in order to avoid using the gateway, the originating host needs to
determine the destination host’s local data link layer address. It achieves this
by sending out an ARP request message containing its own IP address and data
link layer address, and the IP address of the destination host. This message is
sent via the gateway. The destination host then responds with an ARP reply
message containing its own data link layer address and uses the originating
host’s data link layer address as the destination address. Thus the reply does
not need to go via the gateway. The originating host and destination host store
the learned network and data link layer address pairing in their ARP caches for
future use, thus avoiding the use of the gateway altogether. The rest of the hosts
on the LAN build up similar caches, thus reducing LAN traffic.
OSPF
OSPF (Open Shortest Path First) is an open protocol, as defined in Request
For Comments (RFC) 1247. It is based on the Dijkstra’s ‘Shortest Path First’
algorithm, which is a link state routing mechanism.
In an OSPF network, each router maintains a link-state database that describes
the topology of the autonomous system (AS). The database contains the local
state for each router in the AS, including the router’s usable interfaces and
reachable neighbors. Each router periodically checks for changes in its local
state and shares any changes detected by flooding link-state advertisements
(LSAs) throughout the AS. Routers synchronize their topological databases
based on the sharing of information from LSAs.
From the topological database, each router constructs a shortest-path tree, with
itself as the root. The shortest-path tree gives the optimal route to each
destination in the AS. Routing information from outside the AS appears on the
tree as leaves. OSPF routes IP traffic based solely on the destination IP address
and subnet mask, and IP Type of Service (TOS) contained in the IP packet
header.
OSPF is designed specifically for use on larger networks, providing several
features to reduce the amount of traffic and processing overhead associated
with the routing protocol. Amongst these features are the ability to segment a
large network into a number of areas, and route summarization, a technique
which greatly reduces the volume of route advertisement traffic where the
addressing scheme is hierarchical.
The manner in which a network is segmented into areas is governed by strict
rules. There is a core area—known as the backbone area—which is area
0.0.0.0, sometimes referred to as area 0. All other areas are connected directly
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-97
to the backbone area, or, where this is not possible, connected indirectly using
a ‘virtual link’ or tunnel. See Figure 10-28 on page 10-100.
The topology of each OSPF area is invisible to entities outside the area. This
area partitioning system speeds up routing, because all packets with
destinations within an area are contained within that area; packets destined for
another area are sent to the backbone area for redirection.
The rules for area use within OSPF networks contrast with the way areas are
implemented in OSI in the following ways:
• There is no requirement for a backbone area within OSI.
• The border between OSI areas is between routers (that is, a OSI router can
only reside in one area), whereas the border between OSPF areas runs
through a router (that is, an OSPF router may be in more than one area).
Interfacing OSPF networks with non-OSPF networks
The DCN design does not support running other IP routing protocols within
the OSPF network. However, there are applications where non-OSPF is the
only protocol available and these networks must be able to send to and receive
packets from the OSPF network.
There are two ways in which this can be done:
1 static routes (see Figure 10-30)
2 redistribution.
Redistribution
Redistribution gives visibility of both networks using dynamic routing. Routes
from one area to subnets in the other are costed within limitations. There is no
easy way for non-OSPF to interpret OSPF metrics and vice versa.
• The boundary router advertises all OSPF routes into the non-OSPF
network with a cost of one hop.
• Redistributing non-OSPF routes into the OSPF network is more complex.
To a router within the OSPF network, networks in the non-OSPF network
within one hop of the boundary router have the same cost as the cost of
reaching the boundary router. To a router within the OSPF network,
networks in the non-OSPF network beyond one hop of the boundary router
have a cost equal to the number of hops required in the non-OSPF network.
The cost to reach the boundary router within the OSPF area is considered
to be zero. How this is implemented varies between router manufacturers.
A router (boundary router) must always be used as the interface between the
two networks. There may be more than one router performing this role.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-98 Appendix A: Data communications planning
Implementing OSPF in a network
This section covers issues that the implementer of an OSPF network needs to
be aware of.
Terms
Some terms associated with OSPF are:
• Costs Routes have a cost associated with them. The higher the cost the less
favourable the route. OSPF has a number of metrics which are converted
with algorithm into a cost.
• Policy filters This parameter only applies when an OSPF network uses
external routes. An announce filter acts on the outward advertisements
form the OSPF area and the accept filter acts on inward advertisements. As
the LSPs are modified by the filter and the resultant used to produce a
routing table, it follows that policy filters need to be applied to all routers
in the OSPF network and not just to the boundary router.
•
•
•
•
•
•
•
•
•
•
•
•
Link state is the status of a link between two routers.
Cost of a link is computed from bandwidth, real cost, availability,
reliability and other link metrics.
OSPF area is a collection of connected routers which exchange link state
updates.
Adjacencies database lists all a router’s neighbours.
Link State Database is a list of link states from all other routers in the
OSPF area. All routers have identical link state databases.
OSPF routing table is produced from the OSPF link state database.
Routing table (forwarding table). The best routes are chosen from all
protocol routing tables. Note that each router has a different routing table.
Backbone area Area to which all other OSPF areas are connected, either
directly or via a virtual link. It is referred to as area 0.0.0.0 or area 0.
Standard area Area which is not the backbone area but which receives all
link state updates from external networks.
Stub areas These are areas which can have more than one interface, but by
definition do not carry transit data and do not receive link state updates
from external networks. All routers in a stub area must be set to be stub
routers. How this is implemented varies between router manufacturers.
Totally stubby areas Stub areas which do not receive summary LSAs.
NSSA (Not So Stubby Areas) Stub areas which receive certain link state
updates from external networks.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-99
•
•
•
•
Router ID This is the number by which each router is known to OSPF. On
a Bay router the default is the IP address of the first configured interface.
On Cisco the default is the highest configured IP address. On both routers
it should be manually configured to be the same as the circuitless
IP/loopback address.
Border router A router which is in the backbone area and one or more
other OSPF areas.
Boundary router (or ASBR—Autonomous System Boundary Router) A
router which is the gateway between an OSPF network and another
network which uses a separate routing mechanism, including static routes.
Designated router Link state routing protocols have an inherent problem
when a number of routers exist on the same LAN. The solution is for a
router to be elected as a proxy for all the routers on the LAN, this is known
as a designated router (DR). The DR creates a dummy routing entity with
which all routers on the LAN form an adjacency. There are no other
adjacencies formed on the LAN. Thus, routers on a LAN will have only
one link on the LAN, rather than one for each of the other routers on the
LAN. This means that the number of links on a LAN with n routers is
reduced from n * (n - 1) to n * 2:
— A router with a priority of 0 never becomes DR.
— If a router with a higher priority connects to the network there is no
re-election.
— Changing router priorities does not cause a re-election.
— Changing router IDs does not cause a re-election.
•
OSPF multicasts. Packets sent out with 224.0.0.5 are sent to all OSPF
routers. Packets sent out with 224.0.0.6 are sent to all OSPF designated
routers.
Topology considerations
An OSPF network has to be planned out in areas to take full advantage of the
protocol.
With OSPF packets destined for an area outside the current area are sent to
area 0. Thus it may be inferred that all areas must have a connection to area 0.
There may be more than one connection between an area and area 0 but there
must be no inter-area connections.
It can be concluded that OSPF networks are tree structures which lend
themselves to hierarchical addressing schemes using variable length subnet
masks.
OSPF places demands upon a routing processor. It is recommended that no
more than 50 OSPF routers be placed within an OSPF area.
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-100 Appendix A: Data communications planning
The designated router on a LAN in a network running OSPF has a very high
processor utilization. It may be that some routers are unsuitable for this role
and so should be allocated a priority of 0. If it is not possible to have an area
connected directly to area 0, a virtual route may be used as in Figure 10-28
(dashed line).
Figure 10-28
OSPF areas
Area 1
Area 2
Area 0
(Backbone)
Area 3
virtual route
Area4
Area 6
AUTONOMOUS SYSTEM (AU)
Wherever possible the DCN network should be fitted into one area (area 0).
This gives the benefit of OSPF speed and versatility without the restrictions
on topology.
Basic OSPF configuration steps for each interface are:
1 Enable OSPF.
2 Define an OSPF area.
3 Define interface type.
4 Define interface metrics.
Other parameters may need to be changed.
Advantages of OSPF
OSPF is link state technology as opposed to the distance vector technology and
OSPF addresses the requirements of large scalable networks. Issues addressed
by OSPF are:
• Speed of convergence With OSPF convergence is quicker because routing
changes are flooded throughout the network and new routing tables
computed in parallel.
•
Variable length subnet masks OSPF supports variable subnet masking
and advertises varying levels of subnets.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-101
•
Route summarization OSPF supports route summarization which is the
consolidation of multiple routes into one single advertisement. It requires
a hierarchical network but has the advantage of confining topology
changes to within an area and so significantly reduces the workload on
routers in other areas.
Figure 10-29
Route summarization
.
Route summarization
140.150.10.0/24
Area Border
Router
140.150.10.0/24
140.100.10.0/24
140.100.20.0/24
140.100.30.0/24
140.100.40.0/24
140.100.0.0/16
Route summarization allows the right hand networks to be
advertised using one update
•
•
•
•
Supernetting Supernetting comes from the introduction of CIDR. Address
space is allocated without class as a contiguous number of class C
addresses. For example, an allocation of addresses in the range 196.0.16.0
to 196.0.31.255 could be represented by 196.0.16/20. Such an entry in a
routing table is referred to as a supernet. Subnetting is used to achieve route
summarization and cannot be used with routing protocols such as RIP
which categorize IP addresses by class.
Network reachability There is no path limit with OSPF.
Bandwidth considerations OSPF just sends out link state updates when
they occur, with a maximum interval of 30 minutes.
Route selection OSPF determines a best route using the concept of cost.
Each interface configured with OSPF has a metric parameter, whose value
has been derived from the formula 108/interface speed (however, it is at the
discretion of the engineer to change it, if required—for example when the
link is busy). According to the formula, some values are:
— Ethernet 100BaseTX: 1
— Ethernet 10BaseT: 10
— Serial at 2 Mbit/s: 48
— Serial at 64 kbit/s: 1562
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-102 Appendix A: Data communications planning
Route preference
All routing protocols are assigned a preference which allows the router to
select routes when different protocols each report a path to the same network.
It could be considered as a measure of believability. The exact ranking of
protocols depends on the router manufacturer, but link state routing protocols
(for example, OSPF) are considered more reliable than distance vector
routing protocols (for example, RIP). A static route should be assigned a high
preference and a default route a low one.
Static and default routes
Static routes are manually configured on a router in contrast to routes learned
via a routing protocol. Static routes are permanent and remain in the routing
table even though an interface associated with the route goes down. They are
most commonly used for:
• Defining routes to use when two autonomous systems must exchange
routing information, rather than having entire routing tables exchanged.
Often subnetworks linked to a corporate network do not wish to receive
routing updates but require some facilities provided by the corporate
network. The intermediate router on the border would advertise to the
corporate network that it had a route to the subnetwork.
• A network which has dial-on-demand links. Routing updates passing over
this link would keep the link up permanently. A static route ensures that the
link is only enabled when traffic data requires the link to reach its
destination.
Routers must be configured to listen to and redistribute static routes.
Default routes are a form of static routes in that they provide a catch-all for
destinations not contained in routing tables. In effect they provide a static
route to a large network rather than a specific IP address or subnetwork. In the
case of the subnetwork attached to a corporate network, the intermediate
router on the border has a default route to the corporate network advertised
into the subnetwork.
Figure 10-30 shows an example of the way that static routes and default
routes are used.
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Appendix A: Data communications planning 10-103
Figure 10-30
Default and static routes
Intermediate router
Corporate Network
and Internet gateway
Subnetwork
47.132.32.0/20
default route to
corporate network
route advertisement
(47.132.32.0 mask 255.255.240.0)
static route
to subnetwork
route advertisement
(0.0.0.0 mask 0.0.0.0)
Planning Guide NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
10-104 Appendix A: Data communications planning
Optical Multiservice Edge 6110
NT6Q92AD Rel 2.2 Issue 1 Standard May 2007
Nortel
Optical Multiservice Edge
6110
Planning Guide
Copyright  2007 Nortel Networks, All Rights Reserved
This document is protected by copyright laws and international
treaties. All information, copyrights and any other intellectual
property rights contained in this document are the property of
Nortel Networks. Except as expressly authorized in writing by
Nortel Networks, the holder is granted no rights to use the
information contained herein and this document shall not be
published, copied, produced or reproduced, modified, translated,
compiled, distributed, displayed or transmitted, in whole or part,
in any form or media.
This information is provided “as is”, and Nortel Networks does not
make or provide any warranty of any kind, expressed or implied,
including any implied warranties of merchantability,
non-infringement of third party intellectual property rights, and
fitness for a particular purpose. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use
the information contained herein.
Nortel, the Nortel logo, the Globemark, are trademarks of Nortel
Networks.
NT6Q92AD
Standard Rel 2.2 Issue 1
May 2007
Printed in Canada