NTRN10BC

NTRN10BC
Nortel
Optical Multiservice Edge 6500
Planning Guide
Standard Release 1.2 Issue 1 April 2005
What’s inside...
Introduction
Feature overview
Applications and upgrades
Hardware description
User interface description
OAM&P description
Technical specifications
Ordering information
Technical assistance
Appendix A: Data communications planning
*N0029999*
Copyright  2004-2005 Nortel Networks, All Rights Reserved
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to
its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third
parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except
as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
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.
Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
Printed in Canada
iii
Publication history 0
April 2005
Standard Issue 1.
Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

iv Publication history
Optical Multiservice Edge 6500 NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005
v
Contents 0
About this document xiii
Introduction 1-1
OME6500 applications 1-4
OME6500 service interfaces 1-6
Optical interfaces 1-6
Distributed service modules 1-8
Services transport 1-8
Point-to-point optical broadband services 1-9
Transparent services 1-10
TDM switching 1-10
Layer 2 switching 1-11
Next generation RPR 1-11
Network management 1-12
Key features and benefits 1-13
Feature overview 2-1

Physical description 2-12
Bay/rack configurations 2-12
Interface circuit packs 2-17
Configurations 2-17
Connection management 2-18
Service mapping 2-19
Traffic protection 2-19
Equipment protection 2-20
Synchronization 2-21
Alarm and events 2-21
Performance monitoring 2-22
Operational measurements 2-22
System lineup and testing 2-23
Loopbacks 2-23
Data management 2-23
Autodiscovery 2-23
Security and administration 2-24
Data communication network 2-24
OME6500 management 2-24
Site Manager 2-24
TL1 user interfaces 2-25

vi Contents
Interworking with Nortel portfolio 2-25

DWDM Interworking 2-26
Interoperating with non-Nortel portfolio 2-26
Applications and upgrades 3-1

Unprotected configuration 3-2
1+1/MSP linear 3-3
BLSR/MS-SPRing 3-4
UPSR/SNCP configuration 3-6
Gigabit Ethernet point-to-point application 3-7
Intra-office application 3-9
OMX applications 3-10
Network sites 3-10
DWDM configurations 3-11
Common Photonic Layer applications 3-14
Network reconfiguration 3-14
Upgrade support 3-15
Software 3-15
Hardware 3-15
3-15
Hardware description 4-1

Hardware architecture 4-2
Shelf assemblies 4-2
Cooling configurations 4-5
Breaker interface panel (optional) 4-9
OME6500 BIPs 4-9
DSM BIP 4-15
Shelf 4-17
Backplane 4-18
Shelf ID module 4-19
Shelf ESD interface 4-19
Access panel 4-19
Electrical interface area 4-21
Optical/front electrical shelf 4-21
Optical/rear electrical shelf 4-22
Maintenance interface card 4-23
Power input card 4-24
Shelf processor 4-25
Cross-connect circuit packs 4-27
Synchronization 4-29
Database storage 4-30
Synchronization hardware 4-30
Interface circuit pack descriptions 4-31
1xOC-192/STM-64 circuit pack 4-34
8xOC-3/12/STM-1/4 circuit pack 4-38
4xGE EPL circuit pack 4-39
63xE1 working and protection circuit packs 4-42
Contents vii
24xDS3/EC-1 working and protection circuit packs 4-44

Filler card 4-45
DS1 service module shelf 4-45
Equipping rules 4-46
Multiple IS 4-46
DSM 84xDS1 termination module (TM) 4-48
I/O and protection hardware 4-49
E1 I/O panels and protection hardware 4-49
DS3/EC-1 I/O panels 4-51
Fiber/cable routing channel 4-53
Shelf cover 4-54
Optical multiplexer 4-55
Fiber manager 4-56
User interface description 5-1

OME6500 Site Manager 5-1
TL1 interface 5-2
OAM&P description 6-1

UPSR/SNCP traffic protection 6-3
Provisioning UPSR/SNCP traffic protection 6-4
UPSR/SNCP protection switch criteria 6-5
DS1 service module support 6-6
Equipment/facility provisioning 6-6
Cross-connect provisioning 6-8
Protection provisioning 6-9
DS3/EC-1 support 6-10
Facility provisioning 6-10
Cross-connect provisioning 6-10
Protection provisioning 6-11
Gigabit Ethernet drop-and-continue 6-11
International gateway 6-15
Performance monitoring enhancements 6-17
FTP of performance monitoring data 6-17
Support for DS1, DS3, and EC-1 performance monitoring 6-17
Time of day synchronization 6-17
Alarm/event enhancements 6-18
Increased VT1.5/VC12 alarm support 6-18
Support for DS1, DS3, and EC-1 alarms 6-18
Communications enhancements 6-19
Nested Telnets 6-19
OME6100 interworking 6-19
OSI ping 6-19
User interface enhancements 6-19
Site Manager enhancements 6-19
TL1 shelf AID extension 6-19
Commissioning and testing 6-20
Commissioning Assistant Tool 6-20
Global support 6-20
Equipment management 6-22

viii Contents
Managing provisionable equipment 6-24

Facility management 6-25
Managing facilities 6-26
Loopbacks 6-27
Synchronization management 6-29
Timing generation 6-29
Timing distribution 6-31
Synchronization operating modes 6-32
Synchronization status messages 6-33
Viewing and management 6-34
Synchronization protection 6-36
Stratum clocks 6-37
Synchronization hierarchy 6-37
Hierarchy violations 6-39
Timing loops 6-39
Building-integrated timing supply 6-39
Mixed timing engineering guidelines 6-40
Circuit pack compatibility 6-42
OME6500 connection types 6-44
Supported unidirectional configurations 6-47
Payload interconnection 6-47
Time slot assignment (TSA) 6-50
Time slot interchange (TSI) 6-50
Connection management application 6-51
Cross-connect circuit pack protection 6-52
63xE1 and 24xDS3/EC-1 circuit pack protection 6-53
Provisioning 1:N equipment configurations 6-53
1:N protection switch criteria 6-54
1:N protection exerciser 6-55
84xDS1 TM circuit pack protection 6-56
Traffic Protection application 6-59
1+1/MSP linear traffic protection 6-59
Provisioning MSP linear protected connections 6-59
1+1/MSP linear protection switch criteria 6-60
2-Fiber BLSR/MS-SPRing traffic protection 6-61
Provisioning 2-Fiber BLSR/MS-SPRing traffic protection 6-63
BLSR/MS-SPRing protection switch criteria 6-64
STS/VC BLSR/MS-SPRing with VT/LO VC assignment 6-65
Traffic protection exerciser 6-66
Unprotected connections 6-67
Provisioning unprotected connections 6-67
OME6500 OAM comms 6-68
Interfaces 6-69
OAM comms management 6-70
OAM comms routing 6-71
TID address resolution protocol (TARP) 6-71
DSM OAM comms 6-72
Alarm and event management 6-72
Contents ix
OME6500 local alarm indications 6-73

Site Manager alarm management/surveillance 6-73
PM functions 6-76
PM parameters 6-77
PM time intervals 6-79
PM enable/disable 6-79
PM inhibition 6-79
PM parameter thresholds and PM profiles 6-79
TCA events 6-80
Operational measurements time interval collection 6-81
Local account user authentication 6-82
Local ‘challenge/response’ user authentication 6-82
Centralized security administration (CSA) 6-83
Centralized user administration and authentication through RADIUS 6-83
Security levels 6-85
Login sessions 6-85
Local password management 6-86
Intrusion attempt handling 6-87
Security log audit trail 6-88
Network element name 6-89
Time date and time setting 6-89
Backing up and restoring the network element database 6-89
Installing Site Manager software 6-90
Installing and upgrading network element software 6-90
Release management 6-91
Upgrade management 6-91
Technical specifications 7-1

Physical specifications 7-2
Weights 7-6
Power specifications 7-7
Connector pinouts 7-10
BIP connector pinouts 7-10
Access panel connector pinouts 7-12
Shelf processor connector pinout 7-15
10/100Base-T RJ-45 pinout 7-16
DSM OAM adapter module 7-16
E1 cable pinouts and assemblies 7-18
Cable assemblies 7-18
Connectors 7-18
E1 I/O panel, interface circuit pack, and connector port mapping 7-18
DS1 cable pinout and assemblies 7-25
DS3/EC-1 cable assemblies 7-27
1xOC-192/STM-64 optical specifications 7-28
8xOC-3/12/STM-1/4 SFP optical specifications 7-32
DSM 84xDS1 TM optical specifications 7-34
4xGE EPL SFP optical specifications 7-35

x Contents
OMX optical specifications 7-36

Electrical specifications 7-36
Environmental specifications 7-38
Operating environment specifications 7-38
Air flow specifications 7-39
Electromagnetic specifications 7-40
Safety specifications 7-41
General commercial and regulatory 7-41
Laser emission 7-41
Power and grounding specifications 7-42
DC input voltage ranges 7-42
Ordering information 8-1

New items in Release 1.2 8-1
Technical assistance 9-1

Technical support and information 9-2
Nortel web site 9-2
Field return information 9-3
Appendix A: Data communications planning 10-1

Public DCN connectivity 10-2
Public IP address model 10-2
Private IP address model 10-3
General DCN provisioning rules 10-4
Gateway network element 10-4
Non-gateway network element 10-6
IP addressing 10-7
DHCP 10-10
LAN ports 10-10
iISIS router 10-11
iISIS circuits 10-12
IP routing table 10-13
Lower layer DCC 10-13
Upper layer DCC 10-14
OSPF router 10-15
OSPF circuits 10-16
GRE 10-16
ARP 10-17
FTP 10-17
PPP 10-18
Serial/RS-232 10-18
Telnet 10-18
OME6500 DCC communications 10-18
OME6500 interworking with IP-managed network elements 10-19
OME6500 interworking with OSI-managed network elements 10-19
DCC protection 10-21
OSI data communications on the OME6500 10-21
DCN design examples 10-22
DCN example 1 - using static routing 10-23
Contents xi
DCN example 2 - using OSPF with two OME6500 gateway network elements in
different OSPF areas 10-27
DCN example 3 - using OSPF with two OME6500 gateway network elements
connected to OSPF backbone 10-31
DCN example 4 - using DCN tunnels 10-35
DCN example 5 - management of Optical Metro 4000 through OME6500 with IP
only external DCN 10-41
DCN example 6 - management of OME6500 through non-OME6500 network
element 10-46
DCN example 7- management of Optical Metro 3500 through OME6500 10-51
DCN example 8 - DCN drops to every OME6500 network element 10-57
DCN example 9 - auto-tunnelling 10-61
DCN example 10 - OME6500/HDX interworking using HDX DCC transparency and
multiple OSI areas 10-64
Dialup connectivity 10-65
Firewalls 10-66
Troubleshooting 10-67
Engineering guidelines 10-68
IP networks, addressing, and masks 10-70
Dotted decimal notation for IP addresses 10-71
Circuitless IP interface 10-73
IP routing protocols 10-74
ARP 10-74
OSPF 10-75
Route preference 10-80
Static and default routes 10-81
Subnetting and supernetting - IP addressing examples 10-82

xii Contents
xiii
About this document 0
This planning guide describes the applications and functionality provided by

the software and hardware of Nortel Optical Multiservice Edge 6500
(OME6500) Release 1.2.
This planning guide covers the following topics:
• Introduction
• Features overview
• Applications, upgrades, and interworking
• Hardware description
• User interface description
• Operations, administration, maintenance and provisioning (OAM&P)
description
• Technical specifications
• Ordering information
• Technical assistance
• Data communications planning
Supported software release

This document supports the software release for OME6500 Release 1.2.
Audience
The following members of your company are the intended audience of this
document:
• planners
• provisioners
• network administrators
• transmission standards engineers
• maintenance personnel

xiv About this document
Optical Multiservice Edge 6500 NTP library

This roadmap identifies the OME6500 library structure and the use of guides
and Nortel technical publications (NTP).
Planning a Network Installing, Managing and Maintaining and Supporting

Commissioning and Provisioning Troubleshooting documentation
Testing a Network a Network a Network for the OME6500
Library
Site Manager for
Optical Multiservice
Edge 6500 R1.2
Planning and
Installation Guide
(NTNM34DC)
Network
Interworking Guide
(NTCA68CA)
About the Installation Security and Performance

OME6500 (323-1851-201) Administration Monitoring
NTP Library (323-1851-301) (323-1851-520)
(323-1851-090) Commissioning
and Testing Provisioning Alarm and
Ordering Information (323-1851-221) and Operating Trouble Clearing
(323-1851-151) Procedures (323-1851-543)
(323-1851-310)
Planning Guide Module
(NTRN10BC) Replacement
Procedures
(323-1851-545)
References
This document refers to the following OME6500 NTPs:
• About the OME6500 NTP Library, 323-1851-090
• Installation, 323-1851-201
• Commissioning and Testing, 323-1851-221
• Security and Administration, 323-1851-301
• Provisioning and Operating Procedures, 323-1851-310
• Performance Monitoring, 323-1851-520
• Alarm and Trouble Clearing, 323-1851-543
• Module Replacement Procedures, 323-1851-545
This document refers to the following OME6500 supporting documentation:

• Site Manager for Optical Multiservice Edge R1.2 Planning and
Installation Guide, NTNM34DC
1-1
Introduction 1-
This chapter provides an overview of the capabilities supported on the Nortel

Optical Multiservice Edge 6500 (OME6500) platform. The chapters that
follow detail the specific features and functionality supported in Release 1.2.
The OME6500 combines and extends the advantages of next generation

SONET/SDH and metropolitan dense wave division multiplexing (DWDM)
platforms for converged time division multiplexing (TDM), data, wavelength,
and transparent services transport over a single consolidated multiservice
optical platform.
The OME6500 epitomizes a new breed of optical networking platforms for

efficiently aggregating, switching, and managing a mix of global services
ranging from lower speed electrical DS1/E1, DS3/EC-1/E3 private line service
through to high-speed optical OC-3/STM-1, OC-12/STM-4, OC-48/STM-16,
OC-192/STM-64 services. The OME6500 is a global platform that can be
deployed in both SONET and SDH environments. SONET and SDH protocols
are supported on the same circuit pack and provisionable through software.
The OME6500 offers:

• next generation data capabilities for both Optical Ethernet services
(10/100Base-T, 100Base-FX, Gigabit Ethernet (GE), and 10 GE) and
Optical Storage connectivity services (Fibre Channel and FICON).
• Layer 2 Service Switch (L2SS) capabilities to help aggregate and switch
Ethernet services. L2SS provides a strong Ethernet services and
infrastructure solution for IP, Ethernet Private LANs, Ethernet VPNs,
Ethernet Virtual Private Lines, Triple Play Services, and Internet access
solutions.
• Resilient Packet Ring (RPR) support which is a ring based technology that
enables bandwidth sharing, high reliability, and network simplicity across
multiple Ethernet ports for efficient transport of packets. L2SS RPR
Ethernet support provides support for private LAN applications and an
efficient Ethernet switched backhaul for Ethernet VPN and IP traffic.
• protocol independent and bit-rate tolerant transparent interfaces to enable
high capacity transparent wavelength services over existing SONET/SDH
infrastructure.

1-2 Introduction
Figure 1-1 provides an illustration of the OME6500 shelf.

Figure 1-1
OME6500 shelf
The OME6500 provides dramatic cost savings for rolling out established
steady revenue generating services as well as supporting emerging broadband
services. The OME6500 realizes significant space and power savings over
currently deployed and available solutions and simplifies network
management operations by integrating multiple network functions into a
single platform, such as:
• broadband service delivery
• access head end consolidation
• next generation digital cross connection application with full
VT1.5/VC-12 connection management
• metropolitan and regional core networking
One of the main benefits of the OME6500 is its ability to facilitate the
widespread deployment of optical broadband services (OBS) through its
embedded OBS service management support capabilities. These applications
are all supported by the OME6500 platform software and are implemented
using the flexible high capacity switching capabilities and the broad selection
of high density service adaptation and line interfaces available.
Introduction 1-3
The OME6500 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 OME6500 further
enhance the dependability of service transport. For access head end
applications, service traffic can either be connected via unidirectional
path-switched ring (UPSR)/subnetwork connection protection (SNCP) or via
protected point-to-point 1+1 connections. Typically, for core networking, a
more efficient and sophisticated bidirectional line-switched ring
(BLSR)/multiplex section shared protection ring (MS-SPRing) or mesh
protection scheme is deployed.
The OME6500 architecture supports a wide range of traffic protection and

restoration schemes including:
• unprotected
• 1+1 protection
• UPSR/SNCP (supports multiple UPSR/SNCP rings on single network
element)
• BLSR/MS-SPRing (supports multiple BLSR/MS-SPRing rings on a single
network element)
• dynamic mesh restoration (control plane)
• shared mesh protection (control plane)
The OME6500 has no predefined aggregate/line and tributary slots, therefore
these protection schemes can be applied flexibly across all slots
(BLSR/MS-SPRing is supported on OC-48/STM-16 and OC-192/STM-64
interfaces). This implies that the OME6500 can support multiple types of
traffic protection on a single shelf provisionable on a per port basis.

1-4 Introduction
OME6500 applications
The OME6500 can be configured to add value to various network applications
that span across the customer access space through the metro or regional core
network. The principal OME6500 target applications are:
• Edge broadband service switch: The wide set of client service interfaces
offered by the OME6500, in terms of density, optical reach, rate flexibility,
and protocol variety enables deployment of a diverse set of services. In
particular, the OME6500s standards-based edge service adaptation
functionality for the efficient transport of optical broadband services
(10/100/1000 Mbit/s Ethernet, Fibre Channel, FICON, and transparent
services) combined with platform integrated OBS service management
support functions enable widespread deployment of differentiated
high-capacity data transport services.
• Access head end mux: The OME6500s switching capacity and flexibility,
in terms of granularity (unconstrained VT1.5/VC-12 switching) and
transparency (transparent payload mapping), provide an effective means
for multi-service switching, aggregation, and grooming to higher rates at
smaller and medium sized central offices (CO). In this application, the
OME6500 can directly subtend multiple access rings or linear connections
without the need for multiple separate fiber access head-end terminating
multiplexers.
• Next generation digital cross connect system (DCS): The OME6500s
scalable and VT1.5/VC-12 granular TDM switching matrix enables
flexible connection management of circuit-based private line services.
The high electrical interface density (E1, E3, DS1, and DS3) and
scalability of the OME6500 can be leveraged with this flexible switching
capability to reduce the need for costly legacy DCS deployment or
expansion at central offices.
• Metro inter-office (IOF) and regional core transport: The OME6500 is
capable of readily scaling its transport capacity to support core networking
between metro and regional service aggregation COs via multi-fiber
connections at 2.5 Gbit/s and 10 Gbit/s (design ready for 40 Gbit/s) line
rates through its integrated long range optics, including DWDM
compatible interfaces. In addition, the OME6500 provides various
sophisticated standards-based protection options such as
BLSR/MS-SPRing and control plane-based mesh networking support that
complies with the more stringent and efficient protection requirements for
core networking across the backbone.
The OME6500 fully interworks with the current Nortel Networks optical
portfolio as depicted in Figure 1-2. This interworking capability is ensured
through careful attention to optical layer design, service implementation
technology details, network management consistency and detailed
interoperation testing.
Introduction 1-5
Figure 1-2
OME6500 application overview
Access Edge Core

Control plane: Auto discovery, End-End connection management and restoration
10/100Base-T OM3/4K Scalable VT1.5/ Cost effective10Gbps

100Base-FX VC-12 switching Metro and NE consolidation
GE/FC UPS
R/S
NCP N x 2.5/10G BLSR/
FR /1+1 MS-SPRing Mesh
ATM OM3500
DS1/E1 UPSR/SNCP/1+1
DS3/E3/EC1
OC-3/STM-1 bda
OME6500
OC-12/STM-4 OM5K x Lam Optical Cross
N
Common Connect
OC-48/STM-16
Photonic HDX/HDXc
10GE Transparent mapping Layer
ESCON into SONET/SDH
FC100/200 network
FICON
Service management, assurance and performance reporting
Converged "Connectivity Services" (Layer 0-2) network

Combining established and future services while leveraging current infrastructure
The OME6500 integrates high-speed metro and regional core networking long
reach optical interfaces, thereby obviating the need to deploy specialized core
networking transport ADMs. Initially the OME6500 supports multiple
2.5 Gbit/s (OC-48/STM-16) or 10 Gbit/s (OC-192/STM-64) line rate rings or
point-to-point connections for core networking applications.
The OME6500 can be deployed as the fiber access head end mux to Nortel
Networks market leading Optical Metro multiservice platforms. In addition,
subtending OME6500 shelves, that may either be collocated with the CO
head-end OME6500 or situated remotely at a customer site, can be used as
scalable aggregation points for mixed optical and electrical service access.
These service aggregation OME6500s would use smaller cross-connect
fabrics feeding aggregated services into an OME6500 with a larger
cross-connect fabric through multiple OC-3/STM-1, OC-12/STM-4,
OC-48/STM-16, OC-192/STM-64 interfaces as the uplink.
The suite of OME6500 supported optical interfaces include DWDM optics for
scalable high-capacity core networking even in fiber constrained
environments. This multi-faceted platform has also been designed such that
the system characteristics support 40 Gbit/s (OC-768/STM-256) line optics
when the market is ready for deploying these higher capacities.

1-6 Introduction
In applications where there is a need to hand-off traffic to the Optical Cross

Connect HDX/HDXc, or other optical switch or DCS for service connectivity
management, the OME6500 provides the option for highly cost effective short
reach optical interfaces or high density electrical interfaces. This flexibility of
interconnection interface types enables service providers to choose the most
economical solution for each given traffic scenario.
OME6500 service interfaces

OME6500 offers transport and aggregation of asynchronous private lines,
SONET, SDH, and Optical broadband services including transparent
wavelengths via dedicated and protocol and bit rate agile interfaces onto
2.5Gbit/s or 10Gbit/s DWDM or non-DWDM transport interfaces. The
OME6500 supports three basic categories of interface:
• SONET/SDH
— A full range of optical and electrical interfaces including
OC-3/STM-1o, STM-1e, OC-12/STM-4, OC-48/STM-16, and
OC-192/STM-64 are available in a number of variants including
1310 nm, 1550 nm, VSR, and DWDM. In addition, the OME6500
system is architected for smooth evolution to optical
OC-768/STM-256 interface rates as needed.
• PDH
— A full range of electrical interfaces with associated electrical 1:N
protection circuit packs including E1, DS1, E3, DS3, and EC-1.
• Broadband Services
— A full range of broadband and data service interfaces including GE,
FC, FICON, 2.5G wavelengths, 10G wavelengths, 10/100Base-T,
100Base-FX, Optical Date Unit 1 (ODU1), Optical Data Unit 2
(ODU2), and flex-rate protocol independent wavelengths.
Optical interfaces
The OME6500 uses small form-factor pluggable (SFP) interfaces to deliver
optical rate and reach flexibility on a per port basis. 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 a low first-in cost solution for
the circuit pack plus any SFPs needed for initial service delivery. Additional
pluggable optics can then be deployed as services need to be activated in
response to actual customer demand since SFP modules can be incrementally
added to a circuit pack after it is already provisioned with traffic on other ports.
This defers the capital cost until services are sold, thereby preventing stranded
investment.
Introduction 1-7
SFPs also reduce the cost of sparing by enabling a common circuit pack to
offer the reach and data rate as required without having to spare multiple types
of circuit packs. Pluggable technology is especially useful in WDM
applications where the sparing costs across a WDM system can be expensive.
Furthermore, pluggable WDM optics enables multi-port circuit packs to select
the wavelength of the optics pluggable, which enhances optical routing
flexibility.
The OME6500 offers WDM interfaces on its 2.5 Gbit/s and 10 Gbit/s
interfaces; supporting 100 GHz wavelengths compliant to the ITU grid. In
addition, CWDM wavelengths are supported on the GE/FC-100 and 2.5 Gbit/s
interfaces. The DWDM capabilities will enable optical bypass, optical
amplification, and improved fiber capacity utilization. CWDM provides
similar benefits when fewer channels are required at lower cost points.
Figure 1-3 provides a summary of the pluggable optical modules supported on
the OME6500 platform.
Figure 1-3
Pluggable optical modules summary
Small-form factor pluggable (SFP)

155/622 Mbit/s, 2.5 Gbit/s - Carrier grade
non-DWDM, GE/FC
- Reduced first-in cost
- Service tolerance (mix and match combinations of):
- reach (IC/SR/IR/LR) (SX, LX, ZX)
- rate (OC-3/STM-1, OC-12/STM-4, OC-48/STM-16,
GE/FC)
- CWDM with wavelength per pluggable slot
- DWDM 100GHz ITU Grid with wavelength
per pluggable slot
- Operational simplification
- Forecast tolerance (deploy optical interface aligned
DWDM pluggable optics (DPO)
with actual demand)
2.5G DWDM - Expenditure matched with reach requirements
- CAPEX savings through reduced sparing
- Elimination of stranded ports and investment
- Fewer cards per shelf frees up other shelf slots to
deliver additional services
Delivering first-in-cost, density, scale, and flexibility

1-8 Introduction
Distributed service modules

In addition to high density in-skin service interfaces, the OME6500 supports
increased service density scalability through the use of compact subtended
service modules.
A DS1 service module (DSM) can be subtended from an OME6500 shelf. The
DSM supports 84 DS-1s per unit and connects to the main shelf via protected
(1+1) or unprotected OC-3 connections. Based on the 16-port OC-3 circuit
pack density of the OME6500, DSM modules can be stacked to provide 8,064
protected or 16,128 unprotected DS1 interfaces in a single shelf. The DSM
DS1 interfaces can be protected with 1+1 protection.
Ethernet service modules (ESMs) providing compact 10/100Base-T,

100Base-FX, and GE interfaces interworking with the OME6500 via optical
interfaces can also be deployed to scale Ethernet service ports as well.
Services transport
The OME6500 provides various service interfaces to efficiently adapt and
transport emerging optical broadband services, including;
• optical Ethernet (OE) connectivity
• optical storage connectivity
• wavelength services
The OME6500 provides these capabilities via standards-based technology for
edge service adaptation that leverages the strength of Nortel Networks
end-to-end solutions portfolio.
The OME6500 platform supports 10/100Base-T, 100Base-FX, and GE

interfaces. These Ethernet interfaces can connect through the STS fabric, the
Layer-2 (L2) switching matrix, and RPR to provide Ethernet connectivity
services. The services which can be offered include;
• Ethernet private line (EPL)
• Ethernet L2 VPN
• Ethernet point-to-multi-point aggregation
• Resilient Packet Ring (RPR) Private LAN
The OME6500 supports efficient point-to-point Ethernet services and Fibre
Channel Storage Area Network extension services through the Generic
Framing Procedure (GFP), Virtual Concatenation (VCAT), and Link Capacity
Adjustment Scheme (LCAS) standards.
Other types of data transport are supported on the OME6500 via the
Transparent Payload Envelope (TPE) technology that transparently maps any
constant bit-rate signal over SONET/SDH.
Introduction 1-9
Point-to-point optical broadband services

The OME6500-based implementation for point-to-point Ethernet and storage
connectivity services uses the GFP, VCAT, and LCAS standards.
GFP provides an efficient mechanism for GE and FC transport over a

SONET/SDH core network via efficiently mapping varying client signals into
SONET/SDH VT1.5/VC-12 and STS/VC-3/4 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 GE signal, and enables consistent SONET/SDH based
performance monitoring (PM) through the network. Since the GE is mapped
into SONET/SDH frames, the existing core network can transport the Ethernet
frames transparently.
Management features available for the GFP are the client payload type, and
GFP frame sequence check. All of the client management frames will be
supported which will enable alarming on far end status, GFP loss of frame
delineation, or service mismatch. The VCAT can be alarmed on
loss-of-multi-frame, sequence mismatch, and loss of alignment.
These same interfaces will also support Fibre Channel. Each port can be
provisioned as either GE or Fibre Channel and will be supported via GFP over
VT1.5/VC-12 or STS/VC-3/4 frames. Fibre Channel is typically limited to
transport distance limitations of a few hundred kilometres due to storage
networking latency constraints. To overcome this limitation Nortel Networks
has patented a buffer credit mechanism which enables Fibre Channel extension
up to a thousand kms, extending the reach of storage based networking
(SANs).
The OME6500 also supports Virtual Concatenation (ITU-T G.707 compliant)

with support at the VT1.5-nv, STS-1-nv, and STS-3c-nv SONET rates as well
as VC-12-nv, VC-3-nv, and VC-4-nv SDH rates. Up to 14 ms of differential
delay is supported.
Along with VCAT, the OME6500 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 service level agreements (SLA) through graceful
service degradation when necessary. In particular, during network and service

1-10 Introduction
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.
Transparent services
Transparent Payload Envelope (TPE) is a proposal from Nortel Networks for
transparently mapping any constant bit rate signal over SONET/SDH virtual
containers. TPE enables complete support for transparent bit-rate, protocol,
and timing of the client signal across the network. TPE will be used on the
OME6500 platform to offer G.modem services and transport for other
non-SONET/SDH protocols as well as transparent SONET/SDH over
SONET/SDH services.
TPE enables the mapping of ODU structures into virtual container structures
for the transport of OTN elements over existing SONET/SDH transport
networks:
• An ODU1 is mapped into 17 STS-3c/VC-4s
• An ODU2 is mapped into 68 STS-3c/VC-4s
Nortel Networks is actively working with the standards body to incorporate
this into G.709.
TPE will address the following protocols not addressed by GFP:

• Transparent mapping of SONET/SDH signals into SPE (to support
transparent services)
— OC-12/STM-4 into STS-15c/VC-4-5c
• Efficient transport of protocols from 50M to 2.7G over SONET/SDH
— Some protocols include ESCON, DV6000, FDDI, and HDTV.
TDM switching
In the OME6500 architecture, traffic is switched between port circuit packs via
the cross-connect circuit packs. Two cross-connect circuit packs are used to
provide redundant equipment protection. All ingress port circuit pack traffic is
mapped into VT1.5/VC-12 or STS-1/VC-3/4 containers and directed towards
the cross-connect circuit pack which is configured to switch the incoming
traffic to the appropriate egress port circuit pack. The cross-connect circuit
pack allows any input channel to be connected to any output channel. Using
this basic functionality, the system can support diverse connection and
protection configurations.
Introduction 1-11
The OME6500 platform has been designed to support several different switch
fabrics which include an 80 Gbit/s STS-1/VC-3 matrix, an 80 Gbit/s
VT1.5/VC-12 matrix, and a 160 Gbit/s STS-1/VC-3 matrix. The architecture
of the OME6500 has been designed to scale beyond this switching capacity in
the future in response to market demand.
Layer 2 switching
The OME6500 supports Layer 2 Service Switch (L2SS) series of circuit packs
to help aggregate and switch Ethernet services. The L2SS will work into both
the STS-1/VC-3 and VT1.5/VC-12 cross-connect circuit packs for GFP
mapped Ethernet, which could be provided by the OME6500, OM3000, and
OM5000 Ethernet Private Line (EPL) circuit packs. The L2SS circuit packs
also support native Ethernet interfaces for switching directly into the transport
network including 802.3ah support for head end integration of the OME1000
series of products. Designed for carrier grade reliability, manageability,
broadband data rates, and service flexibility, the L2SS series of circuit packs
provide a strong Ethernet services and infrastructure solution for IP, Ethernet
Private LANs, Ethernet VPNs, Ethernet Virtual Private Lines, Triple Play
Services, and Internet access solutions.
With the L2SS series of circuit packs, Nortel Networks continues its
technology direction to support Ethernet over GFP for transport over
SONET/SDH as demonstrated in our OM3000, OM4000, and OM5000
product lines. The L2SS will also support virtual and contiguous concatenation
as well as LCAS (for VCAT) in order to ensure that packet traffic is most
efficiently, reliably, and deterministically carried over the transport network.
The L2SS circuit packs will evolve by supporting stacked VLAN switching,
stacking, popping, MAC Switching, Distributed Multi-link Trunking, and
Resilient Packet Ring for immense scale and availability. The L2SS circuit
packs support both Ethernet UNI (User-to-Network interfaces) such as VLAN
and raw Ethernet as well as Ethernet NNI (Network-to-Network Interfaces)
with stacked VLAN and Mac-in-Mac [IEEE 802.1ah] and includes
point-to-point, point-to-multipoint, and any-to-any logical topologies.
Next generation RPR

The OME6500 supports RPR as defined by the IEEE 802.17. RPR is a ring
based technology that enables bandwidth sharing, high reliability, and network
simplicity across multiple Ethernet ports for efficient transport of packets.
L2SS RPR Ethernet circuit packs are offered for private LAN applications and
as efficient Ethernet switched backhaul for Ethernet VPN and IP traffic. These
circuit packs allow for the sharing of STS/VC bandwidth amongst multiple
nodes and allow for any-any connectivity. Virtual LANs can share RPR ring
bandwidth using Traffic Domain Identifier (TDI) labels. These labels are
similar to VLAN tags but provide greater flexibility and scalability. RPR ring
bandwidth can be allocated at the STS-1/VC-3/VC-4, STS-3c/VC-4,
STS-12c/VC-4-4c, and STS-48c/VC-4-16c levels. RPR is a key technology
within the OME6500 Layer 2 switching solution.

1-12 Introduction
Nortel Networks' market leading RPR technology has been successfully

demonstrated and deployed on the Optical Metro 3500 platform with many
customers.
Network management
The OME6500 is managed as an integral part of Nortel Networks' market
proven end-to-end optical portfolio management capabilities. This framework
supports sophisticated and highly customizable desktop applications
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 capabilities are supported by the Optical
Manager and Optical Application Platform in alignment with Nortel Networks
overall optical networks portfolio.
Network design is facilitated through Optical Planner. Optical Planner

provides network designs for multiple applications and technologies. The
design software offers SONET/SDH switching functionality including traffic
grooming, segmentation, protection, and restoration. Carriers utilizing the
Optical Planner can expect to achieve both capital savings from the equipment
used for future network builds and operational efficiencies from the
streamlined planning process. By leveraging the extensive automation
capabilities in the tool network designers can improve productivity and
efficiently manage large network plans (operational savings). By
incorporating advanced searching techniques and heuristics based
optimization algorithms designers may focus their efforts exhaustively
examining possible architectures and “what-if” sensitivity modeling leading to
the most cost effective design possible (capital equipment savings).
Site Manager provides complete nodal management that can be integrated into
a centralized network wide view through the Optical Application platform.
Additionally, open OSS interfaces such as TL1 and TMF814 ensure a smooth
fit into existing OSS systems and processes. The OME6500 TL1 is built to the
Telecordia SR (Special Report)-1665 standards.
Introduction 1-13
Key features and benefits

The OME6500 converged optical services 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
OME6500 can be summarized as follows:
• carrier-grade deployment of a broad set of services (SONET/SDH,
transparent wavelength, TDM electrical, Ethernet connectivity, storage
connectivity)
• switching granularity and flexibility for service grooming and connection
management
— unconstrained VT1.5/VC-12 level switching
— support for a wide range of concatenated payloads
— transparent mapping/switching/transport of services
— integrated L2 switching
— next generation RPR capability
• cost-efficient service deployment through
— high density service specific interfaces
— dynamically pluggable optical interfaces (lowers sparing costs and
reduces the number of service specific interface circuit packs needed
for low-fill applications requiring diverse reach and optical rates)
— flexible, complete, and easy to use network and service management
leading to simplified operations for rolling out and maintaining
services
• a future proof platform that efficiently delivers existing profitable services
and fits smoothly into the networks of today, worldwide, while enabling
the wide scale deployment of optical broadband services and core
networking transport scalability (through 10 Gbit/s DWDM and towards
40 Gbit/s).
The OME6500 simply defines the multiservice edge of innovative service
providers in their quest for business success through accelerated service
deployment in a scalable and flexible manner.

1-14 Introduction
2-1
Feature overview 2-
This chapter provides a brief overview of the Optical Multiservice Edge 6500
(OME6500) features. Release 1.2 of Optical Multiservice Edge 6500
introduces the following new features:
• new hardware
— 20G VT1.5/VC-12 cross-connect circuit pack (20/20)
— 24xDS3/EC-1 working and protection circuit packs
— 48xDS3/EC-1 I/O panel (front and rear versions)
— DS1 service module (DSM) (including new BIP)
— new pluggable modules:
– 1 new STM-1e SFP (1.0/2.3mm) (contact Nortel Networks for
availability)
– 8 new OC-48/STM-16 CWDM SFPs (8 wavelengths, 1471 nm to
1611 nm)
– 1 new OC-3/STM-1 SFP (SR0 multimode)
– 1 new OC-3/12/STM-1/4 SFP (SR1/I1.1_I4.1)
– 1 new GE ZX 1550 nm SFP
– 8 new GE/FC CDWM SFPs (8 wavelengths, 1471 nm to 1611 nm)
• performance monitoring (PM) enhancements:
— DS1, DS3, and EC-1 PMs
— FTP of PMs (for OMEA)
• alarm enhancements
— enhanced VT1.5/VC12 alarm support (up to 1344 per slot)
— support for DS1, DS3, EC-1, and DSM alarms
• DS1, DS3, and EC-1 loopbacks
• security enhancements:
— intrusion attempt handling for DSM
— OSI login security for DSM
• time of day (TOD) synchronization to SNTP server

2-2 Feature overview
• protection enhancements:
— unprotected DS1, DS3/EC-1
— 1:N equipment protection for DS3/EC-1
— 1+1 equipment protection for DSM 84xDS1 termination module (TM)
circuit pack
— unidirectional path-switched ring (UPSR)/subnetwork connection
protection (SNCP) at VT1.5, VC12, STS-1/VC3, STS-3c/VC-4,
STS-12c/VC4-4c, STS-24c/VC4-8c, STS-48c/VC416c, and
STS-192c/VC4-64c on OC-3/STM-1, OC-12/STM-4,
OC-48/STM-16, OC-192/STM-64, and GE interfaces
• connection management enhancements:
— STS-1 (AU3) to AU4 conversion for international SONET/SDH
gateway applications
— 1-way protected (1WAYPR) and 2-way protected (2WAYPR)
cross-connects (for UPSR/SNCP)
— dual 2-way protected (2WAYDPR) for connections between
UPSR/SNCP configurations
— GE drop-and-continue for broadcast video applications
Note 1: There is no limit for drops and continues per connection for the
VT1.5/VC12 cross-connect circuit pack. In Release 1.2, Nortel Networks
has tested system configurations with up to 20 drops and continues (for
example, 1 drop and 19 continues). For the STS-1/VC3 cross-connect
circuit pack, the maximum of 4 drops and continues remains.
Note 2: See Supported unidirectional configurations on page 6-47 for
more information.
• new service mappings:
— DS3 to STS-1/LO_VC3
— DS1 to VT1.5
• DCN enhancements:
— Nested Telnets
— interworking with OME6110
— OSI ping tool
• upgrade support from Release 1.1
• user interface enhancements:
— consolidated craft support (for OME6500, OM3000, and HDX)
— raw TL1 port for OSS
• support for four 2-fiber BLSR/MS-SPRing configurations on same
OME6500 shelf
Table 2-1 on page 2-3 lists the features available in different releases of Optical
Multiservice Edge 6500. 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 OME6500 OME6500 OME6500 Reference for more
R1.0 R1.1 R1.2 information
Bay/rack configurations
OME shelf options Yes Yes Yes Bay/rack configurations on
page 2-12
Shelves
Optical shelf Yes Yes Yes
Optical/front electrical shelf Yes Yes Yes Shelf assemblies on page 4-2
Optical/rear electrical shelf No Yes Yes
Cooling system
Front venting Yes Yes Yes
Cooling configurations on
Top venting No Yes Yes
page 4-5
Rear venting No Yes Yes
Common equipment
Breaker interface panel (2 x 100 A) Yes Yes Yes
Breaker interface panel (4 x 40 A) No Yes Yes
Breaker interface panel
DSM breaker interface panel No No Yes (optional) on page 4-9
(2 x 100 A)
Access panel (SDH) Yes Yes Yes
Access panel on page 4-19
Access panel (SONET/J-SDH) No Yes Yes
Fiber routing channel Yes Yes Yes Fiber/cable routing channel on
page 4-53
Shelf cover Yes Yes Yes Shelf cover on page 4-54
Common circuit packs/cards
Maintenance interface card Yes Yes Yes Maintenance interface card on
page 4-23
40 A power input card - breakered Yes Yes Yes
Power input card on page 4-24
40 A power input card - breakerless Yes Yes Yes
Shelf processor Yes Yes Yes Shelf processor on page 4-25

Table 2-1 (continued)

Cross-connect 80G STS-1/VC-3 Yes Yes Yes
Cross-connect 160G+ STS1/VC-3 Yes Yes Yes
Cross-connect 80G/80G No Yes Yes Cross-connect circuit packs on
VT1.5/VC-12 (80/80) page 4-27 (see Note 1 and
Note 2 on page 2-11)
Cross-connect 80G/20G No Yes Yes
VT1.5/VC-12 (80/20)
Cross-connect 20G/20G No No Yes
VT1.5/VC-12 (20/20)
Filler card Yes Yes Yes Filler card on page 4-45
Optical interface circuit packs
1xOC-192/STM-64 STS-1/HO No Yes Yes
SR1/I64.1
1xOC-192/STM-64 STS-1/HO Yes Yes Yes
IR2/S64.2
1xOC-192/STM-64 STS-1/HO No Yes Yes
LR2/L64.2
1xOC-192/STM-64 STS-1/HO Yes Yes Yes
DWDM (initial 8 wavelengths)
1xOC-192/STM-64 STS-1/HO No Yes Yes 1xOC-192/STM-64 circuit
DWDM (additional 8 OMX pack on page 4-34
compliant wavelengths and 36 CPL
compliant wavelengths)
1xOC-192/STM-64 VT1.5/LO No Yes Yes
SR1/I64.1
IR2/S64.2
LR2/L64.2
DWDM (16 OMX compliant
wavelengths, 36 CPL compliant
wavelengths)
2xOC-48/STM-16 STS-1/HO DPO No Yes Yes
2xOC-48/STM-16 STS-1/HO SFP No Yes Yes
2xOC-48/STM-16 circuit pack
2xOC-48/STM-16 VT1.5/LO DPO No Yes Yes
on page 4-36
2xOC-48/STM-16 VT1.5/LO SFP No Yes Yes

8xOC-3/12/STM-1/4 STS-1/HO Yes Yes Yes 8xOC-3/12/STM-1/4 circuit
SFP pack on page 4-38
8xOC-3/12/STM-1/4 VT1.5/LO SFP No Yes Yes
4xGE EPL SFP Yes Yes Yes 4xGE EPL circuit pack on
page 4-39
SFP/DPO modules
OC-3/STM-1 LR2/L1.2 1550 nm Yes Yes Yes
OC-3/12/STM-1/4 IR1/S1.1_S4.1 Yes Yes Yes
1310 nm
OC-12/STM-4 LR2/L4.2 1550 nm Yes Yes Yes
GE/FC 1000-BaseSX 850 nm Yes Yes Yes
GE/FC 1000-BaseLX 1310 nm Yes Yes Yes
OC-48/STM-16 IR1/S16.1 1310 nm No Yes Yes
OC-48/STM-16 LR2/L16.2 No Yes Yes
1550 nm
OC-48/STM-16 DPO (1528.77 nm No Yes Yes
to 1564.68 nm), 8 OMX compliant Optical transceivers on page
wavelengths and 36 CPL compliant 4-33
wavelengths)
OC-3/STM-1 SR0 (multimode) No No Yes
1310 nm
OC-3/12/STM-1/4 SR1/I1.1_I4.1 No No Yes
1310 nm
OC-48/STM-16 CWDM (1471 nm No No Yes
to 1611 nm), 8 wavelengths
1.25 Gbit/s GE CWDM (1471 nm to No No Yes
1611 nm), 8 wavelengths
GE 1000-BaseZX 1550 nm No No Yes
STM-1e No No Yes
Electrical interface circuit packs/modules
63xE1 working No Yes Yes
63xE1 1:N protection No Yes Yes
63xE1 working and protection
E1 I/O protection module No Yes Yes
circuit packs on page 4-42
252xE1 front I/O panel No Yes Yes
120 ohm converter module No Yes Yes


24xDS3/EC-1 working No No Yes
24xDS3/EC-1 protection No No Yes 24xDS3/EC-1 working and
protection circuit packs on
48xDS3/EC-1 I/O module (front and No No Yes
page 4-44
rear versions)
DSM shelf
84xDS1 service module No No Yes DS1 service module shelf on
page 4-45
Configuration
Unprotected Yes Yes Yes Unprotected configuration on
page 3-2
MSP linear (SDH) Yes Yes Yes
1+1/MSP linear on page 3-3
1+1 linear APS (SONET) No Yes Yes
2-Fiber BLSR/MS-SPRing No Yes Yes BLSR/MS-SPRing on page
3-4
UPSR/SNCP No No Yes UPSR/SNCP configuration on
page 3-6
GE point-to-point Yes Yes Yes Gigabit Ethernet point-to-point
application on page 3-7
E1 intra-office No Yes Yes Intra-office application on
page 3-9
DS1, DS3/EC-1, STM-1e No No Yes
intra-office
Equipment and facility management
Global nodal provisioning No Yes Yes Global support on page 6-20
Equipment management Yes Yes Yes Setting the NE mode is
provisionable from the Node
Information application in the
Configuration menu in Site
Manager. on page 6-21
Facility management Yes Yes Yes Facility management on page
6-25

Connection/bandwidth management
VC4 bandwidth management Yes Yes Yes
STS-1 bandwidth management No Yes Yes
VT1.5/VC12 and LO VC3 No Yes Yes
bandwidth management
Concatenated rates (VC4-4c, Yes Yes Yes
VC4-8c)
Concatenated rates No Yes Yes Connection management on
(STS-3c, STS-12c, STS-24c, page 6-41
STS-48c/VC4-16c,
STS-192/VC4-64c)
Virtual concatenation No Yes Yes
(STS-1-nv/VC3-nv, where n = 1 to
21, STS-3c-nv/VC4-nv, where n = 1
to 7)
International gateway No No Yes
STS-1 (AU3) to AU4 connections
on OC-48/STM-16 ports
Service mappings
GE GFP-F to VC4, VC4-4c, VC4-8c Yes Yes Yes
GE GFP-F to STS-1, STS-3c, No Yes Yes
STS-12c, STS-24c Generic Framing Procedure
GE GFP-F to STS-1/VC3-nv and No Yes Yes on page 6-49
STS-3c/VC4-nv (virtual
concatenation)
E1 to VC12 No Yes Yes
Connection management
DS3 to STS-1/LO_VC3 No No Yes
application on page 6-51
DS1 to VT1.5 No No Yes
Traffic protection
Unprotected - STM-1, STM-4, Yes Yes Yes
STM-64 Unprotected connections on
Unprotected - OC-3, OC-12, No Yes Yes page 6-67
OC-48/STM-16, OC-192
MSP Linear - STM-1, STM-4, Yes Yes Yes
STM-64 1+1/MSP linear traffic
protection on page 6-59
1+1/MSP Linear - OC-3, OC-12, No Yes Yes
OC-48/STM-16, OC-192


2-Fiber BLSR/MS-SPRing No Yes Yes 2-Fiber BLSR/MS-SPRing
traffic protection on page 6-61
UPSR/SNCP No No Yes UPSR/SNCP traffic protection
on page 6-3
Protection exerciser No Yes Yes Traffic protection exerciser on
page 6-66
Equipment protection
Cross-connect Yes Yes Yes
E1 (1:N) No Yes Yes
Equipment protection on page
DS3/EC-1 (1:N) No No Yes 6-51
DSM 84xDS1 TM (1+1) No No Yes
Synchronization
Internal, external, line, and mixed Yes Yes Yes
timing
Protection (redundant) Yes Yes Yes
Timing generation hierarchy (up to Yes Yes Yes
4 references)
Timing distribution hierarchy (up to Yes Yes Yes
4 references)
Synchronization management
SDH SSM generation/termination Yes Yes Yes on page 6-29
SONET SSM No Yes Yes
generation/termination
2 MHz ESI Yes Yes Yes
2 MHz ESO No Yes Yes
2 Mbit/s ESI/ESO with SSM No Yes Yes
DS1 ESI/ESO with SSM No Yes Yes
Alarms and events
LEDs indication of shelf and circuit Yes Yes Yes
pack status Alarm and event management
Alarm and event reporting Yes Yes Yes on page 6-72

Performance monitoring
SDH RS, MS, and path - near end Yes Yes Yes
SONET section, line, and path - No Yes Yes
near end
SONET/SDH line/MS and path - far No Yes Yes
end
Physical PM (1xOC-192/STM-64 Yes Yes Yes
circuit pack only)
Physical PM (all optical circuit No Yes Yes Performance monitoring on
packs) page 6-75
Protection switch counts/duration No Yes Yes
E1 PM - near and far end No Yes Yes
EC-1 line and path PM - near and No No Yes
far end
EC-1 section PM - near end No No Yes
DS3 line - near end No No Yes
DS3 path - near end and far end No No Yes
DS1 line and path - near end and No No Yes
far end
FTP of PMs No No Yes
Operational measurements
Generic Interface OMs - LAN and Yes Yes Yes
WAN Operational measurements on
page 6-80
Ethernet Specific OMs Yes Yes Yes
System lineup and testing
Commissioning Assistant Tool Yes Yes Yes Commissioning Assistant Tool
on page 6-20
Troubleshooting tools
Facility and Terminal Loopbacks Yes Yes Yes
(STM-n)
Facility and Terminal Loopbacks No Yes Yes Loopbacks on page 6-27
(GE, OC-n, E1)
Facility and Terminal Loopbacks No No Yes
(DS3, EC-1, and T1)


Data management
Network element data backup and Yes Yes Yes Backing up and restoring the
restore network element database on
page 6-89
Autodiscovery
Network topology No Yes Yes Autodiscovery on page 2-23
Security and administration
Local user account/password Yes Yes Yes
management
Centralized security administration No Yes Yes
Intrusion attempt handling No Yes Yes Security and administration on
RADIUS authentication No Yes Yes page 6-81
Network element naming, date and Yes Yes Yes

time
Time of day synchronization No No Yes
OSI login security for DSM No No Yes
Data communications network
RS232, LAN, optical DCC physical Yes Yes Yes
interfaces
IP addressing Yes Yes Yes
OSI addressing Yes Yes Yes
iISIS router Yes Yes Yes
OSPF router No Yes Yes
Tunnelling (GRE) Yes Yes Yes
OME6500 OAM comms on
DHCP server Yes Yes Yes
page 6-68 and Appendix A:
DCC protection follows traffic No Yes Yes Data communications
HTTP server No Yes Yes planning on page 10-1
FTP client and server Yes Yes Yes

Telnet client and server Yes Yes Yes
PPP/LAPD over DCC Yes Yes Yes
DSM OAM links No No Yes
Nested Telnets No No Yes
IP ping tools Yes Yes Yes
OSI ping tools No No Yes

System management
Consolidated craft No No Yes
Site Manager Yes Yes Yes
Site Manager downloadable from No Yes Yes User interface description on
shelf processor page 5-1
Site Manager - enhanced No Yes Yes
window/application management
TL1 command builder No Yes Yes
Raw TL1 port for OSS No No Yes
Interworking
Nortel portfolio Yes Yes Yes Interworking with Nortel
portfolio on page 2-25
non-Nortel portfolio Yes Yes Yes Interoperating with non-Nortel
portfolio on page 2-26
Supported upgrade and backout paths
Network element upgrade No Yes Yes
Slot upgrades of circuit packs No Yes Yes Installing and upgrading
requiring cold restart network element software on
page 6-90
Site Manager upgrade No Yes Yes
Shelf processor only upgrade No Yes Yes
Supported circuit pack reconfigurations (see Note 1 and Note 2)
In-service STS-1/VC3 to No Yes Yes
VT1.5/VC12 cross-connect circuit Hardware on page 3-15
pack
In-service STS-1/HO to VT1.5/LO No Yes Yes
optical interface circuit pack
Note 1: STS-1/VC-3 cross-connect circuit packs provide high order (HO) traffic switching at STS-1
(SONET) and VC-3_HO and VC-4 (SDH) traffic granularities.
Note 2: VT1.5/VC-12 cross-connect circuit packs provide low order traffic (LO) switching at VT1.5
(SONET) and VC-12 and VC-3_LO (SDH) traffic granularities, as well as high order traffic switching at
STS-1 (SONET) and VC-3_HO and VC-4 (SDH) traffic granularities.

Physical description
The OME6500 hardware platform has the following modular components:
• OME6500 shelf (refer to Shelf assemblies on page 4-2)
• cooling unit (refer to Cooling configurations on page 4-5)
• fiber routing channel (refer to Fiber/cable routing channel on page 4-53)
• electrical interface chassis (refer to Electrical interface area on page 4-21)
• breaker interface panel (optional) (refer to Breaker interface panel
(optional) on page 4-9)
The OME6500 platform fits a standard ETSI (19 in. EIA) or NEBS2000 rack
with a standard 300 mm x 600 mm footprint and the ANSI (23 in.) rack.
OME6500 provides three shelf assemblies as follows:
• optical shelf assembly
• optical/front electrical shelf assembly
• optical/rear electrical shelf assembly
For more information, refer to Shelf assemblies on page 4-2.
Bay/rack configurations
The OME6500 bay configuration and rack density depends on the services to
be deployed (optical only or optical and/or electrical) which determines the
shelf assembly to deploy. OME6500 supports the following bay
configurations:
• up to three OME6500 shelves per bay when deploying only optical
services requiring only the optical shelf assembly
• up to two OME6500 shelves per bay when deploying:
— two optical/front electrical shelves for deploying optical services
and/or front access electrical services
— one optical shelf assembly and one optical/front electrical shelf
• up to four OME6500 shelves per bay when deploying the optical/rear
electrical shelf assemblies. If space is required in the rack for optical fiber
management and/or DWDM equipment, the maximum number of
optical/rear electrical shelf assemblies will be less than four. Each
optical/rear electrical shelf assembly or pair of stacked optical/rear
electrical shelf assemblies requires an air inlet plenum and a cooling unit.
Note 1: The optical/front electrical shelf and optical/rear electrical shelf
assemblies ensure the bay configuration can provide electrical services.
Note 2: See Configuration rules in Ordering Information, 323-1851-151
for thermal limitations for deploying optical/rear electrical shelf
assemblies.
The OME6500 provides both breakered and breakerless power input cards.
For deployment of breakerless power input cards, an OME6500 breaker
interface panel (BIP) is required. The OME6500 BIP provides power
distribution, breaker interfaces, and visual alarms for the OME6500 shelves
installed within the bay. Figure 2-1 and Figure 2-2 provide an overview of the
possible OME6500 only bay configurations supported in this release. Figure
2-3 and Figure 2-4 provide an overview of the possible combined OME6500
and DSM bay configurations supported in this release.
Figure 2-1
OME6500 bay configurations - optical and optical/front electrical shelves
BIP/Reserved space 2U BIP/Reserved space 2U BIP/Reserved space 2U

Optical fiber management
and DWDM equipment 3U Cooling unit 3U
and DWDM equipment 8U
Cooling unit 3U
Optical shelf assembly Cooling unit 3U

10U Optical/front electrical
18U
shelf assembly
Cooling unit 3U Optical/front electrical

shelf assembly
18U
Optical shelf assembly Cooling unit 3U

10U
Cooling unit 3U Optical/front electrical Cooling unit 3U

shelf assembly 18U
Optical shelf assembly

10U Optical shelf assembly 10U
Optical shelf Optical/front Optical shelf and

assemblies electrical shelf assemblies optical/front
electrical shelf assemblies
These figures are based on 44U of total available rack space

Figure 2-2
OME6500 bay configurations - optical/rear electrical shelves
BIP/Reserved space 2U BIP/Reserved space 2U

Cooling unit 3U and DWDM equipment 3U
Cooling unit 3U
Optical/rear electrical
8U
shelf assembly
shelf assembly 8U
Optical/rear electrical 8U Air plenum 2U

shelf assembly
Cooling unit 3U
Air plenum 2U
Cooling unit 3U Optical/rear electrical 8U

shelf assembly
Optical/rear electrical 8U Air plenum 2U

shelf assembly
Cooling unit 3U
Optical/rear electrical 8U Optical/rear electrical 8U

shelf assembly shelf assembly
Air plenum 2U Air plenum 2U
Stacked optical/rear Single optical/rear electrical

electrical shelf assemblies shelf assemblies (with fiber
management/DWDM
equipment space)
Figure 2-3
OME6500 and DSM bay configurations - optical and DSM shelves
DSM BIP
2U OME6500 BIP 2U OME6500 BIP 2U
DSM BIP 1U DSM BIP 1U
DSM shelf assembly 4U
Cooling unit 3U Cooling unit 3U

Optical shelf assembly 10U Optical shelf assembly 10U
DSM shelf assembly 4U Cooling unit 3U

DSM shelf assembly 4U Optical shelf assembly 10U


DSM shelf assembly 4U 3U
DSM shelf assembly 4U DSM shelf assembly 4U DSM shelf assembly 4U
DSM shelf assembly 4U DSM shelf assembly 4U

DSM shelf assembly 4U DSM shelf assembly 4U
DSM shelf Optical & DSM shelf Optical & DSM shelf
assemblies assemblies assemblies

Figure 2-4
OME6500 and DSM bay configurations - optical/rear electrical, optical/front electrical, and DSM
shelves
OME6500 BIP 2U OME6500 BIP 2U OME6500 BIP 2U

DSM BIP 1U DSM BIP 1U DSM BIP 1U
Cooling unit 3U Cooling unit 3U Cooling unit 3U
Optical/rear electrical Optical/rear electrical

8U 8U
shelf assembly shelf assembly
Air plenum 2U Optical/front electrical 18U

shelf assembly
DSM shelf assembly 4U Optical/rear electrical 8U
shelf assembly

Air plenum 2U
Optical/rear Optical/rear Optical/front

electrical & DSM electrical & DSM electrical & DSM
shelf assemblies shelf assemblies shelf assemblies
For more information, refer to Hardware description on page 4-1 and the
configuration rules in Ordering Information, 323-1851-151.
Interface circuit packs

The OME6500 architecture supports both optical and electrical interfaces on
the same shelf. The following optical and electrical interfaces are currently
supported:
• SONET/SDH optical interfaces (OC-3/STM-1, OC-12/STM-4,
OC-48/STM-16, and OC-192/STM-64)
• Gigabit Ethernet (GE) data optical interfaces
• E1 (2 Mbit/s) electrical interfaces
• DS3/EC-1 electrical interfaces
• DS1 electrical interfaces
• STM-1e electrical interfaces
The OME6500 allows the user to provision any interface circuit pack type in
any service interface slot as follows:
• OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, GE, and STM-1e
interfaces can be installed in slots 1-6 or 9-14
• OC-192/STM-64 interfaces can be installed in slots 5, 6, 9, and 10
• working E1 and DS3/EC-1 interfaces can be installed in slots 1-4 and 9-12,
protection E1 and DS3/EC-1 interfaces can be installed in slots 13 and 14.
• DS1 interfaces can be installed in a separate DS1 service module (DSM)
shelf.
For more information about the interface circuit packs, see Interface circuit
pack descriptions on page 4-31. For more information about slot equipping
rules, see Ordering Information, 323-1851-151.
Configurations
OME6500 currently supports the following configurations.
Unprotected
OME6500 supports unprotected configurations. For more information, refer to
Unprotected configuration on page 3-2.
1+1/MSP linear protection
OME6500 supports 1+1/multiplex section protection (MSP) linear
configurations. For more information, refer to 1+1/MSP linear on page 3-3.
2-Fiber BLSR/MS-SPRing
OME6500 supports 2-Fiber BLSR/MS-SPRing, providing ring switching
capability.
In a 2-Fiber BLSR/MS-SPRing configuration, two optical fibers connect each

node to each of its two adjacent nodes. Each optical fiber carries both working
and protection traffic in one direction. The bandwidth on each optical fiber is

divided into two equal halves, one half for working and the other half for
protection. BLSR/MS-SPRing supports ring connections on the
OC-48/STM-16, and OC-192/STM-64 optical interfaces.
For more information, refer to BLSR/MS-SPRing on page 3-4.

UPSR/SNCP
OME6500 supports subtending unidirectional path switched ring
(UPSR)/sub-network connection protection (SNCP) configurations.
The UPSR/SNCP function provides:

• the capability of eliminating subtending head-end nodes with back-to-back
tributaries by terminating the UPSR/SNCP directly on the OME6500
• a single OME6500 network element to terminate several UPSR/SNCP
systems, as well as providing unrestricted connections across all
UPSR/SNCP configurations in a non-blocking fashion.
In an UPSR/SNCP 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 UPSR/SNCP configuration on page 3-6.
OME6500 supports nodal port-to-port connection management. OME6500
also supports contiguous and virtual concatenated payloads. Concatenation
allows equipment to carry payloads that exceed the bandwidth capacity of a
single STS-1/VC3/VC4. The concatenated payload provisioning feature
introduces the ability to provision bidirectional and unidirectional
concatenated rate connections at the following rates:
• contiguous concatenated: STS-3c, STS-12c/VC4-4c, STS-24c/VC4-8c,
STS-48c/VC4-16c, and STS-192c/VC4-64c
• virtual concatenated for GE services: STS-1-nv/VC3-nv, where n = 1 to 21,
STS-3c-nv/VC4-nv, where n = 1 to 7
The cross-connect granularity depends on the cross-connect and interface
circuit packs. All circuit packs support STS-1/VC4 switching granularity. The
VT1.5/VC12 cross-connect circuit packs and VT1.5/LO interface circuit
packs support VT1.5/VC12/LO-VC3 switching granularity.
For more information, refer to Connection management on page 6-41.
Service mapping
All services (SONET/SDH, GE, DS3/EC-1, DS1 and E1) are mapped to
appropriate SONET/SDH containers.
The OME6500 uses Generic Framing Procedure (GFP), as its standards based
SONET/SDH mapping for GE 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 GE to SONET/SDH containers.
E1 services are mapped to VC12 containers. DS1 services are mapped to

VT1.5 containers. DS3 services are mapped to STS-1/LO_VC3 containers.
EC-1 services support STS-1 and VT1.5 connections.
Traffic protection
OME6500 supports 1+1/MSP linear, BLSR/MS-SPRing, and UPSR/SNCP
traffic protection. The system monitors the traffic facilities for performance
degradation and failure and performs protection switching when these
conditions are present.
Table 2-2 provides a summary of the supported protection and restoration

schemes for the traffic carrying circuit packs.
For more information, refer to Traffic protection on page 6-56.

Table 2-2
Traffic protection summary
Protection scheme Supported traffic carrying circuit packs

Unprotected • 1xOC-192/STM-64 circuit pack
(default for all supported circuit • 2xOC-48/STM-16 circuit pack
packs)
• 8xOC-3/12/STM-1/4 circuit pack
• 4xGE EPL circuit pack
• 63xE1 working circuit pack
• DS3/EC-1 working circuit pack
• DS1 service module
• 84xDS1 TM (on DSM)
1+1/MSP linear • 1xOC-192/STM-64 circuit pack
(Unidirectional/bidirectional, • 2xOC-48/STM-16 circuit pack
nonrevertive)
• 84xDS1 TM (on DSM)
BLSR/MS-SPRing • 1xOC-192/STM-64 circuit pack
• 2xOC-48/STM-16 circuit pack
UPSR/SNCP • 1xOC-192/STM-64 circuit pack
• 2xOC-48/STM-16 circuit pack
• 4xGE EPL circuit pack
Note: Since GE, DS3, EC-1, DS1, and E1 services are mapped to
appropriate STS/VT/VC containers and assigned as STS/VT/VC level
connections, the traffic protection scheme supported by the OC-n/STM-n
interface circuit packs can be used to provide a protected GE, DS3, EC-1,
DS1, or E1 service without requiring a redundant handoff from the
subtending GE, DS3, EC-1, DS1, or E1 equipment.
OME6500 supports the following equipment protection schemes and modes:
• 1+1 nonrevertive for cross-connect circuit packs
• 1:N for E1 working/protection circuit packs
• 1:N for DS3/EC-1 working/protection circuit packs
• 1+1 for DS1 TM circuit packs
For more information about the supported features for equipment protection,
refer to Equipment protection on page 6-51.
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.
The OME6500 provides system synchronization using 1+1 redundant

synchronization hardware on the cross-connect circuit pack for both timing
generation and timing distribution.
For more information about the hardware associated with OME6500

synchronization, refer to Synchronization hardware on page 4-30. For more
information about the management of synchronization features and
capabilities, refer to Synchronization management on page 6-29.
Alarm and events

The OME6500 provides several mechanisms to identify and localize faults and
events.
• light-emitting diodes (LED) on the faceplate indicates the status of the
functionality supported on the circuit pack
— circuit pack failed on all circuit packs
— loss of signal on interface circuit packs
— loss of synchronization reference on cross-connect circuit pack
• LED on the power input card provides the power status
• LEDs on the MIC provides a summary of active alarms at the shelf level
and shelf level power status
• visual alarms interface on the access panel provides a summary of active
alarms at the shelf level
• LEDs and an external alarm interface port on the BIP provides a summary
of active alarms for all OME6500s in a bay
Refer to the appropriate sections in the Chapter 4, “Hardware description” for
more information about LED definition and external alarm interfaces.
The OME6500 stores active alarms, alarm history, events, and logs which can
be viewed from the Site Manager user interface.
The OME6500 also allows the user to provision (enable/disable) alarm points
through the alarm profile feature in the Site Manager craft user interface. For
more information, refer to Alarm and event management on page 6-72.

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. PM 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 PM:

• section/regenerator section (RS), line/multiplex section (MS), E1, DS3,
EC-1, DS1 and path near-end PM
• line/MS, E1, DS3, DS1, and path far-end PM
• physical layer PM for the all optical interfaces
• protection switching counts/duration PM
• GE LAN (client facing) and WAN (GFP-F mapped - line facing) PM
The OME6500 allows the user to retrieve:
• current PM values (15 minute, 1-Day and untimed values in progress)
• recent history (32 previous 15 minute and Day values stored on the
network element)
The OME6500 supports user provisionable threshold crossing alerts (TCA) to
advise the user when a PM parameter threshold has been exceeded. PM
profiles allow the user to manage the threshold values used to trigger TCAs.
For more information, refer to Performance monitoring on page 6-75.
The 4xGE EPL circuit pack collects operational measurements which contain
a set of counters for the LAN interface (client facing) and the WAN interface
(GFP-F mapped) for each interface port. These operational measurements are
asynchronously retrieved and cleared and are not stored in bins (except
ETH/WAN In Frames, In Errored Frames, In Discarded, and Out Frames
counts). The operational measurements collected by the 4xGE EPL circuit
pack are divided into two groups:
• generic interface operational measurements (based on the Interfaces Group
MIB, RFC 1213, RFC 2233, RFC 2863) and applies to the GE LAN and
WAN interface.
• Ethernet specific operational measurements (based on RFC 2665
Ethernet-Like MIB) and applies to the GE LAN interface only.
For more information, refer to Operational measurements on page 6-80.
System lineup and testing

System lineup and testing (SLAT) is the process of bringing a newly installed
OME6500 network element to an in-service state ready for carrying traffic.
Refer to Commissioning and Testing, 323-1851-221 for detailed procedures.
OME6500 supports a Commissioning Assistant Tool (CAT) that guides the

user through the network element SLAT process step by step. The CAT is a
Site Manager application.
For more information, refer to Commissioning and testing on page 6-20.
Loopbacks
The OME6500 supports facility and terminal loopbacks on OC-n/STM-n, GE,
DS3/EC-1, DS1, and E1 ports. The loopbacks provide a quick and reliable way
to sectionalize connections during testing and troubleshooting.
For more information, refer to Loopbacks on page 6-27.
Data management
The network element is responsible for the resilience of its provisioning data.
Each piece of provisioning data exists on at least two separate circuit packs
within the network element. Each circuit pack contains a copy of its
configuration data. The shelf processor contains a master copy of the
configuration data for all circuit packs installed on the shelf. Both
cross-connect circuit packs contain a copy of the shelf processor specific
configuration data.
The OME6500 provides the capability to backup and/or restore the

provisioning data to/from the local file system on the shelf processor and
to/from an external storage device.
For more information, refer to Backing up and restoring the network element
database on page 6-89.
Autodiscovery
Autodiscovery is used by the network management to build the network
topology for end-to-end connection management. The network management
application instructs the network element to transmit autodiscovery tags from
the interface circuit packs using the internal DCN. Messages received from
other network elements containing autodiscovery tags are stored and also
reported to the network management application. This process allows the
network management application to build the topology.
Note: DSM shelves remain hidden from the other network elements in the
network and are indicated in the autodiscovery information.


The OME6500 provides the following security and administration capabilities
managed from Site Manager:
• network element security
— security levels
— login sessions
— local password management
— security log/audit trail
— local user authentication
— challenge/response authentication
— centralized RADIUS authentication
— intrusion attempt handling
• network element administration
— network element naming
— date and time setting
— time of day administration
For more information, refer to Security and administration on page 6-81.
Data communication network

OME6500 uses an IP-based data communications infrastructure for network
element management and for interworking with IP-based network elements.
OME6500 also supports OSI based infrastructures for interworking with
OSI-based network elements.
The OME6500 supports the following types of management interfaces:

• central office LAN (COLAN) for interface to the DCN
• intershelf LAN (ILAN) for intershelf DCN
• RS-232 and 10/100Base-T for craft user interface
• section/RS and line/MS DCC for OAM&P access to remote network
elements
For more information, refer to OME6500 OAM comms on page 6-68 and
Appendix A: Data communications planning on page 10-1.
OME6500 management
Site Manager
The OME6500 supports a comprehensive suite of OAM&P functionality
which can be managed through the Site Manager craft user interface. The Site
Manager craft user interface is a graphical, nodal management tool that is
available on a CD or can be downloaded from the shelf processor.
The Site Manager craft user interface is platform independent, running

natively on Windows, UNIX and Solaris workstations ensuring field
technicians and network operations centre (NOC) operators are operating with
the same view.
For more information, refer to User interface description on page 5-1.
TL1 user interfaces

Transaction Language 1 (TL1) is an industry recognized common language
protocol that allows an operating system to communicate with different vendor
equipment.
OME provides a TL1 command line interface (CLI). The TL1 CLI is a
standard command line interface. The OME6500 TL1 interface conforms to
standards GR-831, GR-833, and GR-199 for syntax, information structure, and
transactions.
For more information, refer to TL1 interface on page 5-2.
Interworking with Nortel portfolio

OME6500 is compliant with SONET/SDH standards and therefore enables
interworking with other SONET/SDH compliant network elements.
OME6500 Release 1.2 operates with the following network management

software:
• Optical Manager Element Adapter (OMEA) Release 3.1
• Site Manager
OME6500 Release 1.2 interworks with the following Nortel products through
OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, OC-192/STM-64, or GE
optical interfaces, or DS3, EC-1, DS1, or E1 electrical interfaces (only if these
products support the associated interfaces):
• Optical Multiservice Edge 6110
• Optical Metro 4200
• Optical Cross Connect HDX/HDXc
• Optical Cross Connect DX
• S/DMS TransportNode OC-48
• TN-16X

• Optical Line System 1600, Wavelength Translator application

• Optical DWDM Terminal
Note: GE GFP-F interworking is only supported with Optical Metro 3500,
Optical Metro 5000, and Optical Cross Connect HDX/HDXc.
DWDM Interworking
The OME6500 OC-48/STM-16 and OC-192/STM-64 DWDM wavelengths
interwork with:
• the Optical Metro 5000-series optical multiplexer (OMX) product for
DWDM applications through the OC-48/STM-16 and OC-192/STM-64
DWDM optical interfaces. OME6500 supports 16 wavelengths in the
C-Band for interworking with the OMX. For more information, refer to
OMX applications on page 3-10 or the Optical Metro 5000 documentation.
• the Common Photonic Layer (CPL) product through the OC-48/STM-16
and OC-192/STM-64 DWDM optical interfaces. OME6500 supports 36
wavelengths in the C-Band for interworking with the CPL. For details of
the CPL applications, refer to the Common Photonic Layer Planning
Guide.
Refer to “1xOC-192/STM-64 circuit pack” on page 4-34 and
“2xOC-48/STM-16 circuit pack” on page 4-36 for more information about the
DWDM optical interfaces.
Interoperating with non-Nortel portfolio

The Optical Multiservice Edge 6500 shelf supports OC-3/STM-1,
OC-12/STM-4, OC-48/STM-16, and OC-192/STM-64 UPSR/SNCP
interoperability with other GR-1400 and ITU-T G.841 compliant vendors for
the purpose of passing traffic, routing, and network management data.
The Optical Multiservice Edge 6500 shelf supports OC-3/STM-1,

OC-12/STM-4, OC-48/STM-16, and OC-192/STM-64 1+1 and 0+1
interoperability with other vendors for the purpose of passing traffic, routing,
and network management data.
Interoperability with the Optical Multiservice Edge 6500 OC-192/STM-64

DWDM optical interfaces requires G.709 compatible optics.
The Optical Multiservice Edge 6500 does not support BLSR/MS-SPRing

interoperability with non-Nortel products, as the standards have not been
defined.
3-1
Applications and upgrades 3-
This chapter describes how the Optical Multiservice Edge 6500 (OME6500)
fits in a network and interworks with other Nortel products. This chapter also
describes the upgrade considerations for OME6500. Table 3-1 lists the topics
in this chapter.
Table 3-1
Topics in this chapter
Topic Page
Unprotected configuration 3-2
1+1/MSP linear 3-3
BLSR/MS-SPRing 3-4
UPSR/SNCP configuration 3-6
Gigabit Ethernet point-to-point application 3-7
Intra-office application 3-9
OMX applications 3-10
Common Photonic Layer applications 3-14
Network reconfiguration 3-14
Upgrade support 3-15
Note: OME6500 maps GE, DS3, EC-1, DS1, and E1 services to

appropriate STS/VT/VC containers which are assigned as STS/VT/VC
level connections. The traffic protection scheme supported by the
OC-n/STM-n interface circuit packs can therefore provide a protected GE,
DS3, EC-1, DS1, or E1 service without requiring a redundant handoff from
the subtending GE, DS3, EC-1, DS1, or E1 equipment. Refer to Gigabit
Ethernet point-to-point application on page 3-7 and Intra-office
application on page 3-9 for more information.
For an overview of the OME6500 applications supported by this release, refer

to OME6500 applications on page 1-4.

3-2 Applications and upgrades
Unprotected configuration
An unprotected connection configuration has a single pair of optical
fibers/electrical cables interconnecting network elements and is supported on
all interface circuit packs available in this release:
• 1xOC-192/STM-64
• 2xOC-48/STM-16
• 8xOC-3/12/STM-1/4 (including STM-1e electrical interfaces)
• 4xGE Ethernet Private Line (EPL)
• 24xDS3/EC-1
• 63xE1
• 84xDS1 TM (DSM)
Figure 3-1 shows the OME6500 network elements supporting unprotected line
configuration between OME6500 network elements and between other
network elements.
Figure 3-1
Unprotected configuration
HDX/HDXc
OME6500 NE OME6500 NE
Working Working
Unprotected
- OC-192/STM-64
Working
Working
Working
Working
- OC-48/STM-16
- OC-12/STM-4
- OC-3/STM-1
- STM-1e
- GE
SONET/SDH GE SONET/SDH GE
NE NE
For more information about unprotected configuration rules, refer to Ordering

Information, 323-1851-151. For more information about the unprotected
protection scheme, refer to Unprotected connections on page 6-67.
1+1/MSP linear
1+1/multiplex section protection (MSP) linear is a line level traffic protection
scheme and consists of a point-point configuration with two optical
fiber/coaxial cable pairs carrying the traffic (one for working and the other for
protection). Traffic is carried on both working and protection lines and the
receiving interfaces determine which line to select based on signal quality or
user-initiated actions. Table 3-2 provides an overview of the 1+1/MSP linear
protection scheme supported in this release.
Table 3-2
1+1/MSP linear overview
Facility Protection Interface circuit Maximum number of protection pairs
modes packs per OME6500 network element
OC-3/STM-1, • unidirectional/ 1xOC-192/STM-64 2 (single port circuit pack by 2-paired
STM-1e (see Note), bidirectional slots)
OC-12/STM-4, • nonrevertive 2xOC-48/STM-16 12 (two-port circuit pack by 6-paired
OC-48/STM-16,
slots)
OC-192/STM-64
8xOC-3/12/STM-1/4 48 (eight-port circuit pack by 6-paired
slots)
84xDS1 TM (on DSM) 1 per DSM, up to 16 DSMs per
OME6500 shelf
Note: The STM-1e SPF modules are installed on the 8xOC-3/12/STM-1/4 circuit pack.
The OME6500 supports 1+1/MSP linear protection switching on a per port

basis provisionable by software. The OME6500 carries working and
protection lines on adjacent slots for equipment redundancy. Figure 3-2 shows
OME6500 network elements connected by 1+1/MSP linear protection
between OME6500 network elements and between other network elements.
For more information about 1+1/MSP linear protection configuration rules,

refer to Ordering Information, 323-1851-151. For more information about the
1+1/MSP linear protection scheme, refer to 1+1/MSP linear traffic protection
on page 6-59.

Figure 3-2
1+1/MSP linear configuration
HDX/HDXc
Working Working
Protection Protection
1+1/MSP linear
Protection
Protection
- OC-192/STM-64
Working
Working
- OC-48/STM-16
- OC-12/STM-4
- OC-3/STM-1
- STM-1e
SONET/SDH SONET/SDH
NE NE
BLSR/MS-SPRing
A 2-Fiber bidirectional line-switched ring (BLSR)/multiplex section shared
protection ring (MS-SPRing) is a line level traffic protection scheme. A
2-Fiber BLSR/MS-SPRing is a ring network of nodes interconnected by a pair
of optical fibers. Each optical fiber carries both working and protection
channels, the bandwidth being divided into two equal halves, one half for
working and the other half for protection. The user assigns traffic to the
working channels in either direction around the ring. The protection channels
travel around the ring in the opposite direction to the working channels that
they protect.
Table 3-3 provides an overview of the BLSR/MS-SPRing protection scheme

supported in this release.
Table 3-3
BLSR/MS-SPRing overview
Facility Interface circuit Maximum number of

packs protection groups per
OME6500 network element
OC-48/STM-16, 1xOC-192/STM-64 4
OC-192/STM-64
2xOC-48/STM-16
The OME6500 supports BLSR/MS-SPRing protection on a per port basis

provisionable by software on the OC-48/STM-16 or OC-192/STM-64
interfaces. The east and west pair of interfaces must be provisioned on adjacent
slots. Figure 3-3 shows OME6500 network elements connected by
BLSR/MS-SPRing protection between OME6500 network elements.
For more information about BLSR/MS-SPRing protection configuration rules,

refer to Ordering Information, 323-1851-151. For more information about the
BLSR/MS-SPRing protection scheme, refer to 2-Fiber BLSR/MS-SPRing
traffic protection on page 6-61.
Figure 3-3
BLSR/MS-SPRing configuration
Working/protection
Working/protection
Working/protection
BLSR/MS-SPRing
- OC-192/STM-64
- OC-48/STM-16
Working/protection

UPSR/SNCP configuration
OME6500 supports subtending unidirectional path switched ring
(UPSR)/subnetwork connection protection (SNCP) configurations.
The UPSR/SNCP function provides:

• the capability of eliminating subtending head-end nodes with back-to-back
tributaries by terminating the UPSR/SNCP directly on the OME6500
• a single OME6500 network element to terminate several UPSR/SNCP
systems, as well as providing unrestricted cross-connects across all
UPSR/SNCP configurations in a non-blocking fashion
• simplicity (no coordination required between the network elements)
In a UPSR/SNCP 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 (see Figure 3-4). 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.
Figure 3-4
UPSR/SNCP configuration
Node B
Node A Node C
Legend
Node D
= Signal
= Path selector
Table 3-4 provides an overview of the UPSR/SNCP protection scheme

supported in this release.
Table 3-4
UPSR/SNCP overview
Facility Protection Interface circuit Maximum configurations per OME6500

modes packs network element (see Note 1)
OC-3/STM-1, • nonrevertive 1xOC-192/STM-64 80/0 and 160/0 XCs
STM-1e (see Note 2), 2xOC-48/STM-16 • 512 STS-1/VC3
OC-12/STM-4,
OC-48/STM-16, 8xOC-3/12/STM-1/4 • 170 STS-3C/VC4
OC-192/STM-64 4xGE EPL 80/20 XC
GE WAN • 512 STS-1/VC3
• 170 STS-3C/VC4
• 3584 VT1.5
• 3072 VC12
20/20 XC
• 128 STS-1/VC3
• 42 STS-3C/VC4
• 3584 VT1.5
• 3072 VC12
80/80 XC
• 128 STS-1/VC3
• 42 STS-3C/VC4
• 4480 VT1.5
• 3840 VC12
Note 1: The maximum number of UPSR/SNCP configurations depends on the number of
cross-connects destinations. Figures quoted are for bidirectional connections using 2WAYPR
connections (three destinations per connection).
Note 2: The STM-1e SPF modules are installed on the 8xOC-3/12/STM-1/4 circuit pack.
Gigabit Ethernet point-to-point application

OME6500 supports GE point-to-point applications by mapping the GE client
signal into SONET/SDH containers using Framed-Generic Framing
Procedure (GFP-F). This mapping enables the assignment of STS-1/VC3/VC4
level connections across OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, or
OC-192/STM-64 for transport across the OME6500 network or handoff to
other SONET/SDH networks.

This release supports the assignment of GE using:

• STS-1 and VC4 connections
• contiguous concatenation at STS-3c, STS-12c/VC4-4c, and
STS-24c/VC4-8c levels
• virtual concatenation at STS-1-nv/VC3-nv (n = 1 through 21) or
STS-3c-nv/VC4-nv (n = 1 through 7)
OME6500 maps GE to STS/VC containers which are assigned as STS/VC
level connections. The traffic protection scheme supported by the
OC-n/STM-n interface circuit packs can therefore provide a protected GE
service without requiring a redundant handoff from the subtending GE
equipment. If protection is required for the Ethernet side of the GE circuit
packs, dual unprotected connections can be used with a L2/L3 protection
scheme (not part of OME6500).
The assignment of GE to SONET/SDH containers and the use of contiguous

and virtual concatenation enables users to provide either full rate or sub rate
GE services. The assignment flexibility allows users to offer GE services from
50 Mbit/s to 1200 Mbit/s (full rate).
Figure 3-5 shows an example of a GE point-to-point application across an

OME6500 1+1/MSP linear system and GE handoff to an SONET/SDH
network through OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, or
OC-192/STM-64 interfaces.
Figure 3-5
OME6500 GE point-to-point application
Working Working
SONET/SDH
Network
Protection Protection
1+1/MSP linear
- OC-192/STM-64
Working
Working
- OC-48/STM-16
- OC-12/STM-4
- OC-3/STM-1
Hand-off to SONET/SDH network
at OC-3/STM-1, OC-12/STM-4,
OC-48/STM-16, or OC-192/STM-64
GE GE
Intra-office application
OME6500 supports DS1, DS3/EC-1, E1, and STM-1e intra-office applications
where DS1, DS3, EC-1, E1, and STM-1e interfaces are used as the primary
intra-office connection medium.
OME6500 maps the DS1, DS3, EC-1, or E1 signals to SONET/SDH

containers (VT1.5 for DS1, STS-1/LO-VC3 for DS3, STS-1 for EC-1, and
VC12 for E1) which are assigned as appropriate connections. The traffic
protection scheme supported by the OC-n/STM-n interface circuit packs can
be used provide a protected service through the SONET/SDH network.
OME6500 provides 1:N equipment protection of the DS3/EC-1 and E1 circuit

packs (2 banks of 1:4 protection) and 1+1 protection of the DS1 circuit packs.
If any of the working circuit packs fail or are removed, the system switches all
the services to the protection circuit pack to maintain the availability.
Figure 3-6 shows an example of an intra-office application and handoff to an

SONET/SDH network through OC-n/STM-n.
Figure 3-6
OME6500 intra-office application
Copper digital
distribution frame
(DDF)
DS1,
SONET/SDH DS3/EC1, OME6500
NE E1, NE
STM-1e Metro
Long Haul
SONET/SDH SONET/SDH
network network
BLSR/MS-SPRing
1:N (DS3/EC1 and E1) Hand-off to SONET/SDH
or 1+1 (DS1)equipment network at OC-3/STM-1,
protection OC-12/STM-4, OC-48/STM-16,
or OC-192/STM-64

OMX applications
The optical multiplexer (OMX) module is a multiplexer and demultiplexer
capable of supporting up to four wavelengths (one band).
Each OMX module contains passive optical filters that add and drop up to four
channels in the assigned wavelength band. The OMX module can multiplex
four wavelengths (channels) into an optical band. The bands can then be
optically combined into a single optical fiber and can be added to other bands
in an optical fiber path. See Figure 3-7.
Additional OMX modules are required for each DWDM band. The DWDM
bands can be multiplexed onto one optical fiber to daisy-chain the OMX
modules together.
OMX modules can be interconnected to provide a working and protection

traffic path. A single OMX module supports unprotected traffic.
Figure 3-7
OME6500 and OMX interconnect
OME OME OME OME OME OME OME OME

6500 6500 6500 6500 6500 6500 6500 6500
λ8 λ7 λ6 λ5 λ4 λ3 λ2 λ1
OMX OMX
Single
patch fiber
Single fiber
Network sites
There are two types of sites in an OME6500 network:
• terminal sites
• optical add/drop multiplexer sites (OADM)
Terminal sites consist of single or multiple OME6500 shelves where
wavelengths must be added or dropped. Terminal sites are sometimes called
hub sites when used in hubbed-ring configurations.
At an OADM site, single or multiple OME6500 shelves are placed to gain

access to specific wavelengths in the system, so that some wavelengths are
terminated, and some are optically passed through at that location. OADM
sites are sometimes called remote sites.
DWDM configurations
The following OMX configurations are supported:
• hubbed-ring
• a meshed-ring
• linear point-to-point
Hubbed-ring configuration
The hubbed-ring configuration is optimized for traffic flows that are
characteristic of access networks. For an example of a hubbed-ring
configuration, see Figure 3-8 and Figure 3-9.
Note: The OME6500 shelf provides up to four OC-192/STM-64 DWDM

optical interfaces or up to 24 OC-48/STM-16 DWDM optical interfaces
(or a mixture of the OC-192/STM-64 DWDM and OC-48/STM-16
DWDM optical interfaces).
Multiple OME6500 shelves can be installed at the terminal to provide one

wavelength for each wavelength dropped at the OADM shelves in the hubbed
ring. Four wavelengths are grouped into one band. The same wavelength band
is assigned to the terminal shelves and the corresponding OADM shelves.
Figure 3-8
Physical connections in a hubbed-ring configuration
Terminal site
OMX OMX OMX

1 2 3
OADM site
OADM site
OMX
1
OMX
3
OMX
2

Figure 3-9
Logical connections in a hubbed-ring configuration
Terminal
OME OME OME
6500 6500 6500
1 2 3
OADM
OADM OME
6500
OME 1
6500 OME
3
6500
2
Meshed-ring configuration
The meshed-ring configuration is optimized for traffic flows that are
characteristic of interoffice networks. For an example of a meshed-ring
configuration, see Figure 3-10 and Figure 3-11.
Individual wavelengths can be added or dropped at different locations. You

can also reuse wavelengths.
Band meshing and channel meshing are both supported.
Band meshing allows the system to drop and add all wavelengths of a given
band at one node or at multiple nodes in the network. Other bands can be
passed through the system.
Channel meshing provides the capability for any channel from one node in the
network to be terminated (added or dropped) at any other node in the network
and at multiple nodes in the network.
Note: The OME6500 shelf provides up to 4 OC-192/STM-64 DWDM

optical interfaces or up to 24 OC-48/STM-16 DWDM optical interfaces
(or a mixture of the OC-192/STM-64 DWDM and OC-48/STM-16
DWDM optical interfaces).
Figure 3-10
Physical connections in a meshed-ring configuration
OADM or
Terminal site
OME OME
6500 6500
1 2
OADM–site C OADM–site A
OME OME
6500 6500
OADM–site B
OME OME
6500 6500
Figure 3-11
Logical connections in a meshed-ring configuration
OADM or
Terminal site
OME OME
6500 6500
1 2
OADM–site C OADM–site A
OME OME
6500 6500
OADM or
Terminal site B
OME OME
6500 6500

Linear point-to-point
A point-to-point configuration transports traffic between two sites on a
protected OMX DWDM system. Two fiber spans between the sites in a
DWDM point-to-point configuration have the same functionality as up to 32
fiber spans in a non-DWDM point-to-point configuration. An OMX shelf is
required at both sites. The fiber connects to the OTS OUT on the OMX module
at one site, and the OTS IN on the OMX module at the other site. See Figure
3-12 for an example of a point-to-point configuration for four channels.
Figure 3-12
DWDM point-to-point configuration
Physical Connections Logical Connections
OME OME OME OME

6500 6500 6500 6500
OME OMX OMX
OME OME OME
6500 6500 6500 6500
OME OME OME OME
6500 OMX OMX 6500 6500 6500
OME OME OME OME
6500 6500 6500 6500
Common Photonic Layer applications

OME6500 interworks with Common Photonic Layer (CPL) applications
through the OC-48/STM-16 and OC-192/STM-64 DWDM interfaces. For
details of the CPL application, refer to the Common Photonic Layer Planning
Guide.
Network reconfiguration
OME6500 supports the following in-service reconfigurations:
• addition of an OME6500 network element to an OME6500 linear ADM
chain
• addition of an OME6500 network element to a linear chain
• addition/deletion of an OME6500 network element into/from an
OME6500 UPSR/SNCP configuration
• addition/deletion of an OME6500 network element into/from an
OME6500 BLSR/MS-SPRing configuration
For a list of change application procedures for supported network
reconfigurations, refer to Ordering Information, 323-1851-151.
Note 1: Some other network reconfigurations scenarios are available

on-demand. Contact your Nortel Networks representative for more
information (refer to Technical assistance on page 9-1).
Note 2: OME6500 also supports non-standard network reconfigurations.
Contact your Nortel Networks representative for more information (refer
to Technical assistance on page 9-1).
Upgrade support
This section provides information when planning upgrades on the OME6500.
Software
The OME6500 supports the following in-service software upgrades:
• OME6500 Release 1.1 to OME6500 Release 1.2 (GA)
Note 1: When upgrading to Release 1.2, you must also upgrade the Site
Manager software.
Note 2: Upgrades must be performed following a specific procedure.
Refer to the upgrade change application procedure (CAP), NTRN38AA,
for more details and detailed upgrade procedures.
Hardware
No hardware upgrades are required when upgrading to Release 1.2 unless you
require the new functionality provided by new circuit packs.
Note: The DSM shelves introduced in Release 1.2 require cross-connect

circuit packs and optical interface circuit packs that support VT1.5/VC12
granularity.
Reconfiguration to new cross-connect circuit packs and optical interface

circuit packs that support VT1.5/VC12 granularity can be performed
in-service. Detailed procedures for reconfiguring the cross-connect and optical
interface circuit packs are provided in Module Replacement Procedures,
323-1851-545.

4-1
Hardware description 4-
This chapter provides an overview of the Optical Multiservice Edge 6500

(OME6500) hardware. This chapter describes the OME6500 shelf, circuit
packs, cooling system, power management and bay configurations as listed in
Table 4-1.
Table 4-1
Topic Page
Hardware architecture 4-2
Cooling configurations 4-5
Breaker interface panel (optional) 4-9
Shelf 4-17
Access panel 4-19
Electrical interface area 4-21
Maintenance interface card 4-23
Power input card 4-24
Shelf processor 4-25
Cross-connect circuit packs 4-27
Synchronization hardware 4-30
Interface circuit pack descriptions 4-31
Filler card 4-45
I/O and protection hardware 4-49
Fiber/cable routing channel 4-53
Shelf cover 4-54
Optical multiplexer 4-55
Fiber manager 4-56

4-2 Hardware description
Hardware architecture
The OME6500 platform consists of the following modular components:
• breaker interface panel (optional)
• cooling unit
• OME6500 shelf which contains the following components:
— common equipment (access panel, shelf processor, cross-connect
circuit packs, power input cards, and maintenance interface card)
— interface circuit packs
— optical fiber/cable routing channel
• electrical interface chassis (optical/front electrical shelf assembly and
optical/rear electrical shelf assembly)
• DS1 service module (DSM) shelf (peripheral shelf that connects to the
OME6500 shelves via OC-3 interfaces)
Shelf assemblies
OME6500 provides three shelf assemblies as follows:
• optical shelf assembly
• optical/front electrical shelf assembly
• optical/rear electrical shelf assembly
Refer to Ordering Information, 323-1851-151, for the product engineering
codes (PEC) information.
The optical shelf assembly is used in applications where only optical services
(see Note) will be deployed and contains the OME6500 shelf and integrated
optical fiber/cable routing channel/air plenum. Figure 4-1 shows a view of the
optical shelf assembly.
Note: The optical shelf assembly can support electrical services if using
DSM DS1 services or using STM-1e SFP modules on the
8xOC-3/12/STM-1/2 circuit packs.
Figure 4-1
Cooling unit
(3 U / 132.6 mm/ 5.2 in.) Shelf
Optical shelf assembly Fiber/cable

(10 U / 444.5 mm/ 17.5 in.) routing channel/
air plenum
440.5 mm /
17.3 in.
280.0 mm /
11.0 in.
Optical/front electrical shelf assembly

The optical/front electrical shelf assembly supports both optical and electrical
services and is used in applications where electrical services are planned to be
deployed. The shelf assembly contains the OME6500 shelf, an integrated
optical fiber/cable routing channel, and an electrical interface chassis which
houses the electrical interface modules. Figure 4-2 shows a view of the
optical/front electrical shelf assembly.
Note: The optical shelf assembly cannot be upgraded in-service to support

electrical services (except DSM DS1 and STM-1e SFP services). If you
plan to deploy electrical services other than DSM DS1 or STM-1e SFPs in
the future (including 10/100Base-T services which are not currently
available), you must deploy the optical/front electrical shelf assembly if
you require front access electrical connections.

Figure 4-2
Optical/front electrical shelf assembly
Cooling unit
(3 U / 132.6 mm/ 5.2 in.)
Shelf
Fiber/cable
routing channel
Optical/front electrical
shelf assembly Front access
(18 U / 800.1 mm/ 31.5 in.) electrical interface
440.5 mm /
280.0 mm / 17.3 in.
11.0 in.
Optical/rear electrical shelf assembly

The optical/rear electrical shelf assembly supports both optical and electrical
services and is used in applications where electrical services are planned to be
deployed. The shelf assembly contains the OME6500 shelf and an integrated
optical fiber/cable routing channel, though this is smaller in size than the
channel on the optical shelf and optical/front electrical shelf assemblies. A
separate air plenum is required for each optical/rear electrical shelf assembly
or pair of optical/rear electrical shelf assemblies. Electrical interface modules
can be installed on the backplane at the rear of the shelf for rear access. Figure
4-3 shows a view of the optical/rear electrical shelf assembly.
Note: The optical shelf assembly cannot be upgraded in-service to support

electrical services (except DSM DS1 and STM-1e SFP services). If you
plan to deploy electrical services other than DSM DS1 or STM-1e SFPs in
the future (including 10/100Base-T services which are not currently
available), you must deploy the optical/rear electrical shelf assembly if you
require rear access electrical connections.
Figure 4-3
Optical/rear electrical shelf assembly
Shelf
shelf assembly
(8 U / 355.6 mm/ 14 in.)
Fiber routing
channel
Rear access
electrical interface
440.5 mm /
17.3 in.
280.0 mm /
11.0 in.
Note: Each optical/rear electrical shelf or pair of optical/rear

electrical shelf requires a cooling unit and an air plenum.
Cooling configurations
The OME6500 supports flexible cooling configurations which includes front,
rear, and top venting. The fan unit draws air from the bottom of the shelf and
vents it through the front, rear, or top of the shelf. The protective grill/air
deflector can be easily adjusted to deflect air either towards the top or bottom
of the bay for operational convenience. Figure 4-4 provides an overview of the
different cooling configurations supported by the OME6500.

Figure 4-4
OME6500 cooling configurations
Front Venting Rear Venting Top Venting
Cooling units Cooling units Cooling units
OME6500 OME6500 OME6500

shelf shelf shelf
Fiber routing/ Fiber routing/ Fiber routing/

air plenum air plenum air plenum
Side view Side view Side view
The OME6500 cooling system consists of the following components:

• cooling shelf installed at the top of the OME6500 shelf and contains the
following:
— front, rear, or top venting cooling unit kit
— three front, rear, or top cooling fan modules
Note 1: Each venting option requires different fan modules.
Note 2: When deploying the optical/rear shelf assembly, one cooling unit
and air plenum can support two optical/rear shelf assemblies.
• front intake air plenum
— integrated with the optical fiber/cable routing channel and located at
bottom of the optical shelf assembly and the optical/front electrical
shelf
— separate item for optical/rear shelf assembly (supports a single or a pair
of optical/rear shelf assemblies).
Note: The optical/front electrical shelf assembly does not require an air
plenum as air is drawn from the bottom of the shelf through the electrical
interface chassis.
Refer to Ordering Information, 323-1851-151, for the PEC information.

Figure 4-5 shows the components of the cooling system (optical shelf shown).
Figure 4-5
OME6500 cooling system
Cooling
unit
Fiber/cable
routing
channel
Air plenum
(integrated on optical
shelf assembly, separate
on optical/rear electrical
shelf assembly)
The cooling unit contains three fans and draw air from the bottom of the shelf
through an air filter and vented through the front, rear, or top of the shelf
depending on the cooling unit. Figure 4-6 shows the cooling system
components and air flow (shows front venting option).

Figure 4-6
Cooling unit components
Fan
modules
Grill/air
deflector
Spring-loaded
pin
The fans operate at variable speeds depending on the cooling required.

Temperature sensors in the fan units detect temperature changes. Table 4-2
lists the four supported cooling system states.
Table 4-2
Cooling system states
Temperature Fan status
Below -14oC all fans OFF
-14oC to +12oC one fan ON at 75% maximum speed
+12oC to +55oC all fans ON at 75% maximum speed
Above +55oC all fans ON at 100% maximum speed
Note 1: If one of the fans fail or is removed and the temperature is above +12oC,
the remaining fans operate at 100% maximum speed.
Note 2: When the temperature exceeds +71oC, the system raises the ‘High
Temperature Alarm’ and all fans continue to operate at 100% maximum speed.
Breaker interface panel (optional)

The OME6500 shelf supports redundant power feeds from separate -48/60 V
dc power sources. An OME6500 specific breaker interface panel (BIP) can be
used for power distribution and management to the OME6500 shelves on a per
bay basis. The BIP is installed at the top of the rack and can support up to four
shelves terminating in a single rack.
This release supports three BIP variants:

• OME6500 BIPs
— NTK599AA: 2 x 100 A input with D-type alarm connectors providing
4 x 40 A outputs per feed
— NTK599BA: 4 x 40 A (or optional 2 x 80 A) input with D-type alarm
connectors with optional wire-wrap adaptor providing 4 x 40 A outputs
per feed
• DSM BIP
— NTN458RA: 2 x 100 A input with wire-wrap alarm connectors
providing 8 outputs per feed (4 x 20 A, 1 x 15 A, and 3 x 5 A)
OME6500 BIPs
The BIP attributes are as follows:
• input connections for:
— two independent A and two independent B, -48/60 V dc supplies
(NTK599AA) with rear access connections
— four independent A and four independent B, -48/60 V dc supplies
(NTK599BA) with front access connections and the capability of
linking adjacent input feeds
• input connection point (2 x M6 studs) for bonding the protective earth (PE)
to the BIP chassis
• 160 A maximum input current (4 x 40 A circuit breakers per A and B feed
providing eight circuit breakers mounting capability)
• eight circuit breakers, four connected to ‘A’ negative input(s) and four
connected to ‘B’ negative input(s)
• eight output power connectors, four connected to ‘A’ negative input(s) and
four connected to ‘B’ negative input(s) with either rear access connectors
(NTK599AA) or front access connectors (NTK599BA).
• 19 in./23 in./ETSI rack mount, 1 U high unit (NTK599AA) or 2 U high
unit (NTK599BA), and 280 mm deep
• circuit breaker trip indication (circuit breaker type to be On, Off or trip
position)

• alarm unit for bay level alarm gathering, display (critical, major and minor
lamps for the frame), and alarm reset. For the NTK599BA variants, the
alarm unit is field replaceable.
• input and output alarm connectors/wire-wrap fields (D-type for
NTK599AA, D-type/wire-wrap field for NTK599BA)
• visual alarm inputs and outputs (NTK599AA) or visual and audible alarm
inputs and outputs (NTK599BA)
• optional battery return (BR) to frame ground (FG) strap
Figure 4-7 shows a front view of the BIP (1U variant). Figure 4-8 shows a rear
view of the BIP (NTK599AA variant). Figure 4-9 shows a front view of the
BIP (2U variants).
Input power connection
The BIP operates over the steady state input voltage range of -40.0 V to
-75.0 V dc with overvoltage transients. Each input supply feed consists of up
to two 100 A separate feeds (NTK599AA) or four 40 A (or two 80 A with
application of optional external jumpers) separate feeds (NTK599BA) for each
A and B power input. Input power connectors to the BIP are made using two
shrouded terminal block assemblies for each of the A and B input power feeds.
The input terminals, with lugs in position, are protected from inadvertent
access preventing the shorting of any negative terminal to any positive
terminal, or any terminal to frame.
The BIP has a pair of M6 studs for connection to protective earth (PE). These
studs work with double hole crimp terminals. This connection point is separate
from the two points where the optional connection can be made between the
common A and B feed returns and PE.
The BIP also provides for input reverse polarity protection in that reversing the
polarity does not affect the characteristics of the BIP.
The BIP provides LEDs to indicate the status of each of the A or B input power
feeds as follows:
• green FLT LED (one for the A feed (FLTA) and one for B feed (FLTB))
illuminated under normal operating conditions to indicate that each power
interface (A or B) feed has two power feeds
The green FLT LED extinguishes to indicate either or both of the following
conditions:
— the input feed on the side (A or B) of the module below -39 V dc ± 1 V
dc
— an open fuse in the capacitor module
Output power connection

The BIP provides eight output power connectors where four connect to the ‘A’
negative input and four connect to the ‘B’ negative input. All eight power
output connectors are 3-way (NTK599AA) or 2-way (NTK599BA) Combo
D-type panel mount shell.
Circuit breakers
The BIP provides eight plug-in rocker switch circuit breakers where four
connect to the ‘A’ negative input and four connect to the ‘B’ negative input.
Alarm input
The BIP receives:
• three alarm signals (Critical, Major and minor visual alarms) from the
OME6500 through a 9-way D-type connector (Male/Pin type) alarm input
interface (NTK599AA)
• three alarm signals (Critical, Major and minor visual and audible alarms,
six inputs) from the OME6500 through a 9-way D-type connector
(Female/receptacle type) alarm input interface (NTK599BA)
Refer to BIP connector pinouts on page 7-10 for details on the connector
pinouts.
For the NTK599AA BIP, the external alarm signal activation is a relay contact
to -48/60 V dc return (RTN). The incoming alarm signal energizes a relay in
the BIP and causes illumination of the corresponding alarm LEDs on the alarm
unit.
For the NTK599BA BIP, the external alarm signal activation is a loss of a relay
contact to -48/60 V dc return (RTN). The loss of the alarm signal energizes a
relay in the BIP and causes illumination of the corresponding alarm LEDs on
the alarm unit.
Note: If using the alarm input on the NTK599BA BIP, you must use either
a Issue 3 or later SDH access panel (NTK505LA) or a SONET/J-SDH
access panel (NTK505MA).

Figure 4-7
OME6500 BIP (NTK599AA) - front view
Major
Breaker interfaces Critical Minor
ALARM-IN 4x40 A
(DB-9 male) A feed B feed
Filter-B
Bracket status Bracket
Filter-A LED Power
ALARM OUT status Alarm
test
(DB-25 male) reset
Rack alarm unit
Figure 4-8
OME6500 BIP (NTK599AA) - rear view
B3 B1
B4 B2
A3 A1
A4 A2
BAT B2- BAT B1- RTN B2+ RTN B1+ RTN A2+ RTN A1+ BAT A2- BAT A1-
Figure 4-9
OME6500 BIP (NTK599BA) - front view
Alarm cutoff
With front cover on Lamp test
Status A feed status
Breakers
B feed status
With front cover open (wire-wrap variant shown

for the Alarm out connector) Power landing
area
Alarm in
Output power
Front cover cable area
Diagram
(inside the cover)
Alarm out
Detail for D-sub

adaptor variant
Alarm output
The BIP provides an alarm output interface through a 25-way D-type, pin/male
connector (NTK599AA) or a 25-way D-type, pin/male or wire-wrap field
(NTK599BA) and provides the following output alarms:
• three visual bay alarms (critical, major and minor)
• three audible bay alarms (critical, major and minor) (NTK599BA only)
• power alarm
• circuit breaker alarms

The NTK599AA and NTK599BA BIPs do not contain an internal audible

alarm. However, an audible alarm signal from other equipment can be passed
through the NTK599BA BIP and carried on the alarm contacts provided within
the input/output connectors.
The relays of the NTK599AA BIP are de-energized when there is no alarm
condition, and energized in an alarm condition. The relays of the NTK599BA
BIP are energized when there is no alarm condition, and de-energized in an
alarm condition. ‘Normal’ (N/O and N/C) refers to a de-energized relay. The
three relay contacts are:
• COM (common) - the contact connected to either of the other two contacts
• N/O (normally open)
• N/C (normally closed)
Refer to BIP connector pinouts on page 7-10 for details on the connector
pinouts.
Alarm unit
The alarm unit (AU) contains LEDs to provide visual indication of alarms
active for the OME6500 installed on the rack. The alarm unit illuminates the
appropriate LEDs (critical, major and minor) on the front panel of the BIP
based on alarm signals received from the OME6500 shelves through the alarm
input interface and close the appropriate alarm relay contacts on the alarm
output interface.
The alarm unit contains the following LEDs:

• red and yellow alarm LEDs fed from the input alarm signals illuminate to
indicate the following conditions:
— critical alarm (red)
— major alarm (red)
— minor alarm (yellow)
• red power LED illuminates to indicate either or both of the following
conditions:
— tripped circuit breaker on either side (A or B)
— open alarm unit fuse
The alarm unit contains an LED test button on the front panel of the BIP. When
pressed, all LEDs illuminate. The alarm unit also contains a push button switch
(ACO) on the BIP front panel to reset all BIP alarm relays. The alarm unit is
field replaceable on variants NTK599BA.
DSM BIP
The DSM BIP is mounted at the top of the equipment frame and is fed by two
redundant office battery inputs (-48 V dc). The breaker interface panel (BIP)
NTN458RA supports four breakers at 20 A, three breakers at 5 A, and one
breaker at 15 A per feed. The BIP can accommodate eight DSMs.
Figure 4-10 shows views of the DSM BIP (NTRN458RA variant).

Power input alarm
This circuit detects input power failure. A green light “on” indicates normal
operation. If input power has been lost, this light is off. In normal operation,
the power input alarm external relay contacts are in an energized or powered
state. The contacts are in a deenergizing or powered-off state when input
power is lost, providing common (C) to normally closed (NC) closure for the
alarm state.
Breaker alarm
Breaker alarms operate in one of two ways. Both methods have a red indicator
light “off” for normal operation and “on” when the alarm circuit is activated.
The first method uses indicating type breakers that provide a mechanical
connection to activate the alarm card. The second method uses open-circuit
electronic sensing across the fuse holder. Open-circuit detection usually
requires a reset switch to clear the breaker alarm.
Both methods have the breaker alarm external relay contacts deenergized or in
a powered-off state for normal operation and energized or in a powered-on
state when a breaker alarm is detected, providing common (C) to normally
open (NO) closure for the alarm state.
Bay alarms
Bay alarms are visual indications for the rack frame (system level). These
alarms can be a combination of three different levels: critical, major, and
minor. Critical alarms are red; a major alarm can either be a red or yellow; and
the minor alarm is always yellow. The external alarm contacts are deenergized
or in a powered-off state for normal operation and energizing or going to a
power-on state when an external alarm is detected. Activation of these types of
alarms comes from external equipment alarm contacts that are either in the
rack frame or system and provide an alarm ground to the input ports of the
alarm system.
Alarm circuits
Most monitoring alarm systems require an alarm ground signal to activate the
individual alarms. The most common, is a single-point contact or paralleled
contact configuration. An alarm ground wire connects to the common of the
external relay contact, and the associated NC or NO contact connects to the
alarm monitoring system. When the alarm activates, the relay closure between
the C and either the NC or NO sends an alarm ground to the alarm monitoring

system, activating the appropriate alarm. Multiple relay contacts can be

paralleled in this configuration to activate a single or multiple input to the
alarm monitoring system.
Figure 4-10
DSM BIP (NTN458RA)
Output
connectors
B A
Rear view
(rotated)
TOP OF PANEL
PWR FUSE
ALM ALARM BAY ALARMS
VIS AUD CONTACTS ACTIVATE
CR
NO NC NC NO C A R
MJ
NC NO NC NO C A R
MN
C C NC NO C A R
5"
Top view
23" bracket
19" bracket
A B
Front view
Output breakers Output breakers
power A power B
Shelf
Figure 4-11 provides an overview of the OME6500 shelf layout.
Figure 4-11
OME6500 shelf layout
Access panel
Power input
card
ESD jack (slot 17, subslot 1)
location Maintenance
interface card
(slot 17, subslot 2)
ESD jack location

Power input
card
(slot 17, subslot 3)
Fiber/cable
routing channel
Shelf processor
slots
(slots 15 and 16)
Service interface Service interface
slots (slots 1 to 6) slots (slots 9 to 14)
Cross-connect
slots (slots 7 and 8)
The OME6500 shelf consists of seventeen 25 mm (1 in.) slots and

accommodates both the common equipment and interface circuit packs:
• common equipment
— access panel (AP) located on the top of the OME6500 shelf
— maintenance interface card (MIC) located in slot 17, subslot 2
— power input cards located in slot 17, subslots 1 and 3
— cross-connect circuit packs located in slots 7 and 8
— shelf processor (SP) located in slots 15 and 16
Note: This release supports one shelf processor located in slot 15.
• interface circuit packs located slots 1-6 and slots 9-14

The OME6500 shelf also contains a fiber/cable routing channel located at the
bottom of the shelf used to manage optical fiber/cabling entering and exiting
the shelf. For the optical shelf assembly, the fiber/cabling routing channel
includes an integral air plenum (see Cooling configurations on page 4-5).

Refer to Ordering Information, 323-1851-151, for more information about

engineering rules.
Backplane
All interface circuit packs and the access panel interfaces, cooling system, and
electrical interfaces interconnect through the backplane which provides a
number of mechanisms for inter-card communications and control.
• a link for sending status information between the shelf processor and the
interface circuit packs
• a link for sending status information between adjacent slots and between
ports on interface circuit pack slots and the cross-connect circuit pack slots
• Ethernet – 100Base-T link between each circuit pack and the shelf
processor used for OAM
• control signaling – dedicated links between cards to provide simple
presence, inventory, and control signaling
The backplane provides power and synchronization distribution (both phase
and frequency aligned) to all circuit packs in the shelf. All traffic routes
through the backplane to the cross-connect circuit pack.
The OME6500 shelf backplane architecture allows for eight 12.5 Gbit/s and
four 25 Gbit/s slots to ensure seamless scalability to new higher bandwidth
services. Figure 4-12 shows an overview of the backplane capacity.
Figure 4-12
OME6500 backplane capacity
Access Panel
Power
Cross-connect slot
Cross-connect slot
Shelf processor
12.5 Gbit/s
12.5 Gbit/s
12.5 Gbit/s
12.5 Gbit/s
12.5 Gbit/s
12.5 Gbit/s
12.5 Gbit/s
12.5 Gbit/s
Filler card
25 Gbit/s
25 Gbit/s
25 Gbit/s
25 Gbit/s
MIC
Power
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Fiber/cable routing channel
Shelf ID module
The OME6500 shelf also contains two shelf ID (SID) redundant modules that
contain the serial number, version, and PEC information about the shelf. The
OME6500 software uses the SID to determine the type and version of the shelf.
The SID information is displayed in Site Manager through the Inventory
screen. The SID modules, which are located on the shelf backplane behind the
access panel, are not meant to be field replaceable but they can be replaced, out
of service, if necessary.
Shelf ESD interface

The OME6500 shelf contains two ESD interfaces used to connect an antistatic
wrist strap required when handling circuit packs to avoid damaging the circuit
packs as a result of electrostatic discharge. Figure 4-11 shows the location of
the ESD interfaces on the OME6500 shelf (example shows the optical shelf,
other shelves have ESD interfaces in similar positions).
Access panel
The access panel (AP) at the top of the OME6500 shelf provides access to
OAM&P functions such as:
• external synchronization input (ESI)
• external synchronization output (ESO)
• telemetry I/O and alarms
• data communications interfaces to the OME6500 for dial-up modem
access, DCN access, craft user interface access, and collocated shelf
interconnect.
OME6500 supports two access panel variants:
• SDH access panel (NTK505LA)
• SONET/J-SDH access panel (NTK505MA)
Figure 4-13 shows the interfaces available on the access panels. Table 4-3
provides a description of the interfaces available on the access panels.
Figure 4-13
Access panel - front views
A ESI B A ESO B ESI/ESO DTE Alarm Telemetry COLAN-A COLAN-B ILAN In ILAN Out COLAN-X
SDH Access Panel
A Japan Clock B ESI/ESO ACO Visual / Audible Alarms Telemetry COLAN-A COLAN-B ILAN In ILAN Out COLAN-X
DTE
SONET Access Panel

Table 4-3
Access panel - interface descriptions
Port Physical interface Description

ESI / ESO • 75 ohm • External synchronization inputs for timing generation references
unbalanced BT which enable the OME6500 to be timed from an external timing
type 43 connector reference of stratum 3 (ST3)/G.813 Option 1 or better quality.
or 120 ohm • External synchronization outputs for timing distribution
balanced DB9 references which enable other network elements to be timed
female connector from the OME6500.
(NTK505LA)
Note: The SONET/J-SDH access panel also includes two
• wire-wrap pins
mini-BNC connectors for 6.312 MHz outputs which are not used
(NTK505MA)
in present applications.
Alarms • DB9 female • Provides an interface for Critical, Major and minor alarm
connector conditions.
(NTK505LA) • Alarms are intended to be connected to the frame alarm unit
• wire-wrap pins (AU) and combined with other central office alarms.
(NTK505MA) Note: Audible alarms are only available on the SONET/J-SDH
access panel.
Remote ACO • wire-wrap pins • Enables user to cut-off audible alarms from a remote switch (for
(NTK505MA) example, rack ACO on BIP).
DTE • DB9 male • Asynchronous RS-232 interface for remote dial-in access
connector through modem to the OME6500.
Telemetry • DB25 female • 16 telemetry inputs enable the customer to connect external
connector environmental monitoring equipment to the OME6500 (for
(NTK505LA) example, door open indicator, fire alarm, and flood alarm).
• wire-wrap pins • Four telemetry outputs enable the customer to control external
(NTK505MA) equipment from the OME6500 (for example, lights and alarms).
• Provision for both normally open and normally closed contacts.
COLAN (A/B) • RJ-45 connector • Provides 10/100Base-T connectivity between the carrier’s DCN
and the specific shelf processor (A refers to shelf processor
located in slot 15 and B refers to shelf processor located in slot
16). This release supports COLAN-A. COLAN-B is not
supported in the current release.
ILAN_IN/ • RJ-45 connector • Interoffice LAN and provides 10/100BT connectivity from the
OUT OME6500 to subtended shelves for shelf management.
COLAN_X • RJ-45 connector • Central office LAN provides switched 10/100Base-T
connectivity between the carrier’s DCN and the OME6500.
• Port is switched to the active shelf processor located in slot 15;
intended for applications in which the carrier supplies a single
port to the DCN.
Refer to Access panel connector pinouts on page 7-12 and 10/100Base-T

RJ-45 pinout on page 7-16 for details on the connector pinouts.
Electrical interface area

Optical/front electrical shelf
The bottom section of the optical/front electrical shelf supports the installation
of hardware associated with electrical interfaces (E1 or DS3/EC-1).
Figure 4-14 shows the layout of the electrical interface area fitted with the E1
interface hardware. For more information about the E1 and DS3/EC-1
hardware, refer to I/O and protection hardware on page 4-49.
Figure 4-14
Optical/front electrical shelf - electrical interface area
E1 electrical hardware
The E1 electrical interface hardware includes:
• I/O panels (up to two)
• I/O protection modules (up to four per I/O panel) - optional
• 120 ohm converter modules (up to eight per I/O panel) - optional
When installed, this hardware allows for up to 504 75 ohm or 120 ohm E1
electrical interfaces. Cabling associated with interfaces can be routed via either
side of the shelf.

DS3/EC-1 electrical hardware

The DS3/EC-1 electrical interface hardware includes up to four I/O panels.
When installed, this hardware allows for up to 192 75 ohm DS3/EC-1

side of the shelf.
Optical/rear electrical shelf

The rear of the backplane of the optical/rear electrical shelf supports the
installation of hardware associated with electrical interfaces (DS3/EC-1).
Figure 4-15 shows the layout of the electrical interface area fitted with the
DS3/EC-1 interface hardware. For more information about the DS3/EC-1
hardware, refer to I/O and protection hardware on page 4-49.
Figure 4-15
Optical/rear electrical shelf - electrical interface area
DS3/EC-1 electrical hardware

The DS3/EC-1 electrical interface hardware includes up to four I/O panels.
When installed, this hardware allows for up to 192 75 ohm DS3/EC-1

side of the shelf.
Maintenance interface card

The maintenance interface card (MIC) located in slot 17, subslot 17-2 (see
Figure 4-11 on page 4-17) provides the following functionality:
• visual alarm indicator light emitting diodes (LED) for critical, major and
minor alarms that are active on the OME6500 shelf
• shelf power status (indicates shelf is receiving sufficient power from
power interfaces A and/or B)
• enables the shelf processor to receive LAN or DTE communications from
the access panel
• allows the user to shut off the receive attention and perform a shelf level
lamp test using a push button switch.
Figure 4-16 provides an overview of the MIC faceplate.
Figure 4-16
MIC faceplate overview
Green circle (Power)

MIC Single LED for combined PWR feeds (OR’d) -
Power used to indicate presence of -48 V A or B
Critical Red / Yellow circles (Shelf level alarm)
One LED for each shelf level alarm,
Major red for Critical, red for Major and yellow for Minor
Minor
ACO
White circle (ACO/RCV ATTN)
Single LED to indicate an ACO or
ACO/
Lamp Test Receive Attention condition
ACO/Lamp test push-button

Power input card

The OME6500 supports redundant -48/60 V dc power feeds (A and B) through
power input cards located in slot 17, subslots 17-1 and 17-3 (see Figure 4-11
on page 4-17). Both breakered and breakerless power input cards are available.
You must use a BIP when using breakerless power input cards. Each power
input card provides the following functionality:
• operates over the range -40 V to -75 V dc
• 40 A capacity
• low voltage indication to the shelf processor from each power input card
for low voltage alarms and combining of low voltage indicators to derive
shelf brownout state
Figure 4-17 provides an overview of the breakered power input card faceplate.
Figure 4-18 provides an overview of the breakerless power input card
faceplate.
Figure 4-17
Breakered power input card
Green circle (Power status)

Power Indicates presence of power to card
Card
Circuit breaker switch

Po Available on breakered power cards only
OK
Card pull tab

Tab to aid in power card removal from shelf
-48/60V
D-type connector
48/60 V dc RTN (male)
L+ PE (female)
48/60 V dc (male)
L-
Note: NTK505AA variant shown. NTK505CE

variant has 2-way connector.
Figure 4-18
Breakerless power input card
Green circle (Power status)

Power Indicates presence of power to card
Card
Po
OK
Test Test points
points Available on breakerless power cards only
Card pull tab

Tab to aid in power card removal from shelf
-48/60V
D-type connector
48/60 V dc RTN (male)
L+ PE (female)
48/60 V dc (male)
L-
Note: NTK505BA variant shown. NTK505DE

variant has 2-way connector.
Shelf processor
The OME6500 architecture supports two shelf processors. This release
supports one shelf processor located in slot 15 (see Figure 4-11 on page 4-17).
The shelf processor provides the following functionality:
• performs software management for the shelf
• maintains a copy of the current software load plus one backup on a flash
disk
• manages the intershelf LAN (ILAN) and central office LAN (COLAN)
DCN
• manages OAM messaging between circuit packs
• main repository for the complete shelf provisioning data
• provides an RS-232 DCE port and a 10/100BaseT interface on the
faceplate for access to the craft user interface

In the event of a shelf processor failure/removal, the shelf continues to

function (traffic is not affected and protection switching can occur) as the
interface circuit packs and the cross-connect circuit packs contain a copy of the
configuration data. Removal or failure of a shelf processor affects external
communications to/from the OME6500 shelf (local or remote craft access is
not possible).

Figure 4-11 on page 4-17 shows the location of the shelf processor in the
OME6500 shelf and Figure 4-19 provides an overview of the shelf processor
faceplate.
Figure 4-19
Shelf processor faceplate
Red triangle (Fail)

- Used to communicate hardware or software failure state
- Card OK = LED off, Card Failed = LED on
Green rectangle (Ready)
- Used to communicate hardware or software functional state (circuit
pack is healthy and available for use, does not reflect provisioning state)
- Card initializing = Blinking LED; Card active = LED on; Card failed = LED off
Blue diamond (In Use)
10/100BT RJ-45 connector for craft interface
RS-232 DCE DB-9 connector for craft interface
Refer to Shelf processor connector pinout on page 7-15 and 10/100Base-T

RJ-45 pinout on page 7-16 for details on the connector pinouts.
Cross-connect circuit packs

The OME6500 supports redundant cross-connect circuit packs (1+1
equipment protection) located in slots 7 and 8 (see Figure 4-11 on page 4-17).
Five cross-connect circuit packs are currently available:
• 80 Gbit/s fixed cross-connect with STS-1/VC4 switching granularity
• 160 Gbit/s ready cross-connect with STS-1/VC4 switching granularity.
Note: This release enables 80 Gbit/s of cross-connect capacity. This
circuit pack can be upgraded through software to support 160 Gbit/s of
cross-connect capacity in a future software release.
• 80 Gbit/s cross-connect with VT1.5/VC12 switching granularity, capable

of unrestricted connections up to 80G capacity
Note: VT1.5/VC12 capacity limited to 25G in this release.
• 80 Gbit/s cross-connect with VT1.5/VC12 switching granularity, with the

VT1.5/VC12 capacity limited to 20G.
• 20 Gbit/s cross-connect with VT1.5/VC12 switching granularity
Note 1: STS-1/VC-3 cross-connect circuit packs provide high order (HO)
traffic switching at STS-1 (SONET) and VC-4 (SDH) traffic granularities.
Note 2: VT1.5/VC-12 cross-connect circuit packs provide low order
traffic (LO) switching at VT1.5 (SONET) and VC-12 and VC-3_LO
(SDH) traffic granularities, as well as high order traffic switching at STS-1
(SONET) and VC-4 (SDH) traffic granularities.
The cross-connect circuit pack performs the following functions:
• connection management
• synchronization
• database backup for SP specific information
The cross-connect circuit packs manage synchronization and shelf bandwidth
as separate entities. For example, if there is a synchronization failure on the
cross-connect circuit pack in slot 7, and a bandwidth management failure on
the cross-connect circuit pack in slot 8, the system can still carry traffic and
provide synchronization timing to other network elements.

Figure 4-20 shows the faceplate of the cross-connect circuit pack.

Figure 4-20
Cross-connect circuit pack faceplate
Red triangle (Fail)

X-Comm 80G
STS-1/VC-3
Sync - ST3
Fail
Ready
In Use
- Used to communicate hardware or software functional state

Sync
- Used to communicate whether circuit pack can be extracted
Ref 1
(on->no pull, off->can be pulled
Ref 2
- Equipment in-service = LED on; Equipment out-of-service = LED off
LOS
Ref 3
Yellow circle (Synchronization status)
Ref 4
- Used to communicate loss of synchronization timing reference
- One LED per timing reference (1 Fail, 2 Fail, 3 Fail, 4 Fail)
R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type E
In the OME6500 architecture, the cross-connect circuit packs switch traffic
between port circuit packs. Two cross-connect circuit packs provide redundant
equipment protection. All ingress port circuit pack traffic is mapped into
appropriate SONET/SDH containers and directed towards the cross-connect
circuit pack which switches the incoming traffic to the appropriate egress port
circuit pack.
The cross-connect circuit pack allows any input channel to be connected to any
output channel. This basic functionality allows the system to support diverse
connection and protection configurations. Figure 4-21 provides an overview of
the OME6500 cross-connect architecture.
The cross-connect circuit packs are 1+1 protected working in hot standby and
have synchronization phase and frequency alignment. The OME6500 supports
hitless (no errors) switching between the switch matrices for circuit pack
failure, removal of the circuit pack, and software upgrades. Switching to the
redundant cross-connect does not affect system configuration and user
commands.
Figure 4-21
OME6500 cross-connect overview
Cross-connect circuit pack
Switch
Port circuit pack Port circuit pack
Port circuit pack Port circuit pack
The size of the cross-connect switching capacity determines the service

interface slot capacity. The 80 Gbit/s cross-connect translates to 5 Gbit/s of
high speed slot capacity for slots 1-4, 11-14 and 10 Gbit/s of ultra high speed
slot capacity for slots 5, 6, 9 and 10. Figure 4-22 shows the slot capacity
enabled by the 80 Gbit/s cross-connect.
Synchronization
synchronization hardware on the cross-connect circuit pack for both timing
generation and timing distribution.
For more information about the hardware associated with OME6500
synchronization, refer to Synchronization hardware on page 4-30. For more
information about the management of synchronization features and
capabilities, refer to Synchronization management on page 6-29.

Figure 4-22
OME6500 80 Gbit/s cross-connect slot capacity
Access Panel
17-1
Pwr
Shelf processor
80 Gbit/s fabric
80 Gbit/s fabric
17-2
Filler card
10 Gbit/s
10 Gbit/s
10 Gbit/s
10 Gbit/s
5 Gbit/s
5 Gbit/s
5 Gbit/s
5 Gbit/s
5 Gbit/s
5 Gbit/s
5 Gbit/s
5 Gbit/s
MIC
17-3
Pwr
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Fiber routing channel
Database storage
The cross-connect circuit packs also maintain a copy of the shelf processor
specific provisioning data as a backup to the master copy maintained on the
shelf processor. For more information about database management, refer to
Backing up and restoring the network element database on page 6-89.
Synchronization hardware
The OME6500 synchronization system spans across several components and
consist of the following:
• cross-connect circuit pack (see Cross-connect circuit packs on page 4-27)
• OC-n/STM-n interface circuit pack (see Interface circuit pack descriptions
on page 4-31)
• access panel (see Access panel on page 4-19)
• shelf processor (see Shelf processor on page 4-25)
Figure 4-23 provides an overview of the OME6500 sychronization
architecture. For more information about the synchronization management
feature, refer to Synchronization management on page 6-29.
Figure 4-23
OME6500 synchronization architecture
ESI/ESO ESI/ESO
Unbalanced Balanced
ESI-A ESI-B ESO-A ESO-B ESI-A ESI-B ESO-A ESO-B
Access Panel
Shelf
Processor
OC-n/STM-n interface circuit packs
Interface circuit pack descriptions

This section provides an overview of the OME6500 interface circuit packs.
The interface circuit packs are located in slots 1-6 and slots 9-14 (see Figure
4-11 on page 4-17). OME6500 supports the interface circuit packs listed in
Table 4-4.
Table 4-4
OME6500 interface circuit packs
Interface circuit pack Page

8xOC-3/12/STM-1/4 circuit pack 4-38
4xGE EPL circuit pack 4-39
63xE1 working and protection circuit packs 4-42
24xDS3/EC-1 working and protection circuit packs 4-44

Table 4-5 details the interface circuit pack densities. Table 4-6 provides a
summary of the functionality provided by each of the interface circuit packs.
Table 4-5
OME6500 interface circuit pack density
Circuit pack Port density/ Circuit pack/ shelf Port density/

circuit pack shelf
OC-192/STM-64 1 4 4
OC-48/STM-16 2 12 24
OC-3/12/STM-1/4 8 12 96
GE EPL 4 12 48
E1 63 8 (working) + 2 504
(protection)
DS3/EC-1 24 8 (working) + 2 192

(protection)
DS1 84 per DSM Support for 16 1344

DSMs per shelf
Table 4-6
Interface circuit pack summary
Interface Summary
OC-192/STM-64 • Fixed optics using LC connectors
• STS-1/HO and VT1.5/LO variants:
— STS-1/HO support with STS-1/VC4 granularity
— VT1.5/LO support with VT1.5/VC12 granularity
• IR-2/S64.2, SR-1/I64.2, LR-2/L64.2 circuit packs
• DWDM (10.7G) circuit packs
— 16 compliant with OMX, 36 compliant with CPL
— G.709 wrapper for RS-8 FEC
OC-48/STM-16 • Pluggable optics using LC connectors
• STS-1/HO and VT1.5/LO variants:
• SFP modules: IR1/S16.1, LR2/L16.2, CWDM (8 wavelengths)
• DPO modules: 41 wavelengths in C-Band (100 GHz spaced), 16 compliant with
OMX, 36 compliant with CPL

Interface circuit pack summary
Interface Summary
OC-3/12/ • Pluggable optics using LC connectors
STM-1/4 • STS-1/HO and VT1.5/LO variants:
• SFP modules: SR0 (multimode) OC-3/STM-1, LR2/L1.2 OC-3/STM-1, LR2/L4.2
OC-12/STM-4, SR1/I1.1_I4.1 OC-3/12/STM-1/4, IR1/S1.1_S4.1
OC-3/12/STM-1/4, STM-1e (see Note)
• Per port selectable to OC-3/STM-1 or OC-12/STM-4
GE • Pluggable optics using LC connectors
• SFP modules: SX (850 nm), LX (1310 nm), ZX (1550 nm), CDWM
(8 wavelengths)
• GFP-F mapped (ITU-T G.7041 compliant)
E1 • 75 ohm or 120 ohm inputs/outputs
• VC12 mapping
• 1:N protection in two banks of 1:4
• ITU-T G.703 compliant ports
DS3/EC-1 • 75 ohm inputs/outputs
• STS-1/LO_VC3 mapping
• 1:N protection in two banks of 1:4
• Per port selectable to DS3 or EC-1
• ANSI T1.102 compliant ports
DS1 • 100 ohm inputs/outputs
• VT1.5 mapping
• 1+1 protection
• ANSI T1.102 compliant ports
Note: Contact Nortel Networks regarding the availability of these SFPs.
Optical transceivers
OME6500 has two types of optical transceivers as follows:
• fixed optics
Fixed optics are where the optical module is permanently mounted on the
interface circuit pack. The 1xOC-192/STM-64 circuit pack uses fixed
optics for short reach, intermediate reach, long reach, and DWDM
applications. For DWDM applications, the 1xOC-192/STM-64 circuit
packs use G.709 wrapper for RS-8 FEC and supports all C-Band
wavelengths for CPL and the OMX (see Ordering Information,
323-1851-151 for list of wavelengths).

• pluggable optics
Pluggable optics are where the optical module is a separate, pluggable
component on the interface circuit pack. The OC-3/STM-1, OC-12/STM-4
and GE interfaces use small form-factor pluggable (SFP) interfaces to
deliver optical rate and reach flexibility on a per port basis. The
OC-48/STM-16 optical interfaces use SFP modules for short reach,
intermediate reach, long reach, and CDWM applications and DWDM
pluggable optic (DPO) modules for DWDM applications. For DWDM
applications, the 2xOC-48/STM-16 DPO circuit packs support 41
wavelengths in the C-Band compliant to the ITU-T grid (see Ordering
Information, 323-1851-151 for list of wavelengths).
VT1.5/LO and STS-1/HO circuit packs

There are two versions of the 1xOC-192/STM-64, 2xOC-48/STM-16, and
8xOC-3/12/STM-1/4 circuit packs:
• VT1.5/Low Order (LO)
These circuit pack supports VT1.5/VC12 and above switching granularity
(including LO VC3).
• STS-1/High Order (HO)
These circuit pack supports STS-1/VC4 and above switching granularity.
Note: To use the VT1.5/VC12 granularity, both the optical interface
circuit packs and the cross-connect circuit packs must support
VT.15/VC12 switching granularity.

OME6500 supports the short reach, intermediate reach, long reach, and
DWDM variants of the 1xOC-192/STM-64 circuit pack. The
1xOC-192/STM-64 circuit pack uses fixed optics and can be installed in slots
5, 6, 9 and 10. The same circuit pack supports both OC-192 (SONET) and
STM-64 (SDH) services.
The DWDM circuit pack supports ITU-T DWDM compliant wavelengths as

follows:
• 36 wavelengths for interworking with the Common Photonic Layer (CPL)
equipment.
• 16 wavelengths for interworking with the Optical Metro 5000-series
DWDM optical multiplexer (OMX).
Figure 4-24 shows the faceplate of a 1xOC-192/STM-64 circuit pack.
Figure 4-24
1xOC-192/STM-64 circuit pack faceplate
Red triangle (Fail)

OC-192/STM-64
STS-1/HO
1 Port G.709 DWDM
Fail
Ready
In Use
Rx Tx Blue diamond (In Use)

Yellow circle (LOS)

- Used to communicate Rx Loss of Signal
Transmit/receive fixed dual LC connector

(on latest circuit packs, the orientation of the
LC connectors is vertical [one above another])
Hazard
level:
R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type A
1xOC-192/STM-64 functionality overview

The 1xOC-192/STM-64 circuit pack provides the following functionality:
• supports OC-192 (SONET) and STM-64 (SDH) services
• supports non-concatenated rates of VT1.5/VC12 (VT1.5/LO circuit packs
only) and STS-1/LO_VC3/VC4
• supports contiguous concatenation at STS-3c, STS-12c/VC4-4c,
STS-24c/VC4-8c, STS-48c/VC4-16c, and STS-192c/VC4-64c
• terminates both section/RS and line/MS overhead
— terminates section/RS and line/MS overhead bytes in Rx direction
— inserts section/RS and line/MS overhead bytes in Tx direction
• section/RS DCC or line/MS DCC selectable (default is Off)
• supports section/RS and line/MS PMs
• supports STS-1, STS-3c/VC4, STS-12c/VC4-4c, STS-24c/VC4-8c,
STS-48c/VC4-16c, and STS-192c/VC4-64c PMs
• monitors optical power input and output on all circuit pack types

• G.709 wrapper (non provisionable) with RS-8 FEC selectable (default is

On) on the DWDM interfaces only
• selectable automatic laser shutdown controlled by software
• supports unprotected, BLSR/MS-SPRing, 1+1/MSP linear, and
UPSR/SNCP traffic protection schemes
• line timing synchronization support (provides the handover between the
line timing and the shelf)
Refer to Ordering Information, 323-1851-151, for the PEC information. Refer
to 1xOC-192/STM-64 optical specifications on page 7-28 for optical
specifications and the sections in OAM&P description on page 6-1 for more
details on functionality supported.

OME6500 supports SFP and DPO variants of the 2xOC-48/STM-16 circuit
pack. The 2xOC-48/STM-16 SFP circuit pack uses SFP optics for short reach,
intermediate reach, long reach, and CDWM variants. The 2xOC-48/STM-16
DPO circuit pack uses DPO optics for DWDM variants. The
2xOC-48/STM-16 circuit pack can be installed in slots 1-6 and 9-14. The same
circuit pack supports both OC-48 (SONET) and STM-16 (SDH) services.
The 2xOC-48/STM-16 SFP circuit pack supports the eight CWDM
wavelengths.
The DWDM circuit pack supports ITU-T DWDM compliant wavelengths as
follows:
• 36 wavelengths for interworking with the Common Photonic Layer (CPL)
equipment.
• 16 wavelengths for interworking with the Optical Metro 5000-series
DWDM optical multiplexer (OMX).
Figure 4-25 shows the faceplate of the 2xOC-48/STM-16 circuit packs.
2xOC-48/STM-16 functionality overview
The 2xOC-48/STM-16 circuit pack provides the following functionality on all
circuit pack variants unless otherwise noted:
• supports OC-48 (SONET) and STM-16 (SDH) services
• supports contiguous concatenation at STS-3c, STS-12c/VC4-4c,
STS-24c/VC4-8c, and STS-48c/VC4-16c
• terminates section/RS and line/MS overhead
• section/RS DCC or line/MS DCC selectable (default is Off)

• supports STS-1, STS-3c/VC4, STS-12c/VC4-4c, STS-24c/VC4-8c, and
STS-48c/VC4-16c PMs
• automatic detection/provisioning of SFP and DPO modules, which are hot
pluggable.
• supports unprotected, BLSR/MS-SPRing, 1+1/MSP linear, and
UPSR/SNCP traffic protection schemes
Figure 4-25
2xOC-48/STM-16 circuit pack faceplate
Red triangle (Fail)

OC-48/STM-16 OC-48/STM-16
STS-1/HO STS-1/HO
2 Ports SFP 2 Ports SFP
Fail Fail
Ready Ready Green rectangle (Ready)

In Use In Use


1 Tx 1
Rx - Equipment in-service = LED on; Equipment out-of-service = LED off
2 Tx
Rx
Red/yellow bi-color circle (Fail/LOS)

- Used to communicate Rx Loss of Signal/optical module (SFP/DPO) fail
- Red = module fail; Yellow = Rx Loss of Signal
Transmit/receive SFP dual LC connector

2
Hazard Hazard
level: level:
R99
R99
EEEEE99999
EEEEE99999
S/N NT030MEE9999E
S/N NT030MEE9999E
Transmit/receive DPO dual LC connector

NTUD99EE
NTUD99EE
Type A Type A
SFP DPO

to 2xOC-48/STM-16 optical specifications on page 7-30 for optical
specifications and the sections in OAM&P description on page 6-1 for more

8xOC-3/12/STM-1/4 circuit pack

The 8xOC-3/12/STM-1/4 circuit pack uses SFP optics for short reach,
intermediate reach, and long reach applications or an STM-1e SFP for
intra-office applications. The 8xOC-3/12/STM-1/4 circuit pack can be
installed in slots 1-6 and 9-14. OME6500 supports OC-3/STM-1 or
OC-12/STM-4 per port and is selectable through software. The same circuit
pack supports both OC-3/12 (SONET) and STM-1/4 (SDH) services.
Figure 4-26 shows the faceplate of the 8xOC-3/12/STM-1/4 circuit pack.
Figure 4-26
8xOC-3/12/STM-1/4 circuit pack faceplate
Red triangle (Fail)

OC-3/12/STM-1/4
STS-1/HO
8 Ports SFP
Fail
Ready
In Use

1 Tx - Card initializing = Blinking LED; Card active = LED on; Card failed = LED off
Rx
2 Tx
Rx
3 Tx
Rx (on->no pull, off->can be pulled
4 Tx - Equipment in-service = LED on; Equipment out-of-service = LED off
Rx
5 Tx
Rx Red/yellow bi-color circle (Fail/LOS)

6 Tx - Used to communicate Rx Loss of Signal/optical module fail
Rx
- Red = module fail; Yellow = Rx Loss of Signal
7 Tx
Rx
8 Tx
Rx
Hazard
level: Transmit/receive SFP dual LC connector
or dual 1.0/2.3 mm coaxial connector
R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type A
8xOC-3/12/STM-/4 functionality overview

The 8xOC-3/12/STM-1/4 circuit pack provides the following functionality:
• supports OC-3 or OC-12 (SONET) or STM-1 or STM-4 (SDH) services
• per port selectable to OC-3/STM-1 or OC-12/STM-4
• auto-detection of SFP modules, which are hot pluggable
• auto provisioning of OC-3/STM-1 or OC-12/STM-4 specific SFPs
• manual provisioning of SFP modules that support both OC-3/STM-1 and

OC-12/STM-4. For example, since the IR-1/S1.1_S4.1 OC-3/12/STM-1/4
SFP supports both OC-3/STM-1 and OC-12/STM-4, the user must
manually provision the SFP module for OC-3/STM-1 or OC-12/STM-4
operation.
• supports contiguous concatenation at STS-3c and STS-12c/VC4-4c for
OC-12/STM-4
• terminates section/RS and line/MS overhead
• section/RS DCC or line/MS DCC selectable (default is Off). Section/RS
DCC can be enabled on all ports, line/MS DCC can be enabled on any two
ports
• supports STS-1, STS-3c/VC4, STS-12c/VC4-4c PMs
Note: Optical power not applicable to STM-1e SFPs.

Note: For STM-1e SFPs, you must ensure that automatic laser shutdown
is disabled (see Provisioning and Operating Procedures, 323-1851-310 for
details).
• supports unprotected, 1+1/MSP linear, and UPSR/SNCP traffic protection

schemes
to 8xOC-3/12/STM-1/4 SFP optical specifications on page 7-32 for optical
specifications, Electrical specifications on page 7-36 for STM-1e electrical
specifications, and the sections in OAM&P description on page 6-1 for more
4xGE EPL circuit pack

The 4xGE Ethernet Private Line (EPL) circuit pack uses SFP optics for short
reach, long reach, and CDWM applications. The 4xGE EPL circuit pack can
be installed in slots 1-6 and 9-14.
Figure 4-27 shows the faceplate of a 4xGE EPL circuit pack.

Figure 4-27
4xGE EPL circuit pack faceplate
Red triangle (Fail)

GE
EPL
4 Ports SFP
Fail
Ready
In Use

1 Tx (on->no pull, off->can be pulled
Rx
2 Tx
Rx
3 Tx
Rx Red/yellow bi-color circle (Fail/LOS)

4 Tx - Used to communicate Rx Loss of Signal/optical module fail
Rx
- Red = module fail;
- Yellow = Rx Loss of Signal, loss of 8B10B synch, or link down
Hazard
level:
Transmit/receive SFP dual LC connector

R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type A
4xGE EPL functionality overview

The 4xGE EPL circuit pack consists of two entities (client facing and line
facing):
• client facing interfaces referred to as LAN ETH ports
• line facing (mapped for transport via SONET/SDH containers) aspects of
the circuit pack referred to as WAN ports
Figure 4-28 shows the LAN-WAN concept of the 4xGE EPL circuit pack.
Figure 4-28
4xGE EPL LAN-WAN concept
Line facing
Client facing (GFP-F mapped)
GE LAN/ETH port 1 WAN port 1 STS/VC containers

The 4xGE EPL circuit pack supports the following:

• supports the transport of GE service
• auto-detection of SFP modules, which are hot pluggable
• manual provisioning of SFP modules
• point-to-point GE application.
• supports full-rate GE service transport
• supports sub-rate GE service transport
• mapping of GE to/from SONET/SDH containers via Framed GFP at
following levels:
— STS-1 and VC-4
— contiguous concatenation (STS-3c, STS-12c/VC4-4c, and
STS-24c/VC4-8c)
— virtual concatenation (STS-1-nv/VC3-nv, where n = 1 to 21,
STS-3c-nv/VC4-nv, where n = 1 to 7)
• supports provisionable Ethernet auto-negotiation (Enable or Disable) with
the local Ethernet link partner as per clause 37 of IEEE 802.3-2000
• supports full duplex mode only
• 64 byte to 9600 byte Ethernet frame support
• supports provisionable Ethernet maximum transfer unit (MTU) of 1600
bytes (default) or 9600 bytes
• supports Ethernet flow control capabilities
— None (advertises flow control not supported)
— Asymmetric (default) (advertises asymmetric flow control toward the
link partner)
— Symmetric (advertises symmetric flow control or asymmetric flow
control toward the local device)
Note: This attribute is ignored when auto-negotiation is disabled.
— supports loss less local flow control for distances up to 10 km (local

loop) for all MTU sizes (1600 and 9600)
— automatically adjusts the PAUSE transmit thresholds to maximize the
supported distance based on the MTU attribute

• support for enabling/disabling Ethernet control frames transport

— the only currently standardized Ethernet control frame (T/L=0x8808)
is the PAUSE frame
— determine if received Ethernet control frames (T/L=0x8808) are
discarded or passed through transparently
– editable to DISABLE (default) or ENABLE
— Ethernet frames received with T/L=0x8809 (slow protocols) are
always transparently passed through
• 8B10B Performance Monitoring accumulation and generation
• Ethernet operational measurements generation
— generic interface OMs based on RFC 2863 (applies to both the Ethernet
LAN and the WAN facilities)
— Ethernet specific OMs based on RFC 2665 (it applies to the Ethernet
LAN interface only)
Note: GE services map to SONET/SDH containers and are assigned as
connections to OC/STM interface circuit packs. They can therefore use the
traffic protection schemes supported by the OC-n/STM-n interface circuit
packs to provide a protected GE service without the requirement of a
redundant handoff from the subtending GE equipment.
Refer to Ordering Information, 323-1851-151, for the PEC information, 4xGE

EPL SFP optical specifications on page 7-35 for optical specifications, and the
sections in OAM&P description on page 6-1 for more details on functionality
supported.
63xE1 working and protection circuit packs

The 63xE1 working circuit pack supports the mapping of up to 63 E1 signals
to VC12 containers within the network element. The 63xE1 working circuit
pack can be installed in slots 1-4 and 9-12.
OME6500 supports equipment protection for the E1 circuit packs using 1:N
protection in two banks. Each bank requires a 63xE1 protection circuit pack.
The 63xE1 protection circuit pack in slot 13 provides protection for the circuit
packs in slots 1-4. The 63xE1 protection circuit pack in slot 14 provides
protection for the circuit packs in slots 9-12.
Note 1: The 1:N protection also requires E1 I/O interface modules and
protection modules in the lower electrical interface section of the
optical/front electrical shelf (see I/O and protection hardware on page
4-49). Unprotected E1 services do not require protection modules.
Note 2: For the E1 circuit packs, you must use cross-connect circuit packs
and optical interface circuit packs that support VT.15/VC12 switching
granularity.
Figure 4-27 shows the faceplate of an E1 circuit pack.

Figure 4-29
63xE1 circuit pack faceplate
Red triangle (Fail)

E1
63 Ports
Fail
Ready
In Use
LOS

Yellow circle (LOS)

- Used to communicate loss of signal of any E1 input signal
R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type E
The 63xE1 circuit packs provides the following functionality:

• supports up to 63 E1 services
• auto and manual provisioning of working and protection circuit packs
• mapping of E1 signals to VC12 containers
• support for G.704 E1 framed and multiframed signals
• terminates and inserts VC12 path overhead
• supports line and path E1 PMs
• supports unprotected and 1:N equipment protection (2 banks, each bank
providing up to 1:4 equipment protection)
Refer to Ordering Information, 323-1851-151, for the PEC information,
Electrical specifications on page 7-36 for electrical specifications, and the
supported.

24xDS3/EC-1 working and protection circuit packs

The 24xDS3/EC-1 working circuit pack supports up to 24 DS3 or EC-1
services. The DS3 signals are mapped to STS-1/LO_VC3 containers. The
EC-1 signals support VT1.5 and STS-1 connections.
Note: EC-1 services are only supported in the SONET network element
mode.
The 24xDS3/EC-1working circuit pack can be installed in slots 1-4 and 9-12.
OME6500 supports equipment protection for the 24xDS3/EC-1 circuit packs

using 1:N protection (in two banks of 1:4). Each bank requires a 24xDS3/EC-1
protection circuit pack. The 24xDS3/EC-1 protection circuit pack in slot 13
provides protection for the circuit packs in slots 1-4. The 24xDS3/EC-1
protection circuit pack in slot 14 provides protection for the circuit packs in
slots 9-12.
Note: Unprotected or 1:N protected 24xDS3/EC-1 circuit packs require
48xDS3/EC-1 I/O panels (see DS3/EC-1 I/O panels on page 4-51).
Figure 4-27 shows the faceplate of an 24xDS3/EC-1 circuit pack.

Figure 4-30
24xDS3/EC-1 circuit pack faceplate
Red triangle (Fail)

DS3/EC1
24 Ports
Fail
Ready
In Use
1
3
4
5
6 (on->no pull, off->can be pulled
7
8
9
10
11
12
LOS
13
14
15
16
17
18
19
20
Yellow circle (LOS) - one per input
21 - Used to communicate loss of signal of a DS3/EC1 input signal
22
23
24
R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type E
The 24xDS3/EC-1 circuit packs provides the following functionality:

• supports up to 24 DS3 or EC-1 services, selectable on a per port basis
Note: EC-1 services are only supported in the SONET network element
mode.
• auto and manual provisioning of working and protection circuit packs

• mapping of DS3 signals to STS-1/LO_VC3 containers
• VT1.5 and STS-1 connections for the EC-1 signals
• support for asynchronous (M13), C-BIT, and unframed DS3 signals
• terminates/inserts section and line overhead in EC-1 signals
• terminates and inserts path overhead
• supports for following PMs:
— section and line EC-1 PMs
— line DS3 PMs
— path PMs
• supports unprotected and 1:N equipment protection (2 banks, each bank
providing up to 1:4 equipment protection)
Refer to Ordering Information, 323-1851-151, for the PEC information,
Electrical specifications on page 7-36 for electrical specifications, and the
supported.
Filler card
The filler card is required to fill any empty slots. Although the filler card does
not contain electronic components, the filler card ensures airflow and cooling
is constant for each slot in the shelf and ensures EMI compliance.
DS1 service module shelf

The DS1 service module (DSM) (see Figure 4-31) is a peripheral shelf
connected to an OME6500 network element. The DSM connects to the
OME6500 network element through the OC-3 ports on a host
8xOC-3/12/STM-1/4 circuit pack. The DSM is a terminal DS1 multiplexer.
The DSM has three I/O modules. Each I/O module supports up to 28 DS1
facilities.
The DSM has two numbered slots for DSM 84xDS1 termination module (TM)
circuit packs. DSM 84xDS1 TM circuit packs support up to 84 DS1 facilities.
The two circuit packs provide 1+1 protection.

Equipping rules
The DSM connects to the OC-3 ports on the OME6500 shelf using either one
(unprotected) or two (1+1/MSP linear protected) OC-3 optical interfaces. An
OME6500 shelf supports up to 16 protected or unprotected DSMs.
Note: The DSM is only supported in the SONET network element mode.
Multiple IS
Multiple intermediate system (IS) is a function that allows the DSM, and
communication between the DSM shelf and the shelf processor on the host
network element, to remain hidden from the other network elements in the
network. The DSMs do not appear in the Routing Information table and are not
included in the autodiscovery information.
Figure 4-31
DS1 service module shelf
OAM adapter
module
Connector
retaining spring
Cover
lock (2)
Front cover
LEDs
DS1 1-28 in
connectors
out
in
DS1 29-56
connectors out Mounting
bracket in
19-in configuration
in
DS1 57-84
connectors out
Figure 4-32
DS1 service module (front cover open) equipped with 84xDS1 TM circuit packs
DSM fan module
LEDs
OAM adapter DS1 connector

module with protective cap
DSM 84xDS1
termination
module in slot 2
DSM 84xDS1
termination
module in slot 1
DS-1
DS-1
DS-1
DS-1
DS-1
DS-1
DS-1
DS-1
57
-8
4
DS-1
DS-1
DS-1
DS-1
Fiber storage
Front Front cover

attaching screws
cover Optical
connector
applicator
Note: The DSM fiber storage tray capacity is 45 ft.

Figure 4-33
DSM OAM with cover off
A- Return
(White/red)
A- Battery
(Red) -48V
Mate-N-Lok receptacles Power A

mate directly with breaker
BIP power cable Power B
harnesses breaker
Clip pin
A feed
B feed
B- Return
(White/blue)
A- Battery
(Red/blue) -48V
LUI RS-232
connector
Clip pin
Alarm
connectors
Note: The local user interface (LUI) is an RS-232c port with D-type nine pin connector.
The LUI is used for retrieving messages when performing low-level trouble shooting on the DSM.
Used to access the active 84 xDS1 TM circuit pack, it provides remote login to the host in the
case of an OAM fail.
DSM 84xDS1 termination module (TM)

The DSM 84xDS1 termination module (DSM 84xDS1 TM) has been
developed for use in the DS1 service module (DSM). The DSM 84xDS1 TM
supports 84 DS1 facilities.
For each DSM 84xDS1 TM, you need one OC-3 interface installed in the
OME6500 shelf.
Note: You are recommended to use the DS1 right-angle cable assembly
with the DSM shelf.
Equipping rules
When you order the DSM shelf kit (NTN407AC), two 84xDS1 TM circuit
packs (NTN313AC) and a DSM shelf (NTN407MA) are included. For an
unprotected DSM, order one 84xDS1 TM circuit pack (NTN313AC) and one
DSM shelf (NTN407MA).
The 84xDS1 TM circuit pack is an intermediate reach optical interface which

is compliant with the OC-3x4/STM-1x4 optical specifications.
For more information, refer to:

• DSM 84xDS1 TM optical specifications on page 7-34
• 8xOC-3/12/STM-1/4 SFP optical specifications on page 7-32
Note: The NTN313AC circuit pack comes with LC connectors
pre-installed.

Protection switching
DSM 84xDS1 termination module protection switching is 1+1 non-revertive.
If a working DSM 84xDS1 TM becomes defective, the traffic is switched to
the protection DSM 84xDS1 TM. Switching can also take place under user
control.
I/O and protection hardware

I/O modules for the OME6500 optical/front electrical and optical/rear
electrical shelves provide input and output of electrical signals for traffic. The
I/O modules are removable and replaceable.
Refer to Ordering Information, 323-1851-151, for the PEC information for the
I/O and protection hardware.
E1 I/O panels and protection hardware

I/O panel
I/O panels in the electrical interface chassis of the optical/front electrical shelf
provide the electrical interfaces for the 63xE1 circuit packs. Each I/O panel
supports 252 E1 inputs/outputs. The electrical interface chassis contains four
slots for mounting the I/O panels, two for each I/O panel:
• the I/O panel connected to slots 1 and 2 in the electrical interface chassis
supports the 63xE1 working circuit packs in slots 1-4
• the I/O panel connected to slots 3 and 4 in the electrical interface chassis
supports the 63xE1 working circuit packs in slots 9-12
Alignment pins on the backplane and an insertion/ejector bar on the I/O panels
aid alignment during installation of the I/O modules.
Each I/O panel has eight 32-port 75 ohm connectors. 75 ohm cable assemblies,
each containing 2x32 coaxial cables, fit directly to the connectors on the I/O
panel. Figure 4-34 shows the layout of an I/O panel.

Figure 4-34
E1 I/O panel
Cable
connector
Insertion/ejector
latch
Protection
module Handle
connector
Cable
connector
cover
Protection module
connector cover
120 ohm converter modules

For 120 ohm interfaces, 120 ohm converter modules are available which fit on
the connectors on the E1 I/O panel. One 120 ohm cable assembly, containing
2x32 twisted pairs, fits on to each converter module. Two fixing screws secure
the converter module to the E1 I/O panel. Figure 4-35 shows the layout of an
120 ohm converter module.
Figure 4-35
120 ohm converter module
Fixing screw
E1 input/output
I/O panel connector
connector
I/O protection modules

For 1:N equipment protection, each 63xE1 working circuit pack requires an
I/O protection module. Each I/O module supports four I/O protection modules,
one for each of the possible 63xE1 working circuit packs in the 1:N equipment
protection bank. The I/O protection module has a blue LED which, when lit,
indicates that the module is active and must not be removed. Two fixing screws
secure the I/O protection module to the I/O panel.
Figure 4-38 shows the layout of an I/O protection module.

Figure 4-36
I/O protection module
Blue In
Use LED
Handle for
insertion/
extraction
Fixing screw
DS3/EC-1 I/O panels

I/O panel
I/O panels in the electrical interface chassis of the optical/front electrical shelf
or the optical/rear electrical shelf provide the electrical interfaces for the
24xDS3/EC-1 circuit packs. Each I/O panel supports 48 DS3/EC-1
inputs/outputs. The electrical interface chassis contains four slots for mounting
the I/O panels, one for each I/O panel:
• the I/O panel connected to slot 1 in the electrical interface chassis supports
the 24xDS3/EC-1 working circuit packs in slots 1 and 2 (unprotected or
1:N protected)
1:N protected)
1:N protected)

1:N protected)
Alignment pins on the backplane and an insertion/ejector bar on the I/O panels
aid alignment during installation of the I/O modules.
The following variants of the DS3/EC-1 I/O panels are available (see Figure
4-37):
• 48xDS3/EC-1 front access I/O panel, NTK572CA (for unprotected or 1:N
protected configurations)
• 48xDS3/EC-1 rear access I/O panel, NTK572QA (for unprotected or 1:N
protected configurations)
Figure 4-37
DS3/EC-1 I/O panels
Fiber/cable routing channel

The fiber/cable routing channel at the bottom of the OME6500 shelf allows for
the management of optical fibers/cables to/from the optical/STM-1e electrical
service interfaces (see Figure 4-11 on page 4-17).
Figure 4-38 shows the management and separation of optical fibers within the
fiber routing channel.
Figure 4-38
OME6500 optical fiber management
Fiber Fiber

Optical fibers/cable leave the faceplate of the interfaces and drop through 60
degrees (fixed optics and SFPs) or 90 degrees (DPOs) into the fiber/cable
routing channel and are routed through both sides of the shelf. Each side can
handle half of the total shelf optical fiber/cable capacity. Optical fibers/cables
are diversely run through the shelf and frame:
• high speed (line-side) can be segregated from low speed (client-side)
• east and west optical fibers/cables are separate
The fiber/cable routing channel at the bottom the OME6500 shelf provides
sufficient space to route 2.0 mm outside diameter jacketed optical fibers or
RG179DT cables for all circuit packs in all shelf slots. While using greater
than 2.0 mm outside diameter jacketed optical fiber is acceptable, it may limit
fiber channel capacity for the denser port optical circuit packs. Refer to the
Ordering Information, 323-1851-151 for the correct optical fibers/cables to be
used with the OME6500.
Shelf cover
An optional OME6500 shelf cover is available for additional protection and
security. The shelf cover provides visual access to the LEDs on the circuit
packs and the MIC so that the user can view the status of each circuit pack and
the shelf level alarm status. The shelf cover also provides a clip that can be
used to insert a lock. Figure 4-39 shows the OME6500 shelf with the shelf
cover on.
The shelf cover can only be used with optical fiber having a 42.5 mm long
strain relief boot. The use of optical fiber with longer strain relief boots may
impact the bend radius of the optical fibers routing off the circuit pack
faceplates when closing the shelf cover. Refer to the Ordering Information,
323-1851-151 for the correct optical fibers to be used with the OME6500.
A shelf cover is also available for the electrical I/O interface area in an
optical/rear electrical shelf.
Figure 4-39
OME6500 shelf cover
Clip for
inserting lock
Shelf cover
Optical multiplexer
The optical multiplexer (OMX) can be used with the OME6500 shelves and is
a stand-alone unit. The OMX multiplexes and demultiplexes up to four optical
channels in one band.
Each OMX is a 1U high external drawer that contains optical filters, a small
patch panel with bulkhead connectors, and fiber management components.
The drawers can be mounted anywhere in a rack (see Ordering Information,
323-1851-151 for recommended rack layouts). Each OMX uses bulkhead
connectors and patch cords to connect circuit packs. The OMX has locking
latches to prevent trays from being pulled out completely. Figure 4-40 shows
the OMX with the tray open.
Two variants of the OMX are available:

• standard OMX (NT0H32xE)
• enhanced OMX (NT0H32xF) - provides higher isolation and lower
insertion loss

Figure 4-40
OMX equipment drawer
Fiber manager
The fiber manager is an external drawer used to manage slack fiber (see Figure
4-41). The fiber manager:
• is a 1 U high rack-mounted external drawer
• is used wherever slack fiber needs to be managed
• contains 16 flip-up fiber spools (each fiber spool can manage 1.6 m of
fiber, maximum 3 mm diameter)
• can manage a maximum of 16 fibers (at 2 m each)
• has a fiber capacity of 240 ft (73.15 m)
The fiber manager can be front-mounted or mid-mounted in equipment racks
of varying sizes. In order to meet specific installation requirements, the fiber
manager is shipped with five different sets of mounting brackets. Each bracket
is stamped with a letter to identify its type.
The letters and the type of rack each bracket is used with are listed in Table 4-7.
Figure 4-41
Fiber manager
Spring-loaded lock
Cable outlet
Mounting bracket
Note: The fiber manager capacity is 16 fibers x 2 m (6.56 ft) each.
Table 4-7
Mounting bracket labels
Letter Rack type

A EIA 19-in wide with 1.25 in (31.75 mm) hole spacing
B EIA 19-in wide with 1.00 in (25.00 mm) hole spacing
C EIA 23-in wide with 1.25 in (31.75 mm) hole spacing
D EIA 23-in wide with 1.00 in (25.00 mm) hole spacing
E ETSI width with 1.00 in (25.00 mm) hole spacing

5-1
User interface description 5-
This chapter provides an overview of the craft user interface available for the
Optical Multiservice Edge 6500 (OME6500). Table 5-1 lists the topics in this
chapter.
Table 5-1
Topic Page
OME6500 Site Manager 5-1
TL1 interface 5-2
OME6500 Site Manager

OME6500 Release 1.2 introduces support for the Site Manager consolidated
craft interface which is a common launch pad for craft interfaces in different
optical products (HDX, OME6500, OM3000). Each product still retains its
own craft application which can be started/launched using a common tool. The
Site Manager framework is used as the common launcher application:
• Site Manager is started first to login to different network element types
• the Site Manager launcher provides a consolidated alarm banner and fault
summary.
For more information about Site Manager and consolidated craft, refer to Site
Manager for Optical Multiservice Edge 6500 Rel 1.2 Planning and
Installation Guide, NTNM34DC.
The OME6500 Site Manager craft user interface is a graphical, nodal

management tool that is available on a CD or can be downloaded from the
shelf processor. Site Manager is loaded and installed from the CD or shelf
processor on to a computing platform. The craft user interface provides full
access to the OME6500 network element across TCP/IP and to other
OME6500 network element visible across DCC or locally across the network
element's 10/100Base-T and RS232 ports.

5-2 User interface description
Site Manager provides support for the following functions:

• fault and alarm management
• equipment and facility management
• PM viewing and threshold setting
• synchronization management
• upgrades and software download
• backup and restore
• protection status and control
• shelf level view
• nodal security management
• BLSR/MS-SPRing configuration
• nodal connection management
• DCN communications management
Refer to Chapter 6, “OAM&P description” for more information about the
operations, administration, maintenance and provisioning (OAM&P)
capabilities supported by the OME6500.
For more information on Site Manager, refer to Site Manager for Optical
Multiservice Edge 6500 Rel 1.2 Planning and Installation Guide,
NTNM34DC.
TL1 interface
Transaction Language 1 (TL1) allows you to manage SONET/SDH optical
equipment for OME6500. TL1 is a common language protocol for messages
exchanged between network elements and Site Manager. TL1 is based on
Telcordia specifications. TL1 message sets allow you to perform the following
functions:
• testing
• provisioning
• alarm and network surveillance
• performance monitoring
• protection switching
• network security and administration
• inventory retrieval
The OME6500 TL1 interface conforms to standards GR-831, GR-833 and
GR-199 for syntax, information structure and transactions.
6-1
OAM&P description 6-
This chapter provides the operations, administration, maintenance and

provisioning (OAM&P) description for the Optical Multiservice Edge 6500
(OME6500) network element. Table 6-1 lists new OAM&P features in
OME6500 Release 1.2 and Table 6-2 lists OAM&P features OME6500
Release 1.2 continues to support.
Table 6-1
New or enhanced OAM&P features in OME6500 Release 1.2
Topic Page
UPSR/SNCP traffic protection 6-3
DS1 service module support 6-6
DS3/EC-1 support 6-10
Gigabit Ethernet drop-and-continue 6-11
International gateway 6-15
Performance monitoring enhancements 6-17
Time of day synchronization 6-17
Alarm/event enhancements 6-18
Communications enhancements 6-19
User interface enhancements 6-19

6-2 OAM&P description
Table 6-2
OME6500 OAM&P features
Topic Page
Commissioning and testing 6-20
Global support 6-20
Setting the NE mode is provisionable from the Node Information 6-21
application in the Configuration menu in Site Manager.
Facility management 6-25
Loopbacks 6-27
Synchronization management 6-27
1+1/MSP linear traffic protection 6-59
2-Fiber BLSR/MS-SPRing traffic protection 6-61
Traffic protection exerciser 6-66
Unprotected connections 6-67
OME6500 OAM comms 6-68
Alarm and event management 6-72
Backing up and restoring the network element database 6-89
Installing Site Manager software 6-90
Installing and upgrading network element software 6-90
UPSR/SNCP traffic protection

UPSR/SNCP is a type of path protection scheme. In a UPSR/SNCP
configuration, identical traffic is bridged at an entry node and transmitted
simultaneously on two separate ports. At the exit node, the selector function
selects the better quality signal from one of the two paths. Since the exit node
handles the protection switching, there is no need for communication between
entry and exit nodes.
UPSR/SNCP ring is similar to the 1+1 linear/MSP configuration in that

protection is left to the discretion of the exit node. Unlike the 1+1 linear/MSP
configuration, UPSR/SNCP protection is done using the path level indicators
instead of the line level indicators, so that protection switching occurs to the
affected paths only.
The entry and exit nodes are designated at connection provisioning time. A
node can be both entry and exit node in the case of a bidirectional UPSR/SNCP
connection. UPSR/SNCP groups are formed from unprotected facilities when
UPSR/SNCP connections are provisioned on these facilities. All intermediate
nodes have pass-through connections.
Note: The From and Switch mate endpoints for UPSR/SNCP connections
(1WAYPR, 2WAYPR, and 2WAYDPR) can only be provisioned on
unprotected OCn/STMn or GE facilities.
Figure 6-1 shows an example of a UPSR/SNCP configuration, with a

unidirectional STS-n/VC4-n connection between node B and node D. In this
example, node B is the entry node, node D is the exit node, node A and node
C are the intermediate nodes.
Figure 6-1
UPSR/SNCP protection scheme
Node A
STS-n/VC4-n
Node B Node D
Node C

OME6500 supports UPSR/SNCP connections at VT1.5/VC12, STS-1/VC3,

STS-3c/VC4, STS-12c/VC4-4c, STS-24c/VC4-8c, STS-48c/VC4-16c,
STS-192c/VC4-64c rates on the OC-3/STM-1, OC-12/STM-4,
OC-48/STM-16, OC-192/STM-64, and GE interfaces.
Provisioning UPSR/SNCP traffic protection

A UPSR/SNCP configuration requires the following items to be provisioned.
Protection group provisioning
The user performs protection group provisioning from the Provisioning
application in the Protection menu of Site Manager. The user selects
Unprotected protection scheme for a port on an interface circuit pack.
Cross-connect provisioning
The user performs cross-connect provisioning from the Nodal Cross-Connect
application in the Configuration menu of Site Manager.
For bidirectional connections, the user provisions 2WAYPR connections at the

end points as well as selecting an associated switch mate and timeslot. At the
passthrough nodes, the user provisions 2WAY connections. When
interconnecting UPSR/SNCP rings with bidirectional connections, a dual
2WAYPR connection (2WAYDPR) is used.
For unidirectional connections, the user provisions two 1WAY connections at

the entry node, 1WAY connections at the intermediate nodes, and a 1WAYPR
connection at the exit node. When interconnecting UPSR/SNCP rings with
unidirectional connections, two 1WAYPR connections are used.
Note 1: Since UPSR/SNCP provides path level protection, any path can
be protected by any other path (of the same rate) on any interface port.
Unlike line level protection, the interface circuit packs need not be
adjacent to each other. For example, a STS-3c/VC4 on slot 1 port 1 can
provide STS-3c/VC4 protection for a STS-3c/VC4 on slot 3 port 3 and a
STS-3c/VC4 on slot 1 port 1 can also provide STS-3c/VC4 protection for
a STS-3c/VC4 on slot 12 port 1.
Note 2: The OME 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
pass-through nodes that make up the end-to-end circuit.
Note 3: You must provision the UPSR/SNCP protection against the From
and Switch Mate endpoints in 1WAYPR, 2WAYPR, and 2WAYDPR
connections. The From and Switch Mate endpoints (and the To and
Destination Mate endpoints for 2WAYDPR connections) must be
unprotected OCn/STMn or GE ports.
For detailed procedures, see Provisioning and Operating Procedures,
323-1851-310.
UPSR/SNCP protection switch criteria

A UPSR/SNCP protection switch request can occur automatically by the
system or by user initiated actions.
Automatic switch
The protection switch trigger hierarchy is as per Telcordia GR-1400 and
ITU-T G.841. An automatic switch occurs automatically and can be triggered
by the following conditions:
• Facility OOS
• Path AIS
• Path LOP
• Path Unequipped
• Path Excessive BER
• Path Payload Label Mismatch
• Path Trace Identifier Mismatch (see Note)
• Path Signal Degrade
Note: The Path Trace Identifier Mismatch alarm used to trigger an
automatic switch can take up to 48 seconds to be raised after the mismatch
exists.
An automatic switch will be executed only if a higher priority switch request

is not active or the path is available. This release supports non-revertive
switching. This implies that once an automatic switch occurs, traffic will not
revert to the previous active path on a port of an interface circuit pack. An
automatic switch causes an event to be generated indicating a protection
switch occurred.
The automatic switch criteria are user provisionable and apply to the complete
network element (Path AIS and Path LOP are always automatic switch criteria
and cannot be disabled). The default automatic switch criteria depends on the
NE mode as follows:
• For the SONET mode, the default automatic switch criteria are Path AIS,
Path LOP, Path Unequipped, Path Excessive BER, and Path Signal
Degrade.
• For the SDH mode, the default automatic switch criteria are Path AIS and
Path LOP (SNC-I parameters).
Note 1: The provisioning of the automatic switch criteria is independent
of the NE mode.
Note 2: For SDH mode, automatic switch criteria for SNC-N are Path AIS,
Path LOP, Path Unequipped, Path Excessive BER, and Path Signal
Degrade.

User initiated switches

• Manual switch
This command causes the selector at the receiving end to select the
alternate subnetwork connection path. The manual switch has the lowest
priority and will be executed only if the alternate path is available (no
active automatic switch or forced switch). The manual switch is a
non-standing request as once the switch has occurred or is refused, the
request is lowered.
• Forced switch
This command causes the selector at the receiving end to select the
alternate subnetwork connection path regardless of the availability of the
alternate path. The forced switch has the highest priority. The forced
switch is a standing request as it remains active until it is cleared by the
user.
The user performs traffic protection switches from the Status application in
the Protection menu of Site Manager.
Table 6-3 summarizes the hierarchy of protection commands.

Table 6-3
UPSR/SCNP protection - command hierarchy
Switch request Priority

Forced 1 (highest)
Auto (Signal Fail) 2
Auto (Signal Degrade) 3
Manual 4 (lowest)

323-1851-310.
DS1 service module support

Release 1.2 introduces support for the DS1 service module (DSM). A
OME6500 shelf can support up to 16 DSM shelves.
Note: The DSM is not supported if the NE mode is SDH.
Equipment/facility provisioning
The DSM connects to the OME6500 network element through the ports on a
host 8xOC-3/12/STM-1/4 circuit pack. The optical facilities on the
8xOC-3/12/STM-1/4 circuit pack must be provisioned as OC-3 facilities. The
remaining optical facilities on the 8xOC-3/12/STM-1/4 circuit pack can be
used for any service (for example, another DSM or an OC-3/OC-12 1+1 linear
protected configuration).
Note: For DSM support, you must use cross-connect circuit packs and
8xOC-3/12/STM-1/4 circuit packs that support VT1.5/VC12 switching
granularity.
The host OC-3 port against which the DSM 84xDS1 TM circuit pack is to be
provisioned must meet the following requirements:
• port must be in SONET mode and support VT1.5 rate connections
• the port must have an OC-3 facility and section DCC provisioned
• the port must not already be associated with a DSM 84xDS1 TM circuit
pack
• the port must not have cross-connects or protection provisioned
• the port is not provisioned as a shelf timing reference
The user must provision the section DCC on the host OC-3 facilities so that an
OAM link used to communicate with the 84xDS1 TM circuit packs in the
DSM can be established. The user provisions the section DCC on the host
OC-3 facilities from the DSM OAM Link application in the Interfaces tab of
the Comms Setting Management menu of Site Manager. Only OC-3 facilities
meeting the following criteria are available in the DSM OAM Link
application:
• have DS1TM equipment already provisioned
• do not have DS1TM equipment provisioned and the lower layer DCC is
provisioned as section DCC with LAPD and L2 frame size of 1304
• do not have DS1TM equipment provisioned and the lower layer DCC is not
provisioned
• are set to unprotected
Note: The OC-3 host ports are automatically set to 1+1 linear protection
when a 1+1 protected DSM is connected and provisioned on the OC-3 host
ports.
When provisioning (enabling) a DSM OAM link on an OC-3 facility, the
following parameters are set:
• lower layer DCC: Carrier = Section, Protocol = LAPD, L2 Frame Size =
1304
• iISIS circuit: Circuit Default Metric: 6, Neighbour Protocols Supported
Override = OSI

If the DSM is unprotected (no protection DSM 84xDS1 TM circuit pack in slot
2), the host OC-3 facility can be any OC-3 facility in any slot (odd or even). If
the DSM is 1+1 protected (see Protection provisioning on page 6-9 for more
information), the:
• host OC-3 facility connected to the working DSM 84xDS1 TM circuit
pack (slot 1) must be in an odd slot
• host OC-3 facility connected to the protection DSM 84xDS1 TM circuit
pack (slot 2) must be in an even slot
If auto equipping is enabled on an host OC-3 facility (which meets the DSM
OAM link requirements), a DSM 84xDS1 TM circuit pack is automatically
provisioned when the optical fibers are connected between the host OC-3 port
on the OME6500 shelf and the OC-3 port of the 84xDS1 TM circuit pack in
the DSM shelf.
If auto equipping is disabled on an host OC-3 facility, the user can manually
provision a DSM 84xDS1 TM circuit pack using the Equipment & Facility
Provisioning application in the Configuration menu of Site Manager.
Note: It is recommended that the working DSM 84xDS1 TM circuit pack
is manually or automatically provisioned before the protection DSM
84xDS1 TM circuit pack
When the DSM 84xDS1 TM circuit pack is provisioned, no DS1 facilities are
provisioned. You must manually add the DS1 facilities.
Only VT1.5 connections can be provisioned on a DS1 facility and require

cross-connect circuit packs and interface circuit packs that support
VT1.5/VC12 switching granularity.
Note: For 1WAYPR, 2WAYPR, and 2WAYDPR connections on a
UPSR/SNCP network, the DS1 endpoints can only be provisioned on the
To endpoint and cannot be provisioned on the From or Switch Mate
endpoints.
Protection provisioning
The DSM supports:
• non-revertive 1+1/MSP linear protection on the OC-3 facilities (see
1+1/MSP linear traffic protection on page 6-59 for details). The OC-3
facilities on the OME6500 must use the same port number on adjacent
8xOC-3/12/STM-1/4 circuit packs (slots 1/2, 3/4, 5/6, 9/10, 11/12, 13/14).
• non-revertive 1+1 protection on the DSM 84xDS1 TM circuit packs
When a fault or user initiated switch occurs, protection switching occurs
simultaneously on the OC-3 facilities and the DSM 84xDS1 TM circuit packs.
84xDS1 TM circuit pack protection
In the 1+1 protection, the protection switch moves all of the traffic on a
working 84xDS1 TM circuit pack to the protection 84xDS1 TM circuit pack,
enabling the faulty working 84xDS1 TM circuit pack to be replaced without
affecting traffic.
84xDS1 TM protection group provisioning
The 1+1 protection is automatically provisioned when a protection 84xDS1
TM circuit pack is automatically or manually provisioned in slot 2 of the DSM.
The 1+1 protection cannot be changed manually. The user can view the 1+1
protection parameters but cannot change them.
1+1 84xDS1 TM protection switch criteria
1+1 84xDS1 TM equipment protection switch request can occur automatically
by the system or by user initiated actions.
• Automatic switch
An automatic switch occurs automatically after the following failures:
— equipment unavailability (circuit pack removal, reset, fail)
— OC-3 facility alarms: loss of signal, loss of frame, AIS, section trace
mismatch, signal fail, signal degrade, circuit pack loss of host timing
ref
— OC-3 facility out-of-service
This release supports non-revertive switching, when an automatic switch
occurs, traffic does not revert to the previous circuit pack. The automatic
switch is a non-standing request as once the switch has occurred or is
refused, the request is lowered.
• Manual switch
This command switches the DS1 signals from the working circuit pack to
the protection circuit pack. The manual switch has the lowest priority of
user initiated switch request and occurs only if a higher priority switch is
not active (no active automatic switch, forced switch, or protection circuit
pack failed). The manual switch is a non-standing request as once the
switch has occurred or is refused, the request is lowered.

• Forced switch
This command switches the DS1 signals from the working circuit pack to
the protection circuit pack regardless of the effect on traffic. The forced
switch occurs only if the protection circuit pack is available. The forced
switch is a standing request as it remains active until it is released by the
user.
Table 6-10 shows the hierarchy of protection commands.
Table 6-4
1+1 84xDS1 TM equipment protection hierarchy
Switch request Priority

Automatic (Protection) 1 (highest)
Forced 2
Automatic (Working) 3
Automatic (Signal Degrade) 4
Manual 5 (lowest)
DS3/EC-1 support
Release 1.2 introduces support for the 24xDS3/EC-1 circuit pack.
Facility provisioning
The 24xDS3/EC-1 circuit pack has 24 ports which can be configured as
follows:
• if the NE mode is SONET, each port can be configured as a DS3 or EC-1
facility
• if the network element mode is SDH, each port can be configured only as
a DS3 facility (EC-1 facilities are not supported)
Note: When the 24xDS3/EC-1 circuit pack is provisioned, no DS3 or
EC-1 facilities are provisioned. You must manually add the DS3 or EC-1
facilities.
If the network element mode is SONET, STS-1 cross-connects can be

provisioned on a DS3 facility and VT1.5 or STS-1 cross-connects can be
provisioned on a EC-1 facility.
If the network element mode is SDH, LO_VC3 cross-connects can be

provisioned on a DS3 facility.
The DS3 and EC-1 facilities support 16 byte path trace for the VT1.5, STS-1,
and LO_VC3 cross-connects.
Note 1: For VT1.5 support, you must use cross-connect circuit packs and
optical interface circuit packs that support VT1.5/VC12 switching
granularity.
Note 2: For 1WAYPR, 2WAYPR, and 2WAYDPR connections on a
UPSR/SNCP network, the DS1/EC-1 endpoints can only be provisioned
on the To endpoint and cannot be provisioned on the From or Switch Mate
endpoints.
Protection provisioning
OME6500 supports 1:N equipment protection of the 24xDS3/EC-1 circuit
packs. The 1:N protection is arranged in two banks of 1:4 protection where up
to four 24xDS3/EC-1 working circuit packs are protected by a single
24xDS3/EC-1 protection circuit pack.
Note: The default protection mode is unprotected. If required, 1:N

protection must be provisioned by the user.
In the 1:N protection, the protection switch moves all of the traffic on a
working circuit pack to the protection circuit pack, enabling the faulty working
circuit pack to be replaced without affecting traffic.
The two banks of 1:4 protection are provided by:

• 24xDS3/EC-1 working circuit packs in slots 1 to 4 and a protection circuit
pack in slot 13
• 24xDS3/EC-1 working circuit packs in slots 9 to 12 and a protection circuit
pack in slot 14
For more information, refer to 63xE1 and 24xDS3/EC-1 circuit pack
protection on page 6-53.
Gigabit Ethernet drop-and-continue

OME6500 extends its unidirectional multi-node drop-and-continue capability
to support unidirectional Gigabit Ethernet (GE) traffic. Unidirectional
multi-node drop-and-continue provides the ability to drop a time slot, either
SONET/SDH contiguous (STS-1/VC3, STS-3c/VC4, STS-12c/VC4-4c and
STS24c/VC4-8c) or virtual concatenation (STS-1-nv/VC3-nv, n = 1 through
21 or STS-3c-nv/VC4-nv, n = 1 through 7), at a single or on a continuing series
of nodes in an UPSR/SNCP, BSLR/MS-SPRing, or 1+1/MSP linear chain
configuration using a single timeslot.
Figure 6-2 shows an application where a video signal is inserted on a 4xGE

interface at one node and dropped on 4xGE interfaces at 5 subsequent nodes
using a unidirectional CCAT or VCAT timeslot(s).

Figure 6-2
Gigabit Ethernet drop-and-continue application
UPSR/SNCP
Node 6 Node 5 1WAYPR
connection used
Node 1 Node 4
UPSR/SNCP
Video
4xGE
distribution
EPL
head end VCAT (STS1-nv/VC3-nv
Node 2 Node 3 or STS3c-nv/VC4-nv)
and CCAT
cross-connects
supported. Time slots
re-used around ring.
Legend
OME6500 4xGE
EPL
Because the connection is unidirectional, the other direction (timeslot) can be

reused for another circuit. Unidirectional drop-and-continue on OME6500 can
be used to provide applications such as video broadcast, multi-media
conferencing, and distance learning for residential, business, research, and
educational services.
Note: For procedures on provisioning cross-connects in GE

drop-and-continue applications (including dual feeds from a single node in
UPSR/SNCP configurations and dual feeds from different nodes in
UPSR/SNCP configurations), refer to Provisioning and Operating
Procedures, 323-1851-310.
At the GE unidirectional add node, local client failures are propagated to the
far end using client signal fail (CSF) client management frames (CMFs). If
subrate GE WAN bandwidth is provisioned, enabling PAUSE flow control
may be required if the connected equipment cannot properly send the GE
traffic to match the provisioned WAN bandwidth.
Figure 6-3 shows a GE drop-and-continue application with two redundant

feeds (each providing two broadcast GE signals). OME6500 #1 and #7 provide
separate feeds onto a configuration of two UPSR/SNCP rings. At each drop
node, the UPSR/SNCP configuration selects either the feed from OME6500 #1
or the feed from OME6500 #7. UPSR/SNCP path switching is triggered by an
path unequipped signal sent from the faulty add node (OME6500 #1 or
OME6500 #7).
Protection switching at the end nodes is as follows:

• at the drop nodes (OME6500 #2, #3, #4, #5, and #6), any GE facility
failure at the drop node requires a manual switch (put good ports in-service
and the bad ports out-of-service)
• at the add (head-end) nodes (OME6500 #1 and #7), the path unequipped
signal is sent to trigger UPSR/SNCP switching if the port is put
out-of-service. In addition, the user can select the WAN conditioning as
unequipped, nil trace, unequipped & nil trace, and GFP CMFs for other
Ethernet failure scenarios (for example, loss of signal, loss of data sync, or
link down). Refer to Provisioning and Operating Procedures,
323-1851-310, for details of WAN conditioning.

Figure 6-3
Gigabit Ethernet dual feed drop-and-continue application
OME6500
OME6500 OME6500 #6
#2 #3
Broadcast Broadcast
GE #1 OME6500 OME6500 OME6500 GE #1
GE #2 #1 #4 #7 GE #2
Primary Secondary
Source OME6500 Source
#5
OC48/STM16 Cross-connect OC48/STM16

(Slot 5) (Slot 6)
4xGE 4xGE
(Pri) (Sec)
OME6500
Legend
Video feeds
(primary) GE
CLIENT
Video feeds EQUIPMENT
(secondary)
GE port (IS)
GE port (OOS)
UPSR/SNCP
selected feeds
Fiber connection
Idle link
Engineering rules
• Unidirectional GE traffic is supported on 1+1/MSP linear,
BLSR/MS-SPRing, and UPSR/SNCP configurations.
• A valid Gigabit Ethernet signal must be connected to the receiver interface
of the 4xGE port at each drop node, otherwise GE idles will be transmitted.
Note: An external optical splitter can be used to loop back the GE signal
from the Tx port to the Rx port of 4xGE, if the connected equipment cannot
provide a valid GE signal.
• Auto-negotiation (AN) can be enabled, however both the receive (Rx) and
transmit (Tx) fibers must connect to the same partner otherwise
auto-negotiation will not complete properly.
Note: It is recommended to disable auto-negotiation (AN) and pause
transmit (PAUSETX) frames at the drop nodes in this configuration.
• In UPSR/SNCP configurations, you must ensure that the WAN

conditioning settings at the add nodes match the path protection switch
criteria at the drop nodes (refer to Provisioning and Operating Procedures,
323-1851-310, for details).
Note 1: As only unequipped is sent when a GE facility is placed
out-of-service, it is recommended that both unequipped and path trace are
provisioned as path switching criteria in the UPSR/SNCP.
Note 2: The WAN conditioning parameter must be set to the same on both
GE sources feeding the UPSR/SNCP.
Note 3: If provisioning virtual concatenation connections for the GE
feeds, at the drop nodes ensure that the virtual concatenation parameter is
set to ‘Enabled; Grouped’ for the GE facility.
• In UPSR/SNCP configurations, for drop nodes it is recommended that the
Ethernet transmit conditioning is disabled.
Note: See Supported unidirectional configurations on page 6-47 for
configurations and limitations regarding drop-and-continue (broadcast)
connections.
International gateway
OME6500 Release 1.2 introduces the international gateway feature which
allows the OME6500 to function in mixed SONET/SDH environments by
allowing individual OC-48/STM-16 ports to be provisioned to SONET or
SDH mode. For example, the NE mode can be set to SONET but an individual
OC-48/STM-16 port can be provisioned to the SDH mode. The feature is
useful for customers with SONET/SDH network elements that need to support
SDH/SONET ports (for example, a North American SONET customer
servicing a submarine cable coming from Europe in the SDH mode).

Setting the port mode, sets the SS bits, section trace format, path trace, ALS,
RDI insertion, and DCC diversity parameters to the selected port mode (see
Global support on page 6-20).
Engineering rules
The port mode is set during the adding of an optical facility with the following
rules:
• by default, the port mode is set to the NE mode
• only OC-48/STM-16 ports with unprotected or 1+1/MSP linear protection
schemes are supported in this release
• supports conversions between:
— STS-1 and LO_VC3 (see Figure 6-4)
— STS-3c and VC4
— STS-12c and VC4-4c
• the port mode is not editable, you must set the mode during adding of the
optical facility. Once set, to change the port mode you must delete the
facility and then add the facility again with the correct port mode.
Note: An OC-48/STM-16 facility is automatically added when the
OC-48/STM-16 port is added. To change the port mode, you must delete
the automatically provisioned facility and re-add it with the correct port
mode.
• for 1+1/MSP linear protection scheme, both working and protection
facilities must be set to the same port mode
• cross-connects require low-order cross-connect circuit packs and
low-order interface circuit packs for both the SONET STS-1 the SDH LO
VC3 endpoints
• you cannot use an international port (one where the port mode is different
from the NE mode) for synchronization.
Figure 6-4
STS-1 to LO_VC3 gateway connections
Low Order Port Low Order Port

Circuit Pack Circuit Pack
OC-48 STS-1 TU3 TUG3 VC4 AU4 STM-16
AUG
Provisioning cross-connects
When adding an cross-connect requiring conversion in Site Manager, the user
selects an OC-48 SONET facility as the ‘from’ instance and a STM-16 SDH
facility as the ‘to’ instance (or vice-versa). Refer to Provisioning an Operating
Procedures, 323-1851-310 for details.
Performance monitoring enhancements

FTP of performance monitoring data
Due to the high capacity and capabilities provided by the OME6500 network
element, the amount of performance monitoring data that is sent to the network
management system (OMEA) can be large. This release provides an option to
transmit the PM data in a compressed format to a specified URL instead of
transmitting the full PM data. This can reduce the bandwidth required for PM
data by over 90%.
The option to send the PM data in compressed format is achieved by adding

optional parameters in the TL1 retrieve PM commands. The optional
parameters specify the URL to be used for the FTP and the compression format
(GZIP to RFC 1952 only in current release). These optional parameters are
added to the TL1 commands sent by the OMEA when requesting PM data, no
user intervention is required.
Support for DS1, DS3, and EC-1 performance monitoring

Release 1.2 provides enhancements to support performance monitoring and
performance monitoring thresholds for DS1, DS3, and EC-1 facilities. Refer
to Performance monitoring on page 6-75 for more information.
Time of day synchronization

Release 1.2 introduces a time of day (TOD) synchronization feature which
allows the shelf processor to synchronize its time with SNTP servers:
• up to 5 SNTP server IP addresses can be provisioned (no servers set as
default)
• synchronization frequency of the shelf processor can be provisioned in
10 minute granularity up to 24 hours (default 1 hour)
• the shelf processor selects the SNTP server to use based on stratum and
availability
When TOD synchronization is enabled, the shelf processor time is
automatically adjusted after a shelf processor replacement or shelf power
failures. If no SNTP server is available, the shelf processor time is based on an
internal clock. When an SNTP server is available, the shelf processor time is
automatically adjusted after shelf processor replacement or shelf power
failures.

If OMEA server(s) are managing the OME6500 network element, TOD

synchronization is automatically provisioned when the network element is
enrolled by the OMEA so that timestamps for alarms and events are aligned.
When the OMEA enrols the OME6500 network element, the OMEA:
• first sets the OME6500 time to the OMEA time (setting the time to the
OMEA time first ensures that the initial timestamps are aligned as
alignment using SNTP can take several minutes)
• provisions the primary OMEA server as the first SNTP server on the
OME6500 network element
• in a resilient OMEA configuration, provisions the secondary OMEA
server as the second SNTP server on the OME6500 network element
• if applicable, removes the third, fourth, and fifth SNTP servers provisioned
on the OME6500 network element
• sets the polling interval on the OME6500 network element to 1440 minutes
(24 hours)
If managed by the OMEA, it is recommended that you do not manually
provision the SNTP servers. If SNTP servers are manually provisioned, the
TOD provisioning information is replaced when the network element is
enrolled by the OMEA and whenever communications is re-established after
a communications break between the OME6500 network element and the
OMEA servers.
The user can provision TOD synchronization from the Node Information
application in the Configuration menu of Site Manager. For detailed
procedures, see Provisioning and Operating Procedures, 323-1851-310.
Alarm/event enhancements
Increased VT1.5/VC12 alarm support
In Release 1.1, the alarm monitoring of VT1.5/VC12 facilities was limited to
336 for each optical interface circuit pack, any request to monitor more than
this limit was rejected. In Release 1.2, the limit for alarm monitoring of
VT1.5/VC12 facilities is increased to 1344 for each optical interface circuit
pack.
Support for DS1, DS3, and EC-1 alarms
Release 1.2 provides enhancements to support DS1, DS3, and EC-1 facility
alarms and DSM equipment alarms. Refer to Alarm and event management on
page 6-72 for more information.
Communications enhancements
Nested Telnets
When connected to an OME6500 network element, a user can now Telnet to a
remote network element from the initial Telnet session.
Note: Nested Telnets are available in the General Utilities Menu of the
command line interface available when using a Telnet or a terminal
session.
OME6100 interworking
Release 1.2 supports interworking with the OME6110 network element. For
details and configuration examples, refer to the OME6100 Planning Guide.
OSI ping
Release 1.2 supports three new OSI ping tools that can be used to verify OSI
connectivity (netping, coping, and clping).
Note: These tools are available in the General Utilities Menu of the
command line interface available when using a Telnet or a terminal
session.
User interface enhancements

Site Manager enhancements
OME6500 Release 1.2 introduces support for the Site Manager consolidated
craft interface which is a common launch pad for craft interfaces in different
optical products (HDX, OME6500, OM3000). For more information about
Site Manager and consolidated craft, refer to Site Manager for Optical
Multiservice Edge 6500 Rel 1.2 Planning and Installation Guide,
NTNM34DC.
TL1 shelf AID extension
OME6500 Release 1.2 adds support for a shelf AID extension which will be
expanded in future releases to support TID consolidation. For Release 1.2, all
commands that use the AID field or have AIDs in the command parameter
fields have been changed to include the shelf AID extension. In addition, the
RTRV-SHELF command is introduced to allow the shelf number to be
retrieved. For Release 1.2, the shelf value is fixed at ‘1’.
The shelf number is visible in Site Manager in the Node Information and
Shelf Level View applications and in TL1 commands and responses when
viewing the Comm Log. The shelf number is also required when sending
commands in the TL1 Command Builder application.

Commissioning and testing

Commissioning and testing is a three part process consisting of commissioning
an OME6500 network element, site testing, and system testing.
Commissioning and site testing bring a newly installed OME6500 network
element to an in-service state ready to carry traffic. System testing verifies the
end-to-end traffic continuity and performance of the network.
For more information about the commissioning and testing process, refer to
Commissioning and Testing, 323-1851-221.
Commissioning Assistant Tool

The Commissioning Assistant Tool (CAT) is a task based application that
guides the user through the commissioning process step by step. The CAT tool
has a navigation tree containing a list of commissioning tasks and a task panel
which contains the detailed steps required to complete the commissioning task.
For each item in the navigation task tree, there is a corresponding task panel.
The CAT application is accessible from the Tools menu in Site Manager. For
more information on the CAT, refer to Commissioning and Testing,
323-1851-221.
Global support
Optical Multiservice Edge 6500 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. On initial startup, the NE mode is Unknown and the system
raises a NE Mode Unknown alarm. While the network element is in the
Unknown mode, the user cannot provision other aspects of the network
element.
The user sets the NE mode to either SONET or SDH during initial
commissioning. When the user sets the mode, the NE Mode Unknown alarm
clears and the user can provision the network element.
Note 1: You cannot change the mode from SONET to SDH or from SDH
to SONET. To change the mode, you must first delete all provisioning and
change the mode to Unknown.
Note 2: You cannot change the mode back to Unknown unless you delete
all provisioning (equipment, facilities, synchronization, and related
entities).
The NE mode defines the defaults for some provisioning items as detailed in
Table 6-5. 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-5
NE mode - differences between SONET mode and SDH mode
Provisioning item SONET mode SDH mode

Cannot be overridden by user
Port mode (see International gateway Optical ports support OC-n Optical ports support STM-n
on page 6-15) interfaces interfaces
Linear protection mode Supports 1+1 APS linear Supports MSP linear
(Telcordia GR-253) (ITU-T G.841)
Ring protection terminology Uses BLSR Uses MS-SPRing
ESI/ESO mode Supports DS1 (1.5 Mbit/s) Supports 2 MHz and E1
interfaces (2 Mbit/s) interfaces
SSM format Optical and ESI/ESO ports Optical and ESI/ESO ports use
use SONET quality levels SDH quality levels
PM and OMs Supports bit based PM Supports block based PM
Path RFI/RDI insertion AIS and LOP AIS, LOP, TIM, and
Unequipped
Connection terminology Uses VT and STS Uses VC and AU (J, K, L, M)
Site Manager terminology SONET SDH
Can be overridden by user
Automatic equipping Defaults to enabled for all Defaults to disabled for all slots
(can be overridden on a slot basis) slots
SS bits (signal mode) Optical ports default to Optical ports default to SDH
(can be overridden on a port basis) SONET (00) (10)
Section trace format Defaults to 16-byte string Defaults to 1-byte number
(can be overridden on a port basis) format format (0 to 255)
(see Note 2) (up to 15 character input)
Path trace format Defaults to 64-byte format Defaults to 16-byte format
(can be overridden on a STS/VC (up to 62 character input) (up to 15 character input)
payload basis) (see Note 2) (see Note 1)
Automatic laser shutdown Optical ports default to Optical ports default to enabled
(can be overridden on a port basis) disabled
Note 1: VT/VC12 path trace always uses a 16-byte format irrespective of the NE/port mode.
Note 2: Alarm monitoring for section trace and path trace is disabled as default irrespective of the NE
mode.
Setting the NE mode is provisionable from the Node Information application

in the Configuration menu in Site Manager.

Equipment management
In OME6500, equipment is a logical entity and is the software representation
of a circuit pack. Two types of equipment entities exist in the OME6500
platform as follows:
• provisionable equipment – represents equipment that can be provisioned
and managed by user commands. These entities reside in slots 1 through
14 of the OME6500 shelf and include the following equipment:
— cross-connect circuit pack (slot 7 and 8)
— interface circuit packs (slots 1-6 and 9-14)
– 1xOC-192/STM-64 circuit pack (slots 5, 6, 9, and 10)
– 2xOC-48/STM-16 circuit pack (slots 1-6 and 9-14)
– 8xOC-3/12/STM-1/4 circuit pack (slots 1-6 and 9-14)
– 4xGE EPL circuit pack (slots 1-6 and 9-14)
– 63xE1 working circuit pack (slots 1-4 and 9-12)
– 63xE1 protection circuit pack (slots 13 and 14)
– 24xDS3/EC-1 working circuit pack (slots 1-4 and 9-12)
– 24xDS3/EC-1 protection circuit pack (slots 13 and 14)
– 84xDS1 termination module (slots 1 and 2 of DSM shelf, related to
a host OC-3 slot/port on OME6500 shelf)
— pluggable optical modules
• non-provisionable equipment – represents equipment not managed by user
commands but required to operate an OME6500 network element.
Non-provisionable equipment includes the following:
— cooling units
— access panel
— power input cards
— maintenance interface card
— shelf processor
— shelf backplane
— filler cards
— I/O panels
— 120 ohm converter modules
— I/O protection modules
Note: Although this equipment is non-provisionable, the equipment is
inventoried. The equipment (except the access panel, maintenance
interface card, and 120 ohm converter modules) is also alarmed.
Figure 6-5 shows a layout of the OME6500 shelf and the slot numbering
scheme. Figure 6-6 shows the port numbering scheme for the interface circuit
packs.
Figure 6-5
OME6500 shelf layout
Access Panel
17-1
80 Gbit/s Cross-connect Slot

80 Gbit/s Cross-connect Slot
Pwr
10 Gbit/s Interface Slot


Shelf processor
17-2
Filler card
MIC
17-3
Pwr
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Fiber routing channel
Figure 6-6
Port numbering scheme for interface circuit packs
10-1
10-2
10-1
10-3
10-2 10-1
10-4 10-1
10-3 10-2
10-5
10-4
10-6
10-7
10-8
Slot 10 Slot 10 Slot 10 Slot 10
8 port pluggable 4 port pluggable 2 port pluggable 1 port pluggable

circuit pack circuit pack circuit pack circuit pack

Managing provisionable equipment

Provisionable equipment refers to any equipment entity that can be
provisioned and managed by user commands. The following is a list of
provisionable actions available to the user.
Setting the automatic equipping mode for the shelf is provisionable from the
Shelf Level View application in the Configuration menu of Site Manager.
Automatic equipping
Automatic equipping refers to the automatic creation and enabling of
functionality when the automatic equipping mode is enabled. Automatic
equipping occurs when the user:
• inserts a circuit pack into an unequipped valid slot
• inserts a pluggable module (SFP or DPO) into an unequipped valid
interface circuit pack socket
• automatic equipping is enabled for a slot which has a circuit pack
physically inserted and no equipment already provisioned
You do not require user commands to create the equipment or pluggable
module entities.
Note 1: Automatic equipping is enabled by default if the network element

mode is SONET and disabled by default if the network element mode is
SDH.
Note 2: For equipment supporting multiple service types and rates (for
example, the OC-3/12/STM-1/4 or GE/FC SFPs or the DS3/EC-1 circuit
pack), the user must manually equip the type/rate for each port.
Note 3: Automatic equipping of DS1 service modules (DSM) is dependent
on the auto equipping mode of the host OC-3 facility.
After insertion into the shelf, the system creates the circuit pack and pluggable
module software attributes. The attributes are visible in the OAM&P
management system through applications such as Inventory, Shelf Level
View, and Equipment & Facility Provisioning in Site Manager.
Manual equipping
Manual equipping refers to the manual creation and enabling of functionality
on a circuit pack when inserted into an unequipped valid slot, or a pluggable
module when inserted into an unequipped valid interface circuit pack socket.
User commands create the equipment, pluggable module, or non-payload
facility entities. The user performs manual equipping from the Equipment &
Facility Provisioning application in the Configuration menu of Site
Manager.
When provisioned, the system creates the circuit pack and pluggable module
software attributes. The attributes are visible in the OAM&P management
system through applications such as Inventory, Shelf Level View, and
Equipment & Facility Provisioning in Site Manager.
Unequipping
Unequipping refers to the manual deletion and disabling of functionality of a
circuit pack or a pluggable module. You cannot unequip a circuit pack if the
equipped circuit pack is providing a service (the facility state is in-service [IS]
and is being used as a synchronization source, carries DCC, has protection
provisioned on it, or has a connection provisioned). The connection must first
be deleted and the facility deprovisioned before a circuit pack can be
deprovisioned. The user performs manual unequipping (deleting equipment)
from the Equipment & Facility Provisioning application in the
Configuration menu of Site Manager.
When unequipped, the circuit packs and pluggable modules are no longer
visible in the OAM&P management system.
Provisionable cards and load management
The provisionable cards support auto-upgrade/downgrade of their software to
match the shelf software version. The upgrade/downgrade occurs
automatically without user intervention when the user inserts a provisionable
circuit pack with the incorrect software load in the shelf.
For a complete list of editable and retrievable parameters, refer to Provisioning

and Operating Procedures, 323-1851-310.
Facility management
A facility represents an equipment’s OAM&P capabilities that allow the user
to provision, inspect, and control that equipment. Facilities can be divided into
two categories for the OME6500 platform as follows:
• payload facilities: these facilities are endpoints of a SONET/SDH
connection. Examples of these facilities are VT1.5/VC12, STS-1/VC3,
STS-3c/VC4, STS-12/VC4-4c, STS-24c/VC4-8c, STS-48c/VC4-16c, and
STS-192c/VC4-64c.
• non-payload facilities: these facilities refer to the optical and electrical
interfaces, synchronization, DCC, management ports, and data facilities
that are not payloads. Examples are GE, E1, DS1, DS3, EC-1,
OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, and OC-192/STM-64.
For a complete list of editable and retrievable parameters for each layer, refer
to Provisioning and Operating Procedures, 323-1851-310.

Managing facilities
Provisioning of the facilities normally occurs when the user provisions the
associated equipment. Facility provisioning is a nodal function that allows you
to query and edit facility attributes on a specific network element. Facility
provisioning applies to all provisionable equipment in the OME6500.
When you insert a circuit pack in a shelf, automatic or manual provisioning

• provisions the circuit pack with default values
• puts the circuit pack in-service
• places facilities in that circuit pack in-service
For non-payload facility entities supporting multiple service types and/or rates
(for example, 8xOC-3/12/STM-1/4, 4xGE, 24xDS3/EC-1, DSM DS1TM,
63xE1), the user must manually provision each port.
The user manages facilities from the Equipment & Facility Provisioning
When you change a facility from in-service (IS) to the out-of-service (OOS)
state, the following occurs:
• traffic is not carried on the facility
• system inserts both line/MS AIS and path AIS on the signal (optical
interface circuits)
• system inserts AIS (electrical interface circuits)
• system inserts an unequipped signal label on the WAN side and turns the
laser off on the Ethernet side (GE circuit packs)
• traffic alarms for the facility clear
• performance monitoring terminates for the facility
• line/MS DCC, if provisioned, is disabled (section/RS DCC remains active
if provisioned)
Note: You cannot change the state of an equipment if the facility
associated with the equipment is in-service (except for E1 and DS3/EC-1
equipment).
System parameters
The OME6500 supports system or network element wide parameters. The user
provisions and views system parameters from the Node Information
Some system facility parameters are not editable by the user but are used by
the system to trigger actions (for example, Ethernet/WAN thresholds). For a
complete list of editable and retrievable parameters for each layer, refer to
Provisioning and Operating Procedures, 323-1851-310.
Loopbacks
The OME6500 supports the following types of loopback:
• Facility - the received line signal is looped back towards the optical
transmitter/electrical interface immediately on entering the circuit pack.
The following conditioning is applied in the signal towards the
cross-connect circuit pack:
— OC-n/STM-n facilities: line/MS AIS
— GE (WAN) facilities: path unequipped
— DS1 facilities: DS1 AIS
— EC-1 facilities: EC-1 AIS
— E1 facilities: E1 AIS
• Terminal - the line signal just prior to the optical transmitter/electrical
interface is looped back towards the cross-connect circuit pack. The
following conditioning is applied in the signal towards the
optical/electrical interface:
— OC-n/STM-n facilities: none
— GE (WAN) facilities: no link pulse
— EC-1 facilities: EC-1 AIS
— E1 facilities: E1 AIS
Figure 6-7 provides an overview of a terminal and facility loopback.
The user performs loopbacks on an OC-n/STM-n, GE, DS1, DS3, EC-1, or E1

facility port from the Equipment & Facility Provisioning application in the
Configuration menu of Site Manager. A loopback on a facility requires that
the associated facility be out-of-service. A facility and a terminal loopback
cannot be performed on the same facility at the same time.
For detailed procedures, refer to Provisioning and Operating Procedures,

323-1851-310.

Figure 6-7
Facility and terminal loopbacks
Optical Optical
circuit pack circuit pack
AIS
To To
cross-connect cross-connect
Facility Terminal
loopback loopback
OC-n/STM-n circuit packs
GE circuit pack GE circuit pack

Path Uneqp
To To
cross-connect No Link cross-connect
circuit pack Pulse circuit pack
LAN side Facility WAN side LAN side Terminal WAN side
loopback loopback
GE circuit packs
Electrical Electrical
AIS
To To
Electrical cross-connect Electrical cross-connect
interface circuit pack interface circuit pack
AIS
Facility Terminal
loopback loopback
Electrical circuit packs
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.
The OME6500 provides network element synchronization using 1+1

redundant synchronization hardware on the cross-connect circuit pack for both
timing generation and timing distribution.
Synchronization provisioning on the OME6500 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 OME6500 network element
at each site.
Timing generation
Timing generation is the ability of the OME6500 to extract and use the
synchronization reference from any of the defined synchronization inputs. The
OME6500 generates shelf timing signals based on external, line, or internal
(freerun or holdover) references. The OME6500 supports a timing generation
hierarchy of up to four timing references.
The OME6500 is capable of generating a redundant 4.6 ppm quality clock

internally (internal timing mode). This clock is the default synchronization
reference. The OME6500 also supports synchronizing to a reference clock
signal derived from the following sources (provisioned by the user as defined
by the network synchronization plan):
• external timing
An external timing reference input such as a timing signal generator can be
used to provide redundant DS1 (SONET), E1 (SDH), or 2.048 MHz (SDH)
signals to the external synchronization input (ESI) interfaces ESI-A or
ESI-B. See Figure 6-8 on page 6-31 example (b).
Note 1: If the network element is in the SDH mode, the signal format must
be the same on all ESI and ESO ports. ESI-A, ESI-B, ESO-A, and ESO-B
must all be set to either 2 MHz or 2 Mbit/s (E1).
Note 2: To maximize reliability, the BITIN/ESI ports require the payload
of the incoming signal to be all 1’s. The BITIN/ESI hardware may not
operate correctly with other payload patterns.

• line timing
Line timing is a clock derived from a port of an OC-n/STM-n interface
circuit pack. See Figure 6-8 on page 6-31 example (c). OME6500 supports
a hierarchy of up to four inputs.
When using line timing to provide the timing reference for the OME6500,
you must consider the OC-n/STM-n ports to be used for line timing.
Note 1: One port per OC-n/STM-n circuit pack can be used as a timing
reference. A port on a different OC-n/STM-n circuit pack must be selected
when defining more than one timing reference in the hierarchy.
Note 2: DS1 service module (DSM) facilities and OC-3 ports which are
provisioned as DSM hosts cannot be used as timing references.
Note 3: OC-48/STM-16 ports being used as international gateways (port
mode is different from NE mode) cannot be used as timing references.
• mixed timing
The OME6500 enables the user to provision both external and line timing
as a timing references for the four input hierarchy.
Note: For information and guidance on provisioning the timing generation
parameters, refer to Provisioning and Operating Procedures,
323-1851-310.
The OME6500 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 OME6500 falls into holdover mode. In the holdover
mode, the cross-connect 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.6 ppm
clock). See Figure 6-8 on page 6-31 example (a).
The OME6500 allows the user to modify the timing mode without
deprovisioning the active timing reference as follows:
• from line to mixed timing
• from external to mixed timing
All other timing mode changes require the user to deprovision the timing
reference source before changing the source.
Note: The user cannot deprovision an active timing reference. The user
must first switch away from the active timing reference to another valid
timing reference. If no other valid timing references are available, the
active timing reference must be locked out. Refer to Synchronization
protection on page 6-36 for information about performing a lockout.
Refer to Viewing and management on page 6-34 for information about the
synchronization application in Site Manager and on provisioning external
timing, line timing, or mixed timing on the OME6500.
Figure 6-8
Flow of synchronization timing signals
Stratum 3 (ST3)/G.813 Option 1

or better
Access Panel Access Panel
Clock Port Port

Port Port
Cross-connect Cross-connect
(a) Internal timing (b) External timing
Access Panel
Port Service interface port
Port Port Clock Internal clock generator

Cross-connect Synchronization timing
External synchronization reference

(c) Line timing
Traffic flow
Timing distribution
Timing distribution is the ability of the OME6500 to provide a synchronization
reference to external devices. The OME6500 distributes shelf timing signals
through the external synchronization output (ESO) interfaces located on the
access panel. The OME6500 distributes a DS1 (SONET), 2 Mbit/s (SDH), or
2.048 MHz (SDH) clock at each of its ESO-A and ESO-B interfaces based on
a timing reference derived from the following sources:
• an external clock source such as a timing signal generator used to provide
a DS1 (1.5 Mbit/s), 2 Mbit/s, or 2.048 MHz clock to the ESI interfaces
located on the access panel
• a clock derived from any of the OC-n/STM-n signals
Note 1: One port per OC-n/STM-n circuit pack can be used as a timing
reference. If a port on an OC-n/STM-n circuit pack is selected as the timing
reference for timing generation, that same port on the same OC-n/STM-n
circuit pack can be used for timing distribution.
Note 2: If the network element is in the SDH mode, the signal format must
be the same on all ESI and ESO ports. ESI-A, ESI-B, ESO-A, and ESO-B
must all be set to either 2 MHz or 2 Mbit/s (E1).

The OME6500 supports a hierarchy of up to four timing references for timing

distribution.
Note: For information and guidance on provisioning the timing

distribution parameters, refer to Provisioning and Operating Procedures,
323-1851-310.
Refer to Viewing and management on page 6-34 for information about the
Synchronization application in Site Manager and for an overview on
provisioning OME6500 to act as a timing source.
Synchronization operating modes

The OME6500 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 (default setting)
• locked
• holdover
Freerun mode
In freerun mode, the voltage controlled crystal oscillator (VCXO) clock is not
locked to a timing reference and runs at its natural frequency. The
synchronization hardware on the cross-connect circuit pack provides timing
references of internal Stratum 3 (ST3)/G.813 Option 1 quality (4.6 ppm). The
OME6500 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 alarm is
raised to advise the user.
Locked mode
In locked mode, the VCXO clock is locked to a timing reference. The
OME6500 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
VCXO clock in the synchronization hardware holds within a certain frequency
range of the last locked-in timing reference in which case a warning alarm is
raised to advise the user.
When a valid 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.
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 OC-n/STM-n interfaces), and the internal clock of the
network element.
A network element can select the best of the four timing signals provided by
the timing sources provisioned by the user. The selection is based on the
quality values carried in the SSMs. SSMs are carried in bits 5 through 8 of the
S1 byte in the SONET/SDH line/MS overhead and the DS1 ESF datalink code
byte (SONET) or E1 SAN nibble (SDH) of the ESI/ESO signals. 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 (DUS) message. See Table 6-6 for an
overview of SSM designations supported by OME6500.
Table 6-6
Synchronization status messages
Description Designation Quality level
SONET SDH SONET SDH
Primary reference source (traceable to G.811) ST1 PRS 1 2
Synchronization traceability unknown STU - 2 -
Stratum 2 (G.812 Type II) ST2 - 3 -
Synchronization supply unit A TNC SSU-A 4 4

(G.812 Type V, Transit node clock)
Stratum 3E (G.812 Type III) ST3E - 5 -
Stratum 3 (G.812 Type IV) ST3 - 6 -
Synchronization supply unit B - SSU-B - 8

(G.812 Type VI, Local node clock)
SDH equipment clock - SEC - 11
SONET minimum clock SMC - 7 -
Do not use for synchronization DUS DUS 9 15
Provisionable network operator PNO - - -
Note: The table shows the quality hierarchy (ST1/PRS is highest quality, DUS is lowest quality).

Note 1: 2.048 MHz, superframe DS1, and normal frame E1 external

timing references do not support SSM.
Note 2: If the incoming quality level is not recognized by the OME6500,
the quality level is displayed as invalid (INV). To use a timing source with
an INV quality level as a timing reference, the user must override the INV
quality level.
Note 3: See Table 6-7 on page 6-37 for details of the SONET stratum
clock levels.
See Figure 6-9 on page 6-35 for an example of a network showing the
synchronization flow, head-end network element, synchronization boundary,
and synchronization status messaging.
SSM on a port can be disabled by:

• for OC-n/STM-n ports:
— setting the incoming quality override for the OC-n/STM-n port to STU
(SONET) or SSU-A (SDH) and setting the DUS Override parameter
on the OC-n/STM-n port to Enabled.
• for BITSIN/ESI ports:
— setting the incoming quality override for the BITSIN/ESI port to STU
(SONET) or SSU-A (SDH) and supplying a SF framed DS1 signal
(SONET) or Normal framed E1 signal (SDH).
Quality level overrides
A user can specify or override the SSM quality level of an incoming or
outgoing timing source.
The user can specify the incoming quality level if the timing source comes
from equipment that does not support SSM (for example, equipment from
another vendor). To avoid timing loops do not override the quality level of an
incoming timing source if SSM is supported.
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 Site Manager. The user views and provision synchronization parameters
for a OME6500 network element from the Synchronization in the
For detailed procedures, refer to Provisioning and Operating Procedures,

323-1851-310.
Figure 6-9
Synchronization flow detail in an OME6500 network (example)
DUS
Rx Tx
Line
Y X
Tx Rx
(Active)
ST3/
SSU-B
Synchronization
stream
(Active)
Tx Rx ST3/ Tx Rx DUS
X SSU-B Y
Line Line
Y (Active) X
ST3/ Rx Tx ST3/ Rx Tx
SSU-B SSU-B
Synchronization
boundary
Tx Rx ST3/ Tx Rx DUS
X SSU-B Y
Line Line
Synchronization Y X
(Active)
stream Rx Tx Rx Tx
ST3/ ST3/
SSU-B SSU-B
(Active)
DUS
Rx Tx
X Y
Head end
Tx Rx
Legend DUS
= Optical interface

Synchronization protection
synchronization hardware on the cross-connect circuit packs to protect against
synchronization equipment failure. Synchronization hardware protection is
performed by the system automatically.
The OME6500 also supports the protection of the timing reference used for
timing generation and timing distribution.
From Site Manager, the Synchronization Protection application is available

from the Protection menu and displays the protection status of the provisioned
synchronization hierarchies for an network element. The application shows the
source facility name, source state, current quality level, and any active
synchronization protection switches on the sources for each hierarchy.
Synchronization protection switches include the following:
• automatic switch
• manual switch
• forced switch
• lockout
Automatic switch
When a timing reference is selected, the protection algorithm does not select a
different reference unless the active reference has failed or the quality level of
the active reference is below that of a timing reference defined in the hierarchy.
In this case, an automatic switch occurs to a valid timing reference with the
next highest quality level. If two or more timing references have the same
quality level, the system selects the first one as defined in the hierarchy.
If all the timing references in the hierarchy are faulty or the quality levels are
worse than or equal to SMC (SONET) or worse than SSU-B (SDH), the
network element enters into holdover mode for timing generation. A network
element can remain in holdover mode for a minimum of 24 hours after which
the network element switches to freerun mode.
Manual switch
A user initiated manual switch operated on a synchronization source results in
the selection of that source, provided:
• there is no forced switch in operation
• the source's derived quality is equal to the current source's derived quality
• the source's derived quality is not DUS
Forced switch
A user initiated forced switch operated on a synchronization source results in
the selection of that source, provided all sources are not locked out.
If the forced switch results in the selection of a faulty source, the network
element enters holdover operation for timing generation. In the case of timing
distribution, if the forced switch results in selection of a faulty source, the
network element transmits AIS (DS1 and E1 signals) with a SSM of DUS (if
applicable) or squelches the signal (2 MHz) on the ESO port.
The forced switch remains active until the user issues a forced release
command or a lockout request. In the case of a lockout, the forced switch will
be released.
Lockout
A user initiated lockout operation of a synchronization source prevents that
source from being selected. A locked out source remains locked out until the
user issues a lockout release command.
If the user applies a lockout to the last synchronization source, the network
element goes into holdover. A lockout is also released when the user deletes
the locked out reference from the synchronization hierarchy. The user cannot
delete an active reference, so applying a lockout to the last synchronization
source allows the user to delete the last synchronization reference.
For synchronization procedures, refer to Provisioning and Operating

Stratum clocks
Stratum clocks are stable timing reference signals that are graded according to
their accuracy. American National Standards Institute (ANSI) standards have
been developed to define four levels of stratum clocks. The accuracy
requirements of these stratum levels are shown in Table 6-7 on page 6-37.
Table 6-7
ANSI-required standard clock strata
Clock quality Minimum accuracy Minimum holdover stability
Stratum 1 +1.0 x 10-11 not applicable

-8
Stratum 2 +1.6 x 10 1 x 10-10 per day
Stratum 3 +4.6 ppm +0.37 ppm during first 24 hours
SMC +20 ppm +4.6 ppm during first 24 hours
Stratum 4 +32 ppm not required
Synchronization hierarchy
A synchronization hierarchy is a network of stratum clocks that contains one
Stratum 1 clock and several lower stratum clocks, as shown in Figure 6-10 on
page 6-38. The Stratum 1 clock sends a reference signal to several Stratum 2
clocks. These Stratum 2 clocks, in turn, transmit synchronization signals to
other Stratum 2 and Stratum 3 clocks. Similarly, Stratum 3 clocks synchronize

other Stratum 3 and Stratum 4 clocks. It is permissible to skip stratum levels

(for example, a Stratum 1 clock sending a reference signal to several Stratum
3 clocks).
Figure 6-10
Hierarchical network synchronization
Stratum 1
Stratum 1
2A 2B 2C
Stratum 2
3A 3B 3C
3D
Stratum 3
4A 4B 4C
Stratum 4
Legend
= Primary reference
= Secondary reference
Note: Each box represents an office using the building-integrated

timing supply (BITS) concept.
For reliable operation, the synchronization network includes primary and

secondary synchronization facilities to each Stratum 2 and 3 node, and to many
Stratum 4 nodes. In addition, each Stratum 2 and 3 node is equipped with an
internal clock that can bridge short disruptions to the synchronization
reference.
Each network element transmits a synchronization-status message (SSM)

from all OC-n/STM-n and SSM compatible ESO interfaces. When the timing
reference to a network element is disrupted, the network element enters
holdover mode.
A network element in holdover mode transmits timing signals with the quality
level of its internal clock, depending on the quality of the alternate timing
reference. If the alternate timing reference is of a higher quality than the
internal clock of a network element, the network element uses the alternate
timing reference. See Synchronization status messages on page 6-33.
Hierarchy violations
A hierarchy violation occurs when a clock of one stratum level is used to
synchronize a clock of a higher stratum level. A Stratum 3 clock synchronizing
a Stratum 2 clock is one such example. The synchronization network must be
carefully planned so that no hierarchy violations occur.
Timing loops
A timing loop is created when a clock is synchronizing itself, either directly or
through intermediate equipment. A timing loop causes excessive jitter and can
result in traffic loss.
Timing loops can be caused by a hierarchy violation, or by having clocks of

the same stratum level synchronize each other. In a digital network, timing
loops can be caused during the failure of a primary reference source, if the
secondary reference source is configured to receive timing from a derived
transport signal within the network.
A timing loop can also be caused by incorrectly provisioned SSM for some of
the facilities in a linear or ring system. Under normal conditions, if there is a
problem in the system (for example, pulled fiber), the SSM functionality heals
the timing in the system. However, if the SSM is incorrectly provisioned, the
system might not be able to heal itself and might segment part of itself in a
timing loop. See Mixed timing engineering guidelines on page 6-40.
Building-integrated timing supply

The building-integrated timing supply (BITS) concept requires that all digital
equipment in a physical structure must receive timing from the same master
clock. This master clock is the most accurate and stable clock in the structure.
The BITS is driven by a Stratum 3 or better reference signal. This signal can
come from the following sources:
• a timing signal derived from a OC-n/STM-n signal, such as the output of a
ESO source in an OME6500 network element
• an external stratum clock

The BITS distributes a clock signal to all equipment in the same physical
location. The implementation of BITS has the following advantages.
Performance
The designation of a master timing supply for each structure simplifies and
enhances the reliability of the timing distribution. The BITS concept
minimizes the number of synchronization links entering a building, since each
piece of equipment no longer has its own external timing source.
Utilization of resources
A single, high-quality reference timing source can be shared among many
services within the office because BITS provides a large number of signals for
distribution.
Operations
Record keeping for provisioning and maintenance purposes will be easier
when new digital services are introduced because BITS is location-dependent,
not service-dependent.
Mixed timing engineering guidelines

When using mixed timing (see Timing generation on page 6-29), you must
study the timing in the network to determine its susceptibility to timing loops
under fault conditions (see Timing loops on page 6-39). The following sections
provide some engineering guidelines that can be used in the study to help
prevent timing loops.
Note: Determining the synchronization flow at a network element can be

difficult, examine network topology diagrams carefully.
Mixed timing in ring systems
The use of mixed timing in ring systems is dependent on the number of
externally timed (BITSIN/ESI) network elements as follows:
• Mixed timing should not be used if there is only one externally timed
network element. A timing loop may be formed if the BITSIN/ESI signal
fails.
• Mixed timing can be used if there are two externally timed network
elements as follows:
— One externally timed network element must have only the clockwise
OC-n/STM-n interface provisioned as a timing generation reference.
— The other externally timed network element must have only the
counter-clockwise OC-n/STM-n interface provisioned as a timing
generation reference.
A timing loop may be formed if the two externally timed network elements
have both the clockwise and counter-clockwise OC-n/STM-n interfaces
provisioned as timing generation references and the BITSIN/ESI signals
fail at both externally timed network elements.
• Mixed timing can be used if there are three or more externally timed
network elements as follows:
— One externally timed network element must have only the clockwise
OC-n/STM-n interface provisioned as a timing generation reference.
— Another externally timed network element must have only the
counter-clockwise OC-n/STM-n interface provisioned as a timing
generation reference.
— The remaining externally timed network elements can have both the
clockwise and counter-clockwise OC-n/STM-n interfaces provisioned
as timing generation references.
Mixed timing in linear systems
Use of mixed timing in linear systems will not cause timing loops:
• A linear system with only one externally timed network element does not
provide any benefit as under BITSIN/ESI fail conditions the other
OC-n/STM-n interface receives a DUS SSM and a synchronization switch
does not occur.
• Mixed timing can be used if there are two or more externally timed
network elements without any possibility of forming timing loops. To
function correctly, provision one OC-n/STM-n interface as a timing
generation reference at terminal network elements and provision both
OC-n/STM-n interfaces as timing generation references at add/drop
network elements.
Release 1.2 introduces the following connection management enhancements:
• support for DS1 to VT1.5 mapping (SONET only)
• support for DS3 to STS-1/LO_VC3 mapping
• support for EC-1 to VT1.5 and STS-1 mapping (SONET only)
• 1WAYPR, 2WAYPR, and 2WAYDPR connection types for UPSR/SNCP
applications
• support for 1WAY connection types at any rate
• support for international gateway connections (STS-1 to LO_VC3) (see
International gateway on page 6-15)
In the OME6500 architecture, traffic is switched between ports on interface
circuit packs through the cross-connect circuit packs. Two cross-connect
circuit packs provide redundant equipment protection.
All ingress traffic, from a port on a interface circuit pack, maps to appropriate
VT/STS (SONET) or VC (SDH) containers for transmission to the
cross-connect circuit pack. The user configures the cross-connect circuit pack

to switch the VT/STS/VC container to a port on another interface circuit pack.

This basic functionality allows the OME6500 to support diverse connection
and protection configurations.
OME6500 supports the following connection management capabilities:

• full non-blocking cross-connects down to a granularity of a single VT1.5
and STS-1 (SONET) or VC12, VC3 (LO-AU4 mapping), and VC4 (SDH)
level
Note: VT1.5/VC12 cross-connects are only possible if both the
cross-connect circuit pack and the interface circuit pack support
VT1.5/VC12 traffic (see Circuit pack compatibility on page 6-42).
• contiguous concatenated connections for STS-3c, STS-12c/VC4-4c,

STS-24c/VC4-8c, STS-48c/VC4-16c, and STS-192c/VC4-64c rates
• virtual concatenated connections for STS-1-nv/VC3-nv, n = 1 through 21
or STS-3c-nv/VC4-nv, n = 1 through 7 for GE circuit packs
• bandwidth management models:
— bidirectional connection type (2WAY)
— unidirectional connection type (1WAY)
— bidirectional protected connection type (2WAYPR)
— unidirectional protected connection type (1WAYPR)
— dual bidirectional protected connection type (2WAYDPR)
— time slot assignment (TSA)
— time slot interchange (TSI) (not supported on BLSR/MS-SPRing
configurations)
— port to port
Circuit pack compatibility
The cross-connects available depends on the equipped cross-connect circuit
packs and interface circuit packs.
VT1.5/VC12 cross-connects are supported only if both the cross-connect and

interface circuit packs support VT/LO connections.
Note: Reconfiguration to new cross-connect circuit packs and optical

interface circuit packs that support VT1.5/VC12 granularity can be
performed in-service. Detailed procedures for reconfiguring the
cross-connect and optical interface circuit packs are provided in Module
Replacement Procedures, 323-1851-545.

OME5400 currently supports five variants of the cross-connect circuit pack as
follows:
• 80G STS-1/VC-3 XC (NTK557AA): cross-connect circuit pack capable of
STS-1/VC3 connections up to 80G capacity
• 160G+ STS-1/VC-3 XC (NTK557BA): cross-connect circuit pack capable
of STS-1/VC3 connections up to 160G capacity (80G supported in this
release)
• 80G/80G VT1.5/VC-12 XC (80/80) (NTK557NA): cross-connect circuit
pack capable of VT1.5/STS (SONET) or VC12/VC3 (LO-AU4
mapping)/VC4 (SDH) connections up to 80G capacity (VT1.5/VC12
capacity limited to 25G in this release)
• 80G/20G VT1.5/VC-12 XC (80/20) (NTK557PA): cross-connect circuit
pack capable of VT1.5/STS (SONET) or VC12/VC3(LO-AU4
mapping)/VC4 (SDH) connections up to 80G capacity, with the
VT1.5/VC12 capacity limited to 20G
• 20G/20G VT1.5/VC-12 XC (20/20) (NTK557QA): cross-connect circuit
pack capable of VT1.5/STS (SONET) or VC12/VC3(LO-AU4
mapping)/VC4 (SDH) connections up to 20G capacity
Note 1: The system raises a LO BW Near Limit warning alarm if 90% of
the 20G low-order capacity is reached on the NTK557PA and NTK557QA
cross-connects or if 90% of the 25G low-order capacity is reached on the
NTK557NA cross-connect. The system raises a Shelf BW Near Limit
warning alarm if 90% of the total capacity is reached on any cross-connect
circuit pack.
Note 2: STS-1/VC-3 cross-connect circuit packs provide high order (HO)
traffic switching at STS-1 (SONET) and VC-3_HO and VC-4 (SDH)
traffic granularities.
Note 3: VT1.5/VC-12 cross-connect circuit packs provide low order
traffic (LO) switching at VT1.5 (SONET) and VC-12 and VC-3_LO
(SDH) traffic granularities, as well as high order traffic switching at STS-1
(SONET) and VC-3_HO and VC-4 (SDH) traffic granularities.
There are two types of OC-n/STM-n circuit packs as follows:
• STS-1/HO: Interface circuit packs capable of STS-1/VC4 connections.
• VT1.5/LO: Interface circuit packs capable of VT1.5/STS (SONET) or
VC12/VC3(LO-AU4 mapping)/VC4 (SDH) connections
For a full list of interface circuit packs, see Ordering Information,
323-1851-151.

OME6500 connection types

1WAY unidirectional
A unidirectional (1WAY) connection type is an unidirectional path connection
mapped between two interface ports for drop-and-continue cross-connects.
For a 1WAY connection type:

• The From instance can be any channel on an OC-n/STM-n or GE facility
• The To instance can be any channel on an OC-n/STM-n or GE facility.
Figure 6-11 shows the 1WAY connection type for a STS-12c/VC4-4c path. See
Supported unidirectional configurations on page 6-47 for details of supported
unidirectional configurations.
Figure 6-11
1WAY connection type
STS-12c/VC4-4c STS-12c/VC4-4c
Port A
Port B
Interface Cross-connect Interface

circuit packs circuit packs circuit packs
2WAY bidirectional
A bidirectional (2WAY) connection type is a bidirectional path connection
mapped between two interface ports for pass-through, add/drop, or
port-to-port cross-connects.
For a 2WAY connection type the From and To instances can be any channel on
an OC-n/STM-n, GE, DS3, EC-1, DS1, or E1 facility.
Figure 6-12 shows the 2WAY connection type for a STS-1/VC4 path.
Figure 6-12
2WAY connection type
STS-1/VC4 STS-1/VC4
STS-1/VC4 STS-1/VC4
Port A
Port B
STS-1/VC4 STS-1/VC4
Interface Cross-connect Interface

circuit packs circuit packs circuit packs
2WAYPR bidirectional
Defined as a bidirectional path protected connection between two interface
ports. A path selector controls which of the two protecting paths is passed to
the output. In the opposite direction, the traffic path is bridged to both
protecting paths.
For a 2WAYPR connection type:

• The From and Switch mate instances can be any channel on an unprotected
OC-n/STM-n or GE facility.
• The To instance can be any channel on an OC-n/STM-n, GE, DS3, EC-1,
DS1, or E1 facility.
Figure 6-13 illustrates the 2WAYPR connection type for a STS-1/VC-4 path.
Figure 6-13
2WAYPR connection type
STS-1/VC4
STS-1/VC4
Port B
STS-1/VC4 STS-1/VC4
STS-1/VC4
Port A
STS-1/VC4 STS-1/VC4
STS-1/VC4
Cross-connect
Port C
Interface
circuit packs circuit packs
STS-1/VC4
Interface
circuit packs
1WAYPR unidirectional
Defined as a unidirectional path protected connection between two interface
ports. A path selector controls which of the two protecting paths is passed to
the output.
For a 1WAYPR connection type:

OC-n/STM-n or GE facility.
• The To instance can be any channel on an OC-n/STM-n or GE facility.
Figure 6-14 illustrates the 1WAYPR connection type for a STS/VC-4 paths.
See Supported unidirectional configurations on page 6-47 for details of
supported unidirectional configurations.

Figure 6-14
1WAYPR connection type
STS-1/VC4
STS-1/VC4
Port B
STS-1/VC4
STS-1/VC4 STS-1/VC4
Port A
STS-1/VC4
STS-1/VC4 STS-1/VC4
Port C
Cross-connect Interface
circuit packs circuit packs
STS-1/VC4
Interface
circuit packs
Dual 2WAYPR bidirectional

Defined as a dual bidirectional path protected connection between four
interface ports. The connection type is used for UPSR/SNCP ring
interconnection and is the equivalent to four 1WAYPR connections.
For a 2WAYDPR connection type:

OC-n/STM-n facility.
• The To and Destination Mate instances can be any channel on an
unprotected OC-n/STM-n facility.
Figure 6-15 illustrates the Dual 2WAYPR connection type for a STS-1/VC-4
path.
Figure 6-15
Dual 2WAYPR connection type
STS-1/VC4 STS-1/VC4
STS-1/VC4 STS-1/VC4
Port C
Port A
STS-1/VC4 STS-1/VC4
UPSR/ UPSR/
SNCP SNCP
A STS-1/VC4 STS-1/VC4 B
STS-1/VC4 STS-1/VC4
Port D
Port B
STS-1/VC4 STS-1/VC4
Interface Interface
circuit packs Cross-connect circuit packs
circuit packs
Supported unidirectional configurations

Unidirectional cross-connects (1WAY and 1WAYPR) are only supported for
the following applications:
• GE drop-and-continue applications on UPSR/SNCP, BLSR/SNCP, and
1+1/MSP linear configurations at STS-1, STS-3c, STS-12c, STS-24c,
STS-3c-nv (SONET) and VC4-nv (SDH) connection rates only. The
endpoints can be either OCn/STMn or GE facilities.
• dual feed connections on OC-48/STM-16 or OC-192/STM-64
BLSR/MS-SPRing configurations at the STS-12c/VC4-4c connection rate
only. Feeds on/off the BLSR/MS-SPRing configuration must be
OC-12/STM-4, OC-48/STM-16, or OC-192/STM-64 facilities in either
unprotected or 1+1/MSP linear configurations.
• dual feed connections on OC-12/STM-4, OC-48/STM-16, or
OC-192/STM-64 unprotected configurations at the STS-12c/VC4-4c
connection rate only. Feeds on/off the unprotected configuration must be
OC-48/STM-16 facilities in either unprotected or 1+1/MSP linear
configurations.
For drop-and-continue (broadcast) applications:
• For the VT1.5/VC12 cross-connect circuit packs (NTK557NA/PA/QA),
there is no limit for drops and continues per connection. In Release 1.2,
Nortel Networks has tested system configurations with up to 20 drops and
continues (for example, 1 drop and 19 continues).
• For the STS-1/VC3 cross-connect circuit packs (NTK557AA/BA), a
maximum of 4 drops and continues per connection is allowed. Each of the
drop-and-continue endpoints, including protected endpoints, must be on
different interface circuit packs (slots) on the OME6500. These limitations
only apply to the STS-1/VC3 cross-connect circuit packs and do not apply
to the VT1.5/VC12 cross-connect circuit packs with STS-1/VC3 (or higher
rates) connections.
Note: If the drops or continues are protected (either 1+1/MSP linear,
BLSR/MS-SPRing, or equipment protection), the drop or continue counts
as two towards the broadcast limit.
Payload interconnection
OME6500 supports the following payload interconnections:
• Non-concatenated at the VT1.5/STS (SONET) or VC12/VC3(LO-AU4
mapping)/VC4 (SDH) level
• Contiguous concatenated at the STS-3c/STS-12c/STS-24c/
STS-48c/STS-192c (SONET) or VC4-4c/VC4-8c/VC4-16c/VC4-64c
(SDH) levels
Table 6-8 provides a summary of the service mappings and interconnection
type currently supported.

All services (SONET/SDH, GE, DS1, DS3, and E1) are mapped to the
VT/STS/VC appropriate containers. The OME6500 uses Generic Framing
Procedure (GFP) as its standards based SONET/SDH mapping for
point-to-point GE connectivity services.
Table 6-8
OME6500 service mapping
Service Mapping Interconnection type

OC-3/ • STS-1 or VC4 • non-concatenated at STS-1 or VC4 level
STM-1 • STS-3c • contiguous concatenation at STS-3c
STM-4 • STS-3c, STS-12c/VC4-4c • contiguous concatenation at STS-3c,
STS-12c/VC4-4c level
STM-16 • STS-3c, STS-12c/VC4-4c, • contiguous concatenation at STS-3c,
STS-24c/VC4-8c, STS-12c/VC4-4c, STS-24c/VC4-8c,
STS-48c/VC4-16c STS-48c/VC4-16c levels
STM-64 • STS-3c, STS-12c/VC4-4c, • contiguous concatenation at STS-3c,
STS-24c/VC4-8c, STS-12c/VC4-4c, STS-24c/VC4-8c,
STS-48c/VC4-16c, STS-48c/VC4-16c, STS-192c/VC4-64c levels
STS-192c/VC4-64c
GE • GFP-F to STS-1 or VC4, STS-3c, • non-concatenated at STS-1 or VC4 level
STS-12c/VC4-4c, STS-24c/VC4-8c • contiguous concatenation at STS-3c,
• GFP-F to STS-1nv/VC3-nv (n = 1 to STS-12c/VC4-4c, STS-24c/VC4-8c levels
21), STS-3c-nv/VC4-nv (n = 1 to 7) • virtual concatenation at STS-1nv/VC3-nv (n = 1 to
21), STS-3c-nv/VC4-nv (n = 1 to 7)
E1 • VC12 • non-concatenated at VC12 level
DS1 • STS-1 • non-concatenated at VT1.5 level
DS3 • STS-1/LO_VC3 • non-concatenated at STS-1/LO_VC3 level
EC-1 • VT1.5 • non-concatenated at VT1.5 level
• STS-1 • non-concatenated at STS-1 level
VC4 mapped VC3s (applicable to SDH only)

OME6500 currently supports the following VC3 (LO-AU4 mapping)
mappings:
• VC4 mapped VC3 connection, connected at the VC4 level
• VC4 mapped VC3 where individual VC3s are connected directly to
another VC3 at the VC3 level
• VC4 mapped VC3 where the VC3s of one VC4 are connected to VC3s in
different VC4s at the VC3 level
Note: VC3 (LO-AU4 mapping) connections require the VT1.5/VC-12
cross-connect circuit packs and the VT1.5/LO interface circuit packs.
Figure 6-16 shows a visual representation of these different mappings.

Figure 6-16
VC3 payload mappings
VC4 VC4
VC3 VC3 VC3 VC3 VC3 VC3
VC4 VC4
VC3 VC3 VC3 VC3 VC3 VC3
VC4 VC4
VC3
VC3 VC3 VC3
VC4
VC3
VC4
VC3
DS1 and E1 mapping

The DS1 signals are mapped to VT1.5 containers. The user has the option to
provision individual VT1.5 cross-connects for DS1 facilities or bulk provision
VT1.5 cross-connects for ports 1 to 28, ports 29 to 56, or ports 57 to 84.
The E1 signals are mapped to VC12 containers. The user has the option to
provision individual VC12 cross-connects for E1 facilities or bulk provision
VC12 cross-connects for ports 1 to 21, ports 22 to 42, or ports 43 to 63.
Generic Framing Procedure
GFP is an ITU standard (G.7041) which describes a flexible mapping
technique for transparent transport of multiple protocols in SONET and SDH.
GFP provides an efficient mechanism for Gigabit Ethernet (GE) and other data
services like Fibre Channel and FICON to be transported over an
SONET/SDH network via efficiently mapping varying client signals into
STS/VC containers.
GFP defines two different implementations, Transparent GFP (GFP-T) and

Framed-mapped GFP (GFP-F). This release does not support GFP-T.

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 (operational
measurements (OM) and performance monitoring (PM)).
In GFP-F, idle frames are inserted as necessary to fill the transport payload.
Multiple GFP-F frames can be aggregated in a single SONET/SDH payload.
Table 6-9 lists the different available transport structures available for the
4xGE EPL circuit pack and the associated throughput allocation for GE.
Table 6-9
Transport structure for GE and throughput
SONET/SDH Number of STS-1/VC3, WAN bandwidth

transport structure STS-3c/VC4 groups allocated
STS-1nv/VC3-nv n n x 50 Mbit/s
STS-3c/VC4 1 150 Mbit/s
STS-3c-nv/VC4-nv n n x 150 Mbit/s
STS-12c/VC4-4c 4 600 Mbit/s
STS-24c/VC4-8c 8 1200 Mbit/s
Note: GE, DS1, DS3, EC-1, and E1 services are mapped to SONET/SDH
containers and assigned as SONET/SDH level connections to
OC-n/STM-n interface circuit packs.
Time slot assignment (TSA)

The OME6500 supports:
• unconstrained time slot assignment to any STS-1/VC4/VC3 container at
all STS-1/VC4 interconnection levels.
• partial time slot assignment to any low-order (VT1.5/VC12) container at
VT1.5/VC12 interconnection levels.
Note: The level of TSA supported depends on the cross-connect circuit
packs and the interface circuit packs.
TSA is performed as part of the connection creation process.
Time slot interchange (TSI)

The OME6500 provides the ability to change the time slot assignment of a
VT/STS/VC container to another available time slot at any point in the
add/drop or passthrough node in an OME6500 1+1/MSP linear, UPSR/SNCP,
or unprotected network. TSI is not available on BLSR/MS-SPRing
configurations.
Connection management application

OME6500 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 Table 6-11 provides an overview of the traffic protection
schemes currently supported. on page 6-57 for more details.
The Nodal Cross-Connect application in the Configuration menu of Site

Manager allows the user to view, add, edit, and delete nodal cross-connects.
SDH payload instance numbering
In Site Manager, SDH payload instances are displayed using J, K, L, and M
format where:
• J is the AU-4 number (range depends on circuit pack, for example range is
1 to 16 for OC-48/STM-16 circuit pack)
• 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)
For example, a format of J-K = 3-2, L = 6, M=2 identifies:
• AU-4 number 3
• TUG-3 number 2
• TUG-2 number 6
• TU-12 payload number 2
Connection blocking
The systems blocks any invalid cross-connects as follows:
• STS-1/VC4 cross-connects if low-order cross-connects
(VT1.5/VC12/VC3) already exist on the endpoint
• low-order cross-connects (VT1.5/VC12/VC3) if the associated
STS-1/VC4 is already connected
For detailed procedures and associated rules, refer to Provisioning and
Operating Procedures, 323-1851-310.
Equipment protection detects an equipment failure that causes a loss of
service, and restores the failed services from a redundant piece of equipment.
Equipment protection manages core functions and services in a network
element that are normally traffic affecting.

This section provides a definition of OME6500 equipment protection,

including information about the protection scheme and mode for the following
equipment:
• cross-connect circuit packs
• 63xE1 circuit packs
• 24xDS3/EC-1 circuit packs
• 84xDS1 termination module (TM) circuit packs in a DS1 service module
(DSM)
Performance degradation and/or equipment failure triggers equipment
protection. The protection switch can be the result of the following:
• hardware or software failure on the circuit pack
• removal of the circuit pack from the network element
• manual command (not applicable to cross-connect circuit packs)
The OME6500 supports the following equipment protection schemes and
modes:
• 1+1 non-revertive for the cross-connect circuit packs
• 1:N revertive for the 63xE1 or 24xDS3/EC-1 circuit packs (2 banks of 1:4
protection)
• 1+1 non-revertive for the 84xDS1 TM circuit packs
In a revertive mode, when the condition that caused the equipment protection
switch clears, the working unit becomes active after a wait-to-restore (WTR)
period.
In a non-revertive mode, when the condition that caused the equipment

protection switch clears, the working unit does not become active
automatically.
Cross-connect circuit pack protection

OME6500 supports equipment protection for the cross-connect circuit pack in
a 1+1 scheme and non-revertive mode. The cross-connect circuit pack
provides core functions such as port-to-port interconnection and shelf
synchronization.
Equipment switching for the cross-connect circuit packs is automatic and can
result from hardware or software failure on the circuit pack, removal of the
circuit pack from the network element, putting the circuit pack out-of-service
(OOS), or a warm/cold restart. Manual switching of the cross-connect circuit
packs is not supported.
63xE1 and 24xDS3/EC-1 circuit pack protection

OME6500 supports equipment protection for the 63xE1 or 24xDS3/EC-1
circuit packs in a 1:N scheme and revertive mode. The 1:N protection is
arranged in two banks of 1:4 protection where up to four 63xE1 or
24xDS3/EC-1 working circuit packs are protected by a single 63xE1 or
24xDS3/EC-1protection circuit pack.
In the 1:N protection, the protection switch moves all of the traffic on a
working circuit pack to the protection circuit pack, enabling the faulty working
circuit pack to be replaced without affecting traffic.
The two banks of 1:4 protection are provided by:

• 63xE1 or 24xDS3/EC-1 working circuit packs in slots 1 to 4 and a
protection circuit pack in slot 13
• 63xE1 or 24xDS3/EC-1 working circuit packs in slots 9 to 12 and a
protection circuit pack in slot 14
For each 63xE1 working circuit pack in the 1:N protection configuration, you
must install an I/O protection module in the appropriate slot in the associated
I/O panel. For example, if slots 1 and 2 contain 63xE1 working circuit packs,
you must install I/O protection modules in slots 1 and 2 of the bank 1 (left) I/O
panel.
Note: I/O protection modules are not required for 1:N protection of
24xDS3/EC-1 circuit packs.
Provisioning 1:N equipment configurations

1:N equipment protection requires the following items to be provisioned.
application in the Protection menu of Site Manager. When the user selects the
1:N protection scheme for a working circuit pack:
• if auto-equipping is enabled, the protection circuit pack automatically
provisions (if not already provisioned). If a different circuit pack is
provisioned in the protection slot, the systems rejects the 1:N provisioning.
• if auto-equipping is disabled, the system rejects the 1:N provisioning if a
protection circuit pack is not provisioned
Note 1: If auto-equipping is disabled, you must provision the protection
circuit pack before selecting the 1:N protection on the working circuit
pack.
Note 2: For the 63xE1 circuit packs, if the protection circuit pack is
provisioned but the correct I/O protection modules are not present for the
associated working circuit packs, the system raises Protection Sub-module
Missing or Protection Sub-module Mismatch alarms.

Note 3: The default protection mode is unprotected. If required, 1:N

protection must be provisioned by the user.
The user also provisions the wait-to-restore time as part of the protection group
provisioning. The default time is 5 minutes. OME6500 allows the user to
provision an infinite wait-to-restore period for the 1:N protection group. This
feature allows the user to provision the 1:N protection group to autonomously
switch in a non-revertive mode.
1:N protection switch criteria

1:N protection switch requests can occur automatically by the system or by
user initiated actions.
Automatic switch
An automatic switch occurs for working circuit pack removal or failure
provided no higher priority switch exists and at least one of the following
conditions exist:
• at least one facility on the working circuit pack is in-service and has an
associated cross-connect
• the working circuit pack and the protection circuit pack are both in-service
The user has the option of assigning a priority (low or high) to the working
circuit pack during provisioning. Circuit packs with a high priority take
precedence over low priority circuit packs. The 1:N protection is revertive,
when the fault clears and the wait-to-restore time has expired, traffic switches
back to the working circuit pack. Traffic also switches back to the working
circuit pack if the protection circuit pack fails or is removed.
User-initiated switches
• Manual switch
This command switches the E1 or DS3/EC-1 signals from the working
circuit pack to the protection circuit pack. The manual switch has the
lowest priority and occurs only if a higher priority switch is not active (no
active automatic switch, forced switch, lockout, or protection circuit pack
failed). The manual switch remains active until released by the user or a
higher priority switch occurs. A manual switch can only be applied to
working circuit packs and only one manual switch can be present.
• Forced switch
This command switches the E1 or DS3/EC-1 signals from the working
circuit pack to the protection circuit pack regardless of the effect on traffic.
The forced switch occurs only if the protection circuit pack is available and
no active lockout commands exist. The forced switch remains active until
released by the user or a higher priority switch occurs. A forced switch can
only be applied to working circuit packs and only one forced switch can be
present.
• Lockout
A lockout removes the circuit pack from the protection system. If you
apply a lockout to a working circuit pack, that circuit pack is not protected.
If you apply a lockout to the protection circuit pack, none of the working
circuit packs are protected. The lockout command has the highest priority.
The lockout remains active until released by the user. A lockout can be
applied to any working or protection circuit pack (you can apply multiple
lockouts).
Table 6-10 shows the hierarchy of protection commands.

Table 6-10
1:N equipment protection hierarchy
Switch request Priority Applicable to Working/Protection

Lockout 1 (highest) Working or protection circuit packs
Automatic (Protection) 2 Protection circuit pack (failed or
out-of-service)
Forced 3 Working circuit packs
Automatic (High) 4 Working circuit packs (assigned high
priority)
Automatic (Low) 5 Working circuit packs (assigned low
priority)
Manual 6 Working circuit packs
Wait-to-restore 7 (lowest) Working circuit packs
1:N protection exerciser

The 1:N protection exerciser tests the protection paths to ensure protection can
function correctly. If protection is not functioning correctly, the protection
exerciser raises a Protection Exerciser Fail alarm.
The 1:N protection exerciser tests certain signal paths and some components
on the working and protection circuit packs by bridging traffic from each
working circuit pack to the protection circuit pack, and verifying traffic. The
protection exerciser does not affect traffic.
Any or all working circuit packs can be ‘allowed’ or ‘inhibited’ from the
protection exerciser. An allowed circuit pack will be exercised during the next
exercise run. An inhibited circuit pack will not be exercised during the next
exercise run.

The protection exerciser can be performed on a single working circuit pack or

all working circuit packs. The exerciser can run automatically on a schedule
set in advance, or can be initiated manually.
CAUTION
E1 and DS3/EC-1 protection exerciser schedule frequency
Do not schedule the E1 or DS3/EC-1 protection exerciser to run
for extended periods at a frequency below one hour (this will
cause excessive wear on the protection relays). If you must
schedule the E1 or DS3/EC-1 protection exerciser to run at
frequencies below one hour (for example, during debugging
activities), ensure that this is for short periods (no more than 2
or 3 days).
The exerciser can be set to run autonomously for an allowed circuit pack. This
means that the protection exerciser also runs for the working circuit pack when
it detects a signal fail change.
The 1:N protection exerciser does not run if there is a protection switch active,
except on the circuit pack that is currently switched.
84xDS1 TM circuit pack protection
For information on 1+1 equipment protection for the DSM 84xDS1 TM circuit
packs, refer to DS1 service module support on page 6-6.
Traffic protection
Traffic protection is a mechanism to enhance the dependability of a transport
service. The OME6500 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.
OME6500 supports line level traffic protection and restoration schemes. This
implies that all payloads provisioned on a port of the interface circuit pack are
switched together. The following line level traffic protection schemes are
currently available:
• 1+1/multiplex section protection (MSP) linear
• 2-Fiber bidirectional line-switched ring (BLSR)/multiplex section shared
protection ring (MS-SPRing)
• unprotected
Note 1: Traffic switches for the 1+1/MSP linear and 2-Fiber
BLSR/MS-SPRing schemes are port based and not circuit pack based. For
example, if a problem is detected on a working port of circuit of a
multi-port circuit pack, only traffic on the faulty port is switched, not
traffic on all the ports on the circuit pack.
Note 2: The working and protection ports on an adjacent pair of multi-port
traffic circuit packs must be horizontally aligned. For example, on an
8xOC-3/12/STM-1/4 SFP circuit pack where the working port is on slot 1
port 3, the protection port is on slot 2 port 3 (same port number). This rule
applies for all multi-port circuit packs operating in protection pairs
irrespective of protection scheme being utilized (1+1/MSP linear or
BLSR/MS-SPRing).
OME6500 also supports UPSR/SNCP path level protection (see UPSR/SNCP
traffic protection on page 6-3).
The traffic protection architecture consists of one working channel and one
protection channel, carried on separate fibers/cables and separate equipment.
The system provides traffic protection by switching traffic between the two
channels either automatically when a degradation or failure is detected or by
user initiated actions. Figure 6-17 provides an overview of the line traffic
protection architecture on the OME6500.
Figure 6-17
OME6500 line traffic protection architecture
Cross-connect
circuit packs
Service
interface ports Port A Port B
Optical interface
circuit packs
Pair of adajcent
service interface ports
used to provide traffic
protection
Working Protection
Table 6-11 provides an overview of the traffic protection schemes currently

supported.

Table 6-11
OME6500 traffic protection summary
Protection Interface Maximum

scheme circuit packs configurations per
network element
1+1/MSP linear 1xOC-192/STM-64 circuit pack 2
2xOC-48/STM-16 circuit pack 12
8xOC-3/12/STM-1/4 circuit pack 48
UPSR/SNCP 1xOC-192/STM-64 circuit pack 80/0 and 160/0 XCs
(see Note 2) 2xOC-48/STM-16 circuit pack • 512 STS-1/VC3
8xOC-3/12/STM-1/4 circuit pack • 170 STS-3C/VC4
4xGE EPL circuit pack 80/20 XC
• 512 STS-1/VC3
• 170 STS-3C/VC4
• 3584 VT1.5
• 3072 VC12
20/20 XC
• 128 STS-1/VC3
• 42 STS-3C/VC4
• 3584 VT1.5
• 3072 VC12
80/80 XC
• 128 STS-1/VC3
• 42 STS-3C/VC4
• 4480 VT1.5
• 3840 VC12
2-Fiber 1xOC-192/STM-64 circuit pack 4
BLSR/MS-SPRing 2xOC-48/STM-16 circuit pack
Unprotected 1xOC-192/STM-64 circuit pack 4
2xOC-48/STM-16 circuit pack 24
8xOC-3/12/STM-1/4 circuit pack 96
4xGE EPL circuit pack 48
Note 1: The default traffic protection mode on the OME6500 network element is
unprotected.
Note 2: The maximum number of UPSR/SNCP configurations depends on the
number of cross-connects destinations. Figures quoted are for bidirectional
connections using 2WAYPR connections (three destinations per connection).
The OME6500 supports any mix of traffic protection schemes listed in Table
6-11 on a single network element so long as the maximum per network element
value is not exceeded. Refer to Ordering Information, 323-1851-151 for more
information.
Traffic Protection application

The user performs provisioning of traffic protection by selecting the
Provisioning application in the Protection menu of Site Manager.
For more information on provisioning traffic protection, see Provisioning and

1+1/MSP linear traffic protection

1+1/MSP linear traffic protection uses a pair of interface ports in adjacent slots
to provide line traffic protection. 1+1/MSP linear traffic protection uses the
1+1/MSP protocol to handshake between adjacent network elements to
determine when a protection switch should occur. All of the payloads within
the line are protected together.
Provisioning MSP linear protected connections

1+1/MSP linear traffic protection requires the following items to be
provisioned.
1+1/MSP Linear protection scheme for an interface port located in an odd slot
of the OME6500 shelf. The system assigns the adjacent port on the interface
circuit pack located in the even slot to the immediate right of the identified slot
as the mate port to provide the 1+1/MSP linear protection.
The user also provisions the switch mode as either bidirectional (both
transmit and receive directions switch together) or unidirectional (only the
transmit or receive directions switched based on the fault or user initiated
action).
application in the Configuration menu of Site Manager. The user selects a
2WAY connection type at the end points and at any pass-through nodes if
applicable.
Note: The OME6500 supports nodal provisioning. When provisioning an

end-to-end circuit, you must provision the traffic protection and
cross-connects at the connection end points and at any pass-through nodes
that make up the end-to-end circuit.

For detailed procedures for 1+1/MSP linear protection and connection

provisioning, refer to Provisioning and Operating Procedures, 323-1851-310.
1+1/MSP linear protection switch criteria

1+1/MSP linear protection switch request can occur automatically by the
Note: User-initiated 1+1/MSP linear switching commands are signaled
through the 1+1/MSP channels (K1 and K2 bytes).
Automatic switch
An automatic switch occurs automatically after a signal fail, signal degrade, or
equipment unavailability (circuit pack removal, reset, failure) condition
associated with an interface port. An automatic switch occurs unless a higher
priority switch request is active. This release supports non-revertive switching.
When an automatic switch occurs, traffic does not revert to the previous active
interface port. The automatic switch is a non-standing request as once the
switch has occurred or is refused, the request is lowered.
• Manual switch
This command switches the working line to the protection line or the
protection line to the working line. The manual switch has the lowest
priority and occurs only if the requested line is available (no active
automatic switch or forced switch). The manual switch is a non-standing
request as once the switch has occurred or is refused, the request is
lowered.
• Forced switch
This command switches the working line to the protection line or the
protection line to the working line. The forced switch occurs only if the
protection line is available and no active lockout commands exist. The
forced switch is a standing request as it remains active until it is released
by the user.
• Lockout
This command prevents the working line from switching to the protection
line. The lockout command has the highest priority. The lockout is a
standing request as it remains active until it is released by the user. A
lockout can only be performed on the protection circuit pack (even circuit
pack slot)
Table 6-12
1+1/MSP linear protection - command hierarchy

Lockout 1 (highest) Protection channel
Auto (Signal Fail) 2 Protection channel
Forced 3 Working or Protection channel
Auto (Signal Fail) 4 Working channel
Auto (Signal Degrade) 5 Working or Protection channel
Manual 6 (lowest) Working or Protection channel

323-1851-310.
2-Fiber BLSR/MS-SPRing traffic protection

A 2-Fiber bidirectional line-switched ring (BLSR)/multiplex section shared
protection ring (MS-SPRing) is a ring network of nodes interconnected by a
pair of optical fibers. BLSR/MS-SPRing traffic protection provides 100%
restoration of restorable traffic for single failures by reserving 50% of the
ring’s capacity for protection. As a result, a 2-Fiber OC-48/STM-16 or
OC-192/STM-64 ring effectively has a span capacity of STS-24/STM-8 and
STS-96/STM-32 respectively.
For a 2-Fiber BLSR/MS-SPRing operating at the OC-48/STM-16 level, time

slot numbers 1 through 24 (SONET) or 1 through 8 (SDH) at the multiplex
input are reserved for working channels. Time slot number ‘X’ of the first fiber
is protected using time slot number ‘X+24’ (SONET) or ‘X+8’ (SDH) of the
second fiber in the opposite direction, where X is an integer between 1 and 24
(SONET) or between 1 and 8 (SDH).
For a 2-Fiber BLSR/MS-SPRing operating at the OC-192/STM-64 level, time

slot numbers 1 through 96 (SONET) or 1 through 32 (SDH) at the multiplex
input are reserved for working channels. Time slot number ‘X’ of the first fiber
is protected using time slot number ‘X+96’ (SONET) or ‘X+32’ (SDH) of the
second fiber in the opposite direction, where X is an integer between 1 and 96
(SONET) or between 1 and 32 (SDH).
In a BLSR/MS-SPRing, switching nodes communicate to each other through

K-bytes. All of the STS-1s/VC-4s within the line are protected together (see
STS/VC BLSR/MS-SPRing with VT/LO VC assignment on page 6-65).
Figure 6-18 shows an overview of the 2-Fiber BLSR/MS-SPRing traffic
protection.

Figure 6-18
2-Fiber BLSR/MS-SPRing traffic protection overview
Working time slots

STS #1 to 24 for OC-48/
VC4 #1 to 8 for STM-16
VC4 #1to 32 for STM-64
Port C Port B
Protection time slots

Port A
STS #97 to 192 for OC-192/
Client Equipment
Legend
= Optical fiber
= working time slots
= protection time slots
For information about 2-Fiber BLSR/MS-SPRing traffic protection, including

how the ring switches during fault conditions, see Provisioning and Operating
Provisioning 2-Fiber BLSR/MS-SPRing traffic protection

A 2-Fiber BLSR/MS-SPRing requires the following items to be provisioned.
BLSR/MS-SPRing protection scheme for a port on an interface circuit pack
located in an odd slot of the OME6500 shelf. The system assigns the adjacent
port on the interface circuit pack located in the even slot to the immediate right
of the identified slot as the mate port to provide the BLSR/MS-SPRing
protection.
The user also provisions the wait-to-restore time as part of the protection group
provisioning. The default time is 5 minutes. OME6500 allows the user to
provision an infinite wait-to-restore period in BLSR/MS-SPRing protected
interfaces. This feature allows the user to provision BLSRs/MS-SPRings to
autonomously switch in a non-revertive mode.
Ring map provisioning
The user performs ring map provisioning from the BLSR/MS-SPRing
Configuration application in the Configuration menu of Site Manager.
The ring map contains an ordered list of up to 16 APS IDs, ranging in value
from 0 to 15 (APS ID0, APS ID1, APS ID2, …APS ID15).
Note: Although ordered, the list does not have to be in sequential order of
0 to 15.
For more information on ring map provisioning, refer to Provisioning and

application in the Configuration menu of Site Manager. The user provisions
a 2WAY connection type at the end points and any pass through nodes if
applicable.
Note: For dual feed applications on BLSR/MS-SPRing configurations,

use the 1WAY connection type to create drop-and-continue connections
(see 1WAY unidirectional on page 6-44).
For BLSR/MS-SPRing connections only, the BLSR/MS-SPRing end points

must be identified. The BLSR/MS-SPRing end points are the APS IDs of the
connection end points.


end-to-end circuit, you must provision the traffic protection and
cross-connects at the end points and at any pass through nodes that make
up the end-to-end circuit.
For detailed procedures for BLSR/MS-SPRing protection, ring map, and

connection provisioning, refer to Provisioning and Operating Procedures,
323-1851-310.
BLSR/MS-SPRing protection switch criteria

BLSR/MS-SPRing protection switch requests can occur automatically by the
Note 1: All user-initiated BLSR/MS-SPRing switching commands are
signaled on the APS channels (K1 and K2 bytes).
Note 2: The signal fail protection and lockout of protection - span
switching commands use the same code in the K-bytes. If an automatic
switch due to a signal fail protection condition is active, the protection
status application in Site Manager displays ‘lockout of protection - remote’
(this is the expected behavior).
Automatic switch
An automatic switch occurs automatically after a signal fail, signal degrade, or
equipment unavailability (circuit pack removal, reset, failure) condition
associated with a service interface port. An automatic switch occurs unless a
higher priority switch request is active. This release supports revertive
switching. When the fault clears and the wait-to-restore time has expired,
traffic switches back to the pre-assigned working time slot.
• Manual switch
This command performs the ring switch from the working to the protection
channels for the span between the node at which the command was
initiated and the adjacent node to which the command was destined. This
switch occurs if the protection channels to be used are not satisfying an
equal or higher priority request (including failure of the protection
channels). A manual switch cannot segment the ring.
• Forced switch
This command performs the ring switch from the working to the protection
channels for the span between the node at which the command is initiated
and the adjacent node to which the command is destined. This switch
occurs regardless of the state of the protection channels, unless the
protection channels are satisfying a higher priority request. A forced
switch can segment the ring.
• Lockout of Working
This command prevents the working time slots from switching to the
protection time slots. The lockout command has the highest priority. The
lockout remains active until cleared by the user.
A lockout of working channels on a span prevents the span from switching.
• Lockout of Protection
This command prevents the protection time slots from being used by other
nodes in the ring. The lockout command has the highest priority. The
lockout remains active until cleared by the user.
A lockout of protection channels on a span prevents the use of the span for
any protection activity, and prevents (and pre-empts) ring switches
anywhere in the ring.

Table 6-13
BLSR/MS-SPRing protection - command hierarchy

Lockout 1 (highest) Working or Protection channel
Forced 2 Working channel
Auto (Signal Fail) 3 Working channel
Auto (Signal Degrade) 4 Working channel
Manual 5 Working channel
Exerciser 6 (lowest) Working channel
For detailed procedures for BLSR/MS-SPRing protection switching, refer to

STS/VC BLSR/MS-SPRing with VT/LO VC assignment

This release supports VT/low order (LO) VC assignment on
BLSRs/MS-SPRings. Payload connectivity in the BLSR/MS-SPRing
configurations is at the STS-1/VC4 level where the STS-1/VC4 managed
connection can contain VT/LO VC payloads. Individual VT/LO VC payload
overheads are not monitored.

In VT/LO VC assigned BLSRs/MS-SPRings, users must provision

STSn/VC4-nc connections at pass-through nodes. This gives a number of
distinct advantages to the user:
• less connections for the user to manage
• less, therefore quicker, connection retrievals on pass-through nodes
• interoperability support with STSn/VC4-nc based products (for example,
Optical Cross Connect HDX/HDXc and Optical Cross Connect DX)
VT/LO VC assigned end-to-end connections must have the following
characteristics:
• for any given end-to-end VT/LO VC connection, add and drop nodes must
be provisioned with VT/LO VC connections and pass-through nodes must
be provisioned with STSn/VC4-nc connections
• if one VT/LO VC connection within a STSn/VC4-nc is provisioned as
VT/LO VC assigned, all of the VTs/LO VCs within that STSn/VC4-nc
must be VT/LO VC assigned
• all VT/LO VC assigned end-to-end connections with an STSn/VC4-nc
channel must terminate (add/drop) at the same node
Traffic protection exerciser

The traffic protection exerciser allows you to verify the protection
functionality without affecting the traffic. By running the protection exerciser,
you can detect silent protection-related failures before the failures become
service-affecting.
The traffic protection exerciser is a routine that tests the integrity of the
protection switching bytes (K-bytes) communication between an optical
interface pair of a 1+1/MSP linear or BLSR/MS-SPRing configuration. If the
two ends fail to exchange the K-bytes, the test fails and alarms are raised.
The exerciser can run automatically on a schedule set in advance, or can be

initiated manually.
The exerciser is the lowest priority user command and does not run if:
• a higher priority feature or command is in effect
• alarms are present on the interface circuit packs
The exerciser runs only on a pair of interface circuit packs that meet all the
following conditions:
• The interface circuit packs must be in a 1+1/MSP linear or
BLSR/MS-SPRing configuration. If the interface circuit packs are in a
BLSR/MS-SPRing configuration, they must also have a valid
BLSR/MS-SPRing configuration and no active protection switch. If the
interface circuit packs are in a 1+1/MSP linear configuration, there must
not be an active protection switch and the working facilities must be active.
• in-service
• in bidirectional protection switching mode, if in a 1+1/MSP linear
configuration
Unprotected connections
Unprotected connections are 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 mode in OME6500.
Provisioning unprotected connections

As unprotected is the default traffic protection mode, unless the user has
already provisioned the interface circuit pack for another protection scheme,
the user can just provision cross-connects.
application in the Configuration menu of Site Manager. The user selects a
2WAY connection type at the end points and at any pass-through nodes if
applicable.

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, see Provisioning and Operating Procedures,

323-1851-310.

OME6500 OAM comms

The OME6500 OAM interfaces and comms provides the capabilities for local
and remote management of the OME6500 network element and for
interworking with other network elements to provide a cohesive network
management solution. The OME6500 OAM interfaces provided are as
follows:
• COLAN (COLAN-A or COLAN-X ports) for interface to a data
communications network (DCN)
• ILAN (ILAN-IN and ILAN-OUT ports) for intershelf DCN
• RS-232 port on the access panel and shelf processor and a 10/100Base-T
port on the shelf processor for craft user interface
• section/RS and line/MS DCC for OAM&P access to remote network
elements
Figure 6-19 provides an overview of the OME6500 OAM communications
architecture.
Figure 6-19
OME6500 OAM communications architecture
Local Craft Access
Used for
RS232 RS232 temporary access
10/100B DTE DCE
Craft Modem Craft
COLAN A
10/100B
Carrier
Access COLAN X SONET/SDH Embedded
DCN 10/100B OME6500 DCC (PPP or DCC Remote
Network Element LAPD) Access
Used for external

DCN access ILAN IN ILAN OUT Used between
10/100BT 10/100BT sites
Embedded Used between

DCN Site shelves at a site
Interconnect
Interfaces
The interfaces/protocols are configured from the Comms Setting
Management application available from the Configuration menu item in Site
Manager.
For comms management procedures, see Provisioning and Operating

Procedures, 323-1851-310. Refer to Appendix A: Data communications
planning on page 10-1 for an overview of OME6500 communications
planning.
COLAN interface
The COLAN interface provides a mechanism to connect the OME6500
network element to the office DCN for connectivity to a management system
for remote management of the OME6500 network and subtending network
elements.
The COLAN interfaces consist of the two 10/100Base-T RJ-45 LAN ports
located on the access panel. The ports are configurable as half-duplex
10 Mbit/s, half-duplex 100 Mbit/s, full-duplex 10 Mbit/s, full-duplex
100 Mbit/s, and automatic. The default value for LAN port configuration is
automatic.
The COLAN port can be enabled or disabled with the default being disabled.
ILAN interface
The ILAN interface provides a mechanism to interconnect colocated
OME6500 network elements so that a remote user can perform OAM
functions by using a single OAM connection to OME6500 network elements
at a site. The ILAN interface can also be used to connect to other IP and OSI
based network elements via an Ethernet connection.
The ILAN interfaces consist of two 10/100Base-T RJ-45 LAN ports located
on the access panel. The ports are configurable as half-duplex 10 Mbit/s,
half-duplex 100 Mbit/s, full-duplex 10 Mbit/s, full-duplex 100 Mbit/s, and
automatic. The default value for LAN port configuration is automatic.
The ILAN port can be enabled or disabled with the default being disabled.
Craft user interface
The craft interface provides a mechanism to connect a PC or a modem to the
OME6500 network element for local or remote management. The physical
interfaces consist of the following:
• one 10/100Base-T RJ-45 LAN port located on the shelf processor circuit
pack. This port is configurable as half-duplex 10 Mbit/s, half-duplex
100 Mbit/s, full-duplex 10 Mbit/s, full-duplex 100 Mbit/s, and automatic.
The default value for LAN port configuration is automatic.
The LAN port can be enabled or disabled with the default being enabled.

• an RS-232 DB-9 DTE modem port located on the access panel. The baud
rate is set to auto-detect.
• an RS-232 DCE craft access port located on the shelf processor circuit
pack. The baud rate is set to auto-detect.
Section/RS and line/MS DCC interface
The section/RS and line/MS DCC interfaces provide a mechanism for
OME6500 network elements and subtending network elements to
communicate and exchange OAM messages using the section/RS and line/MS
overhead bytes.
The OME6500 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 using OSI or IP based DCC interfaces. The OAM for the OME6500
uses IP DCC and supports full routing of OSI DCC for other nodes which need
to route through the OME6500. Each DCC interface can be provisioned to
support IP or OSI. The network element supports GRE tunneling of OSI/IP
and IP/OSI on all interfaces.
Each SONET/SDH OCn/STMn port is capable of supporting comms on the
section/RS or line/MS DCC interface. The OME6500 supports the following
DCC capabilities:
• A DCC port can be configured as section/RS, line/MS, or Off. The default
value is Off. The OME6500 supports one section/RS DCC per optical port
and up to two line/MS DCC per OC-n/STM-n circuit pack.
• 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 off (DCC follows traffic) or on (DCC active on both
working and protected paths) is supported on 1+1/MSP linear
configurations (default is route diversity on). For BLSR/MS-SPRing
configurations, route diversity is always on.
• An alarm is raised when the DCC comms is lost on any port that is
configured and operational.
• Line/MS DCC port is linked to the administrative state of the associated
facility (when a facility is placed out-of-service, the line/MS DCC link
goes down)
OAM comms management
The OME6500 uses an IP-based comms infrastructure for network element
management and interworking with IP-based DCC network elements.
OME6500 also supports OSI-based DCC for interworking with OSI-based
network elements.
For more information about provisioning the communication parameters, see

OAM comms routing

Support of IP-based and OSI-based DCC requires support of several routing
protocols. OME6500 supports the following routing protocols:
• Integrated ISIS (iISIS)
iISIS is used as the internal DCN routing protocol and is available on all
interfaces except Autotunnel interfaces and the RS-232 ports.
• OSPF
OSPF is supported on the COLAN and ILAN ports but not the shelf
processor craft LAN port (LAN-15).
• Tunnelling
Generic Routing Encapsulation (GRE) is the encapsulation mechanism for
all tunnels. OME6500 supports the following tunnels:
— IP over OSI tunnelling
— OSI over IP tunnelling
— static tunnel configuration with up to 4 tunnels over each network layer
protocol (IP, OSI)
— dynamic tunnelling using auto-tunnelling, allowing a “plug and play”
architecture
OME6500 provides tunnelling support on all interfaces except the RS-232
port.
• DHCP server
The DHCP server supports Windows (98, NT, 2000, XP) based DHCP
client and is supported on the 10/100Base-T port located on the shelf
processor for local PC support.
The DHCP server can be configured with a single IP address. The default
value for configured DHCP server IP address is 10.0.0.2.
• HTTP server
OME6500 supports a single session HTTP server. The server supports
requests to deliver files to the HTTP client. Typically the HTTP server is
used to deliver Site Manager software stored on the shelf processor to a
local PC using a web browser. The HTTP is also used to deliver shelf OAM
data files to the Site Manager when a user logs in, speeding up the shelf
configuration retrieval.
TID address resolution protocol (TARP)
The TID address resolution protocol (TARP) is used by TL1-based network
elements to convert target identifiers (TID) into network service access points
(NSAP). An NSAP is used internally in a SONET/SDH communications
network as a means of addressing a network element.

TARP is a propagation protocol. TARP uses this propagation method with a

distributed database of learned TID/network entity title (NET) mappings.
TARP allows network elements to translate between TID and NET by
automatically exchanging mapping information with other TL1-based
network elements without the need for craftsperson intervention. No
additional address provisioning is required at the network element to support
TARP.
This release only supports TARP transparency which is required for

operations, administration, and maintenance (OAM) interoperability between
OME6500 network elements and network elements that are based on TL1.
DSM OAM comms

This release supports up to 16 DS1 service modules (DSM). These DSMs are
external equipment connected to the host OME6500 shelf via OC-3 optical
ports.
The DSMs are managed as an equipment entity in the OME6500 shelf in an

internal IS domain and do not appear as nodes in the external DCN (do not
appear in Routing Information table). Before a DSM can be provisioned
(either manually or automatically), a DSM OAM link must be provisioned on
the host OC-3 facility on the OME6500 (see Equipment/facility provisioning
on page 6-6).
The DSM supports a remote login (rlogin) facility which allows a PC

connected to the serial port of the DSM to access the OME6500 shelf if an
OAM link exists. If a OAM link does not exist between the DSM and the
OME6500, connecting a PC to the serial port opens a local UI which allows
the user to retrieve status information for SLAT or troubleshooting.
Note: The rlogin facility is only supported on the DSMs and is not
supported on the OME6500 network elements.
Alarm and event management

Active alarms are indicated on the OME6500 equipment and are visible from
the Site Manager user interface. Alarm history, events, and logs are stored on
the OME6500 network element. Login sessions using Site Manager craft user
interface, Optical Manager, and Optical Application Platform provide details
of network element alarms.
The types of OME6500 network element alarms are:

• equipment
• common equipment
• facility
The severity of an alarm is indicated by the following designations: Critical

(C), Major (M), minor (m) or warning (w). 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.
OME6500 local alarm indications

Trouble conditions present on the OME6500 network element are indicated
locally by:
• light-emitting diodes (LED) on the faceplate of a circuit pack. OME6500
uses a LED indication scheme based on simple intuitive relationships
where:
— Red indicates failure (requires replacement)
— Green indicates active (powered and operational)
— Yellow indicates warning (something missing or activity in progress)
— Blue indicates do not unseat (removing the circuit pack will impact
service) (except for the shelf processor which can be unseated with the
blue LED on)
• lamps and audible alarms on the MIC and BIP, see “Maintenance interface
card” on page 4-23 and “Breaker interface panel (optional)” on page 4-9.
Note: The MIC indicates alarms for the shelf and the BIP indicates alarms
for the OME6500 shelves in a bay.
For more information about the local alarm indications, refer to Alarm and
Trouble Clearing, 323-1851-543.
Site Manager alarm management/surveillance

The Site Manager provides the user with the ability to view and manage alarms
and events for the OME6500 as follows:
• view active alarms
• view alarm history and events
• manage alarm profiles
• provision alarms
• external alarm provisioning and controls
Viewing active alarms
Site Manager provides the user with a visual summary of all active alarms for
all OME6500s logged in to through the alarm banner. The user views a list of
active alarms on an OME6500 shelf by selecting the Active Alarms
application in the Fault menu of Site Manager.

The active alarm application provides the user with the ability to filter and sort
alarms and perform manual or automatic refresh of the active alarm list.
Alarms details are available for each active alarm in the list.
Alarm reports can be affected by the primary state of the circuit pack and
facilities. For example, an alarm is not reported until the primary state of a
circuit pack or facility changes from out-of-service to in-service.
For more information about surveillance and alarm clearing procedures, refer
to Alarm and Trouble Clearing, 323-1851-543.
Viewing alarm history and events
The user views the events on an OME6500 shelf by selecting the Events
application in the Fault menu of Site Manager. The Events feature supports the
following functionality:
• viewing of historical (current and cleared) alarms for the OME6500
network element
• viewing of logs
• filtering of alarms based on severity
• details for specific events (alarms or logs)
The OME6500 network element stores up to 5000 events. The events
application provides the user with the ability to filter and sort events and
perform manual refresh of the event list.
For more information about surveillance and alarm clearing procedures, refer
to Alarm and Trouble Clearing, 323-1851-543.
Alarm profiles
The Alarm profiles application in the Configuration menu of Site Manager
provides the ability for users to set up alarm profiles for an alarm class. The
application gives to the user the ability to view, edit, add and delete alarm
profiles.
An alarm profile contains all the alarm points applicable for the alarm class
and a status - enabled or disabled - for each alarm point. A profile can be
applied to an individual facility or circuit pack of that alarm class to quickly
disable multiple alarm points. A default profile can be set for an alarm class so
that when a new facility or circuit pack of that class is first provisioned, the
default alarm profile is applied to it automatically.
The OME6500 network element provides two non-editable predefined profiles

(All Enabled and All Disabled) and allows for three more predefined profiles
to be user editable on the network element.
For low order (VT1.5/VC12) path facilities on interface circuit packs, there is
an additional non-editable profile (Factory Default). The Factory Default
profile disables the reporting and logging of the VT1.5/VC12 defects. By
default, all VT1.5/VC12 facilities are set to Factory Default. Alarm monitoring
of VT1.5/VC12 facilities is limited to 1344 for each interface circuit pack, any
request to monitor more than this limit is rejected.
The Common alarm class also supports the Factory Default profile. For the
Common alarm class, this profile enables all common alarms except for the
LAN-15 alarm, which is disabled.
Viewing disabled alarms
Alarms that have been disabled from the alarm profiles application are not
displayed in the Active Alarms application. Active alarms which have been
disabled can be viewed in the Active Disabled Alarms application in the
Faults menu of Site Manager.
External alarm provisioning and controls
The OME6500 network element and each provisioned DSM has 16 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 alarms must be set up during provisioning. The alarm
types are assigned to a specific contact pin.
The External Alarm Provisioning application in the Configuration menu of

Site Manager supports the following functionality:
• displaying external alarm attributes (telemetry input points)
• enabling or disabling alarm attributes (telemetry input points)
The External Controls application in the Configuration menu of Site
Manager allows the user to retrieve and display the labels and status of the four
external controls relays for the OME6500 network element and each
provisioned DSM. The OME6500 network element allows the user to operate
or release these relays to turn external equipment on and off (for example, air
conditioning, fan, sprinkler) and edit the labels of the relays.
For detailed procedures and associated rules, refer to Alarm and Trouble
Clearing, 323-1851-543.
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. PM can also be used to facilitate
trouble/fault isolation.

Release 1.2 introduces support for DS1, DS3, and EC-1 PMs.
The OME6500 monitors the following entities for PM collection:

• section/regenerator section (RS) for OC-3/STM-1, OC-12/STM-4,
OC-48/STM-16, and OC-192/STM-64 facilities
• line/multiplex section (MS) for OC-3/STM-1, OC-12/STM-4,
OC-48/STM-16, and OC-192/STM-64 facilities
• path PM for STS-1, STS-3c/VC4, STS-12c/VC4-4c, STS-24c/VC4-8c,
STS-48c/VC4-16c, STS-192c/VC4-64c payloads
• section for EC-1 facilities
• line for EC-1, DS1, and DS3 facilities
• path for EC-1, DS1, and DS facilities
Note: DS1 and EC-1 facilities are only supported on SONET network
elements.
• line/PPI and path E1 facilities (SDH only)

• Ethernet PM for GE LAN (client facing)
• Ethernet PM for GE WAN (GFP-F mapped)
• physical PM for all OC-n/STM-n circuit packs (except for STM-1e SFPs
and DSM OC-3 facilities)
• protection switch count/duration
The OME6500 craft user interface (Site Manager) PM application allows the
user to retrieve:
• current PM values (15 minute, 1-Day and untimed values in progress)
• recent history (32 previous 15 minute and Day values stored on the
network element)
The PM counts can be viewed from the Facility PM counts application in the
Performance menu of Site Manager.
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. Each performance parameter has two thresholds which can be
applied to either the current 15 minute, day, or untimed counts. Each physical
parameter has one threshold on the current gauge value. 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 is available in two different applications on the

Site Manager.
• PM Threshold - allows the user to manage individual thresholds. The
Facility PM Threshold application is available from the Performance
menu in Site Manager.
• PM Profile - provides the user with the ability to create default thresholds
that can be applied across the many facilities. The PM Profiles application
is available from the Performance menu in Site Manager.
See PM parameter thresholds and PM profiles on page 6-79 and TCA events
on page 6-80 for more details on PM thresholding.
PM parameters
Three categories of PM parameters exist:
• facility PM parameters
• physical PM parameters
• protection switching PM parameters
PM parameter collection is also divided according to location/origination (near
end or far end) and direction (transmit or receive). The PM parameters are
represented as positive integer values associated with different time intervals,
plus an invalid data flag (IDF) represented as a question mark (?).
PM measurement mode
The method of counting facility PM parameters depends on the mode of the
associated port (SONET or SDH).
SONET PM is based on bit error measurement while SDH PM is based on

block error measurement:
• Bit error measurement - when the BIP byte/bits are checked, any of the
parity bits that indicate a parity error give rise to one bit error.
• Block error measurement - when the BIP byte/bits are checked, if one or
more of the parity bits indicate a parity error, only one block error is
counted.

Facility parameters
Facility parameters are mainly counts of errors, seconds containing errors, or
frame counts. Facility PM can be viewed from the Facility PM Counts
application available in the Performance menu of Site Manager.
For a complete definition of the PM parameters, see Performance Monitoring,

323-1851-520.
Physical parameters
The physical PM parameters behave as gauge readings which vary up and
down over time. Physical parameters are available in normalized and/or
un-normalized format.
Note: Physical PM are supported for all OC-n/STM-n circuit packs (not
supported on STM-1e SFPs).
For a complete definition of the physical parameters, see Performance

Monitoring, 323-1851-520.
Protection performance monitoring
The protection performance monitoring parameters include:
• protection switch count (PSCW and PSCP)
PSCW: For a working line, PSCW is the number of times that service
switched from the working line to the protection line, plus the number of
times that service switched back to the working line.
PSCP: For a protection line, PSCP is the number of times that service
switched from the protection line to the working line, plus the number of
times service switched back to the protection line.
Note: A protection event consist of any switching to/from protection
which includes protection completes due to the automatic switching as
well as user protection switching. Counts will usually be the same on both
protection and working circuit packs.
• protection switch duration (PSD)

For a working line, PSD is the number of seconds that service was carried
on the protection line. For a protection line, PSD is the number of seconds
that the line was used to carry service. The PSD accumulates until traffic
reverts to the working line. PSD is not available if the switch mode is
non-revertive and is therefore not applicable to 1+1/MSP linear protection
on OME6500.
PM time intervals
For the facility layer, physical layer, and protection switching parameters, the
following PM counts are stored and can be retrieved:
• current 15-minute interval
• last 32 15-minute intervals
• current day
• previous day
• untimed
PM enable/disable
Monitoring and threshold checking is enabled by default. The system does not
generate TCAs if the port/facility is out-of-service (OOS).
PM inhibition
The system inhibits the collection of PM when the associated facility is in the
out-of-service (OOS) state and for some parameters during various trouble
conditions.
The counting of all facility parameters for a level (except for section/RS SES,
line/MS UAS, line/MS FC, and PSC/PSD) is suppressed during periods of
unavailability. An entity (line/MS or section/RS) becomes unavailable at the
onset of 10 consecutive SES. The onset of 10 seconds which are not severely
errored marks the return to the available state.
PM parameter thresholds and PM profiles

When the error rate reaches or exceeds threshold values, the system generates
a threshold crossing alert (TCA). This alert warns maintenance personnel that
the number of performance errors is above an acceptable level for a parameter.
Each facility supports a set of TCA conditions that are raised when the first
applicable TCA is generated, and lowered when all applicable TCAs have
been reset or when the particular timed accumulation bin has terminated.
The OME6500 provides a PM profiles feature that enables users to manage the
threshold values that are used to trigger TCAs.
The OME6500 network element provides two non-editable predefined profiles

(All Off and Factory Default) and allows for four more predefined profiles to
be user editable on the network element. For details of the factory defaults, see
Performance Monitoring, 323-1851-520.

A profile contains all the facility and physical PM parameters that are
supported on the selected entity. Additionally, the user can assign a default
profile for an entity so that when a new object of that entity is first provisioned,
the system applies the default PM profile to it automatically. Only one default
profile can be assigned to an entity.
TCA events
The details of the TCA events include the following information:
• date and time of threshold crossing detection
• PM parameter associated with the TCA
• the affected facility, port and layer
• exceeded threshold
• threshold value
• parameter value that exceeded the threshold
• time interval to which the threshold applies
For more information, refer to Performance Monitoring, 323-1851-520.
The 4xGE EPL circuit pack collects operational measurements which contain
a set of counters not specific to any LAN interface type. Operational
measurements are also used for the WAN side of the circuit pack and consists
of 64 bit octet and packet counters for all interface speeds. The counters are
combined for unicast, multicast, and broadcast packets. These operational
measurements are asynchronously retrieved and cleared and are not stored in
bins (see Operational measurements time interval collection on page 6-81 for
exceptions). These counts can be viewed and cleared from the Operational
Measurements application in the Performance menu of Site Manager.
The operational measurements are collected by the 4xGE EPL circuit pack and
are divided into two groups:
• Generic Interface Operational Measurements and apply to the GE LAN
and WAN interface.
• Ethernet Specific Operational Measurements and apply to the GE LAN
interface only.
For details and definitions of the Generic Interface and Ethernet Specific
Operational Measurements, refer to Performance Monitoring, 323-1851-520.
Operational measurements time interval collection

The operational measurements are retrieved and cleared asynchronously and
are not stored in bins. However, the following OM counters are stored and can
be retrieved for both the ETH and WAN interfaces from the Facility PM
Counts application available from the Performance menu in Site Manager:
• In Frames
• In Errored Frames
• In Discarded Frames
• Out Frames
The following bins are provided for OM counter retrieval.
• current 15-minute interval
• last 32 15-minute intervals
• current day
• previous day
• untimed
For a more information, refer to Performance Monitoring, 323-1851-520.

The OME6500 provides the following security and administration capabilities
managed from Site Manager:
• network element security
— security levels
— login sessions
— local password management
— security log/audit trail
— local user authentication
— challenge/response authentication
— centralized RADIUS authentication
• network element administration
— network element naming
— date and time setting
— time of day administration (see Time of day synchronization on page
6-17)
For details of the procedures associated with security and administration, refer
to Security and Administration, 323-1851-301.

Local account user authentication

Local account user authentication uses a user ID and password and is the
default method on OME6500 network elements. A user ID and password is
managed individually at each network element.
Note 1: This method of user authentication is not available for network

elements enabled with centralized security administration (see Centralized
security administration (CSA) on page 6-83) and the alternative
authentication method provisioned as challenge/response.
Note 2: Local account user authentication is the default authentication
mode for network elements.
Local ‘challenge/response’ user authentication
When a local user logs in with ‘challenge/response’ as the specified domain,
they receive a challenge for which they must provide a response.
Challenge/response addresses many security issues associated with sending

authentication information over unsecured links:
• When a user tries to authenticate, they receive a challenge. This challenge
changes at each login attempt, regardless of if the login is successful or not.
• The system uses a local shared secret to calculate a response for a given
challenge. This local shared secret is never transmitted as part of the
authentication process.
Note: Only users with administrative access (default ADMIN, UPC 4) can
provision the challenge/response local shared secret.
• A response calculator (an application in the Tools menu of Site Manager)

generates a response for a challenge using the local shared secret. The
network element uses the same shared secret to validate if the response is
correct for the challenge.
The challenge generator and response validator are present on the shelf
processor. The user provisions the local shared secret on each shelf processor
which stores the local shared secret in a way that it is not visible in clear text.
Note 1: The challenge/response login mechanism is always available to

the user.
Note 2: If a challenge/response login is successful, the UPC level given to
the user is derived from the level encoded into the response from the
response calculator (found in the Tools menu of Site Manager).
Note 3: If the response for a challenge/response login includes lowercase
characters, you must enter the response in double quotes (“) when you log
in through TL1.
Note 4: The default local shared secret is ‘nortelnetworks’ (all in lower

case). The local shared secret can be provisioned through Site Manager or
TL1 and must be between 6 and 20 alphanumeric characters. To maintain
case sensitivity when you provision the secret through TL1, you must
enclose the secret in double quotes (“). The double quotes are not included
in the length of the secret.
The network element shared secret can be configured from the Centralized
Security Administration application in the Security menu of Site Manager.
Centralized security administration (CSA)

The centralized authentication mechanism that provides additional security
when accessing OME6500 network elements.
System administrators can provision access to be based on any one of three
methods:
• centralized user administration and authentication through RADIUS
• local account user authentication
• local ‘challenge-response’ user authentication
Note: Local account user authentication and RADIUS authentication
require a user identifier and password. See Local password management
on page 6-86 for information on password restrictions.
The CSA feature can be configured from the Centralized Security

Administration application in the Security menu of Site Manager.
Centralized user administration and authentication through RADIUS

OME6500 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, SLIP, PPP, telnet, and rlogin). The RADIUS protocol
is a UDP-based client-server protocol. OME6500 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
• Access-Accept - message sent from the authentication server to the
network element allowing access to the user
The shelf processor 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 either local account user authentication (if provisioned as the alternate) or
local challenge/response user authentication (always available).
Note 1: Network elements with CSA interoperate seamlessly with

network elements that do not support CSA or have not enabled CSA.
Note 2: If a user connects by RS-232 to a shelf processor, user
authentication is through centralized authentication. If the RADIUS server
is down, the system prompts the user to select between retrying with CSA,
challenge/response, or local authentication. Local authentication is only
available if provisioned as the alternate authentication method.
For more information about the login/retry strategy using the RADIUS server
and more information on the supported messages, refer to Security and
Administration, 323-1851-301.
Users can provision on the shelf processor:
• 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 server (enabled/disabled)
Note: The RADIUS server must be enabled before enabling CSA feature.
• state of the CSA feature (enabled/disabled)

• alternate login method on the network element
Database save and restore operations include the centralized authentication
provisioning data on the shelf processor. The centralized authentication
provisioning data on the shelf processor survives circuit pack restarts and
replacements.
The shelf processor raises the following alarms if it receives no response

within the timeout period:
• a Primary or Secondary RADIUS Server Unavailable alarm (minor,
non-traffic affecting) if the shelf processor receives no response from
either the primary or secondary RADIUS server
• an All Provisioned RADIUS Servers Unavailable alarm (major, non-traffic
affecting) if the shelf processor receives no response from both the primary
or secondary RADIUS server
The alarms clear when the connection with the server(s) recovers or when the
user deprovisions the RADIUS server or disables the CSA feature.
Security levels
OME6500 network elements support multiple security access levels. This
feature reduces accidental or intrusive interruption of service. There are five
user privilege code (UPC) security levels that allow a range of task execution
capabilities:
Level 5
• Surveillance allows complete access to all commands.
Level 4
• Administration allows complete access to all commands.
Level 3
• Provisioning allows access to provision, test, edit, and retrieve commands.
Level 2
• Control allows access to control and retrieve commands but not to
provisioning.
Level 1
• Retrieve allows the user to execute retrieve and report related commands.
Because of its limits, level 1 is appropriate for monitoring purposes.
Note: UPC levels 4 and 5 provide the same capabilities. It is
recommended that UPC level 4 is used to access all commands.
The shelf processor has two default accounts named SURVEIL (level 5 access)
with SURVEIL password and ADMIN (level 4 access) with ADMIN
password. Nortel Networks recommends that the default passwords be
changed. See Local password management on page 6-86 for more information.
Up to 100 accounts can be created for one network element. Five user sessions
using these accounts can be active at one time on one network element.
Login sessions
To manage an OME6500 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 10.
Multiple login sessions
Several user accounts can be active at the same time so long as the maximum
number of 10 login sessions in not exceeded. When several sessions are active,
commands can be sent to any network element on which the sessions are
active. Site Manager can display alarms, events and performance monitoring
reports for all network elements logged in. The network element allows
multiple concurrent login sessions through local or remote connections.
A local connection includes:
• connecting to an RS-232 port
• connecting to a 10/100Base-T port over TCP/IP

A remote connection is a login session from a local connection to any available

network element.
Local password management

The user performs local password management from the User Profile,
Change Password, and Invalid Passwords applications in the Security menu
of Site Manager.
Password restrictions
For the OME6500 network element, use a password identifier (PID) to activate
a user login session to the user ID (UID) specified, or to change the current
PID. The PID is a confidential code to qualify the authorized system user’s
access to the account specified by a UID. PIDs are between 6 and 10 characters
in length with a combination of alphanumeric (a-z, A-Z, 0-9) and special
characters. The following special characters are supported for use in PIDs:
! ” # $%’ () * + - . / < = >@[ ] ^ _ ‘{|} ~ space
The password must contain at least one alphabet character.
Control characters are not supported for the PID.
Enhanced password restrictions force you to select more secure passwords

using a password checking algorithm that meets the following requirements:
• A user can select as their password, an existing password that is associated
with another user ID thereby never divulging an existing password.
• Passwords must be at least six characters in length and contain a
combination of alphanumeric characters including at least one alphabet
and at least one numeric or special character as listed above.
• Passwords cannot contain the associated user ID.
• The network element provides a mechanism that prevents a user from
selecting a password that is part of the specified set of excluded passwords,
such as locally used acronyms and names.
Password reuse
To ensure that users do not reuse passwords, the systems enforces the
following requirements:
• there is a minimum waiting period (Password Change period)
(provisionable from 0 to 999 days) before an existing password can be
updated
• the user cannot reuse any of the five most recent passwords
Password aging
Password aging forces users to change their passwords periodically. The
longer a password remains in use, the greater the risk an intruder can discover
that password. When you change your password frequently you reduce the risk
of an intruder break-in.
The password aging interval can be set on a per user ID basis. The user
privilege code (UPC) 4 and 5 accounts cannot be disabled because of password
aging which ensures that there is always a way to login to the network element.
The system prompts users for password changes accordingly.
The system does not allow users with UPC 1 through 3 to log in if their
passwords have expired. There are two password modes for level 1 through 3
accounts: ‘Assigned’ and ‘Valid’.
• A user password is in ‘Assigned’ mode when the system administrator was
the last person to change the password (that is, initial account creation or
user forgot password). At this point, the system administrator and the user
both know the password. The user is expected to change their password to
one that only they know.
• A user password is in ‘Valid’ mode when the user password was last
changed by the user (that is, the user is the only person who knows the
password).
The following intervals are provisionable by a level 4 or 5 user to support
password aging:
• Password Expiry Period: the length of time after which the password is no
longer valid
• Password Validation Period: if the system administrator is the last person
to change the password (for example, initial creation of account or user
forgot password), the period of time a user has to change the password
before it expires
• Password Warning Period: the number of days before password expiration
that a warning message appears when a user logs into the network element
• Password Change Period: a specified minimum waiting period before an
existing password can be updated
Temporary Accounts
You can use the password aging feature to implement a temporary user account
feature. A temporary account denies the user access when the password
expires. A user creates a temporary account by setting the Password Change
Period to a period of time longer than the Password Validation Period. The
password therefore expires before the user can be change it.
Intrusion attempt handling

Intrusion attempts on the OME6500 network elements are alarmed and
displayed when an incoming access attempt fails due to incorrect user ID or
password. This alarm alerts administrators of intrusion after a provisionable
number of failed login attempts.
When users log in to a shelf they must give a user ID and a password. If the
information they enter matches a valid user ID and password, the system
allows the user access to the shelf. If the user ID or password is wrong, the user

can re-enter the user information to try again and a counter advances by one.
The provisionable range of invalid logins is between 2 and 20 before the
system locks the port out. The default value is 5 login attempts.
The system locks users out based on their originating address. When the
counter reaches the maximum number of invalid attempts, the system locks the
user out of the port for the required amount of time (0 to 7200 seconds, default
60 seconds). A user with a UPC level 4 or above can unlock the port.
The system raises an Intrusion Attempt alarm (Major, non-service affecting) to

warn the system administrator that an intrusion attempt has occurred. The
alarms clears if:
• a successful login occurs at the port
• a user unlocks the port
• a user manually clears the alarm using the clear security alarms feature
(this does not unlock the port).
Security logs record the originating address and connection type of invalid
access attempt to the shelf processor.
Intrusion attempt handling is enabled by default.
Intrusion attempt handling can be configured from the Intrusion Attempt

Handling application in the Security menu of Site Manager.
Security log audit trail

The security log, by default, records all commands on the network element that
require level 2 access or higher. The Security logs application is available
from the Security menu in Site Manager. The security log display includes the
following:
• date and time of the event
• user identification
• type of event
• names of resources accessed
• success or failure of event
The security log records the following events:
• all user login and logouts
• invalid user authentication attempts (and alarm/alerts caused by invalid
authentication attempts)
• authorized commands (according to user class)
• changes made in a users security profiles and attributes
• changes made in security profiles and attributes associated with a channel

or port
• changes made in the network element’s security configuration
The shelf processor archives these logs in a circular buffer accessible through
the Security menu in Site Manager. The circular buffer has a capacity of 600
logs per node (estimated 1 week’s activity). The security log does not include
logging on to Site Manager. The login is limited to operations on Site Manager
that invoke (directly or indirectly) commands and events on the local network
element as opposed to a network level view.
Network element name
The user can edit the network element name assigned during the
commissioning phase from the Node Information application in the
Time date and time setting

The user can edit the network element date and time setting provisioned during
the commissioning phase from the Node Information application in the
Backing up and restoring the network element database

Data management deals with the management and protection of provisioning
data within the network element. The provisioning data that is managed,
distributed, and replicated is divided into two sets:
• slot based data - all data required to set up services and traffic on a
provisionable traffic, service or cross-connect circuit packs in a slot. This
data includes:
— equipment attributes including family, type and state
— facility (including) payload attributes
— traffic and/or connection attributes
— protection data
— shelf synchronization data
— alarm provisioning instance data
• network element wide data that is replicated or backed up by this feature:
— IP addresses
— alarm provisioning templates
— security data
— account management data (user ids and password)
— network element or system configuration attributes
— user defined defaults

The network element is responsible for the resilience of its provisioning data.
Each piece of provisioning data exists on at least two separate circuit packs
within the network element. Each circuit pack contains a copy of its
configuration data and the shelf processor contains a master copy of all
databases on the shelf.
The shelf processor specific provisioning data is backed up to both

cross-connect circuit packs. This ensures that in the event of a failure of the
shelf processor circuit pack containing the master copy of the data, the system
can recover on its own without manual intervention. Replication of persistent
data ensures quick provisioning data recovery over shelf processor,
cross-connect circuit pack, or interface circuit pack restarts, including shelf
power down.
The user manages database backups from the Backup and Restore Manager
application in the Configuration menu of Site Manager. The application
allows 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 remote operations use FTP to move configuration data between
network elements and external backup repositories.
Refer to Security and Administration, 323-1851-301, for more information.
Installing Site Manager software

The Site Manager is the primary OAM&P interface for the OME6500 and is
available on a CD and from the shelf processor on the network element.
Installation of the Site Manager is a user-friendly, graphical user interface,
installation procedure that guides the user through the complete installation
process.
Refer to Chapter 8, “Ordering information” for the Site Manager OME6500

Release 1.2 Software CD product code and to the Site Manager for Optical
Multiservice Edge R1.2 Planning and Installation Guide, NTNM34DC for
more information about installing Site Manager from CD or from the network
element.
Installing and upgrading network element software

Release 1.2 network element software is factory installed on the circuit packs
and is also available on a CD in the event the network element software needs
to be re-installed on the circuit packs. Refer to Chapter 8, “Ordering
information” for the OME6500 Release 1.2 software load on CD product code.
Upgrading of the network element software is performed by two applications

in Site Manager:
• Release Management
• Upgrade Management
Note: Software upgrades must be performed following a specific
procedure. Refer to the upgrade change application procedure (CAP),
NTRN38AA, for more details and detailed upgrade procedures.
Release management
The release management feature allows the user to transfer a software load to
the network element. The release management process consists of the
following steps:
• Check Release (optional)- performs the following activities:
— Verifies accessibility to the remote server containing the new software
release.
— Verifies that all files exist on the remote server.
— Verifies that there is sufficient memory space on the shelf processor to
store the new software release.
• Deliver Release - performs the following activities:
— Verifies that there is sufficient memory space on shelf processor to
store the new software release.
— Transfers the software from the remote server to the shelf processor file
system.
— Performs a checksum on each file to ensure the file transfer was
successful.
Upgrade management
The upgrade management feature allows the user to upgrade:
• the complete network element software
• the shelf processor software only without upgrading other circuit packs
(when a shelf processor is inserted in a shelf which contains a higher or
lower software load)
Note: The software load must have been previously transferred using the
release management feature.

The upgrade management process consists of the following steps:

• Check Upgrade (optional)- performs the following activities:
— Verifies that upgrade path is supported.
— Performs a hardware baseline check to ensure the cards on the
OME6500 shelf are supported and comply with the minimum
hardware version.
— Validates if all files are present on shelf processor and performs a
checksum on each file.
— Performs same checks as check release.
— Verifies alarm free state.
• Load Upgrade - the network element proceeds to download the new
software to the shelf processor.
• First Invoke Upgrade - the shelf processor is restarted and executes the
new software loaded on the alternate flash zone.
• Second Invoke Upgrade - the software is distributed to the individual
circuit packs on the network element and then proceeds to restart each
circuit pack so that they execute the new software loaded on the alternate
flash zone. See Slot upgrade on page 6-92.
• Commit Upgrade - the new software loaded on the alternate flash zone is
copied to the primary flash zone.
Slot upgrade
This release supports a slot upgrade feature which minimizes the impact of
circuit packs that require a cold restart (due to an FPGA change) during an
upgrade. After the first invoke, the user is given the option of a fully automated
upgrade or a manual slot upgrades:
• a fully automated upgrade performs cold restarts on each circuit pack (if
required) one circuit pack at a time to minimize traffic impacts
• a manual slot upgrade which allows the user initiate the cold restart on
circuit packs requiring a cold restart using a new Slot Upgrades tab in the
Upgrade Management application in Site Manager.
The option to select a fully automated or manual slot upgrade is only available
after the first invoke has been performed and is selected using a checkbox on
the upgrade management application.
Network element software upgrade is performed following a detailed Change

Application Procedure (CAP). Refer to the appropriate Software Upgrade
CAP for more details (see Chapter 8, “Ordering information”).
7-1
Technical specifications 7-
This chapter provides technical specifications, as listed in Table 7-1, for the
Optical Multiservice Edge 6500 (OME6500) network element.
Table 7-1
Topic Page
Physical specifications 7-2
Power specifications 7-7
Connector pinouts 7-10
E1 cable pinouts and assemblies 7-18
E1 I/O panel, interface circuit pack, and connector port mapping 7-18
DS1 cable pinout and assemblies 7-25
DS3/EC-1 cable assemblies 7-27
8xOC-3/12/STM-1/4 SFP optical specifications 7-32
DSM 84xDS1 TM optical specifications 7-34
4xGE EPL SFP optical specifications 7-35
OMX optical specifications 7-36
Electrical specifications 7-36
Environmental specifications 7-38
Electromagnetic specifications 7-40
Safety specifications 7-41
Power and grounding specifications 7-42

7-2 Technical specifications
Physical specifications
Table 7-2 lists the following physical specifications for OME6500 bays. Table
7-3 lists the service interface port density.
Table 7-2
Physical specifications for OME6500 platform
Equipment Physical specification Notes

Shelf assemblies
Optical shelf assembly 10U (444.5 mm / 17.5 in.) Refer to:
height • Figure 7-1 on page 7-4 for an overview
Optical/front electrical 18U (800.1 mm / 31.5 in.) of the OME6500 optical shelf assembly
shelf assembly height • Figure 7-2 on page 7-4 for an overview
of the OME6500 optical/rear electrical
Optical/rear electrical shelf 8U (355.6 mm / 14.0 in.)
shelf assembly
assembly height
• Figure 7-3 on page 7-5 for an overview
DSM shelf assembly 3.3U (148 mm / 5.83 in.) of the OME6500 optical/front electrical
Width 440.5 mm / 17.3 in. shelf assembly
• Ordering Information, 323-1851-151 for
Depth 280.0 mm / 11 in.
more information about physical
specifications
Cooling units
Height 3U (132.6 mm / 5.2 in.)
Width 440.5 mm / 17.3 in.
Depth 280.0 mm / 11 in.
Breaker interface panels (OME6500 variants)
Height (2 x 100 A variant, 1U (44.4 mm / 1.75 in.) 1U required above NTK599AA BIP for
NTK599AA) maintenance and cabling purposes (for
example, torqing and lug inspection)
Height (universal variant, 2U (88.9 mm / 3.5 in.)
NTK599BA)
Width (all variants) 440.5 mm / 17.3 in.
Depth (all variants) 280.0 mm / 11 in.
Breaker interface panels (DSM variant)
DSM variant, NTN458RA:
Height 1U (44.4 mm / 1.75 in.)
Width 482.6 mm / 19 in (with brackets)
584.2 mm /23 in. (with brackets)
Depth 281.6 mm / 11.09 in.

Physical specifications for OME6500 platform
Equipment Physical specification Notes

Air plenums
Height 2U (88.9 mm / 3.5 in.) Required for optical/rear electrical shelf
assemblies. Integrated with fiber routing
Width 440.5 mm / 17.3 in. channel for optical and optical/front
Depth 280.0 mm / 11 in. electrical access shelf assemblies.
OMX module
Height 1U (44.4 mm / 1.75 in.)
Width 445.0 mm / 17.5 in.
Depth 280.0 mm / 11 in.
Fiber manager
Height 1U (44.4 mm / 1.75 in.)
Width 445.0 mm / 17.5 in.
Depth 280.0 mm / 11 in.
Table 7-3
OME6500 service interface port density
Circuit pack Port density/ Circuit pack/ Port density/
circuit pack shelf shelf
1xOC-192/STM-64 1 4 4
2xOC-48/STM-16 2 12 24
8xOC-3/12/STM-1/4 8 12 96
4xGE EPL 4 12 48
63xE1 63 8 (working) + 504

2 (protection)
24xDS3/EC-1 24 8 (working) + 192

2 (protection)
84xDS1 TM 84 per DSM 16 DSMs per 1344

OME6500
shelf
Refer to Ordering Information, 323-1851-151 for configuration rules.

Figure 7-1
OME6500 optical shelf assembly - physical specifications
Cooling unit
(3 U / 132.6 mm/ 5.2 in.) Shelf
Optical shelf assembly Fiber/cable

(10 U / 444.5 mm/ 17.5 in.) routing channel/
air plenum
440.5 mm /
17.3 in.
280.0 mm /
11.0 in.
Figure 7-2
OME6500 optical/rear electrical shelf assembly - physical specifications
Shelf
shelf assembly
(8 U / 355.6 mm/ 14 in.)
Fiber routing
channel
Rear access
electrical interface
440.5 mm /
17.3 in.
280.0 mm /
11.0 in.
Note: Each optical/rear electrical shelf or pair of optical/rear

electrical shelf requires a cooling unit and an air plenum.
Figure 7-3
OME6500 optical/front electrical shelf assembly - physical specifications
Cooling unit
(3 U / 132.6 mm/ 5.2 in.)
Shelf
Fiber/cable
routing channel
Optical/front electrical
shelf assembly Front access
(18 U / 800.1 mm/ 31.5 in.) electrical interface
440.5 mm /
280.0 mm / 17.3 in.
11.0 in.

Weights
Table 7-4 lists the weights for each OME6500 shelf item and circuit pack.
Table 7-4
Bay, shelf, and circuit pack weights
Description PEC Weight
Bay assemblies and accessories
600 mm wide x 300 mm deep x 2125 mm (high) NTRU0501 90.0 kg (198 lb)
PTE2000-EEA Frame (NEBS)
Extended EIA adapter rail kit NTRU0560 4.0 kg (8.8 lb)
PTE 2000 70 mm frame extender NTRU0510 5.0 kg (11.0 lb)
Concrete floor anchor kit (2 anchors) NTRU0328 1.0 kg (2.2 lb)
Shelf equipment
19” Optical Shelf Assy NTK503AA 15.0 kg (33 lb)
19” Optical/Front Electrical Shelf Assy NTK503BA 23.0 kg (50.6 lb)
19” Optical/Rear Electrical Shelf Assy NTK503CA 14.6 kg (32.2 lb)
84xDS1 DSM Shelf Assy (fully equipped) NTN407AC 9.6 kg (21.2 lb)
Top Venting Cooling Unit Kit NTK507AA 8.1 kg (17.8 lb)
Front Venting Cooling Unit Kit NTK507BA 7.3 kg (16.1 lb)
Rear Venting Cooling Unit Kit NTK507CA 9.0 kg (19.9 lb)
Air Plenum Assembly NTK507RA 3.0 kg (6.6 lb)
Shelf Front Cover NTK509CA 2.0 kg (4.5 lb)
Shelf Front Cover, Bottom NTK509DA 2.0 kg (4.5 lb)
Breaker Interface Panel, 4x40A, 1U+1U NTK599AA 4.9 kg (10.8 lb)
Breaker Interface Panel, 4x40A, 2U NTK599BA 8.6 kg (19.0 lb)
D-type/wire-wrap alarm connectors
Breaker Interface Panel, 20A (for DSM shelves) NTK458RA 4.5 kg (10.1 lb)
E1 75/120 ohm I/O Panel NTK571CA 3.6 kg (7.9 lb)
DS3/EC-1 I/O Panel NTK572CA/QA 1.7 kg (3.7 lb)
Common equipment
Access Panel (SDH) NTK505LA 1.0 kg (2.2 lb)
Access Panel (SONET/J-SDH) NTK505MA 1.0 kg (2.2 lb)
40 A Power Interface Card (breakered) NTK505AA 0.8 kg (1.8 lb)
40 A Power Interface Card (breakerless) NTK505BA 0.8 kg (1.8 lb)
Maintenance Interface Card NTK505FA 0.5 kg (1.1 lb)
Processor SP Circuit Pack Kit NTZF01AE 1.0 kg (2.2 lb)
X-CONN Circuit Pack NTK557AA/BA/NA/PA/QA 1.2 kg (2.6 lb)

Bay, shelf, and circuit pack weights
Description PEC Weight
Interface Filler Card NTK505YA 1.0 kg (2.2 lb)
1xOC-192/STM-64 circuit pack NTK523BA/DA/FA 1.3 kg (2.9 lb)
NTK524BA/DA/FA
1xOC-192/STM-64 DWDM circuit pack NTK526xx/NTK527xx 1.4 kg (3.1 lb)
2xOC-48/STM-16 SFP circuit pack NTK516BA/NTK517BA 1.3 kg (2.9 lb)
2xOC-48/STM-16 DPO circuit pack NTK519BA/NTK520BA 1.3 kg (2.9 lb)
8xOC-3/12/STM-1/4 SFP circuit pack NTK513DA/MA 1.2 kg (2.6 lb)
4xGE EPL SFP circuit pack NTK535LA 1.2 kg (2.6 lb)
63xE1 (75/120 ohm) circuit pack NTK541BA/PA 1.3 kg (2.9 lb)
E1 Protection Module NTK579NA 0.7 kg (1.5 lb)
24xDS3/EC-1 circuit pack NTK543NA/NTK544NA 0.9 kg (2.0 lb)
Optical modules
SFPs Various 0.02 kg (0.04 lb)
DPOs Various 0.08 kg (0.18 lb)
E1 cableforms
20 m E1 cableform (75 ohm) - 18 kg (39.6 lb)
Power specifications
The OME6500 equipment operates from -40 V dc to -75 V dc measured at the
input terminals of the network element. The following tables list the estimated
power consumption for the different modules:
• Table 7-5 lists the estimated power requirement for the common
equipment at -54 V dc.
• Table 7-6 lists the estimated power requirement for each interface circuit
pack -54 V dc.
• Table 7-7 lists the estimated power requirement for each small form-factor
pluggable (SFP) optical module and each DWDM pluggable optics (DPO)
module at -54 V dc.
• Table 7-8 lists the recommended feeders per shelf for this release.
Note: For practical purposes, the typical power consumption of an
equipment can be used as the equipment heat dissipation when calculating
facilities thermal loads.

Table 7-5
Power consumption for common equipment at -54 V dc
Circuit pack Typical (W)
Access panel (SDH) 0
Access panel (SONET/J-SDH) 0
40 A power input card (breakered) 2
40 A power input card (breakerless) 2
Maintenance interface card 1.2
Shelf processor 26
X-CONN 80G STS1/VC-3 circuit pack 48
X-CONN 160G STS1/VC-3 circuit pack 48
X-CONN 80G VT1.5/VC-12 (80/80) circuit pack 50
Interface filler card 0
Front cooling fan module 20
Top cooling fan module 20
Rear cooling fan module 20
Table 7-6
Power consumption for each interface circuit pack at -54 V dc
1xOC-192/STM-64 STS-1/HO IR2/S64.2 37
1xOC-192/STM-64 STS-1/HO SR2/I64.2 37
1xOC-192/STM-64 STS-1/HO LR2/L64.2 37
1xOC-192/STM-64 STS-1/HO DWDM 41
1xOC-192/STM-64 VT1.5/LO IR2/S64.2 60
1xOC-192/STM-64 VT1.5/LO SR2/I64.2 60
1xOC-192/STM-64 VT1.5/LO LR2/L64.2 60
1xOC-192/STM-64 VT1.5/LO DWDM 63
8xOC-3/12/STM-1/4 STS-1/HO SFP 44
8xOC-3/12/STM-1/4 VT1.5/LO SFP 46
2xOC-48/STM-16 STS-1/HO DPO 46
2xOC-48/STM-16 STS-1/HO SFP 29
2xOC-48/STM-16 VT1.5/LO DPO 51
2xOC-48/STM-16 VT1.5/LO SFP 34

Power consumption for each interface circuit pack at -54 V dc
4xGE EPL SFP circuit pack 39
63xE1 working circuit pack 45
63xE1 protection circuit pack (see Note) 55
24xDS3/EC-1 working circuit pack 32.2
24xDS3/EC-1 protection circuit pack 39.5
DSM shelf (without DS1x84TM circuit packs) 13
DSM shelf (with two DS1x84TM circuit packs) 55
DS1x84TM 21
Note: The 63xE1 protection circuit pack powers the protection
sub-modules. The 55 W figure includes the power required by one
protection sub-module (9 W). A maximum of one protection sub-module is
powered at a given time.
Table 7-7
Power consumption for each SFP/DPO at -54 V dc

SFP Modules 0.7
DPO Modules 0.7
GE/FC 1000-BaseLX XCT Enhanced SFP Module 0.8
Table 7-8
Recommended feeders
Configuration Feeders per shelf

OME6500 single shelf A feed (40 A) and redundant B feed (40 A)
bay solution (see Note)
Note: Maximum load is considered for future expansion.
Note: Refer to Ordering Information, 323-1851-151 for information about

BIP power feeds.
Refer to Ordering Information, 323-1851-151 for a list of power cables

assemblies available and the Installation, 323-1851-201 NTP for details on
installing and connecting power to an OME6500 shelf.

Connector pinouts
BIP connector pinouts
Table 7-9 to Table 7-13 provide details on the DB-9, DB-25, and wire-wrap
connector pinouts available on the BIPs.
Note: The relays are in the alarm condition when no power is

applied/available.
Table 7-9
Alarm input DB-9 male connector - pin assignment (NTK599AA)
Pin Signal
1 Spare pin
Pin 1 Pin 5 2 Critical
3 Major
4 Minor
Pin 6 Pin 9
5 Reserved pin
6 Spare pin
7 Receive Attention
8 Battery Return
9 Fault clear
Table 7-10
Alarm input DB-9 female connector - pin assignment (NTK599BA)
Pin Signal
1 Critical Visual N/O
Pin 5 Pin 1 2 Critical Audible, N/O

3 Battery Return
4 Battery Return
Pin 9 Pin 6
5 Battery Return
6 Major Visible, N/O
7 Major Audible, N/O
8 Minor Visible, N/O
9 Minor Audible, N/O
Table 7-11
Alarm output DB-25 male connector - pin assignment (NTK599AA)
Pin Signal Pin Signal

1 Minor, N/O 14 Minor, COM
2 Minor, N/C 15 Not connected
Pin 1 Pin 13
3 Major, N/O 16 Major, COM
4 Major, N/C 17 Not connected
Pin 14 Pin 25 5 Critical, N/O 18 Critical, COM
6 Critical, N/C 19 Not connected
7 Power, N/O 20 Power, COM
8 Power, N/C 21 Not connected
9 BRK Audible, N/O 22 BRK Audible, COM
10 BRK Audible, N/C 23 Not connected
11 BRK Visual, N/O 24 BRK Visual, COM
12 BRK Visual, N/C 25 Not connected
13 Not connected
Table 7-12
Alarm output DB-25 female connector - pin assignment (NTK599BA)

1 Minor Audible, N/O 14 Minor Visual, N/O
Pin 13 Pin 1 2 Minor Audible, COM 15 Minor Visual, COM

3 Minor Audible, N/C 16 Minor Visual, N/C
4 Not connected 17 Not connected
Pin 25 Pin 14
5 Major Audible, N/O 18 Major Visual, N/O
6 Major Audible, COM 19 Major Visual, COM
7 Major Audible, N/C 20 Major Visual, N/C
9 Critical Audible, N/O 22 Critical Visual, N/O
10 Critical Audible, COM 23 Critical Visual, COM
11 Critical Audible, N/C 24 Critical Visual, N/C
13 Not connected

Table 7-13
Optional alarm output wire-wrap connector - pin assignment (NTK599BC)

1A Visual Minor, N/O 1B Visual Minor, N/C
2A Visual Minor, COM 2B Visual Major, COM
Pin 1A Pin 9A
3A Visual Major, N/O 3B Visual Major, N/C
4A Visual Critical, N/O 4B Visual Critical, N/C
Pin 1B Pin 9B
5A Visual Critical, COM 5B Audible Minor, COM
6A Audible Minor, N/O 6B Audible Minor, N/C
7A Audible Major, N/O 7B Audible Major, N/C
8A Audible Major, COM 8B Audible Critical, COM
9A Audible Critical, N/O 9B Audible Critical, N/C
Access panel connector pinouts

Figure 7-4 shows the interfaces available on the SDH (NTK505LA) and
SONET/J-SDH (NTK505MA) access panels. Table 7-14 to Table 7-18 provide
details on the DB-9, DB-25, and wire-wrap connector pinouts available on the
access panels.
Figure 7-4
Access panel interfaces - overview
A ESI B A ESO B ESI/ESO DTE Alarm Telemetry COLAN-A COLAN-B ILAN In ILAN Out COLAN-X
SDH Access Panel
A Japan Clock B ESI/ESO ACO Visual / Audible Alarms Telemetry COLAN-A COLAN-B ILAN In ILAN Out COLAN-X
DTE
SONET Access Panel
Table 7-14
ESI/ESO 120 ohm balanced DB-9 female connector pinout (NTK505LA)

1 ESI A-N (ring) 6 ESI A-P (tip)
Pin 5 Pin 1 2 ESO A-N (ring) 7 ESO A-P (tip)
3 ESI B-N (ring) 8 ESI B-P (tip)
4 ESO B-N (ring) 9 ESO B-P (tip)
Pin 9 Pin 6
5 GND
Table 7-15
Alarms DB-9 female connector pinout (NTK505LA, Release 1 and 2)

1 NC 6 NC
Pin 5 Pin 1 2 Critical, N/O 7 NC
3 Major, N/O 8 COM
4 Minor, N/O 9 NC
Pin 9 Pin 6
5 NC
Table 7-16
Alarms DB-9 female connector pinout (NTK505LA, Release 3 onwards)

1 Visual Critical N/C 6 Visual Critical COM
Pin 5 Pin 1 2 Visual Critical N/O 7 Visual Major N/C
3 Visual Major, N/O 8 Visual Major COM
4 Visual Minor, N/O 9 Visual Minor N/C
Pin 9 Pin 6
5 Visual Minor COM
Table 7-17
Telemetry in/out DB-25 female connector pinout (NTK505LA)

1 Out 3, N/O 14 Out 3, COM
Pin 13 Pin 1 3 Out 4, N/O 16 Out 4, COM
Pin 14 5 In 7 18 In 15
Pin 25
6 In 8 19 In 16
7 In 5 20 In 13
8 In 6 21 In 14
9 GND 22 In 11
10 In 3 23 In 12
11 In 4 24 In 9
12 In 1 25 In 10
13 In 2

Table 7-18
DTE DB-9 male connector pinout (NTK505LA/MA)
Pin Signal Direction Description
1 CD DCE-to-DTE Carrier Detect
2 RX DCE-to-DTE Receive Data
Pin 1 Pin 5
3 TX DTE-to-DCE Transmit Data
4 DTR DTE-to-DCE Data Terminal Ready
Pin 6 Pin 9 5 GND Ground
6 DSR DCE-to-DTE Data Set Ready
7 RTS DTE-to-DCE Request To Send
8 CTS DCE-to-DTE Clear To Send
9 RI DCE-to-DTE Ring Indicator
Table 7-19
BITS/ACU/alarms wire-wrap connector pinout (NTK505MA)
BITS
Pin 12A
Pin 8A Pin 32A 2A ESI A-P (tip) 2C ESI A-N (ring)
Pin 2A Pin 16A
RMT VISUAL/AUDIBLE
4A ESI B-P (tip) 4C ESI B-N (ring)
BITS ACU ALARMS
6A ESO A-P (tip) 6C ESO A-N (ring)
Pin 2C 8A ESO B-P (tip) 8C ESO B-N (ring)

Pin 16C
Pin 8C Pin 32C RMT ACU
Pin 12C
12A ACO/Lamp Test 12C Ground
Visual/Audible Alarms
16A Visual Minor, N/O 16C Visual Minor, N/C
18A Visual Minor, COM 18C Visual Major, COM
20A Visual Major, N/O 20C Visual Major, N/C
22A Visual Critical, N/O 22C Visual Critical, N/C
24A Visual Critical, COM 24C Audible Minor, COM
26A Audible Minor, N/O 26C Audible Minor, N/C
28A Audible Major, N/O 28C Audible Major, N/C
30A Audible Major, COM 30C Audible Critical, COM
32A Audible Critical, N/O 32C Audible Critical, N/C
Table 7-20
Telemetry wire-wrap connector pinout (NTK505MA)
2A Out 4, N/O 2C Out 4, COM
Pin 2A Pin 30A
Pin 2C Pin 30C 10A In 16 10C Ground
12A Ground 12C In 15
14A In 13 14C In 14
16A Ground 16C In 12
18A In 10 18C In 11
20A Ground 20C In 9
22A In 7 22C In 8
24A Ground 24C In 6
26A In 4 26C In 5
28A Ground 28C In 3
30A In 1 30C In 2
Shelf processor connector pinout

Table 7-21 provides the pinout of the DB-9 DCE port on the shelf processor.
Table 7-21
DCE DB-9 female connector pinout
1 CD DCE-to-DTE Carrier Detect
2 TX DCE-to-DTE Transmit Data
Pin 5 Pin 1 3 RX DTE-to-DCE Receive Data
4 DTR DTE-to-DCE Data Terminal Ready
5 GND Ground
Pin 9 Pin 6
6 DSR DCE-to-DTE Data Set Ready
7 RTS DTE-to-DCE Request To Send
8 CTS DCE-to-DTE Clear To Send
9 RI DCE-to-DTE Ring Indicator

10/100Base-T RJ-45 pinout

Table 7-22 provides the pinout of the 10/100Base-T RJ-45 connectors on the
access panel and the shelf processor.
Table 7-22
10/100Base-T RJ-45 pinout
Signal
RJ-45 Plug Pin
Shelf processor Access panel
1 RXD+ TXD+
2 RXD– TXD–
3 TXD+ RXD+
4 No connection No connection
Pin 1 Pin 8
6 TXD– RXD–
DSM OAM adapter module

Table 7-23 provides the pinout of the DB9 connector on the DSM OAM
adapter module.
Table 7-23
DSM local user interface (LIU) - pinout
1 CD DSM Carrier Detect
2 RX DSM out Receive Data
Pin 1 Pin 5
3 TX DSM in Transmit Data
4 DTR DSM in Data Terminal Ready
Pin 6 Pin 9 5 GND in/out Ground
6 DSR DSM Data Set Ready
7 RTS DSM in Request To Send
8 CTS DSM Clear To Send
9 - Not connected
Table 7-24 provides the pinout of the wire-wrap connector on the DSM OAM
adapter module.
Table 7-24
DSM OAM adapter module - pinout
Env in
1 8
0 0 0 0 0 0 0 0 0
Environmental Ground
Environmental 0 0 0 0 0 0 0 0 0
inputs 1-16
alarm pins
Env in
16
0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0
Ground Environmental
0 0 0 0 0 0 0 0 0
output 1-4
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 Environmental
0 0 0 0 0 0 0 0 0 outputs -RET
C M m sp C M m sp
N.O. 0 0 0 0 0 0 0 0 0 BRET A
COM 0 0 0 0 0 0 0 0 0 BRET B
N.C. 0 0 0 0 0 0 0 0 0 ACO
Audible
Visual 54
1 2 3 4 5 6 7 8 9
Environmental Inputs
1 ENVIN1 ENVIN2 ENVIN3 ENVIN4 ENVIN5 ENVIN6 ENVIN7 ENVIN8 GND
2 ENVIN9 ENVIN10 ENVIN11 ENVIN12 ENVIN13 ENVIN14 ENVIN15 ENVIN16 GND
Environmental Outputs
3 GND GND GND ENVOUT ENVOUT ENVOU1 ENVOU2 ENVOU3 ENVOU4
-RET -RET
Audible/Visual Alarms
4 AUD CR AUD MJ AUD MN AUD VIS CR VIS MJ VIS MN VIS spare BRET A
N/O N/O N/O spare N/O N/O N/O N/O
N/O
5 AUD CR AUD MJ AUD MN AUD VIS CR VIS MJ VIS MN VIS spare BRET B
COM COM COM spare COM COM COM COM
COM
6 AUD CR AUD MJ AUD MN AUD VIS CR VIS MJ VIS MN N/C ACO
N/C N/C N/C spare N/C N/C N/C N/C

E1 cable pinouts and assemblies

Cable assemblies
Each 63xE1 working circuit pack requires two E1 cable assemblies. The
following sections detail the pinouts and port mappings for the 75 ohm and
120 ohm cable assemblies. These cable assemblies can be ordered from Nortel
Networks (see Ordering Information, 323-1851-151):
• Figure 7-5 shows the 75 ohm cable assembly and connector pinout.
Table 7-25 shows the 75 ohm cable identification information. The lower
cable provides the receive interfaces, the upper cable provides the transmit
interfaces. For example, the coaxial cable connected to pins 75 and 100 is
labelled as ‘RX-04’ (cable/port) in Table 7-25. This means that cable
provides the receive interface for connector port 04.
• Figure 7-6 shows the 120 ohm cable assembly and connector pinout. The
120 ohm twisted pair cable assembly is constructed with 26 AWG tinned
copper solid conductors.
Table 7-26 shows the cable identification information. The lower cable
provides the receive interfaces, the upper cable provides the transmit
interfaces. Each cable contains eight groups of four twisted pairs identified
by the wire colors as shown in Table 7-25 (for example, orange and
orange/white pair are twisted pair 1). Group 1 provides the connector ports
1 to 4, group 2 provides connector ports 5 to 8, ...., and group 8 provides
connector ports 29 to 32.
For example, the twisted pair connected to pins 72 and 104 is labelled as
‘RX- 4’ (cable/group) and has a brown (signal +) and brown/white
(signal -) twisted pair. This means that the twisted pair provides the receive
interface contained in cable group 4 and is the twisted pair 4 in that group.
Group 4 provides connector ports 13 to 16, so twisted pair 4 in group 4 is
connector port 16.
See E1 I/O panel, interface circuit pack, and connector port mapping on page
7-18 for details on the mapping of connector ports to the ports on the 63xE1
circuit packs.
Connectors
The user must terminate the free end of the cable assemblies with appropriate
connectors. See Ordering Information, 323-1851-151 for details of the
connectors available for the 75 ohm cable assemblies.
E1 I/O panel, interface circuit pack, and connector port mapping

Table 7-27 on page 7-23 and Table 7-28 on page 7-24 provide details of the
mapping of the ports on the interface connectors to the ports on the 63xE1
circuit packs. These tables should be read in conjunction with Table 7-25
(75 ohm) or Table 7-26 (120 ohm) to determine the coaxial cable/twisted pair
allocation for each port on each cable.
Figure 7-5
E1 75 ohm cable assembly
x
40A
Various lengths
TC
NT
x
up to 100 m
40A
32 position
TC
Tx
NT
coaxial cable
(see Note)
Rx
Upper cable
(Tx)
Tx
Lower cable
x
(Rx)
40A
Rx
TC
NT
x
40A
TC
NT
Pin 71 Pin 36
Pin 106 Pin 1
Pin 140 Pin 35

Pin 105 Pin 70
Note: Each coaxial cable bundle has a
maximum outside diameter of 16 mm.

Table 7-25
E1 75 ohm cable identification information
75 Ohm Cable Assembly - Cable/Wire Identification (see Figure 7-5)
Pos Cable Config. E1 Pos Cable Config E1 Pos Cable/ Config E1 Pos Cable Config E1
/No Conn /No . Conn No . Conn /No . Conn
Port # Port # Port # Port #
001 - n.c. 036 - n.c. 071 - n.c. 106 - n.c.
002 - n.c. 037 - n.c. 072 - n.c. 107 - n.c.
003 - n.c. 038 - n.c. 073 - n.c. 108 - n.c.
004 RX-01 Ground 1 039 RX-01 Signal 1 074 RX-02 Signal 2 109 RX-02 Ground 2
020 TX-01 Ground 1 055 TX-01 Signal 1 090 TX-02 Signal 2 125 TX-02 Ground 2
Figure 7-6
E1 120 ohm cable assembly
x
0B
A4
x
TC
0B
NT
A4
Various lengths Twisted pair
TC
NT
up to 100 m cable
Tx
(see Note)
Rx
Tx
Upper cable
Rx
(Tx)
x
0B
A4
Lower cable
x
TC
0B
NT
A4
(Rx) Pin 65 Pin 33

TC
NT
Pin 97 Pin 1
Pin 128 Pin 32

Pin 96 Pin 64
Note: Each twisted pair cable bundle has a
maximum outside diameter of 12.8 mm.

Table 7-26
E1 120 ohm cable identification
120 Ohm Twisted Pair Cable Assembly - Cable/Wire Identification (see Figure 7-6)
Pin Cable- Color E1 Pin Cable- Color E1 Pin Cable- Color E1 Pin Cable- Color E1
Group Conn Group Conn Group Conn Group Conn
Port # Port # Port # Port #
001 RX-1 Or 1 033 RX-1 Or/Wh 1 065 RX-1 Gn 2 097 RX-1 Gn/Wh 2
002 RX-1 Bl 3 034 RX-1 Bl/Wh 3 066 RX-1 Bn 4 098 RX-1 Bn/Wh 4
017 TX-1 Or 1 049 TX-1 Or/Wh 1 081 TX-1 Gn 2 113 TX-1 Gn/Wh 2
018 TX-1 Bl 3 050 TX-1 Bl/Wh 3 082 TX-1 Bn 4 114 TX-1 Bn/Wh 4
Wire Identification 1 Orange (Or) Signal + Orange/White (Or/Wh) Signal -

2 Green (Gn) Signal + Green/White (Gn/Wh) Signal -
3 Blue (Blue) Signal + Blue/White (Bl/Wh) Signal -
4 Brown (Bn) Signal + Brown/White (Bn/Wh) Signal -
Table 7-27
E1 port mappings - 252xE1 I/O panel in interface slots 1 and 2 (left side)
E1 Connector 1:
E1 Connector 2:
E1 Connector 3:
E1 Connector 4:
E1 Connector 5:
E1 Connector 6:
E1 Connector 7:
E1 Connector 8:
Interface Card
Interface Card
Interface Card
Interface Card
Interface Card
Interface Card
Interface Card
Interface Card
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
1 Slot 1 1 Slot 1 1 Slot 2 1 Slot 2 1 Slot 3 1 Slot 3 1 Slot 4 1 Slot 4
Port 1 Port 33 Port 1 Port 33 Port 1 Port 33 Port 1 Port 33
32 Slot 1 32 32 Slot 2 32 32 Slot 3 32 32 Slot 4 32
Port 32 Port 32 Port 32 Port 32

Table 7-28
E1 port mappings - 252xE1 I/O panel in interface slots 3 and 4 (right side)
E1 Connector 3:
E1 Connector 4:
E1 Connector 5:
E1 Connector 6:
E1 Connector 7:
E1 Connector 8:
E1 Connector 1:
E1 Connector 2:
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Interface Card
Interface Card
Interface Card
Interface Card
Interface Card
Interface Card
Interface Card
Interface Card
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
Port Number
32 Slot 9 32 32 Slot 10 32 32 Slot 11 32 32 Slot 12 32
Port 32 Port 32 Port 32 Port 32
DS1 cable pinout and assemblies

Two DS1 cable assemblies are required for every 28 DS1s (one for 28 DS1 in,
and one for 28 DS1 out), see Figure 7-7 and Figure 7-8. Table 7-29 shows the
pinout for the connectors on the DS1 cable assemblies.
Note 1: The color codes and pinout provided apply to the suggested DS1
cables. Color codes and pinout may vary by manufacturer.
Note 2: You are recommended to use ‘right-angle’ cables for the DSM.
Figure 7-7
DS1 straight cable assembly
Pin #1
33 1
64 32
655 ft (max)
Figure 7-8
DS1 right-angle cable assembly
655 ft (max)
Pin #1

Table 7-29
DS1 cable assemblies - pinout
DS1 tributary Pin number Color DS1 tributary Pin number Color
1 (ring) 1 bl/w 17 (ring) 17 o/y
1 (tip) 33 w/bl 17 (tip) 49 y/o
2 (ring) 2 o/w 18 (ring) 18 gr/y
2 (tip) 34 w/o 18 (tip) 50 y/gr
3 (ring) 3 gr/w 19 (ring) 19 br/y
3 (tip) 35 w/gr 19 (tip) 51 y/br
4 (ring) 4 br/w 20 (ring) 20 sl/y
4 (tip) 36 w/br 20 (tip) 52 y/sl
5 (ring) 5 sl/w 21 (ring) 21 bl/v
5 (tip) 37 w/sl 21 (tip) 53 v/bl
6 (ring) 6 bl/r 22 (ring) 22 o/v
6 (tip) 38 r/bl 22 (tip) 54 v/o
7 (ring) 7 o/r 23 (ring) 23 gr/v
7 (tip) 39 r/o 23 (tip) 55 v/gr
8 (ring) 8 gr/r 24 (ring) 24 br/v
8 (tip) 40 r/gr 24 (tip) 56 v/br
9 (ring) 9 br/r 25 (ring) 25 sl/v
9 (tip) 41 r/br 25 (tip) 57 v/sl
10 (ring) 10 sl/r 26 (ring) 26 bl/w
10 (tip) 42 r/sl 26 (tip) 58 w/bl
11 (ring) 11 bl/bk 27 (ring) 27 o/w
11 (tip) 43 bk/bl 27 (tip) 59 w/o
12 (ring) 12 o/bk 28 (ring) 28 gr/w
12 (tip) 44 bk/o 28 (tip) 60 w/gr
13 (ring) 13 gr/bk GND 29 —
13 (tip) 45 bk/gr GND 61 —
14 (ring) 14 br/bk GND 30 —
14 (tip) 46 bk/br GND 62 —
15 (ring) 15 sl/bk GND 31 —
15 (tip) 47 bk/sl GND 63 —
16 (ring) 16 bl/y GND 32 —
16 (tip) 48 y/bl GND 64 bare (see Note)
Note: Unclad sheath drain wire. DS1grounding must be built into the cables during cable assembly.
Ensure shield (sheath) drain wire is connected to ground pin inside connector at the end of cable and
at the end of DS1 cable opposite shelf end of cable (i.e. both ends of shield drain to be grounded).
DS3/EC-1 cable assemblies

Two DS3/EC-1 cable assemblies are required for each DS3/EC-1 interface
(one for DS3/EC-1 in, and one for DS3/EC-1 out). Cable assemblies are
available with either 1, 12, or 24 conductors with straight connectors (see
Figure 7-9). These cable assembles use 735A coaxial cable.
Figure 7-9
DS3/EC-1 cable assemblies
Single Conductor Cable Assembly (NTTC03Ax)
12 Conductor Cable Assembly (NTTC03Cx)
24 Conductor Cable Assembly (NTTC03Ex)
Connectors
The user must terminate the free end of the cable assemblies with appropriate
connectors (see Table 8-1 on page 8-1 for details). See Ordering Information,
323-1851-151 for details of the connectors available for the DS3/EC-1 cable
assemblies.

1xOC-192/STM-64 optical specifications

Table 7-30 lists the transmitter specifications and Table 7-31 lists the receiver
specifications for the OC-192/STM-64 circuit packs.
Table 7-30
Transmitter specifications for 1xOC-192/STM-64
Transmitter specifications SR1/I64.1 IR2/S64.2 LR2/L64.2 LR2/L64.2

PEC NTK523BA/ NTK523DA/ NTK523FA/ NTK523FB/
NTK524BA NTK524DA NTK524FA NTK524FB
Nominal wavelength 1310 nm 1550 nm 1533 nm 1557 nm
Wavelength range 1290 nm to 1530 nm to +/- 2.5 nm +/- 2.5 nm
1330 nm 1565 nm
Transmit output power -6 dBm to -1 dBm to +1 dBm to +1 dBm to
-1 dBm +2 dBm +5 dBm +5 dBm
Nominal reach 7 km 40 km 80 km (see 80 km
Note 3)
Note 1: All parameter values in the above table achieve an optical system BER better than 1x10-12
when used over G.652 specified SMF-28 fiber.
Note 2: Nominal reach figures are for classification purposes only and apply for specified wavelength
range.
Note 3: Dispersion limited performance is approximately 1600 ps/nm which gives an dispersion
limited reach of 80 km when using NDSF fibre.
Table 7-31
Receiver specifications for 1xOC-192/STM-64
Receiver specifications SR1/I64.1 IR-2/S-64.2 LR2/L64.2 LR2/L64.2
PEC NTK523BA/ NTK523DA/ NTK523FA/ NTK523FB/
NTK524BA NTK524DA NTK524FA NTK524FB
Wavelength range 1260 nm to 1260 nm to 1530 nm to 1530 nm to
1600 nm 1600 nm 1565 nm 1565 nm
Receiver sensitivity -11 dBm -14 dBm -23.5 dBm -23.5 dBm
Receiver overload -1 dBm -1 dBm -6 dBm -6 dBm
Path penalty 1 dB 2 dB 2 dB 2 dB
Note: All parameter values in the above table achieve an optical system BER better than 1x10-12
specifications for the 1xOC-192/STM-64 DWDM circuit packs.
Table 7-32
Transmitter specifications for 1xOC-192/STM-64 DWDM
Transmitter specifications DWDM circuit packs

Tx module laser type DFP laser with InP MZ modulator
Laser spectral width 20 MHz Full Width Half Maximum
Wavelength range 1528.77 nm to 1564.68 nm
(see Note 1)
Central wavelength accuracy +/- 0.04 nm
Transmit output power +2.6 dBm to +4.2 dBm
Dispersion Limited Performance 2000 ps/nm (see Note 2)
Chirp polarity negative
Note 1: Refer to Ordering Information, 323-1851-151 for list of supported wavelengths and
PECs.
Note 2: Equates to approximately 110 km to 120 km of NDSF fibre depending on transmit
wavelength.
Table 7-33
Receiver specifications for 1xOC-192/STM-64 DWDM
Receiver specifications DWDM circuit packs
Photodetector type APD (uncooled)
Wavelength range 1528.77 nm to 1564.68 nm
Receiver sensitivity at OSNR >= 28 dB -23 dBm (see Note1)
Receiver overload -8 dBm
Note 1: The sensitivity level is the minimum optical power for which the interface meets an
corrected bit-error-rate of 10-15 with FEC on.
Note 2: Quoted OSNRs are as measured using 0.1 nm resolution bandwidth.

2xOC-48/STM-16 optical specifications

specifications for the OC-48/STM-16 SFPs.
Table 7-34
Transmitter specifications for OC-48/STM-16 SFPs
Transmitter specifications IR1/S16.1 LR2/L16.2 2.5G NRZ CWDM
(S-C8L1-1Dx)
PEC NTTP03CF NTTP03FF NTK590xH
(see Note 4)
Nominal wavelength 1310 nm 1550nm 1471 nm to
1611 nm
Transmit output power -5 dBm to 0 dBm -2 dBm to +3 dBm 0 dBm to +5 dBm
Nominal reach 15 km 80 km See Note 3
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 except for the CWDM value which is for an
optical system BER better than 1x10-12.
Note 2: Nominal reach figures are for classification purposes only.
Note 3: 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 4: Refer to Ordering Information, 323-1851-151 for list of supported wavelengths and PECs.
Table 7-35
Receiver specifications for OC-48/STM-16 SFPs
Receiver specifications IR1/S16.1 LR2/L16.2 2.5G NRZ CWDM
(S-C8L1-1Dx)
PEC NTTP03CF NTTP03FF NTK590xH
Wavelength range 1260 nm to 1500 nm to 1260 nm to
1360 nm 1580 nm 1620 nm
Receiver sensitivity -18 dBm -28 dBm -28 dBm
Receiver overload 0 dBm -9 dBm -9 dBm
Path penalty 1 dB 2 dB 2.5 dB
Note: 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 except for the CWDM value which is for an optical
system BER better than 1x10-12.
specifications for the OC-48/STM-16 DWDM DPOs.
Table 7-36
Transmitter specifications for OC-48/STM-16 DWDM DPOs
Transmitter specifications DWDM DPOs

Tx module laser type Direct mod.
Laser spectral width 1 nm
Wavelength range 1527 nm to 1563 nm
(see Note)
Central wavelength accuracy +/- 0.10 nm
Transmit output power +2.6 dBm to +6.0 dBm
Dispersion Limited Performance 3000 ps/nm
Chirp polarity Non-chirp direct mod.
Note: Refer to Ordering Information, 323-1851-151 for list of supported wavelengths and PECs.
Table 7-37
Receiver specifications for OC-48/STM-16 DWDM DPOs
Receiver specifications DWDM DPOs
Photodetector type APD
Receiver sensitivity at OSNR >= 28 dB -28 dBm (see Note 1)
Path penalty 2 dB (see Note 2)
Note 1: The sensitivity level is the minimum optical power for which the interface meets a
bit-error-rate of 10-12.
Note 2: At the dispersion maximum provided in Table 7-36.
Note 3: Quoted OSNRs are as measured using 0.1 nm resolution bandwidth.

8xOC-3/12/STM-1/4 SFP optical specifications

Table 7-38
Transmitter specifications SR0 LR2/L1.2
PEC NTTP02AD NTTP02FF
Nominal wavelength 1270 nm to 1380 nm 1550 nm
Transmit output power -20 dBm to -14 dBm -5 dBm to 0 dBm
Nominal reach 2 km 80 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. 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.
Table 7-39
Receiver specifications SR0 LR2/L1.2
PEC NTTP02AD NTTP02FF
Wavelength range 1100 nm to 1600 nm 1260 nm to 1580 nm
Receiver sensitivity -30 dBm -34 dBm
Receiver overload -14 dBm -10 dBm
Path penalty N/A 1 dB
Note: 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.
Table 7-40
Transmitter specifications LR2/L4.2
PEC NTTP05FF
Nominal Wavelength 1550 nm
Transmit output power -3 dBm to +2 dBm
Nominal reach 80 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.
Table 7-41
Receiver specifications LR2/L4.2
PEC NTTP05FF
Receiver sensitivity -28 dBm
Path penalty 1 dB
Note: 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.
specifications for the OC-3/12/STM-1/4 SFPs.
Table 7-42
Transmitter specifications for OC-3/12/STM-1/4 SFPs
Transmitter specifications SR1/I1.1_I4.1 IR1/S1.1_S4.1
PEC NTTP04BF NTTP04CF
Nominal wavelength 1310 nm 1310 nm
Transmit output power -15 dBm to -8 dBm -15 dBm to -8 dBm
Nominal reach 2 km 15 km
Note 1: All parameter values in the above table achieve an optical system BER better than 1x10-10
Table 7-43
Receiver specifications for OC-3/12/STM-1/4 SFPs
Receiver specifications SR1/I1.1_I4.1 IR1/S1.1_S4.1
PEC NTTP04BF NTTP04CF
Wavelength range 1274 nm to 1580 nm 1274 nm to 1580 nm
Receiver sensitivity -28 dBm -28 dBm
Receiver overload -8 dBm -8 dBm
Path penalty 1 dB 1 dB
Note: All parameter values in the above table achieve an optical system BER better than 1x10-10

DSM 84xDS1 TM optical specifications

specifications for the DSM 84xDS1 TM interfaces.
Table 7-44
Transmitter specifications for DSM 84xDS1 TM
Transmitter specifications IR1/S1.1
PEC NTN313AC
Nominal wavelength 1310 nm
Transmit output power -15 dBm to -8 dBm
Nominal reach 15 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.
Table 7-45
Receiver specifications for DSM 84xDS1 TM
Receiver specifications IR1/S1.1
PEC NTN313AC
Receiver sensitivity -28 dBm
Path penalty 1 dB
Note: 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.
4xGE EPL SFP optical specifications

specifications for the GE/FC SFPs.
Table 7-46
Transmitter specifications for GE/FC SFPs
Transmitter SX LX ZX CWDM
specifications
PEC NTTP01AF NTTP01CF NTTP07FF NTK591xB
Nominal 850 nm 1310 nm 1550 nm 1471 nm to 1611 nm
wavelength (20 nm channels)
Transmit output -9.5 dBm to -9.5 dBm to 0 dBm to 0 dBm to
power x dBm -3 dBm +5 dBm +5 dBm
(see Note 3)
Nominal reach 220 m to 550 m 10 km ~70 km (see Note 6) see Note 7
(see Note 4) (see Note 5)
Note 1: All parameter values in the above table achieve an optical system BER better than 1x10 -12.
Note 3: The maximum transmit power is the lesser of Class 1 safety limits (CDRH and EN 60825) or
the receiver overload.
Note 4: The nominal reach is 220 nm over 62.5 µm, 160 MHz-km MMF to 550 m over 50 µm,
500 MHz-km MMF.
Note 5: When used over G.652 specified SMF-28 fiber.
Note 6: When used over NDSF SMF (link engineering is required for links using the ZX SFP).
Note 7: 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.
Table 7-47
Receiver specifications for GE/FC SFPs
Receiver SX LX ZX CWDM
specifications
PEC NTTP01AF NTTP01CF NTTP07FF NTK591xB
Wavelength range 770 nm to 860 nm 1270 nm to 1540 nm to 1570 nm 1260 nm to 1620 nm
1355 nm
Receiver -17 dBm -20 dBm -24 dBm -24 dBm
sensitivity
Receiver overload -3 dBm -3 dBm -3 dBm 0 dBm
Note 1: Parameter values for SX SFP are characterized for 62.5 um 160 MHz-km MMF
Note 2: All parameter values in the above table achieve an optical system BER better than 1x10 -12.

OMX optical specifications

Table 7-48 lists the optical specifications for the OMX modules.
Table 7-48
OME optical specifications
Variant
OMX characteristics
NT0H32xE NT0H32xF
Connector type SC SC
Maximum total input power 17 dBm 17 dBm
Minimum return loss centre wavelength centre wavelength
+/- 0.25 nm +/- 0.25 nm
Passband 40 dB 45 dB
Minimum band isolation - drop 20 dB 35 dB
Minimum band isolation - thru out 12 dB 20 dB
Insertion loss (port to port) - add path 4.5 dB (maximum) 2.8 dB (maximum)
3.2 dB (typical) 2.1 dB (typical)
Insertion loss (port to port) - drop path 4.9 dB (maximum) 3.1 dB (maximum)
3.5 dB (typical) 2.4 dB (typical)
Insertion loss (port to port) - 1.2 dB (maximum) 1.0 dB (maximum)
pass-through per band 0.7 dB (typical) 0.7 dB (typical)
Electrical specifications
Table 7-49 to Table 7-53 lists the electrical specifications for the E1, DS3,
EC-1, DS1, and STM-1e interfaces.
Table 7-49
E1 electrical specifications
Parameter Value
Line rate 2048 kbit/s +/- 50 ppm
Line code HDB3
Impedance 75 ohm or 120 ohm
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)
Table 7-50
DS1 electrical specifications
Parameter Value
Line code AMI, AMIZCS, or B8ZS
Impedance 100 ohm ± 5%
Pulse amplitude 2.4 V to 3.6 V
Power level In a band not wider than 3 kHz, centered at 772 kHz, the power
level is between 12.6 and 17.9 dBm.
In a band not wider than 3 kHz, centered at 1544 kHz, the power
level is at least 29 dB below the power level centered at 772 kHz.
Cable distances Maximum 200 m (655 ft)
Line build-out Using NTN458Mx cables:
(LBO) ranges Short: 0 to 150 ft (45.7) m, Medium: 150 ft (45.7) m to 450 ft (137
m), Long: 450 ft (137 m) to 655 ft (200 m)
Table 7-51
DS3 electrical specifications
Parameter Value
Line code B3ZS or HDB3
Impedance 75 ohm ± 5%, unbalanced
Pulse amplitude 0.36 V to 0.85 V peak
Power level -4.7 dBm to +3.6 dBm
Cable distances Maximum 230 ft (70 m) using 735A cables (NTTC03xx)
Line build-out Using 735A cables (recommended) (NTTC03xx):
(LBO) ranges Short: 0 to 115 ft (35.0 m), Long: 115 ft (35.0 m) to 230 ft (70.1 m)
Table 7-52
EC-1 electrical specifications
Parameter Value
Line code B3ZS
Impedance 75 ohm ± 5%
Power level -2.7 dBm to +4.7 dBm
Cable distances Maximum 200 m (655 ft)
Line build-out Using 735A cables (recommended) (NTTC03xx):
(LBO) ranges Short: 0 to 115 ft (35.0 m), Long: 115 ft (35.0 m) to 230 ft (70.1 m)

Table 7-53
STM-1e electrical specifications
Parameter Value
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
Operating environment specifications
Table 7-54 outlines the OME6500 operating environment specifications.
Table 7-54
Operating environmental specifications for OME6500 system
Attribute Condition Test method and specification
o o
Normal operating 5 C to 40 C • Telcordia GR-63 CORE, Issue 2, April 2002
temperature (41oF to 104oF) (NEBS)
Short term operating -5oC to 55oC • ETSI EN 300 019-1-3 v2.1.0 (2001-12)
temperature (23oF to 131oF)
(not more than 96 consecutive
hours and a total of not more
than 15 days in a year)
Normal operating 5% to 85% RH
humidity
Short term operating 5 to 90% RH but not to exceed
humidity 0.024 kg water/kg dry air
Temperature cycling -5oC to 55oC • Telcordia GR-63 CORE, Issue 2, April 2002
(23oF to 131oF) (NEBS)
at a rate of change of • ETSI EN 300 019-1-3 v2.1.0 (2001-12)
temperature of 30oC per hour
(54oF per hour)

Operating environmental specifications for OME6500 system
Attribute Condition Test method and specification
Operational altitude -60 m to 1800 m at 40oC (-197 • Telcordia GR-63 CORE, Issue 2, April 2002
ft to 5906 ft) and from 1800 m (NEBS)
to 4000 m at 30oC (5906 ft to
13123 ft)
Airborne indoor contaminant levels • Telcordia GR-63 CORE, Issue 2, April 2002
contaminants (NEBS)
Earthquake/seismic Zone 4 • Telcordia GR-63 CORE, Issue 2, April 2002
(NEBS)
Operational vibration 0.1 g (5 - 100 Hz, sinusoidal) • ETSI EN 300 019-1-3 v2.1.0 (2001-12)
• IEC 68-2-6 test Fc
• Telcordia GR-63 CORE, Issue 2, April 2002
(NEBS)
Fire resistance According to specification • Telcordia GR-63 CORE, Issue 2, April 2002
(NEBS)
Storage temperature -40 oC to 70oC • ETSI EN 300 019:1992 Class 1.2/2.3
(-40oF to 158oF) • Telcordia GR-63 CORE, Issue 2, April 2002
(72-hour duration at each (NEBS)
extreme)
Storage humidity Up to 95% relative humidity
(RH), non condensing
(for 96 hours at 95% RH)
Handling shock Packaged and unpackaged • Telcordia GR-63 CORE, Issue 2, April 2002
criteria (by weight) per (NEBS)
specification
Transportation 0.5 g (5-50 Hz) • Telcordia GR-63 CORE, Issue 2, April 2002
vibration 3 g (50-500 Hz) (NEBS)
Acoustic noise 60 dBA at 25oC (77oF), sea • Telcordia GR-63 CORE, Issue 2, April 2002
level (NEBS)
Illumination According to specification • Telcordia GR-63-CORE, Issue 2, April 2002
(NEBS)
Air flow specifications

Maximum fan speed:
390 cubic feet per minute (CFM) for all three fans (130 CFM per fan)
Normal fan speed (at ambient temperature with all fans in the cooling unit):
280 CFM for all three fans (93.3 CFM per fan)

Electromagnetic specifications
Table 7-55 lists the electromagnetic compatibility of the OME6500 network
element.
Table 7-55
Electromagnetic specifications for OME6500
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:2001
H-field: 10Hz to 30 MHz • EN 55022:1998
• FCC Part 15 Subpart B
• Telcordia GR-1089-CORE, Iss.3
Conducted emissions • EN 300 386:2001
10 Hz to 100 MHz • EN 55022:1998
power and signal cables • Telcordia GR-1089-CORE, Iss.3
• ETS 300 132-2:1996
• Bellcore GR-499-CORE, Iss.2
RF Immunity Radiated RFI • EN 300 386:2001
E-field: 10kHz to 10 GHz • Telcordia GR-1089-CORE, Iss.3
10 V/m • EN 55024:1998
Conducted RFI • EN 300 386:2001
10 Hz to 80 MHz • EN 55024:1998
power and signal cables • ETS 300 132-2:1996
• 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 • EN 300 386:2001
electrostatic discharge (ESD) air discharge up to 15 kV • Telcordia GR-1089-CORE, Iss.3
contact discharge up to 8 kV • Telcordia GR-78-CORE
• EN 55024:1998
Operational Condition: no effect occurs when the system is exposed to
the RF levels described in the specifications above.

Electromagnetic specifications for OME6500
Electromagnetic topic Attribute Test method and specification

Electrical fast transient (EFT) power and signal cables • EN 300 386:2001
4 kV - power and ground • Telcordia GR-1089-CORE, Iss.3
1 kV - signal • EN 55024:1998
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:2001
1.5 kV, 2/10 µs pulse • Telcordia GR-1089-CORE, Iss.3
0.5 kV, 1.2/50 µs pulse • EN 55024:1998
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 OME6500 complies with the safety requirements of the following
specifications:
• CAN/CSA-C22.2 No 60950-1/ UL 60950-1
• IEC/EN 60950-1:2001
• Telcordia GR-1089-CORE, Iss.3
Laser emission
The OME6500 meets the requirements of the following specifications:
• IEC/EN 60825-1:2001
• IEC/EN 60825-2:2004
• FDA 21 CFR 1040.10
The OME6500 is a class 1 laser product/optical fiber communications system.

Power and grounding specifications

The following section outlines the power and grounding specifications
DC input voltage ranges
The operational input voltage range for the OME6500 is -40 V dc to -75 V dc.
The OME6500 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 +75 V dc (the system does not function with a
reversed polarity supply).
The OME6500 automatically recovers when the input voltage returns to a

value exceeding the minimum voltage within a acceptable period of time and
without any manual intervention. During a recovery from a low voltage battery
condition, circuit packs recover between -42.5 V dc and -43.5 V dc (measured
at the OME6500 input terminals).
The OME6500 meets the specifications listed in Table 7-56.

Table 7-56
Power, grounding, and noise references
Topic References
Power • ANSI T1.315-2001, Voltage Levels for DC Powered Equipment

Used in the Telecommunications Environment, 2001
• Telcordia: GR-499-CORE, Transport Systems Generic
Requirements (TSGR): Common Requirements Issue 2,
December 1999
• BTR2511, issue 3, British Telecom Requirements for
Telecommunication Power Requirements
• FTZ 19, Issue 1, German Telecom Power Requirements
(Deutches Bundesposte Telekom, Germany)
• 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
• TP00344B, Spec 1550, Issue 1, Telecom Australia / Power
Interface Standards
• DS8171, Issue 2, 60 Hz and -48 V dc Power for DC Powered
Telecommunication Equipment, Bell Canada
• TELEBRAS 240-500-700, General Specifications for DC Powered
Telecommunication Equipment, Brazil

Power, grounding, and noise references
Topic References
Grounding • Nortel Networks Corporate Standard CS4122, Grounding of

Communications Systems
• 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 EE-2002, Earthing and Bonding of Telecommunication
Equipment in Telecommunication Centers
• ETSI ETS 300 253, Equipment Engineering (EE); Earthing and
bonding of telecommunication equipment in telecommunication
centres, January 1995
• RUS Telecom Engineering and Construction Manual, section 810
• TPH 2253, Telecom Australia (High Ohmic Power and Earthing
Guidelines)
• TP01115(U), (Telecom Australia)
• NFPA70, (US National Electrical Code)
• CSA 22.1, (Canadian Electrical Code)
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
• Telcordia: GR-499-CORE, Transport Systems Generic
Requirements (TSGR): Common Requirements Issue 2,
December 1999
• Telcordia: GR-1089-CORE, Electromagnetic Compatibility, Issue
2, Revision 1, February 1999

8-1
Ordering information 8-
ATTENTION
This chapter provides the ordering information for the new items introduced
in Optical Multiservice Edge 6500 Release 1.2. It is recommended to review
Ordering Information, 323-1851-151 which contains all orderable items
before ordering.
New items in Release 1.2

Table 8-1 lists the ordering codes for new items in Release 1.2 of Optical
Multiservice Edge 6500.
Table 8-1
Optical Multiservice Edge Release 1.2 new items
Description Order Code Notes

Bay equipment
DSM BIPs
DSM breaker interface panel, 2 x 100 A NTN458RA 1
Shelf brackets
EIA adapter rail kit, with 127 mm (5") setback for PTE2000-EEA NTRU0570 2
Shelf Installation Kit, ANSI/EIA (for imperial hardware) NTK509ZX 3
Shelf Installation Kit, ETSI (for metric hardware) NTK509ZY 4
2U BIP installation hardware
2U BIP Installation/Grounding Kit NTK599ZX 5
2U BIP Power Lug Kit 6AWG/16 mm sq 90 degree NTK599ZA 6
2U BIP Power Lug Kit 6AWG/16 mm sq Straight NTK599ZB 7
2U BIP Power Lug Kit 2AWG/35 mm sq 90 degree NTK599ZC 8
2U BIP Power Lug Kit 2AWG/35 mm sq Straight NTK599ZD 9
Planning Guide NTRN10BC Standard Rel 1.2 Iss 1 Apr 2005

8-2 Ordering information


Circuit packs, SFP/DPO modules, and associated hardware
Circuit packs
Processor SP Circuit Pack Kit, Release 1.2 NTZF01AJ 10
X-CONN 20G/20G VT1.5/VC-12 (20/20) Circuit Pack NTK557QA 11, 12
24xDS3/EC-1 Working Circuit Pack NTK543NA 13, 14
24xDS3/EC-1 Protection Circuit Pack NTK544NA 13, 14
SFP/DPO modules
GE 1000-BaseZX 1550nm XCT Enhanced SFP Module NTTP07FF 15
1.25 Gbit/s CWDM 1471 nm SFP Module NTK591LB 15
1.25 Gbit/s CWDM 1491 nm SFP Module NTK591MB 15
1.25 Gbit/s CWDM 1511 nm SFP Module NTK591NB 15
1.25 Gbit/s CWDM 1531 nm SFP Module NTK591PB 15
1.25 Gbit/s CWDM 1551 nm SFP Module NTK591QB 15
1.25 Gbit/s CWDM 1571 nm SFP Module NTK591RB 15
1.25 Gbit/s CWDM 1591 nm SFP Module NTK591SB 15
1.25 Gbit/s CWDM 1611 nm SFP Module NTK591TB 15
OC-3/STM-1 SR-0 (Multimode) 1310 nm Enhanced SFP Module NTTP02AD 16
OC-48/STM-16 CWDM 1471 nm SFP Module NTK590LH 17
OC-48/STM-16 CWDM 1491 nm SFP Module NTK590MH 17
OC-48/STM-16 CWDM 1511 nm SFP Module NTK590NH 17
OC-48/STM-16 CWDM 1531 nm SFP Module NTK590PH 17
OC-48/STM-16 CWDM 1551 nm SFP Module NTK590QH 17
OC-48/STM-16 CWDM 1571 nm SFP Module NTK590RH 17
OC-48/STM-16 CWDM 1591 nm SFP Module NTK590SH 17
OC-48/STM-16 CWDM 1611 nm SFP Module NTK590TH 17
OC-3/12/STM-1/4 SR1/I1.1_I4.1 1310 nm XCT Enhanced SFP Module NTTP04BF 16
STM-1e Enhanced SFP Module NTTP60AE 16, 18
DS3/EC-1 interface hardware
48xDS3/EC-1 I/O Panel Front (1:N or unprotected) NTK572CA 19
48xDS3/EC-1 I/O Panel Rear (1:N or unprotected) NTK572QA 20
Optical Multiservice Edge 6500 NTRN10BC Standard Rel 1.2 Iss 1 Apr 2005


DS1 service module hardware
DSM Shelf Kit (with LC connectors) NTN407AC 21
DSM 84xDS1 TM Circuit Pack (with LC connectors) NTN313AC 22
DSM Shelf Assembly NTN407MA 22, 23
Cables
DSM BIP cables
DSM BIP cable harness, 1 feed NTN458MU 24
DSM BIP cable harness, 5 feed NTN458ZB 25
DSM BIP cable harness, 8 feed NTN458ZD 26
DS1 cables
DS1 right angle cable assembly, 15.24 m (50 ft) NTN458MQ 27
DS1 right angle cable assembly, 30.48 m (100 ft) NTN458MR 27
DS3/EC-1 cables
Cable Assembly, Co-axial, mini-BNC, single, 10 m NTTC03AA 28
Cable Assembly, Co-axial, mini-BNC, single, 20 m NTTC03AB 28
Cable Assembly, Co-axial, mini-BNC, single, 30 m NTTC03AC 28
Cable Assembly, Co-axial, mini-BNC, single, 40 m NTTC03AD 28
Cable Assembly, Co-axial, mini-BNC, single, 50 m NTTC03AE 28
Cable Assembly, Co-axial, mini-BNC, single, 60 m NTTC03AF 28
Cable Assembly, Co-axial, mini-BNC, single, 70 m NTTC03AG 28
Cable Assembly, Co-axial, mini-BNC, 12 circuits, 10 m NTTC03CA 29
Cable Assembly, Co-axial, mini-BNC, 12 circuits, 20 m NTTC03CB 29
Cable Assembly, Co-axial, mini-BNC, 12 circuits, 30 m NTTC03CC 29
Cable Assembly, Co-axial, mini-BNC, 12 circuits, 40 m NTTC03CD 29
Cable Assembly, Co-axial, mini-BNC, 12 circuits, 50 m NTTC03CE 29
Cable Assembly, Co-axial, mini-BNC, 12 circuits, 60 m NTTC03CF 29
Cable Assembly, Co-axial, mini-BNC, 12 circuits, 70 m NTTC03CG 29
Cable Assembly, Co-axial, mini-BNC, 24 circuits, 10 m NTTC03EA 30
Cable Assembly, Co-axial, mini-BNC, 24 circuits, 20 m NTTC03EB 30
Cable Assembly, Co-axial, mini-BNC, 24 circuits, 30 m NTTC03EC 30
Cable Assembly, Co-axial, mini-BNC, 24 circuits, 40 m NTTC03ED 30



Cable Assembly, Co-axial, mini-BNC, 24 circuits, 50 m NTTC03EE 30
Cable Assembly, Co-axial, mini-BNC, 24 circuits, 60 m NTTC03EF 30
Cable Assembly, Co-axial, mini-BNC, 24 circuits, 70 m NTTC03EG 30
DS3/EC-1 connector kits
Connector Kit, Coax, BNC, Male/Plug, Free, 735A Cable, Qty 12 NTTC00AC 31
Connector Kit, Coax, BNC, Male/Plug, Free, 735A Cable, Qty 24 NTTC00AE 32
Connector Kit, Coax, BNC, Female/Jack, Flange Mount, 735A Cable, Qty 12 NTTC00AQ 33
Connector Kit, Coax, BNC, Female/Jack, Flange Mount, 735A Cable, Qty 24 NTTC00AS 34
Connector Kit, Coax, Mini-BNC, Male/Plug, Free, 735A Cable, Qty 12 NTTC00CB 35
Connector Kit, Coax, Mini-BNC, Male/Plug, Free, 735A Cable, Qty 24 NTTC00CD 36
Connector Kit, Coax, Mini-BNC, Female/Jack, Flange Mount, 735A Cable, NTTC00CP 37
Qty 12
Connector Kit, Coax, Mini-BNC, Female/Jack, Flange Mount, 735A Cable, NTTC00CR 38
Qty 24
DS3/EC-1 mini-BNC insertion/removal tool
Mini-BNC Insertion/Removal Tool A0554187 39
DS3/EC-1 single connectors
Connector Coax, BNC 75 ohm, Male, Straight Plug Crimp/Crimp for use with A0666932 40
735A Cable
Connector Coax, BNC 75 ohm, Female Straight, Bulkhead, Jack A0638987 40
Crimp/Crimp for use with 735A Cable
Connector Coax, Mini-BNC, 75 ohm, Male, Straight, Plug Crimp/Crimp for A0542679 40
use with 735A Cable
Connector Coax, Mini-BNC, 75 ohm, Female, Straight, Bulkhead, Jack N0031383 40
Crimp/Crimp for use with 735A Cable
STM-1e cables
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 10 m NTTC04AA 41
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 20 m NTTC04AB 41
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 30 m NTTC04AC 41
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 40 m NTTC04AD 41
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 50 m NTTC04AE 41
Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 60 m NTTC04AF 41


STM-1e single connectors
Connector Coax, BNC 75 ohm, Male, Straight Plug for use with RG179DT A0360953 42
Cable
Connector Coax, BNC 75 ohm, Female Straight, Bulkhead, Jack for use with A0678277 42
RG179DT Cable
Connector Coax, BT43 75 ohm, Male, Straight, Bulkhead DDF for use with A0620780 42
RG179DT Cable
Connector Coax, HDC43 Bulkhead Plug (Male) Crimp/Crimp, RG179/U, N0032563 42
DDF Mount, Single PC. Body
Connector Coax, DIN 1.0/2.3mm, Straight Cable Plug Crimp/Crimp 75 ohm N0032582 42
RG179/U
Software and licences
Software
OME6500 Release 1.2 software load on CD-ROM NTK562AJ 43
Site Manager OME6500 Release 1.2 Software CD NTNM34SC 44
Licences
OME6500 Release 1.2 Certificate NTK569AJ 45
OME6500 Release 1.2 Site Manager RTU NTNM34RC 46
OME6500 Release 1.2 Site Manager Upgrade RTU NTNM34NC 47
OME6500 UPSR/SNCP RTU NTK560BF 48
Documentation
Release 1.2 documentation (see Table 8-2 on page 8-9 for a list of documents in the NTP suite)
OME6500 Release 1.2 NTP library suite (paper) NTK565AJ
OME6500 Release 1.2 NTPs (interactive CD-ROM) NTK564AJ
OME6500 Release 1.2 NTPs (Helmsman CD-ROM) NTK564AZ
OME6500 Release 1.2 Planning Guide NTRN10BC
Site Manager OME6500 Release 1.2 Planning and Installation Guide NTNM34DC
CAPs
Software Upgrade to Release 1.2 from Release 1.1 NTRN38AA
SONET - Add an OME6500 to a linear chain NTRN68AB
SDH - Add an OME6500 to a linear chain NTRN68BB
SONET - Add an OME6500 to a BLSR NTRN68CA
SDH - Add an OME6500 to an MS-SPRing NTRN68DA



SONET - Add an OME6500 to a UPSR NTRN68EA
SDH - Add an OME6500 to an SNCP NTRN68FA
Note 1: This breaker interface panel provides four 20 A, one 15 A, and three 5 A circuit breakers to
power up to eight DSMs (depending on the power cable used). This breaker interface panel cannot be
used to power the OME6500 shelves.
Note 2: One EIA adapter rail kit is required for each PTE2000-EEA frame. These adapter rails change
the mounting hole spacing and pitch and allow collocation with other 19” standard equipment (for
example, DSM, CPL, fiber managers, and OMXs). The EIA rails reduce the center-to-center distance
between the mounting holes from 515 mm to 465 mm and change the pitch of the holes from 25 mm to
EIA standard pitch (0.625/0.625/0.500 in.). Requires brackets with 465 mm centre-to-centre mounting
holes, 127 mm setback, and EIA hole pitch (NTK509MC and NTK509MD).
Note 3: Use this kit when installing mounting bracket kits for 19" EIA or ANSI 23" frame deployments.
Kit includes all hardware for mounting one OME6500 shelf, cooling unit, and air plenum. Kit includes
screws, lock washers, tie-wraps, velcro, ground cable, cable lug connectors, and no-ox.
Note 4: Use this kit when installing mounting bracket kits for ETSI or PTE-2000 EEA frame
deployments. Kit includes all hardware for mounting one OME6500 shelf, cooling unit, and air plenum.
Kit includes screws, lock washers, tie-wraps, velcro, ground cable, cable lug connectors, and no-ox.
Note 5: The 2U BIP Installation Kit contains fasteners and cage nuts to mount the 2U breaker interface
panel to a variety of equipment frames/racks. It contains a length of cable and lugs to connect the 2U
BIP to office frame/rack ground.
Note 6: This 2U BIP Power Lug Kit contains four 90° lugs for connecting 6AWG or 16mm² cables (flex
or standard) between the BIP and the office power source. These lugs are used when routing the cables
from the 2U BIP back from the power landing area. This kit supports office power connections to the 2U
BIP for one OME6500 shelf.
Note 7: This 2U BIP Power Lug Kit contains four straight lugs for connecting 6AWG or 16mm² cables
(flex or standard) between the BIP and the office power source. These lugs are used when routing the
cables from the 2U BIP directly up from the power landing area. This kit supports office power
connections to the 2U BIP for one OME6500 shelf.
Note 8: This 2U BIP Power Lug Kit contains four 90° lugs for connecting 2AWG or 35mm² cables (flex
or standard) between the BIP and the office power source. These lugs are used when routing the cables
from the 2U BIP back from the power landing area. This kit supports office power connections to the 2U
BIP for up to two OME6500 shelves.
Note 9: This 2U BIP Power Lug Kit contains four straight lugs for connecting 2AWG or 35mm² cables
(flex or standard) between the BIP and the office power source. These lugs are used when routing the
cables from the 2U BIP directly up from the power landing area. This kit supports office power
connections to the 2U BIP for up to two OME6500 shelves.
Note 10: This kit includes one shelf processor, NTK555AA, and one NTK561AJ Release 1.2 software
load.
Note 11: This cross-connect has a fixed capacity of 20 Gbit/s with VT1.5/VC-12 switching granularity.
VT1.5/VC-12 capacity is 20 Gbit/s.
Note 12: To support VT1.5/VC-12 switching granularity, the optical interface circuit packs must be also
be capable of VT1.5/LO switching granularity (see Ordering Information, 323-1851-151).


Note 13: Requires DS3/EC-1 electrical interface hardware.
Note 14: This circuit pack requires the VT1.5/VC-12 cross-connect circuit packs (see Ordering
Information, 323-1851-151) if VT1.5 cross-connects are required on EC-1 facilities.
Note 15: This module is used with the data services interface circuit packs listed in Ordering
Information, 323-1851-151.
Note 16: This module is used with the OC-3/12/STM-1/4 optical interface circuit packs listed in Ordering
Information, 323-1851-151.
Note 17: This module is used with the OC-48/STM-16 SFP optical interface circuit packs listed in
Ordering Information, 323-1851-151.
Note 18: Contact Nortel Networks regarding the availability of this item.
Note 19: This panel provides for up to 48 DS3/EC-1 interfaces. Up to four panels can be fitted to the
optical/front electrical shelf.
Note 20: This panel provides for up to 48 DS3/EC-1 interfaces. Up to four panels can be fitted to the
optical/rear electrical shelf.
Note 21: This kit contains one DSM shelf assembly (NTN407MA) and two 84xDS1 TM circuit packs
(NTN313AC). Order this kit if 1+1 protection of the DSM 84xDS1 TM circuit packs is required.
Note 22: Order one DSM shelf assembly (NTN407MA) and one 84xDS1 TM circuit pack (NTN313AC)
if a DSM with a single unprotected DSM 84xDS1 TM circuit pack is required.
Note 23: The shelf assembly does not include the 84xDS1 TM circuit packs (NTN313AC). Shelf
assembly includes one DSM fan module (NTN355AA), one DSM extender pack (NTN31112), one DSM
OAM adaptor modules (NTN356AA), three DSM DS1 I/O module (NTN312AA), and one DSM ground
cable (NTN45060).
Note 24: One NTN458ZB cable harness supports A and B feeds for one DSM shelf connected to BIP
NTN458RA.
Note 25: One NTN458ZB cable harness supports A and B feeds for five DSM shelves connected to
BIP NTN458RA.
Note 26: One NTN458ZD cable harness supports A and B feeds for eight DSM shelves connected to
BIP NTN458RA.
Note 27: This cable assembly provides 28 100 ohm balanced DS1 connectors. Two cable assemblies
are required for every 28 DS1s (one for 28 DS1 in, and one for 28 DS1 out). The cables assembles are
terminated at one end only. You must order appropriate connectors for the open end of each cable
assembly.
Note 28: This cable provides a single DS3/EC-1 connector. The cable uses 735A coaxial cable. You
must order appropriate connectors for the open end of each cable assembly. Two cable assemblies are
required for every DS3/EC-1 interface.
Note 29: This cable provides twelve DS3/EC-1 connectors. The cable assembly uses 735A coaxial
cables. You must order an appropriate connector kit for the open end of each cable assembly. Two cable
assemblies are required for every 12 DS3/EC-1 interfaces.
Note 30: This cable provides 24 DS3/EC-1 connectors. The cable assembly uses 735A coaxial cables.
You must order an appropriate connector kit for the open end of each cable assembly. Two cable
assemblies are required for every 24 DS3/EC-1 interfaces.



Note 31: This kit contains 12 A0666932 field terminable connectors (BNC, 75 ohm, Male, Straight,
Plug) for the DS3/EC-1 cable assemblies (NTTC03xx).
Note 32: This kit contains 24 A0666932 field terminable connectors (BNC, 75 ohm, Male, Straight,
Note 33: This kit contains 12 A0638987 field terminable connectors (BNC, 75 ohm, Female, Straight,
Bulkhead) for the DS3/EC-1 cable assemblies (NTTC03xx).
Note 34: This kit contains 24 A0638987 field terminable connectors (BNC, 75 ohm, Female, Straight,
Bulkhead) for the DS3/EC-1 cable assemblies (NTTC03xx).
Note 35: This kit contains 12 A0542679 field terminable connectors (Mini-BNC, 75 ohm, Male, Straight,
Note 36: This kit contains 24 A0542679 field terminable connectors (Mini-BNC, 75 ohm, Male, Straight,
Note 37: This kit contains 12 N0031383 field terminable connectors (Mini-BNC, 75 ohm, Female,
Straight, Bulkhead) for the DS3/EC-1 cable assemblies (NTTC03xx).
Note 38: This kit contains 24 N0031383 field terminable connectors (Mini-BNC, 75 ohm, Female,
Straight, Bulkhead) for the DS3/EC-1 cable assemblies (NTTC03xx).
Note 39: Order one mini-BNC insertion/tool per site to assist inserting/removing the DS3/EC-1
mini-BNC connectors from the I/O panels.
Note 40: These are single field terminable connectors for the DS3/EC-1 cable assemblies
(NTTC03Ax/Cz/Ex).
Note 41: 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 42: These are single field terminable connectors for the STM-1e cable assemblies (NTTC04Ax).
Note 43: This code provides one copy of the OME6500 Release 1.2 software load (NTK561AJ) on a
CD-ROM, includes Site Manager software to deliver Site Manager installer to the shelf processor (for
delivery of Site Manager via the HTTP server).
Note 44: This code provides one copy of OME6500 Site Manager software for craft access to the
OME6500 and a copy of the Site Manager OME6500 Release 1.2 Planning and Installation Guide on
CD ROM.
Note 45: One OME6500 Release 1.2 Certificate is required for each OME6500 network element.
Note 46: One OME6500 Release 1.2 Site Manager RTU is required for each OME6500 shelf.
Note 47: One OME6500 Release 1.2 Site Manager Upgrade RTU is required for each OME6500 shelf
if upgrading the software from a previous release.
Note 48: One OME6500 UPSR/SNCP RTU is required for each OME6500 shelf supporting
UPSR/SNCP.
Table 8-2 lists the OME6500 NTPs.

Table 8-2
OME6500 NTPs
NTPs Document code

Planning Guide NTRN10BC
About the OME6500 library 323-1851-090
Ordering Information 323-1851-151
Installation 323-1851-201
Commissioning and Testing 323-1851-221
Security and Administration 323-1851-301
Provisioning and Operating Procedures 323-1851-310
Performance Monitoring 323-1851-520
Alarm and Trouble Clearing 323-1851-543
Module Replacement Procedures 323-1851-545

9-1
Technical assistance 9-
This chapter includes information on how to contact Nortel Networks for

technical assistance.
Table 9-1
Technical assistance topics Page
Technical support and information 9-2
Nortel web site 9-2
Field return information 9-3

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: North America:
For 24-hour emergency recovery or software upgrade 1-800-4NORTEL (1-800-466-7835)
support, that is, for:
• restoration of service for equipment that has been International:
carrying traffic and is out of service 001-919-992-8300
• issues that prevent traffic protection switching
• issues that prevent completion of software upgrades
For non-service-affecting problems: North America:
For 24-hour support on issues requiring immediate 1-800-4NORTEL (1-800-466-7835)
support or for 14-hour support (8 a.m. to 10 p.m. EST) Note: You require an express routing code
on upgrade notification and non-urgent issues.
(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.
Nortel web site

You can also contact us through the Nortel web site at: www.nortel.com.
Select the link Support.
Technical assistance 9-3
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:

9-4 Technical assistance
Field Return Information Form (continued)
Failure data
LED status:
Optical input power at the receive interface: __ dBm
Optical output power at the transmit interface: __ 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:
10-1
Appendix A: Data communications

planning 10-
This chapter provides an overview of Optical Multiservice Edge 6500

(OME6500) network data communications. Table 10-1 lists the topics covered
in this chapter.
Table 10-1
Topic Page
Public DCN connectivity 10-2
General DCN provisioning rules 10-4
OME6500 DCC communications 10-18
OSI data communications on the OME6500 10-21
DCN design examples 10-22
Dialup connectivity 10-65
Firewalls 10-66
Troubleshooting 10-67
Engineering guidelines 10-68
IP networks, addressing, and masks 10-70
IP routing protocols 10-74
Subnetting and supernetting - IP addressing examples 10-82
This Appendix provides information on typical DCN configurations/models

and provides some examples and guidance on provisioning different
configurations. For general information about the OME6500 data
communication architecture and features, refer to OAM&P description on
page 6-1.

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.
Public DCN connectivity

Connectivity of the OME6500 network element (NE) to a public DCN is
through the COLAN interface (10/100Base-T-RJ-45) located on the access
panel (AP).
OME6500 supports two basic DCN models, a public IP address model and a
private IP address model. The following sections provide general information
about the basic DCN models. Subsequent sections provide general
provisioning guidance and examples of DCN configurations.
• Public IP address model: all nodes have a unique IP address, addressable
from the DCN.
• Private IP address model: where a specific network element is allocated a
gateway IP address on the DCN and all other network elements are hidden
below this network element and supplied with an arbitrary set of IP
addresses. These network elements are visible through a tunnel between
the OSS and the gateway network element and the internal IP addresses are
not advertised to the DCN, but must be known by the OSS.
Public IP address model
The network configuration in Figure 10-1 shows all OME6500 network
elements and OAM interface ports (COLAN and ILAN) having a unique IP
address, addressable from the DCN and are part of the same address space.
Figure 10-1
Public IP address model
47.2.1.1/28 COLAN 47.1.1.2/32

47.2.1.2/28
47.1.2.1/30
Carrier
Access 47.1.1.3/32
DCN
OMEA OME6500
47.2.1.3/28 47.1.1.1/32
47.1.1.4/32
Site manager /28 is 255.255.255.240

/30 is 255.255.255.252
/32 is 255.255.255.255
In the example shown, all network elements fall in the 47.X.X.X address range
with the management systems being in a different address range. All network
elements are acting as IP routers for the whole network with PPP being used
as the data link layer across the DCC channels (section/RS or line/MS).
Private IP address model

The network configuration in Figure 10-2 shows a private IP address model
which provides a mechanism whereby the user is not required to assign unique
IP addresses to all the network elements. In this model, routers in the carrier
access DCN are being used to originate/terminate a static IP over IP tunnel.
This implies that the network elements and management system can be
configured with private IP addresses (in this case 10.5.1.X and 10.6.1.X
addresses) with another unique IP address being assigned to the external
Ethernet port on the gateway network element (10.5.2.2). As in the public IP
address model, all network elements are acting as IP only routers with PPP
across the DCC channels.
Figure 10-2
Private IP address model
Only 47.x.x.x addresses

visible to Carrier
Access DCN
GRE tunnel
10.6.1.2/28
COLAN 10.5.1.2/32
10.5.2.2/30
Carrier Access
DCN
OMEA 10.5.1.3/32
OME6500
10.6.1.3/28
10.6.1.1/28 10.5.2.1/30
47.1.1.1/30 10.5.1.1/32
Site Manager 10.5.1.4/32
OME6500 addresses visible

to Site Manager and OMEA:
10.5.1.1
10.5.1.2 /28 is 255.255.255.240
10.5.1.3 /30 is 255.255.255.252
10.5.1.4 /32 is 255.255.255.255

General DCN provisioning rules

This section provides general information about provisioning the DCN
parameters on an OME6500 network element. The parameters are provisioned
using the Comms Setting Management application in the Configuration
menu of Site Manager (see Provisioning and Operating Procedures,
323-1851-310 for details). Procedures associated with the provisioning of the
DCN parameters are also included in the Commissioning Assistant Tool
(CAT) available in the Tools menu of Site Manager.
The provisioning of DCN parameters is dependent on whether the OME6500
is a gateway or a non-gateway network element. For a gateway network
element, additional parameters need to be provisioned associated with the
connection to the external DCN. DCN design examples on page 10-22
provides example DCN configurations and associated provisioning details.
Note: The actual parameters that need to be configured depend on the
DCN configuration (see DCN design examples on page 10-22 for example
parameters).
Gateway network element

The sequence for provisioning the DCN parameters on a gateway network
element is:
1 Provision the circuitless IP address (NE-IP)
Select the Interfaces tab and select IP as the Interface type. Provision the
appropriate information for the NE IP (see IP addressing on page 10-7).
2 Provision the COLAN port
Select the Interfaces tab and select LAN as the Interface type. Enable the
appropriate COLAN port (COLAN-X port recommended) (see LAN ports
on page 10-10)
appropriate information for the COLAN port (see IP addressing on page
10-7).
3 Provision the IP routing table (if using Static routing between gateway and
external DCN)
Select the Routers tab and select IP Routing Table as the Router type.
Add a static route for the COLAN port (see IP routing table on page
10-13).
4 Provision manual area addresses (MAA) (if interworking with other OSI
products using different MAAs)
Select the Routers tab and select Upper Layer DCC as the Router type.
Add/delete the necessary manual area addresses (see Upper layer DCC on
page 10-14).
Note: The OME6500 has a default MAA of 490000. It is recommended

that the default MAA of 490000 is deleted if not required (you cannot
delete it if it is the only MAA).
5 Provision the iISIS router
Select the Routers tab and select IISIS Router as the Router type. Add
the iISIS router (see iISIS router on page 10-11).
6 Provision the OSPF router (if using OSPF between gateway and external
DCN).
Select the Routers tab and select OSPF Router as the Router type. Add
an OSPF router (see OSPF router on page 10-15).
7 Provision ILAN ports (if required)
appropriate ILAN port (see LAN ports on page 10-10).
appropriate information for the ILAN port (see IP addressing on page
10-7).
8 Provision DCC (on OC-n/STM-n ports directly connected to the remote
network elements)
Select the Interfaces tab and select Lower Layer DCC as the Interface
type. Add the appropriate DCC (section/RS or line/MS) and the protocol
(LAPD or PPP) for the associated OC-n/STM-n port (see Lower layer
DCC on page 10-13).
9 Provision GRE tunnels (if using tunnels between gateway network
element and management system)
Select the Interfaces tab and select GRE as the Interface type. Add the
OSI over IP or IP over OSI tunnels (GRE-IP-1 to 4, GRE-OSI-1 to 4) (see
GRE on page 10-16).
10 Provision iISIS circuits
Select the Routers tab and select IISIS Circuit as the Router type. Add
an IISIS circuit to each comms port provisioned on the network element
that requires iISIS routing (ILAN, COLAN, NE-IP, OC-n/STM-n DCC
ports, GRE tunnels) (see iISIS circuits on page 10-12).
Note: Do not provision IISIS circuits on the LAN-15 port unless using the
LAN-15 port to access another OME6500 on the network.
11 Provision OSPF circuits (if using OSPF between gateway and external
DCN)
Select the Routers tab and select OSPF Circuit as the Router type. Add
the OSPF circuit to each comms port provisioned on the network element
that requires OSPF routing (COLAN, ILAN, and NE-IP only) (see OSPF
circuits on page 10-16).

Non-gateway network element

The sequence for provisioning the DCN parameters on a non-gateway network
element is:
1 Provision the circuitless IP address (NE-IP)
appropriate information for the NE IP (see IP addressing on page 10-7).
2 Provision manual area addresses (MAA) (if interworking with other OSI
products using different MAAs)
Select the Routers tab and select Upper Layer DCC as the Router type.
Add/delete the necessary manual area addresses (see Upper layer DCC on
page 10-14).
Note: The OME6500 has a default MAA of 490000. It is recommended
that the default MAA of 490000 is deleted if not required (you cannot
delete it if it is the only MAA).
3 Provision the iISIS router

Select the Routers tab and select IISIS Router as the Router type. Add
the iISIS router (see iISIS router on page 10-11).
4 Provision ILAN ports (if required)
appropriate ILAN port.
appropriate information for the ILAN port (see IP addressing on page
10-7).
5 Provision DCC (on OC-n/STM-n ports directly connected to the remote
network elements)
Select the Interfaces tab and select Lower Layer DCC as the Interface
type. Add the appropriate DCC (section/RS or line/MS) and the protocol
(LAPD or PPP) for the associated OC-n/STM-n port (see Lower layer
DCC on page 10-13).
6 Provision iISIS circuits
Select the Routers tab and select IISIS Circuit as the Router type. Add
an IISIS circuit to each comms port provisioned on the network element
that requires iISIS routing (ILAN, COLAN, NE-IP, OC-n/STM-n DCC
ports) (see iISIS circuits on page 10-12).
Note: Do not provision IISIS circuits on the LAN-15 port unless using the
LAN-15 port to access another OME6500 on the network.
IP addressing
Each OME6500 shelf must have one IP address assigned to it for management
purposes. Typically, the IP address used to manage the OME6500 is the
circuitless IP address. The circuitless IP is designated NE-IP.
CAUTION
Circuitless IP (NE-IP) address
The circuitless IP must have a subnet mask of
255.255.255.255.
Note: It is not necessary to assign the NE-IP address if the OME6500

network element connects directly to the LAN via the COLAN and does
not require any routing protocol. However, if being managed by the
OMEA you must assign a NE-IP address to each OME6500 network
element.
Each Ethernet interface can be assigned a single IP address and subnet mask.
A gateway network element requires an IP address on a different subnet to the
NE-IP for the Ethernet interface connected to the external DCN.
ATTENTION
For all network elements, the NE-IP address and each Ethernet interface
(COLAN-A, COLAN-X, ILAN-IN, ILAN-OUT) with a (numbered) IP
address must be on a different subnet (ILAN interfaces are usually
unnumbered).
An unnumbered IP address (0.0.0.0) is assigned to optical ports automatically

when PPP DCC is enabled and the circuit is created. Do not change these
unnumbered IP addresses.
All IP addresses assigned to an OME6500 network element must be in

different subnets (unless using unnumbered, 0.0.0.0).
For general information on assigning IP addresses in a network, see IP

networks, addressing, and masks on page 10-70 and Subnetting and
supernetting - IP addressing examples on page 10-82.
Host-only mode
In a host-only mode, a circuit will only accept packets which terminate at its
IP address. Routing updates and packets to be forwarded through other circuits
will be dropped.
The host-only mode is configurable on all LAN ports (optical ports are always
off) and is relevant when using IP tunnels over a public network.

Non-routing mode
In the non-routing mode, a circuit does not forward routing update packets
through that interface.
IP addressing implementation rules
You must observe the following rules when you implement the IP addresses:
• Each network element must be assigned at least one IP address and subnet
mask, usually the circuitless IP (NE-IP) address.
Note: It is not necessary to assign the NE-IP address if the OME6500
network element connects directly to the LAN via the COLAN, does not
require any routing protocol, and is not managed by OMEA.
• All gateway network elements for a particular sub-network must be

connected to different IP sub-networks to ensure a fully redundant
solution.
• For redundant gateway network element configurations, it is
recommended that the management system (for example, OMEA) is in a
different IP sub-network than the OME6500 interfaces (including the
COLAN ports).
• If you need to change the NE-IP address (for example, if you enter an
invalid IP address/mask), in the IP option of the Comms Setting
Management application you must either:
— If the original NE-IP address is valid, use the Edit command to change
the NE-IP address. A shelf processor restart is not required.
— If the original NE-IP address is invalid (for example, has the incorrect
mask), you can either:
– use the Edit command (or the Delete and Enter commands) to
change the NE-IP address to the required address and then perform
a cold restart of the shelf processor.
– use the Edit command to change the NE-IP address to an unused IP
address and then use the Edit command again to change the NE-IP
address to the required address. A shelf processor restart is not
required.
If you do not follow one these methods, the new NE-IP address will not be
visible in the Routing Table and will not be visible when adding a new
node to a login profile (a manual entry will be required).
• When deleting and then re-adding IP addresses on the COLAN and ILAN
ports, you must restart the network element by performing a cold restart on
the shelf processor before the new (added) IP addresses become active.
• For a gateway network element, you must provision an IP address on at
least one of the COLAN ports on a different subnet to the NE-IP address.
The COLAN interface must be assigned an IP address in the same subnet
of the router port connected to the gateway network element.
• 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 OME6500 network that will
contain OM5000 network elements.
• The Craft LAN port (LAN-15) has a default IP address of 10.0.0.1 which
allows a local craft PC with an IP address configured (see DHCP on page
10-10) to access the network element. Nortel Networks recommends that
the default IP address of the LAN-15 port is not changed.
If you are using the LAN-15 port to access another OME6500 on the
network, the Host-only mode must be Off (default setting). In addition, you
must:
— connect the Craft PC to the OME6500 using the LAN-15 port and
assign a unique IP address to the LAN-15 port (each LAN-15 port
defaults to the same address of 10.0.0.1)
— remove the Craft PC from the OME6500 and manually set the IP
address of the Craft PC
— connect the Craft PC to the OME6500 using the LAN-15 port and
modify the DHCP information (see DCN example 2 - using OSPF with
two OME6500 gateway network elements in different OSPF areas on
page 10-27 for typical changes). This ensures that you do not have to
manually set the IP address of the Craft PC each time it is subsequently
connected.
— add an iISIS circuit on LAN-15
Note: You can also connect to the OME6500 using the serial port to assign
a unique IP address to the LAN-15 port and change the DHCP information.
Then re-connect using the LAN-15 port and add the LAN-15 circuit. This
means you do not have to manually set the IP address of the Craft PC.
• For ILAN ports, the port is used for connecting to collocated OME6500
network elements, OSI devices, or an external ISIS device. When
connecting to a collocated OME6500 network element, the IP address
should be unnumbered (0.0.0.0). When connecting to a collocated OSI
device, an IP address is not required.
• If using unnumbered (0.0.0.0) ILAN ports, the ILAN ports should only be
directly connected to other equipment (point-to-point) and not connected
through an Ethernet hub or switch. For connection of collocated OME6500
network elements, a ring connection of ILAN ports is recommended.

DHCP
OME6500 supports a dynamic host configuration protocol (DHCP) server on
the Craft Ethernet interface on the shelf processor (LAN-15). The DHCP
server:
• eliminates the need for the Craft user to manually assign an IP address to
the Craft PC when it is connected to the Craft Ethernet port
• facilitates moving the craft PCs to a Craft port on a different network
element, without having to worry about re-assigning an IP address to the
craft PC
The DHCP server supports Microsoft Windows DHCP clients.
Note: The DHCP server is only supported on the craft Ethernet port
(LAN-15 on the shelf processor).
The DHCP server is enabled by default and has the following default values:
• IP address: 10.0.0.2
• Netmask: 255.255.255.252
• Gateway address: 10.0.0.1 (default IP address of craft Ethernet port)
• Default lease period: 600 seconds (not provisionable)
• Maximum lease period: 7200 seconds (not provisionable)
LAN ports
The OME shelf supports five external Ethernet ports as follows:
• two 10/100BT COLAN ports on the access panel to interface to the
customer DCN.
• two 10/100BT ILAN ports on the access panel for inter-shelf
communications
• one 10/100BT craft port on the shelf processor
The LAN ports support both Ethernet 2 (IP) and ISO802.2 (OSI). Each LAN
port is configurable as half-duplex 10 Mbit/s, half-duplex 100 Mbit/s,
full-duplex 100 Mbit/s, full-duplex 100 Mbit/s, or Automatic.
Note: If you set the configuration to Automatic, auto-negotiation and
automatic medium-dependent interface cross-over (auto-MDIX) are
enabled. Auto-negotiation automatically senses the speed/mode settings of
the link. Auto-MDIX automatically senses what type of cable is connected.
If you set the LAN port configuration to Automatic, the link works with
either a straight-through or cross-over cable and the OME6500 LAN port
will behave as a DCE or DTE depending on what it is connected to. If the
LAN port configuration is not set to Automatic, the OME6500 LAN port
is a DCE and requires a cross-over cable.
LAN implementation rules

You must observe the following rules when you implement the LAN:
• By default, only the craft LAN port (LAN-15) is configured with the
configuration set to Automatic.
• For gateway network elements, at least one COLAN port should be
configured for connection to the customer DCN.
• It is recommended that the ILAN ports are used for connecting to
collocated OME6500 network elements, OSI devices, or an external iISIS.
When using the ILAN to connect to collocated network elements or OSI
devices:
— ensure that the port is enabled and the configuration is correctly set
(matches the device you are connecting to). If you disable
auto-negotiation, ensure that the correct type of Ethernet cable is used.
— if connecting to another OME6500 network element, set the IP address
of the ILAN port to 0.0.0.0 (netmask 255.255.255.255). If connecting
to an OM3000 or OM4000 network element or an OSI managed
device, do not set an IP address for the ILAN port.
— provision an iISIS circuit on the ILAN port (with neighbour protocol
supported override parameter set to Off).
• Do not add a LAN port unless the port will be connected otherwise LAN
alarms will be raised.
• If using unnumbered (0.0.0.0) ILAN ports, the ILAN ports should only be
directly connected to other equipment (point-to-point) and not connected
through an Ethernet hub or switch. For connection of collocated OME6500
network elements, a ring connection of ILAN ports is recommended.
iISIS router
Integrated ISIS (iISIS) is a routing protocol based on the OSI Intra-domain
routing protocol with IP specific extensions as specified in 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.
iISIS is used as the internal OME6500 DCN routing protocol and is available
on all interfaces except Auto-tunnel interfaces and the RS-232 ports. The iISIS
router allows the shelf processor to route messages across any LAN or DCC
port.
iISIS router implementation rules
You must observe the following rules when you implement the iISIS router:
• As iISIS is used as the internal DCN routing protocol, you must add an
iISIS router for each network element (gateway network elements and
non-gateway network elements).

• For a gateway network element, you must set up a redistribution list

(Static, OSPF) when the gateway network element connects to an external
DCN that does not support iISIS.
• When adding a redistribution list for an iISIS router, you must set the
metric (cost) of any OSPF or static route distribution entries to between 1
and 63.
• The iISIS router requires an upper layer DCC MAA.
• When adding an IISIS router (including deleting and re-adding the IISIS
router), you must perform a cold restart of the shelf processor for the
changes to be implemented.
iISIS circuits
An iISIS circuit links the LAN or DCC ports to the iISIS router.
CAUTION
Configuring LAN ports
If required, Ethernet ports must be configured for OSPF with an
IP address or iISIS/ISIS. Do not configure OSPF and
iISIS/ISIS on the same Ethernet port.
iISIS circuit implementation rules

You must observe the following rules when you implement the iISIS circuits:
• You must create an iISIS circuit on each provisioned interface you want
iISIS to run on (except Auto-tunnels and the RS-232 ports).
• Do not configure an iISIS circuit on the LAN-15 port unless using the
LAN-15 port to access another OME6500 on the network (see IP
addressing on page 10-7 for more information).
• Use the circuit default metric parameter to represent the speed/reliability
of the circuit. Recommended settings are:
— COLAN and ILAN ports: 4
— Line/MS DCC: 5
— Section/RS DCC: 6
— circuitless IP (NE-IP): 4
Note: These are the default settings.
• When provisioning an iISIS circuit on an ILAN port, you must ensure that
neighbour protocol supported override parameter is set to Off.
• When provisioning an iISIS circuit on an optical DCC port connected to
OSI managed networks elements (for example, Optical Metro 3000 and
Optical Metro 4000), you must ensure that neighbour protocol supported
override parameter is set to OSI.
Note: Settings for the Optical Metro 4000 OPE100 interworking are
undefined, contact Nortel Networks for more information.
IP routing table
The IP routing table provides details of the static and dynamic IP routing (see
Static and default routes on page 10-81 for more information). Use the static
routing option to add static routes.
IP routing table implementation rules
You must observe the following rules when you implement static routes in the
IP routing table:
• If static redistribution is being used, you must set up the static routing in
the IP routing table before setting up the iISIS router or OSPF router.
• To set up a default route, it is recommended that the IP subnet is set up with
a subnet mask of 255.0.0.0 (for example, IP subnet 47.0.0.0 and subnet
mask 255.0.0.0). Do use the default route of 0.0.0.0 (IP subnet 0.0.0.0 and
subnet mask 0.0.0.0) for iISIS.
Lower layer DCC
Each optical port can support communications on the section/regenerator
section (RS) interface or the line/multiplex section (MS) interface.
Each DCC interface can support either PPP (IP-based DCC datalink layer) or
LAPD (OSI-based DCC datalink layer).
For more information about DCC, see OME6500 DCC communications on

page 10-18.
Lower layer DCC implementation rules
You must observe the following rules when you implement the lower layer
DCC:
• One section/RS DCC per optical port and up to two line/MS DCC per
optical circuit pack are supported.
• Each optical port, the DCC can be configured as section/RS or line/MS.
• Each optical port can support PPP or LAPD. The default is PPP.
— When using DCC to connect to an OME6500 (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.
• If an optical port is configured for LAPD, the circuit is configured as
Automatic.

• If an optical port is configured for LAPD, the frame size can be configured
between 512 and 1492. The default is 1304. The LAPD frame size must be
set to the same setting at both ends of the optical link otherwise
communication problems can occur.
• Once a new DCC circuit has been provisioned, an iISIS circuit must be
added for this port.
• You must delete the associated iISIS circuit before deleting the DCC
circuit.
The supported options for the different network element types is as follows:
• OME6500
— Supported DCC: section/RS, line/MS, or off (default)
— L2 frame size: 512 to 1492 (default 1304)
— L2 side role: network, user, or automatic (default)
• OM4000 series
Note: The DCC supported is dependent on the circuit pack type, refer to
the Optical Metro 4000 documentation for details.
— L2 frame size: 512 (default, not configurable)
— L2 side role: automatic (default, not configurable)
• OM3000 series
— L2 side role: network, user, or automatic
• Optical Cross Connect HDX/HDXc
the Optical Cross Connect HDX/HDXs documentation for details.
— L2 side role: network, user, or automatic (default)
• Optical Cross Connect DX
the Optical Cross Connect DX documentation for details.
Upper layer DCC
The OME6500 requires OSI manual area addresses to interop with other OSI
products. The manual area addresses are used to form the NSAP address of
each network element in the OSI level 1 area.
Upper layer DCC implementation rules

You must observe the following rules when you add manual area addresses:
• You must have at least one manual area address, you cannot delete a
manual area address if it is the only one in the list.
• The default manual area address is 490000.
• Up to three manual area addresses can be provisioned.
• If a new manual area address is provisioned, it is recommended that the
default manual area address of 490000 is deleted if not required.
Note: The routing table supports a maximum of 150 nodes (IS and ES) in
a level 1 area. A Routing Table Overflow alarm is raised if the 150 limit is
exceeded.
OSPF router
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.
OME6500 supports OSPF routing on all LAN interfaces for interworking with
an external customer OSPF DCN.
For more information about OSPF, see IP routing protocols on page 10-74.
OSPF router implementation rules
You must observe the following rules when you implement the OSPF router:
• As iISIS is used as the internal DCN routing protocol, you must add an
OSPF router for each gateway network element that interfaces to an OSPF
network.
• It is recommended that the NE-IP address is used for the OSPF router ID.
• It is recommended that route summarization is set to On (default setting) if
using dual gateways on a fully robust external DCN network and Off if the
DCN network is not fully robust and therefore could be partitioned.
• For a gateway network element, you must set up a redistribution list
(Static, ISIS) with defines the IP subnet and submask of all the OME6500
network elements.
Note: You must also add an OSPF distribution list for the iISIS router to
distribute DCN routes to the other OME6500 network elements (see iISIS
router on page 10-11).

• If you require one gateway network element to act as the primary, the
primary gateway network element should have a metric a lot lower than a
secondary gateway network element.
OSPF circuits
An OSPF circuit links the LAN ports to the OSPF router.
CAUTION
Configuring LAN ports
If required, Ethernet ports must be configured for OSPF (IP
address) or iISIS/ISIS. Do not configure OSPF and iISIS/ISIS
on the same Ethernet port.
OSPF circuit implementation rules

You must observe the following rules when you implement the OSPF circuits:
• You must create an OSPF circuit on the LAN ports on which you want to
run OSPF on the gateway network element connected to the OSPF
network.
• Use a metric that is the same as the external router Ethernet port.
• The following parameters are dependent on the network implementation:
— Network area: OSPF area the OSPF circuit is in (defaults to backbone
area, 0.0.0.0)
— Area: determines type of area (Off [normal], NSSA, or Stub)
Note: NSSA and Stub areas are not supported in the current release.
• The following parameters are normally left at the default settings for most
network applications:
— Area default cost: 1 (default)
— Dead interval: 40 (default)
— Hello interval: 10 (default)
— Retransmit interval: 5 (default)
— Transmit delay: 1 (default)
— Priority: 1 (default)
GRE
Generic routing encapsulation (GRE) provides a standard method for
transporting one arbitrary network layer protocol over another arbitrary
network layer protocol (tunnelling). A tunnel is effectively a point-to-point
connection which allows packets to be enclosed/encapsulated within another
packet.
OME supports static tunnels and auto-tunnels:

• 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 (IP or OSI 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-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 the support iISIS.
GRE implementation rules
You must observe the following rules when you implement GRE:
• Up to 4 static tunnels can be configured for each protocol. For an OSI
tunnel (GRE-OSI-1 to 4), you must provision the destination OSI (NSAP)
address. For an IP tunnel (GRE-IP-1 to 4), you must provision the
destination IP address.
• The destination node/router must also be configured for tunnelling with the
destination address of the OME network element (normally the COLAN
port address).
ARP
Address resolution protocol (ARP) is used to map IP addresses to LAN
hardware addresses. The user can configure up to 10 static ARP entries for
hosts which do not support ARP. The static entries do not time-out.
FTP
File transfer protocol (FTP) is a standard internet protocol used for transferring
files across a network. This protocol uses a client/server architecture. Both an
FTP client and server are supported on the shelf processor of the OME.
The FTP protocol is used on the OME6500 platform to handle all file transfers
within the network element, between network elements, and between the
network element and the management system.
The user can enable/disable the FTP server and can configure the time before
an idle FTP session is disconnected.

PPP
Point-to-point protocol (PPP) is a data link layer protocol used to pass data
between two systems on behalf of the IP network layer protocol.
Note: For this release, only the magic number support PPP parameter can
be edited, the remaining parameters are set to the default settings. Refer to
Provisioning and Operating Procedures, 323-1851-310 for details of the
default settings.
Serial/RS-232
The OME supports two RS-232 ports:
• an RS-232 DCE craft access port located on the shelf processor.
• an RS-232 DTE port located on the access panel intended for a permanent
modem connection
Note 1: For this release, the serial/RS-232 parameters cannot be edited and
are set to the default settings.
Note 2: It is recommended that the serial port on a PC connected to the
OME6500 is set to either 9600 or 19200.
Telnet
Telnet is a user command and an underlying TCP/IP protocol for accessing
remote computers.
A Telnet client is supported on the shelf processor of the OME6500 which

allows login to other network elements.
The user can configure the maximum number of concurrent Telnet sessions
allowed and the time before an idle Telnet session is disconnected.
OME6500 DCC communications

The OME6500 uses an IP-based data communications infrastructure for
network element management and interworking with IP-managed network
elements. OME6500 also supports Open Systems Interconnection (OSI) based
infrastructures for interoperability with OSI-managed network elements.
The SONET/SDH optical interfaces support both section/RS and line/MS

DCC. Each DCC interface supports both PPP and LAPD with PPP being the
default.
Line/MS DCC provides a faster link than section/RS DCC. If an optical

facility is taken out-of-service, line/MS DCC is lost but section/RS DCC
remains up. Make sure that the settings at each end of the DCC links are the
same.
OME6500 interworking with IP-managed network elements

Because OME6500 uses an IP-based DCC infrastructure, the OME6500
network element interworks with IP-managed network elements by acting as
an IP router for the whole network. PPP is used as the data link layer across the
section/RS and line/MS DCCs. Figure 10-3 shows the OME6500 interworking
with IP-managed network elements.
Figure 10-3
OME6500 interworking with IP-managed network elements
NEs across
Managing
OME6500 NE
IP-managed
Carrier
Access
DCN
OME6500 IP-Managed NE
DCC
COLAN DCC
OME6500 routing IP-DCC

messages between
IP-Managed NE subtending IP-managed NEs
Provisioning OME6500 to interwork with IP-managed network elements

OME6500 supports both section/RS and line/MS DCC datalink layer settings
which enables interworking.
OME6500 interworking with OSI-managed network elements

The OME6500 provides a 4-layer OSI stack (ISO 802.3 encapsulation) for
interoperability with OSI-managed network elements. The following
scenarios are typical examples of OME6500 interworking with OSI-managed
network elements:
• OME6500 routing OSI messages between subtending OSI-based network
elements
• Managing OSI-managed network elements across OME6500 network
elements

Figure 10-4 shows the OME6500 interworking with OSI-managed network

elements.
Note: The configuration in Figure 10-4 assumes that the gateway network
element is not acting as a TL1 gateway (not supported). The gateway
network element will pass-through OSI management traffic but cannot be
used to access the OSI based network elements.
Figure 10-4
OME6500 interworking with OSI-managed network elements
NEs across
Managing
OME6500 NE
OSI-managed
Carrier
Access
DCN
OME6500 OSI-Managed NE
DCC
COLAN DCC
OME6500 routing OSI-DCC

messages between
OSI-Managed NE subtending OSI-managed NEs
Provisioning OME6500 to interwork with OSI-based DCC network elements

OME6500 provides the capability to manually configure the section/RS and
line/MS DCC datalink layer settings which enables interworking. OME6500
also provides the capability to manually configure the data link layer
parameters for LAPD and other appropriate parameters to ensure they line up
with the subtending equipment OSI parameters.
OSI System Ids are derived automatically from the OME6500 shelf MAC
address. The OME6500 supports three configurable manual area addresses
(MAAs). A default MAA of 49000 is assigned to an network element.
DCC protection
OME6500 supports the following protection schemes for the DCC interfaces:
• protected DCC (route diversity Off) where DCC comms follows traffic
• unprotected DCC (route diversity On) where DCC comms does not follow
traffic
The default value for route diversity defaults to On.
Note 1: For BLSR/MS-SPRing configurations, route diversity is always

on. Route diversity is not applicable to unprotected configurations.
Note 2: Protected DCC (route diversity off) is not supported on PPP DCC
links (only supported for LAPD DCC links). You cannot set route diversity
to off if either of the DCCs in the 1+1/MSP linear protection scheme is set
to PPP.
Protected DCC
Protected DCC (route diversity off) is only supported on 1+1/MSP linear
protection schemes. If the 1+1/MSP linear protection is unidirectional, the
DCC follows traffic regardless of the facility traffic is on, thus DCC traffic can
be on different facilities for the transmit and receive direction.
For protected DCC (route diversity off), you must provision two DCC circuits,
one for each port of the 1+1/MSP protection pair. DCC is sent on both working
and protection ports but only the receive DCC of the active port is selected.
With route diversity off, only the DCC associated with the active port is
alarmed.
Unprotected DCC
For unprotected DCC (route diversity on), you can provision one or two DCC
circuits for the 1+1/MSP protection pair. If you provision DCC on both
working and protection ports, DCC is transmitted and received on both ports.
With route diversity on, the DCC associated with the each port is alarmed
separately.
OSI data communications on the OME6500

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.

DCN design examples

This section describes different options available for designing a data
communications network containing OME6500 network elements. The
section covers the following examples:
• DCN example 1 - using static routing. Used for OME6500 networks with
a single gateway network element into a non-iISIS or non-OSPF network
(for example, external RIP protocol network).
• DCN example 2 - using OSPF with two OME6500 gateway network
elements in different OSPF areas. Used for redundant OME6500 networks
with two gateway network elements into an OSPF network via
non-backbone OSPF areas.
• DCN example 3 - using OSPF with two OME6500 gateway network
elements connected to the OSPF backbone area. Used for redundant
OME6500 networks with two gateway network elements into the OSPF
backbone area.
• DCN example 4 - using DCN tunnels. Used if IP address isolation is
required between the OME6500 network and the external DCN network.
• DCN example 5 - management of OM4000 network elements through
OME6500 network elements. Used where the OME6500 network is
between management system and the OM4000 network elements.
• DCN example 6 - management of OME6500 across non-OME 6500
network elements (using auto-tunnelling). Used when managing the
OME6500 network when part of the network contains non-OME6500
network elements.
• DCN example 7 - management of OM3500 network elements through
OME6500 network elements. Used where the OME6500 network is
between the OM3500 headend network element and the subtending
OM3500 network elements. Requires the OM3500 headend network
element to be collocated with gateway OM6500 network element and
connected with the ILAN interface.
• DCN example 8 - DCN drops to every OME6500 network element. Used
where the OME6500 network elements are all connected directly to routers
in the DCN.
• DCN example 9 - auto-tunnelling. Shows the creation of auto-tunnels over
an optical interface or LAN.
• DCN example 10 - OME6500/HDX interworking using HDX DCC
transparency and multiple OSI areas. Used when managing the OME6500
network when part of the network contains HDX/HDXc network elements
(using transparent DCC on the HDX/HDXc).
Note: For DCN interworking between the OME6500 and OME6110, refer
to the OME6100 Planning Guide.
DCN example 1 - using static routing

In this example (see Figure 10-5), one OME6500 network element is
connected to the external DCN and acts as the gateway network element for
the other OME6500 network elements. Static routes are added to the router for
each of the network element traffic to be routed through the gateway network
element.
Each OME6500 network element is assigned a circuitless IP address (NE-IP)

from the same subnet. The COLAN interface on the gateway network element
is assigned an IP address in the same subnet of the router port connected to the
gateway network element. Each NE-IP address is visible within the external
DCN.
The customer must assign unique IP addresses to the network elements from
their corporate IP addressing range if the DCN will exist in their corporate
network. If the DCN is a self-contained network, the assigned IP addresses
only need to be unique within the DCN itself.
Static routing is used between the OME6500 gateway network element and the
external DCN and requires the gateway network element to be configured with
a static IP route and static redistribution on the iISIS router.
PPP is used as the data link layer across the DCC for communication between
the OME6500 network elements.
This example does not provide redundant access to the OME6500 network in
case of DCN failure.
OME6500 provisioning details
Table 10-2 details the DCN parameters for the OME6500 network elements in
the DCN for the DCN example 1 configuration. See General DCN
provisioning rules on page 10-4 for general provisioning guidelines.
Note: For parameters not listed, use the default settings or leave blank.
Router provisioning information
The static routing must also be set up on the router (IP subnet 10.5.17.0, subnet
mask 255.255.255.248, next hop 10.6.1.2, cost 2).

Figure 10-5
DCN example 1 - Static routes with a single gateway network element
RADIUS X terminal
10.11.12.171 10.11.12.170
Subnet: 10.11.12.160
Subnetmask: 255.255.255.224
Broadcast: 10.11.12.191
OMEA Optical
10.11.12.168 Network
Manager
10.11.12.161
10.11.12.172/27
ROUTER
10.6.1.1/30
10.5.17.2/32
Subnet: 10.5.17.0
NE2 Subnetmask: 255.255.255.248
OME6500
NE1 NE3
COLAN-X
10.6.1.2/30
10.5.17.1/32 10.5.17.3/32
NE4
/27 is 255.255.255.224 10.5.17.4/32
/29 is 255.255.255.248
/30 is 255.255.255.252
/32 is 255.255.255.255
Table 10-2
DCN example 1 - OME6500 DCN provisioning details
Parameters NE1 NE2 NE3 NE4

1 Set up IP address
Add COLAN-X port Yes No No No

Add IP address on
COLAN-X port:
IP address 10.6.1.2 N/A N/A N/A
Netmask 255.255.255.252 N/A N/A N/A
Host only mode Off Off Off Off
Non-routing mode Off Off Off Off
Add IP address on
circuitless IP (NE-IP):
IP address 10.5.17.1 10.5.17.2 10.5.17.3 10.5.17.4
Netmask 255.255.255.255 255.255.255.255 255.255.255.255 255.255.255.255
2 Set up IP routing (see Note 1 and Note 2)
Add static IP route

(gateway NE only):
IP subnet 10.11.12.160 - -- -
Subnet mask 255.255.255.224 - - -
Next hop 10.6.1.1 - - -
Cost 2 - - -
Circuit Id COLAN-X - - -
Add iISIS router: Yes Yes Yes Yes
Router level Level-1 Level-1 Level-1 Level-1
L1 priority 64 64 64 64
Route summarization: On On On On
Provisioning Static redistribution - - -
IP subnet 10.11.12.160 - - -
Subnet mask 255.255.255.224 - - -
Metric 10 - - -
Metric type External - - -
3 Set up DCC (see Note 3)
Add DCC on:

OC-192/STM-64 in slot 5:
Carrier Line/MS Line/MS Line/MS Line/MS
Protocol PPP PPP PPP PPP



4 Set up internal (iISIS) routing
Add iISIS circuit for:

NE-IP:
Name NE-IP NE-IP NE-IP NE-IP
Circuit default metric 4 4 4 4
Neighbour protocols Off Off Off Off
supported override
DCC on OC-192 /STM-64
in slot 5:
Name OC192/STM64-5-1 OC192/STM64-5-1 OC192/STM64-5-1 OC192/STM64-5-1
supported override
in slot 6:
supported override
Note 1: Only the gateway OME6500 network element requires static routing.
Note 2: The gateway OME6500 network element requires an iISIS router with static redistribution. The
non-gateway OME6500 network element just require a basic iISIS router without any redistribution.
Note 3: Assumes line/MS DCC on OC-192/STM-64 circuit pack is slots 5 and 6 is used to connect OME6500
network elements. Section/RS DCC could be used (as long as far end setting is same), see OME6500 DCC
communications on page 10-18.
DCN example 2 - using OSPF with two OME6500 gateway network

elements in different OSPF areas
In this example (see Figure 10-6), two OME6500 network elements are
connected to the external DCN and act as the gateway network element for the
other OME6500 network elements. OSPF is used on the COLAN interface of
gateway network elements for integration with the external DCN.

from the same subnet. The COLAN interface on the gateway network
elements are assigned an IP address in the same subnet of the router port
connected to the gateway network element. Each NE-IP address is visible
within the external DCN.
The gateway network element are configured as an OSPF autonomous system

boundary router (ABSR) they are located between the OSPF autonomous
system and a non-OSPF area (iISIS).
Note: The example shows the gateway network elements in different

OSPF areas but they could be connected to the same OSPF area if required
as the AS-External_LSA redistributed route into iISIS does not take
precedence to an iISIS learned route.
Both OSPF areas could be configured as NSSAs to prevent the OME6500

network elements form being flooded with AS_External_LSAs from the
backbone (from OME6500 network elements connected to the backbone via
different OSPF areas).
OME6500 provisioning information
OME6500 extra provisioning information for LAN-15 if being used to access
other network elements
Table 10-4 details extra provisioning details for configuring the craft port
(LAN-15) with non-default IP addresses with the host only mode set to off
which allows the craft user visibility of all the network elements in the
subsystem.

Note: Provisioning of the craft port (LAN-15) with non-default IP

addresses is also applicable to the other examples in this section.
Router configuration information
The OSPF routers (R1 and R2) are area border routers (ABR).
Figure 10-6
DCN example 2 - using OSPF with two OME6500 gateway network elements in different OSPF
areas
RADIUS OMEA
47.1.1.2/29 47.1.1.1/29
Subnet: 47.1.1.0/29
47.1.1.3/29
R3
NOTE:
IP addresses in DCN
Router DCN Network backbone not shown.
OSPF Backbone Area 0.0.0.0
R2
R1
47.1.1.17/30 47.1.1.21/30
COLAN-X OSPF OSPF COLAN-X

47.1.1.18/30 Area Area 47.1.1.22/30
0001 0002
NE1 NE4
DCC
47.1.1.32/32 47.1.1.35/32
DCC DCC
/29 is 255.255.255.248 NE2 DCC NE3

/30 is 255.255.255.252
/32 is 255.255.255.255 47.1.1.33/32 47.1.1.34/32
Table 10-3

1 Set up IP address
Add COLAN-X port Yes No No Yes

Add IP address on
COLAN-X port:
IP address 47.1.1.18 - - 47.1.1.22
Netmask 255.255.255.252 - - 255.255.255.252
Host only mode Off - - Off
Non-routing mode Off - - Off
Add IP address on
IP address 47.1.1.32 47.1.1.33 47.1.1.34 47.1.1.35
Netmask 255.255.255.255 255.255.255.255 255.255.255.255 255.255.255.255
2 Set up routing (see Note 1 and Note 2)

L1 priority 64 64 64 64
Provisioning OSPF redistribution - - OSPF redistribution
IP subnet (see Note 4) 47.0.0.0 - - 47.0.0.0
Subnet mask 255.0.0.0 - - 255.0.0.0
Metric 10 - - 20
Metric type External - - External
Add OSPF router: Yes No No Yes

OSPF Router Id 47.1.1.32 - - 47.1.1.35
Link state External - - External
Route summarization Off - - Off
Provisioning ISIS distribution - - ISIS distribution
IP subnet 47.1.1.32 - - 47.1.1.32
Subnet mask 255.255.255.248 - - 255.255.255.248
Metric 10 - - 20
Add DCC on:





NE-IP:
supported override
in slot 5:
supported override

in slot 6:
supported override
5 Set up external (OSPF) routing
Add OSPF circuit for

COLAN-X:
Name COLAN-X - - COLAN-X
Network area 0.0.0.1 - - 0.0.0.2
Cost 10 12
Area Off Off
Note 1: Only the gateway OME6500 network elements require an OSPF router.
Note 2: The gateway OME6500 network element requires an iISIS router with OSPF redistribution. The
Note 4: 47.0.0.0 is used for distribution into iISIS as it provides some resilience and aids diagnostics. You can
provision more specific distribution if you want to reduce routing updates.
Table 10-4
DCN example 2 - additional provisioning when using LAN-15 to access other network elements

1 Set up IP address
Change IP address
LAN-15:
IP address 10.10.10.1 10.10.10.5 10.10.10.9 10.10.10.13
Netmask 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252
Change DHCP settings:
DHCP server Yes Yes Yes Yes
IP address 10.10.10.2 10.10.10.6 10.10.10.10 10.10.10.14
Netmask 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252
Gateway address 10.10.10.1 10.10.10.5 10.10.10.9 10.10.10.13

LAN-15:
Name LAN-15 LAN-15 LAN-15 LAN-15
supported override
Note: Refer to IP addressing on page 10-7 for more information on using the LAN-15 port to access other network
elements.
DCN example 3 - using OSPF with two OME6500 gateway network

elements connected to OSPF backbone
In this example (see Figure 10-7), two OME6500 network elements are
connected to the OSPF backbone and act as the gateway network element for
the other OME6500 network elements. OSPF is used on the COLAN interface
of gateway network elements for integration with the external DCN.

from the same subnet. The COLAN interface on the gateway network
elements are assigned an IP address in the same subnet of the router port
connected to the gateway network element. Each NE-IP address is visible
within the external DCN.

The gateway network elements are configured as an OSPF autonomous system

boundary router (ABSR) as they are located between the OSPF autonomous
Figure 10-7
DCN example 3 - using OSPF with two OME6500 gateway network elements connected to the
OSPF backbone
RADIUS OMEA
47.1.1.2/29 47.1.1.1/29
Subnet: 47.1.1.0/29
47.1.1.3/29
R1 NOTE:
IP addresses in DCN
backbone not shown.
Router DCN Network
COLAN-X COLAN-X
47.1.1.18/30 47.1.1.22/30
NE1 NE4
DCC
47.1.1.32/32 47.1.1.35/32
DCC DCC
/29 is 255.255.255.248 NE2 DCC NE3

/30 is 255.255.255.252
/32 is 255.255.255.255 47.1.1.33/32 47.1.1.34/32
Table 10-5

1 Set up IP address

Add IP address on
COLAN-X port:
IP address 47.1.1.18 - - 47.1.1.22
Netmask 255.255.255.252 - - 255.255.255.252
Add IP address on
IP address 47.1.1.32 47.1.1.33 47.1.1.34 47.1.1.35
Netmask 255.255.255.255 255.255.255.255 255.255.255.255 255.255.255.255

L1 priority 64 64 64 64
IP subnet (see Note 4) 47.0.0.0 - - 47.0.0.0
Subnet mask 255.0.0.0 - - 255.0.0.0
Metric 10 - - 20
OSPF Router Id 47.1.1.32 - - 47.1.1.35
IP subnet 47.1.1.32 - - 47.1.1.32
Subnet mask 255.255.255.248 - - 255.255.255.248
Metric 10 - - 20
Add DCC on:

OC-192/STM-64 in slot 6




NE-IP:
supported override
in slot 5:
supported override
in slot 6:
supported override

COLAN-X:
Network area 0.0.0.0 - - 0.0.0.0
Cost 10 12
Area Off Off
Note 4: 47.0.0.0 is used for distribution into iISIS as it provides some resilience and aids diagnostics. You can
provision more specific distribution if you want to reduce routing updates.
DCN example 4 - using DCN tunnels

This design (see Figure 10-8) can be used when address isolation is required
between the OME6500 network elements and the external DCN networks. The
configuration requires extra routers to be installed at the OME6500 gateway
and management sites.
In this example, two OME6500 network elements are connected to the

external DCN and act as gateway network elements for the other OME6500
network elements. OSPF is used on the COLAN interface of gateway network
elements for integration with the external DCN.

gateway network element. Each NE-IP address is visible from the
management LAN but is not visible from the router DCN.
the private IP addressing range.
DCN tunnels are used between routers connected to the management systems
(OMEA) and the routers connected to the OME6500 gateway network
elements. All traffic to/from the OME6500 network elements and the
management systems are in the tunnels. In this example, NE2 and NE3 cannot
ping R1 and R2 without redistributing 10.6.1.30 and 10.6.1.5 into iISIS.
The gateway network element is configured as an OSPF autonomous system

boundary router (ABSR) as it is located between the OSPF autonomous
Note: OSPF areas 1 and 2 are interconnected via the backbone area with
R3 acting as the ABR. Alternatively, R1 and R2 can be ABRs with the
tunnel interfaces in the backbone area, this is the configuration assumed
for this example.

Figure 10-8
DCN example 4 - using DCN tunnels
RADIUS OMEA
10.11.12.1/29 10.11.12.2/29
Subnet: 10.11.12.0/29
R3 10.11.12.3/29
Any OSPF area
47.3.3.1/30 or other protocol
Router DCN
Network
47.1.1.1/30 47.2.2.1/30
R1 R2
10.6.1.1/30 10.6.1.5/30
COLAN-X OSPF OSPF COLAN-X

10.6.1.2/30 Area Area 10.6.1.6/30
0001 0002
NE1 NE4
DCC
10.5.1.1/32 10.5.1.4/32
DCC DCC
NE2 DCC NE3

/29 is 255.255.255.248
/30 is 255.255.255.252
10.5.1.2/32 10.5.1.4/32
/32 is 255.255.255.255
Table 10-6

1 Set up IP address

Add IP address on
COLAN-X port:
IP address 10.6.1.2 - - 10.6.1.6
Netmask 255.255.255.252 - - 255.255.255.252
Add IP address on
IP address 10.5.1.1 10.5.1.2 10.5.1.3 10.5.1.4
Netmask 255.255.255.255 255.255.255.255 255.255.255.255 255.255.255.255

L1 priority 64 64 64 64
Route summarization: On Off Off On
IP subnet 10.11.12.0 - - 10.11.12.0
Subnet mask 255.255.255.248 - - 255.255.255.248
Metric 10 - - 20
OSPF Router Id 10.5.1.1 - - 10.5.1.4
IP subnet 10.5.1.0 - - 10.5.1.0
Subnet mask 255.255.255.240 - - 255.255.255.240
Metric 10 - - 20
Add DCC on:

OC-192/STM-64 in slot 6




NE-IP:
supported override
in slot 5:
supported override
in slot 6:
supported override

COLAN-X:
Network area 0.0.0.1 - - 0.0.0.2
Cost 10 12
Area Off Off

R1 and R2 are configured as ABRs in this example (alternatively R3 could be
the ABR) with the tunnel interfaces in the backbone area and the LAN
interfaces to NE1 and NE2 in OSPF area 1 and OSPF area 2. R1, R2, and R3
each have an interface connected to the Router DCN which are assigned an IP
address from the Router DCN. For this example, it is assumed that this
interface is provided via Ethernet.
• R1 configuration (circuitless IP addresses not detailed)

— IP addresses:
– Ethernet interface connected to Router DCN: 47.1.1.1/30
– Ethernet interface connected to gateway network element:
10.6.1.1/30
— OSPF router
– ABR into OSPF backbone 0.0.0.0
– OSPF circuit on 10.6.1.1 in OSPF area 0.0.0.1
— static route
– destination: 47.0.0.0
– subnet mask: 255.0.0.0
– next hop: 47.1.1.2 (assumed, not shown in example)
— tunnel 1
– source: 47.1.1.1
– destination: 47.3.3.1 (R3 Ethernet port)
– mode: GRE IP
— IP addresses:
10.6.1.5/30
— OSPF router
— static route

— tunnel 2
– source: 47.2.2.1
– mode: GRE IP
— IP addresses:
– Ethernet interface connected to management LAN: 10.11.12.3/29
— OSPF router
– normal router in OSPF backbone 0.0.0.0
— static route
— tunnel 1
– source: 47.3.3.1
– mode: GRE IP
— tunnel 2
– source: 47.3.3.1
– mode: GRE IP
DCN example 5 - management of Optical Metro 4000 through OME6500

with IP only external DCN
This design (see Figure 10-9) is used when managing Optical Metro 4000
(OM4000) series network elements (or Optical TN-1C network elements)
through the OME6500 network elements. As the OME6500 has OSI
capability, the OM4000 network elements are managed natively once the
tunnel through the access DCN has been terminated.
In this example, a router at the EC-1 management site is used to tunnel the OSI
data over IP to the single gateway OME6500 network element. The gateway
OME6500 network element encapsulates the OSI packets which are then
routed through the other OME6500 network elements as native OSI packets to
the OM4000 network elements.

gateway network element. Each NE-IP address is visible within the external
DCN. The example assumes all NEs are in the default 49000 MAA.
The DCC interfaces between the OME6500 network elements are configured
for PPP. The DCC interfaces on the OME 6500 network element connecting to
the OM4000 network elements are configured for LAPD as OSI is being used.
The router (R2) at the management site must also support OSI and must be
configured with an OSI over IP tunnel as follows:
• Ethernet port connected to DCN (48.1.1.9): Host only mode
• Tunnel
— source address: 48.1.1.9
— terminating address: 48.1.1.13
— run iISIS routing
— support CLNS forwarding

Figure 10-9
DCN example 5 - Managing OM4000 through OME6500 with IP only external DCN
EC-1
OMEA
48.1.1.2/29
Tunnel Terminating IP
48.1.1.1/29 Addresses (EC-1 and OME6500)
IP 48.1.1.2 and 48.1.1.13
R2
48.1.1.3/29
48.1.1.9/30
IP Only DCN
OSPF Area 0
R1
48.1.1.14/30
OSPF
COLAN Area 1
48.1.1.13/30
NE1
48.1.1.41/32
iISIS routing 48.1.1.43/32
of IP & CLNP
NE2 over DCC
NE3 NE5
48.1.1.42/32 iISIS routing

of CLNP
OME6500 over DCC
NE4 NE6
OME4000
/29 is 255.255.255.248
/30 is 255.255.255.252
/32 is 255.255.255.255
Table 10-7
Parameters NE1 NE2 NE3

1 Set up IP address
Add COLAN-X port Yes No No

Add IP address on COLAN-X
port:
IP address 47.1.1.13 - -
Netmask 255.255.255.252 - -
Host only mode Off - -
Non-routing mode Off - -
Add IP address on circuitless IP
(NE-IP):
IP address 47.1.1.41 47.1.1.42 47.1.1.43
Netmask 255.255.255.255 255.255.255.255 255.255.255.255
Host only mode Off Off Off
Non-routing mode Off Off Off
Add iISIS router: Yes Yes Yes

Router level Level-1 Level-1 Level-1
L1 priority 64 64 64
Route summarization: On Off Off
Provisioning OSPF redistribution - -
IP subnet 48.1.1.0 - -
Subnet mask 255.255.255.248 - -
Metric 2 - -
Metric type External - -
Add OSPF router: Yes No No
OSPF Router Id 48.1.1.41 - -
Link state External - -
Route summarization Off - -
Provisioning ISIS distribution - -
IP subnet 48.1.1.40 - -
Subnet mask 255.255.255.248 - -
Metric 10 - -



Add DCC on:

Carrier Line/MS Line/MS Line/MS
Protocol PPP PPP PPP
OC-12/STM-4 in slot 1 port 1:
Carrier - - Line/MS
Protocol - - LAPD
L2 size (see Note 4) - - 512
Carrier - - Line/MS
Protocol - - LAPD
4 Add OSI over IP tunnel
Add tunnel:
Name GRE-IP-1 - -
Network area 48.1.1.2 - -

NE-IP:
Name NE-IP NE-IP NE-IP
Circuit default metric 4 4 4
Neighbour protocols supported Off Off Off
override
DCC on OC-192 /STM-64 in
slot 5:
Name OC192/STM64-5-1 OC192/STM64-5-1 OC192/STM64-5-1
override


slot 6:
override
DCC on OC-12 /STM-4 in slot 1
port 1:
Name - - OC12/STM4-1-1
Circuit default metric - - 5
Neighbour protocols supported - - OSI
override
port 1:
override
GRE-IP-1:
Name GRE-IP-1 - -
Circuit default metric 4 - -
Neighbour protocols supported Off - -
override
Add OSPF circuit for COLAN-X

Name COLAN-X - -
Cost 10 - -
Area Off - -
Note 1: Only the gateway OME6500 network element requires an OSPF router.
Note 2: The gateway OME6500 network element requires an iISIS router with OSPF
redistribution. The non-gateway OME6500 network element just require a basic iISIS router
without any redistribution.
Note 3: Assumes line/MS DCC on OC-192/STM-64 circuit pack is slots 5 and 6 is used to connect
OME6500 network elements and line/MS DCC on port1 of OC-12/STM-4 circuit pack is slots 1 and
2 is used to connect to OM4000 network elements. Section/RS DCC could be used (as long as far
end setting is same), see OME6500 DCC communications on page 10-18.
Note 4: If connecting to other network element types make sure that the L2 size (and line/MS or
section/RS selection) is the same on the other network elements and the OME6500 network
elements. The OM4000 network elements have a L2 size of 512 which cannot be configured. The
OME6500 network elements default to a L2 size of 1304. When connecting to OM4000 network
elements, you must change the settings on the OME6500 network elements to 512.

DCN example 6 - management of OME6500 through non-OME6500

network element
This design (see Figure 10-10) is used when managing OME6500 network
elements through a non-OME6500 network element. The example uses
Optical Metro 4000 (OM4000) series network elements but the design equally
applies to other network element type (for example, Optical Metro 3500 or
Optical TN-1C network elements).
Auto-tunnelling is used to package the IP packets for the subtended OME6500

network elements into OSI packets to traverse the OSI only network. Using the
GRE auto-tunnelling and the iISIS routing, the OME6500 network elements
can identify dual routers that can be used for the origination and termination
of dynamically tunnelled data.
In the example, NE2 (47.1.3.2) identifies that there is an OSI only network
portion between it and the destination network element. If an IP packet
destined for NE4 (47.1.3.4) arrives at NE2, NE2 encapsulates (auto-tunnels)
the IP information in an OSI PDU. The OSI PDU destination address will be
the OSI of NE4. All intermediate OM4000 network elements and OM6500
network elements will route the packet using iISIS routes to the destination.
This example uses the flat DCN model therefore public IP addresses are used
for the OME6500 NE-IP addresses which are visible in the external DCN.
the OM4000 network elements are configured for LAPD as OSI is being used.
This configuration does not require any special provisioning as
auto-tunnelling is used to traverse the OSI only network.
Figure 10-10
DCN example 6 - Managing OME6500 through non-OME6500 network elements
OMEA EC-1
47.1.1.1/24 47.1.1.2/24
DGW 471.1.254/24 DGW 47.1.1.254/24 OSI
IP OSI Area A
OSPF 47.1.1.254/24
Area 39.x..x.000A
0000 R3 L2 47.1.2.3/32
L2 L2
47.1.2.1/32 L1/L2 47.1.2.2/32
39.x..x.000B L2
L2 L2 39.x..x.000B Dual homed
R1 R2 leased bandwidth
47.1.2.4/32 47.1.2.5/32
39.x..x.000B L1 R4 R5 L1
39.x..x.000B
47.1.2.18/28 47.1.2.34/28
OSI OSI
OSPF
Area IP IP
0001
COLAN-X COLAN-X
47.1.2.17/28 47.1.2.33/28 COLAN-A
COLAN-A OSI Area B
NE1 L1 NE3
L1 L1
47.1.3.1/32 47.1.3.3/32
39.x..x.000B iISIS routing 39.x..x.000B
of IP & CLNP
OME6500 over DCC
NE2
L1
47.1.3.2/32
OME4000 39.x..x.000B ISIS routing
(or any OSI based NE) of CLNP over DCC.
IP is tunnelled. L1 39.x..x.000B
OSI Area B
/24 is 255.255.255.0
L1
/28 is 255.255.255.240 39.x..x.000B
L1
/29 is 255.255.255.248
/32 is 255.255.255.255 NE4
39.x..x.000B L1 39.x..x.000B
47.X.X.X = IP address
39.x.x.0000 = OSI area address
47.1.3.4/32

Table 10-8

1 Set up interfaces (LANs and IP addresses)
Add COLAN-X port Yes No Yes No

port:
IP address 47.1.2.17 - 47.1.2.33 -
Netmask 255.255.255.240 - 255.255.255.240 -
Host only mode Off - Off -
Non-routing mode Off - Off -
Add IP address on circuitless
IP (NE-IP):
IP address 47.1.3.1 47.1.3.2 47.1.3.3 47.1.3.4
Netmask 255.255.255.255 255.255.255.255 255.255.255.255 255.255.255.255
Add COLAN-A port Yes No Yes No
2 Set up MAAs
Edit MAAs
Manual Area Address 1 - - - -
Manual Area Address 2 39.528f.8000.0000. 39.528f.8000.0000. 39.528f.8000.0000. 39.528f.8000.0000.
0000.0002.000B 0000.0002.000B 0000.0002.000B 0000.0002.000B
Manual Area Address 3 - - - -

L1 priority 64 64 64 64
Route summarization: On Off On Off
Provisioning OSPF redistribution - OSPF redistribution -
IP subnet 47.1.1.0 - 47.1.1.0 -
Subnet mask 255.255.255.0 - 255.255.255.0 -
Metric 2 - 2 -
Metric type External - External -
Add OSPF router: Yes No Yes No
OSPF Router Id 47.1.3.1 - 47.1.3.4 -
Link state External - External -
Route summarization Off - Off -
Provisioning ISIS distribution - ISIS distribution -
IP subnet 47.1.3.0 - 47.1.3.0 -
Subnet mask 255.255.255.248 - 255.255.255.248 -
Metric 10 - 10 -
Metric type External - External -


Add DCC on:

Carrier Line/MS Line/MS Line/MS -
Protocol PPP PPP PPP -
Carrier Line/MS Line/MS Line/MS -
Protocol PPP PPP PPP -
Carrier - Line/MS - -
Protocol - LAPD - -
L2 size (see Note 4) - 512 - -
Carrier - Line/MS - Line/MS
Protocol - LAPD - LAPD
L2 size (see Note 4) - 512 - 512

NE-IP:
supported override
slot 5:
Name OC192/STM64-5-1 OC192/STM64-5-1 OC192/STM64-5-1 -
Circuit default metric 5 5 5 -
Neighbour protocols Off Off Off -
supported override
slot 6:
Name OC192/STM64-6-1 OC192/STM64-6-1 OC192/STM64-6-1 -
Circuit default metric 5 5 5 -
Neighbour protocols Off Off Off -
supported override
COLAN-A:
Name COLAN-A - COLAN-A -
Circuit default metric 4 - 4 -
Neighbour protocols Off - Off -
supported override



slot 1 port 1:
Name - OC12/STM4-1-1 - OC12/STM4-1-1
Circuit default metric - 5 - 5
Neighbour protocols - Off - Off
supported override
slot 6 port 1:
Name - OC12/STM4-2-1 - -
Circuit default metric - 5 - -
Neighbour protocols - Off - -
supported override

COLAN-X
Name COLAN-X - COLAN-X -
Network area 0.0.0.1 - 0.0.0.1 -
Cost 10 - 12 -
Area Off - Off -
Note 3: Assumes:
— line/MS DCC on OC-192/STM-64 circuit pack is slots 5 and 6 is used to connect OME6500 network elements
NE1, NE2, and NE3
— line/MS DCC on port 1 of OC-12/STM-4 circuit pack is slots 1 and 2 is used to connect NE2 to OM4000 network
elements
— line/MS DCC on port 1 of OC-12/STM-4 circuit pack is slot 1 is used to connect NE4 to OM4000 network
element.
— section/RS DCC could be used (as long as far end setting is same), see OME6500 DCC communications on
page 10-18.
Note 4: If connecting to other network element types make sure that the L2 size (and line/MS or section/RS
selection) is the same on the other network elements and the OME6500 network elements. The OM4000 network
elements have a L2 size of 512 which cannot be configured. The OME6500 network elements default to a L2 size of
1304. When connecting to OM4000 network elements, you must change the settings on the OME6500 network
elements to 512.
DCN example 7- management of Optical Metro 3500 through OME6500

This design (see Figure 10-11) is used when managing Optical Metro 3000
(OM3000) series network elements through the OME6500 network elements.
In this example, the headend OM3500 network element with the network
processor (NP) is collocated with the gateway OM6500 network element
(NE1) which also has a COLAN connection to the external DCN.
The OM6500 network elements forward the OSI only traffic between the
OM3500 headend network element and the OM3500 network element
subtended from the OME6500 network element (NE3).

gateway network element.
To provide address isolation in this example, DCN tunnels are used between
routers connected to the management systems (OMEA) and the routers
connected to the OME6500 gateway network element. All traffic to/from the
OME6500 network elements and the management systems are in the tunnels.
Private IP addresses are used for the OME6500 NE-IP addresses which are not
visible in the external DCN. The ILAN interface used to connect to the
OM3500 headend network element, this interface does not require an IP
address.
the OM3000 series network elements are configured for LAPD as OSI is being
used.

Figure 10-11
DCN example 7- Managing OM3500 through OME6500
MOA
OMEA
10.6.1.2/29
10.6.1.1/29
Subnet: 10.6.1.0/29
10.6.1.3/29 R2
48.3.3.1/30
Carrier
Access
DCN
48.2.2.1/30
48.1.1.14/29 R1
COLAN
NE1 48.1.1.15/29
COLAN ILAN ILAN
OM3500
48.1.1.13/29 with NP
10.5.1.1/32
iISIS routing 10.5.1.3/32
of IP & CLNP
NE2 over DCC
NE3
10.5.1.2/32 iISIS routing

of CLNP
OME6500 over DCC
OME3500
/29 is 255.255.255.248
/30 is 255.255.255.252
/32 is 255.255.255.255
Table 10-9

1 Set up IP address and LANs
Add COLAN-X port Yes No No

port:
IP address 48.1.1.13 - -
Netmask 255.255.255.252 - -
Host only mode Off - -
Non-routing mode Off - -
(NE-IP):
IP address 10.5.1.1 10.5.1.2 10.5.1.3
Netmask 255.255.255.255 255.255.255.255 255.255.255.255
Add ILAN-In port Yes No No

Route summarization: On On On
Provisioning OSPF redistribution - -
IP subnet 10.6.1.1 - -
Subnet mask 255.255.255.248 - -
Metric 2 - -
Add OSPF router: Yes No No
OSPF Router Id 10.5.1.1 - -
Link state External - -
Route summarization Off - -
Provisioning ISIS distribution - -
IP subnet 10.5.1.1 - -
Subnet mask 255.255.255.248 - -
Metric 2 - -



Add DCC on:

Carrier - - Section/RS
Protocol - - LAPD
Carrier - - Section/RS
Protocol - - LAPD

NE-IP:
override
slot 5:
override
slot 6:
override


port 1:
override
port 1:
override
ILAN-In:
Name ILAN-In - -
Circuit default metric 4 - -
Neighbour protocols supported Off - -
override
Add OSPF circuit for COLAN-X:

Name COLAN-X - -
Cost 10 - -
Area Off - -
Note 1: Only the gateway OME6500 network element requires an OSPF router.
Note 2: The gateway OME6500 network element requires an iISIS router with OSPF
redistribution. The non-gateway OME6500 network element just require a basic iISIS router
without any redistribution.
OME6500 network elements and section/RS DCC on port1 of OC-12/STM-4 circuit pack is slots 1
and 2 is used to connect to OM3500 network elements.
Note 4: The OM3500 and OME6500 network elements default to a L2 size of 1304. If you change
the settings on the OME6500 network elements you must also change the settings on the
OME3500 network elements.


R1 is configured as ABRs in this example (alternatively R2 could be the ABR)
with the tunnel interfaces in the backbone area and the LAN interfaces to NE1.
R1 and R2 each have an interface connected to the Router DCN which are
assigned an IP address from the Router DCN. For this example, it is assumed
that this interface is provided via Ethernet.

— IP addresses:
48.1.1.14/30
— OSPF router
— static route
— tunnel
– source: 48.2.2.1
– mode: GRE IP
— IP addresses:
– Ethernet interface connected to management LAN: 10.6.1.3/29
— OSPF router
– normal router in OSPF backbone 0.0.0.0
— static route
— tunnel
– source: 47.3.3.1
– mode: GRE IP
DCN example 8 - DCN drops to every OME6500 network element

In this example (see Figure 10-12), the OME6500 network elements are all
connected directly to routers in the DCN.
Each OME6500 network element is assigned a private circuitless IP address

(NE-IP), each of the NE-IP addresses must be unique. Each OME6500 acts as
a gateway network element and requires a COLAN interface to be assigned an
IP address in the same subnet of the router connected to the gateway network
element. A static default route is provisioned on each COLAN interface. The
COLAN ports are set to the Host only mode off.
Note: It is not necessary to assign an NE-IP address if not managed by the

OMEA and if DCC is not required.
The customer must assign unique IP addresses to the COLAN ports from their
corporate IP addressing range if the DCN will exist in their corporate network.
If the DCN is a self-contained network, the assigned IP addresses only need to
be unique within the DCN itself.
This example does not provide redundant access to the OME6500 network in
case of DCN failure.
In Figure 10-12, the DCC interfaces between the OME6500 network elements
are configured for PPP. If there are no DCC requirements (for example, there
are no subtending equipment on the OME6500 network elements that require
DCC to carry comms across the OME6500 network), there is no need to
configure the DCC circuits or associated iISIS circuits.
Table 10-10 details the DCN parameters for the OME6500 network elements
in the DCN for the DCN example 8 configuration. See General DCN

Figure 10-12
DCN example 8 - DCN drops to every OME6500 network element
OMEA
47.1.1.1/29
R4
DCN
R1 R3
R2
COLAN-X
47.1.1.22/30
NE2
COLAN-X COLAN-X
47.1.1.18/30 47.1.1.26/30
10.5.17.2/32
NE3
NE1
10.5.17.1/32 10.5.17.3/32
OME6500
/29 is 255.255.255.248
/30 is 255.255.255.252
/32 is 255.255.255.255
Table 10-10

1 Set up IP address
Add COLAN-X port Yes Yes Yes

port:
IP address 47.1.1.18 47.1.1.22 47.1.1.26
Netmask 255.255.255.252 255.255.255.252 255.255.255.252
TTL 90 90 90
Host only mode On On On
(NE-IP):
IP address 10.5.17.1 10.5.17.2 10.5.17.3
Netmask 255.255.255.255 255.255.255.255 255.255.255.255
2 Set up IP routing (see Note 1)
Add static IP route (gateway NEs

only):
IP subnet 47.0.0.0 47.0.0.0 47.0.0.0
Subnet mask 255.0.0.0 255.0.0.0 255.0.0.0
Next hop 47.1.1.17 47.1.1.21 47.1.1.25
Cost 2 2 2
Circuit Id COLAN-X COLAN-X COLAN-X
Route summarization: Off Off Off
Provisioning - - -
IP subnet - - -
Subnet mask - - -
Metric - - -
Metric type - - -
Add DCC on:





NE-IP:
override
slot 5:
override
slot 6:
override
Note 1: The gateway OME6500 network elements require static routing.

OME6500 network elements. Section/RS DCC could be used (as long as far end setting is same),
see OME6500 DCC communications on page 10-18.
DCN example 9 - auto-tunnelling

In these examples (see Figure 10-13 and Figure 10-14) auto-tunnelling is used
to package the IP packets for the subtended OME6500 network elements into
OSI packets to traverse the OSI only network. Using the GRE auto-tunnelling
and the iISIS routing, the OME6500 network elements can identify dual
routers that can be used for the origination and termination of dynamically
tunnelled data.
In Figure 10-13, an IP over OSI auto-tunnel is created between NE1 and NE3
over the DCC on the optical interfaces to the OSI network element (for
example, Optical Cross Connect HDX).
In Figure 10-14, an IP over OSI auto-tunnel is created between NE1 and NE3
over the LAN (using the ILAN port on the OME6500) to the OSI network
element and then the DCC on the optical interface to NE3.
No special provisioning is required for the OME6500 network element in these
configurations as the auto-tunnels are created without user intervention. The
following are some general provisioning information (refer to the other DCN
examples in this chapter for provisioning details on similar configurations):
• In Figure 10-13, the DCC on the OME6500 and the OSI network element
must be configured for LAPD (with same L2 frame size). The neighbour
protocols supported override parameter for the iISIS circuits on the DCC
of NE1 and NE2 must be set to OSI.
• In Figure 10-14, the ILAN must be configured on NE1 and an iISIS circuit
added for the ILAN (the neighbour protocol supported override parameter
for the ILAN must be set to Off). In addition, the DCC on the OME6500
and the OSI network element must be configured for LAPD (with same L2
frame size).

Figure 10-13
DCN example 9 - auto-tunnelling over DCC
EMS
47.1.1.1/24
DGW 47.1.1.254/24
47.1.1.254/24
R2 47.1.2.3/32
Router DCN Network

OSPF Backbone Area 0.0.0.0 NOTE:
IP addresses in DCN
backbone not shown.
R1 47.1.2.1/32
47.1.2.18/28
IP & OSPF
OSPF
COLAN-X Area
47.1.2.17/28 0001
NE1 DCC
47.1.3.1/32
OSI
Network Element
OME
DCC DCC
/24 is 255.255.255.0 iISIS
/28 is 255.255.255.240
/32 is 255.255.255.255
IP over OSI NE2

Autotunnel 47.1.3.2/32
Figure 10-14
DCN example 9 - auto-tunnelling over the LAN
EMS
47.1.1.1/24
DGW 47.1.1.254/24
47.1.1.254/24
R2 47.1.2.3/32
Router DCN Network

R1 47.1.2.1/32
47.1.2.18/28
IP & OSPF
OSPF
COLAN-X Area
47.1.2.17/28 0001
NE1 ILAN 47.1.2.19/28
47.1.3.1/32
OSI
Network
Element
OME
DCC DCC
/24 is 255.255.255.0 iISIS
/28 is 255.255.255.240
/32 is 255.255.255.255
IP over OSI
Autotunnel NE2
47.1.3.2/32

DCN example 10 - OME6500/HDX interworking using HDX DCC

transparency and multiple OSI areas
This example (see Figure 10-15) shows the OME6500 interworking with
Optical Cross Connect HDX/HDXc using the DCC transparency feature on
the HDX/HDXc and multiple OSI areas. The DCC transparency feature on the
HDX is used to transparently connect OME6500 network elements that are in
different OSI areas than the HDX.
The network consists of three OSI areas as follows:

• OSI Area 1 (39....0001): OME6500 NE1, NE4, and NE5
• OSI Area 2 (39....0002): OME6500 NE2, NE6, and NE7 and the HDX
• OSI Area 3 (39....0003): OME6500 NE3, NE8, and NE9
For OSI Area 1, the DCC from/to the OME6500 gateway network element is
transparently connected on the HDX (which is in OSI Area 2) to the
subtending OME6500 rings. A separate OCn/STMn connection is available on
the OME6500 gateway network element to each subtending ring, therefore the
DCC is transparently connected directly through the HDX.
For OSI Area 2, the OME6500 network elements are in the same OSI area as
the HDX therefore IP over OSI auto-tunnels are created over the LAN and the
DCC (see DCN example 9 - auto-tunnelling on page 10-61 for details).
For OSI Area 3, the DCC from/to the OME6500 gateway network element is
transparently connected on the HDX (which is in OSI Area 2) to the
subtending OME6500 rings. As there is not an separate OCn/STMn
connection from the OME6500 gateway network element to each of the
subtending rings, the DCC is daisy-chained between the subtending rings on
the HDX so that all the OME6500 network elements have DCC connectivity
to the OME6500 gateway network element.
No special provisioning is required for the OME6500 network element in these
configurations (refer to the other DCN examples in this chapter for
provisioning details on similar configurations).
Figure 10-15
DCN example 10 - OME6500/HDX interworking using HDX DCC transparency and multiple OSI
areas
EMS
47.1.1.1/24
DGW 47.1.1.254/24
R2 47.1.1.254/24
47.1.2.3/32
Router DCN Network

R1
47.1.2.18/28
OSI 1
OSI 2 OSI 3
OSPF IP
Area
0001 COLAN-X
COLAN-X COLAN-A 47.1.2.21/28
47.1.2.20/28
COLAN-X COLAN-A COLAN-A
47.1.2.17/28 47.1.4.2/32
39...0002
NE1 ILAN NE2 47.1.5.3/32
47.1.3.1/32 39...0003
39...0001 HDX
39...0002 NE3
OC-n/STM-n connection Single OC-n/STM-n
to HDX required for each connection to HDX
subtended ring required with DCC
daisy-chained between
rings on HDX
47.1.5.9/32
47.1.3.4/32 39...0003
39...0001
NE4 NE9
47.1.5.8/32
47.1.3.5/32 39...0003
NE5 39...0001 47.1.4.6/32 47.1.4.7/32 NE8
39...0002 39...0002
NE6 NE7
OME
/24 is 255.255.255.0
DCC over optical /28 is 255.255.255.240
/32 is 255.255.255.255
IP over OSI autotunnel
Transparant DCC connection
Dialup connectivity
The OME6500 also supports connectivity to the OME6500 network element
via dialup. Dialup access allows for remote access to the OME6500 network
via an analog line. Dialup access is also required in order to receive proper
assistance from Nortel Networks support teams. Dial-up access is only
available to access the local network element, you cannot directly reach other
network elements on the DCN from the RS-232 port.

Note: You can reach remote network elements using the nested Telnets
functionality available from the General Utilities Menu of the command
line interface available when breaking out from a TL1 session.
This method requires an externally callable telephone line and an external

modem to connect to the DTE interface (DB-9 male connector) located on the
access panel of the OME6500 network element. The modem needs to be
Hayes-compatible (able to respond to AT command set) and there must be an
ability to locally provision the modem. To hook up the modem to the
OME6500 network element, an RS-232 cable is needed. The cable needs to be
DB9 female connector on the side connecting to the OME6500 network
element and to whatever specification to connect to the modem.
Firewalls
The following ports must be passed through any firewall between the
management systems and the OME6500 network:
• TCP
— 20, 21 - FTP ports used to deliver software and backup and restore
configurations and for upgrades.
— 23 - Telnet port used to telnet to the OME6500 and to support remote
debug access.
— 80 - Used by HTTP server when downloading Site Manager software
to a PC. HTTP is also used for downloading the OAM Data file during
Site Manager Login. See Note 3 and Note 4.
— 8888 - Used for remote debug access to OME6500 by Nortel
Networks.
— 10001, 10003 - Used by the OMEA to manage the OME6500
• UDP
— 67, 68 - Used by DHCP server
— 1812 - Used by RADIUS
Note 1: Ports 20, 21, 10001, and 10003 are mandatory. If access to ports
23 and 8888 are not provided, users can Telnet using port 10001 to break
in to debug access.
Note 2: OME6500 initiates FTP (ports 20 and 21) sessions. All other
sessions are requested by the management platforms. Make sure that
opened firewall ports are in the correct direction.
Note 3: Firewall on port 80 (HTTP server) is not required if Site Manager
software will only be loaded to a local PC via the craft port.
Note 4: OAM Data is only downloaded by Site Manager on Login if it is
not already available locally (once downloaded it is stored locally in the
Site Manager installation directory on a per release basis). If users install
and initially log into the network elements within the firewall (or directly
connected to the network element LAN port), the HTTP port can be
blocked on the firewall without impacting functionality.
Note 5: For more information on firewalls for OMEA, refer to the OMEA
planning guide.
Troubleshooting
The following section provides some DCN troubleshooting information for
some common scenarios.
Note: For information and procedures for the DCN troubleshooting tools
provided in the General Utility Menu, see Provisioning and Operation
Telnet and ping successful to all DCC connected NE-IP addresses
If Telnet and ping are successful to all DCC connected NE-IP addresses, the
DCN is correctly provisioned on all the OME6500 network elements.
Telnet and ping successful to head-end COLAN and NE-IP addresses only
If Telnet and ping are successful to the head-end COLAN and NE-IP addresses
only, there could be a DCN issue between the OME6500 network elements due
to either a DCC or route distribution issue.
Verify:
• the DCC (or ILAN) provisioning and use the IP Routing Table to ensure
that the NE-IP addresses are being learnt over the iISIS.
• the route distribution to ISIS on the head-end and attempt a ping from
OME6500 to OME6500 network element.
Telnet and ping successful to head-end COLAN IP address only
If Telnet and ping are successful to the head-end COLAN IP address only,
there could be a DCN issue with the head-end distribution of NE-IP addresses
to the customer DCN.
Verify the route distribution at the head-end OME6500 network element.

Telnet and ping unsuccessful to head-end COLAN IP address
If Telnet and ping are unsuccessful to the head-end COLAN IP address, there
could be physical problems at the head-end.
Verify at the head-end network element that:

• the COLAN port has been enabled
• the correct Ethernet cable is being used if the COLAN configuration is not
Automatic
• the maintenance interface card (MIC) is fully seated if COLAN-X is being
used

Engineering guidelines
The following are DCN engineering guidelines for OME6500 Release 1.2. For
the following guidelines, a gateway network element (GNE) subnet is a
complete DCN network of network elements accessed through a GNE with
COLAN access. The term GNE subnet applies to both the network elements
accessed via DCC from the GNE and the GNE.
ATTENTION
For configurations that exceed the following guidelines, contact Nortel
Networks for assistance.
• iISIS
— Maximum of 150 ISs and ESs nodes per OSI area
— Maximum of 200 L1 LSPs per OSI area
— Average of 10 adjacencies per L1 IS.
— Maximum of 50 adjacencies per L1 IS
— Recommended iISIS metrics:
– LAN: 4
– Line/MS DCC: 5
– Section/RS DCC: 6
• OSPF
— Maximum of 100 per OSPF area
• OSI
— Maximum of 150 OSI routes (NSAP) in the L1 routing table
• IP
— The OME6500 IP routing table supports 300 IP routes in total
— Maximum of 90 hops from OMEA to OME6500
• Physical (DCC)
— Maximum of 50 DCCs per network element
— Maximum of two line/MS DCCs per circuit pack
• DCN throughput
— Maximum of 72 subtended OM3000, OM4000, or OME6110 network
elements
— Maximum of eight subtending OME6500 network elements through a
headend shelf over DCC or through the ILAN port
— Maximum of 73 nodes in a GNE subnet (one OME6500 network
element and 72 non-OME6500 network elements)
Note 1: When managing subtended OME6500 and

OM3000/OM4000/OME6110 network elements from the same OME6500
gateway network element, each OME6500 network element should be
counted as nine OM3000/OM4000/OME6110 network elements in order
to calculate the maximum combination supported.
Note 2: The DCN throughput limits apply to any OME6500 network
element which has DCN throughput from subtending network elements,
even if the OME6500 is not the gateway network element for the
subtending equipment.
• DSM support
— A single network element can support a maximum of 16 DSMs.
— A GNE subnet can support a maximum of 64 DSMs.
— A network element with six or more DSMs requires COLAN access.
• Telnet sessions (see Note 1)
— Maximum of 36 Telnet sessions with autonomous output (AO)
message reporting enabled for a GNE subnet (four Telnet sessions per
OME6500 network element). This maximum can be increased if
OM3000/OM4000/OME6110 network elements are substituted for the
OME6500 network elements (maximum of two TL1/CLUI sessions
per OM3000/OM4000/OME6500 network element). For example, a
GNE subnet with one gateway OME6500 network element, seven
subtending OME6500 network elements, and nine
OM3000/OM4000/OME6500 network elements can have a maximum
of 50 Telnet sessions (four Telnet sessions for each of the eight
OME6500 network elements and two TL1/CLUI sessions for each of
the nine OM3000/OM4000/OME6500 network elements).
— If more than four Telnet sessions per OME6500 network element are
required, AO message reporting should be disabled for the additional
Telnet sessions. The additional Telnet sessions should be through local
connections on the network element or a COLAN connection and not
through a DCC or ILAN connection.
Note 1: The OM3000 and OM4000 do not use Telnet (OM3000 uses TL1
sessions and OM4000 uses CLUI sessions). The TL1 and CLUI sessions
should be used for calculating the maximum number of Telnet sessions.
Note 2: To inhibit and allow AO message reporting on OME6500, use the
TL1 INH-MSG-ALL and ALL-MSG-ALL commands. The
INH-MSG-ALL command disables AO message reporting only for that
Telnet session.
Note 3: Each Site Manager session in OME6500 opens a Telnet session
(which should be counted towards the maximum number of Telnet
sessions). To inhibit AO message reporting from Site Manager, clear the
Auto Refresh check box in the Active Alarms application and run the
INH-MSG-ALL command from the TL1 Command Builder application.

To re-enable AO message reporting from Site Manager, run the

INH-MSG-ALL command from the TL1 Command Builder application
and select the Auto Refresh check box in the Active Alarms application if
real-time monitoring of alarms is required.
• Software release delivery
— Maximum of three parallel software release delivery operations per
GNE subnet (excluding the GNE itself). The software release delivery
to the GNE should be performed separately from the other network
elements in the GNE subnet.
• Serial ports
— AO message reporting should be disabled on serial port connections.
• Cross-connects
— Maximum of 6720 VT1.5/VC12 cross-connects (add/drop or
passthrough) per network element (25G of bidirectional VT1.5/VC12
connections).
— A network element with more than 4000 cross-connects must have
COLAN access.
• VT1.5/VC12 alarm enabling/disabling
— If failure conditions are present, commands to enable or disable
VT1.5/VC12 alarms should be performed on a single STS-1/VC4
granularity or smaller. There is an upper limit of 1344 enabled
VT1.5/VC12 alarms per interface circuit pack.
• Static routes
— A maximum of 10 static routes can be provisioned on an OME6500
network element.
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-71.
• 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 must decide how many bits define the subnetwork
and how many define the host ID, according to the actual and possible
future network architecture.
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 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
Example: 10010001
• 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:
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.
Circuitless IP interface
A circuitless IP interface (NE-IP interface on OME6500) 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.
Note: Some manufactures use other terms for the circuitless IP interface
(for example, loopback interface).
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
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
to the backbone area, or, where this is not possible, connected indirectly using
a ‘virtual link’ or tunnel. See Figure 10-16 on page 10-79.
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-18)
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.
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.
• 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.
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-16
(dashed line).
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.
Figure 10-16
OSPF areas
Area 1
Area 2
Area 0
(Backbone)
Area 3
virtual route Area4
Area 6
AUTONOMOUS SYSTEM (AU)
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.
• 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-17
Route summarization
.
Route summarization
140.100.10.0/24
140.150.10.0/24 Area Border 140.100.20.0/24
Router 140.100.30.0/24
140.100.40.0/24
140.150.10.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
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-18 shows an example of the way that static routes and default
routes are used.
Figure 10-18
Default and static routes
Intermediate router Subnetwork

Corporate Network 47.132.32.0/20
and Internet gateway
default route to
corporate network
route advertisement
static route (0.0.0.0 mask 0.0.0.0)
to subnetwork
route advertisement
(47.132.32.0 mask 255.255.240.0)

Subnetting and supernetting - IP addressing examples

When a network address is allocated, the network administrator may need to
subdivide the network into smaller subnetworks, based on the network
design. This is achieved by subnetting the network address, which consists in
subdividing the available network address range into smaller subnetwork
addresses ranges. To do so, the network administrator can allocate some of
the available bits for the subnetworks and some for the hosts.
Supernetting is the opposite of subnetting, as it consists in aggregating several

networks together into a single address and relevant address mask.
Supernetting is used for route summarization (sometimes called route
aggregation), to allow collections of networks to be advertised with a single
routing entry. This reduces the burden of big routing tables to advertise a
large number of hosts.
The following example shows typical IP addressing for an example network

containing two routers. The example is used to illustrate the mechanism of
address allocation and subnetting. You must remember to allow for network
expansion when allocating IP addresses. Failure to do so can lead to
unnecessary and time-consuming address reallocation when modifications to
the network are made.
Although not shown in these examples, when address availability is limited, it

may be beneficial to begin network numbering from the most significant end
of the mask to allow the network/host boundary to be redefined at a later date
without allocating new addresses. For example, if an allocation of IP addresses
were given with a mask of 255.255.240.0, six bits could be used for host (h)
and six bits for subnetworks (s):
11111111.11111111.1111nnnn.nnhhhhhh
Host numbering would start 000001, 000010, 000011 ..., but network
numbering would start at 100000, 010000, 110000, ... .
Figure 10-19 shows an example of two routers within a DCN,
Note: Figure 10-19 is only an example used to illustrate the general

principles of IP addressing allocation.
Figure 10-19
Example IP addressing for two routers within a DCN
Serial link 2
Serial link 1 S0 S1 S1 S0 Serial link 3
router 1 router 2
circuitless IP circuitless IP
Ethernet 0 Ethernet 0
LAN LAN
Between them, the two routers shown in Figure 10-19 have the following
interfaces:
• router 1, serial 0
• router 1, Ethernet 0
• router 1, circuitless IP
• router 2, Ethernet 0
• router 2, circuitless IP
Seven separate subnetworks are required. These are the networks connected to
R1 Ethernet 0, R1 circuitless IP, R2 Ethernet 0, and R2 circuitless IP, and the
three serial links. In order to provide seven subnetworks, three bits are
required.
If four bits are used for the subnetwork addresses, this gives provision for up
to 14 subnetworks; subnets 0000 and 1111 are reserved. This leaves four bits
that are used for the host ID.
However, not all the subnetworks need to be the same size. Only two devices
are on a WAN point-to-point link, so a mask of 255.255.255.252 would
suffice, giving four combinations (host ID of 00 and 11 not allowed).
Circuitless IP addresses are singularities and in general may have a mask of
255.255.255.255. In the following examples, one subnet has been further
subnetted for the serial links and another for the circuitless IP interfaces.

Note: Circuitless IP interfaces on Nortel Networks routers, running

versions of Bay RS prior to 15.0 must use a subnet mask of
255.255.255.252.
Four bits gives 16 combinations. The host IDs of 0000 and 1111 are reserved.
The Ethernet port of the router usually has host ID 0001. Therefore 0010 to
1110 are available for up to 13 other devices.
The subnetwork mask is therefore:

in binary:
11111111 11111111 11111111 1111 0000

Subnetwork Host ID
in decimal: 255.255.255.240
Subnetworks available with this mask are:
• 192.168.7.0 (reserved as the subnet field is all zeros)
• 192.168.7.16
• 192.168.7.32
• 192 168.7.192
• 192 168.7.208 (addresses in this range are used for serial interfaces with a
mask of 255.255.255.252, four addresses)
• 192 168.7.224 (addresses in this subnet range are used for circuitless IP
interfaces with a mask of 255.255.255.252, single address)
Therefore, the following addresses can be allocated for the Ethernet ports (see
Figure 10-20):
• R1 Ethernet 0
— subnetwork 192.168.7.16 (192.168.7.0 is reserved)
— IP address 192.168.7.17, subnetwork mask 255.255.255.240
— host ID for other devices connected to R1 Ethernet 0: 192.168.7.18 to
192.168.7.30
• R2 Ethernet 0
— subnetwork 192.168.7.32
— host ID for other devices connected to R2 Ethernet 0: 192.168.7.34 to
192.168.7.46
Circuitless IP addresses are as follows:

• R1 circuitless IP
• R2 circuitless IP
— IP address 192.168.7.229 subnetwork mask 255.255.255.255
Serial interface addresses are as follows:
• serial link 1
— subnetwork 192.168.7.208
— IP address 192.168.7.209 and 192.168.7.210*, subnetwork mask
255.255.255.252
• serial link 2
— subnetwork 192.168.7.212
— IP address 192.168.7.213 and 192.168.7.214, subnetwork mask
255.255.255.252
• serial link 3
— subnetwork 192.168.7.216
— IP address 192.168.7.217 and 192.168.7.218*, subnetwork mask
255.255.255.252
* These addresses are used by the routers at the other end of links 1 and 3.
Note 1: Subnetworks 192.168.7.48, 192.168.7.64, up to 192.168.7.192 are

available for future expansion.
Note 2: Note that network address 192.168.7.0 is used in order to leave
network addresses 192.168.1.0 through 192.168.6.0 for the management
areas.

Figure 10-20
Allocation of IP addresses
Serial link 2
Serial link 1 Serial link 3
192.168.7.212
192.168.7.208 S0 S1 S1 S0 192.168.7.216
circuitless IP: circuitless IP:

192.168.7.225 192.168.7.229
Ethernet 0: Ethernet 0:
S0 192.168.7 209 192.168.7.17 192.168.7.33 S0 192.168.7.217
S1 192.168.7.213 S1 192.168.7.214
LAN LAN
Subnet: Subnet:
192.168.7.16 192.168.7.32
Network: 192.168.7.0
Nortel
Optical Multiservice Edge

6500
Planning Guide
Copyright ã 2004-2005 Nortel Networks, All Rights Reserved
The information contained herein is the property of Nortel

Networks and is strictly confidential. Except as expressly
authorized in writing by Nortel Networks, the holder shall keep all
information contained herein confidential, shall disclose the
information only to its employees with a need to know, and shall
protect the information, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it uses
to protect its own confidential information, but with no less than
reasonable care. Except as expressly authorized in writing by
Nortel Networks, the holder is granted no rights to use the
information contained herein.
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.
Nortel, the Nortel logo, and the Globemark are trademarks of

Nortel Networks.
Netscape Navigator is a trademark of Netscape Communications

Corp.
Solaris, SunOs, and Sun Microsystems are trademarks of Sun
Microsystems, Inc.
Internet Explorer, Windows, and Windows NT are trademarks of
Microsoft Corporation.
NTRN10BC
Standard Release 1.2 Issue 1
April 2005
Printed in Canada

NTRN10BC - PG.r1.2 - OME6500 Planning Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NTRN10BC - PG.r1.2 - OME6500 Planning Guide

Uploaded by

Copyright:

Available Formats

Standard Release 1.2 Issue 1 April 2005

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

About this document xiii

Feature overview 2-1

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

Interworking with Nortel portfolio 2-25

Applications and upgrades 3-1

Hardware description 4-1

24xDS3/EC-1 working and protection circuit packs 4-44

User interface description 5-1

OAM&P description 6-1

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

Managing provisionable equipment 6-24

OME6500 local alarm indications 6-73

Technical specifications 7-1

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

OMX optical specifications 7-36

Ordering information 8-1

Technical assistance 9-1

Appendix A: Data communications planning 10-1

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

About this document 0

This planning guide describes the applications and functionality provided by

Supported software release

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

Optical Multiservice Edge 6500 NTP library

Planning a Network Installing, Managing and Maintaining and Supporting

About the Installation Security and Performance

This document refers to the following OME6500 supporting documentation:

This chapter provides an overview of the capabilities supported on the Nortel

The OME6500 combines and extends the advantages of next generation

The OME6500 epitomizes a new breed of optical networking platforms for

The OME6500 offers:

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

Figure 1-1 provides an illustration of the OME6500 shelf.

The OME6500 architecture supports a wide range of traffic protection and

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

Access Edge Core

10/100Base-T OM3/4K Scalable VT1.5/ Cost effective10Gbps

Converged "Connectivity Services" (Layer 0-2) network

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

In applications where there is a need to hand-off traffic to the Optical Cross

OME6500 service interfaces

Small-form factor pluggable (SFP)

Delivering first-in-cost, density, scale, and flexibility

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

Distributed service modules

Ethernet service modules (ESMs) providing compact 10/100Base-T,

The OME6500 platform supports 10/100Base-T, 100Base-FX, and GE

Point-to-point optical broadband services

GFP provides an efficient mechanism for GE and FC transport over a

The OME6500 also supports Virtual Concatenation (ITU-T G.707 compliant)

LCAS provides a soft protection and load-sharing mechanism to automatically

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

restoration LCAS can support hitless bandwidth expansion and contraction

TPE will address the following protocols not addressed by GFP:

Next generation RPR

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005

Nortel Networks' market leading RPR technology has been successfully

Network design is facilitated through Optical Planner. Optical Planner

Key features and benefits

Planning Guide NTRN10BC Rel 1.2 Iss 1 Standard Apr 2005